Chapter 2. Getting Started. TimePlex LINK/2+, LINK/2+ miniLINK/2+, LINK/2+ microLINK/2+

Chapter

2

Getting Started

Information you need to start using the LINK/2+ System is contained in this chapter:

●

Power application and turn-off

●

Self-test and other start-up activities

●

Accessing the supervisory port

●

Supervisory port log in and log out

●

Loading Network Module/Interlink Module operational software

●

Loading Integrated Trunk Module operational software

●

Loading X.50 Server Module operational software

●

Loading VSM.3 and VSM.5 Voice Server Module operational software

●

Opening and closing Mainframe door

This chapter assumes the LINK/2+ System has already been properly configured and installed. If not, see the LINK/2+ Configuration Planning Manual and the Installation section of the LINK/2+

Installation and Maintenance Manual.

Day-to-day management of the LINK/2+ System can be performed via the integral supervisory port or the optional TIME/VIEW 2000 Network Management System. This manual discusses supervisory port operation only. For information on using TIME/VIEW, see the TIME/VIEW

2000 documentation.

Typical network management activities that the operator can perform from the supervisory terminal once the LINK/2+ System is powered up include:

●

Monitoring system status and alarm messages. See Chapter 5, Display Commands.

●

Connecting/disconnecting channels and performing other configuration activities. See

Chapter 6, Configuration Commands.

●

Performing diagnostic tests. See Chapter 7, Diagnostic Commands.

POWER APPLICATION AND TURN-OFF

Procedure 2-1 defines the power turn-on sequence for each LINK/2+ System. Procedure 2-2 defines the power turn-off sequence.

L2UG

6/30/97

2-1

Procedure 2-1. Power Turn-On

1.

Ensure that all channel devices and external line drivers are turned on and operational.

2.

If local supervisory terminal is to be used, ensure that terminal is turned on and operational.

3.

For 18-slot Mainframes, remove power supply grille.

For 13-slot (miniLINK/2+) Mainframes, open Mainframe door.

4.

For 18-slot and 13-slot Mainframes, set POWER switch on Power Supply Module(s) to 1 and observe that:

●

●

●

POWER ON (green) indicator is lit.

ON LINE (green) indicator is lit on in-control Power Supply Module.

LOAD SHARE (yellow) indicator is lit on in-control Power Supply Module

(redundancy) or is off if only a single Power Supply Module (no redundancy) is installed.

Go to step 6.

5.

For 6-slot (microLINK/2+) Mainframes:

A.

Ensure power cord from Power Supply Module is connected to rear of Fan Tray

Module.

B.

Apply power by connecting power cord from Fan Tray Module to AC power source.

C.

Ensure that both fans in Fan Tray Module are rotating.

PRECAUTION: If one or both of the fans fail to operate, unplug the power cord from rear of chassis immediately. See Fan

Tray Module replacement procedure in the LINK/2+

Installation and Maintenance Manual.

6.

The LINK/2+ System performs a self-test. (See "Self-Test" paragraph.) If the self-test is successful, the LINK/2+ System is ready for operation. If an error occurs, see the

Troubleshooting chapter in the LINK/2+ Installation and Maintenance Manual.

7.

If Line Termination System (LTS) Chassis and Line Termination Modules are installed, connect -48 VDC power source at rear of chassis.

8.

For 18-slot Mainframes, reinstall power supply grille.

For 13-slot Mainframes, close Mainframe door.

Procedure 2-2. Power Turn-Off

1.

Notify all concerned parties that the LINK/2+ System is being shut down.

2-2

L2UG

6/30/94

2.

If LTS Chassis and Line Termination Modules are installed, disconnect -48 VDC power source at rear of chassis.

3.

For 18-slot Mainframes, remove power supply grille.

For 13-slot (miniLINK/2+) Mainframes, open Mainframe door.

4.

For 18-slot and 13-slot Mainframes, set POWER switch on Power Supply Module(s) to 0.

For 6-slot (microLINK/2+) Mainframes, disconnect power cord from AC power source.

All indicators go off.

SELF-TEST AND OTHER START-UP ACTIVITIES

The following paragraphs discuss activities that occur after system start-up and during system operation:

●

Self-test

●

Bit error rate (BER) test

●

Channel connections

●

Alarm indicators and messages

Self-Test

When power is applied to the LINK/2+ System, the Network Module ON LINE indicator lights and the system automatically resets and runs a self-test diagnostic procedure The self-test routine checks the hardware and firmware of the following modules:

●

Network Module

●

Interlink Module

●

Integrated Trunk Module

●

X.50 Server Module

●

Voice Processor

●

D-Channel Module

●

Channelized Services Processor

●

Enhanced Voice Module

●

Voice Server Module

●

Dual Isochronous Module

L2UG

6/30/94

2-3

2-4

●

Isochronous Communication Module

●

Foreign Exchange Office Module

●

Foreign Exchange Station Module

●

Quad Asynchronous Module

The supervisory terminal lists each test as it is performed on the Network Module in the following order:

NCL BOOT STARTUP TESTS

RAM - OK

PROM - OK

NCL STARTUP TESTS

UART - OK

ECP - OK

DATABASE - OK D2

RTC - OK

PLL - OK

NOTES:

The "68020 - ERROR" message is displayed only if one of the 68020

CPU diagnostic tests fail.

The "DIP SWITCH 8 OFF" message is displayed only if DIP Switch

K1-8 on the Network Module is incorrectly set to the OFF/OPEN position.

The "ERROR BATTERY" message is displayed only if one, or both, batteries on the Network Module are defective or low in voltage.

●

If the Network Module self-test is satisfactory and passwords have been previously defined:

Module comes online.

Message, LINK/2 (or microLINK/2) Supervisory Port On-Line, appears on the supervisory terminal.

Password prompt (ENTER PASSWORD:) appears. See "Supervisory Port Log In" paragraph.

After password is entered correctly:

Time and date appear on the supervisory terminal.

Prompt (Nxxxx>) appears. (xxxx is the local node number.)

●

If the Network Module self-test is satisfactory and passwords have not been previously defined:

Module comes online.

L2UG

6/30/97

Message, LINK/2 (or microLINK/2) Supervisory Port On-Line, and time and date appear on the supervisory terminal.

Prompt (Nxxxx>) appears.

●

If the Network Module self-test is NOT satisfactory and a redundant Network Module is installed, the LINK/2+ System switches to the redundant Network Module. The supervisory terminal lists the self-test messages for this Network Module.

●

If any error messages appear or alarm indicators light, see the Troubleshooting chapter in the

LINK/2+ Installation and Maintenance Manual.

Self-tests of the Interlink, Integrated Trunk, D-Channel, Voice Processor, Channelized Services

Processor, Dual Isochronous, Isochronous Communication, Enhanced Voice, Foreign Exchange

Office, Foreign Exchange Station, Quad Asynchronous, Voice Server, and X.50 Server Modules are run during the Network Module self-test, but no messages are displayed on the supervisory terminal for these modules.

●

If the self-tests of the Interlink, Integrated Trunk, D-Channel, Voice Processor, Channelized

Services Processor, Isochronous Communication, Enhanced Voice, Foreign Exchange Office,

Foreign Exchange Station, Voice Server, and X.50 Server Modules are satisfactory:

Module’s ON LINE indicator lights.

Module comes online.

●

If the self-tests of the Dual Isochronous and Quad Asynchronous Modules are satisfactory, the modules come online, but no indicators light.

●

If any error messages appear or alarm indicators light, see the Troubleshooting chapter in the

LINK/2+ Installation and Maintenance Manual.

Bit Error Rate (BER) Test

Upon start-up, each Interlink Module and proprietary bundle on an Integrated Trunk Module continuously performs a BER test to determine the quality of the transmission facility. The BER results are averaged over several half-minute periods (windows) and then categorized based on the values presented in Table 2-1. BER status can be displayed with the DSP ST DL command; see Chapter 5, Display Commands. BER is not calculated on a simplex transmit only intermachine link.

The BER affects connections in the following manner:

●

Connections are disallowed if the BER fails to exceed POOR at least once following powerup or reset.

●

If an ABM profile is used, channels can be automatically connected or rerouted only over intermachine links meeting the user-specified link error performance level.

L2UG

6/30/94

2-5

BER Level

Table 2-1. BER Levels

Description

VERY GOOD

GOOD

FAIR

POOR

Better than 1 x 10-5

Between 1 x 10-5 and 1 x 10-4

Between 1 x 10-4 and 1 x 10-3

Worse than 1 x 10-3

Channel Connections

The LINK/2+ System automatically connects noncontention channels after start-up. For I/O channels designated as contention channels, the LINK/2+ System allocates bandwidth dynamically, at the request of the user (via I/O module control signals). A bandwidth contention channel will be automatically connected if the following conditions exist:

●

The request function (I/O module control signal) for that channel is activated.

●

Sufficient bandwidth is available.

Channel connect messages for noncontention channels are displayed on the supervisory terminal; see "Alarm Indicators and Messages" paragraph.

When the network is configured, individual channels or groups of channels can be designated as noncontention channels or as bandwidth contention channels, according to the application. For example, the noncontention channels may use all of the bandwidth during daytime operations.

The contention channels can come online when bandwidth becomes available due to some noncontention channels being programmed to be disconnected at a specific time in the evening.

For information on configuring channels as contention or noncontention, see the LINK/2+

Configuration Planning Manual.

When used with the Integrated Trunk Module, the D-Channel Module can provide dial-up connections between nodes, as well as bandwidth expansion and backup or redundancy of existing intermachine links.

For commands used to connect and disconnect channels, see Chapter 6, Configuration

Commands.

Alarm Indicators and Messages

To inform the user of a problem or status:

●

Module alarm indicators light.

2-6

L2UG

6/30/94

●

Unsolicited alarm messages are displayed on the supervisory terminal when system errors occur, when define (DEF) or SET commands are issued, and at a fixed time interval until the alarm is cleared. Other alarm conditions must be solicited by entering the DSP AQ command.

●

Unsolicited channel connected and not connected messages are also displayed on the supervisory terminal.

NOTE:

The supervisory terminal will NOT display unsolicited messages if the SET MUM LOC command has been entered. To resume the display of unsolicited messages, enter the CLR MUM LOC command.

See Chapter 4, Support Commands.

The supervisory terminal will NOT display continuous occurrences of alarm 07 (intermachine link declared out-of-service) if the DEF DL parameter alarm 7 masking (AL7MASK) is set to ON. See

Intermachine Link Parameters chapter in the LINK/2+ Configuration

Planning Manual.

Alarm 04 (power supply failure) does not occur in the microLINK/2+

System, and alarm 08 (fan failure) does not indicate a fan failure in the microLINK/2+ System. The Fan Fail Alarm Defeat Plug (FFD) must be installed to avoid continuous display of alarm 08. If the

Power Supply Module fails or the fans stop rotating, see the

LINK/2+ Installation and Maintenance Manual for replacement procedure.

If an alarm condition occurs, see the Troubleshooting chapter in the LINK/2+ Installation and

Maintenance Manual. For a summary of error and status messages, see Appendix A.

ACCESSING THE SUPERVISORY PORT

If a local supervisory terminal is to be used, the LINK/2+ System must be programmed by

Network Module DIP switch to use default supervisory port parameter values or parameter values stored in the database:

●

If Network Module DIP switch is set to use default supervisory port parameter values, the parameter values take effect when power is applied to the LINK/2+ System. Default supervisory port parameter values are:

speed: 9600 bps

stop bits: 1

data bits/parity: 8 data bits, no parity

●

If Network Module DIP switch is set to use parameters from the database, supervisory port parameter values must be defined from a supervisory port or a supervisory computer port.

See "Define Supervisory Port Parameters (DEF SP) Command" paragraph in Chapter 6,

Configuration Commands.

L2UG

6/30/94

2-7

The supervisory port is online when the LINK/2+ System is turned on. To access the supervisory port:

●

Ensure that:

Supervisory terminal is connected to LINK/2+ System.

Supervisory port parameter values have been defined.

Supervisory terminal is turned on and operational.

●

If passwords have been defined, log in per "Supervisory Port Log In" paragraph.

●

Prompt (Nxxxx>) must be displayed before commands can be entered. If prompt is not displayed, enter Control C character or BREAK.

To prevent unauthorized supervisory port access, log out per "Supervisory Port Log Out" paragraph when you are finished at the supervisory terminal.

Supervisory Port Log In

If passwords have been defined, the password prompt (ENTER PASSWORD:) appears on the supervisory terminal whenever power is applied or a reset occurs to the LINK/2+ System. To log in to the LINK/2+ System, carefully key in the correct password, then press RETURN key.

If the password is entered correctly:

●

Time and date appear on the supervisory terminal.

●

Prompt (Nxxxx>) appears.

NOTE:

If the password is not entered correctly, the password prompt

(ENTER PASSWORD:) appears again on the supervisory terminal.

If the password is entered incorrectly three times, the LINK/2+

System will wait 30 seconds before allowing further password attempts. See your system manager for correct password.

If necessary, passwords can be disabled. See the Network Module chapter in the LINK/2+ Installation and Maintenance Manual.

The password used to log in determines the commands that you are allowed to use. See "System

Security Features" paragraphs.

Supervisory Port Log Out

To prevent unauthorized system access, you can log out of the LINK/2+ System in two ways:

●

By entering the EX command. At the prompt (Nxxxx>), type EX to log out. If prompt is not displayed, enter Control C character or BREAK.

2-8

L2UG

6/30/94

●

By a time out. If the log in time out parameter is enabled, you will be logged out if no keystroke is entered for 30 minutes.

After logging out of the LINK/2+ System:

●

Message "Logged Out" appears on the supervisory terminal.

●

Time and date appear.

●

Password prompt "ENTER PASSWORD:" appears.

NETWORK MODULE/INTERLINK MODULE OPERATIONAL SOFTWARE

The LINK/2+ System is shipped with the Network Module/Interlink Module operational software already installed in the Network Module(s). Two copies of the software reside on each

Network Module; a copy in each of two flash memory banks. In addition, a high density, 3.5inch floppy disk containing the operational software is also provided.

NOTE:

The Interlink Module software is resident on the Network Module and is automatically loaded to the Interlink Modules by the Network

Module. No separate action by the user is required.

If a new version of the software is released, perform the following procedure to load the operational software, provided on the floppy disk, from a microcomputer to the Network

Module.

Procedure 2-3. Loading Network Module/Interlink Module Operational

Software

1.

Determine the supervisory port parameters for use in configuring the microcomputer by entering the DSP SP command. Record these parameters:

•

SPEED: for example, 9600 bps

•

STOP: 1 stop bit (required setting)

•

DATA: 8 data bits, no parity (required setting)

If the STOP and DATA parameters do not match the required settings, enter the DEF SP command to change the supervisory port parameters to the required settings.

2.

Connect the serial port of the microcomputer to the supervisory port of the LINK/2+

System. The microcomputer should have the following:

•

High-density 3.5-inch floppy disk drive

•

Serial port

•

Communications application software containing XMODEM with CRC file transfer protocol (compatible with ProComm Plus 2.01)

L2UG

6/30/94

2-9

2-10

3.

Using the parameters recorded in step 1 for the supervisory port, configure the microcomputer communications application software for the same parameters.

4.

Verify that the communications application is running correctly by entering a supervisory port command such as DSP TIM.

5.

Verify (on the disk label) that the version of the operational software is correct prior to loading and record the filename.

6.

Insert the operational software disk into the microcomputer.

7.

Replace the operational software in the offline bank of flash EPROM with the new operational software by entering:

LOA SW n:ss (or LOA SW n:ss/F)

NOTE:

If the terminal emulation program running on the microcomputer supports a speed of 57600 bps, you can use the optional /F modifier with the LOA SW command to download the operational software at a speed of 57600 bps to the Network Module.

You do not need to reconfigure the SP port speed to 57600 bps when using the /F modifier as the Network Module automatically switches the SP port to this speed. However, you do need to reconfigure the emulation program speed to 57600 bps.

The following message is displayed:

ERASING OFFLINE-FLASH

NOTE:

To abort the LOA SW command, enter CONTROL C. If the file transfer has been started, press ESC to abort the file transfer.

When erasing is complete, the following message is displayed:

CONNECT SP PORT TO PC AND INVOKE XMODEM PROTOCOL.

C’s appear on the screen until the file transfer is started.

8.

Set the file transfer protocol on the microcomputer to XMODEM to send the file from the microcomputer to the LINK/2+ System. Enter the path and filename recorded from the disk label.

If successful, the load process takes about 12 minutes (at 9600 bps). If not successful, repeat step 7.

PRECAUTION: The TGL BNK command is used to upgrade the system.

Issuing this command to an online Network Module will automatically reset the node.

9.

When ready to upgrade, enter:

TGL BNK n:ss

L2UG

6/30/94

The LINK/2+ System resets. The offline bank of flash EPROM becomes the online bank.

The Network Module is now using the new operational software and the new operational software is automatically loaded to all Interlink Modules in the node.

Observe that the start-up self-test is successful.

10. If the new operational software is to be loaded onto the other bank, enter:

COP SW n:ss where ss is the slot number of the online Network Module.

11. If a redundant pair of Network Modules exists and if the new operational software is to be loaded onto the offline Network Module, copy the new version of operational software from the online Network Module to the offline bank of the offline module by entering the following commands:

COP SW n:ss

1

n:ss

2 where n:ss

1 is the source module slot location and n:ss location.

2

is the destination module slot

TGL BNK n:ss where ss is the slot number of the offline Network Module.

The offline Network Module resets. The offline bank of flash EPROM becomes the online bank.

12. If the new operational software is to be loaded onto the second bank of the offline Network

Module, issue the following command to the online Network Module:

COP SW n:ss

1

n:ss

2 where n:ss

1 is the source module slot location and n:ss location.

2

is the destination module slot

INTEGRATED TRUNK MODULE OPERATIONAL SOFTWARE

The LINK/2+ System is shipped with the Integrated Trunk Module operational software already installed in the Integrated Trunk Module(s). In addition, a high density, 3.5-inch floppy disk containing the operational software is also provided.

If a new version of the software is released, perform the following procedure to load the operational software, provided on the floppy disk, from a microcomputer to the Integrated Trunk

Module.

L2UG

6/30/94

2-11

Procedure 2-4. Loading Integrated Trunk Module Operational Software

1.

Determine the supervisory port parameters for use in configuring the microcomputer by entering the DSP SP command. Record these parameters:

•

SPEED: for example, 9600 bps

•

STOP: 1 stop bit (required setting)

•

DATA: 8 data bits, no parity (required setting)

If the STOP and DATA parameters do not match the required settings, enter the DEF SP command to change the supervisory port parameters to the required settings.

2.

Connect the serial port of the microcomputer to the supervisory port of the LINK/2+

System. The microcomputer should have the following:

•

High-density 3.5-inch floppy disk drive

•

Serial port

•

Communications application software containing XMODEM with CRC file transfer protocol (compatible with ProComm Plus 2.01)

3.

Using the parameters recorded in step 1 for the supervisory port, configure the microcomputer communications application software for the same parameters.

4.

Verify that the communications application is running correctly by entering a supervisory port command such as DSP TIM.

5.

Verify (on the disk label) that the version of the operational software is correct prior to loading and record the filename.

6.

Insert the operational software disk into the microcomputer.

PRECAUTION: Before logically removing the online Integrated Trunk

Module, notify all users that all channels are being taken offline or data will be lost.

7.

Logically remove the online Integrated Trunk Module using the RMV n:ss command.

8.

Replace the operational software in the flash EPROM with the new operational software by entering:

LOA SW n:ss (or LOA SW n:ss/F)

NOTE:

If the terminal emulation program running on the microcomputer supports a speed of 57600 bps, you can use the optional /F modifier with the LOA SW command to download the operational software at a speed of 57600 bps to the Integrated Trunk Module.

2-12

L2UG

6/30/94

L2UG

6/30/94

You do not need to reconfigure the SP port speed to 57600 bps when using the /F modifier as the Network Module automatically switches the SP port to this speed. However, you do need to reconfigure the emulation program speed to 57600 bps.

The following message is displayed:

CONNECT SP PORT TO PC AND INVOKE XMODEM PROTOCOL.

NOTE:

To abort the LOA SW command, enter CONTROL C. If the file transfer has been started, press ESC to abort the file transfer.

C’s appear on the screen until the file transfer is started.

9.

Set the file transfer protocol on the microcomputer to XMODEM to send the file from the microcomputer to the LINK/2+ System. Enter the path and filename recorded from the disk label.

If successful, the load process takes about 5 minutes (at 9600 bps). The following message is displayed:

LOAD COMPLETE. INSERT AND WAIT FOR 90 SECONDS TO PROGRAM FLASH.

NOTE:

Immediately after the operational software has been loaded, the lights on the Integrated Trunk Module will cycle on and off a few times while the flash is being programmed. After the lights remain off, proceed to the next step.

10. Logically insert the Integrated Trunk Module using the INS n:ss command. The ON LINE indicator should light indicating that this Integrated Trunk Module is now online.

If the ON LINE indicator does not light, use the DSP PPN n:ss command to verify that the new RP part number is displayed. If the correct part number is displayed, use the RST n:ss command to reset the Integrated Trunk Module.

11. If a redundant pair of Integrated Trunk Modules exists and if the new operational software is to be loaded onto the offline Integrated Trunk Module, proceed as follows:

A.

Logically remove the offline Integrated Trunk Module using the RMV n:ss command.

B.

Copy the new version of operational software from the online Integrated Trunk Module to the offline module by entering the following command:

COP SW n:ss

1

n:ss

2 where n:ss

1 location.

is the source module slot location and n:ss

2

is the destination module slot

Depending on the slot numbers, the following message is displayed:

COPYING SW FROM SLOT 1:05 TO SLOT 1:06.

2-13

If successful, the copy process takes about 30 seconds. The following message is displayed:

LOAD COMPLETE. INSERT AND WAIT FOR 90 SECONDS TO PROGRAM

FLASH.

NOTE:

Immediately after the operational software has been loaded, the lights on the Integrated Trunk Module will cycle on and off a few times while the flash is being programmed. After the lights remain off, proceed to the next step.

C.

Logically insert the offline Integrated Trunk Module using the INS n:ss command.

Use the DSP PPN n:ss command to verify that the new RP part number is displayed.

12. To copy the operational software to another Integrated Trunk Module in the Control

Mainframe, repeat step 11A through 11C. Note that the source module must always be online and the destination module must first be logically removed.

X.50 SERVER MODULE OPERATIONAL SOFTWARE

The LINK/2+ System is shipped with the X.50 Server Module operational software already installed in the X.50 Server Module(s). In addition, a high density, 3.5-inch floppy disk containing the operational software is also provided.

If a new version of the software is released, perform the following procedure to load the operational software, provided on the floppy disk, from a microcomputer to the X.50 Server

Module.

Procedure 2-5. Loading X.50 Server Module Operational Software

NOTE:

If an existing X.50 Server Module in the node already contains the current software, you can copy the current software to another X.50

Server Module using the COP SW command. See Procedure 2-6.

1.

Determine the supervisory port parameters for use in configuring the microcomputer by entering the DSP SP command. Record these parameters:

•

SPEED: for example, 9600 bps

•

STOP: 1 stop bit (required setting)

•

DATA: 8 data bits, no parity (required setting)

If the STOP and DATA parameters do not match the required settings, enter the DEF SP command to change the supervisory port parameters to the required settings.

2.

Connect the serial port of the microcomputer to the supervisory port of the LINK/2+

System. The microcomputer should have the following:

•

High-density 3.5-inch floppy disk drive

2-14

L2UG

6/30/94

L2UG

6/30/94

•

Serial port

•

Communications application software containing XMODEM with CRC file transfer protocol (compatible with ProComm Plus 2.01)

3.

Using the parameters recorded in step 1 for the supervisory port, configure the microcomputer communications application software for the same parameters.

4.

Verify that the communications application is running correctly by entering a supervisory port command such as DSP TIM.

5.

Verify (on the disk label) that the version of the operational software is correct prior to loading and record the filename.

6.

Insert the operational software disk into the microcomputer.

PRECAUTION: Before logically removing an online X.50 Server Module, notify all users that all channels are being taken offline or data will be lost.

7.

Logically remove the X.50 Server Module using the RMV n:ss command.

8.

Replace the operational software in the flash EPROM with the new operational software by entering:

LOA SW n:ss (or LOA SW n:ss/F)

NOTE:

If the terminal emulation program running on the microcomputer supports a speed of 57600 bps, you can use the optional /F modifier with the LOA SW command to download the operational software at a speed of 57600 bps to the X.50 Server Module.

You do not need to reconfigure the SP port speed to 57600 bps when using the /F modifier because the Network Module automatically switches the SP port to this speed. However, you do need to reconfigure the emulation program speed to 57600 bps.

The following message is displayed:

CONNECT SP PORT TO PC AND INVOKE XMODEM PROTOCOL.

NOTE:

To abort the LOA SW command, enter CONTROL C. If the file transfer has been started, press ESC to abort the file transfer.

C’s appear on the screen until the file transfer is started.

9.

Set the file transfer protocol on the microcomputer to XMODEM to send the file from the microcomputer to the LINK/2+ System. Enter the path and filename recorded from the disk label.

If successful, the load process takes about 5 minutes (at 9600 bps). The following message is displayed:

LOAD COMPLETE. INSERT AND WAIT FOR 90 SECONDS TO PROGRAM FLASH.

2-15

10. Logically insert the X.50 Server Module using the INS n:ss command. If the X.50 Server

Module was originally online, the ON LINE indicator should light indicating that this X.50

Server Module is once again online.

If the ON LINE indicator does not light, use the DSP PPN n:ss command to verify that the new RP part number is displayed. If the correct part number is displayed, use the RST n:ss command to reset the X.50 Server Module.

Procedure 2-6. Copying X.50 Server Module Operational Software

To copy the current operational software from one X.50 Server Module (source) to another X.50

Server Module (destination) in the node, proceed as follows:

PRECAUTION: Before logically removing an online X.50 Server Module, notify all users that all channels are being taken offline or data will be lost.

1.

Logically remove the destination X.50 Server Module using the RMV n:ss command.

2.

Copy the new version of operational software from the source X.50 Server Module to the destination X.50 Server module by entering the following command:

COP SW n:ss

1

n:ss

2 where n:ss

1 location.

is the source module slot location and n:ss

2

is the destination module slot

Depending on the slot numbers, the following message is displayed:

COPYING SW FROM SLOT 1:08 TO SLOT 2:06.

If successful, the copy process takes about 30 seconds. The following message is displayed:

LOAD COMPLETE. INSERT AND WAIT FOR 90 SECONDS TO PROGRAM FLASH.

3.

Logically insert the destination X.50 Server Module using the INS n:ss command.

Use the DSP PPN n:ss command to verify that the new RP part number is displayed.

VSM.3/VSM.5 VOICE SERVER MODULE OPERATIONAL SOFTWARE

The LINK/2+ System is shipped with the VSM.3 and VSM.5 Voice Server Module operational software already installed in the VSM.3 and VSM.5 Voice Server Modules. In addition, a highdensity, 3.5-inch floppy disk containing the operational software is also provided.

If a new version of the software is released, perform the following procedure to load the operational software, provided on the floppy disk, from a microcomputer to the VSM.3 or

VSM.5 Voice Server Module.

2-16

L2UG

6/30/97

Procedure 2-7. Loading VSM.3 or VSM.5 Voice Server Module

Operational Software

NOTE:

If an existingVSM.3 or VSM.5 Voice Server Module in the node already contains the current software, you can copy the current software to another VSM.3 or VSM.5Voice Server Module respectively, using the COP SW command. See Procedure 2-8.

1.

Determine the supervisory port parameters for use in configuring the microcomputer by entering the DSP SP command. Record these parameters:

•

SPEED: for example, 9600 bps

•

STOP: 1 stop bit (required setting)

•

DATA: 8 data bits, no parity (required settings)

If the STOP and DATA parameters do not match the required settings, enter the DEF SP command to change the supervisory port parameters to the required settings.

2.

Connect the serial port of the microcomputer to the supervisory port of the LINK/2+

System. The microcomputer should have the following:

•

High-density, 3.5-inch floppy disk drive

•

Serial port

•

Communications application software containing XMODEM with CRC file transfer protocol (compatible with ProComm Plus 2.01)

3.

Using the parameters recorded in step 1 for the supervisory port, configure the microcomputer communications application software for the same parameters.

4.

Verify that the communications application is running correctly by entering a supervisory port command such as DSP TIM.

5.

Verify (on the disk label) that the version of the operational software is correct prior to loading and record the filename.

6.

Insert the operational software disk into the microcomputer.

PRECAUTION: Before logically removing an online VSM.3 or VSM.5

Voice Server Module, notify all users that all channels are being taken offline or voice/fax traffic will be lost.

7.

Logically remove the VSM.3 or VMS.5 Voice Server Module using the RMV n:ss command.

8.

Replace the current operational software in the VSM.3 or VSM.5 Voice Server Module with the new operational software by entering:

LOA SW n:ss (or LOA SW n:ss/F)

L2UG

6/30/97

2-17

NOTE:

If the terminal emulation program running on the microcomputer supports a speed of 57600 bps, you can use the optional /F modifier with the LOA SW command to download the operational software at a speed of 57600 bps to the VSM.3 or VSM.5 Voice Server Module.

You do not need to reconfigure the SP port speed to 57600 bps when using the /F modifier because the Network Module automatically switches the SP port to this speed. However, you do need to reconfigure the emulation program speed to 57600 bps.

The following message is displayed:

CONNECT SP PORT TO PC AND INVOKE XMODEM PROTOCOL.

NOTE:

To abort the LOA SW command, enter CONTROL C. If the file transfer has been started, press ESC to abort the file transfer.

C’s appear on the screen until the file transfer is started.

9.

Set the file transfer protocol on the microcomputer to XMODEM to send the file from the microcomputer to the LINK/2+ System. Enter the path and file name recorded from the disk label.

If successful, the load process takes about 5 minutes (at 9600 bps). The following message is displayed:

LOAD COMPLETE. MODULE READY TO GO ONLINE.

10. Logically insert the VSM.3 or VSM.5 Voice Server Module using the INS n:ss command. If the VSM.3 or VSM.5 Voice Server Module was originally online, the ON LINE indicator should light indicating that this Voice Server Module is once again online.

After the module comes back online, use the DSP PPN n:ss command to verify that the new software number is displayed.

Procedure 2-8. Copying VSM.3 or VSM.5 Voice Server Module

Operational Software

To copy the current operational software from one VSM.3 Voice Server Module (source) to another VSM.3 Voice Server Module (destination) or from one VSM.5 Voice Server Module

(source) to another VSM.5 Voice Server Module (destination) in the node, proceed as follows:

PRECAUTION: Before logically removing an online VSM.3 or VSM.5

Voice Server Module, notify all users that all channels are being taken offline or voice/fax traffic will be lost.

1.

Logically remove the source VSM.3 or VSM.5 Voice Server Module using the RMV n:ss command.

2.

Logically remove the destination VSM.3 or VSM.5 Voice Server Module using the RMV n:ss command.

2-18

L2UG

6/30/97

3.

Copy the new version of operational software from the source VSM.3 Voice Server Module to the destination VSM.3 Voice Server Module or from the source VSM.5 Voice Server

Module to the destination VSM.5 Voice Server Module by entering the following command:

COP SW n:ss

1

n:ss

2 where n:ss

1 location.

is the source module slot location and n:ss

2

is the destination module slot

Depending on the slot numbers, the following message is displayed:

COPYING SW FROM SLOT 1:08 TO SLOT 2:06.

If successful, the copy process takes about 50 seconds. The following message is displayed:

LOAD COMPLETE. MODULE READY TO GO ONLINE.

4.

Logically insert the source VSM.3 or VSM.5 Voice Server Module using the INS n:ss command.

5.

Logically insert the destination VSM.3 or VSM.5 Voice Server Module using the INS n:ss command.

Use the DSP PPN n:ss command to verify that the new RP part number is displayed.

SYSTEM CONFIGURATION

For information on configuring the LINK/2+ System, see the Configuration Planning Manual.

After the system has been configured, refer to the following paragraphs for information on backing up the configured database.

DATABASE BACKUP

After system configuration has been completed, perform Procedure 2-9 to back up the database via file transfer to a microcomputer hard disk drive or floppy disk. Periodically perform database backups after changes have been made to the system configuration.

Procedure 2-9. Database Backup

1.

Determine the supervisory port parameters for use in configuring the microcomputer to match the supervisory port by entering the DSP SP command. Record these parameters:

•

SPEED: for example, 9600 bps

•

STOP: for example, 1 stop bit (required setting)

•

DATA: for example, 8 data bits, no parity (required setting)

L2UG

6/30/97

2-19

2-20

If the STOP and DATA parameters do not match the required settings, enter the DEF SP command to change the supervisory port parameters to the required settings.

2.

Connect the serial port of the microcomputer to the supervisory port of the LINK/2+

System. The microcomputer should have the following:

•

High-density 5.25-inch floppy disk drive, high-density 3.5-inch floppy disk drive, or hard disk drive

•

Serial port

•

Communications application software containing XMODEM with CRC file transfer protocol (compatible with ProComm Plus 2.01)

•

CHECKDB.EXE program (provided with LINK/2+ operational software floppy disk package)

3.

Using the parameters recorded in step 1 for the supervisory port, configure the microcomputer communications application software for the same parameters.

4.

Verify that the communications application is running correctly by entering a supervisory port command such as DSP TIM.

5.

Issue the DSP CKS command and record the displayed checksum and the time and date of the last database change for future reference. (The purpose of this step is for comparison of the stored database with the contents of the Network Module database.)

6.

If the database is to be backed up to a floppy disk, insert the disk.

7.

Back up the database from the Network Module to the microcomputer by entering:

SAV DB

The following message is displayed:

CONNECT SP PORT TO PC AND INVOKE XMODEM PROTOCOL

NOTE:

To abort the SAV DB command, enter CONTROL C. If the file transfer has been started, press ESC to abort the file transfer.

8.

Set the file transfer protocol on the microcomputer to XMODEM for the microcomputer to receive the file from the Network Module. Enter an appropriate filename to distinguish the version of the database being backed up.

9.

At the DOS prompt, verify that the database backup was successful by entering:

CHECKDB filename

This program will provide the following information, Figure 2-1:

•

Database filename selected by the user

•

Node ID

•

Database checksum and validated checksum

L2UG

6/30/97

•

Timestamp with time the last database change was made

•

Datestamp with date the last database change was made

ascomTimeplex LINK/2 NCL Database Verification Program RP50001A

Filename Node Checksum Validated Timestamp Datestamp

N4_12-21.8AM 0004 57 57 07:54:42 12/21/93

N4_12-31.8AM 0004 75 75 15:16:42 12/30/93

Figure 2-1. Typical Database Verification Program Results

OPENING AND CLOSING MAINFRAME DOOR

WARNING: KEEP MAINFRAME DOOR LOCKED DURING NORMAL

OPERATION. VOLTAGES WITHIN THE MAINFRAME

COULD PRESENT A SHOCK HAZARD.

The 18-slot and 13-slot (miniLINK/2+) Mainframe front doors have a handle located on the left side for opening and closing the door.

To open the 6-slot (microLINK/2+) Mainframe front door, unlock the key at the bottom of the door and pull door slightly forward at the base. Lift door off frame.

To close the microLINK/2+ Mainframe front door, position the door on the top of the frame, then push the bottom of the door toward the back of the unit until the door snaps into place. Lock the door.

L2UG

6/30/97

2-21