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.
|
IfAddrType |
Indicates the inetAddressType of an interface
address. The value can be:
|
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
- Check whether this PIM interface is expected to become
the DR.
If so, go to Step 8.
If not, go to Step 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.
- 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.
- 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.
- 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.
- 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.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.