ICMP Port Unreachable from gateway 10.40.20.154 for udp from testserver (10.40.20.13) to 10.20.250.16 port 33440

Unanswered Question
Apr 3rd, 2010

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

sir, why ICMP Port Unreachable from gateway 10.40.20.154

for udp from testserver (10.40.2013) to 10.20.250.16 port 33440 error message is coming.

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

testserver # ping -s 10.20.250.16

PING 10.20.250.16: 56 data bytes

64 bytes from 10.20.250.16: icmp_seq=0. time=1. ms

64 bytes from 10.20.250.16: icmp_seq=1. time=40152. ms

64 bytes from 10.20.250.16: icmp_seq=2. time=39152. ms

64 bytes from 10.20.250.16: icmp_seq=3. time=38154. ms

64 bytes from 10.20.250.16: icmp_seq=4. time=37155. ms

64 bytes from 10.20.250.16: icmp_seq=5. time=36156. ms

64 bytes from 10.20.250.16: icmp_seq=6. time=35157. ms

64 bytes from 10.20.250.16: icmp_seq=7. time=34158. ms

ICMP Time exceeded in transit from 10.40.20.122

for udp from testserver (10.40.2013) to 10.20.250.16 port 33437

ICMP Time exceeded in transit from 10.40.20.122

for udp from testserver (10.40.2013) to 10.20.250.16 port 33438

ICMP Time exceeded in transit from 10.40.20122

for udp from testserver (10.40.2013) to 10.20.250.16 port 33439

ICMP Port Unreachable from gateway 10.40.20.154

for udp from testserver (10.40.2013) to 10.20.250.16 port 33440

64 bytes from 10.20.250.16: icmp_seq=42. time=10036. ms

64 bytes from 10.20.250.16: icmp_seq=43. time=9037. ms

64 bytes from 10.20.250.16: icmp_seq=44. time=8039. ms

64 bytes from 10.20.250.16: icmp_seq=45. time=7040. ms

64 bytes from 10.20.250.16: icmp_seq=46. time=6041. ms

ICMP Port Unreachable from gateway 10.40.20.154

for udp from testserver (10.40.20.13) to 10.20.250.16 port 33442

64 bytes from 10.20.250.16: icmp_seq=47. time=5043. ms

64 bytes from 10.20.250.16: icmp_seq=48. time=4044. ms

64 bytes from 10.20.250.16: icmp_seq=49. time=3045. ms

64 bytes from 10.20.250.16: icmp_seq=53. time=0. ms

64 bytes from 10.20.250.16: icmp_seq=54. time=0. ms

64 bytes from 10.20.250.16: icmp_seq=55. time=1. ms

64 bytes from 10.20.250.16: icmp_seq=56. time=0. ms

64 bytes from 10.20.250.16: icmp_seq=57. time=1. ms

64 bytes from 10.20.250.16: icmp_seq=58. time=0. ms

^C

----10.20.250.16 PING Statistics----

59 packets transmitted, 22 packets received, 62% packet loss

round-trip (ms)  min/avg/max = 0/14200/40152

testserver #

Regards Senthil

Attachment: 
I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Ganesh Hariharan Sat, 04/03/2010 - 01:00

Hi,

Check out the reply given in your previous thread and follow the link hope that helps !!

Ganesh.H

Cisco are currently donating money to the Haiti earthquake appeal for every rating so please consider rating all helpful posts.

kumar94437 Sat, 04/03/2010 - 02:02

Sir,

i have checked that  link.As per that link i checked server.In server eeprom mac-address is true sir,Whether the problem is server or switch

Regards,

Senthil

Ganesh Hariharan Sun, 04/04/2010 - 23:43

Sir,

i have checked that  link.As per that link i checked server.In server eeprom mac-address is true sir,Whether the problem is server or switch

Regards,

Senthil

Senthil,

Check out the reply on previous messages and as said do either acces port or trunk port configuration on cisco 4507 switch and then check the responce from server.

Ganesh.H

kumar94437 Mon, 04/05/2010 - 00:13

Sir,

Thanks for your reply.i have removed trunking on 4507 switch.But still same problem exists.Ping output is as below.

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

testserver# ping -s 10.20.250.3

PING 10.20.250.3: 56 data bytes

64 bytes from 10.20.250.3: icmp_seq=0. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=1. time=40141. ms

64 bytes from 10.20.250.3: icmp_seq=2. time=39143. ms

64 bytes from 10.20.250.3: icmp_seq=3. time=38143. ms

64 bytes from 10.20.250.3: icmp_seq=4. time=37144. ms

64 bytes from 10.20.250.3: icmp_seq=5. time=36146. ms

64 bytes from 10.20.250.3: icmp_seq=6. time=35146. ms

64 bytes from 10.20.250.3: icmp_seq=7. time=34147. ms

64 bytes from 10.20.250.3: icmp_seq=8. time=33148. ms

64 bytes from 10.20.250.3: icmp_seq=42. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=43. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=44. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=45. time=1. ms

64 bytes from 10.20.250.3: icmp_seq=46. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=47. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=48. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=49. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=50. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=51. time=1. ms

64 bytes from 10.20.250.3: icmp_seq=52. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=53. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=54. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=55. time=1. ms

64 bytes from 10.20.250.3: icmp_seq=56. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=57. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=58. time=2. ms

64 bytes from 10.20.250.3: icmp_seq=59. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=60. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=61. time=2. ms

64 bytes from 10.20.250.3: icmp_seq=62. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=63. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=64. time=2. ms

64 bytes from 10.20.250.3: icmp_seq=65. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=66. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=67. time=1. ms

64 bytes from 10.20.250.3: icmp_seq=68. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=69. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=70. time=1. ms

64 bytes from 10.20.250.3: icmp_seq=71. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=72. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=73. time=1. ms

64 bytes from 10.20.250.3: icmp_seq=74. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=75. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=76. time=1. ms

64 bytes from 10.20.250.3: icmp_seq=77. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=78. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=79. time=1. ms

64 bytes from 10.20.250.3: icmp_seq=80. time=1. ms

64 bytes from 10.20.250.3: icmp_seq=81. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=82. time=1. ms

64 bytes from 10.20.250.3: icmp_seq=83. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=84. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=85. time=1. ms

64 bytes from 10.20.250.3: icmp_seq=86. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=87. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=88. time=1. ms

64 bytes from 10.20.250.3: icmp_seq=89. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=90. time=0. ms

64 bytes from 10.20.250.3: icmp_seq=91. time=1. ms

^C

----10.20.250.3 PING Statistics----

92 packets transmitted, 59 packets received, 35% packet loss

round-trip (ms)  min/avg/max = 0/4969/40141

testserver#

Output is having 35% only .

Regards,

senthil

Ganesh Hariharan Mon, 04/05/2010 - 00:16

Senthil,

Can you also check the port duplex setting the server is conencted to switch and switch to switch connectivity,right now are you getting the same message repeatedly which was earlier in you r message you are having packet loss.

Ganesh.H

kumar94437 Mon, 04/05/2010 - 00:53

Sir,

Actually switch is having two vlans.vlan 1-10.20.250.3 and vlan 2 is 10.40.20.154

I can able to ping vlan ip 2 (10.40.20.154) without any loss from server.While pinging vlan ip 1(10.20.250.3) then only this problem is coming.

Regards,

Senthil

Ganesh Hariharan Mon, 04/05/2010 - 01:44

Sir,

Actually switch is having two vlans.vlan 1-10.20.250.3 and vlan 2 is 10.40.20.154

I can able to ping vlan ip 2 (10.40.20.154) without any loss from server.While pinging vlan ip 1(10.20.250.3) then only this problem is coming.

Regards,

Senthil

Senthil,

Configure trunking between the switches and then check what is the status.

Ganesh.H

Actions

This Discussion