No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OceanStor BCManager 6.5.0 eReplication User Guide 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring Alarm Reporting to the Upper-Layer NMS

Configuring Alarm Reporting to the Upper-Layer NMS

This operation configures the Trap IP address and alarm reporting parameters for an upper-layer network management system (NMS). After the configuration, alarms of eReplication can be reported to the upper-layer NMS.

Procedure

  1. On the menu bar, select Settings.
  2. In the navigation tree, choose Layered NMS > Trap Settings.
  3. Configure the northbound Trap reporting parameters for the upper-layer NMS and eReplication communicate with each other.

    If the northbound Trap reporting parameters of the upper-layer NMS are changed, those of eReplication must be changed accordingly.

    1. In the Trap Parameters area, configure the northbound Trap reporting parameters for the upper-layer NMS and eReplication communicate with each other. Table 7-7 describes related parameters.

      Table 7-7  Northbound Trap reporting parameters

      Parameter

      Description

      Value

      Username

      Northbound Trap username used by the upper-layer NMS and eReplication communicate with each other.

      [Value range]

      The name contains 1 to 64 characters.

      [Example]

      user

      Environment Name

      Name of the environment engine.

      [Value range]

      The name contains 1 to 64 characters.

      [Example]

      sa

      Environment Engine ID

      Unique identifier of an SNMP engine. This ID is used together with the environment name to determine an environment that uniquely identifies an SNMP entity. An SNMP message packet is processed only when the environments of the sender terminal and the recipient terminal are the same. Otherwise, the SNMP message packet will be discarded. This parameter supports two input modes:
      • Hexadecimal input mode: The ID must be in the format of #**.**.**. The validity verification involves the value length and each hexadecimal value. The maximum length is 97 characters, including pound signs (#).
      • Non-hexadecimal input mode: Enter the ID directly. The validity verification involves only the length. The maximum length is 32 characters.

      -

      Authentication Protocol

      Protocol used for verifying messages. The parameter value can be HMACMD5, HMAC_SHA1, HMAC_SHA2(SHA256) or no protocol.

      [Example]

      HMAC_SHA2

      NOTE:

      The default value is HMAC_SHA2. HMACMD5 or HMAC_SHA1 is an insecure protocol which may cause security risks. Therefore, HMAC_SHA2(SHA256) is recommended.

      Authentication Password

      If the authentication protocol is used to verify messages, you need to set the authentication password.

      The password complexity requirements are as follows:
      • Contains 8 to 64 characters.
      • Must contain special characters, including !"#$%&'()*+,-./:;<=>?@[\]^`{_|}~ and spaces.
      • Must contain upper-case letters, lower-case letters, and digits.
      • Cannot be the same as the username or the mirror writing of the username.

      Data Encryption Protocol

      Encryption protocol used for encapsulating data. The value can be DES or AES, or no encryption.

      • DES: an international universal encryption algorithm. The key length is 56 bytes.
      • AES: an advanced encryption standard. There are three types of key length: 128 bytes, 192 bytes, and 256 bytes. Different lengths provide different-level security protection.

      [Example]

      AES

      NOTE:

      The default value is AES. DES is an insecure protocol which may cause security risks. Therefore, AES is recommended.

      Data Encryption Password

      If the encryption algorithm is used for encapsulating data, you need to set the data encryption password.

      The password complexity requirements are as follows:
      • Contains 8 to 64 characters.
      • Must contain special characters, including !"#$%&'()*+,-./:;<=>?@[\]^`{_|}~ and spaces.
      • Must contain upper-case letters, lower-case letters, and digits.
      • Cannot be the same as the username or the mirror writing of the username.

    2. Click OK.
  4. Add the Trap IP address of the upper-layer NMS.
    1. In the Trap IP Address area, click Add.
    2. Configure IP Address and Port for the upper-layer NMS to receive alarms.
    3. Click OK.

    NOTE:

    The MIB file needs to be obtained for parsing alarms.

    After deploying BCManager, obtain MIB file Lego-NorthTrap-MIB from directory /opt/BCManager/Runtime/LegoRuntime/mibs.

Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 14729

Downloads: 70

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next