SYNFONET Access Node Manager NOkia

SYNFONET Access Node Manager
Release A for SAN Release C2.0 Users Manual C33543.21 A1
C33543002SE_01
E Copyright Marconi Communications
SYNFONET Access Node Manager Users Manual
E COPYRIGHT Marconi Communications 2000 All rights reserved.

No part of this publication may be copied, distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language without the prior written permission of Marconi Communications. The manufacturer has made every effort to ensure that the instructions contained in the documents are adequate and free of errors and omissions. The manufacturer will, if necessary, explain issues which may not be covered by the documents. The manufacturer s liability for any errors in the documents is limited to the correction of errors and the aforementioned advisory services. The documents have been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using them. The manufacturer welcomes customer comments as part of the process of continual development and improvement of the documentation in the best way possible from the user s viewpoint. Please submit your comments to the nearest Marconi sales representative. Marconi is a trademark of Marconi Communications. SYNFONET is a trademark of Marconi Communications. Any other trademarks mentioned in the documents are the property of their respective owners.
ii
C33543002SE_01
Document History
Document C33577011SE_00 Date 23.06.1999 Comment This document is valid for program P31614.0x release A, which is included in SAN C2.0 CDROM P31512.10. Please see Section 2.4 for the list of product codes. Released by Marconi Communications
C33441004SE_01
June 2000
C33543002SE_01
iii
iv
C33543002SE_01
Contents
Chapter 1 About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Typographical conventions . . . . . . . . . . . . . . . . . . . . . . . .
1-1
1-2
Chapter 2 Introduction to the SYNFONET Access Node Manager . . 2-1

2.1 2.2 2.2.1 2.2.2 2.2.3 2.2.4 2.3 2.4 Using the Node Manager . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware and software requirements . . . . . . . . . . . . . . . Hard disk storage requirements . . . . . . . . . . . . . . . . . . . . . . Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NDIS driver version information . . . . . . . . . . . . . . . . . . . . . Other sources of information . . . . . . . . . . . . . . . . . . . . . . . . Copyright notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 2-1 2-3 2-3 2-4 2-4 2-4 2-4
Chapter 3 Installing the SAN Manager software . . . . . . . . . . .

3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.2 3.3 Modifications to your system . . . . . . . . . . . . . . . . . . . . . . Files and directories created . . . . . . . . . . . . . . . . . . . . . . . . Group windows created (NT 3.51) . . . . . . . . . . . . . . . . . . . Folders created (NT 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Files changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the stack startup . . . . . . . . . . . . . . . . . . . . . . . .
3-1
3-2 3-2 3-3 3-3 3-4 3-4 3-8
C33543002SE_01
3.4 3.5 3.6 3.7 3.7.1 3.7.2 3.7.3 3.7.4 3.7.5 3.7.6 3.7.7 3.7.8 3.7.9 3.7.10
Changing the NSAP address after installation . . . . . . . . Enabling security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing related products . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Insufficient disk space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Q3 stack not running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SANM does not start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cannot connect to node . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backedup databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Insufficient memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Low virtual memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a LAN card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing an older version of the software . . . . . . . . . . . . . No nodes found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-9 3-10 3-11 3-11 3-11 3-11 3-11 3-11 3-12 3-12 3-12 3-12 3-12 3-13
Chapter 4 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 4.2 4.2.1 4.2.2 4.2.3 4.2.4 4.2.5 4.3 4.4 4.4.1 4.4.2 4.4.3 4.4.4 4.4.5 4.4.6 4.4.7 4.4.8 4.4.9 4.4.10 4.4.11 4.5 4.5.1 About the Node Manager . . . . . . . . . . . . . . . . . . . . . . . . . Node Manager Overview . . . . . . . . . . . . . . . . . . . . . . . . . The application window . . . . . . . . . . . . . . . . . . . . . . . . . . . The Node Subrack window . . . . . . . . . . . . . . . . . . . . . . . . . Tooltips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the left and right mouse buttons . . . . . . . . . . . . . . . . Using the keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Node Manager . . . . . . . . . . . . . . . . . . . . . . . Operating the Node Manager . . . . . . . . . . . . . . . . . . . . . . Operation methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receiving data from the node . . . . . . . . . . . . . . . . . . . . . . . Making changes to the node . . . . . . . . . . . . . . . . . . . . . . . . Indicating progress of an operation . . . . . . . . . . . . . . . . . . . Failing to send or refresh data . . . . . . . . . . . . . . . . . . . . . . . Aborting an operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communications failure behaviour . . . . . . . . . . . . . . . . . . . Reconnecting to a node . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving node configuration data . . . . . . . . . . . . . . . . . . . . . . Printing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping the Node Manager . . . . . . . . . . . . . . . . . . . . . . . Closing the connection to a node . . . . . . . . . . . . . . . . . . . .
4-1
4-1 4-2 4-2 4-7 4-10 4-11 4-12 4-15 4-16 4-16 4-17 4-18 4-19 4-22 4-23 4-23 4-23 4-24 4-24 4-24 4-27 4-27
vi
C33543002SE_01
4.5.2 4.5.3
Closing document windows . . . . . . . . . . . . . . . . . . . . . . . . Closing the SAN Node Manager . . . . . . . . . . . . . . . . . . . . .
4-27 4-28
Chapter 5 Installing nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1 5.2 5.3 5.4 5.4.1 5.5 5.6 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a new node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reinstalling a node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the node settings . . . . . . . . . . . . . . . . . . . . . . Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating the Real Time Clock window . . . . . . . . . . . . . . . Installing units in the node . . . . . . . . . . . . . . . . . . . . . . . . Initialising a node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-1
5-1 5-2 5-10 5-11 5-15 5-17 5-27 5-30
Chapter 6 Managing SYNFONET Access Nodes . . . . . . . . . . .

6.1 6.1.1 6.1.2 6.1.3 6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.2.5 6.2.6 6.3 6.3.1 6.3.2 6.3.3 6.3.4 6.3.5 6.3.6 6.3.7 6.3.8 6.4 Q3 addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting to a node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Address of the PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Address of a node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Node names and addresses . . . . . . . . . . . . . . . . . . . . . . . . Name of a node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Node areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rules for assigning node and area names . . . . . . . . . . . . . . Connecting to nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storing node and area information . . . . . . . . . . . . . . . . . . . Copying the address database to another PC . . . . . . . . . . . Connecting to a node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the full name and address details of a node . . . . . Connecting to a node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the address details of a node . . . . . . . . . . . . . . . . Deleting a node address . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a new node address . . . . . . . . . . . . . . . . . . . . . . . . Creating a new area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the address details of an area . . . . . . . . . . . . . . . Deleting an area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management and auxiliary channels . . . . . . . . . . . . . . . .
6-1
6-1 6-1 6-2 6-3 6-3 6-3 6-4 6-4 6-5 6-6 6-7 6-7 6-8 6-9 6-10 6-11 6-12 6-12 6-13 6-15 6-15
C33543002SE_01
vii
6.4.1 6.4.2 6.4.3 6.4.4 6.5 6.5.1 6.5.2
Q3 management channels . . . . . . . . . . . . . . . . . . . . . . . . . . Manual adjacencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overhead connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summing points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EOW Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring an EOW Unit . . . . . . . . . . . . . . . . . . . . . . . . Setting the Manager Options . . . . . . . . . . . . . . . . . . . . . . View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Polling window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-16 6-21 6-24 6-30 6-32 6-32 6-34 6-34 6-35
Chapter 7 Configuring synchronisation . . . . . . . . . . . . . . . . . . .

7.1 7.1.1 7.1.2 7.1.3 7.1.4 7.2 7.2.1 7.2.2 7.2.3 7.2.4 7.2.5 7.2.6 7.3 7.3.1 7.3.2 7.4 7.5 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Node selectors information . . . . . . . . . . . . . . . . . . . . . . . . . Availability of synchronisation sources . . . . . . . . . . . . . . . . Quality of synchronisation sources . . . . . . . . . . . . . . . . . . . Priority of synchronisation sources . . . . . . . . . . . . . . . . . . . Viewing and configuring the node clock . . . . . . . . . . . . . Changing the priority list . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the synchronisation source . . . . . . . . . . . . . . . . . . Viewing selector information . . . . . . . . . . . . . . . . . . . . . . . Removing synchronisation sources . . . . . . . . . . . . . . . . . . . Configuring the source selection mode . . . . . . . . . . . . . . . . Calibrating the node clock . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing and configuring the output clock . . . . . . . . . . . . Viewing the output synchronisation source . . . . . . . . . . . . . Configuring the output clock source . . . . . . . . . . . . . . . . . . Setting the quality of the synchronisation sources . . . . . Sending the synchronisation data to the node . . . . . . . . .
7-1
7-1 7-3 7-4 7-5 7-6 7-7 7-7 7-9 7-9 7-9 7-10 7-11 7-12 7-12 7-13 7-13 7-15
Chapter 8 Configuring 2Mbit/s interfaces . . . . . . . . . . . . . . . . .

8.1 8.1.1 8.1.2 8.2 8.2.1 8.2.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing a 2M interface unit to configure it . . . . . . . . . . . Blocks and alarm fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the configuration window . . . . . . . . . . . . . . . . . . . . Viewing block status alarms . . . . . . . . . . . . . . . . . . . . . . . . Viewing the Status of the 2M signal . . . . . . . . . . . . . . . . . .
8-1
8-1 8-2 8-2 8-3 8-3 8-5
viii
C33543002SE_01
8.2.3 8.2.4 8.3 8.3.1
Viewing the Status of the VC12 Signal . . . . . . . . . . . . . . . Configuring Individual Blocks in the 2M Window . . . . . . . CORE2M units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring individual blocks in the CORE2M window . .
8-6 8-8 8-17 8-17
Chapter 9 Configuring single-interface terminal multiplexers

9.1 9.1.1 9.1.2 9.2 9.2.1 9.2.2 9.2.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing an STM-1 single PIM interface unit to configure it . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blocks and alarm fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the configuration window . . . . . . . . . . . . . . . . . . . . Viewing Block Status alarms . . . . . . . . . . . . . . . . . . . . . . . . Configuring individual blocks . . . . . . . . . . . . . . . . . . . . . . . Configuring the TUG structure . . . . . . . . . . . . . . . . . . . . . .
9-1
9-1 9-1 9-2 9-3 9-4 9-5 9-14
Chapter 10 Configuring dual-interface terminal multiplexers .

10.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.1.1 Accessing an STM-1 dual PIM interface unit to configure it 10.1.2 Blocks and alarm fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2 10.2.1 10.2.2 10.2.3 Using the configuration window . . . . . . . . . . . . . . . . . . . . Viewing block status alarms . . . . . . . . . . . . . . . . . . . . . . . . Configuring individual blocks . . . . . . . . . . . . . . . . . . . . . . . Configuring the TUG structure . . . . . . . . . . . . . . . . . . . . . .
10-1
10-1 10-2 10-2 10-4 10-4 10-6 10-15
Chapter 11 Configuring 345M units . . . . . . . . . . . . . . . . . . . . . . .

11.1 11.1.1 11.1.2 11.1.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blocks and alarm fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing 345M block alarms . . . . . . . . . . . . . . . . . . . . . . . . Configuring individual blocks in the 345M window . . . . .
11-1
11-1 11-2 11-3 11-4
Chapter 12 Configuring cross connections . . . . . . . . . . . . . . . . .

12.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.1 Characteristics of cross connections . . . . . . . . . . . . . . . . . . 12.1.2 Cross connection path protection . . . . . . . . . . . . . . . . . . . .
12-1
12-2 12-2 12-2
C33543002SE_01
ix
12.1.3 Representing cross connections . . . . . . . . . . . . . . . . . . . . . . 12.1.4 Cross connection naming . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.5 Termination identification . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 Path protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.3 Viewing cross connections . . . . . . . . . . . . . . . . . . . . . . . . . 12.3.1 Sorting the Cross Connection window . . . . . . . . . . . . . . . . 12.4 12.5 Adding cross connections . . . . . . . . . . . . . . . . . . . . . . . . . Editing Cross Connections . . . . . . . . . . . . . . . . . . . . . . . .
12-3 12-3 12-4 12-6 12-7 12-7 12-8 12-11 12-13 12-13 12-15 12-17 12-18
12.6 Protecting Cross Connections . . . . . . . . . . . . . . . . . . . . . . 12.6.1 Signals which can be used for protection . . . . . . . . . . . . . . 12.7 12.8 12.9 Unprotecting Cross Connections . . . . . . . . . . . . . . . . . . . Deleting Cross Connections . . . . . . . . . . . . . . . . . . . . . . . Printing Cross connections . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 13 Using files to save and load data . . . . . . . . . . . . . . . .

13.1 Saving data in a window as text . . . . . . . . . . . . . . . . . . . . 13.2 Saving the whole node . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2.1 Details not saved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.3 13.4 Saving part of a node configuration to file . . . . . . . . . . . Saving the data from a window . . . . . . . . . . . . . . . . . . . .
13-1
13-2 13-2 13-5 13-5 13-6 13-7 13-7 13-13
13.5 Loading data from file . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.5.1 Loading a whole node configuration from file . . . . . . . . . . 13.5.2 Loading a window configuration from file . . . . . . . . . . . . .
Chapter 14 Managing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.1 14.1.1 14.1.2 14.1.3 14.1.4 14.2 14.2.1 14.2.2 14.2.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Descriptive text message of alarm . . . . . . . . . . . . . . . . . . . . Time and date of alarm occurrence . . . . . . . . . . . . . . . . . . . Alarm classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Visual alarm notification . . . . . . . . . . . . . . . . . . . . . . . . . . On the status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On the Node Subrack window . . . . . . . . . . . . . . . . . . . . . . . Windows which display alarm information . . . . . . . . . . . . .
14-1
14-2 14-2 14-6 14-6 14-7 14-8 14-8 14-9 14-10
C33543002SE_01
14.2.4 On the Block Status window . . . . . . . . . . . . . . . . . . . . . . . . 14.2.5 On the Current Alarm List window . . . . . . . . . . . . . . . . . . . 14.2.6 On the Cross Connection window . . . . . . . . . . . . . . . . . . . . 14.3 Configuring external alarms . . . . . . . . . . . . . . . . . . . . . . . 14.4 Configuring station alarms . . . . . . . . . . . . . . . . . . . . . . . . 14.4.1 Enabling or disabling station alarms . . . . . . . . . . . . . . . . . . 14.5 14.5.1 14.5.2 14.5.3 14.5.4 14.5.5 Using the Event history log . . . . . . . . . . . . . . . . . . . . . . . . Viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up the event history log file . . . . . . . . . . . . . . . . . . . Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14-12 14-13 14-15 14-16 14-18 14-18 14-19 14-19 14-21 14-22 14-22 14-23
Chapter 15 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1 15.2 15.3 Security principles in SAN . . . . . . . . . . . . . . . . . . . . . . . . Security as seen by the user . . . . . . . . . . . . . . . . . . . . . . . User access levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15-1
15-1 15-2 15-2 15-3 15-3 15-3
15.4 Security administration . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.1 Enabling security at installation . . . . . . . . . . . . . . . . . . . . . 15.4.2 Setting a user s access level . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 16 Performance monitoring . . . . . . . . . . . . . . . . . . . . . .

16.1 16.2 16.3 16.4 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring performance data collection . . . . . . . . . . . . Viewing current performance data . . . . . . . . . . . . . . . . . Viewing the performance history . . . . . . . . . . . . . . . . . . .
16-1
16-1 16-1 16-3 16-6
Chapter 17 Printing SYNFONET Access Node data . . . . . . . . . .

17.1 17.2 17.3 17.4 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up the printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing node data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing node data to file . . . . . . . . . . . . . . . . . . . . . . . . . .
17-1
17-1 17-1 17-2 17-2
C33543002SE_01
xi
Chapter 18 Downloading software to a network . . . . . . . . . . . . . 181

18.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 182 183 183 184 187 1810 18.2 Preliminary steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.1 Setting up an Operation Log . . . . . . . . . . . . . . . . . . . . . . . . 18.2.2 Selecting a software directory . . . . . . . . . . . . . . . . . . . . . . . 18.3 Selecting nodes to receive the download . . . . . . . . . . . . . 18.3.1 Downloading the software . . . . . . . . . . . . . . . . . . . . . . . . . . 18.3.2 Viewing an Operation Log . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 19 Node Version Control . . . . . . . . . . . . . . . . . . . . . . . . . 191

19.1 Accessing the Node Version Control tool . . . . . . . . . . . . 191
Appendix A Key to the SAN C2.0 Manager menus . . . . . . . . . . .

A.1 A.1.1 A.1.2 A.1.3 A.1.4 A.1.5 A.1.6 A.2 A.3 The Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Toolbar equivalents of commands . . . . . . . . . . . . . . . . . . Summary of secondary windows and dialogs . . . . . . . . .
A-1
A-2 A-2 A-3 A-4 A-5 A-6 A-6 A-7 A-9
Appendix B Default unit combinations . . . . . . . . . . . . . . . . . . . . .

B.1 B.2 B.3 Node subracks supported . . . . . . . . . . . . . . . . . . . . . . . . . Node types supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default node combinations . . . . . . . . . . . . . . . . . . . . . . . .
B-1
B-2 B-2 B-3
Appendix C Q3 address format . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.1 Structure of the Q3 address . . . . . . . . . . . . . . . . . . . . . . .
C-1
C-1
xii
C33543002SE_01
C.2 C.3 C.4
Editable fields of the Q3 address . . . . . . . . . . . . . . . . . . . Sizes and values for editable fields . . . . . . . . . . . . . . . . . . Defining node addresses . . . . . . . . . . . . . . . . . . . . . . . . . .
C-1 C-2 C-3
Appendix D Related products . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.1 D.2 Network Management System/10 . . . . . . . . . . . . . . . . . . . SYNFONET Alarm Manager . . . . . . . . . . . . . . . . . . . . . .
D-1
D-1 D-3
Glossary Index
C33543002SE_01
xiii
xiv
C33543002SE_01
Chapter 1 About this manual

This manual is for users of the SYNFONET Access Node (SAN) manager (Version C2.0). It contains all the information you need to start using the SAN C2.0 Manager to manage a SYNFONET Access Node, Version C2.0. For further information on the operation of the node hardware, refer to the SYNFONET Access Node Operating Manual. What you need to know first This manual assumes that you will be involved with installing and/or managing SYNFONET Access Nodes, and that you are familiar with Microsoft Windows. How to use this manual If you are not familiar with using Microsoft Windows, refer to the manuals supplied with your computer or to the Windows online tutorial, which contain a basic description of how to operate Windows. When you have read this and are confident about using Windows, you can continue reading this manual. This User s Manual provides the following information: Chapter 2 gives a brief general description of what the SAN C2.0 Manager does, and tells you what hardware and software are needed to run it. Chapter 3 describes how to install the SAN C2.0 Manager under the Windows NT operating system.
C33543002SE_01
1-1
Chapter 4 describes the design and basic operation of the SAN C2.0 Manager, and how it can be used to manage a SYNFONET Access Node. Chapter 4 also explains how to start and stop the SAN C2.0 Manager. Chapter 5 explains how to use the SAN C2.0 Manager to install a completely new SYNFONET Access Node or just to install additional units in an already installed SYNFONET Access Node. Chapter 6 explains how to connect to and manage a SYNFONET Access Node using the SAN C2.0 Manager. The remaining chapters in this manual describe how to use the SAN C2.0 Manager to manage and configure a SYNFONET Access Node . At the back of this manual is a set of Appendixes containing reference information, which you need not read until you need to look up some specific point. The Appendixes are followed by a Glossary and an Index.
1.1
Typographical conventions
Table 1-1 presents the typographical conventions used throughout this User s Manual.
1-2
C33543002SE_01
Italic font
Indicates a word or phrase that is emphasised, or a reference to the title of a manual, chapter or section. Example:
See Chapter 3 Installation

Bold font
Indicates the title of a window, or an option, command, field or group, or anything that you must type exactly as it appears. Examples:
Help Index means: choose Index from the Help menu. A:\install means: type A:\install
ALL CAPITALS
SMALL CAPITALS
Indicate a directory or file name. Example:
INSTALL.EXE
Indicate the keys of the terminal keyboard. Example:
CTRL
Font Courier
Indicates computer input and output. Highlights the start of a procedure. Indicates the end of a chapter.
"
Table 1-1
Typographical conventions
C33543002SE_01
1-3
1-4
C33543002SE_01
Chapter 2 Introduction to the SYNFONET Access Node Manager
2.1
Using the Node Manager

The SYNFONET Access Node Manager allows you to manage a SYNFONET Access Node. You can manage nodes of the current C2.0 release or nodes of the C1.5 or C1.0 releases. SYNFONET is the Synchronous Digital Hierarchy (SDH) transmission equipment produced by Marconi. Using the SAN C2.0 Manager you can:
D D D
Connect to and communicate with a SYNFONET Access Node Configure a SYNFONET Access Node to set it up for receiving and transmitting data on a network Obtain status information from a SYNFONET Access Node including information about any alarms that have been generated on the node Reconfigure a SYNFONET Access Node to modify its role in the network.
2.2
Hardware and software requirements

The SAN C2.0 Manager runs on standard PCcompatible computers. The SAN C2.0 Manager communicates with a SYNFONET Access Node via the Ethernet port connected from the back of the computer to the CORE or CORE2M unit in the subrack.
C33543002SE_01
2-1
Details of the hardware and software requirements are given in Table 2-1 (hardware requirements) and Table 2-2 (software requirements).
Feature Processor Memory Hard disk Display CD ROM drive Pointing device Interface ports Requirement Pentium 60 or equivalent (Pentium 120 recommended) 24 MB minimum, 32 MB recommended 34 MB minimum free space, 40 MB recommended Colour or grey scale (16 shades of grey) This is for installation purposes (see the note below). Mouse, tracker ball or equivalent with necessary controlling software Coaxial Ethernet port (BNC connector, not twisted-pair) for Q3 communication to the node Serial port or Parallel port for printer Mouse port (if a mouse is used as the pointing device)
Table 2-1 Note
Hardware requirements The product software is delivered on a CD ROM, but organised in floppy disk images so that if you want to have the product software only on floppy disks, you can easily copy it on to floppy disks.
2-2
C33543002SE_01
Feature Operating system
Requirement Windows NT Version 3.51 plus service pack 5, or Windows NT Version 4.0 plus service pack 3 or above, or Windows NT Server 4.0, Terminal Server Edition plus service pack 3 or above. Microsoft Windows NT NDIS Version 3.0-compliant
Graphical interface NDIS driver
Table 2-2 Note
Software requirements If desired the node manager user interface can be accessed from a UNIX machine, with the actual program running on an NT server. When using Windows NT Version 3.51, WinDD software is required whereas when using Windows NT Version 4.0 the same role is played by the Terminal Server software.
Memory requirements At least 24 MB of RAM is required to support the Windows NT operating system, communications software and SAN C2.0 Manager. Although it may be possible to use less memory, this may cause a significant loss of performance. Any other applications in use at the same time will use system resources and reduce performance. Service pack requirements for Windows NT 4.0 If you are using Windows NT 4.0, you must have at least Service Pack 3 installed on your PC in order to run SAN C2.0 Manager. 2.2.1 Hard disk storage requirements At least 34 MB of hard disk space is needed for use exclusively by the SAN C2.0 Manager. Any node information which is kept on disk will require extra space. 2.2.2 Monitors Both colour and grey scale monitors are supported.
C33543002SE_01
2-3
2.2.3
NDIS driver version information A Network Driver Interface Specification (NDIS) driver is supplied with all Ethernet network cards, to enable Windows applications to communicate on the network. See Table 2-2 for details of the version used.
2.2.4
Other sources of information For more details about the computer, consult the manuals that are supplied with it.
2.3
Copyright notice
The copyright to the SAN C2.0 Manager software is owned by Marconi Communications. All rights reserved. Unauthorized use, copying and modification of this software is prohibited.
D D
The program may be used only on the number of computers for which it is licensed. The program may be copied for backup and security purposes only.
E COPYRIGHT Marconi Communications 2000 All rights reserved.
2.4
Product Codes
The following product codes are used to define the range of SAN C2.0 Manager products. These codes should always be used when ordering SAN C2.0 Manager products. P31614.0x P31614.11 P31614.12 P31614.13 P31614.14 C33577.23 SAN C2.0 NM software (for identification only) SAN C2.0 NM NT, licence for 1 system SAN C2.0 NM NT, licence for 5 systems SAN C2.0 NM NT, licence for 10 systems SAN C2.0 NM NT, licence for 25 systems SAN C2.0 Manager User s Manual
2-4
C33543002SE_01
Product codes in system release upgrades When upgrading from an earlier version of the SAN Manager, the following product codes are used. These codes should always be used when ordering SAN Manager upgrades. P31614.51 P31614.52 P31614.53 P31614.54 C33577.23 SAN C1.5 to C2.0 NM upgrade, licence for 1 system SAN C1.5 to C2.0 NM upgrade, licence for 5 systems SAN C1.5 to C2.0 NM upgrade, licence for 10 systems SAN C1.5 to C2.0 NM upgrade, licence for 25 systems SAN C2.0 Manager User s Manual
C33543002SE_01
2-5
2-6
C33543002SE_01
Chapter 3 Installing the SAN Manager software

About this chapter This chapter describes how to install the SAN C2.0 Manager software. This chapter assumes that:
D D D
You have the SAN C2.0 Manager installation CDROM (or user created diskettes). You know how to use Windows NT. (For more information, refer to the Microsoft Windows NT online tutorial.) You are an administrator as defined by Windows NT (see the Windows NT glossary in the Windows NT user manual or help file). If you are not an administrator, you will not be able to install the SAN C2.0 Manager. The computer being installed with the SAN C2.0 Manager fulfils the hardware and software requirements, as detailed in Chapter 2.
C33543002SE_01
3-1
3.1
Modifications to your system

This section contains information about all the changes that are made to your system when installing the SAN C2.0 Manager.
3.1.1
Files and directories created The SAN C2.0 Manager installation program creates the following folder structure on your computer:
C: NOKIAMGR ...other node managers SYSTEM DATABASE SYSTEM32 INF SANM2.0 DATA
Figure 3-1
Installation folder layout
NOKIAMGR This is the folder in which all Node Managers are installed so that they can share common files and directories. The default name and location for this folder is C:\NOKIAMGR. You can change the default but you should make sure that all subsequent releases of this SAN C2.0 Manager and any other Node Manager products are also installed in this new folder. SYSTEM This is the folder in which files and directories common to all Node Managers are installed. The name of this folder should never be changed.
3-2
C33543002SE_01
DATABASE This folder contains the database of all areas and nodes (other than those on the local LAN). SYSTEM32 The same as SYSTEM (see above) but for 32bit components. INF This is the folder in which all Node Manager information files are installed. The name of this folder should never be changed. SANM2.0 This is the folder which contains all files specific to the version of the SAN C2.0 Manager you are installing. The default folder name is derived from the product and the version number of the SAN C2.0 Manager you are installing. DATA This folder contains all the data which you create using the SAN C2.0 Manager, such as saved configuration details. 3.1.2 Group windows created (NT 3.51) The SAN C2.0 Manager installation program creates an applications group window in the Program Manager which contains the SAN C2.0 Manager application. If you have installed any other Nokia or Marconi applications on your computer, this group window will have already been created. In this case, the SAN C2.0 Manager application will be added to this group window. 3.1.3 Folders created (NT 4) The SAN C2.0 Manager installation program creates the Programs folder that contains the SAN C2.0 Manager application. If you have installed any other Nokia or Marconi applications on your computer, this group window will have already been created. In this case, the SAN C2.0 Manager application will be added to this group window.
C33543002SE_01
3-3
3.1.4
Files changed ODBC registry settings are amended to add an entry for [DBS] if one is not already present. The ODBC files will be added to the WINNT\SYSTEM32 folder. The SAN C2.0 Manager installation program changes the Registry (part of Microsoft Windows NT; use regedt32 to view it). The Registration sections entry for HKEY_LOCAL_MACHINE\CurrentCon trolSet\Services has the following items: S S NokiaTP4 StackMac
3.2
Installation procedure
If you have any problems during the installation procedure described in this section, refer to Section 3.7 which contains information on some of the more common problems that can be encountered. " To install the SAN C2.0 Manager: 1. Switch ON your computer. 2. If it has not already started, start Windows NT, by logging on to NT as described in your Windows User Guide. (You must log into NT with administrator privileges to install the SAN C2.0 Manager.) If you are unsure which login names have administrator privileges on your computer, log in as an administrator and click on User Manager in the Administrative Tools group to display the users. Doubleclick on Administrators to list those users who have administrator privileges. You can use a different login name to run SAN C2.0 Manager than you used when you installed SAN C2.0 Manager. 3. Insert the SAN C2.0 Manager installation CDROM (or user created diskettes). 4. In Windows NT3.51, open the Program Manager. In Windows NT4, click on the Start button at the bottom left of your screen. 5. In Windows NT3.51, select FileRun from the application window. (This will bring up the Run dialog box.) In Windows NT4, select Run... from the Start menu (This will bring up the Run dialog box.).
3-4
C33543002SE_01
6. If you are installing from CDROM run setup.exe from D:\SANM_SW\disk1\setup.exe assuming D is the CDROM drive letter. If you are installing from floppy disks, in Windows NT3.51 enter a:\setup.exe in the Command Line field and click on OK, and in Windows NT4 enter a:\setup.exe in the Open field and click on OK. 7. The SAN C2.0 Manager installation setup program will be initialized and then the SAN C2.0 Manager installation program will start up, indicated by a dialog box. 8. The Choose Destination Location dialog box appears with a default folder name. (For more information on the Marconi SAN C2.0 Manager main folder refer to Section 3.1.1.) Enter a new folder name or leave the default folder name, and click on OK. (The default location is recommended.) Caution The folder name must not contain a blank space. The setup program will not install SAN C2.0 Manager into a folder whose name contains a blank space.
9. You are now asked whether you want to add icons to the program folder and whether you want to add short-cuts. Make your selection and click on OK. 10. The dialog box shown in Figure 3-2 will be displayed to ask you whether you want security to be enabled (see Chapter 15). Select either Disable Security or Enable Security, and then click on Next>.
C33543002SE_01
3-5
Figure 3-2
Enable Security dialog box
11. The installation program will then begin the installation. A dialog box will be displayed indicating the progress that is being made reading the CDROM (or user created diskettes). 12. If you are installing using the user created diskettes, as the installation progresses, you will be prompted to insert all the remaining installation diskettes. Remove the previous installation diskette, insert the requested installation diskette and click on OK Note The system may not ask you for all the diskette that you were sent. Do not be concerned about this, because the other diskettes contain files that you do not need for your particular setup.
13. A prompt will be displayed offering you the option to install the following: S S Network Downloader software Timeout/Retry settings
14. A prompt will be displayed to remind you to install the Q3 stack. You can find these instructions in the text file C:\NOKIAMGR\SYSTEM32\INF\STACK32.TEXT.
3-6
C33543002SE_01
Note
You do not need to carry out Step 14. if an earlier type of Nokia Node Manager using Q3 has been previously installed on your PC.
15. Reboot your PC. 16. The TP4 NSAP Configuration dialog is displayed (Figure 3-3). (TP4 NSAP refers to the four lower layers in the communications protocol.) If you want the PC to have the same address as it did before you installed this version of SAN C2.0 Manager, click on Restore Previous Address. (The Restore Previous Address button will not be displayed if this is the first time you have installed a SYNFONET Node Manager.) All the empty address fields will be filled in automatically. If you want to give the PC a different address, enter new details in the IDI and Area Address fields (for an explanation of these fields, see Appendix C). When the address details are correct, click on Apply.
Figure 3-3
NSAP Address Dialog
C33543002SE_01
3-7
A warning dialog will be displayed reminding you that there must not be any applications currently running that use the stack. 17. When you look in the Program Manager (for Windows 3.51) or the Start menu (under Windows NT 4.0) you will notice that a new applications group will have been created, containing the SAN C2.0 Manager application and the Configure PC Address application.
3.3
Changing the stack startup

The communications stack will be installed so that it starts whenever NT is booted up. If you want to change the stack settings, run the STACKCFG.EXE application. To change the settings or manually start or stop the stack, you must have administrator privileges.
Figure 3-4
Stack configuration dialog
Select how the stack will be started by clicking on one of the radio buttons in the Startup Type group and then click on Apply. If you wish to start or stop the stack manually click either the Start Stack or Stop Stack buttons. The configuration utility also allows you to view other NSAPs which have been located on the Local LAN. These NSAPS will include the
3-8
C33543002SE_01
addresses of the SAN C2.0 Manager and other management systems, as well as nodes. Click on Refresh or check Auto Refresh to update the NSAPs list. Select an item in the list to view its Ethernet Address. Click on Close to end the dialog after you have made any changes. If you have selected Start when requested, the SAN C2.0 Manager users must have administrator privileges.
3.4
Changing the NSAP address after installation

Run the PCQ3.EXE application to change the NSAP address. You must not be running any applications that use the Q3 stack while you are changing the NSAP address.
Figure 3-5
NSAP Address Dialog (Existing Address)
After you have edited the address click on Apply to save the changes. A warning dialog will be displayed reminding you that there must not be any applications currently running that use the stack.
C33543002SE_01
3-9
Click on OK to accept the changes or click on Cancel if you want to exit without changing the NSAP address.
3.5
Enabling security
You can enable security to control which users can make changes to the node. Other users will be given warning messages when they connect to a node and also if they try to send data to the node (see Chapter 4). " To enable security: When the setup program asks you whether you want security enabled (Figure 3-6), select Enable Security. (For instructions on how to use the security feature when you have installed the SAN C2.0 Manager, see Chapter 15.)
Figure 3-6
Security enable/disable prompt
Click on Next>.
3-10
C33543002SE_01
3.6
Installing related products

There are several other Marconi network products that you can use with your network. Refer to the manual supplied with that product for installation and operating details. A brief description of these products is given in Appendix D.
3.7
Troubleshooting
This section contains information on some of the more common problems which you may encounter during the installation procedure.
3.7.1
Insufficient disk space If you do not have enough free disk space on your PC, it will not be possible to install SAN C2.0 Manager. Consult your system administrator for advice.
3.7.2
Q3 stack not running Use the STACKCFG tool to ensure that the stack is started when NT is rebooted.
3.7.3
SANM does not start If the installation was successful, but you cannot start SAN C2.0 Manager, ensure that the Q3 stack is running, using STACKCFG.
3.7.4
Cannot connect to node If the installation was successful, but you cannot connect to a node:
D D D
Ensure that the node is connected to the Ethernet port. The node is switched on and operational, and that the Ethernet is installed correctly. Ensure that you have defined a valid NSAP address for the PC. Note that the PC must have the same address as the node to which you want to connect.
C33543002SE_01
3-11
3.7.5
Backedup databases When new Marconi applications are installed, they may change the database format. Existing databases in SYSTEM\DATABASE are automatically modified to be compatible with the new format. Existing database backups on other directories will not be updated. When you install a new product, take new backups of your database files.
3.7.6
Insufficient memory If you have less than 24 MB of RAM, SAN C2.0 Manager may function more slowly or not at all. If you have 24 MB, but are running several programs at the same time you will also experience performance problems. Add more memory or run SAN C2.0 Manager on its own.
3.7.7
Low virtual memory If you get a message indicating that the virtual memory is insufficient on your PC, it will not be possible to install SAN C2.0 Manager. Consult your system administrator for advice.
3.7.8
Installing a LAN card A LAN card and supporting software is required. Consult the installation instructions that came with your card for details on how to install and configure it.
3.7.9
Installing an older version of the software If the version number of new files that are installed is older than the version of files they are replacing, then a dialog box will be displayed indicating that a newer version of the software has been found. Click on Yes, if you wish to continue with the installation. Click on No, if you wish to stop the installation program. (Choosing this option will mean that only a partial installation has taken place.) Select Exit to exit completely from the installation program. You can also remove your old program files from the NOKIAMGR directories by using Delete from Windows NT Explorer.
3-12
C33543002SE_01
3.7.10 No nodes found If, after installation, there are no nodes displayed in the Select Node dialog, the Q3 stack may not have been installed. Refer to the instructions on installing the Q3 driver and setting the NSAP address (Section 3.2). Also check the Ethernet connection.
C33543002SE_01
3-13
3-14
C33543002SE_01
Chapter 4 Getting started

About this chapter This chapter describes the design and basic operation of the SAN C2.0 Manager, and how it can be used to manage a SYNFONET Access Node.
4.1
About the Node Manager

The SAN C2.0 Manager is a fully compliant Microsoft Windows NT application. When the SAN C2.0 Manager is managing a node it can request various data from the node about its current state. For example, the SAN C2.0 Manager can request the node to display a list of current alarms on that node or a list of its cross connections. The SAN C2.0 Manager allows you to carry out the following tasks.
D
You can update the data received from the node whenever you want to, and you can arrange for some types of data to be updated automatically on a regular basis (see Section 4.4.2). You can edit the data and send the new details back to the node to update its configuration (see Section 4.4.3). You can see how an operation is progressing (see Section 4.4.4). You can abort some operations (see Section 4.4.6). You can save all or selected parts of the configuration data to a file and load it back from the file (see Section 4.4.9).
D D D D
C33543002SE_01
4-1
D D
You can print out data (see Section 4.4.10). You can access an online help system (see Section 4.4.11).
4.2
Node Manager Overview

The SAN C2.0 Manager provides an easytouse graphical user interface running under Microsoft Windows NT. The interface consists of a series of windows, menus and dialog boxes to enable you to perform all management operations on the node easily and efficiently. At any time in a typical node management session, your screen shows the SAN C2.0 Manager application window. Windows which are displayed within the Application window are called document windows. A special document window called the Node Subrack window is permanently present in the application window (either as a window or iconised) when the SAN C2.0 Manager is managing a node. The Node Subrack window provides a graphical representation of the node that is currently being managed. It enables you to select specific node units which you can configure using the SAN C2.0 Manager. In addition, the SAN C2.0 Manager also opens dialog boxes, to request information from you and to provide you with information about the node.
4.2.1
The application window The application window is the main window that first appears when you start the SAN C2.0 Manager. Using this window, you can reach any other window in the SAN C2.0 Manager. In particular, the application window allows you to:
D D D
Connect to and disconnect from a SYNFONET Access Node node Configure and manage a SYNFONET Access Node node Exit from the SAN C2.0 Manager
Figure 4-1 shows the application window.
4-2
C33543002SE_01
Figure 4-1
Application window
Components of the application window Title bar The Title bar at the top of window shows the name of the application (SAN C2.0 Manager) and the name of the node being managed. Toolbar Below the Title bar is the toolbar containing the commands available for using the SAN C2.0 Manager. The menus provided on the toolbar stay the same at all times when the SAN C2.0 Manager is connected to a node. When the SAN C2.0 Manager is not connected to a node (see Figure 4-2), you cannot use the Data, Monitor, Configure, and Window menus.
C33543002SE_01
4-3
Figure 4-2
Application window not connected to a node
The items displayed for each menu remain the same at all times. However, they will either be enabled or disabled (greyed out) depending on the operation being performed on the node. The commands also have additional characters added to them to indicate which action they perform when they are selected:
D
commands with three dots (an ellipsis) after them produce a dialog box (for example, Node Unit Information...).
Figure 4-3
Command producing a dialog box
4-4
C33543002SE_01
Commands with no characters after them execute the command or action immediately (for example, Data Refresh from Node).
Figure 4-4
Command indicating a direct command or action
Toolbar Below the Menu bar is the Toolbar which is used to provide mouse shortcuts for commonlyused commands. Some icons may be greyed out, depending on whether the SAN C2.0 Manager is connected to or not connected to a node, and whether the associated command is currently available; for example, the performance icons are available only when a block on an interface that supports performance data reporting is currently available. Table 4-1 defines the associated command for the icons displayed on the Toolbar. The icons shown in the Toolbar are always displayed while a node is being managed. The icons will be greyedout when the icons equivalent command on the toolbar is greyedout. The display of the Toolbar in the application window can be toggled on and off. To enable or disable the display of the Toolbar, select Node Manager Options... and check the Toolbar check box in the View tabbed window of the Node Manager Options dialog box (see Section 6.5.1). A tick alongside the name indicates whether it is currently being displayed. Selecting the command turns the display on or off.
C33543002SE_01
4-5
Icon
Associated command
NodeManage... NodeStop Managing DataSend to Node DataRefresh from Node MonitorCurrent Alarms Monitor Event History Log MonitorCurrent Performance MonitorBlock Status MonitorPerformance History ConfigureSynchronisation ConfigureCross Connect ConfigureMan. and Aux. Channels WindowCascade HelpContents
Table 4-1
Toolbar icons and their associated commands
Application window workspace Below the Toolbar is the application window workspace. It is an area of the application window which contains all document windows created by the SAN C2.0 Manager, including the Node Subrack window.
4-6
C33543002SE_01
Status bar At the bottom of the window is the Status bar which consists of three parts: the Handy Hints area, the Security Level area, and the Alarm Status area. The Handy Hints area is on the left-hand side of the Status bar. It displays Help information about menu commands chosen from the toolbar and icons from the Toolbar. It also displays status messages and warning messages about the currently selected action. If security is enabled, the Security Level area displays your current user access level (see Chapter 15), as in the example shown in Figure 4-5.
Figure 4-5
User access level shown in Security Level area
The Alarm Status area is on the right-hand side of the Status bar. It displays a descriptive text message about the most severe alarm for the node which is currently being managed. This field will be empty when no node is being managed. The message is displayed on a coloured background (grey scale for monochrome monitors) which indicates the severity of the alarm. For more information about alarms, please see Chapter 14.
D D
The meaning of the colours or scale of grey is explained in Table 14-6. The definitions of the alarm severities are given in Table 14-5.
The display of the Status bar in the application window can be toggled on and off from the Node Manager Options window (see Section 6.5). A tick alongside the name indicates that it is currently being displayed. 4.2.2 The Node Subrack window A graphical representation of the subrack is always displayed in a window in the application window workspace while a node is being managed by the SAN C2.0 Manager. This window is known as the Node Subrack window. A typical Node Subrack window is shown in Figure 4-6.
C33543002SE_01
4-7
Figure 4-6
Node Subrack Window
The Node Subrack window has many uses:

D D D D D D D
It identifies the type of node the SAN C2.0 Manager is connected to. It provides information about the type of units present in the node. It provides information on where the units are in the subrack. It provides information on the units which should be present and what units are actually present for the current node type. It provides information about the most severe current alarms on each unit. It is used to install new units in the subrack. (For more information on installing units, refer to Chapter 5.) It is used to select units for subsequent node management operations. (For more information on selecting units, refer to Section 4.4.)
The Node Subrack window is automatically displayed when you connect to a node using the SAN C2.0 Manager. Components of the Node Subrack window Header Area The Header Area displays the following general information about the rack:
D D
The Name defined for the node. The node Type.
4-8
C33543002SE_01
D D D D D
The System ID of the node. The Location defined for the node. The current Release of software being used by the node. The Node Time displays the realtime node clock. The elapsing time is emulated by the SAN C2.0 Manager and should not be assumed to indicate the actual time at the node. The Synchronisation Source which is currently in use.
Alarm and Slot Number Area The Alarm and Slot number area shows:
D D
The slot numbers in the subrack. This is indicated by the numbers in the squares above the unit areas. The SAN C2.0 Manager uses subracks with 2, 4, or 8 slots. The most severe current alarm associated with each slot number. This is indicated by the background colour of the square (grey scale for monochrome monitors). The meaning of the colours or scale of grey is explained in Table 14-6. The definitions of the alarm severities are given in Table 14-5.
Unit Area The unit area shows the type and location of the units which are present in the subrack (see the example in Figure 4-7).
Figure 4-7
Unit area
For more information on how to configure the node so that the Node Subrack window shows the correct units, refer to Chapter 5.
C33543002SE_01
4-9
4.2.3
Tooltips Tooltips identify an item on the screen which has no text label. A tooltip on the toolbar (see Figure 4-8) identifies a button.
Figure 4-8
Tooltip on the toolbar
A tooltip on the alarm status area identifies the most severe current alarm in the subrack (see Figure 4-9).
Figure 4-9
Tooltip on the alarm status area
A tooltip in a document window(see Figure 4-10) identifies the most severe current alarm in that block within the window.
Figure 4-10
Tooltip in a document window
4-10
C33543002SE_01
4.2.4
Using the left and right mouse buttons When you are using the mouse, the left and right buttons have different functions. (You can also control the SAN C2.0 Manager by using the keyboard. See Section 4.2.5.) Left mouse button The left mouse button is used to select a particular object from a window. For example, in Figure 4-11, the left mouse button has been clicked with the cursor on the CORE2M unit and its attached STM1 primary interface module, which are now selected. To show you that this pair of units is selected, they appear to protrude from the subrack. Where units exist only in pairs (a CORE or CORE2M with a Primary Interface Module (PIM) attached, the unit which is currently selected by the cursor has a narrow pattern of dots around the border of the grey area (light grey for monochrome screens). The purpose of this border is so that when you want to configure an individual unit within the pair, you can tell which one is currently selected.
Figure 4-11
Effect of clicking with left mouse button
Right mouse button The right mouse button is used to invoke a popup menu which contains a list of options which are available to you in the slot or block on which the cursor is positioned. (Some of the options may be greyed out because they are not available.) In Figure 4-12, the right mouse button
C33543002SE_01
4-11
has been clicked with the cursor on the STM-1 Primary Interface Module. A popup menu is displayed with a list of options. You can select any of the options by placing the cursor on it and clicking once with either mouse button. If you do not have a mouse, select the unit with the arrow keys, and then use SHIFT + F10 which carries out the function of the right mouse button. Alternatively, select the function which you want by using the menu bar.
Figure 4-12
Effect of clicking with right mouse button
4.2.5
Using the keyboard A list of keyboard commands for controlling the Node Manager is given in Table 4-2 and Table 4-3. You can see the same list on the screen by selecting HelpKeyboard. Keyboard shortcuts are also displayed in pulldown menus, as in Figure 4-13. You can also use the ALT key to access the commands on the Toolbar. For instance, ALT+D opens the Data menu.
4-12
C33543002SE_01
Figure 4-13
Keyboard shortcuts displayed in a pulldown menu
You can also control the Node Manager by using the mouse. See Section 4.2.4.
C33543002SE_01
4-13
Press... Ctrl+M Ctrl+T Ctrl+Shift+R Ctrl+Shift+I Ctrl+Shift+U Ctrl+O Ctrl+Z Ctrl+S Ctrl+R Ctrl+F Ctrl+Shift+F Ctrl+P Ctrl + V Ctrl+E Ctrl+A Ctrl+L Ctrl+B Ctrl+Shift+P Ctrl+Shift+H Ctrl+Y Ctrl+Shift+X Ctrl+I Ctrl+X
To... Select a node to manage Stop managing a node Reconnect to a node Reinstall a node Display unit information Display manager options Undo the last action Send the data in the window to the node
Equivalent command NodeManage NodeStop Managing NodeReconnect NodeReinstall NodeUnitInformation NodeManager Options DataUndo DataSend to Node
Refresh the data from the DataRefresh from Node node Save data to file Load data from file Print the currently active window DataSave to File DataLoad from File DataPrint
Save data in the currently- DataSave As... selected window as text Display External Alarms Display Current Alarms Display the Event History Log Display the Block Status Display the Current Performance Display the Performance History MonitorExternal Alarms MonitorCurrent Alarms Monitor Event History Log MonitorBlock Status MonitorCurrent Performance MonitorPerformance History
Configure synchronisation ConfigureSynchronisation Configure Management and Auxiliary Channels Configure a unit interface Configure cross connections ConfigureMan. and Aux. Channels ConfigureInterface ConfigureCross Connections
Table 4-2
Keyboard shortcuts (continued on next page)
4-14
C33543002SE_01
Press... Ctrl+U Ctrl+N Ctrl+Alt+Shift +P Shift+F5 Shift+F10 F1
To... Configure unit type Configure node settings Configure unit protection Cascade the windows
Equivalent command ConfigureUnit Type ConfigureNode Settings ConfigureUnit Protection WindowCascade
Invoke a popup menu for Same function as clicking the selected item the right mouse button Display online help (will HelpContents
display contextsensitive help if available)
Table 4-3
Keyboard shortcuts (continued from previous page)
4.3
Starting the Node Manager

This Section explains how to start SAN C2.0 Manager. " To start the SAN C2.0 Manager: 1. Switch ON your computer. The SAN C2.0 Manager must be installed on your computer. The computer must be physically connected to a SYNFONET node via an Ethernet cable connected from the Ethernet port on the computer to the CORE2M unit in the subrack. 2. Doubleclick on the SAN C2.0 Manager Programitem icon on the desktop (Figure 4-14):
Figure 4-14
The SAN C2.0 Manager programitem icon
The SAN C2.0 Manager will start up and display the Manage Node window (Figure 4-15):
C33543002SE_01
4-15
Figure 4-15
Manage Node window
Refer to Chapter 6 for information on how to continue from this point and connect to a node.
4.4
4.4.1
Operating the Node Manager

Operation methodology To use the SAN C2.0 Manager, you use one of two methods. Select a slot and then select an action To select a slot in the subrack window, either:
D D
Click on the slot, or Use the left and right cursor keys. The selected slot will appear to protrude from the subrack. Press the Spacebar when the correct slot is selected.
For example, if you want to configure a CORE2M unit in a node, select the slot containing the CORE2M unit you want to configure, and then select Configure Interface from the Menu bar. This displays the Configure CORE2M Interface window.
4-16
C33543002SE_01
In another example, if you want to add a 2M unit to a node, select the slot where you want to add the unit, and then select Configure Unit Type... from the Menu bar. This displays the Unit Type dialog box enabling you to install the unit. Other options are always available from the Menu bar, irrespective of the selection status of the node. For example, the Current Alarms window can always be displayed while a node is being managed. Select an action To select an action, first select a command from the Menu bar. For example, to configure the cross connections, select Configure from the Menu bar, and then select Cross Connections from the Configure menu. Selecting the default window for a slot Doubleclicking on any of the units present in the node opens the most appropriate (default) window for the unit. For example, if you doubleclick on a 2M unit, the SAN C2.0 Manager assumes that you want to configure the interfaces on the 2M unit and so displays the Configure 2M window. If you doubleclick on an empty slot, the SAN C2.0 Manager assumes that you want to install a unit in the empty slot and so displays the Unit Type dialog box. 4.4.2 Receiving data from the node Manually Most windows can be manually updated by choosing the command DataRefresh from Node. This command updates the data being displayed in the currently active window. The data is requested from the node and the window is updated with the new data received from the node. The DataRefresh from Node command is especially useful if you have edited a window (but have not yet sent the changes to the node) and want to return to the original configuration or setting which is currently present on the node. You could also use DataUndo.
C33543002SE_01
4-17
Dynamically Block alarms, external alarms, current performance, synchronisation status, and laser power measurements are regularly updated when Auto Refresh is selected for a window. The default setting for Auto Refresh is set by selecting NodeManager Options... (See Section 6.5.2.) The SAN C2.0 Manager displays data about the current alarms present on the currently managed node in the following areas:
D D D D D D D D
Current Alarms window Block Status 2M and STM1 configuration windows Synchronisation configuration windows Node Subrack window Alarm Status area of the Status bar Protection Alarms in the Cross Connection window External Alarms window.
When a new alarm occurs which changes any of the current alarm information shown in these windows, they are dynamically updated. When the Current Alarms window is open, it displays any new alarms occurring on the node. (See Section 14.2.5.) When any type of 2M, STM1, Cross Connection, or Synchronisation configuration window is open, any new alarms will be displayed in the appropriate areas of the window. (See Section 14.2.3.) When the node subrack window is open, it displays the most severe current alarm associated with each unit present in the subrack. Any new alarm occurring on a unit which is higher in severity than the current alarm shown will be dynamically updated. (See Section 14.2.2.) When a new alarm occurs which is higher in severity than any alarm being shown, the Alarm Status area is updated. (See Section 14.2.1.) 4.4.3 Making changes to the node If the manager s security system has been enabled, you can make changes to the node only if your system administrator has granted you a high enough user access level to allow you to make the edit which you are attempting (see Chapter 15). When you edit data obtained from the node, the changes which you can see on your screen are not immediately applied to the node. To put the
4-18
C33543002SE_01
changes into effect, you must send the edited data to the node, using the command DataSend to Node. This command updates the node with the changed data currently being displayed in the active window. 4.4.4 Indicating progress of an operation The SAN C2.0 Manager will provide as much information as possible whenever it is busy, that is:
D D
When a window or dialog box is sending data to the node or receiving data from the node When the SAN C2.0 Manager is connecting to or disconnecting from the node.
The information provided consists of a set of progress indicators which completely cover the contents of the window involved in the operation. While the progress indicators are being displayed, you cannot edit the window in which they appear. However, you are free to edit other windows. When the operation has finished, the progress indicators are removed from the window or dialog box and the contents of the window or dialog box are displayed again. An example of a window containing progress indicators while connecting to a node is shown in Figure 4-16.
C33543002SE_01
4-19
Figure 4-16
Typical progress indicators in a window
The progress indicators that are used and their meaning are listed in the following Sections. Whirly wheel The whirly wheel is used to indicate that the SAN C2.0 Manager and Windows are still running.
Figure 4-17 Note
Whirly wheel The whirly wheel does not indicate that the action which you are trying to perform is actually being carried out successfully by the Node Manager. This is shown by the progress indicator.
The whirly wheel is always displayed for any operation.
4-20
C33543002SE_01
If the whirly wheel stops rotating briefly, then it is likely to be caused by another application running on the computer consuming all the processing power of the computer. Progress bar The Progress bar is used to indicate how much of the data has been sent to or received from the node, expressed as a percentage of the total amount of data being sent or received.
Figure 4-18
Progress bar
Progress counter The Progress counter is used to indicate how much of the data has been sent to or received from the node, expressed as a steadily incrementing stream of numbers. The progress counter is used in situations where the total amount of data to be sent or received cannot be foreseen, and so progress cannot be shown as a percentage of the total because the total is unknown.
C33543002SE_01
4-21
Figure 4-19
Progress counter
If the whirly wheel is rotating but the progress indicators stop If the progress bar or the progress indicator stops incrementing, but the whirly wheel is still rotating, then there is a delay in the data transmission between the node and the computer. If the whirly wheel is rotating but there is no progress indicator If the whirly wheel is rotating in a window, but the progress bar or progress counter does not appear within a reasonable time (that is, the box above the whirly wheel remains empty), then the action which you were trying to perform may have failed. (If you are trying to carry out a lengthy operation such as loading the configuration window for a 2M unit, it will always be a long time before the numbers begin to appear in the box.) If you believe that the action which you were trying to perform has failed, press CTRL+ALT+DEL and follow the instructions displayed. If all progress indicators stop incrementing If the progress bar or the progress counter stops incrementing, and the whirly wheel stops rotating, then either the SAN C2.0 Manager has stopped responding or Windows itself has stopped responding. To recover from this situation, press CTRL+ALT+DEL and follow the instructions displayed. 4.4.5 Failing to send or refresh data If a send or refresh from the node is not successful, then the SAN C2.0 Manager will display a dialog box telling you of the failure and asking you if you want to try the operation again.
4-22
C33543002SE_01
For example, Figure 4-20 shows the dialog box that is displayed if the SAN C2.0 Manager fails to send the contents of the Configure 345M (slot 3) window to the node:
Figure 4-20
Failed to send data warning message dialog box
Click on Yes if you want to try to send the data to the node again. Click on No if you want to cancel the send. 4.4.6 Aborting an operation Some operations can be aborted before they finish, by clicking on the Abort button. Clicking on the Abort button will cause the operation to stop communicating with the node. The progress indicators will be removed and the window will be displayed again. 4.4.7 Communications failure behaviour When a communications failure occurs between the node and the computer, the DataSend to Node and DataRefresh from Node commands, and all the other commands which depend on access to the node, will be disabled until communication with the node is re-established. If a communications failure occurs while you are communicating with the node (for example, sending information to a node, or reading information from a node), the operation will be terminated. Once the node has established connection again, you can then repeat the operation. 4.4.8 Reconnecting to a node If the connection between the computer and the node fails for some reason, the SAN C2.0 Manager will automatically make one attempt to
C33543002SE_01
4-23
reconnect to the node. If this attempt fails, the message shown in Figure 4-21 will be displayed.
Figure 4-21
Reconnection message
The system will keep trying to reconnect to the node unless you click on Stop trying. 4.4.9 Saving node configuration data When you want to save node configuration data, the commands Data Save to File and Data Load From File enable you to save the information to a file and load it from the file in which it was saved. The instructions for saving and loading node configuration data are in Chapter 13. 4.4.10 Printing data When you want to obtain a printed copy of the data contained in a window, you can send the data to a printer. The command Data Print enables you to send the data contained in the window to the currently selected printer. For more information on printing node data, refer to Chapter 17. 4.4.11 Using online help The SAN C2.0 Manager contains an Online Help system which provides you with Help information about how to use all aspects of the SAN C2.0 Manager. Help information is available at any time when you are using the SAN C2.0 Manager.
4-24
C33543002SE_01
The Help system can be accessed in two main ways, when you are using the SAN C2.0 Manager:
D D
By choosing a command from the Help menu on the Menu bar By pressing F1
Both these methods of accessing the Help system are described in the next two Sections. For more information on using the Help system, refer to the Microsoft Windows User s Guide. Accessing help from the menu bar To view all the Help information available about the SAN C2.0 Manager, choose Help Contents. This will display a window containing a list of all the Help topics covered in the Help system. If you are stuck and unsure what to do next, click on the first item in the Contents list, Got a Problem? Click Here! which is easy to find because it is in red. You will then see a list of common problems. If the problem which you have encountered is listed there, click on it. You will then be shown an explanation and told what to do. Index and Find functions If the Contents list does not show you where to go in the Help system for the information which you need, click on Index for a list of topics or on Find for a list of keywords (for example, if you do not understand what the whirly wheel is doing, doubleclick on whirly wheel for a list of topics which deal with the whirly wheel, and then doubleclick on the appropriate topic). The other commands on the Help menu provide you with shortcuts for accessing specific topics of the Help system, rather than starting first at the Contents window:
Help Search...
Opens the Help Search dialog box enabling you to search for specific information about a topic. Help Keyboard Displays the Help window showing all the keyboard shortcuts that are available for using the SAN C2.0 Manager.
C33543002SE_01
4-25
Help Symbols Displays the Help window showing all the symbols (window icons, speedbar icons etc.) that are used in the SAN C2.0 Manager. Help About... Displays the About SAN C2.0 Manager dialog box containing copyright information for the SAN C2.0 Manager. Accessing contextsensitive help To view Help information which is specific to the currently active window, press F1. This will display the Help window which is most appropriate for the currently active window. For example, if the Real Time Clock window is the currently active window and you press F1, the Help window displayed will contain information about how to set the real time clock on the node. If there is no Help screen which is specific to the currently active window, pressing F1 will display the Contents window (see above).
4-26
C33543002SE_01
4.5
4.5.1
Stopping the Node Manager

Closing the connection to a node To stop managing the node, but without closing the SAN C2.0 Manager, select Node Stop Managing to end the management session. (For instructions on how to stop managing the node and exit from the SAN C2.0 Manager in one operation, see Section 4.5.3.) The SAN C2.0 Manager will now check if there are any unsent edits contained in any document windows. If there are, a warning message dialog box will be displayed telling you about the unsent edits (Figure 4-24). Click on OK and carry out the procedure for closing a document window (see the instructions in Section 4.5.2). Once this is complete, select Node Stop Managing again. When there are no document windows with unsent edits, the dialog box shown in Figure 4-22 will be displayed.
Figure 4-22
Confirm exit dialog box
Click on Yes. The connection to the node will be closed within a few seconds. 4.5.2 Closing document windows When you choose to close down or refresh windows containing edited data which has not yet been sent to the node, the SAN C2.0 Manager will always check first if you want to continue with the close or refresh, because you would lose the edits which you had made. For example, Figure 4-23 shows the dialog box which is displayed if you attempt to close down a Configure STM1 (Slot 1) window which has been edited.
C33543002SE_01
4-27
Figure 4-23
Unsent edits warning message dialog box
If you click on No, the operation you have selected will be abandoned. If you choose Yes, the operation you have selected will continue and you will lose the changes you have made to the window. 4.5.3 Closing the SAN Node Manager Caution It is important that you follow the procedure outlined below for closing down the SAN C2.0 Manager. If you do not close down the SAN C2.0 Manager using this procedure, data may be corrupted.
To completely close down the SAN C2.0 Manager: 1. Select Node Stop Managing. If the SAN C2.0 Manager is managing a node when you try to close the manager, it will check if there are any document windows containing unsent edits. If there are, you will be asked if you want to continue with the operation or cancel the operation, as shown in Figure 4-24. You must then close the window which contains the unsent edits, as described in Section 4.5.2, before you repeat the request to stop managing the node. If there are no unsent edits, the dialog box shown in Figure 4-22 will be displayed.
Figure 4-24
Edited windows warning message dialog box
4-28
C33543002SE_01
2. Close down the SAN C2.0 Manager by one of the two following methods: S S Choose Node Exit, or Click on the Close button the application window). (in the top righthand corner of
3. If you want to stop managing the node, click on Yes. The SAN C2.0 Manager itself will then close down. This may take a few seconds to complete.
C33543002SE_01
4-29
4-30
C33543002SE_01
Chapter 5 Installing nodes

About this chapter This chapter contains information on how to install a node using the SAN C2.0 Manager. Installing a node means either setting up a completely new node or reconfiguring a node from one type of node to another type of node, by adding or removing units. The procedure for either operation is basically the same.
5.1
Introduction
Installation of a node means setting up a completely new node so that it can be used on a network for data transmission. Installation of a node is performed with five procedures:
D D D D D
Installing a new node (Section 5.2) Reinstalling a node (Section 5.3) Configuring the node settings (Section 5.4) Installing units in the node (Section 5.5) Initialising a node (often referred to as resetting or blasting the node), (Section 5.6).
If you are installing a completely new node, proceed to Section 5.2. If you are reinstalling a node, turn to Section 5.3. If you have already installed the node and just want to change the units in a node, proceed directly to Section 5.5.
C33543002SE_01
5-1
5.2
Installing a new node

If security is enabled, you must hold at least user access level 4 (NMS/10 Network Administrator) (see Chapter 15) to be able to install a new node. " To install a node, follow the procedure below: 1. Ensure that the node is not connected to any network other than a direct Ethernet link to the PC. 2. Power up the node. 3. Start up the SAN C2.0 Manager as described in Section 4.3. 4. The Manage Node dialog box will be displayed (Figure 5-1).
Figure 5-1
Manage Node dialog box
5. Select the LocalLAN area from the dropdown list box in the Area group box. 6. Select the only node listed in the Node List group box that is labelled DEADDEADF5B0. This is the node that you are connected to.
5-2
C33543002SE_01
Note
If the Node List group box is blank, and you are sure there is a node connected to the SAN C2.0 Manager, click on Refresh. Communication over the local LAN may delay the recognition of nodes on the network. Try clicking on Refresh again, because it can take up to 30 seconds for all the nodes on the local LAN to be recognised. This may result in all of the nodes being listed.
7. Click on Manage. The SAN C2.0 Manager will attempt to connect to the chosen node. If the connection is successful, and you are connecting to a previously uninstalled node, the first dialog box of the Install Wizard will be displayed in the workspace of the application window (Figure 5-2). This dialog box is the first step in the Install Wizard feature which guides you through installing a SYNFONET Access Node.
Figure 5-2
Install Wizard first dialog box
C33543002SE_01
5-3
If you want to install the node with a configuration which was previously saved as a file (see Chapter 13), check the Check this box if you want to install from file check box and then click on Next>. The Open window will then be displayed. The system will then use the Edit Whole Node File Configuration Data wizard to install the node. For details, see Chapter 13. If you install the node from file, you will not be returned to the Install Wizard. If you have not chosen to install the node from file (see the previous paragraph) click on Next>. The second dialog box will be displayed (Figure 5-3).
Figure 5-3
Install Wizard second dialog box
The Type: box is readonly. If you want, you can enter a name for the node in the Name: edit field and a location name in the Location: edit field. The Release: field offers you only the SAN C2.0 option in this release of the software. Click on Next>. The third dialog box will be displayed (Figure 5-4).
5-4
C33543002SE_01
Figure 5-4
Install Wizard third dialog box
Select a node type from the Type: dropdown list box. Enter the required information about the subrack (which is printed on the sticker attached to the subrack) in the Variant, Version and Serial No: fields. Caution The information you enter in these fields is not used by the SAN C2.0 Manager. The fields are provided for you to enter supplementary information about the node. If you want, you can leave the fields as they are, but
you cannot change this information later without completely reconfiguring the node.
Click on Next>. The fourth dialog box will be displayed (Figure 5-5).
C33543002SE_01
5-5
Figure 5-5
Install Wizard fourth dialog box
From the Name: dropdown list box, select the name of the area in which you want to install the node. If the name does not appear in the list, click on Search Database... (If this the first time SAN C2.0 Manager has been run, there will be no database available yet.) The Select Area dialog box will be displayed (Figure 5-6). Press Add to add a new area name. (See Chapter 7 for rules on creating area and node names.)
Figure 5-6
Select Area dialog box
5-6
C33543002SE_01
Node Enter the System ID in the System ID: edit field. The AFI:, IDI:, and Area Address: fields are readonly, and so is the NSel: field in the Node group box, but you can change them by using the Search Database... button to select a different address. (See Appendix C for details about address formats.) Click on Next>.
C33543002SE_01
5-7
The fifth dialog box will be displayed. There are three versions, depending on the number of slots in the subrack. There are three types of subrack:
D D D
2slot subrack 4slot subrack 8slot subrack
Figure 5-7
Install Wizard fifth dialog box
Each type of node configuration has a default card set associated with it. To install it, select the node type in the Default units set dropdown list box. If you have already inserted all the units in the node, click on Configure From Node. This will automatically read which units are present in the node and set up this dialog box accordingly. (The Configure From Node button is not available in the Reinstall Wizard.) When you have finished entering the details of the configuration, click on Next>. The sixth dialog box will be displayed (Figure 5-8).
5-8
C33543002SE_01
Figure 5-8
Install Wizard sixth dialog box
In the Set mode radio button group box, you can choose either to have the clock take its time from the PC by selecting Set to PC time, or set the time manually by selecting Manual and entering the date in the Date group box and the time in the Time group box. The new time will take effect after you click on Finish and select Data Send to Node. The configuration details for the new node are now complete.
C33543002SE_01
5-9
The Information window is now displayed (Figure 5-9). Read through it and check that the configuration is as you want it. If the configuration is correct, click on Send. The details of the new node will be sent to the node and it will be installed. If the configuration is not correct, click on <Back to start going through the Install Wizard procedure again.
Figure 5-9
Information window
5.3
Reinstalling a node
The procedure is the same as in Section 5.2, except that you select Node Reinstall... The Reinstall dialog box will be displayed as shown in Figure 5-10.
5-10
C33543002SE_01
Figure 5-10
Reinstall dialog box
This dialog box is the first step in the Reinstall Wizard feature which guides you through reinstalling a SYNFONET Access Node node in the same way as the Install Wizard does for installing a new node (see Section 5.2). Caution Reinstalling the node may lose all the existing configurations, which you will have to enter again.
5.4
Configuring the node settings

" To view or change settings on a node, select ConfigureNode Settings After the system has taken a few moments to get the current settings from the node, the Node Settings dialog box will be displayed. The first window to be displayed is Node, as shown in Figure 5-11. You can move to any of the other windows by clicking on its tab.
C33543002SE_01
5-11
Figure 5-11
Node Settings dialog box, Node window
The Type: field is readonly and shows you the type of the node. To change the name of the node, enter the new name in the Name: field. To change the location of the node, enter the new location name in the
Location: field.
The next window is the Subrack window, as shown in Figure 5-12.
5-12
C33543002SE_01
Figure 5-12
Node Settings dialog box, Subrack window
The Subrack window contains the readonly Subrack Information field which contains the current details for the subrack. You can change these details by using the Reinstall Wizard (see Figure 5-4). The next window is the Q3 Address window, as shown in Figure 5-13.
C33543002SE_01
5-13
Figure 5-13
Node Settings dialog box, Q3 Address window
The Q3 Address window contains three group boxes: Node Area, Node, and Network Parameters. Node Area Select the name of the area from the Name: dropdown list box. If you want to add a new name, or edit or delete an area name, click on Database... The Select Area dialog box will be displayed (Figure 5-14).
Figure 5-14
Select Area dialog box
5-14
C33543002SE_01
To add an area, click on Add... and follow the instructions for adding an area given in Section 6.3.6. To edit an area, click on Edit... and follow the instructions for editing an area given in Section 6.3.7. To delete an area, select the area from the dropdown list box, click on Delete, and follow the instructions for deleting an area given in Section 6.3.8. Node The Node window initially contains the system ID of the node. You can edit this to change the system ID. Network Parameters You can set the Maximum Area Addresses: spin box to any value from 1 to 254. The values which are shown initially are supplied to the SAN C2.0 Manager. by the node. The default value is 3. You can set the Originating level 1 LSP buffer size: spin box to any value from 507 to 1492. The values which are shown initially are supplied to the SAN C2.0 Manager. by the node. The default value is 1492. You should not change the default to another value unless you need to do so. (This may be necessary for connecting to some types of thirdparty equipment.) Caution The network parameters must be the same for all the nodes in the same level 1 area. For example, although a system ID may be from 2 to 18 alphanumeric characters long, all the system IDs in the same level 1 area must be of the same length.
The next window is the Real Time Clock window, as shown in Figure 5-15.
C33543002SE_01
5-15
Figure 5-15
Real Time Clock window
1. In the Set mode radio button group box, you can either select Set to PC time which will make the clock take its time from the PCs clock, or Manual, which will let you set the time manually. If you want to set the time manually, select Manual and follow steps 2. to 4. below; otherwise, go directly to step 4. 2. In the Date fields, click in each box you want to change and type in a new value. Note The year selected must be between the years 19902030.
3. In the Time fields, click in each box you want to change and type in a new value. 4. Select Data Send to Node to send the contents of the window to the node. The entire contents of the Real Time Clock window (date and time) will be sent to the node.
5-16
C33543002SE_01
Note
There will always be a delay in sending the data to the node, so the time on the node will always be inaccurate by the amount of time taken to send the data. For this reason, it is recommended that you should allow for this delay in the time values which you entered.
5.4.1
Updating the Real Time Clock window The Real Time Clock window is not dynamically updated, so if the Real Time Clock window is displayed in the application window for a while, the information displayed in the window quickly becomes out of date. To update the contents of the Real Time Clock window, click in the Real Time Clock window to make it active and select Data Refresh from Node. The current time and date will be reread from the SYNFONET Access Node node and the Real Time Clock window will be updated with the new time and date. The next window is the EFDs window, as shown in Figure 5-16.
C33543002SE_01
5-17
Figure 5-16
Node Settings dialog box EFDs window
This window is used to configure Event Forwarding Discriminators (EFDs). Four EFDs are provided, each of which can be configured to forward alarm and events to a management system. Select which of the four EFDs you want to view and configure by clicking on the appropriate button in the EFD radio button group box. The default is 1. The number of the current EFD is shown in the label of the second group box, so the default label is EFD 1 as in Figure 5-16. To put the selected EFD into use or out of use, click on the Used check box. The NSAP edit field is for the NSAP part of the destination address. (See Appendix C for details of the address format.) You can enter from 1 to 20 bytes in hexadecimal format in this field. The TSEL edit field is for the TSEL part of the destination address. (See Appendix C for details of the address format.) You can enter from 1 to 32 bytes in this field, in hexadecimal format.
5-18
C33543002SE_01
The SSEL edit field is for the SSEL part of the destination address. (See Appendix C for details of the address format.) You can enter from 1 to 16 bytes in this field, in hexadecimal format. The PSEL edit field is for the PSEL part of the destination address. (See Appendix C for details of the address format.) You can enter from 0 to 4 bytes in this field, in hexadecimal format. The Buffer Full radio button group box allows you to specify what the node will do if the EFD buffer becomes full while the node is waiting to send EFD information. If you select Halt, the node will stop accepting new information, but if you select Wrap, the node will begin overwriting the oldest items of information with the newest items. The Reports radio button group box allows you to specify the mode in which the node will send EFD information. If you select Confirmed, the node will obtain confirmation that EFD reports have been received, but if you select Unconfirmed, the node will send EFD reports without obtaining confirmation. The next window is the Software Settings window, as shown in Figure 5-17. This window allows you to:
D D D
Configure the node software release level (the compatibility level) Put the node into Maintenance State Download software to a particular card.
C33543002SE_01
5-19
Figure 5-17
Software Settings window
" To change the present compatibility level of the software: 1. Click on the New Level: dropdown list box. The Maximum Safe Level is displayed above the dropdown list box. The list of available release levels will be displayed as in the example shown in Figure 5-18.
Figure 5-18
Release levels list
5-20
C33543002SE_01
2. Select the release level which you want to apply, and release the mouse button. The level which you have selected will appear in the New Level: dropdown list box. The Valid columns will display either Yes or No to show you whether a switch to the proposed new level would be possibe for each unit listed. The new level cannot be sent to the node until all the software in the units has been switched to valid software (see below). " To switch between inactive and active software: 1. Select one or more units from the list box. 2. Click on the Switch button. The active and inactive software will be switched round. A twoway arrow symbol will be displayed to the left of the unit name, and the serial numbers of the active and inactive software will each have moved to the opposite column (see Figure 5-19).
Figure 5-19
Display of switched software
You can switch back to the previous configuration by clicking on the Switch button again. Note When you send the data to the node to make the switch, the system will display a progress counter and the whirly wheel. In some circumstances, the progress counter window may remain empty while the whirly wheel continues to rotate. This does not necessarily mean that the switch has failed. After a period of up to four minutes, either the Software Settings window will be re-displayed showing a successful switch as in the example in Figure 5-19, or the Reconnecting dialog box (see Section 4.4.8) will be displayed if the switch operation has failed. Some types of switch will cause the SAN C2.0 Manager to close down. Restart it in the usual way.
C33543002SE_01
5-21
Checking compatibility details Before you make any changes, you can preview whether they will be possible or not. " To check compatibility details: 1. Select the unit from the list box. 2. Click on the Details button. The Node Compatibility Details window will be displayed (Figure 5-20).
Figure 5-20
Node Compatibility Details window
The Node Compatibility Details window shows you whether it would be possible to switch software from active to inactive at particular software release levels. If you have asked for a switch which is impossible, the system will reject the change when you select Data Send to Node. The error message shown in Figure 5-21 will be displayed.
5-22
C33543002SE_01
Figure 5-21
Error message for impossible switch
Click on OK and view the Node Compatibility Details window (see above) to see whether you could make the change by altering the Software Release Level. 3. Select Data Send to Node to send the configuration to the node. " To download software to a particular card (Windows NT users only): 1. In the Node Settings window (Figure 5-17), click on Download. The Download Software window is displayed (Figure 5-22).
Figure 5-22
Download Software window
2. If the software which you want is not listed in the Download Software window, click Set Directory... to access the Set Directory window (Figure 5-23). If your PC is on a network, the Network... button will be enabled. Click on Network... to access other network drives in which you can search for the software which you want.
C33543002SE_01
5-23
Figure 5-23
Set Directory window
3. When you have selected the software you want, click OK. The Set Directory window will be closed and the Download Software window will be redisplayed. 4. Select the software to be downloaded to a particular card, by either selecting the check box to the left of the card name, or selecting the check box to the left of the software file name (to select all the cards listed below it). 5. Click on Download. The SAN C2.0 Manager will begin downloading the selected software to the cards which you specified. This may take several minutes. Caution You will not be able to open the Current Alarm List window (see Chapter 14) while a software download is in progress. If you want to be able to receive information about current alarms during the software download, open the Current Alarm List window before you start the download. The Current Alarm List window will be updated automatically while the download is in progress. If you click on Abort during the download, the message shown in Figure 5-24 will be displayed to warn you that the file transfer which is currently in progress cannot be aborted. All file transfers which would have occurred after it will be aborted.
Note
5-24
C33543002SE_01
Figure 5-24
Abort download message
When the SAN C2.0 Manager has finished downloading the software, you will need to refresh the screen. The dialog box shown in Figure 5-25 will be displayed.
Figure 5-25
Refresh screen after download dialog box
Maintenance State Maintenance State notifies the network administrators who are monitoring the network using a network manager such as NMS/10 (see Appendix D) that they can ignore any alarms which the node has raised. These alarms are caused by the fact that the configuration of the node will contain temporary incompatibilities while the changes are being made. Caution You must take the node out of maintenance state when you have finished changing its configuration, so that the network administrators know that any alarms should no longer be ignored.
To put the node into Maintenance State, check the Maintenance State check box. 6. Click on OK and then select Data Refresh from Node.
C33543002SE_01
5-25
Node behaviour after a switch which changes the release level If a software switch would change the node release level, the warning dialog in Figure 5-26 is displayed.
Figure 5-26
Software release level switch warning
If the software release version is completely different (for example, upgrading from C1.0.1 to C1.5.1) the SAN C2.0 Manager will close down completely. Otherwise, the SAN C2.0 Manager will lose the connection to the node and carry out the normal reconnection attempts. The last window is the Test Timeout window, as shown in Figure 5-27. " To change the timeout period for loopback and laser power tests, follow the procedure below: 1. Select Configure Node Settings. 2. Click on the Test Timeout tab button to select the Test Timeout window (Figure 5-27).
5-26
C33543002SE_01
Figure 5-27
Test Timeout window
3. Enter the timeout period in Days, Hours, and Minutes. The maximum value is 99 days, 23 hours, and 59 minutes. The default period is five minutes, as shown in the example in Figure 5-27. 4. Select Data Send to Node to send the contents of the window to the node.
5.5
Installing units in the node

This Section contains information on how to install units in the node, change existing units in the node, or remove units from the node. Note Before attempting to install any units in a node you must ensure that all document windows are closed down.
" To install a unit in a node, follow the procedure below: 1. Click on the slot in the Node Subrack window where you want to install the unit. 2. Click once with the right mouse button.
C33543002SE_01
5-27
3. Select Configure Unit Type.... 4. The Unit Type dialog box will be displayed for the currently selected slot in the Node Subrack window (Figure 5-28).
Figure 5-28
Unit Type dialog box
If there is no unit in the selected slot, the dialog box will display No Unit in the Type dropdown list box. 5. In the Type dropdown list box, select the new unit type you want to install in the selected slot. The unit types listed are the only units that can be installed in the selected slot, for the particular type of node and subrack. The example in Figure 5-28 is for Slot 4, in which you must first select the unit type for the main unit, and then the unit type for the Primary Interface Module. The unit names are shown in their abbreviated form. A full list of the abbreviations used for the units is given in Table 5-1. Note If you want to uninstall a unit, i.e. remove the unit from the node, select No Unit from the list box.
The Description field contains a full description of the unit currently selected in the Type dropdown list box.
5-28
C33543002SE_01
Unit Abbreviation No unit CORE CORE2M STM1 PIM Dual STM1 PIM SAN 2M unit 345M EOW ACL4 Empty slot
Full Unit Name Node Control Unit Node Control Unit with 8 x 2Mbit/s interfaces STM1 Optical Interface Primary Interface Module STM1 Optical Interface Primary Interface Module with two interfaces 21 x 2Mbit/s interfaces and two auxiliary interfaces 345M unit Engineering Order Wire unit Access Line equipment (two sets of 2 Mb/s HDSL interfaces)
Table 5-1
Unit name abbreviations
6. Click on OK. The Node Subrack window will be updated with the new unit for the currently selected slot. The way that the unit is displayed in the Node Subrack window will indicate whether it has been correctly installed (see Figure 5-29).
Actual unit in the slot
Expected unit in the slot No unit expected in the slot
Figure 5-29
Correct and incorrect installations in a subrack
C33543002SE_01
5-29
7. After you have installed all the units, select Data Send to Node to send the contents of the window to the node. Unit Information To view information on a unit in the subrack, select the unit and then select NodeUnit Information. The Unit Information dialog box will be displayed as in Figure 5-30 with the description of the unit and details of the hardware and software.
Figure 5-30
Unit Information dialog box
Related Information For more information on checking that the unit has been installed correctly, refer to Chapter 9.
5.6
Initialising a node
The node can be initialised so that all configuration data (such as crossconnections) is removed. The node must then be configured. This will set the units to the factory default configuration.
5-30
C33543002SE_01
Caution
Before initialising a node, check that there are no other initialised nodes on the network. All initialised nodes are given the same System ID (see Step 6. below). Consequently, two or more initalised nodes appear on the network with the same System ID and cannot be distinguished from each other.
" To perform an initialisation on the node, you will need a potentiometer tool or some other type of nonmetallic stick about 2mm thick and at least 100mm long. Follow the steps below: 1. Exit from SAN C2.0 Manager. 2. Turn off the power to the node. 3. Insert the stick in the reset hole as far as it will go. This will operate the reset button which is hidden at the bottom of the hole. 4. While still keeping the reset button held down, turn the power on again. The colours of the LEDs on the plugin units will change from red to yellow to green. Wait until the LEDs turn yellow and start to blink. 5. When the yellow LED starts to blink, remove the stick. 6. The node is now ready to be installed. The node will be assigned a default NSAP address until you assign it a unique address. The default address details are:
D D D D
AFI: IDI: Area address: System ID:
39 246F 00000116000000010001 DEADDEADF5B0
" To install the node, you must change the area address of your PC: 1. Change the address of your PC to the default address shown above (see Chapter 6 for instructions on changing the address of the PC). 2. Select Node Manage... and connect to the node. 3. While you are using the Installation Wizard to install the node (see Section 5.2), change the address of the node to the address which you want 4. When installation is complete, disconnect from the node.
C33543002SE_01
5-31
5. Change the address of the PC back to the original address which you changed in Step 1.
5-32
C33543002SE_01
Chapter 6 Managing SYNFONET Access Nodes

About this chapter This chapter explains how to use the SAN C2.0 Manager to connect to and manage a SYNFONET Access Node. This chapter contains information on:
D D D D D
Q3 Addressing (Section 6.1) Node Names and Addresses (Section 6.2) Connecting to a node (Section 6.3) Enabling the management and auxiliary channels on the node (Section 6.4) Setting the Manager options (Section 6.5)
This chapter assumes that you have successfully started the SAN C2.0 Manager and installed a node as described in Chapter 4 and Chapter 5.
6.1
6.1.1
Q3 addressing
Connecting to a node The SAN C2.0 Manager is physically connected to a node via the Ethernet cable plugged into the CORE2M unit in the subrack. (See Chapter 4.) The SAN C2.0 Manager uses this Ethernet connection to send management information data to the node, using the communications protocol known as Q3.
C33543002SE_01
6-1
For data to be sent from the SAN C2.0 Manager to the node and from the node to the SAN C2.0 Manager, a Q3 address must be given to the node and to the computer running the SAN C2.0 Manager. Using Q3 addressing, the SAN C2.0 Manager can also connect to and manage other nodes on a network remotely, through the node it is connected to, so long as it knows what the address of the node is. For more information on the format of the Q3 address, refer to Appendix C. 6.1.2 Address of the PC The Q3 address of the PC running the SAN C2.0 Manager is set up during the SAN C2.0 Manager installation procedure, as described in Chapter 3. If you wish to change the address of the computer after the installation procedure, you will need to run the Configure PC Address application located in the appropriate Applications group box. The Configure PC Address application displays a dialog box containing exactly the same fields which are used for setting the address of a node (described in Section 3.4).
6-2
C33543002SE_01
Figure 6-1 6.1.3
Configure PC Address dialog box
Address of a node For the SAN C2.0 Manager to be able to connect to and manage a node it needs to know the Q3 address of the node. The address of a node is a long string of bytes and is difficult to remember, so the SAN C2.0 Manager provides an easy way of referring to nodes, by enabling you to assign names to a node and placing nodes in areas.
6.2
6.2.1
Node names and addresses

Name of a node To simplify the connection procedure the SAN C2.0 Manager enables you to give a node a name and associate the node name with the address of the node. The node address is unique for each node; node names are used just for convenience. This name can then be used to select the required node to manage. The node name is a simple text name.
C33543002SE_01
6-3
If several users access the computer, a single node could be given several different node names, but each node would only have one node address, because a node cannot have more than one node address. 6.2.2 Node areas To further identify a node, it is given an area address. Like the node address, the area address can be given an area name using the SAN C2.0 Manager. A typical arrangement of nodes and areas is shown in Figure 6-2. The same area address can have different names. In this case it is considered two different areas as far as node names are concerned. Areas which have differing area addresses must have a Level 2 Router connecting the areas. In Figure 6-2 two areas have been defined, Cambridge and London, containing five nodes and three nodes respectively. The SAN C2.0 Manager views the nodes in one area separately from nodes in other areas. There is no confusion between the two nodes called Regent St. because they are in different areas. 6.2.3 Rules for assigning node and area names The name you assign to the node or area can be up to 15 characters long, consisting of alphanumeric characters, the space character and the following punctuation characters:
: + . / ( )
The name is not casesensitive, so, for example, the node or area names CPD and cpd are regarded as the same name. Restrictions a. You cannot use the minus sign () in the node or area name, since this will prevent other applications accessing the node or area by its text string. b. The node name cannot begin with a number. The first character of the node name must be a letter.
6-4
C33543002SE_01
Magdalene St. Huntingdon Rd.
Sidney St.
Regent St.
Mill Rd.
Cambridge London
Regent St.
Oxford Rd. Baker St.
Figure 6-2
A network of nodes arranged in areas
6.2.4
Connecting to nodes The SAN C2.0 Manager can connect to nodes in two ways:
D D
via the Ethernet connection using the LocalLAN area via the Management channels and the Ethernet connection at the first node.
LocalLAN area The LocalLAN area enables you to connect to and manage nodes, whether or not they have been given a name or assigned to an area. The nodes to be managed must be connected to your computer via Ethernet. The LocalLAN area is always displayed by the SAN C2.0 Manager when it is connected to a node. This area is always present and includes at least one node: the node which is connected to the computer along with any other nodes which are connected via Ethernet to this node.
C33543002SE_01
6-5
For example, Figure 6-12 in Section 6.4 shows the nodes Sidney St. and Mill Rd. would be contained in the LocalLAN area, because they are connected by Ethernet. These two nodes, together with the other nodes to which they are connected by Ethernet, would also appear in the Cambridge area. Note Any nodes which are connected via Ethernet but which are not operating will not be shown in the LocalLAN area list.
Remote connection by node management channel All other nodes are connected by management channels embedded in STMN signals between the nodes. If these management channels are enabled, then the SAN C2.0 Manager can also connect to and manage these nodes. Section 6.4 describes how to establish and use management channels. These nodes will not appear in the Local LAN list, so to be able to connect to them their details must have been entered in the Manage Node window (see Section 6.3). 6.2.5 Storing node and area information For each node which you connect to, you have to enter the following information about the node:
D D D
A name for the node An address for the node An area, by adding the node to an existing area, or creating a new area for the node.
This information about each node is entered automatically into the node database by the SAN C2.0 Manager. The database file is stored on the computer and automatically maintained by the SAN C2.0 Manager. New node information can be added to the database while you are running the SAN C2.0 Manager. It does not have to be connected to a node. Note When you are using the SAN C2.0 Manager to connect to nodes and enter the details of new nodes, the SAN C2.0 Manager always checks to ensure that you do not give a new node the same name as an already existing node.
6-6
C33543002SE_01
6.2.6
Copying the address database to another PC The address database consists of two files, DBS.LDB and DBS.MDB which are in the directory \NOKIAMGR\SYSTEM\DATABASE. Caution You must not copy a database from a higher version of the software to a PC which is running an earlier version of the software.
6.3
Connecting to a node
" To connect to a node, select Node Manage... from the menu bar. This will bring up the Manage Node dialog box (Figure 6-3):
Figure 6-3
Manage Node dialog box
The Manage Node dialog box displays the nodes which are available on the local LAN and in the node database. The Area group box contains a dropdown list box which lists all the areas that have been created using the SAN C2.0 Manager. The Node List group box contains a list box which lists all the nodes that are contained in the currentlyselected area.
C33543002SE_01
6-7
If this is the first time you have started the SAN C2.0 Manager then the dropdown list box in the area Area group box will contain LocalLAN, and the list box in the Node List group box will show the nodes which are available on the local LAN. From the Manage Node dialog box, you can perform any of the following actions on the database. Note
D D D D D D D D
These changes affect only the database, and have no effect on the nodes themselves.
View the full name and address details for a node (see Section 6.3.1) Manage a node (see Section 6.3.2) Change the address details of a node (see Section 6.3.3) Delete a node address (see Section 6.3.4) Create a new node address (see Section 6.3.5) Create a new area (see Section 6.3.6) Change the address details of an area (see Section 6.3.7) Delete an area (see Section 6.3.8).
6.3.1
Viewing the full name and address details of a node 1. Select Node Manage.... The Manage Node dialog box (Figure 6-3) appears. 2. In the dropdown list box in the Area group box, select the name of the area containing the node you are interested in. 3. (Only if you are searching in the local LAN) if the node which you want is not listed, click on Refresh. This may cause the list of nodes to expand. 4. In the list box in the Node List group box, select the name of the node you are interested in. 5. Click on Details.... The Node Details readonly dialog box will be displayed (Figure 6-4) showing the name and address details of the selected node and also the name and address details of the area containing the node. The SNPA box contains the SubNetwork Point of Attachment (the Ethernet address of the node). Nodes which have a user-defined area and node address do not have an SNPA.
" To view the name and address details, follow the procedure below:
6-8
C33543002SE_01
Figure 6-4
Node Details dialog box
6. Click on OK. The Node Details dialog box will disappear and the Manage Node dialog box will be displayed. 6.3.2 Connecting to a node 1. Select Node Manage.... The Manage Node dialog box appears. 2. In the dropdown list box in the Area group box, select the name of the area containing the node you wish to connect to. 3. In the list box in the Node List group box, select the name of the node you wish to connect to. (If you are searching in the local LAN, click on Refresh. 4. Click on OK. The SAN C2.0 Manager will attempt to connect to the chosen node. If the connection is successful and the node has been installed, the name of the node will be displayed in the Title bar of the application window and the Node Subrack window will be displayed in the workspace of the application window (Figure 6-5).
" To connect to a node, follow the procedure below:
C33543002SE_01
6-9
Figure 6-5 Caution
Application window connected to a node You should not terminate the SAN C2.0 Manager part way through the connection to a node, because this may cause data to be lost or corrupted. If the connection is successful and the node has not been installed, the Install Node dialog box will be displayed. Refer to Section 5.2 for more information.
Note
6.3.3
Changing the address details of a node 1. Select Node Manage.... The Manage Node dialog box appears. 2. In the dropdown list box in the Area group box, select the name of the area containing the node you wish to change. (This cannot be a node in the local LAN.) 3. In the list box in the Node List group box, select the name of the node you wish to change. 4. Click on Edit... in the Node List group box.
" To change the address details, follow the procedure below:
6-10
C33543002SE_01
This brings up the Edit Node dialog box (Figure 6-6), which enables you to edit the address details of the selected node:
Figure 6-6
Edit Node dialog box
5. Edit the details of the node until they are as you want. Refer to Section 6.2 for more information on the node name. Refer to Appendix C for more information on the System ID of the node. 6. Click on OK. The Edit Node dialog box will disappear and the Manage Node dialog box will be updated with the new node name, if the node name has been changed. 6.3.4 Deleting a node address 1. Select Node Manage.... The Manage Node dialog box appears. 2. In the dropdown list box in the Area group box, select the name of the area containing the node you wish to delete. 3. In the list box in the Node List group box, select the name of the node you wish to delete. 4. Click on Delete in the Node List group box. The node will be deleted from the list.
" To delete a node address, follow the procedure below:
C33543002SE_01
6-11
6.3.5
Creating a new node address 1. Select Node Manage.... The Manage Node dialog box appears. 2. Select the area in which you wish to add the new node, from the dropdown list box in the Area group box. 3. Click on Add... in the Node List group box. The Add Node dialog box will be displayed (Figure 6-7).
" To create a new address, follow the procedure below:
Figure 6-7
Add Node dialog box
4. Enter a name for the node in the Node Name: edit field. Refer to Section 6.2 for more information on the node name. 5. Enter the system ID part of the full address of the node in the System ID: edit field. Refer to Appendix C for more information on the System ID of the node. 6. Click on OK. The Add Node dialog box will disappear and the Manage Node dialog box will be updated with the new node name. 6.3.6 Creating a new area
" To create a new area, follow the procedure below:
6-12
C33543002SE_01
1. Select Node Manage.... The Manage Node dialog box appears. 2. Click on Add... in the Area group box.
Figure 6-8
Add Area dialog box
3. Enter a name for the new area in the Area Name: edit field. Refer to Appendix C for more information on the format of the address of a node area. 4. Enter the AFI (Authority and Format Identifier) address in the AFI: field. (See the SAN C2.0 Node Operating Manual for the correct AFI for your country.) This field requires two hexadecimal characters. 5. Enter the IDI (Initial Domain Identifier) address in the IDI: field. This accepts four hexadecimal characters, representing two bytes. All four characters must be entered for this field to be valid. 6. Enter the address of the area in the Area Address: field. This can contain up to 20 hexadecimal characters. 7. Click on OK. The Add Area dialog box will disappear and the Manage Node dialog box will be updated with the new area name information. 6.3.7 Changing the address details of an area
" To edit the address details of the selected area, follow the procedure below:
C33543002SE_01
6-13
1. Select Node Manage.... The Manage Node dialog box appears.
2. In the dropdown list box in the Area group box, select the name of the area you wish to change. 3. Click on Edit... in the Area group box. This brings up the Edit Area dialog box (Figure 6-9), which enables you to edit the address details of the selected node:
Figure 6-9
Edit Area dialog box
6-14
C33543002SE_01
4. Edit the details of the area until they are as you want. Refer to Appendix C for more information on the format of the address of a node area. 5. Click on OK. The Edit Area dialog box will disappear and the Manage Node dialog box will be updated with the new area name, if the area name has been changed. 6.3.8 Deleting an area 1. Select Node Manage.... The Manage Node dialog box appears. 2. In the dropdown list box in the Area group box, select the name of the area you wish to delete. 3. Click on Delete in the Area group box. A warning message box will be displayed, asking you to confirm the operation and warning you that any nodes contained in the area will also be deleted (Figure 6-10).
" To delete an area, follow the procedure below:
Figure 6-10
Delete area warning message dialog box
4. Click on Yes in the warning message box. The area will be deleted, and any nodes contained in this area will also be deleted.
6.4
Management and auxiliary channels

Management and auxiliary connections enable routing of management and userdefined information in overhead bytes between differ-
C33543002SE_01
6-15
ent nodes. SAN C2.0 Manager allows you to configure the following management and auxiliary channels on a node:
D D D D
Q3 Management Channels Overhead channels Summing points EOW Connections
Management channels Management channels provide Q3 management paths between nodes. Auxiliary channels Auxiliary channels consist of overhead channels and summing points. Auxiliary channels can be used to carry management information or to carry test signals, or they can provide an extra (low bandwidth) data path. The Management and Auxiliary Channels window is divided into four tabs: Q3 Management, Overheads, Summing Points, and EOW Connections. Note that EOW Cconnections tab only appears when an EOW unit is installed in the node. You can switch between different tabs by clicking on the tab you want or by pressing CTRL + TAB or CTRL + SHIFT + TAB (see Figure 6-11).
Figure 6-11
Management and auxiliary channels tabs
6.4.1
Q3 management channels Nodes connected via Ethernet can transfer Q3 management data between themselves. To manage nodes which are networked together but not connected by Ethernet, you need to set up a Q3 management channel between both nodes. When a management channel is set up between two nodes, you can use the SAN C2.0 Manager to send management commands to both of these nodes, just as if they were connected by Ethernet, even though only one is connected via Ethernet.
6-16
C33543002SE_01
Management channels are available as embedded signals in STM1 PIMs (via DCCR, DCCM and F2Bytes) or 2M Units (via TSns or R Bytes). This is known as an Embedded Control Channel (ECC). Each STM1 PIM installed in a node is capable of carrying two management channel per STM1 interfaces, except for single-PIM interfaces on SAN C1.0 units, which carry only one channel. You can set up a node management network by careful enabling of the STM1 or 2M management channels. Once this network has been set up, the SAN C2.0 Manager can access any node within the network from any other node on the network. For example, in Figure 6-12, the only nodes accessible to the SAN C2.0 Manager when it is connected to Mill Rd. are the nodes contained in the Cambridge area. However, if you enable the management channel between Huntingdon Rd. and Oxford St. the result is that the London area is now also accessible to the SAN C2.0 Manager. In this state, the SAN C2.0 Manager is able to connect to and manage any node in the two areas when it is connected to any node on the network. This is shown in Figure 6-13. The nodes at either end of a link must have their management channels enabled. (Use SAN C2.0 Manager locally at both nodes to enable the channel.) The same management channel, either DCCM (multiplexer) or DCCR (regenerator) (or RByte, F2Byte, or TSn in 2M Units) must be enabled at both ends for the management link to work.
C33543002SE_01
6-17
Sidney St.
Regent St.
Mill Rd.
Cambridge
Node Manager running on computer
London
Regent St.
Oxford St. Baker St.

Management Channel (Enabled) Management Channel (Disabled) SYNFONET Node Ethernet connection
Figure 6-12
Accessibility of nodes to the SAN C2.0 Manager
6-18
C33543002SE_01
Sidney St.
Regent St.
Mill Rd.
Cambridge
Node Manager running on computer
London
Regent St.
Oxford St.
Baker St.
Ethernet connection
Management Channel (Enabled)
Figure 6-13
Accessibility of nodes to the SAN C2.0 Manager
C33543002SE_01
6-19
" To enable the management channel on an STM1 unit on the currentlymanaged node, follow the instructions below: 1. Select ConfigureMan and Aux. Channels. The Management and Auxiliary Channels window will be displayed, showing the current management channel status (Figure 6-14):
Figure 6-14
Management and Auxiliary Channels window
2. In the Q3 Management tabbed window, select one of the interfaces in the list box. 3. Click on Configure... The Configure window for management and auxiliary channels will be displayed (Figure 6-15).
6-20
C33543002SE_01
Figure 6-15
Configure window for management and auxiliary channels
4. In the Connection tab, select a connection point. Manual adjacencies A manual adjacency is a set of system IDs that define the systems that you can reach via the Q3 link. (For details on how to configure the Q3 stack, see Section 5.4). These provide manual routing information when using SYNFONET Access Nodes with other vendor s kit that does not support automatic ISIS routing protocols. 5. if you want to create manual adjacencies, select the Manual Adjacencies tab and click on Add. The Add Manual Adjacency dialog box is displayed as shown in Figure 6-16.
C33543002SE_01
6-21
Figure 6-16
Add Manual Adjacency dialog box
6. Select an SNPA from the Sub-Network Point of Attachment dropdown list box. 7. Enter a system ID in the System ID text box, and then click on OK. Repeat steps 5. to 7. for any other system IDs that you want to add. The system IDs of the manual adjacencies that you entered will be displayed in the Manual Adjacencies tabbed window, as shown in the example in Figure 6-17.
6-22
C33543002SE_01
Figure 6-17
Manual adjacency system IDs
If you create a new connection from the same connection point, the message dialog shown in Figure 6-18 will be displayed.
Figure 6-18
Same adjacencies message dialog
" To disable a management channel: 1. In the Q3 Management tabbed window, select one of the interfaces in the list box.
C33543002SE_01
6-23
2. Click on Configure... The Configure window for management and auxiliary channels will be displayed (Figure 6-15). 3. Select the connection that you want to disable, and click on Clear. 4. Click on OK. The warning message dialog shown in Figure 6-19 will be displayed.
Figure 6-19
Loss of connection warning message
5. If you want to proceed, click on OK. 6. Select Data Send to Node to send the contents of the window to the node. 6.4.2 Overhead connections The Overhead tab on the Management and Auxiliary Channels window provides a way of configuring the following pointtopoint connections:
D D D D D
OHAUX OHOH VC3F2 VC4F2 TS0 Unless a backup route for traffic is available, do not change the channel on the remote end of the working link, because the link will be cut while the Node Manager disconnects the old link and sets up the new one.
Caution
Clicking on the Overhead tab displays all of the overhead connections configured for the node.
6-24
C33543002SE_01
Figure 6-20
Overhead window
" To add an overhead channel on the currently managed node, follow the instructions below: 1. Click on Add... The Add New Overhead Connection window will be displayed (Figure 6-21):
C33543002SE_01
6-25
Figure 6-21
Add New Overhead Connection window
2. Click on the appropriate tab (AUX, STM-1, VC3, VC4, or TS0 to see the particular OH resource which you want to use. (The Connections fields show which connection points you have selected.) A list of available resources will be displayed as shown in Figure 622.
6-26
C33543002SE_01
Figure 6-22
Overhead connection resources list
3. Select a resource from the list and click on Add Point 1. The selected resource will be shown in bold as in the example in Figure 6-23.
Figure 6-23
Overhead resource selected
4. Select a second resource from this list or one of the other lists available in this dialog, and click on Add Point 2. 5. Click on OK. 6. Select Data Send to Node to send the contents of the window to the node.
C33543002SE_01
6-27
Using a timeslot resource If you choose to use a timeslot resource from the TS0 tab, you must also configure the bitmask to be used. The bitmask window (Figure 6-24) will be displayed automatically.
Figure 6-24
Edit Bitmask window
Either choose one of the bitmask configurations from the dropdown list box, or edit the bitmask manually. 7. Click on OK to add the channel. 8. Select Data Send to Node to send the contents of the window to the node. " To edit an overhead channel on the currentlymanaged node, follow the instructions below: 1. In the Overhead window (Figure 6-20), select a Connection Point pair from the list. 2. Click on Edit.... The Edit Overhead Connection window will be displayed as shown in Figure 6-25.
6-28
C33543002SE_01
Figure 6-25
Edit Overhead Connection window
3. Select the tab for the type of OH resource which you want to edit. 4. Select the new connection point which you want, and make the changes in the same way as for adding a new resource (see above). " To delete an overhead channel on the currentlymanaged node, follow the instructions below: 1. In the Overhead window (Figure 6-20), select a Connection Point pair from the list. 2. Click on Delete. 3. Select Data Send to Node to send the contents of the window to the node.
C33543002SE_01
6-29
6.4.3
Summing points Summing and broadcast bytes differ from overhead bytes in that they are broadcast to many nodes from either one or two sources. For more details, see the Application Planning chapter of the SYNFONET Access Node Operating Manual. Summing points must either contain both master and slave legs, or two master legs. Caution All the summing points on a network must be configured before any data can be sent over it. If you have not configured all the summing points, and one of the bytes is unterminated at some point, the data will not be able to pass that point, and service will be interrupted.
The Summing Points window (Figure 6-26) provides a way of connecting one master summing point to many slaves.
Figure 6-26
Summing Points window
" To add a summing point on the currentlymanaged node, follow the instructions below: 1. Click on the Summing Points tab on the Management And Auxiliary Channels window
2. Select a summing point to configure from the dropdown list box. 3. Click on Configure...
6-30
C33543002SE_01
The Configure Summing Point window will be displayed (Figure 6-27):
Figure 6-27
Configure Summing Point window
4. Click on the appropriate tab (AUX, STM-1, VC4, or TS0) to select a particular type of resouce. 5. Select a new resource from the list. 6. Click on Add Master or Add Slave. 7. Click on OK to add the channel. 8. Select Data Send to Node to send the contents of the window to the node. " To delete a Summing Point channel on the currently-managed node, follow the instructions below:
C33543002SE_01
6-31
1. In the Summing Points window (Figure 6-26 ), select a summing point from the list. 2. Click on Clear. 3. Select Data Send to Node to send the contents of the window to the node. 6.4.4 EOW Connections The EOW (Engineering Order Wire) unit enables you to make service telephone connections. The EOW connections are used to communicate between nodes. This is specifically used for communication between maintenance engineers in areas where they have no access to other communication means such as mobile phones, etc. Configuring an EOW Unit " To configure an EOW connection on the currently-managed node, follow the instructions below:
Figure 6-28
EOW Connections window
1. In the EOW Connections window (Figure 6-28), select an EOW connection from the list.
6-32
C33543002SE_01
2. Click on Configure... The Configure EOW Summing Points window is displayed (Figure 6-29).
Figure 6-29
Configure EOW Summing Point window
3. Select the appropriate tabbed window (STM-N or VC4) for the connection that you want to configure. 4. Select a connection from the list and click on Connect. The message Resource is now an EOW connection is displayed. 5. Click on OK. 6. Select Data Send to Node to send the contents of the window to the node. " To delete an EOW connection from the node: 1. Select the connection from the list of existing connections at the top of the window. 2. Click on Clear.
C33543002SE_01
6-33
3. Click on OK. 4. Select Data Send to Node to send the contents of the window to the node. " To delete all the EOW connections from the node: 5. Click on Clear All. 6. Click on OK. 7. Select Data Send to Node to send the contents of the window to the node.
6.5
Setting the Manager Options

" To set the Manager Options, select Node Manager Options... The Node Manager Options window will be displayed, which has two tabbed pages, View (Figure 6-30) and Polling (Figure 6-31).
6.5.1
View window
Figure 6-30
Node Manager Options View window
Check the Toolbar check box to choose whether the Toolbar is displayed or not. Check the Status Bar check box to choose whether the Status bar is displayed or not. Click on OK to apply the settings.
6-34
C33543002SE_01
6.5.2
Polling window
Figure 6-31
Node Manager Options Polling Window
This window controls whether Auto Refresh is initially enabled in windows to which these categories of information apply. (See the Index for more information on each of these categories.) If you enable or disable Auto Refresh while a window is open, the setting is not remembered, and the next time you open that window Auto Refresh will be set as enabled or disabled according to whether the check box in the Node Manager Options Polling window is checked or empty. When you have made your choices, click on OK to apply the settings.
C33543002SE_01
6-35
6-36
C33543002SE_01
Chapter 7 Configuring synchronisation

About this chapter The node requires a clock source to use for synchronising all its operations. This chapter describes how to configure synchronisation on a SYNFONET Access Node node using the SAN C2.0 Manager. The SAN C2.0 Manager can be used to configure the behaviour of node synchronisation, by enabling you to:
D D D D D D
View information about the status and priority of the node clock selector (Sections 7.2.1 and 7.2.2) Select and configure the sources you want to use for synchronisation (Sections 7.2.3 and 7.2.5 ) Remove node clock synchronisation sources (Section 7.2.4) View and configure the output clock synchronisation (Section 7.3) Set the quality of the selected STMN and external 2M synchronisation sources (Section 7.4) Set overall quality determination on STMN synchronisation sources (Section 7.4)
This chapter assumes that you have successfully started the SAN C2.0 Manager and accessed a node, as described in Chapter 6.
7.1
Introduction
There are a number of possible sources which the node can use for synchronisation. They are listed in Table 7-1.
C33543002SE_01
7-1
Source Internal Node Clock Ext S1 2MHz 2M STM1
Description The nodes internal clock (always available) The output of the node selector (when used as a source) 2MHz external clock S1 2Mbit/s external signals STM1 external signals
Table 7-1
Node synchronisation sources
The node uses two separate clocks for synchronisation:

D D
Internal synchronisation Output synchronisation.
Internal synchronisation This is used to generate the nodes clock, which is used by all the units on the node for synchronisation. The SAN C2.0 Manager is used to configure the sources which can be used for the nodes clock. For more information on viewing the node clock synchronisation sources which are currently being used by the node, refer to Section 7.3. Output synchronisation This is used to generate a node output synchronisation signal, called the external reference signal. For more information on viewing the output synchronisation sources that are currently being used by the node, refer to Section 7.3.
7-2
C33543002SE_01
Available sync sources Internal Clock 2 MHz signal 2M sync sources STMN sync sources External Reference Clock Selector External reference signal used for synchronising other telecomms equipment Internal Reference Clock Selector Sync source used for internal node synchronisation
Node Clock
Figure 7-1
Node synchronisation block diagram
7.1.1
Node selectors information The SAN C2.0 Manager also monitors the health and alarm status of the reference clock selectors: the part of the node which selects the external and internal synchronisation sources to use. For more information on viewing node selector information, refer to Section 7.2.3. Health of the clock selector The possible health settings of the node clock selector are given in Table 7-2.
Health Good Bad Description The node clock is giving valid output. The node hardware is producing an undefined output.
Table 7-2
Possible health settings of the clock selector
C33543002SE_01
7-3
Alarms on the clock selector The possible alarm text which may be displayed for the clock selector is given in Table 7-3.
Alarm text LTI Description (Loss of Timing Information) Using internal clock while there are only unusable synchronisation sources left in the priority list. Synchronisation forced
FORC
Table 7-3 Note
Possible alarms on the clock selector The LTI alarm is not shown if there are no sources above Internal in the priority list.
For more information about the colour of the alarms displayed in the Synchronisation window, refer to Section 14.2. 7.1.2 Availability of synchronisation sources The availability of the synchronisation sources can vary because of many factors: As units are installed or removed the number of sources will increase or decrease. Note If you remove a card while the window showing its details is open on the screen, the window will not be updated until you select Data Refresh from Node.
D D
If the network becomes unstable, certain synchronisation sources may become unavailable.
Consequently, the node needs to be able to quickly select another synchronisation source to use. The SAN C2.0 Manager can be used to provide a list of possible sources for the node to use. From this list, the node itself selects the source to use for synchronisation. The SAN C2.0 Manager displays the availability of the synchronisation sources. A list of the possible types of availability is given in Table 7-4.
7-4
C33543002SE_01
Source OK Not OK No Lock
Description The synchronisation source is available. The synchronisation source is not available. The synchronisation source is unstable.
Table 7-4
Source availability types
For more information on selecting the sources to be used for synchronisation, refer to Section 7.2.2. For more information on removing sources used for synchronisation, refer to Section 7.2.4. 7.1.3 Quality of synchronisation sources The sources also have a quality associated with them. Quality refers to the quality of the signals clock. For all STM1 synchronisation sources, the quality is normally carried in the SDH signal overhead, by Synchronisation Status Messaging (SSM). The STM1 quality can also be manually forced to a fixed quality; for instructions on how to do this, see Section 7.4. If the STM1 interface comes from equipment which does not support SSM, you can set the interface quality manually (see Section 7.4) The 2MHz external clock signal and the 2Mbit/s signals have no such innate quality in the clock signal. Therefore, these sources need to have their quality level set manually (see Section 7.4). The SAN C2.0 Manager can be used to display and configure the quality of the 2M signals used for synchronisation. The list of possible quality levels used in descending order of quality is given in Table 7-5.
C33543002SE_01
7-5
Quality G.811 G.812T(ransit) G.812L(ocal) SETS Do Not Use
Description of quality level A Primary Reference Clock defined in G.811 A transit node clock defined in G.812 A local node clock defined in G.812 Synchronous Equipment Timing Source (internal oscillator of a node) Do not use for synchronisation (to prevent timing loops)
Table 7-5
Types of 2M synchronisation quality levels
For more information on configuring the quality of the 2M signals used for synchronisation, refer to Section 7.4. 7.1.4 Priority of synchronisation sources The node will always use the available source with the highest quality for synchronisation. If two or more sources have equal quality levels and are also both available, the node will consult the priority list to resolve which source should be used for synchronisation. The priority list is configured using the SAN C2.0 Manager. For more information, refer to Section 7.2.1.
7-6
C33543002SE_01
7.2
7.2.1
Viewing and configuring the node clock

Changing the priority list
" To change the priority of the synchronisation sources, follow the procedure below: 1. Select Configure Synchronisation. The Synchronisation window will be displayed (Figure 7-2).
Figure 7-2
Synchronisation window
2. Click on the Node Clock tab button, if it is not already selected. Node Clock is the default window. 3. Select a source from the Sources list box by clicking on it. 4. Click on Add to move the selected source into the Priority List list box.
C33543002SE_01
7-7
5. Repeat the procedure from steps 3 and 4 until all the sources you require have been added to the Priority List list box. (You can add up to 16 sources to the priority list.) 6. Select an entry in the Priority List list box whose level of priority you want to either raise or lower. 7. Set the priority of the new signal source by either: S S Clicking on Raise to increase the priority for that signal. Clicking on Lower to lower the priority.
8. Continue moving the signal sources until they are ordered in the desired priority. 9. You can also remove a signal source from the Priority List list box by selecting it and then clicking on Remove. (See Section 7.2.4) 10. Select Data Send to Node to send the contents of the window to the node. The data will be sent to the node as described in Section 7.5. Note You cannot raise the priority of the Internal synchronisation source (Internal clock). This is always the last source in the Priority List list box. This source will be used if none of the other synchronisation sources in the priority list are available.
7-8
C33543002SE_01
7.2.2
Viewing the synchronisation source
" To view the current synchronisation source being used to generate the nodes clock, follow the procedure below: 1. Select Configure Synchronisation. The Synchronisation window appears (Figure 7-2). 2. Click on the Node Clock tab, if it is not already selected. The current source being used for synchronisation will be shown in the Current Source field in the Status group box. The current source is also displayed in the Node Subrack window. 7.2.3 Viewing selector information
" To view information about the status of the clock selector for the synchronisation sources, follow the procedure below: 1. Select Configure Synchronisation. The Synchronisation window appears (Figure 7-2). 2. Click on the Node Clock tab button (if it is not already selected) to view the status of the synchronisation source node selector. The status of the clock selector is displayed in the Status group box, showing the health of the selector and any alarm associated with the selector. The most severe current alarm associated with the selector is displayed in its abbreviated form. The background colour (grey scale for monochrome monitors) of the alarm field indicates the severity of the alarm. If there is no alarm is present on the selector, the field is empty and filled with green (white for grey scale monitors). If no alarm information has been received from the node, the field is empty and filled with the background colour of the Synchronisation window. 7.2.4 Removing synchronisation sources
" To remove synchronisation sources from the priority list so that they cannot be used by the node for synchronisation, follow the procedure below: 1. Select Configure Synchronisation.
C33543002SE_01
7-9
The Synchronisation window appears (Figure 7-2). 2. Click on the Node Clock tab button, if it is not already selected. 3. In the Priority List list box, select the source which you want to remove from use. 4. Click on Remove. Note You cannot remove the Internal synchronisation source (Internal clock). This source will be used if none of the other synchronisation sources in the priority list are available.
5. Select Data Send to Node to send the contents of the window to the node. The data will be sent to the node as described in Section 7.5. 7.2.5 Configuring the source selection mode
" To configure whether the synchronisation source will be selected automatically or manually, follow the procedure below: 1. Select Configure Synchronisation. 2. Click on the Node Clock tab button (if it is not already selected). 3. Check Auto Refresh to cause the current source field to be updated periodically from the node. 4. Select the method for determining the priority source by checking one of the Mode radio buttons. The node can select the source by using the Priority List (Section 7.2.1), by the item determined by Manual selection, or use HoldOver to force use of the internal clock. Note If you select Manual, you must then select a source from the Priority List or Sources list boxes. When you have selected a source, the name of that source is displayed in the readonly field to the right of the Manual radio button, as shown in Figure 7-3.
If a node is forced manually to a source which is not available, the node will go into HoldOver mode. When the source becomes available, the node will then switch to manual mode.
7-10
C33543002SE_01
Figure 7-3
Manuallyselected source name display
5. Select Data Send to Node to send the contents of the window to the node. The data will be sent to the node as described in Section 7.5. For more information on setting the priority of the synchronisation sources, refer to Section 7.2.1. 7.2.6 Calibrating the node clock 1. Select Configure Synchronisation. 2. Click on the Node Clock tab button (if it is not already selected). 3. Check Calibrate Internal Clock. The internal clock will be calibrated from the current source when you next send the contents of the window to the node. The Calibrate Internal Clock check box will then be cleared automatically. If you try to calibrate with any source which is not G.811, a warning message will be displayed. You should carry out a calibration of the node clock after it has been in service for two years. 4. Select Data Send to Node to send the contents of the window to the node. The data will be sent to the node as described in Section 7.5. For more information on setting the priority of the synchronisation sources, refer to Section 7.2.1.
" To calibrate the node clock, follow the procedure below:
C33543002SE_01
7-11
7.3
7.3.1
Viewing and configuring the output clock

Viewing the output synchronisation source
" To view the current synchronisation source being used by the SAN C2.0 Manager to generate the nodes 2 MHz output synchronisation signal, follow the procedure below: 1. Select Configure Synchronisation. The Synchronisation window appears (Figure 7-2). 2. Click on the Output tab button, if it is not already selected. The Output window is displayed (Figure 7-4).
Figure 7-4
Output window
The current source being used for Ext S1 synchronisation will be indicated by the radio buttons. Either the Node Clock or the source displayed alongside the Other radio button will be used.
7-12
C33543002SE_01
7.3.2
Configuring the output clock source
" To select the source which you want to use for the external reference, follow the procedure below: 1. Select Configure Synchronisation. The Synchronisation window appears (Figure 7-2). 2. Click on the Output tab button (if it is not already selected). The Output window appears (Figure 7-4). 3. Select the source to be used by checking either the Node Clock or Other radio buttons. If you chose Other for a reference source, do this by doubleclicking on the source, or by highlighting it and pressing the Select button. The name of the source being used is then displayed next to the Other radio button. 4. Select Data Send to Node to send the contents of the window to the node. The data will be sent to the node as described in Section 7.5.
7.4
Setting the quality of the synchronisation sources

This section describes how to set the quality of the STM1 and 2M sources which you are using for node synchronisation. " To set the quality of the synchronisation sources, follow the procedure below: 1. Select Configure Synchronisation. The Synchronisation window appears (Figure 7-2). 2. Click on the Quality tab button on top of the window. The Synchronisation (Quality) window appears (Figure 7-5), showing all the STM1 and 2M synchronisation sources which are potentially available for node synchronisation. The current quality level of these sources (see Table 7-5) is also displayed alongside the source.
C33543002SE_01
7-13
Figure 7-5
Synchronisation (Quality) window
3. In the list box, select the source you want to set the quality for. 4. Click on the radio button in the Quality Determination group box corresponding to how the quality is to be assigned. STM1 can have the quality assigned automatically by SSM, or you can assign the quality manually. Because 2M and 2MHz signal quality is always defined manually, the Quality Determination group box will be disabled when you select signals of these types. 5. If you choose Set Manually, you can click on the radio button in the Quality Level group box corresponding to the quality level you want to set for the selected source. S The quality level for the selected source(s) will change in the list box as you click on the radio button in the Quality Level group box.
If you choose Use SSM, the quality level will be set automatically by the node using the Synchronisation Status Messages.
7-14
C33543002SE_01
6. Select Data Send to Node to send the contents of the window to the node. The data will be sent to the node as described in Section 7.5.
7.5
Sending the synchronisation data to the node

To send the editable data contained in the Synchronisation window to the node: select Data Send to Node. The contents of the window will be sent to the node as described in Section 4.4.3. If the data is successfully sent to the node, the Synchronisation window will be redisplayed.
C33543002SE_01
7-15
7-16
C33543002SE_01
Chapter 8 Configuring 2Mbit/s interfaces

About this chapter This chapter describes how to use the SAN C2.0 Manager to configure 2Mbit/s interfaces on 2M and CORE2M units. (You cannot configure a CORE unit.) The SAN C2.0 Manager must have at least one CORE or CORE2M unit installed, or it will not operate. This chapter assumes that you have successfully started the SAN C2.0 Manager and accessed a node, as described in Chapter 6.
8.1
Introduction
There are two types of 2M interface units which can be installed in a SYNFONET Access Node :
D D
SAN2M units CORE2M units
The 2M unit provides 21 2M interfaces and the CORE2M unit provides 8 interfaces, each with the following functional blocks:
D D D D
E12 E12/P12 P12/S12 S12
C33543002SE_01
8-1
8.1.1
Accessing a 2M interface unit to configure it All the 2M interface units are displayed in the subrack. Select the interface unit which you want to configure by clicking on it once with the left mouse button. The selected interface unit will appear to protrude from the subrack as shown in Figure 8-1.
Figure 8-1
Subrack with 2M unit selected
8.1.2
Blocks and alarm fields To see any alarms which may be in effect on this unit, doubleclick on the selected unit with the left mouse button. The configure window for the unit will be displayed, in the form of a series of blocks each with a coloured alarm field. (If you have a monochrome monitor, the alarm fields will appear in white or two different depths of grey, looking similar to the way they do in the printed example in Figure 8-2.) If a particular block is not being monitored for alarms, its alarm field will be grey.
8-2
C33543002SE_01
Figure 8-2
Example window showing blocks and alarm fields
The alarm field shows the most severe alarm on that block, with the name of the type of alarm in abbreviated form. The meaning of the colours or scale of grey is explained in Table 14-6. The definitions of the alarm severities are given in Table 14-5. For more information about alarms, see Section 8.2.1 and Chapter 14.
8.2
Using the configuration window

The various blocks are described below. You select a block by clicking on it.
8.2.1
Viewing block status alarms When you have selected a block, you can see any alarms which currently exist on that block by clicking once with the right mouse button. This will bring up a popup menu offering you the choice between
C33543002SE_01
8-3
viewing block status alarms and configuring the block. This is shown in Figure 8-3.
Figure 8-3
Block status alarms popup menu
Click on Block Status.The Block Status window for the selected block will be displayed as in Figure 8-4.
8-4
C33543002SE_01
Figure 8-4
Block Status window
8.2.2
Viewing the Status of the 2M signal 1. Click on the unit you want to configure in the Node Subrack window. 2. Select Configure Interface. 3. The Configure window for the unit selected in the Node Subrack window will be displayed, showing details about the unit, down to the functional block level.
" To view the Signal Status, follow the steps below:
C33543002SE_01
8-5
Figure 8-5
2M Configure Window
If the E12 field displays Out of Use, that channel is disabled and therefore it does not generate alarms (the channel also sends 2MAIS upstream and downstream). When the channel is In Use, the E12 field will display the interface alarms (if any have occurred). The test loopback status, if configured for the interface, is displayed in the same box in which alarms appear. The P12/S12 block contains alarm information for bytesynchronous PDH interfaces. 8.2.3 Viewing the Status of the VC12 Signal 1. Click on the unit you want to configure in the Node Subrack window. 2. Select Configure Interface.
" To view the Signal Status, follow the steps below:
8-6
C33543002SE_01
The Configure window (Figure 8-5) for the unit selected in the Node Subrack window will be displayed, showing details about the unit, down to the functional block level. 3. The S12 functional block column shows the VC12 signal alarm status. See Figure 8-6.
Figure 8-6
S12 block
If the S12 field displays NMON, that channel is not being monitored and it does not generate alarms. When the channel is being monitored, the S12 field will display the VC12 alarms (if any have occurred). If you want to change the status of the VC12 signal (that is, enable or disable monitoring of the signal and generation of alarms), see LPT block in Section 8.2.4. 4. The P12/S12 functional block column shows what type of mapping is being used by the VC12 signal. See Figure 8-7.
Figure 8-7
VC12 Mapping Type Field
This field can contain one of three different types of mapping. These are listed in Table 8-1.
Content Of Field aSy bSy bTe Meaning Asynchronous Bytesynchronous-monitored Bytesynchronous-terminated
Table 8-1
VC12 Mapping Types
C33543002SE_01
8-7
Mapping mode The mapping modes determine the amount of error detection that is carried out, and also determine access to the internals of the signal. If the data in the 2M is not a G.703 framed signal, you must use Asynchronous mapping mode. Asynchronous means that the data is treated as an unstructured data stream. No access to any of the timeslots is allowed, and only LOS errors will be reported. If the data in the 2M is G.703-framed, you can use Asynchronous mapping mode if you want, or you can do more error checking on the signal by selecting either ByteSynchronous-Monitored or ByteSynchronous-Terminated mode. ByteSynchronous-Monitored means that the node does not terminate TS0, but does look at its contents. TS0 can be used for carrying data such as PDH management data. ByteSynchronous-Monitored mode allows checking of LOF, AIS, DEG, RDI, SSF, and EXC in the PDH direction, and LOF and AIS in the SDH direction. ByteSynchronousMonitored mode does not disturb the CRC, so equipment further down the path can look at the CRC for the whole path. ByteSynchronousMonitored mode requires stricter timing than Asynchronous mode: 4.6 ppm, compared to 50 ppm for Asynchronous mode. ByteSynchronous-Terminated means that TS0 is terminated. The content of TS0 is examined, and then regenerated (including the CRC). TS0 can still be used for carrying data such as PDH management data. In ByteSynchronous-Terminated mode, PDH errors are reported, but not SDH errors (because the signal is being regenerated at this point). ByteSynchronous-Terminated mode requires stricter timing than Asynchronous mode: about 4.6 ppm, compared to 50 ppm for Asynchronous mode. If you want to change the signal mapping of the VC12 signal, see Section 8.2.4. 8.2.4 Configuring Individual Blocks in the 2M Window
E12 block " To configure an Electrical Physical PDH Interface (E12) block, select the E12 block that you want to configure, and click once with the right mouse button. A popup menu will appear. Click on Configure. The window shown in Figure 8-8 is displayed.
8-8
C33543002SE_01
Figure 8-8
2M E12 block window
The Channel field shows which interface you are configuring. If you select the tabs for the other functional blocks (E12/P12, P12/S12, and S12), you will see that the Channel field appears in all of them, looking exactly the same. If you select a different channel in any of the functional blocks, all the other blocks will change to the new channel automatically. The Physical Interface group box contains two controls. The Interface in use check box allows you to choose whether the E12 interface is enabled or not Note If the 2M interface is not in use, the signal transmitted (both upstream and downstream) is 2MAIS.
When the interface is not in use the alarms for the same functional blocks are not generated, and so they are not displayed in this window.
C33543002SE_01
8-9
The two check boxes in the Performance Collection group box allow you to choose whether performance data will be collected every 15 minutes, every 24 hours, at both of these intervals, or not at all. The Loopback dropdown list box allows you to select one of four options for test loopback signals:
D D D D
(No Loopback) To Equipment To Interface To Equipment and Interface.
If you want to apply the changes which you have made in this window to more than one channel, click on Also Apply To... The window shown in Figure 8-9 is displayed.
Figure 8-9
Also Apply To window
To apply the changes to all the channels, click on OK. To apply them to only some of the channels, use the check boxes to select which channels will have their configuration changed. E12/P12 block " To configure the E12/P12 block, either click with the right mouse button on the E12/P12 block and then click on Configure on the popup menu, or click with the left mouse button on the E12/P12 tab. The window shown in Figure 8-10 is displayed.
8-10
C33543002SE_01
Figure 8-10
2M E12/P12 block window
The CRC4 monitored group box contains two check boxes which control whether the received PDH signal is expected to contain Cyclic Redundancy Check4 (CRC4) signals. If either or both of the boxes is checked, CRC4 will be monitored. The SDH Direction and PDH Direction check boxes control the direction in which CRC-4 will be monitored.(These check boxes will not be displayed if the VC12 mapping is not bytesynchronous.) The Retiming Enabled check box controls whether the signal retiming function is enabled or not. The signal retiming function is for use when equipment connected to the SDH network cannot use any means of synchronisation except the incoming 2Mbit/s. The 2Mbit/s retiming causes additional delay to the signal flow because of the buffer which is used to filter out most of the wander introduced in the signal by the mapping and pointer jitter. The signal retiming function uses the SYNFONET Access Node clock to
C33543002SE_01
8-11
resynchronise the signal. Signal retiming is illustrated by the two diagrams in Figure 8-11.
2 MHz
PDH 2 Mbit/s
SYNFONET SAN Node
SDH Network
Synchronizing PDH equipment by using a 2MHz signal from SDH network
Retiming
SDH Network
Retimed SYNFONET 2 Mbit/s SAN Node
PDH
Synchronizing PDH equipment by using a retimed 2 Mbit/s signal from SDH network
Figure 8-11
Signal retiming
8-12
C33543002SE_01
P12/S12 block To configure the P12/S12 block, either click with the right mouse button on the P12/S12 block and then click on Configure on the popup menu, or click with the left mouse button on the P12/S12 tab. The window shown in Figure 8-12 is displayed.
Figure 8-12
2M P12/S12 block window
The VC12 Mapping dropdown list box allows you to choose among three modes: Asynchronous, ByteSynchronousMonitored, and ByteSynchronousTerminated. The readonly Signal Labels field shows the label of the actual received signal (Rx Received) the label of the expected received signal (Rx Expected), and the label of the signal to be transmitted (Tx Sent). Table 8-2 lists the possible signal label values which can be displayed in these fields.
C33543002SE_01
8-13
Text Unequipped Equipped non specific Asynchronous Bit synchronous Bytesynchronous Test signal VCAIS
C2 byte value (hex) 0 1 2 3 4 6 7
Table 8-2
Signal label values
For all other values, the text shown will be Equipped unused (xxh), where xx is the value of the signal label in hexadecimal format. You may see this in some cases where the signal label is obtained from the network. If you want to apply the changes which you have made in this window to more than one channel, click on Also Apply To... The window shown in Figure 8-9 is displayed. To apply the changes to all the channels, click on OK. To apply them to only some of the channels, use the check boxes to select which channels will have their configuration changed.
8-14
C33543002SE_01
S12 block To configure the S12 block, either click with the right mouse button on the S12 block and then click on Configure on the popup menu, or click with the left mouse button on the S12 tab if you can see it. The window shown in Figure 8-13 is displayed.
Figure 8-13
2M S12 block window
The VC12 Path Monitoring box allows you to choose whether the VC12 path is monitored or not. If the Monitored check box is checked, monitoring is enabled, and alarms will be generated. The two check boxes in the Performance Collection group box allow you to choose whether performance data will be collected every 15 minutes, every 24 hours, at both of these intervals, or not at all. The Trail Trace check box allows you to choose whether to monitor the trail trace which is received. With Trail Trace enabled, the Rx Received
C33543002SE_01
8-15
is compared to Rx Expected and a Trail Trace Identifier Mismatch alarm is raised if they are different. The readonly Rx Received field and the Tx Sent field are always displayed. The Rx Received field shows any trail trace which is being received. The Rx Expected field is displayed only when Trail Trace is enabled. It contains the trail trace expected to be received (up to fifteen 7bit alphanumeric characters), which you can edit. The Tx Sent field contains the trail trace to be sent (up to fifteen 7bit alphanumeric characters). Note When you edit the Rx Expected field or the Tx Sent field, the characters appear underlined as shown in Figure 8-13.
If you want to apply the changes which you have made in this window to more than one channel, click on Also Apply To... The window shown in Figure 8-9 is displayed. To apply the changes to all the channels, click on OK. To apply them to only some of the channels, use the check boxes to select which channels will have their configuration changed.
8-16
C33543002SE_01
8.3
CORE2M units
A typical CORE2M configuration window is shown in Figure 8-14.
Figure 8-14
Configure CORE2M unit window
8.3.1
Configuring individual blocks in the CORE2M window
E12 block " To configure an Electrical Physical PDH Interface (E12) block, select the E12 block that you want to configure, and click once with the right mouse button. A popup menu will appear. Click on Configure. The window shown in Figure 8-15 is displayed.
C33543002SE_01
8-17
Figure 8-15
CORE2M E12 block window
The Channel field shows which interface you are configuring. If you select the tabs for the other functional blocks (E12/P12, P12/S12, and S12), you will see that the Channel field appears in all of them, looking exactly the same. If you select a different channel in any of the functional blocks, all the other blocks will change to the new channel automatically. Caution If you make a change in one block (using, for example, Channel 1), and then move to a different channel in another block (for example, Channel 2), the change which you made in the original block will be made to the new channel and not to the one in which you were originally working. In this example, the change will be made to Channel 2 and not to Channel 1.
The Physical Interface group box contains two controls. The Interface in use check box allows you to choose whether the E12 interface is en-
8-18
C33543002SE_01
abled or not. If this check box is enabled, use the Monitoring drop down list box to choose whether alarms will be generated when they occur (Monitored) or not (Not Monitored). Note If the 2M interface is not in use, the signal transmitted (both upstream and downstream) is 2MAIS.
When the interface is not in use the alarms for the same functional blocks are not generated, and so they are not displayed in this window. The two check boxes in the Performance Collection group box allow you to choose whether performance data will be collected every 15 minutes, every 24 hours, at both of these intervals, or not at all. The Loopback dropdown list box allows you to select one of four options for test loopback signals:
D D D D
(No Loopback) To Equipment To Interface To Equipment and Interface.
Figure 8-16
To apply the changes to all the channels, click on OK. To apply them to only some of the channels, use the check boxes to select which channels will have their configuration changed.
C33543002SE_01
8-19
E12/P12 block " To configure the E12/P12 block, either click with the right mouse button on the E12/P12 block and then click on Configure on the popup menu, or click with the left mouse button on the E12/P12 tab. The window shown in Figure 8-17 is displayed.
Figure 8-17
2M E12/P12 block window
The Retiming Enabled check box controls whether the signal retiming function is enabled or not. The signal retiming function is for use when equipment connected to the SDH network cannot use any means of synchronisation except the incoming 2Mbit/s. The 2Mbit/s retiming causes additional delay to the signal flow because of the buffer which is used to filter out most of the wander introduced in the signal by the mapping and pointer jitter. The signal retiming function uses the SYNFONET Access Node clock to
8-20
C33543002SE_01
resynchronise the signal. Signal retiming is illustrated by the two diagrams in Figure 8-18.
2 MHz
PDH 2 Mbit/s
SYNFONET SAN Node
SDH Network
Synchronizing PDH equipment by using a 2MHz signal from SDH network
Retiming
SDH Network
Retimed SYNFONET 2 Mbit/s SAN Node
PDH
Synchronizing PDH equipment by using a retimed 2 Mbit/s signal from SDH network
Figure 8-18
Signal retiming
C33543002SE_01
8-21
P12/S12 block To configure the P12/S12 block, either click with the right mouse button on the P12/S12 block and then click on Configure on the popup menu, or click with the left mouse button on the P12/S12 tab. The window shown in Figure 8-19 is displayed.
Figure 8-19
2M P12/S12 block window
The VC12 Mapping dropdown list box allows you to choose among three modes: Asynchronous, ByteSynchronousMonitored, and ByteSynchronousTerminated. Refer back to Section 8.2.3 for explanation of Mapping mode. Note If TSn is being used for data, it cannot be used for payload. This restriction does not apply to TS0.
8-22
C33543002SE_01
The readonly Signal Labels field shows the label of the actual received signal (Rx Received) the label of the expected received signal (Rx Expected), and the label of the signal to be transmitted (Tx Sent). Table 8-3 lists the possible signal label values which can be displayed in these fields.
Text Unequipped Equipped non specific Asynchronous Bit synchronous Bytesynchronous Test signal VCAIS Value (hex) 0 1 2 3 4 6 7
Table 8-3
Signal label values
For all other values, the text shown will be Equipped unused (xxh), where xx is the value of the signal label in hexadecimal format. You may see this in some cases where the signal label is obtained from the network. If you want to apply the changes which you have made in this window to more than one channel, click on Also Apply To... The window shown in Figure 8-16 is displayed. To apply the changes to all the channels, click on OK. To apply them to only some of the channels, use the check boxes to select which channels will have their configuration changed.
C33543002SE_01
8-23
S12 block To configure the S12 block, either click with the right mouse button on the S12 block and then click on Configure on the popup menu, or click with the left mouse button on the S12 tab if you can see it. The window shown in Figure 8-20 is displayed.
Figure 8-20
CORE2M S12 block window
The VC12 Path Monitoring box allows you to choose whether the VC12 path is monitored or not. If the Monitored check box is checked, monitoring is enabled, and alarms will be generated. The two check boxes in the Performance Collection group box allow you to choose whether performance data will be collected every 15 minutes, every 24 hours, at both of these intervals, or not at all. The Trail Trace check box allows you to choose whether to monitor the trail trace which is received. With Trail Trace enabled, the Rx Received
8-24
C33543002SE_01
is compared to Rx Expected and a Trail Trace Identifier Mismatch alarm is raised if they are different. The readonly Rx Received field and the Tx Sent field are always displayed. The Rx Received field shows any trail trace which is being received, and the details are repeated automatically in the Rx Expected field if it is displayed. The Rx Expected field is displayed only when Trail Trace is enabled. It contains the trail trace expected to be received (up to fifteen 7bit alphanumeric characters), which you can edit. The Tx Sent field contains the trail trace to be sent (up to fifteen 7bit alphanumeric characters). Note When you edit the Rx Expected field or the Tx Sent field, the characters appear underlined as shown in Figure 8-20.
If you want to apply the changes which you have made in this window to more than one channel, click on Also Apply To... The window shown in Figure 8-16 is displayed. To apply the changes to all the channels, click on OK. To apply them to only some of the channels, use the check boxes to select which channels will have their configuration changed.
C33543002SE_01
8-25
8-26
C33543002SE_01
Chapter 9 Configuring single-interface terminal multiplexers

About this chapter This chapter describes how to use the SAN C2.0 Manager to configure terminal multiplexers using STM-1 single Primary Interface Modules (PIMs) on a SYNFONET Access Node node. (For details on configuring STM-1 dual Primary Interface Modules, see Chapter 10.) This chapter assumes that you have successfully started the SAN C2.0 Manager and accessed a node, as described in Chapter 6.
9.1
Introduction
The STM-1 Single PIM contains one optical interface with either four or six functional blocks:
D D D D D D
OS1 RS1 MS1 MS1/S4 S4 (only if the MS1/S4 functional block has been terminated) S4/TUG (only if the MS1/S4 functional block has been terminated)
9.1.1
Accessing an STM-1 single PIM interface unit to configure it Select the interface unit which you want to configure by clicking on it once with the left mouse button. The selected interface unit, together
C33543002SE_01
9-1
with the CORE2M unit to which it is linked, will appear to protrude from the subrack as shown in Figure 9-1.
Figure 9-1
Subrack with STM-1 single PIM unit selected
9.1.2
Blocks and alarm fields To see any alarms which may be in effect on this unit, doubleclick on the selected unit with the left mouse button. The configure window for the unit will be displayed, in the form of a series of blocks each with a coloured alarm field at the bottom of the block. (If you have a monochrome monitor, the alarm fields will appear in white or two different depths of grey, looking similar to the way they do in the printed example in Figure 9-2.) If a particular block is not being monitored for alarms, its alarm field will be grey.
9-2
C33543002SE_01
Figure 9-2
9.2
Using the configuration window
Figure 9-3
STM1 configuration window
The window shown above is a typical example of an STM1 window. Windows which you see on your screen may be somewhat different: the number of blocks which are shown vary, because they depend on the settings which have been applied for the unit. The various blocks which may appear are described below. You select a block by clicking on it.
C33543002SE_01
9-3
Laser power indication The window also shows the laser power, both Tx (transmitted) and Rx (received), as well as OFF if the laser is off and ALS if Auto Laser Shutdown is active. 9.2.1 Viewing Block Status alarms When you have selected a block, you can see any alarms which currently exist on that block by clicking once with the right mouse button. This will bring up a popup menu offering you the choice between viewing block status alarms and configuring the block. This is shown in Figure 9-4.
Figure 9-4
Click on Block Status Alarms. The Block Status window will be displayed as in the example shown in Figure 9-5.
9-4
C33543002SE_01
Figure 9-5
Block Status window
The Block Status window gives you details about the alarms on the block, including the full name of the type of alarm. You can find out when alarms occurred by setting up an Event History log (see Chapter 14). Updating of the alarm information You can arrange for the Block Status window to show new alarms which occur on the node while the window is open on your screen. Check the Auto Refresh box. Alarms which are cleared will also have their status updated in the window. 9.2.2 Configuring individual blocks
OS1 block " To configure the OS1 block, click with the left mouse button on Configure. The window shown in Figure 9-6 is displayed.
C33543002SE_01
9-5
Figure 9-6
Configure OS1 block window
The Monitoring dropdown list box is for setting the monitoring state of the interface. There are two possible values: Monitored or Not monitored. The Auto Refresh for laser powers check box lets you determine whether the laser power measurements are updated periodically from the node to the unit window. You can define the default for whether Auto Refresh is initially enabled or disabled; this is done in the Node Manager Options window. (Select Node Manager Options... if you want to do this; see Section 6.5.) The Laser State dropdown list box lets you set the mode of the laser to be Normal, Forced On, Forced Off or Test.
D D D D
Normal sets the laser to turn itself on and off as required. Forced On sets the laser to be on all the time. Forced Off sets the laser to be off all the time. Test is used when you are carrying out a laser power test.
In the Automatic Laser Shutdown group box, the ALS enabled check box lets you choose whether ALS is enabled or not. If the box is
9-6
C33543002SE_01
checked, ALS is enabled. The Manual Restart check box allows you to request a Manual Restart. If the box is checked, you are requesting a Manual Restart. The 2 seconds and 90 seconds radio buttons give you a choice of whether the laser will restart manually for 2 or for 90 seconds. RS1 block " To configure the RS1 block, either click with the right mouse button on the RS1 block and then click on Configure on the popup menu, or click with the left mouse button on the RS1 tab. The window shown in Figure 9-7 is displayed.
Figure 9-7
Configure RS1 block window
" This block shows the Regenerator Section Termination function. The two check boxes in the Performance Collection group box allow you to choose whether performance data will be collected every 15 minutes, every 24 hours, at both of these intervals, or not at all.
C33543002SE_01
9-7
If security is enabled, you must hold at least user access level 2 (NMS10 Basic) (see Chapter 15) to be able to edit the performance collection settings. The Trail Trace check box allows you to choose whether to monitor the trail trace which is received. With Trail Trace enabled, the Rx Received is compared to Rx Expected and a Trail Trace Identifier Mismatch alarm is raised if they are different. The readonly Rx Received field and the Tx Sent field are always displayed. The Rx Received field shows any trail trace which is being received. If no trail trace is being received by the node, the message NO TTI RECEIVED is displayed. The Rx Expected field is displayed only when Trail Trace is enabled. It contains the trail trace expected to be received (up to fifteen 7bit alphanumeric characters), which you can edit. The Tx Sent field contains the trail trace to be sent (up to fifteen 7bit alphanumeric characters). Note When you edit the Rx Expected field or the Tx Sent field, the characters appear underlined as shown in Figure 9-7.
You should check the Single Fibre Working check box whenever you are using the node for single fibre working. When the box is checked, the system will raise an LOS alarm if the Rx Received signal is the same as the Tx Sent signal. The LOS alarm is raised because this situation suggests that the fibre is broken, and that the node is receiving its own signal back reflected from the face of the broken fibre. Also Apply To... The Also Apply To... button allows you to apply any editing changes which you have made in one channel to one or more of the other channels in the tab which is open. When you click on the Also Apply To... button, the Also Apply To... dialog box is displayed (Figure 9-8).
9-8
C33543002SE_01
Figure 9-8
Also Apply To dialog box
When all the details in the RS1 window are as you want them, click on OK and then select Data Send to Node to send the contents of the window to the node.
C33543002SE_01
9-9
MS1 block " To configure the MS1 block, either click with the right mouse button on the MS1 block and then click on Configure on the popup menu , or click with the left mouse button on the MS1 tab. The window shown in Figure 9-9 is displayed.
Figure 9-9
Configure MS1 block window
This block shows the Multiplex Section Termination function. The two check boxes in the Performance Collection group box allow you to choose whether performance data will be collected every 15 minutes, every 24 hours, at both of these intervals, or not at all.
9-10
C33543002SE_01
MS1/S4 block " To configure the MS1/S4 block, either click with the right mouse button on the MS1/S4 block and then click on Configure on the popup menu, or click with the left mouse button on the MS1/S4 tab. The window shown in Figure 9-10 is displayed.
Figure 9-10
Configure MS1/S4 block window
This block shows the Multiplex Section Adaptation function. The check box in the VC4 Path group box allows you to choose whether the higher order path is terminated. S4 block The S4 block is displayed only if the VC4 path has been terminated in the MS1/S4 block (see Figure 9-10). " To configure the S4 block, either click with the right mouse button on the S4 block and then click on Configure on the popup menu, or click with the left mouse button on the S4 tab if you can see it. The window shown in Figure 9-11 is displayed.
C33543002SE_01
9-11
Figure 9-11
Configure S4 block window
This block shows the Higher order Path Termination function. (If the VC4 path is not terminated, this tab will be blank.) The VC-4 path monitoring check box allows you to choose whether the VC-4 path is monitored for alarms or not. The two check boxes in the Performance Collection group box allow you to choose whether performance data will be collected every 15 minutes, every 24 hours, at both of these intervals, or not at all. The Trail Trace check box allows you to choose whether to monitor the trail trace which is received. With Trail Trace enabled, the Rx Received is compared to Rx Expected and a Trail Trace Identifier Mismatch alarm is raised if they are different. The readonly Rx Received field and the Tx Sent field are always displayed. The Rx Received field shows any trail trace which is being received. If no trail trace is being received by the node (as in the example in Figure 9-11 above), the message NO TTI RECEIVED is displayed. The Rx Expected field is displayed only when Trail Trace is enabled. It contains the trail trace expected to be received (up to fifteen 7bit alphanumeric characters),
9-12
C33543002SE_01
which you can edit. The Tx Sent field contains the trail trace to be sent (up to fifteen 7bit alphanumeric characters). Note When you edit the Rx Expected field or the Tx Sent field, the characters appear underlined as shown in Figure 9-11.
S4/TUG block The S4/TUG block is displayed only if the VC4 path has been terminated in the MS1/S4 block (see Figure 9-10). " To configure the S4/TUG block, either click with the right mouse button on the S4/TUG block and then click on Configure on the popup menu, or click with the left mouse button on the S4/TUG tab if you can see it. The window shown in Figure 9-12 is displayed.
Figure 9-12
Configure S4/TUG block window
This block shows the Higher order Path Adaptation function. (If the VC4 path is not terminated, this tab will be blank.)
C33543002SE_01
9-13
There are three readonly fields in the Signal Labels group box. The Rx Received field shows the actual received signal label in textual form. The possible values are shown in Table 9-1.
Text Unequipped Equipped non specific TUG structure Locked TU ATM MAN (DQDB) FDDI Test signal VCAIS C2 byte value (hex) 0 1 2 3 13 14 15 FE FF
Table 9-1
Signal label values
The Rx Expected field shows the expected signal label in the same format as shown in the table above. The Tx Sent field shows the signal label which is sent, in the same format as shown in the Table 9-1.
9.2.3
Configuring the TUG structure
" To configure the TUG Structure, click on the TUG Mapping... button. The TUG Structure window will be displayed as shown in Figure 9-13.
9-14
C33543002SE_01
Figure 9-13
TUG structure window
This window displays the mapping of the VCNs in the terminated VC4. The meaning of the icons is explained below. Icon Meaning Terminated Nonterminated Terminated and not editable (already crossconnected) Nonterminated and not editable (already crossconnected) Note If you want to make a particular uneditable VCN editable, you can do it by deleting the crossconnection (see Chapter 12).
1. Click on the or + boxes to change the mapping. 2. When the TUG structure is as you want it, click on OK.
C33543002SE_01
9-15
3. Select Data Send to Node to send the contents of the window to the node.
9-16
C33543002SE_01
Chapter 10 Configuring dual-interface terminal multiplexers

About this chapter This chapter describes how to use the SAN C2.0 Manager to configure STM-1 dual Primary Interface Modules (PIMs) in a SYNFONET Access Node node. (For details on configuring STM-1 single Primary Interface Modules, see Chapter 9.) This chapter assumes that you have successfully started the SAN C2.0 Manager and accessed a node, as described in Chapter 6.
10.1 Introduction
The STM-1 dual PIM contains two optical interfaces, each of which has either four or six functional blocks:
D D D D D D
OS1 RS1 MS1 MS1/S4 S4 (only if the MS1/S4 functional block has been terminated) S4/TUG (only if the MS1/S4 functional block has been terminated)
C33543002SE_01
10-1
10.1.1 Accessing an STM-1 dual PIM interface unit to configure it Select the interface unit which you want to configure by clicking on it in the subrack once with the left mouse button. The selected interface unit will appear to protrude from the subrack as shown in Figure 10-1.
Figure 10-1
Subrack with STM-1 Dual PIM unit selected
10.1.2 Blocks and alarm fields To see any alarms which may be in effect on this unit, doubleclick on the selected unit with the left mouse button. The configure window for the unit will be displayed, in the form of a series of blocks each with a coloured alarm field at the bottom of the block. (If you have a monochrome monitor, the alarm fields will appear in white or two different depths of grey, looking similar to the way they do in the printed example in Figure 10-2.) If a particular block is not being monitored for alarms, its alarm field will be grey.
10-2
C33543002SE_01
Figure 10-2
C33543002SE_01
10-3
10.2 Using the configuration window
Figure 10-3
STM1 configuration window
The window shown above is a typical example of an STM1 dual PIM unit window. Windows which you see on your screen may be somewhat different: the number of blocks which are shown vary, because they depend on the settings which have been applied for the unit. The various blocks which may appear are described below. You select a block by clicking on it. Laser power indication The window also shows the laser power transmitted (Tx) and received (Rx), as well as OFF if the laser is off and ALS if Auto Laser Shutdown is active. 10.2.1 Viewing block status alarms When you have selected a block, you can see any alarms which currently exist on that block by clicking once with the right mouse button. This will bring up a popup menu offering you the choice between viewing block status alarms and configuring the block. This is shown in Figure 10-4.
10-4
C33543002SE_01
Figure 10-4
Click on Block Status. The Block Status window will be displayed as in the example shown in Figure 10-5.
Figure 10-5
Block Status window
The Block Status window gives you details about the alarms on the block, including the full name of the type of alarm. You can find out when alarms occurred by setting up an Event History log (see Chapter 14).
C33543002SE_01
10-5
Updating of the alarm information You can arrange for the Block Status window to show new alarms which occur on the node while the window is open on your screen. Check the Auto Refresh box. Alarms which are cleared will also have their status updated in the window. 10.2.2 Configuring individual blocks OS1 block " To configure the OS1 block, click with the left mouse button on Configure. The window shown in Figure 10-6 is displayed.
Figure 10-6
Configure OS1 block window
The Monitoring dropdown list box is for setting the monitoring state of the interface. There are two possible values: Monitored or Not monitored. The Auto Refresh for laser powers check box lets you determine whether the laser power measurements are updated periodically from
10-6
C33543002SE_01
the node to the unit window. You can define the default for whether Auto Refresh is initially enabled or disabled; this is done in the Node Manager Options window. (Select Node Manager Options... if you want to do this; see Section 6.5.) The Laser State dropdown list box lets you set the mode of the laser to be Normal, Forced On, Forced Off or Test.
D D D D
Normal sets the laser to turn itself on and off as required. Forced On sets the laser to be on all the time. Forced Off sets the laser to be off all the time. Test is used when you are carrying out a laser power test.
In the Automatic Laser Shutdown group box, the ALS enabled check box lets you choose whether ALS is enabled or not. If the box is checked, ALS is enabled. The Manual Restart check box allows you to request a Manual Restart of the laser. If the box is checked, you are requesting a Manual Restart. The 2 seconds and 90 seconds radio buttons give you a choice of whether the laser will restart manually for 2 or for 90 seconds. If you want the changes which you have made to also be applied to the other interface, click on Also Apply To... The Also Apply To... window will be displayed as shown in Figure 10-7.
Figure 10-7
Check the box for the other channel and click on OK.
C33543002SE_01
10-7
RS1 block " To configure the RS1 block, either click with the right mouse button on the RS1 block and then click on Configure on the popup menu, or click with the left mouse button on the RS1 tab. The window shown in Figure 10-8 is displayed.
Figure 10-8
Configure RS1 block window
" This block shows the Regenerator Section Termination function. The two check boxes in the Performance Collection group box allow you to choose whether performance data will be collected every 15 minutes, every 24 hours, at both of these intervals, or not at all. If security is enabled, you must hold at least user access level 2 (NMS10 Basic) (see Chapter 15) to be able to edit the performance collection settings. The Trail Trace check box allows you to choose whether to monitor the trail trace which is received. With Trail Trace enabled, the Rx Received is compared to Rx Expected and a Trail Trace Identifier Mismatch alarm is raised if they are different. The readonly Rx Received field
10-8
C33543002SE_01
and the Tx Sent field are always displayed. The Rx Received field shows any trail trace which is being received. If no trail trace is being received by the node, the message NO TTI RECEIVED is displayed. The Rx Expected field is displayed only when Trail Trace is enabled. It contains the trail trace expected to be received (up to fifteen 7bit alphanumeric characters), which you can edit. The Tx Sent field contains the trail trace to be sent (up to fifteen 7bit alphanumeric characters). Note When you edit the Rx Expected field or the Tx Sent field, the characters appear underlined as shown in Figure 10-8.
You should check the Single Fibre Working check box whenever you are using the node for single fibre working. When the box is checked, the system will raise an LOS alarm if the Rx Received signal is the same as the Tx Sent signal. The LOS alarm is raised because this situation suggests that the fibre is broken, and that the node is receiving its own signal back reflected from the face of the broken fibre. Also Apply To... If you want the changes which you have made to also be applied to the other interface, click on Also Apply To... The Also Apply To... window will be displayed as shown in Figure 10-7. When all the details in the RS1 window are as you want them, click on OK and then select Data Send to Node to send the contents of the window to the node.
C33543002SE_01
10-9
MS1 block " To configure the MS1 block, either click with the right mouse button on the MS1 block and then click on Configure on the popup menu, or click with the left mouse button on the MS1 tab. The window shown in Figure 10-9 is displayed.
Figure 10-9
Configure MS1 block window
This block shows the Multiplex Section Termination function. The two check boxes in the Performance Collection group box allow you to choose whether performance data will be collected every 15 minutes, every 24 hours, at both of these intervals, or not at all. If you want the changes which you have made to also be applied to the other interface, click on Also Apply To... The Also Apply To... window will be displayed as shown in Figure 10-7.
10-10
C33543002SE_01
MS1/S4 block " To configure the MS1/S4 block, either click with the right mouse button on the MS1/S4 block and then click on Configure on the popup menu, or click with the left mouse button on the MS1/S4 tab. The window shown in Figure 10-10 is displayed.
Figure 10-10 Configure MS1/S4 block window This block shows the Multiplex Section Adaptation function. The check box in the VC4 Path group box allows you to choose whether the higher order path is terminated. If you want the changes which you have made to also be applied to the other interface, click on Also Apply To... The Also Apply To... window will be displayed as shown in Figure 10-7. S4 block The S4 block is displayed only if the VC4 path has been terminated in the MS1/S4 block (see Figure 10-10).
C33543002SE_01
10-11
" To configure the S4 block, either click with the right mouse button on the S4 block and then click on Configure on the popup menu, or click with the left mouse button on the S4 tab if you can see it. The window shown in Figure 10-11 is displayed.
Figure 10-11 Configure S4 block window This block shows the Higher order Path Termination function. (If the VC4 path is not terminated, this tab will be blank.) The VC-4 path monitoring check box allows you to choose whether the VC-4 path is monitored for alarms or not. The two check boxes in the Performance Collection group box allow you to choose whether performance data will be collected every 15 minutes, every 24 hours, at both of these intervals, or not at all. The Trail Trace check box allows you to choose whether to monitor the trail trace which is received. With Trail Trace enabled, the Rx Received is compared to Rx Expected and a Trail Trace Identifier Mismatch alarm is raised if they are different. The readonly Rx Received field and the Tx Sent field are always displayed. The Rx Received field
10-12
C33543002SE_01
shows any trail trace which is being received. If no trail trace is being received (as in the example shown in Figure 10-11 above) the message NO TTI RECEIVED will be displayed. The Rx Expected field is displayed only when Trail Trace is enabled. It contains the trail trace expected to be received (up to fifteen 7bit alphanumeric characters), which you can edit. The Tx Sent field contains the trail trace to be sent (up to fifteen 7bit alphanumeric characters). Note When you edit the Rx Expected field or the Tx Sent field, the characters appear underlined as shown in Figure 10-11.
If you want the changes which you have made to also be applied to the other interface, click on Also Apply To... The Also Apply To... window will be displayed as shown in Figure 10-7. S4/TUG block The S4/TUG block is displayed only if the VC4 path has been terminated in the MS1/S4 block (see Figure 10-10). " To configure the S4/TUG block, either click with the right mouse button on the S4/TUG block and then click on Configure on the popup menu, or click with the left mouse button on the S4/TUG tab if you can see it. The window shown in Figure 10-12 is displayed.
C33543002SE_01
10-13
Figure 10-12 Configure S4/TUG block window This block shows the Higher order Path Adaptation function. (If the VC4 path is not terminated, this tab will not be available.) There are three readonly fields in the Signal Labels group box. The Rx Received field shows the actual received signal label in textual form. The possible values are shown in Table 10-1.
10-14
C33543002SE_01
Text Unequipped Equipped non specific TUG structure Locked TU ATM MAN (DQDB) FDDI Test signal VCAIS
C2 byte value (hex) 0 1 2 3 13 14 15 FE FF
Table 10-1
Signal label values
The Rx Expected field shows the expected signal label in the same format as shown in the table above. The Tx Sent field shows the signal label which is sent, in the same format as shown in the Table 10-1. If you want the changes which you have made to also be applied to the other interface, click on Also Apply To... The Also Apply To... window will be displayed as shown in Figure 10-7. 10.2.3 Configuring the TUG structure " To configure the TUG Structure, click on the TUG Mapping... button. The TUG Structure window will be displayed as shown in Figure 10-13.
C33543002SE_01
10-15
Figure 10-13 TUG structure window This window displays the mapping of the VCNs in the terminated VC4. The meaning of the icons is explained below. Icon Meaning Terminated Nonterminated Terminated and not editable (already crossconnected) Nonterminated and not editable (already crossconnected) Note If you want to make a particular uneditable VCN editable, you can do it by deleting the crossconnection (see Chapter 12).
1. Click on the or + boxes to change the mapping. 2. When the TUG structure is as you want it, click on OK.
10-16
C33543002SE_01
C33543002SE_01
10-17
10-18
C33543002SE_01
Chapter 11 Configuring 345M units

About this chapter This chapter describes how to use the SAN C2.0 Manager to configure 345M (34M/45M) units in a SYNFONET Access Node. This chapter assumes that you have successfully started the SAN C2.0 Manager and accessed a node, as described in Chapter 6.
11.1 Introduction
The 345M interface unit allows 34 or 45Mbit/s PDH signals to be transmitted over SDH networks. You can change the unit from 34M mode to 45M mode or the other way round (see Section 11.1.3). " To configure a 345M unit, begin by selecting it in the subrack window, either by clicking on it once with the left mouse button, or by navigating to it with the arrow keys. The 345M unit will then appear to protrude from the subrack, as shown in Figure 11-1.
C33543002SE_01
11-1
Figure 11-1
Subrack with 345M unit selected
Either doubleclick on the 345M unit or press the Spacebar while the 345M unit is selected. This will open the Configuration window for the 345M unit. A typical 345M Configuration window is shown in Figure 11-2.
Figure 11-2
345M Configuration window
11.1.1 Blocks and alarm fields The configuration window is in the form of a series of blocks each with an alarm field at the bottom of the block.
11-2
C33543002SE_01
If the interface is set to Monitored, the field will show the colour or shade of grey representing the most severe current alarm on that block, with the name of the type of alarm in abbreviated form. If there are no alarms, the field will be green (white for monochrome monitors), and if the interface is not being monitored, the field will show the background colour. The meaning of the colours or scale of grey is explained in Table 14-6. The definitions of the alarm severities are given in Table 14-5. For more information about alarms, see Section 11.1.2 and Chapter 14. 11.1.2 Viewing 345M block alarms Once you have selected a block by clicking on it with the left mouse button, you can see any alarms which currently exist on that block (if the interface is being monitored) by clicking once with the right mouse button. This will bring up the popup menu shown in Figure 11-3.
Figure 11-3
345M Block alarms popup menu
Click on Block Alarms with the left mouse button. The Block Status window will be displayed as in the example shown in Figure 11-4.
C33543002SE_01
11-3
Figure 11-4
Block Status window
The Block Status window gives you details about the alarms on the block, including the full name of the type of alarm. You can find out when alarms occurred by setting up an Event History log (see Chapter 14). Updating the alarm information You can arrange for the Block Status window to show new alarms which occur on the node while the Block Status window is open on your screen. Check the Auto Refresh box. Alarms that are cleared will disappear from the window. 11.1.3 Configuring individual blocks in the 345M window " Select a block to configure by doubleclicking on it with the left mouse button. E3 block The E3 (Electrical PDH Physical Interface) block is shown in Figure 11-5.
11-4
C33543002SE_01
Figure 11-5
345M E3 block
In the Physical Interface group box, the Interface in use check box controls whether the interface is in use or not. Click in the check box to enable or disable the interface. You must hold at least user access level 3 (NMS10 Experienced) (see Chapter 15) to be able to change the setting of the Interface in use check box. When the physical interface is in use, alarms are reported for the E3 and S3/P3 blocks. Note If the 345M interface is not in use, the signal transmitted (both upstream and downstream) is 45MAIS.
When the interface is not in use the alarms for the same functional blocks are not generated, and so they are not displayed in this window. The Performance Collection group box contains two check boxes which allow you to choose whether performance data will be collected
C33543002SE_01
11-5
every 15 minutes, every 24 hours, at both of these intervals, or not at all. You must hold at least user access level 2 (NMS10 Basic) (see Chapter 15) to be able to change the Performance Collection settings. The Loopback group box allows you to choose one of four options for loopback tests:
D D D D
(No loopback) To Equipment To Interface To Equipment and Interface.
The Tx Level option button group box (which appears only when the unit is in 45M mode) allows you to choose between two options:
D D
High level Low level.
You must hold at least user access level 4 (NMS10 Network Administrator) (see Chapter 15) to be able to change the Sensitivity Level setting. 1. When all the details in the E3 block are as you want them, click on OK. 2. Select Data Send to Node to send the contents of the window to the node. S3/P3 block The S3/P3 (Lower order Path Adaptation) block is shown in Figure 11-6.
11-6
C33543002SE_01
Figure 11-6
345M S3/P3 block
There are three readonly fields in the Signal Labels group box. The Rx Received field displays the actual signal label of the received signal, in the format shown in Table 11-1. The Rx Expected field shows the signal label expected to be received. The Tx Sent field shows the signal label of the transmitted signal. The possible signal label values are shown in Table 11-1. The term value means the actual value in the C2 byte.
C33543002SE_01
11-7
Text Unequipped Equipped non specific TUG structure Locked TU Async 34M/45M Async 140M ATM MAN (DQB) FDDI Test signal VCAIS
Value (hex) 0 1 2 3 4 12 13 14 15 FE FF
Table 11-1
Signal label values
The Mode option button group box allows you to switch between 34M mode and 45M mode. You must hold at least user access level 4 (NMS10 Network Administrator) (see Chapter 15) to be able to change the mode. 1. When all the details in the S3/P3 block are as you want them, click on OK. 2. Select Data Send to Node to send the contents of the window to the node. S3 block The S3 (Lower order Path Termination) block is shown in Figure 11-7.
11-8
C33543002SE_01
Figure 11-7
345M S3 block
The VC3 path monitoring check box allows you to choose whether the VC3 path is monitored for alarms or not. You must hold at least user access level 2 (NMS10 Basic) (see Chapter 15) to be able to change the setting of the VC3 path monitoring check box. The two check boxes in the Performance Collection group box allow you to choose whether performance data will be collected every 15 minutes, every 24 hours, at both of these intervals, or not at all. You must hold at least user access level 2 (NMS10 Basic) (see Chapter 15) to be able to change the Performance Collection settings. The Trail Trace check box allows you to choose whether to monitor the trail trace which is received. You must hold at least user access level 3 (NMS10 Experienced) (see Chapter 15) to be able to change the setting of the Trail Trace check box.
C33543002SE_01
11-9
The readonly Rx Received field and the Tx Sent field are always displayed. The Rx Received field shows any trail trace which is being received, and the details are repeated automatically in the Rx Expected field if it is displayed. Note Because the trail trace names can contain blank spaces, all the characters appear underlined as shown in Figure 11-8 so that you will be able to see where a blank space appears.
The Rx Expected field is displayed only when Trail Trace is enabled. It contains the trail trace expected to be received (up to fifteen 7bit alphanumeric characters), which you can edit. The Tx Sent field contains the trail trace to be sent (up to fifteen 7bit alphanumeric characters). 1. When all the details in the S3 block are as you want them, click on OK. 2. Select Data Send to Node to send the contents of the window to the node.
11-10
C33543002SE_01
Chapter 12 Configuring cross connections

About this chapter This chapter describes how to use the SAN C2.0 Manager to configure the cross connections for various types of SYNFONET Access Node. For a complete list of the different types of node supported by the SAN C2.0 Manager, refer to Appendix B. For more information on the hardware specification of SYNFONET Access Node, refer to the SYNFONET Access Node Operating Manual. This chapter contains information on:
D D D D D D D D
Path protection (Section 12.2) Viewing current cross connections (Section 12.3) Adding cross connections (Section 12.4) Editing cross connections (Section 12.5) Protecting cross connections (Section 12.6) Unprotecting cross connections (Section 12.7) Deleting cross connections (Section 12.8) Printing cross connections (Section 12.9) Successfully installed the correct units required for using SYNFONET Access Node. Successfully started the SAN C2.0 Manager and accessed the node you want to configure, as described in Chapter 6.
This chapter assumes that you have:

D D
C33543002SE_01
12-1
12.1 Introduction
Cross connections enable you to connect traffic on two or three interfaces of one node to another. Using the SAN C2.0 Manager you can view, add, edit, protect, unprotect, and delete the cross connections on a node. 12.1.1 Characteristics of cross connections All cross connections are bidirectional; that is, interfaces which are connected can both transmit and receive signals. The different types of card support the following levels.
D D D
STMN: VC4, VC3, VC2, and VC12 2M: 345M VC12 VC3
Each cross connection is made up of the following data:

D D
A descriptive name At least two connection points (CPs) CP1 and CP2. There may also be a third CP (the protecting CP) if the cross connection is protected. If the cross connection is protected, a protection group number will be displayed. The protection group number is assigned automatically by the SAN C2.0 Manager.
Each CP in a connection must be different and cannot be used in any other connection. Also, each CP in a protected connection must be part of a different AU4, so that the protecting connection will not be affected by a problem which interrupts the protected connection. 12.1.2 Cross connection path protection Cross connection path protection enables you to protect a path between two nodes by providing an alternative route for the signal if the existing path becomes unavailable. The SAN C2.0 Manager supports singleended, bidirectional, oneplusone subnetwork connection (SNC) protection at the VC12 level. (VC4, VC3, and VC2 cross connections cannot be protected.
12-2
C33543002SE_01
12.1.3 Representing cross connections
Cross Connection name
Reliable CP Protected CP
Protecting CP
Figure 12-1
Typical cross connection table from a window
The complete cross connection layout for a node is known as a cross connection table. This table appears in the Cross Connection window (Figure 12-4). A typical cross connection table is shown in Figure 12-1. The table contains either one or two lines of text for each cross connection: S The first line for each cross connection contains the Name of the cross connection (see Section 12.1.4), followed by the two connection points (CP1/ Reliable CP and CP2/ Unreliable CP) used in the cross connection. (For more information on viewing cross connections, refer to Section 12.3.) If the cross connection is protected, the line underneath the protected cross connection will contain the name of an additional CP (the protecting CP). This will be located underneath CP2/Unreliable CP. (For more information on cross connection path protection, refer to Section 12.1.2.)
12.1.4 Cross connection naming You can give a cross connection descriptive name, so that the cross connection can be easily identified when the full cross connection table for a node is displayed in a window. The name given to a cross connection can be up to 15 alphanumeric characters long: for example, LondonHelsinki.
C33543002SE_01
12-3
12.1.5 Termination identification The connection points given in a Cross Connection window are used to locate precisely where on the node the signal is being transmitted and received. The connection points are identified using different schemes depending on the interface unit being used for the cross connection. Tributary Unit Groups The multiplexing hierarchy for all units which can be installed in a SYNFONET Access Node node is controlled by the Tributary Unit Group (TUG) which forms part of the complete SYNFONET Access Node node architecture hierarchy. If you are not familiar with TUGs or the other related terminology, refer to the SYNFONET Access Node Operating Manual. STM1 interface units For connection points on STM1 units, the TU3, TU2, and TU12 connection points are identified according to their position within the multiplexing hierarchy on the STM1 signal. The connection points are denoted using the format: Us STM1 (k, l, m) Table 12-1 defines the variables used in the format.
Variable s Range 18 Definition Slot number of the STM1 unit in the node subrack The number of the TUG3 The number of the TUG2 (within the kth TUG3) The number of the TU12 (VC12) within the lth TUG2
k l
13 17
13
Table 12-1
STM1Connection Point Definition
12-4
C33543002SE_01
For example, connection point U1 STM1 (2,6,2) designates a connection point on an STM1 unit located in slot 1 on the node and location 2,6,2 in the multiplexing hierarchy of the STM1 unit. (See Figure 12-2):
STM1 Slot 1 TUG3 2 TUG2 6 TU12 2
Figure 12-2
Part of the Multiplexing Hierarchy for an STM1 Unit
2M interface units The connection points on 2M units are identified by their physical interface on the unit. They are denoted using the format: Us 2M q Table 12-2 defines the variables used in the format.
Variable s q Range 1, 38 121 Definition Slot number of the 2M unit in the node subrack The physical interface number on the 2M unit in slot s
Table 12-2
2M interface definition
For example, connection point U7 2M i/f:9 designates a connection point on the 2M unit located in slot 7 on the node at physical interface 9 on the unit.
C33543002SE_01
12-5
12.2 Path protection

SAN C2.0 Manager can provide, for example, self-healing rings. In the example shown in Figure 12-3, the protected signal is simultaneously transmitted to both sides of the ring and both signals are monitored at the receiving end. If the primary signal fails, the receiving node switches automatically to the protecting signal.
CA AC
Normal operation: Connection AC operating normally.
Node A
Node E
Node B
Node D
Node C
CA
AC
Failure: Connection AC switched to the protecting signal in nodes A and C.
CA AC
LINK FAILURE
Node A
Node E
Node B
Node D
Node C
CA AC
Figure 12-3
Bidirectional self-healing ring
12-6
C33543002SE_01
12.3 Viewing cross connections

Users at any access level (see Chapter 15) can view cross connections even if security has been enabled. " To view the current cross connection configuration for the currently managed node, select Configure Cross Connections. The Cross Connection window appears showing the Cross connection table for the currently managed node. A typical Cross Connection window is shown below (Figure 12-4):
Figure 12-4
Cross Connection window
12.3.1 Sorting the Cross Connection window You can sort the Cross Connection window by one of the following categories:
D D D
Name (or Protection Group, if names are duplicated) CP1 CP2
This is especially useful when you are searching for a particular cross connection, which you may only know by its name or by one of the CPs used in the connection.
C33543002SE_01
12-7
By name To sort the Cross Connection window by name, click on the Name list title. The names are listed in alphabetical order. (The numbers 0 to 9 are sorted before A to Z.) The Protection Group (PG) number of the cross connection is shown to the left of the name. If names are duplicated, they are sorted by Protection Group number. By CP To sort the Cross Connection window by CP, click on the CP1 or CP2 list title. If you select CP1, the Cross Connection window is sorted by the first CP in the cross connection (CP1). If you select CP2, the Cross Connection window is sorted by the second CP in the cross connection (CP2).
12.4 Adding cross connections

If security is enabled, you must hold at least user access level 3 (NMS10 Experienced) (see Chapter 15) to be able to add cross connections. " To add a cross connection, follow the procedure below: 1. Select Configure Cross Connections.
12-8
C33543002SE_01
The Cross Connection window (shown in Figure 12-4) appears. Select the level type (VC4, VC3, VC2 or VC12) by clicking on the appropriate tab. 2. Click on the Add button in the Cross Connection window. The Add Cross Connection dialog box appears (Figure 12-5):
Figure 12-5
Add Cross Connection dialog box
3. Click in the Connection Name: edit field and type in a name for the cross connection which you are adding. The name can be up to 15 alphanumeric characters long. Select a name which gives an indication of the path of the signal which you are connecting.
C33543002SE_01
12-9
4. Click in the Number of Connections edit field and type in the number of cross connections which you are adding. (If you add more than one cross connection, they will all have the same name.) The number of connections you can enter is from 1 up to the maximum number, such that no CP in the new connection will be used twice. 5. Select one CP each from the CP1 and CP2 group boxes as the CPs which you want to use for the cross connection. The dropdown list box in each group box contains families of CPs. Note The entries in the CP lists are based on installed equipment. The cross connect will fail if you attempt to create a cross connect based on equipment which is shown in the window as being installed, but which has been removed from the equipment rack since the last time the window was updated.
6. Doubleclick on the first CP which you want to use. A list of the channels which are available on the CP is displayed as shown in Figure 12-6.
Figure 12-6
Example of channels within a CP
7. If you are making a VC12 cross connection, and you want to protect the cross connection, select the Protecting CP check box and select an available channel. (For more information on protecting cross connections, see Section 12.6.) (Protection is not available for VC4, VC3, or VC2 cross connections.) 8. Click on Next if you want to add another cross connection to the current Cross Connection window, and then repeat from Step 4. Otherwise, click on OK. If you click on Next, the Add Cross Connection dialog box will be filled in with the next available CPs.
12-10
C33543002SE_01
If you click on OK, the Add Cross Connection dialog box will disappear. The Cross Connection window will be updated with the new cross connection. If you have entered a value greater than 1 in the Number of Connections:, the window will be updated with all the new cross connections. All the new cross connections will have the same name. 9. Select Data Send to Node to send the contents of the window to the node.
12.5 Editing Cross Connections

If security is enabled, you must hold at least user access level 3 (NMS10 Experienced) (see Chapter 15) to be able to edit cross connections. Before you begin the procedure for editing a cross connection, the entries in the CP list must be up to date. If you attempt to change a cross connect and you select CPs which are in fact no longer in the node because they were on equipment which has been removed from the rack, the change will fail. Select Data Refresh from Node in order to make sure that you have the latest data. " To edit a cross connection, follow the procedure below: 1. Select Configure Cross Connections. The Cross Connection window appears. 2. Select the level type (VC4, VC3, VC2, or VC12) by clicking on the appropriate tab. 3. Select the cross connection you want to edit in the list box. (You can also select more than one cross connection, which you can edit together as a group.) 4. Click on the Edit button in the Cross Connection window. The Edit Cross Connections dialog box appears, showing details of the selected cross connection (Figure 12-7):
C33543002SE_01
12-11
Figure 12-7
Edit Cross Connections dialog box
5. Click in the Connection Name edit field, if you want to change the name of the cross connection and type in a new name. The name can be up to 15 alphanumeric characters long. 6. Select a new CP from either the CP1 or the CP2 group box, if you want to change either CP used in the cross connection. 7. If you are making a VC12 cross connection, and you want to protect the cross connection, follow the instructions in Section 12.6. (Protection is not available for VC4, VC3, or VC2 cross connections.) 8. If you want to change the switching criteria, follow the instructions in Section 12.6. (If you want to remove a force, either to Protected or to Protecting, you can make the change only if the protected CP is present.)
12-12
C33543002SE_01
9. Click on Next if you want to edit the next cross connection in the current Cross Connection window. The previous change will appear in the Cross Connection window, but they will not take effect until you next send the window data to the node (see step 10.). If you do not want to edit any other cross connections in the node, click on OK. If you click on Next, the Edit Cross Connections dialog box will be filled in with the details of the next cross connection as read from the current Cross Connection window. Refer to the beginning of this Section for details on how to edit a cross connection. If you click on OK, the Edit Cross Connections dialog box will disappear. The Cross Connection window will be updated with the edited cross connection. 10. Select Data Send to Node to send the contents of the window to the node.
12.6 Protecting Cross Connections

If security is enabled, you must hold at least user access level 3 (NMS10 Experienced) (see Chapter 15) to be able to edit protection for cross connections. Protection is available only for VC12 cross connections. Before you begin the procedure for protecting a VC12 cross connection, the entries in the CP list must be up to date. If you attempt to change a cross connect and you select CPs which are in fact no longer in the node because they were on equipment which has been removed from the rack, the change cross connect will fail. Select Data Refresh from Node in order to make sure that you have the latest data. 12.6.1 Signals which can be used for protection Only STM-1 signals can be used for protection. 2M interfaces are not used for path protection: they can only be selected as the reliable CP. " To protect a cross connection, follow the procedure below: 1. Select Configure Cross Connections. The Cross Connection window appears. 2. Select the VC12 level by clicking on the VC12 tab.
C33543002SE_01
12-13
3. Press either Add (see Section 12.4) or Edit (see Section 12.5). The procedure for protecting a cross connection is the same whether you are adding a new cross connection or editing an existing cross connection. 4. Select the cross connection which you want to protect. 5. In the Protecting CP group box, which will have its list box and group boxes greyed out, click on the Protect check box. 6. Select a CP to be the protecting CP. 7. In the Protecting radio button group box, select protection for one of the CPs in the cross connection by clicking on the appropriate radio button. 8. In the Switching criteria radio button group box (see Figure 12-7), select the switching behaviour of the cross connection protection: S Click on Automatic Switching if you want the connection to be automatically switched to the other CP when the active CP becomes unavailable. Click on Forced to Protected CP if you want to force the connection to always be with the protected CP, even if this CP becomes unusable. The protected CP must be physically present in the node. Click on Force to Protecting CP if you want to force the connection to always be with the protecting CP, even if this CP becomes unusable. Click on APS Notifications if you want an event to be raised when the protected cross connection switches. Note that this feature is only available in SAN C2.0 Manager and above.
9. Click on OK. The Add or Edit dialog box will disappear and the Cross Connection window will be updated to show the protection details for the selected cross connection. 10. Select Data Send to Node to send the contents of the window to the node. 11. Select Data Refresh from Node to update the window.
12-14
C33543002SE_01
12. The Cross Connection window will display the updated information. Any protected cross connections will have the alarm status for the path indicated by a Protection Group block, as shown in Figure 12-8. Note The symbol of a letter A in a circle next to a CP indicates that it is the Active of the two unreliable CPs (that is, Automatic switching is selected), and the letter F in a circle indicates that the cross connection is forced to that CP (Forced switch is selected).
Figure 12-8
Protected Cross Connections
12.7 Unprotecting Cross Connections

If security is enabled, you must hold at least user access level 3 (NMS10 Experienced) (see Chapter 15) to be able to unprotect cross connections. " To unprotect a cross connection, follow the procedure below: 1. Select Configure Cross Connections. The Cross Connection window appears. 2. Select the VC12 level by clicking on the VC12 tab.
C33543002SE_01
12-15
3. Select the protected cross connection you want to unprotect in the list box. The cross connection will appear in reverse video as shown in Figure 12-9.
Figure 12-9
Window with a cross connection selected
4. Click on Edit... The Edit Cross Connections dialog box appears (see Figure 12-7). 5. Uncheck the Protect check box. The Unprotect dialog box appears as shown in Figure 12-10.
Figure 12-10 Unprotect dialog box
12-16
C33543002SE_01
6. In the Remove radio button group box, remove one of the protecting cross connections: S S Click on the Protected CP radio button to make the protecting CP become CP1 in the unprotected connection. Click on the Protected CP radio button to make the protected CP become CP1 in the unprotected connection.
7. Click on OK. The Unprotect dialog box will disappear and the Cross Connection window will be updated to show that protection has been removed for the selected cross connection. 8. Select Data Send to Node to send the contents of the window to the node.
12.8 Deleting Cross Connections

" To delete a cross connection, follow the procedure below: 1. Select Configure Cross Connections. The Cross Connection window appears. 2. Select the level type (VC4, VC3, VC2, or VC12) by clicking on the appropriate tab. 3. Click on the cross connection that you want to delete. 4. Click on the Delete button. A message will be displayed as shown in Figure 12-11, asking you to confirm that you want to delete the cross connection.
Figure 12-11 Delete cross connection confirmation message 5. Click on Yes if you want to delete the cross connection.
C33543002SE_01
12-17
6. If you want to delete more cross connections, repeat steps 1. to 5. for each one. (You can select more than one cross connection and delete them in one operation.) When you confirm each deletion (see step 5.), the selected connections are deleted from the Cross Connection window. 7. Select Data Send to Node to send the contents of the window to the node.
12.9 Printing Cross connections

" To print some or all of the data in the Cross Connection window, select Data Print... The Print Cross Connections dialog box (Figure 12-12) appears.
Figure 12-12 Print Cross Connections dialog box Choose which data to print out by checking the boxes for the details which you want. In the example shown in Figure 12-12, only the VC4 cross connections box has been checked, so only the details of VC4 cross connections will be printed out.
12-18
C33543002SE_01
Chapter 13 Using files to save and load data

About this chapter This chapter describes how to save data to file and load data from file. This chapter contains information on:
D D D D D
saving data in a window as text (Section 13.1 ) saving the whole node (Section 13.2) saving part of a node configuration to file (Section 13.3) saving the data in a particular window (Section 13.4) loading data from file (Section 13.5).
Saving data in a window as text You can save the data from any window which is printable (see Chapter 17) as a text file. This is useful for passing on the details of the window to colleagues who do not have access to a printer. Saving data from a node You can use this feature in three ways:
D D D
for copying configurations from one node to another to use an existing configuration as the basis of a more complex configuration as a simple way of backing up configurations.
This chapter assumes that you have successfully started the SAN C2.0 Manager and connected to a node, as described in Chapter 6.
C33543002SE_01
13-1
13.1 Saving data in a window as text

" To save the data in a window as text: 1. Select Data Save As... The Save As dialog box is displayed as in the example shown in Figure 13-1.
Figure 13-1
Save As dialog for saving data as text
2. If you want, change the filename and the directory in which the file will be saved. 3. When the details in the Save As window are as you want them, click on Save. The data has now been saved as a .TXT file, which you can open and print in the usual way.
13.2 Saving the whole node

" To save the configuration details of the whole node: 1. Close all windows except the Node Subrack window. 2. Select Data Save to File... The Save Configuration Data window will be displayed as shown in Figure 13-2. Note that the Save All box is checked, and all the other check boxes are greyed out. Do not change these settings if you want to save the whole node.
13-2
C33543002SE_01
Figure 13-2
Save Configuration Data window
3. Click on OK. The Saving Configuration Data window will be displayed (Figure 13-3).
Figure 13-3
Saving Configuration Data window
When the node manager has read all the data to be saved from the node, the Saving Configuration Data window will be closed and the Save As window will be displayed (Figure 13-4).
C33543002SE_01
13-3
4. Enter a file name in the File name: field. The file extension .SNM will be added automatically.
Figure 13-4
Save As window
The File version: and Date: fields are filled in automatically. The Last edited by: and Reason for Saving Configuration fields are optional, but you are recommended to fill them in so that there is a record of who saved the configuration and why. Caution You must enter a file name (or select an existing file name) before you enter a name in the Last edited by: field. If you enter the name of the person editing the file first, it will be deleted automatically when you choose the file name.
5. When the details in the Save As window are as you want them, click on Save. The details of the configuration of the whole node have now been saved under the file name which you specified in Step 4.
13-4
C33543002SE_01
13.2.1 Details not saved Some details of the node configuration are not saved, either because they must not be copied from one node to another (such as the System ID), or because they consist of short-term information (such as current alarms). The details which are not saved are:
D D D D D D D D
System ID Software Settings Maintenance State Current Alarms the contents of the Event History Log Real Time Clock Current Performance Performance History.
13.3 Saving part of a node configuration to file

" To save part of a node configuration to file: 1. Close all windows except the Node Subrack window. 2. Select Data Save to File... The Save Configuration Data window will be displayed as shown in Figure 13-2. 3. Clear the Save All check box. 4. Check the boxes for the details which you want to save. (The Subrack details are always saved, so the Subrack check box is always checked and greyed out.) In the example shown in Figure 13-5, the details of the External Alarms, Event History Log, and Node Settings will be saved.
C33543002SE_01
13-5
Figure 13-5
Saving part of the configuration data
5. Carry out Step 3. to Step 5. from Section 13.2. The procedure is the same, except that you will have saved only part of the configuration data which you specified.
13.4 Saving the data from a window

You can save the data from the following configuration windows to file. You can save them individually or in combination in a new .SNM file or within an existing .SNM file.
D D D D D D D
Transmission cards (see the appropriate chapter: for example Configuring SAN 2M interface units) Cross Connections (see Chapter 12) Auxiliary Connections (see Chapter 6) Synchronisation (see Chapter 7) External Alarms (see Chapter 14) Event History Log settings (see Chapter 14) Node Settings (see Chapter 5).
13-6
C33543002SE_01
" To save the data in a window: 1. Open the configuration window whose data you want to save, carry out any edits which you want to make, and send the data to the node. 2. Select Data Save to File... The Save As window will be displayed (Figure 13-4). 3. Carry out Step 4. to Step 5. from Section 13.2. The procedure is the same, except that you will have saved only the configuration data in the window which was open.
13.5 Loading data from file

You can load data from a file into a node which has already been installed (see Chapter 5). 13.5.1 Loading a whole node configuration from file Caution You can load a whole node configuration only into a node with the same number of slots as the node from which the configuration was originally saved.
" To load a whole node configuration from file: 1. Select Data Load from File... The Open window will be displayed (Figure 13-6).
C33543002SE_01
13-7
Figure 13-6
Open window
2. Select the file which you want and click on Open.The Node Information dialog box (Figure 13-7) will be displayed, which is the first dialog box of the Whole Node Load Wizard.
13-8
C33543002SE_01
Figure 13-7
Whole Node Load Wizard, Node Information dialog box
3. Change the name of the node in the Name: edit field, and the location of the node in the Location: edit field, if required. This depends upon whether you are recreating a node, or copying or cloning another node. 4. Click on Next>. The Subrack Information dialog box (Figure 13-8) of the Whole Node Load Wizard is displayed.
C33543002SE_01
13-9
Figure 13-8
Whole Node Load Wizard, Subrack Information dialog box
5. All the fields in this window are read-only. The SAN C2.0 Manager enters the details for you automatically. 6. Click on Next>. The Node Address dialog box (Figure 13-9) of the Whole Node Load Wizard will be displayed.
13-10
C33543002SE_01
Figure 13-9
Whole Node Load Wizard, Node Address dialog box
7. Select a name for the area to which the node is to belong, from the list in the Name: drop-down list. If the area name which you want does not appear in the list, click on Search Database... The Select Area dialog box will be displayed (Figure 13-10).
Figure 13-10 Select Area dialog box You can use the Select Area dialog box to add a new area or edit an existing area. When you have finished, click OK to return to the Whole Node Load Wizard.
C33543002SE_01
13-11
8. Enter the System ID of the node in the System ID: edit field. 9. Click on Next>. The Configuration Data dialog box (Figure 13-11) of the Whole Node Load Wizard is displayed.
Figure 13-11 Edit Whole Node Load File Configuration Data wizard, screen 4 10. If you do not want to load all the details which were saved, clear the boxes for the data which you do not want. For example, in the configuration shown in Figure 13-11, you could clear the Cross Connections box if you did not want to load the cross connections details. You cannot choose not to load the Subrack details, so the Subrack box is always selected and greyed out. Any details which were not saved in the configuration are also greyed out. Selecting a check box may cause another box to be selected automatically. For example, if you select Cross-Connections, the Transmission Cards box will be selected automatically, because the SAN C2.0 Man-
13-12
C33543002SE_01
ager cannot load the details of the cross connections unless it loads the details of the transmission cards as well. 11. When the details are as you want them, click on Finish. The Loading Configuration Data window is displayed (Figure 13-12).
Figure 13-12 Loading Configuration Data window The SAN C2.0 Manager begins loading all the data from the file, starting with the Subrack details, and sends it to the node to which it is connected. When the data has been sent, the Loading Configuration Data window closes and the Node Subrack window is displayed. The loading of the node configuration is now complete and the node is ready for use. 13.5.2 Loading a window configuration from file " To load a configuration from file: 1. Open the window into which you want to load the configuration details (for example, open the Cross Connection window if you want to load details of a set of cross connections). 2. Select Data Load from File... The Open window will be displayed
(Figure 13-6).
If you are opening a file containing cross-connection data, the Load Cross-Connection dialog box (Figure 13-13) will be displayed asking
C33543002SE_01
13-13
you whether you want to overwrite the current cross-connections, or merge them with (add them to) the current cross-connections.
Figure 13-13 Load Cross-Connections dialog box 3. Select the configuration file which you want and click on Open. The Choose Block Type window is displayed (Figure 13-14).
Figure 13-14 Choose Block Type window 4. Select the block type which you want. (It should match the type of the window which is currently open. For example, Figure 13-14 shows a file which was saved from a Cross Connection window. You should open this file only when a Cross Connection window (Figure 12-4) is open. 5. Click on OK. The configuration will be loaded into the window.
13-14
C33543002SE_01
C33543002SE_01
13-15
13-16
C33543002SE_01
Chapter 14 Managing alarms

About this chapter This chapter describes how to use the SAN C2.0 Manager to manage alarms on a SYNFONET Access Node. This chapter contains information on:
D D D D D
Alarm information (Section 14.1) Visual alarm notification (Section 14.2) Configuring external alarms (Section 14.3) Configuring station alarms (Section 14.4) Event history logs (Section 14.5).
This chapter assumes that you have successfully started the SAN C2.0 Manager and accessed a node, as described in Chapter 6. Related information Refer to the Commissioning and Maintenance Section of the SAN Operating Manual for a full description of the alarms displayed by the SAN C2.0 Manager. Refer to Chapter 16 for information on performance monitoring and performance history. Refer to the Node Manager Options window (accessed by Node Manager Options) to enable or disable Auto Refresh. See Section 6.5.
C33543002SE_01
14-1
14.1 Introduction
A large number of different alarms can be generated by a node. For any alarm that has occurred on a node, the SAN C2.0 Manager can provide the following information about the alarm:
D D D D
A descriptive text message about the alarm The severity of the alarm The classification of the alarm The time and date that the alarm occurred, if known. (This information is only available for alarms recorded in an Event History Log.)
Along with a text message describing the alarm that occurred and the time of its occurrence, each alarm is graded to help identify how severe the alarm is and also classified to indicate the possible cause of the alarm. These different types of alarm information are described in the next few Sections. 14.1.1 Descriptive text message of alarm The descriptive message about the alarm that has occurred is displayed in one of two forms depending on where the message is displayed. The two forms are:
D D
Micro Long
To save space, the micro form of alarms are displayed in the configuration windows of units, and on the Status bar of the application window. Long form alarms are displayed in the Current Alarm List window, the Block Status window and the Event History Log window. For any alarm that can be displayed by the SAN C2.0 Manager, the two forms of the alarm give progressively more information about the alarm and from where it was generated. For example, if a signal is lost on the OS1 block of an STM1 unit located in slot 1 of the subrack, the long form alarm text message would be:
14-2
C33543002SE_01
Loss of Signal
U1 STM1i/f:2 OS1
The micro form of this message would be: LOS
C33543002SE_01
14-3
A list of alarms in their Micro and Long forms is given in Table 14-1, Table 14-2, and Table 14-3.
Micro AIR AIR AIR AIS BATT BATT BATT BKUP CABL CMPF CMPF COMM CONF DEG DETE DOOR E0 EBOF ENG EXC FAIL FAN FAN FIRE FLOOD FORC FORC FORC FORC FORC Long Air Compressor Failure Air Conditioning Failure Air Dryer Failure Alarm Indication Signal (not an alarm, shown only in Block Status windows) Battery Discharging Battery Failure Low Battery Threshold Backup Fail Low Cable Pressure Compatibility Failure Compatibility Proposal Failure Communications Subsystem Failure Configuration or Customisation error Degraded Signal Fire Detector Failure Enclosure Door Open Indeterminate Event Buffer Overflow Engine Failure Excessive BER Unit Fail Cooling Fan Failure Critical Fan Failure Fire Flood Synchronisation forced High Order Path Protection forced Lower Order Path Protection forced Laser Forced Off Laser Forced On
Table 14-1
Alarm text meanings (continues on next page)
14-4
C33543002SE_01
Micro FUEL FUSE GAS GAS GENR HUMI HUMI ICE INTR LGOF LPPF LOF LOP LOS LTI LTRE MAIN MISM MISS PLM POW POW PROT PUMP RECT RDI SMOK SSF TEMP TEMP TEST
Long Low Fuel Fuse Failure Explosive Gas Toxic Gas Generator Failure High Humidity Low Humidity Ice Buildup Intrusion Detection Log Overflow Lower Order Path Protection Failure Loss Of Frame Loss Of Pointer Loss Of Signal Loss of Timing Information Local Node Transmission Error Maintenance State Unit Mismatch Unit Missing Payload Mismatch Commercial Power Failure Power Problem Communications Protocol Error Pump Failure Rectifier Failure Remote Defect Indication (not an alarm, shown only in block status win dows) Smoke Server Signal Fail High Temperature Low Temperature In Test
Table 14-2
Alarm text meanings (continues on next page)
C33543002SE_01
14-5
Micro TIM UNEQ WIND VOLT VOLT VENT
Long Trace Identifier Mismatch Unequipped High Wind Rectifier High Voltage Rectifier Low Voltage Ventilation System Failure
Table 14-3
Alarm text meanings (continued)
14.1.2 Time and date of alarm occurrence The time and date an alarm occurred is displayed using the time and date format defined in the Windows Control Panel (described in the Microsoft Windows User s Guide). This information is used by the Event History Log to record when alarms occur on the node. To change either the time or date format, use the International or Regional option from the Windows Control Panel. 14.1.3 Alarm classification To indicate the possible cause of an alarm it is classified according to its type. Alarm types indicate what general subject area an alarm is associated with. Table 14-4 lists all the different types of alarms which can be generated by a SYNFONET Access Node and displayed by the SAN C2.0 Manager.
Alarm type COMMS PROCESSING EQUIP ENVIRONMENT Definition Transmission failure Software and processor failure Equipment failure Environmental failure, i.e. ice, flood, fire etc.
Table 14-4
Alarm types
14-6
C33543002SE_01
14.1.4 Alarm severity To identify how severe an alarm is, it is graded according to its severity. The different severities of alarms are listed in Table 14-5.
Alarm severity CRITICAL Definition The most severe alarm. It signifies that a serviceaffecting condition has occurred and an immediate corrective action is required. Signifies that a serviceaffecting condition has occurred and urgent corrective action is required. Indicates the existence of a nonservice affecting fault condition and that corrective action should be taken in order to prevent a more serious fault. Indicates the detection of a potential or impending serviceaffecting fault, before any significant effects have been felt. Action should be taken to further diagnose and correct the problem in order to prevent it from becoming a more serious service affecting fault. Indicates the clearing of one or more previously reported alarms.
MAJOR
MINOR
WARNING
CLEARED
Table 14-5
Alarm severities
C33543002SE_01
14-7
14.2 Visual alarm notification

There are six different locations where the alarms on a currently managed node can be viewed using the SAN C2.0 Manager. Each location provides more of the available alarm information described in Section 14.1. The locations are:
D D D D D D
Alarm Status area of the status bar Node Subrack window
Editable windows, including the Synchronisation window and all types of Configure windows The Block Status window
Current Alarm List window and nodebased Event History Log
window The Cross Connection window (for protected cross connections)
14.2.1 On the status bar The righthand side of the status bar in the application window contains the Alarm Status field, which displays the most severe alarm for the node that is currently being managed. The descriptive message about the alarm is given in its short form. The message is displayed on a coloured background (grey scale for monochrome monitors) to indicate the severity of the alarm. Table 14-6 shows the meaning of each displayed colour/shade of grey in terms of alarm severity. Refer to Section 14.1 for a definition of the different severities of alarm. If more than one alarm of equal severity exists on the node, the alarm which was first received by the SAN C2.0 Manager will be displayed. If no alarms are present on the node, an empty green block (white for monochrome monitors) will be displayed in the Status bar. Updating of the alarm information The Alarm Status field can be regularly updated while the node is being managed by using the Auto Refresh option. This ensures that
14-8
C33543002SE_01
you are always aware of the most serious alarm on the node and you are quickly warned when a serious alarm occurs on the node. 14.2.2 On the Node Subrack window The Node Subrack window (described in Section 4.2.2) contains information about the most severe alarm present on each unit installed in the node. The colour of the square containing the slot number (grey scale for monochrome monitors) indicates the most severe current alarm associated with the unit in the slot. Figure 14-1 shows a typical Node Subrack window.
Figure 14-1
Node Subrack window
Alarm severity Colour CRITICAL MAJOR MINOR WARNING CLEARED or No alarms Red Orange Yellow Blue Green
Definition Grey scale Dark grey Dark grey Dark grey Light grey White
Table 14-6
Alarm severity colour classification
C33543002SE_01
14-9
Table 14-6 shows the meaning of each displayed colour/shade of grey in terms of alarm severity. Refer to Section 14.1 for a definition of the different grades of alarm severity. Updating of the alarm information The Node Subrack window can be regularly updated while the node is still being managed by using the Auto Refresh option. This ensures that you are always aware of the severity of the most serious alarm on each unit in the node and you are quickly warned when a serious alarm occurs on a unit. You can set Auto Refresh to be enabled automatically whenever you open the Node Subrack window by using the Polling window of the Manager Options menu (see Section 6.5). 14.2.3 Windows which display alarm information The windows which display alarm information are:
D D D D
Synchronisation Configuration window 2M Configuration windows All types of STM1 Configuration windows Cross Connection window
Synchronisation window To view the current alarms which are associated with the synchronisation node selector, select Configure Synchronisation The Synchronisation window contains information about the most severe alarm associated with the node. See Figure 14-2. The background colour (grey scale for monochrome monitors) of the alarm field indicates the severity of the alarm. If no alarm is present on the node synchronisation, the field is empty and filled with green (white for grey scale monitors) If no alarm has been received from the node, the field is empty and filled with the background colour of the Synchronisation window.
14-10
C33543002SE_01
Figure 14-2
Configure Synchronisation window
For more information on node synchronisation, and the alarms which can be displayed in the window, refer to Chapter 7. 2M and STM1 configuration windows 2M and STM1 configuration windows contain information about the most severe alarm associated with each functional block contained in the unit. " To view the current alarms that are present on the functional blocks of a 2M or STM1 unit, follow the procedure below: 1. Select the unit in the Node Subrack window. 2. Select Configure Interface. The Configuration window for the unit selected in the Node Subrack window appears, showing details about the unit, down to the functional block level. The most severe current alarms associated with each functional block are displayed for each block.
C33543002SE_01
14-11
Figure 14-3 shows the location of the alarm areas for the functional blocks contained in a typical STM1 configuration window.
Figure 14-3
Configure STM1 window with alarm information
For each functional block, the following alarm information is displayed in the window:
D D
the abbreviated form of the alarm text message. a colour (grey scale for monochrome monitors) indicating the severity of the alarm
For more information on configuring all types of STMN units, refer to Chapter 9, and for CORE2M units, refer to Chapter 8. 14.2.4 On the Block Status window To view the current alarms that are present on the node in more detail, you can view the alarms by functional block. " To view the block status, follow the steps below: 1. Click on the unit you want to view in the Node Subrack window. 2. Select Configure Interface. The Configuration window for the unit selected in the Node Subrack window will be displayed, showing details about the unit, down to the functional block level. In the Configuration window, the most severe current alarm is shown in its abbreviated form for each functional block in the unit. 3. Click on a functional block in the Configuration window. 4. Select Monitor Block Status.
14-12
C33543002SE_01
The Block Status window for the selected block will be displayed. See Figure 14-4.
Figure 14-4
Block Status window
Updating of the alarm information While it is being viewed, the Block Status window can be regularly updated with any new alarms that occur on the node by checking Auto Refresh. Alarms which are cleared will be removed from the window. 14.2.5 On the Current Alarm List window To view the current alarms that are present on the node in more detail:
D D D
Select Monitor Current Alarms, or click on the type

CTRL
icon in the Toolbar, or
+A
Any of these actions will cause the Current Alarm List window to be displayed, showing all the alarms which are currently present on the node. A typical Current Alarm List window is shown in Figure 14-5:
C33543002SE_01
14-13
Figure 14-5
Current Alarm List window
Alarms are displayed in the window one per line, most recent at the top (unless you have sorted the list manually; see below). Each line contains the severity and classification of the alarm followed by the long form of the descriptive text message about the alarm. Note Although the Current Alarm List window does not give you the date and time when the alarm occurred, you can obtain this information by setting up an Event History Log. For more information, refer to Section 14.5.
Sorting the alarm information in the Current Alarm List To sort the alarms in the Current Alarm List window, either click on the right mouse button or press SHIFTF10. A popup will appear as shown in Figure 14-6.
14-14
C33543002SE_01
Figure 14-6
Alarm sort popup
Each of the three options applies to one of the columns: Severity, Type, and Alarms. Select the appropriate option either with the mouse or with the arrow keys, and then either click on it or press RETURN. Updating of the alarm information While it is being viewed, the Current Alarm List window will be dynamically updated with any new alarms that occur on the node. Alarms which have been cleared will be removed from the window. 14.2.6 On the Cross Connection window Alarm status information related to the path of protected cross connections is displayed on the Cross Connection window. The colour indicates the alarm status for the most severe alarm involved in the path. Either when adding a new protection path using the Add Cross Connection window or when editing a cross connection that has a protection path using the Edit Cross Connection window, click on the APS Notifications check box to enable or disable the notification. If enabled, any alarm event related to the concerned protection path will be displayed in the Current Alarm List window.
C33543002SE_01
14-15
Figure 14-7
Protected Cross Connections
14.3 Configuring external alarms

If security is enabled, you must hold at least user access level 3 (NMS10 Experienced) (see Chapter 15) to be able to configure external alarms. The SYNFONET Access Node node can process four external alarms. The cause, severity and text can be specified from the External Alarms And Station Alarms window. " You can use the SAN C2.0 Manager to enable or disable the use of external alarms on the node subrack: 1. Select Configure External Alarms. The External Alarms And Station Alarms window appears (Figure 14-8).
14-16
C33543002SE_01
Figure 14-8
External Alarms And Station Alarms window
The current state of the alarm is indicated by the leftmost field. The Indication field has two possible values: Status (which is reported only in this window) or Alarm (which is also reported in the Current Alarm List window and the Event History Log window). 2. Select a level for the alarm from the Severity dropdown list box. 3. Select an entry for the alarm from the Probable Cause dropdown list box. 4. Enter a description in the Additional Text Field. 5. Select Data Send To Node to send the new setup to the node. Note Note The Polarity field allows you to choose whether the alarms are raised for high or low logic inputs. If you change the information for an external alarm while it is raised, the alarm information in the current alarm list is not changed, but alarms raised after the change will show the changed information.
C33543002SE_01
14-17
14.4 Configuring station alarms

If security is enabled, you must hold at least user access level 3 (NMS10 Experienced) (see Chapter 15) to be able to configure station alarms. The rack containing the currentlymanaged node displays station alarms which correspond to the current alarms that are present on the node. Station alarms are shown by rack alarm lamps on the Rack Power Interface Unit (RPIU) or DCPSA, and also as relay contact signals. Station alarms appear only if station alarms are enabled (see Section 14.4.1). There are two sources from where station alarms can be obtained:
D D
Rack Power Interface Unit (RPIU) lamps (when RPIU feeding is used) or DCPSA Relay outputs from each subrack and RPIU (if connected)
For more information on station alarms, refer to the SYNFONET Access Node Operating Manual. 14.4.1 Enabling or disabling station alarms You can use the SAN C2.0 Manager to enable or disable the use of station alarms on the node: " To enable or disable the use of station alarms: 1. Select Monitor External Alarms. The External Alarms and Station Alarms window appears. 2. In the Station Alarms group box (see Figure 14-9), click on the Enabled check box to enable or disable station alarms.
14-18
C33543002SE_01
Station Alarms check box
Figure 14-9
Station Alarms check box
3. Select Data Send To Node to send the new setup to the node.
14.5 Using the Event history log

The event history log is a file that is stored in memory on a node. It is used to record information about:
D D
alarms that have been generated by the node alarms that have been cleared on the node
Initially, a node is configured to use Event History Logs, but if you want you can prevent Event History Logs from being created. Refer to the next Section for details. 14.5.1 Viewing Viewing the event history log file " To view the event history log file for the currently managed node: 1. Select Monitor Event History Log.
C33543002SE_01
14-19
2. The Event History Log window will be displayed, showing the alarms which have been generated by the node, including those which have been cleared (Figure 14-10).
Figure 14-10 Event History Log window Note If the log file contains many stored alarms, the window may take some time to be displayed by the SAN C2.0 Manager. A progress bar will be displayed to keep you informed while this is happening.
The alarms are displayed exactly as they would be displayed in the

Current Alarm List window, except that the time and date the alarm
occurred is also given. Alarms are displayed in the window one per line, the most recent at the top. Each line contains the time and date, severity and classification of the alarm followed by the long form of the descriptive text message about the alarm. Cleared alarms appear in the Event History Log window but not in the Current Alarm List window. For more information on the alarm information displayed in the window, refer to Section 14.1.
14-20
C33543002SE_01
Sorting the event information in the event history log To sort the events in the Event History Log window, either click on the right mouse button or press SHIFTF10. A popup will appear as shown in Figure 14-11, or click on the column heading.
Figure 14-11 Event sort popup Each of the four options applies to one of the columns: Time, Severity, Type, and Alarms/Events. Select the appropriate option either with the mouse or with the arrow keys, and then either click on it or press RETURN. 14.5.2 Setting up the event history log file If security is enabled, you must hold at least user access level 2 (NMS10 Basic) (see Chapter 15) to be able to set up an event history log. " To set up an event history log file for the currentlymanaged node: 1. Select Monitor Event History Log. 2. Click on Set Up.... 3. The Set Up Event History Log dialog box appears (Figure 14-12):
C33543002SE_01
14-21
Figure 14-12 Set Up Event History Log dialog box 4. Check the Enabled check box in the Data Collection group box. 5. Select Wrap or Halt from the Full Action radio button group box, depending on what you want to happen to the event history log file when it becomes full: S S
Wrap starts to overwrite the log file from the beginning with
new alarms
Halt stops appending new alarms to the log file
6. Click on OK. From now on, any new alarms generated by the node will be saved on the node in the event history log file. For information on viewing the log file, refer to Section 14.5.1. 14.5.3 Updating To update the contents of the Event History Log window, click in the window to make it the currently active window and choose Data Refresh from Node. The SAN C2.0 Manager will re-read the alarm information from the node and update the window with any new alarms which have occurred or any alarms which have been cleared, since the node was last read. 14.5.4 Clearing If security is enabled, you must hold at least user access level 2 (NMS10 Basic) (see Chapter 15) to be able to clear the event history log. " To clear the event history log file:
14-22
C33543002SE_01
1. Choose Monitor Event History Log. 2. Check the Clear Log check box. 3. Choose Data Send To Node. The event history log file will be cleared of all information. The configuration settings for the log file will be retained. 14.5.5 Disabling If security is enabled, you must hold at least user access level 2 (NMS10 Basic) (see Chapter 15) to be able to disable the event history log. " To disable the event history log file: 1. Choose Monitor Event History Log. 2. Click on Set Up.... 3. The Set Up Event History Log dialog box appears. (Figure 14-12). 4. Clear the Enabled check box in the Data Collection group box. 5. Click on OK. For information on enabling the log file again, refer to Section 14.5.2.
C33543002SE_01
14-23
14-24
C33543002SE_01
Chapter 15 Security
About this chapter This chapter describes the security features which are available. Note The security features are not available if the SAN C2.0 Manager has been installed under Windows 95.
This chapter contains information on:

D D D D
security principles in SYNFONET Access Node (Section 15.1) security as seen by the user (Section 15.2) user access levels (Section 15.3) security administration (Section 15.4)
15.1 Security principles in SAN

The SAN C2.0 Manager running under Windows NT offers a security feature, which the system administrator can choose to enable. A system administrator is someone who is registered in Windows NT as an administrator (see the Windows NT glossary in the Windows NT user manual or help file). System administrators are users who have rights to make administrative changes to the system.
C33543002SE_01
15-1
If security is enabled, the system administrator can control which users can make particular types of change to nodes. Users privileges to make particular types of change are divided into five user access levels (see Section 15.3). A users access level is set by the system administrator.
15.2 Security as seen by the user

As a user, you may be allowed to carry out a range of editing functions, depending upon your user access level. The system administrator controls what your user access level is. Controls which are not available for a user to edit because of too low an access level are greyed out (see Section 4.4.3). If you want to be able to make this type of change to the node, ask your system administrator to raise your user access level.
15.3 User access levels

There are five user access levels, which are set by the system administrator. The prefix NMS10 is necessary in order to maintain compatibility with the NMS/10 network management system (see Appendix D). NMS10 Operator - Level 1 Operators can read data from the node, but cannot edit any settings on the node. Operators can add nodes to the PC address database and delete nodes from the PC address database. They can also print data and save data to a PC. NMS10 Basic - Level 2 Basic users can can enable and disable collection of performance data for transmission interfaces. Basic users can also clear Current Performance data and delete Performance History records. NMS10 Experienced - Level 3 Experienced users can edit transmission-related variables within an existing network such as cross-connections and interfaces. Experienced users can also configure external alarms and station alarms.
15-2
C33543002SE_01
NMS10 Network Administrator - Level 4 Network Administrators can change node addresses and install and uninstall nodes. Network Administrators can also configure synchronisation and edit the DCN network. System Administrator - Level 5 System Administrators manage access rights. The rest of this chapter is for system administrators only. It deals with features and procedures to which ordinary users do not have access.
15.4 Security administration

If you are a system administrator, you can:
D D
enable security when the SAN C2.0 Manager is installed set, raise, or lower a user s access level
You need to be familiar with Windows NTs own security features in order to act as a system administrator for SAN C2.0 Manager. 15.4.1 Enabling security at installation You can enable or disable security when you install SAN C2.0 Manager under Windows NT. For instructions, see Chapter 3. 15.4.2 Setting a users access level " To set a user s access level: 1. If you are using Windows NT 3.51, select FileRun... in Program Manager.. Enter MUSRMGR.EXE and press RETURN. Alternatively, double-click on the User Manager icon in the Administrative Tools group. If you are using Windows NT 4.0, click on the Start button and select
ProgramsAdministrative Tools (Common)User Manager.
2. If you are adding a new user, select New User... from the User menu. If you want to change the access level of an existing user, select that user s name from the list.
C33543002SE_01
15-3
3. Select Properties... from the User menu. Click on Groups.The Group Memberships dialog box will be displayed as shown in Figure 15-1. If you are adding a new user, the four user access levels will already be listed in the Not member of: list box. If you are editing the access level of an existing user, their current user access level will be shown in the Member of: list box.
Figure 15-1
Group Memberships dialog box
4. If you are adding a new user, select the user access level which you want to assign from the Not member of: list box and then click on <-Add. Click on OK. 5. If you are editing the access level of an existing user, select their current access level from the Member of: list box and then click on Remove->. Select the user access level which you want to assign from the Not member of: list box and then click on <-Add. Click on OK.
15-4
C33543002SE_01
Chapter 16 Performance monitoring

About this chapter This chapter describes how to view and configure performance monitoring for a node. This chapter assumes that you have successfully started the SAN C2.0 Manager and accessed a node, as described in Chapter 6.
16.1 Introduction
The performance windows provide the current and historical error performance on functional blocks within a SYNFONET Access Node node. Performance information is available as absolute counts or as ratios. Related information Refer to Chapter 14 for information on viewing current alarms and alarm history.
16.2 Configuring performance data collection

Before you can view performance data for a unit, you must first enable the collection of the data by configuring the performance attributes. If security is enabled, you must hold at least user access level 2 (NMS10 Basic) (see Chapter 15) to be able to configure performance data collection. " To configure the performance attributes, follow the steps below:
C33543002SE_01
16-1
1. Doubleclick on the unit you want to configure in the Node Subrack window. 2. Click on the tabbed button for the functional block for which you want to enable data collection. The example shown in Figure 16-1 is for the RS1 block of an STM1 window. Other types of window may offer you different options. Press F1 to obtain contextsensitive help for using that particular window. 3. Click once with the righthand mouse button. The popup menu shown in Figure 16-2 is displayed. 4. Click on Configure. The Configuration window for the unit selected in the Node Subrack window will be displayed, showing details about the unit, down to the functional block level.
Figure 16-1
Example Performance Data collection options
16-2
C33543002SE_01
5. In this example, the Performance Collection group box allows you to choose whether performance data will be collected every 15 minutes, every 24 hours, at both of these intervals, or not at all. To enable or disable either or both of the collection intervals, check the appropriate check box. Click on OK. 6. Click on Data Send to Node.
16.3 Viewing current performance data

" To view the current performance data, follow the steps below: 1. Doubleclick on the unit you want to configure in the Subrack window. 2. Click once with the righthand mouse button on the functional block you want to configure performance for. The popup menu shown in Figure 16-2 is displayed.
Figure 16-2
Menu with performance details options
3. Click on Current Performance. The Current Performance window for the block selected in the Node Subrack window will be displayed, showing details about the performance of the block (Figure 16-3.) Depending on how performance has been configured for the unit, 15 minutes and 24 hours performance information will be displayed for
C33543002SE_01
16-3
the currently chosen interface and functional block within that interface.
Figure 16-3
Current Performance window
The titles in the left column vary according to the options which are in effect. Both possible titles are shown in the explanation below. The meanings of the values are: S S S S S S
Elapsed Time time elapsed from the start of the period. ES/ESR Errored Seconds or Errored Seconds Ratio. SES/SESR Severely Errored Seconds or Severely Errored
Seconds Ratio.
UAS/UASR Unavailable Seconds or Unavailable Seconds
Ratio.
BBE/BBER Background Bit/Block Error or Background Bit/
Block Error Ratio.

Collecting The status of the performance record (OK, Suspect,
Not Collected, or Cleared). OK means that performance data were collected throughout the time period (15 minutes or 24 hours). Suspect means that performance collection was not enabled for part of the time period, so that data was not collected for the whole 15 minutes or 24 hours.
16-4
C33543002SE_01
4. To refresh the contents of the performance window automatically, check Auto Refresh. 5. In the Display group box, select either Counts or Ratios. Changing the display option will change the titles and performance values displayed in the table. The ratio values are based on the available seconds. An example of a Current Performance window with the ratios option enabled is shown in Figure 16-4.
Figure 16-4
Data display using ratios option
The relative values are shown in exponent format in the form x.xxe yy. For example, a ratio of 1/10 000 is shown as 1.00e04. Ratios are shown to three significant figures. If there is no performance data shown for the selected unit, this is because performance data collection has not been enabled. For more information on configuring performance data collection, refer to Section 16.2. To clear the current performance record for data collected at 15minute intervals, click on Clear. To clear the the current performance record for data collected at 24hour intervals, click on Clear. A message box of the type shown in Figure 16-5 will be displayed asking you if you want to clear these records from the node.
C33543002SE_01
16-5
Figure 16-5
Clear current records confirmation message
If you click on OK, the fields are reset. Note After you have cleared a current performance record, you cannot receive any more current performance data until you select Data Refresh from Node.
Select Data Send to Node. The Show History button displays the Performance History window (see Section 16.4).
16.4 Viewing the performance history

Historical performance records are also available. " To view the performance history: 1. Doubleclick on the unit you want to configure in the Node Subrack window. 2. Click once with the righthand mouse button on the functional block you want to configure performance for. The popup menu shown in Figure 16-2 is displayed. 3. Click on Performance History. The Performance History window for the block selected in the Unit window will be displayed, showing details about the performance of the block (Figure 16-6.)
16-6
C33543002SE_01
Figure 16-6
Performance History window
4. Select the 24 hour or 15 min radio button for the performance periods to view. Periods of either 15 minutes or 24 hours performance information will be displayed for the currently-selected functional block. 5. Use the scroll bar to view performance records that are not displayed on the screen. The Record No row identifies the history record number for each column. There can be up to 16 performance history records stored in the node. The End Date and End Time are the date and time for the end of the performance period. The remaining titles have the same meanings as in the Current Performance window (Section 16.3). An end time of 00:00 means a period which was collected the previous day and which ended at midnight. Note The date format in the End Date: field is fixed in the form DD:MM:YY (day-month-year), and the time format in the End Time: field is fixed in the format HH:MM:SS (hour-minute-second).
6. Select the Display option for either counter values or relative ratios. Changing the display option will change the row titles and performance values displayed in the table. The data will be displayed as ratios in the same format as in Figure 16-4.
C33543002SE_01
16-7
To delete a record, click on it anywhere in the data fields. The data fields will then be displayed in reverse video, and the Delete button will be enabled. Click on Delete. A message box of the type shown in Figure 16-7 will be displayed to warn you that these records will not be recoverable if you delete them from the node. If security is enabled, you must hold at least user access level 2 (NMS10 Basic) (see Chapter 15) to be able to delete performance history records.
Figure 16-7
Clear historical records confirmation message
7. Click on OK. 8. Select Data Send to Node. The Show Current button displays the Current Performance window (see Section 16.3).
16-8
C33543002SE_01
Chapter 17 Printing SYNFONET Access Node data

About this chapter This chapter describes how to print the data contained in document windows displayed by the SAN C2.0 Manager.
17.1 Introduction
The contents of every document window displayed by the SAN C2.0 Manager can be printed by choosing Data Print. This command sends the contents of the window to the DEFAULT printer, as configured by the Windows Print Manager. For best performance it is recommended that you should select the Generic/Text Only printer, and that you should set the character width to 80 characters. It is always useful to have a copy of some of the most important configuration data of the node for reference, should anything happen to the node causing a loss of information.
17.2 Setting up the printer

To set up a printer attached to your computer, you need to use the Print Manager. This is an integral part of the Windows operating system software running on your computer. The Print Manager enables you to install and configure printers, connect to network printers and control the printing of data from all
C33543002SE_01
17-1
Windows applications which support printing, including the SAN C2.0 Manager. For more information on using the Print Manager, refer to the Microsoft Windows User s Guide supplied with your computer.
17.3 Printing node data

The window data is printed out in a nonpaginated form. At the start of the printout, the following information is printed:
D D D
the name of the node currently being managed the title of the window being printed the date and time the data was printed (read from the computer).
An example of the printout that would be produced for a typical Node Subrack window is shown in Figure 17-1.
17.4 Printing node data to file

The contents of a window can be saved to file by configuring the printer to print to the FILE port, rather than a printer port such as LPT1. When you next print from the SAN C2.0 Manager, the contents of the window will be sent to a file that you specify. For more information on printing to file, refer to the Print Manager Help file or the Microsoft Windows User s Guide supplied with your computer.
17-2
C33543002SE_01
Local LAN: 39246F000001160000000100010000000000E300 SYNFONET Access Node Manager Subrack 04/03/99 14:03:10 Node type SAN STM1 Node name CBG Node location Milton Road Cambridge Node software SAN C2.0 Node time 04/03/99 13:59:00 Sync source Internal Node address AFI 39 IDI 246F Area 00000116000000010001 System ID 0000000000E3 Nsel 00 Subrack Actual Units: Slot 1 1(PIM) 2 3 4 5 6 7 8 Type Exp (Act) CORE2M STM1 1I/F 345M 2M EOW 2M HW T31491.07 A0 T31491.07 A0 T31450.04 A0 T31420.02 A0 T31460.01 A0 T31420.02 A0 Serial no H974900123 H975000607 30072557 H980800948 H980800200 H980800944 Active SW P31512.60 08 Inactive SW P31512.60 07 SYNFONET ACCESS 4 slots 1 1 1
P31512.70 08 P31512.40 08 P31511.40 22 P31512.40 08
P31512.70 07 P31512.40 07 P31511.40 17 P31512.40 07
Marconi Communications
Figure 17-1
Node Subrack window printout
C33543002SE_01
17-3
17-4
C33543002SE_01
Chapter 18 Downloading software to a network

About this chapter This chapter describes how to use the Network Downloader to download software to up to 100 nodes in a single operation. The Network Downloader is particularly useful, for example, when you are installing a new network or upgrading the software in an existing network. The Network Downloader always downloads software to the inactive bank, so it is impossible for anyone to cause problems on your network by downloading unsuitable software to the active bank of your own nodes.
18.1 Introduction
The Network Downloader is a separate program which is supplied with the new versions of node managers. It appears as an icon on your desktop as shown in Figure 18-1.
Figure 18-1
Network Downloader program icon
If there is no Network Downloader icon on your desktop, you can find the Network Downloader in the folder NWD1.0 as the file NWD.EXE. Network Downloader Help file The Network Downloader has its own help file, which you can use either from the Help item on the menu bar, or by pressing the F1 key. Pressing F1
C33543002SE_01
181

will give you context-sensitive help if it is available for the window which is currently opened and has focus. Initial window When you start the Network Downloader, the initial window is displayed (Figure 18-2).
Figure 18-2
Network Downloader initial window
18.2 Preliminary steps

Before you can download files to a network, you must first set up an output log in which the system will record the progress of the download. You must also select a software directory from which the files will be downloaded.
182
C33543002SE_01
18.2.1 Setting up an Operation Log " To set up an operation log: 1. Select File Operation Log... The Select Operation Log dialog will be displayed (Figure 18-3 shows an example of this window obtained while using operating system: NT Version 4.0 Service Pack 4).
Figure 18-3
Select Operation Log dialog
2. Click the appropriate folder in the Save in list box. 3. Either enter a new filename in the File name: text box, or select an existing file name from the list above it. When you have entered a name for the log, click on Save. 18.2.2 Selecting a software directory " To select a software directory from which to download files to a network: 1. Select File Software Directory... The Select Software Directory dialog will be displayed (Figure 18-4).
C33543002SE_01
183
Figure 18-4
Select Software Directory dialog
2. Either enter a new directory path in text box, or select an existing directory from the list box below it. If the directory that you want to use is not listed, select the appropriate drive from the Drives: list box. If the drive does not appear on the list, click on the Network... button to map the drive to your PC. When you have selected a directory, click on OK.
18.3 Selecting nodes to receive the download

" To select the nodes to which you will be downloading: 1. Select Edit Node List... The Node List Editor dialog will be displayed (Figure 18-5).
184
C33543002SE_01
Figure 18-5
Node List Editor dialog
The Node Database group box allows you to vary the list of nodes which are displayed in the Available Nodes: list box. You can change the area whose nodes are displayed by changing the setting in the Area: spin box. Note The Local LAN is presented as a special area. It is not part of the Node Area Database.
When the list of nodes displayed in the Available Nodes: list box is the one that you want, you will be able to select the node or nodes to which the download will be made. 2. Select the node or nodes to receive the download. The ID number or name of the node or nodes which you select will be greyed out in the Available Nodes: list box, and the node will appear in the list box in the Nodes Selected group box (see Figure 18-6).
D D
You can select all the nodes in the list by clicking on the
button.
You can select one node at a time by selecting it with the mouse or keyboard and then clicking on the button. button.
185
You can de-select all the nodes in the list by clicking on the
C33543002SE_01

D
You can de-select one node at a time by selecting it with the mouse or keyboard and then clicking on the button.
The ID numbers or names of the de-selected nodes will disappear from the Nodes Selected group box. If they are listed in the Available Nodes: list box, they will no longer be greyed out.
Figure 18-6
Nodes selected in Node List Editor dialog
3. If you want to specify the order in which the system will download the software to the nodes, change the order by selecting the node with the mouse and dragging it up and down, or by changing the setting in the Position Setting: spin box. 4. When all the settings in the Node List Editor dialog are as you want them, click on OK. The Node List Editor will be re-displayed as shown in Figure 18-7, with a list of the nodes which you have selected and which are now ready for the download.
186
C33543002SE_01
Figure 18-7
Nodes ready for a software download
18.3.1 Downloading the software " To download the software to the nodes: 1. Select Operations StartCheck. Note If the log name which you entered already exists (because of previous operations), the dialog shown in Figure 18-8 is displayed when you click Check (or Download). Then you have to click on the appropriate button on this dialog to continue.
C33543002SE_01
187
Figure 18-8
Dialog for existing output log name
The Network Downloader will try to connect to all the nodes which you have selected. The results will be shown in the download window (Figure 18-9).
188
C33543002SE_01
Figure 18-9
Results of a check operation
The results of the check are shown in three ways:

D D
Each node is marked as having either given a successful connection, or that the Network Downloader failed to connect. In the Operation Log (the lower half of the window), where the operations being carried out are shown as they happen, and are simultaneously written to the .LOG file
C33543002SE_01
189

D
The right-hand end of the status bar shows the number of nodes in four different categories: S S S S Pending (not yet checked). The icon is grey. Connecting. The icon is green (on colour monitors), with an inward-pointing arrow superimposed on it. Successful connection. The icon is green (on colour monitors) Failed to connect. The icon is pink, with a diagonal cross superimposed on it.
2. If you have any nodes which failed to connect, select Edit SelectFailed.. The Node List Editor will be redisplayed (see Section 18.3). De-select all the failed nodes. 3. Select Operations StartDownload. The Network Downloader will begin downloading the software to the nodes that you selected. While this is happening, the Operation Log will show continuously how the download is progressing. If you are carrying out a complex download to a large number of nodes, the download operation may take several hours. If you have to leave the download in progress overnight or over a nonworking day, examine Operation Log or the .LOG file when you come back, to see whether any problems were encountered during the download. " To suspend the download: Select Operations Suspend. " To restart the download: Select Operations Resume. " To stop the download: Select Operations Stop. 18.3.2 Viewing an Operation Log " To view an operation log: 1. Select View Operation Log. 2. You can now choose between two options. You can select one of the named .LOG files, if any are listed. (If there are none, it means that no .LOG files exist yet.) When you select the file you can open it for viewing in the default editor.
1810
C33543002SE_01
Alternatively, you can click on Open... The Select Operation Log dialog box will be displayed as in the example in Figure 18-10.
Figure 18-10 Select Operation Log dialog 3. Select one of the .LOG files from the list. You can open it for viewing in the default editor.
C33543002SE_01
1811
1812
C33543002SE_01
Chapter 19 Node Version Control

Whenever you add a node to an area with a SAN Node Manager, an entry for the node is added to the PC database. If you try to manage a node via NMS/10, the NMS/10 application reads the database to see which type and version the node is, and launches the correct Manager. If you have added a node to an area in the past with SAN Manager C1.0 or C1.5, then this SAN Manager software will still be selected by NMS/10 even though you have now installed the SAN C2.0 Manager. The Node Version Control tool allows you to update the PC database so that the new SAN C2.0 Manager is now selected for a particular node. It is only possible to upgrade database entries from one node version to the next. Two upgrade tools are then provided: one to convert database entries from C1.0 to C1.5, and the other to convert them from C1.5 to C2.0.
19.1 Accessing the Node Version Control tool

Doubleclick on the SAN NM C2.0 Node Version Control icon on the desktop (see Figure 19-1).
Figure 19-1
Node Version Control tool icon
If for some reason this icon is not on your desktop, look in the folder C:\NOKIAMGR\SANM2.0 where you will find the Node Version Control tool as
C33543002SE_01
191

the file DBCSAN20.EXE. Doubleclick on the filename to start the Node Version Control tool.
192
C33543002SE_01
Appendix A Key to the SAN C2.0 Manager menus

About this appendix This appendix provides a quick reference to all the menus and commands provided by the SAN C2.0 Manager:
D D
Menu bar (Section A.1) Toolbar equivalents of commands (Section A.2)
This appendix also tells you where to obtain more information in the manual about each command. Not all the commands described in this appendix are always available. Some items are only available when particular windows are also being displayed in the application window.
C33543002SE_01
A-1
A.1 The Menu bar

The Menu bar appears on the Application window (Figure A-1). This Section describes the commands available from this Menu bar.
Figure A-1
The SAN C2.0 Manager Menu bar
A.1.1 Node
Manage... (CTRL + M) displays the Select Node dialog box, enabling a
node to be selected to be managed. See Section 6.3.

Stop Managing (CTRL + T) closes the connection to the currently
managed node, but does not exit the SAN C2.0 Manager application. See Section 4.5.1.
Reconnect attempts to reconnect to the currently selected node
following a communications failure. See Section 6.3.

Reinstall (CTRL + SHIFT + I) displays the first screen of the Reinstall Wiz-
ard to guide you through the process of reinstalling a node. See Section 5.3.
Unit Information... (CTRL +
+ U) displays the Unit Information dialog box for the currently selected unit in the Node Subrack window, containing information about the unit. See Section 5.5.
SHIFT
Manager Options... (CTRL + O) displays the Node Manager Options window, which has two tabbed pages, View (which allows you to
choose whether the Toolbar and/or the Status bar are displayed), and Polling (which allows you to choose whether Auto Refresh is enabled
A-2
C33543002SE_01
or disabled by default for various categories of information). See Section 6.5.

Exit closes the connection to the currently managed node (if a node is
being managed) and exits the SAN C2.0 Manager application. See Section 4.5.3. A.1.2 Data
Undo (CTRL + Z) restores the Node Subrack details to the state before the
last operation was executed.

Send to Node (CTRL + S) sends the data contained in the currently active
window to the currently managed node. See Section 4.4.3.

Refresh from Node (CTRL + R) rereads the data being displayed in the
currently active window from the currently managed node and updates the document window with the new data. See Section 4.4.2.
Save to File... (CTRL + F) displays the Save As dialog box, enabling the
data contained in the currently active window to be saved to a file. See Chapter 13.
Load from File... (CTRL + SHIFT + F) displays the Open dialog box, enab-
ling a file to be loaded into the currently active window. See Section 13.5.
Print (CTRL + P) sends the contents of the currently active window
directly to the default printer. See Section 17.3.

Save As... (CTRL + V) saves the data in a printable window as a text file.
C33543002SE_01
A-3
A.1.3 Monitor
External Alarm (CTRL + E) displays the External Alarms And Station Alarms window, containing details of the external alarms and station
alarms on the currentlymanaged node and allowing you to configure these alarms and to choose whether station alarms are enabled or disabled. See Section 14.3 and Section 14.4.
Current Alarms (CTRL + A) displays the Current Alarm List window,
containing details of the current alarms on the currently managed node. See Section 14.5.
Event History Log (CTRL + L) displays the Event History Log window,
containing details of the alarm history log for the currentlymanaged node and enabling the attributes of the Event History log file to be configured. See Section 14.5.1.
Block Status (CTRL + B) displays the Block Status window, containing
details of the current problems on the selected block. See Section 14.2.4.
Current Performance (CTRL + SHIFT + P) displays the Current Performance window, . See Chapter 9. Performance History (CTRL + SHIFT + H) displays the Performance History window, containing details of the performance data for the cur-
rentlyselected block in the currentlyselected interface window. See Chapter 9.
A-4
C33543002SE_01
A.1.4 Configure
Synchronisation (CTRL + Y) displays the Synchronisation window enab-
ling the synchronisation source to be selected for the currently managed node. See Chapter 7.
Man. and Aux. Channels (CTRL + SHIFT + X) displays the Management and Auxiliary Channels window, showing the embedded management
channels for all the installed STMN units on a node and allowing the embedded management control channels to be disabled or enabled. See Chapter 6.
Interface (CTRL + I) displays the Configuration window for the currently selected unit in the Node Subrack window, enabling the interface char-
acteristics of the unit to be configured. See Chapter 9.

Cross Connections (CTRL + X) displays the Cross Connection window,
enabling the cross connections on the node to be configured. See Chapter 12.
Unit Type... (CTRL + U) displays the Unit Type dialog box for the currently selected unit or empty slot in the Node Subrack window,
enabling the existing unit to be changed or a new unit to be installed. See Section 5.5.
Unit Protection... (CTRL + ALT + SHIFT + P) is not enabled in Release C1.0
of SAN C2.0 Manager.

Node Settings... (CTRL + N) displays the Node Settings dialog box, enab-
ling the node type and Node Subrack type to be viewed, and the node address, Real Time Clock, EFDs, software settings, and test timeout to be configured. See Section 5.4.
C33543002SE_01
A-5
A.1.5 Window
Cascade (SHIFT + F5) resizes and layers all the open document windows
within the application window workspace, so that the title bar of each window is visible.
Arrange Icons distributes all the icons contained in the application
window workspace evenly along the lower edge of the application window.
Close All is not enabled in SAN C2.0 Manager.
Selecting any of the window titles listed at the bottom of the Window menu, brings the selected window to the front of the application window. You can also select a window from the keyboard by ALT + W, n where n is the number beside the window name on the menu. A.1.6 Help
Contents (F1) displays a window containing a list of all the Help topics
covered in the Help system. See Section 4.4.11.

Search displays the Help Search dialog box enabling you to search for
specific Help information. See Section 4.4.11.

Keyboard displays the Help window containing all the keyboard
shortcuts that are used in the SAN C2.0 Manager. See Section 4.4.11.
Symbols displays the Help window showing all the symbols (window
icons, Speed bar icons etc.) that are used in the SAN C2.0 Manager. See Section 4.4.11.
A-6
C33543002SE_01
About SYNFONET Node Manager... displays the About SAN Node Manager dialog box containing copyright information and the release
and product number of the SAN C2.0 Manager. See Section 4.4.11.
A.2 Toolbar equivalents of commands

The Toolbar provides mouse short cuts for commonlyused commands. The number of icons available changes depending on whether the SAN C2.0 Manager is connected to or not connected to a node. Table A-1 defines the associated command for the icons displayed on the toolbar. The icons shown in the toolbar are always displayed while a node is being managed. The icons will be dimmed when the icons equivalent command on the Menu bar is dimmed. Every icon also has its function explained by a tooltip which appears for six seconds whenever the cursor remains on the icon for more than half a second.
C33543002SE_01
A-7
Icon
Associated command
NodeManage... NodeStop Managing DataSend to Node DataRefresh from Node MonitorCurrent Alarms Monitor Event History Log MonitorCurrent Performance MonitorBlock Status MonitorPerformance History ConfigureSynchronisation ConfigureCross Connections ConfigureMan. and Aux. Channels WindowCascade HelpContents
Table A-1
Toolbar icons and their associated commands
The display of the toolbar in the application window can be toggled on and off. To toggle the display of the toolbar, select Node Manager Options and then click on the Toolbar check box in the View tabbed window. A tick alongside the name indicates whether it is currently being displayed. Selecting the command turns the display on or off.
A-8
C33543002SE_01
A.3 Summary of secondary windows and dialogs

The table below lists the names of all secondary windows or dialogs and gives the manual chapter or section that covers their use.
Name Add Area Add Cross-Connection Add Node Management and Auxiliary Channels Q3 Management Summing Points Overhead Block Status Configure 2M Cross-Connection Address PC Q3 Address Configure STM-1 Current Alarms Current Performance Edit Area Edit Cross-Connection Edit Node EFDs Event History Log External Alarms And Station Alarms Install Wizard Load from File Manage Node Manager Options Node Address Node Information Node type Performance History Real Time Clock Reinstall Wizard Type Dialog Dialog Dialog Window Section 6.3.6 12.4 6.3.5 6.4.1 6.4.3 6.4.2 9.2.1 8.2 12 5.4 6.1 9 14.2.5 16.3 6.3.7 12.5 6.3.3 6.4 14.5 14.3 5.2 13.2 6.3 6.5 6.4 6.3.1 6.4 16.4 6.4 5.3
Window Dialog Dialog Dialog Dialog Dialog Window Window Dialog Dialog Dialog Dialog Window Window Dialog Dialog Dialog Window Dialog Dialog Dialog Window Dialog Dialog
C33543002SE_01
A-9
Name Save to File Set up Event History Log Software Settings Subrack Subrack type Synchronisation Node Clock Output Quality Test Timeout Unit Type Unit Information VC-12 POH
Type Dialog Dialog Dialog Window Dialog Window
Section 13.5 14.5.2 6.4 4.2.2 6.4 7.2 7.3 7.4 6.4 5.5 5.5 8.2.4
Dialog Dialog Dialog Dialog
A-10
C33543002SE_01
Appendix B Default unit combinations

About this appendix This appendix contains detailed information about the default unit combinations that are supported by the SAN C2.0 Manager. The default combinations specified are based on the subrack. The same type of node can be produced from different combinations of units in the same type of subrack. These different combinations are shown in the following sections. Related information For more information on the unit combinations available and how to plan a particular unit combination, refer to the SYNFONET Access Node Operating Manual supplied with the node.
C33543002SE_01
B-1
B.1 Node subracks supported

For version C2.0 of the SAN C2.0 Manager, three types of SYNFONET Access Node node subrack are supported:
D D D
SYNFONET Access Node 2slot subrack SYNFONET Access Node 4slot subrack SAN 8slot subrack
B.2 Node types supported

Version C2.0 of the SAN C2.0 Manager supports STM1 Add/Drop Multiplexer (STM1 ADM) SYNFONET Access Node nodes. For more information on the types of nodes available for C2.0, refer to the Application Planning section of the SYNFONET Access Node Operating Manual.
B-2
C33543002SE_01
B.3 Default node combinations

The default combinations available from the SAN C2.0 Manager are described in this section. The combinations are deliberately kept simple and only one or two defaults are offered for any subrack type.
Slot Allowed 1 2 3 4 5 6 7 8 CORE, CORE2M None SAN2M SAN2M SAN2M SAN2M SAN2M SAN2M SAN2M SAN2M SAN2M SAN2M SAN2M SAN2M Default card CORE2M Default PIM STM1 2I/F
Table B-1
8slot Add/drop multiplexer
Slot Allowed 1 2 3 4 CORE, CORE2M None SAN2M SAN2M
Default card CORE2M SAN2M SAN2M
Default PIM STM1 2I/F
Table B-2
4slot Add/drop multiplexer
C33543002SE_01
B-3
Slot Allowed 1 2 CORE, CORE2M None
Default card CORE2M
Default PIM STM1 2 I/F
Table B-3
2slot Add/Drop multiplexer
B-4
C33543002SE_01
Appendix C Q3 address format

About this appendix This appendix provides information on the Q3 address format used by the node and the computer running the SAN C2.0 Manager to communicate with each other.
C.1 Structure of the Q3 address

The Q3 address used by the computer and the node to communicate with each other is a long stream of hexadecimal digits which is split into many fields (Figure C-1).
NSAP
TSEL
SSEL
PSEL
Figure C-1
Structure of part of the Q3 address
The first field, the NSAP, can change. The final three fields are a fixed size and value for SYNFONET Access Node equipment.
C.2 Editable fields of the Q3 address

The only part of the address which can change is the first part, the NSAP. The size of the NSAP can be no more than 20 bytes. The structure of the NSAP is given in Figure C-2.
C33543002SE_01
C-1
NSAP
TSEL
SSEL
PSEL
AFI
IDI
Area Address 20 bytes
System ID
NSEL
Figure C-2
Structure of the NSAP
C.3 Sizes and values for editable fields

The valid sizes and values for all the fields of the NSAP are given in Table C-1.
Address field AFI IDI System ID NSEL Size Fixed Fixed Fixed Fixed Value Variable Variable Variable Variable Fixed Hexadecimal value 1 byte 2 bytes up to 10 bytes 1-8 bytes 1 byte
Area Address Fixed
Table C-1
Sizes and values for the NSAP
Therefore, out of the full node address, there are only four address fields of the node address which need to be edited:
D D D D
AFI (Authority and Format Identifier) IDI (Initial Domain Identifier) Area Address System ID
The AFI, IDI and Area Address define the area which the node is in.
C-2
C33543002SE_01
The System ID identifies the node within a particular area. Therefore, if you have just one area in a node network, this is the only part of the address that needs to change for each node on the network.
C.4 Defining node addresses

In every country there should be an official organisation which allocates the NSAP address space. You must follow the numbering scheme given by this organisation when you are assigning addresses to nodes. Your Marconi representative can tell you where to find this information. The data country code for your country is specified in the International Standards Organisation (ISO) document ISO 3166 or you can obtain it from your local ISO representative. For each country there is a specific three-digit code, e.g. for Finland 246, Sweden 752, Thailand 764, and for the United Kingdom 826. This number appears in the IDI field.
C33543002SE_01
C-3
C-4
C33543002SE_01
Appendix D Related products
D.1 Network Management System/10

NMS/10 is a PC product for monitoring SYNFONET Network alarm information and configuring SYNFONET networks. NMS/10 communicates with the SYNFONET network via an Ethernet connection.
C33543002SE_01
D-1
NMS/10 Collect Alarm Status Install Managers Install Drivers Run Node Managers Configure Nodes
SYNFONET NETWORK
Figure D-1
An NMS/10 unit managing a SYNFONET network
D-2
C33543002SE_01
Using the management facilities provided by NMS/10 you can:

D D D
Obtain and display alarm information from SYNFONET nodes. (up to 50 nodes can be monitored simultaneously.) Create Network Profiles to enable or disable monitoring of SYNFONET nodes operating on a network Create Network Maps to show the real-time alarm status of SYNFONET nodes operating in a network. The maps are displayed graphically, and can be arranged into hierarchies Install Node Manager Applications, Alarm Managers, and Communications Drivers Print lists of new, cleared, or acknowledged alarms Run the Node Manager Application for network nodes to modify their role in the network Configure Communications Drivers
D D D D
D.2 SYNFONET Alarm Manager

SYNFONET Alarm Manager is an alarm collection program which monitors all types of SYNFONET node and passes the alarms to NMS/10 or another network management utility.
C33543002SE_01
D-3
D-4
C33543002SE_01
Glossary
Abbreviations
ADM AIS AS ATM AU BBE BBER BER CAM CCITT CMIP CP CRC4 DCC DCCM DCCR DEG DXC EBER Add/drop Multiplexer Alarm Indication Signal Available Seconds Asynchronous Transfer Mode Administrative Unit Background Block Error Background Block Error Ratio Background Error Ratio Communications Access Manager See ITUT. Common Management Information Protocol Connection Point Cyclic Redundancy Check4 Data Communications Channel Data Communications Channel (Multiplexer) Data Communications Channel (Regenerator) Signal Degraded Digital Cross Connect Excessive Bit Error Rate
C33543002SE_01
Glossary-1
EFD EOW EPPI ES ESPI ESR ETSI FTAM HPA HPT ITUT LAN LOF LOM LOP LOS LPA LPC LSP LPT MS MSA MST NDIS NE NSAP NSel OSPI PDH PIM
Event Forwarding Discriminator Engineering Order Wire Electrical PDH Physical Interface Errored Seconds Electrical SDH Physical Interface Errored Seconds Ratio European Telecommunications Standards Institute File Transfer Access and Management Higher order Path Adaptation Higher order Path Termination International Telecommunications Union Telecommunications Local Area Network Loss of Frame Loss of Multiframe Loss of Pointer Loss of Signal Lower order Path Adaptation Lower order Path Connection Link State PDU (Protocol Data Unit) Lower order Path Termination Multiplex Section Multiplex Section Adaptation Multiplex Section Termination Network Driver Interface Specification Network Element Network Service Access Point Value of the last byte of the NSAP address Optical SDH Physical Interface Plesiochronous Digital Hierarchy Primary Interface Module
Glossary-2
C33543002SE_01
PPA PPI PSAP Q3 RDI RPIU RS RST SAN SANM SD SDH SES SESR SETS SLM SNC SNPA SSF SSM STM STMN TIM TM TMN TU TUG UAS UASR
Plesiochronous Path Adaptation Plesiochronous Physical Interface Physical Service Access point Network management interface Remote Defect Indication Rack Power Interface Unit Regenerator Section Regenerator Section Termination SYNFONET Access Node SAN C2.0 Manager Signal Degrade Synchronous Digital Hierarchy Severely Errored Seconds Severely Errored Seconds Ratio Synchronisation Equipment Timing Source Signal Label Mismatch SubNetwork Connection SubNetwork Point of Attachment (the Ethernet address of the node) Server Signal Failure Synchronisation Status Message Synchronous Transport Module An abbreviated way of referring to different forms of STM units (STM1 single and dual) Trace Identifier Mismatch Terminal Multiplexer Transmission Management Network Tributary Unit (TU3, TU2, TU12) Tributary Unit Group (TUG3, TUG2) UnAvailable Seconds UnAvailable Seconds Ratio
C33543002SE_01
Glossary-3
UNEQ VC
Unequipped Virtual Container (VC4, VC3, VC2, VC12)
Terms
Managed node A managed node is a node that has been selected by the Node Manager as a node to perform management operations on. A communications session between the Node Manager and the node has been established. Network element See Node. Node Nodes or network elements are interchangeable terms that are used to describe any single piece of transmission equipment. This manual uses the term nodes to refer to network elements. A node consists of a number of functional blocks: each functional block has a distinct function within the node. A node has a number of physical interfaces, that is, a number of optical or electrical connectors. Node address A number which uniquely identifies a SYNFONET Access Node node on a network. The node address is known as the PSAP address. It is made up of four parts: NSAP, TSEL, SSEL and PSEL. Only one of these parts, the NSAP, is editable for SYNFONET nodes. Node area A name used to refer to an area, which may contain a number of SYNFONET Access Node nodes. It provides a userfriendly way of referring to a node area. The name can be up to 16 alphanumeric characters long. Node name A name used to refer to a SYNFONET Access Node node on a network. It provides a userfriendly way of referring to the node. The node name can be up to 16 alphanumeric characters long.
Glossary-4
C33543002SE_01
Physical Service Access Point (PSAP) The internal address used by the node to communicate with the protocol layer in the communications stack. See Node Address. Q3 Management interface used by the Node Manager for managing SYNFONET Access Node nodes. Sobriquet The name of the node. SYNFONET The brand name used for a family of Marconi SDH transmission equipment. Whirly wheel A progress indicator used to indicate that the Node Manager and Windows are still running.
C33543002SE_01
Glossary-5
Glossary-6
C33543002SE_01
Index
Numbers
140M unit, signal label values table, 11-8 2M unit, E12 block, 8-9 2M E12 block configuration window, 8-9 2M interface units, viewing, performance data, 16-3 16-5 2M unit viewing status of 2M signal, 8-5 8-7 viewing status of VC12 signal, 8-6 8-8 345M unit, 11-1 block alarms, 11-3 Block Status window, 11-4 configuration window, 11-2 E3 block, 11-5 loopback tests, 11-6 S3 block, 11-9 S3/P3 block, 11-7 34M mode and 45M mode, switching between, 11-8 45M mode and 34M mode, switching between, 11-8 Add Manual Adjacency dialog, 6-22 Add New Overhead Connection window, 6-26 Add Node dialog box, 6-12 address NSAP, C-3 Q3, C-1 address database, copying to another PC, 6-7 alarm and slot number area, 4-9 alarm fields, 8-3, 9-3, 10-3 alarm history log clearing, 14-22 disabling, 14-23 14-25 setting up, 14-21 14-23 updating, 14-22 viewing, 14-19 alarm status area, 4-7 alarm text meanings, 14-4, 14-5, 14-6 alarms classification, 14-6 14-8 descriptive text message, 14-2 notification, 14-8 14-16 in the block alarms window, 14-12 14-14 in the cross connection window, 14-15 14-17 in the current alarms window, 14-13 14-15 on 2M and STM1 windows, 14-11 14-13
A
access level, setting, 15-3 Add Area dialog box, 6-13 Add Cross Connection dialog box, 12-9
C33543002SE_01
Index-1
on synchronisation window, 14-10 14-12 on the Node Subrack window, 14-9 14-10 on the status bar, 14-8 14-9 setting up current, 14-18 14-20 external, 14-16 14-18 severity, 14-7 14-9 time and data occurrence, 14-6 alarms, sorting, in Current Alarm List, 14-14 ALS, see Automatic Laser Shutdown, 9-6, 10-7 Also Apply To window, 8-10, 8-19, 10-7 application window, 4-2 components of, 4-3 workspace, 4-6 autoInstallation of a Node and Subrack, 5-30 Automatic Laser Shutdown, 9-6, 10-7 Auxiliary Connection, 6-15
Configure E12/P12 block window, 8-11, 8-20 Configure EOW Summing Point window, 6-33 Configure MS1 block window, 9-10, 10-10 Configure MS1/S4 block window, 9-11, 10-11 Configure MST block window, 9-10, 10-10 Configure Omnibus Summing Point window, 6-31 Configure OS1 block window, 9-6, 10-6 Configure P12/S12 block window, 8-13, 8-22 Configure RS1 block window, 9-7, 10-8 Configure S12 block window, 8-15 Configure S4 block window, 9-12, 10-12 Configure S4/TUG block window, 9-13, 10-14 Configure STM1 window, 9-6, 10-6 with alarm, 14-12 Configure STM4 window, 9-7, 10-8 Configure Synchronisation window, 7-7, 14-11 configuring an STM1 dual PIM Interface Unit, accessing it, 10-2 configuring an STMN Interface Unit, accessing it, 9-1 configuring the node settings, 5-11 Confirm exit message box, 4-27 Connection, Remote, 6-6 contextsensitive help, accessing, 4-26 copying the address database, 6-7 CORE2M Configure S12 block window, 8-24 CORE2M E12 block configuration window, 8-18 CORE2M unit, EPPI block, 8-18 CP abbreviation explained, 12-2
B
bitmask, 6-28 Block Status window, 9-5, 10-5
C
calibrating, node clock, 7-11 channels, within a CP, 12-10 check results, Network Downloader, 189 closing the node manager, 4-28 colour monitors, 2-3 communications failure, 4-23 compatibility level, 5-19 configuring a 2M unit, accessing it, 8-2 Configure 2M Unit window, 8-17 Configure CORE2M unit window, 8-17
C33543002SE_01
Index-2
AU4 channels within an STM1, 12-10 cross connection selected, 12-16 cross connection table, typical, 12-3 Cross Connection window, 12-7 sorting, 12-7 12-9 cross connections adding, 12-8 12-12 characteristics of, 12-2 deleting, 12-17 editing, 12-11 12-15 naming, 12-3 path protection, 12-2 12-6 printing, 12-18 protecting, 12-13 12-18 representing, 12-3 12-5 termination points for 2M units, 12-5 12-7 for STM1 units, 12-4 12-6 viewing current, 12-7 12-9 Current Alarm List window, 14-14 Current Performance window, 16-4, 16-7
ECC channels, enabling/disabling, 6-16 Edit 2M Synchronisation Quality dialog box, 7-14 Edit Area dialog box, 6-14 Edit Bitmask window, 6-28 Edit Cross Connections dialog box, 12-12 Edit Node dialog box, 6-11 Edit Whole Node Load File Configuration Data wizard screen 2, 13-10 screen 4, 13-12 Enable Security dialog box, 3-6 enabling or disabling station alarms, 14-18 enabling security, 3-10 EOW Connections window, 6-32 Event History Log window, 14-20 events, sorting, in Event History Log, 14-21 example performance data collection options, 16-2 Exiting from the Node Manager, 4-27 confirmation dialog box, 4-27 External Alarms And Station Alarms dialog box, 14-17
D
Data folder, 3-3 database, 6-6 Database folder, 3-3 DEFAULT printer, 17-1 deleting a summing point, 6-31 dialog boxes, 4-2 summary, A-9 document window, 4-2 Download Software window, 5-23 downloading software, refresh ing screen after, 5-25
F
failing to send or receive data from the node, 4-22
G
grey scale monitors, 2-3 Group Memberships dialog box, 15-4
H
handy hints area, 4-7 hardware requirements, 2-2 header area, 4-8
E
E3 block, 345M unit, 11-5
C33543002SE_01
Index-3
help system, using, 4-24 4-26
Manage Node window, 4-16 Management and Auxiliary Channels window, 6-20 Management Channel, 6-6, 6-15 Manager Options window, 9-6, 10-7 manual, purpose, 1-1 manual adjacencies, 6-21 manuallyselected source name, 7-11 measurements, laser power, 9-6, 10-6 memory requirements, 2-3 menu bar, options, A-2 A-7 menu bar items greyed out, 4-4 with an ellipsis (...), 4-4 mouse, using, 4-11 left mouse button, 4-11 right mouse button, 4-11 MS1 block, 9-10, 10-10 MS1/S4 block, 9-11, 10-11
I
icons explained, A-8 inactive software, switching to active, 5-21 INF directory, 3-3 initial window, Network Downloader, 182 initialising a node, 5-30 Install Wizard fifth dialog box, 2slot subrack, 5-8 first dialog box, 5-3 fourth dialog box, 5-6 Information window, 5-10 second dialog box, 5-4 sixth dialog box, 5-9 third dialog box, 5-5 installing a new node, 5-2 installing a node from file, 5-4
K
keyboard shortcuts, 4-14, 4-15
N
NDIS driver, 2-4 2-6 version information, 2-3 network download, restarting, 1810 network download, stopping, 1810 network download, suspending, 1810 Network Downloader check results, 189 Network Downloader initial window, 182 Network Downloader program icon, 181 new node, installing, 5-2 node, reinstalling, 5-10 node address changing, 6-10 6-12 creating, 6-12 deleting, 6-11 node area changing the address details of, 6-13 6-15
L
Laser Mode, 9-6, 10-7 laser power measurements, 9-6, 10-6 left mouse button, 4-11 Load CrossConnections dialog box, 13-14 Loading Configuration Data window, 13-13 loading data from file, 13-7 whole node, 13-7 LocalLAN area, 6-5 loopback tests, 345M unit, 11-6
M
Manage Node dialog box, 5-2
C33543002SE_01
Index-4
creating, 6-12 6-14 deleting, 6-15 node clock, calibrating, 7-11 7-14 Node Compatibility Details window, 5-22 node configuration data, saving, 4-24 Node Details dialog box, 6-9 Node List Editor dialog, 185 node management channels, enabling/disabling, 6-16 6-20 node manager, closing, 4-28 Node Manager Options window Polling page, 6-35, 14-21 View page, 6-34 node selector alarms, 7-9 possible health settings, 7-3 node settings, configuring, 5-11 Node Settings dialog box, 5-12 EFDs window, 5-18 Node window, 5-12 Q3 Address window, 5-14 Real Time Clock window, 5-16 Software Settings window, 5-20 Subrack window, 5-13 Test Timeout window, 5-27 node subrack window, 4-7 components of, 4-8 definition of, 4-2 displaying, 4-8 selecting default window, 4-17 node synchronisation available sources, 7-2 sending to the node, 7-15 source selection mode, selecting, 7-10 7-13 sources availability, 7-4 changing the priority of, 7-7 7-9 priority selection, 7-6 quality, 7-5
removing, 7-9 selecting, 7-13 7-16 setting the quality of 2M, 7-13 7-15 viewing, 7-9 7-11 viewing status of node selector, 7-9 7-11 node units abbreviations, 5-29 installing, 5-27 5-29 node, new, installing, 5-2 node, whole, saving, 13-2 NOKIAMGR directory, 3-2 NSAP, 5-18, C-2 C-4 NSAP address, C-3
O
Open window, 13-8 operation log, 1810 OS1 block, 9-5, 10-6 output window, 7-12 overhead connection, 6-16 overhead connection resources list, 6-27 Overhead window, 6-25
P
P3/S3 block, 345M unit, 11-7 Performance Collection, 9-7, 9-10, 9-12, 10-8, 10-10, 10-12 in RST block, 9-7, 9-10, 9-12, 10-8, 10-10, 10-12 performance data collection, enabling, 16-1 16-3 physical interface, taking into and out of use, 11-5 print manager, 17-2 printing data, 4-24 to file, 17-2 17-4 to the DEFAULT printer, 17-2 17-4
C33543002SE_01
Index-5
printing cross connections, 12-18 product codes, 2-4 progress bar, 4-21 progress counter, 4-22 Protected Cross Connections, 14-16 Protecting CP, 12-2 Protection group. See Protected cross connections
S4 block, 9-11, 10-11 S4/TUG block, 9-13, 10-13 SANM2.0 directory, 3-3 Save As dialog, for saving data as text, 13-2 Save As window, 13-4 Save Configuration Data window, 13-3 Saving Configuration Data window, 13-3 saving data to file, 4-24 saving part of a node configuration to file, 13-5 saving part of the configuration data, 13-6 saving the whole node, 13-2 security administration, 15-3 enable/disable prompt, 3-10 enabling at installation, 15-3 enabling during installation, 3-6 security principles, 15-1 user access level, 15-3 user access levels, 15-2 Security Level area, 4-7 security, enabling, 3-10 select, cross connection, 12-16 Select Area dialog box, 5-6, 5-14, 13-11 select cross connection, 12-16 Select Node dialog box, 6-7 Select Operation Log dialog, 1811 Select Software Directory dialog, 184 self-healing ring, example, 12-6 sending data to the node, 4-18 Set Directory window, 5-24 Set Up Alarm History Log dialog box, 14-22 signal label values, 9-14, 10-15 140M unit, 11-8 Signal Labels, 9-14, 10-14 signal retiming, 8-12, 8-21
Q
Q3 Address for a node, 6-3 for a PC, 6-2 Q3 address, format, C-1 Q3 management channels, 6-16
R
real time clock, updating, 5-17 5-19 receiving data from the node auto refresh, 4-18 manually, 4-17 4-19 reconnecting to a node, 4-23 Refresh screen after download, 5-25 reinstalling a node, 5-10 Release levels list, 5-20 Remote Connection, 6-6 reset the node, 5-30 restarting a network download, 1810 retiming, signal, 8-12, 8-21 right mouse button, 4-11 RS1 block, 9-7, 10-8
S
S3 block, 345M unit, 11-9
C33543002SE_01
Index-6
single fibre working, 9-8, 10-9 SNPA, 6-8 software download, abort download warning, 5-25 software requirements, 2-3 sorting alarms, in Current Alarm List, 14-14 sorting events, in Event History Log, 14-21 SSEL, 5-19 SSM, 7-5, 7-14 stack configuration dialog, 3-8 station alarms, enabling and disabling, 14-18 status bar, 4-7 STM1 configuration window, 9-3, 10-4 STM1 dual PIM interface unit, accessing the unit to configure it, 10-2 STM1 Single PIM interface unit, accessing the unit to configure it, 9-1 STMN interface units, viewing, performance data, 16-6 STM-1 Single PIM interface units, block status alarms, 8-3, 9-4, 10-4 stopping a network download, 1810 stopping the Node Manager, 4-27 subrack with STM-1 dual PIM unit selected, 10-2 subrack with STM-1 Single PIM unit selected, 9-2 Summing Point, configuration window, 6-31 summing point, deleting, 6-31 summing points, 6-16 Summing Points window, 6-30 suspending a network download, 1810 switching active and inactive software, 5-21 switching criteria, 12-14 Synchronisation Status Messaging, 7-5
SYNFONET node address, 6-3 area, 6-4 configuring 2M units, 8-1 8-16 alarms, 14-2 14-6 cross connections, 12-2 12-11 synchronisation, 7-1 7-5 connecting to, 6-9 6-11 default configurations, B-3 B-15 installing, 5-1 5-9 name, 6-3 name and address details, 6-8 6-10 serial number, 5-5 variant, 5-5 version, 5-5 SYNFONET Node Manager aborting an operation, 4-23 4-26 copyright information, 2-4 directory structure, 3-2 indicating progress, 4-19 4-22 installing, 3-4 3-8 node subracks supported, B-2 node types supported, B-2 printing, 17-1 product codes, 2-4 SYSTEM directory, 3-2 system ID, 6-12 SYSTEM32 directory, 3-3
T
Table, Cross Connection, typical, 12-3 timeslot overhead connection, 6-28 title bar, 4-3 Toolbar, displaying, 4-5 toolbar, 4-3, 4-5, A-7 displaying, A-8 tooltip in a document window, 4-10 on the alarm status area, 4-10 on the toolbar, 4-10
C33543002SE_01
Index-7
Trail Trace, 8-15, 8-24, 9-8, 9-12, 10-8, 10-12, 11-9 Tributary Unit Groups, 12-4 TSEL, 5-18 TUG Mapping, 9-14, 10-15 TUG Structure, configuring, 9-14, 10-15 TUG structure, configuring, 9-14, 10-15 TUG Structure window, 9-15, 10-16 typographical conventions, 1-2 1-4
user access levels, 15-2
V
VC4 path, 9-11, 9-12, 9-13, 10-11, 10-12, 10-14 VC-4 path monitoring, 9-12, 10-12
W
whirly wheel, 4-20 Whole Node Load Wizard Node Address dialog box, 13-11 Node Information dialog box, 13-9 whole node, saving, 13-2 windows application menu, A-2 toolbar, A-7 closing, 4-27 summary, A-9
U
uninstalling a unit, 5-28 unit area, 4-9 Unit Information dialog box, 5-30 Unit Type dialog box, 5-28 Unprotect dialog box, 12-16 user access level, shown in Security Level area, 4-7
C33543002SE_01
Index-8

SYNFONET Access Node Manager NOkia

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SYNFONET Access Node Manager NOkia

Hochgeladen von

Copyright:

Verfügbare Formate

SYNFONET Access Node Manager

Release A for SAN Release C2.0 Users Manual C33543.21 A1

E Copyright Marconi Communications

SYNFONET Access Node Manager Users Manual

E COPYRIGHT Marconi Communications 2000 All rights reserved.

E Copyright Marconi Communications

E Copyright Marconi Communications

SYNFONET Access Node Manager Users Manual

E Copyright Marconi Communications

Chapter 2 Introduction to the SYNFONET Access Node Manager . . 2-1

Chapter 3 Installing the SAN Manager software . . . . . . . . . . .

E Copyright Marconi Communications

SYNFONET Access Node Manager Users Manual

Chapter 4 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Closing document windows . . . . . . . . . . . . . . . . . . . . . . . . Closing the SAN Node Manager . . . . . . . . . . . . . . . . . . . . .

Chapter 5 Installing nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 6 Managing SYNFONET Access Nodes . . . . . . . . . . .

E Copyright Marconi Communications

SYNFONET Access Node Manager Users Manual

6.4.1 6.4.2 6.4.3 6.4.4 6.5 6.5.1 6.5.2

6-16 6-21 6-24 6-30 6-32 6-32 6-34 6-34 6-35

Chapter 7 Configuring synchronisation . . . . . . . . . . . . . . . . . . .

Chapter 8 Configuring 2Mbit/s interfaces . . . . . . . . . . . . . . . . .

E Copyright Marconi Communications

8.2.3 8.2.4 8.3 8.3.1

8-6 8-8 8-17 8-17

Chapter 9 Configuring single-interface terminal multiplexers

Chapter 10 Configuring dual-interface terminal multiplexers .

Chapter 11 Configuring 345M units . . . . . . . . . . . . . . . . . . . . . . .

Chapter 12 Configuring cross connections . . . . . . . . . . . . . . . . .

E Copyright Marconi Communications

SYNFONET Access Node Manager Users Manual

Chapter 13 Using files to save and load data . . . . . . . . . . . . . . . .

Chapter 14 Managing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E Copyright Marconi Communications

Chapter 16 Performance monitoring . . . . . . . . . . . . . . . . . . . . . .

Chapter 17 Printing SYNFONET Access Node data . . . . . . . . . .

E Copyright Marconi Communications

SYNFONET Access Node Manager Users Manual

Chapter 18 Downloading software to a network . . . . . . . . . . . . . 181

Chapter 19 Node Version Control . . . . . . . . . . . . . . . . . . . . . . . . . 191

Appendix A Key to the SAN C2.0 Manager menus . . . . . . . . . . .

Appendix B Default unit combinations . . . . . . . . . . . . . . . . . . . . .

Appendix C Q3 address format . . . . . . . . . . . . . . . . . . . . . . . . . . .

E Copyright Marconi Communications

C.2 C.3 C.4

C-1 C-2 C-3

Appendix D Related products . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E Copyright Marconi Communications

SYNFONET Access Node Manager Users Manual

E Copyright Marconi Communications

Chapter 1 About this manual

E Copyright Marconi Communications

SYNFONET Access Node Manager Users Manual

E Copyright Marconi Communications

See Chapter 3 Installation

Indicate a directory or file name. Example:

E Copyright Marconi Communications

SYNFONET Access Node Manager Users Manual

E Copyright Marconi Communications

Chapter 2 Introduction to the SYNFONET Access Node Manager

Using the Node Manager

Hardware and software requirements