Reason why some optical interfaces of the TD20 board are not displayed on the NMS


These optical interfaces are internal virtual ports of the TD20 board. They are annotated in the Product Documentation.

Other related questions:
Reason why the lease of some addresses in the address pool displays - on S series switches
Run the display ip pool [ { interface interface-pool-name | name ip-pool-name } [ start-ip-address [ end-ip-address ] | all | conflict | expired | used ] ] command to check DHCP address pool allocation on S series switches excluding the S1700. You can find that some addresses�?lease display -. This is because these addresses are one of idle, excluded, statically bound, and conflicting addresses.

Why do some traps fail to reach the NMS after the SNMP trap function is configured on an S series switch
For S series switches (except the S1700), not all traps are enabled by default. If a type of trap is not enabled, the NMS cannot receive traps of this type. To check the list of currently enabled traps, run the display snmp-agent trap all command in the system view. You can run the snmp-agent trap enable feature-name feature-name command in the system view to enable a specified type of trap or the snmp-agent trap enable command to enable all the traps.

Reason why the working mode of the TN54NS4 and TN55NO2 boards cannot be specified on the NMS
The working mode can be specified only after the TN54NS4 or TN55NO2 board is added as 54NS4(REG) or 55NO2(REG) on the NMS.

Why does the NMS tool display an error message when it attempts to load some MIB files for S series switches
For S series switches (except the S1700), when the NMS tool is used to load some MIB files, error message "cannot load this MIB, error: ParseError,no content found, except 'DEFINITIONS::=BEGIN';line:1)" or "cannot load this MIB, error: MIB Parsing failed" is displayed. The reason is that some MIB files, such as RFC1155-SMI, RFC-1212, and SNMPv2-CONF, only define syntax and do not contain MIB objects. These MIB files are referenced by other MIB files. For example, RFC-1212 defines how MIB files are written, and RFC-1215 defines the syntax of TRAP-TYPE macro. Ignore these messages when you are loading these MIB files.

Reason why Optical Interface Attenuation Ratio of a wavelength is set to Blocking on the NMS
The Optical Interface Attenuation Ratio parameter is used to manage the added 40 or 80 wavelengths. You need to first create optical cross-connections for wavelengths on the NMS for the WSM9 board. After the optical cross-connections are created, the default value of this parameter is Blocking for each wavelength. A wavelength whose Optical Interface Attenuation Ratio is Blocking cannot traverse the WSM9 board because the wavelength attenuation is the maximum. To enable the wavelength to traverse the WSM9 board, set the parameter to another value.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top