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

E9000 Server V100R001 HMM Alarm Handling 19

This document describes E9000 server alarms in terms of the meaning, impact on the system, possible causes, and solutions.
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).
PIM

PIM

PIMPRO_1.3.6.1.2.1.157.0.1 pimNeighborLoss

Description

The PIM neighbor is lost. (NbrIntIndex=[NbrIntIndex], NbrAddrType=[NbrAddrType], NbrAddr=[NbrAddr], NbrUpTime=[NbrUpTime])

The PIM neighbor was lost.

Attributes

Attribute

Description

Trap OID

1.3.6.1.2.1.157.0.1

Trap severity

Warning

Parameters

Parameter

Description

NbrIntIndex

Index of the neighboring interface

NbrAddrType

Address type of the neighboring interface:

  • 0: MIB_ADDRESSTYPE_UNKNOWN
  • 1: MIB_ADDRESSTYPE_IPV4
  • 3: MIB_ADDRESSTYPE_IPV4Z
  • 16: MIB_ADDRESSTYPE_DSN
  • 17: MIB_ADDRESSTYPE_MAX

NbrAddr

Address of the neighboring interface

NbrUpTime

Lifetime of the neighbor relationship

Impact on the System

The PIM neighbor relationship is interrupted or fails to be established, the route is unreachable, and service data forwarding is interrupted.

Possible Causes

Cause 1: The link was faulty.

Cause 2: The neighboring device failed.

Cause 3: The protocol configuration of the neighboring device was incorrect.

Procedure
  • Cause 1: The link was faulty.
    1. Run the ping command to check whether the link between PIM neighbors works properly.
      • If the link works properly, go to Step 3.
      • If the link works improperly, go to Step 2.
    2. Collect the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.
    3. End.
  • Cause 2: The neighboring device failed.
    1. Run the display ip routing-table command to check whether the unicast route between PIM neighbors is reachable.
      • If the unicast route is reachable, go to Step 2.
      • If the unicast route is unreachable, rectify the route fault to clear the alarm.
    2. End.
  • Cause 3: The protocol configuration of the neighboring device was incorrect.
    1. Run the display this command in the view of the corresponding PIM neighboring interface to check whether the interface is enabled with PIM-SM.
      • If PIM-SM is enabled on the neighboring interface, PIM neighbor loss is caused by the change of the IP address of the neighboring interface. If the PIM neighbor relationship cannot be re-established after a certain period, go to Step 2.
      • If PIM-SM is not enabled on the neighboring interface, run the pim sm command in the interface view to enable PIM-SM to clear the alarm.
    2. Collect the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.

PIMPRO_1.3.6.1.2.1.157.0.2 pimInvalidRegister

Description

PIM receives an invalid register message. (GroupMappingOrigin=[GroupMappingOrigin], GroupMappingAddressType=[GroupMappingAddressType], GrpAddr=[GrpAddr], GrpPfxLen=[GrpPfxLen], GroupMappingRPAddressType=[GroupMappingRPAddressType], RPAddr=[RPAddr], GroupMappingPimMode=[GroupMappingPimMode], InvRegAddressType=[InvRegAddressType], InvRegOriginAddr=[InvRegOriginAddr], InvRegGrpAddr=[InvRegGrpAddr], InvRegRpAddr=[InvRegRpAddr])

PIM received invalid Register messages.

Attributes

Attribute

Description

Trap OID

1.3.6.1.2.1.157.0.2

Trap severity

Warning

Parameters

Parameter

Description

GroupMappingOrigin

RP type

GroupMappingAddressType

Group address type

GrpAddr

Group address of the Registered messages

GrpPfxLen

Mask length of the multicast group address

GroupMappingRPAddressType

RP address type

RPAddr

Address of the RP serving the multicast group

GroupMappingPimMode

Current PIM mode

InvRegAddressType

Address type of the invalid Register messages

InvRegOriginAddr

Source address of the invalid Register messages

InvRegGrpAddr

Group address of the invalid Register messages

InvRegRpAddr

Destination address of the invalid Register messages

Impact on the System

After the RP receives an invalid Register message, the source that sends the message fails to register with the RP.

Possible Causes

Cause 1: The interface that received the Register message was not the RP that serves the group address in the Register message.

Cause 2: The group address in the received Register message was within the SSM range specified on the local device.

Procedure
  • Cause 1: The interface that received the Register message was not the RP that serves the group address in the Register message.
    1. Run the display pim rp-info command to check whether the local device functions as the RP to which the group address in the Register message corresponds.
      • If the local device functions as the RP to which the group address in the Register message corresponds, go to Step 2.
      • If the local device does not function as the RP to which the group address in the Register message corresponds, ensure that the configured RP to which the group corresponds on the source DR is the same as that on the local device.
    2. Collect the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.
  • Cause 2: The group address in the received Register message was within the SSM range specified on the local device.
    1. Run the display current-configuration command to check whether the group address in the received Register message is within the SSM group address range on the local device.
      • If the group address in the received Register message is within the SSM group address range on the local device, go to Step 2.
      • If the group address in the received Register message is not within the SSM group address range on the local device, configure a same SSM group address range for the group address in the received Register message and the local device.
    2. Collect the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.

PIMPRO_1.3.6.1.2.1.157.0.3 pimInvalidJoinPrune

Description

PIM receives an Invalid Join/Prune message. (GroupMappingOrigin=[GroupMappingOrigin], GroupMappingAddrType=[GroupMappingAddrType], GrpAddr=[GrpAddr], GrpPfxLen=[GrpPfxLen], GroupMappingRPAddrType=[GroupMappingRPAddrType], RPAddr=[RPAddr], GroupMappingPimMode=[GroupMappingPimMode], InvJPAddrType=[InvJPAddrType], InvJPOriginAddr=[InvJPOriginAddr], InvJPGrpAddr=[InvJPGrpAddr], InvJPRpAddr=[InvJPRpAddr], NbrIfIndex=[NbrIfIndex], NbrAddrType=[NbrAddrType], NbrAddr=[NbrAddr], NbrUpTime=[NbrUpTime])

PIM received invalid Join/Prune messages.

Attributes

Attribute

Description

Trap OID

1.3.6.1.2.1.157.0.3

Trap severity

Warning

Parameters

Parameter

Description

GroupMappingOrigin

RP type

GroupMappingAddrType

Group address type

GrpAddr

Group address in the Join/Prune message

GrpPfxLen

Mask length of the multicast group address

GroupMappingRPAddrType

RP address type

RPAddr

RP address

GroupMappingPimMode

Current PIM mode

InvJPAddrType

Address type of the invalid Join/Prune messages

InvJPOriginAddr

Source address of the invalid Join/Prune messages

InvJPGrpAddr

Group address of the invalid Join/Prune messages

InvJPRpAddr

RP address of the invalid Join/Prune messages

NbrIfIndex

Index of the neighboring interface

NbrAddrType

Address type of the neighboring interface

NbrAddr

Address of the neighboring interface

NbrUpTime

Lifetime of the neighbor relationship

Impact on the System

After the RP receives an invalid Join or Prune message, information about multicast members fails to reach the RP.

Possible Causes

Cause 1: The RP address carried in the received Join or Prune message was different from that specified on the device.

Cause 2: A Join or Prune message of (*.G) or (S, G, RPT) type was received but its group address was in the SSM range specified on the device.

Procedure
  • Cause 1: The RP address carried in the received Join or Prune message was different from that specified on the device.
    1. Run the display pim rp-info command to check whether the RP configurations of the device that sends the Join/Prune message are the same with that of the local device.
      • If the RP configurations of the device that sends the Join/Prune message are the same with that of the local device, go to Step 2.
      • If the RP configurations of the device that sends the Join/Prune message are different from that of the local device, configure a same RP for the devices.
    2. Collect the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.
  • Cause 2: A Join or Prune message of (*.G) or (S, G, RPT) type was received but its group address was in the SSM range specified on the device.
    1. Run the display current-configuration command to check whether the SSM group address range on the device that sends the Join/Prune message is the same as that on the local device.
      • If the SSM group address range on the device that sends the Join/Prune message is the same as that on the local device, go to Step 2.
      • If the SSM group address range on the device that sends the Join/Prune message is different from that on the local device, configure a same SSM group address range for the devices.
    2. Collect the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.

PIMPRO_1.3.6.1.2.1.157.0.4 pimRPMappingChange

Description

The RP changes. (GroupMappingOrigin=[GroupMappingOrigin], GroupMappingAddressType=[GroupMappingAddressType], szGrpAddr=[szGrpAddr], GrpPfxLen=[GrpPfxLen], GroupMappingRPAddressType=[GroupMappingRPAddressType], RPAddr=[RPAddr], GroupMappingPimMode=[GroupMappingPimMode], Precedence=[Precedence])

The RP changed.

Attributes

Attribute

Description

Trap OID

1.3.6.1.2.1.157.0.4

Trap severity

Warning

Parameters

Parameter

Description

GroupMappingOrigin

RP type

GroupMappingAddressType

Group address type

szGrpAddr

Group address

GrpPfxLen

Mask length of the group address

GroupMappingRPAddressType

RP address type

RPAddr

New RP address

GroupMappingPimMode

Current PIM mode

Precedence

Precedence of different types of RPs

Impact on the System

The change of the RP causes the source and multicast members fail to communicate. This will adversely affect multicast services.

Possible Causes

Cause1: A static RP was reconfigured and the preferred parameter was configured to preferentially select the static RP.

Cause2: A C-RP with a higher priority than the existing ones existed.

Procedure
  • Cause1: A static RP was reconfigured and the preferred parameter was configured to preferentially select the static RP.
    1. Check whether RP information is changed manually.
      • If so, go to Step 5.
      • If not, go to Step 2.
    2. Run the static-rp rp-address preferred command in the PIM view to configure the original RP as a static RP on every . The static RP is preferred. Then, go to Step 3.
    3. Run the display pim rp-info group-address command to check whether RP information meets requirements.
      • If so, go to Step 5.
      • If not, go to Step 4.
    4. Collect the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.
    5. End.
  • Cause2: A C-RP with a higher priority than the existing ones existed.
    1. Check whether RP information is changed manually.
      • If so, go to Step 5.
      • If not, go to Step 2.
    2. Run the c-rp priority priority or c-rp interface-type interface-number priority priority command in the PIM view to reduce the priority value of the C-RP, that is, increase the priority of the C-RP on the that is expected to serve as the RP. Then, go to Step 3.
    3. Run the display pim rp-info group-address command to check whether RP information meets requirements.
      • If so, go to Step 5.
      • If not, go to Step 4.
    4. Collect the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.
    5. End.

PIMPRO_1.3.6.1.2.1.157.0.5 pimInterfaceElection

Description

The interface is elected as a DR. (IfIndex=[IfIndex], IfIPverion=[IfIPverion], IfAddrType=[IfAddrType], Addr=[Addr])

The interface is elected as a DR.

Attributes

Attribute

Description

Trap OID

1.3.6.1.2.1.157.0.5

Trap severity

Warning

Parameters

Parameter

Description

IfIndex

Interface index

IfIPverion

IP version of the interface

IfAddrType

Interface address type

Addr

Interface address

Impact on the System

If the source-side DR changes, the RP receives an incorrect Register message; if the member-side DR changes, the RP receives an incorrect Join message.

Possible Causes

Cause1: The PIM interface received a new Hello packet and had a higher DR priority or IP address than other interfaces on the shared network segment.

Cause2: After a PIM interface went Up, the PIM interface did not receive Hello packets after the interval between Hello packets expired.

Procedure
  1. Check whether this PIM interface is expected to become the DR.
  • If so, go to Step 8.
  • If not, go to Step 2.
  1. Run the display pim interface interface-type interface-number command to check whether the DR address is the same as the IP address of this interface. If the interface is the current DR, the interface address in the display is marked with "local".

    • If so, go to Step 3.
    • If not, go to Step 8.

  2. Run the display pim interface interface-type interface-number command to check whether interfaces on the shared network segment all support the Hello packets to carry the DR priority field.

    • If so, go to Step 4.
    • If not, go to Step 5.

  3. Run the display pim neighbor neighbor-address command to check whether the DR priority of every neighboring interface is smaller than the DR priority of this PIM interface.

    • If so, run the pim hello-option dr-priority priority command in the interface view to reduce the DR priority of this interface . Then, go to Step 4.
    • If not, run the ip address ip-address { mask | mask-length } command in the interface view to configure a smaller IP address for this interface. Then, go to Step 6.

  4. Run the ip address ip-address { mask | mask-length } command in the interface view to configure a smaller IP address for this interface. Then, go to Step 6.
  5. Run the display pim interface interface-type interface-number command to check whether the DR changes.

    • If so, go to Step 8.
    • If not, go to Step 7.

  6. Collect configuration information, trap messages, and log messages, and then contact Huawei technical personnel.
  7. End.

PIMPRO_1.3.6.1.4.1.2011.5.25.149.4.0.1 hwPimNeighborLoss

Description

PIM neighbor loss. (NbrIntIndex=[NbrIntIndex], NbrAddrType=[NbrAddrType], NbrAddr=[NbrAddr], NbrUpTime=[NbrUpTime], NbrIntName=[NbrIntName], InstanceID=[InstanceID], InstanceName=[InstanceName], NeighborLossReason=[NeighborLossReason])

After receiving a Hello message from a neighbor, a device recorded information about this neighbor and started a timer for this neighbor. If the device received no Hello packet before the timer expired, the device considered the neighbor lost, and thereby reported a trap message.

Attributes

Attribute

Description

Trap OID

1.3.6.1.4.1.2011.5.25.149.4.0.1

Trap severity

Major

Match trap

PIMPRO_1.3.6.1.4.1.2011.5.25.149.4.0.6 hwPimNeighborAdd

Parameters

Parameter

Description

NbrIntIndex

Index of the interface where the neighbor relationship is established.

NbrAddrType

Address family of a PIM neighbor

NbrAddr

Neighbor address

NbrUpTime

Time since the neighbor relationship is established

NbrIntName

Name of the interface where the neighbor relationship is established

InstanceID

Instance index

InstanceName

Instance name

NeighborLossReason

Reason why the neighbor relationship is unavailable

Impact on the System

The PIM neighbor relationship is interrupted or fails to be established, the route is unreachable, and data forwarding services are interrupted.

Possible Causes

Cause 1: Neighbor timer expired.

Cause 2: Interface is down.

Cause 3: Neighbor is deleted.

Cause 4: Receive hello cancel message.

Cause 5: BFD session is down.

Procedure
  • Cause 1: Neighbor timer expired.
    1. Run the ping command to check whether the link between PIM neighbors is up.
      • If the link is up, go to Step 3.
      • If the link is down, go to Step 2.
    2. Run the display ip routing-table command to check whether the unicast route from the local device to the neighbor works properly.
      • If the route works properly, go to Step 3.
      • If the route works improperly, you can clear the alarm by rectifying the routing fault.
    3. Run the display this command in the view of the corresponding PIM neighboring interface to check whether the interface is enabled with PIM-SM.
      • If PIM-SM is enabled on the neighboring interface, the IP address of the neighboring interface changes. If the PIM neighbor relationship is not re-established after a certain period, go to Step 4.
      • If PIM-SM is not enabled on the neighboring interface, run the pim sm command in the interface view to enable PIM-SM to clear the alarm.
    4. Collect log messages and contact Huawei technical support personnel.
  • Cause 2: Interface is down.
    1. Run the display interface brief command to check the physical layer status and the protocol layer status of the interface. First, check whether the protocol layer status of the interface is up.
      • If the protocol layer status of the interface is up, go to Step 2.
      • If the protocol layer status is down, run the ip address command to configure an IP address for the interface.
    2. Check whether the physical layer status of the interface is up.
      • If the physical layer status of the interface is up, go to Step 3.
      • If the physical layer status of the interface is down, the interface is Down. Then, locate the fault on the interface.
      • If the physical layer status is of the interface *down, the shutdown command is run on the interface. In this case, run the undo shutdown command on the interface to clear the alarm.
    3. Collect log messages and contact Huawei technical support personnel.
  • Cause 3: Neighbor is deleted.
    1. Run the display this command in the view of the corresponding interface to check whether the pim neighbor-policy command is run on the interface.
      • If the pim neighbor-policy command is run on the interface, go to Step 2.
      • If the pim neighbor-policy command is not run on the interface, go to Step 3.
    2. Run the display acl command to check whether the ACL configuration is proper.
      • If the ACL configuration is proper, go to Step 3.
      • If the ACL configuration is improper, reconfigure ACL rules.
    3. Collect log messages and contact Huawei technical support personnel.
  • Cause 4: Receive hello cancel message.
    1. Run the display this command in the view of the interface connecting the neighbor to the local device to check whether the interface is enabled with PIM-SM.
      • If the interface is enabled PIM-SM, go to Step 2.
      • If the interface is not enabled with PIM-SM, run the pim sm command to enable PIM-SM on it.
    2. Run the display interface brief command on the neighboring device to check the status of the interface directly connected to the local device. Check whether the protocol layer status of the interface is up.
      • If the protocol layer status of the interface is up, go to Step 3.
      • If the protocol layer status is down, run the ip address command to configure an IP address for the interface.
      • If the interface status is *down, run the undo shutdown command.
    3. Collect log messages and contact Huawei technical support personnel.
  • Cause 5: BFD session is down.
    1. Run the ping command to check whether the link between PIM neighbors is up.
      • If the link is up, go to Step 3.
      • If the link is down, go to Step 2.
    2. Run the display interface brief command on the device to check the status of the interface directly connected to the local device. Check whether the protocol layer status of the interface is up.
      • If the protocol layer status of the interface is up, go to Step 3.
      • If the protocol layer status is down, run the ip address command to configure an IP address for the interface.
      • If the interface status is *down, run the undo shutdown command.
    3. Run the display ip routing-table command to check whether the unicast route from the local device to the neighbor works properly.
      • If the route works properly, go to Step 3.
      • If the route works improperly, you can clear the alarm by rectifying the routing fault.
    4. Collect log messages and contact Huawei technical support personnel.

PIMPRO_1.3.6.1.4.1.2011.5.25.149.4.0.6 hwPimNeighborAdd

Description

PIM neighbor add. (NbrIntIndex=[NbrIntIndex], NbrAddrType=[NbrAddrType], NbrAddr=[NbrAddr], NbrExpiryTime=[NbrExpiryTime], InstanceID=[InstanceID], InstanceName=[InstanceName])

A new PIM neighbor is created.

Attributes

Attribute

Description

Trap OID

1.3.6.1.4.1.2011.5.25.149.4.0.6

Trap severity

Cleared

Match trap

PIMPRO_1.3.6.1.4.1.2011.5.25.149.4.0.1 hwPimNeighborLoss

Parameters

Parameter

Description

NbrIntIndex

Index of the interface on the newly created neighbor.

NbrAddrType

Address type of the interface on the newly created neighbor, which is one of the followings:

  • 0: MIB_ADDRESSTYPE_UNKNOWN
  • 1: MIB_ADDRESSTYPE_IPV4
  • 3: MIB_ADDRESSTYPE_IPV4Z
  • 16: MIB_ADDRESSTYPE_DSN
  • 17: MIB_ADDRESSTYPE_MAX

NbrAddr

Address of the interface on the newly created neighbor

NbrExpiryTime

The time out period of the PIM neighbor relationship

InstanceID

Indicates the ID of the instance to which the neighbor interface belongs.

InstanceName

Indicates the name of the instance to which the neighbor interface belongs.

Impact on the System

Services will not be affected.

Possible Causes

Cause 1: PIM is enabled on the interface of the neighboring device.

Cause 2: The PIM interface receives Hello packets.

Procedure
  • This alarm message is informational only, and no action is required.
Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 210906

Downloads: 1591

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