hit training presentation2

7/27/2019 HiT Training Presentation2

1/97

Siemens hiT 70 series training


2/97

Course Contents

Basic units of SDH multiplexer General Description of HiT 7070/ HiT7060 /HiT7035 Functionality of Modules Hardware / Software installation

Installation of Cards TNMS CT (LCT) and OSI Stack setup Commissioning of HiT

Operation and Maintenance Routine Maintenance

Equipment Configuration database backup (VCDB) Cleaning Dust filter and fan module

Understanding Alarm Generation and Alarm Handling

Performance Analysis Creation of services Testing / Trouble shooting Card Replacement

Hardware / Software Upgrade Installation of new cards HiT software upgrade


3/97

Basic units of SDH Multiplexer


4/97

Basic units of SDH Multiplexer

An SDH Multiplexer has following basic units NE Controller

Timing Unit

Higher Order Cross connection

Lower Order Cross connection

SDH / PDH / Ethernet / ATM Line Interface units


5/97

General Description of hiT 7070 /hiT 7060 / hiT 7035


6/97

General Description of HiT 7070 / HiT 7060 / HiT 7035

Siemens new range of equipment that makes thepromise of Next Generation SDH a reality:

the SURPASS hiT 70 series.

This platform provides the flexibility of true packet

switching and Ethernet transport, while operating withthe inherent reliability of SDH. Multiple network elementsare integrated and consolidated into a single compactunit. The efficiency of this approach, together withextensive use of highly integrated components allows theSURPASS hiT 70 series to be offered at lower costs

than current solutions.

Data + Voice = SURPASS hiT 70 series


7/97



8/97


(Enabling Technologies)

Following are the key enabling technologies for SURPASS hiT 70

series :

1) Generic Framing Procedure (GFP)

2) Virtual Concatenation (VC, a standard way of packing lower

bandwidth circuits into SDH/SONET frames)3) Link Capacity Adjustment Scheme (LCAS)

4) Ethernet Functions


9/97


(Enabling Technologies/ GFP)

GFP/G.7041 provides a framing procedure for octet-aligned, variable-

length payloads for subsequent mapping into SDH VC-groups. GFP

differs from other packet mappings (e.g., Packet over SONET)

because it is Layer 2 independent and maintains the Layer-2 header

information, in a manner such that the destination node may

reproduce the entire stream of Layer-2 frames. This in turn, allows

the transport network to transparently connect two Layer-2 devices


10/97


(Enabling Technologies/ Virtual Concatenation)

In order to transport payloads exceeding the payload capacity of thestandard set of Virtual Container Group (VC-group), VirtualConcatenation was defined. There are two types of concatenationsdefined in ITU standards: contiguous concatenation and virtualconcatenation

Contiguous concatenation was conceived to accommodate high-speed data applications that use protocols such as ATM. The ITUdefined contiguously concatenated containers only support certainrates including: STM-4c, STM-16c and STM-64c

The basic idea ofVirtual concatenation (VC) is to create a finergranularity of payloads than contiguous concatenation can offer.Carriers can map any arbitrary bandwidth to a corresponding andappropriate number of VC-12 or VC-3 or VC-4 channels. The benefitof VC is that little bandwidth is wasted and carriers now have a moreefficient scenario for carrying data over the SDH/SONET network


11/97


(Enabling Technologies/ LCAS)

LCAS is a protocol to synchronize the re-sizing of a virtual

concatenation group in use, so it can be changed without corrupting

packets in the process. LCAS provides automatic recovery of a link

after member failures LCAS builds on Virtual Concatenation. While the virtual

concatenation is a simple labeling of individual VC/VT members

within a virtual concatenation group, LCAS is a two-way signaling

protocol that runs continuously between the two ends of the pipe

and ensures that commands from the network management systemto alter the pipe capacity do not impair the users traffic


12/97


(Enabling Technologies/ LCAS)

Layer 2 Ethernet functions implemented in the system typicallyinclude the following:1. Layer 2 aggregation and switching function

2. 802.1p QoS/CoS based on Ethernet port and/or VLAN

3. Rapid Spanning Tree Protocol (RSTP) acc. IEEE802.1w to provideLayer 2 traffic resiliency mechanism

4. Rate limiting function at per port or per VLAN basis, the maximumallowable rate per port or per VLAN is user provisionable

5. VLAN function

6. Ethernet Shared Ring (ESR)

7. Services acc. ITU-T G.8011

8. Services acc. MEF Ethernet Service Definition


13/97


(hiT 7070 Overview)

Subrack Types

Double-row subrack (DC)

Single-row subrack (SC)

Extension shelves

Metro WDM OADM (Lambda Shelf)

Booster/Preamplifier shelf

DCM shelf

PDH extension shelf (microshelf)Switch Matrices

Double-row subrack: Fully non-blocking switching matrix 160 Gbit/s switching capacity

with VC-4 granularity

Single-row subrack: Fully non-blocking switching matrix 110 Gbit/s switching capacity

with VC-4 granularity

Fully non-blocking switching matrix with VC-12 and VC-3 granularity

Packet fabric for Resilient Package Rings with 2.5 Gbit/s capacity

Interface Types

Electrical traffic interfaces: 2 Mbit/s, STM-1

Optical traffic interfaces: STM-1/4/16/64, 40 Gbit/s optical traffic interface,2,5 Gbit/s coloredinterface, 10 Gbit/s colored interface, 10 Gbit/s colored interface (long haul) with FEC

Ethernet interfaces: 10/100/1000 BaseT, 1000BaseLX/SX via GFP-F


14/97


(hiT 7070 Overview)

NE features

Automatic SW download, plug and play on a per card and port granularity

Auto link detection

Virtual concatenation (VC-3, VC-4, VC-12) and contiguous concatenation VC-4

Engineering order wire (EOW)

Configurable squelch tables

Protection

MSP (1+1) for STM-1/4/16/64 MSP (1:1) for STM-1/4

1+1 port protection for STM-1/4/16/64 optical and for STM-1 electrical

1+1 protection of switching matrices

1:N card protection for 2 Mbit/s

SNCP

4-fiber shared ring (BSHR-4) for STM-16/64

2-fiber and multiple 2-fiber shared ring protection for STM16/64 (BSHR2)

Ethernet Functionality

Generic Framing Procedure GFP-F (ITU-T G.7041)

GFP mapping and GFP sub-channeling for Ethernet traffic

Ethernet flow control and traffic shaping adjustable in steps of 1 Mbit/s

Up to 8 virtual concatenated groups at the 10/100 BaseT board and up to 4 virtual

concatenated groups at the GbE boards


15/97


(hiT 7060 Overview)

SURPASS hiT 7060 employs an innovative dual TDM/Data plane design,with large SONET/SDH high-order cross-connect capacity (70G) andsubstantial low-order cross connect (5G) capacity. This feature enablesdynamic allocation of platform bandwidth for TDM, IP and ATM traffic flows.The L2 data module provides L2 switching and aggregation functions.SURPASS hiT 7060 supports a rich variety of client data interfacesincluding 10/100M FE/FX, GE, and ATM. The system supports IP/Ethernet,Layer 2 switching, RPR, and ATM PVC switching functions, providing highlyefficient data transport

SURPASS hiT 7060 supports a wide range of SONET/SDH/PDH interfacesfrom high speed optical interfaces OC-48/STM-16 to optical/electricalinterfaces of OC-3/STM-1, DS3/E3, 1.5Mb/s, and 2Mb/s. It provides a fullsuite of SONET/SDH functions including mapping, multiplexing, cross-connection, various protection schemes such as MS-SP Ring, SNCP, MSP,

DNI, etc., Virtual Concatenation (VCAT), contiguous concatenation (VC-4-4c and VC-4-16c) and Link Capacity Adjustment Scheme (LCAS)


16/97


(hiT 7035 Overview)

SURPASS hiT 7035 is a compact carrier class full blown STM-4/-1

add-drop-multiplexer which can be upgraded to a compact STM-16

ADM.

SURPASS hiT 7035 supports core equipment protection with nosingle point of failure, and PDH electrical protection.

SURPASS hiT 7035 offers a High Order cross connection capacity

upto 15.2G and a Low Order cross connection capacity up to 5G.

SURPASS hiT 7035 supports the complete range of PDH and SDH

interfaces ranging from E1, E3/DS3, STM-1 el./opt. to STM-4 and

even STM-16. It provides a full suite of SDH functions including

mapping, multiplexing, cross-connection and various protection

schemes


17/97

Functionality of Modules


18/97


(hiT 7070)


19/97


(hiT 7070)


20/97


(hiT 7060)


21/97


(hiT 7060)

SURPASS hiT 7060 supports two types of cross connection and switching capabilities: Type A: 70G/5G CC

HOCC: (70G) 448 448 VC-4 LOCC: (5G) 2016 2016 VC12 (9696 VC-3 or 32 32 VC-4

equivalent) Type B: 25G/10G CC w. 1 STM-16/4 optical interface on the same module

HOCC: 25G, 160 160 VC-4

LOCC: 10G, 4032 4032 VC12 (equivalent to 192 192 VC-3, or 64 64 VC-4) SURPASS hiT 7060 provides the following line interface:

SDH: 4 STM-1/4 Optical Line Interface Board (max. 32 ports/system) SDH: 1 STM-16 Optical Line Interface Board (max. 8 ports/system) SDH: 2 STM-1 Optical Interface Board (max. 16 ports/system) SDH: 4 STM-1E (W/P) Electrical Interface Card (max. 32 ports/system) TDM: 63 E1 (W/P) client interface card TDM: 3 E3/DS3 (W/P) interface card IP/Ethernet: 6 FE/L2 interface card IP/Ethernet: 8 FE/T Ethernet interface card IP/Ethernet: 2 GE + 8 FE/A interface card IP/Ethernet: 2 GE + 8 FE RPR interface card Optical Amplifier card


22/97


(hiT 7035)

SURPASS hiT 7035 supports two types of cross connection and switching capabilities: ADM-4/-1: 7.2G/2.5G CC with 1x STM-4/-1 line interface:

HOCC: (7.2G) LOCC: (2.5G)

ADM-16/-4: 15.2G/5 CC with 1x STM-16/-4 line interface: HOCC: 15.2G LOCC: 5G

SURPASS hiT 7035 provides the following line interfaces:

1. SDH: 1 STM-4 Optical Line Interface Board 2. SDH: 2 STM-1 Optical Interface Board 3. SDH: 2 STM-1E (W/P) Electrical Interface Card 4. SDH: 2 STM-1E PaddleCard 5. PDH: 3 E3/DS3 (W/P) interface card 6. PDH: 3 E3/DS3 Paddle 7. PDH: 63 E1 (W/P) client interface card 8. PDH: 63 E1 75ohm Paddle 9. PDH: 63 E1 120ohm Paddle

10. ATM-IMA 126xE1 interface card 11. IP/Ethernet: 8 FE/L2 interface card 12. IP/Ethernet: 8 FE/T Ethernet interface card 13. IP/Ethernet: 1 GE/T interface card 14. Optical Amplifier cards (13, 15 and 18 dBm) 15. Optical Pre-Amplifier card (20dB)


23/97

Hardware / Software Installation


24/97


(Card Installation HiT 7070)


25/97



The slots 307 and 308 are dedicated for:

High Order switching fabric SF160G

The slots 214 and 215 are dedicated for Synchronous Equipment Timing Source:

Central Clock Unit (CLU)

The card slot 314 is dedicated for: System Controller and Overhead Unit (SCOH)

BSHR/4:

For BSHR/4 protection up to two groups can be configured. The first group occupies slots

303, 304, 305, 306

For the second group following slots are reserved

309, 310, 311, 312

In the slot 303 and / or 309 Ring West Worker card shall be configured

In the slot 304 and / or 310 Ring West Protecting card shall be configured

In the slot 305 and / or 311 Ring East Worker card shall be configured

In the slot 306 and / or 312 Ring East Protecting card shall be configured

MSP 1+1: For the MSP 1+1 protection the following pairs of slots are reserved

The card in the slot 301 is a Worker Card and the card in the slot 302 is a Protecting Card for the card in the slot 301







26/97




27/97




28/97




29/97


(TNMS-CT and OSI stack)

Depending on the needs, two different modes are available forTNMS CT.

LCT Mode: The Local Craft Terminal (LCT) is used for local management and

commissioning of network elements. The MSN Manager, organizationalrelationships between network elements in the network and network

alarms are not available for the LCT. The LCT can communicate with amaximum of 150 network elements. Up to three element managers maybe open at the same time only.

NCT Mode: The Network Craft Terminal (NCT) is used for local or remote

management of network elements. In addition to the LCT functions, themonitoring of all the alarms reported from each accessible networkelement is allowed. The NCT can communicate with a maximum of 150network elements (including alarm monitoring). Up to 50 elementmanagers or up to five MSN Managers may be open at the same timeonly.


30/97



The TNMS CT specific software package allows the creation of a graphicalrepresentation of the network such as a geographical arrangement of the NE symbolsas an example.

Each NE is represented on the GUI by an individual icon. The NE-specific Element Manager can be activated via mouse click on the NE

symbol. It is possible to open more than one Element Manager application at the same time.

Program control and command entry can be performed by means of the mouseand/or keyboard using pull-down menus and the deposition of popup menus,activated via right mouse button click.

All menus and actions, which can be activated via popup menu are also selectablevia pull-down menu-titles.

Menu titles and menu options, which are frequently used, can also be selected viafunction keys.

The operator is guided through the program by menus. One has no need to learncomplex command syntax. Furthermore the program offers mechanisms as filteringor sorting of information and offers support through help functions.


31/97



Starting TNMS-CT server TNMS CT Server is started automatically on system startup,

before any user is logged on. Once it has been started, aconnection to all configured and activated network elements isestablished and their data is uploaded. An icon is displayed in

the Windows 2000 taskbar. Once the Server has started, it isalways active. Moreover, terminating the Client does not result instopping the Server and disconnecting from the NEs.

Starting a TNMS CT client session Once the TNMS CT Server has been started, TNMS CT Client

can be started from the Computers Desktop: From "Start" menu

using the "CT Client" icon


32/97




33/97



1. Enter the name or the IP address of your TNMS CT server

2. Enter a valid user name and password. By default the name of the last logged on

user is displayed. You are given your user name and password by your TNMS

administrator

3. Click on 'Login' button or press the enter key.

4. Wait up to end of Startup procedure


34/97



The TNMS CT GUI gives access to all functions for supervision, operation, configuration and maintenance of thenetwork. The set of functions available to each individual operator depending on the operators user class which isdefined by the administrator. Via the TNMS CT GUI you can also start the element manager applications (e.g. theEM of an SMA16/4 or the MSN Manager) to control and configure individual network elements

The TNMS Client user interface consists of the following parts:

1. Menu bar:

Menu bar of the TNMS CT main window contains the number of the menu items. When you click on one ofthese menu items, the pull-down menu specific to the menu item opens.

2. Toolbar:

The toolbar runs along the top edge of the main window above the working area. Clicking on one of thesebuttons with the left mouse button provides quick and particularly easy access to certain frequently usedfunctions.

3. Status bar:

The status bar runs along the bottom of the main window. It gives information on the operating states anddisplays important messages, such as alarms, in short form

4. Network View:

The Network View provides graphical representation of your network. Orientation within the Network View canbe improved by using a background bitmap. For example, you can attach the picture of a city map to bedisplayed in the background of the network plan and position your network elements in this map accordingto their real location. Moreover, the Network View offers quick access to information concerning single NEs(e.g. current access state, alarm state). Each item of the Network View offers an individual context menu.

5. Working Area:

This is the main area where the operator can arrange the individual work place


35/97




36/97


(TNMS-CT setup)Connection to NE via F Interface

In the TNMS CT, click the DCN Mgm button.

In the DCN Management window, select Serial Line Server -> QST V2Serial

Line Channel and click the Properties button.

Make the settings according to figure given below


37/97



In the DCN Management window, select Serial Line Server -> QST V2 Serial Line

Channel -> QST V2 Serial Line NE and click the Properties button.

Make the settings according to figure


38/97



The default password is NEPASSWORD


39/97


40/97


(TNMS-CT setup)

OSI stack setting

Open the OSI Stack Configuration window using the Start menu: Start -> Settings -> ControlPanel -> OSI Stack icon.

In the OSI Stack Configuration window, make the settings according to figure below After this connect NE


41/97


(TNMS-CT setup)Connection to NE via Q Interface

In the TNMS CT, click the DCN Mgm button.

In the DCN Management window, select the NE from the TNMS-CT Server entriesand click the Properties button.

Make the settings according to figure below


42/97



User Name: NMS for NCT and LCT for LCT

The default password is NEPASSWORD


43/97



The default area address is the SIEMENS proprietary address:495349454D454E534147000001

Enter it into the QST Properties window

Read the MAC address of the main controller (SCOH) from the card extraction aid and add it(e.g. 00D093010CD9).

At the end of the NSAP/IP address, add the NSAP selector 01.

Enter the T selector QST.

Next step is to connect NE


44/97


(Commissioning of hiT 70xx series)

Following are the steps for commissioning of HiT 70xx series HiT Check the Read Write Status Change the LCT/NCT password Enter NE location and Name Activate the NE Set the NE time and date Set MCF Stack parameters Enter the sub rack data Set the NE to operation Set alarm severity threshold Configure Modules

Configure DCC channels Configure Synchronization Configure Module features Configure Traffic flow features Perform Back of NE database (VCDB)


45/97



Check Read / Write Status

Start up and login TNMS CT client session. Startup hiT element manager application. Check the write access

Write access allows the user to perform configuration changes. Only one user can have write access to the NE at

the same time. In case the NE is in read only mode, request write access to that NE by selectiing


46/97



Change LCT/NCT password

The default password is NEPASSWORD. It should be changed as soon as possible.

Change the LCT/NCT NE password by selecting


47/97



Enter Location and Name

The NE Name must be entered before you can set the hiT to ACTIVE STATE. Enter NE name, location andapplication type by selecting


48/97



Activate the NE

Activate the NE by selecting After applying, the net element starts to reboot. This will take some minute. Now connect again to the NE (start

element manager). However, changing from Idle to Active state is only possible if the NE name is not the defaultname

After reboot login NE again and prove NE state


49/97



Set the NE time and date

Set NE Date and Time by selecting

The internal clock of the operating system controls date and time. The network element time is configured with an

offset relative to GMT


50/97



Set MCF stack parameters

The NSAP address (Network Service Access Point) must be specified before hand on the basis of a network planso that na individual address is assigned to each NE

For the case of hiT 7060 and hiT 7035 IP address is specified instead of NSAP


51/97



Enter the Sub rack data

Specific customer identification data can be entered for the sub rack. Enter sub rack data by selecting


52/97



Set the NE to operation

Switch NE to the Operation state by selecting

The NE specific data are uploaded to the element manager


53/97



Set Alarm severity threshold

By selecting the Warning option, you will ensure that all alarms will be displayed Set the alarm severity threshold and the toolbar display by selecting < Settings>


54/97



Configure Modules

If Empty-Auto is selected, it is not necessary to configure the traffic interface modules, as the NE willautomatically configure the module when the module is plugged in

To configure the modules (cards) manually select in the sub rack view:


55/97



Configure DCC channels

Configuring the DCC channels is a precondition for inter-element communication

Configure the DCC channels by selecting

H d / S f I ll i


56/97



Configure Synchronization

In according to the planning data configure the external clock sources available. The NE will run on Free Runningmode until there is no high quality clock available to connect to

Configure the synchronization selecting

H d / S ft I t ll ti


57/97



Configure Module features

The card user label is intended for entering network specific information about the card. Cofigure the modulefeatures by selection



58/97



Configure Traffic flow features

Depending on the selected module (card) and traffic flow symbol, various supervision parameters related to thatcard can be configured

Configure traffic flow features by selecting



59/97



Perform Back up of NE database

The procedure to create VCDB backup will be covered in the nextsection


60/97

Operation and Maintenance



61/97

Ope a o a d a e a ceRoutine Maintenance

(Equipment Configuration Database back)

One of the most important tasks in routine Maintenance of HiT is backup ofequipment configuration database known as VCDB

VCDB contains all the configurations including cross connection information

To backup VCDB go to



62/97

Operation and MaintenanceRoutine Maintenance

(Cleaning of fan module and dust filter)

Cleaning of fan modules and accompanying dust at regular intervals is another must

in routine maintenance

In hiT 7070 there are two fan modules (with dust filters) one at the top and one at the

bottom of the rack

In hiT 7060 there is one fan module at the bottom of the chassis. The fan working

status is indicated at the interface panel. Each fan assembly is replaceable when the

system is in service

In hiT 7035 also there is one fan module at the bottom of the chassis. The fan

working status is indicated at the interface panel. Each fan assembly is replaceable

when the system is in service


63/97

Operation and MaintenanceUnderstanding alarm generation and alarm handling

Basic Information: The failures and the failure processing are differentiated in two failure classes: transmission

failures and equipment failures Failures are reported via the QST management interface to the OS and may also

lead to alarm indications at the TNMS

Any alarm message (raised alarm or cleared alarm) is saved in an alarm log in

order to provide an alarm history. Furthermore a list of current alarms is kept for

every NE and is updated according to changes reported by the respective NE


64/97


SDH Alarm Scheme:

Large numbers of alarm and error messages are an integral part of SDH

networks. In SDH, these are referred to as defects and anomalies, respectively.

They are coupled to network sections and the corresponding overhead

information

Complete failure of a circuit results, for example, in a LOS alarm (loss of signal)

in the receiving network element. This alarm triggers a complete chain ofsubsequent messages in the form of AIS (alarm indication signals). The

transmitting side is informed of the failure by the return of an RDI alarm (remote

defect indication)

The alarm messages are transmitted in fixed bytes in the SOH or POH. For

example, byte G1 is used for the HP-RDI alarm

If the received signal contains bit errors, the sensor indicates BIP errors. Sincethis is not the same as a complete failure of the circuit, the alarm here is referred

to as an anomaly that is indicated back in the direction of transmission. The

return message is called a REI (remote error indication)


65/97


O


66/97


The following diagram attempts to show the Alarms raised, their subsequent actions,destinations in the forward and backward directions

O ti d M i t


67/97


Alarm handling

The steps involved in the basic alarm handling are shown below

O ti d M i t


68/97


Alarm handling

Initial Step: check LEDs The initial approach to fault f inding is to observe LED indications. This will help you to determine where the

fault might be quickly. The observation of these LED's can be done without the need to connect a TNMS CT

O ti d M i t


69/97


Alarm handling

Next step: log in with TNMS CT When one has reached the "Fault" option you can select either

"Equipment Alarms" (or "Communication Alarms") "Acknowledge"

O ti d M i t


70/97


Alarm handling

Next step: embedded online help Clicking "F1" button on the keyboard or via main menu bar "Online Help" the page "Alarm

Names, Severities and Remedial Actions" containing Remedial Action needs to beopened

O ti d M i t


71/97

Operation and MaintenancePerformance Analysis

Specific bytes in the individual overheads are provided for bit errormonitoring and fault localization. These bytes contain information indicatingthe bit error rate and thus the quality of the transmission sections concerned



72/97


(Performance Monitoring Sections)

Following are the Performance monitoring Sections of SDH Regenerator Section

Multiplex Section



73/97


(Performance Monitoring Sections)

Regenerator Section: B1 in RSOH One BIP-8 code word (1 byte) is provided for bit error monitoring. This code word is

generated over all bits in the STM-N frame after scrambling. The BIP-8 byte is subsequentlyinserted in the allocated position B1 of the RSOH in the next frame before scrambling starts.this byte is evaluated and regenerated in every multiplexer and regenerator

Multiplexer Section: B2 in the MSOH A BIP-N x 24 code word (N x 3 bytes) is provided for error monitoring on the individual

multiplexer sections. This BIP-N x 24 code cord is generated prior to scrambling over theentire STM-N frame, but not on the first 3 rows of the SOH. The N x 3-byte BIP-N24 x 24

code word is inserted prior to scrambling in the N x 3 bytes B2 provided for this purpose inthe MSOH of the next frame. These B2 bytes are not modified in the regenerator



74/97


(Error Second Ration)

111 2 2

43 4

2 3

ESR=(4+2)/10=60%

When one or more error code sets occur in any second, this second is called an error

second (ES), In a specific measuring time period, ratio between the occurring ES to the

total available seconds is called ESR

Error

code

block

NO SES NO SES SEScorrect

code

block



75/97

Ope a o a d a e a cePerformance Analysis

(Severely Error Second Ration)

111 2 2

43 4

2 3

SESR=2/10=20%

When no less than 30% of EB or at least one severe disturbance period (SDP) occurs

within any second, then this second is called a severely error second (SES).

Within a specified measuring time, the ratio between the SES to the total available seconds

is called the severely error second ratio (SESR).

Error

code

block

NOT ES NOT SES SEScorrect

code

block



76/97

pPerformance Analysis

(Background Block Error Second Ration)

111 2 2

43 4

2 3

BBER=8/(10*8)=10%

Except the EB(error block) that occurs during SES and UAS , all the other error blocks are

called the background block error (BBE). Within a specified measuring time, the ratio o

BBE to the total blocks which has already deduct the blocks of SES and UAS is called

BBER

Error

code

block

NOT ES NOT SES SEScorrect

code

block



77/97

pPerformance Analysis

(Unavailable Second)

when continuous 10 seconds are SES ,the UAS begin. (the ten seconds are

included)

when there is not SES within continuous 10 seconds ,the UAS ends .(the ten

seconds are included in AS)

32 5 7 10 111 4 6 8 9

UAS

Error

code

block

SES

correct

code

block



78/97

Operation and MaintenanceCreation of services

Switching signals between different interface modules requires that cross-connections to be configured. These connections are initiated by software command

and allow easy configuration, reconfiguration or deletion

The number of cross-connections that can be set depends on the switching capacity

of the NE. hiT 7070 SC has the switching capacity of 704 x 704 STM-1 equivalents

HO granularity (VC-4)

Generally, cross-connections can be created between: line interface and line interface.

line interface and tributary interface.

tributary interface and tributary interface.



79/97




80/97


The through-connections are established with the aid of "Termination Points" TP.Each termination point characterizes the source TP A or the sink TP B of theconnection. There are four different types of cross-connections that can be set up:

Unidirectional cross-connections:

In a unidirectional cross-connection, unidirectional termination points are linked together

Bi-directional cross-connections:

In a bi-directional cross-connection, bi-directional termination points are linked together

Loop back cross-connection:

In a loop back cross-connection, the source and the sink of the termination point are linked in a loop

Broadcast cross-connection:

A broadcast cross-connection is a special arrangement of a number of unidirectional cross-connections that have the same "source" termination point. Broadcast cross-connections are onlypossible without protection



81/97




82/97


Getting the list of Cross connections

In addition to the list of the CC a graphical presentation of the existing CC's can beobtained by selecting from the NE "Main" window: "Cross Connections" -> "Graphic...". Or press Graphic Button on the CC List window



83/97


Getting list of CC



84/97


Creating Cross connections



85/97


Creating Cross connections



86/97


Deleting cross connection



87/97


Deleting cross connection



88/97

Operation and MaintenanceTesting / Trouble shooting



89/97

Operation and MaintenanceCard Replacement

Before replacing any suspect module, try to reactivate the system by means ofa hardware reset (e. g. pulling and re-inserting the module, however, do notattempt this if the red fault LED on the module is lit

When replacing modules, you must comply with the safety regulations When replacing a module, it is essential to check and record the optical and

the electrical transmitting power, using an optical or electrical power meterrespectively, before the modules are returned to service.

The module setup procedure can only commence once the module hasbeen correctly inserted into the slot, as far as the stop, and then locked.

Modules can be removed from or plugged into the sub-rack while they arelive.

After a module has been replaced, the module status must be checked

using the LCT/NCT. As the modules are pulled out or plugged in, spontaneous error messages

and error messages can suppressed if the complete network element or themodule to be replaced is configured in the Maintenance operating mode:"NE State... -> Set to Maintenance"



90/97

Card Replacement

(SCOH)

The new SCOH module must contain the same APS (Application ProgramSystem) as the replaced module; otherwise there can be uncontrolled APSchangeover with a variety of consequences, which may even include trafficinterruptions

The HW/SW compatibility numbers of the new and the replaced module must be

identical or the APS currently active must support both the old and the newcompatibility number

1) Remove the faulty SCOH module from the sub-rack.

2) Pull out the MMC card from the faulty SCOH module (placed at the front panel ofthe SCOH)

3) Insert the MMC card to the new SCOH module

4) Plug in new SCOH module with the inserted MMC card to the sub-rack. After theSCOH module is plugged in, it begins its startup sequence and accepts the lastvalid NE configuration data (VCDB) from the MMC card

5) Connect TNMS CT to the NE and prove that NE is "Active" and in "Operation"mode.


91/97

Hardware / Software Upgrade


92/97

Hardware / Software UpgradeInstallation of new card



93/97


For each SDH or Ethernet cards port provisioning or certain protection features, e.g. the operator may configureMSP. For optical modules equipped with SFP modules provisioning is necessary to put the SFP module in tooperation.

Port can be configured as: Empty Empty-Auto Working

If the port is configured in "Empty-Auto" mode it will change its own status automatically to "Working" after theSFP module has been inserted. If a physically equipped with SFP module port is configured as "Empty", thecorresponding module is taken out of service. If the actual configuration and the software configuration do not

match, the latter is displayed but the port starts flashing in red (with a blue edge) because an "unavailable" erroroccurs. To provision a port, the following procedure shall be performed:



94/97



95/97




96/97

pg

HiT Software Upgrade

All HiT7070 V2.1 will go into 2 steps, First upgrade of V2.1 to V3.0 and then V3.0 toV3.2.2. This means the procedure will be repeated the same way as the first one andthe time duration of the activity will be twice the total time used in first step.

All HiT7070 V3.0 will be done only in one step, Upgrade from V3.0 to V3.2.2.

The first is to deactivate the Network Element from TNMS-Core that needs to be

upgraded. (Duration: 2 minutes)Reason: NE needs to be deactivated in order to give the full access to the personnel that willconduct the upgrade. Deactivation is needed to restrict other personnel on accessing theHiT7070 during the procedure

Deactivation of the IF2M Card Protection on HiT7070 sub rack and micro shelf.(Duration: 10 minutes).

Reason: Deactivation of IF2M Card Protection is needed in order to upgrade all IF2M modulesin each slots. Modules should be available without protection scheme

Upload the Current NE-VCDB. (Duration: 15 minutes).Reason: Backup of NE database is needed after swapping of the APS Software. Upload is

must procedure when you are doing any activity in the system.



97/97

pg

HiT Software Upgrade

4. Download of APS Software to the NE. (Duration: 20 minutes)Reason: Downloading of APS software is needed to load the latest software of theHiT7070 in the Inactive APS at the Software Management.

5. Swap the Active and Inactive APS Software. (Duration: 10 minutes)Reason: Swapping of APS is needed in order to replaced the old APS by the new APS in

the Active Side of Software Management.

6. After swapping of APS software the NE will go into IDLE and

Maintenance State. Verify/Check the APS software in the active side ifthat is the new version. Then afterwards, download the NE-VCDB thatyou save from the step #3. (Duration: 15 minutes)

Reason: Downloading of the database is needed in order to restore the completeconfiguration of the HiT7070.

7. Set NE from IDLE to Active State. (Duration: 2 minutes per card)Reason: SCOH will reset/reboot for the activation process. Setting the HiT7070 into

active state will initiate to activate and upgrade all modules present in the sub rack.

Sporadic bit errors will occur on all IF2M, 2 minutes intermittent bit error will occurper module of IF2M.

Duration of procedure is dependent on the number of cards available in eachHiT7070, all HIT7070 with micro shelf will need additional time onuploading and downloading process.

hit training presentation2

Documents