OpenVMS Cluster Systems - OpenVMS Systems - HP
OpenVMS Cluster Systems - OpenVMS Systems - HP
OpenVMS Cluster Systems - OpenVMS Systems - HP
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
LANs (local area networks) (cont’d)<br />
troubleshooting NISCA communications, F–16<br />
LAN Traffic Monitor<br />
See LTM<br />
LAVC$FAILURE_ANALYSIS.MAR program, F–30<br />
to F–34<br />
distributed enable filter, F–31<br />
distributed enable messages, F–32<br />
distributed trigger filter, F–32<br />
distributed trigger messages, F–33<br />
filtering LAN packets, F–31<br />
filtering LAN retransmissions, F–31<br />
filters, F–30<br />
partner program, F–34<br />
retransmission errors, F–33<br />
sample program, D–3<br />
scribe program, F–34<br />
starter program, F–33<br />
LAVC$START_BUS.MAR sample program, D–1<br />
LAVC$STOP_BUS.MAR sample program, D–2<br />
%LAVC-I-ASUSPECT OPCOM message, D–10<br />
LAVc protocol<br />
See NISCA transport protocol<br />
See PEdriver<br />
%LAVC-S-WORKING OPCOM message, D–10<br />
%LAVC-W-PSUSPECT OPCOM message, D–10<br />
LAVc_all filter<br />
<strong>HP</strong> 4972 LAN Protocol Analyzer, F–31<br />
LAVc_TR_ReXMT filter<br />
<strong>HP</strong> 4972 LAN Protocol Analyzer, F–31<br />
Layered products<br />
installing, 4–6<br />
License database, 4–6<br />
Licenses<br />
DECnet, 4–5<br />
installing, 4–5<br />
<strong>OpenVMS</strong> <strong>Cluster</strong> systems, 4–5<br />
<strong>OpenVMS</strong> operating system, 4–5<br />
LMF (License Management Facility), 1–9<br />
Load balancing<br />
determining failover target, 6–5<br />
devices served by MSCP, 6–22<br />
MSCP I/O, 6–22<br />
dynamic, 6–22, 6–23<br />
static, 6–22, 6–23<br />
queue database files, 7–4<br />
queues, 5–1, 7–1<br />
Load capacity ratings, 6–23<br />
Load file<br />
satellite booting, 9–5<br />
Local area networks<br />
See LANs<br />
Local area <strong>OpenVMS</strong> <strong>Cluster</strong> environments<br />
capturing distributed trigger event, F–32<br />
debugging satellite booting, C–1, C–5<br />
network failure analysis, C–24<br />
Index–8<br />
Lock database, 2–9<br />
LOCKDIRWT system parameter, A–2<br />
used to control lock resource trees, 2–14<br />
Lock manager<br />
See Distributed lock manager<br />
Logical names<br />
clusterwide<br />
in applications, 5–11<br />
invalid, 5–10<br />
system management, 5–6<br />
defining<br />
for QMAN$MASTER.DAT, 5–23<br />
system, 5–5<br />
LOGINOUT<br />
determining process quota values, 10–17<br />
Logins<br />
controlling, 5–22<br />
disabling, 4–7<br />
LRPSIZE system parameter, 10–16, A–2<br />
LTM (LAN Traffic Monitor), 10–23<br />
M<br />
Macros<br />
NISCA, F–19<br />
Maintenance Operations Protocol<br />
See MOP servers<br />
MASSBUS disks<br />
dual-ported, 6–2<br />
Mass storage control protocol servers<br />
See MSCP servers<br />
MCDRIVER, 2–2<br />
Members<br />
definition, 1–3<br />
managing<br />
cluster group numbers, 2–11<br />
cluster passwords, 2–11<br />
cluster security, 5–16<br />
state transitions, 1–4<br />
shadow set, 6–27<br />
MEMORY CHANNEL, 2–2<br />
configurations, 3–10<br />
system parameters, A–2<br />
Messages<br />
acknowledgment, F–24<br />
distributed enable, F–32<br />
distributed trigger, F–33<br />
OPCOM, D–10<br />
Mirroring<br />
See Volume shadowing and Shadow sets<br />
MKDRIVER, 2–2<br />
MODPARAMS.DAT file<br />
adding a node or a satellite, 8–11<br />
adjusting maximum packet size, 10–17<br />
cloning system disks, 9–16<br />
created by CLUSTER_CONFIG.COM procedure,<br />
8–1