When Interconnection Fails Due to Inconsistent Timeslot Numbering Modes

The services in certain timeslots are intermittently available during the equipment interconnection. During the problem investigation, it is found that the timeslot numbering modes are not consistent.

Product

• OptiX OSN 1500A/1500B
• OptiX OSN 2500
• OptiX OSN 3500
• OptiX OSN 3500 II
• OptiX OSN 7500

Fault Type

• Equipment interconnection failure

Symptom

The OptiX OSN devices form a chain network that connects to an optical interface switch. The user configures VC-12 pass-through services in timeslots 1-38 on the OptiX OSN device. The services in timeslots 1-2, 4-5, and 7-8 are intermittently available on the switch. If the user configures VC-12 pass-through services in timeslots 1-63, this problem does not occur.

Cause Analysis

The timeslot numbering modes are not consistent. Currently, timeslot numbering modes are classified into sequential mode and interleaved mode, and Huawei equipment adopts the sequential mode by default. According to the user, the services are intermittently available. Thus, it can be inferred that the service configurations are correct, and the problem may be caused by the inconsistent timeslot numbering modes between the switch and the transmission device.

Procedure

1. Through investigation, the switch of the user adopts the interleaved mode, which is inconsistent with the default timeslot numbering mode of Huawei equipment.
2. The T2000 V100R002 that is used by the user can directly use the line numbers (Lucent mode) to create services in timeslots 1-38. After being reconfigured, the services on the switch become normal.

10G Card Issue in Quidway S5300

In S5700 when configuring voice vlan there is an error says “no enough resources”

When OptiX OSN 1800 Database Recovery Failures

The SCC Board Reports the HARD_BAD Alarm

The SCC board reports the HARD_BAD alarm. When you query the version information about the BPA board and the GSCC board, you find that the version of the BPA board does not match the version of the GSCC board. After you upgrade the BPA board, the HARD_BAD alarm is cleared.

Product

OptiX OSN 3500

Fault Type

HARD_BAD

Others

Symptom

The SCC board reports the HARD_BAD alarm. After the working and protection SCC boards are switched, the HARD_BAD alarm persists.

Cause Analysis

Check the HARD_BAD alarm on the T2000 to determine the slot of the faulty board and the cause of the fault.

Procedure

1. Check the HARD_BAD alarm on the T2000. Location Information displays information about the board that causes the alarm. After you select an alarm on the T2000, the alarm location information is displayed in the lower left corner of the page.
2. Check the software version of the board.
   1. Choose Report > Board Information Report from the Main Menu.
   2. Select the NE, and then click .
   3. Right-click a parameter name in Board Information Report and choose Software Version to display the software version of the board.
3. Check the software version of the board, and you can find that the version of the BPA board does not match the software version of the GSCC board.
4. Upgrade the BPA board. After the BPA board is upgraded, the HARD_BAD alarm is cleared.

Related Information

None.

More related:

How to do when Abnormal Optical Power Reporting Caused by the Coupling Exception

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

Incorrect Configuration of the ZL80018 Chip on OptiX OSN 1800

OTU Boards Report the IN_PWR_LOW Alarm Due to Wavelength Wander

The wavelength wander of an OTU board causes the downstream OTU boards to report the IN_PWR_LOW alarm.

Product

OptiX BWS 1600G, Huawei OSN3500, Huawei MA5683T,Huawei MA5608T

Fault Type

Optical power abnormity

Optical Transponder Unit

IN_PWR_LOW

Symptom

The OptiX BWS 1600G is networked in the chain mode: OTM----OTM (A)----OTM (B) ----OTM, that is, multiple OTM stations form a ring of 7 channels (one is standby). One day, the IN interface of the 18th-channel LWC board at station B reports the IN_PWR_LOW alarm.

Cause Analysis

• The LWC board of station B is faulty or a fault in the fiber from the D40 to LWC causes excessively high attenuation.
• The launched optical power of the opposite station A is abnormal. As a result, the local received optical power is abnormal.
• Other boards are faulty, for example, the M40 at the transmit end or the D40 at the receive end is faulty. Because these two boards are passive optical components, they are less likely to be faulty.
• Other causes.

Check the optical power of the equipment level by level from the downstream to the upstream according to the signal flow for fault locating.

Procedure

1. Measure the input optical power of the D40 and LWC at station B. Excessively low optical power causes the OTU board to report the alarm.
2. Scan the wavelengths of the D40 and OAU at station B with a multi-wavelength meter. The 18th wavelength is absent.
3. The wavelength ranges of the LWC and M40 at station A are in consistent. The 18th wavelength is not input to the M40. Measure optical interface 23 of the M40 at station A. The input optical power is measured as -2 dBm (normal).
4. Scan the wavelengths of the M40 board at station A. The 18th wavelength is still absent. Use the optical power meter to measure the optical power, which is found normal.
5. Directly scan the wavelengths of the OUT interface of the 18th-wavelength LWC board. The root cause of the fault is finally located. The scanning result shows that the optical power of the 18th wavelength is -2 dBm (normal value) and the wavelength is 1547.468 nm. The standard wavelength, however, is 1546.92 nm. The wavelength wander is up to 0.5 nm. In the WDM system, the wavelength wander range of the OTU board should be not more than 0.15 nm.
6. Temporarily solve the problem by using the standby wavelength between the two stations. Apply for a new 18th-wavelength LWC board and replace the faulty LWC board.

Reference Information

None.

More related:

when Ring MSP Configuration Failures on SSN1SLQ16 Boards on OSN 3500 Products

How to do when Occasional Hot Patch Installation Failures?

Why Broadcast Packets Cannot Be Transmitted Successfully on Several HMSTP Data Boards?

The GE Port on the Client Side Reports LINK_DOWN Alarm

Due to the auto negotiation, the GE port reports LINK_DOWN alarm when FDG connects to a GE port of Cisco 12410 router on the client side.

Product

OptiX BWS 1600G, Huawei OSN3500, Huawei MA5683T,Huawei MA5608T

Fault Type

Service interruption

Equipment Interconnection

Client Equipment

LINK_DOWN

Symptom

In one DWDM network, two type of GE services are transmitted over wavelengths, which are generated by the FDG board. When the FDG connects to Cisco Router 12410, the GE port on the router reports LINK_DOWN alarm.

Cause Analysis

This problem occurs because the FDG board is improperly connected to the client-side device or the fiber between them is damaged. If auto-negotiation function is required when the FDG connects to the client-side device, this problem also occurs.

Procedure

1. Check the fiber that connects the client-side port on the FDG to the router.
2. Check the input optical power on the T2000. The input optical power is found normal.
3. Use the optical power meter to check the output optical power of the client-side device. The output optical power is found normal.
4. If Cisco router still reports LINK_DOWN. Perform the following setting:
   1. In the NE Explorer, select the desired FDG board and choose Configuration > WDM Interface from the Function Tree.
   2. Select By Board/Port(Channel).
   3. Select Channel from the drop-down list.
   4. Adjust the Auto Negotiation as Enabled in the Basic Attributes tab and click Apply.
5. Confirm that the port on Cisco router reports LINK_UP.

Reference Information

None.

More related:

When Interruption of Existing Services on Some Data Boards of OSN Products

How to do when Bit Errors Occur in Lower Order Path Due to Improper Grounding

What Caused Occasional NE Unreachability

The Received Optical Power of Downstream Stations Is not Flat and Some Wavelengths Report the IN_PWR_LOW Alarm

The received optical power of downstream stations is not flat and the wavelengths report the IN_PWR_LOW alarm because the designed pass-through wavelengths are not connected.

Product

OptiX BWS 1600G, Huawei OSN3500, Huawei MA5683T,Huawei MA5608T

Fault Type

Optical power abnormity

Optical Transponder Unit

IN_PWR_LOW

Symptom

The result of commissioning the OptiX BWS 1600G system at station A shows that the three LWC1 boards use the 21st wavelength, 23rd wavelength, and 40th wavelength. When the fibers are properly connected, the optical amplifier board is adjusted to the nominal value. The LWC1 boards that use the 21st wavelength and the 40th wavelength report the IN_PWR_LOW alarm.

Cause Analysis

• The tail fiber or optical attenuator is faulty.
• The transmit part of the opposite end or the receive part of the local end is faulty.

Procedure

1. Remove the tail fiber of the D40 and then measure the launched optical power of each optical interface of the D40. The launched optical power of the LWC1 boards that use the 21st wavelength and the 40th wavelength is about 5 dB different from that of the LWC1 board that uses the 23rd wavelength. Check on the upstream station shows that the upstream 2*OTM station B has only one OTU (LWC1 board using the 23rd wavelength) and only the LWC1 board of No.1 OTM is connected to the LWC1 board of No.2 OTM on the client site. Further check on the upstream OTM station C shows that station C has three LWC1 boards, just like the local station.
2. According to the design document, the 21st and 40th wavelengths are to pass through station B but they are not connected. To connect the two wavelengths, connect the interface on D40 at station OTM1 for the two interfaces to the mapping interface on M40 of station OTM2.
3. When the alarm is cleared, check the input optical power of the three local LWC1 boards. The optical power flatness meets the requirement.

Reference Information

None.

More related:

Incorrect Configuration of the ZL80018 Chip on OptiX OSN 1800

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

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

Many BD_STATUS Alarms Occur Due to the ECC Storm

Many BD_STATUS alarms occur due to the ECC storm.

Product

OptiX BWS 1600G, Huawei OSN3500, Huawei MA5683T, MA5608T

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

1. 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.
2. 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.
3. 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.
4. 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.

More related:

How to do when Occasional Hot Patch Installation Failures?

Why Broadcast Packets Cannot Be Transmitted Successfully on Several HMSTP Data Boards?

Warning of Unexpected NE Resets Resulted from Resetting Boards Without a CPU on MSTP NEs

MSBBE Bit Errors and OTU_LOF Alarm Occur in a DWDM 10G Network Due to the Incorrect PMD

The bit errors occur in a DWDM 10G network due to the incorrect PMD.

Product

OptiX BWS 1600G, Huawei OSN3500, Huawei MA5683T, MA5608T

Fault Type

Bit error

PMD Abnormity

OTU_LOF

Symptom

After the fiber of the OTM site (node CLS1 to node CLS2) is replaced, the MSBBE bit errors and OTU_LOF alarm occur on the OTM site.

Cause Analysis

The bit errors occur in the network due to the incorrect PMD.

Procedure

1. The optical power is measured and adjusted to the reference value. After the adjustment, bit errors and the alarm are cleared. Half an hour later, the bit errors and alarm occur again.
2. Add or remove the DCM to extend the distance from 5 km to 10 km. Then, the bit errors and alarm are cleared. One hour later, the bit errors and alarm occur again.
3. Then, the customer checks the features of the new fiber (chromatic dispersion and polarization mode dispersion). The check shows that the chromatic dispersion (CD) in the fiber is normal but the polarization mode dispersion (PMD) is excessively high. The problem is solved when the customer replaces the fiber.

Reference Information

PMD coefficient relation is given in Table 1.

Table 1 PMD coefficient relation
Bit Rate(Gbit/s)	Max PMD(ps) a	PMD Coefficient (ps.km) a
2.5	40	< 2.0
10	10 (with no FECb)	< 0.5
40	2.5	< 0.125
a: Standards suggest a value for 10 Gbit/s only. Values at other data rates are nonetheless accepted by the industry. b: Most long-haul instruments perform forward error correction (FEC).

More related:

When Interruption of Existing Services on Some Data Boards of OSN Products

How to do when Bit Errors Occur in Lower Order Path Due to Improper Grounding

when Ring MSP Configuration Failures on SSN1SLQ16 Boards on OSN 3500 Products

The Minimum Optical Power of the SC2 Is Detected As -35 dBm

Because the fibers or the fiber jumpers are in fault, the minimum optical power of the SC2 is detected as -35 dBm.

Product

OptiX BWS 1600G, Huawei OSN3500, Huawei MA5683T, MA5608T

Fault Type

Optical power abnormity

Optical Supervisory Channel Unit

Symptom

A WDM chain with the OptiX BWS 1600G NEs is deployed in an office. The line attenuation between site A and site B is about 30 dB. One day, the received optical power of the two sites decreases by 8 dB and the OSNR also decreases. The optical power of the supervisory channel, however, remains unchanged, which is -35 dBm.

Cause Analysis

As the optical power of the supervisory channel remains unchanged, the cause does not lie in the fiber cable or out-frame ODF, but in the span between the in-frame FIU and OAU of the two sites.

Procedure

1. Test the optical power of MON interfaces of the OBU and FIU boards for transmitting signals to the opposite end at the two sites.
2. The optical power difference of the two MON interfaces is as slight as not more than 1 dB. It can be concluded that the no problem exists between the OBU at the transmit end and the RC port of the FIU, and no problem exists on the OUT interface of the FIU. The detected optical power of MON interfaces is 1% of the optical power of the OUT interface. If the OUT interface is faulty, the receiving of the SC2 at the opposite end is affected.
3. The previous analysis shows that the problem lies in the receive port of the FIU or the fiber from the FIU to OAU. There is low possibility that the two stations have the same fault. In addition, for further test, the optical path must be disconnected. To locate the problem for once, re-compose the fault locating scheme.
4. The cable problem can be excluded if the detected optical power of the SC2 is consistent with the actual optical power. The received optical power of the SC2 for receiving signals from the opposite end is tested after suspicion. The actual value is -35 dBm. If the transmitted optical power of the SC2 is -4.2 dBm, it is concluded that the attenuation of the supervisory channel is around 40 dB and the attenuation of the service channel is around 38 dB.
5. It can be concluded that cables and the fiber jumper between the FIU and ODF of the two stations are faulty. Then, test cables and the ODF with the cooperation of users. Locate and rectify the fault.

Reference Information

None.

More related:

Incorrect Configuration of the ZL80018 Chip on OptiX OSN 1800

What Caused Occasional NE Unreachability

How The SSE3LWF Board Reports the OTU_LOF Alarm When Interworking with the SSE1TMR

About board autoload force.

Function

board autoload force is used to enable forced-autoload for a board. After this command is executed successfully and forced-autoload takes effect, the board software is loaded from the control board to the board during board startup, irrespective of whether the software version on the board is consistent with the software version on the control board.

NOTICE:

Exercise caution when using this command to avoid board function failures.

undo board autoload force is used to disable forced-autoload for a board. After this command is executed successfully, the board follows the common principle for board software loading. The default state is disable.

Format

board autoload force
undo board autoload force

Parameters

None

Modes

Diagnose mode, Huawei OSN3500, Huawei MA5683T, Huawei MA5608T

Level

Super user level

Usage Guidelines

In the privilege mode or global config mode, run the diagnose command to enter the Diagnose mode.

Example

To enable forced-autoload for a board, do as follows:

huawei(diagnose)%%board autoload force

To disable forced-autoload for a board, do as follows:

huawei(diagnose)%%undo board autoload force

System Response

• If you run the board autoload force command on a board with forced-autoload enabled, the system displays a message "Forcing board autoload switch has been turned on".
• If you run the undo board autoload force command on a board with forced-autoload disabled, the system displays a message "Forcing board autoload switch has been turned off". 

More related:

How to do when Occasional Hot Patch Installation Failures?

Why Broadcast Packets Cannot Be Transmitted Successfully on Several HMSTP Data Boards?

Warning of Unexpected NE Resets Resulted from Resetting Boards Without a CPU on MSTP NEs

What's the board add?

Function

This command is used to add a board offline. After adding a board, you can configure and query the board data even when the board status is Failed. After you insert the board into a slot, the board status becomes Normal and configuration data takes effect.

NOTE:

All power interface boards do not support auto-find. Therefore, the power interface boards (except the PRTG board) must be added using this command. The PRTG board does not support software management. Its status is normal after you run this command to add it, irrespective of the physical board status.

Format

board add frameid/slotid board-type
board add frameid/slotid H801ETHA { sub0 etha_sub0_type | sub1 etha_sub1_type } *
board add frameid/slotid H801ETHB [ sub0 sub0_type ]
board add frameid/slotid H801AIUG { sub0 aiu_sub0_type | sub1 aiu_sub1_type } *
board add frameid/slotid H801TOPA sub0 sub0_type
board add frameid/slotid H801BIUA [ sub0 sub0_type ]
board add frameid/slotid H801CITB [ sub0 sub0_type ]
board add frameid/slotid H801CITD [ sub0 sub0_type ]

Parameters

Parameter	Description	Value
frameid/slotid	frameid/slotid indicates the subrack ID and slot ID. Enter a slash (/) between the subrack and slot IDs. board-type indicates the board model. When adding a board, you must specify the subrack ID, slot ID, and model of the board.	Please see Differences Between Shelves.
board-type		Enumerated type. Options: Options vary according to the device type.
sub0 etha_sub0_type	Indicates the type of daughter board 0 of the H801ETHA Ethernet cascade board. You can use one or two daughter boards for the H801ETHA Ethernet cascade board. You can add a daughter board only after the H801ETHA Ethernet cascade board is added.	Enumerated type. Option: o4gs (it provides four GE optical ports for cascade).
sub1 etha_sub1_type	Indicates the type of daughter board 1 of the H801ETHA Ethernet cascade board. You can use one or two daughter boards for the H801ETHA Ethernet cascade board. You can add a daughter board only after the H801ETHA Ethernet cascade board is added.	Enumerated type. Option: o4gs (it provides four GE optical ports for cascade).
sub0 sub0_type	Indicates the type of the daughter board 0. For H801ETHB, you can install one or do not install any daughter board. When the backplane does not support the board binding, the x1ha daughter board provides an HG port (inter-chip cascading port) for inter-board interworking. H801TOPA is used for TDM services and provides the E1 and STM-1 ports through different daughter boards to implement native TDM or CESoP function. H801BIUA, a BITS interface unit board, inputs and outputs BITS clock signals. H801CITB and H801CITD, integrated interface transfer boards, provide the clock source for the system.	Enumerated type. Options are as follows: H801ETHB: x1ha (provides inter-chip cascading port for inter-board interconnection) H801TOPA: nh1a: supports TDM signals transmitted over the E1 port in the upstream direction for implementing the native TDM function. eh1a: supports TDM signals transmitted over the E1 port in the upstream transmission for implementing the CESoP function. o2ce: supports TDM signals transmitted over the STM-1 optical port in the upstream direction for implementing the native TDM function. cssa: supports TDM signals transmitted over the STM-1 optical port in the upstream direction for implementing the CESoP function. H801BIUA: h801ckma and h802ckma. The daughter boards can independently provide 32.768 MHz clock signals or trace external 8 kHz clock reference source signals and outputs synchronized 32.768 MHz clock signals. H801CITB and H801CITD: bitsb. This daughter board recovers 2 Mbit/s clock signals or reshapes 2 MHz signals. Processed clock signals can be used as the system clock signals.
sub0 aiu_sub0_type	Indicates the type of daughter board 0 of the H801AIUG board. H801AIUG is the ATM interface unit board that is connected to the ATM-DSLAM and provides the ATM and IP private services. H801AIUG provides two daughter board slots. You can use two O2CS daughter boards. If you use only one daughter board, you must install the daughter board in slot 0.	Enumerated type. Option: o2cs (it provides two ATM optical ports for upstream transmission).
sub1 aiu_sub1_type	Indicates the type of daughter board 1 of the H801AIUG board. H801AIUG provides two daughter board slots. You can use two O2CS daughter boards.	Enumerated type. Option: o2cs (it provides two ATM optical ports for upstream transmission).

Modes

Global config mode

Level

Operator level

Usage Guidelines

• When adding a board, pay attention to the following points:
  • The subrack and slot IDs of the added board in the command line must be consistent with those of the actual subrack and slot.
  • The added board type in the command line must be consistent with the actual board type.
• You can add a board in the following two modes:
  • Add a board offline.
    1. Run the board add command to add a board in the vacant slot and the system reports a board faulty alarm (alarm ID is 0x02310000).
    2. Insert the board into the matched slot manually. If the inserted board type is consistent with the added board type, the system reports a board fault clear alarm (alarm ID is 0x02320000). If they are inconsistent, the system reports a mismatch event (event ID is 0x02300082).
  • Automatically find a board.
    1. Insert a board into the vacant slot.
    2. The system displays the message indicating that the board is found automatically.
    3. Run the board confirm command to confirm the automatically found board.

Example

To add a GPBC board in slot 0/3 offline, do as follows:

huawei(config)#board add 0/3 H801GPBC
  0 frame 3 slot board added successfully

To add an H801BIUA board whose daughter board type is H801CKMA to slot 0/0 offline, do as follows:

huawei(config)#board add 0/0 H801BIUA
{ <cr>|sub0<K> }:sub0
{ sub0_type<E><h801ckma,h802ckma> }:h801ckma
                                                                                
  Command:
          board add 0/0 H801BIUA sub0 h801ckma
  0 frame 0 slot board added successfully

System Response

• The system displays the message "x frame x slot board added successfully" after the board is added offline successfully. The x and y are the subrack ID and slot ID respectively.
• For more information about the error message that the system displays against a command entered with incorrect syntax, see the "Syntax Check" in Parameter.

Huawei OSN3500, Huawei MA5608T, Huawei MA5683T

More related:

When Interruption of Existing Services on Some Data Boards of OSN Products

How to do when Bit Errors Occur in Lower Order Path Due to Improper Grounding

when Ring MSP Configuration Failures on SSN1SLQ16 Boards on OSN 3500 Products