OpenVMS Cluster Systems - OpenVMS Systems - HP

More documents

Recommendations

Info

Sample Programs for LAN Control D.5 Using the Network Failure Analysis Program Table D–2 (Cont.) Creating a Physical Description of the Network Step Action Comments 4 Classify each component into one of the following categories: • Node: VAX or Alpha system in the OpenVMS Cluster configuration. • Adapter: LAN adapter on the system that is normally used for OpenVMS Cluster communications. • Component: Generic component in the network. Components in this category can usually be shown to be working if at least one path through them is working. Wiring concentrators, DELNI interconnects, DEMPR repeaters, LAN bridges, and LAN segments and rings typically fall into this category. • Cloud: Generic component in the network. Components in this category cannot be shown to be working even if one or more paths are shown to be working. 5 Use the component labels from step 3 to describe each of the connections in the OpenVMS Cluster communications network. 6 Choose a node or group of nodes to run the network failure analysis program. D–6 Sample Programs for LAN Control The cloud component is necessary only when multiple paths exist between two points within the network, such as with redundant bridging between LAN segments. At a high level, multiple paths can exist; however, during operation, this bridge configuration allows only one path to exist at one time. In general, this bridge example is probably better handled by representing the active bridge in the description as a component and ignoring the standby bridge. (You can identify the active bridge with such network monitoring software as RBMS or DECelms.) With the default bridge parameters, failure of the active bridge will be called out. You should run the program only on a node that you included in the physical description when you edited LAVC$FAILURE_ANALYSIS.MAR. The network failure analysis program on one node operates independently from other systems in the OpenVMS Cluster. So, for executing the network failure analysis program, you should choose systems that are not normally shut down. Other good candidates for running the program are systems with the following characteristics: • Faster CPU speed • Larger amounts of memory • More LAN adapters (running the NISCA protocol) Note: The physical description is loaded into nonpaged pool, and all processing is performed at IPL 8. CPU use increases as the average number of network components in the network path increases. CPU use also increases as the total number of network paths increases.
Sample Programs for LAN Control D.5 Using the Network Failure Analysis Program D.5.2 Edit the Source File Follow these steps to edit the LAVC$FAILURE_ANALYSIS.MAR program. Step Action 1 Copy the following files from SYS$EXAMPLES to your local directory: • LAVC$FAILURE_ANALYSIS.MAR • LAVC$BUILD.COM 2 Use the OpenVMS Cluster network map and the other information you collected to edit the copy of LAVC$FAILURE_ANALYSIS.MAR. Example D–1 shows the portion of LAVC$FAILURE_ANALYSIS.MAR that you edit. Example D–1 Portion of LAVC$FAILURE_ANALYSIS.MAR to Edit ; *** Start edits here *** ; ; ; ; ; Edit 1. Define the hardware components needed to describe the physical configuration. NEW_COMPONENT NEW_COMPONENT NEW_COMPONENT NEW_COMPONENT NEW_COMPONENT NEW_COMPONENT SYSTEM LAN_ADP DEMPR DELNI SEGMENT NET_CLOUD NODE ADAPTER COMPONENT COMPONENT COMPONENT CLOUD ; Edit 2. ; ; Diagram of a multi-adapter local area OpenVMS Cluster ; ;; Sa -------+---------------+---------------+---------------+------- ; | | | | ; | MPR_A | | ; | .----+----. | | ; | 1| 1| 1| | ; BrA ALPHA BETA DELTA BrB ; | 2| 2| 2| | ; | ‘----+----’ | | ; | LNI_A | | ; | | | | ; Sb -------+---------------+---------------+---------------+------- ; ;; Edit 3. ; ; Label ; ----- Node ------ Description ----------------------------------------------- SYSTEM A, LAN_ADP A1, LAN_ADP A2, ALPHA, , , < - MicroVAX II; In the Computer room> . . . , . . . , . . . SYSTEM B, LAN_ADP B1, LAN_ADP B2, BETA, , , < - MicroVAX 3500; In the Computer room> . . . , . . . , . . . (continued on next page) Sample Programs for LAN Control D–7
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:
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:
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 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
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 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
5 Preparing a Shared Environment In
Page 85 and 86:
Preparing a Shared Environment 5.2
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Table 5-2 Alias Collisions and Outc
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Table 5-3 (Cont.) Security Files Fi
Page 103 and 104:
Table 5-3 (Cont.) Security Files Fi
Page 105 and 106:
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 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
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:
Page 147 and 148:
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: Cluster System Parameters A.1 Value
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 269 and 270: Cluster Troubleshooting C.3 Satelli
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 285 and 286: Table C-5 Informational and Other E
Page 287 and 288: Entry Description Cluster Troublesh
Page 293 and 294: Table C-6 (Cont.) Port Messages for
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: Sample Programs for LAN Control D.5
Page 309 and 310: Location Action Sample Programs for
Page 311: Sample Programs for LAN Control D.5
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 356 and 357:
Troubleshooting the NISCA Protocol
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?