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

Alarm Handling

S9300, S9300E, and S9300X V200R013C00

This document provides the explanations, causes, and recommended actions of alarms 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).
PIM-STD

PIM-STD

PIM-STD_1.3.6.1.2.1.157.0.1 PimNeighborLoss

Description

PIM-STD/2/PUBLIC_NBRLOSS:OID [oid] PIM neighbor loss. (NbrIntIndex=[integer], NbrAddrType=[integer], NbrAddr=[binary], NbrUpTime=[timetick])

A PIM neighbor relationship was lost.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.157.0.1

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

NbrIntIndex

Index of a neighbor

NbrAddrType

Indicates the inetAddressType of neighbor address. The value can be:
  • 1: IPv4 address

  • 2: IPv6 address

NbrAddr

Address of a neighbor

NbrUpTime

Time elapsed since a neighbor relationship was established

Impact on the System

The PIM neighbor relationship will be interrupted and multicast services will be affected.

Possible Causes

Cause 1:

The timer of a PIM neighbor expired.

Cause 2:

The switch received a Hello packet with the Holdtime field of 0.

Procedure

  1. Run the display pim interface interface-type interface-number command on a PIM neighbor. Check whether PIM is enabled on the interface connecting the PIM neighbor to the local switch.

    • If PIM is enabled on the interface, go to step 3.

    • If PIM is disabled on the interface, go to step 2.

  2. Run the pim dm or pim sm command to enable PIM on the interface connecting the PIM neighbor to the local switch. Run the display pim neighbor neighbor-address command on the PIM neighbor to view the PIM neighbor relationship status.

    • If the PIM neighbor relationship is established, go to step 6.

    • If the PIM neighbor relationship is not established, go to step 3.

  3. Run the display ip routing-table ip-address command on the PIM neighbor to view the route to the local switch.

    • If the route is reachable, go to step 5.

    • If the route is unreachable, go to step 4.

  4. Rectify the route fault to clear the trap. After the route becomes reachable, run the display pim neighbor neighbor-address command on the PIM neighbor to view the PIM neighbor relationship status.

    • If the PIM neighbor relationship is established, go to step 6.

    • If the PIM neighbor relationship is not established, go to step 5.

  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.

Related Information

None

PIM-STD_1.3.6.1.2.1.157.0.2 pimInvalidRegister

Description

PIM-STD/3/PUBLIC_INVREG:OID [oid] Invalid Register message. (GroupMappingOrigin=[integer], GroupMappingAddressType=[integer], GrpAddr=[binary], GrpPfxLen=[gauge], GroupMappingRPAddressType=[integer], RPAddr=[binary], GroupMappingPimMode=[integer], InvRegAddressType=[integer], InvRegOriginAddr=[binary], InvRegGrpAddr=[binary], InvRegRpAddr=[binary])

An invalid Register message was received.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.157.0.2

Minor

processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

GroupMappingOrigin

Indicates the type of a group-RP mapping.
  • 1: mapping between an RP and a link-local or unreachable group address

  • 2: mapping between a local static RP and a group

  • 3: mapping between an RP and a group address in the local SSM address range

  • 4: mapping learned through the PIM BSR mechanism

  • 5: mapping learned through the auto-RP mechanism

  • 6: mapping learned through the embedded-RP mechanism

  • 7: mapping learned through other mechanisms

NOTE:
Currently, the device supports only the 2, 4, 5, 6 types of group-RP mappings.

GroupMappingAddressType

Indicates the inetAddressType of mapping group address. The value can be:
  • 1: IPv4 address

  • 2: IPv6 address

GrpAddr

Group address

GrpPfxLen

Mask length of the multicast group address

GroupMappingRPAddressType

Indicates the inetAddressType of an RP address. The value can be:
  • 1: IPv4 address

  • 2: IPv6 address

RPAddr

RP address

GroupMappingPimMode

Indicates the group mapping mode.
  • 1: mapping without groups

  • 2: PIM-SSM

  • 3: PIM-ASM

  • 4: BIDR-PIM

  • 5: PIM-DM

  • 6: others

NOTE:
Currently, the device supports only the 2, 3, and 5 modes.

InvRegAddressType

Indicates the inetAddressType of the invalid Register message address. The value can be:
  • 1: IPv4 address

  • 2: IPv6 address

InvRegOriginAddr

Source address in the Register packet

InvRegGrpAddr

Group address in the Register packet

InvRegRpAddr

RP address in the Register packet

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

An (S, G) entry was not created for a received Register message, the group address in the Register message was in the ASM address range, and the router's RP address was different from that contained in the Register message.

Procedure

  1. Run the display pim rp-info group-address command to view information about the RP that serves the group address on the source-side DR and local switch. Check whether the RP information on the source-side DR is the same as that on the local switch.

    • If the two devices have the same RP information, go to step 3.

    • If the two devices have different RP information, go to step 2.

  2. Run the display pim rp-info group-address command to check the RP configured on the source-side DR and the local switch. Proceed with either of the following operations based on a static or dynamic RP:

    • If a static RP is configured, run the static-rp rp-address preferred command in the PIM view to configure the same and correct static RP on the source-side DR and local switch. The preferred parameter is configured to preferentially select the static RP. Then go to step 1.

    • If a dynamic RP is configured, rectify the fault in the dynamic RP. After the fault is rectified, go to step 1.

  3. Run the display this command in PIM view on the source-side DR and the local switch. Check whether the ssm-policy { basic-acl-number | acl-name acl-name } command has been run.

    • If the command has been run, go to step 4.

    • If the command has not been run, go to step 6.

  4. Run the display acl { name acl-name | acl-number } command on the local switch. Check whether the SSM range on the source-side DR is the same as that on the local switch.

    • If the SSM ranges are the same, go to step 6.

    • If the SSM ranges are different, go to step 5.

  5. Run the ssm-policy { basic-acl-number | acl-name acl-name } command on the local switch to specify an ACL the same as that on the source-side DR. After that, the local switch and the source-side DR have the same SSM range. Check whether the trap is displayed.

    • If the trap is displayed, go to step 6.

    • If the trap is cleared, go to step 7.

  6. Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

None

PIM-STD_1.3.6.1.2.1.157.0.3 PimInvalidJoinPrune

Description

PIM-STD/3/PUBLIC_INVJP:OID [oid] Invalid Join/Prune message. (GroupMappingOrigin=[integer], GroupMappingAddrType=[integer], GrpAddr=[binary], GrpPfxLen=[gauge], GroupMappingRPAddrType=[integer], RPAddr=[binary], NbrIfIndex=[integer], NbrAddrType=[integer], NbrAddr=[binary], GroupMappingPimMode=[integer], InvJPAddrType=[integer], InvJPOriginAddr=[binary], InvJPGrpAddr=[binary], InvJPRpAddr=[binary], NbrUpTime=[timetick])

An invalid Join or Prune message was received.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.157.0.3

Minor

processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

GroupMappingOrigin

Indicates the type of a group-RP mapping.
  • 1: mapping between an RP and a link-local or unreachable group address

  • 2: mapping between a local static RP and a group

  • 3: mapping between an RP and a group address in the local SSM address range

  • 4: mapping learned through the PIM BSR mechanism

  • 5: mapping learned through the auto-RP mechanism

  • 6: mapping learned through the embedded-RP mechanism

  • 7: mapping learned through other mechanisms

NOTE:
Currently, the device supports only the 2, 4, 5, 6 types of group-RP mappings.

GroupMappingAddrType

Indicates the inetAddressType of mapping group address. The value can be:
  • 1: IPv4 address

  • 2: IPv6 address

GrpAddr

Group address

GrpPfxLen

Mask length of the multicast group address

GroupMappingRPAddrType

Indicates the inetAddressType of an RP address. The value can be:
  • 1: IPv4 address

  • 2: IPv6 address

RPAddr

RP address

NbrIfIndex

Index of a neighbor interface

NbrAddrType

Indicates the inetAddressType of a neighbor address. The value can be:
  • 1: IPv4 address

  • 2: IPv6 address

NbrAddr

Address of a neighbor

GroupMappingPimMode

Indicates the group mapping mode.
  • 1: mapping without groups

  • 2: PIM-SSM

  • 3: PIM-ASM

  • 4: BIDR-PIM

  • 5: PIM-DM

  • 6: others

NOTE:
Currently, the device supports only the 2, 3, and 5 modes.

InvJPAddrType

Indicates the inetAddressType of the invalid message address. The value can be:
  • 1: IPv4 address

  • 2: IPv6 address

InvJPOriginAddr

Source address in an invalid packet

InvJPGrpAddr

Group address in an invalid packet

InvJPRpAddr

RP address in an invalid packet

NbrUpTime

Time elapsed since a neighbor relationship was established

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 message was different from that specified on the switch.

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 switch.

Procedure

  1. Run the display pim rp-info command to view information about the RP that serves the group address on the local switch and the device that sends the Join or Prune message. Check whether the RP information on both devices is the same.

    • If the two devices have the same RP information, go to step 3.

    • If the two devices have different RP information, go to step 2.

  2. Run the display pim rp-info command on the local switch and the device that sends the Join or Prune message. Proceed with either of the following operations based on a static or dynamic RP:

    • If a static RP is used, run the static-rp(IPv4) rp-address command in the PIM view to configure the same and correct static RP on the local switch and the device that sends the Join or Prune message. Then go to step 1.

    • If a dynamic RP is used, rectify the fault in the dynamic RP. After the fault is rectified, go to step 1.

  3. Run the display this command in PIM view on the local switch and the device that sends the Join or Prune message. Check whether the ssm-policy { basic-acl-number | acl-name acl-name } command has been run.

    • If the command has been run, go to step 4.

    • If the command has not been run, go to step 6.

  4. Run the display acl { name acl-name | acl-number } command on the local switch and the device that sends the Join or Prune message. Check whether the SSM ranges on the two devices are the same.

    • If the SSM ranges are the same, go to step 6.

    • If the SSM ranges are different, go to step 5.

  5. Run the ssm-policy { basic-acl-number | acl-name acl-name } command to specify an ACL on the local end the same as that configured on the peer end that sends Join/Prune packets. This allows the sending end and the local end to have the same SSM range. Then check whether the trap is cleared.

    • If the trap is displayed, go to step 6.

    • If the trap is cleared, go to step 7.

  6. Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

None

PIM-STD_1.3.6.1.2.1.157.0.4 PimRPMappingChange

Description

PIM-STD/3/PUBLIC_RPCHG:OID [oid] RP changed. (GroupMappingOrigin=[integer], GroupMappingAddressType=[integer], szGrpAddr=[binary], GrpPfxLen=[gauge], GroupMappingRPAddressType=[integer], RPAddr=[binary], GroupMappingPimMode=[integer], Precedence=[gauge])

Information about an RP that serves a specific multicast group on a network was changed. The trap is not displayed when an RP is added or deleted.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.157.0.4

Minor

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

GroupMappingOrigin

Indicates the type of a group-RP mapping.
  • 1: mapping between an RP and a link-local or unreachable group address

  • 2: mapping between a local static RP and a group

  • 3: mapping between an RP and a group address in the local SSM address range

  • 4: mapping learned through the PIM BSR mechanism

  • 5: mapping learned through the auto-RP mechanism

  • 6: mapping learned through the embedded-RP mechanism

  • 7: mapping learned through other mechanisms

NOTE:
Currently, the device supports only the 2, 4, 5, 6 types of group-RP mappings.

GroupMappingAddressType

Indicates the inetAddressType of mapping group address. The value can be:
  • 1: IPv4 address

  • 2: IPv6 address

szGrpAddr

Group address

GrpPfxLen

Mask length of the multicast group address

GroupMappingRPAddressType

Indicates the inetAddressType of an RP address. The value can be:
  • 1: IPv4 address

  • 2: IPv6 address

RPAddr

RP address

GroupMappingPimMode

Indicates the group mapping mode.
  • 1: mapping without groups

  • 2: PIM-SSM

  • 3: PIM-ASM

  • 4: BIDR-PIM

  • 5: PIM-DM

  • 6: others

NOTE:
Currently, the device supports only the 2, 3, and 5 modes.

Precedence

Indicates the preference of the mapping mode.
  • 0: embedded-RP
  • 1: auto-RP
  • 2: PIM BSR
  • 3: static RP
  • 4: others

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

Cause 1:

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

Cause 2:

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

Procedure

  1. Check whether RP information can be changed based on the network plan.

    • If RP information can be changed, go to step 5.

    • If the RP information cannot be changed, go to step 2.

  2. Run the display pim rp-info group-address command to check whether the RP on the network is a static RP or a dynamic RP.

    • If a static RP is configured, run the static-rp rp-address preferred command in the PIM view to configure a static PR and allow the static PR to be preferentially selected. Then go to step 3.

    • If a dynamic RP is configured, run the c-rp priority priority or c-rp interface-type interface-number priority priority command in the PIM view on the switch that is expected to be a C-RP to set a smaller priority value to increase the priority. Then go to step 3.

  3. Run the display pim rp-info group-address command to check whether RP information is identical with the networking plan.

    • If RP information is identical with the networking plan, go to step 5.

    • If RP information is not identical with the networking plan, go to step 4.

  4. Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.

Related Information

None

PIM-STD_1.3.6.1.2.1.157.0.5 PimInterfaceElection

Description

PIM-STD/1/PUBLIC_INTELECTDR:OID [oid] Interface is elected to be DR. (IfIndex=[integer], IfIPverion=[integer], IfAddrType=[integer], Addr=[binary])

The switch was elected as a DR on a shared network segment.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.157.0.5

Critical

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

IfIndex

Index of an interface

IfIPverion

Indicates the version of the interface address.
  • 1: IPv4

  • 2: IPv6

IfAddrType

Indicates the inetAddressType of an interface address. The value can be:
  • 1: IPv4 address

  • 2: IPv6 address

Addr

IP address of an interface

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

Cause 1:

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.

NOTE:

The start of a PIM interface triggers a DR change. This is a normal situation, and therefore a DR change during the interval for the first Hello packet will not trigger this trap.

Cause 2:

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 the interface can be a DR based on the network plan.

    • If the interface can be a DR, go to step 8.

    • If the interface cannot be a DR, go to step 2.

  2. Run the display pim interface interface-type interface-number command to view the IP address of the PIM interface. Check whether the IP address of the interface is followed by a word "local."

    • If there is the word "local", the interface is the DR. Then go to step 3.

    • If there is not the word "local", go to step 8.

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

    • If they support the function, obtain the interface DR priority and go to step 4.

    • If they do not support the function, go to step 5.

  4. Run the display pim neighbor neighbor-address command to view the neighbor priorities. Check whether all neighbors' DR priorities are lower than the interface DR priority.

    • If all neighbors have lower priorities than the PIM interface, run the pim hello-option dr-priority priority command to set a lower priority for the interface than the priorities of neighbors. Then go to step 6.

    • If all neighbors have higher priorities than the PIM interface, run the ip address ip-address { mask | mask-length } command to configure a lower IP address for the interface than IP addresses of the neighbors. Then go to step 6.

  5. If all neighbors' priorities are higher than the PIM interface, run the ip address ip-address { mask | mask-length } command to configure a lower IP address for the interface than its neighbors. Then go to step 6.
  6. Run the display pim interface interface-type interface-number command to the DR information. Check whether the DR information is changed.

    • If the DR information is changed, go to step 8.

    • If the DR information is unchanged, go to step 7.

  7. Collect alarm information and configuration information, and then contact technical support personnel.
  8. End.

Related Information

None

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 5168

Downloads: 6

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