One aspect is that Cisco WGBs send IAPP messages to the WLC, which is how the WLC learns about the wired clients behind the WGB. Non-Cisco WGBs don't use IAPP, and therefore can't act as an intermediary to send information about their clients. Of course, setting a Cisco WGB as a "Universal WGB" would make it act like a non-Cisco WGB, so there wouldn't be much difference there. I guess I would look for the following:
1) Multiple devices behind a non-Cisco or Universal WGB - Disable MAC to IP Binding checks. 2) Passive device(s) behind non-Cisco or Universal WGB - Enable Passive Client Honestly, if I'm doing #1, I'm probably also doing #2 unless the wording says to NOT enable Passive Client. Remember that over-configuration is allowed, as long as it doesn't go against the specific requirements of the test - read them carefully! Jason Boyers, CCIE #26024 (Wireless) Blog: netboyers.wordpress.com On Sat, Dec 29, 2012 at 5:14 PM, Jeff Rensink <[email protected]> wrote: > Thanks Jason. > > That type of scenario is pretty easy to identify as needing the passive > client feature. I'm more thinking of when WGBs come into the picture. For > instance, here is a snippet of of the 7.0.116.0 release notes regarding > passive client. > > Non-Cisco WGB Support > > Starting in release 7.0.116.0, the controller software has been updated to > accommodate non-Cisco workgroup bridges so that the controller can forward > ARP, DHCP, and data traffic to and from the wired clients behind workgroup > bridges. This processes is accomplished by enabling the passive client > feature. To configure your controller to work with non-Cisco workgroup > bridges, you must enable the passive clients feature. All traffic from the > wired clients is routed through the work group bridge to the access point. > > > > So it seems that when WGBs get into the picture, both passive client and > the MAC-to-IP binding features can come into play. When WGBs are > mentioned, what's the best way to decide which feature is being asked about > (or if both would be needed). > > > Jeff > > > > > On Sat, Dec 29, 2012 at 3:20 PM, Jason Boyers <[email protected]> wrote: > >> A passive client is that- passive. That means that it, generally >> responds to traffic sent to it as opposed to initiating the traffic >> exchange. You may see wireless printers and other devices that behave in >> that manner. Without "passive client," those devices would potentially be >> dropped at the User Idle Timeout because they didn't initiate traffic. >> >> Jason Boyers >> CCIE wireless #26024 >> On Dec 29, 2012 4:14 PM, "Jeff Rensink" <[email protected]> wrote: >> >>> Can anyone help to distinguish when to use the passive client feature >>> and when to disable the MAC to IP binding check? They seem to be used in >>> somewhat similar circumstances. >>> >>> The example that the fastlane workbook gives for disabling the MAC to IP >>> binding check is with a universal gateway with multiple clients behind it. >>> So the WLC can see more than 1 IP using a single MAC address. >>> >>> For using passive client feature, I've seen mention to scenarios like >>> static IPed devices and non Cisco WGBs. I know it allows ARPs to flow >>> between wired/wireless devices rather than being proxied by the WLC. >>> >>> I guess I'm confused over when one should be used over another. Are >>> there key words I should be looking for that would point me to one or the >>> other? >>> >>> Jeff Rensink >>> >>> _______________________________________________ >>> For more information regarding industry leading CCIE Lab training, >>> please visit www.ipexpert.com >>> >>> Are you a CCNP or CCIE and looking for a job? Check out >>> www.PlatinumPlacement.com >>> >>> >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
