We are also testing 4.1.3.1 mac agent.... and are still stuck running
the script to fix the CPU utilization issue.

I have seen exactly this symptom you describe - in our case, we have 2
ssids, which are represented by 2 different roles in cca and 2 different
vlans... when users switch from one ssid to the other, they get an SSL
error. I haven't grabbed the debug logs yet from the agent or opened a
ticket...

Also, I have one report of a user experiencing intermittent network
drops when on their home network and the CCA mac agent is still running.
This sounds an awfully lot like the 4.1.3.0 PC agent problem that
affected non-CCA-monitored networks... but I'm waiting on data on that
one. 

Please let me know if you make any discoveries ;-) I think there aren't
many people out there running the mac agent ;-)

-faith

Faith Baynes
Systems Administrator
Catlin Gabel School

-----Original Message-----
From: Cisco Clean Access Users and Administrators
[mailto:[log in to unmask]] On Behalf Of Isabelle Graham
Sent: Thursday, April 10, 2008 12:54 PM
To: [log in to unmask]
Subject: Mac agent 4.1.3.1

We're doing some preliminary testing with the current version of the Mac
agent (4.1.3.1) 
and I was wondering if anyone else was testing/using this version and
what experience 
you've had with it (good or bad).
In testing 4.1.3.0 we saw the issue others have reported of steady CPU
activity spikes, 
but that seems to have been fixed. However we have seen an issue with
4.1.3.1 where moving 
between wired and wireless connections will sometimes result in the new
log in being 
denied with an SSL error. If the agent is restarted the log in goes
through, but this is 
going to be a bit of a hassle for our users. Any suggestions or
feedback?

Thanks

-- 
Isabelle Graham
Information Security
American University