Using SNMPv1 or SNMPv2c
This section describes how to connect to the eSight using SNMPv1 or SNMPv2c.
Context
To log in to the NE normally through the eSight, you need to enable the SNMP protocol on the NE and add the NE to the eSight.
Procedure
- Use the web-based NMS to configure SNMP parameters for the device. For details, see section Connecting to the Web-based NMS.
- Configure SNMP parameters. Here, SNMPv2c is used as an example. The configurations of SNMPv1 are the same as those of SNMPv2c.Table 1-1 Configuring SNMP parameters
Parameter
Value Range
Description
NMS IP Address
For example: 10.70.35.6
Specifies the IP address of the NMS server that manages NEs over SNMP.
NOTE:This parameter can be set to 0.0.0.0 when the NMS server does not have access control on the terminal IP addresses. In this case, all traps are not reported.
Read/Write Permission
Read Only, Read/Write
Specifies permission for the NMS server to manage alarm and performance data over SNMP.
- Read Only: Indicates that the NMS server has only read permission on NEs, such as viewing alarms and performance data reported by the NEs.
- Read/Write: Indicates that the NMS server has both read and write permission on NEs, such as viewing and processing the alarm and performance data reported by the NEs.
Report SDH Performance Trap
No Report, Report
Specifies whether to report the traps of SDH performance data to the NMS server.
- No Report: Indicates that the NEs do not report the traps of SDH performance data to the NMS server.
- Report: Indicates that the NEs report the traps of SDH performance data to the NMS server.
Report IP Performance Trap
No Report, Report
Specifies whether to report the traps of IP performance data to the NMS server.
- No Report: Indicates that the NEs do not report the traps of IP performance data to the NMS server.
- Report: Indicates that the NEs report the traps of IP performance data to the NMS server.
Report Alarm Trap
No Report, Report
Specifies whether to report alarm traps to the NMS server.
- No Report: Indicates that the NEs do not report alarm traps to the NMS server.
- Report: Indicates that the NEs report alarm traps to the NMS server.
Trap Port
1 to 65535
Specifies the ID of the port through which the trap is reported.
Read Community Name
The string must meet the following rules:
- It is a character string at least consisting of 6 characters.
- It contains at least two types of the following characters:
- Lowercase letter: a-z
- Uppercase letter: A-Z
- Digit: 0-9
- Special character: ` ~ ! @ # $ % ^ & * ( ) - _ = + \ | [ { } ] ; : ' " , < . > / ? or space..
Specifies the name of the read community.
Confirm Read Community Name
Write Community Name
Specifies the name of the write community.
Confirm Write Community Name
Report Trap Version
SNMPV1, SNMPV2C, SNMPV3
Specifies the trap version to report.
Report Trap Community Name
The string must meet the following rules:
- It is a character string at least consisting of 6 characters.
- It contains at least two types of the following characters:
- Lowercase letter: a-z
- Uppercase letter: A-Z
- Digit: 0-9
- Special character: ` ~ ! @ # $ % ^ & * ( ) - _ = + \ | [ { } ] ; : ' " , < . > / ? or space..
Specifies the trap community name to report.
NOTE:You could not specify the Report Trap Community Name if the report trap version has been set as SNMPV3.
Report Trap User Name
String
Specifies the trap user name to report.
- Log in to the eSight from the NMS.
To log in to the eSight, you need to set related parameters on the browser. For details, see Connecting to the Web-based NMS step 2.
- Add the NE to the eSight.
- Add a single NE.
Here, SNMPv2c is used as an example. The configurations of SNMPv1 are the same as those of SNMPv2c.
- Add NEs in batches.
- Configure the SNMP template first, and then configure the SNMP parameters of NE to match the template.
- Automatic discovery of devices.
- Configure the SNMP template first, and then configure the SNMP parameters of NE to match the template.
- Add a single NE.