Hi,
We have a problem with a "hanging" route in one of our asr9k. Even though the interface is numbered it is not considered connected.
Here is the interface config:
interface TenGigE0/1/0/3.950
ipv4 address 10.1.159.65 255.255.255.248
encapsulation dot1q 950
!
interface TenGigE0/1/0/3.951
ipv4 address 10.1.159.73 255.255.255.248
encapsulation dot1q 951
!
interface TenGigE0/1/0/3.952
ipv4 address 10.1.159.81 255.255.255.248
encapsulation dot1q 952
!
interface TenGigE0/1/0/3.953
ipv4 address 10.1.159.89 255.255.255.248
encapsulation dot1q 953
There is also a null-route for the larger /20 where these prefixes are included:
router static
address-family ipv4 unicast
10.1.144.0/20 Null0
The interface in question is TenGigE0/1/0/3.950. When we try to ping both the local ip of that interface and other end this is the result:
RP/0/RSP0/CPU0:router#ping 10.1.159.66
Fri Jul 6 10:37:30.195 MEST
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.159.66, timeout is 2 seconds:
UUUUU
Success rate is 0 percent (0/5)
RP/0/RSP0/CPU0:router#ping 10.1.159.65
Fri Jul 6 10:37:34.690 MEST
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.159.65, timeout is 2 seconds:
UUUUU
Success rate is 0 percent (0/5)
and the route looks like this:
RP/0/RSP0/CPU0:router#sh ip route 10.1.159.66
Fri Jul 6 10:37:48.249 MEST
Routing entry for 10.1.144.0/20
Known via "static", distance 1, metric 0 (connected)
Installed Jun 29 06:30:36.776 for 1w0d
Routing Descriptor Blocks
directly connected, via Null0
Route metric is 0
No advertising protos.
RP/0/RSP0/CPU0:router#sh ip route 10.1.159.65
Fri Jul 6 10:38:01.176 MEST
Routing entry for 10.1.144.0/20
Known via "static", distance 1, metric 0 (connected)
Installed Jun 29 06:30:36.779 for 1w0d
Routing Descriptor Blocks
directly connected, via Null0
Route metric is 0
No advertising protos.
Anyone have any idea why this has happened, and how to solve it? All other interfaces are working as expected.
Regards
Johny
