RSVP
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.1 hwRsvpTeHelloLost
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.2 hwRsvpTeHelloLostRecovery
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.3 hwRsvpTeAuthFail
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.4 hwRsvpTeAuthSuccess
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.5 hwRsvpTeIfNbrThresholdExceed
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.6 hwRsvpTeIfNbrThresholdExceedClear
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.7 hwRsvpTeIfNbrTotalCountExceed
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.8 hwRsvpTeIfNbrTotalCountExceedClear
RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.1 hwRsvpTeHelloLost
Description
RSVP/2/HWRSVPHELLOLOST:OID [oid] The RSVP Hello neighbor is lost. (IpAddress=[ipaddr])
The RSVP neighbor relationship was interrupted.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.148.1.12.2.1 | Major | communicationsAlarm(2) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
IpAddress |
IP address of a neighbor |
Impact on the System
If GR has been enabled, services will not be affected. If GR has not been enabled, the LSP goes Down or a master/slave LSP switchover is performed using FRR.
Possible Causes
The RSVP neighbor or the link over which the RSVP neighbor relationship is established became faulty.
Procedure
- Check whether the physical link or the RSVP neighbor is
faulty.
If so, repair the physical link or restart the RSVP neighbor.
If not, go to step 2.
- Run the display ip routing-table command to check whether there is a route to the RSVP neighbor.
If so, go to step 3.
If not, configure an IGP to advertise routes.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.2 hwRsvpTeHelloLostRecovery
Description
RSVP/2/HWRSVPHELLOLOSTRECOVERY: OID [oid] The RSVP Hello neighbor is resumed. (IpAddress=[ipaddr])
The device is restored from the status of interruption of RSVP neighbor relationship.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.148.1.12.2.2 | Major |
communicationsAlarm(2) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
IpAddress |
IP address of a neighbor |
RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.3 hwRsvpTeAuthFail
Description
RSVP/2/HWRSVPAUTHFAIL: OID [oid] The RSVP neighbor authentication is incorrect. (IpAddress=[ipaddr])
RSVP authentication failed.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.148.1.12.2.3 | Major | communicationsAlarm(2) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
IpAddress |
IP address of a neighbor |
Impact on the System
Not all packets sent from the RSVP neighbor are processed. As a result, RSVP services cannot run properly.
Procedure
- Run the display this command in the views of directly connected
interfaces on both ends to check whether the authentication key information
displayed in the mpls rsvp-te authentication plain fields are
the same.
If so, go to Step 2.
If not, run the mpls rsvp-te authentication command to modify the configuration to keep authentication key information the same on both ends.
If the authentication key information is not displayed, the authentication key is in encrypted text. Modify the configuration to keep the authentication key information the same on both ends.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.4 hwRsvpTeAuthSuccess
Description
RSVP/2/HWRSVPAUTHSUCCESS: OID [oid] The RSVP neighbor authentication is normal. (IpAddress=[ipaddr])
RSVP authentication succeeded.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.148.1.12.2.4 | Major |
communicationsAlarm(2) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
IpAddress |
IP address of a neighbor |
RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.5 hwRsvpTeIfNbrThresholdExceed
Description
RSVP/3/RSVPIFNBRTHRESHOLDEXCEED: OID [oid] The number of RSVP neighbors exceeded the threshold. (hwRsvpTeIfName=[octet], hwRsvpTeIfNbrCurrentCount=[integer], hwRsvpTeIfNbrThreshold=[integer], hwRsvpTeIfNbrTotalCount=[integer])
The proportion of configured RSVP neighbors to all supported ones reached the upper alarm threshold.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.148.1.12.2.5 |
Minor |
qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
hwRsvpTeIfName |
Name of an RSVP interface |
hwRsvpTeIfNbrCurrentCount |
Number of existing RSVP neighbors |
hwRsvpTeIfNbrThreshold |
Threshold (percent) of RSVP neighbors that device supports |
hwRsvpTeIfNbrTotalCount |
Maximum number of RSVP neighbors that a device supports |
Impact on the System
If new RSVP neighbors are created after the proportion of configured RSVP neighbors to all supported ones on a specified interface has reached the upper alarm threshold, services may be affected.
Possible Causes
The proportion of configured RSVP neighbors to all supported ones on a specified interface reached the upper threshold.
Procedure
- Check the hwRsvpTeIfName field and obtain information about the interface on which the alarm is generated.
- Check whether hwRsvpTeIfNbrThreshold is set in a specified
range. (Setting hwRsvpTeIfNbrThreshold to 80% of hwRsvpTeIfNbrTotalCount
is recommended. A smaller value leads to useless threshold-crossing
alarms to be generated.)
- If the value is within the specified range, go to Step 4.
- If the value is out of the specified range, go to Step 3.
- Run the mpls rsvp-peer-number
threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value command to set the alarm threshold.
Then check whether the alarm is cleared.
- If the alarm is cleared, go to Step 6.
- If the alarm persists, go to Step 4.
- Run the undo mpls rsvp-te command in the interface view
to delete unwanted RSVP interface configurations or delete unwanted
RSVP interface configurations on the peer interface to reduce the
number of RSVP neighbors. Then check whether the alarm is cleared.
- If the alarm is cleared, go to Step 6.
- If the alarm persists, go to Step 5.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.6 hwRsvpTeIfNbrThresholdExceedClear
Description
RSVP/3/RSVPIFNBRTHRESHOLDEXCEEDCLEAR: OID [oid] The number of RSVP neighbors fell below the threshold. (hwRsvpTeIfName=[octet])
The proportion of configured RSVP neighbors to all supported ones fell below the lower alarm threshold.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.148.1.12.2.6 |
Minor |
qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
hwRsvpTeIfName |
Name of an RSVP interface |
RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.7 hwRsvpTeIfNbrTotalCountExceed
Description
RSVP/2/RSVPIFNBRTOTALCOUNTEXCEED: OID [oid] The number of RSVP neighbors reached the maximum number. (hwRsvpTeIfName=[octet], hwRsvpTeNbrTotalCount=[integer])
The number of configured RSVP neighbors reached the maximum number of supported RSVP neighbors.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.148.1.12.2.7 |
Major |
qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
hwRsvpTeIfName |
Name of an RSVP interface |
hwRsvpTeNbrTotalCount |
Maximum number of RSVP neighbors that a device supports |
Impact on the System
If new RSVP neighbors are created after the number of existing RSVP neighbors on a specified interface has reached the upper threshold, services may be affected.
Possible Causes
The number of configured RSVP neighbors on a device reached the maximum number of supported RSVP neighbors.
Procedure
- Check the hwRsvpTeIfName field and obtain information about the interface on which the alarm is generated.
- Run the undo mpls rsvp-te command in the interface view to delete unwanted RSVP interface configurations or delete unwanted RSVP interface configurations on the peer interface to reduce the number of RSVP neighbors. Then check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.8 hwRsvpTeIfNbrTotalCountExceedClear
Description
RSVP/2/RSVPIFNBRTOTALCOUNTEXCEEDCLEAR: OID [oid] The number of RSVP neighbors fell below the maximum number. (hwRsvpTeIfName=[octet])
The number of all RSVP neighbors fell below 95% of the maximum number of supported RSVP neighbors.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.148.1.12.2.8 |
Major |
qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
hwRsvpTeIfName |
Name of an RSVP interface |
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.1 hwRsvpTeHelloLost
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.2 hwRsvpTeHelloLostRecovery
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.3 hwRsvpTeAuthFail
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.4 hwRsvpTeAuthSuccess
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.5 hwRsvpTeIfNbrThresholdExceed
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.6 hwRsvpTeIfNbrThresholdExceedClear
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.7 hwRsvpTeIfNbrTotalCountExceed
- RSVP_1.3.6.1.4.1.2011.5.25.148.1.12.2.8 hwRsvpTeIfNbrTotalCountExceedClear