Case of shooting oneself in the foot. Lease times set to expire in 60 minutes, heartbeat timer set to 240 minutes. Shutdown machine for over one hour, lease placed back in pool, power up machine, previous lease picked up by Vista client, I'm using XP, bingo OS Mismatch.
Changed heartbeat timer to 30 minutes, wiping egg off face now... -----Original Message----- From: Cisco Clean Access Users and Administrators [mailto:[email protected]] On Behalf Of Speight, Howard Sent: Thursday, February 12, 2009 08:52 To: [email protected] Subject: Re: OS Mismatch No, that didn't occur to me, DHCP "shouldn't" be giving two people the same IP address. At one time the WISM blade was set to DHCP only which wouldn't allow hard coded IP addresses to work (that doesn't stop someone from hard coding an IP), I'll have to inquire if that has changed. I believe there was a performance issue and there was a debate as to whether to turn that off. I searched on my Mac address, not the IP, good tip... :-) -----Original Message----- From: Cisco Clean Access Users and Administrators [mailto:[email protected]] On Behalf Of Dennis Xu Sent: Thursday, February 12, 2009 08:33 To: [email protected] Subject: Re: OS Mismatch Howard, When the OS Mismatch issue happens, did you search the online users list to see if the IP is already in the OUL with a different OS? Dennis ----- Original Message ----- From: "Howard Speight" <[email protected]> To: [email protected] Sent: Thursday, February 12, 2009 8:23:30 AM GMT -05:00 US/Canada Eastern Subject: Re: OS Mismatch I would love to, but I don't plan on running 4.1.3.1 much longer, I'm recommending an upgrade and if I can push it through, as early as next weekend. To further elaborate this is happening in our wireless environment and we do authentication only, no checks. Our wireless environment is reset every morning at 2am, see attached. This happened to me three days in a row since upgrading to 4.1.8.0 Agent, this morning logged in fine. I have a couple of users that report the problem constantly, but they move from wired to wireless back to wired without ever turning off their laptop. I'd never experienced it until upgrading to Agent 4.1.8.0 but I was using wireless exclusively (wired interface disabled). If it's still happening after upgrading the CAM/CAS I will certainly open a TAC case. The Agent is not mandatory in our wireless environment, but anyone using the Agent will receive an upgrade notification. We are also running HA and I rebooted the Primary CAS yesterday (for other reasons), let it recover, then rebooted the active Stand-by, now back on the Primary. Not sure if that was a factor or not? -----Original Message----- From: Cisco Clean Access Users and Administrators [mailto:[email protected]] On Behalf Of Alok Agrawal (alagrawa) Sent: Thursday, February 12, 2009 02:05 To: [email protected] Subject: Re: OS Mismatch Hey Howard, We tried reproducing this in our lab, no luck. Can you open a TAC case and unicast me the tac case number? Thanks -Alok -----Original Message----- From: Cisco Clean Access Users and Administrators [mailto:[email protected]] On Behalf Of Speight, Howard Sent: Wednesday, February 11, 2009 12:03 PM To: [email protected] Subject: OS Mismatch Anyone else seeing this? CCA 4.1.3.1, Agent 4.1.8.0, ADSSO. Machine boots up, log into the Domain, Agent is running, get OS Mismatch, hung at this point. Hung meaning stop and start Agent, still get OS Mismatch, no info on the CAM. Exit the Agent, authenticate through web browser, logout, restart the Agent, ADSSO logs in machine, now works fine. Looks like I have two choices, down grade to Agent 4.1.3.1 or upgrade CAM/CAS to 4.1.8? Thanks, Howard
