Procedure 6.7: LOAD SOFTWARE UPDATE(s) FROM SCANS/OR TAPE
OVERVIEW
There is a 24-hour time limit imposed from the time the switch is primed until SCANS must begin the data session. If
SCANS puts the binary overwrite (BOW) request in the queue, it may take up to that 24-hour limit to start sending
data to the switch.
IN REMOTE STARTED
is output to indicate the start of the data session. The
IN REMOTE
REPT
message may be output periodically during the session to indicate various file rejects. Termination of the
session is indicated by an
IN REMOTE REPT
output message followed immediately by the
IN REMOTE STOPPED
output message.
PROCEDURE
1.
If loading software update(s) from
SCANS
, continue to Step 2.
If loading software update(s) from
TAPE
, go to Step 16.
2.
At master control center (MCC), type and enter:
IN:REMOTE,START;
Response:
IN REMOTE INITIALIZED
TRANSACTION ID: a
TIME: b
Where:
a
= 7-digit transaction ID to be supplied to SCANS when issuing binary overwrite command.
b
= Time at which 24-hour timer began in the format hours
:
minutes.
3.
At SCANS terminal, access SCANS per local instructions.
4.
At SCANS terminal, type and enter:
BOW, S 5E, R a[:b], O c, PW d
Where:
a
= first or only software update in range.
b
= last software update in range (if ordering more than one software update).
c
= office name.
d
= transaction ID. (obtained in Step 2.)
5.
At MCC, type and enter:
IN:REMOTE,REPT;
Comment:
In response to the
IN:REMOTE,REPT
input, the
IN REMOTE REPT
output indicates the
data session is still in progress while the
IN REMOTE ERROR 12
indicates no IN REMOTE
processes are active at this time (that is, data session is over - successfully or
unsuccessfully or we could already have).
6.
Is response
IN REMOTE WAITING
or
IN REMOTE ERROR 12
?
If
IN REMOTE WAITING
, continue to Step 7.
If
IN REMOTE ERROR
, go to Step 8.
7.
Wait approximately 1 hour.
8.
For a listing of BWMs not in switch, At the MCC, type and enter:
OP:STATUS:LISTDIR,FN="/etc/bwm";
.
Response:
OP STATUS LISTDIR COMPLETED
235-105-210
October 1999
Copyright © 1999
Page 1
Summary of Contents for 5ESS-2000
Page 96: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 184: ...235 105 210 October 1999 Copyright 1999 Page 3 ...
Page 300: ...13 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 55 ...
Page 339: ...7 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 342: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 359: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 609: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 12 ...
Page 676: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 792: ...3 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 799: ...Figure 11 36 3 1 Cleaning Points 235 105 210 October 1999 Copyright 1999 Page 7 ...
Page 801: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 839: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 16 ...
Page 999: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 1008: ...Figure 11 55 1 CTSNS DIP Switch Settings 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1011: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1053: ...235 105 210 October 1999 Copyright 1999 Page 15 ...
Page 1289: ...Figure 15 17 2 AMATPS Data Link 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1292: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1303: ...9 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1360: ...Figure 15 47 2 Typical SCANS III Link Diagram 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1372: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1374: ...235 105 210 October 1999 Copyright 1999 Page 4 ...
Page 1421: ...Table 1 1 O M Checklist 235 105 210 October 1999 Copyright 1999 Page 3 ...