Showing posts with label OSN6800.OSN8800. Show all posts
Showing posts with label OSN6800.OSN8800. Show all posts

Wednesday, July 13, 2016

The Maximum Optical Power that an LSH/APC and an FC/UPC Connector can Withstand is 33 dBm and 25 dBm Respectively

The maximum optical power that an LSH/APC and an FC/UPC connector can withstand is 33 dBm and 25 dBm respectively.

Product


Fault Type

Others

Symptom

Among the WDM products, the Raman amplifier outputs high optical power. Thus an LSH/APC connector is recommended for a Raman amplifier. In addition, adopt fiber splicing, whenever feasible, on the ODF to prevent the interface section from being burned out by laser radiation. When interface section is burned out, reflected laser radiation may burn the amplifier.
Therefore, pay special attention to the range of optical power that various connectors can withstand.

Cause Analysis

  • The fiber patch cord with an LSH/APC connector can withstand optical power as high as 2000 mw, that is, 33 dBm.
  • The fiber patch cord with an FC/UPC connector can withstand optical power as high as 300 mw, that is, 25 dBm.

Procedure

  1. None.

Result

The problem is resolved.

Reference Information

None.

How to Use the LDMD Board to Configure Intra-Board 1+1 Protection Fails?

Posted by at No comments:
Labels: ,

Wednesday, July 6, 2016

How Signals Are Selected When the DCP Board Is Used

This section describes how signals are selected when the DCP board is used.

Product

Fault Type

Optical Protection Unit

Symptom

None.

Cause Analysis

When the DCP board is not used for protection but physically connect to an OTU board through the RI11 and RI12 optical interfaces to receive the client-side signals on the OTU board, the difference between the receive optical power values at the two optical interfaces is small and the receive optical power values are in the normal range. In this case, you need to observe the following points.
  • When the DCP board is running:
    • Because protection is not configured, the DCP board does not perform protection switching regardless of the channel status. That is, the system receives signals from the RI11 or RI12 optical interface even when no signal is available at the RI11 or RI12 optical interface.
  • When the DCP board is powered off:
    • The system always receives signals from the RI12 optical interface no matter whether signals are available at the RI11 or RI12 optical interface.
When the DCP board is used for configuring Inter-subrack client 1+1 protection or Intra-subrack client 1+1 protection and connects to an OTU board through the RI11 and RI12 optical interfaces to receive the client-side signals on the OTU board, the difference between the receive optical power values at the two optical interfaces is small and the receive optical power values are in the normal range. In this case, you need to observe the following points.
  • When the DCP board is running:
    • With protection configured, the system selectively receives signals on the working channel by default, that is, the system receives signals from the RI11 optical interface.
    • When no signal is available at the RI11 optical interface, the system selectively receives signals from the RI12 optical interface (protection channel).
    • When no signal is available at the RI12 optical interface, the system selectively receives signals from the RI11 optical interface (working channel).
  • When the DCP board is powered off:
    • The system selectively receives signals from the RI12 optical interface no matter whether signals are available at the RI11 or RI12 optical interface.

Procedure

  1. None.

Result

The problem is resolved.

Reference Information

None.

How to Use the Ethernet Test Frames on the OptiX OSN 6800?

Posted by at No comments:
Labels:

40G Wavelengths Are Unavailable Due to Inappropriate PMD

40G wavelengths are unavailable due to inappropriate polarization mode dispersion (PMD).

Product

OptiX BWS 1600G, OSN6800,OSN8800

Fault Type

PMD Abnormity

Symptom

An OptiX BWS 1600G network transmits both 10G and 40G wavelengths. The network diagram is shown in the following figure. 40G wavelengths are transmitted from station A to station C. They pass through station B. 10G wavelengths are added and dropped at station B. 40G wavelengths in two directions between station A and station C are unavailable. Performance of the 10G wavelengths between station A and station C and those between station A and station B fluctuates and the BER before correction exceeds two orders of magnitude; however, performance of the wavelengths between station B and station C is normal.

Cause Analysis

The possible causes of the performance fluctuation of the wavelengths are as follows:
  • The PMD is excessively high.
  • The optical amplifier boards work unstably.
The receive optical power on the OTU board at station C is stable. Therefore, the possibility that the optical amplifier boards work unstably is excluded. The measured PMD on the optical fibers during network design is low. In addition, the optical fibers are not rerouted. Therefore, it is preliminarily determined that the PMD is inappropriate.

Procedure

  1. Perform self-loops on the 40G OTU boards at stations A and C. The result is normal. This indicates that the 40G OTU boards work normally. The BERs of the 10G OTU boards fluctuate but there is only a slight change in the receive optical power. It is concluded that both the 10G and 40G OTU boards work normally.
  2. Check the total optical power and the optical power of each wavelength on each optical amplifier board along the links. The result is normal and the OSNR at the receive end reaches the specified value. This indicates that the links in the network are normal.
  3. Add a 40G board at station B. That is, add a 40G wavelength from station A to station B and from station B to station C each. The 40G wavelength from station A to station B is still unavailable but that from station B to station C is normal. It is concluded that the link from station A to station B is abnormal.
  4. Check the DCM modules at each station on the link from station A to station B. All DCM modules are properly connected. Therefore, it is determined that the PMD may be inappropriate.
  5. Measure the PMD span by span from station A to station B. It is found that the PMD of the optical fibers in the transmit and receive directions in a span is much higher than the design value. After the optical fibers in the span are replaced, the bidirectional 40G wavelengths between station A and station C are available.

Result

The problem is resolved.

Reference Information

None.

10G Card Issue in Quidway S5300

Posted by at No comments:
Labels:

Friday, June 24, 2016

The Service Alarm Indicator on an OTU Board Is Still Red After the HARD_ERR and HARD_BAD Alarms Are Suppressed

The service alarm indicator on an OTU board is still red after the HARD_ERR and HARD_BAD alarms are suppressed.

Product

Fault Type

Optical Transponder Unit
HARD_ERR
HARD_BAD

Symptom

An OTU board in the OptiX OSN 6800 on a network reports the HARD_ERR or HARD_BAD alarm. After the reported alarm is suppressed on the T2000, the service alarm indicator (SRV) on the board is still red. After the other alarms, if any, are suppressed on the T2000, the service alarm indicator on the board becomes green if the board does not report extra alarms.

Cause Analysis

The HARD_ERR and HARD_BAD alarms indicate hardware faults. When the board reports either alarm, it indicates that the hardware of the board is faulty. In this case, the board needs to be replaced. The designing helps the on-site engineers in replacing the board.

Procedure

  1. When the board reports the HARD_ERR or HARD_BAD alarm, it indicates that the hardware of the board is faulty. After these two alarms are suppressed on the T2000, the service alarm indicator on the board is still red.

Result

The OptiX OSN 6800 is designed in this manner to help the on-site engineers in replacing the board.

Reference Information

None.


How to do when Failing to Connect the 155 Mbit/s Optical Port on the Router of Company C

Posted by at No comments:
Labels:

Monday, June 6, 2016

The Optical Amplifier Reports the IN_PWR_HIGH Alarm Because of Optical Power Reflection

The optical amplifier reports the IN_PWR_HIGH alarm because of optical power reflection.

Product

Fault Type

Optical Amplifier Unit
IN_PWR_HIGH

Symptom

A metropolitan area ring network composed of the OptiX Metro 6040 bears single wavelengths. After the local commissioning of all sites, if you shut down all the optical amplifiers such as the OPU and OBU, the IN_PWR_HIGH alarm is reported. In this case, if you power on some of the amplifiers, the optical power of the network is restored.

Cause Analysis

This problem is caused by optical refection of the amplifiers.
The sites of the network are OADM sites. That is, services pass through between the MI and MO optical interfaces on the MR2 boards of all the sites. If the pass-through wavelengths of the network are not blocked, optical power reflection of the amplifiers occur.

Procedure

  1. To solve this problem, the pass-through wavelengths between the MI and MO optical interfaces on the MR2 boards of the network must be blocked. If a wavelength bearing no services passes through the MR2 boards of all the sites, this wavelength must also be blocked. You can also add a electrically variable optical attenuator to the link between the MI and MO optical interfaces of each site, and set the attenuation of each electrically variable optical attenuator to the maximum value until more pass-through wavelengths are loaded.
  2. This method is used to avoid repeated amplification of noise.

Reference Information

None.

More related:

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

Posted by at No comments:
Labels:

Wednesday, June 1, 2016

The WXCP Protection Configured for the LOG Board Is Invalid

The WXCP protection configured for the LOG board is invalid due to the configured attributes of the board.

Product

OptiX Metro 6040

Fault Category

Protection

Symptom

The LOG board is configured with the correct WXCP protection.
During a protection switching test, services are interrupted because there is no protection channel to which the services can be switched; however, no alarms are reported to the T2000.
Check whether the protection configuration is correct.
If you delete the protection group and then configure a new one, the fault persists.

Cause Analysis

The WXCP protection configured for the LOG board is invalid due to the configured attributes of the board.

Procedure

  1. Check the LOG board of the protection group.
    1. In the NE Explorer, select the LOG board to be checked.
    2. Select Configuration > WDM Interface from the Function Tree.
    3. Click the Advanced Attributes tab.
    4. Check whether the Max Packet Length is 9800.
  2. In this case, set the value of this parameter to 1511.
  3. Because the value of the parameter cannot be changed, set the LOG board.
  4. After the LOG board is reset, the value of the parameter is displayed as 9800.
  5. Test whether the fault is cleared. If the fault is cleared, the WXCP protection becomes valid.

Reference Information

None.

Incorrect Configuration of the ZL80018 Chip on OptiX OSN 1800

Posted by at No comments:
Labels: ,

The Input Optical Power of the OTU Board Is Abnormal Due to a Fault of the OPU Board

The input optical power of the OTU board is abnormal due to a fault of the OPU board.

Product

OptiX Metro 6040

Fault Category

Optical Power Abnormity
Optical Amplifier Unit

Symptom

In a single-channel ring network, the input optical power of an OTU board drops from 0 dBm to -7 dBm, -15 dBm, or -62 dBm.
This ring network bears the SDH service and is configured with the multiplex section protection (MSP).

Cause Analysis

The launched optical power of the opposite OTU is abnormal, or the line amplifier unit is faulty.

Procedure

  1. By checking whether there are abnormal alarms against the input optical power of the opposite OTU board, you can find that the parameters of the opposite OTU board are proved normal. This indicates that the launched optical power of the opposite OTU is normal.
  2. The input and output optical power of the opposite amplifier board are also checked normal.
  3. The input and output optical power of the local amplifier board, however, are checked abnormal. The input optical power of the local amplifier board is constant, whereas the output optical power of the local amplifier board is abnormal. This indicates that the local amplifier board is faulty.
  4. After you replace the local amplifier board, the system is restored.

Reference Information

  • When you find that the output optical power of the local OTU is abnormal, check the following items:
    • Input and output optical power of the opposite OTU board
    • Input and output optical power of the opposite amplifier board
    • Input and output optical power of the local amplifier board
  • If the anomaly of optical power occurs at random, perform the following steps:
    • Check whether any fiber jumper is loose or bent.
    • Clean the fibers and connectors.
    • Perform an optical time domain reflectometer (OTDR) test under the customer's consent.



Posted by at No comments:
Labels:

Friday, May 27, 2016

What is the simulate call start ont?

Function

The simulate call start ont command is used to start an ONT call emulation test. When the voice service on the live network for the ONT POTS user is faulty, use the call emulation test function. That is, use the test module of the ONT to emulate the user phone to perform a call test, help the user to check whether the call of the ONT is normal, help the user quickly locate the problem, and improve the efficiency of resolving the problem.

Format

simulate call start ont { caller frameid/slotid/portid ontid ont-potsid telno telno-value [ caller-stop-time caller-stop-time-value ] | callee frameid/slotid/portid ontid ont-potsid [ callee-stop-time callee-stop-time-value ] }

Parameters

Parameter Description Value
caller It specifies an ONT POTS port on which the caller emulation test is started. -
frameid/slotid/portid Indicates the subrack ID, slot ID and port ID. Enter a slash (/) between the subrack, slot and port IDs. Please see Differences Between Shelves.
ontid ID of the ONT to be queried. numeral type. Range: varies with the board type.
ont-potsid POTS port ID of the ONT to be queried. numeral type. Range: 1-255.
telno telno-value Indicates the phone number of callee in the caller emulation test. Character string type, a string of 1-16 characters.
caller-stop-time caller-stop-time-value Indicates the duration of the caller emulation test. The caller emulation test is automatically stopped once exceeding the duration. Numeral type. Range: 60-300s.
Unit: s.
Default: 180s.
callee It specifies an ONT POTS port on which the callee emulation test is started. -
callee-stop-time callee-stop-time-value Indicates the duration of the callee emulation test. The callee emulation test is automatically stopped once exceeding the duration. Numeral type. Range: 60-300s.
Unit: s.
Default: 180s.

Modes

Global config mode, WDM,OSN 6800,OSN 8800

Level

Operator level

Usage Guidelines

  • Running this command, run the config command to enter the global config mode.
  • The call emulation test can be a caller or callee emulation test.
    • Caller emulation test: The POTS port on the ONT serves as the calling party and the test engineer serves as the called party. This test requires manual operations.
    • Callee emulation test: The POTS port on the ONT serves as the called party and the test engineer serves as the calling party. This test requires manual operations.
  • The ONT call emulation test can be started only when the voice service of the POTS port on the ONT is normal.

Example

To start a callee emulation test on POTS port 1 of ONT 0 connected to port 0/3/0 and set the emulation test duration to 120s, do as follows:
huawei(config)#simulate call start ont
{ callee<K>|caller<K> }:callee                                   
{ frameid/slotid/portid<S><Length 5-15> }:0/3/0                                
{ ontid<U><0,255> }:0                                                           
{ ont-potsid<U><1,255> }:1                                                    
{ <cr>|callee-stop-time<K> }:callee-stop-time                                   
{ callee-stop-time-value<U><60,300> }:120

  Command:
          simulate call start ont callee 0/3/0 0 1 callee-stop-time 120
  ----------------------------------------------------------------
  F/S/P                : 0/3/0   
  ONT-ID               : 0
  ONT-POTSID           : 1    
  Test type            : callee emulational call test  
  Current status       : test end 
  Test Result          : success
  ---------------------------------------------------------------
To start a caller emulation test on POTS port 1 of ONT 0 connected to port 0/3/0, set the callee number to 88820003, and set the emulation test duration to 60s, do as follows:
huawei(config)#simulate call start ont
{ callee<K>|caller<K> }:caller                                   
{ frameid/slotid/portid<S><Length 5-15> }:0/3/0                                
{ ontid<U><0,255> }:0                                                           
{ ont-potsid<U><1,255> }:1                                                    
{ telno<K> }:telno                                                              
{ telno-value<S><Length 1-16> }:88820003                                        
{ <cr>|caller-stop-time<K> }:caller-stop-time                                   
{ caller-stop-time-value<U><60,300> }:60  

  Command:
          simulate call start ont caller 0/3/0 0 1 telno 88820003 caller-stop-ti
me 60
  ----------------------------------------------------------------
  F/S/P                : 0/3/0   
  ONT-ID               : 0
  ONT-POTSID           : 1    
  Test type            : caller emulational call test 
  Detected  number     : 88820003
  Reported number      : 88820003   
  Current status       : test end 
  Test Result          : success 
  ----------------------------------------------------------------

System Response

  • The system displays the test result after the emulation test that is successfully started is completed.
  • The following table describes the parameters in response to the simulate call start ont command.
    Parameter Description
    F/S/P Indicates the subrack ID, slot ID, and port ID of the PON port connected to the ONT.
    ONT-ID Indicates the ONT ID. It uniquely identifies an ONT of the PON port.
    ONT-POTSID Indicates the ID of a POTS port on the ONT.
    Test type Indicates the test type. Options: caller emulational call test and callee emulational call test.
    Current status
    Indicates the current status of the current call emulation test. Options:
    • Idle: The port is idle.
    • Off-hook: The caller or callee picks up the phone.
    • Dial tone: The dial tone is played for the caller (unique status in the caller emulation test).
    • Receiving: The caller is receiving digits (unique status in the caller emulation test).
    • Receive end: The caller completes receiving digits (unique status in the caller emulation test).
    • Ringing-back: The caller hears the ring back tone (unique status in the caller emulation test).
    • Ringing: The phone is ringing (unique status in the callee emulation test).
    • Connected: The call is ongoing.
    • Busy tone: The caller hears the busy tone (unique status in the caller emulation test).
    • On-hook: The caller or callee hangs up the phone.
    • Test end: The emulation test is ended.
    • Other: other unrecognized states.
  • For more information about the error message that the system displays against a command entered with incorrect syntax, see the "Syntax Check" in Parameter.

More related:
Posted by at No comments:
Labels: ,
Subscribe to: Posts (Atom)