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

eSight V300R010C00SPC200, 300, and 500 Self-Service Integration Guide 10

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 Third-Party System Information

Configuring Third-Party System Information

You must configure the third-party system information so that the SNMP NBI can send messages to the third-party system or receive requests from the third-party system.

The following configuration items must be configured:

  • IP address for receiving traps
  • Port for receiving traps
  • SNMP version used for authentication between the eSight and the third-party system
  • Get and set community (for SNMPv1 or SNMPv2c)
  • Security user name, authentication password, and encryption password (for SNMPv3)
  • Alarm severity filtering
  • Alarm category filtering
  • NE type filtering
  • Third-Party System for interconnecting with resource information

You can configure the third-party system for interconnecting with resource information in the eSight installation directory/AppBase/etc/nbi/snmp/snmpagent.xml.

The community names and passwords in the configuration file must be cipertext. Before entering the community names or passwords, use GenerateNBPass to encrypt them.

To ensure consistency of the community names and passwords between the third-party system and the configuration, notify the third-party system maintenance personnel of the community names and passwords before encryption and the method of using GenerateNBPass.

An SNMP V3's user name cannot be the same as Authentication password and Encryption password.

The community names and passwords must meet the following requirements:

  • Combination of at least three of the following characters:
    • lowercase letters
    • uppercase letters
    • digits
    • special characters: !"#$%&'()*+,-./:;<=>?@[\]^`{_|}~ and space
  • A string of 8 to 32 characters and can't be composed of repeat substring such as "Ab_dAb_dAb_d".
  • To use GenerateNBPass to encrypt data on Linux, run the following commands:

    1>cd eSight installation directory/AppBase/app/nbi/bin

    2>./GenerateNBPass -e

    3>Enter the password and re-enter the password according to the prompt.

    The command output is similar to the following information, where, contents next to

    Encrypt password result: are the encrypted data:

    Encrypt password result: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
  • To use GenerateNBPass.bat to encrypt data on Windows, run the following commands:

    1>cd /d eSight installation directory/AppBase/app/nbi/bin

    2>GenerateNBPass.bat -e

    3>Enter and confirm the new password as prompted.

    The command output is similar to the following information, where, contents next to

    Encrypt password result: are the encrypted data:

    Encrypt password result: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Configuration Item

<template name="template">
<param name="IPAddress"></param>
<param name="Port"></param>
<param name="Version"></param>
<community name="community1">
<param name="Read"></param>
<param name="Write"></param>
</community>
<param name="V3User"></param>
<param name="AuthPassword"></param>
<param name="PrivPassword"></param>
<alarmlevel name="alarmlevel">
<param name="Critical"></param>
<param name="Major"></param>
<param name="Minor"></param>
<param name="Warning"></param>
</alarmlevel>
<category name="category">
<param name="Event"></param>
<param name="Fault"></param>
<param name="Recover"></param>
<param name="Acknowledge"></param>
<param name="Unacknowledge"></param>
<param name="Change"></param>
</category>
<param name="NETypeFilter"></param>
<param name="NEFDNFilter"></param>
</template>

Parameter

Parameter

Configuration Item Path

Description

Default Value

IPAddress

snmpagent /nmsinfo/IPAddress

Indicates the IP address or host name of the third-party system used to receive traps.

-

Port

snmpagent/nmsinfo/Port

Indicates the port of the third-party system used to receive traps. The IP address and port jointly determine the destination of real-time alarm traps, alarm synchronization result traps, and heartbeat traps.

-

Version

snmpagent/nmsinfo/Version

Indicates the SNMP version.

  • 1: SNMPv1
  • 2: SNMPv2c
  • 3: SNMPv3

-

Suggest using SNMPv3.

Read

snmpagent/nmsinfo/community1/Read

Indicates the get community required when SNMPv1 or SNMPv2c is used.

The community name must be encrypted before being entered.

-

Write

snmpagent/nmsinfo/community1/Write

Indicates the set community required when SNMPv1 or SNMPv2c is used.

The community name must be encrypted before being entered.

-

Suggest configuring different as get community.

V3User

snmpagent/nmsinfo/V3User

Indicates the security user name required when SNMPv3 is used.

-

AuthPassword

snmpagent/nmsinfo/AuthPassword

Indicates the authentication password of the third-party system user. It is required when SNMPv3 authentication is available. The authentication password must be encrypted before being entered.

-

PrivPassword

snmpagent/nmsinfo/PrivPassword

If SNMPv3 is used and the security level is Auth and Priv, the password must be encrypted. The password must be encrypted before being entered.

-

Suggest configuring different as authentication password.

Critical

snmpagent/nmsinfo/ alarmlevel/Critical

Specifies whether critical alarms are reported.

  • 0: Critical alarms are not reported.
  • 1 or blank: Critical alarms are reported.

-

Major

snmpagent/nmsinfo/alarmlevel/Major

Specifies whether major alarms are reported.

  • 0: Major alarms are not reported.
  • 1 or blank: Major alarms are reported.

-

Minor

snmpagent/nmsinfo/alarmlevel/Minor

Specifies whether minor alarms are reported.

  • 0: Minor alarms are not reported.
  • 1 or blank: Minor alarms are reported.

-

Warning

snmpagent/nmsinfo/alarmlevel/Warning

Specifies whether warning alarms are reported.

  • 0: Warning alarms are not reported.
  • 1 or blank: Warning alarms are reported.

-

Event

snmpagent/nmsinfo/category/Event

Specifies whether events are reported.

  • 0: Events are not reported.
  • 1 or blank: Events are reported.

-

Fault

snmpagent/nmsinfo/category/Fault

Specifies whether fault alarms are reported.

  • 0: Fault alarms are not reported.
  • 1 or blank: Fault alarms are reported.

-

Recover

snmpagent/nmsinfo/category/Recover

Specifies whether clear alarms are reported.

  • 0: Clear alarms are not reported.
  • 1 or blank: Clear alarms are reported.

-

Acknowledge

snmpagent/nmsinfo/category/Acknowledge

Specifies whether acknowledged alarms are reported.

  • 0: Acknowledged alarms are not reported.
  • 1 or blank: Acknowledged alarms are reported.

-

Unacknowledge

snmpagent/nmsinfo/category/Unacknowledge

Specifies whether unacknowledged alarms are reported.

  • 0: Unacknowledged alarms are not reported.
  • 1 or blank: Unacknowledged alarms are reported.

-

Change

snmpagent/nmsinfo/category/Change

Specifies whether change alarms are reported.

  • 0: Change alarms are not reported.
  • 1 or blank: Change alarms are reported.

-

NETypeFilter

snmpagent/nmsinfo/NETypeFilter

Indicates the device type for which alarms are not reported. By default, this parameter is left blank, indicating that alarms for all devices are reported. Multiple device types can be configured, which are separated by commas (,).

-

NEFDNFilter

snmpagent/nmsinfo/NEFDNFilter

Indicates the NE DN for which alarms are not reported. By default, this parameter is left blank, indicating that alarms for all devices are reported. Users can specify the NEs whose alarms are not reported. Users can set one or more NEs and separate NE DNs with a semicolon (;).

-

MaintenanceAlarmFilter

snmpagent/nmsinfo/MaintenanceAlarmFilter

Specifies whether maintenance alarms are filtered. Currently this configuration item is not supported.

-

  • In the configuration item path in the preceding table, nmsinfo can be nmsinfo1, nmsinfo2, nmsinfo3...., or nmsinfo10. The current configuration file provides only a template reference for the third-party system information and cannot be directly used. You need to add nmsinfo to configure the third-party system configuration. If you want to use the nmsinfo examples in the configuration file, you need to delete the comment tag (<!-- -->) because the content in the comment tag is invalid by default.
  • To configure multiple third-party system users, you are advised to set different read-write community names (v1 or v2) for them, use different user names (v3), or ensure that not all user names are identical. If not all read-write community names (v1 or v2) are identical, duplicate user names (v3) exist, and the passwords for authentication and encryption are different, the interworking may fail for some users.

Configuration example for SNMPv1 or SNMPv2c:

<nmsinfo name="nmsinfo1">
<param name="IPAddress">10.66.51.0</param>
<param name="Port">9997</param>
<community name="community1">
<param name="Read">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</param>
<param name="Write">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</param>
</community>
<param name="Version"></param> <!--Set this parameter to 1 or 2.-->
<alarmlevel name="alarmlevel">
<param name="Critical">1</param>
<param name="Major">1</param>
<param name="Minor">1</param>
<param name="Warning">1</param>
</alarmlevel> <category name="category">
<param name="Event">1</param>
<param name="Fault">1</param>
<param name="Recover">1</param>
<param name="Acknowledge">1</param>
<param name="Unacknowledge">1</param>
<param name="Change">1</param> </category>
<param name="NETypeFilter">BSC6900,DBS390</param>
<param name="NEFDNFilter">OS=1</param>
<param name="MaintenanceAlarmFilter"></param>
</nmsinfo>

Configuration example for SNMPv3:

<nmsinfo name="nmsinfo1">
<param name="IPAddress">10.66.50.253</param>
<param name="Port">9997</param>
<param name="Version">3</param>
<param name="V3User">nbi</param>
<param name="AuthPassword">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</param>
<param name="PrivPassword">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</param>
<alarmlevel name="alarmlevel">
<param name="Critical">1</param>
<param name="Major">1</param>
<param name="Minor">1</param>
<param name="Warning">1</param>
</alarmlevel> <category name="category">
<param name="Event">1</param>
<param name="Fault">1</param>
<param name="Recover">1</param>
<param name="Acknowledge">1</param>
<param name="Unacknowledge">1</param>
<param name="Change">1</param> </category>
<param name="NETypeFilter">BSC6900,DBS390</param>
<param name="NEFDNFilter">OS=1</param>
<param name="MaintenanceAlarmFilter"></param>
</nmsinfo>

Configuring the Upper-Layer NMS to Query Device and Link Information

Information about interconnected devices and links is configured in the <Installation directory>/AppBase/etc/oms.nbi/nbi.xml file on the upper-layer NMS, and other SNMP parameters are configured in the <Installation directory>/AppBase/etc/nbi/snmp/snmpagent.xml file.

The IP address must be configured as that of the upper-layer NMS in the snmpagent.xml file. Otherwise, eSight cannot correctly respond to SNMP requests from the IP address.

The following table describes configuration items of resource information on the upper-layer NMS.

Configuration Item

Description

Effective Mode

Reference Configuration

NmsinfoName

Indicates information about the upper-layer NMS, that is, the name value of the nmsinfo configuration item in <Installation directory>/AppBase/etc/nbi/snmp/snmpagent.xml or IP address of the upper-layer NMS.

Restart eSight.

Data type: String

Value Range:

  • name value of the nmsinfo configuration item in <Installation directory>/AppBase/etc/nbi/snmp/snmpagent.xml
  • Valid IP address

Default value: nmsinfo1

Translation
Download
Updated: 2019-10-30

Document ID: EDOC1100044386

Views: 15802

Downloads: 83

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