ISIS_1.3.6.1.3.37.2.0.16 isisProtocolsSupportedMismatch

Description

ISIS/2/PROTO_MISMATCH:OID [oid] The protocol of received Protocol TLV is mismatched with local configuration. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduProtocolsSupported=[opaque], pduLspId=[opaque], pduFragment=[opaque], ifName=[string])

The type of the protocol supported TLV (the type field being 0x81) carried in the received LSP mismatched with the type of the protocol supported by the local switch.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.3.37.2.0.16	Major	environmentalAlarm(6)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
sysInstance	Indicates the ID of the IS-IS process.
sysInstanceofLevel	Indicates the ID of the IS-IS process.
sysLevel	Indicates the IS-IS level: 1: Level-1 2: Level-2
sysInstanceofCircIfIndex	Indicates the ID of the IS-IS process.
circIndex	Indicates the index of the interface.
ifIndex	Indicates the index of the interface.
circIfIndex	Indicates the IF index of the interface.
pduProtocolsSupported	Indicates the supported protocol.
pduLspId	Indicates the ID of the LSP.
pduFragment	Indicates the fragment of 64-byte PDU header.
ifName	Indicates the name of the interface.

Impact on the System

LSPs cannot be learnt, and routes cannot be generated.

Possible Causes

The protocol type supported by the source switch that generated the LSP was different from that supported by the local switch.

Procedure

The type of the protocol supported TLV carried in the received LSP mismatched with the type of the protocol supported by the local switch. Check whether the trap is cleared in 10 minutes.
- If so, go to Step 3.
- If not, go to Step 2.
Collect the trap information, log information, and configuration of the switch, and contact technical support personnel.
End.

Related Information

None