I've attached my config from my 2811. There are a couple things I can't figure out.
Why is VLAN1 up / down?
cao-va_colh#sh ip int brief Interface IP-Address OK? Method Status Protocol FastEthernet0/0 172.18.4.1 YES NVRAM up up FastEthernet0/1 unassigned YES NVRAM administratively down down FastEthernet0/1/0 unassigned YES unset up down FastEthernet0/1/1 unassigned YES unset up down FastEthernet0/1/2 unassigned YES unset up down FastEthernet0/1/3 unassigned YES unset up down FastEthernet0/1/4 unassigned YES unset up down FastEthernet0/1/5 unassigned YES unset up down FastEthernet0/1/6 unassigned YES unset up down FastEthernet0/1/7 unassigned YES unset up down FastEthernet0/1/8 unassigned YES unset up down Serial0/2/0:0 unassigned YES NVRAM up up Serial0/2/0:0.500 63.x.x.x YES NVRAM up up wlan-controller1/0 172.19.4.1 YES NVRAM up up Vlan1 172.20.4.1 YES NVRAM up down NVI0 unassigned NO unset up up
The second and more pressing matter is this sh ip account.
Why is a wired, LAN device going through the AP-Manager? All wired clients should get 172.18.4.x addresses. All wireless clients should get 172.19.4.x addresses and WAPs should get 172.20.4.x addresses. Since WLAN1 is up / down, I understand why WAPs aren't getting 172.20.4.x but why would a wired device be using the AP-Manager as it's source to the internet?
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...