
- •Introduction
- •Laboratory work №1
- •Introduction to the management of dss si2000
- •The purpose of the work
- •Key positions
- •Key questions
- •Hometask
- •Laboratory task
- •Laboratory work №2
- •Key questions
- •Hometask
- •Laboratory task
- •Laboratory work №3
- •3. Control questions
- •4. Hometask
- •5. Laboratory task
- •Laboratory work №4
- •Key questions
- •Hometask
- •Laboratory task
- •Laboratory work №5
- •3. Key questions
- •4. Hometask
- •5. Laboratory task
- •Laboratory work №6
- •2.2 Forwarding.
- •2.3 Identification services:
- •2.4 Waiting:
- •2.5 Barring of the calls:
- •2.6 Abbreviation:
- •2.7 Group.
- •2.8 Multiparty:
- •2.9 Alarm and Notification:
- •3. Key questions
- •4. Hometask
- •5. Laboratory task
- •Laboratory work №7
- •3. Key questions
- •4. Hometask
- •5. Laboratory task
- •6. The content of the protocol
- •Laboratory work №8
- •1 Objectives
- •2 Key positions
- •2.2 Stages of outgoing call routing management.
- •3 Control questions
- •4 Hometask
- •5 Lab assignment
- •6 Report contents
- •Laboratory work №9
- •1 Objective
- •2 Key positions
- •Laboratory work №10
- •3 Control questions
- •4 Home task
- •5 Lab task
- •Laboratory work №11
- •Laboratory work №12
- •3 Control questions
- •4 Home task
- •5 Lab task
- •6 Report contents
- •Laboratory work №13
- •1 Objective
- •2 Key positions
- •In Operation
- •3 Control questions
- •4 Home task
- •5 Lab task
- •6 Report contents
- •Laboratory work №14
- •1 Objectives
- •2 Key positions
In Operation
Cold Stand By
No Response
Unknown
5. Alarm Status – indicates the urgency degree of the most urgent fault signal:
Urgent – there is at least one urgent fault signal, or the TCP/IP connection is broken;
Semi Urgent – there is at least one semi-urgent fault signal;
Non Urgent – there is at least one non-urgent emergency signal;
Normal – no faults appeared in unit;
Unknown
6. UA – quantity of urgent fault signals;
7. SA - quantity of semi-urgent fault signals;
8. NA - quantity of non-urgent fault signals;
9. Disk – allocated status of hard drive, in %;
10 Reported at – the time of fault error receive;
2.3 Indicating the fault quantity changing in nodes. If the number of faults in nodes has changed, the following indication will appear:
the message <N Unacknowledged Object> will appear in Alarm Monitoring window header;
the window, indicating the highest priority error, appears in tab header;
the marker, indicating that the manager had took care of all faults, disappears;
the application uses audible indication.
The Suspend command allows to stop the node status monitoring (fault signals from this unit are not shown). In this case, the unit marker color turns to gray, and Connection State parameter takes a Suspended value.
"AMG", "CMG", FMG", "PMG", "DOC", "SMG"; "SYS"- a command to launch the particular application for controlling the particular unit.
All actions on acknowledging the emergency states of controllable devices from all the units, driven from the MN, are recorded in special file. You can view this file in Alarm Monitoring > File > Confirmation Log.
2.4 Viewing the emergency signals in SN/AN. In order to do this, use Open command to open the <Node: Hostname> window, which shows the current state of emergency signals from controllable unit.
The table top is shows nearly the same information, that Alarm Monitoring window does.
The <Node: Hostname> table columns show the following:
Priority – the urgency degree of emergency signal, each priority also has its own color:
red - Urgent or No Response or Link Down,
yellow - Semi Urgent,
cyan - Non Urgent.
Module Type;
Object Identity;
Object Type;
Error Code;
Error Description.
3 Control questions
3.1 What for the Alarm Monitoring application is intended?
3.2 What the way the applications are interacting with network nodes?
3.3 List all possible types of faults in nodes.
3.4 What information is shown in main window of Alarm Monitoring?
4 Home task
4.1 Answer the control questions in writing.
4.2 Learn the Key Positions.
5 Lab task
5.1 Launch the Alarm Monitoring.
5.2 Familiarize with nodes which are monitored by the application.
5.3 Select nodes, connection to which is active.
5.4 Take a look on faults, present in active units. Determine the malfunction type, its causes and recovery methods using the documentation.
5.5 Activate one of ports for E1 insertion on considered node.
5.6 Refresh the Alarm monitoring window. Explain the causes of new emergency signals.
5.7 Perform the 5.4 task for all active nodes.
5.8 Propose means to take care of existing emergency signals.