No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs on the product.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
OSPF/4/NSSA_TRANS_STATE_CHG

OSPF/4/NSSA_TRANS_STATE_CHG

Message

OSPF/4/OSPF_NSSA_TRANS_STATE_CHG: The status of the NSSA translator changes. (RouterId=[RouterId], AreaId=[AreaId], NSSATranslatorState=[NSSATranslatorState])

Description

The NSSA translator state of a switch changed between Enabled, Elected, and Disabled.

Parameters

Parameter Name Parameter Meaning

RouterId

Router ID

AreaId

ID of an NSSA

NSSATranslatorState

Current NSSA translator state

  • 1: ENABLED
  • 2: ELECTED
  • 3: DISABLED

Possible Causes

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

Cause 2: A new router ID has been configured for an ABR in the NSSA, and the configuration has taken effect.

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

Cause 4: In the backbone area or the NSSA, the OSPF protocol was restarted or the master/slave switchover was performed on a switch, causing topology flapping.

Cause 5: Manual command configuration or parameter modification causes a topology change in the backbone area or the NSSA. For example, parameters no-summary and no-import-route of the nssa command are configured on or removed from the current switch. As a result, the current switch needs to reestablish neighbor relationships in the backbone area or the NSSA.

Cause 6: The current switch has changed to be an ABR or a non-ABR.

Cause 7: The topology of the backbone area or the NSSA changes. As a result, the route from the current switch to an ABR with a larger router ID or for which translator-always is configured is unreachable in the backbone area or the NSSA.

Procedure

  1. If the parameter translator-always of the nssa command has been configured on or deleted from an ABR in the NSSA, run the display ospf brief command to check whether the NSSA translator state of the current switch is correct.

    • If yes, go to step 11.
    • If no, go to step 2.

  2. If the translator-always has been configured for an ABR in the NSSA using the nssa command, run the display ospf lsdb router command to check whether the Nt bit in the Router-LSA of the ABR changes or check whether the parameter translator-always has been configured for other ABRs in the NSSA by running the nssa command.

    • If yes, check whether the NSSA translator state of the current switch is correct.
      • If yes, go to step 11.
      • If no, go to step 3.
    • If no, go to step 3.

  3. If a new router ID has been configured for the current NSSA translator and the configuration takes effect, check whether the NSSA translator state of the current switch is correct after the topology in the NSSA is stable.

    • If yes, go to step 11.
    • If no, go to step 4.

  4. If a new router ID has been configured for an ABR other than the translator in the NSSA, check the configuration of other ABRs.

    • After the router ID of an ABR changes and the topology in the NSSA is stable, check whether the NSSA translator state of the current switch is correct.
      • If yes, go to step 11.
      • If no, go to step 5.

  5. If a new switch is added to the NSSA, or a switch is removed from the NSSA, perform operations as follows:

    • If the added or removed switch is not an ABR, check whether the NSSA translator state of the current switch is correct after the topology in the NSSA is stable.
      • If yes, go to step 11.
      • If no, go to step 6.
    • If the added or removed switch is an ABR, check whether the current switch has recovered to the original NSSA translator state after the topology in the NSSA is stable.
      • If yes, go to step 11.
      • If no, go to step 6.

  6. If manual command configuration or parameter modification causes a topology flapping in the backbone area or the NSSA, check whether the current switch has restored to the original NSSA translator state.

    • If yes, go to step 11.
    • If no, go to step 7.

  7. Run the display ospf brief command to check whether the current switch has changed to be an ABR or a non-ABR.

    • If the change is caused by manual configuration, check whether the NSSA translator state of the current switch is correct.
      • If yes, go to step 11.
      • If no, go to step 8.
    • If the change occurs without manual intervention, check whether the alarm OSPF_1.3.6.1.2.1.14.16.2.2 ospfNbrStateChange is reported on the current switch or its neighbors.
      • If yes, perform troubleshooting according to the online help of the alarm OSPF_1.3.6.1.2.1.14.16.2.2 ospfNbrStateChange.
      • If no, go to step 8.

  8. If the NSSA translator status of the current switch is changed from Disabled to Elected, and another switch has a larger router ID than the current switch or translator-always has been configured for another ABR, run the display ospf routing router-id [ router-id ] command to check whether the route from the current switch to the last NSSA translator in the backbone area or the NSSA is reachable.

    • If yes, go to step 10.
    • If no, the topology in the backbone area or the NSSA changes. Go to step 10.

  9. Check whether the alarm OSPF_1.3.6.1.2.1.14.16.2.2 ospfNbrStateChange is reported on the current switch or its neighbors.

    • If yes, perform troubleshooting. After the topology in the backbone area or the NSSA is stable, check whether the current switch has restored to the original NSSA translator state.
      • If yes, go to step 11.
      • If no, go to step 10.
    • If no, go to step 11.

  10. Collect the alarm, log, and configuration information, and contact technical support personnel technical support personnel.
  11. End.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 125829

Downloads: 90

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next