HiT Training Presentation-2

Siemens hiT 70 series training
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
Basic units of SDH Multiplexer
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
General Description of hiT 7070 /
hiT 7060 / hiT 7035
General Description of HiT 7070 / HiT 7060 / HiT 7035
Siemens new range of equipment that makes the

promise 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 with
the inherent reliability of SDH. Multiple network elements
are integrated and consolidated into a single compact
unit. The efficiency of this approach, together with
extensive use of highly integrated components allows the
SURPASS hiT 70 series to be offered at lower costs
than current solutions.
Data + Voice = SURPASS hiT 70 series

(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
(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
(Enabling Technologies/ Virtual Concatenation)
• In order to transport payloads exceeding the payload capacity of the

standard set of Virtual Container Group (VC-group), Virtual
Concatenation was defined. There are two types of concatenations
defined in ITU standards: contiguous concatenation and virtual
concatenation
• Contiguous concatenation was conceived to accommodate high-
speed data applications that use protocols such as ATM. The ITU
defined contiguously concatenated containers only support certain
rates including: STM-4c, STM-16c and STM-64c
• The basic idea of Virtual concatenation (VC) is to create a finer
granularity of payloads than contiguous concatenation can offer.
Carriers can map any arbitrary bandwidth to a corresponding and
appropriate number of VC-12 or VC-3 or VC-4 channels. The benefit
of VC is that little bandwidth is wasted and carriers now have a more
efficient scenario for carrying data over the SDH/SONET network
(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 system
to alter the pipe capacity do not impair the user’s traffic
(Enabling Technologies/ LCAS)
• Layer 2 Ethernet functions implemented in the system typically

include 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 provide
Layer 2 traffic resiliency mechanism
4. Rate limiting function at per port or per VLAN basis, the maximum
allowable 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
(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 colored
interface, 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
(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
(hiT 7060 Overview)
• SURPASS hiT 7060 employs an innovative dual TDM/Data plane design,

with large SONET/SDH high-order cross-connect capacity (70G) and
substantial low-order cross connect (5G) capacity. This feature enables
dynamic 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 interfaces
including 10/100M FE/FX, GE, and ATM. The system supports IP/Ethernet,
Layer 2 switching, RPR, and ATM PVC switching functions, providing highly
efficient data transport
• SURPASS hiT 7060 supports a wide range of SONET/SDH/PDH interfaces
from high speed optical interfaces OC-48/STM-16 to optical/electrical
interfaces of OC-3/STM-1, DS3/E3, 1.5Mb/s, and 2Mb/s. It provides a full
suite 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)
(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 no
single 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
Functionality of Modules
(hiT 7070)
(hiT 7070)
(hiT 7060)
(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 (96×96 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
(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)
Hardware / Software Installation
(Card Installation HiT 7070)
• 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
(TNMS-CT and OSI stack)
• Depending on the needs, two different modes are available for

TNMS CT.
• LCT Mode:
– The Local Craft Terminal (LCT) is used for local management and
commissioning of network elements. The MSN Manager, organizational
relationships between network elements in the network and network
alarms are not available for the LCT. The LCT can communicate with a
maximum of 150 network elements. Up to three element managers may
be 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, the
monitoring of all the alarms reported from each accessible network
element is allowed. The NCT can communicate with a maximum of 150
network elements (including alarm monitoring). Up to 50 element
managers or up to five MSN Managers may be open at the same time
only.
• The TNMS CT specific software package allows the creation of a graphical

representation of the network such as a geographical arrangement of the NE symbols
as 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 mouse
and/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 selectable
via pull-down menu-titles.
• Menu titles and menu options, which are frequently used, can also be selected via
function keys.
• The operator is guided through the program by menus. One has no need to learn
complex command syntax. Furthermore the program offers mechanisms as filtering
or sorting of information and offers support through help functions.
• Starting TNMS-CT server
– TNMS CT Server is started automatically on system startup,
before any user is logged on. Once it has been started, a
connection to all configured and activated network elements is
established and their data is uploaded. An icon is displayed in
the Windows 2000 taskbar. Once the Server has started, it is
always active. Moreover, terminating the Client does not result in
stopping 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
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
The TNMS CT GUI gives access to all functions for supervision, operation, configuration and maintenance of the
network. The set of functions available to each individual operator depending on the operator’s user class which is
defined by the administrator. Via the TNMS CT GUI you can also start the element manager applications (e.g. the
EM 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 of
these 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 these
buttons with the left mouse button provides quick and particularly easy access to certain frequently used
functions.
3. Status bar:
The status bar runs along the bottom of the main window. It gives information on the operating states and
displays 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 can
be improved by using a background bitmap. For example, you can attach the picture of a city map to be
displayed in the background of the network plan and position your network elements in this map according
to 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
(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 V2
Serial
– Line Channel and click the Properties button.
– Make the settings according to figure given below
(TNMS-CT setup)
• 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
(TNMS-CT setup)
• The default password is NEPASSWORD

(TNMS-CT setup)
• In QST tab set the NSAP/IP address

(TNMS-CT setup)
OSI stack setting
• Open the OSI Stack Configuration window using the Start menu: Start -> Settings -> Control
Panel -> OSI Stack icon.
• In the OSI Stack Configuration window, make the settings according to figure below
• After this connect NE
(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 entries
and click the Properties button.
• Make the settings according to figure below
(TNMS-CT setup)
• User Name: NMS for NCT and LCT for LCT

• The default password is NEPASSWORD
(TNMS-CT setup)
• 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
(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)
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
<Security><Request Write Access>
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 <Security><Change Password>
Enter Location and Name
• The NE Name must be entered before you can set the hiT to ACTIVE STATE. Enter NE name, location and
application type by selecting <Module View><NE/ Subrack><Configuration><Network Element>
Activate the NE
• Activate the NE by selecting <NE State><Set to Active>

• 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 default
name
• After reboot login NE again and prove NE state
Set the NE time and date
• Set NE Date and Time by selecting <Module View> <NE/ Sub rack>
• The internal clock of the operating system controls date and time. The network element time is configured with an
offset relative to GMT
Set MCF stack parameters
• The NSAP address (Network Service Access Point) must be specified before hand on the basis of a network plan
so 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
Enter the Sub rack data
• Specific customer identification data can be entered for the sub rack. Enter sub rack data by selecting <Module
View><NE / Sub rack><Configuration><Sub rack> <Customer Specific>
Set the NE to operation
• Switch NE to the “Operation” state by selecting <NE state> <Set to Operation>

• The NE specific data are uploaded to the element manager
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 <Options> < Settings>
Configure Modules
• If Empty-Auto is selected, it is not necessary to configure the traffic interface modules, as the NE will
automatically configure the module when the module is plugged in
• To configure the modules (cards) manually select in the sub rack view: <Module View><[slot number]>
Configure DCC channels
• Configuring the DCC channels is a precondition for inter-element communication

• Configure the DCC channels by selecting <Module View> <SCOH> <Configuration>
<MCF><DCC><Configuration>
Configure Synchronization
• In according to the planning data configure the external clock sources available. The NE will run on Free Running
mode until there is no high quality clock available to connect to
• Configure the synchronization selecting <Module View> <NE / Sub rack> <SEC>
Configure Module features
• The card user label is intended for entering network specific information about the card. Cofigure the module
features by selection <Module View><[Module name]><Configuration><Card>
Configure Traffic flow features
• Depending on the selected module (card) and traffic flow symbol, various supervision parameters related to that
card can be configured
• Configure traffic flow features by selecting <Module View><[interface module name]><[symbol in the port
list]><Subview><[traffic flow symbol]><configuration>
Perform Back up of NE database
• The procedure to create VCDB backup will be covered in the next

section
Operation and Maintenance
Routine Maintenance
(Equipment Configuration Database back)
• One of the most important tasks in routine Maintenance of HiT is backup of
equipment configuration database known as VCDB
• VCDB contains all the configurations including cross connection information
• To backup VCDB go to <Module View><NE / Sub rack><Config DB Management>
Routine 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
Understanding 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
• 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 of
subsequent 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. Since
this 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)
• The following diagram attempts to show the Alarms raised, their subsequent actions,
destinations in the forward and backward directions
Alarm handling
• The steps involved in the basic alarm handling are shown below
Alarm handling
• Initial Step: check LEDs

– The initial approach to fault finding 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
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"
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 be
opened
Performance Analysis
• Specific bytes in the individual overheads are provided for bit error
monitoring and fault localization. These bytes contain information indicating
the bit error rate and thus the quality of the transmission sections concerned
(Performance Monitoring Sections)
• Following are the Performance monitoring Sections of SDH
– Regenerator Section
– Multiplex Section
(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 subsequently
inserted 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 the
entire 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 in
the MSOH of the next frame. These B2 bytes are not modified in the regenerator
(Error Second Ration)
•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
ESR=(4+2)/10=60%
1 2 3 4
1 1 2 2 3 4
correct Error NO SES NO SES SES

code code
block block
(Severely Error Second Ration)
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).
SESR=2/10=20%
1 2 3 4
1 1 2 2 3 4
correct Error NOT ES NOT SES SES

code code
block block
(Background Block Error Second Ration)
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 of
BBE to the total blocks which has already deduct the blocks of SES and UAS is called
BBER 。
BBER=8/(10*8)=10%
1 2 3 4
1 1 2 2 3 4
correct Error NOT ES NOT SES SES

code code
block block
(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)
1 2 3 4 5 6 7 8 9 10 11
UAS
correct Error
code code SES
block block
Creation 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.
• 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 the
connection. 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 only
possible without protection
Getting the list of Cross connections
• In addition to the list of the CC a graphical presentation of the existing CC's can be
obtained by selecting from the NE "Main" window:
– "Cross Connections" -> "Graphic...".
– Or press “Graphic” Button on the CC List window
Getting list of CC
Creating Cross connections
Creating Cross connections
Deleting cross connection
Deleting cross connection
Testing / Trouble shooting
Card Replacement
Before replacing any suspect module, try to reactivate the system by means of
a hardware reset (e. g. pulling and re-inserting the module, however, do not
attempt 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 meter
respectively, before the modules are returned to service.
• The module setup procedure can only commence once the module has
been 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 are
live.
• 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 the
module to be replaced is configured in the “Maintenance” operating mode:
"NE State... -> Set to Maintenance"
Card Replacement
(SCOH)
• The new SCOH module must contain the same APS (Application Program
System) as the replaced module; otherwise there can be uncontrolled APS
changeover with a variety of consequences, which may even include traffic
interruptions
• 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 new
compatibility 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 of
the 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 the
SCOH module is plugged in, it begins its startup sequence and accepts the last
valid 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.
Hardware / Software Upgrade
Installation of new card
• For each slot a pop-up menu with the appropriate module types (the
possible equipping) can be called up by clicking on the slot number
with the right mouse button (RMB).
• To configure a slot, choose a module from this pop-up menu. The
new data is then immediately included in the actual equipping of the
network element. If the slot is configured in "Empty-Auto" mode
(default settings) then the type of the card is defined and card is
configured automatically after the card will be inserted. If a
physically equipped slot is configured empty, the corresponding
module is taken out of service. If the actual configuration and the
software configuration don't match, the latter is displayed but the
module starts flashing in red (with a blue edge) because an
"unavailable" error occurs
• For each SDH or Ethernet cards port provisioning or certain protection features, e.g. the operator may configure
MSP. For optical modules equipped with SFP modules provisioning is necessary to put the SFP module in to
operation.
• 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 the
SFP module has been inserted. If a physically equipped with SFP module port is configured as "Empty", the
corresponding 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" error
occurs.
• To provision a port, the following procedure shall be performed:
HiT Software Upgrade
All HiT7070 V2.1 will go into 2 steps, First upgrade of V2.1 to V3.0 and then V3.0 to
V3.2.2. This means the procedure will be repeated the same way as the first one and
the 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 will
conduct the upgrade. Deactivation is needed to restrict other personnel on accessing the
HiT7070 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 modules
in 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.
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 the
HiT7070 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 if
that is the new version. Then afterwards, download the NE-VCDB that
you save from the step #3. (Duration: 15 minutes)
Reason: Downloading of the database is needed in order to restore the complete
configuration 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 occur
per module of IF2M.
Duration of procedure is dependent on the number of cards available in each
HiT7070, all HIT7070 with micro shelf will need additional time on
uploading and downloading process.

HiT Training Presentation-2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HiT Training Presentation-2

Uploaded by

Copyright:

Available Formats

Siemens hiT 70 series training

Siemens new range of equipment that makes the

Data + Voice = SURPASS hiT 70 series

Following are the key enabling technologies for SURPASS hiT 70

1) Generic Framing Procedure (GFP)

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

• In order to transport payloads exceeding the payload capacity of the

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

• Layer 2 Ethernet functions implemented in the system typically

• SURPASS hiT 7060 employs an innovative dual TDM/Data plane design,

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

• The slots 307 and 308 are dedicated for:

• Depending on the needs, two different modes are available for

• The TNMS CT specific software package allows the creation of a graphical

The TNMS Client user interface consists of the following parts:

– In the TNMS CT, click the DCN Mgm button.

• The default password is NEPASSWORD

• In QST tab set the NSAP/IP address

• In the TNMS CT, click the DCN Mgm button.

• User Name: NMS for NCT and LCT for LCT

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

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

• Activate the NE by selecting <NE State><Set to Active>

• Switch NE to the “Operation” state by selecting <NE state> <Set to Operation>

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

• The procedure to create VCDB backup will be covered in the next

• SDH Alarm Scheme:

• Initial Step: check LEDs

• Next step: log in with TNMS CT

• Next step: embedded online help

• Regenerator Section: B1 in RSOH

correct Error NO SES NO SES SES

correct Error NOT ES NOT SES SES

correct Error NOT ES NOT SES SES

• Switching signals between different interface modules requires that cross-

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

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

– Loop back cross-connection:

• A broadcast cross-connection is a special arrangement of a number of unidirectional cross-

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

• Upload the Current NE-VCDB. (Duration: 15 minutes).

You might also like