Virtual management IP of 8600 is 10.192.1.160 (slot 5 is .161, slot 6 is .162).
From other subnets on our network I can ping 10.192.1.160 and get reply.
From 8600 I can ping other IP's on 10.192.1 subnet and get reply.
From 8600 when I ping IP's that are on other subnets I do not get reply.
Packet captures show the traffic initiated by 8600 to other subnets comes across with source IP of 10.192.1.250 (wrong IP).
10.192.1.250 is not in config.cfg or boot.cfg.
10.192.1.250 is not in ARP table for router that routes 10.192.1.
No NAT or static ARP on router that routes 10.192.1.
8600 has route for 10. subnets.
We have several other 8600's with similar setup, never had this problem.
Can't figure out why traffic that should be coming from 10.192.1.160 is associated with 10.192.1.250.
From other subnets on our network I can ping 10.192.1.160 and get reply.
From 8600 I can ping other IP's on 10.192.1 subnet and get reply.
From 8600 when I ping IP's that are on other subnets I do not get reply.
Packet captures show the traffic initiated by 8600 to other subnets comes across with source IP of 10.192.1.250 (wrong IP).
10.192.1.250 is not in config.cfg or boot.cfg.
10.192.1.250 is not in ARP table for router that routes 10.192.1.
No NAT or static ARP on router that routes 10.192.1.
8600 has route for 10. subnets.
We have several other 8600's with similar setup, never had this problem.
Can't figure out why traffic that should be coming from 10.192.1.160 is associated with 10.192.1.250.
Comment