Page 1 of 1

Cisco ISIS Neighbor Init State

Posted: 30 Jan 2018 03:52
by plawansai
Cisco#show isis neighbor

System Id Type Interface IP Address State Holdtime Circuit Id
010x.xx04.7136 L2 Po5 10.2.2.18 INIT 24 00

A:Nokia# show router isis adjacency
No Matching Entries

I tried to debug on Nokia side but not see any debug log:
debug router isis adjacency
configure log log-id 1 from debug-trace
configure log log-id 1 to session


A:Nokia# show log log-id

Log Source Filter Admin Oper Logged Dropped Dest Dest Size
Id Id State State Type Id
------------------------------------------------------------------------------
1 D none up up 0 0 session N/A

A:Nokia# show router isis interface

===============================================================================
Router Base ISIS Instance 0 Interfaces
===============================================================================
Interface Level CircID Oper State L1/L2 Metric
-------------------------------------------------------------------------------
To_Cisco L2 4 Up -/10

How should I do :?:

Thank you very much.

Re: Cisco ISIS Neighbor Init State

Posted: 30 Jan 2018 05:44
by mivens
Try "debug router isis packet "To_Cisco L2 ".
You can constrain it further to just the hellos, if you want.
For example, if it's a p2p link, "debug router isis packet ptop-hello "To_Cisco L2 "

Also check the MTUs are consistent on both sides, depending on how you have hello padding configured on both ends.

Re: Cisco ISIS Neighbor Init State

Posted: 30 Jan 2018 06:16
by paramount
HI,

it's also worth sharing the configs you have at each end along with info on the interfaces. Although ISIS is not an IP protocol, is ping successful between the interfaces?

Have you set the NET on the Cisco, as it won't even start ISIS until it has this.

Cheers
Paramount

Re: Cisco ISIS Neighbor Init State

Posted: 31 Jan 2018 00:59
by plawansai
OK, Solved.
The MTU between Nokia and Cisco IOS should be 14 bytes different.

Thank you very much.