I have a 350 series WGB running software v8.65.02. After configuring it with an IP and an SSID. It worked fine. A duplicate IP address with another device caused it to lose its IP. Even after changing the IP address of the other device, It still fails to show its IP. My problem no is that I cannot get into the bridge to correct the IP. I used the IP Utility and telnet and nothing works.
Please help on how I can get into the bridge. The bridge works ok even without the IP, but i need to change the SSID.
Two things that you can do to get into the WGB. One is to get a laptop or PC and configure it with an IP address of 192.168.200.2 and try to telnet to the WGB using it's default IP address of 192.168.200.1 as it may have changed it's IP back to the default when there was an IP conflict. The second thing to do is to reset the WGB back to factory default then use the laptop or PC like I mentioned in the first scenario to telnet into the device and reconfigure it. Here is a link that shows how to reset the WGB back to factory defaults. http://www.cisco.com/warp/public/102/wlan/pwrec-2.html#workgroup_bridge
kmarrero, I'm having the same problem, but even after setting back to defaults, reconfiguring, then bench testing with standard antennas, everything works fine. UNTIL, I install them in the field with the Hyperlink pararbolic antennas. As soon as the links come up, I lose IP connectivity with the bridges. I'm still passing data, but cannot telnet, web, etc into the bridge, as the IP does not respond.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...