TMS Controller Version 5.1 - gdc.com · Microlite Backup Edge Data Archiving and Disaster Recovery Software Ver. 2.2 TMS Controller Software Product Ver 5.1.4 TMS-3000 Controller

TMS Controller Version 5.1.4Release Notes 036R903-V514, Issue 5 - July 2008

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© 2008 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.

TMS Controller Version 5.1.4 Publication No. 036R903-V514Issue 5 - July 2008

Releas

TABLE OF CONTENTS5

......

.....6

......6

.....7

.....7

.....7

......8

......9

....9

....9

.....10

..10

.11

12

.13

...14

...15

16

.16

.16

17

7

18

..19

...19

...19

.20

..20

...21

2

..23

...23

..23

...25

Section 1 - TMS Controller Version 5.1.4..........................................1.0 Overview ......................................................................................................................... 52.0 Software Reference.....................................................................................................5

3.0 TMS Version and Patch History ..................................................................................

4.0 SCO Operating System Guidelines.............................................................................

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

6.0 Replacing TMS V2.2.0 Controllers .............................................................................

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

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

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

7.1 TMS User Login ...............................................................................................

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

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

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

7.4 Configuring a new TMS Controller...................................................................

7.4.1 New LAN IP Configuration ...................................................................

7.4.2 Edit the Informix sqlhosts File .............................................................

7.4.3 Secure Tunnel (ssh) Setup ..................................................................

7.4.4 Register SCO OpenServer Operating System ....................................

7.4.5 Activate Microlite Backup Edge Software ............................................

7.4.6 Configure Time Zone ............................................................................

7.4.7 Configure SNMP Traps ........................................................................

7.5 Modify TMS Controller Configuration ..............................................................

7.5.1 Modify Existing LAN IP Configuration ................................................1

7.5.2 Modify an Exisiting Gateway ................................................................

8.0 TMS 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 TMS System.......................................................................

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

9.0 Upgrading the TMS Controller to Version 5.1.4 ..........................................................

9.1 Prepare for Version 5.1.4 Upgrade ..................................................................

9.2 Configure the SNMP Agent..............................................................................

9.3 TMS Software Upgrade ...................................................................................

e Notes Page 3

Publication No. 036R903-V514 TMS Controller Version 5.1.4Issue 5 - July 2008

Page 4

.25

....26

....2

..27

..28

..28

..28

..28

...29

...29

..29

...30

...30

..30

...30

...30

..31

....31

...31

..31

...31

..32

...33

..

9.4 Compile TMS MIBs ..........................................................................................

10.0 TMS Nodal Hardware Requirements .........................................................................

11.0 Operation Guidelines ..................................................................................................7

11.1 Software Download Guidelines ........................................................................

11.2 Supervisory Communications Guidelines ........................................................

11.3 Controller Mastership Guidelines.....................................................................

11.3.1 Login Guidelines ..................................................................................

11.3.2 Swap of Mastership .............................................................................

11.4 Alarms Guidelines ...........................................................................................

11.5 Diversity and Redundancy Guidelines ............................................................

11.6 IAR Guidelines .................................................................................................

11.7 Manual Routes Guidelines...............................................................................

11.8 Redundant Controllers Guidelines...................................................................

11.9 XNET Guidelines .............................................................................................

11.10 X.50 Guidelines ...............................................................................................

11.11 Status/Diagnostics Guidelines .........................................................................

11.12 ACM Module Guidelines..................................................................................

11.13 OPP Guidelines...............................................................................................

11.14 RCC Guidelines ...............................................................................................

11.15 XNET Guidelines .............................................................................................

11.16 X.50 Guidelines ...............................................................................................

11.17 CDA Module Guidelines ..................................................................................

11.18 OCM Guidelines ..............................................................................................

12.0 Known Issues................................................................................................................36

Release Notes


Releas

s the

nual.

ed e C

the the

nce

e a ain)

re.

Section 1 - TMS Controller Version 5.1.41.0 Overview

These release notes provide new information relevant to this version of the General DataComm Transport Management System (GTS) controller, hereafter referred to aTMS Controller. This document updates information in the TMS-3000 Controller V5.1.0 Operation Manual. If you need detailed operating instructions, please refer to that ma

TMS Software Version 5.1.4 is pre-installed and tested on a Pentium-class PC shippfrom the factory, fully equipped for use as a TMS-3000 system controller. To upgradprevious versions of TMS 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 TMS Software Version 5.1.4. 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: As later versions of SCO OS become available, a later version of the SCO MaintenaPack may be required. Contact your TMS representative for more information.

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

Note: When software/hardware components are installed/configured, refer to Section 10.0, Section 11.0, Section 12.0 in this document for important module/controller guidelines.

Table 1: Software Reference for TMS Controller

Item Part Number/Description Version

TMS 5.1.4 Software/Controller/OS Bundle

Pentium IV Workstation (Desktop Mid-tower) S-076A020-001 Ver --

Pentium IV Workstation (Rackmount 19” 3RU) S-076A021-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

SCO Maintenance Pack MP5 or higher

Microlite Backup Edge Data Archiving and Disaster Recovery Software Ver. 2.2

TMS Controller Software Product Ver 5.1.4

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

TMS-3000 Technical Overview 036R304-000 Latest Issue

TMS-3000 Installation & Operation Manual 036R303-000 Latest Issue

e Notes Page 5


Page 6

d

cal) rd port.

e

f

ller

gs

s

m and

MS d

rly.

3.0 TMS Version and Patch HistoryTMS Software Version 5.1.4 resolves the following reported problems:

• Fixed a problem where multiple configurations would occasionally stop all subordinate controllers in a network from completing the update.

• Fixed a problem where the start point in an OCM circuit could not be change(OCM-OCM or OCM-TMS).

• Fixed communication interruption between the controller and the attached (lonode, caused when the user enabled Aggregate Performance on the digiboa

• Fixed ACC card configuration problem that prevented the user from setting thdesired out-of-sync delay time.

• Fixed a problem where a restart of TMS software caused a 30-second loss osystem time, approximately.

• Fixed controller processing slowdown that was due to inadequate available memory resources.

• Fixed a problem that caused the display of false smux errors on the screen.

• Fixed a problem so that TMS software will automatically restart after a contromalfunction.

• Version 5.1.4 with SCO MP5 resolves a problem that affected Daylight SavinTime processing. See Section 4.0 SCO Operating System Guidelines.

Note: For important information on the additional capabilities and/or restrictions of previoureleases, refer to the associated Release Notes posted on www.gdc.com.

4.0 SCO Operating System GuidelinesThe Pentium-based TMS-3000 controller is purchased with the SCO operating systeassociated Maintenance Pack components installed and fully tested.

Note: IMPORTANT! If you intend to upgrade an existing TMS Version 5.X Controller with TV5.1.4, ensure that the required SCO OS and Maintenance Pack are already installebefore performing the TMS upgrade. Otherwise, SCO utilities will not function prope

Previous Versions

Description of Change

TMS Ver 5.1.3 Fixed multiple issues associated with larger networks.Fixed clear channel configuration issues between a MiniMux and a CDA card.Fixed a problem in networks with three or more configured V5.X controllers.Fixed buffer overflow that disrupted master-slave controller communication

TMS Ver 5.1.2 Internal GDC Engineering build only (Not for General Release)

TMS Ver 5.1.1 Fixed occasional controller lockup in very large networks.Fixed problem with local TTY login at the controller COM port.

TMS Ver 5.1.0 Supports SNMP traps to SNMP hosts.

TMS Ver 5.0.0 Initial release of the TMS Version 5.0.0 software on a Pentium IV PC.

Release Notes


Releas

re elow:

ased PCs.

laced

tch 5 S

ave

rs

an

his key.

ber the

5.0 Minimum Hardware RequirementsThe Pentium-based TMS-3000 controller is purchased with all hardware and softwacomponents installed and fully tested. Minimum hardware characteristics are listed b

• Pentium IV PC, 3 GHz, monitor, keyboard (Desktop or Rackmount)

• One COM (serial) port

• Two parallel ports

• Digiboard 4-Port Serial I/O card

• Ethernet Network Interface

• 512 MB RAM

• 80 GB hard drive

• 3.5 floppy drive

• DVD Read/Write drive

6.0 Replacing TMS V2.2.0 ControllersAn older version of the TMS software, TMS Version 2.2.0, operates only on the SCOXENIX operating system, with an older version of the Informix database, and on 386-bcomputer hardware. TMS 2.2.0 will not operate on newer and faster Pentium IV-basedAlthough a TMS network may have both TMS V.2.2.0 controllers and TMS V5.X.X controllers online at the same time, it is recommended that the older controllers be repwith the Pentium IV-class TMS V5.X.X systems for optimal performance.

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

6.1 Replacement GuidelinesThe following conditions must be met before a TMS V2.2.0 controller can migrate toTMS V 5.X.X:

• The controller to be replaced must be at TMS Version 2.2.0 and must have Paand Patch 26 installed in order to migrate to the Pentium IV-class PC with TMVersion 5.X.X.

• 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 TMS V5.X.X controller.

• When a TMS 5.X.X controller has mastership on a network that still has TMSV2.2.0 controllers, the Software Integrity screen on the TMS V2.2.0 controllewill display INV CFG (invalid configuration). This condition does not affect system performance.

• When both TMS V2.2.0. and TMS V5.X.X controllers are online in a network,Alarm Filter created at a TMS V5.X.X controller can cause a System Error message when that Alarm Filter is downloaded to the TMS V2.2.0 controller. Tdoes not affect system performance. To dismiss the message, press the F9

• When replacing TMS V2.2.0 controllers in larger networks, minimize the numof version alarms generated by giving a TMS V2.2.0 controller mastership ofnetwork until all others have been replaced by TMS V5.X.X controllers.

e Notes Page 7


Page 8

tion

sent.

.

ble.

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

2. Unhook the TMS 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 off 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 TMS V5.X.X controller.)

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

9. Power up the new TMS V.5.X.X 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 TMS V5.X.X controller to the node by attaching the COM1 serial ca

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

Release Notes


Releas

e

a ssh erating

a time

and

only.

7.0 Controller Software Procedures

7.1 TMS User LoginWhen powering up the controller, the TMS application is launched automatically. Thdefault user accounts for the TMS software are: gts , mso or tty01. Additional default usernames may be provided with your system. No password is required for accessing TMS within the TMS network. Note that in order to access TMS remotely viprotocol, 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 TMS softwareprovide the OpenServer # prompt.

1. If not at the TMS 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.

e Notes Page 9


Page 1

ust

ord

match

er to ocols. 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 TMS controller, press Alt-F2 to switch to another console.

2. Log on 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 TMS 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 TMS controller via Secure Shell (ssh) or Telnet protPerform 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


Releas

plete e TMS

can ed ill TMS

a ta.

res

ns:

om a

ssary d

7.4 Configuring a new TMS ControllerThe TMS-3000 Controller is shipped from the factory with the TMS software fully installed and ready for configuration. An accompanying Recovery CD contains a comcopy of the TMS system software as shipped. This CD can be used to restore the entirsystem to the original factory default settings, if desired. As an alternative, the systembe restored from your own backup CD using the Microlite Backup Edge utility includwith your system. With either method, any unsaved network configuration changes wneed to be restored from a previously saved configuration diskette as described in theOperation 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

To configure a new controller and activate all required utilities, the following procedumust be performed in the sequence given:

Section 7.4.1 : New LAN IP Configuration

Section 7.4.2 : Edit the Informix sqlhosts File

Section 7.4.3 : Setup Secure Tunnel (if applicable)

Section 7.4.4 : Register SCO OpenServer Operating System

Section 7.4.5 : Activate Microlite Backup Edge Software

Section 7.4.6 : Time Zone Configuration

Section 7.4.7 : Configure SNMP Traps

To modify the LAN configuration of an existing controller, refer to the following sectio

Section 7.5.1 : Modify Existing IP, Mask and Broadcast Address (as needed)

Section 7.5.2 : Modify Existing Gateway IP (as needed)

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

Note: IMPORTANT! Before you begin, acquire the correct controller hostname, host IP address, and gateway IP address from your network administrator. This data is neceto configure LAN/Telnet access, register the SCO OpenServer operating system, anactivate the Microlite Backup Edge software.

e Notes Page 11


Page 1

ress, N

you

data rk

, and s not ame.

e t.

then ess

g

7.4.1 New LAN IP ConfigurationWhen the Controller PC is to be connected to a LAN, you will need to set up the IP addhost name, gateway IP address, etc., and then configure the network interface for LA/Telnet access, as described in the procedures below.

Note: IMPORTANT! The following procedure is only for first time set up of a new system. Ifneed to change an existing IP address, host name, gateway IP, etc., skip to Section 7.5.

1. At the OpenServer prompt, log on 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 then 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: IMPORTANT! Local hostname must be no more than eight alphanumeric charactersthe first character must be a letter. Use only lowercase for letters. If the hostname doecomply with these requirements, contact your Network Administrator for a new hostn

Note: IMPORTANT! Check carefully all values typed in the fields, especially your hostnamentry. DO NOT proceed to the next step unless you are certain the values are correc

10. When you are certain all entries are typed correctly in the fields, tab to [OK] andpress Enter. The Modify Networking Product window appears, displaying a succmessage 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.

2 Release Notes


Releas

ay

u

ow

ntil a

the

e.

e.

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

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.(See your Network Administrator for the proper gateway address.)

Note: IMPORTANT! Check your gateway IP address entry carefully before proceeding. Yomust enter the exact gateway address as provided by your Network Administrator.

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 Section 7.4.2 to continue the TMS configuration.

7.4.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 PC host name as entered in the LAN IP Configuration procedure abov

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 PC host name as entered in the LAN IP Configuration procedure abov

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

e Notes Page 13


Page 1

r turn

ate a shed, ler.

must

er to

n

ight n.

ecure nates

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

16. At the # prompt, type:

shutdown -g0

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 TMS.

7.4.3 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 ssh connections from a Windows-based remote workstation, you download/install PuTTY client software and perform the setup described in Section 7.3.

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

1. Log on 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 copyrand opening messages. The GTS logo screen appears, indicating that the TMSapplication software is loaded and the controller is ready for TMS-3000 operatio

Note: In ssh (secure shell) applications, when a connection is made to the controller via a stunnel, timestamps reflect Greenwich Mean Time (GMT). When the connection termiand the user resumes operation at the local controller, timestamps reflect local time.

4 Release Notes


Releas

iated s to

or the

7.4.4 Register SCO OpenServer Operating System1. At the OpenServer prompt, log on 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! Registration Lock is case-sensitive. Be sure to copy it accurately.

7. Using a computer with Internet access, log on 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! Registration Lock is case-sensitive. Be sure to copy it accurately.

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 off by typing: Quit

e Notes Page 15


Page 1

oller ckly

MS ware the

o use

eat up

dard e:

and the

7.4.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 TMS system, as described in Chapter 41.

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


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.

Note: Once activated, Microlite Backup Edge can be used for backup and restoral of the controller. Refer to Section 8.1 for detailed information and procedures.

Note: IMPORTANT! If you need to change the hostname or host IP address, you must repthis procedure to generate a new registration number and re-activate Microlite BackEdge.

7.4.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.

7.4.7 Configure SNMP TrapsSNMP Traps are supported in controllers installed with TMS Software Version 5.1.0later. To add or modify SNMP host addresses, or change the host listening port fromdefault 162, refer to Chapter 42 of the latest issue of the TMS-3000 Controller Operation Manual (036R603-V510 or higher).

6 Release Notes


Releas

s, edure.

ress.

then ess

g

dress, to

7.5 Modify TMS Controller Configuration

Note: IMPORTANT! The following procedures are only for modifying an existing IP addreshost name, gateway IP, etc. If you need to set up a new system, do not use this procInstead, follow the steps in Section 7.4.1 New LAN IP Configuration.

7.5.1 Modify Existing LAN IP Configuration1. At the OpenServer prompt, log on as root .



4. Use the arrow keys to select Network Configuration Manager then 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 the IP address field and change as required.

10. Tab to the Net Mask field and change as required.

11. Tab to the Broadcast address field and change as required.

Note: IMPORTANT! The Broadcast address should not be confused with the gateway add

12. When you are certain all entries are typed correctly in the fields, tab to [OK] andpress Enter. The Modify Networking Product window appears, displaying a succmessage with [OK] highlighted. Press Enter.

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

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

15. 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]

16. Press Enter to continue. The system will reboot and start up with the new IP admask and broadcast address. If you also need to modify the gateway, continue Section 7.5.2.

e Notes Page 17


Page 1

u

ow

7.5.2 Modify an Exisiting Gateway1. At the OpenServer prompt, log on as root .



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

5. Use arrow keys to highlight the Services selection, then press Enter.

6. Tab to /etc/hostfile

7. Use arrow keys to select Default route and press Enter.

8. Tab to Gateway IP Address

9. Select Modify to highlight the gateway IP address field.

10. Type in the appropriate Gateway IP address.

Note: IMPORTANT! Check your gateway IP address entry carefully before proceeding. Yomust enter the exact gateway address as provided by your Network Administrator.

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

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

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

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

15. Tab to the File menu, then arrow down to Exit and press Enter. The # prompt appears. This completes the procedure for modifying the gateway IP address.

8 Release Notes


Releas

at or your ou can

Edge

SCO twork

n. up

a

8.0 TMS 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 TMS system from the CD provided with system or from a backup CD created at your site. Once the TMS system is restored, ythen update the network configuration with data previously saved to diskette.

To restore the TMS 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.4.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 TMS 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 Enter. A series of help screens may appear the first time this function is ruProceed through the help screens without making any entries until the Edit BackSchedule screen appears.

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] .

e Notes Page 19


Page 2

the

g

.

and

with

g

and

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

2. At the OpenServer prompt, log on 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. This runs 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, TMS V5.X.X, the Microlite Backup Edge Version number.

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

2. Insert a blank CDROM into the DVD drive.

3. At the OpenServer prompt, log on 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 a bootable unscheduled full backup of the PC hard drive on the CDROMall 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, TMS V5.X.X, the Microlite Backup Edge Version number.

0 Release Notes


Releas

se

drive

ake

last

tem

the as

8.2 Restore the Entire TMS 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 TMS 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 really want to exit RecoverEDGE?] question.

15. Remove the CDROM from the drive.

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

17. Start up the TMS controller application. The TMS system is now restored to thefull 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.

e Notes Page 21


Page 2

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 TMS system. This procedure is usually only necessary network changes were made after the last scheduled full system backup. You must fully capable TMS 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.

2 Release Notes


Releas

:

ngly intend Port

s ets.

MP

9.0 Upgrading the TMS Controller to Version 5.1.4The following procedures are intended for patch and software upgrades on deployedcontrollers that are already running at least TMS software version 5.0.0. For older controllers running TMS Version 2.2.0, refer to the procedures in Section 6.0 Replacing TMS V2.2.0 Controllers, or contact your GDC representative for assistance.

You must preform the upgrade procedures in the proper sequence, as shown below

• Ensure that the SCO MP5 is installed.

• Prepare system for upgrade

• Configure SNMP Agent

• Update TMS Software

• Modify SNMP Manager

To take advantage of the streamlined install script provided for this upgrade, it is strorecommended that all SNMP parameters be entered as prompted, even if you do notto implement the SNMP trap feature right away. SNMP trap destinations and the UPDassignment, however, can be easily added and modified at a later date as needed.

Note: IMPORTANT! Avoid terminating the install script prematurely. Enter the proper valueas instructed, rather than using default values shown on the screen in [square] brack

9.1 Prepare for Version 5.1.4 Upgrade1. Shut down TMS from the main menu by selecting Controller Maintenance

and then Shutdown GTS Only .

2. When the Login: prompt appears, login as root. For the password type meansquare or enter the password assigned by your system administrator.

3. Insert the TMS 5.1.4 Upgrade CD in the CDROM drive.

4. At the # prompt type:

# mount /dev/cd0 /mnt

# cp /mnt/installupg . (Be sure to include the . in the entry.)

# ./installupg

9.2 Configure the SNMP AgentPerform Step 5. through Step 11. to configure the SNMP Agent on your controller for thefirst time, or to change existing SNMP parameters. If you do not intend to use the SNAgent, type q in Step 5. to skip to the Section 9.3 TMS Software Upgrade procedure.

5. Once the system is prepared for the upgrade as described above, the followingmessage will appear:

Do you wish to update or remove the SNMP Agent Configuration files? Please enter: u - to update or r - to remove or enter q to quit[q]:

e Notes Page 23


Page 2

r and

eters

e ss.

this

na-

r to ).

ill dify

Note: IMPORTANT! To proceed with SNMP configuration, you must type u now. Typing r , q or pressing Enter will terminate SNMP configuration and launch otheprocesses, such as the TMS Software Upgrade. Be sure to cancel those processes continue with SNMP Agent configuration until completed.

6. Type u and then press Enter to configure the SNMP agent now with the paramfor your environment. The following continuation prompt appears.

Do you wish to continue installing the SNMP Agent? (y/n)

7. Type y to continue.

8. The SNMP Agent Setup message appears. At the continuation prompt, type y .The MIB System Setup message appears.

• At the prompt, enter your sysContact name, normally the local system administrator, then press Enter.

• At the next prompt, enter your sysLocation then press Enter.

9. SNMP Community Setup information is displayed. Since TMS does not performSNMP sets or gets , no entry is required. Just press Enter at the prompt. Thinstall script automatically fills in the community name “public” for read-only acce

10. SNMP Trap Systems Setup information is displayed. If you know your trap destinations and community names, enter them at this time. If you want to enterinformation at a later date, you may type q to skip any of the prompts in this step.

A. At the prompt, enter a community/session name, typically “public”.

B. At the next prompt, enter the host IP address, using the proper format, e.g., ###.###.###.### then press Enter.

C. The community/session prompt reappears, allowing you add additional destition IP addresses in the same manner. Otherwise, press q to quit.

D. The standard UDP Port 162 is automatically assigned to your traps.

Note: To add or modify SNMP host addresses, or change host listening port from 162, refeChapter 42 in the TMS-3000 Controller Operation Manual (036R603-V510 or higher

11. SMUX Peer Setup information is now displayed. At the prompt, you must pressEnter . The install script automatically fills in the correct peer name.

12. SNMP Agent configuration at the TMS controller is complete and the installer wproceed immediately to the TMS 5.1.4 upgrade. After the upgrade, you must moyour SNMP Manager to recognize TMS traps, as described in Section 9.4 Compile TMS MIBs.

4 Release Notes


Releas

d or

ed.

.

ing:

er.

start,

ith

ler, r, as

9.3 TMS Software UpgradeThe install script proceeds automatically to this point when you have either completeinterrupted the previous SNMP Agent configuration process. The message, ABOUT TO COPY FILES.... , will display, indicating that the TMS software is about to be updat

Note: IMPORTANT! If you have not configured the SNMP Agent as described in Section 9.0, quit the upgrade process and complete SNMP Agent configuration before continuing

13. Once you have configured the SNMP Agent, the install script displays the followABOUT TO COPY FILES....

14. You must press Enter to upgrade TMS software. Files are copied to the controll

Note: IMPORTANT! Typing q will terminate the TMS Software Upgrade.

15. When complete, the following messages are displayed:Modifying kernel tunable parameters...

The UNIX operating system will now be rebuilt...

(... additional messages)

The UNIX kernel has been rebuilt.

16. Type y (es) when the following prompt appears:

Do you want this kernel to boot by default? (y/n)

17. Type y (es) when the following prompt appears:

Do you want the kernel environment rebuilt? (y/n)

18. At the # prompt type: shutdown -g0 then press Enter. A warning/confirmationmessage appears as follows: Do you want to continue? (y or n)

19. Type y then press Enter. The system will display shutdown messages.

20. Remove the Install CD from the drive, then press any key to reboot the PC. On rethe new software will be in effect. Be sure to do a full system backup (Section 8.1.3).

21. If you have configured the SNMP Agent, you must now compile the TMS MIBs wyour SNMP Manager, as described below.

9.4 Compile TMS MIBsFor your SNMP Network Manager to recognize traps received from the TMS controlyou must acquire the MIB source files and compile them with your Network Managedescribed below:

1. Point your browser to ftp://ftp.gdc.com/pub/mibs/gts_tms and download the following TMS MIB source files:

ALMTSK.mib

Smi.defs

2. Compile these MIBs according to your SNMP Manager’s requirements.

e Notes Page 25


Page 2

s are

ase:

)

04)

10.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

6 Release Notes


Releas

nter

The es are nual

0 ding

-

iles

on

not t

ion,

oller

11.0 Operation 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 Software Download Guidelines• TMS software is responsible for downloading the TMS mux software to the ESCC

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

• OCM downloads remain disruptive but are much more efficient, since each TMS 300node will download to connected OCM nodes, rather than all OCM downloads proceefrom the Controller. After loading this release, all future OCM downloads will be nondisruptive. Note that non-disruptive OCM download requires redundant CCM cards.

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

• In a multiple controller environment, each controller should be disconnected from thenetwork prior to updating object files. This avoids conflicts between active controllersthe network.

• With multiple downloads, occasionally one subordinate controller in the network maycomplete the update. To correct this, shutdown and restart the TMS software on thasubordinate controller.

• In a multiple controller environment, the “Examine CURRENT Routing -> Examine Circuits” screen of subordinate controllers may temporarily show no circuits. In additthe Examine CURRENT Routing -> Examine Event List may only display: END-OF-EVENT-HISTORY. This is a temporary situation that can occur when the master contris downloading changes to the network. It will persist until the master controller has completed the download.

IMPORTANT: If this situation occurs, the operator should take no corrective action other than verifying the following screen displays:

A. Monitor the master controller’s Download screen until the “Restoral: Current Activity” section displays: Awaiting Next Event .

B. At the TMS Controller Main Menu -> Diagnostics -> TMS Controller screen, verify that the “Number of Missing Updates” section displays all green zeros.

C. At this point, the “Examine Circuits” screen will display the correct routing information.

e Notes Page 27


Page 2

tion

e

d:

pts.

from a

and

a

000 ease tc.

and

rized

for

11.2 Supervisory Communications GuidelinesTo 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 detach the controller from the node by disconnecting the cable to thnode 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 off of the on-line network.

4. Log onto the on-line network, entering the username and password at the prom

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.3 Controller Mastership Guidelines

11.3.1Login Guidelines• Caution! You should only perform a Telnet or SSH or Remote TTY Login into

Subordinate TMS 3000 controller, and not a Master TMS 3000 Controller.

• It is advised Not to Telnet or SSH or Remote TTY Login into the Master TMS 3controller because this will terminate the current master's TMS session and cits current activities, e.g., Multi-Controller downloads, IAR processing, TOR e

11.3.2Swap of MastershipSwap of mastership between two controllers involves configuring the current masterthe intended master, as well as checking all subordinate controllers.

Note: IMPORTANT! Swap of mastership should only be performed as required by an authotechnician.

1. Check that all controllers agree as to which controller is the master:Select TMS Main Menu -> Diagnostics -> TMS Controller. Column 2 (labeled “M/S”) should match for each controller in column 1.

2. Check that the subordinate controllers have all outstanding updates. Select TMS Main Menu -> Diagnostics. The “Num. of Missing Updates” columnshould show all green zeros, indicating all controllers are up to date. If not, wait the updates to clear. A single update may take 30 minutes to clear.

8 Release Notes


Releas

s. ght-

,

ler. e.

ftware

as to

es for

ot in Slot”

lock

m larms

p

8:

it is short

DA n card

in-

ked

3. Check that the current master controller is not busy with active or queued eventAt the current master controller, select TMS Main Menu -> Download. The top rihand field (column header is Restoral: Current Activity) should read Awaiting Next Event . If the column reads a current activity, wait for all activities to clearthen repeat Step 2.

4. From the TMS Main Menu on any controller, select Diagnostics -> TMS ControlSelect Switch Controller Mastership, then enter the new master controller's nam

5. Watch and ensure that the current master and the intended master controller soperforms a restart and returns to the login prompt.

6. Login to the former master and the new master to ensure both controllers agreewhich controller is master, and verify that the master is the one targeted in Step 4.

11.4 Alarms Guidelines• Inserting a CDA into a slot which has the ACO set may generate alarm clear messag

the 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.

• After every complete or general download, Historical Alarms are deleted from the subordinate controllers. This will clear the screen display of the two most recent alarmessages received from the network (Lines 24 and 25). Occasionally, one or two old aare displayed.

• When the alarm log gets full, alarms will not display on the screen. Be sure to backualarms and then purge the alarm log at regular intervals.

Note: For procedures on backing up alarms onto a floppy or a CD/DVD, refer to Chapter 3Alarms, in the TMS-3000 Controller Operation Manual (036R603-V510 or higher).

11.5 Diversity and Redundancy GuidelinesIf 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 to 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.6 IAR GuidelinesIt 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.

e Notes Page 29


Page 3

, the ual

hich n it

e as

a new

must ial rate ork.

k; at

ding

ons

e true ide een.

minal.

links out

e

s have

11.7 Manual Routes GuidelinesWhen 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.8 Redundant Controllers GuidelinesIf 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.9 XNET Guidelines• When 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 specNo. 3 in one network, it also must be defined as special rate No. 3 on the other netw

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

11.10 X.50 Guidelines• An OCM X.50 termination circuit (configured to an X.50 DS0) must have a correspon

X.50-bundle/network-circuit configured in order to be fully functional. If an X.50 termination circuit's network circuit is not configured, then the X.50 channel card willremain out of service. The TMS Controller's status screen will report no error conditifor this channel.

• 14.4Kbps X.50 channel rates are not supported.

11.11 Status/Diagnostics Guidelines• The diagnostic indicator on the Channel Summary screen does not always reflect th

state of Circuit Diagnostics, rather, it gives the view of the circuit from the selected sonly. The test will always be properly displayed in the Circuit Diagnostic or Status scr

• Some Megamux Plus diagnostic tests are not displayed correctly on a supervisory terHowever, the tests run correctly.

• VF-idle test sometimes fails. This can be caused by the propagation delay over CDAof the controls needed for the test. To work around this problem, restart the test withterminating it. This resets the failure without interrupting the test.

• Some local voice channel diagnostics can cause “Out-of-Sync” error messages at thremote channel end.

• Internal Bert tests on TMS channels deceptively report zero errors if the channel cardno receive clock.

0 Release Notes


Releas

at the ay

re

ode

does n is

rted

ured

ven ht to

uired

tatus

must ial rate her

k; at

ding

ons

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

• On an OCM-to-OCM voice circuit it is necessary to terminate the operating test befoinitiating a VF Monitor Test.

• It is possible that Supervisory Route Tracing will show successful routing to an OCM neven though a User Reset alarm exists to that node.

• The Subaggregate Status Summary screen may indicate “----” in the Alarm field. Thatnot indicate a problem with the subaggregate. The Subaggregate Diagnostics screeavailable for more detail.

11.12 ACM Module GuidelinesIf a 320K bundle circuit is configured between two ACM IIs, and there is insufficient bandwidth in the TMS network to support this circuit, a configuration error will be repoat the TMS Controller for the ACM IIs. The ACM IIs will go out of service (standby).

11.13 OPP Guidelines• A configuration mismatch will not be reported when a non-OPP card is in a slot config

for 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.14 RCC GuidelinesThere 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.15 XNET Guidelines• When 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.

11.16 X.50 Guidelines• An OCM X.50 termination circuit (configured to an X.50 DS0) must have a correspon

X.50-bundle/network-circuit configured in order to be fully functional. If an X.50 termination circuit's network circuit is not configured, then the X.50 channel card willremain out of service. The TMS Controller's status screen will report no error conditifor this channel.

• 14.4Kbps X.50 channel rates are not supported.

e Notes Page 31


Page 3

/E1 -s:

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.17 CDA Module Guidelines1. 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. Inversion can be corrected as follow

• 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 Communications 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.

2 Release Notes


Releas

und .

ws:

r the uted.

2 uits the

:

the

agg

d by ter

7. A 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

8. There are application limitations when DTEC bundles (network circuits) are routed/rerouted through the TMS-3000 backplane to another CDA card, as follo

• Maximum number of selects available to the CDA card is 256.

• Each network circuit consumes 3 backplane selects.

• Link Bundle Size is the number of DS0s. The higher the link bundle size, lowenumber of remaining selects and the fewer available circuits that can be rero

To Calculate: The number of remaining selects for a CDA card:

256 - (Link Bundle Size x 8) For example: 256 - (31 DS0s x 8) = 8

To Calculate: The number of circuits that can be rerouted through the backplane:

As shown in the example above, when the link bundle size is 31 DS0s, only network circuits can be rerouted through the backplane. If more network circneed to be rerouted, increase the number of remaining backplane selects onCDA card by carefully descreasing the link bundle size, as described below.

Recalculate: Decrease the link bundle size to yield more circuits, as shown below

11.18 OCM Guidelines1. 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.

256 - (Link Bundle Size x 8)3

For example: 256 - (31 DS0s x 8) =3

= 238

With 30 DS0s:

3With 29 DS0s:

With 28 DS0s:

256 - (30 x 8) = 16 remaining selects



16= 5 circuits=

324= 8 circuits=

332= 10 circuits=

e Notes Page 33


Page 3

ens s load

rt

s the

r

up

dule is at

LIM n

orted

not

uld

e rrect.

ancy

must

s will

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-of- service 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.

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. The following maintenance terminal features are not supported in this release: modem support and diagnostics.

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.

4 Release Notes


Releas

s ent til not

al

y

into MS

e to

to the

as

on

ult, that n and

s , and s

nd

is also

n,

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.

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 TMS 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 er

Documents

TMS Controller Version 5.1 - gdc.com · Microlite Backup Edge Data Archiving and Disaster Recovery Software Ver. 2.2 TMS Controller Software Product Ver 5.1.4 TMS-3000 Controller