02 Alcatel 1320CT Training Manual PDF

Alcatel 1320CT 1.7.
x Operation
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel
Training manual 8AS 90001 1860 VH ZZA Ed. 05 Edition 2004
Page intentionally left blank
Note : Please print this document with comments pages
Alcatel University - 8AS 90001 1860 VH ZZA Ed.05
Page 0.2
Contents
Alcatel 1320CT 1.7.x Operation 1 8AS 90001 1860 VH ZZA
Equipment view opening 1.1

1.1 Introduction..1.3 1.2 1320CT start-up..1.5 1.3 NE supervision start-up. 1.8 1.4 NE log in.. 1.10 1.5 NE restart.1.12 1.6 Navigation in NE view 1.14 1.7 ISA boards supervision..............................................................................................1.18
Subrack and board declaration 2.1

2.1 Local access request. 2.3 2.2 Remote inventory display..2.5 2.3 Object administrative state modification. 2.10 2.4 Object declaration.. 2.13 2.5 MIB management... 2.18
Communication parameter configuration..3.1

3.1 Overview on comm & routing domain. 3.3 3.2 Local configuration. 3.5 3.3 LAPD configuration 3.7 3.4 Ethernet configuration3.11 3.5 OS configuration. 3.14 3.6 RAP/MESA configuration.. 3.16 3.7 IP configuration........................................... 3.19 3.8 Tunneling configuration............................................. 3.27 3.9 Network Time Protocol configuration...... 3.38
Page 0.3
Contents
4 Network topology creation.4.1
4.1 Map/Submap/NE creation. 4.3 4.2 Map/Submap/NE management 4.9
Alarm management.. 5.1

5.1 External point management..5.3 5.2 Alarm notification 5.7 5.3 Alarm identification in NE view. 5.11 5.4 ASAP management5.18 5.5 NE time check. 5.26 5.6 AS application handling.5.28
Administration for operators. 6.1

6.1 NE software download...6.3 6.2 CT environment management..6.11 6.3 Log files display.. 6.17
Appendix 1 Glossary.A1.1
Page 0.4
1 Equipment view opening
Alcatel University - 8AS 90001 1860 VT ZZA Ed.05
1.1
Page 1.1
1 Equipment view opening Session presentation
Objective: to be able to start-up the 1320CT and to open the equipment view Program: 1.1 Introduction 1.2 1320CT start-up 1.3 NE supervision start-up 1.4 NE log in 1.5 NE restart 1.6 Navigation in NE view 1.7 ISA boards supervision
1.2
Page 1.2
1.1 Introduction
1.3
Page 1.3
1.1 Introduction
CD ROM
Software product for download to update the NE
Software product for management to install in the PC
F interface
RS232 cable
1.4
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: z The software products used for management permit the dialogue between CT and NE to realize the functions as configuration, alarm management, etc. z 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 : z 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 z 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 Operators Handbook
Page 1.4
1.2 1320CT start-up
1.5
Page 1.5
1.2 1320CT start-up NES window opening
1) Connect the RS232 cable 2) Click on the 1320CT icon 3) Wait until the NES (Network Element Synthesis) window appears
1.6
When 1320CT is started, the map Unnamed is opened in NES window that: z is empty, if F interface isnt connected z 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: z select the NES window z Maps Exit Led symbols on the left border z Nes IM: indicates if the application is properly started. z Retix LL (OSI): indicates if the connection to the OSI layer of the CT is active. z Local NE address: indicates if the OSI address of the local NE is known. z CT address: indicates if the OSI address of the Craft Terminal is known. Warning symbols On the NES view are present warning symbols: z On the Maps tabbed pane z On the title bar The colour of the warning symbols are: z Grey: warning not present z Blue: normal warning z Red: important warning Connectivity state in the NES window: Local NE plugged Local NE unplugged Remote NE Alcatel University - 8AS 90001 1860 VH ZZA Ed.05
Page 1.6
1.2 1320CT start-up Lower 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
1.7
Link: z Port: COM port for F interface set in Start-->Settings-->Control Panel-->Alcatel Lower Layers settings z 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 z 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. z 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 havent 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 z Nectas: OFF or ON (mixed network with QB3* and Q3 protocols) IP network addresses: z Local: IP address of the Adapter Interface of the PC z Mask: subnet mask of the Adapter Interface of the PC z Adjacent: IP address of the Point To Point Interface of the NE z SubNet: is the subnetwork of the Point To Point interface of the NE and is automatically evaluated and assigned (SubNet = Adjacent AND Mask) z Waiting: IP addresses are unknown OSI network addresses: z 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 Operators Handbook ) z Adjacent: NE OSI address z Waiting: 1320CT and NE OSI addresses are unknown Clients (Applications and connections) z Internal numbers indicating the number of active applications (usually not important for the operator) Warning: these numbers can change with the releases Alcatel University - 8AS 90001 1860 VH ZZA Ed.05
Page 1.7
1.3 NE supervision start-up
1.8
Page 1.8
1.3 NE supervision start-up
1) Select the NE in the Map 2) Supervision Start 3) Wait for the icon indicating the supervision is started
Alarms
Highest alarm severity
1.9
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: z Select the NE in the Map z Supervision Stop z Wait for the icon indicating the supervision is stopped
Page 1.9
1.4 NE Login
1.10
Page 1.10
1.4 NE Login
Severity alarm synthesis
Domain alarm synthesis
1) Select the supervised NE in the Map 2) Supervision NE Login 4) Insert Login & Password 3) Wait for the Equipment View window
1.11
Indications can change according to NE. Default Login: ADMIN; default Password: ADMIN. Severity alarm synthesis z CRI = CRITICAL: Alarm that needs immediate trouble-shouting z MAJ = MAJOR: Urgent alarm that needs trouble-shouting z MIN = MINOR: Not-Urgent alarm that needs delayed trouble-shouting z WNG = WARNING z IND = INDETERMINATE Domain alarm synthesis z SYNC = SYNCHRONIZATION: Alarm in the timing domain z EXTP = EXTERNAL POINT: Alarm associated with housekeeping inputs z EQP = EQUIPMENT: Alarm due to equipment failure z TRNS = TRANSMISSION: Alarm due to failure in the transmission network domain Management state z SUP = Supervision: indicates that NE is supervised (green) or not supervised (brown) z ALI = Alignment: indicates that the configuration is aligned (green) or not aligned (orange) z Key = Local Access State: indicates that 1320CT has the OS permission to modify the NE configuration (green) or hasnt the permission (blue) z Q3 or COM : indicates the NE/1320CT connection state; disabled (red) or enabled (green) z OS: indicates that NE is supervised by 1353SH (blue) or not supervised (green) z MGR: indicates that NE is managed by 1354RM (blue) or not managed (green) z NTP = Network Time Protocol: disabled (brown), enabled and NTP servers not reachable (green), enabled and at list one NTP server reachable (blue) z AC = Abnormal Condition: e.g. Active loopback, ALS disabled, card missing, etc... To close the Equipment View : z Views Exit
Management state
Page 1.11
1.5 NE restart
1.12
Page 1.12
1.5 NE restart
1.13
The restart operation is a software reset and can be executed in normal traffic conditions.
Page 1.13
1.6 Navigation in NE view
1.14
Page 1.14
1.6 Navigation in NE view Domain views
To open a particular NE domain view: Views Equipment
Transmission
1.15
Initially, Transmission view is empty; the operator have to select a starting point using Transmission--> Add TP.
Page 1.15
1.6 Navigation in NE view Navigation principles in Equipment View (1) To zoom in an object: z Double click on the selected object or z Select the object and: Views Open Object or Open in Window or z In the Board View , select the port and: Board Port Access
1.16
Page 1.16
1.6 Navigation in NE view Navigation principles in Equipment View (2)
To return to the previous view: z Views Backward
To display the equipment supporting an object: z In the Equipment / Board View , select the object and: Equipment / Board Show Supporting Equipment or z In the Port View , select the port and: Port Show Supporting Board
1.17
Page 1.17
1.7 ISA boards supervision
1.18
Page 1.18
1.7 ISA boards supervision
1.19
In order to manage ISA boards: 1) Supervision -->Start on NE hosting ISA boards 2) Select the supervised NE --> NE Directory --> Realign ISA board population Composite NE is made of the NE and the hosted ISA boards 3) select an ISA board and Supervision -->Start 4) select the supervised ISA board and Supervision -->NE Login to start the ISA-USM application
Page 1.19
1 Equipment view opening Exercise
9 Start-up the 1320CT 9 Check the LLM window 9 Disconnect the RS232 cable 9 Check the LLM window 9 Start-up the supervision 9 Check the NE icon 9 Open the NE view 9 Check alarm synthesis and
Time allowed: 35 minutes
management states 9 Open the Transmission View 9 Open the Equipment View 9 Select one board in the subrack and display the Port View 9 Return to the Board View
1.20
Page 1.20
1 Equipment view opening Evaluation
Objective: to be able to start-up the 1320CT and to open the equipment view
Thank you for answering the self-assessment of the objectives sheet
1.21
Page 1.21
1 Equipment view opening Notes
1.22
Page 1.22
2 Subrack and board declaration
2.1
Page 2.1
2 Subrack and board declaration Session presentation
Objective: to be able to align and modify the MIB according to the hardware configuration Program: 2.1 Local access request 2.2 Remote inventory display 2.3 Object administrative state modification 2.4 Object declaration 2.5 MIB management
2.2
Page 2.2
2.1 Local access request
2.3
Page 2.3
2.1 Local access request
CT access granted CT access denied
To allow or to inhibit the craft access: Supervision Access State OS
Requested
2.4
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. z If LAC is granted that means CT is allowed to manage the NE. The icon with a key symbol has a green rectangular shape. z 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. z 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 : z Switching from the OS to the CT access state. z Switching from the CT access state back to the OS access state.
Page 2.4
2.2 Remote inventory display
2.5
Page 2.5
2.2 Remote inventory display Board level
To display the remote inventory data of the selected board: Equipment Remote inventory
Board Level
2.6
Page 2.6
2.2 Remote inventory display Global inventory storage (1st mode)
To store the remote inventory data of the NE in the CT: Supervision Upload Remote Inventory
2.7
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 doesnt know exactly where the remote inventory is stored.
Page 2.7
2.2 Remote inventory display Global inventory display
To display the remote inventory data of the NE previously stored in the CT: Diagnosis View
Remote Inventory
2.8
Page 2.8
2.2 Remote inventory display Global inventory storage (2nd mode)
To store the remote inventory data of the NE in the PC: Equipment Remote inventory
Subrack Level
2.9
The operator decides where the remote inventory must be stored or printed.
Page 2.9
2.3 Object administrative state modification
2.10
Page 2.10
2.3 Object administrative state modification Administrative states
Out of Service
In Service
2.11
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.
Page 2.11
2.3 Object administrative state modification State modification
1) Select an in Service or out of Service object 2) Equipment
Set out of Service

or
Set in Service
2.12
Page 2.12
2.4 Object declaration
2.13
Page 2.13
2.4 Object declaration Declaration procedure
1) Select an empty slot or subrack 2) Equipment Set 3) Choose the desired object
2.14
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.
Page 2.14
2.4 Object declaration Deletion procedure
1) Select an out of Service object 2) Equipment Remove
2.15
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: z Protection z LAPD z Connection z Synchonization z Performance monitoring point z OH TP
Page 2.15
2.4 Object declaration Modification procedure
1) Select an object (in Service or out of Service) 2) Equipment Modify 3) Choose the desired object
2.16
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 --> S4.1N). In this case, the settings of the board can be maintained.
Page 2.16
2.4 Object declaration Exercise
9 Allow the CT access if necessary 9 Display a board remote inventory 9 Display the global inventory of your NE 9 Make a hardware reset of the data base
in order to get the default configuration of the NE (see Operator Handbook) 9 Align the MIB according to the hardware configuration
2.17
Page 2.17
2.5 MIB management
2.18
Page 2.18
2.5 MIB management MIB definition
The MIB is stored in the NE Any configuration modification will immediately modify only the MIB in the NE
MIB
Modification
2.19
MIB: Management Information Base
Page 2.19
2.5 MIB management OMSN MIB backup
To save a copy of the MIB in the CT: 1) Download MIB management 2) Enter a name for the backup 3) Click on Backup 4) Wait for the message Backup successfully completed!
2.20
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: z Backup.dat z Backup.dsc z Userlbl.txt: contains the Backup name written by the operator An example of backup subdirectory path is: z C:\ALCATEL\Q3CT-Pv1.1.5.3\FTservices\data\1\B52_1
Page 2.20
2.5 MIB management OMSN MIB restore
To restore a backup: 1) Download MIB management 2) Select the backup to restore 3) Click on Restore 4) Wait for the message Restore completed! 5) Click on Activate 6) Wait for the message MIB activation completed! 7) Wait for the CPU restart
2.21
Page 2.21
2.5 MIB management ISA cards MIB Backup / Restore This function is accessible by selecting, in the menu bar : MIB-Management Backup/Restore DB
2.22
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: z Delete: to delete the selected backup file; z Close: to close the window without doing any operation; z Help: to get helps about this function. The restoration function will take some time to finish and during this interval the ATM board not respond to the ATM Craft Terminal
Page 2.22
2.5 MIB management MIB export
Starting from NES: 1) Supervision Files Administration
MIB Copies Save to disk 2) select the .dsc file in folder 1 Open 3) select the target directory Open
4) Wait for the Message
2.23
This operation is only allowed if: z the NE is supervised z the backup have already been done (see the previous slide)
Page 2.23
2.5 MIB management MIB import
Starting from NES: 1) Supervision Files Administration MIB Copies
Load from disk 2) Select the directory Search

3) Select the backup (i.e. 68B 1660SM c:\...) OK 4) 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.24
Page 2.24
2.5 MIB management Exercise
9 Perform your own backup 9 Export it to A:/ 9 Delete it in the 1320CT from the NE
MIB management window 9 Remove (software) one board in the Equipment view 9 Import your backup from A:/ 9 Restore it 9 Check that the board previously removed is present
2.25
Page 2.25
2 Subrack and board declaration Evaluation
Objective: to be able to align and modify the MIB according to the hardware configuration
2.26
Page 2.26
3 Communication parameter configuration
3.1
Page 3.1
3 Communication parameter configuration Session presentation Objective: to be able to configure the communication and routing parameters in order to supervise the whole network from the OS Program: 3.1 Overview on comm & routing domain 3.2 Local configuration 3.3 LAPD configuration 3.4 Ethernet configuration 3.5 OS configuration 3.6 RAP/MESA configuration 3.7 IP configuration 3.8 Tunneling configuration 3.9 Network Time Protocol configuration
3.2
Page 3.2
3.1 Overview on comm & routing domain
3.3
Page 3.3
3.1 Overview on comm & routing domain
L1
L1 L1
L1
L1
L1
L1 L1
L1
L1
L2 L2
L1
L1
AREA (subdomain) 1
L1
= NE supporting IS-IS = NE not supporting IS-IS
AREA (subdomain) 2
3.4
Partitioning into Routing Domains During the TMN design process, a network is partitioned into domains; each domain consists of a collection of two types of nodes: z 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. z 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 Subdomains In order to reduce the overhead associated with distributed adaptative routing, it may be useful to divide an adaptative routing domain into smaller routing subdomains, called areas or level 1 subdomain. In one area, we can find different type of nodes: z Level 1 Intermediate Systems (L1 ISs) for every node pertaining to an area. z 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.
Page 3.4
3.2 Local configuration
3.5
Page 3.5
3.2 Local configuration
Configuration
Comm/Routing Local Configuration

3.6
In the Local Configuration window, the following fields are present: z 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. 9 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. 9 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. 9 Network Selector (N Sel.) provides the distinction among users of the network service (value is 1D). z 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. z System Type This 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.
Page 3.6
3.3 LAPD configuration
3.7
Page 3.7
3.3 LAPD configuration LAPD role MS RS RS
DCC
MUX
REG
DCC RS = USER RS = NETWORK
MUX
RS = NETWORK MS = NETWORK
RS = USER MS = USER
3.8
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: z D1-D3 RsTTP: DCC in RSOH z D4-D12 MsTTP: DCC in MSOH
Page 3.8
3.3 LAPD configuration LAPD window
Configuration
Comm/Routing Interfaces Configuration LAPD Configuration

3.9
Page 3.9
3.3 LAPD configuration OSC configuration for WDM NE Port menu of an OFA
TERM A
OLA 1
OLA 2
TERM B
3.10
The OSC (Optical Supervisory Channel) is an out-of-band channel dedicated to the transport of a 2Mbit/s supervision frame.
Page 3.10
3.4 Ethernet configuration
3.11
Page 3.11
3.4 Ethernet configuration L2 parameter

AREA 1
AREA 2 OS
LAN L2 NE No NE No L2 NE Yes L2
L2 only
AREA 3
3.12
Page 3.12
3.4 Ethernet configuration Ethernet window
Configuration
Comm/Routing Interfaces Configuration Ethernet Configuration

3.13
Ethernet Interface This 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 Address This 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 z 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. z L1 Default Metric is a not modifiable field, Priority field can be set (default value for ethernet is 64) z 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.
Page 3.13
3.5 OS configuration
3.14
Page 3.14
3.5 OS configuration
Configuration
Comm/Routing OS Configuration
3.15
This window allows to configure the addresses of the Main and Spare OS that have to manage the NE. Main/Spare OS Address This section contains the same type of information than the one in the Local Configuration dialog-box
Page 3.15
3.6 RAP/MESA configuration
3.16
Page 3.16
3.6 RAP/MESA configuration RAP configuration
Configuration
Comm/Routing OSI Routing Configuration RAP Configuration

3.17
Partitioning into separate Routing Domains In 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: z Routing domain A resides in a level 1 subdomain with area address a z 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 z 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 isnt empty, the field displays the selected port and allows to change it. z 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. z 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.
Page 3.17
3.6 RAP/MESA configuration MESA configuration
Configuration
Comm/Routing OSI Routing Configuration MESA Configuration

3.18
MESA Table Configuration z 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 isnt empty, the field displays the selected port and allows to change it. z System Id This section represents the System Id of the ES element. z MAC Address This section allows to address the element in the Ethernet LAN; the field is managed as a simple string of 12 digits.
Page 3.18
3.7 IP configuration
3.19
Page 3.19
3.7 IP configuration Presentation 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 the configuration of management communications messages for of ISA cards in the equipment and in the network. IP configuration menu allows to declare : z IP address of the ISA board z IP address of the Point-To-Point board, z 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.
3.20
ISA boards are managed by means of SNMP (Simple Network Management Protocol). Therefore, the encapsulation of SNMP messages 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.
Page 3.20
3.7 IP configuration Presentation
7 Application 6 Presentation 5
Session
ACSE 7.2 7.1 X.216 X.215 ISO 8073 ISO 8473 LLC MAC Not specified
Info Model
CMISE, ROSE, ACSE
X.216 X.215 ISO 8073 ISO 8473 LLC MAC Not specified
Telnet FTP, NFS SMTP HTTP SNMP TCP / UDP IP LLC MAC Not specified
4 Transport 3 2 1
Network Data link
Physical
OSI model
QB3*
Q3
TCP/IP
3.21
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
Page 3.21
3.7 IP configuration How to declare ISA card In each equipment hosting ISA card : z Declare ISA card in a slot (Equipment view) z Declare the ISA card IP address Configuration Comm/Routing IP configuration ISA board IP address
3.22
This window allows to delare the ISA board IP address
Page 3.22
3.7 IP configuration How 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 PointTo-Point Interface
3.23
This dialog-box allows to set the Equipment Controller IP Address
Page 3.23
3.7 IP configuration Definition 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
3.24
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
Page 3.24
3.7 IP configuration IP static routing configuration This table is used when the element to reach is not in the same area or hasn't routing table Configuration Comm/Routing IP Configuration IP Static Routing Configuration
3.25
Destination Host IP Address This section allows to define the IP address necessary to reach a specific Host. Destination Network This 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 Address This section allows to define the address of the next hop gateway. CLNP (Connection Less Network Protocol) Tunnel This field allows to use a pre-define IP over OSI tunnel towards a gateway. IP Point-to-Point Interface Id This section allows to use point to point interfaces made available by EC.
Page 3.25
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. z The local address is the "PC" IP address. z The Adjacent address is the Point to point address of the NE where the PC is connected.
3.26
This configuration has to be made by the PC administrator.
Page 3.26
3.8 Tunneling configuration
3.27
Page 3.27
3.8 Tunneling configuration IP over OSI Presentation
Its 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.
CT
EC
ISA
IP over OSI tunnels
Area n
3.28
Page 3.28
3.8 Tunneling configuration IP over OSI configuration Configuration
Comm/Routing Tunneling Configuration IP Over OSI
3.29
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: z OSPF (Open Shortest Path First) z RIP (Routing Information Protocol) z Both z None If OSPF or Both options are selected, also the Associated OSPF Area must be set.
Page 3.29
3.8 Tunneling configuration Route 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-ToPoint IP address (start) and the ISA card IP address (destination).
@ IP Point-To-Point card (EC) @ IP ISA card
EC ISA
CT
One route has to be created for each ISA card present in the network including ISA card(s) belonging to the NE where the CT is connected.
Routes
Area n
3.30
Page 3.30
3.8 Tunneling configuration Route 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.31
Page 3.31
3.8 Tunneling configuration Route 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.32
Page 3.32
3.8 Tunneling configuration Route 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
3.33
Destination Address (ISA cards)
Gateway Address (Point to Point card)
Interface address (PC)
CT
Page 3.33
3.8 Tunneling configuration ISA card supervision As soon as a route is declared, the supervision of the ISA cards is possible : z Open the 1320CT z Select the OMSN equipment z In the menu bar : select NE directory menu > realign ISA board population
OMSN Equipment ISA card
3.34
Page 3.34
3.8 Tunneling configuration ISA card supervision ISA card supervision z Select the ISA card z Launch the supervision :
Supervision start supervision (menu bar) Supervision menu show equipment
3.35
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.
Page 3.35
3.8 Tunneling configuration ISA card view
3.36
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.
Page 3.36
3.8 Tunneling configuration OSI over IP
Configuration
Comm/Routing Tunneling Configuration OSI Over IP

3.37
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.
Page 3.37
3.9 Network Time Protocol configuration
3.38
Page 3.38
3.9 Network Time Protocol configuration NTP server configuration
Configuration
Comm/Routing NTP Server Configuration

3.39
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 : z Enabling NTP protocol section allows to enable (Yes) or disable (No) the NTP protocol. z 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. z 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.
Page 3.39
3.9 Network Time Protocol configuration NE time
Look also: NTP icon, colour and shape
Configuration
NE Time
3.40
NTP Status z NTP Protocol = Disabled or Enabled; it depends on Enabling NTP Protocol setting (No or Yes) in NTP Server Configuration window. z 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 z NE Time refers to the NE z OS Time refers to the PC z 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.
Page 3.40
3 Communication parameter configuration Exercise
9Configure: 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.41
Page 3.41
3 Communication parameter configuration Evaluation
Objective: to be able to configure the communication and routing parameters in order to supervise the whole network from the OS
3.42
Page 3.42
4 Network topology creation
Alcatel University -8AS 90001 1860 VT ZZA Ed.05
4.1
Page 4.1
4 Network topology creation Session presentation
Objective: to be able to create and manage a network topology from the CT Program: 4.1 Map/Submap/NE creation 4.2 Map/Submap/NE management
4.2
Page 4.2
4.1 Map/Submap/NE creation
4.3
Page 4.3
4.1 Map/Submap/NE creation Map/Submap creation
To create a new map in NES: 1) Maps New Map 2) Select the Map Unnamed 3) Maps Save as Private/Public 4) Enter a new name 5) Maps Description (optional) To create a new submap inside the map, follow again the instructions previously given: Maps New Submap
4.4
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: z Private: only the WINDOWS user who performs the saving can manage the map z Public: all the WINDOWS users can manage the map
Page 4.4
4.1 Map/Submap/NE creation NE creation
To add a new NE in a map: 1) Select the Map 2) NE Directory Create NE 3) Insert NE address
4.5
NE physically connected to the CT: z The NE is recognized by the CT and automatically presented in the NES window. z If the same NE was already created in one only saved map, this map will be automatically opened. z If the same NE is already created in several saved maps, the operator must select one map. z If the Maps New option is selected, the plugged NE is presented in the view. NE physically not connected to the CT (Remote NE): z Follow the NE creation procedure For each NE the Description option can also be used.
Page 4.5
4.1 Map/Submap/NE creation SNMP NE creation
To add a new SNMP NE in a map: 1) Select the Map 2) NE Directory Create SNMP NE 3) Insert Basic Settings
4.6
Page 4.6
4.1 Map/Submap/NE creation Slave NE definition
4.7
Page 4.7
4.1 Map/Submap/NE creation Slave NE creation
4.8
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).
Page 4.8
4.2 Map/Submap/NE management
4.9
Page 4.9
4.2 Map/Submap/NE management Map/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.10
Page 4.10
4.2 Map/Submap/NE management NE 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
4.11
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
Page 4.11
4.2 Map/Submap/NE management NE management: NE supervised
To display or to change NE address in the map & in the NE: 1) NE Addresses Settings 2) Select the OSI stack settings option 3) Click on Set NE Address To change the User label or the Location name in the map & in the NE: 1) NE Addresses Settings 2) Select the Other settings option 3) Click on Change
4.12
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
Page 4.12
4.2 Map/Submap/NE management Tabbed window
In case of selection of several NEs, the right part of NES window provides a tab for each NE
4.13
Page 4.13
4.2 Map/Submap/NE management NE user password modification
4.14
Default login: ADMIN Default password: ADMIN
Page 4.14
4.2 Map/Submap/NE management NE user creation
4.15
Operator: five types of operators are defined with different NE access rights as follow: z admin: all functionality except cross-connection deletion if created by RM z Administrator: all functionality except cross-connection deletion if created by RM z Constructor: all functionality except selection of manager assignment (SY manager, RM, etc) z Operator: all functionality except selection of manager assignment (SY manager, RM, etc) z Viewer: no modification is allowed
Page 4.15
4 Network topology creation Exercise
9 Create a new public map 9 Add NE in your map 9 Change the User label and the
Location name of the local NE 9 Start-up the supervision on a remote NE 9 Create a new user profile for the local NE
4.16
Page 4.16
4 Network topology creation Evaluation
Objective: to be able to create and manage a network topology from the CT
4.17
Page 4.17
4 Network topology creation Notes
4.18
Page 4.18
5 Alarm management
5.1
Page 5.1
5 Alarm management Session presentation
Objective: to be able to manage the alarms Program: 5.1 External point management 5.2 Alarm notification 5.3 Alarm identification in NE view 5.4 ASAP management 5.5 NE time check 5.6 AS application handling
5.2
Page 5.2
5 Alarm management
5.1 External point management
5.3
Page 5.3
5.1 External point management External Points view
5.4
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: z The external point type: Input or Output. z The user label: a user-friendly label associated to the configurable external point. z 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: z output criteria: if configurated, displays the alarm event and the board affected associated to the output point.
Page 5.4
5.1 External point management External input/output point display
5.5
Page 5.5
5.1 External point management External point configuration
For Output point For Input point
5.6
External input point configuration z 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) z External State: this field is set to Off and cant be changed by the operator z Probable cause: this field is set to housekeeping and cant be changed by the operator External output point configuration z 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) z 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 z 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
Page 5.6
5 Alarm management
5.2 Alarm notification
5.7
Page 5.7
5.2 Alarm notification Alarm notification/inhibition
5.8
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.
Page 5.8
5.2 Alarm notification Alarm notification permission
5.9
Page 5.9
5.2 Alarm notification Alarm resynchronisation
5.10
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.
Page 5.10
5 Alarm management
5.3 Alarm identification in NE view
5.11
Page 5.11
5.3 Alarm identification in NE view Screen hierarchy
EQUIPMENT
RACK
SUBRACK
BOARD
Alarm synthesis boxes (Equipment)
Port alarm synthesis box (Transmission)
Board alarms (Equipment)

5.12
Page 5.12
5.3 Alarm identification in NE view Alarm synthesis screens Rack view Subrack view
Alarms synthesis box
Board alarms synthesis boxes
Subrack alarms
5.13
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)
Page 5.13
5.3 Alarm identification in NE view Alarm synthesis screens Subrack view Board view
Board alarms synthesis box
Board alarms
5.14
Page 5.14
5.3 Alarm identification in NE view Alarm synthesis screens Board view Port view
Board transmission alarm synthesis box
Board transmission alarms
5.15
Page 5.15
5.3 Alarm identification in NE view Abnormal conditions
To display the abnormal conditions: Diagnosis
Abnormal
Condition List
Navigation to the view of the selected object 5.16
Abnormal Conditions are: loopbacks, force or lockout command on protection schemes, force command on laser, board missing,...
Page 5.16
5.3 Alarm identification in NE view Exercise
9 Open the External Points view 9 Configure an external output point 9 Remove (software) a board in the
Equipment view 9 Check the alarms 9 Extract (hardware) another board in the subrack 9 Compare the alarms 9 Open the abnormal condition list
5.17
Page 5.17
5 Alarm management
5.4 ASAP management
5.18
Page 5.18
5.4 ASAP management ASAP list
To display the list of ASAPs : Configuration
Alarms Severities
5.19
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: z No Alarms (Profile 1) : all alarms are disabled (non alarmed) z Primary Alarms (Profile 2) z Path Alarms or No Remote Alarms (Profile 3) z All alarms (Profile 4) : all alarms are enabled
Page 5.19
5.4 ASAP management ASAP display
5.20
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 Name list. To find a particular probable cause, enter its name in the Search entry box at the bottom.
Page 5.20
5.4 ASAP management ASAP creation
5.21
The created ASAP is identified with following names: #10001, #10002, The maximum number of new ASAP can change according to NE type (SDH, WDM).
Page 5.21
5.4 ASAP management ASAP modification
5.22
To modify the severity associated with a probable cause, select the option button: z Service Affecting: not protected probable cause z Non Service Affecting: protected probable cause z Service Independent (not used)
Page 5.22
5.4 ASAP management ASAP assignment
5.23
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 object 2) Configuration Set Alarms Severities 3) Select an ASAP 4) Click on OK to send the selected ASAP to the selected object Selected object and subordinates (examples for OMSN): z subordinates of SPI are: RST, MST and AU4 z subordinates of PPI are: E1, P12 and VC12 z subordinates of AU4 are: HPOM, HTCM, HTCT Choose current ASAP: z 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
Page 5.23
5.4 ASAP management ASAP deletion
5.24
It is possible to delete an ASAP only if it isnt assigned to any object.
Page 5.24
5.4 ASAP management Exercise
9 Display the ASAP list 9 Create your own ASAP 9 Select a block and assign your ASAP 9 Assign to that block another ASAP 9 Delete your ASAP
5.25
Page 5.25
5 Alarm management
5.5 NE time check
5.26
Page 5.26
5.5 NE time check
To make sure that NE time and CT time are the same: Configuration
NE Time
5.27
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.
Page 5.27
5 Alarm management
5.6 AS application handling
5.28
Page 5.28
5.6 AS application handling AS principles
AS is dedicated to receive, store, display in real time alarms raised by different sources (CURRENT ALARMS)
Network ressources Display alarms

CURRENT ALARMS
AS Operator
Raise & clear alarms
Manage alarms
5.29
Maximum number of current alarms: up to 10000
Page 5.29
5.6 AS application handling AS start up from NES
1) select a supervised NE 2) Supervision Show NE Alarms
Supervision Alarm Surveillance

5.30
In NES, AS can be started in two ways: z Show NE Alarms provides the alarms of the selected NE under supervision. z Alarm Surveillance provides the alarms of all the NEs under supervision in the map.
Page 5.30
5.6 AS application handling AS start up from USM
Diagnosis
Alarms NE Alarms or
5.31
USM: User Service Manager It is possible to select a subset of alarms: z NE Alarms: all NE alarms are listed in the AS report z Object Alarms: only alarms of the selected object are listed in the AS report z Subtrees Alarms: only alarms of the selected object and of the relevant subtrees are listed in the AS report z Equipment Alarms: only alarms of equipment are listed in the AS report z Transmission Alarms: only alarms of transmission are listed in the AS report
Page 5.31
5.6 AS application handling Counter Summary window
Flag to indicate new alarms in the sublist
Specific counter of cleared alarms
Overflow status of the current alarm list
5.32
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: z The Main Alarm List contains all available alarms z The Critical, Major, Minor, Warning, Indeterminate sublists contain respectively critical major, minor, warning, indeterminate alarms z 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: z Inactive Sublists: if this option is activated, the user can see the inactive sublists z 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. z 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: z Create a sublist z Modify a sublist z Delete a sublist z Activate or Deactivate a current alarm sublist (Inactive sublists have all their counters set to x ) z Open a sublist z Close a sublist z Save a sublist z Exit from the current window
Page 5.32
5.6 AS application handling Sublist 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
5.33
Sublist creation To duplicate the characteristics of an existing sublist: 1) Select the source sublist 2) 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 Sublist 2) Sublist Create Then the Counter Summary window is updated and a new sublist is displayed.
Page 5.33
5.6 AS application handling Sublist management: DISPLAY panel
Sublist name
Sublist colour (double click to modify)
Other available attributes (to move to the displayed attributes list, select and click on the arrow)
Click here to validate modifications
Currently displayed attributes in the sublist (select and click on the arrow to remove from the list)
5.34
Page 5.34
5.6 AS application handling Sublist management: FILTER panel

To save your filter To select a saved filter Filter on status Filter on date and time
Filter on severity Filter on alarm type Filter on correlation parameter Filter on probable cause (click on Select... to make your choice)
5.35
In Filter Name section, the matching status is notified. One of the following three statuses may appear: z Match None: no alarm could match the filter. In this case, there may be conflicting options specified in the filter. z Match Some: some alarms may match the filter. z 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: z Object instance type If Friendly Name is selected, the user can also specify the nature of the test: 9 Equal: self-understanding 9 Substring: the actual Friendly Name must contain the specified string 9 Begin with: the actual Friendly Name must begin by the specified string 9 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: 9 Base: to only consider the object specified by the instance 9 Subtree: to also include in the search all the objects contained in the specified object z Object class type The 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.
Page 5.35
5.6 AS application handling Sublist management: SORT panel
To select a saved sort
To save your sort choice
Click here to select the order (increment or decrement) Parameters not used to sort the sublist (select and click on the arrow to use it) Parameters used to sort the sublist
5.36
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.
Page 5.36
5.6 AS application handling Sublist 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.37
Page 5.37
5.6 AS application handling Actions on current alarms
By using the Action menu, the user can: z Select an alarm z Reserve or Unreserve an alarm z Create a Trouble Ticket z Acknowledge an alarm z Perform a Manual Purge of alarms z Outpout alarms (see next slide) By using the Display menu, the user can: z Get More Info about an alarm z Display Hidden Coloumns z Auto-Select incoming alarms
5.38
Reserving/Unreserving alarms To 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 Ticket A 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 alarms By 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 alarm When the user purges alarms, they disappear from the sublist. Exporting (Output) alarms The user can select one or more alarms in the sublist and export them to a file or to a printer. Auto-selecting the incoming alarms New alarms are automatically selected when they appear in the sublist.
Page 5.38
5.6 AS application handling Output alarms and Alarm Formatter
5.39
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).
Page 5.39
5.6 AS application handling AS facilities from the Counter Summary window
To resynchronize the AS application with network resources: Option Synchronization To get reports on performed actions: Option Report
5.40
Resynchronizing AS The 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 actions After an action has been launched on the users request, it may be useful to visualize a report offering detailed informations about the progress or achievement (successful or not) of his action. z 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 z 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.
Page 5.40
5.6 AS application handling AS facilities from the sublist window
To navigate from AS to an external application: Navigation External Application
EML-USM
5.41
EML-USM: Element Manager Layer- User Service Manager
Page 5.41
5.6 AS application handling Exercise
9 Check NE time 9 Set NE time with OS time if necessary 9 Start the AS application 9 Display the Major sublist 9 Create your own sublist with following
parameters:
Major alarms Communications alarms Cleared alarms In the last 24 hours Sort the sublist by event date & time Emit a tone for incoming alarms
9 Perform actions on alarms (reserve,) 9 Navigate from AS to EML-USM

5.42
Page 5.42
5 Alarm management Evaluation
Objective: to be able to manage the alarms
5.43
Page 5.43
5 Alarm management Notes
5.44
Page 5.44
6 Administration for operators
6.1
Page 6.1
6 Administration for operators Session presentation
Objective: to be able to administrate the NE and the CT Program: 6.1 NE software download 6.2 CT environment management 6.3 Log files display
6.2
Page 6.2
6.1 NE software download
6.3
Page 6.3
6.1 NE software download Installation: introduction
Before starting the software download by means of USM application: z the new NE software package must be transfered to Q3CT directory. Two types of installation are possible: only SDH software package installation (see next slide) SDH and Specific Software packages installation in case of ATM, PR, PR-EA,... boards (see next slide and the following).
6.4
Page 6.4
6.1 NE software download Installation: Computer Hardware Configuration
The computer configuration to be used as a Craft Terminal support consists of :

Release Q3CT-P v1.1.5.5 Q3CT-P v1.2.1.5 Q3CT-P v1.3.0.5 Q3CT-P v1.3.0.7 Q3CT-P v1.3.1 Q3CT-P v1.5.x CT-K v2.0.1 CT-K v2.0.2 CT-K v3.0.0 CT-K v3.0.1 Platform Windows NT Windows NT Windows NT, 2000 Windows NT, 2000 Windows NT, 2K, XP Windows NT, 2K, XP Windows NT, 2K, XP Windows NT, 2K, XP Windows 2K, XP Windows 2K, XP
CPU Pentium II 200 Mhz RAM 128 Mb (256 Mb suggested) HARD DISK free space 4 Gb Swap area 300 Mb MONITOR 12 (14 suggested) RESOLUTION 1024 x 768 pixel CDRom drive For Craft Terminal Software Installation and Handbook looking through the CDROM
6.5
options: z Ethernet port As an alternative to the CDRom drive for Craft Terminal Software Installation.In alternative to the serial bootstrap, the Ethernet port can be used for LAN based bootstrap, In this case it permits to download the NE without software inside, reducing time to some minutes. z one 3 1/2 floppy disk drive (1 , 44MB) to facilitate external files exchanges and to support the installation of equipment other than infomodel Alcatel, generally managed by the 1320 NX Craft Terminal (NECTAS application). z a printer (serial or parallel known by WINDOWS)
Page 6.5
6.1 NE software download Installation: SDH software package
6.6
To install SDH software package: 1) Supervision Files Administration Software Package Administration 2) Select SDH tag, click Install, select the xxx.dsc file corresponding to the new NE software package in the relevant directory ( Ect/Swdw/... for CD-ROM) and click Open 3) Wait for the message Successful installation of the new Software Package At this point the SDH Software Package is installed in Q3CT directory and, if no Specific Software component is required, is available to be downloaded as explained by Software download slide.
Page 6.6
6.1 NE software download Installation: Service Specific software package
6.7
To install Service Specific software package: 1) Supervision Files Administration Software Package Administration 2) Select SERV. SPEC. tag, click Install, select the xxx.dsc file corresponding to the new Service Specific software package in the relevant directory ( Ect/Swdw/... for CD-ROM) and click Open 3) Wait for the message Successful installation of the new Software Package At this point the Specific Software component is installed in Q3CT directory.
Page 6.7
6.1 NE software download Installation: Merge
6.8
Before downloading, the SDH software package and the Service Specific software package(s) must be merged in order to have just one software package with all of the necessary files. To merge: 1) Select the SDH tag, select the SDH software package and press Create Enhanced 2) Press YES in OMSN Creation succeded window --> OMSN tag is automatically selected 3) Select the SDH software package and the Service Specific software package and press Add Note: selecting SDH tag, the name of the equipment is 1660SM ; selecting OMSN tag, the name of the equipment is 1660SME, where E stands for Enhanced.
Page 6.8
6.1 NE software download Software download
To download the merged software package (SDH+Service Specific) To download only the SDH software package
6.9
To download the software in the desired NE: 1) Open the NE view (USM) 2) Download Init download 3) Select the new software 4) Click on OK to start the download 5) A Software download in Progress dialogue box is displayed 6) Wait for the message Software download completed! The new software is not running after downloading since it replaces the standby software. Thus, the new software must be activated (see next slide).
Page 6.9
6.1 NE software download Software details / activation
To get information about a software package
To activate a new software package
6.10
USM view --> Download --> Units info... The Software packages information dialogue box displays the name and type of the NE, the respective package name and status of the committed and (if existing) the uncommitted (Standby) software. The SW units det. button allows to give more information about a selected software package. To activate the new software: z select the Activate option with the Action roll up menu in the Software packages information window z confirm and wait for the reestablishement of the Q3 communication
Page 6.10
6.2 CT environment management
6.11
Page 6.11
6.2 CT environment management Process control
To list the running and stopped processes on the CT: NES CT Environment
Process control
6.12
The Process Control is selectable but reserved for Alcatel personnal, typically for assistance.
Page 6.12
6.2 CT environment management Software list
To list the software installed in the CT: NES CT Environment
List Software
6.13
List Software is independent from the NE management state.
Page 6.13
6.2 CT environment management NES backup
To save the data configured in the Network Element Synthesis view (mainly the created maps): 1) CT Environment Backup 2) Select the directory where to save data
6.14
This operation is independent from the NE management state.
Page 6.14
6.2 CT environment management NES restore
To restore in the Network Element Synthesis view the configuration data previously saved in the directories of the PC: 1) CT Environment Restore 2) Select the directory where the NES configuration data are present
6.15
This operation is independent from the NE management state. After the operation, the restored data are present in the NES view; for example the maps of the previously saved file are summed to the maps created in the view.
Page 6.15
6.2 CT environment management ANTP configuration
6.16
The ANTP option is disabled (greyed) if the ANTP component is not installed. ANTP component is inside the Lower Layer Manager software. In the usual CT scenario it is assumed that the NEs get the time from an OS and the CT sets its time with the local NE time . The following configuration is required: z WINDOWS user must be allowed to modify the PC date/time (i.e. Administrator profile). z In NES --> CT Environment --> ANTP, ANTP Server address automatic management must be selected in order to have the CT time synchronised with the local NE you are plugged in: after each Start Supervision on the local NE its NSAP is written in the Alcatel Network Time Protocol Setting window. z in the Alcatel Network Time Protocol Setting window, Enable Client must be selected. Practically: 1) In NES --> CT Environment --> ANTP select ANTP Server address automatic management 2) Start Supervision on the local NE. 3) If Time Mismatch report is issued, select No. 4) In Alcatel Network Time Protocol Setting window: the address of the local NE is already written in Main box and the operator have to select Enable Client and press OK 5) After about five minutes the date/time of the PC is aligned with the date/time of the NE When a Start Supervision request is completed, the CT gets the NE time and compares it with the PC time. z If the difference is lower than 1 day, the CT assumes that the NE and CT have both an acceptable time and the difference is due to clock misalignment. In this case the CT will realign the PC time with the NE time. z If the difference is higher than 1 day, the CT assumes that the NE or the CT has unacceptable time difference. In this case the operator is informed with a Time Mismatch report. The operator may want that CT be aligned with a fixed device (remote NE, OS,...). In this case: z ANTP Server address automatic management must not be selected. z In Alcatel Network Time Protocol Setting window the address of the device must be manually written. z It is not necessary the device be supervised. Alcatel Network Time Protocol Setting window can be also opened from WINDOWS: Start --> Programs --> Alcatel --> Alcatel Network Time Protocol --> ANTP Settings Enable Server selection allows the CT to deliver its time. Both Enable Client and Enable Server can be active at the same time.
Page 6.16
6.3 Log files display
6.17
Page 6.17
6.3 Log files display NE alarm log
6.18
Page 6.18
6.3 Log files display NE event log
6.19
Page 6.19
6.3 Log files display CT event log
6.20
Page 6.20
6.3 Log files display CT activity log
To display the system activity log, select the Activity Log panel in NES It gives information on: z Pending activities z Completed activities
6.21
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. z All Pending activities move to the Completed sub-tree once they are finished, regardless to whether they succeeded or failed. z 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. z 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".
Page 6.21
6 Administration for operators Exercise
9 Install the new software package into

the CT 9 Simulate a software download (don t click the last OK) 9 Perform a NES backup 9 Configure ANTP 9 Display NE alarm log 9 Display CT event log
6.22
Page 6.22
6 Administration for operators Evaluation
Objective: to be able to administrate the NE and the CT
6.23
Page 6.23

02 Alcatel 1320CT Training Manual PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

02 Alcatel 1320CT Training Manual PDF

Uploaded by

Copyright:

Available Formats

Alcatel 1320CT 1.7.

Training manual 8AS 90001 1860 VH ZZA Ed. 05 Edition 2004

Page intentionally left blank

Note : Please print this document with comments pages

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

Equipment view opening 1.1

Subrack and board declaration 2.1

Communication parameter configuration..3.1

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

Alarm management.. 5.1

Administration for operators. 6.1

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

1 Equipment view opening

Alcatel University - 8AS 90001 1860 VT ZZA Ed.05

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

1 Equipment view opening Session presentation

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

1 Equipment view opening

Alcatel University - 8AS 90001 1860 VT ZZA Ed.05

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

Software product for download to update the NE

Software product for management to install in the PC

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

1 Equipment view opening

1.2 1320CT start-up

Alcatel University - 8AS 90001 1860 VT ZZA Ed.05

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

1.2 1320CT start-up NES window opening

1.2 1320CT start-up Lower Layers Manager (LLM)

1 Equipment view opening

1.3 NE supervision start-up

Alcatel University - 8AS 90001 1860 VT ZZA Ed.05

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

1.3 NE supervision start-up

Highest alarm severity

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

1 Equipment view opening

Alcatel University - 8AS 90001 1860 VT ZZA Ed.05

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

Severity alarm synthesis

Domain alarm synthesis

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

1 Equipment view opening

Alcatel University - 8AS 90001 1860 VT ZZA Ed.05

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

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

1 Equipment view opening

1.6 Navigation in NE view

Alcatel University - 8AS 90001 1860 VT ZZA Ed.05

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

1.6 Navigation in NE view Domain views

To open a particular NE domain view: Views Equipment

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

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

1.6 Navigation in NE view Navigation principles in Equipment View (2)

To return to the previous view: z Views Backward

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

1 Equipment view opening

1.7 ISA boards supervision

Alcatel University - 8AS 90001 1860 VT ZZA Ed.05

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

1.7 ISA boards supervision