02 - alcatel 1320ct training manual

Alcatel 1320CT 1.7.xOperation

Training manual8AS 90001 1860 VH ZZA Ed. 05

Edition 2004

© All rights reserved. Passing on and copying of this document, use and communication of its contents not

permitted without written authorization from Alcatel

© Alcatel University - 8AS 90001 1860 VH ZZA Ed.05 Page 0.2

Page intentionally left blank

Note : Please print this document with comments pages


Contents

Alcatel 1320CT 1.7.x Operation 8AS 90001 1860 VH ZZA1 Equipment view opening……………………………………………………… 1.1

1.1 Introduction………………………………………………………………………………..1.31.2 1320CT start-up…………………………………………………………………………..1.51.3 NE supervision start-up…………………………………………………………………. 1.81.4 NE log in………………………………………………………………………………….. 1.101.5 NE restart………………………………………………………………………………….1.121.6 Navigation in NE view……………………………………………………………………1.141.7 ISA boards supervision..............................................................................................1.18

2 Subrack and board declaration……………………………………………… 2.1

2.1 Local access request……………………………………………………………………. 2.32.2 Remote inventory display………………………………………………………………..2.52.3 Object administrative state modification………………………………………………. 2.102.4 Object declaration……………………………………………………………………….. 2.132.5 MIB management………………………………………………………………………... 2.18

3 Communication parameter configuration…………………………………..3.1

3.1 Overview on comm & routing domain…………………………………………………. 3.33.2 Local configuration………………………………………………………………………. 3.53.3 LAPD configuration……………………………………………………………………… 3.73.4 Ethernet configuration……………………………………………………………………3.113.5 OS configuration………………………………………………………………………….3.143.6 RAP/MESA configuration………………………………………………………………..3.163.7 IP configuration..........................................……………………………………………. 3.193.8 Tunneling configuration..........................................…………………………………... 3.273.9 Network Time Protocol configuration....………………………………………………..3.38


Contents

4 Network topology creation…………………………………………………….4.1

4.1 Map/Submap/NE creation……………………………………………………………….4.34.2 Map/Submap/NE management…………………………………………………………4.9

5 Alarm management…………………………………………………………….. 5.1

5.1 External point management……………………………………………………………..5.35.2 Alarm notification………………………………………………………………………… 5.75.3 Alarm identification in NE view………………………………………………………….5.115.4 ASAP management………………………………………………………………………5.185.5 NE time check…………………………………………………………………………….5.265.6 AS application handling………………………………………………………………….5.28

6 Administration for operators………………………………………………….6.1

6.1 NE software download…………………………………………………………………...6.36.2 CT environment management…………………………………………………………..6.116.3 Log files display………………………………………………………………………….. 6.17

Appendix 1 Glossary……………………………………………………………….A1.1


© Alcatel University - 8AS 90001 1860 VT ZZA Ed.051.1

1 Equipment view opening


1.2

1 Equipment view openingSession presentation

Ë Objective: to be able to start-up the 1320CT and to open the equipment view

Ë Program: 1.1 Introduction1.2 1320CT start-up1.3 NE supervision start-up1.4 NE log in1.5 NE restart1.6 Navigation in NE view1.7 ISA boards supervision




1.1 Introduction


1.4

1.1 Introduction

RS232 cable

F interface

Software product for management

to install in the PC

Software product for download to update

the NE

CD ROM

Ë The Craft Terminal (CT) is generally a personal computer (PC), connected through the F interface for local management of Network Element (NE). With the remote CT application, it is possible to manage up to 32 NEs via the DCCM / DCCR channels.

Ë The software products are distributed by Alcatel in a CD-ROM:¸ The software products used for management permit the dialogue between CT and NE to realize the functions as

configuration, alarm management, etc.¸ The software product used for updating the NE must be installed on the PC and then downloaded into the NE.

Ë The PC configuration to be used as a CT consists of :¸ Hardware configuration:

Č CPU: Pentium II 200MhzČ RAM: 128Mb (256Mb suggested)Č HARD DISK: 4GbČ MONITOR: 12’’ (14’’ suggested)Č RESOLUTION: 1024 x 768 pixelČ CD-ROM drive For CT software installation and handbook looking

¸ Software configuration:Č WINDOWS NT 4.0 Services Package 3 or WINDOWS 2000Č Sun Microsystems Java JRE 1.2 or 1.3Č Netscape Communicator 4.x or Internet Explorer 4.x or higher versions

Ë To install the software products, use the procedure described in the « 1320CT Basic Operator’s Handbook »




1.2 1320CT start-up


1.6

1.2 1320CT start-upNES window opening

1) Connect the RS232 cable2) Click on the 1320CT icon3) Wait until the NES (Network Element Synthesis) window appears

Ë When 1320CT is started, the map Unnamed is opened in NES window that: ¸ is empty, if F interface isn’t connected¸ contains the connected NE whose address is automatically retrieved, if F interface is connected

If a map containing the connected NE already exists, this map is opened instead of map Unnamed.If two or more maps containing the connected NE already exists, 1320CT let the operator decide which map has to be opened.Remote NEs have to be declared by the operator.

Ë To stop the application:¸ select the NES window¸ Maps Č Exit

Ë Led symbols on the left border¸ Nes IM: indicates if the application is properly started.¸ Retix LL (OSI): indicates if the connection to the OSI layer of the CT is active.¸ Local NE address: indicates if the OSI address of the local NE is known.¸ CT address: indicates if the OSI address of the Craft Terminal is known.

Ë Warning symbolsOn the NES view are present warning symbols:¸ On the « Maps » tabbed pane¸ On the title bar

The colour of the warning symbols are:¸ Grey: warning not present¸ Blue: normal warning¸ Red: important warning

Ë Connectivity state in the NES window:Local NE pluggedLocal NE unpluggedRemote NE


1.7

1.2 1320CT start-upLower Layers Manager (LLM)

Ë At the bottom right of the screen (in the task bar), there is a red triangle

Ë When you double click on this triangle, the window Alcatel Lower Layers Manager is displayed indicating the status of the connection with the local NE

Ë Link:¸ Port: COM port for F interface set in “Start-->Settings-->Control Panel-->Alcatel Lower Layers settings”¸ Physical:

Č OFF: indicates that the serial connection is physically broken because serial cable is absent, serial cable is not connected on the configured port of the PC or serial cable is broken.

Č ON: physical link is OK¸ OSI:

Č OFF: indicates that the serial connection is logically broken because physical link is OFF (in this case logical link is always OFF), NE software is restarting (temporary state) or NE software is not able to start (if it lasts for some minutes)

Č ON: logical link is OK; thus OSI addresses can be retrieved.¸ IP:

Č OFF: indicates that there is no IP dialogue between CT and NE because Adapter Interface of the PC or Point To Point Interface of the NE haven’t been configured, or Lower Layer IP Manager has not been set during software installation.

Č ON: CT and NE can exchange IP messages because IP addresses are valid¸ Nectas: OFF or ON (mixed network with QB3* and Q3 protocols)

Ë IP network addresses:¸ Local: IP address of the Adapter Interface of the PC¸ Mask: subnet mask of the Adapter Interface of the PC¸ Adjacent: IP address of the Point To Point Interface of the NE¸ SubNet: is the subnetwork of the Point To Point interface of the NE and is automatically evaluated and assigned

(SubNet = Adjacent AND Mask) ¸ Waiting: IP addresses are unknown

Ë OSI network addresses:¸ Local: CT OSI address. If the System Identifier = 000000000000 in the LLM settings window, the NE inserts the CT

address with a random algorithm (refer to the installation procedure described in the « 1320CT Basic Operator’s Handbook »)

¸ Adjacent: NE OSI address¸ Waiting: 1320CT and NE OSI addresses are unknown

Ë Clients (Applications and connections)¸ Internal numbers indicating the number of active applications (usually not important for the operator)

Č Warning: these numbers can change with the releases




1.3 NE supervision start-up


1.9

1.3 NE supervision start-up

1) Select the NE in the « Map »2) Supervision Č Start3) Wait for the icon indicating the

supervision is started

Alarms

Highest alarm severity

Ë NE symbols:

OSI network layer is down

Discovering NSAP

Unknown type / release

Discovering NE type and release

NE type and release discovered

Starting supervision

Supervision successfully started

Supervised, but unreachable

Stopping supervision

Ë To stop the supervion:¸ Select the NE in the Map¸ Supervision Č Stop¸ Wait for the icon indicating the supervision is stopped




1.4 NE Login


1.11

1.4 NE Login

1) Select the supervised NE in the « Map »

2) Supervision Č NE Login4) Insert Login & Password3) Wait for the « Equipment View »

window

Management state

Severity alarm

synthesis

Domain alarm

synthesis

Ë Indications can change according to NE. Default Login: ADMIN; default Password: ADMIN.

Ë Severity alarm synthesis¸ CRI = CRITICAL: Alarm that needs immediate trouble-shouting¸ MAJ = MAJOR: Urgent alarm that needs trouble-shouting¸ MIN = MINOR: Not-Urgent alarm that needs delayed trouble-shouting¸ WNG = WARNING¸ IND = INDETERMINATE

Ë Domain alarm synthesis¸ SYNC = SYNCHRONIZATION: Alarm in the timing domain¸ EXTP = EXTERNAL POINT: Alarm associated with housekeeping inputs¸ EQP = EQUIPMENT: Alarm due to equipment failure¸ TRNS = TRANSMISSION: Alarm due to failure in the transmission network domain

Ë Management state¸ SUP = Supervision: indicates that NE is supervised (green) or not supervised (brown)¸ ALI = Alignment: indicates that the configuration is aligned (green) or not aligned (orange)¸ “Key” = Local Access State: indicates that 1320CT has the OS permission to modify the NE configuration (green) or

hasn’t the permission (blue)¸ Q3 or COM : indicates the NE/1320CT connection state; disabled (red) or enabled (green)¸ OS: indicates that NE is supervised by 1353SH (blue) or not supervised (green)¸ MGR: indicates that NE is managed by 1354RM (blue) or not managed (green) ¸ NTP = Network Time Protocol: disabled (brown), enabled and NTP servers not reachable (green), enabled and at list

one NTP server reachable (blue)¸ AC = Abnormal Condition: e.g. Active loopback, ALS disabled, card missing, etc...

Ë To close the « Equipment View »:¸ Views Č Exit




1.5 NE restart


1.13

1.5 NE restart

Ë The restart operation is a software reset and can be executed in normal traffic conditions.




1.6 Navigation in NE view


1.15

1.6 Navigation in NE viewDomain views

Ë To open a particular NE domain view:Views Č Equipment

Č TransmissionČ…

Ë Initially, Transmission view is empty; the operator have to select a starting point using Transmission--> Add TP.


1.16

1.6 Navigation in NE viewNavigation principles in « Equipment View » (1)

Ë To zoom in an object:¸ Double click on the selected object

or¸ Select the object and:

ViewsČ Open Object or Open in Windowor¸ In the « Board View », select the port and:

BoardČ Port Access


1.17

1.6 Navigation in NE viewNavigation principles in « Equipment View » (2)

Ë To return to the previous view:¸ Views Č Backward

Ë To display the equipment supporting an object:¸ In the « Equipment / Board View », select the object and:

Equipment / Board Č Show Supporting Equipmentor¸ In the « Port View », select the port and:

Port Č Show Supporting Board




1.7 ISA boards supervision


1.19

1.7 ISA boards supervision

Ë In order to manage ISA boards:1) Supervision -->Start on NE hosting ISA boards2) Select the supervised NE --> NE Directory --> Realign ISA board population

Composite NE is made of the NE and the hosted ISA boards3) select an ISA board and Supervision -->Start4) select the supervised ISA board and Supervision -->NE Login to start the ISA-USM application


1.20

1 Equipment view openingExercise

VStart-up the 1320CTVCheck the LLM windowVDisconnect the RS232 cableVCheck the LLM windowVStart-up the supervisionVCheck the NE iconVOpen the NE viewVCheck alarm synthesis and

management statesVOpen the «Transmission View»VOpen the «Equipment View»VSelect one board in the subrack and

display the «Port View»VReturn to the «Board View»

Time allowed: 35 minutes


1.21

1 Equipment view openingEvaluation

Ë Objective: to be able to start-up the 1320CT and to open the equipment view

Thank you for answeringthe self-assessment

of the objectives sheet


1.22

1 Equipment view openingNotes



2 Subrack and board declaration


2.2

2 Subrack and board declarationSession presentation

Ë Objective: to be able to align and modify the MIB according to the hardware configuration

Ë Program: 2.1 Local access request2.2 Remote inventory display2.3 Object administrative state modification2.4 Object declaration2.5 MIB management




2.1 Local access request


2.4

2.1 Local access request

Ë To allow or to inhibit the craft access:Supervision Č Access StateČ OS

Č Requested

CT access granted

CT access denied

Ë NE can be managed by Operation System or by Craft Terminal. To control the competition between OS and CT, a Local Access Control (LAC) is available.¸ If LAC is « granted » that means CT is allowed to manage the NE. The icon with a key symbol has a green

rectangular shape.¸ If LAC is « denied » that means OS manages the NE and CT is not allowed to modify NE configuration (it can only

read). The icon with a key symbol has a blue circular shape.¸ If LAC is « requested » that means CT has requested permission to OS and is waiting for a reply. The icon with a key

symbol has a white circular shape.

Ë The access state of a NE can be modified from two types of view :¸ Switching from the OS to the CT access state.¸ Switching from the CT access state back to the OS access state.




2.2 Remote inventory display


2.6

2.2 Remote inventory displayBoard level

Ë To display the remote inventory data of the selected board:EquipmentČ Remote inventory ČČ Board Level


2.7

2.2 Remote inventory displayGlobal inventory storage (1st mode)

Ë To store the remote inventory data of the NE in the CT: Supervision Č Upload Remote Inventory

Ë The Supervision-->Upload Remote Inventory option stores in the Craft Terminal the remote inventory data (information on all the boards and components of the NE). The operator doesn’t know exactly where the remote inventory is stored.


2.8

2.2 Remote inventory displayGlobal inventory display

Ë To display the remote inventory data of the NE previously stored in the CT:

DiagnosisČ View ČČ Remote Inventory


2.9

2.2 Remote inventory displayGlobal inventory storage (2nd mode)

Ë To store the remote inventory data of the NE in the PC: EquipmentČ Remote inventoryČČ Subrack Level

Ë The operator decides where the remote inventory must be stored or printed.




2.3 Object administrative state modification


2.11

2.3 Object administrative state modificationAdministrative states

Out of Service

In Service

Ë Out of Service state doesn ’t impact the object activity.

Ë An in service slot is indicated by the presence of a padlock.An out of service slot is indicated by the presence of a “circle+point” icon.


2.12

2.3 Object administrative state modificationState modification

1) Select an in Service or out of Service object

2) EquipmentČ Set out of ServiceorČ Set in Service




2.4 Object declaration


2.14

2.4 Object declarationDeclaration procedure

1) Select an empty slot orsubrack

2) Equipment Č Set3) Choose the desired object

Ë When an item is selected on the screen, it is surrounded by an orange rectangle.

Ë An in service slot is indicated by the presence of a padlock. In this case, to perform the Set option the padlock must be removed by the Set out of Service command and the slot or the subrack must not be involved in any activity and configuration.

Ë If a slot is not used the operator has to set Empty slot.

Ë The window “Create/Modify Equipments” displays the list of objects allowed in the selected subrack or slot. Only the relevant options are available.


2.15

2.4 Object declarationDeletion procedure

1) Select an out of Serviceobject

2) Equipment Č Remove

Ë Before removing a subrack, all the boards in that subrack must be removed.

Ë Before removing a board, you have to make sure that the unit is not involved in:¸ Protection¸ LAPD¸ Connection¸ Synchonization¸ Performance monitoring point¸ OH TP


2.16

2.4 Object declarationModification procedure

1) Select an object (in Service or out of Service)

2) EquipmentČ Modify3) Choose the desired object

Ë This option is not always available. It depends on the board type.

Ë Modify is useful when a board must be replaced with a board of the same type but different version (i.e. STM-4: S-4.1 --> S-4.1N). In this case, the settings of the board can be maintained.


2.17

2.4 Object declarationExercise

VAllow the CT access if necessaryVDisplay a board remote inventoryVDisplay the global inventory of your NEVMake a hardware reset of the data base

in order to get the default configuration of the NE (see Operator Handbook)VAlign the MIB according to the hardware

configuration





2.5 MIB management


2.19

2.5 MIB managementMIB definition

Ë The MIB is stored in the NEË Any configuration modification will

immediately modify only the MIB in the NE

Modification

MIB

Ë MIB: Management Information Base


2.20

2.5 MIB managementOMSN MIB backup

Ë To save a copy of the MIB in the CT:1) Download Č MIB management2) Enter a name for the backup3) Click on Backup4) Wait for the message « Backup

successfully completed! »

Ë Backup is a copy of the MIB in a given moment and is not up-to-dated by further NE configurations.

Ë The NE backup is stored in a special subdirectory of the CT and is made up of three files:¸ Backup.dat¸ Backup.dsc¸ Userlbl.txt: contains the Backup name written by the operator

Ë An example of backup subdirectory path is:¸ C:\ALCATEL\Q3CT-Pv1.1.5.3\FTservices\data\1\B52_1


2.21

2.5 MIB managementOMSN MIB restore

Ë To restore a backup:1) DownloadČ MIB management2) Select the backup to restore3) Click on Restore4) Wait for the message « Restore

completed! »5) Click on Activate6) Wait for the message « MIB

activation completed! »7) Wait for the CPU restart


2.22

2.5 MIB managementISA cards MIB Backup / Restore

Ë This function is accessible by selecting, in the menu bar : MIB-Management Ą Backup/Restore DB

Ë This function permits to save (Backup) the AtmNE configuration and/or to Restore it.

Ë The Backup (save) can be done writing a name for the current configuration in the field “Backup name” and then clicking on the “Backup” button.

Ë The Restore can be done selecting a name in the field “Available Backup Files” and then clicking on the “Restore” button.

Ë Different options are presents:¸ “Delete”: to delete the selected backup file;¸ “Close”: to close the window without doing

any operation;¸ “Help”: to get helps about this function.

Ë The restoration function will take some time to finishand during this interval the ATM board not respond to the ATM Craft Terminal


2.23

2.5 MIB managementMIB export

Ë Starting from NES: 1) Supervision Č Files Administration

Č MIB Copies Č Save to disk2) select the .dsc file in folder 1 ČOpen3) select the target directoryČOpen4) Wait for the Message

Ë This operation is only allowed if:¸ the NE is supervised¸ the backup have already been done (see the previous slide)


2.24

2.5 MIB managementMIB import

Ë Starting from NES:1) Supervision Č Files Administration Č MIB Copies

Č Load from disk2) Select the directoryČ Search3) Select the backup (i.e. 68B 1660SM c:\...)Č OK4) Wait for the Message

Ë This operation is only allowed if the NE is supervised.

Ë The file is automatically saved in a dedicated path. The file denomination in NE view is the same than the one given by the operator to the backup file during the saving operation.


2.25

2.5 MIB managementExercise

VPerform your own backupVExport it to A:/VDelete it in the 1320CT from the « NE

MIB management » windowVRemove (software) one board in the

« Equipment view »VImport your backup from A:/VRestore itVCheck that the board previously

removed is presentTime allowed: 35 minutes


2.26

2 Subrack and board declarationEvaluation

Ë Objective: to be able to align and modify the MIB according to the hardware configuration





3 Communication parameter configuration


3.2

3 Communication parameter configurationSession presentation

Ë Objective: to be able to configure the communication and routingparameters in order to supervise the whole network from the OS

Ë Program: 3.1 Overview on comm & routing domain3.2 Local configuration3.3 LAPD configuration3.4 Ethernet configuration3.5 OS configuration3.6 RAP/MESA configuration3.7 IP configuration3.8 Tunneling configuration3.9 Network Time Protocol configuration




3.1 Overview on comm & routing domain


3.4

3.1 Overview on comm & routing domain

L1 L1

L1

L1

L1 L1

L1

L1

L2

AREA (subdomain) 1

AREA (subdomain) 2

L2 L1

L1

L1

L1

L1

= NE supporting IS-IS

= NE not supporting IS-IS

Ë Partitioning into Routing DomainsDuring the TMN design process, a network is partitioned into domains; each domain consists of a collection of two types of nodes:¸ Nodes supporting the IS-IS protocol; these nodes are called adaptive routers.

The IS-IS protocol allows automatic network (re)configuration by dynamically building routing tables.¸ Nodes not supporting this protocol; these nodes are called static routers.

Network partitions consisting of the former type of node are called adaptative routing domains; network partitions consisting of the later type of node are called static routing domains.Moreover, nodes which have to take routing decisions are called Intermediate Systems (ISs), all others are called End Systems (ESs).

Ë Partitioning into Routing SubdomainsIn order to reduce the overhead associated with distributed adaptative routing, it may be useful to divide an adaptative routingdomain into smaller routing subdomains, called areas or level 1 subdomain. In one area, we can find different type of nodes:¸ Level 1 Intermediate Systems (L1 ISs) for every node pertaining to an area.¸ Level 2 Intermediate Systems (L2 ISs) for every node which act as boundary ISs between areas. These ISs act as

L1 ISs with respect to their own area and as L2 ISs with respect to other areas.




3.2 Local configuration


3.6

3.2 Local configuration

ConfigurationČ Comm/RoutingČ Local Configuration

Ë In the « Local Configuration » window, the following fields are present:¸ Local Address

Č Presentation Selector (P Sel.) identifies a presentation entity at the location identified by the NSAP Address.Č Section Selector (S Selector) identifies a section entity at the location identified by the NSAP Address.Č Transport Selector (T Sel.) identifies a transport entity at the location identified by the NSAP Address.Č NSAP (Network Service Access Point) Address identifies a location in the network.

V AFI (Authority and Format Identifier) determines the NSAP format.– The value 49 identifies the local format of variable lenght (from 16 to 40 characters).– The value 39 identifies the ISO-DCC format of 40 characters long.– The value 47 identifies the GOSIP-V2 format of 40 characters long.

V System Id identifies a NE in an area and is 12 characters long.It might be the equipment MAC Ethernet address, level 2, inserted in the NE, or it might be selected by the operator.

V Network Selector (N Sel.) provides the distinction among users of the network service (value is 1D).¸ Synonymous Area Address – Optional

This section allows to have multiple synonymous area addresses within a level 1 subdomain. The compilation of the two network addresses is optional and if they are inserted, the last two fields, System Id and Network selector, of the mandatory address and of the synonymous addresses must be the same.

¸ System TypeThis section determines whether the local NE acts as a « Intermediate System Level 1 » or as a « Intermediate System Level 2 » or as a « End System ». Note that a level 2 intermediate system performs functions of a level 1 too.

Ë NB: After modifying the local configuration, the NE restarts automatically.




3.3 LAPD configuration


3.8

3.3 LAPD configurationLAPD role

MS

RS RS

MUX MUXREG

RS = NETWORK

MS = NETWORK

RS = USER

MS = USER

RS = USER RS = NETWORK

DCC

DCC

Ë The CT communicates with remote NEs through the DCC (Data Communication Channels) that support Qecc protocol.

Ë It is suggested (but not mandatory) to follow a predetermined order for the Network/User sequence in the complete network.

Ë Two groups of DCC can be configured:¸ D1-D3 RsTTP: DCC in RSOH¸ D4-D12 MsTTP: DCC in MSOH


3.9

3.3 LAPD configurationLAPD window

ConfigurationČ Comm/RoutingČ Interfaces ConfigurationČ LAPD Configuration


3.10

3.3 LAPD configurationOSC configuration for WDM NE

TERM A TERM BOLA 1 OLA 2

Port menu of an OFA

Ë The OSC (Optical Supervisory Channel) is an out-of-band channel dedicated to the transport of a 2Mbit/s supervision frame.




3.4 Ethernet configuration


3.12

3.4 Ethernet configurationL2 parameter

L2 L2

NENo

AREA 1

AREA 2

AREA 3

LAN

NENo

L2

NEYes

OS

L2 only


3.13

3.4 Ethernet configurationEthernet window

ConfigurationČ Comm/RoutingČ Interfaces ConfigurationČ Ethernet Configuration

Ë Ethernet InterfaceThis field allows to define or remove a Local Area Network (LAN) port for the access to the Data Communication Network (DCN). When you disable the Ethernet interface, the CPU restart.

Ë MAC AddressThis section displays the address of the NE in the Ethernet LAN only if Ethernet Interface is enabled. It is a read only field.

Ë OSI Section¸ L2 Only Parameter

This field indicates if the port can be used for level 2 traffic only, thus avoiding transmitting L1 packets. Note that the flag shall be set to No if some other nodes (NEs or OSs) of the same area are connected to the Ethernet LAN.

¸ L1 Default Metric is a not modifiable field, Priority field can be set (default value for ethernet is 64)¸ L2 Default Metric is a not modifiable field, Priority field can be set (default value for ethernet is 64)

Ë IP Section allows to define the IP Address, the IP Mask and the Routing Ip Protocol of the Ethernet Interface; if OSPF or Both options are selected, also the Associated OSPF Area must be set.




3.5 OS configuration


3.15

3.5 OS configuration

ConfigurationČ Comm/RoutingČ OS Configuration

Ë This window allows to configure the addresses of the Main and Spare OS that have to manage the NE.

Ë Main/Spare OS AddressThis section contains the same type of information than the one in the Local Configuration dialog-box




3.6 RAP/MESA configuration


3.17

3.6 RAP/MESA configurationRAP configuration

ConfigurationČ Comm/RoutingČ OSI Routing ConfigurationČ RAP Configuration

Ë Partitioning into separate Routing DomainsIn certain situations it may be better to partition a given network into separate routing domains, where no routing information is exchanged between these domains. The major benefits of this partitioning are reduction of memory, processing and traffic overhead. Communication between separate routing domains must be achieved through the use of Reachable Address Prefixes (RAP).A RAP represents static routing information. It can only be associated with a link of level 2 intermediate system, whereby this link crosses routing domain boundaries. A RAP is handled in the same way as information about a foreign level 1 subdomain within the own domain. The RAP indicates that any packet whose destination network address NSAP matches the prefix may be forwarded via the link with which the prefix is associated.For example, consider network which is split into two separate routing domains:¸ Routing domain A resides in a level 1 subdomain with area address « a »¸ Routing domain B resides in a level 1 subdomain with area address « b »

In order to enable the communication, the RAP in routing domain A must contain the area address « b » and the RAP in routing domain B must contain the area « a ».On the other hand, within a given level 1 subdomain, there can be some NEs not supporting IS-IS nor ES-IS protocol (static routing). In such condition, the communication can be achieved through the use of Manual End System Adjacencies (MESA).A prerequisite for the use of MESA is that the area addresses of the connected nodes must be the same; as a consequence the nodes must belong to the same level 1 subdomain.Within a pure Alcatel network there is no need to use any kind of static routing. Therefore normally RAP and MESA shall never be used

Ë RAP Table Configuration¸ Physical Interface

Č If the element is empty, the field displays the « none » value and allows to select a LAPD port or a LAN port which will be used to reach the addressed area.

Č If the element isn’t empty, the field displays the selected port and allows to change it.¸ Area Address Prefix

Č This section allows the user to address the separate domain. This Area Address Prefix represents a NSAP address without the fields System Id and Network Selector.

¸ MAC AddressČ This section allows to address the element of a domain to be reached the Ethernet LAN; the field is managed

as a simple string of 12 digits.


3.18

3.6 RAP/MESA configurationMESA configuration

ConfigurationČ Comm/RoutingČ OSI Routing ConfigurationČ MESA Configuration

Ë MESA Table Configuration¸ Physical Interface

Č If the element is empty, the field displays the « none » value and allows to select a LAPD port or a LAN port which will be used to reach the End System element.

Č If the element isn’t empty, the field displays the selected port and allows to change it.¸ System Id

Č This section represents the System Id of the ES element.¸ MAC Address

Č This section allows to address the element in the Ethernet LAN; the field is managed as a simple string of 12 digits.




3.7 IP configuration


3.20

3.7 IP configurationPresentation

Ë ISA Board has been implemented as an SNMP Agent, SNMP being based on UDP/IP protocol. This requires to declare IP addresses for each element. IP configuration and Tunneling configuration are relevant to theconfiguration of management communications messages for of ISA cards in the equipment and in the network.

Ë IP configuration menu allows to declare :¸ IP address of the ISA board¸ IP address of the Point-To-Point board, ¸ Definition of the routing configuration

Ë Tunneling is needed because the ISA boards are managed via SNMP, and they shall be reachable through a pure OSI network.

Ë ISA boards are managed by means of SNMP (Simple Network Management Protocol). Therefore, the encapsulation of SNMPmessages inside the OSI layers ("IP over OSI tunneling") is required. In this way the ATM and MPLS management information is transported over the existing SDH networks.


3.21

3.7 IP configurationPresentation

QB3*

X.216

X.215

ISO 8073

ISO 8473

LLC MAC

Not specified

ACSE 7.27.1

Info ModelCMISE, ROSE, ACSE

X.216

X.215

ISO 8073

ISO 8473

LLC MAC

Not specified

Q3

Application

Presentation

Session

Transport

Network

Data link

Physical

OSI model

7

6

5

4

3

2

1

TelnetFTP, NFS

SMTPHTTPSNMP

TCP / UDP

IP

LLC MAC

Not specified

TCP/IP

Ë The “Physical layer” of Ethernet can be : 10 Base 2, 10 Base T ... Ë LLC MAC: Logical Link Control Media Access Control (Ethernet address management)

Ë ISO 8473: The NSAP (Network Service Access Point) address is managed by this layer

Ë IP: Internet Protocol . The IP adddress is managed by this layer Ë TCP: Transport Control ProtocolË UDP: User Datagram Protocol

Ë CMISE: Common Management Information Service ElementË ROSE: Remote Operation Service ElementË ACSE: Association Control Service Element

Ë FTP: File Transfer ProtocolË NFS: Network File SystemË SMTP: Simple Mail Transfer ProtocolË HTTP: Hyper Text Transfer ProtocolË SNMP: Simple Network Management Protocol


3.22

3.7 IP configurationHow to declare ISA card

Ë In each equipment hosting ISA card :¸ Declare ISA card in a slot (Equipment view)¸ Declare the ISA card IP address

Configuration Ā Comm/Routing Ā IP configuration Ā ISA board IP address

Ë This window allows to delare the ISA board IP address


3.23

3.7 IP configurationHow to declare the Point-To-Point card

Ë Point-To-Point IP address Declaration :The Point-to-Point card represents the Equipment Controller function of the OMSN equipment.

Configuration Comm/Routing Ā IP configuration Ā IP Address Configuration of Point-

To-Point Interface

Ë This dialog-box allows to set the Equipment Controller IP Address


3.24

3.7 IP configurationDefinition of the routing configuration (OSPF area configuration)

Ë OSPF is a routing protocol in the IP protocol and is used by the NEs to exchange routing and network topology information.It provides the creation of routing tables for each NEs and their alignment to respect to the actual DCN topology.OSPF, like IS-IS in OSI network, follows a hierarchical architecture of the network. Network is split into Areas

Ë OSPF is to be defined before creating tunneling

Ë OSPF : Open short Path FirstË The OSPF is a filter :

In this example, the OSPF Area Address means that all addresses beginning with 155.11.xx.xx are taken in count in the Area. The filter is defined with the second line :255.255.0.0 means that the first and the second address parts are kept.

You can defined several sub-networks through the OSPF


3.25

3.7 IP configurationIP static routing configuration

This table is used when the element to reach is not in the same area or hasn't routing tableConfiguration

Comm/RoutingIP Configuration

IP Static Routing Configuration

Ë Destination Host IP AddressThis section allows to define the IP address necessary to reach a specific Host.

Ë Destination NetworkThis field is alternative to Destination Host IP Address. It allows to define the IP Address and IP Mask to reach a network.

Ë Default Gateway IP AddressThis section allows to define the address of the next hop gateway.

Ë CLNP (Connection Less Network Protocol) TunnelThis field allows to use a pre-define IP over OSI tunnel towards a gateway.

Ë IP Point-to-Point Interface IdThis section allows to use point to point interfaces made available by EC.


3.26

3.7 IP configuration Check the "PC" IP address

Ë "PC" IP address Checking :At the bottom right of the screen (in the task bar), double click on the red Triangle to open the Low Layer Manager window.

¸ The local address is the "PC" IP address.

¸ The Adjacent address is the Point to point address of the NE where the PC is connected.

Ë This configuration has to be made by the PC administrator.




3.8 Tunneling configuration


3.28

3.8 Tunneling configurationIP over OSI Presentation

Ë It’s necessary to build a set of tunnels in order to provide the IP connectivity between GNE (NE where the CT is connected) and each NEs hosting ISA Board.

Ë Between two NEs hosting one or more ISA Boards, only one tunnel is required to guarantee the IP connectivity.

Ë The ‘IP over OSI tunnel’ End Points are identified by NEs NSAP Address.

Ë An OSPF area must be associated to each IP over OSI tunnel.

Area n

EC ISA

IP over OSItunnels

CT


3.29

3.8 Tunneling configurationIP over OSI configuration

ConfigurationČ Comm/RoutingČ Tunneling ConfigurationČ IP Over OSI

Ë This feature is applicable to NEs.It consists of using QB3/QECC channels to carry SNMP messages. The extraction/insertion of IP packets from/into QB3/QECC channels is performed by EC.

Ë IP Routing section allows to choose the type of IP routing supported as follows:¸ OSPF (Open Shortest Path First)¸ RIP (Routing Information Protocol)¸ Both¸ None

If OSPF or Both options are selected, also the Associated OSPF Area must be set.


3.30

3.8 Tunneling configurationRoute declaration

Ë A route allows to prepare the communication between ISA cards and the Craft Terminal (to supervise the ISA cards). A route is defined between Point-To-Point IP address (start) and the ISA card IP address (destination).

One route has to be created for each ISA card present in the network includingISA card(s) belonging to the NE where the CT is connected.

Area n

ISA

@ IP Point-To-Point card (EC) @ IP ISA card

CT

Routes

EC


3.31

3.8 Tunneling configurationRoute declaration : adding a route

Ë Open the DOS command window :in the task bar > start > execute type CMD > OK

Ë The route is defined as following(type this command) :

route add <destination IP address (ISA card)> <start IP address (Point to point address where the CT is connected)>


3.32

3.8 Tunneling configurationRoute declaration : delete a route

Ë To delete a route, type this command (DOS window) :

route delete <destination IP address (ISA card)> <start IP address (Point to point address where the CT is connected)>


3.33

3.8 Tunneling configurationRoute declaration : check the the list of declared routes

Ë To display the declared routes, type this command (DOS window):Č route print

Destination Address Network Mask Gateway Address Interface address Metric

Destination Address Gateway Address Interface address(ISA cards) (Point to Point card) (PC)

CT


3.34

3.8 Tunneling configurationISA card supervision

Ë As soon as a route is declared, the supervision of the ISA cards is possible :¸ Open the 1320CT¸ Select the OMSN equipment¸ In the menu bar : select NE directory menu > realign ISA board

population

ISA card

OMSN Equipment


3.35

3.8 Tunneling configurationISA card supervision

Ë ISA card supervision¸ Select the ISA card¸ Launch the supervision :

Č Supervision Č start supervision (menu bar)

Č Supervision menu Č show equipment

Ë The ISA card is an independent element : the supervision is performed selecting the ISA card and starting the supervision. It's not necessary to supervise the OMSN to supervise the ISA card.


3.36

3.8 Tunneling configurationISA card view

Ë The ISA card is an independent element : the supervision is performed selecting the ISA card and starting the supervision. It's not necessary to supervise the OMSN to supervise the ISA card.


3.37

3.8 Tunneling configurationOSI over IP

ConfigurationČ Comm/RoutingČ Tunneling ConfigurationČ OSI Over IP

Ë This feature is applicable to NEs.It consists of using IP network to carry OSI messages. The extraction/insertion of OSI messages from/into IP packets is performed by EC.

Ë It allows to configure the Remote Destination IP Address of the Equipment Controller.




3.9 Network Time Protocol configuration


3.39

3.9 Network Time Protocol configurationNTP server configuration

ConfigurationČ Comm/RoutingČ NTP Server Configuration

Ë This dialog-box allows to configure the addresses of the Main and Spare NTP (Network Time Protocol) Servers reachable by the NE, used for time distribution in the network. The following fields are present :¸ Enabling NTP protocol section allows to enable (Yes) or disable (No) the NTP protocol.¸ Main NTP Server Address section contains the same type of information than the one into the Local Address section

in the Local Configuration dialog-box.¸ Spare NTP Server Address section contains the same type of information than the one into the Local Address

section in the Local Configuration dialog-box.

Ë If the NTP server is coincident with the OS (same hardware), the OS NSAP address must be assigned.


3.40

3.9 Network Time Protocol configuration NE time

ConfigurationČ NE Time

Look also: NTP icon, colour and

shape

Ë NTP Status¸ NTP Protocol = Disabled or Enabled; it depends on Enabling NTP Protocol setting (No or Yes) in NTP Server

Configuration window.¸ NTP Main/Spare = Unreachable or Reachable; it depends on the connection with the NTP Servers whose addresses

are written in NTP Server Configuration window.Ë Time

¸ NE Time refers to the NE¸ OS Time refers to the PC¸ Set NE Time With OS Time put the NE Time equal to the OS Time; it is a manual command and is available only if

NTP Protocol is disabled.


3.41

3 Communication parameter configuration Exercise

VConfigure:– the NE address– the LAPD ports– the Ethernet interface– the OS address– the IP addresses (if ISA board)

according to the instructions given by the trainer



3.42

3 Communication parameter configurationEvaluation

Ë Objective: to be able to configure the communication and routing parameters in order to supervise the whole network from the OS




© Alcatel University -8AS 90001 1860 VT ZZA Ed.054.1

4 Network topology creation


4.2

4 Network topology creationSession presentation

Ë Objective: to be able to create and manage a network topology from the CT

Ë Program: 4.1 Map/Submap/NE creation4.2 Map/Submap/NE management




4.1 Map/Submap/NE creation


4.4

4.1 Map/Submap/NE creationMap/Submap creation

Ë To create a new map in NES:1) MapsČ New Č Map2) Select the « Map Unnamed »3) Maps Č Save as Č Private/Public4) Enter a new name5) Maps Č Description (optional)

Ë To create a new submap inside the map, follow again the instructions previouslygiven:

MapsČ New Č Submap

Ë With the Description menu it is possible to insert more details to comment the map. Desciption is stored in the CT.

Ë When you save your map for the first time, select the Save as menu in order to define the status of your map:¸ Private: only the WINDOWS user who performs the saving can manage the map¸ Public: all the WINDOWS users can manage the map


4.5

4.1 Map/Submap/NE creationNE creation

Ë To add a new NE in a map:1) Select the « Map »2) NE Directory Č Create NE3) Insert NE address

Ë NE physically connected to the CT:¸ The NE is recognized by the CT and automatically presented in the NES window.¸ If the same NE was already created in one only saved map, this map will be automatically opened.¸ If the same NE is already created in several saved maps, the operator must select one map.¸ If the Maps Č New option is selected, the plugged NE is presented in the view.

Ë NE physically not connected to the CT (Remote NE):¸ Follow the « NE creation » procedure

Ë For each NE the Description option can also be used.


4.6

4.1 Map/Submap/NE creationSNMP NE creation

Ë To add a new SNMP NE in a map:1) Select the « Map »2) NE Directory Č Create SNMP NE3) Insert Basic Settings


4.7

4.1 Map/Submap/NE creationSlave NE definition


4.8

4.1 Map/Submap/NE creationSlave NE creation

Ë The NEs which support remote management of slave devices or subrack, require this Slave NE creation procedure.

Ë The created slave NE is displayed only when the master NE is supervised. The indication in the label, in this example, reports the master NE which is connected to the rack (1), slot (09) and the line (01).




4.2 Map/Submap/NE management


4.10

4.2 Map/Submap/NE managementMap/Submap management

Ë To open a map:MapsČ Open

Ë To save the current map:MapsČ Save

Ë To rename the current map:MapsČ Rename

Ë To delete a map:MapsČ Delete


4.11

4.2 Map/Submap/NE managementNE management: NE not supervised

Ë To display or to change NE address only in the map:NE Directory Č NE Properties

Ë To remove NE from the map:NE Directory Č Remove NE

Ë NE Properties is available only if the NE is not supervised

Ë Remove NE is available only if the NE is not supervised and is not the local NE


4.12

4.2 Map/Submap/NE managementNE management: NE supervised

Ë To display or to change NE address in the map & in the NE:1) NE Addresses Č Settings2) Select the « OSI stack settings » option3) Click on Set NE Address

Ë To change the « User label » or the « Location name » in the map & in the NE:

1) NE AddressesČ Settings2) Select the « Other settings » option3) Click on Change

Ë NE Address Settings window can be opened only if the NE is supervised.

Ë Address modification gets the NE CPU restart

Ë User label and Location name are stored in the NE


4.13

4.2 Map/Submap/NE managementTabbed window

Ë In case of selection of several NEs, the right part of NES window provides a tab for each NE


4.14

4.2 Map/Submap/NE managementNE user password modification

Ë Default login: ADMINDefault password: ADMIN


4.15

4.2 Map/Submap/NE managementNE user creation

Ë Operator: five types of operators are defined with different NE access rights as follow:¸ admin: all functionality except cross-connection deletion if created by RM¸ Administrator: all functionality except cross-connection deletion if created by RM¸ Constructor: all functionality except selection of manager assignment (SY manager, RM, etc)¸ Operator: all functionality except selection of manager assignment (SY manager, RM, etc)¸ Viewer: no modification is allowed


4.16

4 Network topology creationExercise

VCreate a new public mapVAdd NE in your mapVChange the « User label » and the

« Location name » of the local NEVStart-up the supervision on a remote NEVCreate a new user profile for the local

NE



4.17

4 Network topology creationEvaluation

Ë Objective: to be able to create andmanage a network topology from the CT



Ë


4.18

4 Network topology creationNotes



5 Alarm management


5.2

5 Alarm managementSession presentation

Ë Objective: to be able to manage the alarmsË Program:

5.1 External point management5.2 Alarm notification5.3 Alarm identification in NE view5.4 ASAP management5.5 NE time check5.6 AS application handling



5 Alarm management

5.1 External point management


5.4

5.1 External point management« External Points » view

Ë An external input point is an environmental alarm (also called housekeeping alarm). It corresponds to an external event which is monitored by the NE. Number of relays on the NE are dedicated to check modification of the environment as for example a fire, a flood, ...

Ë An external output point is used to manage a NE contact (i.e relay) connected to detector. An external output point is independent from external input point.

Ë The following information is given for each external point:¸ The external point type: Input or Output.¸ The user label: a user-friendly label associated to the configurable external point.¸ The external state represents the alarm state. On when the alarm is raised, else Off. If the external point is active

(On), a little flag is represented near the status of the concerned point.

Ë Only for the output external points there is the following information:¸ output criteria: if configurated, displays the alarm event and the board affected associated to the output point.


5.5

5.1 External point managementExternal input/output point display


5.6

5.1 External point managementExternal point configuration

For Inputpoint

For Output point

Ë External input point configuration¸ User Label: this field can be filled by the user with a label that indicates the associated event that must be taken

under check (for example presence of water or fire in the room where the NE is placed)¸ External State: this field is set to Off and can’t be changed by the operator¸ Probable cause: this field is set to housekeeping and can’t be changed by the operator

Ë External output point configuration¸ User Label: this field can be filled by the user with a label that indicates the alarm detected or the action that must be

executed if a specific event occurs (for example a pump activation when water is present in the room where the NE is placed)

¸ External State : this field can be set to On (alarm) or Off (non alarm) only if Manual option has been selected in the Output Criteria field

¸ Output Criteria and Involved TP:Č When Output Criteria is set to Manual, the output contact is set to On or Off not depending on a particular

event but according to External State setting.For example the output contact could be used to manually activate a pump to drain water from the room where the equipment is placed.

Č When Output Criteria is set to LOS, RDI or LOF, the event that triggers the output contact is the detection of the selected alarm on the Termination Point chosen in Involved TP



5 Alarm management

5.2 Alarm notification


5.8

5.2 Alarm notificationAlarm notification/inhibition

Ë To inform the operator that alarms have been inhibited, the labels of the alarm panel are greyed out.

Ë Inhibiting the alarms notification means that they are not forwarded to the CT but alarms are still generated by the NE.


5.9

5.2 Alarm notificationAlarm notification permission


5.10

5.2 Alarm notificationAlarm resynchronisation

Ë The system provides the possibility to recover alarms present within the NE and to update the current problem list of the NE. After this operation CT and NE current alarms are consistent.



5 Alarm management

5.3 Alarm identification in NE view


5.12

5.3 Alarm identification in NE viewScreen hierarchy

Board alarms (Equipment)

Port alarmsynthesis box (Transmission)Alarm synthesis

boxes (Equipment)

RACK SUBRACK BOARDEQUIPMENT


5.13

5.3 Alarm identification in NE viewAlarm synthesis screens

Rack view Subrack view

Ala

rms

synt

hesi

s bo

x

Subrack alarms

Board alarms

synthesis boxes

Ë The Board alarms synthesis box refers to configuration alarms (type mismatch,...), hardware alarms (unit problem, board missing,...) and all the other Board alarms in the bottom of the Board View (see next slide)


5.14


Board alarms synthesis box

Board alarms

Subrack view Board view


5.15


Board view Port view

Board transmission alarm synthesis box Board

transmission alarms


5.16

5.3 Alarm identification in NE viewAbnormal conditions

Ë To display the abnormal conditions:DiagnosisČ Abnormal

Condition List

Navigation to the view of the selected object

Ë Abnormal Conditions are: loopbacks, force or lockout command on protection schemes, force command on laser, board missing,...


5.17

5.3 Alarm identification in NE viewExercise

VOpen the « External Points » viewVConfigure an external output pointVRemove (software) a board in the

« Equipment view »VCheck the alarmsVExtract (hardware) another board in the

subrackVCompare the alarmsVOpen the abnormal condition list




5 Alarm management

5.4 ASAP management


5.19

5.4 ASAP managementASAP list

Ë To display the list of ASAPs :

ConfigurationČ Alarms Severities

Ë ASAP: Alarm Severity Assignment Profile

Ë For each NE, 4 fixed ASAP are defined by default by the manufacturer and others can be created by the user. The fixed ASAP are mandatory and can not be modified or deleted but they can be cloned to create a new ASAP.

Ë The default profiles are:¸ No Alarms (Profile 1) : all alarms are disabled (non alarmed)¸ Primary Alarms (Profile 2)¸ Path Alarms or No Remote Alarms (Profile 3)¸ All alarms (Profile 4) : all alarms are enabled


5.20

5.4 ASAP managementASAP display

Ë The ASAP Edition window is used to manage the severity of each Probable Cause.

Ë The Probable Cause Families section allows to filter the probable causes that will appear in the Probable Causes Namelist. To find a particular probable cause, enter its name in the Search entry box at the bottom.


5.21

5.4 ASAP managementASAP creation

Ë The created ASAP is identified with following names: #10001, #10002, …The maximum number of new ASAP can change according to NE type (SDH, WDM).


5.22

5.4 ASAP managementASAP modification

Ë To modify the severity associated with a probable cause, select the option button:¸ Service Affecting: not protected probable cause¸ Non Service Affecting: protected probable cause¸ Service Independent (not used)


5.23

5.4 ASAP managementASAP assignment

Ë This option permits to send the ASAP to the selected object (equipment, board, port, TP).It permits also to check the current ASAP used by the object.

Ë To assign an ASAP to an object:1) Select an object2) Configuration Č Set Alarms Severities3) Select an ASAP4) Click on OK to send the selected ASAP to the selected object

Ë Selected object and subordinates (examples for OMSN):¸ subordinates of SPI are: RST, MST and AU4¸ subordinates of PPI are: E1, P12 and VC12¸ subordinates of AU4 are: HPOM, HTCM, HTCT

Ë Choose current ASAP:¸ the ASAP selected in List of ASAPs will be assigned only to the objects whose ASAP is equal to the one written in

Choose current ASAP box


5.24

5.4 ASAP managementASAP deletion

Ë It is possible to delete an ASAP only if it isn’t assigned to any object.


5.25

5.4 ASAP managementExercise

VDisplay the ASAP listVCreate your own ASAPVSelect a block and assign your ASAPVAssign to that block another ASAPVDelete your ASAP




5 Alarm management

5.5 NE time check


5.27

5.5 NE time check

Ë To make sure that NE time and CT time are the same:

ConfigurationČ NE Time

Ë The NE Time window displays the current date and time of the CT (OS Time) and the NE.The status of the NTP (Network Time Protocol) can be checked.To re-align the NE time on the OS time, click in the Set NE Time With OS Time section on the Set push button.



5 Alarm management

5.6 AS application handling


5.29

5.6 AS application handlingAS principles

Ë AS is dedicated to receive, store, display in real time alarms raised by different sources (CURRENT ALARMS)

CURRENT

ALARMS

Network ressources

Display alarms

Manage alarms

AS Operator

Raise & clear alarms

Ë Maximum number of current alarms: up to 10000


5.30

5.6 AS application handlingAS start up from NES

Supervision ČAlarm Surveillance

1) select a supervised NE2) Supervision �

Show NE Alarms

Ë In NES, AS can be started in two ways:¸ Show NE Alarms provides the alarms of the selected NE under supervision.¸ Alarm Surveillance provides the alarms of all the NEs under supervision in the map.


5.31

5.6 AS application handlingAS start up from USM

Diagnosis Č AlarmsČ NE Alarms or …

Ë USM: User Service ManagerË It is possible to select a subset of alarms:

¸ NE Alarms: all NE alarms are listed in the AS report¸ Object Alarms: only alarms of the selected object are listed in the AS report¸ Subtrees Alarms: only alarms of the selected object and of the relevant subtrees are listed in the AS

report¸ Equipment Alarms: only alarms of equipment are listed in the AS report¸ Transmission Alarms: only alarms of transmission are listed in the AS report


5.32

5.6 AS application handlingCounter Summary window

Flag to indicate new alarms in thesublist

Specific counter of cleared alarms

Overflow status of the current alarm list

Ë The « Counter Summary » window is the start-up window for current alarms management. It provides a first view on the set of available sublists and on the situation of the network.

Ë The default set of sublists managed by the AS application for current alarms is composed of:¸ The Main Alarm List contains all available alarms¸ The Critical, Major, Minor, Warning, Indeterminate sublists contain respectively critical major, minor, warning,

indeterminate alarms¸ The Cleared sublist contains alarms which have been cleared, that is the alarms that are no longer active.

Ë To set the display of the « Counter Summary » window, select the Display pull down menu:¸ Inactive Sublists: if this option is activated, the user can see the inactive sublists¸ Severity counters: if this option is activated, each line representing a sublist displays in addition:

Č The number of alarms for each severity level,Č The number of cleared alarms,Č The number of non-acknowledged alarms.

¸ Auto-raise: if this option is activated, the « Counter Summary window » will be reactivated by incoming alarms and the sublist will be automatically updated.

Ë By using the Sublist pull down menu, the user can:¸ Create a sublist¸ Modify a sublist¸ Delete a sublist¸ Activate or Deactivate a current alarm sublist (Inactive sublists have all their counters set to « x »)¸ Open a sublist¸ Close a sublist¸ Save a sublist¸ Exit from the current window


5.33

5.6 AS application handlingSublist management

Ë To create a new sublist:SublistČ Create

Ë To delete a selected sublist:SublistČ Delete

Ë To modify a selected sublist:SublistČ Modify

A « Sublist Properties » window is displayed containing four panels:

ČDISPLAY parameters to identify the sublistČ FILTER to store alarms with common propertiesČSORT to sort order of alarms in the sublistČ TRIGGER consequent actions in case of alarms

Ë Sublist creationTo duplicate the characteristics of an existing sublist:

1) Select the source sublist2) SublistČ Create

To use the characteristics of a special sublist, the Default Alarm Sublist, whose goal is to store a common initial definition corresponding to user preferences:

1) Do not select any sublist or select Default Alarm Sublist2) SublistČ Create

Then the « Counter Summary » window is updated and a new sublist is displayed.


5.34

5.6 AS application handlingSublist management: DISPLAY panel

Sublist name

Currently displayed attributes in thesublist (select and click on the arrow to remove from the list)

Other available attributes (to move to the displayed attributes list, select and click on the arrow)

Sublist colour (double click to modify)

Click here to validate modifications


5.35

5.6 AS application handlingSublist management: FILTER panel

To select a saved filter

To save your filter

Filter on correlation parameter

Filter on status

Filter on date and time

Filter on probable cause (click on “Select...” to make your choice)

Filter on severity

Filter on alarm type

Ë In Filter Name section, the matching status is notified. One of the following three statuses may appear:¸ Match None: no alarm could match the filter. In this case, there may be conflicting options specified in the filter.¸ Match Some: some alarms may match the filter.¸ Match All: all alarms will match the filter. This means in particular that a sublist characterized by this type of filter will

extract all alarms of the main list.

Ë The Source sub-panel contains two attributes:¸ Object instance type

Č If Friendly Name is selected, the user can also specify the nature of the test:V Equal: self-understandingV Substring: the actual Friendly Name must contain the specified stringV Begin with: the actual Friendly Name must begin by the specified stringV End with: the actual Friendly Name must end by the specified string

Č If MO Instance is selected, the user can specify the kind of test to be performed:V Base: to only consider the object specified by the instanceV Subtree: to also include in the search all the objects contained in the specified object

¸ Object class typeThe possibility is given to extract alarms with respect to multiple MO Class attribute values.

Ë To retrieve valid values for MO Class, MO Instance and Friendly Name, the user can use the « More Alarm Information »window (see after). This window can be called from any opened sublist window after selection of an alarm in the table. The three attributes are displayed in the identity panel.


5.36

5.6 AS application handlingSublist management: SORT panel

To select a saved sort

To save your sort choice

Parameters not used to sort the sublist(select and click on the arrow to use it)

Parameters used to sort the sublist

Click here to select the order (increment or decrement)

Ë Decr. : for boolean attributes such as Reservation Status, the set value (eg Reserved) is assimilated to 1, the unset value (eg Unreserved) to 0, which allows defining an ascending or descending order.


5.37

5.6 AS application handlingSublist management: TRIGGER panel

Activate this option to receive a beep for each incoming alarm in the sublist

To execute a script if the number of alarms in the sublist is greater than a certain value

To execute a script if the number of alarms in the sublist is smaller than a certain value


5.38

5.6 AS application handlingActions on current alarms

Ë By using the Action menu, the user can:¸ Select an alarm¸ Reserve or Unreserve an alarm¸ Create a Trouble Ticket¸ Acknowledge an alarm¸ Perform a Manual Purge of alarms¸ Outpout alarms (see next slide)

Ë By using the Display menu, the user can:

¸ Get More Info about an alarm¸ Display Hidden Coloumns¸ Auto-Select incoming alarms

Ë Reserving/Unreserving alarmsTo ensure to be the only responsible for an alarm, the user can perform the reservation action on alarm.The status of the selected alarm will change from NRSV to RSV.An alarm can only be reserved if it has not been reserved before by another user.Only the user who has reserved an alarm can unreserve it.

Ë Creating a Trouble TicketA Trouble Ticket is a collection of all kinds of information about a specific problem. Thus, it contains at least the information related to an alarm, but can also include information relative to the actions performed to solve this problem.AS can be customized to interface with the third-party Trouble Ticket managing product ARS (edited by Remedy Corporation). In this case, all menus concerning the management of Trouble Tickets are inaccessible (i.e. greyed).The flag corresponding to the selected alarm changes in the Trouble Ticket Creation Flag column, passing from NO to YES.

Ë Acknowledging alarmsBy acknowledging a single or a group of alarms in the sublist, the user notifies he is taking it or them into account.The status of the alarm(s) changes in the Ack. Status column, passing from NACK to ACK.Acknowledging a cleared alarm causes its disapperance from the list.

Ë Manually purging an alarmWhen the user purges alarms, they disappear from the sublist.

Ë Exporting (Output) alarmsThe user can select one or more alarms in the sublist and export them to a file or to a printer.

Ë Auto-selecting the incoming alarmsNew alarms are automatically selected when they appear in the sublist.


5.39

5.6 AS application handlingOutput alarms and Alarm Formatter

Ë Action --> Output command can be used to save the selected alarms of the sublist to a file. But the alarms are saved in a not-friendly format (see three-alarms.txt figure).

Ë Extras --> Alarm Formatter command in NES window can be used to present in a friendly format the alarms previously saved (see three-alarms.txt.OUT figure).


5.40

5.6 AS application handlingAS facilities from the « Counter Summary » window

Ë To resynchronize the AS application with network resources:Option Č Synchronization

Ë To get reports on performed actions:Option Č Report

Ë Resynchronizing ASThe CAL (Current Alarm List) displays alarms emitted within the system. It is real time refreshed. Except the case of purging, an alarm received by the AS is immediately displayed on the screen.Since the CAL may become inconsistent with network ressources (manual purge, …), the user can explicitely initiate the resynchronization of current alarms.

Ë Getting reports on performed actionsAfter an action has been launched on the user’s request, it may be useful to visualize a report offering detailed informations about the progress or achievement (successful or not) of his action.¸ Possible type of action

Č Get Alarm List AttributesČ Get All AlarmsČ Get More Alarm InfoČ Get Correlated Alarms Č Set Alarm List Attributes Č Set User NoteČ Reserve AlarmsČ Unreserve AlarmsČ Acknowledge AlarmsČ Create Trouble TicketČ Manually Purge AlarmsČ Synchronize Application

¸ Possible status of the operationČ In Progress (Indeterminate severity level colour) : request is ongoing.Č Aborted (Minor severity level colour) : request hasn't been sent.Č Failure (Critical severity level colour) : request failed.Č Success (Cleared severity level colour) : request succeeded.Č Half Success (Major severity level colour) : request partially succeeded. In this case, read the report details in

order to find out what failed in the request.


5.41

5.6 AS application handlingAS facilities from the sublist window

Ë To navigate from AS to an external application:

Navigation Č External Application Č EML-USM

Ë EML-USM: Element Manager Layer- User Service Manager


5.42

5.6 AS application handlingExercise

VCheck NE timeVSet NE time with OS time if necessaryVStart the AS applicationVDisplay the Major sublistVCreate your own sublist with following

parameters:Major alarmsCommunications alarmsCleared alarmsIn the last 24 hoursSort the sublist by « event date & time »Emit a tone for incoming alarms

VPerform actions on alarms (reserve,…)VNavigate from AS to EML-USM



5.43

5 Alarm managementEvaluation

Ë Objective: to be able to manage the alarms




5.44

5 Alarm managementNotes


6.19

6.3 Log files displayNE event log


6.20

6.3 Log files displayCT event log


6.21

6.3 Log files displayCT activity log

Ë To display the system activity log, select the Activity Logpanel in NES

Ë It gives information on:¸ Pending activities¸ Completed activities

Ë NES USM includes a log of all pending and completed activities. Activities include initialisation, alarm poll, start/stop, supervision, and more.

Ë For each activity, information about status, steps, start/stop time, etc..., are maintained in an internal repository.

Ë Listed activities are split in two categories: Pending Activities and Completed Activities. ¸ All Pending activities move to the Completed sub-tree once they are finished, regardless to whether they succeeded

or failed. ¸ Exit status information is stored by the Activity log.

Ë The Properties sub-node contains information about start time, last step time (which becomes "Finish Time" for a completed activity), and status of the activity. For Completed activities there is also a fourth sub-item, "Duration".

Ë Under the Steps tree we find one node per step. Each node carries the name of the activity step it represents. If we open one step node, say, the Step 2 node, we can access the step information. ¸ Start time, step Status, and duration (for pending steps) are listed here. Duration is only listed for completed steps --

the last step of a pending activity would not have the Duration sub-node, and its Status sub-node would contain "In Progress".


6.22

6 Administration for operators Exercise

VInstall the new software package into the CTVSimulate a software download (don ’t

click the last OK)VPerform a NES backupVConfigure ANTPVDisplay NE alarm logVDisplay CT event log



6.23

6 Administration for operatorsEvaluation

Ë Objective: to be able to administrate the NE and the CT



02 - alcatel 1320ct training manual

Documents

local configuration

ne log

os configuration

rapmesa configuration

lapd configuration

ip configuration

alcatel alcatel university

ne view1