We have this senario: out of band L2 NAC deployment for wireless. Everything works great, however, when the client is connected to wired network which is not part of the NAC enforcement, we get this Error popping up over and over again:
Invalid switch configuration-OOB Error: OOB client x:x:x:x:x/y.y.y.y not found
I know that this error is coming because the switch is not added in the CAM. We can mask the issue by either unchecking the popup option on the NAC agent icon in system tray or changing the CAS ip on the NAC agent to unreachable address. Moreover, IP connectivity of the client is not affected by this message as we can reach the network from the client. The only issue is that we have the popup. Is there a way to stop the agent from doing SWISS discovery when on wired network? Any insight would be appreciated.
I'm facing similar issue with wireless NAC user, not to wired NAC user. Some wireless NAC user cannot login to their NAC agent, the error message is OOB Error: connected device not found. When this happen, i user clear mac address-table dyna on switches. I wonder if there are some parameter that i need to tune in the NAC or WLC or the switches?
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...