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 V300R009C00 Operation Guide 09

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).
Principles

Principles

This section describes the SNMP protocol and how to add devices to eSight by configuring SNMP.

SNMP Protocol

This section describes the versions and basic principles of the SNMP protocol.

SNMP Management Model

Figure 12-1 shows an SNMP management model.

Figure 12-1 SNMP management model

An SNMP system consists of four parts: network management system (NMS), agent, MO, and Management Information Base (MIB).

Each managed device contains an agent process, an MIB, and multiple MOs. The NMS interacts with the agent on a managed device. When receiving a command from the NMS, the agent performs the corresponding operation on the MIB in the managed device.

NMS

The NMS is a manager on a network. It monitors and controls network devices using SNMP. The NMS software runs on NMS servers to implement the following functions:

  • Sends requests to agents on managed devices to query or modify parameters.
  • Receives traps from agents on managed devices to learn device status.

Agent

The agent is a process running on a managed device. It maintains data on the managed device, responds to requests from the NMS, and sends management data to the NMS.

  • Upon receiving a request from the NMS, the agent performs the corresponding operation on the MIB and sends the operation result to the NMS.
  • When a fault or an event occurs on the managed device, the agent sends a notification containing the current device status to the NMS.

MIB

The MIB is a database containing the variables that are maintained by the managed device. (The variables can be queried or set by the agent.) The MIB defines the attributes of the managed device, including the name, status, access rights, and data type of managed objects.

The MIB provides the following functions:

  • The agent queries the MIB to obtain the current device status.
  • The agent modifies the MIB to set device status parameters.

MO

An MO is an object to be managed on a network device. A managed device contains multiple MOs, for example, a hardware component (such as an interface board) and a set of parameters configured for the hardware or software (such as a route selection protocol).

SNMP Application Environment

When planning and constructing a new network, you are advised to select the SNMP version based on the application scenario. When expanding or upgrading an existing network, you are advised to select the SNMP version on the device based on the version used on the NMS to ensure communication between the device and NMS.

Table 12-2 Application scenario of each SNMP version

Version

Application Scenario

SNMPv1

Applies to small-sized simple networks where security requirements are not high or the network environment is safe and stable, such as campus networks and small-sized enterprise networks.

SNMPv2c

Applies to medium- to large-sized networks where security requirements are not high or the network environment is safe (such as VPNs), but a large volume of traffic exists and traffic congestion may occur.

SNMPv3 (Recommended)

Applies to networks of various scales, especially those where security requirements are high and only authorized administrators can manage network devices, such as networks where communication data between the NMS and managed devices is transmitted over the public network.

As shown in Figure 12-2, the NMS manages devices through SNMP. The NMS queries and receives alarms from devices to obtain the running status of the devices. With approved rights, the NMS can set device parameters to manage devices.

Figure 12-2 Typical application
SNMP Implementation

Figure 12-3 shows SNMPv1/SNMPv2c implementation.

NOTE:

SNMPv3 implementation is the same as SNMPv1/SNMPv2c implementation, except that SNMPv3 supports identity authentication and encryption.

Figure 12-3 SNMPv1/SNMPv2c implementation

As shown in Table 12-3, SNMPv1/SNMPv2c defines seven types of operations for exchanging information between the NMS and agent.

Table 12-3 SNMPv1/SNMPv2c operations

Operation

Description

Get

Reads one or several parameter values from the agent.

GetNext

Reads the next parameter value by the dictionary order from the agent.

Set

Sets the one or more parameters for the agent.

Response

Returns one or more parameter values. The agent performs this operation to respond to the GetRequest, GetNextRequest, SetRequest, and GetBulkRequest operations. Upon receiving a Get or Set request, the agent performs the query or modification operation using the MIB and then performs the response operation to send information to the NMS.

Trap

The agent proactively sends trap messages to notify the NMS of a fault or event on the managed device.

GetBulk

Queries managed devices in batches.

Inform

Notifies the NMS of an alarm on a managed device. This operation is performed by the managed device. After a managed device sends an Inform packet, the NMS must send an InformResponse packet to the managed device.

NOTE:

SNMPv1 does not support the GetBulk and Inform operations.

Device Addition

This section describes how to add devices to eSight through SNMP.

Figure 12-4 shows the principle of adding devices to eSight through SNMP.

Figure 12-4 Adding devices to eSight

eSight delivers commands containing SNMP parameters to devices. If the devices detect that the received SNMP parameters are the same as those on them, the devices are successfully added to eSight.

Download
Updated: 2019-05-17

Document ID: EDOC1100011877

Views: 282998

Downloads: 536

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