BRASAM_1.3.6.1.4.1.2011.6.8.2.2.0.23 hwIPPoolDAPReleaseUnsuccessful

Trap Buffer Description

Fail to release an address segment.(PoolName=[PoolName],Subnet=[Subnet],Mask=[Mask],Reason=[Reason])

Fail to release an address segment.

In VS mode, this trap is supported only by the admin VS.

This alarm is supported only on NetEngine 8000 F1A.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Warning
Mnemonic Code	hwIPPoolDAPReleaseUnsuccessful
Trap OID	1.3.6.1.4.1.2011.6.8.2.2.0.23
MIB	HUAWEI-IPPOOL-MIB
Alarm ID	This is an event trap and does not involve alarm ID.
Alarm Name	This is an event trap and does not involve alarm name.
Alarm Type	This is an event trap and does not involve alarm type.
Raise or Clear	This is an event trap and does not involve alarm generation or clearance.
Match trap	-

Trap Buffer Parameters

Parameter	Description
PoolName	Name of the global address pool.
Subnet	Subnet address being applied for. If address segment allocation fails, the subnet address is all Fs. If address segment allocation succeeds but the allocated address segment conflicts with the local one, the subnet address is the actual one.
Mask	Subnet gateway mask.
Reason	Causes for address segment releasing failures. The value can be: 1. The server failed to respond.
PoolIndex	Address pool index.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.6.8.1.1.1.2	hwIPPoolName	hwIPPoolIndex
1.3.6.1.4.1.2011.6.8.1.1.1.3	hwIPPoolRouterIPAddr	hwIPPoolIndex
1.3.6.1.4.1.2011.6.8.1.1.1.4	hwIPPoolRouterIPMask	hwIPPoolIndex
1.3.6.1.4.1.2011.6.8.2.1.8	hwIPPoolDAPReason	-

Impact on the System

The BRAS releases the address segment locally, but the server still considers the address segment being used because it fails to receive the request for releasing the address segment. As a result, the address segment cannot be allocated to another client, wasting address segment resources.

Possible Causes

The server failed to respond.

Procedure

1.Perform the following steps to check whether the RADIUS server is unavailable or the response times out. If so, select another RADIUS server, then go to Step 2. If not, go to Step 3.

a.Run the ping command to check the link connectivity of the RADIUS server. If the link is faulty, rectify the link fault.

b.If the link is running properly, check whether the link is busy. Run the test-aaa command to check the interval between packet sending and receiving. If the interval is greater than 30s, the link is busy. An interval of over 2 minutes will result in an address segment application timeout.

2.Check whether the alarm is cleared.

If the alarm persists, go to Step 3.
If the alarm is cleared, go to Step 4.

3.Collect trap, log, and configuration information, and contact technical support personnel.

4.End.