Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 08-HH3C-RIB-MIB | 396.08 KB |
Contents
hh3cRibPublicIPv4PrefixTHLimit
hh3cRibPublicIPv6PrefixTHLimit
hh3cRibVrfIPv4PrefixExceedClear
hh3cRibVrfIPv4PrefixTHExceedClr
hh3cRibVrfIPv6PrefixExceedClear
hh3cRibVrfIPv6PrefixTHExceedClr
hh3cRibPUBIPv4PrefixExceedClear
hh3cRibPUBIPv4PrefixTHExceedClr
hh3cRibPUBIPv6PrefixExceedClear
hh3cRibPUBIPv6PrefixTHExceedClr
HH3C-RIB-MIB
About this MIB
Use the HH3C-RIB-MIB to obtain device RIB information and collect alarm information.
MIB file name
hh3c-rib.mib
Root object
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cRib (219)
Scalar objects
hh3cRibVrfName
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibVrfName (1.3.6.1.4.1.25506.2.219.1.2) |
accessible-for-notify |
OCTET STRING |
OCTET STRING (0..31) |
VPN instance name. |
As per the MIB. |
hh3cRibVrfIndex
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibVrfIndex (1.3.6.1.4.1.25506.2.219.1.3) |
accessible-for-notify |
Gauge32 |
INTEGER(0..65535) |
VPN instance index. |
As per the MIB. |
hh3cRibVrfIPv4PrefixNumber
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibVrfIPv4PrefixNumber (1.3.6.1.4.1.25506.2.219.1.6) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Number of IPv4 route prefixes in the VPN instance. |
As per the MIB. |
hh3cRibVrfIPv4PrefixLimit
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibVrfIPv4PrefixLimit (1.3.6.1.4.1.25506.2.219.1.7) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Maximum number of IPv4 route prefixes in the VPN instance. |
As per the MIB. |
hh3cRibVrfIPv4PrefixTHLimit
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibVrfIPv4PrefixTHLimit (1.3.6.1.4.1.25506.2.219.1.8) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Alarm threshold for the number of IPv4 route prefixes in the VPN instance. |
As per the MIB. |
hh3cRibVrfIPv6PrefixNumber
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibVrfIPv6PrefixNumber (1.3.6.1.4.1.25506.2.219.1.9) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Number of IPv6 route prefixes in the VPN instance. |
As per the MIB. |
hh3cRibVrfIPv6PrefixLimit
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibVrfIPv6PrefixLimit (1.3.6.1.4.1.25506.2.219.1.10) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Maximum number of IPv6 route prefixes in the VPN instance. |
As per the MIB. |
hh3cRibVrfIPv6PrefixTHLimit
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibVrfIPv6PrefixTHLimit (1.3.6.1.4.1.25506.2.219.1.11) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Alarm threshold for the number of IPv6 route prefixes in the VPN instance. |
As per the MIB. |
hh3cRibPublicIPv4PrefixNumber
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibPublicIPv4PrefixNumber (1.3.6.1.4.1.25506.2.219.3.1) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Number of IPv4 route prefixes in the public network. |
As per the MIB. |
hh3cRibPublicIPv4PrefixLimit
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibPublicIPv4PrefixLimit (1.3.6.1.4.1.25506.2.219.3.2) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Maximum number of IPv4 route prefixes in the public network. |
As per the MIB. |
hh3cRibPublicIPv4PrefixTHLimit
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibPublicIPv4PrefixTHLimit (1.3.6.1.4.1.25506.2.219.3.3) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Alarm threshold for the number of IPv4 route prefixes in the public network. |
As per the MIB. |
hh3cRibPublicIPv6PrefixNumber
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibPublicIPv6PrefixNumber (1.3.6.1.4.1.25506.2.219.3.4) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Number of IPv6 route prefixes in the public network. |
As per the MIB. |
hh3cRibPublicIPv6PrefixLimit
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibPublicIPv6PrefixLimit (1.3.6.1.4.1.25506.2.219.3.5) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Maximum number of IPv6 route prefixes in the public network. |
As per the MIB. |
hh3cRibPublicIPv6PrefixTHLimit
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibPublicIPv6PrefixTHLimit (1.3.6.1.4.1.25506.2.219.3.6) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Alarm threshold for the number of IPv6 route prefixes in the public network. |
As per the MIB. |
hh3cRibIPv4PrefixNumber
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibIPv4PrefixNumber (1.3.6.1.4.1.25506.2.219.5.1) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Number of IPv4 route prefixes on the device. |
As per the MIB. |
hh3cRibIPv4PrefixLimit
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibIPv4PrefixLimit (1.3.6.1.4.1.25506.2.219.5.2) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Maximum number of IPv4 route prefixes on the device. |
As per the MIB. |
hh3cRibIPv4PrefixTHLimit
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibIPv4PrefixTHLimit (1.3.6.1.4.1.25506.2.219.5.3) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Alarm threshold for the number of IPv4 route prefixes on the device. |
As per the MIB. |
hh3cRibIPv6PrefixNumber
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibIPv6PrefixNumber (1.3.6.1.4.1.25506.2.219.5.4) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Number of IPv6 route prefixes on the device. |
As per the MIB. |
hh3cRibIPv6PrefixLimit
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibIPv6PrefixLimit (1.3.6.1.4.1.25506.2.219.5.5) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Maximum number of IPv6 route prefixes on the device. |
As per the MIB. |
hh3cRibIPv6PrefixTHLimit
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cRibIPv6PrefixTHLimit (1.3.6.1.4.1.25506.2.219.5.6) |
accessible-for-notify |
Gauge32 |
INTEGER(0..4294967295) |
Alarm threshold for the number of IPv6 route prefixes on the device. |
As per the MIB. |
Notifications
hh3cRibVrfIPv4PrefixExceed
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.2.0.3 |
The number of IPv4 route prefixes in the VPN instance exceeds the maximum value. |
Error |
Warning |
1.3.6.1.4.1.25506.2.219.2.0.4 (hh3cRibVrfIPv4PrefixExceedClear) |
ON |
Notification triggers
This notification is generated when the number of IPv4 route prefixes in the VPN instance exceeds the maximum value.
System impact
When the number of IPv4 route prefixes in the VPN instance exceeds the maximum value, you cannot add new route prefixes, which might result in route loss and traffic interruption.
Status control
ON
CLI: Use the snmp-agent trap enable rib vrf-prefix-exceed command.
OFF
CLI: Use the undo snmp-agent trap enable rib vrf-prefix-exceed command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.1.2 (hh3cRibVrfName) |
VPN instance name. |
N/A |
OCTET STRING |
OCTET STRING(0..31) |
|
1.3.6.1.4.1.25506.2.219.1.3 (hh3cRibVrfIndex) |
VPN instance index. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.6 (hh3cRibVrfIPv4PrefixNumber) |
Number of IPv4 route prefixes in the VPN instance. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.7 (hh3cRibVrfIPv4PrefixLimit) |
Maximum number of IPv4 route prefixes in the VPN instance. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
1. Execute the display ip routing-table vpn-instance vpn-instance-name summary command to examine the values for the Max Active Route and Remain Active Route fields. Verify that the number of IPv4 routes in the VPN instance has reached the upper limit.
a. If yes, proceed to step 2.
b. If not, proceed to step 3.
2. Execute the display ip routing-table vpn-instance vpn-instance-name statistics command to verify that the number of IPv4 routes of each protocol in the VPN instance is as expected.
a. If yes, enter IPv4 address family view of the local VPN instance, and set a greater value for the routing-table limit command.
b. If not, check and adjust the configuration of the specific routing protocol (for more information, see the protocol configuration guide) with exceeded routes. After modifying the configuration and removing redundant routes, repeat step 1 to identify whether the number of route prefixes is within the upper limit.
3. If the issue persists, collect configuration data, log information, and alarm information, and then contact H3C Support for help.
hh3cRibVrfIPv4PrefixExceedClear
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219. 2.0.4 |
The number of IPv4 route prefixes in the VPN instance drops below the maximum value. |
Recovery |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the number of IPv4 route prefixes in the VPN instance drops below the maximum value.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable rib vrf-prefixexceed-clear command.
OFF
CLI: Use the undo snmp-agent trap enable rib vrf-prefixexceed-clear command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.1.2 (hh3cRibVrfName) |
VPN instance name. |
No |
OCTET STRING |
OCTET STRING(0..31) |
|
1.3.6.1.4.1.25506.2.219.1.3 (hh3cRibVrfIndex) |
VPN instance index. |
No |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.6 (hh3cRibVrfIPv4PrefixNumber) |
Number of IPv4 route prefixes in the VPN instance. |
No |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.7 (hh3cRibVrfIPv4PrefixLimit) |
Maximum number of IPv4 route prefixes in the VPN instance. |
No |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
No action is required.
hh3cRibVrfIPv4PrefixTHExceed
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.2.0.5 |
The number of IPv4 route prefixes in the VPN instance exceeds the alarm threshold. |
Error |
Warning |
1.3.6.1.4.1.25506.2.219.2.0.6 (hh3cRibVrfIPv4PrefixTHExceedClr) |
ON |
Notification triggers
This notification is generated when the number of IPv4 route prefixes in the VPN instance exceeds the alarm threshold.
System impact
The number of IPv4 route prefixes in the VPN instance has reached the alarm threshold. Adding new route prefixes might affect services because of exceeded upper limit.
Status control
ON
CLI: Use the snmp-agent trap enable rib vrf-prefixthreshold-exceed command.
OFF
CLI: Use the undo snmp-agent trap enable rib vrf-prefixthreshold-exceed command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.1.2 (hh3cRibVrfName) |
VPN instance name. |
N/A |
OCTET STRING |
OCTET STRING(0..31) |
|
1.3.6.1.4.1.25506.2.219.1.3 (hh3cRibVrfIndex) |
VPN instance index. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.6 (hh3cRibVrfIPv4PrefixNumber) |
Number of IPv4 route prefixes in the VPN instance. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.8 (hh3cRibVrfIPv4PrefixTHLimit) |
Alarm threshold for the number of IPv4 route prefixes in the VPN instance. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
1. Execute the display ip routing-table vpn-instance vpn-instance-name summary command to examine the values for the Max Active Route, Remain Active Route, and Threshold value percentage fields. Verify that the number of IPv4 routes in the VPN instance has reached the alarm threshold.
a. If yes, proceed to step 2.
b. If not, proceed to step 3.
2. Execute the display ip routing-table vpn-instance vpn-instance-name statistics command to verify that the number of IPv4 routes of each protocol in the VPN instance is as expected.
a. If yes, enter IPv4 address family view of the local VPN instance, and set a greater value for the routing-table limit command.
b. If not, check and adjust the configuration of the specific routing protocol (for more information, see the protocol configuration guide) with exceeded routes. After modifying the configuration and removing redundant routes, repeat step 1 to identify whether the number of route prefixes has dropped below the alarm threshold.
3. If the issue persists, collect configuration data, log information, and alarm information, and then contact H3C Support for help.
hh3cRibVrfIPv4PrefixTHExceedClr
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.2.0.6 |
The number of IPv4 route prefixes in the VPN instance drops below the alarm threshold. |
Recovery |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the number of IPv4 route prefixes in the VPN instance drops below the alarm threshold.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable rib vrf-prefixthresholdexceed-clear command.
OFF
CLI: Use the undo snmp-agent trap enable rib vrf-prefixthresholdexceed-clear command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.1.2 (hh3cRibVrfName) |
VPN instance name. |
N/A |
OCTET STRING |
OCTET STRING(0..31) |
|
1.3.6.1.4.1.25506.2.219.1.3 (hh3cRibVrfIndex) |
VPN instance index. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.6 (hh3cRibVrfIPv4PrefixNumber) |
Number of IPv4 route prefixes in the VPN instance. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.8 (hh3cRibVrfIPv4PrefixTHLimit) |
Alarm threshold for the number of IPv4 route prefixes in the VPN instance. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
No action is required.
hh3cRibVrfIPv6PrefixExceed
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.2.0.7 |
The number of IPv6 route prefixes in the VPN instance exceeds the maximum value. |
Error |
Warning |
1.3.6.1.4.1.25506.2.219.2.0.8 (hh3cRibVrfIPv6PrefixExceedClear) |
ON |
Notification triggers
This notification is generated when the number of IPv6 route prefixes in the VPN instance exceeds the maximum value.
System impact
When the number of IPv6 route prefixes in the VPN instance exceeds the maximum value, you cannot add new route prefixes, which might result in route loss and traffic interruption.
Status control
ON
CLI: Use the snmp-agent trap enable ipv6 rib vrf-prefix-exceed command.
OFF
CLI: Use the undo snmp-agent trap enable ipv6 rib vrf-prefix-exceed command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.1.2 (hh3cRibVrfName) |
VPN instance name. |
N/A |
OCTET STRING |
OCTET STRING(0..31) |
|
1.3.6.1.4.1.25506.2.219.1.3 (hh3cRibVrfIndex) |
VPN instance index. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.9 (hh3cRibVrfIPv6PrefixNumber) |
Number of IPv6 route prefixes in the VPN instance. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.10 (hh3cRibVrfIPv6PrefixLimit) |
Maximum number of IPv6 route prefixes in the VPN instance. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
To resolve the issue:
1. Execute the display ipv6 routing-table vpn-instance vpn-instance-name summary command to examine the values for the Max Active Route and Remain Active Route fields. Verify that the number of IPv6 routes in the VPN instance has reached the upper limit.
a. If yes, proceed to step 2.
b. If not, proceed to step 3.
2. Execute the display ipv6 routing-table vpn-instance vpn-instance-name statistics command to verify that the number of IPv6 routes of each protocol in the VPN instance is as expected.
a. If yes, enter IPv6 address family view of the local VPN instance, and set a greater value for the routing-table limit command.
b. If not, check and adjust the configuration of the specific routing protocol (for more information, see the protocol configuration guide) with exceeded routes. After modifying the configuration and removing redundant routes, repeat step 1 to identify whether the number of route prefixes is within the upper limit.
3. If the issue persists, collect configuration data, log information, and alarm information, and then contact H3C Support for help.
hh3cRibVrfIPv6PrefixExceedClear
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.2.0.8 |
The number of IPv6 route prefixes in the VPN instance drops below the maximum value. |
Recovery |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the number of IPv6 route prefixes in the VPN instance drops below the maximum value.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable ipv6 rib vrf-prefixexceed-clear command.
OFF
CLI: Use the undo snmp-agent trap enable ipv6 rib vrf-prefixexceed-clear command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.1.2 (hh3cRibVrfName) |
VPN instance name. |
N/A |
OCTET STRING |
OCTET STRING(0..31) |
|
1.3.6.1.4.1.25506.2.219.1.3 (hh3cRibVrfIndex) |
VPN instance index. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.9 (hh3cRibVrfIPv6PrefixNumber) |
Number of IPv6 route prefixes in the VPN instance. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.10 (hh3cRibVrfIPv6PrefixLimit) |
Maximum number of IPv6 route prefixes in the VPN instance. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
No action is required.
hh3cRibVrfIPv6PrefixTHExceed
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.2.0.9 |
The number of IPv6 route prefixes in the VPN instance exceeds the alarm threshold. |
Error |
Warning |
1.3.6.1.4.1.25506.2.219.2.0.10 (hh3cRibVrfIPv6PrefixTHExceedClr) |
ON |
Notification triggers
This notification is generated when the number of IPv6 route prefixes in the VPN instance exceeds the alarm threshold.
System impact
The number of IPv6 route prefixes in the VPN instance has reached the alarm threshold. Adding new route prefixes might affect services because of exceeded upper limit.
Status control
ON
CLI: Use the snmp-agent trap enable ipv6 rib vrf-prefixthreshold-exceed command.
OFF
CLI: Use the undo snmp-agent trap enable ipv6 rib vrf-prefixthreshold-exceed command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.1.2 (hh3cRibVrfName) |
VPN instance name. |
N/A |
OCTET STRING |
OCTET STRING(0..31) |
|
1.3.6.1.4.1.25506.2.219.1.3 (hh3cRibVrfIndex) |
VPN instance index. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.9 (hh3cRibVrfIPv6PrefixNumber) |
Number of IPv6 route prefixes in the VPN instance. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.11 (hh3cRibVrfIPv6PrefixTHLimit) |
Alarm threshold for the number of IPv6 route prefixes in the VPN instance. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
To resolve the issue:
1. Execute the display ipv6 routing-table vpn-instance vpn-instance-name summary command to examine the values for the Max Active Route, Remain Active Route, and Threshold value percentage fields. Verify that the number of IPv6 routes in the VPN instance has reached the alarm threshold.
a. If yes, proceed to step 2.
b. If not, proceed to step 3.
2. Execute the display ipv6 routing-table vpn-instance vpn-instance-name statistics command to verify that the number of IPv6 routes of each protocol in the VPN instance is as expected.
a. If yes, enter IPv6 address family view of the local VPN instance, and set a greater value for the routing-table limit command.
b. If not, check and adjust the configuration of the specific routing protocol (for more information, see the protocol configuration guide) with exceeded routes. After modifying the configuration and removing redundant routes, repeat step 1 to identify whether the number of route prefixes has dropped below the alarm threshold.
3. If the issue persists, collect configuration data, log information, and alarm information, and then contact H3C Support for help.
hh3cRibVrfIPv6PrefixTHExceedClr
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.2.0.10 |
The number of IPv6 route prefixes in the VPN instance drops below the alarm threshold. |
Recovery |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the number of IPv6 route prefixes in the VPN instance drops below the alarm threshold.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable ipv6 rib vrf-prefixthresholdexceed-clear command.
OFF
CLI: Use the undo snmp-agent trap enable ipv6 rib vrf-prefixthresholdexceed-clear command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.1.2 (hh3cRibVrfName) |
VPN instance name. |
N/A |
OCTET STRING |
OCTET STRING(0..31) |
|
1.3.6.1.4.1.25506.2.219.1.3 (hh3cRibVrfIndex) |
VPN instance index. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.9 (hh3cRibVrfIPv6PrefixNumber) |
Number of IPv6 route prefixes in the VPN instance. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.1.11 (hh3cRibVrfIPv6PrefixTHLimit) |
Alarm threshold for the number of IPv6 route prefixes in the VPN instance. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
No action is required.
hh3cRibPUBIPv4PrefixExceed
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.4.0.1 |
The number of IPv4 route prefixes in the public network exceeds the maximum value. |
Error |
Warning |
1.3.6.1.4.1.25506.2.219.4.0.2 (hh3cRibPUBIPv4PrefixExceedClear) |
ON |
Notification triggers
This notification is generated when the number of IPv4 route prefixes in the public network exceeds the maximum value.
System impact
When the number of IPv4 route prefixes in the public network exceeds the maximum value, you cannot add new route prefixes, which might result in route loss and traffic interruption.
Status control
ON
CLI: Use the snmp-agent trap enable rib public-prefix-exceed command.
OFF
CLI: Use the undo snmp-agent trap enable rib public-prefix-exceed command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.3.1 (hh3cRibPublicIPv4PrefixNumber) |
Number of IPv4 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.3.2 (hh3cRibPublicIPv4PrefixLimit) |
Maximum number of IPv4 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
1. Execute the display ip routing-table summary command to examine the values for the Max Active Route and Remain Active Route fields. Verify that the number of IPv4 routes in the public network has reached the upper limit.
a. If yes, proceed to step 2.
b. If not, proceed to step 3.
2. Execute the display ip routing-table statistics command to verify that the number of IPv4 routes of each protocol in the public network is as expected.
a. If yes, execute the ip public-instance and address-family ipv4 commands to enter public network IPv4 address family view, and set a greater value for the routing-table limit command.
b. If not, check and adjust the configuration of the specific routing protocol (for more information, see the protocol configuration guide) with exceeded routes. After modifying the configuration and removing redundant routes, repeat step 1 to identify whether the number of route prefixes is within the upper limit.
3. If the issue persists, collect configuration data, log information, and alarm information, and then contact H3C Support for help.
hh3cRibPUBIPv4PrefixExceedClear
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219. 4.0.2 |
The number of IPv4 route prefixes in the public network drops below the maximum value. |
Recovery |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the number of IPv4 route prefixes in the public network drops below the maximum value.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable rib public-prefixexceed-clear command.
OFF
CLI: Use the undo snmp-agent trap enable rib public-prefixexceed-clear command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.3.1 (hh3cRibPublicIPv4PrefixNumber) |
Number of IPv4 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.3.2 (hh3cRibPublicIPv4PrefixLimit) |
Maximum number of IPv4 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
No action is required.
hh3cRibPUBIPv4PrefixTHExceed
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219. 4.0.3 |
The number of IPv4 route prefixes in the public network exceeds the alarm threshold. |
Error |
Warning |
1.3.6.1.4.1.25506.2.219.4.0.4 (hh3cRibPUBIPv4PrefixTHExceedClr) |
ON |
Notification triggers
This notification is generated when the number of IPv4 route prefixes in the public network exceeds the alarm threshold.
System impact
The number of IPv4 route prefixes in the public network has reached the alarm threshold. Adding new route prefixes might affect services because of exceeded upper limit.
Status control
ON
CLI: Use the snmp-agent trap enable rib public-prefixthreshold-exceed command.
OFF
CLI: Use the undo snmp-agent trap enable rib public-prefixthreshold-exceed command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.3.1 (hh3cRibPublicIPv4PrefixNumber) |
Number of IPv4 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.3.3 (hh3cRibPublicIPv4PrefixTHLimit) |
Alarm threshold for the number of IPv4 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
1. Execute the display ip routing-table summary command to examine the values for the Max Active Route, Remain Active Route, and Threshold value percentage fields. Verify that the number of IPv4 routes in the public network has reached the alarm threshold.
a. If yes, proceed to step 2.
b. If not, proceed to step 3.
2. Execute the display ip routing-table statistics command to verify that the number of IPv4 routes of each protocol in the public network is as expected.
a. If yes, execute the ip public-instance and address-family ipv4 commands to enter public network IPv4 address family view, and set a greater value for the routing-table limit command.
b. If not, check and adjust the configuration of the specific routing protocol (for more information, see the protocol configuration guide) with exceeded routes. After modifying the configuration and removing redundant routes, repeat step 1 to identify whether the number of route prefixes has dropped below the alarm threshold.
3. If the issue persists, collect configuration data, log information, and alarm information, and then contact H3C Support for help.
hh3cRibPUBIPv4PrefixTHExceedClr
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.4.0.4 |
The number of IPv4 route prefixes in the public network drops below the alarm threshold. |
Recovery |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the number of IPv4 route prefixes in the public network drops below the alarm threshold.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable rib public-prefixthresholdexceed-clear command.
OFF
CLI: Use the undo snmp-agent trap enable rib public-prefixthresholdexceed-clear command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.3.1 (hh3cRibPublicIPv4PrefixNumber) |
Number of IPv4 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.3.3 (hh3cRibPublicIPv4PrefixTHLimit) |
Alarm threshold for the number of IPv4 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
No action is required.
hh3cRibPUBIPv6PrefixExceed
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.4.0.5 |
The number of IPv6 route prefixes in the public network exceeds the maximum value. |
Error |
Warning |
1.3.6.1.4.1.25506.2.219.4.0.6 (hh3cRibPUBIPv6PrefixExceedClear) |
ON |
Notification triggers
This notification is generated when the number of IPv6 route prefixes in the public network exceeds the maximum value.
System impact
When the number of IPv6 route prefixes in the public network exceeds the maximum value, you cannot add new route prefixes, which might result in route loss and traffic interruption.
Status control
ON
CLI: Use the snmp-agent trap enable ipv6 rib public-prefix-exceed command.
OFF
CLI: Use the undo snmp-agent trap enable ipv6 rib public-prefix-exceed command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.3.4 (hh3cRibPublicIPv6PrefixNumber) |
Number of IPv6 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.3.5 (hh3cRibPublicIPv6PrefixLimit) |
Maximum number of IPv6 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
To resolve the issue:
1. Execute the display ipv6 routing-table summary command to examine the values for the Max Active Route and Remain Active Route fields. Verify that the number of IPv6 routes in the public network has reached the upper limit.
a. If yes, proceed to step 2.
b. If not, proceed to step 3.
2. Execute the display ipv6 routing-table statistics command to verify that the number of IPv6 routes of each protocol in the public network is as expected.
a. If yes, execute the ipv6 public-instance and address-family ipv6 commands to enter public network IPv6 address family view, and set a greater value for the routing-table limit command.
b. If not, check and adjust the configuration of the specific routing protocol (for more information, see the protocol configuration guide) with exceeded routes. After modifying the configuration and removing redundant routes, repeat step 1 to identify whether the number of route prefixes is within the upper limit.
3. If the issue persists, collect configuration data, log information, and alarm information, and then contact H3C Support for help.
hh3cRibPUBIPv6PrefixExceedClear
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.4.0.6 |
The number of IPv6 route prefixes in the public network drops below the maximum value. |
Recovery |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the number of IPv6 route prefixes in the public network drops below the maximum value.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable ipv6 rib public-prefixexceed-clear command.
OFF
CLI: Use the undo snmp-agent trap enable ipv6 rib public-prefixexceed-clear command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.3.4 (hh3cRibPublicIPv6PrefixNumber) |
Number of IPv6 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.3.5 (hh3cRibPublicIPv6PrefixLimit) |
Maximum number of IPv6 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
No action is required.
hh3cRibPUBIPv6PrefixTHExceed
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219. 4.0.7 |
The number of IPv6 route prefixes in the public network exceeds the alarm threshold. |
Error |
Warning |
1.3.6.1.4.1.25506.2.219.4.0.8 (hh3cRibPUBIPv6PrefixTHExceedClr) |
ON |
Notification triggers
This notification is generated when the number of IPv6 route prefixes in the public network exceeds the alarm threshold.
System impact
The number of IPv6 route prefixes in the public network has reached the alarm threshold. Adding new route prefixes might affect services because of exceeded upper limit.
Status control
ON
CLI: Use the snmp-agent trap enable ipv6 rib public-prefixthreshold-exceed command.
OFF
CLI: Use the undo snmp-agent trap enable ipv6 rib public-prefixthreshold-exceed command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.3.4 (hh3cRibPublicIPv6PrefixNumber) |
Number of IPv6 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.3.6 (hh3cRibPublicIPv6PrefixTHLimit) |
Alarm threshold for the number of IPv6 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
1. Execute the display ipv6 routing-table summary command to examine the values for the Max Active Route, Remain Active Route, and Threshold value percentage fields. Verify that the number of IPv6 routes in the public network has reached the alarm threshold.
a. If yes, proceed to step 2.
b. If not, proceed to step 3.
2. Execute the display ipv6 routing-table statistics command to verify that the number of IPv6 routes of each protocol in the public network is as expected.
a. If yes, execute the ipv6 public-instance and address-family ipv6 commands to enter public network IPv6 address family view, and set a greater value for the routing-table limit command.
b. If not, check and adjust the configuration of the specific routing protocol (for more information, see the protocol configuration guide) with exceeded routes. After modifying the configuration and removing redundant routes, repeat step 1 to identify whether the number of route prefixes has dropped below the alarm threshold.
3. If the issue persists, collect configuration data, log information, and alarm information, and then contact H3C Support for help.
hh3cRibPUBIPv6PrefixTHExceedClr
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219. 4.0.8 |
The number of IPv6 route prefixes in the public network drops below the alarm threshold. |
Recovery |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the number of IPv6 route prefixes in the public network drops below the alarm threshold.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable ipv6 rib public-prefixthresholdexceed-clear command.
OFF
CLI: Use the undo snmp-agent trap enable ipv6 rib public-prefixthresholdexceed-clear command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.3.4 (hh3cRibPublicIPv6PrefixNumber) |
Number of IPv6 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.3.6 (hh3cRibPublicIPv6PrefixTHLimit) |
Alarm threshold for the number of IPv6 route prefixes in the public network. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
No action is required.
hh3cRibIPv4PrefixExceed
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.6.0.1 |
The number of IPv4 route prefixes on the device exceeds the maximum value. |
Error |
Warning |
1.3.6.1.4.1.25506.2.219.6.0.2 (hh3cRibIPv4PrefixExceedClear) |
ON |
Notification triggers
This notification is generated when the number of IPv4 route prefixes on the device exceeds the maximum value.
System impact
When the number of IPv4 route prefixes on the device exceeds the maximum value, you cannot add new route prefixes, which might result in route loss and traffic interruption.
Status control
ON
CLI: Use the snmp-agent trap enable rib prefix-exceed command.
OFF
CLI: Use the undo snmp-agent trap enable rib prefix-exceed command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.5.1 (hh3cRibIPv4PrefixNumber) |
Number of IPv4 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.5.2 (hh3cRibIPv4PrefixLimit) |
Maximum number of IPv4 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
1. Execute the display ip routing-table all-routes statistics command to verify that the number of IPv4 routes in the public network and all VPN instances on the device has reached the upper limit.
a. If yes, proceed to step 2.
b. If not, proceed to step 3.
2. Execute the display ip routing-table all-routes statistics command to verify that the number of IPv4 routes of each protocol in the public network and all VPN instances is as expected.
a. If yes, proceed to step 3.
b. If not, check and adjust the configuration of the specific routing protocol (for more information, see the protocol configuration guide) with exceeded routes. After modifying the configuration and removing redundant routes, repeat step 1 to identify whether the number of route prefixes is within the upper limit.
3. If the issue persists, collect configuration data, log information, and alarm information, and then contact H3C Support for help.
hh3cRibIPv4PrefixExceedClear
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.6.0.2 |
The number of IPv4 route prefixes on the device drops below the maximum value. |
Recovery |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the number of IPv4 route prefixes on the device drops below the maximum value.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable rib prefix-exceed-clear command.
OFF
CLI: Use the undo snmp-agent trap enable rib prefix-exceed-clear command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.5.1 (hh3cRibIPv4PrefixNumber) |
Number of IPv4 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.5.2 (hh3cRibIPv4PrefixLimit) |
Maximum number of IPv4 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
No action is required.
hh3cRibIPv4PrefixTHExceed
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.6.0.3 |
The number of IPv4 route prefixes on the device exceeds the alarm threshold. |
Error |
Warning |
1.3.6.1.4.1.25506.2.219.6.0.4 (hh3cRibIPv4PrefixTHExceedClr) |
ON |
Notification triggers
This notification is generated when the number of IPv4 route prefixes on the device exceeds the alarm threshold.
System impact
The number of IPv4 route prefixes on the device has reached the alarm threshold. Adding new route prefixes might affect services because of exceeded upper limit.
Status control
ON
CLI: Use the snmp-agent trap enable rib prefix-threshold-exceed command.
OFF
CLI: Use the undo snmp-agent trap enable rib prefix-threshold-exceed command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.5.1 (hh3cRibIPv4PrefixNumber) |
Number of IPv4 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.5.3 (hh3cRibIPv4PrefixTHLimit) |
Alarm threshold for the number of IPv4 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
To resolve the issue:
1. Execute the display ip routing-table all-routes statistics command to verify that the number of IPv4 routes in the public network and all VPN instances on the device has reached the alarm threshold. The alarm threshold is the value configured with the routing-table limit number simply-alert command in RIB IPv4 address family view.
a. If yes, proceed to step 2.
b. If not, proceed to step 3.
2. Execute the display ip routing-table all-routes statistics command to verify that the number of IPv4 routes of each protocol in the public network and all VPN instances is as expected.
a. If yes, execute the rib and address-family ipv4 commands in sequence to enter RIB IPv4 address family view, and set a greater value for the routing-table limit number simply-alert command.
b. If not, check and adjust the configuration of the specific routing protocol (for more information, see the protocol configuration guide) with exceeded routes. After modifying the configuration and removing redundant routes, repeat step 1 to identify whether the number of route prefixes has dropped below the alarm threshold.
3. If the issue persists, collect configuration data, log information, and alarm information, and then contact H3C Support for help.
hh3cRibIPv4PrefixTHExceedClr
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.6.0.4 |
The number of IPv4 route prefixes on the device drops below the alarm threshold. |
Recovery |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the number of IPv4 route prefixes on the device drops below the alarm threshold.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable rib prefix-thresholdexceed-clear command.
OFF
CLI: Use the undo snmp-agent trap enable rib prefix-thresholdexceed-clear command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.5.1 (hh3cRibIPv4PrefixNumber) |
Number of IPv4 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.5.3 (hh3cRibIPv4PrefixTHLimit) |
Alarm threshold for the number of IPv4 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
No action is required.
hh3cRibIPv6PrefixExceed
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.6.0.5 |
The number of IPv6 route prefixes on the device exceeds the maximum value. |
Error |
Warning |
1.3.6.1.4.1.25506.2.219.6.0.6 (hh3cRibIPv6PrefixExceedClear) |
ON |
Notification triggers
This notification is generated when the number of IPv6 route prefixes on the device exceeds the maximum value.
System impact
When the number of IPv6 route prefixes on the device exceeds the maximum value, you cannot add new route prefixes, which might result in route loss and traffic interruption.
Status control
ON
CLI: Use the snmp-agent trap enable ipv6 rib prefix-exceed command.
OFF
CLI: Use the undo snmp-agent trap enable ipv6 rib prefix-exceed command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.5.4 (hh3cRibIPv6PrefixNumber) |
Number of IPv6 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.5.5 (hh3cRibIPv6PrefixLimit) |
Maximum number of IPv6 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
To resolve the issue:
1. Execute the display ipv6 routing-table all-routes statistics command to verify that the number of IPv6 routes in the public network and all VPN instances on the device has reached the upper limit.
a. If yes, proceed to step 2.
b. If not, proceed to step 3.
2. Execute the display ipv6 routing-table all-routes statistics command to verify that the number of IPv6 routes of each protocol in the public network and all VPN instances is as expected.
a. If yes, proceed to step 3.
b. If not, check and adjust the configuration of the specific routing protocol (for more information, see the protocol configuration guide) with exceeded routes. After modifying the configuration and removing redundant routes, repeat step 1 to identify whether the number of route prefixes is within the upper limit.
3. If the issue persists, collect configuration data, log information, and alarm information, and then contact H3C Support for help.
hh3cRibIPv6PrefixExceedClear
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.6.0.6 |
The number of IPv6 route prefixes on the device drops below the maximum value. |
Recovery |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the number of IPv4 route prefixes on the device drops below the maximum value.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable ipv6 rib prefix-exceed-clear command.
OFF
CLI: Use the undo snmp-agent trap enable ipv6 rib prefix-exceed-clear command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.5.4 (hh3cRibIPv6PrefixNumber) |
Number of IPv6 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.5.5 (hh3cRibIPv6PrefixLimit) |
Maximum number of IPv6 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
No action is required.
hh3cRibIPv6PrefixTHExceed
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.6.0.7 |
The number of IPv6 route prefixes on the device exceeds the alarm threshold. |
Error |
Warning |
1.3.6.1.4.1.25506.2.219.6.0.8 (hh3cRibIPv6PrefixTHExceedClr) |
ON |
Notification triggers
This notification is generated when the number of IPv6 route prefixes on the device exceeds the alarm threshold.
System impact
The number of IPv6 route prefixes on the device has reached the alarm threshold. Adding new route prefixes might affect services because of exceeded upper limit.
Status control
ON
CLI: Use the snmp-agent trap enable ipv6 rib prefix-threshold-exceed command.
OFF
CLI: Use the undo snmp-agent trap enable ipv6 rib prefix-threshold-exceed command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.5.4 (hh3cRibIPv6PrefixNumber) |
Number of IPv6 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.5.6 (hh3cRibIPv6PrefixTHLimit) |
Alarm threshold for the number of IPv6 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
To resolve the issue:
1. Execute the display ipv6 routing-table all-routes statistics command to verify that the number of IPv6 routes in the public network and all VPN instances on the device has reached the alarm threshold. The alarm threshold is the value configured with the routing-table limit number simply-alert command in RIB IPv6 address family view.
a. If yes, proceed to step 2.
b. If not, proceed to step 3.
2. Execute the display ipv6 routing-table all-routes statistics command to verify that the number of IPv6 routes of each protocol in the public network and all VPN instances is as expected.
a. If yes, execute the rib and address-family ipv6 commands in sequence to enter RIB IPv6 address family view, and set a greater value for the routing-table limit number simply-alert command.
b. If not, check and adjust the configuration of the specific routing protocol (for more information, see the protocol configuration guide) with exceeded routes. After modifying the configuration and removing redundant routes, repeat step 1 to identify whether the number of route prefixes has dropped below the alarm threshold.
3. If the issue persists, collect configuration data, log information, and alarm information, and then contact H3C Support for help.
hh3cRibIPv6PrefixTHExceedClr
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.219.6.0.8 |
The number of IPv6 route prefixes on the device drops below the alarm threshold. |
Recovery |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the number of IPv6 route prefixes on the device instance drops below the alarm threshold.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable ipv6 rib prefix-thresholdexceed-clear command.
OFF
CLI: Use the undo snmp-agent trap enable ipv6 rib prefix-thresholdexceed-clear command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.219.5.4 (hh3cRibIPv6PrefixNumber) |
Number of IPv6 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
|
1.3.6.1.4.1.25506.2.219.5.6 (hh3cRibIPv6PrefixTHLimit) |
Alarm threshold for the number of IPv6 route prefixes on the device. |
N/A |
Gauge32 |
INTEGER(0..4294967295) |
Recommended action
No action is required.
