BRASAM/4/hwIPPoolDAPApplyUnsuccessful
Message
BRASAM/4/hwIPPoolDAPApplyUnsuccessful: Fail to apply for the address segment.(PoolName=[PoolName],Subnet=[Subnet],Mask=[Mask],Reason=[Reason])
In VS mode, this log is supported only by the admin VS.
Parameters
| Parameter Name | Parameter Meaning |
|---|---|
|
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 allocation failures,The value can be: 1. The server failed to respond. 2. The server rejected the application. 3. The server did not have addresses available for allocation. 4. The server allocated an invalid address. 5. The address allocated by the server conflicted with an existing address on the device. 6. The number of addresses on the device reached the maximum number allowed. |
Possible Causes
Cause 1: The server failed to respond. Cause 2: The server rejected the application. Cause 3: The server did not have addresses available for allocation. Cause 4: The server allocated an invalid address. Cause 5: The address allocated by the server conflicted with a existing address on the device. Cause 6: The number of addresses on the device reached the maximum number allowed.
Procedure
1. Determine the alarm cause based on the value of the Reason field in the alarm.
- If the value is "The server failed to respond", go to Step 2.
- If the value is "The server rejected the application", go to Step 3.
- If the value is "The server did not have addresses available for allocation", go to Step 4.
- If the value is "The server allocated an invalid address", go to Step 5.
- If the value is "The address allocated by the server conflicted with a existing address on the device", go to Step 6.
- If the value is "The number of addresses on the device reached the maximum number allowed", go to Step 7.
2. Perform the following steps to pinpoint the cause why the server does not respond, rectify the link fault, or reselect a RADIUS server.
- Run the ping command to check whether the link to the RADIUS server is normal.If the link cannot be pinged, rectify the link fault.
- If the link is normal, check whether the RADIUS link is busy.Run the test-aaa command to check the interval between packet sending and receiving.If the interval exceeds 30 seconds, the link is busy. If the interval exceeds 2 minutes, address segment application times out.
3. Perform the following steps to locate the reason why the server fails to respond.
- Check whether the corresponding user information exists on the server.
- If the user information exists, check whether the username and password configured on the device are the same as those on the server.
4. Check whether the server has an address segment. If no address segment is available, re-plan the server address allocation.
5. Perform the following steps to locate the reason why the address segment returned by the server is invalid and re-plan the server address allocation.
- Run the display ip pool dynamic command to check the Total field. Check whether the number of delivered address segments exceeds the system specification (4096).
- Check whether the number of addresses in the delivered address segment exceeds the upper limit (65536) based on the Subnet and Mask parameters in the current alarm.The number of addresses in the delivered address segment is calculated as follows: (2^32-mask length) – Number of addresses from the start address of the network segment to the Subnet + 1.For example, if Subnet is 10.0.0.5 and Mask is 255.0.0.0 (that is, the start IP address of the network segment is 10.0.0.0), the number of IP addresses in the network segment is (2^32-8) - 6 + 1 = 16777211.
6. Check whether the address segment in the current alarm overlaps with or contains the address segment of the current device. If yes, replan the address segment.Method: Run the display ip routing-table ip-address mask command to check whether the route of the current address segment exists on the device.
7. If the number of IP addresses supported by the device reaches the upper limit, you need to add BRASs. Run the display ip pool command to check the Total field under IP Address Statistic. Check whether the number of delivered IP addresses exceeds the maximum number of IP addresses supported by the device (2211840).
8. Check whether the fault persists.
- If so, go to Step 9.
- If not, go to Step 10.
9. Collect alarm, log, and configuration information, and contact technical support personnel.
10. End.