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

Enterprise
Worldwide
Huawei Global - English
Search
Support Documentation
Alarm Handling
S1700, S2720, S5700, and S6700 V200R019C10

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

PIM

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.1 hwPimNeighborLoss

Description

PIM/2/NBRLOSS:OID [oid] PIM neighbor loss. (NbrIntIndex=[integer], NbrAddrType=[integer], NbrAddr=[binary], NbrUpTime=[timetick], NbrIntName=[string], InstanceID=[integer], InstanceName=[string], NeighborLossReason=[integer])

The PIM neighbor was lost.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.0.1

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

NbrIntIndex

Indicates the index of a neighbor.

NbrAddrType
Indicates the inetAddressType of neighbor address. The value can be:

  • 1: IPv4 address

  • 2: IPv6 address

NbrAddr

Indicates the address of a neighbor.

NbrUpTime

Indicates the period during which the neighbor relationship is in the Up state.

NbrIntName

Indicates the name of the neighbor interface.

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.

NeighborLossReason
Indicates a possible cause for PIM neighbor loss.

  • 1: The neighbor relationship expires.

  • 7: Hello messages with the holdtime 0 are received.

  • 8: The BFD session goes Down.

  • 9: A user manually tears down the PIM neighbor relationship.

Impact on the System

The PIM neighbor is disconnected, which has impact on multicast services.

Possible Causes

1. The timer of the PIM neighbor expired.

2. The switch received a Hello message with the Holdtime value being 0.

Procedure

  1. Run the display pim interface interface-type interface-number command on the neighboring switch to check whether PIM is enabled on the interface that connects the local switch.

    • If so, go to Step 3.

    • If not, go to Step 2.

  2. Run the pim dm or pim sm command on the interface that connects the local switch to enable PIM. Run the display pim neighbor neighbor-address command on the neighboring switch to check whether the PIM neighbor of the local switch is established.

    • If so, go to Step 6.

    • If not, go to Step 3.

  3. Run the display ip routing-table ip-address command on the neighboring switch to check whether the route to the local switch exists.

    • If so, go to Step 5.

    • If not, go to Step 4.

  4. Confirm that no unicast route is faulty. Run the display pim neighbor neighbor-address command on the neighboring switch to check whether the PIM neighborship is established between the local switch and its neighbor.

    • If so, go to Step 6.

    • If not, go to Step 5.

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

Related Information

None

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.2 hwPimInvalidRegister

Description

PIM/3/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], InstanceID=[integer], InstanceName=[string])

A switch received an invalid Register message.

Attribute

Alarm ID Alarm Severity Alarm Type

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

Indicates the group address.

GrpPfxLen

Indicates the mask length of a multicast address.

GroupMappingRPAddressType
Indicates the inetAddressType of an RP address. The value can be:

  • 1: IPv4 address

  • 2: IPv6 address

RPAddr

Indicates the 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

Indicates the source address carried in the invalid Register message.

InvRegGrpAddr

Indicates the multicast address carried in the invalid Register message.

InvRegRpAddr

Indicates the RP address carried in the invalid Register message.

InstanceID

Indicates the instance ID.

InstanceName

Indicates the instance name.

Impact on the System

After the RP receives an invalid Register message, the source fails to register with the RP. This has impact on multicast services.

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 RP address on the switch was different from that contained in the Register message.

Procedure

  1. Run the display pim rp-info group-address command on the DR on the source side and the local switch to check whether the interface that receives the Register message is the RP to which the group address in the Register message corresponds.

    • If so, go to Step 3.

    • If not, go to Step 2.

  2. Run the display pim rp-info group-address command to check the RP configured on the DR on the source side and the local switch is a static RP or a dynamic RP.

    • If it is a static RP, run the static-rp rp-address preferred command in the PIM view on the DR on the source side and the local switch to configure correct and identical static RP. The static RP is preferred. Then, go to Step 1.

    • If it is a dynamic RP, confirm whether no dynamic RP is faulty. Then, go to Step 1.

  3. Run the display this command in the PIM view on the DR on the source side and the local switch to check whether the ssm-policy basic-acl-number command is configured.

    • If so, go to Step 4.

    • If not, go to Step 6.

  4. Run the display acl acl-number command on the switch that is configured with the ssm-policy basic-acl-number command and check whether the SSM ranges of the DR on the source side and the local switch are the same.

    • If so, go to Step 6.

    • If not, go to Step 5.

  5. Configure the ACL specified in the ssm-policy basic-acl-number command on the local switch so that the SSM ranges of the DR on the source side and the local switch are the same. Then, check whether the trap persists.

    • If so, go to Step 6.

    • If not, go to Step 7.

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

Related Information

None

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.3 hwPimInvalidJoinPrune

Description

PIM/3/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], NbrIfName=[string], InstanceID=[integer], InstanceName=[string])

A switch received an invalid Join/Prune message.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.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, 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

Indicates the group address.

GrpPfxLen

Indicates the mask length of a multicast address.

GroupMappingRPAddrType
Indicates the inetAddressType of an RP address. The value can be:

  • 1: IPv4 address

  • 2: IPv6 address

RPAddr

Indicates the RP address.

NbrIfIndex

Indicates the index of a neighboring interface.

NbrAddrType
Indicates the inetAddressType of a neighbor address. The value can be:

  • 1: IPv4 address

  • 2: IPv6 address

NbrAddr

Indicates the 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

Indicate the source address carried in the invalid message.

InvJPGrpAddr

Indicate the multicast address carried in the invalid message.

InvJPRpAddr

Indicate the RP address carried in the invalid message.

NbrUpTime

Indicates the period during which the neighbor relationship is in the Up state.

NbrIfName

Indicates the name of the neighbor interface.

InstanceID

Indicates the instance ID.

InstanceName

Indicates the instance name.

Impact on the System

After the RP receives an invalid Join or Prune message, information about multicast members fails to reach the RP. This has impact on multicast services.

Possible Causes

1. The RP address carried in the received Join message is different from the address of the RP that serves the group on the switch.

2. The Join/Prune message of the (*.G) or (S,G,RPT) type was received but its group address was in the SSM range.

Procedure

  1. Run the display pim rp-info command to check whether the RP information on the switch that sends the Join or Prune message is the same as RP information on the local switch.

    • If so, go to Step 3.

    • If not, go to Step 2.

  2. Run the display pim rp-info command to check the RP configured on the switch that sends the Join or Prune message and the local switch is a static RP or a dynamic RP.

    • If it is a static RP, run the static-rp rp-address command in the PIM view on the end of sending the Join/Prune message and the local switch to configure correct and identical static RP. Then, go to Step 1.

    • If it is a dynamic RP, confirm that no dynamic RP is faulty. Then, go to Step 1.

  3. Run the display this command in the PIM view on the switch that sends the Join or Prune message and the local switch to check whether the ssm-policy basic-acl-number command is configured.

    • If so, go to Step 4.

    • If not, go to Step 6.

  4. Run the display acl acl-number command on the switch that is configured with the ssm-policy basic-acl-number command to check whether the SSM ranges of the end of sending the Join/Prune message and the local switch are the same.

    • If so, go to Step 6.

    • If not, go to Step 5.

  5. Configure the ACL specified in the ssm-policy basic-acl-number command on the local switch and the end of sending the Join/Prune message so that the SSM ranges of the end of sending the Join/Prune message and the local switch are the same. Then, check whether the trap persists.

    • If so, go to Step 6.

    • If not, go to Step 7.

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

Related Information

None

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.4 hwPimRpMappingChange

Description

PIM/3/RPCHG:OID [oid] RP changed. (GroupMappingOrigin=[integer], GroupMappingAddressType=[integer], szGrpAddr=[binary], GrpPfxLen=[gauge], GroupMappingRPAddressType=[integer], RPAddr=[binary], GroupMappingPimMode=[integer], Precedence=[gauge], InstanceID=[integer], InstanceName=[string])

For a group, there is only one RP in the entire network. The trap was generated when the entries of a group existed on the switch and RP information about the group changed.

Attribute

Alarm ID Alarm Severity Alarm Type

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

Indicates the address of a multicast group.

GrpPfxLen

Indicates the mask length of a multicast address.

GroupMappingRPAddressType
Indicates the inetAddressType of an RP address. The value can be:

  • 1: IPv4 address

  • 2: IPv6 address

RPAddr

Indicates an 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

InstanceID

Indicates the instance ID.

InstanceName

Indicates the instance name.

Impact on the System

The change of the RP causes the source and multicast members to fail to communicate. This has impact on multicast services.

Possible Causes

1. A static RP was re-configured in the network. The command used to configure static RP contains preferred, the static RP is preferred.

2. A C-RP with higher priority emerged in the network.

Procedure

  1. Check whether RP information is expected to change.

    • If so, go to Step 5.

    • If not, go to Step 2.

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

    • If it is a static RP, run the static-rp rp-address preferred command in the PIM view to configure the original RP as a static RP on every switch. The static RP is preferred. Then, go to Step 3.

    • If it is a dynamic RP, 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 switch 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 alarm information and configuration information, and then contact technical support personnel.
  5. End.

Related Information

None

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.5 hwPimInterfaceElection

Description

PIM/1/INTELECTDR:OID [oid] Interface is elected to be DR. (IfIndex=[integer], IfIPverion=[integer], IfAddrType=[integer], Addr=[binary], IfName=[string], InstanceID=[integer], InstanceName=[string])

This trap is generated when a switch was elected as the DR used to forward data in the shared network segment.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.0.5

Critical

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

IfIndex

Indicates the 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

Indicates the address of an interface.

IfName

Indicates the name of the interface.

InstanceID

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

InstanceName

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

Impact on the System

The change of the DR on the source side causes the RP to receive an incorrect Register message; the change of the DR on the multicast member side causes the RP to receive an incorrect Join message. This has impact on multicast services.

Possible Causes

1. The PIM interface received a new Hello message and the DR priority or IP address of the PIM interface was greater than that of another interface in the shared network segment.

When a PIM interface is just started, the DR changes. This is a normal situation. Thus, this trap is not generated when the DR change occurs during the Holdtime of the first Hello packet.

2. The PIM interface changes to the Up state but it does not receive any Hello message from other interfaces after the first Hello interval expires.

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.

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

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

  4. 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 6.

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

  5. 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.
  6. 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.

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

Related Information

None

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.6 hwPimNeighborAdd

Description

PIM/2/NEWNBR:OID [oid] PIM neighbor add. (NbrIntIndex=[integer], NbrAddrType=[integer], NbrAddr=[binary], NbrExpiryTime=[timetick], InstanceID=[integer], InstanceName=[string])

A new PIM neighbor is created.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.0.6

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

NbrIntIndex

Index of the interface on the newly created neighbor.

NbrAddrType
Indicates the inetAddressType of the interface address on the newly created neighbor. The value can be:

  • 1: IPv4 address

  • 2: IPv6 address

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

1:

PIM is enabled on the interface of the neighboring switch.

2:

The PIM interface receives Hello packets.

Procedure

  • This alarm message is informational only, and no action is required.

Related Information

None.

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.9 hwPimMrtLimit

Description

PIM/1/MRTLIMIT:OID [oid] PIM entries cannot be created because the upper limit is crossed. (GrpAddrType=[integer], SrcAddr=[binary], GrpAddr=[binary], InstanceID=[integer], InstanceName=[string])

The number of PIM entries exceeds the upper limit defined in the License file. (To check the upper limit defined in the License file, run the display multicast paf-license command. The paf value in PAF_LCS_ROUT_MCAST_PIM_MAX_WC_ENTRY_NUM and PAF_LCS_ROUT_MCAST_PIM_MAX_SG_ENTRY_NUM in the command output indicates the upper limit defined in the License file.)

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.0.9

Critical

processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

GrpAddrType
Indicates the inetAddressType of the multicast group address. The value can be:

  • 1: IPv4 address

  • 2: IPv6 address

SrcAddr

Indicates the source address of the entry.

GrpAddr

Indicates the group address of the entry.

InstanceID

Indicates the ID of the instance to which the entry belongs.

InstanceName

Indicates the name of the instance to which the entry belongs.

Impact on the System

After the number of PIM entries reaches the upper limit defined in the License file, no more PIM entries can be added.

Possible Causes

Adding PIM entries fails because the number of PIM entries reaches the upper limit defined in the License file.

Procedure

  1. Run the display pim routing-table command or the display pim ipv6 routing-table command to check whether the number of existent PIM entries reaches the upper limit defined in the License file.

    • If so, go to Step 2.

    • If not, go to Step 3.

  2. The number of multicast entries reaches the upper limit and no more entries can be added. Then, you are recommended to reduce the deployed multicast services or replace the device with a higher-performance device to solve the problem, go to Step 4.
  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.12 hwPimMrtLimitClear

Description

PIM/1/hwpimmrtlimitclear:OID [oid] PIM entries can be created because the number of PIM entries falls below the upper limit. (GrpAddrType=[integer], SrcAddr=[binary], GrpAddr=[binary], InstanceID=[integer], InstanceName=[string])

The number of Protocol Independent Multicast (PIM) entries fell below the upper threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.0.12

Critical

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

GrpAddrType
Indicates the inetAddressType of the multicast group address. The value can be:

  • 1: IPv4 address

  • 2: IPv6 address

SrcAddr

Source address

GrpAddr

Group address

InstanceID

ID of the instance to which a PIM entry belongs

InstanceName

Name of the instance

Impact on the System

None.

Possible Causes

PIM entries were deleted and the number of existing PIM entries fell below the upper threshold defined in a PAF file.

Procedure

  1. This alarm is informational only, and no action is required.

Related Information

PIM1.3.6.1.4.1.2011.5.25.149.4.0.9 hwPimMrtLimit

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.13 hwPimStarGThresholdExceed

Description

PIM/3/hwPimStarGThresholdExceed:OID [oid] PIM (*, G) entries of all instances count reached the upper threshold. (hwPimNotificationAddressType=[integer], hwPimStarGCurrentCount=[integer], hwPimStarGThreshold=[integer]%, hwPimStarGTotalCount=[integer])

The proportion of global PIM (*, G) entries created to the maximum global PIM (*, G) entries allowed reached the upper alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.0.13

Minor

communicationsAlarm

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwPimNotificationAddressType
Group address type:

  • 1: IPv4 address

  • 2: IPv6 address

hwPimStarGCurrentCount

Number of global PIM (*, G) entries created

hwPimStarGThreshold

Alarm threshold for global PIM (*, G) entries

hwPimStarGTotalCount

Maximum number of global PIM (*, G) entries allowed

Impact on the System

If the number of (*, G) PIM entries in the system reaches the upper limit and this alarm is reported, the device cannot create new PIM entries, causing failures to forward some multicast traffic.

Possible Causes

The proportion of global PIM (*, G) entries created to the maximum global PIM (*, G) entries allowed reached the upper alarm threshold.

Procedure

  1. Check whether the upper alarm threshold is too low in the configuration file.

    • If the threshold is too low, go to Step 2.

    • If the threshold is not low, go to Step 3.

  2. Run the pim star-group-number threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value command in the multicast MIB view to set the upper alarm threshold to a larger value.
  3. Confirm whether network expansion is required. If network expansion is required, contact technical support personnel.
  4. End.

Related Information

None

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.14 hwPimStarGThresholdExceedClear

Description

PIM/3/hwPimStarGThresholdExceedClear:OID [oid] PIM (*, G) entries of all instances count fell below the lower threshold. (hwPimNotificationAddressType=[integer], hwPimStarGCurrentCount=[integer], hwPimStarGThreshold=[integer]%, hwPimStarGTotalCount=[integer])

The proportion of global PIM (*, G) entries created to the maximum global PIM (*, G) entries allowed fell below the lower alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.0.14

Minor

communicationsAlarm

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwPimNotificationAddressType
Group address type:

  • 1: IPv4 address

  • 2: IPv6 address

hwPimStarGCurrentCount

Number of global PIM (*, G) entries created

hwPimStarGThreshold

Alarm threshold for global PIM (*, G) entries

hwPimStarGTotalCount

Maximum number of global PIM (*, G) entries allowed

Impact on the System

Services will not be affected.

Possible Causes

The proportion of global PIM (*, G) entries created to the maximum global PIM (*, G) entries allowed fell below the lower alarm threshold.

Procedure

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

Related Information

None

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.15 hwPimStarGExceed

Description

PIM/3/hwPimStarGExceed:OID [oid] PIM (*, G) entries of all instances cannot be created because the limit is reached. (hwPimNotificationAddressType=[integer], hwPimNotificationSrcAddr=[binary], hwPimNotificationGrpAddr=[binary], hwPimStarGTotalCount=[integer], hwPimInstanceName=[string])

The number of global PIM (*, G) entries created exceeded the maximum number of global PIM (*, G) entries allowed.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.0.15

Minor

communicationsAlarm

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwPimNotificationAddressType
Group address type:

  • 1: IPv4 address

  • 2: IPv6 address

hwPimNotificationSrcAddr

Source address

hwPimNotificationGrpAddr

Group address

hwPimStarGTotalCount

Maximum number of global PIM (*, G) entries allowed

hwPimInstanceName

Name of the VPN instance that caused the global PIM (*, G) entries to exceed the maximum number of global PIM (*, G) entries allowed

Impact on the System

No more PIM (*, G) entries can be created.

Possible Causes

The number of global PIM (*, G) entries created exceeded the maximum number of global PIM (*, G) entries allowed.

Procedure

  1. Confirm whether network expansion is required. If network expansion is required, contact technical support personnel.
  2. If the global PIM (*, G) entries of an address family indicated in the alarm information are not needed, delete them to reduce the number of global PIM (*, G) entries.
  3. End.

Related Information

None

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.16 hwPimStarGExceedClear

Description

PIM/3/hwPimStarGExceedClear:OID [oid] PIM (*, G) entries can be created because the number of PIM (*, G) entries of all instances fell below the limit. (hwPimNotificationAddressType=[integer])

The number of global PIM (*, G) entries created fell below the maximum number of global PIM (*, G) entries allowed and new PIM (*, G) entries could be created again.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.0.16

Minor

communicationsAlarm

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwPimNotificationAddressType
Group address type:

  • 1: IPv4 address

  • 2: IPv6 address

Impact on the System

Services will not be affected.

Possible Causes

The number of global PIM (*, G) entries created fell below the maximum number of global PIM (*, G) entries allowed.

Procedure

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

Related Information

None

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.17 hwPimSGThresholdExceed

Description

PIM/3/hwPimSGThresholdExceed:OID [oid] PIM (S, G) entries of all instances count reached the upper threshold. (hwPimNotificationAddressType=[integer], hwPimSGCurrentCount=[integer], hwPimSGThreshold=[integer]%, hwPimSGTotalCount=[integer])

The proportion of global PIM (S, G) entries created to the maximum global PIM (S, G) entries allowed reached the upper alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.0.17

Minor

communicationsAlarm

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwPimNotificationAddressType
Group address type:

  • 1: IPv4 address

  • 2: IPv6 address

hwPimSGCurrentCount

Number of global PIM (S, G) entries created

hwPimSGThreshold

Alarm threshold for global PIM (S, G) entries

hwPimSGTotalCount

Maximum number of global PIM (S, G) entries allowed

Impact on the System

If the number of (S, G) PIM entries in the system reaches the upper limit and this alarm is reported, the device cannot create new PIM entries, causing failures to forward some multicast traffic.

Possible Causes

The proportion of global PIM (S, G) entries created to the maximum global PIM (S, G) entries allowed reached the upper alarm threshold.

Procedure

  1. Check whether the upper alarm threshold is too low in the configuration file.

    • If the threshold is too low, go to Step 2.

    • If the threshold is not low, go to Step 3.

  2. Run the pim source-group-number threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value command in the multicast MIB view to set the upper alarm threshold to a larger value.
  3. Confirm whether network expansion is required. If network expansion is required, contact technical support personnel.
  4. End.

Related Information

None

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.18 hwPimSGThresholdExceedClear

Description

PIM/3/hwPimSGThresholdExceedClear:OID [oid] PIM (S, G) entries of all instances count fell below the lower threshold. (hwPimNotificationAddressType=[integer], hwPimSGCurrentCount=[integer], hwPimSGThreshold=[integer]%, hwPimSGTotalCount=[integer])

The proportion of global PIM (S, G) entries created to the maximum global PIM (S, G) entries allowed fell below the lower alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.0.18

Minor

communicationsAlarm

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwPimNotificationAddressType
Group address type:

  • 1: IPv4 address

  • 2: IPv6 address

hwPimSGCurrentCount

Number of global PIM (S, G) entries created

hwPimSGThreshold

Alarm threshold for global PIM (S, G) entries

hwPimSGTotalCount

Maximum number of global PIM (S, G) entries allowed

Impact on the System

Services will not be affected.

Possible Causes

The proportion of global PIM (S, G) entries created to the maximum global PIM (S, G) entries allowed fell below the lower alarm threshold.

Procedure

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

Related Information

None

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.19 hwPimSGExceed

Description

PIM/3/hwPimSGExceed:OID [oid] PIM (S, G) entries of all instances cannot be created because the limit is reached. (hwPimNotificationAddressType=[integer], hwPimNotificationSrcAddr=[binary], hwPimNotificationGrpAddr=[binary], hwPimSGTotalCount=[integer], hwPimInstanceName=[string])

The number of global PIM (S, G) entries created exceeded the maximum number of global PIM (S, G) entries allowed.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.0.19

Minor

communicationsAlarm

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwPimNotificationAddressType
Group address type:

  • 1: IPv4 address

  • 2: IPv6 address

hwPimNotificationSrcAddr

Source address

hwPimNotificationGrpAddr

Group address

hwPimSGTotalCount

Maximum number of global PIM (S, G) entries allowed

hwPimInstanceName

Name of the VPN instance that caused the global PIM (S, G) entries to exceed the maximum number of global PIM (S, G) entries allowed

Impact on the System

No more PIM (S, G) entries can be created.

Possible Causes

The number of global PIM (S, G) entries created exceeded the maximum number of global PIM (S, G) entries allowed.

Procedure

  1. Confirm whether network expansion is required. If network expansion is required, contact technical support personnel.
  2. If the global PIM (S, G) entries of an address family indicated in the alarm information are not needed, delete them to reduce the number of global PIM (S, G) entries.
  3. End.

Related Information

None

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.20 hwPimSGExceedClear

Description

PIM/3/hwPimSGExceedClear:OID [oid] PIM (S, G) entries can be created because the number of PIM (S, G) entries of all instances fell below the limit. (hwPimNotificationAddressType=[integer])

The number of global PIM (S, G) entries fell below the maximum number of global PIM (S, G) entries allowed and new PIM (S, G) entries could be created again.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.0.20

Minor

communicationsAlarm

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwPimNotificationAddressType
Group address type:

  • 1: IPv4 address

  • 2: IPv6 address

Impact on the System

Services will not be affected.

Possible Causes

The number of global PIM (S, G) entries created fell below the maximum number of global PIM (S, G) entries allowed.

Procedure

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

Related Information

None

Translation
日本語 简体中文
Download
Updated: 2022-05-25

Document ID: EDOC1100127008

Views: 75568

Downloads: 320

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Digital Signature File

Digital Signature Authentication Mode
Share
Previous Next

Copyright © 2023 Huawei Technologies Co., Ltd. All rights reserved.

You are going to visit :