Mypower
S4100
Troubleshooting
Maipu Confidential & Proprietary Information
Page
112
of
124
negotiation parties. Modify the NET address to ensure consistency.
5.
IIH authentication types do not match.
How to find out the cause:
Open debug isis adj-packets to see the prompt message:
Authentication Failure.
Solution:
Check the IIH authentication type of the interface. Modify the
authentication type to ensure consistency.
6.
IIH authentication parameters do not match.
How to find out the cause:
Open debug isis adj-packets to see the prompt message:
Authentication Failure.
Solution:
Check the IIH authentication password of the interface. Modify the
authentication password to ensure consistency.
7.
The IS-IS network modes of the two interfaces are not
matched
How to find out the cause:
Open debug isis adj-packets to see the prompt message: Hello PDU
type invalid.
Solution:
Check the ISIS network mode of the interface. Modify the ISIS
network mode to ensure consistency.
8.
Parameter setting of the ISIS layer is not matched.
How to find out the cause:
Open debug isis adj-packets to see the prompt message: mismatch
with circuit type.
Solution:
Check the level parameter configuration of the ISIS process in the
two negotiation parties. Modify the level parameter to ensure
consistency.
9.
Parameter setting of the interface layer is not matched.
How to find out the cause:
Open debug isis adj-packets to see the prompt message: mismatch
with circuit type.
Solution:
Check the configuration of the level parameter. Modify the level
parameter to ensure consistency or to restore the default value
level-1-2.
10.
The ISIS external domain attributes are configured at the
opposite interface.
How to find out the cause:
Open the debug isis adj-packets command to see that the IIH
packets are sent but not received.
Solution:
Check the configuration of the opposite interface. Remove the
command of the ISIS external domain attributes.
11.
The opposite interface is set to the passive interface by the
ISIS process.
How to find out the cause:
Open the debug isis adj-packets command to see that the IIH
packets are sent but not received.
Solution:
Check the configuration of the opposite IS-IS process. Remove the
passive interface commands of the interface.
12.
The System IDs of the ISIS between neighbors are the same.
How to find out the cause: run the debug isis adj-packets
command, you can see Recv IIH have same source ID with local
system, discard; show run router isis, you can also see whether the
system ID is set to the neighbor system ID.
Solution:
