3 If Compaq Insight Manager is loaded and configured, use it to check the
operation statistics and possible error messages for the cluster
interconnect adapter installed in each cluster node.
When Using an Ethernet-based Cluster
Interconnect
3 Make sure that the cluster interconnect and the client LAN are on
different Ethernet switches.
3 Make sure that all non-Oracle Ethernet traffic is using the client LAN,
not the cluster interconnect.
When Using a ServerNet-based Cluster
Interconnect
3 Use the viping utility to verify all nodes can communicate with each
other over the ServerNet cluster interconnect. For information about
viping options and error diagnostics, see Appendix A, "viping Utility."
Compaq Confidential Need to Know Required
Writer: Bob Schiermann Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: h-ch7 Troubleshooting.doc Last Saved On: 6/2/99 9:14 AM
Troubleshooting 7-9
Viping Does Not Complete Successfully
Sometimes, when using viping to ping the node name (machine host name),
the viping utility is not successful in communicating with the node specified.
Before concluding that cluster nodes cannot communicate through a ServerNet
cluster interconnect, try pinging the ServerNet ID of the node in question.
Get the ServerNet ID of a node by entering a viping command from that node
using the local node name as the operand for viping. For example, if the
machine host name of a node is node1, enter viping node1 to get the
ServerNet ID of node1.
If on node1 the command viping node2 does not return successfully:
1. Get the ServerNet ID of node2 by entering viping node2 at node2. The
viping utility responds in the following way. (0xF0040 is an example of
a ServerNet ID.)
Pinging node2 [0xF0040] with 12 bytes of data:
Reply from 0xF0040: bytes = 12 time = 12ms
2. Test node1 to node2 ServerNet connectivity using the ServerNet ID by
entering viping 0xF0040 at node1. The viping utility responds in the
following way.
Pinging 0xF0040 with 12 bytes of data:
Reply from 0xF0040: bytes = 12 time = 12ms
If the viping utility does not complete successfully using either the ServerNet
ID or node name, check the hardware connections. If the hardware
connections are correct, you might need to uninstall and reinstall the ServerNet
OSDs. See Chapter 6, "Cluster Management."
For information about viping options and error diagnostics, see Appendix A,
"viping Utility."
Compaq Confidential Need to Know Required
Writer: Bob Schiermann Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: h-ch7 Troubleshooting.doc Last Saved On: 6/2/99 9:14 AM
7-10 Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i Release 8.1.5 Administrator Guide
Unable to Ping the Cluster Interconnect
or the Client LAN
3 If you are using the recommended method of using static IP addresses,
ensure that the hosts file and lmhosts files are properly set up.
When Using an Ethernet-based Cluster
Interconnect
3 Make sure that the Ethernet cables are properly connected and the
Ethernet switch or hub is powered on. In a redundant cluster
interconnect configuration, two Ethernet switches are used. Validate that
all cluster interconnect adapters used as the primary interconnect path
are connected to the same switch and that all adapters used as the
redundant cluster interconnect path are connected to the redundant
switch.
3 Make sure that the Ethernet drivers are properly installed and configured
on the cluster nodes. Verify the Ethernet drivers for the cluster
interconnect adapters are the same revision level on all cluster nodes.
3 If you are directly connecting a two node cluster with an Ethernet
crossover cable, make sure the cable is connected to the cluster
interconnect adapters, not the client LAN adapters.
When Using a ServerNet-based Cluster
Interconnect
3 Make sure that the ServerNet cables are properly connected and the
ServerNet switch is powered on. In a redundant cluster interconnect
configuration, two ServerNet switches are used to create an X-path and
a Y-path for cluster interconnect communication. All of the ServerNet
cables connected to the X-port on the ServerNet adapter must be
connected to the same X-path ServerNet switch. Likewise, all ServerNet
cables connected to the Y-port on the ServerNet adapter must be
connected to the same Y-path ServerNet switch.
3 Make sure that the ServerNet drivers are properly installed and
configured on the cluster nodes. Verify the ServerNet drivers for the
cluster interconnect adapters are the same revision level on all cluster
nodes.
Compaq Confidential Need to Know Required
Writer: Bob Schiermann Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: h-ch7 Troubleshooting.doc Last Saved On: 6/2/99 9:14 AM
Troubleshooting 7-11
Node or Nodes Unable to Rejoin the Cluster
3 Use ping to ensure that the rejoined node or nodes can communicate
with other nodes in the cluster.
3 Make sure the OSDs have been properly installed on the affected
node(s) by running the Oracle Universal Installer on the cluster's
primary node. Click Installed Products and verify an entry for the OSDs
exists.
3 Make sure the OracleCMService, the OracleNMService, and all other
necessary Oracle services have started without error. Run the Services
applet in the Windows NT Control Panel and check to see if the services
have started. Run the Windows NT Event Log and check for error
messages about the Oracle services.
3 Verify that the node has access to the shared storage. Run Windows NT
Disk Administrator and make sure all the shared disk resources appear
as expected.
Ping Shows the Cluster
Interconnect IP Address Instead of Client LAN IP
Address
3 This issue is commonly caused by a problem in Windows NT. Windows
NT Service Pack 4 provides a fix.
3 Refer to the Compaq white paper, Supported Ethernet Interconnect for
Compaq Database Clusters using Oracle Parallel Server (Doc #
ECG062/0299) for additional information.
3 If you do not have Windows NT Service Pack 4 installed, the following
suggestions may alleviate the issue:
Y Due to the complexity of Windows NT Server and multiple-NIC
servers under Windows NT Server, the manner by which you assign
a cluster interconnect or client LAN to a specific network card might
not occur as you expected. Use the ping utility to verify IP and
computer name addresses. You may have to accept the address that
Windows NT Server has assigned to a given NIC port or subport.
Y Check the %SystemRoot%\system32\drivers\etc\hosts file to verify
that the cluster interconnect IP address and computer names are
correctly associated and that the client LAN IP addresses and
computer names are correctly associated. Perform ping testing as
described in "Verifying Cluster Communications" in Chapter 5,
"Installation and Configuration."
Compaq Confidential Need to Know Required
Writer: Bob Schiermann Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: h-ch7 Troubleshooting.doc Last Saved On: 6/2/99 9:14 AM
7-12 Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i Release 8.1.5 Administrator Guide
Troubleshooting Client-to-Cluster
Connectivity Problems
A Network Client Cannot Communicate with
the Cluster
3 Verify the user ID has sufficient rights to perform the desired action.
3 Make sure proper network connectivity exists by verifying that the
connections from the network client to the cluster are cabled correctly.
Additionally, verify that the network routers/switches/hubs used in the
client LAN are powered on and properly cabled.
3 Make sure that pinging an IP address over the client LAN from a client
to the cluster issues a correct reply. Perform ping testing as described in
"Verifying Cluster Communications" in Chapter 5, "Installation and
Configuration."
3 Make sure that the TNSNames.ora file is properly configured on client
and cluster nodes as defined by the Oracle Net8 Config Assistant utility.
3 Make sure that the Oracle TNSListener is running on the cluster nodes.
Run the Service applet in the Windows NT Control Panel to verify that
it is started.
3 Make sure that the Oracle Listener files are set up on the cluster nodes
by using the Oracle TNSPing utility.
Compaq Confidential Need to Know Required
Writer: Bob Schiermann Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: h-ch7 Troubleshooting.doc Last Saved On: 6/2/99 9:14 AM
Troubleshooting 7-13
Troubleshooting Shared Storage
Problems
This section addresses potential problems arising from the use of the RA4000
External Storage Subsystem as a shared storage subsystem. This section does
not address RA4000 Array problems that are specific to the storage subsystem
itself or to the use of the storage subsystem in a standalone server
configuration. For those issues, refer to the Compaq StorageWorks RAID
Array 4000 User Guide.
Node Cannot Connect to the Shared Drives
3 Verify that a physical connection exists from each node to the Storage
Hub.
Y Verify the shortwave Gigabit Interface Converters (GBICs) are
properly seated.
Y Verify that all Fibre Channel cables are properly connected to their
GBICs.
3 Verify all nodes can access the shared storage. On each node, start Disk
Administrator to verify that the same shared disk resources are seen
from every node in the cluster.
3 The storage subsystem components must be powered on before the
servers. If any cluster node was powered on before either the Storage
Hub or the RA4000 Array, shut down the node then restart.
Compaq Confidential Need to Know Required
Writer: Bob Schiermann Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: h-ch7 Troubleshooting.doc Last Saved On: 6/2/99 9:14 AM
7-14 Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i Release 8.1.5 Administrator Guide
Drives in the RA4000 Array Are Not Recognized
3 Restart the affected node or nodes.
3 Make sure the Compaq StorageWorks Fibre Channel Host Adapter
(Fibre Host Adapter) driver for Windows NT Server is installed and
running on all cluster nodes. If it is not installed, refer to the Compaq
StorageWorks Fibre Channel Host Adapter Installation Guide for
detailed information about installing it.
3 If the drives are still not recognized, it is recommended that you start
investigating the problem from the lowest level of drive configuration.
Y Run the Compaq Array Configuration Utility. You can run this
utility online if at least one logical drive is configured and
recognized. The Array Configuration Utility is used to see if any of
the drive arrays are offline (degraded or failed).
Y The online utility is installed as part of the Compaq Support
Software Diskette (SSD) for Windows NT Server. If you need to run
this utility offline, shut down the servers and restart with either the
SmartStart CD in the CD slot, or with diskette number 1 of the Array
Configuration Utility in the A: drive.
3 If all drives are not recognized by the Array Configuration Utility, it is
probably a physical connection problem.
Y Verify that the lights on the Fibre Host Adapter, Storage Hub, and
RA4000 Array Controller are all green.
Y Verify the shortwave Gigabit Interface Converters (GBICs) are
properly seated in the Fibre Host Adapters, the RA4000 Array
Controller, and the Storage Hub.
Y Verify that all Fibre Channel cables are properly connected to their
shortwave GBICs. For details on how to connect the GBICs and the
Fibre Channel cables, refer to the Compaq StorageWorks RAID
Array 4000 User Guide.
3 If all drives are recognized by the Array Configuration Utility and are
configured correctly, start Windows NT Server and run Disk
Administrator. Verify that all drive volumes appear in Disk
Administrator.
3 If you continue to have problems, refer to the Compaq Fibre Channel
Troubleshooting Guide for further corrective actions.
Compaq Confidential Need to Know Required
Writer: Bob Schiermann Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: h-ch7 Troubleshooting.doc Last Saved On: 6/2/99 9:14 AM
Troubleshooting 7-15
Troubleshooting Other Potential Problems
NT Blue Screen With AFD.SYS Failure Displayed
This blue screen can occur as a result of a significant amount of traffic going
over the Microsoft Windows NT NDIS driver.
3 Restart the node.
3 If the problem persists, contact Microsoft and request the AFD.SYS
hotfix.
Compaq Confidential Need to Know Required
Writer: Bob Schiermann Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: h-ch7 Troubleshooting.doc Last Saved On: 6/2/99 9:14 AM
A
Appendix
viping Utility
The viping utility verifies that cluster nodes can communicate with each other
using the ServerNet cluster interconnect. The following shows the syntax and
option summary of the viping command.
Syntax and Option Summary
viping < node |snid > [-t] [-b size] [-v] [-?]
Node name or ServerNet ID. The node name is the machine
host name, or local node name. 0xF0040 is an example of a
ServerNet ID. A node can determine its own ServerNet ID
by using its machine host name as the operand for viping.
-t Retry the viping command until interrupted. This option is
useful if, for example, you are changing ServerNet cabling
and you want viping to continue trying to establish
communication while making cable changes.
-b size Size of the viping buffer. The default size is 12 bytes. The
maximum size is 256K bytes, which is useful when
diagnosing problems with large data transfers.
-v Enable verbose logging output. This option provides
extended tracing information, which can be useful in
debugging situations.
-? Display viping command syntax and option summary.
Compaq Confidential Need to Know Required
Writer: Linda Waterhouse Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: i-apa viping utility.doc Last Saved On: 5/7/99 9:17 AM
A-2 Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i Release 8.1.5 Administrator Guide
Example
To test ServerNet connectivity from one node to another in which the machine
host names are node1 and node2, enter the following command at node1:
C\: viping node2
If successful, viping returns the following sample output. (0xF0040 is an
example of a ServerNet ID.)
Pinging node2 [0xF0040] with 12 bytes of data:
Reply from 0xF0040: bytes = 12 time = 12ms
Error Diagnostics
The following table shows the errors viping can produce, possible causes, and
what action to take to correct the problem.
Table A-1
viping Errors
Error Possible Cause/Corrective Action
Generic system resource error. The system might be running low on memory or
system resources. Try the operation again. If the
problem persists, restart the system.
Generic vi internal error. Check ServerNet hardware connections. If the
problem persists, restart the system or uninstall
and reinstall ServerNet OSDs.
Data integrity check failed. Potential data corruption has been detected. Check
ServerNet hardware connections. If the problem
persists, restart the system or uninstall and
reinstall ServerNet OSDs.
continued
Compaq Confidential Need to Know Required
Writer: Linda Waterhouse Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: i-apa viping utility.doc Last Saved On: 5/7/99 9:17 AM
viping Utility A-3
Table A-1
viping Errors continued
Error Possible Cause/Corrective Action
Connection to remote node timed A communications error with a remote node has
out. occurred. Check ServerNet hardware connections
and verify the ServerNet ID for the remote node. If
the problem persists, restart the system or
uninstall and reinstall ServerNet OSDs.
Request timed out. A communications error with a remote node has
occurred. Check ServerNet hardware connections.
If the problem persists, restart the system or
uninstall and reinstall ServerNet OSDs.
Unrecognized parameter -a. The format of viping does not conform to normal
usage. Correct the command syntax and try again.
Multiple node names defined node More than one node name has been specified.
and node. Correct the command syntax and try again.
Unable to determine SNID for viping could not communicate with the remote
remote node node. node using the node name. Try again using the
ServerNet ID as the operand for viping.
Compaq Confidential Need to Know Required
Writer: Linda Waterhouse Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: i-apa viping utility.doc Last Saved On: 5/7/99 9:17 AM
Glossary
A measure of how well a computer system can deliver services to its
Availability
clients continuously. Availability is typically expressed as a
percentage, with 100% being the best possible rating.
A local area network dedicated to servicing requests between
Client LAN
network client machines and between the cluster nodes and the
client machines. This is different than a cluster interconnect, which
is dedicated to servicing information requests to and from only
cluster nodes.
An integration of software and hardware technologies that enables a
Cluster
set of loosely-coupled servers and storage to present a single
system image to clients and to operate as a single system.
Clustering is a way to improve availability and scalability.
The period of time that a computer system is unable to service
Downtime
clients' requests.
A standard network protocol that operates mostly on a physical
Ethernet
level, using network interface cards and cabling to transmit data
between computers. Transfer rates are normally 10 or 100 megabits
per second.
Compaq Confidential Need to Know Required
Writer: Ron Reisdorf Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle 8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: j-Glossary.doc Last Saved On: 6/2/99 9:21 AM
2 Compaq Parallel Database Cluster Model PDC/O1000 for Oracle 8i Release 8.1.5 Administrator Guide
A characteristic that allows continued operation of a computer entity
Fault tolerance
when a fault (or failure) is encountered. Fault tolerance applies to a
computer component, an individual computer, or a cluster of
computers, primarily through designing redundant elements into the
entity.
An IEEE standard for providing high-speed data transfer among
Fibre channel
workstations, mainframes, supercomputers, desktop computers,
storage devices, and display devices.
Heartbeat A signal transmitted between cluster nodes to indicate whether the
nodes are operating.
High availability A term used to identify a computer system that can continuously
deliver services to its clients 99.9% of the time (no more than 8.5
hours of downtime per year).
Hot pluggable A computer component that can be removed and replaced without
powering down the system.
Hot spare A computer component that is powered on, not actively processing
data, and awaiting a request to take over operation of a failed
component.
Interconnect A physical connection between cluster nodes that transmits intra-
cluster communication, e.g. the cluster heartbeat. The Compaq
Parallel Database Cluster interconnect is dedicated to servicing
requests only between cluster nodes.
Integrated An Oracle software component that coordinates database locks
Distributed Lock among cluster nodes. Sometimes abbreviated as IDLM.
Manager
IP Address Internet Protocol Address. An address assigned to a network
interface card, which computer entities use to locate and
communicate with each other. IP addresses can be statically or
dynamically assigned.
LAN Local Area Network.
Load balancing To balance the amount of work (processing) undertaken by each
node in a cluster.
Compaq Confidential Need to Know Required
Writer: Ron Reisdorf Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle 8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: j-Glossary.doc Last Saved On: 6/2/99 9:21 AM
Glossary 3
Multiple Fibre The installation of additional RA4000 External Storage Subsystem
Channel loops components to the server nodes in a PDC/O1000 cluster for the
purpose of increasing the amount of shared storage space available
to the cluster nodes and to increase the cluster's I/O performance.
NIC Network Interface Controller. A board that allows a computer to be
connected with a network, and works with the network operating
system to control the flow of information over the network.
Node An individual server in a cluster.
NTFS NT File System. A file organization system by which data is stored
and accessed in a Windows NT operating system.
Operating A collection of low-level software modules that monitor critical
System clustering hardware components and constantly transmits/receives
Dependent (OSD)
cluster state information to/from Oracle Parallel Server.
layer
Oracle8i Parallel A software component that ships as an option of Oracle8i Enterprise
Server (OPS) Edition. The component is responsible for enabling parallel database
support. An additional license is required for OPS.
Oracle Universal An installation application used to install and de-install both Oracle
Installer software and the hardware vendor's Operating System Dependent
modules.
POST Power-On Self-Test. A set of operations executed every time a
system is turned on to verify that components are present and
operating.
Raw Partition A disk partition that does not contain file system formatting
information. An unformatted partition. Oracle Parallel Server requires
its database files to be stored on raw partitions.
RAID Redundant Array of Inexpensive Disks. A method of using hard disk
drives in an array to provide data redundancy to increase system
reliability and performance.
Reliability The continuous integrity of a system (server, storage, network, or
cluster).
Compaq Confidential Need to Know Required
Writer: Ron Reisdorf Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle 8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: j-Glossary.doc Last Saved On: 6/2/99 9:21 AM
4 Compaq Parallel Database Cluster Model PDC/O1000 for Oracle 8i Release 8.1.5 Administrator Guide
Resource A software or hardware entity upon which a client/server application
or service is dependent. As it pertains to the Compaq Parallel
Database Cluster, a cluster resource must have the ability to be
managed by the cluster and must reside on one of the cluster
nodes.
Scalability The ability of a system (server, storage, network, or cluster) to grow
or expand in performance, throughput, or capacity.
ServerNet A communication architecture used for high-speed, low-latency
transmission of data. In a Compaq Parallel Database Cluster,
ServerNet can be implemented as the cluster interconnect;
consisting of ServerNet adapters, switches, cables, and software
drivers.
Service A data set or operation set exported by application servers to their
clients.
Within the Windows NT operating system, a Service is server
process that performs a specific system function. It frequently
enables an application programming interface with which it interacts
with other processes.
Shared resource A type of cluster organization in which some resources are
accessible to all systems in the cluster.
Shared storage A storage system that can be accessed by multiple cluster nodes.
Storage array A storage cabinet used to hold physical disk drives. The Compaq
RA4000 Array is an example of a storage array.
Storage system A complete storage subsystem, including array controller(s), storage
array(s), and physical disk(s).
System A complete computer system capable of operating independently. A
system can be either a single processor system or an SMP system.
Example: a server.
UPS Uninterruptible power supply.
Compaq Confidential Need to Know Required
Writer: Ron Reisdorf Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle 8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: j-Glossary.doc Last Saved On: 6/2/99 9:21 AM
Index
cluster
adding a node 6-10
A
defined 1-2
administrator privileges 5-21 managing degradation in 6-3
Automatic Server Recovery 5-3 monitoring performance 6-22
availability replacing a node 6-10
defined 1-3 cluster communications
ServerNet cluster
interconnect 5-42
C
verifying 5-20
cabling cluster configuration planning
client LAN 5-11 large PDC/O1000 cluster 4-8
cluster interconnect 5-6 midsize PDC/O1000
Ethernet cluster cluster 4-7
interconnect 5-7 cluster connectivity
Ethernet crossover cables 5-7 troubleshooting 7-10
Ethernet hubs 5-7 cluster interconnect
Ethernet switches 5-7 cabling 5-6
ServerNet cluster defined 2-14
interconnect 5-9 Ethernet cluster
ServerNet Switches 5-9 interconnect 2-15
capacity planning 4-2 options 2-14
cluster interconnect and client ServerNet cluster
LAN components 4-5 interconnect 2-21
Compaq ProLiant servers 4-2 cluster interconnect adapters
reference material 4-6 installation 5-4
shared storage cluster node
components 4-3 adding 6-10
client LAN connectivity failure 7-13
adapters installation 5-4 replacing 6-10
cabling 5-11 shutting down 6-2
redundant 5-11 unable to join cluster 7-11
Compaq Confidential Need to Know Required
Writer: John Blackburn Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle 8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: k-index.doc Last Saved On: 5/18/99 4:18 PM
2 Compaq Parallel Database Cluster Model PDC/O1000 for Oracle 8i Release 8.1.5 Administrator Guide
configuration
cluster nodes
Oracle 5-43
supported servers 2-2
cluster software
overview 3-1 D
clusters
Disk Administrator 5-18
overview 1-1
disk drives
Compaq Array Configuration
adding to increase
Utility 5-6, 5-14, 5-15
capacity 6-19
Compaq authorized reseller xvii
non-shared 4-14
Compaq Full Spectrum Fault
planning 4-14
Management 3-4
replacing a failed disk 6-18
Compaq Insight Manager
shared 4-15
description 3-3
distributed lock manager 2-14
for RA4000 External Storage
downtime 1-3
Subsystem 2-13
Compaq Operating System
Dependent Modules 3-4 E
Compaq Options ROMPaq 3-4
Ethernet adapters
Compaq SmartStart and Support
installation 5-4
software 3-2
Ethernet cluster interconnect 2-15
Compaq software
adapter installation 5-4
Array Configuration
adapters 2-17
Utility 6-4, 7-14
cabling 5-7
Compaq Insight Manager 3-3,
Ethernet switch 2-17
6-4
lmhosts and hosts files entries
Compaq Operating System
for 5-14
Dependent Modules 3-4
non-redundant Ethernet cluster
Compaq Options
interconnect 2-15
ROMPaq 3-4
redundant 5-8
Compaq SmartStart and
redundant Ethernet cluster
Support software 3-2
interconnect 2-16
Compaq Support Software
Ethernet crossover cables
Diskette for Windows
cabling 5-7
NT 3-3
Ethernet hubs 5-7
Compaq System Configuration
cabling 5-7
Utility 3-3
Ethernet OSDs
summary of 3-2
installation 5-22
Compaq Storage Hub
Ethernet switches 5-7
data paths 2-11
cabling 5-7
overview 2-9
power sequencing 5-13
Compaq Support Software Diskette
for Windows NT 3-3
Compaq System Configuration
Utility 3-3
Compaq website xvi
Compaq Confidential Need to Know Required
Writer: John Blackburn Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle 8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: k-index.doc Last Saved On: 5/18/99 4:18 PM
Index 3
hardware 5-3
F
operating system
Fibre Channel software 5-14
distances 2-6 Oracle 5-42
Fibre Channel cable overview 5-2
maximum distances 2-6 RA4000 Arrays 5-5
Fibre Channel data paths ServerNet OSDs 5-31
Fibre Host Adapter to Storage servers 5-3
Hub 2-12 SmartStart 5-15
overview 2-11 SNMP agents 5-16, 5-19
Storage Hub to RA4000 troubleshooting 7-5
Array 2-13 Windows NT Server 5-16
Fibre Host Adapters Integrate Management Display 3-3
installation 5-3 Integrated Management Log 3-3
overview 2-11 interconnect
firmware revisions 7-4 network protocol 5-14
redundancy 7-10
troubleshooting 7-8
G
getting help xvi
L
lmhosts file 4-15, 5-15
H
local area network (LAN) 2-24
hardware
installation 5-3
M
installation verification 5-45
help managing
additional sources xvi cluster database software 6-5
Compaq website xvi Microsoft software
Compq authorized resellers, Microsoft Windows NT Server
telephone numbers xvi 4.0 3-2
technical support telephone multiple Fibre Channel loops 2-6
numbers xvi
hosts file 4-15, 5-15
N
net use command 5-21
I
network planning 4-15
icons network protocols
symbols on equipment xv TCP/IP 5-14
IMD See Integrated Management nodes
Display installation 5-3
installation non-shared disk drives 4-14
cluster interconnect
adapters 5-4
Ethernet OSDs 5-22
Fibre Host Adapters 5-3
Compaq Confidential Need to Know Required
Writer: John Blackburn Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle 8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: k-index.doc Last Saved On: 5/18/99 4:18 PM
4 Compaq Parallel Database Cluster Model PDC/O1000 for Oracle 8i Release 8.1.5 Administrator Guide
overview
O
Compaq Parallel Database
operating system dependent Cluster 1-4
modules (OSDs)
deinstalling 6-6
P
installation 5-18
installation verification 5-45 PDUs 5-12
operating system software ping utility 5-21
description 3-2 planning
installation 5-14 disk drives 4-14
OPS_CMDISK files 5-43 grouping physical disk storage
Oracle space 4-13
configuration 5-43 networks 4-15
installation 5-42 power distribution 5-12
Oracle certification 3-7 RA4000 Arrays 5-13
Oracle CM Service 5-31, 5-41 servers 5-12
Oracle software power distribution units 5-12
client reconnect software 3-6 power sequencing 5-13
configuring 5-43 ProLiant servers
installation availability features 2-3
troubleshooting 7-5 overview 2-2
Oracle certification 3-7
Oracle Enterprise
R
Manager 6-5
Oracle Universal Installer 7-5 RA4000 Array
Oracle8i Enterprise Manager adding 6-20
Release 8.1.5 3-6 availability features 2-5
Oracle8i Parallel Server Option installation 5-5
Release 8.1.5 3-5 overview 2-8
Oracle8i Server Enterprise power distribution 5-13
Edition Release 8.1.5 3-5 power sequencing 5-13
Oracle8i Server Release troubleshooting 7-13
8.1.5 3-5 RA4000 Array Controller 2-9
upgrading 6-9 RA4000 External Storage
Oracle Universal Installer 5-18 Subsystem
Oracle8i Enterprise Manager components summary 2-4
Release 8.1.5 3-6 Fibre Channel data paths 2-11
Oracle8i Parallel Server Option Fibre Host Adapter 2-11
Release 8.1.5 3-5 maximum distances between
Oracle8i Server Enterprise Edition components 2-6
Release 8.1.5 3-5 RA4000 Array 2-8
Oracle8i Server Release 8.1.5 3-5 RA4000 Array Controller 2-9
OSDs Storage Hub 2-9
installation 5-18 RAID planning
installation verification 5-45 overview 4-9
OUI 5-18
Compaq Confidential Need to Know Required
Writer: John Blackburn Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle 8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: k-index.doc Last Saved On: 5/18/99 4:18 PM
Index 5
ServerNet Switches 5-9
raw data storage and datatbase
cabling 5-9
size 4-11
overview 2-22
selecting correct levels 4-12
power sequencing 5-13
supported RAID levels 4-10
ServerNet VI Protocol 5-34
redundant
servers
client LAN 5-11
installation 5-3
ServerNet cluster
power distribution 5-12
interconnect 5-10
power sequencing 5-13
redundant Ethernet client LAN
Service Pack
Service Pack for 5-11
for a redundant Ethernet client
redundant Ethernet cluster
LAN 5-11
interconnect 5-8
for a redundant Ethernet cluster
Service Pack for 5-8
interconnect 5-8
RJ-45 receptacle xv
shared storage
troubleshooting 7-13
S
SmartStart 5-15
Sanman 5-34 installation 5-15
scalability SNMP agents 5-34
defined 1-3 installation 5-16, 5-19
SCSI software
drives 2-13 installation verification 5-45
ServerNet revisions 7-3
redundancy 7-10 Storage Hub
ServerNet cluster interconnect description 2-9
adapter installation 5-4 power sequencing 5-13
cabling 5-9 symbols in text xiv
lmhosts and hosts files entries symbols on equipment xv
for 5-15
non-redundant ServerNet T
cluster interconnect 2-21
redundant 5-10 technical support xvi
redundant ServerNet cluster telephone numbers xvii
interconnect 2-21 text conventions xiii
ServerNet PCI Adapter 2-22 troubleshooting
ServerNet Switch 2-22 basic tips 7-2
verifying communication cluster connectivity 7-10
in 5-42 error log files 6-3
ServerNet OSDs interconnect 7-8
installation 5-31 nodes unable to join
ServerNet PCI Adapters cluster 7-11
driver 5-34 Oracle software
installation 5-4 installation 7-5
overview 2-22 shared storage 7-13
viping 7-9
Compaq Confidential Need to Know Required
Writer: John Blackburn Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle 8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: k-index.doc Last Saved On: 5/18/99 4:18 PM
6 Compaq Parallel Database Cluster Model PDC/O1000 for Oracle 8i Release 8.1.5 Administrator Guide
electrical shock xv
U
Windows NT Server
uninterrupible power sources 5-12 installation 5-16
UPSs 5-12 Windows NT Server Disk
Administrator 5-18
www.compaq.com xvi
V
viping utility 5-42
W
warnings
Compaq Confidential Need to Know Required
Writer: John Blackburn Project: Compaq Parallel Database Cluster Model PDC/O1000 for Oracle 8i Release 8.1.5 Administrator Guide Comments:
Part Number: 104286-001 File Name: k-index.doc Last Saved On: 5/18/99 4:18 PM
| 104286-001
|
