08 Tr3272eu00tr 0302 MCF Configuration

MCF configuration Siemens
TR3272EU00TR_0302
2003 Siemens AG
1
Contents
1 Introduction to DCN (Data Communication Network) 3
1.1 General 4
1.2 NSAP structure 6
1.3 Routing basics 8
2 Management interfaces and supported stack profiles 10
3 Configuration of message communication function 13
3.1 MCF function group 14
4 Overhead access 25
4.1 General information 26
4.2 Overhead Cross-Connection function OHCC 30
4.3 Engineering order wire 38
5 Exercises 50
6 Solution 60

MCF configuration
Siemens MCF configuration

TR3272EU00TR_0302
2003 Siemens AG
2

TR3272EU00TR_0302
2003 Siemens AG
3
1 Introduction to DCN (Data Communication
Network)

I am Louis
I am Peter
I am Elena
I am Tom

Fig. 1


TR3272EU00TR_0302
2003 Siemens AG
4

1.1 General
Network Management is the general term used to define a process by which one or
more management system, can control and manage equipment in the network.
The Data Communication Network (DCN) provides facilities and connections
between all components of a Telecommunications Management Network.
A basic requirement of the DCN is to provide a path that can deliver all control or
management messages from management system to the managed equipment and
reports or requested data from managed equipment to the management system.
An SDH network is constructed so that the hardware meets the requirements of the
traffic network (the payload). The resulting topology need not necessarily match the
requirements of the DCN network. For the DCN network, each SDH network element
must be accessible from a central point.
The following network elements are directly accessible:
All network elements in the station where the central supervision system is
located.
All SDH systems connected via STM-N connection(s) with each other and at
least one of these SDH systems acts as Gateway Network Element.
Network elements that do not meet any of the conditions listed above can be
connected via Embedded LAN.

The available DCN connections used in SDH networks are in general as follows:
Data Communication Channels (DCC) in SDH Section Overhead, DCCR
(192Kbit/s) and DCCM (576Kbit/s).
Local Area Network (LAN) based on carrier sense multiple access/collision
detect (CSMA/CD) protocol.
Wide Area Network (WAN), for example, SDH payload traffic via tributary of a
SDH Add/Drop Multiplex with 2Mbit/s interface.

A DCN is usually designed to be resilient against failure of any single link or item of
equipment in a network. To provide such resilience, it is necessary that there are at
least two physically separate routes between entities that need to communicate with
one another.


TR3272EU00TR_0302
2003 Siemens AG
5

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Bridge
STM-16
STM-1
STM-1
STM-16 STM-1
Bridge
Leased Lines or
SDH Payload
as WAN connection
Central Station
TNMS C or TNMS CT
Server
Central Station LAN
GNE
TNMS C or
TNMS CT
Client
Extended LAN
GNE
Remote Station
Embedded LAN
GNEs
STM-1
STM-1
DCN connections
over DCCR/M Channels

Fig. 2 DCN Connections


TR3272EU00TR_0302
2003 Siemens AG
6

1.2 NSAP structure
An NSAP (Network Service Access Point) address must be defined for each network
element. The NSAP address is used as NE identifier in the manageable network. It
must be unique worldwide.
An NSAP address has a maximum length of 20 Bytes (40 characters) and generally
consists of 2 parts: the Network-specific part and the Network Element specific part.
The first byte of the NSAP address is the Authority and Format Identifier (AFI). The
AFI indicates the format and coding applicable to NSAPs. There are a number of
formats which are supported, such as:

AFI Recommendation
37 Address as per CCITT X.121.
53 Address as per CCITT X.121.
39 Address as per ISO 3166/DCC.
47 Address as per ISO 6523/ICD.
49 Local addresses (private).

Since Siemens is registered with the British Standard Institute as the operating
company / administrator of an international data network (ISO 6523 ICD, AFI - 47),
Siemens has its own ICD (0099). Unless the customer has its own address format,
this is the standard procedure for assigning NSAP addresses. The precise structure
of the HODSP is defined in a separate paper Numbering Scheme for Siemens
Supervisory Network, together with the specifications as to which address bytes are
required for which purposes.
ICD: International Code Designator.
HODSP: High Order Domain Specific Part defined by administrative core.
DID: Domain ID defined by network authority.
SID: System Identifier defined by network authority.
SEL: NSAP Selector.


TR3272EU00TR_0302
2003 Siemens AG
7

AFI IDI HO-DSP Domain System ID
NSAP
SEL
Network-specific part Network Element specific part
1 Octet 2-7 Octets 0 -5 Octets 1-9 Octets 1-9 Octets 1Octet
NSAP Maximum Total Length = 20 Octets

Fig. 3 NSAP Structure
AFI Code Design. HODSP Domain SID SEL
47 2 Bytes 0-5 Bytes 1-9 Bytes 1-9 Bytes 1 Byte
3 Bytes fixed max. 16 Bytes
e.g.
IDP DSP
AFI IDI
AFI ISO ICD
Format
HODSP Domain ID System ID NSAP
Selector
47 0099 008000000 000000F101 0800061F7BF4 01
ISO 6523-ICD

Fig. 4 Example of ISO 6523-ICD NSAP address


TR3272EU00TR_0302
2003 Siemens AG
8

1.3 Routing basics
In Data Communication Network hiT 70xx series network elements function as IS-IS
routers. They support Level 1 and Level 2 routing.
IS-IS is a dynamic routing protocol; it uses information gathered from the network to
form routing tables, which are used to perform routing decisions. IS-IS allows for a
two-stage hierarchy within the routing domain, the Level-1 sub-domain and the Level-
2 sub-domain. The Level-2 sub-domain consists of all Level-2 IS-IS routers; the
Level-1 sub-domain consists of multiple sub-domains of Level-1 routers, each sub-
domain possessing a discrete address prefix (AREA). IS-IS uses the concept of link
metrics when assessing the optimal route through a network. The assessment
process sums the metrics associated with the proposed links to workout the metric
sum for the overall route.
Each network element knows the entire topology of the network. This enables each
network element to send a message to the recipient or to know via which neighbor
network element the recipient can be reached. The SDH Systems using OSI routing
algorithm generate their dynamic routing tables automatically. There will be a primary
route and a secondary route calculated and changed by SDH systems.
Routing Domain
The routing domain is a group of NEs that use the same routing procedure. All
the devices of a network can form a single common routing domain if all devices
use the same routing method. Devices with different routing methods (this
includes; dynamic IS-IS routing, IS-IS broadcast routing and static routing) must
be assigned to different routing domains. Static routing information, in the form
of a Reachable Address Prefix (RAP) is required to connect routing domains
with different routing methods.
Sub Domain
A sub domain is a sub-network of IS using a common routing method. For level
1 routing, a level 1 sub-domain consists of all IS in the routing area. This type of
sub domain is therefore a subgroup of the routing area. For level 2 routing, a
level 2 sub-domain consists of all related level 2 IS within a routing domain.
Level 1 Intermediate Systems
These systems route directly to systems within their own area. For destinations
outside their own area they route towards the nearest level 2 Intermediate
system. These systems use the System ID part of the NSAP to route the
packets.
Level 2 Intermediate Systems
Level 2 systems route towards a different routing area, or another routing
domain. These systems use the first part of the NSAP address to route the
packets. These systems also act as Level 1 intermediate systems within their
own routing area.


TR3272EU00TR_0302
2003 Siemens AG
9

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TNMS CT
STM-16
STM-1
STM-16 STM-1
GNE
Embedded LAN
STM-1
STM-16 STM-1
STM-16
Other Routing
Domain
Routing Domain
Level 2
Subdomain
Level 1
Subdomain
Level 1
Subdomain
L1 IS
L1 IS
L1 IS
L1 IS
L1 IS
L1 IS
L1 IS
L1 IS
L1 IS
L1 IS
L1 IS
L1 IS
L1/L2 IS
L1/L2 IS
L1/L2 IS
L1/L2 IS
RAP RAP
Area part of NSAP:
470099002760000c0000000040
Area part of NSAP:
470099002760000c0000000060

Fig. 5 Routing Domain


TR3272EU00TR_0302
2003 Siemens AG
10

2 Management interfaces and supported
stack profiles
Supported Management Interfaces
The SURPASS hiT 70 series offers a rich set of element management interfaces for
local and remote access using different stack profiles:
LCT on local F-interface
LCT over Q-interface
NCT over Q-interface
TNMS-C over Q-interface
Supported Stack Profiles
The SURPASS hiT 70xx series provides physical access (Layer 1) to the
management functionality via 3 different types of interfaces:
DCC channels:
hiT 7070: 30 DCC channels embedded in the SDH overhead (DCCM, DCCR,
HCOC3, HCOC9, F2-Byte)
hiT 7050: 4 DCC channels embedded in the SDH overhead (DCCM, DCCR,
HCOC3, F2-Byte)
WARNING
The SDH drawers O155-2 and O622-2 do not support the F2 and the HCOC3
byte termination due to hardware constraint.
Ethernet Interface(s):
hiT 7070: Three external Ethernet interfaces (Q_EXT, Q_F2 and Q) connected
by an internal switch to one internal SCOH Ethernet interface
hiT 7050: One external Ethernet interface (Q)
Serial Interface:
One Serial RS232 interface (F)
The SURPASS hiT 70xx series supports two different and independent acting
protocol stacks:
An OSI stack including TP0, TP4, CLNS, ES-IS, IS-IS, LAPD and LLC1
managed with QST, which is able to interact with already deployed Siemens
stack implementations
A TCP/IP stack including TCP, UDP, IP, OSPF, PPP and Ethernet framing
defined in RFC894 managed with SNMP


TR3272EU00TR_0302
2003 Siemens AG
11

Part of
Linux Kernel
ZebOS OSPF
daemon
Part of BASW
TP4
Layer 5..7
Layer 4
Layer 3
Layer 2
Layer 1
OSPF
Routing
protocol
Marben Stack
Part of ASW
SNMP/QST
wrapper
SNMP
master
agent
OSPF
subagent
IP MIB2
subagent
Telnet
server
Enterprise
subagent
CIF
(QST agent)
Hardware
Part of BASW
hiT 70xx protocol stack
hiT 70xx protocol stack
UDP TCP
IP
RFC894
RS232
driver
Ethernet
driver
DCC
driver
CLNP ES-IS/IS-IS
LAPD LLC1
TP0
RFC1006
PPP
Multiplexer
Q, Q_F2, Q_EXT F DCCR, DCCM, F2, HCOC3, HCOC9

Fig. 6 hiT 70xx protocol stack
Accessible parts of functionality
Application
Protocol
(Layer 57)
Transport
Protocol
(Layer 4)
Network
Protocol
(Layer 3)
Data link Protocol
(Layer 2)
LCT F-interface
All functionality specified in QST
including SNMP over QST for
management of IP and OSPF functionality
QST
TP0 over
TCP (RFC
1006)
IP
- PPP over RS232
using predefined
IP addresses
LCT Q-interface, NCT,
TNMS-C and other
management systems
supporting the QST
interface
QST TP4 CLNS
- LAPD over DCC
- LLC1 over
Ethernet
IP based management
applications
QST
TP0 over
TCP (RFC
1006)
IP
- PPP over DCC
- RFC894
Combinations of Management Interfaces and Stack Profiles
Combinations of Management Interfaces and Stack Profiles

Fig. 7 Supported Combinations of Management Interfaces and Stack Profiles

TR3272EU00TR_0302
2003 Siemens AG
12


TR3272EU00TR_0302
2003 Siemens AG
13

3 Configuration of message communication
function


TR3272EU00TR_0302
2003 Siemens AG
14

3.1 MCF function group
All required MCF settings could be done via the "Message Communication
Function" window. The general design is the same for hiT7070 and hiT7050 Network
Element types. The window is grouped into five function groups where the actual
settings can be viewed or modified.

Stack Parameters:
Settings for Layer 3, Layer 4 and routing principles of the OSI protocol.
Ethernet:
Settings for Q-Interface (Layer 2) and Reachable Address Prefixes (RAP)
related to the communication over LAN.
DCC:
Settings for DCC and RAP related to the communication over STM-N lines.
CLNS:
This is where the information about collected routing information (Connection
Less Network Service, CLNS) can be obtained.
Transport Connections:
This is where the information about active connections to the remote systems
can be checked.

"Message Communication Functions" window can be opened as follow:
From NE Main window select (RMB) "SCOH" (hiT 7070) or "MFP1" (hiT 7050)
function symbol and from opened Pull Down menu select "Configuration -> MCF".

WARNING
The settings for the MCF parameters on the network elements are specified by
the Network Planning Department. All data in this window should not be
changed after commissioning, unless the DCN topology has been changed. If
in doubt, the default values should be retained.


TR3272EU00TR_0302
2003 Siemens AG
15

Fig. 8 Opening Message Communication window hiT 7070

Fig. 9 Opening Message Communication window hiT 7050 FP1

TR3272EU00TR_0302
2003 Siemens AG
16

3.1.1 Stack parameters
Layer 4 (Transport):
The real propagation time of PDUs within the network has to be less than the
reaction times of the timer values set in layer 4. The layer 4 timer values needs to be
the same for all NEs within the same routing domain.

Window Timer:
Time of inactivity. After the timer will be expired connection will be terminated.
Inactivity means, that neither data nor acknowledge data packets (PDUs) were
received.
Maximum No. of Transmissions:
Specifies how often the PDU will be retransmitted in case the retransmission
timer has been expired.
Retransmission Time:
If a sent PDU is not acknowledged in this time, it will be retransmitted.

Layer 3 (NSAP):
NSAP address of the NE:
The complete NSAP length is divided into a Domain Area Address part and
System ID (SID) part, which are entered separately.

WARNING
The NSAP address must be unique.


TR3272EU00TR_0302
2003 Siemens AG
17

Fig. 10 Stack Parameters window

Layer 3 (CLNS):
CLNS Maximum Lifetime:
Every message data contains a field for message lifetime. This value will be
decreased by the value of 0.5 if passing through the NE or if the NE cannot
transmit the message to the next NE within 0.5s. If the NE receives a message
with the lifetime of 0 the message will be discarded.
Routing Principle:
Level 1 IS. These systems route directly to other systems within their own area
only. For destinations outside their own area they route towards the nearest
level 2 Intermediate system. These systems use the System ID part of the
NSAP to route the packets.
Level 2 IS. Level 2 systems route towards a different routing area, or another
routing domain. These systems use the first part of the NSAP address to route
the packets. These systems also act as Level 1 intermediate systems within
their own routing area.


TR3272EU00TR_0302
2003 Siemens AG
18

3.1.2 Ethernet
This is where the data communication over Ethernet port can be configured or
proved.

Configuration:
These parameters are used for the configuration of the Q-Interface of the NE.
Traffic Mode:
Select the traffic mode according to the planning data (default is OSIIP).
External Domain:
Default value no mean ISIS Routing is enabled. The setting yes disables the
ISIS routing. This might be useful to block ISIS Routing in case if only static
routing over Ethernet connection needs to be used.
L1/L2 Intermediate System Priority:
Priority of the system for being selected as the designated IS on the sub
network.
Level 1/2 Default Metric:
Each output port of an IS gets a metric value in the range 1 63. With the help
of the metrics, the shortest path can be found. All metrics along a path are
cumulative. The PDUs will be sent over the path with the lowest metric. The
max. value in a routing table is 1023, any "longer" routes can not be used.
MAC Ethernet Address:
This is the setup of Layer 2 (LAN-MAC) address. This address is specified by
the Network Planning Department.
MCF Linkage State:
MCF Linkage state is enabled if communication on layer 2 is ok.

Reachable Addresses:
This is where the list of configured Reachable Address Prefixes can be validated.
RAP (Reachable Address Prefix) is used to connect Routing Domain, which does not
support the ISIS routing. On the LAN Reachable Address Prefix (RAP) needs a "Sub-
network Point of Attachment" (SNPA). This is the LAN-MAC address of the
destination system.

WARNING
Every RAP within an NE must be unique and must not be a part of another
RAP.


TR3272EU00TR_0302
2003 Siemens AG
19

Fig. 11 Ethernet Port configuration window

Whit the use of the "Add" or "Modify" buttons, "Ethernet Reachable Address
Add" or "Ethernet Reachable Address Modify" windows can be opened where you
can create a new entry in the reachable address list or modify an existing one.
Address Prefix:
This is where the Reachable Address Prefix can be set up.
Default Metric:
This is the setup of metric value for that interface. With the help of the metrics,
the shortest path can be found.
Default Metric Type:
Possible values: internal or external. If metric type is set to Internal the RAP
metric will be used to calculate the path. Only in case a link with metric-type
Internal is no more available the link with the type External will be used.
SNPA Address:
"Sub-network Point of Attachment" (SNPA) is the LAN-MAC address of the
destination system.

TR3272EU00TR_0302
2003 Siemens AG
20

3.1.3 DCC
This is where the data communication over DCCR, DCCM, F2, HCOC3 or HCOC9
(only for hiT7070) channels can be configured or verified. The settings for this serial
communication channels is similar to the Ethernet settings. If necessary, RAPs may
also be set for communication over DCCR/DCCM/F2 to Routing Domain, which does
not support the ISIS routing, but without SNPA.
DCC List:
In this window, you can create or delete connections between DCC channels and the
DCCM, DCCR, F2, HCOC3 or HCOC9 ports. Up to 30 connections (max. 20 DCCM)
can be set up in case of hiT 7070 or up to 4 connections (max. 2 DDCM) in case of
hiT 7050.
To set up a new connections the following needs to be done:
1. Select (LMB) in the "DCC List" field a free DCC Channel.
2. In the "New DCC Cross Connection" field select "Port Type" (DCCR, DCCM,
F2, HCOC3 or HCOC9) and "Port" (define the SDH port where DCCR, DCCM,
F2, HCOC3 or HCOC9 channel should be used).
3. Confirm settings with the "Connect" button.
If the existing connections needs to be modified:
4. Select (RMB) the connection that needs to be modified.
5. From open Pull Down menu select "Configuration" and "DCC Linkage
Config" window will be opened.
The following parameters can be modified or confirmed in the "MCF DCC Linkage
Configuration" window.
External Domain:
Default value no mean ISIS Routing is enabled. The setting yes disables the
ISIS routing. This might be useful to block ISIS Routing in case if only static
routing over this DCC connection needs to be used.
Level 1/2 Default Metric:
Each output port of an IS gets a metric value in the range 1 63. With the help
of the metrics, the shortest path can be found. All metrics along a path are
cumulative. The PDUs will be sent over the path with the lowest metric. The
max value in a routing table is 1023; any "longer" routes cannot be used.
T200 Time:
This timer is responsible for layer 2 and should be the same for neighboring
Network Elements. If the values are very different the connection will be
unstable.


TR3272EU00TR_0302
2003 Siemens AG
21

1
3
2
5
4

Fig. 12 DCC Configuration window
Traffic Mode
This attribute determines if this DCC channel will be used for OSI traffic, for IP
traffic or for both types of traffic. Possible values are: IP, OSI, OSIIP. Select the
traffic mode according to the planning data.
Interface Type:
Possible values are "User" or "Network". This parameter is used to set master -
slave behavior on DCCR, DCCM, F2, HCOC3 or HCOC9 connections. Both
ends of the connection must have the alternative values (User <-> Network or
Network<->User) otherwise the communication over this DCCR, DCCM, F2,
HCOC3 or HCOC9 connection is not possible.
Line Code:
Displays the NRZ (non return to zero) line code. It cannot be changed.
MCF Linkage State:
MCF Linkage state is enabled if communication on layer 2 is ok.
Reachable Addresses:
Here the list of configured Reachable Address Prefixes can be validated. The
settings for the RAPs are similar to the settings in the Ethernet function group, but
without SNPA.

TR3272EU00TR_0302
2003 Siemens AG
22

3.1.4 Transport connections
This is where the information about active connections to the remote systems can be
verified.

Remote NSAP Address:
This is where the NSAP Address of the connected TNMS CT or TNMS C can be
checked.
Remote T Selector:
T Selector used by the remote manager for this transport connection.
Local T Selector:
T Selector used by this NE for this transport connection.
Connection Type:
Direction of the set-up transport connection. (Outgoing = sent from the local
system, Incoming = sent from the remote system).
Window Timer:
Displays Time of inactivity. After time of inactivity will be expired connection will
be terminated. Inactivity means, that neither data nor acknowledge data packets
(PDUs) were received.
Maximum No. of Transmissions:
Displays how often the PDU will be retransmitted in case the retransmission
timer has been expired.
Retransmission Time:
Displays the time after the PDU is repeated if there is no answer from the
opposite station.


TR3272EU00TR_0302
2003 Siemens AG
23

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 13 Transport Connection information window


TR3272EU00TR_0302
2003 Siemens AG
24

3.1.5 CLNS
By means of this functional group the information about collected routing information
(Connection Less Network Service) CLNS, can be obtained.

The following information from the internal routing tables can be found:
"Adjacencies", direct neighbors over the LAN or DCCR/M links.
"Destination Systems", Level 1 routing information (inside the same area).
"Destination Areas", Level 2 routing information (to other areas).

Fig. 14 Routing information window


TR3272EU00TR_0302
2003 Siemens AG
25

4 Overhead access

TR3272EU00TR_0302
2003 Siemens AG
26

4.1 General information
The following overhead access functions are provided:
Access to SOH and VC-4 F2 POH Overhead bytes and DCC channels of the
STM-n interfaces (SOH #1)
Access to 4 auxiliary external interfaces V.11 / X.21, bidirectional (supported by
hiT 7070 only)
Engineering Order Wire Conference (EOWC), including Ring Manager for ring
operation
2-wire handset for EOW
4-wire E&M interface for EOW (supported by hiT 7070 only)
Cross connect function (switching) of SOH bytes (including transparent DCC
connections) and connect function to MCF, EOWC and Ring Manager.
WARNING
Access to the V.11 / X.21 auxiliary interfaces as well as EOW support requires
additional HW (OHM module for hiT 7070, EOW module for hiT 7050) to be
installed on the controller cards (SCOH, MFP1).
Accessible Overhead Bytes
The table below gives an overview to the accessible overhead bytes, which are
defined for use as overhead channels with SURPASS hiT 7070 and 7050.
EOW channels can be realized with the bytes E1 and/or E2
An RSOH user definable channel can be realized with the byte F1
DCCR channels can be realized with the bytes D1 D3
DCCM channels can be realized with the bytes D4 D12
Special ECCs can be realized with the byte F2
A set out of the MSOH bytes is defined for use as one high capacity channel
and/or for 64kb/s channels accessible via X.21 interfaces


TR3272EU00TR_0302
2003 Siemens AG
27

4 external interfaces accessible at the COPA V.11 / X.21 (SCOH)
Ring Manager RM (SCOH)
Engineering Order Wire Conference EOWC (SCOH)
F2 VC-4 POHs in LO SF TPs
E2 (9,7,1); Z1 (9,2,1) and (9,3,1); Z2 (9,4,1) and (9,5,1)
Unused: (5,5,1), (5,6,1), (5,8,1), (5,9,1), (6,2,1), (6,3,1), (6,5,1), (6,6,1), (6,8,1), (6,9,1), (7,2,1),
(7,3,1), (7,5,1), (7,6,1), (7,8,1), (7,9,1), (8,2,1), (8,3,1), (8,5,1), (8,6,1), (8,8,1), (8,9,1)
NU: (9,8,1) and (9,9,1)
HCOC3 Group 1: combined CP for bytes (5,5,1), (5,6,1), (5,8,1)
HCOC27: combined CP for bytes (5,5,1), (5,6,1), (5,8,1), (5,9,1), (6,2,1), (6,3,1), (6,5,1), (6,6,1),
(6,8,1), (6,9,1), (7,2,1), (7,3,1), (7,5,1), (7,6,1), (7,8,1), (7,9,1), (8,2,1), (8,3,1), (8,5,1), (8,6,1),
(8,8,1), (8,9,1), (9,2,1), (9,3,1), (9,4,1), (9,8,1) and (9,9,1)
DCCM: combined CP for bytes (6,1,1), (6,4,1), (6,7,1), (7,1,1), (7,4,1), (7,7,1), (8,1,1), (8,4,1)
and (8,7,1)
HCOC9 Group 1: combined CP for bytes (5,9,1), (6,2,1), (6,3,1), (6,5,1), (6,6,1), (6,8,1), (6,9,1),
(7,2,1) and (7,3,1)
HCOC9 Group 2: combined CP for bytes (7,9,1), (8,2,1), (8,3,1), (8,5,1), (8,6,1), (8,8,1), (8,9,1),
(9,8,1) and (9,9,1)
MSOH CPs in each
termination point
E1 (2,4,1); F1 (2,7,1); NU (2,8,1); Unused (3,8,1)
DCCR: combined CP for bytes (3,1,1), (3,4,1) and (3,7,1)
RSOH CPs in each
termination point
hiT7070
Overhead Connection Points for hiT 7070

Fig. 15 Overhead Connection Points for hiT 7070
Note:
The SOH numbering scheme (a, b, c) defines:
the row (a)
the multi-column of an STM-1 channel (b)
the STM channel within the STM-N signal (c)


TR3272EU00TR_0302
2003 Siemens AG
28

Ring master RM (MFP1)
Engineering Order Wire Conference EOWC (MFP1)
F2 VC-4 POHs (HO path TPs)
E2 (9,7,1); Z1 (9,2,1) and (9,3,1); Z2 (9,4,1) and (9,5,1)
Unused: (5,5,1), (5,6,1), (5,8,1), (5,9,1), (6,2,1), (6,3,1), (6,5,1), (6,6,1), (6,8,1), (6,9,1), (7,2,1),
(7,3,1), (7,5,1), (7,6,1), (7,8,1), (7,9,1), (8,2,1), (8,3,1), (8,5,1), (8,6,1), (8,8,1), (8,9,1)
NU: (9,8,1) and (9,9,1)
DCCM: combined CP for bytes (6,1,1), (6,4,1), (6,7,1), (7,1,1), (7,4,1), (7,7,1), (8,1,1), (8,4,1)
and (8,7,1)
MSOH CPs in each
termination point
E1 (2,4,1); F1 (2,7,1); NU (2,8,1); Unused (3,8,1)
DCCR: combined CP for bytes (3,1,1), (3,4,1) and (3,7,1)
RSOH CPs in each
termination point
hiT 7050

Fig. 16 Overhead Connection Points for hiT 7050
Note:
The SOH numbering scheme (a, b, c) defines:
the row (a)
the multi-column of an STM-1 channel (b)
the STM channel within the STM-N signal (c)


TR3272EU00TR_0302
2003 Siemens AG
29

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Framing bytes
Bit Interleaved Parity
for bit error monitoring
Section trace
(STM identifier)
Data channels
Order wire
A1, A2
B1, B2
J0
D1-D12
E1, E2
Automatic protection switching
F1
K1, K2
M1
S1
Z1, Z2
User channels
Remote error indication
Sync. status (timing marker)
spare
for national use
Media dependent bytes
AU Pointer
RSOH
MSOH
B1
B2 B2 B2
D1 D2 D3
D4 D5 D6
D7 D8 D9
D10 D11 D12
E1 F1
K2 K1
S1 E2
J0
Z1 Z1 Z2 Z2 M1
H1
A1 A1 A1 A2 A2 A2
H2 H2 H1 H3 H3 H3 H1 H2
Section overhead assignment acc. G.707
Section overhead assignment acc. G.707
a=1
a=2
a=3
a=5
a=6
a=7
a=8
a=9
b=1 b=2 b=3 b=4 b=5 b=6 b=7 b=8 b=9
column (b)
row (a)

Fig. 17 Section overhead assignment acc. G707


TR3272EU00TR_0302
2003 Siemens AG
30

4.2 Overhead Cross-Connection function OHCC
4.2.1 Overview
Overhead bytes can be cross-connected by means of the overhead cross-connection
function OHCC. The granularity is 64 kbit (one byte).
The overhead cross-connection function allows the following flexible connections:
MCF using DCCR bytes or DCCM bytes or the F2 byte
EOWC using E1 byte and/or E2 byte
4-wire analogue interface using E1, E2 bytes.
X.21 interfaces using bytes according
RSOH, MSOH and POH bytes according
The table shown in Fig. 19 gives an overview to the possible overhead cross-
connections. Accessible via the external, physical, interfaces X.21 are the bytes E1,
F1, E2, NU, unused and F2.

TIP
The connection between EOWC and the 2-wire handset interface is not done via the
OHCC.


TR3272EU00TR_0302
2003 Siemens AG
31

OH
Bytes
EOWC
MCF
OHCC
function
#
A/D Coverter,
Ringing
Generator etc.
2-wire analogue
EOW handset
interface *
A/D Coverter,
optional E&M
support etc.
4-wire analogue
interface *
2-wire EOW
handset
digital
interface
* = External, physical interfaces
**= Core only
X.21
interfaces **
fix connected
to EOWC
digital
interface
Overhead Cross-Connection Function OHCC
Overhead Cross-Connection Function OHCC

Fig. 18 Overhead Cross-Connection Function OHCC
X RM
X X X F2
X X X X HCOC9
X X X X HCOC3
X X X X DCCM
X X X X DCCR
X X HCOC27
X X X
F1, Z1, Z2, NU,
Unused
X X X X E1, E2
V
.
1
1

/
X
.
2
1
E
O
W
C
F
2
M
C
F
H
C
O
C
9
H
C
O
C
3
D
C
C
M
D
C
C
R
H
C
O
C
2
7
F
1
,

Z
1
,

Z
2
,
N
U
,

U
n
u
s
e
d
E
1
,

E
2
Connection
Point
CP1/CP2
Possible OH / DCC connections
Possible OH / DCC connections

Fig. 19 Possible OH / DCC connections

TR3272EU00TR_0302
2003 Siemens AG
32

4.2.2 Auxiliary channels (hiT 7070 only)
64kb/s-Auxiliary Channels built with SOH Bytes(hiT 7070)
Fig. 20 gives an overview to the use of SOH bytes with SURPASS hiT 7070 as
64kb/s-overhead channels through a network. In the given example an overhead byte
out of the MSOH shall be used to transfer data from NE 4 to NE 1 (and of course
not shown here for simplification of description- vice versa). An MSOH byte has been
configured, because in this example the OH path shall be protected between NE 3
and NE 2 by a linear 1+1 MSP.
The incoming data are connected via a physical X.21 interface to the OHCC of NE 4.
The data are transported via a NE-internal transport mechanism for OH bytes to the
corresponding interface and inserted into the configured byte of the MSOH in NE 4.
In NE 3 the used OH byte is extracted from the MSOH and transmitted to the OHCC.
In transmit direction the OHCC broadcasts the OH byte via the NE-internal transport
mechanism to the interfaces of the working port and the protecting port. There it is
inserted into the configured OH byte. (Remark: In opposite direction the OHCC
selects -triggered by the MSP function- the OH byte from the active line). The MSP
functionality in NE 2 is inverse corresponding to NE 3. The selected OH byte is
inserted via the OHCC into the MSOH of the outgoing signal to NE 1. In NE 1 the
extracted OH byte is cross-connected via the OHCC to the physical X.21 interface
and forwarded to the data sink.
64kb/s-ECC Channel built with the POH Byte F2
OH access of POH Byte F2 at path terminating points (structured VC-4) is supported
only at LO switching fabric (hiT 7070) or at certain STM-N cards in hiT 7050.
If network termination equipment like SMA1K or SURPASS hiT 7050 shall be
controlled via an ECC a problem raises if this ECC shall be piped through a network
of another carrier (see Fig. 21). It is not possible to use DCCR or DCCM because
carrier A cannot configure the necessary OH cross-connections for the DCC within
the NEs in the network of carrier B. One way to control this remote NE is to use the
F2 byte within the VC-4-POH because the VC-4 is transported transparently through
the network.
Fig. 21 depicts this situation. With SURPASS hiT 7070/7050 it is possible to control
the remote NE via an ECC built with the F2 byte with a transport capacity of 64kb/s.
The OS is connected to an SURPASS hiT 7070/7050 within the area of carrier A.
Using the F2 byte the remote NE (e.g. SMA1K) can be controlled remotely via the
area of carrier B.


TR3272EU00TR_0302
2003 Siemens AG
33

Location B
Router A
Location A
Router A
OHCC
NE3
OHCC
NE2
OHCC
NE1
OHCC
NE4
1+1 MSP
Overhead Path using an MSOH Byte and MSP
Overhead Path using an MSOH Byte and MSP
X.21 X.21
Working
Protecting
Multiplex Section Overhead Byte
Multiplex Section Overhead Byte

Fig. 20 Example for an Overhead Path through a Network using an MSOH Byte and MSP
Remote NE
(e.g. SMA1K)
controlled by
Carrier A
F2-byte cross-connected
via OHCC to MCF
MCF
Carrier A
Use of POH Byte F2
Use of POH Byte F2
Carrier B
TNMS
S
M
A
1
K
S
M
A
1
K
M
C
F
VC-4 path
F2-byte in POH
used as ECC

Fig. 21 Use of POH Byte F2


TR3272EU00TR_0302
2003 Siemens AG
34

DCC Transparency Channels
In addition to the possible cross-connections DCC -> MCF, the OHCC in SURPASS
hiT 7070 offers the possibility to cross-connect DCC to DCC and DCC to NU-
and/or unused OH-bytes (see Fig. 19). This feature (DCC Transparency) can be
used to realize a DCCpipe through a network. Because these DCC-bytes are cross-
connected by means of the OHCC functionality from port to port directly, these
channels are bypassed to the MCF; i.e. the MCF in the intermediate NE are not
loaded by this DCC.
Fig. 22 shows an example how a DCC Transparency Channel can be used. Coming
from Carrier 1 an STM-N signal carrying a DCCM channel is connected to the
SURPASS hiT 7070 ring of Carrier 2. This carrier provides the transparent transport
of the DCCM channel through his network. In NE1 the incoming DCCM channel is
cross-connected to (e.g.) the HCOC9 Group2. This Group of OH bytes transports the
DCCM channel from NE1 to NE2. Within the intermediate NEs appropriate cross-
connections for this group of OH bytes have to be configured. In NE2 -in outgoing
direction- the HCOC9 Group 2 is cross-connected to the DCCM channel of the
outgoing STM-N signal to Carrier 1 again. In this way a transparent transport of DCC
information for the carrier 1 through the network of carrier 2 is realized.
According to the actual need for transport capacity the Groups of OH-bytes can be
used per port at the same time as shown in Fig. 23.


TR3272EU00TR_0302
2003 Siemens AG
35

hiT 7070 Ring
Carrier 2
NE1 NE2
Carrier 1 Carrier 1
Cross-Connection
DCCM <-> HCOC9
Cross-Connection
HCOC9 <-> HCOC9
Cross-Connection
HCOC9 <-> DCCM
STM-N STM-N
DCCM
HCOC9

Fig. 22 Example for the Use of DCC Transparency Channels
(9,9,1) HCOC3 Group5
HCOC9 Group2
(9,8,1)
(9,4,1)
(9,3,1)
(9,2,1)
HCOC3 Group5 (8,9,1)
(8,8,1)
(8,5,1)
(8,3,1)
HCOC9 Group2
(7,9,1)
(7,8,1)
(7,5,1)
(7,3,1)
(7,2,1)
(6,9,1)
(6,8,1)
(6,6,1)
(6,5,1)
(6,3,1)
(6,2,1)
HCOC9 Group1
(5,9,1)
(5,8,1)
(5,6,1)
HCOC27
1728kb/s
HCOC3 Group1
(5,5,1)
OH-Bytes

Fig. 23 Group Definitions for DCC Transparency Channels and HCOC

TR3272EU00TR_0302
2003 Siemens AG
36

High Capacity Overhead Channel (HCOC) (hiT 7070 only)
For management of a 3rd party equipment, one or two auxiliary OH channels with a
configurable transport capacity of up 1728 kbit/s can be configured per NE. To realize
this feature certain groups of MSOH bytes are predefined for this purpose. MSOH
bytes are used because of the protection capability and the number of free bytes.
Four transport capacities are predefined: 64 kb/s, 192kb/s, 576kb/s, and 1728kb/s. A
HCOC can be used (beside other possibilities) as a DCC pipe for a DCN backbone
from router to router through a network (see Fig. 24). The limited number of free
MSOH bytes gives the maximum transport capacity. Access to these HCOC is
provided via the OHCC and the physical X.21 interfaces.
Because the used MSOH bytes are terminated in every NE, they have to be cross-
connected from port to port within all intermediate NE. Therefore:
HCOC can only be used in carrier-own networks; i.e. it is not possible to
configure a path through a network of any other carrier.
All intermediate NE must provide OH-connectivitys for all used MSOH-bytes
according to the table shown in Fig. 23.
In the example shown in Fig. 24 a DCC-pipe is configured through a network
between router A and router B. For protection purposes two HCOCs are configured
using the same NEs at the interchange points. The routers are connected via two
data paths, the working path between the NE-ports A <-> A and the protecting path
between the NE-ports B <-> B.
Because the interchange points for the working and the protecting path are located in
the same NEs (NE 1 / NE 5), two HCOCs are to be configured in these two NEs. A
disadvantage of this configuration is that the internal transport mechanism for OH
bytes is loaded with two HCOC capacities and if NE 1 or NE 5 fails totally, the whole
data pipe is interrupted.
A possible configuration that avoids these disadvantages is the shown in Fig. 25. It
assumes that the NEs 1 and 7 are accessible at the same location. The same holds
for the NEs 6 and 11. Regarding the data paths the difference to Fig. 24 is that the
data are feed to the network via two different NEs. Iin this case the NE internal
transport mechanism for OH bytes is loaded with one HCOC capacity only. Further
on the pipe is not interrupted, if one of the feeding NEs fails totally.


TR3272EU00TR_0302
2003 Siemens AG
37

Location A Location B
NE6 NE8
NE7
NE9
NE1
NE2 NE4
NE5
NE3
OHCC
X.21 X.21
OHCC
X.21 X.21
Protection path
Working path
port A port A
port B port B
Router A Router B
Interchange point
Interchange point
DCC Pipe using two HCOCs for Protection Purposes
DCC Pipe using two HCOCs for Protection Purposes

Fig. 24 DCC Pipe for a Third Party Equipment through a Net using two HCOCs for Protection Purposes
NE2 NE4
NE3
NE5
NE1
NE8 NE10
NE6
NE9
OHCC
X.21
OHCC
X.21
Protection path
Working path
Router A Router B
Interchange point
Interchange point
DCC Pipe using two different NEs for Protection
DCC Pipe using two different NEs for Protection
NE7
X.21
OHCC
NE11
OHCC
X.21
Location A Location B

Fig. 25 DCC Pipe for a Third Party Equipment using two different NEs for feeding to the Network


TR3272EU00TR_0302
2003 Siemens AG
38

4.3 Engineering order wire
4.3.1 Introduction
The engineering order wire channels are transmitted via the EOW bytes E1 and E2
acc. to ITU-T. They can be accessed via the overhead cross-connection and EOW
connection functions and one handset with a two wire analogue interface. In addition
a 4-wire analogue telephone interface is supported (voice mode only). The telephone
conference circuit allows the interconnection of external speech channels (e.g. from
East and West line signals as well as tributary signals; 2-wire and 4-wire interface)
so that each subscriber is connected with every other subscriber.
TIP
Correct connection of the EOW channels into a conference or in a ring structure is
the responsibility of the system administrator.
3-digit selective, group and conference call numbers are supported in which case the
directory numbers 000, XY0 and X00 are reserved for collective call and group call
(see Manual Operator Guidelines OGL).

Note The handset can be connected to the EOWC via the physical analogue 2-
wire EOW interface.
Note The used E bytes are broadcasted to/received from all ports to which the
EOWC is cross-connected via the OHCC function.
Fig. 26 shows an example how an EOW line can be configured through a network. In
this example it is assumed, that the E2 byte shall be used for the line from NE1, NE3
up to the NE8 whereas the E1 byte shall be used for the line between NE1 and NE2.
EOW shall be used at the locations 1, 2, 5, 7 and 8.

NE1: EOWC is cross-connected via
OHCC with:
E2 byte of port 1
E1 byte of port 2
OHCC with:
E2 byte of port 1
OR (see Note below)
E2 byte of port 2
OHCC with:
E1 byte of port 1
OHCC with:
E2 byte of port 1
E2 byte of port 2
E2 byte of port 3
OHCC with:
E2 byte of port 1
E2 byte of port 2
OHCC with:
E2 byte of port 1
E2 byte of port 2


TR3272EU00TR_0302
2003 Siemens AG
39
OHCC with:
E2 byte of port 1
E2 byte of port 2
E2 byte of port 3
OHCC with:
E2 byte of port 2


TR3272EU00TR_0302
2003 Siemens AG
40

NE 3
NE 1
NE 8
NE 4
NE 7
NE 6
EOW-Path:
NE 2
1
2
8
P
o
r
t

1
P
o
r
t

2
P
o
r
t

1
Port 2
Port 1
Port 2
P
o
r
t

3
P
o
r
t

2
P
o
r
t

1
P
o
r
t

1
P
o
r
t

2
Port 2
Port 1
P
o
r
t

3
P
o
r
t

2
Port 1
# = is cross connected to
E2 # EOWC
via OHCC
E2 # EOWC
via OHCC
E1 # EOWC
via OHCC
E1 # EOWC
via OHCC
E2 # EOWC
via OHCC
E2 # EOWC
via OHCC
E2 # EOWC
via OHCC
E2 #
EOWC
via
OHCC
E2 # EOWC
via OHCC
E2 # EOWC
via OHCC
E2 # EOWC
via OHCC
7
5
NE 5
*
*
#
= optional to avoid a closed EOW-loop
EOW Path through a Network
EOW Path through a Network
Ring Manager

Note The handset can be connected to the EOWC via the physical analogue 2-
wire EOW interface.
Note The used E bytes are broadcasted to/received from all ports to which the
EOWC is cross-connected via the OHCC function.
Fig. 26 Example for an EOW Path through a Network

TIP
NE5 can also take part of the EOW line, but in this example the EOW path is
interrupted here by means of the activated ring manager function in order to avoid an
EOW-loop. I.e., the EOWC may not be cross-connected to the E2 bytes of both ports
1 and 2, but to one port only. This works as an EOW protection in the case of a span
failure.
Example: If the E2 byte from port 2 is used and a line within the ring fails, the E2 byte
from port 1 will be used for EOW automatically.


TR3272EU00TR_0302
2003 Siemens AG
41

Engineering Order Wire Conference (EOWC)
In SURPASS hiT 7070/7050 design, one EOWC, which belongs to a party line
consisting of one or several EOW channels, is supported. All EOW communication
channels are linked together in the network element by means of the EOWC function.
Necessary data processing, as adding and subtracting the adequate E1/E2 bytes,
supervision of all EOWC-inputs for static bytes, etc. are performed by the EOWC
functionality within the NE.
Several subscribers can use the conference (one conference is supported) at the
same time. In the SURPASS hiT 7050 maximum 4 lines can attend the conference
call, and in the SURPASS hiT 7070 up to 8. The sum of the incoming digital voice
signals of all ports, minus the incoming digital voice signal of the own port (high
return loss) is distributed to all outgoing ports. Internally the data are processed as
linear PCM code (A-law according to ITU-T G.711).

TR3272EU00TR_0302
2003 Siemens AG
42

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

EOWC
A/D Coverter,
Ringing
Generator etc.
2-wire analogue
EOW handset
interface *
A/D Coverter,
optional E&M
support etc.
4-wire analogue
interface **
2-wire EOW
handset
digital
interface
* = External, physical interfaces
**= Core only
X.21
interfaces **
Fixed
connection
to EOWC
digital
interface
OHCC and EOWC function
OHCC and EOWC function
RM
OHMUX
function
Configurable
connection
to EOWC
OHM module
on SCOH
OH
Bytes
MCF
OHCC
function

Fig. 27 Overhead Cross-connection function OHCC and Engineering Order Wire Conference function EOWC


TR3272EU00TR_0302
2003 Siemens AG
43

EOW in Networks with Ring-Configuration / Ring manager
An automatic EOW ring-manager is supported only for SURPASS hiT 7070 only. The
7050 has restricted functionality. The ring manager is called ring master, and in the
case of fiber break it has to be reconfigured by hand.
If rings are supported, an EOW ring manager must be implemented in order to
provide EOW protection. In case of STM ring networks the EOW network must still be
a linear chain. This is accomplished by means of the EOW ring manager function in
one NE of the ring. The ring manager disconnects the EOW channels between east
and west line interfaces.
The EOW network will be a linear chain starting at one side of the NE with the ring
manager and ending at the other side of the same NE. In case of a ring failure the
ring manager has to connect the east and west EOW channels in order to have still
EOW access to all NEs of the ring. This is accomplished by comparing the signal
levels of the EOW channels from east and west side. If the mean amplitudes of both
sides are the same, the ring is working correctly and east and west sides are
disconnected. If they are different, a ring failure has occurred and east and west
sides are connected together.
TIP
Without an EOW ring manager it is still possible to operate an EOW in a ring. In this
case the EOW has to be configured as a linear chain with the result that the EOW is
not protected in case of span or node failures. But note, this is exactly the situation,
where an EOW connection should be available for the service staff immediately,
without the need of reconfiguration the EOW.
If the ring manager shall be activated, it has to be inserted in an EOW loop by
connecting the E1/E2 byte of one line interface to the ring manager and the ring
manager to the EOW conference.
Fig. 28 and Fig. 29 show an example with a 4-node ring. All connections between the
network elements represent E1/E2 data transmission channels. So, in case of a
configured ring of NEs, the EOW (E1/E2 byte data transmission) has to be
interrupted at exactly one node (EOW ring manager function).


TR3272EU00TR_0302
2003 Siemens AG
44

EOW channels disconnected by ring manager
2-wire handset
connection
Ring manager (RM) function
OH/EOW
hiT 7070
O
H

/

E
O
W
h
i
t
7
0
7
0
O
H

/

E
O
W
OH/EOW
hiT 7070
h
i
T
7
0
7
0
RM function in a fault-free hiT 7070 ring
RM function in a fault-free hiT 7070 ring

Fig. 28 Ring manager function in a fault free hiT 7070 ring
rerouted connection in RM
2-wire handset
connection interrupted due to fiber break
fiber break
connection
Ring manager (RM) function
OH/EOW
hiT 7070
O
H

/

E
O
W
h
i
t
7
0
7
0
O
H

/

E
O
W
OH/EOW
hiT 7070
h
i
T
7
0
7
0
RM function in a disturbed hiT 7070 ring
RM function in a disturbed hiT 7070 ring

Fig. 29 Ring manager function in a disturbed hiT 7070 ring


TR3272EU00TR_0302
2003 Siemens AG
45

4.3.2 EOW configuration
To configure the EOW functionality the user needs to program the feature in the
following order:
Activate EOW
Assign Telephone Nr. to 2-wire handset
Connect/disconnect 4-wire E&M interface to EOW Conference
Connect E1/E2 OH byte(s) to EOWC as necessary
Optionally in SDH ring configuration connect RM to E1/E2 OH byte

TIP
The OHM module needs to be installed on the SCOH card.

Function: Activate EOW
Step Name of the Window Used Menu or Command Remarks
1 "Module View" Window Select (RMB) SCOH module
symbol. From open menu select
"Configuration > Card"
"SCOH Config"
Window opens.
2 "SCOH Config" Window Set the "EOW Active"
checkmark to "ON"

3 "SCOH Config" Window Confirm selection with the
"Apply" button.

Function: Configure OH functions
1 "Module View" Window Select (RMB) NE functional
"Configuration > Overhead
Functions"
"NE - Overhead
Functions
Config" Window
opens.
2 "NE - Overhead
Functions Config"
Set the three digit "Telephone
Number" as required
Telephone Nr.
for 2-wire
handset
3 "NE - Overhead
Functions Config"
Connect/disconnect 4-wire E&M
interface to EOWC as required.

4 "NE - Overhead
Functions Config"
Confirm selection with the
"Apply" button.


TR3272EU00TR_0302
2003 Siemens AG
46

1
2
3

Fig. 30 EOW Active configuration
1
2
4
3

Fig. 31 Configure Overhead Functions


TR3272EU00TR_0302
2003 Siemens AG
47

Function: Connect E1/E2 OH byte(s) to EOW Conference (EOWC)
"Configuration > OH Cross-
connections"
"Overhead Cross
connection"
Window opens.
2 "Overhead Cross
connection" Window
Select "STM-N E1/E2" OH byte
you want to connect and choose
"Set as TP_A"

3 "Overhead Cross
connection" Window
Select "EOW Conf" and choose
"Set as TP_B"

4 "Overhead Cross
connection" Window
Set the cross-connection with the
"Connect" button.

5 "Overhead Cross
connection" Window
For additional connections to the
EOWC repeat steps 2 up to 4.

Function: Connect E1/E2 OH byte(s) to Ring manager (RM)
"Configuration > OH Cross-
connections"
"Overhead Cross
connection"
Window opens.
2 "Overhead Cross
connection" Window
Select "EOW Ring" and choose
"Set as TP_A"

3 "Overhead Cross
connection" Window
Select "STM-N E1/E2" OH byte
you want to connect and choose
"Set as TP_B"

4 "Overhead Cross
connection" Window
Set the cross-connection with the
"Connect" button.

TIP
If you want to get a list of existing OH Cross-connections, select the "OH CC List"
tab in the "Overhead Cross connection" Window (see Fig. 35).

TR3272EU00TR_0302
2003 Siemens AG
48

1

Fig. 32 OH Cross connections I
2
3
4

Fig. 33 OH Cross Connections II


TR3272EU00TR_0302
2003 Siemens AG
49

Fig. 34 View OH Cross Connections Termination Points

Fig. 35 View OH Cross Connections List

TR3272EU00TR_0302
2003 Siemens AG
50

5 Exercises

Fig. 36


TR3272EU00TR_0302
2003 Siemens AG
51


TR3272EU00TR_0302
2003 Siemens AG
52

Exercise 1
Title:
MCF functions
Objectives:
The participant shall be able to:
display and configure MCF parameters
Pre-requisite:
Pre-read chapter "MCF configuration"

WARNING
The following exercises will require active TNMS Core Client session.

Task 1

Ask your instructor for the name of your team (e.g. student01), IP address of the
TNMS Core Main server (e.g. 10.10.72.190), name and the type of the NE which will
be use for the exercises (e.g. NE name: Muenchen; NE type: hiT 7070 DC) and
write it down in the fields bellow:

I am working with the team: student _ _
IP address of TNMS Core: __ . __ . __ . __
Type of the NE: ___________________
Name of the NE: ____________________

Fig. 37


TR3272EU00TR_0302
2003 Siemens AG
53

Start up the TNMS Core client SW and login to the TNMS Core.
Start up the Element Manager SW to open details view of the NE assigned to your
team.
Open the "Message Communication Function" window and check the MCF
settings of the NE. Write down the MCF parameters of the NE in the table bellow.

Fill in the following table
NSAP Address NE
Name
NE
Type Area Part SID Part
MAC
Address
Routing
Principle

Task 2

Using the data in the drawing below configure the MCF parameters for the NE
assigned to your team.

WARNING
For the parameters, which are not applicable, leave the default settings as they
are.

From the instructor PC (use a projector) check the MCF settings have been
configured for all network elements.

Fill in the following table
NE Name Stack Parameters DCC Parameters
6. Comply 7. Comply
8. Comply 9. Comply
10. Comply 11. Comply


TR3272EU00TR_0302
2003 Siemens AG
54

S
T
M

1
6
STM 16
S
T
M

1
6
STM 1 STM 1
STM 1
102
#1
102
#3
102
#1
102
#3
304
#1
304
#1
303
#1
304
#1
303
#1
hiT 7070 SC
Nuernberg or Mainz
hiT 7070 SC
Ulm or Essen
hiT 7070 DC
Muenchen or Dortmund
hiT 7050 FP1
Augsburg or
Paderborn
hiT 7050 FP1
Erding or
Giessen
Stack Parameters
Routing Principle -> Level 1 IS
DCC Parameters
Port Type #1 -> DCCM
Port #1 -> 303 IFS2G5.01
Interface Type -> User
Port #2 -> 304 IFS2G5.01
Interface Type -> Network
Student01
Student04
Student03
Student02
Stack Parameters
DCC Parameters
Port #1 -> 303 IFS2G5.01
Port #2 -> 304 IFS2G5.01
Stack Parameters
DCC Parameters
Port #1 -> 102 O155-4.01
Port #2 -> 102 O155-4.03
Stack Parameters
DCC Parameters
Port #1 -> 102 O155-4.01
Port #2 -> 102 O155-4.03
TNMS CT
Server
Q ST
102
#1
102
#1
109
#1
109
#2
101
#1
Stack Parameters
DCC Parameters
Port #1 -> 101 IFS2G5.01
Port #2 -> 102 IFS2G5.01
DCC Parameters
Port #3 -> 109 IFO155M.01
Port #4 -> 109 IFO155M.02

Fig. 38 DCN setup

In the laboratory connect Gateway network elements (Muenchen or Dortmund) to the
local TNMS CT via Q3 interface and disconnect all other NE's from the LAN (if they
are connected).
To prove the functionality of the DCN network deactivate and then activate again
connection to the NE's from "DCN Management" window of the TNMS CT. Login to
the network elements and perform some simple operations (e.g. request alarm data).


TR3272EU00TR_0302
2003 Siemens AG
55

If you are experiencing difficulties getting connection to NE,
please consult with your instructor,
and together find a solution to get a connection
to the NE.
And as for you, have you done
everything that you had to do?

Fig. 39

Ive got it !
(Connect all NE's back to the LAN
as they were before exercise).
F I N I S H . F I N I S H .

Fig. 40


TR3272EU00TR_0302
2003 Siemens AG
56

Exercise 2
Title:
EOW
Objectives: The participant shall be able to:
configure EOW function
Pre-requisite:
Pre-read chapter "EOW configuration"

WARNING
The following exercises will require active TNMS Core Client session.

Task 1

Ask your instructor for the name of your team (e.g. student01), IP address of the
TNMS Core Main server (e.g. 10.10.72.190), name and the type of the NE which will
be use for the exercises (e.g. NE name: Muenchen; NE type: hiT 7070 DC) and
write it down in the fields bellow:

I am working with the team: student _ _
IP address of TNMS Core: __ . __ . __ . __
Type of the NE: ___________________
Name of the NE: ____________________

Fig. 41


TR3272EU00TR_0302
2003 Siemens AG
57

Start up the TNMS Core client SW and login to the TNMS Core.
Start up the Element Manager SW to open details view of the NE assigned to your
team.

Make sure, that the "EOW Active" parameter is activated at the SCOH
EOW Active Yes No

Assign the telephone number to the 2-wire handset at your node, as indicated in the
network diagram; see Fig. 42 for EOW Plan (hiT 70xx Row 3) or Fig. 43 for EOW
Plan (hiT 70xx Row 8).
Node Name: _______________
Telephone Number: _________

Connect the STM-N E2 OH bytes to the EOWC or to RM respectively, as indicated in
the network diagram; see Fig. 42 for EOW Plan (hiT 70xx Row 3) or Fig. 43 for EOW
Plan (hiT 70xx Row 8).
How many OH Cross-connections you have set up at your node?
1 2 3

Connect 2-wire handset to your node and verify the configuration by setting up test
calls between NEs.
Connectivity OK? Yes No

Break the ring between the nodes "Mainz/Nuernberg" and "Dortmund/Muenchen"
(e.g. by Laser Shutdown). Again set up test calls between NEs.
Connectivity OK? Yes No

Reconnect the ring as it was before.

TR3272EU00TR_0302
2003 Siemens AG
58

S
T
M

1
6
STM 16
S
T
M

1
6
EOW Plan (hiT 70xx Row 3)
hiT 7070 SC
Mainz
hiT 7070 SC
Mainz
304
#1
304
#1
303
#1
hiT 7070 DC
Dortmund
hiT 7070 DC
Dortmund
102
#1
102
#1
101
#1
hiT 7070 SC
Essen
hiT 7070 SC
Essen
304
#1
303
#1
Handset Tel. Nr.: 313 Handset Tel. Nr.: 312
Handset Tel. Nr.: 311
TP A TP B
1-304 EOW Conf
IFQ2G5.01
MSOH 9.7 (E2)
TP A TP B
1-303 EOW Conf
IFQ2G5.01
MSOH 9.7 (E2)
TP A TP B
1-101 EOW Conf
IFQ2G5.01
MSOH 9.7 (E2)
TP A TP B
1-102 EOW Conf
IFQ2G5.01
MSOH 9.7 (E2)
TP A TP B
1-303 EOW Conf
IFQ2G5.01
MSOH 9.7 (E2)
TP A TP B
EOW Ring 1-304
IFQ2G5.01
MSOH 9.7 (E2)

Fig. 42 EOW Plan (hiT 70xx Row 3)
S
T
M

1
6
STM 16
S
T
M

1
6
EOW Plan (hiT 70xx Row 8)
hiT 7070 SC
Nuernberg
hiT 7070 SC
Nuernberg
304
#1
304
#1
303
#1
hiT 7070 DC
Muenchen
hiT 7070 DC
Muenchen
102
#1
102
#1
101
#1
hiT 7070 SC
Ulm
hiT 7070 SC
Ulm
304
#1
303
#1
Handset Tel. Nr.: 813 Handset Tel. Nr.: 812
Handset Tel. Nr.: 811
TP A TP B
1-304 EOW Conf
IFQ2G5.01
MSOH 9.7 (E2)
TP A TP B
1-303 EOW Conf
IFQ2G5.01
MSOH 9.7 (E2)
TP A TP B
1-101 EOW Conf
IFQ2G5.01
MSOH 9.7 (E2)
TP A TP B
1-102 EOW Conf
IFQ2G5.01
MSOH 9.7 (E2)
TP A TP B
1-303 EOW Conf
IFQ2G5.01
MSOH 9.7 (E2)
TP A TP B
EOW Ring 1-304
IFQ2G5.01
MSOH 9.7 (E2)

Fig. 43 EOW Plan (hiT 70xx Row8)


TR3272EU00TR_0302
2003 Siemens AG
59

If you are experiencing difficulties getting connection to NE,
please consult with your instructor,
and together find a solution to get a connection
to the NE.
And as for you, have you done
everything that you had to do?

Fig. 44

Ive got it !
(Reconnect the ring as it was before).
F I N I S H . F I N I S H .

Fig. 45

TR3272EU00TR_0302
2003 Siemens AG
60

6 Solution

Fig. 46


TR3272EU00TR_0302
2003 Siemens AG
61


TR3272EU00TR_0302
2003 Siemens AG
62

Solution
Title:
MCF functions
Objectives:
The participant shall be able to:
display and configure MCF parameters
Pre-requisite:
Pre-read chapter "MCF configuration"

(No solution).


TR3272EU00TR_0302
2003 Siemens AG
63

08 Tr3272eu00tr 0302 MCF Configuration

Uploaded by

Document Information

Original Description:

Original Title

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

08 Tr3272eu00tr 0302 MCF Configuration

Uploaded by

Copyright:

Available Formats

MCF configuration Siemens

You might also like