GTS Controller Version 5.0 - GDCGTS Controller Version 5.0.0 Release Notes 036R903-V500, Issue 4 - May 2006

GTS Controller Version 5.0.0Release Notes 036R903-V500, Issue 4 - May 2006

Warranty

General DataComm warrants that its equipment is free from defects in materials and workmanship. The warrantyperiod is one year from the date of shipment. GDC's sole obligation under its warranty is limited to the repair orreplacement of the defective equipment provided it is returned to GDC, transportation prepaid, within a reasonableperiod. This warranty will not extend to equipment subjected to accident, misuse, or alterations or repair not madeby GDC or authorized by GDC in writing. The foregoing warranty is exclusive and in lieu of all other warranties,express or implied, including but not limited to, warranties of merchantability and fitness for purpose.

Trademarks and PatentsGeneral DataComm, the General DataComm logo and the following are trademarks of General DataComm, Inc inthe United States and other countries: ACCULINE, ANALOOP, AUTOFRAME, BERT 901, DATACOMMSECURE-PAK, DATALOOP, DIGIDIAL, ENmacs, FASTPRO, FIRST RESPONSE, GDC, GDC APEX,GENERAL DATACOMM X-PRESS, GEN*NET, GEN*PAC, IMAGE*TMS, KILOMUX, LAN*TMS,MEGA*BRIDGE, MEGAMUX, MEGAMUX TMS, MEGANET, MEGASPLIT, MEGASWITCH, MEGAVIEW,NETCON, NETSWITCH, NMC, QUIKSHIPPERS, SERVI-CHECK, SERVI-SNAP, WINmacs.

ANALOOP and DATALOOP respectively are protected by U.S. patents 3,655,915 and 3,769,454. All other productsor services mentioned in this document are identified by the trademarks, service marks, or product names asdesignated by the companies who market those products. Inquiries concerning such trademarks should be madedirectly to those companies.

Copyright© 2006 General DataComm, Inc. All rights reserved.6 Rubber Avenue, Naugatuck, Connecticut 06770 U.S.A.

This publication and the software it describes contain proprietary and confidential information. No part of thisdocument may be copied, photocopied, reproduced, translated or reduced to any electronic or machine-readableformat without prior written permission of General DataComm, Inc.

The information in this document is subject to change without notice. General DataComm assumes no responsibilityfor any damages arising from the use of this document, including but not limited to, lost revenue, lost data, claims bythird parties, or other damages. If you have comments or suggestions concerning this manual, please write toTechnical Publication Services or call 1-203-729-0271.

GTS Controller Version 5.0.0 Publication No. 036R903-V500Issue 4 - May 2006

Releas

TABLE OF CONTENTS. 5

......

........6

...

.....6

.....7

.....7

......8

......9

.....9

....9

.....10

..10

..11

.11

..11

.12

12

.13

....14

....15

..16

...16

...16

.17

..17

....18

9

....20

....21

....2

..21

...21

...22

...23

Section 1 - GTS Software Version 5.0.0 ............................................1.0 Overview ......................................................................................................................... 52.0 Software Reference.....................................................................................................5

3.0 Changes and Improvements Since Last Release.......................................................

4.0 Corrected Issues.............................................................................................................6

5.0 Minimum Hardware Requirements .............................................................................

6.0 Replacing GTS V2.2.0 Controllers..............................................................................

6.1 Replacement Guidelines ..................................................................................

6.2 Replacement Procedure ..................................................................................

7.0 Controller Software Procedures..................................................................................

7.1 GTS User Login...............................................................................................

7.1.1 OpenServer User Login .......................................................................

7.2 Secure Shell (ssh) Passwords.........................................................................

7.3 PuTTY Software for Telnet/ssh........................................................................

7.4 TMS GTS Software ..........................................................................................

7.5 Activate Microlite Backup Edge Software ........................................................

7.6 Configure Time Zone........................................................................................

7.7 Configure LAN/Telnet Access ..........................................................................

7.7.1 LAN IP Configuration ...........................................................................

7.7.2 Edit the Informix sqlhosts File .............................................................

7.8 Secure Tunnel (ssh) Setup ..............................................................................

7.9 Register SCO OpenServer Operating System ................................................

8.0 GTS System Backup and Restoral (off-line network only) ..........................................

8.1 Backup the Entire System................................................................................

8.1.1 Backup and Schedule Setup ................................................................

8.1.2 Make a Backup CDROM ......................................................................

8.1.3 Fastest Way to Perform a Full System Bootable Backup ....................

8.2 Restore the Entire GTS System ......................................................................

8.2.1 Restore Network Configuration Files (off-line network only) ..............1

9.0 TMS Nodal Hardware Requirements .........................................................................

10.0 Software Download Guidelines ..................................................................................

11.0 Operating Guidelines ..................................................................................................1

11.1 ACM .................................................................................................................

11.2 Alarms..............................................................................................................

11.3 CDA.................................................................................................................

11.4 Diversity and Redundancy...............................................................................

e Notes for GDC Part No. 036U580-C01 Page 3

Publication No. 036R903-V500 GTS Controller Version 5.0.0Issue 4 - May 2006

Page 4

...23

...23

...23

....26

...26

...26

....26

....26

...27

...27

...2

..

11.5 IAR...................................................................................................................

11.6 Manual Routes .................................................................................................

11.7 OCM ................................................................................................................

11.8 OPP .................................................................................................................

11.9 RCC .................................................................................................................

11.10 Redundant Controllers .....................................................................................

11.11 Software Upgrade ...........................................................................................

11.12 Status/Diagnostics...........................................................................................

11.13 Supervisory Communications..........................................................................

11.14 XNET...............................................................................................................

11.15 X.50..................................................................................................................8

12.0 Known Issues................................................................................................................28

Release Notes for GDC Part No. 036U580-C01


Releas

uire

ipped rade C

the the

e a ain)

re.

Section 1 - GTS Software Version 5.0.0

1.0 Overview These release notes provide new information relevant to this version of the General DataComm Transport Management System (GTS) software product, updating the information supplied by the TMS-3000 Controller V5.0.0 Operation Manual. If you reqdetailed operating instructions, please refer to that manual.

The GTS Software Version 5.0.0 is pre-installed and tested on a Pentium-class PC shfrom the factory and fully equipped for use as a TMS-3000 system controller. To upgprevious versions of GTS software operating on legacy controllers, contact your GDrepresentative.

2.0 Software ReferenceThe following table provides detailed reference information for all software modules relevant to the GTS Software Version 5.0.0. Throughout this manual, short forms of software product names will be used. For the latest GDC product information, checkGDC website at http://www.gdc.com or contact your GDC representative.

Note: Remote users at Windows-based workstations require PuTTY client software to makTelnet or ssh (secure shell) connection. The PuTTY client software (in the public domcan be downloaded from http://www.putty.nl/download.html.SCO OpenServer workstations currently have their own Telnet and ssh client softwa

Table 1: Software Reference for TMS GTS Controller

Item Part Number/Description Version / Release

TMS GTS Software Product 036U580-C01 Ver 5.0.0

TMS-3000 Controller Operation Manual 036R603-V500 or greater Latest Issue

GTS 5.0.0 Software/Controller/OS Bundle

Pentium IV Workstation S-076A020-001 Ver --

Informix Standard Engine UC1 Database Software and Runtime License Ver 7.25

SCO OS OpenServer Enterprise Edition Operating System Software Ver 5.07

Microlite Backup Edge Data Archiving and Disaster Recovery Software Ver. 2.1 or later

TMS-3000 Technical Overview 036R304-000 Issue 2 or later

TMS-3000 Installation & Operation Manual 036R303-000 Issue 10 or later



Page 6

.

ypted

port

r

ode

are ation

3.0 Changes and Improvements Since Last ReleaseThis is the initial release of the TMS GTS Version 5.0.0 software. It differs from the previous release as follows:

• This version of GTS software runs on the SCO OpenServer operating systemV5.0.7, with IBM Informix Database Version 7.25, on a Pentium IV-based PC

• Software keys are no longer needed to activate GTS software modules.

• Supports ssh (secure shell) capability which creates a secure tunnel for encrcommunication between a remote workstation and a TMS-3000 controller.

• Supports LAN/Telnet access.

• Supports existing TMS and OCM hardware, including discontinued modules such as RCC Modules at version AH or lower).

• GTS V5.0.0 and higher do not support sync communication at the supervisor(between the node and the controller).

• GTS V5.0.0 and higher do not support MegaView, MegaView DU, NetCon, oNetView.

• GTS V5.0.0 and higher do not support dial backup from the controller to the nat this time. For more information, contact your GDC reepresentative.

• GTS Version V2.2.0 and higher versions do not support the IAC Module.

4.0 Corrected IssuesNone

5.0 Minimum Hardware RequirementsThe Pentium-based TMS-3000 controller is purchased from the factory with all hardwand software components installed and fully tested. The minimum hardware configuris listed below:

• Pentium IV PC, 3 GHz, monitor, keyboard

• One COM port

• Two parallel ports

• Digiboard 4-Port Serial I/O card

• NIC card

• 512 MB RAM

• 80 GB hard drive

• 3.5 floppy drive

• DVD Read/Write drive



Releas

n the 386-tium GTS rs be

tch 5 S

ave

2.2.0

m

an sage

not

the ave

6.0 Replacing GTS V2.2.0 ControllersThe previous version of the GTS software (TMS GTS Version 2.2.0) operates only oSCO XENIX operating system, with an older version of the Informix database, and onbased computer hardware. TMS GTS 2.2.0 will not operate on newer and faster PenIV-based PCs. Although a TMS network may have both GTS V.2.2.0 controllers and V5.0.0 controllers online at the same time, it is recommended that the older controllereplaced with the Pentium IV-class GTS V5.0.0 systems for optimal performance.

Note: IMPORTANT! All GTS V2.2.0 controllers in your TMS network must have Patch #5 and Patch #26 installed. Otherwise, network anomolies will occur that affect operability.

6.1 Replacement GuidelinesThe following conditions must be met before a GTS V2.2.0 controller can migrate toGTS V 5.0.0:

• The controller to be replaced must be at GTS Version 2.2.0 and must have Paand Patch 26 installed in order to migrate to the Pentium IV-class PC with GTVersion 5.0.0.

• Before replacing the older controller, format a floppy from that controller and sits network configuration. This configuration data will be used to replace the default configuration on the new GTS V5.0.0 controller.

• When a GTS 5.0.0 controller has mastership on a network that still has GTS Vcontrollers, the Software Integrity screen on the GTS V2.2.0 controllers will display INV CFG (invalid configuration). This condition does not affect systeperformance.

• When both GTS V2.2.0. and GTS V5.0.0 controllers are online in a network, Alarm Filter created at a GTS V5.0.0 controller can cause a System Error meswhen that Alarm Filter is downloaded to the GTS V2.2.0 controller. This doesaffect system performance. To dismiss the message, press the F9 key.

• When replacing GTS V2.2.0 controllers in larger networks, you can minimizenumber of version alarms generated by allowing a GTS V2.2.0 controller to hmastership of the network until all others have been replaced by GTS V5.0.0controllers.



Page 8

tion

nt.

.

ble.

6.2 Replacement Procedure1. Note the name of the node to which the controller is connected.

2. Unhook the GTS V2.2.0 controller from the node by detaching the COM1 serialcable.

3. Wait until the following alarm message is received at the controller:

Controller Lnk Lvl-Prt [0 or 1] Inoperative4. Log out of the On-line Network and on to the Off-line Network.

5. At the Network Maintenance screen, select Format a Floppy Disk to perform the required formatting operation.

6. At the Network Maintenance screen, select Save Network Configuration Files . A prompt instructs you to insert the formatted disk.

7. At the Continue ? prompt, type y . All configuration files on the hard disk will be stored on the diskette. (This data will be used to replace the default configuradata on the new GTS V5.0.0 controller.)

8. Log off the current network and log on to the second and third networks, if preseRepeat Step 5. through Step 7. for each network.

9. Power up the new GTS V.5.0.0 controller.

10. Select Create New Off-line Network .

11. Enter a name for the network, and then press Enter.

12. At the Network Maintenance screen, select Restore Network Configuration Files .

13. Answer Yes [Y] at the following prompt:

Retaining current PC software revision lists, continue?

14. When prompted, insert Backup Floppy disk #1, #2, or #3 for the first, second or third network, and confirm by typing Y .

15. When the process is complete, the TMS Main Menu appears.

16. Repeat Step 10. through Step 15. for the other networks, if present.

17. With all network revision lists saved onto floppies, select the On-line Network .

18. Enter the user name, then press Enter.

19. When prompted for a node name, enter the name from step 1, and press Enter

20. Connect the GTS V5.0.0 controller to the node by attaching the COM1 serial ca

21. Observe the Status Line for any pertinent communication messages.



Releas

e

ia ssh erating

a time

and

only.

7.0 Controller Software Procedures

7.1 GTS User LoginWhen powering up the controller, the GTS application is launched automatically. Thdefault user accounts for the GTS software are: gts , mso or tty01. Additional default usernames may be provided with your system. No password is required for accessing GTS within the TMS network. Note that in order to access GTS remotely vprotocol, an ssh password is required and must be generated via the OpenServer opsystem as described below.

7.1.1 OpenServer User LoginYou will need to access the SCO OpenServer operating system in order to configure zone, configure LAN/Telnet access, create a ssh password, or launch a Telnet/ssh connection to another controller. The following steps will shut down the GTS softwareprovide the OpenServer # prompt.

1. If not at the TMS GTS Main Menu, press F4 .

• If a network exists, use the arrow keys to select Access Off-Line Network , then press Enter. When prompted, type the username and password for the network. The user must have Maintenance Utility (MUT) privilege.

• If there is no network, select Create Off-Line Network and press Enter. When prompted, type a name for the network.

2. Use the arrow keys to select Controller Maintenance and press Enter.

3. Use the arrow keys to select Shutdown GTS Only and press Enter.

4. Be sure the floppy drive is empty and answer Yes to the questions.

5. At the OpenServer login prompt, type root (This is the default user account for the OpenServer operating system).

6. At the password prompt, type meansquare (the default OpenServer password).

Note: OpenServer user account and password must be entered with lowercase characters

7. The # prompt appears, indicating the OpenServer command line. You can nowconfigure the time zone, or access parameters as described in the following paragraphs.



Page 1

ust

ord

match

er to tocols. TTY ctions.

ke

7.2 Secure Shell (ssh) PasswordsIf you intend to access a controller from a remote workstation via ssh protocol, you mgenerate an ssh password as described below.

1. At the GTS controller, press Alt-F2 to switch to another console.

2. Logon using the user account mso .

3. At the $ prompt, type passwd and then press Enter. If there is already a passwand you want to change it, you will be prompted to enter the existing password.

4. At the menu, type 1 to select Pick a password .

5. At the New Password prompt, enter the desired password and press Enter.

6. At the Re-enter password prompt, retype the password and press Enter. If a misoccurs, you will be prompted to start over.

7. At the $ prompt, type exit and then press Enter.

8. Press Alt-F1 to return to the GTS controller.

7.3 PuTTY Software for Telnet/sshThe PuTTY client software is required at a remote Windows-based workstation in ordrun a management session with a GTS controller via Secure Shell (ssh) or Telnet proPerform the following one-time procedure at the remote workstation to set up the Puclient. Be sure an ssh password has been established if you intend to use ssh conneTelnet connections do not require a password.

1. Launch the PuTTy client software.

2. In the Category box, under Terminal, click keyboard .

3. Under Function keys and keypad , select SCO.

4. In the Category box, click Session to get back to the session configuration.

5. Enter the hostname.

6. Under Protocol , select SSH or Telnet , depending on the type of connectionyou want to make.

7. In the Load, save or delete a stored session box, type a name to add the configuration to the Saved Sessions box. If desired, click Default Settings to make it the default session.

8. Click Save to complete the PuTTY setup.

9. When you next launch PuTTY, click the desired session name and then click Load the session to make the connection. If you save a default session, it will mathe connection automatically.

0 Release Notes for GDC Part No. 036U580-C01


Releas

lled py of system e

, ill TMS

a ta.

oller ckly

re ftware the

o use

dard e:

7.4 TMS GTS SoftwareThe TMS-3000 Controller is shipped from the factory with the GTS software fully instaand ready for configuration. An accompanying Recovery CD contains a complete cothe GTS system software as shipped. This CD can be used to restore the entire GTS to the original factory default settings, if desired. As an alternative, the system can brestored from your own backup CD using the backup utility included with your systemdescribed below. With either method, any unsaved network configuration changes wneed to be restored from a previously saved configuration diskette as described in theGTS Operation Manual, Chapter 41, Network Maintenance.

Note: In some cases, a TMS-3000 controller is shipped from the factory pre-configured foruser’s network; that is, the default database may already have your initial network da

7.5 Activate Microlite Backup Edge SoftwareThe TMS-3000 Controller software system includes Microlite Backup Edge softwarewhich safely archives every file, directory, device node, and special file on your contrhard drive. In the event of a catastrophic hardware failure, this utility allows you to quirecover your GTS system, as described in Chapter 41.

IMPORTANT! You must have previously activated the Microlite Backup Edge softwabefore it can be used to restore a GTS system. Ideally, the Microlite backup edge soshould be activated as soon as the controller is installed in the network. To activate Microlite Backup Edge software, perform the following steps:

1. At the OpenServer prompt, logon as root .

2. Type edgemenu then press Enter.

3. Arrow over to the Setup menu, then arrow down to [Activate Backup Edge].

4. Fill in the appropriate fields and generate a registration number.You may need tthe down arrow key to scroll down to the generated registration number.

5. Follow the activation instructions in the USERGUIDE.pdf file on the Microlite Backup Edge CDROM.

7.6 Configure Time ZoneThe controller is shipped from the factory with the time zone set to EST (Eastern StanTime). To configure the time zone for your local time, perform the following procedur


2. Type the following command:

tz

3. Follow the instructions as prompted for setting the time zone for your locality.



Page 1

ss, cess,

rom a

data rk

.

g

7.7 Configure LAN/Telnet AccessIf the Controller PC is to be connected to a LAN, you will need to set up the IP addrehost name, gateway, etc., and then configure the network interface for LAN /Telnet acas described in the procedures below.

Note: To run a management session with a GTS controller via the ssh or Telnet protocols fremote Windows-based workstation, the PuTTY client software is required.

7.7.1 LAN IP Configuration1. At the OpenServer prompt, logon as root .

2. At the # prompt, type scoadmin and press Enter.

3. Use the arrow keys to select Networks and press Enter.

4. Use the arrow keys to select Network Configuration Manager and press Enter.

5. With the highlight on the Hardware selection, use the Tab key to move to the Current networking configuration box.

6. Under HW Intel Pro/100 M Network Connection, use the arrow keys to select SCO TCP/IP . Press the Tab key to return to the top menu.

7. Use the arrow keys to select Protocol and press Enter.

8. Use arrow keys to select Modify Protocol configuration and press Enter.

9. Tab to each field, use the Delete key to remove any existing data, then enter therequired for your network, such as IP address, hostname, etc. (See your NetwoAdministrator for proper values.)

Note: The local hostname must be entered in no more than eight, all lowercase charactersNumbers may be entered, but the first character must be an alphabetic character.

10. When all entries are correctly entered, tab to [OK] and press Enter. The Modify Networking Product window appears, displaying a success message with [OK] highlighted. Press Enter.

11. Use arrow keys to highlight the Hardware selection, then press Enter.

12. Use arrow keys to select Exit and press Enter. A dialog box appears for relinkinthe kernel. Select Yes and press Enter.

13. Answer y to the questions. Press Enter when prompted:

Do you want this kernel to reboot by default? [Y]Do you want the kernel environment rebuilt? [Y]

14. Press Enter to continue.

15. Use the arrow keys to highlight Client Manager , then press Enter.

16. Arrow over to the Service menu, arrow down to Add... , then press Enter.

17. In the dialog box that appears, select Default Route .



Releas

ay

ow

ntil a

the

e,

re,

.

18. At the Add Default Route box, tab to the Gateway Address field. Type the gatewaddress for the default gateway router on the network where the controllerresides.

19. Tab to highlight the OK field, then press Enter.

20. At the confirmation window, press Enter. The Network Client Manager screen ndisplays a default route.

21. Use the arrow keys to highlight the Host menu, then press Enter.

22. Arrow down to Exit , then press enter to return to the main SCOAdmin screen.

23. Tab to the File menu, then arrow down to Exit and press Enter. The # prompt appears.

24. Proceed to the next section to edit the Informix sqlhosts file.

7.7.2 Edit the Informix sqlhosts FileFor the next procedure, consider these guidelines:

• Letter keys for commands must be in the case shown. For example, use 'i' not 'I '.

• If an error is made and you are not sure how to correct it, press the esc key ubeep is heard. Then type : to get to the command line, and type q! [Enter] to quit without saving. You can then restart the procedure from the beginning.

1. At the # prompt type:

cd /usr/informix/etc

2. Press Enter.

3. At the # prompt, type:

vi sqlhosts

4. Press Enter. The sqlhosts file is displayed.

5. Use the arrow keys to go to the last line displayed. The first and third fields are host name for the computer. The factory default is scosysv .

6. Press the x key repeatedly to delete the name.

7. Press the i key to switch to insert mode.

8. Type the host name for the PC as entered in the LAN IP Configuration procedurabove.

9. Press the esc key to switch to command mode again.

10. Use the arrow keys to get to the start of the third field on the line.

11. Press the x key repeatedly to delete the name.

12. Press the i key to switch to insert mode.

13. Type the host name for the PC as entered in the LAN IP Configuration proceduabove.

14. Press the esc key to switch to command mode again.

15. Press : to get the command line, and type wq and [Enter] to save the file and exit

16. At the # prompt, type: shutdown -g0



Page 1

r turn

ate a shed, ler.

tion, ribed

er to

n

ight, n r is

ecure

17. Press Enter. The following message appears:

The System is being shut down now!Log off now or risk your files being damaged.Do you want to continue? [Y or N] Y

18. Press Enter to confirm shutdown. A message will appear when it is safe to eitheoff the computer or press a key to reboot.

19. Press any key to reboot the PC and restart GTS.

7.8 Secure Tunnel (ssh) SetupThe TMS controller supports a secure shell (ssh) connection from a remote user at aworkstation that has a ssh client. The remote workstation with ssh capability can cresecure tunnel for remote connections to the node, as described below. Once establiencrypted communication can pass between the remote workstation and the control

Before attempting to make a ssh connection from a Windows-based remote workstayou must download and install the PuTTY client software and perform the setup descin Section 7.3.

Note: The PuTTY client software is required at remote Windows-based workstations in ordcommunicate with a GTS controller via the ssh or Telnet protocols.

1. Login to the workstation as a user that has privileges to run the ssh client.

2. Type ssh [hostname] -l mso(where [hostname] represents the controller’s hostname, and mso is your pre-assigned user account name)

3. Press Enter.

• If this is the first time a ssh connection is being made from a workstation, a confirmation message may inform you that the IP/hostname of the workstatiobeing connected is about to be added to the list of known hosts. For example, the SCO OpenServer will display the following:

The authenticity of host ‘[hostname or IP]’ can’t be established. RSA key fingerprint is [mac address].Are you sure you want to continue connecting? (yes/no)

(The actual message will vary according to the operating system.)Type y or yes to confirm, and then press Enter.

4. The workstation monitor will scroll the SCO OpenServer operating system copyropening messages, and then the GTS opening messages. The GTS logo screeappears, indicating that the GTS application software is loaded and the controlleready for TMS-3000 operating routines.

Note: In ssh (secure shell) applications, when a connection is made to the controller via a stunnel, all timestamps are displayed in Greenwich Mean Time (GMT). When the connection is terminated and the user resumes operation at the local controller, timestamps revert to local time.



Releas

iated s to

or the

t

7.9 Register SCO OpenServer Operating System1. At the OpenServer prompt, logon as root .

2. At the # prompt, type scoadmin and then press Enter.

3. Use the arrow keys to select License Manager , then press Enter."SCO OpenServer Enterprise System" should be highlighted and have an assocasterisk (* ). If not, use the tab key to switch to that window and use the arrow keyselect it; then tab back to the menu.

4. Use the arrow keys to select Register and then press Enter.

5. Press Enter to select Register Product .

6. Write down the Registration Lock.

Note: IMPORTANT! The registration lock is case-sensitive. Ensure that you have written itaccurately.

7. Using a computer with Internet access, logon to http://www.sco.com/support/registration/

8. Click on the Register link.

9. Fill in the form to create a user account. User Type should be End User .

10. Click Continue at the bottom of the page and follow the instructions to register OpenServer.

11. In the Product Edition, select "SCO OpenServer Release 5 Enterprise System" fProduct/Family Version "OpenServer 6.0 and 5.0.7".

12. Print the Registration page that results for the Registration Key.

13. Tab to the Registration Key field and enter the Registration Key.

Note: IMPORTANT! The registration key is case-sensitive. Ensure that you have entered iaccurately.

14. Tab to Register and press Enter. You should get a message for successful registration. If not, verify the Registration Key was entered properly.

15. Select License and press Enter.

16. Select Exit and press Enter.

17. Tab to the menu and press Enter.

18. Use the arrow keys to select Exit and press Enter.

19. Log out by typing: Quit



Page 1

at or your ou can

Edge

SCO twork

er. A ough en

a

8.0 GTS System Backup and Restoral (off-line network only)In the rare instance of database corruption or hard disk failure, you will need to reformreplace the faulty hard drive and restore the GTS system from the CD provided withsystem or from a backup CD created at your site. Once the GTS system is restored, ythen update the network configuration with data previously saved to diskette.

To restore the GTS system, you must have previously activated the Microlite Backup software on the controller at the time of installation. Refer to the procedure in Section 7.5 above for instructions on activating the Microlite Backup Edge software.

8.1 Backup the Entire SystemThis procedure backs-up the entire hard disk drive to a bootable CD that includes theOperating System, the Informix Database, the GTS application software, and your neconfiguration files.

8.1.1 Backup and Schedule SetupSet up Backup Parameters


2. At the # prompt, type edgemenu .

3. At the BackupEdge menu, arrow over to [Setup] and press Enter.

4. Arrow down to [Make Recover Edge Media], then press Enter.

5. Select [Image Only for dvd0 Bootable Backups].

6. Select [Generate].

7. Press Enter to continue.

8. Press Enter to continue a second time.

9. Select [Quit]. This setup procedure need only be done for the first backup.

Create a Schedule

1. At the BackupEdge menu, arrow to [Schedule] [Basic Schedule], and press Entseries of help screens may appear the first time this function is run. Proceed thrthe help screens without making any entries until the Edit Backup Schedule screappears.

2. At the Edit Backup Schedule, tab to the Time field and type the desired time forbackup to be performed (24-hour time setting).

3. Tab to the Enabled field and type X.

4. At the Primary Resources field, the entry must be:

hostname:dvd!dvd0 (DO NOT change this setting!)(hostname is your PC network name)

5. Tab to the Day fields and select the desired days for backup by typing X.

6. Tab to the Notify/Advanced [Change] field and press Enter.

7. Tab to the Attempt Bootable field and type X.

8. Tab to [Next] and press Enter.

9. Select [Save].



Releas

his

the

g

d the

g

d the

8.1.2 Make a Backup CDROM1. Shutdown GTS application software, if running.

2. At the OpenServer prompt, login as root


4. At the BackupEdge menu, select [Backup] [Run Scheduled] option.

5. At the Select Scheduled Job screen, choose the Basic Schedule, and [Run] it. Truns the same backup Scheduled Job that you defined during installation. It alsokeeps Sequence information intact.

6. Configure the scheduled backup to make a bootable CD.

7. Insert a blank CDROM into the DVD drive. This will back up the PC hard drive to CDROM. This process will take several minutes.

8. At the Backup/Verify/Index Successful popup window, select [OK].

9. At the Backup Edge information screen, select [Done].

10. When the backup is completed you can view the backup information by selectin[Verify] [View Backup Edge LogFile] [Enter].

11. Select [Verify] [Show Archive] [Enter] to see that the CD is bootable.

12. Select [File] [Exit].

13. Label the CDROM with the Backup PC name, the date and time, GTS V5.0.0, anMicrolite Backup Edge Version number.

8.1.3 Fastest Way to Perform a Full System Bootable Backup1. Shutdown the GTS application, if running.

2. Insert a blank CDROM into the DVD drive.

3. At the OpenServer prompt, login as root


5. Set up the backup Parameters as described in Section 8.1.1. (You only need to do this with the first backup.)

6. At the Backup Edge menu, select [B] [U], put an X in the “Make DVD Bootable” box, then select [Execute Backup] [Enter]. This command combination creates abootable unscheduled full backup of the PC hard drive on the CDROM with all defaults intact.This process will take several minutes.

7. Select [OK] at the Backup/Verify/Index Successful popup.

8. Select [Done] at the Backup Edge information screen.

9. When the backup is completed you can view the backup information by selectin[Verify] [View Backup Edge LogFile] then press Enter.

10. Select [Verify] [Show Archive Label] to see that the CD is bootable.

11. Select [File] [Exit].

12. Label the CDROM with the Backup PC name, the date and time, GTS V5.0.0, anMicrolite Backup Edge Version number.



Page 1

se

drive

ake

o the

tem

the as

8.2 Restore the Entire GTS System

Note: WARNING ! This procedure will restore your entire hard drive. Make sure that you uthe desired backup CDROM or your system WILL NOT be restored properly.

Note: The PC that you are recovering to must have the exact same hardware and hard diskas the PC that did the backup.

1. Shutdown the GTS application, if running.

2. Insert the desired Backup CDROM into the DVD drive.

3. Shut down PC with the following command:

Shutdown -g0

4. After the PC shuts down, select Reboot the PC.

5. At the Boot: prompt, press the Enter key.

6. Follow the prompt to Start Recover EDGE [Enter]

7. Select [Enter] at the command prompt.

8. Select [Automatic]

9. Select [Yes] [Yes]

10. At Archive Information popup, Select [Enter] [Enter] [Enter] [Enter] [Enter]The selected Back up CDROM will restore the PC hard drive. This process will tseveral minutes to complete.

11. When Restore is finished select [Enter]

12. Select [No] at the Do you want to Restore more archives now? question.

13. Select [Quit] to exit Recover Edge.

14. Select [OK] at the Do you want to Restore more archives now? question.

15. Remove the CDROM from the drive.

16. Power off the PC, then power it back on.

17. Start up the TMS GTS controller application. The GTS system is now restored tlast full backup.

• If you had made no changes to the network since your last scheduled full sysbackup, your controller is now fully restored.

• If you had made changes to the network since your last scheduled full systembackup, you should now restore that configuration data by either re-entering changes manually, or loading them from a previously saved backup diskette,described in Section 8.2.1.



Releas

ckup when have a ost nges

ette.

.

e the

sert

th ins

ette

m

ackup

8.2.1 Restore Network Configuration Files (off-line network only)This procedure only restores previously saved network configuration data from a badiskette onto a fully capable GTS system. This procedure is usually only necessary network changes were made after the last scheduled full system backup. You must fully capable GTS system running on the controller and have previously saved the mrecent configuration changes for each network to separate diskettes. Otherwise, chamade since the last full system backup will need to be re-entered manually.

Note: IMPORTANT! Do not perform the following procedure unless you intend to overwriteexisting configuration files on the controller with the backup files from the floppy disk

1. Log onto an off-line network.

2. At the main menu, select Network Maintenance.

3. At the Network Maintenance screen, select Restore Network Configuration FilesThe following prompt appears:

Retaining current PC software revision list, continue?

[Default YES(Y/N)]

4. The revision list is a record of the module versions. It is not necessary to replacrevision list if the module versions have not changed.

• Type N to leave the revision list on the controller unchanged. At the prompt, inthe diskette that contains your previously saved network data.Then proceed to Step 8.

• Type Y to if you want to replace the revision list currently in the controller wia more recent list on the diskette. At the prompt, insert the diskette that contayour previously saved network data. Then proceed to Step 5.

5. The following prompt appears, alerting you that the object (obj) files on the diskrevision list are not necessarily on the Controller and/or in the nodes.

Replace the PC software revision list with one on disk

[Default NO(Y/N)]:

6. Type Y to proceed with revision list restoral. The following prompt appears:

Are the objs in the disk’s revision list in the PC?[Default NO (Y/N)]

7. Type Y to replace the revision list on the controller with the revision list data frothe floppy onto the Controller.

8. At this time, the network configuration data is fully restored.

9. Repeat this procedure for each additional network, if any, using the associated bdiskettes for each network.



Page 2

s are

ase:

)

04)

9.0 TMS Nodal Hardware RequirementsThe following minimum hardware revisions of the TMS common card modules are required to support this release. When restoring older version back-ups, new featuretypically set to default values. Users must review configurations to assure that their requirements are met. For assistance contact your GDC representative.

• Enterprise System Control Card (ESCC) (GDC Part No. 036M337-001)

• Aggregate Control Card (ACC) (GDC Part No. 036M313-003)

• Channel Interface Card (CIC) (GDC Part No. 036P304-002)

• Digital Bridge Card (DBC) (GDC Part No. 036P342-001)

• Combined Digital Aggregate (CDA-T1) (GDC Part No. 036M309-002/3)

• Combined Digital Aggregate (CDA-E1) (GDC Part No. 036M328-001/2)

• ADPCM Compression Module (ACM) (GDC Part No. 036M330-001/2)

• ADPCM Compression Module II (ACM-II) (GDC Part No. 036M335-001/2)

• TMS Packet Processor (TPP) (GDC Part No. 036M360-XXX)

The following lists the minimum revisions of OCM cards required to support this rele

• Common Control Module (CCM) (GDC Part No. 036M400-004)

• DSX1 T1 LIM (GDC Part No. 036M410-001)

• CEPT E1 LIM (GDC Part No. 036M410-002)

• CSU T1 LIM (GDC Part No. 036M410-003)

• V.11 LIM (GDC Part No. 036P436-001)

• V.35 LIM (GDC Part No. 036P436-002)

• BQ LIM/BQ Channel (GDC Part No. 036P438-001)

• Dual Data Module (DDM 232) (GDC Part No. 036P413-001)

• High Speed Data Module EIA232 (HSDM) (GDC Part No. 036P410-001)

• High Speed Data Module V.35 (HSDM) (GDC Part No. 036P410-002)

• High Speed Data Module RS422 (HSDM) (GDC Part No. 036P410-003)

• High Speed Data Module RS423 (HSDM) (GDC Part No. 036P410-004)

• High Speed Data Module G.703 (HSDM) (GDC Part No. 036P416-001)

• Turbo Data Channel - 256K (GDC Part No. GS936P417-001)

• Turbo Data Channel - 512K (GDC Part No. GS936P417-002)

• ADPCM Voice Module (FXS, FXO, or E&M) with/without Echo Canceller

• VLBRV Voice Module (FXS, FXO, or E&M) with/without FAX

• CELP Voice Module (FXS, FXO, or E&M) with/without FAX

• DPV Voice Module (FXS, FXO, or E&M) with/without FAX X.50

• Quad Data Module (GDC Part No. 036P414-001)

• OCM Packet Processor - Ethernet (OPP) (GDC P/N 036M450-001B/003/004

• OCM Packet Processor-Token Ring (OPP) (GDC P/N 036M451-001B/003/0



Releas

CC ntrol.

he

MS

re ad

s

rom

nter

re is r

es for

ot in Slot”

lock

10.0 Software Download Guidelines• GTS software is responsible for downloading the TMS mux software to the ES

module(s) in the network. The ESCC can then update the modules under its coThe mux downloads are non-disruptive and will proceed as expected when tprocedures are properly followed as described in Chapter 1 of the TMS-3000Controller Operation Manual under the paragraphs on Software Updates.

• OCM downloads remain disruptive but are much more efficient, since each T3000 node will download to connected OCM nodes, rather than all OCM downloads proceeding from the Controller. After loading this release, all futuOCM downloads will be non-disruptive. Note that non-disruptive OCM downlorequires redundant CCM cards.

• It is important that all online controllers have the same revision list of version(obj) files for the common system modules.

• In a multiple controller environment, each controller should be disconnected fthe network prior to updating object files. This avoids conflicts between activecontrollers on the network.

11.0 Operating GuidelinesFollow these guidelines in this section to maximize system effectiveness and avoid potential problems. Most of the items are application specific; you will not likely encoumost of the situations described below. However, when you do encounter a system limitation, use these guidelines to work around the limitation. Contact your GDC fieldrepresentative if you have any further questions.

11.1 ACMA problem arises if a 320K bundle circuit is configured between two ACM IIs, and theinsufficient bandwidth in the TMS network to support this circuit. A configuration errowill be reported at the GTS Controller for the ACM IIs, and the ACM IIs will go out ofservice (standby).

11.2 AlarmsInserting a CDA into a slot which has the ACO set may generate alarm clear messagthe port and subaggregates. However, ACO becomes effective shortly thereafter.

If an undefined common card slot becomes defined and the card is not in slot, no “NSlot” alarm is generated. A subsequent alarm regeneration will generate the “Not in alarm.

Because of Alarm filtering that occurs on the CIC/DBC, channel transmit and receive calarms of short durations may not be reported to the TMS Controller.



Page 2

/E1 -llows:

d

on a nnel. 88C

3 or may other

nel t.

issing

egate ectify clear s a

s

ork

en

do so

head oid

gle may

11.3 CDA1. If an X.50 subaggregate is configured on a CDA/T1 -001 or -002 card or a CDA

001 card, the X.50 channel data is inverted. The inversion can be corrected as fo

• If the X.50 channel enters the network on an older CDA card and leaves the network on an older CDA card, there is no inversion. The data will get invertetwice, resulting in no net inversion.

• If the X.50 channel enters the network on an older CDA card and terminatesTMS data card, the inversion can be corrected by inverting the data on the chaThis is done by placing the S1-1 switch on the channel card to the MIL_STD_1position.

• If the X.50 channel enters on an older card and leaves on a new card (T1-00E1-002), the channel will be inverted. It cannot be corrected in the network. It be possible to correct it outside the network (i.e., if one end terminates on anGDC network, the channel card can be set to invert.)

• If the X.50 channel enters on an older card and terminates on an OCM chancard, the data will be inverted. The OCM channel card cannot be set to inver

2. If a CDA subaggregate is more than 1 DS0 and is carried over a link that has mor bad DS0s, the CDA may not generate an alarm.

3. Communications to a remote node could be lost if the DS0 location of a subaggris changed and the subaggregate is the only supervisory path to that node. To rthis situation, access the remote node via the ESCC maintenance console and the CDA configuration. This may be accomplished by configuring the CDA’s slot aredundant ACC with a rate index of 0.

4. Network and Clear channels configured on a CDA actually appear to the CDA asubaggregates. Since IAR and TOR can add or delete these channels, other subaggregates on the CDA may take momentary “hits”. Configure Clear or Netwchannels on the CDA to use DS0 numbers that are higher than any TMS or TMS/network subaggregates. This will avoid hits on the TMS subaggregates whTOR or IAR modifies the clear channels.

5. The Tran/B7 Jumper should be set to Tran (Transparent) in all cases. Failure tocauses data errors and subaggregate failures.

6. There is a problem on the CDA with overhead Ccommunications which affects subaggregates connected to OCM V.35 or V.11 LIMs. Symptoms are loss of overcommunications (subagg down), or inability of OCM to get a configuration. To avthis problem, use only the following configuration combinations:

Total Number of DS0s Maximum Allowable Size ofUsed on CDA (in DS0s) V.35/V.11 Subaggregate (in DS0s)

31, 32 630 925-29 1020-24 11Below 20 No Restriction

For example: If a CDA has a 10 DS0 subagg to a V.35 OCM and also has 15 sinDS0 subaggregates for a total of 25 DS0s used, the 10 DS0 V.35 subaggregateexperience problems.



Releas

it is short

DA n card

in-

ked

, the ual

hich n it

the

agg

d by ter

ens s load

rt

s the

r

11.4 Diversity and RedundancyIf the backup card in a TMS Compact node is switched into service for an ACC whichNOT already set to back up (i.e.; for which the Backup card is not already primed), a link down may be generated (2-5 seconds).

Only insert a CDA card configured as non-redundant 256 into the primary slot. If a Cis configured non-redundant 256 and inserted into the secondary slot and any commois inserted into the corresponding primary slot, the card in the primary slot will comeservice and the CDA in the secondary slot will go out-of service.

11.5 IARIt is recommended that the number of events listed in the IAR event screen be checperiodically. If the number of events exceeds 50, IAR performance will be seriously degraded. Doing a circuit route optimization will reset the event list.

11.6 Manual RoutesWhen configuring a circuit with routing type either “Manual Preferred” or “Manual Required”, if the user enters the “Circuit Route Selection” screen and hits the F4 key“Route Information” screen comes up. On this screen and the “Route Definition” manroute screen, the destination end (located on the right side of the screen) of a link wterminates on a CDA-E1 card will display the DS0 bundle number as one greater thaactually is in the configuration. This is a display issue only.

11.7 OCM1. Disregard “SYS ERR” which may appear on software integrity screen just after

activation of a new version of the OCM software.

2. Performing selftest on a channel card which terminates the only circuit on a submay cause the other subagg (if one exists) to lose sync momentarily.

3. Non-disruptive downloads once started must finish. Trying to abort the downloachanging the revision list may not be effective. Only changing the revision list afdownload is finished will recover the CCM version.

4. During non-disruptive downloads to the redundant CCM, the CCM’s status screwill be in alarm due to the detailed status alarm “RED. CNFG. MISMATCH”. Thialarm is invalid and should be ignored. The status error will clear when the downfinishes.

5. LIMs with network circuits which lose their TMS circuit configuration will not repo“No Configuration” until an optimization is done.

6. After a link outage on a redundant V.35 LIM, it is possible that a red alarm will remain active on the out-of-service LIM even though the link has recovered. Thialarm can be cleared by toggling the out-ofservice LIM into service or re-seatingout-of-service LIM

7. If experiencing inexplicable losses of sync on a V.35/V.11 LIM, it may be due to control 1 (RTS/DCD) into the LIM being in the off state. Check your wiring and/oapplication, as appropriate.



Page 2

up

dule is at

LIM n

ted in

orted

not

uld

e rrect.

ancy

must

s will

s ent til not

al

8. The OCM architecture uses a framing processor on the Channel Module to set communication with the CDA. The OCM searches for a maximum of two subaggregates (aggregates). The framing processor on the common control moshared between the two subaggregates until a configuration is received that hasleast one channel configured and a channel module is present. Until the OCM receives such a configuration, the software integrity screen will not show any configuration for this subaggregate's group. In subaggregate status these subaggregates will show up as “not part of the running configuration”.

9. When doing local loopbacks on a CDA subaggregate connected to an OCM V.35card, the diagnostic screen will first indicate “Local Loopback” status and will theindicate “External Loopback” status. Since the Controller cannot terminate an external loopback, the user must wait for the loopback to time-out before the subaggregate returns to normal.

10. Maintenance terminal features modem support; and diagnostics are not supporthis release.

11. The option to supply an alarm associated with dropping of Control 1 is not suppin the OCM in this release.

12. Do not configure a LIM-T1 module in slot 2 of an OCM enclosure if this slot doeshave an RJ45 connector on the backplane.

13. The VF dBm Monitor on the VCM is a peak latch. For best results, the user shomanually reset the results and collect a few samples.

14. T1/E1 LIM switch options will be displayed under HW options on the network controller only if the LIM has a firmware revision of C- or later. Older LIM firmwarrevisions do not support this feature and the switch status displayed will be inco

15. Running a Self Test on the Primary LIM of a redundant pair will cause a redundtoggle even if the Primary has been “Forced”.

16. Remote OCM subaggregate loopbacks cannot be prematurely terminated, theyrun for the time duration specified when the test was started.

17. When forcing control state changes in channel diagnostics, OCM voice channeldisplay “controller state change” and turn on their test LED whereas OCM data channels will not.

18. When a loopback is initiated on an OCM subaggregate and this subaggregate provides the current communications path to the OCM, then the communicationpath may be lost before the TMS controller receives a diagnostics acknowledgmfrom the OCM. The Controller will appear to lock up for a short period of time uncommunications is restored or the Controller recognizes that communications isavailable. However, the loopback test does function properly.

19. BQM LIM redundancy is not supported

20. BQM LIM is not supported in a Dual LIM configuration.

21. OCM non-disruptive download does not support “fallback” capability.

22. The OCM G.703 channel module's alarm LED is not turned on when an “externsignal loss” alarm is active.

23. Status of any OCM card that was just inserted may temporarily be invalid.



Releas

y

into MS

e to

to the

as

on

ult, that n and

s , and s

nd

is also

n,

h

SU rts an is

with n the

ot

24. An OCM channel module self test will not run if another diagnostic test is alreadrunning on that channel.

25. Stand-by CCMs do not store OCM configuration. When a stand-by CCM comesservice it must get its configuration records from the connected CDA(s) and the TController. Therefore it will take approximately 60 seconds for the OCM to restorfull operation after the CCM swap.

26. If two subaggregates are defined on an OCM at least one circuit must be routedOCM.

27. Local loopbacks on a CDA subaggregate connected to an OCM should be donebilateral loopbacks.

28. Selftest cannot not be commanded on the in-service CCM. The selftest results reported for CCMs are the results from the last selftest performed. SelfTests areperformed on CCMs at power up and when commanded on an out-of-service (redundant) CCM.

29. The USA900 (900 ohm analog port impedance) country code configuration optifor the DPV FXS and FXO cards is not currently implemented by GTS 2.2.

30. If a DPV circuit is configured and saved with a rate selected other than the defaand then the rate-selection screen is reentered, typing of alpha-numeric keys atpoint may cause the cursor to jump to the upper left hand corner of the PC screeecho the typed text. The F3 key will return the cursor to the previous screen. It ipossible that the rate will have been changed to an undesired value at this pointwill need to be re-selected. In order to avoid the problem, use only the arrow keywhen in the rate selection screen.

31. An alarm indication is erroneously reported and summed-up to the LIM, Node aNetwork Status screens when a LIM is forced into service via the Redundancy Control diagnostic feature. In addition, on those same screens, a diagnostic test reported as being in progress, accurately reflecting that a “User State Change” condition exists while the LIM is forced. However, on the LIM Status Detail screethe “Diag” field continues to display “None” (even though the Status Detail subscreen accurately displays “User State Change”).

32. If an OCM is configured with redundant CCMs in slots 1 & 2 while slots 5 througthe last slot are already configured, then slot “2A” is erroneously offered as the default next available slot when attempting to configure a Network circuit to thatNode. Simply change the slot number to 3, 4, or 5.

33. The LIM/CSU does not report the ESF ANSI mode status correctly. If the LIM/Cis both configured and strapped for ANSI ESF mode, the card erroneously repoOffice Compatibility Mismatch, and displays the ANSI strap setting in red. Thereno similar problem with the status when the mode is set for ATT.

34. Running a node selftest may cause a non-recoverable loss of communications the OCM being tested. To re-establish communications, power must be cycled oOCM.

35. LIMs with Network Circuits which lose their configuration will not report “No Configuration” in the Alarm field on the LIM Status screen (and “Configuration NLoaded” in the Status Detail subscreen) until an Optimization is done.



Page 2

e

ured

ven ht to

uired

tatus

e as

a new

und .

ct the

nos-

ry

CDA test

at the

36. When configuring an FXS to FXO circuit connection, it is necessary to select th“A0” selection to configure the FXS channel-end for “Not Ring” conditioning.

11.8 OPPA configuration mismatch will not be reported when a non-OPP card is in a slot configfor an OPP card.

The Encoding field on an OPP Network Circuit screen is erroneously fixed at NRZI, ethough the OPP card defaults to NRZ and is not currently configurable. The PC ougdisplay NRZ, and not allow access to the field.

To use an OPP card in a Network Circuit configuration, the minimum OPP version reqis OPP V2.2.0.

11.9 RCCThere is a new version of the RCC (-003) which does not have an internal modem. Sat the TMS Controller cannot currently distinguish it from other RCC versions.

11.10 Redundant ControllersIf the operator logs onto a different on-line network on the Master Controller and theSubordinate Controller has two networks defined, neither of which has the same namthe new network on the Master, the network will not be crossloaded. In order to forcecrossload of the new network, the operator on the Subordinate Controller must createminimal network with the name of the new network as documented in the TMS 3000Installation and Operation Manual.

11.11 Software UpgradeA CDA may have trouble accepting a software download. This can occur if:

• It is not a background download, that is, the CDA is in boot.

• The boot is revision CD_D (CDA-T1) or E1_A (CDA-E1).

• The CDA is receiving Network or Clear Channel data on port A. The workaroif this occurs is to stop the channel's data flow until the download is complete

11.12 Status/Diagnostics1. The diagnostic indicator on the Channel Summary screen does not always refle

true state of Circuit Diagnostics, rather, it gives the view of the circuit from the selected side only. The test will always be properly displayed in the Circuit Diagtic or Status screen.

2. Some Megamux Plus diagnostic tests are not displayed correctly on a supervisoterminal. However, the tests run correctly.

3. VF-idle test sometimes fails. This can be caused by the propagation delay over links of the controls needed for the test. To work around this problem, restart thewithout terminating it. This resets the failure without interrupting the test.

4. Some local voice channel diagnostics can cause “Out-of-Sync” error messagesremote channel end.



Releas

l

rvice

CM

.

tion

he

d:

ts.

from a

and

must ial rate her

k; at

5. Internal Bert tests on TMS channels deceptively report zero errors if the channecards have no receive clock.

6. In the Equipment Diagnostic screen for a redundant card, if neither card is in-seat the time of examination, the “Card In-service” field should show “Neither”, however, it may blank out.

7. On an OCM-to-OCM voice circuit it is necessary to terminate the operating test before initiating a VF Monitor Test.

8. It is possible that Supervisory Route Tracing will show successful routing to an Onode even though a User Reset alarm exists to that node.

9. The Subaggregate Status Summary screen may indicate “----” in the Alarm fieldThat does not indicate a problem with the subaggregate. The Subaggregate Diagnostics screen is available for more detail.

11.13 Supervisory CommunicationsTo move a controller between two nodes that have been defined as having a connecwith a network controller, the following steps must be followed:

1. Temporarily detatch the controller from the node by disconnecting the cable to tnode at the controller’s Serial Port 0 (COM1).

2. Go into the Download screen and wait until the following messages are displaye

No recognized network (displayed at top left corner of the screen)

No cnfg (displayed on the green bar at the bottom of the screen)

Controller Lnk Lvl-Prt [0 or 1] Inoperative (alarm received) 3. Log out of the on-line network.

4. Log into the on-line network, entering the username and password at the promp

5. At the next prompt, enter the name of the second node, or press Enter to select list of nodes.

6. After your entry or selection, press Enter.

7. Re-attach the controller to the node. A System Initialization message appears, indicating that supervisory communication has resumed between the controller the second node.

11.14 XNETWhen using special rates over an XNET link, for either link rate or circuits, the rates have the same rate index in both networks. For example, if a rate is defined as specnumber 3 in one network, it also must be defined as special rate number 3 on the otnetwork.

Not all combinations of signalling are supported on a voice circuit across an XNET linleast one end must be configured for E&M.



Page 2

-an l

hive

ve.

11.15 X.501. An OCM X.50 termination circuit (configured to an X.50 DS0) must have a corre

sponding X.50-bundle/network-circuit configured in order to be fully functional. If X.50 termination circuit's network circuit is not configured, then the X.50 channecard will remain out of service. The TMS Controller's status screen will report noerror conditions for this channel.

2. 14.4Kbps X.50 channel rates is not supported.

12.0 Known Issues• When the alarm log gets full, alarms will not display on the screen. Be sure to arc

alarms and then purge the alarm log at regular intervals.

• Reset clock source does not reset “forced” nodes.

• Font size or row placement causes truncation in document network.

• As a security measure, users will not be able to view password files at the GTS controller. For assistance with stored passwords, contact your GDC representati


Section 1 - GTS Software Version 5.0.02.0 Software Reference3.0 Changes and Improvements Since Last Release4.0 Corrected Issues5.0 Minimum Hardware Requirements6.0 Replacing GTS V2.2.0 Controllers6.1 Replacement Guidelines6.2 Replacement Procedure

7.0 Controller Software Procedures7.1 GTS User Login7.1.1 OpenServer User Login

7.2 Secure Shell (ssh) Passwords7.3 PuTTY Software for Telnet/ssh7.4 TMS GTS Software7.5 Activate Microlite Backup Edge Software7.6 Configure Time Zone7.7 Configure LAN/Telnet Access7.7.1 LAN IP Configuration7.7.2 Edit the Informix sqlhosts File

7.8 Secure Tunnel (ssh) Setup7.9 Register SCO OpenServer Operating System

8.0 GTS System Backup and Restoral (off-line network only)8.1 Backup the Entire System8.1.1 Backup and Schedule Setup8.1.2 Make a Backup CDROM8.1.3 Fastest Way to Perform a Full System Bootable Backup

8.2 Restore the Entire GTS System8.2.1 Restore Network Configuration Files (off-line network only)

9.0 TMS Nodal Hardware Requirements10.0 Software Download Guidelines11.0 Operating Guidelines11.1 ACM11.2 Alarms11.3 CDA11.4 Diversity and Redundancy11.5 IAR11.6 Manual Routes11.7 OCM11.8 OPP11.9 RCC11.10 Redundant Controllers11.11 Software Upgrade11.12 Status/Diagnostics11.13 Supervisory Communications11.14 XNET11.15 X.50

12.0 Known Issues

Documents

GTS Controller Version 5.0 - GDCGTS Controller Version 5.0.0 Release Notes 036R903-V500, Issue 4 - May 2006