Professional Documents
Culture Documents
Optix RTN SNMP User Guide v1 1 20121231 A
Optix RTN SNMP User Guide v1 1 20121231 A
Issue 01
Date 2012-02-16
PUBLIC
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Email: support@huawei.com
OptiX RTN
SNMP User Guide About This Document
Author
Prepared by Date 2011-09-19
Reviewed by Date
Approved by Date
Authorized by Date
Change History
Date Revisio CR ID / Sec Change Author Approved
n Defect No. Description by
Version ID
1 Contents
2 Configuring Commands.................................................................6
2.1 Adding SNMP NMS Messages..........................................................................................................................6
2.2 Querying NMS Messages..................................................................................................................................7
2.3 Deleting an NMS Message................................................................................................................................7
3 SNMP Operations..........................................................................8
3.1 Software Preparation..........................................................................................................................................8
3.2 Collecting Information.......................................................................................................................................8
3.3 MIB Information about the OptiX Equipment...................................................................................................8
3.3.1 Introduction to OptiX RTN 600 MIB Files..............................................................................................8
3.3.2 Introduction to OptiX RTN 900 MIB Files..............................................................................................9
3.4 Obtaining the MIB Files..................................................................................................................................10
3.4.1 Loading MIB Files..................................................................................................................................10
3.5 SNMP Operations............................................................................................................................................10
3.5.1 Get..........................................................................................................................................................10
3.5.2 Get Next..................................................................................................................................................11
3.5.3 Get Bulk..................................................................................................................................................11
3.5.4 Set...........................................................................................................................................................12
6 FAQs........................................................................................... 16
7 Attachment................................................................................. 18
7.1 OptiX RTN 600V100R005 MIB User Guide..................................................................................................18
7.2 OptiX RTN 900 V100R002C01 MIB User Guide...........................................................................................18
7.3 OptiX RTN 900 V100R003C00 MIB ID.........................................................................................................18
7.4 OptiX RTN 900 V100R005C00 MIB User Guide...........................................................................................18
OptiX RTN
SNMP User Guide 7 Attachment
1 Summary
iso£¨ 1£©
org£ ¨ 3£ ©
dod£¨ 6£©
internet£¨ 1£©
Each object managed by the SNMP on the equipment is identified by a unique OID in the
MIB tree. The SNMP organizes the managed objects in a visual manner (by using the MIB
tree). The SNMP also classifies the operations performed on the managed objects into several
simple operations. Therefore, simplicity is an important feature of the SNMP.
The SNMP uses the "management process + agent process" model. The management process
is the SNMP network management system (NMS). The agent process runs on the equipment.
After the equipment starts up, the MIB tree becomes a static tree and is initialized by the
SNMP agent.
The managed objects on the equipment correspond to the OIDs in the MIB tree. The
operations that the SNMP NMS performs on the equipment can be considered as the
operations performed on the nodes in the MIB tree. Hence, different SNMP NMSs can
manage the equipment when they have the information about the MIB. The NMSs do not
need to learn how each object is managed.
for example, change of the interface state (linkup/linkdown), failure to verify the authority, or
performance degrade of the equipment, the SNMP agent sends a TRAP message to the SNMP
NMS to prompt the network management personnel to take proper measures. The default
TRAP port is port 162.
The simple SNMP operations include the requests that the SNMP NMS actively sends to the
SNMP agent, and the corresponding responses (GetResponse), TRAP messages, Infor
messages, and Report messages that the SNMP agent sends to the SNMP NMS. The requests
include the GetRequest, GetNextRequest, SetRequest, and GetBulkRequest (supported by the
SNMP V2 and later versions). SNMP on the OptiX RTN equipment does not support Infor
messages and Report messages, but support other aforesaid messages.
GetRequest
UDP 161
GetResponse
SNMP agent
SNMP NMS
(Managed
GetNextRequest equipment)
UDP 161
GetResponse
SetRequest
UDP 161
GetResponse
UDP 162
Trap
Most of the SNMP NMSs run the user datagram protocol (UDP) to transmit data. The SNMP
request packets and SNMP response packets are relatively independent of each other because
the UDP is a connectionless and unreliable protocol. Generally, each SNMP NMS uses the
timeout and retransmission mechanism to solve the unreliability problem.
OptiX RTN
SNMP User Guide 7 Attachment
IP network or
crossover cable
NMS B
OptiX equipment C
OptiX equipment B
OptiX equipment A
IP network or
crossover cable
NMS A
The SNMP interface is a network management interface and functions as an interface module.
The SNMP module is in the same position as the MML module and Qx module in the NE
software.
The SNMP uses the UDP as the transport layer protocol. The SNMP interface does not
receive or transmit NM communication packets by using the communication module, but
directly monitors port UDP 161. The SNMP interface waits for the requests from the NMS on
port UDP 161. The SNMP sends TRAP messages to port UDP 162 of the NMS (the port to
which the SNMP sends the report packets can be configured).
2 Configuring Commands
SNMP can only be configured on the Navigator and cannot be directly configured on the
OptiX RTN equipment due to lack of SNMP interfaces.
Function
This command is used to add SNMP NMS messages. You can use the SNMP NMS to perform
operations on the equipment only after you add SNMP NMS messages on the equipment. To
correctly perform the querying operations such as Get, Get-Next, and Get-Bulk, the name of
the read community must be correct (the querying operations cannot be performed if only the
name of the write community is correct). To correctly perform the setting operations, the
name of the write community must be correct. An SNMP agent supports a maximum of 32
SNMP NMS messages.
Parameter Description
ip: This parameter specifies the IP address of the SNMP NMS, not the IP address of the
equipment. Wildcard characters are not supported.
port: This parameter specifies the number of a port that receives TRAP messages on the
SNMP NMS from the equipment. The default TRAP port on the SNMP NMS is port 162.
rCommunity: This parameter specifies the name of the read community, which is also the
name of the trap community. The rCommunity parameter must be a visible ASCII (31,
128) character string with a length of 6 to 16 digits. The value of the rCommunity
parameter is the password used when the SNMPv1/SNMPv2 protocol is used to perform
querying operations. The default value of rCommunity on the SNMP NMS is public.
wCommunity: This parameter specifies the name of the write community. The
wCommunity parameter must be a visible ASCII (31, 128) character string with a length
of 6 to 16 digits. The value of the wCommunity parameter is the password used when the
SNMPv1/SNMPv2 protocol is used to perform setting operations. The default value of
wCommunity on the SNMP NMS is private.
ver: This parameter specifies the version of the trap message. The ver parameter can be
V1 or V2. When a trap message is to be sent, the SNMP agent sends the trap message of
the version specified by this parameter to the SNMP NMS. The ver parameter, either V1
or V2, must be consistent with the version of MIB files. The ver parameter can only be
set to V2 for OptiX RTN equipment because only MIB files of SNMPv2 are available
for OptiX RTN equipment. Otherwise, TRAP messages cannot be correctly parsed on the
SNMP NMS.
Example
:snmp-add-trapinfo:129.9.0.1,162,"public","private",V2
Function
This command is used to query all the SNMP NMS messages that have been added to the
OptiX RTN equipment.
Function
This command is used to delete a specified SNMP NMS message from the OptiX RTN
equipment.
Parameter Description
ip: This parameter specifies the IP address of the SNMP NMS on which a specified SNMP
NMS message is to be deleted. Wildcard characters are not supported.
Example
:snmp-del-trapinfo:129.9.0.1
3 SNMP Operations
3.5.1 Get
Function
Obtain the value of an object and this operation only applies to leaf nodes.
Example
Remote address: 129.9.90.52 port: 161 transport: IP/UDP
Local address: 129.9.0.122 port: 3619 transport: IP/UDP
Protocol version: SNMPv2c
Operation: Get
Request binding:
1: per15mMonitorStartTime.0 (null) null
Response binding:
1: per15mMonitorStartTime.0 (octet string) 1990-4-10,0:24:53.0 [07.C6.04.0A.00.18.35.00
(hex)]
Example
Remote address: 129.9.90.52 port: 161 transport: IP/UDP
Local address: 129.9.0.122 port: 3620 transport: IP/UDP
Protocol version: SNMPv2c
Operation: Get next
Request binding:
1: per15mMonitorStartTime.0 (null) null
Response binding:
1: per15mMonitorEndTime.0 (octet string) 2010-7-18,17:1:1.0 [07.DA.07.12.11.01.01.00
(hex)]
Example
Remote address: 129.9.90.52 port: 161 transport: IP/UDP
Local address: 129.9.0.122 port: 3625 transport: IP/UDP
Protocol version: SNMPv2c
Operation: Get bulk
Request binding:
1: per15mMonitorStartTime.0 (null) null
Response bindings:
1: per15mMonitorEndTime.0 (octet string) 2010-7-18,17:1:1.0 [07.DA.07.12.11.01.01.00
(hex)]
2: per24hMonitorStartTime.0 (octet string) 1990-4-10,0:24:53.0 [07.C6.04.0A.00.18.35.00
(hex)]
3.5.4 Set
Function
Set the value of an object and this operation applies only to writable leaf nodes.
Example
***** SNMP SET-RESPONSE START *****
1: pmHistCtrEnableFlag.17 (integer) enable(1)
***** SNMP SET-RESPONSE END *****
4 MIB Supported by OptiX RTN
RTN900V1R3C00 MIB
ID.xls