Hi,
I am trying to establish an adjacency between a Juniper MX switch and a NX-OS 7700 device running NX-OS 6.2
It's a fairly basic configuation, on the Nexus side:
version 6.2(12)
feature isis
router isis LAB
net 49.0001.0100.7907.9004.00
is-type level-2
address-family ipv6 unicast
interface Ethernet1/2/4
ipv6 router isis LAB
no isis hello-padding
isis circuit-type level-2
The adjacency comes up but stays in the INIT state, and I see the following in the NX-OS logs:
2017 May 15 17:11:20.929843 isis: LAB [29880] Receive L2 LAN IIH over Ethernet1/2/4 from XXXX.2711.7000 (f4b5.2f71.dfc4) len 59 prio 7
2017 May 15 17:11:20.929912 isis: LAB [29880] Fail to find IPv4 address TLV mt 0
2017 May 15 17:11:20.929991 isis: LAB [29880] Fail to find iih nbr tlv
2017 May 15 17:11:20.930022 isis: LAB [29880] Neighbor TLV missing in hello from XXXX.2711.7000 , hence adjacency in INIT state
2017 May 15 17:11:20.930044 isis: LAB [29880] Obtained Restart TLV RR=0, RA=0, SA=0
2017 May 15 17:11:20.930067 isis: LAB [29880] Remaining Time 0 for SID 0000.0000.0000
The IS-IS IIH looks right on the Juniper side:
17:22:21.246503 Out IS-IS, length 59
L2 Lan IIH, hlen: 27, v: 1, pdu-v: 1, sys-id-len: 6 (0), max-area: 3 (0)
source-id: XXXX.2711.7000, holding time: 27s, Flags: [Level 2 only]
lan-id: XXXX.2711.7000.00, Priority: 64, PDU length: 59
Protocols supported TLV #129, length: 1
NLPID(s): IPv6 (0x8e)
IPv6 Interface address(es) TLV #232, length: 16
IPv6 interface address: fe80::f6b5:2fff:fe71:dfc4
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
What might be causing the adjancecy to stick in the INIT state?
Cheers,
Matt
