Thursday, May 26, 2016

How to delete dba-profile

Function

This command is used to delete a dynamic bandwidth assignment (DBA) profile. When you do not need to use a DBA profile, run this command to delete the profile to facilitate the DBA profile management.

Format

dba-profile delete { profile-id profile-id | profile-name profile-name }

Parameters

Parameter Description Value
profile-id profile-id Indicates the DBA profile ID. When you need to specify the DBA profile by profile ID, use this parameter. Numeral type. Range: 10-512.
profile-name profile-name Indicates the DBA profile name. When you need to delete a DBA profile by specifying the profile name, use this parameter. If the parameter is specified as the name (dba-profile_x, x ranges from 0 to 9) of any one of the default ten DBA profiles (profile 0 to profile 9), the system does not delete the DBA profile. Character string type, a string of 1-33 characters.The characters must be visible and cannot contain a question mark (?). A double quotation mark (") except the outer-layer double quotation mark (") cannot be followed by a space. If the start or end character is a double quotation mark (), the corresponding end or start character must also be a double quotation mark (").

Modes

Global config mode

Level

Operator level

Usage Guidelines

  • By default, the system has ten DBA profiles numbering 0-9. The default DBA profiles can be queried or modified, but cannot be deleted.
  • The DBA profile that is bound to a GPON port cannot be deleted. If you need to delete a DBA profile that is bound to a GPON port, run the undo tcont bind-profile (In the distributing mode) or undo tcont (In the profile mode) command to unbind them first.

Example

To delete DBA profile 20, do as follows:
huawei(config)#dba-profile delete                                             
{ profile-id<K>|profile-name<K> }:profile-id                                    
{ profile-id<U><10,512> }:20                                                   
                                                                                
  Command:                                                                      
          dba-profile delete profile-id 20                                   

System Response

  • The system does not display any message after a DBA profile is deleted 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

Intermittent BEFFEC_EXC Alarm at IN/OUT optical interfaces on LWF board

The intermittent BEFFEC_EXC alarm is reported at IN/OUT optical interfaces on the LWF board housed in slot 10 of one surack NE.

Product

OptiX BWS 1600G, WDM,OSN 6800,OSN 8800

Fault Type

Optical Transponder Unit
BEFFEC_EXC

Symptom

The intermittent BEFFEC_EXC alarms are reported at the IN/OUT optical interfaces on the LWF board housed in slot 10 of one surack NE.
Initial operations:
  • Check connection.
  • Replace MR2 board in slot 8, which is connected with the IN optical interface of LWF board.
  • Still alarm at NMS.
Expected operations from vendor:
  • Clear the Problem
  • Provide User Guide (faulty description and problem handling)
  • Provide Maintenance Manual Books

Cause Analysis

The LWF board has the FEC function of correcting bit errors generated in the transmission over DWDM equipment. If the number of bit errors is beyond FEC correction ability, the number of uncorrectable bit errors and alarms is reported.
Then, initialize the current performance data and observe the NMS after a certain period. The NMS shows that the channels that report bit errors and number of bit errors are not stable.
If bit errors occur in one direction, it indicates that the fault is related to unidirectional optical fibers or boards. In this case, only the local station has bit errors. This means that the fault happens only in one direction.

Procedure

  1. Query performance events
  2. After 15m performance, bit errors occur in local station for the signals that are received from the opposite station and pass through 5 OLA stations. The channels that report bit errors and number of bit errors are not stable.
  3. No bit error occurs on the signals sent from the opposite station to the local station.
  4. Conclusion: Bit errors occur in one direction.
  5. Check optical power.
    1. Check the optical power of the amplifier at each station on the NMS. The optical power is identical with the value specified during engineering commissioning.
    2. Check optical power of the LWF at the local station on the NMS. The optical power is identical with the value specified during engineering commissioning.
  6. Adjust optical power:
    1. Adjust the optical power. With OSNR guaranteed, increase the input optical power of the optical fiber with bit errors. Observe the variation of the number of bit errors on the NMS. It shows the number of bit errors increases with the optical power. Reduce the input optical power of the fiber. It shows that the number of bit errors decreases with the optical power.
  7. Check the transmit power of the LWF board in slot 10 in the local station, which the transmission direction is from the opposite station to the local station. Trace step by step each site the OAU receiving power and transmit go to the local station also power gain. Make sure the power receive and power transmit adjust equally or difference is not significant.
  8. The launched optical power of the upstream station is excessively high about +15 dBm and the OAU gain +28 dB.
  9. The bit errors are caused by the non-linearity of optical fiber. Reduce the input optical power in the local station and bit error problem is solved.

The MCA Board Reports an Execution Failure

The MCA board reports an execution failure if the wavelength is not set to the monitor status.

Product

OptiX BWS 1600G, WDM, OSN 6800, OSN 8800

Fault Type

Spectrum Analyzer Unit

Symptom

To analyze the OSNR, a user sets the MCA board but mistakenly sets a wrong wavelength to the monitor status. As this wavelength is received from the opposite end, wavelength 192.3 nm of port 1 need be set to the monitor status. Instead, the user mistakenly sets wavelength 192.3 nm of port 2 of the MAC card to the monitor status. During the analysis on the laser spectrum, the MCA board prompts execution failure.

Cause Analysis

A wrong port is selected for monitoring.

Procedure

  1. Set the right port and wavelength received from the opposite end to the monitor status.
  2. The problem is solved.

Wednesday, May 25, 2016

Failing to Add IMA Boards into the DPS Protection Group

IMA boards fail to be added into the DPS protection group, hence failing to realize the DPS protection.

Product

Fault Type

Configuration_Problem

Symptom

Boards fail to be added into the DPS protection group.
The configuration of the DPS protection fails to be performed. The boards fail to be added into the DPS protection group.

Cause Analysis

IMA boards that are added into the DPS protection group must be inserted in the paired slots.

Procedure

  1. Make sure that the IMA boards that are configured with DPS protection are set to the paired slots.

Failing to Create ATM Services

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

Product

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

  1. Add the two connections into the protection group.

Mismatching Between MA Groups and Associated VCTRUNKs, Hence Causing the Binding Failure

IMA groups fail to be bound with associated VCTRUNKs. You need to configure IMA groups to match with associated VCTRUNKs.

Product

Fault Type

Configuration_Problem

Symptom

The principle of binding VCTRUNKs is met, but VCTRUNKS fail to be bound.

Cause Analysis

Mutual check relation exists between IMA groups and associated VCTRUNKs.

Procedure

  1. If IMA groups are symmetrically configured, make sure that the mapping VCTRUNKs are symmetrical.
  2. If VCTRUNKs are nonsymmetrical, make sure that the mapping IMA groups are nonsymmetrical.

Tuesday, May 24, 2016

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

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.