₦airaland Forum

ATM services fail to be created, thus failing to realize the protection. You need to add the two connections into the protection group.
Product

OptiX OSN 1500A/1500B
OptiX OSN 2500
OptiX OSN 3500 II
OptiX OSN 3500
OptiX OSN 7500
Fault Type

Configuration_Problem
Symptom

After you create two connections that have the same source but different sinks, or that have the same sink but different sources, the service of a connection fails to be created.
The service fails to be created. The protection fails to be achieved accordingly.
Cause Analysis

The second connection takes effect only after you add the two connections that have the same source but different sinks, or that have the same sink but different sources into the protection group.
Procedure

Add the two connections into the protection group.
Reference Information

None.

The OptiX OSN 6800 is new equipment and several OptiX OSN 6800 NEs have this alarm. It is suspected that the power module is faulty.
After cutting off the power of the OptiX OSN 6800 then power on, the equipment time and date information is lost and changes to the initial time and date, that is 1990-01-01 00:00:00. Then, the battery on the SCC may be faulty.
Procedure

Remove the SCC board and check the jumper that controls the battery. This jumper is found in an incorrect state.
Change the state of the jumper so that the battery works.
Insert the SCC. The POWER_FAIL alarm is cleared.
Reset the date and time.
Reset the equipment and the time and date information is not lost. The problem is solved.

The connection between the telephone set and the ONT is abnormal.
The ONT port to which the telephone set is connected is configured incorrectly.
The telephone set does not register with the voice server.
The voice service of the telephone set is not configured with a high priority.
The line connections are abnormal.
The telephone set is faulty.
The numbers configured on the ONT(such as HG8245H) are incomplete.
The digitmap configuration is incorrect.
The codec and authentication configured on the ONT(such as HG8245A) are incorrect.
A phone number conflict occurs during the registration.
The voice IP address fails to be obtained.

Function
This command is used to restore each threshold of the ONT POTS port test to the default value.

Format
ont pots-test-threshold restore

Parameters
None

Modes
Test mode

Level
Operator level

Usage Guidelines
Run the config command to enter the global config mode, and then run the test command to enter the test mode.
After each threshold is restored to the default value, the ONT uses the internal default value to analyze the test result when you run the ont pots test command to start the ONT POTS port test.
Example
To restore each threshold of the ONT POTS port test to the default value, do as follows:

huawei(config-test)#ont pots-test-threshold restore

huawei(config-test)#System Response
The system does not display any message after the command is executed successfully.
For more information about the error message that the system displays against a command entered with incorrect syntax, see the "Syntax Check" in Parameter.

Function
This command is used to query the information about the ONT capability set profile in a distributed mode.

Format
display ont-profile { profile-id profile-id | profile-name profile-name | all }

Parameters
Parameter
Description
Value

profile-id profile-id
Indicates the ID of the ONT capability set profile. It identifies a capability set profile uniquely.
Numeral type. Range: 1-128.

profile-name profile-name
Indicates the name of the ONT capability set profile. The default naming rule in the system is "ont-profile_x". "x" is the ID of the ONT capability set profile.
Character string type, a string of 1-63 characters.

all
When you need to query the summary information on all the ONT capability set profiles, use this parameter. The summary information about all ONT capability set profiles includes the profile ID, profile name, and binding times of an ONT capability set profile.
-


Modes
Privilege mode

Level
Operator level

Usage Guidelines
To switch the xPON mode, run the diagnose command in privilege mode or global config mode to enter diagnose mode, and then run thexpon mode switch-to command. After the switching, reset the device for the mode to take effect.
When the profile ID or profile name is specified, the system displays the detailed information about the specified profile.
Example
To query the detailed information about ONT capability set profile 1, do as follows:

huawei#display ont-profile
{ all<K>|profile-id<K>|profile-name<K> }:profile-id
{ profile-id<U><1,128> }:1

Command:
display ont-profile profile-id 1
---------------------------------------------------------------------------
Profile ID : 1
Profile name: ont-profile_1
---------------------------------------------------------------------------
Number of POTS ports: 0
Number of ETH ports: adaptive
Number of VDSL ports: 0
TDM port type: E1
TDM service type: TDMoGem
Number of TDM ports: 8
Number of MOCA ports: 0
Number of CATV UNI ports: 0
Mapping mode: VLAN ID
The type of flow control: PQ
---------------------------------------------------------------------------
Binding times: 0
---------------------------------------------------------------------------To query the information about all the ONT profiles, do as follows:

huawei#display ont-profile
{ all<K>|profile-id<K>|profile-name<K> }:all

Command:
display ont-profile all
---------------------------------------------------------------------------
Profile ID Profile name Binding Times
---------------------------------------------------------------------------
1 ont-profile_1 0
2 ont-profile_2 0
3 ont-profile_3 0
4 ont-profile_4 0
5 ONT_PROFILE_HW_OT925 0
6 ONT_PROFILE_HW_HG850 0
7 ONT_PROFILE_HW_HG810 0
17 OT923 1
---------------------------------------------------------------------------
Total: 8System Response
The system displays the queried result when the command runs successfully.
The following table describes the parameters in response to the display ont-profile profile-id 1 command.
Parameter
Description

profile-id
Indicates the ID of the ONT capability set profile.

profile-name
Indicates the name of the ONT capability set profile.

Number of POTS ports
Indicates the number of POTS ports. When the value is adaptive, it indicates adaptive mode, in which the number of POTS ports is set based on the actual number on the ONT.

Number of ETH ports
Indicates the number of ETH ports. When the value is adaptive, it indicates adaptive mode, in which the number of Ethernet ports is set based on the actual number on the ONT.

Number of VDSL ports
Indicates the number of VDSL ports. When the value is adaptive, it indicates adaptive mode, in which the number of VDSL ports is set based on the actual number on the ONT.

TDM port type
Indicates the TDM port type. It can be E1 or T1 type.

TDM service type
Indicates the TDM service type. It can be TDMoGEM type only, that is, TDM service over GPON encapsulation mode.

Number of TDM ports
Indicates the number of TDM ports.

Number of MOCA ports
Indicates the number of MOCA ports.

Number of CATV UNI ports
Indicates the number of CATV ports on the user side. When the value is adaptive, it indicates adaptive mode, in which the number of CATV ports is set based on the actual number on the ONT.

Mapping mode
Indicates the mapping mode between the service stream and the GEM port. In single-bridge mode, the mapping mode can be configured to VLANID, 802_1PPRI, or VLANID+802_1PPRI. The default mode is VLANID. In multi-bridge mode, the mapping mode can be configured to PORT ID. You can run the mapping-mode(gpon profile) command to configure the mapping mode.

By default, the ONT supports the VLAN mapping mode. Each [urlhttp://www.thunder-link.com/HG8245H_p698.html]ONT[/url] can be configured with only one mapping mode.

The type of flow control
Indicates the type of the flow control, which can be PQ, GEMPORT-CAR, or FLOW-CAR.
When the PQ mode is used, you need to define the sending queue of the GEM port packets in the T-CONT. The T-CONT sends the upstream data strictly according to the queue priority. By default, there are eight queues (queue 0 to queue 7) in the system. Queue 7 has the highest priority and the traffic of this queue is assured first.
When the GEMPORT-CAR mode is used, the ONT restricts the rate of data packets carried on the GEM port based on the flow control settings of the GEM port. When the GEM port carries multiple service streams, the default scheduling mode of the ONT determines whether the PQ scheduling, WRR scheduling, or PQ+WRR scheduling is used. If there are multiple GEM ports in the T-CONT, the scheduling mode of the data packets between the GEM ports is also determined by the default scheduling mode of the ONT.
When the FLOW-CAR mode is used, the ONT controls all service streams carried on the GEM port one by one, which is more refined as compared with the flow control in the GEM flow control mode. After the flow control of the service streams is complete, the service streams are scheduled in the T-CONT queue. The scheduling mode is determined by the default scheduling mode of the ONT.

Binding times
Indicates the binding times of the ONT capability set profile.


The following table describes the parameters in response to the display ont-profile all command.
Parameter
Description

GPON Profile ID
Indicates the ID of the ONT capability set profile.

Profile name
Indicates the name of the ONT capability set profile.

Binding Times
Indicates the binding times of the ONT capability set profile.


For more information about the error message that the system displays against a command entered with incorrect syntax, see the "Syntax Check" in Parameter

the web-based management features supported by S series switches.
Table 1 Web-based management features supported by switches Category
Function

System management
Upgrade, patch loading, PoE, DNS, stacking, viewing log files, and setting the system time, SNMP parameters, and EasyDeploy parameters

NOTE:
Switches in V200R002 and later versions support SNMP and EasyDeploy parameter configuration.

Interface management
Viewing/configuring basic interface attributes and viewing statistics on an interface

Service management
VLAN, MAC address, STP, voice VLAN, DHCP, ARP, VRRP, and IGMP snooping

ACL management
Creating/modifying/deleting ACL rules and effective periods

QoS
Priority mapping, traffic policy, rate limit on an interface, traffic shaping, and congestion management

Route management
Viewing IPv4 routes, configuring static routes, and setting the preference of static routes

Security management
Port isolation, static user binding, AAA, 802.1x authentication, and MAC address authentication

Tools
Ping, Tracert, and VCT

CAC check errors are displayed when you create a link. Hence, you need to delete the useless connections on the port.
Product

OptiX OSN 1500A/1500B
OptiX OSN 2500
OptiX OSN 3500
OptiX OSN 7500
Fault Type

Configuration_Problem
Symptom

When you create a connection, a CAC check error is displayed. A connection fails to be created.
Cause Analysis

The boards support the CAC check function. If a link needs to be created, and if the sum of selected traffic rate and the traffic rate of all the existing links at the port exceeds the total bandwidth of the port, a CAC check error is displayed. Consequently, the link fails to be created.
Procedure

Make sure that the selected traffic rate is less than the remaining bandwidth of the port when you create a link. Delete the links that are not required at the port, and then create new links again.
Reference Information

None.

Many BD_STATUS alarms occur due to the ECC storm.
Product

OptiX BWS 1600G, OptiX OSN 2500
OptiX OSN 3500 II
OptiX OSN 3500
OptiX OSN 7500
Fault Type

NE offline
ECC
BD_STATUS
Symptom

In a network of the OptiX BWS 1600G, many NEs becomes unreachable to the T2000. The NE icons become grayed and then normal. In this process, each board reports the BD_STATUS alarm. This problem occurs several times a week, and lasts for one to two hours each time.
NOTE:
Recently, many NEs are expanded by adding boards or subracks. The new boards are all the LBE and TMX.
Cause Analysis

Conflict of IDs causes the BD_STATUS alarm and NEs to be unreachable.
In a complex network, there may be more than one route available for inter-network communication due to application of the OSC, ESC, and extended ECC. As a result, the ECC data overflows to cause incorrect IDs and incorrect ECC routes.
When an OptiX BWS 1600G NE is added, the DCN is configured improperly.
Procedure

Extract the log file of an OptiX BWS 1600G NE and check the ECC route. Many ECC routes are found, the number of which exceeds the number of NEs, that is, 20. When a new ID is created on the T2000, the T2000 prompts that the ID exceeds the range.
Check the OptiX BWS 1600G subrack. The extended ECC and ECC are found enabled. As planned, the extended ECC communication of the gateway NE at site OTM is to be disabled. Then, the communication over the ECC route between gateway NEs are terminated. Many NEs, however, are connected now. In this way, the ECC communication is terminated for most NEs in the network.
The previous analysis shows that the problem may be due to an ECC storm.
Disable all the extended ECC communication and most ESC communication on the OptiX BWS 1600G. Observation for weeks shows that the problem does not occur.
It is suspected that the ID conflict causes the BD_STATUS alarm when new boards are configured. Finally, check on the subrack shows that the SCC is reset frequently in the case of the BD_STATUS alarm. Now, the alarm is cleared.
An ECC storm causes the SCC to be so busy (confirmed by reset log) that it fails to respond to the signals of in-service boards. Then, the BD_STATUS alarm occurs.
Reference Information

None.

If certain packets are discarded in a network that employs the QinQ function, you can solve the problem by adding bytes to short packets.
Products

OptiX OSN 1500A/1500B
OptiX OSN 2500
OptiX OSN 3500 II
OptiX OSN 3500
OptiX OSN 7500
Fault Type

Configuration fault
Symptom

The point-to-point protocol over Ethernet (PPPoE) client services enter a switch for convergence. The converged services are accessed to an OptiX NE for transmission over networks to the broadband access server at the destination end. The PPPoE active discovery session-confirmation (PADS) data packets in the downlink services returning from the broadband server to the client side are lost. As a result, the PPPoE verification fails.
Cause Analysis

The PPPoE services include the PADI, PADO, PADR and PADS data packets. Compared with the other types of data packets, the PADS data packet is only of a 64-byte length which is the minimum data packet length that the Ethernet supports.
After the QinQ function is configured, two tags are added without changing the original data packet length: C-VLAN and S-VLAN. When the downlink services travel over the OptiX NE to the client-side NE, the external S-VLAN tag is detagged. Hence, the data packet length changes from 64 bytes to 60 bytes. As a result, when the 60-byte services travel over the switch, they are regarded as abnormal and extra-short Ethernet data packets and are thus discarded. In this case, the PPPoE endpoint cannot receive the PADS data packet. As a result, the PPPoE verification fails and the services are not available.
Currently, some Ethernet boards are added with the short-packet length extension function against the problem that the extra-short data packets caused during detagging are discarded. When the length of a data packet is extra-short, it can be complemented on the Ethernet boards on the client side and system side to ensure that the data packet is transmitted at a length compliant with the Ethernet specification.

The excessive attenuation between the TDC and RDC ports results in that the gain of the E3OAU cannot be set.
Product

OptiX BWS 1600G, Huawei OSN3500, Huawei MA5683T
Fault Type

Optical amplifier board
Symptom

In a new project, during network commissioning, the gain of the E3OAU board at a station needs to be enhanced. The gain value should be within the range and can be adjusted. The gain, however, cannot be set no matter through the network management system (NMS) or the command line.
Cause Analysis

According to the query, the output power at the TDC port of the E3OAU board is 10.5 dBm and the input power at the RDC port is -9.5 dBm. The attenuation between the TDC and RDC ports is 20 dB. Therefore, the gain of the board reaches the maximum and cannot be adjusted.
The reason is that the attenuation between the TDC and RDC ports is excessive.
Procedure

The on-site engineers remove the tail fiber from the DCM module between the TDC and RDC, reconnect the OAU, and then re-query the gain. The re-query shows that the attenuation between the TDC and RDC decreases to about 8 dB. Through the network management system, the gain of the board can be set normally. The fault is ratified.
Reference Information

None.

Six sets of OptiX OSN3500 that are configured with the N2SL64 boards form a 10 Gbit/s MSP ring. During the MSP ring switching test, the fiber is cut. The services, however, are not interrupted and the MSP switching is normal. Reconnect the fiber. The switching is restored after 10 minutes. The services, however, are interrupted immediately and are automatically restored in four minutes. At the same time, the optical board where switching is performed reports the B3_SD alarm. The B3_SD alarm lasts for two hours and then is automatically cleared. Check on the T2000. It is found that the MSP switching is normal. Replace the cross-connect board. It is found that the fault persists.

If certain packets are discarded in a network that employs the QinQ function, you can solve the problem by adding bytes to short packets.
Products

OptiX OSN 1500A/1500B
OptiX OSN 2500
OptiX OSN 3500 II
OptiX OSN 3500
OptiX OSN 7500
Fault Type

Configuration fault
Symptom

The point-to-point protocol over Ethernet (PPPoE) client services enter a switch for convergence. The converged services are accessed to an OptiX NE for transmission over networks to the broadband access server at the destination end. The PPPoE active discovery session-confirmation (PADS) data packets in the downlink services returning from the broadband server to the client side are lost. As a result, the PPPoE verification fails.
Cause Analysis

The PPPoE services include the PADI, PADO, PADR and PADS data packets. Compared with the other types of data packets, the PADS data packet is only of a 64-byte length which is the minimum data packet length that the Ethernet supports.
After the QinQ function is configured, two tags are added without changing the original data packet length: C-VLAN and S-VLAN. When the downlink services travel over the OptiX NE to the client-side NE, the external S-VLAN tag is detagged. Hence, the data packet length changes from 64 bytes to 60 bytes. As a result, when the 60-byte services travel over the switch, they are regarded as abnormal and extra-short Ethernet data packets and are thus discarded. In this case, the PPPoE endpoint cannot receive the PADS data packet. As a result, the PPPoE verification fails and the services are not available.
Currently, some Ethernet boards are added with the short-packet length extension function against the problem that the extra-short data packets caused during detagging are discarded. When the length of a data packet is extra-short, it can be complemented on the Ethernet boards on the client side and system side to ensure that the data packet is transmitted at a length compliant with the Ethernet specification.

Obtaining a Web File
The web file is released with the system software package and varies depending on software versions. The following uses S7700V200R003 as an example to describe how to obtain a web file.

Open the Internet Explorer and enter http://e.huawei.com/en/ in the address box.

NOTE:
You must have a permission to obtain the web file. To obtain the permission, choose My Huawei > Permissions.


Choose Support > Product Support.
Choose Downloads > Enterprise Networking > Switch > Campus Switch.
In the navigation tree on the left, choose S7700.
Select the version S7700 V200R003C00SPC500 and click the version number to view details.
Under Version and Patch Software, find the web file with the file name extension .web.7z and download the web file.
Loading the Web File and Configuring an HTTP User
The following uses S7700 V200R003 as an example.

Run the system-view command to enter the system view.
Run the http server load file-name command to load the web file.

NOTE:
Before loading a web file, upload the web file to the switch through FTP, SFTP, or TFTP. The web file must be loaded to the root directory of the switch's storage medium; otherwise, the web file cannot be loaded.


Run the http secure-server enable command to enable the HTTPS server function.
Run the http server enable command to enable the HTTP server function.
Run the aaa command to enter the AAA view.
Run the local-user user-name password { cipher | irreversible-cipher } password command to configure an AAA local user name and password.
Run the local-user user-name privilege level level command to set the local user level.

NOTE:
HTTP users of level 3 or higher can manage the switch on the web system, whereas HTTP users of level 2 or lower can only view the switch configuration.


Run the local-useruser-nameservice-type http command to set the service type to HTTP.
Logging In to the Web System
Open the Internet Explorer on the PC, enter http://IP address (for example, https://10.164.19.131) in the address box, and press Enter. The login dialog box is displayed.

NOTE:
The IP address is the management address of a device, and can be an IPv4 or IPv6 address depending on the HTTPS type (HTTPS IPv4 or IPv6) you have selected.

To ensure compatibility, the system converts http://IP address you entered into https://IP address.


Enter the HTTP user name, password, and verification code, and select a language for the web system.
Click Login or press Enter. The web system home page is displayed.
You can manage and maintain the switch after logging in to the web system.
You can buy Huawei MA5683T, OSN3500 from us.

Both the ONU and OLT check the link status and determine whether to trigger protection switching based on the link status.
If the OLT detects a fault on link A in Figure 1, it automatically switches to the protection-side link and uses the protection-side link to send messages to ONU 1 to notify that protection switching has occurred. In addition, the OLT notifies ONU 1 of the switching cause.
If ONU 1 detects a fault on link A in Figure 1, it automatically switches to the protection-side link and sends messages to the OLT to notify that protection switching has occurred. In addition, the ONU notifies the OLT of the switching cause.
After switching, services on ONU 1 are transmitted to the OLT through the protection port, all the backbone fibers connected to the OLT transmitted service packets, and ONU N is not affected. The changes on ONU 1 are as follows:
The state of the working port changes to standby.
The state of the protection port changes to active, and service packets are transmitted through link B in Figure 1.
After protection switching, ONU 1 can automatically switch back to the working port. The OLT sends an automatic switchback message and the switchback time, called the wait to restore (WTR) time, to the ONU.
If the OLT learns that ONU 1's working port and the working-side line are functioning properly and the working-side line stays normal during the WTR time, the OLT automatically switches back to the working-side line when the WTR time expires. In addition, the OLT notifies the ONU of the switching and switching cause.
If ONU 1 learns that its working port and the working-side line are functioning properly and the working-side line stays normal during the WTR time, the ONU automatically switches back to the working-side line when the WTR time expires. In addition, the ONU notifies the OLT of the switching and switching cause.

The EXT ports on the AUX boards of two sets of the OptiX OSN 3500 are incorrectly connected. As a result, boards fail to be added. To solve this problem, remove the cable that incorrectly connects the EXT ports.
Product

OptiX OSN3500
Fault Type

DCN Fault
BD_STATUS
Symptom

One SEP1 board on the OptiX OSN 3500 reports the BD_STATUS in an interrupted manner. Erase the data on the SCC board, reset the SCC board. It is found that all boards fail to be added. After the boards are added through other methods, the BD_STATUS alarm on the original SEP1 board persists. The board type of the original SEP1 switches between the PQ1 and the SEP1. The board type of the original EU08 board in slot 19 switches between the EU08 and the D12S. In addition, the idle slot 20 is incorrectly shown to house the D12S board.
Cause Analysis

The data configuration on the SCC board may be incorrect or the inter-board communication may be faulty.
Procedure

Erase the database and then reset the SCC board. It is found that no reset record exists and that all boards fail to be added.
Erase the database on the SCC board again. Then, reset the SCC board on site, and add boards again. It is found that the SCC board can be added but the other boards fail to be added.
After all the boards are successfully added, the original SEP1 board still reports the BD_STATUS alarm in an interrupted manner. The board type of the original SEP1 switches between the PQ1 and the SEP1. The board type of the original EU08 board in slot 19 switches between the EU08 and the D12S. In addition, the idle slot 20 is incorrectly shown to house the D12S board.
Exchange the SCC board with the SCC in the corresponding extended subrack (OptiX OSN 3500). Then, repeat Steps 1, 2, and 3, and then find that the problem persists.
Check the cables on site. It is found that a cable is used to connect the EXT ports on the two sets of OptiX OSN 3500. Remove the cable and then find that the problem is solved.
Reference Information

The EXT ports of the main subrack and the extended subrack can be connected only when the UXCSA board is configured to connect to the extended subrack. In this case, the alarms and configuration information of the extended subrack are transmitted to the SCC board in the main subrack through the EXT ports. The extended subrack need not be configured with the SCC board and the XCE board.
When the extended subrack is connected to a non-protection chain, the main subrack and extended subrack are independent of each other. Hence, the EXT ports of the main subrack and the extended subrack need not be connected. If the EXT ports are connected by a cable, collision occurs. As a result, boards fail to be added or cannot be smoothly added. In addition, even the board type switches.

It is confirmed that the alarm is generated because the incorrect setting of the jumpers on the SCC board is sent to the field.
The J17 and J16 jumpers on the N1GSCC board are used to control the input voltage of the equipment.
Remove the jumper cap: The equipment adopts the power supply whose input voltage is -60 V.
Maintain the jumper cap: The equipment adopts the power supply whose input voltage is -48 V.

The PoE card of an S5700 is ES0D0G48VA00. The possible causes are as follows:

The PoE power module is not installed in the PoE power slot.
The PoE power module is not powered on. 3. The DIMM is faulty.
For the handling methods, see "Cards Cannot Be Registered" in the Hardware Troubleshooting.

Whether attenuators are required depends on the transmit power at the Tx end and the receive power range allowed at the Rx end. If the transmit power at the Tx end is beyond the receive power range allowed at the Rx end, attenuators are required. The path loss is small in short-distance transmission. If optical modules with a long transmission distance (generally more than 40 km) are used for short-distance connection, it is recommended that you use attenuators to reduce the receive power at the Rx end.

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.

During the deployment of the OptiX OSN equipment, two rings are isolated from each other, but the ECC communication is available between the two rings. Check the relevant information. It is found that the extended ECC function is automatically enabled. Hence, to isolated two rings, you need to disable the extended ECC function.
Product

OptiX OSN 3500
Fault Type

DCN fault
Symptom

The OptiX OSN 3500 forms two rings: north ring and south ring. The two rings are isolated from each other. The north and south rings are connected to the NMS in the central equipment room through a hub for centralized monitoring. Check the ECC routing of the NE. It is found that the ECC routes between the north ring and the south ring are abnormally available.
Cause Analysis

The possible causes are as follows:
The fiber connection between the north ring and the south ring in the central equipment room is incorrect. For example, the fibers of the south ring are connected to the north ring.
The extended ECC function is automatically enabled.
Procedure

Disable the laser by using the T2000. It is found that the fiber connection on the north and south rings is correct.
Check the ECC routing. The OptiX OSN equipment is newly deployed. Thus, the extended ECC function is not preset and is in the default mode. That is, the AUX board automatically enables the extended ECC function. Disable the extended ECC function. It is found that the ECC communication between the north and south rings is unavailable.
Reference Information

When the OSI protocol is started at the network interfaces, the ECC communication is available between isolated subnetworks. For details, see MC-B9 Fibers Are Not Connected Between Equipment but ECC Communication Between Equipment Is Available.

Some optical ports reported the IN_PWR_ABN alarm, which indicated that the input optical power was abnormal, because optical modules were not securely installed. The fault was rectified by re-installing optical modules.
Product

OptiX OSN 3500
Fault Type

IN_PWR_ABN
Connection fault
Symptom

Some optical ports on a line board reported the IN_PWR_ABN alarm. The NMS showed that the input optical power at those optical ports was too high.
NOTE:
Generally, an optical port reports the LSR_NO_FITED alarm indicating that a laser is not installed if the optical module is not securely installed or is faulty. However, in this case, the optical ports reported the IN_PWR_ABN alarm instead of the LSR_NO_FITED alarm.
Cause Analysis

The possible causes are as follows:
The input optical power was too high.
The optical ports were faulty.
The input power detection circuits on the line board were faulty.
The optical modules were not securely installed.
The optical modules were faulty.
Procedure

Viewed the IN_PWR_ABN alarm on the NMS and determined the ID of the alarmed port (assuming that the alarmed port was A and it housed optical module C).
Measured the input optical power at optical port A using an optical power meter. The meter reported that the input optical power at optical port A was normal. Therefore, this issue was not related to the input optical power.
Removed optical module C and inserted it into optical port B. Optical port B did not report the IN_PWR_ABN alarm. Therefore, this issue was not related to optical module C.
Re-inserted optical module C into optical port A. Optical port A did not report the IN_PWR_ABN alarm, and the input optical power was normal. Therefore, the cause of this issue was that the optical module was not securely installed.
Related Information

None

NE ESC communication interrupted because of the closure of the OTU laser.
Product

OptiX Metro 6100
OptiX Metro 6040
OptiX BWS 1600G
Fault Type

NE Offline
ECC
Optical Transponder Unit
Symptom

An OptiX Metro 6100 NE at a station is unreachable by the NMS and cannot be manually logged in to. The ESC communication is interrupted and the NMS reports the NE_COMMU_BREAK and NE_NOT_LOGIN alarms.
Cause Analysis

The OptiX Metro 6100 and OptiX BWS 1600G support two types of supervisory channel: optical supervisory channel (OSC) and electrical supervisory channel (ESC). The ESC is transmitted by any OTU. The difference between the OSC and the ESC is that the OSC is transmitted by a dedicated supervisory channel board but the ESC is transmitted by the DCC byte or subcarrier module of the OTU.
When the ESC is used for communication, in the case that only the OTUs are used for connection of two NEs, when the ALS function is enabled or the lasers on the OTUs are turned off forcibly, the communication on the remote NE is interrupted, and users cannot log in to the NE.
Procedure

Analyze the engineering document of the network and query the ECC routing table. It is confirmed that the ESC communication is used for the upstream and downstream NEs of the unreachable NE.
It is confirmed that the lasers on an OTU board on the upstream peer NE are manually turned off for engineering purposes.
An engineer must go to the station and turn on the lasers on the OTUs to restore the communication.
Reference Information

It is not recommended to use the ESC when two NEs are connected through the OTUs.
If the ESC is used for communication, engineers must turn on the lasers of the OTUs forcibly and it is recommended to set Automatic Laser Shutdown to Disabled (Automatic Laser Shutdown for some OTU boards is set to Enabled by default).

When the OTU board accesses light, the laser at output end is disabled.
Product

OptiX BWS 1600G
Fault Type

Protection
Optical Transponder Unit
Symptom

During the TMX test in the OptiX BWS 1600G, it is found that no light is transmitted at the transmit end on the client side of the TMX board after the fiber on the WDM side of IN port is removed. After a meter is connected to the WDM side, the client-side laser on the TMX board cannot be enabled automatically (the automatic laser shutdown (ALS) function is enabled). In this case, you have to disable the ALS function, enable the client-side laser manually, and then enable the ALS function. Then, the situation becomes normal. That is, the client-side laser is enabled automatically after a meter is connected to the WDM side of the TMX board.
Cause Analysis

None.
Procedure

When the problem occurs, make sure that there is no R_LOS alarm on the OTU board (note that the alarm may be suppressed). If there is the R_LOS alarm and the automatic laser shutdown (ALS) function is enabled, the laser at the output end is disabled.
Check whether the SCC issues a command to disable the laser or not. If yes, the ALS function cannot take effect, unless the SCC issues a command to enable the laser.
Check whether the SCS protection is configured or not. If yes, the SCC disables the laser of one board to duplicate the service. In this case, the ALS function cannot take effect.
Reference Information

If there is service on the SCS, do not enable the laser that is disabled by the SCC. Otherwise, the service is interrupted, unless the fiber from the OTU to the SCS is removed.

When the OTU board accesses light, the laser at output end is disabled.
Product

OptiX BWS 1600G
Fault Type

Protection
Optical Transponder Unit
Symptom

During the TMX test in the OptiX BWS 1600G, it is found that no light is transmitted at the transmit end on the client side of the TMX board after the fiber on the WDM side of IN port is removed. After a meter is connected to the WDM side, the client-side laser on the TMX board cannot be enabled automatically (the automatic laser shutdown (ALS) function is enabled). In this case, you have to disable the ALS function, enable the client-side laser manually, and then enable the ALS function. Then, the situation becomes normal. That is, the client-side laser is enabled automatically after a meter is connected to the WDM side of the TMX board.
Cause Analysis

None.
Procedure

When the problem occurs, make sure that there is no R_LOS alarm on the OTU board (note that the alarm may be suppressed). If there is the R_LOS alarm and the automatic laser shutdown (ALS) function is enabled, the laser at the output end is disabled.
Check whether the SCC issues a command to disable the laser or not. If yes, the ALS function cannot take effect, unless the SCC issues a command to enable the laser.
Check whether the SCS protection is configured or not. If yes, the SCC disables the laser of one board to duplicate the service. In this case, the ALS function cannot take effect.
Reference Information

If there is service on the SCS, do not enable the laser that is disabled by the SCC. Otherwise, the service is interrupted, unless the fiber from the OTU to the SCS is removed.

Transparent transmission of multicast data for private-line users
Transparent transmission of IGMP messages
In the upstream direction, the service board determines whether to transparently transmit the received IGMP messages according to the VLAN-level IGMP transparent transmission policy and service-port-level transparent transmission policy. If transparent transmission is allowed, IGMP messages are added with the SVLAN tag on the service board and then are transmitted to the control board. After arriving at the control board, IGMP messages are broadcast by the control board within the SVLAN. If transparent transmission is not allowed, IGMP messages are dropped.

In the downstream direction, the IGMP messages transmitted from the network side are broadcast by the control board within the SVLAN and after they arrive at the service board, the service board determines whether to transparently transmit them according to the VLAN-level IGMP transparent transmission policy and service-port-level transparent transmission policy. If transparent transmission is allowed, the service board translates the SVLAN tag to the CLAN tag according to the configuration of the traffic stream and then transmits the messages to users. If transparent transmission is not allowed, IGMP messages are dropped.

Transparent transmission of unknown multicast data
In the upstream direction, the service board determines whether to transparently transmit the received unknown multicast data according to the VLAN-level IGMP transparent transmission policy and service-port-level transparent transmission policy. If transparent transmission is allowed, IGMP messages are added with the SVLAN tag on the service board and then are transmitted to the control board. After arriving at the control board, IGMP messages are broadcast by the control board within the SVLAN. If transparent transmission is not allowed, IGMP messages are dropped.

In the downstream direction, the unknown multicast data transmitted from the network side is broadcast by the control board within the SVLAN and after the data arrives at the service board, the service board determines whether to transparently transmit the data according to the VLAN-level IGMP transparent transmission policy and service-port-level transparent transmission policy. If transparent transmission is allowed, the service board translates the SVLAN tag to the CLAN tag according to the configuration of the traffic stream and then transmits the data to users. If transparent transmission is not allowed, unknown multicast data is dropped.

NOTE:
To prevent the multicast data of the multicast user provisioned with multicast service from being transmitted to the upstream unauthorized multicast sources, make sure that the policy of transmitting unknown multicast data is set to drop. The transparent transmission policies of unknown multicast traffic have the switches of two levels on a service board: the VLAN level and the service port level. When the two switches are both set to transparent transmission, the policy is transparent transmission. When either of the two switches is set to drop, the policy is drop. (Only transparent transmission is supported for connection-oriented traffic and the policy is not configurable in this case.)

Co-existence of IPTV service and transparent transmission of multicast data
Multi-service-port solution
IPTV service and multicast transparent transmission service are carried on two service ports, and the SVLAN of the service port that carries multicast transparent transmission service must not be the MVLAN.

The service port that carries IPTV service processes the received IGMP messages following the flow of processing IPTV service, and forwards the multicast data according to the multicast forwarding entry.

The service port that carries multicast transparent transmission service transparently transmits or drops the received IGMP messages according to the IGMP transparent transmission policy of the traffic stream, and transmits or drops the received unknown multicast data according to the unknown multicast transparent transmission policy of the traffic stream.

Single-service-port solution
IPTV service and multicast transparent transmission service are carried on one service port, whose SVLAN must not be the MVLAN.

When the Access Node receives upstream IGMP messages, it matches the multicast group address in IGMP messages to the programs in the MVLAN. If the group address successfully matches a program, the Access Node processes the messages as IPTV service. If the group address fails to match any program, the Access Node determines whether to transparently transmit the messages according to the IGMP transparent transmission policy of the SVLAN and service port. The Access Node transparently transmits the messages only when the IGMP transparent transmission policy is enabled for both the SVLAN and service port.

If the Access Node receives downstream IGMP messages that carry the MVLAN tag, the Access Node processes the IGMP messages as IPTV service. If the messages carry the SVLAN tag, the Access Node forwards them according to the IGMP transparent transmission policy of the SVLAN and service port. The Access Node transparently transmits the messages only when the IGMP transparent transmission policy is enabled for both the SVLAN and service port.

If the Access Node receives the multicast data of IPTV service, the Access Node forwards the multicast data according to the multicast forwarding entry. If the multicast data is unknown, the Access Node forwards the data according to the unknown multicast transparent transmission policy of the VLAN and service port. The Access Node transparently transmits the data only when the unknown multicast transparent transmission policy is enabled for both the SVLAN and service port.
Our company supply a large of Huawei OSN 3500, MA5683T.

The downstream optical amplifier board does not report MUT_LOS when the service between the upstream optical amplifier board and the FIU board is interrupted.
Product

OptiX Metro 6100
OptiX Metro 6040
Fault Type

Service Interruption
Optical Power Abnormity
Optical Multiplexer and Demultiplexing Unit
Optical Amplifier Unit
MUT_LOS
Symptom

The downstream optical amplifier board does not report MUT_LOS when the service between the upstream optical amplifier board and the FIU board is interrupted because of fiber jumper failure.
Cause Analysis

The transmit optical power of the SC2 ranges from 0 dBm to -4 dBm. The threshold for the downstream optical amplifier board to report MUT_LOS is -35 dBm. Assume that the transmit optical power of the upstream SC2 is -2 dBm. When the loss on the line side is no less than 19.5 dB (35-2-1.5-12, where 1.5 is the insertion loss of the FIU and 12 is the isolation of the FIU), the downstream optical amplifier board reports the MUT_LOS alarm.
When the WDM equipment is used in a MAN, the line loss is normally smaller than 19.5 dB. In this case, the downstream optical amplifier board does not report the MUT_LOS alarm when there is a fiber cut between the upstream optical amplifier board and the FIU.
Procedure

Check the output optical power of the upstream optical amplifier board. The output optical power is within the normal range.
Check the input optical power of the upstream FIU. The input optical power is very low. This indicates that the fiber between the optical amplifier board and the FIU is faulty.
Replace the fiber between the upstream optical amplifier board and the FIU. Then, the services become normal.
Reference Information

None.

The LWF board reports R_LOS because the incorrect fiber type leads to dispersion over-compensation.
Product

OptiX BWS 1600G
Fault Type

Dispersion Abnormity
Optical Transponder Unit
Fiber
R_LOS
R_LOF
Symptom

In a national backbone WDM network, the OptiX BWS 1600G is used. A, B, C, and D are the OTM, OLA, OADM, and OTM stations respectively. The distance between A, B, C, and D is more than 100 km. The 120 km dispersion compensation module (DCM) is added between C and D. A 100 km DCM is configured at the transmit end and a 20 km is configured at the receive end. The OTU boards that are configured at stations A, C, and D are the LWM, LWF, and LQG. The OTU is forced to emit light. After the system commissioning is complete, the LWF boards at stations A, C, and D report R_LOS on the WDM side.
Cause Analysis

The per-channel optical power is very low or no light is received.
The multiplexer/demultiplexer device is faulty, which causes wavelength drop.
The LWF board is faulty.
The OSNR does not meet the design requirements.
There is problem in the dispersion.
Procedure

The LWF boards at stations A, C, and D report R_LOS. Hence, the cause cannot lie in a certain board. Use an optical power meter to measure the optical power at the IN interface of every LWM board. The optical power is about -8 dBm, which meets the requirement. Hence, the problem is not caused by the LWF, D40, M40, or MR2.
In the same system, the problem does not occur on the LWM and LQG at 2.5 Gbit/s. Because the board at 10 Gbit/s has different OSNR and dispersion requirements from the board at 2.5 Gbit/s, the problem must be caused by a dispersion problem.
Remove the 20 km DCM at the receive end at station D. The alarm persists. Then, remove the 100 km DCM at the transmit end at station D, the alarm that is reported at station C changes to R_LOF. Remove the DCM at station C, the alarms on the corresponding LWFs at stations A and D change to R_LOF. Hence, the problem lies in the dispersion. Remove the 100 km DCM and the R_LOF alarm persists. The dispersion to be compensated that is obtained during the design phase cannot be more than 100 km. Check the fibers that are used on site. The G.655 fibers are used. The G.652 fibers, however, are used during the design phase. Hence, replace the fibers between station A and station D. Then, the R_LOS on the WDM side of the LWF is cleared and the problem is solved.
Reference Information

None.