Precaution of the NMS Failing to Synchronize ONUs

Keywords:

ONU version information, FTP, synchronization failure

Summary:

When an NMS synchronizes with ONUs from an OLT through the FTP, the character string length of the version information (such as the equipment ID, ONT model, ONU hardware version, ONU primary software version, ONU secondary software version) reported by some ONUs exceeds the maximum length defined in the protocol, and the reported character string does not contain any string tokenizer. As a result, the NMS fails to synchronize with the ONUs, and customers cannot manage the newly-deployed ONUs or deploy new services.

[Problem Description]

Trigger condition:

  1. The U2000 is earlier than V100R006C02CP3207 and the OLT is the MA5680T V800R011 earlier than V800R011C00SPC107 or MA5680T V800R012 earlier than V800R012C00SPC103.
  2. The NMS synchronizes with ONUs through the FTP.
  3. The character string length of the version information reported by some ONUs exceeds the maximum length defined in the protocol, and the reported character string does not contain any string tokenizer. (As defined in the protocol, the maximum length of the equipment ID or ONT model is 20 bytes and that of ONU hardware version, primary software version, and secondary software version is 16 bytes.)

When the above conditions are met, the NMS fails to synchronize with the ONUs.

Symptom:

The following describes the possible symptoms:

  1. The ONUs cannot be displayed on the NMS network topology.
  2. ONU information, such as the ONU SN (GPON), LOID (EPON), and equipment ID, cannot be displayed on the NMS interface.
  3. ONU information cannot be found on the OLT.

Identification method:

If the above symptoms occur, use the following methods to determine whether they are caused by the problem in this precaution.

If both the NMS and the OLT are in the version ranges mentioned above, proceed to the next step.

  1. On the NMS:

Synchronize with the ONUs on the NMS, and reproduce the synchronization failure. View the NMS synchronization log, U2000\server\var\logs\Develop\BmsAccess_9961\BmsAccess_*_*.log or U2000\server\var\logs\Develop\BmsAccess_1\BmsAccess_*_*.log (* indicates the date and time), and check whether the following error message is displayed:

Call Function return Error:DoUpdate(pTableDesc, pSrcTable, pOutPutTable)

If not, the problem described in this precaution does not occur. The synchronization failure is caused by other causes.

If yes, the character string length exceeds the maximum length when the NMS parses the POD file. Therefore, the information cannot be written into the NMS database. The problem can be solved by using the suggested solutions in this precaution (see “Measures and Solutions”).

  1. On the OLT:

Query all ONT version information on the faulty OLT. The command output of the GPON or EPON ONT version information is as follows:

 

In the command output, if the type name, software version, or hardware version of a certain ONU exceeds the maximum length listed in the following table, the character string reported by the ONU does not contain any string tokenizer, which results in the problem described in this precaution. The problem can be solved by using the suggested solutions in this precaution (see “Measures and Solutions”).

GPON ONU EPON ONU
Information Maximum Length Information Maximum Length
Equipment-ID 20 bytes ONT model 20 bytes
ONT Version 16 bytes ONT hardware version 16 bytes
Main Software Version 16 bytes ONT software version 16 bytes
Standby Software Version 16 bytes

Use the following method to confirm the character string: Copy the ONT model or software version information to the UltraEdit, and choose View > Display Ruler from the main menu.

 

 

[Root Cause]

The version information reported by the ONU does not contain a string tokenizer.

The following uses the ONU software version as an example.

Different ONUs use different methods to report the ONU software version. Generally, an ONU adds a string tokenizer \0 at the end of the reported character string. In this way, the upper-layer device detects how many bytes the software version reported by the ONU contains.

If an ONU reports a 16-byte character string to the OLT but does not add a string tokenizer at the end of the character string, the OLT cannot determine how many bytes this character string contains. Therefore, the character string length of the ONU software version reported by the OLT to the NMS is uncertain, and may exceed the maximum length supported by the NMS. In addition, the NMS does not support this abnormal behavior and considers that the character string length of the ONU software version exceeds the maximum length. The NMS fails to parse the ONU software version. Consequently, the NMS fails to synchronize with the ONU.

[Impact and Risk]

If the character string length of the reported ONU software version exceeds the maximum length defined in the protocol and reported ONU software version does not contain a string tokenizer, the NMS fails to synchronize with the ONU through the FTP. As a result, customers cannot manage the newly-deployed ONUs or deploy new services.

[Measures and Solutions]

Preventive measure:

The NMS synchronizes with ONUs through the SNMP instead of the FTP, but the synchronization efficiency will be reduced by about 80%.

If you need to use this solution, contact Huawei R&D engineers for confirmation in advance to prevent NMS performance from being affected. The specific methods for synchronizing with ONUs through the SNMP are as follows:

  1. Back up theU2000\server\nemgr\nemgr_access\dcp\platform\v100\feature\gdm\mxu_conf_dev_feature.xml file.
  2. Copy the backup file and edit it. Find <feature name=”PollOptimize” support=”1″>in the file as follows:

 

  1. The <dev type> structure in the file indicates an NE type and its version range information, among which the dev typefield uniquely identifies the NE type. Delete the corresponding <dev type> structure based on the faulty equipment type on the live network.

Use the MA5600T and MA5680T as examples. In the dev type=”41″ and dev type=”45″ fields, 41 indicates the MA5600T, and 45 indicates the MA5680T. Delete the corresponding structures (the following two lines in the given XML file) for the NMS to synchronize with these two types of NEs through SNMP:

<dev type=”41″ area=”[MA5600V800R006C03B000,MA5600V800R006C03BZ);[MA5600V800R006C32B010,MA5600V800R006C33BZ);[MA5600V800R006C72B010,MA5600V800R006C72BZ);[MA5600V800R007C00,MA5600V800RZ)”/>

<dev type=”45″ area=”[MA5600V800R006C32B010,MA5600V800R006C32BZ);[MA5600V800R006C72B010,MA5600V800R006C72BZ);[MA5600V800R007C00,MA5600V800R007CZ);[MA5680V800R007,MA5680V800R099CZ);[MA5683V800R007,MA5683V800R099CZ)”/>

The values of Dev type and the specific NE types are mapped as follows.

Dev type Equipment Type
41 MA5600T
45 MA5680T
75 MA5603T
2331 MA5608T

 

  1. Restart the following processes: profile, BmsAccess, BmsCommon, TL1NbiDm, inTL1NbiDm, BmsTimingTask, BmsTest, BmsAtur, and BmsHGMPDm. For processes that cannot be found, ignore them.

Solution:

A patch for the NMS is released to resolve this issue. Patch version: U2000 V100R006C02SPC303 (to be released on September 30, 2013)

A patch for the OLT is released to resolve this issue. Patch version: MA5600T V800R011C00SPC109 (to be released on September 15, 2013)

Patch version: MA5600T V800R012C00SPC103 (to be released on August 20, 3013)

The problem can be resolved by loading the NMS patch or the OLT patch.

SN1EMS4/SSN1EGS4 Basic BIOS Upgrade Guide

SN1EMS4/SSN1EGS4 Basic BIOS Upgrade Guide

  1. Choose Administration > NE Software Management > Board Software Upgradefrom the main menu.

1

  1. Log in to the NE and select the desired board.

2

  1. Select thebasic BIOS software version that you want upgrade.

 

3

  1. ClickStart. The upgrade starts.

4

  1. ClickActivate.The software is activated.

5

  1. After the software is activated, you can see from the specifications that the basic BIOS is upgraded to issue 2.36.

6

Attention: Before update basebios, must add the logic board, and ensure the board works normally.

 

S2300 switch models available in V100R006C01

Series Model Maximum Number of Service Ports
S2300-SI S2309TP-SI 9 total:8 10/100BASE-TX ports, 1 combo GE port (10/100/1000BASE-T + 100/1000BASE-X)

S2318TP-SI 18 total: 16 10/100BASE-TX ports, 2 combo GE ports(10/100/1000BASE-T + 100/1000BASE-X)

S2326TP-SI 26 total:24 10/100BASE-TX ports, 2 combo GE ports(10/100/1000BASE-T + 100/1000BASE-X)

S2300-EI S2309TP-EI-AC 9 total:8 10/100BASE-TX ports, 1 combo GE port (10/100/1000BASE-T + 100/1000BASE-X)

S2309TP-EI-DC 9 total:8 10/100BASE-TX ports, 1 combo GE port
(10/100/1000BASE-T + 100/1000BASE-X)

S2309TP-PWR-EI 9 total:8 10/100BASE-TX ports, 1 combo GE port
(10/100/1000BASE-T + 100/1000BASE-X)

S2318TP-EI-AC 18 total:16 10/100BASE-TX ports, 2 combo GE ports
(10/100/1000BASE-T + 100/1000BASE-X)

S2318TP-EI-DC 18 total:16 10/100BASE-TX ports, 2 combo GE ports
(10/100/1000BASE-T + 100/1000BASE-X)

S2326TP-EI-AC 26 total:24 10/100BASE-TX ports, 2 combo GE ports
(10/100/1000BASE-T + 100/1000BASE-X)

S2326TP-EI-DC 26 total:24 10/100BASE-TX ports, 2 combo GE ports
(10/100/1000BASE-T + 100/1000BASE-X)

S2326TP-PWR-EI 26 total:24 10/100BASE-TX ports, 2 combo GE ports
(10/100/1000BASE-T + 100/1000BASE-X)

S2352P-EI-AC 52 total:48 10/100BASE-TX ports, 2 100/1000BASE-X ports,
2 1000BASE-X ports

S2352P-EI-DC 52 total:48 10/100BASE-TX ports, 2 100/1000BASE-X ports,
2 1000BASE-X ports

Route Computing Fails During Creation, Optimization, or Rerouting of an ASON Service or During an Upgrade of a Static Service to an ASON Service

The route computing fails during creation, optimization, or rerouting of an ASON service or during an upgrade of a static service to an ASON service.

Fault Description

The following dialog box is often displayed when an attempt is made to create, optimize, or reroute an ASON service, or to upgrade a static service to an ASON service.

Network Topology

None.

Cause Analysis

There are the following possible causes for a route computation failure:

  1. The control link is unreachable. In other words, there are no physical paths from the source to the sink.
  2. A link fault has occurred. For example, if a link break or downgrade fault occurs when the ASON software searches for routes between the source and sink nodes, the ASON software will be unable to find the sink node.
  3. No idle channels are available. For optical-layer ASON, no end-to-end uniform idle timeslots are available.
  4. The add wavelengths are duplicated with the drop wavelengths at the source or sink node.
  5. Fiber connections are configured incorrectly for the source and sink nodes or for the intermediate nodes.
  6. If regeneration boards are configured at the optical layer, the possible causes are:
    1. Logical fiber connections are incorrectly configured for the regeneration boards.
    2. The optical module types of the regeneration boards do not match the optical module types of the add/drop boards.
    3. The service rates of the regeneration boards do not match the service rates of the add/drop boards.
    4. The FEC settings of the regeneration boards are inconsistent with the FEC settings of the add/drop boards.

Troubleshooting Procedure

Use the following steps to diagnose the fault:

  1. Check whether the control link is reachable. In the NE Explorer, choose Configuration > WDM ASON > WDM Control Link Management to check information about the control link. If node that the ASON service has to traverse is isolated, handle the control link fault to ensure that the control link is reachable.
  2. In the NE Explorer, choose Configuration > WDM ASON > WDM (like OSN 8800)Control Link Management. Check all of the TE links that the ASON service may traverse and ensure that Alarm Status is No Alarm and Link Status is Up for the TE links. If there are any TE link faults, handle them before performing the next step.
  3. Check whether idle channels are available. First, determine the trails that the ASON service may traverse through visual inspection. Then check the channel status (either on FIU or OTU boards) for the trails one by one. In addition, ensure that channels are not reserved. The following figure shows an example for navigating to the channel information on FIU boards.
  4. Check whether add wavelengths are duplicated with drop wavelengths at the source or sink node. Ensure that each wavelength is used for carrying only one service in the same direction.
  5. Ensure that all fiber connections are configured correctly. Focus on checking the fiber connections for the newly inserted boards after the deployment commissioning.
  6. If regeneration boards are used, check the configurations of the regeneration boards. Ensure that the fiber connections of the regeneration boards are configured correctly. Then check the optical module types, service rates, and FEC settings of the regeneration boards to ensure that they match those of the add/drop boards.

Conclusion and Suggestion

Routes can be computed successfully for ASON services only when the logical fiber connections are correctly configured and there are idle link and channel resources. If route computation fails, it is generally due to a link fault or the required channels are unavailable. Therefore, to pinpoint the root cause of the route computation failure, users must check the status of the required link and channel resources.

It is recommended that preset restoration trails be configured for ASON services. By configuring preset restoration trails, users can determine the trail to which an ASON service can be rerouted and at the same time ensure the quality of the trail to which the ASON service is rerouted.

What about H801X2CS Board?

The H801X2CS board is a 2-port 10GE Uplink Interface Card that provides two 10GE upstream or cascading optical ports.

Parameters of the H801X2CS board

1

Working principle of the H801X2CS board(MA5683T Equipment)

2

The basic working principle of the H801X2CS board is as follows:

  • The control module reports the status of and manufacturing information about the board, and provides the interface information. The control module also manages the modules on the board, and processes alarms.
  • The interface module provides two 10GE ports.
  • The synchronization Ethernet clock module extracts clock signals from the 10GE signals, and synchronizes the 8 kHz clock of the control board with the clock signals.
  • The power module supplies power to other functional modules of the board.
  • The clock module provides clock signals for other functional modules of the board.

 

Ports of the H801X2CS board

3

NOTE
Different optical modules can be configured to achieve different reaches.

Front panel and LED of the H801X2CS board

4

 

How to start an Upgrade Tasks?

1

The error tolerance function is enabled for an upgrade to OptiX OSN 8800/OSN 6800/3800 V100R007C02SPC100/SPC200/SPC300. That is, if a board fails to be upgraded during the upgrade, the upgrade task pauses. When this occurs, continue the upgrade task. For details, you can see thunder-link.com.

Step 1 Start an upgrade task. Choose Administration> NE Software Management > NE Upgrade Task Management from the main menu. Right-click the desired upgrade task and choose Start Task from the shortcut menu. In the dialog box that is displayed, click Yes.

2

5

During the upgrade, the overall upgrade progress is displayed.

 

3

  • If the upgrade fails at the Backup phase, ask field engineers to handle exceptions and then perform the upgrade again.
  • If the upgrade fails at the Load Software, Dispense, Activate, or Commit phase, see section Thunder-link.com. Then perform the upgrade again after the field engineers handle the exceptions.

 Step 2 Confirm that the upgrade is complete. After all the preceding upgrade steps are performed, check whether the Operation Statefield for each operation displays Success.

 

4

Step 3 Restore the system settings. If you disabled the automatic database backup and alarm synchronization functions when preparing for the upgrade, enable them again now. Before performing another upgrade, you must disable the functions again according to section 7 “Checking System Settings.”

—-End

What’s the Working Principle of SCUF?

Working principle of the H801SCUF board

SCUF.png

Backplane Connector

The basic working principle of the H801SCUF board is as follows:

  • The control module manages the entire board and the service boards, and communicates with the fan tray through the extended serial port.
  •  The power module supplies power to other functional modules of the board.
  • The clock module provides clock signals for other functional modules of the board.
  • The switching module provides the GE port and the 10GE port to switch and aggregate services at Layer 2 or Layer 3.
    – Providing 16 GE ports to implement GE switching on each service board
    – Provides four GE channels and one 10GE channel for each upstream slot, which are
    used for upstream transmission through the upstream board.
  • NOTE
  • The switching module provides four GE channels and one 10GE channel for each upstream slot, generally corresponding to an upstream board with four GE ports (GICD, GICE, or GSCA) or an upstream board with a 10GE port besides the following situations:
  • The H801SCUF control board supports the GICK board (an upstream board with two GE ports), but only the first GE port on the GICK board is available. In addition, the GICK board must be a version released later than April 2010.
  • The H801SCUF control board supports the X2CS board (an upstream board with two 10GE ports), but only the first 10GE port on the X2CS board is available. The H801SCUF control board does not support the X2CA board.
  • Either the four GE ports in the first upstream slot or the GE ports on the H801SCUF control board can be selected through the electronic switch for upstream transmission.
  • On the MA5600T, when the GICD/GICE/GSCA/GICK board is configured in slot 19, the GE ports on these boards cannot be used together with GE ports on the front panel of the H801SCUF control board. For the 10GE upstream boards such as X1CA and X2CS, there is no such restriction. That is, the 10GE ports on these boards can be used together with the GE ports on the front panel of the H801SCUF control board.
  • On the MA5603T, when the GICD/GICE/GSCA/GICK board is configured in slot 8, the GE ports on these boards cannot be used together with the GE ports on the front panel of the SCUF control board. For the 10GE upstream boards such as X1CA and X2CS, there is no such restriction. That is, the 10GE ports on these boards can be used together with the GE ports on the front panel of the SCUF control board.
  • Either the last of the four GE ports in the second upstream slot or the daughter board attached to the SCUF control board can be selected through the electronic switch.
  • On the MA5600T, when the GICD/GICE/GSCA board is configured in slot 20, the fourth GE port on these boards cannot be used together with the daughter board attached to the SCUF control board. When the GICK board is configured in slot 20, only the first GE port on the GICK board is available. For the 10GE upstream boards such as X1CA and X2CS, there is no such restriction.
    That is, the 10GE ports on these boards can be used together with the daughter board attached to the SCUF control board.
  • On the MA5683T, when the GICD/GICE/GSCA board is configured in slot 9, the fourth GE port on these boards cannot be used together with the daughter board attached to the SCUF control board. When the GICK board is configured in slot 20, only the first GE port on the GICK board is available. For the 10GE upstream boards such as X1CA and X2CS, there is no such restriction. That is, the 10GE ports on these boards can be used together with the daughter board attached to
    the SCUF control board.