Cisco Cisco Clean Access 3.5

See also 

With release 3.5, you can configure the Clean Access Manager to be managed/monitored by an SNMP 
management tool (such as HP OpenView). This release is intended to provide minimal manageability 
using SNMP (v1). It is expected that future releases will have more information/actions exposed via 
SNMP. 

With release 3.5, you can configure the Clean Access Manager for basic SNMP polling and alerting 
through Monitoring > SNMP. Note that SNMP polling and alerts are disabled by default. Clicking the 
Enable button under Monitoring > SNMP activates the following features:

SNMP Polling — If an SNMP 

rocommunity

 (“Read-only community”) string is specified, the Clean 

Access Manager will respond to 

snmpget

 and 

snmpwalk

 requests with the correct community string. 

SNMP Traps — The Clean Access Manager can be configured to send traps by adding trap sinks. A 
trap sink is any computer configured to receive traps, typically a management box. All traps sent are 
version 1 (v1) traps. A copy of each trap will be sent to each trapsink.

When enabled, the SNMP module monitors the following processes:

SSH Daemon

Postgres Database

Clean Access Manager

Apache Web Server

The Clean Access Manager also sends traps in the following cases:

When the Clean Access Manager comes online.

When the Clean Access Manager shuts down.

When the Clean Access Manager gains or loses contact with any Clean Access Servers it manages.

When the SNMP service starts (a Cold Start Trap is sent). 

This section describes the following:

1.

0 instead of * shows the most recent log.

2.

Starting with 3.5(5), Switch Management events for notifications received by the CAM from switches are no longer written 
to the web Event Log. They are instead written only to the logs on the file system (/perfigo/logs/perfigo-log0.log.0). 
Furthermore, these events are written to disk only when the log level is set to INFO or finer.