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 

• 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 EMS, open the SIOP port number and the TCP port number 15011.

• If the ORB Notification Service is enabled via the event-notif-service command, you can set 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.

configure 
   orbem 
      iiop-transport 
      iiop-port iiop_port_number 
      event-notif-iiop-port iiop_notif_port 
      end 

• If you are using the Secure Sockets Layer (SSL) option, do not enable the IIOP transport parameter.

• You configure the ORBEM interface to use SSL by specifying a certificate and private key.

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 
   snmp mib mib_name 
   snmp runtime-debug [ debug-tokens token_id token_id token_id...token_id 
   end 

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

• An snmp 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, an EMS may only process SNMP version 1 (SNMPv1) and SNMP version 2c (SNMPv2c) traps. If the SNMP target you are configuring is the EMS application, use the snmp target command to configure use of 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 notif-threshold command configures the number of SNMP notifications that need to be generated for a given event and the number of seconds in the monitoring window size (default = 300), before the notification is propagated to the SNMP users (default = 300).

• 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 associated SNMP entities, thus providing a security association between the two for the sending and receiving of data.

• The snmp user name is for SNMP v3 and is optional. There are numerous keyword options associated with this command.

• Use the snmp mib command to enable other industry standard and Cisco MIBs. By default only the STARENT-MIB is enabled.

• By default SNMP runtime debugging always runs and consumes CPU cycles for event logging. To control CPU usage you can set no snmp runtime-debug to disable runtime debugging. An option to this command allows you to specify SNMP token values that will locate and parse specified MIBs.