Configuration Procedures

Six port working modes are available for the LOA board on the NMS. The port for the None (not for ports) mode does not require configurations. The other five modes require configurations.

General Configuration Procedure

In the flowchart, the mandatory actions are required for each port working mode and optional actions vary according to port working modes.
The optional actions must be configured in the following scenarios:

• Configure the port type: Port Type must be set to Client Side Color Optical Port when colored optical signals are received on the client side.
• Configure the timeslot configuration mode: ODU Timeslot Configuration Mode must be set for the line side of the LOA board.
  • When the signal flow is from ODU0 or ODUflex to ODU2, ODU Timeslot Configuration Mode must be set to Assign random.
  • When the signal flow is ODU0 -> ODU1 -> ODU2, ODU Timeslot Configuration Mode must be set to Assign consecutive.
  • When the signal flow is from Any or ODU1 to ODU2 directly, ODU Timeslot Configuration Mode can be set to Assign consecutive or Assign random. However, the value must be the same as the value that is set on the interconnected LOA or line board.
• Configure the service mode: When Service Type is set to OTU1, Service Mode must be set to OTN Mode first.
• Configure the ODUflex tolerance(ppm): when the port of the TOA board works in ODUflex mode, this parameter can be configured. This parameter is reserved and optional in configuring service types which are currently supported.
• Configure cross-connections from the client side to LP ports: This action is required only for the ODU0 non-convergence mode and ODU1 convergence mode.

The following describes the configuration procedure and involved parameter settings for each mode.

• Table 1 describes the configuration procedure for the ODU0 non-convergence mode.
• Table 2 describes the configuration procedure for the ODU1 non-convergence mode.
• Table 3 describes the configuration procedure for the ODU1_ODU0 mode.
• Table 4 describes the configuration procedure for the ODUflex non-convergence mode.
• Table 5 describes the configuration procedure for the ODU2 non-convergence mode.

Configuration Procedure for the ODU0 Non-Convergence Mode

Table 1 Configuration procedure

No.	Action	Description
1	Configure the port working mode.	Optional Parameter settings: The default value of Port Working Mode is ODU0 non-convergence mode (Any->ODU0[->ODU1]->ODU2->OTU2). If the default value is used, skip this step. Operation description: For details about the configuration procedure, see Configuring the Working Mode.
2	Configure the port type.	Optional Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port. Operation description: For details about the configuration procedure, see Modifying Port.
3	Configure the timeslot configuration mode.	Optional Parameter settings: The value of ODU Timeslot Configuration Mode varies according to the two signal flows in the ODU0 non-convergence mode. When the signal flow is Any->ODU0->ODU2->OTU2, set ODU Timeslot Configuration Mode to Assign random. When the signal flow is Any->ODU0->ODU1->ODU2->OTU2, set ODU Timeslot Configuration Mode to Assign consecutive. Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface from the Function Tree. Click By Function and choose ODU Timeslot Configuration Mode from the the dropdown list. Set ODU Timeslot Configuration Mode for the WDM side port.
4	Configure the service type.	Mandatory Parameter settings: The available values for Service Type are FE, GE(TTT-GMP), GE(GFP-T), STM-1/OC-3, STM-4/OC-12, FC100, ESCON, FICON, FDDI, SDI, and DVB-ASI. Operation description: For details about the configuration procedure, see Configuring the Service Type. NOTE: Two channels (channel 1 and channel 2) are available at each LP port. Set the service type for only one of the two channels. When the LOA board is interconnected with a TN52TOM board, the channel where you set the service type must be the same as the channel where the service type is set on the TN52TOM board. When the LOA board is interconnected with another board, set the service type for channel 1.
5	Configure cross-connections from the client side to LP ports on the LOA board.	Mandatory Parameter settings: Level and Service Type: If you set Service Type to GE in step 4, retain the default value (GE) for Level. If you set Service Type to a value other than GE in step 4, set Level to Any and then set Service Type to the same value that you set in step 4. Direction: Set it to Bidirectional. Source Slot/Sink Slot: Set the two parameters to the ID of the slot where the LOA board is housed. Source Optical Port: Set it to a port in the range of 3(RX1/TX1) to 10(RX8/TX8). Source Optical Channel: Set it to 1. Sink Optical Port: Set it to a port in the range of 201(ClientLP1/ClientLP1) to 208(ClientLP8/ClientLP8). Ensure that the client-side port matches an LP port. That is, if you set the source optical port to RXi/TXi, set the sink optical port to ClientLPi. Sink Optical Channel: 1 or 2. Set it to the channel for which you configure the service type in step 4. Operation description: Configure cross-connections from the client side to each LP port. For details about the configuration procedure, see Creating Cross-Connections.
6	Configure ODU0-level cross-connections from LP ports to the WDM side on the LOA board.	Mandatory Parameter settings: See Table 6. Operation description: Configure cross-connections from each LP port to the WDM side. For details about the configuration procedure, see Creating Cross-Connections.

Configuration Procedure for the ODU1 Non-Convergence Mode

Table 2 Configuration procedure

No.	Action	Description
1	Configure the port working mode.	Mandatory Parameter settings: Set Port Working Mode to ODU1 non-convergence mode (OTU1/Any->ODU1->ODU2->OTU2). Operation description: For details about the configuration procedure, see Configuring the Working Mode.
2	Configure the port type.	Optional Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port. Operation description: For details about the configuration procedure, see Modifying Port.
3	Configure the timeslot configuration mode.	Optional Parameter settings: Set ODU Timeslot Configuration Mode to Assign consecutive or Assign random. Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface from the Function Tree. Click By Function and choose ODU Timeslot Configuration Mode from the dropdown list. Set ODU Timeslot Configuration Mode for the WDM side port.
4	Configure the service mode.	Optional Parameter settings: The default value of Service Mode is Client Mode. When you set Service Type to OTU1, set Service Mode to OTN Mode. Operation description: For details about the configuration procedure, see Configuring the Service Mode.
5	Configure the service type.	Mandatory Parameter settings: The available values for Service Type are HDSDI, HDSDIRBR, FC200, FICON Express, OTU1, STM16, or OC-48. Operation description: For details about the configuration procedure, see Configuring the Service Type.
6	Configure ODUk-level cross-connections from LP ports to the WDM side on the LOA board.	Mandatory Parameter settings: See Table 6. Operation description: Configure cross-connections from each LP port to the WDM side. For details about the configuration procedure, see Creating Cross-Connections.

Configuration Procedure for the ODU1_ODU0 Mode

Table 3 Configuration procedure

No.	Action	Description
1	Configure the port working mode.	Mandatory Parameter settings: Set Port Working Mode to ODU1_ODU0 mode (OTU1->ODU1->ODU0[->ODU1]->ODU2->OTU2). Operation description: For details about the configuration procedure, see Configuring the Working Mode.
2	Configure the port type.	Optional Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port. Operation description: For details about the configuration procedure, see Modifying Port.
3	Configure the timeslot configuration mode.	Optional Parameter settings: The value of ODU Timeslot Configuration Mode varies according to the two signal flows in the ODU1_ODU0 mode. When the signal flow is OTU1->ODU1->ODU0->ODU2->OTU2, set ODU Timeslot Configuration Mode to Assign random. When the signal flow is OTU1->ODU1->ODU0->ODU1->ODU2->OTU2, set ODU Timeslot Configuration Mode to Assign consecutive. Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface from the Function Tree. Click By Function and choose ODU Timeslot Configuration Mode from the the dropdown list. Set ODU Timeslot Configuration Mode for the WDM side port.
4	Configure the service mode.	Mandatory Parameter settings: Set Service Mode to OTN Mode. Operation description: For details about the configuration procedure, see Configuring the Service Mode.
5	Configure the service type.	Mandatory Parameter settings: The available values for Service Type is OTU1 only. Operation description: For details about the configuration procedure, see Configuring the Service Type.
6	Configure ODUk-level cross-connections from LP ports to the WDM side on the LOA board.	Mandatory Parameter settings: See Table 6. Operation description: Configure cross-connections from each LP port to the WDM side. For details about the configuration procedure, see Creating Cross-Connections.

Configuration Procedure for the ODUflex Non-Convergence Mode

Table 4 Configuration procedure

No.	Action	Description
1	Configure the port working mode.	Mandatory Parameter settings: Set Port Working Mode to ODUflex non-convergence mode (Any->ODUflex->ODU2->OTU2). Operation description: For details about the configuration procedure, see Configuring the Working Mode. NOTE: When the RX1/TX1 port receives the FC800 service, set Port Working Mode to ODUflex non-convergence mode (Any->ODUflex->ODU2->OTU2) only for port LP1. And set Port Working Mode to None (not for ports) for the other seven LP ports.
2	Configure the port type.	Optional Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port. Operation description: For details about the configuration procedure, see Modifying Port.
3	Configure the timeslot configuration mode.	Mandatory Parameter settings: The default value of ODU Timeslot Configuration Mode is Assign random. If the default value is used, skip this step. Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface from the Function Tree. Click By Function and choose ODU Timeslot Configuration Mode from the the dropdown list. Set ODU Timeslot Configuration Mode to Assign random for the WDM side port.
4	Configure the service type.	Mandatory Parameter settings: The available values for Service Type are 3GSDI, 3GSDIRBR, FC-400, or FC-800. FC-800 is only for the RX1/TX1 port. Operation description: For details about the configuration procedure, see Configuring the Service Type. NOTE: The FICON4G service and the FC400 service are processed identically. For the FICON4G service, you can configure it as the FC400 service on the U2000. The FICON8G service and the FC800 service are processed identically. For the FICON8G service, you can configure it as the FC800 service on the U2000.
5	Configure the ODUflex tolerance(ppm).	Optional Parameter settings: For the transmission of 3G-SDI services, set this parameter to 10; for the transmission of other services, set this parameter to 100. Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the displayed window, set ODUflex tolerance(ppm) for the required ports.
6	Configure ODUk-level cross-connections from LP ports to the WDM side on the LOA board.	Mandatory Parameter settings: See Table 6. Operation description: Configure cross-connections from each LP port to the WDM side. For details about the configuration procedure, see Creating Cross-Connections.

Configuration Procedure for the ODU2 Non-Convergence Mode

Table 5 Configuration procedure

No.	Action	Description
1	Configure the port working mode.	Mandatory Parameter settings: Before setting Port Working Mode to ODU2 non-convergence mode (Any->ODU2->OTU2) for port LP1, set to None (not for ports) for the other seven LP ports. Operation description: For details about the configuration procedure, see Configuring the Working Mode.
2	Configure the port type.	Optional Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port. Operation description: For details about the configuration procedure, see Modifying Port.
3	Configure the timeslot configuration mode.	Mandatory Parameter settings: Set ODU Timeslot Configuration Mode to Assign random or Assign consecutive. Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface from the Function Tree. Click By Function and choose ODU Timeslot Configuration Mode from the the dropdown list. Set ODU Timeslot Configuration Mode for the WDM side port.
4	Configure the service type.	Mandatory Parameter settings: Set Service Type to FC800 only for the RX1/TX1 port. Operation description: For details about the configuration procedure, see Configuring the Service Type.
5	Configure ODUk-level cross-connections from LP ports to the WDM side on the LOA board.	Mandatory Parameter settings: See Table 6. Operation description: Configure cross-connections from each LP port to the WDM side. For details about the configuration procedure, see Creating Cross-Connections.

Related:

End-to-End GE Services Cannot Be Created on the OptiX OSN 6800

When unable to configure OSN1800 using built in WebLCT TL1 without need U2000 or WebLCT on laptop?

When End-to-End GE Services Cannot Be Created on the OptiX OSN 6800?

WDM Basic Concepts

The basic concepts involved in WDM service configuration include electrical cross-
connections, WDM service types, and board models. Understanding the basic concepts helps
you successfully configure services.
General Principles for Configuring Electrical Cross-
Connections
Electrical cross-connections include inter-board cross-connections (namely, cross-connections
between boards) and intra-board cross-connections (namely, cross-connections inside a
board). This topic describes the concepts, port types, configuration principles, and
applications of the two types of electrical cross-connections.
Inter-board Electrical Cross-Connections
This topic describes the concept, port types, configuration principles, and two applications of
inter-board electrical cross-connections. In addition, this topic provides an example of
configuring inter-board electrical cross-connections using the U2000.
Basic Concept
Inter-board electrical cross-connections are configured between boards to groom ODUk and
GE services inside a subrack. They are configured on the U2000.
Specifically, inter-board electrical cross-connections can be configured either between OTN
tributary and line boards (include PID boards) or between line boards (include PID boards).
The line boards include OTN line boards, universal line boards.
Some OTU boards for the OptiX OSN 3800 and OptiX OSN 6800 support inter-board 10GE
and GE cross-connections. For details, see section "Physical and Logical Ports".
Port Type
The source and sink ports must be specified when you configure inter-board cross-
connections. On the U2000, the following ports can be configured as the source or sink ports
of cross-connections:

• ClientLP-n: the logical client-side port of a board in compatible mode, for example, 201(ClientLP1/ClientLP1)-1, where 201(ClientLP1/ClientLP1) indicates the port number and -1 indicates the channel number.
• ODUkLP-n: the logical ODUk port of a board in compatible mode, for example, 61(ODU0LP1/ODU0LP1)-2, where 161(ODU0LP1/ODU0LP1) indicates the port number and -2 indicates the channel number.
• RX/TX-n: the logical client-side port of a board in standard mode, for example, RX2/TX2-2, where RX2/TX2 indicates the port number and -2 indicates the channel number. n(INn/OUTn)-OCH:1-ODUk:m-ODUp:q: the ODUk-level logical port of a board in standard mode, from which you can learn the service mapping path. The service mapping paths are different in the following ODU timeslot configuration modes: Assign consecutive and Assign random.

-- In the Assign consecutive mode, level-by-level service mapping is performed from

lower rates to higher rates, for example, ODU0->ODU1->ODU2. In this example,

the logical port is represented as 1(IN1/OUT1)-OCH:1-ODU2:1-ODU1:2-ODU0:1,

which means the first ODU0 in the second ODU1 of the first ODU2 on optical port

.

– In the Assign random mode, cross-level service mapping is performed from a low

rate to a high rate, for example, ODU0->ODU2. In this example, the logical port is

represented as 1(IN1/OUT1)-OCH:1-ODU2:1-ODU0:1, which means the first

ODU0 in the second ODU2 on optical port 1.

Configuration Principles

The source and sink ports of a cross-connection must have the same ODUk service

granularity and line rate (standard mode/speedup mode ), but they do not require the same

board working mode (standard/compatible) or ODUk timeslot configuration mode (assign

random/assign consecutive). The following figure shows ODU0-level cross-connections. In

the figure, each of the boards can work in either standard or compatible mode.

• As for the same ODUk service granularity, tributary boards (standard/compatible) can interconnect with line boards (standard/compatible), and the cross-connections between the boards are indicated by 1 3 4 2 in the figure.
• As for the same ODUk service granularity and line rate, line boards (standard/compatible) can interconnect with each other, and the cross-connection between the boards is indicated by 5 in the figure.

NOTE

• On the U2000, the subrack layout diagram displays different names of the board in different modes(standard and compatible). For example, the name of the TN52ND2 board in standard mode is displayed as TN52ND2(STND), and the name of the TN52ND2 board in compatible mode is displayed as TN52ND2. For the board names in different modes, see 2.1.2 Standard Mode and Compatible Mode.
• Line Rate is a parameter available only to line boards and can be set using the U2000. For theparameter setting of boards, see the "Parameters Can Be Set and Queried on the NMS" topic for the boards.

More blog:

End-to-End GE Services Cannot Be Created on the OptiX OSN 6800

Comunication failure between the GSCC and EOW Gateway NE

Broadcast storm occured in S5300 when STP was ruuning

Incorrect Client-Side Service Type Causes Failure of Interconnection With a Router

Incorrect client-side service type causes a failure of interconnection with a router.

Product

OptiX BWS 1600G, OSN 6800, OSN 8800

Fault Type

Equipment Interconnection

Client Equipment

Symptom

On a network, an ETMX board on the OptiX BWS 1600G is used to receive a 2.5 Gbit/s service from a router on the client side. Client-side channels run properly after an expansion is performed on the network.

When the ETMX board on the OptiX BWS 1600G receives the 2.5 Gbit/s service, interconnections with ports on the router are successful but exchanges of protocols fail. After an outloop is configured on the ETMX board at the local end by using the NMS to loopback the service to the router, port interconnections and protocol exchanges are successful. After an inloop is configured on the WDM-side optical port on the ETMX board at the remote end by using a fiber patch cord to loopback the service to the router, port interconnections are successful but protocol exchanges fail. This indicates that the fault lies on the WDM-side link or interconnected ports.

Cause Analysis

The analysis of the problem is as follows:

1. An SDH analyzer is used to test the WDM-side channel after the expansion is performed. No exception is found.
2. After the outloop on the ETMX board at the local end is performed, port interconnections and protocol exchanges are successful. This indicates that the router is running properly.
3. After the inloop on the ETMX board at the remote end through a fiber patch cord is performed, protocol exchanges fail. This indicates that protocol configuration is incorrect after signals are transmitted from the router to the ETMX board.

The preceding information shows that the problem is due to incorrect configurations of the ETMX board.

Procedure

1. Check the WDM-side configurations of the board. Service Type for services received from the client side of the ETMX board can beSDH, SONET, or ODU1.. By default, Service Type is set to SDH and J0 byte in the SDH interface overhead is set to Null.
2. Check the interconnected ports and no alarm is generated. This indicates that the no error is generated in the J0 byte.
3. Confirm that on the client side of the OptiX BWS 1600G, the service type interconnected with the router is OC48, which is different from the service type of the ETMX board. This is why the problem occurs.
4. Change Service Type of the ETMX board to SONET. Then, protocol exchanges are successful and services are normal.

Result

The problem is resolved.

Reference Information

None.

MORE BLOG:

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

Dispersion Topology Affects System Performance

Dispersion topology affects system performance.

Product

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

Fault Type

Dispersion Abnormity

BEFFEC_EXC

Symptom

The AB network uses the OptiX BWS 1600G 80-channel system, the system OSNR satisfies the requirement for transmitting 10G services. However, BEFFEC_EXC alarms are reported for some wavelengths, indicating that the pre-FEC BER exceeds the permitted range. In addition, the multi-channel spectrum analyzer (MCA) scanning result shows that the OSNRs for some wavelengths are low.

The OSNRs for all wavelengths transmitted from site B to site A are low, and BEFFEC_EXC alarms are reported for some wavelengths.

The following figure shows the network topology.

Figure 1 The Network Topology of AB Network

Cause Analysis

The inherent dispersion of G.655 fibers is near 0 ps/nm.km. Therefore, the signal transmission performance is likely affected by non-linear effects during long-haul transmission of wavelengths over G.655 fibers. The non-linear effects lead to a wider spectrum. A wider spectrum results in a higher noise base than the actual noise base and lower scanned OSNRs than the actual OSNRs.

Dispersion and non-linearity affect one other. The dispersion topology in the direction from site A to site B has a relatively good quality and minimizes the impact of non-linear effects on the optical spectrum. Therefore, the scanned OSNRs in this direction are close to the actual OSNRs. The dispersion topology in the direction from site B to site A has a relatively poor quality and fails to effectively suppress the impact of non-linear effects on the optical spectrum. Therefore, the scanned OSNRs in this direction are lower than the actual OSNRs.

The impact of non-linear effects on the system performance can be minimized by optimizing the dispersion topology in the direction from site B to site A. By doing this, the scanned OSNRs will be closer to the actual OSNRs.

Procedure

1. Collect data from the live network. The network conditions satisfy the requirements for commissioning line optical power.
2. Verify that the flatness of each wavelength. The flatness of each wavelength is within the permitted range using the MCA.
3. Calculate the residual network dispersion according to the design documents. The residual dispersion is within the range defined in 10G OTU board specifications.
4. Optimize the dispersion topology in the direction from site B to site A to minimize the impact of non-linear effects on the system performance. The scanned OSNRs are closer to the actual OSNRs. The problem is resolved.

Result

The problem is resolved.

Reference Information

Optical fibers (such as LEAF and G.653 fibers) with smaller dispersion coefficients cause more intensive non-linear effects than optical fibers (such as SMF fibers) with larger dispersion coefficients. To improve the receive-end system performance, you can optimize the dispersion topology.

MORE BLOG:

What’s the alarm on the OptiX OSN 1800II board restarts after power-off

Cautions for Drive Failure on the SSX2T2TM Module

Watch out Wavelength Information of the TNF1X40 on the OSN 1800

WDM-Side Pre-FEC BER Changes Drastically

Because the accumulated PMD over a 10G line exceedes the design value, the WDM-side pre-FEC BER changes drastically.

Product

OptiX Metro 6100

OptiX Metro 6040

OptiX OSN 6800

OptiX OSN 8800

Fault Type

Bit Error

PMD Abnormity

Symptom

During expansion of WDM equipment on the network L, the pre-FEC BER in three 10G channels for expansion changes drastically. Within a day, the pre-FEC BER changes from 10^–6 to 10^–11.

The newly deployed 10G services report a transient alarm indicating that the pre-FEC BER crosses the threshold. The existing 2.5G services are normal without any bit error or alarm.

Cause Analysis

Compared with low-rate services such as 2.5G services, high-rate services such as 10G or 40G services have higher requirements for specifications of cables. For example, if the accumulated PMD is higher than the tolerance value, a large non-linear cost will be introduced. As a result, system performance deteriorates.

The possible causes of the fault are as follows:

• The line optical power fluctuates, with a deviation greater than 3 dB.
• The board at the transmit end is faulty.
• The board at the receive end is faulty.
• The quality of line cables deteriorates (for example, PMD is excessively high).

Procedure

1. The collected data indicates that the line optical power does not change drastically.
2. Replace the relevant board, but the BER still changes drastically. Therefore, the fault is irrelevant to the board.
3. The data on the line collected by using the OTDR in a test indicates that reflection is lower than or equal to -27 dB.
4. Therefore, it is suspected that the line PMD exceeds the tolerance of a 10G system. The result of an on-site test indicates that the accumulated PMD over a 10G line reaches 12 ps, exceeding the design value. After the cables are replaced, the fault is rectified.

Result

The problem is resolved.

Reference Information

None.

MORE BLOG:

When customized for North America unable to configure OSN1800.

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

When OptiX OSN 1800 Database Recovery Failures

An NE Is Frequently Unreachable to the NMS Due to Insufficient Processing Capacity of a Router

An NE is frequently unreachable to the NMS due to insufficient processing capacity of a router.

Product

OptiX BWS 1600G

Fault Type

NEs are unreachable.

Symptom

At a certain site, there are four WDM networks consists of 44 subracks of the OptiX BWS 1600G, two iManager T2000 servers, and the iManager T2000 clients on computers.

All equipment is GNEs. On the T2000, each network is configured with two gateways and an extended ECC is used for communication inside a network.

Each network is connected to a HUB with the T2000 server and client by a network cable. The 44 equipment is monitored by the T2000. T2000 displays that the NE communication is abnormal. NEs are unreachable randomly. In addition, the NE_COMMU_BREAK and NE_NOT_LOGIN alarms are reported and cleared automatically a certain while later. After multiple GNEs are configured on the T2000, the T2000 can re-monitor NEs temporarily. The problem occurs at a lower frequency; however, the problem is not resolved completely.

Cause Analysis

The possible causes of the preceding problem are as follows:

• Equipment problems, such as a fault on the SCC board and improper ECC settings, may result in abnormal data flow.
• NMS problems, such as an abnormal database, network card problems, and improper NMS settings.
• DCN networking problems, such as incorrect network of the DCN, a fault on a router or switch, and network cable problems.

After an analysis, it is concluded that before the IP address of Sever 2 is changed, the 44 subracks of the four WDM systems cannot communicate with Server 2 by the switch directly. Because the IP addresses of the subracks are 132.37.23.**, while that of Server 2 is 132.37.5.**, the subracks and Server 2 are not in a same segment. Thus the subracks cannot communicate with Server 2 by a switch directly. The four WDM networks are monitored by Server 2. In this case, the data flow direction is: the equipment<--->the switch<--->the router<--->the switch<--->the server. There are 140 NEs in the four networks. Thus, the data flow is heavy and all data is forwarded by the router. The router, however, a 2630E router of an early age and with low-end technology, is configured with only one FE port. Communications of the two proceeding segments are forwarded through the IP addresses (of the two segments) configured at the same EO port. The bottleneck of the processing capacity of the router causes the network communication abnormality. Communications may be normal when the data volume is small. Once the data volume is larger, congestion of data packets is serious. As a result, NEs are unreachable. After the IP address of Server 2 is changed, the IP address of Server 2 and those of the added four DWDM systems are in the same segment. In this case, the data flow direction is: the equipment<--->the switch<--->the server. The communication between the four systems and Server 2 is implemented by the switch only and router forwarding is no longer required in the communication, thus greatly easing the processing load of the router and avoiding the bottleneck of the processing capacity of the router. The networks are smoother. Thus the preceding problem is resolved.

As a network becomes larger and more equipment is added in the network, the network structure is more and more complicated. If a network is lack of an overall planning at the early stage, communication problems at the later stage are of a great possibility. In addition, some causes for communication problems are difficult to detect, some causes are on the equipment, NMS, or network environment and need to observe for a period to see whether a processing step is effective after the processing step is performed. This consumes a lot of time and efforts. Therefore, at the early stage of project planning, not only service requirements but also the DCN network environment (such as the configuration, module and processing capacity of the router) should be taken into account.

Procedure

1. In an early DCN structure, equipment and servers are connected through a HUB. In the HUB, data packets are broadcasted. This makes a bottleneck of processing capacity of the HUB. In addition, when running a ping command to the equipment, obvious packet losses occur in the HUB. Therefore, it is preliminarily suspected that the HUB is faulty. After replacing the HUB with a Layer 2 24-port switch, the equipment can be connected by running a remote ping command. Large packets are normal and CML tools can log in to NEs. The operation is improved; however, the problems that NEs are unreachable randomly last in Server 2. In System A, the problems are serious and certain sites can be hardly logged in to. Then a conclusion is inferred preliminarily that the HUB has certain impact on the NE communication, but it is not the main cause of the problems. Problems in System A are much more serious than that of other three systems. Therefore, it is suspected that the settings of a certain ECC or a network cable connection is faulty in System A.
2. After the settings of ECC and routing of network cables in System A are checked, T2000 restores the monitoring on NEs. But after a few days' observation, the problems that NEs are unreachable for a long time are reduced obviously. Alarms, that are reported on the T2000, such as an NE_COMMU_BREAK alarm indicates that the NE communication is interrupted and an NE_NOT_LOGIN alarm indicates that an NE is not logged in to, however, indicate that NEs of all systems are unreachable transiently in Server 2. Thus a conclusion is inferred that the settings of ECC and routing of network cables in System A have certain impact on the NE communication, but are not the main cause of the problems. Problems in Server 1 which is located in the same equipment room as Server 2 are rare. Therefore, it is suspected that Server 2 is faulty.
3. Upload the data of certain NEs of the four systems to Server 1 and observe the operation. In addition, re-install the operating system in Server 2 and re-install the T2000. In the next few days of observation, however, it is found that alarms indicating unreachable NEs transiently are not cleared in Server 2 and alarms indicating that the added NEs are unreachable are reported in Server 1. It is inferred that Server 2 is not faulty and is not the main cause of the problems. On Server 1 which is located in the same equipment room, original NEs are reachable and only the newly added NEs are unreachable frequently. In addition, the IP addresses of the four systems are not in the same segment with those of the two servers or old equipment. Therefore, it is suspected that the router is faulty in forwarding.
4. According to analyzed on site by specialists in data communication and analyses with development engineers in optical network on related data in the T2000 logs, it is found that the main cause for the problems (NEs are unreachable) is network congestion. The data that the T2000 transmits to NEs cannot be sent out in time, which also proves the inference in Step 3. The forwarding capacity of the router may be insufficient, which resulting in congestion. Packets cannot be sent out in time. Thus, NEs are unreachable.
5. Change the IP address of Server 2 (132.37.23.254), subnet mask (255.255.255.128), gateway (132.37.23.129) to make sure that the IP addresses of the server and added equipment are in the same segment. In this case, the communication between the equipment and T2000 is implemented directly by the switch and no router forwarding is required. After the modification, all the NEs in the four systems can be re-monitored normally. In the observation for a week, the alarms indicating that NEs are unreachable transiently are completely cleared.

Result

The problem is resolved.

Reference Information

None.

MTU Supported by an LBF Board for the 10G LAN Service on Client Side Cannot Be Configured

The MTU supported by an LBF board for the 10G LAN service on client side cannot be configured.

Product

OSN6800,OSN8800,WDM

Fault Type

Optical Transponder Unit

Symptom

When the WDM interface attributes on an E3LBFS board are configured by using the NMS, the Maximum Packet Length parameter cannot be configured after Service Type is set to 10GE(LAN). By default, Maximum Packet Length is 1518.

Cause Analysis

The possible causes of the preceding problem are as follows:

• An E2LBF board supports client-side services in two modes, that is, Flow Control Mode and Transparent Transmission Mode. In Flow Control Mode, the MTU is 9600 and cannot be changed. In Transparent Transmission Mode, the MTU is invalid.
• An E3LBF board supports the client-side services only in Transparent Transmission Mode. In this mode, the board transfers service packets transmitted from the client side without limits.

Procedure

1. None.

Result

The problem is resolved.

Reference Information

None.

How to Change the Link Type of an Interface?

10G Card Issue in Quidway S5300

In S5700 when configuring voice vlan there is an error says “no enough resources”

How to Configure Two TMX Boards in a Client-Side 1+1 Protection Group Through an SCS Board

How to configure two TMX boards in a client-side 1+1 protection group through an SCS board.

Product

OptiX Metro 3000

OptiX Metro 1000

Fault Type

Protection

Symptom

When configuring two TMX boards in a client-side 1+1 protection group through an SCS board, how to configure the attributes of the WDM interface ?

It is required to determine whether the Laser Status parameter should be set to Open and Automatic Laser Shutdown to Disabled, or Laser Status should be set to Open and Automatic Laser Shutdown to Enabled.

Is the laser on the TMX board closed automatically when the TMX boards work with an SCS board?

Cause Analysis

The setting of the Automatic Laser Shutdown parameter of the port on the WDM side or the client side is irrelevant to the protection. Normally, when the attributes of the WDM interface on the TMX board are configured through an OTU board, the Automatic Laser Shutdown parameter of the port on the WDM side is set to Disabled and Automatic Laser Shutdown of the port on the client side is set to Enabled.

After a client-side 1+1 protection group is configured, the status of the client-side laser is controlled by the status of protection group.

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?

How to enable command log on S9300?

Why Automatical configuration backup cannot work on S5700

LINK_ERR Occurs Due to an Optical Module Fault on the TQX Board

This section describes how to remove the LINK_ERR alarm resulting from an optical module fault on the TQX board.

Product

OptiX OSN 8800

Fault Type

Tributary Unit and Line Unit

LINK_ERR

Symptom

There are two channels of point-to-point 10G LAN services between station A and station B in a network. The TQX tributary board and NQ2 line board are used at either station. After the network connects to a router, it is found that both station A and station B report the LINK_ERR alarms in one channel of 10G LAN services. As a result, this channel of 10G LAN services is interrupted. However, the other channel of 10G LAN service runs normally.

Cause Analysis

The possible causes of this problem are as follows:

• The working mode of receive optical interface on WDM side the NQ2 board at the local station is different from the working mode of the transmit optical interface on the WDM side of the NQ2 board at the opposite station.
• The link is faulty.
• Optical fiber connections are incorrect.
• The opposite equipment is faulty.
• The input optical power of the client-side optical interface on the TQX board is excessively high or low.
• The working modes of the optical interfaces on the client side of the TQX board are inconsistent.
• The board at the local station is faulty.

Procedure

1. Exclude the possibility that working modes of the optical interfaces on the client side of the TQX board are inconsistent since the TQX board has no PHY chip.
2. Check the client-side optical power on the TQX board, finding that the receive optical power on the client side of the TQX board at station A is -6.7 dBm and that at station B is -8.1 dBm. Both of the receive optical power values are in normal range.
3. Make sure that the chip for detecting link status information is located behind the cross-connect chip since the TQX board has no Layer 2 chip. Then, configure an inloop on the client side of the NQ2 board at each of station A and station B, finding that the LINK_ERR alarm on the TQX board at station A is cleared but the LINK_ERR alarm on the TQX board at station B persists.
4. Perform a cold reset on the TQX board at station B. The LINK_ERR alarm persists.
5. Replace the optical module at optical interface 3 on the client side of the TQX board at station B, finding that the LINK_ERR alarm is cleared.
6. Release the inloop at stations A and B. At this point, the LINK_ERR alarm is cleared and normal connection between the network and the router is achieved.

Result

The problem is resolved.

Reference Information

None.

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

How to enable command log on S9300?

Why Automatical configuration backup cannot work on S5700