eG Administration
 

Modify an SNMP Manager

Some environments may already be using network-monitoring systems such as HP OpenView, Tivoli NetView, etc., for monitoring their networks and systems. Administrators of such environments may desire that eG Enterprise's alarms be reported to their existing alarm consoles. By configuring the eG manager to send eG alarms as SNMP traps to one/more SNMP management consoles in an environment, you can enable eG Enterprise to support the integrated display and tracking of alarms from a single monitoring console.

To modify the SNMP managers/trap receivers to which the eG manager needs to send SNMP traps, do the following:

  1. To modify a new SNMP management console, click the Modify an SNMP Manager tab.

  2. The IP address of the SNMP manager on which the SNMP manager application is executing has to be provided in the SNMP manager text box. The port number on which the SNMP manager is listening for traps from the eG manager is specified in the SNMP manager port field.

  3. By default, the eG agent supports SNMP version 1. Accordingly, the default selection in the SNMP version list is v1. However, if a different SNMP framework is in use in your environment, say SNMP v2 or v3, then select the corresponding option from this list.

  4. The SNMP community field appears only if the SNMP version chosen is 1 or 2. Here, specify the community string that is used by an eG manager to report alarm information via SNMP to an SNMP manager.

  5. If the SNMPVERSION is 3, then you will have to specify the following parameters:

    • Engine ID: Specify the engine ID of the trap sender. This should be in hexadecimal - i.e., should begin with “0x”.
    • User name: As SNMPv3 traps require authentication, specify a valid user name here.
    • Authentication password: Enter the password of the above-mentioned User name.
    • Confirm password: Confirm the Authentication Password by retyping it here.
    • Authentication type: Choose the authentication algorithm using which SNMP v3 converts the specified User name and Authentication password into a 32-bit format to ensure security of SNMP transactions. You can choose between the following options:

      • MD5 - Message Digest Algorithm
      • SHA - Secure Hash Algorithm

    • Encrypt flag: By default, the eG manager does not encrypt SNMP traps. Accordingly, this parameter is set to No by default. To ensure that SNMP traps sent by the eG manager are encrypted, select the Yes option.
    • Encrypt type: If the Encrypt flag is set to Yes, then you will have to mention the encryption type by selecting an option from the Encrypt type list. SNMP v3 supports the following encryption types:

      • DES - Data Encryption Standard
      • AES - Advanced Encryption Standard

    • Encrypt password: Specify the encryption password here.

    • Confirm password: Confirm the Encrypt password by retyping it here.

  6. Next, select one or more of the check boxes from the Alarm types section, to indicate your preference in terms of the priority of problems for which you wish to receive alerts via the SNMP manager console. For instance, if you choose Critical, you would receive critical priority alarms alone and not the other types. Normal alerts are generated by the eG system as and when a problem is corrected.

  7. Finally, click the Update button to add the new trap receiver.