02.12.2012 Views

OpenVMS Cluster Systems - OpenVMS Systems - HP

OpenVMS Cluster Systems - OpenVMS Systems - HP

OpenVMS Cluster Systems - OpenVMS Systems - HP

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

NISCA transport protocol (cont’d)<br />

CC protocol, F–3<br />

channel formation problems, F–16<br />

channel selection and congestion control<br />

appendix, G–1<br />

datagram flags, F–24<br />

datagrams, F–19<br />

definition, F–1<br />

diagnosing with a LAN analyzer, F–19<br />

DX header, F–21<br />

DX protocol, F–3<br />

Equivalent Channel Set, G–1<br />

function, F–3<br />

LAN Ethernet header, F–20<br />

LAN FDDI header, F–20<br />

load distribution, G–1<br />

packet format, F–19<br />

packet loss, F–12<br />

PEDRIVER implementation, F–4<br />

PI protocol, F–3<br />

PPC protocol, F–3<br />

PPD protocol, F–3<br />

retransmission problems, F–17<br />

TR header, F–23<br />

troubleshooting, F–1<br />

TR protocol, F–3<br />

NISCA Transport Protocol<br />

channel selection, G–1<br />

congestion control, G–3<br />

preferred channel, G–2<br />

NISCS_CONV_BOOT system parameter, 8–10,<br />

A–6, C–5<br />

NISCS_LAN_OVRHD system parameter, A–7<br />

NISCS_LOAD_PEA0 system parameter, 4–4, A–7,<br />

C–13<br />

caution when setting to 1, 8–20, A–7<br />

NISCS_MAX_PKTSZ system parameter, 10–16,<br />

A–7<br />

NISCS_PORT_SERV system parameter, A–8<br />

Node allocation classes<br />

See Allocation classes<br />

O<br />

OPCOM (Operator Communication Manager),<br />

10–9, D–10<br />

<strong>OpenVMS</strong> Alpha systems<br />

RAID device-naming problems, 6–13<br />

<strong>OpenVMS</strong> <strong>Cluster</strong> sample programs, D–1<br />

LAVC$FAILURE_ANALYSIS.MAR, D–3<br />

LAVC$START_BUS.MAR, D–1<br />

LAVC$STOP_BUS.MAR, D–2<br />

<strong>OpenVMS</strong> <strong>Cluster</strong> systems<br />

adding a computer, 8–10, 8–33, 8–41<br />

adjusting EXPECTED_VOTES, 8–35<br />

architecture, 2–1<br />

benefits, 1–2<br />

clusterwide logical names, 5–6, 5–11<br />

Index–10<br />

<strong>OpenVMS</strong> <strong>Cluster</strong> systems (cont’d)<br />

common environment, 5–2<br />

startup command procedures, 5–14<br />

common SYSUAF.DAT file, 10–17<br />

configurations, 3–1, 9–1<br />

keeping records, 10–3<br />

preconfiguration tasks, 8–3<br />

procedures, 8–1, 8–4<br />

disaster tolerant, 1–1<br />

distributed file system, 1–4, 2–15<br />

distributed processing, 5–1, 7–1<br />

hang condition, C–15<br />

interprocessor communications, 6–29<br />

local resources, 5–2<br />

maintenance, 10–1<br />

members, 1–3<br />

mixed-architecture<br />

booting, 4–1, 10–5, 10–8<br />

system disks, 3–5, 10–8<br />

multiple environments, 5–2, 5–3<br />

functions that must remain specific, 5–14<br />

startup functions, 5–15<br />

operating environments, 5–2<br />

preparing, 4–1<br />

partitioning, 2–5, C–17<br />

reconfiguring a cluster, 8–33<br />

recovering from startup procedure failure,<br />

C–14<br />

removing a computer, 8–33<br />

adjusting EXPECTED_VOTES, 8–35<br />

security management, 5–16, 10–14<br />

single security domain, 5–16<br />

system applications, 1–5<br />

System Communications Services (SCS), 1–4<br />

system management overview, 1–7<br />

system parameters, A–1<br />

tools and utilities, 1–7, 1–11<br />

troubleshooting, C–1<br />

voting member, 2–6<br />

adding, 8–33<br />

removing, 8–33<br />

<strong>OpenVMS</strong> Management Station, 1–10<br />

Operating systems<br />

coordinating files, 5–22<br />

installing, 4–1<br />

on common system disk, 5–4<br />

upgrading, 4–1<br />

Operator Communications Manager<br />

See OPCOM<br />

P<br />

Packet loss<br />

caused by network congestion, F–12, G–3<br />

caused by too many HELLO datagrams, G–5<br />

NISCA retransmissions, F–12

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!