We try to reboot the client device, still can not get past the bridge. We can ping the bridge but not the gateway from the devices behind the WGB. We try to do a dhcp release / renew it does not work. When logged into client behind the WGB, client shows 169.x.x.x address or its acquired DHCP address. We are always able to reach the WGB, but not the client or clients behind it. If multiple device are connected to the WGB, they do not loose connectivity at the same time. Since we upgraded - the issue we are having is devices behind the WGB lose connection randomly.
#Lehigh libray wired client upgrade#
The WGBs worked as normal on code version 7.3.112, however we had to upgrade to the 8.X platform for compatibility with ISE for our non WGB wireless networks.
We use 1231s, 1602i, and 1702i for WGBs in the field. We use 3502 APs in flex connect with local switching. We have a Cisco 5508 WLC running version 8.0.133.0. I was reading through your post, and I am experiencing a very similar issue with our WGBs since we upgraded to the 8.X version of code. *DHCP Socket Task: Aug 18 17:18:36.023: 3c:07:54:61:90:23 DHCP dropping packet (no mscb) found - (giaddr 0.0.0.0, pktInfo->srcPort 68, op: 'BOOTREQUEST')ĭid someone ever see this problem too and is there a workaround? *iappSocketTask: Aug 18 17:17:22.622: 3c:07:54:61:90:23 Ignoring wired client add as the WGB is not in RUN state. The problem occurs, when the client wants to re-bind its DHCP address or tries to get a new one: *iappSocketTask: Aug 18 17:17:21.551: 3c:07:54:61:90:23 Ignoring wired client add as the WGB is not in RUN state. We have a simple WGB szenario with a client behind (no VLANs on WGB side) and trying to connect to a Cisco WLC 8.3 controller:Īuthentication key-management wpa version 2 cckm
0 kommentar(er)
