Why IS-IS adjacency is not UP ?

Basic routine performed when IS-IS adjacency is not UP on example lt-0/0/0.10 interface.

1. Check if ISO family is configured on interface
root# run show interfaces lt-0/0/0.10 | match iso 
    Protocol iso, MTU: 1497
2.Check what level was configured on interface. In this case only Level 1 was configured.
root# run show isis interface | match "Level|lt-0/0/0.10"  
Interface             L CirID Level 1 DR        Level 2 DR        L1/L2 Metric
lt-0/0/0.10           1   0x1 0172.0027.2554.02 Disabled               10/10
3.Check if authentication was configured.
root# run show isis authentication | match "Level|lt-0/0/0.10" 
Interface             Level IIH Auth  CSN Auth  PSN Auth
lt-0/0/0.10           1     Simple    MD5       MD5     
4. If simple Hello authentication was configured, check if keys are the same on the both sides. Please note that in this moment you could also check area address (49.0001). On Level 1 area addresses must be the same on both sides
root# run monitor traffic interface lt-0/0/0.10 detail           
16:16:43.340481 Out IS-IS, length 65
        L1 Lan IIH, hlen: 27, v: 1, pdu-v: 1, sys-id-len: 6 (0), max-area: 3 (0)
          source-id: 0172.0027.2551,  holding time: 6s, Flags: [Level 1 only]
          lan-id:    0172.0027.2554.02, Priority: 64, PDU length: 65
            IS Neighbor(s) TLV #6, length: 6
              SNPA: 0205.8671.5034
            Protocols supported TLV #129, length: 1
              NLPID(s): IPv4 (0xcc)
            IPv4 Interface address(es) TLV #132, length: 4
              IPv4 interface address:
            Area address(es) TLV #1, length: 4
              Area address (length: 3): 49.0001
            Restart Signaling TLV #211, length: 3
              Flags [none], Remaining holding time 0s
            Authentication TLV #10, length: 8
              simple text password: Juniper

What else can be checked ? :)

Brak komentarzy:

Prześlij komentarz