Veritas Storage Foundation 5.1 SP1 for Oracle RAC Administrator"s Guide (5900-1512, April 2011)

■ Loading Veritas drivers into memory

See “Loading Veritas drivers into memory” on page 93.

■ Verifying VCS configuration

See “Verifying VCS configuration” on page 93.

■ Starting and stopping VCS

See “Starting and stopping VCS” on page 93.

■ Environment variables to start and stop VCS modules

See “Environment variables to start and stop VCS modules” on page 93.

■ Adding and removing LLT links

See “Adding and removing LLT links” on page 95.

■ Displaying the cluster details and LLT version for LLT links

See “Displaying the cluster details and LLT version for LLT links” on page 101.

■ Configuring aggregated interfaces under LLT

See “Configuring aggregated interfaces under LLT” on page 99.

■ Configuring destination-based load balancing for LLT

See “Configuring destination-based load balancing for LLT” on page 102.

■ Enabling and disabling intelligent resource monitoring

See “Enabling and disabling intelligent resource monitoring for agents

manually” on page 102.

■ Administering the AMF kernel driver

See “Administering the AMF kernel driver” on page 104.

If you encounter issues while administering VCS, see the troubleshooting section

in the Veritas Cluster Server Administrator's Guide for assistance.

Viewing available Veritas device drivers

To view the devices that are loaded in memory, run the kcmodule command as

shown in the following examples.

For example:

If you want to view whether or not the driver 'gab' is loaded in memory:

# kcmodule |grep gab

gab loaded explicit auto-loadable, unloadable

If you want to view whether or not the 'vx' drivers are loaded in memory:

# kcmodule |grep vx

Administering SF Oracle RAC and its components

Administering VCS