40G Wavelengths Are Unavailable Due to a DCM Module Connection Problem

40G wavelengths are unavailable due to a DCM module connection problem.

Product

OptiX OSN 6800

Fault Type

DCM Module

Symptom

10G and 40G wavelengths are transmitted in an OptiX OSN 6800 network. The network topology is shown in the following figure. 40G wavelengths in two directions between station A and station G are unavailable. In addition, the performance of 10G wavelengths is lower than the expected performance although it is stable.

Cause Analysis

The optical power and OSNR after commissioning are normal and the optical fibers are newly routed. In this case, it is impossible that the PMD is excessively high. In addition, the link in the network is long, which results in use of many DCM modules. Therefore, it is possible that the DCM modules at a station are incorrectly connected.

Procedure

1. Each station between station A and station G uses different DCM modules in two directions and the compensation distance of the two DCM modules differs by more than 40 km. In this case, incorrect connection of DCM modules at any station can make the 40G wavelengths unavailable.
2. At each station, query the optical power of the optical amplifier boards and calculate the attenuation of the DCM modules. The attenuation of a DCM module increases with the compensation distance of the DCM module.
3. Check station D. The result shows that station D is abnormal. That is, the attenuation of the DCM module connected to optical amplifier board A03 is lower than that of the DCM module connected to optical amplifier board A05.
4. Check whether the DCM modules at station D are incorrectly connected. After rectifying the connections, confirm that the 40G wavelengths are available.

Result

The problem is resolved.

Reference Information

None.

How to enable command log on S9300?

Why Automatical configuration backup cannot work on S5700

How to Change the Link Type of an Interface?

The Client Equipment Interconnected with the TOM Board Reports the R_LOS Alarm Due to a Problem with the Optical Module on the TOM Board

The client equipment interconnected with the TOM board reports the R_LOS alarm due to a problem with the optical module on the TOM board.

Product

OptiX OSN 6800

OptiX OSN 8800

Fault Type

Tributary Unit and Line Unit

R_LOS

Symptom

The SLQ4 board in the client equipment OptiX OSN 3500 interconnected with the TOM board in the OptiX OSN 6800 reports the R_LOS alarm. If you add an optical attenuator to the SLQ4 board, the alarm is cleared. In this case, the R_LOS alarm is reported again if you self-loop a client-side optical interface on the TOM board.

Cause Analysis

There is a problem with the client-side optical module on the TOM board.

Procedure

1. Replace the client-side optical module on the TOM board to check whether the module is faulty. The R_LOS alarm, however, persists after the module is replaced. This indicates that the module is normal.
2. Configure the bidirectional services between a client-side optical interface on the TOM board and the client equipment. In this case, the R_LOS alarm is cleared.
3. Consult the R&D engineers. They explain that the client-side optical module on the TOM board reports the R_LOS alarm instead of the R_LOF alarm upon receipt of all "0"s or all "1"s signals if no service is configured for the module.

Result

To solve the problem, configure services for the client-side optical module on the TOM board.

Reference Information

None.

How to do when the Occasional Failure to Go Online for TN11HSC1 Boards

Incorrect Configuration of the ZL80018 Chip on OptiX OSN 1800

When Service Interruption on 100G and 40G Boards in WDM Products

The TDX Board Reports the BUS_ERR Alarm When Cross-Connections Are Configured on the Board Because the Service Type of the Board Is Not Set

The TDX board reports the BUS_ERR alarm when cross-connections are configured on the board because the service type of the board is not set.

Product

OptiX OSN 6800

OptiX OSN 8800

Fault Type

Electrical Cross-connection

Tributary Unit and Line Unit

BUS_ERR

Symptom

When the ODU2 cross-connections between the TDX and ND2 boards in the OptiX OSN 6800 on a network are configured, the boards report the BUS_ERR alarm.

Cause Analysis

This problem occurs when the input service type of the board is not set before cross-connections are configured on the board. The problem, however, does not affect the normal operation of the boards on the network.

Procedure

1. Replace the TDX board to check whether it is faulty. The BUS_ERR alarm, however, persists after the board is replaced.
2. Reseat the TDX board to check whether it is loose in its slot. The BUS_ERR alarm, however, persists after the board is reseated.
3. Test the WDM-side signal rates of the TDX and ND2 boards. The test result shows that the WDM-side signal rate of the TDX board is 11.1 Gbit/s while that of the ND2 board is 10.7 Gbit/s. When the cross-connections between the TDX and ND2 boards are configured, the TDX board receives signals at a rate of 11.1 Gbit/s while the rate of the signals sent from the ND2 board is 10.7 Gbit/s. As a result, the boards report the BUS_ERR alarm. If the service type of the TDX board is set to STM-64, the TDX board receives signals at a rate of 11.1 Gbit/s and the problem is solved.

Result

Currently, only the TN12TDX, TN11TQX, TN11ND2, and TN12NS2 boards report the BUS_ERR alarm in the preceding case. These boards support ODU2 cross-connections.

Therefore, the input service type of the TDX board should be set before ODU2 cross-connections are configured on the board.

Reference Information

None.

When Service Interruption on 100G and 40G Boards in WDM Products

Incorrect Configuration of the ZL80018 Chip on OptiX OSN 1800

How to do when the Occasional Failure to Go Online for TN11HSC1 Boards

The Service Alarm Indicator on an OTU Board Is Still Red After the HARD_ERR and HARD_BAD Alarms Are Suppressed

The service alarm indicator on an OTU board is still red after the HARD_ERR and HARD_BAD alarms are suppressed.

Product

OptiX OSN 6800

OptiX OSN 8800

Fault Type

Optical Transponder Unit

HARD_ERR

HARD_BAD

Symptom

An OTU board in the OptiX OSN 6800 on a network reports the HARD_ERR or HARD_BAD alarm. After the reported alarm is suppressed on the T2000, the service alarm indicator (SRV) on the board is still red. After the other alarms, if any, are suppressed on the T2000, the service alarm indicator on the board becomes green if the board does not report extra alarms.

Cause Analysis

The HARD_ERR and HARD_BAD alarms indicate hardware faults. When the board reports either alarm, it indicates that the hardware of the board is faulty. In this case, the board needs to be replaced. The designing helps the on-site engineers in replacing the board.

Procedure

1. When the board reports the HARD_ERR or HARD_BAD alarm, it indicates that the hardware of the board is faulty. After these two alarms are suppressed on the T2000, the service alarm indicator on the board is still red.

Result

The OptiX OSN 6800 is designed in this manner to help the on-site engineers in replacing the board.

Reference Information

None.

Related:

What Caused Occasional NE Unreachability

When Incorrect Fan Rotation Speed Adjustment of the OptiX OSN NG WDM Products

When Service Interruption on 100G and 40G Boards in WDM Products

The Client Equipment Interconnected with the TOM Board Reports the R_LOS Alarm Due to a Problem with the Optical Module on the TOM Board

The client equipment interconnected with the TOM board reports the R_LOS alarm due to a problem with the optical module on the TOM board.

Product

OptiX OSN 6800

OptiX OSN 8800

Fault Type

Tributary Unit and Line Unit

R_LOS

Symptom

The SLQ4 board in the client equipment OptiX OSN 3500 interconnected with the TOM board in the OptiX OSN 6800 reports the R_LOS alarm. If you add an optical attenuator to the SLQ4 board, the alarm is cleared. In this case, the R_LOS alarm is reported again if you self-loop a client-side optical interface on the TOM board.

Cause Analysis

There is a problem with the client-side optical module on the TOM board.

Procedure

1. Replace the client-side optical module on the TOM board to check whether the module is faulty. The R_LOS alarm, however, persists after the module is replaced. This indicates that the module is normal.
2. Configure the bidirectional services between a client-side optical interface on the TOM board and the client equipment. In this case, the R_LOS alarm is cleared.
3. Consult the R&D engineers. They explain that the client-side optical module on the TOM board reports the R_LOS alarm instead of the R_LOF alarm upon receipt of all "0"s or all "1"s signals if no service is configured for the module.

Result

To solve the problem, configure services for the client-side optical module on the TOM board.

Reference Information

None.

Related blog:

When OptiX OSN 1800 Database Recovery Failures

How to Use the Ethernet Test Frames on the OptiX OSN 6800?

TD Alarms Falsely Reported by Some Boards Using Pluggable Optical Modules in WDM Products

The External Clock Source Is Unavailable After a Fiber Cut Because the Clock Configuration Is Incorrect

The priorities of the clock sources are set incorrectly, so the external clock source is unavailable after a fiber cut. After the priorities of the clock sources are re-set, the fault is rectified.

Product

OptiX OSN 7500

Fault Type

• Bit errors
• LTI

Symptom

The EOW board on NE A is connected to two clock sources from third-party equipment, the network clock tracing is normal, as shown in Figure 1. After a fiber cut occurs on the ring network, the external clock source becomes unvailable. In addition, NE D reports the LTI alarm, and a large amount of bit errors occur.

Figure 1 Clock tracing diagram

Cause Analysis

In normal cases, the working path of the clock tracing is external clock source->NE A->NE B->NE C->NE D->NE F; the protection path is external clock source->NE A->NE F->NE D->NE C->NE B. After a fiber cut occurs on the ring network, the clock source of NE D is lost. After the clock configuration of the network is checked, it is found that System Clock Source Priority Table on NE D is not configured.

Procedure

1. Query the clock subnet configuration by using the NMS.
   1. In the NE Explorer of NE D, choose Configuration > Clock > Clock Subnet Configuration.
   2. Choose the Clock Quality tab, and Choose the Clock Source Quality. Click Query. The return shows that the system receives the G.811 primary reference clock (PRC) from the 11-SL64 board.
   3. Choose View > Clock View to obtain the clock tracing relationship of NE D. The west clock source (on NE C) next to NE D is unavailable, so NE C should trace its east clock source.
2. In the NE Explorer of NE D, choose Configuration > Clock > Clock Source Priority. Then, select Priority Table for Phase-Locked Sources of 2nd External Clock Output, and click Create to add 8-SL64 and 11-SL64 as clock sources.
3. In the Clock View, refresh the clock tracing relationship. Then, the alarm clears.

Related blog:

Pay attention to TN51XCS Boards MOS Transistors

Reasons for logical abnormality and Fail restoration of TN serises DWDM board

Cautions for a Protection Switching Failure on the DCP and OLP Board On OSN8800

Locally Logging in to the Web Interface

This topic describes the data plan and procedure for logging in to the web configuration interface.

Context

Before setting up the configuration environment, ensure that data information listed in Table 1 is available.

Table 1 Data plan
Item	Description
User name and password	Default settings: · Administrator (installation and maintenance personnel): § User name: telecomadmin § Password: admintelecom NOTE: § After logging in to the web page, if you do not perform any operations within five minute, you will be locked out and return back to the login interface. Then, You can unlock the account by entering the login user name and password. § Three times within five minutes the user name and password input error, the system is locked and unlocked automatically after one minute. § Modify the password through the BMS. § Certain carriers may customize accounts and passwords, which are different from the default accounts and passwords listed in the preceding. For details, contact the corresponding carrier. CAUTION: § Please change the initial password to ensure administrator account security. § Do not provide terminal users with the password of the administrator account. The administrator account is used by the carrier for O&M. If a terminal user uses the administrator account, service parameters may be incorrectly modified and services may be affected. · Common user (terminal user): § User name: root § Password: adminHW NOTE: § The common user account can be used to query the service status. For ONTs that support Wi-Fi and the USB storage function, the common user account can be used to configure services such as Wi-Fi and home sharing. § After logging in to the web page, if you do not perform any operations within five minute, you will be locked out and return back to the login interface. Then, You can unlock the account by entering the login user name and password. § Three times the user name and password input error, the system is locked and unlocked automatically after one minute. § Modify the password through the Web. § Certain carriers may customize accounts and passwords, which are different from the default accounts and passwords listed in the preceding. For details, contact the corresponding carrier. CAUTION: Change the initial password after Common users log in to the web page.

Procedure

1. Use a network cable to connect the LAN port of the ONT to a PC.
2. Ensure that the Internet Explorer (IE) of the PC does not use the proxy server. The following section considers IE 6.0 as an example to describe how to check whether the IE uses the proxy server.
   1. Start the IE, and choose ToolsInternet Options from the main menu of the IE window. Then, the Internet Options interface is displayed.
   2. In the Internet Options interface, click the Connections tab, and then click LAN settings.
   3. In the Proxy server area, ensure that the Use a proxy server for your LAN (These settings will not apply to dial-up or VPN connections). check box is not selected (that is, without the "√" sign). If the check box is selected, deselect it, and then click OK.
3. Set the IP address and subnet mask of the PC. For details, see Table 1.
4. Log in to the Web configuration interface.
1. Enter http://192.168.100.1 in the address bar of IE (192.168.100.1 is the default IP address of the ONT, such as HG8245H,HG8245A)), and then press Enter to display the login interface, as shown in Figure 1.
   Figure 1 Login interface
   
    NOTE:

   The web page login supports SSL3.0, TLS1.0, TLS1.1, and TLS1.2. It is recommended that you use high-security TLS1.1 or TLS1.2 if you log in to the ONT using https. The TCP port 80 is used for listening for HTTPS packets. You need to type "https://192.168.100.1:80" in the address bar of IE and press Enter to log in to the ONT.
2. In the login interface, enter the use name and password. For details about default settings of the user name and password, see Table 1. After the password authentication is passed, the Web configuration interface is displayed.

Related Blog:

What’s the alarm on the OptiX OSN 1800II board restarts after power-off

Cautions for Drive Failure on the SSX2T2TM Module

Watch out Wavelength Information of the TNF1X40 on the OSN 1800