Hello All,

We're having an interesting issue with a Build 57 box on an X2100 M2
(dual bge, dual nge). After a certain amount of time/bandwidth
transferred (about 9 hours), any TCP services that had been constantly
in use during that time (SMTP & DNS) both become inaccessible. Also,
while you can ping the IP of the box from outside, trying to ping
anything from the box itself makes ping hang. This includes pinging
IPs on both nge and bge interfaces. Actually, after about 5 mins of
waiting the ping eventually succeeds, but you get this:

64 bytes from 10.1.62.1: icmp_seq=64. time=18001.518 ms
64 bytes from 10.1.62.1: icmp_seq=65. time=17001.515 ms
64 bytes from 10.1.62.1: icmp_seq=66. time=16001.543 ms
64 bytes from 10.1.62.1: icmp_seq=67. time=15001.567 ms
64 bytes from 10.1.62.1: icmp_seq=68. time=14001.583 ms
64 bytes from 10.1.62.1: icmp_seq=69. time=13001.598 ms
64 bytes from 10.1.62.1: icmp_seq=70. time=12001.621 ms
64 bytes from 10.1.62.1: icmp_seq=71. time=11001.640 ms
64 bytes from 10.1.62.1: icmp_seq=72. time=10001.661 ms
64 bytes from 10.1.62.1: icmp_seq=73. time=9001.682 ms
64 bytes from 10.1.62.1: icmp_seq=74. time=8001.698 ms
64 bytes from 10.1.62.1: icmp_seq=75. time=7001.719 ms
64 bytes from 10.1.62.1: icmp_seq=76. time=6001.738 ms
64 bytes from 10.1.62.1: icmp_seq=77. time=5001.761 ms
64 bytes from 10.1.62.1: icmp_seq=78. time=4001.780 ms
64 bytes from 10.1.62.1: icmp_seq=79. time=3001.799 ms
64 bytes from 10.1.62.1: icmp_seq=80. time=2001.819 ms
64 bytes from 10.1.62.1: icmp_seq=81. time=1001.842 ms
64 bytes from 10.1.62.1: icmp_seq=82. time=1.862 ms
64 bytes from 10.1.62.1: icmp_seq=83. time=1.809 ms
64 bytes from 10.1.62.1: icmp_seq=84. time=3.134 ms
64 bytes from 10.1.62.1: icmp_seq=85. time=1.934 ms
64 bytes from 10.1.62.1: icmp_seq=86. time=1.793 ms
64 bytes from 10.1.62.1: icmp_seq=87. time=2.586 ms
64 bytes from 10.1.62.1: icmp_seq=88. time=4.437 ms
64 bytes from 10.1.62.1: icmp_seq=89. time=1.772 ms
64 bytes from 10.1.62.1: icmp_seq=90. time=1.761 ms
64 bytes from 10.1.62.1: icmp_seq=91. time=1.760 ms
64 bytes from 10.1.62.1: icmp_seq=92. time=1.886 ms
64 bytes from 10.1.62.1: icmp_seq=93. time=1.747 ms
64 bytes from 10.1.62.1: icmp_seq=94. time=1.884 ms
64 bytes from 10.1.62.1: icmp_seq=95. time=1.731 ms
64 bytes from 10.1.62.1: icmp_seq=96. time=1.860 ms
64 bytes from 10.1.62.1: icmp_seq=97. time=1.982 ms
64 bytes from 10.1.62.1: icmp_seq=98. time=1.714 ms


Resetting the port on the switch side doesn't correct the issue...only
rebooting.  Also, there aren't any CRC or other ethernet errors logged
on the switch side (Foundry FastIron 800, F48-E JetCore 10/100 48-port
blade). Any ideas what could cause this?

Best Regards,
Jason
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to