On the Catalyst 9800, the point at which client traffic enters the wired network is controlled in the policy profile. The command context is wireless profile policy, followed by the profile name. Inside that context, no central switching tells the controller that clients of the WLANs mapped to this policy are switched locally at the AP, so their traffic enters the network at the AP switch port instead of being tunnelled in CAPWAP to the WLC. This normally goes together with no central dhcp and no central association for FlexConnect sites, and the AP must be in FlexConnect mode, which is achieved through the Flex profile and site tag. The command keyword local switching does not exist in the policy profile. Likewise, wireless flexconnect policy is not a valid configuration context on this platform. The Flex profile is created with wireless profile flex, and the switching behaviour is not set there. The only option that uses the correct context and the correct command is the set with wireless profile policy and no central switching.
[Reference:Blueprint 1.1 (FlexConnect switching); Cisco Catalyst 9800 Series Software Configuration Guide, FlexConnect and policy profile. Source key listed C; corrected to D (see appendix)., ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit