C-DOT NMS

SPECIFICATIONS

Table of Content
Chapter 1.

Chapter 2.

Chapter 3.

Introduction ..............................................................................................................................5
1.1.

Network Configurations Supported ...........................................................................6

1.2.

Equipment Configurations Supported : .....................................................................6

Operational Requirements.......................................................................................................8
2.1.

System Requirements .................................................................................................8

2.2.

System Upgradability .................................................................................................8

Functional Specifications of CNMS.......................................................................................10

3.1.

Basic Features Supported .........................................................................................10

3.2.

Basic Functional Blocks ............................................................................................11

Chapter 4.

Documentation........................................................................................................................28

Chapter 5.

References ...............................................................................................................................29

Chapter 6.

Abbreviations ..........................................................................................................................30

Annexures

List of Annexures....................................................................................................................31

Annexure A

List of Features in Release 1.0 of CNMS ..............................................................................32

Annexure B

Line Diagrams of Various Equipment Configurations ........................................................35

Annexure C

List of Alarms, Alarm Types and Severity Levels................................................................39

Annexure D

List of Performance Parameters, their Threshold Ranges and Default Threshold ..............
Values ....................................................................................................................................43

Annexure E

List of Functions Available for Each Category of User........................................................46

H:\HOME\CNMS\CNMSSPEC.DOC

April 24, 2000

Chapter 1.

Introduction
C-DOT Network Management System (CNMS) shall manage a transport network
consisting of C-DOT SDH network elements. CNMS Ver1.0 shall support a network of
CSAM155. The network topologies supported are point to point, ring and bus. Hubbing
feature shall also be supported.
CNMS shall manage the SDH network via a gateway network element through Q
interface. It shall interact with the SDH hardware and software for information exchange
required for supporting various management functions.
CNMS is a powerful and advanced network management system, which can exploit the
full potential of SDH networks. It is a modular system which provides user friendly
graphical interface and a persistent database.
The CNMS specifications are derived from the overall TMN specifications.

SPECIFICATIONS

Chapter 1

1.1.

NETWORK CONFIGURATIONS SUPPORTED

CNMS-OS
Q I/F
DCN(OPTIONAL)
Q I/F
ECC(STM-1)

ECC(STM-1)
SDH
NE

TRIBS

GNE

SDH

SDH
SDH

(WITH HUB)

ECC(STM-1)

TRIBS

ECC(STM)

ECC(STM-1)
TRIBS

SDH
NE

SDH
NE

SDH
NE

TRIB

FIG-1 : NETWORK TOPOLOGY

CNMS shall support a network topology of a RING with hub connectivity to linear
chain of network elements.
Other topologies supported are linear or bus. The following network topologies can
be achieved using various configurations of the SDH network element :

1.2.

Linear network (with 1+1 protection)

Ring network(2 fibre)

Hub network

EQUIPMENT CONFIGURATIONS SUPPORTED :

CNMS shall support the following configurations of C-DOT SDH network elements
within a network. :

C-DOT NMS

INTRODUCTION

STM-1 Add Drop Multiplexer:

2 fibre (CA01-2F)
4 fibre (CA01-4F)

STM-1 Add Drop Multiplexer as Hubbing node:

2 fibre (CH01-2F)
4 fibre (CH01-4F)

STM-1 Terminal Multiplexer with 1+1 line (CM01)

STM-1 Line Regenerator (CR01)

The tributary configurations are as follows:

CA01-2F or CM01 with max-63 nos. of 2 Mbps tributaries

CA01-4F or CH01-2F with max-32 nos. of 2 Mbps tributaries

CH01-4F does not provide add/drop at tributary level if 1+1 protection is

provided at the hub.

SPECIFICATIONS

Chapter 2.

Operational Requirements
2.1.

SYSTEM REQUIREMENTS
CNMS-OS shall be a workstation based system with the following requirements:
1.

The workstation configuration shall be

HP 9000 model 712 with

80 MHz PA7100 LC chip

Internal speaker (audio alarms)

Serial port (RS-232)

Parallel port (printer)

64MB RAM

1 GB hard disk

3.5 Floppy drive(1.44MB MFY ,external)

DAT drive

Keyboard , mouse (three button), mouse pad and accessories

S/W on DDS drive (HP-UX 9.0x, HP-VUE and MOTIF 1.2)

17 Colour monitor

The serial interface shall be RS232, asynchronous upto 9600 bauds

3.

The operating system used shall be HP-UX 9.05 . The user interface shall be
developed on X-windows based MOTIF(ver 1.2) widget set.
Printer (Optional): Postscript printer

2.2.

SYSTEM UPGRADABILITY
The system shall have upgrade paths with respect to the following

System shall be upgradable to support management of STM-4 network.

System upgradation shall be possible to provide more management

application functions like accounting management and also to upgrade the
C-DOT NMS

OPERATIONAL REQUIREMENTS

present application functions of fault, performance, configuration and

security management.

It shall be possible to upgrade the system to support other network topologies

consisting of cross connect systems.

SPECIFICATIONS

Chapter 3.

Functional Specifications of CNMS

CNMS functional specifications are derived from the TMN specifications.
3.1.

BASIC FEATURES SUPPORTED

Basic features supported by CNMS are :

10

Creation and configuration of the network.

Installation and provisioning of the network.

Flexible routing of the payload demands.

Display of routing map.

Reconfiguration of the network for addition/deletion of a network element (to

be added in later release).

Inspection and configuration of the resources like

reference clock

order-wire channels

Forced/manual protection switching (later release).

Alarm acquisition and real time display.

Selective masking of alarms.

Suspend/resume alarm reporting.

Summary of recent alarms.

Setting of Alarm Event Criteria.

Alarm logging.

Selective display of logged alarms.

Alarm localisation.

Trouble Administration.

Performance monitoring according to G.826.

Setting of performance counters thresholds.

C-DOT NMS

FUNCTIONAL SPECIFICATIONS OF CNMS

3.2.

Retrieval and display of performance parameter counts (both current and

historic).

Setting of performance data monitoring resolution (15 min/1day).

Suspend/resume performance data collection.

Display of parameter threshold crossings.

Backup of the alarm and performance data.

Authorised and restricted access to various features.

Creation/ Deletion of users.

List of existing users.

BASIC FUNCTIONAL BLOCKS

CNMS is a logical network which not only interacts with the SDH transport
network but also uses part of the network to send/receive information to/from it and
control its operations . CNMS can be classified into the following functional blocks

CNMS-OSF ( CNMS Operations System Function )

CNMS-OSF-MAF

CNMS-OSF-MCFq

CNMS-WSF (CNMS Workstation Function)

CSAM-NEF (CSAM Network Element Function)

CSAM-NEF-MAF

CSAM-NEF-MCFq

CSAM-NEF-MCFecc

SPECIFICATIONS

11

Chapter 3

OSF

MAF

f ref. point

WSF

MCFq

q reference

MCF
MCFecc

MCFecc

NEF
MAF

SDH NETWORK

MCFecc

MCFecc
MCFq

NEF
MCFecc

MAF

MAF

NEF

MCFq

MCFecc

FIG 2-FUNCTIONAL BLOCK

3.2.1.

CNMS-OSF(OPERATIONS SYSTEM FUNCTION)

The CNMS Operations System Function shall be responsible for collecting,
storing and processing of management information provided by CSAM-NEF.
This functional block shall be running on HP-UX and shall provide a human
interface (CNMS-WSF) through user friendly X/Motif GUI. With the support

12

C-DOT NMS

FUNCTIONAL SPECIFICATIONS OF CNMS

of information received from CSAM-NEF, it shall perform various

management functions to execute remote provisioning with bandwidth
allocation, path setting management, protection switching and service state
management; performance monitoring with logging, statistical analysis and
display; centralized monitoring with logging, real time display and
localization of faults; user registration and login control.
The functional components constituting the block CNMS-OSF are :

3.2.1.1.

CNMS-OSF-MAF

CNMS-OSF-MCFq

CNMS-OSF-MAF (CNMS-OSF-MANAGEMENT APPLICATION

FUNCTION)
These Management Application Functions are the essential and underlying
part of the OSF.
These are categorised into the following Management Function Areas :

3.2.1.1.1.

Configuration management

Fault management

Performance management

Security management

CONFIGURATION MANAGEMENT
The configuration management covers the Management Application
Functions (MAFs) which enable the user to create and modify the
management model for both logical and physical resources within the SDH
network. It provides MAFs to exercise control over, identify, collect data from
and provide data to NEs.
The following functions shall be provided:

Installation of the Network and/or NE.

Installation is the process of bringing up a resource (network and
equipments) to the default configuration. It is assumed that the first
Network Element that gets installed is the Gateway Network Element
(gateway of the n/w to CNMS-OS). Each NE establishes contact with
the CNMS-OS (called the manager), once it gets its basic identity
information. After the handshaking of control messages, the
NE/network enters into provisioning state.

Provisioning the network and/or NE:

Provisioning consists of procedures which are necessary to bring an
equipment into service. Once installation is over, complete

SPECIFICATIONS

13

Chapter 3

configuration information is downloaded onto each NE, following which

the NE/network enters into the In-service state.

NE status and control:

Complete NE configuration shall be maintained by the CNMS-OS. It
sends/receives configuration/change in configuration to/from each NE
on demand or autonomously. The following configuration information
shall be maintained and sent to each NE to configure the
corresponding units.
1. Synchronisation: Each NE shall be
configured for its
synchronization reference as well as the Clock generator mode as
synchronous/free-running/holdover or internal.
2. Network connectivity: According to the topology of the network
created by the operator, the neighbours of each NE shall be
maintained. The connectivity of each NE from any other NE in the
network shall also be maintained for the DCC communication.
3. Payload: Every demand for payload given by the user shall be
checked for the availability of the tributary ports and bandwidth. If
the demands can be routed then the payload is mapped into the
STM frame otherwise port/bandwidth unavailability is informed to
the user.
4. Order-wire: Order-wire related information including the selective
call no., the groups to which the NE belongs, handset connectivity,
exchange connectivity, call status, selective call routing, and
omnibus call routing information shall be maintained.
5. Path Monitoring: Path connectivity is monitored for each demand
and for each connection through path trace and signal label bytes of
POH.
6. Card Status: The card status and configuration of each card in
the NE shall be maintained.
7. Line interfaces: The configuration of the line
(optical/electrical) for each line shall be maintained.

interfaces

8. Protection state: The protection switch state is maintained. Each

time, protection switching occurs, the status is informed to the
manager.

Protection switching:
Following protection switching commands can be initiated by the user
for maintenance purpose-

14

FSR- Forced switch for Ring

C-DOT NMS

FUNCTIONAL SPECIFICATIONS OF CNMS

MSR-Manual switch for Ring

EXR-Exerciser for signalling

LOP-Lock out of protection

Routing of the Payload:

For each payload demand entered by the user, the path from the
source to the destination shall be calculated and the payload tributary
is mapped into STM frame.

Network and/or NE state Maintenance:

CM maintains the following states of the NEs and the network :

Out of Service

Installation

Provisioning

In service

Reconfiguration

Reconfiguration of the network:

The network shall be reconfigured by adding or deleting a NE.

Maintenance of Network information:

The following information shall be maintained by CM in the form of
files

3.2.1.1.2.

Information of the network like name, topology, size, state of the

network and the information of each NE in the network like
label, address, node id, family, type and state of the NE.

Network Connectivity matrix.

Configuration information for each NE.

Routing information for each of demand like the path selected,

the KLM no. at each line along the path and the state of
demand.

FAULT MANAGEMENT
Fault management is a set of functions which enable the detection, reporting
and localization of fault conditions that occur in a SDH network. It shall
provide alarm surveillance and maintenance of a database of alarms
The following functions shall be supported

SPECIFICATIONS

Alarm Surveillance:

15

Chapter 3

It is mainly concerned with the alarm reports from the NEs. It

supports

allow /inhibit alarm reporting

request/report status of allow/inhibit alarm reporting

allow reporting of selective alarm types

get the types of alarms currently enabled for reporting

get the history of most recent alarm types

Alarm Logging
It facilitates logging of all the reported alarms. Once the log exceeds a
predefined value the alarms are flushed into system log files following
which the user can take back up.

Selective logging of reported alarms with a provision to log all

reported alarms.

View the log/query the log based on some alarm attributes.

back up the system log files

view from the backup device

provide a summary of logged alarms

Alarm localisation
Alarm localization shall give a list of alarms, outstanding for the last
24 hours on each card unit of the NE.

Trouble administration
It is concerned with generation of troubles on identification of root
alarms in the network. Each trouble shall be identified by a unique
trouble id. and it contains a brief description of the trouble. The
trouble is automatically deleted on cessation of the root cause.

3.2.1.1.3.

PERFORMANCE MANAGEMENT
Performance Management provides functions to evaluate and report upon the
behavior of telecommunication equipment and the effectiveness of the
network or network element.
It does the function of monitoring the SDH network by collecting the
performance related data (i.e. values of the various performance parameters)
from the NE .The following functions shall be supported:

16

Performance Monitoring :

C-DOT NMS

FUNCTIONAL SPECIFICATIONS OF CNMS

It involves fetching the performance parameter values from the Nes.

Threshold crossing notifications for the parameters are also sent by the
Nes. The various monitoring functions are ;
-

Get Reporting Option :

This feature is used to find out the current reporting option set
by the user for each NE.

Get Dump Report:

Dump report is requested by the user when he is interested in
the past data. He can request for all parameters or select some
parameters for reporting.

Get Scheduled Report:

The user can set different schedules (for different sets of
parameters or different duration) for future reporting according
to his requirement. The respective NE will report as per the
schedules set. Schedules can be set for all parameters or selected
parameters.

Get Continuous Report:

If the user wants performance parameter reports every 15
minutes then he selects continuous reporting mode. He can
request for all parameters or selected parameters.

DEFAULT REPORTING MODE: Continuous Reporting of all parameters.

Performance Control:
It shall involve changing the attributes related to performance
monitoring. The attributes are performance parameter thresholds and
reporting option . The control functions supported shall be :
-

Set Reporting Option :

Reporting options are Start/Stop Reporting. Start Reporting
starts default reporting and Stop Reporting stops continuous
as well as scheduled reporting (except dump request) but
autonomous reporting of threshold crossing is not affected.

Set Thresholds :
Thresholds for performance parameters shall be set by the user
as per the specified ranges.

Performance Database:
This feature facilitates logging of the reports. The scheduled and
continuous reports are logged into separate databases. Dump reports

SPECIFICATIONS

17

Chapter 3

are not logged as they are displayed online. Following actions can be
taken on the database:

3.2.1.1.4.

view scheduled report of specified schedule.

view continuous report of the specified parameters.

view continuous report of all parameters.

plot the specified report in rectangular or curve form.

view the schedules set by the user.

backup of the database.

restore and view from the backup device.

SECURITY MANAGEMENT
It deals with the aspects of security access relating to management functions.
The following System Administration functions are supported :

Create User

Delete User

List User

Working User

Change Password

The users are categorized into three types :

Super-user

Privileged user

Ordinary user

Each type of user is authorized to perform a certain set of functions.

Super-user : A super-user is authorized to perform all functions including
System Administration functions of Create User and Delete User. The user
who can login first after installation is the super-user. Further, he creates
other users.
Privileged User : A privileged user is authorized to perform all the
management functions of CM, FM and PM but the System Administrative
functions like Create User and Delete User are not in his domain.
Ordinary User : An ordinary user is not authorized to perform the functions
of Network Creation, defining the configuration or setting any parameter of
the NE/network. He can perform the monitoring functions only.

18

C-DOT NMS

FUNCTIONAL SPECIFICATIONS OF CNMS

3.2.1.2.

CNMS-OSF-MCFq
(CNMS-OSF-MESSAGE
FUNCTION AT Q INTERFACE)

COMMUNICATION

CNMS-OSF-MCFq is related to the physical interface and the associated

protocol stack at the q reference point. Reference point q is between CNMSOSF and CSAM-NEF, called Q interface. This interface shall support bidirectional data transfer for the management of SDH network. It shall have a
four layer protocol stack. The management applications shall be developed
using the transport layer primitives. The protocol stack specifications are :
PHYSICAL LAYER

V.24/V.28 or X.25 High Speed I/F

DATA LINK LAYER

X.212 / X.222

NETWORK LAYER

X.213 / X.223

TRANSPORT LAYER

X.214 / X.224

(TP0, TP2, TP3)

3.2.1.2.1.

PHYSICAL LAYER :
It shall form the first layer of the four layer stack. It shall conform to the EIA
RS-232C (ITU V.24 and V.28) standard. The details are given in annexures.
The high speed interface shall be synchronous X.25.

3.2.1.2.2.

DATA LINK LAYER :

It shall form the second layer of the four layer stack. The features supported
shall be:

CONNECTION ESTABLISHMENT AND RELEASE :

It shall support connection oriented services. Therefore, for any
services to be obtained from this layer, requires the service user to first
establish a connection. The connection should be released
(disconnected) after using the service.

FLOW CONTROL :
Data shall be transferred after the connection is established. Flow
control is required to ensure data transfer in proper sequence and to
prevent data loss and buffer overflows.

DETECTION OF ERRORS & RECOVERY :

Link shall be reset and re-established in case of abnormal link
conditions. CRC is required to check data integrity.

SPECIFICATIONS

19

Chapter 3

3.2.1.2.3.

NETWORK LAYER :
Network Layer forms the third layer of the four layer stack. It shall support
the following features :

CONNECTION MANAGEMENT :
The Network Layer simulates multiple logical connections over a
single data link connection. It manages each logical connection for its
establishment as well as release.

DATA TRANSFER :
It takes data from Transport Layer (TPDU) and hands it over to the
other end Transport Layer as it is. For each connection, NL store upto
8 TPDUs, each of maximum size 2k.

FLOW CONTROL :
Flow control is required to regulate the information transfer. The
sliding window flow control with a window size 2 shall be used.

FRAGMENTATION AND RE-ASSEMBLY :

To achieve higher end transparency, the TPDU (from transport layer)
size is independent of the maximum data allowed in a packet by the
subnet or the protocol. NL performs fragmentation, if required, and reassembly at the other end.

ROUTING OF PACKETS :
The network Layer enhanced with Routing and Congestion control is
responsible for submitting the packet to the final destination from the
source, irrespective of the no. of NEs and their connectivity. It utilizes
multiple data link interfaces to support end to end connectivity to the
transport layer.

LINK MANAGEMENT :
NL maintains the status of each link (LAP-B) associated with the NL.

3.2.1.2.4.

TRANSPORT LAYER :
It forms the fourth layer of the protocol stack. The following features shall be
supported.

CONNECTION AND BUFFER MANAGEMENT :

Transport layer is based on the connection oriented philosophy.
Various attributes and buffers are maintained for each connection .
After receiving positive acknowledgment from the peer side for the
data transmitted, the corresponding buffers can be freed.

20

C-DOT NMS

FUNCTIONAL SPECIFICATIONS OF CNMS

RELIABLE DATA TRANSFER :

The transport layer receives messages from the application layer in
terms of real time notifications or commands. Thus transport layer
handles and store the application PDU in its buffer according to the
maximum size negotiated. These PDUs are to be reliably transferred to
the other side. Any in-between problem like loss of link or sequence is
to be taken care by the transport layer without any notification to the
application process.

CREDIT BASED HIGHLY FLEXIBLE FLOW CONTROL :

The credit based flow control is similar to the sliding window flow
control. The only difference is that the window size is not fixed but is
dynamic. The peer end can control the traffic for the connection by
reducing or increasing the credit. Thus this way, the credit based flow
control is highly flexible and can adjust itself according to the load at
the receiver end. The maximum credit value is two as per the
recommendation of X.224.

CONNECTION CONTROL MANAGEMENT :

This involves availability of connections to high priority application
processes in case the number of allocated connection equals the total
number of transport connections that can be allocated. The arbiter
which is the connection control manager, then searches the connection
with the least priority. It then initiates the disconnection of that
connection and once the peer acknowledges the disconnection then the
freed connection is given to the higher priority application process that
had requested for a connection. Here the allocation of the priority is
the task of people in the application domain and the arbiter assumes
that the priorities have been assigned in advance statically.

MULTIPLEXING OF MULTIPLE APPLICATIONS ONTO LIMITED

TRANSPORT CONNECTIONS :
The transport layer multiplexes multiple transport connections onto a
single network connection if the source and the destination addresses
of all the transport connection are same of that of the network
connection. This helps in effective loading of the network connection
and also minimizes the resources to be needed at the network layer.

ETERNAL AND DYNAMIC CONNECTION SUPPORT :

To facilitate the communication between remote entities the transport
layer supports the concept of eternal and dynamic connection. The
eternal connections are those connection which are always present
once registered. They are fabricated in our design so that the remote
end always has a server to talk to and is globally known. For CM, FM

SPECIFICATIONS

21

Chapter 3

and PM there are eternal servers with the global connection numbers
of 1, 2 and 3 in the order. The registration of server is done by invoking
the TP primitive for connection establishment. In this the remote is
not specified and the procedure is called passive opening. Once the
passive open is done then the dynamic connections can be initiated to
the remote end. The initiation of dynamic connection is called active
opening. The transport layer can support any number of eternal
connections and up to nm dynamic connection where n is the number
of network connection and m is the multiplexing factor.

SERVER QUEUE TO STORE CONCURRENT REQUESTS TO A

SINGLE ETERNAL CONNECTION :
On the eternal connection there is always a eternal server attached to
it. Any transport connection request to the other end is delivered to
the eternal server as an indication. The eternal server on receiving any
indication from the peer end, forks a child server to cater to the need of
the peer client. The forked child server then replies by giving a
connection response. In the time period between the connection
indication to the connection response, the eternal connection remains
occupied and thus can not service any requests from any other client.
In order to compensate this, the server queue concept is introduced
whereby the extra connection indications are stored in the server
queue if the eternal connection is not free.

REASSIGNMENT AND RESYNCHRONISATION :

While the transport connection is still open and there is some fault
detected in the network connection due to which it gets disconnected.
The transport layer tries to re-establish the network connection. This
process is called reassignment.
In case of resets where the peer ends loses the synchronism, the
transport layer on either side sends the information regarding the
number of TPDUs already received. This way it is able to establish
the correct sequence of TPDUs received at either end. This process is
called resynchronisation.

FREEZING OF TRANSPORT CONNECTION :

In some cases it may happen that the release of transport connection
cannot be propagated to both ends due to failure of link. In such cases
one end might have an open transport connection waiting for a event
from peer end and the other end is just trying to initiate a new
connection. To prevent the new connection being assigned the old
value, the freezing of transport connection is introduced. Here a list of
all the free connection is maintained and whenever a connection is
assigned it is removed from the list. After the connection is freed, the

22

C-DOT NMS

FUNCTIONAL SPECIFICATIONS OF CNMS

connection number is added to the end of the list so it is frozen till all
the elements are allocated from the list.
3.2.2.

CNMS-WSF (CNMS-WORKSTATION FUNCTION)

The Workstation Function provides the means to interpret the management
information for the management information user. CNMS shall provide a
powerful and easy to use graphical user interface to support the various
management and maintenance functions. This interface shall be based upon
X11 R5/Motif1.2.

3.2.3.

CSAM-NEF (CSAM-NETWORK ELEMENT FUNCTION)

CSAM-NEF shall communicate with the CNMS-OSF for the purpose of being
monitored and/or controlled. The functional components constituting the
block CSAM-NEF are

3.2.3.1.

CSAM-NEF-MAF

CSAM-NEF-MCFq

CSAM-NEF-MCFecc

CSAM-NEF-MAF
FUNCTION

(CSAM-NEF-MANAGEMENT

APPLICATION

CSAM-NEF-MAF supports the following Management Function Areas in

support of the corresponding management functions of CNMS-OSF-MAF :

3.2.3.1.1.

Configuration management

Fault Management

Performance Management

CONFIGURATION MANAGEMENT
The configuration management shall maintain the complete configuration of
the equipment. It shall support following configuration management
functions.

System installation
System installation shall bring the system operational into the
network. It shall be performed after the initialization and boot up is
over. The installation shall also be possible with the help of PC based
LMI. The local manager shall provide the following data required for
installing the system at the request sent by the CM :

SPECIFICATIONS

NE family and type

NE address

23

Chapter 3

NMS (CNMS-OS) presence information

Timing reference selection

EOW related data

Payload configuration and network connectivity table

Protection Switching
The system shall support Dedicated Protection Ring. The request to
perform protection switching can be initiated either externally or
automatically.

Signalling of F1 data channel

F1 data channel request can be given from LMI or orderwire handset.

Network synchronisation
-

reference clock selection

quality of clocks

fallback order of clocks

holdover time

Payload mapping
deals with mapping of PDH traffic into STM-n frame and crossconnection of traffic between STM-n frames.

Record of equipment configuration data

Following is the list of equipment configuration data that shall be
maintained by the CM.

3.2.3.1.2.

NE identity

Payload configuration

Switch Matrix

Alarm thresholds

EOW related data

Network connectivity table

Timing reference and fallback order

FAULT MANAGEMENT
The fault management function shall comply with ITU-T Recommendation
G.784 and X.733. FM shall be responsible for collection, validation and
reporting of all the alarms occurring in the NE. It shall also maintain the

24

C-DOT NMS

FUNCTIONAL SPECIFICATIONS OF CNMS

current status of all the alarms. History of 150 alarms shall be provided. The
following functions are supported :

reporting of alarms on the basis of condition filters

maintain separate condition filters for CNMS, LMI and remote LMI.
These condition filters shall be configurable from the respective
interfaces.

allow / inhibit alarm reporting

enable / disable history recording

reporting of current status of alarms

reporting status of allow / inhibit alarm reporting

There shall be six severity levels of the alarms :

critical

major

minor

warning

indeterminate

clear

The above functions are provided for ITU-T specified as well as some
equipment specific alarms. For tables, refer to CSAM155 System
Specifications Document.
3.2.3.1.3.

PERFORMANCE MANAGEMENT
The performance management function shall comply with ITU-T
Recommendation G.784 and G.826. It shall handle the collection, monitoring
and reporting of performance parameters.
One second window shall be used to collect the accumulated performance
data or performance related information. The performance data shall be
stored for the period of 24 hours in 15 minutes registers and for past one
month in day registers. There shall be threshold values for 15 minute and
one day registers. Crossing of threshold values signify performance
degradation of the system and shall be notified to the user. The threshold
values shall be user configurable.
The reporting on all monitoring functions shall be user configurable through
LMI or CNMS. There shall be no monitoring during unavailable time (UAT).

SPECIFICATIONS

25

Chapter 3

Performance data in the system shall be specified as:

Code Violation

ES count

SES count

UAS count

The threshold values for these counters is calculated section wise as per
G.784. Refer to CSAM155 System Specifications Document for performance
parameters and related thresholds.
3.2.3.2.

CSAM-NEF-MCFq
(CSAM-NEF-MESSAGE
FUNCTION AT Q INTERFACE)

COMMUNICATION

CSAM-NEF-MCFq is related to the physical interface and the associated

protocol stack at the Q interface. It supports communication with CNMSOSF-MCFq. It terminates, routes or otherwise processes messages on the Q
interface. Refer to section 3.2.1.2 for the protocol stack specifications and the
features supported at each layer.
3.2.3.3.

CSAM-NEF-MCFecc
(CSAM-NEF-MESSAGE
FUNCTION AT ECC INTERFACE)

COMMUNICATION

CSAM-NEF-MCFecc is related to the physical interface and the associated

protocol stack at the ECC interface. It terminates, routes or otherwise
processes messages on the ECC. An Embedded Control Channel (ECC)
provides a logical operations channel between SDH NEs, utilizing a data
communications channel as its physical layer.
ECC is used for the transfer of operations, administration, maintenance and
provisioning messages across the SDH network elements.
The following protocol stack shall be used for the communication of
management messages over the SDH DCC .
PHYSICAL LAYER

SDH DCC (D1-D3)

DATA LINK LAYER

X.212 / X.222

NETWORK LAYER

X.213 / X.223

TRANSPORT LAYER

X.214 / X.224

(TP0, TP2, TP3 )

3.2.3.3.1.

ECC PHYSICAL LAYER :

The Embedded Control Channel uses Data Communication Channels as its
physical layer. Within an STM-N signal (Synchronous Transport Module -

26

C-DOT NMS

FUNCTIONAL SPECIFICATIONS OF CNMS

level N) there are two Data Communication Channels (DCC), comprising

bytes D1-D3 and D4 - D12.

3.2.3.3.2.

D1 - D3

192 kbps

D4 - D12

576 kbps

ECC DATA LINK LAYER :

This is the second layer of the four layer ECC protocol stack. Refer to section
3.2.1.2.2 for the features supported.

3.2.3.3.3.

ECC NETWORK LAYER :

It is the third layer of the ECC protocol stack. It supports Routing and
Congestion Control to rout the messages. Refer to section 3.2.1.2.3 for the
features supported.

3.2.3.3.4.

ECC TRANSPORT LAYER :

It is the fourth layer of the ECC protocol stack. Refer to section 3.2.1.2.4 for
the features supported.

SPECIFICATIONS

27

Chapter 4.

Documentation
The documentation provided shall be :
CNMS Users manual and Installation procedure.

28

C-DOT NMS

Chapter 5.

References

ITU-T : G.783, G.784, G.826

M.3010, M.3200, M.3300, M.3400,

X.733

V.24/V.28

ANSI : EIA RS-232C

C-DOT : CSAM155 Specifications,

specifications document

SPECIFICATIONS

CSAM155

software

requirement

29

Chapter 6.

Abbreviations
The following provides the expanded forms of the abbreviations used in the document,
along with the main references.

30

SDH

Synchronous Digital Hierarchy

STM-n

Synchronous Transport Module-level n

TMN

Telecommunication Management Network

CNMS

C-DOT SDH Network Management Systems

OS

Operations System

DCN

Data Communication Network

NE

Network Element

GNE

Gateway Network Element

MF

Mediation Function

CM

Configuration Management

PM

Performance Management

FM

Fault Management

MAF

Management Application Function

MCF

Message Communication Function

ECC

Embedded Control Channel

DCC

Data Communication Channel

UAT

Unavailable Time

ES

Error Seconds

SES

Severely Error Seconds

UAS

Unavailable Seconds

EOW

Engineering Order Wire

APS

Automatic Protection Switching

DPR

Dedicated Protection Ring

ITU-T

International Telecommunication Union

C-DOT NMS

Annexures

List of Annexures
A

List of Features in Release 1.0 of CNMS

Line Diagram of various Equipment Configurations

List of Alarms, Alarm types and Severity levels

List of Performance Parameters, their threshold ranges and default

threshold values

List of Functions available for each category of user

SPECIFICATIONS

31

Annexure A

List of Features in Release 1.0 of CNMS

Minimum configuration requirements of CNMS:
1.

RESOURCE CUSTOMISATION
Concerned with customising HP-VUE environment to suit the graphical
environment of CNMS.

2.

ETERNAL PROCESSES
Creation of daemon processes (protocol, CM_main, FM_main, FM_log_server,
RM_startup )

3.

BOOTUP RECOVERY
Ensures successful booting up of CNMS.

4.

SYSTEM ADMINISTRATION
Assuming the default user to be super-user, provides for addition/deletion and other
miscellaneous system admin functions:

1.

Add user

Delete user

List users

Current user

Change password

NETWORK CREATION/EDIT FEATURES

Facilitates the user to create the network as per the topology requirement and
provide the network information through the front end GUI. Following functions
are supported:

32

Creation of a new network/opening an existing network

Addition of NEs

Creation of interconnections between NEs

C-DOT NMS

LIST OF FEATURES IN RELEASE 1.0 OF CNMS

Select a connection to display connection details like VC-4 path trace, signal
label etc.

Delete NE/connection for editing purposes

Save the created network

Select a NE to display NE details (type, family etc.)

Close an open network

REL 1.0 MANAGEMENT FUNCTIONS

Configuration Management
1.

Initiate installation of the saved network

2.

Connection of manager to an operational network

3.

Payload configuration/reconfiguration for immediate demands and demand status

4.

Clock configuration/reconfiguration

5.

Orderwire configuration for selective call

6.

Setting of calender date and time at the NE

Fault management
1.

Alarm reporting schedule : for starting/inhibiting alarm reporting mechanism

2.

Alarm reporting filter : four types of filter support for controlling alarm reporting
mechanism of NEs

3.

History : periodic/on demand reporting of history to CNMS

4.

Current alarm status : to fetch currently outstanding alarms from the NE

5.

Log filter : to control the logging activity of reported alarms

6.

View log file : display of alarms transferred to a log file

7.

Summary : to display alarms logged during the past X hours

Performance management
1.

Get performance report from the NE of the performance parameters as specified in

the request by user.

2.

Maintain a database of the performance reports supplied by the NE.

3.

Provide a GUI for convenient viewing of this database.

4.

Provide a means for setting/changing schedules of reporting for various network

elements in the network.

SPECIFICATIONS

33

Annexure A

5.

Provide a means for setting/changing thresholds of various performance parameters

(es, ses, uas etc) for various NEs in the network.

34

C-DOT NMS

Annexure B

Line Diagrams of Various Equipment

Configurations
For the various equipment configurations supported by CNMS (given in section 1.2), the
line nomenclature and number of FE1 Cards shall be as follows:
1.

CA01-2F
This equipment shall be used for the two fibre DP ring topology.
FE1

FE

N
LINE2
P

LINE 1

6
2.

CA01-4F
This equipment shall be used for the linear case with protection.
N

LINE 1

LINE 3

LINE 4

LINE 2
6

10

11

Card 7 shall be protection card for card 6

SPECIFICATIONS

35

Annexure B

Card 11 shall be protection card for Card 10

3.

CH01(2F)
This equipment shall be used to provide hub connectivity to a two fibre DP ring.
N

LINE 2
N

LINE 1

10

11

LINE 4

LINE 3

For this configuration, cards 6 and 7 shall have DP Ring protection and cards 10 and 11
shall be configured for linear protection.
4.

CH01-4F
N

LINE 1

LINE 2

LINE 3

10

11

12
Line 5

13

LINE 4

LINE 6

Cards 6 ,7 and 10,11 shall be for line side.

Cards 12 and 13 shall be for the hub line.

36

C-DOT NMS

LINE DIAGRAMS OF VARIOUS EQUIPMENT CONFIGURATIONS

5.

CM01
N

LINE 1

LINE 2

FE1 cards are in slots 6 and 7 only with linear protection.

6.

CR01
N

LINE 1 Rx

LINE 1 Tx

LINE 2 Rx

LINE 2 Tx

LINE 3 Rx

LINE 3 Tx

LINE 4 Rx

LINE 4 Tx
6

10

11

FE1 cards are in slots 6 and 7. The signal from each line shall enter and be regenerated
from the same card.
A pair of optical fibre/cable coming from a FE1 card shall be designated with a line no.
FE1
Slot 6

Line1

Slot 7

Line2

Slot 10

Line3

Slot 11

Line 4

Slot 12

Line 5

Slot 13

Line 6

SPECIFICATIONS

37

Annexure B

Type of Connection
Two types of connection are defined for a TU.
Unidirectional connection -A TU is dropped and added from different FE1 Cards
Bi-directional Connection - Same Number of TU is added and dropped from the same FE1
card .
For each connection type the modes possible are unidirectional

bi-directional

- add

-add drop

- drop

- pass

- drop and pass

-add-drop pass

38

C-DOT NMS

Annexure C

List of Alarms, Alarm Types and

Severity Levels
1.

LIST OF ALARMS

Loss of Signal (LOS) :

For optical interface, whenever the power level of the incoming signal has
dropped to a level which is lower than that desired to cause BER of 1x10-3,
loss of signal is said to have occurred (G.958).
For electrical interface, input below 35 dB nominal for 10-255 consecutive
pulse intervals is detected by the line interface device as the loss of signal
(G.775).

Transmit Fail (Txfail) :

For optical interface, whenever the transmitter power level goes out of range,
-5 dBm to 0 dBm, transmit fail is said to have occurred (G.958).
For electrical interface, not applicable.

Loss of Frame (LOF) :

It indicates the failure of the equipment to detect the start of a new frame.
This alarm occurs when Out of Frame (OOF) state persists for T
milliseconds. To avoid intermittent OOF detection, OOF state is not cleared
until in-frame condition persists for T milliseconds. Suggested values of T :
0<=T<=3 (T=3 ms presently)

Excessive BER (ExBER) :

If BER evaluated from B2 bytes is found to be greater than 10-3, Excessive
BER is said to have occurred. (This condition should be detected in 1ms.)

Signal Degrade (SD) :

If BER evaluated from B2 byte is found to be greater than a pre-set threshold
in the range of 10-5 to 10-9. (This condition should be detected in 1 second to
10,000 seconds.)

Multiplex Section Far End Receive Failure (MS-FERF) or Multiplex Section

Remote Defect Indication (MS-RDI) :

SPECIFICATIONS

39

Annexure C

The presence of the pattern 110 in 6,7 & 8 bit positions of K2 byte is flagged
as MS-FERF. This pattern is received whenever the sink of this multiplex
section detects a SD.

Multiplex Section Alarm Indication Signal (MS-AIS) :

The presence of the pattern 111 in 6, 7 & 8 bit positions of K2 byte for at
least three consecutive frames is flagged as MS-AIS. This pattern is observed
whenever LOS/LOF are observed at the NE.

Administrative Unit - Loss of Pointer (AU-LOP) :

The AU pointer is used to reference dis-interleaved VC-3/4s. AU-LOP is
detected as per pointer processing algorithm. The detection of this condition
causes VC-3/4s inaccessible and hence All ONEs signal is propagated to
higher order path function.

Administrative Unit - Alarm Indication Signal (AU-AIS) :

It is an All ONEs signal, propagated to higher order path function as a result
of AU-LOP.

Loss of Multiframe (LOM or H4 Error) :

This alarm occurs when the n H4 bytes (H4 is multiframe indicator byte)
received consecutively are not correctly in sequence with any part of the
multiframe sequence. Suggested values of n : 2<=n<=10. (Presently, incorrect
sequence in one multiframe, n=4lues of n : 2<=n<=10. (Presently, incorrect
sequence in one multiframe, n=4).This alarm ceases to exist when n frames
are received consecutively correctly in sequence with part of the multiframe
sequence.

Higher Order Path-Far End Receive Failure (HP-FERF) or Higher Order

Path Remote Defect Indication (HP-RDI) :
HP-FERF is observed whenever bit 5 of G1 byte is set. This is set when the
remote path sink notices a AU-AIS.

Tributary Unit 12 - Loss of pointer (TU12-LOP) :

The TU pointer is used to reference the interleaved VC in VC-3/4. TU-LOP is
detected as per the pointer processing algorithm.

Higher Order Path Signal Label Mismatch (HP-SLM) :

This alarm occurs when the value of
provisioned value.

J1 byte received differs from the

Higher Order Path Trace Identifier Mismatch (HP-TIM) :

This alarm occurs when the value of J1 byte received differs from the
provisioned value.

40

C-DOT NMS

LIST OF ALARMS, ALARM TYPES AND SEVERITY LEVELS

Lower Order Path Signal Label Mismatch (LP-SLM) :

This alarm occurs when the value of bits 5, 6 & 7 of V5 byte differs from the
provisioned value. (NOT IMPLEMENTED)

Lower Order Path Trace Identifier Mismatch (LP-TIM) :

(NOT IMPLEMENTED)

Lower Order Path Far End Receive Failure (LP-FERF) or Lower Order Path
Remote Defect Indication (LP-RDI) :
This alarm is raised whenever bit 8 of V5 byte is set. This bit is set by the
path termination function of the sink on finding a TU-AIS.

E1 Loss of Signal (E1-LOS) :

E1-LOS is detected when the incoming PDH signal has no transitions i.e.
when the signal level is less than or equal to a signal level of 35 dB below
nominal for N consecutive pulse intervals where 10<=N<=255.

E1 Alarm Indication Signal (E1-AIS) :

An AIS defect at 2.048 kbps interface is detected when the incoming signal
has two or less zeros in each of two consecutive double frame periods (512
bits).

2.

Loss of Reference Clock :

LIST OF ALARM TYPES :

Alarm type identifies the ISO category of an alarm. The alarms are classified into
the following types :

3.

Communication Alarm : is associated with the process required to convey

information from one node to another in the network.

Quality of Service (QOS) alarm : is associated with degradation in the quality

of service.

Processing Error Alarm : is associated with a software fault.

Equipment Alarm : Is associated with an equipment fault.

Environmental Alarm : is associated with a condition related to an enclosure

in which the equipment resides.

SEVERITY LEVELS :
Severity characterises the enormity of an alarm. Following severity levels are
defined :

Critical

Major

SPECIFICATIONS

41

Annexure C

42

Minor

Warning

Clear

Indeterminate

C-DOT NMS

Annexure D

List of Performance Parameters, their

Threshold Ranges and Default
Threshold Values
Table 1: 1
IN-SERVICE PERFORMANCE MONITORING

Monitored
Section
R sec

M sec

HVC-VC4

Performan
ce
Parameter

Defects / Automobiles

Threshold
15 min.

Threshold
1 day

CV

B1 error count

1-13997

1-1343693

ES

B1 error

1-900

1-65535

SES

B1 error

1-255

1-4095

OFS

OOF

1-255

1-4095

UAS

As per G.826

1-255

1-4095

CV

B2 error

1-13997

1-1343693

ES

B2 error, MS-IS,MS_FREF

1-900

1-65535

SES

B2 error, MS-IS,MS_FREF

1-255

1-4095

PJC

PJE,NJE

--

--

PSC

Protection Switching

--

--

PSD

Protection Switching

--

--

UAS

As per G.826

1-255

1-4095

CV

B3 error count

1-13531

1-1298903

ES

B3,LOP,J1mm,C2mm,HP-FEBE.

1-900

1-65535

1-255

1-4095

1-255

1-4095

HP-FREF,AIS
HVC-VC4

SES

B3 error,LOP,J1mm,C2mm,
HP-FEBE,HP-FERF,AIS

UAS
SPECIFICATIONS

As per G.826

43

Annexure D
Monitored
Section
LVCVC3,VC12

Performan
ce
Parameter

Defects / Automobiles

CV

Threshold
15 min.

B3/V5 error count

Threshold
1 day

1-202

1-19354

(VC12)

(VC12)

1-4407

1-423015

(VC3)

(VC3)

ES

B3/V5 error.FEBE,FERE,TU-LOP, TUAIS,J1-J2mm,C2/V5mm,H4

SES

B3,FEBE,FERF,TU-LOP,TU-AIS,J1J2mm,C2/V5mm,H4

1-255

1-4095

UAS

As per G.826

1-255

1-4095

Section / Parameter

Rsect
LOS
LOF

Msect
UAT AIS LOP

HVC path
UAT AIS LOP

LVC path
UAT AIS

RSect
CV

ES

SES

OFS

UAS

CV

ES

SES

PSC

PSD

UAS

CV

ES

SES

UAS

MSect

HVC path

LVC path

44

C-DOT NMS

List of Performance Parameters, their Threshold Ranges and Default Threshold Values
Section / Parameter

Rsect
LOS
LOF

Msect
UAT AIS LOP

HVC path
UAT AIS LOP

LVC path
UAT AIS

CV

ES

SES

UAS

I -Inhibited
M-Monitored
Parameters during UAT will be inhibited in CMF-PM and monitored by LCU-PM.
Similarly parameters during alarm conditions shall be inhibited in LCU-PM

SPECIFICATIONS

45

Annexure E

List of Functions Available for Each

Category of User
Three categories of users are defined namely Super-user, Privileged user and ordinary
user.
Functions of Launch pad GUI as classified for the three types of users are :
FEATURE NAME

SUPER-USER

PRIVELEGED

ORDINARY

Network # New

Network # Open

Network # Close

Network # Delete

Network # Save

Edit # Add NE

Edit # Add Connection

Edit # Delete Connection

Edit # Delete NE

Mgmt # CM

Mgmt # FM

Mgmt # PM

Install

Connect to N/W

Reconfiguration

System Admin # Add New User

System Admin # Delete User

System Admin # List Users

System Admin # Current User

46

C-DOT NMS

LIST OF FUNCTIONS AVAILABLE FOR EACH CATEGORY OF USER

Functions of CM GUI as classified for the three types of users are :

FEATURE NAME

SUPER-USER

PRIVELEGED

ORDINARY

Payload # View traffic # View tributary map

Payload # View traffic # View port map

Payload # Add/Drop

Payload # Demand list

Order-wire # Set

Order-wire # View

Synchronisation # Synchronisation mode

Synchronisation # Clock quality and priority

Synchronisation # OIC # Lock out

Synchronisation # OIC #Clear lockout

Synchronisation # OIC # Switch & MPLL

mode

Synchronisation # Clear switch mode

Synchronisation # Get Synchronisation status

ALS # Set

ALS # View

Exit # CM exit

Set calender time

Functions of FM GUI as classified for the three types of users are :

FEATURE NAME

SUPER USER

PRIVELEGED
USER

Reporting # Surveillance control

Reporting#History#Get parameters

Reporting#History#Set parameters

Reporting#History#Request History

Reporting # AIS control # Set

Reporting # AIS control # View

Reporting # Optical parameters

Thresholds # Set

Thresholds # Get

SPECIFICATIONS

ORDINARY
USER

47

Annexure E
FEATURE NAME

SUPER USER

PRIVELEGED
USER

ORDINARY
USER

Log # View

Log # Summary

Localise # Localise

Trouble Admin # List trouble tickets

Trouble Admin # Open trouble ticket

View History

Current Alarm Status

View Surveillance

FM Exit # Exit

Functions of PM GUI as classified for the three types of users are :

FEATURE NAME

SUPER
USER

PRIVELEGED
USER

Reporting mode # Continuous reporting # Set

Reporting mode # Continuous reporting # View

Reporting mode # Scheduled reporting

Reporting mode # Dump reporting

Threshold # Set # Default Settings

Threshold # Set # New Settings

Threshold # View

Schedules # View

Schedules # Cancel

Log # Database# Threshold crossing report

Log # Database # Scheduled report

Log # Database # Continuous report

Log # Backup

PM Exit # Exit

48

ORDINARY
USER

C-DOT NMS