Cisco Cisco NAC Appliance 4.1.0
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
12-17
Cisco NAC Appliance - Clean Access Server Installation and Administration Guide
OL-12213-01
Chapter 12 Administer the Clean Access Server
Support Logs and Loglevel Settings
To manually modify the system time:
1.
In the Time form of the Misc tab, either:
2.
Type the time in the Date & Time field and click Update Current Time. The time should be in the
form:
form:
mm/dd/yy hh:ss PM/AM
3.
Or, click the Sync Current Time button to have the time updated by the time servers listed in the
Time Servers field.
Time Servers field.
To automatically synchronize with the time server:
The default time server is the server managed by the National Institute of Standards and Technology
(NIST), at time.nist.gov. To specify another time server:
(NIST), at time.nist.gov. To specify another time server:
1.
In the Time form of the Misc tab type the URL of the server in the Time Servers field. The server
should provide the time in NIST-standard format. Use a space to separate multiple servers.
should provide the time in NIST-standard format. Use a space to separate multiple servers.
2.
Click Update Current Time.
If more than one time server is listed, the CAS tries to contact the first server in the list when
synchronizing. If available, the time is updated from that server. If it is not available, the CAS tries the
next one, and so on, until a server is reached.
synchronizing. If available, the time is updated from that server. If it is not available, the CAS tries the
next one, and so on, until a server is reached.
The CAS will then automatically synchronize time with the configured NTP server at periodic intervals.
To change the time zone of the server system time:
1.
In the Time form of the Misc tab, choose the new time zone from the Time Zone dropdown menu.
2.
Click Update Time Zone.
Support Logs and Loglevel Settings
The Support Logs page on the Clean Access Server is intended to facilitate TAC support of customer
issues. The Support Logs page allows administrators to combine a variety of system logs (such as
information on open files, open handles, and packages) into one tarball that can be sent to TAC to be
included in the support case. Administrators should download these support logs when sending their
customer support request.
issues. The Support Logs page allows administrators to combine a variety of system logs (such as
information on open files, open handles, and packages) into one tarball that can be sent to TAC to be
included in the support case. Administrators should download these support logs when sending their
customer support request.
The Support Logs pages on the CAM web console and CAS direct access web console
(
(
)provide web page controls to configure the level of log detail recorded for troubleshooting
purposes in /perfigo/logs. These web controls are intended as convenient alternative to using the CLI
loglevel
command and parameters in order to gather system information when troubleshooting.
For normal operation, the log level should always remain at the default setting (severe). The log level is
only changed temporarily for a specific troubleshooting time period —typically at the request of the
customer support/TAC engineer. In most cases, the setting is switched from “Severe” to “All” for a
specific interval, then reset to “Severe” after data is collected. Note that once you reboot the CAM/CAS,
or perform the
only changed temporarily for a specific troubleshooting time period —typically at the request of the
customer support/TAC engineer. In most cases, the setting is switched from “Severe” to “All” for a
specific interval, then reset to “Severe” after data is collected. Note that once you reboot the CAM/CAS,
or perform the
service perfigo restart
command, the log level will return to the default setting
(Severe).
Caution
Do not leave the log level set at “All” or “Info” indefinitely, as this will cause the log file to grow very
quickly.
quickly.