Cisco Cisco MGX-FRSM-HS2 B Serial Frame Service Module Manual Técnica
address.
There is not any layer−3 connectivity between H−REAP and the WLC.
There is not any layer−3 connectivity between H−REAP and the WLC.
•
There is not a Lightweight Access Point Protocol (LWAPP) connectivity between the H−REAP and
WLC.
WLC.
•
Other reasons are the H−REAP joining to a different controller, certificate mismatch, problem with
WLC or H−REAP itself, etc.
WLC or H−REAP itself, etc.
•
Perform these steps to troubleshoot these problems:
Verify that H−REAP AP is assigned an IP address.
If DHCP is used through the console of the AP, verify that the AP gets an address with this command:
.
AP_CLI#show dhcp lease
If the output of this command is none, it implies that DHCP addressing is not used for this AP.
Now, ensure that the static IP address is assigned to the AP in a proper way. This can be verified with
this command:
this command:
AP_CLI#show lwapp ip config
LWAPP Static IP Configuration
IP Address 10.77.244.222
IP netmask 255.255.0.0
Default Gateway 10.77.244.220
The output displays a static IP address of 10.77.244.222 assigned to the AP. If this is not the intended
IP address to be assigned, correct the IP address.
IP address to be assigned, correct the IP address.
1.
Verify the IP connectivity between the AP and the management interface of the controller.
Once the IP address has been verified, ping the management IP address of the controller to make sure
that the AP can communicate with the controller. Use the ping command through the console of the
AP with this syntax:
that the AP can communicate with the controller. Use the ping command through the console of the
AP with this syntax:
AP_CLI#ping 10.77.244.210
!−−− 10.77.244.210/27 is the example management interface IP address of the controller.
If the ping is not successful, it indicates that there is a problem in the IP connectivity between AP and
the controller. Ensure that the upstream network is properly configured and that WAN access back to
the corporate network is up. Verify that the controller is operational and is not behind any NAT/PAT
boundaries. Ping from the controller to the AP with the same syntax. Make sure the MTU for the path
between the controller and the H−REAP is at a minimum of 1500. This can be checked with the ping
−l 1500 <WLC Management IP > command from a computer on the H−REAP side of the WAN.
the controller. Ensure that the upstream network is properly configured and that WAN access back to
the corporate network is up. Verify that the controller is operational and is not behind any NAT/PAT
boundaries. Ping from the controller to the AP with the same syntax. Make sure the MTU for the path
between the controller and the H−REAP is at a minimum of 1500. This can be checked with the ping
−l 1500 <WLC Management IP > command from a computer on the H−REAP side of the WAN.
Here is a sample ouput of the successful ping command:
ping −l 1500 10.77.244.210
Pinging 10.77.244.204 with 1500 bytes of data:
Reply from 10.77.244.210: bytes=1500 time=6ms TTL=252
2.