> Configuring Management Settings
> This chapter provides instructions for configuring management options such as Object Request Broker Element Management (ORBEM) and Simple Network Management Protocol (SNMP).
> Configuring ORBEM Settings Overview
> The system can be managed by a Common Object Broker Request Architecture (CORBA)-based software application called the Web Element Manager.
> In order for the system to communicate with the server running the Web Element Manager application, you mus configure the ORBEM settings.
> Important: Commands used in the configuration samples in this section provide base functionality. The most common commands and keyword options are presented. In many cases, other optional commands and keyword options are available. Refer to the Command Line Interface Reference for information about all commands.
> Configure the system to communicate with the Web Element Manager:

> Step 1 | Set client ID parameters and configure the STOP/TCP port settings by applying the example configuration in the Configuring Client and Port Parameters section.

> Step 2 | Configure Internet Inter-ORB Protocol (IIOP) transport parameters by applying the example configuration in the Configuring Internet Inter-ORB Protocol (IIOP) Transport Parameters section.

> Step 3 | View your new ORBEM configuratioini by following the steps in the Verifying ORBEM Parameters section.

> Step 4 | Save the configuration as described in the Verifying and Saving Your Configuration chapter.

> Configuring Client and Port Parameters
> Use the following example to set client ID parameters and configure the SIOP/TCP port settings:
> configure
> orbem
> client id encrypted password <password>
> max-attempt <number>
> session-timeout <time>
> siop-port <port_number>
> event-notif-siop-port <siop_notif_port>
> event-notif-service
> end
> Notes:

> • | You can issue the client id command multiple times to configure multiple clients.

> • | If a client ID is de-activated due to reaching the configured maximum number of attempts, use the activate client id command to reactivate it.

> • | If a firewall exists between the system and the Web Element Manager, open the SIOP port number and the TCP port number 15011.

> • | If the ORB Notification Service is enabled (event-notif-service), you can configure filters to determine which events are to be sent. By default, the Service sends all error and higher level events, “info” level events for the ORBS facility, CLI command logs, and license change logs. Optionally, configure a filter by including the event-notif-service filter command. Enter this command for each filter you need to configure.

> Configuring Internet Inter-ORB Protocol (IIOP) Transport Parameters
> Use the following example to configure IIOP transport parameters that enable ORB-based management to be performed over the network:
> configure
> orbem
> iiop-transport
> iiop-port <iiop_port_number>
> event-notif-iiop-port <iiop_notif_port>
> end
> Notes:

> • | If you are using the Secure Sockets Layer (SSL) option, do not enable the IIOP transport parameter. The Web Element Manager’s default process enforces SSL.

> Verifying ORBEM Parameters

> Step 1 | Enter the following to verify that the client was configured properly:

> show orbem client table
> This command lists the configured ORBEM clients and displays their state and privileges.

> Step 2 | Verify the ORBEM parameter configuration by entering the following command:

> show orbem status
> The following displays a sample of this command’s output.
> Service State : On
> Management Functions : FCAPS
> IOP URL : 192.168.1.150
> SSL Port : 14131
> TCP Port : 14132
> Notification SSL Port : 7777
> Notification TCP Port : 7778
> Session Timeout : 86400 secs
> Max Login Attempts : 5
> IIOP Transport : On
> Notification : On
> Debug Level : Off
> IDL Version Check : On
> Number of Current Sessions : 1
> Number of Event Channels Open : 0
> Number of Operations Completed : 2895
> Number of Events Processed : 0
> Avg Operation Processing time : 87214 usecs
> (last 1000) : 87950 usecs
> Configuring System SNMP Settings
> The system uses the SNMP to send traps or events to the Web Element Manager server or an alarm server on the network.
> In order for the system to communicate with those devices, configure SNMP settings.
> Important: Commands used in the configuration samples in this section provide base functionality. The most common commands and keyword options are presented. In many cases, other optional commands and keyword options are available. Refer to the Command Line Interface Reference for complete information.
> To configure the system to communicate with the WEM server or an alarm server, enter:
> [local]host_name#

> Step 1 | Configure SNMP parameters such as UDP port, and alarm server target by applying the example configuration in the Configuring SNMP and Alarm Server Parameters section.

> Step 2 | To view your new SNMP configuration, follow the steps in the Verifying SNMP Parameters section.

> Step 3 | Save the configuration as described in the Verifying and Saving Your Configuration chapter.

> Configuring SNMP and Alarm Server Parameters
> Use the following example to set SNMP and alarm server parameters:
> configure
> system contact <contact_name>
> system location <location_name>
> snmp authentication-failure-trap
> snmp community <community_string>
> snmp server port <port_number>
> snmp target <name ip_address>
> snmp engine-id local <id_string>
> snmp notif-threshold <value> low <low_value> period <time_period>
> snmp user <user_name>
> end
> Notes:

> • | The system contact is the name of the person to contact when traps are generated that indicate an error condition.

> • | A community string is a password that allows access to system management information bases (MIBs).

> • | The system can send SNMPv1, SNMPv2c, or SNMPv3 traps to numerous target devices. However, the Web Element Manager can only process SNMP version 1 (SNMPv1) and SNMP version 2c (SNMPv2c) traps. If the SNMP target you are configuring is the Web Element Manager application, configure this command to use version 1 or version 2c. Issue this command as many times as you need to configure multiple targets. If you configure multiple targets, generated alarms are sent to every configured target.

> • | The snmp engine-id local command is optional. It is only required if your network requires SNMP v3 support. The engine ID uniquely identifies the SNMP engine and the SNMP entitiy(ies) thus providing a security association between the two for the sending and receiving of data.

> • | SNMP user name is for SNMPv3 and is optional. There are numerous keyword options associated with this command.

> Important: SNMPv3 traps are not supported for Web Element Management application.
> Verifying SNMP Parameters

> • | To verify that the SNMP server information is correctly configured, enter the following command:

> show snmp server
> The following displays a sample output.
> SNMP Server Configuration:
> Server State : enabled
> SNMP Port : 161
> sysLocation : chicago
> sysContact : admin
> authenticationFail traps : Enabled
> EngineID : 123456789
> Alert Threshold : 100 alerts in 300 seconds
> Alert Low Threshold : 20 alerts in 300 seconds

> • | Verify that the SNMP community(ies) were configured properly by entering the following command:

> show snmp communities
> The output of this command lists the configured SNMP communities and their corresponding access levels.

> • | Verify that the SNMP transports are configured properly by entering the following command:

> show snmp transports
> The following displays a sample output:
> Target Name: rms1
> IP Address: 192.168.1.200
> Port: 162
> Default: Default
> Security Name: public
> Version: 1
> Security:
> View:
> Notif Type: traps
> Controlling SNMP Trap Generation
> The system uses SNMP traps to indicate that certain events have occurred. Refer to the SNMP MIB Reference for a complete listing of the traps supported by the system and their descriptions.
> By default, the system enables the generation of all traps. However, you can disable individual traps to allow only traps of a certain type or alarm level to be generated. This section provides instructions for disabling/enabling SNMP traps.
> Important: Commands used in the configuration samples in this section provide base functionality. The most common commands and keyword options are presented. In many cases, other optional commands and keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands.
> To configure SNMP trap generation:

> Step 1 | Set parameters by applying the following example configuration:

> Configure
> snmp trap suppress
> snmp trap suppress <trap_name1> <trap_name2> ... <trap_nameN>
> Important: If at a later time you wish to re-enable a trap that was previously suppressed, use the snmp trap enable command. Use the following command to specify which traps go to a specific trap server:
> snmp trap enable <trap_name1> <trap_name2> ... <trap_nameN> target <target-name>

> Step 2 | Save the configuration as described in the Verifying and Saving Your Configuration chapter.

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883