What’s the xDSL Noise Margin Profile Configuration of display xdsl noise-margin-profile(tr165) ?

Function Description

This topic describes the commands related to xDSL noise margin profile configuration in TR165 mode. The commands can be used to add, delete, modify, and query an xDSL noise margin profile.

display xdsl noise-margin-profile(tr165)

Function

This command is used to query an xDSL SNR margin profile. To query the information such as the upstream/downstream target SNR margin, the upstream/downstream minimum SNR margin, the maximum upstream/downstream SNR margin, the SNR margin for upstream/downstream rate upshift, and the SNR margin for upstream/downstream rate downshift, run this command.

Format

display xdsl noise-margin-profile [ profile-index ]

Parameters

Parameter Description Value
profile-index Indicates the ID of the xDSL SNR margin profile to be queried. This parameter is optional. Numeral type. Range: 1-4294967294.

Modes

Privilege mode, VDSL mode, ADSL mode

Level

Operator level

Usage Guidelines

  • In the global config mode, run the interface vdsl command to enter VDSL mode or run the interface adsl command to enter ADSL mode.
  • If the ID of an xDSL SNR margin profile is not specified, the brief information about all the xDSL(like ADEE) SNR margin profiles in the system is displayed. If the ID of an xDSL SNR margin profile is specified, the detailed information about this xDSL SNR margin profile is displayed.

Example

To query the brief information about all xDSL SNR margin profiles, do as follows:

huawei#display xdsl noise-margin-profile                               
{ <cr>|profile-index<U><1,4294967294> }:                                               
                                                                                
  Command:                                                                      
          display xdsl noise-margin-profile                                     
  ------------------------------------------------------------------------------
     Profile  Profile          Target downstream     Target upstream       Ref
     Index    Description      SNR margin (0.1dB)    SNR margin (0.1dB)    Times
  ------------------------------------------------------------------------------
           1  DEFVAL                           60                    60       48
           2  DSL NOISE MARGIN                 60                    60        0
               PROFILE 2
  ------------------------------------------------------------------------------
  Total: 2

To query the detailed information about xDSL SNR margin profile 2, do as follows:

huawei#display xdsl noise-margin-profile                                
{ <cr>|profile-index<U><1,4294967294> }:2                                            
                                                                                
  Command:                                                                      
          display xdsl noise-margin-profile 2                                   
  ------------------------------------------------------------------------------
  Profile index               : 2
  Description                 : XDSL NOISE MARGIN PROFILE 2
  Target SNR margin downstream(0.1dB)                  : 100
  Minimum SNR margin downstream(0.1dB)                 : 10
  Maximum SNR margin downstream(0.1dB)                 : 200
  Target SNR margin upstream(0.1dB)                    : 20
  Minimum SNR margin upstream(0.1dB)                   : 10
  Maximum SNR margin upstream(0.1dB)                   : 100
  Transmitter referred virtual noise downstream        : Enable
  Transmitter referred virtual noise upstream          : Enable
  Form of transmit rate adaptation downstream          : AdaptAtStartup
  Form of transmit rate adaptation upstream            : AdaptAtStartup
  SNR margin for rate upshift downstream(0.1dB)        : 150
  Minimum upshift time downstream(second)              : 3600
  SNR margin for rate downshift downstream(0.1dB)      : 10
  Minimum downshift time downstream(second)            : 3600
  SNR margin for rate upshift upstream(0.1dB)          : 100
  Minimum upshift time upstream(second)                : 3600
  SNR margin for rate downshift upstream(0.1dB)        : 10
  Minimum downshift time upstream(second)              : 10
  ------------------------------------------------------------------------------

System Response

  • The system displays the queried result when the command runs successfully.

Precaution of the NMS Failing to Synchronize ONUs

Keywords:

ONU version information, FTP, synchronization failure, MA5680T&MA5683T, OLT

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 MA5600T V800R011 earlier than V800R011C00SPC107 or MA5600T 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.

Incorrect Configuration of the ZL80018 Chip on OptiX OSN 1800

Keywords: TNF1LDX, TNF2LSX, TNF2ELOM, OptiX OSN 1800

Summary:

On the TNF1LDX, TNF2LSX, and TNF2ELOM boards intended for the OptiX OSN 1800 of V100R003C01SPC300 and earlier versions, the ZL80018 chips in version H occasionally fail to be configured. As a result, bit errors are generated on the WDM side of the peer end or services are unavailable. This issue has been rectified in version V100E003C01SPC300.

 

[Problem Description]

Trigger condition:

This issue occasionally occurs when the TNF1LDX, TNF2LSX, or TNF2ELOM board intended for OptiX OSN 1800 is powered off or (cold) reset, or the services on any of the boards are changed.

Symptom:

After the TNF1LDX (03021ETT), TNF2LSX (03021FTM), or TNF2ELOM (03030MSG) board used during the network deployment or on the live network is powered off or (cold) reset, or the services on any of the boards are changed, the services will be unavailable or bit errors will be generated. The typical symptom is as follows: An ODU0_LOFLOM, ODU1_LOFLOM, ODU2_PM_BDI, or BEFFEC_EXC alarm is reported on the WDM side of the peer board. An ODU0_PM_BDI, ODUFLEX_PM_BDI, or ODU1_PM_BDI alarm is reported on the WDM side of the local board.

Identification method:

You can determine that this issue occurs when the following conditions are met:

  1. After the TNF1LDX, TNF2LSX, or TNF2ELOM board used is powered off or (cold) reset, or the services on any of the boards are changed, the services are unavailable or bit errors are generated. To be specific, an ODU0_LOFLOM, ODU1_LOFLOM, ODU2_PM_BDI, or BEFFEC_EXC alarm is reported on the WDM side of the peer board, and an ODU0_PM_BDI, ODUFLEX_PM_BDI, or ODU1_PM_BDI alarm is reported on the WDM side of the local board.
  2. The NE software version satisfies either of the following requirements:

The NE software version is earlier than V100R003C01SPC300 and is not upgraded after a fault occurs.

The NE software version is earlier than V100R003C01SPC300 when a fault occurs and then is upgraded to V100R003C01SPC300 or later, but no cold reset is performed on the TNF1LDX, TNF2LSX, or TNF2ELOM board.

  1. The ZL80018 chip in version H is used and the boards satisfy the following requirements:

TNF1LDX: manufactured after December 14, 2012 and board barcode being numbered after 021ETT10CB000492

TNF2LSX: manufactured after December 14, 2012 and board barcode being numbered after 021FTM10CC000157

TNF2ELOM: manufactured after December 28, 2012 and board barcode being numbered after 030MSG10CC000745

 

[Root Cause]

The ZL80018 chip has a defect. It may fail to be configured, which has a higher probability for ZL80018 chips in version H. The TNF1LDX, TNF2LSX, and TNF2ELOM boards intended for OptiX OSN 1800 do not strictly comply with the latest erata code standards of the ZL80018 chip and cannot completely prevent the defect. As a result, the ZL80018 chip in version H used on the TNF1LDX, TNF2LSX, and TNF2ELOM boards intended for OptiX OSN 1800 earlier than V100R003C01SPC300 occasionally fails to be configured. Consequently, the clock performance is affected and the services on the boards are unavailable or bit errors are generated.

 

[Impact and Risk]

For OptiX OSN 1800 earlier than V100R003C01SPC300, when the TNF1LDX, TNF2LSX, or TNF2ELOM board using the ZL80018 chip in version H is powered off, (cold) reset, or services are changed, bit errors will be occasionally generated or services will be occasionally unavailable. This issue, however, will not occur during the normal running of the boards.

 

[Measures and Solutions]

Recovery measures:

Perform a cold reset on the involved boards (sometimes cold resets may need to be performed several times).

Workarounds:

None

Preventive measures:

This issue has been rectified since OptiX OSN 1800 V100R003C01SPC300. Therefore, upgrade the NE software version to OptiX OSN 1800 V100R003C01SPC300 or later. When this issue occurs, upgrade the NE software and perform a cold reset on the TNF1LDX, TNF2LSX, or TNF2ELOM board.

ACL is forbidden to be modified in S5700

ACL is forbidden to be modified in S5700

If the ACl is applied to a vlan and I want to modify the ACL, I get this error:
Error: The ACL is contained by some application(s) and forbidden to be modified.

I do not want to remove the ACL from vlan, Change it and then reapply it back. It is rather inconvenient.
What should I do?

Alarm Information

The ACL is contained by some application(s) and forbidden to be modified.

Handling Process

You have 2 Solution:

1- You can use “Traffic policy” under vlan, then, You can modify ACL dynamically.
2- You can upgrade software version to V200R005 (or higher) version, You can modify ACL dynamically when using “Traffic-xxx” Commands

Example:
***********
[huawei-GigabitEthernet0/0/1]traffic-mirror inbound acl
[huawei-GigabitEthernet0/0/1]traffic-redirect inbound acl
[huawei-GigabitEthernet0/0/1]traffic-remark inbound acl
[huawei-GigabitEthernet0/0/1]traffic-secure inbound acl

 

How to Start the T2000 Client?

To manage networks through the T2000 client graphical user interface, you need to use the T2000 client to log in to the T2000 server.

Prerequisite
The T2000 server must be started correctly.

Procedure
Step 1 On the computer of the T2000 client, double-click the T2000 Client icon on the desktop.

Step 2 Enter User Name and Password, and select Server in the Login dialog box.
For example, enter admin in the User Name field and T2000 in the Password field.
NOTE
By default, the initial user name is admin, and the password is T2000. To protect the T2000 from illegal login, you need to instantly change this password and keep the new one. The administrator needs to create new T2000 users and assign them to certain authority groups.

Step 3 Optional: Set the server parameters.
1. Click to display the Setting dialog box.
2. Click New to display Setting dialog box.
3. In the Setting dialog box, specify the IP Address, Server Name and Mode.
NOTE
Enter the IP address of the T2000 server. In the Mode field, Common and SSL are available. When it is set to SSL, the communication between the client and server is encrypted.
The mode of the client must be the same as that of the server. Otherwise, login fails. Choose System > Communication Security Setting from the sysmonitor client of the server, and you can view the communication mode of the server. The Port number does not need to be entered by the user. After the Mode is specified, the system selects a port number automatically.
4. Click OK to complete adding a server.
5. Click OK to complete the server settings.
Step 4 Select Server and click Login to display the Main Topology of the T2000.
—-End

OptiX OSN 6800 Intelligent Optical Transport Platform Commissioning Guide

 

Downgrade failed on S5700-28X-PWR-LI-AC running V200R002C00SPC100

Issue Description

Switch:
VRP (R) software, Version 5.120 (S5700 V200R002C00SPC100)
Copyright (C) 2000-2015 HUAWEI TECH CO., LTD
HUAWEI S5700-28X-PWR-LI-AC Routing Switch

downgrade to V200R001C00SPC300 failed.

Alarm Information

error that we have received when trying to set the new system software as startup was:

startup system-software s5700li-v200r001c00spc300.cc
Error: Upgrade basic-bootrom failed.Software does not match this device.
Error: Failed in upgrading bootrom, next step is copying file. Continue?[Y/N]:Y
Error: The file is not supported by the device.
Info: Failed in setting the software for booting system.

Handling Process

S5700-28X-PWR-LI-AC is new on the market and was designed to support new features available only on the newer versions. So actually the first system-software and only available for this model is V200R002C00SPC100 and V200R003C00SPC300.

Root Cause

none.

Suggestions

Upgrade to V00R003C00SPC300.

Update of V100R010C10SPC200 Compared with V100R010C00SPC200

Hardware Name Update Type Description
TN97MD2 New The TN97MD2 board is a multiplexer and demultiplexer board that supports extended C band. It can be used to multiplex the wavelengths of the new site and existing site during submarine expansion, construct the COTDR detection channel, or form a terrestrial regeneration site with OAs and provide the COTDR loopback channel.
TN97M48V New As a type of optical multiplexing unit, the M48V board multiplexes a maximum of 48 extended C channels of signals into one channel of signals that comply with ITU-T Recommendations, and adjusts the input optical power of each channel.
TN97D48 New As a type of optical demultiplexing unit, The D48 board implements the demultiplexing of one optical signal into a maximum of 48 ITU-T Recommendation-compliant WDM signals.
TN97FIU New As an optical multiplexing and demultiplexing unit, the TN97FIU board is used in the extended spans of the submarine system on land, and multiplexes the main channel (service channel) signal and the OSC signal onto a single communications channel. The TN97FIU board also performs the reverse process. In addition, the TN97FIU board supports high power input when works with the TN97HBA board.
TN97ITL New As a type of optical multiplexing and demultiplexing unit, the TN97ITL board implements multiplexing/demultiplexing between the extended C-band optical signals at a channel spacing of 100 GHz and the signals at a channel spacing of 50 GHz.
TN97TD20 New The TN97TD20 board applies to a SLTE site to broadcast a multi-wavelength signal that contains 20 coherent wavelength signals to 20 coherent line boards. Because coherent line boards support automatic wavelength selection, the coherent line boards automatically select the required signal from the multi-wavelength signal, offering colorless applications.
TN97TM20 New The TN97TM20 board is a multiplexer board and is intended for colorless applications. It is used to add 20 coherent optical signals over different wavelengths and multiplex these signals into one multi-wavelength signal. It supports C-band and extended band wavelengths and flexible grid wavelength signals.
TN97ASE New The TN97ASE board is optical amplifier board with amplified spontaneous emission. It applies to the submarine system to generate extended C-band dummy light. In addition, it supports pump redundancy protection function.
TN97OBU2 New The TN97OBU2 board is optical amplifier board. It applies to the submarine system to support optical power amplification of the extended C-band and pump redundancy protection function. It also supports the gain locking, power locking, and APC modes.
TN97OAU2 New The TN97OAU2 board is a gain-adjustable optical amplifier board. It applies to the submarine system to support optical power amplification of the extended C-band and pump redundancy protection. It supports the gain locking, power locking, and APC modes.
TN97RPC New The TN97RPC board is an OA board. It can produce multi-wavelength backward pump light with high power and achieve the distributed in-service amplification of signals within the entire bandwidth of the extended C-band while producing very little noise.
TN12RAU1 New Added the TN12RAU106E board.
TN12RAU2 New Added the TN12RAU201E board.
TNK3STG New Added the TNK3STG board.
TN13STG New Added the TN13STG board.
TN15TM20 New Added the TN15TM20 board which supports flexible grid wavelength signals.
TN11OLSP New s optical protection boards, It supports 1:1 optical transmission section (OTS) optical line protection.
TN11OLSPA/TN11OLSPB New TN11OLSPA and TN11OLSPB boards are optical protection boards and must be used in pairs. They support 1:1 OTS optical line protection. In addition, they can work together with the SFIU board on an optical regeneration site and support the IEEE 1588v2 application scenario.
TN51RPC New The TN51RPC board is an OA board. It can produce multi-wavelength forward pump light with high power and achieve the distributed in-service amplification of signals within the entire bandwidth of the C-band and extended C-band while producing very little noise.
TN51ROP New C-band and extended C-band Remote optical pump processing Board.
TN51HBA New Compared with the TN11HBA board, the TN51HBA board can amplifie the power of Extend C-band optical signals. The TN51HBA board occupies two slots and consumes less power.