WISM, Controller, ASA5515. New wireless Guest implementation failure
I have been trying to get our 5508 guest controller to talk to our wism2. I got the mobility group up and working but could not get the 5508 to communicate to the asa5515x even though they are directly connected.
This is a new implementation.
The 5508 will be the anchor with internal dhcp.
I created a interface for it as well. Vlan 1500.
5508 is anchored to the wism2s through mobility and communicates through the mgmt ip.
The 5508 then goes through an ASA5515x before it hits the internet.
I talked to various wireless engineers and asa engineers and no one could seem to figure it out. They all kept pointing to trunking but the asa is unable to set a physical port as trunking.
I created a sub interface on the ASA5155x then put that sub interface In the vlan. The mgmt ip of 5508 is the only vlan that actually lives on our
The Cisco Controller "should not" be used as a DHCP server in production network. A CCIE stated this was really only for LAB scenarios!?!
The Ports on the Controller are not really like a switch port, therefore a direct connection between a ASA 5515x Gi0/0 interface and Gig port 1-8 on controller is not recommended. The recommend putting a switch in between. Rack space is small and defeates the original design intent.
These last 2 revelations, from Cisco employees, begs for the phrase "wth"?!?!
The goal is to keep Guest user traffic OFF the main production network.
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...