AM/4/AM_XML_STATIC_BIND

Message

AM/4/AM_XML_STATIC_BIND: AM XML static bind failed. Reason: [STRING]. Operation:[STRING].

Description

In free mobility scenarios, an IP address in the IP address pool on the device failed to be statically bound to or unbound from a user's MAC address based on the XML file delivered by the controller.

Parameters

Parameter Name	Parameter Meaning
Reason	Cause of the failure to statically bind or unbind IP and MAC addresses. Possible causes can be classified into XML packet error, abnormal device status, and incorrect configuration as follows: XML packet error Incorrect packet format: The packet format is incorrect. Necessary attribute missing: Necessary attributes in the packet are lost. Attribute unknow: The packet contains unknown attributes. Incorrect attribute value: The attribute value is incorrect. Duplicate attribute: The packet contains duplicated attributes. Abnormal device status Internal processing exception: The device runs abnormally. Device busy: The device is busy and cannot provide sufficient resources. Incorrect configuration Specification full: The configuration exceeds the specifications. No global address pool: The global address pool name delivered by the controller does not exist on the device. No interface address pool: The interface address pool name delivered by the controller does not exist on the device. IP status error: The IP address to be bound is in use or conflicts with another device's IP address. Interface not exist: The interface does not exist. Invalid MAC address: The format of the MAC address to be bound is invalid. Invalid IP address: The format of the IP address to be bound is invalid.
Operation	Operation, corresponding IP address pool name, and IP and MAC addresses delivered by the controller. The operation includes: Add: static binding Delete: unbinding NOTE: When the failure cause is XML packet error or abnormal device status, the device cannot parse information in the XML packet. As a result, the IP address pool name, IP address, and MAC address are not recorded in the log.

Parameter Name

Parameter Meaning

Reason

Cause of the failure to statically bind or unbind IP and MAC addresses. Possible causes can be classified into XML packet error, abnormal device status, and incorrect configuration as follows:

XML packet error
- Incorrect packet format: The packet format is incorrect.
- Necessary attribute missing: Necessary attributes in the packet are lost.
- Attribute unknow: The packet contains unknown attributes.
- Incorrect attribute value: The attribute value is incorrect.
- Duplicate attribute: The packet contains duplicated attributes.
Abnormal device status
- Internal processing exception: The device runs abnormally.
- Device busy: The device is busy and cannot provide sufficient resources.
Incorrect configuration
- Specification full: The configuration exceeds the specifications.
- No global address pool: The global address pool name delivered by the controller does not exist on the device.
- No interface address pool: The interface address pool name delivered by the controller does not exist on the device.
- IP status error: The IP address to be bound is in use or conflicts with another device's IP address.
- Interface not exist: The interface does not exist.
- Invalid MAC address: The format of the MAC address to be bound is invalid.
- Invalid IP address: The format of the IP address to be bound is invalid.

Operation

Operation, corresponding IP address pool name, and IP and MAC addresses delivered by the controller. The operation includes:

Add: static binding
Delete: unbinding

NOTE:

When the failure cause is XML packet error or abnormal device status, the device cannot parse information in the XML packet. As a result, the IP address pool name, IP address, and MAC address are not recorded in the log.

Possible Causes

In free mobility scenarios, an IP address in the IP address pool fails to be statically bound to a MAC address based on the XML file delivered by the controller. For details about the cause, see parameter meanings listed in the preceding table.

Procedure

If the failure cause is XML packet error, obtain the packet header to check whether the packets are valid.
If the failure cause is abnormal device status, check the device status.
If the failure cause is incorrect configuration, check the configuration parameters on the controller.