Re: [c-nsp] Inconsistent CLNS/IS-IS routes

2013-05-02 Thread Adam Vitkovsky
I'd start by checking the isis database first. On Algiers do: ALG2-R26-01#sh isis dat 0030.6E4B.455C.00-00 ver (I'm not sure whether the name of the LSP ends with .00-00) . You can do: ALG2-R26-01#sh isis dat ver |be 0030.6E4B.455C You can also check whether you see the server's LSP on Oran. OR

[c-nsp] Inconsistent CLNS/IS-IS routes

2013-05-01 Thread Vincent DE KEYZER
Hello all, I'm back on c-nsp after several years of absence, convinced that I will get the usual good service... 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 no

[c-nsp] Inconsistent CLNS/IS-IS routes

2013-05-01 Thread Vincent DE KEYZER
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

Re: [c-nsp] Inconsistent CLNS/IS-IS routes

2013-05-01 Thread Vincent DE KEYZER
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