Content .. 32 33 34 35 ..

HUAWEI OptiX OSN 8800 T64/T32 Intelligent Optical Transport Platform. Product Description - part 34

Front Panel Appearance

Panel

Interface

Usage

Interface

Type

NM_ETH2

RJ-45

l Connects the network

EFI1

interface on the OptiX

OSN 8800 through a

network cable to that on

the U2000 server to

achieve the management

of the U2000 over the

OptiX OSN 8800.

l Connects the NM_ETH1

and NM_ETH2 network

interfaces on an NE

through a network cable

to such interfaces on

another NE to achieve the

communication between

NEs.

SERIAL

DB9

The OAM interface is a serial

NM interface, providing

functions of serial NM and

supporting X.25 protocol.

LAMP1,

RJ-45

This interface drives the

EFI2

LAMP2

running indicators and alarm

indicators of the cabinet that

holds the subrack.

NM_ETH1

RJ-45

l Connects the network

interface on the OptiX

OSN 8800 T32 through a

network cable to that on

the U2000 server to

achieve the management

of the U2000 over the

OptiX OSN 8800 T32.

l Connects the NM_ETH1

and NM_ETH2 network

interfaces on an NE

through a network cable

to such interfaces on

another NE to achieve the

communication between

NEs.

356

Front Panel Appearance

Panel

Interface

Usage

Interface

Type

ETH1, ETH2,

RJ-45

l Connects a network cable

ETH3

from the ETH1/ETH2/

ETH3 interface on one

subrack to corresponding

interfaces on the other

subracks to achieve the

communication between

the master subrack and

slave subracks.

NOTE

When inter-subrack

protection is configured, the

ETH3 interface cannot be

used for the communication

between the master and

slave subracks.

l Connects a network cable

to a CRPC or ROP board

to achieve

communication with the

CRPC or ROP board.

CLK1, CLK2

RJ-45

Connects the CLK1 and

CLK2 interfaces on another

subrack through a network

cable to achieve the

synchronization of clock

signals.

TOD1, TOD2

RJ-45

Connects the TOD1 and

TOD2 interfaces on another

subrack through a network

cable to achieve the

synchronization of timing

signals.

8.5 Orderwire Function

The orderwire provides voice communication for the operation engineers or maintenance

engineers at different stations.

The orderwire provides the following functions:

l Addressing call: Addressing call, that is, point-to-point call, is the basic function of the

orderwire. In this case, the calling party dials the number of the called party.

l Subnet conference call: The subnet conference call realizes a group call among the stations

on a subnet. A subnet refers to the physical subnetwork. It is a collection of the NEs that

have the same subnet ID and are connected by optical fibers.

357

NOTE

If the subnet contains only the OptiX OSN 6800, OptiX OSN 3800, and OptiX OSN 8800 equipment, the

subnet conference call is supported. In any other scenarios, the subnet conference call is not supported.

Only a master subrack supports the orderwire function.

8.6 Security Management

The NMS uses many schemes to manage the security of the OptiX OSN 8800/6800/3800 NE.

8.7 Master-Slave Subrack Management

The OptiX OSN 8800 supports master-slave subrack management. When multiple subracks are

required on one NE, the master-slave subrack mode should be used for unified management of

these subracks. In this manner, the IP resources can be saved. In addition, when optical-layer

ASON and optical-layer services are configured on the NE, the optical subracks on the NE should

be taken out to form a new NE for management. This facilitates the maintenance and reduces

the management cost.

In OptiX OSN 8800 T32/T64, SCC 1+1 protection is recommended for the master subrack.

In OptiX OSN 8800 T32/T64, the SCC boards in the master and slave subrack must use the same

software version.

If the number of subracks on an NE is beyond the NE's management capacity, the NE can be

divided into two NEs for management.

To ensure future smooth expansion, users are recommended to configure separate optical NEs

and electrical NEs.

8.7.1 Master-Slave Subrack Management

In the master-slave subrack mode, the multiple subracks are displayed as one NE on the U2000.

On the same NE, the OptiX OSN 6800 and OptiX OSN 8800 can be configured as the master

and slave subracks.

For the OptiX OSN 8800 T64, when the master subrack uses the TNK2SCC as the system control

and communication board, comply with the following rules to configure the master and slave

subracks.

l Each NE supports a maximum of 24 optical subracks. That is, one master optical subrack

manages 23 slave optical subracks.

l Each NE supports a maximum of 8 electrical subracks. That is, one master electrical subrack

manages 7 slave electrical subracks.

l When an NE consists of optical and electrical subracks, the master subrack of the NE

supports a maximum of 19 slave subracks and the number of electrical slave subracks

cannot exceed 4.

l When an NE uses only optical subracks with the ASON function, the NE supports a

maximum of 24 optical subracks. That is, one optical master subrack manages 23 slave

optical subracks.

l When an NE uses only electrical subracks with the ASON function, the NE supports a

maximum of 4 electrical subracks. That is, one electrical master subrack manages 3 slave

optical subracks.

358

l When an NE consists of optical subracks with the ASON function and electrical subracks

without the ASON function, the master subrack of the NE supports a maximum of 19 slave

subracks and the number of electrical slave subracks cannot exceed 4.

l When an NE consists of optical subracks without the ASON function and electrical

subracks with the ASON function, the master subrack of the NE supports a maximum of

7 slave subracks and the number of electrical slave subracks cannot exceed 4.

For the OptiX OSN 8800 T32, when the master subrack uses the TN52SCC as the system control

and communication board, comply with the following rules to configure the master and slave

subracks.

Each NE supports a maximum of 24 optical subracks. That is, one master optical subrack

manages 23 slave optical subracks.

Each NE supports a maximum of 8 electrical subracks. That is, one master electrical subrack

manages 7 slave electrical subracks.

When an NE consists of optical and electrical subracks, the master subrack of the NE

supports a maximum of 19 slave subracks and the number of electrical slave subracks

cannot exceed 4.

When an NE uses only optical subracks with the ASON function, the NE supports a

maximum of 24 optical subracks. That is, one optical master subrack manages 23 slave

optical subracks.

When an NE uses only electrical subracks with the ASON function, the NE supports a

maximum of 4 electrical subracks. That is, one electrical master subrack manages 3 slave

electrical subracks.

When an NE consists of optical subracks with the ASON function and electrical subracks

without the ASON function, the master subrack of the NE supports a maximum of 19 slave

subracks and the number of electrical slave subracks cannot exceed 4.

When an NE consists of optical subracks without the ASON function and electrical

subracks with the ASON function, the master subrack of the NE supports a maximum of

7 slave subracks and the number of electrical slave subracks cannot exceed 4.

In OptiX OSN 8800 T32/T64, the master subrack is recommended to configure 1+1

protection for the SCC boards.

In OptiX OSN 8800 T32/T64, the software version of the SCC board in the master subrack

must be the same as that of the SCC board in each slave subrack.

If the number of subracks on an NE is beyond the management capability of this NE, the

NE can be divided into two NEs to enable subrack management.

To ensure future smooth expansion, users are recommended to configure separate optical

NEs and electrical NEs.

NOTE

l The word "subrack" in this context means an equivalent subrack. The equivalent subrack takes the

OptiX OSN 6800 subrack as the unit. One OptiX OSN 6800 subrack is an equivalent subrack. One

OptiX OSN 8800 T32 subrack is taken as two equivalent subracks. One OptiX OSN 8800 T64 subrack

is taken as four equivalent subracks.

l Electrical subrack is the subrack that houses the cross-connect board, OTU board, or tributary board.

l Optical subrack is the subrack that houses the optical-layer board only.

359

NOTE

l The slave subrack cannot be upgraded to the master subrack smoothly.

l The HUB mode (one subrack functions as an NE) cannot be upgrade to the master-slave mode smoothly.

l An OCS subrack cannot function as a master or slave subrack but an independent NE. The SDH boards

must be installed in the same OCS subrack.

8.7.2 Subrack Cascading Scheme

Subracks can be connected by using internal or external fibers and use either an ESC or OSC

technology to carry ECC and network management information. The physical layer for

transmitting ECC is a DCC channel. This means that the ECC is transmitted over fibers. In the

master-slave subrack mode, multiple subracks are displayed as one NE on the NMS.

In certain special situations, a network or an NE is isolated on a transport network and no fiber

connection is established between the network or NE and a gateway NE. Huawei provides

extended ECC communication. If subracks are cascaded by using Ethernet cables, an extended

channel (for example, Ethernet) instead of a DCC channel can be used to carry the ECC to meet

the requirements in these special situations.

Connect the ETH1, ETH2, or ETH3 interface on the EFI2 board of the master subrack to the

ETH1, ETH2, or ETH3 interface on the EFI2 board of a slave subrack to implement

communication between the two subracks.

NOTE

When inter-subrack protection is configured, the ETH3 interface cannot be used for the communication

between the master and slave subracks.

Connect the NM_ETH1 or NM_ETH2 interface on the EFI1 or EFI2 board of the master subrack

on the GNE to an Ethernet interface on the NMS computer by using an Ethernet cable so that

the NMS can manage the all the connected subracks. Connect the NM_ETH1 or NM_ETH2

interface on the EFI1 or EFI2 board of the master subrack on an NE to the NM_ETH1 or

NM_ETH2 interface on the EFI1 or EFI2 board of the master subrack on another NE to

implement the communication between the two NEs.

Figure 8-1 shows the subrack cascading scheme.

360

Figure 8-1 Subrack cascading scheme

Extended ECC

Master NM

Master

Subrack-1

Subrack-2

EFI2

Master

Subrack-2

Subrack-1

SCC

OTU

EFI1

OTU

Slave

SCC

Subrack-2

Subrack-1

FIU

SC2

FIU

OADM/OTM

EFI2

OADM/OTM

Slave

Subrack-1

Subrack-2

External

Internal

Ethernet

Bus

Fiber

Cable

Two cascading modes are available in master-slave subrack mode. In the first mode, subracks

are cascaded in tree-like structure, and in the other mode subracks are cascaded in ring-like

structure. By default, subracks are cascaded in tree-like structure. When subracks are cascaded

in tree-like structure, the master and slave subracks are not under protection so that the subracks

can be managed in the same way.

Figure 8-2 shows the tree-like subrack cascading scheme. Figure 8-3 shows the ring-like

subrack cascading scheme.

361

Figure 8-2 Tree-like subrack cascading scheme

Master

NM_ETH2

NM_ETH1

NM_ETH2

NM_ETH1

Subrack 0

ETH1

ETH2

ETH1

ETH2

Slave

ETH1

Slave

ETH2

Slave

Subrack 1

Subrack 4

Subrack 1

ETH2

ETH1

Slave

ETH1

Slave

ETH2

Slave

Subrack 2

Subrack 5

Subrack 2

ETH2

ETH1

ETH2

Slave

ETH1

Slave

Subrack 6

Subrack 3

ETH2

ETH1

ETH2

ETH1

Slave

Subrack 7

ETH2

NE2

NE1

362

Figure 8-3 Ring-like subrack cascading scheme

Master

NM_ETH1

Subrack 0

NM_ETH2

ETH1

ETH2

Slave

ETH1

ETH2

Slave

Subrack 1

Subrack 3

ETH2

ETH1

Normal State

ETH1

ETH2

Slave

Subrack 2

Protection switching

Failure recovery

Master

NM_ETH1

Subrack 0

NM_ETH2

ETH1

ETH2

Slave

ETH1

ETH2

Slave

Subrack 1

Subrack 3

ETH2

ETH1

ETH2

Protection State

Slave

Subrack 2

8.8 Administration and Maintenance

The design of the cabinet and boards and the configuration of the system incorporate the

requirements with easy and effective operation, administration, and maintenance of the

equipment.

8.8.1 Alarm and Performance Event Management

The system uses the alarm and performance event monitoring function for administration and

maintenance.

363

System Alarm Function

The system supports the alarm management function. This enables the set and query of alarm

level, automatic reporting of alarms, and deletion of history alarms. These help the user to

monitor and maintain the system in real time.

The system monitors alarm status of equipment in real time, analyzes alarms according to the

alarm relativity, and displays the analysis result on the client. A user can view the analysis result

on the client. The NMS enables a user to set the maximum alarm storage capacity and storage

period. If the history alarm data exceeds the capacity or the storage period of the history alarm

data expires, the NMS automatically saves the data in the history alarm database to files.

System Performance Monitoring Function

The performance event is a key parameter that reflects the working performance.

Knowledge about the causes that lead to the performance events, the relevant boards and alarms

helps locate the faults during routine maintenance and analyze faults when they occur.

At the end of each performance monitoring period, the SCC board reports performance events

to the NMS. The NMS enables a user to set the maximum performance storage capacity and

storage period. If the history performance data exceeds the capacity or the storage period the

history performance data expires, the NMS automatically saves the data in the history

performance database to files.

Performance events are related to the alarms. If the performance event value exceeds the preset

threshold value, the relevant alarm will be generated.When a performance event occurs, check

whether the relevant alarm is generated.

System Monitoring Items

The system provides the following system monitoring information.

l Temperature of the running board

l In-position status of the physical board

l Management function of the boards in different functional units

l Management function of the fan module

l Management function of the power module

l Input/Output optical power of the OTU

l Input/Output optical power of the OA

l Current status of the laser in the amplifier

l Temperature of the laser in the amplifier

l Temperature of the transmitting laser

8.8.2 Performance Monitoring of Access Services

Table 8-3 lists the 15-minute or 24-hour performance monitoring of access services provided

by the OptiX OSN 8800.

364

NOTE

l The equipment can save 15-minute performance data in a maximum of 96 performance detection

periods. That is, the equipment can save twenty-four hours of performance data (15-minute

performance).

l The equipment can save 24-hour performance data in a maximum of 30 performance detection periods.

That is, the equipment can save thirty days of performance data (24-hour performance).

Table 8-3 Performance monitoring of access services

Service

Monitored Item

Service Type