I have a basic question to ask regarding the flow of traffic.
Following is the setup,
WLC----> Core Switch ----> Firewall/Filtering Server ----> Internet : (Network A)
WLC------> Core Switch -----> External Network : (Network B)
There are two seperate networks A & B. WLC on Network A is the remote controller & WLC on network B is the anchor controller.
The question is regarding network A users.
Network A WLC has dhcp server pointed to the Firewall/Filtering Server (which has the scope configured). I know that WLC A connections will be tunneled to WLCB as it is the main controller. But how will the dhcp request from a user in network A travel?
Will it travel from WLC A to WLC B or becuase the dhcp server is within Network A, users dhcp request will simply to WLC A & get redirected to Firewall/Filtering server in Network A?
Did you configure "Auto-Anchor" feature for the WLAN ? What type of WLAN is this ? is this a WLAN configured for guest traffic ?
If it is typical Guest WLAN, then WLC at network A won't have any L3 attachement of your clients. When client associations hits that WLC it will tunnel back to Anchor WLC who will manage the IP assignment to client. So Anchor WLC will go back to whereever you configured as DHCP server to get an IP for the client. So all L3 information with anchor WLC only.
Asymmetric tunneling breaks when an upstream router has reverse path filtering (RPF) enabled. In this case, the client traffic is dropped at the router because the RPF check ensures that the path back to the source address matches the path from which the packet is coming. When symmetric mobility tunneling is enabled, all client traffic is sent to the anchor controller and can then successfully pass the RPF check
Symmetric mobility tunneling is also useful in the following situations:
•If a firewall installation in the client packet path drops packets because the source IP address does not match the subnet on which the packets are received.
•If the access-point group VLAN on the anchor controller is different than the WLAN interface VLAN on the foreign controller. In this case, client traffic could be sent on an incorrect VLAN during mobility events.
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...