BRASAAA_1.3.6.1.4.1.2011.5.2.2.2.0.6 hwRbpStateChange
Trap Buffer Description
RBP State changed. (RBP=[RBP], OldState=[OldState], NewState=[NewState], ChangeReason=[ChangeReason])
The RBP state changed.
In VS mode, this trap is supported only by the admin VS.
Trap Attributes
| Trap Attribute | Description |
|---|---|
Alarm or Event |
Event |
Trap Severity |
Warning |
Mnemonic Code |
RBP_STATE_CHANGE |
Trap OID |
1.3.6.1.4.1.2011.5.2.2.2.0.6 |
MIB |
HUAWEI-AAA-MIB |
Alarm ID |
This is an event trap and does not involve alarm ID. |
Alarm Name |
This is an event trap and does not involve alarm name. |
Alarm Type |
This is an event trap and does not involve alarm type. |
Raise or Clear |
This is an event trap and does not involve alarm generation or clearance. |
Match trap |
- |
Trap Buffer Parameters
| Parameter | Description |
|---|---|
RBP |
Indicates the RBP name. |
OldState |
Indicates the previous state of the RBP. |
NewState |
Indicates the new state of the RBP. |
ChangeReason |
Indicates the reason why the RBP state changed. |
VB Parameters
| VB OID | VB Name | VB Index |
|---|---|---|
1.3.6.1.4.1.2011.5.2.2.1.8 |
hwRbpChangeName |
- |
1.3.6.1.4.1.2011.5.2.2.1.9 |
hwRbpOldState |
- |
1.3.6.1.4.1.2011.5.2.2.1.10 |
hwRbpNewState |
- |
1.3.6.1.4.1.2011.5.2.2.1.11 |
hwRbpChangeReason |
- |
Possible Causes
Cause 1: Invalid Statechange Reason
Cause 2: Priority calculation is performed
Cause 3: The timer expired
Cause 4: The interface where the VRRP group resides went Up
Cause 5: The interface where the VRRP group resides went Down
Cause 6: The VRRP group was deleted (vrrp group delete)
Cause 7: The VRRP group was created (vrrp group create)
Cause 8: The mVRRP backup group drove the status change of the service VRRP group (admin-vrrp drove)
Cause 9: The device is the IP address owner
Cause 10: The IP address of the interface on which the VRRP group resides changed
Cause 11: The link BFD session associated with the VRRP group went Up
Cause 12: The link BFD session associated with the VRRP group went Down
Cause 13: The peer BFD session went Down
Cause 14: The number of link BFD sessions in the Down state associated with the VRRP group reached the threshold (link bfd down-number change)
Cause 15: The link BFD session associated with the VRRP group was deleted (link bfd delete)
Cause 16: The peer BFD session was deleted
Cause 17: The status of the link BFD session associated with the VRRP group was unknown
Cause 18: The mVRRP backup group ignored the interface Down event (ignore if down)
Cause 19: The VRRP group was added to the VRRP LBRG
Cause 20: The VRRP group was deleted from the VRRP LBRG
Cause 21: VRRP became an mVRRP backup group (vrrp become admin)
Cause 22: The VRRP backup group was no longer an mVRRP backup group (vrrp not admin)
Cause 23: The EFM session associated with the VRRP group went Up
Cause 24: The EFM session associated with the VRRP group went Down
Cause 25: The configuration of the EFM session associated with the VRRP group was deleted
Cause 26: The CFM fault associated with the VRRP group was rectified
Cause 27: The CFM session associated with the VRRP group went Down
Cause 28: The interface on which the VRRP backup group is configured went offline
Cause 29: The interface Down event ignored by the mVRRP backup group was deleted (becoming normal)
Cause 30: The number of Down EFM sessions associated with the VRRP group reached the threshold (efm down-number change)
Cause 31: The common VRRP backup group was unbound from the mVRRP backup group (vrrp exit admin)
Cause 32: The dynamic BFD session associated with the VRRP group went Down (dyn bfd down)
Cause 33: Unknown cause
Procedure
1. Run the display remote-backup-profile command to check whether the RBP status has changed.
2. Run the display device command to check whether the interface board bound to the RBP is faulty.
3. Run the display interface brief command to check whether the interface bound to the RBP is Down.
4. Run the display vrrp command to check the VRRP priority in the PriorityRun field. If the priority is changed, check whether the change is caused by manual configuration. If not, check whether the network-side uplink of the master device is faulty.
5. Check whether the device is faulty.