- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
01-HH3C-AAA-MIB | 68.88 KB |
Contents
HH3C-AAA-MIB
About this MIB
Use this MIB to manage AAA.
MIB file name
hh3c-aaa.mib
Notifications
hh3cAAAUserSlotMaxNum
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.181.1.2.0.1 |
Maximum number of online users on a slot reached. |
Fault |
Major |
1.3.6.1.4.1.25506.2.181.1.2.0.2 (hh3cAAAUserSlotMaxNumResume) |
OFF |
Notification triggers
Possible reason 1: This notification is generated when the number of online users on a slot reaches the maximum number of online users on the slot.
Possible reason 2: The configured alarm threshold for access users per module is too low.
System impact
The number of users on the module has reached the threshold, which may result in new users failing to come online from the module.
Status control
ON
CLI: Use the snmp-agent trap enable slot-user-warning-threshold command.
OFF
CLI: Use the undo snmp-agent trap enable slot-user-warning-threshold command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.4.1.25506.2.181.1.1.1.1 (hh3cAAAUserChassis) |
Chassis number. |
N/A |
Integer32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.181.1.1.1.2 (hh3cAAAUserSlot) |
Slot number. |
N/A |
Integer32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.181.1.1.1.3 (hh3cAAAUserSlotMaxNumThreshold) |
Maximum number of online users on the slot. |
N/A |
Integer32 |
Standard MIB values. |
Recommended action
For an integrated device:
1.Use the display this command in system view to view the configured user resource alarm threshold (slot-user-warning-threshold) and verify if the threshold is too low.
- If the threshold is too low, set a higher threshold.
- If the threshold is proper, proceed to step 2.
2.Use the display access-user command in system view to view the number of online users. If the number is close to the maximum supported user quantity, replace the module with one that supports more users or configure new users to come online from a relatively idle module. If the issue persists, proceed to step 3.
3.Collect alarm, log, and configuration information, and contact Technical Support.
For a vBRAS-CP device, if a UP-VM sends this notification:
4.Use the display this command in system view or UP-manage view to view the configured user resource alarm threshold (slot-user-warning-threshold) and verify if the threshold is too low.
- If the threshold is too low, set a higher threshold.
- If the threshold is proper, proceed to step 2.
5.Use the display access-user command in system view to view the number of online users. If the number is close to the maximum supported user quantity, replace the module with one that supports more users or configure new users to come online from a relatively idle module. If the issue persists, proceed to step 3.
6.Collect alarm, log, and configuration information, and contact Technical Support.
For a vBRAS-CP device, if a BRAS-VM sends this notification:
7.Use the display this command in system view to view the configured user resource alarm threshold (access-user bras-vm user-warning-threshold) and verify if the threshold is too low.
- If the threshold is too low, set a higher threshold.
- If the threshold is proper, proceed to step 2.
8.Use the display access-user command in system view to view the number of online users. If the number is close to the maximum supported user quantity, replace the module with one that supports more users or configure new users to come online from a relatively idle module. If the issue persists, proceed to step 3.
9.Collect alarm, log, and configuration information, and contact Technical Support.
hh3cAAAUserSlotMaxNumResume
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.181.1.2.0.2 |
The alarm that the maximum number of online users on a slot reached was cleared. |
Recovery |
Major |
N/A (N/A) |
OFF |
Notification triggers
This notification is generated when the number of online users on a slot drops below 90 percent of the maximum number of online users on the slot.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable slot-user-warning-threshold command.
OFF
CLI: Use the undo snmp-agent trap enable slot-user-warning-threshold command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.4.1.25506.2.181.1.1.1.1 (hh3cAAAUserChassis) |
Chassis number. |
N/A |
Integer32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.181.1.1.1.2 (hh3cAAAUserSlot) |
Slot number. |
N/A |
Integer32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.181.1.1.1.3 (hh3cAAAUserSlotMaxNumThreshold) |
Maximum number of online users on the slot. |
N/A |
Integer32 |
Standard MIB values. |
Recommended action
No action is required.
hh3cAAAUserCpuMaxNum
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.181.1.2.0.3 |
Maximum number of online users on a CPU reached. |
Fault |
Major |
1.3.6.1.4.1.25506.2.181.1.2.0.4 (hh3cAAAUserCpuMaxNumResume) |
OFF |
Notification triggers
Possible reason 1: This notification is generated when the number of online users on a CPU reaches the maximum number. The number of CPU users represents the maximum number of users supported by the device driver chip.
Possible reason 2: The configured upper alarm threshold for access users per module is too low.
System impact
When the number of CPU users reaches the threshold, it may cause failures for subsequent users to come online.
Status control
ON
CLI: Use the snmp-agent trap enable slot-user-warning-threshold command.
OFF
CLI: Use the undo snmp-agent trap enable slot-user-warning-threshold command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.4.1.25506.2.181.1.1.1.1 (hh3cAAAUserChassis) |
Chassis number. |
N/A |
Integer32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.181.1.1.1.2 (hh3cAAAUserSlot) |
Slot number. |
N/A |
Integer32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.181.1.1.1.4 (hh3cAAAUserCpu) |
CPU number |
N/A |
Integer32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.181.1.1.1.5 (hh3cAAAUserCpuMaxNumThreshold) |
Maximum number of online users supported by the CPU. |
N/A |
Integer32 |
Standard MIB values. |
Recommended action
For an integrated device:
1.Use the display this command in system view to view the configured user resource alarm threshold (slot-user-warning-threshold) and verify if the threshold is too low.
- If the threshold is too low, set a higher threshold.
- If the threshold is proper, proceed to step 2.
2.Use the display access-user command in system view to view the number of online users. If the number is close to the maximum supported user quantity, replace the module with one that supports more users or configure new users to come online from a relatively idle module. If the issue persists, proceed to step 3.
3.Collect alarm, log, and configuration information, and contact Technical Support.
For a vBRAS-CP device, if a UP-VM sends this notification:
4.Use the display this command in system view or UP-manage view to view the configured user resource alarm threshold (slot-user-warning-threshold) and verify if the threshold is too low.
- If the threshold is too low, set a higher threshold.
- If the threshold is proper, proceed to step 2.
5.Use the display access-user command in system view to view the number of online users. If the number is close to the maximum supported user quantity, replace the module with one that supports more users or configure new users to come online from a relatively idle module. If the issue persists, proceed to step 3.
6.Collect alarm, log, and configuration information, and contact Technical Support.
hh3cAAAUserCpuMaxNumResume
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.181.1.2.0.4 |
Number of online users on a CPU drops to 90% of the maximum number. |
Recovery |
Major |
- |
OFF |
Notification triggers
This notification is generated when the number of online users on a CPU drops to 90% of the maximum number.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable slot-user-warning-threshold command.
OFF
CLI: Use the undo snmp-agent trap enable slot-user-warning-threshold command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.4.1.25506.2.181.1.1.1.1 (hh3cAAAUserChassis) |
Chassis number. |
N/A |
Integer32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.181.1.1.1.2 (hh3cAAAUserSlot) |
Slot number. |
N/A |
Integer32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.181.1.1.1.4 (hh3cAAAUserCpu) |
CPU number. |
N/A |
Integer32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.181.1.1.1.5 (hh3cAAAUserCpuMaxNumThreshold) |
Maximum number of online users supported by the CPU. |
N/A |
Integer32 |
Standard MIB values. |
Recommended action
No action is required.
hh3cAAAAdminLoginFailed
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.181.1.2.0.5 |
Number of login failures of an admin user reaches the alarm threshold within a specific period. |
Fault |
Major |
1.3.6.1.4.1.25506.2.181.1.2.0.6 (hh3cAAAAdminLoginFailedClear) |
OFF |
Notification triggers
This notification is sent when the number of login failures of a management user reaches the upper alarm threshold for the first time, or increases from a value lower than the recovery threshold to a value higher than the upper threshold during a statistics collection period. You can use the aaa login-failed alarm-threshold command to configure the threshold and the statistics collection period.
System impact
The system may be under login attacks.
Status control
ON
CLI: Use the snmp-agent trap enable aaa login-failed-threshold command.
OFF
CLI: Use the undo snmp-agent trap enable aaa login-failed-threshold command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.4.1.25506.2.181.1.1.1.6 (hh3cAAALoginFailedTimes) |
Number of login failures. |
N/A |
Integer32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.181.1.1.1.7 (hh3cAAAStatisticPeriod) |
Alarm period. |
N/A |
Integer32 |
Standard MIB values. |
Recommended action
The system might be under attack. Contact the network administrator.
hh3cAAAAdminLoginFailedClear
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.181.1.2.0.6 |
Number of login failures of an admin user drops below the alarm clearing threshold within a specific period. |
Recovery |
Major |
- |
OFF |
Notification triggers
This notification is sent when the number of login failures of a management user drops from a value higher than or equal to the upper alarm threshold to a value lower than the recovery threshold. You can use the aaa login-failed alarm-threshold command to configure the threshold and the statistics collection period.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable aaa login-failed-threshold command.
OFF
CLI: Use the undo snmp-agent trap enable aaa login-failed-threshold command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.4.1.25506.2.181.1.1.1.6 (hh3cAAALoginFailedTimes) |
Number of login failures. |
N/A |
Integer32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.181.1.1.1.7 (hh3cAAAStatisticPeriod) |
Alarm threshold. |
N/A |
Integer32 |
Standard MIB values. |
Recommended action
No action is required.