[c-nsp] SVI can't ping itself?

[Jeff Kell]

Can anyone think of a reason why a 6500's SVI's suddenly can't ping themselves?  Just noticed this a few days ago while troubleshooting something else altogether, and can't duplicate the problem on other switches (4500s, 3550s, etc).

> interface Vlan998
>  ip address 192.168.0.1 255.255.255.0
>  ip verify unicast reverse-path
>  ip helper-address 192.168.128.52
>  no ip redirects
>  no ip proxy-arp
>  ip pim sparse-dense-mode
>  ip route-cache flow
>  ip cgmp
>  arp timeout 240
>  no mop enabled
> end

Can't ping it normally:

> UTC-6509#ping 192.168.0.1
> 
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 192.168.0.1, timeout is 2 seconds:
> .....
> Success rate is 0 percent (0/5)

Can't extended ping explicitly from itself:

> UTC-6509#ping
> Protocol [ip]:                 
> Target IP address: 192.168.0.1     
> Repeat count [5]: 
> Datagram size [100]: 
> Timeout in seconds [2]: 
> Extended commands [n]: y
> Source address or interface: 192.168.0.1
> Type of service [0]: 
> Set DF bit in IP header? [no]: 
> Validate reply data? [no]: 
> Data pattern [0xABCD]: 
> Loose, Strict, Record, Timestamp, Verbose[none]: 
> Sweep range of sizes [n]: 
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 192.168.0.1, timeout is 2 seconds:
> .....
> Success rate is 0 percent (0/5)

Can't extended ping from another interface address:

> UTC-6509#ping            
> Protocol [ip]:     
> Target IP address: 192.168.0.1
> Repeat count [5]: 
> Datagram size [100]: 
> Timeout in seconds [2]: 
> Extended commands [n]: y
> Source address or interface: 172.31.0.1
> Type of service [0]: 
> Set DF bit in IP header? [no]: 
> Validate reply data? [no]: 
> Data pattern [0xABCD]: 
> Loose, Strict, Record, Timestamp, Verbose[none]: 
> Sweep range of sizes [n]: 
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 192.168.0.1, timeout is 2 seconds:
> .....
> Success rate is 0 percent (0/5)
> UTC-6509#

Jeff