Optix Rtn Snmp User Guide v1.1-20121231-A

OptiX RTN

SNMP User Guide

Issue

01

Date

2012-02-16

PUBLIC

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2012. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions 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.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]

OptiX RTN SNMP User Guide

About This Document

About This Document Author Prepared by

Date

Reviewed by

Date

Approved by

Date

Authorized by

Date

2011-09-19

Change History Date

Revisio n Version

2012-0919

V1.00

CR ID / Defect ID

Sec No.

Change Description

Author

Completed the initial draft.

Liu Yang Ma Jian

Approved by

OptiX RTN SNMP User Guide

Contents

1

Contents

About This Document.......................................................................ii 1 Summary...................................................................................... 1 1.1 SNMP Basic Theory..........................................................................................................................................1 1.2 SNMP Framework.............................................................................................................................................2 1.3 Networking Mode..............................................................................................................................................4 1.4 Introduction to the System Structure.................................................................................................................5

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

4 MIB Supported by OptiX RTN........................................................13 5 Common Error Code....................................................................14 5.1 Error Code of SNMPv1...................................................................................................................................14 5.2 Error Code of SNMPv2...................................................................................................................................14

OptiX RTN SNMP User Guide

Contents

5.3 Abnormal Errors..............................................................................................................................................15

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

1.1 SNMP Basic Theory The basic concepts of the SNMP are as follows: 

SNMP: The SNMP architecture consists of the MIB, SMI, and SNMP.



MIB: It refers to the management information base. The MIB is the collection of the objects that can be managed by the SNMP on the equipment. The MIB does not store the actual data of the managed objects. The managed objects are organized according to the structure of the hierarchical tree.



SMI: It refers to the structure of management information. The SMI contains the conventions to which the equipment conforms during the maintenance of the management information. The MIB is the collection of the managed objects, and the SMI is the collection of the conventions for naming and defining the managed objects.



OID: Object Identifier. OID: Each node in the MIB tree is allocated with a 32-digit nonnegative integer. The OID of a node is the dotted collection of all the non-negative integers on the path from the root node to the object node of the MIB tree. For example,

The OID of node private in the following figure is 1.3.6.1.4. Figure 1.1.1.I.1.1.1 Top of the MIB tree defined in RFC1155 (SMI) iso£¨ 1£©

org£ ¨ 3£ © dod£¨ 6£©

internet£¨ 1£©

directory£ ¨ 1£ ©

mgmt£ ¨ 2£ ©

experimental£¨ 3£© private£ ¨ 4£ ©

OptiX RTN SNMP User Guide

7 Attachment

Figure 1.1.1.I.1.1.2 Diagram of the MIB tree

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.

1.2 SNMP Framework The SNMP management network consists of the managed equipment, agent, and NMS. The SNMP agent receives the requests from the SNMP NMS by monitoring port 161. By interacting with the application protocol module, the SNMP agent performs the operations requested by the object. Then, the SNMP agent sends the response to the SNMP NMS. Therefore, a complete "request-response" interaction is realized. In the case of an emergency,

OptiX RTN SNMP User Guide

7 Attachment

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. Figure 1.1.1.I.1.1.1 Basic SNMP operations GetRequest UDP 161 GetResponse SNMP NMS GetNextRequest

SNMP agent (Managed 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

1.3 Networking Mode The following figure shows the networking diagram. Figure 1.1.1.I.1.1.2 Networking diagram of the SNMP NMSs

IP network or crossover cable NMS B OptiX equipment C

OptiX equipment B

OptiX equipment A IP network or crossover cable NMS A

The transmission equipment supports the following access modes: The NMS accesses the gateway NE. The laptop or desk-top computer that works as the NMS is connected to the managed equipment through a crossover cable or an IP network. In Figure 1.1.1.I.1.1.2, the NMS can access NE A and NE C. The NMS accesses the non-gateway NE. This access mode requires that the remote NE and the gateway NE support the IP over DCC feature. As shown in figure, NMS A accesses the OptiX equipment B and OptiX equipment C through the non-gateway NE. The OptiX equipment A, OptiX equipment B, and OptiX equipment C must support the IP over DCC feature.

OptiX RTN SNMP User Guide

7 Attachment

1.4 Introduction to the System Structure Figure 1.4.1.I.1.1.1 Position of the SNMP module in the system

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.

2.1 Adding SNMP NMS Messages Command snmp-addtrapinfo:ip(IP),port(us),rCommunity(string),wCommnunity(string ),ver(us)

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

2.2 Querying NMS Messages Command snmp-get-trapinfo

Function This command is used to query all the SNMP NMS messages that have been added to the OptiX RTN equipment.

2.3 Deleting an NMS Message Command snmp-del-trapinfo: ip(ip)

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.1 Software Preparation 

MIB files: You need to obtain MIB files of the version that matches the NE software version.



Navigator: You need to configure the SNMP NMS for the equipment on the Navigator.



SNMP NMS software: You need to be familiar with the usage of the SNMP NMS software, which may be NetCool, AdventNet, MG-SOFT and so on.

3.2 Collecting Information You need to collect information about the networking of a customer's network, the functions of network that the customer accepts, prepare for configuring the network according to the customer's requirements, such as configuring communication protocols (IP over DCC feature is required to visit NE at the remote end), adding routes and SNMP NMS messages. For details about networking of IP over DCC solution, refer to IP over DCC Features of SDH Product Deployment Guide.

IP over DCC Features of SDH Product Deployment Guide-20080718-A.zip

3.3 MIB Information about the OptiX Equipment 3.3.1 Introduction to OptiX RTN 600 MIB Files File Name

Function

OPTIX-OID-MIB.mib

Defines the proprietary OID node of Huawei OptiX equipment.

File Name

Function

OPTIX-SDH-TC-MIB.mib

Defines alarms, performance events, and objects supported.

OPTIX- SDH -ALM-MIB.mib

Defines alarm-related node information.

OPTIX- SDH -PER-TIME-MIB.mib

Defines node information related to SDH performance.

OPTIX-RMON-MIB

Defines node information related to RMON performance.

OPTIX- SDH -TRAPS-MIB.mib

Defines the nodes that are used for reporting the TRAP information (for example, reporting the alarms and performance events).

OPTIX-HK-RMON-MIB.mib

Defines the node that manages the RMON information (only the current RMON statistics can be queried).

3.3.2 Introduction to OptiX RTN 900 MIB Files File Name

Function

OPTIX-OID-MIB.mib

Defines the proprietary OID node of Huawei OptiX equipment.

OPTIX-GLOBAL-TC-MIB.mib

Defines alarms, performance events, and objects supported.

OPTIX-GLOBAL-ALM-MIB.mib

Defines the nodes that are used to manage alarms (current alarms, historical alarms, and alarm report)

OPTIX-GLOBAL-PER-TIME-MIB.mib

Defines the start time and end time of SDH performance period.

OPTIX-GLOBAL-PER-SDH-OptiX RTN900-MIB.mib

Defines the SDH performance statistics (current statistics and history statistics).

OPTIX-GLOBAL-PER-TRAPS-OptiX RTN900-MIB.mib

Describes the reporting of TRAP messages in the SDH performance historical data.

OPTIX-GLOBAL-TRAPS-MIB.mib

Defines the reporting of TRAP messages (alarm reporting and performance reporting).

OPTIX-GLOBAL-PM-MIB.mib

Defines RMON history control group.

OPTIX-GLOBAL-PM-DATA-OptiX RTN900-MIB.mib

Defines the RMON information (the current RMON statistics and history RMON statistics).

OPTIX-GLOBAL-PM-TRAPS-OptiX RTN900-MIB.mib

Describes the reporting of TRAP messages in the RMON historical data.

3.4 Obtaining the MIB Files You can obtain the MIB files from the mapping platform files used by the OptiX product.

3.4.1 Loading MIB Files You can compile the MIB files of the OptiX RTN equipment in the following sequence: OPTIX-OID-MIB.mib > OPTIX-GLOBAL-TC-MIB.mib > other MIB files whose loading or compile order is not regulated. You need to know the directory requirements for MIB files of the SNMP NMS software. For example, MG-SOFT does not allow MIB files to be installed in a Chinese directory.

3.5 SNMP Operations The basic operations that the SNMPv1 protocol can execute includes: Get, Get-Next, and Set. The SNMPv2 protocol or later can execute the Get-Bulk operation. Following are the execution results on the MG-SOFT MIB BROWER.

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)]

3.5.2 Get Next Function Obtain the next alphabetical order value of an object.

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)]

3.5.3 Get Bulk Function Obtain the next alphabetical order values of an object in batches. This operation functions as multiple Get-Next operation. The following two parameters must be set in the Get-Bulk operation. 

Non repeaters: The number of variables that performs Get-Next operation once only. The value of Non repeaters is the total number of variables when it is set to be a value greater than the total number of variables. The value of Non repeaters is 0 when it is set to be a value less than 0. The value of Non repeaters is usually set to be 0.



Max repetitions: The maximum repetition times for the Get-Next operation performed on variables (excluding the variables specified in Non repeaters). Otherwise, tooBig is returned.

The Get-Bulk operation is usually performed for a single object. If Non repeaters = 0 and Max repetitions = 1, results of Get-Bulk operation and Get-Next operation are the same.

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

OptiX RTN Equipment Version

Support for the SNMP Function

The first OptiX RTN Equipment Version that Supports the SNMP Function

Related Document

OptiX RTN 600

Supported

All mainstream versions

OptiX RTN 900 V100R001

Not supported

None

None

OptiX RTN 900 V100R002

Supported

OptiX RTN 900 V100R002C01 (5.76.02.21)

7.1"OptiX RTN 600V100R005 MIB User Guide"

OptiX RTN 900 V100R003C00SPC100

Supported

OptiX RTN 900 V100R003C00SPC100 (5.76.03.12)

5

Common Error Code

5.1 Error Code of SNMPv1 

tooBig: It indicates that PDU is too large. You can reduce the value of Max repetitions in the Get-Bulk operation or reduce the number of variables to clear this bit error.



noSuchName: The object does not exist in the MIB. In other words, the OID node is wrong.



genErr: It indicates that the SNMP agent fails to send a request. For example, failure in applying for memory or other failures not caused by error in protocol content.



badValue: It indicates that the data type, length or value is incorrect.



readOnly: When set operation is performed for a read-only variable, readOnly is returned. For the RFC, noSuchName instead of readOnly is returned when a set operation is performed.



noError: It indicates that the operation is successful. If the operation is successful in the MIB Browser, execution result is displayed and noError will not be returned.

5.2 Error Code of SNMPv2 

noAccess: A variable cannot be visited.



wrongType: The set type of a variable is inconsistent with the required one.



wrongLength: The set length of a variable is inconsistent with the required one.



wrongValue: The set value exceeds the specified range and is invalid.



noCreation: The variable that you are trying to modify or create is nonexistent or noncreatable.



inconsistentValue: The set value is invalid in the current condition. For example, when the RowStatus object value is set to createAndWait, but should be active in the current condition, inconsistentValue is returned.



inconsistentName: The value that you set is nonexistent or non-creatable in the current condition. However, this value can be set or created when required conditions are met.



notWritable: The variable is existent but set operation cannot be performed on it. For example, when set operation is performed on a read-only variable, notWritable is returned.



commitFailed: If set operation fails under conditions that are different from the preceding error conditions, commitFailed is returned.



undoFailed: The set operation fails and not all the successfully set variables can back to the value before the set operation is performed. undoFailed indicates a rolled back failure.

5.3 Abnormal Errors The following errors only apply to SNMPv2 or later. When the same conditions are met in SNMPv1, noSuchName is returned. 

end of mib view: When Get-Next or Get-Bulk operation completes all operations on the instances of an object, end of mib view is returned, indicating that all the instances are traversed by MIB tree.



no such object: SNMP agent does not support such object.



no such instance: The instance does not exist, that is, index is incorrect.

6 

FAQs

Question: No response is returned for the SNMP configuration command. Why? Answer: Check whether the NE software supports the SNMP feature.



Question: The SNMP configuration information cannot be added. Why? Answer:

1.

Check whether 32 records of the SNMP configuration information exist. If there are already 32 records of the SNMP information, delete the unnecessary records.

2.

Check whether the command parameters are correctly configured.



Question: The login on the equipment from the NMS times out. Why?

1

Check whether the NMS information is added to the accessed equipment.

3.

Check whether the read community name on the NMS is consistent with the one on the equipment.

4.

Check whether the NMS login timeout is too short and whether the equipment can be automatically logged in from the NMS. SNMP agent processes requests in a serial order. If the login request is resent immediately after the previous login request times out, more loads are placed on the equipment. Therefore, it is recommended that you set the timeout value according to data size and the re-login value to 0.



Question: A correctly configured tool cannot access the equipment. Why? Answer:

1

Check whether the communication between PC and the equipment is proper.

5.

Check whether routing from the NMS PC to the equipment is available and whether the network is an IP network.



Question: The SNMP NMS tool cannot receive TRAP messages. Why? Answer:

1

On the Windows 2000 operating system, check the access options on the control panel. Check whether the SNMP service is deactivated. If the SNMP service is not deactivated, deactivate the SNMP service.

6.

Check whether the TRAP port on the SNMP NMS is consistent with the one on the equipment and whether the port status is proper. The default TRAP port is port 162.



Question: Reading a large quantity of data is slow. Why? Answer: The SNMP querying function uses the index walking mechanism. When you query a large quantity of data, the system needs to buffer a lot of data. In addition, the system walks through each leaf node. Hence, reading data is at a slow speed.



Question: What is an index? Answer: When the SNMP queries information, the SNMP sorts the information according to the alphabetical order. In addition, the SNMP creates indexes for the information objects. Hence, when the SNMP reads information, the SNMP obtains a unique record according to the sequence. This is similar to the creation of indexes for the database table. The key fields are used as indexes. To read a record, the system reads the record according to the index of the record.



Question: How to obtain the OID? Answer: The MIB has a tree structure. The OID uniquely identifies a node on the MIB tree. The OIDs are allocated.



Question: OID is returned in some queries and is not easy to read. Why? Answer: MIB files are not loaded into MIB Browser.



Question: How to verify whether the data returned by SNMP is complete? Answer: SNMP returns value in an alphabetical order. You can query the same object on other terminals and then check whether the returned value is consistent with the value returned by SNMP. If the object is in the table, you can issue the :snmp-print-indexinfo MML command to query the number of total records that SNMP agent received from the application module, and check whether it is consistent with the total records returned by the SNMP.



Question: The total number of queried records of an object in the table is inconsistent with the actually recorded total number. However, they are consistent after a while. Why? A: This is due to cache index mechanism on the SNMP agent. −

When an object in the table is being queried, if the table index is not cached by the SNMP agent, the SNMP agent obtains data from the application module to generate an index. Therefore, the total number of queried records is consistent with the actually recorded total numbers.

−

If the table index is cached on the SNMP agent, SNMP agent does not need to obtain data from the application module to generate an index. If the data in table index cached on the SNMP agent is inconsistent with the data in the application module, then the total number of queried records is inconsistent with the actually recorded total numbers.

SNMP agent caches index in 2 minutes. SNMP agent obtains data from the application module to generate an index 2 minutes later. Therefore, the total number of queried records is consistent with the actually recorded total numbers after a while. 

Question: what data will be collected if SNMP fails?

1

Execution result of the :snmp-get-trapinfo command

7.

bb0 log and, if NE is reset, errlog log

8.

NE software version, platform software version, and board software version

9.

Parameters configured in MIB Browser, for example, community name, and timeout time

10. IP address of the PC on which MIB Browser is installed 11. MIB files in use

7

Attachment

7.1 OptiX RTN 600V100R005 MIB User Guide OptiX RTN 600 OptiX RTN600V1R5 V100R005 SNMP User Guide.doc MIB ID.xls

7.2 OptiX RTN 900 V100R002C01 MIB User Guide OptiX RTN 900 RTN MIB ID.xls V100R002C01 SNMP User Guide.doc

7.3 OptiX RTN 900 V100R003C00 MIB ID RTN900V1R3C00 MIB ID.xls

7.4 OptiX RTN 900 V100R005C00 MIB User Guide RTN900V1R5C00 MIB RTN900V1R5C00SNMP ID.xls guide.docx