[c-nsp] Inconsistent CLNS/IS-IS routes
Vincent DE KEYZER
vdekeyzer at wis-telecom.com
Fri Jan 11 11:28:13 EST 2013
Hello all,
We are currently troubleshooting an old, badly-documented, non-supported, CLNS/IS-IS network (for management of Alcatel NEs).
One of the issues we have identified is IS-IS routes not being announced by one router to another (this might or might not explain the overall problem of no connectivity, but let's go step by step).
The two routers are ALGiers and ORAn, directly connected with a serial E1 link.
The adjacency looks good to me. Algiers correctly sees Oran (and has a CLNS neighborship via the server we are interested in):
ALG2-R26-01#sh clns ne
System Id Interface SNPA State Holdtime Type Protocol
0007.729E.FFEE Et0/1 0007.729e.ffee Up 92 L1 IS-IS
0007.72A2.FEA6 Et0/1 0007.72a2.fea6 Up 91 L1 IS-IS
0020.602B.CBB4 Et0/1 0020.602b.cbb4 Up 95 L1 IS-IS
0020.6013.2DD2 Et0/1 0020.604a.972e Up 92 L1 IS-IS
--> 0030.6E4B.455C Et0/1 0011.85c7.3ec0 Up 97 L1 IS-IS <----- Server
0030.6E4B.47DB Et0/1 0012.799d.51a6 Up 95 L1 IS-IS
rtrnoc01 Et0/1 0014.1ce6.60fd Up 9 L1L2 IS-IS
rtrann01 Se0/2 *PPP* Up 24 L1L2 IS-IS
--> rtrora01 Se0/3 *PPP* Up 26 L1L2 IS-IS <----- Oran router
1880.F524.8FF0 Et0/1 1880.f52d.958e Init 48 L1 IS-IS
ALG2-R26-01#
Oran sees Algiers:
ORA1-R26-01#sh clns ne
System Id Interface SNPA State Holdtime Type Protocol
0020.6013.37F2 Fa0/1 0020.6013.37f2 Up 96 L1 IS-IS
--> rtrnal01 Se0/1/1:0 *PPP* Up 24 L1L2 IS-IS <----- Algiers router
rtralg01 Se0/1/0:0 *PPP* Up 28 L1L2 IS-IS
0020.602B.CF8A Fa0/1 0020.602b.cf8a Up 46 L1 IS-IS
0080.9F20.0931 Fa0/1 0080.9f20.03a3 Up 93 L1 IS-IS
ORA1-R26-01#
But Oran does not seem receive from Algiers any of its 6 CLNS neighbors (and that includes the server):
ORA1-R26-01#sh isis route | i 455C
ORA1-R26-01#
You can see that the CLNS names are not consistent with the hostnames, but CDP does confirm the situation
ALG2-R26-01#sh cdp ne
Device ID Local Intrfce Holdtme Capability Platform Port ID
ORA1-R26-01 Ser 0/3 163 R S I Cisco 2801Ser 0/1/1:0
(...)
All seven routers in the network have already been rebooted.
Any idea why this inconsistency, or on how to troubleshoot further?
Thanks,
Vincent
[WIS Logo]
Vincent DE KEYZER - Provisioning & Support Manager
WIS TELECOM
[WIS BAND]<http://www.wis-telecom.com>
Rue du Commerce, 23
B-1400 Nivelles - Belgium
vdekeyzer at wis-telecom.com<mailto:vdekeyzer at wis-telecom.com> T +32 67 740 826
F +32 67 411 881
M +32 493 511 052
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20130111/d736c533/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: new_logo_wis_email152b.png
Type: image/png
Size: 7607 bytes
Desc: new_logo_wis_email152b.png
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20130111/d736c533/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: banda_wis_telecom4887.png
Type: image/png
Size: 2554 bytes
Desc: banda_wis_telecom4887.png
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20130111/d736c533/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: spacer_tabella18d5.png
Type: image/png
Size: 126 bytes
Desc: spacer_tabella18d5.png
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20130111/d736c533/attachment-0005.png>
More information about the cisco-nsp
mailing list