NAC ACS SSO

Hi all

I know that there is AD SSO in the NAC. I would like to have SSO with ACS that is integrated with AD. is there any document to show how to configure SSO with ACS Express or ACS?

Thank you

Alex

Alex,

In the short number - or at least, I have to say that I don't know of any way to do. To make the SSO with GBA, looking to connect to Windows with Radius or GANYMEDE +. This means that Windows GINA (Ctrl-Alt-Delete the piece of code) should be able to talk Radius or GANYMEDE + with the ACS server.

Only standards bodies supported on GRP are AD SSO (where connect you to your Windows machine and SSO happens) or RADIUS SSO (kind VPN wireless / installation). The second type is where you can make the accounting on ACS. With AD authentication, I don't know any way so he could be taken into account in the ACS.

One thing you could do theoretical is to send an accounting package to your express ACS of the CPC or the machine itself, but these are wacky solutions and require a lot of work/trials etc.

So in short, not :-)

[EDIT] An option that I have completely forgotten and could work for your customer is to configure the accounting server to the CCA. In this way, you can connect to AD and always send accounting packets to an accounting server. More information here:

http://www.Cisco.com/en/us/partner/docs/security/NAC/appliance/configuration_guide/45/cam/m_auth.html#wp1159082

[END_EDIT]

HTH,

Faisal

Tags: Cisco Security

Similar Questions

  • NAC VPN SSO Help

    I recently inherited the administration of a NAC solution in need of a tune up (running 4.1.8!). The largest consistent I get from users is that SSO VPN does not work and that users must open a web browser to authenticate with NAC once their SSL VPN has been implemented. I'm quite familiar with configuring VPN SSO and I'm ready to do it, but I can't find the answer to a specific question, I. You can enable VPN SSO for a certain types of users only? We have a combination of two employees (who have the officer) and entrepreneurs (who have no agent). I want to only VPN SSO to work for employees and contractors having to open a web browser for authentication. Is this possible and if so, how? I have found that if you do not have the agent and VPN SSO is enabled the connection is very clumsy. You open a browser, you redirected to NAC, and then you get connected once java or active x to run without having to provide your information identification and then you not directed your orginal http request.

    Thank you!

    For your employees, you can use the attribute class to match to a user within the NAC role according to the criteria of mapping Cisco VPN auth provider. You can also map the class attribute of entrepreneurs for the role of uanauthenticate so when pull it toward the top of their browser, they will see the authentication page of the. Once they authenticate and then in their user role, you can select the redirection page.

    I hope this helps.

    Tarik Admani

  • NAC AD SSO error: could not start the SSO service. Please check the configuration.

    Hi, can someone please help me with a problem of SSO?

    I'm trying to start the SINGLE sign-on service, but when I try to update I get the error message: "error: could not start the SSO service.» Please check the configuration. »

    The announcement is a Windows 2008 Server Standard R2 (64-bit) running at a 2003 domain functional level. (several servers) with the deployment of the OOB

    I was unable to ping the advertising server CASE CLI, so I created a static route to the announcement on the server of the ANC, and after that I successfully of the NAC Server ping IP address of the AD. The nac_server.log when I try to start the SSO:

    [[email protected]/ * / _primary_ag ~] # ping 10.200.0.3

    PING 10.200.0.3 (10.200.0.3) 56 (84) bytes of data.

    64 bytes from 10.200.0.3: icmp_seq = 1 ttl = 128 time = 0,247 ms

    64 bytes from 10.200.0.3: icmp_seq = 2 ttl = 128 time = 0,232 ms

    -ping - 10.200.0.3 statistics

    2 packets transmitted, 2 received, 0% packet loss, time 999ms

    RTT min/avg/max/leg = 0.232/0.239/0.247/0.017 ms

    [[email protected]/ * / _primary_ag ~] # tail-f /perfigo/access/tomcat/logs/nac_server.log

    2012-07-27 17:20:39.079-0300 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:20:39.079-0300 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:20:39.080-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader

    2012-07-27 17:20:39.080-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0

    2012-07-27 17:20:39.080 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init

    2012-07-27 17:20:39.080 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0

    2012-07-27 17:20:39.081 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync

    2012-07-27 17:20:39.081 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0

    2012-07-27 17:20:39.081-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip

    2012-07-27 17:20:39.081-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0

    2012-07-27 17:20:41.775-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:20:41.775-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:20:41.775-0300 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:20:41.775-0300 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:20:41.776-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader

    2012-07-27 17:20:41.776-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0

    2012-07-27 17:20:41.777 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init

    2012-07-27 17:20:41.777 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0

    2012-07-27 17:20:41.777-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOState = 1

    2012-07-27 17:20:41.777-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOState = 1:DURATION = 0

    2012-07-27 17:20:41.778-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOUser = casuser

    2012-07-27 17:20:41.778-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOUser = casuser:DURATION = 0

    2012-07-27 17:20:41.778-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOKdc = nissin.com.br

    2012-07-27 17:20:41.778-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOKdc = nissin.com.br:DURATION = 0

    2012-07-27 17:20:41.779-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSORealm = NISSIN.COM.BR

    2012-07-27 17:20:41.779-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - setAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSORealm = NISSIN.COM.BR:DURATION = 0

    2012-07-27 17:20:41.779 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:save

    2012-07-27 17:20:41.779 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:save:DURATION = 0

    2012-07-27 17:20:41.780 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:startSSOServer

    2012-07-27 17:20:41.780 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:startSSOServer:DURATION = 0

    2012-07-27 17:20:58.605-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager is running: {0.85,0.3, [0: 15:15]}: DETECT_INTERVAL = 20:DETECT_TIME_OUT = 300

    2012-07-27 17:20:58.608-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager http_code = 200: {0.85,0.3, [0: 15:15]}

    [2012-07-27 17:20:58.608-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager go to sleep: delay of {0.85,0.3, [0: 15:15]}] = 19997

    [2012-07-27 17:21:08.892-0300 connection TCP RMI 83 - 10.200.48.101 DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory: removed socket: 173d72d [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=11093,localport=1099]]

    2012-07-27 17:21:08.892-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETS_SIZE = 0 DEBUG

    2012-07-27 17:21:08.892-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE DEBUG =]

    2012-07-27 17:21:08.892-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETS_SIZE = 0 DEBUG

    2012-07-27 17:21:08.892-0300 connection TCP RMI 83 - 10.200.48.101 com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE DEBUG =]

    2012-07-27 17:21:18.610-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager is running: {0.85,0.3, [0: 15:15]}: DETECT_INTERVAL = 20:DETECT_TIME_OUT = 300

    2012-07-27 17:21:18.613-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager http_code = 200: {0.85,0.3, [0: 15:15]}

    [2012-07-27 17:21:18.613-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager go to sleep: delay of {0.85,0.3, [0: 15:15]}] = 19997

    2012-07-27 17:21:38.615-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager is running: {0.85,0.3, [0: 15:15]}: DETECT_INTERVAL = 20:DETECT_TIME_OUT = 300

    2012-07-27 17:21:38.618-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager http_code = 200: {0.85,0.3, [0: 15:15]}

    [2012-07-27 17:21:38.618-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager go to sleep: delay of {0.85,0.3, [0: 15:15]}] = 19997

    2012-07-27 17:21:41.794-0300 DEBUG Thread-246 com.perfigo.wlan.common.HttpClientResource - go to url https://10.200.48.100:443 / wlan/gss/GSSNotificationServlet ...

    [2012-07-27 17:21:41.813-0300 HandshakeCompletedNotify-threaded DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory: added the socket: 1e7e7ac [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=19660,localport=1099]]

    2012-07-27 17:21:41.814-0300 HandshakeCompletedNotify-threaded DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETS_SIZE = 1

    [2012-07-27 17:21:41.814-0300 HandshakeCompletedNotify-threaded DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE = [1e7e7ac [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=19660,localport=1099]]]

    2012-07-27 17:21:41.814-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOStatus

    2012-07-27 17:21:41.814-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:SSOStatus:DURATION = 0

    2012-07-27 17:21:44.103-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:21:44.103-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:21:44.104-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:21:44.104-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:21:44.104-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader

    2012-07-27 17:21:44.104-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0

    2012-07-27 17:21:44.105 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init

    2012-07-27 17:21:44.105 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0

    2012-07-27 17:21:44.105 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync

    2012-07-27 17:21:44.106 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 1

    2012-07-27 17:21:44.106-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip

    2012-07-27 17:21:44.106-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0

    2012-07-27 17:21:49.105-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:21:49.105-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:21:49.105-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:21:49.105-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:21:49.106-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader

    2012-07-27 17:21:49.106-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0

    2012-07-27 17:21:49.107 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init

    2012-07-27 17:21:49.107 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0

    2012-07-27 17:21:49.107 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync

    2012-07-27 17:21:49.107 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0

    2012-07-27 17:21:49.108-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip

    2012-07-27 17:21:49.108-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0

    2012-07-27 17:21:54.107-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:21:54.107-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:21:54.108-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:21:54.108-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:21:54.108-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader

    2012-07-27 17:21:54.108-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0

    2012-07-27 17:21:54.109 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init

    2012-07-27 17:21:54.109 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0

    2012-07-27 17:21:54.110 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync

    2012-07-27 17:21:54.110 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0

    2012-07-27 17:21:54.110-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip

    2012-07-27 17:21:54.110-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0

    2012-07-27 17:21:58.619-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager is running: {0.85,0.3, [0: 15:15]}: DETECT_INTERVAL = 20:DETECT_TIME_OUT = 300

    2012-07-27 17:21:58.622-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager http_code = 200: {0.85,0.3, [0: 15:15]}

    [2012-07-27 17:21:58.622-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager go to sleep: delay of {0.85,0.3, [0: 15:15]}] = 19997

    2012-07-27 17:21:59.109-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:21:59.109-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:21:59.110-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:21:59.110-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:21:59.110-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader

    2012-07-27 17:21:59.110-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0

    2012-07-27 17:21:59.111 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init

    2012-07-27 17:21:59.111 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0

    2012-07-27 17:21:59.112 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync

    2012-07-27 17:21:59.112 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0

    2012-07-27 17:21:59.113-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip

    2012-07-27 17:21:59.113-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0

    2012-07-27 17:22:04.111-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:22:04.111-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:22:04.112-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:22:04.112-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:22:04.112-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader

    2012-07-27 17:22:04.113-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 1

    2012-07-27 17:22:04.113 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init

    2012-07-27 17:22:04.113 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0

    2012-07-27 17:22:04.114 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync

    2012-07-27 17:22:04.114 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0

    2012-07-27 17:22:04.114-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip

    2012-07-27 17:22:04.114-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0

    2012-07-27 17:22:09.114-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:22:09.114-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:22:09.114-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:22:09.114-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:22:09.115-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader

    2012-07-27 17:22:09.115-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0

    2012-07-27 17:22:09.116 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init

    2012-07-27 17:22:09.116 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 1

    2012-07-27 17:22:09.116 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync

    2012-07-27 17:22:09.116 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0

    2012-07-27 17:22:09.117-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip

    2012-07-27 17:22:09.117-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0

    2012-07-27 17:22:14.116-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:22:14.116-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:22:14.116-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:22:14.116-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:22:14.117-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader

    2012-07-27 17:22:14.117-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0

    2012-07-27 17:22:14.117 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init

    2012-07-27 17:22:14.118 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 1

    2012-07-27 17:22:14.118 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync

    2012-07-27 17:22:14.118 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0

    2012-07-27 17:22:14.119-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip

    2012-07-27 17:22:14.119-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0

    2012-07-27 17:22:17.017-0300 DEBUG RMI RenewClean-[10.200.2.103:1099] com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETS_SIZE = 2

    [[2012-07-27 17:22:17.017 - 0300 DEBUG RMI RenewClean-[10.200.2.103:1099] com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE = [1e7e7ac [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=19660,localport=1099]], 1871db1 [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=server_primary_ag/10.200.2.103,port=1099,localport=12312]]]

    [2012-07-27 17:22:17.017-0300 HandshakeCompletedNotify-threaded DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory: socket: 59725 c added [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.2.103,port=12312,localport=1099]]

    2012-07-27 17:22:17.017-0300 HandshakeCompletedNotify-threaded DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETS_SIZE = 3

    [[[2012-07-27 17:22:17.017-0300 HandshakeCompletedNotify-threaded DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE = [1e7e7ac [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=19660,localport=1099]], 1871db1 [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=server_primary_ag/10.200.2.103,port=1099,localport=12312]], 59725 c [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.2.103,port=12312,localport=1099]]]

    2012-07-27 17:22:18.624-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager is running: {0.85,0.3, [0: 15:15]}: DETECT_INTERVAL = 20:DETECT_TIME_OUT = 300

    2012-07-27 17:22:18.627-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager http_code = 200: {0.85,0.3, [0: 15:15]}

    [2012-07-27 17:22:18.627-0300 TRACE Timer-0 com.perfigo.wlan.jmx.admin.FailSafeManager - FailSafeManager go to sleep: delay of {0.85,0.3, [0: 15:15]}] = 19997

    2012-07-27 17:22:19.118-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:22:19.118-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:22:19.118-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:22:19.118-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:22:19.119-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader

    2012-07-27 17:22:19.119-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0

    2012-07-27 17:22:19.120 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init

    2012-07-27 17:22:19.120 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0

    2012-07-27 17:22:19.120 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync

    2012-07-27 17:22:19.120 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0

    2012-07-27 17:22:19.121-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip

    2012-07-27 17:22:19.121-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0

    2012-07-27 17:22:24.119-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:22:24.119-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:22:24.119-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:22:24.119-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:22:24.120-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader

    2012-07-27 17:22:24.120-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0

    2012-07-27 17:22:24.121 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init

    2012-07-27 17:22:24.121 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0

    2012-07-27 17:22:24.122 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync

    2012-07-27 17:22:24.122 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0

    2012-07-27 17:22:24.122-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip

    2012-07-27 17:22:24.122-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0

    2012-07-27 17:22:29.120-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:22:29.120-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:22:29.121-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:22:29.121-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:22:29.121-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader

    2012-07-27 17:22:29.121-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0

    2012-07-27 17:22:29.122 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init

    2012-07-27 17:22:29.122 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0

    2012-07-27 17:22:29.123 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync

    2012-07-27 17:22:29.123 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0

    2012-07-27 17:22:29.123-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip

    2012-07-27 17:22:29.123-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0

    [2012-07-27 17:22:32.022-0300 RMI Scheduler (0) DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory: removed socket: 1871db1 [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=server_primary_ag/10.200.2.103,port=1099,localport=12312]]

    2012-07-27 17:22:32.022-0300 com.perfigo.wlan.ssl.SSLLog RMI Scheduler (0) DEBUG - RMISocketFactory:CACHED_SOCKETS_SIZE = 2

    [[2012-07-27 17:22:32.022-0300 RMI Scheduler (0) com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE = DEBUG [1e7e7ac [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=19660,localport=1099]], 59725 c [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.2.103,port=12312,localport=1099]]]

    [2012-07-27 17:22:32.022-0300 connection TCP RMI 86 - 10.200.2.103 DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory: moved socket: 59725 c [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.2.103,port=12312,localport=1099]]

    2012-07-27 17:22:32.022-0300 TCP RMI 86 - 10.200.2.103 DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETS_SIZE = 1 connection

    [2012-07-27 17:22:32.022-0300 connection TCP RMI 86 - 10.200.2.103 com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE = DEBUG [1e7e7ac [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=19660,localport=1099]]]

    2012-07-27 17:22:32.022-0300 TCP RMI 86 - 10.200.2.103 DEBUG com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETS_SIZE = 1 connection

    [2012-07-27 17:22:32.022-0300 connection TCP RMI 86 - 10.200.2.103 com.perfigo.wlan.ssl.SSLLog - RMISocketFactory:CACHED_SOCKETSE = DEBUG [1e7e7ac [TLS_RSA_WITH_AES_128_CBC_SHA: Socket[addr=/10.200.48.101,port=19660,localport=1099]]]

    2012-07-27 17:22:34.122-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:22:34.123-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - isRegistered DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 1

    2012-07-27 17:22:34.123-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo

    2012-07-27 17:22:34.123-0300 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - unregisterMBean: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:DURATION = 0

    2012-07-27 17:22:34.123-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader

    2012-07-27 17:22:34.123-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - createMBean DEBUG: com.perfigo.wlan.jmx.admin.ServerInfo:DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CAS:type = MLet, name = casLoader:DURATION = 0

    2012-07-27 17:22:34.124 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init

    2012-07-27 17:22:34.124 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:init:DURATION = 0

    2012-07-27 17:22:34.125 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync

    2012-07-27 17:22:34.125 connection TCP RMI 85 - 10.200.48.101 DEBUG com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper --0300 call: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:isServerInSync:DURATION = 0

    2012-07-27 17:22:34.125-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip

    2012-07-27 17:22:34.125-0300 connection TCP RMI 85 - 10.200.48.101 com.perfigo.wlan.jmx.BeanServerWrapper - BeanServerWrapper - getAttribute DEBUG: DefaultDomain:type = com.perfigo.wlan.jmx.admin.ServerInfo:CurrMgrEth0Ip:DURATION = 0

    [[email protected]/ * / _primary_ag ~] #.

    Thank you

    Moises,

    I wanted to know if you have followed these steps:

    http://www.Cisco.com/en/us/docs/security/NAC/appliance/configuration_guide/49/CAs/s_adsso.html#wp1266896

    Thank you

    Tarik Admani
    * Please note the useful messages *.

  • Urgent - NAC + ACS + Web-Auth in Wired environment - https redirection - certificate problem

    Hello world.

    I'm seting of an environment that uses Web-Auth for my cable and wireless. I followed the exact steps in this page of Cisco to run:

    http://www.Cisco.com/en/us/prod/collateral/iosswrel/ps6537/ps6586/ps6638/app_note_c27-577490.html

    I'm only testing environment wired right now.

    I plug a PC on a port, and I try to access a Web page of randon (for example, www.cisco.com). It is automatically redirected to the authentication page. I type the user name and password, but when authentication is successful, it goes automatically to the https version of the page, which brings me to the problem. I should add an exception (more on this option on the IE Web page) to this page to continue with the authentication and gain access to the internet. I enclose the steps I must perform:

    I think that it is linked to the certificate, but I'm not sure who or where. I would like to get some advice on your part to avoid this problem. I have no intention to buy all certificates, so if I could jump the https would be great.

    Thanks a lot for your help

    Victor Alves

    If you don't want an official cert, you must go to http only. But this means that people paswords will transit in the clear on the network.

    It's been long that I tried, but not is not remove 'ip http-server secure' do the trick?

  • SNS-3415-K9: hardware device console login reset password

    We brought a hardware appliance for small server secure network for the Applications of the NAC & ACS ISE: SNS-3415-K9. After the initial Setup, we have forgotten the IP address and the password for this unit. I access console on the server, but I can not connect because I forgot the password.

    I access MMIC, but I have no idea to reset password to log in to the console.

    Please help me.

    You will need to start using the installation media of the product you are using (ACS or ISE). Once you have started, you will be presented with a list of options, which is to reset the password for the admin user.

    Javier Henderson

    Cisco Systems

  • CCA Agent refreshing kills mapped IP apps?

    Deployment of the NAC L2OOB with AD SSO - users have the drive mapping connection scripts and kick sending apps but CCA Agent refreshes the IP address that by Cisco TAC are unconfigurable (despite the authentic giving optional web!). During this update, any mapped application disappears from the office and must be updated. I do NO need DHCP to update, but since you apparently, how can I avoid these applications mapped to disappear? Surely, this is done in many places with NAC and SSO AD? Thank you!

    Check if the dhcp configuration is done correctly on the cisco NAC.

    see the "dhcp Configuration" section in the following url for more information about the dhcp configuration:

    http://www.Cisco.com/en/us/docs/security/NAC/appliance/configuration_guide/412/CAs/s_dhcp.html

    See the following url for more information on troubleshooting cisco NAC with Active Directory Single Sign-On (SSO AD):

    http://www.Cisco.com/en/us/docs/security/NAC/appliance/configuration_guide/412/CAs/s_adsso.html#wp1156402

  • Problem of the NAC in the virtual tape gateway VPN SSO

    Hello

    I've implemented a NAC solution for remote users. The unit of CASE mode configured in the gateway enVirtual Strip.

    I followed all the steps listed in http://www.cisco.com/en/US/products/ps6128/products_configuration_example09186a008074d641.shtml

    Remote users can connect succeffuly using the cisco vpn software and they can ping the SIN, but not the DNS (the ASA offers IP @ but not the DNS I do not know why).

    When I access the NAS, I can download the NAC Agent but VPN SSO is not executed and the Agent asks me to connect using LOCAL DB.

    Any help please,.

    Kind regards

    Larson,

    For VPN SSO work, you must send the accounting package to the CAs. The CASE can in turn send for the ACS if you need accounting also be done on GBA, but for authentication ONLY work, the accountant must reach the CASE.

    HTH,

    Faisal

  • NAC SSO vpn: is the CASE real-IP mode supported?

    Hi all

    I tried to setup a CAS like inline real gateway IP to support only enroll via a Cisco ASA running IPsec cisco vpn client.

    CASE and CAM are 4.5.1 running

    I followed the guide online to the letter (except for running in the virtual gateway mode and do the mapping vlan)

    My vpn authentication works on the SAA and Ray is transmitted if the CASE to the ACS server very well.

    I did a tcpdump on the case and cam and saw the package of accounting Radius passed from the ASA to the CAs, and then by the CAS to the CAM, so managing accounts radius 'start' package is sent to the user authenticated on the vpn.

    The problem is that the laptop is trying to access the network does not display the "auto connect" screen of the agent of the CCA, in contrast, agent of the CCA screen the authentication of user request and password details.

    I also following the advice of this link unsuccessfully

    (Known issue for VPN SSO after upgrade to version 4.5)

    http://www.Cisco.com/en/us/docs/security/NAC/appliance/Release_notes/45/45rn.html#wp711526

    So, I am now suspecting whether the CASES can take in charge SSO real-mode gateway IP.

    Dale

    I've implemented in real gw ip mode, but not in 4.5. It has worked well.

    What is the guide that you followed?

    http://www.Cisco.com/en/us/partner/docs/security/NAC/appliance/configuration_guide/45/CAs/s_vpncon.html

  • ACS + NAC-L2-IP & 802. 1 x

    Hello! I implement NAC now, I knew of the NAC Framework configuration guide, I can use the NAC-L2-IP for posture validation, but this model (technology) does not provide the identity of the user. So the question is - at the same time we use the NAC-L2-IP for the validation of the posture and 802. 1 x for authentication of the user (using MS-CHAPv2) on Catalyst 3560 G and with ACS 4.1?

    Thank you in advance!

    Yes, this can work. If you are migrating at some point to have NAC with 802. 1 X, well, you will get are studying twice on the ports configured for two well.

  • NAC OOB AD SSO

    Hello

    I am configuring SSO OOB of the NAC with AD. The software on my CASE and the CAM is 4.7 (2)

    and my ad is Windows Server 2008.

    I have some information I must not run ktpass with this version of the software of the NAC (4.7.2)

    on the AD server. Is this true? Because I found this kind of information in any textbook.

    So I run the ktpass, and if I do, what version should I use?

    Thank you

    Zoran,

    Check out this link. Even though it says it's for 4.8, he works with 4.7.2 also:

    http://www.Cisco.com/en/us/docs/security/NAC/appliance/configuration_guide/48/CAs/s_adsso.html#wp1300720

    HTH,

    Faisal

  • Urgent - NAC V 4.8 AD SSO for WIN 2008 64 bit support

    Hi all

    Cisco NAC V 4.8 support AD SSO with WIN 2008 64 bit?, & I want to configure AD SSO in win 2008 64 bit with output KTPass running the command.

    I tried in 32-bit Win 2008, ts works great, but the customer needs to upgrade their ad to win 2008 64 bit. Waiting for your valuable answers.

    Concerning

    Dietsch

    Dietsch,

    It's supported (R2 and Enterprise only!). Check table 7 on this page:

    http://www.Cisco.com/en/us/docs/security/NAC/appliance/support_guide/agntsprt.html#wp66672

    HTH,

    Faisal

  • Supported Macintosh SSO in the NAC version 4.7.2

    Is it possible to do SSO with a Macintosh uses the last agent and NAC version 4.7.2.

    (I have not seen documentation so be it).

    Thank you!

    Bob

    Bob,

    Yes SSO VPN.

    SSO AD No.

    HTH,

    Faisal

  • Integration of Cisco ACS and Cisco NAC Manager - downloadable ACLs

    Hello

    I have Setup Cisco NAC in my environment. These are all works well. The users themselves will get authenticated via Cisco NAC Manager. The Cisco NAC Manager meets with Cisco ACS for the part of the user database. These are all works well. I would like to activate downloadable ACLs. I tried to use the CISCO-AV-PAIR method and creating a downloadable ACL entry in the shared components, but nothing works. It's either I'm doing wrong or this configuration of the mine does not support downloadable ACLs? Please advice kindly.

    Kind regards

    RAM

    + 6 012-2918870

    Hello

    It is not possible.

    You cannot push the ACL in the NAC manager.

    If you make the Radius of NAC authentication manager, you can do is create roles the NAC Manager, and on the roles you define traffic strategies.

    Using the Radius attributes you can then map users to roles.

    Please, take a look at this:

    http://www.cisco.com/en/US/docs/security/nac/appliance/configuration_guide/48/cam/m_auth.html#wp1158789.

    HTH,

    Tiago

    --

    If this helps you or answers to your question if it you please mark it as 'responded' or write it down, if other users can easily find it.

  • ACS NAC 5.2 comments Sponor Radius Authentication

    For some reason, I can't get the Hall "sponsors" for authentication on the server of comments of the NAC (2.0.2) using ACS 5.2 via Radius.

    I managed to find a way to get feedback from the NAC authentication Radius for 'Administrator' to work by adding the value of custom RADIUS IEFT-6 under...

    • Elements of strategy
    • Authorization & permissions
    • Access to the network
    • Authorization profiles

    I added a strategy & tab attributes Radius... I manually entered an attribute that looks like the following:

    • Dictionary type: = IETF RADIUS
    • The RADIUS attribute: = Type of Service
    • Type of attribute: = enumeration
    • Attribute value: = static
    • Value = "administrative".

    Then I created an access policy... I looked for an ad group specific - result = 'Name of custom political upstairs'...

    All this works fine... the Docs of the NAC comments you say the Radius server must return a value of IETF-6...

    When he enters in the sponsor section, it does not tell you the value of your server Radius must return... so just to smile, instead of 'Name custom top political', I tried "Allow access"... I tried the 'name of the custom policy above "...  Don't know what else to try to get this working... Anyone have any ideas?

    This is a similar to the document I'm following:

    http://www.Cisco.com/en/us/docs/security/NAC/guestserver/configuration_guide/20/nacguestsrvr.PDF

    Page 68 refers to the "Sponsor configuration authentication" Ray... it just tell you to change the order of authentication & add the Radius server...

    Use NAS prompt (7) instead of administrative (6) for users of sponsor.

    -Jesse

  • What is the difference between Cisco NAC and ACS?

    I am currently part of a new construction project and my Cisco account manager and sales engineer recommend Cisco NAC for our new MDF. I'm confused because I don't clearly know the difference between a Cisco ACS and the NAC. What is the difference?

    Thank you

    Chris

    Chris,

    The two are completely different, maybe the sales rep could present you with more information and application. Each offers a variety of services tailored to the specific needs. I think that we need to read more in depth on the proceeds of the NAC. NAC seems an excellent solution for authentication authorization but other regulatory compliance.

    When you see ask your representative to sales for more information/demo.

    ACS is more widely use as a central point to access control to network devices routers, an example is for acs accounting management and the authority to order on all devices on the network using acs as RADIUS server. Considering that the NAC is over a central point of safety inspection on earlier systems of access to your network by via LAN or outside, an example of these respected regulatory defined could be inspections could be virus definition checks before getting lan access thus preventing access to the LAN if the system does not have regulatory compliance defined in NAC access is denied. Another example could be the unknown local host connections etc... So, it seems that NAC is a much broader product that provides endpoint security internal, not only the authentication authorization as acs... ACS has been there for a long time, NAC is rather new product.

    NAC

    http://www.Cisco.com/en/us/NetSol/ns466/networking_solutions_package.html

    http://www.Cisco.com/en/us/solutions/collateral/ns340/ns394/ns171/ns466/ns617/net_qanda0900aecd800fdd6f_ns466_Networking_Solutions_Q_and_A.html

    ACS

    http://www.Cisco.com/en/us/products/sw/secursw/ps5338/index.html

    Rgds

    Jorge

Maybe you are looking for

  • Apple Watch

    During the year of market my Apple Watch sometimes sounds and closes the session without asking for confirmation.  Any ideas on what goes wrong and how to fix?

  • How do I update my Iphone 5 c when he says that there is an error?

    My iphone 5 c - ios8.0.2 is need to be updated, but when I click on updates there is a message that says unable to verify the update and that an error has occurred.

  • Customize does not work

    Not able to use the customization works after right click on a blank section of the band to tabs and select Customize... The window customize the toolbar doesn't Pern.

  • From photos of the new software 'Photos '.

    Hello I have just updated the OS on my imac in the OSX El Capitan, and it changed my iphoto for pictures library. Since then if I write an email and want to attach a picture to it or add it to a Web site or use it in a drawing program the only way I

  • by selecting the correct format during extraction

    ripping in windows media player