Generate SNMP Traps

This section describes the process for generating specific types of SNMP traps. SNMP must be set up and running on the server in order for the individual traps to generate. Follow Set Up SNMP Traps for instructions on how to set up your system to generate SNMP traps.


Note
The processing time for individual SNMP traps varies depending on which trap you are attempting to generate. Some SNMP traps may take up to a few minutes to generate.


Generate SNMP Traps

SNMP Traps

Process

ccmPhoneStatusUpdate

To trigger the ccmPhoneStatusUpdate trap:

  1. In the ccmAlarmConfig Info mib table, set ccmPhoneStatusUpdateAlarmInterv (1.3.6.1.4.1.9.9.156.1.9.4) = 30 or higher.

  2. Login to Cisco Cisco Unified Communications Manager Administration.

  3. For a phone that is in service and that is registered to Cisco Cisco Unified Communications Manager, reset the phone.

    The phone deregisters, and then reregisters, generating the ccmPhoneStatusUpdate trap.

ccmPhoneFailed

To trigger the ccmPhoneFailed trap:

  1. In the ccmAlarmConfigInfo mib table, set ccmPhoneFailedAlarmInterval (1.3.6.1.4.1.9.9.156.1.9.2) =30 or higher.

  2. In Cisco Cisco Unified Communications Manager Administration, change the MAC address of the phone to an invalid value.

  3. In Cisco Cisco Unified Communications Manager Administration, reregister the phone.

  4. Set the phone to point to the TFTP server A and plug the phone in to a different server.

ccmGatewayFailed

To trigger the ccmGatewayFailed SNMP trap:

  1. Confirm that ccmGatewayAlarmEnable (1.3.6.1.4.1.9.9.156.1.9.6) is set to true.

  2. In Cisco Cisco Unified Communications Manager Administration, change the MAC address of the gateway to an invalid value.

  3. Reboot the gateway.

ccmGatewayLayer2Change

To trigger the ccmGatewayLayer2Change trap on a working gateway where layer 2 is monitored (for example, the MGCP backhaul load):

  1. In the ccmAlarmConfig Info mib table, set ccmGatewayAlarmEnable (1.3.6.1.4.1.9.9.156.1.9.6.0) = true.

  2. In Cisco Cisco Unified Communications Manager Administration, change the MAC address of the gateway to an invalid value.

  3. Reset the gateway.

MediaResourceListExhausted

To trigger a MediaResourceListExhausted trap:

  1. In Cisco Cisco Unified Communications Manager Administration, create a media resource group that contains one of the standard Conference Bridge resources (CFB-2).

  2. Create a media resource group list that contains the media resource group that you created.

  3. In the Phone Configuration window, set the Media Resource Group List field to the media resource group lis that you just created.

  4. Stop the IP Voice Media Streaming service. This action causes the ConferenceBridge resource (CFB-2) to stop working.

  5. Make conference calls with phones that use the media resource group list. The "No Conference Bridge available" message appears in the phone screen.

RouteListExhausted

To trigger a RouteListExhausted trap:

  1. Create a route group that contains one gateway.

  2. Create a route group list that contains the route group that you just created.

  3. Create a unique route pattern that routes a call through the route group list.

  4. Deregister the gateway.

  5. Dial a number that matches the route pattern from one of the phones.

MaliciousCallFailed

To trigger a MaliciousCallFailed trap:

  1. Create a softkey template that includes all available "MaliciousCall" softkeys.

  2. Assign the new softkey template to phones in your network and reset the phones.

  3. Place a call between the phones.

  4. During the call, select the "MaliciousCall" softkey.

ccmCallManagerFailed

To trigger the ccmCallManagerFailed trap:

  1. Run the show process list CLI command to get the Process Identifier (PID) of the CallManager application ccm.

    This command returns a number of processes and their PIDs. You must obtain the PID for ccm specifically since this is the PID that you must stop in order to generate the alarm.

  2. Run the delete process <pid> crash CLI command.

  3. Run the utils core active list CLI command.

The CallManager Failed Alarm is generated when internal errors are generated. These internal errors may include an internal thread quitting due to the lack of CPU, pausing the CallManager server for more than 16 seconds, and timer issues.

Note   

Generating a ccmCallManagerFailed alarm/trap shuts down the CallManager service and generates a core file. To avoid confusion, Cisco recommends that you delete the core file immediately.

syslog messages as traps

To receive syslog messages above a particular severity as traps, set the following two mib objects in the clogBasic table:

  1. Set clogNotificationsEnabled (1.3.6.1.4.1.9.9.41.1.1.2) to true(1). Default value is false(2). For example, snmpset -c <Community String> -v 2c <transmitter ip address> 1.3.6.1.4.1.9.9.41.1.1.2.0 i 1

  2. Set the clogMaxSeverity (1.3.6.1.4.1.9.9.41.1.1.3) to a level that is greater than the level at which you want your traps to be produced. The default value is warning (5).

    All syslog messages with alarm severity lesser than or equal to the configured severity level are sent as traps. For example, snmpset -c <Community String> -v 2c <transmitter ip address> 1.3.6.1.4.1.9.9.41.1.1.3.0 i <value>