100CCM Installer/User Guide

Appendix C: Supported Traps

The CCM appliance supports the following MIB2 traps:

authenticationFailure

linkUp

linkDown

coldStart

Table C.1 lists the supported enterprise traps. The Avocent web site (www.avocent.com) contains the complete trap MIB.

Table C.1: CCM Appliance Enterprise Traps

Trap

Description and Variable(s)

AggregatedServer StatusChanged

The status of one or more servers (connections paths) has changed. The appliance always sends this trap upon bootup. Thereafter, it sends the trap when there is a change in connection path status, and will include only those paths whose status has changed.

Variable(s): connection path(s)

ConfigurationFile

The CCM appliance has loaded a configuration file. This trap applies to

AVWorks software.

Loaded

Variables: initiating username and name of loaded file

 

 

 

 

The CCM appliance has received a command to set itself to factory default values.

FactoryDefaultsSet

(The appliance sends this trap after receiving the command, but before actually

 

reverting to factory default values.)

 

 

 

An image upgrade has ended.

ImageUpgradeResults

Variables: result (successful or error code), initiating username, image type (boot or

application), upgrade version number and running version number (if the upgrade

 

 

was successful, the two version numbers will match)

 

 

 

The CCM appliance has started an image upgrade.

ImageUpgradeStarted

Variables: initiating username, image type (boot or application), new version

 

number, current version number

 

 

NFSDisableRqstd

A request has been made to disable NFS.

Variable: requesting username

 

 

 

NFSEnableRqstd

A request has been made to enable NFS.

Variable: requesting username

 

 

 

NFSMountedOK

NFS is enabled and the mount operation has completed successfully.

 

 

 

NFS is enabled but repeated mount attempts have failed. No additional mount

NFSMountFailedGave

retries will be performed.

Up

Variables: primary and secondary NFS error codes (see NFS Error Codes and Port

 

Status on page 105)