In Kindly see below the challenges encountered yesterday, September 21, 2017 - Thursday, during the registration of Huawei AP to Access Controller.
2 AP's are still not registered on AC. Status of 2 AP, 'idle' and 'fault.' Please see actual photo below.
Current Setup: AP was directly connected to CS were the other AP's are up and running.
I. Tried to delete and enroll it again. Result: Failed, AC can't still detect the AP.
II. Tried to reboot AC. Result: Failed, AC can't still detect the AP.
III. Reset AP. Result: Failed, AC can't still detect the AP.
IV. Checked config, but it was same configuration of other AP.
1.) After rebooting of Access Controller, it takes an hour to power up all the AP's connected. Please see actual photo below.
2.) After booting up of all AP's. SSID consistently went down after 2 mins and be back in 2 mins. It happens in hour to completely become stable.
3.) From AC ping AP , if we ping large size packets , its cannot passed , but when the AP download configuration from AC , its need large packets , so we need middle device passed at least 1514 size packets.
1- we checked the AP online failed inform , we found the AP failed reason is config failed, please refer to below picture .
2- Yesterday we made test on AC , we ping the AP which can get the IP address 192.168.100.250 , if we ping AP use size 1500 , ICMP packets cannot be reached AP , it lost on the middle device . form the topology , we know between AC and AP only one xxxx switch , so we doubt the packets lost on xxxx switch .
3- actually xxxx device only permit 1472 byte size packets , please let xxxx device check it .
4- From our lab , I ping size 9600 ICMP packet can be reached AP .
xxxx switch canot allow 1514 Bytes packets passed , so AP cannot get the configuration from AC.
Need the middle device passed 1514 Byte packets .
1- Connect AP to AC directly .
2- Use one Huawei POE switch connect to AP.
3- Let xxxx Switch passed large size packets .