Asymetric Routing

[grahamuk2015]

Hi,

I think that we possibly have an asymetric routing issue and tried to run a ping with the record route option but when I do I get a time out. Just a standard ping to the same address works so I was just wondering if anyone knew if there are any configurtion settings that could prevent this from working? We are running HP Procurve 5406's .

Thanks,

Graham

[16again]

do a traceroute from both sides, to see path in both directions

Normally, routing on L3 switches is stateless, so assymetric routing shouldn't be an issue

[grahamuk2015]

I tried this again with a different IP address and it worked. This doesn't appear to show the information that I expected though. I am pinging from our site B switch to a server at site A and the traffic goes through our core switch at site A. The ping shows the address of our site A switch 10.1.1.1 and then the transit VLAN IP address 172.32.6.2 but I would expect to see this the other way round as it should hit the transit VLAN IP first?

I tried a tracert and I just see the transit VLAN IP's and nothing else.

ping 10.1.10.137 ip-option record-route repetitions 2
Sending 2, ICMP echos to 10.1.10.137, timeout is 3 seconds:
Packet has IP options: Total option = 39 bytes, padded length= 40
Recorded Route :  <*>
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
End of list

10.1.10.137 is alive, iteration 1, time = 3 ms
Packet has IP options: Total option = 40 bytes, padded length= 40
Recorded Route :
   (10.1.1.1)
   (172.32.6.2)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   <*>
End of list
10.1.10.137 is alive, iteration 2, time = 4 ms
Packet has IP options: Total option = 40 bytes, padded length= 40
Recorded Route :
   (10.1.1.1)
   (172.32.6.2)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   <*>

Thanks

[grahamuk2015 · Accepted solution]

I have done this via a pc now and I have a much more useful output. I just used ping -r and the external gateway address.