This document answers the most frequently asked questions (FAQs) related to Cisco Clean Access Manager. This document is part one of a two part documentation set. Refer to Cisco Clean Access Manager FAQ 2 for part two.
The product names have changed. This table lists both the old and new names:
Old Name | New Name |
---|---|
SmartManager | Clean Access Manager |
SecureSmart Server | Clean Access Server |
SmartEnforcer | Clean Access Agent |
CleanMachinesAPIs | Clean Access APIs |
Refer to the Cisco Technical Tips Conventions for more information on document conventions.
A. There are two solutions:
Provide a link for unregistered or new users to click on from the Login page. The registration page can show up on the right frame. The user can register first, and then obtain their login credentials.
Use attribute mapping in LDAP that indicates if the users are registered or not. If the users are not registered, put them in a particular role (based on the response from LDAP). Then redirect them to a registration web site in order to obtain their login credentials based on the role.
A. Cisco suggests that you set these rules in this order in order to mitigate the need to put individual Windows Update or antivirus update IP addresses:
Allow DNS (your DNS can be internal or external) to resolve the DNS of the update site.
Block all TCP/UDP/ICMP incoming traffic to your internal network.
Enable outbound port 80/443 so traffic can traverse to Windows Update and perform the update.
![]()
Cisco also recommends that you set the Quarantine session timer accordingly (for example, 20 minutes).
![]()
Note: domain-based policy filtering has been added in versions 3.2 and later (allows windowsupdate.microsoft.com in the policy permit).
A. The event log is in the database table name as log_info table.
There are other logs in the Cisco Clean Access Manager:
/var/log/messages - startup
/var/log/dhcplog - dhcp relay, dhcp logs
/tmp/perfigo-log0.log.? - service logs
/perfigo/control/apache/logs/* - ssl, apache error logs
/perfigo/control/tomcat/logs/localhost*. - tomcat, redirect, jsp logs
A. It is located in /perfigo/access/tomcat/webapps/auth/perfigo_ipsec_enforced.jsp on the Cisco Clean Access Server.
A. The remote back up script is on the Cisco Clean Access Manager in the /perfigo/control/bin directory named as pg_backup.
If you run it without any parameters, it tells you how it needs to be used. Usage for the script is:
pg_backup [FTP-Server] [Username] [Password]
A. This can be due to:
If there is a router downstream, the Cisco Clean Access Manager shows the MAC address of the router, as long as the router is ARPing for the IP addresses in question (for example, user's IP). If the router is not (for some reason), then you have 00:00:00:00:00:00 as the MAC address of the user.
If the user comes in from the trusted side (for example, there is no ARP entry for the user on the untrusted side), the Cisco Clean Access Manager shows all zeros.
A. If you do not want your end users to see the certificate warning, get a certificate for the Cisco Clean Access Server, not the Cisco Clean Access Manager.
A. No, you cannot use a certificate that you bought for the Cisco Clean Access Manager on the Cisco Clean Access Server. You need to buy a separate certificate for each Cisco Clean Access Server.
A. Select a date in the future and click the enable/disable box in order to disable the certified timer.
A. You do not need to do this. The license key is kept in the database. It makes its way over to the secondary Manager through database replication.
A. Cisco currently supports Authentication Server clustering and plans to look into Authentication Server Failover in future releases.
A. A bursty factor is used to determine the "capacity" of the bucket. As an example, assume the bandwidth is 100 Kbps and the factor is 2. Therefore, the capacity of the bucket is 100 Kb * 2=200 Kb.
If a user does not send any packet for some time, they have at most 200 Kb tokens in the bucket. Once the user needs to send packets, the user is able to send out 200 Kb packets immediately. Thereafter, the user needs to wait for the tokens to come in at the rate of 100 Kbps to send out additional packets.
One way to think of the fit is that the average rate is 100 Kbps, and the peak rate is approximately 200 Kbps. Therefore, it is good for bursty applications such as web browsing.
A. If you have a non-site license, inform Cisco Technical Support of the change on the MAC address for a new license key issuance. For a failover pair, provide both MAC addresses. If you have a site license, you do not need to inform Cisco Technical Support.
A. This can be a case of the NICs not being recognized as Broadcom NICs. Try to:
Console into the box.
Issue the cd /lib/modules/kernel-2.4.9-perfigo/drivers/addon/bcm5700 command.
Issue the insmod ./bcm5700.o command.
If these commands result in no errors, issue the vi /etc/modules.conf command and add these two lines:
alias eth0 bcm5700 alias eth1 bcm5700
A. On the primary Cisco Clean Access Manager from the root prompt, enter this command:
root>psql –h 127.0.0.1 –U postgres controlsmartdbYou are now in the database shell - controlsmartdb=#.
Examples:
Enter this command to get the number of users logged on per Cisco Clean Access Server:
select count(*) from user_info where ss_key= (select ss_key from securesmart_info where ss_ip='x.x.x.x');Note: Make sure you enter the trailing semi-colon. Change the IP address to get information for the other Cisco Clean Access Servers.
Enter this command to get the number of users logged on per role:
select count(*) from user_info where role_id= (select role_id from role_info where role_name='Wireless');Note: Replace the role name for information related to the other roles.
Enter this command to get the event logs:
select * from report_info;
A. For iPhones, you can configure the device filter option under Device Management > Filters > Devices > New. Once you include the list of MAC addresses that you want to bypass, you must specify ALLOW for the Access Type in order to permit the access to those specific devices. Refer to Configure Device Filters for more information.