Anda di halaman 1dari 224

HUGHES

.
NETWORK SYSTEMS LTD
A Hughes Electronics Company

Inmarsat-C Land Earth Station Configuration Document Customer Release Configuration Guide For Telecomunicaciones De Mexico

Reference: A4-SCG-003076-1

Date: Issue: Status:

21-August-2002 V3.9 Accepted

Hughes Network Systems Limited Saxon Street Milton Keynes MK14 6LD United Kingdom

Telephone Facsimile

+44 1908 221122 +44 1908 221127

Copyright Hughes Network Systems Ltd 2002

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

The contents of this document are proprietary to HNS Limited and cannot be disclosed, duplicated, reproduced or used in part or in whole for any purpose other than in connection with the associated binding contract between HNS Limited and the recipient. This restriction does not apply to information in this document if it is obtainable from another source without breach of this notice.

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Revision History
Issue Status 1.0A 1.0B 1.0C 1.0D 1.0E 1.0F 1.0G 1.0H Pre QC Pre QC Pre QC Pre QC Pre QC Pre QC Pre QC Pre QC Date 11-Sep-91 24-Sep-91 30-Oct-91 14-Nov-91 26-Nov-91 10-Dec-91 18-Dec-91 1-Mar-92 Author P.R.Dodson P.R.Dodson P.R.Dodson P.R.Dodson P.R.Dodson P.R.Dodson D.R.Lovell I.M.West Comments & Change References

1.0I 1.0J 1.0K

Pre QC Pre QC Pre QC

1-May-92 1-Aug-92 20-Jul-93

I.M.West I.M.West I.M.West

1.0L 1.0M 1.0N 1.0 1.1 2.0A 2.0B 2.0C 2.0D 2.0D

Pre QC Pre QC Pre QC Accepted Accepted For Review For Review

29-Oct-93 04-Aug-94 10-Aug-94 10-Aug-94 07-Oct-94 05-Nov-94 29-Jun-95

M. M. M. M. M. M. P.

Gupta Gupta Gupta Gupta Gupta Hart Bisp

For Review 04-Jul-95 For Review 05-Jul-95 For Review 06-Jul-95

D. Toora P. Bisp D. Toora

Original Updated to include enhancements plus new SADREDEF.COM Expanded from installation to config guide Updated and included build guide General update Added Chapter 7 on database and Appendix SOC_BUILD on building the SOC Updated security concepts in Chapter on SECURITY Added sections for References, Glossary and About This Guide Added Chapter 5 Added Chapter 6 Included security list files for all customers in Chapter SECURITY Added section DB_PINS_VERSIONS Added Appendix ACCOUNTS Added Appendix LOGICALS Added Appendix SYMBOLS Added Appendix DISKS Added Appendix TIMES Corrections and update for R5.11M software level Corrections and update for R5.12 software level Corrections and update for R7.0 software level Removed appendices relating to activities of the Build Manager and the Software Engineering Team Major updates for 72000 release. Major updates for 73000 release. Update to database installation Review comments incorporated. Customer Review comments incorporated. Extra Fax notes included. Corrections and updates to fax notes arising from SCR372 and SCR382. Also removed Appendix PCFAX_SW. Adding in the new chapter - Database Administration duties as part of an LES Software Upgrade. Replacement of LESFax diagram. Removal of Appendix LESFAX_HW. Changed the section to dump the online database in chapter Actions to be taken prior to Software Installation to refer to section in the new chapter - Database Administration duties as part of an LES Software Upgrade. Also, update examples of online and offline database conversions.

Customer Release Configuration Guide Telecomunicaciones De Mexico

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

2.0E 2.0F

For Review 12-Jul-95 For Review 30-Oct-95

P. Lockyer

Updates following review Make document more generic A. Chisholm Updates following review, and incorporating SPRs 22483, 23793, 23795 A. Chisholm Updates from reviews, 7000 Release A. Chisholm SPRs 24159, 24508, 24654, 24656, 24660, 24672. A. Chisholm Released. A. Chisholm Second OR for Italy, inclusion of Omega Clock commissioning, SPR 24684. A. Chisholm Minor corrections A. Chisholm Released A. Chisholm Turn on all ORs for Telstra. SPR 25242 A. Chisholm Released A. Chisholm Introducing FAX for CAT SPR25342 A. Chisholm Released A. Chisholm Updates from reviews, 8000 Release A. Chisholm SCR 426, SPRs 24612, 24856. A. Chisholm Released. A. Chisholm Merge with V2.3, SCR491, general updates. A. Chisholm Released.

2.0 2.1A

Accepted For Review

14-Nov-95 8-Feb-96

2.1 2.2A

Accepted

25-Mar-96

For Review 10-Jun-96

2.2B 2.2 2.3A 2.3 2.4A 2.4 3.0 3.1A 3.1 3.2A 3.2 3.3A

Follow Up Accepted

27-Jun-96 2-Jul-96

For Review 20-Aug-96 Accepted 4-Sep-96

For Review 21-Jan-97 Accepted Accepted For Review 28-Jan-97 14-Nov-95 8-Feb-96

Accepted 25-Mar-96 For Review 7-Oct-96 Accepted For Review 3-Dec-96

17-Mar-97 A. Chisholm Merge with V2.4 Greek second ocean region. SCR531, SPR22543 7-Apr-97 1-May-97 21-May-97 1-Jul-97 31-Jul-97 A. Chisholm Final Corrections. A. Chisholm IMR1, SCRs 541,485 SPR25579 A. Chisholm Final Corrections. A. Chisholm AMR4, SCR 558, updates to Async. A. Chisholm Final Corrections.

3.3 3.4A 3.4 3.5A 3.5

Accepted For Review Accepted For Review Accepted

3.6A For Review 21-Oct-97 M.J.Williams. First issue to Telstra for 80000. 3.6 Accepted 11-Jun-98 M.J.Williams. Only changes in this version are to enable existing (accepted) updates

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

for Telstra, so put to Accepted and issue. 3.7A For Review 10-Apr-01 M.J.Williams. SPR26349 - installation details in line with current PROJECTINSTALL and improve order of instructions. Updates confined to BAP and FEP.

3.7b For Review 12-Apr-01 M.J.Williams. Re-organisation and rationalisation of sections in chapter 4 following latest additions. Index added covering these changes. 3.7c For Review 18-Apr-01 M.J.Williams. SOC installation details amended. 3.7d For Review 23-Apr-01 M.J.Williams. Post informal review modifications 3.7 Accepted 26-Apr-01 M.J.Williams. Post forma review, with clarification to fallback instructions.

3.8a For Review 06-Aug-01 M.J.Williams. SPR26352/55/64/65 Automation and improvements to installation defaults SPR26379, note to protect CRM_Memory file added to section 2.2 and 4.1.3.1 SPR26367, Instructions for Xantic remote FEP installation. 3.8b For Review 26-Sep-01 M.J.Williams. SPR26388 - Check removed for MCM$EXE:Que_INIT_Data.Dat 3.8c For Review 11-Dec-01 M.J.Williams. Updates to installation procedures following release of 80140 3.8 Accepted 12-Dec-01 M.J.Williams. 3.9a For Review 09-May-02 M.J.Williams. SPR26426 Updates to EBF instalation procedure (automated) 3.9 Accepted 19-Feb-03 M.J.Williams No comments

Change bars indicate modifications since V3.6 of this document

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Reporting Issues with this Document


Any errors or omissions found in this document should be reported to HNS by means of a Customer Service Problem Report (CSPR). This method may also be used to raise any suggestions for future releases. The procedure for raising an CSPR is explained in Appendix F of the System Operator Console Operator Guide reference [1].

Customer Release Configuration Guide Telecomunicaciones De Mexico

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

ii

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Table of Contents
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting Issues with this Document . . . . . . . . . . . . . . . . . . . . i

Referenced and Related Documents . . . . . . . . . . . . . . . . . . . . . Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1-1 1-1 1-2 1-2 2-1 2-1 2-2 2-2 2-3 2-3 2-4 3-1 3-1 3-1 3-2 3-2 3-3 3-4 3-7 3-8 3-8 3-10 4-1 4-3 4-3 4-6 4-8 4-9 4-19 4-22 4-23 4-24 4-24 4-24 4-25 4-25

New Features 1. Introduction 1.1. 1.2. 1.3. 1.4. 2.

Introduction . . . . . . Structure of This Guide Associated Documents Conventions . . . . . .

Actions to be taken prior to Software Installation . . . . . . . . . . . . . . 2.1. 2.2. 2.3. 2.4. 2.5. Save previous release . . . . . . . . . . . . . . . . . . Customer specific data . . . . . . . . . . . . . . . . . 2.2.1. Customer specific data - automated protection Archiving the LES Database . . . . . . . . . . . . . . Dumping the Online Database . . . . . . . . . . . . . Generating POP files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.

DEC Products Installation and Configuration . . . . . . . . . . . . . . . . 3.1. 3.2. VMS Image backup Restoration . . . . . . . . . . . . . . Restoring the saveset from tape to the System Disk . . . 3.2.1. Shutting Down a Vax System . . . . . . . . . . . . 3.2.2. Dismounting the System Disk . . . . . . . . . . . 3.2.3. Standalone Boot for Vax 4000-100 Series Systems Installation of Licences . . . . . . . . . . . . . . . . . . . DECNET configuration . . . . . . . . . . . . . . . . . . . Installation of Disks . . . . . . . . . . . . . . . . . . . . . System Configuration . . . . . . . . . . . . . . . . . . . . Preparing for Project Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3. 3.4. 3.5. 3.6. 3.7. 4.

LES Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1. BAP Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1. Deinstallation of Existing BAP . . . . . . . . . . . . . . . . . . 4.1.2. Installation of New BAP . . . . . . . . . . . . . . . . . . . . . . 4.1.2.1. BAP system information for new installations only . 4.1.2.2. BAP system information for exisiting installations . 4.1.2.3. Problems during an initial BAP installation . . . . . . 4.1.3. Additional post installation actions . . . . . . . . . . . . . . . 4.1.3.1. Restore protected Files. . . . . . . . . . . . . . . . . 4.1.4. Start Installation Outage . . . . . . . . . . . . . . . . . . . . . 4.1.4.1. Rename FEP load files on Master BAP . . . . . . . . 4.1.4.2. Stop the Master BAP . . . . . . . . . . . . . . . . . . 4.1.4.3. Define FEP load files on upgraded BAP and re-trigger 4.1.5. Automated completion of installation . . . . . . . . . . . . . .

Customer Release Configuration Guide Telecomunicaciones De Mexico

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

4.2.

4.1.5.1. Automated completion dialogue . . . . . . . . . . . 4.1.5.2. Automated saved file comparison . . . . . . . . . . 4.1.6. Configuring a New BAP . . . . . . . . . . . . . . . . . . . . . 4.1.6.1. Running DEFSAD.COM on a new BAP . . . . . . . 4.1.7. Confidence Checks . . . . . . . . . . . . . . . . . . . . . . . 4.1.8. Installation Template . . . . . . . . . . . . . . . . . . . . . . 4.1.9. Installation Template Example . . . . . . . . . . . . . . . . . SOC Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.1. Deinstallation of Existing SOC . . . . . . . . . . . . . . . . . 4.2.2. Installation of New SOC . . . . . . . . . . . . . . . . . . . . . 4.2.2.1. SOC system information for new installations only 4.2.3. Install SOC software . . . . . . . . . . . . . . . . . . . . . . . 4.2.3.1. Configuring the SOC ID on the BAP . . . . . . . . . 4.2.3.2. Problems during an initial installation . . . . . . . 4.2.4. Currently required additional manual actions . . . . . . . . . 4.2.4.1. Setting up the System Usage Displays . . . . . . . 4.2.5. Configuring A New SOC . . . . . . . . . . . . . . . . . . . . 4.2.5.1. Running DEFSAD.COM on a new SOC . . . . . . . 4.2.6. Installation Template . . . . . . . . . . . . . . . . . . . . . . 4.2.7. Installation Template Example . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

4-25 4-30 4-31 4-31 4-39 4-40 4-43 4-46 4-46 4-49 4-51 4-52 4-57 4-58 4-62 4-62 4-62 4-63 4-65 4-66 5-1 5-1 5-1 6-1 6-1 6-2 6-2 6-2 6-2 6-2 6-3 6-3 6-4 6-4 6-5 6-6 7-1 7-1 7-1 7-3 7-3 7-3 7-4 7-4 7-6 7-7 7-8 7-9 7-9

5.

Sybase Product Installation 5.1. 5.2.

. . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to Sybase Concepts . . . . . . . . . . . . . . . . . . . . Installation of Sybase Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.

LES Software EBF Installation 6.1.

6.2. 6.3. 7.

BAP EBF Installation . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.1. Actions to be performed prior to software upgrade . . . . 6.1.2. Stop and Deinstall the Standby BAP and one SOC . . . . . 6.1.3. Install the new software on the stopped BAP and SOC . . 6.1.4. Database conversions . . . . . . . . . . . . . . . . . . . . 6.1.4.1. Example Online Database Conversion Procedure 6.1.4.2. Example OffLine Database Conversion Procedure 6.1.5. FEP installation . . . . . . . . . . . . . . . . . . . . . . . . 6.1.6. Start the newly installed BAP and SOC . . . . . . . . . . . SOC EBF Installation . . . . . . . . . . . . . . . . . . . . . . . . . BAP EBF Automated Installation . . . . . . . . . . . . . . . . . . . 6.3.1. Install the new software on the stopped BAP . . . . . . . .

Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1. Installation of LES Database . . . . . . . . . . . . . . . . . . . . . 7.1.1. Installing the LES Database . . . . . . . . . . . . . . . . . 7.1.2. The Sybase Report Writer Product . . . . . . . . . . . . . . 7.1.3. Loading the Specific Population Files into the Database . . 7.1.4. Installing the Offline Database . . . . . . . . . . . . . . . . Database Administration Duties During an LES Software Upgrade 7.2.1. Database Administration PRIOR to Upgrade . . . . . . . . 7.2.2. Database Administration During Upgrade . . . . . . . . . . 7.2.2.1. DBCC corrective actions . . . . . . . . . . . . . . 7.2.3. Database Conversion (ONDB) . . . . . . . . . . . . . . . . 7.2.4. Database Administration Issues after Successful Upgrade Database General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.

7.3.

ii

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

7.4.

7.3.1. Sybase Account Details . . . . . . . . . . . . . . . . . . . 7.3.2. Creating the Sybase Devices . . . . . . . . . . . . . . . . 7.3.3. Changing the Sybase System Administrators Password Populating the Database . . . . . . . . . . . . . . . . . . . . . . 7.4.1. The Basic Database Dump and the PINS Prebuild . . . . 7.4.2. Specific Variants of PINS . . . . . . . . . . . . . . . . . .

. . . . . .

. . . . . .

. . . . . .

7-10 7-10 7-11 7-11 7-11 7-12 8-1 8-1 8-7 8-11 8-11 8-13 9-1 9-1 9-2 9-3 9-3 10-1 10-1 10-1 10-1 10-1 10-3 10-3 10-4 10-4 10-5 10-5 10-5 11-1 11-1 11-2 11-3 12-1 12-1 12-3 12-12 12-12 12-13 12-13 12-13 12-13 12-14 12-15 12-15 12-16

8.

LES Software Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1. 8.2. 8.3. Starting the BAP . . . . . . . . . . . . . . . . . . . . . Starting the SOC . . . . . . . . . . . . . . . . . . . . . Starting the SOC Viewer . . . . . . . . . . . . . . . . 8.3.1. Starting the SOC Viewer from the SOC . . . . 8.3.2. Starting the SOC Viewer from the BAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.

Tracing the Running System . . . . . . . . . . . . . . . . . . . . . . . . . 9.1. 9.2. Tracing facilities on the BAP . . . . . . . 9.1.1. Fault location on the BAP . . . . . 9.1.2. Process tracing on the BAP . . . Tracing facilities on the SOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.

Procedure to revert to an old version of BAP or SOC 10.1. BAP Fallback procedure . . . . . . . . . . . . . . 10.1.1. BAP Fallback procedure Summary . . . . . 10.1.2. Stop the upgraded BAP . . . . . . . . . . . 10.1.3. Save current live data . . . . . . . . . . . . 10.1.4. Restoring the database . . . . . . . . . . . 10.1.4.1. Restore previous DB dump . . . 10.1.4.2. Restore live data . . . . . . . . . 10.1.5. Rename FEP load files and re-trigger FEPS 10.1.6. Restart unaffected BAP . . . . . . . . . . . 10.1.7. Restore the software on the upgraded BAP. 10.2. SOC Fallback procedure . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.

BAP Maintenance

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.1. Changing the Ocean Areas and Spot IDs . . . . . . . . . . . . . . . . 11.2. Changing the Janitor Criteria . . . . . . . . . . . . . . . . . . . . . . . 11.3. Changing the Channel Unit Rack Displaying Summary Alarms . . . . 12. FAX Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.1. Hardware and Software Installation . . . . . . . 12.1.1. Install Pathworks on the LES . . . . . . . 12.1.2. Database Tables Required . . . . . . . . 12.1.3. Install Etherworks card . . . . . . . . . . 12.1.3.1. Installing Etherworks 3 . . . . . 12.1.3.2. Installing Etherworks 2 . . . . . 12.1.4. Install Modem cards . . . . . . . . . . . . 12.1.4.1. Notes For All Modem Types . . 12.1.5. Hayes modem commands . . . . . . . . 12.1.6. Taking a Fax Modem Card Out Of Service 12.1.7. Install Operating System . . . . . . . . . 12.1.8. Install NTS/2 LAPS Software . . . . . . .

iii

Customer Release Configuration Guide Telecomunicaciones De Mexico

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

12.1.9. Install Etherworks driver . . . . . . . . . . . . . . . . . 12.1.9.1. Installing Etherworks 3 . . . . . . . . . . . . . 12.1.9.2. Installing Etherworks 2 . . . . . . . . . . . . . 12.1.10. Installing LAN Server/Requester . . . . . . . . . . . . . 12.1.11. LAN Requestor commands . . . . . . . . . . . . . . . . 12.1.12. Install Pathworks on PCs . . . . . . . . . . . . . . . . . 12.1.12.1. Installing Pathworks Version 5.0 . . . . . . . 12.1.12.2. Installing Pathworks Version 2.0 . . . . . . . 12.1.13. Setup Remote Remote Access . . . . . . . . . . . . . . 12.1.14. Install Zetafax Software . . . . . . . . . . . . . . . . . . 12.1.14.1. Create Zetafax Folders for OS/2 . . . . . . . . 12.1.14.2. Create Zetafax Folders for OS/2 Warp . . . . . 12.1.15. Install PC Fax Software . . . . . . . . . . . . . . . . . . 12.2. Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1. Upgrading Zetafax Version 2.1 - 4.0 . . . . . . . . . . . 12.2.2. Upgrading Zetafax Version 4.0 - 4.0+ HNS Extensions . 12.2.3. PCFAX Upgrade . . . . . . . . . . . . . . . . . . . . . . 12.3. Creating and installing the Letterhead file . . . . . . . . . . . . 12.4. Fax Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 12.4.1. DecNet Troubleshooting . . . . . . . . . . . . . . . . . 12.4.2. Zetafax and Fax Modem Troubleshooting . . . . . . . . 12.4.2.1. Zetafax Error messages returned to the ACSE 12.4.3. Pathworks Troubleshooting . . . . . . . . . . . . . . . A. B. Accounts and Privileges PC System file examples Index

. . . . 12-17 . . . . 12-18 . . . . 12-19 12-20 . . . . 12-22 . . . . 12-22 . . . . 12-22 . . . . 12-24 . . . . 12-29 . . . . 12-29 . . . . 12-32 . . . . 12-33 . . . . 12-33 . . . . . . . . 12-34 . . . . 12-35 . . . . 12-36 . . . . 12-36 . . . . 12-36 . . . . 12-37 . . . . 12-37 . . . . 12-39 . . . . 12-40 . . . . 12-42 A-1 B-1 1

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

iv

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

List of Figures
12-1 FAX Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Referenced and Related Documents


1. Inmarsat-C LES Operators Guide Identity: A4-OPG-003076 Issue: latest 2. ACSE System manual Identity: A4-OMM-003076 Issue: latest 3. VAXStation 3100 Model 30 Owners Manual Identity: EK-265AA-OM-001 Issue: 4. Pathworks for VMS : Server Installation Guide Identity: AA-LB63E-TE Issue: September 1991 5. OS/2 2.1 Using the Operating System Identity: May 1993 Issue: First Edition 6. Users Guide to OS/2 Warp Identity: October 1994 Issue: First Edition NTS/2 : LAN Adapter and Protocol Support Configuration Guide Identity: S96F-8489-00 Issue: First Edition (September 1992) 7. LAN Server Network Administrator Reference Volume 1: Planning and Installation Identity: S96F-8428-00 Issue: First Edition 8. Pathworks for OS/2 : Installation and Configuration Guide Identity: AA-PB99E-TK Issue: October 1994

Customer Release Configuration Guide Telecomunicaciones De Mexico

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

9. Pathworks for OS/2 : Installation and Configuration Guide Identity: AA-PB99C-TK Issue: September 1991 10. ZETAFax User Manual Identity: May 1995 Issue: Release 4.5

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Glossary
ASCII United States version of IA5 (internationally standardized alpha-numeric code with national options). ACSE Access Control and Signalling Equipment.

BAP Background Application Processor. There are two BAPs, for redundancy purposes. CCC Call Completion Code. CD-ROM Compact Disk Read Only Memory. CES Coast Earth Station. This is the previous name for the LES. CES is still referred to in some system prompts. DBCC Database Consistency Checker. DEC Digital Equipment Corporation. DECNET Networking protocol for DEC systems. DEMSA DEC VAX system used as front end processor for X25. DOS Disk Operating System. EBF Emergency Bug Fix EQUISYS Authors and distributors of the Zetafax software.

FAX

Customer Release Configuration Guide Telecomunicaciones De Mexico

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Facsimile produced from text file and transmitted over PSTN (telephone) network. FEP Front End Processor. There are at least two FEPs for each driver, for redundancy purposes.

FTU Fax transmission Unit. GKS Graphical Kernel System. A VMS layered software product, for controlling graphics on a screen. HNS Hughes Network Systems. IBM International Business Machines. LAN Local Area Network. LAPS Local Area Protocol Support. PC software required for FAX operation. LES Land Earth Station. The system that stores and forwards messages between terrestrial users and mobile users operating MESs. Communicates with the NCS to obtain satellite resources. Operated by a telecommunications company. Formerly known as CES. MES Mobile Earth Station. The terminal accessing the Inmarsat-C network via the Inmarsat-C protocol. MOTIF DECWindows system software. NCP Network Control Program. Used to configure and control DECnet networks. NCS Network Coordination System. The system that coordinates access to the satellite resources in the Inmarsat-C system. Operated by Inmarsat.

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

NTS/2 Network Transport Services. PC software required for FAX operation.

OS/2 Graphical operating system supplied by IBM. PATHWORKS Networking Software to communicate VAX and PC systems. PC Personal Computer. PCFAX The HNS software running on a PC, interacting indirectly with the LESFAX software via the WORK AREA, and directly with the ZETAFAX software via the ZETAFAX API (Application Programmers Interface). PIPM Pipe Manager. Component of LES Software. POP Population file. Files that contain data that can be inserted into the database tables. PSI Packetnet System Interface. SCSI Small Computer Systems Interconnect. SDA System Database Access. The LES component that interfaces to the LES database. SHADOWSET Two or more VAX disks can be shadowed to provide data redundancy in the event of a disk drive or disk controller failure. Such a set of disks is accessed logically as if it were a single disk. SOC System Operator Console. The software responsible for the LES user interface. Runs on a VAX workstations. SQL Structured Query Language. High-level language used by SYBASE. SYBASE Relational Database used for storing data in the LES.

Customer Release Configuration Guide Telecomunicaciones De Mexico

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

TDMS Terminal Data Management System. A VMS layered software product, for controlling forms on a screen. UIC User Identification Code. Used by VMS to allocate and identify ownership. UIS User Interface System. The programming interface to the windowing application software (VWS) on a VAX workstation. VAX Virtual Address Extension. VAX computers are made by DEC. The range includes workstations such as the VAXstation 3100, superminis such as the MicroVAX 3800, and single-board processors such as the KA620, all of which are used in the LES hardware configuration. VMS Virtual Memory System. The operating system that runs on VAX computers. VWS VMS Workstation Software. The windowing system on a VAX workstation. X25 Communications protocol used to exchange digital data. ZETAFAX Fax delivery software, supplied by Equisys.

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

New Features
In V3.7 of the Customer Configuration Guide for Telecomm This is the first Customer Configuration Guide to be issued to Telcomm since V3.0. Changes applied in the latest revision are indicated by the heavier change bar. The major changes made and new features introduced since that issue are: The BAP installation procedure description has been ammended, removing minor errors (in the description) and making the sequence more logical in following actual practice. A new section (4.1.4) has been introduced to describe any upgrade actions required after the first BAP and SOC have been installed or upgraded, but before starting the BAP and the second BAP and SOC have been modified. An index has been added covering the BAP installation. The description on how to set up the asynchronous interface is included as a new chapter. Previously this was in the Operator Guide. The description of a new command line has been included. This has to be entered after BAP installation, to configure the improved System Usage Display. New logical names have been introduced for the elements of second shadow set. This affects the prompts during BAP installation. There are also a number of minor changes and updates which have been made as part of the ongoing improvements to the customer deliverable documentation.

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico Introduction

Chapter 1 Introduction
1.1 Introduction This document is a guide to the installation of the Inmarsat-C Land Earth Station Software (LES) for Telecomunicaciones De Mexico. Specific installation and operations information for the LES Software on VAX/VMS computers is included. 1.2 Structure of This Guide This chapter contains a brief summary of the rest of this Guide. Chapter 2 describes the procedures for making backups of the system. This information may be subsequently used to restore the system, for instance in the case of a bad upgrade. Chapter 3 details the procedures to be followed when installing VMS and the layered products. Chapter 4 gives instructions on installing the LES Software on the BAP, FEP and SOC processors. Chapter 5 gives instructions on installing the Sybase database products on the BAPs. Chapter 6 gives step by step instructions on how to upgrade the LES Software on a live LES system which must continue to carry traffic. Chapter 7 discusses the organisation and management of the Sybase databases. Chapter 8 shows how to start the BAP and SOC processors and includes details of customer specific startup. Chapter 9 describes methods for obtaining tracing information from the running LES system. Chapter 10 describes the method for reverting to the old version of software, in the case of an upgrade failing. The data used in this case will be that which was saved in chapter 2. Chapter 11 describes the methods for the occasional maintenance of parts of the BAP configuration. Chapter 12 gives instructions on installing the FAX PCs, Modems and the associated software. Appendix A describes the system of accounts used to run the LES software. Appendix B provides examples of system files for FAX PCs

1-1

Customer Release Configuration Guide Telecomunicaciones De Mexico Introduction

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

1.3 Associated Documents The following documents may be useful in association with the Customer Release Configuration Guide: Inmarsat-C LES Operators Guide Ref [1] VAXStation 3100 Model 30 Owners Manual Ref [3] 1.4 Conventions Throughout this document there is a common method for indicating system prompts shown in bold and user input shown in italics. General system output is shown as: small light text. Where any additional comments are provided in the middle of a long run of system output they are shown in italics. Where user input consists of a single answer to a prompt, it is shown in bold with angle brackets <thus>. In such cases, if a null input is required (just hitting the RETURN key), it is shown as <>. Where an input is described by Ctrl/ key this indicates the key is used in conjunction with the control key. Where input includes items in (parentheses), this indicates valid input descriptions (e.g. (TAPE DRIVE)). Items shown in [brackets] denote a default value, which can be chosen without further input simply by hitting the RETURN key. Other documents are referenced to the Referenced and Related Documents section by its number in square brackets, e.g. "Inmarsat-C LES Operators Guide" will be reference [1]. The prompt for VAX command lines is shown as a dollar prompt $. On Telecomunicaciones De Mexico systems this prompt will be redefined (e.g. CES MEBAPA> on a BAP and CES MESC1A> on a SOC).

1-2

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Chapter 2 Actions to be taken prior to Software Installation


Prior to any upgrade, it is necessary to ensure certain aspects of the system are saved. This is to ensure that in the case of any problems, with the upgrade, it is possible to fall back to the old version of software. Refer to section 3.2 for instructions on how to restore a BAP from a backup. 2.1 Save previous release If a backup has not been taken of the LES recently, then the old BAP and SOC software should be backed up to tape. Before doing this, the disk should be tidied. This should include: Purging whole disk (but take care to preserve any file versions which are currently being worked on) Deleting all unwanted files, including, for example *.tjl; *.tmp; tmp.*; reports, old log, billing, error files which are no longer required. database dumps already backed up or no longer required. Dismount the system disk from other nodes, on the cluster, shut down the BAP then boot it as standalone. See section 3.2 for instructions. Ensure a write enabled tape is inserted in the drive. Initiate the backup by entering: $ BACKUP/IMAGE/LOG/OVERWRITE $1$DIA5: MKA500:FULLBACK.BCK /LABEL=040194/REW Where $1$ DIA5: is the system disk, and MKA500: is the magnetic tape device. Once in Standalone reboot, the system prompts with: Do you want to perform another standalone backup. [YES]. This will return to the system prompt. At this stage the system can be rebooted, by pressing HALT and B (at the three chevrons prompt). In the case of a normal routine installation, it will not always be neccesary to perform a full, standalone backup, normally a simple disk backup will suffice. $ BACKUP/LOG/OVERWRITE $1$DIA5: MKA500:DIA5_BACK.SAV/SAV /LABEL=040194/REW
2-1

Customer Release Configuration Guide Telecomunicaciones De Mexico Actions to be taken prior to Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

After the installation of the new software, should problems arise and there is a need to go back to the old release, then this image backup can be restored from the tape (rather than the software release). For further details on the fall back procedure see chapter 10. 2.2 Customer specific data This section identifies a procedure for saving customer specific LES data prior to an installation. Any customer specific data files should be copied to a safe directory, perhaps on the quorum disk, until the installation is complete. The customer specific files should be resupplied with a new release. These should be checked against the pre-release files for any inconsistencies. To do this see 4.1.3.1. Take care not to overwrite file protected during the first pass with files from the second pass. Some are node specific. Customer specific files are: CRM$EXE:CRM_MEMORY_PARAMETERS_MEXICO.DAT DRH$EXE:DRH_CNTL_FLAG.INI MDIR$EXE:MDIR_CP_INIT_MEXICO.DAT MSCH$EXE:MSCH_CP_INIT_MEXICO.DAT SOI$EXE:SOI_WS_SETUP.TXT SOI$EXE:SOI_CNTL_FLAG.INI BM$EXE:AUTO_BILLING_CONFIG.DAT BM$EXE:BM_AHK_CONFIG.DAT XCCC$EXE:TABLE_MEXICO.TXT XCCC$EXE:X25_PARAMS.DAT MCM$EXE:JANITOR.INI MCM$EXE:MCM_CNTL_FLAG.INI CUTL$DAT:CUTL_MH_CONVERSION.DAT FAX$EXE:LESFAX_PARAMS_MEXICO.DAT Check the current [BAPSW...] area for any other files which may be required (for example customer produced command files). All files remaining in this area may be deleted during the installation. 2.2.1 Customer specific data - automated protection From release 80140 onwards, a generic file

2-2

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico Actions to be taken prior to Software Installation

SAD_PROTECT_FILES.DAT will be delivered and placed in SAD$EXE. This will contain a list of all files which are known to require protection. During an installation, the existing data file will be used to protect critical file, including itself. On completing installation, the new file will be used to create a differences list for the saved and new files. The option ignore either file (old or new) or to edit the new file will be offered at that time. When loading the first release containing this file, a verified copy should be placed in the existing [BAPSW.REL801x.SAD.EXECUTE] directory in order to make use of this new facility as soon as possible. The content of this file should be checked to ensure that all wanted files are listed (verify against the list in the previous section). Any missing or additional files should be included using the same conventions. This file will protect itself, and may thus be propagated from release to release. Similarly, this file may be checked before installing any subsequent release to ensure that it reflects the current needs. 2.3 Archiving the LES Database Certain Database tables, especially those governing the system configuration, should be archived prior to an installation. This section describes the procedures required to save the Online database. The ONLINE database would normally be running on the master BAP. Ensure that the online server is active using the following command: $ SHOWSERVER /SERVER=ONDB If the server is not active start the ONLINE database : $ @SAD$EXE:SAD_START_SYBASE Ensure that the file SOCV_ONLN_CONFIG_TABLES.DAT has not been compromised by checking its creation date is prior to that of the last upgrade. Enter: $ DIRECTORY/DATE SOCV$EXE:SOCV_ONLN_CONFIG_TABLES.DAT If the date displayed is later than the last full installation date then contact HNS. Login to the SOCViewer, on the system running the database (that is the Master BAP). Select Online Processing Select Database Management Select Archive Database Configuration 2.4 Dumping the Online Database Database Dumps must be performed, just prior to the database upgrade, so that they can be reloaded should any problems occur with the upgraded system. To do this, refer to section 7.2.1.
2-3

Customer Release Configuration Guide Telecomunicaciones De Mexico Actions to be taken prior to Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

2.5 Generating POP files. Any data data liable to be subject to conversion should be saved to POP files. The software release notes will advise if this is necessary. Start the Database Viewer & Pop File Generator by entering: $ @PINS$EXE:PINS_VIEWER_START This is menu driven from which the tables required for dumping may be selected. The population files are created in the PINS$EXE directory. It is advisable to create a temporary area on the quorum disk to hold these .POP files, for the duration of the installation. This is especially important for a live system upgrade, since every other disk is affected by the installations performed on both BAPs.

2-4

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Chapter 3 DEC Products Installation and Configuration


This chapter describes the installation and configuration of the DEC software (VMS and layered products) on a new system. This chapter is only intended for reference by HNS staff performing DEC installations. It is not intended as a specific guide for any individual customer configuration. 3.1 VMS Image backup Restoration This section describes the production of the image backup (that is the saveset) of a BAP and SOC node. The System Manager, at HNS, is tasked with the production of this saveset. It is, therefore his responsibility to install all of the required layered products on a test rig and then produce the image backup. This document will not discuss the details of the System Managers activities. NOTE: Before any new data is restored to the system disk it must be established that a backup of the current state of the system disk has been taken. Section 2 describes this operation. The steps to restore from an image backup will also be taken in the event of a disk failure where the disk data has been lost. Reference 1 describes how regular backups are taken and advises upon backup frequency. However in the case of disk failure, HNS should be contacted before any restoration is made. 3.2 Restoring the saveset from tape to the System Disk For a save set to be successfully restored to a system disk, then the system must be configured such that the system disk will not be in use, or directly accessed by any other system while the restore is in progress. For a successful restore, the following conditions must apply: That the system that uses the system disk to be restored is shut down. That the system disk to be restored is not mounted on the other bap. The system that uses the system disk can be booted into standalone mode. In standalone disk files are not accessed which allows a successful restore to the system disk. The following subsections describe the process of making a successful restore. Each subsection describes a discrete step, which must be taken in the order shown below. As an example, it is assumed that the system disk for BAPA is to be restored. BAPA is clustered to BAPB and the cluster is functioning normally. The steps to restore are: 1. Shut down BAPA. (Section 3.2.1). 2. Dismount BAPAs system disk from BAPB. (Section 3.2.2). 3. Boot BAPA as standalone. (Section 3.2.2 or 3.2.3, depending on what model BAPA is).
3-1

Customer Release Configuration Guide Telecomunicaciones De Mexico DEC Products Installation and Configuration

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

4. Restore the system disk from magnetic tape. (Section 3.2.3). 5. Boot the BAP. The manner in which the BAP is booted depends upon the circumstances of the restore. If the restore is of a backup taken from BAPA in its present configuration, then BAPA can be rebooted and brought into service. If the restored image is not from BAPA in its present configuration, then it will require booting in isolation from other cluster devices (apart from the system disk) and VMS configured to the cluster. (Section 3.2.3). This section also describes the booting of the system, and all subsequent sections are concerned with configuring VMS. 3.2.1 Shutting Down a Vax System Log into the system account on BAPA. Now shut down BAPA. Enter: $ @SYS$SYSTEM:SHUTDOWN Enter <Y> at the prompt to confirm the system is to be shut down. This will display a prompt for Reason, the response should be Image_backup and at the prompt for shutdown options enter Remove_node,Save_feedback,Reboot_check where: Remove_node Ensures that the BAP is safely removed from the cluster. The other BAP will make adjustments to acknowledge this. Save_feedback Saves collected system data into a file, creating a new Autogen file for use after the system reboots. Reboot_check Verifies that all files necessary for the system to reboot are present. If any are not then the operator is notified. Any missing files must be replaced before the system is shut down. Like DCL commands, the shutdown option names can be truncated, as long as the string remains unique. For example, the operator can type Remove,Save,Reboot. Enter return (<>) to all other prompts. Once the "SYSTEM SHUTDOWN COMPLETE" message appears, then BAPA is ready to be booted as a standalone system. 3.2.2 Dismounting the System Disk Perform the following steps: 1. Log into BAPB as SYSTEM. 2. On BAPB check the identity of BAPAs system disk by entering: $ SHOW DEVICE D This will return the information on all drives. For example:
Device Name Device Status Error Count Volume Label Free Trans Mnt Blocks Count Cnt

3-2

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


DSA7: DSA8: $1$DIA0: $1$DIA1: $1$DIA2: $1$DIA3: $1$DIA4: $1$DIA5: $1$DIA6: $1$DIA9: $1$DKA400: Mounted Mounted Mounted ShadowSetMember ShadowSetMember Mounted Mounted ShadowSetMember ShadowSetMember Mounted Online wrtlck

Customer Release Configuration Guide Telecomunicaciones De Mexico DEC Products Installation and Configuration
0 0 0 0 0 0 0 0 0 0 0 USER01 USER02 BAPA_SYS (member of (member of QUORUM BAPBB_SYS (member of (member of USER03 250857 312405 254055 DSA7:) DSA8:) 41373 386763 DSA7:) DSA8:) 25824 20 3 363 1 1 1 2 2 2 2 2 2

(R5SEGF) (R1AEUI) (R1CINE) (R1C2AI) (R5WIEG) (R1UDWA) (R1TKEE) (R5ULVG) (CVAXA)

In the above example, $1$DIA0: is the system disk for BAPA, which will require dismounting from BAPB. 3. On BAPB, enter: $ DISMOUNT/CLUSTER (BAPAs SYSTEM DISK DEVICE) The following standalone backup will work on 3100, 4000-60 and 4000-700 series systems. NOTE: On 3100 systems the expansion box containing the TK50 drive may need to be connected to the workstation. This is so that a media drive is available for backup/restoration Refer to section 4.2.2 for instructions. Press Halt key on BAPA. The >>> prompt will appear on the console. Boot Standalone with Backup from the ">>>" prompt on a console connected to OPA0: type: >>> SHOW DEVICE This gives a list of tape and disk devices on the current node. >>> SHOW BOOT This gives the current boot device i.e. the system disk. >>> B/E0000000 (SYSTEM DISK DEVICE) The system will now boot into standalone mode. 3.2.3 Standalone Boot for Vax 4000-100 Series Systems Press Halt key on BAPA. The >>> prompt will appear on the console. Ensure that the correct CD-Rom that contains the standalone system is loaded into the CDRom drive. The CD-Roms volume number is VMS2H4055 (Volume 1 of 1). Boot Standalone with Backup from the ">>>" prompt on a console connected to OPA0: type: >>> B DKA400: The system will now boot into standalone mode. If a CD_Rom drive is not available, the system can be booted standalone (from the >>> prompt) by entering: >>> B/E0000000 (SYSTEM DISK DEVICE)
3-3

Customer Release Configuration Guide Telecomunicaciones De Mexico DEC Products Installation and Configuration

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

VMS boots to the standalone prompt which allows backup commands to be typed in. Insert the tape into the tape drive (for example MKA500:). At the standalone prompt type: BACKUP/IMAGE/LOG (TAPE DEVICE):(SAVESET_NAME).SAV/REWIND/IGNORE=LABEL) (SYSTEM DISK) Where SAVESET_NAME is the name given to the saveset when it was taken. This will be on the tape label and associated documentation. As the saveset may span more than one tape watch out for Operator messages prompting for the next tape. The labels on the tape will indicate how many volumes were used to back up the system. The restore should take less than 3 hours. When the image backup is restored, the System will prompt for further backup operations, at this point halt the System. The >>> prompt will appear on the console. BAPA is now ready for booting. In the case of a normal installation from a HNS supplied tape, then the BAPA will have to be booted without ethernet connections. Then VMS can be configured. If the backup was from BAPA in its present configuration, it can be brought straight into service. Booting BAPA when VMS re-configuration is required. Boot with the node not connected to the ethernet and only the System Disk Online. This will prevent any spurious DECNet connections and the wrong disks from being mounted. At the ">>>" prompt type: >>> b VMS should boot. VMS will allow one login at the Operator Console. Log in to the SYSTEM account. Follow the following sections in this chapter for configuring VMS. Booting BAPA from a backup that required no configuration. Ensure all disks are running and ethernet connections are made. At the ">>>" prompt type: >>> b VMS should boot. BAPA should now be ready. 3.3 Installation of Licences Load all licenses for both BAPs on each node. This is a feature of VMS5.5-2 - DEC expect there to be only one System Disk in a Cluster with one license database, so to simulate this all nodes in a Dual System Disk Cluster have to have duplicate license databases.
3-4

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico DEC Products Installation and Configuration

First the old licenses have to be dropped. Obtain a list of licenses, at the "$" prompt type: $ LICENSE LIST
License Management Facility License Database File: Created on: Created by user: LMF Version: SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB;1 16-AUG-1993 SYSTEM V1.1

----------------------------------BASE-VMS-250136 DEC DVNETEND DEC DVNETEND DEC NET-APP-SUP-300 DEC P.S.I.-ACCESS DEC P.S.I.-ACCESS DEC P.S.I.-ACCESS DEC VAX-VMS DEC VAXCLUSTER DEC VAXCLUSTER DEC VMS-USER DEC VMS-USER DEC VOLSHAD DEC VOLSHAD DEC

Each individual product must be dropped using the following commands because the licenses are invalid on the BAP. $ LICENSE DELETE/ALL (PRODUCT NAME) e.g. LICENSE DELETE/ALL VOLSHAD This will delete all occurrences of a particular product from the license database. The license database is then ready to be loaded with the licences specific to the BAP. Type the following: $ @SYS$UPDATE:VMSLICENSE
VMS License Management Utility Options: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. REGISTER a Product Authorization Key AMEND an existing Product Authorization Key CANCEL an existing Product Authorization Key LIST the Product Authorization Keys MODIFY an existing Product Authorization Key DISABLE an existing Product Authorization Key DELETE an existing Product Authorization Key COPY an existing Product Authorization Key MOVE an existing Product Authorization Key ENABLE an existing Product Authorization Key SHOW the licenses loaded on this node SHOW the unit requirements for this node

99. EXIT this procedure Type ? at any prompt for a description of the information requested. Press Ctrl/Z at any prompt to exit this procedure. Enter one of the above choices [1] <>

3-5

Customer Release Configuration Guide Telecomunicaciones De Mexico DEC Products Installation and Configuration
Do you have your Product Authorization Key? [YES] <> Use the REGISTER option to add a new license to a license database. A Product Authorization Key (PAK) provides the product name and information you need to register the license. You must enter all the information provided by your PAK exactly as it appears. PAK ID: Issuer [DEC]<DEC> Authorization Number []<ALS-IL-98364-72348> PRODUCT ID: Product Name []<VMS-USER> Producer [DEC]<DEC> NUMBER OF UNITS: Number of Units []<800> KEY LEVEL: Version []<> Product Release Date []<> KEY TERMINATION DATE: Key Termination Date []<> RATING: Availability Table Code []<> Activity Table Code []<CONSTANT=100> MISCELLANEOUS: Key Options []<NO_SHARE>

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

This Product Authorization Key has been provided with the NO_SHARE option. This requires that this license be restricted to a specific node within a cluster. Enter the node name of the VAXcluster member to which this license is restricted. Is this PAK restricted to a cluster member node? [YES] <> Node this PAK is restricted to (SCS Node name) [] <CVAXA> Product Token []<> Hardware-Id []<> Checksum []<1-DPNT-WDFG-UMSD-ADAW> License Database File: Issuer: Authorization: Producer: Product Name: Units: Release Date: Version: Termination Date: Availability: Activity: Options: Token: Hardware ID: Checksum: SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB DEC ALS-IL-98364-72348 DEC VMS-USER 800

CONSTANT=100 NO_SHARE 1-DPNT-WDFG-UMSD-ADAW

This authorization key is restricted to: CVAXA Is this information correct? [YES] <> Registering VMS-USER license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB... Do you want to LOAD this license on this system? [YES] <> VMS License Management Utility Options: 1. REGISTER a Product Authorization Key

3-6

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12.

Customer Release Configuration Guide Telecomunicaciones De Mexico DEC Products Installation and Configuration

AMEND an existing Product Authorization Key CANCEL an existing Product Authorization Key LIST the Product Authorization Keys MODIFY an existing Product Authorization Key DISABLE an existing Product Authorization Key DELETE an existing Product Authorization Key COPY an existing Product Authorization Key MOVE an existing Product Authorization Key ENABLE an existing Product Authorization Key SHOW the licenses loaded on this node SHOW the unit requirements for this node

99. EXIT this procedure Type ? at any prompt for a description of the information requested. Press Ctrl/Z at any prompt to exit this procedure. Enter one of the above choices [1] <99>

Do not forget to load all licenses on both BAPs. 3.4 DECNET configuration The NCP database must be configured. HNS recommends that the BAP Nodes are called CVAXA and CVAXB, although any other name can be selected. Run the command file SYS$MANAGER:NETCONFIG.COM to define the executor node. HNS will provide DECNet addresses for all nodes on a system.
What do you What do you Do you want Do you want Do you want Do you want Do you want Do you want Do you want want your DECnet node name to be? [CRUX]: want your DECnet address to be? [41.80]: to operate as a router? [NO (nonrouting)]: a default DECnet account? [NO]: default access to the TASK object disabled? [YES]: a default account for the MAIL object? [YES]: a default account for the FAL object? [NO]: a default account for the PHONE object? [YES]: a default account for the NML object? [YES]: <CVAXA> <57.xx> <NO> <YES> <NO> <> <YES> <> <>

Finally execute the created command file by answering <YES> to the "Do you want these commands to be executed?" prompt.

Define a node to copy known nodes from, for example: $ MC NCP NCP> SET NODE 57.172 NAME CVAXA NCP> DEF NODE 57.172 NAME CVAXA Copy known nodes from EARTH (used here as an example node, it is on the development cluster at HNS LTD) to both the permanent and volatile NCP databases. $ MC NCP NCP> COPY KNOWN NODES FROM EARTH TO BOTH
3-7

Customer Release Configuration Guide Telecomunicaciones De Mexico DEC Products Installation and Configuration

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Ensure that the executor maximum link parameter is set to 256 $ MC NCP NCP> SHOW EXEC CHAR NCP> DEFINE EXEC MAX LINKS 256 NCP> SET EXEC MAX LINKS 256 NOTE: This procedure sets the service state of the downline load circuit to off. This will prevent downloading over ethernet. It must be switched back to on as part of fepinstall. See section 6.1.5. 3.5 Installation of Disks Defining the disks: Type: $ SHOW DEV D NOTE: DO NOT INITIALISE THE SYSTEM DISK. To initialise an RF35 disk type: $ INIT $1$DIAn/HEADERS=100000 (VOLUME NAME) The Quorum disk must be initialise with volume name "QUORUM" To initialise the solid state disks HNS support is required. Change SYS$MANAGER:LOCAL_MOUNT.COM to reflect the disk names and unit numbers. All unit numbers must be unique, for example, disk $1$DIA3: the unit number is 3 and for shadowset DSA4: the unit number is 4. The following is an example of SYS$MANAGER:LOCAL_MOUNT.COM.
$! LOCAL_MOUNT.COM $! $!Insert the Systems actual disk names here $!Note: Each unit number must be unique, this is why the shadowset $! are DSA4 and DSA5 because 4 and 5 are unique unit numbers. $ MOUNT/CLUS/NOASS $1$DIA3: CVAXA_SYS $ MOUNT/CLUS/NOASS $1$DIA5: CVAXB_SYS $ MOUNT/CLUS/NOASS DSA4:/shadow=($1$dia2:,$1$dia1:) user01 user01 $ MOUNT/CLUS/NOASS DSA5:/shadow=($1$dia6:,$1$dia7:) user02 user02 $ MOUNT/CLUS/NOASS $1$DIA0: QUORUM

3.6 System Configuration In the examples in this sections, the system CRUX (a test node at HNS) is used. Edit SYS$SYSTEM:MODPARAMS.DAT to enable Clustering.
3-8

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico DEC Products Installation and Configuration

Change SCSNode so that it reflects the node name: SCSNODE="CVAXA" Change SCSSystemID. This is calculated as follows, as an example CRUX is used: $ MC NCP SHOW NODE CRUX
Node Volatile Summary as of 27-OCT-1993 14:18:21 Node 41.80 (CRUX) State Active Links Delay Circuit ISA-0 Next node 41.50 (DOUGAL)

The system ID is calculated as 41 1024 + 80 = 42064 (where 41 = Area Number, 80 = Node ID) So in Modparams change SCSSYSTEMID to be equal to the value 42064: SCSSYSTEMID=42064 Set VAXCluster to 1 VAXCLUSTER=1 Define the QUORUM disk DISK_QUORUM="$1$DIA0" To make these parameters active type: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK As this saveset is an image backup from an inhouse node, certain startup files contain references to this node name. Search SYS$MANAGER:.COM and SYS$SYSTEM:.DAT for all occurrences of this node name (e.g. CRUX). Change LAT$SYSTARTUP.COM and LTLOAD.COM to refer to CVAXA or CVAXB. Type: $ SEARCH SYS$MANAGER:.COM CRUX
****************************** SYS$SYSROOT:[SYSMGR]LOCAL_MOUNT.COM;18

$ MOUNT/CLUS/NOASS $1$DIA3: CRUX_SYS


****************************** SYS$COMMON:[SYSMGR]LAT$SYSTARTUP.COM;6

$ LCP SET NODE CRUX/ident="CES - Generic VAX 4000 model 100"/NOLOG


3-9

Customer Release Configuration Guide Telecomunicaciones De Mexico DEC Products Installation and Configuration
****************************** SYS$COMMON:[SYSMGR]LTLOAD.COM;2

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

$ LCP SET NODE CRUX/IDENT="CES - Generic VAX 4000 model 100" /NOLOG Change these occurrences to refer to CVAXA or CVAXB with
ident="LES - VAX 4000 model 700A"

NOTE: CVAXA and CVAXB are node names recommended by HNS, but may be different, as may the VAX model, e.g. 4000-100A. 3.7 Preparing for Project Install Before running Projectinstall type: $ SHOW DEV Take note of the Tape and Disk Devices. Then run a project install without restoring the SAVESET, so that DEFSAD and FEPINSTALL are run. Note that running NETCONFIG will disable FEP downloads. During ProjectInstall: change the BAPSYS,BAPV,BAPSW,CESTST UIC numbers so that they are unique within the Cluster. This will prevent problems with trying to access clusterwide locks. During SADREDEF: Do not use NL: as a default device names for Alarm Printers, and FEPSwitches as device protections can cause problems with DECNET. Note MAR$DAT will have to be defined to point to another SHADOWSET. After ProjectInstall. Check that the file ownership of the BAPSYS, BAPSW and CESTST files and directories match the UICs in the Authorize database: $ SET DEF SYS$SYSTEM $ MC AUTHORIZE UAF> SHOW BAP/BRIEF UAF> SHOW CESTST/BRIEF
Owner BAPSYS BAPV Username BAPSW BAPSYS BAPV UIC [126,1] [126,1] [126,3] Account BAPSW BAPSYS BAPV Privs Pri Directory Normal All All 4 LES$DISK0:[BAPSW] 4 LES$DISK0:[BAPSYS] 3 LES$DISK0:[BAPSYS]

UAF> SHOW CESTST/BRIEF Owner CESTST Username CESTST UIC [125,2] Account CESTST Privs Pri Directory All 4 LES$DISK0:[CESTST]

UAF> exit

3-10

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico DEC Products Installation and Configuration

To change file ownership, enter: $ SET FILE SYS$SYSDEVICE:[BAPSYS...]..;./OWNER=[126,1] $ SET FILE SYS$SYSDEVICE:[000000]BAPSYS.DIR/OWNER=[126,1] Note: For a pair of BAPs, the UIC group number (126 in the above example) should be different for each BAP.

3-11

Customer Release Configuration Guide Telecomunicaciones De Mexico

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

3-12

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Chapter 4 LES Software Installation


. This chapter describes the LES software installation procedure as applied to both existing and new systems. The method to be adopted for LES software upgrades is to install on the Standby BAP whilst the Master carries traffic. Prior to the LES software installation, the system must have the correct version of VMS installed and be correctly configured (see chapter 3) and all relevant areas of the system be backed up (see chapter 2). To minimise the system downtime, it is possible to leave the Master running until the moment when the database needs to be converted and the new FEPs are to be loaded. (Section 4.1.4) Refer to any Release Notes for the installation for details of any additional, release specific actions. In summary the installation steps are:1. Preparation a. Save the previous release. See section 2.1. b. Save customer specific files. NOTE:From release 80140, this step will be automated as part of the installation itself. See section 2.2. c. Protect any additional files listed in the Release Notes specific to this installation. d. Archive the Online Database. See section 2.3. e. Dump the Online Database. See sections 2.4 (7.2.1). f. Generate any additional POP files listed in the Release Notes that may be needed in case of fallback. See section 2.5. 2. Install First BAP (non redundant) a. Stop and Deinstall the Standby BAP. See section 4.1.1 b. Install the new software on the stopped BAP (this includes the first pass FEP install). See section 4.1.2 (Not 4.1.2.3). c. Additional post installation actions. See section 4.1.3. 3. Install First SOC
4-1

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

a. Stop and Deinstall one SOC. See section 4.2.1. b. Install the new software on the SOC. See section 4.2.3 (not 4.2.3.1 and 4.2.3.2) 4. Outage a. Start Installation Outage See section 4.1.4. b. Optionally perform DBCC on the Online Database. See section 7.2.2. c. Perform ONDB conversion for options defined in the release notes. See section 7.2.3. d. Start newly upgraded BAP and SOC. See section 8. 5. Check system Ensure system functions correctly (do not move on until agreed that there will be no fall back). See section 4.1.7. 6. Prepare and install second BAP a. Save customer specific files. See section 2.2. b. Protect any additional files listed in the Release Notes specific to this installation. c. Deinstall the second BAP (already stopped). See section 4.1.1 d. Install the second BAP (this includes the second pass FEP install). See section 4.1.2. e. Perform post installation checks. See section 4.1.3. f. Start second BAP. See section 8. 7. Install Other SOC(s) a. Stop and Deinstall other SOC(s). See section 4.2.1. b. Install the other SOC(s). See section 4.2.3 (not 4.2.3.1 and 4.2.3.2) c. Start the other SOC(s) See section 8. 8. Tidy and Backup a. Tidy up & backup disks See section 2.1. b. Archive the Online Database. See section 2.3. c. Dump the Online Database. See sections 2.4 (7.2.1). The above is a summary representing a normal installation of a new release on an existing system. In all cases, when performing installations, specific directions given in the release notes which will accompany the release software, take precedence over any directions stated in this guide. The release notes must be followed at all times.
4-2

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

NOTE: The VMS and Sybase product installations must have been performed before any LES software is installed on a new system. This can be assumed when installing new software on an existing system. 4.1 BAP Installation This section describes the installation of LES software on the BAP. If this is the first time the LES software is being installed on the system, then skip the following section and continue from section 4.1.2. 4.1.1 Deinstallation of Existing BAP Log into the operational account (BAPSYS) on the BAP where the LES software is to be installed. Check if the system is currently running by entering: $ BAPOP SHOW BAP which produces a display such as the following:
BAP version Rel80000 from disk $1$DIA4: The Current State of the BAP is :STARTED The Current Processor Mode is :STANDBY The Current Processor State is :RUNNING Show Active BAP Processes <Y/[N]>: <N> 02-NOV-1996 10:40:51.81

Make a note of the BAP version. In response to the prompt Show Active BAP Processes <Y/[N]> enter <N>. If the current state of the BAP is STARTED then you must stop the BAP. If this BAP is a member of a redundant pair and its processor mode is MASTER, then this system is currently available for carrying traffic. Either install the Standby BAP first or perform a BAP switchover as detailed in reference [1]. In order to minimise outages and switchovers, it is always preferable to perform the first installation on the standby (or idle) BAP. At this point broadcast a message to all other users warning them about the impending installation: $ REPLY/ALL/BELL/SHUTDOWN "LES software installation - please logoff now." To stop the existing software running on the BAP enter: $ BAPOP STOP BAP The following will then be displayed:

4-3

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

-------------------------------------------------------------------------------Stopping the BAP -------------------------------------------------------------------------------... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... forcexed forcexed stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped stopped forcexed forcexed process process process process process process process process process process process process process process process process process process process process process process process process process process process process process process process process process PRC_EVENT_MO_01 XCCC_P_01 APM_P_01 DIM_LINK_MGR_02 DIM_LINK_MGR_03 ERRLOG_01 MC_LOGGER_P_01 PRC_HANDSHAK_01 PRC_PROC_STA_01 PRC_TASK_STA_01 CUC_BAP_MSD__01 DCD_MGR_P_01 DIM_LINK_MGR_01 DIM_LINK_MGR_04 EM_P_01 FAXCC_DRIVER_01 FCR_BAP_CONN_01 FDCD_EXT_MGR_01 FDCD_EXT_MGR_02 FDCD_EXT_MGR_03 FDCD_EXT_MGR_04 FEH_BAP_MAIN_01 IC_BAP_MSD_P_01 LFM_FILE_SER_01 MDIR_P_01 RG_P_01 SDC_MAIN_P_01 SM_P_01 TACC_DRIVER__01 TOKM_P_01 PADR_MAIN_P_01 PRC_ARB_01 PIPM_ATL

-------------------------------------------------------------------------------Process# 2740055F 274007B1 274006D6 Process Name BAPSYS_01 BAPSYS_02 BAPSYS_14 Terminal LTA49: OPA0: LTA35: Image [SYSEXE]RTPAD.EXE [N]: <> [N]: <> [N]: <>

2740084F BAPSYS_01 LTA48: Stop BAPSYS_02 (Y)es, (N)o, (A)ll, (S)how, (Q)uit 274007B1 BAPSYS_02 OPA0: Stop BAPSYS_03 (Y)es, (N)o, (A)ll, (S)how, (Q)uit 274006D6 BAPSYS_14 LTA35: [SYSEXE]RTPAD.EXE Stop BAPSYS_14 (Y)es, (N)o, (A)ll, (S)how, (Q)uit

If there are processes which are running testers, for example MCM_TESTER_P, these must also be stopped, the responses above would therefore be Y. Wait until the command line prompt appears again after the list of stopped processes. The procedure will continue to force the images running in the processes to exit until the processes have terminated. If the procedure appears to come to a stop then break out using Control-C or Control-Y and try again. You must complete this step successfully before proceeding. Now ensure that all other operators have logged off by entering: $ SHOW USERS/FULL/NODE Only the account (BAPSYS) should be logged in. If not give a final warning as above and
4-4

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

then for each process enter (take note of which operator you are by typing Control-T): $ STOP (PROCESS NAME) This will not work for other users who are not in the same group as the operational account. To force these users to logout use: $ STOP/ID=(PROCESS ID) Next the installed images must be de-installed. HNS recommends that the DEINSTALLBAP procedure is run three times consecutively. This ensures that all relevant images have been deinstalled. Run the procedure by entering: $ DEINSTALLBAP The following will be displayed whilst the installed images are deinstalled:
-------------------------------------------------------------------------------Deleting BAP global sections -------------------------------------------------------------------------------... BAP global sections deleted -------------------------------------------------------------------------------Deinstalling BAP images -------------------------------------------------------------------------------... deinstalling CDMC ... deinstalling DIM_LINK_MGR_P ... deinstalling DIM_SHARE ... deinstalling ERR ... deinstalling ERRMC ... deinstalling MC_MC_IF ... deinstalling NRA ... deinstalling SAD_BAP_IMAGE_P ... deinstalling SAD_SHARE ... deinstalling SDC_CONFIG_DB ... deinstalling UTL ... deinstalling UTLDATA %DELETE-W-FILNOTDEL, error deleting DSA3:[BAPSYS.INSTALL]UTLDATA125.EXE;1 -RMS-E-FLK, file currently locked by another user ... deinstalling UTLTRCFLG ... BAP images deinstalled

It is possible that during this procedure errors referring to installed images still being in use can appear. If such a message appears ensure that the relevant file is deleted from the area defined by the logical BAP$INS: $ DELETE BAP$INS:.;/LOG The de-installation of the installed images should result in all the files in the BAP$INS area being deleted. If files remain in this area they will have no detrimental effect upon any subsequent system startup. Issuing the above DELETE command only deletes copies of the originals which are held with the rest of the LES software. If any files cannot be deleted then they still have a real reference most likely from a remaining user logged onto the system using a test program. In this case they must be logged off before the installed image file can be deleted. To determine which process has a reference to this file enter: $ SHOW DEVICE/FILES
4-5

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

You can then use the STOP/ID command above to force them to logout. Now enter the following: $ SHOW LOGICAL REL Make a note of the values of the logicals BAP$REL_DISK and BAP$REL_NAME, you will need them later. The first is the disk where the existing software is installed - you should install the new software on the same disk. The second is the release number for that software. Then enter: $ SHOW LOGICAL RUN Make a note of the value of the logical BAP$RUN_DISK as above. This is the disk where the operational accounts areas are held. In most cases this will be the same disk as the disk holding the software, but there may be exceptions. The deletion of COMDEV files has now been automated following release 80140. Consequently the actions listed below for manual deletion can now be omitted NOTE: COMDEV directories tend to contain emergency bug-fixes (if any), and the PIPM_NETWORK_SETUP.DAT file. The PIPM file will be recreated on the first login after the installation. Deassign group images: $ DEASSIGN/GROUP/ALL Now logout of the operational account by entering: $ LOGOUT NOTE: Check whether the four digit release number of the new software matches that of the the first four digits of the current software. This was noted when entering the BAPOP SHOW BAP command described above. If the numbers are the same then the existing software baseline will be automatically replaced during the new software installation. If this is the case skip the rest of this section and continue from section 4.1.2. In previous versions of this document, the opertator was required at this point to logon as SYSTEM and delete the previous version of the release (for full installations). From release 80140, this should be left to the automated installation process, where these files will be deleted after the automated protection of the customer specific files. 4.1.2 Installation of New BAP If this is a full BAP software installation then certain hardware and software configuration information should be obtained prior to performing the installation. If this is not possible then the installation can be performed and the configuration information setup later (see section 4.1.6). Following release 80140, much of this information gathering is now automatic. A minimum amount of information must be obtained before the installation can take place. This includes: Project name - this is always CES and is now not required to be entered.
4-6

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

Processor name - this is BAP, PROJECTINSTALL now detects the processor type and automatically applies this. Release number - this should be marked on the tape and should be included in the release notes provided with the release. The number must contain four digits, e.g. 8011. This information can now be obtained automatically from either: The release tape label if already inserted in the appropriate drive. The directory name if the source file location is on disk. The number determined in this way is offered as the default, and may be ignored if neccessary. Location of release software - this will usually be the tape drive device name, but it may also be a disk device either locally or on a remote machine. The following formats are allowed: Mmcu: - tape device name, e.g. MKA500: Disk:[path] - local disk device name, e.g. LES$DISK0 - if the path is omitted the default will be one [CES.RELnnnn], e.g. [CES.REL8011] remote disk device name, e.g. node::$a$Ddcu:[path] EARTH::$1$DUA0: - if the path is omitted the default will be [CES.RELnnnn], e.g. [CES.REL8011] (Note: for this to work a proxy login of the form ::account/DEFAULT must exist on the remote node where the account is the same as the account you will be using to do the installation on the target machine. Currently the installation procedures do not support access control strings.) A list of currently available drives will be presented. In the case where only one drive is available, then this will be offered as the default. If a disk location is specified, then this will be searched for any installation files. In this case, a list of all (if any) valid releases will be offered for selection. Location of installed software - this will usually be the local system disk device name, but it could be another local disk. Format is $a$Ddcu:, e.g. $1$DIA0:. The disk currently used will be offered as default. This is usually LES$DISK0 Account group numbers - there are four accounts created by a new software installation. They are arranged in two groups with two accounts in each group. These groups must not be the same as any existing account groups. Suggested group numbers are 126 and 127. For more details see Appendix A. From Release 80140, it will no longer be neccessary to verify the details for each account. The default is to accept them all unchanged. In the rare instance that a change is required, then each account will be presented, in turn, for verification. NOTE: When installing the LES software on two BAPs in a cluster which are intended for
4-7

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

redundant operation, ensure that the group number of the operational account on each BAP is different from the group number of the operational account on the other BAP. This must be done to prevent deadlocks caused by clashing cluster wide locks. This can be simply achieved by allocating two group numbers for the operational/captive accounts and the system/maintenance accounts, and then using them one way round on one BAP and the opposite way round on the other BAP. 4.1.2.1 BAP system information for new installations only Other hardware and software configuration information can be specified during installation or alternatively it can be specified prior to system startup (see section 4.1.6). Some of this information is obtained from answers to questions put to you during the installation procedure. This information includes: Release number and location of installed software. Names of logical processor and Pipe Manager network. Device names of disks, tapes and the Arbiter port. Printer devices and printer queue names. Channel unit switch port names. Telex interface switch port names. DEMSA switch port names. BAP node names. Ocean region service states and LES numbers. Channel unit controller node names. Telex interface controller node names. SOC node names. DEMSA pair names. DEMSA node names. X25 interface characteristics. Kermit interface characteristics. If you intend to supply this information during the installation procedure then you should collect the information on a configuration sheet such as that shown in section 4.1.8. For guidance see the example in section 4.1.9. If you intend to supply this information after the installation then it is possible to enter null values during the procedure and then you can then supply the real values later (see section 4.1.6).

4-8

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

4.1.2.2 BAP system information for exisiting installations The majority of the required information listed in the previous section does not normally change from one release to another. However the release number usually does need updating. It is this change which neccesitates the re-running of the SADREDEF utility. From release 80140, this update can be performed without further intervention from the operator other than confirmation that no additional manual changes are to be made. Installation from TAPE: The tape should now load into the drive. If the tape drive unit has load/unload or online controls ensure that the tape is loaded and that the tape drive is online to allow it to be controlled by the computer. Now login to the SYSTEM account (if not already). To find out the name of the local tape drive name enter: $ SHOW DEVICE MK the resulting display should look like:
Device Name MARS$"MKA500:" Device Status Online Error Count Volume Label 0 Free Trans Mnt Blocks Count Cnt

No action is required if the released software is on disk except that you could check that the disk is mounted and available for use. Now enter the following: $ SET DEFAULT SYS$MANAGER Then enter the following if loading from a local tape device: $ BACKUP/NEW/LOG (TAPE):PROJINSTALL.SAV Or one of the following, if the saveset is on disk: $ BACKUP/NEW/LOG (DISK):[CES.RELnnnn]PROJINSTALL.SAV/SAV Local disk save set where nnnn is the new release number. $ BACKUP/NEW/LOG (NODE)::(DISK):[CES.RELnnnn]PROJINSTALL.SAV/SAV Remote disk save set where nnnn is the new release number. In all cases ensure that there is a space immediately preceding the asterisk (). The /NEW qualifier must be included in the backup command to ensure the files are created in the directory with version numbers higher than any existing files. The following files will be created in the default area: SYS$SYSROOT:[SYSMGR]PROJECTINSTALL.COM SYS$SYSROOT:[SYSMGR]BAPINSTALL.COM SYS$SYSROOT:[SYSMGR]CESINSTALL.COM
4-9

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

SYS$SYSROOT:[SYSMGR]FEPINSTALL.COM SYS$SYSROOT:[SYSMGR]SOCINSTALL.COM Then purge: $ PURGE/LOG To initiate the installation procedure enter: $ @PROJECTINSTALL It is assumed that this is NOT a first time installation (this would normally be performed by HNS Staff). However where appropriate, details for an initial installation are described. <N> is sometimes used where <> will suffice in order to show the options available.
Enter disk/tape (e.g., LES$DISK0, MKA500, <System>::<Disk Device> ) where release software resides: [MKA500:] <> -- Should be the location of the PROJINSTALL.SAV saveset. See System Manager for this info. -- for tape save sets, it is the tape logical unit, for disk save sets, it is the -- pathname of the directory. If more than one tape drive is available -- then these will be presetned as a list before the question above. -- Note: Include the Node Name but NOT the Access Control String. -----------------------------------------------------------------------------Checking for correct tape in MKA500:: now %MOUNT-I-WRITELOCK, volume is write locked %MOUNT-I-MOUNTED, R8013 mounted on MKA500:: Is 8888 correct Enter return to accept, Q to quit or correct release Release number 8013 <> -- The source file location specified in the previous step is now searched for -- the release number. In the case of a tape, this is obtained from the label. -- Or, from disk, the directory name(s) in the [CES.REL8nnn] format. The default -- thus obtained may be overwritten if required. In this case, you will be asked -- to confirm the alteration. -----------------------------------------------------------------------------Copying files for protection (where they exist) to les$disk0:[PROTECTED.Pre_REL8013] -- Files to be protected are now copied from their normal, working locations to -- the above named release specific directory. One such file is shown in the -- example below. The file names are taken from SAD$EXE:SAD_PROTECT_FILES.DAT -- This file is updated with every release. However, as this too is subject to -- protection any locally made additions to this list will be handled in the -- same way as for the other protected files. -----------------------------------------------------------------------------%COPY-S-COPIED, $1$DIA4:[BAPSW.REL8013.SAD.EXECUTE]SAD_PROTECT_FILES.DAT;13 copied to $1$DIA4:[PROTECTED.PRE_REL8013]SAD_PROTECT_FILES.DAT;18 (6 blocks) " " " " ------------------------------------------------------------------------------

4-10

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

Reusable files have been saved to les$disk0:[PROTECTED.Pre_REL8013] -- If any files listed as being potentially due for protection were not -- found, then they will be listed now. In all probablilty any such files -- listed will not be applicable for this installation. However the operator -- should verify that this is the case, though it is very unlikely that a -- file will exist (in the correct location and yet not be found. It is -- possible though that it may have been renamed at some time. -- The files listed below are purely for illustration. ) LES$DISK0:[BAPSW.REL8013.SOI.EXECUTE]SOI_CNTL_FLAG.INI LES$DISK0:[BAPSW.REL8013.BM.EXECUTE]BM_AHK_CONFIG.DAT LES$DISK0:[BAPSW.REL8013.INT.EXECUTE]INT_DITCH_MRN.COM LES$DISK0:[BAPSW.REL8013.INT.EXECUTE]INT_RWAST_DETECTOR.COM The above files, listed in MISSING_PROTECT_FILES.TXT, have not been saved. Verify that none apply to this installation before continuing Enter C to continue when ready, or A to abort or anything else to re-display <C> -- As a precaution against failing to copy a required file, a list of files which -- were not copied is presented for inspection. NOTE, that since the list of -- files to protect is generic, then it may be expected that some files will -- appear here as they will not all be applicable to every customer site. The -- presence of files not found, is not an indication of an error. -- If an error is suspected, then the installation may be aborted at this point. -----------------------------------------------------------------------------Current BAP release 8012 is being superceded by 8013 copied from MKA500: -- Confirmation of the release to be installed Enter disk on which release is to be installed (e.g., LES$DISK0): <LES$DISK0> -- Should be the value of the logical name BAP$REL_DISK. -- See System Manager to find out the name of the system disk -- NOTE: Please ensure that the correct location is given. Some -- BAPs may not be defined in terms of LES$DISK0 -------------------------------------------------------------------------------Checking existence of processor system account --------------------------------------------------------------------------------- This account is required by PROJECTINSTALL and is created if it -- does not already exist. ... BAPSW account exists - UIC = [125,1] -- If the account does not exist then the user is prompted -- for account group and member number. -------------------------------------------------------------------------------Backing up release software -------------------------------------------------------------------------------*** Backing up release from MKA500::BAPSW.SAV to $1$DIA0:[BAPSW.REL8011...] Continue? ([Y]/N/S(kipBackup)): <> -- The operator is now offered the choice of deleting the old release. In the case -- where the old and new release numbers are the same then this is brought to the -- operators notice. If this is a re-installation on top of existing s/w, then -- it may be preferable to delete the previous installation first. If this is an -- EBF installation then the previous release will almost certainly need to be -- kept. Normally, however, this question will not arise. As the files for -- protection will now have been saved, then it is safe to delete the old release. The new and old release numbers are the same. This may indicate that this is an EBF installation so you may not want to delete the existing software.

4-11

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Delete old rel 8013 on this node PHACT ? Y/N Please confirm it is OK to delete current installation files NOW Y/N : y ... deleting any existing release 8011 software ... backing up release 8011 software %BACKUP-S-CREDIR, created directory $1$DIA0:[BAPSW.REL8011.<component>.EXECUTE] %BACKUP-S-CREATED, created $1$DIA0:[BAPSW.REL8011.<component>.EXECUTE]<file> : : : : : : : : : %BACKUP-S-CREDIR, created directory $1$DIA0:[BAPSW.REL8011.<component>.EXECUTE] %BACKUP-S-CREATED, created $1$DIA0:[BAPSW.REL8011.<component>.EXECUTE]<file> : : : : : : : : : %BACKUP-S-CREDIR, created directory $1$DIA0:[BAPSW.REL8011.000000] %BACKUP-S-CREATED, created $1$DIA0:[BAPSW.REL8011.000000]BASELINE.DAT;1 -------------------------------------------------------------------------------Copying VAX definition files to SYS$MANAGER -------------------------------------------------------------------------------%BACKUP-S-CREATED, created SYS$SYSROOT:[SYSMGR]SADSTARTUP.COM;15 Do you want to reuse all existing CES accounts ? ([Y]/N): <> -- Under normal circumstances, Y is the correct response. -- Prior to 80140, the operator would have had to signify acceptance of all -- parameters for each individual account. Now they can be accepted in bulk. In -- this case, the sequence of events resumes at " Defining VAX devices " below. -- The intervening examples are only now accessed if N is entered and should normally be ignored. -------------------------------------------------------------------------------Defining CES operational account to be used -------------------------------------------------------------------------------Do you want to reuse an existing operational CES account? ([Y]/N): <> -- This depends whether it is a new system or an upgrade, -- Reply N if it is a new system, Y if it is an upgrade. Enter disk device of existing CES account [LES$DISK0:]: <> -- Should be the value of the logical name BAP$RUN_DISK. -- Under normal conditions this is the system disk Enter name of existing CES account [BAPSYS]: <> -- Can be anything but BAPSYS is the standard. If a new account is specified, the -- installer is also prompted for the accounts group and member number. -------------------------------------------------------------------------------Defining CES maintenance account to be used -------------------------------------------------------------------------------Do you want to reuse an existing maintenance CES account? ([Y]/N): <> -- This depends whether it is a new system or an upgrade. -- Reply N if it is a new system, Y if it is an upgrade. Enter name of existing CES account [CESTST]: <> -- Can be anything but CESTST is the standard. -- If a new CES account is specified then the installer -- is prompted for the accounts member number.

-------------------------------------------------------------------------------Defining CES captive account to be used --------------------------------------------------------------------------------- This is the captive account on the BAP that is used for running the SOC VIEWER. -- Whether you will be using a new account or not, the account name MUST be BAPV -- or the SOC VIEWER will NOT work.

4-12

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

Do you want to reuse an existing captive CES account? ([Y]/N): <> -- This depends whether it is a new system or an upgrade -- Reply N if it is a new system, Y if it is an upgrade Enter name of new CES account [BAPV]: <> -- This MUST be BAPV -- If a new CES captive account is specified then the installer -- is prompted for the accounts member number. -------------------------------------------------------------------------------Defining VAX devices --------------------------------------------------------------------------------------------------------------------------------------------------------------Defining BAP parameters --------------------------------------------------------------------------------- The following question (defaulted to YES) in order to force the creation of a -- new DEFSAD.COM using the new parameters. From release 80140 the insertion of -- these parameters is now fully automatic and the installation process resumes, -- after first displaying a list of the automated updates, at -- "Creating CES definition file SYS$LOGIN:DEFSAD.COM " below. -- In some circumstances, though the majority of these parameters will all be -- correct for the new release, some manual changes may be required. In this case -- enter N for manual update, and correct those entries which require change. -- DEFSAD.COM will now contain a logical defining the load file type for each --CU FEP. Consequently SADREDEF will need to be run to enter these definitions -- the first time an 8014 release is installed. The system logicals can be automatically updated for this release using information already available If non-routine changes are required then the logicals should be updated manually, accepting all other defaults offered. Refer to the release notes Under normal circumstances, automatic update is recommended Do you wish to accept automatic updates alone Y/N? [Y] <> -- The normally required response has been shown. In which case the updated DEFSAD -- information will be displayed, as is listed below, but without pausing for operator responses. When prompted for input, enter data according to the configuration you require. Some prompts display a default reply [shown in brackets]. To use the default, press the RETURN key. To replace default data, enter the new data to be used. To cancel the use of default data without entering new data, enter the backslash (\) character. You will have the opportunity to review and correct your responses before actually creating DEFSAD.COM. RELEASE: Release Number: Release Disk : 8011 LES$DISK0:

* Is this information correct? (Y/N) [Y]: <> NAMES: Processor Name: Current Region: BAPB ATLANTIC

* Is this information correct? (Y/N) [Y]: <> CONFIGURATION: System Size : SMALL

4-13

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


MCM Ast Length: MCM Ast Usable: 200 160

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

* Is this information correct? (Y/N) [Y]: <> DEVICES: Arbiter Device Shadow set 1 Shadow set 1 Disk Shadow set 1 Disk Shadow Set 2 Shadow set 2 Disk Shadow set 2 Disk MAR File disk Quorum Disk OFDB Disk Cartridge Tape: Spool Tape : UTC Device : : : : : : : : : : : LTA2: DSA1: $1$DIA1: $1$DIA5: DSA2: $1$DIA2: $1$DIA6: DSA2: $1$DIA3: $1$DIA3: MKA500: MKA500: UNKNOWN

1 2 1 2

* Is this information correct? (Y/N) [Y]:<> PRINTERS: Alarm Printer 1 Alarm Printer 2 Alarm Printer 3 Alarm Printer 4 Alarm Printer 5 Alarm Printer 6 Alarm Printer 7 Alarm Printer 8 Alarm Printer 9 Offline Report Queue Online Report Queue : : : : : : : : : : : LTA1: LTA2: UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED REPORT$PRINTER UNDEFINED

* Is this information correct? (Y/N) [Y]: <> CHANNEL UNIT SWITCHES: CUC1 CUC2 CUC3 CUC4 Switch: Switch: Switch: Switch: UNDEFINED TXA2: UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <> TELEX INTERFACE SWITCHES: TIC1 TIC2 TIC3 TIC4 TIC5 TIC6 COB1 Switch: Switch: Switch: Switch: Switch: Switch: Switch: UNDEFINED UNDEFINED TXA4: UNDEFINED UNDEFINED UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <> DEMSA SWITCHES: DEMSA DEMSA DEMSA DEMSA 1 2 3 4 Switch: Switch: Switch: Switch: TXA1: UNDEFINED UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <> BACKGROUND APPLICATIONS PROCESSORS: BAPA: CBAPA Service State: IN_SERVICE

4-14

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


BAPB: CBAPB Service State:

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


IN_SERVICE

* Is this information correct? (Y/N) [Y]: <> OCEAN REGIONS: WEST ATLANTIC PACIFIC INDIAN Ocean Ocean Ocean Ocean Region Region Region Region Service Service Service Service State: State: State: State: OUT_OF_SERVICE IN_SERVICE OUT_OF_SERVICE OUT_OF_SERVICE LES LES LES LES Number: Number: Number: Number: 44 3 44 44

* Is this information correct? (Y/N) [Y]: <> CHANNEL UNIT CONTROLLERS: ATLANTIC: CUC2A: CUC2B:

FEPSD4 FEPSD3

Service State: Service State:

IN_SERVICE Load file type: 90 IN_SERVICE Load file type: 95

* Is this information correct? (Y/N) [Y]: <> TELEX INTERFACE CONTROLLERS: TIC1A: TIC1B: TIC2A: TIC2B: TIC3A: TIC3B: TIC4A: TIC4B: TIC5A: TIC5B: TIC6A: TIC6B: UNDEFINED UNDEFINED UNDEFINED UNDEFINED FEPSE3 FEPIO3 UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED Service Service Service Service Service Service Service Service Service Service Service Service State: State: State: State: State: State: State: State: State: State: State: State: UNDEFINED UNDEFINED UNDEFINED UNDEFINED IN_SERVICE IN_SERVICE UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <> SYSTEM OPERATOR CONSOLES: SOC1A: SOC1B: SOC2A: SOC2B: SOC1A SOC1B UNDEFINED UNDEFINED Service Service Service Service State: State: State: State: IN_SERVICE IN_SERVICE UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <> DEMSA PAIR NAMES: DEMSA DEMSA DEMSA DEMSA 1 2 3 4 Pair: Pair: Pair: Pair: DOUGAL UNDEFINED UNDEFINED UNDEFINED Switch Switch Switch Switch Setting: Setting: Setting: Setting: A A A A

* Is this information correct? (Y/N) [Y]: <> DEMSA NODE NAMES: DEMSA DEMSA DEMSA DEMSA DEMSA DEMSA DEMSA DEMSA 1A: 1B: 2A: 2B: 3A: 3B: 4A: 4B: EDONIS WASAT UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED Service Service Service Service Service Service Service Service State: State: State: State: State: State: State: State: IN_SERVICE IN_SERVICE UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <> PSDN INTERFACE: X.25 Destination Name : X25LES

4-15

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


X.400 Destination Name: X.25 Low Sub-Address : X.25 High Sub-Address : X.400 Sub-Address : DEMSA Poll Timer : PSI Network : PSI DEMSA Pair Number : LES DTE Address : X25 Line Fail Retry : X400LES 25 27 28 60.0 HNS_B 1 399922117000 10

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

* Is this information correct? (Y/N) [Y]: <> KERMIT INTERFACE: Maximum Packet Size : Number of Pad Characters: Pad Character : Control Prefix Character: Binary Prefix Character : End of Line Character : Number of Retries : Timeout : 80 0 32 (" ") 35 ("#") 38 ("&") 13 3 60

* Is this information correct? (Y/N) [Y]: <> -------------------------------------------------------------------------------Creating CES definition file SYS$LOGIN:DEFSAD.COM --------------------------------------------------------------------------------------------------------------------------------------------------------------Creating CES report file SYS$LOGIN:CONFIGURATION.TXT -------------------------------------------------------------------------------*** BAP parameter definition complete -------------------------------------------------------------------------------Copying X25 PSI/X29 System Template definition file to SYS$MANAGER -------------------------------------------------------------------------------%BACKUP-S-CREATED, created SYS$SYSROOT:[SYSMGR]PSI$X29_SYSTEM_TEMPLATE.COM;35 -------------------------------------------------------------------------------Copying Sybase command files to target directories. -------------------------------------------------------------------------------%BACKUP-S-CREATED, created SYBASE_491:[SYBASE.UTILS]STOP_SYBASE_SERVER.COM;40 %UAF-I-LSTMSG1, writing listing file %UAF-I-LSTMSG2, listing file SYSUAF.LIS complete %BACKUP-S-CREATED, created $1$DIA4:[SYBASE_491.SYBASE]SYBASE_LOG_DIAG.COM;40 %UAF-I-LSTMSG1, writing listing file %UAF-I-LSTMSG2, listing file SYSUAF.LIS complete %BACKUP-S-CREATED, created $1$DIA4:[CBAPSYS]STOP_ONDB_NOWAIT.COM;40 %UAF-I-LSTMSG1, writing listing file %UAF-I-LSTMSG2, listing file SYSUAF.LIS complete %BACKUP-S-CREATED, created $1$DIA4:[CBAPSYS]FAIL_BAP.COM;40 -- With release 80140, a change was made in the way that the FEP load file are -- defined. Logicals are now used with the result that these need never be -- redefined again, as the logical location is true for all releases. The NCP -- database will be searched. If all load files are found to be in terms of -- logicals, then the operator will be informed that NO redefinition will be -- required and the default response of N may safely be entered. Installation -- will now resume at the reboot question. However, if any non-logicals are -- found, then redefinition will be required. FEP names and load file types are -- now extracted from DEFSAD.COM and suplied as defaults, where known. ** Start of FEP Installation Procedure.

4-16

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


-- EITHER

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

All CURRENT FEP load files are defined in terms of the logical directory name - FELNSYS$EXE - containing the load files Redefinition is only required when adding or changing FEP types -- OR the following will be seen At least one FEP load file is defined using the full directory path name, such as $1$diax:[BAPSW.REL80nn.FELNSYS.EXECUTE]FEP_XXX.SYS This will need to be redefined for a new installation Do you want to change FEP loadfiles (FEPINSTALL.COM) (Y/[N]) ?: N -------------------------------------------------------------------------------Invoking FEP specific installation procedure --------------------------------------------------------------------------------

...Creating file BAP$SYSTEM:[8011.FELNSYS.EXECUTE]INSTALLFEP.COM Configure VMS host for downline loading ? This only needs to be done after a fresh installation of VMS. [N]: <> -- Each defined FEP name, type and load file will be presented -- in turn with the applicable responses supplied as default. -- When the known list is exhausted, then the FEP name will be shown -- as undefined. At this point further FEPs may be added - though -- these should heve been defined in DEFSAD prior to this - or Q -- entered to quit. -- The default naming convention uses logical name, Enter Node Name of FEP to be configured (Q when finished [MECU4A] : <> Has MECU4A been used before on this System ? (Y/N/Q) [Y]: Y -- The FEP names need ordinarily only be entered -- during an initial installation. Is MECU4A a C(hannel) Unit FEP or T(elex) FEP or Q(uit) [C] ?: Is MECU4A a RTVAX1000 (1000), a VAX3100-80 (80), VAX3100-85 (85) or VAX3100-95 (95) FEP or Q(uit) [80 ?: Remote node = MECU4A Load file = FELNSYS$EXE:FEP_MAIN_P.SYS_80 Is this correct ? (Y/N/Q) [Y]: <> -- If N is entered, then the automatic choice can be -- overwritten. However, this will not be accepted if the file -- cannot be found. -- Under normal circumstances re-triggering - via this com file - will not -- be required as the automated installation process will re-trigger these -- just before the new , first pass, BAP is to be started Trigger FEP MECU4A to load FEP Software ? (Y/N) [N]: <> Enter Node Name of FEP to be configured (CR when finished): <> $!********************************************************** $!* BAP$SYSTEM:[REL8011.FELNSYS.EXECUTE]INSTALLFEP.COM $!* Generated by FEPINSTALL.COM at 17-JAN-1996 15:54:03.52 $!********************************************************** $ mcr ncp !FEP MECU4A Characteristics DEF NODE MECU4A ADDRESS 41.305 SERVICE CIRCUIT SVA-0 DEF NODE MECU4A HARDWARE ADDRESS 08-00-2B-94-C1-F3 DEF NODE MECU4A ACCESS BOTH SET NODE MECU4A ALL

4-17

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


! !Node MECU4A load file DEF NODE MECU4A LOAD FILE FELNSYS$EXE:FEP_MAIN_P.SYS_80 SET NODE MECU4A ALL ! ! Trigger MECU4A TRIGGER NODE MECU4A ! exit $exit -- Always answer the following question with Y for second pass -- and Y for first pass if the intention is to start the newly -- installed BAP as soon as possible. -- Other wise enter N and the FEPS will need to be installed -and -- triggered- manually after first pass immediately before BAP start

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Run file BAP$SYSTEM:[REL8011.FELNSYS.EXECUTE]INSTALLFEP.COM ? (Y/N) [N]: <Y> <N>(delayed first pass) -- Replying Y will cause the above file to be run. ** End of FEP Installation Procedure *** BAP specific installation of release 8011 complete

-------------------------------------------------------------------------------HNS strongly recommends that the processors are rebooted to clear out system/group logicals and global symbols. -------------------------------------------------------------------------------Do you want to reboot the BAP processor? ([Y]/N): Y *** PROJECTINSTALL of BAP release 8011 complete -------------------------------------------------------------------------------Invoking AUTOGEN to set system parameters and reboot the system -------------------------------------------------------------------------------%AUTOGEN-I-BEGIN, GETDATA phase is beginning. %AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created. You may wish to purge this file. %AUTOGEN-I-END, GETDATA phase has successfully completed. %AUTOGEN-I-BEGIN, GENPARAMS phase is beginning. %AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created. You may wish to purge this file. %AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created. You may wish to purge this file. %AUTOGEN-I-END, GENPARAMS phase has successfully completed. %AUTOGEN-I-BEGIN, GENFILES phase is beginning. ****************** %AUTOGEN-W-REPORT, Warnings were detected by AUTOGEN. Please review the information given in the file SYS$SYSTEM:AGEN$PARAMS.REPORT ****************** %AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages which have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You may wish to review the information in that file. %AUTOGEN-I-END, GENFILES phase has successfully completed. %AUTOGEN-I-BEGIN, SETPARAMS phase is beginning. %AUTOGEN-I-END, SETPARAMS phase has successfully completed. %AUTOGEN-I-BEGIN, REBOOT phase is beginning. The system is shutting down to allow the system to boot with the generated site-specific parameters and installed images. The system will automatically reboot after the shutdown and the

4-18

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


upgrade will be complete.

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

SHUTDOWN -- Perform an Orderly System Shutdown on node VEGA %SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check... %SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed %SHUTDOWN-I-OPERATOR, This terminal is now an operators console. %%%%%%%%%%% OPCOM 17-JAN-1996 16:00:20.90 %%%%%%%%%%% Operator _VEGA$RTA1: has been enabled, username SYSTEM %%%%%%%%%%% OPCOM 17-JAN-1996 16:00:20.92 %%%%%%%%%%% Operator status for operator _VEGA$RTA1: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled. %SET-I-INTSET, login interactive limit = 0, current interactive value = 2 %SHUTDOWN-I-SHUTNET, The DECnet network will now be shut down. %SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped. SHUTDOWN message on VEGA from user SYSTEM at _VEGA$RTA1: 16:00:24 VEGA will shut down in 0 minutes; back up soon. Please log off node VEGA. Reboot system with AUTOGENerated parameters %SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked. 3 terminals have been notified on VEGA. %SHUTDOWN-I-STOPUSER, All user processes will now be stopped. %SHUTDOWN-I-REMOVE, All installed images will now be removed. %SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted. %SHUTDOWN-I-STOPAUDIT, stopping the audit server %%%%%%%%%%% OPCOM 17-JAN-1996 16:00:35.62 %%%%%%%%%%% Message from user SYSTEM on VEGA _VEGA$RTA1:, VEGA shutdown was requested by the operator. %%%%%%%%%%% OPCOM 17-JAN-1996 16:00:35.83 %%%%%%%%%%% Logfile was closed by operator _VEGA$RTA1: Logfile was VEGA::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;144 %%%%%%%%%%% OPCOM 17-JAN-1996 16:00:36.04 %%%%%%%%%%% Operator _VEGA$RTA1: has been disabled, username SYSTEM

4.1.2.3 Problems during an initial BAP installation Unlike an upgrade, an initial installation invokes AUTOGEN to set system parameters prior to the final reboot. If any problems are encountered, then instead of rebooting the system displays the message: NOTE: The following message may appear instead of those above:
-------------------------------------------------------------------------------AUTOGEN detected errors with the system parameters specified in the file SYS$SYSTEM:MODPARAMS.DAT. A report detailing these problems follows. --------------------------------------------------------------------------------

followed by a page by page report such as:


AUTOGEN Parameter Calculation Report on node: MARS This information was generated at 6-MAR-1992 14:41:45.82 AUTOGEN was run from GETDATA to REBOOT using NOFEEDBACK Processing Parameter Data files ------------------------------Including parameters from: SYS$SYSTEM:MODPARAMS.DAT This run of AUTOGEN is *NOT* based on FEEDBACK information. The resulting calculations may not be representative of your workload. DIGITAL recommends the use of feedback to adjust system resources to match system workloads.

4-19

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


Parameter information follows: ------------------------------

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

VIRTUALPAGECNT parameter information: Override Information - parameter calculation has been overriden. The calculated value was 139072. The new value is 150000. VIRTUALPAGECNT has been disabled by a hard-coded value of 150000. Information on VMS executable image Processing: ** ERROR ** - The file SYS$MANAGER:VMS$IMAGES_MASTER.DAT was not found. AUTOGEN will *NOT* be able to create VMSIMAGES.DAT. Please correct this problem before rebooting your system. Endphase has been changed to TESTFILES GBLPAGFIL parameter information: Override Information - parameter calculation has been overriden. The calculated value was 1024. The new value is 20000. GBLPAGFIL is not allowed to be less than 20000. GBLPAGES parameter information: Override Information - parameter calculation has been overriden. The calculated value was 31200. The new value is 120000. GBLPAGES is not allowed to be less than 120000. GBLSECTIONS parameter information: Override Information - parameter calculation has been overriden. The calculated value was 230. The new value is 900. GBLSECTIONS is not allowed to be less than 900. SRPCOUNT parameter information: Override Information - parameter calculation has been overriden. The calculated value was 2604. The new value is 4000. SRPCOUNT has been increased by 1024. SRPCOUNT is not allowed to be less than 4000. IRPCOUNT parameter information: Override Information - parameter calculation has been overriden. The calculated value was 1904. The new value is 4000. IRPCOUNT is not allowed to be less than 4000. LRPCOUNT parameter information: Override Information - parameter calculation has been overriden. The calculated value was 43. The new value is 200. LRPCOUNT is not allowed to be less than 200. NPAGEDYN parameter information: Override Information - parameter calculation has been overriden. The calculated value was 962941. The new value is 1100000. NPAGEDYN is not allowed to be less than 1100000. PAGEDYN parameter information: Override Information - parameter calculation has been overriden. The calculated value was 1265273. The new value is 2300000. PAGEDYN is not allowed to be less than 2300000. SYSMWCNT parameter information: Override Information - parameter calculation has been overriden. The calculated value was 3553. The new value is 4500. SYSMWCNT is not allowed to be less than 4500. LOCKIDTBL parameter information: Override Information - parameter calculation has been overriden. The calculated value was 1500. The new value is 3800. LOCKIDTBL is not allowed to be less than 3800. LNMSHASHTBL parameter information: Override Information - parameter calculation has been overriden. The calculated value was 128. The new value is 2048. LNMSHASHTBL is not allowed to be less than 2048. PROCSECTCNT parameter information: Override Information - parameter calculation has been overriden.

4-20

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

The calculated value was 32. The new value is 64. PROCSECTCNT is not allowed to be less than 64. Page, Swap, and Dump file calculations Page and Swap file calculations. PAGEFILE parameter information: Override Information - parameter calculation has been overriden. The calculated value was 122000. The new value is 150000. PAGEFILE has been disabled by a hard-coded value of 150000. PAGEFILE will not be modified. SWAPFILE parameter information: Override Information - parameter calculation has been overriden. The calculated value was 27000. The new value is 30000. SWAPFILE has been disabled by a hard-coded value of 30000. SWAPFILE will not be modified. Dumpfile calculations: ** WARNING ** - The system disk would be over 95% full if the dump file were created with 131081 blocks. No dump file modifications would have been made. Dumpfile will remain at 0 blocks.

If this is the case the following message will appear:


-------------------------------------------------------------------------------You must manually edit the file SYS$SYSTEM:MODPARAMS.DAT to correct the problems reported by AUTOGEN and then reinvoke AUTOGEN using the command $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK --------------------------------------------------------------------------------

You must follow the advice given in the report above and then issue the command: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK as described. You may also need to manually edit SYS$SYSTEM:MODPARAMS.DAT before doing this. Finally, if you elected not to update the system parameters, you may also see:
-------------------------------------------------------------------------------SHUTDOWN detected fatal error whilst attempting to shut the system down. --------------------------------------------------------------------------------

In this case enter: $ @SYS$SYSTEM:SHUTDOWN The following messages and prompts will be displayed (example responses are shown enclosed in <> )
SHUTDOWN -- Perform an Orderly System Shutdown on node MARS Do you really want to shutdown node MARS [NO]? <Y> How many minutes until final shutdown [0]: <> Reason for shutdown [Standalone]: <> Do you want to spin down the disk volumes [NO]? <> Do you want to invoke the site-specific shutdown procedure [YES]? <> Should an automatic system reboot be performed [NO]? <Y> When will the system be rebooted [shortly via automatic reboot]: <> Shutdown options (enter as a comma-separated list): REBOOT_CHECK Check existence of basic system files SAVE_FEEDBACK Save AUTOGEN feedback information from this boot

4-21

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Shutdown options [NONE]: <REB,SAV> %SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check... %SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed %SHUTDOWN-I-SAVEFEED, Saving AUTOGENs feedback information from this boot... %SHUTDOWN-I-SAVEOK, Feedback info. saved in SYS$SYSTEM:AGEN$FEEDBACK.DAT %SHUTDOWN-I-BRDOPROFF, Broadcasts to the operator window have been disabled. %SHUTDOWN-I-OPERATOR, This terminal is now an operators console. %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:00.47 %%%%%%%%%%% Operator _MARS$RTA1: has been enabled, username SYSTEM %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:00.48 %%%%%%%%%%% Operator status for operator _MARS$RTA1: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled. %SET-I-INTSET, login interactive limit = 0, current interactive value = 1 %SHUTDOWN-I-SHUTNET, The DECnet network will now be shut down. %SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped. %SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked. SHUTDOWN message on MARS from user SYSTEM at _MARS$RTA1: 13:32:02 MARS will shut down in 0 minutes; back up shortly via automatic reboot. Please log off node MARS. Standalone %SHUTDOWN-I-STOPUSER, All user processes will now be stopped. 1 terminal has been notified on MARS. %SHUTDOWN-I-REMOVE, All installed images will now be removed. %SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted. %SHUTDOWN-I-STOPAUDIT, stopping the audit server %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:06.31 %%%%%%%%%%% Message from user SYSTEM on MARS _MARS$RTA1:, MARS shutdown was requested by the operator. %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:06.86 %%%%%%%%%%% Logfile was closed by operator _MARS$RTA1: Logfile was MARS::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;12 %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:07.43 %%%%%%%%%%% Operator _MARS$RTA1: has been disabled, username SYSTEM

NOTE: On rare occasions the VMS SHUTDOWN procedure may not complete. This is usually because it is being used from a remote terminal which is using DECnet. Since DECnet is shutdown during the procedure, the procedure itself can fail. In such cases you should log into a local terminal on the machine and repeat the exercise. If you cannot physically get to the machine to use a local terminal, then access the machine over LAT. At this stage the LES software has been loaded onto the BAP. It is now necessary to perform some additional actions, described in the next section, prior to starting up the BAP software. If this is an upgrade to a live system then it is necessary to confirm with the Customer when it is possible to shut the live system down. 4.1.3 Additional post installation actions The following procedures are now automated following release 80140. The instructions have been left below to assist in understanding and in the event that additional checks are to be carried out. The automated process is described in section 4.1.5 below. Once installation of the BAP has been completed, then the following operations must be carried out, via the BAPSYS account, many of these are now initiated automatically following release 80140. These are to be performed on each BAP after that BAP has been in4-22

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

stalled and prior to starting the new s/w for the first time. Perform the following actions: Delete FDCD$EXE:FDCD_EXT_MGR_DATA.DAT and recreate it by running @FDCD$EXE:FDCD_CREATE_DATA_FILE.COM Check the version limit on the BAP$ERROR directory has been set to at least 100 The customer should ensure that any/all of their pre-start actions have been carried out. Enter the command: $ @SOI$EXE:SOI_CREATE_WS_SETUP This will then re-create the data file SOI$EXE:SOI_WS_SETUP.TXT 4.1.3.1 Restore protected Files. The customer-specific files delivered as part of a release by HNS must be checked for consistency. This is in case any locally made updates had not been reported to HNS, and so not been incorporated into the release. The configuration data and command files saved prior to installation should checked against the corresponding file in the release directories. This is achieved by using the DCL command DIFFERENCES. During pre-installation, these files were copied to a safe directory (see section 2.2). These must be compared with the newly installed files. For example, the file X25_PARAMS.DAT, having been copied to a directory [SAFE_DIR], would be compared with the command: $ DIFFERENCES XCCC$EXE:X25_PARAMS.DAT DISK:[SAFE_DIR]X25_PARAMS.DAT If any significant differences are reported then HNS should be notified. NOTE: Restoration should be made with care. Check the reference to this section in the Release Notes to ascertain if changes or additions have been made to the new versions of these files and proceed accordingly. CRM$EXE:CRM_MEMORY_PARAMETERS_MEXICO.DAT DRH$EXE:DRH_CNTL_FLAG.INI MDIR$EXE:MDIR_CP_INIT_MEXICO.DAT MSCH$EXE:MSCH_CP_INIT_MEXICO.DAT SOI$EXE:SOI_WS_SETUP.TXT SOI$EXE:SOI_CNTL_FLAG.INI BM$EXE:AUTO_BILLING_CONFIG.DAT
4-23

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

BM$EXE:BM_AHK_CONFIG.DAT XCCC$EXE:TABLE_MEXICO.TXT XCCC$EXE:X25_PARAMS.DAT MCM$EXE:JANITOR.INI MCM$EXE:MCM_CNTL_FLAG.INI CUTL$DAT:CUTL_MH_CONVERSION.DAT FAX$EXE:LESFAX_PARAMS_MEXICO.DAT 4.1.4 Start Installation Outage . Following the release of 80140, the option to perform all the FEP file and re-triggering actions will be offered automatically when first logging on to BAPSYS. If those options were not exercised at that time, then these manual operations may be performed as and when required - as described below. This section defines those actions which must be performed immediately before and during the outage as part of the standard procedures. 4.1.4.1 Rename FEP load files on Master BAP Perform the following commands on the MASTER BAP - before the outage.
Enter: $ Set Def FELNSYS$EXE $ Pur *.SYS $ Dir *.SYS This should show the following files: FEP_MAIN_P.SYS FEP_MAIN_P.SYS_3100_80 FEP_MAIN_P.SYS_95 Then enter: $ Rename FEP_MAIN_P.SYS FEP_MAIN_P.SYS_OLD $ Rename FEP_MAIN_P.SYS_3100_80 FEP_MAIN_P.SYS_3100_80_OLD $ Rename FEP_MAIN_P.SYS_95 FEP_MAIN_P.SYS_95_OLD $ Dir *.SYS*

The final command should verify that all the SYS files have been renamed, thus making them unavailable for FEP loading. This should take less than one minute and must be performed immediately before the next action. 4.1.4.2 Stop the Master BAP At the agreed outage time, stop the MASTER BAP by entering: $ BAPOP STOP BAP

4-24

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

4.1.4.3 Define FEP load files on upgraded BAP and re-trigger The system console should be set to display OPCOM messages. This will allow the operator to verify that the FEPs have been correctly re-loaded. If the system console is unavailable, then, to enable the above display on any terminal, use the following commands: $ SET TERM/BROAD $ REPLY/ENABLE While the Master BAP is stopping, on the newly upgraded BAP, enter: $ @FELNSYS$EXE:INSTALLFEP This will run the FEP load file definition file created during the first pass, AND re-trigger the FEPS, using the new s/w. For each FEP in the system, a pair of OPCOM messages will be seen as reproduced below. Here, NEW_BAP represents the node name of the newly installed BAP and MECU4A represents the node name of each FEP. The values and names are used for example only. Verify that EVERY FEP is successfully loaded from the new BAP
%%%%%%%%%%% OPCOM 10-APR-2001 11:09:36.02 %%%%%%%%%%% (from node NEW_BAP at 10-APR-2001 11:09:35.64) Message from user DECNET on NEW_BAP DECnet event 0.3, automatic line service From node 41.196 (NEW_BAP), 10-APR-2001 11:09:35.63 Circuit ISA-0, Load, Requested, Node = 41.109 (MECU4A) File = $1$DIA3:[BAPSW.REL8011.FELNSYS.EXECUTE]FEP_MAIN_P.SYS_80 Operating system, Ethernet address = 08-00-2B-18-75-1B %%%%%%%%%%% OPCOM 10-APR-2001 11:10:26.92 %%%%%%%%%%% (from node NEW_BAP at 10-APR-2001 11:10:26.54) Message from user DECNET on NEW_BAP DECnet event 0.3, automatic line service From node 41.196 (NEW_BAP), 10-APR-2001 11:10:26.53 Circuit ISA-0, Load, Successful, Node = 41.109 (MECU4A) File = $1$DIA3:[BAPSW.REL8011.FELNSYS.EXECUTE]FEP_MAIN_P.SYS_80 Operating system, Ethernet address = 08-00-2B-18-75-1B

4.1.5 Automated completion of installation Following the installation of a new release, and prior to re-booting, the file SAD$EXE:SAD_FINISH_INSTALL.COM will be copied to the BAPSYS login directory. This file will will run once after the first login on BAPSYS, and then will delete itself from [BAPSYS] This file will offer easy access to the commands required to perform all the actions described in 4.1.3 above. All responses and actions are quite simple and straightforward, however, the description of the automated file restoration is fully described in the section 4.1.5.2 below. 4.1.5.1 Automated completion dialogue Examples of the first pass dialogue using the automated procedure are given below.
-----------------------------------------------------------------------------

4-25

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


Refer to the current release notes for instructions regarding the following actions

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

-- The actions listed at the start of this section 4.1.3 have been -- included here primarily as an aide memoir since in normal circumstance these -- will not be required. The defaults have been set to N in each case. Refer -- to any special instructions in the release notes before login on for the first -- time. In each case below Y has been entered in order purely to illustrate -- the events ----------------------------------------------------------------------------Do you need to recreate FDCD_EXT_MGR_DATA.DAT Y/N [N] ? Y %DELETE-I-FILDEL, $1$DIA4:[BAPSW.REL8013.FDCD.EXECUTE]FDCD_EXT_MGR_DATA.DAT;1 de leted (42 blocks) %DCL-I-SUPERSEDE, previous value of DBA$DB_DIR has been superseded ----------------------------------------------------------------------------The default version limit on BAP$ERROR is currently 99 Do you want to reset this Y/N [N] ? Y It may take a few minutes to set the new limit Enter the new version limit 13 You have entered 13 - is this correct Y/N ? Y -- The time take to complete this action will depend on the number of -- files in the directory, and may take a few minutes. ----------------------------------------------------------------------------Do you need to run SOI_CREATE_WS_SETUP Y/N [N] ? Y -- No dialogue will be seen from this, however a file will be created -- SOI$EXE:SOI_WS_SETUP.TXT - this may differ from the saved file (if this exists). -- This will become apparent during the next stage of the installation when saved -- and new files are compared. The opportunity will be given to accept or change -- these modifications if required. -----------------------------------------------------------------------------

----------------------------------------------------------------------------Checking protected files for differences after installation -- See section 4.1.5.2 below for a description as to how this works ----------------------------------------------------------------------------Checking file LES$DISK0:[BAPSW.RELRel.SAD.Execute]SAD_PROTECT_FILES.DAT Checking file LES$DISK0:[BAPSW.RELRel.SOI.Execute]SOI_WS_SETUP.TXT Checking file LES$DISK0:[BAPSW.RELRel.SOI.Execute]SOI_CNTL_FLAG.INI Checking file LES$DISK0:[BAPSW.RELRel.BM.Execute]AUTO_BILLING_CONFIG.DAT Checking file LES$DISK0:[BAPSW.RELRel.BM.Execute]BM_AHK_CONFIG.DAT Checking file LES$DISK0:[BAPSW.RELRel.XCCC.Execute]TABLE_Customer.TXT Checking file LES$DISK0:[BAPSW.RELRel.XCCC.Execute]X25_PARAMS.DAT Checking file LES$DISK0:[BAPSW.RELRel.MCM.Execute]JANITOR.INI Checking file LES$DISK0:[BAPSW.RELRel.MCM.Execute]MCM_CNTL_FLAG.INI Checking file LES$DISK0:[BAPSW.RELRel.CUTL.execute]CUTL_MH_CONVERSION.DAT -----------------------------------------------------------------------------

4-26

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

Differences for CUTL:CUTL_MH_CONVERSION.DAT (Return to view next page - if any) THe NEW file is on the left, the OLD, protected file on the right ------------------------------------------------------------------------------ In this example, a comment had been put in the saved file in order to -- demonstrate a single difference. Normally the display would change to 132 -- characters to show the differences on the same line. For clarity on the printed -- page, the two halves have been presented sequentially -- If no differences are found then the sequence continues from -- "Extracting name of installation disk on ...." -- below -----------------------------------------------------------------File $1$DIA4:[BAPSW.REL8013.CUTL.EXECUTE]CUTL_MH_CONVERSION.DAT | -------------------------------- 60 -----------------------------| ---------------------------------------------------------------------------------------------------------------------------------File $1$DIA4:[PROTECTED.PRE_REL8013]CUTL_MH_CONVERSION.DAT;6 -------------------------------- 60 ----------------------------C test comment ----------------------------------------------------------------Number of difference sections found: 1 Number of difference records found: 1 DIFFERENCES /IGNORE=()/OUTPUT=$1$DIA4:[BAPSYS]TMP.DIF;1/PARALLEL$1$DIA4:[BAPSW.REL8013.CUTL.EXECUTE]CUTL_MH_CONVERSION.DAT;1$1$DIA4:[PROTECTED.PRE_REL8013]CUTL_MH_CONVERSION.DAT;6 ----------------------------------------------------------------------------Do you want to view the differences for CUTL_MH_CONVERSION.DAT again Y/N <n> -----------------------------------------------------------You now have three options: 1 - Accept the new file with no changes 2 - Merge the two (Edit the new file and apply the required changes) 3 - Re-use the saved file, ignoring the new -----------------------------------------------------------Enter option number (Return to view the differences for CUTL_MH_CONVERSION.DAT a gain) <1> -- In this instance, the new file has been accepted with no change. -- Checking resumes with the next saved file. Checking file LES$DISK0:[BAPSW.RELRel.FAX.Execute]LESFAX_PARAMS_Customer.DAT Checking file LES$DISK0:[BAPSW.RELRel.INT.Execute]INT_DITCH_MRN.COM Checking file LES$DISK0:[BAPSW.RELRel.INT.Execute]INT_RWAST_DETECTOR.COM Checking file LES$DISK0:[BAPSW.RELRel.SDA.Execute]SDA_MOBILE.SQL ----------------------------------------------------------------------------Differences have been found in protected files, please check les$disk0:[PROTECTED.Pre_REL8013]DIFFERENCES.LIST for a list of affected files -- The above file is created for reference purposes, and may -- be used to verify changes and corrections -----------------------------------------------------------------------------

4-27

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

-- The installation needs now to determine some details from the other BAP -- node. If no BAP found then this will be listed as UNDEFINED ----------------------------------------------------------------------------Extracting name of installation disk on - name of other BAP node ----------------------------------------------------------------------------Individual nodes: CRUX Username BAPSYS will be used on nonlocal nodes 2 *LES$DISK0* = *$1$DIA8:* (LNM$SYSTEM_TABLE) $1$DIA0:[BAPSYS]MCSYSTMP.OUT;2 2 lines [EOB] BAPSYS disk on CRUX : $1$DIA8: -- This is an example of the display obtained on the HNS test node -- PHACT, when interogating the partner node CRUX ------------------------------------------------------------------------------- The following paragraph will only be displayed if this appears -- to be a second pass - for the reasons indicated. The same release 8013 is currently defined on the other BAP <BAP_Name> This normally indicates a second pass installation. However, this may not be the case if this is an EBF installation FEP load files (on other BAP will only be renamed to _OLD on a first pass The option to re-trigger the FEPs will only be offered for a first pass -- The selection of 1 here does not result in the immediate -- re-triggering, merely the creation of COM files to assist in this -- task later. -----------------------------------------------------------------------------Please enter 1 or 2 for first or second pass 1/[2] <1> ------------------------------------------------------------------------------ First pass installatin process resumes here This is a first pass installation -- Confirmation of the selection ----------------------------------------------------------------------------$1$DIA8:[bapsw.REL8013...] will be renamed _OLD The options available are: To rename the above files (default) - Y To specify an alternative (earlier) files - A To rename NO files - N Please choose Y/A/N [Y] ? %RENAME-I-RENAMED, $1$DIA4:[BAPSW.REL8013.FELNSYS.EXECUTE]FEP_MAIN_P.SYS;1 renam ed to $1$DIA4:[BAPSW.REL8013.FELNSYS.EXECUTE]FEP_MAIN_P.SYS_OLD;1 %RENAME-I-RENAMED, $1$DIA4:[BAPSW.REL8013.FELNSYS.EXECUTE]FEP_MAIN_P.SYS_3100_80 ;1 renamed to $1$DIA4:[BAPSW.REL8013.FELNSYS.EXECUTE]FEP_MAIN_P.SYS_3100_80_OLD; 1 %RENAME-I-RENAMED, $1$DIA4:[BAPSW.REL8013.FELNSYS.EXECUTE]FEP_MAIN_P.SYS_95;1 re named to $1$DIA4:[BAPSW.REL8013.FELNSYS.EXECUTE]FEP_MAIN_P.SYS_95_OLD;1 -- Here examples of renaming SD FEP load files is shown the file -- SAD$EXE:SAD_RESTORE_FEP_LOAD_FILES.COM may be used to restore these file names -- if required -----------------------------------------------------------------------------Searching for all FEPs defined in DEFSAD.COM for this LES

4-28

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

-----------------------------------------------------------------------------Contents of SAD$EXE:SAD_TRIGGER_SD_FEPS.COM : $!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! $! File automatically created on 2001-08-06 16:13:19.07 $! for release REL8013 $!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! $! $ Triggering Node FEPSD3" $ mc ncp trigger node FEPSD3 $! $ Triggering Node FEPSD9" $ mc ncp trigger node FEPSD9 $! -----------------------------------------------------------------------------Do you want to re-trigger ALL FEPs now. This should normally only be done IMMEDIATELY before stopping an uninstalled master BAP at the end of a FIRST PASS installation. FEPs may be re-triggered at any time simply by running the command: @SAD$EXE:SAD_TRIGGER_SD_FEPS for SD FEPs OR @SAD$EXE:SAD_TRIGGER_TIC_FEPS for telex FEPs -----------------------------------------------------------------------------Enter Y to re-trigger or N not to Y/[N]

-- Y should be entered if there are no further manual actions required before -- stopping the current master BAP running the previous release of software. -- If the new BAP is not to be started immediately, then the COM files just created -- may be run later to re-trigger when required Triggering Node FEPSD3 Triggering Node FEPSD9 -- Confirmation of the node triggered (if requested is shown) -----------------------------------------------------------------------------If this is a first pass, AND all there are no outstanding actions, other than the database upgrade, then now is the appropriate time to stop the old master BAP and to start the new BAP or the ONDB server if a DB upgrade is required IF and ONLY if all other preparation has been completed, STOP the other BAP Is installation otherwise complete AND the other BAP stopped or stopping Y/N N Do you want to pause while the other BAP is stopped Y/N ? Y Is installation otherwise complete AND the other BAP stopped or stopping Y/N Y Do the Release Notes call for a database upgrade? Y/N Y Starting ONDB now Starting the MASTER SQL Server ONDB on node PHACT. Runserver file: SYBASE_SYSTEM:[SYBASE.INSTALL]RUN_ONDB.COM Quota values: cpulm = 0 astlm = 254 wsextent = 30000 biolm = 175 diolm = 79 wsquota = 30000 wsdefault = 30000 bytlm = 153023 enqlm = 31

4-29

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


fillm = 31 pgflquota = 30000 tqelm = 40 prclm = 8 jtquota = 2600 Base priority: 4 VMS process name: ONDB_SQL Do you need to upgrade the ONLINE database now Y/N -- At this point, a check will be made to see if ONDB server is running on this -- node. If it is, then the file -- DBCONV80000$EXE:ONDB_CONVERSION_MENU.COM -- will be run. If the server is not running, then the preceding questions will -- asked again, and the opportunity given to start the server again if overlooked -- before.

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Automatic installation is now complete, after completing any remaining actions or options which may have been skipped, start the BAP using BAPOP START BAP ARBITER - or as otherwise directed in the release notes

4.1.5.2 Automated saved file comparison This file will: 1. Check the files from the previous release protected during installation against the newly installed files. If there are differences, then, for each file with differences, three options will be offered: a. Accept the new file with no changes. b. Start an editor, opening both files so that the new version may be updated with details from the old. The new file will then be re-saved with any changes made. c. Replace the new file with the protected file in its entirety. 2. An attempt will be made to determine if this is a first or second pass installation. The most likely case will be presented as a default response. However, it remains the operators responsibility to ensure that the correct response is made. 3. If this is a second pass, then no further options are offered, and no actions taken. 4. If this is a first pass: a. It will offer to rename all the FEP load files on the partner BAP. b. Create a COM file(SAD$EXE:SAD_TRIGGER_SD_FEPS.COM). c. Offer to run the above file now. This should only be done if there are no further manual actions required before starting the newly installed BAP - such as database upgrade. 5. When done this file will remove itself from sys$login and will not run again.

4-30

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

4.1.6 Configuring a New BAP This section describes the procedure to follow if there is a need to redefine the system configuration. For example if FEP nodes or SOC names are to be added or removed. This can be done from the operational account (BAPSYS) by entering: $ @SAD$EXE:SADREDEF.COM This executes a section of the installation procedure (SADREDEF.COM). It will create a new version of SYS$LOGIN:DEFSAD.COM which contains the configuration information. See section 4.1.6.1 below for an example of this procedure. NOTE: DEFSAD.COM must not be manually changed since there are a great many rules and requirements for consistency which can only be checked if the proper procedure is used. To make use of any changes you have made to the values in this file enter: $ @SYS$LOGIN:DEFSAD followed by: $ @SYS$LOGIN:LOGIN The BAP must then be stopped and restarted. The current configuration information is stored, in textual form, in a file called CONFIGURATION.TXT. This file is in the BAPSYS SYS$LOGIN directory. The layout of this file makes it a useful source of information and as such a copy should be kept safe. See the blank sheet and a filled in example in sections 4.1.8 and 4.1.9 for further details. 4.1.6.1 Running DEFSAD.COM on a new BAP This example of the procedure to redefine the DEFSAD parameters is similar to that given in the main body of text for an installation on an existing BAP. In the example below, however, the non default answers have been utilised so as to generate a full set of examples to illustrate the procedure. After entering @SAD$EXE:SADREDEF.COM the question will be asked:
Do you want to change BAP (SADREDEF) configuration ? (Y/[N]): <Y> When prompted for input, enter data according to the configuration you require. Some prompts display a default reply [shown in brackets]. To use the default, press the RETURN key. To replace default data, enter the new data to be used. To cancel the use of default data without entering new data, enter the backslash (\) character. You will have the opportunity to review and correct your responses before actually creating DEFSAD.COM. RELEASE: Release Number: Release Disk : 8002 LES$DISK0:

* Is this information correct? (Y/N) [Y]: <N>

4-31

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

* Enter 4-digit release number, e.g. 0102? [8002]: 8011 * Enter disk on which release 8011 resides, e.g. USER1? [LES$DISK0:]: <> Release Number: Release Disk : 8011 LES$DISK0:

* Is this information correct? (Y/N) [Y]: <> NAMES: Processor Name: Current Region: BAPB ATLANTIC

* Is this information correct? (Y/N) [Y]: <N> * Enter processor name for this BAP, e.g. BAPA? (BAPA/BAPB) [BAPB]: <> * Enter current region, e.g. ATLANTIC? (WEST/ATLANTIC/PACIFIC/INDIAN) [ATLANTIC]: <> Processor Name: Current Region: BAPB ATLANTIC

* Is this information correct? (Y/N) [Y]: <> CONFIGURATION: System Size : MCM Ast Length: MCM Ast Usable: SMALL 200 160

* Is this information correct? (Y/N) [Y]: <N> The System Size can have the values SMALL,MEDIUM,LARGE,XLARGE: where: SMALL represents a system with 1-2 TDMs, typically a VAX4000-100 and a message rate of about 3000 messages per hour. MEDIUM represents a system with 2-3 TDMs, typically a VAX4000-700A with solid state disks and a message rate of typically 5500 messages per hour. LARGE represents a system with 2-3 TDMs, typically a VAX7000-640 with a solid state disks and a message rate of typically 7000 messages per hour. XLARGE represents a system with up to 6 TDMs, typically a VAX7000-640 with a solid state disks and a message rate of typically 15000 messages per hour. * Enter System Size? (SMALL/MEDIUM/LARGE/XLARGE) [SMALL]: <> The recommended values for MCM Active Ship Transfer List Sizes are dependent on the System Size :SMALL - MCM$AST_LENGTH = 200 - MCM$AST_USABLE = 160 MEDIUM LARGE XLARGE MCM$AST_LENGTH = MCM$AST_USABLE = MCM$AST_LENGTH = MCM$AST_USABLE = 200 160 372 312

MCM$AST_LENGTH = 1530 MCM$AST_USABLE = 1116

* Enter length of Active Ship Transfer List? [200]: <> * Enter usable length of Active Ship Transfer List? [160]: <> CONFIGURATION: System Size : MCM Ast Length: MCM Ast Usable: SMALL 200 160

* Is this information correct? (Y/N) [Y]: <> DEVICES:

4-32

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

Arbiter Device : LTA2: Shadow set 1 : DSA1: Shadow set 1 Disk 1 : $1$DIA1: Shadow set 1 Disk 2 : $1$DIA5: Shadow Set 2 : DSA2: Shadow set 2 Disk 1 : $1$DIA2: Shadow set 2 Disk 2 : $1$DIA6: MAR File disk : DSA2: Quorum Disk : $1$DIA3: OFDB Disk : $1$DIA3: Tk50{MKB500:}, Tk70{MKB500:}, Tf85{MIA6:}, Dds{MKA500:}> Spool Tape : MKA500: UTC Device : UNKNOWN * Is this information correct? (Y/N) [Y]: <N> * Enter arbiter card terminal device, e.g. TXA0? [LTA2:]:<> Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt DSA1: Mounted 0 USER01 225954 17 2 DSA2: Mounted 0 USER02 312405 3 2 $1$DIA0: (R5SEGF) Mounted 0 MEBAPA_SYS 601623 344 2 $1$DIA1: (R1AEUI) ShadowSetMember 0 (member of DSA1:) $1$DIA2: (R1CINE) ShadowSetMember 0 (member of DSA2:) $1$DIA3: (R1C2AI) Mounted 0 QUORUM 41652 1 2 $1$DIA4: (R5WIEG) Mounted 0 MEBAPB_SYS 593676 1 2 $1$DIA5: (R1UDWA) ShadowSetMember 0 (member of DSA1:) $1$DIA6: (R1TKEE) ShadowSetMember 0 (member of DSA2:) $1$DIA9: (R5ULVG) Mounted 0 USER03 248838 1 2 $1$DKA400: (CVAXA) Online wrtlck 0 * Enter first shadow set device, e.g. DSA1? [DSA1:]:<> * Enter first shadow set member 1, e.g. USER01? [$1$DIA1:]:<> * Enter first shadow set member 2, e.g. USER02? [$1$DIA5:]:<> * Enter second shadow set device, e.g. DSA2? [DSA2:]:<> * Enter second shadow set member 1, e.g. USER03? [$1$DIA2:]:<> * Enter second shadow set member 2, e.g. USER04? [$1$DUA6:]:<> * Enter MAR file disk (use second shadowset if it exists)? [DSA2:]:<> * Enter quorum disk, e.g USER3 ? [$1$DIA3:]:<> * Enter OFDB disk (use quorum disk if it exists)? [$1$DIA3:]:<> * Enter TK70 cartridge tape device, e.g. MUA0? [MKA500:]: <> * Enter TU81 spool tape device, e.g. MUA1? [MKA500:]: <> ** Enter UTC clock port, e.g. TXA0? [UNKNOWN]:<> Arbiter Device Shadow set 1 Shadow set 1 Disk Shadow set 1 Disk Shadow Set 2 Shadow set 2 Disk Shadow set 2 Disk MAR File disk Quorum Disk OFDB Disk Cartridge Tape Spool Tape UTC Device : : : : : : : : : : : : : LTA2: DSA1: $1$DIA1: $1$DIA5: DSA2: $1$DIA2: $1$DIA6: DSA2: $1$DIA3: $1$DIA3: MKA500: MKA500: UNKNOWN

1 2 1 2

* Is this information correct? (Y/N) [Y]:<> PRINTERS: Alarm Printer 1 Alarm Printer 2 Alarm Printer 3 Alarm Printer 4 Alarm Printer 5 Alarm Printer 6 Alarm Printer 7 Alarm Printer 8 Alarm Printer 9 Offline Report Queue : : : : : : : : : : LTA1: LTA2: UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED REPORT$PRINTER

4-33

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


Online Report Queue : UNDEFINED

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

* Is this information correct? (Y/N) [Y]: <N> * * * * * * * * * * * Enter Enter Enter Enter Enter Enter Enter Enter Enter Enter Enter alarm printer 1 device, e.g. LTA1? [LTA1:]: <> alarm printer 2 device, e.g. LTA2? [LTA2:]: <> alarm printer 3 device, e.g. LTA3? [UNDEFINED]: <> alarm printer 4 device, e.g. LTA4? [UNDEFINED]: <> alarm printer 5 device, e.g. LTA5? [UNDEFINED]: <> alarm printer 6 device, e.g. LTA6? [UNDEFINED]: <> alarm printer 7 device, e.g. LTA7? [UNDEFINED]: <> alarm printer 8 device, e.g. LTA8? [UNDEFINED]: <> alarm printer 9 device, e.g. LTA9? [UNDEFINED]: <> offline report printer queue, e.g. PRINT1? [REPORT$PRINTER]: <> online report printer queue, e.g. PRINT1? [UNDEFINED]: <> Alarm Printer 1 Alarm Printer 2 Alarm Printer 3 Alarm Printer 4 Alarm Printer 5 Alarm Printer 6 Alarm Printer 7 Alarm Printer 8 Alarm Printer 9 Offline Report Queue Online Report Queue : : : : : : : : : : : LTA1: LTA2: UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED REPORT$PRINTER UNDEFINED

* Is this information correct? (Y/N) [Y]: <> CHANNEL UNIT SWITCHES: CUC1 CUC2 CUC3 CUC4 Switch: Switch: Switch: Switch: UNDEFINED TXA2: UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <N> * * * * Enter Enter Enter Enter CUC1 CUC2 CUC3 CUC4 CUC1 CUC2 CUC3 CUC4 switch switch switch switch Switch: Switch: Switch: Switch: terminal terminal terminal terminal device, device, device, device, e.g. e.g. e.g. e.g. TXA1? TXA2? TXA3? TXA4? [UNDEFINED]: <> [TXA2:]: <> [UNDEFINED]: <> [UNDEFINED]: <>

UNDEFINED TXA2: UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <> TELEX INTERFACE SWITCHES: TIC1 TIC2 TIC3 TIC4 TIC5 TIC6 COB1 Switch: Switch: Switch: Switch: Switch: Switch: Switch: UNDEFINED UNDEFINED TXA4: UNDEFINED UNDEFINED UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <N> * * * * * * * Enter Enter Enter Enter Enter Enter Enter TIC1 TIC2 TIC3 TIC4 TIC5 TIC6 COB1 switch switch switch switch switch switch switch terminal terminal terminal terminal terminal terminal terminal device, device, device, device, device, device, device, e.g. e.g. e.g. e.g. e.g. e.g. e.g. TXA1? TXA2? TXA3? TXA4? TXA5? TXA6? TXA1? [UNDEFINED]: [UNDEFINED]: [TXA4:]: <> [UNDEFINED]: [UNDEFINED]: [UNDEFINED]: [UNDEFINED]: <> <> <> <> <> <>

TIC1 Switch:

UNDEFINED

4-34

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


TIC2 TIC3 TIC4 TIC5 TIC6 COB1 Switch: Switch: Switch: Switch: Switch: Switch: UNDEFINED TXA4: UNDEFINED UNDEFINED UNDEFINED UNDEFINED

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

* Is this information correct? (Y/N) [Y]: <> DEMSA SWITCHES: DEMSA DEMSA DEMSA DEMSA 1 2 3 4 Switch: Switch: Switch: Switch: TXA1: UNDEFINED UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <N> * * * * Enter Enter Enter Enter DEMSA DEMSA DEMSA DEMSA DEMSA DEMSA DEMSA DEMSA 1 2 3 4 1 2 3 4 switch switch switch switch Switch: Switch: Switch: Switch: terminal terminal terminal terminal device, device, device, device, e.g. e.g. e.g. e.g. TXA1? TXA2? TXA3? TXA4? [TXA1:]: <> [UNDEFINED]: <> [UNDEFINED]: <> [UNDEFINED]: <>

TXA1: UNDEFINED UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <> BACKGROUND APPLICATIONS PROCESSORS: BAPA: BAPB: CBAPA CBAPB Service State: Service State: IN_SERVICE IN_SERVICE

* Is this information correct? (Y/N) [Y]: <N> * Enter node name of BAPA, e.g. BAP01A? [CBAPA]: <> * Enter service state of BAPA, e.g. IN_SERVICE? (IN_SERVICE/OUT_OF_SERVICE) [IN_SERVICE]: <> * Enter node name of BAPB, e.g. BAP01B? [CBAPB]: <> * Enter service state of BAPB, e.g. IN_SERVICE? (IN_SERVICE/OUT_OF_SERVICE) [IN_SERVICE]: <> BAPA: BAPB: CBAPA CBAPB Service State: Service State: IN_SERVICE IN_SERVICE

* Is this information correct? (Y/N) [Y]: <> OCEAN REGIONS: WEST ATLANTIC PACIFIC INDIAN Ocean Ocean Ocean Ocean Region Region Region Region Service Service Service Service State: State: State: State: OUT_OF_SERVICE IN_SERVICE OUT_OF_SERVICE OUT_OF_SERVICE LES LES LES LES Number: Number: Number: Number: 44 3 44 44

* Is this information correct? (Y/N) [Y]: <N> * Enter service state of WEST ocean region, e.g. IN_SERVICE? (IN_SERVICE/OUT_OF_SERVICE) [OUT_OF_SERVICE]: <> * Enter service state of ATLANTIC ocean region, e.g. IN_SERVICE? (IN_SERVICE/OUT_OF_SERVICE) [IN-SERVICE]: <>

* Enter service state of PACIFIC ocean region, e.g. IN_SERVICE? (IN_SERVICE/OUT_OF_SERVICE) [OUT_OF_SERVICE]: <>

* Enter service state of INDIAN

ocean region, e.g. IN_SERVICE?

4-35

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

(IN_SERVICE/OUT_OF_SERVICE) [OUT_OF_SERVICE]: <>

WEST ATLANTIC PACIFIC INDIAN

Ocean Ocean Ocean Ocean

Region Region Region Region

Service Service Service Service

State: State: State: State:

OUT_OF_SERVICE IN-SERVICE OUT_OF_SERVICE OUT_OF_SERVICE

LES LES LES LES

Number: Number: Number: Number:

44 3 44 44

* Is this information correct? (Y/N) [Y]: <> CHANNEL UNIT CONTROLLERS: ATLANTIC: CUC2A: CUC2B:

FEPSD4 FEPSD3

Service State: Service State:

IN_SERVICE IN_SERVICE

* Is this information correct? (Y/N) [Y]: <N>

ATLANTIC: CUC2A: CUC2B:

FEPSD4 FEPSD3

Service State: Service State:

IN_SERVICE IN_SERVICE

* Is this information correct? (Y/N) [Y]: <> TELEX INTERFACE CONTROLLERS: TIC1A: TIC1B: TIC2A: TIC2B: TIC3A: TIC3B: TIC4A: TIC4B: TIC5A: TIC5B: TIC6A: TIC6B: UNDEFINED UNDEFINED UNDEFINED UNDEFINED FEPSE3 FEPIO3 UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED Service Service Service Service Service Service Service Service Service Service Service Service State: State: State: State: State: State: State: State: State: State: State: State: UNDEFINED UNDEFINED UNDEFINED UNDEFINED IN_SERVICE IN_SERVICE UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <N> * * * * * * Enter Enter Enter Enter Enter Enter node name of TIC1A, e.g. TIC01A? [UNDEFINED]: <> node name of TIC1B, e.g. TIC01B? [UNDEFINED]: <> node name of TIC2A, e.g. TIC02A? [UNDEFINED]: <> node name of TIC2B, e.g. TIC02B? [UNDEFINED]: <> node name of TIC3A, e.g. TIC03A? [FEPSE3]: <> service state of TIC3A, e.g. IN_SERVICE? (IN_SERVICE/OUT_OF_SERVICE) [IN_SERVICE]: <> node name of TIC3B, e.g. TIC03B? [FEPIO3]: <> service state of TIC3B, e.g. IN_SERVICE? (IN_SERVICE/OUT_OF_SERVICE) [IN_SERVICE]: <> node name of TIC4A, e.g. TIC04A? [UNDEFINED]: <> node name of TIC4B, e.g. TIC04B? [UNDEFINED]: <> node name of TIC5A, e.g. TIC05A? [UNDEFINED]: <> node name of TIC5B, e.g. TIC05B? [UNDEFINED]: <> node name of TIC6A, e.g. TIC06A? [UNDEFINED]: <> node name of TIC6B, e.g. TIC06B? [UNDEFINED]: <> TIC1A: TIC1B: TIC2A: TIC2B: TIC3A: TIC3B: TIC4A: UNDEFINED UNDEFINED UNDEFINED UNDEFINED FEPSE3 FEPIO3 UNDEFINED Service Service Service Service Service Service Service State: State: State: State: State: State: State: UNDEFINED UNDEFINED UNDEFINED UNDEFINED IN_SERVICE IN_SERVICE UNDEFINED

* Enter * Enter * * * * * * Enter Enter Enter Enter Enter Enter

4-36

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


TIC4B: TIC5A: TIC5B: TIC6A: TIC6B: UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED Service Service Service Service Service State: State: State: State: State:

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <> SYSTEM OPERATOR CONSOLES: SOC1A: SOC1B: SOC2A: SOC2B: SOC1A SOC1B UNDEFINED UNDEFINED Service Service Service Service State: State: State: State: IN_SERVICE IN_SERVICE UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <N> * Enter node name of SOC1A, e.g. SOC01A? [SOC1A]: <> * Enter service state of SOC1A, e.g. IN_SERVICE? (IN_SERVICE/OUT_OF_SERVICE) [IN_SERVICE]: <> * Enter node name of SOC1B, e.g. SOC01B? [SOC1B]: <> * Enter service state of SOC1B, e.g. IN_SERVICE? (IN_SERVICE/OUT_OF_SERVICE) [IN_SERVICE]: <> * Enter node name of SOC2A, e.g. SOC02A? [UNDEFINED]: <> * Enter node name of SOC2B, e.g. SOC02B? [UNDEFINED]: <> SOC1A: SOC1B: SOC2A: SOC2B: SOC1A SOC1B UNDEFINED UNDEFINED Service Service Service Service State: State: State: State: IN_SERVICE IN_SERVICE UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <> DEMSA PAIR NAMES: DEMSA DEMSA DEMSA DEMSA 1 2 3 4 Pair: Pair: Pair: Pair: DOUGAL UNDEFINED UNDEFINED UNDEFINED Switch Switch Switch Switch Setting: Setting: Setting: Setting: A A A A

* Is this information correct? (Y/N) [Y]: <N> * * * * * Enter Enter Enter Enter Enter pair name of DEMSA 1 pair, e.g. switch setting of DEMSA 1 pair, pair name of DEMSA 2 pair, e.g. pair name of DEMSA 3 pair, e.g. pair name of DEMSA 4 pair, e.g. DEMSA DEMSA DEMSA DEMSA 1 2 3 4 Pair: Pair: Pair: Pair: DOUGAL UNDEFINED UNDEFINED UNDEFINED PSDN1? [DOUGAL]: <> e.g. A? (A/B) [A]: <> PSDN2? [UNDEFINED]: <> PSDN3? [UNDEFINED]: <> PSDN4? [UNDEFINED]: <> Switch Switch Switch Switch Setting: Setting: Setting: Setting: A A A A

* Is this information correct? (Y/N) [Y]: <> DEMSA NODE NAMES: DEMSA DEMSA DEMSA DEMSA DEMSA DEMSA DEMSA DEMSA 1A: 1B: 2A: 2B: 3A: 3B: 4A: 4B: EDONIS WASAT UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED Service Service Service Service Service Service Service Service State: State: State: State: State: State: State: State: IN_SERVICE IN_SERVICE UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <N> * Enter node name of DEMSA 1A, e.g. PSDN1A? [EDONIS]: <> * Enter service state of DEMSA 1A, e.g. IN_SERVICE?

4-37

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

(IN_SERVICE/OUT_OF_SERVICE) [IN_SERVICE]: <> * Enter node name of DEMSA 1B, e.g. PSDN1B? [WASAT]: <> * Enter service state of DEMSA 1B, e.g. IN_SERVICE? (IN_SERVICE/OUT_OF_SERVICE) [IN_SERVICE]: <> * * * * * * Enter Enter Enter Enter Enter Enter node node node node node node name name name name name name 1A: 1B: 2A: 2B: 3A: 3B: 4A: 4B: of of of of of of DEMSA DEMSA DEMSA DEMSA DEMSA DEMSA 2A, 2B, 3A, 3B, 4A, 4B, e.g. e.g. e.g. e.g. e.g. e.g. PSDN2A? PSDN2B? PSDN3A? PSDN3B? PSDN4A? PSDN4B? Service Service Service Service Service Service Service Service [UNDEFINED]: [UNDEFINED]: [UNDEFINED]: [UNDEFINED]: [UNDEFINED]: [UNDEFINED]: State: State: State: State: State: State: State: State: <> <> <> <> <> <>

DEMSA DEMSA DEMSA DEMSA DEMSA DEMSA DEMSA DEMSA

EDONIS WASAT UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED

IN_SERVICE IN_SERVICE UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <> PSDN INTERFACE: X.25 Destination Name : X.400 Destination Name: X.25 Low Sub-Address : X.25 High Sub-Address : X.400 Sub-Address : DEMSA Poll Timer : PSI Network : PSI DEMSA Pair Number : LES DTE Address : X25 Line Fail Retry : X25LES X400LES 25 27 28 60.0 HNS_B 1 399922117000 10

* Is this information correct? (Y/N) [Y]: <N> X.25 destination name, e.g. X25LES? [X25LES]: <> X.400 destination name, e.g. X400LES? [X400LES]: <> X.25 low sub-address, e.g. 00? [25]: <> X.25 high sub-address, e.g. 98? [27]: <> X.400 sub-address, e.g. 99? [28]: <> DEMSA poll timer interval (real seconds) or OFF, e.g. 60.0? [60.0]: <> * Enter PSI network name, e.g. PSS, IPN_A, IPN_B, IPN2_A, IPN2_B, PSDN_A, PSDN_B? [HNS_B]: <> * * * * * * Enter Enter Enter Enter Enter Enter * Enter PSI DEMSA pair number, e.g. 1? [1]: <> * Enter LES DTE address, e.g. 39992211700000 ? []: <> * Enter X25 Line Fail Retry Counter? [10]: <> X.25 Destination Name : X.400 Destination Name: X.25 Low Sub-Address : X.25 High Sub-Address : X.400 Sub-Address : DEMSA Poll Timer : PSI Network : PSI DEMSA Pair Number : LES DTE Address : X25 Line Fail Retry : X25LES X400LES 25 27 28 60.0 HNS_B 1 399922117000 10

* Is this information correct? (Y/N) [Y]: <> KERMIT INTERFACE: Maximum Packet Size : Number of Pad Characters: Pad Character : 80 0 32 (" ")

4-38

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


Control Prefix Character: Binary Prefix Character : End of Line Character : Number of Retries : Timeout : 35 ("#") 38 ("&") 13 3 60

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

* Is this information correct? (Y/N) [Y]: <N> * Enter maximum packet size Kermit should receive (characters), e.g. 80? [80]: <> * Enter number of pad characters, e.g. 0? [0]: <> * Enter pad character (ASCII code or character), e.g. 32? [32]: <> * Enter control prefix character (ASCII code or character), e.g. 35? [35]: <> * Enter binary prefix character (ASCII code or character), e.g. 38? [38]: <> * Enter end of line character (ASCII code or character), e.g. 13? [13]: <> * Enter number of times Kermit should try to send a packet, e.g. 3? [3]: <> * Enter number of seconds Kermit should wait before timing out, e.g. 60? [60]: <> Maximum Packet Size : Number of Pad Characters: Pad Character : Control Prefix Character: Binary Prefix Character : End of Line Character : Number of Retries : Timeout : 80 0 32 (" ") 35 ("#") 38 ("&") 13 3 60

* Is this information correct? (Y/N) [Y]: <> -------------------------------------------------------------------------------Creating CES definition file SYS$LOGIN:DEFSAD.COM --------------------------------------------------------------------------------------------------------------------------------------------------------------Creating CES report file SYS$LOGIN:CONFIGURATION.TXT --------------------------------------------------------------------------------

*** BAP parameter definition complete

4.1.7 Confidence Checks Following the successful installation and re-start of the first BAP. Carry out any confidence checks deemed neccessary or indicated in the accompanying release notes. If it is seen that the system is functioning correctly, then it should be agreed that fall-back is not neccessary and the installation can be continued at a convenient time. If the system is not functioning correctly, then the cause should be determined and resolved. If this is not possible, then it should be agreed that fall-back is required and the installation should be aborted. Continue at section 10 after first checking for any special instructions for fall-back in the Release Notes.

4-39

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

4.1.8 Installation Template


BAP CONFIGURATION System: ______ : : : : _________ _________ _________ _________ At: _______________________ Operational Disk Operational Account Operational Group Page 1 of 3

Project Name Processor Name Operator Name Customer Name

: _________ : _________ : _________

RELEASE: Release Number : _________ Release Disk Release Date : _______________________ NAMES: BAP name (BAPA/BAPB) DEVICES: Arbiter Device 1st Shadow Set 1st Shadow Set disk 1 2nd Shadow Set 2nd Shadow Set disk 1 MAR File Disk OFDB Disk Spool Tape PRINTERS: Alarm Printer 1 Alarm Printer 2 Alarm Printer 3 Alarm Printer 4 Alarm Printer 5 Alarm Printer 6 Alarm Printer 7 Alarm Printer 8 Alarm Printer 9 Offline Report Queue Online Report Queue CHANNEL UNIT CUC1 CUC2 CUC3 CUC4 SWITCHES: Switch Device Switch Device Switch Device Switch Device : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________

: _________

Current Region : _________

1st Shadow Set disk 2 : ________ 2nd Shadow Set disk 2 : ________ Quorum Disk : ________ Cartridge Tape : ________ UTC Device : ________

TELEX INTERFACE SWITCHES: TIC1 Switch Device TIC2 Switch Device TIC3 Switch Device TIC4 Switch Device TIC5 Switch Device TIC6 Switch Device COB1 Switch Device DEMSA SWITCHES: Demsa Port Demsa Port Demsa Port Demsa Port 1 2 3 4 Device Device Device Device

4-40

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


BAP CONFIGURATION BAPS: BAPA node name : _________ OCEAN REGIONS: WEST : ______________ ATLANTIC : ______________ CHANNEL UNIT CONTROLLERS: WEST: CUC1A : _________ CUC1B : _________ ATLANTIC: CUC2A : _________ CUC2B : _________ PACIFIC: CUC3A : _________ CUC3B : _________ INDIAN: CUC4A : _________ CUC4B : _________ TELEX INTERFACE CONTROLLERS: TIC1A : _________ TIC1B : _________ TIC2A : _________ TIC2B : _________ TIC3A : _________ TIC3B : _________ TIC4A : _________ TIC4B : _________ TIC5A : _________ TIC5B : _________ TIC6A : _________ TIC6B : _________ SYSTEM OPERATOR CONSOLES: SOC1A : _________ SOC1B : _________ SOC2A : _________ SOC2B : _________ ___ ___ System: ______

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


At: _______________________ BAPB node name : _________ PACIFIC INDIAN : ______________ : ______________ ___ ___ Page 2 of 3

Service State Service State Service State Service State Service State Service State Service State Service State Service Service Service Service Service Service Service Service Service Service Service Service Service Service Service Service State State State State State State State State State State State State State State State State

: ______________ : ______________ : ______________ : ______________ : ______________ : ______________ : ______________ : ______________ : : : : : : : : : : : : : : : : ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________

4-41

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


BAP CONFIGURATION System: ______ : : : : : : : : : : : : _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ UNITS: _________ _________ _________ _________ : : : : : : : : : : : : : : : : : : At: _______________________ Switch Switch Switch Switch Setting Setting Setting Setting State State State State State State State State : : : : : : : : : : : : ____ ____ ____ ____

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


Page 3 of 3

DEMSA PAIR NAMES: DEMSA 1 pair DEMSA 2 pair DEMSA 3 pair DEMSA 4 pair DEMSA NODE NAMES: DEMSA 1A DEMSA 1B DEMSA 2A DEMSA 2B DEMSA 3A DEMSA 3B DEMSA 4A DEMSA 4B

Service Service Service Service Service Service Service Service

______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________

FACSIMILE TRANSMISSION FTU 1 port : FTU 2 port : FTU 3 port : FTU 4 port :

Service Service Service Service

State State State State

: : : :

______________ ______________ ______________ ______________

PSDN INTERFACE: X.25 Destination Name X.400 Destination Name X.25 Low Sub-Address X.25 High Sub-Address X.400 Sub-Address DEMSA Poll Timer PSI Network PSI DEMSA Pair Number LES DTE Address X25 Line Fail Retry KERMIT INTERFACE: Maximum Packet Size Number of Pad Characters Pad Character Control Prefix Character Binary Prefix Character End of Line Character Number of Retries Timeout

_________ _________ _________ _________ _________ _________ _________ _________ ______________ ________ _________ _________ _________ _________ _________ _________ _________ _________

4-42

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

4.1.9 Installation Template Example


BAP CONFIGURATION System: VAXB : : : : CES BAP SOC MEXICO At: 11-OCT-1993 07:24:11.96 Operational Disk Operational Account Operational Group Page 1 of 3

Project Name Processor Name Operator Name Customer Name

: $1$DIA3: : BAPSYS : 125

RELEASE: Release Number : 8011 Release Disk Release Date : 16-JUN-1996 16:39:39.19 NAMES: BAP name (BAPA/BAPB) DEVICES: Arbiter Device 1st Shadow Set 1st Shadow Set Disk 1 2nd Shadow Set 2nd Shadow Set Disk 1 MAR File Disk OFDB Disk Spool Tape PRINTERS: Alarm Printer 1 Alarm Printer 2 Alarm Printer 3 Alarm Printer 4 Alarm Printer 5 Alarm Printer 6 Alarm Printer 7 Alarm Printer 8 Alarm Printer 9 Offline Report Queue Online Report Queue CHANNEL UNIT CUC1 CUC2 CUC3 CUC4 SWITCHES: Switch Device Switch Device Switch Device Switch Device : BAPB : : : : : : : : TXA0: DSA1: $1$DIA1: DSA2 $1$DIA3: DSA2 $1$DIA5: MKA500:

: $1$DIA3:

Current Region : PACIFIC

1st Shadow Set Disk 2 : $1$DIA2 2nd Shadow Set Disk 2 : $1$DIA4 Quorum Disk : $1$DIA5 Cartridge Tape : MKA500: UTC Device : UNDEFINED

: : : : : : : : : : : : : : : : : : : : : : : : : :

LTA1: LTA2: UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED REPORT$PRINTER UNDEFINED UNDEFINED UNDEFINED TXA2: TXA3: TXA4: TXA5: UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED TXA1: UNDEFINED UNDEFINED UNDEFINED

TELEX INTERFACE SWITCHES: TIC1 Switch Device TIC2 Switch Device TIC3 Switch Device TIC4 Switch Device TIC5 Switch Device TIC6 Switch Device COB1 Switch Device DEMSA SWITCHES: Demsa Port Demsa Port Demsa Port Demsa Port 1 2 3 4 Device Device Device Device

4-43

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


BAP CONFIGURATION BAPS: BAPA node name : VAXA OCEAN REGIONS: WEST : OUT_OF_SERVICE ATLANTIC : IN_SERVICE CHANNEL UNIT CONTROLLERS: WEST: CUC1A : UNDEFINED CUC1B : UNDEFINED ATLANTIC: CUC2A : OTCU2A CUC2B : OTCU2B PACIFIC: CUC3A : UNDEFINED CUC3B : UNDEFINED INDIAN: CUC4A : UNDEFINED CUC4B : UNDEFINED TELEX INTERFACE CONTROLLERS: TIC1A : OTCT1A TIC1B : OTCT1B TIC2A : OTCT2A TIC2B : OTCT2B TIC3A : UNDEFINED TIC3B : UNDEFINED TIC4A : UNDEFINED TIC4B : UNDEFINED TIC5A : UNDEFINED TIC5B : UNDEFINED TIC6A : UNDEFINED TIC6B : UNDEFINED SYSTEM OPERATOR CONSOLES: SOC1A : HADES SOC1B : MIMAS SOC2A : UNDEFINED SOC2B : UNDEFINED 44 44 BAPB node name : VAXB PACIFIC INDIAN System: VAXB At: 11-OCT-1993 07:24:11.96

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


Page 2 of 3

: OUT_OF_SERVICE : OUT_OF_SERVICE

40 40

Service State Service State Service State Service State Service State Service State Service State Service State Service Service Service Service Service Service Service Service Service Service Service Service Service Service Service Service State State State State State State State State State State State State State State State State

: UNDEFINED : UNDEFINED : IN_SERVICE : IN_SERVICE : UNDEFINED : UNDEFINED : UNDEFINED : UNDEFINED : : : : : : : : : : : : : : : : IN_SERVICE IN_SERVICE IN_SERVICE IN_SERVICE UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED IN_SERVICE IN_SERVICE UNDEFINED UNDEFINED

4-44

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


BAP CONFIGURATION System: VAXB : : : : : : : : : : : : OTCD1 UNDEFINED UNDEFINED UNDEFINED OTCD1A OTCD1B UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNITS: UNDEFINED UNDEFINED UNDEFINED UNDEFINED : : : : : : : : : : : : : : : : : :

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


At: 11-OCT-1993 07:24:11.96 Switch Switch Switch Switch Setting Setting Setting Setting State State State State State State State State : : : : : : : : : : : : A A A A IN_SERVICE IN_SERVICE UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED UNDEFINED Page 3 of 3

DEMSA PAIR NAMES: DEMSA 1 pair DEMSA 2 pair DEMSA 3 pair DEMSA 4 pair DEMSA NODE NAMES: DEMSA 1A DEMSA 1B DEMSA 2A DEMSA 2B DEMSA 3A DEMSA 3B DEMSA 4A DEMSA 4B

Service Service Service Service Service Service Service Service

FACSIMILE TRANSMISSION FTU 1 port : FTU 2 port : FTU 3 port : FTU 4 port :

Service Service Service Service X25LES X400LES 00 00 99 60.0 OTCD_A 1 226020 10 80 0 32 (" ") 35 ("#") 38 ("&") 13 3 60

State State State State

: : : :

UNDEFINED UNDEFINED UNDEFINED UNDEFINED

PSDN INTERFACE: X.25 Destination Name X.400 Destination Name X.25 Low Sub-Address X.25 High Sub-Address X.400 Sub-Address DEMSA Poll Timer PSI Network PSI DEMSA Pair Number LES DTE Address X25 Line Fail Retry KERMIT INTERFACE: Maximum Packet Size Number of Pad Characters Pad Character Control Prefix Character Binary Prefix Character End of Line Character Number of Retries Timeout

4-45

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

4.2 SOC Installation This section describes the installation of LES software on the SOC. If this is the first time the LES software is being installed on the system, then skip the following section and continue from section 4.2.2. 4.2.1 Deinstallation of Existing SOC Log into the operational account (SOCSYS) on the SOC where the LES software is to be installed. If it is not possible to see the monitor or if there is some doubt as to whether the system has been stopped previously, check if the system is currently running by entering: $ SHOW LOGICAL SOC$START One of the following should be displayed: 1. "SOC$START" = "STARTING" 2. "SOC$START" = "STARTED" 3. %SHOW-S-NOTRAN, no translation for logical name SOC$START If the result is 1 or 2 then you must stop the SOC. To perform an upgrade of a live redundant system, you should follow the procedure in Chapter 6.2. Otherwise, install the first SOC which is not in use at present. At this point broadcast a message to all other users warning them about the impending installation: $ REPLY/ALL/BELL/SHUTDOWN "LES software installation - please logoff now." To stop the existing software running on the SOC enter: $ STOPSOC At this point the workstation screen will switch temporarily from colour to monochrome in order to display an operator message about the SOC being stopped in a few lines of the operator console window. You can either wait the 30 seconds for it to timeout and continue by itself or you can hit the F2 key marked Operator Window which will cancel the timeout immediately. The following will then be displayed:

4-46

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

-------------------------------------------------------------------------------Stopping the SOC -------------------------------------------------------------------------------Terminal _CASTOR$OPA0: has been notified. -------------------------------------------------------------------------------Stopping processes -------------------------------------------------------------------------------... ... ... ... ... ... ... stopped stopped stopped stopped stopped stopped stopped process process process process process process process SOC_SRV_TASK_01 SOC_FKI_TASK_01 SOC_FRM_TASK_02 ERRLOG_01 MC_LOGGER_P_01 PRC_ARB_01 PIPM_ATL

*** SOC stopped Process# Process Name 27200260 SOCSYS_02 Terminal RTA1: Image [SOCSW.REL7203.SAD.EXECUTE]SAD_SHOW_GROUP_P.EXE

Wait until the command line prompt appears again after the list of stopped processes. The procedure will continue to force the images running in the processes to exit until the processes have terminated. If the procedure appears to come to a stop then break out using Control-C or Control-Y and try again. This step must be completed successfully before proceeding. Now ensure that all other operators have logged off by entering: $ SHOW USERS/FULL Only the account (SOCSYS) should be logged in. If not give a final warning as above and then for each process enter (take note of which operator you are by typing Control-T): $ STOP (PROCESS NAME) This will not work for other users who are not in the same group as the operational account. To force these users to logout use: $ STOP/ID=(PROCESS ID) Next the installed images must be de-installed by entering: $ DEINSTALLSOC The following will be displayed whilst the installed images are deinstalled:
-------------------------------------------------------------------------------Deleting SOC global sections -------------------------------------------------------------------------------... SOC global sections deleted -------------------------------------------------------------------------------Deinstalling SOC images -------------------------------------------------------------------------------... deinstalling CDMC ... deinstalling DIM_LINK_MGR_P ... deinstalling DIM_SHARE

4-47

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


... ... ... ... ... ... ... ... ... ... deinstalling ERR deinstalling ERRMC deinstalling MC_MC_IF deinstalling NRA deinstalling SAD_BAP_IMAGE_P deinstalling SAD_SHARE deinstalling UTL deinstalling UTLDATA deinstalling UTLTRCFLG SOC images deinstalled

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

It is possible that during this procedure errors referring to installed images still being in use can appear. For example:
%DELETE-W-FILNOTDEL, error deleting DSA3:[SOCSYS.INSTALL]ERR125.EXE;1 -RMS-E-FLK, file currently locked by another user

If such a message appears ensure that the relevant file is deleted from the area defined by the logical SOC$INS: $ DELETE SOC$INS:.;/LOG The de-installation of the installed images should result in all the files in the SOC$INS area being deleted. If files remain in this area they will have no detrimental effect upon any subsequent system startup. Issuing the above DELETE command only deletes copies of the originals which are held with the rest of the LES software. If any files cannot be deleted then they still have a real reference most likely from a remaining user logged onto the system using a test program. In this case they must be logged off before the installed image file can be deleted. To determine which process has a reference to this file enter: $ SHOW DEVICE/FILES You can then use the STOP/ID command above to force them to logout. Now enter the following: $ SHOW LOGICAL REL Make a note of the values of the logicals SOC$REL_DISK and SOC$REL_NAME, you will need them later. The first is the disk where the existing software is installed - you should install the new software on the same disk. The second is the release number for that software. Then enter: $ SHOW LOGICAL RUN Make a note of the value of the logical SOC$RUN_DISK as above. This is the disk where the operational accounts areas are held. In ALL cases this MUST be the same disk as the disk holding the software, if not then the software previously installed could not have possibly worked. In this case you must choose between the two values of SOC$REL_DISK and SOC$RUN_DISK and specify only one value for both logical names during this new installation. Deassign group images:
4-48

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

$ DEASSIGN/GROUP/ALL If any fixes have been installed in the COMDEV area, this must be cleaned out with: $ SET DEFAULT SYS$LOGIN $ DELETE [SOCSYS.COMDEV...].;/LOG Now logout of the operational account by entering: $ LOGOUT The installation procedures allow more than one release of software to reside on the system at once. This can allow a new set of software to be tested before removing the old set. Currently there is sufficient disk space on a SOC workstation with 104 Mb RZ23 disks to keep three sets installed at any one time. The disk space requirements for a particular build will be stated in its release notes. If there is not enough space for another set of software and since the oldest set of existing software will not be replaced by the new installation, it must be deleted by hand. The steps do do this are listed below If there is sufficient space then go to 4.2.2. Login into the SOC as (SYSTEM) and enter: $ SET DEFAULT SOC$SYSTEM:[RELnnnn] (Where nnnn is the oldest release number.) $ DELETE [...].;/LOG (Three times to delete the directories as well.) $ SET DEFAULT [-] $ SET PROT RELnnnn.DIR This will set the delete privilege on this file. $ DELETE RELnnnn.DIR;/LOG 4.2.2 Installation of New SOC If this installation is the first to occur since a VMS installation then certain hardware and software configuration information should be obtained prior to performing the installation. If this is not possible then the installation can be performed and the configuration information setup later (see section 4.2.5). Following release 80140, much of this information gathering is now automatic. A minimum amount of information must be obtained before the installation can take place. This includes: Project name - this is always CES and is now not required to be entered. Processor name - this is SOC, PROJECTINSTALL now detects the processor type and automatically applies this. Release number - this should be marked on the tape and should be included in the release notes provided with the release. The number must contain four digits, e.g. 8011.
4-49

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

This information can now be obtained automatically from either: The release tape label if already inserted in the appropriate drive. The directory name if the source file location is on disk. The number determined in this way is offered as the default, and may be ignored if neccessary. Location of release software - this will usually be the tape drive device name, but it may also be a disk device either locally or on a remote machine. The following formats are allowed: Mmcu: - tape device name, e.g. MKA500: Ddcu:[path] - local disk device name, e.g. DKA200: - if the path is omitted the default will be [CES.RELnnnn], e.g. [CES.REL1050] remote disk device name, e.g. node::$a$Ddcu:[path] EARTH::$1$DUA0: - if the path is omitted the default will be [CES.RELnnnn], e.g. [CES.REL1050] (NOTE: for this to work a proxy login of the form ::account/DEFAULT must exist on the remote node where the account is the same as the account you will be using to do the installation on the target machine. Currently the installation procedures do not support access control strings.) A list of currently available drives will be presented. In the case where only one drive is available, then this will be offered as the default. If a disk location is specified, then this will be searched for any installation files. In this case, a list of all (if any) valid releases will be offered for selection. Location of installed software - this will usually be the local user disk device name, but it could be another local disk. Format is Ddcu:, e.g DKA300:. (Note: if space allows more than one set of software to be installed, all the sets must held on one disk, otherwise it will not be possible switch between different sets of software solely by changing the software configuration (see section 4.2.5)). Account group numbers - there are four accounts created by a new software installation. They are arranged in two groups with two accounts in each group. These groups must not be the same as any existing account groups. Suggested group numbers are 125 and 126. For more details see Appendix A. From Release 80140, it will no longer be neccessary to verify the details for each account. The default is to accept them all unchanged. In the rare instance that a change is required, then each account will be presented, in turn, for verification. NOTE: The disk chosen to hold the LES software MUST be the same as the disk containing the operational accounts areas (for example DKA300:). In fact these two names MUST be exactly the same. If this is not the case, all SOC processes will fail on startup.

4-50

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

4.2.2.1 SOC system information for new installations only Other hardware and software configuration information can be specified during installation or alternatively it can be specified prior to system startup (see section 4.2.5). Some of this information is obtained from answers to questions put to you during the installation procedure. This information includes: Release number and location of installed software. Names of logical processor and Pipe Manager network. BAP node names. If you intend to supply this information during the installation procedure then you should collect the information on a configuration sheet such as that shown in section 4.2.6. For guidance see the example in section 4.2.7. If you intend to supply this information after the installation then it is possible to enter null values during the procedure and then you can then supply the real values later (see section 4.2.5). Now login to the (SYSTEM) account (if not already). If the released software is on DAT tape then skip to 4.2.3. If the released software is on tape then you should now check that tape drive in the external expansion box is correctly connected to the workstation. If this is not the case, plug it into the relevant socket (see the System Manager) and enter: $ MC SYSGEN AUTOCONFIGURE ALL to inform the workstation that a new device has been introduced. NOTE: Take care when connecting and disconnecting expansion boxes to and from workstations. When connecting an expansion box to the workstation the correct sequence of events should be: 1. Shut down VMS. Refer to section 3.2 for instructions. 2. Turn the system unit off. 3. Remove the SCSI cover. 4. Remove the SCSI terminator. 5. Set the terminator and cover aside. 6. Connect the small 68-pin end of the connector cable into the system unit SCSI port. 7. Turn the expansion box on. 8. Turn the system unit on. 9. Boot VMS. Refer to section 3.2 for instructions.

4-51

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

When disconnecting an expansion box from the workstation the correct sequence of events should be: 1. Shut down VMS. Refer to section 3.2 for instructions. 2. Turn the system unit off. 3. Turn the expansion box off. 4. Dis-connect the small 68-pin end of the connector cable from the system unit SCSI port. 5. Insert the SCSI terminator. 6. Replace the SCSI cover. 7. Turn the system unit on. 8. Boot VMS. Refer to section 3.2 for instructions. For further details see the Chapter on the use of Expansion Boxes in reference [3]. 4.2.3 Install SOC software You should now load the tape into the tape drive. If the tape drive unit has load/unload or online controls ensure that the tape is loaded and that the tape drive is online to allow it to be controlled by the computer. Much of the information described below will be determined automatically in PROJECTINSTALL from release 80140 onwards. The descriptions below have been included to aid understanding of the requirements for an installation. To find out the name of the local tape drive name enter: $ SHOW DEVICE MK the resulting display should look like:
Device Name EUROPA$MKA500: Device Status Online Error Count 0 Volume Label Free Trans Mnt Blocks Count Cnt

In this case the tape device is called MKA500:. If the released software is on disk then the user should check that the disk is mounted and available for use. Now enter the following: $ SET DEFAULT SYS$MANAGER $ PURGE/LOG Then enter the following if loading from a local tape device: $ BACKUP/NEW/LOG (TAPE):PROJINSTALL.SAV (Tape save set)
4-52

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

Or one of the following if the saveset is on disk. It may be more convenient to copy the PROJINSTAL.SAV and SOCSW.SAV files from tape to a directory [CES.RELnnnn] on a BAP or another SOC. This may be required if, for example a portable tape drive is required, but not available, or where the SOC requires a TK or TF tape and the SOC s/w is supplied on a DAT tape with the BAP s/w. $ BACKUP/NEW/LOG (DISK):[CES.RELnnnn]PROJINSTALL.SAV/SAV Local disk save set where nnnn is the new release number. $ BACKUP/NEW/LOG (NODE)::(DISK):[CES.RELnnnn]PROJINSTALL.SAV/SAV Remote disk save set where nnnn is the new release number. In all cases ensure that there is a space immediately preceeding the asterisk (). The /NEW qualifier must be included in the backup command to ensure the files are created in the directory with version numbers higher than any existing files. The following files will be created in the default area: SYS$SYSROOT:[SYSMGR]PROJECTINSTALL.COM SYS$SYSROOT:[SYSMGR]BAPINSTALL.COM SYS$SYSROOT:[SYSMGR]CESINSTALL.COM SYS$SYSROOT:[SYSMGR]FEPINSTALL.COM SYS$SYSROOT:[SYSMGR]SOCINSTALL.COM To initiate the installation procedure enter: $ @PROJECTINSTALL The following messages and prompts will be displayed (example responses are shown enclosed in <> ) It is assumed that this is NOT a first time installation (this would normally be performed by HNS Staff). However where appropriate, details for an initial installation are described. <N> is sometimes used where <> will suffice in order to show the options available.
Enter disk/tape (e.g., LES$DISK0, MKA500, <System>::<Disk Device>) where release software resides MKA500: <CBAPA::$1$dia4> -- Should be the location of the SOCSYS.SAV saveset. -- for tape save sets, it is the tape logical unit, -- for disk save sets, it is the pathname of the directory. -- Note: Include the Node Name but NOT the Access Control String. -- The example is for a location on a BAP. This is often a quicker -- option where a SOC has a removeable tape drive which needs to be -- fitted, or where the release has been made on a DAT tape and has -- been copied from tape to a BAP disk in advance. -- Having specified the location, then, as for the BAP installation -- an attempt will be made to identify the release number from either -- the tape label or directory names on the specified disk -----------------------------------------------------------------------------5 directories have been found. 1 - 8011

4-53

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

2 - 8013 3 - 8014 4 - 8015 5 - 8888 Enter the line number of the required release 1 - 5 ,Q to exit, or Return to accept the default [8888] <5> The existing release was 8013. Is 8888 the correct new release ? Y/N <Y> -- In this example the BAP disk contains more than one possible -- release. The highest numberd will be offered as the default -----------------------------------------------------------------------------Current SOC release 8013 is being superceded by 8888 copied from CVAXA::$1$DIA4 Enter disk on which release is to be installed [LES$DISK0]: <> -- LES$DISK0 is the normal location for the installed software. -- However, as some SOCs may not have been set up to use this, verify -- whether or not this definition exists before installation. If the -- logical does not exist, then use the disk number instead -------------------------------------------------------------------------------Checking existence of processor system account --------------------------------------------------------------------------------

... SOCSW account exists - UIC = [100,1] -- If the SOCSW account did not exist then it would be created -- at this point. The installer would be prompted for an account -- group and member number. -------------------------------------------------------------------------------Backing up release software -------------------------------------------------------------------------------*** Backing up release from MKA500:SOCSW.SAV to DKA300:[SOCSW.REL<8011>...] Continue? ([Y],N,Skipbackup): <Y> -- The actual location names entered will be shown here ... deleting any existing release 8011 software ... backing up release 8011 software %BACKUP-S-CREDIR, created directory DKA300:[SOCSW.REL8011.<component>.EXECUTE] %BACKUP-S-CREATED, created DKA300:[SOCSW.REL8011.<component>.EXECUTE]<file> : : : : : : : : : %BACKUP-S-CREDIR, created directory DKA300:[SOCSW.REL8011.<component>.EXECUTE] %BACKUP-S-CREATED, created DKA300:[SOCSW.REL8011.<component>.EXECUTE]<file> : : : : : : : : : %BACKUP-S-CREDIR, created directory DKA300:[SOCSW.REL8011.000000] %BACKUP-S-CREATED, created DKA300:[SOCSW.REL8011.000000]BASELINE.DAT;1 -------------------------------------------------------------------------------Copying VAX definition files to SYS$MANAGER -------------------------------------------------------------------------------%BACKUP-S-CREATED, created SYS$SYSROOT:[SYSMGR]SADSTARTUP.COM;24 Do you want to reuse all existing CES accounts ? ([Y]/N): -- Normall all existing accounts can be accepted en masse and -- installation will contine from Defining VAX devices below -------------------------------------------------------------------------------Defining CES operational account to be used -------------------------------------------------------------------------------Do you want to reuse an existing operational CES account ? ([Y]/N): <> Enter disk device of existing CES account [LES$DISK0:]: <>

4-54

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

Enter name of existing CES account [SOCSYS]: <> -- In an initial installation a new CES operational account -- would have to be specified. After entering <N> to the -- first prompt, the installer would be prompted for -- disk device, account name and account group and member number. -------------------------------------------------------------------------------Defining CES maintenance account to be used -------------------------------------------------------------------------------Do you want to reuse an existing maintenance CES account? ([Y],N): <> Enter disk device of existing CES account [LES$DISK0:]: <> Enter name of existing CES account [SOCSYS]: <> -- In an initial installation a new CES maintenance account -- would have to be specified. After entering <N> to the -- prompt, the installer would be prompted for -- account name and account member number. -------------------------------------------------------------------------------Defining CES captive account to be used --------------------------------------------------------------------------------- This is the captive account on the SOC that is used for -- running the SOC VIEWER. Do you want to reuse an existing captive CES account? ([Y],N): <> Enter name of existing CES account [SOCV]: <> -- In an initial installation a new CES captive account -- would have to be specified. After entering <N> to -- the prompt, the installer would be prompted for account -- name and account member number. -------------------------------------------------------------------------------Defining VAX devices --------------------------------------------------------------------------------- During a normal installation no prompt appears here. -- However if it is a first time installation the installer -- is prompted whether or not the CES VAX devices are to be -- redefined. If the installer replies <Y> then a list of -- disk devices that may hold project software and the report -- generation printer queue is prompted for. -------------------------------------------------------------------------------Defining SOC parameters --------------------------------------------------------------------------------- The following question (defaulted to YES) in order to force -- the creation of a new DEFSAD.COM using the new parameters -- From release 80140 the insertion of these parameters is now -- fully automatic and the installation process resumes, after first -- displaying a list of the automated updates, at -- "Creating CES definition file SYS$LOGIN:DEFSAD.COM " -- below. -- In some circumstances, though the majority of these parameters -- will all be correct for the new release, some manual changes may -- be required. In this case enter N for manual update, and correct -- those entries which require change. -- DEFSAD.COM will now contain a logical defining the load file type -- for each CU FEP. Consequently SADREDEF will need to be run to -- enter these definitions the first time an 8014 release is -- installed. The system logicals can be automatically updated for this release using information already available If non-routine changes are required then the logicals should be updated manually, accepting all other defaults offered. Refer to the release notes Under normal circumstances, automatic update is recommended

4-55

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


Do you wish to accept automatic updates alone Y/N? [Y] <> -- The normally required response has been shown. In which case -- the updated DEFSAD information will be displayed, as is listed -- below, but without pausing for operator responses.

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Do you want to change SOC (SADREDEF) configuration ? (Y/[N]): Y When prompted for input, enter data according to the configuration you require. Some prompts display a default reply [shown in brackets]. To use the default, press the RETURN key. To replace default data, enter the new data to be used. To cancel the use of default data without entering new data, enter the backslash (\) character. You will have the opportunity to review and correct your responses before actually creating DEFSAD.COM. RELEASE: Release Number: Release Disk : 8011 LES$DISK0:

* Is this information correct? (Y/N) [Y]: <> NAMES: Processor Name: Current Region: SOCB ATLANTIC

* Is this information correct? (Y/N) [Y]: <> BACKGROUND APPLICATIONS PROCESSORS: BAPA: BAPB: CBAPA CBAPB

* Is this information correct? (Y/N) [Y]: <> -------------------------------------------------------------------------------Creating CES definition file SYS$LOGIN:DEFSAD.COM --------------------------------------------------------------------------------------------------------------------------------------------------------------Creating CES report file SYS$LOGIN:CONFIGURATION.TXT -------------------------------------------------------------------------------*** SOC parameter definition complete Does this workstation support Motif? (Y/N) - [x]: <> -- The default X (Y or N will be supplied in accordance -- with what PROJECTINSTALL is able to determine about the SOC -- Reply Yes ONLY if this workstation supports MOTIF Otherwise enter N. ) -------------------------------------------------------------------------------Copying Workstation Options window definition file to SYS$MANAGER -------------------------------------------------------------------------------%BACKUP-S-CREATED, created SYS$SYSROOT:[SYSMGR]UISBG.DAT;24 *** A reboot is required for this file to take effect

4-56

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

-------------------------------------------------------------------------------Renaming font load files for TDMS form windows in SYS$FONT -------------------------------------------------------------------------------*** SOC specific installation of release <8011> complete -------------------------------------------------------------------------------HNS strongly recommends that this processor is rebooted. -------------------------------------------------------------------------------Do you want to reboot the SOC processor? ([Y]/N): <> *** PROJECTINSTALL of SOC release 8011 complete -------------------------------------------------------------------------------Invoking SHUTDOWN to reboot the system -------------------------------------------------------------------------------SHUTDOWN -- Perform an Orderly System Shutdown on node EUROPA -- The following prompt may not appear, -- depending on how the system is configured. Do you really want to shutdown node EUROPA [NO]? <Y> %SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check... %SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed %SHUTDOWN-I-BRDOPROFF, Broadcasts to the operator window have been disabled. %SHUTDOWN-I-OPERATOR, This terminal is now an operators console. %SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled. %%%%%%%%%%% OPCOM 5-MAR-1992 15:38:47.42 %%%%%%%%%%% Operator _EUROPA$RTA1: has been enabled, username SYSTEM %SET-I-INTSET, login interactive limit = 0, current interactive value = 3 %%%%%%%%%%% OPCOM 5-MAR-1992 15:38:47.69 %%%%%%%%%%% Operator status for operator _EUROPA$RTA1:CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, LICENSE,OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11,OPER12 %SHUTDOWN-I-SHUTNET, The DECnet network will now be shut down. %SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped. SHUTDOWN message on EUROPA from user SYSTEM at _EUROPA$RTA1: 15:38:52 EUROPA will shut down in 0 minutes; back up soon. Please log off node EUROPA. Reboot system with AUTOGENerated parameters 3 terminals have been notified on EUROPA. %SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked. %SHUTDOWN-I-STOPUSER, All user processes will now be stopped. %SHUTDOWN-I-REMOVE, All installed images will now be removed. %SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted. %SHUTDOWN-I-STOPAUDIT, stopping the audit server %%%%%%%%%%% OPCOM 5-MAR-1992 15:39:08.85 %%%%%%%%%%% Message from user SYSTEM on EUROPA _EUROPA$RTA1:, EUROPA shutdown was requested by the operator. %%%%%%%%%%% OPCOM 5-MAR-1992 15:39:09.41 %%%%%%%%%%% Logfile was closed by operator _EUROPA$RTA1: Logfile was EUROPA::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;49 %%%%%%%%%%% OPCOM 5-MAR-1992 15:39:09.93 %%%%%%%%%%% Operator _EUROPA$RTA1: has been disabled, username SYSTEM

The system will automatically reboot and the installation of the SOC is complete. 4.2.3.1 Configuring the SOC ID on the BAP The SOC ID must be configured on the BAP. This can be done during BAP install 4.1.2. To reconfigure the SOC id on the BAP outside an installation, log into account (BAPSYS) on the BAP and enter:
4-57

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

$ @SAD$EXE:SADREDEF This gives the response:


When prompted for input, enter data according to the configuration you require. Some prompts display a default reply [shown in brackets]. To use the default, press the RETURN key. To replace default data, enter the new data to be used. To cancel the use of default data without entering new data, enter the backslash (\) character. You will have the opportunity to review and correct your responses before actually creating DEFSAD.COM. -- The file offers the same prompts displayed during a BAP install. Respond with <> until the prompt for the SOC IDs are offered. Then follow the example below (here replacing ARIEL with DEIMOS): SYSTEM OPERATOR CONSOLES: SOC1A: SOC1B: SOC2A: SOC2B: ARIEL PHOBOS UNDEFINED UNDEFINED Service Service Service Service State: State: State: State: IN_SERVICE IN_SERVICE UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <N> * Enter node name of SOC1A, e.g. SOC01A? [ARIEL]: <DEIMOS> * Enter service state of SOC1A, e.g. IN_SERVICE? (IN_SERVICE/OUT_OF_SERVICE) [IN_SERVICE]: <> * Enter node name of SOC1B, e.g. SOC01B? [PHOBOS]: <> * Enter service state of SOC1B, e.g. IN_SERVICE? (IN_SERVICE/OUT_OF_SERVICE) [IN_SERVICE]: <> * Enter node name of SOC2A, e.g. SOC02A? [UNDEFINED]: <> * Enter node name of SOC2B, e.g. SOC02B? [UNDEFINED]: <> SOC1A: SOC1B: SOC2A: SOC2B: DEIMOS PHOBOS UNDEFINED UNDEFINED Service Service Service Service State: State: State: State: IN_SERVICE IN_SERVICE UNDEFINED UNDEFINED

* Is this information correct? (Y/N) [Y]: <>

4.2.3.2 Problems during an initial installation Unlike an upgrade, an initial installation invokes AUTOGEN to set system parameters prior to the final reboot. If any problems are encountered, then instead of rebooting the system displays the message:
-------------------------------------------------------------------------------AUTOGEN detected errors with the system parameters specified in the file SYS$SYSTEM:MODPARAMS.DAT. A report detailing these problems follows. --------------------------------------------------------------------------------

followed by a page by page report such as:


AUTOGEN Parameter Calculation Report on node: EUROPA This information was generated at 27-FEB-1992 16:27:12.83 AUTOGEN was run from GETDATA to REBOOT using NOFEEDBACK Processing Parameter Data files ------------------------------Including parameters from: SYS$SYSTEM:MODPARAMS.DAT

4-58

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

The following problems were detected within MODPARAMS.DAT These problems should be reviewed immediately. ** WARNING ** - Multiple MIN values found for MIN_NPAGEDYN. Using MODPARAMS value (900096) which is superseding VMS value (419840) ** WARNING ** - Multiple MIN values found for MIN_GBLPAGES. Using MODPARAMS value (120000) which is superseding VMS value (17600) ** WARNING ** - Multiple MIN values found for MIN_GBLSECTIONS. Using MODPARAMS value (600) which is superseding VMS value (512) ** WARNING ** - Multiple MIN values found for MIN_GBLPAGFIL. Using VMS value (17600) which is superseding MODPARAMS value (10000) ** WARNING ** - Multiple MIN values found for MIN_MAXBUF. Using MODPARAMS value (4096) which is superseding VMS value (2048) ** WARNING ** - Duplicate values for MIN_SWAPFILE found. Records were defined by MODPARAMS and VMS to set symbol to 6000 This run of AUTOGEN is *NOT* based on FEEDBACK information. The resulting calculations may not be representative of your workload. DIGITAL recommends the use of feedback to adjust system resources to match system workloads. Parameter information follows: -----------------------------MAXPROCESSCNT parameter information: Override Information - parameter calculation has been overriden. The calculated value was 29. The new value is 64. MAXPROCESSCNT is not allowed to be less than 64. VIRTUALPAGECNT parameter information: Override Information - parameter calculation has been overriden. The calculated value was 24384. The new value is 40000. VIRTUALPAGECNT is not allowed to be less than 40000. Information on VMS executable image Processing: ** ERROR ** - The file SYS$MANAGER:VMS$IMAGES_MASTER.DAT was not found. AUTOGEN will *NOT* be able to create VMSIMAGES.DAT. Please correct this problem before rebooting your system. Endphase has been changed to TESTFILES GBLPAGFIL parameter information: Override Information - parameter calculation has been overriden. The calculated value was 1024. The new value is 17600. GBLPAGFIL has been increased by 12000. GBLPAGFIL is not allowed to be less than 17600. GBLPAGES parameter information: Override Information - parameter calculation has been overriden. The calculated value was 28800. The new value is 120000. GBLPAGES is not allowed to be less than 120000. GBLSECTIONS parameter information: Override Information - parameter calculation has been overriden. The calculated value was 230. The new value is 630. GBLSECTIONS has been increased by 400. GBLSECTIONS is not allowed to be less than 600. SRPCOUNT parameter information: Override Information - parameter calculation has been overriden. The calculated value was 684. The new value is 1024. SRPCOUNT is not allowed to be less than 1024. LRPCOUNT parameter information: Override Information - parameter calculation has been overriden. The calculated value was 16. The new value is 50. LRPCOUNT is not allowed to be less than 50.

4-59

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

NPAGEDYN parameter information: Override Information - parameter calculation has been overriden. The calculated value was 498395. The new value is 900096. NPAGEDYN has been increased by 300000. NPAGEDYN is not allowed to be less than 900096. BALSETCNT parameter information: Override Information - parameter calculation has been overriden. The calculated value was 57. The new value is 64. BALSETCNT is not allowed to be less than 64. PAGEDYN parameter information: Override Information - parameter calculation has been overriden. The calculated value was 1482267. The new value is 3184667. PAGEDYN has been increased by 1702400. PAGEDYN is not allowed to be less than 3072000. SPTREQ parameter information: Override Information - parameter calculation has been overriden. The calculated value was 2500. The new value is 3200. SPTREQ has been increased by 700. SPTREQ is not allowed to be less than 2500. SYSMWCNT parameter information: Override Information - parameter calculation has been overriden. The calculated value was 1159. The new value is 1459. SYSMWCNT has been increased by 300. WINDOW_SYSTEM parameter information: Override Information - parameter calculation has been overriden. The calculated value was 0. The new value is 2. WINDOW_SYSTEM has been disabled by a hard-coded value of 2. PROCSECTCNT parameter information: Override Information - parameter calculation has been overriden. The calculated value was 32. The new value is 64. PROCSECTCNT is not allowed to be less than 64. Page, Swap, and Dump file calculations Page and Swap file calculations. PAGEFILE parameter information: Override Information - parameter calculation has been overriden. The calculated value was 27600. The new value is 40000. PAGEFILE is not allowed to be less than 40000. PAGEFILE will not be modified. SWAPFILE parameter information: Override Information - parameter calculation has been overriden. The calculated value was 1900. The new value is 6000. SWAPFILE is not allowed to be less than 6000. SWAPFILE will not be modified. Dumpfile calculations: No dump file modifications would have been made. Dumpfile will remain at 16395 blocks.

If this is the case the following message will appear:


-------------------------------------------------------------------------------You must manually edit the file SYS$SYSTEM:MODPARAMS.DAT to correct the problems reported by AUTOGEN and then reinvoke AUTOGEN using the command $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK --------------------------------------------------------------------------------

You must follow the advice given in the report above and then issue the command: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK
4-60

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

as described. You may need to manually edit SYS$SYSTEM:MODPARAMS.DAT before doing this. Finally, if you elected not to update the system parameters, you may also see:
-------------------------------------------------------------------------------SHUTDOWN detected fatal error whilst attempting to shut the system down. --------------------------------------------------------------------------------

In this case enter: $ @SYS$SYSTEM:SHUTDOWN The following messages and prompts will be displayed (example responses are shown enclosed in <> )
SHUTDOWN -- Perform an Orderly System Shutdown on node EUROPA Do you really want to shutdown node EUROPA [NO]? <Y> How many minutes until final shutdown [0]: <> Reason for shutdown [Standalone]: <> Do you want to spin down the disk volumes [NO]? <> Do you want to invoke the site-specific shutdown procedure [YES]? <> Should an automatic system reboot be performed [NO]? <Y> When will the system be rebooted [shortly via automatic reboot]: <> Shutdown options (enter as a comma-separated list): REBOOT_CHECK Check existence of basic system files SAVE_FEEDBACK Save AUTOGEN feedback information from this boot Shutdown options [NONE]: <REB,SAV> %SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check... %SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed %SHUTDOWN-I-SAVEFEED, Saving AUTOGENs feedback information from this boot... %SHUTDOWN-I-SAVEOK, Feedback info. saved in SYS$SYSTEM:AGEN$FEEDBACK.DAT %SHUTDOWN-I-BRDOPROFF, Broadcasts to the operator window have been disabled. %SHUTDOWN-I-OPERATOR, This terminal is now an operators console. %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:00.47 %%%%%%%%%%% Operator _EUROPA$RTA1: has been enabled, username SYSTEM %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:00.48 %%%%%%%%%%% Operator status for operator _EUROPA$RTA1: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled. %SET-I-INTSET, login interactive limit = 0, current interactive value = 1 %SHUTDOWN-I-SHUTNET, The DECnet network will now be shut down. %SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped. %SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked. SHUTDOWN message on EUROPA from user SYSTEM at _EUROPA$RTA1: 13:32:02 EUROPA will shut down in 0 minutes; back up shortly via automatic reboot. Please log off node EUROPA. Standalone %SHUTDOWN-I-STOPUSER, All user processes will now be stopped. 1 terminal has been notified on EUROPA. %SHUTDOWN-I-REMOVE, All installed images will now be removed. %SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted.

4-61

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation


%SHUTDOWN-I-STOPAUDIT, stopping the audit server %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:06.31 %%%%%%%%%%% Message from user SYSTEM on EUROPA _EUROPA$RTA1:, EUROPA shutdown was requested by the operator. %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:06.86 %%%%%%%%%%% Logfile was closed by operator _EUROPA$RTA1: Logfile was EUROPA::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;12 %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:07.43 %%%%%%%%%%% Operator _EUROPA$RTA1: has been disabled, username SYSTEM

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

NOTE: On rare occasions the VMS SHUTDOWN procedure may not complete. This is usually because it is being used from a remote terminal which is using DECnet. Since DECnet is shutdown during the procedure, the procedure itself can fail. In such cases you should log into a local terminal on the machine and repeat the exercise. If you cannot physically get to the machine to use a local terminal, then access the machine over LAT. If all goes well the installation of the LES software on the SOC is complete. You should now proceed to section 8.2 to startup the SOC. 4.2.4 Currently required additional manual actions This section contains information on extra manual installation steps that are currently required. 4.2.4.1 Setting up the System Usage Displays The system usage displays have to be configured on each SOC. This is achieved by the following steps Log into the operational account (SOCSYS) Enter: $ @SOC$EXE:SOC_GEN_COMMANDS Now the SOC must accept the changes: If the SOC is a VAXStation 3100 it must be rebooted. If the SOC is a Vaxstation 4000 series, the session manager needs to be restarted. 4.2.5 Configuring A New SOC If there is a need to configure a new SOC, for instance a replacement for a faulty SOC or in addition to the current set of SOCs, then the LES configuration must be changed to reflect this. This can be done from the operational account (SOCSYS) by entering: $ @SAD$EXE:SADREDEF This executes a section of the installation procedure (SADREDEF.COM). This will create a new version of SYS$LOGIN:DEFSAD.COM which contains the configuration information. See section 4.1.6.1 below for an example of this procedure.
4-62

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

NOTE: DEFSAD.COM must not be manually changed since there are a great many rules and requirements for consistency which can only be checked if the proper procedure is used. To make use of any changes you have made to the values in this file enter: $ @SYS$LOGIN:DEFSAD followed by: $ @SYS$LOGIN:LOGIN $ @SAD$EXE:SADCONFIGSOC Certain changes may not take effect until the SOC has been stopped and re-started. A file CONFIGURATION.TXT is generated specifically for the operator to read easily. This file will always contain the current configuration information and can be printed in case the information on disk is lost. See the blank sheet and a filled in example in sections 4.2.6 and 4.2.7. The customer name must be entered when the system is started (see section 8.2). If you want to select the startup Telecomunicaciones De Mexico enter: $ @SAD$EXE:SADCONFIGSOC MEXICO This will define logical names and copy customer specific files as necessary. 4.2.5.1 Running DEFSAD.COM on a new SOC This example of the procedure to redefine the DEFSAD parameters is similar to that given in the main body of text for an installation on an existing SOC. In the example below, however, the non default answers have been utilised so as to generate a full set of examples to illustrate the procedure. After entering @SAD$EXE:SADREDEF.COM the question will be asked:
Do you want to change SOC (SADREDEF) configuration ? (Y/[N]): Y When prompted for input, enter data according to the configuration you require. Some prompts display a default reply [shown in brackets]. To use the default, press the RETURN key. To replace default data, enter the new data to be used. To cancel the use of default data without entering new data, enter the backslash (\) character. You will have the opportunity to review and correct your responses before actually creating DEFSAD.COM. RELEASE: Release Number: Release Disk : 8001 LES$DISK0:

customer

without

starting

the

system,

for

* Is this information correct? (Y/N) [Y]: <N> * Enter 4-digit release number, e.g. 0102? [8011]:

4-63

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

* Enter disk on which release 8011 resides, e.g. USER1? [LES$DISK0:]: Release Number: Release Disk : 8011 LES$DISK0:

* Is this information correct? (Y/N) [Y]: <Y> NAMES: Processor Name: Current Region: SOCB ATLANTIC

* Is this information correct? (Y/N) [Y]: <N> * Enter processor name for this SOC, e.g. SOCA? (SOCA/SOCB) [SOCB]: * Enter current region, e.g. ATLANTIC? (WEST/ATLANTIC/PACIFIC/INDIAN) [ATLANTIC] : Processor Name: Current Region: SOCB ATLANTIC

* Is this information correct? (Y/N) [Y]: <> BACKGROUND APPLICATIONS PROCESSORS: BAPA: BAPB: CBAPA CBAPB

* Is this information correct? (Y/N) [Y]: <N> * Enter node name of BAPA, e.g. BAP01A? [CBAPA]: * Enter node name of BAPB, e.g. BAP01B? [CBAPB]: BAPA: BAPB: CBAPA CBAPB

* Is this information correct? (Y/N) [Y]: <> -------------------------------------------------------------------------------Creating CES definition file SYS$LOGIN:DEFSAD.COM --------------------------------------------------------------------------------------------------------------------------------------------------------------Creating CES report file SYS$LOGIN:CONFIGURATION.TXT -------------------------------------------------------------------------------*** SOC parameter definition complete

4-64

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

4.2.6 Installation Template


SOC CONFIGURATION Project Name Processor Name Operator Name Customer Name : : : : System: ______ _________ _________ _________ _________ At: _______________________ Page 1 of 1

Operational Disk (Run Disk) : _________ Operational Account (Run Root) : _________ Operational Group : _________

RELEASE: Release Number : _________ Release Disk Release Date : _______________________ NAMES: SOC name (SOCA/SOCB) BAPS: BAPA node name : _________ BAPB node name : _________

: _________

Current Region : _________ : _________

4-65

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

4.2.7 Installation Template Example


SOC CONFIGURATION Project Name Processor Name Operator Name Customer Name : : : : System: HADES CES SOC SOC MEXICO At: 27-JUL-1992 07:47:19.48 Page 1 of 1

Operational Disk (Run Disk) : DKA300: Operational Account (Run Root) : SOCSYS Operational Group : 125

RELEASE: Release Number : 8011 Release Disk Release Date : 16-JUN-1992 16:39:39.19 NAMES: SOC name (SOCA/SOCB) BAPS: BAPA node name : VAXA : SOCA

: DKA300:

Current Region :ATLANTIC BAPB node name : VAXB

4-66

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Chapter 5 Sybase Product Installation


This chapter provides instructions on installing the Sybase database product prior to installing the LES software. NOTE: The VMS product installation must have taken place before the Sybase product can be installed on a new system. 5.1 Introduction to Sybase Concepts The Sybase installation has been designed to run with the DEC VMSINSTAL utility provided by VMS. To install Sybase insert the SYBASE INSTALLATION tape into the DDS drive on the machine where it is to be installed. From the system account invoke VMSINSTAL using the following command, assuming that the DDS drive is called MKA500:. $ @SYS$UPDATE:VMSINSTAL SYB491 MKA500: This will invoke a standard layered product installation which will automatically extract and execute the KITINSTAL.COM from the first save set on the tape. At this point the procedure has entered the HNS specific installation for Sybase. Following is a sample run of installing the Sybase Dataserver and Report Writer products. The Dataserver is configured for 100 users and a full Sybase Physical device of 110 Mbytes is created ready for PROJECTINSTALL to create the LES database and load it from the basic dump. If a clean installation is required then please ensure that any previous Sybase installation has been removed, including the Sybase account etc. 5.2 Installation of Sybase Kit An example of the system output that results when a Sybase product installation is performed is as follows:
VAX/VMS Software Product Installation Procedure V5.4-1A It is 20-DEC-1991 at 19:03. Enter a question mark (?) at any time for help.

%VMSINSTAL-W-LOWQUOTA, The following account quotas may be too low: BYTLM: currently 9904; minimum expected 32768 ENQLM: currently 100; minimum expected 200 %VMSINSTAL-W-ACTIVE, The following processes are still active: SYSTEM * Do you want to continue anyway [NO]? <Y> -- The following will appear if you are logged into either account. * Are you satisfied with the backup of your system disk [YES]? <Y> Please mount the first volume of the set on MKA500: . * Are you ready? <Y>

5-1

Customer Release Configuration Guide Telecomunicaciones De Mexico Sybase Product Installation


%MOUNT-I-MOUNTED, SYB491 mounted on _NEPTNE$MKA500: The following products will be processed: SYB V4.9.1 Beginning installation of SYB V4.9.1 at 19:05 %VMSINSTAL-I-RESTORE, Restoring product save set A ... *** *** *** HNS Ltd. Sybase Products Installation Procedure. This procedure installs the Sybase Dataserver V4.9.1 and Sybase SQL Toolset V5.2 DWB & RWB products

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

*** *** ***

Do you want to continue with the installation (Y/N) : <Y> Do you want to create/replace the SYBASE account (Y/N) : <Y> -- Y, if this is a first time installation, and if the Sybase account does not exist. *** Please Please Please Please Please Create Sybase Account ... (if applicable) SYBASE SYBASE SYBASE SYBASE SYBASE account name [SYBASE]: <> group number [300]: <> UIC number [3]: <> disk device [SYS$SYSDEVICE:]: <> Identifier [SYBASE]: <> ***

enter enter enter enter enter

Please enter the number of connections L=25, F=100 [F]: <> Do you wish to create a SYBASE account (Y/N)?: <Y> -- <N>, if not first installation or OFDB installation only - skips to dataserver installation section below Remove any existing SYBASE account details... %UAF-W-BADUSR, username does not exist \SYBASE\ %UAF-E-RDBREMERR, unable to remove SYB from rights data base -SYSTEM-F-NOSUCHID, unknown rights identifier Creating SYBASE account configured for 25 user connections... %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier SYBASE value: [000300,000003] added to rights data base %UAF-I-RDBADDMSGU, identifier Sybase value: [000300,177777] added to rights data base %UAF-I-MDFYMSG, user record(s) updated %UAF-I-MDFYMSG, user record(s) updated %UAF-I-MDFYMSG, user record(s) updated %UAF-I-RDBREMMSGU, identifier SYBASE value: [000300,000003] removed from rights data base %UAF-I-RDBREMMSGU, identifier SYBASE value: [000300,177777] removed from rights data base %UAF-I-RDBADDMSGU, identifier SYB value: [000300,177777] added to rights data base %UAF-I-RDBADDMSGU, identifier SYBASE value: [000300,000003] added to rights data base SYBASE account creation complete. Do you want to copy the SYBASE software from tape (Y/N) : <N> *** Defining disks for ONDB & OFDB - showing current diskdrives Device Status Mounted Mounted Mounted ShadowSetMember Error Count 0 0 0 0 ***

Device Name DSA1: DSA2: $1$DIA0: $1$DIA1:

(R5SEGF) (R1AEUI)

Volume Free Trans Mnt Label Blocks Count Cnt USER01 225954 17 2 USER02 312405 3 2 MEBAPA_SYS 601623 344 2 (member of DSA1:)

5-2

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico Sybase Product Installation

$1$DIA2: (R1CINE) ShadowSetMember 0 (member of DSA2:) $1$DIA3: (R1C2AI) Mounted 0 QUORUM 41652 1 $1$DIA4: (R5WIEG) Mounted 0 MEBAPB_SYS 593676 1 $1$DIA5: (R1UDWA) ShadowSetMember 0 (member of DSA1:) $1$DIA6: (R1TKEE) ShadowSetMember 0 (member of DSA2:) $1$DIA9: (R5ULVG) Mounted 0 USER03 248838 1 $1$DKA400: (CVAXA) Online wrtlck 0 Please enter disk for online DB (usually SHADOWSET) e.g. DSA0: : <DSA1:> Please enter disk for offline DB (usually QUORUM) e.g. $1$DIA2: :<$1$DIA3>: *** *** *** *** *** *** *** *** *** *** Creating & executing SYLOGICALS.COM to setup SYBASE logical names Creating interfaces file for ONDB & OFDB servers Creating RUN_ONDB.COM & RUN_M_ONDB.COM files Creating ONDB_QUOTA.DAT file *** *** *** *** ***

2 2 2

Creating RUN_OFDB.COM & RUN_M_OFDB.COM files Creating OFDB_QUOTA.DAT file ***

Creating STOP_ONDB.COM & STOP_OFDB.COM files

*** *** *** ***

Setting directory & file protections and file limits Note that warnings may be given if servers are running or if shared image has been previously installed

%SET-E-READERR, error reading SYS$SYSDEVICE:[SYBASE_491]KITINSTAL.COM -SYSTEM-W-ACCONFLICT, file access conflict %SET-E-READERR, error reading SYS$SYSDEVICE:[SYBASE_491.SYBASE.LIB]SYB_DBSHR.EXE -SYSTEM-W-ACCONFLICT, file access conflict %SET-E-READERR, error reading SYS$SYSDEVICE:[SYBASE_491]KITINSTAL.COM -SYSTEM-W-ACCONFLICT, file access conflict %SET-E-READERR, error reading SYS$SYSDEVICE:[SYBASE_491.SYBASE.LIB]SYB_DBSHR.EXE -SYSTEM-W-ACCONFLICT, file access conflict *** Create SYBASE devices - NOTE !!! This only needs to be run on 1 BAP ***

Do you wish to create the ON-LINE database disk devices ? (Y/N) : <Y> *** Building the ONDB master device ***

Master device: ONDB_491:[SYBASE_491.DEVICES]MASTER_ONDB.DAT creating 5120 page (20480 block) master device File created is CONTIGUOUS BEST TRY writing configuration area writing the MASTER database writing the MODEL database writing allocation pages for remaining 5 MB, (2560 pages) 2 MB 4 MB 5 MB Buildmaster complete *** Starting the ONDB Dataserver ***

Starting the MASTER SQL Server ONDB on node MEBAPA. Runserver file: SYBASE_SYSTEM:[SYBASE.INSTALL]RUN_ONDB.COM Quota values: astlm = 756

5-3

Customer Release Configuration Guide Telecomunicaciones De Mexico Sybase Product Installation


wsextent = 44000 biolm = 756 diolm = 250 wsquota = 44000 wsdefault = 44000 bytlm = 150000 enqlm = 100 fillm = 150 pgflquota = 30000 tqelm = 50 prclm = 15 jtquota = 10100 Base priority: 4 VMS process name: ONDB_SQL MASTER SQL Server State ============================ VMS Process Initialization Kernel Initialization Companion/DBMS Initialization Recovery Started Recovery Complete Successfully started a MASTER SQL Server. *** *** *** Installing the Master Scripts Installing the Model Scripts *** *** ***

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Installing the Serial Number Script

*** ***

Installing new system messages Setting the SA password ***

***

Password changed. (return status = 0) *** Setting the database configuration values for 100 users ***

Configuration option (return status = 0) (1 row affected) Configuration option (return status = 0) Configuration option (return status = 0) Configuration option (return status = 0) Configuration option (return status = 0) Configuration option (return status = 0) ***

changed. Run the RECONFIGURE command to install. changed. Run the RECONFIGURE command to install. changed. Run the RECONFIGURE command to install. changed. Run the RECONFIGURE command to install. changed. Run the RECONFIGURE command to install. changed. Run the RECONFIGURE command to install. ***

Rebooting the Dataserver to take up new config values

Stopping the MASTER SQL Server ONDB Starting the MASTER SQL Server ONDB on node MEBAPA. Runserver file: SYBASE_SYSTEM:[SYBASE.INSTALL]RUN_ONDB.COM Quota Values: astlm = 756 wsextent = 44000 biolm = 756 diolm = 250 wsquota = 44000

5-4

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


wsdefault = 44000 bytlm = 150000 enqlm = 100 fillm = 150 pgflquota = 30000 tqelm = 50 prclm = 15 jtquota = 10100 Base priority: 4 VMS process name: ONDB_SQL MASTER SQL Server State ============================ VMS Process Initialization Kernel Initialization Companion/DBMS Initialization Recovery Started Recovery Complete Successfully started a MASTER SQL Server. ***

Customer Release Configuration Guide Telecomunicaciones De Mexico Sybase Product Installation

Creation of SYBASE device ONDB01 of 110MBytes

***

CREATE A SYBASE LOGICAL DEVICE ============================== *** WARNING This will create the Sybase device as follows:disk init name = "ONDB01", physname = "ONDB_491:[SYBASE_491.DEVICES]ONDB01.DAT", vdevno = "1", size = "56320", (= 110MBytes) Is this correct? Do you wish to continue. Please confirm (Y/N, [N]): <Y>

Creating Sybase device ONDB01. Please wait ... Stopping the MASTER SQL Server ONDB *** Finished creation of ON-LINE SYBASE devices ***

Do you wish to create the OFF-LINE database disk devices ? (Y/N) : <Y> *** Building the OFDB master device ***

Master device: OFDB_491:[SYBASE_491.DEVICES]MASTER_OFDB.DAT creating 9216 page (36864 block) master device File created is CONTIGUOUS BEST TRY writing configuration area writing the MASTER database writing the MODEL database writing allocation pages for remaining 13MB, (6656 pages) 2 MB 4 MB 6 MB 8 MB 10 MB 12 MB 13 MB Buildmaster complete *** Starting the OFDB Dataserver ***

Starting the MASTER SQL Server OFDB on node MEBAPA. Runserver file: SYBASE_SYSTEM:[SYBASE.INSTALL]RUN_OFDB.COM Quota values: astlm = 756 wsextent = 30000

5-5

Customer Release Configuration Guide Telecomunicaciones De Mexico Sybase Product Installation


biolm = 756 diolm = 250 wsquota = 30000 wsdefault = 30000 bytlm = 150000 enqlm = 100 fillm = 150 pgflquota = 30000 tqelm = 50 prclm = 15 jtquota = 10100 Base priority: 4 VMS process name: OFDB_SQL MASTER SQL Server State ============================ VMS Process Initialization Kernel Initialization Companion/DBMS Initialization Recovery Started Recovery Complete Successfully started a MASTER SQL Server. *** *** *** *** *** Installing the Master Scripts Installing the Model Scripts *** *** ***

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Installing the Serial Number Script Installing new system messages Setting the SA password *** ***

Password changed. (return status = 0) *** Setting the database configuration values for 20 users ***

Configuration option changed. Run the RECONFIGURE command to install. (return status = 0) Configuration option changed. Run the RECONFIGURE command to install. (return status = 0) *** Rebooting the Dataserver to take up new config values ***

Stopping the MASTER SQL Server OFDB Starting the MASTER SQL Server OFDB on node MEBAPA. Runserver file: SYBASE_SYSTEM:[SYBASE.INSTALL]RUN_OFDB.COM Quota values: cpulm = 0 astlm = 756 wsextent = 30000 biolm = 756 diolm = 250 wsquota = 30000 wsdefault = 30000 bytlm = 150000 enqlm = 100 fillm = 150 pgflquota = 30000 tqelm = 50 prclm = 15 jtquota = 10100 Base priority: 4 VMS process name: OFDB_SQL MASTER SQL Server State ============================ VMS Process Initialization

5-6

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


Kernel Initialization Companion/DBMS Initialization Recovery Started Recovery Complete Successfully started a MASTER SQL Server. ***

Customer Release Configuration Guide Telecomunicaciones De Mexico Sybase Product Installation

Creation of SYBASE devices OFDB01 and OFDB02

57MBytes & 125MBytes

***

CREATE A SYBASE LOGICAL DEVICE ============================== *** WARNING This will create the Sybase device as follows:disk init name = "OFDB01", physname = "OFDB_491:[SYBASE_491.DEVICES]OFDB01.DAT", vdevno = "1", size = "29184", (= 57MBytes) Is this correct? Do you wish to continue. Please confirm (Y/N, [N]): <Y> Please wait ...

Creating Sybase device OFDB01. CREATE A SYBASE LOGICAL DEVICE ==============================

*** WARNING This will create the Sybase device as follows:disk init name = "OFDB02", physname = "OFDB_491:[SYBASE_491.DEVICES]OFDB02.DAT", vdevno = "2", size = "64000", (= 125MBytes) Is this correct? Do you wish to continue. Please confirm (Y/N, [N]): <Y> Please wait ... ***

Creating Sybase device OFDB02.

*** Modifying master DB to be 12MBytes & temp DB to be 56MBytes Extending database by 4096 pages on disk master Extending database by 12800 pages on disk OFDB01 Extending database by 12800 pages on disk OFDB02 Extending database by 256 pages on disk master Stopping the MASTER SQL Server OFDB *** *** *** *** *** *** Finished creation of OFF-LINE SYBASE devices ***

HNS Inhouse Sybase installation procedure complete NOTE !!! Ensure that the file SYS$MANAGER:SYSTARTUP_V5.COM contains commands to start the SYBASE$BATCH queue, install the SYBDBSHR shareable image, and run SYLOGICALS.COM HNS Inhouse Sybase installation procedure complete. ***

*** *** *** ***

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of SYB V4.9.1 completed at 19:39 VMSINSTAL procedure done at 19:40

The above procedure installs the Sybase server and creates the standard database and devices. It does not install the LES specific database (CES_ONDB), the procedure to do this is discussed in the next chapter.
5-7

Customer Release Configuration Guide Telecomunicaciones De Mexico Sybase Product Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

If you experience any failures during the creation of the logical devices then see section 7.3.2 for information on creating devices manually once you have remedied the cause of the failure. Alternatively, once the LES software is installed you can login to the operational account (BAPSYS) and enter the following to login to Sybase as the System Administrator: $ SA You can then create the logical devices manually. For example, to create the last (offline database) device above you would enter the following commands exactly as shown: 1> disk init 2> name = "OFDB02", 3> physname = "OFDB_491:[SYBASE.DEVICES]OFDB02.DAT", 4> vdevno = 2, 5> size = 64000 6> <> 1> exit NOTE: The SYBASE Product Installation is now complete - Now go to section 7.1.1, for details on creating and populating the database. The above procedure must be run on both BAPs. It is important to note, however that the Sybase Devices should be created only on the first BAP.

5-8

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Chapter 6 LES Software EBF Installation


This chapter describes the steps involved in installing partial LES software, for instance Emergency Bug-Fixes (EBFs), on a live system with minimal down-time. The first two sections below describe the principle actions, in detail, for installing an EBF. However a significant amount of time would be taken in simply manipulating the same predetermined files when protecting and copying the new files to their destinations. Consequently, when a release contains more than just a few BAP files, an installation COM file and a file list will be included with the release. These files may then be used to semiautomate the installation. The final section below gives the instructions for this procedure. 6.1 BAP EBF Installation This section describes the steps to be taken during installation of a partial release. This may be a few executables, or a database convertor. The method to be adopted for software upgrades is to install on the Standby BAP whilst the Master carries traffic. To minimise the system downtime, it is possible to leave the Master running until the moment when the database needs to be converted and any new FEP software needs to be loaded. In summary the installation steps are highlighted below, although the exact details will be included in the Software Release Notes. The general steps to follow are: 1. Actions to be performed prior to software upgrade. See section 6.1.1. 2. If necessary, convert the Online Database. For an upgrade the Software installation notes will describe the procedure to follow. See section 6.1.4.1. 3. Stop and Deinstall the Standby BAP and a SOC. See section 4.1.1. 4. Install the new software on the stopped BAP a SOC. See section 4.1.2. 5. Stop the Master BAP. 6. If necessary, install the Satellite Driver FEPs on the stopped BAP noting that this is the first FEP installation. See section 4.1.2.2, page 17. 7. Copy back any customer specific files that were copied to a safe directory in section 2.2. 8. Start the newly installed BAP and SOC. See sections 8.1 and 8.2. 9. Install the other BAP and the other SOC. See sections 4.1.1 and 4.1.2. 10. Install the Satellite Driver FEPs on the stopped BAP noting that this is the second FEP installation. See section 4.1.2.2, page 17. 11. Copy back any customer specific files that were copied to a safe directory in section 2.2. 12. Start the newly installed BAP and SOC. See sections 8.1 and 8.2.
6-1

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software EBF Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

6.1.1 Actions to be performed prior to software upgrade See chapter 2, section 2.1 for further details on saving the LES software. Then the partial saveset, must be copied (from the release tape) to a safe directory, perhaps on the quorum disk. For example: $ SET DEF $1$DIA2:[(SAFE_DIRECTORY)] $ BACKUP/NEW/LOG MKA500:80111.SAV/SAV OR, if there are only a few file in the release $ COPY/LOG MKA500: [] The release notes will indicate which should be used. 6.1.2 Stop and Deinstall the Standby BAP and one SOC See chapter 4, section 4.1.1 and 4.2.1, for further details. 6.1.3 Install the new software on the stopped BAP and SOC This will involve copying the new files to the correct directories. For example if the executable XCCC_P.EXE is one of the affected then it should be copied to the directory XCCC$EXE: $ COPY/LOG $1$DIA2:[(SAFE_DIRECTORY)]XCCC_P.EXE XCCC$EXE: 6.1.4 Database conversions Stop the Master BAP, in preparation for Database conversion. NOTE: Prior to performing the conversion, it is necessary to perform a database dump and archive. The Software release notes will identify the tables affected, therefore these tables should be dumped to POP files prior to conversion. See section 2 for further details. Convert the Online Database, if necessary. Details will be provided in the Software Release Notes, for an example see below. Convert the Offline Database, if necessary. Details will be provided in the Software Release Notes, for an example see below. NOTE: Prior to an upgrade of the offline database, the operator must ensure billing operations are complete and that an archive has been performed. This is especially important for a major upgrade, if for instance the structure of the logfiles have changed. 6.1.4.1 Example Online Database Conversion Procedure This section describes an example conversion procedure for the Online database. It shows a conversion from version 73 to 80000. Any specific values indicated are examples only. $ @SAD$EXE:SAD_START_SYBASE
6-2

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software EBF Installation

This will start the database on the current BAP. Execute the conversion process as follows: $ SET DEFAULT DBCONV80000$EXE $ @ONDB_CONVERSION_MENU Choose option 1. Enter MEXICO as customer name. Hit return to accept default database name ONDB. The log file created in the the default area is ONDB_CONV_1.LOG. Search the conversion log for level to find error messages. The following errors are examples of what may be expected to appear (if errors are expected, reference should have been be made in the release notes), no others should appear, if they do, contact HNS Ltd. Invalid object name Regd_User There is already an object named DRH in the database. Attempt to insert duplicate key row in object MMI_Login_Access with unique index MMI_Login_Idx1 Restart the online database. This will perform database initialization after upgrade. $ @SAD$EXE:SAD_START_SYBASE 6.1.4.2 Example OffLine Database Conversion Procedure This section describes an example conversion procedure for the Offline database. It shows a conversion from version 72* to 80000. Any specific values indicated are examples only. Use procedures in the DBCONV80000$EXE area. $ SET DEFAULT DBCONV80000$EXE $ @OFDB_CONVERSION_MENU Choose option 1. Enter MEXICO as customer name. Hit return to accept default database name OFDB. Enter Y to setup the OFDB server DSQUERY logical name. The log file created in the default area is OFDB_CONV_1.LOG. Check this file for any error messages. Once the conversion is complete, enter Y to reset the ONDB server DSQUERY logical name. Search the conversion log for level to find error messages. No errors are expected to appear. If errors do appear, then contact HNS Ltd. 6.1.5 FEP installation Prior to the FEP installation being performed, the old load files, if any, must be renamed. This means that when the FEPs are rebooted, the new load files will be picked up. For example: $ RENAME/LOG FELNSYS$EXE:FEP_MAIN_P.SYS_80 FELNSYS$EXE:FEP_Main_P.OLDSYS

6-3

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software EBF Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

$ RENAME/LOG FELNSYS$EXE:FEP_MAIN_P.MAP_80 FELNSYS$EXE:FEP_Main_P.OLDMAP

This procedure is in two stages. The first stage, on the new BAP, will load the FEPs, that is it will reboot them. The second stage, to be performed on the standby BAP, once it has been upgraded, does not require a FEP reboot. See section 4.1.2.2, following the comment ** Start of FEP Installation Procedure., page 17, for further details. Note also that the renaming step should only be performed once when the first BAP is installed, and that is on the the original files on the uninstalled BAP. 6.1.6 Start the newly installed BAP and SOC Once any conversions have been completed the First BAP can be started as the Master. Use the procedure in section 8.1 to do this. Install the other BAP and SOCs once the upgrade has been proven to be satisfactory. The upgrade procedure is now complete. 6.2 SOC EBF Installation This section describes the upgrade procedure for each SOC. The normal installation procedures can be used (see section 4.2). This time the only affect will be the raising of a Minor SOC_Failure alarm from each BAP when the SOC is shutdown. However, unlike a full SOC installation, NO files should be deleted. All SOC files which are to be replaced (see installation notes) must first be protected in a similar manner to those for a BAP EBF (see above). If this is a combined BAP and SOC EBF release, then the SOC files will already have been extracted from tape along with the BAP files. These should be copied to the SOC. The release notes will identify which files are required and their locations. SOC workstations are not actively redundant, single point failures being handled by having at least two SOCs. For most changes to the SOC it will be possible the restart the newly installed SOC before upgrading both BAPs and it should be completely if not mostly usable until both BAPs have been upgraded. There are certain changes to the SOC where it will not be possible to start the newly installed SOC without upgrading both BAPs. These changes involve the way in which the SOC establishes connections with the BAPs. These changes are unlikely. The worst that can happen is that the SOC will not be usable until the Master BAP is running with the new software which is consistent with the SOC and some extraneous SOC alarms may be raised on the BAPs. The BAPs should remain otherwise unaffected. If the changes are problematic it is vitally important not to upgrade all the SOC workstations leaving them in an un-usable state whilst the system continues to carry traffic. This will prevent the operators from continuing to observe and control the system. Upon re-starting each newly installed SOC,
6-4

if

all

goes

well

an

Info_Only

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software EBF Installation

SOC_Startup_Complete alarm should be raised on each BAP to which the SOC establishes a connection. Once any BAP upgrade is complete (section 6.1) the operators can now use any upgraded SOCs. Any remaining SOCs can be upgraded when convenient. 6.3 BAP EBF Automated Installation This section describes the steps to be taken during the automated installation of a partial release. This generally be the case for an EBF of more than about 5 files. The preceding section covering the BAP manual installation should be read first so as to understand the principle involved and any supporting actions which may be required. This section covers ONLY those instructions required to run the installation procedure. For all supporting actions before and after the installation, refer to the sections above. The method to be adopted for software upgrades is to install on the Standby BAP whilst the Master carries traffic. To minimise the system downtime, it is possible to leave the Master running until the moment when the database needs to be converted and any new FEP software needs to be loaded. In summary the installation steps are highlighted below, although the exact details will be included in the Software Release Notes. The general steps to follow are: 1. Actions to be performed prior to software upgrade. See section 6.1.1. 2. If necessary, convert the Online Database. For an upgrade the Software installation notes will describe the procedure to follow. See section 6.1.4.1. 3. Stop and Deinstall the Standby BAP and a SOC. See section 4.1.1. 4. Install the new software on the stopped BAP. See section 6.3.1. 5. Install the new software on the stopped SOC. See section 6.1.3. 6. Stop the Master BAP. 7. If necessary, install the Satellite Driver FEPs on the stopped BAP noting that this is the first FEP installation. 8. See section 4.1.2.2, page 17. 9. Copy back any customer specific files that were copied to a safe directory in section 2.2. 10. Start the newly installed BAP and SOC. See sections 8.1 and 8.2. 11. Install the other BAP and the other SOC. See sections 4.1.1 and 6.3.1. 12. Install the Satellite Driver FEPs on the stopped BAP noting that this is the second FEP installation. 13. See section 4.1.2.2, page 17. 14. Copy back any customer specific files that were copied to a safe directory in
6-5

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software EBF Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

section 2.2. 15. Start the newly installed BAP and SOC. See sections 8.1 and 8.2. 6.3.1 Install the new software on the stopped BAP Included with the release files on the tape will be two additional files: INSTALL_EBF.COM and a dat file nnnn.DAT where nnnn is the release series, created at the same time as the release. The files in the current release which are about to be replaced must first be copied to a protected area in case fall-back is required. The commands for using the COM file are $ SET DEF $1$DIA3:[HNS.EBF80142] $ @INSTALL_EBF PROTECT <NODE> The <node> parameter is optional, and, if used, will result in files being copied FROM the specified node to the current directory for protection. If the <node> parameter is omitted, then the current node is assumed. The operator will be prompted for the password of the node specified. This is useful on installations where there are BAPs not in the same cluster (HNS test rigs, for example). Now copy the new software files to the correct release directories; the commands to do this are: $ @INSTALL_EBF COPY <NODE> In addition, the COM file may verify the copied contents in their destination directories. The commands for using the COM file are $ @INSTALL_EBF VERIFY <NODE> When installing the second BAP simply log on to that BAP then set default to the same directory, already containing the release software and proceed as for the first installation. Note, files need not be protected again, as copies will already exist. FALL BACK The commands for using the COM file are $ SET DEF $1$DIA3:[HNS.EBF80142] $ @INSTALL_EBF FALLBACK <NODE>

6-6

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Chapter 7 Database Information


. This chapter provides information about the use of the Sybase database. 7.1 Installation of LES Database 7.1.1 Installing the LES Database This section details how the LES specific database is created and populated with data. Once the Sybase product installation is complete the following procedure must be performed to install and configure the LES Online and offline databases. NOTE: this procedure may also be used in the case of unrecoverable problems with the database, which effectively requires a reinstallation of the database. Login to the operational account (BAPSYS). Start the Sybase dataserver, by entering: $ STARTSERVER/SERVER=ONDB/WAIT Create the database using the PINS command file. The parameters are P1=db name, P2=syb logical dev name, P3=size of data segment. and P4=size of log segment. NOTE: The SIZE of the DATA and LOG SEGMENTS should be the SAME as those of the database WHERE THE DUMP WAS CREATED FROM. $ @PINS$EXE:PINS_CREATE_EMPTY_DATABASE ONDB ONDB01 12 4 The database must now be extended to a larger value than the supplied (16Mb), execute the following command file (NOTE: These are example values): The parameters are P1=db name, P2=sybase device name, P3=size to extend by, P4=whether the extension is log space or not (Y=log,N=data). $ @PINS_EXE:PINS_EXTEND_DATABASE ONDB ONDB01 6 Y This extends the database CES_ONDB on device ONDB01 by 6 Mb of log space. The fourth parameter is Y indicating the extended data should be turned into pure log space. $ @PINS_EXE:PINS_EXTEND_DATABASE ONDB ONDB01 88 N This extends the database CES_ONDB on device ONDB01 by 88 Mb of data space.
7-1

Customer Release Configuration Guide Telecomunicaciones De Mexico Database Information

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

The above parameters give a database of 110 Mbytes in size. An empty database now exists. This will need to be populated with data, the procedure for performing this will be described below: Load the database from the dump by performing the following: You must assign the PINS_EXE logical name in the system table as Sybase runs in a different group by entering: $ DEFINE/SYS PINS_EXE BAP$SYSTEM:[RELnnnn.PINS.EXECUTE] NOTE: The PINS_EXE logical name MUST be defined in the system logical name table. Then load the database using the PINS command file adding the database name when prompted for: $ @PINS$EXE:PINS_LOAD_DB_FROM_DUMP ONDB NOTE: The Master BAP MUST be stopped as this requires exclusive access to the database. This command file creates a disk dump device to point to the file PINS_EXE:CES_DISKDUMP.DMP and loads the specified database (prefixing it with CES_) from that dump. It then adds the database options "trunc. log on checkpoint" and finally adds the database Logins and Users for that database." The CES_ONDB database does not have the correct options set. It should have "select into/bulkcopy, trunc. log on chkpt.". Usually just after a first installation it will only have "trunc. log on chkpt.". In this state the database archive mechanism will not work. You must issue the the following commands from any account to add the extra option: $ @SYBASE_SYSTEM:[SYBASE.INSTALL]SYBASE_USER $ @SYBASE_SYSTEM:[SYBASE.INSTALL]SYBASE_MANAGER $ SA or $ ISQL/U="sa"/P="my_passwd"/TERM="" 1> sp_dboption CES_ONDB,"select into/bulkcopy",true 2> <> 1> sp_dboption CES_ONDB,"trunc. log on chkpt.",true 2> <> 1> checkpoint 2> <> 1> use CES_ONDB 2> checkpoint
7-2

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico Database Information

3> <> 1> exit 7.1.2 The Sybase Report Writer Product To install the Sybase Report Writer product, create a directory on the system device called SYBASE_LDR and modify the SYBASE_SYSTEM logical name by editing the SYS$SYSDEVICE:[SYBASE_491.SYBASE.INSTALL]SYLOGICALS.COM file as follows: Check the following line exists:
$ SYB_DEF/executive sybase_system sybase_491

To install report writer, run the following command: $ @SOCV$EXE:SOCV_ONLN_IMPORT_VMS_FILES_TO_RW_TABLES CLEAR TRUNC_TRANS 7.1.3 Loading the Specific Population Files into the Database Check that the SDA* database symbols are pointing to the correct database and then execute the command: $ @PINS_MEXICO$EXE:PINS_MEXICO_LOAD.COM NOTE: This should only be performed for a first time installation. At this point the Online database installation is complete. 7.1.4 Installing the Offline Database This section describes the procedure for installation of the offline database. Log into the BAP as BAPV or via the SOC as SOCV: In the SOC Viewer: Select option (2), Offline Processing, Select option (3), Start Offline Database Server, Select option (E) to return to the Main Menu, Select option (E) to exit the SOC Viewer. Then log into the operational account (BAPSYS) on the BAP, and enter: $ DEFINE DSQUERY OFDB $ SA 1> sp_helpdb 2> <>
7-3

Customer Release Configuration Guide Telecomunicaciones De Mexico Database Information

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Check that, for a first time installation, the databases CES_OFDB and CES_OFDB_C do not exist. If the do exist then the following should be performed: 1> drop database CES_OFDB 2> <> 1> drop database CES_OFDB_C 2> <> Then run: $ @OFDB$EXE:OFDB_INSTALL.COM On a standard installation, this will take approximately forty minutes. The following messages and prompts will be displayed:
What size database do you want L=Limited(45Mbytes),F=Full(100Mbytes) [F]: <> Creating database CES_OFDB, 100Mbytes Please Wait...

Enter: $ DEASS DSQUERY To stop the offline database, follow the following procedure: In the SOC Viewer: Select option (2), Offline Processing, Select option (4), Stop Offline Database Server, Select option (E) to return to the Main Menu, Select option (E) to exit the SOC Viewer. At this point the Offline database installation is complete. 7.2 Database Administration Duties During an LES Software Upgrade NOTE: These duties are INDEPENDENT of safety measures against Database corruption that are taken by the customer e.g. daily archives. These duties DO NOT IN ANY WAY replace them. 7.2.1 Database Administration PRIOR to Upgrade NOTE: that this should be done when LES activity is at its lowest. Obtain database dumps for the master, model and CES_ONDB databases on the online server using the (SYBASE) account. These dumps will be stored on a disk device with at least 200,000 blocks free (in the commands below, we assume $1$dia3 is such a device).
7-4

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico Database Information

(Note, this is the minimum size to hold dumps where CES_ONDB database is the standard size of 110 MBytes. If the database is larger than this the minimum size considered will have to reflect this). It is recommended that all unnecessary database dumps be backed up to tape and removed from the BAP to free diskspace which can be subsequently used for up to date dumps. All customer sites should have the PINSDISKDUMP SYBASE dump device defined. Use this database dump device to produce the dumps if the system logical "PINS_EXE" is pointing to a device with enough disk space. Firstly, login to the SYBASE account. If the system logical "PINS_EXE" is not pointing to a device with enough disk space redefine it to do so e.g. $ DEFINE/GROUP PINS_EXE $1$DIA3:[UPGRADE_LES_DUMP] Where $1$DIA3: is the disk device. Now, check that the PINSDISKDUMP SYBASE dump device is defined using the following command: $ sa 1> sp_helpdevice PINSDISKDUMP 2> <> 1> exit If the PINSDISKDUMP SYBASE dump device is not defined, do so using the following command: $ sa 1> sp_addumpdevice "disk",PINSDISKDUMP, 2> "pins_exe:ces_diskdump.dmp",2 3> <> 1> exit The dumps can now be produced using the following commands. They will be renamed to a more meaningful name and to an area that has enough disk space to hold all the dumps. (<REL_NO> should be replaced by the release number upgrading FROM e.g. 80024: $ sa 1> dump database model to PINSDISKDUMP 2> <> 1> exit $ RENAME PINS_EXE:CES_DISKDUMP.DMP $1$dIA3:[UPGRADE_LES_DUMP]MODEL_CES_DISKDUMP_(REL_NO).DMP $ sa 1> dump database master to PINSDISKDUMP
7-5

Customer Release Configuration Guide Telecomunicaciones De Mexico Database Information

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

2> <> 1> exit $ RENAME PINS_EXE:CES_DISKDUMP.DMP $1$dIA3:[UPGRADE_LES_DUMP]MASTER_CES_DISKDUMP_(REL_NO).DMP $ sa 1> dump database CES_ONDB to PINSDISKDUMP 2> <> 1> exit $ RENAME PINS_EXE:CES_DISKDUMP.DMP $1$dIA3:[UPGRADE_LES_DUMP]CES_ONDB_CES_DISKDUMP_(REL_NO).DMP The procedure for producing database dumps is now complete. The dumps should be left on disk at least until the LES has been successfully upgraded. It is preferable that they remain here until the next upgrade at which point they can be backed up to tape. 7.2.2 Database Administration During Upgrade Perform these actions when both BAPs are down and before the online database convertor is run. Log on to the BAP and ensure it is running the online server. This can be determined by using the following command: $ SHOWSERVER/SERVER=ONDB If not, then start the online server: $ STARTSERVER/SERVER=ONDB/WAIT Check the consistency of the master, model and CES_ONDB databases, using the following SYBASE commands. Log onto the online database using: $ ISQL/U="sa"/P="my_passwd"/OUT=DBCC.TXT This will result in the redirection of the output for the following SYBASE commands to file DBCC.TXT. This may take approx 25 mins. 1> dbcc checkdb (model) 2> go 1> dbcc checkalloc (model) 2> go 1> dbcc checkdb (master) 2> go
7-6

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico Database Information

1> dbcc checkalloc (master) 2> go 1> dbcc checkdb (CES_ONDB) 2> go 1> dbcc checkalloc (CES_ONDB) 2> go 1> exit 7.2.2.1 DBCC corrective actions Check DBCC.TXT. If errors 2521,2540,2546,7939,7940 or 7949 were raised during the running of the "dbcc checkalloc" command, carry out the following corrective action. (The commands below assumes the correction is needed for the database, CES_ONDB, if the correction is required for the master or model, replace CES_ONDB in the following commands with that database name). Firstly, set the database to single user mode. $ sa 1> sp_dboption CES_ONDB, single, true 2> <> 1> use CES_ONDB 2> <> 1> checkpoint 2> <> 1> exit Then, redirect the SYBASE output: $ ISQL/U="sa"/P="my_passwd"/OUT=DBCC.TXT This will result in the redirection of the output for the following SYBASE commands to file DBCC.TXT. 1> use master 2> go 1> dbcc fix_al (CES_ONDB) 2> go 1> exit
7-7

Customer Release Configuration Guide Telecomunicaciones De Mexico Database Information

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Now reset the database option i.e. allow multiple users to access the database. $ sa 1> sp_dboption CES_ONDB, single, false 2> <> 1> use CES_ONDB 2> <> 1> checkpoint 2> <> 1> exit As a result, you should get an error free output in the file DBCC.TXT. If any errors were reported, contact HNS Ltd. NOTE: If an error is reported, then it is likely that recent database dumps may be similarly affected, and it is possible at ALL dumps since the last successful DBCC are at fault. If the problem cannot be rectified by the corrective actions given above, then recovery will require the loading of the last KNOWN good dump followed by all database conversions required to bring this up to date. All customer data (such as user registrations) subsequent to the date of the restored dump will be lost. It may possible to restrict the loss of data by restoring each dump in succession, running DBCC after each until the first occurrence of the DBCC failure is found, then regressing one step. However as DBCC may take well in excess of 30 minutes the outage time may be judged excessive. The customer must trade off the benefits of maintaining verified good, up to date dumps and the longer duration of the outage needed to perform DBCC. 7.2.3 Database Conversion (ONDB) This section describes the steps required for a database conversion. The prerequisites for conversion are: The new release has been loaded on (what was) the standby BAP The Master BAP has been stopped ONDB has been started on the newly installed BAP If it is not already running, then start the online database server (on the newly installed BAP) using the following command. $ STARTSERVER/SERVER=ONDB/WAIT Before starting the conversion, ascertain the current status of the database and obtain confirmation of the last conversion
7-8

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico Database Information

$ ONDB 1>select * from SDA_Version 2>where Timestamp = (select max(Timestamp) from SDA_Version) 3> Timestamp SW_Version Feb 17 2000 9:45AM PINS 80110, SPR: 26132. Component

SCRs: 578,579

The above details are for illustration only. Note the text in the SW_Version field. Convert the online database $ Set Default DBConv80000$Exe $ @ONDB_Conversion_Menu If the release number determine in SW_Version above is not displayed, then select the option to display the next screen (repeat until the desired entry is found) The starting point for conversion should normally be the next entry following the above. Consult HNS if this is not the case. Select the numbered conversion to start from and step through each successive option up to and including the version covering the release being installed (usually the last entry). Verify there are no errors in the conversion logs ONDB_CONV_<nn>.LOG after each step, where <nn> represents the conversion step. (It will be very much easier to have a second session running to view these log files as they are created). Any deviation from these instructions will be indicated in the release notes. A partial conversion may take anything from 30 seconds to 5 minutes per step. The online database upgrade is now complete. Should there be any unexpected errors, please consult HNS Ltd. 7.2.4 Database Administration Issues after Successful Upgrade NOTE: This should be done when LES activity is at its lowest. The dumps for the three databases should now be produced as described in section 7.2.1, Database Administration prior to upgrade. (NOTE, however the <REL_NO> should be replaced by the release number upgraded TO, not from e.g. 73020). 7.3 Database General Information This section provides general information about the database. It is to provide work-arounds in case of problems during Sybase installation and the subsequent creation of the LES database.

7-9

Customer Release Configuration Guide Telecomunicaciones De Mexico Database Information

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

7.3.1 Sybase Account Details The Sybase product must have been installed on the machine with the correct privileges and quotas. The quotas and privileges of the account should be as follows (as displayed using AUTHORIZE):
Fillm: Shrfillm: BIOlm: DIOlm: ASTlm: TQElm: Enqlm: 150 0 756 250 756 50 100 Bytlm: 150000 Pbytlm: 0 JTquota: 10100 WSdef: 44000 WSquo: 44000 WSextent: 44000 Pgflquo: 30000 These values support the standard configuration of 25 users. This can be observed by the ISQL command sp_configure.

Authorized Privileges & Default Privileges: CMKRNL SYSNAM GRPNAM DETACH ALTPRI TMPMBX NETMBX SYSPRV SYSLCK SHARE

In our application the SYBASE account and associated root directories are located on the system disk and can therefore be referenced using the SYS$SYSDEVICE logical name in both AUTHORIZE and the system command files. The system wide Sybase logicals must be set up on VAX/VMS machine startup, so the line: $ @SYS$SYSDEVICE:[SYBASE_491.SYBASE.INSTALL]SYLOGICALS.COM must be included in the file SYS$MANAGER:SYSTARTUP_V5.COM. Also check that the queue SYBASE$BATCH, that is required by SAD$EXE:SAD_START_SYBASE.COM, is created on VMS startup and that it is running on the correct node. Check that the SYBASE account and root is setup correctly in terms of ownership of files and directories and that the correct protections are on the files. In particular check that the directories and files: SYS$SYSDEVICE:[000000]SYBASE_491.DIR SYS$SYSDEVICE:[SYBASE_491]SYBASE.DIR SYBASE_SYSTEM:[SYBASE]INTERFACES Have WORLD READ and EXECUTE protections. To check this enter: $ DIRECTORY/PROTECTION (FILENAME) 7.3.2 Creating the Sybase Devices If there is a requirement to create the Sybase device manually, in case of a corruption for instance, the following describes the procedure to follow. To create a Sybase device using the command file from the operational account (BAPSYS) enter: $ @PINS_CREATE_SYBASE_DEVICE ONDB01 ONDB_491:[SYBASE_491.DEVICES]ONDB01.DAT 1 56320
(size in 2 Kbyte pages - divide by 512 to give size in Mbytes).

7-10

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico Database Information

7.3.3 Changing the Sybase System Administrators Password When a dataserver is first created the System Administrators (SA) password is set to a null string (called NULL); this should be changed to the standard value of my_passwd using the following procedure. Check the value of DSQUERY (this may be setup in the process table after executing the SYBUPDATE.COM) by entering: $ SHOW LOGICAL DSQUERY Check whether the ISQL symbol is set up by entering: $ SHOW SYMBOL ISQL If it is not defined then enter: $ @SYBASE_SYSTEM:[SYBASE]SYBASE_USER followed by: $ ISQL/U="sa"/P/TERM="" 1> sp_password NULL,my_passwd 2> <> 1> exit The SA symbol should now work correctly. The SA symbols are setup in the file BAPENV.COM (in the (BAPSYS) SYS$LOGIN directory) as follows:
$sa :== "isql /U=""sa"" /P=""my_passwd"" /Term="""""

$sa_load :== "isql /U=""sa"" /P=""my_passwd"" /Input= ")

7.4 Populating the Database This section details how the database is populated with data. 7.4.1 The Basic Database Dump and the PINS Prebuild NOTE: This section is only relevant to a first time installation. A basic database dump file is created at build time by the PINS PREBUILD file. This database dump contains all the required database table definitions and the SQL stored procedures required to interface with them from Ada. Some of the tables that are not customer/machine configuration specific are populated at this time. At build time the files are loaded into a database called CES_COMDEV of data segment size 12 Mb, and log segment size 4 Mb. This can be checked by using the ISQL command sp_helpdb CES_COMDEV.
7-11

Customer Release Configuration Guide Telecomunicaciones De Mexico Database Information

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

After the build has completed the resultant file is PINS_EXE:CES_DISKDUMP.DMP. This file is loaded on upgrades by executing the PINS command file thus (first checking that PINS_EXE logical name is assigned in the system table and points to the appropriate PINS execute directory): $ @PINS_EXE:PINS_LOAD_DB_FROM_DUMP You should enter ONDB at the database name prompt. If the database is required to be extended to a larger value than the supplied 16 Mb, execute the following command file (NOTE: These are example values): $ @PINS_EXE:PINS_EXTEND_DATABASE ONDB ONDB01 10 N This example extends the database CES_ONDB on device ONDB01 by 10 Mb leaving the space as data and log. If the fourth parameter is Y then the extended data would be turned into pure log space. NOTE: The above loading of the database from the dump and then extending its size is usually performed by PROJECTINSTALL unless it is an upgrade when the existing database is converted. 7.4.2 Specific Variants of PINS NOTE: this section is only relevant to a first time installation. Since the basic database dump contains only the non specific table population information, there is specific data stored as separate PINS components. These separate components are released independently of the basic PINS component and are copied to the PINS_MEXICO$EXE directory. To convert the basic database into a customer specific database for Telecomunicaciones De Mexico perform the following command: $ @PINS_MEXICO$EXE:PINS_MEXICO_LOAD.COM

7-12

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Chapter 8 LES Software Startup


. This chapter gives instructions on starting the BAP and SOC processors. Information is included about customer specific startup. Chapter 9 describes methods for obtaining tracing information from the running LES system. 8.1 Starting the BAP This section describes the procedure to startup the LES software on the BAP. Login to the operational account (BAPSYS) on the new BAP. To do this locate a terminal connected either directly to the BAP or to a DECserver terminal server. Initiate the login sequence according to where you intend to login by following one of the procedures below and then proceed to login as described later. If the terminal is directly connected to the BAP then type one of Control-Y, <> or Control-C. You should then see something like :
VAX VMS 5.5-2H4 - No Unauthorized Access Username:

You can now login as described below. If the terminal is attached to a terminal server then you can communicate with the BAP over LAT. Hit the Return key until you see the Local> prompt. If it appears that the terminal is already in use then hit the Break key (F5) to return control to the terminal server. At this point enter: Local> CONNECT (LAT service name) In all cases the LAT service name will be the same as the DECnet node name. The CONNECT command can be abbreviated to C. Having done this you should now see something like :
Local -010- Session <n> to <node name> established VAX VMS 5.5-2H4 - No Unauthorized Access Username:

You can now login as described below. You should now enter the username of the operational account (BAPSYS), for example: Username: BAPSYS You will then be prompted for the password. Type in the current password, it will not be echoed to the screen, thus keeping it secure: Password: (PASSWORD)
8-1

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Startup

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

If you see a message such as:


User authorization failure

then hit Return to get the Username: prompt back and try again. If you have successfully entered the password you should then see messages such as:
+------------------------------------------------------------------+ | ***** CES - Generic MicroVAX 3800 VMS 5.5-2H4 ***** | +------------------------------------------------------------------+ ******************************************************************************* 20-July-92 Layered Products : P.S.I. MailBus VMS-DEBUG version 4.3 version 3.2 new version

******************************************************************************* Last interactive login on Thursday, 6-AUG-1992 13:20 Last non-interactive login on Thursday, 6-AUG-1992 11:56

When you login in you may get a message such as:


WARNING - Your password expires on <date and time>

This can be ignored until the time specified, when the following will be displayed the next time you login:
Your password has expired; you must set a new password to log in.

In this case you should choose a new password which must be different from the current one. Enter your new password twice as shown: New password: (password) Verification: (password) If this is the first time you have logged in since the installation of the VMS operating system, the following messages will then appear:
Defining logical names ******************************************************** *** Setting BAP Environment ******************************************************** ******************************************************** *** Copying SAD$EXE:SAD_PROCESS_DATA_.DAT *** to SAD_EXE:SAD_PROCESS_DATA.DAT ******************************************************** ******************************************************** *** Creating MAR$DAT:*_TEXT_FILE.TXT files ******************************************************** ******************************************************** *** Creating MAR$DAT:TEST_MSG_TEXT_FILE.TXT file ******************************************************** ******************************************************** *** Creating MAR$DAT:OPER_MSG_RESP_TEXT_FILE.TXT file ******************************************************** ******************************************************** *** Creating MAR$DAT:MAR_CONFIG_DATA.DAT file ******************************************************** ******************************************************** *** Creating MAR$DAT:G3FAX-DEF_BANR-IA_5-OTHER.TXT file ******************************************************** ******************************************************** *** Creating MAR$DAT:G3FAX-DEF_BANR-IA_5-DN.TXT file ********************************************************

8-2

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Startup

******************************************************** *** Creating MAR$DAT:G3FAX-DEF_BANR-IA_5-SAC.TXT file ******************************************************** ******************************************************** *** Creating CUTL$DAT:CUTL_MH_CONVERSION.DAT file ******************************************************** ******************************************************** *** Creating CRM$DAT:CRM_*.CR_LIS_FMT files ******************************************************** ******************************************************** *** Creating CRM$DAT:CRM_*.CR_REP_DEF files ******************************************************** ******************************************************** *** Creating CRM$DAT:DEFAULT.CR_REP_DEF file ******************************************************** ******************************************************** *** Creating DBA$DB_DIR:FDCD_EXT_MGR_DATA.DAT file ******************************************************** ******************************************************** *** Creating XCCC$DAT:DEMSA_TABLE. file ******************************************************** ******************************************************** *** Creating BAP$LOG:LOW_WATER_MARK.DAT file ******************************************************** -------------------------------------------------------------------------------Verifying image installation -------------------------------------------------------------------------------*** Checking installation of BAP images ... not installed *** Installing BAP ... installing ... installing ... installing ... installing ... installing ... installing ... installing ... installing ... installing ... installing ... installing ... installing ... installing ... BAP images images CD:CDMC DEB:NRA DIM:DIM_SHARE DIM:DIM_LINK_MGR_P ERR:ERR ERR:ERRMC MC:MC_MC_IF SAD:SAD_BAP_IMAGE_P SAD:SAD_SHARE SDC:SDC_CONFIG_DB UTL:UTL UTL:UTLDATA UTL:UTLTRCFLG installed

******************************************************** *** Creating PIPM$EXE:PIPM_NETWORK_SETUP.DAT file ******************************************************** *** Creating XCCC$DAT:DEMSA_TABLE. file ********************************************************

For all subsequent logins the following will appear:


******************************************************** *** Setting BAP Environment ******************************************************** UNITDEV SAD COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! UNITDEV PIPM COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! UNITDEV TLX COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! UNITDEV XCCC COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -------------------------------------------------------------------------------Verifying image installation --------------------------------------------------------------------------------

8-3

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Startup


*** Checking installation of BAP images ... installed

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

NOTE: If this is the first time you have logged in since the installation of the VMS operating system, you will need to create the Sybase database devices, load the basic database dump and extend the database segments before configuring the database for the specific target machine - for instructions on how to do this see section 7.1.1. NOTE: If at this stage you have not yet performed the additional actions required after installation and before startup then stop at this point and follow the procedures set out in section 4.1.3 before attempting to start the system up. Once the system is ready to start enter one of the following commands: $ BAPOP START BAP ARBITER Without specifying the mode the system will startup in the mode in which it was started last. If this is the first time the system is being started the startup procedures will assume the value ARBITER for the mode. $ BAPOP START BAP (MODE) The system will startup in the mode specified and you will not be asked to confirm the value. $ BAPOP START BAP (MODE) (STARTUP CUSTOMER) Specifying the startup customer will automatically reconfigure the system for that customer before starting it up. Possible values for the mode parameter are: ARBITER For redundant systems using an Arbiter card which will decide the mode of the BAP. MASTER For non-redundant systems without an Arbiter card or redundant systems using an Arbiter card when the operator needs to override its decision where the BAP should startup as the Master BAP. STANDBY For non-redundant systems without an Arbiter card or redundant systems using an Arbiter card when the operator needs to override its decision where the BAP should startup as the Standby BAP. IDLE For non-redundant systems without an Arbiter card or redundant systems using an Arbiter card when the operator needs to override its decision where the BAP should startup as the Idle BAP. After invoking the relevant command the following messages and prompts will be displayed
8-4

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Startup

(example responses are shown enclosed in <>):


-------------------------------------------------------------------------------Starting the BAP using release REL8011 --------------------------------------------------------------------------------------------------------------------------------------------------------------Verifying image installation -------------------------------------------------------------------------------*** Checking installation of BAP images ... installed -------------------------------------------------------------------------------Configuring BAP operational software for customer MEXICO -------------------------------------------------------------------------------%DCL-I-SUPERSEDE, previous value of CUSTOMER_NAME has been superseded ******************************************************** *** Setting BAP Environment ******************************************************** UNITDEV PIPM COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! UNITDEV TLX COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! UNITDEV XCCC COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -------------------------------------------------------------------------------Verifying image installation -------------------------------------------------------------------------------*** Checking installation of BAP images ... installed Configure VMS host for downline loading (only needs to be done once) [N]: <> Configure FEP nodes (only needs to be done once) [N]: <> Set FEP load files [N]: <> *** Warning - Loading Software will cause the indicated FEP to crash! Load FEP Software onto FEP Target [N]: <> *** FELN specific installation of release 8011 complete ******************************************************** *** Creating SAD$DAT:SADCONFIGBAP.DAT ******************************************************** -------------------------------------------------------------------------------Performing BAP initialisation -------------------------------------------------------------------------------*** Initialising BAP devices %SYSTEM-W-NOTALLPRIV, not all requested privileges authorized ... initialising Alarm Printer 1 => TXB0: ... Using TXA5: for FTU1_Port ... initializing the Universal Time Clock Port *** Deleting BAP global sections (except MC) *** Initialising BAP data -------------------------------------------------------------------------------Initializing MC flags -------------------------------------------------------------------------------*** Starting the Pipe Manager

8-5

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Startup


%RUN-S-PROC_ID, identification of created process is 000002EA *** Starting the Arbiter Manager %RUN-S-PROC_ID, identification of created process is 000002EB *** Initialising PRC subsystem data BAP is under local control with mode MASTER *** Initialising DIM subsystem data *** Initialising FDCD subsystem data ***

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Beginning DCD Load External DB Change Distribution List Procedure

***

This procedure is stand-alone MAIN program which updates the External Distribution DB Change List in Global memory while the BAP is on-line. It reads the DB updates from file_id: FDCD$EXE:FDCD_Ext_Dist_DB_Changes_Text.Txt *** *** *** *** Begin Loading DCD External Distribution DB Change File *** Reading File-ID: FDCD$EXE:FDCD_Ext_Dist_DB_Changes_Text.Txt *** End Loading DCD External Distribution DB Change File *** Ending DCD Load External DB Change Distribution List Procedure ***

-------------------------------------------------------------------------------Starting processes -------------------------------------------------------------------------------... starting (detached) process APM_P_01 using image APM_P %RUN-S-PROC_ID, identification of created process is 2740093B ... starting (detached) process CUC_BAP_MSD__01 using image SAD_BAP_IMAGE_P %RUN-S-PROC_ID, identification of created process is 2740093D

... starting (detached) process <process_name> using image <image_name> %RUN-S-PROC_ID, identification of created process is <PID> : : : : : : : : *** BAP REL8011 started at 2-NOV-1993 11:23:13.80

$ BAPOP STOP BAP


BAP version Rel80110 from disk $1$DIA4: The Current State of the BAP is :STARTED The Current Processor Mode is :MASTER The Current Processor State is :RUNNING Show Active BAP Processes <Y/[N]>: <Y> Process# Process Name 27400938 PIPM_ATL 27400939 PRC_ARB_01 .. etc. All the processes will be displayed. Terminal Image [BAPSW.REL7203.PIPM.EXECUTE]PIPM_SERVER_P.EXE [BAPSW.REL7203.PRC.EXECUTE]PRC_ARBITER_MANAGER 9-JUL-1993 18:49:51.81

Once the BAP is Master Running, startup of the LES software on the BAP is complete. After a period of around 15 minutes the system should be ready to carry traffic.
8-6

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Startup

8.2 Starting the SOC This section describes the procedure to startup the LES software on the SOC. Login to the operational account (SOCSYS) on the new SOC. To do this locate either the VAXstation on which the SOC is running, a terminal attached to a DECserver terminal server or a terminal connected directly to the workstation itself. Initiate the login sequence according to where you intend to login by following one of the procedures below and then proceed to login as described later. If you have located the VAXstation workstation running the SOC then you can login using the workstation screen as a terminal. Using the mouse attached to the workstation locate the tip of the pointer on the screen over a region of empty space between any windows on the screen and press the leftmost mouse button. A small Workstation Options window should appear with the list of options shown below one of which you can select by again moving the mouse pointer over the words of the option of your choice and pressing the leftmost mouse button: Help Create SOC form window Create new VT200 window Print (portion of) screen Set up the workstation Exit this menu Select the Create new VT200 window option, within a few seconds a terminal window should appear with something like the following displayed:
VAX VMS V6.0 No Unauthorized Access Username:

You can now login as described below. If the Workstation supports MOTIF, the following will be displayed.
Motif Terminal Window Menu ========================== 1. 2. 3. 4. SOC Viewer Window SOC Form Task Window DECTerm Window Exit.

Select the DECTerm window option, within a few seconds a terminal window should appear with the following displayed:
VAX OpenVMS V6.0 - No Unauthorized Access

8-7

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Startup


Username:

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

If you cannot locate the VAXstation itself then locate a terminal connected either to a DECserver terminal server or directly to the VAXstation running the SOC. If the terminal is attached to a terminal server then you can communicate with the SOC over LAT. Hit the Return key until you see the Local> prompt. If it appears that the terminal is already in use then hit the Break key (F5) to return control to the terminal server. At this point enter: Local> CONNECT <LAT service name> In all cases the LAT service name will be the same as the DECnet node name. The CONNECT command can be abbreviated to C. Having done this you should now see something like :
Local -010- Session <n> to <node name> established VAX VMS V6.0 No Unauthorized Access Username:

You can now login as described below. If the terminal is directly connected to the SOC then type one of Control-Y, Return or Control-C. You should then see something like :
VAX VMS V6.0 No Unauthorized Access Username:

You can now login as described below. You should now enter the username of the operational account (SOCSYS), for example: Username: SOCSYS You will then be prompted for the password. Type in the current password, it will not be echoed to the screen, thus keeping it secure: Password: (PASSWORD) If you see a message such as:
User authorization failure

then hit Return to get the Username: prompt back and try again. If you have successfully entered the password you should then see messages such as:
+-----------------------------------------------------------+ | ***** Generic - VAXStation 3100 , VMS V6.0 ***** | +-----------------------------------------------------------+ ******************************************************************************* 19-December-1991 Layered Products : GKS TDMS version 4.0 (runtime) version 1.8A (runtime)

*******************************************************************************

8-8

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


Last interactive login on Thursday,

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Startup


29-OCT-1993 09:33

When you login in you may get a message such as:


WARNING - Your password expires on <date and time>

This can be ignored until the time specified, when the following will be displayed the next time you login:
Your password has expired; you must set a new password to log in.

In this case you should choose a new password which must be different from the current one. Enter your new password twice as shown: New password: (PASSWORD) Verification: (PASSWORD) If this is the first time you have logged in since the installation of the VMS operating system, the following messages will then appear:
Defining logical names %DCL-I-SUPERSEDE, previous value of SOC$LOGICALS has been superseded ******************************************************** *** Setting SOC Environment ******************************************************** *** No PIPM directories in COMDEV project tree. *** Do you wish to create them (Y,[N]): <Y> *** Creating PIPM directories in COMDEV UNITDEV PIPM COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! *** No SAD directories in COMDEV project tree. *** Do you wish to create them (Y,[N]): <Y> *** Creating SAD directories in COMDEV UNITDEV SAD COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! *** No SOC directories in COMDEV project tree. *** Do you wish to create them (Y,[N]): <Y> *** Creating SOC directories in COMDEV UNITDEV SOC COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ******************************************************** *** Creating SYS$LOGIN:LOGIN.COM ********************************************************

For all subsequent logins the following will appear:


******************************************************** *** Setting SOC Environment ******************************************************** UNITDEV PIPM COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! UNITDEV SAD COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! UNITDEV SOC COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

NOTE: If at this stage you have not yet performed the additional actions required after installation and before startup then stop at this point and follow the procedures set out in section 4.2.4 before attempting to start the system up. Once the system is ready to start enter one of the following commands: $ STARTSOC This form of the command available in all releases, is for Telecomunicaciones
8-9

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Startup

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

De Mexico $ STARTSOC MEXICO Specifying the startup customer will automatically reconfigure the system for Telecomunicaciones De Mexico before starting it up. See section 4.2.5 for details on how to change the configuration without starting the system. After invoking the relevant command the following messages and prompts will be displayed (example responses are shown enclosed in <>):
-------------------------------------------------------------------------------Starting the SOC using release REL8011 --------------------------------------------------------------------------------------------------------------------------------------------------------------Verifying image installation -------------------------------------------------------------------------------*** Checking installation of SOC images ... not installed *** Installing SOC ... installing ... installing ... installing ... installing ... installing ... installing ... installing ... installing ... installing ... installing ... installing ... SOC images images CD:CDMC DEB:NRA DIM:DIM_SHARE DIM:DIM_LINK_MGR_P ERR:ERR ERR:ERRMC SAD:SAD_BAP_IMAGE_P SAD:SAD_SHARE UTL:UTL UTL:UTLDATA UTL:UTLTRCFLG installed

* Enter customer configuration name for this SOC, e.g. INT: <MEXICO> -------------------------------------------------------------------------------Configuring SOC operational software for customer MEXICO -------------------------------------------------------------------------------%DCL-I-SUPERSEDE, previous value of CUSTOMER_NAME has been superseded ******************************************************** *** Setting SOC Environment ******************************************************** UNITDEV PIPM COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! UNITDEV SAD COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! UNITDEV SOC COMDEV !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ******************************************************** *** Creating SAD$EXE:SADCONFIGSOC.DAT ******************************************************** -------------------------------------------------------------------------------Performing SOC initialization -------------------------------------------------------------------------------*** Deleting SOC global sections (except MC) *** Initializing SOC data

8-10

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


*** Initialising PRC subsystem data

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Startup

*** Starting PIPM %RUN-S-PROC_ID, identification of created process is 0000006E -------------------------------------------------------------------------------Initializing MC flags -------------------------------------------------------------------------------*** Waiting for a network connection -- At this point the startup will pause until network information -- has been downloaded from the running BAPs to the SOC. This process -- should take less than two minutes. The completion of this is -- signalled by PIPM on the SOC creating the mailbox PIPM_AT. If no -- BAPs are running then the startup will not proceed until they are. -------------------------------------------------------------------------------Starting processes -------------------------------------------------------------------------------... starting (detached) process ERRLOG_01 using image ERRLOG %RUN-S-PROC_ID, identification of created process is <PID> ... starting (detached) process MC_LOGGER_P_01 using image MC_LOGGER_P %RUN-S-PROC_ID, identification of created process is <PID> ... starting (detached) process SOC_SRV_TASK_01 using image SOC_SRV_TASK %RUN-S-PROC_ID, identification of created process is <PID> *** SOC REL8011 started at 2-NOV-1992 11:20:00.00

This completes the startup of the LES software on the SOC. After approximately two minutes the SOC should be available for use. Once there is data on the System Usage Display, and the banner indicates connection to the BAPs, the operator can login to the SOC. 8.3 Starting the SOC Viewer The SOC Viewer can be accessed in two ways: 1. Via a SOC workstation. 2. Directly from a BAP. These methods are detailed in the following sections. For further information on how to use the SOC Viewer see the Chapter entitled GUIDE TO THE SOC VIEWER in reference [1]. 8.3.1 Starting the SOC Viewer from the SOC To access the SOC Viewer via the SOC workstation login to the captive account (SOCV) on the SOC from which you wish to run the SOC Viewer. To do this select Create new VT220 window from the Workstation Options window and enter the name of the captive account (SOCV) in response to the prompt Username:. After a few seconds the following should appear:
Welcome to the SOC Viewer Which node do you require? ((M)aster,(S)tandby,BAP(A),BAP(B) or F10 to exit) [M]:

At this point you may enter one of the following:


8-11

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Startup

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

M - This indicates that you want to use the SOC Viewer on the current Master BAP. S - This indicates that you want to use the SOC Viewer on the current Standby BAP. A - This indicates that you want to use the SOC Viewer on BAPA. B - This indicates that you want to use the SOC Viewer on BAPB. The first two options are only available when the SOC workstation has a connection to the BAPs. Only then does it know which is Master and Standby. If you enter anything else you will see:
Invalid choice - please choose M, S, A or B

If you try to use M or S when the SOC is not connected to a BAP in the requested mode, then a message such as the following will appear:
MASTER BAP is not known - please choose A or B

If you want a BAP in a particular mode then trial and error will need to be used to find the correct one. The mode and logical name of the BAP is indicated in the top right corner of the screen in the Main Menu, e.g. MASTER BAPA. You may also see the following message:
Possible switchover in progress - please choose A or B, or try again later

This indicates that the SOC Viewer has detected an inconsistency in the modes of the two BAPs which could indicate that they are currently in the middle of a switchover. If you want a BAP in a particular mode then you should try again in a few minutes after watching the modes in the display of the BAP status in the SOC Banner window. If not then try A or B. If you see a message such as:
BAPA is not defined - please contact system operator

then this indicates that the SOC workstation is not correctly configured and it currently does not know the physical node name of the BAP in question. To correct this you should log into the operational account (SOCSYS) on the workstation and define the correct BAP node names by performing the configuration procedure described in section 4.2.5 before continuing. To finish using the SOC Viewer, return to the Main Menu and select (E) to exit and then enter <Y> to confirm. You will then be logged off the BAP and you will see:
Welcome back to the SOC Viewer Which node do you require? ((M)aster,(S)tandby,BAP(A),BAP(B) or F10 to exit) [M]:

At this point hit the F10 (Exit) function key or type Control-Z at which point the SOC Viewer window will disappear.

8-12

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico LES Software Startup

8.3.2 Starting the SOC Viewer from the BAP To access the SOC Viewer directly from the BAP login to the captive account (BAPV) on the BAP on which you wish to run the SOC Viewer. To do this either locate a terminal directly connected to the BAP or login to another machine and use the SET HOST command to access the BAP. In response to the prompt Username: enter the name of the captive account (BAPV). After a few seconds the Main Menu should appear. If you want a BAP in a particular mode then trial and error will need to be used to find the correct one. The mode and logical name of the BAP is indicated in the top right corner of the screen in the Main Menu, e.g. MASTER BAPA. To finish using the SOC Viewer, return to the Main Menu and select (E) to exit and then enter <Y> to confirm. You will then be logged off the BAP. If you have used the SET HOST command you will be returned to the machine you initially logged into. You should also log off this machine.

8-13

Customer Release Configuration Guide Telecomunicaciones De Mexico

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

8-14

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Chapter 9 Tracing the Running System


. This chapter shows how to obtain tracing information from the running LES system on the BAP and SOC processors. 9.1 Tracing facilities on the BAP To see the states of all the LES processes running on the BAP enter: $ BAPOP SHOW STATE A display will then be shown such as:
PRC Ready TRUE Commanded Processor Mode MASTER Introduced TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALSE Processor Mode MASTER Current State RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING UNKNOWN Processor State RUNNING Desired State RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING RUNNING UNKNOWN Synchronizing FALSE Notify_On Responded State_Change TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALSE TRUE TRUE TRUE TRUE TRUE FALSE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALSE TRUE TRUE TRUE TRUE TRUE FALSE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALSE FALSE

Ind Task Name 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 APM_P_01 CUC_BAP_MSD__01 DCD_MGR_P_01 DIM_LINK_MGR_01 DIM_LINK_MGR_02 DIM_LINK_MGR_03 DIM_LINK_MGR_04 EM_P_01 ERRLOG_01 FAXCC_DRIVER_01 FAXLM_DRIVER_01 FCR_BAP_CONN_01 FDCD_EXT_MGR_01 FDCD_EXT_MGR_02 FEH_BAP_MAIN_01 IC_BAP_MSD_P_01 LFM_FILE_SER_01 MC_LOGGER_P_01 MCM_P_01 MDIR_P_01 PRC_EVENT_MO_01 PRC_HANDSHAK_01 PRC_PROC_STA_01 PRC_TASK_STA_01 RG_P_01 SDC_MAIN_P_01 SM_P_01 SOI_SERVER_P_01 TACC_DRIVER__01 TOKM_P_01 XCCC_P_01 PADR_MAIN_P_01 SADINIT_01

An alternative command is: $ BAPOP SHOW BAP which produces a display such as the following:
BAP version Rel80110 from disk $1$DIA4: The Current State of the BAP is :STARTED 9-JUL-1993 18:49:51.81

9-1

Customer Release Configuration Guide Telecomunicaciones De Mexico Tracing the Running System
The Current Processor Mode is The Current Processor State is :MASTER :RUNNING

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Show Active BAP Processes <Y/[N]>: <Y> Process# Process Name 208010E7 20800507 20800509 2080050C 2080050E 20800512 20800514 20800516 20800518 2080051A 2080051C 2080051E 20800521 20800523 20800526 20800528 2080052A 20800530 20800532 20800534 20800603 20800605 20800615 2080061A 2080061C 20800620 20800625 2080062A 2080062D 20800632 20800634 20800636 20800638 2080063A 2080063E Terminal NVA1: Image [BAPSW.REL7200.SAD.EXECUTE]SAD_SHOW_GROUP_P.EXE;1 [BAPSW.REL7200.PIPM.EXECUTE]PIPM_SERVER_P.EXE;1 [BAPSW.REL7200.PRC.EXECUTE]PRC_ARBITER_MANAGER_P.EXE;1 [BAPSW.REL7200.APM.EXECUTE]APM_P.EXE;1 [BAPSYS.INSTALL]SAD_BAP_IMAGE_P125.EXE [BAPSW.REL7200.DCD.EXECUTE]DCD_MGR_P.EXE;1 [BAPSYS.INSTALL]DIM_LINK_MGR_P125.EXE [BAPSYS.INSTALL]DIM_LINK_MGR_P125.EXE [BAPSYS.INSTALL]DIM_LINK_MGR_P125.EXE [BAPSYS.INSTALL]DIM_LINK_MGR_P125.EXE [BAPSW.REL7200.EM.EXECUTE]EM_P.EXE;1 [BAPSW.REL7200.ERR.EXECUTE]ERRLOG.EXE;1 [BAPSW.REL7200.FAXCC.EXECUTE]FAXCC.EXE;1 [BAPSW.REL7200.FAXLM.EXECUTE]FAXLM.EXE;1 [BAPSYS.INSTALL]SAD_BAP_IMAGE_P125.EXE [BAPSW.REL7200.FDCD.EXECUTE]FDCD_EXT_MGR_P.EXE;1 [BAPSW.REL7200.FDCD.EXECUTE]FDCD_EXT_MGR_P.EXE;1 [BAPSYS.INSTALL]SAD_BAP_IMAGE_P125.EXE [BAPSYS.INSTALL]SAD_BAP_IMAGE_P125.EXE [BAPSW.REL7200.LFM.EXECUTE]LFM_FILE_SERVER_P.EXE;1 [BAPSW.REL7200.MC.EXECUTE]MC_LOGGER_P.EXE;1 [BAPSW.REL7200.MCM.EXECUTE]MCM_P.EXE;3 [BAPSW.REL7200.MDIR.EXECUTE]MDIR_P.EXE;1 [BAPSW.REL7200.PRC.EXECUTE]PRC_EVENT_MONITOR_P.EXE;1 [BAPSYS.INSTALL]SAD_BAP_IMAGE_P125.EXE [BAPSYS.INSTALL]SAD_BAP_IMAGE_P125.EXE [BAPSYS.INSTALL]SAD_BAP_IMAGE_P125.EXE [BAPSW.REL7200.RG.EXECUTE]RG_P.EXE;1 [BAPSW.REL7200.SDC.EXECUTE]SDC_MAIN_P.EXE;1 [BAPSW.REL7200.SM.EXECUTE]SM_P.EXE;1 [BAPSW.REL7200.SOI.EXECUTE]SOI_SERVER_P.EXE;2 [BAPSW.REL7200.TACC.EXECUTE]TACC_DRIVER_P.EXE;1 [BAPSW.REL7200.TOKM.EXECUTE]TOKM_P.EXE;1 [BAPSW.REL7200.XCCC.EXECUTE]XCCC_P.EXE;1 [BAPSW.REL7200.FAXLO.EXECUTE]FAXLO.EXE;1

BAPSYS_01 PIPM_ATL PRC_ARB_01 APM_P_01 CUC_BAP_MSD__01 DCD_MGR_P_01 DIM_LINK_MGR_01 DIM_LINK_MGR_02 DIM_LINK_MGR_03 DIM_LINK_MGR_04 EM_P_01 ERRLOG_01 FAXCC_DRIVER_01 FAXLM_DRIVER_01 FCR_BAP_CONN_01 FDCD_EXT_MGR_01 FDCD_EXT_MGR_02 FEH_BAP_MAIN_01 IC_BAP_MSD_P_01 LFM_FILE_SER_01 MC_LOGGER_P_01 MCM_P_01 MDIR_P_01 PRC_EVENT_MO_01 PRC_HANDSHAK_01 PRC_PROC_STA_01 PRC_TASK_STA_01 RG_P_01 SDC_MAIN_P_01 SM_P_01 SOI_SERVER_P_01 TACC_DRIVER__01 TOKM_P_01 XCCC_P_01 FAXLO_01

This shows information as to the version and source of the LES software running and all LES processes in the operational group running in the system including other interactive operator processes. 9.1.1 Fault location on the BAP In the directory BAP$ERROR: there are a number of log files which are used by the processes to report error messages. $ TYPE/P BAP$ERROR:ERROR.LOG This file contains errors reported by all processes on the BAP. On the SOC, the following file contains all the error messages: $ TYPE/P SOC$ERROR:ERROR.LOG These files should be checked regularly for error messages which may indicate impending process failure. In the case of a post-mortem those files should be the first source of information.
9-2

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico Tracing the Running System

9.1.2 Process tracing on the BAP A process by process tracing mechanism is available. However this process tracing is normally switched off and information must be obtained on how to switch the trace on for each individual process. Not all processes have this facility. If the process trace is switched on, the output may be directly broadcast to any operator terminal logged into the operation account (BAPSYS). To direct the trace to your terminal enter the following command exactly as shown (note the single quotes ()): $ DEFINE/GROUP TRC(PROCESS NAME) F$TRNLNM("TT") where (PROCESS NAME) is the name of the process shown in the output from the BAPOP SHOW BAP command above. You should soon begin to see trace messages appearing spontaneously on your terminal as the process runs. To suspend the display of the command line prompt enter: $ WAIT 23 this will suspend the prompt (in this case) for 23 hours. To get the prompt back again type Control-C. To disable the trace messages enter: $ DEASSIGN/GROUP TRC(PROCESS NAME) It is possible to have more than one set of trace messages sent to one terminal, but the output may be confusing and since the messages are broadcast asynchronously there is the danger that they may not be displayed if they arrive in quick succession. All tracing processes must be switched off when no longer required and certainly before logout. This will prevent unnecessary degradation of the BAPs performance. The session can be logged out of without deassigning the logical name TRC(PROCESS NAME). The logout command file (SAD$EXE:SADLOGOUT.COM) will automatically deassign any trace logicals assigned to the terminal. 9.2 Tracing facilities on the SOC There is no equivalent on the SOC to the BAPOP SHOW STATE or BAPOP SHOW BAP commands available on the BAP. There is also no equivalent PRC command. Attempting to use the PRC tester will produce the following: $ RUN/NODEBUG PRC$EXE:PRC_TESTER_P
PRC Ready TRUE Commanded Processor Mode MASTER Introduced TRUE TRUE Processor Mode MASTER Current State RUNNING RUNNING Processor State INIT Desired State RUNNING RUNNING Synchronizing TRUE DB_SYNC Notify_On Responded State_Change FALSE FALSE TRUE TRUE

Ind Task Name 1 2 ERRLOG_01 MC_LOGGER_P_01

As a substitute to the BAPOP SHOW BAP command the following may be entered: $ SHOW SYSTEM
9-3

Customer Release Configuration Guide Telecomunicaciones De Mexico Tracing the Running System

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

This will produce a display such as:


VAX/VMS V6.0 on node GEMINI 01-NOV-1992 11:10:10.05 Uptime 4 00:25:12 Pid Process Name State Pri I/O CPU Page flts Ph.Mem 00000041 SWAPPER HIB 16 0 0 00:00:16.39 0 0 00000045 ERRFMT HIB 8 2932 0 00:00:18.77 95 133 00000046 OPCOM HIB 8 103 0 00:00:06.18 256 134 00000047 AUDIT_SERVER HIB 10 37 0 00:00:00.89 1363 408 00000048 JOB_CONTROL HIB 10 466 0 00:00:01.16 227 397 00000049 IPCACP HIB 10 7 0 00:00:00.11 89 147 0000004A TP_SERVER HIB 10 23104 0 00:03:54.37 180 261 0000004B NETACP HIB 9 938 0 00:00:05.93 211 391 0000004C EVL HIB 5 1686 0 00:00:06.27 101994 38 0000004D REMACP HIB 9 57 0 00:00:00.17 89 50 0000004F VWS$DISPLAYMGR HIB 7 4677 0 00:00:32.44 1080 871 00000050 VWS$EMULATORS HIB 6 17853 0 00:05:46.12 3971 270 00000191 PIPM_ATL HIB 4 21708 0 00:00:52.52 4398 1140 00000193 ERRLOG_01 LEF 6 246 0 00:00:05.96 4996 910 00000195 MC_LOGGER_P_01 LEF 6 159 0 00:00:05.90 5639 828 00000197 SOC_SRV_TASK_01 HIB 6 7990 0 00:11:24.08 7213 1462 00000198 SOC_BAN_TASK_01 HIB 6 431 0 00:16:01.26 8641 1794 00000199 SOC_SUD_TASK_01 HIB 4 11782 0 00:07:16.53 7938 1724 0000019A SOC_FKI_TASK_01 LEF 5 735 0 00:00:54.90 7878 1630 0000019E SOC_FRM_TASK_01 HIB 4 11135 0 00:44:19.14 103968 2041 000001A8 SOC_FRM_TASK_02 HIB 6 1558 0 00:01:38.28 10652 2039 000001A9 SOCSYS_01 CUR 4 256 0 00:00:06.81 4784 405

S S S S S

This shows all SOC processes running in the system including the VMS system processes and all other interactive operator processes. Alternatively the equivalent to the BAPOP SHOW BAP command on the BAP is indirectly available on the SOC by entering the following command: $ RUN/NODEB SAD$EXE:SAD_SHOW_GROUP_P which produces the following type of display:
Process# 23A0005C 23A0005E 23A00060 23A00062 23A00063 23A00064 23A00065 23A0007B 23A0007E 23A0007F Process Name Terminal PIPM_ATL ERRLOG_01 MC_LOGGER_P_01 SOC_SRV_TASK_01 SOC_BAN_TASK_01 SOC_SUD_TASK_01 SOC_FKI_TASK_01 SOC_FRM_TASK_01 SOC_FRM_TASK_02 SOCSYS_01 RTA1: Image [SOCSW.REL7200.PIPM.EXECUTE]PIPM_SERVER_P.EXE;1 [SOCSW.REL7200.ERR.EXECUTE]ERRLOG.EXE;1 [SOCSW.REL7200.MC.EXECUTE]MC_LOGGER_P.EXE;1 [SOCSW.REL7200.SOC.EXECUTE]SOC_SRV_TASK.EXE;1 [SOCSW.REL7200.SOC.EXECUTE]SOC_BAN_TASK.EXE;1 [SOCSW.REL7200.SOC.EXECUTE]SOC_SUD_TASK.EXE;1 [SOCSW.REL7200.SOC.EXECUTE]SOC_FKI_TASK.EXE;1 [SOCSW.REL7200.SOC.EXECUTE]SOC_FRM_TASK.EXE;1 [SOCSW.REL7200.SOC.EXECUTE]SOC_FRM_TASK.EXE;1 [SOCSW.REL7200.SAD.EXECUTE]SAD_SHOW_GROUP_P.EXE

As on a BAP a process by process tracing mechanism is available. The slight degradation in performance is insignificant and message carrying is completely unaffected. For this reason the tracing mechanism is always switched on. The output from this process trace may be directly broadcast to any operator terminal logged into the operational account (SOCSYS). To direct the trace to your terminal enter the following command exactly as shown (note the single quotes ()): $ DEFINE/GROUP TRC(PROCESS NAME) F$TRNLNM("TT") where (PROCESS NAME) is the name of the process shown in the output from the SHOW SYSTEM command above. You should soon begin to see trace messages appearing spontaneously on your terminal as the process runs. To suspend the display of the command line prompt enter:

9-4

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico Tracing the Running System

$ WAIT 23 this will suspend the prompt (in this case) for 23 hours. To get the prompt back again type Control-C. To disable the trace messages enter: $ DEASSIGN/GROUP TRC(PROCESS NAME) It is possible to have more than one set of trace messages sent to one terminal, but the output may be confusing and since the messages are broadcast asynchronously there is the danger that they may not be displayed if they arrive in quick succession. The session can be logged out of without deassigning the logical name TRC(PROCESS NAME). The logout command file (SAD$EXE:SADLOGOUT.COM) will automatically deassign any trace logicals assigned to the terminal. In addition to the process trace facility there is another trace mechanism for monitoring the operations involved in the display and capture of data in the SOC forms. The SOC uses TDMS, a DEC package for implementing the forms, and this can provide a trace to see what is happening within them. There are two methods of enabling the TDMS trace from SOC forms. Neither method requires the SOC to be shutdown. The first method is to define the group logical TSS$TRACE_OUTPUT to be the name of a file. The following command is suggested: $ DEFINE/GROUP TSS$TRACE_OUTPUT SOC$ERROR:SOC_FRM_TASK.TRACE If you now request a new form, upon starting up, the process will translate this logical name and this alone will cause the TDMS trace to be switched on with the output going to the file SOC$ERROR:SOC_FRM_TASK.TRACE. With this method, if you leave this logical defined, each new form will produce a new version of this file with the same name. It may or may not be important to know which file relates to which form. The second method involves editing the file SOC$EXE:SOC_START.COM. To do this you should create a copy of this file in the COMDEV SOC_EXE area first and then edit the copy rather than changing the original in the baseline area. When you have finished you can just delete the copy and the original will be used again. The change that should be made to the file is to uncomment the following line:
$!---- $ IF ImageToRun .EQS. "SOC_FRM_TASK" THEN DEFINE /NOLOG TSS$TRACE_OUTPUT SOC$ERROR:ImageMainProcedure.TRACE

so that it appears as follows (it has been split into two lines here for clarity, but it is in fact only one line in the file):
$ IF ImageToRun .EQS. "SOC_FRM_TASK" THEN DEFINE /NOLOG TSS$TRACE_OUTPUT SOC$ERROR:ImageMainProcedure.TRACE

This time when a new form starts up it will translate its own process logical name which is defined to be a file which includes the process name, so it is more apparent which file belongs to which form process. In both of these methods you should not attempt to define the logical to be a terminal device in the style of the process trace logicals above. Doing this will cause the SOC to crash as
9-5

Customer Release Configuration Guide Telecomunicaciones De Mexico Tracing the Running System

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

soon as you create the next form process. Also since the output file is not opened by TDMS for shared access, it is not possible to see to contents of the file until you logout and exit from the form window concerned, causing the form process to terminate. Only then will the file be closed and become accessible to you. NOTE: These TDMS trace logicals are not automatically deassigned when you log off since the output is not related to a terminal. After you have finished collecting trace output and you have closed all the form windows created, it is essential that you DEASSIGN the group logical TSS$TRACE_OUTPUT or DELETE the file SOC_EXE:SOC_START.COM according to which method you have used. Failing to do this will mean that the workstation disk will rapidly fill up and the workstation will eventually fail. If the trace files are on the system disk then this could render the workstation unusable.

9-6

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Chapter 10 Procedure to revert to an old version of BAP or SOC


. In the case of a failed upgrade, it is necessary to revert to the old version of the software. This section details the actions necessary for this. It is assumed that 1 BAP and 1 SOC only have been upgraded and that the Standby nodes still have the old version of the software. Fallback should only be performed in conjunction with HNS Staff. In some instances it may be possible to curtail certain steps, thus shortening the time to recovery. 10.1 BAP Fallback procedure Unless otherwise stated, the following actions are sequential and should be carried out without interuption so that, for example, the exit state from one action (i.e. database running) is the starting state of the next. It is assumed that the non-upgraded BAP is not running. 10.1.1 BAP Fallback procedure Summary This section lists the steps to be followed in order to restore the old system. Stop the BAP which had been upgraded. Save current live data Restore the database upon that BAP. Rename the FEP load files and re-trigger the FEPs Start the BAP which had not been upgraded. Restore the old software on the upgraded BAP. Start the now restored BAP. 10.1.2 Stop the upgraded BAP The upgraded BAP must be stopped to allow the latest live data to be saved and to start the online database on the other BAP prior to restoration. $ BAPOP STOP BAP At this point BOTH BAPs will be stopped 10.1.3 Save current live data Several tables must be dumped to Population files. The total disk space and time that this process will require is dependant on the level of system activity and the size and number of
10-1

Customer Release Configuration Guide Telecomunicaciones De Mexico Procedure to revert to an old version of BAP or SOC

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

entries in each table. The Mobile table alone may require in excess of 35000 blocks and take ten minutes to produce. Note, these files will be created in the PINS$EXE directory on the upgraded BAP and will be deleted when that BAP is re-installed. Log into the account BAPSYS on the upgraded BAP (where the online database server is running - see section 7.2.2 for instructions on verifying this) and follow these steps: Start the DATABASE VIEWER & POP FILE GENERATOR by entering: $ @PINS$EXE:PINS_VIEWER_START Enter 2 to select PINS POP File Generator from the menu. From the PINS POP FILE GENERATOR menu enter 3 to start the MH Specific tables menu. Dump the MAR_Control table (which contains the latest message reference number) by entering 2. Dump the Msg Details tables (MD_MDS, MD_DDS, MD_DDS_Array and PINS_MD_REMOTE_DEL_STATUS) by entering 7. Enter 8 to select MH Specific tables menu 2. Dump the DRH tables (DRH_PIN, DRH_DNID and DRH_Entry) by entering 2. Dump the EGC_Seq_Num table (which contains the latest EGC sequence number for each OR) by entering 3. Dump the CRM table (which contains the latest the latest Call Serial Number by entering 7 Enter 0 in two menus, returning to the PINS POP FILE GENERATOR menu. Select the General tables menu by entering 7. Dump the Regd_User tables (Regd_User, Regd_User_DNID, Regd_User_Info_Provider, Regd_User_EGC_ID, Regd_User_NUA, Regd_User_Mobile and Regd_User_Poll_Seq_Num) by entering 2. Dump the Mobile table by entering 6. Enter 0 in two menus, returning to the Main Menu Select the User Specified PINS POP File Generator menu by entering 3 and enter DRH_Usage to generate the DRH_Usage table. Enter 0, then enter Y to fully exit the DATABASE VIEWER & POP FILE GENERATOR. The following files will have been created in the directory PINS$EXE: Current message and EGC details: PINS_CRM.POP
10-2

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico Procedure to revert to an old version of BAP or SOC

PINS_MAR_CONTROL.POP PINS_MD_DDS.POP PINS_MD_DDS_ARRAY.POP PINS_MD_MDS.POP PINS_MD_REMOTE_DEL_STATUS.POP PINS_EGC_SEQ_NUM.POP Data report details: PINS_DRH_DNID.POP PINS_DRH_ENTRY.POP PINS_DRH_PIN.POP PINS_DRH_USAGE.POP Registered User information: PINS_REGD_USER.POP PINS_REGD_USER_DNID.POP PINS_REGD_USER_EGC_ID.POP PINS_REGD_USER_INFO_PROVIDER.POP PINS_REGD_USER_MOBILE.POP PINS_REGD_USER_NUA.POP PINS_REGD_USER_POLL_SEQ_NUM.POP Mobile registrations: PINS_MOBILE.POP These POP files will be used to upgrade these tables in the old database once it has been restored. 10.1.4 Restoring the database 10.1.4.1 Restore previous DB dump The database dump, taken just prior to the upgrade, is now to be restored using the following procedure. This may take 30 minutes or more. The preparatory work defined in section 10.1.4.2 below and the FEP actions described in section 10.1.5 may both be started while the database is reloading. Using the naming scheme and file location defined in section 7.2 for the dumping of the
10-3

Customer Release Configuration Guide Telecomunicaciones De Mexico Procedure to revert to an old version of BAP or SOC

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

original database, define PINS_EXE as the directory containing the required dump, and rename the dump file so that it will be recognised by the database loader: $ DEFINE/GROUP PINS_EXE: $1$DIA3:[UPGRADE_LES_DUMP] $ RENAME/LOG PINS_EXE:CES_ONDB_CES_DISKDUMP_(REL_NO).DMP PINS_EXE:[UPGRADE_LES_DUMP]CES_DISKDUMP.DMP The database may now be restored: $ SA 1> load database CES_ONDB from PINSDISKDUMP 2> <> 1> exit 10.1.4.2 Restore live data Data saved in section 10.1.3 may now be restored A decision will be made in conjunction with HNS as to which POP files will be re-loaded. This will be dependant on what changes occurred in the conversion and what new entries have been made in the database since the system was started with the new software. Some files may need to be edited to remove fields which do not exist in the new version. The software release notes will contain specific details. HNS staff will do this prior to loading the files into the database. Then the POP files will be loaded to ensure live message details and other changes have been brought forward. 10.1.5 Rename FEP load files and re-trigger FEPS Having restored the database, ensure that all FEP original SYS file names have been restored and that the load files are defined correctly, using the original files/locations on this BAP. If the corresponding (new) files are still accessible on the upgraded BAP, then these should be deleted before re-triggering the FEPs To remove the unwanted new files, log on to the UPGRADED BAP, using the BAPSYS account: $ DEL/LOG FELNSYS$EXE:FEP*.SYS;* Then, on the UN-upgraded BAP: Enter:
$ Set Def FELNSYS$EXE $ Pur *.SYS $ Dir *.SYS

This should show the following files:


FEP_MAIN_P.SYS_OLD FEP_MAIN_P.SYS_3100_80_OLD

10-4

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


FEP_MAIN_P.SYS_95_OLD

Customer Release Configuration Guide Telecomunicaciones De Mexico Procedure to revert to an old version of BAP or SOC

Then enter:
$ $ $ $ Rename FEP_MAIN_P.SYS_OLD FEP_MAIN_P.SYS Rename FEP_MAIN_P.SYS_3100_80_OLD FEP_MAIN_P.SYS_3100_80 Rename FEP_MAIN_P.SYS_95_OLD FEP_MAIN_P.SYS_95 Dir *.SYS*

The final command should verify that all the SYS files have been renamed, thus making them available for FEP loading. Now re-trigger all FEPs $ MC NCP TRIGGER NODE <fep_name> 10.1.6 Restart unaffected BAP The BAP may restarted. $ BAPOP START BAP ARBITER 10.1.7 Restore the software on the upgraded BAP. In this section the upgraded BAP and SOC will be restored with the old version of the LES software. Dismount the system disk from the BAP that does not use it (i.e. if the system disk is used by BAPA, dismount it from BAPB). Section 3.2.2 describes how this is done. On the BAP which uses the system disk, the disk can be restored with the BAP running as normal, or in standalone mode. Section 3 describes how to shut down the BAP and boot it as standalone. Otherwise, logon to account SYSTEM on the BAP. Restore the image backup. $ BACKUP/IMAGE/LOG MKA500:FULLBACK.BCK/IGNORE=LABEL/REW $1$DIA5: Where MKA500: is the tape drive and $1$DIA5: is the system disk. NOTE: Once the BAP has been restored, this disk must be correctly remounted on both nodes. See section 3.5 for an example. The command file described must be run from the system account of the node from which the disk had been dismounted. Alternatively, the relevant command, for the disk in question, may be entered at the system prompt. 10.2 SOC Fallback procedure Stop the upgraded SOC and restore the previous system disk dump. The disk must be restored in standalone mode. Section 3 describes how to shut down the SOC and boot it as standalone. Restore the image backup. $ BACKUP/IMAGE/LOG MKA500:FULLBACK.BCK/IGNORE=LABEL/REW DKA300: Where MKA500: is the tape drive and DKA300: is the system disk.

10-5

Customer Release Configuration Guide Telecomunicaciones De Mexico

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

10-6

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Chapter 11 BAP Maintenance


. This chapter covers the occasional maintenance needs for the system. Changes covered here would be due to a change in configuration or in response to a problem. These activities will normally be performed by HNS. 11.1 Changing the Ocean Areas and Spot IDs The Ocean Regions and Spot IDs are defined for the initial installation of a BAP by the file CUTL$EXE:CUTL_MH_CONVERSION_(CUSTOMER).DAT Where (CUSTOMER) refers to the systems operators, e.g. CUTL$EXE:CUTL_MH_CONVERSION_MEXICO.DAT. The contents of this file is copied to the file CUTL$DAT:CUTL_MH_CONVERSION.DAT as part of that initial installation. Ocean regions and Spot IDs may occasionally need to be redefined. This is achieved by editing the data file which defines them, and then converting the system table. Edit the data file: $ EDIT CUTL$DAT:CUTL_MH_CONVERSION.DAT The Ocean Regions and Spot IDs have both name and full name specified. E.g.
Ocean_Region 0 Name R11 Full_Name R1Rack1 Ocean_Region 1 Name R12 Full_Name R1Rack2 Spot_ID 0 Name GSP Full_Name All Spots Spot_ID 1 Name ESP Full_Name Eastern

Once the file has been amended then the system table may be updated. To do this enter: $ RUN/NODEBUG MDIR$EXE:MDIR_VIEW_P A number of commands are listed. From these enter: Command: MANAGE_CONV_TABLE A list of conversion table commands is displayed. From these enter: Conversion table Command: RESTORE_CONV_TABLE Then reply to the prompt with the data file name: File name: CUTL$DAT:CUTL_MH_CONVERSION.DAT Enter QUIT twice to return to the $ prompt.
11-1

Customer Release Configuration Guide Telecomunicaciones De Mexico BAP Maintenance

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

11.2 Changing the Janitor Criteria Calls on the satellite side of the BAP are monitored and deleted if they appear to have become stuck. This is monitored by the janitor process, part of the satellite driver. It checks, where applicable, that messages have not stayed in any one state for longer than is acceptable. It may be necessary to change the criteria of the janitor process. The criteria by which messages are failed are specified in the file MCM$EXE:JANITOR.INI. This file describes against each state: Check - Either TRUE or FALSE, whether a message is subject to any checking. Events - Either TRUE or FALSE, whether a message has any events queued to act upon it. If TRUE is returned then the message has active events and is not deleted. Timers - Either TRUE or FALSE, whether a message is has a timer associated. If true TRUE If TRUE is returned then the message has an active timer and is not deleted. Duration - The value (in seconds) that a message may stay in that state before it is eligible for deletion. The final value The interval to check the AST list on is the period at which messages are checked. An example of the file JANITOR.INI is listed below. The lines starting with are comments and are thus ignored by the system.
* This file contains the janitor task start up configuration * SS01 Not in Region * Check Events Timers Duration FALSE FALSE FALSE 3600.0 * * SS02 In Region * Check Events Timers Duration TRUE FALSE TRUE 3600.0 * * SS03 Wait * Check Events Timers Duration FALSE FALSE FALSE 3600.0 * * SS04 wait for congestion * Check Events Timers Duration FALSE FALSE FALSE 3600.0 * * SS06 wait for NCS individual poll * Check Events Timers Duration FALSE FALSE FALSE 3600.0 * * SS61 wait for Test * Check Events Timers Duration FALSE FALSE FALSE 3600.0 * * SS62 wait for distress test * Check Events Timers Duration FALSE FALSE FALSE 3600.0 * * SS71 wait fort NCS announce * Check Events Timers Duration FALSE FALSE FALSE 3600.0

11-2

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


* * SS72 wait for SES reply announce * Check Events Timers Duration TRUE TRUE TRUE 3600.0 * * SS73 wait for NCS cancel * Check Events Timers Duration FALSE FALSE FALSE 3600.0 * * SS75 wait for NCS distress * Check Events Timers Duration FALSE FALSE FALSE 3600.0 * * SS90 wait for CUC ship to shore * Check Events Timers Duration TRUE TRUE TRUE 3600.0 * * SS91 wait for CUC shore to ship * Check Events Timers Duration TRUE TRUE TRUE 3600.0 * * SS92 wait for CUC test * Check Events Timers Duration FALSE FALSE FALSE 3600.0 * * The interval to check the AST list on * 180.0

Customer Release Configuration Guide Telecomunicaciones De Mexico BAP Maintenance

To update the criteria of the janitor process: 1. On both BAPs, edit the janitor file with the new values, enter: $ EDIT MCM$EXE:JANITOR.INI 2. Switch BAPs from the SOC. 11.3 Changing the Channel Unit Rack Displaying Summary Alarms The ASM module in the top tray of a channel unit rack can indicate alarms (with severity) or SCP line failure. Only one Channel Unit rack in an LES will be used for alarms. Generally, this is the Channel Unit rack for the lowest numbered Ocean Region. However, any Channel Unit rack can be configured to display alarms. The file EM_EXE:EM_MC_FLAG.INI configures the Channel Unit rack displaying alarms by: Specifying if a specified Channel Unit rack is to be used. Specifying which Ocean Region corresponds to the Channel Unit rack to display alarms. This file will normally be configured by HNS prior to system installation. The two flags in the file are: Override_Alarm_Region - Set to 0 if the default channel unit is satisfactory (i.e. that for the lowest Ocean Region), set to 1 if an Ocean Region is to be specified. Alarm_Region - The Ocean Region corresponding to the Channel Unit rack which is to display alarms (and is not the default).

11-3

Customer Release Configuration Guide Telecomunicaciones De Mexico BAP Maintenance

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

The Ocean Regions are numbered: 0 1 2 3 AORW AORE POR IOR

The file for Telecomunicaciones De Mexico is:


Override_Alarm_Region Alarm_Region 0 0

To modify the Channel Unit rack displaying alarms: 1. Edit EM_MC_FLAG.INI to reflect the desired configuration: $ EDIT EM_EXE:EM_MC_FLAG.INI 2. Perform a BAP switchover from the SOC to effect the change.

11-4

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Chapter 12 FAX Installation


The LES FAX system has two major components, a Fax driver running on the BAP and PCFAX software running on the Fax PCs. Messages for Fax transmission are collected by the BAP Fax driver and passed to the PC FAX software via a shared disk area. The PCFAX software is responsible for Fax message delivery reporting back to the BAP once message delivery has completed. This chapter describes the procedures for installing and upgrading LES FAX, particularly concerning the installation and configuration of the Fax PCs. Section 12.1 is concerned with the installation of the fax PCs and Pathworks on the BAP from scratch, whilst Section 12.2 deals with upgrading the software on the Fax PCs. Section 12.4 provides some details on how to investigate and rectify problems relating to FAX. 12.1 Hardware and Software Installation The PC hardware requirements are: A minimum of 2 PCs capable of running Microsoft Windows and IBM OS/2 operating systems. 1 Etherworks card per PC. Modem cards (typically 4 per PC). Some customers may have a spare PC and/or spare modems and etherworks cards. Ethernet connection must be established to the two PCs intended for use. This must be done prior to the software installation, otherwise certain processes will not start.

12-1

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

VAX System (BAP A)


LES Fax Driver DSSI Bus LES Software

SHADOWSET DSSI Bus PC_A Work Area PC_B Work Area PC_C Work Area PC_D Work Area

VAX System (BAP B)


LES Fax Driver LES Software

Pathworks Server

Pathworks Server

Ethernet
Route M Fax PC A Fax PC B PC FAX Driver Pathworks Zetafax Server Client Fax Modem Fax Modem Fax Modem Fax Modem Etherworks Route M Fax PC C PC FAX Driver Pathworks Zetafax Server Client Fax Modem Fax Modem Fax Modem Fax Modem Etherworks Route N Fax PC D PC FAX Driver Pathworks Zetafax Server Client Fax Modem Fax Modem Fax Modem Fax Modem Etherworks Route N

Fax Modem

Fax Modem

Fax Modem

Fax Modem

Etherworks

12-2
[lesfax.eps]

PC FAX Driver Pathworks Zetafax Server Client

PSTN

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Figure 12-1. FAX Configuration

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

In summary the installation steps for each PC are : 1. Install Etherworks card (see section 12.1.3). 2. Install Modem cards (see section 12.1.4). 3. Install Operating System (see section 12.1.7). 4. Install NTS/2 and LAPS software (see section 12.1.8). 5. Install Etherworks software (see section 12.1.9). 6. Install LAN Server/Requester software (see section 12.1.10). 7. Install Pathworks software (see section 12.1.12). 8. Install Zetafax software from Scratch (see section 12.1.14). 9. Install PC Fax software (see section 12.1.15). In addition to the configuration of the PCs it is also necessary to install Pathworks on the LES and configure the LESFAX database tables. 12.1.1 Install Pathworks on the LES Prior to this installation, a backup of the System Disk should be performed. If this installation is being performed on a Live system, the first BAP to be upgraded should be the Standby. Logon to the Standby BAP as SYSTEM. $ Mount/System DKA400: VAXBINJAN945 $ SET DEF SYS$UPDATE $ @VMSINSTAL PCSAU1042 DKA400:[PCSAU1042.KIT] OPTIONS N Where is DKA400: the system disk device and VAXBINJAN945 is its label.
VAX/VMS Software Product Installation Procedure V5.5-2H4 It is 30-JUN-1994 at 12:52. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? <> The following products will be processed: PCSAU1 V4.2 Beginning installation of PCSAU1 V4.2 at 12:52 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. 2. Display release notes Print release notes

12-3

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation


3. 4. Both 1 and 2 None of the above

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

* Select option [2]: 4 * Do you want to continue the installation [NO]? YES %VMSINSTAL-I-RELMOVED, Products release notes have been moved to SYS$HELP. ********************************************************************** PATHWORKS for VMS V4.2-1 installation procedure ********************************************************************** Installation taking place on an OpenVMS VAX system. %PCSAU1-I-VERSION, Checking for OpenVMS VAX version 5.3 or greater... %PCSAU1-I-VERSOK, VMS version meets requirements, proceeding... * Do you want to run the IVP after the installation [YES]? <> * Do you want to purge files replaced by this installation [YES]? <> %PCSAU1-I-FREEBLKS, Checking for 9000 free blocks %PCSAU1-I-CHK_NET, Checking to see if DECnet is running * Disk Name for PCSA system/application software [SYS$SYSDEVICE]: <> * Disk Name for User accounts, COMMON services [SYS$SYSDEVICE]: (Shadow_Disk) : * Group number for PCFS software directories [360]: <> * Disk Name for LAD BOOT disks [SYS$SYSDEVICE]: <> All questions have been answered. The installation of PATHWORKS for VMS V4.2-1 will continue. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %PCSAU1-I-DIRECTORY, Checking for [PCSA] on the system disk %VMSINSTAL-I-SYSDIR, This product creates system directory [PCSA]. If you intend to execute this layered product on other nodes in your VAXcluster, and you have the appropriate software license, you must prepare the system-specific roots on the other nodes by issuing the following command on each node (using a suitably privileged account): $ CREATE /DIRECTORY SYS$SPECIFIC:[PCSA] %PCSAU1-I-CRE_RBDB, Creating the Remote Boot Service Database %PCSAU1-I-CRE_ACF, Creating the File Service Database %PCSAU1-I-CRE_LAD_ACF, Creating the Local Area Disk Service Database %PCSAU1-I-INITIAL, Creating the initial Server directory structure %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[PCFS_SPOOL]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[PCFS_SPOOL.DEFAULT]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[PCSA]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[PCSA.LAD]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[LADBOOT]. %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PCFS$ACCOUNT. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier PCFS$ACCOUNT value: [000360,000001] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PCFS$ACCOUNT. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PCFS$ACCOUNT. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PCFS$ACCOUNT.

12-4

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

%UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PCFS$ACCOUNT. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PCSA$RMI. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier PCSA$RMI value: [000360,000002] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PCSA$RMI. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PCSA$RMI. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PCSA$RMI. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PCSA$RMI. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PCSA$RMI. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation adds an identifier named PCFS$READ. %UAF-I-RDBADDMSG, identifier PCFS$READ value: %X8001000A added to rights database %VMSINSTAL-I-ACCOUNT, This installation adds an identifier named PCFS$UPDATE. %UAF-I-RDBADDMSG, identifier PCFS$UPDATE value: %X8001000B added to rights data base %VMSINSTAL-I-ACCOUNT, This installation adds an identifier named NETBIOS$ACCESS. %UAF-I-RDBADDMSG, identifier NETBIOS$ACCESS value: %X8001000C added to rights data base %VMSINSTAL-I-ACCOUNT, This installation adds an identifier named PCFS$USER. %UAF-I-RDBADDMSG, identifier PCFS$USER value: %X8001000D added to rights database %PCSAU1-I-CRE_PARAMS, Creating Service Parameter Database %PCSAU1-I-CRE_PCFS_LOG, Creating PCFS_LOGICALS.COM %PCSAU1-I-CRE_LAD_LOG, Creating LAD_LOGICALS.COM %PCSAU1-I-DEF_OBJS, Defining DECnet objects PCFS,PCSA$RMI,PCX$SERVER,and PCSA$MAIL %PCSAU1-I-SPECIFY, Specifying target directories for the appropriate files %PCSAU1-I-REPLACE, PCFS$STARTUP_PARAMS.DAT has been replaced POST INSTALLATION INSTRUCTIONS To complete the installation of PATHWORKS for VMS you must invoke the PCSA$CONFIG utility as documented in the installation guide: $ @SYS$STARTUP:PCSA$CONFIG PCSA$CONFIG may ask you to reboot your system to apply the system configuration changes that it may make. Please note that if you are NOT required to reboot your system after running PCSA$CONFIG, you may still have to reboot to use the LAST, LANS, LAD, or LADC drivers installed by this kit. * Press RETURN to continue: <> After running PCSA$CONFIG you may start the file server using the specified transport(s): For DECnet, For TCP, For DECnet and TCP, @SYS$STARTUP:PCFS_STARTUP @SYS$STARTUP:PCFS_STARTUP TCP @SYS$STARTUP:PCFS_STARTUP DECNET/TCP

You may start the disk server by using the command: $ @SYS$STARTUP:LAD_STARTUP Be sure to add these commands to your system-specific startup procedure so that PATHWORKS for VMS will be started automatically every time your system restarts.

12-5

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation


* Press RETURN to complete the installation: <>

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Starting Installation Verification Procedure for PATHWORKS for VMS V4.2-1 at 30-JUN-1994 12:58 IVP Completed Successfully at 30-JUN-1994 12:59 Installation of PCSAU1 V4.2 completed at 12:59 VMSINSTAL procedure done at 12:59

Now the initial configuration procedure must be performed. $ @SYS$STARTUP:PCSA$CONFIG


PATHWORKS for VMS Initial Configuration procedure Checking SYS$SPECIFIC directories for files that interfere with the running of PATHWORKS for VMS... Cluster Configuration %SYSMAN-I-ENV, current command environment: Individual nodes: THBAPB Username SYSTEM will be used on nonlocal nodes %SYSMAN-I-ENV, current command environment: Clusterwide on local cluster Username SYSTEM will be used on nonlocal nodes %SYSMAN-I-OUTPUT, command execution on node THBAPA %DCL-E-OPENIN, error opening SYS$COMMON:[PCSA]PCSA$PARAMS.COM; as input -RMS-E-DNF, directory not found -SYSTEM-W-NOSUCHFILE, no such file %SYSMAN-I-OUTPUT, command execution on node THBAPB Setting DECnet objects ... PCFS PCSA$RMI PCX$SERVER PCSA$MAIL object object object object defined/set... defined/set... defined/set... defined/set...

%RENAME-I-RENAMED, SYS$COMMON:[PCSA]PCSA$PARAMS.COM;1 renamed to SYS$COMMON: [PCSA]PCSA$PARAMS.COMPLETE;1 Checking system parameters... Calling Configuration menu .... The screen changes to a form entitled Configure Server Parameters Type CTRL-D for advanced parameters - change the number of Workstations to 4 and Open files per workstation to 5. Then type CTRL-E. Press Return when prompted. The ADMINISTER verb must be added to your DCL tables before you can run PATHWORKS for VMS. Exit the menu system and reboot the system now for the system DCL tables to be updated. Press any key to continue ... Checking LAST CIRCUIT_MAXIMUM parameter... No changes required

12-6

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


Configuration Completed

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

$ EDIT SYS$MANAGER:SYSTARTUP_V5.COM Add the line @SYS$STARTUP:PCFS_STARTUP after DECNET is started in this file. Add PC node identifiers and names to the NCP database. For example assuming node names of HNSFXA and HNSFXB with node addresses of 43.180 and 43.181 respectively : $ MC NCP NCP> DEFINE NODE 43.180 NAME HNSFXA NCP> DEFINE NODE 43.181 NAME HNSFXB NCP> EXIT These will be copied into the volatile database on rebooting. Modify the file SYS$COMMON:[SYS$STARTUP]PCFS_LOGICALS.COM This file defines a default set of logicals and then appends the specific values given at installation time. Modify the final occurrence of the definition of PCFS$SERVICE_DATABASE to point to a directory (SHADOW_DISK:[PCSA]) Save the file and exit the editor. Create a directory [PCSA] on (SHADOW_DISK), by: $ CREATE/DIR (SHADOW_DISK):[PCSA] $ COPY/LOG SYS$COMMON:[PCSA]PCFS$SERVICE_DATABASE. (SHADOW_DISK): [PCSA] $ SET DEF SYS$SYSTEM Check and determine the RID codes for PCFS$READ, PCFS$UPDATE, PCFS$USER, NETBIOS$ACCESS $ MC AUTHORIZE UAF> SHOW /IDENTIFIER PCFS$READ -- returns a value, for example 1000A UAF> SHOW /IDENTIFIER PCFS$UPDATE UAF> SHOW /IDENTIFIER NETBIOS$ACCESS UAF> SHOW /IDENTIFIER PCFS$USER In each instance note the value returned. UAF> Exit
12-7

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Shutdown the Standby BAP and reboot. Enter on the Operator console: $ @SYS$SYSTEM:SHUTDOWN The following messages and prompts will be displayed (example responses are shown enclosed in <> )
SHUTDOWN -- Perform an Orderly System Shutdown on node MARS Do you really want to shutdown node MARS [NO]? <Y> How many minutes until final shutdown [0]: <> Reason for shutdown [Standalone]: <> Do you want to spin down the disk volumes [NO]? <> Do you want to invoke the site-specific shutdown procedure [YES]? <> Should an automatic system reboot be performed [NO]? <Y> When will the system be rebooted [shortly via automatic reboot]: <> Shutdown options (enter as a comma-separated list): REBOOT_CHECK Check existence of basic system files SAVE_FEEDBACK Save AUTOGEN feedback information from this boot Shutdown options [NONE]: <REB,SAV> %SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check... %SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed %SHUTDOWN-I-SAVEFEED, Saving AUTOGENs feedback information from this boot... %SHUTDOWN-I-SAVEOK, Feedback info. saved in SYS$SYSTEM:AGEN$FEEDBACK.DAT %SHUTDOWN-I-BRDOPROFF, Broadcasts to the operator window have been disabled. %SHUTDOWN-I-OPERATOR, This terminal is now an operators console. %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:00.47 %%%%%%%%%%% Operator _MARS$RTA1: has been enabled, username SYSTEM %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:00.48 %%%%%%%%%%% Operator status for operator _MARS$RTA1: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled. %SET-I-INTSET, login interactive limit = 0, current interactive value = 1 %SHUTDOWN-I-SHUTNET, The DECnet network will now be shut down. %SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped. %SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked. SHUTDOWN message on MARS from user SYSTEM at _MARS$RTA1: 13:32:02 MARS will shut down in 0 minutes; back up shortly via automatic reboot. Please log off node MARS. Standalone %SHUTDOWN-I-STOPUSER, All user processes will now be stopped. 1 terminal has been notified on MARS. %SHUTDOWN-I-REMOVE, All installed images will now be removed. %SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted. %SHUTDOWN-I-STOPAUDIT, stopping the audit server %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:06.31 %%%%%%%%%%% Message from user SYSTEM on MARS _MARS$RTA1:, MARS shutdown was requested by the operator. %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:06.86 %%%%%%%%%%% Logfile was closed by operator _MARS$RTA1: Logfile was MARS::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;12 %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:07.43 %%%%%%%%%%% Operator _MARS$RTA1: has been disabled, username SYSTEM

Once the system has rebooted, login as (SYSTEM) and ensure the PCFS_SERVER is running (SHOW SYSTEM). Add the PC nodes as file services to the Pathworks database on this BAP:
12-8

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

$ ADMIN /PCSA > MENU > SERVICE OPTIONS > LIST SERVICES > LIST Registered File Services > LIST Authorised File and Printer Services Service names for the PCs will not currently appear and should be added to these lists. So exit menu mode and then create directory services for the File server running on VMS. Directories are created under VMS to which the PC clients are granted full file access: > ADD Service / directory / root=(Shadow_Disk):[HNSFXA] rms=(s:rwed,o:rwed,g:rwed,w:rwed) HNSFXA > ADD Service / directory / root=(Shadow_Disk):[HNSFXB] rms=(s:rwed,o:rwed,g:rwed,w:rwed) HNSFXB In addition ensure that these new services are authorised as follows : > Menu > Service Options > Grant Group Access > HNSFXA > PUBLIC > Read/Write/Create > Grant Group Access > HNSFXB > PUBLIC > Read/Write/Create Now ensure that the services have been correctly added and authorised : > List Services > List Registered File Services > List Authorised File and Printer Services It is then necessary to install Pathworks on the Master BAP. Logon to the Master BAP, as SYSTEM.
12-9

/ /

type=common type=common

/ /

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

$ Mount /system DKA400: VAXBINJAN945 $ SET DEF SYS$UPDATE $ @VMSINSTAL PCSAU1042 DKA400:[PCSAU1042.KIT] OPTIONS N $ @SYS$STARTUP PCSA$CONFIG Add the line @SYS$STARTUP:PCFS_STARTUP to SYS$MANAGER:SYSTARTUP_ V5.COM, after DECNET startup procedure. Then Reboot the system. Enter: $ @SYS$SYSTEM:SHUTDOWN from the Operator console. The following messages and prompts will be displayed (example responses are shown enclosed in <> )
SHUTDOWN -- Perform an Orderly System Shutdown on node MARS Do you really want to shutdown node MARS [NO]? <Y> How many minutes until final shutdown [0]: <> Reason for shutdown [Standalone]: <> Do you want to spin down the disk volumes [NO]? <> Do you want to invoke the site-specific shutdown procedure [YES]? <> Should an automatic system reboot be performed [NO]? <Y> When will the system be rebooted [shortly via automatic reboot]: <> Shutdown options (enter as a comma-separated list): REBOOT_CHECK Check existence of basic system files SAVE_FEEDBACK Save AUTOGEN feedback information from this boot Shutdown options [NONE]: <REB,SAV> %SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check... %SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed %SHUTDOWN-I-SAVEFEED, Saving AUTOGENs feedback information from this boot... %SHUTDOWN-I-SAVEOK, Feedback info. saved in SYS$SYSTEM:AGEN$FEEDBACK.DAT %SHUTDOWN-I-BRDOPROFF, Broadcasts to the operator window have been disabled. %SHUTDOWN-I-OPERATOR, This terminal is now an operators console. %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:00.47 %%%%%%%%%%% Operator _MARS$RTA1: has been enabled, username SYSTEM %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:00.48 %%%%%%%%%%% Operator status for operator _MARS$RTA1: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled. %SET-I-INTSET, login interactive limit = 0, current interactive value = 1 %SHUTDOWN-I-SHUTNET, The DECnet network will now be shut down. %SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped. %SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked. SHUTDOWN message on MARS from user SYSTEM at _MARS$RTA1: 13:32:02 MARS will shut down in 0 minutes; back up shortly via automatic reboot. Please log off node MARS. Standalone %SHUTDOWN-I-STOPUSER, All user processes will now be stopped. 1 terminal has been notified on MARS. %SHUTDOWN-I-REMOVE, All installed images will now be removed. %SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted. %SHUTDOWN-I-STOPAUDIT, stopping the audit server %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:06.31 %%%%%%%%%%% Message from user SYSTEM on MARS _MARS$RTA1:, MARS shutdown was requested by the operator.

12-10

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

%%%%%%%%%%% OPCOM 12-MAR-1992 13:32:06.86 %%%%%%%%%%% Logfile was closed by operator _MARS$RTA1: Logfile was MARS::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;12 %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:07.43 %%%%%%%%%%% Operator _MARS$RTA1: has been disabled, username SYSTEM

Note, during the installation on this BAP the directories are not required to be created, since they exist on the Shadow disk. Ensure that the rights identifier values match between the Master and Standby BAPs. If they are different, then the following actions must be performed: $ SET DEF SYS$SYSTEM $ MC AUTHORIZE UAF> Modify /Identifier PCFS$READ /Value=identifier:%X1000A NOTE: This is an example of the value. Ensure that any new RID values selected are not already in use by another identifier. Using the show command for example: UAF> Show /Identifier /Value=identifier:%X1000B Add PC node identifiers and names to the NCP database. For example assuming node names of HNSFXA and HNSFXB with node addresses of 43.180 and 43.181 respectively : $ MC NCP NCP> DEFINE NODE 43.180 NAME HNSFXA NCP> DEFINE NODE 43.181 NAME HNSFXB NCP> EXIT Reboot the system. Enter: $ @SYS$SYSTEM:SHUTDOWN from the Operator console. The following messages and prompts will be displayed (example responses are shown enclosed in <> )
SHUTDOWN -- Perform an Orderly System Shutdown on node MARS Do you really want to shutdown node MARS [NO]? <Y> How many minutes until final shutdown [0]: <> Reason for shutdown [Standalone]: <> Do you want to spin down the disk volumes [NO]? <> Do you want to invoke the site-specific shutdown procedure [YES]? <> Should an automatic system reboot be performed [NO]? <Y> When will the system be rebooted [shortly via automatic reboot]: <> Shutdown options (enter as a comma-separated list): REBOOT_CHECK Check existence of basic system files SAVE_FEEDBACK Save AUTOGEN feedback information from this boot Shutdown options [NONE]: <REB,SAV> %SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check... %SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed %SHUTDOWN-I-SAVEFEED, Saving AUTOGENs feedback information from this boot... %SHUTDOWN-I-SAVEOK, Feedback info. saved in SYS$SYSTEM:AGEN$FEEDBACK.DAT

12-11

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

%SHUTDOWN-I-BRDOPROFF, Broadcasts to the operator window have been disabled. %SHUTDOWN-I-OPERATOR, This terminal is now an operators console. %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:00.47 %%%%%%%%%%% Operator _MARS$RTA1: has been enabled, username SYSTEM %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:00.48 %%%%%%%%%%% Operator status for operator _MARS$RTA1: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled. %SET-I-INTSET, login interactive limit = 0, current interactive value = 1 %SHUTDOWN-I-SHUTNET, The DECnet network will now be shut down. %SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped. %SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked. SHUTDOWN message on MARS from user SYSTEM at _MARS$RTA1: 13:32:02 MARS will shut down in 0 minutes; back up shortly via automatic reboot. Please log off node MARS. Standalone %SHUTDOWN-I-STOPUSER, All user processes will now be stopped. 1 terminal has been notified on MARS. %SHUTDOWN-I-REMOVE, All installed images will now be removed. %SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted. %SHUTDOWN-I-STOPAUDIT, stopping the audit server %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:06.31 %%%%%%%%%%% Message from user SYSTEM on MARS _MARS$RTA1:, MARS shutdown was requested by the operator. %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:06.86 %%%%%%%%%%% Logfile was closed by operator _MARS$RTA1: Logfile was MARS::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;12 %%%%%%%%%%% OPCOM 12-MAR-1992 13:32:07.43 %%%%%%%%%%% Operator _MARS$RTA1: has been disabled, username SYSTEM

12.1.2 Database Tables Required Two database tables are required, LESFAX_ROUTE and LESFAX_PC. Example of LESFAX_ROUTE table contents:
Route_Number 18 Route_Name FAX_ROUTE1 Desired_State IN_SERVICE Fax_Quality HIGH Banner_Name DEF_BANR

Example of LESFAX_PC table contents:


Route_Number 18 18 18 PC_ID PC_A PC_B PC_C Node_Name HNSFXA HNSFXB HNSFXC Desired_State IN_SERVICE IN_SERVICE IN_SERVICE

12.1.3 Install Etherworks card The following sections will detail the procedure for installing the Etherworks card. This will normally be a DEC Etherworks 3 Turbo card, also known as EWRK3, with a product number of DE205. However instructions are also included for the installation of the old style Dec Etherworks 2 card, with a product number of DE202. Only one of these Etherworks cards will be installed at a given site so the only one of the following will be applicable.

12-12

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

12.1.3.1 Installing Etherworks 3 Install Digital Etherworks 3 card (DE205) into the third (i.e. Middle) option slot of the FAX PC. Configure Etherworks 3 card to use IRQ 11 by running NICSETUP from the Etherworks 3 installation disk. This diskette containing along with instructions are provided with the Digital Etherworks 3 card. Default the other parameters (Base I/O address, Memory Base address and Memory Mode). 12.1.3.2 Installing Etherworks 2 Configure the Digital Etherworks 2 card (DE202) to use IRQ 11 by setting the correct IRQ jumper on the card. Install the Digital Etherworks 2 card (DE202) into the third (i.e. Middle) option slot of the Fax PC. 12.1.4 Install Modem cards Check which modem type is installed in each slot. The exact make and model depends on the compatability with the local PSTN connection. The following information relates to the modems supplied by HNS. 12.1.4.1 Notes For All Modem Types The Fax PC has five ISA expansion slots running horizontally at the rear of the PC chassis. From bottom to top, we will number these 1 to 5. Slot 3 is used for the Etherworks card. The remaining slots are used for modem cards. The standard configuration is that the COM port increases with the slot number, and the IRQ is set as follows :Slot 5 Slot 4 Slot 3 Slot 2 Slot 1 Modem configured as COM4 IRQ 2 (shown as 9 in CONFIG.SYS) Modem configured as COM3 IRQ 5 Etherworks card configured to use IRQ11. Modem configured as COM2 IRQ 3 Modem configured as COM1 IRQ 4

In addition use of an Interrupt Request Level of 9 (set as Level 2 on the board) may not work with some modem cards. So if a device initialization error is reported by Zetafax on startup for COM port 4, then try using IRQ7 (which is the LPT1 parallel port 1) for COM port 4. To minimise problems, the lower COM numbers (and hence slots) should be used in preference to higher COM numbers. For example if 3 modems were to be installed, then they would be configured as 1,2 & 3 in preference to 1,3 & 4. Test out the individual modems using PM Terminal/Softerm (in the Productivity folder), to ensure they are correctly configured. Youll need to ensure that Zetafax is not running in order to do this. Typing ATE1 <CR> AT <CR> should produce some sort of response from each modem.

12-13

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

12.1.5 Hayes modem commands This section summarizes the commands which are normally available on a modem : ++++ A/ AT ATA AT&Cn AT&C0 AT&C1 ATDx ATDTx ATDPx AT&Dn AT&D0 AT&D1 ATEn ATE0 ATE1 AT&F ATHn ATH0 ATH1 ATIn ATMn ATM0 ATM1 ATM2 ATM3 ATO Escape data mode, enter command mode. (Doesnt require AT prefix or <CR>). Repeat the last command. (Doesnt require AT prefix or <CR>). Attention code preceding all commands. Answer call, even if no ring is present. Data Carrier Detect control. Forces Carrier Detect on. Allows Carrier Detect to act normally. Dial from keyboard (x = telephone number). Where x consists of digits and dial modifier characters which include P and T. Normally used as a Dial modifier character for Touch Tone dialling. Normally used as a Dial modifier character for Pulse dialling. Data Terminal Ready control. Means DTR is ignored. Normally means go to command start on DTR drop. Echo select. Means that the modem does not echo typed commands. Means that the modem does echo typed commands. Reinitialize memory or restore factory default settings from ROM and DIP switch settings. On/Off hook. Means hang up (go on hook). means go off hook. Modem Identification. Loudspeaker control. Means turn speaker off. Means turn speaker is on during dialling and call set-up. Means speaker is always on. Means speaker is only on during call set-up. Exit command mode and return to data mode. Often O0 is used to mean immediate return to data mode and O1 means return to data mode and initiate a retrain. Data Set Ready control. Means DSR is always on. Means DSR follows the RS232C specification. Verbose/Numeric response codes. Means the modem will send numeric responses. Means that the modem will send verbose responses.

AT&Sn ATS0 ATS1 ATVn ATV0 ATV1

12-14

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

12.1.6 Taking a Fax Modem Card Out Of Service The following steps should be taken on a Fax PC in order to deinstall a Fax modem card : 1. Double left click on the Zetafax icon. 2. If Zetafax is still running then double left click on Stop Zetafax Server. 3. Double left click on Zetafax Install. 4. Change this Install window to full screen size by a left click on the small box at the top right of the menu bar. 5. Select the Configure Devices option. 6. Select the Modify a device option. 7. Select the card which is to be taken out of service. Note the attributes of this card, then use the Escape key to exit this option. 8. Select the Delete device option. 9. Select the card to be taken out of service. 10. Then use exit to return through the option levels and exit the installation program. Close the Zetafax Install window. 11. Note that if a modem card is to be physically removed, then it is advisable (in accordance with standard PC practice) to ensure that contiguous COM ports are in use. For example if the card set as COM port 2 is removed and ports 3 and 4 are occupied, then the card set as port COM4 should be set to occupy COM2. 12. Then shutdown the PC. The suspect modem card may now be removed. 13. Reboot the Fax PC, and from the Zetafax Monitor window ensure that the deinstalled modem card is no longer referenced during Zetafax installation. 12.1.7 Install Operating System The Operating System used for Fax PCs is IBMs OS/2. Different versions of OS/2 are installed on sites depending on when the installation was performed. Whichever version of OS/2 is to be installed, follow the installation notes in the manual provided with the software. Reference 5 or Reference 6. The most recent version to be installed is OS/2 Warp (OS/2 Version 3) and the following comments relate particularly to this version. As the Zetafax software is a Microsoft Windows based product it is necessary to ensure that Windows programs are supported by OS/2. To do this OS/2 must be installed on top of Microsoft Windows. This means that, as part of the OS/2 installation, you will be prompted for the original Windows installation diskettes. If Windows was pre-installed on the PC by the manufacturer there may not have been a set of Windows installation diskettes supplied. In this case the PC manufacturer should have supplied a mechanism for the user to generate a set of Windows backup diskettes. This
12-15

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

utility is normally supplied as part of Windows. For example, when entering Windows on a Digital PC the user is confronted with a Digital Setup screen displaying various installation options before entering Windows. One of these options is to generate a set of Windows backup diskettes. Follow the PCs instructions to generate these diskettes. Once a set of Windows diskettes are available, start the installation as shown in the OS/2 User Guide, selecting the Easy Installation. On completion of the installation check that Windows is fully supported within OS/2. Select OS/2 System by double left clicking on it. Select Command Prompts. Select WIN-OS/2 Full Screen. If this produces a full Windows session starting with the Windows Program Manager then the OS/2 installation has been a success and you can proceed to the next section. If not, then it is necessary to selectively deinstall DOS and Windows and re-install them. From the OS/2 System window select System Setup. Select Selective Uninstall. Select OS/2 DOS and WIN-OS/2 Support. Select Uninstall. Similarly, use Selective Install to re-install DOS and Windows. Perform the above check to ensure that Windows is now fully supported within OS/2. 12.1.8 Install NTS/2 LAPS Software For further details see Reference [6]. During this part of the installation the NTS/2 LAN adapters and Protocol Support and DEMCA/DEPCA diskettes are required. Select OS/2 System icon. Select Command Prompts. Select OS/2 window. Maximize the window by clicking on the box at the top right corner of the window. Insert the NTS/2 LAN Adapter and Protocol Support diskette. Change drive and directory to the root directory of the diskette drive. [C:\] A: Invoke the LAPS program : [A:\] LAPS
12-16

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

This creates a window with an IBM logo for LAPS installation. Click on the Install option. LAPS prompts for a drive to install on, select drive C then click on OK. Files are then transferred from diskette to the target drive C. LAPS tells you that installation is complete. LAPS must now be configured before it can be used. Click on OK. The original LAPS screen, with the IBM logo, is displayed. Click on Configure. Select the configuration option Configure LAN Transports, then click on Continue. A window titled Configure Workstation should be displayed. A Network Adapter and two Protocols are to be added. These will appear in the Current Configuration box, which should initially be empty. In the Network Adapters box, scroll down to the option IBM PS/2 Adapter for Ethernet Networks. Highlight this option by clicking on it, then click on Add. In the Protocols box, scroll down to the option IBM IEEE 802-2. Highlight this option by clicking on it, then click on Add. In the Protocols box, scroll down to the option IBM OS/2 NetBIOS. Highlight this option by clicking on it, then click on Add. The adaptor and two protocols selected should now appear in the Current Configuration box. If this is correct click on OK. The IBM logo window will be displayed. Click on Exit to end the LAPS installation. The program will update the CONFIG.SYS file on drive C. Click on Continue to allow this. Wait until the confirmation indicating the successful update of CONFIG.SYS then click on OK. There is additional information displayed by LAPS. This should be read before clicking on Exit. At this stage Do NOT reboot (or shutdown) the machine. The adaptor must be reconfigured to be the one supplied on diskette with the Etherworks card. 12.1.9 Install Etherworks driver The following sections detail the procedure for installing the software associated with the Etherworks card. Normally a DEC Etherworks 3 Turbo card will be in use. However, instructions are also included for the installation of software associated with the older style DEC Etherworks 2 card. Only one of these Etherworks cards will be installed at a given site so the following two sections are mutually exclusive.

12-17

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

12.1.9.1 Installing Etherworks 3 For this part of the installation the DEC Etherworks 3 Drivers diskette is required. Invoke the LAPS program from the hard disk: [C:] C:\IBMCOM\LAPS This creates the window with an IBM logo for LAPS installation. Click on the Install option to install additional network drivers. Insert the Etherworks 3 Drivers diskette into drive A: Enter the source for the network information file as A:\MSLANMAN.OS2\DRIVERS\NIF Enter the source for the driver file as A:\MSLANMAN.OS2 LAPS tells you that installation is complete. LAPS must now be configured before it can be used. Click on OK. The original LAPS screen with the IBM logo is displayed. Click on Configure. Select the configuration option Configure LAN Transports, then click on Continue. A window titled Configure Workstation should be displayed. The Current Configuration box should initially contain the protocols and adapters previously selected. Before the DEC Etherworks 3 adapter is added it is necessary to remove the current protocols and adapters. Remove each protocol from the Current Configuration by clicking on it to highlight it and clicking on Remove. Remove the adapter from the Current Configuration by clicking on it to highlight it and clicking on Remove. A new Network Adapter and two Protocols are to be added to the Current Configuration box, which should now be empty. In the Network Adapters box, scroll down to the option DEC Etherworks Adapter. Highlight this option by clicking on it, then click on Add. In the Protocols box, scroll down to the option IBM IEEE 802-2. Highlight this option by clicking on it, then click on Add. In the Protocols box, scroll down to the option IBM OS/2 NetBIOS. Highlight this option by clicking on it, then click on Add. The adaptor and two protocols selected should now appear in the Current Configuration box. If this is correct, click on OK. The IBM logo window will be displayed. Click on Exit, to end the LAPS installation.

12-18

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

The program will update the CONFIG.SYS file on drive C. Click on Continue to allow this. Wait until the confirmation indicating the successful update of CONFIG.SYS, then click on OK. There is additional information displayed by LAPS. This should be read before clicking on Exit. Remove the diskette from drive A: To use the OS/2 System editor, select OS/2 System by double clicking on it, then select Productivity then select OS/2 System Editor. A simpler way is to call the editor from the command line of an OS/2 window, e.g. [C:\] e FILENAME.EXT Using the OS/2 System Editor modify the IBM LAN Requester PROTOCOL.INI file C:\IBMCOM\PROTOCOL.INI to use interrupt 11 instead of 5. In the section headed [EWRK3_nif] change the following line: INTERRUPT = 5 to: INTERRUPT = 11 Save this file. On saving if the editor asks for the specific file type, always select plain text. Shutdown the system and reboot. To do this, use right click anywhere on the screen not currently occupied by an icon or window. A pop-up menu is produced, select the Shutdown option and click on OK for all the pop-up screens that are produced. Press Control-Alt-Delete when ask to do so. If a shutdown request does not succeed in closing down OS/2 then it may be necessary to close any open windows manually and then to reboot the PC using Control-Alt-Delete. Appendix B contains examples of C:\CONFIG.SYS, C:\PCSAOS2\DEV\PROTOCOL.INI and C:\IBMCOM\PROTOCOL.INI for Etherworks 3. 12.1.9.2 Installing Etherworks 2 Load up the OS/2 driver and the IBM LAN Requester Vn 3.0 NIF file for Etherworks 2 from the DEMCA/DEPCA Install V1.3 DD disk. Return to the OS/2 window. Change directory as follows : [C:\] cd A:\MSLANMAN.OS2\DRIVERS\ETHERNET\DEPCA [A:\MSLANMAN.OS2\DRIVERS\ETHERNET\DEPCA] copy DEPCA.OS2 C:\IBMCOM\MA CS\DEPCA.OS2 Change directory as follows : [A:\MSLANMAN.OS2\DRIVERS\ETHERNET\DEPCA] cd A:\MSLANMAN.OS2\DRIVERS\N
12-19

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

IF [A:\MSLANMAN.OS2\DRIVERS\NIF] copy DEPCA.NIF C:\IBMCOM\MACS\DEPCA.NIF Change directory back to the C: drive as follows : [A:\MSLANMAN.OS2\DRIVERS\NIF] c: Remove the diskette from drive A: Using the OS/2 System Editor, edit the C:\CONFIG.SYS file. Change the following line: DEVICE = C:\IBMCOM\MACS\MACETH.OS2 to: DEVICE = C:\IBMCOM\MACS\DEPCA.OS2 Using the OS/2 System Editor, modify the IBM LAN Requester C:\IBMCOM\PROTOCOL.INI to use a DEPCA binding instead of a MACETH binding. In the [IBMLXCFG] Section, add: DEPCA_NIF = DEPCA.nif Change every instance of BINDINGS = MACETH_nif to BINDINGS = DEPCA. Add the following to the end of the file: [DEPCA_nif] Drivername = DEPCA$ ;This comment line is mandatory. Save the file. Shutdown the system and reboot. To do this, use right click anywhere on the screen not currently occupied by an icon or window. A pop-up menu is produced, select the Shutdown option and click on OK for all the pop-up screens that are produced. Press Control-Alt-Delete when ask to do so. Appendix B contains examples of C:\CONFIG.SYS, C:\PCSAOS2\DEV\PROTOCOL.INI and C:\IBMCOM\PROTOCOL.INI for Etherworks 2. 12.1.10 Installing LAN Server/Requester Further details can be obtained from page 3-14 of Reference [7]. For this part of the installation the LAN server install diskette 1 and the OS/2 Requester diskettes are required. Insert Server Install Diskette 1 into drive A:
12-20

file

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

Set up an OS/2 window, as described in section 12.1.8. Run the LAN Installation software from drive A: [C:\] A:LANINST The installation program copies some files to the C: drive then displays a Server Installation/Configuration window with the IBM logo. Click on OK. Click on Advanced. Select the option Install or Configure this workstation, then click on OK. The type of server required is a Domain controller. Select this option, then click on OK. Select the option Install or Remove a component, then click on OK. No changes are required. Choose the option Configure a component,then click on OK. Select Server, then click on Configure. Enter the Server and Domain names. These should be the PC node name followed by _S and _D, respectively. Click on OK. Select the option to start the server automatically on workstation startup, then click on OK. In the Server Services window, ensure the AUTOSTART settings are OFF for each service, except NETLOGON. Click on OK. (If the LAN Server/Requester has previously been installed on this PC then a Reinitialize Domain Control Database window will appear and a decision is required on whether the domain control database should be reinitialised). In the Configure window, click on OK. Select Apply the changes and click on OK. Then insert diskettes as requested. Ensure the three IBM OS/2 LAN Server V3.0 LAN Requester Install Diskettes are used rather than the DOS LAN Requester diskettes which are also supplied. Click on OK in the File Backup window. Click on OK in the window detailing the User ID and Password. LANINST now indicates the successful completion of the installation and configuration procedure. The system must be shutdown, in the normal manner, having read the instructions. Remove any diskette in the A: drive prior to shutdown.
12-21

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

On startup the command file STARTUP.CMD is automatically executed as are the LAN requester and LAN server processes. NOTE: If Ethernet is not connected the server will not start. 12.1.11 LAN Requestor commands Useful LAN Requester commands are : net help - List the available net commands. net log [on|off] - Display whether logging is ON or OFF and the location of the log file. Logging can also be turned ON or OFF using this command. net start - List the Requester services which have started. net statistics requester [/clear] - Display statistics for the LAN Requester function. The statistics can be reset using this command. net statistics server [/clear] - Display statistics for the LAN Server function. The statistics can be reset using this command. net stop requester - Stop the LAN Requester (and LAN Server) net use - List the Requester connections. net who - List who is logged into the domain. 12.1.12 Install Pathworks on PCs The following sections detail the procedure for installing the Pathworks software. The latest version in use is Pathworks version 5.0, however instructions are also included for the installation of Pathworks version 2.0 which is currently in use at some sites. Only one version will be installed at a given site so the following two sections are mutually exclusive. 12.1.12.1 Installing Pathworks Version 5.0 Using the Pathworks for OS/2 Installation and Configuration Guide which accompanies the software. See Reference [8]. Create an OS/2 window as described in section 12.1.8. Insert the diskette PWRKS 5.0 for OS/2 Disk 1 into the A: drive. Run PWINST from the A: drive. [C:\] A:PWINST At the Install window enter the source directory as A:\ and destination directory as C:\PATHWRKS. Follow the prompts until the Configure License window is displayed. Select Combined Client Server (CCS) leaving all other fields as defaults before clicking on OK. At the Configure Local DECnet Node window enter the PCs node name and node address, for example node name HNSFXA, node address 43.180. This will be supplied by
12-22

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

HNS Ltd. Select Ethernet line type, then click on OK. The DLLMAC Driver is then installed using the previously installed LAPS software. The LAPS screen, with the IBM logo, is displayed. Click on Configure. Select the configuration option Configure LAN Transports, then click on Continue. A window titled Configure Workstation should be displayed. In the Protocols box, scroll down to the option Digital Datalink to MAC Interface. Highlight this option by clicking on it, then click on Add. This protocol should now appear in the Current Configuration box. If this is correct click on OK. The IBM logo window will be displayed. Click on Exit to end the LAPS installation. The program will update the CONFIG.SYS file on drive C. Click on Continue to allow this. Wait until the confirmation indicating the successful update of CONFIG.SYS then click on OK. There is additional information displayed by LAPS. This should be read before clicking on Exit. You will now be returned to the Pathworks installation. At the Configure SETHOST window select Multinational Character Set (MCS) and DEC Multinational before clicking on OK. At the Configure Known DECnet Nodes window add the node name, node address and select MS-NET for BOTH BAPs before clicking OK. The Pathworks installation is now complete. Remove any diskettes from the A: drive, shutdown and reboot the PC. When the PC has restarted select the Pathworks folder. Select Install and Configure. Pull down the Installation menu and select File Fixup. Select OK and exit Pathworks Installation and Configuration. Edit C:\STARTUP.CMD using the OS/2 System editor: After the NET START SERVER line add: LOGON USERID /P:PASSWORD Save the modified STARTUP.CMD file.

12-23

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

12.1.12.2 Installing Pathworks Version 2.0 Create an OS/2 window as described in section 12.1.8. [C:\] copy C:\CONFIG.SYS C:\CONFIG.LS Insert the diskette PWRKS for OS/2 V2.0 1/11 HD into the A: drive. See also p.2-1, Using NETSETUP of Reference [9]. Then run NETSETUP from the A: drive ignoring the warning about incompatibilities. [C:\] A:NETSETUP Press Enter to continue. A page is displayed describing two modes of setting up Pathworks. The one required is CONFIGURATION mode. Press Enter and then press F10 to toggle mode to Configuration. Select one transport to be DECnet. LAN manager needs to be NOT Installed. Local Area Transport should be Started. Local Area Disk should be NOT Installed. Click on Next. Adapter - Ethernet, NDIS drive type - Digital Etherworks, NDIS adaptor Digital Etherworks adaptor. Click on Next. Enter the DECnet node name and node address, decided upon previously. Click on Next Network virtual disk - Not started. Network virtual printer - Not started. Job spawner - Started. The Remainder of the entries in this table should be set to Spawned. Click on Next. LAT Setup. Click on Next Enter the node names and DECnet addresses of the two BAPs. LAT should be Yes and default user name should be blank in both cases. Add the PC itself to the database as, for example: CVAXA 43.3 YES <blank>
12-24

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

CVAXB 43.4 YES <blank> HNSFXA 43.180 NO <blank> Click on Next - Mail setup. Click on Next - Terminal setup. Click on Next Set the IVP to Yes and fill in the PC node name and DECnet address fields which are then displayed. Click on Next - Software installation Click on Next - Begin process. Press Enter. Then insert the Pathworks for OS/2 diskettes as requested (only disks 1,2,3 and 11 are required). At the request to read README.TXT - type N. A message is then displayed to reboot the PC. Press Enter to return to the desktop. DO NOT REBOOT. [C:\] copy C:\CONFIG.SYS to C:\CONFIG.PW [C:\] copy C:\CONFIG.LS to C:\CONFIG.SYS Edit C:\CONFIG.SYS using the OS/2 System editor. The PATH lines specified below must include the entries against them: At the beginning of this line: LIBPATH PATH DPATH C:PCSAOS2\PBIN; \ C:PCSAOS2\CS; Insert the following three lines at the beginning of CONFIG.SYS: Set DECNET=C:\PCSAOS2\DECNET Set DNETPATH=C:\PCSAOS2\DECNET Set DNETMAIL=C:\PCSAOS2\MAIL Before the line IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN/N insert the following: DEVICE=C:\PCSAOS2\DEV\DLLMAC.SYS DEVICE=C:\PCSAOS2\DEV\DNP.SYS /NAME:xxxxxx /ADDR:a.n DEVICE=C:\PCSAOS2\DEV\IOCBDRV.SYS
12-25

Add: C:PCSAOS2\DLL; C:PCSAOS2\PBIN; C:PCSAOS2\DECNET; \

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Replacing xxxxxx with the PCs DECnet node name and a.n with its DECnet address. Save the edited CONFIG.SYS file. If the Etherworks 2 card (DEPCA) has been installed then the CONFIG.SYS and PROTOCOL.INI files should be modified as follows : [C:\] COPY C:\IBMCOM\MACS\DEPCA.OS2 C:\PCSAOS2\DEV\DEPCA.OS2 Modify C:CONFIG.SYS as follows. Change: DEVICE=C:\IBMCOM\MACS\DEPCA.OS2 to DEVICE=C:\PCSAOS2\DEV\DEPCA.OS2 Save the modified CONFIG.SYS file. Edit the C:\IBMCOM\PROTOCOL.INI file. Insert the following immediately after the [IBMLXCFG] section:
<blank line> [DATALINK] <blank line> DRIVERNAME BINDINGS RC_BUFFERS RL_BUFFERS TX_BUFFERS <blank line>

= = = = =

DLL$DEC DEPCA 32 43 16

And insert "DATALINK = DATALINK.nif at the head of the list in the [IBMLXCFG] section. NOTE: All the above statements should be in capitals. Save the modified PROTOCOL.INI file. Ensure that the Pathworks PROTOCOL.INI file C:\PCSAOS2\DEV\PROTOCOL.INI has been modified to use an DEPCA binding instead of a MACETH binding:
[Protocol Manager] DriverName = PROTMAN$ ... [DATALINK] Drivername Bindings ... ; DEPCA and Etherworks Adapters. [DEPCA] DriverName = DEPCA$ = DLL$DEC = DEPCA

Appendix B contains examples of C:\CONFIG.SYS, C:\PCSAOS2\DEV\PROTOCOL.INI and C:\IBMCOM\PROTOCOL.INI for Etherworks 2.


12-26

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

Alternatively, If the Etherworks 3 card (EWRK3) has been installed then the CONFIG.SYS and PROTOCOL.INI files should be modified as follows : C:\ COPY C:\IBMCOM\MACS\EWRK3.OS2 C:\PCSAOS2\DEV\EWRK3.OS2 Modify C:CONFIG.SYS as follows. Change: DEVICE=C:\IBMCOM\MACS\EWRK3.OS2 to DEVICE=C:\PCSAOS2\DEV\EWRK3.OS2 Save the modified CONFIG.SYS file. Edit the C:\IBMCOM\PROTOCOL.INI file. Insert the following immediately after the [IBMLXCFG] section:
<blank line> [DATALINK] <blank line> DRIVERNAME BINDINGS RC_BUFFERS RL_BUFFERS TX_BUFFERS <blank line>

= = = = =

DLL$DEC EWRK3 32 43 16

And insert "DATALINK = DATALINK.nif at the head of the list in the [IBMLXCFG] section. NOTE: All statements above should be in the specified case. Save the modified PROTOCOL.INI file. Modify the Pathworks PROTOCOL.INI file C:\PCSAOS2\DEV\PROTOCOL.INI to use an EWRK3 binding instead of a DEPCA binding:
[Protocol Manager] DriverName = PROTMAN$ ... [DATALINK] Name = DLL$DEC Binding = EWRK3 ... ; Etherworks 3 [EWRK3] DriverName IOAddress RAMAddress MemoryMode Interrupt Diagnostic card. = = = = = = EWRK3$ 0x300 0xD000 2 11 1

NOTE: The remaining updates are required regardless of the Etherworks card installed.
12-27

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Edit the C:\IBMLAN\IBMLAN.INI file. Insert the following into the [NETWORKS] section:
net1 = NETBEUI$,0,LM10,32,50,14 net2 = DEC$NBE,0

Modify the line wrknets = in the [REQUESTER] section to:


wrknets = NET1,NET2

Modify the line srvnets = in the [SERVER] section to:


srvnets = NET1,NET2

Save the modified IBMLAN.INI file. Edit the file C:\STARTUP.CMD. Move the call C:\PCSAOS2\PCSAOS2.CMD to before the NET START SERVER line. Save the modified C:\STARTUP.CMD file. Edit C:\PCSAOS2\PCSAOS2.CMD. Remove NETBIND line and if errorlevel 1 goto Failed from the :INITIATE section. Save the modified C:\PCSAOS2\PCSAOS2.CMD file. Return to the OS/2 window. Insert the diskette PWKS OS/2 V2.0B UPDATE 1/1 and install the update. [C:\] A:INSTALL C Remove the diskette. Then shutdown the machine and reboot. Edit CONFIG.SYS. Remove /NAME:xxxxxx /ADDR:a.n from the line:
DEVICE=C:\PCSAOS2\DEV\DNP.SYS

Save the modified CONFIG.SYS file. Shutdown and Reboot again. Provided the installation is successful, the PC should reboot without any errors. A basic test can be performed to check LAN requester, by entering the following commands at the DOS prompt: > NET USE > NET WHO This should show a successful status. Appendix B contains examples of C:\CONFIG.SYS, C:\PCSAOS2\DEV\PROTOCOL.INI and C:\IBMCOM\PROTOCOL.INI for Etherworks 3.

12-28

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

12.1.13 Setup Remote Remote Access PC access can be set up such that basic PC commands can be used remotely from the BAP. This can allow remote access to the PC via the BAP from HNS in cases where support or investigation is required. This communication between the BAP and the PC is performed via Pathworks, which has been previously installed to enable LESFAX to communicate with the PCs. The following steps allow remote access: Enter the Network Control Program. [C:\] NCP At the NCP prompt define access using hns as username and password. NCP> DEFINE ACCESS USER HNS PASSWORD HNS ALL Exit from NCP. NCP> EXIT It should now be possible to browse through the PCs directory structure from the BAP and to update PC files. To access the PCs from the BAP use commands of the form: $ (VAX-COMMAND PCNAME"USERNAME PASSWORD")::C: for example: $ DIR MEXFXA"HNS HNS"::C: $ TYPE MEXFXA"HNS HNS"::C:CONFIG.SYS $ TYPE MEXFXA"HNS HNS"::C:[ZETAFAX.SERVER.Z-DB]SERVER.LOG Notes: 1. The networking usernames and passwords will not expire. 2. The use of the obvious username and password (hns) will not affect customer security as access will only be possible from the customers network (i.e. BAPs). 3. The networking software must be running OK (starts automatically as part of PC startup routine) for this to work. 12.1.14 Install Zetafax Software The latest version of Zetafax to be installed is currently version 4.0+ HNS Extensions. Before installing Zetafax a registration code is required from Equisys, the authors of Zetafax. When the Zetafax software package is delivered it will contain a licence number (usually on the software box) and upgrade serial numbers for extra facilities, such as extra lines and API usage. These should be entered onto the accompanying software registration form along with the organisation name to appear on the top of the fax (usually specified by the Operator) and a contact name (Hughes Network Systems). This form should be returned to Equisys who will then generate a registration code which is required to install Zetafax cor12-29

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

rectly. The current Zetafax licence details for Mexico are: Site: Licence Number: Licence Type: Organisation Name: Contact Name: Registration Code: Site: Licence Number: Licence Type: Organisation Name: Contact Name: Registration Code: Where: License type comprises of: Users permitted to use the Zetafax software at any one time. A copy of PCFAX software counts as one user. The number of lines (i.e. modems) that can be configured in a PC. That Application Programmers Interface (API) can access Zetafax. The operating system Zetafax can run on (e.g. OS/2) Organisation Name is displayed at the top line of every fax sent. This cannot be configured by any party other than Equisys. The text for this field should be specified when applying for the license. Contact HNS to arrange a change in license if a change is required. Contact Name can be modified without a change in license. To install Zetafax, the following instructions must be followed: Select OS/2 System by double left clicking on it. Select Command Prompts. Select WIN-OS/2 Full Screen. The Windows Program Manager should now be displayed. Insert the Zetafax OS/2 Fax Server Installation disk 1, version 4.0. Pull down the File menu and select Run At the command line prompt enter A:INSTALL. Select Install Zetafax Server.
12-30

Mexico 49412257-AFAEDG-HSPGMA 5 users, 4 lines, API, OS/2 Telecomunicaciones de Mexico Hughes Network Systems EWKFWG Mexico 49412258-AFAEDG-HCQGMA 5 users, 4 lines, API, OS/2 Telecomunicaciones de Mexico Hughes Network Systems PEVTHL

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

At the server base directory prompt enter C:\ZETAFAX, then click on Continue. At the Startup Files window click on Make changes when Zetafax offers to modify the CONFIG.SYS file. Click on OK to acknowledge that the startup files have been changed. Click on OK to acknowledge that a reboot will be necessary. The installation program unpacks the files onto disk. Change disk when prompted. Information stating that it is necessary to create new folders will be displayed. Click on OK to continue. The information required to create these folders is provided in sections 12.1.14.1 and 12.1.14.2. The Zetafax Installation window will request a username, enter ?, then click on OK. Click on OK to run the Zetafax SETUP utility. At the Modify Licence Details window enter the required Licence details. These are: the licence number, the Organisation name and the Contact name (as specified on the software registration form) and the Registration Code provided by Equisys. Click on OK, then click on Close when the details are correct, At the Zetafax - User Configuration window click on New to add a new user. Enter the username as API, click on OK, enter both the network login id and the full name as API, then click on OK. Add the user HNS in the same way. Click on Close. At the Zetafax - Device Configuration window add details for all installed devices. For each device perform the following: Click New to add a new device. Pull down the Device to Add menu and select the correct device. Ensure the device number is 1-4 depending on the COM port being specified. Click on OK. Enter the description to describe what modem is being added (the device name from the previous pull down menu will suffice). Ensure the COM port specified is correct and that it matches the device number previously entered. Ensure there is no dial prefix and enter the fax number to appear on the header line as specified by the customer. This could either be the number of a local fax machine for queries by customers or more usefully perhaps to identify the PC and modem used for the delivery. For example 619 302 0333. Select DTMF tone dialling. Ensure receive incoming faxes is set to disabled and use for incoming calls is blank. Click on OK. Click No when Zetafax warns about receiving incoming faxes. After configuring all installed devices, click on Close. The installation should now be complete. Clicking on OK to acknowledge that the files have been updated will exit back to Windows. Close Windows by pulling down the File menu, selecting Exit, then clicking on OK to end
12-31

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

the session. Customers require a company graphic to appear at the top of the first Fax page. Currently this is done using either a letterhead or a logo file which must exist in the directory C:\ZETAFAX\SYSTEM\Z-LETTER or C:\ZETAFAX\SYSTEM\Z-GRAPH respectively. For the subtle differences in these methods see Reference [10]. In future all customers will use the letterhead method so, as part of this installation it is necessary to install a new default letterhead on the PC. Insert the Zetafax Upgrade and PCFax Release diskette. From an OS/2 window copy the default banner to the Zetafax letterhead directory. [C:\] COPY A:DEF_BANR.G3F C:\ZETAFAX\SYSTEM\Z-LETTER This new letterhead should be added to Zetafax using the SETUP utility. [C:\] C:\ZETAFAX\SERVER\SETUP Select Coversheets and Letterheads, then click on OK. Select Letterheads, then click on New. Enter the letterhead name DEF_BANR and a description such as Default banner for customer. Click on OK. Click on Close to exit the Coversheets and Letterheads window. Click on OK to exit the Zetafax SETUP utility. It is then necessary to upgrade from Zetafax version 4.0 to Zetafax version 4.0+ HNS Extensions. See section 12.2.2. As this installation of Zetafax is from scratch it will be necessary to create the Zetafax folders on the OS/2 Desktop. The actions required depend on the version of OS/2 being used. 12.1.14.1 Create Zetafax Folders for OS/2 Double left click on Templates icon. Within Templates folder, right click on Folder icon and select the Create Another option. Enter a folder name of Zetafax, select the DeskTop as the destination, then click on Create. Then exit the Templates folder. Double left click on Zetafax icon, to open the new folder. Double left click on Command Prompts and then double right click on OS/2 window. Select the Copy option, select the Zetafax folder, then click on Copy. Produce a total of 4 OS/2 and 2 DOS icons in this way. Right click on each new icon in the Zetafax folder in turn. Select Open Settings and set up command paths and parameters as follows :
Zetafax WorkStation Start Server Stop Server Monitor Server Workstation Setup Install OS/2 OS/2 OS/2 OS/2 DOS DOS C:\ZETAFAX\SYSTEM\ZETAFAX.EXE C:\ZETAFAX\SERVER\ZSERVER.EXE C:\ZETAFAX\SERVER\ZSERVER.EXE C:\ZETAFAX\SERVER\ZSERVER.EXE C:\ZETAFAX\SYSTEM\WKSETUP.EXE C:\ZETAFAX\SERVER\INSTALL.EXE Start Stop Monitor

12-32

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

12.1.14.2 Create Zetafax Folders for OS/2 Warp Double left click on Templates icon. Within Templates folder, right click on Folder icon and select the Create Another option. Enter a folder name of Zetafax, select the DeskTop as the destination, then click on Create. Then exit the Templates folder. Double left click on Zetafax icon, to open the new folder. Double left click on Command Prompts, then double right click on OS/2 window. Select the Copy option, select the Zetafax folder, then click on Copy. Produce a total of 2 OS/2 and 3 WIN-OS/2 icons in this way. Right click on each new icon in the Zetafax folder in turn. Select Settings and set up Command Paths and Parameters on the Programs page and Title on the General page as follows:
Title Zetafax WorkStation Start Server Stop Server Monitor Server Workstation Setup WIN-OS/2 OS/2 OS/2 OS/2 WIN-OS/2 Path and filename C:\ZETAFAX\SYSTEM\ZETAFAX.EXE C:\ZETAFAX\SERVER\ZSERVER.EXE C:\ZETAFAX\SERVER\ZSERVER.EXE C:\ZETAFAX\SERVER\ZSERVER.EXE C:\ZETAFAX\SERVER\SETUP.EXE Params Start Stop Monitor

12.1.15 Install PC Fax Software From an OS/2 window create directory C:\PCFAX [C:\] md C:\PCFAX. Insert Zetafax Upgrade and PCFax release diskette. [C:\] copy A:PCFAX.EXE C:\PCFAX Also copy the file STARTUP.CMD from the PCFax release disk [C:\] copy A:STARTUP.CMD C: To use the OS/2 System editor, select OS/2 System by double clicking on it, then select Productivity then select OS/2 System Editor. A simpler way is to call the editor from the command line of an OS/2 window, e.g. [C:\] e FILENAME.EXT Using the OS/2 System editor modify the file to refer to the correct VAX Node names. For example, given Vax nodes CVAXA and CVAXB then on a Fax PC named HNSFXA, STARTUP.CMD would include the section :
: TRY_AGAIN NET USE D: \\CVAXA\HNSFXA NET USE E: \\CVAXB\HNSFXA C:\PCFAX\PCFAX TRACE_OFF NET USE D: \\CVAXA\HNSFXA /D NET USE E: \\CVAXB\HNSFXA /D goto TRY_AGAIN

Using the OS/2 System editor edit C:CONFIG.SYS Add line AUTOFAIL=YES to the top of the file. Change line FILES to FILES=50.
12-33

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Change line BUFFERS to BUFFERS=60. On saving files if the editor asks for the specific file type, always select plain text. Add Zetafax monitor to startup folder in OS2 System folder as follows. Open the OS/2 System folder and then the Startup folder. Minimise the Startup folder. Then open the Zetafax folder and double right click on the Monitor Server icon. Select Copy from the menu and select the Startup folder for the target of the create. The Startup folder should now contain the Monitor Server icon. Shutdown and Reboot. The PCFAX code and Zetafax monitor should start up automatically on reboot. If a Login window appears during startup select Cancel. An example of C:\STARTUP.CMD for PCFAX is listed in appendix B. 12.2 Software Upgrade In order to utilize the full range of Zetafax features, including features specific to HNS, it is necessary for the latest version of Zetafax to be installed. This is currently version 4.0+ HNS Extensions. It is assumed that, as an upgrade is being performed, the current system is live. Sites with Zetafax installed prior to June 1995 will be running Zetafax Version 2.1 or earlier and will need to be upgraded. Compatibility problems will arise if the Zetafax and PCFax upgrade is not performed during the BAP software upgrade, in the following manner. Following the installation of the new software onto the first BAP but before restarting it, take Fax PC A out of service using the Fax PC Management SOC form. Upgrade Fax PC A from version 2.1 to version 4.0+ HNS Extensions by following the installation notes in sections 12.2.1, 12.2.2. and 12.2.3. Just before restarting the first upgraded BAP take Fax PC B out of service using the Fax PC Management SOC form. This will minimise the length of time that no PCs are in service. After the updated BAP is restarted and the second BAP is stopped, put Fax PC A back into service. Test the upgraded BAP and PC fully before attempting to upgrade another PC. If for some reason the installation is aborted and the previous BAP software is reinstalled any upgraded Fax PCs will NOT be compatible. Upgrade Fax PC B in the same way as Fax PC A. As soon as this is complete Fax PC B can be put back into service. If there is a spare PC, this should not be upgraded until the fully upgraded system is performing satisfactorily.

12-34

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

12.2.1 Upgrading Zetafax Version 2.1 - 4.0 Ensure that PCFax is not running. If the PCFax code is running there will be a STARTUP.CMD window. This will need to be stopped. Click on the top left corner of the STARTUP.CMD window to pull down the menu. Select Close, then click on Yes to confirm the action. Ensure the Zetafax server is not running. Select Zetafax by double left clicking on it. Select Stop Server. Select OS/2 System. Select Command Prompts. Select WIN-OS/2 Full Screen. The Windows Program Manager should now be displayed. Insert the Zetafax OS/2 Fax Server Installation disk 1, version 4.0. Pull down the File menu and select Run At the command line prompt enter A:INSTALL. Select Update selected server files. A warning may then be displayed stating that some files are already installed, click on Yes to overwrite them. At the Update Selected Server Files window select Programs and Fonts, then click on Continue. At the Startup Files window click on Make changes when Zetafax offers to modify the CONFIG.SYS file. Click on OK to acknowledge that the startup files have been changed. Click on OK to acknowledge that a reboot will be necessary. The installation program unpacks the files onto disk. Change disk when prompted. Information stating that it is necessary to create new folders will be displayed. These folders will already exist so this will not be necessary. Click on OK to continue. The installation should now be complete. Clicking on OK to acknowledge that the files have been updated will exit back to Windows. Close Windows by pulling down the File menu, selecting Exit, then clicking OK to end the session.
12-35

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customers require a company graphic to appear at the top of the first Fax page. Currently this is done using either a letterhead or a logo file which must exist in the directory C:\ZETAFAX\SYSTEM\Z-LETTER or C:\ZETAFAX\SYSTEM\Z-GRAPH respectively. For the subtle differences in these methods see Reference [10]. In future all customers will use the letterhead method so, as part of this upgrade, it is necessary to install a new default letterhead on the PC. Section 12.3 describe how letterheads are created and installed. 12.2.2 Upgrading Zetafax Version 4.0 - 4.0+ HNS Extensions Insert the Zetafax Upgrade and PCFax Release diskette in necessary. From an OS/2 window copy the Zetafax executable from the diskette to the C: drive. [C:\] COPY A:QM.EXE C:\ZETAFAX\SERVER Remove the diskette. Using the OS/2 System editor edit C:\ZETAFAX\SYSTEM\Z-DB\SETUP.INI At the bottom of the [QUEUEMAN] section, add the line:
QueueStatsFrequency: 60 LoadBalance: YES RememberDevicesTried: YES

Save the modified file C:\ZETAFAX\SYSTEM\Z-DB\SETUP.INI. If the editor asks for a specific file type, select plain text. 12.2.3 PCFAX Upgrade Insert the PCFAX release diskette if necessary. [C:\] copy A:PCFAX.EXE C:\PCFAX remove the PCFAX release diskette. Shutdown and Reboot the PC. automatically on reboot. The PCFAX code and Zetafax monitor should start

If a Login window appears during startup select Cancel. 12.3 Creating and installing the Letterhead file This section describes the procedure that should be followed in order to create a new logo or letterhead file for use with Zetafax. Choose a PC which is running both Microsoft Windows and Zetafax to generate the file. Use MicroSoft Write to generate a file for a new logo or letterhead. It may be necessary to generate the file using a graphics package (e.g. Microsoft Draw) and import it into MicroSoft Write. Start up the Zetafax Server and Zetafax Workstation by performing the follow12-36

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

ing : Double left click on the Zetafax icon. Double left click on Zetafax Server. Minimise the Zetafax Server once it is running. Double left click on Zetafax Workstation icon. On Zetafax Workstation login as HNS. From MicroSoft Write select Print Setup and choose the Zetafax printer. From MicroSoft Write print the logo file. Now Zetafax popup menus should appear. Select Preview Message (not Send Message), Click on Options and select Resolution: High and CoverSheet: (None) On the Zetafax Workstation window the new message should appear in the Out Tray. Double left click on message to examine Message Information. Note the directory containing the message. It should be of the form C:\ZETAFAX\USERS\HNS\Z-OUT. Select file view to obtain the filename which should be of the form ~SEND000.G3F The resultant file should be copied to floppy disk and then loaded onto the destination Fax PC using the following procedure, depending on whether it is to be a Logo file or a Letterhead file : Logo File Copy the logo file onto the destination Fax PC under the directory C:\ZETAFAX\SYSTEM\Z-GRAPH. In addition on the BAP ensure that the LESFAX Parameter file refers to this file via the LOGO_FILENAME directive. Also ensure that no letterhead is configured in the database table LESFAX_ROUTE for the route associated with this PC. Letterhead File Copy the letterhead file onto the destination Fax PC under the directory C:\ZETAFAX\SYSTEM\Z-LETTER. In addition on the BAP ensure that there is no LOGO_FILENAME directive within the LESFAX Parameter file. Also ensure that a letterhead is configured in the database table LESFAX_ROUTE for the route associated with this PC. 12.4 Fax Troubleshooting The following sections detail how FAX problems may be investigated and rectified. 12.4.1 DecNet Troubleshooting In order to check the operation of DecNet between a BAP (for example MEBAPA) and a Fax PC (for example MEXFXA) the following tests can be tried on the Fax PC : > NCP LOOP EXECUTOR COUNT 10 Check the executor name and ensure test is OK. > NCP LOOP NODE MEBAPA COUNT 10

12-37

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Ensure test is successful. > NCP LOOP NODE MEXFXA COUNT 10 Ensure test is successful. > NCP SHOW KNOW CIRCUITS Should report that ETHER-1 is On/Running. Designated Router. > NCP LOOP CIRCUIT ETHER-1 COUNT 10 Ensure test is successful. > NCP LOOP CIRCUIT ETHER-1 NODE MEBAPA COUNT 10 Ensure test is successful. > NCP SHOW EXECUTOR Check the name and DecNet address. > NCP SHOW EXEC CHAR Note down all the details (use Control-S and Control-Q to flow control ouput). Check these details with those on MEXFXA. > SETHOST MEBAPA Ensure that you can logon to the BAP from the Fax PC. In addition the following can be tried on the BAP : $ MC NCP LOOP EXECUTOR If successful no output is produced. $ MC NCP SHOW KNOWN CIRCUIT Note the circuit name (ISA-0 for example). Note name and DecNet address of adjacent routing node. $ MC NCP LOOP CIRCUIT ISA-0 NODE MEXFXA If successful then there is no output. $ MC NCP LOOP NODE MEXFXA If successful then there is no output. $ MC NCP LOOP NODE MEBAPA If successful then there is no output. $ MC NCP SHOW EXECUTOR
12-38

Also note the address of the

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

Check name and DecNet address. $ MC NCP SHOW EXEC CHAR Note down characteristics. Also check values for Max broadcast non-routers and routers. $ MC NCP SHOW KNOWN NODES Check that node names and address on MEXFXA do indeed match the values listed here. 12.4.2 Zetafax and Fax Modem Troubleshooting To determine the state of Zetafax on a Fax PC the following should be examined : The Zetafax Monitor window gives a good indication of the status of Zetafax. Any messages currently queued for Zetafax will be listed here together with their current status : SENDING CONNECTING WAITING Message is currently transmitting to the quoted Fax number. Zetafax is currently dialling the quoted Fax number. Message is held waiting for conversion or transmission. This may be because the Fax number was engaged earlier and the message transmission is to be reattempted, or it may be because all the modem cards on the Fax PC are currently in use.

Other possible states are listed in the Zetafax Users Guide Appendix B : API, Message Information. Zetafax maintains a simple text file of all messages logged by the Zetafax Server during the current run. C:\ZETAFAX\SERVER\Z-DB\SERVER.LOG This file keeps growing whilst Zetafax Server is running and is cleared down each time the Zetafax Server is restarted. The STARTUP.CMD window provides trace information relating to the PCFAX software and the underlying software packages. If a problem is suspected with one of the Fax modem cards then the status of these cards can be determined from the Zetafax Workstation program: Double left click on Zetafax icon, from the OS/2 desktop. Double left click on the Zetafax Workstation icon. Left click on Status and select Server. From this Server status window determine the status of fax devices. Chronological event logs of significant events are maintained in a series of log files of the form C:\ZETAFAX\SERVER\Z-DB\Z-YYMMDD.LOG These can be searched via the Zetafax Workstation log menu.
12-39

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

12.4.2.1 Zetafax Error messages returned to the ACSE Zetafax error codes received by the ACSE are translated into call completion codes. The table below shows which call completion codes are caused by which Zetafax error codes. All call completion codes are described in reference 1.

12-40

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

CCC 404 410 411 412 413

Zetafax Error Code & Name 16#01A# 16#007# 16#008# 16#009# 16#010# 16#014# 16#018# 16#019# L2ERR_PATH_NOT_FOUND L2ERR_CANT_OPEN_CTL_FILE L2ERR_INVALID_CTL_FILE L2ERR_CANT_OPEN_MSG_FILE L2ERR_MSG_NOT_FOUND L2ERR_DISK_FULL L2ERR_NO_ZETAFAX_INI_FILE L2ERR_BAD_ZETAFAX_INI_FILE L2ERR_CANT_CONVERT L2ERR_CVT_NO_CTL_FILE L2ERR_CVT_NO_MSG_FILE L2ERR_CVT_BAD_TIFF_MSG_FILE L2ERR_CVT_FAILED L2ERR_CVT_FILE_ERROR L2ERR_CVT_INIT_ERROR L2ERR_CVT_NO_LETTERHEAD_FILE L2ERR_CVT_INVALID_TIFF_BG_FILE L2ERR_CVT_NO_APPEND_FILE

Description Path does not exist Cant open control file Invalid control data Cant open message file Invalid message No space on disk Unable to open ZETAFAX.INI Bad format ZETAFAX.INI file Cant convert file format CTL file not found Message file not found Tiff message file invalid General error General file error General init error Letterhead file missing Letterhead or Coversheet file invalid

414

16#015# 16#203# 16#206# 16#214# 16#217# 16#218# 16#219# 16#207# 16#20E# 16#21A# 16#21B# 16#21C# 16#21D#

415

416

Graphics append file not found L2ERR_CVT_NO_INCLUDE_FILE Graphics include file not found L2ERR_CVT_BAD_TIFF_APPEND_FILE Graphics append file invalid L2ERR_CVT_BAD_TIFF_INCLUDE_FILE Graphics include file invalid L2ERR_DEVICE_FAILED L2ERR_DEVICE_BUSY L2ERR_DEVICE_OFFLINE L2ERR_INVALID_DEVICE L2ERR_NO_AVAILABLE_DEVICES L2ERR_PROTOCOL_ERROR Cant talk to device Cant talk to device - in use Should recover soon Invalid device No working devices Serious error communicating with the device Device handler timeout No dial tone on line

417 418 419 420 421 422

16#100# 16#101# 16#102# 16#011# 16#012# 16#107#

423 424

16#108# 16#10C#

L2ERR_DEVICE_TIMEOUT L2ERR_NO_DIAL_TONE

12-41

Customer Release Configuration Guide Telecomunicaciones De Mexico FAX Installation

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

CCC 425 426 427 428 429 430

Zetafax Error Code & Name 16#030# 16#10A# 16#10B# 16#103# 16#105# 16#20A# L2ERR_NO_DIAL_PERMIT L2ERR_PHONE_NUMBER_BUSY L2ERR_CALL_NOT_ANSWERED L2ERR_CANT_CONNECT L2ERR_TRANS_ERROR L2ERR_CVT_TOO_MANY_PAGES

Description No permission to send Phone number engaged Phone call not answered No answer when sending Comms error sending File too large

12.4.3 Pathworks Troubleshooting The following VMS files can be checked for Pathwork errors : PCFS$LOG_FILES:PCFS_SERVER.LOG PCFS$LOG_FILES:PCFS$STARTUP.LOG PCFS$LOG_FILES:PCFA$STARTUP_ERRORS.LOG PCFS$LOG_FILES:NETBIOS_OUTPUT.LOG PCFS$LOG_FILES:NETBIOS_ERROR.LOG PCFS$LOG_FILES:PCFS_SERVER.LOG In addition Registered File Services and Authorised File and Printer Services can be checked on VMS using admin /pcsa. On each FAXPC for example, running OS/2, try USE D: \\BAPA\FAXPCA and USE E: \\BAPB\FAXPCA to access VMS directory DSA1:[000000.FAXPCA], where DSA1 is the shadowset on the BAPs. If one of these redirections works but not the other, then this may indicate a Pathworks configuration problem on the BAPs.

12-42

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Appendix A Accounts and Privileges


This Appendix describes the arrangement of accounts that the LES software requires and the privileges given to each account. There are four account names created by the LES software installation. They are arranged in two groups - BAP and SOC accounts. On each processor there are two groups of accounts - System and Operator, with two accounts in each group, The account organisation are as shown in this Appendix for SOC and BAP processors. SOC Accounts
Group: Title: Username: Use: System Group ----------------------------System Maintenance SOCSW Owns the baseline CESTST Maintains the LES system Operator Group ----------------------------Operational Captive SOCSYS Runs the LES system SOCV For SOC Viewer

BAP Accounts
Group: Title: Username: Use: Example UICs CVAXA: CVAXB: [125,1] [125,1] [125,2] [125,2] [126,1] [127,1] [126,2] [127,2] System Group ----------------------------System Maintenance BAPSW Owns the baseline CESTST Maintains the LES system Operator Group ----------------------------Operational Captive BAPSYS Runs the LES system BAPV For SOC Viewer

NOTE: In the case of the BAP processors example UICs are given for each account for each BAP. Whilst the system accounts are the same across the clustered nodes, the BAP accounts must have different UIC group numbers. This prevents clashing cluster wide locks.

A-1

Customer Release Configuration Guide Telecomunicaciones De Mexico Accounts and Privileges

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

List of privileges required by target machine accounts:


Group: Privilege ACNT ALLSPOOL ALTPRI BUGCHK BYPASS CMEXEC CMKRNL DETACH DIAGNOSE EXQUOTA GROUP GRPNAM GRPPRV LOG_IO MOUNT NETMBX OPER PFNMAP PHY_IO PRMCEB PRMGBL PRMMBX PSWAPM READALL SECURITY SETPRV SHARE SHMEM SYSGBL SYSLCK SYSNAM SYSPRV TMPMBX VOLPRO WORLD Accounts System Group Operator Group --------------------------------------------------------System Maintenance Operational Captive * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

* * * * * * * * * * * * * *

* * * * * * * * * * * * * *

* * * * * *

* * * * * *

A-2

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico

Appendix B PC System file examples


The following file listings are examples of PC files that are necessary for the FAX software. C:\STARTUP.CMD file for PCFAX An example STARTUP.CMD file is:
ECHO ON CALL C:\PCSAOS2\PCSAOS2.CMD ECHO ON LOGON USERID /P=PASSWORD ECHO ON DEL C:\PCFAX\PCFAX.BAK RENAME C:\PCFAX\PCFAX.TRC PCFAX.BAK :TRY_AGAIN USE D: \\THBAPA\PICTOR USE E: \\THBAPB\PICTOR C:\PCFAX\PCFAX USE D: \\THBAPA\PICTOR /D USE E: \\THBAPB\PICTOR /D goto TRY_AGAIN @EXIT

B-1

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

C:\CONFIG.SYS file for Etherworks 2 on PCFAX An example CONFIG.SYS file for Etherworks 2 driver on PCFAX is :
AUTOFAIL=YES SET ZFAXINIT=C:\ZETAFAX SET DECNET=C:\PCSAOS2\DECNET SET DNETPATH=C:\PCSAOS2\DECNET SET DNETMAIL=C:\PCSAOS2\MAIL TRACEBUF=63 TRACE=ON IFS=C:\OS2\HPFS.IFS /CACHE:64 /CRECL:4 PROTSHELL=C:\OS2\PMSHELL.EXE SET USER_INI=C:\OS2\OS2.INI SET SYSTEM_INI=C:\OS2\OS2SYS.INI SET OS2_SHELL=C:\OS2\CMD.EXE SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,CONNECTIONS SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE SET COMSPEC=C:\OS2\CMD.EXE LIBPATH=C:\PCSAOS2\DLL;C:\IBMLAN\NETLIB;C:\MUGLIB\DLL;C:\IBMCOM\DLL; .;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL; SET PATH=C:\PCSAOS2\PBIN;C:\IBMLAN\NETPROG;C:\MUGLIB;C:\OS2; C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\; C:\OS2\MDOS;C:\OS2\APPS; SET DPATH=C:\PCSAOS2\DECNET;C:\PCSAOS2\PBIN;C:\PCSAOS2\CS; C:\IBMLAN\NETPROG;C:\IBMLAN;C:\MUGLIB;C:\IBMCOM;C:\OS2; C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\; C:\OS2\BITMAP;C:\OS2\MDOS;C:\OS2\APPS; SET PROMPT=$I[$P] SET HELP=C:\OS2\HELP;C:\OS2\HELP\TUTORIAL; SET GLOSSARY=C:\OS2\HELP\GLOSS; SET IPF_KEYS=SBCS PRIORITY_DISK_IO=YES FILES=50 DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM DEVICE=C:\OS2\TESTCFG.SYS DEVICE=C:\OS2\DOS.SYS DEVICE=C:\OS2\PMDD.SYS BUFFERS=60 IOPL=YES DISKCACHE=512,LW,AC:C MAXWAIT=3 MEMMAN=SWAP,PROTECT SWAPPATH=C:\OS2\SYSTEM 2048 4096 BREAK=OFF THREADS=256 PRINTMONBUFSIZE=134,134,134 COUNTRY=044,C:\OS2\SYSTEM\COUNTRY.SYS SET KEYS=ON REM SET DELDIR=C:\DELETE,512; BASEDEV=PRINT01.SYS BASEDEV=IBM1FLPY.ADD BASEDEV=IBM1S506.ADD BASEDEV=OS2DASD.DMD SET BOOKSHELF=C:\IBMLAN\BOOK;C:\OS2\BOOK; SET EPMPATH=C:\OS2\APPS; REM DEVICE=C:\OS2\APPS\SASYNCDA.SYS PROTECTONLY=NO SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS FCBS=16,8 RMSIZE=640 DEVICE=C:\OS2\MDOS\VEMM.SYS DOS=LOW,NOUMB DEVICE=C:\OS2\MDOS\VDPX.SYS DEVICE=C:\OS2\MDOS\VXMS.SYS /UMB DEVICE=C:\OS2\MDOS\VDPMI.SYS DEVICE=C:\OS2\MDOS\VCDROM.SYS DEVICE=C:\OS2\MDOS\VWIN.SYS REM DEVICE=C:\OS2\PCMCIA.SYS REM DEVICE=C:\OS2\MDOS\VPCMCIA.SYS DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\POINTDD.SYS

B-2

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples

DEVICE=C:\OS2\MOUSE.SYS DEVICE=C:\OS2\COM.SYS DEVICE=C:\OS2\MDOS\VCOM.SYS CODEPAGE=850,437 DEVINFO=KBD,UK166,C:\OS2\KEYBOARD.DCP SET EPMPATH=C:\OS2\APPS REM DEVICE and RUN statements from your older CONFIG.SYS REM IFS=C:\OS2\CDFS.IFS /Q BASEDEV=AHA154X.ADD BASEDEV=OS2SCSI.DMD BASEDEV=IBMINT13.I13 REM DEVICE=C:\OS2\APPS\SASYNCDA.SYS DEVICE=C:\OS2\MDOS\VSVGA.SYS DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP SET VIDEO_DEVICES=VIO_SVGA SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA) RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE RUN=C:\IBMCOM\LANMSGEX.EXE DEVICE=C:\IBMCOM\PROTOCOL\NETBEUI.OS2 DEVICE=C:\IBMLAN\NETPROG\RDRHELP.200 DEVICE=C:\IBMLAN\NETPROG\LOOPDRV.OS2 DEVICE=C:\PCSAOS2\DEV\DLLMAC.SYS DEVICE=C:\PCSAOS2\DEV\DNP.SYS DEVICE=C:\PCSAOS2\DEV\IOCBDRV.SYS IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN /N DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2 DEVICE=C:\IBMCOM\PROTOCOL\LANDD.OS2 DEVICE=C:\IBMCOM\PROTOCOL\LANDLLDD.OS2 DEVICE=C:\PCSAOS2\DEV\DEPCA.OS2 RUN=C:\IBMCOM\PROTOCOL\LANDLL.EXE RUN=C:\IBMLAN\NETPROG\LSDAEMON.EXE

B-3

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

C:\PCSAOS2\DEV\PROTOCOL.INI file for Etherworks 2 on PCFAX An example C:\PCSAOS2\DEV\PROTOCOL.INI file for Etherworks 2 driver on PCFAX is :
; ; ; ; ; ; ; This is the PROTOCOL.INI file for PATHWORKS for OS/2 V2.0. There are many sections in this file. Not all sections are used in every configuration. Sections that are not used do not affect the operation of the other configurations.

[protocol manager] Drivername

= PROTMAN$

; ; This section is used if DECnet, LAT, or LAD is installed. ; [DATALINK] Drivername = DLL$DEC Bindings = DEPCA RC_Buffers = 32 RL_Buffers = 43 Tx_Buffers = 16 ; ; The following sections are used if TCPIP is installed. ; [TCPIP] Drivername = TCPIP$ ArpTblSize = 10 IPSocketSize = 0 TCPConnections = 32 TCPWindowSize = 2048 TCPSegmentSize = 1024 LoadFactor = 100 LBufSz = 1100 MBufSz = 600 SBufSz = 100 LBP = 50 MBP = 30 Clientod = 10 Clientbd = 30 Clientmsg = 20 Clientamsg = 20 [RFCNETBIOS] Drivername Bindings Internetnames NumNCBs NumNames NumSessions Scope [TCPGLOBAL] [DNR] Drivername Bindings [NMDRV] Drivername Bindings SystemID SystemDesc [SOCKETS] Drivername Bindings MaxSendSize PoolSize = = = = = = = TCPNB$ TCPIP 20 16 6 8 ""

= DNR$ = TCPIP = = = = = = = = NMDRV$ TCPIP "1.3.6.1.4.1.43.1.5" " " SOCKETS$ TCPIP 1024 10000

B-4

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


NumSockets NumThreads = 32 = 32

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples

; ; This section is used if NetBEUI is installed. ; [NETBEUI_XIF] Drivername = netbeui$ ; ; The following sections are for the various Ethernet/Token Ring ; adapters. At most one of these sections is used. ; ; Digital Equipment Corporation PC Adapter. ; This section is used for all DEPCAs and EtherWorks Adapters [DEPCA] Drivername = DEPCA$ ; 3Com Etherlink II Adapter Card, 3C503 [ELNKII] IOAddress = 0x300 Interrupt = 3 MaxTransmits = 40 Drivername = ELNKII$ ; 3Com Etherlink Microchannel card, 3C523 [ELNKMC] Drivername = ELNKMC$ ; 3Com Etherlink Plus card, 3C505 [ELNKPL] Drivername = ELNKPL$ Interrupt = 3 IOAddress = 0x300 DMAChannel = 5 ; Western Digitals [MACWD] Drivername IRQ RAMAddress IOBase ReceiveBufsize Ethercard+WD8003E and /A adapter card = = = = = MACWD$ 3 0xD400 0x280 1024

; Novell NE1000 Card [MS1000] IOBase = 0x300 Interrupt = 3 Drivername = MS1000$ ; Novell NE2000 Card [MS2000] IOBase = 0x300 Interrupt = 3 Drivername = MS2000$ ; IBM Token Ring Adapter [IBMTOK] Drivername = IBMTOK$ ; 3Com TokenLink Adapter Card [TLNK] Drivername = TLNK$ IOAddress = 0x300 Interrupt = 3 DMAChannel = 1 MaxTransmits = 40

B-5

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

C:\IBMCOM\PROTOCOL.INI file for Etherworks 2 on PCFAX An example C:\IBMCOM\PROTOCOL.INI file for Etherworks 2 driver on PCFAX is :
[PROT_MAN] DRIVERNAME = PROTMAN$ [IBMLXCFG] DATALINK = DATALINK.nif LANDD_nif = LANDD.nif NETBEUI_nif = NETBEUI.nif MACETH_nif = MACETH.nif DEPCA_nif = DEPCA_nif [DATALINK] DriverName Bindings = RC_BUFFERS RL_BUFFERS TX_BUFFERS [LANDD_nif] DriverName = LANDD$ Bindings = DEPCA ETHERAND_TYPE = "I",,"I" SYSTEM_KEY = 0x0,,0x0 OPEN_OPTIONS = 0x2000,,0x2000 TRACE = 0x0,,0x0 LINKS = 8,,8 MAX_SAPS = 3,,3 MAX_G_SAPS = 0,,0 USERS = 3,,3 TI_TICK_G1 = 255,,255 T1_TICK_G1 = 15,,15 T2_TICK_G1 = 3,,3 TI_TICK_G2 = 255,,255 T1_TICK_G2 = 25,,25 T2_TICK_G2 = 10,,10 IPACKETS = 250,,250 UIPACKETS = 100,,100 MAXTRANSMITS = 6,,6 MINTRANSMITS = 2,,2 TCBS = 64,,64 GDTS = 30,,30 ELEMENTS = 800,,800 [NETBEUI_nif] DriverName = netbeui$ Bindings = DEPCA ETHERAND_TYPE = "I" USEADDRREV = "YES" OS2TRACEMASK = 0x0 SESSIONS = 40 NCBS = 95 NAMES = 21 SELECTORS = 5 USEMAXDATAGRAM = "NO" ADAPTRATE = 1000 WINDOWERRORS = 0 MAXDATARCV = 4168 TI = 30000 T1 = 500 T2 = 200 MAXIN = 1 MAXOUT = 1 NETBIOSTIMEOUT = 500 NETBIOSRETRIES = 8 NAMECACHE = 0 = DLL$DEC DEPCA = 32 = 43 = 16

B-6

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


PIGGYBACKACKS = 1 DATAGRAMPACKETS = 2 PACKETS = 350 LOOPPACKETS = 1 PIPELINE = 5 MAXTRANSMITS = 6 MINTRANSMITS = 2 DLCRETRIES = 5 [DEPCA] DriverName = DEPCA$ [MACETH_nif] DriverName = MACETH$ MaxRequests = 8 MaxTransmits = 12 ReceiveBuffers = 12 ReceiveBufSize = 256 ReceiveChains = 12

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples

B-7

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

C:\CONFIG.SYS file for Etherworks 3 on PCFAX An example CONFIG.SYS file for Etherworks 3 driver on PCFAX is :
AUTOFAIL=YES SET DECNET=C:\PCSAOS2\DECNET SET DNETPATH=C:\PCSAOS2\DECNET SET DNETMAIL=C:\PCSAOS2\MAIL SET ZFAXINIT=C:\ZETAFAX IFS=C:\OS2\HPFS.IFS /CACHE:64 /CRECL:4 PROTSHELL=C:\OS2\PMSHELL.EXE SET USER_INI=C:\OS2\OS2.INI SET SYSTEM_INI=C:\OS2\OS2SYS.INI SET OS2_SHELL=C:\OS2\CMD.EXE SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,CONNECTIONS SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE SET COMSPEC=C:\OS2\CMD.EXE LIBPATH=C:\PCSAOS2\DLL;C:\IBMLAN\NETLIB;C:\MUGLIB\DLL; C:\IBMCOM\DLL;.;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL; SET PATH=C:\PCSAOS2\PBIN;C:\IBMLAN\NETPROG;C:\MUGLIB; C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\; C:\OS2\MDOS;C:\OS2\APPS; SET DPATH=C:\PCSAOS2\DECNET;C:\PCSAOS2\PBIN;C:\PCSAOS2\CS; C:\IBMLAN\NETPROG;C:\IBMLAN;C:\MUGLIB;C:\IBMCOM;C:\OS2; C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\; C:\OS2\BITMAP;C:\OS2\MDOS;C:\OS2\APPS; SET PROMPT=$i[$p] SET HELP=C:\OS2\HELP;C:\OS2\HELP\TUTORIAL; SET GLOSSARY=C:\OS2\HELP\GLOSS; SET IPF_KEYS=SBCS PRIORITY_DISK_IO=YES FILES=20 DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM DEVICE=C:\OS2\TESTCFG.SYS DEVICE=C:\OS2\DOS.SYS DEVICE=C:\OS2\PMDD.SYS BUFFERS=30 IOPL=YES DISKCACHE=512,LW,AC:C MAXWAIT=3 MEMMAN=SWAP,PROTECT SWAPPATH=C:\OS2\SYSTEM 2048 4096 BREAK=OFF THREADS=256 PRINTMONBUFSIZE=134,134,134 COUNTRY=044,C:\OS2\SYSTEM\COUNTRY.SYS SET KEYS=ON REM SET DELDIR=C:\DELETE,512; BASEDEV=PRINT01.SYS BASEDEV=IBM1FLPY.ADD BASEDEV=IBM1S506.ADD BASEDEV=OS2DASD.DMD SET BOOKSHELF=C:\IBMLAN\BOOK;C:\OS2\BOOK DEVICE=C:\OS2\APPS\SASYNCDA.SYS PROTECTONLY=NO SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS FCBS=16,8 RMSIZE=640 DEVICE=C:\OS2\MDOS\VEMM.SYS DOS=LOW,NOUMB DEVICE=C:\OS2\MDOS\VDPX.SYS DEVICE=C:\OS2\MDOS\VXMS.SYS /UMB DEVICE=C:\OS2\MDOS\VDPMI.SYS DEVICE=C:\OS2\MDOS\VCDROM.SYS DEVICE=C:\OS2\MDOS\VWIN.SYS DEVICE=C:\OS2\APM.SYS DEVICE=C:\OS2\MDOS\VAPM.SYS DEVICE=C:\OS2\PCMCIA.SYS DEVICE=C:\OS2\MDOS\VPCMCIA.SYS DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\MOUSE.SYS

B-8

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples

DEVICE=C:\OS2\COM.SYS (1,03F8,4,I) (2,02F8,3,I) (3,03E8,7,I) DEVICE=C:\OS2\MDOS\VCOM.SYS CODEPAGE=850,437 DEVINFO=KBD,UK166,C:\OS2\KEYBOARD.DCP DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP SET VIDEO_DEVICES=VIO_SVGA SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA) DEVICE=C:\OS2\MDOS\VSVGA.SYS RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE RUN=C:\IBMCOM\LANMSGEX.EXE DEVICE=C:\IBMCOM\PROTOCOL\NETBEUI.OS2 DEVICE=C:\IBMLAN\NETPROG\RDRHELP.200 DEVICE=C:\PCSAOS2\DEV\DLLMAC.SYS DEVICE=C:\PCSAOS2\DEV\DNP.SYS DEVICE=C:\PCSAOS2\DEV\IOCBDRV.SYS IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN /N DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2 DEVICE=C:\IBMCOM\PROTOCOL\LANDD.OS2 DEVICE=C:\IBMCOM\PROTOCOL\LANDLLDD.OS2 DEVICE=C:\PCSAOS2\DEV\EWRK3.OS2 RUN=C:\IBMCOM\PROTOCOL\LANDLL.EXE RUN=C:\IBMLAN\NETPROG\LSDAEMON.EXE

B-9

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

C:\PCSAOS2\DEV\PROTOCOL.INI for Etherworks 3 on PCFAX An example C:\PCSAOS2\DEV\PROTOCOL.INI file for Etherworks3 driver on PCFAX is :
; ; ; ; ; ; ; This is the PROTOCOL.INI file for PATHWORKS for OS/2 V2.0. There are many sections in this file. Not all sections are used in every configuration. Sections that are not used do not affect the operation of the other configurations.

[protocol manager] Drivername

= PROTMAN$

; ; This section is used if DECnet, LAT, or LAD is installed. ; [DATALINK] Drivername = DLL$DEC Bindings = EWRK3 RC_Buffers = 32 RL_Buffers = 43 Tx_Buffers = 16 ; ; The following sections are used if TCPIP is installed. ; [TCPIP] Drivername = TCPIP$ ArpTblSize = 10 IPSocketSize = 0 TCPConnections = 32 TCPWindowSize = 2048 TCPSegmentSize = 1024 LoadFactor = 100 LBufSz = 1100 MBufSz = 600 SBufSz = 100 LBP = 50 MBP = 30 Clientod = 10 Clientbd = 30 Clientmsg = 20 Clientamsg = 20 [RFCNETBIOS] Drivername Bindings Internetnames NumNCBs NumNames NumSessions Scope [TCPGLOBAL] [DNR] Drivername Bindings [NMDRV] Drivername Bindings SystemID SystemDesc [SOCKETS] Drivername Bindings MaxSendSize PoolSize = = = = = = = TCPNB$ TCPIP 20 16 6 8 ""

= DNR$ = TCPIP = = = = = = = = NMDRV$ TCPIP "1.3.6.1.4.1.43.1.5" " " SOCKETS$ TCPIP 1024 10000

B-10

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


NumSockets NumThreads = 32 = 32

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples

; ; This section is used if NetBEUI is installed. ; [NETBEUI_XIF] Drivername = netbeui$ ; ; The following sections are for the various Ethernet/Token Ring ; adapters. ; At most one of these sections is used. ; ; Digital Equipment Corporation PC Adapter. ; This section is used for all DEPCAs and EtherWorks Adapters [DEPCA] Drivername = DEPCA$ ; 3Com Etherlink II Adapter Card, 3C503 [ELNKII] IOAddress = 0x300 Interrupt = 3 MaxTransmits = 40 Drivername = ELNKII$ ; 3Com Etherlink Microchannel card, 3C523 [ELNKMC] Drivername = ELNKMC$ ; 3Com Etherlink Plus card, 3C505 [ELNKPL] Drivername = ELNKPL$ Interrupt = 3 IOAddress = 0x300 DMAChannel = 5 ; Western Digitals [MACWD] Drivername IRQ RAMAddress IOBase ReceiveBufsize Ethercard+WD8003E and /A adapter card = = = = = MACWD$ 3 0xD400 0x280 1024

; Novell NE1000 Card [MS1000] IOBase = 0x300 Interrupt = 3 Drivername = MS1000$ ; Novell NE2000 Card [MS2000] IOBase = 0x300 Interrupt = 3 Drivername = MS2000$ ; IBM Token Ring Adapter [IBMTOK] Drivername = IBMTOK$ ; 3Com TokenLink Adapter Card [TLNK] Drivername = TLNK$ IOAddress = 0x300 Interrupt = 3 DMAChannel = 1 MaxTransmits = 40 ; Etherworks 3 Card. [EWRK3]

B-11

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples


DriverName IOAddress RamAddress MemoryMode Interrupt Diagnostic = = = = = = EWRK3$ 0x300 0xD000 2 11 1

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

B-12

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples

C:\IBMCOM\PROTOCOL.INI for Etherworks 3 on PCFAX An example IBMCOM\PROTOCOL.INI file for Etherworks 3 driver on PCFAX :
[PROT_MAN] DRIVERNAME = PROTMAN$ [IBMLXCFG] DATALINK = DATALINK.nif DEPCA_nif = DEPCA.nif EWRK3_nif = EWRK3.nif MACETH_nif = MACETH.nif LANDD_nif = LANDD.nif NETBEUI_nif = NETBEUI.nif [DATALINK] DriverName Bindings = RC_Buffers RL_Buffers Tx_Buffers [LANDD_nif] DriverName = LANDD$ Bindings = EWRK3 ETHERAND_TYPE = "I" SYSTEM_KEY = 0x0 OPEN_OPTIONS = 0x2000 TRACE = 0x0 LINKS = 8 MAX_SAPS = 3 MAX_G_SAPS = 0 USERS = 3 TI_TICK_G1 = 255 T1_TICK_G1 = 15 T2_TICK_G1 = 3 TI_TICK_G2 = 255 T1_TICK_G2 = 25 T2_TICK_G2 = 10 IPACKETS = 250 UIPACKETS = 100 MAXTRANSMITS = 6 MINTRANSMITS = 2 TCBS = 64 GDTS = 30 ELEMENTS = 800 [NETBEUI_nif] DriverName = netbeui$ Bindings = EWRK3 ETHERAND_TYPE = "I" USEADDRREV = "YES" OS2TRACEMASK = 0x0 SESSIONS = 40 NCBS = 95 NAMES = 21 SELECTORS = 5 USEMAXDATAGRAM = "NO" ADAPTRATE = 1000 WINDOWERRORS = 0 MAXDATARCV = 4168 TI = 30000 T1 = 500 T2 = 200 MAXIN = 1 MAXOUT = 1 NETBIOSTIMEOUT = 500 NETBIOSRETRIES = 8 = DLL$DEC EWRK3 = 32 = 43 = 16

B-13

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples


NAMECACHE = 0 PIGGYBACKACKS = 1 DATAGRAMPACKETS = 2 PACKETS = 350 LOOPPACKETS = 1 PIPELINE = 5 MAXTRANSMITS = 6 MINTRANSMITS = 2 DLCRETRIES = 5 [MACETH_nif] DriverName = MACETH$ MaxRequests = 8 MaxTransmits = 12 ReceiveBuffers = 12 ReceiveBufSize = 256 ReceiveChains = 12 [DEPCA] DriverName = DEPCA$ [EWRK3] DriverName = EWRK3$

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

B-14

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples

C:\IBMLAN\IBMLAN.INI on PCFAX An example IBMLAN\IBMLAN.INI file on PCFAX :


; OS/2 LAN Server initialization file [networks] net1 = NETBEUI$,0,LM10,32,50,14 net2 = dec$nbe,0 ; netlb = LOOPDRV$,0 ; This information is read by the redirector at ; device initialization time [requester] COMPUTERNAME = HYDR_S DOMAIN = HYDR_D The following parameters generally do not need to be changed by the user. charcount = 16 chartime = 250 charwait = 3600 keepconn = 600 keepsearch = 600 maxcmds = 16 maxerrorlog = 100 maxthreads = 10 maxwrkcache = 64 numalerts = 12 numcharbuf = 10 numservices = 16 numworkbuf = 15 numdgrambuf = 14 othdomains = printbuftime = 90 sesstimeout = 45 sizcharbuf = 512 sizerror = 1024 sizworkbuf = 4096 The next lines help you to locate bits in the wrkheuristics entry. 1 2 3 0123456789012345678901234567890123 wrkheuristics = 1111111121311111110001011120111221 WRKSERVICES = LSCLIENT wrknets = NET1,NET2

; ;

; ; ;

[messenger] logfile = messages.log sizmessbuf = 4096 [lsclient] multilogon = no timesync = yes logonverification = domain logonwarningmsgs = all [netlogon] SCRIPTS = C:\IBMLAN\REPL\IMPORT\SCRIPTS pulse = 60 update = yes [replicator] replicate = IMPORT IMPORTPATH = C:\IBMLAN\REPL\IMPORT tryuser = yes password = interval = 5

B-15

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples


guardtime = 2 pulse = 3 random = 60 [dcdbrepl] tryuser = yes password = interval = 5 guardtime = 2 pulse = 3 random = 60 [server]

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

; ; ; ;

; ; ;

alertnames = auditing = no autodisconnect = 120 maxusers = 32 The following parameters generally do not need to be changed by the user. NOTE: srvnets= is represented in the server info struct as a 16-bit lan mask. Srvnet names are converted to indexes within [networks] for the named nets. guestacct = guest accessalert = 5 alertsched = 5 diskalert = 5000 erroralert = 5 logonalert = 5 maxauditlog = 100 maxchdevjob = 6 maxchdevq = 2 maxchdevs = 2 maxconnections = 128 maxlocks = 64 maxopens = 250 maxsearches = 50 maxsessopens = 80 maxsessreqs = 50 maxsessvcs = 1 maxshares = 16 netioalert = 5 numbigbuf = 12 numfiletasks = 1 numreqbuf = 36 sizreqbuf = 4096 srvanndelta = 3000 srvannounce = 60 The next lines help you to locate bits in the srvheuristics entry. 1 01234567890123456789 srvheuristics = 11110141111311001331 SRVSERVICES = NETLOGON,LSSERVER srvnets = NET1,NET2

[alerter] sizalertbuf = 3072 [netrun] maxruns = 3 runpath = C:\ [lsserver] cleanup = yes srvpipes = 3 [services] ; Correlates name of service to pathname of service program. ; The pathname must be either

B-16

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002


; ; ;

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples

1) an absolute path (including the drive specification) OR 2) a path relative to the IBMLAN root alerter = services\alerter.exe dcdbrepl = services\dcdbrepl.exe dlrinst = services\dlrinst.exe genalert = services\genalert.exe lsclient = services\lsclient.exe lsserver = services\lsserver.exe messenger = services\msrvinit.exe netlogon = services\netlogon.exe netpopup = services\netpopup.exe netrun = services\runservr.exe remoteboot = services\rplservr.exe replicator = services\replicat.exe requester = services\wksta.exe server = services\netsvini.exe timesource = services\timesrc.exe ups = services\ups.exe

B-17

Customer Release Configuration Guide Telecomunicaciones De Mexico PC System file examples

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

C:\PCSAOS2\PCSAOS2.CMD on PCFAX An example C:\PCSAOS2\PCSAOS2.CMD file on PCFAX :


echo off :INSTALL if not exist C:\PCSAOS2\INSTALL.CMD goto SETUP call C:\PCSAOS2\INSTALL.CMD del C:\PCSAOS2\INSTALL.CMD :SETUP if not exist C:\PCSAOS2\SETUP.CMD goto INITIATE call C:\PCSAOS2\SETUP.CMD del C:\PCSAOS2\SETUP.CMD :INITIATE ECHO Initiating PATHWORKS for OS/2 2.0 ... detach C:\PCSAOS2\PBIN\MOP if errorlevel 1 goto FAILED C:\PCSAOS2\PBIN\STARTDNP if errorlevel 1 goto FAILED :PROCESS ECHO Starting DECnet components ... detach C:\PCSAOS2\PBIN\SPAWNER if errorlevel 1 goto FAILED if exist C:\PCSAOS2\NVDPRO.CMD call C:\PCSAOS2\NVDPRO.CMD ECHO Starting the Local Area Transport (LAT) ... detach C:\PCSAOS2\PBIN\LATCP /D:20 /S:4 if errorlevel 1 goto FAILED :VERIFY if not exist C:\PCSAOS2\VERIFY.CMD goto COMPLETED ECHO Verifying PATHWORKS for OS/2 2.0 Installation. call C:\PCSAOS2\VERIFY.CMD del C:\PCSAOS2\VERIFY.CMD :COMPLETED ECHO PATHWORKS for OS/2 2.0 successfully started. goto END :FAILED ECHO PATHWORKS for OS/2 2.0 failed. pause :END

B-18

A4-SCG-003076-1 Issue V3.9 - Accepted 21-August-2002

Customer Release Configuration Guide Telecomunicaciones De Mexico Configuration Document

Index
@Projectinstall 4-10 Automated completion of installation 4-25 Automated file protection 2-2 Bap installation - Pre-requisites 4-6 BAP parameter definition - during installation 4-13 Confidence checks 4-39 Defining BAP parameters - during installation 4-13 DEFSAD.COM - BAP 4-31 DEFSAD.COM - SOC 4-63 DEFSAD.COM 4-13 Deinstall BAP 4-3 FEP - triggering on first pass 4-25 FEP installation - during installation 4-17 FEP Installation 4-17 FEP load file definition - first pass 4-25 FEP SYS files 4-24 Installation (full) summary 4-1 INSTALLFEP.COM 4-17 Installing BAP from disk 4-9 Installing BAP from tape 4-9 Installing FEPs - during installation 4-17 Post installation checks 4-22 Projectinstall 4-10 Protected file restoration 4-22 Reboot after installation 4-18 Renaming FEP SYS files 4-24 Restoring saved files 4-22 SADREF - during installation 4-13 Saved file restoration - automated 4-30 Stop Master BAP - first pass 4-24 SYS files 4-24 Trigger FEPs 4-25 VMS Difference command 4-23