Analysis of the POWER_FAIL Alarm on the OptiX OSN 6800 and Solution

The SCC board reports the POWER_FAIL alarm due to a battery failure.

Product

OptiX OSN 6800

OptiX OSN 3800

Fault Type

System and Communication Unit

POWER_FAIL

Symptom

During commissioning of the OptiX OSN 6800 in a pilot project, the SCC board reports the POWER_FAIL alarm.

Alarm Parameters (hex): 0x05 0xff 0xff 0xff 0xff

Cause Analysis

The OptiX OSN 6800 is new equipment and several OptiX OSN 6800 NEs have this alarm. It is suspected that the power module is faulty.

After cutting off the power of the OptiX OSN 6800 then power on, the equipment time and date information is lost and changes to the initial time and date, that is 1990-01-01 00:00:00. Then, the battery on the SCC may be faulty.

Procedure

1. Remove the SCC board and check the jumper that controls the battery. This jumper is found in an incorrect state.
2. Change the state of the jumper so that the battery works.
3. Insert the SCC. The POWER_FAIL alarm is cleared.
4. Reset the date and time.
5. Reset the equipment and the time and date information is not lost. The problem is solved.

Reference Information

The jumper is to be set before delivery, the setting on sit is not required to be fixed normally.

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

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, 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.

Reference Information

None.

More related:

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

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

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

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， 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.

Reference 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

Configuring Dual-homed Inter-Board Link Aggregation

In dual-homed inter-board link aggregation, primary and secondary upper-layer devices are configured. LAGs are configured on these two devices for interconnecting with the access device
(such as Huawei MA5683T). This type of link aggregation provides protection for upper-layer devices between LAGs. If the active LAG malfunctions, the bandwidth and priority of the active LAG are lower than those of the standby LAG, which triggers a protection switchover.

Service Requirements

The bandwidth between the access device uplink ports and the upper-layer switch(such as S5720-36C-PWR-EI-AC) is required to increase in load sharing mode. In addition, link protection is required. If one link becomes faulty, the upstream bandwidth is decreased, and the Internet access rate is reduced. However, the Internet access service must not be interrupted, and the access rate reduction slightly degrades user experience.
LAG protection must be implemented. If one LAG becomes faulty, services are not interrupted.

In upstream transmission(such as OSN3500) of inter-board link aggregation scenarios, the access device functions as the actor (indicating the party that is dominant in negotiation) to determine the primary and secondary roles of LAGs. To determine the primary device, the access device adheres to the following rules:

• The access device uses the received peer end's information carried in the LACP packet to determine the dual homing network. Then, the access device automatically calculates the number of LinkUp ports on the two upper-layer devices, and selects the device that has the greater number of LinkUp ports as the primary device. The other upper-layer device is the secondary device.
• If the two upper-layer devices provide the same number of LinkUp ports, the rules vary depending on the LACP priority preemption mode configured on the access device.
  • If LACP works in priority preemption mode, the access device preferentially selects the peer end device connected to the local port with the higher priority as the primary device.
  • If LACP works in non-priority preemption mode, the access device preferentially selects the peer end device connected to the port that is currently in forwarding state as the primary device.
• If the link forwarding traffic is interrupted, the access device uses the preceding rules to select the primary device.

Networking

dual-homed inter-board link aggregation: Two GIU boards on the access device are used for upstream transmission, and the access device is interconnected with two devices. One LAG is configured for a GIU board of the access device and an interconnected device.

Figure 1 Networking of dual-homed inter-board link aggregation

Prerequisite

• Interconnected devices, hardware, and ports support LAGs.
• The two aggregated ports do not have a static MAC address. To check whether an aggregated port has a static MAC address, run the display mac-address command.

Data Plan

Table 1 lists data plan for configuring dual-homed inter-board link aggregation.

Table 1 Data plan for configuring dual-homed inter-board link aggregation

Item	Data	Remarks
LAG member port	0/19/0 (master port) 0/19/1 0/20/0 0/20/1	The configuration of the slave port must be the same as that of the master device. Alternatively, the slave port is not configured. It is recommended that you do not configure the slave port to prevent a service failure due to data inconsistency with the master port.
Aggregation type	LACP aggregation	When the access device connects to a device supporting LACP, the LACP aggregation mode is recommended. When the access device connects to a device not supporting LACP, only manual aggregation can be configured.
Load sharing type	Load sharing	A LAG works in load sharing mode by default.

Procedure

1. (Mandatory) Create a LAG and select an aggregation type. Run the link-aggregation command to add multiple uplink Ethernet ports to the same LAG to protect ports and share load between the ports. The port with the smallest port ID is the master port.
   
2. (Optional) Add a LAG member port. Perform this step when the LAG bandwidth or link reliability is required to improve. To do so, run the link-aggregation add-member command to add an Ethernet port to a LAG.
   
   NOTE:

   When adding a port to or deleting a port from a LAG, if this port has connected to the peer device, run the shutdown(Ethernet) command to deactivate this port or disconnect the optical fiber from this port to prevent a link loop.
   
   
3. (Optional) Select a load bearing type. This step is required only when the LAG works in LACP aggregation mode.
   Configuring the maximum active links in a LAG implements traffic allocation in load non-sharing mode. For example, M+N links have been configured in a LAG. Then, run the link-aggregation max-link-number command to specify N active links. The remaining M links are standby ones. If an active link is interrupted, a standby link automatically changes to the active one.
   
   
4. (Optional) Set the system priority and port priority. This step is required only when the LAG works in LACP aggregation mode.
   
   • LACP system priority: If the access device is dual homed to two convergence devices, the access device determines the primary and standby LAGs. Run the lacp priority system command to set the LACP system priority of the access device to be higher than that of the peer device.
   • LACP port priority: LACP port priority must be used with the maximum number of links. If a port is required preferentially for carrying services, set its priority higher. Run the lacp priority port command to change the link priority so that the standby link and the active link can be switched over.
   
   
5. (Optional) Select a link revertive mode. This step is required only when the LAG works in LACP aggregation mode. Run the lacp preempt command to set whether traffic is switched back to the original link when the original link recovers.
   
6. (Optional) Query LAG information. Run the display link-aggregation command to query the LAG information, including the master port, number of links, aggregation type (manual or LACP aggregation), and maximum number of links.
   

Result

The bandwidth between the access device uplink ports and the upper-layer switch is increased in load sharing mode. In addition, link protection is implemented. If one LAG becomes faulty, services are not interrupted. If this happens, the access device automatically switches services to the LAG providing a higher bandwidth.

Example

The following configurations are used as an example to configure dual-homed inter-board link aggregation:

• The access device transmits data upstream using two GIU boards.
• Uplink ports 0/19/0, 0/20/0, 0/19/1, and 0/20/1 on the active and standby GIU boards are added to an inter-board LAG.
• Packets are forwarded to these ports based on source and destination MAC addresses.
• The LAG works in LACP aggregation mode.

huawei(config)#link-aggregation 0/19 0-1 0/20 0-1 egress-ingress workmode lacp-static
huawei(config)#display link-aggregation all
  -------------------------------------------------------------------------
  Master port  Link aggregation mode  Port NUM  Work mode  Max link number
  -------------------------------------------------------------------------
  0/19/0       egress-ingress                4  lacp-static              -
  -------------------------------------------------------------------------     
  Total: 1 link aggregation(s)                                                  

Configuration File

link-aggregation 0/19 0-1 0/20 0-1 egress-ingress workmode lacp-static

MORE RELATED:

Cautions for Unavailable Services After N2EFT8 & N2EFT8A board is Connected to Third-Party 

Alarm of Optical Module’s on PEX2&PEX1 and EX2 Boards on H-MSTP Equipment

Have You Ever Met Service Interruption of ET1 Board on Metro 1000V3 upon Power-off ResetEquipment

Configuring Single-homed Inter-Board Link Aggregation

In inter-board link aggregation, one or more ports on two boards are added to a LAG. Inter-board link aggregation provides protection for boards configured with aggregated links. In single homing, only one upstream device is available, without differentiating between primary and slave devices.

Service Requirements

The bandwidth between the access device(such as Huawei MA5683T) uplink ports and the upper-layer switch (such as S5720-36C-PWR-EI-AC)is required to increase in load sharing mode. In addition, link protection is required. If one link becomes faulty, the upstream bandwidth is decreased, and the Internet access rate is reduced. However, the Internet access service must not be interrupted, and the access rate reduction slightly degrades user experience.
Board-level protection must be implemented in the LAG. If one board becomes faulty, services are not interrupted.

Networking

single-homed inter-board link aggregation: Two GIU boards on the access device are used for upstream transmission(such as Huawei OSN3500), and the access device is interconnected with another device. One LAG is configured on the two GIU boards of the access device, and the other LAG is configured on two boards of the interconnected device.

Figure 1 Networking of single-homed inter-board link aggregation

Prerequisite

• Interconnected devices, hardware, and ports support LAGs.
• The two aggregated ports do not have a static MAC address. To check whether an aggregated port has a static MAC address, run the display mac-address command.

Data Plan

Table 1 lists data plan for configuring single-homed inter-board link aggregation.

Table 1 Data plan for configuring single-homed inter-board link aggregation

Item	Data	Remarks
LAG member port	0/19/0 (master port) 0/20/0	The configuration of the slave port must be the same as that of the master device. Alternatively, the slave port is not configured. It is recommended that you do not configure the slave port to prevent a service failure due to data inconsistency with the master port.
Aggregation type	LACP aggregation	When the access device connects to a device supporting LACP, the LACP aggregation mode is recommended. When the access device connects to a device not supporting LACP, only manual aggregation can be configured.
Load sharing type	Load sharing	A LAG works in load sharing mode by default.

Procedure

1. (Mandatory) Create a LAG and select an aggregation type. Run the link-aggregation command to add multiple uplink Ethernet ports to the same LAG to protect ports and share load between the ports. The port with the smallest port ID is the master port.
   
2. (Optional) Add a LAG member port. Perform this step when the LAG bandwidth or link reliability is required to improve. To do so, run the link-aggregation add-member command to add an Ethernet port to a LAG.
   
   NOTE:

   When adding a port to or deleting a port from a LAG, if this port has connected to the peer device, run the shutdown(Ethernet) command to deactivate this port or disconnect the optical fiber from this port to prevent a link loop.
   
   
3. (Optional) Select a load bearing type. This step is required only when the LAG works in LACP aggregation mode.
   Configuring the maximum active links in a LAG implements traffic allocation in load non-sharing mode. For example, M+N links have been configured in a LAG. Then, run the link-aggregation max-link-number command to specify N active links. The remaining M links are standby ones. If an active link is interrupted, a standby link automatically changes to the active one.
   
   
4. (Optional) Set the system priority and port priority. This step is required only when the LAG works in LACP aggregation mode.
   
   • LACP system priority: Run the lacp priority system command to set the LACP system priority of the access device.
   • LACP port priority: LACP port priority must be used with the maximum number of links. If a port is required preferentially for carrying services, set its priority higher. Run the lacp priority port command to change the link priority so that the standby link and the active link can be switched over.
   
   
5. (Optional) Select a link revertive mode. This step is required only when the LAG works in LACP aggregation mode. Run the lacp preempt command to set whether traffic is switched back to the original link when the original link recovers.
   
6. (Optional) Query LAG information. Run the display link-aggregation command to query the LAG information, including the master port, number of links, aggregation type (manual or LACP aggregation), and maximum number of links.
   

Result

The bandwidth between the access device uplink ports and the upper-layer switch is increased in load sharing mode. In addition, link protection is implemented. If one board in the LAG becomes faulty, services are not interrupted.

Example

The following configurations are used as an example to configure single-homed inter-board link aggregation:

• The access device transmits data upstream using two GIU boards.
• Uplink ports 0/19/0 and 0/20/0 on the active and standby GIU boards, respectively, are added to an inter-board LAG.
• Packets are forwarded to these ports based on source and destination MAC addresses.
• The LAG works in LACP aggregation mode.

huawei(config)#link-aggregation 0/19 0 0/20 0 egress-ingress workmode lacp-static
huawei(config)#display link-aggregation all
  -------------------------------------------------------------------------
  Master port  Link aggregation mode  Port NUM  Work mode  Max link number 
  -------------------------------------------------------------------------
  0/19/0       egress-ingress                4  lacp-static              -
  -------------------------------------------------------------------------
  Total: 1 link aggregation(s)

Configuration File

link-aggregation 0/19 0 0/20 0 egress-ingress workmode lacp-static

More related:

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


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



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

Configuring Single-homed Inter-Board Link Aggregation

In inter-board link aggregation, one or more ports on two boards are added to a LAG. Inter-board link aggregation provides protection for boards configured with aggregated links. In single homing, only one upstream device is available, without differentiating between primary and slave devices.

Service Requirements

The bandwidth between the access device uplink ports and the upper-layer switch (such as
LS-S5700-24TP-PWR-SI-AC)is required to increase in load sharing mode. In addition, link protection is required. If one link becomes faulty, the upstream bandwidth is decreased, and the Internet access rate is reduced. However, the Internet access service must not be interrupted, and the access rate reduction slightly degrades user experience.
Board-level protection must be implemented in the LAG. If one board becomes faulty, services are not interrupted.

Networking

Two GIU boards on the access device are used for upstream transmission, and the access device is interconnected with another device. One LAG is configured on the two GIU boards of the access device, and the other LAG is configured on two boards of the interconnected device.

Prerequisite

• Interconnected devices, hardware, and ports support LAGs.
• The two aggregated ports do not have a static MAC address. To check whether an aggregated port has a static MAC address, run the display mac-address command.

Data Plan

Table 1 lists data plan for configuring single-homed inter-board link aggregation.

Table 1 Data plan for configuring single-homed inter-board link aggregation

Item	Data	Remarks
LAG member port	0/19/0 (master port) 0/20/0	The configuration of the slave port must be the same as that of the master device. Alternatively, the slave port is not configured. It is recommended that you do not configure the slave port to prevent a service failure due to data inconsistency with the master port.
Aggregation type	LACP aggregation	When the access device connects to a device supporting LACP, the LACP aggregation mode is recommended. When the access device connects to a device not supporting LACP, only manual aggregation can be configured.
Load sharing type	Load sharing	A LAG works in load sharing mode by default.

Procedure

1. (Mandatory) Create a LAG and select an aggregation type. Run the link-aggregation command to add multiple uplink Ethernet ports to the same LAG to protect ports and share load between the ports. The port with the smallest port ID is the master port.
   
2. (Optional) Add a LAG member port. Perform this step when the LAG bandwidth or link reliability is required to improve. To do so, run the link-aggregation add-member command to add an Ethernet port to a LAG.
   
   NOTE:

   When adding a port to or deleting a port from a LAG, if this port has connected to the peer device, run the shutdown(Ethernet) command to deactivate this port or disconnect the optical fiber from this port to prevent a link loop.
   
   
3. (Optional) Select a load bearing type. This step is required only when the LAG works in LACP aggregation mode.
   Configuring the maximum active links in a LAG implements traffic allocation in load non-sharing mode. For example, M+N links have been configured in a LAG. Then, run the link-aggregation max-link-number command to specify N active links. The remaining M links are standby ones. If an active link is interrupted, a standby link automatically changes to the active one.
   
   
4. (Optional) Set the system priority and port priority. This step is required only when the LAG works in LACP aggregation mode.
   
   • LACP system priority: Run the lacp priority system command to set the LACP system priority of the access device.
   • LACP port priority: LACP port priority must be used with the maximum number of links. If a port is required preferentially for carrying services, set its priority higher. Run the lacp priority port command to change the link priority so that the standby link and the active link can be switched over.
   
   
5. (Optional) Select a link revertive mode. This step is required only when the LAG works in LACP aggregation mode. Run the lacp preempt command to set whether traffic is switched back to the original link when the original link recovers.
   
6. (Optional) Query LAG information. Run the display link-aggregation command to query the LAG information, including the master port, number of links, aggregation type (manual or LACP aggregation), and maximum number of links.
   

Result

The bandwidth between the access device uplink ports and the upper-layer switch is increased in load sharing mode. In addition, link protection is implemented. If one board in the LAG becomes faulty, services are not interrupted.

Example

The following configurations are used as an example to configure single-homed inter-board link aggregation:

• The access device transmits data upstream using two GIU boards.
• Uplink ports 0/19/0 and 0/20/0 on the active and standby GIU boards, respectively, are added to an inter-board LAG.
• Packets are forwarded to these ports based on source and destination MAC addresses.
• The LAG works in LACP aggregation mode.

huawei(config)#link-aggregation 0/19 0 0/20 0 egress-ingress workmode lacp-static
huawei(config)#display link-aggregation all
  -------------------------------------------------------------------------
  Master port  Link aggregation mode  Port NUM  Work mode  Max link number 
  -------------------------------------------------------------------------
  0/19/0       egress-ingress                4  lacp-static              -
  -------------------------------------------------------------------------
  Total: 1 link aggregation(s)

Configuration File

link-aggregation 0/19 0 0/20 0 egress-ingress workmode lacp-static

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

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:

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?

How to modify dba-profile?

Function

This command is used to modify a dynamic bandwidth assignment (DBA) profile. When the configuration of the DBA profile cannot meet the service requirements, run this command to modify the DBA profile.

Format

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

Parameters

Parameter	Description	Description
profile-id profile-id	Indicates the DBA profile ID. When you need to modify a DBA profile by specifying the profile ID, use this parameter.	Numeral type. Range: 0-512.
profile-name profile-name	Indicates the DBA profile name. When you need to modify a DBA profile by specifying the profile name, use this parameter.	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.

Example

To modify the fixed bandwidth of DBA profile 2 to 2 Mbit/s and the maximum bandwidth to 10 Mbit/s, do as follows:

huawei(config)#dba-profile modify                                               
{ profile-id<K>|profile-name<K> }:profile-id 
{ profile-id<U><0,512> }:2                                  
                                                                                
  Command:                                                                      
          dba-profile modify profile-id 2                                       
>  Start modifying a DBA-profile:                                               
>  The type of the DBA-profile (1~5) [3]: 5                                     
>  The fixed bandwidth of the DBA-profile(128~10000000kbps) [0] : 2048        
>  The assured bandwidth of the DBA-profile(128~10000000kbps) [15360] : 2048         
>  The maximum bandwidth of the DBA-profile(128~10000000kbps) [30720] : 10240  
>  The additional bandwidth of the DBA-profile(0:non-assure  1: best-effort) [1]
 : 1  
>  The priority of the DBA-profile(0~3) [1] :2 
>  The weight of the DBA-profile(1~10000) [100] :200

To modify the fixed bandwidth of DBA profile 12 to 2 Mbit/s and disable the fixed delay, do as follows:

huawei(config)#dba-profile modify                                               
{ profile-id<K>|profile-name<K> }:profile-id 
{ profile-id<U><0,512> }:12                                  
                                                                                
  Command:                                                                      
          dba-profile modify profile-id 12                                      
>  Start modifying a DBA-profile:                                               
>  The type of the DBA-profile (1~5) [1]: 1                                    
>  The fixed bandwidth of the DBA-profile(128~10000000kbps) [192] : 2048       
>  The bandwidth compensation of the DBA-profile(0: No 1: Yes) [0] : 0         
> The fix delay switch of the DBA-profile(0: No 1: Yes) [1]: 0                 

System Response

• The system does not display any message after the DBA profile is modified successfully.
• The following table describes the parameters in response to this command.

  Parameter	Description
  The type of the DBA-profile	Indicates the DBA profile type. There are five types of DBA profiles: 1: fixed bandwidth 2: assured bandwidth 3: assured bandwidth + maximum bandwidth 4: maximum bandwidth 5: fixed bandwidth + assured bandwidth + maximum bandwidth For details about the application scenarios of each type of profiles, see the "Description" of the dba-profile add command.
  The fixed bandwidth of the DBA-profile	Indicates the fixed bandwidth of the DBA profile. The fixed bandwidth is reserved for a specified ONU or certain services of the ONU. It cannot be used for other ONUs even when the upstream service stream is not transmitted on the ONU. This type of bandwidth is mainly used for services, such as TDM and VoIP, that have a high QoS requirement. When the DBA profile is of type1 and type5, you can modify the fixed bandwidth.
  The bandwidth compensation of the DBA-profile	Indicates the bandwidth compensation of the DBA profile. The bandwidth compensation refers to that the bandwidth is accelerated during the transmission when the actual bandwidth cannot meet requirements. This parameter can be modified only when the DBA profile is in TYPE1.
  The fix delay switch of the DBA-profile	Indicates the fixed delay function of the DBA profile. It can ensure the minimum jitter of the fixed bandwidth service. After the fixed delay function is enabled, more bandwidth resources will be occupied. This parameter can be modified only when the DBA profile is in TYPE1.
  The assured bandwidth of the DBA-profile	Indicates the assured bandwidth of the DBA profile. The assured bandwidth is the available bandwidth of an ONU when the ONU requires the bandwidth. When the actual service stream does not reach the assured bandwidth, the DBA mechanism of the The device is used to allocate the remaining bandwidth to services of other ONUs. When the DBA profile is of type2, type3 and type5, you can modify the assured bandwidth. Because of the DBA mechanism that allocates the remaining bandwidth to services of other ONUs, the assured bandwidth has a poorer real-time performance than fixed bandwidth does.
  The maximum bandwidth of the DBA-profile	Indicates the maximum bandwidth of the DBA profile. This type of bandwidth is the maximum bandwidth that can be used by an ONU to meet the ONU bandwidth requirement to the greatest extent. It is used for services such as IPTV and high-speed Internet access service. When the DBA profile is of type3, type4 and type5, you can modify the maximum bandwidth.
  The additional bandwidth of the DBA-profile	Indicates the additional bandwidth type of the DBA profile. Options are as follows: 0: non-assure 1: best-effort 2: both 3: default In privilege mode: non-assure and best-effort In diagnosis mode: non-assure, best-effort, both, and default When the additional bandwidth type is both or default, they are displayed as best-effort in privilege mode. This parameter can be modified only when the DBA profile is in TYPE5.
  The priority of the DBA-profile	Indicates the priority of the DBA profile. This parameter can be modified only when the DBA profile is in TYPE4 or when the DBA profile is in TYPE5 and the additional bandwidth type is not non-assure.
  The weight of the DBA-profile	Indicates the weight of the DBA profile. This parameter can be modified only when the DBA profile is in TYPE4 or when the DBA profile is in TYPE5 and the additional bandwidth type is not non-assure.

• 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:

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

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