RM
- RM_1.3.6.1.4.1.2011.5.25.145.6.1 hwTunnelGroupUp
- RM_1.3.6.1.4.1.2011.5.25.145.6.2 hwTunnelGroupDown
- RM_1.3.6.1.4.1.2011.5.25.145.19.1.1 hwPublicIpv4PrefixExceed
- RM_1.3.6.1.4.1.2011.5.25.145.19.1.2 hwPublicIpv4PrefixExceedClear
- RM_1.3.6.1.4.1.2011.5.25.145.19.1.3 hwPublicIpv4PrefixThresholdExceed
- RM_1.3.6.1.4.1.2011.5.25.145.19.1.4 hwPublicIpv4PrefixThresholdExceedClear
- RM_1.3.6.1.4.1.2011.5.25.145.19.2.1 hwPublicIpv6PrefixExceed
- RM_1.3.6.1.4.1.2011.5.25.145.19.2.2 hwPublicIpv6PrefixExceedClear
- RM_1.3.6.1.4.1.2011.5.25.145.19.2.3 hwPublicIpv6PrefixThresholdExceed
- RM_1.3.6.1.4.1.2011.5.25.145.19.2.4 hwPublicIpv6PrefixThresholdExceedClear
- RM_1.3.6.1.4.1.2011.5.25.145.19.3.1 hwL3vpnIpv6PrefixExceed
- RM_1.3.6.1.4.1.2011.5.25.145.19.3.2 hwL3vpnIpv6PrefixExceedClear
- RM_1.3.6.1.4.1.2011.5.25.145.19.3.3 hwL3vpnIpv6PrefixThresholdExceed
RM_1.3.6.1.4.1.2011.5.25.145.6.1 hwTunnelGroupUp
Description
RM/2/TNLGROUP_UP:OID [oid] The status of the tunnel group changed to Up. (Destination=[IPADDR], TunnelPolicy=[STRING])
The status of the tunnel group used by the service changed to Up.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.145.6.1 | Major |
qualityOfServiceAlarm(2) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
Destination |
Destination IP address of the tunnel on which services depend. |
TunnelPolicy |
Tunnel policy used by services. |
RM_1.3.6.1.4.1.2011.5.25.145.6.2 hwTunnelGroupDown
Description
RM/2/TNLGROUP_DOWN:OID [oid] The status of the tunnel group changed to Down. (Destination=[IPADDR], TunnelPolicy=[STRING])
The status of the tunnel group used by the service changed to Down.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.145.6.2 | Major |
qualityOfServiceAlarm(2) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
Destination |
Destination IP address of the tunnel on which services depend. |
TunnelPolicy |
Tunnel policy used by services. |
Possible Causes
1:
A link fault occurred.
2:
The configuration was changed, causing no available tunnel to the specified destination.
3:
The VPN routes iterated to public network tunnels are deleted.
Procedure
- After a tunnel group fails, the device sends an alarm with
information about the destination address and tunnel policy to inform
users of the tunnel group failure. You can run the display this command
in the tunnel policy view to check whether tunnel-policy tunnel-policy-name is displayed.
- If tunnel-policy tunnel-policy-name is displayed, run the display tunnel-policy tunnel-policy-name command to check the tunnel policy.
- If Select-Seq is displayed, the sequence tunnel policy is used. Then, go to Step 2.
- If Destination and Tunnel Intf are displayed, the binding tunnel policy is used. Then, go to Step 3.
If tunnel-policy tunnel-policy-name is not displayed, go to Step 4.
- Run the display tunnel-info all command to check whether there are tunnels of the type configured
in the tunnel policy.
- If there are tunnels of the type configured in the tunnel policy, go to Step 5.
- If there is no tunnel of the type configured in the tunnel policy, change the tunnel policy used by VPN services.
- If a binding tunnel policy is used, run the display
interface tunnel interface-number command to check whether the bound tunnel interface is Up.
- If the bound tunnel interface is Up, go to Step 5.
- If the bound tunnel interface is not Up, configure the TE interface.
- Check where there is an LSP.
- If there is an LSP, go to Step 5.
- If there is no LSP (LDP LSP, BGP LSP, or static LSP), check the LSP configuration.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
RM_1.3.6.1.4.1.2011.5.25.145.19.1.1 hwPublicIpv4PrefixExceed
Description
RM/2/PUBLIC_IPV4_PREFIX_EXCEED:OID [oid] The number of public IPv4 prefixes exceeded the maximum value. (PrefixCount=[Integer], MaxValue=[Integer])
The number of IPv4 public route prefixes exceeded that supported by the system.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.145.19.1.1 |
Major |
qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
PrefixCount |
Indicates the number of IPv4 public route prefixes in the routing table. |
MaxValue |
Indicates the maximum number of IPv4 public route prefixes supported by the device. |
Impact on the System
New IPv4 public route prefixes cannot be added to the routing table. Services will be affected if the number of IPv4 route prefixes keeps increasing.
Possible Causes
Cause 1:
A large number of IPv4 dynamic protocol routes (BGP or IGP routes for example), static routes, direct routes, or UNR routes were added to the routing table.
Cause 2:
The maximum number of IPv4 public route prefixes supported by the system was decreased.
Procedure
- Run the display ip routing-table statistics command
to check the number of IPv4 public route prefixes and the number of
routes of each protocol that are added to the routing table. Run the display ip routing-table limit command to check
the number of IPv4 public route prefixes supported by the system.Check whether services need these routes or whether the routes are added to the routing table due to incorrect configurations.
If the routes are added to the routing table due to incorrect configurations, go to 2.
If services need these routes, replace the license or contact technical support personnel for specification expansion.
- Adjust the configurations to delete unneeded
routes, and check whether the RM_1.3.6.1.4.1.2011.5.25.145.19.1.2 hwPublicIpv4PrefixExceedClear alarm is generated.
- If the RM_1.3.6.1.4.1.2011.5.25.145.19.1.2 hwPublicIpv4PrefixExceedClear alarm is not generated, go to 3.
- If the RM_1.3.6.1.4.1.2011.5.25.145.19.1.2 hwPublicIpv4PrefixExceedClear alarm is generated, go to 4.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
RM_1.3.6.1.4.1.2011.5.25.145.19.1.2 hwPublicIpv4PrefixExceedClear
Description
RM/2/PUBLIC_IPV4_PREFIX_EXCEED_RESM:OID [oid] The number of public IPv4 prefixes falls below the maximum value. (PrefixCount=[Integer], MaxValue=[Integer])
The number of IPv4 public route prefixes fell below that supported by the system.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.145.19.1.2 |
Major |
qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
PrefixCount |
Indicates the number of IPv4 public route prefixes in the routing table. |
MaxValue |
Indicates the maximum number of IPv4 public route prefixes supported by the device. |
Possible Causes
Cause 1:
The network administrator deleted some routes from the routing table or the number of routes learned by dynamic protocols decreased due to network topology changes.
Cause 2:
The maximum number of IPv4 public route prefixes supported by the system was increased or the limit on the number of IPv4 public route prefixes was deleted.
RM_1.3.6.1.4.1.2011.5.25.145.19.1.3 hwPublicIpv4PrefixThresholdExceed
Description
RM/4/PUBLIC_IPV4_PREFIX_THRESHOLD_EXCEED:OID [oid] The number of public IPv4 prefixes exceeded the threshold. (PrefixCount=[Integer], Threshold=[Integer])
The number of IPv4 public route prefixes exceeded the alarm threshold.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.145.19.1.3 |
Warning |
qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
PrefixCount |
Indicates the number of IPv4 public route prefixes in the routing table. |
Threshold |
Indicates the threshold of the number of IPv4 public route prefixes. |
Impact on the System
The number of IPv4 public route prefixes exceeded the alarm threshold, and services may be affected if the number of IPv4 public route prefixes keeps increasing.
Possible Causes
Cause 1:
A large number of IPv4 dynamic protocol routes (BGP or IGP routes for example), static routes, direct routes, or UNR routes were added to the routing table.
Cause 2:
The threshold of the number of IPv4 public route prefixes was decreased.
Procedure
- Run the display current-configuration command to check whether the threshold value specified in the ip prefix-limit command is too small.
- Rerun the ip prefix-limit number alert-percent command to increase number and alert-percent.
-
Run the display ip routing-table
statistics command to check the number of IPv4 public route
prefixes and the number of routes of each protocol that are added
to the routing table. Check whether services need these routes or whether the routes are added to the routing table due to incorrect configurations.
If the routes are added to the routing table due to incorrect configurations, go to 4.
If services need these routes, replace the license or contact technical support personnel for specification expansion.
-
Adjust the configurations to delete unneeded routes, and check
whether the RM_1.3.6.1.4.1.2011.5.25.145.19.1.4 hwPublicIpv4PrefixThresholdExceedClear alarm is generated.
- If the RM_1.3.6.1.4.1.2011.5.25.145.19.1.4 hwPublicIpv4PrefixThresholdExceedClear alarm is not generated, go to 5.
- If the RM_1.3.6.1.4.1.2011.5.25.145.19.1.4 hwPublicIpv4PrefixThresholdExceedClear alarm is generated, go to 6.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
RM_1.3.6.1.4.1.2011.5.25.145.19.1.4 hwPublicIpv4PrefixThresholdExceedClear
Description
RM/4/PUBLIC_IPV4_PREFIX_THRESHOLD_EXCEED_RESM:OID [oid] The number of public IPv4 prefixes falls below the threshold. (PrefixCount=[Integer], Threshold=[Integer])
The number of IPv4 public route prefixes fell below the clear alarm threshold.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.145.19.1.4 |
Warning |
qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
PrefixCount |
Indicates the number of IPv4 public route prefixes in the routing table. |
Threshold |
Indicates the threshold of the number of IPv4 public route prefixes. |
Possible Causes
Cause 1:
The network administrator deleted some routes from the routing table or the number of routes learned by dynamic protocols decreased due to network topology changes.
Cause 2:
The threshold of IPv4 public route prefixes was increased or the limit on the number of IPv4 public route prefixes was deleted.
RM_1.3.6.1.4.1.2011.5.25.145.19.2.1 hwPublicIpv6PrefixExceed
Description
RM/2/PUBLIC_IPV6_PREFIX_EXCEED:OID [oid] The number of public IPv6 prefixes exceeded the maximum value. (PrefixCount=[Integer], MaxValue=[Integer])
The number of IPv6 public route prefixes exceeded that supported by the system.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.145.19.2.1 |
Major |
qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
PrefixCount |
Indicates the number of IPv6 public route prefixes in the routing table. |
MaxValue |
Indicates the maximum number of IPv6 public route prefixes supported by the device. |
Impact on the System
New IPv6 public route prefixes cannot be added to the routing table. Services will be affected if the number of IPv6 route prefixes keeps increasing.
Possible Causes
Cause 1:
A large number of IPv6 dynamic protocol routes (BGP or IGP routes for example), static routes, direct routes, or UNR routes were added to the routing table.
Cause 2:
The maximum number of IPv6 public route prefixes supported by the system was decreased.
Procedure
- Run the display ipv6 routing-table statistics command
to check the number of IPv6 public route prefixes and the number of
routes of each protocol that are added to the routing table.Check whether services need these routes or whether the routes are added to the routing table due to incorrect configurations.
If the routes are added to the routing table due to incorrect configurations, go to 2.
If services need these routes, replace the license or contact technical support personnel for specification expansion.
- Adjust the configurations to delete unneeded
routes, and check whether the RM_1.3.6.1.4.1.2011.5.25.145.19.2.2 hwPublicIpv6PrefixExceedClear alarm is generated.
- If the RM_1.3.6.1.4.1.2011.5.25.145.19.2.2 hwPublicIpv6PrefixExceedClear alarm is not generated, go to 3.
- If the RM_1.3.6.1.4.1.2011.5.25.145.19.2.2 hwPublicIpv6PrefixExceedClear alarm is generated, go to 4.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
RM_1.3.6.1.4.1.2011.5.25.145.19.2.2 hwPublicIpv6PrefixExceedClear
Description
RM/2/PUBLIC_IPV6_PREFIX_EXCEED_RESM:OID [oid] The number of public IPv6 prefixes falls below the maximum value. (PrefixCount=[Integer], MaxValue=[Integer])
The number of IPv6 public route prefixes fell below that supported by the system.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.145.19.2.2 |
Major |
qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
PrefixCount |
Indicates the number of IPv6 public route prefixes in the routing table. |
MaxValue |
Indicates the maximum number of IPv6 public route prefixes supported by the device. |
Possible Causes
Cause 1:
The network administrator deleted some routes from the routing table or the number of routes learned by dynamic protocols decreased due to network topology changes.
Cause 2:
The maximum number of IPv6 public route prefixes supported by the system was increased or the limit on the number of IPv6 public route prefixes was deleted.
RM_1.3.6.1.4.1.2011.5.25.145.19.2.3 hwPublicIpv6PrefixThresholdExceed
Description
RM/4/PUBLIC_IPV6_PREFIX_THRESHOLD_EXCEED:OID [oid] The number of public IPv6 prefixes exceeded the threshold. (PrefixCount=[Integer], Threshold=[Integer])
The number of IPv6 public route prefixes exceeded the alarm threshold.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.145.19.2.3 |
Warning |
qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
PrefixCount |
Indicates the number of IPv6 public route prefixes in the routing table. |
Threshold |
Indicates the threshold of the number of IPv6 public route prefixes. |
Impact on the System
The number of IPv6 public route prefixes exceeded the alarm threshold, and services may be affected if the number of IPv6 public route prefixes keeps increasing.
Possible Causes
Cause 1:
A large number of IPv6 dynamic protocol routes (BGP or IGP routes for example), static routes, direct routes, or UNR routes were added to the routing table.
Cause 2:
The threshold of the number of IPv6 public route prefixes was decreased.
Procedure
- Run the display current-configuration command to check whether the threshold value specified in the ipv6 prefix-limit command is too small.
- Rerun the ipv6 prefix-limit number alert-percent command to increase number and alert-percent.
- Run the display
ipv6 routing-table statistics command to check the
number of IPv6 public route prefixes and the number of routes of each
protocol that are added to the routing table. Check whether services need these routes or whether the routes are added to the routing table due to incorrect configurations.
If the routes are added to the routing table due to incorrect configurations, go to 4.
If services need these routes, replace the license or contact technical support personnel for specification expansion.
- Adjust the configurations to delete unneeded
routes, and check whether the RM_1.3.6.1.4.1.2011.5.25.145.19.2.4 hwPublicIpv6PrefixThresholdExceedClear alarm is generated.
- If the RM_1.3.6.1.4.1.2011.5.25.145.19.2.4 hwPublicIpv6PrefixThresholdExceedClear alarm is not generated, go to 5.
- If the RM_1.3.6.1.4.1.2011.5.25.145.19.2.4 hwPublicIpv6PrefixThresholdExceedClear alarm is generated, go to 6.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
RM_1.3.6.1.4.1.2011.5.25.145.19.2.4 hwPublicIpv6PrefixThresholdExceedClear
Description
RM/4/PUBLIC_IPV6_PREFIX_THRESHOLD_EXCEED_RESM:OID [oid] The number of public IPv6 prefixes falls below the threshold. (PrefixCount=[Integer], Threshold=[Integer])
The number of IPv6 public route prefixes fell below the clear alarm threshold.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.145.19.2.4 |
Warning |
qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
PrefixCount |
Indicates the number of IPv6 public route prefixes in the routing table. |
Threshold |
Indicates the threshold of the number of IPv6 public route prefixes. |
Possible Causes
Cause 1:
The network administrator deleted some routes from the routing table or the number of routes learned by dynamic protocols decreased due to network topology changes.
Cause 2:
The threshold of IPv6 public route prefixes was increased or the limit on the number of IPv4 public route prefixes was deleted.
RM_1.3.6.1.4.1.2011.5.25.145.19.3.1 hwL3vpnIpv6PrefixExceed
Description
RM/2/L3VPN_IPV6_PREFIX_EXCEED:OID [OID] The number of IPv6 prefixes in the VPN instance exceeded the maximum value. (VpnInstanceName=[octet], PrefixCount=[Integer], MaxValue=[Integer])
The number of IPv6 route prefixes in the VPN instance exceeded the maximum number that is allowed.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.145.19.3.1 | Major | qualityOfServiceAlarm |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
VpnInstanceName |
Name of a VPN instance |
PrefixCount |
Current number of IPv6 route prefixes in the VPN instance |
MaxValue |
Maximum number of IPv6 route prefixes in the VPN instance |
Possible Causes
Cause 1:
A large number of IPv6 VPN dynamic protocol (BGP or an IGP), static, direct, and UNR routes were added to the routing table.
Cause 2:
The maximum number of IPv6 route prefixes in the VPN instance was reduced.
Procedure
- Run the display
ipv6 routing-table vpn-instance vpn-instance-name statistics command to check the total number of route prefixes and the number
of route prefixes of each protocol. Then run the display ipv6
routing-table limit command to check whether the
number of IPv6 route prefixes in the VPN instance has exceeded the
maximum number that is allowed.
If the number of IPv6 route prefixes in the VPN instance has exceeded the maximum number that is allowed, go to Step 3.
If the number of IPv6 route prefixes in the VPN instance has not exceeded the maximum number that is allowed, go to Step 2.
- Collect alarm information and configuration information, and then contact technical support personnel.
- Implement capacity expansion or delete unnecessary services.
- End.
RM_1.3.6.1.4.1.2011.5.25.145.19.3.2 hwL3vpnIpv6PrefixExceedClear
Description
RM/2/L3VPN_IPV6_PREFIX_EXCEED_RESM:OID [OID] The number of IPv6 prefixes in the VPN instance falls below the maximum value. (VpnInstanceName=[octet], PrefixCount=[Integer], MaxValue=[Integer])
The number of IPv6 route prefixes in the VPN instance fell below the maximum number that is allowed.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.145.19.3.2 | Major | qualityOfServiceAlarm |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
VpnInstanceName |
Name of a VPN instance |
PrefixCount |
Current number of IPv6 route prefixes in the VPN instance |
MaxValue |
Maximum number of IPv6 route prefixes in the VPN instance |
RM_1.3.6.1.4.1.2011.5.25.145.19.3.3 hwL3vpnIpv6PrefixThresholdExceed
Description
RM/4/L3VPN_IPV6_PREFIX_THRESHOLD_EXCEED:OID [OID] The number of IPv6 prefixes in the VPN instance exceeded the threshold. (VpnInstanceName=[octet], PrefixCount=[Integer], Threshold=[Integer])
The number of IPv6 route prefixes in the VPN instance exceeded the alarm threshold.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.145.19.3.3 | Warning | qualityOfServiceAlarm |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
VpnInstanceName |
Name of a VPN instance |
PrefixCount |
Current number of IPv6 route prefixes in the VPN instance |
Threshold |
Alarm threshold for the number of IPv6 route prefixes in the VPN instance |
Impact on the System
The number of IPv6 route prefixes in the VPN instance is approaching the maximum number that is allowed, and route prefixes will no longer be accepted if the maximum number is reached, affecting services.
Possible Causes
Cause 1:
A large number of IPv6 VPN dynamic protocol (BGP or an IGP), static, direct, and UNR routes were added to the routing table.
Cause 2:
The alarm threshold for the number of IPv6 route prefixes in the VPN instance was reduced.
Procedure
- Run the display ipv6 routing-table vpn-instance vpn-instance-name statistics command to check the total number of route prefixes and the number of route prefixes of each protocol. Then run the display ipv6 routing-table limit command to check whether the number of IPv6 route prefixes in the VPN instance has exceeded the alarm threshold.
If the number of IPv6 route prefixes in the VPN instance has exceeded the alarm threshold, go to Step 2.
If the number of IPv6 route prefixes in the VPN instance has not exceeded the alarm threshold, go to Step 3.
- If the configured private network prefix threshold value is too small, run the prefix limit command in the IPv6 address family view of the VPN instance to reconfigure the threshold. Then check whether the fault is rectified.
If yes, go to step 4.
If no, go to step 3.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
- RM_1.3.6.1.4.1.2011.5.25.145.6.1 hwTunnelGroupUp
- RM_1.3.6.1.4.1.2011.5.25.145.6.2 hwTunnelGroupDown
- RM_1.3.6.1.4.1.2011.5.25.145.19.1.1 hwPublicIpv4PrefixExceed
- RM_1.3.6.1.4.1.2011.5.25.145.19.1.2 hwPublicIpv4PrefixExceedClear
- RM_1.3.6.1.4.1.2011.5.25.145.19.1.3 hwPublicIpv4PrefixThresholdExceed
- RM_1.3.6.1.4.1.2011.5.25.145.19.1.4 hwPublicIpv4PrefixThresholdExceedClear
- RM_1.3.6.1.4.1.2011.5.25.145.19.2.1 hwPublicIpv6PrefixExceed
- RM_1.3.6.1.4.1.2011.5.25.145.19.2.2 hwPublicIpv6PrefixExceedClear
- RM_1.3.6.1.4.1.2011.5.25.145.19.2.3 hwPublicIpv6PrefixThresholdExceed
- RM_1.3.6.1.4.1.2011.5.25.145.19.2.4 hwPublicIpv6PrefixThresholdExceedClear
- RM_1.3.6.1.4.1.2011.5.25.145.19.3.1 hwL3vpnIpv6PrefixExceed
- RM_1.3.6.1.4.1.2011.5.25.145.19.3.2 hwL3vpnIpv6PrefixExceedClear
- RM_1.3.6.1.4.1.2011.5.25.145.19.3.3 hwL3vpnIpv6PrefixThresholdExceed