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

S12700 V200R013C00 Log Reference

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).
OSPFV3

OSPFV3

OSPFV3/4/OSPFV3_AUTO_CHG_RTRID

Message

OSPFV3/4/OSPFV3_AUTO_CHG_RTRID: OSPFV3 automatically changes the router ID when detecting router ID conflict in the area. (ProcessId=[USHORT], NewRouterId=[STRING], OldRouterId=[STRING], ConflictRtrIdNum=[ULONG])

Description

OSPFv3 automatically changed the router ID when two or more same router IDs were detected in an area.

Parameters

Parameter Name Parameter Meaning
ProcessId Process ID.
NewRouterId New router ID.
OldRouterId Original router ID.
ConflictRtrIdNum Number of conflict router IDs.

Possible Causes

The same router ID was configured for at least two indirectly connected routers within one area, which caused the router lSA to be refreshed frequently. As a result, route flapping occurred.

Procedure

  1. If the undo ospfv3 router-id auto-recover disable command is enabled by default, the system will be automatically restored after two or more same router IDs are detected.
  2. If the system cannot be restored automatically, change a router ID manually.

OSPFV3/6/BFD_RM_EVNT

Message

OSPFV3/6/BFD_RM_EVNT: OSPFv3 BFD Received event notification [ULONG] from RM on interface [STRING] for remote IPv6 address [STRING].

Description

When RM notifies any BFD related event change, this dialog is displayed.

Parameters

Parameter Name Parameter Meaning

[ULONG]

Indicates the BFD event value from RM

[STRING]

Indicates the Interface name

  • Create/update BFD sessions
  • Delete BFD sessions

[STRING]

Indicates the IPv6 address.

Possible Causes

RM notifies any BFD related event change.

Procedure

  1. This log message is informational only, and no action is required.

OSPFV3/6/BFD_SESSION_NTFY

Message

OSPFV3/6/BFD_SESSION_NTFY: OSPFv3 BFD sending session [STRING] notification to RM on interface [STRING] for remote IPv6 address [STRING]. (MinTransmitInterval=[ULONG], MinReceiveInterval=[ULONG], DetectMultiplier=[ULONG])

Description

When OSPFv3 notifies RM to create, delete or update BFD session, this dialog is displayed.

Parameters

Parameter Name Parameter Meaning

[STRING]

Indicates the BFD event value from RM

[STRING]

Indicates the Interface name

  • Create/update BFD sessions
  • Delete BFD sessions

[STRING]

Indicates the IPv6 address.

MinTransmitInterval

Indicates minimum transmit interval for BFD support in OSPFv3 on a given OSPFv3 process.

MinReceiveInterval

Indicates minimum receive interval for BFD support in OSPFv3 on a given OSPFv3 process.

DetectMultiplier

Indicates detect multiplier value for BFD support in OSPFv3 on a given OSPFv3 process.

Possible Causes

BFD enabled OSPFv3 adjacency is formed or broken down.

Procedure

  1. This log message is informational only, and no action is required.

OSPFV3/4/OSPFV3_CONFLICT_ROUTERID_INTER

Message

OSPFV3/4/OSPFV3_CONFLICT_ROUTERID_INTER: OSPFv3 router ID conflict may have occurred in inter-area.(ProcessId=[USHORT], RouterId=[STRING])

Description

The router IDs of OSPFv3 devices in different areas might conflict because external routes were constantly refreshed.

Parameters

Parameter Name Parameter Meaning
ProcessId Indicates the ID of a process.
RouterId Indicates the ID of a router.

Possible Causes

The same router ID was configured for devices in different areas, causing route flapping.

This log is generated in the following scenarios:

  • Normal scenario: Device A generates a Type 5 LSA and floods it to Device B. Due to a fault, Device A restarts and reestablishes the neighbor relationship with Device B. Then, Device A receives the Type 5 LSA generated by itself from Device B. Because the router ID in the LSA conflicts with the local one, the log is generated. A large number of Type 5 LSAs may exist in the system. Therefore, this scenario is common. The log generated in this scenario requires no action.
  • Conflict scenario: The same router ID is configured for devices in different areas, causing route flapping.

Procedure

  1. Run the router-id router-id command to change the router ID.
  2. End.

OSPFV3/4/OSPFV3_CONFLICT_ROUTERID_INTF

Message

OSPFV3/4/OSPFV3_CONFLICT_ROUTERID_INTF: OSPFv3 router ID conflict is detected on the interface.(ProcessId=[USHORT], RouterId=[STRING], AreaId=[STRING], InterfaceName=[STRING], InstanceId=[ULONG], IpAddr=[STRING], PacketSrcIp=[STRING])

Description

A router ID conflict was detected on an OSPFv3 interface.

Parameters

Parameter Name Parameter Meaning
ProcessId Indicates the ID of a process.
RouterId Indicates the ID of a router.
AreaId Indicates the ID of an area.
InterfaceName Indicates the name of an interface.
InstanceId Indicates the ID of an instance.
IpAddr Indicates an IP address.
PacketSrcIp Indicates the source address of a packet.

Possible Causes

The router IDs of directly connected interfaces conflicted.

Procedure

  1. Run the router-id router-id command to change the router ID.
  2. End.

OSPFV3/4/OSPFV3_CONFLICT_ROUTERID_INTRA

Message

OSPFV3/4/OSPFV3_CONFLICT_ROUTERID_INTRA:OSPFv3 router ID conflict is detected in intra-area.(ProcessId=[USHORT], RouterId=[STRING], AreaId=[STRING])

Description

A router ID conflict was detected in an OSPFv3 area.

Parameters

Parameter Name Parameter Meaning
ProcessId Indicates the ID of a process.
RouterId Indicates the router ID of a router.
AreaId Indicates the ID of an area.

Possible Causes

At least two indirectly routers were configured with the same router ID, causing router LSAs to be constantly refreshed. As a result, route flapping occurs.

Procedure

  1. Run the router-id router-id command to change the router ID.
  2. End.

OSPFV3/3/GRBCKLNKERR

Message

OSPFV3/3/GRBCKLNKERR: There is no link to restarting router in the received LSA, so prematurely exit graceful restart and reset OSPFv3 [ULONG] process.

Description

No link to the GR router existed in the new LSA. Then GR was quitted.

Parameters

Parameter Name Parameter Meaning

[ULONG]

Indicates the process ID.

Possible Causes

No link to the GR router existed in the new LSA. Then GR was prematurely quitted and the OSPFv3 protocol was reset.

Procedure

  1. This log message is informational only, and no action is required.

OSPFV3/3/GRFLLALLNBRERR

Message

OSPFV3/3/GRFLLALLNBRERR: OSPFv3 [ULONG] restarting router is full with all the neighbors, hence exiting graceful restart.

Description

The OSPFv3 process became full with all the neighbors. Then GR was quitted.

Parameters

Parameter Name Parameter Meaning
[ULONG] Indicates the process ID.

Possible Causes

The OSPFv3 process became full with all the neighbors during GR.

Procedure

  1. This log message is informational only, and no action is required.

OSPFV3/3/GRINTFDWNERR

Message

OSPFV3/3/GRINTFDWNERR: Interface [STRING] state changed in restarting router, so prematurely exit graceful restart and reset OSPFv3 [ULONG] process.

Description

The OSPFv3-GR interface was Down during GR.

Parameters

Parameter Name Parameter Meaning
[STRING] Indicates the process ID.
[ULONG] Indicates the interface name.

Possible Causes

The OSPFv3-GR interface was Down during GR. Then GR was prematurely quitted and the OSPFv3 protocol was reset.

Procedure

  1. This log message is informational only, and no action is required.

OSPFV3/6/GRNOHLPCNFG

Message

OSPFV3/6/GRNOHLPCNFG: OSPFv3 [ULONG] helper is not configured.

Description

No helper configuration was present.

Parameters

Parameter Name Parameter Meaning
[ULONG] Indicates the process ID.

Possible Causes

No helper configuration was present.

Procedure

  1. This log message is informational only, and no action is required.

OSPFV3/3/GRNORMALRSTERR

Message

OSPFV3/3/GRNORMALRSTERR: Exited from graceful restart because normal reset is executed on OSPFv3 process [ULONG].

Description

The normal reset was finished, and GR was quitted.

Parameters

Parameter Name Parameter Meaning
[ULONG] Indicates the process ID.

Possible Causes

The OSPFv3 process was reset during GR. Then GR was prematurely quitted and the OSPFv3 protocol was reset.

Procedure

  1. This log message is informational only, and no action is required.

OSPFV3/6/GRNOTENBL

Message

OSPFV3/6/GRNOTENBL: OSPFv3 [ULONG] graceful restart is not enabled.

Description

The GR function was not enabled.

Parameters

Parameter Name Parameter Meaning
[ULONG] Indicates the process ID.

Possible Causes

The GR function was not configured.

Procedure

  1. Configure the GR function and run the reset ospfv3 command to restart the OSPFv3 protocol.

OSPFV3/3/GRPRDEXPERR

Message

OSPFV3/3/GRPRDEXPERR: OSPFv3 [ULONG] grace period timer expired.

Description

The GR period timer expired.

Parameters

Parameter Name Parameter Meaning
[ULONG] Indicates the process ID.

Possible Causes

The GR period timer in the OSPFv3 process expired.

Procedure

  1. This log message is informational only, and no action is required.

OSPFV3/3/GRPROCDELERR

Message

OSPFV3/3/GRPROCDELERR: Exited from graceful restart because OSPFv3 process [ULONG] is deleted.

Description

GR was quitted because the GR process was deleted.

Parameters

Parameter Name Parameter Meaning
[ULONG] Indicates the process ID.

Possible Causes

The OSPFv3 process was deleted during GR. Then GR was prematurely quitted and the OSPFv3 protocol was reset.

Procedure

  1. This log message is informational only, and no action is required.

OSPFV3/3/GRSLFORGNTWKMSSERR

Message

OSPFV3/3/GRSLFORGNTWKMSSERR: Exited graceful restart as self originated Network-LSAs were not received from the neighbor [STRING] on interface [STRING] during database synchronization for OSPFv3 process [ULONG].

Description

During the period of Database Description packets exchange, the pre-restart network LSAs that were self originated were not received. Then GR was quitted.

Parameters

Parameter Name Parameter Meaning
[STRING] Indicates the ID of the neighbor router.
[STRING] Indicates the interface name.
[ULONG] Indicates the process ID.

Possible Causes

No pre-restart network LSA that was self originated was received. This showed that at least one neighbor was not the helper. Then GR was prematurely quitted and the OSPFv3 protocol was reset.

Procedure

  1. This log message is informational only, and no action is required.

OSPFV3/4/HELLO_DELAY

Message

OSPFV3/4/HELLO_DELAY: Sending hello packet on the interface [STRING] is delayed more than 3 times of the hello interval.

Description

Interval between last sending hello packet and current hello packet sending is greater than three times hello interval which may indicate task schedule delay.

Parameters

Parameter Name Parameter Meaning
[STRING] Indicates the name of interface.

Possible Causes

Interval between last sending hello packet and current hello packet sending is greater than three times hello interval which may indicate task schedule delay.

Procedure

  1. This log message is informational only, and no action is required.

OSPFV3/6/IFSMCHG

Message

OSPFV3/6/IFSMCHG:Interface [interface-name] state changed from [old-interface-state] to [new-interface-state]. (Event=[STRING], ProcessId=[ULONG])

Description

The interface status changed from status 1 to status 2.

Parameters

Parameter Name Parameter Meaning
[interface-name] Indicates the interface name.
[old-interface-state] Indicates the old interface status.
[new-interface-state] Indicates the new interface status.
Event Indicates the interface event.
ProcessId Indicates the process ID.

Possible Causes

The interface status changed.

Procedure

  1. This log message is informational only, and no action is required.

OSPFV3/4/MAXEXTROUTESLIMIT

Message

OSPFV3/4/MAXEXTROUTESLIMIT: OSPFv3 [ULONG] external route addition is unsuccessful due to maximum limit.

Description

The maximum number of configurable external routes was reached.

Parameters

Parameter Name Parameter Meaning
[ULONG] Indicates the process ID.

Possible Causes

The maximum number of configurable external routes was reached.

Procedure

  1. Change the PAF/LCS of the router or reduce the route count.

OSPFV3/4/MEMSHORT

Message

OSPFV3/4/MEMSHORT:Received memory shortage notification from memory management.

Description

Received the memory shortage notification from the memory management module.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

The memory was insufficient.

Procedure

  1. Run the display diagnostic-information command to save the displayed result and contact technical support personnel.

OSPFV3/4/NBR_FLAP_SUPPR_STATUS

Message

OSPFV3/4/NBR_FLAP_SUPPR_STATUS: The status of peer flapping suppress is changed.(ProcessId=[USHORT], AreaId=[STRING], ifName=[STRING], SuppressStatus=[STRING], LastSuppressStatus=[STRING])

Description

The status of OSPFv3 neighbor relationship flapping suppression changed on the local interface.

Parameters

Parameter Name Parameter Meaning
ProcessId

Process ID

AreaId

Area ID

ifName

Interface name

SuppressStatus

Suppression status

LastSuppressStatus

Original suppression mode

Possible Causes

OSPFv3 neighbor relationship flapping suppression started on the local interface, or the interface exited from the suppression.

Procedure

  1. Check whether frequent interface flapping occurs.

    • If frequent interface flapping occurs, this trap message is informational only and no action is required.
    • If no frequent interface flapping occurs, go to Step 2.

  2. Run the reset ospfv3 process-id suppress-flapping peer [ interface-type interface-number ] [ notify-peer ] command to force the interface to exit from OSPFv3 neighbor relationship flapping suppression.
  3. End.

OSPFV3/6/NFSMCHG

Message

OSPFV3/6/NFSMCHG:Neighbor state changed from [neighbor-old] to [neighbor-new]. (Event=[STRING], RouterId=[STRING], Interface=[STRING], ProcessId=[ULONG])

Description

The neighbor state changed from state 1 to state 2.

Parameters

Parameter Name Parameter Meaning
[neighbor-old] Indicates the old status of the neighbor.
[neighbor-new] Indicates the new status of the neighbor.
Event Indicates the neighbor event.
RouterId Indicates the ID of the neighbor router.
Interface Indicates the interface to the neighbor.
ProcessId Indicates the process ID.

Possible Causes

The status of the neighbor changed.

Procedure

  1. This log message is informational only, and no action is required.

OSPFV3/4/PROC_UP_FAIL_MEMSHT

Message

OSPFV3/4/PROC_UP_FAIL_MEMSHT: OSPFv3 [ULONG] process cannot come up due to memory shortage.

Description

The process failed to go Up because of insufficient memory.

Parameters

Parameter Name Parameter Meaning
[ULONG]

Indicates the process ID.

Possible Causes

The process failed to go Up because of insufficient memory.

Procedure

  1. This log message is informational only, and no action is required.

OSPFV3/6/PROCUNDRGR

Message

OSPFV3/6/PROCUNDRGR: OSPFv3 [ULONG] process is undergoing reset.

Description

The process was undergoing reset.

Parameters

Parameter Name Parameter Meaning
[ULONG] Indicates the process ID.

Possible Causes

When the GR hold timer expired, the process is undergoing reset.

Procedure

  1. This log message is informational only, and no action is required.

OSPFV3/4/RMMEMRESTR

Message

OSPFV3/4/RMMEMRESTR:Received memory restore notification from RM.

Description

Received the memory restoring notification from the route management.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

The memory was restored.

Procedure

  1. Run the display diagnostic-information command to save the displayed result and contact technical support personnel.

OSPFV3/4/RMMEMSHORT

Message

OSPFV3/4/RMMEMSHORT:Received memory shortage notification from RM.

Description

Received the memory shortage notification from the route management.

Parameters

Parameter Name Parameter Meaning
None None

Possible Causes

The memory was insufficient.

Procedure

  1. Run the display diagnostic-information command to save the displayed result and contact technical support personnel.
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065665

Views: 5436

Downloads: 15

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