Table Of Contents

Configuring SNMP on the Cisco Unified MeetingPlace Cisco WebEx Node

About SNMP on the Cisco WebEx Node

Requirements for SNMP on the Cisco WebEx Node

Configuring SNMP on the Cisco WebEx Node

Configuring SNMP on the Cisco Unified MeetingPlace Cisco WebEx Node

---

Release 8.5

Revised: April 14, 2013 11:16 pm

Topics in this module include:

•About SNMP on the Cisco WebEx Node

•Requirements for SNMP on the Cisco WebEx Node

•Configuring SNMP on the Cisco WebEx Node

About SNMP on the Cisco WebEx Node

•SNMP versions 2c and 3 are supported.

•Traps are used to report events. See Table 1.

Each major and minor software notification includes an integer exception code and indicates which software module and server reported the alarm. Normally, each alarm instance generates a separate notification. In some cases, however, one specific incident could trigger multiple types of alarms.

Table 1 SNMP Traps for the Cisco WebEx Node

Group ID	Name	Alarm ID	Severity	Description
	System Resource Alarms
1	resUsageNormalEvent	.1.3.6.1.4.1.11435.1.7.6.5	Normal	System Resource Usage normal event.
	resUsageMinorEvent	.1.3.6.1.4.1.11435.1.7.6.6	Minor	System resource Usage minor event.
	resUsageMajorEvent	.1.3.6.1.4.1.11435.1.7.6.7	Major	System Resource Usage major event.
2	wbxSNMPNodeMgrUpEvent	.1.3.6.1.4.1.11435.1.8.3	Normal	Sends out notifications when node manager up.
	wbxSNMPNodeMgrDownEvent	.1.3.6.1.4.1.11435.1.8.4	Major	Sends out notifications when node manager down.
	Eureka Server Alarms
1	servStatusEvent	.1.3.6.1.4.1.11435.2.1.2.3	Major	Notifies the managing application of server status changes. Also carries server IP address, server type, server status, server current time and trap sequence number.
2	servCapacityEvent	.1.3.6.1.4.1.11435.2.1.2.6	Major	Once the usage of server capacity crosses the preset threshold, a trap will be sent out. The trap will also carries the server IP address, server type, server available capacity, server current time and trap sequence number.
3	servDormantEvent	.1.3.6.1.4.1.11435.2.1.2.8	Warning	Occurs if server heartbeat freezes for over two minutes. This notification is sent out along with the server IP address, server type, server status, server current time and trap sequence number.
	servHeartbeatEvent	.1.3.6.1.4.1.11435.2.1.2.9	Normal	Occurs after the server heartbeat resumes. This notification is sent out along with the server IP address, server type, server status, server current time and trap sequence number.
4	winConfigErrorEvent	.1.3.6.1.4.1.11435.2.1.2.10	Major	Sends out this notification in case the error is detected in the centralized wincfg.xml file.
5	daemonStatusEvent	.1.3.6.1.4.1.11435.2.1.2.17	Normal	Sends out notifications after daemon status is changed.

Related Topics

•Alarm and Exception Code Reference for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_technical_reference_list.html

•Alarm Severity Levels in the Using Alarms and Logs on Cisco Unified MeetingPlace module

•Using Alarms and Logs on Cisco Unified MeetingPlace module

Requirements for SNMP on the Cisco WebEx Node

Import the following non-standard MIBs from the Cisco WebEx node:

•WBX-DIABLO-SNMP-MIB.my: Cisco WebEx Diablo server monitoring

•WBX-EUREKA-SNMP-MIB.my: Cisco WebEx Eureka server monitoring

You can download these MIB files by entering the show webex mibs command. This will place the MIB files in your SFTP root directory. You can obtain them by using SCP or SFTP.

Configuring SNMP on the Cisco WebEx Node

Before You Begin

•Upload two non-standard MIBs onto your SNMP manager/server: WBX-DIABLO-SNMP-MIB.my and WBX-EUREKA-SNMP-MIB.my.

•Obtain the SNMP read-only community string.

•Obtain the SNMP manager IP address.

•Plan a maintenance window to allow for Cisco WebEx node services to restart.

Procedure

---

Step 1 SSH to the Cisco WebEx Node, using your wbxadmin credentials.

Step 2 Enter set webex snmp version (NONE|V2|V3) to configure the SNMP version.

Step 3 Enter set webex snmp community [read-community-string] to configure the read-only community.

Step 4 Enter set webex snmp manager [manager-ip-address] to configure the SNMP manager IP address.

Step 5 Enter service webex restart to restart your WebEx Node services.

Step 6 Verify your Cisco WebEx node SNMP Service by entering the following:

show webex snmp

show webex services

my-wbxnode.mydomain.com > show webex snmp

Current Cisco WebEx Node SNMP Configuration

================================================================================

    VERSION:                  V2

    COMMUNITY:                [public]

    TRAP MANAGER:             [192.168.1.101]

--

<B>my-wbxnode.mydomain.com > show webex services</B>

Initializing before action ......  [ Done ]

Checking all services for Node ......

        Checking Node info ...... [ Ok ]

        Checking service for general ......

                Checking service [SSLGW] process [wbxsslgw] ...... [ Running ]

                Checking service [MZM] process [wbxmzm] ...... [ Running ]

                Checking service [CB-1] process [wbxcb-01] ...... [ Running ]

                Checking service [CB-2] process [wbxcb-02] ...... [ Running ]

                Checking service [TA-1] process [wbxapta-01] ...... [ Running ]

                Checking service [TA-2] process [wbxapta-02] ...... [ Running ]

                Checking service [DV-1] process [wbxapdv-01] ...... [ Running ]

                Checking service [DV-2] process [wbxapdv-02] ...... [ Running ]

                Checking service [FS-1] process [wbxapfs-01] ...... [ Running ]

                Checking service [FS-2] process [wbxapfs-02] ...... [ Running ]

                Checking service [POLL-1] process [wbxappoll-01] ...... [ Running ]

                Checking service [POLL-2] process [wbxappoll-02] ...... [ Running ]

                Checking service [MDC] process [wbxdcagt] ...... [ Running ]

        Checking service for SLIM ......

                Checking service [SLIM] process [slimdm] ...... [ Running ]

        Checking service for Monitor ......

                Checking service [ProcessManager] process [snmpd] ...... [ Running ]	<<--- 
Successful Start

                Checking service [ProcessManager] process [wbxurkpm] ...... [ Running ]

                Checking service [ProcessManager] process [wbxurkagt] ...... [ Running ]

                Checking service [ProcessManager] process [wbxcwnpm] ...... [ Running ]

                Checking service [Monitor] process [monitor.sh] ...... [ Running ]

Operation for action[status] is successful !