Case Study: Wireless Configuration Synchronization Does Not Take Effect
Symptom
The web system displays a message indicating that wireless configuration synchronization does not take effect.
Relevant Alarms and Logs
The web system displays the following error message.
Cause Analysis
- Commands in the RADIUS server template view: radius-attribute nas-ip ip-address, radius-attribute nas-ipv6 ipv6-address, radius-server accounting { ipv4-address | ipv6-address } port source ip-address { ipv4-address | ipv6-address }, and radius-server authentication { ipv4-address | ipv6-address } port source ip-address { ipv4-address | ipv6-address }
- hwtacacs-server source-ip ip-address command in the HWTACACS server template view.
- Portal server template view: source-ip ip-address
- Location profile view: source { ip-address ip-address | ipv6-address ipv6-address }
- BLE profile view: source { ip-address ip-address | ipv6-address ipv6-address }
Procedure
- Replace the configuration commands related to source IP address and NAS-IP-Address attribute with the related configuration commands in the system view on each AC. The following commands are involved:
- radius-attribute nas-ip ip-address, radius-attribute nas-ipv6, and radius-server source ip-address { ipv4-address | ipv6-address }
- hwtacacs-server source-ip ip-address
- web-auth-server source-ip ip-address
- location source { ip-address ip-address | ipv6-address ipv6-address }
- ble source { ip-address ip-address | ipv6-address ipv6-address
For example, the original configuration commands are as follows:
<AC> system-view [AC] radius-server template group1 [AC-radius-group1] radius-server accounting 10.1.2.1 1813 source ip-address 10.1.1.1
Replace the configuration commands with the following ones:
<AC> system-view [AC] radius-server template group1 [AC-radius-group1] radius-server accounting 10.1.2.1 1813 [AC-radius-group1] quit [AC] radius-server source ip-address 10.1.1.1
Suggestion and Summary
When configuring wireless configuration synchronization, ensure that the configurations related to source-ip and nas-ip do not exist in a template or profile. Otherwise, wireless configuration synchronization does not take effect or fails.