Hi all Can anyone explain what does the following syslog mean for ? Sep 07 10:35:29 10.1.1.1 CC: Client bridge device xbo1ap0 has lost its connection (1) mu Sep 07 10:35:30 10.1.1.1 CC: Mesh Connection Break: reason = 8 Sep 07 10:35:30 10.1.1.1 CC: Mesh roam num_ap_bridges(2) 0 Sep 07 10:35:30 10.1.1.1 CC: Roam Debug: Before brctl del Sep 07 10:35:30 10.1.1.1 CC: brctl ioctl cmd to eth0 failed, error = -1 Sep 07 10:35:30 10.1.1.1 CC: Roam Debug: After brctl del Sep 07 10:35:30 10.1.1.1 CC: Mesh: Failed to del xbo1ap0 from subnet 1 (-2). Sep 07 10:35:30 10.1.1.1 CC: Assert Fail, File wlap.cpp, Line 1163; Exiting Sep 07 10:35:30 10.1.1.1 ccsrvr: requesting evtlog dump from AP Sep 07 10:35:30 10.1.1.1 ccsrvr: Process 237 exiting Sep 07 10:35:30 10.1.1.1 wispctld: main : select() timed out Sep 07 10:35:30 10.1.1.1 wispctld: main : select() timed out Sep 07 10:35:30 10.1.1.1 wispctld: Wisper_Event : WISPER_STATE_RUN to WISPER_STATE_RUN, evt=WISPER_EVENT_TIMEOUT tmo=1 The syslog was captured during the following test setup. Please notes in the step 6, 7, 8, there were misbehaviour under the CB's CLI and console output. 1. 2 AP5131 working as Base Bridge (BB) and 1 AP5181 working as Client Bridge (CB) 2. a direct LAN cable was connect to the CB and a monitoring PC, in which - a telent session was issued to the CB and issuing the cmd "network.wireless.radio.802.11a.mesh --> sh stat" continuously to monitor the mesh status - a continuous ping command was issue to the CB 3. a hyper-terminal was setup to monitor the CB's console port 4. CB was simulated to get away from the all BB until CB could not see any BB 5. CB was simulated to get back in order to re-form mesh from 1 of the BB 6. The telnet session "sh stat" command return error. Error message was : stats read failed 7. The console terminal displayed the following error message: _send_ioctl error: Invalid argument 8. After while, the CB reboot automatic Regards Antony
AP rebooted in mesh with AP51x1// Expert user has replied. |
4 Replies
Hi Pramada Thanks for your reply. This is what we have observed. We recongized that when the AP was going to reboot, the following message would be logged. Sep 07 10:35:30 10.1.1.1 CC: Mesh Connection Break: reason = 8 We have noted that there were some other Break reason logged for mesh disconnection. However, only the AP would reboot only when the Break reason was 8. Could you indicate some meaning about the value on the break reaosn ? We do see the break reason with 0, 4, 8, 64. We would like to know what we have done in the testing that will cause this break reason to be logged in order to troubleshoot and suggest solution to our customer. We are using a tailor made firmware for our customer. Both BB and CB are AAP. The firmware version in 2.2.2.1-008WCB / 2.2.2.1-009WCB. For RFS switch it is running 1.3.1.4-006WCB / 1.3.1.4-007WCB respectively. Regards Antony
Hi Antony, The reason codes mean the following: 0 - Radio is going down 4 - Association failed 8 - Association lost 64 - client bridge will try to roam to a better base bridge Association lost can happen when the client bridge does not hear beacons from the base bridge, or the client bridge is not able to transmit to the base bridge, or the base bridge sends a deauth or disassociation frame to the client bridge. This should not cause the AP to reboot. Does the reboot happen only one AP or does it happen on multiple APs? Thanks, Pramada
Anthony - this version was made for one customer only - Wuhan. If Wuhan is reporting a problem - please escalate thru regular process to ECRT. Don't use this forum since this is a special firmware that you are using. Alona
Hi Antony, The syslog messages mean that the client bridge has lost association to the base bridge then it tried to delete the mesh interface from the bridge but the bridge control failed in the delete operation. This caused assert fail and so the process ccserver is exiting. This will cause the AP to reboot. What is the firmware version you are using on the client bridge and the base bridges? Are these APs being used in adaptive mode with a switch? What is the SKU of these APs? Regards, Pramada Singamsetty