V7000 Configuration and Maintenance Guide - Atossupport.bull.com/ols/product/system/gcos7/gcos7-com/g7-dps7000/doc...V7000 Configuration and Maintenance Guide iv 77 A2 77US Chapter

V7000

Configuration and

Maintenance Guide DPS

7000/XTA

NO

VASC

ALE

7000

Hardware: DPS7000/XTA

REFERENCE77 A2 77US 04

DPS7000/XTANOVASCALE 7000

V7000Configuration and Maintenance Guide

Hardware: DPS7000/XTA

March 2006

BULL CEDOC

357 AVENUE PATTON

B.P.20845

49008 ANGERS CEDEX 01

FRANCE

REFERENCE77 A2 77US 04

The following copyright notice protects this book under Copyright laws which prohibit such actions as, but notlimited to, copying, distributing, modifying, and making derivative works.

Copyright Bull SAS 2006

Printed in France

Suggestions and criticisms concerning the form, content, and presentation of thisbook are invited. A form is provided at the end of this book for this purpose.

To order additional copies of this book or other Bull Technical Publications, youare invited to use the Ordering Form also provided at the end of this book.

Trademarks and Acknowledgements

We acknowledge the right of proprietors of trademarks mentioned in this book.

Intel® and Itanium® are registered trademarks of Intel Corporation.

Windows® and Microsoft® software are registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark in the United States of America and other countries licensed exclusively throughthe Open Group.

Linux® is a registered trademark of Linus Torvalds.

The information in this document is subject to change without notice. Bull will not be liable for errors containedherein, or for incidental or consequential damages in connection with the use of this material.

77 A2 77US iii

Preface

This guide describes the configuration and maintenance of a DPS 7000/XTA machine.

It contains all the information required to administer, configure and maintain the V7000 Virtual Machine (V7000 VM).

The other DPS 7000/XTA machine guides are also listed in the present guide.

Further information can be obtained via the V7000 Tools Help Engine.

Bull support technicians

Chapter 1 Introduction gives an overview of V7000 tools (reserved for BULL Support technicians), rights and security groups, and Init keys.

Chapter 2 V7000 Configuration Editor describes how to create and edit a V7000 configuration.

Chapter 3 GCOS7 Disk Manager describes how to create, rename, normalize and delete the virtual disks used by GCOS7.

Chapter 4 V7000 Information Collector describes how to collect the data required for maintenance.

Chapter 5 V7000 Key Manager describes how to install or check the hardware key for access to the V7000 platform.

Chapter 6 V7000 Platform Identifier describes platform identification required for hardware key calculation.

Scope

Intended Reader

Structure

V7000 Configuration and Maintenance Guide

iv 77 A2 77US

Chapter 7 V7000 Configuration Tools describes:

- how to use the Alarm Transfer Configurator. To set the parameters required to transfer alarms to the Bull Support GTS Center

- how to use the MasterSlave Wait Time Configuration to set wait time for a V7000 user to change from Slave status to Master status.

Chapter 8 V7000 Trace Manager describes how to activate the trace in order to collect maintenance data.

Chapter 9 Backing up a DPS 7000/XTA Platform's System Environment describes how to perform a system backup in order to be able to recover from a serious hardware or software failure.

Chapter 10 Power Supply Management describes the implementation of a mechanism for shutting down the V7000 virtual machine after the shutdown of applications running on GCOS7 when the server switches to battery power subsequent to a drop in power or power failure.

Chapter 11 V7000 Log Viewer Tool describes the tool used to view, on a client station, a specific log, and collect and merge all Event Logs Windows or selected ones (Application, System, V7000, V7000_Consoles_S0, V7000_INTEROP7) on a V7000 machine, by chronological order in a new log file that can be saved.

Chapter 12 V7000 Firewall Configurator describes how to configure the native firewall from Windows 2003 SP1 or Windows XP SP2 for V7000, Interop7 and factory installed third party components.

Chapter 13 Load Galileo Firmware describes how to update the firmware of a Galileo device directly from V7000 software.

Chapter 14 V7000 Performance Log describes how to launch V7000 performances audit.

Preface

77 A2 77US v

Appendix A V7000 Resources: Description

Appendix B V7000 Resources: External Identification

Appendix C Deploy Center V5.0 Installation

Appendix D Reversing disks

Appendix E Disaster Recovery

Appendix F Recommendations for Creating W2K Shared Disks

Appendix G RCF7 Configuration

Glossary

Index


vi 77 A2 77US

V7000 Operator’s Guide.......................................................................... 47 A2 74US V7000 Software Installation and Activation Guide ................................. 77 A2 88US Evolution Guide....................................................................................... 47 A2 76US GCOS7-V10 System Installation Configuration and Updating Guide ................................................................................ 47 A2 23US V7000 Configuration and Maintenance Guide ....................................... 77 A2 77US GCOS7-V10 System Operator’s Guide.................................................... 47 A2 53US Interop7 User’s GUIDE........................................................................... 47 A2 91US

Bibliography

77 A2 77US vii

Table of Contents

1. Introduction

1.1 List of V7000 Tools Reserved for Bull Support Technicians .......................................... 1-2 1.2 V7000 use and Administration: Rights and Security Groups.......................................... 1-5

1.2.1 Rights................................................................................................................. 1-5 1.2.2 User Roles and Windows™ Security Group Membership................................. 1-5 1.2.3 Privileges Required for an ‘Action Launched by a User’ ................................... 1-6

1.3 Using V7000 Tools........................................................................................................ 1-10 1.3.1 Complete Installation ....................................................................................... 1-10 1.3.2 Adapting the Configuration .............................................................................. 1-12 1.3.3 Upgrading a DPS 7000/XTA............................................................................ 1-13 1.3.4 Changing a Hardware Component .................................................................. 1-14 1.3.5 Adding a Hardware Component ...................................................................... 1-15 1.3.6 Reconfiguring a Network Card ........................................................................ 1-15

1.4 V7000 Key..................................................................................................................... 1-16

2. V7000 Configuration Editor

2.1 Users............................................................................................................................... 2-1 2.2 Tool Description .............................................................................................................. 2-2 2.3 Configuration Editor Presentation ................................................................................... 2-4 2.4 V7000 Configuration ....................................................................................................... 2-5 2.5 Objects ............................................................................................................................ 2-6 2.6 Hierarchization ................................................................................................................ 2-7 2.7 Procedure........................................................................................................................ 2-7 2.8 V7000 Configuration Resources..................................................................................... 2-8

2.8.1 V7000 Resource Identification........................................................................... 2-8 2.8.1.1 External Type .................................................................................... 2-8 2.8.1.2 External Name................................................................................... 2-9

2.8.2 Potential V7000 Resources ............................................................................... 2-9


viii 77 A2 77US

2.8.3 Resource Limits ............................................................................................... 2-10 2.9 Configuration Editor Commands................................................................................... 2-11

2.9.1 Configuration Editor Home Page..................................................................... 2-12 2.9.2 V7000 Configuration Root Context Menu........................................................ 2-13

2.9.2.1 New Command................................................................................ 2-14 2.9.2.2 Open Command.............................................................................. 2-17 2.9.2.3 Save Commands............................................................................. 2-19 2.9.2.4 Check Command ............................................................................ 2-19 2.9.2.5 Activate Command.......................................................................... 2-22 2.9.2.6 Copy to Clipboard Command.......................................................... 2-22

2.9.3 Global Information ........................................................................................... 2-23 2.9.3.1 Selecting Global Information ........................................................... 2-23 2.9.3.2 Global Information Context Menu ................................................... 2-23

2.9.4 CPUs (Processors) .......................................................................................... 2-26 2.9.4.1 Selecting the CPUs Node ............................................................... 2-26 2.9.4.2 CPUs Context Menu ....................................................................... 2-26 2.9.4.3 IPxx Context Menu.......................................................................... 2-29

2.9.5 MMUs (Memories) ........................................................................................... 2-30 2.9.5.1 Selecting MMUs .............................................................................. 2-30 2.9.5.2 MMUs Context Menu ...................................................................... 2-31 2.9.5.3 MUxx Context Menu........................................................................ 2-33

2.9.6 IOPs (Input / Output Processors) .................................................................... 2-34 2.9.6.1 Selecting IOPs................................................................................. 2-35 2.9.6.2 IOPs Context Menu......................................................................... 2-36 2.9.6.3 IOxx Context Menu ......................................................................... 2-38 2.9.6.4 PXmn Context Menu ....................................................................... 2-42 2.9.6.5 Disk Controller Context Menu ......................................................... 2-44 2.9.6.6 Tape Cartridge Controller Context Menu ........................................ 2-47 2.9.6.7 Printer Controller Context Menu...................................................... 2-54 2.9.6.8 Telecom Controller Context Menu .................................................. 2-58 2.9.6.9 Disk Context Menu.......................................................................... 2-60 2.9.6.10 Tape Cartridge Context Menu......................................................... 2-62 2.9.6.11 Printer Context Menu ...................................................................... 2-63 2.9.6.12 Telecom Context Menu ................................................................... 2-65

2.10 Sharable Disks Configuration ....................................................................................... 2-66 2.10.1 Sharable Property of a GCOS7 Disk ............................................................... 2-66 2.10.2 Identification Information of the Partner Site ................................................... 2-72 2.10.3 Checking the Configuration (Check Command).............................................. 2-76

77 A2 77US ix

3. GCOS7 Disk Manager

3.1 General Presentation ...................................................................................................... 3-1 3.2 Implementing GCOS7 Disks: GCOS_Disks Directories ................................................. 3-2 3.3 Protecting GCOS7 Disks ................................................................................................ 3-4

3.3.1 GCOS7 Disk Files (MSxx) ................................................................................. 3-4 3.3.2 Upstream GCOS_Disks Tree Directory Leading to an MSxx File..................... 3-4

3.4 GCOS7 Disk Manager User Rights ................................................................................ 3-5 3.5 GCOS7 Disk Manager Functions ................................................................................... 3-6

3.5.1 CREATE ............................................................................................................ 3-9 3.5.2 RENAME ......................................................................................................... 3-10 3.5.3 MAKE UP......................................................................................................... 3-11 3.5.4 DELETE........................................................................................................... 3-11

3.6 External Visibility........................................................................................................... 3-12 3.6.1 General Screen Presentation .......................................................................... 3-12 3.6.2 Home Page...................................................................................................... 3-15 3.6.3 CREATE Windows........................................................................................... 3-16

3.6.3.1 Home Page ..................................................................................... 3-16 3.6.3.2 Working Directory Selection Window.............................................. 3-17 3.6.3.3 Window after Opening the Working Directory (no File Selected) ... 3-18 3.6.3.4 Window after Opening the Working Directory (File Selected) ........ 3-20 3.6.3.5 Home Page During the Creation of a File ....................................... 3-21

3.6.4 RENAME Windows.......................................................................................... 3-23 3.6.4.1 Home Page ..................................................................................... 3-23 3.6.4.2 Home Page after Opening a Directory and Entering a Valid File Name

(MSGG in the Example) .................................................................. 3-24 3.6.4.3 Home Page after Entering a New Valid Name for the File (MSCC in the

Example) ......................................................................................... 3-27 3.6.4.4 Home Page after Pressing RENAME ............................................. 3-29

3.6.5 DELETE Windows ........................................................................................... 3-30 3.6.5.1 Home Page ..................................................................................... 3-30 3.6.5.2 Home Page after Opening a Directory and Entering a Valid File Name

(MSCC in the Example) .................................................................. 3-31 3.6.5.3 Home Page after Pressing the Yes Button ..................................... 3-32

3.6.6 MAKE UP Windows......................................................................................... 3-33 3.6.6.1 Home Page ..................................................................................... 3-33 3.6.6.2 File Selection Window..................................................................... 3-34 3.6.6.3 Home Page after Selecting Files..................................................... 3-35

3.6.7 HISTORY Windows ......................................................................................... 3-37 3.6.7.1 File Selection Window..................................................................... 3-37 3.6.7.2 History Files..................................................................................... 3-38

3.7 Restrictions ................................................................................................................... 3-39


x 77 A2 77US

3.8 GCOS7 Disk Shared Mode Function............................................................................ 3-39 3.8.1 DEFINE SHARING Function ........................................................................... 3-41 3.8.2 DISPLAY Function........................................................................................... 3-45 3.8.3 Shared Mode With RENAME, DELETE and MAKE UP Functions ................. 3-47

4. V7000 Information Collector

4.1 Function Offered ............................................................................................................. 4-3 4.2 Creation of the Cabinet File ............................................................................................ 4-6 4.3 The Helps........................................................................................................................ 4-9 4.4 The Errors ..................................................................................................................... 4-11 4.5 Saving Collected Information on a DAT Cartridge........................................................ 4-12

5. V7000 Key Manager

6. V7000 Platform Identifier

7. V7000 Configuration Tool

7.1 Alarm Transfer Configurator Parameters and Transfer Test button ............................... 7-2 7.2 MasterSlave Wait Time Configuration ............................................................................ 7-6

8. V7000 Trace Manager

8.1 V7000 Trace Manager Home Page ................................................................................ 8-3 8.2 Selecting or Displaying Trace Domains.......................................................................... 8-4 8.3 Select Trace Level .......................................................................................................... 8-6 8.4 Start Trace ...................................................................................................................... 8-8 8.5 Stop Trace....................................................................................................................... 8-9 8.6 Quit.................................................................................................................................. 8-9 8.7 Checks and Errors ........................................................................................................ 8-10

9. Backing up a DPS 7000/XTA or Novascale 7000 Platform’s System Environment

9.1 Overview ......................................................................................................................... 9-1 9.2 Reminders....................................................................................................................... 9-2

9.2.1 Not Raided Models ............................................................................................ 9-2 9.2.2 Raided Models................................................................................................... 9-3

9.3 Archiving ......................................................................................................................... 9-4

77 A2 77US xi

9.4 Cloning ............................................................................................................................ 9-5 9.5 Errors Encountered during Cloning Operations............................................................ 9-17 9.6 Errors encountered after Restarting on the Clone........................................................ 9-17 9.7 Cloning procedure with two different internal disks ...................................................... 9-18 9.8 NT Backup .................................................................................................................... 9-20

9.8.1 Backup............................................................................................................. 9-21 9.8.2 Restoration ...................................................................................................... 9-26 9.8.3 Troubleshooting ............................................................................................... 9-31 9.8.4 Rebuild a New System Disk ............................................................................ 9-31

9.9 Hardware mirroring for DPS7000/XTA 1X4 .................................................................. 9-32 9.9.1 Save of system disk......................................................................................... 9-33 9.9.2 Back to a steady system.................................................................................. 9-33 9.9.3 Disk Substitution in case of disk Hardware Failure Windows running ............ 9-34 9.9.4 Disk substitution disk in case of disk Hardware Failure Windows stopped..... 9-34 9.9.5 ServerRaid manager Graphical User Interface Tool (GUI) ............................. 9-34

9.10 Hardware mirroring for DPS7000/XTA X5 .................................................................... 9-37 9.10.1 Save of system disk......................................................................................... 9-38 9.10.2 Back to a steady system.................................................................................. 9-39 9.10.3 Disk Substitution in case of disk Hardware Failure Windows running ............ 9-39 9.10.4 Disk substitution disk in case of disk Hardware Failure Windows stopped..... 9-40 9.10.5 MegaRAID Client Tool Graphical User Interface Tool..................................... 9-40

9.11 Hardware mirroring for Novascale 7000 ....................................................................... 9-45 9.11.1 Disk locations in Chaparral sub-system .......................................................... 9-47 9.11.2 Backup Disk creation....................................................................................... 9-47 9.11.3 Restart from an old backup disk ...................................................................... 9-49

10. Power Supply Management

10.1 Principle ........................................................................................................................ 10-1 10.2 Processing Events ........................................................................................................ 10-2 10.3 Implementation ............................................................................................................. 10-5

10.3.1 Startup of PowerChute® Business Edition Console ........................................ 10-5 10.3.2 Startup of PowerChute® Business Edition Agent ............................................ 10-9 10.3.3 Configuring the Power Failed Event .............................................................. 10-13 10.3.4 Configuring the Power Restored Event ......................................................... 10-14 10.3.5 Configuring the Time on Battery Threshold Exceeded Event ....................... 10-15 10.3.6 Configuring the Shutdown ............................................................................. 10-17

10.4 Control and Errors....................................................................................................... 10-18


xii 77 A2 77US

11. V7000 Log Viewer Tool

11.1 How to launch V7000 Log Viewer Tool......................................................................... 11-2 11.2 V7000 Log Viewer Tool use.......................................................................................... 11-3

A. V7000 Resources: Description

A.1 90xx.................................................................................................................................A-1 A.2 CONS..............................................................................................................................A-2 A.3 CPM-V7...........................................................................................................................A-3 A.4 CT-V7..............................................................................................................................A-4 A.5 EMU-V7...........................................................................................................................A-5 A.6 ELT..................................................................................................................................A-6 A.7 ETHA...............................................................................................................................A-7 A.8 FSA .................................................................................................................................A-8 A.9 IOP-V7 ............................................................................................................................A-9 A.10 IP-V7 .........................................................................................................................A-10 A.11 LNM-V7 .........................................................................................................................A-11 A.12 MEM-V7 ........................................................................................................................A-12 A.13 MSP-V7.........................................................................................................................A-13 A.14 NCC-V7.........................................................................................................................A-14 A.15 PR90 .........................................................................................................................A-15 A.16 PSI-V7 .........................................................................................................................A-16 A.17 PXD-V7 .........................................................................................................................A-17 A.18 PXL-V7 .........................................................................................................................A-18 A.19 PXN-V7 .........................................................................................................................A-19 A.20 PXP-V7 .........................................................................................................................A-20 A.21 PXT-V7 .........................................................................................................................A-21 A.22 RMSC .........................................................................................................................A-22 A.23 TC-V7 .........................................................................................................................A-23 A.24 TDEV .........................................................................................................................A-24

77 A2 77US xiii

B. V7000 Resources: External Identification

B.1 Naming Controllers and Devices ....................................................................................B-1 B.1.1 External Name...................................................................................................B-1 B.1.2 External Type.....................................................................................................B-2 B.1.3 Controllers and Telecom Lines..........................................................................B-3

C. Deploy Center V5.0 Installation

D. Reversing the Disks

E. Disaster Recovery

E.1 Classical DPS7000/XTA .................................................................................................E-1 E.1.1 Incidents Concerning Software or Limited to Disk0...........................................E-1 E.1.2 Other Hardware Incidents..................................................................................E-4

E.2 1X4 DPS7000/XTA Models.............................................................................................E-4 E.3 X5 DPS7000 XTA Models...............................................................................................E-5 E.4 Novascale Models...........................................................................................................E-7 E.5 Partitions Shifts ...............................................................................................................E-8

F. Recommendations for Creating W2K Shared Disks

F.1 Requirements.................................................................................................................. F-1 F.2 Creating Partitions on W2K Disks on the First Server .................................................... F-2 F.3 Creating GCOS7 Disks on W2K Shared Disks............................................................... F-4 F.4 Recognizing the W2K Shared Disks on the Second Server........................................... F-5 F.5 GCOS7 Disks With Shared Mode and the V7000 Configurations.................................. F-5

G. RCF7 Configuration

Glossary

Index


xiv 77 A2 77US

Table of Graphics

Figure 1-1. Start Menu: Access to V7000 Tools................................................. 1-3 Figure 1-2. Key Evolutions................................................................................ 1-16 Figure 2-1. V7000 Configuration Description ..................................................... 2-3 Figure 2-2. V7000 Configuration Editor Home Page........................................ 2-12 Figure 2-3. V7000 Configuration Root Context Menu ...................................... 2-13 Figure 2-4. Selecting the V7000 Key................................................................ 2-14 Figure 2-5. Configuration via the New Command ............................................ 2-15 Figure 2-6. Configuration Editor Window after the Save Command ................ 2-16 Figure 2-7. Configuration Editor Window after Selection of the MMUs Node .. 2-16 Figure 2-8. Configuration Editor Window after Clicking the IOPs + ................. 2-17 Figure 2-9. Different Key Message................................................................... 2-18 Figure 2-10. Key Not Compatible Message........................................................ 2-18 Figure 2-11. Configuration Editor Window after an Open Command................. 2-18 Figure 2-12. Detailed Report after a Check Command ...................................... 2-20 Figure 2-13. End of the Warning Messages for the "Check" Command ............ 2-21 Figure 2-14. Saving Changes before a General Check Dialogue Box............... 2-22 Figure 2-15. Selecting the Global Information Node .......................................... 2-23 Figure 2-16. Global Information Node Context Menu......................................... 2-23 Figure 2-17. Global Information Properties: Key ................................................ 2-24 Figure 2-18. Global Information Properties: Key ................................................ 2-25 Figure 2-19. Selecting the CPUs Node .............................................................. 2-26 Figure 2-20. CPUs Node Context Menu............................................................. 2-26 Figure 2-21. Add CPUs Dialogue Box ................................................................ 2-27 Figure 2-22. Add a specific CPU Dialogue Box.................................................. 2-28 Figure 2-23. CPUs Node Properties................................................................... 2-28 Figure 2-24. IPxx Context Menu......................................................................... 2-29 Figure 2-25. IPxx Properties ............................................................................... 2-29 Figure 2-26. List of MUs in the Result Pane....................................................... 2-30 Figure 2-27. MMUs Node Context Menu............................................................ 2-31 Figure 2-28. Add MMUs Dialogue Box ............................................................... 2-31 Figure 2-29. MMUs Properties ........................................................................... 2-32 Figure 2-30. MUxx Context Menu....................................................................... 2-33 Figure 2-31. MUxx Properties............................................................................. 2-33 Figure 2-32. Selecting the IOP Node.................................................................. 2-35 Figure 2-33. Configuration Window after Expanding the IOPs Node

and Selecting IO03......................................................................... 2-35

Figures

77 A2 77US xv

Figure 2-34. Configuration Window after Selecting a PXU Node in the Scope Pane.................................................................................... 2-36

Figure 2-35. IOPs Node Context Menu .............................................................. 2-36 Figure 2-36. Add IOPs Dialogue Box ................................................................. 2-37 Figure 2-37. IOP Properties................................................................................ 2-38 Figure 2-38. IOxx Context Menu (Scope Pane) ................................................. 2-38 Figure 2-39. IOxx Context Menu (Result Pane) ................................................. 2-39 Figure 2-40. Add PXUs Dialogue Box ................................................................ 2-40 Figure 2-41. Delete IOP Confirmation Dialogue Box.......................................... 2-41 Figure 2-42. IOxx Properties............................................................................... 2-41 Figure 2-43. PXmn Context Menu ...................................................................... 2-42 Figure 2-44. Add controller(s) Dialogue Box ...................................................... 2-42 Figure 2-45. PXnm Properties ............................................................................ 2-43 Figure 2-46. Disk Controller Context Menu ........................................................ 2-44 Figure 2-47. Add a disk Dialogue Box ................................................................ 2-45 Figure 2-48. Disk Controller Properties .............................................................. 2-46 Figure 2-49. Tape Cartridge Controller Context Menu ....................................... 2-47 Figure 2-50. Add a Cartridge Dialog Box............................................................ 2-48 Figure 2-51 <Port Bus Target> or <WWPN> LUN Drive Type drop down list 2-50 Figure 2-52 Result pane showing the two addressing modes in the cartridges

configuration................................................................................... 2-50 Figure 2-53. Tape Cartridge Controller Properties ............................................. 2-53 Figure 2-54. Printer Controller Context Menu..................................................... 2-54 Figure 2-55. Printer Controller Properties........................................................... 2-55 Figure 2-56. Add a Printer Dialogue Box............................................................ 2-55 Figure 2-57. Add a PR800n Printer (with no IGP Card) ..................................... 2-57 Figure 2-58. Telecom Controller Context Menu ................................................. 2-58 Figure 2-59. Telecom Controller Properties (NCC) ............................................ 2-59 Figure 2-60. Disk Context Menu......................................................................... 2-60 Figure 2-61. Disk Properties ............................................................................... 2-61 Figure 2-62. Tape Cartridge Context Menu........................................................ 2-62 Figure 2-63. Tape Cartridge Features ................................................................ 2-62 Figure 2-64. Printer Context Menu ..................................................................... 2-63 Figure 2-65. Printer Properties ........................................................................... 2-64 Figure 2-66. Properties of a GCOS7 disk named MS01 in the Result Pane; this

disk is configured with the property Sharable=No. ........................ 2-66 Figure 2-67. Property page for the MS01 disk; the box “Disk sharable” is not

checked. ......................................................................................... 2-67 Figure 2-68. Property page for the MS01 disk; the box “Disk sharable” is

checked. ......................................................................................... 2-68 Figure 2-69. Properties of the GCOS7 disk named MS01 in the Result Pane; this

disk is now configured with the property Sharable=Yes. ............... 2-69 Figure 2-70. Adding a GCOS7 disk named MS02 by checking the “Disk Sharable”

box.................................................................................................. 2-69 Figure 2-71. Properties of the previous GCOS7 disks named MS01 and MS02 in

the Result Pane; these disks are now configured with the property Sharable=Yes................................................................................. 2-70

Figure 2-72. Property page for the GCOS7 disk named MSM1 when 56 disks are already configured with the property Sharable=Yes. ..................... 2-71

Figure 2-73. Default values of the “SharedDiskManager” tab ............................ 2-72 Figure 2-74. “SharedDiskManager” tab after providing values........................... 2-74


xvi 77 A2 77US

Figure 2-75. Result of the Check command (see Figure 2-76) .......................... 2-76 Figure 2-76. (With above figure). Result of the Check command when at least one

GCOS7 disk is configured and the values of the “SharedDiskManager” tab are not provided. ...................................................................... 2-76

Figure 2-77. Result of the Check command (see Figure 2-78) .......................... 2-77 Figure 2-78. (With above figure). Result of the Check command when

Sharable=No (Configuration) and Shared=Yes (Disk Manager) ... 2-78 Figure 2-79. Result of the Check command (see Figure 2-80) .......................... 2-78 Figure 2-80. (With above figure). Result of the Check command when

Sharable=Yes (Configuration) and Shared=No (Disk Manager) ... 2-79 Figure 3-1. GCOS7 Disk Implementation ........................................................... 3-3 Figure 3-2. Warning Message: Unauthorized Access ........................................ 3-5 Figure 3-3. Warning Message: Invalid Key......................................................... 3-5 Figure 3-4. GCOS7 Disk Manager Page Description......................................... 3-7 Figure 3-5. GCOS7 Restore Protection Confirmation Dialog Box...................... 3-7 Figure 3-6. No History Buffer Free Warning Message ..................................... 3-13 Figure 3-7. Disks Being Built Warning Message .............................................. 3-14 Figure 3-8. GCOS7 Disk Manager Home Page ............................................... 3-15 Figure 3-9. GCOS7 Disk Manager Home Page: CREATE............................... 3-16 Figure 3-10. Working Directory Selection Window............................................. 3-17 Figure 3-11. Incorrect Path Warning Message................................................... 3-18 Figure 3-12 . Window after Opening the Working Directory (no File Selected) .. 3-19 Figure 3-13. Window after Opening the Working Directory (File Selected) ....... 3-20 Figure 3-14. Existing File Warning Message...................................................... 3-21 Figure 3-15. Insufficient Disk Space Warning Message..................................... 3-21 Figure 3-16. Home Page During the Creation of a Disk..................................... 3-22 Figure 3-17. GCOS7 Disk Manager Home Page: RENAME.............................. 3-23 Figure 3-18. GCOS7 Disk Manager: RENAME.................................................. 3-24 Figure 3-19. Unknown File Warning Message ................................................... 3-25 Figure 3-20. File Open Warning Message.......................................................... 3-25 Figure 3-21. Access Denied or Write Protected File Warning Message ............ 3-26 Figure 3-22. Incorrect Control Area Warning Message...................................... 3-26 Figure 3-23. Home Page after Entering a New Valid File Name: RENAME ...... 3-27 Figure 3-24. Existent File Warning Message...................................................... 3-28 Figure 3-25. Home Page after Pressing RENAME ............................................ 3-29 Figure 3-26. GCOS7 Disk Manager Home Page: DELETE ............................... 3-30 Figure 3-27. Home Page after Selecting the File to Be Deleted ........................ 3-31 Figure 3-28. Delete Confirmation Dialogue Box................................................. 3-32 Figure 3-29. Home Page after Pressing the Yes Button .................................... 3-32 Figure 3-30. GCOS7 Disk Manager Home Page: MAKE UP............................. 3-33 Figure 3-31. MAKE UP File Selection Window................................................... 3-34 Figure 3-32. Home Page after Selecting the MAKE UP Files ............................ 3-35 Figure 3-33. MAKE UP Warning Message: File in Use...................................... 3-36 Figure 3-34. MAKE UP Warning Message: File Write Protected ....................... 3-36 Figure 3-35. MAKE UP Error Warning Message................................................ 3-36 Figure 3-36. History File Selection Window........................................................ 3-37 Figure 3-37. History File Specimen .................................................................... 3-38 Figure 3-38. GCOS7 Disk Manager version error message for Shared mode

definition. ........................................................................................ 3-40 Figure 3-39. GCOS7 Disk Manager page description with DEFINE SHARING and

DISPLAY functions (at utility startup)............................................. 3-41

77 A2 77US xvii

Figure 3-40. GCOS7 Disk Manager page description after clicking the DEFINE SHARING radio button................................................................... 3-42

Figure 3-41. GCOS7 Disk Manager page description after selecting the desired GCOS7 disk with the BROWSE button.......................................... 3-43

Figure 3-42. GCOS7 Disk Manager page description after answering Yes in the preceding Warning Dialog Box....................................................... 3-44

Figure 3-43. GCOS7 Disk Manager page description after clicking the DISPLAY radio button .................................................................................... 3-45

Figure 3-44. GCOS7 Disk Manager page description after selecting the desired GCOS7 disk using the BROWSE button ....................................... 3-46

Figure 3-45. Warning Dialog Box on RENAME command for a disk for which Shared mode is specified............................................................... 3-47

Figure 3-46. Warning Dialog Box on DELETE command for a disk for which Shared mode is specified............................................................... 3-48

Figure 3-47. Warning Dialog Box on MAKE UP command for a disk for which Shared mode is specified............................................................... 3-49

Figure 4-1. Start menu giving access to V7000 tools......................................... 4-1 Figure 4-2. Error message displayed when you are not allowed to use this tool4-2 Figure 4-3. Warning message displayed when you are allowed to use this tool 4-2 Figure 4-4. Main V7000 Information Collector Window...................................... 4-3 Figure 4-5. Collect complete window to save the compressed file. ................... 4-6 Figure 4-6. Collect complete window.................................................................. 4-8 Figure 4-7. Starting the Backup Utility .............................................................. 4-12 Figure 4-8. Backup Welcome Screen............................................................... 4-12 Figure 4-9. Backup File Selection Window....................................................... 4-13 Figure 4-10. Media Warning Message ............................................................... 4-14 Figure 4-11. Information on the Backup that Will Start....................................... 4-14 Figure 4-12. Backup Progress Window at the Start of the Backup .................... 4-15 Figure 4-13. Backup Progress Window at the End of the Backup ..................... 4-16 Figure 5-1 Key Manager Home Page....................................................................1 Figure 5-2 Key File Selection Browser ..................................................................2 Figure 6-1. Platform Identifier Home Page ......................................................... 6-1 Figure 6-2. Backup File Selection Browser ........................................................ 6-2 Figure 7-1. Alarm Transfer Configurator – Initial Display ................................... 7-2 Figure 7-2. Alarm Transfer Configurator – Example .......................................... 7-3 Figure 8-1. Trace Manager Home Page............................................................. 8-2 Figure 8-2. Trace Domains List Dialog Box (Trace not Active) .......................... 8-4 Figure 8-3. Domains List Dialog Box (Trace Active) .......................................... 8-5 Figure 8-4. Home Page: Select Trace Level ...................................................... 8-6 Figure 8-5. Home Page: Trace Active ................................................................ 8-8 Figure 8-6. Home Page: Trace Not Active.......................................................... 8-9 Figure 8-7. Trace Manager Already Launched Error Message........................ 8-10 Figure 8-8. Warning Message N° 1: No Domain Selected ............................... 8-10 Figure 8-9. Warning Message N° 2: No Level Selected................................... 8-10 Figure 9-1. Loading the Deploy Center 5.0 Tool ................................................ 9-6 Figure 9-2. Deploy Center 5.0 Menu .................................................................. 9-6 Figure 9-3. Tools Menu....................................................................................... 9-7 Figure 9-4. Selecting the Partitions to Delete ..................................................... 9-8 Figure 9-5. Confirming the Destruction of the Partitions .................................... 9-8 Figure 9-6. Situation after Destroying the Partitions........................................... 9-9 Figure 9-7. Selecting the Source Disk .............................................................. 9-10


xviii 77 A2 77US

Figure 9-8. Selecting the Partitions on the Source Disk................................... 9-10 Figure 9-9. Selecting the Target Disk ............................................................... 9-11 Figure 9-10. Selecting the Backup Space on the Target Disk............................ 9-12 Figure 9-11. Status of Information Collected ...................................................... 9-12 Figure 9-12. Copying the WIN2000 Partition...................................................... 9-13 Figure 9-13. Viewing the Results after Copying ................................................. 9-14 Figure 9-14. Details of the Target Disk after Copying ........................................ 9-14 Figure 9-15. Partition Resizing Options.............................................................. 9-16 Figure 9-16 Checking the Disable Information for the Second Internal Disk .... 9-18 Figure 9-17. Accessing NT Backup .................................................................... 9-20 Figure 9-18. NT Backup...................................................................................... 9-21 Figure 9-19. Parameter Selection....................................................................... 9-22 Figure 9-20. Suppress GCOS data in the backup structure............................... 9-23 Figure 9-21. Case with a Media Already Used................................................... 9-24 Figure 9-22. Requested Information................................................................... 9-24 Figure 9-23. First Confirmation for a Media Used .............................................. 9-25 Figure 9-24. Second Confirmation for a Media Used ......................................... 9-25 Figure 9-25. Backup Progress............................................................................ 9-25 Figure 9-26. End of Backup................................................................................ 9-26 Figure 9-27. Restore Menu Welcome Screen .................................................... 9-27 Figure 9-28. Replace Files Option...................................................................... 9-27 Figure 9-29. Selecting the Restoration Parameters ........................................... 9-28 Figure 9-30. Confirming the Restoration ............................................................ 9-28 Figure 9-31. 4mm Cartridge Load ...................................................................... 9-29 Figure 9-32. Progress of the Restoration ........................................................... 9-29 Figure 9-33. End of Restoration and Final Status .............................................. 9-30 Figure 9-34. Restart Request ............................................................................. 9-30 Figure 9-35 ServerRaid Manager tool ............................................................... 9-35 Figure 9-36 Disk resynchronisation progress.................................................... 9-36 Figure 10-1. Console Logon Window ................................................................. 10-5 Figure 10-2. Main Window: PowerChute® Business Edition Console................ 10-6 Figure 10-3. Battery Status menu in PowerChute® Business Edition ................ 10-7 Figure 10-4. Power Failure Menu in PowerChute® Business Edition................. 10-8 Figure 10-5. Agent Login Window .................................................................... 10-10 Figure 10-6. Main Window in PowerChute® Business Edition Agent............... 10-11 Figure 10-7. Event Actions Window ................................................................. 10-12 Figure 10-8. Menu for the Power Failed Event................................................. 10-13 Figure 10-9. Menu for the Power Restored Event ............................................ 10-14 Figure 10-10. Menu for the Time on Battery Threshold Exceeded Event .......... 10-15 Figure 10-11. System Shutdown Management Menu ........................................ 10-17 Figure 10-12. Error Message: Incorrect Parameter............................................ 10-18 Figure 10-13. Warning Message: V7000 System Control Not Started............... 10-18 Figure 10-14. Warning Message: V7000 Virtual Machine Not Running............. 10-18 Figure 10-15. Warning Message: GCOS7 Not Operational ............................... 10-19 Figure 10-16. Error Message: Internal Error....................................................... 10-19 Figure 11-1 Main window of V7000 Log Viewer Tool........................................ 11-2 Figure D-1. Opening the Disk Cover ...................................................................D-1 Figure D-2. Identifying Disk1 and Disk0..............................................................D-1 Figure E-1: BIOS Initialization tool for LSI MegaRAID........................................E-6 Figure F-1. Example of W2K Disks Access Paths after Server Reboot

(NB: Gcos_Disks Must Be Read Instead of GCOS_DISK).............. F-3

77 A2 77US xix

Figure F-2. Example of One 2GB GCOS7 Disk Named MSGM Created on a W2K Disk (NB: Gcos_Disks Must Be Read Instead of GCOS_DISK)...... F-4


xx 77 A2 77US

Table 1-1. Roles and Security Group Membership ............................................................ 1-5 Table 1-2. User Privileges (1/4) .......................................................................................... 1-6 Table 2-1. V7000 Resource Type and Family .................................................................... 2-8 Table 2-2. Potential V7000 Resources ............................................................................... 2-9 Table 2-3. Resource Limits ............................................................................................... 2-10 Table A-1. List of Disks Supported by V7000 and Corresponding Sizes............................A-8 Table B-1. V7000 Resource Type and Family ....................................................................B-2 Table B-2. External Identification of Controllers & Devices Connected to IO00 ................B-4 Table B-3. External Identification of Controllers & Devices Connected to IO01 ................B-5 Table B-4. External Identification of Controllers & Devices Connected to IO02 ................B-6 Table B-5. External Identification of Controllers & Devices Connected to IO03 ................B-7 Table B-6. External Identification of Controllers & Devices Connected to IO04 ................B-8 Table B-7. External Identification of Controllers & Devices Connected to IO05 ................B-9 Table B-8. External Identification of Controllers & Devices Connected to IO06 ..............B-10 Table B-9. External Identification of Controllers & Devices Connected to IO07 ..............B-11 Table E-1. Estimated Reconstruction Time / Elements ......................................................E-3

Tables

77 A2 77US 1-1

1. Introduction

The new range of DPS 7000 machines (DPS 7000/XTA) is built on an Intel® Architecture (IA) platform and is based on a series of BULL software components grouped under the name V7000 Virtual Machine, also called V7000 or V7000 VM in the present document.

V7000 comprises a kernel and installation and administration tools.

A V7000 platform is an IA machine running the Microsoft® Windows� operating system on which the V7000 virtual machine components have been installed, i.e. a DPS 7000/XTA.

NOTE: V7000 Operator’s Guide (47 A2 74US) describes V7000 operation.

V7000 Software Installation and Activation Guide (77 A2 88US) describes V7000 installation.

V7000 Configuration and Maintenance Guide (77 A2 77US) (the present guide) describes V7000 Virtual Machine administration tool use.

IMPORTANT: Administration tools are reserved for BULL Support technicians.

13

3


1-2 77 A2 77US

1.1 List of V7000 Tools Reserved for Bull Support Technicians

The V7000 platform Start Menu presents the following tools:

Configuration Editor to create and edit a V7000 configuration,

GCOS7 Disk Manager to create the various virtual disks used by GCOS7,

Information Collector to collect all the data required for V7000 maintenance,

Key Manager to install and check the hardware key for access to the V7000 platform,

Platform Identifier to establish platform identification and to calculate the V7000 platform hardware key,

V7000 Configuration Tool Alarm Transfer Configurator page: to set the

parameters required to transfer alarms to the Bull Support GTS Center,

MasterSlave Wait Time Configuration page: to set wait time for V7000 user status to become Master when Slave,

Trace Manager to activate / stop the trace in order to collect maintenance data,

Version Manager to activate another version of V7000.

Firewall Configuration to configure the native firewall for V7000, Interop7 and factory installed third party components,

Load Galileo Firmware to update firmware of Galileo directly from V7000 software,

V7000 Performance Log to audit DPS7000 XTA or Novascale 7000 Platforms performances with specific V7000 and Windows System counters,

Introduction

77 A2 77US 1-3

Figure 1-1. Start Menu: Access to V7000 Tools


1-4 77 A2 77US

Note:

- From this edition, a V7000 Log Viewer Tool is appended( See chapter 11). This tool views a log file named Bct-MergedV7000AndSystemLogFiles.log extracted from cabinet file (.cab) that is created by Information Collector tool or it can create, on a V7000 machine, a text formatted file whose contents are same as �Bct-MergedV7000AndSystemLogFiles� text formatted file.

- To start this tool, open a DOS window, and launch the file GUI_LogViewer.bat under the directory c:\Program Files\Bull\V7000\Component.

Whenever a tool is started, the following check is performed:

• Does the user belong to the V7000BullServices group?

If the answer is No, the tool is not started and the following message is displayed:

You are not allowed to use this tool

If the answer is Yes, the following Warning Message is displayed when the tool is started:

CAUTION: This tool is dedicated to BULL Support operation This message does not prevent use of the tool.

This check is carried out whether the tool is started from a V7000 platform or from a remote station.

Introduction

77 A2 77US 1-5

1.2 V7000 use and Administration: Rights and Security Groups

1.2.1 Rights

Certain actions can only be carried out if the operator has the appropriate rights. Windows™ establishes user rights per security group. GCOS7 establishes user rights per project.

The same user can play several roles and Windows™ allows each user to belong to several groups.

1.2.2 User Roles and Windows™ Security Group Membership

Table 1-1. Roles and Security Group Membership

Role Windows™ Security Group (Windows™) or GCOS7 Project

Membership

BULL Client

BULL Maintenance

W2K Administrator Member of the V7000 local platform Administrators group

Yes On request

V7000 / Interop7 Operator Member of the V7000 local platform V7000Operators group

Yes Yes, subject to authorization

V7000 / Interop7 Installation Member of the V7000 local platform Administrators group

Possible Yes

V7000 Tool User Member of the V7000 local platform V7000BullServices group

Possible Yes

Interop7 Tool User Member of the V7000 local platform V7000Operators group


GCOS7 Administrator Unknown to Windows™. Belongs to the GCOS7 SYSADMIN project

Yes On request

GCOS7 Operator Unknown to Windows™. Belongs to the GCOS7 OPERATOR project



1-6 77 A2 77US

1.2.3 Privileges Required for an ‘Action Launched by a User’

Unless stipulated otherwise, all the security groups indicated in the following table are local V7000 platform security groups:

Table 1-2. User Privileges (1/4)

User V7000 Action Launched by:

∀ Obtain the platform signature Launch the executable file: PlatformIdentifier_EXE or Start → Programs → V7000 → BULL Services → Platform Identifier

∀ Use the EventViewer to view logs

Computer → Manage → Events Select V7000 LNxx ou System

∀ Use the Service Control Panel Computer → Manage → Services

Populate the security groups Computer → Manage → Local Users & Groups

Shut down / Restart W2K Start → Shut Down

∈ Administrators Group

Install V7000 on the V7000 platform

Launch Setup from the V7000 installation CD-Rom

∈ Remote Station Administrators Group

Install a remote V7000 control station

Launch Setup from the V7000 installation CD-Rom

∈ Administrators and V7000BullServices Groups PROHIBITED otherwise

Remove a GCOS7 disk with the Explorer

Explorer, select MSxx file, then press the Delete key

∈ Administrators and V7000BullServices Groups

Change / activate the version of V7000 to be used

Start → Programs → V7000 → BULL Services → Version Manager

Introduction

77 A2 77US 1-7



Configure V7000 Start → Programs → V7000 → BULL Services → Configuration

Install a V7000 key Start → Programs → V7000 → BULL Services → Key Manager

Create / Rename / or Make-up a GCOS7 disk

Start → Programs → V7000 → BULL Services → Disk Manager

Remove a GCOS7 disk Start → Programs → V7000 → BULL Services → Disk Manager

Collect V7000 problem data Start → Programs → V7000 → BULL Services → Information Collector

Activate / Stop V7000 trace Start → Programs → V7000 → BULL Services → Trace Manager

Configure Alarm Transfer Start → Programs → V7000 → BULL Services → Alarm Transfer Configurator

∈ V7000 platform V7000BullServices Group

Use VMP Click the VMP icon

∈ V7000 Platform V7000Operators Group

Control V7000 from the DPS7000/XTA platform

Start → Programs → V7000 → System Control Start → Programs → V7000 → Operation Supervisor

∈ V7000 Platform V7000Operators GroupUser credentials (domain \ user name, password) are to be known to the V7000 platform

Control V7000 from a remote station

Start → Programs → V7000 → System Control Start → Programs → V7000 → Operation Supervisor then Connect to another computer

∈ V7000 Platform V7000Operators GroupUser credentials (domain \ user name, password) given in the Terminal Services Start window are to be known to the V7000 platform

Control V7000 from a remote station via Terminal Services

Σ all the options available for this group on the V7000 platform


1-8 77 A2 77US



∈ V7000 Platform V7000BullServices Group

Use the V7000 tools reserved for the V7000BullServices group on a remote station VIA Terminal Services

Σ all the options available for this group as described above

∈ Administrators Group

Install Interop7 on the V7000 platform

Launch Setup from the Interop7 installation CD-Rom

∈ Remote Station Administrators Group

Install a remote Interop7 control station

Connection to the Diane Server Interop7 Web Site via the Browser, then Download �

Configure Interop7 Editor: edits: FTP7 host files opengtw.ini OPENGTW file

Start → Programs → V7000 → Interop7 → ASCII-EBCDIC Conversion Table Management

Start → Programs → V7000 → Interop7 → Mailbox Configuration

Start → Programs → V7000 → Interop7 → Administration Servers

Control Interop7 gateways Start → Programs → V7000 → Interop7 → Administration Servers

Visualize the use of Interop7 gateways

Start → Programs → V7000 → Interop7 → NT7GW Server Start → Programs → V7000 → Interop7 → OpenGTW Server


Interop7 maintenance DOS Windows: HSL: ls_shmem.exe, ls_attach.exe, dl_shmem.exe

SOCKET:v7stat.exe, v7dbg.exe, v7dump.exe

Start → Programs → V7000 → Interop7 → Administration Servers (FTP trace)

Start → Programs → V7000 → Interop7 → NT7GW Server (trace)

Start → Programs → V7000 → Interop7 → OpenGTW Server (trace)

Introduction

77 A2 77US 1-9



Configure Interop7 from a remote station

Start → Programs → V7000 → Interop7 → ASCII-EBCDIC Conversion Table Management

Start → Programs → V7000 → Interop7 → Mailbox Configuration


Control Interop7 gateways from a remote station


Configure Interop7 from a remote station


Visualize the use of Interop7 gateways on a remote station

Start → Programs → V7000 → Interop7 → NT7GW Server

Start → Programs → V7000 → Interop7 → OpenGTW Server

∈ V7000 Platform V7000Operators GroupUser credentials (domain \ user name, password) are to be known to the V7000 platform

Interop7 maintenance from a remote station

Start → Programs → V7000 → Interop7 → Administration Servers (FTP trace)

Start → Programs → V7000 → Interop7 → NT7GW Server (trace)

Start → Programs → V7000 → Interop7 → OpenGTW Server (trace)


Administer Interop7 (installation +configuration + control + maintenance) from a remote station via Terminal Services

Σ all the Interop7 functions listed in this column

∀ means any ∈ means �belong to�


1-10 77 A2 77US

1.3 Using V7000 Tools

IMPORTANT: These tools are to be used when installing V7000 or an Upgrade, or when reporting a problem to the BULL Support Center.

The method recommended in this document is NOT the only method.

These tools are interactive (Cf. V7000 Installation and Activation Guide, 77 A2 88US).

These tools may only be used by a user belonging to the V7000 platform V7000BullServices group. Certain operations described in the following paragraphs require the user to also belong to the Windows� Administrators group.

The following descriptions are applicable to both local platform users and to users using Terminal Services from a remote station.

1.3.1 Complete Installation

The first installation described hereafter is made by manufacturing.

1. Check that the Username belongs to the platform Administrators group.

2. Get the platform identification (or signature) with the Platform Identifier:

− From the V7000 installation CD-Rom: Click on PlatformIdentifier_EXE.exe.

− Note the location of the resulting signature file: this signature file is to be input in the key generating tool at the Manufacturing Department.

3. Calculate the corresponding V7000 key (Init key): the signature file and the name of the DPS 7000 model to be installed are requested. An encrypted key file (extension: .g7k) is output with a text file of the same name (extension: .txt), enabling the visualization of system features:

− model and serial number, − maximum resource envelope (maximum number of IP, MU, IO, PX per

type and per device type). 4. Install V7000 from the CD-Rom: Cf. V7000 Software Installation and

Activation Guide, 77 A2 88US.

5. Place at least one user in the V7000BullServices security group and one in the V7000Operators group.

6. Finish the current session (Start ! Shut Down, then select Log off).

13

3

Introduction

77 A2 77US 1-11

7. Open another session with a Username belonging to the Administrators and V7000BullServices groups.

8. Activate the software version to be used with the Version Manager. (Cf. V7000 Software Installation and Activation Guide 77 A2 88US).

9. Close the current session (Start ! Shut Down then select Log off).

10. Open a new Windows� session under a Username belonging to the V7000BullServices group.

11. Install the key via the Key Manager. From the Start Menu, select: Start! V7000 ! BULL Services ! Key Manager. (Cf. Chapter 5).

12. Create the first configuration with the Configuration Editor.

− From the Start Menu, select: Start ! V7000 ! BULL Services ! Configuration Editor. Use the command New and select Installed Key (Cf. Chapter 2). A configuration is automatically generated with the default settings and the maximum value envelope licensed by the key

− Save this configuration under the name and in the directory you wish (Save as command) and leave this window open. You can also copy this configuration to the clipboard (Copy to Clipboard command) in order to edit it. Now, all GCOS7 configuration disks have a defined name.

13. Create a GCOS_Disks directory directly under a logical device name (e.g.: C: or F: etc) or under a disk folder name (Cf. Chapter 3). This directory will be used for the GCOS7 disk image.

14. Decompress the GCOS7 disk image contained on the GCOS7 CD-Rom by clicking on the autodezippable.exe file. In the Browse window, choose the GCOS_Disks directory defined in §13. The GCOS7 disk image is transferred to this directory under the name MS04 (2GB).

15. Rename this disk MS01 by launching the GCOS7 Disk Manager from the Start Menu: Start! V7000 ! BULL Services ! GCOS7 Disk Manager. Use the RENAME function. (Cf. Chapter 3).


1-12 77 A2 77US

1.3.2 Adapting the Configuration

The configuration created by manufacturing must be modified, on site, by Bull technicians to take into account the specific needs of the customer.

1. Create GCOS7 disks.

IMPORTANT: It is to be remembered that GCOS7 disks are seen as files under Windows�. The data on these disks is only accessible from GCOS7.

GCOS7 disks are created as follows:

− Create the GCOS_Disks directories on each of the Windows� logical volumes on which one or several GCOS7 disks are to be implemented. It is mandatory to create these directories under the root of each disk used to receive the GCOS7 disks. These roots are either letters followed by �:� or disk folder names.

− Launch the GCOS7 Disk Manager from the Start Menu: Start ! V7000 ! BULL Services ! GCOS7 Disk Manager

− Use the CREATE function (Cf. Chapter 3) to successively create all the disks required for GCOS7.

− Open the Configuration Editor window to get the list of the disk names to be created.

− Select location (Windows� logical volume and associated GCOS_Disks file) with the integrated Browser.

IMPORTANT: The Configuration Editor lists the maximum number of disks licensed by the key. It is not necessary to create all the disks. Just create the number of disks required.

The various GCOS_Disks directories can also be directly created via the GCOS7 Disk Manager Browser when creating a disk.

2. Finish configuration by returning to the corresponding window.

NOTE: Use Properties for all the following points (Cf. Chapter 2):

− for each disk (MSxx) created above: indicate its size and location (via the Browser).

13

3

13

3

Introduction

77 A2 77US 1-13

− for each telecommunications controller (UCx0): select the MAC address and complete the IP address field. The IP field is not functional. However, it will ease future DSA network generation (NetGen) under GCOS7.

− for each printer (PRxx): give the port, interface, model and speed.

− for each cartridge (CTxx=) : match with the physical device installed on the platform.

3. Save the edited configuration (Save command).

4. Check data validity (Check command).

− In the event of a Stop error � materialized by a white cross against a red background: correct the error, then save and check the configuration in compliance with the procedure described above.

− In the event of Warnings: read the warnings and if they seem �normal�, proceed as follows:

5. Activate the configuration (Activate command). The configuration is now set. Exit the Configuration Editor.

6. If the user does not belong to the V7000Operators group, close the current Windows� session (Start !Shut Down then Log off) and start another session with a user belonging to the V7000Operators group so that V7000 and GCOS7 can be started. Cf. V7000 Operator’s Guide (47 A2 74US).

7. Then launch the GCOS7 configuration job. Cf. GCOS7 System Installation Configuration and Updating Guide (47 A2 18US).

1.3.3 Upgrading a DPS 7000/XTA

1. Make the necessary platform hardware changes and start the system.

2. Open a Windows� session (CTRL+ALT+DEL then Log on) under a Username belonging to the V7000BullServices group.

3. Install the upgrade key with the Key Manager: Start! V7000 ! BULL Services ! Key Manager This key is supplied with the upgrade. It is automatically calculated and supplied by the Manufacturing Department in compliance with the new order and the previous key (saved in a database).

4. Create the new configuration from the previous configuration:

− Launch the Configuration Editor from the Start Menu: Start! V7000 ! BULL Services ! Configuration Editor


1-14 77 A2 77US

− Use the Open command, enter the name of the current configuration file and select Installed Key,

− If new disks are to be defined, they are to be created as set out in §1.3.1, − Define the new resources supplied with the upgrade as set out in § 1.3.1, − Save the edited configuration under another name (Save As command), − We recommend the use of the default V7000 trace directory:

Program Files\BULL\V7000\trace. − Check data validity (Check command),

In the event of a Stop error � materialized by a white cross against a red background: correct the error, then save and check the configuration in compliance with the procedure described above. In the event of Warnings: read the warnings and if they seem �normal�, proceed as follows:

− Activate the configuration (Activate command). The configuration is now set. Exit the Configuration Editor.

5. If the user does not belong to the V7000Operators group, close the current Windows� session (Start !Shut Down then Log off) and start another session with a user belonging to the V7000Operators so that V7000 and GCOS7 can be controlled. Cf. V7000 Operator’s Guide (47 A2 74US).

6. Then launch a GCOS configuration job. Cf. GCOS7 System Installation Configuration and Updating Guide (47 A2 18US).

1.3.4 Changing a Hardware Component

After the repair of a hardware component, check that it can be used under Windows�, independently of V7000. Cf. V7000 Evolution guide (47 A2 76US).

When a component is part of the central sub-system, there should be nothing to do at V7000 level provided that the component is replaced by an identical component snapped into the same location.

When the component is a device, V7000 configuration may have to be changed according to the device replaced:

• If the device is a telecommunications card, change the corresponding telecommunications controller MAC address (Ucx0) via the V7000 Configuration Editor (Cf. § 2.9.6.8).

• If the device is a cartridge driver, there should be nothing to do provided that the component is replaced by the same type of component. Should this not be the case, modify V7000 configuration (Cf. § 2.9.6.10).

Introduction

77 A2 77US 1-15

• If the device is a printer, check that it is connected to the same port and that the baud rate is the same. Should this not be the case, modify V7000 configuration (Cf. § 2.9.6.11).

CAUTION: In some cases, after changing a component, the hardware key migth become temporary. If so, you must compure the new �platform identifier� and ask for a new key.

1.3.5 Adding a Hardware Component

If a device is added, check correct operation under Windows� (Cf. V7000 Evolution Guide, 47 A2 76US) and modify V7000 configuration so that the device can be used under GCOS7 (Cf. Chapter 2).

1.3.6 Reconfiguring a Network Card

Network card properties must be compliant with corresponding equipment (hub, switch, router) characteristics. The DPS 7000/XTA Administrator may therefore need to change network card properties under Windows� for efficient network operation, e.g.: half-duplex / full-duplex connections on the same Ethernet link.

To change network card properties, the Windows� Administrator is to:

• Know the MAC address,

• Use the Configuration Editor to find out whether the card is used by GCOS7 (Cf. Chapter 2).

• If the card is not used by GCOS7, V7000 is not affected by changing card properties. If the card is used by GCOS7:

− Locate the OCSi server to be stopped via the following GCOS7 Operator commands:

S : DNET LPL CODE = LONG ⇒ (MAC addresses LCT) S : DTSVR CODE = LONG ⇒ (OCS servers LCT)

− Stop the server with the following GCOS7 command:

S : TTSVR OCS OCSi

− Change network card properties under Windows�,

− Restart the corresponding OCSi server via the GCOS7 command: S : STSVR OCS OCSi


1-16 77 A2 77US

1.4 V7000 Key

A unique key is associated with each DPS 7000/XTA. This key identifies and defines the machine. The resource envelope is subject to the model purchased. The resource envelope can only be extended by purchasing another model.

Each DPS 7000/XTA is delivered with a key called INIT Key. Key evolutions are explained in the following diagram:

t0 Running a first DPS 7000/XTA

t1 Change of a platform hardware component affecting the signature. A message is displayed in the SYC Activity History indicating that the key is now a Temporary Key.

t2 = t1 + 15 days: the key is now invalid and the V7000 system is shut down. Daily messages are edited throughout this fortnight, followed by hourly messages on the last day.

t3 < t2 BULL recalculates a new key. The new platform signature and the previous INIT Key, which are stored in the Manufacturing Department database are input in the key generating tool. The resulting UPDATE Key only differs from the INIT Key with regard to platform signature.

Delivery of a new DPS 7000/XTA model in the form of an Add-on or Upgrade

The key is calculated from the current key: UPDATE Key or INIT Key or UPGRADE Key. This key is stored in the V7000 key database managed by the Manufacturing Department.

Current Key (INIT,UPGRADE or UPDATE)

TEMPORARY Key:Valid for 15 days

INVALID Key

UPDATE Key

BULL

UPGRADE KeyBULL

Figure 1-2. Key Evolutions

Introduction

77 A2 77US 1-17

IMPORTANT: An UPDATE Key only differs from the previous key with regard to platform signature. The rest is identical.

An UPGRADE Key always has the same serial number as the previous key and platform identification is identical. At least one feature varies: • model name, • resource envelope.

In terms of configuration, a key is compatible with a previous key when the resource envelope defined for a given DPS 7000/XTA (same serial number) is the same or greater.

An UPDATE Key is ALWAYS compatible. An UPGRADE Key is only compatible when the resource envelope is the same or greater.

In the case of an Add-on with a non-compatible key, the entire configuration process is to be repeated since the envelope provided by the new key is smaller.

It is possible, for commercial purpose, to obtain a TEMPORARY KEY (for example, to test an upper model). The validity of such a key is limited to a certain amount of days.

13

3


1-18 77 A2 77US

77 A2 77US 2-1

2. V7000 Configuration Editor

The V7000 Configuration Editor is used to define the V7000 Virtual Machine configuration transmitted to GCOS7.

The resources (IP, IO, PX, controllers, devices, �) manipulated by the Configuration Editor are identical to previous DPS 7000 resources. The difference being that these resources can either be physical (IP, CT) or logical (disks), whereas previous resources were only physical.

The user is to be familiar with the DPS 7000 configuration tree. Should this not be the case, Cf. the SRST PA1586 Manual and Annex A to the present document.

The Configuration Editor operates as a text editor or spreadsheet on a workstation, allowing the creation of a new configuration or the modification of an existing configuration. The result is saved to a file in a directory selected by the user. The Configuration Editor is not a standard editor, it is based on the Windows™ Microsoft® Management Console (MMC), i.e. object Properties and Context Menus.

New functionalities of version V2 concerning the sharable disks are described in section 2.10.

2.1 Users

This tool is reserved for use by the BULL Support technician in charge of configuring a new DPS 7000/XTA or updating an existing configuration (Upgrade).

V7000 virtualizes most DPS 7000 resources, i.e. hardware components belonging to the Windows™ platform.


2-2 77 A2 77US

2.2 Tool Description

The Configuration Editor is a V7000 Support tool. It is not directly interactive with the V7000 Virtual Machine during operation.

The Configuration Editor is used BEFORE system operation. It can be run on the V7000 Windows™ platform or on any remote V7000 Windows™ station. It is used for the following functions:

• to describe V7000 configuration,

• to check this description with regard to the Windows™ resources on the platform,

• to activate the configuration, i.e. to save the configuration to be used at the next V7000 startup.

At V7000 startup, this file is used to create:

• the V7000 resource configuration tables required at system startup and for dynamic reconfiguration instructions,

• the SRST segment image located in the DPS 7000 memory.

The following diagram outlines V7000 configuration description:

V7000 Configuration Editor

77 A2 77US 2-3

Configuration file active

xx.g7c configuration file not valid

V7000 MEMORY

IOP

SYSTEM CONTROL(SYC)

CONFIGURATIONEDITOR

CONFIGURATIONEDITOR

HSLManager

CPUIOP

IOP

Windows Workstation :No access to the V7000 platform

Validation not possible

V7000 Platform

V7000 Key

Configuration tables + SRSTimage

Registry

V7000 KeyGCOS7 active configuration

check

V7000 Key

SRST

Activation of theconfiguration

Figure 2-1. V7000 Configuration Description


2-4 77 A2 77US

2.3 Configuration Editor Presentation

The V7000 Configuration Editor is an MMC Snap-in comparable to the other V7000 and Windows™ administration tools. The Configuration Tool is an easy-to-use tool requiring little training and extra investment.

The Configuration Editor console (MMC) is divided into two panes:

• the Scope Pane,

• the Result Pane.

The Scope Pane presents the list of hierarchized items managed by the Configuration Editor. This list is made up of nodes (Cf. § 2.5) associated with objects.

The operator can navigate in the Scope Pane to view the items in the hierarchized list. When a node is selected (left-click), the associated objects and their features are displayed in the Result Pane on the right.

The Result Pane display is in the form of a detailed report.

Context Menus are obtained by right-clicking the associated item. Only the actions authorized at the time of interaction can be selected via a Context Menu.

Each Context Menu is specific to the associated item. However, Properties can be selected in each Context Menu to display object Property Sheets.

Property Sheet Dialogue Boxes display item data and features. Various control boxes are available: Check Box, Edit Box, Drop-down List, �. Items may be updated by modifying the values and data displayed in the control boxes.


77 A2 77US 2-5

2.4 V7000 Configuration

Each configuration is created from the target V7000 system hardware key. This key authorizes the use of V7000 on a platform and describes the model and associated configuration envelope.

The Configuration Editor uses the maximum values described in the configuration envelope to build the configuration tree (allocation to PXUs and name selection).

The hardware key used to create the configuration is also to be supplied for updates and upgrades.

When working from a remote station, the operator is to be in possession of the V7000 system key (�.g7k� file). When working on the V7000 platform, the Installed Key is used.

Data supplied by the Key:

• Type of key: Init, Upgrade or Update,

• V7000 machine identification: model and serial number,

• Number of IPUs,

• Total memory size in MB,

• Number of IOPs,

• Number of disk PXUs and number of disks,

• Number of cartridge PXUs and number of cartridges,

• Number of NCC telecommunications PXUs,

• Number of LNM telecommunications PXUs,

• Number of printer PXUs and number of printers,

• Signature of the platform on which the V7000 machine is to be launched,

• Name of the partner system if disks are shared. Non-significant for the first version of V7000 installed.


2-6 77 A2 77US

2.5 Objects

With the Configuration Editor, the operator can build or update the list of hierarchized objects constituting the GCOS7 configuration.

Only downlevel V7000 virtual machine resources are associated with V7000 platform physical resources.

The operator manipulates objects or nodes. There are three types of nodes:

1. The root node (configuration type): data structure representing the configuration. This structure is stored in the �.g7c� file (Cf. 2-1).

2. Nodes representing a group of items of a given type, e.g.:

− a hardware component (processor, telecommunications line, cartridge drive�),

− a software component (virtual component seen by the V7000 virtual machine as a process, e.g. an IOP software dispatcher to the PXUs which, in turn, are process threads).

3. Group nodes or folders for improved hierarchization of list items and actions.

If the type of object is known to the Configuration Editor, the operator defines the occurrence rate for each type of object during the configuration session.


77 A2 77US 2-7

2.6 Hierarchization

The Configuration Editor manages a list of hierarchized objects.

Hierarchization is based on �dependency�, linking the occurrence of an A-type object and the occurrence of a B-type object, e.g.:

Case 1: �described”: • E.g.: between the occurrence of a V7000 configuration node and the occurrence

of a group node, i.e. the relationship between the root node and its immediate sons. A configuration comprises a CPUs node representing all the IP resources, a MMUs node, an IOPs node and a Global Information node.

• E.g.: between the occurrence of a group node and the occurrence of the corresponding nodes. The CPUs group node (CPUs Folder) describes CPU configuration, i.e. CPU sons (also called IP).

Case 2: �connected to”: • E.g.: a printer connected to a printer controller.

Case 3: �mapped in”: • E.g.: an IOP (Windows™ software process) allocating its I/O flows to its

immediate sons: PXUs, according to the I/O recipient device. Although �dependency� is intrinsic to MMC operation, the operator must select the occurrence rate for each type of node and assess its impact on machine rate.

2.7 Procedure

An object Context Menu (Cf. 2.3) displays the list of actions available for a given type of object. This list is expandable and guides the operator in his task.

The following procedure can be followed when creating a configuration from scratch:

• Select New in the V7000 Configuration object Context Menu,

• Enter the configuration Key,

• Check and edit the items not precisely defined by the Key (e.g.: disk size and location),

• Validate the definition with regard to the hardware resources available on the target platform,

• Save the result to a file,

• Check and activate the configuration for the next V7000 session.

This procedure is only an example. The operator is free to proceed as he wishes.


2-8 77 A2 77US

2.8 V7000 Configuration Resources

2.8.1 V7000 Resource Identification

External Ident is the GCOS7 name for V7000 platform resources.

The resource is known to GCOS7 under this name (e.g.: IP02, MSK4, MC01�) which is also used by the Configuration Editor.

This name or External Ident comprises 4 characters: • External Type: 2 characters (letters) defining the resource family (MS:disk, CT:

cartridge, MU: memory, �),

• External Name: 2 characters (letters or digits) identifying the resource within the family.

2.8.1.1 External Type

A V7000 configuration uses the following External Types. The shaded entries are not seen by the Configuration Editor since the corresponding resources are automatically generated in the SRST:

Table 2-1. V7000 Resource Type and Family

External Type Resource Family CP System Resource (Global Information) CT Cartridge Device EA Ethernet Adapter IO Input / Output Processor IP Instruction Processing LN Console Line LT Telecom Line MC Disk Controller MS Disk Device MU Memory Unit PC Input / Output Interface PR Printer Device PX Input / Output Module TC Cartridge Controller UC Printer Controller UC Network Controller UC Emulated Controller


77 A2 77US 2-9

2.8.1.2 External Name

This name is formed by the last 2 characters. It identifies the resource within its family. It is generated by the Configuration Editor: 32 (10 + 22) possible characters and 32*32 = 1024 combinations. (Cf. Appendix B).

The Configuration Editor generates a unique External Name for each device, without taking the resource families into account (except LTxx Telecom Lines).

The list of possible External Names for V7000 devices, according to their PCLC, is given in Appendix B.

2.8.2 Potential V7000 Resources

Table 2-2. Potential V7000 Resources

Model Name

External Ident.

Comments

90xx CP01 Model 90 system resource: xx = sub-model (numeric value) CONS LNxx xx ∈ (02, 03, 04) GCOS7 Consoles CPM-V7 UCxx Printer Controller: x digit / letter CTC-V7 TCxx Tape Cartridge Controller: x digit / letter CT-V7 CTxx Cartridge: x digit / letter ELT LTxx Ethernet Terminator: x digit EMU-V7 UCxx GCOS7 Console Emulated Controller ETHA EAxx Ethernet Adapter FSA MSxx Disk: x digit / letter IO-V7 IO0x IOP: x decimal digits (00 <= xx =< 07) IP-V7 IPxx CPU: x decimal digits (00 <= xx =< 23) LNM-V7 Ucx0 LNM Network Controller: x digit MEM-V7 MU0x Memory Unit: x decimal digits (00 <= xx =< 07) MSP-V7 MCxx Mass Storage Controller: x digit / letter NCC-V7 Ucx0 NCC Network Controller: x digit PR90 PRxx Printer: x digit / letter PSI-V7 PCxx Physical Channel Unit: xx hexadecimal digits (xx=< x�FD�) PXD-V7 PXxx Disk PXU: xx octal digits (00 <= xx =< 77) PXL-V7 PXxx Network LNM PXU: xx octal digits (00 <= xx =< 77) PXN-V7 PXxx Network NCC PXU: xx octal digits (00 <= xx =< 77) PXP-V7 PXxx Printer PXU: xx octal digits (00 <= xx =< 77) PXT-V7 PXxx Tape Cartridge PXU: xx octal digits (00 <= xx =< 77) RMSC LN06 RMS Transfer Interface between GCOS7 and the SAM TDEV LN07 Date and Time plus variance

V7000 resource not seen by the Configuration Editor


2-10 77 A2 77US

Table 2-2 lists potential V7000 resources, classified by model name.

Appendix A describes SRST data and the data seen by the Configuration Editor.

The terms used below are PA1586 terms (SRST Entry Standard) and take DPS 7000/XTA features into account.

2.8.3 Resource Limits

As is the case for ARTEMIS, there can only be 8 IOPs per system, each with a maximum of 8 PXUs.

V7000 sets specific limits for each type of PX. These limits are given in the following table:

Table 2-3. Resource Limits

PX Type PX Model Maximum Number of Controllers per PX

Maximum Number of Devices per Controller

Disk PXD-V7 4 4

Telecom PXL-V7 1 16

Telecom PXN-V7 1 12

Printer PXP-V7 4 4

Cartridge PXT-V7 4 4

IMPORTANT: There can be one PXL-V7 per V7000 VM and up to four PXN-V7.

PX number 77 is a special case. If it is not a telecom PX, it can only contain 2 controllers.

13

3


77 A2 77US 2-11

2.9 Configuration Editor Commands

Each Context Menu contains the associated object commands. System configuration data is divided into 4 categories:

• Global Information

• IPUs (Instruction Processors)

• MMUs (Memories)

• IOPs (Input / Output Processors)

The following icons are used in the various displays:

represents the Global Information node

represents the CPUs node

represents the MMUs node

represents the IOPs node

represents a disk controller

represents a printer controller

represents a cartridge controller

represents an NCC telecom controller

represents an LNM telecom controller

represents a disk PXU and a disk

represents a printer PXU and a printer

represents a cartridge PXU and a cartridge

represents an NCC telecom PXU and an ELT line connected to an NCC telecom controller

represents an LNM telecom PXU and an ELT line connected to an LNM telecom controller.


2-12 77 A2 77US

2.9.1 Configuration Editor Home Page

Start the Configuration Editor via the Start Menu:

Start -! Programs ! V7000 ! BULL Services ! Configuration

Figure 2-2. V7000 Configuration Editor Home Page

The standard Home Page opens. A configuration session is not underway. The V7000 Configuration root is selected.


77 A2 77US 2-13

2.9.2 V7000 Configuration Root Context Menu

Right-click V7000 Configuration to display the standard Configuration Editor Context Menu:

Figure 2-3. V7000 Configuration Root Context Menu

In addition to the menu items supplied by the MMC (View, Refresh, Export List), the V7000 configuration root Context Menu allows the user to create a new configuration (New) or to open an existing configuration file for modification (Open). Non-significant actions are shaded (as is the case for all Context Menus).


2-14 77 A2 77US

2.9.2.1 New Command

The first Dialogue Box asks whether the operator wants to use the Installed V7000 Key or an External Key (i.e. to prepare the configuration of another system):

Figure 2-4. Selecting the V7000 Key

Working with the installed key means that the configurator is run on the machine for which the configuration is created. In this case, the check (2.9.2.4) and activation (2.9.2.5) commands are authorized.

When External Key is checked and validated by OK, a Dialogue Box opens so that the operator can indicate the path and the name of the file containing the description of the key to be used. In this case, the configuration editor is able to determine whether it is executed on the DPS7000 / XTA machine corresponding to this key, or on another machine. The configuration control (2.9.2.4) will only be proposed if the configuration editor is executed on the target machine. The configuration activation command (2.9.2.5 ) is always disabled when working with an external key.

The Configuration Editor defines a V700 configuration which includes all the resources of the envelope associated with the key. The operator will have to edit this configuration, especially at I/O level, since the characteristics of each one need to be specified.


77 A2 77US 2-15

The values of the key used to generate the examples given in the present chapter are the following:

V7000 machine identification: model and serial number 9007 5061 Number of IPUs: 2 Total memory size in MB: 1024 Number of IOPs: 6 Number of disk PXUs and number of disks: 15 120 Number of cartridge PXUs and number of cartridges: 2 20 Number of NCC telecom PXUs and number of LTs: 4 48 Number of LNM telecom PXUs and number of LTs: 1 16 Number of printer PXUs and number of printers: 2 8

Figure 2-5. Configuration via the New Command

Right-click the Scope Pane to display the Context Menus:

IMPORTANT: Once the configuration has been saved, V7000 Configuration: New is replaced by V7000 Configuration: config-name (the file to which the configuration was saved being called config-name.g7c) (Cf. Figure 2-6).

13

3


2-16 77 A2 77US

Figure 2-6. Configuration Editor Window after the Save Command

In the example above, the configuration was saved to the file named: 50610001-Init.g7c.

If the Global Information, CPUs and MMUs + is clicked, nothing will appear below these nodes in the Scope Pane since these nodes have no associated sons. If one of these nodes is selected, the corresponding terminal items are displayed in the Result Pane.

Figure 2-7. Configuration Editor Window after Selection of the MMUs Node


77 A2 77US 2-17

If the IOPs + is clicked, the list of the IOs in the configuration is displayed below the node in the Scope Pane: the first level of the I/O tree.

Figure 2-8. Configuration Editor Window after Clicking the IOPs +

If the one of the Global Information, CPUs, MMUs or IOPs items is right-clicked, the corresponding Context Menu appears.

2.9.2.2 Open Command

A Dialogue Box appears requesting the configuration file name (xxxx.g7c) and access path. A standard Browse command may be used to locate this file.

Click OK. A Dialogue Box asks which key is to be used:

• if configuration is being performed on the platform, select: Installed Key,

• if configuration is being performed on a remote station or server, select: External Key.

Indicate the path and the name of the xx.g7k file containing the V7000 system key.


2-18 77 A2 77US

When a configuration file is opened with a different key from the one last used, the following message is displayed:

Figure 2-9. Different Key Message

Click OK and check that the new key is compatible with the key used previously. If the key is not compatible, the following message is displayed:

Figure 2-10. Key Not Compatible Message

If the key is compatible, the following window appears (here the file name is: 50610001-Init.g7c).

Figure 2-11. Configuration Editor Window after an Open Command


77 A2 77US 2-19

2.9.2.3 Save Commands

After creating a configuration or opening an existing configuration, use the Save or Save as command to save the configuration. According to the context, a Dialogue Box appears prompting the user to indicate the configuration file name (.g7c) and access path. Cf. Figure 2-6

2.9.2.4 Check Command

The Check command is used to check that declared GCOS7 resources are compatible with the Windows™ platform in question:

• sufficient number of CPUs, memory size with regard to hardware configuration,

• existence of disk files, telecom cards with MAC addresses, cartridge unit attributes, printer ports and attributes, �

Once this general check has been carried out, a detailed report is displayed in a specific window.

Two types of messages are displayed in this window:

• Error messages: the configuration cannot be activated,

• Warning messages: certain items are absent or incomplete, but V7000 can be activated.


2-20 77 A2 77US

The Check command can only be used from the target platform by selecting Installed Key.

Figure 2-12. Detailed Report after a Check Command

In the example, the Error messages indicate that:

• The MAC address related to telecom controller UC30 in PX33, is incorrect and does not fit with the MAC address of the telecom board dedicated to GCOS7. In this case the user has to modify this MAC address in the property sheet of the UC30 controller.

In the example, the Warning messages indicate that:

• the number of CPUs defined in the V7000 configuration is not compliant with the number of CPUs actually present on the platform,

• disk MS01 does not exist (Cf. § 3.5).

• the size of disks MS02 is incorrect,

The window below shows the end of this example's warning messages.


77 A2 77US 2-21

Figure 2-13. End of the Warning Messages for the "Check" Command

• the MS04 disk does not exist because there is no NTFS file with this name in the tree structure given.

• the next two messages concern the cartridge drives (CTD9 and CTDA) which have been defined in the configuration and which are missing or have been disconnected from the server, as a result of the check.

• the last message concerns the PR13 printer which is described in the configuration but for which no parameters have been defined (see the "Add Printer" command).

IMPORTANT: IPxx: PXxx: MCxx: MSxx Sharing Violation Warning messages indicate that certain items of the configuration to be validated are being used. These messages may appear when V7000 is active.

When there are only information messages, the window contains a yellow triangle with an exclamation mark in place of the white cross on the red circle.

The Check command is not available if the configuration has not been saved to a file or if an item has been modified since the last backup. In this case, a Dialogue Box prompts the operator to perform a backup before carrying out a general check.

13

3


2-22 77 A2 77US

Figure 2-14. Saving Changes before a General Check Dialogue Box

2.9.2.5 Activate Command

The Activate command can only be used when no errors were detected during hte general check. The current configuration is then used at the next V7000 startup.

The Activate command can only be used from the target platform by selecting Installed Key.

2.9.2.6 Copy to Clipboard Command

The Copy to Clipboard command is used to place the configuration image (containing the configuration tree and resources) in the Clipboard. The image is in txt format and is to be pasted in a text editor (Notepad / Wordpad / Word) for printing.


77 A2 77US 2-23

2.9.3 Global Information

2.9.3.1 Selecting Global Information

When the Global Information node is selected, data concerning the configuration and the key are displayed in the Result Pane.

Figure 2-15. Selecting the Global Information Node

Right-click an item in the Result Pane to get the Global Information Context Menu (also obtained by right-clicking Global Information in the Scope Pane.

2.9.3.2 Global Information Context Menu

The Global Information Context Menu is the following (obtained in the example by right-clicking the Global Information node in the Scope Pane).

Figure 2-16. Global Information Node Context Menu


2-24 77 A2 77US

Select Properties. The Key and Configuration tabs appear.

"Key" gives

• the model,

• the serial number,

• the location of the key file used. When working on a DPS7000 XTA with the installed key, only the "Installed key" key identification is given.

The "Key" tab is displayed by default.

Figure 2-17. Global Information Properties: Key


77 A2 77US 2-25

The "Configuration" tab displays the number of elements in the current configuration and the maximum values authorized by the key.

It is thus easy to compare the configuration description with the limits authorized by the key.

Figure 2-18. Global Information Properties: Key


2-26 77 A2 77US

2.9.4 CPUs (Processors)

2.9.4.1 Selecting the CPUs Node

The list of V7000 CPUs, called IPxx as on a standard DPS 7000, is displayed in the Result Pane.

Figure 2-19. Selecting the CPUs Node

Right-click an IPxx item in the Result Pane to get an IPxx Context Menu.

2.9.4.2 CPUs Context Menu

Right-click CPUs in the Scope Pane to get the CPUs node Context Menu:

Figure 2-20. CPUs Node Context Menu


77 A2 77US 2-27

If the configuration already contains the maximum number of CPUs authorized by the key, Add CPUs is shaded and cannot be activated.

If this is not the case, click Add CPUs to get the window indicating the current number of CPUs in the configuration and the maximum number authorized by the key.

This data is displayed in a Dialogue Box allowing:

• the addition of a set of CPUs ( giving a number of CPU).

• the addition of a specific CPU ( giving a CPU name),

Figure 2-21. Add CPUs Dialogue Box

Add a set of CPUs is the default option. The default value is 1, but can be modified according to the number authorized by the key. CPUs are named from the lowest non-allocated number.


2-28 77 A2 77US

Figure 2-22. Add a specific CPU Dialogue Box

If Add a specific CPU is selected, CPU names are displayed in the Dropdown Menu.

Properties displays CPUs features (number of CPUs defined in the configuration and maximum number of CPUs authorized by the key). This window cannot be used to modify the number of CPUs.

Figure 2-23. CPUs Node Properties


77 A2 77US 2-29

2.9.4.3 IPxx Context Menu

Right-click an IPxx item in the Result Pane to get the IPxx Context Menu:

Figure 2-24. IPxx Context Menu

Delete removes the selected item.

Properties displays item features in a Dialogue Box.

Figure 2-25. IPxx Properties


2-30 77 A2 77US

2.9.5 MMUs (Memories)

2.9.5.1 Selecting MMUs

Select MMUs in the Scope Pane.

Figure 2-26. List of MUs in the Result Pane

Right-click MMUs in the Scope Pane to get the MMUs Context Menu.

Right-click an MUxx item in the Result Pane to get the MUxx Context Menu.


77 A2 77US 2-31

2.9.5.2 MMUs Context Menu

Right-click MMUs to get the corresponding Context Menu:

Figure 2-27. MMUs Node Context Menu

Add MMUs� displays the following Dialogue Box:

Figure 2-28. Add MMUs Dialogue Box


2-32 77 A2 77US

Add a set of MMUs is the default option. In this example, the default number is 1. If the configuration already contains the maximum number of MMUs, the first field will be shaded.

If Add a specific MMU is selected, MMUs are named from the lowest available number (e.g; MU07 in an 8-MMU maximum configuration �in which MU00 to MU06 already exist).

Properties displays MMUs node features (number of MMUs defined in the configuration, total memory size, �). This window cannot be used to modify the number of MMUs.

Figure 2-29. MMUs Properties


77 A2 77US 2-33

2.9.5.3 MUxx Context Menu

The MUxx Context Menu is the following:

Figure 2-30. MUxx Context Menu

Delete removes the selected item,

Properties displays MU features.

Figure 2-31. MUxx Properties

IMPORTANT: The size of all memories is 128 Mo. Memory size cannot be modified.

13

3


2-34 77 A2 77US

2.9.6 IOPs (Input / Output Processors)

Right click on a node in the Scope Pane or result pane to display:

• the IOPs Context Menu,

• the IOxx Context Menu,

• the PXmn Context Menu,

• a Disk Controller Context Menu,

• a Disk Context Menu ,

• a Printer Controller Context Menu,

• a Tape Cartridge Controller Context Menu,

• a Telecom Controller Context Menu (NCC and LNM),

• a Printer Context Menu,

• a Cartridge Drive Context Menu,

• a Telecom Line Context Menu.

The tree level display and expansion process is the following:

− when a node is selected, the next level of associated items is displayed in the Result Pane,

− when + is clicked, the next level of associated items is expanded in the Scope Pane and the + is replaced by a �. When the last level is reached, the +can no longer be clicked,

− when �. is clicked the related lowest levels are masked.

− when an item in the Result Pane or in the Scope Pane is right-clicked, the corresponding item Context Menu is displayed.


77 A2 77US 2-35

2.9.6.1 Selecting IOPs

Figure 2-32. Selecting the IOP Node

Figure 2-33. Configuration Window after Expanding the IOPs Node and Selecting IO03


2-36 77 A2 77US

Figure 2-34. Configuration Window after Selecting a PXU Node in the Scope Pane

2.9.6.2 IOPs Context Menu

The IOPs node Context Menu is the following:

Figure 2-35. IOPs Node Context Menu

If the configuration already contains the maximum number of IOPs, Add IOP(s) is shaded.


77 A2 77US 2-37

Add IOPs displays the following Dialogue Box:

Figure 2-36. Add IOPs Dialogue Box

Add a set of IOPs is the default option. It allows the addition of a set or IOPs. The default number of IOPs to be added is 1. The displayed value can be increased and / or decreased by clicking the arrows, remaining within the envelope defined by the key.

When Add a specific IOP is selected, the user chooses a name from the list of the authorized IOPs in the Dropdown Menu.

Properties displays IOPs node features (number of IOPs defined in the configuration �). This window cannot be used to modify the number of IOPs.


2-38 77 A2 77US

Figure 2-37. IOP Properties

2.9.6.3 IOxx Context Menu

Right-click IOxx in the Scope Pane or in the Result Pane to display the IOxx Context Menu:

Figure 2-38. IOxx Context Menu (Scope Pane)


77 A2 77US 2-39

Figure 2-39. IOxx Context Menu (Result Pane)

Add PXUs allows the addition of one or several PXUs in compliance with the procedure described for CPUs in 2.9.4.2. PXU type can be selected. This Dialogue Box also indicates the current number of PXUs and the maximum number authorized by the key.


2-40 77 A2 77US

Figure 2-40. Add PXUs Dialogue Box

Add a set of PXUs is the default option with a default value of 1. PXUs are named in sequence from the lowest free number in the authorized envelope.

When the Add a specific PXU option is selected, the user chooses a name from the list of PXUs authorized for the IOP concerned.

When Delete is selected, a confirmation Dialogue Box is displayed.

CAUTION: The deletion of an IOP results in the deletion of the associated PXUs, controllers and any devices with this IOP in their path.


77 A2 77US 2-41

Figure 2-41. Delete IOP Confirmation Dialogue Box

Properties displays IOxx features (IOP name). This window is for guidance only. The features displayed cannot be modified.

Figure 2-42. IOxx Properties


2-42 77 A2 77US

2.9.6.4 PXmn Context Menu

Right-click PXmn in the Scope Pane or in the Result Pane to display the PXmn Context Menu:

Figure 2-43. PXmn Context Menu

When the PXU contains all the authorized controllers the command Add controller(s) is shaded. Add controllers� displays the following Dialogue Box:

Figure 2-44. Add controller(s) Dialogue Box


77 A2 77US 2-43

Add a set of CTRL(s) is the default option (1)

When the user selects Add a specific CTRL, the Configuration Editor prompts the first suitable name available.

IMPORTANT: Telecom controller settings are accessed by selecting Properties in the specific telecom controller context menu (Cf. 2.9.6.8).

• When Delete is selected, a confirmation Dialogue Box is displayed (as for IOPs).

CAUTION: The deletion of a PXU results in the deletion of the associated controllers and devices with only one path.

• Properties displays PX features (PX name and model, number of controllers).

The features displayed cannot be modified.

Figure 2-45. PXnm Properties

13

3


2-44 77 A2 77US

2.9.6.5 Disk Controller Context Menu

The Disk Controller Context Menu is the following:

Figure 2-46. Disk Controller Context Menu

In this example, Add a disk is shaded, i.e. the controller is already managing 4 disks or the total number of disks defined by the configuration is already reached.


77 A2 77US 2-45

Select Add a disk to add a disk to this controller. The following Dialogue Box is displayed:

Figure 2-47. Add a disk Dialogue Box

The name of the disk is prompted by the Configuration Editor according to the PCLC selected. A Dropdown list allows the user to select disk size in GB (2, 4, 8 or 9) and Browse allows the user to give the path and name of the file representing the GCOS7 disk.

The Browser can only be used from the target platform.

• When Delete is selected, the controller is removed. A Confirmation Dialogue Box is displayed. If the user confirms this choice, all the disks associated with this controller will be removed if they only have one path.

• Properties displays controller features (controller name and model, physical name (PCLC), brother controller name and PCLC, if applicable.


2-46 77 A2 77US

Figure 2-48. Disk Controller Properties

Only the Brother Controller field can be modified in this window.

Disks with 2 paths are defined by completing this field. This field is only accessible for disk controllers.

This option is used for protection against V7000 software crashes: two PX threads in two different IO processes manage access to the same disk. The unexpected disappearance of one of these threads or processes does not result in the non-availability of the GCOS7 disk. However, more system processes are used.

Delete is shaded in the controller context menu when this controller has a brother.

IMPORTANT: Only use on extensive, multiprocessor DPS 7000/XTA machines.

13

3


77 A2 77US 2-47

2.9.6.6 Tape Cartridge Controller Context Menu

The Tape Cartridge Controller Context Menu is the following:

Figure 2-49. Tape Cartridge Controller Context Menu


2-48 77 A2 77US

• When Add a Cartridge is selected, the following Dialog Box is displayed:

Figure 2-50. Add a Cartridge Dialog Box

There are three parameters to be entered in 3 drop-down lists:

• GCOS7 Type from among the following list:

M6 / 36T / M5

• SCL/Lib from among the following list:

Not defined / SCL / Lib

• The following rules apply between GCOS7 Type / Data Compaction / Density Type / SCL/Lib parameters:


77 A2 77US 2-49

Table 2-4. GCOS7 Type / Data Compaction / Density Type / SCL/Lib relations

GCOS7 Type Data Compaction Density Type SCL/Lib

M6 No S35/S75 Not defined / SCL

M5 Yes Not defined Not defined / SCL / Lib

36T Yes Not defined Not defined / SCL / Lib

• <Port Bus Target> or <WWPN> LUN Drive Type

See the following paragraph �WWPN vs SCSI addressing mode� below for details.

WWPN vs SCSI addressing mode

From V4.9 version of V7000 and Windows 2003 SP1, cartridges may be addressed by two ways :

" <Port Bus Target> LUN : already existing addressing mode for SCSI Connection only

" <WWPN> LUN : new addressing mode for Fiber Connection only WWPN means World Wide Port Name and is under the form: NN:NN:NN:NN:NN:NN:NN:NN where N is a hexadecimal digit.

The goal of the new WWPN addressing is to make the V7000 configuration independent from the SCSI address (Port Bus Target) modifications. The WWPN identifies the sub-system where the tape drive is connected, and not the path in terms of (Port Bus Target) to access it.

When a new V4.9 V7000 configuration is created:

" the <Port Bus Target> LUN addressing mode is necessarily used if the cartridge drive is connected through SCSI direct

" the <WWPN> LUN addressing mode is necessarily used if the cartridge drive is connected through Fiber Channel

In the following Add a cartridge dialog box (Figure 2-51), two cartridges are found on the system:

" the first one is connected through Fiber Channel, and thus addressed with <WWPN> LUN


2-50 77 A2 77US

" the second one is connected through SCSI direct, and thus addressed with <Port Bus Target> LUN

The Figure 2-52 shows the result pane after the two founded cartridges have been configured.

Figure 2-51 <Port Bus Target> or <WWPN> LUN Drive Type drop down list

Figure 2-52 Result pane showing the two addressing modes in the cartridges configuration


77 A2 77US 2-51

When a V4.9 V7000 configuration is opened, the following steps are recommended:

" check the V7000 configuration using the Check command

" modify the V7000 configuration in relation with the warning messages (if any) concerning the addressing mode of the cartridge devices.

When a pre-V4.9 V7000 configuration is opened, the following steps are recommended:

" save it into a new V4.9 V7000 configuration using the Save As� command by giving a new name; thus, the pre-V4.9 V7000 configuration file is kept unchanged. This step is necessary if the pre-V4.9 is re-activated.

" check then the new saved V4.9 V7000 configuration using the Check command

" modify the V7000 configuration in relation with the warning messages (if any) concerning the addressing mode of the cartridge devices.

The warning messages resulting from the Check command and concerning the addressing mode of the cartridge devices are the following:

1. IOxx:PXyy:TCzz:CTww: <Port Bus Target> or <WWPN>, LUN and Type <WWPN> <LUN> <DriveType> : This device should be configured with the new corresponding WWPN

2. IOxx:PXyy:TCzz:CTww: <Port Bus Target> or <WWPN>, LUN and Type <WWPN> <LUN> <DriveType> : This device should be configured with the corresponding (Port Bus Target) SCSI address (if defined on the system)

3. IOxx:PXyy:TCzz:CTww: <Port Bus Target> or <WWPN>, LUN and Type <Port Bus Target> <LUN> <Dive Type> : This device should be configured with the corresponding WWPN if connected on FiberChannel or with the new (Port Bus Target) SCSI Address (if defined on the system)

4. IOxx:PXyy:TCzz:CTww: <Port Bus Target> or <WWPN>, LUN and Type <Port Bus Target> <LUN> <Dive Type> : This device should be configured with the new (Port Bus Target) SCSI address (if defined on the system)


2-52 77 A2 77US

Case 1: The cartridge has already been configured with the WWPN addressing mode (the configuration was made from V4.9), but this WWPN has changed (the sub-system where the tape drive is connected has physically changed). Thus, it is recommended to configure it with the new corresponding WWPN, else the cartridge wont be accessible from GCOS7.

Case 2: The cartridge has been configured with the WWPN addressing mode (the configuration was made from V4.9), but is connected now through SCSI direct and no more through Fiber Channel. Thus, it is recommended to configure it with the corresponding (Port Bus Target) SCSI address, else the cartridge wont be accessible from GCOS7.

Case 3: The cartridge has been configured with the (Port Bus Target) addressing mode (the configuration was made from V4.9 or pre-V4.9):

" If the cartridge is connected through Fiber Channel, it is recommended to configure it with the corresponding WWPN. Nevertheless, the cartridge will be accessible from GCOS7 if the (Port Bus Target) address is still valid.

" If the cartridge is connected through SCSI direct, this (Port Bus Target) SCSI address is no more present on the system. Thus, it is recommended to configure it with the new (Port Bus Target) SCSI address, else the cartridge wont be accessible from GCOS7.

Case 4: The cartridge has been configured with the (Port Bus Target) addressing mode (the configuration was made from V4.9 or pre-V4.9), but this (Port Bus Target) SCSI address is no more present on the system. Thus, it is recommended to configure it with the new (Port Bus Target) SCSI address , else the cartridge wont be accessible from GCOS7 (NB: no cartridge is connected through Fiber Channel on the system).


77 A2 77US 2-53

• When Delete is selected, the controller is removed. A confirmation Dialog Box is displayed. If the user confirms this choice, all the associated cartridge drives will also be removed.

• Properties displays controller features (controller name and model, (PCLC)).

Figure 2-53. Tape Cartridge Controller Properties

The features displayed cannot be modified.


2-54 77 A2 77US

2.9.6.7 Printer Controller Context Menu

The Printer Controller Context Menu is the following:

Figure 2-54. Printer Controller Context Menu

The "Add Printer" command is described below.

IMPORTANT: Selecting Delete effectively deletes the controller. The user is prompted to confirm. If the user chooses Yes, all the printers dependent on the controller are also deleted.

Selecting Properties displays the controller's characteristics (name and model, Physical Name (PCLC)).

13

3


77 A2 77US 2-55

Figure 2-55. Printer Controller Properties

Add a Printer displays the following Dialogue Box:

Figure 2-56. Add a Printer Dialogue Box


2-56 77 A2 77US

There are four parameters to be entered in 4 drop-down lists:

• The printer model from among the following list:

PR800 / PR900 / PR701 /PR801 / PR901 / PR702 / PR802 / PR902 / PR800n / PR900n.

Models PR800n and PR900n represent the PR800 and PR900 printers without an IGP card. These two models only support the RS-232 interface and the XON/XOFF protocol. The baud rate is limited to 19200 bauds.

• The serial port number (COMi) which the printer is connected to. The user is presented with the list of COM ports installed on the server.

• The connection interface: RS-232 or RS-422. The choice is imposed (RS-232) for the PRx00[n] models.

• The baud rate from the drop-down list of the following values: 9600 bauds / 19200 / 38400 / 57600

The protocol used by the printer controller is defined automatically depending on the model and interface chosen in accordance with the correspondence table below.

Table 2-5. Model, Protocol, Interface relations

Model Protocol for interface RS-232 Protocol for interface RS-422

PR800n XON/XOFF NA

PR900n XON/XOFF NA

PR800 Series1 1 CHAR NA

PR900 Series1 1 CHAR NA

PR701 Series1 1 CHAR Series1 1 CHAR







PR2000 NA Series1 1 CHAR NA: not applicable

Models PRx01 and PRx02 support both RS-232 and RS-422 interfaces; the SERIES 1 protocol is imposed during setup.


77 A2 77US 2-57

Models PRx02A and PRx02SA are assimilated with the corresponding PRx02 model in the configurator.

For PRx00[n] printers, the rate must be 9600 or 19200 bauds. Other values cannot be defined in the printer. This point is checked by the Configurator Check command. If not respected, a warning is displayed in the detailed report.

In the specific case where the user selects either of the PR800[n] and PR900[n] models for which only the RS-232 interface is supported, the latter is automatically forced by the system (Figure 2-57 below).

Figure 2-57. Add a PR800n Printer (with no IGP Card)


2-58 77 A2 77US

2.9.6.8 Telecom Controller Context Menu

There are two types of telecom controllers (NCC-V7 et LNM-V7) each associated with two different PXUs (respectively, PXN-V7 and PXL-V7). The Context Menu for these PXUs is identical:

Figure 2-58. Telecom Controller Context Menu

• Add a Telecom Line is always shaded because it is not significant in this context.

• Delete removes the selected controller. A Confirmation Dialogue Box is displayed. If the user confirms this choice, all the associated lines are also removed.

• Properties displays controller features (controller name and model, Physical Name (PCLC), �).


77 A2 77US 2-59

Figure 2-59. Telecom Controller Properties (NCC)

This window is used to enter specific parameters:

• MAC Address MAC address of the network card supporting this controller. This field is not to be completed if all telecom cards are not present on the platform. This field will be updated later, once the missing card has been installed.

When configuring from the target platform, use the Dropdown Menu displaying the list of DSA dedicated network card MAC addresses. When configuring from a remote station, enter the corresponding controller MAC address manually.

IMPORTANT: When a platform is configured from another platform, do not use the Dropdown Menu since the addresses listed are local platform addresses.

IP Address The IP address associated with this controller. When this field is completed, this IP address and the IP address in the OCS server configuration files are checked when the OCS server is started under GCOS7 (the 2 IP addresses are to be identical). This field is not mandatory.

The Configuration Editor checks that the same IP address has not been used twice and that the IP address is not a native telecom card address, via the Check command. This field can only be completed manually.

An IP address is not required for LNM-V7 controllers.

• Network type (Ethernet or FDDI).

13

3


2-60 77 A2 77US

2.9.6.9 Disk Context Menu

The Disk Context Menu is the following:

Figure 2-60. Disk Context Menu

• When Delete is selected, a confirmation Dialogue Box is displayed.


77 A2 77US 2-61

• Properties displays disk features:

Figure 2-61. Disk Properties

Disk size is selected with the Dropdown Menu. Four values may be selected: 2, 4, 8 and 9 GB.

The path can be entered manually or located with the Browse button. The Browser is only to be used on the V7000 platform being configured.


2-62 77 A2 77US

2.9.6.10 Tape Cartridge Context Menu

The Tape Cartridge Context Menu is the following:

Figure 2-62. Tape Cartridge Context Menu

• When Delete is selected, a confirmation Dialogue Box is displayed. If the user confirms this choice, the cartridge drive is removed from the configuration.

• Properties displays cartridge features:

Figure 2-63. Tape Cartridge Features


77 A2 77US 2-63

GCOS7 type (36T/M6/M5, SCL/LIB) and Windows™ data can be modified in this window via the associated Dropdown Menus. If no cartridge driver is installed on the platform, Windows™ data is not accessible via the Dropdown Menu.

Refer to section 2.9.6.6 describing the "Add a Cartridge" command for a complete description of the parameters, and particularly the paragraph �WWPN vs SCSI addressing mode�.

IMPORTANT: When selecting data, do not select the Windows™ (NT type) devices whose name contains Sony or HP. These devices are reserved for use under Windows™. It is not to be included in the V7000 configuration.

2.9.6.11 Printer Context Menu

The Printer Context Menu is the following:

Figure 2-64. Printer Context Menu

• When Delete is selected, a Confirmation Dialogue Box is displayed. If the user confirms this choice, the printer is removed from the configuration.

• Properties displays Printer features.

13

3


2-64 77 A2 77US

Figure 2-65. Printer Properties

A printer's four parameters can be modified: • Model • Port • Interface • Baud Rate

Refer to section 2.9.6.7 describing the "Add Printer" command for the description.

Displaying or modifying a printer's properties page on a machine other than the target machine Here, the user is unable to choose the COM port, which must be refreshed on the target machine.

If a COM port has been assigned to the printer, it is displayed on a gray background (whatever its value) and cannot be modified. All the other parameters can be modified.

Displaying or modifying a printer's properties page on a target machine whose COM ports are not installed/have been incorrectly installed


77 A2 77US 2-65

The display of a printer's properties page is preceded by the dynamic creation of the list of COM ports installed on the server. While this list is created, the user is informed of all possible anomalies via a dedicated dialogue box.

• No COM ports installed on the server Message: "No COM Port available". In the properties page, the Port drop-down list is grayed.

• COM ports are incorrectly installed on the server, the list could not be created (the list is empty). Message: "No COM Port available. Some port are unavailable". In the properties page, the Port drop-down list is grayed.

• Certain COM ports are incorrectly installed on the server, the complete list could not be created (the list is partial). Message: "Other COM Ports are unavailable".

In the properties page, the Port drop-down list presents the COM ports that could not be listed.

NOTE: Errors encountered while creating the list of COM ports are recorded in the Event Viewer (source V7000_CONFEDT).

2.9.6.12 Telecom Context Menu

This Context Menu does not exist. Telecom lines cannot be removed and significant properties are displayed with Controller properties.


2-66 77 A2 77US

2.10 Sharable Disks Configuration

This section describes how to take into account, in the V7000 Configuration Editor, the GCOS7 disk created on W2K shared disks. Section 3.8 and Appendix F must be consulted together with this section.

Two types of information must be defined for sharable disks configuration:

• the Sharable property of a GCOS7 disk

• the identification information of the partner site sharing GCOS7 disk(s)

2.10.1 Sharable Property of a GCOS7 Disk

This property means that a GCOS7 disk has a specific access mode management during the V7000 virtual machine session.

This property can be specified through a checked box:

• Either in the property page of the disk �MSxx Properties�

• or in the add disk dialog box �Add a Disk�

Figure 2-66. Properties of a GCOS7 disk named MS01 in the Result Pane; this disk is configured with the property Sharable=No.


77 A2 77US 2-67

Figure 2-67. Property page for the MS01 disk; the box �Disk sharable� is not checked.


2-68 77 A2 77US

Figure 2-68. Property page for the MS01 disk; the box �Disk sharable� is checked.


77 A2 77US 2-69

Figure 2-69. Properties of the GCOS7 disk named MS01 in the Result Pane; this disk is now configured with the property Sharable=Yes.

Figure 2-70. Adding a GCOS7 disk named MS02 by checking the �Disk Sharable� box


2-70 77 A2 77US

Figure 2-71. Properties of the previous GCOS7 disks named MS01 and MS02 in the Result Pane; these disks are now configured with the property Sharable=Yes.


77 A2 77US 2-71

A control is made on the number of GCOS7 disks configured with the Sharable property. This number is limited to 56; beyond this limit, the �Disk sharable� checkbox of the �MSxx Properties� property page or of the �Add a Disk� dialog box is grayed and not checked.

Figure 2-72. Property page for the GCOS7 disk named MSM1 when 56 disks are already configured with the property Sharable=Yes.


2-72 77 A2 77US

2.10.2 Identification Information of the Partner Site

This information is defined through the �SharedDiskManager� tab of the �Global Information Properties� property page of the �Global Information� node.

This information is mandatory if at least one GCOS7 disk is configured with the Sharable property.

Figure 2-73. Default values of the �SharedDiskManager� tab


77 A2 77US 2-73

Partner System Identification:

Identifies the V7000 system number of the partner. This identifier is fixed to S0 and is not modifiable.

Partner Serial Number:

Identifies the serial number of the DPS7000/XTA server on which the V7000 system partner is running. This serial number is given by the V7000 key corresponding to the DPS7000/XTA partner server.

A serial number is unique.

Partner Site:

Identifies the DPS7000/XTA partner server on the network, and can be specified in two ways:

Network Name name of the DPS7000/XTA partner server inside the TCP-IP network

IP Address TCP-IP address of the DPS7000/XTA partner server

These two forms are mutually exclusive.

Port Number:

Identifies the port number used for the dialog between the two V7000 system partners over the TCP-IP network.

Default value: 7000.


2-74 77 A2 77US

Figure 2-74. �SharedDiskManager� tab after providing values

IMPORTANT: The consistency of the identification information between the configurations of the two V7000 system partners must be �manually� checked:

1. The Serial Number and the Site (Network Name or IP Address) of one DPS7000/XTA server must be the Partner Serial Number and the Partner Site (Network Name or IP Address) of the other.

2. The Port Number must be the same on the two servers.

13

3


77 A2 77US 2-75

Information: Relation [Partner] Serial Number / DUALSYS GCOS7 keyword

The Serial Number and the Partner Serial Number are used as parameters of the GCOS7 configuration DUALSYS keyword

The Model Name and the Partner Model Name, given by the V7000 key, are also used as parameters of the GCOS7 configuration DUALSYS keyword.

Example of use:

Server DPS7000/XTA DIANE1.

Model Name 9018

Serial Number 5004

Server DPS7000/XTA DIANE2.

Model Name 9018

Serial Number 5003

On DIANE1: DUALSYS 90185003,MYSELF=90185004

On DIANE2: DUALSYS 90185004,MYSELF=90185003


2-76 77 A2 77US

2.10.3 Checking the Configuration (Check Command)

If at least one GCOS7 disk is configured with the Sharable property, the Check command checks that the values of the �SharedDiskManager� tab are provided. If this is not the case, the configuration is invalid and cannot be activated.

Figure 2-75. Result of the Check command (see Figure 2-76)

Figure 2-76. (With above figure). Result of the Check command when at least one GCOS7 disk is configured and the values of the �SharedDiskManager� tab are not provided.


77 A2 77US 2-77

The Sharable property is checked for consistency for all GCOS7 disks.

• If Sharable=Yes, the Check command checks that the disk is defined to be used in Shared mode (see Chapter 3, �GCOS7 Disk Manager�)

• If Sharable=No, the Check command checks that the disk is not defined to be used in Shared mode (see Chapter 3, �GCOS7 Disk Manager�)

If this consistency is not respected, the configuration is invalid and cannot be activated.



2-78 77 A2 77US

Figure 2-78. (With above figure). Result of the Check command when Sharable=No (Configuration) and Shared=Yes (Disk Manager)



77 A2 77US 2-79

Figure 2-80. (With above figure). Result of the Check command when Sharable=Yes (Configuration) and Shared=No (Disk Manager)

IMPORTANT: The Sharable property must be defined in the V7000 configurations of the two partner systems (V7000 configuration files .g7c are independent), whereas the Shared mode is defined from one of the partner systems through the GCOS7 Disk Manager (see Chapter 3).

13

3


2-80 77 A2 77US

77 A2 77US 3-1

3. GCOS7 Disk Manager

New functionalities of version V2 concerning the Shared mode of GCOS7 disks are described in section 3.8, on page 3-39.

3.1 General Presentation

GCOS7 disks are represented by Windows� files on all DPS 7000/XTA platforms.

The GCOS7 Disk Manager is a tool used to create, rename, make-up or delete GCOS7 disks on a DPS 7000/XTA platform. It is a multi-functional, user-friendly graphic tool supplied with V7000 in the form of an executable program. A history file maintains the successive operations performed for each GCOS7 disk.

The Disk Manager is to be used when configuring V7000 virtual machine resources. Cf. Chapters 1 and 2.

When V7000 VM is active, this tool or any other tool cannot be used to act on GCOS7 disks belonging to the active configuration.


3-2 77 A2 77US

3.2 Implementing GCOS7 Disks: GCOS_Disks Directories

IMPORTANT: It is MANDATORY for the Windows� files representing GCOS7 disks to be implemented in a file tree under a root directory called GCOS_Disks.

The creation of directories depends on the number of physical disks connected to the platform, the number of Windows� partitions defined in these physical disks and the access path: (Logical device : �letter� followed by �:�, disk folder: �directory declared as such� ).

NOTE: It is recommended to create a global directory under C: describing all the disk partitions (logical volumes) used by the server. The user can then protect the space used for GCOS7 disks and implement non-V7000 files on these disks.

For example, a DPS 7000/XTA server with two DSS1 disk sub-systems, each with 8 logical disks (partitions) can be described as follows:

a directory for global server disk space: GlobalDiskSpace

followed by a directory for each disk sub-system: DDS1_i

followed by a disk folder for each partition (logical volume): DSS1_i_j

followed by a GCOS7 directory for each disk folder: GCOS_Disks

followed by directories for non-GCOS7 data: other

13

3

GCOS7 Disk Manager

77 A2 77US 3-3

This method is illustrated in Figure 3-1:

< - - - > < - - > <disk folder> < - - - > disks

C:\GlobalDiskSpace \DSS1_1 \DSS1_1_1 \GCOS_Disks\ MS01MSL1

- - - - - - - - - - - - -\other1

\DSS1_1_2 \GCOS_Disks\ S02MSL2

- - - - - - - - - - - - -\other2

\DSS1_1_3 \GCOS_Disks\ MS03MSL3

- - - - - - - - - - - - -\other3

- - - - - - - - - - - - -- - - - - - - - - - - - -- - - - - - - - - - - - -- - - - - - - - - - - - -

\DSS1_1_8 \GCOS_Disks\ MS14\other8

\DSS1_2 \DSS1_2_1 \GCOS_Disks\ MS21MSN1

- - - - - - - - - - - - -\other9

\DSS1_2_2 \GCOS_Disks\ MS22MSN2

- - - - - - - - - - - - -\other10

\DSS1_2_3 \GCOS_Disks\ MS23MSN3

- - - - - - - - - - - - -- - - - - - - - - - - - -- - - - - - - - - - - - -- - - - - - - - - - - - -

\DSS1_2_8 \GCOS_Disks\ MS3BMSPB

- - - - - - - - - - - - -\other16

Figure 3-1. GCOS7 Disk Implementation


3-4 77 A2 77US

3.3 Protecting GCOS7 Disks

The GCOS7 Disk Manager forces access rights on each disk and tree directory in which these disks are implemented at CREATE function time.

The system is protected as follows:

3.3.1 GCOS7 Disk Files (MSxx)

• Administrators Group • Full Control

• V7000BullServices Group • Full Control

• Everyone • None

3.3.2 Upstream GCOS_Disks Tree Directory Leading to an MSxx File

• Administrators Group • Full Control

• V7000BullServices Group • Full Control

• Everyone • Read Furthermore, the inheritance of father rights is cut off from this directory.

In all events, the default Owner identified by Windows� is the Administrators Group and cannot be changed or forced by the GCOS7_Disk Manager.

GCOS7 Disk Manager

77 A2 77US 3-5

3.4 GCOS7 Disk Manager User Rights

The use of the GCOS7 Disk Manager is reserved for members of the V7000BullServices Group. Any attempt to launch the Disk Manager by a non-authorized user results in an Error Message.

Figure 3-2. Warning Message: Unauthorized Access

The GCOS7 Disk Manager can only be activated if a valid key is present on the machine. If a valid key is not present, the following message is displayed:

Figure 3-3. Warning Message: Invalid Key


3-6 77 A2 77US

3.5 GCOS7 Disk Manager Functions

Figure 3-4 shows the GCOS7 Disk Manager Home Page.

The Home Page is divided into 5 zones. The content of each zone changes according to the context:

• Selections offers the following standard functions in the form of radio buttons:

− CREATE to create a GCOS7 disk,

− RENAME to change the name of an existing disk,

− MAKE UP to normalize a disk,

− DELETE to remove a disk.

The Disk Size Dropdown List is displayed when CREATE is checked.

• Current Path to choose the location and the name of the file concerned by the action to be performed via the BROWSE button. This button is shaded to begin with.

• Current Action to build the command prompt. When the command prompt is complete, a start button (CREATE, RENAME or DELETE) and a CANCEL button appear on the right (previously hidden).

• Previous Action indicates the last action performed by the tool and the HISTORY button gives access to the history file in which the tool records all the actions performed. This button is shaded to begin with.

• Activity indicates current actions (none in the example). The QUIT button is used to exit the tool.

GCOS7 Disk Manager

77 A2 77US 3-7

Start Button

Browse Button

History Button

Command prompt

Cancel Button

Disk sizeDrop-down menu

Quit Button

Prompt box

Figure 3-4. GCOS7 Disk Manager Page Description

When the tool is accessed and a function has been selected, the user is prompted to check and restore (where applicable) GCOS7 disk access rights.

Figure 3-5. GCOS7 Restore Protection Confirmation Dialog Box

If the answer is Yes, all the GCOS_Disks trees on the platform are checked.


3-8 77 A2 77US

This operation restores directory rights so that GCOS7 disk files are protected as described in § 3.3. This process may take several minutes, according to V7000 configuration.

The answer must be Yes when existing GCOS7 disks have been created without using the CREATE function (for instance, GCOS7 disks normalized using the MAKE UP function)

(Refer § 3.5.1 and § 3.5.3 for details on CREATE and MAKE UP functions).

GCOS7 Disk Manager

77 A2 77US 3-9

3.5.1 CREATE

This function is used to:

• Create a Windows� file with the MSxx name of the corresponding GCOS7 disk.

• Forces access rights on the created GCOS7 disk file and tree directory in which this file is implemented as described in § 3.3.

• Initialize, at the top of this file, a control area characterizing this file as an eponym GCOS7 disk.

• Write the EOF setting GCOS7 disk size.

• Write the last file block, so that the GCOS7 disk can be immediately managed by a V7000 disk controller. This process is asynchronous: a thread is launched for each disk to be created.

• Save the disk creation process to a memory history buffer, specific to the current directory logical drive (LL). This takes place in two phases:

− when the last block of the disk is being written, the disk is said to be in Creation,

− at the end of the writing process, in Creation becomes Created.

IMPORTANT: When the buffer is saved to the history file during the creation of a disk, the creation trace appears twice: in Creation: beginning of disk creation, Created: end of disk creation.

The buffer is saved to the disk when the buffer is full or when the user asks to view the history file (Cf. below).

GCOS7 disks can only be created on physical disks with a sector size of 512 bytes.

The size of the control area is 1 Kbyte for disks created with version V7000 V0.x. The size of this area is now 16 Kbytes for disks created as of version V7000 V1.y. This implies that the size displayed for a GCOS7 disk by the Windows Explorer differs according to the V7000 version used to create it. Here is an example for a 4 GB GCOS7 disk:

• 4 194 305 Kbytes for a disk created with V1 • 4 194 320 Kbytes for a disk created with V0. GCOS7 disks can only be created in directories defined as follows:

• <LL>:\GCOS_Disks\Optional_sub_directory(ies)\ (LL = Logical Drive: letter followed by �:�)

13

3


3-10 77 A2 77US

or C:\directory\�\disk folder\GCOS_Disks\Optional_Sub_directory(ies)\

Cf. the example given in § 3.2.

EXAMPLES:

C:\GCOS_Disks\MS01

X:\GCOS_Disks\Group1\MSDS

C:\GlobalSpaceDisk\K1-1\K1-1-1\GCOS_Disks\MS03 here, K1-1-1 is a disk folder.

$

Either case can be used for the name of the GCOS_Disks directory.

The name of the disk is not followed by an extension. It is composed of four alphanumeric characters (excluding I, O and Q), the first two of which are MS.

When the file is created, this name is forced in capital letters.

If there is no GCOS_Disks directory in the selected tree, GCOS7 disks cannot be created. The BROWSE button in the Current Path zone allows the user to create this directory via the standard Windows� Browser.

3.5.2 RENAME

This function is used to change the name of a GCOS7 disk. It is only used on GCOS7 Windows� files created by the GCOS7 Disk Manager.

RENAME is used when a configuration check reports that disks are missing. Existing disks may not have been named in compliance with Configuration Editor requirements and need to be renamed:

• The Windows� file is renamed in compliance with the rules set out in § 3.2. In order to be able to use disks obtained with previous versions of the creation tool, the initial file name case is not checked,

• The file control area is modified so that it can be recognized as the renamed GCOS7 disk,

• The disk name change is saved to the current directory logical drive (LL) history buffer.

RENAME and MAKE UP allow old file names to remain unchanged for case normalization.

The path, size and content of a renamed file seen by GCOS7 remain the same.

GCOS7 Disk Manager

77 A2 77US 3-11

3.5.3 MAKE UP

This function is only used on GCOS7 Windows� files created by the GCOS7 Disk Manager. It updates the control area.

This function is used to normalize GOCS7 disk files that have been copied or moved by the Windows� Explorer. It is also used to indicate how files may have been handled outside the GCOS7 Disk Manager.

Unlike the other functions, MAKE UP can be applied to a series of files within a single directory.

Any files without a valid name are ignored without notifying the operator. The history file lists the disks processed successfully.

• In order to be able to use disks obtained with previous versions of the creation tool, the file name case is not checked, but is converted into capital letters.

• The file control area is modified so that the file is recognized as a GCOS7 disk in the current path.

• The process is saved to the current directory logical drive (LL) history buffer.

The size and content of the file seen by GCOS7 remain the same.

3.5.4 DELETE

This function deletes a GCOS7 disk image file. It is only used on GCOS7 Windows� files created by the GCOS7 Disk Manager.

• A file can only be deleted if its control area is valid,

• A Windows� file is deleted after confirmation,

• This process is saved to the current directory logical drive (LL) history buffer.

CAUTION: Data written on the GCOS7 disk is irremediably lost (update of V7000 configuration is necessary after DELETE function).


3-12 77 A2 77US

3.6 External Visibility

3.6.1 General Screen Presentation

The window comprises the tool icon and name (GCOS7 Disk Manager) along with five main zones:

• Your selections is used to:

− Select a function via four radio buttons.

− Select and view the size of the disk created. The default selection in CREATE mode is: V7000 8.0 GB.

− View the size of the disk to be renamed or deleted.

• Current Path is used to:

− Select the current working directory via the BROWSE button.

− View and activate this directory via the OPEN button, displayed by clicking BROWSE.

The name of the file selected is displayed in the Current Action zone.

• Current Action is used to:

− Define, launch or cancel the action to be performed.

The operator is guided by a command prompt constituted by the function selected and the name of the GCOS7 disk(s) concerned. This prompt defines the action to be performed.

Names are entered in interactive windows, which appear and disappear as the command prompt is built.

Consistency and feasibility checks are carried out as the command prompt is built. When the prompt is complete, buttons appear to allow the operator to start or cancel performance of the current action.

The name of the start button recalls the action to be launched: CREATE, RENAME, DELETE. MAKE UP is never displayed on this button. The MAKE UP function is launched by selecting the files concerned.

The function may be cancelled via the CANCEL button. However, partial or complete command prompts are cancelled when the selection is changed.

The Current Action zone refers to the Current Path zone.

GCOS7 Disk Manager

77 A2 77US 3-13

• Previous Action is used to:

− Display the last action validated and performed via a command as built in the Current Action zone (with the Current Path value inserted between the function and the name of the target disk).

− Read LL history files with at least one LL:\GCOS_Disks\ directory opened by the Browser. The HISTORY button allowing this action is shaded until one of the directories concerned has been opened.

When HISTORY is pressed:

− Non-empty history buffers are written in append mode to their history files: <LL>_Disk History.txt,

− A window opens allowing the history files to be selected and viewed.

Prior to this action, each buffer contains a description of the actions previously performed on the LL concerned.

A multiple selection of history files is carried out by dragging items in the list displayed by clicking HISTORY. These files are opened by releasing the left mouse button.

The GCOS7 Disk Manager limits the number of history buffers maintained simultaneously to sixteen.

When an LL:\GCOS_Disks directory belonging to a seventeenth LL is selected, all the history buffers are written. When disks are no longer being built on an LL, the corresponding history buffer is deleted from the list of maintained history buffers, thereby allowing the new history buffer to be accepted.

If no history buffers are deleted, the following Warning Message is displayed:

Figure 3-6. No History Buffer Free Warning Message

The above message is edited when 16 disks are being built on 16 different LLs.

<LL>_Disk History.txt history files are located in the Trace directory.

Each file contains the trace of the GCOS7 Disk creations, name changes, file arrangements and deletions carried out on the corresponding logical driver (LL).


3-14 77 A2 77US

• Activity is used to:

− Display the number of disks currently being created. When disks are being created, the box flashes (building of tables required to write the last block).

A 2 GB disk is built in approximately 2 minutes. An 8 GB disk is built in approximately 10 minutes. These times are only given for guidance and vary according to DPS 7000/XTA platform type.

The QUIT button closes the GCOS7 Disk Manager. If disks are still being built when QUIT is pressed, the following message is displayed:

Figure 3-7. Disks Being Built Warning Message

QUIT is then shaded and is only accessible when the last disk has been built.

GCOS7 Disk Manager

77 A2 77US 3-15

3.6.2 Home Page

Figure 3-8. GCOS7 Disk Manager Home Page

Only the function selection radio buttons and the QUIT button are accessible. The cursor is placed on the main function radio button, i.e. CREATE.


3-16 77 A2 77US

3.6.3 CREATE Windows

3.6.3.1 Home Page

Click the CREATE radio button:

Figure 3-9. GCOS7 Disk Manager Home Page: CREATE

V7000 8.0GB is automatically selected in the Selected disk size list. Click the Drop-down Menu to edit this choice and select the required disk size. Four sizes may be selected: 2 GB, 4 GB, 8 GB and 9 GB.

The Current Path BROWSE button is accessible.

A different function may be selected at this stage.

GCOS7 Disk Manager

77 A2 77US 3-17

3.6.3.2 Working Directory Selection Window

Click BROWSE to open the following window:

Icon : �Create new folder�

Figure 3-10. Working Directory Selection Window

The cursor is automatically placed on Open.

When Open is pressed for the first time, the Title Bar prompts the user to select a directory:

�Select your working GCOS_Disks folder�

When Open is pressed again, the Title Bar recalls the directory previously opened, e.g.:

�You are working in one Y:\GCOS_Disks\�

This is useful since the Look in field only displays the name of the last path and this name may not be unique.

By clicking Open or double-clicking one of the files in the list, the resulting path is accepted as the Current Path if its root is <LL>:\GCOS_Disks\ or �\disk folder \GCOS-Disks.


3-18 77 A2 77US

If not, a Warning Message is displayed:

Figure 3-11. Incorrect Path Warning Message

When a file is selected, its name is copied to the prompt box in the Current Action zone. The disk with this name becomes the target disk and the feasibility check is performed on this disk. If the feasibility check is successful, the CREATE and CANCEL buttons appear. If the feasibility check is not successful, an Error Message is displayed.

When no file is selected, MS alone is copied to the prompt box and the operator has to complete the target file name manually.

If a GCOS_Disks directory has not yet been created, this directory can be created by clicking on the Create new folder icon.

3.6.3.3 Window after Opening the Working Directory (no File Selected)

The Current Action zone displays Create MS. This name can be completed by the operator.

The CREATE, RENAME, MAKE UP and DELETE radio buttons, the Disk size Dropdown list and the BROWSE button are accessible, allowing the selection of a new function, disk size or path.

The HISTORY button is accessible, allowing the X_Disk History.txt file to be viewed.

The CREATE and CANCEL buttons are invisible.

GCOS7 Disk Manager

77 A2 77US 3-19

Figure 3-12 . Window after Opening the Working Directory (no File Selected)


3-20 77 A2 77US

3.6.3.4 Window after Opening the Working Directory (File Selected)

Figure 3-13. Window after Opening the Working Directory (File Selected)

The CREATE and CANCEL buttons are accessible because MSGG is a valid name:

• the working directory does not already contain a disk with this name,

• there is sufficient space to create a 2 GB disk.

If these conditions are not fulfilled, Warning Messages may appear and the CREATE button becomes invisible or shaded.

GCOS7 Disk Manager

77 A2 77US 3-21

Figure 3-14. Existing File Warning Message

Figure 3-15. Insufficient Disk Space Warning Message

3.6.3.5 Home Page During the Creation of a File

• CREATE and CANCEL buttons are invisible.

• Previous Action has been updated, Activity is flashing and indicating that another disk is being built.

• Specific disk name characters are deleted from the prompt box. A new disk name can now be entered.

• The CREATE, RENAME, MAKE UP and DELETE radio buttons, the Disk size Dropdown List and the BROWSE button are accessible, allowing the selection of a new function, disk size or path.


3-22 77 A2 77US

Figure 3-16. Home Page During the Creation of a Disk

GCOS7 Disk Manager

77 A2 77US 3-23

3.6.4 RENAME Windows

3.6.4.1 Home Page

Click the RENAME radio button.

If a path has not been previously selected, the CREATE, RENAME, MAKE UP and DELETE radio buttons and the BROWSE button only are accessible.

If a path has been selected, the GCOS7 Disk Manager Home Page is displayed:

Figure 3-17. GCOS7 Disk Manager Home Page: RENAME

Rename MS is displayed in the Current Action zone. This name may be completed by the operator.

The BROWSE button is accessible for selection of another directory and / or selection of the disk via the OPEN button.


3-24 77 A2 77US

No disk size is displayed.

The HISTORY button and the Current Path and Previous Action zones maintain their status.

3.6.4.2 Home Page after Opening a Directory and Entering a Valid File Name (MSGG in the Example)

Figure 3-18. GCOS7 Disk Manager: RENAME

GCOS7 Disk Manager

77 A2 77US 3-25

Since MSGG is an existing file with a valid control area, Rename MSGG is followed by:

• as MS: in this case, MS is to be completed to form the new name allocated to MSBB, or

• as MSGG: if the previous action was a RENAME without a name change � in view of normalizing the names of a series of disks. This action can also be performed via the MAKE UP function.

Disk Size V7000 2.0 GB corresponds to the type of MSGG disk. If the file to be renamed does not exist, a Warning Message is displayed, e.g. MSHG instead of MSGG:

Figure 3-19. Unknown File Warning Message

If the file is opened by another tool, a Warning Message is displayed:

Figure 3-20. File Open Warning Message


3-26 77 A2 77US

If user access rights are insufficient or if the file is write protected, the following Warning Message is displayed:

Figure 3-21. Access Denied or Write Protected File Warning Message

If the control area is incorrect, the following Warning Message is displayed:

Figure 3-22. Incorrect Control Area Warning Message

GCOS7 Disk Manager

77 A2 77US 3-27

3.6.4.3 Home Page after Entering a New Valid Name for the File (MSCC in the Example)

Figure 3-23. Home Page after Entering a New Valid File Name: RENAME

The RENAME and CANCEL buttons are visible because MSCC is a valid name and no disk with this name exists in the current directory.


3-28 77 A2 77US

If a file with this name already exists in the current directory, a Warning Message is displayed, e.g.:

Figure 3-24. Existent File Warning Message

At this level, a modification of the initial MSGG name in the Rename zone hides as MSCC along with the RENAME and CANCEL buttons.

However, entry of a different valid name results in the appearance of as MS. If this name is MSGG, as MSCC along with the RENAME and CANCEL buttons reappear.

GCOS7 Disk Manager

77 A2 77US 3-29

3.6.4.4 Home Page after Pressing RENAME

Figure 3-25. Home Page after Pressing RENAME

Previous action is updated.

If the name of the file previously renamed was entered via the selection of a file with BROWSE (and not modified in the prompt box), the GCOS7 Disk Manager places the cursor on BROWSE. Otherwise, the cursor is placed in the prompt box. The user is to know the list of disk files to be renamed.


3-30 77 A2 77US

3.6.5 DELETE Windows

3.6.5.1 Home Page

Click the DELETE radio button.

If a path has not been previously selected, the CREATE, RENAME, MAKE UP and DELETE radio buttons and the BROWSE button only are accessible.

The Current Action zone displays Delete MS. This name may be completed by the operator.

The BROWSE button is accessible, allowing the selection of another directory and / or the disk via the OPEN button.

Disk size is not displayed.


Figure 3-26. GCOS7 Disk Manager Home Page: DELETE

GCOS7 Disk Manager

77 A2 77US 3-31

If the status of the file named by the operator is incompatible with the action to be performed, Warning Messages are displayed. These Warning Messages are the same as those displayed for the RENAME function.

3.6.5.2 Home Page after Opening a Directory and Entering a Valid File Name (MSCC in the Example)

Figure 3-27. Home Page after Selecting the File to Be Deleted

The DELETE and CANCEL buttons are visible because MSCC is the name of an existing file with a valid control area.

Disk Size V7000 2GB corresponds to MSCC disk type.


3-32 77 A2 77US

Press DELETE to display the following Dialog Box:

Figure 3-28. Delete Confirmation Dialogue Box

If No is pressed now or if CANCEL is pressed during the previous stage, a window similar to that in Figure 3-26 is displayed.

3.6.5.3 Home Page after Pressing the Yes Button

Figure 3-29. Home Page after Pressing the Yes Button

GCOS7 Disk Manager

77 A2 77US 3-33

Previous action is updated.

If the name of the file previously renamed was entered via the selection of a file with BROWSE (and not modified in the Rename zone), the GCOS7 Disk Manager places the cursor on BROWSE. Otherwise, the cursor is placed in the Rename zone. The user is to be in possession of the list of disk files to be renamed.

3.6.6 MAKE UP Windows

This function is used to normalize a GCOS7 disk control area. It is to be used when one or several disks have been moved via the Explorer. This function normalizes several disks in the same directory in a single process.

3.6.6.1 Home Page

Click the MAKE UP radio button:

Figure 3-30. GCOS7 Disk Manager Home Page: MAKE UP


3-34 77 A2 77US

Disk size is not displayed.


The CREATE, RENAME, MAKE UP and DELETE radio buttons allow the selection of another function. If another function is selected, it is MANDATORY to press BROWSE after selecting the function.

The BROWSE button is accessible. It is MANDATORY to press this button to multiple select the disk files to be processed.

3.6.6.2 File Selection Window

Figure 3-31. MAKE UP File Selection Window

Files are selected in the same way as with the Windows� Explorer, i.e. by pressing the Shift or Control keys and the left mouse button.

The File name field shows all the files selected.

The cursor is automatically placed on the Open button.

GCOS7 Disk Manager

77 A2 77US 3-35

3.6.6.3 Home Page after Selecting Files

Click the Open button:

Previous Action is updated. It indicates the action performed on the disks in the selection.

The Disk size display corresponds to the disk indicated in Previous Action.

The CREATE, RENAME, MAKE UP and DELETE radio buttons and the BROWSE button are accessible, allowing the function to be changed or a new selection to be made.

Figure 3-32. Home Page after Selecting the MAKE UP Files


3-36 77 A2 77US

If it is impossible to perform MAKE UP on certain selected disks, Warning Messages are displayed, e.g.:

Figure 3-33. MAKE UP Warning Message: File in Use

Figure 3-34. MAKE UP Warning Message: File Write Protected

If OK is pressed, the process is continued. At the end of the process, the following Warning Message is displayed:

Figure 3-35. MAKE UP Error Warning Message

GCOS7 Disk Manager

77 A2 77US 3-37

3.6.7 HISTORY Windows

3.6.7.1 File Selection Window

Click HISTORY to update the history files and to display the history file selection window:

Figure 3-36. History File Selection Window

This window contains the name of the <LL>_Disk History.txt history files (16 files maximum) for the LL with at least one <LL>_GCOS_Disk\�\ directory open. In the example above: LL=C.

These files are read-only files. History files can be multiple selected by dragging in the list displayed by clicking HISTORY. Release the left mouse button to open these files.


3-38 77 A2 77US

When one or several files are selected, the selection window closes and the file(s) is(are) opened. The HISTORY button, which was replaced by the SELECT button is restored. If no file is selected, the window is closed when the operator presses a button or modifies a disk name.

3.6.7.2 History Files

The name of the history file, its creator and the date and time of creation head the display:

C:\Programs\BULL\V7000\Trace\C_Disks History.txt created by Disk Manager PID:

2172, user: NT AUTHORITY\Dianetest the 11/07/2001 at 16:39:45

These data are followed by the blocks corresponding to history buffer dump dates. Dumping is launched by:

• clicking HISTORY,

• closing the GCOS7 Disk Manager. In this case (when exiting) is indicated in the block header,

• when a history buffer is full.

Apart from the date and time, the block header contains the name of the operator and the PID. The PID is useful when several GCOS7 Disk Managers are working simultaneously in the same directory.

The block-containing file renaming data may be written with the block containing creation data. The dates and times of these actions are exact.

The history blocks contain the description of the actions performed and the date and time of performance.

State stamped by Disk Manager PID: 2172, user: NT AUTHORITY\Dianetest the 11/07/2001 at 18:23:45

the 11/07/2001 at 16:40:20 MSGG (V7000 2.0 GB SS= 512) was created in folder C:\Gcos_Disks\Marketing\

the 11/07/2001 at 18:07:39 MSGG (V7000 2.0 GB SS= 512) was renamed as MSCC in folder C:\Gcos_Disks\Marketing\

the 11/07/2001 at 18:09:41 MSCC (V7000 2.0 GB SS= 512) was deleted in folder C:\Gcos_Disks\Marketing\

the 11/07/2001 at 18:32:24 MS22 (V7000 2.0 GB SS= 512) was made up as MS22 in folder C:\Gcos_Disks\Marketing\



the 11/07/2001 at 18:32:25 MS44 (V7000 2.0 GB SS= 512) wasn't made up in folder C:\Gcos_Disks\Marketing\

the 11/07/2001 at 18:32:25 MS45 (V7000 2.0 GB SS= 512) wasn't made up in folder C:\Gcos_Disks\Marketing\

Figure 3-37. History File Specimen

GCOS7 Disk Manager

77 A2 77US 3-39

3.7 Restrictions

The maximum number of creation threads is 64, i.e. the number of files that can be created simultaneously.

The maximum number of files that can be managed simultaneously by the MAKE UP function is 64.

The maximum number of history buffers that can be managed simultaneously is 16, i.e. the number of LLs in which disks can simultaneously be created.

The maximum number of history buffer entries is 64. Each entry corresponds to the description of an action performed on a disk.

When a history file is written, the block header and each entry is formatted and written to a buffer. The size of this buffer is 16 KB.

The maximum number of history files that can be read simultaneously is 64.

3.8 GCOS7 Disk Shared Mode Function

Before presenting this function, it is necessary to provide some definitions concerning �disk terminology� on a DPS7000/XTA server.

GCOS7 disk

An NTFS file composed of a control area (V7000 software visible only) and of GCOS7 data.

GCOS7 sharable disk (see Chapter 2: V7000 Configuration Editor)

• Property given to a GCOS7 disk in the V7000 configuration

• Sharing between two V7000 virtual machines named �partner systems�, each running on one DPS7000/XTA server

GCOS7 shared disk

• State known and managed by GCOS7 only

− DUALSYS keyword in GCOS7 configuration necessary

− SHARED option at ISL or RDV operator command

• State unknown by V7000 software


3-40 77 A2 77US

W2K shared disk

LUN (Logical Unit Number) of a disks sub-system visible and accessible from two W2K servers at the same time

IMPORTANT: 1. When a GCOS7 disk is an NTFS file created on a W2K shared disk, the

Shared mode must be specified for this GCOS7 disk through the GCOS7 Disk Manager. Currently, this is the only way to inform the V7000 software that this GCOS7 disk is created on a W2K shared disk, because W2K does not manage this sharing.

2. Only NTFS files corresponding to GCOS7 disks must be allocated on W2K shared disks.

Two functions are used to take into account the Shared mode of a GCOS7 disk:

1. DEFINE SHARING: defines, for the V7000 software, whether the GCOS7 disk must be used in Shared mode or not. This information is stored in the control area of the GCOS7 disk.

2. DISPLAY: displays the control area of the GCOS7 disk (particularly, the Shared mode).

IMPORTANT: To be defined with the Shared mode, a GCOS7 disk must have been created with V7000 software version V1.2 or later.

Figure 3-38. GCOS7 Disk Manager version error message for Shared mode definition.

13

3

13

3

GCOS7 Disk Manager

77 A2 77US 3-41

Figure 3-39. GCOS7 Disk Manager page description with DEFINE SHARING and DISPLAY functions (at utility startup)

3.8.1 DEFINE SHARING Function

This function defines the Shared mode or the not Shared mode for a GCOS7 disk.

When you click the DEFINE SHARING radio button, the GCOS7 Protection Confirmation Dialog Box is displayed. Answer Yes to display the following GCOS7 Disk Manager box.


3-42 77 A2 77US

Figure 3-40. GCOS7 Disk Manager page description after clicking the DEFINE SHARING radio button

The Shared check box appears and is checked by default.

The BROWSE button is now accessible. It must be used to select the desired GCOS7 disk, which must have been previously created using the CREATE command.

GCOS7 Disk Manager

77 A2 77US 3-43

Figure 3-41. GCOS7 Disk Manager page description after selecting the desired GCOS7 disk with the BROWSE button

A Warning Dialog Box is displayed to ask the user to confirm the operation. If the the user chooses Yes, the operation continues and the Shared mode is specified for the disk; otherwise the operation is aborted.

NOTE: This Warning Dialog Box is also displayed when the Shared is not checked. The message describes the modification of the Shared mode:

not Shared!Shared or Shared!not Shared operation


3-44 77 A2 77US

Figure 3-42. GCOS7 Disk Manager page description after answering Yes in the preceding Warning Dialog Box

At this point, the Shared mode is specified for the GCOS7 disk and �Make shared PATH\MSxx� is displayed under the Previous Action label.

For a Shared!not Shared operation, the message �Make not shared PATH\MSxx� is displayed under the Previous Action label.

GCOS7 Disk Manager

77 A2 77US 3-45

3.8.2 DISPLAY Function

This function: displays the control area of the GCOS7 disk (particularly, the Shared mode).

Figure 3-43. GCOS7 Disk Manager page description after clicking the DISPLAY radio button

The check box With Logging appears and is not checked by default.

If checked, this option stores the result of the DISPLAY command in the history file (see section 3.6.7).


3-46 77 A2 77US

Figure 3-44. GCOS7 Disk Manager page description after selecting the desired GCOS7 disk using the BROWSE button

The message �Display PATH\MSxx� is displayed under the Previous Action label.

Click on the HISTORY button to display the result of the DISPLAY command.

For a disk for which the Shared mode has been specified, the result is as follows:

States stamped by Disk Manager PID: 1104, user: NT AUTHORITY\GAUTHIER the 30/07/2002 at 16:10:39 the 30/07/2002 at 16:10:35 MS01 (V7000 2.0 GB SS= 512) was found as (SHARED) in folder D:\Gcos_Disks\ For a disk for which the not Shared mode has been specified, the result is as follows:

States stamped by Disk Manager PID: 1868, user: NT AUTHORITY\GAUTHIER the 30/07/2002 at 16:17:37 the 30/07/2002 at 16:17:33 MS01 (V7000 2.0 GB SS= 512) was found as (NOT SHARED) in folder D:\Gcos_Disks\

GCOS7 Disk Manager

77 A2 77US 3-47

3.8.3 Shared Mode With RENAME, DELETE and MAKE UP Functions

If the Shared mode is specified for a GCOS7 disk, the following Warning Dialog Boxes are displayed when using the RENAME, DELETE or MAKE UP functions for this disk.

Figure 3-45. Warning Dialog Box on RENAME command for a disk for which Shared mode is specified


3-48 77 A2 77US

Figure 3-46. Warning Dialog Box on DELETE command for a disk for which Shared mode is specified

GCOS7 Disk Manager

77 A2 77US 3-49

Figure 3-47. Warning Dialog Box on MAKE UP command for a disk for which Shared mode is specified


3-50 77 A2 77US

77 A2 77US 4-1

4. V7000 Information Collector

The V7000 Information Collector is a Windows� application used to collect DPS 7000/XTA troubleshooting data.

This tool �V7000 Information Collector� is also called BCT �Bull Collect Tool�.

This tool could be launched on a Diane platform, from the �start� menu.

Figure 4-1. Start menu giving access to V7000 tools


4-2 77 A2 77US

If an unauthorized user attempts to launch this tool, the following window is displayed.

Figure 4-2. Error message displayed when you are not allowed to use this tool

By clicking on the OK button, the tool is exited.

When starting the following window appears, recalling that the use of the tool is reserved to the members recorded in the V7000BULLSERVICES V7000OPERATORS or ADMINISTRATORS group.

It is an information message.

Figure 4-3. Warning message displayed when you are allowed to use this tool

By clicking on the OK button, the following window is obtained:

V7000 Information Collector

77 A2 77US 4-3

Figure 4-4. Main V7000 Information Collector Window

4.1 Function Offered

In the window above, you must select the box according to the incident for which you want to saved the files. Then while clicking on the RUN button, the collection of information is launched.

The �Elapsed Time� field is updated as well as the progress bar �Files Names�.

Once the collection of the files is finished, a new window will be posted, you requiring where you want to create the cabinet file ( describes in the paragraph 4.2).

For more information, you can display the helps by clicking the HELP button.(describes in the paragraph 4.3).

The QUIT button isn�t operational any more when the RUN function is launched.


4-4 77 A2 77US

A report file(A-Bct-ReportLog.txt) containing the list of the files saved will be produced in the cabinet file.

A trace file(A-Bct-TraceLog.txt) containing the events trace of this tool will be produced in the selected directory.(The default is : ..\Trace\CollecTool).

According to the type of problem encountered, the user then checks one or several boxes :

Input parameters:

Brief Description: Summary description of the problem (80 characters maximum). This information will be written in the report file.

V7000 Incident: To collect V7000 incident files.

VCP7 Incident: To collect VCP7 incident files. (local controller of the OCS server).

VLCT Incident: To collect VCP7 incident files. (local controller of the TNS server).

INTEROP Incident: To collect INTEROP7 incident files.

SAM Incident: To collect SAM incident files.

WINDOWS Incident: To collect Windows� incident files.

OTHER Incident: To collect the files for an indefinite incident.

List of files collected according to the selected incident.


77 A2 77US 4-5

Incident V7000

Incident VCP7

Incident VLCT

Incident INTEROP7 Incident SAM

Incident WindowsTM

2000Incident Other

EventLog FilesLOGFILEID_V7000 x x x x x xLOGFILEID_APPLICATION x x x x x x xLOGFILEID_SECURITY x x x x x x xLOGFILEID_CONSOLES x x x x x xLOGFILEID_SYSTEM x x x x x x xLOGFILEID_INTEROP7 x x

System filesboot.ini , System.ini , Win.ini x x x x x x xInterop7 Installation and activation x x x x x x xSetupact.log , Setuperr.log x x x x x x xSysevent.evt, Secevent.log x x x x x x xAppevent.log x x x x x x xConfig.nt x x x x x x xSystem Information report x x x x x x x

RegistryDrWtsn registry x x x x x x xAeDebug registry x x x x x x x

DumpDrWtsn dump ( if exists) x x x x x x xUser dump ( if exists) x x x x x x x

Files of the TRACE diectoryV7000*.* x x x x x x*History.txt x x x x x xCPU_FW* x x x x x xIOP* x x x x x xInstall* x x x x x xVCP* x xVLC* x xV7000_Telecom_AdminTool.exe x x x

Files of the Component directoryList of the all files x x x x x x

Files of the Controller directoryList of the all files x x x x x x

ConfigConfig* x x x x x xInstall* x x x x x x

INTEROP7 filesLog* x xOpenGtwTrace x x


4-6 77 A2 77US

4.2 Creation of the Cabinet File

As soon as the collection of the whole files is finished, the following window is displayed.

Figure 4-5. Collect complete window to save the compressed file.

This window gives you two possibilities:

1. By clicking the button "The compressed file will be stored on 4mm tape", the cabinet file will be saved on a DAT 4mm tape using the standard tool NTBACKUP.

You can change the name of the cabinet file by clicking on the Browse button or by directly changing the name in the text bar.

The cabinet file will not be deleted after the saving on the DAT 4mm tape.

NOTA :

a - This option is reserved to the members recorded in the ADMINISTRATORS group.

b - The media DAT 4mm tape must have the format supported by NTBACKUP. (refer the general HELP)


77 A2 77US 4-7

2. By clicking the button "The compressed file will be stored in the directory", the cabinet file will be created in the default directory.

(C:\Program Files\Bull\V7000\Trace\CollectTool)

You can change the name of the cabinet file by clicking on the Browse button or by directly changing the name in the text bar.

The cabinet file will not be deleted after the saving.

If you want to save the cabinet file later on a DAT 4mm tape , please refer you to the chapter 4.5.

The removal of the files collected in the repertory /Trace will be carried out after the creation of the cabinet file, if it is requested.

NOTE : It�s the implicit option.

If you do not want to remove the files after the collection, uncheck the following box :

"Delete saved files from \Trace directory"

To launch the creation of the cabinet file or the saving of this file on the DAT 4mm tape.

Click on the button OK

For more information refer to the help of the NTBACKUP tool (backup function) accessible from the �start� menu.

(Start\Programs\Accessories\System Tools\Backup).

The cabinet file will be always available in the directory�/Trace/CollectTool after the save.

When the cabinet file has been saved on DAT 4mm tape or was created in the selected directory, the following window is displayed.


4-8 77 A2 77US

Figure 4-6. Collect complete window.

While clicking on the OK button , you return on the principal window:


A new collection may be launched.


77 A2 77US 4-9

4.3 The Helps

This window is displayed when you click on the HELP button in the main window

"V7000 Information Collector" with no button selected.

While clicking on the NO button, you return on the principal window:

"V7000 Information Collector"


4-10 77 A2 77US

While clicking on the YES button, the following window is displayed

While clicking on the OK button, you return on the principal window:


You can display the help relating to an incident by selecting this incident and by clicking on the HELP button in the main window:



77 A2 77US 4-11

4.4 The Errors

The errors messages are displayed in the message box:

List of the errors messages:

<file> = file name

<rc> = return code

Unable to copy File V7000 : <file> error = <rc> OpenDllEVLogFile FAILED error = <rc> BackupEVLogFile FAILED error = <rc> CloseDllEVLogFile FAILED error = <rc> You are not allowed to use this tool.This tool is dedicated to Bull Support Operation. Warning: this tool is dedicated to Bull Support Operation. no selection ! Try again GetFileVersionInfo Failed VerQueryValue Failed GetFileVersionInfo Failed ERROR see the trace File Tape 4mm is not configurated. The .cab file will be available in the directory Collectool The requested media is not currently on-line. Please insert the specified media. When the media is ready click on the OK button else CANCEL The tape is write-protected. Please , remove the protection . When the media is ready click on the OK button else CANCEL Unable to CopyFile : <file> Delete File Error : <file> Delete Directory Error : <dir> ***** ERROR Cannot get the path of the TRACE folder ui32rc = <rc> ***** ERROR Unable to create Directory : CollectTool ui32rc = <rc> ***** ERROR Unable to create Directory : <dir> ui32rc = <rc>


4-12 77 A2 77US

4.5 Saving Collected Information on a DAT Cartridge

Once the .cab file has been created subsequent to the collection, it must be saved on a cartridge, which is then sent to the Bull Support Center for analysis.

For this purpose, the Windows Backup tool is used. Proceed as follows:

• Start the tool from the "Start" menu

Figure 4-7. Starting the Backup Utility

• The following window is displayed:

Figure 4-8. Backup Welcome Screen


77 A2 77US 4-13

• Click on the Backup tab

The backup file selection window is displayed. By clicking on the + signs, the tree structure is deployed to reach the appropriate file, in this case:

C:\Program Files\Bull\trace\Collect Tool\Bct-010918-093817.cab

Figure 4-9. Backup File Selection Window

The "Backup destination" drop-down list is used to select the backup support. The user must choose "4mm DDS".

The "Backup media or file name" drop-down list is used to specify the backup support. Here the user indicates a new media, in other words one that has not yet been used for a backup.

Once everything has been correctly filled, the user must click on the "Start Backup" button to continue.

Depending on the support inserted in the device, different messages may be displayed. Here (Figure 4-10), Backup indicates that the cartridge has an unrecognized format and that it contains information.


4-14 77 A2 77US

Figure 4-10. Media Warning Message

In this example, the user answered �Yes� to confirm the use of this cartridge, thus accepting the loss of any previous information it contained.

Figure 4-11. Information on the Backup that Will Start

As appropriate, the user may choose either to append this backup to a previous backup on the one hand, or replace any previously saved information on the other hand.

By clicking on the "Start Backup" button, the backup is activated.

If needed, a dialog box may be displayed prompting the user to insert the cartridge.

Once the cartridge has been inserted, the following window is displayed and remains displayed until the end of the operation.


77 A2 77US 4-15

Figure 4-12. Backup Progress Window at the Start of the Backup

In the "Files" field, we can see that there is 1 file to save and that none (0) have been saved yet. The "Bytes" field indicates that no bytes have been transferred yet to the cartridge.

During the backup, the "Processing" field indicates the progress of the operation.


4-16 77 A2 77US

At the end of the backup, the appearance of this window changes, as illustrated below:

Figure 4-13. Backup Progress Window at the End of the Backup

As indicated in the "Status" field, the backup is Completed; the time elapsed is given in the "Time" field, while the number of files and bytes processed corresponds to the estimated number.

Clicking on the "Report" button displays the backup report in a Notepad window.

Clicking on the Close button takes the user back to the main Backup window either to proceed with another backup, or to quit by clicking on the cross at the top right of the window.

The media obtained in this way is then sent to the Bull Support Center. It must be referred in the PARM request associated with the problem.

V7000 Key Manager

77 A2 77US 1

5. V7000 Key Manager

The V7000 Key Manager is a Windows� application used to install or to check a V7000 key on a V7000 platform. The user is to belong to the V7000BullServices group to launch the application.

The name of the file containing the key is in the following format: xxxxyyyy.g7k. This key file is accompanied by a text file: xxxxyyyy.txt.

Figure 5-1 Key Manager Home Page

The Load Key button activates a Browser for the selection of the key file to be installed. The name of the file is to be compliant with the format indicated above.


2 77 A2 77US

Figure 5-2 Key File Selection Browser

Select a file and click Open.

The installation context and key type are checked.

If the check result is correct, the selected key file and corresponding text file (which should be in the same directory) are installed on the V7000 platform.

The following message is displayed: Key successfully installed.

When the key is a temporary key, the following message is displayed: Temporary key successfully installed. Key validity: xxx days.

§ 1.4 describes DPS 7000/XTA key evolutions.

Potential Error Messages:

Error messages are listed below in italics, followed by the appropriate corrective action:

• You are not allowed to use this tool. The user must belong to the V7000BullServices group to launch the application.

• Key file cannot be opened, cause: nnn. Contextual error: the key file is not accessible (nnn: Cf. Win32 Error Codes)

• Key file name must have the .g7k extension.

• Key file is not consistent. The key file supplied is incorrect. A new key file must be generated.

V7000 Key Manager

77 A2 77US 3

• Key is not compliant with hardware. The key file supplied does not match with the current hardware signature. Platform identification is to be recalculated before generating a new key file. Contact the BULL Support Center.

• Error checking hardware identifier. Contact the BULL Support Center.

• Cannot reach installation directory. Contact the BULL Support Center.

• Cannot reach installed key file. Contact the BULL Support Center.

• Registry not accessible. Consult the log file to identify the internal error and contact the BULL Support Center.

• Input file key is not consistent with installed key. Upgrade or Update key. The key supplied is not consistent with the key installed (incorrect serial or version number). A new key file must be generated from the key file currently installed. Contact the BULL Support Center.

• A second temporary key may not be installed. The installed key is temporary and a new temporary key cannot be installed. A new key file must be generated. Contact the BULL Support Center.

• A key file is already installed. Do you want to overwrite it? A key is already installed and the user is trying to reinstall an Init key.

The Check Key button checks the validity of the installed key.

If the check result is correct, one of the following message is displayed:

Installed key is valid. The key is valid.

Installed temporary key is valid. The key is valid until the delay given at the building of the key has expired.

Installed temporary key is invalid: Delay has expired. The key is invalid because the delay given at the building of the key has expired.


4 77 A2 77US

Installed key is become temporary. First(Second/Third) hardware component is invalid. Expiration date = yyyy/MM/dd HH:mm:ss

The key is become temporary because one of the component of the hardware identifier is invalid. The key is valid until the expiration date.

Installed key is become temporary. First(Second/Third) hardware component is invalid. Delay of temporary installed key has expired

The key is become temporary because one of the component of the hardware identifier is invalid. The key is invalid because the delay of 15 days until the first detection has expired.


• You are not allowed to use this tool. The user must belong to the V7000BullServices group to launch the application.

• OpenRegistry failed -> RC=xxxxxxxx.. Contact the BULL Support Center.

• No installed key Fatal Error ReadCodedKey -> RC=xxxxxxxx. Contact the BULL Support Center.

• No installed key. Fatal Error ExistKeyProduct -> RC=xxxxxxxx. Contact the BULL Support Center.

• Installed key is invalid TestHardwareSignature -> RC=xxxxxxxx. Contact the BULL Support Center

• Installed key is invalid TestHardwareSignature -> RC=xxxxxxxx.

77 A2 77US 6-1

6. V7000 Platform Identifier

The V7000 Platform Identifier is a Windows� application used to calculate the identification of a V7000 platform and to store the calculated identification in a hdwident.g7p file. This file is required to calculate the V7000 platform Init or Upgrade key.

Figure 6-1. Platform Identifier Home Page

The Get PlatformIdentifier button is used to activate a Browser for the selection of the generated file backup directory. The name hdwident is prompted. The generated file is given the extension .g7p.


6-2 77 A2 77US

Figure 6-2. Backup File Selection Browser

Select a file and click Save.

If the process runs correctly, the following message is displayed: File name and path complete. File has been generated.


Error messages are listed below in italics, followed by the appropriate corrective action:

• Coded Platform Identifier file cannot be opened. Contextual error: the indicated file cannot be reached (incorrect path).

• Platform Identifier file name must have the .g7p extension. Contextual error: the indicated file extension is incorrect.

• Data required to build the Platform Identifier is not accessible. The tool is being used on a non-DPS 7000/XTA platform.

77 A2 77US 7-1

7. V7000 Configuration Tool

The V7000 Configuration Tool is a Windows� application using tabbed property pages.

• The first page describes the Alarm Transfer Configurator application that sets the parameters required to transfer alarms to the Bull Support GTS Center.

• The second page describes the MasterSlave Wait Time Configuration that sets the wait time for the change from SLAVE status to MASTER status for V7000 clients (SYC and console).

File transfers to the GTS station can only be carried out by a known user with sufficient access rights to the watchdog station running the FTP server. The user must also know the GTS station network name.

In the event of a transfer failure, the user can configure the transfer retry rate.

Alarm Transfer Configurator data may be subject to change. Data can therefore be updated during a V7000 session.

The MasterSlave Wait Time Configuration application allows the user to change the wait time value during a V7000 session.

The Alarm Transfer Configurator Transfer Test button allows the user to send an alarm test to the Bull Support GTS Center.


7-2 77 A2 77US

7.1 Alarm Transfer Configurator Parameters and Transfer Test button

The initial display of the Alarm Transfer Configurator page only shows Retry Transfer Frequency default values and the button Transfer Test is gray.

Figure 7-1. Alarm Transfer Configurator � Initial Display

The user may supply values for the Custom Site Identification and for the User Name , Password fields according to the configuration of the BULLMAINT station. To ungray the Transfer Test button GTS Host Name must be supplied.

It is possible to select an FTP port number other than the default value (21). This allows alarms from multiple machines to be received on the incoming alarm server, with different incoming port numbers.

The Transfer Retry Rate can be changed via the DAYS, HOURS, and MINUTES boxes. Remarks: Before clicking on the Transfer Test button, the user must register the changes via Apply or OK button.

V7000 Configuration Tool

77 A2 77US 7-3

Figure 7-2. Alarm Transfer Configurator � Example

IMPORTANT: Transfer Retry Rate:

Minimum: 0 days 0 hours 10 minutes Maximum: 45 days 23 hours 59 minutes Default: 0 days 1 hour 0 minutes

The data entered in this Dialog Box is stored in the register (GTS key) for use in the customer FTP application.

Once the parameters are registered, a click on the Transfer Test button will send an alarm test to the Bull Support GTS Center.

13

3


7-4 77 A2 77US

After the Transfer Test button being clicked, one of the following modal messages boxes will be displayed:

1) Service V7000 System Control in �Started� state

2) Service V7000 System Control in �Stopped� state

3) Failure during the alarm creation

V7000 Configuration Tool

77 A2 77US 7-5

If the alarm test is successfully transferred to GTS site, the format of this alarm test message looks like the following example:

DIANE: MODLN=DPS7000/XTA001;

NT: SITEN=FRCLS3642; SSN=90015119;

V7000: MODLN=DPS7000/XTA001; SITEN=FRCLS3642; SSN=90015119;

[Date]: 09/26/2005

[Time]: 02:39:38 PM

[Computer Name]: FRCLS3642

[System Id]: 0

[Source]: CONFIGURATION_TOOLS

[EventType]: Information

[EventId]: 1000

[EventMsg]: This is a test of V7000ConfigurationTools to send an alarm to GTS station

[Complementary Text]: No complementary text file.


7-6 77 A2 77US

7.2 MasterSlave Wait Time Configuration

The MasterSlave WaitTime Configuration page displays the current wait time value and the possible values the wait time can take.

Figure 7-3. V7000 Configuration tool: MasterSlave WaitTime

Configuration

To change the wait time value, either double click on a value in the list box or select a value in the list box and then click OK. The data is stored in the register (VAS key) for use in VAS.

To stop the V7000 Configuration Tool application click Quit.

77 A2 77US 8-1

8. V7000 Trace Manager

This V7000 maintenance tools is used to collect additional data when standard data gathered by V7000 Information Collector are not sufficient to identify a problem.

Trace Manager is launched on the request of maintenance people who must specify the domain and level of trace.

Data collected by trace manager are put in files located in the directory Bull\Trace. Names of these files look like : V7000_doamin_x.txt where domain is the name of the domain and x can take value 1 or 2.

The V7000 Trace Manager is a Windows� Dialog Box type tool. The Trace Manager is manually launched from the local server running the V7000 engine. To have access to this tool, the user is to belong to the V7000BullServices group.

Once user identity has been checked, the application allows the user to display or edit trace activation parameters.


8-2 77 A2 77US

The various trace functions are displayed on the Home Page:

Figure 8-1. Trace Manager Home Page

If the trace is not active when the V7000 Trace Manager is launched, only the Stop Trace button is shaded.

If the trace is active when the V7000 Trace Manager is launched:

• The Start Trace button is shaded.

• The Trace Domain and Trace Level cannot be edited.

• Domains List boxes cannot be checked / unchecked.

• The Select Trace Level Drop-down Menu is shaded and cannot be edited.

V7000 Trace Manager

77 A2 77US 8-3

8.1 V7000 Trace Manager Home Page

The Home Page allows the following functions to be activated:

Select or View Trace Domains: Displays a Checklist type Dialog Box used to select trace domains if the trace is not active or to display the selected domains when the trace is already active.

Select Trace Level: Displays Trace Levels in a Drop-down Menu (the same Trace Level is applied to all the domains selected).

Trace State: Displays Trace State (active or not active) and the Trace Level when active.

Start Trace: Validates the Trace Domains selected by Select Trace Domains at the level specified by Select Trace Level.

Stop Trace: Validates Trace Domains at level 0 (Stop Trace).

Quit: Closes the V7000 Trace Manager application.


8-4 77 A2 77US

8.2 Selecting or Displaying Trace Domains

Figure 8-2. Trace Domains List Dialog Box (Trace not Active)

This menu is used to display the list Trace Domains that can be activated or that are already activated. It is obtained by pressing the Select or View Trace Domains button. A domain is selected by clicking the corresponding check box.

OK: Validates the list of selected domains and closes the Domains List Dialog Box.

Cancel: Closes the Domains List Dialogue Box without editing the previous selection.

Select All: Selects all the domains (without having to check the corresponding boxes).

If the trace is active when Trace Manager is launched, the Domains List can be viewed but cannot be edited.

V7000 Trace Manager

77 A2 77US 8-5

The Cancel and Select All buttons are shaded.

Figure 8-3. Domains List Dialog Box (Trace Active)

The following domains can be activated:

• PX00 to PX80,

• IO00 to IO08,

• HAM0, HAM1 (trace domains of HAM component),

• VAS0 to VASE (trace domains of VAS service)


8-6 77 A2 77US

8.3 Select Trace Level

This menu is used to display and select the Trace Level.

Figure 8-4. Home Page: Select Trace Level

NOTE: If the trace is active when Trace Manager is launched, trace levels cannot be edited.

V7000 Trace Manager

77 A2 77US 8-7

The following Trace Levels are available:

• Function Title: highest level (value 1). It is used to store main function input and output messages.

• Error: second level (value 3). It capitalizes fatal error messages, i.e. all the texts transmitted to the LOG. Error messages can be systematically traced via the application Log Message process, by simply specifying the message number (EventId).

• Warning: intermediate level (value 5). It is used to report all ignored, corrected or bypassed events. These errors do not affect the success of a function.

• Passing Point: standard trace level (value 7). It is used to mark the transition between the various branches of the algorithm during the execution of a program.

• Information: lowest level (value 9). All trace texts are stored along with any useful details concerning operating parameters (API use, Trace Text or Trace Dump).


8-8 77 A2 77US

8.4 Start Trace

Figure 8-5. Home Page: Trace Active

When the trace is not active, the Start Trace button can be used to activate the selected trace domains at the specified level.

The Trace State box is updated according to the level selected.

After clicking Start Trace, the button is shaded. The Domains List and the Trace Level can be viewed but cannot be edited until the trace is stopped.

V7000 Trace Manager

77 A2 77US 8-9

8.5 Stop Trace

The Stop Trace button is used to deactivate trace domains when the trace is active.

Figure 8-6. Home Page: Trace Not Active

The Trace State box is updated to display Trace Not Active.

After clicking Stop Trace, the button is shaded. The Domains List and the Trace Level can be viewed and edited.

IMPORTANT: If V7000 is shut down (TS) and restarted (INIT), traces are not deactivated. They still go on after restarting V7000.

8.6 Quit

The Quit button and the cross in the right-hand corner are used to close the V7000 Trace Manager application.

• When the Service System Control (SYC) is started: If the trace is active when Quit is pressed, the domains selected and the trace level remain active and the trace continues. If the trace is not active when Quit is pressed, the domains selected and / or the trace level are not maintained.

• When the Service System Control (SYC) is not started: If the trace is active when Quit is pressed, the domains and / or trace level are not maintained (Cf. Trace Active above).

13

3


8-10 77 A2 77US

8.7 Checks and Errors

• If V7000 Trace Manager application is launched a second time, the following Error Message is displayed:

Figure 8-7. Trace Manager Already Launched Error Message

Click OK to close the Trace Manager.

• If no domain has been selected and the Start Trace button is pressed, the following Warning Message is displayed:

Figure 8-8. Warning Message N° 1: No Domain Selected

Click OK to display the Domains List.

• If no level has been selected and the Start Trace button is pressed, the following Warning Message is displayed:

Figure 8-9. Warning Message N° 2: No Level Selected

Click OK to close this Warning Message box.

77 A2 77US 9-1

9. Backing up a DPS 7000/XTA or Novascale 7000 Platform’s System Environment

9.1 Overview

On a DPS7000 / XTA or Novascale 7000 machines, backups of the system (Windows 2000� 1), V7000 and GCOS7 B-Disk are essential. Indeed, being able to resume operations subsequent to a serious hardware/software incident using the most up-to-date backups possible and within a delay of less than 45 minutes is crucial.

Sensitive data are located on the internal disk of the machine, visible in the Windows� Explorer.

Its preservation calls on two procedures:

• Physical duplication:

• Models XTA X0, 1X0, X2, 1X2, X3, 1X4, X4 : cloning of one disk to another with DOS Power Quest� Deploy Center V5.0 (and later) tool. Windows� and V7000 are thus stopped.

• Models 1X4: Hardware mirroring (see §9.9).

• Models X5: Hardware mirroring (see §9.10).

• Novascale 7000: Hardware mirroring (see §9.11).

• Logical backup, using the standard Windows NT Backup tool, to a 4mm DAT magnetic cartridge. Windows� and V7000 are thus running.

1 Windows 2000 is a generic term covering all Windows systems that support V7000, the first being Windows 2000

Advanced Server, the second Windows 2003 Enterprise Edition.


9-2 77 A2 77US

NOTE: This backup only concerns the internal disks on the DPS7000 / XTA or Novascale 7000 machines. GCOS7 data, located in the external storage bays, follows its traditional backup/restoration procedures under GCOS7.

NOTE: Appendix E gives a disaster recovery procedure when the standard one is not successful.

IMPORTANT: At the end of the installation and configuration procedures completed by the customer, the active disk must be cloned before starting to use GCOS7 in production.

9.2 Reminders

9.2.1 Not Raided Models

A DPS 7000 / XTA machine incorporates two internal Basic disks with a capacity of 16.95 GB (or more). However, on the factory-delivered machine, the Windows� disk manager sees only one disk.

This disk corresponds to Disk0 (address: Bus0, TargetId: 0, LUN 0), and is split into four partitions:

• A hidden FAT partition, required for the machine's hardware maintenance.

• A C:\ system partition, called WIN2000 (approximately 4 GB), containing Windows� 2000 and the V7000 software among others.

• An E:\ partition called V7000 (approximately 5 GB), containing the V7000 configuration, the Gcos7 Starter disk or B-Disk, and the Gcos7 Disk Folders, corresponding to the anchor points of the disks that make up the external storage bays, drivers, etc.

• An F:\ partition called Data (approximately 8 GB or more), empty on delivery and the use of which is free.

The second disk (address: Bus0, TargetId: 0, LUN 1) is logically excluded from the hardware configuration recognized by Windows� to protect it from corruption. At the end of factory conditioning, it contains a physical copy (a clone) of disk0 created using the Deploy Center tool.

13

3

Backing up a DPS 7000/XTA or Novascale 7000 Platform’s System Environment

77 A2 77US 9-3

9.2.2 Raided Models

On Raided DPS 7000 XTA, Windows disks are Raid1 protected and managed by a LSI Logic Raid card. Windows Disk Manager sees only one disk with the three partitions C;\, E:\ and F:\. For 1X4 and X5 models, or four (plus Fat partition) for the other ones.

On Novascale 7000 machine, Windows disks are located and managed by SR-0812 subsystem. Raid1 protection is managed by SR-0812 Raid card.

Windows visibility is the same as DPS 7000 XTA machines, and Windows Disk Manager sees only one disk with the three partitions C:\, E:\ and F:\.

IMPORTANT: Before cloning the current active disk0, the user must make sure that the second internal disk is still logically excluded from the configuration. It is essential that this information be copied on the clone in order to be remanent. This is checked by selecting Computer Manage! Device Manager ! Disk Drives where the status of the second disk is Disabled (see also Figure 9-16). If this is not the case, select it then right-click and choose Disable.

13

3


9-4 77 A2 77US

9.3 Archiving

The purpose of the Disk0 backup is to save all the hardware and/or software changes monitored by a DPS 7000 / XTA machine, and thus be able to restore a stable state as quickly as possible in the event of an incident (loss of disks, human errors, etc.).

These changes will vary in terms of importance. The most constraining will require the machine to be shut down to take account of new characteristics; these changes correspond to:

• Windows� upgrades (installation of a Service Pack x) or V7000 upgrades (installation of a new Version Vx.y),

• Installation of tools or new drivers in relation to V7000,

• Hardware modifications to the platform (new or replaced peripherals, model upgrades, etc.).

If possible, these major changes must be combined in a single update phase to minimize the server's down time.

At the end of the update, Disk0 is cloned (cf. § 3.4), without significantly increasing the machine's down time.

For greater security (see §3.5), a complete NT Backup of the C:\ and E:\ partitions on a 4mm DAT cartridge is recommended.

Changes may also occur that do not require Bull's intervention, or even a machine restart, or which barely diverge in relation to the current clone. These can be:

• Customizations (adding users in the V7000 groups, etc.),

• Other modifications with no direct relation to V7000 and/or GCOS7.

These changes do not necessarily require an immediate complete backup of Disk0 by cloning.

The machine's administrator can perform the backup by carrying out a complete NT Backup minimal of the C:\ and E:\ partitions on a 4mm DAT cartridge (cf. §3.5).

The administrator is responsible for archiving the F:\ partition using NT Backup.


77 A2 77US 9-5

9.4 Cloning

IMPORTANT: The boot diskettes and the Deploy Center program provided with the DPS7000 / XTA machine are used. The product does not therefore have to be installed unless the diskettes need to be regenerated (see Appendix C).

The tool runs under DOS and sees both internal disks (Disk0 and Disk1). When the boot diskette has finished initializing the machine, the user inserts the Program diskette then presses a key to load Deploy Center.

NOTE: If the load fails due to an early key strike, the tool can be restarted using the PQIMGCTR command at A:\ level after inserting the second diskette.

IMPORTANT: An empty target disk is required for a cloning operation. Indeed, the second internal disk that will be used contains a pre-existing clone on delivery from the factory. The partitions on this volume must therefore be deleted using Deploy Center (see below).

IMPORTANT: At the end of each cloning operation, the user must restart on the clone to make sure it is valid by physically inverting the machine's two internal volumes. The user must open the internal disk compartment, switch the disk in position 0 to position 1, and the disk previously in position 1 to position 0 (see Appendix D).

Disk to disk cloning is summarized below.

NOTE: Disk0 (address: Bus0, TargetId: 0, LUN: 0) and Disk1 (address: Bus0, TargetId: 0, LUN: 1) become Disk1 and Disk2 in Windows for the Deploy Center tool.

IMPORTANT: This procedure is available when internal disks are identical (same constructor and features). Otherwise the cloning procedure must be modified. See paragraph 9-7.

Before cloning, check if the internal disks are identical (during BIOS startup, or with Windows Device Manager).

13

3

13

3

13

3

13

3


9-6 77 A2 77US

The load window below is displayed when the user restarts in DOS.

Figure 9-1. Loading the Deploy Center 5.0 Tool

The following welcome screen is then displayed.

Figure 9-2. Deploy Center 5.0 Menu


77 A2 77US 9-7

Given that the target disk is not empty since it contains the last clone performed, the partitions must be deleted before being able to use it.

Proceed as follows (steps 1 to 20):

1. In the Tools menu, choose the Delete Disk Partitions option (Figure 9-3).

Figure 9-3. Tools Menu


9-8 77 A2 77US

Figure 9-4. Selecting the Partitions to Delete

2. In the Delete Partitions window (Figure 9-4), select Disk2 in the Physical Drives area, then

3. Click the Delete All button.

IMPORTANT: Make sure that disk 2 is the one selected.

4. Confirm the destruction of the data (Figure 9-5).

Figure 9-5. Confirming the Destruction of the Partitions

13

3


77 A2 77US 9-9

At the end of the operation, disk 2 regains its full free capacity (Figure 9-6).

Figure 9-6. Situation after Destroying the Partitions

5. Quit the Tools menu, go back to the Welcome screen (Figure 9-2) and choose the Disk to Disk option.

The selection of the disk to copy is then proposed (Figure 9-7).


9-10 77 A2 77US

Figure 9-7. Selecting the Source Disk

6. Select Disk 1 (Figure 9-7).

7. Click on the Next button.

The characteristics of the source disk (size, partitioning, etc.) are then displayed on-screen (Figure 9-8).

Figure 9-8. Selecting the Partitions on the Source Disk


77 A2 77US 9-11

8. In the Disk to Disk Copy window (Figure 9-8), click on the Select All button (concerns all the partitions).


10. Select the target disk � Disk2 � (Figure 9-9).


Figure 9-9. Selecting the Target Disk

12. The free space that is to receive the clone is then selected (Figure 9-10).

NOTE: If Disk2's space is not completely unused, this means it still contains partitions which must be deleted by going back to the Tools menu in the Welcome screen (Figure 9-3).


9-12 77 A2 77US

Figure 9-10. Selecting the Backup Space on the Target Disk

13. Click on the Next button (Figure 9-10).

A summary of the current cloning status is displayed (Figure 9-11).

Figure 9-11. Status of Information Collected

14. Click on the Finish button (standard options of the process are kept).


77 A2 77US 9-13

The cloning process starts on the four FAT, WIN2000, V7000 and DATA partitions respectively. Progress windows showing the operation's progress, like the one in Figure 9-12 for the WIN2000 partition, are displayed.

These windows represent the phases for controlling � relatively quickly � the consistency of the file structures. They cover the copying step for each partition.

Figure 9-12. Copying the WIN2000 Partition

IMPORTANT : If error occurs during partition cloning, please refer to § 9.5 .

13

3


9-14 77 A2 77US

At the end of the process, the user is prompted to view the results (Figure 9-13).

Figure 9-13. Viewing the Results after Copying

15. Click on the Yes button, to check the target disk at the end of the process (Figure 9-14).

Figure 9-14. Details of the Target Disk after Copying


77 A2 77US 9-15

IMPORTANT: Check if WIN2000 partition is active as shown on figure 9-14. .

In other cases, this partition must be set active using Hide/unhide Partition and/or Set Active Partition options from Tool Menu (Figure 9-3)

16. Click on the Close button (Figure 9-14).

17. Go back to the PowerQuest ImageCenter welcome screen (Figure 9-2), then choose Exit.

18. Remove the Deploy Center Program diskette from the drive, then stop the machine.

19. Physically invert the internal disks in positions 0 and 1, then restart the machine on the clone created.

20. If the clone works properly, keep it as the active disk, otherwise go back to the reference and resume the cloning process.

IMPORTANT: If the capacity of the disks used in the cloning differs slightly, the procedure described previously is slightly different.

Figure 9-14 shows Disk2 with 7.8 MB of unused space. This may occur when the cloning is done on a disk whose capacity is not strictly the same as that of the source disk, or if the partitioning did not apply to all the space on the disk.

After the selected the target disk, an additional window (Figure 9-15) is displayed, concerning the resizing of the partitions when the target disk is different.

13

3

13

3


9-16 77 A2 77US

In this case, the user must select the Leave remaining unused space option.

Figure 9-15. Partition Resizing Options


77 A2 77US 9-17

9.5 Errors Encountered during Cloning Operations

The error 1516 can stop the cloning. This error may have been caused by a power failure or Windows system crash while Windows operating system was writing the partition. This problem, and many other ones, can often be resolved by running chkdsk command on the affected partition when Windows has been restarted.

• run a dos command window, then go to X partition by typing cd <X>:\

• run chkdsk with switch /f, if cloning already failed

• stop Windows then clone.

In case of error #45 returned by cloning process and unsuccessful check disk, the file(s) responsible for the error can be found in a trace file created by the tool. To do so, reboot the platform with the first Deploy Center disket then type �enter� twice when the second disket is asked . Introduce the Deploy Center tool disket then launch a:\PQIMGCTR /DBG=trace.txt command. Look for the wrong files in the trace.txt file.

Reboot Windows then delete or restore the wrong file(s) from a previous NT Backup, then clone the disk once more time.

In case of other serious problems or unsuccessful command chkdsk /f, please refer to Powerquest site at http://www.powerquest.com/support/ .

9.6 Errors encountered after Restarting on the Clone

Once Windows is restarted on the clone disk, verify:

• The partitions on the active system disk (Windows, V7000, DATA) are assigned respectively with C, E, F letters (or CEF structure) using the Windows� Explorer, for example. A structure with C:\, E:\ and F:\ is essential on the disk started after the cloning. Otherwise, the user must reassign these letters to the WIN2000, V7000 and DATA partitions respectively, using standard Windows� tools.

• In Windows 2000, clone partition structure can be different of CEF�s one when started. More often, second internal disk is not more disabled and its partitions have been mounted (or used) by Windows system. Verify reference state, second internal disk status (disable) then restart cloning.

• If problem persist, see Appendix E.3 .


9-18 77 A2 77US

• In Windows 2003, security level has been increased, and new partitions are not automatically mounted at system restart. Clone partitions have a new signature (or ID) for Windows and except system one no assigned letter at restart time. Partition structure is C.

• In this case, follow the procedure below :

• Restart on the reference disk

• Verify CEF partition structure,

• In a cmd window, launch mountvol /r command then after mountvol /e command

• Shutdown

• Clone reference

• Start on clone disk

• Verify CEF partition structure

•

• The remanence of the second internal disk's Disabled status (Figure 9-16).

Figure 9-16 Checking the Disable Information for the Second Internal Disk

If it has disappeared, it must be reset using the Windows� Device Manager and right-clicking ! Disable on Disk1.

9.7 Cloning procedure with two different internal disks

When internal disks are plainly identical (same features and constructor), Disk0 (reference) and Disk1 (clone) can be physically substituted without Windows scan for hardware changes after reference or clone restart.


77 A2 77US 9-19

The �disable� feature bound to Disk1 under Windows Device Manager is preserved. Reference and clone are independent system disks. The partition structure C,E,F (for C:\, E:\ and F:\) is always valid after reference or clone restart.

When an internal disk is changed (after a hardware failure, �) with one from different features or constructor, the permutation is no more possible after cloning step. On system restart, Windows detects a new disk and removes the �disable� feature from the second internal disk. If the new disk is empty or contains no partitions, apply "disable" feature on the second disk with Windows Device Manager then follow the cloning steps (see § 9.4).

When the used disk is not empty, letters are given to second disk partitions and system files can also be allocated on these partitions.

Conflicts between partitions letters can appear and partition structure from system disk (Disk0) can be different of C,E,F. The most current one is C,H,I .

For all these reasons, the cloning procedure is changed as follow:

1. Check if Disk0 is a stand-alone Windows system disk (remove failed Disk1 then boot Windows system)

2. Check for C,E,F partition structure on Disk0 (restore it if necessary using the Windows Disk Manager then check applications consistency)

3. Insert the new disk in position Disk1 (address: Bus0, TargetId: 0, LUN: 1)

4. With Windows Device Manager, right click on platform then click Scan for Hardware Changes if necessary. Windows system launches the disk signature wizard to recognize the new disk.

5. Put "disable" feature on Disk1 when seen by Windows

6. Shut down Windows

7. Clone the system disk on Disk1

8. Do not substitute internal disks if not necessary (use only clone on recovery need)

9. To validate the clone, remove reference disk, move the clone from slot 1 to slot 0 then restart (The reference disk must not be mounted).

10. After clone validation, replace the two disks at their original location then restart the system

NOTE: If the clone must be used, remove the previous system disk from the platform then restart with the clone. Verify partition structure after restart, then clone on a new disk.


9-20 77 A2 77US

NOTE: Use NT Backup solution more often to secure the exploitation Backup.

9.8 NT Backup

This section proposes a simple, easy procedure to back up the partitions of Disk0 to a 4mm DAT cartridge. This procedure is complementary to the cloning procedure.

NT Backup is started from the Start menu: Accessories ! System Tools ! Backup by a user with Backup rights, such as the administrator.

Figure 9-17. Accessing NT Backup

The welcome screen (Figure 9-18) gives the following choices:

• Backup

• Restore

• Schedule jobs (not dealt with here)


77 A2 77US 9-21

9.8.1 Backup

Figure 9-18. NT Backup

Click on Backup Wizard to enter the backup parameters (Figure 9-19).


9-22 77 A2 77US

Figure 9-19. Parameter Selection

Select the C:\ and E:\ partitions and the system state.

NOTE: Deselect the GCOS_DISKS directory (and other directory) on each disk mounted under the GlobalDiskSpace directory on E:\ partition (Figure 9-20).


77 A2 77US 9-23

Figure 9-20. Suppress GCOS data in the backup structure.

It is up to the administrator whether to select the F:\ partition or not.

Deselect My Documents and choose 4mm DDS media type in Backup Destination.

Then click on the Start Backup button.

Wait for the window requesting information (Figure 9-21) which succeeds fugitive windows for collecting various information by Windows�.

NOTE: The user is prompted to confirm before overwriting a support (Figure 9-21).


9-24 77 A2 77US

Figure 9-21. Case with a Media Already Used

Choose Allocate this media to Backup now, which displays Figure 9-22.

Figure 9-22. Requested Information

Do not modify anything and start the Backup, represented by the progress window (Figure 9-24).

NOTE: The user is prompted to confirm for a media used previously (Figures 9-23 et 9-24).


77 A2 77US 9-25

Figure 9-23. First Confirmation for a Media Used

Figure 9-24. Second Confirmation for a Media Used

Figure 9-25. Backup Progress


9-26 77 A2 77US

At the end of the backup procedure (Figure 9-26), the user is prompted to view a report (file in text format) which summarizes the operations carried out. Close it if opened, then close the window.

Figure 9-26. End of Backup

Quit NT Backup, remove and label the cartridge and place it in a safe place.

9.8.2 Restoration

One or more problems may cause file restoration operations.

NOTE: Before starting the restoration, collect the information pertaining to V7000 using the Information Collector via the V7000 Start menu, and save this information on a 4mm DAT for analysis.

In the Restore tab, choose the DAT drive, then open out its tree structure (Figure 9-27).

NOTE: If the tree structure does not open (cartridge not generated on the actual machine or recycled), the user must force its reading and determine its contents by right-clicking on it and choosing Catalog.


77 A2 77US 9-27

Figure 9-27. Restore Menu Welcome Screen

In all cases, the restored files replace the original files. Choose Tools ! Options ! Restore and select the Always replace the file on my computer option (Figure 9-28).

Figure 9-28. Replace Files Option


9-28 77 A2 77US

Now start the restoration after selecting the parameters (Figure 9-29).

Figure 9-29. Selecting the Restoration Parameters

NOTE: If a partition is opened out to select files more selectively, additional windows are displayed. This is only advised for experienced users who know how to accurately determine the source of the problem encountered. If in doubt, restore the entire support.

Click on Start Restore.

If the system's status is restored, the user is prompted to confirm. The confirmation of this restoration must in turn be confirmed (Figure 9-30).

Figure 9-30. Confirming the Restoration

Click on the OK button to confirm.


77 A2 77US 9-29

The cartridge is read and loaded (Figure 9-31).

Figure 9-31. 4mm Cartridge Load

The progress of the restoration is displayed via a progress window (Figure 9-32).

Figure 9-32. Progress of the Restoration


9-30 77 A2 77US

The following window indicates the end of the restoration (Figure 9-33):

Figure 9-33. End of Restoration and Final Status

The user can view the report summarizing the operations performed via the Report button.

Click on the Close button to close the window, then exit NT Backup.

The restoration of the system's status requires the machine to be restarted (Figure 9-34) in order to be accepted. This should be done immediately (click on Yes).

Figure 9-34. Restart Request

KEEP THE CARTRIDGE AS A PRECAUTION, OR REUSE IT FOR A FUTURE BACKUP.


77 A2 77US 9-31

9.8.3 Troubleshooting

After you use NT Backup to restore a complete Windows 2000 computer and system state, HBA adapter drivers (Emulex), and other device drivers may not work correctly.

To resolve this issue, delete and re-install each affected device after you complete the restoration:

• Click Start, point to Settings, click Control Panel, double-click Computer Management, and then double-click Device Manager.

• Right-click a device that is affected by this issue (yellow question mark), and then click Uninstall. Repeat this step until each device that is affected by this issue is removed.

NOTE: Don't forget to uninstall Emulex HBA even there's no yellow question mark.

• Right-click the computer name in Device Manager, click Scan for hardware changes, and then follow the instructions on the screen to install the correct drivers.

If a .sys file is asked, browse on C:\WINNT\system32\drivers to find it.

If a .exe file is asked, browse on C:\WINNT\system32

Based on Microsoft Knowledge Base Article � 322649

9.8.4 Rebuild a New System Disk

To rebuild a new system disk, don't forget to build the Maintenance Partition with Express Builder CD before installing Windows 2000.

Then use NT Backup to restore a complete Windows 2000 computer and system state.

If the Maintenance Partition is not created, the restored Boot.ini file indicates Partition(2) as Boot Partition. In this case on system restart after NT Backup restore, the following message will appear:

Windows 2000 could not start because the following file is missing or corrupt. <Windows 2000 root> System 32 \ntoskrnl.exe

NOTE: Boot.ini file can be modified after Starting the Recovery Console.


9-32 77 A2 77US

9.9 Hardware mirroring for DPS7000/XTA 1X4

For new models such as 1X4 DPS7000/XTA and later, cloning of system disk with Deploy Center Tool cannot be used to secure the V7000 Platform.

The both internal disks are in Raid1 configuration managed by one LSI Logic adapter on Motherboard, and it is not possible to add a new internal disk to perform cloning such as described before.

The save process is based on the automatic resynchronisation between the two internal disks when one in changed. This resynchronisation is managed by the LSI Logic adapter and can visually be followed with ServeRAID Manager Tool (see §9.9.5).

During resynchronisation, surviving disk of Raid configuration is physically mirrored on the target disk where all previous data are erased.

Thus, save of system disk consist in removing one of the internal disks, replaced by a new one, which will be dynamically updated. The removed disk can later be used as backup one.

NOTE: The Raid1 configuration is built during manufacturing stage with ServerGuide. tool, and must not be changed or modified out of recovery process.

IMPORTANT: Thanks to automatic resynchronisation no action must be done under BIOS or with ServeRAID Manager Tool (see §9.9.5).

Four procedures are defined to secure DPS7000/XTA 1X4 models.

IMPORTANT: Three disks with identical size are necessary per rotations. A previous save is re-used to create a new one.

NOTE: Appendix E gives a disaster recovery procedure when the Raid1 Disk is broken.

13

3

13

3


77 A2 77US 9-33

9.9.1 Save of system disk

This case is similar to create a clone of system disk.

1. Stop GCOS7 then V7000

2. Shut down the Platform

3. Remove disk1 (right side in front of the Platform) and preserve it

4. Restart the Platform with only one disk

5. Connect to Windows

6. Restart V7000 then GCOS7

7. Insert the new disk in the empty slot.

8. [ Launch ServerRaid Manager tool from Start Menu/ServerRaid Manager to control the resynchronisation progress (see §9.9.5) ]

The stop duration of the platform is minimal. The total resynchronisation duration takes about 2 hours for 36GB disks.

9.9.2 Back to a steady system

This case corresponds to come back to a previous steady save when current system is unstable.



3. Remove the two internal disks in front of the Platform

4. Insert the steady backup disk in the left slot

5. Restart the Platform





•


9-34 77 A2 77US

9.9.3 Disk Substitution in case of disk Hardware Failure Windows running

1. Locate the failed disk (see §9.9.5 if necessary)

2. Remove the failed disk in front of the Platform



No need to stop GCOS7, V7000 and Windows because resynchronisation is automatic.

9.9.4 Disk substitution disk in case of disk Hardware Failure Windows stopped

Restart the platform with only one disk and insert the new disk Windows running.

9.9.5 ServerRaid manager Graphical User Interface Tool (GUI)

This Windows tool is only used to visualize the resynchronisation process between the two physical disks. Through Windows services, it can exchange information with the physical LSI Logic adapter and display them.

The GUI is launched from Start Menu/ServerRaid Manager menu.

After Controller1 and Channel1 node development, three panels are displayed (Figure 9-35):


77 A2 77US 9-35

Figure 9-35 ServerRaid Manager tool

• Left panel: raid1 configuration description and controller status

• Right panel: physical (left) and logical (right) device status

• Underside panel: log of last actions.

The progress of a pending resynchronisation can be followed by clicking on Logical Drive object in right panel (Figure 9-36) and log messages in underside panel.


9-36 77 A2 77US

Figure 9-36 Disk resynchronisation progress

This tool also permits to locate a physical disk from Raid1 configuration in front of the Platform.

Select the disk in the Physical Device part of the right panel, then right click, choose Properties then Identify Physical Drive 0 ou 1. The selected disk blinks in front of the Platform. When located, close the windows the drive light is blinking.

Status of physical disk in Raid1 configuration is also given in disk properties sheet by clicking Status option (answer will be Primary or secondary).


77 A2 77US 9-37

9.10 Hardware mirroring for DPS7000/XTA X5

For new models such as X5 DPS7000/XTA and later, cloning of system disk with Deploy Center Tool cannot be used to secure the V7000 Platform.

The both internal disks are in Raid1 configuration managed by one LSI Logic adapter on Motherboard, and it is not possible to add a new internal disk to perform cloning such as described before.

The save process is based on the automatic resynchronisation between the two internal disks when one in changed. This resynchronisation is managed by the LSI Logic adapter and can visually be followed with MegaRAID Client Tool (see §9.10.5).

During resynchronisation, surviving disk of Raid configuration is physically mirrored on the target disk where all previous data are erased.

Thus, save of system disk consist in removing one of the internal disks, replaced by a new one, which will be dynamically updated. The removed disk can later be used as backup one.

NOTE: The Raid1 configuration is built during manufacturing stage with ServerGuide. tool, and must not be changed or modified out of recovery process.

IMPORTANT: Thanks to automatic resynchronisation no action must be done under BIOS or with MegaRAID Client Tool (see §9.10.5).

Four procedures are defined to secure DPS7000/XTA X5 models.

IMPORTANT: Three disks with identical size are necessary per rotations. A previous save is re-used to create a new one.

NOTE: Appendix E gives a disaster recovery procedure when the Raid1 Disk is broken.

13

3

13

3


9-38 77 A2 77US

The front of the server is described below (Figure 9-37).

Figure 9-37 Front of X5 Model

NOTE: The Current Clone Disk (ID 2) is disconnected.

9.10.1 Save of system disk

This case is similar to create a clone of system disk.



3. Remove disk ID 1 and preserve it

4. Restart the Platform with only one disk (ID 0)


6. Launch MegaRAID Client Tool to control the resynchronisation progress (see §9.10.5)

7. Insert the new disk in the empty slot


The stop duration of the platform is minimal. The total resynchronisation duration takes about 1.5 hours for 70 GB disks.


77 A2 77US 9-39

9.10.2 Back to a steady system

This case corresponds to come back to a previous steady save when current system is unstable.



3. Remove the two internal disks in front of the Platform

4. Insert the steady backup disk in the ID 0 slot

5. Restart the Platform



8. Insert the new disk in the empty slot

9. Visualize the resynchronisation progress


9.10.3 Disk Substitution in case of disk Hardware Failure Windows running

1. Locate the failed disk (see Physical Devices Panel Figure 9-38, which gives failed disk ID in red color)

2. Remove the failed disk

3. Insert the new disk in the empty slot (ID 0 or ID 1)


No need to stop GCOS7, V7000 and Windows because resynchronisation is automatic.


9-40 77 A2 77US

9.10.4 Disk substitution disk in case of disk Hardware Failure Windows stopped

Restart the platform with only one disk (Reference or Clone) and insert the new disk Windows running.

9.10.5 MegaRAID Client Tool Graphical User Interface Tool

This Graphical User Interface (GUI) tool is only used to visualize the resynchronisation process between the two physical disks. Through Windows services, it can exchange information with the physical LSI Logic card and display them.

The GUI is launched from Start Menu/Power Console Plus/MegaRAID Client

Two modes are available (Figure9-38).

Figure 9-38 Server Selection mode

Default option is Full Access.

Select View only. Then Main Windows appears (Figure 9-39) in View Only Mode.


77 A2 77US 9-41

Figure 9-39 MegaRAID Client Main Console

Main window is divided in four parts:

• Tool Menu at the top of the window

• High Panel: managed server (local) and adapters (Only one there)

• Middle panel: physical devices status and properties

• Low panel: logical device status and properties

When a problem occurs on one physical disk, its state changes from Onln to Failed (Figure 9-40).


9-42 77 A2 77US

Figure 9-40 Disk state change

When a new disk is inserted, automatic resynchronisation starts (Figure 9-42) after SCSI rescan.

NOTE: If the state of inserted disk stayes Failed (Figure 9-40), right click on red icon disk then Properties (Figure 9-41).


77 A2 77US 9-43

Figure 9-41 Disk Status

When the disk is Failed, State field of properties page is only filled with Not Connected.

Unplug then plug the disk again in Disk ID-2 (Figure 9-37). Warning light disk must pass green then yellow for a few seconds then green again. If the warning ligfht stayes yellow, disk may not work properly.


9-44 77 A2 77US

Figure 9-42 Start of disks resynchronisation

The resynchronisation is logged (Figure 9-43) and when finished, progression window is closed. Disks state is the same (OnLine) as shown in Figure 9-39.

To see log, click on Adpater Menu then View Log.

Figure 9-43 Log File opening


77 A2 77US 9-45

9.11 Hardware mirroring for Novascale 7000

On Novascale 7000 Platform, Windows system disk is located in external Chaparral sub-system disk.

Chaparral disk sub-system (named SR-0812) contains four disks:

• two ones are in Raid1 configuration (�mirrored� in Chaparral documentation, defining an array with two members 1 and 2) and supports Windows system,

• one is in Spare state, ready to be automatically inserted in Raid1 configuration if one disk becomes unavailable,

• last one is used to backup Windows system disk when necessary (equivalent of clone for DPS 7000 XTA)

NOTE: Raid or Spare disk state is written (MetaDATA) on physical disk itself. Thus location of disks can be changed in Chaparral sub-system without state recognition problems.

One array is known at a given time.

When a disk is introduced in Chaparral disk sub-system, four cases must be considered:

• previous disk state was Spare; new state is Spare

• current disk is a new one for Chaparral sub-system; state is then Available and disk can be used as Spare if necessary

• disk was member of an array in a Chaparral sub-system but is older or newer than current disk of the bay; new state is Leftover and disk cannot be directly used by the Chaparral sub-system without disk previous Chaparral data clearing. After clearing state is Available.

• no disk from the current known array is present; the new disk becomes Member1 of the new array, which will be taken in account by Chaparral sub-system, et can be used to start Windows system. If a Spare disk is present, Raid1 configuration will be automatically rebuilt.

Chaparral sub-sytem rescans regularly the disk bay to look after changes of disks. The frequency is about 3 minutes but can be forced if necessary.


9-46 77 A2 77US

NOTE: Chaparral sub-system uses internal caches. Thus disks cannot be removed before cache cleaning. Use Hot Swap Pause command to do this.

IMPORTANT: Do not introduce an old raided disk in Chaparral sub-system disk containing a complete (or not) array. Conflicts can appear between previous raided disk and current array. Thus Chaparral sub-system can marked Leftover the bad disk.

To prevent this situation, remove the right disk(s), introduce the old raided one and mark it as Available. Then introduce the right one(s).

Chaparral sub-system management is described in �86A145EG00: BULL SR-0812 RAIDStorage System User�s Guide� documentation.

In Novascale 7000 context, a few commands must be used and will be discribed below.

• Hot Swap Pause: forces cache cleaning. Windows system must be stopped before to clean Windows caches.

Launching: System Menu ! Utilities Menu ! Hot Swap Pause

• Rescan: forces a hardware scan of the disk bay.

Launching: System Menu ! Utilities Menu ! Rescan

• Clear MetaDATA: clear disk MetaDATA.

Launching: System Menu ! Utilities Menu !Drive Utilities Menu ! Clear MetaData, then select disk to be cleared

• Adding a disk in Spare pool: adds a disk in spare pool ones

Launching: System Menu ! Pool Spare Menu ! Add Pool Spare, then select disk in proposed list

• Disk state visualization: gives the disk state, which can be Array Member, Pool Spare, Available, LetfOver.

Launching: System Menu ! Display Drive

13

3


77 A2 77US 9-47

• Array or Raid state visualization: gives the Raid state, which can be Fault-Tol (right one), Critical (only one disk is working), RCNTnn (in rebuid mode where nn corresponding to rebuild rate)

Launching: System Menu ! Array Menu ! Array Status or Drive Status

• Stop of ringing alarm: to stop alarm started on disk bay hardware incident

Launching: System Menu ! Configuration Menu ! Alarm Mute

9.11.1 Disk locations in Chaparral sub-system

The location of the connected disks in Chaparral sub-system disk is discribed in Figure 9-44.

The backup on is not connected and preserved.

RAID1 � DISC1 (ch2-Id01)

RAID1 � DISC2 (ch2-Id02)

SPARE (ch1-Id4)

Figure 9-44 Physical disk location in Chaparral sub-system disk

NOTE: Novascale 7000 documentation explains how to get this hardware running configuration.

9.11.2 Backup Disk creation

Synopsis: remove Member2 disk from current array, plug backup disk that will be erased to pass Available then Spare state, then automatic rebuild will start.


9-48 77 A2 77US

NOTE: Permanent Spare disk (Figure 4-44) is not used and kept for hardware Raid1 failure.

Chaparral commands are in bold italics.

1. Verify disks states (RAID1 � DISC1, RAID1 � DISC2 and SPARE � Figure 4-44)

2. Shutdown Windows system of the concerned partition and wait for INACTIVE state (on PAM)

3. ShutDown/Restart to stop Chaparral sub-system

4. Unplug from many centimeters RAID1-DISC1 and SPARE disks; remove RAID1-DISC2 disk and preserve it (it is now the current backup system disk)

5. Plug the previous backup disk in RAID1-DISC2 location and wait for permanent green warning light (or green LED)

6. Press ENTER to restart Chaparral sub-system

7. Display Drives to see disk state

8. If disk state is:

a. Array1 Member2 then ! Delete An Array ! Display Drives. Disk state must be Available (in RAID1-DISC2 location)

b. LeftOver then ! Clear MetaDATA ! Display Drives. Disk state must be Available (in RAID1-DISC2 location)

c. Spare ! Delete Spare ! Display Drives. Disk state must be Available (in RAID1-DISC2 location)

9. ShutDown/Restart ! confirm

10. Plug RAID1-DISC1 and wait for green LED

11. Press ENTER to reboot the Chaparral sub-system

12. Display Drives to see disk state. RAID1-DISC1 state must be Array1 Member1

13. Pool Spare Menu ! Add Spool Spare and select RAID1-DISC2 Available disk

14. Wait for a few seconds then Array Menu ! Array Status. Array must be in CRIT RCONxx% state

15. Hot Swap Pause


77 A2 77US 9-49

16. Plug the third disk SPARE and wait for green LED

17. Press ENTER to resume Hot Swap Pause command

18. Rescan ! Display Drives. Disk states must be:

a. RAID1-DISC1: Array Member 1 RCST

b. RAID1-DISC2: Array Member 2 RCST

c. SPARE :Pool Spare

19. Restart of Windows (Power ON partition on PAM) before resynchronization end

Command Array Menu ! Array Status shows resynchronization rate.

During resynchronization ends, alarm rings up. To stop it: System Menu ! Configuration Menu ! Alarm Mute.

9.11.3 Restart from an old backup disk

Synopsis: remove Member2 disk from current array, the other Raid disk is erased to pass Available then Spare state. Backup disk is then introduced to automatically rebuild Raid1 disk.

1. Verify disks states (RAID1 � DISC1, RAID1 � DISC2 and SPARE � Figure 4-44)

2. Shutdown Windows system of the concerned partition and wait for INACTIVE state (on PAM)


4. Unplug from many centimeters SPARE disk; remove RAID1-DISC2 disk and preserve it. Only RAID1-DISC1 is present in its location

5. Press ENTER to reboot Caparral sub-system

6. Display Drives to see disk state. RAID1-DISC1 must be in Array1 Member1 state

7. Delete An Array ! Display Drives. RAID1-DISC1 must be in Available state


9. Move Available disk from RAID1-DISC1 location to RAID1-DISC2 one


9-50 77 A2 77US

10. In RAID1-DISC1 location plug backup disk and wait for green LED

11. Press ENTER to reboot the Chaparral sub-system

12. Display Drives to see disk states:

a. RAID1-DISC1 must be in Array1 Member2 state

b. RAID1-DISC2 must be in Available state

13. Pool Spare Menu ! Add Pool Spare and select Available disk

14. Wait for a few seconds then Array Menu ! Array Status. Array must be in CRIT RCONxx% state

15. Hot Swap Pause

16. Plug the third disk SPARE and wait for green LED

17. Press ENTER to resume Hot Swap Pause command

18. Rescan ! Display Drive to see disk states:

a. RAID1-DISC1: Array1 Member1 RCST

b. RAID1-DISC2: Array1 Member2 RCST

a. SPARE :Pool Spare

19. Restart of Windows (Power ON partition on PAM) before resynchronization end

Command Array Menu ! Array Status shows resynchronization rate.

During resynchronization, alarm rings up. To stop it: System Menu ! Configuration Menu ! Alarm Mute.

77 A2 77US 10-1

10. Power Supply Management

10.1 Principle

This chapter concerns DPS7000 XTA platforms equipped with an APC® UPS (Uninterruptible Power Supply) and its control software application (PowerChute® Business Edition).

It describes the implementation of a mechanism on the DPS7000 XTA platform used to shut down the V7000 virtual machine after the shutdown of applications running on GCOS7 when the server switches to battery power subsequent to a drop in power or power failure.

This mechanism uses functions in the UPS management module and GCOS7 system exception management functions.

The UPS management application is used to retrieve signals sent by the UPS and to convert them into events accessible via a user interface module. From this interface, the user can associate an executable file with the event, which is activated when the event occurs.

With GCOS7, an exception system (class 0 type 14) handles power supply problems; this exception is activated on "Battery On", "Line Back" and "Battery Off" events.

On "Battery On" and "Line Back" events, specific messages (paragraph 10.2) are sent via the GCOS7 operator console, and the POWERMGT job in the SITE.STARTUP library (job to create) is activated.

This POWERMGT job's function is to shut down the applications running on GCOS7; its contents thus depend on the client applications.

On the "Battery Off" event, the TSYS power off command is activated, which effectively shuts down the V7000 virtual machine.


10-2 77 A2 77US

The principle consists in providing the UPS management module with an executable (UPSNotifMgt.exe supplied with the V7000 software) whose parameter corresponds to the event. This executable notifies the SYC which notifies the CPU which in turn initiates the appropriate system exception. Using the executable's parameter, you associate a UPS management application event with a GCOS exception (for example, on GCOS 7, the "switch to battery" event generates the 0-14 exception with the "Battery On" event").

10.2 Processing Events

• Event "Power failed"

-> execution of the UPSNotifMgt.exe executable with the POWERON and dddd parameters (number of seconds; e.g., 1800).

The first POWERON parameter initiates exception 0-14 with the "Battery On" event on GCOS7. The second parameter, in seconds (1800), indicates the time remaining before the V7000's shutdown; this delay must allow the POWERMGT job to be run, but it must be less than the UPS battery's runtime and must be calculated in order to take into account the delay before the minimum battery level signal is received (chapter 10.3.6).

This parameter is sent to GCOS7 by way of indication (it is the Low Battery Condition external event that initiates the GCOS7's shutdown, not the fact that its value reaches zero); if it exceeds the value of 2032s, then this is the value taken into account by default (the variance between this value given on input and the value displayed in the error message is due to the formats of internal calculations).

On the GCOS7 operator console:

− The following message is displayed: "* hh.mnmn POWER FAILURE: BACKUP BATTERY SWITCHED ON (1879s)"

− The POWERMGT job is activated: "STARTED POWERMGT OPERATOR P"

− The message is repeated every 10 seconds (this interval cannot be modified) while displaying the time remaining.

Power Supply Management

77 A2 77US 10-3

• Event "Power Restored"

-> execution of the UPSNotifMgt.exe executable with the LINEBACK parameter.

The LINEBACK parameter produces exception 0-14 with the "Line Back" event type on GCOS7.

On the GCOS7 operator console:

− the following message is displayed: "hh.mnmn POWER RESTORED: BACKUP BATTERY SWITCHED OFF"

− the POWERMGT job is activated: "STARTED POWERMGT OPERATOR P"

− the previous event's reiterative message is stopped. • Event "Time On Battery Threshold Exceeded"

->execution of the UPSNotifMgt.exe executable with the POWERLOW parameter. The POWERLOW parameter produces exception 0-14 with the "Battery Off" event type on GCOS7, which initiates the shutdown of GCOS7 followed by the shutdown of the V7000 virtual machine.

The following messages are displayed on the GCOS7 operator console: * AV01 EMERGENCY SHUTDOWN * AV01 REASON: POWER FAILURE

NOTE: The POWERMGT job in the SITE.STARTUP library started subsequent to exception 0-14 for the "Battery On" and "Line Back" events has 2 parameters.

The first parameter identifies the event at the origin of the job's startup; ON for the "Battery On" event and OFF for the "Line Back" event.

It is used to differentiate the processing operations in the POWERMGT job subsequent to the two aforementioned events.

The second parameter represents the time remaining before the V7000's shutdown, given as a parameter to UPSNotifMgt.exe; this parameter is only meaningful when the first parameter's value is ON.


10-4 77 A2 77US

Example of a POWERMGT job written to handle short power failures (up to 5 mins for this sample parameter definition):

POWERMGT

0 JUMP &1; 0 ON: 0 SEND ' ************************************************ ' ALL; 0 SEND ' * START THE EMERGENCY SHUTDOWN PROCEDURE * ' ALL; 0 SEND ' * IN 5 MINUTES * ' ALL; 0 SEND ' * LOSS OF POWER AND SWITCH TO BATTERY * ' ALL; 0 SEND ' *********************************************** ' ALL; 0 SEND ' * TO STOP THE PROCEDURE: CUR REQUEST=PWOFF * ' MAIN; 0 SEND ' ************************************************ ' MAIN; 0 EXDIR 'EJR POWEROFF,,SITE.STARTUP WHEN=+5M NAME=PWOFF;'; 0 JUMP FIN; 0 OFF: 0 SEND ' ************************************************ 'ALL; 0 SEND ' * CANCEL EMERGENCY SHUTDOWN PROCEDURE' ALL; 0 SEND ' * POWER BACK ON * ' ALL; 0 SEND ' ********************************************** ' ALL; 0 EXDIR 'CUR REQUEST=PWOFF; '; 0 FIN:

POWEROFF

0 SEND ' *********************************************** ' ALL; 0 I: SEND ' * START THE EMERGENCY SHUTDOWN PROCEDURE * ' ALL; 0 SEND ' * END OF BATTERY AUTONOMY * ' ALL; 0 SEND ' *********************************************** ' ALL; 0 EXDIR 'TSRV TBM1'; 0 EXDIR 'TSRV TGM1'; 0 EXDIR 'TMB KA10'; 0 EXDIR 'TMB KA1E'; 0 EXDIR 'TTSVR RAEH'; 0 EXDIR 'TTSVR OCS OCS1'; 0 EXDIR 'TTSVR OCS OCS2'; 0 EXDIR 'TCMSR'; For a power failure, the POWERMGT job is activated with the ON parameter following exception 0-14 for the "Battery On" event.

The POWEROFF job must be started 5 mins after the activation of the POWERMGT job.

If the power is restored within the 5-minute interval, the POWERMGT job is activated with the OFF parameter following exception 0-14 for the "Line Back" event, and in this case, the CUR REQUEST=PWOFF command cancels the startup of the POWEROFF job.

If the power is not restored within 5 minutes, the POWEROFF job is executed;

It stops the GCOS applications (dependent on the client site).


77 A2 77US 10-5

10.3 Implementation

• Installation of the UPS management software application: refer to the manufacturer's documentation corresponding to the software supplied with the UPS.

• Configuration of this software: refer to the manufacturer's documentation and to the chapters hereafter for details on how to configure events corresponding to the switch to battery power, the restoration of the normal power supply and the low battery problem.

NOTE: The implementation of the management of a Smart_UPS 1400 RM with the PowerChute® Business Edition software is given by way of example.

The UPS is connected to the V7000 platform via the COM1 port.

10.3.1 Startup of PowerChute® Business Edition Console

1. From the Start menu, select Programs then APC PowerChute Business Edition.

2. Select Console.

3. In the Logon dialog box, enter the User Name, Password and the Server which the console must connect to.

Figure 10-1. Console Logon Window


10-6 77 A2 77US

Click on the Connect button; the main window is displayed:

Figure 10-2. Main Window: PowerChute® Business Edition Console


77 A2 77US 10-7

From the View menu, select Device Properties then Battery Status; this menu displays the UPS battery's runtime duration ("Runtime Remaining"). This time starts to count down the moment the platform switches to battery power.

Figure 10-3. Battery Status menu in PowerChute® Business Edition


10-8 77 A2 77US

From the Device Properties menu, select Shutdown then Power Failure; select the At runtime limit option.

Figure 10-4. Power Failure Menu in PowerChute® Business Edition

NOTE: The strategy chosen for the implementation of the machine's shutdown after switching to battery power is the Maximize Runtime strategy.


77 A2 77US 10-9

10.3.2 Startup of PowerChute® Business Edition Agent

This is the PowerChute® Business Edition agent interface used to define the parameters of those events for which the UPSNotifMgt.exe executable is activated.

The selected events are: "Power Failed", "Power Restored" and "Time On Battery Threshold Exceeded".

For each of these events, you must create a command file in the following directory:

\Program Files\APC\Powerchute Business Edition\Agent\cmdfiles\

file PowerFailed.cmd @echo off rem Power Failed @START "" "C:\Program Files\Bull\V7000\Component\UPSNotifMgt.exe" POWERON 1200 @echo on file PowerRestored.cmd @echo off rem Power Restored @START "" "C:\Program Files\Bull\V7000\Component\UPSNotifMgt.exe" LINEBACK @echo on file BatteryThreshold.cmd @echo off rem Time On Battery Threshold Exceeded @START "" "C:\Program Files\Bull\V7000\Component\UPSNotifMgt.exe" POWERLOW @echo on To obtain the interface with the Powerchute Business Edition agent, key in the following address in your browser: http://localhost :3052


10-10 77 A2 77US

The following menu is displayed:

Figure 10-5. Agent Login Window


77 A2 77US 10-11

Once you have logged on to agent, the following main menu is displayed:

Figure 10-6. Main Window in PowerChute® Business Edition Agent


10-12 77 A2 77US

To obtain the list of configurable events, click on the Events field, then on the Actions item.

Figure 10-7. Event Actions Window


77 A2 77US 10-13

10.3.3 Configuring the Power Failed Event

To configure the Power Failed event, click on the Power Failed field in the Event Actions menu.

The menu displayed lists the configurable actions for this event.

Figure 10-8. Menu for the Power Failed Event

In the context of this documentation, only the Command file item is taken into account.

Select the Enable Command File Execution option.

In the Choose Command File Name field, key in the full path of the command file relative to this event:

C:\Program Files\APC\Powerchute BusinessEdition\agent\cmdfiles\ PowerFailed.cmd

In the Command File Execution Duration field, enter the time required to execute the command file and perform the corresponding action on the V7000 virtual machine.

Click on the Apply button.


10-14 77 A2 77US

10.3.4 Configuring the Power Restored Event

To configure the Power Restored event, click on the Power Restored field in the Event Actions menu.

The menu displayed lists the configurable actions for this event.

Figure 10-9. Menu for the Power Restored Event

In the context of this documentation, only the Command file item is taken into account.

Select the Enable Command File Execution option.

In the Choose Command File Name field, key in the full path of the command file relative to this event:

C:\Program Files\APC\Powerchute Business Edition\agent\cmdfiles\ PowerRestored.cmd

In the Command File Execution Duration field, enter the time required to execute the command file and perform the corresponding action on the V7000 virtual machine.

Click on the Apply button.


77 A2 77US 10-15

10.3.5 Configuring the Time on Battery Threshold Exceeded Event

To configure the Time on Battery Threshold Exceeded event, click on the Time on Battery Threshold Exceeded field in the Event Actions menu. The menu displayed lists the configurable actions for this event.

Figure 10-10. Menu for the Time on Battery Threshold Exceeded Event

In the context of this documentation, the Configure Time On Battery Threshold (figure 10-10) and Command file items (figure 10-10bis) are taken into account. In the Time On Battery Threshold field, enter the time after which the Time on Battery Threshold Exceeded event will take place once the platform has switched to battery power. Select the Enable Command File Execution option. In the Choose Command File Name field, key in the full path of the command file relative to this event: C:\Program Files\APC\Powerchute Business Edition\agent\cmdfiles\ BatteryThreshold.cmd In the Command File Execution Duration field, enter the time required to execute the command file and perform the corresponding action on the V7000 virtual machine. Click on the Apply button.


10-16 77 A2 77US

Figure 10-10 bis. Menu for the Time on Battery Threshold Exceeded Event


77 A2 77US 10-17

10.3.6 Configuring the Shutdown

Windows 2000 is shut down subsequent to the Low Battery Signal event.

To obtain the shutdown configuration menu, click on the Protected System field, then on the Shutdown Settings item.

Figure 10-11. System Shutdown Management Menu

Configure the Runtime Remaining Threshold, Low Battery Signal and OS Shutdown Delay fields to shut down the server applications and Windows 2000 correctly before the shutdown of the DPS7000 XTA platform.


10-18 77 A2 77US

10.4 Control and Errors

• If the parameter definition of the UPSNotifMgt executable is incorrect, the following error message is displayed:

Figure 10-12. Error Message: Incorrect Parameter

Click OK to close this dialog box.

Here, you must reconfigure the command file option of the action event concerned.

• If the SYC service is not started when UPSNotifMgt is executed, the following

warning message is displayed:

Figure 10-13. Warning Message: V7000 System Control Not Started

Click OK to close this dialog box. • If the V7000 virtual machine is not running when UPSNotifMgt is executed, the

following warning message is displayed:

Figure 10-14. Warning Message: V7000 Virtual Machine Not Running

Click OK to close this dialog box.


77 A2 77US 10-19

• If GCOS7 is not started when UPSNotifMgt is executed, the following warning message is displayed:

Figure 10-15. Warning Message: GCOS7 Not Operational

Click OK to close this dialog box. • For all other errors, the error is written in the V7000 Event Log file and the

following error message is displayed:

Figure 10-16. Error Message: Internal Error

Click OK to close this dialog box. • For each of the following three events, a warning message is displayed in the

V7000 System Control tool's Activity History window.

− "Power Supply On received by SYstem Control"

− "Main Power Restored received by SYstem Control"

− "Power Supply Low received by SYstem Control"


10-20 77 A2 77US

❑

47 A2 53US 11-1

11. V7000 Log Viewer Tool

The V7000 Log Viewer Tool is a Windows� application used to :

- Display Log files issued from V7000 system, as for example the specific log file: Bct-MergedV7000AndSystemLogFiles.log created by V7000 Information Collector Tool.

- Collect and merge some or all of the Event Logs Windows (Application, System)and V7000 logs(V7000, V7000_Consoles_S0, V7000_INTEROP7) of the V7000 local server, by chronological order into a unique new formatted log file .

- Collect and merge some or all of Event Logs Windows (Application, System)and V7000 logs(V7000, V7000_Consoles_S0, V7000_INTEROP7) issued of a V7000 machine, by chronological order into a unique new formatted log file .

The event records of this log file are text formatted (see Figure 11-5). Information describing logs, number of records per logs, size of logs are also stored in the log file when saved.

This tool behaves like an Editor tool with specific functions as creating new Log files, formatting the display and filtering records with several criteria.

To realize these functions five menus are proposed: File Menu , Edit Menu , View Menu, Filters Menu and Help Menu (Figure 11-1).

11-2 47 A2 53US

11.1 How to launch V7000 Log Viewer Tool

Start the V7000 Log Viewer tool via the Start Menu:

Start ! Programs ! V7000 ! BULL Services ! V7000 LogViewer .

The main window of tool is then opened (Figure 11-1).

Figure 11-1 Main window of V7000 Log Viewer Tool

47 A2 53US 11-3

11.2 V7000 Log Viewer Tool use

When the V7000 Log Viewer is just started, it proposes five menus. The commands of Edit and Filters menus are not accessible. They become available when a log file is created or opened.

To Create or Open a log file, the File Menu (Figure 11-2) must be used.

Figure 11-2. File menu

File menu can be also used to Save , Save Selection As, Print, Print Selection a log file or Exit .

To create a log file from local windows or V7000 event logs, select the command Create Log Standard, a « Create Standard Log» window (Figure 11-) is displayed.

11-4 47 A2 53US

Figure 11-3. Standard Log File Creation

The user has to give a file path name of the new Log File in �File to Create� edit box and to choose which logs he wants to collect and merge. Eventually he can introduce a comment which will be written in the generated Log File. The comment is written in the Log File on a special line beginning with "//com:...".

The user can merge all the following files into a Log File.

V7000 V7000 log

Console V7000 Console log

Interop7 V7000 Interop7 log

Application Windows Application log

System Windows System log

The button [Set all] may be used to quickly select all logs and in the same manner the button [Reset all] unselect all logs.

When the user click �OK�, the new file is created and displayed in the text area of the V7000 Log Viewer.

47 A2 53US 11-5

To create a log file from windows or V7000 event logs issued from a V7000 system, select the command Create Log External, a « Create External Log » window (Figure 11-4) is displayed.

Figure 11-4. External Log File Creation

The user has to give the file path name of the new Log File in �File to Create� edit box and to �Add� in the list of �File to collect� all the files he wants to collect and merge in this Log File. Eventually he can introduce a comment.

When the user click �OK�, the new file is created and displayed in the text area of the V7000 Log Viewer.

11-6 47 A2 53US

The display of a log File can be also obtained with the command Open Log Collect in the File menu.

Figure 11-5. Opened log File

The Log File is displayed in the text area of the V7000 Log Viewer. Inside the text area, the user can select a text by using the mouse like in all editors. When a text is selected, the user can copy it into the clipboard, print it, or save it into another file. Format of a Log File A Log file is an ASCII text file composed of several lines and each line is composed of several fields named Columns (Figure 11-6). Any text editor may be used to edit a Log file but the V7000 Log Viewer offers functions to create them, to format the display and to filter records with several criteria. These functions doesn't exist on a standard text editor. A Log File can be a collection of several logs of different natures. All these logs are formatted and merged by chronogical order into a file named a Log Collect File or more briefly a Log File. This is very useful to make a correlation when a problem occurs on a V7000 system.

47 A2 53US 11-7

Each line of the Log File begins with a letter (named the Id) which identifies the log where the information has been extracted. A Log File may contain several special lines, beginning with "//". In example, comment introduce at the Log File creation, appear as "//com:..." in the Log File.

Figure 11-6. A line format in the log File

Detail of the Log File fields in the Figure 11-6 • L :The L is a single letter which identifies the origin of this record.

V V7000 log C V7000 Console log I V7000 Interop7 log A Windows Application log S Windows System log

• Index : It's a number which identifies the record in the origin log. • Date : It's the date in ANSI format year/month/day issued from the original log. • Hour : It's the hour in format hour:minute:second, eventually followed by

millisecond, issued from the original log. • Evt ID : This field is the identification of the message in the logging

application . • Sev : This field represents the severity of the message. It may be at blank to

indicate an information, or else composed of one | two stars (**) for a warning message, or else composed of three stars (***) to indicate a major problem.

• source : This field identifies more accurately the origin source file from which

the message is yielded. • Text : It's the text of the message extracted from the original source file with all

parameters issued from the original log, and eventually with binary data converted in ASCII format if necessary. Between the text and the previous field, a vertical bar is used as separator ( | ).

11-8 47 A2 53US

Except the text field, the user may specified which field he wants to show in the text area of the Log Viewer. By default, all fields are displayed if no column is removed by the View / Columns menu (Figure 11-9). Note that Date and Hour columns are the time of recorded message.

A log file or filtered log selection can be saved. Created file have text format and can be read with another file editor.

Open a log collect file permits to edit it.

The Edit Menu (Figure 11-7) use to search for specific words or copy selected part of log to clipboard.

Figure 11-7. Edit Menu

View Menu (Figure 11-8) is used to modify fonts and displayed columns (Figure 11-9) in text area.

Figure 11-8. View Menu

47 A2 53US 11-9

Figure 11-9. Columns from View Menu

Filters menu permits to define user filters to view specific messages from opened log (Figure 11-10).

Figure 11-10. Filters Menu

11-10 47 A2 53US

Figure 11-11. Filters Selection

Six features can be used to define filters:

• Identifier of a specific log (V7000, Application, � see Figure 11-11)

• Dates intervals (Figure 11-12)

47 A2 53US 11-11

Figure 11-12. Dates selection

11-12 47 A2 53US

• Events (Figure 11-13)

Figure 11-13. Events selection

Click on Add to validate the chosen EventId.

47 A2 53US 11-13

• Key words (Figure 11-14)

Figure 11-14. Key words selection

Click on Add to validate the chosen Key word.

Filters based on Events and Key words can use lists of events or key words with Add function.

For example, filter based on EventId 02003 (IOP in V7000 log) only extracts messages in relation with it (Figure 11-15)

11-14 47 A2 53US

Figure 11-15. Filter with EventId 02003

47 A2 53US 11-15

• Severity (Figure 11-16)

Figure 11-16. Severity selection

11-16 47 A2 53US

• Sources (Figure 11-17)

Figure 11-17. Sources selection

Click on Add to validate the chosen Source.

77 A2 77US 12-1

12. V7000 Firewall Configurator

The V7000 Firewall Configurator is a Windows� application that may be executed on a �Full V7000 Server� or on a �Remote V7000 Administration Tools� installation, from Windows 2003 SP1 or Windows XP SP2.

From Windows 2003 SP1 and Windows XP SP2, a new version of the native firewall is available. The main characteristics of this firewall are the following:

• Filters incoming and outgoing connections.

• Can be configured for applications (.exe file names) or communication ports (TCP or UDP protocols).

• In case of a configured application, the communication ports used by this application are only opened when it is running.

• The activation of the firewall is available for all connections (i.e all network cards) of the platform.

Several V7000 and Interop7 components are using network facilities, and must correctly operate when the firewall is activated on the platform.

So, the goal of the V7000 Firewall Configurator application is to configure the native firewall of Windows 2003 SP1 or Windows XP SP2 platform:

• for Windows native common components necessary for both V7000 and Interop7 components, on both types (server and remote administration) of V7000 and Interop7 installations

• for V7000 and Interop7 components on both types (server and remote administration) of V7000 and Interop7 installations

• and also for factory installed third party components* on a �Full V7000 Server� installation.

*: a factory installed third party component is a network software component necessary for a general proper working of the V7000 server platform.

However, this application does not have charge of activation or deactivation of the firewall. This is under the customer responsibility.


12-2 77 A2 77US

Two operation modes are available:

• A automatic mode, used in V7000 or Interop7 installations by the suitable tools. This mode allows to configure V7000 products, respectively Interop7 products, without a manually intervention, into the native firewall. This automatic mode is briefly described below in the paragraph 12.1.

• A interactive mode, using a graphical dialog box, allowing individual modifications in V7000 and Interop7 components configuration (versus automatic configuration) and factory installed third party components configuration. This interactive mode is described below from the paragraph 12.2.

Whatever the operation mode used, information, warning and error messages are logged into the V7000 log file under a log source named V7000_FWALL.

V7000 Firewall Configurator

77 A2 77US 12-3

12.1 Automatic mode

The V7000 Firewall Configurator tool is automatically called in the following cases:

" through the V7000 Version Manager tool when a V7000 version is activated on a �Full V7000 Server� installation (case 1)

" through the Interop7 Installation program when a Interop7 server installation is made on a �Full V7000 Server� installation (case 2)

" through the V7000 Installation program when a �Remote V7000 Administration Tools� installation is made (case 3)

" through the Interop7 Installation program when a Interop7 administration installation is made on a �Remote V7000 Administration Tools� installation (case 4)

" through the V7000 Information Collector tool when a BCT is asked to collect the actual state of all components known by the firewall on a �Full V7000 Server� installation (case 5)

" through the V7000 Information Collector tool when a BCT is asked to enumerate the actual state of all components known by the firewall on a �Remote V7000 Administration Tools� installation (case 6)

12.1.1 User rights

The necessary user rights are those of the corresponding tools from which the V7000 Firewall Configurator is called:

" Administrators and V7000BullServices groups for V7000 Version Manager tool

" Administrators group for V7000 and Interop7 Installation programs

" Administrators or V7000BullServices or V7000Operators groups for V7000 Information Collector tool

If the user rights are not sufficient, the following error message is logged:

V7000 Firewall Configurator Error : Error: RC=CONFFW_INSUFFICIENT_USERRIGHTS (45002)


12-4 77 A2 77US

12.1.2 Checking of Windows version

If the Windows version is less than Windows 20003 SP1 (for a �Full V7000 Server� installation) or Windows XP SP2 (for a �Remote V7000 Administration Tools� installation), the following error message is logged:

V7000 Firewall Configurator Error : The native firewall is supported from Windows 2003 SP1 or Windows XP SP2 only.

12.1.3 Checking of Windows Firewall/Internet Connection Sharing (ICS) service state

If the service Windows Firewall/Internet Connection Sharing (ICS) is not started, the following error message is logged:

V7000 Firewall Configurator Error : The service Windows Firewall/Internet Connection Sharing (ICS) is not running.

12.1.4 Automatic mode of configuration (cases 1-4)

The automatic mode of configuration takes into account of the current state of the corresponding components.

In case of the first automatic configuration, all selected components(*) are configured (i.e enabled) in the firewall.

(*) All V7000 components are automatically selected. Interop7 components to install can be selected through the installation program.

Native Windows common components are automatically selected.

In case of a non first automatic configuration, the current state of the selected components set by a preceding use of the V7000 Firewall Configurator tool in interactive mode is kept.

The Native Windows common components are the following:

• DCOM RPC: port 135 protocol TCP

• MMC Admin : application %windir%\system32\mmc.exe


77 A2 77US 12-5

The V7000 components are the following:

• AdminServer : application <V7000 path component>\V7000_Service_VAS.exe

• Engine : application <V7000 path component>\V7000_System_Control.exe

• RCF : application <V7000 path component>\RemoteControlFacility_EXE.exe

• SDM : application <V7000 path component>\V7000_SharedDiskManager.exe

• GCOS7 Consoles : application <V7000 path component>\ClientConsole.exe

<V7000 path component> is the components path directory of a V7000 installation.

On a �Remote V7000 Administration Tools� installation, the only managed component is GCOS7 Consoles.

The Interop7 components are the following:

• AdminServer : application <Interop7 path component>\Interop7Adm.exe

• SockG7 Std : application <Interop7 path component\v7sg7.exe

• SockG7 TDS : application <Interop7 path component>\v7sg7tds.exe

• GFTP Client : application <Interop7 path component>\gftp.exe

• GFTP Server : application <Interop7 path component>\gftpd.exe

• NT7GW : application <Interop7 path component>\NT7GW.exe

• NT7 Admin : application <Interop7 path component>\NT7ADM.exe

• OpenGTW : application <Interop7 path component>\openGTW.exe

• OpenGTW Admin : application <Interop7 path component>\openGtwAdm.exe


12-6 77 A2 77US

• OpenGTW Print : application <Interop7 path component>\opgtwPrint.exe

• CNDSA : application <Interop7 path component>\cndsa.exe

• G7CN : application <Interop7 path component>\G7CN.exe

• G7Ping : application <Interop7 path component>\G7ping.exe

<Interop7 path component> is the components path directory of a Interop7 installation

On a �Remote V7000 Administration Tools� installation, , the only managed components are G7CN and G7Ping, providing that the �Interop7 Basic Administration Tools� option was chosen at installation time.

When an automatic configuration session of the V7000 Firewall Configurator is executed, a corresponding text file is created in the <Trace> directory of a �Full V7000 Server� or of a �Remote V7000 Administration Tools� installation. The name of this text file is:

• V7000ConfigFirewall_V7000_Server.txt (case 1)

• V7000ConfigFirewall_Interop7_Server.txt (case 2)

• V7000ConfigFirewall_V7000_RemoteAdministration.txt (case 3)

• V7000ConfigFirewall_Interop7_RemoteAdministration.txt (case 4)

This file is re-created at each automatic session.

12.1.5 Automatic mode of enumeration (cases 5-6)

The V7000 Information Collector tool calls the V7000 Firewall Configurator to enumerate the actual state of all components known by the firewall, whatever the selected option in the main dialog box of the V7000 Information Collector tool.

When an automatic enumeration session of the V7000 Firewall Configurator is executed, a corresponding text file is created in the <Trace> directory of a �Full V7000 Server� or of a �Remote V7000 Administration Tools� installation. The name of this text file is:

• V7000ConfigFirewall_BCT_Server.txt (case 5)

• V7000ConfigFirewall_BCT_RemoteAdministration.txt (case 6)

This file is re-created at each automatic session.


77 A2 77US 12-7

12.2 V7000 Firewall Configurator User Rights

12.2.1 No user rights

The use of the V7000 Firewall Configurator is reserved for members belonging both to the Administrators and V7000BullServices groups for the complete set of functionalities.

If the user does not belongs neither to the Administrators group, nor to the V7000BullServices group, the following error dialog box is displayed:

Figure 12-1 No user rights (on a �Full V7000 Server� installation)

Figure 12-2 No user rights (on a �Remote V7000 Administration Tools� installation)

Moreover, the following error message is logged:

V7000 Firewall Configurator Error : Error: RC=CONFFW_INSUFFICIENT_USERRIGHTS (45002)


12-8 77 A2 77US

12.2.2 Read only restricted rights

If the user belongs to the Administrators group but not to the V7000BullServices group, the following warning dialog box is displayed before the main dialog box:

Figure 12-3 Read only restricted rights (Administrators group only on a �Full V7000 Server� installation)

Figure 12-4 Read only restricted rights (Administrators group only on a �Remote V7000 Administration Tools� installation)


77 A2 77US 12-9

If the user belongs to the V7000BullServices group but not to the Administrators group, the following warning dialog box is displayed before the main dialog box:

Figure 12-5 Read only restricted rights (V7000BullServices group only on a �Full V7000 Server� installation)

Figure 12-6 Read only restricted rights (V7000BullServices group only on a �Remote V7000 Administration Tools� installation)

In these two cases, the use of the tool is restricted to a visualization mode only.


12-10 77 A2 77US

12.2.3 Full user rights

If the user belongs both to the Administrators and V7000BullServices groups, the following warning dialog box is displayed before the main dialog box:

Figure 12-7 Full user rights (on a �Full V7000 Server� installation)

Figure 12-8 Full user rights (on a �Remote V7000 Administration Tools� installation)


77 A2 77US 12-11

12.3 Checking of Windows version

If the Windows version is less than Windows 20003 SP1 (for a �Full V7000 Server� installation) or Windows XP SP2 (for a �Remote V7000 Administration Tools� installation), the following error dialog box is displayed:

Figure 12-9 Windows version less than W2003 SP1 or XP SP2 (on a �Full V7000 Server� installation)

Figure 12-10 Windows version less than W2003 SP1 or XP SP2 (on a �Remote V7000 Administration Tools� installation)


V7000 Firewall Configurator Error : The native firewall is supported from Windows 2003 SP1 or Windows XP SP2 only.


12-12 77 A2 77US

12.4 Checking of Windows Firewall/Internet Connection Sharing (ICS) service state

If the service Windows Firewall/Internet Connection Sharing (ICS) is not started, the following error dialog box is displayed:

Figure 12-11 Service Windows Firewall/Internet Connection Sharing (ICS) not started (on a �Full V7000 Server� installation)

Figure 12-12 Service Windows Firewall/Internet Connection Sharing (ICS) not started (on a �Remote V7000 Administration Tools� installation)


V7000 Firewall Configurator Error : The service Windows Firewall/Internet Connection Sharing (ICS) is not running.


77 A2 77US 12-13

12.5 Checking of a V7000 Firewall Configurator previous instance

If an instance of the V7000 Firewall Configurator application is already running, the following error dialog box is displayed:

Figure 12-13 Previous instance running (on a �Full V7000 Server� installation)

Figure 12-14 Previous instance running (on a �Remote V7000 Administration Tools� installation)


V7000 Firewall Configurator Error : One instance of this application is already running.


12-14 77 A2 77US

12.6 Components managed in main dialog box

The main dialog box of the V7000 Firewall Configurator application is composed of four group boxes corresponding to the four components types:

• Native Windows common components

• V7000 components

• Interop7 components

• Third party components

12.6.1 Native Windows common components

Two native Windows components are managed:

• DCOM RPC: port 135 protocol TCP

• MMC Admin : application %windir%\system32\mmc.exe

These components are necessary for DCOM remote administration.

The �Common components� group box is always available for update, both on a �Full V7000 Server� and on a �Remote V7000 Administration Tools� installation, unless the use of the tool is restricted to a visualization mode only (see 12.2.2). In this case, all common components are grayed and are checked or unchecked depending on their state in the firewall.

12.6.2 V7000 components

Five V7000 components are managed:

• AdminServer : application <V7000 path component>\V7000_Service_VAS.exe

• Engine : application <V7000 path component>\V7000_System_Control.exe

• RCF : application <V7000 path component>\RemoteControlFacility_EXE.exe

• SDM : application <V7000 path component>\V7000_SharedDiskManager.exe


77 A2 77US 12-15

• GCOS7 Consoles : application <V7000 path component>\ClientConsole.exe

<V7000 path component> is the components path directory of a V7000 installation.

The �V7000 components� group box is always available for update, both on a �Full V7000 Server� and on a �Remote V7000 Administration Tools� installation, unless the use of the tool is restricted to a visualization mode only (see 12.2.2). In this case, all V7000 components are grayed and are checked or unchecked depending on their state in the firewall.

Nevertheless, on a �Remote V7000 Administration Tools� installation, the following components are not available (grayed): AdminServer, Engine, RCF, SDM. They are also always unchecked.

12.6.3 Interop7 components

Thirteen Interop7 components are managed:

• AdminServer : application <Interop7 path component>\Interop7Adm.exe

• SockG7 Std : application <Interop7 path component\v7sg7.exe

• SockG7 TDS : application <Interop7 path component>\v7sg7tds.exe

• GFTP Client : application <Interop7 path component>\gftp.exe

• GFTP Server : application <Interop7 path component>\gftpd.exe

• NT7GW : application <Interop7 path component>\NT7GW.exe

• NT7 Admin : application <Interop7 path component>\NT7ADM.exe

• OpenGTW : application <Interop7 path component>\openGTW.exe

• OpenGTW Admin : application <Interop7 path component>\openGtwAdm.exe

• OpenGTW Print : application <Interop7 path component>\opgtwPrint.exe


12-16 77 A2 77US

• CNDSA : application <Interop7 path component>\cndsa.exe

• G7CN : application <Interop7 path component>\G7CN.exe

• G7Ping : application <Interop7 path component>\G7ping.exe

<Interop7 path component> is the components path directory of a Interop7 installation.

The �Interop7 components� group box is available for update when Interop7 is installed, on a �Full V7000 Server� or on a �Remote V7000 Administration Tools� installation.

On a �Remote V7000 Administration Tools� installation, the following components are not available (grayed): AdminServer, SockG7 Std, SockG7 TDS, GFTP Client, GFTP Server, NT7GW, NT7 Admin, OpenGTW, OpenGTW Admin, OpenGTW Print, CNDSA. They are also always unchecked.

On a �Remote V7000 Administration Tools� installation, the components G7CN and G7Ping only are available, providing that the �Interop7 Basic Administration Tools� option was chosen at installation time. Else, they are unchecked but not grayed.

If Interop7 is not installed, the �Interop7 components� group box is not available (grayed) and all components are grayed and unchecked.

If the use of the tool is restricted to a visualization mode only (see 12.2.2), all components are grayed and are checked or unchecked depending on their state in the firewall.

12.6.4 Third party components

The number of third party components is given by the presence of specific configuration files in the <Config> path directory of a �Full V7000 Server� installation. These files are built by the engineering team and supplied to the factory team at post-process time.

If no such files are found, the �Third party components� group box is not available (grayed) and no component is listed.

On a �Remote V7000 Administration Tools� installation, the �Third party components� group box is not available (grayed) and no component is listed.


77 A2 77US 12-17

If the use of the tool is restricted to a visualization mode only (see 12.2.2), the components are not available and are checked or unchecked depending on their state in the firewall.


12-18 77 A2 77US

12.7 Components state towards the firewall at main dialog box opening time

For each component managed by the V7000 Firewall Configurator application, the real current state towards the firewall is displayed:

• checked if enabled

• unchecked if disabled

If the application detects that the configuration of a component has been updated by another tool (Windows Security Center/Windows Firewall for example):

• a Warning icon is displayed nearby the component, for Windows native, V7000 and Interop7 components

• a yellow highlight of the component name followed by the Warning word for factory installed third party components (on a �Full V7000 Server� installation only)

In this case, the following text is also displayed at the bottom of the main dialog box:

Warning icon(s) (Common/V7000/Interop7 components) or yellow highlighted Warning text(s) (Third party components) mean that the firewall configuration has been modified outside this tool. In this case, it is strongly recommended to reestablish the desired configuration with this tool.

12.7.1 Case of Interop7 components uninstall

When Interop7 components are uninstalled from the server, neither the V7000 Firewall Configurator nor the firewall himself are informed Thus, the current state of these components towards the firewall is kept and the V7000 Firewall Configurator displays it as follow at main dialog box opening time:

• checked if enabled

• unchecked if disabled


77 A2 77US 12-19

12.8 Components state validation/invalidation in main dialog box

The main dialog box is displayed with three buttons: OK, Cancel and Apply.

At main dialog box opening time:

• if the use of the tool is restricted to a visualization mode only (see 12.2.2), the OK button is the only available (not grayed)

• else (full user rights), the Apply button is unavailable (grayed), unless Warning(s) are displayed (see 12.7), and OK and Cancel buttons are available (not grayed)

The modification of a component (checked if not checked, or unchecked if checked):

• removes the corresponding Warning if it exists

• makes the Apply button available

When the Apply button is available (not grayed) (modification(s) in progress or Warning(s) displayed), a click on this button makes it unavailable (grayed) and:

• if modification(s) was (were) in progress, it is (they are) validated

• if Warning(s) was (were) displayed, the following information dialog box is displayed:

Figure 12-15 No more Warning(s) after Apply button clicked (on a �Full V7000 Server� installation)


12-20 77 A2 77US

Figure 12-16 No more Warning(s) after Apply button clicked (on a �Remote V7000 Administration Tools� installation)

and the Warning(s) and the specific text at the bottom of the main dialog box (see 12.5) are removed when this dialog box is closed. The state of the components is validated.

The main dialog box is not closed when the Apply button is clicked.

When the Apply button is unavailable (grayed) (no modification in progress and no Warning displayed):

• a click on the OK button validates the displayed state of the components and closes the main dialog box

• a click on the Cancel button keeps the displayed state of the components and closes the main dialog box


77 A2 77US 12-21

When the Apply button is available (not grayed) (modification(s) in progress or Warning(s) displayed), a click on the OK button:

• validates modification(s) in progress (if any)

• displays the following information dialog box if Warning(s) was (were) displayed:

Figure 12-17 No more Warning(s) after OK button clicked (on a �Full V7000 Server� installation)

Figure 12-18 No more Warning(s) after OK button clicked (on a �Remote V7000 Administration Tools� installation)

and the Warning(s) and the specific text at the bottom of the main dialog box (see 12.7) are removed when this dialog box is closed. The state of the components is validated.

The main dialog box is closed when the OK button is clicked.

When the Apply button is available (not grayed) (modification(s) in progress or Warning(s) displayed), a click on the Cancel button invalidates modification(s) in progress (if any) and closes the main dialog box.


12-22 77 A2 77US

When the Apply or the OK button is clicked, if the application(s) associated with (a) checked component(s) is (are) not found on the system, the following warning dialog box is displayed:

Figure 12-19 Application(s) not found on system (on a �Full V7000 Server� installation)

This example is given for third party components no present (or with erroneous specific configuration files built by the engineering team) on a �Full V7000 Server� installation.

In this case, the components are unchecked in the main dialog box.

NB: The same situation can be arrived for V7000 and Interop7 components on a �Full V7000 Server� installation or on a �Remote V7000 Administration Tools� installation.


77 A2 77US 12-23

12.9 Main dialog box use cases

This paragraph shows different aspects of the main dialog box following various use cases and their combinations:

• �Full V7000 Server� installation

• �Remote V7000 Administration Tools� installation

• Interop7 installed/not installed

• Warning(s) displayed at opening time

• use of the tool restricted to a visualization mode only

• third party components specific configuration files not present


12-24 77 A2 77US

12.9.1 Use case 1

�Full V7000 Server� installation, Interop7 not installed, no third party component, no Warning displayed at opening time.

Figure 12-20 Main dialog box at opening time (use case 1)

Main dialog box at opening time: all common and V7000 components of a �Full V7000 Server� installation are enabled in the firewall and have been previously updated with the V7000 Firewall Configurator, �Interop7 components� and �Third party components� group boxes are unavailable (grayed), Apply button is unavailable (grayed).


77 A2 77US 12-25

12.9.2 Use case 2

�Remote V7000 Administration Tools� installation, Interop7 not installed, no Warning displayed at opening time.


Main dialog box at opening time: all common and V7000 components of a �Remote V7000 Administration Tools� installation are enabled in the firewall and have been previously updated with the V7000 Firewall Configurator, �Interop7 components� and �Third party components� group boxes are unavailable (grayed), Apply button is unavailable (grayed).


12-26 77 A2 77US

12.9.3 Use case 3

�Full V7000 Server� installation, Interop7 installed, no third party component, no Warning displayed at opening time.


Main dialog box at opening time: all common, V7000 and Interop7 components of a �Full V7000 Server� installation are enabled in the firewall and have been previously updated with the V7000 Firewall Configurator, �Third party components� group box is unavailable (grayed), Apply button is unavailable (grayed).


77 A2 77US 12-27

12.9.4 Use case 4

�Full V7000 Server� installation, Interop7 not installed, third party components correctly installed, no Warning displayed at opening time.


Main dialog box at opening time: all common, V7000 and founded third party components* of a �Full V7000 Server� installation are enabled in the firewall and have been previously updated with the V7000 Firewall Configurator, �Interop7 components� group box is unavailable (grayed), Apply button is unavailable (grayed) (*these third party components are examples only)


12-28 77 A2 77US

12.9.5 Use case 5

�Full V7000 Server� installation, Interop7 not installed, third party components correctly installed, Warnings displayed at opening time.



77 A2 77US 12-29

Main dialog box at opening time:

• the common component DCOM RPC is enabled in the firewall but has not been previously updated with the V7000 Firewall Configurator.

• the common component MMC Admin is disabled in the firewall but has not been previously updated with the V7000 Firewall Configurator.

• the V7000 component AdminServer is disabled in the firewall but has not been previously updated with the V7000 Firewall Configurator.

• the V7000 component Engine is enabled in the firewall and has been previously updated with the V7000 Firewall Configurator.

• the V7000 component RCF is disabled in the firewall but has not been previously updated with the V7000 Firewall Configurator.

• the V7000 component SDM is disabled in the firewall and has been previously updated with the V7000 Firewall Configurator.

• the V7000 component GCOS7 Consoles is enabled in the firewall but has not been previously updated with the V7000 Firewall Configurator.

• the third party component* GTS Agent is enabled in the firewall but has not been previously updated with the V7000 Firewall Configurator.

• the third party component* Navisphere Agent is disabled in the firewall but has not been previously updated with the V7000 Firewall Configurator.

• the third party component* Netop Host is enabled in the firewall and has been previously updated with the V7000 Firewall Configurator.

A specific text is displayed at the bottom of the main dialog box, �Interop7 components� group box is unavailable (grayed), Apply button is available (not grayed).

*these third party components are examples only

If the common component MMC Admin is now checked, if the V7000 component AdminServer is now checked, if the V7000 component Engine is now unchecked, if the V7000 component GCOS7 Consoles is now unchecked, if the third party component Navisphere Agent is now checked, the main dialog box is as follow:


12-30 77 A2 77US

Figure 12-25 Main dialog box after some components update (use case 5)

The Warning icons are removed nearby the corresponding common and V7000 components, the third party component* Navisphere Agent is no more yellow highlighted.

*this third party component is an example only


77 A2 77US 12-31

If the Apply button is clicked, the following information message box is displayed:

Figure 12-26 No more Warning(s) after Apply button clicked (use case 5)

After closing the information dialog box, the main dialog box is as follow:


12-32 77 A2 77US

Figure 12-27 Main dialog box after Apply button clicked (use case 5)

No more Warning icons, no more yellow highlighted third party component is displayed, the specific text at the bottom of the main dialog box has been removed, the Apply button is unavailable (grayed): the state towards the firewall of all components has been validated through the V7000 Firewall Configurator.


77 A2 77US 12-33

12.9.6 Use case 6

�Full V7000 Server� installation, Interop7 not installed, third party components correctly installed, no Warning displayed at opening time, use of the V7000 Firewall Configurator restricted to a visualization mode only.


Main dialog box at opening time: all common, V7000 and third party components are unavailable (grayed for common and V7000 components, not grayed for third party components), the OK button is the only available.


12-34 77 A2 77US

12.9.7 Use case 7

�Full V7000 Server� installation, Interop7 not installed, third party components not correctly installed (erroneous specific configuration files), no Warning displayed at opening time.



77 A2 77US 12-35

Main dialog box at opening time: all common and V7000 components of a �Full V7000 Server� installation are enabled in the firewall and have been updated with the V7000 Firewall Configurator, the third party component* GTS Agent is enabled in the firewall and has been updated with the V7000 Firewall Configurator, the third party components* ThirdComponent1, ThirdComponent2 and ThirdComponent3 have erroneous specific configuration files.

*these third party components are examples only

If the third party components ThirdComponent1, ThirdComponent2 and ThirdComponent3 are checked and then the Apply button is clicked, the following warning message box is displayed

Figure 12-30 Application(s) not found on system (use case 7)

and these third party components are unchecked.


12-36 77 A2 77US

12.10 Interactive session file

When an interactive session of the V7000 Firewall Configurator is executed, a corresponding text file is created in the <Trace> directory of a �Full V7000 Server� or of a �Remote V7000 Administration Tools� installation. The name of this text file is:

• V7000ConfigFirewall_Interactive_Server.txt on a �Full V7000 Server� installation

• V7000ConfigFirewall_Interactive_RemoteAdministration.txt on a �Remote V7000 Administration Tools� installation

This file is re-created at each interactive session. The historic of the last session is stored in this file.

77 A2 77US 1

13. Load Galileo Firmware

The Load Galileo Firmware application supplies a Graphical User Interface for updating the firmware version of a Galileo device directly from V7000 software, without specific connection and materials between the Diane server and the Galileo device.

The supply modes of .scs files corresponding to the new firmware version are kept unchanged as previously.

Information, warning and error messages are logged into the V7000 log file under a log source named V7000_GALILEO.

This tool is reserved for Bull Support.

Notes Complementary to this documentation, HTML Helps are accessible from the Help menu (or from the F1 key) of the Graphical User Interface.


2 77 A2 77US

13.1 Load Galileo Firmware User Rights

The use of the Load Galileo Firmware application is reserved for members belonging to the V7000BullServices group.

If the user does not to the V7000BullServices group, the following error dialog box is displayed:

Figure 13-1 No user rights

and the Load Galileo Firmware application is ended.

The corresponding error event is logged:

Load Galileo Firmware Error : You do not belong to V7000BullServices group. You are not allowed to use this tool.

If the user belongs to the V7000BullServices group, the following warning dialog box is displayed before the main dialog box:

Figure 13-2 Full user rights

Load Galileo Firmware

77 A2 77US 3

13.2 Checking of a Load Galileo Firmware previous instance

If an instance of the Load Galileo Firmware application is already running, the following error dialog box is displayed:

Figure 13-3 Previous instance running

and the 2nd instance of the application is ended.


Load Galileo Firmware Error : One instance of this application is already running.


4 77 A2 77US

13.3 Initialization checking

During the main dialog box initialization, the following checking are made:

" If no Galileo device is found on the Diane server, the following information message box is displayed:

Figure 13-4 No Galileo device

and the Load Galileo Firmware application is ended.

" The V7000 active configuration (if any) is opened then read from the corresponding .g7c file.

1- If the V7000 active configuration cannot be opened, the following warning message box is displayed:

Figure 13-5 V7000 active configuration warning at opening

The corresponding warning event is logged:

Load Galileo Firmware Warning : V7000 Active Configuration file cannot be opened -> Cause=<cause> IOsError=<error>


77 A2 77US 5

2- If the V7000 active configuration cannot be read, the following warning message box is displayed:

Figure 13-6 V7000 active configuration warning at reading


Load Galileo Firmware Warning : V7000 Active Configuration file cannot be read -> RC=<reason>

In these both cases, no V7000 configuration is considered as active from the Load Galileo Firmware application point of view, and thus, a GCOS7 operator must check the PX resources state and, if necessary, hold them using the MDHW PXnn OUT command before firmware updating.

3- If the V7000 active configuration is not at the last version format, the following warning message box is displayed:

Figure 13-7 V7000 active configuration not at last version format


Load Galileo Firmware Warning : V7000 active configuration not at last version format -> V7000 Infos could to be not displayed.

In this case, a GCOS7 operator must check the PX resources state and, if necessary, hold them using the MDHW PXnn OUT command before firmware updating.


6 77 A2 77US

After these checking, the main dialog box is opened and looks like the following:

Figure 13-8 Main dialog box at opening time

See the next paragraphs for details.


77 A2 77US 7

13.4 Galileo device selection

The Windows device corresponding to the target Galileo is selected using a combo box displaying the following informations:

• Device

Windows name of the device under the form Tape<n> corresponding to the target Galileo. This information is always displayed.

Example: Tape1

• Identifier

Character string identifying the Galileo device. This information is always displayed.

Example: 2AI PowerSave

• SCSI Address

Four decimal numbers representing the SCSI address, respectively the (Port Bus Target LUN), of the Galileo device. This information is always displayed.

Example: 6 0 0 0 (Port=6 Bus=0 Target=0 LUN=0)

• WWPN (optional)

Sixteen hexadecimal digits representing the WWPN (World Wide Port Name) of the Galileo sub-system. This information is displayed only from Windows 2003 SP1 and if the Galileo device is connected to the Diane server through a Fiber Channel connection.

Example: 50:06:04:84:3D:48:F0:CD


8 77 A2 77US

• V7000 Infos (optional)

If the Galileo device is configured in the active V7000 configuration, the corresponding PXU number and GCOS7 device external name are displayed.

Example: PX54 CTP9

Notes • At main dialog box opening, the first alphabetical Windows device

corresponding to a Galileo device is displayed in the combo box.

• If a (new) V7000 configuration is activated when the Load Galileo Firmware application is running, the instance of the application must be closed and then re-launched to take into account of the new activated V7000 configuration.

Figure 13-9 List of Windows device corresponding to target Galileo

In this example, Tape1 and Tape3 are connected through Fiber Channel (WWPN present), Tape1 and Tape4 are configured in the active V7000 configuration (respectively in PX54/CTP9 and PX10/CT4G).


77 A2 77US 9

13.5 Firmware file selection

The .scs file corresponding to the new Galileo firmware version is selected using the File To Download Browse... button.

The opened file dialog box filters the files of type: Galileo Firmware File (*.scs).

Figure 13-10 Galileo firmware file dialog box

The supply modes of .scs files corresponding to the new firmware version are not described here, but are kept unchanged as previously.

Select the desired .scs file and click Open. Then, the main dialog box looks like the following:


10 77 A2 77US

Figure 13-11 Firmware file .scs selected

After the firmware file has been selected, the Download button is available (no more grayed).


77 A2 77US 11

13.6 Activate the updating processing

The Galileo firmware version updating is activated using the Download button.

The Download button is grayed if a firmware file .scs is not selected.

If PX resources managing cartridges are allocated at firmware updating time, the following warning message box is displayed:

Figure 13-12 PX resource(s) allocated at firmware updating time

and the firmware updating is not processed.

In this case, a GCOS7 operator must held the PX resources using the MDHW PXnn OUT command.

If no PX resource managing cartridges are allocated at firmware updating time, the following confirmation dialog box is displayed:

Figure 13-13 Confirmation dialog box before updating

If the answer is No, the firmware updating is not processed.


12 77 A2 77US

If the answer is Yes, the firmware updating begins. During the updating phase:

• All controls on the main dialog box are inaccessible: Device combo box cannot be opened, Browse..., Download and Quit button are grayed

• If (Close button of the main dialog box) is clicked, the following error message box is displayed:

Figure 13-14 Updating in progress when Close button clicked

• The following message is blinking at the bottom of the main dialog box:

Galileo Firmware corresponding to Tape<n> device is being updated. Please wait...

Before the Galileo firmware version updating, a file corresponding to the previous firmware version is saved in the <Trace> directory of the V7000 installation. The name of this file is under the form:

Galileo_Firmware_Tape<n>_<yyyy>_<mm>_<dd>_<hh>_<mm>_<ss>.scs

where:

Tape<n> is the Windows device name corresponding to the Galileo device

<yyyy>_<mm>_<dd>_<hh>_<mm>_<ss> represents the date and time of the file creation

Example: Galileo_Firmware_Tape1_2006_01_13_14_58_32.scs


77 A2 77US 13

If possible, this file is copied under the same name into the directory where the new Galileo firmware version file was selected. If this copy is not possible, the following warning box is displayed:

Figure 13-15 Saved firmware file cannot be copied

These files (or only the first one if the copy is not possible) are displayed in the grayed edit box named Saved Files Name of Previous Firmware at the successfully end of the updating/re-initialization phase.

If the new and the current firmware version are not compatible, the following error message box is displayed:

Figure 13-16 Galileo firmware versions incompatible

and the firmware updating is not processed. Nevertheless, the current firmware version is still active.


14 77 A2 77US

When updating and re-initialization are successfully completed, the following information message box is displayed:

Figure 13-17 Firmware updating and re-initialization successful

When updating is successfully completed but, if after 1 minute, the re-initialization is not complete, the following warning message box is displayed:

Figure 13-18 Firmware updating successful but not re-initialization

In this case, check the complete re-initialization on the Galileo panel before processing a new updating.

In the two preceding cases, the controls on the main dialog box are accessible again for processing a new updating.


77 A2 77US 15

At the end of the successfully updating/re-initialization phase, the main dialog box looks like the following:

Figure 13-19 Saved previous firmware files displayed at the end of the updating/re-initialization phase

If, after 2 minutes, the updating is not terminated, the following error message box is displayed:

Figure 13-20 Timeout during updating processing

In this case, only the Quit button is accessible. Quit the application then re-launch it for processing a new updating.


16 77 A2 77US

13.6.1 Specific error messages displayed and logged during previous firmware saving

In these cases, the previous firmware saving is aborted, and thus, the firmware updating is not processed.

The corresponding error events are logged:

Load Galileo Firmware Error : SaveCurrentFirmwareVersion() (<id>): DataTransferLength=<length> (erroneous value)

Load Galileo Firmware Error : SaveCurrentFirmwareVersion() (<id>): WriteFile() -> dwNbBytesToWrite=<nbbytes> dwNbBytesWritten=<nbbytes>

Load Galileo Firmware Error : SaveCurrentFirmwareVersion() (<id>): Bad size of firmware: <size>


77 A2 77US 17

13.6.2 Specific error messages displayed and logged during new firmware updating

In this case, the firmware updating is not processed.


Load Galileo Firmware Error : DeviceIoControl() -> Status:<status> SC/ASC/ASCQ:<sc>/<asc>/<ascq>


18 77 A2 77US

13.7 Generic error messages

If an exception occurs, the following error message box is displayed:

and the application is ended.


Load Galileo Firmware Error : An unexpected exception occurs -> a V7000 dump file is produced.

If an error occurs when a Win32 or a V7000 function is called, the following error message box is displayed:

Following the phase where this error arrives, the Load Galileo Firmware application is ended, or the previous firmware saving is aborted and/or the firmware updating is not processed.


Load Galileo Firmware Error : <Internal function> (<id>): <Win32 or V7000 function> -> RC=<reason>

77 A2 77US 1

14. V7000 Performance Log

The V7000 Performance Log supplies a Graphical User Interface for auditing V7000 software and Windows system components on a DPS 7000 XTA or Novascale 7000 Platform.

This tool is reserved for Bull Support, and can be launched from V7000 Start Menu.

It must be used when performance problems or conflicts between Windows and V7000 components occur on a V7000 Server.

Results of selected counters audit are saved in binary files in V7000 Trace directory. These files are collected by Information Collector Tool in BCT files.

Main window is shown in Figure 14-1.

Figure 14-1 Main window of V7000 Performance Log Tool


2 77 A2 77US

Two domains are plugged-in:

- System Overview, Standard Windows Perfmon collect, which samples Windows system behavior

- Specific V7000_Collect_perfMon, which samples V7000 Components behavior and Windows System.

Auditing can be started or stopped by right clicking on selected domain.

14.1 Start of Auditing

Right click on selected domain, then Start (Figure 14-2).

Figure 14-2 Start of Domain auditing

Red icon before domain name becomes green (Figure 14-3) and collect starts.

For V7000, result is saved in the circular file under Log File Name parameter.

Names of file use following naming convention, depending of Platform local time:

V7000_Collect_PerfMon_MMddhhmm.blg

where MM is month, dd is day, hh is hour and mm is minute.

V7000 Performance Log

77 A2 77US 3

Files are saved in C:\Program Files\Bull\V7000\Trace directory on DPS 7000 XTA Paltform, and in C:\Program Files (x86)\Bull\V7000\Trace directory on Novascale 7000 Platform.

14.2 Stop of Auditing

Right click on selected domain, then Start (Figure 14-3).

Figure 14-3 Stop of Domain auditing

Green icon before domain name becomes red (Figure 14-2) and collect stops.

Properties of a domain can be modified on Bull Support request. Right-click on selected domain then open Properties page (Figure 14-4).


4 77 A2 77US

Figure 14-4 Properties of V7000 domain

IMPORTANT: Do not forget that V7000_Collect_PerfMon_MMddhhmm.blg log file is circular and can be overwritten several times. For analyze purpose, first run Information Collector Tool (BCT). Then send BCT file to GCOS7 Support.

13

3

77 A2 77US A-1

A. V7000 Resources: Description

Each DPS 7000/XTA controller or device has a different External Identification, composed of 4 alphanumerical characters, broken down into:

• an External Type (2 letters), defining the resource family,

• an External Name (2 letters or digits), identifying the resource within its family.

Naming devices and controllers is explained in detail in Appendix B.

A.1 90xx

SYSTEM RESOURCE V7000 EXTERNAL IDENTIFICATION : CP01 PHYSICAL TYPE : 00 STANDARD SRST INDEX : 0002 SOFTWARE VISIBLE ATTRIBUTES 1E : 4 SEQUENCE NUMBER : yyyy lowest 4 characters of the system serial number (90xx are the 4 highest) COMPUTED SOFTWARE VISIBLE ATTRIBUTES 30 : 4 TOTAL PHYSICAL MEMORY SIZE : 32 KB binary coded

NOTE: These values are subject to change as new models are introduced during DIANE service life.


A-2 77 A2 77US

A.2 CONS

CONSOLE V7000 EXTERNAL IDENTIFICATION : LNxx PHYSICAL NAME : FEyy PHYSICAL TYPE : 07 SOFTWARE VISIBLE ATTRIBUTES None CONSOLE INDICATOR �C� / �2� / �3� (= different value) COMPUTED SOFTWARE VISIBLE ATTRIBUTES E4150000 yy LC number (between 01 and 03)

NOTE: This resource cannot be seen in the Configuration Editor. It is automatically generated when the SRST is built.

V7000 Resources: Description

77 A2 77US A-3

A.3 CPM-V7

PRINTER INPUT / OUTPUT MODULE CONTROLLER V7000 EXTERNAL IDENTIFICATION : UCxx PHYSICAL NAME : yy00 PHYSICAL TYPE : 04 NUMBER OF LOGICAL CHANNELS : 1 SOFTWARE VISIBLE ATTRIBUTES 18 : 2 Greatest LC attached to this controller (2 decimal characters) COMPUTED SOFTWARE VISIBLE ATTRIBUTES PIO CODE E0 PIO FLAG 0 DVMGT CODE 6 DEVICE ATTRIBUTES 0490


A-4 77 A2 77US

A.4 CT-V7

CARTRIDGE DEVICE V7000 EXTERNAL IDENTIFICATION : CTxx PHYSICAL NAME : yyzz PHYSICAL TYPE : 07 NUMBER OF LOGICAL CHANNELS : 1 SOFTWARE VISIBLE ATTRIBUTES 18 :1 SEQUENTIAL CARTRIDGE LOADER Y (Yes) b (no) 19 :1 DATA COMPACTION Y (Yes) b (no) 1A :1 TRACKS b (M6) D (36T) C (M5) 1B :1 DENSITY TYPE 2 (M6->35/75 Mb/sq. inc) 5 (36T) 1C :1 LIBRARY Y (Yes) b (no) COMPUTED SOFTWARE VISIBLE ATTRIBUTES PIO CODE 51 (if M6), 54 (if 36T), 52(if M5) PIO FLAG 0 DVMGT CODE C DEVICE ATTRIBUTES 8000 (if LIB) or 0000 (else) + 0400 (if M6), 1000 (if 36T) or 0800 (if M5) + 0080 (if Sequential Cartridge Loader) + 0200 (if 36T: Data Compaction) + 0003 (if M6: Bi-density) + 0200 (if /C) Example:

GCOS7 device identification is function of Device Attribute: - if 0800/0880 : CT/M5, or if 8800: CT/LIB/M5 - if 0A00/0A80 : CT/M5 or CT/M5/C, or if 8A00: CT/LIB/M5 or CT/LIB/M5/C - if 1200/1280 : CT/36T or CT/36T/C, or if 9200: CT/LIB/36T or CT/LIB/36T/C

CT/M6 = 0403 CT/M6 SCL = 0483 CT/36T/C = 1200 CT/LIB/36T/C = 9200 CT/36T/C SCL = 1280 CT/M5/LIB/C = 8A00


77 A2 77US A-5

A.5 EMU-V7

EMULATED CONTROLLER V7000 EXTERNAL IDENTIFICATION : UCxx PHYSICAL NAME : FE00 PHYSICAL TYPE : 04 SOFTWARE VISIBLE ATTRIBUTES 18 : 2 Greatest LC attached to this controller (2 decimal characters) COMPUTED SOFTWARE VISIBLE ATTRIBUTES E0061040


In the SRST, it is seen with the model name: AUSP � Initial System Load (ISL) is dependent on this name.


A-6 77 A2 77US

A.6 ELT

ETHERNET TERMINATOR V7000 EXTERNAL IDENTIFICATION : LTxx PHYSICAL NAME : yyzz PHYSICAL TYPE : 07 NUMBER OF LOGICAL CHANNELS : 2 SOFTWARE VISIBLE ATTRIBUTES None COMPUTED SOFTWARE VISIBLE ATTRIBUTES PIO CODE F1 PIO FLAG 0 DVMGT CODE 5 DEVICE ATTRIBUTES 0000

NOTE: The LTxx items described in the Configuration Editor are in 6 or 8 LTxx and LT.. pairs, starting with an odd LC for LTxx and an even LC for LT.. .

6 LT pairs are described for an NCC telecom PX. 8 LT pairs are described for an LNM telecom PX.

E.g.: The following 6 ELT pairs are described on PC=40 :

LT41 - LT.. ( PCLC 4001 & 4002), LT42 - LT.. ( PCLC 4003 & 4004), LT43 - LT.. ( PCLC 4005 & 4006), LT44 - LT.. ( PCLC 4007 & 4008), LT45 - LT.. ( PCLC 4009 & 400A), LT46 - LT.. ( PCLC 400B & 400C),


77 A2 77US A-7

A.7 ETHA

ETHERNET ADAPTER V7000 EXTERNAL IDENTIFICATION : EAxx PHYSICAL NAME : xxyy PHYSICAL TYPE : 05 NUMBER OF LOGICAL CHANNELS : n number of LC (ELT) connected SOFTWARE VISIBLE ATTRIBUTES None COMPUTED SOFTWARE VISIBLE ATTRIBUTES FFF0000 xx PC number of the related controller (NCC-V7) yy LC number of the first ELT connected to this controller


Cf. A.6 � ELT

For a NCC controller 6 ELT resources are defined: (PCLC xx01, xx03, xx05, xx07, xx09 and xx0B). So, n = 12 (X�0C�) and yy = 01 for the related adapter.

For a LNM controller 8 ELT resources are defined: (PCLC xx01, xx03, xx05, xx07, xx09, xx0B, xx0D and xx0F). So, n = 16 (X�10�) and yy = 01 for the related adapter.


A-8 77 A2 77US

A.8 FSA

DISK DEVICE V7000 EXTERNAL IDENTIFICATION : MSxx PHYSICAL NAME : yyzz PHYSICAL TYPE : 07 NUMBER OF LOGICAL CHANNELS : 1 SOFTWARE VISIBLE ATTRIBUTES None COMPUTED SOFTWARE VISIBLE ATTRIBUTES PIO CODE 31 PIO FLAG 0 DVMGT CODE 1 DEVICE ATTRIBUTES 8080 Table A-1. List of Disks Supported by V7000 and Corresponding Sizes

External Type (seen in the

Configuration Editor)

Size in GB (1024**3)

Size in Bytes (Decimal)

Number of data-blocks

(Hexadecimal)

Number of data-blocks (Decimal)

Internal Type

V7000 2.0 GB 2 2147483648 400000 4194304 1C V7000 4.0 GB 4 4294967296 800000 8388608 1E V7000 8.0 GB 8 8589934592 1000000 16777216 22 V7000 9.0 GB 9 9663676416 1200000 18874368 23


77 A2 77US A-9

A.9 IOP-V7

INPUT/OUTPUT PROCESSOR V7000 EXTERNAL IDENTIFICATION : IOxx PHYSICAL NAME : 01xx PHYSICAL TYPE : 22 SOFTWARE VISIBLE ATTRIBUTES None COMPUTED SOFTWARE VISIBLE ATTRIBUTES FFF0 0000 Attached to CP01 resource xx = {00, 01, 02, 03, 04, 05, 06, 07}


A-10 77 A2 77US

A.10 IP-V7

INSTRUCTION PROCESSING UNIT V7000 EXTERNAL IDENTIFICATION : IPxx PHYSICAL NAME : 00xx PHYSICAL TYPE : 08 SOFTWARE VISIBLE ATTRIBUTES None COMPUTED SOFTWARE VISIBLE ATTRIBUTES FFF0 0000 Attached to CP01 resource xx = 00, 01, 02, 03, 04, 05, 06, 07, 08, 09, 0A, 0B, 0C, 0D, 0E, 0F, 10, 11, 12, 13, 14, 15, 16, 17 according to the V7000 model (Cf. CP01 description)


77 A2 77US A-11

A.11 LNM-V7

NETWORKING COMMUNICATION CONTROLLER (LNM) V7000 EXTERNAL IDENTIFICATION : Ucx0 PHYSICAL NAME : yy00 PHYSICAL TYPE : 04 NUMBER OF LOGICAL CHANNELS : 1 SOFTWARE VISIBLE ATTRIBUTES 18 : 2 Greatest LC attached to this controller (2 decimal characters) COMPUTED SOFTWARE VISIBLE ATTRIBUTES PIO CODE E0 PIO FLAG 0 DVMGT CODE 6 DEVICE ATTRIBUTES 0290


A-12 77 A2 77US

A.12 MEM-V7

MAIN MEMORY UNIT V7000 EXTERNAL IDENTIFICATION : MUxx PHYSICAL NAME : 00xx PHYSICAL TYPE : 03 SOFTWARE VISIBLE ATTRIBUTES 16 : 1 MEMORY UNIT SIZE n (expressed in 16 MB numbers) COMPUTED SOFTWARE VISIBLE ATTRIBUTES FFF0 0001 Attached to CP01 resource xx = 00, 01, 02, 03, 04, 05, 06, 07


77 A2 77US A-13

A.13 MSP-V7

MASS STORAGE PROCESSOR V7000 EXTERNAL IDENTIFICATION : MCxx PHYSICAL NAME : yy00 PHYSICAL TYPE : 04 NUMBER OF LOGICAL CHANNELS : 1 SOFTWARE VISIBLE ATTRIBUTES 18 : 2 Greatest LC attached to this controller (2 decimal characters) COMPUTED SOFTWARE VISIBLE ATTRIBUTES PIO CODE 30 PIO FLAG 0 DVMGT CODE 6 DEVICE ATTRIBUTES 0880


A-14 77 A2 77US

A.14 NCC-V7

NETWORKING COMMUNICATION CONTROLLER (NCC) V7000 EXTERNAL IDENTIFICATION : Ucx0 PHYSICAL NAME : yy00 PHYSICAL TYPE : 04 NUMBER OF LOGICAL CHANNELS : 1 SOFTWARE VISIBLE ATTRIBUTES 18 : 2 Greatest LC attached to this controller (2 decimal characters) COMPUTED SOFTWARE VISIBLE ATTRIBUTES PIO CODE E0 PIO FLAG 0 DVMGT CODE 6 DEVICE ATTRIBUTES 0290


77 A2 77US A-15

A.15 PR90

PRINTER V7000 EXTERNAL IDENTIFICATION : PRxx PHYSICAL NAME : yyzz PHYSICAL TYPE : 07 NUMBER OF LOGICAL CHANNELS : 1 SOFTWARE VISIBLE ATTRIBUTES None COMPUTED SOFTWARE VISIBLE ATTRIBUTES PIO CODE E3 PIO FLAG 0 DVMGT CODE 4 DEVICE ATTRIBUTES 201F


A-16 77 A2 77US

A.16 PSI-V7

INPUT OUTPOUT INTERFACE V7000 EXTERNAL IDENTIFICATION : PCxx (xx hexa digits) PHYSICAL NAME : 00xx PHYSICAL TYPE : 02 SOFTWARE VISIBLE ATTRIBUTES 18 :2 PC NUMBER xx Copied from the external name COMPUTED SOFTWARE VISIBLE ATTRIBUTES FFF0 0001 Attached to IO resource IO00 00=< xx =< 07 IO01 10=< xx =< 17 IO02 20=< xx =< 27 IO03 30=< xx =< 37 IO04 40=< xx =< 47 IO05 50=< xx =< 57 IO06 60=< xx =< 67 IO07 70=< xx < 77 PX77 is not explicitly used on V7000



77 A2 77US A-17

A.17 PXD-V7

DISK INPUT/OUTPUT MODULE V7000 EXTERNAL IDENTIFICATION : PXxx PHYSICAL NAME : 00yy PHYSICAL TYPE : 12 SOFTWARE VISIBLE ATTRIBUTES 16 : 2 SMALLEST PHYSICAL CHANNEL NUMBER nn External Name of the smallest PCxx connected to this PXU, hexadecimal. 18 :2 GREATEST PHYSICAL CHANNEL NUMBER nn External Name of the greatest PCxx connected to this PXU, hexadecimal. COMPUTED SOFTWARE VISIBLE ATTRIBUTES FFF0 0001 Attached to IO resource IO00 00=< xx =< 07 00=< yy =< 07 IO01 10=< xx =< 17 08=< yy =< 0F IO02 20=< xx =< 27 10=< yy =< 17 IO03 30=< xx =< 37 18=< yy =< 1F IO04 40=< xx =< 47 20=< yy =< 27 IO05 50=< xx =< 57 28=< yy =< 2F IO06 60=< xx =< 67 30=< yy =< 37 IO07 70=< xx =< 77 38=< yy =< 3F


A-18 77 A2 77US

A.18 PXL-V7

NETWORK INPUT/OUTPUT MODULE (LNM) V7000 EXTERNAL IDENTIFICATION : PXxx PHYSICAL NAME : 00yy PHYSICAL TYPE : 12 SOFTWARE VISIBLE ATTRIBUTES 16 : 2 SMALLEST PHYSICAL CHANNEL NUMBER nn External Name of the smallest PCxx connected to this PXU, hexadecimal. 18 :2 GREATEST PHYSICAL CHANNEL NUMBER nn External Name of the greatest PCxx connected to this PXU, hexadecimal. COMPUTED SOFTWARE VISIBLE ATTRIBUTES FFF0 0001 Attached to IO resource IO00 00=< xx =< 07 00=< yy =< 07 IO01 10=< xx =< 17 08=< yy =< 0F IO02 20=< xx =< 27 10=< yy =< 17 IO03 30=< xx =< 37 18=< yy =< 1F IO04 40=< xx =< 47 20=< yy =< 27 IO05 50=< xx =< 57 28=< yy =< 2F IO06 60=< xx =< 67 30=< yy =< 37 IO07 70=< xx =< 77 38=< yy =< 3F


77 A2 77US A-19

A.19 PXN-V7

NETWORK INPUT/OUTPUT MODULE (NCC) V7000 EXTERNAL IDENTIFICATION : PXxx PHYSICAL NAME : 00yy PHYSICAL TYPE : 12 SOFTWARE VISIBLE ATTRIBUTES 16 : 2 SMALLEST PHYSICAL CHANNEL NUMBER nn External Name of the smallest PCxx connected to this PXU, hexadecimal. 18 :2 GREATEST PHYSICAL CHANNEL NUMBER nn External Name of the greatest PCxx connected to this PXU, hexadecimal. COMPUTED SOFTWARE VISIBLE ATTRIBUTES FFF0 0001 Attached to IO resource IO00 00=< xx =< 07 00=< yy =< 07 IO01 10=< xx =< 17 08=< yy =< 0F IO02 20=< xx =< 27 10=< yy =< 17 IO03 30=< xx =< 37 18=< yy =< 1F IO04 40=< xx =< 47 20=< yy =< 27 IO05 50=< xx =< 57 28=< yy =< 2F IO06 60=< xx =< 67 30=< yy =< 37 IO07 70=< xx =< 77 38=< yy =< 3F


A-20 77 A2 77US

A.20 PXP-V7

PRINTER INPUT/OUTPUT MODULE V7000 EXTERNAL IDENTIFICATION : PXxx PHYSICAL NAME : 00yy PHYSICAL TYPE : 12 SOFTWARE VISIBLE ATTRIBUTES 16 : 2 SMALLEST PHYSICAL CHANNEL NUMBER nn External Name of the smallest PCxx connected to this PXU, hexadecimal. 18 :2 GREATEST PHYSICAL CHANNEL NUMBER nn External Name of the greatest PCxx connected to this PXU, hexadecimal. COMPUTED SOFTWARE VISIBLE ATTRIBUTES FFF0 0001 Attached to IO resource IO00 00=< xx =< 07 00=< yy =< 07 IO01 10=< xx =< 17 08=< yy =< 0F IO02 20=< xx =< 27 10=< yy =< 17 IO03 30=< xx =< 37 18=< yy =< 1F IO04 40=< xx =< 47 20=< yy =< 27 IO05 50=< xx =< 57 28=< yy =< 2F IO06 60=< xx =< 67 30=< yy =< 37 IO07 70=< xx =< 77 38=< yy =< 3F


77 A2 77US A-21

A.21 PXT-V7

CARTRIDGE INPUT/OUTPUT MODULE V7000 EXTERNAL IDENTIFICATION : PXxx PHYSICAL NAME : 00yy PHYSICAL TYPE : 12 SOFTWARE VISIBLE ATTRIBUTES 16 : 2 SMALLEST PHYSICAL CHANNEL NUMBER nn External Name of the smallest PCxx connected to this PXU, hexadecimal. 18 :2 GREATEST PHYSICAL CHANNEL NUMBER nn External Name of the greatest PCxx connected to this PXU, hexadecimal. COMPUTED SOFTWARE VISIBLE ATTRIBUTES FFF0 0001 Attached to IO resource IO00 00=< xx =< 07 00=< yy =< 07 IO01 10=< xx =< 17 08=< yy =< 0F IO02 20=< xx =< 27 10=< yy =< 17 IO03 30=< xx =< 37 18=< yy =< 1F IO04 40=< xx =< 47 20=< yy =< 27 IO05 50=< xx =< 57 28=< yy =< 2F IO06 60=< xx =< 67 30=< yy =< 37 IO07 70=< xx =< 77 38=< yy =< 3F


A-22 77 A2 77US

A.22 RMSC

REMOTE MAINTENANCE CONSOLE V7000 EXTERNAL IDENTIFICATION : LN06 PHYSICAL NAME : FE05 PHYSICAL TYPE : 07 SOFTWARE VISIBLE ATTRIBUTES None CONSOLE INDICATOR �b� COMPUTED SOFTWARE VISIBLE ATTRIBUTES E4150000



77 A2 77US A-23

A.23 TC-V7

CARTRIDGE SUBSYSTEM CONTROLLER V7000 EXTERNAL IDENTIFICATION : TCxx PHYSICAL NAME : yy00 PHYSICAL TYPE : 04 NUMBER OF LOGICAL CHANNELS : 1 SOFTWARE VISIBLE ATTRIBUTES 18 : 2 Greatest LC attached to this controller (2 decimal characters) COMPUTED SOFTWARE VISIBLE ATTRIBUTES PIO CODE 50 PIO FLAG 0 DVMGT CODE 6 DEVICE ATTRIBUTES 8020 (high throughput)


A-24 77 A2 77US

A.24 TDEV

TIME and DEVIATION DEVICE V7000 EXTERNAL IDENTIFICATION : LN07 PHYSICAL NAME : FE06 PHYSICAL TYPE : 07 SOFTWARE VISIBLE ATTRIBUTES None CONSOLE INDICATOR: �b� COMPUTED SOFTWARE VISIBLE ATTRIBUTES E4150000


77 A2 77US B-1

B. V7000 Resources: External Identification

B.1 Naming Controllers and Devices

Each DPS 7000/XTA controller or device has a different External Identification composed of 4 alphanumerical characters, broken down into:

• an External Type (2 letters), defining the resource family,

• an External Name (2 letters or digits), identifying the resource within its family.

Each DPS 7000/XTA controller manages a maximum of 4 LC, EXCEPT telecom controllers which manage 12 or 16.

EXCEPTION: TELECOM CONTROLLERS AND LINES Rules for naming telecom controllers and lines are different. Cf. B.1.3

B.1.1 External Name

The External Name of controllers and devices is generated by the Configuration Editor : 32 (10 + 22) possible characters and 32*32 = 1024 combinations.

The Configuration Editor generates a unique External Name for each device, without taking the resource families into account (except LTxx telecom lines). When a device has 2 access paths, the first path only is taken into consideration when naming the device.

All the devices of a V7000 configuration (except ELT) have different External Names. The External Name of a given device is calculated from its PCLC value. Each controller (except telecom ones) has the same External Name than the first device (LC=01) connected to it.

13

3


B-2 77 A2 77US

The character to the left of the External Name is allocated according to the PC Numbers (Letters I, L, O and Q are not used to avoid error). The character to the right of the External Name is allocated according the PC Number and the LC Number (digit 0 and letters I, O and Q are not used to avoid error and homonymy with telecom controllers External Names).

Table B-2 to B-9 indicate External Name characters:

B.1.2 External Type

The External Type of controllers and devices is allocated in compliance with Table B-1:

Table B-1. V7000 Resource Type and Family

External Type Resource Family CP System Resource (Global Information) CT Cartridge Device EA Ethernet Adaptor IO Input / Output Processor IP Instruction Processing LN Console Line LT Telecom Line MC Disk Controller MS Disk Device MU Memory Unit PC Input / Output Interface PR Printer Device PX Input / Output Module TC Cartridge Controller UC Printer Controller UC Network Controller UC Emulated Controller

The External Type entries shaded in this table are not seen by the Configuration Editor since the corresponding resources are automatically generated in the SRST.

IMPORTANT: Use the same External Name for a controller (LC=0) and for the first device (LC=01) attached to the said controller. The result (except telecom) is indicated in Tables B-3 to B-10, given that �xx� represents the External Type of a device and �yC� represents the External Type of a controller. PC FE is reserved for the emulation of LNs implicitly declared in the SRST. PC FF is illegal.

13

3

V7000 Resources: External Identification

77 A2 77US B-3

B.1.3 Controllers and Telecom Lines

Rules for naming telecommunication controllers and lines are different:

Telecom Controller (Model = LNM-V7, NCC-V7)

External Type = UC

External Name = x0 (x digit from 0 to 7).

The right-hand character (x) is equal to the IOP Number, given that each DPS 7000/XTA has only one telecom PX, therefore only one controller per IOP.

Telecom Adapter (Model = ETHA)

External Type = EA

External Name = x1 (the same x as for the parent controller).

Telecom Line (Model = ELT)

External Type = LT

External Name = x1 to x6 or x8 (in increments of 1).

The right-hand digit is a decimal. The left-hand digit (x) is the same as for the parent controller. It is not to be forgotten that an LT.. item is generated for each LTxx item. There are therefore 6 (or 8) LT pairs (LTx1 LT.., LTx2 LT.., LTx6 LT..[, LTx8 LT..]).


B-4 77 A2 77US

Table B-2. External Identification of Controllers & Devices Connected to IO00

PXU Controllers Devices (LC=01)

Devices (LC=02)

Devices (LC=03)

Devices (LC=04)

PX00 pc00_lc00 yC01 pc00_lc01 xx01 pc00_lc02 xx02 pc00_lc03 xx03 pc00_lc04 xx04

pc01_lc00 yC05 pc01_lc01 xx05 pc01_lc02 xx06 pc01_lc03 xx07 pc01_lc04 xx08

pc02_lc00 yC09 pc02_lc01 xx09 pc02_lc02 xx0A pc02_lc03 xx0B pc02_lc04 xx0C

pc03_lc00 yC0D pc03_lc01 xx0D pc03_lc02 xx0E pc03_lc03 xx0F pc03_lc04 xx0G

PX01 pc04_lc00 yC0H pc04_lc01 xx0H pc04_lc02 xx0J pc04_lc03 xx0K pc04_lc04 xx0L

pc05_lc00 yC0M pc05_lc01 xx0M pc05_lc02 xx0N pc05_lc03 xx0P pc05_lc04 xx0R

pc06_lc00 yC0S pc06_lc01 xx0S pc06_lc02 xx0T pc06_lc03 xx0U pc06_lc04 xx0V

pc07_lc00 yC0W pc07_lc01 xx0W pc07_lc02 xx0X pc07_lc03 xx0Y pc07_lc04 xx0Z



pc0A_lc00 yC19 pc0A_lc01 xx19 pc0A_lc02 xx1A pc0A_lc03 xx1B pc0A_lc04 xx1C

pc0B_lc00 YC1D pc0B_lc01 xx1D pc0B_lc02 xx1E pc0B_lc03 xx1F pc0B_lc04 xx1G

PX03 pc0C_lc00 yC1H pc0C_lc01 xx1H pc0C_lc02 xx1J pc0C_lc03 xx1K pc0C_lc04 xx1L

pc0D_lc00 yC1M pc0D_lc01 xx1M pc0D_lc02 xx1N pc0D_lc03 xx1P pc0D_lc04 xx1R

pc0E_lc00 yC1S pc0E_lc01 xx1S pc0E_lc02 xx1T pc0E_lc03 xx1U pc0E_lc04 xx1V

pc0F_lc00 yC1W pc0F_lc01 xx1W pc0F_lc02 xx1X pc0F_lc03 xx1Y pc0F_lc04 xx1Z












pc1B_lc00 yC3D pc1B_lc01 xx3D pc1B_lc02 xx3E pc1B_lc03 xx3F pc1B_lc04 xx3G






77 A2 77US B-5



Devices (LC=02)

Devices (LC=03)

Devices (LC=04)


































B-6 77 A2 77US



Devices (LC=02)

Devices (LC=03)

Devices (LC=04)
















pc4F_lc00 YC9W pc4F_lc01 xx9W pc4F_lc02 xx9X pc4F_lc03 xx9Y pc4F_lc04 xx9Z

PX24 pc50_lc00 yCA1 pc50_lc01 xxA1 pc50_lc02 xxA2 pc50_lc03 xxA3 pc50_lc04 xxA4

pc51_lc00 yCA5 pc51_lc01 xxA5 pc51_lc02 xxA6 pc51_lc03 xxA7 pc51_lc04 xxA8

pc52_lc00 yCA9 pc52_lc01 xxA9 pc52_lc02 xxAA pc52_lc03 xxAB pc52_lc04 xxAC

pc53_lc00 yCAD pc53_lc01 xxAD pc53_lc02 xxAE pc53_lc03 xxAF pc53_lc04 xxAG

PX25 pc54_lc00 yCAH pc54_lc01 xxAH pc54_lc02 xxAJ pc54_lc03 xxAK pc54_lc04 xxAL

pc55_lc00 yCAM pc55_lc01 xxAM pc55_lc02 xxAN pc55_lc03 xxAP pc55_lc04 xxAR

pc56_lc00 yCAS pc56_lc01 xxAS pc56_lc02 xxAT pc56_lc03 xxAU pc56_lc04 xxAV

pc57_lc00 yCAW pc57_lc01 xxAW pc57_lc02 xxAX pc57_lc03 xxAY pc57_lc04 xxAZ

PX26 pc58_lc00 yCB1 pc58_lc01 xxB1 pc58_lc02 xxB2 pc58_lc03 xxB3 pc58_lc04 xxB4

pc59_lc00 yCB5 pc59_lc01 xxB5 pc59_lc02 xxB6 pc59_lc03 xxB7 pc59_lc04 xxB8

pc5A_lc00 yCB9 pc5A_lc01 xxB9 pc5A_lc02 xxBA pc5A_lc03 xxBB pc5A_lc04 xxBC

pc5B_lc00 yCBD pc5B_lc01 xxBD pc5B_lc02 xxBE pc5B_lc03 xxBF pc5B_lc04 xxBG

PX27 pc5C_lc00 yCBH pc5C_lc01 xxBH pc5C_lc02 xxBJ pc5C_lc03 xxBK pc5C_lc04 xxBL

pc5D_lc00 yCBM pc5D_lc01 xxBM pc5D_lc02 xxBN pc5D_lc03 xxBP pc5D_lc04 xxBR

pc5E_lc00 yCBS pc5E_lc01 xxBS pc5E_lc02 xxBT pc5E_lc03 xxBU pc5E_lc04 xxBV

pc5F_lc00 yCBW pc5F_lc01 xxBW pc5F_lc02 xxBX pc5F_lc03 xxBY pc5F_lc04 xxBZ


77 A2 77US B-7



Devices (LC=02)

Devices (LC=03)

Devices (LC=04)

PX30 pc60_lc00 yCC1 pc60_lc01 xxC1 pc60_lc02 xxC2 pc60_lc03 xxC3 pc60_lc04 xxC4

pc61_lc00 yCC5 pc61_lc01 xxC5 pc61_lc02 xxC6 pc61_lc03 xxC7 pc61_lc04 xxC8

pc62_lc00 yCC9 pc62_lc01 xxC9 pc62_lc02 xxCA pc62_lc03 xxCB pc62_lc04 xxCC

pc63_lc00 yCCD pc63_lc01 xxCD pc63_lc02 xxCE pc63_lc03 xxCF pc63_lc04 xxCG

PX31 pc64_lc00 yCCH pc64_lc01 xxCH pc64_lc02 xxCJ pc64_lc03 xxCK pc64_lc04 xxCL

pc65_lc00 yCCM pc65_lc01 xxCM pc65_lc02 xxCN pc65_lc03 xxCP pc65_lc04 xxCR

pc66_lc00 yCCS pc66_lc01 xxCS pc66_lc02 xxCT pc66_lc03 xxCU pc66_lc04 xxCV

pc67_lc00 yCCW pc67_lc01 xxCW pc67_lc02 xxCX pc67_lc03 xxCY pc67_lc04 xxCZ

PX32 pc68_lc00 yCD1 pc68_lc01 xxD1 pc68_lc02 xxD2 pc68_lc03 xxD3 pc68_lc04 xxD4

pc69_lc00 yCD5 pc69_lc01 xxD5 pc69_lc02 xxD6 pc69_lc03 xxD7 pc69_lc04 xxD8

pc6A_lc00 yCD9 pc6A_lc01 xxD9 pc6A_lc02 xxDA pc6A_lc03 xxDB pc6A_lc04 xxDC

pc6B_lc00 yCDD pc6B_lc01 xxDD pc6B_lc02 xxDE pc6B_lc03 xxDF pc6B_lc04 xxDG

PX33 pc6C_lc00 yCDH pc6C_lc01 xxDH pc6C_lc02 xxDJ pc6C_lc03 xxDK pc6C_lc04 xxDL

pc6D_lc00 yCDM pc6D_lc01 xxDM pc6D_lc02 xxDN pc6D_lc03 xxDP pc6D_lc04 xxDR

pc6E_lc00 yCDS pc6E_lc01 xxDS pc6E_lc02 xxDT pc6E_lc03 xxDU pc6E_lc04 xxDV

pc6F_lc00 YCDW pc6F_lc01 xxDW pc6F_lc02 xxDX pc6F_lc03 xxDY pc6F_lc04 xxDZ

PX34 pc70_lc00 yCE1 pc70_lc01 xxE1 pc70_lc02 xxE2 pc70_lc03 xxE3 pc70_lc04 xxE4

pc71_lc00 yCE5 pc71_lc01 xxE5 pc71_lc02 xxE6 pc71_lc03 xxE7 pc71_lc04 xxE8

pc72_lc00 yCE9 pc72_lc01 xxE9 pc72_lc02 xxEA pc72_lc03 xxEB pc72_lc04 xxEC

pc73_lc00 yCED pc73_lc01 xxED pc73_lc02 xxEE pc73_lc03 xxEF pc73_lc04 xxEG

PX35 pc74_lc00 yCEH pc74_lc01 xxEH pc74_lc02 xxEJ pc74_lc03 xxEK pc74_lc04 xxEL

pc75_lc00 yCEM pc75_lc01 xxEM pc75_lc02 xxEN pc75_lc03 xxEP pc75_lc04 xxER

pc76_lc00 yCES pc76_lc01 xxES pc76_lc02 xxET pc76_lc03 xxEU pc76_lc04 xxEV

pc77_lc00 yCEW pc77_lc01 xxEW pc77_lc02 xxEX pc77_lc03 xxEY pc77_lc04 xxEZ

PX36 pc78_lc00 yCF1 pc78_lc01 xxF1 pc78_lc02 xxF2 pc78_lc03 xxF3 pc78_lc04 xxF4

pc79_lc00 yCF5 pc79_lc01 xxF5 pc79_lc02 xxF6 pc79_lc03 xxF7 pc79_lc04 xxF8

pc7A_lc00 yCF9 pc7A_lc01 xxF9 pc7A_lc02 xxFA pc7A_lc03 xxFB pc7A_lc04 xxFC

pc7B_lc00 yCFD pc7B_lc01 xxFD pc7B_lc02 xxFE pc7B_lc03 xxFF pc7B_lc04 xxFG

PX37 pc7C_lc00 yCFH pc7C_lc01 xxFH pc7C_lc02 xxFJ pc7C_lc03 xxFK pc7C_lc04 xxFL

pc7D_lc00 yCFM pc7D_lc01 xxFM pc7D_lc02 xxFN pc7D_lc03 xxFP pc7D_lc04 xxFR

pc7E_lc00 yCFS pc7E_lc01 xxFS pc7E_lc02 xxFT pc7E_lc03 xxFU pc7E_lc04 xxFV

pc7F_lc00 yCFW pc7F_lc01 xxFW pc7F_lc02 xxFX pc7F_lc03 xxFY pc7F_lc04 xxFZ


B-8 77 A2 77US



Devices (LC=02)

Devices (LC=03)

Devices (LC=04)

PX40 pc80_lc00 yCG1 pc80_lc01 xxG1 pc80_lc02 xxG2 pc80_lc03 xxG3 pc80_lc04 xxG4

pc81_lc00 yCG5 pc81_lc01 xxG5 pc81_lc02 xxG6 pc81_lc03 xxG7 pc81_lc04 xxG8

pc82_lc00 yCG9 pc82_lc01 xxG9 pc82_lc02 xxGA pc82_lc03 xxGB pc82_lc04 xxGC

pc83_lc00 yCGD pc83_lc01 xxGD pc83_lc02 xxGE pc83_lc03 xxGF pc83_lc04 xxGG

PX41 pc84_lc00 yCGH pc84_lc01 xxGH pc84_lc02 xxGJ pc84_lc03 xxGK pc84_lc04 xxGL

pc85_lc00 yCGM pc85_lc01 xxGM pc85_lc02 xxGN pc85_lc03 xxGP pc85_lc04 xxGR

pc86_lc00 yCGS pc86_lc01 xxGS pc86_lc02 xxGT pc86_lc03 xxGU pc86_lc04 xxGV

pc87_lc00 yCGW pc87_lc01 xxGW pc87_lc02 xxGX pc87_lc03 xxGY pc87_lc04 xxGZ

PX42 pc88_lc00 yCH1 pc88_lc01 xxH1 pc88_lc02 xxH2 pc88_lc03 xxH3 pc88_lc04 xxH4

pc89_lc00 yCH5 pc89_lc01 xxH5 pc89_lc02 xxH6 pc89_lc03 xxH7 pc89_lc04 xxH8

pc8A_lc00 yCH9 pc8A_lc01 xxH9 pc8A_lc02 xxHA pc8A_lc03 xxHB pc8A_lc04 xxHC

pc8B_lc00 yCHD pc8B_lc01 xxHD pc8B_lc02 xxHE pc8B_lc03 xxHF pc8B_lc04 xxHG

PX43 pc8C_lc00 yCHH pc8C_lc01 xxHH pc8C_lc02 xxHJ pc8C_lc03 xxHK pc8C_lc04 xxHL

pc8D_lc00 yCHM pc8D_lc01 xxHM pc8D_lc02 xxHN pc8D_lc03 xxHP pc8D_lc04 xxHR

pc8E_lc00 yCHS pc8E_lc01 xxHS pc8E_lc02 xxHT pc8E_lc03 xxHU pc8E_lc04 xxHV

pc8F_lc00 YCHW pc8F_lc01 xxHW pc8F_lc02 xxHX pc8F_lc03 xxHY pc8F_lc04 xxHZ

PX44 pc90_lc00 yCJ1 pc90_lc01 xxJ1 pc90_lc02 xxJ2 pc90_lc03 xxJ3 pc90_lc04 xxJ4

pc91_lc00 yCJ5 pc91_lc01 xxJ5 pc91_lc02 xxJ6 pc91_lc03 xxJ7 pc91_lc04 xxJ8

pc92_lc00 yCJ9 pc92_lc01 xxJ9 pc92_lc02 xxJA pc92_lc03 xxJB pc92_lc04 xxJC

pc93_lc00 yCJD pc93_lc01 xxJD pc93_lc02 xxJE pc93_lc03 xxJF pc93_lc04 xxJG

PX45 pc94_lc00 yCJH pc94_lc01 xxJH pc94_lc02 xxJJ pc94_lc03 xxJK pc94_lc04 xxJL

pc95_lc00 yCJM pc95_lc01 xxJM pc95_lc02 xxJN pc95_lc03 xxJP pc95_lc04 xxJR

pc96_lc00 yCJS pc96_lc01 xxJS pc96_lc02 xxJT pc96_lc03 xxJU pc96_lc04 xxJV

pc97_lc00 yCJW pc97_lc01 xxJW pc97_lc02 xxJX pc97_lc03 xxJY pc97_lc04 xxJZ

PX46 pc98_lc00 yCK1 pc98_lc01 xxK1 pc98_lc02 xxK2 pc98_lc03 xxK3 pc98_lc04 xxK4

pc99_lc00 yCK5 pc99_lc01 xxK5 pc99_lc02 xxK6 pc99_lc03 xxK7 pc99_lc04 xxK8

pc9A_lc00 yCK9 pc9A_lc01 xxK9 pc9A_lc02 xxKA pc9A_lc03 xxKB pc9A_lc04 xxKC

pc9B_lc00 yCKD pc9B_lc01 xxKD pc9B_lc02 xxKE pc9B_lc03 xxKF pc9B_lc04 xxKG

PX47 pc9C_lc00 yCKH pc9C_lc01 xxKH pc9C_lc02 xxKJ pc9C_lc03 xxKK pc9C_lc04 xxKL

pc9D_lc00 yCKM pc9D_lc01 xxKM pc9D_lc02 xxKN pc9D_lc03 xxKP pc9D_lc04 xxKR

pc9E_lc00 yCKS pc9E_lc01 xxKS pc9E_lc02 xxKT pc9E_lc03 xxKU pc9E_lc04 xxKV

pc9F_lc00 yCKW pc9F_lc01 xxKW pc9F_lc02 xxKX pc9F_lc03 xxKY pc9F_lc04 xxKZ


77 A2 77US B-9



Devices (LC=02)

Devices (LC=03)

Devices (LC=04)

PX50 pcA0_lc00 yCM1 pcA0_lc01 xxM1 pcA0_lc02 xxM2 pcA0_lc03 xxM3 pcA0_lc04 xxM4

pcA1_lc00 yCM5 pcA1_lc01 xxM5 pcA1_lc02 xxM6 pcA1_lc03 xxM7 pcA1_lc04 xxM8

pcA2_lc00 yCM9 pcA2_lc01 xxM9 pcA2_lc02 xxMA pcA2_lc03 xxMB pcA2_lc04 xxMC

pcA3_lc00 yCMD pcA3_lc01 xxMD pcA3_lc02 xxME pcA3_lc03 xxMF pcA3_lc04 xxMG

PX51 pcA4_lc00 yCMH pcA4_lc01 xxMH pcA4_lc02 xxMJ pcA4_lc03 xxMK pcA4_lc04 xxML

pcA5_lc00 yCMM pcA5_lc01 xxMM pcA5_lc02 xxMN pcA5_lc03 xxMP pcA5_lc04 xxMR

pcA6_lc00 yCMS pcA6_lc01 xxMS pcA6_lc02 xxMT pcA6_lc03 xxMU pcA6_lc04 xxMV

pcA7_lc00 yCMW pcA7_lc01 xxMW pcA7_lc02 xxMX pcA7_lc03 xxMY pcA7_lc04 xxMZ

PX52 pcA8_lc00 yCN1 pcA8_lc01 xxN1 pcA8_lc02 xxN2 pcA8_lc03 xxN3 pcA8_lc04 xxN4

pcA9_lc00 yCN5 pcA9_lc01 xxN5 pcA9_lc02 xxN6 pcA9_lc03 xxN7 pcA9_lc04 xxN8

pcAA_lc00 yCN9 pcAA_lc01 xxN9 pcAA_lc02 xxNA pcAA_lc03 xxNB pcAA_lc04 xxNC

pcAB_lc00 yCND pcAB_lc01 xxND pcAB_lc02 xxNE pcAB_lc03 xxNF pcAB_lc04 xxNG

PX53 pcAC_lc00 yCNH pcAC_lc01 xxNH pcAC_lc02 xxNJ pcAC_lc03 xxNK pcAC_lc04 xxNL

pcAD_lc00 yCNM pcAD_lc01 xxNM pcAD_lc02 xxNN pcAD_lc03 xxNP pcAD_lc04 xxNR

pcAE_lc00 yCNS pcAE_lc01 xxNS pcAE_lc02 xxNT pcAE_lc03 xxNU pcAE_lc04 xxNV

pcAF_lc00 YCNW pcAF_lc01 xxNW pcAF_lc02 xxNX pcAF_lc03 xxNY pcAF_lc04 xxNZ

PX54 pcB0_lc00 yCP1 pcB0_lc01 xxP1 pcB0_lc02 xxP2 pcB0_lc03 xxP3 pcB0_lc04 xxP4

pcB1_lc00 yCP5 pcB1_lc01 xxP5 pcB1_lc02 xxP6 pcB1_lc03 xxP7 pcB1_lc04 xxP8

pcB2_lc00 yCP9 pcB2_lc01 xxP9 pcB2_lc02 xxPA pcB2_lc03 xxPB pcB2_lc04 xxPC

pcB3_lc00 yCPD pcB3_lc01 xxPD pcB3_lc02 xxPE pcB3_lc03 xxPF pcB3_lc04 xxPG

PX55 pcB4_lc00 yCPH pcB4_lc01 xxPH pcB4_lc02 xxPJ pcB4_lc03 xxPK pcB4_lc04 xxPL

pcB5_lc00 yCPM pcB5_lc01 xxPM pcB5_lc02 xxPN pcB5_lc03 xxPP pcB5_lc04 xxPR

pcB6_lc00 yCPS pcB6_lc01 xxPS pcB6_lc02 xxPT pcB6_lc03 xxPU pcB6_lc04 xxPV

pcB7_lc00 yCPW pcB7_lc01 xxPW pcB7_lc02 xxPX pcB7_lc03 xxPY pcB7_lc04 xxPZ

PX56 pcB8_lc00 yCR1 pcB8_lc01 xxR1 pcB8_lc02 xxR2 pcB8_lc03 xxR3 pcB8_lc04 xxR4

pcB9_lc00 yCR5 pcB9_lc01 xxR5 pcB9_lc02 xxR6 pcB9_lc03 xxR7 pcB9_lc04 xxR8

pcBA_lc00 yCR9 pcBA_lc01 xxR9 pcBA_lc02 xxRA pcBA_lc03 xxRB pcBA_lc04 xxRC

pcBB_lc00 yCRD pcBB_lc01 xxRD pcBB_lc02 xxRE pcBB_lc03 xxRF pcBB_lc04 xxRG

PX57 pcBC_lc00 yCRH pcBC_lc01 xxRH pcBC_lc02 xxRJ pcBC_lc03 xxRK pcBC_lc04 xxRL

pcBD_lc00 yCRM pcBD_lc01 xxRM pcBD_lc02 xxRN pcBD_lc03 xxRP pcBD_lc04 xxRR

pcBE_lc00 yCRS pcBE_lc01 xxRS pcBE_lc02 xxRT pcBE_lc03 xxRU pcBE_lc04 xxRV

pcBF_lc00 yCRW pcBF_lc01 xxRW pcBF_lc02 xxRX pcBF_lc03 xxRY pcBF_lc04 xxRZ


B-10 77 A2 77US



Devices (LC=02)

Devices (LC=03)

Devices (LC=04)

PX60 pcC0_lc00 yCS1 pcC0_lc01 xxS1 pcC0_lc02 xxS2 pcC0_lc03 xxS3 pcC0_lc04 xxS4

pcC1_lc00 yCS5 pcC1_lc01 xxS5 pcC1_lc02 xxS6 pcC1_lc03 xxS7 pcC1_lc04 xxS8

pcC2_lc00 yCS9 pcC2_lc01 xxS9 pcC2_lc02 xxSA pcC2_lc03 xxSB pcC2_lc04 xxSC

pcC3_lc00 yCSD pcC3_lc01 xxSD pcC3_lc02 xxSE pcC3_lc03 xxSF pcC3_lc04 xxSG

PX61 pcC4_lc00 yCSH pcC4_lc01 xxSH pcC4_lc02 xxSJ pcC4_lc03 xxSK pcC4_lc04 xxSL

pcC5_lc00 yCSM pcC5_lc01 xxSM pcC5_lc02 xxSN pcC5_lc03 xxSP pcC5_lc04 xxSR

pcC6_lc00 yCSS pcC6_lc01 xxSS pcC6_lc02 xxST pcC6_lc03 xxSU pcC6_lc04 xxSV

pcC7_lc00 yCSW pcC7_lc01 xxSW pcC7_lc02 xxSX pcC7_lc03 xxSY pcC7_lc04 xxSZ

PX62 pcC8_lc00 yCT1 pcC8_lc01 xxT1 pcC8_lc02 xxT2 pcC8_lc03 xxT3 pcC8_lc04 xxT4

pcC9_lc00 yCT5 pcC9_lc01 xxT5 pcC9_lc02 xxT6 pcC9_lc03 xxT7 pcC9_lc04 xxT8

pcCA_lc00 yCT9 pcCA_lc01 xxT9 pcCA_lc02 xxTA pcCA_lc03 xxTB pcCA_lc04 xxTC

pcCB_lc00 yCTD pcCB_lc01 xxTD pcCB_lc02 xxTE pcCB_lc03 xxTF pcCB_lc04 xxTG

PX63 pcCC_lc00 yCTH pcCC_lc01 xxTH pcCC_lc02 xxTJ pcCC_lc03 xxTK pcCC_lc04 xxTL

pcCD_lc00 yCTM pcCD_lc01 xxTM pcCD_lc02 xxTN pcCD_lc03 xxTP pcCD_lc04 xxTR

pcCE_lc00 yCTS pcCE_lc01 xxTS pcCE_lc02 xxTT pcCE_lc03 xxTU pcCE_lc04 xxTV

pcCF_lc00 YCTW pcCF_lc01 xxTW pcCF_lc02 xxTX pcCF_lc03 xxTY pcCF_lc04 xxTZ

PX64 pcD0_lc00 yCU1 pcD0_lc01 xxU1 pcD0_lc02 xxU2 pcD0_lc03 xxU3 pcD0_lc04 xxU4

pcD1_lc00 yCU5 pcD1_lc01 xxU5 pcD1_lc02 xxU6 pcD1_lc03 xxU7 pcD1_lc04 xxU8

pcD2_lc00 yCU9 pcD2_lc01 xxU9 pcD2_lc02 xxUA pcD2_lc03 xxUB pcD2_lc04 xxUC

pcD3_lc00 yCUD pcD3_lc01 xxUD pcD3_lc02 xxUE pcD3_lc03 xxUF pcD3_lc04 xxUG

PX65 pcD4_lc00 yCUH pcD4_lc01 xxUH pcD4_lc02 xxUJ pcD4_lc03 xxUK pcD4_lc04 xxUL

pcD5_lc00 yCUM pcD5_lc01 xxUM pcD5_lc02 xxUN pcD5_lc03 xxUP pcD5_lc04 xxUR

pcD6_lc00 yCUS pcD6_lc01 xxUS pcD6_lc02 xxUT pcD6_lc03 xxUU pcD6_lc04 xxUV

pcD7_lc00 yCUW pcD7_lc01 xxUW pcD7_lc02 xxUX pcD7_lc03 xxUY pcD7_lc04 xxUZ

PX66 pcD8_lc00 yCV1 pcD8_lc01 xxV1 pcD8_lc02 xxV2 pcD8_lc03 xxV3 pcD8_lc04 xxV4

pcD9_lc00 yCV5 pcD9_lc01 xxV5 pcD9_lc02 xxV6 pcD9_lc03 xxV7 pcD9_lc04 xxV8

pcDA_lc00 yCV9 pcDA_lc01 xxV9 pcDA_lc02 xxVA pcDA_lc03 xxVB pcDA_lc04 xxVC

pcDB_lc00 yCVD pcDB_lc01 xxVD pcDB_lc02 xxVE pcDB_lc03 xxVF pcDB_lc04 xxVG

PX67 pcDC_lc00 yCVH pcDC_lc01 xxVH pcDC_lc02 xxVJ pcDC_lc03 xxVK pcDC_lc04 xxVL

pcDD_lc00 yCVM pcDD_lc01 xxVM pcDD_lc02 xxVN pcDD_lc03 xxVP pcDD_lc04 xxVR

pcDE_lc00 yCVS pcDE_lc01 xxVS pcDE_lc02 xxVT pcDE_lc03 xxVU pcDE_lc04 xxVV

pcDF_lc00 yCVW pcDF_lc01 xxVW pcDF_lc02 xxVX pcDF_lc03 xxVY pcDF_lc04 xxVZ


77 A2 77US B-11



Devices (LC=02)

Devices (LC=03)

Devices (LC=04)

PX70 pcE0_lc00 yCW1 pcE0_lc01 xxW1 pcE0_lc02 xxW2 pcE0_lc03 xxW3 pcE0_lc04 xxW4

pcE1_lc00 yCW5 pcE1_lc01 xxW5 pcE1_lc02 xxW6 pcE1_lc03 xxW7 pcE1_lc04 xxW8

pcE2_lc00 yCW9 pcE2_lc01 xxW9 pcE2_lc02 xxWA pcE2_lc03 xxWB pcE2_lc04 xxWC

pcE3_lc00 yCWD pcE3_lc01 xxWD pcE3_lc02 xxWE pcE3_lc03 xxWF pcE3_lc04 xxWG

PX71 pcE4_lc00 yCWH pcE4_lc01 xxWH pcE4_lc02 xxWJ pcE4_lc03 xxWK pcE4_lc04 xxWL

pcE5_lc00 yCWM pcE5_lc01 xxWM pcE5_lc02 xxWN pcE5_lc03 xxWP pcE5_lc04 xxWR

pcE6_lc00 yCWS pcE6_lc01 xxWS pcE6_lc02 xxWT pcE6_lc03 xxWU pcE6_lc04 xxWV

pcE7_lc00 yCWW pcE7_lc01 xxWW pcE7_lc02 xxWX pcE7_lc03 xxWY pcE7_lc04 xxWZ

PX72 pcE8_lc00 yCX1 pcE8_lc01 xxX1 pcE8_lc02 xxX2 pcE8_lc03 xxX3 pcE8_lc04 xxX4

pcE9_lc00 yCX5 pcE9_lc01 xxX5 pcE9_lc02 xxX6 pcE9_lc03 xxX7 pcE9_lc04 xxX8

pcEA_lc00 yCX9 pcEA_lc01 xxX9 pcEA_lc02 xxXA pcEA_lc03 xxXB pcEA_lc04 xxXC

pcEB_lc00 yCXD pcEB_lc01 xxXD pcEB_lc02 xxXE pcEB_lc03 xxXF pcEB_lc04 xxXG

PX73 pcEC_lc00 yCXH pcEC_lc01 xxXH pcEC_lc02 xxXJ pcEC_lc03 xxXK pcEC_lc04 xxXL

pcED_lc00 yCXM pcED_lc01 xxXM pcED_lc02 xxXN pcED_lc03 xxXP pcED_lc04 xxXR

pcEE_lc00 yCXS pcEE_lc01 xxXS pcEE_lc02 xxXT pcEE_lc03 xxXU pcEE_lc04 xxXV

pcEF_lc00 YCXW pcEF_lc01 xxXW pcEF_lc02 xxXX pcEF_lc03 xxXY pcEF_lc04 xxXZ

PX74 pcF0_lc00 yCY1 pcF0_lc01 xxY1 pcF0_lc02 xxY2 pcF0_lc03 xxY3 pcF0_lc04 xxY4

pcF1_lc00 yCY5 pcF1_lc01 xxY5 pcF1_lc02 xxY6 pcF1_lc03 xxY7 pcF1_lc04 xxY8

pcF2_lc00 yCY9 pcF2_lc01 xxY9 pcF2_lc02 xxYA pcF2_lc03 xxYB pcF2_lc04 xxYC

pcF3_lc00 yCYD pcF3_lc01 xxYD pcF3_lc02 xxYE pcF3_lc03 xxYF pcF3_lc04 xxYG

PX75 pcF4_lc00 yCYH pcF4_lc01 xxYH pcF4_lc02 xxYJ pcF4_lc03 xxYK pcF4_lc04 xxYL

pcF5_lc00 yCYM pcF5_lc01 xxYM pcF5_lc02 xxYN pcF5_lc03 xxYP pcF5_lc04 xxYR

pcF6_lc00 yCYS pcF6_lc01 xxYS pcF6_lc02 xxYT pcF6_lc03 xxYU pcF6_lc04 xxYV

pcF7_lc00 yCYW pcF7_lc01 xxYW pcF7_lc02 xxYX pcF7_lc03 xxYY pcF7_lc04 xxYZ

PX76 pcF8_lc00 yCZ1 pcF8_lc01 xxZ1 pcF8_lc02 xxZ2 pcF8_lc03 xxZ3 pcF8_lc04 xxZ4

pcF9_lc00 yCZ5 pcF9_lc01 xxZ5 pcF9_lc02 xxZ6 pcF9_lc03 xxZ7 pcF9_lc04 xxZ8

pcFA_lc00 yCZ9 pcFA_lc01 xxZ9 pcFA_lc02 xxZA pcFA_lc03 xxZB pcFA_lc04 xxZC

pcFB_lc00 yCZD pcFB_lc01 xxZD pcFB_lc02 xxZE pcFB_lc03 xxZF pcFB_lc04 xxZG

PX77 pcFC_lc00 yCZH pcFC_lc01 xxZH pcFC_lc02 xxZJ pcFC_lc03 xxZK pcFC_lc04 xxZL

pcFD_lc00 yCZM pcFD_lc01 xxZM pcFD_lc02 xxZN pcFD_lc03 xxZP pcFD_lc04 xxZR


B-12 77 A2 77US

77 A2 77US C-1

C. Deploy Center V5.0 Installation

This installation must only be carried out if the Deploy Center diskettes supplied need to be regenerated, and the Deploy Center tool has not been installed.

If the tool has been installed, use the Create Rescue Diskettes command from the Power Quest Deploy Center 5.0 Start menu. This initiates the transfer to the creation of the diskettes in the procedure described below.

In the Control Panel's Add/Remove Programs window, search for the file: <CD-ROM drive>:\IMGCTRSRV\SETUP\SETUP.EXE, then execute it.

The installation first requests which visibility is to be given to the tool (limited to the administrator or not), then requests information on the user, the license number on the CD-ROM, the acceptance of the license terms, and the type of installation (choose Typical).

After a summary window, it continues by recommending the creation of rescue diskettes (Figure C-1).

Figure C-1. Request to Create Diskettes


C-2 77 A2 77US

• Click on Next.

The two diskettes are created by a dedicated Setup activated by the Deploy Center's main Setup.

The first diskette created is a boot diskette (Figure A-2), the second one a tool diskette.

Figure C-2. Boot Diskette Creation

• Click on Next (Do not select anything)

Follow the indications and insert the diskettes when requested.

Once the installation is complete, proceed without choosing to read the Readme and without registering the software with Power Quest.

Click on Finish to exit and close any windows still open.

77 A2 77US D-1

D. Reversing the Disks

Open the machine cabinet, then open the internal disk compartment (Figure D-1) by unscrewing the top two screws.

Figure D-1. Opening the Disk Cover

Then unclip Disk0 and Disk1 (Figure D-2).

Figure D-2. Identifying Disk1 and Disk0

The disks are identified from right to left. To remove a disk, raise the clip (shown by the arrow) and pull the disk from its guide.

To replace a disk after the reversal, insert the disk in the guide, push in completely then lower the clip.


D-2 77 A2 77US

77 A2 77US E-1

E. Disaster Recovery

E.1 Classical DPS7000/XTA

Subsequent to an incident, the machine's quick recovery depends on the problems encountered, on the backup elements available and their quality, or on the balance between these elements.

For example, an up-to-date clone will enable a fast restart in optimal conditions, whereas the restoration of NT Backups on a machine on which a minimum Windows version must first be reinstalled will be costly in terms of time.

Consequently, it is important to know which recovery mode is most suited to the incident encountered and to the backups available.

E.1.1 Incidents Concerning Software or Limited to Disk0

The incidents can concern the operating system (Windows™), V7000 and its configuration data.

Malfunctions are indicated by:

• Messages or explicit warnings by Windows™ (blue screen, system log) or applications other than V7000

• Messages or explicit warnings by V7000 or located in the V7000 system log

• The impossibility of starting V7000, loss of the active hardware configuration key, etc.

• Etc.

Distinguishing V7000 incidents means time can be gained if the diagnostic is correct, and can avoid having to stop and restart the machine. If the reinstallation or reactivation of the version does nothing to help, an environment restoration method must be used.


E-2 77 A2 77US

NOTE: Remember that restoring the system's status by NT Backup will require the machine to be stopped. Consequently, if the machine's shutdown is foreseeable, opt for using the clone, even if old, and re-apply the last valid NT Backup.

The following three situations specify the actions to take to re-establish a machine subsequent to an incident.

1- V7000 won't start

• Reactivate the current version using the Version Manager.

• If this doesn't work:

− Display the activation log (the V7000 Installation and Activation.log file in the V7000 Trace directory) and the V7000 system log to detect the possible error and correct it.

− If necessary, reinstall the V7000 version, then

− Reactivate the version using Version Manager.


− Restore the last complete NT Backup.


− Restart the last valid clone.


− Contact Bull for an intervention.

• Otherwise:

− Manually re-apply the modifications known.

2- Windows won't start

• Restart on the clone.



• Otherwise

• Clone a third disk if possible (security).

• Start on the second clone then apply the last NT Backup available.

Disaster Recovery

77 A2 77US E-3


• Start on the first clone and manually re-apply the modifications (do not re-apply the last NT Backup since this has already been attempted before starting on the second clone).



3 - Disk0 won't start

• Start on the clone.



• Otherwise

• Clone a third disk (security).

• Start on the second clone then re-apply the last available NT Backup.


− Start on the first clone and manually re-apply the modifications.



Depending on the elements available, the software reconstruction time for a system can be estimated as follows (Table 1):

Table E-1. Estimated Reconstruction Time / Elements

Components available Estimated time Intervening parties

Clone 10 minutes Administrator/Bull

NT Backup 30 minutes Administrator

Clone + NT Backup 40 minutes Administrator/Bull

Windows 2000 + NT Backup 2 hours Administrator/Bull

No Windows2000 No valid backups

One day minimum Bull

The last case corresponds to the worst possible situation and should never occur.

The times are given by way of indication only, and imply the most favorable conditions.


E-4 77 A2 77US

The intervening parties specified are theoretical; the intervention depends on the contractual relationships established between Bull and the Customer.

IMPORTANT: Once the machine has been restored, the disk must be cloned, and an additional complete NT Backup must be done.

E.1.2 Other Hardware Incidents

After Bull's intervention, once the machine has been restored, Disk0 - rebuilt or re-established - must be cloned then activated.

E.2 1X4 DPS7000/XTA Models

This procedure explains how to repair Raid1 configuration under BIOS with LSI Logic utility. It must be used carefully in the last resort.

• Shutdown of the Platform then power on

• When the BIOS loads and you see the message about the LSI Logic Configuration Utility, press CTRL C to start the utility. Wait for message �Please wait, invoking LSI Logic Configuration Utility��

• On the Main menu screen of the utility, use the arrow keys to select an adapter (two by physical adapter) then press <ENTER>

• Verify that physical disks are managed by selected adapter (press <Devices Properties> then <ESCAPE> to return). Change selected adapter if necessary (because LSI Logic adapter is a dual port adapter but only one is used to manage Raid1 configuration)

• On the Adapter Properties screen, use the arrow keys to select RAID Properties then press <ENTER>

• In the RAID Properties screen, use the arrow keys to select the primary disk for the Raid1 configuration (the disk with the data to want to mirror)

• Use the arrow keys to move to the Array Disk column for this disk, and use the + or � keys to select Yes as the value

13

3

Disaster Recovery

77 A2 77US E-5

• When the �Keep Data/Erase Disk” message appears, press F3 to keep the data that is currently on this disk. The value in the Array Disk column changes to Primary.

• Use the arrow key to select the secondary (mirrored) disk, and select Yes as the value for the Array Disk column. A message warns you that data on the disk will be lost when the mirrored volume is created. Press <DELETE> to confirm erasing data.

• When the two disks are selected, press <ESCAPE> and select �Save changes, then exit this menu”

• In Main utility screen, verify that status value is resyncing on the valid adapter and press <ESCAPE>

• Select <Exit setup utilities> that causes the restart of the Platform.

• Launch ServerRaid Manager tool from Start Menu/ServerRaid Manager to control the resynchronisation progress.

When the Raid1 configuration becomes available, use the procedure �Back to a steady system� (see § 9.9.2) to restore V7000 and System states.

Apply also last NT Backup updates if exist.

E.3 X5 DPS7000 XTA Models

This procedure explains how to repair Raid1 configuration under BIOS with LSI Logic utility.

It must be used carefully in the last resort.

• Shutdown of the Platform then power on.

• At the initialization of the card MegaRAID 320-2 press ENTER to activate the configuration tool (Figure E-1).


E-6 77 A2 77US

Figure E-1: BIOS Initialization tool for LSI MegaRAID

• Opening of Configure Menu (Figure E-2)

Figure E-2: Configuration tool for LSI MegaRAID Main window

• Verify that physical disks are managed by selected adapter

Press <Devices Properties> then <ESCAPE> to return. Change selected adapter if necessary (because LSI Logic adapter is a dual port adapter but only one is used to manage Raid1 configuration)

• On the Adapter Properties screen, use the arrow keys to select RAID Properties then press <ENTER>

Disaster Recovery

77 A2 77US E-7

• In the RAID Properties screen press <ESCAPE> then use the arrow keys to select the primary disk for the Raid1 configuration (the disk with the data to want to mirror)

• Use the arrow keys to move to the Array Disk column for this disk, and use the + or � keys to select Yes as the value

• When the �Keep Data/Erase Disk” message appears, press F3 to keep the data that is currently on this disk. The value in the Array Disk column changes to Primary.

• Use the arrow key to select the secondary (mirrored) disk, and select Yes as the value for the Array Disk column. A message warns you that data on the disk will be lost when the mirrored volume is created. Press <DELETE> to confirm erasing data.

• When the two disks are selected, press <ESCAPE> and select �Save changes, then exit this menu”

• In Main utility screen, verify that status value is resyncing on the valid adapter and press <ESCAPE>

• Select <Exit setup utilities> that causes the restart of the Platform.

Launch ServerRaid Manager tool from Start Menu/ServerRaid Manager to control the resynchronisation progress (see §9.10.5)

E.4 Novascale Models

See Chaparral sub-system management described in �86A145EG00: BULL SR-0812 RAIDStorage System User�s Guide� documentation, and Fame related documentations.


E-8 77 A2 77US

E.5 Partitions Shifts

When the reference (and also clone) partition structure is no more C:\,E:\, F:\ (or CEF), V7000 can not start.

CEF partition structure must be restored on reference disk. To do that, follow the procedure below.

• Open My Computer then right click Manage

• Disk Manager then select Disk0.

• Select volume V7000 then right click change drive letter and path

• Add E: letter (if no valid, choose a temporary letter then after give E:)

• Select volume DATA then right click change drive letter and path

• Add F: letter (if no valid, choose a temporary letter then after give F:)

• Reboot then verify partition structure

• Clone if correct then restart the current procedure

77 A2 77US F-1

F. Recommendations for Creating W2K Shared Disks

Definition of a�W2K shared disk�

LUN (Logical Unit Number) of a disks sub-system visible and accessible from two W2K servers at the same time.

This appendix gives some recommendations for the creation of W2K shared disks, on which the NTFS files corresponding to GCOS7 disks in Shared mode will be created.

F.1 Requirements

• Both the DPS7000/XTA servers must be installed with W2K SP3.

• It is assumed that the LUN (Logical Unit Number) has already been created using the suitable sub-system administration tool, but is not yet visible nor accessible from the DPS7000/XTA servers.

• It is necessary to work on one DPS7000/XTA server only, while the other is stopped.


F-2 77 A2 77US

F.2 Creating Partitions on W2K Disks on the First Server

1. Boot the first DPS7000/XTA server.

− Automatic recognition of the W2K shared disks 2. Use the W2K Disk Management tool to configure the new disks.

− Disks are seen as �Disk i�. − Disk states are �Unknown�. − Disk space is �Unallocated�.

3. Write Signature for each disk

− The disk state is updated to �Basic�. − Do not upgrade the disk to �Dynamic�.

4. Create one partition on each disk:

− Primary partition. − Take all the available space. − Accept the proposed drive letter. − Perform a quick format. − Label the partition.

5. Reboot the server.

− Creation of a virtual directory named �System Volume Information�. − Each partition is seen as a drive and accessed through a drive letter. − Check that each drive contains the directory �System Volume

Information�.

Recommendations for Creating W2K Shared Disks

77 A2 77US F-3

6. Launch the Disk Management tool to replace the drive letter by a mounted point.

− Ccommand Change Drive Letter and Path ! Remove Letter. − Command Change Drive Letter and Path ! Add ! Mount in this

NTFS folder. − The given folder must already exist. − The path to this folder must contain a folder named Gcos_Disks.

7. Reboot the server.

Figure F-1. Example of W2K Disks Access Paths after Server Reboot (NB: Gcos_Disks Must Be Read Instead of GCOS_DISK)

IMPORTANT: Only NTFS files corresponding to GCOS7 disks must be allocated on W2K shared disks.

13

3


F-4 77 A2 77US

F.3 Creating GCOS7 Disks on W2K Shared Disks

Use the GCOS7 Disk Manager tool to define the Shared mode for the GCOS 7 disk (for more information, see Chapter 3):

DEFINE SHARING ! Shared mode

Defining the Shared mode of a GCOS7 disk is the only way to inform the V7000 software that this GCOS7 disk is allocated on a W2K shared disk.

There is no specific recommendation concerning the number of GCOS7 disks created on each W2K shared disk. However, space and performance aspects must be taken into account.

Figure F-2. Example of One 2GB GCOS7 Disk Named MSGM Created on a W2K Disk (NB: Gcos_Disks Must Be Read Instead of GCOS_DISK).

Recommendations for Creating W2K Shared Disks

77 A2 77US F-5

F.4 Recognizing the W2K Shared Disks on the Second Server

1. Boot the second DPS7000/XTA server.

− The W2K shared disks are recognized automatically. − A drive letter is assigned to each new drive.

2. Launch the Disk Management tool to replace the drive letter by a mounted

point.

− Command Change Drive Letter and Path ! Remove Letter. − Command Change Drive Letter and Path ! Add ! Mount in this

NTFS folder. − The given folder must already exist and must be the same as on the first

DPS7000/XTA server.

F.5 GCOS7 Disks With Shared Mode and the V7000 Configurations

The GCOS7 disks with Shared mode must be configured with the Sharable property in the V7000 configurations of the two DPS7000/XTA servers � for more information, see Chapter 2.

Check and Activate the V7000 configurations on both the servers before initializing their respective V7000 virtual machines.


F-6 77 A2 77US

77 A2 77US G-1

G. RCF7 Configuration

This appendix provides some information related to �Remote Control Facility� (RCF7) server management.

Purpose

This V7000 item is an optional server that enables communication, using Pilot/OpenMaster, between a distant client (Pilot) and V7000 system (SYC or LN0x).

Operation

RCF7 is introduced with V7000 version V2.5.

When RCF7 is configured, it starts automatically with V7000 System Control. The following message appears in the RCF7 specific window:

COMP_RCF component successfully initialized The following message appears in the Event Log (Event Source: V7000_RCF):

RCF7 is ready to connect a new session Otherwise these messages, in SYC window and Event Log, are:

No port number on V7000 _RCF7Si in \ETC\SERVICES ! RCF7 is abandoned.

Configuration

When V7000 version V2.5 is setting up, but before activating from Version Manager, you must include the port number for using RCF7 in the system file WINNT\system32\drivers\etc\services.

The same port number must be set on the client side and the server side.

The default port number, for a Bull environment, is 7011.


2 77 A2 77US

An operator who wants to use RCF7 must belong to the �V7000Operators� group on the host machine.

Reference

To obtain the installation and configuration guide for Pilot/OpenMaster, contact:

E-mail: [email protected]

Telephone: +33 (0)5 56 43 78 45

Fax: +33 (0)5 56 43 79 78

77 A2 77US g-1

Glossary

D

DPS 7000/XTA New generation of eXtended Twin Architecture DPS 7000 machines running on an Intel® Architecture (IA) hardware platform under the Microsoft® Windows� Operating System and the BULL V7000 Virtual Machine.

G

GCOS7 BULL propriety Operating System running on DPS 7000 platforms.

I

Intel® Architecture (IA) Intel® Processor Architecture represented by Xeon� processors.

K

Key The device used to control DPS 7000/XTA distribution and to guarantee BULL against the illegal use of V7000 Virtual Machine software.

L

Logical Volume Windows� concept designating a quantum of disk space, also called Partition. A physical disk can contain several logical volumes or partitions. These logical volumes are materialized by a letter followed by �:� or by a �Disk Folder� or special directory represented by a gray rectangle in the Windows� Explorer.


g-2 77 A2 77US

O

OS or Operating System Windows� and GCOS7 are Operating Systems.

S

SRST: System Resource and Status Table This table, in which all GCOS7 resources are described, is transmitted to GCOS7 by the V7000 Init command. It results from the V7000 configuration.

T

Terminal Services Windows� product used to operate a server from a remote station. Remote operability is the same as local operability � the display is repeated on the remote station.

V

V7000 Platform DPS 7000/XTA hardware platform.

V7000 Virtual Machine (VM) or V7000 BULL software installed on a V7000 platform to run the BULL GCOS7 system and applications.

W

WINDOWSTM Generic term designating the Microsoft® Operating System used for the V7000 platform.

77 A2 77US i-1

Index

A access rights 3-7 Activate 1-13, 2-22 Activity 3-6, 3-14 administration tools 1-1 API 8-7

B Brother Controller 2-46 BULL Support 2-1

C CANCEL 3-6 cartridge 2-5 cartridge drive 2-6, 2-34 cartridge driver 1-14, 2-53 check 1-4 Check 1-13 Check Box 2-4 command prompt 3-12 Configuration 2-24 Configuration Editor 1-2, 2-1 Context Menu 2-7, 2-13 control area 3-9, 3-10, 3-11, 3-33 control boxes 2-4 Copy To Clipboard 2-22 CREATE 3-6, 3-16 creating a new configuration 2-1 creating GCOS7 disks 1-12 creation threads 3-39 CT 2-8

Current Action 3-6, 3-12 Current Path 3-6, 3-12

D decompress 1-11 DELETE 3-6, 3-30 device 1-14 Dialogue Box 2-4 directory 3-17 disk 2-34, 2-60 disk controller 2-34, 2-44 disk files 3-29, 3-33 disk size 3-16 disks 2-5 DPS 7000/XTA 1-1 Drop-down List 2-4

E Edit Box 2-4 EOF 3-9 Error 8-7 error messages 2, 4 External Ident 2-8 External Key 2-17 External Name 2-8 External Type 2-8

F feasibility check 3-18 file name 2-14 file transfer 7-1 file tree 3-2


i-2 77 A2 77US

finish 1-12 first version of V7000 2-5 folders 2-6 Function Title 8-7

G GCOS_Disks 3-2 GCOS7 2-6, 2-63 GCOS7 disk image 1-11 GCOS7 Disk Manager 1-2, 3-1 GCOS7 disks 3-1 GCOS7 name 2-8 Global Information 2-23 group nodes 2-6 GTS station 7-1

H hardware key 2-5 hierarchized objects 2-7 HISTORY 3-6, 3-37 history blocks 3-38 history buffer 3-9, 3-10, 3-11, 3-13, 3-38, 3-

39 history file 3-13, 3-37, 3-38, 3-39 Home Page 2-12

I I/O tree 2-17 IA 1-1 Information Collector 1-2 Init Key 1-16 Init Key 1-16 installation 1-1 installation context 2 Installed Key 2-17 installing the key 1-11 IOP 2-5, 2-35 IOxx 2-34, 2-38 IPU 2-5 IPxx 2-26, 2-29

K K1 3-2 key

different 2-18 not compatible 2-18

Key 2-24 key evolutions 2 key file 1 Key Installer 1-2, 6-1, 11-1 key type 2

L LL

logical drive 3-9 location 1-12 logical resources 2-1

M MAC address 1-15 MAKE UP 3-6, 3-33 memory 2-5 MMC 2-1 MMU 2-30 modifying an existing configuration 2-1 MS 2-8 MSxx 3-9 MU 2-8 MUxx 2-33

N New 2-14 nodes 2-4 non-authorized user 3-5 non-V7000 files 3-2

O Open 2-17 operation 1-1, 2-2 Owner 3-4

Erreur ! Style non défini.

77 A2 77US i-3

P partner system 2-5 path 2-14, 3-17 physical disk 3-2 physical resources 2-1 PID 3-38 Platform Identifier 1-2 Previous Action 3-6, 3-13 printer 1-15, 2-5, 2-34, 2-63 printer controller 2-34, 2-54 processor 2-6 Project 1-5 Properties 2-4 Property Sheet 2-4 PXmn 2-34, 2-42 PXU 2-5

Q Quit 8-3 QUIT 3-6

R remote station 1-4, 2-5 rename 1-11, 3-29, 3-33 RENAME 3-6, 3-23 repair 1-14 report 2-4 Result Pane 2-4 rights 1-5 root directory 3-2 root node 2-6

S Save 1-13, 2-19 Scope Pane 2-4 security group 1-5 Select or View Trace Domains 8-3 Select Trace Level 8-3 Selections 3-6, 3-12 serial number 1-17 Service System Control 8-9

signature 2-5 signature file 1-10 size 1-12 Snap-in 2-4 Stack 8-7 Start Trace 8-3 Stop Trace 8-3 Support tool 2-2 SYC 8-9

T tape cartridge 2-62 tape cartridge controller 2-34, 2-47 target disk 3-18 telecom 2-5, 2-65 telecom controller 2-34, 2-58 telecom line 2-34 telecommunications card 1-14 telecommunications line 2-6 text file 2 threads 2-6 Trace 3-13 trace active 8-2 Trace Dump 8-7 Trace Manager 1-2 Trace State 8-3 Trace Text 8-7 transfer alarms 7-1 type of key 2-5

U unique key 1-16 Update Key 1-16 Upgrade Key 1-16

V V7000 1-1, 3-1 V7000 configuration 2-14 V7000 CPUs 2-26 V7000 key 1 V7000 machine identification 2-5 V7000 platform 1-1, 2


i-4 77 A2 77US

V7000 resources 2-2 V7000 startup 2-2 V7000 Trace Manager 8-1 V7000 Virtual Machine 1-1, 2-2 V7000 VM 1-1, 3-1 V7000BullServices group 3-5, 1 valid key 3-5 Version Manager 1-2 virtual component 2-6

W Warning 8-7 Windows™ partitions 3-2

Technical publication remarks form

Title : DPS7000/XTA NOVASCALE 7000 V7000 Configuration and Maintenance GuideUser's Guide

Reference Nº : 77 A2 77US 04 Date: March 2006

ERRORS IN PUBLICATION

SUGGESTIONS FOR IMPROVEMENT TO PUBLICATION

Your comments will be promptly investigated by qualified technical personnel and action will be taken as required.If you require a written reply, please include your complete mailing address below.

NAME : Date :

COMPANY :

ADDRESS :

Please give this technical publication remarks form to your BULL representative or mail to:

Bull - Documentation Dept.

1 Rue de ProvenceBP 20838432 ECHIROLLES [email protected]

Technical publications ordering form

To order additional publications, please fill in a copy of this form and send it via mail to:

BULL CEDOC357 AVENUE PATTONB.P.2084549008 ANGERS CEDEX 01FRANCE

Phone: +33 (0) 2 41 73 72 66FAX: +33 (0) 2 41 73 70 66E-Mail: [email protected]

CEDOC Reference # Designation Qty

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

[ _ _ ] : The latest revision will be provided if no revision number is given.

NAME: Date:

COMPANY:

ADDRESS:

PHONE: FAX:

E-MAIL:

For Bull Subsidiaries:

Identification:

For Bull Affiliated Customers:

Customer Code:

For Bull Internal Customers:

Budgetary Section:

For Others: Please ask your Bull representative.

BULL CEDOC

357 AVENUE PATTON

B.P.20845

49008 ANGERS CEDEX 01

FRANCE

77 A2 77US 04REFERENCE