Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 02-HH3C-DOMAIN-MIB | 212.89 KB |
Contents
hh3cUserIPLowerlimitWarningAlarm
hh3cUserIPLowerlimitWarningResume
hh3cUserNDRAPfAllocAlarmResume
hh3cUserNDRAPfLowlimitWarnAlarm
hh3cUserNDRAPfLowlimitWarnResume
hh3cUserPDPfLowlimitWarnResume
hh3cUserIPv6WebServerDownAlarm
hh3cUserIPv6WebServerChangeAlarm
HH3C-DOMAIN-MIB
About this MIB
Use this MIB to manage domains.
MIB file name
hh3c-domain.mib
Notifications
hh3cUserIPAllocAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.1 |
High IPv4 address usage alarm occurred in a domain. |
Error |
Major |
1.3.6.1.4.1.25506.2.46.5.0.2 (hh3cUserIPAllocAlarmResume) |
OFF |
Notification triggers
This notification is generated when the IPv4 address usage of a domain reaches or exceeds the high alarm threshold for the first time.
System impact
Address pools in the domain might be used up and new users cannot come online because of IP address obtaining failures.
Status control
ON
CLI: Use the snmp-agent trap enable domain ip-usage-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain ip-usage-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.5.1.6 (hh3cDomainIPUsedPercent) |
IPv4 address usage. |
hh3cDomainName |
STRING |
0..32 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.20 (hh3cDomainIPv4PoolUpperValue) |
High alarm threshold for IPv4 address usage. |
hh3cDomainName |
Integer32 |
1..100 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.21 (hh3cDomainIPv4PoolLowerValue) |
Low alarm threshold for IPv4 address usage. |
hh3cDomainName |
Integer32 |
0..99 |
Recommended action
1.In domain view, use display this to view the ip-usage-warning high-threshold configuration.
- If ip-usage-warning high-threshold is configured and the threshold value is in the range of 1 to 100 (excluded), proceed to step 2.
- If ip-usage-warning high-threshold is not configured or the threshold value is 100, proceed to step 4.
2.In any view, use display dhcp pool-usage and display dhcp pool-group-usage to view if the current IP address usage has reached the peak.
- If yes, proceed to step 3.
- If no, proceed to step 5.
3.Expand the range of the local address pool or address pool group , or configure new users to come online in other domains. Wait for 30 minutes and verify if the alarm can be generated again.
- If yes, proceed to step 4.
- If no, proceed to step 5.
4.Collect alarm, log, and configuration information, and contact Technical Support.
hh3cUserIPAllocAlarmResume
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.2 |
High IPv4 address usage alarm cleared in a domain. |
Recovery |
Major |
N/A (N/A) |
OFF |
Notification triggers
This recovery notification is generated when the IPv4 address usage drops below or reaches the value calculated by using the following formula: High alarm threshold – (high alarm threshold – low alarm threshold)*10%.
During calculation, the system uses value 0 for the low alarm threshold and 100 for the high alarm threshold when no low or high alarm threshold is set.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable domain ip-usage-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain ip-usage-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.5.1.6 (hh3cDomainIPUsedPercent) |
IPv4 address usage. |
hh3cDomainName |
STRING |
0..32 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.20 (hh3cDomainIPv4PoolUpperValue) |
High alarm threshold for IPv4 address usage. |
hh3cDomainName |
Integer32 |
1..100 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.21 (hh3cDomainIPv4PoolLowerValue) |
Low alarm threshold for IPv4 address usage. |
hh3cDomainName |
Integer32 |
0..99 |
Recommended action
No action is required.
hh3cUserIPLowerlimitWarningAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.3 |
Low IPv4 address usage alarm occurred in a domain. |
Error |
Warning |
1.3.6.1.4.1.25506.2.46.5.0.4 (hh3cUserIPLowerlimitWarningResume) |
OFF |
Notification triggers
This notification is generated when the IPv4 address usage of a domain reaches or drops below the low alarm threshold for the first time.
Possible reason 1: Users go offline and the IP usage in the domain drops below the lower threshold.
Possible reason 2: The lower threshold configured by using the ip-usage-warning low-threshold command is too high.
System impact
More clients might go offline unexpectedly.
Status control
ON
CLI: Use the snmp-agent trap enable domain ip-usage-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain ip-usage-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.5.1.6 (hh3cDomainIPUsedPercent) |
IPv4 address usage. |
hh3cDomainName |
STRING |
0..32 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.20 (hh3cDomainIPv4PoolUpperValue) |
High alarm threshold for IPv4 address usage. |
hh3cDomainName |
Integer32 |
1..100 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.21 (hh3cDomainIPv4PoolLowerValue) |
Low alarm threshold for IPv4 address usage. |
hh3cDomainName |
Integer32 |
0..99 |
Recommended action
1.Use the display this command in domain view to view the ip-usage-warning low-threshold configuration, and verify if the current lower threshold for the IP usage is proper.
- If the lower threshold is too high, proceed to step 2.
- If the lower threshold is proper, proceed to step 3.
2.Use the ip-usage-warning low-threshold command in domain view to adjust the lower threshold for the IP usage.
3.In any view, use the display dhcp pool-usage and display dhcp pool-group-usage commands to view the current IP usage.
- If the current IP usage drops below or is approaching the lower threshold, use the display aaa offline-record command to view the user disassociation reason records.
If the disassociation reason is User request, no action is required.
If the disassociation is not User request, contact Technical Support.
- If the current IP usage is not approaching the lower threshold, proceed to step 4.
4.Collect alarm, log, and configuration information, and contact Technical Support.
hh3cUserIPLowerlimitWarningResume
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.4 |
Low IPv4 address usage alarm cleared in a domain. |
Recovery |
Warning |
N/A (N/A) |
OFF |
Notification triggers
This notification is generated if the IP usage in the domain drops below or to the lower threshold minus the alarm gap.
Alarm gap=(Upper threshold–Lower threshold)*10%
If only the upper threshold is configured, the lower threshold value is 0 when calculating the alarm gap. If only the lower threshold is configured, the upper threshold value is 100 when calculating the alarm gap.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable domain ip-usage-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain ip-usage-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.5.1.6 (hh3cDomainIPUsedPercent) |
IPv4 address usage. |
hh3cDomainName |
STRING |
0..32 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.20 (hh3cDomainIPv4PoolUpperValue) |
High alarm threshold for IPv4 address usage. |
hh3cDomainName |
Integer32 |
1..100 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.21 (hh3cDomainIPv4PoolLowerValue) |
Low alarm threshold for IPv4 address usage. |
hh3cDomainName |
Integer32 |
0..99 |
Recommended action
No action is required.
hh3cUserIPv6AllocAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.7 |
Low IPv6 address usage alarm occurred in a domain. |
Error |
Warning |
1.3.6.1.4.1.25506.2.46.5.0.8 (hh3cUserIPv6LowlimitWarnResume) |
OFF |
Notification triggers
This notification is generated when the IPv6 address usage of a domain reaches or drops below the low alarm threshold for the first time.
Possible reason 1: Users go offline and the IPv6 usage in the domain drops below the lower threshold.
Possible reason 2: The lower threshold configured by using the ipv6-usage-warning low-threshold command is too high.
System impact
More clients might go offline unexpectedly.
Status control
ON
CLI: Use the snmp-agent trap enable domain ipv6-usage-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain ipv6-usage-warning command.
Objects
OID (object name)
Description
Index nodes
Type
Value range
1.3.6.1.4.1.25506.2.46.2.5.1.12 (hh3cDomainIPv6AddressUsedPercent)
IPv6 address usage.
hh3cDomainName
STRING
0..32
1.3.6.1.4.1.25506.2.46.2.1.1.22 (hh3cDomainIPv6PoolUpperValue)
High alarm threshold for IPv6 address usage.
hh3cDomainName
Integer32
1..100
1.3.6.1.4.1.25506.2.46.2.1.1.23 (hh3cDomainIPv6PoolLowerValue)
Low alarm threshold for IPv6 address usage.
hh3cDomainName
Integer32
0..99
Recommended action
In domain view, use the display this command to view the ipv6-usage-warning low-threshold configuration and verify if the current lower threshold for the IPv6 usage is proper.
If the lower threshold is too high, proceed to step 2.
If the lower threshold is proper, proceed to step 3.
In domain view, use the ipv6-usage-warning low-threshold command to adjust the lower threshold for the IPv6 usage.
In any view, use the display ipv6 dhcp pool-usage and display ipv6 dhcp pool-group-usage commands to view if the current IPv6 address usage has reached the peak.
If the current IPv6 usage drops below or is approaching the lower threshold, use the display aaa offline-record command to view the user disassociation reason records.
If the disassociation reason is User request, no action is required.
If the disassociation is not User request, contact Technical Support.
If the current IPv6 is not approaching the lower threshold, proceed to step 4.
Collect alarm, log, and configuration information, and contact Technical Support.
hh3cUserIPv6LowlimitWarnResume
Basic information
OID
Event
Type
Severity
Recovery notification
Default status
1.3.6.1.4.1.25506.2.46.5.0.8
Low IPv6 address usage alarm cleared in a domain.
Recovery
Warning
N/A
OFF
Notification triggers
This notification is generated if the IPv6 usage in the domain drops below or to the lower threshold minus the alarm gap.
Alarm gap=(Upper threshold–Lower threshold)*10%
If only the upper threshold is configured, the lower threshold value is 0 when calculating the alarm gap. If only the lower threshold is configured, the upper threshold value is 100 when calculating the alarm gap.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable domain ipv6-usage-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain ipv6-usage-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.5.1.12 (hh3cDomainIPv6AddressUsedPercent) |
IPv6 address usage. |
hh3cDomainName |
STRING |
0..32 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.22 (hh3cDomainIPv6PoolUpperValue) |
High alarm threshold for IPv6 address usage. |
hh3cDomainName |
Integer32 |
1..100 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.23 (hh3cDomainIPv6PoolLowerValue) |
Low alarm threshold for IPv6 address usage. |
hh3cDomainName |
Integer32 |
0..99 |
Recommended action
No action is required.
hh3cUserNDRAPfAllocAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.9 |
High NDRA prefix address usage alarm occurred in a domain. |
Error |
Major |
1.3.6.1.4.1.25506.2.46.5.0.10 (hh3cUserNDRAPfAllocAlarmResume) |
OFF |
Notification triggers
This notification is generated when the NDRA prefix usage of a domain reaches or exceeds the high alarm threshold for the first time.
System impact
The NDRA prefixes in the domain address pool may be exhausted, causing new users to be unable to go online because they cannot be assigned an NDRA prefix.
Status control
ON
CLI: Use the snmp-agent trap enable domain ipv6-usage-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain ipv6-usage-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.5.1.18 (hh3cDomainNDRAPrefixUsedPercent) |
NDRA prefix usage. |
hh3cDomainName |
STRING |
0..64 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.22 (hh3cDomainIPv6PoolUpperValue) |
High alarm threshold for NDRA prefix usage. |
hh3cDomainName |
Integer32 |
1..100 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.23 (hh3cDomainIPv6PoolLowerValue) |
Low alarm threshold for NDRA prefix usage. |
hh3cDomainName |
Integer32 |
0..99 |
Recommended action
1.In domain view, use the display this command to view the ipv6-usage-warning high-threshold configuration.
- If ipv6-usage-warning high-threshold is configured and the upper threshold value is in the range of 1 (1 included) to 100 (100 excluded), proceed to step 2.
- If ipv6-usage-warning high-threshold is not configured or the configured upper threshold is 100, proceed to step 4.
2.In any view, use the display ipv6 dhcp pool-usage and display ipv6 dhcp pool-group-usage commands to view if the current IPv6 address usage has reached the peak.
- If yes, proceed to step 3.
- If no, proceed to step 5.
3.Expand the range of the local address pool or address pool group, or configure new users to come online in other domains. Wait for 30 minutes and verify if the alarm can be generated again.
- If yes, proceed to step 4.
- If no, proceed to step 5.
4.Collect alarm, log, and configuration information, and contact Technical Support.
hh3cUserNDRAPfAllocAlarmResume
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.10 |
High NDRA prefix address usage alarm cleared in a domain. |
Recovery |
Major |
N/A (N/A) |
OFF |
Notification triggers
This recovery notification is generated when the NDRA prefix usage drops below or reaches the value calculated by using the following formula: High alarm threshold – (high alarm threshold – low alarm threshold)*10%.
During calculation, the system uses value 0 for the low alarm threshold and 100 for the high alarm threshold when no low or high alarm threshold is set.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable domain ipv6-usage-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain ipv6-usage-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.5.1.18 (hh3cDomainNDRAPrefixUsedPercent) |
NDRA prefix usage. |
hh3cDomainName |
STRING |
0..64 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.22 (hh3cDomainIPv6PoolUpperValue) |
High alarm threshold for NDRA prefix usage. |
hh3cDomainName |
Integer32 |
1..100 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.23 (hh3cDomainIPv6PoolLowerValue) |
Low alarm threshold for NDRA prefix usage. |
hh3cDomainName |
Integer32 |
0..99 |
Recommended action
No action is required.
hh3cUserNDRAPfLowlimitWarnAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.11 |
Low NDRA prefix address usage alarm occurred in a domain. |
Error |
Warning |
1.3.6.1.4.1.25506.2.46.5.0.12 (hh3cUserNDRAPfLowlimitWarnResume) |
OFF |
Notification triggers
This notification is generated when the NDRA prefix usage of a domain reaches or drops below the low alarm threshold for the first time.
Possible reason 1: Users go offline and the IPv6 NDRA prefix usage in the domain drops below the lower threshold.
Possible reason 2: The lower threshold configured by using the ipv6-usage-warning low-threshold command is too high.
System impact
If this alarm is triggered due to the lower threshold value set too high, it may cause more users to go offline abnormally.
Status control
ON
CLI: Use the snmp-agent trap enable domain ipv6-usage-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain ipv6-usage-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.5.1.18 (hh3cDomainNDRAPrefixUsedPercent) |
NDRA prefix usage. |
hh3cDomainName |
STRING |
0..32 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.22 (hh3cDomainIPv6PoolUpperValue) |
High alarm threshold for NDRA prefix usage. |
hh3cDomainName |
Integer32 |
1..100 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.23 (hh3cDomainIPv6PoolLowerValue) |
Low alarm threshold for NDRA prefix usage. |
hh3cDomainName |
Integer32 |
0..99 |
Recommended action
1.In domain view, use the display this command to view the ipv6-usage-warning low-threshold configuration and verify if the current lower threshold for the IPv6 usage is proper.
- If the lower threshold is too high, proceed to step 2.
- If the lower threshold is proper, proceed to step 3.
2.In domain view, use the ipv6-usage-warning low-threshold command to adjust the lower threshold for the IPv6 usage.
3.In any view, use the display ipv6 dhcp pool-usage and display ipv6 dhcp pool-group-usage commands to view the current IPv6 usage.
- If the current IPv6 usage drops below or is approaching the lower threshold, use the display aaa offline-record command to view the user disassociation reason records.
If the disassociation reason is User request, no action is required.
If the disassociation is not User request, contact Technical Support.
- If the current IPv6 is not approaching the lower threshold, proceed to step 4.
4.Collect alarm, log, and configuration information, and contact Technical Support.
hh3cUserNDRAPfLowlimitWarnResume
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.12 |
Low NDRA prefix address usage alarm cleared in a domain. |
Recovery |
Warning |
N/A (N/A) |
OFF |
Notification triggers
This recovery notification is generated when the NDRA prefix usage reaches or exceeds the value calculated by using the following formula: Low alarm threshold + (high alarm threshold – low alarm threshold)*10%.
During calculation, the system uses value 0 for the low alarm threshold and 100 for the high alarm threshold when no low or high alarm threshold is set.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable domain ipv6-usage-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain ipv6-usage-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.5.1.18 (hh3cDomainNDRAPrefixUsedPercent) |
NDRA prefix usage. |
hh3cDomainName |
STRING |
0..32 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.22 (hh3cDomainIPv6PoolUpperValue) |
High alarm threshold for NDRA prefix usage. |
hh3cDomainName |
Integer32 |
1..100 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.23 (hh3cDomainIPv6PoolLowerValue) |
Low alarm threshold for NDRA prefix usage. |
hh3cDomainName |
Integer32 |
0..99 |
Recommended action
No action is required.
hh3cUserPDPfAllocAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.13 |
High PD prefix address usage alarm occurred in a domain. |
Error |
Major |
1.3.6.1.4.1.25506.2.46.5.0.14 (hh3cUserPDPfAllocAlarmResume) |
OFF |
Notification triggers
This notification is generated when the PD prefix usage of a domain reaches or exceeds the high alarm threshold for the first time.
System impact
The DHCPv6-PD prefixes in the domain may be exhausted, causing new users to be unable to go online because they cannot be assigned a DHCPv6-PD address.
Status control
ON
CLI: Use the snmp-agent trap enable domain ipv6-usage-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain ipv6-usage-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.5.1.24 (hh3cDomainPDPrefixUsedPercent) |
PD prefix usage. |
hh3cDomainName |
STRING |
0..64 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.22 (hh3cDomainIPv6PoolUpperValue) |
High alarm threshold for PD prefix usage. |
hh3cDomainName |
Integer32 |
1..100 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.23 (hh3cDomainIPv6PoolLowerValue) |
Low alarm threshold for PD prefix usage. |
hh3cDomainName |
Integer32 |
0..99 |
Recommended action
1.In domain view, use the display this command to view the ipv6-usage-warning high-threshold configuration.
- If ipv6-usage-warning high-threshold is configured and the upper threshold value is in the range of 1 (1 included) to 100 (100 excluded), proceed to step 2.
- If ipv6-usage-warning high-threshold is not configured or the configured upper threshold is 100, proceed to step 4.
2.In any view, use the display ipv6 dhcp pool-usage and display ipv6 dhcp pool-group-usage commands to view if the current IPv6 address usage has reached the peak.
- If yes, proceed to step 3.
- If no, proceed to step 5.
3.Expand the range of the local address pool or address pool group, or configure new users to come online in other domains. Wait for 30 minutes and verify if the alarm can be generated again.
- If yes, proceed to step 4.
- If no, proceed to step 5.
4.Collect alarm, log, and configuration information, and contact Technical Support.
hh3cUserPDPfAllocAlarmResume
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.14 |
High PD prefix address usage alarm cleared in a domain. |
Recovery |
Major |
N/A (N/A) |
OFF |
Notification triggers
This recovery notification is generated when the PD prefix usage drops below or reaches the value calculated by using the following formula: High alarm threshold – (high alarm threshold – low alarm threshold)*10%.
During calculation, the system uses value 0 for the low alarm threshold and 100 for the high alarm threshold when no low or high alarm threshold is set.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable domain ipv6-usage-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain ipv6-usage-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.5.1.24 (hh3cDomainPDPrefixUsedPercent) |
PD prefix usage. |
hh3cDomainName |
STRING |
0..64 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.22 (hh3cDomainIPv6PoolUpperValue) |
High alarm threshold for PD prefix usage. |
hh3cDomainName |
Integer32 |
1..100 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.23 (hh3cDomainIPv6PoolLowerValue) |
Low alarm threshold for PD prefix usage. |
hh3cDomainName |
Integer32 |
0..99 |
Recommended action
No action is required.
hh3cUserPDPfLowlimitWarnAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.15 |
Low PD prefix address usage alarm occurred in a domain. |
Error |
Warning |
1.3.6.1.4.1.25506.2.46.5.0.16 (hh3cUserPDPfLowlimitWarnResume) |
OFF |
Notification triggers
This notification is generated when the PD prefix usage of a domain reaches or drops below the low alarm threshold for the first time.
Possible reason 1: Users go offline and the IPv6 DHCPv6-PD prefix usage in the domain drops below the lower threshold.
Possible reason 2: The lower threshold configured by using the ipv6-usage-warning low-threshold command is too high.
System impact
More clients might go offline unexpectedly.
Status control
ON
CLI: Use the snmp-agent trap enable domain ipv6-usage-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain ipv6-usage-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.5.1.24 (hh3cDomainPDPrefixUsedPercent) |
PD prefix usage. |
hh3cDomainName |
STRING |
0..32 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.22 (hh3cDomainIPv6PoolUpperValue) |
High alarm threshold for PD prefix usage. |
hh3cDomainName |
Integer32 |
1..100 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.23 (hh3cDomainIPv6PoolLowerValue) |
Low alarm threshold for PD prefix usage. |
hh3cDomainName |
Integer32 |
0..99 |
Recommended action
1.In domain view, use the display this command to view the ipv6-usage-warning low-threshold configuration and verify if the current lower threshold for the IPv6 usage is proper.
- If the lower threshold is too high, proceed to step 2.
- If the lower threshold is proper, proceed to step 3.
2.In domain view, use the ipv6-usage-warning low-threshold command to adjust the lower threshold for the IPv6 usage.
3.In any view, use the display ipv6 dhcp pool-usage and display ipv6 dhcp pool-group-usage commands to view the current IPv6 usage.
- If the current IPv6 usage drops below or is approaching the lower threshold, use the display aaa offline-record command to view the user disassociation reason records.
If the disassociation reason is User request, no action is required.
If the disassociation is not User request, contact Technical Support.
- If the current IPv6 is not approaching the lower threshold, proceed to step 4.
4.Collect alarm, log, and configuration information, and contact Technical Support.
hh3cUserPDPfLowlimitWarnResume
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.16 |
Low PD prefix address usage alarm cleared in a domain. |
Recovery |
Warning |
N/A (N/A) |
OFF |
Notification triggers
This recovery notification is generated when the PD prefix usage reaches or exceeds the value calculated by using the following formula: Low alarm threshold + (high alarm threshold – low alarm threshold)*10%.
During calculation, the system uses value 0 for the low alarm threshold and 100 for the high alarm threshold when no low or high alarm threshold is set.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable domain ipv6-usage-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain ipv6-usage-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.5.1.24 (hh3cDomainPDPrefixUsedPercent) |
PD prefix usage. |
hh3cDomainName |
STRING |
0..32 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.22 (hh3cDomainIPv6PoolUpperValue) |
High alarm threshold for PD prefix usage. |
hh3cDomainName |
Integer32 |
1..100 |
|
1.3.6.1.4.1.25506.2.46.2.1.1.23 (hh3cDomainIPv6PoolLowerValue) |
Low alarm threshold for PD prefix usage. |
hh3cDomainName |
Integer32 |
0..99 |
Recommended action
No action is required.
hh3cUserWebServerDownAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.17 |
The redirect URL of the Web server in a domain became unavailable. |
Error |
Major |
1.3.6.1.4.1.25506.2.46.5.0.18 (hh3cUserWebServerUpAlarm) |
OFF |
Notification triggers
This notification is generated when the state of the Web server IPv4 URL to which users are redirected changes from available to unavailable in an ISP domain.
Possible reason: The Web server is down or the connection is terminated.
System impact
User Web authentication fails.
Status control
ON
CLI: Use the snmp-agent trap enable domain web-server-url-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain web-server-url-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.1.1.30 (hh3cDomainActiveWebServerUrl) |
URL of the Web server. |
hh3cDomainName |
STRING |
0..255 |
Recommended action
1.Examine the operation status of the Web server.
2.If the Web server is down, contact the server administrator and bring up the server.
3.If no recovery alarm is generated after the Web server is up, troubleshoot network connection errors between the device and the Web server until the alarm is cleared.
hh3cUserWebServerUpAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.18 |
The redirect URL of the Web server in a domain became available. |
Recovery |
Major |
N/A (N/A) |
OFF |
Notification triggers
This notification is generated when the state of the IPv4 Web server URL to which users are redirected changes from unavailable to available in an ISP domain.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable domain web-server-url-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain web-server-url-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.1.1.30 (hh3cDomainActiveWebServerUrl) |
URL of the Web server. |
hh3cDomainName |
STRING |
0..255 |
Recommended action
No action is required.
hh3cUserWebServerChangeAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.19 |
The redirect URL of the Web server in a domain changed. |
Informational |
Warning |
N/A (N/A) |
OFF |
Notification triggers
This notification is generated when the IPv4 URL of the Web server changes in an ISP domain.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable domain web-server-url-warning command.
OFF
CLI: Use the undo snmp-agent trap enable domain web-server-url-warning command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.1.1.30 (hh3cDomainActiveWebServerUrl) |
Old URL of the Web server. |
hh3cDomainName |
STRING |
0..255 |
Recommended action
No action is required.
hh3cUserIPv6WebServerDownAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.20 |
The redirect IPv6 URL of the Web server in the domain becomes unavailable. |
Error |
Major |
1.3.6.1.4.1.25506.2.46.5.0.21 (hh3cUserIPv6WebServerUpAlarm) |
OFF |
Notification triggers
This notification is generated when the status of the IPv6 URL of the Web server redirected to users in the ISP domain changes from available to unavailable.
Possible reason: The Web server is down or the connection is terminated.
System impact
No negative impact on the system.
Status control
On
CLI: snmp-agent trap enable domain web-server-ipv6-url-warning
OFF
CLI: undo snmp-agent trap enable domain web-server-ipv6-url-warning
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.1.1.31 (hh3cDomainActiveWebServerIpv6Url) |
IPv6 URL of the Web server. |
hh3cDomainName |
STRING |
0..255 |
Recommended action
1.Examine the operation status of the Web server.
2.If the Web server is down, contact the server administrator and bring up the server.
3.If no recovery alarm is generated after the Web server is up, troubleshoot network connection errors between the device and the Web server until the alarm is cleared.
hh3cUserIPv6WebServerUpAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.21 |
The redirect IPv6 URL of the Web server in the domain becomes available. |
Recovery |
Major |
N/A (N/A) |
OFF |
Notification triggers
This notification is generated when the status of the IPv6 URL of the Web server redirected to users in the ISP domain changes from unavailable to available.
System impact
No negative impact on the system.
Status control
ON
CLI: snmp-agent trap enable domain web-server-ipv6-url-warning
OFF
CLI: undo snmp-agent trap enable domain web-server-ipv6-url-warning
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.1.1.31 (hh3cDomainActiveWebServerIpv6Url) |
IPv6 URL of the Web server. |
hh3cDomainName |
STRING |
0..255 |
Recommended action
No action is required.
hh3cUserIPv6WebServerChangeAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.46.5.0.22 |
The redirect IPv6 URL of the Web server in the domain changes. |
Informational |
Warning |
N/A (N/A) |
OFF |
Notification triggers
This notification is generated when the IPv6 URL of the Web server redirected to users in the ISP domain changes.
System impact
No negative impact on the system.
Status control
ON
CLI: snmp-agent trap enable domain web-server-ipv6-url-warning
OFF
CLI: undo snmp-agent trap enable domain web-server-ipv6-url-warning
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.46.2.1.1.31 (hh3cDomainActiveWebServerIpv6Url) |
IPv6 URL of the Web server. |
hh3cDomainName |
STRING |
0..255 |
Recommended action
No action is required.
