Joining The Mobility Domain - Avaya 8800 Troubleshooting Manual

Troubleshooting the Unified Access solution
6. If none of the above steps resolves the problem, get the switch technical dump and

Joining the mobility domain

After you enable the wireless system, you should be able to join the mobility domain. If you
cannot join the mobility domain, use these procedure steps on the WCP. There are three main
reasons for not being able to join the mobility domain
• The AMDC system IP address cannot be reached.
• The stale controllers need to be purged.
• The TCP/UDP port is different than the AMDC's port.
Procedure
1. Use the following command on the WCP to join the mobility domain:
2. Display the current state of the controller:
3. Display the current state of the peer controller:
4. From the AMDC, purge the stale controllers from domain table:
5. After purging the controller, leave the mobility domain from Peer Controller and then
426 Troubleshooting
default base port is chosen, make sure the DHCP option 43 for APs provides the
non-default base port to the AP.
send it to Avaya Support.
show tech
wireless controller join-domain domain-name <domain name>
mdc-address <amdc ip address>
If you want this controller to be the A-MDC, use the wireless controller
info to verify that the controller is Mobility Domain Controller (MDC) capable. To
configure the controller to be MDC capable, use the controller mdc-
capable command and the mdc-address command to specify its local wireless
system IP address.
show wireless controller domain-membership
or
show wireless controller status
show wireless domain peer-controller status
or
show wireless controller status
wireless domain purge-stale-controllers
join again:
Comments? infodev@avaya.com
July 2013