OpenVMS Cluster Systems - OpenVMS Systems - HP

More documents

Recommendations

Info

Preparing a Shared Environment 5.6 Coordinating Startup Command Procedures 5.6.1 OpenVMS Startup Procedures Several startup command procedures are distributed as part of the OpenVMS operating system. The SYS$SYSTEM:STARTUP.COM command procedure executes immediately after OpenVMS is booted and invokes the site-specific startup command procedures described in the following table. Procedure Name Invoked by Function SYS$MANAGER: SYPAGSWPFILES.COM SYS$MANAGER: SYCONFIG.COM SYS$MANAGER: SYSECURITY.COM SYS$MANAGER: SYLOGICALS.COM SYS$MANAGER: SYSTARTUP_VMS.COM SYS$SYSTEM: STARTUP.COM SYS$SYSTEM: STARTUP.COM SYS$SYSTEM: STARTUP.COM SYS$SYSTEM: ST ARTUP.COM SYS$SYSTEM: STARTUP.COM A file to which you add commands to install page and swap files (other than the primary page and swap files that are installed automatically). Connects special devices and loads device I/O drivers. Defines the location of the security audit and archive files before it starts the security audit server. Creates systemwide logical names, and defines system components as executive-mode logical names. (Clusterwide logical names should be defined in SYSTARTUP_VMS.COM.) Cluster common disks can be mounted at the end of this procedure. Performs many of the following startup and login functions: • Mounts all volumes except the system disk. • Sets device characteristics. • Defines clusterwide logical names • Initializes and starts batch and print queues. • Installs known images. • Starts layered products. • Starts the DECnet software. • Analyzes most recent system failure. • Purges old operator log files. • Starts the LAT network (if used). • Defines the maximum number of interactive users. • Announces that the system is up and running. • Allows users to log in. The directory SYS$COMMON:[SYSMGR] contains a template file for each command procedure that you can edit. Use the command procedure templates (in SYS$COMMON:[SYSMGR]*.TEMPLATE) as examples for customization of your system’s startup and login characteristics. 5.6.2 Building Startup Procedures The first step in preparing an OpenVMS Cluster shared environment is to build a SYSTARTUP_VMS command procedure. Each computer executes the procedure at startup time to define the operating environment. 5–14 Preparing a Shared Environment
Preparing a Shared Environment 5.6 Coordinating Startup Command Procedures Prepare the SYSTARTUP_VMS.COM procedure as follows: Step Action 1 In each computer’s SYS$SPECIFIC:[SYSMGR] directory, edit the SYSTARTUP_ VMS.TEMPLATE file to set up a SYSTARTUP_VMS.COM procedure that: • Performs computer-specific startup functions such as the following: Setting up dual-ported and local disks Loading device drivers Setting up local terminals and terminal server access • Invoking the common startup procedure (described next). 2 Build a common command procedure that includes startup commands that you want to be common to all computers. The common procedure might contain commands that: • Install images • Define logical names • Set up queues • Set up and mount physically accessible mass storage devices • Perform any other common startup functions Note: You might choose to build these commands into individual command procedures that are invoked from the common procedure. For example, the MSCPMOUNT.COM file in the SYS$EXAMPLES directory is a sample common command procedure that contains commands typically used to mount cluster disks. The example includes comments explaining each phase of the procedure. 3 Place the common procedure in the SYS$COMMON:[SYSMGR] directory on a common system disk or other cluster-accessible disk. Important: The common procedure is usually located in the SYS$COMMON:[SYSMGR] directory on a common system disk but can reside on any disk, provided that the disk is cluster accessible and is mounted when the procedure is invoked. If you create a copy of the common procedure for each computer, you must remember to update each copy whenever you make changes. 5.6.3 Combining Existing Procedures To build startup procedures for an OpenVMS Cluster system in which existing computers are to be combined, you should compare both the computer-specific SYSTARTUP_VMS and the common startup command procedures on each computer and make any adjustments required. For example, you can compare the procedures from each computer and include commands that define the same logical names in your common SYSTARTUP_VMS command procedure. After you have chosen which commands to make common, you can build the common procedures on one of the OpenVMS Cluster computers. 5.6.4 Using Multiple Startup Procedures To define a multiple-environment cluster, you set up computer-specific versions of one or more system files. For example, if you want to give users larger working set quotas on URANUS, you would create a computer-specific version of SYSUAF.DAT and place that file in URANUS’s SYS$SPECIFIC:[SYSEXE] directory. That directory can be located in URANUS’s root on a common system disk or on an individual system disk that you have set up on URANUS. Preparing a Shared Environment 5–15
Page 1 and 2:
OpenVMS Cluster Systems Order Numbe
Page 3 and 4:
Contents Preface ..................
Page 5 and 6:
4 The OpenVMS Cluster Operating Env
Page 7 and 8:
6.5.4 Disk Rebuild Operation ......
Page 9 and 10:
10 Maintaining an OpenVMS Cluster S
Page 11 and 12:
D Sample Programs for LAN Control D
Page 13 and 14:
G NISCA Transport Protocol Channel
Page 15 and 16:
Tables 7-3 Clusterwide Generic Prin
Page 17:
F-6 Channel Formation .............
Page 20 and 21:
Appendix C provides troubleshooting
Page 22 and 23:
xxii bold text This typeface repres
Page 24 and 25:
Introduction to OpenVMS Cluster Sys
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
OpenVMS Cluster Concepts 2.1 OpenVM
Page 38 and 39:
OpenVMS Cluster Concepts 2.1 OpenVM
Page 40 and 41:
OpenVMS Cluster Concepts 2.3 Ensuri
Page 42 and 43:
OpenVMS Cluster Concepts 2.3 Ensuri
Page 44 and 45:
OpenVMS Cluster Concepts 2.4 State
Page 46 and 47: OpenVMS Cluster Concepts 2.5 OpenVM
Page 48 and 49: OpenVMS Cluster Concepts 2.6 Synchr
Page 50 and 51: OpenVMS Cluster Concepts 2.8 Disk A
Page 53 and 54: 3 OpenVMS Cluster Interconnect Conf
Page 55 and 56: OpenVMS Cluster Interconnect Config
Page 67 and 68: 4 The OpenVMS Cluster Operating Env
Page 69 and 70: Table 4-1 Information Required to P
Page 71 and 72: Table 4-1 (Cont.) Information Requi
Page 73 and 74: Table 4-2 Installing Layered Produc
Page 75 and 76: The OpenVMS Cluster Operating Envir
Page 83 and 84: 5 Preparing a Shared Environment In
Page 85 and 86: Preparing a Shared Environment 5.2
Page 91 and 92: Table 5-2 Alias Collisions and Outc
Page 95: Preparing a Shared Environment 5.5
Page 101 and 102: Table 5-3 (Cont.) Security Files Fi
Page 103 and 104: Table 5-3 (Cont.) Security Files Fi
Page 107 and 108: 6 Cluster Storage Devices One of th
Page 109 and 110: Figure 6-1 Dual-Ported Disks Networ
Page 111 and 112: Figure 6-3 Configuration with Clust
Page 113 and 114: Cluster Storage Devices 6.2 Naming
Page 127 and 128: Cluster Storage Devices 6.3 MSCP an
Page 129 and 130: Cluster Storage Devices 6.4 MSCP I/
Page 131 and 132: Cluster Storage Devices 6.5 Managin
Page 133 and 134: Cluster Storage Devices 6.5 Managin
Page 135 and 136: Cluster Storage Devices 6.6 Shadowi
Page 137 and 138: 7.1 Introduction 7 Setting Up and M
Page 139 and 140: Setting Up and Managing Cluster Que
Page 141 and 142: Figure 7-1 Sample Printer Configura
Page 143 and 144: Figure 7-2 Print Queue Configuratio
Page 145 and 146: Setting Up and Managing Cluster Que
Page 147 and 148:
Setting Up and Managing Cluster Que
Page 149 and 150:
Page 151 and 152:
Page 153:
Page 156 and 157:
Configuring an OpenVMS Cluster Syst
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 199 and 200:
9 Building Large OpenVMS Cluster Sy
Page 201 and 202:
Building Large OpenVMS Cluster Syst
Page 203 and 204:
Table 9-3 (Cont.) Checklist for Sat
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Table 9-8 (Cont.) Controlling Satel
Page 211 and 212:
Table 9-8 (Cont.) Controlling Satel
Page 213 and 214:
Potential Hot Files Methods to Help
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
10 Maintaining an OpenVMS Cluster S
Page 221 and 222:
Maintaining an OpenVMS Cluster Syst
Page 223 and 224:
Example 10-1 Sample NETNODE_UPDATE.
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
• CLUSTER_SHUTDOWN • REBOOT_CHE
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
10.12 Restoring Cluster Quorum Main
Page 239 and 240:
Command Purpose Maintaining an Open
Page 241:
Page 244 and 245:
Cluster System Parameters A.1 Value
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Building Common Files B.1 Building
Page 261 and 262:
C.1 Diagnosing Computer Failures C
Page 263 and 264:
Table C-1 (Cont.) Sequence of Booti
Page 265 and 266:
Step Action Cluster Troubleshooting
Page 267 and 268:
Page 269 and 270:
Cluster Troubleshooting C.3 Satelli
Page 271 and 272:
Page 273 and 274:
Table C-2 (Cont.) Alpha Booting Mes
Page 275 and 276:
IF... THEN... The startup procedure
Page 277 and 278:
Possible Bugcheck Causes Recommenda
Page 279 and 280:
Cluster Troubleshooting C.10 Diagno
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Table C-5 Informational and Other E
Page 287 and 288:
Entry Description Cluster Troublesh
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Table C-6 (Cont.) Port Messages for
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Table C-8 (Cont.) OPA0 Messages Har
Page 301 and 302:
D Sample Programs for LAN Control S
Page 303 and 304:
Sample Programs for LAN Control D.3
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Location Action Sample Programs for
Page 311:
Page 314 and 315:
Subroutines for LAN Control E.2 Sta
Page 316 and 317:
Subroutines for LAN Control E.3 Sto
Page 318 and 319:
Subroutines for LAN Control E.4 Cre
Page 320 and 321:
Subroutines for LAN Control E.5 Cre
Page 322 and 323:
Subroutines for LAN Control E.7 Sto
Page 324 and 325:
Troubleshooting the NISCA Protocol
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 354 and 355:
Page 356 and 357:
Page 359 and 360:
G NISCA Transport Protocol Channel
Page 361 and 362:
NISCA Transport Protocol Channel Se
Page 363 and 364:
NISCA Transport Protocol Channel Se
Page 365 and 366:
A Access control lists See ACLs ACL
Page 367 and 368:
CLUSTER_AUTHORIZE.DAT files (cont
Page 369 and 370:
Disks system (cont’d) creating du
Page 371 and 372:
HSZ subsystems, 1-4 I Installation
Page 373 and 374:
MODPARAMS.DAT file (cont’d) examp
Page 375 and 376:
Packets capturing data, F-26 maximu
Page 377 and 378:
SAVE_FEEDBACK option, 10-10 SCA (Sy
Page 379 and 380:
System parameters (cont’d) MPDEV_
Page 381:
Voting members, 2-6 adding, 8-10, 8
show all

OpenVMS Cluster Systems - OpenVMS Systems - HP

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?