CNMSSPEC

7/29/2019 CNMSSPEC

http://slidepdf.com/reader/full/cnmsspec 1/46

C-DOT NMS

SPECIFICATIONS

7/29/2019 CNMSSPEC


Table of Content

Chap te r 1. Introduction ..............................................................................................................................5

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

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

Chap t er 2 . Operational Requirements.......................................................................................................8

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

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

Chap t er 3 . Functional Specifications of CNMS.......................................................................................10

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

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

Chap t er 4 . Documentation........................................................................................................................28

Chap t er 5 . References...............................................................................................................................29

Chap t er 6 . Abbreviations..........................................................................................................................30

Annexu r e s List of Annexures....................................................................................................................31

Ann exu r e A List of Features in Release 1.0 of CNMS..............................................................................32

Ann exu r e B Line Diagrams of Various Equipment Configurations ........................................................35

Ann exu r e C List of Alarms, Alarm Types and Severity Levels................................................................39

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

Ann exu r e E List of Functions Available for Each Category of User........................................................46

H:\ HOME\ CNMS\ CNMSSPEC.DOC April 24, 2000

7/29/2019 CNMSSPEC


SPECIFICATIONS 5

Chapter 1.

Introduction

C-DOT Network Management System (CNMS) shall manage a transport networkconsisting 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. Hubbingfeature shall also be supported.

CNMS shall manage the SDH network via a gateway network element through Qinterface. I t 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 thefull potential of SDH networks. It is a modular system which provides user friendlygraphical interface and a persistent database.

The CNMS specifications are derived from the overall TMN specifications.

7/29/2019 CNMSSPEC


Chapter 1

6 C-DOT NMS

1.1. NETWORK CONFIGURATIONS SUPPORTED

CNMS shall support a network topology of a RI NG with hub connectivity to linearchain of network elements.

Other topologies supported are linear or bus. The following network topologies canbe achieved using various configurations of the SDH network element :

! Linear network (with 1+1 protection)

! Ring network(2 fibre)

! Hub network

1.2. EQUIPMENT CONFIGURATIONS SUPPORTED :

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

CNMS-OS

Q I/F

DCN(OPTIONAL)

Q I/F

SDH

SDHNE

SDH

SDH

ECC(STM-1)ECC(STM-1)

ECC(STM-1)

ECC(STM-

TRI BS

SDHNE

SDHNE

SDHNE TRI B

TRI BS

TRI BS

(WITH HUB)

ECC(STM-1)

FIG-1 : NETWORK TOPOLOGY

GNE

7/29/2019 CNMSSPEC


INTRODUCTION

SPECIFICATIONS 7

• 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 isprovided at the hub.

7/29/2019 CNMSSPEC


8 C-DOT NMS

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

5 80 MHz PA7100 LC chip

5 Internal speaker (audio alarms)

5 Serial port (RS-232)

5 Parallel port (printer)

5 64MB RAM

5 1 GB hard disk

5 3.5” Floppy drive(1.44MB MFY ,external)

5 DAT drive

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

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

5 17” Colour monitor

2 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 bedeveloped 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 managementapplication functions like accounting management and also to upgrade the

7/29/2019 CNMSSPEC


OPERATIONAL REQUIREMENTS

SPECIFICATIONS 9

present application functions of fault, performance, configuration andsecurity management.

• I t shall be possible to upgrade the system to support other network topologiesconsisting of cross connect systems.

7/29/2019 CNMSSPEC


10 C-DOT NMS

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 :

• 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 (tobe added in later release).

• Inspection and configuration of the resources like

5 reference clock

5 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.

7/29/2019 CNMSSPEC


FUNCTIONAL SPECIF ICATIONS OF CNMS

SPECIFICATIONS 11

• Retrieval and display of performance parameter counts (both current andhistoric).

• 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.

3.2. BASIC FUNCTIONAL BLOCKS

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

• CNMS-OSF ( CNMS Operations System Function )

5 CNMS-OSF-MAF

5 CNMS-OSF-MCFq

• CNMS-WSF (CNMS Workstation Function)

• CSAM-NEF (CSAM Network Element Function)

5 CSAM-NEF-MAF

5 CSAM-NEF-MCFq

5 CSAM-NEF-MCFecc

7/29/2019 CNMSSPEC


Chapter 3

12 C-DOT NMS

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 humaninterface (CNMS-WSF) through user friendly X/Motif GUI. With the support

OSF

MAF

MCF

WSF

f ref. point

MCF

MCFecc MCFecc

MAF

NEF

MCFecc

MCFqMAF

MCFecc

NEF

MCFecc

MCFqMAF

MCFecc

NEF

q reference

FIG 2-FUNCTIONAL BLOCK

SDH NETWORK

7/29/2019 CNMSSPEC



SPECIFICATIONS 13

of information received from CSAM-NEF, it shall perform variousmanagement functions to execute remote provisioning with bandwidthallocation, path setting management, protection switching and service statemanagement; performance monitoring with logging, statistical analysis anddisplay; centralized monitoring with logging, real time display andlocalization of faults; user registration and login control.

The functional components constituting the block CNMS-OSF are :

5 CNMS-OSF-MAF

5 CNMS-OSF-MCFq

3 .2 .1 .1 . CNM S-OSF-M AF (CNM S-OSF-MA N AGEM EN T APPL I CAT I ON

FUNCT ION )

These Management Application Functions are the essential and underlyingpart of the OSF.

These are categorised into the following Management Function Areas :

5 Configuration management

5 Fault management

5 Performance management

5 Security management

3.2.1.1.1. CONFI GURATI ON MANAGEM EN T

The configuration management covers the Management Application

Functions (MAFs) which enable the user to create and modify themanagement model for both logical and physical resources within the SDHnetwork. It provides MAFs to exercise control over, identify, collect data fromand provide data to NEs.

The following functions shall be provided:

5 Installation of the Network and/or NE.

Installation is the process of bringing up a resource (network andequipments) to the default configuration. It is assumed that the firstNetwork Element that gets installed is the Gateway Network Element

(gateway of the n/w to CNMS-OS). Each NE establishes contact withthe CNMS-OS (called the manager), once it gets its basic identityinformation. After the handshaking of control messages, theNE/network enters into “provisioning” state.

5 Provisioning the network and/or NE:

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

7/29/2019 CNMSSPEC


Chapter 3

14 C-DOT NMS

configuration information is downloaded onto each NE, following whichthe NE/network enters into the “In-service” state.

5 NE status and control:

Complete NE configuration shall be maintained by the CNMS-OS. Itsends/receives configuration/change in configuration to/from each NEon demand or autonomously. The following configuration informationshall be maintained and sent to each NE to configure thecorresponding units.

1. Synch r on i s a t i on : Each NE shall be configured for itssynchronization reference as well as the Clock generator mode assynchronous/free-running/holdover or internal.

2. N etwo r k conn ec t i v i t y : According to the topology of the networkcreated by the operator, the neighbours of each NE shall bemaintained. The connectivity of each NE from any other NE in the

network shall also be maintained for the DCC communication.

3. Pay l oad : Every demand for payload given by the user shall bechecked for the availability of the tributary ports and bandwidth. I f the demands can be routed then the payload is mapped into theSTM frame otherwise port/bandwidth unavailability is informed tothe user.

4. Orde r -w i r e : Order-wire related information including the selectivecall 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. Pa t h Mon i t or i n g : Path connectivity is monitored for each demand

and for each connection through path trace and signal label bytes of POH.

6. Ca r d S t a t u s: The card status and configuration of each card inthe NE shall be maintained.

7. L i ne i n t e r f a ces : The configuration of the line interfaces(optical/electrical) for each line shall be maintained.

8.Pr o tec t i on sta te :

The protection switch state is maintained. Eachtime, protection switching occurs, the status is informed to themanager.

5 Protection switching:

Following protection switching commands can be initiated by the userfor maintenance purpose-

- FSR- Forced switch for Ring

7/29/2019 CNMSSPEC



SPECIFICATIONS 15

- MSR-Manual switch for Ring

- EXR-Exerciser for signalling

- LOP-Lock out of protection

5 Routing of the Payload:

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

5 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

5 Reconfiguration of the network:

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

5 Maintenance of Network information:

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

-Information of the network like name, topology, size, state of thenetwork and the information of each NE in the network likelabel, 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.

3.2.1.1.2. FAU L T M ANAGEM EN T

Fault management is a set of functions which enable the detection, reportingand localization of fault conditions that occur in a SDH network. I t shallprovide alarm surveillance and maintenance of a database of alarms

The following functions shall be supported

5 Alarm Surveillance:

7/29/2019 CNMSSPEC


Chapter 3

16 C-DOT NMS

- I t is mainly concerned with the alarm reports from the NEs. Itsupports

- 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

5 Alarm Logging

It facilitates logging of all the reported alarms. Once the log exceeds apredefined value the alarms are flushed into system log files followingwhich the user can take back up.

- Selective logging of reported alarms with a provision to log allreported 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

5 Alarm localisation

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

5 Trouble administration

It is concerned with generation of troubles on identification of rootalarms in the network. Each trouble shall be identified by a uniquetrouble id. and it contains a brief description of the trouble. Thetrouble is automatically deleted on cessation of the root cause.

3.2.1.1.3. PERFORMAN CE MANAGEMEN T

Performance Management provides functions to evaluate and report upon thebehavior of telecommunication equipment and the effectiveness of thenetwork or network element.

It does the function of monitoring the SDH network by collecting theperformance related data (i.e. values of the various performance parameters)from the NE .The following functions shall be supported:

5 Performance Monitoring :

7/29/2019 CNMSSPEC



SPECIFICATIONS 17

I t involves fetching the performance parameter values from the Nes. Threshold crossing notifications for the parameters are also sent by theNes. 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 inthe past data. He can request for all parameters or select someparameters 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 theschedules set. Schedules can be set for all parameters or selectedparameters.

- Get Continuous Report:

I f the user wants performance parameter reports every 15minutes then he selects continuous reporting mode. He canrequest for all parameters or selected parameters.

DEFAULT REPORTING MODE: Continuous Reporting of all parameters.

5 Performance Control:

It shall involve changing the attributes related to performancemonitoring. The attributes are performance parameter thresholds andreporting 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 continuousas well as scheduled reporting (except dump request) butautonomous reporting of threshold crossing is not affected.

-Set Thresholds :

Thresholds for performance parameters shall be set by the useras per the specified ranges.

5 Performance Database:

This feature facilitates logging of the reports. The scheduled andcontinuous reports are logged into separate databases. Dump reports

7/29/2019 CNMSSPEC


Chapter 3

18 C-DOT NMS

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

- 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.

3.2.1.1.4. SECURI TY M AN AGEM EN T

I t deals with the aspects of security access relating to management functions. The following System Administration functions are supported :

5 Create User

5 Delete User

5 List User

5 Working User

5 Change Password

The users are categorized into three types :

5 Super-user

5 Privileged user

5 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 includingSystem Administration functions of ‘Create User’ and ‘Delete User’. The userwho can login first after installation is the super-user. Further, he createsother users.

Privileged User : A privileged user is authorized to perform all the

management functions of CM, FM and PM but the System Administrativefunctions like ‘Create User’ and ‘Delete User’ are not in his domain.

Ordinary User : An ordinary user is not authorized to perform the functionsof Network Creation, defining the configuration or setting any parameter of the NE/network. He can perform the monitoring functions only.

7/29/2019 CNMSSPEC



SPECIFICATIONS 19

3 .2 .1 .2 . CNMS-OSF-MCFq (CNMS-OSF-MESSAGE COMMUNICAT ION

FUNCT ION AT Q IN TERFACE )

CNMS-OSF-MCFq is related to the physical interface and the associatedprotocol stack at the q reference point. Reference point q is between CNMS-OSF and CSAM-NEF, called Q interface. This interface shall support bi-

directional data transfer for the management of SDH network. I t shall have afour layer protocol stack. The management applications shall be developedusing 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. PHYSI CAL L AYER :

I t shall form the first layer of the four layer stack. It shall conform to the EIARS-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. DAT A L I NK LAYER :

I t shall form the second layer of the four layer stack. The features supportedshall be:

5 CONNECTION ESTABLISHMENT AND RELEASE :

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

5 FL OW CONTROL :

Data shall be transferred after the connection is established. Flowcontrol is required to ensure data transfer in proper sequence and toprevent data loss and buffer overflows.

5 DETECTION OF ERRORS & RECOVERY :

L ink shall be reset and re-established in case of abnormal linkconditions. CRC is required to check data integrity.

7/29/2019 CNMSSPEC


Chapter 3

20 C-DOT NMS

3.2.1.2.3. NETWORK LAYER :

Network Layer forms the third layer of the four layer stack. I t shall supportthe following features :

5 CONNECTION MANAGEMENT :

The Network Layer simulates multiple logical connections over asingle data link connection. I t manages each logical connection for itsestablishment as well as release.

5 DATA TRANSFER :

It takes data from Transport Layer (TPDU) and hands it over to theother end Transport Layer as it is. For each connection, NL store upto8 TPDUs, each of maximum size 2k.

5 FL OW CONTROL :

Flow control is required to regulate the information transfer. Thesliding window flow control with a window size 2 shall be used.

5 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 thesubnet or the protocol. NL performs fragmentation, if required, and re-assembly at the other end.

5 ROUTING OF PACKETS :

The network Layer enhanced with Routing and Congestion control is

responsible for submitting the packet to the final destination from thesource, irrespective of the no. of NEs and their connectivity. It utilizesmultiple data link interfaces to support end to end connectivity to thetransport layer.

5 LINK MANAGEMENT :

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

3.2.1.2.4. TRANSPORT L AYER :

I t forms the fourth layer of the protocol stack. The following features shall be

supported.5 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 thedata transmitted, the corresponding buffers can be freed.

7/29/2019 CNMSSPEC



SPECIFICATIONS 21

5 RELIABLE DATA TRANSFER :

The transport layer receives messages from the application layer interms of real time notifications or commands. Thus transport layerhandles and store the application PDU in its buffer according to themaximum size negotiated. These PDUs are to be reliably transferred to

the other side. Any in-between problem like loss of link or sequence isto be taken care by the transport layer without any notification to theapplication process.

5 CREDIT BASED HIGHLY FLEXIBLE FLOW CONTROL :

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

5 CONNECTION CONTROL MANAGEMENT :

This involves availability of connections to high priority applicationprocesses in case the number of allocated connection equals the totalnumber of transport connections that can be allocated. The arbiterwhich is the connection control manager, then searches the connectionwith the least priority. I t then initiates the disconnection of thatconnection and once the peer acknowledges the disconnection then thefreed connection is given to the higher priority application process that

had requested for a connection. Here the allocation of the priority isthe task of people in the application domain and the arbiter assumesthat the priorities have been assigned in advance statically.

5 MULTIPLEXING OF MULTIPLE APPLICATIONS ONTO LIMITED TRANSPORT CONNECTIONS :

The transport layer multiplexes multiple transport connections onto asingle network connection if the source and the destination addressesof all the transport connection are same of that of the networkconnection. This helps in effective loading of the network connectionand also minimizes the resources to be needed at the network layer.

5 ETERNAL AND DYNAMIC CONNECTION SUPPORT :

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

7/29/2019 CNMSSPEC


Chapter 3

22 C-DOT NMS

and PM there are eternal servers with the global connection numbersof 1, 2 and 3 in the order. The registration of server is done by invokingthe TP primitive for connection establishment. In this the remote isnot specified and the procedure is called passive opening. Once thepassive open is done then the dynamic connections can be initiated tothe remote end. The initiation of dynamic connection is called active

opening. The transport layer can support any number of eternalconnections and up to nm dynamic connection where n is the numberof network connection and m is the multiplexing factor.

5 SERVER QUEUE TO STORE CONCURRENT REQUESTS TO ASINGLE ETERNAL CONNECTION :

On the eternal connection there is always a eternal server attached toit. Any transport connection request to the other end is delivered tothe eternal server as an indication. The eternal server on receiving anyindication 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 aconnection response. In the time period between the connectionindication to the connection response, the eternal connection remainsoccupied and thus can not service any requests from any other client.In order to compensate this, the server queue concept is introducedwhereby the extra connection indications are stored in the serverqueue if the eternal connection is not free.

5 REASSIGNMENT AND RESYNCHRONISATION :

While the transport connection is still open and there is some faultdetected in the network connection due to which it gets disconnected.

The transport layer tries to re-establish the network connection. Thisprocess is called reassignment.

In case of resets where the peer ends loses the synchronism, thetransport layer on either side sends the information regarding thenumber of TPDU’s already received. This way it is able to establishthe correct sequence of TPDU’s received at either end. This process iscalled resynchronisation.

5 FREEZING OF TRANSPORT CONNECTION :

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

7/29/2019 CNMSSPEC



SPECIFICATIONS 23

connection number is added to the end of the list so it is frozen till allthe 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 apowerful and easy to use graphical user interface to support the variousmanagement and maintenance functions. This interface shall be based uponX11 R5/Motif1.2.

3.2.3. CSAM-NEF (CSAM-NETWORK ELEMENT FUNCTION)

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

5 CSAM-NEF-MAF

5 CSAM-NEF-MCFq

5 CSAM-NEF-MCFecc

3 .2 .3 .1 . CSAM-NEF-MAF (CSAM-NEF-MANAGEMENT APPL ICAT ION

FUNCT ION

CSAM-NEF-MAF supports the following Management Function Areas insupport of the corresponding management functions of CNMS-OSF-MAF :

5 Configuration management

5 Fault Management

5 Performance Management

3.2.3.1.1. CONFI GURATI ON MANAGEM EN T

The configuration management shall maintain the complete configuration of the equipment. I t shall support following configuration managementfunctions.

5 System installation

System installation shall bring the system operational into the

network. I t shall be performed after the initialization and boot up isover. The installation shall also be possible with the help of PC basedLMI. The local manager shall provide the following data required forinstalling the system at the request sent by the CM :

- NE family and type

- NE address

7/29/2019 CNMSSPEC


Chapter 3

24 C-DOT NMS

- NMS (CNMS-OS) presence information

- Timing reference selection

- EOW related data

- Payload configuration and network connectivity table

5 Protection Switching

The system shall support Dedicated Protection Ring. The request toperform protection switching can be initiated either externally orautomatically.

5 Signalling of F1 data channel

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

5 Network synchronisation

- reference clock selection

-quality of clocks

- fallback order of clocks

- holdover time

5 Payload mapping

deals with mapping of PDH traffic into STM-n frame and cross-connection of traffic between STM-n frames.

5 Record of equipment configuration data

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

- NE identity

- Payload configuration

- Switch Matrix

- Alarm thresholds

- EOW related data

- Network connectivity table

- Timing reference and fallback order

3.2.3.1.2. FAU L T M ANAGEM EN T

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

7/29/2019 CNMSSPEC



SPECIFICATIONS 25

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

5 reporting of alarms on the basis of condition filters

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

interfaces.

5 allow / inhibit alarm reporting

5 enable / disable history recording

5 reporting of current status of alarms

5 reporting status of allow / inhibit alarm reporting

5 There shall be six severity levels of the alarms :

5 critical

5 major5 minor

5 warning

5 indeterminate

5 clear

The above functions are provided for ITU-T specified as well as someequipment specific alarms. For tables, refer to CSAM155 SystemSpecifications Document.

3.2.3.1.3. PERFORMAN CE MANAGEMEN T

The performance management function shall comply with ITU-TRecommendation G.784 and G.826. I t shall handle the collection, monitoringand reporting of performance parameters.

One second window shall be used to collect the accumulated performancedata or performance related information. The performance data shall bestored for the period of 24 hours in 15 minutes registers and for past onemonth in day registers. There shall be threshold values for 15 minute andone day registers. Crossing of threshold values signify performance

degradation of the system and shall be notified to the user. The thresholdvalues shall be user configurable.

The reporting on all monitoring functions shall be user configurable throughLMI or CNMS. There shall be no monitoring during unavailable time (UAT).

7/29/2019 CNMSSPEC


Chapter 3

26 C-DOT NMS

Performance data in the system shall be specified as:

5 Code Violation

5 ES count

5 SES count

5 UAS count

The threshold values for these counters is calculated section wise as perG.784. Refer to CSAM155 System Specifications Document for performanceparameters and related thresholds.

3 .2 .3 .2 . CSAM-NEF-MCFq (CSAM-NEF-MESSAGE COMMUNICAT ION

FUNCT ION AT Q IN TERFACE )

CSAM-NEF-MCFq is related to the physical interface and the associatedprotocol stack at the Q interface. It supports communication with CNMS-OSF-MCFq. It terminates, routes or otherwise processes messages on the Qinterface. Refer to section 3.2.1.2 for the protocol stack specifications and thefeatures supported at each layer.

3.2 .3 .3 . CSAM -N EF -M CFecc (CSAM-NE F-MESSAGE COMMUN I CAT I ON

FUNCT ION AT ECC IN TERFACE )

CSAM-NEF-MCFecc is related to the physical interface and the associatedprotocol stack at the ECC interface. It terminates, routes or otherwiseprocesses messages on the ECC. An Embedded Control Channel (ECC)provides a logical operations channel between SDH NEs, utilizing a datacommunications channel as its physical layer.

ECC is used for the transfer of operations, administration, maintenance andprovisioning 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 L AYER :

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

7/29/2019 CNMSSPEC



SPECIFICATIONS 27

level N) there are two Data Communication Channels (DCC), comprisingbytes D1-D3 and D4 - D12.

D1 - D3 : 192 kbps

D4 - D12 : 576 kbps

3.2.3.3.2. ECC DAT A L I NK LAYER :

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

3.2.3.3.3. ECC NETWORK LAYER :

I t is the third layer of the ECC protocol stack. I t supports Routing andCongestion Control to rout the messages. Refer to section 3.2.1.2.3 for thefeatures supported.

3.2.3.3.4. ECC TRANSPORT LAYER :

I t is the fourth layer of the ECC protocol stack. Refer to section 3.2.1.2.4 forthe features supported.

7/29/2019 CNMSSPEC


28 C-DOT NMS

Chapter 4.

Documentation

The documentation provided shall be :

CNMS Users’ manual and Installation procedure.

7/29/2019 CNMSSPEC


SPECIFICATIONS 29

Chapter 5.

References

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

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

5 X.733

5 V.24/V.28

• ANSI : EIA RS-232C

• C-DOT : CSAM155 Specifications, CSAM155 software requirementspecifications document

7/29/2019 CNMSSPEC


30 C-DOT NMS

Chapter 6.

Abbreviations

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

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

7/29/2019 CNMSSPEC


SPECIFICATIONS 31

Annexures

List of Annexures

A List of Features in Release 1.0 of CNMS

B Line Diagram of various Equipment Configurations

C List of Alarms, Alarm types and Severity levels

D List of Performance Parameters, their threshold ranges and defaultthreshold values

E List of Functions available for each category of user

7/29/2019 CNMSSPEC


32 C-DOT NMS

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 graphicalenvironment 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 othermiscellaneous system admin functions:

• Add user

• Delete user

• List users

• Current user

• Change password

1. 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 functionsare supported:

• Creation of a new network/opening an existing network

• Addition of NEs

• Creation of interconnections between NEs

7/29/2019 CNMSSPEC


LI ST OF FEATURES IN RELEASE 1.0 OF CNMS

SPECIFICATIONS 33

• Select a connection to display connection details like VC-4 path trace, signallabel 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

Con f i g u r a t i on M an agemen t

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

Fau l t ma nagemen t

1. Alarm reporting schedule : for starting/inhibiting alarm reporting mechanism

2. Alarm reporting filter : four types of filter support for controlling alarm reportingmechanism 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

Per f o rm an ce ma na gemen t

1. Get performance report from the NE of the performance parameters as specified inthe 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 networkelements in the network.

7/29/2019 CNMSSPEC


Annexure A

34 C-DOT NMS

5. Provide a means for setting/changing thresholds of various performance parameters(es, ses, uas etc) for various NEs in the network.

7/29/2019 CNMSSPEC


SPECIFICATIONS 35

Annexure B

Line Diagrams of Various EquipmentConfigurations

For the various equipment configurations supported by CNMS (given in section 1.2), theline 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.

2. CA01-4F

This equipment shall be used for the linear case with protection.

Card 7 shall be protection card for card 6

LINE 1N

PLINE2

N

P

FE1 FE

6 7

LINE 2

LINE 1

N P N P

6 7

LINE 3

LINE 4

10 11

7/29/2019 CNMSSPEC


Annexure B

36 C-DOT NMS

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.

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

4. CH01-4F

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

Cards 12 and 13 shall be for the hub line.

LINE 2

LINE 1

N P N P

6 7

LINE 3

LINE 4

10 11 12 13

N P

Line 5 LI NE 6

N P

N

P

LINE 2LINE 1

6 7 10 11

N

P

7/29/2019 CNMSSPEC


LI NE DIAGRAMS OF VARIOUS EQUIPMENT CONFIGURATIONS

SPECIFICATIONS 37

5. CM01

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

6. CR01

FE1 cards are in slots 6 and 7. The signal from each line shall enter and be regeneratedfrom 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

LINE 2

LINE 1

N P

6 7

LI NE 2 Rx

LI NE 1 Rx

N P N P

6 7

LI NE 3 Rx

LI NE 4 Rx

10 11

LI NE 1 Tx

LI NE 2 Tx

LI NE 3 Tx

LINE 4 Tx

7/29/2019 CNMSSPEC


Annexure B

38 C-DOT NMS

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

7/29/2019 CNMSSPEC


SPECIFICATIONS 39

Annexure C

List of Alarms, Alarm Types andSeverity 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 consecutivepulse 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 clearedunti l in-frame condition persists for ‘T’ milliseconds. Suggested values of T :0<=T<=3 (T=3 ms presently)

• Excessive BER (ExBER) :

I f 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) :

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

• Multiplex Section Far End Receive Failure (MS-FERF) or Multiplex SectionRemote Defect I ndication (MS-RDI ) :

7/29/2019 CNMSSPEC


Annexure C

40 C-DOT NMS

The presence of the pattern ‘110’ in 6,7 & 8 bit positions of K2 byte is flaggedas MS-FERF. This pattern is received whenever the sink of this multiplexsection detects a SD.

• Multiplex Section Alarm Indication Signal (MS-AI S) :

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 observedwhenever 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 isdetected as per pointer processing algorithm. The detection of this conditioncauses VC-3/4s inaccessible and hence All ONEs signal is propagated tohigher order path function.

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

It is an All ONEs signal, propagated to higher order path function as a resultof 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 themultiframe sequence. Suggested values of n : 2<=n<=10. (Presently, incorrectsequence in one multiframe, n=4lues of n : 2<=n<=10. (Presently, incorrectsequence in one multiframe, n=4).This alarm ceases to exist when ‘n’ framesare received consecutively correctly in sequence with part of the multiframesequence.

• Higher Order Path-Far End Receive Failure (HP-FERF) or Higher OrderPath Remote Defect Indication (HP-RDI) :

HP-FERF is observed whenever bit 5 of G1 byte is set. This is set when theremote 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 isdetected as per the pointer processing algorithm.

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

This alarm occurs when the value of J 1 byte received differs from theprovisioned value.

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

This alarm occurs when the value of J 1 byte received differs from theprovisioned value.

7/29/2019 CNMSSPEC


LI ST OF ALARMS, ALARM TYPES AND SEVERITY LEVELS

SPECIFICATIONS 41

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

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

• Lower Order Path Trace Identifier Mismatch (LP-TI M) :

(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 thepath 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 belownominal 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 signalhas two or less zeros in each of two consecutive double frame periods (512bits).

• Loss of Reference Clock :

2. LIST OF ALARM TYPES :

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

the following types :• 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 qualityof 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 enclosurein which the equipment resides.

3. SEVERITY LEVELS :

Severity characterises the enormity of an alarm. Following severity levels aredefined :

• Critical

• Major

7/29/2019 CNMSSPEC


Annexure C

42 C-DOT NMS

• Minor

• Warning

• Clear

• Indeterminate

7/29/2019 CNMSSPEC


SPECIFICATIONS 43

Annexure D

List of Performance Parameters, theirThreshold Ranges and Default

Threshold Values

Table 1: 1IN-SERVICE PERFORMANCE MONITORING

MonitoredSection

Performance

Parameter

Defects / Automobiles Threshold15 min.

Threshold1 day

R sec 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-4095M sec 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

PJ C PJ E,NJ E -- --

PSC Protection Switching -- --

PSD Protection Switching -- --

UAS As per G.826 1-255 1-4095

HVC-VC4 CV B3 error count 1-13531 1-1298903

ES B3,LOP,J 1mm,C2mm,HP-FEBE.

HP-FREF,AIS

1-900 1-65535

HVC-VC4 SES B3 error,LOP,J 1mm,C2mm,

HP-FEBE,HP-FERF,AIS

1-255 1-4095

UAS As per G.826 1-255 1-4095

7/29/2019 CNMSSPEC


Annexure D

44 C-DOT NMS

MonitoredSection

Performance

Parameter

Defects / Automobiles Threshold15 min.

Threshold1 day

LVC-VC3,VC12

CV B3/V5 error count 1-202

(VC12)

1-4407

(VC3)

1-19354

(VC12)

1-423015

(VC3)

ES B3/V5 error.FEBE,FERE,TU-LOP, TU-AIS,J 1-J 2mm,C2/V5mm,H4

SES B3,FEBE,FERF,TU-LOP,TU-AIS,J 1- J 2mm,C2/V5mm,H4

1-255 1-4095

UAS As per G.826 1-255 1-4095

Section / Parameter Rsect

LOS LOFMsect

UAT AIS LOP

HVC path

UAT AIS LOPLVC pathUAT AIS

RSect

CV

ES

SES

OFS

UAS

I I

I I

I I

I I

M M

M M M

M M M

M M M

M M M

M M M

M M M

M M M

M M M

M M M

M M M

M M

M M

M M

M M

M M

MSect

CV

ES

SES

PSC

PSD

UAS

I I

I I

I I

I M

I M

I M

I I M

I I M

I I M

M M M

M M M

M M M

M M M

M M M

M M M

M M M

M M M

M M M

M M

M M

M M

M M

M M

M M

HVC path

CV

ES

SES

UAS

I I

I I

I I

M M

I I M

I I M

I I M

M M M

I I M

I I M

I I M

M M M

M M

M M

M M

M M

LVC path

7/29/2019 CNMSSPEC


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

SPECIFICATIONS 45

Section / Parameter RsectLOS LOF

MsectUAT AIS LOP

HVC pathUAT AIS LOP

LVC pathUAT AIS

CV

ES

SES

UAS

I I

I I

I I

M M

I I I

I I I

I I I

M M M

I I I

I I I

I I I

M M M

I I

I I

I I

M M

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

7/29/2019 CNMSSPEC


46 C-DOT NMS

Annexure E

List of Functions Available for EachCategory of User

Three categories of users are defined namely Super-user, Privileged user and ordinaryuser.

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 Υ Υ Υ

7/29/2019 CNMSSPEC


LI ST OF FUNCTIONS AVAILABLE FOR EACH CATEGORY OF USER

SPECIFICATIONS 47

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 Υ Y Y

Payload# View traffic# View port map Υ Υ Υ

Payload# Add/Drop Υ Y

Payload# Demand list Υ Y

Order-wire# Set Υ Y

Order-wire# View Υ Y Y

Synchronisation# Synchronisation mode Υ Y

Synchronisation# Clock quality and priority Υ Υ

Synchronisation# OIC # Lock out Υ Υ

Synchronisation# OIC #Clear lockout Υ Υ

Synchronisation# OIC # Switch & MPLLmode

Υ Υ

Synchronisation# Clear switch mode Υ Υ

Synchronisation# Get Synchronisation status Υ Υ Y

ALS# Set Υ Υ

ALS# View Υ Υ Y

Exit# CM exit Y Y Y

Set calender time Y

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

FEATURE NAME SUPER USER PRIVELEGEDUSER

ORDINARY USER

Reporting# Surveil lance control Υ Υ

Reporting#History#Get parameters Υ Υ Υ

Reporting#History#Set parameters Υ Υ

Reporting#

History#

Request History Υ

Υ

Υ

Reporting# AI S control # Set Υ Υ

Reporting# AI S control # View Υ Υ Y

Reporting# Optical parameters Υ Υ Υ

Thresholds# Set Υ Υ

Thresholds# Get Υ Υ Υ

7/29/2019 CNMSSPEC


Annexure E

FEATURE NAME SUPER USER PRIVELEGEDUSER

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 SUPERUSER

PRIVELEGEDUSER

ORDINARY USER

Reporting mode# Continuous reporting# Set Υ Υ

Reporting mode# Continuous reporting# View Υ Υ Y

Reporting mode# Scheduled reporting Υ Υ

Reporting mode# Dump reporting Υ Υ Y

Threshold# Set# Default Settings Υ Υ

Threshold# Set# New Settings Υ Υ

Threshold# View Υ Υ Y

Schedules# View Υ Υ Υ

Schedules# Cancel Υ Υ

Log# Database# Threshold crossing report Υ Υ Υ

Log# Database# Scheduled report Υ Υ Y

Log# Database# Continuous report Υ Υ Υ

Log# Backup Υ Υ Υ

PM Exit# Exit Υ Υ Υ

Date post:	14-Apr-2018
Category:	Documents
Upload:	mainkeizer
View:	214 times
Download:	0 times

CNMSSPEC

Documents