OpenVMS Cluster Systems - OpenVMS Systems - HP

Booting
See also Satellites nodes, booting
avoiding system disk rebuilds, 9–14
computer on CI fails to boot, C–3
computer on CI fails to join cluster, C–13
minimizing boot time, 9–3
nodes into existing OpenVMS Cluster, 8–35,
8–41
sequence of events, C–1
Boot nodes
See Boot servers
Boot servers
after configuration change, 8–33
defining maximum DECnet address value, 4–7
functions, 3–5
rebooting a satellite, 8–39
Broadcast messages, 10–9
Buffer descriptor table entries, 9–18
BYE datagram, F–23
C
Cables
configurations, C–21
troubleshooting CI problems, C–21
CC protocol
CC header, F–22
part of NISCA transport protocol, F–3
setting the TR/CC flag, F–23
CCSTART datagram, F–16, F–23
Channel Control protocol
See CC protocol
Channel formation
acknowledging with VERF datagram, F–16,
F–23
BYE datagram, F–23
completing with VACK datagram, F–16, F–23
handshake, F–16
HELLO datagrams, F–16, F–23
multiple, F–19
opening with CCSTART datagram, F–16
problems, F–16
Channels
definition, F–4
established and implemented by PEDRIVER,
F–4
CHECK_CLUSTER system parameter, A–1
CI (computer interconnect), 2–2
cable repair, C–23
changing to mixed interconnect, 8–21
communication path, C–18
computers
adding, 8–10
failure to boot, C–3
failure to join the cluster, C–13
configurations, 3–2
device-attention entry, C–26
Index–2
CI (computer interconnect) (cont’d)
error-log entry, C–31
analyzing, C–24
formats, C–25
error recovery, C–27, C–40
logged-message entry, C–29
MSCP server access to shadow sets, 6–29
port
loopback datagram facility, C–20
polling, C–17
verifying function, C–19
troubleshooting, C–1
CISCEs
See Star couplers
CLUEXIT bugcheck
diagnosing, C–16
Cluster
See OpenVMS Cluster systems
Cluster aliases
definition, 4–14, 4–15
enabling operations, 4–16
limits, 9–20
Cluster authorization file
See CLUSTER_AUTHORIZE.DAT files
Cluster group numbers
in DX header, F–22
location of, F–28
on extended LANs, 2–11, 3–4, 10–14
setting, 2–12, 4–4, 10–15
Cluster passwords, 2–11, 2–12, 4–4, F–16, F–23
See also Security management
error example, 2–12
location of, F–28
multiple LAN configurations, 3–4
on extended LANs, 2–11, 10–14
requested by CLUSTER_CONFIG.COM
procedure, 8–7
setting, 4–4, 10–15
Clusterwide logical names
database, 5–12
defining, 5–12
in applications, 5–11
system management, 5–6
Clusterwide process services, 1–9
CLUSTER_AUTHORIZE.DAT files, 2–12, F–28
See also Authorize utility (AUTHORIZE),
Cluster group numbers, Cluster passwords,
and Security management
enabling LAN for cluster communications,
8–20
ensuring cluster integrity, 10–14
multiple, 10–15
troubleshooting MOP servers, C–9
updating, 10–15
verifying presence of OpenVMS Cluster
software, C–13