Unable to Ping or SNMP management address on two Switches in network

justinparsons · ‎07-10-2013

All

This is a very strange problem I am having.

In basic I have a server at our HQ site that is unable to ping, snmp, or anything to two switches on a remote site over the wan. Its strange because i can perform exactly the same task to two other switches in the same subnet to addresses either side of the non-working addresses. If you perform a trace to the site it gets a response all the way to the sites L3 switch and is unable to hop across to the vlan the switches are using for management.

To add more strangeness to this a server at the HQ site on the same subnet as the first server has no problems at all????? This can see all the switches on site.

How can two servers in the same subnet get two different responses?

Server 1 -

IP Address. . . . . . . . . . . . : 10.0.30.76

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.0.30.254

Server 2 - 10.0.30.185 / 24

IP Address. . . . . . . . . . . . : 10.0.30.185

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.0.30.254

Switch 10.220.56.7 - from Server 1

Tracing route to 10.220.56.7 over a maximum of 30 hops

1    <1 ms    <1 ms    <1 ms 10.0.30.252
2    <1 ms    <1 ms    <1 ms 10.220.20.2
3    <1 ms    <1 ms    <1 ms 10.0.99.154
4     8 ms     7 ms     3 ms 10.255.251.14
5     9 ms     7 ms     5 ms 10.244.1.254
6     *        *        *     Request timed out.
7     *        *        *     Request timed out.

Switch 10.220.56.7 - from Server 2

Tracing route to 10.220.56.7 over a maximum of 30 hops

1    <1 ms    <1 ms    <1 ms 10.0.30.252
2    <1 ms    <1 ms    <1 ms 128.1.100.4
3    <1 ms    <1 ms    <1 ms 10.0.99.154
4     9 ms     7 ms     7 ms 10.255.251.14
5    10 ms     7 ms     3 ms 10.244.1.254
6     7 ms     7 ms     8 ms 10.220.56.7

Trace complete.

Switch 10.220.56.8 - from Server 1

Tracing route to 10.220.56.8 over a maximum of 30 hops

1    <1 ms    <1 ms    <1 ms 10.0.30.252
2    <1 ms    <1 ms    <1 ms 10.220.0.130
3    <1 ms    <1 ms    <1 ms 10.0.99.154
4     7 ms     3 ms     7 ms 10.255.251.14
5     8 ms     7 ms     3 ms 10.244.1.254
6     8 ms     9 ms     7 ms 10.220.56.8

Trace complete.

Switch 10.220.56.8 - from Server 2

Tracing route to 10.220.56.8 over a maximum of 30 hops

1    <1 ms    <1 ms    <1 ms 10.0.30.252
2    <1 ms    <1 ms    <1 ms 128.1.100.4
3    <1 ms    <1 ms    <1 ms 10.0.99.154
4     9 ms     5 ms    10 ms 10.255.251.14
5    10 ms     4 ms     7 ms 10.244.1.254
6     6 ms     5 ms     6 ms 10.220.56.8

Trace complete.

Same Code:

Switch 10.220.56.7 - * 1 52 WS-C2960-48PST-L 12.2(55)SE5 C2960-LANBASEK9-M

Switch 10.220.56.8 - * 1 52 WS-C2960-48PST-L 12.2(55)SE5 C2960-LANBASEK9-M

Management Vlan:

Switch 10.220.56.7

interface Vlan15

ip address 10.220.56.7 255.255.254.0

!

ip default-gateway 10.220.56.1

Switch 10.220.56.8:

interface Vlan15
ip address 10.220.56.8 255.255.254.0
!
ip default-gateway 10.220.56.1

Any help would be much appreciated

mgaven · ‎07-10-2013

Justin, I think that could be a problem in an access list.

Have check you this?

justinparsons · ‎07-10-2013

Sorry No ACL being used, totaly open.

Thanks

justinparsons · ‎09-12-2013

Okay this has now been solved!

The switches were WS-C2960-48PST-L running 12.2(55)SE5.

All routing had been checked by our maintenance support guys but they found nothing.

Reloaded the switch and we regined full service back from the server; this worked for both switches that had the same problem. This must be a bug in the Cisco code or somthing, very strange but now working fine.