OSPFV3_1.3.6.1.2.1.191.0.11 ospfv3NssaTranslatorStatusChange

Trap Buffer Description

The status of the NSSA translator changes. (RouterId=[RouterId], AreaId=[AreaId], NSSATranslatorState=[NSSATranslatorState], ProcessId=[ProcessId])

The NSSA transition role may be changed because the status of the device changes between Enabled, Selected, and Disabled.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Warning
Mnemonic Code	OSPFV3_NSSA_TRANS_STATE_CHG
Trap OID	1.3.6.1.2.1.191.0.11
MIB	OSPFV3-MIB
Alarm ID	This is an event trap and does not involve alarm ID.
Alarm Name	This is an event trap and does not involve alarm name.
Alarm Type	This is an event trap and does not involve alarm type.
Raise or Clear	This is an event trap and does not involve alarm generation or clearance.
Match trap	-

Trap Buffer Parameters

Parameter	Description
RouterId	Router ID of the device generating this trap.
AreaId	Area ID of the NSSA.
NSSATranslatorState	New NSSA translator state, which can be: 1: ENABLED 2: ELECTED 3: DISABLED.
ProcessId	OSPFv3 process ID.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.2.1.191.1.1.1	ospfv3RouterId	-
1.3.6.1.2.1.191.1.2.1.12	ospfv3AreaNssaTranslatorState	ospfv3AreaId

Impact on the System

This trap indicates a translator change, which may affect the original route learning and calculation in the NSSA.

Possible Causes

Cause 1: The translator-always option of the NSSA command was manually configured or deleted on an ABR in the NSSA.

Cause 2: A new router ID is configured on an ABR in the NSSA and the new router ID takes effect.

Cause 3: A new device is added to the NSSA or a device is removed from the NSSA.

Cause 4: A device in the backbone area or the NSSA restarts OSPFv3 or performs a master/slave main control board switchover, causing topology flapping in the area.

Cause 5: The ABR role of the local device changed.

Cause 6: The topology of the backbone area or the NSSA changes. As a result, the local device cannot route routes from the backbone area or the NSSA to another ABR with a larger router ID or with the translator-always option configured.

Procedure

1. If the nssa translator-always command is manually configured or deleted, run the display ospfv3 area command to check whether the translator role is correct.

If nssa translator-always is configured, run the display ospfv3 area command to check whether the NSSA translator is always. If yes, go to step 8. If no, go to Step 7.
If the nssa translator-always configuration is deleted, run the display ospfv3 area command to check the NSSA translator status. If the NSSA translator status is Disabled, go to step 2. If the value is Selected, go to step 8.

2. The possible cause is that the nssa translator-always command is configured on an ABR in the NSSA. You can run the display ospfv3 [process-id] lsdb router command to check whether the Nt bit exists in the router-LSA of an ABR or check whether nssa translator-always is configured on other ABRs.

If Nt bit exists or nssa translator-always is configured on other ABRs, go to step 8.
If the Nt bit does not exist or nssa translator-always is not configured on other ABRs, go to step 3.

3. If a new router ID is configured on the local device and the new router ID takes effect, check whether the NSSA translation role of the local device is correct after the topology in the area becomes stable.

If yes, go to step 8.
If no, go to Step 4.

4. A new router ID may be configured on another ABR in the NSSA. Check the configurations of other ABRs.

Check whether the router ID of an ABR changes. After the topology in the area becomes stable, check whether the new router ID is greater than the local router ID.If yes, go to step 8.If no, go to Step 4.
If the ABR configuration is correct, go to Step 5.

5. If new devices are added to the NSSA:

Add an ABR. After the topology in the area becomes stable, check whether the router ID of the ABR is greater than the local router ID.If yes, go to step 8.If no, go to Step 6.
If the added device is not an ABR, go to Step 6.

6. Check whether alarms are generated on the local and neighboring devices.

OSPFV3_1.3.6.1.2.1.191.0.2 ospfv3NbrStateChange

, OSPFV3_1.3.6.1.2.1.191.0.10 ifstatechange

If any of the preceding alarms is generated, clear the alarm according to the related handling procedure.
If the preceding alarms do not exist, go to step 7.

7. Collect alarm and configuration information and contact technical support engineers.

8. End.