Cluster Quick Installation

SUN CLUSTER

1. Install the Sun Java Web Console Software:bash-3.00# cd /cdrom/cdrom0bash-3.00# lsadministration_svr sun_cluster sun_cluster_agents sunwebconsolebash-3.00# cd sunwebconsole/bash-3.00# lssetup SunOS-5.9-sparc SUNWj3man.pkg SUNWjhdoc.pkgsmcwebserver.1m SUNWbzip.pkg SUNWj3rt.pkg SUNWjhrt.pkgsmreg.1m SUNWj3cfg.pkg SUNWjato.pkg SUNWmcon.pkgSunOS-5.10-sparc SUNWj3dev.pkg SUNWjhdem.pkg SUNWmctag.pkgSunOS-5.8-sparc SUNWj3dmo.pkg SUNWjhdev.pkg SUNWtcatu.pkgbash-3.00# ./setup--------------------------------------------------------------------------------------------------------------------------------------

2. Edit the path in profile:bash-3.00# vi /.profile PATH=$PATH:/opt/SUNWcluster/binMANPATH=$MANPATH:/opt/SUNWcluster/manexport PATH MANPATH:wq!bash-3.00# . ./.profile

3. Install the Sun Cluster: (For “Node 01”)bash-3.00# cd ..bash-3.00# lsadministration_svr sun_cluster sun_cluster_agents sunwebconsolebash-3.00# cd sun_clusterbash-3.00# lsCopyright LICENSEREADME Solaris_10 Solaris_9index.html README Solaris_8bash-3.00# cd Solaris_10/bash-3.00# lsPackages Toolsbash-3.00# cd Tools/bash-3.00# lsdefaults dot.release lib locale scinstallbash-3.00# ./scinstall

*** Main Menu ***

Please select from one of the following (*) options:

* 1) Install a cluster or cluster node 2) Configure a cluster to be JumpStarted from this install server 3) Add support for new data services to this cluster node 4) Upgrade this cluster node 5) Print release information for this cluster node

* ?) Help with menu options * q) Quit

Option: 1

*** Install Menu ***

Please select from any one of the following options:

1) Install all nodes of a new cluster 2) Install just this machine as the first node of a new cluster 3) Add this machine as a node in an existing cluster

?) Help with menu options q) Return to the Main Menu

Option: 2

*** Installing just the First Node of a New Cluster ***

This option is used to establish a new cluster using this machine as the first node in that cluster.

Once the cluster framework software is installed, you will be asked for the name of the cluster. Then, you will have the opportunity to run sccheck(1M) to test this machine for basic Sun Cluster pre-configuration requirements.

After sccheck(1M) passes, you will be asked for the names of the other nodes which will initially be joining that cluster. Unless this is a single-node cluster, you will be also be asked to provide certain cluster transport configuration information.

Press Control-d at any time to return to the Main Menu.

Do you want to continue (yes/no) [yes]? >>> Type of Installation <<<

There are two options for proceeding with cluster installation. For most clusters, a Typical installation is recommended. However, you might need to select the Custom option if not all of the Typical defaults can be applied to your cluster.

For more information about the differences between the Typical and Custom installation methods, select the Help option from the menu.

Please select from one of the following options:

1) Typical 2) Custom

?) Help q) Return to the Main Menu

Option [1]: 2

>>> Software Package Installation <<<

Installation of the Sun Cluster framework software packages will take a few minutes to complete.

Is it okay to continue (yes/no) [yes]?

** Installing SunCluster 3.1 framework **SUNWscr.....doneSUNWscu.....doneSUNWscsckr..doneSUNWscscku..doneSUNWscnmr...doneSUNWscnmu...doneSUNWscdev...doneSUNWscgds...doneSUNWscman...doneSUNWscsal...doneSUNWscsam...doneSUNWscvm....doneSUNWmdmr....doneSUNWmdmu....doneSUNWscmasar.doneSUNWscmasau.doneSUNWscva....doneSUNWscspm...doneSUNWscspmu..doneSUNWscspmr..doneSUNWscrsm...doneSUNWcsc.....doneSUNWcscspm..doneSUNWcscspmu.doneSUNWdsc.....doneSUNWdscspm..doneSUNWdscspmu.doneSUNWesc.....doneSUNWescspm..doneSUNWescspmu.doneSUNWfsc.....doneSUNWfscspm..doneSUNWfscspmu.doneSUNWhsc.....doneSUNWhscspm..doneSUNWhscspmu.doneSUNWjsc.....doneSUNWjscman..doneSUNWjscspm..doneSUNWjscspmu.doneSUNWksc.....doneSUNWkscspm..doneSUNWkscspmu.done

Press Enter to continue:

>>> Software Patch Installation <<<

If there are any Solaris or Sun Cluster patches that need to be added as part of this Sun Cluster installation, scinstall can add them

for you. All patches that need to be added must first be downloaded into a common patch directory. Patches can be downloaded into the patch directory either as individual patches or as patches grouped together into one or more tar, jar, or zip files.

If a patch list file is provided in the patch directory, only those patches listed in the patch list file are installed. Otherwise, all patches found in the directory will be installed. Refer to the patchadd(1M) man page for more information regarding patch list files.

Do you want scinstall to install patches for you (yes/no) [yes]? n

>>> Cluster Name <<<

Each cluster has a name assigned to it. The name can be made up of any characters other than whitespace. Each cluster name should be unique within the namespace of your enterprise.

What is the name of the cluster you want to establish? dbbl-clus

>>> Check <<<

This step allows you to run sccheck(1M) to verify that certain basic hardware and software pre-configuration requirements have been met. If sccheck(1M) detects potential problems with configuring this machine as a cluster node, a report of failed checks is prepared and available for display on the screen. Data gathering and report generation can take several minutes, depending on system configuration.

Do you want to run sccheck (yes/no) [yes]?

Running sccheck ...

sccheck: Requesting explorer data and node report from dbbl01.sccheck: dbbl01: Explorer finished.sccheck: dbbl01: Starting single-node checks.sccheck: dbbl01: Single-node checks finished.


>>> Cluster Nodes <<<

This Sun Cluster release supports a total of up to 16 nodes.

Please list the names of the other nodes planned for the initial cluster configuration. List one node name per line. When finished, type Control-D:

Node name (Control-D to finish): dbbl02 Node name (Control-D to finish): ^D

This is the complete list of nodes:

dbbl01dbbl02

Is it correct (yes/no) [yes]?

>>> Authenticating Requests to Add Nodes <<<

Once the first node establishes itself as a single node cluster, other nodes attempting to add themselves to the cluster configuration must be found on the list of nodes you just provided. You can modify this list using scconf(1M) or other tools once the cluster has been established.

By default, nodes are not securely authenticated as they attempt to add themselves to the cluster configuration. This is generally considered adequate, since nodes which are not physically connected to the private cluster interconnect will never be able to actually join the cluster. However, DES authentication is available. If DES authentication is selected, you must configure all necessary encryption keys before any node will be allowed to join the cluster (see keyserv(1M), publickey(4)).

Do you need to use DES authentication (yes/no) [no]?

>>> Network Address for the Cluster Transport <<<

The private cluster transport uses a default network address of 172.16.0.0. But, if this network address is already in use elsewhere within your enterprise, you may need to select another address from the range of recommended private addresses (see RFC 1918 for details).

If you do select another network address, bear in mind that the Sun Cluster software requires that the rightmost two octets always be zero.

The default netmask is 255.255.0.0. You can select another netmask, as long as it minimally masks all bits given in the network address.

Is it okay to accept the default network address (yes/no) [yes]?

Is it okay to accept the default netmask (yes/no) [yes]?

>>> Point-to-Point Cables <<<

The two nodes of a two-node cluster may use a directly-connected interconnect. That is, no cluster transport junctions are configured. However, when there are greater than two nodes, this interactive form of scinstall assumes that there will be exactly two cluster transport junctions.

Does this two-node cluster use transport junctions (yes/no) [yes]? no

>>> Cluster Transport Junctions <<<

All cluster transport adapters in this cluster must be cabled to a transport junction, or "switch". And, each adapter on a given node must be cabled to a different junction. Interactive scinstall requires that you identify two switches for use in the cluster and the two transport adapters on each node to which they are cabled.

What is the name of the first junction in the cluster [switch1]?

What is the name of the second junction in the cluster [switch2]?

>>> Cluster Transport Adapters and Cables <<<

You must configure at least two cluster transport adapters for each node in the cluster. These are the adapters which attach to the private cluster interconnect.

Select the first cluster transport adapter:

1) bge1 2) bge2 3) bge3 4) ce0 5) ce1 6) ce2 7) ce3 8) Other

Option: 4

Will this be a dedicated cluster transport adapter (yes/no) [yes]?

Adapter "ce0" is an Ethernet adapter.

Searching for any unexpected network traffic on "ce0" ... done Verification completed. No traffic was detected over a 10 second sample period.

The "dlpi" transport type will be set for this cluster.

Name of the junction to which "ce0" is connected [switch1]?

Each adapter is cabled to a particular port on a transport junction. And, each port is assigned a name. You can explicitly assign a name to each port. Or, for Ethernet and Infiniband switches, you can choose to allow scinstall to assign a default name for you. The default port name assignment sets the name to the node number of the node hosting the transport adapter at the other end of the cable.

For more information regarding port naming requirements, refer to the scconf_transp_jct family of man pages (e.g., scconf_transp_jct_dolphinswitch(1M)).

Use the default port name for the "ce0" connection (yes/no) [yes]?

Select the second cluster transport adapter:

1) bge1 2) bge2 3) bge3 4) ce0 5) ce1 6) ce2 7) ce3 8) Other

Option: 5

Will this be a dedicated cluster transport adapter (yes/no) [yes]?

Adapter "ce1" is an Ethernet adapter.

Searching for any unexpected network traffic on "ce1" ... done Verification completed. No traffic was detected over a 10 second sample period.

Name of the junction to which "ce1" is connected [switch2]?

Use the default port name for the "ce1" connection (yes/no) [yes]?

>>> Global Devices File System <<<

Each node in the cluster must have a local file system mounted on /global/.devices/node@<nodeID> before it can successfully participate as a cluster member. Since the "nodeID" is not assigned until scinstall is run, scinstall will set this up for you.

You must supply the name of either an already-mounted file system or raw disk partition which scinstall can use to create the global devices file system. This file system or partition should be at least 512 MB in size.

If an already-mounted file system is used, the file system must be empty. If a raw disk partition is used, a new file system will be created for you.

The default is to use /globaldevices.

Is it okay to use this default (yes/no) [yes]?

>>> Quorum Configuration <<<

Every two-node cluster requires at least one quorum device. By default, scinstall will select and configure a shared SCSI quorum disk device for you.

This screen allows you to disable the automatic selection and configuration of a quorum device.

The only time that you must disable this feature is when ANY of the shared storage in your cluster is not qualified for use as a Sun Cluster quorum device. If your storage was purchased with your cluster, it is qualified.

4. Install the Sun Cluster: (For “Node 02”):

-----------------------------------------------------------------------------------------------Same as Node 01----------------------------------------------------------------------------------------------------

*** Install Menu ***

Please select from any one of the following options:

1) Install all nodes of a new cluster 2) Install just this machine as the first node of a new cluster 3) Add this machine as a node in an existing cluster

?) Help with menu options q) Return to the Main Menu

Option: 3

*** Adding a Node to an Existing Cluster ***

This option is used to add this machine as a node in an already established cluster. If this is an initial cluster install, there may only be a single node which has established itself in the new cluster.

Once the cluster framework software is installed, you will be asked to provide both the name of the cluster and the name of one of the nodes already in the cluster. Then, sccheck(1M) is run to test this machine for basic Sun Cluster pre-configuration requirements.

After sccheck(1M) passes, you may be asked to provide certain cluster transport configuration information.

Press Control-d at any time to return to the Main Menu.

Do you want to continue (yes/no) [yes]?

>>> Type of Installation <<<

There are two options for proceeding with cluster installation. For most clusters, a Typical installation is recommended. However, you might need to select the Custom option if not all of the Typical defaults can be applied to your cluster.

For more information about the differences between the Typical and Custom installation methods, select the Help option from the menu.


1) Typical 2) Custom

?) Help q) Return to the Main Menu

Option [1]: 2

>>> Software Package Installation <<<

Installation of the Sun Cluster framework software packages will take a few minutes to complete.


** Installing SunCluster 3.1 framework **---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

>>> Sponsoring Node <<<

For any machine to join a cluster, it must identify a node in that cluster willing to "sponsor" its membership in the cluster. When configuring a new cluster, this "sponsor" node is typically the first node used to build the new cluster. However, if the cluster is already established, the "sponsoring" node can be any node in that cluster.

Already established clusters can keep a list of hosts which are able to configure themselves as new cluster members. This machine should be in the join list of any cluster which it tries to join. If the list does not include this machine, you may need to add it using scconf(1M) or other tools.

And, if the target cluster uses DES to authenticate new machines attempting to configure themselves as new cluster members, the necessary encryption keys must be configured before any attempt to join.

What is the name of the sponsoring node? dbbl01

>>> Cluster Name <<<

Each cluster has a name assigned to it. When adding a node to the cluster, you must identify the name of the cluster you are attempting to join. A sanity check is performed to verify that the "sponsoring" node is a member of that cluster.

What is the name of the cluster you want to join? dbbl-clus

Attempting to contact "dbbl01" ... done

Cluster name "dbbl-clus" is correct. Press Enter to continue:

>>> Autodiscovery of Cluster Transport <<<

If you are using Ethernet or Infiniband adapters as the cluster transport adapters, autodiscovery is the best method for configuring the cluster transport.

Do you want to use autodiscovery (yes/no) [yes]? yes

Probing ............

The following connections were discovered:

dbbl01:ce0 switch1 dbbl02:ce0dbbl01:ce1 switch2 dbbl02:ce1

Is it okay to add these connections to the configuration (yes/no) [yes]?

>>> Global Devices File System <<<

Each node in the cluster must have a local file system mounted on /global/.devices/node@<nodeID> before it can successfully participate as a cluster member. Since the "nodeID" is not assigned until scinstall is run, scinstall will set this up for you.

You must supply the name of either an already-mounted file system or raw disk partition which scinstall can use to create the global devices file system. This file system or partition should be at least 512 MB in size.

If an already-mounted file system is used, the file system must be empty. If a raw disk partition is used, a new file system will be created for you.

The default is to use /globaldevices.

Is it okay to use this default (yes/no) [yes]?

>>> Automatic Reboot <<<

Once scinstall has successfully installed and initialized the Sun Cluster software for this machine, it will be necessary to reboot. The reboot will cause this machine to join the cluster for the first time.

Do you want scinstall to reboot for you (yes/no) [yes]? no

You will need to manually reboot this node in "cluster mode" after scinstall successfully completes.


5. Install the SC Quorum Devices:bash-3.00# scdidadm –L (See the global devices)1 dbbl01:/dev/rdsk/c0t0d0 /dev/did/rdsk/d1 2 dbbl01:/dev/rdsk/c1t0d0 /dev/did/rdsk/d2 2 dbbl02:/dev/rdsk/c1t0d0 /dev/did/rdsk/d2 3 dbbl01:/dev/rdsk/c1t1d0 /dev/did/rdsk/d3

3 dbbl02:/dev/rdsk/c1t1d0 /dev/did/rdsk/d3 4 dbbl01:/dev/rdsk/c1t2d0 /dev/did/rdsk/d4 4 dbbl02:/dev/rdsk/c1t2d0 /dev/did/rdsk/d4 5 dbbl01:/dev/rdsk/c1t3d0 /dev/did/rdsk/d5 5 dbbl02:/dev/rdsk/c1t3d0 /dev/did/rdsk/d5 6 dbbl01:/dev/rdsk/c1t4d0 /dev/did/rdsk/d6 6 dbbl02:/dev/rdsk/c1t4d0 /dev/did/rdsk/d6 7 dbbl01:/dev/rdsk/c1t5d0 /dev/did/rdsk/d7 7 dbbl02:/dev/rdsk/c1t5d0 /dev/did/rdsk/d7 8 dbbl01:/dev/rdsk/c1t8d0 /dev/did/rdsk/d8 8 dbbl02:/dev/rdsk/c1t8d0 /dev/did/rdsk/d8 9 dbbl01:/dev/rdsk/c1t9d0 /dev/did/rdsk/d9 9 dbbl02:/dev/rdsk/c1t9d0 /dev/did/rdsk/d9 10 dbbl01:/dev/rdsk/c2t0d0 /dev/did/rdsk/d10 11 dbbl01:/dev/rdsk/c2t1d0 /dev/did/rdsk/d11 12 dbbl02:/dev/rdsk/c0t0d0 /dev/did/rdsk/d12 13 dbbl02:/dev/rdsk/c2t0d0 /dev/did/rdsk/d13 14 dbbl02:/dev/rdsk/c2t1d0 /dev/did/rdsk/d14 bash-3.00# scsetup

>>> Initial Cluster Setup <<<

This program has detected that the cluster "installmode" attribute is still enabled. As such, certain initial cluster setup steps will be performed at this time. This includes adding any necessary quorum devices, then resetting both the quorum vote counts and the "installmode" property.

Please do not proceed if any additional nodes have yet to join the cluster.


Do you want to add any quorum devices (yes/no) [yes]?

Following are supported Quorum Devices types in Sun Cluster. Please refer to Sun Cluster documentation for detailed information on these supported quorum device topologies.

What is the type of device you want to use?

1) Directly attached shared disk 2) Network Attached Storage (NAS) from Network Appliance

q)

Option: 1

>>> Add a SCSI Quorum Disk <<<

A SCSI quorum device is considered to be any Sun Cluster supported attached storage which connected to two or more nodes of the cluster. Dual-ported SCSI-2 disks may be used as quorum devices in two-node clusters. However, clusters with more than two nodes require that SCSI-3 PGR disks be used for all disks with more than two node-to-disk paths.

You can use a disk containing user data or one that is a member of a device group as a quorum device.

For more information on supported quorum device topologies, see the Sun Cluster documentation.


Which global device do you want to use (d<N>)? d4

Is it okay to proceed with the update (yes/no) [yes]?

scconf -a -q globaldev=d4

Command completed successfully.


Do you want to add another quorum device (yes/no) [yes]? no

Once the "installmode" property has been reset, this program will skip "Initial Cluster Setup" each time it is run again in the future. However, quorum devices can always be added to the cluster using the regular menu options. Resetting this property fully activates quorum settings and is necessary for the normal and safe operation of the cluster.

Is it okay to reset "installmode" (yes/no) [yes]?

scconf -c -q resetscconf -a -T node=.

Cluster initialization is complete.

Type ENTER to proceed to the main menu:

*** Main Menu ***


1) Quorum 2) Resource groups 3) Data Services 4) Cluster interconnect 5) Device groups and volumes 6) Private hostnames 7) New nodes 8) Other cluster properties

?) Help with menu options q) Quit

Option: q

bash-3.00# scstat -q

-- Quorum Summary --

Quorum votes possible: 3 Quorum votes needed: 2 Quorum votes present: 3

-- Quorum Votes by Node --

Node Name Present Possible Status --------- ------- -------- ------ Node votes: dbbl01 1 1 Online Node votes: dbbl02 1 1 Online

-- Quorum Votes by Device --

Device Name Present Possible Status ----------- ------- -------- ------ Device votes: /dev/did/rdsk/d4s2 1 1 Online

bash-3.00# formatSearching for disks...done

AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e,600000/scsi@2,1/sd@0,0 1. c1t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e,600000/scsi@2,1/sd@1,0 2. c1t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e,600000/scsi@2,1/sd@2,0 3. c1t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e,600000/scsi@2,1/sd@3,0 4. c1t4d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e,600000/scsi@2,1/sd@4,0 5. c1t5d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e,600000/scsi@2,1/sd@5,0 6. c1t8d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e,600000/scsi@2,1/sd@8,0 7. c1t9d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e,600000/scsi@2,1/sd@9,0 8. c2t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@1c,600000/scsi@2/sd@0,0 9. c2t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@1c,600000/scsi@2/sd@1,0Specify disk (enter its number): 2selecting c1t2d0[disk formatted]

partition> Current partition table (original):Total disk cylinders available: 14087 + 2 (reserved cylinders)

Part Tag Flag Cylinders Size Blocks 0 root wm 0 - 12 129.19MB (13/0/0) 264576 1 swap wu 13 - 25 129.19MB (13/0/0) 264576 2 backup wu 0 - 14086 136.71GB (14087/0/0) 286698624 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 usr wm 26 - 14086 136.46GB (14061/0/0) 286169472 7 unassigned wm 0 0 (0/0/0) 0

partition> q

format> qbash-3.00# scconf -p | more Cluster name: dbbl-clusCluster ID: 0x480AE575Cluster install mode: disabled (After install the quorum it automatically be disabled)Cluster private net: 172.16.0.0Cluster private netmask: 255.255.0.0Cluster new node authentication: unixCluster new node list: <. - Exclude all nodes>Cluster transport heart beat timeout: 10000Cluster transport heart beat quantum: 1000Cluster nodes: dbbl01 dbbl02

Cluster node name: dbbl01 Node ID: 1 Node enabled: yes Node private hostname: clusternode1-priv Node quorum vote count: 1 Node reservation key: 0x480AE57500000001 Node transport adapters: ce0 ce1

Node transport adapter: ce0 Adapter enabled: yes Adapter transport type: dlpi Adapter property: device_name=ce Adapter property: device_instance=0 Adapter property: lazy_free=1 Adapter property: dlpi_heartbeat_timeout=10000 Adapter property: dlpi_heartbeat_quantum=1000 Adapter property: nw_bandwidth=80 Adapter property: bandwidth=70

Adapter property: netmask=255.255.255.128 Adapter property: ip_address=172.16.0.129 Adapter port names: 0

Adapter port: 0 Port enabled: yes

Node transport adapter: ce1 Adapter enabled: yes Adapter transport type: dlpi Adapter property: device_name=ce Adapter property: device_instance=1 Adapter property: lazy_free=1 Adapter property: dlpi_heartbeat_timeout=10000 Adapter property: dlpi_heartbeat_quantum=1000 Adapter property: nw_bandwidth=80 Adapter property: bandwidth=70 Adapter property: netmask=255.255.255.128 Adapter property: ip_address=172.16.1.1 Adapter port names: 0

Adapter port: 0 Port enabled: yes

Cluster node name: dbbl02 Node ID: 2 Node enabled: yes Node private hostname: clusternode2-priv Node quorum vote count: 1 Node reservation key: 0x480AE57500000002 Node transport adapters: ce0 ce1

Node transport adapter: ce0 Adapter enabled: yes Adapter transport type: dlpi Adapter property: device_name=ce Adapter property: device_instance=0 Adapter property: lazy_free=1

6. View the owner Node of the Quorum Device:bash-3.00# cd /usr/cluster/lib/scbash-3.00# ./cmm_ctl -g

*** Current Cluster State ***

Local Node Id : 2Highest Node Id : 2Current reconfiguration seqnum : 6Max reconfiguration step : 13CMM is in the end state.

*** Incarnation Numbers of Current Cluster Members ***

Node 1 : 1208673844Node 2 : 1208675464

*** Cluster Configuration Information ***

Max Nodes Supported : 64Node Fenceoff Timeout : 300 secondsBoot Delay : 60 secondsNode Halt Timeout : 5 secondsFailfast grace time : 10 secondsFailfast panic delay : 30 secondsOrb Stop Timeout : 30 secondsOrb Return Timeout : 30 secondsOrb Abort Timeout : 30 secondsOrb Step Timeout : 120 seconds

*** Cluster Quorum Information ***

Total configured votes : 3Current cluster votes : 3Votes needed for quorum : 2

*** Node quorum info ***

Node 1 : state = UP, votes_configured = 1, reservation_key = 0x480ae57500000001

Node 2 : state = UP, votes_configured = 1, reservation_key = 0x480ae57500000002

*** Quorum device info ***

Quorum device 1 : global device name = '/dev/did/rdsk/d4s2', nodes with configured paths = 0x3, state = ONLINE, votes_configured = 1, reservation owner = node 1

7. Veritas Volume Manager configuration on Cluster (“Node01”):

bash-3.00# cd /dumpbash-3.00# lscluster_patch es345 Solaris_sparcbash-3.00# cd es345/bash-3.00# ls_ds.sto es345~a2.gz oracl~ar.gz verit~ar.gzes345~a1.gz es345~ar.gz suncl~ar.gzbash-3.00# gunzip verit~ar.gzbash-3.00# ls_ds.sto es345~a2.gz oracl~ar.gz verit~ares345~a1.gz es345~ar.gz suncl~ar.gzbash-3.00# file verit~arverit~ar: USTAR tar archive

bash-3.00# tar xvf verit~ar

bash-3.00# cd /dump_3.1/veritasbash-3.00# ls4.0 READMEbash-3.00# cd 4.0/bash-3.00# lsREADME storage_solutions_4.0_sunw.tar.gzbash-3.00# gzcat storage_solutions_4.0_sunw.tar.gz |tar xvf –bash-3.00# lsREADME storage_solutions_4.0_sunw.tar.gzstorage_solutions_4.0_sunwbash-3.00# cd storage_solutions_4.0_sunwbash-3.00# lscopyright patches release_notes supportdocs pkgs scripts veritas_enabledbash-3.00# cd pkgs/bash-3.00# lsVRTSalloc VRTSfppm VRTSfspro VRTSobgui VRTSvmdoc VRTSvxfsVRTSap VRTSfsdoc VRTSmuob VRTStep VRTSvmman VRTSvxvmVRTSddlpr VRTSfsman VRTSob VRTSvlic VRTSvmprobash-3.00# pwd/dump_3.1/veritas/4.0/storage_solutions_4.0_sunw/pkgsbash-3.00# pkgadd –d .----------------------------------------------------------------------------------------------------------------------------------------------

bash-3.00# ls_ds.sto es345~a2.gz opt suncl~ar.gzes345~a1.gz es345~ar.gz oracl~ar.gz verit~arbash-3.00# cd optbash-3.00# lssesbash-3.00# cd sesbash-3.00# lssoftwarebash-3.00# cd software/bash-3.00# lsvxSF5.0bash-3.00# cd vxSF5.0/bash-3.00# lsauthentication_service storage_foundationcluster_management_console storage_foundation_cluster_file_systemcluster_server storage_foundation_for_db2cluster_server_agents storage_foundation_for_oraclefile_system storage_foundation_for_oracle_racgetting_started.pdf storage_foundation_for_sybasegnu volume_managerinstaller volume_replicatorperl windows

bash-3.00# cd s torage_foundationbash-3.00# lscopyright patches scripts veritas_enableddocs pkgs toolsinstallsf release_notes uninstallsfbash-3.00# cd pkgs/bash-3.00# lsinfo VRTSddlpr.tar.gz VRTSjre15.tar.gz VRTSvcsmn.tar.gzSYMClma.tar.gz VRTSdsa.tar.gz VRTSllt.tar.gz VRTSvcsvr.tar.gzVRTSaa.tar.gz VRTSdsm.tar.gz VRTSmapro.tar.gz VRTSvdid.tar.gzVRTSacclib.tar.gz VRTSfas.tar.gz VRTSmh.tar.gz VRTSvlic.tar.gzVRTSalloc.tar.gz VRTSfasag.tar.gz VRTSob.tar.gz VRTSvmdoc.tar.gzVRTSat.tar.gz VRTSfasdc.tar.gz VRTSobc33.tar.gz VRTSvmman.tar.gzVRTSccg.tar.gz VRTSfsdoc.tar.gz VRTSobgui.tar.gz VRTSvmpro.tar.gzVRTScmccc.tar.gz VRTSfsman.tar.gz VRTSobweb.tar.gz VRTSvmweb.tar.gzVRTScmcs.tar.gz VRTSfsmnd.tar.gz VRTSpbx.tar.gz VRTSvrdoc.tar.gzVRTScs.tar.gz VRTSfspro.tar.gz VRTSperl.tar.gz VRTSvrpro.tar.gzVRTScscm.tar.gz VRTSfssdk.tar.gz VRTSsmf.tar.gz VRTSvrw.tar.gzVRTScscw.tar.gz VRTSfsweb.tar.gz VRTSspt.tar.gz VRTSvsvc.tar.gzVRTScsdoc.tar.gz VRTSgab.tar.gz VRTSvail.tar.gz VRTSvxfen.tar.gzVRTScssim.tar.gz VRTSgapms.tar.gz VRTSvailadmin VRTSvxfs.tar.gzVRTScutil.tar.gz VRTSgcsha.tar.gz VRTSvcs.tar.gz VRTSvxmsa.tar.gzVRTScweb.tar.gz VRTSgcspr.tar.gz VRTSvcsag.tar.gz VRTSvxvm.tar.gzVRTSdcli.tar.gz VRTSicsco.tar.gz VRTSvcsdc.tar.gz VRTSweb.tar.gzVRTSdcp.tar.gz VRTSjre.tar.gz VRTSvcsmg.tar.gzbash-3.00# cd ..bash-3.00# lscopyright patches scripts veritas_enableddocs pkgs toolsinstallsf release_notes uninstallsfbash-3.00# cd ..bash-3.00# lsauthentication_service storage_foundationcluster_management_console storage_foundation_cluster_file_systemcluster_server storage_foundation_for_db2cluster_server_agents storage_foundation_for_oraclefile_system storage_foundation_for_oracle_racgetting_started.pdf storage_foundation_for_sybasegnu volume_managerinstaller volume_replicatorperl windowsbash-3.00# cd vo lume_manager/bash-3.00# lscopyright patches scripts veritas_enableddocs pkgs tools

installvm release_notes uninstallvmbash-3.00# cd p kgs/bash-3.00# lsinfo VRTSdcp.tar.gz VRTSob.tar.gz VRTSvmdoc.tar.gzSYMClma.tar.gz VRTSddlpr.tar.gz VRTSobc33.tar.gz VRTSvmman.tar.gzVRTSaa.tar.gz VRTSdsa.tar.gz VRTSobgui.tar.gz VRTSvmpro.tar.gzVRTSalloc.tar.gz VRTSdsm.tar.gz VRTSobweb.tar.gz VRTSvmweb.tar.gzVRTSat.tar.gz VRTSfspro.tar.gz VRTSpbx.tar.gz VRTSvrdoc.tar.gzVRTSccg.tar.gz VRTSgcsha.tar.gz VRTSperl.tar.gz VRTSvrpro.tar.gzVRTScs.tar.gz VRTSgcspr.tar.gz VRTSsmf.tar.gz VRTSvrw.tar.gzVRTScsdoc.tar.gz VRTSicsco.tar.gz VRTSspt.tar.gz VRTSvsvc.tar.gzVRTScweb.tar.gz VRTSjre.tar.gz VRTSvcsvr.tar.gz VRTSvxvm.tar.gzVRTSdbms3.tar.gz VRTSjre15.tar.gz VRTSvdid.tar.gz VRTSweb.tar.gzVRTSdcli.tar.gz VRTSmh.tar.gz VRTSvlic.tar.gzbash-3.00# cd ..bash-3.00# lscopyright patches scripts veritas_enableddocs pkgs toolsinstallvm release_notes uninstallvmbash-3.00# cd ..bash-3.00# lsauthentication_service storage_foundationcluster_management_console storage_foundation_cluster_file_systemcluster_server storage_foundation_for_db2cluster_server_agents storage_foundation_for_oraclefile_system storage_foundation_for_oracle_racgetting_started.pdf storage_foundation_for_sybasegnu volume_managerinstaller volume_replicatorperl windowsbash-3.00# cd st orage_foundationbash-3.00# lscopyright patches scripts veritas_enableddocs pkgs toolsinstallsf release_notes uninstallsfbash-3.00# ./installsf –rsh (rsh to install other Node02)

Veritas Storage Foundation 5.0 Installation Program

Copyright (c) 2006 Symantec Corporation. All rights reserved. Symantec, theSymantec Logo are trademarks or registered trademarks of SymantecCorporation or its affiliates in the U.S. and other countries. Other namesmay be trademarks of their respective owners.

The Licensed Software and Documentation are deemed to be "commercialcomputer software" and "commercial computer software documentation" asdefined in FAR Sections 12.212 and DFARS Section 227.7202.

Logs for installsf are being created in /var/tmp/installsf-kSJIUD.

Enter the system names separated by spaces on which to install SF: dbbl01 dbbl02

Initial system check: Checking rsh communication with dbbl02 ..................... SunOS 5.10 Checking SF installation on dbbl01 ...................... not installed Checking SF installation on dbbl02 ...................... not installed


Checking system licensingInstalling licensing packagesSF is not licensed on dbbl01

Enter a SF license key for dbbl01:IRPH-TDRO-PWV8-Y774-V94M-TURCIRPH-TDRO-PWV8-Y774-V94M-TURC successfully registered on dbbl01Demo SF license registered on dbbl01

Do you want to enter another license key for dbbl01? [y,n,q] (n)IRPH-TDRO-PWV8-Y774-V94M-TURC successfully registered on dbbl02Demo SF license registered on dbbl02

Do you want to enter another license key for dbbl02? [y,n,q] (n)


Checking installed packages on dbbl01Checking installed packages on dbbl02


SF can be installed without optional packages to conserve disk space.

Required Veritas Storage Foundation packages - 1023 MB requiredAll Veritas Storage Foundation packages - 1051 MB required

Select the packages to be installed on all systems? [1-2,q,?] (2)


The following SF packages will be installed:VRTSperl Veritas Perl 5.8.8 RedistributionVRTSvlic Veritas LicensingVRTSicsco Symantec Common InfrastructureVRTSpbx Symantec Private Branch ExchangeVRTSsmf Symantec Service Management FrameworkVRTSat Symantec Product Authentication ServiceVRTSobc33 Veritas Enterprise Administrator Core ServiceVRTSob Veritas Enterprise Administrator ServiceVRTSobgui Veritas Enterprise AdministratorVRTSccg Veritas Enterprise Administrator Central Control GridVRTSmh Veritas Storage Foundation Managed Host by SymantecVRTSaa Veritas Enterprise Administrator Action AgentVRTSspt Veritas Software Support Tools

SYMClma Symantec License Inventory AgentVRTSvxvm Veritas Volume Manager BinariesVRTSdsa Veritas Datacenter Storage AgentVRTSfspro Veritas File System Management Services ProviderVRTSvmman Veritas Volume Manager Manual PagesVRTSvmdoc Veritas Volume Manager Documentation

Press [Return] to continue:...continued:VRTSdcli Veritas Distributed Command Line InterfaceVRTSalloc Veritas Volume Manager Intelligent Storage ProvisioningVRTSvmpro Veritas Volume Manager Management Services ProviderVRTSvsvc Veritas Volume Server and Client ProviderVRTSvdid Veritas Device Identification APIVRTSddlpr Veritas Device Discovery Layer Services ProviderVRTSvrpro Veritas Volume Replicator Client Extension and Provider for

Veritas Enterprise AdministratorVRTSvcsvr Veritas Cluster Server Agents for VVRVRTSjre Veritas Java Runtime Environment RedistributionVRTSjre15 Veritas Java Runtime Environment RedistributionVRTSweb Veritas Java Web ServerVRTSvrw Veritas Volume Replicator Web ConsoleVRTSvrdoc Veritas Volume Replicator DocumentationVRTSvxfs Veritas File SystemVRTSfsman Veritas File System Manual PagesVRTSfsdoc Veritas File System DocumentationVRTSfssdk Veritas File System Software Developer KitVRTSfsmnd Veritas File System Software Developer Kit Manual PagesVRTSvail Veritas Array Integration LayerVRTSfas Veritas FlashSnap Agent for Symmetrix

Press [Return] to continue: ...continued:VRTSfasdc Veritas FlashSnap Agent for Symmetrix DocumentationVRTSvxmsa Veritas Mapping Service, Application LibrariesVRTSgapms Veritas Generic Array PluginVRTSmapro Veritas Storage Foundation GUI for Mapping

Press [Return] to continue: Checking for any AP driver issues on dbbl01 ...................... NoneChecking for any AP driver issues on dbbl02 ...................... NoneIt is possible to install SF packages without performing configuration.

It is optional to configure SF now. If you choose to configure SF later, you can either do so manually or run the installsf -configure command.

Are you ready to configure SF? [y,n,q] (y)


Installation completed successfully on all systems

The enclosure-based naming scheme is a feature of Veritas Volume Manager. It allows one to reference disks using a symbolic name that is more meaningful than the operating system's normal device access name. This symbolic name is typically derived from the array name.Do you want to set up the enclosure-based naming scheme? [y,n,q,?] (n)


Veritas Volume Manager default disk group name configuration:Many Veritas Volume Manager commands affect the contents or configuration of a disk group. Such commands

8. Create the Disk Group:

bash-3.00# vxdisk listDEVICE TYPE DISK GROUP STATUSc1t0d0s2 auto:none - - online invalidc1t1d0s2 auto:none - - online invalidc1t2d0s2 auto:none - - online invalidc1t3d0s2 auto:none - - online invalidc1t4d0s2 auto:none - - online invalidc1t5d0s2 auto:none - - online invalidc1t8d0s2 auto:none - - online invalidc1t9d0s2 auto:none - - online invalidc2t0d0s2 auto:none - - online invalidc2t1d0s2 auto:none - - online invalid

bash-3.00# vxdisksetup -i c1t0d0 c1t1d0bash-3.00# vxdisk listDEVICE TYPE DISK GROUP STATUSc1t0d0s2 auto:cdsdisk - - onlinec1t1d0s2 auto:cdsdisk - - onlinec1t2d0s2 auto:none - - online invalidc1t3d0s2 auto:none - - online invalidc1t4d0s2 auto:none - - online invalidc1t5d0s2 auto:none - - online invalidc1t8d0s2 auto:none - - online invalidc1t9d0s2 auto:none - - online invalidc2t0d0s2 auto:none - - online invalidc2t1d0s2 auto:none - - online invalid

bash-3.00# vxdg init nfsdg disk01=c1t0d0 disk02=c1t1d0

bash-3.00# vxdisk listDEVICE TYPE DISK GROUP STATUSc1t0d0s2 auto:cdsdisk disk01 nfsdg onlinec1t1d0s2 auto:cdsdisk disk02 nfsdg onlinec1t2d0s2 auto:none - - online invalidc1t3d0s2 auto:none - - online invalidc1t4d0s2 auto:none - - online invalidc1t5d0s2 auto:none - - online invalidc1t8d0s2 auto:none - - online invalidc1t9d0s2 auto:none - - online invalidc2t0d0s2 auto:none - - online invalidc2t1d0s2 auto:none - - online invalid

bash-3.00# vxdisk -o alldgs listDEVICE TYPE DISK GROUP STATUS

c1t0d0s2 auto:cdsdisk disk01 nfsdg onlinec1t1d0s2 auto:cdsdisk disk02 nfsdg onlinec1t2d0s2 auto:none - - online invalidc1t3d0s2 auto:none - - online invalidc1t4d0s2 auto:none - - online invalidc1t5d0s2 auto:none - - online invalidc1t8d0s2 auto:none - - online invalidc1t9d0s2 auto:none - - online invalidc2t0d0s2 auto:none - - online invalidc2t1d0s2 auto:none - - online invalid

(After creating the other node disk group)bash-3.00# vxdisk -o alldgs listDEVICE TYPE DISK GROUP STATUSc1t0d0s2 auto:cdsdisk disk01 nfsdg onlinec1t1d0s2 auto:cdsdisk disk02 nfsdg onlinec1t2d0s2 auto:none - - online invalidc1t3d0s2 auto:cdsdisk - (webdg) onlinec1t4d0s2 auto:cdsdisk - (webdg) onlinec1t5d0s2 auto:none - - online invalidc1t8d0s2 auto:none - - online invalidc1t9d0s2 auto:none - - online invalidc2t0d0s2 auto:none - - online invalidc2t1d0s2 auto:none - - online invalid

bash-3.00# vxassist -g nfsdg make nfsvol 1g layout-mirr=mirror,nolog alloc=disk01 disk02

bash-3.00# vxprint -htDisk group: nfsdg

DG NAME NCONFIG NLOG MINORS GROUP-IDST NAME STATE DM_CNT SPARE_CNT APPVOL_CNTDM NAME DEVICE TYPE PRIVLEN PUBLEN STATERV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRLRL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNKCO NAME CACHEVOL KSTATE STATEVT NAME RVG KSTATE STATE NVOLUMEV NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPEPL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODESD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODESV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODESC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODEDC NAME PARENTVOL LOGVOLSP NAME SNAPVOL DCOEX NAME ASSOC VC PERMS MODE STATESR NAME KSTATE

dg nfsdg default default 51000 1208758891.17.dbbl01

dm disk01 c1t0d0s2 auto 65536 286632832 -dm disk02 c1t1d0s2 auto 65536 286632832 -

v nfsvol - ENABLED ACTIVE 2097152 SELECT - fsgenpl nfsvol-01 nfsvol ENABLED ACTIVE 2097152 CONCAT - RWsd disk01-01 nfsvol-01 disk01 0 2097152 0 c1t0d0 ENApl nfsvol-02 nfsvol ENABLED ACTIVE 2097152 CONCAT - RWsd disk02-01 nfsvol-02 disk02 0 2097152 0 c1t1d0 ENA

bash-3.00# scconf -a -D type=vxvm,name=nfsdg,nodelist= dddl01:dbbl02,preferenced =true,failback=disabled

bash-3.00# scstat -D

-- Device Group Servers --

Device Group Primary Secondary ------------ ------- --------- Device group servers: webdg dbbl02 dbbl01 Device group servers: nfsdg dbbl01 dbbl02

-- Device Group Status --

Device Group Status ------------ ------ Device group status: webdg Online Device group status: nfsdg Online

-- Multi-owner Device Groups --

Device Group Online Status ------------ -------------

bash-3.00# mkfs -F vxfs /dev/vx/rdsk/nfsdg/nfsvol

bash-3.00# vxprint -htDisk group: nfsdg

DG NAME NCONFIG NLOG MINORS GROUP-IDST NAME STATE DM_CNT SPARE_CNT APPVOL_CNTDM NAME DEVICE TYPE PRIVLEN PUBLEN STATERV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRLRL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNKCO NAME CACHEVOL KSTATE STATE

VT NAME RVG KSTATE STATE NVOLUMEV NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPEPL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODESD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODESV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODESC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODEDC NAME PARENTVOL LOGVOLSP NAME SNAPVOL DCOEX NAME ASSOC VC PERMS MODE STATESR NAME KSTATE

dg nfsdg default default 1000 1208758891.17.dbbl01


v nfsvol - ENABLED ACTIVE 2097152 SELECT - fsgenpl nfsvol-01 nfsvol ENABLED ACTIVE 2097152 CONCAT - RWsd disk01-01 nfsvol-01 disk01 0 2097152 0 c1t0d0 ENApl nfsvol-02 nfsvol ENABLED ACTIVE 2097152 CONCAT - RWsd disk02-01 nfsvol-02 disk02 0 2097152 0 c1t1d0 ENA

bash-3.00# scswitch -z -D nfsdg -h dbbl01bash-3.00# scswitch -z -D nfsdg -h dbbl02bash-3.00# scstat -D







bash-3.00# vxprint -htDisk group: webdg

DG NAME NCONFIG NLOG MINORS GROUP-IDST NAME STATE DM_CNT SPARE_CNT APPVOL_CNTDM NAME DEVICE TYPE PRIVLEN PUBLEN STATERV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRLRL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNKCO NAME CACHEVOL KSTATE STATEVT NAME RVG KSTATE STATE NVOLUMEV NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPEPL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODESD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODESV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODESC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODEDC NAME PARENTVOL LOGVOLSP NAME SNAPVOL DCOEX NAME ASSOC VC PERMS MODE STATESR NAME KSTATE

dg webdg default default 51000 1208759074.17.dbbl02


v webvol - ENABLED ACTIVE 2097152 SELECT - fsgenpl webvol-01 webvol ENABLED ACTIVE 2097152 CONCAT - RWsd disk01-01 webvol-01 disk01 0 2097152 0 c1t3d0 ENApl webvol-02 webvol ENABLED ACTIVE 2097152 CONCAT - RWsd disk02-01 webvol-02 disk02 0 2097152 0 c1t4d0 ENA

bash-3.00# vxdisk listDEVICE TYPE DISK GROUP STATUSc1t0d0s2 auto:cdsdisk disk01 nfsdg onlinec1t1d0s2 auto:cdsdisk disk02 nfsdg onlinec1t2d0s2 auto:none - - online invalidc1t3d0s2 auto:cdsdisk disk01 webdg onlinec1t4d0s2 auto:cdsdisk disk02 webdg onlinec1t5d0s2 auto:none - - online invalidc1t8d0s2 auto:none - - online invalidc1t9d0s2 auto:none - - online invalidc2t0d0s2 auto:none - - online invalid

c2t1d0s2 auto:none - - online invalidbash-3.00# scstat -D







bash-3.00# scswitch -z -D webdg -h dbbl02bash-3.00# scswitch -z -D nfsdg -h dbbl01bash-3.00# scconf -a -D type=vxvm,name=nfsdg,nodelist=dbbl01:dbbl02,preferenced==true,failback=disabled

bash-3.00# mkfs -F vxfs /dev/vx/rdsk/nfsdg/nfsvol version 7 layout 2097152 sectors, 1048576 blocks of size 1024, log size 16384 blocks largefiles supportedbash-3.00# mkdir /global/nfsbash-3.00# mkdir /global/webbash-3.00# bash-3.00# mount -F vxfs global /dev/vx/dsk/nfsdg/nfsvol /global/nfsbash-3.00# mount -F vxfs global /dev/vx/dsk/webdg/webvol /global/web(mount from Node02)

bash-3.00# df -kFilesystem kbytes used avail capacity Mounted on/dev/dsk/c2t0d0s0 50425263 12571911 37349100 26% //devices 0 0 0 0% /devicesctfs 0 0 0 0% /system/contractproc 0 0 0 0% /procmnttab 0 0 0 0% /etc/mnttabswap 10952200 1528 10950672 1% /etc/svc/volatileobjfs 0 0 0 0% /system/objectfd 0 0 0 0% /dev/fdswap 10951080 408 10950672 1% /tmpswap 10950792 120 10950672 1% /var/run

swap 10950672 0 10950672 0% /dev/vx/dmpswap 10950672 0 10950672 0% /dev/vx/rdmp/dev/dsk/c2t0d0s3 2032943 2065 1969890 1% /export/home/dev/did/dsk/d10s4 5045478 7699 4987325 1% /global/.devices/node@1/dev/did/dsk/d13s4 5045478 7699 4987325 1% /global/.devices/node@2/dev/vx/dsk/nfsdg/nfsvol 1048576 17750 966407 2% /global/nfs/dev/vx/dsk/webdg/webvol 1048576 17750 966407 2% /global/web

bash-3.00# vi /etc/vfstab

bash-3.00# cat /etc/vfstab #device device mount FS fsck mount mount#to mount to fsck point type pass at boot

options#fd - /dev/fd fd - no -/proc - /proc proc - no -/dev/dsk/c2t0d0s1 - - swap - no -/dev/dsk/c2t0d0s0 /dev/rdsk/c2t0d0s0 / ufs 1 no -/dev/dsk/c2t0d0s3 /dev/rdsk/c2t0d0s3 /export/home ufs 2

yes -/dev/vx/dsk/nfsdg/nfsvol /dev/vx/rdsk/nfsdg/nfsvol /global/nfs

vxfs 2 yes global/dev/vx/dsk/webdg/webvol /dev/vx/rdsk/webdg/webvol /global/web

vxfs 2 yes global#/dev/dsk/c2t0d0s4 /dev/rdsk/c2t0d0s4 /globaldevices ufs

2 yes -/devices - /devices devfs - no -ctfs - /system/contract ctfs - no -objfs - /system/object objfs - no -swap - /tmp tmpfs - yes -/dev/did/dsk/d10s4 /dev/did/rdsk/d10s4 /global/.devices/node@1 ufs 2 no globalbash-3.00# scstat -D







bash-3.00# scstat -D







Documents

Cluster Quick Installation