From: Ken Felmly (kfelmly@h40a.resva.trw.com)
Date: Wed Jan 29 2003 - 11:06:35 EST
Hi list,
I just need a sanity check on this. MC/SG A.11.14 (N4000's)
Specifically take a look at the SECOND_CLUSTER_LOCK_VG and PV and the
lan1 HEARTBEAT
(2 heartbeats. 1 of which will be on the "failoverable" LAN and the
other with a crossover cable between the 2 nodes).
The SECOND VG/PV are in case the controller in the RAID for the FIRST is
disabled.
LAN0 is the primary LAN with the package IP address(es).
LAN2 is connected to a dedicated archive network.
The NICs are on different VLANs, so we have no network connectivity issues.
Do you see any other issues here?
I appreciate.
CLUSTER_NAME oracle
FIRST_CLUSTER_LOCK_VG /dev/vg01
SECOND_CLUSTER_LOCK_VG /dev/vg02
NODE_NAME node1
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.90.1.5
NETWORK_INTERFACE lan3 # failover LAN0
NETWORK_INTERFACE lan2
STATIONARY_IP 10.90.2.5
NETWORK_INTERFACE lan4 # failover LAN2
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.168.10.136 # secondary heartbeat
{crossover cable between the two nodes}
FIRST_CLUSTER_LOCK_PV /dev/dsk/c0t6d0 # first controller - LUN1
SECOND_CLUSTER_LOCK_PV /dev/dsk/c0t7d0 # second controller - LUN 2
NODE_NAME node2
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.90.1.6
NETWORK_INTERFACE lan3 # failover LAN0
NETWORK_INTERFACE lan2
HEARTBEAT_IP 10.90.2.6
NETWORK_INTERFACE lan4 # failover LAN2
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.168.10.137 # secondary heartbeat
{crossover cable between the two nodes}
FIRST_CLUSTER_LOCK_PV /dev/dsk/c0t6d0 # first controller - LUN1
SECOND_CLUSTER_LOCK_PV /dev/dsk/c0t7d0 # second controller - LUN 2
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:25 EDT