V7000 Operators' Guide DPS7000/XTA NOVASCALE 7000 Hardware: DPS7000/XTA REFERENCE 77 A2 74US 10
DPS7000/XTA NOVASCALE 7000 V7000 Operators' Guide Hardware: DPS7000/XTA Software September 2009 BULL CEDOC 357 AVENUE PATTON B.P.20845 49008 ANGERS CEDEX 01 FRANCE REFERENCE 77 A2 74US 10
The following copyright notice protects this book under Copyright laws which prohibit such actions as, but not limited to, copying, distributing, modifying, and making derivative works. Copyright Bull SAS 1995-2009 Printed in France Suggestions and criticisms concerning the form, content, and presentation of this book 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, you are 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 through the 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 contained herein, or for incidental or consequential damages in connection with the use of this material.
Preface Scope and Objectives This manual describes how to operate V7000 Virtual Machine (DPS 7000 / XTA). This operator s Guide contains all the information you need to initialize and control the V7000 VM (Virtual Machine). It also gives references to others manuals related to this virtual machine. Additional information may be obtained through the help features that are available on each V7000 user interface proposed to control the virtual machine. Intended Readers People who operate a DPS7000/XTA Prerequisites Structure Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Appendix A Appendix B Gives a general presentation of a V7000 Virtual Machine as an application on a Bull IA (Intel Architecture) platform running under Microsoft Windows control. Presents the System Administration Manager functions. Describes the V7000 user interfaces. Describes incidents. Backing up a DPS 7000/XTA Platform s System Environment. Contains checklists for typical situations. Deploy Center V5.0 Installation. Reversing the Disks. 77 A2 74US iii
V7000 Operator's Guide Glossary. Index. Bibliography V7000 Operator s Guide (this document)...47 A2 74US GCOS7-V10 System Installation Configuration... 47 A2 23US and Updating Guide... Describes how to install and configure a GCOS7 release. GCOS7-V10 System Operator s Guide... 47 A2 47US Describes the GCOS7 system operation from both the platform administration and the GCOS7 point of views. INTEROP7 User s GUIDE...47 A2 91US Syntax Notation Delivery Conditions iv 77 A2 74US
Table of Contents 1. Introduction 1.1 V7000 Virtual Machine Description... 1-1 1.2 Hardware Platform... 1-3 1.3 SAM Tools and User Interfaces...1-3 1.4 Users Categories... 1-6 1.4.1 Relation between user roles and group membership...1-7 1.4.2 Relation between user membership and actions to be done... 1-8 1.5 Virtual Machine visibility...1-12 1.5.1 Some recalls on Windows screen... 1-12 1.5.2 V7000 Virtual machine coating in the status area...1-13 2. SAM Functions 2.1 V7000 System Control User Interface... 2-3 2.2 V7000 Operation Supervisor User Interface... 2-5 2.3 GCOS7 Console: LN User Interface... 2-7 3. User Interfaces Description 3.1 Use V7000 System Control... 3-1 3.1.1 Overview... 3-1 3.1.2 V7000 System Control Users... 3-8 3.1.3 How to Initialize System (IN)... 3-9 3.1.4 How to Reload System (RL)... 3-12 3.1.5 How to Restart System (SR)... 3-14 3.1.6 How to Terminate System (TS)... 3-15 3.1.7 How to Become Master... 3-18 3.1.8 How to Refresh the Status Bar... 3-21 3.1.9 How to Update SOP Information... 3-22 77 A2 74US v
V7000 Operator's Guide 3.1.10 How to Activate Online Help... 3-25 3.1.11 How to Build Exclusion List... 3-27 3.1.12 How to Refresh Resources List... 3-31 3.1.13 How to Copy Resources List... 3-32 3.1.14 How to View V7000 Virtual Machine Activity... 3-34 3.1.15 How to Refresh Messages List... 3-35 3.1.16 How to Copy Messages List... 3-36 3.1.17 How to Connect to Another Computer... 3-38 3.2 Use the V7000 Operation Supervisor... 3-40 3.2.1 Overview... 3-40 3.2.2 How to View the User Interfaces Currently Active... 3-41 3.2.3 How to Refresh information for all the User Interfaces... 3-42 3.2.4 How to Copy User Interface List... 3-43 3.2.5 How to Activate Online Help... 3-44 3.2.6 How to Start a LN... 3-45 3.2.7 How to Refresh Information for a Given User Interface... 3-47 3.2.8 How to View Details Information for a Given User Interface... 3-48 3.2.9 How to Connect to Another Computer... 3-50 3.3 Use a GCOS7 Console: LN User Interface... 3-52 3.3.1 How to Send a Break... 3-54 3.3.2 How to Enter a Text or Answer a System Question... 3-54 3.3.3 Description of the Commands Available for a LN User Interface... 3-55 3.3.3.1 File Group Menu... 3-56 3.3.3.2 Edit Group Menu... 3-58 3.3.3.3 View Group Menu... 3-60 3.3.3.4 System Group Menu... 3-63 3.3.3.5 Help Group Menu... 3-64 3.4 Use Computer Management... 3-66 3.4.1 Overview... 3-66 3.4.2 How to Connect to Another Computer... 3-68 4. Incidents 4.1 User Visible Incidents... 4-1 4.1.1 Introduction... 4-1 4.1.1.1 Messages Box... 4-1 4.1.1.2 Activity Messages... 4-2 4.1.2 Error Message Box in User Interfaces... 4-2 4.1.3 Fatal Errors During V7000 Virtual Machine Activity... 4-6 4.1.3.1 V7000 Virtual Machine Initialization... 4-6 4.1.3.2 V7000 Virtual Machine Reload... 4-13 4.1.3.3 V7000 Virtual Machine Restart... 4-18 vi 77 A2 74US
Contents 5. Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment 5.1 Introduction... 5-1 5.2 Internal Disks on a DPS7000 / XTA Machine... 5-3 5.3 Archiving Tools... 5-4 5.3.1 Deploy Center 5.0 (Power Quest)... 5-4 5.3.2 NT Backup (Windows)... 5-4 5.4 Changes on a DPS7000/XTA Machine... 5-6 5.5 Choice of Archiving Tool... 5-7 5.5.1 Machine Upgrades... 5-7 5.5.2 Machine Availability... 5-7 5.5.3 Backup Quality Implementation... 5-8 5.5.4 Recommendations... 5-8 5.5.5 Intervening Parties... 5-9 5.5.5.1 Backup... 5-9 5.5.5.2 Restoration... 5-9 5.5.5.3 Disaster Recovery... 5-10 5.6 NT Backup... 5-11 5.6.1 Backup... 5-12 5.6.2 Restoration... 5-18 5.6.3 Troubleshooting... 5-24 5.6.4 Rebuild a New System Disk... 5-24 5.7 Cloning... 5-26 5.8 Errors encountered during cloning operations... 5-42 5.9 Checks in Windows after Restarting on the Clone... 5-43 5.10 Cloning procedure with two different internal disks... 5-44 5.11 Hardware mirroring for DPS7000/XTA 1X4 and later Models... 5-46 5.11.1 Save of system disk... 5-47 5.11.2 Back to a steady system... 5-47 5.11.3 Disk Substitution in case of disk Hardware Failure Windows running... 5-48 5.11.4 Disk Substitution in case of disk Hardware Failure Windows stopped... 5-48 5.11.5 ServerRaid manager Graphical User Interface Tool (GUI)... 5-48 5.12 Hardware mirroring for DPS7000/XTA X5... 5-51 5.12.1 Save of system disk... 5-52 5.12.2 Back to a steady system... 5-53 5.12.3 Disk Substitution in case of disk Hardware Failure and Windows running... 5-53 5.12.4 Disk substitution in case of disk Hardware Failure and Windows stopped... 5-54 5.12.5 MegaRAID Client Tool Graphical User Interface Tool... 5-54 77 A2 74US vii
V7000 Operator's Guide 5.13 Hardware mirroring for Novascale 7000... 5-59 6. How to and Check Lists 6.1 How to Add a User in the V7000Operators Group... 6-1 6.2 How to Start/stop the V7000 Services... 6-7 6.2.1 How to Stop the V7000 Services... 6-7 6.2.2 How to Start the V7000 Services... 6-8 6.2.3 How to Check the V7000 Services Status... 6-9 6.3 How to Install a New V7000 Version... 6-11 6.4 How to Install a New GCOS7 Technical Status... 6-11 6.5 How to Exit from a V7000 SYSTEM CHECK... 6-11 6.6 How to Exit from a GCOS7 CRASH... 6-12 6.7 How to Exit from a GCOS7 DEADLOCK... 6-12 6.8 How to Build or Modify a V7000 Configuration... 6-12 6.9 How to Make Deliberate General Power Off of the Whole Platform... 6-13 6.10 In Case of General Power Failure for the Whole Platform... 6-13 6.11 How to Exit from a General V7000 System Deadlock... 6-13 6.12 How to Exit from a General Platform Deadlock... 6-14 A. Deploy Center V5.0 Installation B. Reversing the Disks Glossary Index viii 77 A2 74US
Contents Table of Graphics Figures Figure 1-1 General schema of a V7000 Virtual Machine... 1-1 Figure 1-2 Platform resource mapping for V7000 VM... 1-2 Figure 1-3 SAM User Interfaces and Services... 1-4 Figure 1-4 Start menu related to V7000 user interfaces... 1-5 Figure 1-5 Taskbar description... 1-12 Figure 1-6 V7000 icons Software Version... 1-14 Figure 1-7 Icon Properties message box... 1-14 Figure 2-1 V7000 System Control on the V7000 Virtual Machine... 2-3 Figure 2-2. V7000 Operation Supervisor on the V7000 Virtual Machine... 2-4 Figure 2-3. GCOS7 LN02 Console... 2-5 Figure 3-1. Actions on V7000 System... 3-1 Figure 3-2. CSS Resources on the V7000 Platform... 3-3 Figure 3-3. Actions on CSS Resources... 3-5 Figure 3-4. Activity History on V7000 Virtual Machine... 3-6 Figure 3-5. Actions on Activity History... 3-7 Figure 3-6. Actions on V7000: Init(IN)... 3-9 Figure 3-7. Initialization Dialog... 3-10 Figure 3-8. Dialog for Automatic Start of LN02 GCOS7 Console... 3-10 Figure 3-9. Initialize V7000 System Result... 3-11 Figure 3-10. LN02 Console after Initialize V7000 System... 3-11 Figure 3-11. Actions on V7000: Reload(RL)... 3-12 Figure 3-12. Reload Dialog Box... 3-13 Figure 3-13. Actions on V7000: Restart(SR)... 3-14 Figure 3-14. Restart Dialog Box... 3-14 Figure 3-15. Confirm Restart Dialog Box... 3-15 Figure 3-16. Actions on V7000: Terminate (TS)... 3-15 Figure 3-17. Terminate Dialog Box... 3-16 Figure 3-18. Confirm Terminate Dialog Box... 3-16 Figure 3-19. Terminate V7000 System Result... 3-17 Figure 3-20. Actions on V7000: Take Control... 3-18 Figure 3-21. Take Control Dialog Box... 3-18 Figure 3-22. Confirm Take Control Dialog Box... 3-19 Figure 3-23. Take Control Information Dialog Box... 3-19 Figure 3-24. Master Dialog Box for Agreement... 3-20 Figure 3-25. Actions on V7000: Refresh... 3-21 Figure 3-26. Refresh Warning Message... 3-21 77 A2 74US ix
V7000 Operator's Guide Figure 3-27. Actions on V7000: Properties... 3-22 Figure 3-28. V7000 Properties Page... 3-23 Figure 3-29. Actions Menu: Help... 3-25 Figure 3-30. V7000 System Control Book... 3-26 Figure 3-31. Actions on Resources: BuidExclusionList... 3-27 Figure 3-32. CPU Exclusion List... 3-28 Figure 3-33. MMU Exclusion List... 3-29 Figure 3-34. IOP Exclusion List... 3-30 Figure 3-35. Actions on Resources: Refresh... 3-31 Figure 3-36. Warning Refresh Message... 3-32 Figure 3-37. Actions on Resources: ExportList... 3-32 Figure 3-38. Resources Save As Dialog Box... 3-33 Figure 3-39. Activity History View... 3-34 Figure 3-40. Actions on Activity history: Refresh... 3-35 Figure 3-41. Warning Refresh Message... 3-36 Figure 3-42. Actions on Activity History: Export List... 3-36 Figure 3-43. Activity History Save as Dialog Box... 3-37 Figure 3-44. Action on V7000 Connect to Another Computer... 3-38 Figure 3-45. Dialog Box after Selecting Connect to Another Computer... 3-38 Figure 3-46. User Interfaces View... 3-41 Figure 3-47. Actions on User Interfaces: Refresh... 3-42 Figure 3-48. Actions on User Interfaces: Export List... 3-43 Figure 3-49. User Interfaces Save As Dialog Box... 3-43 Figure 3-50. Actions on User Interfaces: Help... 3-44 Figure 3-51. V7000 Operation Supervisor Book... 3-44 Figure 3-52. Actions on LN: Start... 3-45 Figure 3-53. Actions on LN, SYC, VOS: Refresh... 3-46 Figure 3-54. Actions on LN, SYC, VOS: Properties... 3-47 Figure 3-55. User Interfaces Property Page... 3-48 Figure 3-56. Action on User Interfaces Connect to Another Computer... 3-49 Figure 3-57. Dialog Box After Selecting Connect to Another Computer... 3-49 Figure 3-58. Description of the LN User Interface... 3-51 Figure 3-59. Commands of the File Menu for a LN... 3-54 Figure 3-60. Commands of the Edit Menu for a LN... 3-56 Figure 3-61. Commands Available in the View Group Menu for a LN... 3-57 Figure 3-62. Dialog Box before Trying to Reestablish the Communication with the VAS... 3-58 Figure 3-63. LN Console Banner after Reconnection to the VAS... 3-59 Figure 3-64. Commands Available in the System Group Menu for a Slave LN 3-60 Figure 3-65. Commands Available in the Help Group Menu for a LN... 3-61 Figure 3-66. Frame of the LN User Interface Version... 3-61 Figure 3-67. Computer Management Window when Selecting V7000 Management... 3-62 Figure 3-68. Action on Computer Management: Connect to Another Computer 3-64 Figure 3-69. Figure 3-70. Dialog Box Related to Computer Management and Connect to Another Computer... 3-65 V7000 System Control Running inside Computer Management Window... 3-66 Figure 4-1. Example of Incident Message Box... 4-1 Figure 5-1. Accessing NT Backup... 5-9 Figure 5-2. NT Backup... 5-10 x 77 A2 74US
Contents Figure 5-3. Parameter Selection... 5-11 Figure 5-4. Suppress GCOS data in the backup structure... 5-12 Figure 5-5. Case with a Media Already Used... 5-13 Figure 5-6. Requested Information... 5-13 Figure 5-7. First Confirmation for a Media Used... 5-14 Figure 5-8. Second Confirmation for a Media Used... 5-14 Figure 5-9. Backup progress... 5-15 Figure 5-10 End of backup... 5-16 Figure 5-11 Restore menu welcome screen... 5-17 Figure 5-12 Replace files option... 5-17 Figure 5-13 Selecting the restoration parameters... 5-18 Figure 5-14 Confirming the restoration... 5-19 Figure 5-15 Loading of the 4mm tape cartridge... 5-19 Figure 5-16 Restore progress... 5-20 Figure 5-17 End of restore and final status... 5-21 Figure 5-18 Restart request... 5-21 Figure 5-19 Loading the Deploy Center 5.0 tool... 5-26 Figure 5-20 Deploy Center 5.0 menu... 5-27 Figure 5-21 Tools menu... 5-28 Figure 5-22 Selecting the partitions to delete... 5-28 Figure 5-23 Confirming the destruction of the partitions... 5-29 Figure 5-24 Situation after destroying the partitions... 5-30 Figure 5-25 Selecting the source disk... 5-31 Figure 5-26 Selecting the partitions on the source disk... 5-32 Figure 5-27 Selecting the destination disk... 5-33 Figure 5-28 Selecting the backup space on the destination disk... 5-34 Figure 5-29 Status of information collected... 5-35 Figure 5-30 Copying the WIN2000 partition... 5-36 Figure 5-31 Viewing the results after copying... 5-37 Figure 5-32 Details of the destination disk after copying... 5-38 Figure 5-33 Partition resizing options... 5-39 Figure 5-34 Checking the Disable information for the second internal disk... 5-41 Figure 5-35 ServerRaid Manager tool... 5-45 Figure 5-36 Disk resynchronisation progress... 5-46 Figure 6-1. Launching Windows Computer Management User Interface... 6-1 Figure 6-2. List of the Security Groups Shown by Computer Management... 6-2 Figure 6-3. Adding an User in the V7000Operators Group (First Step)... 6-3 Figure 6-4. Adding an User in the V7000Operators Group (Second Step)... 6-4 Figure 6-5. Adding an User in the V7000Operators Group (Third Step)... 6-5 Figure 6-6. Adding a User in the V7000Operators Group (Fourth Step)... 6-6 Figure 6-7. Stop V7000 Services Dialog Box... 6-7 Figure 6-8. SYC Started and VAS Stopped... 6-9 Figure 6-9. SYC and VAS Both Started... 6-9 Figure A-1. Request to Create Diskettes...A-1 Figure A-2. Boot Diskette Creation...A-2 Figure B-1. Opening the Disk Cover...B-1 Figure B-2. Identifying Disk1 and Disk0...B-2 77 A2 74US xi
V7000 Operator's Guide Tables Table 5-1. Upgrades/backups... 5-6 xii 77 A2 74US
1. Introduction 1.1 V7000 Virtual Machine Description The DPS 7000/XTA is a new family of Bull machines. It allows to run GCOS7 and all its related environment on a Bull IA platform controlled by Microsoft Windows operating system acting as a server. V7000, also called V7000 virtual machine, is the software part provided by Bull to manage the GCOS7 environment on such a platform. GCOS 7 applications GCOS 7 V7000 : GCOS 7 VIRTUAL MACHINE DPS7000/XTA = WINDOWS BULL IA Platform INTEROP7 GATEWAYS Local or remote workstation V7000 Virtual Machine Operators Iso DSA Network TCP IP Network GCOS7 Operators Figure 1-1 General schema of a V7000 Virtual Machine 77 A2 74US 1-1
V7000 Operator's Guide V7000 Virtual Machine Configuration Description The whole resources are described in the V7000 VM configuration. The resources are named exactly as they were on a DPS 7000 (IOP, IO, MU, PX, ) in order to keep the GCOS7 operating environment. Each V7000 VM resource of the configuration is mapped on a Microsoft Windows resource. It may be actual hardware resource or on a software component of V7000 VM acting as a hardware resource of a classical DPS 7000. V7000 VM Central Processing Units are mapped on Intel Architecture platform processors. The number of IA platform CPUs must be at least twice the number of V7000 VM CPUs. The physical memory size of the platform must be at least 2 times greater than the memory described in the V7000 VM configuration. No constraint exists for the numbers of IOP and PXU except the current DPS 7000 maximum values: 24 CPU 1024 megabytes of memory 8 IOP and 64 PXU V7000 VM disks are mapped on Microsoft Windows (NTFS) files, and cartridges and printers must be physically present on the hardware platform. There must be also at least one telecom card dedicated to V7000 VM. Applications GCOS 7 C P U C P U C P U C P U IOP V7000 SAM V7000 VM V 7 0 0 0 V 7 0 0 0 V 7 0 0 0 V 7 0 0 0 Windows Drivers HBA HBA CPU IA CPU IA Figure 1-2 Platform resource mapping for V7000 VM 1-2 77 A2 74US
Introduction V7000 Virtual Machine System Administration Manager (SAM) All the features dedicated to V7000 VM control and operation are named the V7000 VM System Administration Manager (SAM). It is composed of core programs belonging to the V7000 VM engine, running on the V7000 VM server, and of User Interfaces or client parts that may run on the V7000 VM server or any Microsoft Windows workstation. The SAM is a set of tools used to operate and control V7000 Virtual Machine. Most of them are built on the client server model and use DCOM architecture: SAM server components are included in the V7000 VM engine and have no external visibility. The User Interfaces run on the client platform or on the server platform. 1.2 Hardware Platform The hardware support of V7000 Virtual Machine is a Bull Intel Architecture platform. This platform, depending on the models, can have up to 16 processors that allow to support DPS 7000 mono to octoprocessor models. The material platform is named DPS 7000/XTA. 1.3 SAM Tools and User Interfaces The SAM (System Administration Manager) tools are built on the client-server model. For each of them, the server part runs on the V7000 platform as a Windows service. It is always operational. There are two services dedicated to V7000 : SYC (System Control) and VAS (V7000 Administration Server). The client parts called user interfaces in this document, are either running or not running depending on the fact that they have been launched by a user or not. They may run either on the V7000 platform or on a remote workstation. They have the same operability anywhere they take place. Some of them are based on MMC (Microsoft Management Console). All of them have a Microsoft Windows look and feel. The V7000 users are supposed to be familiar with this technology. It is also possible to pilot V7000 VM from a remote workstation using TSE (Terminal Server facility) that is a Microsoft Windows standard product. In that case all the User Interfaces are running on the V7000 platform and only the displays of data are deported to a remote workstation through TSE. 77 A2 74US 1-3
V7000 Operator's Guide User interfaces can be started through the standard Start menu. The V7000 operators menu is available as soon as V7000 is installed on the platform and V7000 User Interfaces are installed on a workstation dedicated to V7000 VM control. CPU IOP V7000 System Control (SYC) service V7000 Administration Server (VAS) service V7000 Engine V7000 Platform System Administration Manager User Interfaces System Administration Manager User Interfaces Remote WorkStation Figure 1-3 SAM User Interfaces and Services Figure 1-4 Start menu related to V7000 user interfaces 1-4 77 A2 74US
Introduction Usage and goals of the tools Here under is a frame giving the list of the different User Interfaces and what the V7000 VM operator can do with. Tool Master Slaves Described in V7000 System control : SYC User 1 Up to 5 2.1 Interface V7000 Operation Supervisor: VOS User Interface 0 Up to 6 users 2.2 GCOS7 Consoles : LN02 User Interface 1 Up to 5 2.3 GCOS7 Consoles : LN03 User Interface 1 Up to 5 2.3 GCOS7 Consoles : LN04 User Interface 1 Up to 5 2.3 Master means that a user acts and reacts (modify a file, submit command or answer to questions). In fact the user interacts with the V7000 system. Only one master is allowed Slave means the user has a view of the related window but has no possibility to interact with the V7000 system. Master 1 means that only one person acts and reacts on V7000. 0 means no direct action or reaction on V7000 behavior. Slave means no action on V7000, but can view and display specific information related to V7000 behavior. NOTE: 1. V7000 Management combines several V7000 user interfaces into a single user interface. To use V7000 Management refer to 3.4 Use Computer Management. 2. The Interop7 User interfaces are described in the related documentation 3. Some specific administration tools are reserved to Bull. They are accessible through the V7000 Bull Services menu. 77 A2 74US 1-5
V7000 Operator's Guide 1.4 Users Categories Two user profiles are defined for V7000 Virtual Machine operation: The V7000 operator profile for leading the standard actions: start, stop and check the system operation. The Bull services profile for leading actions reserved to Bull services people (V7000 installation configuration and support actions). So, two groups are created at V7000 installation time: the V7000Operators and V7000BullServices groups. The different users that deal with V7000 User Interfaces must belong to V7000Operators. The second group is reserved to Bull services people. The groups of security are managed at Microsoft Windows level through standard operations. These operations are described in details in the Microsoft Windows documentation and are summarized in chapter 5.1 Add a user in the V7000Operator s group.the following frame shows how the different actions have to be done for V7000 operation. On WINDOWS the user rights are fixed by his membership to security groups. On GCOS7, they are fixed by his project membership. A given user can be, of course, member of several groups. This is the way to give a user several roles in DPS 7000/XTA platform operation and administration. 1-6 77 A2 74US
Introduction 1.4.1 Relation between user roles and group membership Role Security group (Windows ) or Project (GCOS7) Windows Administrator Belongs to «Administrators» group local to V7000platform Operate V7000 / Interop7 Belongs to «V7000Operators» group local to V7000platform Install V7000 / Interop7 Belongs to «Administrators» group local to V7000platform Administrate V7000 Belongs to «V7000BullServices» group local to V7000platform Use Interop7 specific Belongs to «V7000Operators» tools group local to V7000platform Customer Yes Yes Yes Possible Yes Bull Maintenance Yes, after customer agreement Yes, after customer agreement Yes Yes Yes, after customer agreement GCOS7 Administrator GCOS7 Operator Unknown on WINDOWS. Member of SYSADMIN project on GCOS7 Unknown on WINDOWS. Member of OPERATOR project on GCOS7 Yes Yes Yes, after customer agreement Yes, after customer agreement 77 A2 74US 1-7
V7000 Operator's Guide 1.4.2 Relation between user membership and actions to be done These two following frames show for a given user and depending on his membership of security groups the actions that he is authorized to do. They also indicate how do the actions on the V7000 platform and on a remote workstation. The first one is related to V7000 : User Action related to V7000 Launched through : Get platform sign Click on PlatformIdentifier_EXE.exe or Start->Programs->V7000-> Bull Services-> Platform Identifier Use «Service Control Panel» Computer->Manage->Services Use «Event viewer to display logs Computer->Manage->Events FORBIDDEN, except when Groups (Administrators, V7000BullServices) Group (Administrators) Group (Administrators) of the remote workstation Groups (Administrators, V7000BullServices) Group (V7000BullServices) Group (V7000Operators) Suppress a V7000 disk with the WINDOWS «Explorer» Manage users membership of V7000 security groups Shut Down / Restart W2K Install V7000 on a DPS 7000/XTA platform Install V7000 User Interface on a remote workstation Active a V7000 version Bull specific administration tools Operate V7000 on the local platform «Explorer» select a disk file (MSxx) then press «Delete» key. Computer->Manage->Local Users & Groups Start->Shut Down or Start->Restart Click on «Setup» of V7000 CD delivery Click on «Setup» of V7000 CD delivery Start->Programs->V7000-> Bull Services-> Version Manager Start->Programs->V7000-> Bull Services-> Start->Programs->V7000-> System Control Start->Programs->V7000-> Operation Supervisor 1-8 77 A2 74US
Introduction User Action related to V7000 Launched through : Group (V7000Operators, Distributed COM Users) of the V7000 platform Group (V7000BullServices) of the V7000 platform Operate V7000 from a remote workstation Operate V7000 from a remote workstation through Terminal Services Use Bull specific administration tools from a remote workstation through Terminal Services Start->Programs->V7000-> System Control Start->Programs-> V7000-> Operation Supervisor All the actions authorized for this Group on the V7000 platform. All the actions authorized for this Group on the V7000platform. 77 A2 74US 1-9
V7000 Operator's Guide The second one is related to INTEROP7: User Action related to INTEROP7 Launched through : Group (Administrators) Group (Administrators) of the remote workstation Group (V7000Operators) Install INTEROP7 on a V7000 platform Install an INTEROP7 on a remote workstation Configure INTEROP7 Operate INTEROP7 gateways Display INTEROP7 gateways activity Click on «Setup» of Interop7 CD delivery Connect to the Web navigator of the V7000 INTEROP7 server, then download Text editor : modify rhosts file of FTP7, then modify opengtw.ini file of OPENGTW Start->Programs->V7000-> Interop7->ASCII-EBCDIC Conversion table Management Start->Programs->V7000-> Interop7->Mailbox Configuration Start->Programs->V7000> Interop7-> Administration Servers Start->Programs->V7000-> Interop7 -> Administration Servers Start->Programs->V7000-> Interop7->NT7GW Server Start->Programs->V7000-> Interop7->OpenGTW Server Maintain INTEROP7 Command Window : 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) 1-10 77 A2 74US
Introduction User Action related to INTEROP7 Launched through : Group (V7000Operators) de la platform V7000 Configure INTEROP7 from a remote workstation Display on a remote workstation INTEROP7 gateways activity Operate INTEROP7 (installation + configuration + operation + maintenance) from a remote workstation through Terminal Services Start->Programs->V7000-> Interop7-> Administration Servers Start->Programs->V7000-> Interop7-> NT7GW Server Start->Programs->V7000-> Interop7-> OpenGTW Server All the actions allowed for INTEROP7 on the V7000 platform 77 A2 74US 1-11
V7000 Operator's Guide 1.5 Virtual Machine visibility Any user logged on a DPS7000 XTA platform can see whether the Virtual Machine and GCOS7 are running. or not. This is true for any user whatever his group membership. 1.5.1 Some recalls on Windows screen On the Windows 2000 user session screen the task bar usually takes place at the bottom of the screen. This task bar is composed of 4 areas: The taskbar includes the following: 1. Start menu 2. Quick Launch bar 3. Taskbar buttons 4. Status area 1 2 3 4 Figure 1-5 Taskbar description The Start menu contains commands that can access programs, documents, and settings. These commands include Programs, Documents, Settings, Find, Help, Run, and Shut Down. The Quick Launch bar contains shortcuts to applications. Windows provides default entries, such as Internet Explorer, and the user may add any further shortcuts that they choose. A single click on the application's icon in this area launches the application. The Shell places a button on the taskbar whenever an application is created. To switch to a window, the user clicks its window button. Applications can put icons in the status area to indicate the status of an operation or to notify the user about an event. For example, an application might put a printer icon in the status area to show that a print job is under way. The status area is located at the right edge of the taskbar (if the taskbar is horizontal) or at the bottom (if the taskbar is vertical). The status area also displays the current time if the Show clock check box is selected in the taskbar properties. 1-12 77 A2 74US
Introduction 1.5.2 V7000 Virtual machine coating in the status area Depending on the virtual machine context one two or three icons may appear in the status area. Indicates that the V7000 System Control service is running Indicates that V7000 Virtual Machine is started and still running Indicates that V7000 Virtual Machine is started and still running with a temporary key (in this case the V for V7000 is red) Indicates that GCOS7 is running and operational. This icon is displayed when GCOS7 reaches the Ready state. The figures below are the Status area of a DPS7000 / XTA platform on which : V7000 is not installed or the SYC service is stopped. (like 1-1). SYC service is running and V7000 is not started. V7000 Virtual Machine is started V7000 Virtual Machine is started with a temporary key (the V for V7000 is red) GCOS7 is running GCOS7 is running with a temporary key (the V for V7000 is red) A right click on S or V icons gives access to a Properties menu. First case : V7000 Virtual Machine is started Second case : V7000 Virtual Machine is started with a temporary key (the V for V7000 is red) 77 A2 74US 1-13
V7000 Operator's Guide When selecting the Properties menu the following message box is displayed indicating the V7000 software version currently activated. Figure 1-6 V7000 icons Software Version When a temporary key is active the following message box is displayed indicating the V7000 software version currently activated, and the expiration date of the temporary key. Figure 1-7 Icon Properties message box 1-14 77 A2 74US
Introduction When the mouse pointer is placed on one of these four icons a related tool-tip appears indicating what this icon represents. When the mouse pointer is placed on the SYC icon. When the mouse pointer is placed on the V7000 icon. When the mouse pointer is placed on the V7000 icon with temporary key. (the V for V7000 is red) When the mouse pointer is placed on the GCOS7 icon. 77 A2 74US 1-15
V7000 Operator's Guide 1-16 77 A2 74US
2. SAM Functions Here after is a short introduction to the SAM functions. Each of them is available through a specific User Interface. Specific terms are used to describe the User Interfaces. They are defined in Glossary. V7000Operators Group At V7000 Installation time the V7000Operators group is created on the V7000 platform. Before using the following interfaces it is necessary to add the user to the V7000Operators group. Refer to 5.1 Add a user in the V7000Operators group. Commonalities All the User Interfaces have a similar presentation. V7000 Virtual Machine name The User Interfaces display the V7000 Virtual Machine Name in their title bar and status bar. The V7000 Virtual Machine name is the name of the local or remote platform on which the V7000 system (S0) is running. S0 is the V7000 system name. Only one system (S0) is currently available. EXAMPLE: Local/S0 for V7000 system (S0) running on the same (local) V7000 platform. frcls3354/s0 for V7000 system (S0) running on a remote workstation named frcls3309. 77 A2 74US 2-1
V7000 Operator's Guide V7000 system state The User Interfaces display the V7000 system state in their status bar. The V7000 system states are: STOPPED RUNNING INIT IN PROGRESS TERMINATE IN PROGRESS V7000 user status Some User Interfaces display the V7000 user status in their status bar. The available V7000 user status are: MASTER SLAVE The Master user can operate on V7000 system, the Slave users can only consult the system. Some User Interfaces are neither Master nor Slave. That is when they do not interact with the V7000 kernel. They do not show any user status in their status bar. NOTE: Log off from Windows has no effect on V7000 Virtual Machine. 2-2 77 A2 74US
SAM Functions 2.1 V7000 System Control User Interface Use V7000 System Control (SYC) to manage V7000 Virtual Machine from the V7000 platform or from a remote workstation: Initialize and terminate the V7000 system, Restart and Reload the GCOS7 Operating System, View a list of resources declared in the V7000 VM active configuration, Build a CSS resources exclusion list, View messages related to the V7000 Virtual Machine activity. To use V7000 System Control, you must be logged on Windows with an account (domain\user, password) known on the V7000 platform. This account must be a member of the V7000 Operators group on the V7000 platform. To open V7000 System Control, Click Start, point to Programs, then point to V7000 and Click System Control. The following user interface is opened: Console tree Detail pane Status bar Figure 2-1. V7000 System Control on the V7000 Virtual Machine V7000 system state and user status are displayed in the status bar. For a detailed description, refer to chapter 3.1: Use V7000 System Control. 77 A2 74US 2-3
V7000 Operator's Guide NOTES: 1. If V7000 system is not running on Local platform, the following warning message appears: Computer Local is not a V7000Virtual machine. Use Connect to another computer to manage a V7000 Virtual Machine. 2. Closing the V7000 System Control User Interface has no effect on V7000 Virtual Machine. 2-4 77 A2 74US
SAM Functions 2.2 V7000 Operation Supervisor User Interface The V7000 Operation Supervisor (VOS) is related to a given V7000 Virtual Machine. This User Interface may run on a local or remote workstation. Use V7000 Operation Supervisor : To start a GCOS7 Console (LN02, LN03 or LN04) User Interface. To supervise all the User Interfaces related to a V7000 Virtual Machine. Each V7000 User Interface (LN02, LN03, LN04, SYC and VOS itself) interacting with the V7000 Virtual Machine is represented by a line. This line shows who (User Name) has launched the user interface (Client Type), where (Computer Name) it is running and gives the number of active user interfaces of same type. To use V7000 Operation Supervisor, you must be logged on Windows with an account (domain\user, password) known on the V7000 platform. This account must be a member of the V7000 Operators group on the V7000 platform. To open V7000 Operation Supervisor, click Start, point to Programs, then point to V7000 and click Operation Supervisor. The following user interface is opened: Figure 2-2. V7000 Operation Supervisor on the V7000 Virtual Machine For a detailed description, refer to chapter 3.2: Use V7000 Operation Supervisor. 77 A2 74US 2-5
V7000 Operator's Guide NOTES: 1. If V7000 system is not running on Local platform, the following warning message appears: Computer Local is not a V7000Virtual machine. Use Connect to another computer to supervise the V7000 User interfaces. 2. Closing the V7000 Operation Supervisor User Interface has no effect on V7000 Virtual Machine. 2-6 77 A2 74US
SAM Functions 2.3 GCOS7 Console: LN User Interface Use LN02, LN03 or LN04 User Interfaces to dialog with GCOS7: The GCOS7 consoles LN02, LN03 and LN04 have the same user visibility. They can be started through the V7000 Operation Supervisor (refer to 3.2.6 How to Start a LN). LN02 can also be started through the V7000 System Control during V7000 initialization time (refer to 3.1.3 How to Initialize System). A LN02, LN03 or LN04 console runs on the same platform that the User Interface from which you start it. The following user interface is opened: Figure 2-3. GCOS7 LN02 Console For a detailed description, refer to chapter 3.3: Use GCOS7 Console: LN. NOTES: Closing the GCOS7 Console LN User Interface has no effect on V7000 Virtual Machine. 77 A2 74US 2-7
V7000 Operator's Guide 2-8 77 A2 74US
3. User Interfaces Description 3.1 Use V7000 System Control 3.1.1 Overview V7000 System Control uses a two-pane view that is similar to Windows Explorer. The console tree contains three nodes (V7000, Resources, Activity history): V7000 ( V7000Platform name /S0) V7000 is the first node in the V7000 System Control console tree. This node represents the V7000 Virtual Machine. Click V7000 node and choose a command by using Action menu: 77 A2 74US 3-1
V7000 Operator's Guide Figure 3-1. Actions on V7000 System For more information about the individual actions, refer to the following paragraphs: Init (IN) (Refer to 3.1.3 How to Initialize System) Reload (RL) (Refer to 3.1.4 How to Reload System) Restart (SR) (Refer to 3.1.5 How to Restart System) Terminate (TS) (Refer to 3.1.6 How to Terminate System) TakeControl (Refer to 3.1.7 How to Become Master) Refresh (Refer to 3.1.8 How to Refresh Status Bar) Properties (Refer to 3.1.9 How to Update SOP information) Help (Refer to 3.1.10 How to Activate Online Help) Connect to another computer (Refer to 3.1.17 How to Connect to another computer) NOTES: 1. Action menu is also available by a right-click on V7000 node. 2. In Action menu the actions are grayed when the user has insufficient rights or when the actions are forbidden. 3-2 77 A2 74US
User Interfaces Description Resources Resources child node represents the Central SubSystem resources of the V7000 virtual machine. Click Resources node to view the CSS resources of the current active configuration. The following information are displayed in the details pane: Figure 3-2. CSS Resources on the V7000 Platform An icon identifies the External Type (CPU, IO, MU). A red-crossed means that the resource is excluded. 77 A2 74US 3-3
V7000 Operator's Guide Name: Present: Excluded: State: External Identifier (IPxx, MUxx, IOxx, PXxx). Yes, means that the resource is physically present on V7000 platform. No, means that resource is not physically present on V7000 platform. N/A: for no meaning, when the V7000 Virtual Machine is stopped. Present state is meaningful only for IP and MU. In fact, IO and PX are virtual resources and are always present. Yes means that the resource is excluded. No means that the resource is not excluded. Allocated means that the resource is enabled on V7000 Virtual Machine. Not Allocated means that the resource is disabled on V7000 Virtual Machine. A resource Present and Not Excluded becomes Allocated either at V7000 initialization time or when a GCOS7 reconfiguration command (MDHW resource IN) is emitted. An Allocated resource becomes not Allocated either at V7000 termination or when a resource fails (Check), or when a GCOS7 reconfiguration command (MDHW «resource» OUT) is emitted. 3-4 77 A2 74US
User Interfaces Description Click Resources node and choose a command by using Action menu: Figure 3-3. Actions on CSS Resources For more information about the individual actions, refer to the following paragraphs: Build Exclusion List (Refer to 3.1.11 How to Build Exclusion List) Refresh (Refer to 3.1.12 How to Refresh Resources List) Export List (Refer to 3.1.13 How to Copy Resources List) Help (Refer to 3.1.10 How to Activate Online help) NOTES: 1. Action menu is also available by a right-click on Resources node. 2. In Action menu the actions are grayed when the user has insufficient rights or when the actions are forbidden. 77 A2 74US 3-5
V7000 Operator's Guide Activity history Activity history child node allows to watch the V7000 Virtual Machine activity. When you open a V7000 System Control, you can view the 100 last events logged by the System Control service by clicking Activity history. If you perform V7000 command such as Init(IN), Reload(RL), Restart(SR) or Terminate(TS), the events are automatically added to the events list in the details pane. The following information are displayed in the details pane: Figure 3-4. Activity History on V7000 Virtual Machine For a detailed description refer to paragraph 3.1.14 How to view V7000 Virtual Machine Activity. 3-6 77 A2 74US
User Interfaces Description Click Activity history node and choose a command by using Action menu: Figure 3-5. Actions on Activity History For more information about the individual action, refer one of the following paragraphs: Refresh (Refer to 3.1.15 How to Refresh Messages List) ExportList (Refer to 3.1.16 How to Copy Messages List) Help (Refer to 3.1.10 How to Activate Online Help) NOTE: Action menu is also available by a right-click on Activity history node. 77 A2 74US 3-7
V7000 Operator's Guide 3.1.2 V7000 System Control Users The first user who opens the V7000 System Control, wherever he is, is automatically Master. The other users would be automatically Slave. Master User The V7000 Virtual Machine is managed by the Master user. From V7000 node, he can take actions as Init(IN), Reload(RL), Restart(SR) or Terminate(TS). From Resources node, he can exclude resources with the BuildExclusionList action. From Activity history node, he can watch the V7000 Virtual Machine activity. Slave User The Slave user can display information about V7000 Virtual Machine Resources or Activity history. He cannot take actions as Init (IN), Reload (RL), Restart (SR) or Terminate (TS). He cannot exclude resources with the BuildExclusionList action. He can ask to become Master by Take Control action. (Refer to 3.1.7 How to become Master) He can watch the V7000 Virtual Machine activity and the CSS resources. NOTE: In Action menu the actions are grayed when the user has insufficient rights or when the actions are forbidden. 3-8 77 A2 74US
User Interfaces Description 3.1.3 How to Initialize System (IN) Init(IN) action is used to initialize V7000 system You must be the Master user. (Refer to 3.1.7 How to become Master) 1. Open V7000 System Control. 2. In the console tree, click V7000. 3. Click Action, and then click Init(IN). Figure 3-6. Actions on V7000: Init(IN) 4. An Initialization dialog box displays the V7000 Virtual Machine name and the default GCOS7 Load Device given by the SOP (System Operation Panel information). 77 A2 74US 3-9
V7000 Operator's Guide Figure 3-7. Initialization Dialog You can change the Load Device. In this case, the value will be taken for this session and stored in the current "Load Device" information in V7000 property page. The System Operation Panel information is not updated by this action. To modify the SOP Load Device information use V7000 property page. (Refer to 3.1.9 How to Update SOP information) 5. Click OK to start the V7000 system initialization. 6. A Start LN02 dialog box appears to automatically start the LN02 console. Figure 3-8. Dialog for Automatic Start of LN02 GCOS7 Console 7. Click OK to start the LN02 console. 3-10 77 A2 74US
User Interfaces Description 8. Click NO if a LN02 console is already present. The Initialize V7000 system result is automatically displayed in the details pane (refer to paragraph 3.1.14 How to view V7000 Virtual Machine Activity). Figure 3-9. Initialize V7000 System Result Without Init Auto option, after Initialize System has successfully terminated you are at: IL01 OPTIONS? I : Figure 3-10. LN02 Console after Initialize V7000 System 77 A2 74US 3-11
V7000 Operator's Guide 3.1.4 How to Reload System (RL) Reload(RL) action is used to reload GCOS7 system after GCOS7 TSYS command. You must be the Master user. (Refer to 3.1.7 How to become Master). 1. Open V7000 System Control. 2. In the console tree, click V7000. 3. Click Action, and then click Reload(RL). Figure 3-11. Actions on V7000: Reload(RL) 3-12 77 A2 74US
User Interfaces Description 4. A Reload dialog box displays the V7000 Virtual Machine name and the current GCOS7 Load Device. Figure 3-12. Reload Dialog Box 5. Click OK to reload the GCOS7 system. You cannot change the current Load Device. 77 A2 74US 3-13
V7000 Operator's Guide 3.1.5 How to Restart System (SR) Restart(SR) action is used to crash GCOS7 (e.g. in case of deadlock) and automatically reload it without loss of memory contents. Restart System is used to exit from a GCOS7 deadlock. You must be the Master user. (Refer to 3.1.7 How to become Master) 1. Open V7000 System Control. 2. In the console tree, click V7000. 3. Click Action, and then click Restart(SR). Figure 3-13. Actions on V7000: Restart(SR) 4. A Restart dialog box displays the V7000 Virtual Machine name. Figure 3-14. Restart Dialog Box 3-14 77 A2 74US
User Interfaces Description 5. Click OK to restart the GCOS7 system. 6. A confirmation message appears. Figure 3-15. Confirm Restart Dialog Box 7. Click OK to confirm or Cancel to abandon. 3.1.6 How to Terminate System (TS) Terminate(TS) action is used to stop the V7000 system when GCOS has been terminated. You must be the Master user. (see 3.1.7 How to become Master) 1. Open V7000 System Control. 2. In the console tree, click V7000. 3. Click Action, and then click Terminate(TS). 77 A2 74US 3-15
V7000 Operator's Guide Figure 3-16. Actions on V7000: Terminate (TS) 4. A Terminate dialog box displays the V7000 Virtual Machine name. Figure 3-17. Terminate Dialog Box 5. Click OK to stop the V7000 system. 3-16 77 A2 74US
User Interfaces Description 6. A confirmation message appears. Figure 3-18. Confirm Terminate Dialog Box 7. Click OK to confirm or Cancel to abandon. The Terminate V7000 system result is automatically displayed in the details pane (refer to paragraph 3.1.14 How to view V7000 Virtual Machine Activity). Figure 3-19. Terminate V7000 System Result 77 A2 74US 3-17
V7000 Operator's Guide 3.1.7 How to Become Master TakeControl action is used to become Master. You must be a Slave user. Open V7000 System Control. 1. In the console tree, click V7000. 2. Click Action, and then click TakeControl. Figure 3-20. Actions on V7000: Take Control 3. A TakeControl dialog box displays the V7000 Virtual Machine name, 3-18 77 A2 74US
User Interfaces Description Figure 3-21. Take Control Dialog Box 4. Click OK to take the V7000 Virtual Machine control. 5. A confirmation message appears. Figure 3-22. Confirm Take Control Dialog Box 6. Click OK to confirm or Cancel to abandon. 7. An information message appears. Figure 3-23. Take Control Information Dialog Box 8. Click OK. 77 A2 74US 3-19
V7000 Operator's Guide The following message box is sent to the Master user to ask for his agreement: Figure 3-24. Master Dialog Box for Agreement If the master answers NO, the master stays master and the slave stays slave. A message box is sent to warn the slave that: the current MASTER does not allow to take control. If the master answers YES, the slave becomes master and the master becomes slave. If the master does not answer after a time configurated by V7000 Configuration Tool (value between 0 and 15mn, default = 5mn), the master becomes slave and the slave becomes master. 3-20 77 A2 74US
User Interfaces Description 3.1.8 How to Refresh the Status Bar To refresh the Status Bar: 1. Open V7000 System Control. 2. In the console tree, click V7000. 3. Click Action, and then click Refresh. Figure 3-25. Actions on V7000: Refresh The V7000 system state (RUNNING, INITIALIZATION IN PROGRESS, TERMINATE IN PROGRESS, STOPPED) will be written in the left part of the status bar and the user state (MASTER, SLAVE) in the right part. NOTE: The communication between V7000 System Control user interface and V7000 Administration service may be temporarily interrupted. The V7000 System Control user interface automatically connects to V7000 Administration service. The following message box is sent to refresh the V7000 contextual menu: 77 A2 74US 3-21
V7000 Operator's Guide Figure 3-26. Refresh Warning Message 3.1.9 How to Update SOP Information To view or set V7000 system information: 1. Open V7000 System Control. 2. In the console tree, click V7000. 3. Click Action, and then click Properties. Figure 3-27. Actions on V7000: Properties 3-22 77 A2 74US
User Interfaces Description 4. A properties page is displayed. Figure 3-28. V7000 Properties Page 5. You can update Load Device, Time Deviation and Auto Mode in V7000 SOP information group box. 6. Click OK to apply all pending changes and close the page. 7. Click Cancel to discard any pending changes and close the page. Apply is always disabled. A V7000 properties page displays the V7000 Virtual Machine name information following: V7000 System name: It is the name of the local or remote computer on which the V7000 system (S0) is running. EXAMPLE: Local/S0 for local computer 77 A2 74US 3-23
V7000 Operator's Guide frcls3354/s0 for remote computer named frcls3354. V7000 SOP information group box shows the following information: Load Device: (4 characters) It specifies the default GCOS7 Load Device for the next Init(IN) actions. EXAMPLE: MS01 or 9C01 (PCLC of the device) Time Deviation: (5 characters) It gives the local time deviation to be applied on the Universal Time (UT) to get the local time of the V7000 session. In fact, this deviation is applied on the Microsoft Windows server internal time (being in UT). EXAMPLE: +0100 means 1 hour after UT -2200 means 22 hours before UT Auto Mode: If it is checked, the next V7000 initialization Init(IN) will start automatically after Windows startup or V7000 incident. Configuration file: It defines locating the configuration file used for the next V7000 initialization. V7000 current state group box shows the current session information: Current Load Device and current Configuration file. None of them can be modified. User State group box shows the current user state (Refer to 3.1.2 V7000 System Control Users). 3-24 77 A2 74US
User Interfaces Description CAUTION: The server internal time is not the date and time displayed at the bottom left part of the screen, which is the local time managed by Windows. The server internal time must be expressed in Universal Time (UT) and can be set only through BIOS commands. 3.1.10 How to Activate Online Help To activate Online Help: 1. Open V7000 System Control. 2. In the console tree, click V7000 or Resources or Activity history. 3. Click Action, and then click Help. Figure 3-29. Actions Menu: Help 77 A2 74US 3-25
V7000 Operator's Guide 4. V7000 System Control book is opened: Figure 3-30. V7000 System Control Book In dialog boxes, a Help button activates a page of V7000 System Control book corresponding to this dialog box. 3-26 77 A2 74US
User Interfaces Description 3.1.11 How to Build Exclusion List BuildExclusionList action is used to exclude CSS resources from the resources list declared in active configuration. You must be the Master user. (see 3.1.7 How to become Master) 1. Open V7000 System Control. 2. In the console tree, click Resources. 3. Click Action, and then click BuildExclusionList. Figure 3-31. Actions on Resources: BuidExclusionList In the following windows: A grayed check box means that the resource is not declared in active configuration. A white check box means that the resource is declared in active configuration 77 A2 74US 3-27
V7000 Operator's Guide and not excluded. A marked check box means that the resource is excluded. You cannot exclude a resource not declared in the active configuration (grayed). You exclude a resource by a check mark. You reintroduce an excluded resource by clicking on the corresponding marked check box; the check mark disappears. 4. The CPU resources list is displayed. 5. You exclude a resource by a check mark. Figure 3-32. CPU Exclusion List 3-28 77 A2 74US
User Interfaces Description 6. Click Next. 7. The MMU resources list is displayed. 8. You exclude a resource by a check mark. Figure 3-33. MMU Exclusion List 9. Click Next. 10. The IOP resources list is displayed. 77 A2 74US 3-29
V7000 Operator's Guide 11. You exclude a resource by a check mark. Figure 3-34. IOP Exclusion List 12. Click Finish to confirm or Cancel to abandon. When you exclude an IOP, for example IO04, the associated PXs are automatically excluded. When you reintroduce an IOP, for example IO04, the associated PXs are automatically reintroduced. You can exclude some PX, without excluding the corresponding IOP, for example PX11. 3-30 77 A2 74US
User Interfaces Description After the BuildExclusionList action, the resources list is automatically refreshed, in the details pane. 3.1.12 How to Refresh Resources List Refresh action is used to refresh the CSS resources list. 1. Open V7000 System Control. 2. In the console tree, click Resources. 3. Click Action, and then click Refresh. Figure 3-35. Actions on Resources: Refresh 4. The CSS resources list is displayed in the details pane. 77 A2 74US 3-31
V7000 Operator's Guide NOTE: The communication between V7000 System Control user interface and V7000 Administration service may be temporarily interrupted. The V7000 System Control user interface automatically connects to V7000 Administration service. The following message box is sent to refresh the Resources contextual menu and the CSS resources list in the details pane: Figure 3-36. Warning Refresh Message 3.1.13 How to Copy Resources List ExportList action is used to copy the details pane resources list and export it to a text file. 1. Open V7000 System Control. 2. In the console tree, click Resources. 3. Click Action, and then click ExportList. 3-32 77 A2 74US
User Interfaces Description Figure 3-37. Actions on Resources: ExportList 4. A Save As dialog box appears. Figure 3-38. Resources Save As Dialog Box 5. Enter your file name and click Save. 77 A2 74US 3-33
V7000 Operator's Guide 3.1.14 How to View V7000 Virtual Machine Activity Activity history allows to watch the V7000 Virtual Machine activity. 1. Open V7000 System Control. 2. In the console tree, click Activity history. Figure 3-39. Activity History View When you open a V7000 System Control Interface, you get the 100 last events logged by the SYstem Control by clicking Activity histrory. When you perform V7000 actions (Init(IN), Reload(RL), ) the events are automatically added to the events list. 3-34 77 A2 74US
User Interfaces Description The following information are displayed in the details pane: Icon: An icon identifies the severity of the event. A blue arrow flags the beginning and end of V7000 initialization and V7000 stopped. An exclamation mark on a yellow triangle flags a warning error. A white cross on a red circle flags a fatal error. Time: Event time (YY/MM/DD HH/MM/SS). EventID: Event identifier. Description: Message logged by the SYC. 3.1.15 How to Refresh Messages List Refresh action is used to refresh the messages list after a communication failure between V7000 System Control user interface and V7000 Administration service. 1. Open V7000 System Control. 2. In the console tree, click Activity history. 3. Click Action, and then click Refresh. Figure 3-40. Actions on Activity history: Refresh The events logged by the SYstem Control are displayed in the details pane. 77 A2 74US 3-35
V7000 Operator's Guide NOTE: The communication between V7000 System Control user interface and V7000 Administration service may be temporarily interrupted. The V7000 System Control user interface automatically connects to V7000 Administration service and the following message box is sent to refresh the Activity history messages list in details pane: Figure 3-41. Warning Refresh Message 3.1.16 How to Copy Messages List ExportList action is used to copy the right pane messages list and export it to a text file. 1. Open V7000 System Control. 2. In the console tree, click Activity history. 3. Click Action, and then click ExportList. 3-36 77 A2 74US
User Interfaces Description Figure 3-42. Actions on Activity History: Export List 4. A Save As dialog box appears. Figure 3-43. Activity History Save as Dialog Box 5. Enter your file name and click Save. 77 A2 74US 3-37
V7000 Operator's Guide 3.1.17 How to Connect to Another Computer Connect to another computer action is used to access to another platform where V7000 system is running. 1. Open V7000 System Control. 2. In the console tree, click V7000. 3. Click Action, and then click Connect to another computer. Figure 3-44. Action on V7000 Connect to Another Computer 4. A dialog box appears. 3-38 77 A2 74US
User Interfaces Description Figure 3-45. Dialog Box after Selecting Connect to Another Computer 5. Type the name of the platform you want to access. 6. Click OK. NOTES: 1. You must be logged on Windows with an account (domain\user, password) known on the target V7000 platform and member of the V7000 Operators group in this platform 2. If remote platform is not accessible you find your previous V7000 Virtual Machine connection again. 3. If V7000 Administration service is not started or not accessible you find your previous V7000 Virtual Machine connection again. 77 A2 74US 3-39
V7000 Operator's Guide 3.2 Use the V7000 Operation Supervisor 3.2.1 Overview V7000 Operation Supervisor allows to have a general view on all the V7000 User Interfaces currently active on a V7000 Virtual Machine and start GCOS7 LN02, LN03, LN04. V7000 Operation Supervisor uses a two-pane view similar to Windows Explorer. The console tree contains only one node: User Interfaces ( V7000 platform name /S0) V7000 platform name represents the computer on which V7000 Virtual Machine is running. S0 is the V7000 system name. Only one system (S0) is currently available. EXAMPLE FOR V7000 OPERATION SUPERVISOR USER INTERFACE ON THE SAME PLATFORM THAT V7000: User Interfaces (Local/S0) EXAMPLE FOR V7000 OPERATION SUPERVISOR USER INTERFACE ON A REMOTE WORKSTATION: User Interfaces (FRCLS3309/S0) V7000 Virtual Machine is running on FRCLS3309 platform and that V7000 Operation Supervisor is remote. 3-40 77 A2 74US
User Interfaces Description 3.2.2 How to View the User Interfaces Currently Active 1. Open V7000 Operation Supervisor. 2. In the console tree, click User Interfaces. The following information are displayed in the details pane: Figure 3-46. User Interfaces View The status bar of the V7000 Operation Supervisor provides the V7000 system name and state. A line is displayed for each type of User Interface: LN02, LN03, LN04 represent the GCOS7 Console User Interface type. SYC represents the V7000 System Control User Interface type. VOS represents the V7000 Operation Supervisor User Interface type. When no User Interface is active, there is no information in the other columns. The following columns show the Computer Name on which this User Interface is running, the User Name that launched it and the user Status. The last column shows the total Number of that type of User Interface currently active. In this example: The user Dianetest has launched two LN02. One is running on FRCLS3309 platform and Dianetest user is Master. For the other LN02 refer to 3.2.8 How to View details information for a given User Interface. The user Dianetest has launched one SYC user interface running on FRCLS3309 platform. He is Master. 77 A2 74US 3-41
V7000 Operator's Guide The user Dianetest has launched two VOS user interfaces. One is running on FRCLS3309 platform. It is the user interface itself. FRCLS3309 is the name of the local platform in this example. For the other VOS refer to 3.2.8 How to View details information for a given User Interface. 3.2.3 How to Refresh information for all the User Interfaces To refresh information for all the User Interfaces: 1. Open V7000 Operation Supervisor. 2. In the console tree, click User Interfaces. 3. Click Action, and then click Refresh. Figure 3-47. Actions on User Interfaces: Refresh The information (Computer Name, User Name, Status and Number of User LN02 Interfaces) for all the User Interfaces, is updated if necessary. For example, a SYC User Interface has been closed. It is necessary to refresh to have this information. After this action, the status bar of the V7000 Operation Supervisor providing the V7000 system state is refreshed if it has changed. NOTES: 1. When a User Interface is closed, the details pane is not automatically refreshed. Use refresh to have the recent information. 2. The communication between V7000 Operation Supervisor and V7000 Administration service may be temporarily interrupted. The V7000 3-42 77 A2 74US
User Interfaces Description Operation Supervisor automatically connects to V7000 Administration service and the following message box is sent to refresh the list of currently active user interfaces in details pane: Please Retry by using Refresh 3.2.4 How to Copy User Interface List ExportList action is used to copy the right pane User Interface list and export it to a text file. 1. Open V7000 Operation Supervisor. 2. In the console tree, click User Interfaces. 3. Click Action, and then click ExportList. Figure 3-48. Actions on User Interfaces: Export List 4. A Save As dialog box appears. 77 A2 74US 3-43
V7000 Operator's Guide Figure 3-49. User Interfaces Save As Dialog Box 5. Enter your file name and click Save. 3.2.5 How to Activate Online Help To activate Online Help: 1. Open V7000 Operation Supervisor. 2. In the console tree, click User Interfaces. 3. Click Action, and then click Help. Figure 3-50. Actions on User Interfaces: Help 3-44 77 A2 74US
User Interfaces Description 4. V7000 Operation Supervisor book is opened: Figure 3-51. V7000 Operation Supervisor Book 3.2.6 How to Start a LN 1. Open V7000 Operation Supervisor. 2. In the console tree, Click User Interfaces. 3. Click the LN you want to start. 4. Click Action, and then click Start. 77 A2 74US 3-45
V7000 Operator's Guide Figure 3-52. Actions on LN: Start 5. A GCOS7 LN console appears (Refer to 3.3 Use a GCOS7 Console : LN). The detail pane is automatically refreshed. The Start action is available only on LN item. It is not possible to start another V7000 Operation Supervisor or a V7000 System Control from the V7000 Operation Supervisor User Interface. 3-46 77 A2 74US
User Interfaces Description 3.2.7 How to Refresh Information for a Given User Interface To refresh information for a given User Interface: 1. Open V7000 Operation Supervisor. 2. In the console tree, Click User Interfaces. 3. Click the User Interface (LN or SYC or VOS) you want to refresh. 4. Click Action, and then click Refresh. Figure 3-53. Actions on LN, SYC, VOS: Refresh The information (Computer Name, User Name, Status and Number of User Interfaces) corresponding to the selected Client Type (LN02 in this example) is updated if necessary. For example, if a LN02 Console has been closed, it s necessary to refresh to have the information. The status bar of the V7000 Operation Supervisor providing the V7000 system state is refreshed if it is changed. NOTES: 1. When a User Interface is closed, the details pane is not automatically refreshed. Use refresh to have the recent information. 2. The communication between V7000 Operation Supervisor and V7000 Administration service may be temporarily interrupted. The V7000 Operation Supervisor automatically connects to V7000 Administration service and the following message box is sent to refresh the list of currently active user interfaces in details pane: Please Retry by using Refresh. 77 A2 74US 3-47
V7000 Operator's Guide 3.2.8 How to View Details Information for a Given User Interface To view the User Interface details information: 1. Open V7000 Operation Supervisor. 2. In the console tree, Click User Interfaces. 3. Click the User Interface (LN, SYC or VOS) you want to view. 4. Click Action, and then click Properties. Figure 3-54. Actions on LN, SYC, VOS: Properties 5. A property page is displayed. 3-48 77 A2 74US
User Interfaces Description Figure 3-55. User Interfaces Property Page The property page gives information about the selected Client Type (LN02, LN03, LN04, SYC or VOS): In this example, SYC is the selected Client Type. Two V7000 System Control User Interface are active, running on platform named FRCLS3309. The user Dianetest is the Master user for one and a Slave for the other. A maximum of six User Interfaces actives is given for a selected item. Status: A User Interface is Master when the user can interact with V7000 (launching commands or answering system questions). A User Interface is Slave when no interaction is allowed. The user has only the opportunity to watch the current master session. The master /slave status is not significant for a user interface that does not allow any direct interaction with V7000 engine. In that case NA is displayed. So, the only possible VOS status for the VOS User Interface is NA, because the Master / Slave notion does not apply. 77 A2 74US 3-49
V7000 Operator's Guide Machine: It is the platform name on which the User Interface is running. User: It is the name of the user who has run the User Interface. 3.2.9 How to Connect to Another Computer Connect to another computer action is used to access to another platform where V7000 system is running. 1. Open V7000 Operation Supervisor. 2. In the console tree, click V7000. 3. Click Action, and then click Connect to another computer. Figure 3-56. Action on User Interfaces Connect to Another Computer 4. A dialog box appears. 3-50 77 A2 74US
User Interfaces Description Figure 3-57. Dialog Box After Selecting Connect to Another Computer 5. Select Another computer. 6. Type the name of the computer you want to access. 7. Click OK. NOTES: 1. You must be logged on Windows with an account (domain\user, password) known by the V7000 platform and member of the V7000 Operators group in this platform 2. If remote platform is not accessible you find your previous V7000 Virtual Machine connection again. 3. V7000 Administration service is not started or not accessible you find your previous V7000 Virtual Machine connection again. 77 A2 74US 3-51
V7000 Operator's Guide 3.3 Use a GCOS7 Console: LN User Interface All the GCOS7 consoles (LN) have the same user visibility. They can be started through the V7000 Operation Supervisor (refer to 3.2.6 How to Start a LN). LN02 can also be started through the V7000 System Control, at V7000 initialization time (refer to 3.1.3 How to Initialize System). A V7000 LN User Interface is a window split in two areas, the output and the input ones. The output area (upper part) is used to display the messages coming from GCOS7 and the input area (one line at the bottom of the window) is used only for input dialog questions. 3-52 77 A2 74US
User Interfaces Description Save Log as icon Find icon Set Font icon Break icon Menu bar Tool bar Display area Vertical Scroll bar Input area Horizontal Scroll bar Status bar Figure 3-58. Description of the LN User Interface The background of the output display area is gray. The user cannot modify it neither with the keyboard nor through the Paste command. The background of the input area is gray when no question is pending. It becomes white as long as a system question is pending, as shown in Figure 3-58 above. The user can resize the window using the mouse. When the width becomes too small the horizontal scroll bar becomes active in order to allow watching all the left and the right part of the lines. 77 A2 74US 3-53
V7000 Operator's Guide 3.3.1 How to Send a Break Click on the Break icon in the tool bar or press the Insert key. 3.3.2 How to Enter a Text or Answer a System Question When the background of the input area becomes white the user has to answer the question displayed at the last line of the display area. The cursor is blinking at the left side of the input area. The user can key in a text using the keyboard. Only Standard ASCII 7bits characters are valid. If you press a key corresponding to an invalid character a brief sound ( beep ) is emitted and a message appears briefly in the status bar and no character is entered in the input line. A maximum of 80 valid characters is allowed. Press the Return key to terminate. Any text can be pasted on the input line through the Microsoft Windows Paste command. The text can come from the message area or from any other Microsoft Windows tool. If the pasted text contains invalid characters a beep is emitted when the Return is pressed until you update the line. The user can use the paste command or start key in characters even if the cursor is not in the input area. In that case the text is entered at the end of the input area. You can use the and keys to display in the input area, the various lines already input, line after line. A circular buffer is used for this; it contains the last 100 lines keyed in. key goes backwards: gives the previous line. key goes forwards: gives the next line. This text can be updated through standard Microsoft Windows actions before pressing the Return key. 3-54 77 A2 74US
User Interfaces Description 3.3.3 Description of the Commands Available for a LN User Interface They are available from the menu bar. There are 5 groups of commands related to menus available in most of the common text editor tools. File group Edit group View group System group (V7000 specific) Help group Each group is accessible through mouse click or through standard Microsoft Windows key arrangement as described in the Microsoft Windows documentation. A grayed command means it is disabled, depending if the cursor is in input area or display area (see Figure 3-58). 77 A2 74US 3-55
V7000 Operator's Guide 3.3.3.1 File Group Menu Figure 3-59. Save Log As Commands of the File Menu for a LN to save the contents of the display area in a text file. You can browse through standard Microsoft Windows facility to choose the path and the name of the file. Such a file can be read by text editor tools available on Microsoft Windows. Save Log Selection As to save the contents of the text selected in the display area into a text file. You can browse through standard Microsoft Windows facility to choose the path and the name of the file. Such a file can read by text editor tools available on Microsoft Windows. 3-56 77 A2 74US
User Interfaces Description Print Log Print Log Selection Print Preview Print Selection Preview Print Setup Exit to print the contents of the message area. A secondary standard Microsoft Windows menu allows you to choose the printer and some printing options. to print a part of the message area previously selected. Standard Microsoft Windows command. It shows how the text will be as result of the Print Log command above. Standard Microsoft Windows command. It shows how the selected text will be as result of the Print Log Selection command above. Standard Microsoft Windows command. It allows to select the printer and the related parameters. to close the LN window. This does not imply anything on V7000 session. Such a LN window can be closed then reopened either on the V7000 platform or on a remote workstation. 77 A2 74US 3-57
V7000 Operator's Guide 3.3.3.2 Edit Group Menu All these items are Windows standards. Some of them are not available in the display area that cannot be altered by the user ( Cut Paste and Undo ). Figure 3-60. Commands of the Edit Menu for a LN 3-58 77 A2 74US
User Interfaces Description Copy Paste Find to move the selected area in the clipboard. It is available (not grayed) only when text is selected in the display area. to copy the clipboard contents in the input area. This is available only when the input is allowed and when the clipboard is not empty. The user can use the Paste command even when the caret (cursor) is in the display area; in that case characters are pasted at the end of the input area. to search for a text in the whole display area. A secondary standard Windows frame is used to fill the parameters. 77 A2 74US 3-59
V7000 Operator's Guide 3.3.3.3 View Group Menu Figure 3-61. Commands Available in the View Group Menu for a LN 3-60 77 A2 74US
User Interfaces Description Tool Bar if checked the tool bar is displayed under the menu groups at the top of the window: standard Microsoft Windows feature Status Bar if checked the tool bar is displayed at the true bottom of the window: standard Microsoft Windows feature. It is recommended to keep the status bar checked in order to have permanent information on V7000 status (RUNNING or STOPPED) and on the LN itself (MASTER or SLAVE) Set Font... to change the font in the window. It leads to a secondary frame with different fonts, sizes and styles. Only fixed pitch fonts are proposed. Header Refresh to prefix or not each line displayed in the message area by the date and time when the message was emitted by GCOS7. This date and time is a V7000 platform one. When you enable or disable the header this will apply from the following lines only. to update the V7000 status in the status bar. The communication between GCOS7 LN Console and V7000 Administration service may be temporarily interrupted. In most of the cases the GCOS7 LN Console automatically reconnects to V7000 Administration Service (VAS) and the following message box is sent before: Figure 3-62. Dialog Box before Trying to Reestablish the Communication with the VAS If you want to save your console session: use the Save or Save as menu in the console window then click on OK. If you do not want to save before the reconnection click on OK. 77 A2 74US 3-61
V7000 Operator's Guide If you want to exit without trying to reconnect, click on the cross in the left upper corner of the LN window. In the two first cases, the GCOS7 LN console will try to reconnect to the VAS, then the LN window is cleared, a first message is displayed on the screen followed by the 100 last messages sent by GCOS7 to this LN. Figure 3-63. LN Console Banner after Reconnection to the VAS NOTE: When the communication between the console and the VAS is broken, the right way to reconnect is to use the Refresh command in the View menu. Anyway a click on the Break command (or on the related icon) or a click anywhere in the LN console when it is inactive will start the reconnection. When the LN window is still active, Refresh is the only way to reconnect. 3-62 77 A2 74US
User Interfaces Description 3.3.3.4 System Group Menu Figure 3-64. Commands Available in the System Group Menu for a Slave LN BREAK OR INSERT KEY TAKE CONTROL Available (not grayed) only when the user is MASTER. This command is described in paragraph 3.3.1 Command reserved (not grayed) to a SLAVE LN User Interface. This command initiates the process to become master in the same way than for the SYC User Interface (refer to 3.1.7) 77 A2 74US 3-63
V7000 Operator's Guide 3.3.3.5 Help Group Menu Figure 3-65. Commands Available in the Help Group Menu for a LN Commands available through the Help menu are the following: Help topics About Client Console_EXE This gives the version of the LN User Interface component. 3-64 77 A2 74US
User Interfaces Description Figure 3-66. Frame of the LN User Interface Version 77 A2 74US 3-65
V7000 Operator's Guide 3.4 Use Computer Management 3.4.1 Overview Computer Management is a Microsoft Management Console used to manage local or remote computers. Computer Management combines several Windows administrative tools and V7000 Management into a single console tree. To open Computer Management, click Start, point to Programs, then point Administrative Tools and then click Computer Management. Figure 3-67. Computer Management Window when Selecting V7000 Management 3-66 77 A2 74US
User Interfaces Description V7000 Management tool combines several V7000 user interfaces. Use V7000 Management to: Initialize and terminate the V7000 System. Restart and Reload the Operating System. View a list of resources declared in the V7000 active configuration. Build a resources exclusion list. View messages allowed to follow the V7000 Virtual Machine activity. View V7000 User Interface running on local or remote computers. Start the GCOS7 consoles (LN01, LN02, LN03). V7000 Management uses a two-pane view that is similar to Windows Explorer. The console tree contains the V7000 user interfaces available on the local or remote computer. The nodes in this tree are V7000 Operation Supervisor and V7000 System Control. You perform tasks by selecting an interface in the console tree, and using menus and toolbars to take action on that tool in the right, or results pane which displays the tool's attributes or data. The results may be a list of what is contained by the object you select (for example, a list of V7000 user interfaces if you clicked the V7000 Operation Supervisor, or a list of events if you clicked the Activity history in V7000 System Control). NOTES: 1. You must be a member of the V7000Operators group to use V7000 Management. If you are not a member of the V7000Operators group, you won't have access rights to use V7000 Operation Supervisor and V7000 System Control. 2. If Interop7 is installed on a V7000 platform, three nodes are added to V7000 Management for Interop7 User Interfaces. 77 A2 74US 3-67
V7000 Operator's Guide 3.4.2 How to Connect to Another Computer Connect to another computer action is used to access to another platform. 1. Open Computer Management. 2. In the console tree, click Computer Management. 3. Click Action. Figure 3-68. Action on Computer Management: Connect to Another Computer 3-68 77 A2 74US
User Interfaces Description 4. Click Connect to another computer. 5. A dialog box appears. Figure 3-69. Dialog Box Related to Computer Management and Connect to Another Computer 6. Type the name of the platform you want to access. 7. Click OK. 77 A2 74US 3-69
V7000 Operator's Guide When you select V7000 Management, in the console tree, you interact with the remote V7000 Virtual Machine. The V7000 user interfaces (V7000 System Control, V7000 Operation Supervisor) are running on remote platform. Figure 3-70. V7000 System Control Running inside Computer Management Window NOTES: 1. If remote platform is not accessible you find your previous connection again. 2. When you select V7000 Management, if V7000 is not installed on platform a fatal message is written in details pane. 3. If Interop7 is installed on remote V7000 Virtual Machine, Interop7 user interfaces are added under V7000 Management and are running on remote platform. 3-70 77 A2 74US
4. Incidents 4.1 User Visible Incidents 4.1.1 Introduction 4.1.1.1 Messages Box The V7000 User Interfaces display a warning message box to inform users when an incident occurs. In the following example, six V7000 System Control User Interfaces have been launched on Local platform (1 Master and 5 Slaves), the next user who launches V7000 System Control User Interfaces will receive: Figure 4-1. Example of Incident Message Box 77 A2 74US 4-1
V7000 Operator's Guide In fact, the number of V7000 System Control User Interfaces is limited to six users. To have a list of different incidents refer to 4.1.2 Error Message Box in User Interfaces. 4.1.1.2 Activity Messages The V7000 System Control User Interface display messages in details pane, to inform users when an incident occurs. These messages are relative to V7000 Activities as Initialization, Termination, Reload or Restart processing. To have a list of fatal incidents refer to 4.1.3 Fatal errors during V7000 system Activity. 4.1.2 Error Message Box in User Interfaces Computer "computer name" is not a V7000 Virtual Machine: cause: Class not registered: V7000 is not installed on your platform. solution: Use 'Connect to another computer' to manage a V7000 Virtual Machine. Unable to access the V7000 Virtual Machine: cannot find "computer name": cause: RPC (Remote Procedure Call) Server is unavailable. solution: Use 'Connect to another computer' to manage another V7000 Virtual Machine. Access to V7000 Virtual Machine on " computer name" is denied: cause: Access is denied. solution: You must be logged on with an account (user/password) known by the V7000 Virtual Machine. 4-2 77 A2 74US
Incidents On "computer name": the user cannot manage the V7000 Virtual Machine because his access rights are insufficient. cause: The user is not member of V7000 Operators group. solution: Ask Windows administrator to add a user to V7000 Operators group. After this, if V7000 Virtual Machine is on Local computer, log off and log on to take the update into account. If V7000 Virtual Machine is on a remote computer, close your V7000 system control user interface and run another V7000 system control user interface. On "computer name": Two many V7000 System Control users are connected to the V7000 Virtual Machine. cause: The number of V7000 System Control users connected to the V7000 Virtual Machine is > 6. solution: Please retry later. Unable to Advise the V7000 Virtual Machine on "computer name": cause: Access is denied. solution: Contact your Bull Support Center. Computer "computer name" is not a V7000 Virtual Machine. cause: Class not registered: V7000 is not installed on your platform. solution: Use 'Connect to another computer' to supervise the V7000 User Interfaces running on V7000 Virtual Machine. Unable to access the V7000 Virtual Machine: cannot find "computer name". cause: RPC Server is unavailable. solution: Use 'Connect to another computer' to supervise the V7000 User Interfaces running on another V7000 Virtual Machine. 77 A2 74US 4-3
V7000 Operator's Guide On "computer name": the user cannot supervise the V7000 User Interfaces because his access rights are insufficient. cause : The user is not member of V7000 Operators group. solution : Ask Windows administrator to add a user to V7000 Operators group. After this, if V7000 Virtual Machine is on Local computer, log off and log on to take the update into account. If V7000 Virtual Machine is on a remote computer, close your V7000 system control user interface and run another V7000 system control user interface. On "computer name": Two many V7000 Operation Supervisor users are connected to the V7000 Virtual Machine. cause: The number of V7000 Operation Supervisor users connected to the V7000 Virtual Machine is > 6. solution: Please retry later. 4-4 77 A2 74US
Incidents On "computer name": Unable to connect to the V7000 Virtual Machine. cause: The client has already called the ConnectV7000 method. solution: Contact your Bull Support Center. cause: You are not a Snap-In SYC client. solution: Contact your Bull Support Center. cause: VAS internal error (Open of V7000 log file failed). solution: Contact your Bull Support Center. cause: VAS internal error (The OpenThreadToken function failed). solution: Contact your Bull Support Center. cause: VAS internal error (The GetTokenInformation function failed). solution: Contact your Bull Support Center. cause: VAS internal error (The LookupAccountSid function failed). solution: Contact your Bull Support Center. cause: VAS internal error (invalid interface pointer). solution: Contact your Bull Support Center. cause: VAS internal error (The creation of the thread for read of logfile V7000 failed). solution: Contact your Bull Support Center. 77 A2 74US 4-5
V7000 Operator's Guide 4.1.3 Fatal Errors During V7000 Virtual Machine Activity Refer to 3.1.16 How to Copy Messages list to have an example of a fatal error during Initialization processing. 4.1.3.1 V7000 Virtual Machine Initialization EventID 8100 cause: solution: EventID 8210 cause: solution: EventID 8211 cause: solution: Automatic initialization cannot be performed; no Boot Device defined. A Load Device (under the form device name or PCLC) must be defined into the Properties of the V7000 virtual machine. To do this, launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. IN (Init) failed: no V7000 Key currently installed on Diane Platform. Please, ask Bull a V7000 Key corresponding to Hardware Platform. A V7000 Key in phase with the Hardware Platform must be asked to Bull Support Center and then installed under a user belonging to the V7000BullServices group local to the V7000 Platform. IN (Init) failed: V7000 Key used for Configuration does not match currently installed Key. Please Open and Activate the Configuration. Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration, then Check and Activate it. If the existing V7000 Configuration is not compatible with the installed V7000 Key, Create and Save a new one, then Check and Activate it. Or Contact your Bull Support Center. 4-6 77 A2 74US
Incidents EventID 8212 cause: solution: EventID 8213 cause: solution: EventID 8214 cause: solution: EventID 8300 cause: solution: IN (Init) failed: invalid installed V7000 Key (does not match with Hardware Platform). Please, ask Bull a new V7000 Key corresponding to Hardware Platform. A new V7000 Key in phase with the Hardware Platform must be asked to Bull Support Center and then installed under a user belonging to the V7000BullServices group local to the V7000 Platform. IN (Init) failed: original TEMPORARY V7000 Key expired. Please, ask Bull a new V7000 Key corresponding to Hardware Platform. A new V7000 Key in phase with the Hardware Platform must be asked to Bull Support Center and then installed under a user belonging to the V7000BullServices group local to the V7000 Platform. IN (Init) failed: non original TEMPORARY V7000 Key expired. Please, ask Bull a new V7000 Key corresponding to Hardware Platform. A new V7000 Key in phase with the Hardware Platform must be asked to Bull Support Center and then installed under a user belonging to the V7000BullServices group local to the V7000 Platform. IN (Init) failed: no Configuration currently active. Please, Open and Activate a Configuration. Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open an existing V7000 Configuration or Create and Save a new one, then Check and Activate it. Or Contact your Bull Support Center. EventID 8301 cause: solution: EventID 8302 cause: solution: IN (Init) failed: internal error %1. Contact your Bull Support Center. IN (Init) failed: no %1 in %2 state. Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check the Resources Exclusion List. Or Contact your Bull Support Center. 77 A2 74US 4-7
V7000 Operator's Guide EventID 8303 cause: solution: EventID 8304 cause: solution: EventID 8305 cause: solution: EventID 8306 cause: solution: EventID 8307 cause: solution: EventID 8308 cause: solution: EventID 8309 Cause: solution: IN (Init) failed: internal error %1 during creation of %2 component. Contact your Bull Support Center. IN (Init) failed: internal error %1 during initialization of %2 component. Contact your Bull Support Center. IN (Init) failed: internal error %1 occurred for %2 component. Contact your Bull Support Center. IN (Init) failed: internal error %1 during allocation of %2. Contact your Bull Support Center. %2 failed: internal error %1 during "Set Operational Out". Contact your Bull Support Center. %2 failed: internal error %1 during Operating System Loading. Contact your Bull Support Center. %2 failed: internal error %1 during Memory Absolutization. Contact your Bull Support Center. EventID 8310 cause: solution: IN (Init) failed: internal error %1 during SRST Loading. Contact your Bull Support Center. EventID 8311 cause: solution: %2 failed: internal error %1 during Software Activation on %3. Contact your Bull Support Center. EventID 8313 cause: solution: EventID 8328 cause: solution: %2 failed: internal error %1 during access to SOP. Contact your Bull Support Center. IN (Init) failed: internal error %1 during %2 allocation. Contact your Bull Support Center. 4-8 77 A2 74US
Incidents EventID 8329 cause: solution: EventID 8330 cause: solution: EventID 8331 cause: solution: EventID 8332 cause: solution: IN (Init) failed: Configuration file %1 inconsistent. Please, check the Configuration. Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration, then Check and Activate it. If the problem persists, Open another V7000 Configuration or Create a new one, then Check and Activate it. Or Contact your Bull Support Center. %2 failed: PCLC#%1 illegal for a DISK device (LC = 00 or LC > 04 or PC > FD). Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Load Device under the form PCLC defined into the Properties of the V7000 virtual machine, or explicitly given on Initialization command. %2 failed: PCLC#%1 not declared in active Configuration. 1- Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Load Device under the form PCLC defined into the Properties of the V7000 virtual machine, or explicitly given on Initialization command. 2- Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration and Modify it, then Save, Check and Activate it. Or Contact your Bull Support Center. %2 failed: PCLC#%1 excluded from active Configuration. Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Resources Exclusion List.. 77 A2 74US 4-9
V7000 Operator's Guide EventID 8333 cause: solution: EventID 8334 cause: solution: EventID 8335 cause: solution: %2 failed: PCLC#%1 does not correspond to a DISK device. 1- Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Load Device under the form PCLC defined into the Properties of the V7000 virtual machine, or explicitly given on Initialization command. 2- Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration and Modify it, then Save, Check and Activate it. Or Contact your Bull Support Center. %2 failed: DISK device %1 not declared in active Configuration. 1- Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Load Device under the form device name defined into the Properties of the V7000 virtual machine, or explicitly given on Initialization command. 2- Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration and Modify it, then Save, Check and Activate it. Or Contact your Bull Support Center. %2 failed: DISK device %1 excluded from active Configuration. Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Resources Exclusion List.. 4-10 77 A2 74US
Incidents EventID 8336 cause: solution: %2 failed: device %1 not DISK. 1- Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Load Device under the form device name defined into the Properties of the V7000 virtual machine, or explicitly given on Initialization command. 2- Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration and Modify it, then Save, Check and Activate it. Or Contact your Bull Support Center. EventID 8337 cause: solution: %2 failed: DISK device %1 not accessible from Hardware Platform. 1- Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Load Device under the form device name or PCLC defined into the Properties of the V7000 virtual machine, or explicitly given on Initialization command. 2- Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration and Modify it, then Save, Check and Activate it. Or Contact your Bull Support Center. 77 A2 74US 4-11
V7000 Operator's Guide EventID 8338 cause: solution: %2 failed: DISK %1 not a GCOS7 boot device. 1- Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Load Device under the form device name defined into the Properties of the V7000 virtual machine, or explicitly given on Initialization command. 2- Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration and Modify it, then Save, Check and Activate it. Or Contact your Bull Support Center. EventID 8339 cause: solution: EventID 8340 cause: solution: EventID 8344 cause: solution: %2 failed: total allocated memory not sufficient to load GCOS7 Operating System. Contact your Bull Support Center. %2 failed: control zone of GCOS7 boot device %1 incoherent; "Make Up" the disk through the "GCOS7 Disk Manager" tool and Open, Check and Activate the Configuration. Launch the GCOS7 Disk Manager under a user belonging to the V7000BullServices group local to the V7000 Platform. Make Up the Disk. Then, launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration, then Check and Activate it. Or Contact your Bull Support Center. IN (Init) failed: XTA Serial Numbers for both SDM partners are identical. Please, check the Configuration. Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration and Modify it, then Save, Check and Activate it. Or Contact your Bull Support Center. 4-12 77 A2 74US
Incidents EventID 8348 cause: solution: %2 failed: Inconsistent Sharing Mode of GCOS7 boot device %1. Restore consistency using "GCOS7 Disk Manager" and "Configuration Editor". Then, Check and Activate the Configuration. Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration and Modify it, then Save, Check and Activate it and/or launch the GCOS7 Disk Manager under a user belonging to the V7000BullServices group local to the V7000 Platform. Select Define Sharing to restore Sharable/Sharing mode consistency of the GCOS7 disk. Or Contact your Bull Support Center. 4.1.3.2 V7000 Virtual Machine Reload EventID 8307 cause: solution: EventID 8308 cause: solution: EventID 8309 Cause: solution: EventID 8311 cause: solution: %2 failed: internal error %1 during "Set Operational Out". Contact your Bull Support Center. %2 failed: internal error %1 during Operating System Loading. Contact your Bull Support Center. %2 failed: internal error %1 during Memory Absolutization. Contact your Bull Support Center. %2 failed: internal error %1 during Software Activation on %3. Contact your Bull Support Center. EventID 8313 cause: solution: %2 failed: internal error %1 during access to SOP. Contact your Bull Support Center. 77 A2 74US 4-13
V7000 Operator's Guide EventID 8314 cause: solution: EventID 8315 cause: solution: EventID 8316 cause: solution: RL (Reload) failed: internal error %1 during "Reset Operational Out". Contact your Bull Support Center. RL (Reload) failed: internal error %1 during software inactivation on IP resources. Contact your Bull Support Center. RL (Reload) failed: internal error %1 during reloading of HAM structures. Contact your Bull Support Center. EventID 8317 cause: solution: RL (Reload) failed: component %1 not created. Contact your Bull Support Center. EventID 8330 cause: solution: EventID 8331 cause: solution: %2 failed: PCLC#%1 illegal for a DISK device (LC = 00 or LC > 04 or PC > FD). Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Load Device under the form PCLC defined into the Properties of the V7000 virtual machine, or explicitly given on Reload command. %2 failed: PCLC#%1 not declared in active Configuration. 1- Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Load Device under the form PCLC defined into the Properties of the V7000 virtual machine, or explicitly given on Reload command. 2- Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration and Modify it, then Save, Check and Activate it. Or Contact your Bull Support Center. 4-14 77 A2 74US
Incidents EventID 8332 cause: solution: EventID 8333 cause: solution: EventID 8334 cause: solution: %2 failed: PCLC#%1 excluded from active Configuration. Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Resources Exclusion List.. %2 failed: PCLC#%1 does not correspond to a DISK device. 1- Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Load Device under the form PCLC defined into the Properties of the V7000 virtual machine, or explicitly given on Reload command. 2- Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration and Modify it, then Save, Check and Activate it. Or Contact your Bull Support Center. %2 failed: DISK device %1 not declared in active Configuration. 1- Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Load Device under the form device name defined into the Properties of the V7000 virtual machine, or explicitly given on Reload command. 2- Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration and Modify it, then Save, Check and Activate it. Or Contact your Bull Support Center. 77 A2 74US 4-15
V7000 Operator's Guide EventID 8335 cause: solution: %2 failed: DISK device %1 excluded from active Configuration. Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Resources Exclusion List.. EventID 8336 cause: solution: %2 failed: device %1 not DISK. 1- Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Load Device under the form device name defined into the Properties of the V7000 virtual machine, or explicitly given on Reload command. 2- Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration and Modify it, then Save, Check and Activate it. Or Contact your Bull Support Center. EventID 8337 cause: solution: %2 failed: DISK device %1 not accessible from Hardware Platform. 1- Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Load Device under the form device name or PCLC defined into the Properties of the V7000 virtual machine, or explicitly given on Reload command. 2- Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration and Modify it, then Save, Check and Activate it. Or Contact your Bull Support Center. 4-16 77 A2 74US
Incidents EventID 8338 cause: solution: %2 failed: DISK %1 not a GCOS7 boot device. 1- Launch the V7000 System Control under a user belonging to the V7000Operators group local to the V7000 Platform. Check and change the Load Device under the form device name defined into the Properties of the V7000 virtual machine, or explicitly given on Reload command. 2- Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration and Modify it, then Save, Check and Activate it. Or Contact your Bull Support Center. EventID 8339 cause: solution: EventID 8340 cause: solution: %2 failed: total allocated memory not sufficient to load GCOS7 Operating System. Contact your Bull Support Center. %2 failed: control zone of GCOS7 boot device %1 incoherent; "Make Up" the disk through the "GCOS7 Disk Manager" tool and Open, Check and Activate the Configuration. Launch the GCOS7 Disk Manager under a user belonging to the V7000BullServices group local to the V7000 Platform. Make Up the Disk. Then, launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration, then Check and Activate it. Or Contact your Bull Support Center. 77 A2 74US 4-17
V7000 Operator's Guide EventID 8348 cause: solution: %2 failed: Inconsistent Sharing Mode of GCOS7 boot device %1. Restore consistency using "GCOS7 Disk Manager" and "Configuration Editor". Then, Check and Activate the Configuration. Launch the Configuration Editor Tool under a user belonging to the V7000BullServices group local to the V7000 Platform. Open your V7000 Configuration and Modify it, then Save, Check and Activate it and/or launch the GCOS7 Disk Manager under a user belonging to the V7000BullServices group local to the V7000 Platform. Select Define Sharing to restore Sharable/Sharing mode consistency of the GCOS7 disk. Or Contact your Bull Support Center. 4.1.3.3 V7000 Virtual Machine Restart EventID 8318 cause: solution: EventID 8319 cause: solution: SR (System Restart) failed: internal error %1. Contact your Bull Support Center. SR (System Restart) failed: component %1 not created. Contact your Bull Support Center. 4-18 77 A2 74US
5. Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment 5.1 Introduction On a DPS7000 / XTA or Novascale 7000 machines, backing up the system (Windows 2000 1 ), V7000 and the GCOS7 B-Disk (GCOS7 Starter disk) is essential for ensuring maximum machine availability. The operating system is used to start the machine, V7000 is used to start GCOS7 and the GCOS7 B-Disk is used to regenerate the production disk in the event of problems on the current GCOS7 system disk. This sensitive data are located on the machine's active internal disk, whereas GCOS7 data is located in the external storage bay(s). As such, it follows the standard backup/restoration procedures in GCOS7. This data must be backed up regularly to have stable references at all times, thus enabling a machine to be quickly restarted by Bull Technicians subsequent to hardware/software incidents or human errors. The backup follows all hardware/software developments on the machine. A number of solutions are available to protect against a system disk failure. These include hardware/software mirroring of both internal disks, and the partial or complete backup of this disk. Note, however, that mirroring does not protect against manipulation errors or virus attacks, which will immediately affect the mirroring disk. 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. 77 A2 74US 5-1
V7000 Operator's Guide The chosen solution thus relies on security through partial or complete backups of the system disk, thereby enabling users to quickly restore a stable situation in the event of hardware/software incidents or manipulation errors. Two backup methods can be used, depending on the situations encountered and on the machine's availability criteria defined later on: 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 5.11). Models X5: Hardware mirroring (see 5.12). Novascale 7000: Hardware mirroring (see 5.13). Logical backup, using the standard Windows NT Backup tool, to a 4mm DAT magnetic cartridge. Windows and V7000 are thus running. NOTE: At the end of the installation, the internal disk known as Disk0 in Windows Disk Manager tool is systematically cloned, and the machine is restarted on the clone. The following points pertaining to archiving will be dealt with: Internal disks on a DPS7000 / XTA machine Backup tools DPS7000 / XTA upgrades Choice of archiving tool Recommendations 5-2 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment 5.2 Internal Disks on a DPS7000 / XTA Machine A DPS7000 / XTA machine has two internal Basic disks with a capacity of 16.95 GB (or more). However, at the end of the installation, the Windows disk manager sees only one disk. This disk corresponds to Disk0 (address: Bus0, TargetId: 0, LUN: 0), 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. When delivered, it contains a physical copy (a clone) of disk0 created using the Deploy Center tool. 1 3 3 IMPORTANT: The cloning is based on this logical exclusion of the second internal disk. The disable attribute must never be removed from this disk with Windows Device Manager tool. Windows system must not see the two disks together. 77 A2 74US 5-3
V7000 Operator's Guide 5.3 Archiving Tools Two tools can be used to create a backup of Disk0. 5.3.1 Deploy Center 5.0 (Power Quest) Supplied with the platform, this tool consists of a CD-ROM and two boot diskettes, sufficient for the cloning operation. The first diskette is used to boot the machine in DOS and the second to load the tool. The CD-ROM is only used to regenerate the diskettes in the event of an incident. Generally speaking, the time taken to create the clone, including stopping Windows, cloning, then restarting Windows, does not exceed 45 minutes with an empty F:\ DATA partition. The cloning gives a true image of Disk0 (partitions C:\, E:\, F:\), capable of being started and implemented quickly (less than 15 minutes). In addition to shutting down Windows, in order to work, the tool requires a target, non-partitioned disk to create the clone, and the physical inversion of the two internal disks. 5.3.2 NT Backup (Windows) NT Backup is used to dynamically back up partitions or files to a logical support created on a 4mm DAT cartridge. It is also used to save sensitive system files including the registry under what is referred to as the system state. The system is completely backed up, including the C:\ and E :\ partitions and the system state. The F:\ partition is subject to a special NT Backup if necessary. The fuller the partitions, the longer the backup operation. NT Backup is used to back up the system with V7000 started. Using an explorer on the backup support to select the appropriate partitions or files, NT Backup is used to replace the files with their backup. Files in use are not replaced immediately. A copy is made at their final location. The replacement, requested by the tool when saving the settings, is performed when the server is shut down. The more files there are to restore, the longer it takes. 5-4 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment NOTE: The user is always prompted to restart when restoring the system state. A restoration by NT Backup requires a Windows system, even if minimal, that is valid. 77 A2 74US 5-5
V7000 Operator's Guide 5.4 Changes on a DPS7000/XTA Machine The internal Disk0 can only evolve within strict, defined conditions. The developments are of varying importance, thus conditioning the choice of archiving tool. The most important developments - performed by Bull - concern: Hardware modifications to the platform (new or replaced peripherals, model upgrades, etc.). Software upgrades concerning Windows (Service Packs) or V7000 (New Version). Installation of tools or new peripheral drivers in relation to V7000. If possible, these major changes must be combined in a single update phase to minimize down time. They require Disk0 to be cloned, without significantly increasing the machine's unavailability. Less important changes, performed by the DPS7000 / XTA machine administrator, correspond to: Customizations (adding users in the V7000 groups, etc.), Other minor modifications with no direct relation to V7000. These changes do not necessarily require a complete backup of Disk0 and/or the shutdown of the machine: an NT Backup may suffice. 5-6 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment 5.5 Choice of Archiving Tool The choice of the backup type depends on a balance between various factors, the most important of which concern the change in question and the server's availability, the expected quality and the ease with which backups can be implemented. 5.5.1 Machine Upgrades Once the machine has been installed, the active Disk0 will evolve; these developments must be archived. Upgrades leading to the shutdown of the server or concerning V7000 require a cloning, others require an NT Backup (see table below). Table 5-1. Upgrades/backups Upgrade Server Backup Frequency Hardware Shutdown Cloning (+ NT Backup recommended) For each new upgrade Software Shutdown Cloning or NT Backup For each new upgrade Software No shutdown NT Backup For each new upgrade 5.5.2 Machine Availability Beyond system upgrades and hardware changes, the machine's availability depends on whether or not the GCOS7 applications can be stopped. High-availability or critical applications cannot be interrupted: NT Backup must be used. However, the concept of high availability can be localized in time. Outside critical periods, cloning can be used (recommended when possible). Less critical applications can be stopped at a frequency that varies. In this case, cloning or NT Backup can be used. 77 A2 74US 5-7
V7000 Operator's Guide Users are urged to avoid major differences between two successive backups, and to systematically clone after a small number of NT Backups. 5.5.3 Backup Quality Implementation Backup quality is improved with a clone, since it represents a true image of Disk0 at a given moment in time. Implementation is easy: the user simply physically inverses the previously active disk and the clone before restarting the system. NOTE: Cloning requires a server shutdown. Down time spent saving is regained upon restoration, with a high level of quality The NT Backup "Restore" command activates the restoration from a 4mm DAT cartridge. 1 3 3 IMPORTANT: The user must first stop GCOS7, V7000 and any Windows applications that may still be open. After restoration, a machine restart may be requested, since it is necessary. NOTE: If a restart is requested, the Saving your settings operation may take a while (more than just a few minutes). 5.5.4 Recommendations The following recommendations must be noted: Always give preference to cloning, by grouping all major software and hardware developments together (installation of a new V7000 version, hardware changes on the DPS7000/XTA machine, etc.) bearing in mind that maximum down time will not exceed one hour, and that the backup disk is internal and easy to implement. 5-8 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment Always restart on the clone to check it is working. If possible, associate the cloning operation with a complete NT Backup before to avoid the loss of any backups during the actual cloning. The time lost during the backup is gained when the system is reconstructed. If cloning is not possible or cannot be justified, use NT Backup as many times as necessary, each time new software is installed and after any customization modifications. Validate an NT Backup by accessing the backup support's catalog to check that the data is accessible. Do not go any further. If possible, carry out a clone every 3 or 5 NT Backups to always have a stable reference (and avoid too great a divergence between the most recent NT Backup and the most recent clone). 5.5.5 Intervening Parties The backup implies three possible actions (which may involve different intervening parties): preventive backup, restoration of a stable state, and lastly disaster recovery. 5.5.5.1 Backup Bull takes care of the cloning concerning all contractual hardware and software upgrades of the DPS7000 / XTA machine and V7000. Immediately after the cloning, a complete NT Backup is also proposed. NT Backup operations, which are easier to implement, are carried out without Bull assistance. The customer is left to control the machine's load and availability. 5.5.5.2 Restoration Restoring a clone consists in physically inverting the two internal disks (see Appendix B) and restarting the machine. This operation can be done by the customer when considered appropriate, or on Bull's advice. 77 A2 74US 5-9
V7000 Operator's Guide The client can restore an NT Backup when considered appropriate, or on Bull's advice. Returning to a coherent state boils down to applying the last NT Backup on the last valid clone. 5.5.5.3 Disaster Recovery Bull takes responsibility for post-disaster restoration operations. 5-10 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment 5.6 NT Backup This section proposes a simple, easy procedure to back up the partitions of Disk0 to a 4mm DAT drive. The user must use one media support per backup (always complete) of the internal Disk0's C:\ and E:\ partitions. NT Backup is started from the Start menu: Accessories System Tools Backup by a user with Backup rights, such as the administrator (Figure 5-1). Figure 5-1. Accessing NT Backup The welcome screen gives the following choices: Backup (Figure 5-2) Restore Schedule jobs (not dealt with here) 77 A2 74US 5-11
V7000 Operator's Guide 5.6.1 Backup Figure 5-2. NT Backup 5-12 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment Click on Backup Wizard to enter the Backup parameters (Figure 5-3). Figure 5-3. 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 5-4). 77 A2 74US 5-13
V7000 Operator's Guide Figure 5-4. 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 that requests information (Figure 5-6) and which succeeds fugitive windows for collecting various information by Windows. NOTE: The user is prompted to confirm before overwriting a media support (Figure 5-5). 5-14 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment Figure 5-5. Case with a Media Already Used Choose Allocate this media to Backup now, which displays Figure 5-6. Figure 5-6. Requested Information Do not modify anything and start the Backup, represented by the progress window (Figure 5-9). 77 A2 74US 5-15
V7000 Operator's Guide NOTE: The user is prompted to confirm for a media used previously (Figure 5-7 and Figure 5-8). Figure 5-7. First Confirmation for a Media Used Figure 5-8. Second Confirmation for a Media Used 5-16 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment Figure 5-9. Backup progress At the end of the backup procedure (Figure 5-10), 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. 77 A2 74US 5-17
V7000 Operator's Guide Figure 5-10 End of backup End of backup. 5.6.2 Restoration One or more problems may cause file restoration operations. In the Restore tab, choose the DAT drive, then open out its tree structure (Figure 5-11). 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. 5-18 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment Figure 5-11 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 5-12). Figure 5-12 Replace files option 77 A2 74US 5-19
V7000 Operator's Guide Now start the restoration after selecting the parameters (Figure 5-13). Figure 5-13 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. Confirm. The confirmation of this restoration must in turn be confirmed (Figure 5-14). 5-20 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment Figure 5-14 Confirming the restoration Confirm. The tape cartridge is read and loaded (Figure 5-15). Figure 5-15 Loading of the 4mm tape cartridge 77 A2 74US 5-21
V7000 Operator's Guide The progress of the restoration is displayed via a progress window (Figure 5-16). Figure 5-16 Restore progress The following window indicates the end of the restoration (Figure 5-17): 5-22 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment Figure 5-17 End of restore and final status The user can view a 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 5-18) in order to be accepted. This should be done immediately (click Yes). Figure 5-18 Restart request Keep the cartridge as a precaution, or reuse it for a future backup. 77 A2 74US 5-23
V7000 Operator's Guide 5.6.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. it. If a.sys file is asked, browse on C:\WINNT\system32\drivers to find If a.exe file is asked, browse on C:\WINNT\system32 Based on Microsoft Knowledge Base Article 322649 5.6.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. 5-24 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment 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. 77 A2 74US 5-25
V7000 Operator's Guide 5.7 Cloning Contractual cloning is performed by Bull. DPS 7000 / XTA administrators may also decide to clone their disks on a regular basis. This section provides a simple cloning procedure. 1 3 3 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 A). The cloning tool runs in DOS. 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. 1 3 3 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. 1 3 3 IMPORTANT: At the end of each cloning operation, the user must restart on the clone to make sure it is valid, 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 B). A summary of disk to disk cloning is given below. 5-26 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment 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. 1 3 3 IMPORTANT: This procedure is available when internal disks are identical (same constructor and features). Otherwise the cloning procedure must be modified. See paragraph 5.10. Before cloning, check if the internal disks are identical (during BIOS startup, or with Windows Device Manager). 77 A2 74US 5-27
V7000 Operator's Guide The load window below is displayed when the user restarts in DOS. Figure 5-19 Loading the Deploy Center 5.0 tool The following welcome screen is then displayed. 5-28 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment Figure 5-20 Deploy Center 5.0 menu Given that the destination disk is not empty since it contains the last clone performed, the partitions must be deleted before being able to use it. 1. In the Tools menu, choose the Delete Disk Partitions option (Figure 5-21). 77 A2 74US 5-29
V7000 Operator's Guide Figure 5-21 Tools menu Figure 5-22 Selecting the partitions to delete 2. In the Physical Drives area, select Disk2, then 5-30 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment 3. Click on Delete All. 1 3 3 IMPORTANT: Make sure that disk 2 is the one selected. 4. Confirm the destruction of the data (Figure 5-23). Figure 5-23 Confirming the destruction of the partitions At the end of the operation, disk 2 regains its full free capacity (Figure 5-24). 77 A2 74US 5-31
V7000 Operator's Guide Figure 5-24 Situation after destroying the partitions 5. Click on Close (Figure 5-24). 6. Quit the Tools menu and go back to the Welcome screen (Figure 5-21) and choose Disk to Disk option. 7. The selection of the disk to copy is then proposed (Figure 5-25). 5-32 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment Figure 5-25 Selecting the source disk 8. Select Disk 1 (Figure 5-25). 9. Click on Next. 10. The characteristics of the source disk (size, partitioning, etc.) are then displayed (Figure 5-26). 77 A2 74US 5-33
V7000 Operator's Guide Figure 5-26 Selecting the partitions on the source disk 11. Click on Select All (concerns all the partitions). 12. Click on Next. 13. The destination disk Disk2 is then selected (Figure 5-27). 5-34 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment Figure 5-27 Selecting the destination disk 14. Select Disk 2. 15. Click on Next. 16. The free space that is to receive the clone is then selected (Figure 5-28). 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 submenu in the welcome screen (Figure 5-21). 77 A2 74US 5-35
V7000 Operator's Guide Figure 5-28 Selecting the backup space on the destination disk 17. Click on Next. 18. A summary of the current cloning status is displayed (Figure 5-29). 5-36 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment Figure 5-29 Status of information collected 19. Click on Finish (standard options of the process kept). 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 5-30 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. 77 A2 74US 5-37
V7000 Operator's Guide Figure 5-30 Copying the WIN2000 partition 1 3 3 IMPORTANT : If error occurs during partition cloning, please refer to paragraph 5.8. 5-38 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment 20. At the end of the process, the user is prompted to view the results (Figure 5-31). Figure 5-31 Viewing the results after copying 21. Click on Yes, in order to check the destination disk at the end of the process (Figure 5-32). 77 A2 74US 5-39
V7000 Operator's Guide Figure 5-32 Details of the destination disk after copying 22. Click on Close. 23. Go back to the tool's welcome screen (Figure 5-21) then choose Exit. 24. Remove the Deploy Center Program diskette from the drive then stop the machine. 25. Physically invert the internal disks in positions 0 and 1 then restart the machine on the clone created. 26. If the clone works properly, keep it as the active disk, otherwise go back to the reference and resume the cloning process. 1 3 3 IMPORTANT: If the capacity of the disks used in the cloning differs slightly, the procedure described previously is slightly different. Figure 5-22 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 selecting the target disk, an additional window (Figure 5-33) is displayed concerning the resizing of the partitions when the target disk is different. In this case, the user must select the Leave remaining unused space option. 5-40 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment Figure 5-33 Partition resizing options 77 A2 74US 5-41
V7000 Operator's Guide 5.8 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/. 5-42 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment 5.9 Checks in Windows after Restarting on the Clone Once the clone is started, the following must be checked: The active disk's C:\, E:\, F:\ 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. The remanence of the second internal disk's Disabled status (Figure 5-34). Figure 5-34 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. 77 A2 74US 5-43
V7000 Operator's Guide 5.10 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. 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 5.7). 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-44 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment 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. NOTE: Use NT Backup solution more often to secure the exploitation Backup. 77 A2 74US 5-45
V7000 Operator's Guide 5.11 Hardware mirroring for DPS7000/XTA 1X4 and later Models For new models from DPS7000/XTA 1X4, 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 board adapter, 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 5.11.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. 1 3 3 IMPORTANT: Thanks to automatic resynchronisation no action must be done under BIOS or with ServeRAID Manager Tool (see 5.11.5). Four procedures are defined to secure DPS7000/XTA 1X4 models for Bull Support teams. 5-46 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment 1 3 3 IMPORTANT: Three disks with identical size are necessary per rotations. A previous save is re-used to create a new one. 5.11.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 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 5.11.5) ] The stop duration of the platform is minimal. The total resynchronisation duration takes about 2 hours for 36GB disks. 5.11.2 Back to a steady system This case corresponds to come back to a previous steady save when current system is unstable. 1. Stop GCOS7 then V7000 2. Shut down the Platform 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 6. Connect to Windows 7. Restart V7000 then GCOS7 77 A2 74US 5-47
V7000 Operator's Guide 8. Insert the new disk in the empty slot. 9. [ Launch ServerRaid Manager tool from Start Menu/ServerRaid Manager to control the resynchronisation progress (see 5.11.5) ] 5.11.3 Disk Substitution in case of disk Hardware Failure Windows running 1. Locate the failed disk (see 5.11.5 if necessary) 2. Remove the failed disk in front of the Platform 3. Insert the new disk in the empty slot. 4. [ Launch ServerRaid Manager tool from Start Menu/ServerRaid Manager to control the resynchronisation progress (see 5.11.4) ] No need to stop GCOS7, V7000 and Windows because resynchronisation is automatic. 5.11.4 Disk Substitution in case of disk Hardware Failure Windows stopped Restart the platform with only one disk and insert the new disk Windows running. [ Launch ServerRaid Manager tool from Start Menu/ServerRaid Manager to control the resynchronisation progress (see 5.11.4) ] 5.11.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 5-35) 5-48 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment Figure 5-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 5-36) and log messages in underside panel. 77 A2 74US 5-49
V7000 Operator's Guide Figure 5-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). 5-50 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment 5.12 Hardware mirroring for DPS7000/XTA X5 For new models DPS7000/XTA X5, cloning of system disk with Deploy Center Tool is no more used to secure the V7000 Platform. One LSI Logic adapter on Motherboard in Raid1 configuration manages the both internal disks. The save process is based on the automatic resynchronisation between the two internal disks when one is physically changed. This resynchronisation is managed by the LSI Logic adapter and can visually be followed with MegaRAID Client Tool (see 5.12.5). During resynchronisation, surviving disk of Raid configuration is physically mirrored on the target disk on which 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 and must not be changed or modified out of recovery process. 1 3 3 IMPORTANT: Thanks to automatic resynchronisation no action must be done under BIOS or with MegaRAID Client Tool (see 5.10.5). Four procedures are defined to secure DPS7000/XTA X5 models for Bull Support teams. 1 3 3 IMPORTANT: Three disks with identical size are necessary per rotations. A previous save is reused to create a new one. 77 A2 74US 5-51
V7000 Operator's Guide The front of the server is described below (Figure 5-37). Figure 5-37 Front of X5 Model NOTE: The Current Clone Disk (ID 2) is disconnected (or not fully plugged). 5.12.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 disk ID 1 and preserve it 4. Restart the Platform with only one disk (ID 0) 5. Connect to Windows 6. Launch MegaRAID Client Tool to control the resynchronisation progress 7. Insert the new disk in the empty slot 8. Restart V7000 then GCOS7 The stop duration of the platform is minimal. The total resynchronisation duration takes about 1.5 hours for 70 GB disks. 5-52 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment 5.12.2 Back to a steady system This case corresponds to come back to a previous steady save when current system is unstable or unusable. 1. Stop GCOS7 then V7000 2. Shut down the Platform 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 6. Connect to Windows 7. Launch MegaRAID Client Tool to control the resynchronisation progress 8. Insert the new disk in the empty slot 9. Visualize the resynchronisation progress 10. Restart V7000 then GCOS7 5.12.3 Disk Substitution in case of disk Hardware Failure and Windows running 1. Locate the failed disk (see Physical Devices Panel Figure 5-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) 4. Launch MegaRAID Client Tool to control the resynchronisation progress No need to stop GCOS7, V7000 and Windows because resynchronisation is automatic. 77 A2 74US 5-53
V7000 Operator's Guide 5.12.4 Disk substitution in case of disk Hardware Failure and Windows stopped Restart the platform with only one disk (Reference or Clone) and insert the new disk when Windows is running. 5.12.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. It is launched from Start Menu/Power Console Plus/MegaRAID Client (Figure 5-38). Figure 5-38 Server Selection mode Select View only. Then Main Windows appears (Figure 5-39) in View Only Mode. 5-54 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment Figure 5-39 MegaRAID Client Main Console When a problem occurs on one physical disk, its state changes from Onln to Failed (Figure 5-40). 77 A2 74US 5-55
V7000 Operator's Guide Figure 5-40 Disk state change When a new disk is inserted, automatic resynchronisation starts (Figure 5-42) after SCSI rescan. NOTE: If the state of inserted disk stayes Failed (Figure 5-40), right click on red icon disk then Properties (Figure 5-41). 5-56 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment Figure 5-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 5-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. 77 A2 74US 5-57
V7000 Operator's Guide Figure 5-42 Start of disks resynchronisation The resynchronisation is logged (Figure 5-43) and when finished, progression window is closed. Disks state is the same (OnLn) as shown in Figure 5-39. To see log, click on Adpater Menu then View Log. Figure 5-43 Log File opening 5-58 77 A2 74US
Backing up a DPS7000/XTA or Novascale 7000 Platform's System Environment 5.13 Hardware mirroring for Novascale 7000 On Novascale 7000 Platform, Windows system disk is located in external Chaparral sub-system disk. Backup of Windows system disk is more difficult to do, depending on subsystem disk management and Novascale platform architecture. Chaparral sub-system management is described in 86A145EG00: BULL SR- 0812 RAIDStorage System User s Guide documentation. Cloning and mirroring operations are risky; thus Bull Support makes backup of Windows system disk and Raid1 mirroring. 77 A2 74US 5-59
V7000 Operator's Guide 5-60 77 A2 74US
6. How to and Check Lists 6.1 How to Add a User in the V7000Operators Group This is a specific Windows operation. We describe below the basic operation, please refer to the Microsoft documentation for details. Adding a user un the V7000Operators Group must be done by a member of the Windows administrators group. Use the following procedure: 1. In the start menu click on Computer Management (Figure 6-1). 77 A2 74US 6-1
V7000 Operator's Guide Figure 6-1. Launching Windows Computer Management User Interface 2. The Computer Management window appears; click on the + of the System Tools for expansion of the contents then expand (Click on + ) the Local Users and Groups then click on Groups. 3. The list of the known groups of this platform is displayed in the result pane: 6-2 77 A2 74US
How to and Check Lists Figure 6-2. List of the Security Groups Shown by Computer Management 4. A right click on V7000Operators group in the result pane shows a menu for adding a user to the group. Figure 6-3. Adding an User in the V7000Operators Group (First Step) This operation is also possible through the Properties menu. 77 A2 74US 6-3
V7000 Operator's Guide Figure 6-4. Adding an User in the V7000Operators Group (Second Step) In this example, there is no pre-existing user in the V7000Operators group. 6-4 77 A2 74US
How to and Check Lists 5. Click on the Add button (Figure 6-5), then on the arrow of the dialog box Look in that allows choosing a domain. Figure 6-5. Adding an User in the V7000Operators Group (Third Step) In this example we have selected the user Dianetest belonging to the DIANE- DOM domain. 77 A2 74US 6-5
V7000 Operator's Guide 6. Clicking on Add will introduce this user in the list of the users in the lowest frame. Figure 6-6. Adding a User in the V7000Operators Group (Fourth Step) 4. Clicking on OK will introduce them in the V7000Operators group. NOTE: V7000 installation process creates a user called V7000Engine in the Administrators group. This user must always be present in the Administrators group because SYC and all the V7000 components are launched under his name. Nobody can log on as V7000Engine. 6-6 77 A2 74US
How to and Check Lists 6.2 How to Start/stop the V7000 Services The V7000 Administration service and V7000 System Control service are automatically started at V7000 platform boot. When the V7000 Administration Service aborts it is automatically restarted at the first click in one of the User Interfaces. When the System Control service aborts it restarts automatically the first time in the same day. When the user gets messages indicating that SYC is not responding he has first to check if it is stopped then he has to restart it manually as described below. 6.2.1 How to Stop the V7000 Services To open Services: 1. Click Start. 2. Point to Settings. 3. Click Control Panel. 4. Double-click Administrative Tools. 5. Double-click Services. 6. Right-click the V7000 System Control Service. 7. Click Stop. The following dialog box is displayed: 77 A2 74US 6-7
V7000 Operator's Guide Figure 6-7. Stop V7000 Services Dialog Box Click Yes to stop the V7000 Administration Service and the V7000 System Control Service. 6.2.2 How to Start the V7000 Services To open Services: 1. Click Start. 2. Point to Settings. 3. Click Control Panel. 4. Double-click Administrative Tools. 5. Double-click Services. 6. Right-click the V7000 System Control Service. 7. Click Start. 8. Right-click the V7000 Administration Service. 9. Click Start. The V7000 Administration Service and the V7000 System Control Service are started. 6-8 77 A2 74US
How to and Check Lists 6.2.3 How to Check the V7000 Services Status To open Services: 1. Click Start. 2. Point to Settings. 3. Click Control Panel. 4. Double-click Administrative Tools. 5. Double-click Services. 6. Find the V7000 System Control Service and the V7000 Administration Service lines. If the status is automatic the related service is stopped. When the status is Started the service is running. Figure 6-8. SYC Started and VAS Stopped 77 A2 74US 6-9
V7000 Operator's Guide Figure 6-9. SYC and VAS Both Started 6-10 77 A2 74US
How to and Check Lists 6.3 How to Install a New V7000 Version Bull has supplied a new release or technical status of V7000 software. The checklist is: This operation is carried out by Bull maintenance. The customer has no specific task to perform. 6.4 How to Install a New GCOS7 Technical Status Bull has supplied a new release or technical status of GCOS7 and you want to install and operate with this new version. The checklist is: Perform the tasks described in the GCOS7 SICUG (System Installation Configuration and Updating Guide) Perform any tasks described in the CSB (Customer Service Bulletin) associated with the new Technical Status of GCOS7. 6.5 How to Exit from a V7000 SYSTEM CHECK A system Check has occurred on your system and you want to restart operations. The checklist is: The system automatically restarts (re-initializes) The customer has no specific task to perform except to call the Service Center. 77 A2 74US 6-11
V7000 Operator's Guide 6.6 How to Exit from a GCOS7 CRASH A crash has occurred on GCOS7 and you want to restart operations The checklist is: GCOS7 is reloaded automatically. You do not need to take any action. At the ISL (IL01 question), request that a dump be taken After the system restarts, the customer has no other specific task to perform except saving the dump in order to save the information for maintenance purposes. 6.7 How to Exit from a GCOS7 DEADLOCK A deadlock has occurred on GCOS7 and you want to restart the operations The checklist is: Send to an external event to GCOS7 using the SR command as described in 2.2.3 paragraph. A GCOS7 CRASH will occur. At the ISL (IL01 question), request that a dump be taken After the system restarts, the customer has no other specific task to perform except saving the dump in order to save the information for maintenance purposes. 6.8 How to Build or Modify a V7000 Configuration This is the case when you want to add a GCOS7 device or to change the number of GCOS7 CPU or IO processors. The checklist is: This operation is carried out by Bull maintenance with the customer in collaboration. The customer has no specific task to perform, but the GCOS7 configuration Job must be operational to take into account the new configuration. 6-12 77 A2 74US
How to and Check Lists 6.9 How to Make Deliberate General Power Off of the Whole Platform Refer to GCOS7-V10 System Operator s Guide. 6.10 In Case of General Power Failure for the Whole Platform Refer to GCOS7-V10 System Operator s Guide. 6.11 How to Exit from a General V7000 System Deadlock In this case, the V7000 system is in a state such that none of the usual operations (Restart System, Terminate System) solves the problem, but the Microsoft Windows system still goes on. Fortunately this case occurs rarely. The checklist is: Press CTRL+ALT+DEL keys and choose Task Manager. Right click on CPU_FW.exe and choose End Process. If this operation succeeds, V7000 behaves as if a System Check happens and restarts automatically, otherwise see 6.12. 77 A2 74US 6-13
V7000 Operator's Guide 6.12 How to Exit from a General Platform Deadlock In this case, the V7000 system and Microsoft Windows are in a state such that none of the usual operations (Restart System, Terminate System for V7000 and any click is effective for Microsoft Windows ) solves the problem. Fortunately this case occurs rarely. The checklist is: Try to log off be pressing CTRL+ALT+DEL keys and choose log off, then log on. After this if the mouse click is operational in any window it was only a problem in the graphic user management. GCOS7 is still operational, nothing else has to be done by the user. When loging off then logging on lead to the same situation of general deadlock press the CTRL+ALT+DEL keys then choose System Shut Down and after that restart the system. When Windows is operational launch the Bull Collect Tool as described in the V7000 Configuration and Maintenance Guide, to collect all the error context information. The system automatically restarts (re-initializes) when AUTO mode is on. If it is not the case you have to restart V7000 and GCOS7 like in case of V7000 system Check. The customer has no specific task to perform except to call the Service Center and give the collected information. 6-14 77 A2 74US
A. 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 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 A-1). 77 A2 74US A-1
V7000 Operator's Guide Figure A-1. Request to Create Diskettes Click on Next (Figure A-1). 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). Figure A-2. Boot Diskette Creation A-2 77 A2 74US
Deploy Center V5.0 Installation 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 74US A-3
V7000 Operator's Guide A-4 77 A2 74US
B. Reversing the Disks Open the machine cabinet, then open the internal disk compartment (Figure B-1) by unscrewing the top two screws. Figure B-1. Opening the Disk Cover 77 A2 74US B-1
V7000 Operator's Guide Then unclip Disk0 and Disk1 (Figure B-2). Figure B-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. B-2 77 A2 74US