OSPF/2/NSSATRANCHG:OID [oid]: The status of the NSSA translator changes. (AreaId=[area-id], ProcessId=[process-id], RouterId=[router-id], NSSATranslatorState=[translator-state], InstanceName=[instance-name])
The translator role in the NSSA changed. A possible cause is that the status of the translator changed among Enabled, Elected, and Disabled.
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
AreaId |
Indicates the area ID of the NSSA. |
ProcessId |
Indicates the process ID. |
RouterId |
Indicates the ID of the switch that generates the trap. |
NSSATranslatorState |
Indicates the new status of the translator
in the NSSA.
|
InstanceName |
Indicates the instance name. |
ASE routes may flap for a short period in the following situations. The role of the NSSA ABR changes; the Type 5 LSAs translated from Type 7 LSAs need to be flushed; or a new translator is translating Type 7 LSAs to Type 5 LSAs. Moreover, the translator role changes without manual configuration mostly because the topology in the backbone area or the NSSA changes.
1. The parameter translator-always in the nssa command was manually configured or canceled on an ABR in the NSSA.
2. A new router ID was configured on an ABR in the NSSA and took effect.
3. A new switch joined the NSSA or a switch exited from the NSSA.
4. The OSPF protocol was restarted or the master/slave switchover was performed on a switch in the backbone area or the NSSA. This caused topology change in the NSSA.
5. The nssa command was manually configured or parameters in the nssa command were manually modified, which caused topology flapping in the backbone area or the NSSA. For example, configuring or canceling the parameter no-summary or no-import-route in the nssa command will lead to the reestablishment of the neighbor relationship between the local switch and a switch in the backbone area and between the local switch and a switch in the NSSA.
6. The role of the local switch changed to ABR or changed from ABR.
7. The topology of the backbone area or the NSSA changed. As a result, the local switch cannot reach another ABR with a greater router ID or with the parameter translator-always from the backbone area or the NSSA.
If the nssa translator-always command is configured, run the display ospf brief command to check whether the status of the NSSA translator is always. If so, go to Step 8. If not, go to Step 7.
If the configuration about nssa translator-always is canceled, run the display ospf brief command to check the status of the NSSA translator. If the status is disabled, go to Step 2. If the status is elected, go to Step 8.
If the Router-LSA of some ABR contains the Nt bit or an ABR has been configured with the nssa translator-always command, go to Step 8.
If there is no ABR whose Router-LSA contains the Nt bit or no ABR is configured with the nssa translator-always command, go to Step 3.
If so, go to Step 8.
If not, go to Step 4.
If so, go to Step 8.
If not, go to Step 5.
If the router ID of an ABR remains unchanged, go to Step 5.
If so, go to Step 8.
If not, go to Step 6.
If the new joint switch is not an ABR, go to Step 6.