302

323-1061-302

SDH TRANSMISSION

Nortel TN-1X System and Software Administration Procedures

Release 9 Standard July 2001


SDH TRANSMISSION


Document Number: 323-1061-302Document Status: StandardProduct Release Number: 9Date: July 2001

Copyright 1997 – 2001 Nortel Networks, All Rights Reserved.

Printed in England

The copyright of this document is the property of Nortel Networks. Without the written consent of Nortel Networks, given by contract or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person whatsoever.

NORTEL NETWORKS CONFIDENTIAL: The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

So far as Nortel Networks is aware the contents of this document are correct. However, such contents have been obtained from a variety of sources and Nortel Networks can give no warranty or undertaking and make no representation as to their accuracy. In particular, Nortel Networks hereby expressly excludes liability for any form of consequential, indirect or special loss, and for loss of data, loss of profits or loss of business opportunity, howsoever arising and whether sustained by the user of the information herein or any third party arising out of the contents of this document.

*NORTEL NETWORKS, the Nortel Networks logo, the Globemark and Unified Networks are trademarks of Nortel Networks.

Netscape and Navigator are trademarks of Netscape Communications Corporation. Microsoft and Windows are trademarks of Microsoft Corporation. HyperTerminal is a trademark of Hilgraeve Inc.


iii

Publication historyJuly 2001

Release 9 Standard

November 1998Release 8 Standard (Revision 2)

October 1998Release 8 Standard (Revised)

September 1998Release 8 Standard

October 1997Release 7 Standard


v

ContentsAbout this document xiTechnical support and information xiv

User administration 1-1User names and classes 1-1The Preside EC-1 Element Controller user administration function 1-2

Adding users 1-3Deleting a user 1-4Modifying user duty classes/passwords 1-5Changing TN-1X user passwords using the Browser 1-7Setting the automatic logout time 1-8

Date/time administration 2-1TN-1X on board clock 2-1Reading the TN-1X clock 2-1Aligning the NE clock 2-2Aligning NE time with Element Controller time 2-3

Configuration data administration 3-1Archiving NE configuration data to an Preside EC-1 Element Controller archive 3-1Restoring NE configurations to the Preside EC-1 Element Controller from an

archive 3-1TN-1X configuration data 3-2Backing up an NE configuration table 3-2

Backing up a configuration table using Preside EC-1 software 3-3Backing up a configuration table to the CAT 3-4Backing up a configuration table to the Preside EC-1 3-6

Restoring configuration information 3-8Returning a configuration into active use 3-8Restoring a configuration table using Preside EC-1 software 3-10Restoring a configuration table from the CAT 3-14Restoring a configuration table from the Preside EC-1 Element Controller 3-16

Activating a restored NE configuration table 3-18Committing to the new NE configuration data 3-19Backing out to the old NE configuration data 3-20Detached mode 3-21

Exiting Detached mode — Impose_config command 3-21Exiting Detached mode — Default command 3-21Exiting Detached mode — Cold restart 3-22Entering Detached mode — Forced_detached command 3-22Entering Detached mode — Default command 3-23

vi

323-1061-302 Release 9 Standard

Viewing TN-1X software releases 4-1Software release information 4-1Software release information displayed via login reports 4-1Software release displayed via the Admin/Sw/View command 4-2Software release displayed via the Session/Get_mux_status menu 4-3Preside EC-1 Release 10 ‘System Information’ command 4-4

Software administration 5-1Application software 5-1Upgrading application software 5-1

Removal of trib-to-trib connections 5-2Software status 5-3Preparing application software for download on CAT 5-5Preparing application software for download on Preside EC-1 Element

Controller 5-6Downloading application software from the CAT 5-7Downloading application software from the Preside EC-1 5-9Aborting a software download 5-12Switching to the alternative software bank 5-12Committing to new TN-1X software 5-13Backing out to old TN-1X software 5-14

Restarting the TN-1X 5-15

Log administration 6-1Log storage and formatting 6-1Archiving logs 6-1Viewing archived logs 6-3

Monitoring network status 7-1Viewing alarm information 7-1

Viewing alarm count only 7-1Viewing active alarm list 7-2Viewing alarm log list 7-2Status indicators 7-2Clearing the alarm log list 7-3

Alarm report formats 7-3Collecting PM data 7-4Viewing the active alarm list 7-5Viewing the alarm log 7-6Viewing the action log 7-7Viewing a specific performance log 7-8Viewing a specific unavailable time log 7-10Early termination of performance monitoring 7-11Requesting an intermediate PM calculation 7-12Configuring performance monitoring 7-15

Error measurement methods 7-15Severely errored seconds 7-16Setting Quality of Service Violation alarms 7-17

Appendix A: Accessing the Browser 8-1Netscape Navigator 8-1Starting Netscape 8-1Logging in 8-1

Logging in from the CAT 8-3

vii


Logging in from the Preside EC-1 Element Controller 8-4Login reports 8-6

Logging out 8-6

Appendix B: TN-1X Release 7.3/7.4 to Release 9.0 Upgrade Procedure9-1Summary 9-1

References 9-2Preparation of TN-1X network elements for software upgrade 9-2

Prerequisites 9-2Preparatory Procedures 9-2

Upgrade the software AUTOMATICALLY 9-6Upgrade the software MANUALLY 9-9

Appendix C: TN-1X Release 8.1/8.2/8.3 to Release 9.0 Upgrade Procedure10-1

Summary 10-1References 10-2

Preparation of TN-1X network elements for software upgrade 10-2Prerequisites 10-2Preparatory Procedures 10-2

Upgrade the software AUTOMATICALLY 10-6Upgrade the software MANUALLY 10-9

Index 9-1

FiguresFigure 3-1 Returning a configuration table into active use 3-9Figure 5-1 Software upgrade overview 5-4Figure 8-1 The TN-1X login screen 8-2Figure 8-2 Top level of the TN-1X command hierarchy 8-5

TablesTable 1-1 Users and passwords 1-1

ProceduresProcedure 1-1 Opening the Preside EC-1 user administration window 1-2Procedure 1-2 Adding an Preside EC-1 user 1-3Procedure 1-3 Deleting an Preside EC-1 user 1-5Procedure 1-4 Modifying a Preside EC-1 user’s duty class/password 1-6Procedure 1-5 Changing an TN-1X user password 1-7Procedure 1-6 Setting the automatic logout time 1-8Procedure 2-1 Reading the TN-1X clock 2-1Procedure 2-2 Reading the TN-1X clock at the login screen 2-2Procedure 2-3 Aligning the TN-1X clock using the CAT 2-2Procedure 2-4 Aligning the Network Element clock 2-4Procedure 3-1 Performing an on-line manual archive 3-1Procedure 3-2 Creating a backup file manually on the Preside EC-1 3-3Procedure 3-3 Backing up a configuration table to the CAT 3-4Procedure 3-4 Backing up a configuration table to the Preside EC-1 3-6Procedure 3-5 Restoring from a backup of an NE 3-10Procedure 3-6 Restoring from a copy of another NE’s configuration 3-12Procedure 3-7 Restoring from a template 3-13

viii


Procedure 3-8 Restoring a configuration table from the CAT 3-14Procedure 3-9 Restoring a configuration table from the Preside EC-1 3-16Procedure 3-10 Activating a restored NE configuration table 3-18Procedure 3-11 Committing to the new NE configuration data 3-19Procedure 3-12 Backing out to old NE configuration data 3-20Procedure 3-13 Exiting Detached mode — Impose_config command 3-21Procedure 3-14 Exiting Detached mode — Default command 3-21Procedure 3-15 Exiting Detached mode — Cold restart 3-22Procedure 3-16 Exiting Detached mode — Forced_detached command 3-22Procedure 3-17 Exiting Detached mode — Default command 3-23Procedure 4-1 Viewing the software release — Admin/Sw menu 4-2Procedure 4-2 Viewing the software release — Session/Get_mux_status

menu 4-3Procedure 4-3 Viewing system information 4-4Procedure 5-1 Preparing application software for download on CAT 5-5Procedure 5-2 Preparing application software for download on Preside EC-1 5-6Procedure 5-3 Downloading application software from the CAT 5-7Procedure 5-4 Downloading application software from the Preside EC-1 5-9Procedure 5-5 Switching to the alternative software bank 5-12Procedure 5-6 Committing to new TN-1X software 5-13Procedure 5-7 Backing out to the original TN-1X software 5-14Procedure 5-8 Restarting the TN-1X 5-15Procedure 6-1 Perform on-line archive of logs 6-2Procedure 6-2 Viewing archived logs 6-3Procedure 7-1 Clearing the alarm log list 7-3Procedure 7-2 Retrieving PM reports 7-4Procedure 7-3 Viewing the active alarm list 7-5Procedure 7-4 Viewing alarms from the alarm log 7-6Procedure 7-5 Viewing the action/alarm log 7-7Procedure 7-6 Viewing a specific performance log 7-8Procedure 7-7 Viewing a specific performance log 7-10Procedure 7-8 Early termination of performance monitoring 7-11Procedure 7-9 Requesting an intermediate PM calculation 7-12Procedure 7-10 Exporting TN-1X performance logs for external analysis 7-14Procedure 7-11 Setting the error measurement method 7-15Procedure 7-12 Setting severely errored second thresholds 7-16Procedure 7-13 Setting QOSV thresholds 7-18Procedure 7-14 Setting the start time for 24 hour performance periods 7-24Procedure 8-1 Logging in to the TN-1X via the CAT 8-3Procedure 8-2 Logging in to the TN-1X via the Preside EC-1 8-4Procedure 9-1 Extracting the TN-1X R7.0 load image software 9-3Procedure 9-2 Rebooting all TN-1X network elements 9-4Procedure 9-3 Checking status of the rebooted network elements 9-5Procedure 9-4 Automatically download the

TN-1X Release 9.0 load image software 9-6Procedure 9-5 Automatically booting/committing the

TN-1X Release 9.0 network elements 9-7Procedure 9-6 Manually downloading the TN-1X R9.0 load image software 9-9Procedure 9-7 Manually booting the TN-1X R9.0 load image software 9-10Procedure 9-8 Deleting tributary to tributary connections after booting

TN-1X Release 9.0 Software (See Preparation for Software Upgrade) 9-11

Procedure 9-9 Manually committing the downloaded TN-1X R9.0 load image 9-12

Procedure 10-1 Extracting the TN-1X Release 9.0 load image software 10-3

ix


Procedure 10-2 Rebooting all TN-1X network elements 10-3Procedure 10-3 Checking status of the rebooted network elements 10-5Procedure 10-4 Automatically download the

TN-1X Release 9.0 load image software 10-6Procedure 10-5 Automatically booting/committing the

TN-1X Release 9.0 network elements 10-7Procedure 10-6 Manually downloading the TN-1X R9.0 load image software 10-9Procedure 10-7 Manually booting the TN-1X R9.0 load image software 10-9Procedure 10-8 Deleting Tributary to Tributary connections after booting

TN-1X Release 9.0 Software 10-10Procedure 10-9 Manually committing the downloaded

TN-1X R9.0 load image 10-11


xi

About this documentThis document details the system and software administration procedures used for the TN-1X, Craft Access Terminal (CAT) and the Preside EC-1 Element Controller when used with the TN-1X Network Element (NE).

The TN-1X NE is a part of the Nortel Networks transport equipment family, for use within a synchronous digital hierarchy (SDH) fibre optic transmission system.

All procedures in this document, unless stated to the contrary, are Browser User Interface procedures and can be used from the CAT or the Preside EC-1 Element Controller. The Browser is a hypertext system that forms an interface between the user and application software held on the NE. For detailed procedures on reaching the Browser application from either platform, see Appendix A: Accessing the Browser.

In all procedures it is assumed that the user is starting from the root. This can be accessed from any point in the UI menu structure by selecting the ‘Home’ button.

Indication of trademarks in this documentThe asterisk after a name denotes a trademarked item. The title page and back cover acknowledge all trademarked items.

Related documentsThe following documents are referenced within this book:

1 Nortel TN-1X System Description Release 9, NTP 323-1061-100

2 Nortel TN-1X Command Line User Interface Guide Release 9,NTP 323-1061-401

3 Preside EC-1 Element Controller User Procedures Release 14, NTP 323-1091-402

4 Engineering Bulletin TN-1X Release 9.0 Connection Recommendations, SDH_E155

5 Preside EC-1 Network Upgrade Procedure, 323-1091-230

xii About this document


ConventionsThroughout this document, the following conventions are used:

• User entry is in bold, for example: config

• Output reports, displayed by the Browser in a separate output window, are shown as the example below:

Software and Config table status

Throughout this document, the software release numbers shown are 9.6A and 9.7A. These are examples used to show increments in software versions during the upgrade process, but represent the actual software release numbers in format only.

Where confirmation is required, the following message is displayed in a dialogue box, accompanied by an audible warning:

Type Active Active Bank Standby Upgrade Status

SW 9.6A A 9.6A Stable

CFG 9.0E 9.0E Stable


xiii


xiv

Technical support and informationAs far as Nortel Networks knows, the information in this document is correct. If, however, you discover any errors or have comments about the arrangement of the content, send details by email to:

[email protected]

Nortel Networks provides a full technical support service for its customers. The Nortel Networks Service Desk can be called at any time on the following numbers:

Within Europe: Freephone 00800 8008 9009

Outside of Europe: +44 20 8920 4618

Fax within the United Kingdom: 020 8945 3456

Fax outside of the United Kingdom: +44 20 8945 3456

As an option, you can contact technical support through the Nortel Networks web site:

www.nortelnetworks.com

and by selecting Customer Support.

EMC/Safety conformance

This product/product family complies with the essential protection requirements of the EMC Directive 89/336/EEC as amended by 92/31/EEC, when it is properly installed and maintained and when it is used for the purposes for which it is intended.


1-1

�

User administration 1-User names and classes

All users are required to login to the TN-1X using a user name and password. There are three classes of user with different sets of access privileges. These are shown in Table 1-1 below.

The Configuration Manager and System Engineer user classes have compulsory automatic logout. This is initially set to the default setting of fifteen minutes, but this can be changed using the ‘Session’ commands (see “Setting the automatic logout time” on page 1-8). Possible settings are between 0 and 60 minutes (0 will be interpreted as INFINITE time, in other words logout disabled, though the new value only applies to the current session.

Table 1-1Users and passwords

User class User names Access privileges

Status Manager

viewr Read only. Can perform all ‘view’ commands.

Configuration Manager

oper1, oper2 All network traffic control, upgrades, restarts and connections.

SystemEngineer

nortl All commands. Severely Errored Seconds (SES) thresholds, password setting and comms management configuration.

Note: If the System Engineer’s password is forgotten, the Nortel Networks Service Centre should be contacted.

1-2 User administration


The Preside EC-1 Element Controller user administration functionThe User Administration function enables you to add and delete Element Controller users, inspect the details of existing users, and assign and modify user names, passwords and duty classes.

The User Administration facilities are all accessed from the User Administration window (see below).

Procedure 1-1Opening the Preside EC-1 user administration window

Step Action

1 Select the User Administration button from System Administration within the Main Menu. The button turns blue, and the User Administration window is displayed.

—end—

User Administration

List Of Users

Add User

Modify User

Delete User

Cancel

SYSENG01FREDERICKSAMANTHAJONATHON

User administration 1-3


�Adding usersEach user is assigned a unique User Name and a confidential password. When adding a user, you will be asked to enter both of these pieces of information. You will also be asked to assign a Duty Class, which will determine the new user’s access rights.

• The User Name and User Password are both case-sensitive alphanumeric strings. The User Name must be at least four, and no more than twelve, characters in length. The User Password must be at least four, and no more than eight, characters in length.

Note: Some user names are reserved, and cannot be modified.

• The Duty Class is one of System Administrator, Configuration Manager, or Status Manager. Of these, only the Configuration Manager and Status Manager can access the Browser.

• System Engineers can access all functions but assignment of this duty class can only be performed by existing System Engineers using the UNIX operating system.

Procedure 1-2Adding an Preside EC-1 user

Step Action

1 Select the Add User button from the User Administration window. The Add User window is displayed.

2 Select the User Name field to activate it, and type-in the user name, which must be unique to the new user.

3 Select the User Password field to activate it, and type in the User Password. The characters you type are not displayed for security reasons.

—continued—

Add User

Add User

Cancel

JONATHON

OK

User Name

User Password

Confirm Password

Duty Class System Administrator



Procedure 1-2 Adding an Preside EC-1 user (continued)

Step Action

4 Select the Confirm Password field to activate it, and type in the confirmation password, which must be identical to the user password (including the use of upper and lower case letters).

5 The Duty Class field defaults to Status Manager. If you wish to assign an alternative duty class to the new user, position the mouse pointer in the Duty Class field. Press and hold the left-hand mouse button to select the required duty class from the popup menu.

6 Select the OK button to close the window.

—end—

A message box will confirm the addition, or, if the addition was not performed, will inform you of the reason why.

Note: If you have made any error in entering the details, it will always be necessary to re-enter the password.

Deleting a userThe deletion of a user is performed via the Delete User window. This window is displayed when the Delete button on the User Administration window is selected.

Note 1: System engineer users cannot be deleted.

Note 2: Users are able to delete themselves.

CAUTIONDeletion of system administration class usersThe Element Controller allows a user with a System Administrator duty class to delete himself/herself without providing a warning.

Delete User

Delete User

Cancel

JONATHON

OK

User name



�Procedure 1-3Deleting an Preside EC-1 user

Step Action

1 Select the user to be deleted from the List of Users in the User Administration window.

2 Select the Delete User button. A Delete User window is displayed showing the user name you selected.

3 Select the OK button to delete the user. A message box is displayed asking for confirmation.

4 Select the OK button to delete the selected User.

—end—

Note: An alternative method to delete a user is to select the Delete User button with no user selected, select the User Name field of the Delete User window to activate it, and type in the user name.

Modifying user duty classes/passwordsModifications to a user’s password and duty class are made via the Modify User Profile window. This window is displayed when the Modify button on the User Administration window is selected.

Note: Modification of users who are in the System Engineer duty class, or upgrading of existing users to System Engineer, can only be performed by an existing System Engineer via the UNIX operating system.

Modify User Profile

User Profile

Cancel

JONATHON

OK

User Name

User Password

Confirm Password

Duty Class System Administrator



Procedure 1-4Modifying a Preside EC-1 user’s duty class/password

Step Action

1 Select the user whose details you wish to modify from the list box in the User Administration window.

2 Select the Modify User button. The Modify User Profile window is displayed, with the user name you have selected displayed in a read-only field.

3 Select the User Password field to activate it, and type in the User Password. The characters you type are not displayed for security reasons. This field must be completed, even if the password is not going to be changed.

4 Select the Confirm Password field to activate it, and type in the confirmation password, which must be identical to the user password (including the use of upper and lower case letters). This field must be completed, even if the password is not going to be changed.

5 The Duty Class field defaults to the existing duty class for the selected user. If you wish to assign an alternative duty class to the user, position the mouse pointer in the duty class field. Press and hold the left-hand mouse button to select the required duty class from the popup list.

—end—

A message box will confirm the modification. If the operation was not successful, a message box inform you of the reasons.

Note 1: Whatever operation is performed using this window, you must enter the password in both password fields. The password will need to be obtained from the user concerned before performing this procedure.

Note 2: If you have made any error in entering the details, it will always be necessary to re-enter the password in both password fields.

Note 3: Once you have opened the Modify User Profile window, you can load an alternative user’s profile by double-clicking on the appropriate user name in the User Administration window.



�Changing TN-1X user passwords using the BrowserConfiguration Manager and System Engineer user classes are permitted to change their passwords, if the passwords are not fixed. Passwords must be between six and eight characters long, upper or lower case and cannot contain the following characters: comma, colon, semicolon or the equals symbol.

Procedure 1-5Changing an TN-1X user password

Step Action

1 Access the ‘Admin/User’ submenu by selecting:AdminUser

2 Execute the ‘Change_pswd’ command by selecting:Change_pswd

3 The Browser opens a parameter input window enabling the user to enter the existing password, the new password and a repeat of the new password. The window also provides a button to clear any existing text in the fields and a ‘Submit’ button.

4 Enter the existing password, the new password and a repeat of the new password. Passwords are not echoed as they are entered.

Note: System Engineer user classes are also provided with a text box enabling them to enter the username of other users.

—end—



Setting the automatic logout timeThe TN-1X enforces automatic idle logout to users of the Configuration Manager and System Engineer classes. The default time is set at 15 minutes but users can change this to any figure between 0 and 60. If 0 is entered, automatic logout is disabled for the current session. Status Manager class users are not subject to automatic logout, this is to enable prolonged monitoring/surveillance activities. If the user sets the autologout time to two minutes or less, no warning of the imminent automatic logout is given.

Procedure 1-6Setting the automatic logout time

Step Action

1 Access the ‘Session/Auto_logout’ submenu by selecting:Session Auto_logout

2 Execute the ‘Set’ command selecting:SetNo confirmation is required.

3 The Browser opens a parameter input window enabling the user to enter the new automatic logout time. The window also provides a button to clear any existing text in the fields and a ‘Submit’ button.

4 Enter the new automatic logout time.

5 Select the ‘Submit’ button.

6 The Browser responds by refreshing the parameter input window with a feedback message and a ‘Continue’ button.

7 Select the ‘Continue’ button to return to the parameter input window.

8 This new time only applies to the current session, the default is re-applied at each login.

—end—

end of chapter


2-1�

Date/time administration 2-TN-1X on board clock

The Subrack Controller contains a non-volatile real time clock with an accuracy of ±1.25 seconds per day. The clock is used for time stamping alarm, event and performance messages. The clock is factory set but can be adjusted from the CAT or the Element Controller. When connected to a Element Controller, the clock is periodically adjusted to keep the local clock aligned with the Element Controller clock.

The real time clock function has a battery back-up which maintains time and calendar functions for up to approximately six weeks in the absence of power to the Subrack Controller.

Reading the TN-1X clockThe TN-1X clock can be read using Browser commands issued from the CAT or the Element Controller.

Procedure 2-1Reading the TN-1X clock

Step Action

1 Access the ‘Maint/Operations/Clock’ submenu by selecting:MaintOperationsClock

2 Execute the ‘Read’ command by selecting:ReadNo confirmation is required.

3 A report window is opened/refreshed displaying the Network Element date and time.

NE Time

—end—

NE_date NE_time

16/06/1997 14:40:16

2-2 Date/time administration


Procedure 2-2Reading the TN-1X clock at the login screen

Step Action

1 Login to the TN-1X.

2 Execute the ‘NE time’ command by selecting:NE timeNo confirmation is required.

3 A report window is opened displaying the Network Element date and time.

NE Time

—end—

Aligning the NE clockThe TN-1X clock can be aligned to the correct date and time using Browser commands from a CAT or Element Controller.

Procedure 2-3Aligning the TN-1X clock using the CAT

Step Action

1 Access the ‘Maint/Operations/Clock’ submenu by entering:MaintOperationsClock

2 Execute the ‘Align’ command by selecting:AlignNo confirmation is required.

3 The Browser opens a parameter input window enabling the user to enter the date and time. The window also provides a button to clear any existing text in the fields and a ‘Submit’ button.

4 Enter the new date and time.

5 Select the ‘Submit’ button.

6 The Browser responds by refreshing the parameter input window with a feedback message and a ‘Continue’ button.

7 Select the ‘Continue’ button to return to the parameter input window.

—continued—

NE_date NE_time

16/06/1997 14:40:16

Date/time administration 2-3


�

Procedure 2-3 Aligning the TN-1X clock using the CAT (continued)

Step Action

8 The Browser opens/refreshes an output window

Events (952)

Events (951)

—end—

Aligning NE time with Element Controller timeThe Align Time option allows you to manually align the date and time held by the selected NE with that held by the Element Controller. If an unmanaged NE is selected from the NE Type popup menu, the Align Time option is inactive (greyed out).

Note: The Element Controller aligns the date and time on the NEs within its span of control when it first establishes communications. Thereafter, this is performed automatically once per day.

The Element Controller date and time can be set by the System Administrator and System Engineer, for details see Preside EC-1 Element Controller User Procedures, NTP 323-1091-402.

Old Date Old Time User Date Time

29/03/1998 23:06:50 29/03/1998 23:06:55

Command User Date Time

m/o/c/a 29/03/1998 23:06:55 29/03/1998 23:06:55

2-4 Date/time administration


Procedure 2-4Aligning the Network Element clock

Step Action

1 Position the mouse pointer over the required NE in the Network Element Access window and press the left-hand mouse button.

2 Press the right-hand mouse button anywhere in the window to open the popup menu and select Align Time. A confirmation message is displayed. Confirm the action.

3 Select the OK button to align the NE clock.

The messages window indicates the success/failure of this operation.

—end—

Where daylight saving is observed, this change is made automatically. When the system moves from one setting to another, the system continues to run, and alarms and events will be timestamped with the new time. Scheduled events will be run at the old time, unless the system is rebooted before the scheduled time occurs.

end of chapter


3-1

�Configuration data administration 3-Archiving NE configuration data to an Preside EC-1 Element Controller archive

The NE configuration data held on the Element Controller can be made by System Engineer class users using a UNIX window. Ensure that the tape is present in the tape drive, prior to executing an archiving operation. An archive is performed as follows:

Procedure 3-1Performing an on-line manual archive

Step Action

1 Login as root from the VUE login banner by typing:

root ↵<password> ↵

2 Load a blank tape into the tape drive and wait for the tape drive lights to stop flashing.

3 Open a UNIX window from the VUE workspace manager and type the following to invoke the archive:

/home/sdhmsusr/sdhms/bin/.db_archive ↵Various messages are displayed concerning the archive.

4 The system carries out a complete archive of configuration information and log information. A message is displayed within the message tool (if running) to indicate the completion/failure of this operation.

5 Eject, label and store the database archive tape.

6 Exit from the sdhmsusr account by selecting ‘exit’ from the VUE tool bar.

—end—

Restoring NE configurations to the Preside EC-1 Element Controller from an archive

This option retrieves configurations for all NEs from an Preside EC-1 archive. This must be performed via the system console. Before restoring data, the system must be shut down using the System Shutdown function from the Element Controller Main Menu. This and restoring NE configuration data is described fully in Preside EC-1 Element Controller User Procedures, NTP 323-1091-402.

3-2 Configuration data administration


TN-1X configuration dataThe TN-1X has a set of configurable parameters that are required to accommodate various user preferences. The Subrack Controller incorporates two configuration data tables (one active and one inactive) stored in non-volatile memory (battery-backed RAM). Details of the configuration data are given in the TN-1X System Description, NTP 323-1061-100.

The configuration table holds important data on the basic operating parameters of the TN-1X. The user is advised to backup the default configuration before making any changes and to make backups before making any significant changes to a stable configuration.

Note: The Element Controller contains an Automatic Script Driver (ASD) which allows certain configuration procedures (Restore, Commit, and Backout) to be performed on a number of TN-1X NEs in a single operation (see Preside EC-1 Element Controller User Procedures, NTP 323-1091-402).

Backing up an NE configuration tableA backup NE configuration table file can be created in the following ways:

• Using the ‘Backup NE’ function from inside the EC-1 software. This stores the NE’s configuration on the EC-1’s hard drive using an automatically generated name in a fixed directory (see “Backing up a configuration table using Preside EC-1 software” on page 3-3).

• Using the ‘Backup’ command from Browser User Interface session on the CAT. This stores the NE’s configuration on the CAT’s hard drive, using a path and filename provided by the user (see “Backing up a configuration table to the CAT” on page 3-4).

• Using the ‘Backup’ command from Browser User Interface session on the EC-1. This stores the NE’s configuration on the EC-1’s hard drive, using a path and filename provided by the user (see “Backing up a configuration table to the Preside EC-1” on page 3-6).

Before creating a configuration backup file for an NE, the user must ensure that the Software Status and the Configuration Table Status of the NE are both ‘Stable’. This information is available when logging into a Browser User Interface session by selecting the ‘Software and config table status’ login report. If either status reads anything other than ‘Stable’, action must be taken to return to the ‘Stable’ condition.

Note: When specifying a filename for a configuration table, ensure that a unique name is used. No confirmation is requested when an existing name is used. It is recommended that file names include the date, in order to minimise the possibility of accidental overwrites.

Configuration data administration 3-3


�

Backing up a configuration table using Preside EC-1 softwareThis option creates a backup copy of the configuration information for the selected NE. The Preside EC-1 issues a request for this information from the NE, and the extracted information is stored on the Preside EC-1’s hard disk. The NE must be managed for the backup process to be accessible. The Element Controller performs an automatic backup of all NEs during each day.

The configuration information can be stored as the latest backup file for the NE, or as a template.

Backup files from automatic and manual processes are identical, and are stored in the same directory. When an NE has configuration information restored to it, the latest file is used, irrespective of whether it was generated automatically or manually. When a backup is requested, a log of its progress appears in the messages window.

Procedure 3-2Creating a backup file manually on the Preside EC-1

Step Action


2 Press the right-hand mouse button anywhere in the window to open the popup menu and select Backup NE.

The Messages window indicates the progress of the NE backup.

—end—

ATTENTIONIt is recommended that this function is used on managed NEs in preference to the functions available from a User Interface session. This minimises the possibility of errors when file names are specified.



Backing up a configuration table to the CATThis option creates a backup copy of the configuration information for the selected NE on the CAT’s hard drive, using a path and filename provided by the user.

Procedure 3-3Backing up a configuration table to the CAT

Step Action

1 Login to a Browser User Interface session as described in Procedure 8-1.

2 Access the Admin/Cnfg_tbl submenu by selecting:AdminCnfg_tbl

3 Verify that the Software (SW) upgrade status and the Configuration Table (CFG) upgrade status are both ‘Stable’. Execute the ‘View’ command by selecting:ViewThe following report is displayed:


If the Config upgrade status is not ‘Stable’, the Configuration tables are not identical.

If the Config upgrade status is ‘Ready-to-activate’, a Configuration table has been restored but has not yet been activated and the ‘Backup’ command is not available. Use Procedure 3-10 to activate a restored configuration table.

If the Config upgrade status is ‘Ready-to-commit’, the restored table is already active and the ‘Backup’ command is not available. Use Procedure 3-11 to commit to the configuration.

4 Execute the ‘Backup’ command by selecting:Backup

5 The Browser responds by opening/refreshing a parameter input window with a text entry box for the configuration filename. The window also provides a ‘Submit’ button and a ‘Clear’ button.

—continued—

ATTENTIONIt is recommended that the Preside EC-1’s ‘Backup NE’ function is used on managed NEs in preference to the functions available from a User Interface session. This minimises the possibility of errors when file names are specified.






�

Procedure 3-3 Backing up a configuration table to the CAT (continued)

Step Action

6 Enter the configuration table path and filename. This must be a full hierarchic reference up to 50 characters in length, and must include the drive letter. For example, ‘C:\TN-1X_R8\241098’.

Once the path and filename are entered, select the ‘Submit’ button.

Note: It is recommended that the filename should conform to a naming scheme that allows the user to identify the particular NE to which it refers. The filename should be unique, as no confirmation of the filename is requested. It is recommended that the filename contains the date, to minimise the possibility of accidental overwrites.

7 The progress of the backup operation can be monitored using the ‘htmserv’ application. From the Windows95 Taskbar (at the bottom of the screen by default), maximise the ‘htmserv’ task. The ‘htmserv’ window is then displayed.

8 Once the ‘htmserv’ application indicates that the file transfer has completed, a message is displayed inside a Netscape window to confirm this. Close this Netscape window.

9 Do NOT terminate the ‘htmserv’ application. Minimise the ‘htmserv’ window.

—end—

CAUTIONConfirming backup operationOnce the ‘Submit’ button has been pressed (see step 6), it should not be pressed a second time. No additional operations should be actioned via the Browser User Interface until the backup process has completed.

ATTENTIONWhen backing up the configuration table from a CAT, the long file and directory names that are supported by Windows 95 can cause the Browser User Interface’s restore function to abort. When using the Browser, the file hierarchy that contains backed up configuration files must only use file and directory names up to eight characters in length. Longer directory and file names will be truncated into DOS format names (indicated by a tilde (‘~’) character at the beginning of the name), which cannot be processed by the Browser.



Backing up a configuration table to the Preside EC-1This option creates a backup copy of the configuration information for the selected NE on the Preside EC-1’s hard drive, using a path and filename provided by the user.

Procedure 3-4Backing up a configuration table to the Preside EC-1

Step Action






If the Config upgrade status is ‘Ready-to-activate’, a Configuration table has been restored but has not yet been activated and the ‘Backup’ command is not available. Use Procedure 3-10 to activate a restored configuration table.

If the Config upgrade status is ‘Ready-to-commit’, the restored table is already active and the ‘Backup’ command is not available. Use Procedure 3-11 to commit to the configuration.

4 Execute the ‘Backup’ command by selecting:Backup

5 The Browser responds by opening/refreshing a parameter input window with a text entry box for the configuration filename. The window also provides ‘Submit’ button and a ‘Clear’ button.

—continued—

ATTENTIONIt is recommended that the Preside EC-1’s ‘Backup NE’ function is used on managed NEs in preference to the functions available from a User Interface session. This minimises the possibility of errors when file names are specified.






�

Procedure 3-4 Backing up a configuration table to the Preside EC-1 (continued)

Step Action

6 Enter the configuration table path and filename. This must be a hierarchic reference up to 50 characters in length. If the recommended directory structure (‘~sdhms/data/’) is used, this element of the hierarchy may be omitted.

Once the file has been entered/selected, select the ‘Submit’ button.

Note: It is recommended that the filename should conform to a naming scheme that allows the user to identify the particular NE to which it refers. The filename should be unique, as no confirmation of the filename is requested. It is recommended that the filename contains the date, to minimise the possibility of accidental overwrites.

7 The following message is displayed:

OK, (4) Request is being processed in background.

8 The TN-1X generates the following message when the backup process is complete. This messages will be displayed by the Browser when it next refreshes its windows. This occurs whenever the current menu changes, or an additional command is issued to the TN-1X.

Unsolicited messages

—end—

Operation Status User Date Time

Backup Completed 13/06/1997 14:30:21



Restoring configuration informationConfiguration information that has been previously backed up can be restored to an NE. This information is placed in the NE’s inactive configuration table. The active configuration table is unaffected.

A configuration table file can be restored in the following ways:

• Using the ‘Restore NE’ function from inside the EC-1 software. This retrieves the latest version of an NE’s configuration from a specific directory on the EC-1’s hard drive (see “Restoring a configuration table using Preside EC-1 software” on page 3-10).

• Using the ‘Restore’ command from Browser User Interface session on the CAT. This retrieves the NE’s configuration from the CAT’s hard drive, using a path and filename provided by the user (see “Restoring a configuration table from the CAT” on page 3-14).

• Using the ‘Restore’ command from Browser User Interface session on the EC-1. This retrieves the NE’s configuration from the CAT’s hard drive, using a path and filename provided by the user (see “Restoring a configuration table from the Preside EC-1 Element Controller” on page 3-16).

Returning a configuration into active useThe process of returning configuration information into active use on an NE is shown in Figure 3-1. The restore functionality is only one part of this process, irrespective of whether it is performed by the Preside EC-1 software, or from a Browser User Interface session.

ATTENTIONReturning an NE’s configuration into active use requires a number of additional commands to be issued from the Browser. The overall process is detailed in “Returning a configuration into active use” on page 3-8.

ATTENTIONIt is recommended that the Preside EC-1’s ‘Restore NE’ function is used on managed NEs in preference to the functions available from a Browser User Interface session. This minimises the possibility of errors when file names are specified.



�

Figure 3-1Returning a configuration table into active use

Start

Replacement config available

Test loaded configuration

Is loaded configuration

OK?

Yes

No

Finish

Both configuration tables contain the original configuration information

The active table contains the original configuration, and the inactive table now contains the loaded configuration.

While the loaded configuration is being tested, the original configuration is in the inactive configuration table. You can switch between the different configurations.

During normal operation, it is important that both tables contain the same configuration information. If these are different, this can interfere with the operation of configuration functions.

If the loaded configuration is satisfactory, the user may decide to commit to it. If the loaded configuration proves unsatisfactory, then the user must back out, reverting to the original configuration. In either case, the NE is left with the same configuration in both configuration tables.

Switch to loaded configuration

Restore a configuration table to NE

The configuration information that is to be restored is available for use.

Switch to original configuration

Backout

Old configuration in both tables

Commit to loaded configuration

Loaded configurationin both tables



Restoring a configuration table using Preside EC-1 softwareThe NE must be managed for the Restore process to be accessible. The configuration information can be sourced from:

• A backup of the selected NE’s configuration.

• A copy of another NE’s configuration.

• A template file.

The use of these sources is detailed in the sections that follow.

Before configuration information can be restored to an NE, the NE Software and Data Configuration tables must be ‘Stable’. If either status reads anything other than ‘Stable’, action must be taken to return to the ‘Stable’ condition.

Restoring from a backup of the NEWhen backup information for an NE is restored, the last saved backup file for the NE is used. This backup will have been created either manually from inside the Preside EC-1 software (see “Backing up a configuration table using Preside EC-1 software” on page 3-3) or automatically by the Preside EC-1 software. If no backup files are accessible for the NE, the backup will not be possible.

Procedure 3-5Restoring from a backup of an NE

Step Action


2 Press the right-hand mouse button anywhere in the window to open the popup menu and select Restore from backup.

3 A final confirmation is requested. Accept this. The restore process will then begin. The Messages window indicates the progress of this operation.

4 When complete, the NE will contain the restored information in its inactive bank. To activate this configuration table, see Procedure 3-10. To commit to the configuration, see Procedure 3-11.

—end—

ATTENTIONIt is recommended that the Preside EC-1’s ‘Restore NE’ function is used on managed NEs in preference to the functions available from a User Interface session. This minimises the possibility of errors when file names are specified.



�

Restoring from another NE’s backup configurationThe restore process can be performed using the latest backup copy of another NE’s configuration. The backup file is unaffected by this process, and remains available for all purposes. The Restore Files window is used to perform this action (see below).

The Restore Files window (see above) lists backup files from all eligible NEs, along with their creation timestamps. The list of files is determined as follows:

• The files listed are for NEs within the span of control of the Element Controller.

• The files listed are for NEs of the same type. That is, for a TN-1X NE, only backup files for TN-1X NEs are listed.

• The files listed are for NEs using the same backplane type.

The backup method is displayed in brackets after the NE name. If a backup was made automatically, this is indicated by ‘(A)’. Backups that were made manually are denoted by ‘(M)’.

Select file ...

Name File date

Acacia_Rd_01 Wed Dec 11 11:00:47 1997Acacia_Rd_02 Wed Dec 11 11:00:56 1997

Belco_St_01 Fri Nov 29 12:00:01 1997

Restore FIles

Elmdale_Ave_ Mon Dec 2 14:26:11 1997

Cancel

(A)(M)(M)(A)

Confirm



Procedure 3-6Restoring from a copy of another NE’s configuration

Step Action

1 Position the mouse pointer over the required NE in the Network Element Access window and press the left-hand mouse button to select it.

2 Press the right-hand mouse button anywhere in the window to open the popup menu and select Restore as a copy. The Restore Files window is displayed.

3 Position the mouse pointer over the required backup file and select it by pressing the left mouse button.

4 Position the mouse pointer over the Confirm button, and select it by pressing the left mouse button.



—end—

Restoring from a templateThe restore process can be performed using a template file. The Restore Templates window is used to perform this action (see below).

Select file ...

Name File date

position_1 Wed Dec 11 11:00:47 1997position_2 Wed Dec 11 11:00:56 1997

through_conn Fri Nov 29 12:00:01 1997

Restore Templates

head_end_mux Mon Dec 2 14:26:11 1997

CancelConfirm



�

The Restore Templates window (see above) lists all templates created using the Element Controller. Each template file is a historical copy of an NE’s configuration information, and will have been created by a manual backup process from inside the EC-1 software (see “Backing up a configuration table using Preside EC-1 software” on page 3-3). From this list, select one template for use.

Note: A list of saved templates can be viewed, and templates can be deleted, via the Templates window (see Preside EC-1 Element Controller User Procedures, NTP 323-1091-402).

Procedure 3-7Restoring from a template

Step Action

1 Position the mouse pointer over the required NE in the Network Element Access window and press the left-hand mouse button to select it.

2 Press the right-hand mouse button anywhere in the window to open the popup menu and select Restore from a template. The Restore Files window is displayed.

3 Position the mouse pointer over the required template file and select it by pressing the left mouse button.

4 Position the mouse pointer over the Confirm button, and select it by pressing the left mouse button.



—end—



Restoring a configuration table from the CATThis process restores a backed up NE configuration table from the CAT’s hard drive. It is loaded to the inactive configuration table on the NE. This may be required if the configuration tables have become corrupted, or if the user would like to revert to a previous configuration.

Procedure 3-8Restoring a configuration table from the CAT

Step Action






If the Config upgrade status is ‘Ready-to-activate’, a Configuration table has been restored but has not yet been activated and the ‘Restore’ command is not available. Use Procedure 3-10 to activate a restored configuration table.

If the Config upgrade status is ‘Ready-to-commit’, the restored table is already active and the ‘Restore’ command is not available. Use Procedure 3-11 to commit to the configuration.

4 Execute the ‘Restore’ command by selecting:Restore

—continued—

ATTENTIONIt is recommended that the Preside EC-1’s ‘Restore NE’ function is used on managed NEs in preference to the functions available from a Browser User Interface session. This minimises the possibility of errors when file names are specified.






�

Procedure 3-8 Restoring a configuration table from the CAT (continued)

Step Action

5 The Browser responds by opening/refreshing a parameter input window with a text entry box for the local path and filename of the backup configuration. The window also provides a ‘Submit’ and a ‘Clear’ button.

6 Enter the configuration table path and filename. This must be a full hierarchic reference up to 50 characters in length, and must include the drive letter. For example, ‘C:\TN-1X_R8\241098’.


7 The progress of the restore operation can be monitored using the ‘htmserv’ application. From the Windows95 Taskbar (at the bottom of the screen by default), maximise the ‘htmserv’ task. The ‘htmserv’ window is then displayed.



10 If the download is successful, the next stage is to switch to the restored configuration table, see Procedure 3-10.

—end—

CAUTIONConfirming restore operationOnce the ‘Submit’ button has been pressed (see step 6), it should not be pressed a second time. No additional operations should be actioned via the Browser User Interface until the restore process has completed.

ATTENTIONWhen restoring a configuration table from a CAT, the long file and directory names that are supported by Windows 95 can cause the Browser User Interface’s restore function to abort. When using the Browser, the file hierarchy that contains backed up configuration files must only use file and directory names up to eight characters in length. Longer directory and file names will be truncated into DOS format names (indicated by a tilde (‘~’) character at the beginning of the name), which cannot be processed by the Browser.



Restoring a configuration table from the Preside EC-1 Element ControllerThis process restores a backed up NE configuration table from the Preside EC-1’s hard drive. It is loaded to the inactive configuration table on the NE. This may be required if the configuration tables have become corrupted, or if the user would like to revert to a previous configuration.

Procedure 3-9Restoring a configuration table from the Preside EC-1

Step Action





4 If the Config upgrade status is not ‘Stable’, the Configuration tables are not identical.

If the Config upgrade status is ‘Ready-to-activate’, a Configuration table has been restored but has not yet been activated and the ‘Restore’ command is not available. Use Procedure 3-10 to activate a restored configuration table.

If the Config upgrade status is ‘Ready-to-commit’, the restored table is already active and the ‘Restore’ command is not available. Use Procedure 3-11 to commit to the configuration.

5 Execute the ‘Restore’ command by selecting:Restore

—continued—

ATTENTIONIt is recommended that the Preside EC-1’s ‘Restore NE’ function is used on managed NEs in preference to the functions available from a User Interface session. This minimises the possibility of errors when file names are specified.






�

Procedure 3-9 Restoring a configuration table from the Preside EC-1 (continued)

Step Action

6 The Browser responds by opening/refreshing a parameter input window with a text entry box for the local path and filename of the backup configuration. The window also provides a ‘Submit’ and a ‘Clear’ button.

7 Enter the configuration table path and filename. This must be a hierarchic reference up to 50 characters in length. If the recommended directory structure (‘~sdhms/data/’) is used, this element of the hierarchy may be omitted.




9 The TN-1X generates the following message when the restore process is complete. This messages will be displayed by the Browser when it next refreshes its windows. This occurs whenever the current menu changes, or an additional command is issued to the TN-1X.

Unsolicited messages

10 If the restore is successful, the following report is then displayed:


Note: If the following report is not displayed automatically, it can be accessed from a hyperlink that is added above the current menu in the main Netscape window.

11 The next stage is to switch to the restored configuration table, see Procedure 3-10.

—end—

Operation Status User Date Time

Restore Completed 13/06/1997 14:30:21



CFG 9.0E 9.0E Ready_to_activate



Activating a restored NE configuration tableAfter new configuration data has been restored to the inactive configuration table, the user can switch to and test this new configuration. The configuration status must be ‘Ready-to-activate’ before switching to the restored configuration.

Procedure 3-10Activating a restored NE configuration table

Step Action




3 The Config upgrade status ‘Ready_to_activate’ should appear in the report.

If the status is ‘Stable’, the ‘Switch_to_Restored’ command is not available. Use Procedure 3-8 to restore a configuration table.

If the status is ‘Ready-to-commit’, the restored table is already active, the ‘Switch_to_Restored’ command is not available. Use Procedure 3-11 to commit to the configuration.

4 Execute the ‘Switch_to_restored’ command by selecting:Switch_to_restoredThis command requires confirmation.

—end—



CFG 9.0E 9.0E Ready_to_activate



�

Committing to the new NE configuration dataAfter successfully testing a new configuration table, the user must commit to the new version. This procedure overwrites the old configuration data with the new.

Procedure 3-11Committing to the new NE configuration data

Step Action




3 The Config upgrade status ‘Ready_to_commit’ should appear in the report.

If the status is ‘stable’, the ‘Commit’ command is not available. Use Procedure 3-8 to restore a configuration table.

If the status is ‘Ready_to_activate’, the restored table is not currently active and the ‘Commit’ command is not available. Use Procedure 3-10 to activate the new configuration table.

4 Execute the ‘Commit’ command by selecting:CommitThis command requires confirmation.

—end—



CFG 9.0E 9.0E Ready_to_commit



Backing out to the old NE configuration dataIf, when testing a new configuration table, it proves unsatisfactory, the user must backout to the old version. It is necessary to switch back to the old configuration before ‘backing out’ as this procedure overwrites the new configuration data.

Procedure 3-12Backing out to old NE configuration data

Step Action


2 Verify that the Configuration Table (CFG) upgrade status is ‘Ready_to_commit’. Execute the ‘View’ command by selecting:ViewThe following report is displayed:


3 Execute the ‘Switch_to_Original’ command by selecting:Switch_to_originalThis command requires confirmation.

4 Execute the ‘BackOut’ command by entering:BackoutThis command requires confirmation.

—end—



CFG 9.0E 9.0E Ready_to_commit



�

Detached modeIf the Subrack Controller detects that there is a mismatch between the configuration table and the current traffic configuration, the Subrack Controller enters the Detached mode (see TN-1X System Description, NTP 323-1061-100 for details).

Exiting Detached mode — Impose_config commandThe Impose_config command imposes the active configuration table settings onto the traffic cards. This will result in a loss of traffic if there is a difference between the active configuration table settings and the traffic settings.

Procedure 3-13Exiting Detached mode — Impose_config command

Step Action

1


3 Execute the ‘Impose_config’ command by selecting:Impose_configThis command requires confirmation.

—end—

Exiting Detached mode — Default commandThe Default command resets the active configuration table to the TN-1X default settings. This will force the TN-1X to exit Detached mode if the Subrack Controller is a new or replacement unit, or is cyclically rebooting.

Procedure 3-14Exiting Detached mode — Default command

Step Action


2 Execute the ‘Default’ command by selecting:DefaultThis command requires confirmation.

—end—

CAUTIONTraffic affectingEnsure that no traffic is being carried before performing the Impose_config command.



Exiting Detached mode — Cold restartIf the TN-1X is not carrying traffic, a cold restart will clear Detached mode. A cold restart is traffic affecting so cannot be used when traffic is carried.

Procedure 3-15Exiting Detached mode — Cold restart

Step Action

1

2 Access the Admin/Sw submenu by selecting:AdminSw

3 Execute the ‘Cold_restart’ command by selecting:Cold_restartThis command requires confirmation.

—end—

Entering Detached mode — Forced_detached commandThe Forced_detached command forces the TN-1X into detached mode irrespective of the configuration status. This does not affect traffic.

Procedure 3-16Exiting Detached mode — Forced_detached command

Step Action


2 Execute the ‘Forced_detached’ command by selecting:Forced_detachedThis command requires confirmation.

—end—

CAUTIONCold restarts are traffic affectingEnsure that no traffic is being carried before performing the cold restart.



�

Entering Detached mode — Default commandThe Default command overwrites the active configuration table with the TN-1X default settings. This creates a mismatch between the active configuration table and the actual traffic card configuration.

Procedure 3-17Exiting Detached mode — Default command

Step Action


2 Execute the ‘Default’ command by selecting:DefaultThis command requires confirmation.

—end—

end of chapter


4-1

�

Viewing TN-1X software releases 4-Software release information

The current software release of the TN-1X can be determined in a number of ways using the TN-1X UI software and from the Preside EC-1 Element Controller.

• Login reports.

• Admin/Sw/View UI command.

• Session/Get_mux_status UI command.

• Using the Preside EC-1 Element Controller ‘System Information’ command.

The software release number is given as a five character code, and the bank containing the active (running) software is shown. For example:


In this example, software version 9.6A is running in bank B, and the other software bank (bank A) also contains version 9.6A. The active software bank can be either A or B, software download is always to the other software bank.

Software release information displayed via login reportsThere are a number of login report hyperlinks listed at the top of the screen after logging in. These reports provide system information that may be of interest immediately after login, and are only accessible the first time you visit this screen during a session.

To access a login report, click on its hyperlink. A report window is opened displaying the following information for software and configuration tables:

• active version and bank

• standby version and bank

• upgrade status


SW 9.6A B 9.6A Stable


4-2 Viewing TN-1X software releases


Software release displayed via the Admin/Sw/View commandInformation on the software release can be viewed using the TN-1X Admin/Sw menu. The software upgrade status is also displayed, this can be one of the following:

• StableThe software banks contain the same software version.

• Ready_to_activateThe user has downloaded new software, the latest loaded software version is in the inactive bank.

• Ready_to_commitThe user has downloaded new software, the latest loaded software version is in the active bank.

• Download_in_progressSoftware is being downloaded to the inactive bank.

• Checksum_bankThe download process was aborted, new software must be downloaded or the active software must be copied to the inactive bank.

Procedure 4-1Viewing the software release — Admin/Sw menu

Step Action

1 Access the ‘Admin/Software’ submenu by selecting:AdminSw

2 Execute the ‘View’ command by selecting:ViewNo confirmation is required.

3 A report window is opened/refreshed displaying the following information for software and configuration tables:



• upgrade status


—end—




Viewing TN-1X software releases 4-3


�

Software release displayed via the Session/Get_mux_status menuInformation on the software release and upgrade status can also be viewed via the TN-1C Session/Get_mux_status menu.

Procedure 4-2Viewing the software release — Session/Get_mux_status menu

Step Action

1 Access the ‘Session’ menu by selecting:Session

2 Execute the ‘Get_mux_status’ command by selecting:Get_mux_statusNo confirmation is required.

3 Further menu items are displayed allowing the user to select the report type required. The reports available are:

• NE time

• Inventory

• Open sessions

• Software and config table status

• Loopback configuration

• Alarm status

4 To display the current software release, select:Software and config table status

5 A report window is opened/refreshed displaying the following information for software and configuration tables:



• upgrade status


—end—




4-4 Viewing TN-1X software releases


Preside EC-1 Release 10 ‘System Information’ commandThe system information window provides the general information and software version/channel numbering scheme information for each of the variants as follows:

• General information:

— Nortel Networks Logo and copyright.

— Current user name.

— Current duty class.

— Current Preside EC-1 host name.

— Maximum main sessions.

— Maximum reach-throughs.

— NRM interface status.

— Preside EC-1 Area Address.

— Preside EC-1 Mac Address.

— Preside EC-1 software version.

• TN-1X information:

— TN-1X NE load image software version.

• TN-1C information:

— TN-1C NE load image software version(s).

• TN-1P information:

— TN-1P NE load image software version(s).

Procedure 4-3Viewing system information

Step Action

1 Select the System Information button from User Functions within the Main Menu. The button turns blue to indicate selection and the System Information window is displayed.

2 Select the OK button to close the window.

—end—

end of chapter


5-1

�

Software administration 5-Application software

TN-1X application software is stored in non-volatile memory on the Subrack Controller. The Subrack Controller also holds foundation software which includes the operating system and the hardware/software initialisation code.

One copy of the TN-1X application software is held in each bank of flash application memory on the Subrack Controller. The versions held in each bank should be the same at all times except during the software upgrade process. As only one flash memory copy of the application software can be selected by the TN-1X foundation software at any given time, the software in the non-active bank can be updated while the other copy is running.

The TN-1X contains an automatic reversion facility. If the selected application software fails to start-up successfully, the alternative bank (if available) is selected and started. In the unlikely event of both software banks failing, the Subrack Controller should be replaced.

Upgrading application softwareThe software upgrade procedure must start with the software upgrade status and the config upgrade status in the ‘Stable’ state. This can be verified using the Admin/Sw/View command (see page 4-2).

The ‘Stable’ software upgrade status shows that both software banks contain the same, functioning version of the application software. New application software is downloaded into the inactive flash memory bank from either the CAT or the Preside EC-1 Element Controller. The user is then able to switch to the new software in order to test it while retaining the previous software version in the other bank; this permits the user to ‘retreat’ to the previous version should the new version prove unsatisfactory.

CAUTIONSwitching from Release 9 to Release 8 or Release 7If the TN-1X is switched from Release 9 software to Release 8 or Release 7 software, the configuration will be lost, the TN-1X will enter detached mode, and traffic will be hit.

5-2 Software administration


The TN-1X has two configuration tables, one an active table and the other an inactive table. At the time of a software upgrade, each configuration table becomes associated with a flash memory bank. In this situation, configuration changes made using the new software are not reflected in the configuration table associated with the original software. If the user then reverts to the original software, the changes are lost.

To avoid losing configuration data, the software versions in each flash memory bank should be the same whenever possible. After a short period of testing, if the new software proves satisfactory, the user should commit to the new software (this replaces the old software in the inactive bank with a copy of the new software). The TN-1X is then once more in a stable configuration. If the new software is unsatisfactory, the user should revert to the original software (this replaces the new software in the inactive bank with a copy of the old software).

Note: The Element Controller contains an Automatic Script Driver (ASD) which allows certain software procedures (Download, Commit, Backout, and Copy) to be performed on a number of TN-1X NEs in a single operation (see Preside EC-1 Element Controller User Procedures, NTP 323-1091-402).

Removal of trib-to-trib connectionsPrior to an upgrade to Release 9, any Release 8 trib-to-trib connections provisioned via the Preside EC-1/INM should be manually removed.

If the trib-to-trib connections are not removed, the mux will enter DETACHED mode on upgrade from R8 to R9. The user must then manually delete the trib-to-trib connections, before imposing config. This also applies to any 'Config Restore' functionality provided. If a Release 8 config store (containing trib-to-trib connections) is restored onto a mux configured with release 9 software, the software will enter DETACHED mode until any trib-to-trib connections are manually removed and the new configuration is imposed.

Once an upgrade from Release8 to Release 9 has completed a manual defragmentation does not need to take place.

ATTENTIONThe internal bus of the TN-1X is mapped differently at R9 than at earlier releases. While this does not affect the operation of current connections, future connections may not benefit from improved Release 9 performance and may also generate traffic hits to existing connections as a result of adding new connections. Customers should refer to Engineering Bulletin - Connections Recommendations SDH_E155 for advice on how to proceed after upgrade. This will be dependant on the previous release level & traffic configuration.

Software administration 5-3


�

Software statusThe software status can be checked at all times by using the Admin/Sw/View command (see page 4-2). This should be checked during the software upgrade process as, if the status is not correct for the operation being attempted, then the operation will fail. The software upgrade status can be one of the following:

• Stable. Both software banks contain the same version of software.

• Ready_to_activate. New software has been downloaded, and this is in the inactive bank.

• Ready_to_commit. New software has been downloaded, and this is in the active bank.

• Download_in_progress. Software is downloading to the inactive bank.

• Checksum_bank. The download was aborted, or a software bank has been corrupted. New software must be downloaded, or the active software must be copied to the inactive bank.



Figure 5-1Software upgrade overview

Start

New software available

Test new software

Is new software

OK?

Yes

No

Finish

Both configuration tables contain the original software.

The active bank contains the original software, and the inactive bank now contains the new software.

The two versions of the software change places. While the new software is being tested, the original software is in the inactive software bank.

If the new software is satisfactory, the user can decide to commit to it. If the new software proves unsatisfactory, then the user must back out, reverting to the original software. In either case, the software in both banks is the same version.

Switch to new software

Download new software to

inactive bank

Switch back to original software

Backout

Old software in both tables

Commit to new software

New softwarein both tables

During normal operation, it is important that both banks contain the same software. If these are different, this can interfere with the operation of configuration functions.



�

Preparing application software for download on CATTN-1X application software that is intended for download from the CAT is supplied compressed on 3.5 inch floppy disks. This must be copied to a directory on the CAT hard (fixed) disk and decompressed before downloading to the TN-1X. The compressed files are supplied in a self extracting archive format. With this compression system, the files are provided as an executable file which, on execution, extracts the file into the same directory.

Procedure 5-1Preparing application software for download on CAT

Step Action

1 Switch the CAT, and wait for Windows95 to start.

2 Insert the application software disk into the floppy drive of the CAT.

3 From the ‘Start’ menu, open the ‘Programs’ menu and start the ‘Windows Explorer’ application.

4 Create a directory in the root of the CAT’s hard drive called ‘TN-1X_R9’.

5 Copy the ‘tn1x9nn.exe’ file from the floppy disk to the ‘TN-1X_R9’ directory (where ‘9nn’ represents the current R8 version number of the software).

6 Execute the ‘tn1x9nn.exe’ file by double clicking on it. The file will decompress as a file called ‘tn1x9nn.b’ in the ‘TN-1X_R9’ directory.

7 Close the ‘Windows Explorer’ application. The application software is ready for use.

—end—



Preparing application software for download on Preside EC-1 Element Controller

TN-1X application software that is intended for download from the Preside EC-1 is supplied on DAT tape. This must be copied to a directory that the Preside EC-1 is able to access before downloading to the TN-1X. This procedure must be carried out by a System Engineer class user at a UNIX prompt.

Procedure 5-2Preparing application software for download on Preside EC-1

Step Action

1 Insert the application software DAT tape into the tape drive of the Preside EC-1.

2 On the Preside EC-1, start a UNIX session.

3 Change directory to the NE_loads directory by entering:

cd ~/sdhms/data/NE_load/1X ↵4 Copy the software file to this directory by entering:

tar xv ↵5 The software file is placed in the following directory:

~/sdhms/data/NE_load/1X

—end—



�

Downloading application software from the CATApplication software can be downloaded from the CAT’s hard drive to the TN-1X. The user identifies the application software to be downloaded (prepared in Procedure 5-1). The identified file is then transferred to the TN-1X network element.

Procedure 5-3Downloading application software from the CAT

Step Action

1 Login to the TN-1X NE from the CAT using Procedure 8-1.

2 Access the Admin/Software submenu by selecting:AdminSw

3 Verify that the Software (SW) upgrade status and the Configuration Table (CFG) upgrade status are both ‘Stable’. Execute the ‘View’ command by selecting:

ViewThe following report is displayed (the version numbers are examples):


4 The Software and Configuration table upgrade status must both be ‘Stable’, if any other status is reported, the upgrade can not take place.

If the Configuration table upgrade status is not ‘Stable’, see Chapter 3, “Configuration data administration”.

If the Software upgrade status is not ‘Stable’, the software banks do not contain the same software or configuration version and the ‘Download’ command is not available.

If the Software status is ‘Ready_to_activate’, the new software has been downloaded but has not yet been activated (use Procedure 5-5 to activate this software).

If the Software status is ‘Ready_to_commit’, the new software is already active (use Procedure 5-6 to commit to the software).

5 Execute the ‘Download’ command by selecting:Download

—continued—






Procedure 5-3 Downloading application software from the CAT (continued)

Step Action

6 The Browser responds by opening/refreshing a parameter input window with a text entry box for the new software filename. The window also provides a ‘Submit’ and a ‘Clear’ button.

7 Enter the software image path and filename. This must be a full hierarchic reference up to 50 characters in length, and must include the drive letter. For example, ‘C:\TN-1X_R9\tn1x9nn.b’.


8 The progress of the software download operation can be monitored using the ‘htmserv’ application. From the Windows95 Taskbar (at the bottom of the screen by default), maximise the ‘htmserv’ task. The ‘htmserv’ window is then displayed.



11 If the download is successful, the mux will then reboot. This will terminate the current Browser User Interface session. Click on the ‘Logout’ button. The NE Login screen is then displayed.

12 The next stage is to switch to the alternative software bank. This is detailed in Procedure 5-5.

—end—

CAUTIONConfirming software download operationOnce the ‘Submit’ button has been pressed (see step 7), it should not be pressed a second time. No additional operations should be actioned via the Browser User Interface until the software download process has completed.

ATTENTIONWhen downloading a software image from a CAT, the long file and directory names that are supported by Windows 95 can cause the Browser User Interface’s download function to abort. When using the Browser, the file hierarchy that contains the software image must only use file and directory names up to eight characters in length. Longer directory and file names will be truncated into DOS format names (indicated by a tilde (‘~’) character at the beginning of the name), which cannot be processed by the Browser.



�

Downloading application software from the Preside EC-1Application software can be downloaded from the EC-1’s hard drive to the TN-1X. The user identifies the application software to be downloaded (prepared in Procedure 5-2). The identified file is then transferred to the TN-1X network element.

Procedure 5-4Downloading application software from the Preside EC-1

Step Action

1 Login to the TN-1X NE from the Preside EC-1 using Procedure 8-2.

2 Access the Admin/Software submenu by selecting:AdminSw

3 Verify that the Software (SW) upgrade status and the Configuration Table (CFG) upgrade status are both ‘Stable’. Execute the ‘View’ command by selecting:



4 The Software and Configuration table upgrade status must both be ‘Stable’, if any other status is reported, the upgrade can not take place.

If the Configuration table upgrade status is not ‘Stable’, see Chapter 3, “Configuration data administration”.

The Software upgrade status is not ‘Stable’, the software banks do not contain the same software or configuration version and the ‘Download’ command is not available.

If the Software status is ‘Ready_to_activate’, new software has been downloaded but has not yet been activated (use Procedure 5-5 to activate this software).

If the Software status is ‘Ready_to_commit’, the new software is already active (use Procedure 5-6 to commit to the software).

5 Execute the ‘Download’ command by selecting:Download

No confirmation is required.

—continued—






Procedure 5-4 Downloading application software from the Preside EC-1 (continued)

Step Action

6 The Browser responds by opening/refreshing a parameter input window with a text entry box for the new software filename. The window also provides a ‘Submit’ and a ‘Clear’ button.

7 Enter the software image path and filename. This must be a hierarchic reference up to 50 characters in length. If the recommended directory structure (‘~sdhms/data/’) is used, this element of the hierarchy may be omitted.




9 During the software download process, the TN-1X generates a number of messages that track the progress of the operation. These messages will be displayed by the Browser whenever its refreshes its windows. This occurs whenever the current menu changes, or an additional command is issued to the TN-1X.

—continued—



�

Procedure 5-4 Downloading application software from the Preside EC-1 (continued)

Step Action

10 The following messages will be seen from the Browser. The groupings of these messages depends on how frequently the Browser windows are refreshed:

Software Events

11 If the download is successful, the following report is then displayed (the version numbers are examples):


Note: If the following report is not displayed automatically, it can be accessed from a hyperlink that is added above the current menu in the main Netscape window.

12 If the download is successful, the next stage is to switch to the alternative software bank, see Procedure 5-5.

—end—

Operation Status User Reason Date Time

Download Started 13/06/1997 16:56:14

Download preparation in progress... 13/06/1997 16:56:14

Flash erase confirmation (1) in progress... 13/06/1997 16:56:42

Flash erase confirmation (2) in progress... 13/06/1997 16:56:49

Download preparation complete. 13/06/1997 16:56:55

Download operation 12.5% complete... 13/06/1997 17:00:10








Download Complete 13/06/1997 17:07:00


SW 9.6A A 9.7A Ready_to_activate




Aborting a software downloadIt is possible to abort a software download process that was initiated from a Browser User Interface session on the Preside EC-1 platform.

Note: It is not possible to abort a software download process that was initiated from a Browser User Interface session on the CAT.

The abort process erases the partially downloaded software, and automatically copies the software in the active bank into the inactive bank. This returns the mux to a stable condition.

Switching to the alternative software bankAfter a new software version has been successfully downloaded to the flash memory bank not in use, the user can switch to the second flash memory bank and test the new software. Switching to the other software bank initiates a Warm Restart.

Procedure 5-5Switching to the alternative software bank

Step Action


2 Ensure that the configuration status is ‘Stable’ and the software upgrade status is ‘Ready_to_activate’ by executing the ‘View’ command, select:



3 The Upgrade Status ‘Ready_to_activate’ should appear in the report.

If the status is ‘Ready_to_commit’, the new software is already active (use Procedure 5-6 to commit to the software).

If the status is ‘Stable’, both software banks (active and inactive) contain the same software version.

For all except the ‘Ready_to_activate’ status, the ‘Switch_to_Loaded’ command is not available.

4 Execute the ‘Switch_to_Loaded’ command by selecting:Switch_to_loaded

This command requires confirmation.

—end—


SW 9.6A A X9.02A Ready_to_activate




�

Committing to new TN-1X softwareAfter successfully testing a new software version, the user must commit to the new software version.

Procedure 5-6Committing to new TN-1X software

Step Action


2 Ensure that the configuration status is ‘Stable’ and the software upgrade status is ‘Ready_to_commit’ by executing the ‘View’ command, select:



3 The Upgrade status ‘Ready_to_commit’ should appear in the report.

If the status is ‘Ready_to_activate’, the new software has been downloaded but has not yet been activated (use Procedure 5-5 to activate this software).

If the status is ‘Stable’, both software banks (active and inactive) contain the same software version.

For all except the ‘Ready_to_commit’ status, the ‘Commit’ command is not available.

4 Execute the ‘Commit’ command by selecting:Commit


5 Using the ‘View’ command, ensure the software Upgrade status is ‘Stable’.

—end—


SW 9.7A B 9.6A Ready_to_commit




Backing out to old TN-1X softwareAfter testing a new software version that proves unsatisfactory, the user should backout to the original TN-1X software. In this process, the configuration changes made during the software test are lost.

Procedure 5-7Backing out to the original TN-1X software

Step Action


2 Ensure that the configuration status is ‘Stable’ and the software Upgrade status is ‘Ready_to_commit’ or ‘Ready_to_activate’ by executing the ‘View’ command, select:



3 The Upgrade_status ‘Ready_to_commit’ or ‘Ready_to_activate’ should appear in the report.

If the status is ‘Ready_to_commit’, proceed to step 4.

If the status is ‘Ready_to_activate’, proceed to step 6.

For all except the ‘Ready_to_commit’ status, the ‘Switch_to_Original’ command is not available.

4 Execute the ‘Switch_to_Original’ command by selecting:Switch_to_original

This command requires confirmation. You are logged out of the network element during this process.

5 Login to the network element and use the ‘View’ command to ensure that the software Upgrade status is ‘Ready_to_activate’.

6 Execute the ‘BackOut’ command by entering:Backout


7 Using the ‘View’ command, ensure the software ‘Upgrade status’ is ‘Stable’.

—end—

CAUTIONSwitching from Release 9 to Release 8 or Release 7If the TN-1X is switched from Release 9 software to Release 8 or release 7 software, the configuration will be lost, the TN-1X will enter detached mode, and traffic will be hit.


SW 9.7A B 9.6A Ready_to_commit




�

Restarting the TN-1XThe TN-1X provides the user with two restart options, both can be triggered using standard UI commands:

• Cold Restart - a hardware reset is performed on system power-up. Initiating a cold restart during TN-1X operation is traffic affecting.

• Warm Restart - if a software fault occurs, the software is reset; this alone should not affect the traffic.

The ‘Warm_Restart’ command can be modified to restart the TN-1X using the other software bank. This requires the additional parameter ‘other’ to be entered in the dialogue box.

Procedure 5-8Restarting the TN-1X

Step Action

1 Access the ‘Admin/Sw’ submenu by selecting:AdminSw

2 To: Do this:

Confirmation is required.

3 To: Do this:

4 The browser responds by opening/refreshing a parameter input window with a text entry box for the optional parameter ‘other’. The window also has a ‘Submit’ and a ‘Clear’ button.

5 To: Do this:

These commands require confirmation.

—end—

end of chapter

Perform a cold restart Execute the ‘Cold_restart’ command by selecting:

Cold_restart

Perform a warm restart Execute the ‘Warm_restart’command by selecting

Warm_restart

Perform a warm restart using the current software bank

Select the ‘Submit’ button.

Perform a warm restart, and run the software in the other bank

Enter the text ‘other’ in the text entry box and select the ‘Submit’ button.


6-1

�

Log administration 6-Log storage and formatting

Logs are stored on the Element Controller in the following directories:

• Event logs are stored in the ‘sdhmsusr/sdhms/logs’ directory.

• Performance monitoring logs are stored in the ‘sdhmsusr/sdhms/pm’ directory.

Where the logs are stored in a compressed format, a ‘Z’ extension is used to indicate compressed logs. When the logs are viewed, printed or saved, the Element Controller uncompresses the logs so that they can be read. No additional user actions are required in this instance.

If the logs are copied via UNIX (for example, for use in other applications), the logs will have to be uncompressed before being used.

If the logs are just being viewed, it is recommended that the UNIX command ‘zcat’ is used with the ‘more’ pipeline rather than using the ‘uncompress’ command. For example:

zcat <logname.Z> | more

Archiving logsLogs are automatically compressed after seven days. If you wish to delete logs to save space, they need to be archived off the system.

Log files are automatically assigned file names that comprise the system date and time, and the type of log, in the format:

<week day>.<day of month><Month>.<year><type>

Where:

• <week day> is ‘Mon’, ‘Tues’, ‘Wed’, ‘Thus’, ‘Fri’, ‘Sat’, or ‘Sun’.

• <day of month> is 01 to 31.

• <month> is the month in abbreviated form.

• <year> is the last two digits of the year.

6-2 Log administration


• <log type> is given as:

— EL for Event Logs.

— TL for Transaction Logs.

— PL for Performance Logs.

For example:

Mon.21Aug95.EL

Note: Transaction Logs are used by Nortel Networks system engineers as an aid to fault-finding.

Procedure 6-1Perform on-line archive of logs

Step Action

1 Login as System Engineer and select the UNIX Window from the Main Menu.

2 Load a blank tape into the device.

3 Change directory by typing:

cd /home/sdhmusr/sdhms

4 Archive the entire logs directory by typing:

tar cvf /dev/rmt/0m logs

5 Close the UNIX window.

—end—

Log administration 6-3


�

Viewing archived logsWhen archived logs are to be viewed, they must be retrieved from tape, then viewed using an editor such as ‘vi’.

Note: Never restore the logs to the sdhmsusr/sdhms/logs directory. Restored logs must be placed in a temporary directory.

Procedure 6-2Viewing archived logs

Step Action

1 Login as System Engineer and select the UNIX Window from the Main Menu.

2 Load the archive tape into the tape device.

3 Make a temporary directory to restore the logs by typing:

mkdir ~/temp

4 Change directory to the temporary directory by typing:

cd ~/temp

5 Restore the logs by typing:

tar xvf /dev/rmt/0m logs

6 View the required log by typing:

cd logsvi <logfile>

where <logfile> is the filename of the required log.

7 On completion, remove the restored logs by typing:

cd

followed by:

rm -rf temp


—end—

end of chapter


7-1

�

Monitoring network status 7-Viewing alarm information

The Alarm Monitoring window is displayed when you log into the Preside EC-1 Element Controller. This can be configured to display information in one of three modes:

• Alarm Count Only.

• Active Alarm List.

• Alarm Log List.

Only one mode can be selected at a time by selecting the appropriate button.

Viewing alarm count onlyThis is the default mode and displays an alarm count of all outstanding alarms in the Element Controller alarm database. It is updated in real time and a separate count is displayed for Critical, Major and Minor alarm severities.

If a change to the alarm count occurs, the window is brought to the front of any overlying windows and the corresponding alarm severity count is updated. Each update is accompanied by a brief alarm sound.

• If the count is incremented (that is, an alarm occurs), the background rectangle of the relevant number is momentarily displayed in red.

• If the count is decremented (that is, an alarm is cleared), the background rectangle of the relevant number is momentarily displayed in green.

ALARM_MONITORING EC-1 R10 bigsm234

View Active Alarm List

Alarm Bell

View Alarm Log List View Alarm Count Only

Critical

6

Major

5

Minor

5Alarm Count

7-2 Monitoring network status


Viewing active alarm listIn this mode, the Alarm Monitoring window is extended to contain a scrollable read-only list containing all outstanding alarms.

The list is refreshed automatically whenever an alarm is raised or cleared. In the case of an alarm being raised, the alarm details are appended to the end of the list, and in the case of an alarm being cleared, the instance of that alarm is removed from the list. Details of alarm formats, types and attributes are given in “Alarm report formats” on page 7-3

Viewing alarm log listIn this mode, the Alarm Monitoring window is extended to contain a read-only log of all raised and cleared alarms for the network. The list maintains the most recent 200 alarm events generated during the current login session. If this number is exceeded, the oldest entries are overwritten. Details of alarm formats and attributes are given in “Alarm report formats” on page 7-3.

Status indicatorsSome alarm log entries generated by the Element Controller, are alarm log status indicators unrelated to network elements. These entries are timestamped and displayed in a similar format to the first entry in the figure above. No slip number is assigned to status indicators.

ALARM_MONITORING EC-1 R10 bigsm234


Alarm Bell


Critical

12

Major

6

Minor

7Alarm Count

Status Severity Affected Element Alarm Time/Date Slip

present Critical /bigsm234/TN-1X/Alpha7/S9 NE-Card_Out 02/04/99 15:01:05 812present Critical /bigsm234/TN-1X/ALpha7/S11 NE-Card_Out 02/04/99 15:01:05 813present Critical /bigsm234/TN-1X/Alpha7/S13 NE-Card_Out 02/04/99 15:01:05 814present Critical /bigsm234/TN-1X/Alpha7/S14 NE-Unexpected_Lan 02/04/99 15:01:05 815present Critical /bigsm234/TN-1P/Beta7/A RS-Loss_Of_Signal 02/04/99 15:01:52 816present Critical /bigsm234/TN-1P/Beta7/S1-1 PPI-Loss_Of_Signal 02/04/99 15:01:52 817

Type User Label

ALARM_MONITORING EC-1 R6 bnsgh84


Alarm Bell


Critical

12

Major

6

Minor

7Alarm Count

Status Severity Affected Element Alarm Time/Date Slip

Present Critical /bigsm234/TN-1X/Alpha7/S9 NE-Card_Out 02/04/99 15:01:05 812Present Critical /bigsm234/TN-1X/Alpha7/S11 NE-Card_Out 02/04/99 15:01:05 813Cleared Critical /bigsm234/TN-1X/Alpha7/S11 NE-Card_Out 02/04/99 15:01:35 814Present Critical /bigsm234/TN-1X/Alpha7/S14 NE-Unexpected_Lan 02/04/99 15:11:05 815Present Critical /bigsm234/TN-1P/Beta7/A RS-Loss_Of_Signal 02/04/99 15:11:52 816Present Critical /bigsm234/TN-1P/Beta7/S1-1 PPI-Loss_Of_Signal 02/04/99 15:11:52 817

Type User Label

Monitoring network status 7-3


�

Clearing the alarm log listYou can clear all entries from the Alarm Log List using the ‘Clear’ option available from the View Alarm Log List window.

Procedure 7-1Clearing the alarm log list

Step Action

1 Position the mouse pointer in the background of the lower section of the Alarm Log List window.

2 Press and hold the right-hand mouse button to select Clear. The Alarm Log List is cleared and replaced with an entry recording the operation.

—end—

Alarm report formatsThe data columns within alarms reports, which is used to display alarm information in the screen displays and in the reports and alarm logs, is shown below:

<stat> <sev> <elem> <type> <label> <alarm> <time> <slip>

Where:

• <stat> is the alarm status. This will be set to ‘Present’ or ‘Cleared’. For active alarms, this will always be set to ‘Present’.

• <sev> is the alarm severity. This will be ‘Critical’, ‘Major’ or ‘Minor’, according to the seriousness of their impact (or potential impact).

— Critical. This failure could disable or seriously degrade the services provided by the network.

— Major. This failure could degrade the services provided by the network, but to a lesser degree than a Critical failure.

— Minor. This failure will not degrade the services provided by the network.

These categories are fixed for each alarm type.

• <elem> is the affected element. This identifies the affected NE, and (where applicable), a specific part of the NE.

• <type> is the card type for alarms which are raised against cards.

• <label> is the user label. This is a string of up to fifteen characters.

• <alarm> is the alarm name.

• <time> is the time/date stamp. The time the alarm was raised.

• <slip> is the slip number. A sequential slip number is assigned to events recorded in the Event Log, commencing at ‘1’ at the start of each day. Some ‘non-critical’ events, including status indicators (see “Viewing alarm log list” on page 7-2), are not assigned a slip number.



Collecting PM dataThis option enables you to collect Performance Monitoring (PM) data from a managed NE, and to configure PM data collection.PM reports are collected automatically from every NE when communications are established, and then every 7.5 hours.

There are three types of PM data that can be retrieved:

• 15 minute (all NEs).

• 24 hour (TN-1X and TN-1X/S only).

• Unavailable Time (UAT) timestamps (TN-1X and TN-1X/S only).

These options should only be used if the user suspects a problem with the NE.

When used, the NE sends all of the requested PM data it has accumulated since the last report. If no new PM data has been generated, a failure will be reported in the Messages window. PM reports can be viewed via the Reports function (see Preside EC-1 Element Controller User Procedures Release 14, NTP 323-1091-402).

Procedure 7-2Retrieving PM reports

Step Action


2 Press the right-hand mouse button anywhere in the window to open the popup menu and select Retrieve PMs. A submenu is displayed.

3 Select the required PM type to be retrieved. A confirmation message is displayed. Confirm the action.

4 Select the OK button to retrieve the specified PM data. If no data is available, an error is displayed in the Messages window.

—end—



�

Viewing the active alarm listThe user is able to view a report of all active alarms via a TN-1X Browser session using the CAT or Element Controller. For information on the alarm formatting and an explanation of the fields, see “Alarm report formats” on page 7-3.

Procedure 7-3Viewing the active alarm list

Step Action

1 Access the ‘View_status’ menu by selecting:View_status

2 Execute the ‘Active_Alarms’ command by selecting:Active_AlarmsNo confirmation is required.

3 A report window is opened/refreshed displaying the Active Alarms report.

Alarm Status

—end—

NE-Card_Out S1 Present C P 0020 ICC2

NE-Card_Out S2 Present C P 0367 2M75


RS-LOS S6-1 Present C P 1027 A-1o

RS-LOS S7-1 Present C P 1052 B-1o



NE-Card_Out S13 Present C P 1782 PSU

EA-andrew E1 Present C P 0002 SRC

EA-Ext_inp2 E2 Present C P 0003 SRC



Viewing the alarm logThe TN-1X stores all alarms in the alarm log, a buffer that contains all alarm events for the day.

Procedure 7-4Viewing alarms from the alarm log

Step Action


2 Execute the ‘Alarm_log’ command by selecting:Alarm_logNo confirmation is required.

3 A report window is opened/refreshed displaying the alarm log.

Alarms

—end—

Alarm Type Instance Status Severity Category Unique Number

Instance Type

User Label

Date Time

NE-Card_Out S9 Present C P 1429 2M75 08/01/2001 23:50:49

NE-Card_Out S11 Present C P 1776 2M75 08/01/2001 23:50:50

NE-Card_Out S13 Present C P 1782 PSU 08/01/2001 23:50:50

HP-TIM S6-1-J1 Present M D 0971 A-1o 08/01/2001 23:52:27

HP-LOM S6-1-J1 Present M D 0973 A-1o 08/01/2001 23:52:27

INT-AU-AIS S6-1-J1 Present m I 0981 A-1o 08/01/2001 23:52:28

HP-LOM S6-1-J1 Clear M D 0973 A-1o 08/01/2001 23:52:28



�

Viewing the action logThe TN-1X stores all actions (non-alarm events) in the action log, a buffer that contains all actions for the day.

Procedure 7-5Viewing the action/alarm log

Step Action


2 Execute the ‘Action_log’ command by selecting:Action_logNo confirmation is required.

3 A report window is opened/refreshed displaying the action log.

Events (951)

Events (961)

Events (952)

—end—

Command User Date Time

a/c/ic gregory 09/01/2001 01:14:21

m/o/c/a 09/01/2001 01:16:42 bireh115 09/01/2001 01:16:42

s/a/s 60 gregory 09/01/2001 16:11:40

c/a/t/ms/5 andrew 09/01/2001 16:11:52

c/a/t/ms/5 gregory 09/01/2001 16:27:01

c/a/t/ms/5 gregory 09/01/2001 16:27:45

Session Event Uname User Date Time

Login ec_as bireh115 09/01/2001 01:16:39

Login oper1 alan 09/01/2001 04:16:54

Autologout oper1 alan 09/01/2001 04:34:42

Login oper1 andrew 09/01/2001 16:11:05

Logout oper1 andrew 09/01/2001 16:11:29

Login oper1 andrew 09/01/2001 16:11:44

Logout oper1 andrew 09/01/2001 16:12:15

Login oper1 dtweed 09/01/2001 17:16:26

Old Date Old Time User Date Time

09/01/2001 01:16:40 andrew 09/01/2001 01:16:42



Viewing a specific performance logPerformance logs store the results of individual monitoring periods in which monitoring is active. The performance logs are numbered from ‘1’, with the latest logs having the highest log numbers (entering ‘-1’ as the log number will display the latest log).

The number of performance logs that the TN-1X can store is variable, as it depends upon the size of individual logs. When more errors occur, a log will be longer. When no errors occur, a log is not stored.

Procedure 7-6Viewing a specific performance log

Step Action


2 To view a specific 15 minute performance log, execute the ‘Perf_log’ command by selecting:Perf_logNo confirmation is required.

3 The Browser responds by opening/refreshing a parameter input window with a text entry box for the performance log number. The window also provides a ‘Submit’ and a ‘Cancel’ button.

4 Enter the number of the required performance report and select the ‘Submit’ button. For example, to see the latest report, enter -1.

Performance Monitoring Log

5 To view a 24 hour performance log, execute the ‘24H_Perf_log’ command by selecting:24H_Perf_logNo confirmation is required.

6 The Browser responds by opening/refreshing a parameter input window with a text entry box for the performance log number. The window also provides a ‘Submit’ and a ‘Cancel’ button.

—continued—

Status Log_type Report Duration End_Date End_Time Start_Date Start_Time

NA 15M 2246 900 09/01/2001 18:30:00 09/01/2001 18:15:00



�

Procedure 7-6 Viewing a specific performance log (continued)

Step Action

7 Enter the number of the required performance report and select the ‘Submit’ button. For example, to see the latest report, enter -1.


—end—


NA 24H 164 2102 02/04/1998 00:00:00 09/01/2001 01:14:29

Instance PMP ES SES BBE UAS Basis AS Traffic User_label

S6-1 RS 0 0 0 77357 p 77366 A-1o S6-1

S7-1 RS 0 0 0 77399 p 77408 B-1o S7-1

Instance PMP Total_count -ve_count AS Traffic User_label

S2-1 TU-PJE 0 0 0 2M75 S2-1

S2-2 TU-PJE 0 0 0 2M75 S2-2

S2-3 TU-PJE 0 0 0 2M75 S2-3

S2-4 TU-PJE 0 0 0 2M75 S2-4

S2-5 TU-PJE 0 0 0 2M75 S2-5

S2-6 TU-PJE 0 0 0 2M75 S2-6

S2-7 TU-PJE 0 0 0 2M75 S2-7

S2-8 TU-PJE 0 0 0 2M75 S2-8

S2-9 TU-PJE 0 0 0 2M75 S2-9

S2-10 TU-PJE 0 0 0 2M75 S2-10

S2-11 TU-PJE 0 0 0 2M75 S2-11

S2-12 TU-PJE 0 0 0 2M75 S2-12

S2-13 TU-PJE 0 0 0 2M75 S2-13

S2-14 TU-PJE 0 0 0 2M75 S2-14

S2-15 TU-PJE 0 0 0 2M75 S2-15

S2-16 TU-PJE 0 0 0 2M75 S2-16

S4-1 TU-PJE 0 0 0 2M75 S4-1



Viewing a specific unavailable time logThe TN-1X collects unavailable time data for all Performance Monitoring Points (PMPs). Unavailable time logs store the results of daily monitoring periods. These logs are numbered from ‘1’, with the latest logs having the highest log numbers (entering ‘-1’ as the log number will display the latest log).

The number of logs that the TN-1X can store is variable, as it depends upon the size of individual logs.

Procedure 7-7Viewing a specific performance log

Step Action


2 Execute the ‘Uat_perf_log’ command by selecting:Uat_perf_logNo confirmation is required.

3 The Browser responds by opening/refreshing a parameter input window with a text entry box for the unavailable time log number. The window also provides a ‘Submit’ and a ‘Cancel’ button.

4 Enter the number of the required unavailable time log and select the ‘Submit’ button. For example, to see the latest report, enter -1.


—end—

Status Log_type

NA UAT

Instance PMP Type Traffic User_label Date Time

S6-1 RS Start A-1o S6-1 09/01/2001 01:18:42

S7-1 RS Start B-1o S7-1 09/01/2001 01:18:00



�

Early termination of performance monitoringThe performance monitoring functionality of the TN-1X enables the user to record and report on a number of performance criteria. The results are collected over fifteen minute and/or twenty four hour periods of time. Either or both of these performance monitoring periods can be terminated prematurely.

When a performance monitoring period is terminated prematurely, the results are stored by the NE, and a new monitoring period is started automatically. If there is insufficient capacity to store the new performance monitoring log, the oldest log is deleted. The NE is able to store a maximum of two 24 hour logs, and a minimum of sixteen 15 minute logs. As a result, if the premature termination command is used frequently, it is possible that performance monitoring results may be lost. To avoid this event, results should be retrieved regularly from the Element Controller.

Procedure 7-8Early termination of performance monitoring

Step Action

1 Access the ‘Maint/Operations/Pef_mon/Early_termination’ submenu by selecting:Maint OperationsPerf_mon Early_termination

2 To: Do this:

Confirmation is required for these commands.

—end—

Terminate the current 15 minute performance monitoring period.

Execute the 15m command by selecting:

15m

Terminate the current 24 hour performance monitoring period.

Execute the 24h command by selecting:

24h

Terminate the current 15 minute and 24 hour performance monitoring period.

Execute the Both command by selecting:

Both



Requesting an intermediate PM calculationThe TN-1X collects performance data for all PMPs for fixed intervals of 15 minutes and 24 hours. At any time during these periods, the user can request an intermediate performance report. The data in an intermediate report is not logged, the TN-1X continues accumulating performance statistics for the rest of the period.

Procedure 7-9Requesting an intermediate PM calculation

Step Action

1 Access the ‘View_status/Perf_intermediate’ submenu by selecting:View_statusPerf_intermediate

2 Execute the command for the required intermediate performance report, do this by selecting one of the following:Rs_neRs_oofMs_neHp_neHp_feAu_pjeLp_neLp_feTu_pjePpi_cvPpi_CrcNo confirmation is required.

3 The Browser responds by opening/refreshing a parameter input window. This window has text entry boxes that allow the user to specify the port (SDH or PDH) or port and payload (SDH port and AU4 payload), depending on the PMP selected. The window also provides a ‘Submit’ and a ‘Cancel’ button.

4 Enter the port (SDH or PDH) or port and payload (SDH port and AU4 payload) and select the ‘Submit’ button.

—continued—



�

Procedure 7-9 Requesting an intermediate PM calculation (continued)

Step Action

5 A report window is opened/refreshed displaying the requested log.

Intermediate Performance Report

—end—


I 15m 697 01-04-1998 23:26:36 01-04-1998 23:15:00


S6-1 RS 0 0 0 0 p 0 A-1o S6-1


I 24h 75600 01-04-1998 23:26:36 09-01-2001 01:14:29


S6-1 RS 0 0 0 75343 p 75352 A-1o S6-1



Exporting TN-1X performance logs for external analysisPerformance monitoring logs are stored on the Element Controller in the sdhmsusr/sdhms/pm directory. Logs are automatically compressed after seven days.

Where the logs are stored in a compressed format, a ‘Z’ extension is used to indicate compressed logs. When the logs are viewed, printed or saved, the Element Controller uncompresses the logs so that they can be read. No additional user actions are required in this instance.

If the logs are copied via UNIX (for example, for use in other applications), the logs will have to be uncompressed before being used.

The Element Controller allows the user to retrieve performance monitoring logs from the NE and then export them in a format suitable for further analysis using a spreadsheet or other application. This operation assumes that the user has root access and wishes to copy the files to a PC for further analysis.

Procedure 7-10Exporting TN-1X performance logs for external analysis

Step Action

1 Open the Preside EC-1 Element Controller UNIX window.

2 Change the effective ID of the user to ‘root’ by entering:su root ↵<root password> ↵

3 Create a floppy disk directory by entering:mkdir /pcfs ↵

4 Mount the floppy disk by entering:mount -t pcfs /dev/fd0 /pcfs ↵

5 Exit from root by entering:Ctrl-D

6 Change to the logs directory by entering:cd ~sdhmsusr/sdhms/pm

7 Copy all performance logs (PL suffix) to the floppy disk directory by entering:cp *.PL /pcfs ↵

8 Eject the floppy disk by entering:eject ↵


—end—



�

Configuring performance monitoringError measurement methods

Errors are measured in a number of ways by the TN-1X. The error measurement methods described below are used to create performance monitoring statistics.

• Frame-based error measurement relates to the occurrence of parity errors within the STM-1 frame, and can be performed in one of two ways.

— Older Nortel Networks SDH hardware uses a Bit Interleaved Parity (BIP) basis of measurement. This identifies the number of parity bit errors within each STM-1 frame, and accumulates this count over a full second. As 8000 frames are transmitted per second, and there are eight parity bits in each frame, a total of 64000 parity errors can be accumulated per second on a BIP basis.

— Newer Nortel Networks SDH hardware typically uses a Block basis of measurement. This identifies the number of STM-1 frames which contain one or more parity bit errors during each second. As 8000 frames are transmitted per second, a total of 8000 parity errors can be accumulated per second on a Block basis.

Frame-based error measurements contribute to the Errored Seconds, Severely Errored Seconds, Background Block Errors and Unavailable Seconds performance monitoring statistics.

The NE can be set to measure frame-based errors on a BIP or Block basis. BIP is supported by all Nortel Networks SDH hardware, but Block is not. Where a Block basis is selected, any hardware that does not support this will use a BIP basis instead.

Procedure 7-11Setting the error measurement method

Step Action

1 Access the ‘Config/Perf_mon/Basis’ submenu by selecting:ConfigPerf_monBasis

2 To: Do this:

—end—

Enable Bit Interleaved Parity (BIP) basis performance monitoring

Execute the ‘Bip_only’ command by selecting:

Bip_only

Enable Block basis performance monitoring.

Execute the ‘Block’ command by selecting:

Block

These commands apply to the entire NE. No confirmation is required.



Severely errored secondsAn Errored Second (ES) is one in which one or more frame based errors occur, or an alarm relevant to the PMP occurs. A Severely Errored Second (SES) is an ES in which a threshold level of errors is exceeded, or an alarm relevant to the PMP occurs. The threshold levels that distinguish an ES from an SES can be set by the user on a BIP or lock basis. It is recommended that the default SES thresholds are retained for all PMPs.

Procedure 7-12Setting severely errored second thresholds

Step Action

1 Access the ‘Config/Perf_mon/Ses_defines’ submenu by selecting:ConfigPerf_monSes_defines

You need to be a System Engineer class user to access this menu.

2 The Browser window is refreshed with the following menu options:Rs_sesMs_sesHp_sesHp_fe _sesLp_vc12_sesLp_vc3_sesLp_fe_vc12_sesLp_fe_vc3_sesView

3 Select the required performance monitoring point.

—continued—



�

Procedure 7-12 Setting severely errored second thresholds (continued)

Step Action

4 The Browser responds by opening/refreshing a parameter input window that is divided into two frames. The left frame has radio buttons enabling the user to specify a new threshold or restore the default threshold for BIP and Block bases. For BIP basis only, a radio button is provided to ‘Preserve’ the existing threshold. The right frame has text entry boxes for the BIP and Block thresholds or a text message ‘D’ or ‘P’ where Default or Preserve have been selected. The right frame also provides a ‘Submit’ button and a ‘Clear’ button.

5 Select the appropriate radio buttons for the required settings. For example to restore the default Block SES setting, select the radio button in the ‘Default’ column and the ‘Block’ row.

6 Select the ‘Generate’ button. The right frame is refreshed with the appropriate text and/or text entry boxes.

7 Enter the required SES value and select the ‘Submit’ button. No confirmation is required.

—end—

Setting Quality of Service Violation alarmsQuality Of Service Violation (QOSV) alarms are triggered by threshold levels of the ES, SES, BBE and UAS performance counts. These alarms, which can be enabled and disabled on a PMP basis, can only be raised if both monitoring and alarm raising are enabled for the affected PMP. QOSV thresholds can be defined by the user on both a BIP and Block basis.

Threshold levels of ES, SES, BBE and UAS can be set by the user only for existing connections. If a connection is removed, the QOSV thresholds that relate to it are defaulted.

If alarm raising is disabled for a PMP, monitoring is unaffected. Error counts will still be collated, and results will be stored. These results, however, will not be used to trigger alarm events.



Procedure 7-13Setting QOSV thresholds

Step Action

1 Access the ‘Config/Perf_mon’ submenu by selecting:ConfigPerf_mon

2 QOSV thresholds can be set for 24 hour and 15 minute periods. The commands are the same but are located in different menu branches.

To: Do this:

The following steps are the same regardless of the option chosen in step 2.

3 To: Do this:

—continued—

Set thresholds for a 24 hour period Execute the ‘24h’ command by selecting:

24h

Set thresholds for a 15 minute period Execute the ‘15m’ command by selecting:

15m

Configure QOSV thresholds, monitoring and alarms for the Regenerator Section

Execute the ‘Rs_ne’ command by selecting:

Rs_ne

Configure QOSV thresholds, monitoring and alarms for the Multiplexer Section

Execute the ‘Ms_ne’ command by selecting:

Ms_ne

Configure QOSV thresholds, monitoring and alarms for the High Order path

Execute the ‘Hp_ne’ command by selecting:

Hp_ne



�

Procedure 7-13 Setting QOSV thresholds (continued)

Step Action

To: Do this:

The following steps are the same regardless of the option chosen in step 3. Parameters are required by the Browser and the user is prompted for these.

4 To: Do this:

5 The Browser responds by opening/refreshing a parameter input window that is divided into two frames. The left frame has radio buttons enabling the user to select a ‘Single’ instance or ‘All’ instances. When the ‘Single’ radio button is selected, the right frame is refreshed with text entry boxes for the instance. The right frame also provides a ‘Submit’ button and a ‘Clear’ button.

Note: When a single instance is to be specified, the use of the displayed fields depends on the affected PMP:

• For the RS_NE, RS_OOF and MS PMPs, an SDH port is required. This requires the use of the first two fields. That is, the J field should not be completed.

• For the HP_NE, HP_FE and AU_PJE PMPs, a high-order SDH payload (AU4) is required. This requires the use of all three fields.

—continued—

Configure QOSV thresholds, monitoring and alarms for the High Order path far end

Execute the ‘Hp_fe’ command by selecting:

Hp_fe

Configure QOSV thresholds, monitoring and alarms for the Low Order path

Execute the ‘Lp_ne’ command by selecting:

Lp_ne

Configure QOSV thresholds, monitoring and alarms for the Low Order path far end

Execute the ‘Lp_fe’ command by selecting:

Lp_fe

Configure QOSV thresholds, monitoring and alarms for the PDH interfaces

Execute the ‘Ppi_cv’ command by selecting:

Ppi_cv

Enable processing of SDH physical ports, AU4s or PDH ports (depending on the selection made in step 3)

Execute the ‘Monitoring_on’ command by selecting:

Monitoring_on

Disable processing of SDH physical ports, AU4s or PDH ports (depending on the selection made in step 3)

Execute the ‘Monitoring_off’ command by selecting:

Monitoring_off




Step Action

• For the LP_NE, LP_FE, PPI_CV, and TU_PJE PMPs, a PDH port is required. This requires the use of the first two fields. That is, the J field should not be completed.

6 To: Do this:

7 To: Do this:

8 The Browser responds by opening/refreshing a parameter input window that is divided into two frames. The left frame has radio buttons enabling the user to select a ‘Single’ instance or ‘All’ instances. When the ‘Single’ radio button is selected, the right frame is refreshed with text entry boxes for the instance. The right frame also provides a ‘Submit’ button and a ‘Clear’ button.



—continued—

Enable processing of all instances Select the ‘All’ radio button and then the ‘Submit’ button.

Enable processing of a specific instance

Select the ‘Single’ radio button, enter the appropriate instance (with regard to the note above) and then select the ‘Submit’ button.

No confirmation is required for these commands.

Enable alarm raising on SDH physical ports, AU4s or PDH ports (depending on the selection made in step 3)

Execute the ‘Alarm_on’ command by selecting:

Alarm_on

Disable alarm raising on SDH physical ports, AU4s or PDH ports (depending on the selection made in step 3)

Execute the ‘Alarm_off’ command by selecting:

Alarm_off



�


Step Action

• For the LP_NE, LP_FE, PPI_CV, and TU_PJE PMPs, a PDH port is required. This requires the use of the first two fields.


9 To: Do this:

10 To: Do this:

—continued—

Enable alarm raising on all instances Select the ‘All’ radio button and then the ‘Submit’ button.

Enable alarm raising on a specific instance



Set the ES threshold above which a QOSV alarm is raised

Execute the ‘Es_threshold’ command by selecting:

Es_threshold

Set the SES threshold above which a QOSV alarm is raised

Execute the ‘Ses_threshold’ command by selecting:

Ses_threshold

Set the BBE threshold above which a QOSV alarm is raised

Execute the ‘Bbe_threshold’ command by selecting:

Bbe_threshold

Set the UAS threshold above which a QOSV alarm is raised

Execute the ‘Uas_threshold’ command by selecting:

Uas_threshold

For the threshold commands the parameter ‘d’ can be specified to restore the default threshold.




Step Action

11 Access the root menu by selecting the ‘Home’ button.

12 Access the ‘Config/Perf_mon’ submenu by selecting:ConfigPerf_mon

13 Result processing for Rs_oof, Au_pje, Tu_pje PMPs can be set for 24 hour and 15 minute periods. The commands are the same but are located in different menu branches.

To: Do this:

14 To: Do this:

15 To: Do this:

—continued—

Set thresholds for a 24 hour period Execute the ‘24h’ command by selecting:

24h

Set thresholds for a 15 minute period Execute the ‘15m’ command by selecting:

15m

Enable processing of the Rs_oof PMP

Execute the ‘Rs_oof’ command by selecting:

Rs_oof

Enable processing of the Au_pje PMP

Execute the ‘Au_pje’ command by selecting:

Au_pje

Enable processing of the Tu_pje PMP

Execute the ‘Tu_pje’ command by selecting:

Tu_pje

Enable processing of SDH physical ports, AU4s or PDH ports (depending on the selection made in step 14)

Execute the ‘Monitoring_on’ command by selecting:

Monitoring_on

Disable processing of SDH physical ports, AU4s or PDH ports (depending on the selection made in step 14)

Execute the ‘Monitoring_off’ command by selecting:

Monitoring_off



�


Step Action

16 The Browser responds by opening/refreshing a parameter input window that is divided into two frames. The left frame has radio buttons enabling the user to select a ‘Single’ instance or ‘All’ instances. When the ‘Single’ radio button is selected, the right frame is refreshed with text entry boxes for the instance. The right frame w also provides a ‘Submit’ button and a ‘Clear’ button.




• For the LP_NE, LP_FE, PPI_CV, and TU_PJE PMPs, a PDH port is required. This requires the use of the first two fields. That is, the J field should not be completed.

17 To: Do this:

—end—

Enable processing of all instances Select the ‘All’ radio button and then the ‘Submit’ button.

Enable processing of a specific instance





Procedure 7-14Setting the start time for 24 hour performance periods

Step Action

1 Access the ‘Config/Perf_mon/Start_24h’ submenu by selecting:ConfigPerf_monStart_24h

2 Execute the ‘Set’ command by selecting:Set

3 The Browser responds by opening/refreshing a parameter input window. This window has a text entry box enabling the user to specify the start time. The window also provides a ‘Submit’ and a ‘Cancel’ button.

4 Enter the required 24 hour clock start time, 0 (midnight) to 23 (11pm) and select the ‘Submit’ button. No confirmation is required.

—end—

end of chapter


8-1

�

Appendix A: Accessing the Browser 8-The Browser User Interface is application software that allows a user to access, configure and control the TN-1X multiplexer (network element). Access to this application software (which resides on the network element) is via a Craft Access Terminal or a Preside EC-1 Element Controller.

Netscape NavigatorNetscape Navigator* (Netscape) is a hypertext browser. It enables the user to view files that are written in the HyperText Markup Language (HTML). The Browser is an HTML interface to the network element application software. The Browser communicates with the command-line interface of the application software, and presents the results as an intuitive point-and-click interface inside Netscape.

Note: The command-line interface of the TN-1X can be accessed directly from both the CAT and the Preside EC-1 platforms. Details of these mechanisms can be found in the TN-1X Command Line User Interface Guide, NTP 323-1061-401 and the Preside EC-1 Element Controller User Procedures Guide, NTP 323-1091-402.

Starting NetscapeNetscape must be running in order for the Browser to function. This is achieved in the following ways:

• On the CAT platform, there is a ‘CAT’ icon on the Windows95 desktop. Double click on this, and Netscape starts automatically. You are then presented with the TN-1X login screen.

• On the Preside EC-1 platform, there is an ‘Open NE’ command on the command menu for a selected NE in the Network Element Access (NEA) window. Select this option, and Netscape starts automatically. You are then presented with the TN-1X login screen.

Logging inThe TN-1X supports three user sessions from the Preside EC-1 Element Controller, and one from the CAT. Only one system engineer login is permitted. This can be from either Preside EC-1 or CAT, but not from both simultaneously. The configuration manager and status manager classes can have more than one login.

8-2 Appendix A: Accessing the Browser


The TN-1X login screen is shown in Figure 8-1.

Figure 8-1The TN-1X login screen

CAUTIONMultiple configuration manager loginsIf more than one user is logged in as a configuration manager, care should be taken by each configuration manager to ensure that any actions performed do not adversely affect the work of other configuration managers.

Appendix A: Accessing the Browser 8-3


�

The elements shown in Figure 8-1 are detailed below.

• NE selection pull-down menu: A list of available NEs.

Note: This menu is not available when logging in from the CAT, as the NE to which the CAT is attached is the only NE accessible from the CAT.

• User Name: The user name.

• Password: The password for the user name.

• Identification: This differentiates users with the same user name.

• Submit button: Click this button to confirm entered details.

• Clear button: This clears any typed entries.

The user can attempt to login for three minutes. If a successful login is not achieved in this period, the user is automatically disconnected. This event will also occur if four consecutive unsuccessful login attempts are made in the login period.

Logging in from the CATThe procedure for logging into the TN-1X via the CAT is given in Procedure 8-1.

Procedure 8-1Logging in to the TN-1X via the CAT

Step Action

1 Ensure that the CAT PC is switched off.

2 Plug the RS232 cable into the RS232 socket on the CAT PC.

3 Plug the other end of the RS232 cable into the CAT PC port on the TN-1X network element.

4 Switch on the CAT PC and start Microsoft Windows95.

5 Start Netscape, as described in “Starting Netscape” on page 8-1. You are presented with the TN-1X login screen (see Figure 8-1).

6 Position the cursor inside the ‘User Name’ field.

7 Complete the ‘User Name’ field, and press the TAB key to move to the ‘Password’ field.

8 Complete the ‘Password’ field, and press the TAB key to move to the ‘Identification’ field.

9 Complete the ‘Identification’ field, and select the Submit button to confirm the login details.

10 If the login is successful, you are presented with the top level of the command hierarchy (see Figure 8-2). If you are unsuccessful, the login details are cleared. Repeat from step 6.

—end—



Logging in from the Preside EC-1 Element ControllerThe procedure for logging into a TN-1X from the Preside EC-1 is given in Procedure 8-2.

Procedure 8-2Logging in to the TN-1X via the Preside EC-1

Step Action

1 Start the Preside EC-1 software and login.

2 Start Netscape, as described in “Starting Netscape” on page 8-1. You are presented with the TN-1X login screen (see Figure 8-1).

3 Select the NE to be accessed from the NE pull-down menu (see Figure 8-1).

4 Position the cursor inside the ‘User Name’ field.

5 Complete the ‘User Name’ field, and press the TAB key to move to the ‘Password’ field.

6 Complete the ‘Password’ field, and press the TAB key to move to the ‘Identification’ field.

7 Complete the ‘Identification’ field, and press the Submit button to confirm the login details.

8 If the login is successful, you are presented with the top level of the command hierarchy (see Figure 8-2). If you are unsuccessful, the login details are cleared. Repeat from step 3.

—end—

Once logged in, the top level of the command hierarchy is displayed. This is shown in Figure 8-2.

Note: This top level screen is always accessible via use of the ‘Home’ button that is displayed on every Browser screen.

Appendix A: Accessing the Browser 8-5


�

Figure 8-2Top level of the TN-1X command hierarchy

From this screen, you are able to access all of the top-level directories within the command hierarchy.



Login reportsThere are a number of login report hyperlinks listed at the top of the screen after logging in (see Figure 8-2). These reports provide system information that may be of interest immediately after login, and are only accessible the first time you visit this screen during a session.

To access a login report, click on its hyperlink. The report is displayed in the output window.

The login reports duplicate standard reports that are accessible from elsewhere in the command hierarchy. The reports are:

• NE time: This displays the NE time.

• Inventory. This shows all installed plug-in units.

• Open sessions: This lists all logged in users.

• Software and configuration table status: This shows the status of the two software banks, and the two configuration tables.

• Loopback configuration: This shows any active loopbacks.

• Alarm status: This shows all active alarms.

Note: Hyperlinks for all of the above reports can be displayed by selecting the ‘get_mux_status’ command.

Logging outLogout can occur either manually or automatically:

• Manual logout. This is achieved using the ‘Exit’ button from any Browser screen (see Figure 8-2). When this button is pressed, you are logged out from the TN-1X, and returned to the login screen (see Figure 8-1).

• Automatic logout. This occurs after no activity has occurred via the Browser for a predetermined period. Automatic logout period can be adjusted using the commands in the ‘Session’ directory. After automatic logout occurs, you are returned to the login screen when you next attempt to interact with the Browser.

end of chapter


9-1

Appendix B: TN-1X Release 7.3/7.4 to Release 9.0 Upgrade Procedure 9-

This Appendix gives the upgrade process for TransportNode TN-1X (TN-1X) from Release 7.3/7.4 to Release 9.0.

For a description of an upgrade process for TN-1X Release 8.1/8.2/8.3 equipment see “Appendix C: TN-1X Release 8.1/8.2/8.3 to Release 9.0 Upgrade Procedure” on page 10-1.

SummaryAppendix B is subdivided to cover the following key areas:

• Preparation of TN-1X network elements for the software upgrade (Procedure 9-1 to Procedure 9-3).

• Upgrade the network elements with the new software either automatically or manually:

— Using automatic scripts.

(Procedure 9-4 and Procedure 9-5)

— Manually.

(Procedure 9-6 to Procedure 9-8)

Nortel Networks recommends users to upgrade to TransportNode TN-1X Release 9.0 using the automatic scripts, when possible.

CAUTIONChange of internal bus mappingThe internal bus mapping of TN-1X Release 9.0 is different from earlier releases. A VC-12 Defragmentation must be performed on each network element that is upgraded to TN-1X Release 9.0. (For details of, and guidelines on, this process, see Engineering Bulletin TN-1X Release 9.0 Connection Recommendations, SDH_E155.)

9-2 Appendix B: TN-1X Release 7.3/7.4 to Release 9.0 Upgrade Procedure


ReferencesThis Appendix refers to the following Nortel Networks technical publications:

• Nortel TN-1X System Description Release 9, NTP 323-1061-100

• Engineering Bulletin TN-1X Release 9.0 Connection Recommendations, SDH_E155

• Preside EC-1 Network Upgrade Procedure, 323-1091-230

Preparation of TN-1X network elements for software upgradePrerequisites

The following prerequisites are applicable to this upgrade:

• The TN-1X Release 9.0 load image digital audio tape (NTQJ31HG)

• For any Payload Manager, 25U PJ00 750 GXF (at PCS12) in the network Nortel Networks recommends that INT synchronization sources are not used as primary synchronization sources during the upgrade.

Preparatory ProceduresThe following preparatory procedures are normally applicable in sequence:

1 Procedure 9-1 Extracting the TN-1X R7.0 load image software

2 Procedure 9-2 Rebooting all TN-1X network elements

3 Procedure 9-3 Checking status of the rebooted network elements.

CAUTIONBuffer alarm monitoringRelease 7.n of TN-1X does not store PPI_AIS, LP_DEG or INT_LP_ OP_Buffer alarm monitoring information in its configuration memory. When an upgrade to Release 9.0 occurs, these settings default (PPI_AIS alarm monitoring to on, LP_DEG to on and INT_LP_Buffer to off.) Any Release 7.n TN-1X that has these ports provisioned to non-default settings must be reprovisioned after it is upgraded to Release 9.0.

Appendix B: TN-1X Release 7.3/7.4 to Release 9.0 Upgrade Procedure 9-3


Procedure 9-1Extracting the TN-1X R7.0 load image software

Step Action

1 Log on to the Preside EC-1 Element Controller platform, type:

syseng01 ↵↵↵↵<password> ↵↵↵↵

2 Double-click the Preside EC-1 Element Controller icon to log on to the Preside EC-1 Element Controller.

3 Open the System Engineer section of the main menu by clicking on its check box, and open a UNIX window from this menu.

4 In the System Engineer's UNIX window, create a new xterm, type:

xterm -g 120x40 & ↵↵↵↵5 Close the System Engineer's UNIX window. Do not close the new xterm.

6 In the new xterm (UNIX window), change the current shell, type:

csh ↵↵↵↵7 Insert the digital audio tape for the load image software (NTQJ31HG) into the

Digital Audio Tape (DAT) Drive.

8 Change to the following directory, type:

cd /home/sdhmsusr/sdhms/data/NE_load/1X ↵↵↵↵9 Retrieve the required software from the DAT, type:

tar xv ↵↵↵↵The software downloads from the DAT. Messages appear during this process.

10 Remove the digital audio tape (NTQJ31HG) from the DAT drive.

—end—



Procedure 9-2Rebooting all TN-1X network elements

Step Action

Note: This procedure is mandatory, and takes approximately N x 10 minutes, where "N" is the number of associated TN-1X network elements on the network.

1 In a UNIX window, type:

cd /home/sdhmsusr ↵↵↵↵touch router ↵↵↵↵

2 The assigned router (default router) for each Open Systems Interconnection (OSI) Local Area Network (LAN) must be identified, this network element must not be rebooted. Where more than one area address is used, there is one assigned router for each OSI LAN.

If the assigned router is a CISCO/BAY Network router then go to Step 3.

a. The assigned router is the network element with the highest head-end Ethernet address for each OSI LAN. A head-end network element can be identified by the presence of a LAN cable. Use CLUI command, type:

~ c o n v ↵↵↵↵Record the assigned router(s) for each OSI LAN.

Note: A TN-1C multiplexer can be the head-end network element with the highest head-end Ethernet address. All TN-1P multiplexer addresses must be ignored when determining the head-end network element that has the highest Ethernet address.

b. In a UNIX window, add the assigned router(s) network element address(es) to the router file, type:

echo "<designated router address>" >> router ↵↵↵↵The router file must be in the format 00007540xxxx. For example:

000075402345

Repeat the echo statement for each OSI LAN. More than one OSI LAN router file takes the form:

000075402345

000075403456

000075405060

3 In the UNIX window, type:

send_1x -reboot -i router | tee reboot.log ↵↵↵↵Each network element is restarted, one after the other, except the assigned router(s). The script waits until communications are re-established to each rebooted network element before rebooting the next network element.

Note: Association to network elements can be lost on the Preside EC-1 Element Controller during this reboot. Associations can be established within 15 minutes.

—end—



Procedure 9-3Checking status of the rebooted network elements

Step Action

1 Check that all TN-1X network elements are in the "Stable state". Type the following command in the UNIX window:

send_1x -swlisting ↵↵↵↵The script appears.

When this script completes, view the software listing file:

a. If the software status for any network element is "Ready_to_activate", perform a Command Line User Interface (CLUI) login to the selected network element and perform a software backout, type:

~ a s bo ↵↵↵↵b. If the configuration table status for any network element is

"Ready_to_activate", perform a CLUI logon to the selected network element and perform a configuration backout, type:

~ a c bo ↵↵↵↵c. If the software status for any network element is "Ready_to_commit",

perform a CLUI logon to the network element and perform a software commit, type:

~ a s cm ↵↵↵↵d. If the configuration table status for any network element is

"Ready_to_commit", perform a CLUI logon to the network element and perform a configuration commit:

~ a c cm ↵↵↵↵When all network elements are in the "Stable" state, this procedure ends.

—end—



Upgrade the software AUTOMATICALLYThe following procedures facilitate the use of automatic scripts:

• Procedure 9-4 Automatically download the TN-1X Release 9.0 load image software

• Procedure 9-5 Automatically booting/committing the TN-1X Release 9.0 network elements

The use of automated scripts minimizes the introduction of errors occurring during the upgrade process.

Procedure 9-4Automatically download the TN-1X Release 9.0 load image software

Step Action

Note: This procedure takes approximately N x 12 minutes, where ‘N’ is the number of associated TN-1X network elements on the network.


send_1x -swdl NE_load/1X/<load image name> | tee swdl.log ↵↵↵↵Where <load image name> is the load image file name (for example, tn1x906A.b).

Each network element has a software download performed in sequence. Each network element software download is complete before the next network element download starts.

2 Ensure that all network elements have been correctly downloaded with the new software. In the UNIX window, type:

send_1x -swlisting ↵↵↵↵3 View the software listing result, type:

more SW_LISTING ↵↵↵↵The software listing appears.

4 Each network element must be in the "Ready_to_activate" state. Perform a manual download of software for each failed network element (using Procedure 9-6).

—end—



Procedure 9-5Automatically booting/committing the TN-1X Release 9.0 network elements

Step Action

Note: This procedure takes approximately N x 10 minutes, where "N" is the number of associated TN-1X network elements on the network.


send_1x -swboot -i router | tee swboot.log ↵↵↵↵With the exception of the assigned routers, each TN-1X is rebooted in sequence with Release 9.0 software.

Note: Wait 5 minutes after completing the reboots before executing the next step.

2 With the exception of the assigned router(s), ensure that every TN-1X has upgraded correctly. In the UNIX window, type the following command to check the status of all TN-1X network elements:

send_1x -swlisting ↵↵↵↵3 View the software listing results:

more SW_LISTING ↵↵↵↵The software listing appears. With the exception of the assigned router(s), each TN-1X network element must be in the "Ready_to_commit" state). If not, with the exception of the assigned router(s), perform the manual upgrade procedure for each failed network element (see Procedure 9-6,Procedure 9-7, Procedure 9-8 and Procedure 9-9).

4 Check if any TN-1X network elements are in "Detached" mode. If so, the "Detached" mode of operation is a result of there continuing to be one or more Tributary to Tributary connections on the selected TN-1X multiplexer. The operator must reprovision the traffic on these connections before deleting the connections.

5 When the operator has deleted the tributary to tributary connections, use the following CLUI command to bring the multiplexer out of "Detached mode":

~ a c ic ↵↵↵↵Note: All the tributary to tributary connections must be deleted from the TN-1X multiplexers before the TN-1x multiplexers can leave the "Detached" mode.

6 With the exception of the assigned router(s), all network elements are now "Undetached" and are in a "Ready_to_commit" state. Therefore the Release 9.0 software can be committed to the "inactive banks". In the UNIX window, type:

send_1x -swcommit -i router | tee swcommit.log ↵↵↵↵The Release 9.0 software is copied into the "inactive banks".

7 In the UNIX window, use the following command to check the status of all TN-1X network elements, type:

send_1x -swlisting ↵↵↵↵

—continued—



Procedure 9-5 Automatically booting/committing the TN-1X Release 9.0 network elements (Continued)

Step Action

8 View the software listing results, type:

more SW_LISTING ↵↵↵↵The software listing results appear. With the exception of the selected router(s) each network element must be in the "Stable/Stable" state.

9 The assigned router(s) must be upgraded. Perform the manual upgrade procedure as required (see Procedure 9-6, Procedure 9-7, Procedure 9-8 and Procedure 9-9).

Note: When you upgrade the assigned router, this action can cause a loss of communication to all network elements in the network for a period of 10 minutes.

10 Is the complete network in the "Stable/Stable" state?

—end—

If Then

No perform the manual upgrade procedure for each failed network element (see Procedure 9-6, Procedure 9-7, Procedure 9-8 and Procedure 9-9).

Yes with the complete network in the "Stable/Stable" state, repeat step 7 and step 8 only.



Upgrade the software MANUALLY

Procedure 9-6Manually downloading the TN-1X R9.0 load image software

Step Action

1 Click the Network Element Access option from the Management Function on the Preside EC-1 Element Controller main menu bar.

When the NE Access tool opens, a list of network elements appears.

2 Place the cursor on a network element, click the right-hand mouse button and select the NE Command option.

3 At the prompt, type the following:

~ a s dw NE_load/1X/<load image name> ↵↵↵↵Where <load image name> is the load image file name (for example, tn1x906A.b)

The network element reports the progress of the software download in the CLUI window and in the message window on the EC-1 R1

Note: Only one software download can be performed at a time. Do not log off the CLUI session during software download.

4 Last network element in your network?

—end—

If Then

No Repeat step 2 to step 3 for the next network element in your network.

Yes Close the Network Element Access tool.



Procedure 9-7Manually booting the TN-1X R9.0 load image software

Step Action


When the NE Access tool opens, a list of network elements appears.

2 Place the cursor on the selected network element, click on the right-hand mouse button and select the NE Command Line option.

3 At the prompt, type the following to confirm that the correct version is in the "inactive bank":

~ a s v ↵↵↵↵If the correct version is not present, repeat Procedure 9-6 to download the TN-1X load images. If the correct version is in the alternate bank, go to step 5

4 Is the correct version present?

5 At the prompt, type the following to switch to the new load image:

~ a s sl ↵↵↵↵6 Is this the last network element in the network?

—end—

If Then

the correct version is not present

repeat Procedure 6 to download the TN-1X load images to the "inactive bank"

the correct version is in the "inactive banks"

go to step 5

If Then

No repeat step 2 to step 5 for the next network element in your network.

Yes close the Network Element Access tool.



Procedure 9-8Deleting tributary to tributary connections after booting TN-1X Release 9.0 Software (See Preparation for Software Upgrade)

Step Action

Note: Do this procedure if any tributary to tributary connections remain undeleted after a software upgrade of a TN-1X multiplexer.

1 Check if any network elements are in ‘Detached’ mode. If so the "Detached" mode of operation is a result of there continuing to be tributary to tributary connections on the TN-1X multiplexer. The operator must reprovision the traffic on these connections.

2 When the operator has deleted the tributary to tributary connections, use the following CLUI command to bring the TN-1X multiplexer out of "Detached" mode, type:

~ a c ic ↵↵↵↵Note: All tributary to tributary connections must be deleted from the TN-1X multiplexer, before the network element can leave the "Detached" mode.

—end—



Procedure 9-9Manually committing the downloaded TN-1X R9.0 load image

Step Action


When the Network Element Access tool opens, a list of network elements appears.

2 Place the cursor on a network element, click the right-hand mouse button and choose the NE Command Line option.

3 At the prompt, type the following to commit the software, type:

~ a s cm ↵↵↵↵4 Check that the software configuration is in a stable state, type:

~ a s v ↵↵↵↵5 Is this the last network elements in your network?

Note: The internal bus mapping of TN-1X Release 9.0 is different from earlier releases. Refer to Nortel TN-1X System Description Release 9, NTP 323-1061-100 or to Engineering Bulletin TN-1X Release 9.0 Connection Recommendations, SDH_E155, for guidelines on connection changing.

—end—

end of chapter

If Then

No repeat step 2 to step 4 for the next network element in your network.

Yes The upgrade is complete.


10-1

�

Appendix C: TN-1X Release 8.1/8.2/8.3 to Release 9.0 Upgrade Procedure 10-

This Appendix gives the upgrade process for TransportNode TN-1X (TN-1X) from Release 8.1/8.2/8.3 to Release 9.0.

For a description of an upgrade process for TN-1X Release 7.3/7.4 equipment see “Appendix B: TN-1X Release 7.3/7.4 to Release 9.0 Upgrade Procedure” on page 9-1.

SummaryAppendix C is subdivided to cover the following key areas:

• Preparation of TN-1X network elements for software upgrade


• Upgrade the network elements with the new software either automatically or manually:

— Using automatic scripts.

(Procedure 10-4 and Procedure 10-5)

— Manually.


Nortel Networks recommends users to upgrade to TransportNode TN-1X Release 9.0 using the automatic scripts, when possible.

CAUTIONChange of internal bus mappingThe mapping of the internal bus of the TN-1X Release 9.0 network element is different to the mapping used for earlier releases. A VC-12 Defragmentation must be performed on each network element that is upgraded to TN-1X Release 9.0. (For details of and guidelines on this process, see Engineering Bulletin TN-1X Release 9.0 Connection Recommendations, SDH_E155)

10-2 Appendix C: TN-1X Release 8.1/8.2/8.3 to Release 9.0 Upgrade Procedure


ReferencesThis Appendix refers to the following Nortel Networks technical publications:

• Nortel TN-1X System Description Release 9, NTP 323-1061-100

• Engineering Bulletin TN-1X Release 9.0 Connection Recommendations, SDH_E155

• Preside EC-1 Network Upgrade Procedure, 323-1091-230

Preparation of TN-1X network elements for software upgradePrerequisites

The following prerequisites are applicable to this upgrade:

• The TN-1X Release 9.0 load image digital audio tape (NTQJ31HG).

• The Preside EC-1 Element Controller must be at Release 15 or later.

If the Preside EC-1 software needs to be upgraded to support the new network element software, the Preside EC-1 must be upgraded before the network elements, see Preside EC-1 Network Upgrade Procedure, 323-1091-230.

• For any Payload Manager, 25U PJ00 750 GXF (at PCS 12) in the network Nortel Networks recommends that INT synchronization sources are not used as primary synchronization sources during the upgrade.

• Pre-upgrade system checks have been completed and a maintenance freeze in position. A TN-1X Pre-Upgrade Check list is available on request, mailto:[email protected]

• Any traffic across remaining Tributary to Tributary connections has been reallocated and the Tributary to Tributary connections deleted.

Tributary to Tributary connections were an unsupported feature of TN-1X Release 8.x and are not available in TN-1X Release 9.0. A safety feature prevents a user from accidentally removing Tributary to Tributary connections.Where Tributary to Tributary connections exist, any action taken to reboot a TN-1X network element with Release 9.0 software causes the multiplexer going into "detached" mode with the connections kept intact. All Tributary to Tributary connections have to be removed before the multiplexer can leave the "detached" mode and continuing with the upgrade.

Preparatory ProceduresThe following preparatory procedures are normally applicable in sequence:

• Procedure 10-1, Extracting the TN-1X Release 9.0 load image software

• Procedure 10-2, Rebooting all TN-1X network elements

• Procedure 10-3, Checking status of the rebooted network elements

Appendix C: TN-1X Release 8.1/8.2/8.3 to Release 9.0 Upgrade Procedure 10-3


�

Procedure 10-1Extracting the TN-1X Release 9.0 load image software

Step Action

1 Log on to the Preside EC-1 Element Controller platform, type:

syseng01 ↵↵↵↵<password> ↵↵↵↵

2 Double-click the Preside EC-1 Element Controller icon to log on to the Preside EC-1 Element Controller.

3 Open the System Engineer section of the main menu by clicking its check box, and open a UNIX window from this menu.

4 In the System Engineer's UNIX window, create a new xterm, type:

xterm -g 120x40 & ↵↵↵↵5 Close the System Engineer's UNIX window. Do not close the new xterm.

6 In the new xterm (UNIX window), change the current shell, type:

csh ↵↵↵↵7 Insert the digital audio tape for the load image software (NTQJ31HG) into the

DAT Drive.

8 Change to the following directory.

cd /home/sdhmsusr/sdhms/data/NE_load/1X ↵↵↵↵9 Retrieve the required software from the digital audio tape, type:

tar xv ↵↵↵↵The software downloads from the digital audio tape. Messages appear during this process.

10 Remove the digital audio tape (NTQJ31HG) from the DAT drive.

—end—

Procedure 10-2Rebooting all TN-1X network elements

Step Action

Note: This procedure is MANDATORY, and takes approximately N x 12 minutes, where ‘N’ is the number of associated TN-1X network elements on the network.

1 In a UNIX window, type:

cd /home/sdhmsusr ↵↵↵↵touch router ↵↵↵↵

—continued—



Procedure 10-2 Rebooting all TN-1X network elements (Continued)

Step Action

2 The assigned router (default router) for each OSI LAN must be identified. The network element working as the assigned router must NOT be rebooted. There will be an assigned router for each OSI LAN having an area address.

If the assigned router is a CISCO/BAY Network router then go to Step 3.

a. The assigned router is the head-end network element with the highest ethernet address for each OSI LAN. A head-end network element can be identified by the presence of a LAN cable.

Use CLUI command, type:

~ c o n v ↵↵↵↵Record the assigned router(s) for each OSI LAN.

Note: A TransportNode TN-1C multiplexer can be the head-end network element with the highest Ethernet address. All TransportNode TN-1P multiplexer Ethernet addresses can be ignored when determining the head-end network element that has the highest Ethernet address.

b. In a UNIX window, add the assigned router(s) network element address(es) to the router file, type:

echo "<designated router address>" >> router ↵↵↵↵The router file must be in the format 00007540xxxx. For example:

000075402345

Repeat the echo statement for each OSI LAN. Where there is more than one OSI LAN, router file takes the form:

000075402345

000075403456

000075405060


send_1x -reboot -i router | tee reboot.log ↵↵↵↵Each network element restarts, one after the other, except the assigned router(s). The script waits until each rebooted network element establishes communications before rebooting the next network element

Note: Association to network elements can be lost from the Preside EC-1 Element Controller during this reboot. Associations should be established again within 15 minutes.

—end—



�

Procedure 10-3Checking status of the rebooted network elements

Step Action

1 Check that all TN-1X network elements are in the ‘Stable’ state. Type the following command in the UNIX window:

send_1x -swlisting ↵↵↵↵2 When this script completes, view the software listing file:

a. If the software status for any network element is "Ready_to_activate", perform a CLUI log on to the selected network element(s), and perform a software backout, type:

~ a s bo ↵↵↵↵b. If the configuration table status for any network element is

"Ready_to_activate", perform a CLUI log on to the selected network element(s), and perform a configuration backout, type:

~ a c bo ↵↵↵↵c. If the software status for any network element is "Ready_to_commit",

perform a CLUI log on to the selected network element(s), and perform a software commit, type:

~ a s cm ↵↵↵↵d. If the configuration table status for any network element is

"Ready_to_commit", perform a CLUI login to the selected network element(s), and perform a configuration commit, type:

~ a c cm ↵↵↵↵When all the network elements are in the "Stable" state, this procedure ends.

—end—



Upgrade the software AUTOMATICALLYThe following procedures facilitate the use of automated scripts:

• Procedure 10-4, Automatically download the TN-1X Release 9.0 load image software

• Procedure 10-5, Automatically booting/committing the TN-1X Release 9.0 network elements

The use of automated scripts minimises the introduction of errors occurring during the upgrade process.

Procedure 10-4Automatically download the TN-1X Release 9.0 load image software

Step Action

Note: This procedure takes approximately Nx12 minutes, where ‘N’ is the number of associated TN-1X network elements on the network.


send_1x -swdl NE_load/1X/<load image name> | tee swdl.log ↵↵↵↵

Where <load image name> is the load image file name (for example, tn1x906A.b).

Each network element has a software download performed; one after the other. The script waits until each software download is complete before continuing with the next network element.

2 Ensure that all network elements have been correctly downloaded with the new software. In the UNIX window, type:

send_1x -swlisting ↵↵↵↵3 View the software listing results, type:

more SW_LISTING ↵↵↵↵The software listing appears

4 Each network element must be in the "Ready_to_activate" state. Perform a manual download of software for each failed network element (using Procedure 10-6).

—end—



�

Procedure 10-5Automatically booting/committing the TN-1X Release 9.0 network elements

Step Action

Note: This procedure takes approximately Nx12 minutes, where "N" is the number of associated TN-1X network elements on the network.


send_1x -swboot -i router | tee swboot.log ↵↵↵↵Except for the assigned router(s) each TN-1X network element reboots, one after the other with Release 9.0 software.

Note: Wait 5 minutes after the reboots are complete before executing the next step.

2 Except for the assigned router(s), ensure that every TN-1X network element upgrades correctly. In the UNIX window, type the following command to check the status of all TN-1X network elements:

send_1x -swlisting ↵↵↵↵3 View the software listing results, type:

more SW_LISTING ↵↵↵↵The software listing appears. Except for the assigned router(s), each TN-1X network element must be in the "Ready_to_commit" state.If not, perform the manual upgrade procedure for each failed network element. (see Procedure 10-6, Procedure 10-7, Procedure 10-8 and Procedure 10-9)

4 Check if any TN-1X network elements are in ‘Detached’ mode. If so, the detached mode operation is as a result of there continuing to be one or more Tributary to Tributary connections on the selected TN-1X multiplexer. The operator must reprovision the traffic on these connections before deleting the connections.

5 When the operator has deleted the Tributary to Tributary connections, use the following CLUI command to bring the multiplexer out of the "detached" mode, type:

~ a c ic ↵↵↵↵Note: All Tributary to Tributary connections must be deleted from the TN-1X multiplexer, before the TN-1X multiplexer can leave the "detached" mode.

6 Except the assigned router(s), if all network elements are now ’undetached’ and are in a "Ready_to_commit" state then the Release 9.0 software can be committed on to the "inactive banks". In the UNIX window, type:

send_1x -swcommit -i router | tee swcommit.log ↵↵↵↵The Release 9.0 software is copied on to the "inactive banks".

7 In the UNIX window, use the following command to check the status of all TN-1X network elements, type:

send_1x -swlisting ↵↵↵↵

—continued—



Procedure 10-5 Automatically booting/committing the TN-1X Release 9.0 network elements (Continued)

Step Action

8 View the software listing results, type:

more SW_LISTING ↵↵↵↵The software listing appears. Except the assigned router(s), each network element must be in the "Stable/Stable" state.

9 The assigned router(s) must now be upgraded. Perform the manual upgrade procedure as required (see Procedure 10-6, Procedure 10-7, Procedure 10-8 and Procedure 10-9).

Note: Upgrading the assigned router can cause a loss of communications to all network elements in the network for a period of 10 minutes.

10 Is the complete network in the "Stable/Stable" state?

—end—

If Then

no perform the manual upgrade procedure for each failed network element (see Procedure 10-6, Procedure 10-7, Procedure 10-8, and Procedure 10-9)

yes with the complete network in the "Stable/Stable" state, repeat step 7 and step 8.



�

Upgrade the software MANUALLY

Procedure 10-6Manually downloading the TN-1X R9.0 load image software

Step Action

1 Click on the Network Element Access option from the Management Function on the Preside EC-1 Element Controller main menu bar.

When the NE Access tool opens, a list of network elements appear.

2 Place the cursor on the selected network element, click the right-hand mouse button and select the NE Command option.

3 At the prompt, type the following:

~ a s dw NE_load/1X/<load image name> ↵↵↵↵Where <load image name> is the load image file name (for example, tn1x906A.b)

The network element reports the progress of the software download in the CLUI window, and in the message window on the Preside EC-1 Element Controller.

Note: Only one software download can be performed at a time. Do not log off the CLUI session during software download.

4 Last network element in your network?

—end—

Procedure 10-7Manually booting the TN-1X R9.0 load image software

Step Action

1 Click on the Network Element Access option from the Management Function on the Preside EC-1 Element Controller main menu bar.

When the NE Access tool opens, a list of network elements displays.

2 Place the cursor on a selected network element, click the right-hand mouse button and select the NE Command option.

—continued—

If Then

no Repeat step 2 and step 3 for the next network element in your network.

yes Close the Network Element Access tool.



Procedure 10-7 Manually booting the TN-1X R9.0 load image software (Continued)

Step Action

3 At the prompt, type the following to confirm that the correct version is in the alternate bank:

~ a s v ↵↵↵↵If the correct version is not present, repeat Procedure 10-6 to download the TN-1X load images to the "inactive bank". If the correct version is in the "inactive bank", go to step 4.

4 Is the correct version present?

5 At the prompt, type the following to switch to the new load image:

~ a s sl ↵↵↵↵6 Last element in your network?

—end—

Procedure 10-8Deleting Tributary to Tributary connections after booting TN-1X Release 9.0 Software

Step Action

Note: This procedure is to be performed if any Tributary to Tributary connections remain undeleted after a software upgrade of TN-1X multiplexers Release 9.0.

1 Check if any network elements are in ‘Detached’ mode. If so the "detached" mode operation is as a result of there continuing to be Tributary to Tributary connections on the TN-1X multiplexer. The operator must reprovision the traffic on these connections before deleting the connections.

—continued—

If Then

the correct version is not present

repeat Procedure 10-6 to download the TN-1X load images to the "inactive bank"

the correct version is in the "inactive banks"

go to step 5

If Then

no Repeat step 2 to step 5 for the next network element in your network.

yes Close the Network Element Access tool.



�

Procedure 10-8 Deleting Tributary to Tributary connections after booting TN-1X Release 9.0 Software (Continued)

Step Action

2 When the operator has deleted the Tributary to Tributary connections use the following CLUI command to bring the TN-1X multiplexer out of "detached" mode, type:

~ a c ic ↵↵↵↵Note: All Tributary to Tributary connections must be deleted from the TN-1X multiplexer, before the TN-1X multiplexer can leave "detached" mode.

—end—

Procedure 10-9Manually committing the downloaded TN-1X R9.0 load image

Step Action


When the Network Element Access tool opens, a list of network elements appear.

2 Place the cursor on a selected network element, click the right-hand mouse button and select the NE Command option.

3 At the prompt, type the following to commit the software:

~ a s cm ↵↵↵↵4 Check that the software configuration is in a stable state, type:

~ a s v ↵↵↵↵5 Repeat step 2 to step 4 for each TN-1X network element in your network.

6 The upgrade is complete.

Note: Now that the software upgrade to TN-1X Release 9.0 is complete, consideration must be given to the change in internal backplane connection format between TN-1X Release 8.2 and TN-1X Release 9.0.

An audit and defragmentation of the existing VC-12 connections and future connections must be undertaken. Refer to the Nortel TN-1X System Description Release 9, NTP 323-1061-100 and Engineering Bulletin TN-1X Release 9.0 Connection Recommendations, SDH_E155.

—end—

end of chapter


11-1

Index 11-

Aactions

viewing 7-7activating

configuration data 3-18active alarms 7-2adding

new users 1-3alarm displays

active alarms 7-2count 7-1logs 7-2

clearing 7-3alarms

activeviewing 7-5

active alarms display 7-2categories 7-3monitoring 7-2QOSV alarms 7-17report formats 7-3severities 7-3status 7-3

aligningactive alarm list 7-2NE time with Preside EC-1 2-3

application softwareoverview 5-1preparation 5-5

automatic logout 1-1setting 1-8

Bbackground block errors (BBE) 7-15backing out

configuration data 3-20backing up

configuration data 3-3, 3-4, 3-6Bit Interleaved Parity (BIP)

errors 7-15Block

basis 7-15errors 7-15

CCAT

downloading software 5-7platform 8-1

clockaligning 2-2reading 2-1

committing toconfiguration data 3-19

configuration dataactivating 3-18backing out 3-20backing up 3-3, 3-4, 3-6committing to 3-19possible loss 5-2restoring 3-8restoring from archive 3-1

configuration tables 5-2conventions

user entry xiicritical alarm severity 7-3

Ddeleting

users 1-4detached mode 3-21

entering 3-22exiting 3-21

duty classes 1-3changing 1-5

Eerror measurement 7-15

11-2 Index


errored seconds 7-15

Ffoundation software 5-1frame-based errors 7-15

Llogin

password 1-1logout

automatic 1-1

Mmajor alarm severity 7-3messages window 7-4minor alarm severity 7-3modifying users 1-5

Ppasswords 1-3

changing 1-7changing (Preside EC-1) 1-5

performance monitoring 7-4basis of frame errors 7-15error measurement 7-15

platformCAT 8-1

PMPserror measurement 7-15QOSV alarms 7-17

preparationsoftware 5-5

QQOSV

alarms 7-17thresholds

setting 7-17

Rreset

hardware 5-15software 5-15

restoringconfiguration data 3-8

Sseverely errored seconds 7-15

softwarebacking out 5-14banks 4-1committing to 5-13downloading (CAT) 5-7downloading (Preside EC-1) 5-9foundation 5-1preparation 5-5release number 4-1switching banks 5-12upgrade status 4-2, 5-3upgrading 5-4

system date and time 2-3

TTN-1X restart

cold 5-15warm 5-15

Uunavailable seconds 7-15unavailable time log 7-10upgrade procedure

TN-1X Release 7.3/7.4 to Release 9.0 9-1TN-1X Release 8.1/8.2/8.3 to Release

9.0 10-1user

administration 1-2classes 1-1names 1-1

usersadding 1-3deleting 1-4modifying 1-5

International Optical NetworksTechnical Documentation GroupNortel NetworksOakleigh Road SouthLondon, N11 1HB

So far as Nortel Networks is aware the contents of this document are correct. However, such contents have been obtained from a variety of sources and Nortel Networks can give no warranty or undertaking and make no representation as to their accuracy. In particular, Nortel Networks hereby expressly excludes liability for any form of consequential, indirect or special loss, and loss of data, loss of profits or loss of business opportunity, howsoever arising and whether sustained by the user of the information herein or any third party arising out of the contents of this document.

*NORTEL NETWORKS, the Nortel Networks logo, the Globemark and Unified Networks are trademarks of Nortel Networks.

Netscape and Navigator are trademarks of Netscape Communications Corporation.

Microsoft and Windows are trademarks of Microsoft Corporation.

HyperTerminal is a trademark of Hilgraeve Inc.

SDH TRANSMISSION


Copyright 1997 – 2001 Nortel Networks, All Rights Reserved.

The copyright of this document is the property of Nortel Networks. Without the written consent of Nortel Networks, given by contract or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person whatsoever.

NORTEL NETWORKS CONFIDENTIAL: The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

Document Number: 323-1061-302Product Release Number: 9Document Status: StandardDate: July 2001Printed in England

302

Documents

admin cnfg tbl verify

admin sw verify

cd home sdhmsusr sdhms data ne load 1x retrieve

text entry boxes

1s hard drive

cats hard drive

radio buttons enabling

highest ethernet address