- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
06-HH3C-RADIUS-MIB | 107.12 KB |
Contents
hh3cRadiusAuthenticationServerUpTrap
hh3cRadiusAccountingServerUpTrap
hh3cRadiusAuthenticationServerDownTrap
hh3cRadiusAccountingServerDownTrap
hh3cRadiusAccCachePacketDiscard
HH3C-RADIUS-MIB
About this MIB
Use this MIB to obtain and configure RADIUS server settings.
MIB file name
hh3c-radius.mib
Notifications
hh3cRadiusAuthServerUpTrap
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.13.3.0.1 |
Authentication server up |
Recovery |
Warning |
N/A (N/A) |
OFF |
Notification triggers
This notification is generated when the status of an authentication server changes from blocked to active.
This notification cannot function correctly with SNMPv2 and later versions. It has been replaced with hh3cRadiusAuthenticationServerUpTrap (1.3.6.1.4.1.25506.2.13.3.0.4) in SNMPv2 and later versions.
The notification generated by the device for the RADIUS authentication server up event (if enabled) depends on the SNMP version for the event:
If SNMPv1 is specified for this event by using the radius trap-version v1 command, the device generates the hh3cRadiusAuthServerUpTrap (1.3.6.1.4.1.25506.2.13.3.0.1) notification.
If SNMPv2 is specified for this event by using the radius trap-version v2 command, the device generates the hh3cRadiusAuthenticationServerUpTrap (1.3.6.1.4.1.25506.2.13.3.0.4) notification.
System impact
No negative impact on services.
Status control
ON
CLI: Use both the snmp-agent trap enable radius authentication-server-up and radius trap-version v1 commands.
OFF
CLI: Use either the undo snmp-agent trap enable radius authentication-server-up command or the radius trap-version v2 command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.67.1.2.1.1.3.1.2 (radiusAuthServerAddress) |
IP address of an authentication server. |
radiusAuthServerIndex |
IP Address |
Standard MIB values. |
1.3.6.1.2.1.67.1.2.1.1.3.1.3 (radiusAuthClientServerPortNumber) |
Port number of the authentication server. |
radiusAuthServerIndex |
INTEGER |
1.. 65535 |
Recommended action
No action is required.
hh3cRadiusAccServerUpTrap
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.13.3.0.2 |
Accounting server up |
Recovery |
Warning |
N/A (N/A) |
OFF |
Notification triggers
This notification is generated when the status of an accounting server changes from blocked to active.
This notification cannot function correctly with SNMPv2 and later versions. It has been replaced with hh3cRadiusAccountingServerUpTrap (1.3.6.1.4.1.25506.2.13.3.0.5) in SNMPv2 and later versions.
The notification generated by the device for the RADIUS accounting server up event (if enabled) depends on the SNMP version for the event:
If SNMPv1 is specified for this event by using the radius trap-version v1 command, the device generates the hh3cRadiusAccServerUpTrap (1.3.6.1.4.1.25506.2.13.3.0.2) notification.
If SNMPv2 is specified for this event by using the radius trap-version v2 command, the device generates the hh3cRadiusAccountingServerUpTrap (1.3.6.1.4.1.25506.2.13.3.0.5) notification.
System impact
No negative impact on services.
Status control
ON
CLI: Use both the snmp-agent trap enable radius accounting-server-up and radius trap-version v1 commands.
OFF
CLI: Use either the undo snmp-agent trap enable radius accounting-server-up command or the radius trap-version v2 command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.67.2.2.1.1.3.1.2 (radiusAccServerAddress) |
IP address of an accounting server. |
radiusAuthServerIndex |
IP Address |
Standard MIB values. |
1.3.6.1.2.1.67.2.2.1.1.3.1.3 (radiusAccClientServerPortNumber) |
Port number of the accounting server. |
radiusAuthServerIndex |
INTEGER |
1.. 65535 |
Recommended action
No action is required.
hh3cRadiusAuthErrTrap
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.13.3.0.3 |
Authentication failure alarm threshold crossing. |
Informational |
Major |
N/A (N/A) |
OFF |
Notification triggers
This notification is generated when the ratio of the authentication failures to the total authentication requests reaches the authentication failure alarm threshold.
System impact
The system is might being attacked.
Status control
ON
CLI: Use the snmp-agent trap enable radius authentication-error-threshold command.
OFF
CLI: Use the undo snmp-agent trap enable radius authentication-error-threshold command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.67.1.2.1.1.3.1.2 (radiusAuthServerAddress) |
IP address of an authentication server. |
radiusAuthServerIndex |
IP Address |
Standard MIB values. |
1.3.6.1.2.1.67.1.2.1.1.3.1.3 (radiusAuthClientServerPortNumber) |
Port number of the authentication server. |
radiusAuthServerIndex |
INTEGER |
1.. 65535 |
Recommended action
To resolve this issue, contact the administrator for help.
hh3cRadiusAuthenticationServerUpTrap
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.13.3.0.4 |
Authentication server up |
Recovery |
Warning |
N/A (N/A) |
OFF |
Notification triggers
This notification is generated when the status of an authentication server changes from blocked to active.
This notification replaces hh3cRadiusAuthServerUpTrap (1.3.6.1.4.1.25506.2.13.3.0.1) in SNMPv2 and later versions.
The notification generated by the device for the RADIUS authentication server up event (if enabled) depends on the SNMP version for the event:
If SNMPv2 is specified for this event by using the radius trap-version v2 command, the device generates the hh3cRadiusAuthenticationServerUpTrap (1.3.6.1.4.1.25506.2.13.3.0.4) notification.
If SNMPv1 is specified for this event by using the radius trap-version v1 command, the device generates the hh3cRadiusAuthServerUpTrap (1.3.6.1.4.1.25506.2.13.3.0.1) notification.
System impact
No negative impact on services.
Status control
ON
CLI: Use both the snmp-agent trap enable radius authentication-server-up and radius trap-version v2 commands.
OFF
CLI: Use either the undo snmp-agent trap enable radius authentication-server-up command or the radius trap-version v1 command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.67.1.2.1.1.3.1.2 (radiusAuthServerAddress) |
IP address of an authentication server. |
radiusAuthServerIndex |
IP Address |
Standard MIB values. |
1.3.6.1.2.1.67.1.2.1.1.3.1.3 (radiusAuthClientServerPortNumber) |
Port number of the authentication server. |
radiusAuthServerIndex |
INTEGER |
1.. 65535 |
Recommended action
No action is required.
hh3cRadiusAccountingServerUpTrap
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.13.3.0.5 |
Accounting server up |
Recovery |
Warning |
N/A (N/A) |
OFF |
Notification triggers
This notification is generated when the status of an accounting server changes from blocked to active.
This notification replaces hh3cRadiusAccServerUpTrap (1.3.6.1.4.1.25506.2.13.3.0.2) in SNMPv2 and later versions.
The notification generated by the device for the RADIUS accounting server up event (if enabled) depends on the SNMP version for the event:
If SNMPv2 is specified for this event by using the radius trap-version v2 command, the device generates the hh3cRadiusAccountingServerUpTrap (1.3.6.1.4.1.25506.2.13.3.0.5) notification.
If SNMPv1 is specified for this event by using the radius trap-version v1 command, the device generates the hh3cRadiusAccServerUpTrap (1.3.6.1.4.1.25506.2.13.3.0.2) notification.
System impact
No negative impact on services.
Status control
ON
CLI: Use both the snmp-agent trap enable radius accounting-server-up and radius trap-version v2 commands.
OFF
CLI: Use either the undo snmp-agent trap enable radius accounting-server-up command or the radius trap-version v1 command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.67.2.2.1.1.3.1.2 (radiusAccServerAddress) |
IP address of an accounting server. |
radiusAuthServerIndex |
IP Address |
Standard MIB values. |
1.3.6.1.2.1.67.2.2.1.1.3.1.3 (radiusAccClientServerPortNumber) |
Port number of the accounting server. |
radiusAuthServerIndex |
INTEGER |
1.. 65535 |
Recommended action
No action is required.
hh3cRadiusAuthenticationServerDownTrap
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.13.3.0.6 |
Authentication server down |
Error |
Major |
1.3.6.1.4.1.25506.2.13.3.0.4 (hh3cRadiusAuthenticationServerUpTrap) |
OFF |
Notification triggers
This notification is generated when the status of an authentication server changes from active to blocked.
This notification replaces hh3cRadiusAuthServerDownTrap (1.3.6.1.4.1.25506.2.13.3.1) in SNMPv2 and later versions.
The notification generated by the device for the RADIUS authentication server down event (if enabled) depends on the SNMP version for the event:
If SNMPv2 is specified for this event by using the radius trap-version v2 command, the device generates the hh3cRadiusAuthenticationServerDownTrap (1.3.6.1.4.1.25506.2.13.3.0.6) notification.
If SNMPv1 is specified for this event by using the radius trap-version v1 command, the device generates the hh3cRadiusAuthServerDownTrap (1.3.6.1.4.1.25506.2.13.3.1) notification.
System impact
If no secondary authentication servers exist, users cannot perform authentication to come online.
Status control
ON
CLI: Use both the snmp-agent trap enable radius authentication-server-down and radius trap-version v2 commands.
OFF
CLI: Use either the undo snmp-agent trap enable radius authentication-server-down command or the radius trap-version v1 command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.67.1.2.1.1.3.1.2 (radiusAuthServerAddress) |
IP address of an authentication server. |
radiusAuthServerIndex |
IP Address |
Standard MIB values. |
1.3.6.1.2.1.67.1.2.1.1.3.1.3 (radiusAuthClientServerPortNumber) |
Port number of the authentication server. |
radiusAuthServerIndex |
INTEGER |
1.. 65535 |
Recommended action
To resolve this issue:
1.Use the display interface command to view whether the interface connected to the authentication server is up:
- If no, troubleshoot the physical link.
- If yes, go to step 2.
2.Use the ping command to check whether the RADIUS server is reachable:
- If no, first check the network reachability between the device and the RADIUS server, and then check whether firewalls exist in the network. Make sure the RADIUS server is reachable.
- If yes, go to step 3.
3.Use the display current-configuration command to view whether the RADIUS server's configurations are correct:
- If no, modify the RADIUS server's configurations. For more information about RADIUS server configurations, see AAA commands in Security Command Reference and AAA configuration in Security Configuration Guide of the device.
- If yes, go to step 4.
4.Collect alarm information, log messages, and configuration data, and then contact H3C Support for help.
hh3cRadiusAccountingServerDownTrap
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.13.3.0.7 |
Accounting server down |
Error |
Major |
1.3.6.1.4.1.25506.2.13.3.0.5 (hh3cRadiusAccountingServerUpTrap) |
OFF |
Notification triggers
This notification is generated when the status of an accounting server changes from active to blocked.
This notification replaces hh3cRadiusAccServerDownTrap (1.3.6.1.4.1.25506.2.13.3.2) in SNMPv2 and later versions.
The notification generated by the device for the RADIUS accounting server down event (if enabled) depends on the SNMP version for the event:
If SNMPv2 is specified for this event by using the radius trap-version v2 command, the device generates the hh3cRadiusAccountingServerDownTrap (1.3.6.1.4.1.25506.2.13.3.0.7) notification.
If SNMPv1 is specified for this event by using the radius trap-version v1 command, the device generates the hh3cRadiusAccServerDownTrap (1.3.6.1.4.1.25506.2.13.3.2) notification.
System impact
The server is unreachable and users cannot come online.
Status control
ON
CLI: Use both the snmp-agent trap enable radius accounting-server-down and radius trap-version v2 commands.
OFF
CLI: Use either the undo snmp-agent trap enable radius accounting-server-down command or the radius trap-version v1 command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.67.2.2.1.1.3.1.2 (radiusAccServerAddress) |
IP address of an accounting server. |
radiusAuthServerIndex |
IP Address |
Standard MIB values. |
1.3.6.1.2.1.67.2.2.1.1.3.1.3 (radiusAccClientServerPortNumber) |
Port number of an accounting server. |
radiusAuthServerIndex |
INTEGER |
1.. 65535 |
Recommended action
To resolve this issue:
1.Use the display interface command to view whether the interface connected to the accounting server is up:
- If no, troubleshoot the physical link.
- If yes, go to step 2.
2.Use the ping command to check whether the RADIUS server is reachable:
- If no, first check the network reachability between the device and the RADIUS server, and then check whether firewalls exist in the network. Make sure the RADIUS server is reachable.
- If yes, go to step 3.
3.Use the display current-configuration command to view whether the RADIUS server's configurations are correct:
- If no, modify the RADIUS server's configurations. For more information about RADIUS server configurations, see AAA commands in Security Command Reference and AAA configuration in Security Configuration Guide of the device.
- If yes, go to step 4.
4.Collect alarm information, log messages, and configuration data, and then contact H3C Support for help.
hh3cRadiusAuthServerDownTrap
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.13.3.1 |
Authentication server down |
Error |
Major |
1.3.6.1.4.1.25506.2.13.3.0.1 (hh3cRadiusAuthServerUpTrap) |
OFF |
Notification triggers
This notification is generated when the status of an authentication server changes from active to blocked.
This notification cannot function correctly with SNMPv2 and later versions. It has been replaced with hh3cRadiusAuthenticationServerDownTrap (1.3.6.1.4.1.25506.2.13.3.0.6) in SNMPv2 and later versions.
The notification generated by the device for the RADIUS authentication server down event (if enabled) depends on the SNMP version for the event:
If SNMPv1 is specified for this event by using the radius trap-version v1 command, the device generates the hh3cRadiusAuthServerDownTrap (1.3.6.1.4.1.25506.2.13.3.1) notification.
If SNMPv2 is specified for this event by using the radius trap-version v2 command, the device generates the hh3cRadiusAuthenticationServerDownTrap (1.3.6.1.4.1.25506.2.13.3.0.6) notification.
System impact
If no secondary authentication servers exist, users cannot perform authentication to come online.
Status control
ON
CLI: Use both the snmp-agent trap enable radius authentication-server-down and radius trap-version v1 commands.
OFF
CLI: Use either the undo snmp-agent trap enable radius authentication-server-down command or the radius trap-version v2 command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.67.1.2.1.1.3.1.2 (radiusAuthServerAddress) |
IP address of an authentication server. |
radiusAuthServerIndex |
IP Address |
Standard MIB values. |
1.3.6.1.2.1.67.1.2.1.1.3.1.3 (radiusAuthClientServerPortNumber) |
Port number of the authentication server. |
radiusAuthServerIndex |
INTEGER |
1.. 65535 |
Recommended action
To resolve this issue:
1.Use the display interface command to view whether the interface connected to the authentication server is up:
- If no, troubleshoot the physical link.
- If yes, go to step 2.
2.Use the ping command to check whether the RADIUS server is reachable:
- If no, first check the network reachability between the device and the RADIUS server, and then check whether firewalls exist in the network. Make sure the RADIUS server is reachable.
- If yes, go to step 3.
3.Use the display current-configuration command to view whether the RADIUS server's configurations are correct:
- If no, modify the RADIUS server's configurations. For more information about RADIUS server configurations, see AAA commands in Security Command Reference and AAA configuration in Security Configuration Guide of the device.
- If yes, go to step 4.
4.Collect alarm information, log messages, and configuration data, and then contact H3C Support for help.
hh3cRadiusAccServerDownTrap
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.13.3.2 |
Accounting server down |
Error |
Major |
1.3.6.1.4.1.25506.2.13.3.0.2 (hh3cRadiusAccServerUpTrap) |
OFF |
Notification triggers
This notification is generated when the status of an accounting server changes from active to blocked.
This notification cannot function correctly with SNMPv2 and later versions. It has been replaced with hh3cRadiusAccountingServerDownTrap (1.3.6.1.4.1.25506.2.13.3.0.7) in SNMPv2 and later versions.
The notification generated by the device for the RADIUS accounting server down event (if enabled) depends on the SNMP version for the event:
If SNMPv1 is specified for this event by using the radius trap-version v1 command, the device generates the hh3cRadiusAccServerDownTrap (1.3.6.1.4.1.25506.2.13.3.2) notification.
If SNMPv2 is specified for this event by using the radius trap-version v2 command, the device generates the hh3cRadiusAccountingServerDownTrap (1.3.6.1.4.1.25506.2.13.3.0.7) notification.
System impact
The server is unreachable and users cannot come online.
Status control
ON
CLI: Use both the snmp-agent trap enable radius accounting-server-down and radius trap-version v1 commands.
OFF
CLI: Use either the undo snmp-agent trap enable radius accounting-server-down command or the radius trap-version v2 command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.67.2.2.1.1.3.1.2 (radiusAccServerAddress) |
IP address of an accounting server. |
radiusAuthServerIndex |
IP Address |
Standard MIB values. |
1.3.6.1.2.1.67.2.2.1.1.3.1.3 (radiusAccClientServerPortNumber) |
Port number of an accounting server. |
radiusAuthServerIndex |
INTEGER |
1.. 65535 |
Recommended action
To resolve this issue:
1.Use the display interface command to view whether the interface connected to the accounting server is up:
- If no, troubleshoot the physical link.
- If yes, go to step 2.
2.Use the ping command to check whether the RADIUS server is reachable:
- If no, first check the network reachability between the device and the RADIUS server, and then check whether firewalls exist in the network. Make sure the RADIUS server is reachable.
- If yes, go to step 3.
3.Use the display current-configuration command to view whether the RADIUS server's configurations are correct:
- If no, modify the RADIUS server's configurations. For more information about RADIUS server configurations, see AAA commands in Security Command Reference and AAA configuration in Security Configuration Guide of the device.
- If yes, go to step 4.
4.Collect alarm information, log messages, and configuration data, and then contact H3C Support for help.
hh3cRadiusAccCacheAlarm
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.13.8.0.1 |
The ratio of the number of buffered stop-accounting packets to the max number allowed reached the upper threshold. |
Error |
Warning |
1.3.6.1.4.1.25506.2.13.8.0.2 (hh3cRadiusAccCacheResume) |
OFF |
Notification triggers
This notification is generated when the ratio of the number of buffered stop-accounting packets to the allowed max number configured by using the radius stop-accounting-buffer cache command reaches the upper threshold.
System impact
No negative impact on services currently. If the number of buffered stop-accounting packets reaches the allowed max number, the device processes new stop-accounting requests according to whether you have configured the radius stop-accounting-buffer overwrite-oldest command in system view for new stop-accounting request overwriting.
If you have configured the command, the device uses a new stop-accounting request to overwrite the oldest one.
If you have not configured the command, the device stops buffering new stop-accounting requests and new stop-accounting requests are dropped.
Status control
ON
CLI: Use the snmp-agent trap enable radius accounting-cache-upper-threshold command.
OFF
CLI: Use the undo snmp-agent trap enable radius accounting-cache-upper-threshold command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.4.1.25506.2.13.8.1.1 (hh3cRadiusAccCacheMaxPackets) |
Allowed maximum number of stop-accounting packets that can be buffered. |
N/A |
Integer32 |
256..2147483647 |
1.3.6.1.4.1.25506.2.13.8.1.2 (hh3cRadiusAccCacheUpperValue) |
Upper threshold for the ratio of the number of buffered stop-accounting packets to the maximum number allowed, in percentage. |
N/A |
Integer32 |
1..100 |
Recommended action
To resolve this issue:
1.Check whether the set upper threshold for stop-accounting request buffering is appropriate:
- If yes, go to step 2.
- If no, use the radius stop-accounting-buffer warning-threshold command in system view to set the upper threshold to a higher value as needed, and then go to step 2.
2.Use the test-aaa command in user view to test whether communication failures exist between the device and the RADIUS server:
- If the test succeeds, it indicates that the RADIUS server is reachable. Go to step 3.
- If the test fails, troubleshoot the link between the device and the server. If the issue persists when the link is normal, go to step 3.
3.Collect alarm information, log messages, and configuration data, and then contact H3C Support for help.
hh3cRadiusAccCacheResume
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.13.8.0.2 |
The ratio of the number of buffered stop-accounting packets to the max number allowed dropped below the lower threshold. |
Recovery |
Warning |
N/A (N/A) |
OFF |
Notification triggers
This notification is generated when the ratio of the number of buffered stop-accounting packets to the allowed max number configured by using the radius stop-accounting-buffer cache command drops below the lower threshold.
System impact
No negative impact on services.
Status control
ON
CLI: Use the snmp-agent trap enable radius accounting-cache-lower-threshold command.
OFF
CLI: Use the undo snmp-agent trap enable radius accounting-cache-lower-threshold command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.4.1.25506.2.13.8.1.1 (hh3cRadiusAccCacheMaxPackets) |
Allowed maximum number of stop-accounting packets that can be buffered. |
N/A |
Integer32 |
256..2147483647 |
1.3.6.1.4.1.25506.2.13.8.1.3 (hh3cRadiusAccCacheLowerValue) |
Lower threshold for the ratio of the number of buffered stop-accounting packets to the maximum number allowed, in percentage. |
N/A |
Integer32 |
0..99 |
Recommended action
No action is required.
hh3cRadiusAccCachePacketDiscard
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.13.8.0.3 |
The system dropped buffered stop-accounting packets or stop-accounting packets to be buffered after the memory usage reached the minor alarm threshold. |
Informational |
Major |
N/A (N/A) |
OFF |
Notification triggers
This notification is generated when the system drops buffered stop-accounting packets or stop-accounting packets to be buffered after the memory usage reaches the minor alarm threshold.
System impact
The device processes stop-accounting packets according to whether you have configured the radius stop-accounting-buffer memory-minor-threshold overwrite-oldest command. If you have configured this command, the device uses a new stop-accounting request to overwrite the oldest one. Otherwise, the device stops buffering new stop-accounting requests. After the link between the device and the server recovers, some users might fail to go offline in time.
Status control
ON
CLI: Use the snmp-agent trap enable radius accounting-cache-discard command.
OFF
CLI: Use the undo snmp-agent trap enable radius accounting-cache-discard command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.4.1.25506.2.13.8.1.4 (hh3cRadiusAccCacheMemoryUsage) |
Current memory usage, in percentage. |
N/A |
Integer32 |
0..100 |
1.3.6.1.4.1.25506.2.13.8.1.5 (hh3cRadiusAccCachePackets) |
Number of stop-accounting packets that have been buffered. |
N/A |
Integer32 |
256..2147483647 |
Recommended action
To resolve this issue:
1.Use the display memory-threshold command in any view to check whether the memory usage of the MPU reaches the minor memory alarm threshold:
- If yes, go to step 2.
- If no, go to step 5.
2.Check whether the configured minor memory alarm threshold is low:
- If yes, use the memory-threshold command in system view to set the minor memory alarm threshold to a higher value as needed.
- If no, go to step 3.
3.Use the radius stop-accounting-buffer cache command in system view to set the maximum number of stop-accounting requests allowed to a smaller value so as to reduce resource consumption caused by buffered RADIUS stop-accounting requests. Then go to step 4.
4.Use the test-aaa command in user view to test whether communication failures exist between the device and the RADIUS server:
- If the test succeeds, it indicates that the RADIUS server is reachable. Go to step 5.
- If the test fails, troubleshoot the link between the device and the server. If the issue persists when the link is normal, go to step 5.
5.Collect alarm information, log messages, and configuration data, and then contact H3C Support for help.