SUN CLUSTER 1.

Install the Sun Java Web Console Software:
bash-3.00# cd /cdrom/cdrom0 bash-3.00# ls administration_svr sun_cluster sun_cluster_agents sunwebconsole bash-3.00# cd sunwebconsole/ bash-3.00# ls setup SunOS-5.9-sparc SUNWj3man.pkg SUNWjhdoc.pkg smcwebserver.1m SUNWbzip.pkg SUNWj3rt.pkg SUNWjhrt.pkg smreg.1m SUNWj3cfg.pkg SUNWjato.pkg SUNWmcon.pkg SunOS-5.10-sparc SUNWj3dev.pkg SUNWjhdem.pkg SUNWmctag.pkg SunOS-5.8-sparc SUNWj3dmo.pkg SUNWjhdev.pkg SUNWtcatu.pkg bash-3.00# ./setup -------------------------------------------------------------------------------------------------------------------------------------

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

3. Install the Sun Cluster: (For “Node 01”)
bash-3.00# cd .. bash-3.00# ls administration_svr sun_cluster sun_cluster_agents sunwebconsole bash-3.00# cd sun_cluster bash-3.00# ls Copyright LICENSEREADME Solaris_10 Solaris_9 index.html README Solaris_8 bash-3.00# cd Solaris_10/ bash-3.00# ls Packages Tools bash-3.00# cd Tools/ bash-3.00# ls defaults dot.release lib locale scinstall bash-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 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

server

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 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 <<<

this

done SUNWscgds.done SUNWscmasar.....done SUNWscva.done SUNWmdmr.done SUNWhsc......done SUNWkscspmu..done SUNWscvm..done SUNWhscspmu....done SUNWcsc.done SUNWdscspmu.done SUNWscsckr.....done SUNWjsc.... Is it okay to continue (yes/no) [yes]? ** Installing SunCluster 3.done SUNWscsam.done SUNWdscspm..done SUNWkscspm..done SUNWjscspm...done SUNWscsal...done SUNWmdmu..done SUNWscspmr...done SUNWescspm.......done SUNWscu..done SUNWfsc.done SUNWscspmu.done SUNWcscspmu..done SUNWscnmr......done SUNWscrsm.done SUNWscmasau..done SUNWcscspm.....1 framework ** SUNWscr...done SUNWfscspmu..done SUNWscman...done SUNWjscspmu..done SUNWescspmu..done SUNWksc.done SUNWjscman...done SUNWhscspm.....done SUNWdsc.done SUNWesc..done SUNWscspm....done Press Enter to continue: >>> Software Patch Installation <<< ..done SUNWfscspm.....done SUNWscscku..done SUNWscnmu.done SUNWscdev....Installation of the Sun Cluster framework software packages will take a few minutes to complete.....

Do you want scinstall to install patches for you (yes/no) [yes]? >>> Cluster Name <<< Each cluster has a name assigned to it. dbbl-clus n Press Enter to continue: >>> Cluster Nodes <<< This Sun Cluster release supports a total of up to 16 nodes. dbbl01: Starting single-node checks. Patches can be downloaded into the patch directory either as individual patches or as patches grouped together into one or more tar. Refer to the patchadd(1M) man page for more information regarding patch list files. dbbl01: Single-node checks finished. jar. only those patches listed in the patch list file are installed. What is the name of the cluster you want to establish? >>> Check <<< This step allows you to run sccheck(1M) to verify that certain basic hardware and software pre-configuration requirements have been met. all patches found in the directory will be installed. Please list the names of the other nodes planned for the initial cluster configuration. Data gathering and report generation can take several minutes.If there are any Solaris or Sun Cluster patches that need to be added as part of this Sun Cluster installation.. depending on system configuration. All patches that need to be added must first be downloaded into a common patch directory. If a patch list file is provided in the patch directory. type Control-D: Node name (Control-D to finish): dbbl02 . 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. sccheck: sccheck: sccheck: sccheck: Requesting explorer data and node report from dbbl01. Each cluster name should be unique within the namespace of your enterprise. dbbl01: Explorer finished. When finished. or zip files. List one node name per line. Do you want to run sccheck (yes/no) [yes]? Running sccheck . Otherwise. scinstall can add them for you.. The name can be made up of any characters other than whitespace.

That is. 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. However. The default netmask is 255. But. you must configure all necessary encryption keys before any node will be allowed to join the cluster (see keyserv(1M). when there are greater than two nodes. This is generally considered adequate.0. you may need to select another address from the range of recommended private addresses (see RFC 1918 for details).16. DES authentication is available.Node name (Control-D to finish): ^D This is the complete list of nodes: dbbl01 dbbl02 Is it correct (yes/no) [yes]? >>> Authenticating Requests to Add Nodes <<< Once the first node establishes itself as a single node cluster. If you do select another network address. no cluster transport junctions are configured. If DES authentication is selected. 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. other nodes attempting to add themselves to the cluster configuration must be found on the list of nodes you just provided. publickey(4)). this interactive form of scinstall assumes that there will be exactly two cluster transport junctions. as long as it minimally masks all bits given in the network address. if this network address is already in use elsewhere within your enterprise.0. since nodes which are not physically connected to the private cluster interconnect will never be able to actually join the cluster. However.0.255. bear in mind that the Sun Cluster software requires that the rightmost two octets always be zero. You can select another netmask.0. . By default. nodes are not securely authenticated as they attempt to add themselves to the cluster configuration. You can modify this list using scconf(1M) or other tools once the cluster has been established.

No traffic was detected over a 10 second sample period. each adapter on a given node must be cabled to a different junction. or "switch". And. And. 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.. done Verification completed. For more information regarding port naming requirements. each port is assigned a name. refer to the scconf_transp_jct family of man pages (e. 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. The "dlpi" transport type will be set for this cluster..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. for Ethernet and Infiniband switches. you can choose to allow scinstall to assign a default name for you. Or. scconf_transp_jct_dolphinswitch(1M)).. . You can explicitly assign a name to each port. 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. Searching for any unexpected network traffic on "ce0" . These are the adapters which attach to the private cluster interconnect. Select the first cluster transport adapter: 1) 2) 3) 4) 5) 6) 7) 8) Option: bge1 bge2 bge3 ce0 ce1 ce2 ce3 Other 4 Will this be a dedicated cluster transport adapter (yes/no) [yes]? Adapter "ce0" is an Ethernet adapter. Name of the junction to which "ce0" is connected [switch1]? Each adapter is cabled to a particular port on a transport junction.g.

Is it okay to use this default (yes/no) [yes]? >>> Quorum Configuration <<< Every two-node cluster requires at least one quorum device.. If an already-mounted file system is used. The default is to use /globaldevices. scinstall will select and configure a shared SCSI quorum disk device for you. scinstall will set this up for you. If a raw disk partition is used. This file system or partition should be at least 512 MB in size. Searching for any unexpected network traffic on "ce1" . By default. a new file system will be created 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 screen allows you to disable the automatic selection and configuration of a quorum device. Since the "nodeID" is not assigned until scinstall is run. the file system must be empty.devices/node@<nodeID> before it can successfully participate as a cluster member. No traffic was detected over a 10 second sample period. ..Use the default port name for the "ce0" connection (yes/no) [yes]? Select the second cluster transport adapter: 1) 2) 3) 4) 5) 6) 7) 8) Option: bge1 bge2 bge3 ce0 ce1 ce2 ce3 Other 5 Will this be a dedicated cluster transport adapter (yes/no) [yes]? Adapter "ce1" is an Ethernet adapter. 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/. done Verification completed.

select the Help option from the menu. If this is an initial cluster install. For more information about the differences between the Typical and Custom installation methods. After sccheck(1M) passes. you will be asked to provide both the name of the cluster and the name of one of the nodes already in the cluster. it is qualified. there may only be a single node which has established itself in the new cluster.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. 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. Once the cluster framework software is installed. sccheck(1M) is run to test this machine for basic Sun Cluster pre-configuration requirements. 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. Then. you might need to select the Custom option if not all of the Typical defaults can be applied to your cluster. 4. you may be asked to provide certain cluster transport configuration information. If your storage was purchased with your cluster. However. For most clusters. a Typical installation is recommended. Please select from one of the following options: .

this "sponsor" node is typically the first node used to build the new cluster. Already established clusters can keep a list of hosts which are able to configure themselves as new cluster members.. done Cluster name "dbbl-clus" is correct. What is the name of the sponsoring node? >>> Cluster Name <<< Each cluster has a name assigned to it. What is the name of the cluster you want to join? Attempting to contact "dbbl01" . if the target cluster uses DES to authenticate new machines attempting to configure themselves as new cluster members. Is it okay to continue (yes/no) [yes]? ** Installing SunCluster 3. This machine should be in the join list of any cluster which it tries to join.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. the "sponsoring" node can be any node in that cluster. When configuring a new cluster. the necessary encryption keys must be configured before any attempt to join.. if the cluster is already established. A sanity check is performed to verify that the "sponsoring" node is a member of that cluster. However. you must identify the name of the cluster you are attempting to join. When adding a node to the cluster. Press Enter to continue: dbbl-clus dbbl01 . you may need to add it using scconf(1M) or other tools. it must identify a node in that cluster willing to "sponsor" its membership in the cluster.1 framework ** ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------>>> Sponsoring Node <<< For any machine to join a cluster. And. If the list does not include this machine.

.. Do you want to use autodiscovery (yes/no) [yes]? Probing .. The default is to use /globaldevices.. a new file system will be created for you.devices/node@<nodeID> before it can successfully participate as a cluster member. Press Enter to continue: 5.. autodiscovery is the best method for configuring the cluster transport.. 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.00# scdidadm –L (See the global devices) . The following connections were discovered: dbbl01:ce0 dbbl01:ce1 switch1 switch2 dbbl02:ce0 dbbl02:ce1 yes 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/.. Since the "nodeID" is not assigned until scinstall is run.. the file system must be empty. it will be necessary to reboot. scinstall will set this up for you. 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. If an already-mounted file system is used. The reboot will cause this machine to join the cluster for the first time.. Install the SC Quorum Devices: bash-3.>>> Autodiscovery of Cluster Transport <<< If you are using Ethernet or Infiniband adapters as the cluster transport adapters.. This file system or partition should be at least 512 MB in size. If a raw disk partition is used. 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..

Please refer to Sun Cluster documentation for detailed information on these supported quorum device topologies. Please do not proceed if any additional nodes have yet to join the cluster. certain initial cluster setup steps will be performed at this time. 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 . Is it okay to continue (yes/no) [yes]? Do you want to add any quorum devices (yes/no) [yes]? Following are supported Quorum Devices types in Sun Cluster. As such. This includes adding any necessary quorum devices.1 dbbl01:/dev/rdsk/c0t0d0 2 dbbl01:/dev/rdsk/c1t0d0 2 dbbl02:/dev/rdsk/c1t0d0 3 dbbl01:/dev/rdsk/c1t1d0 3 dbbl02:/dev/rdsk/c1t1d0 4 dbbl01:/dev/rdsk/c1t2d0 4 dbbl02:/dev/rdsk/c1t2d0 5 dbbl01:/dev/rdsk/c1t3d0 5 dbbl02:/dev/rdsk/c1t3d0 6 dbbl01:/dev/rdsk/c1t4d0 6 dbbl02:/dev/rdsk/c1t4d0 7 dbbl01:/dev/rdsk/c1t5d0 7 dbbl02:/dev/rdsk/c1t5d0 8 dbbl01:/dev/rdsk/c1t8d0 8 dbbl02:/dev/rdsk/c1t8d0 9 dbbl01:/dev/rdsk/c1t9d0 9 dbbl02:/dev/rdsk/c1t9d0 10 dbbl01:/dev/rdsk/c2t0d0 11 dbbl01:/dev/rdsk/c2t1d0 12 dbbl02:/dev/rdsk/c0t0d0 13 dbbl02:/dev/rdsk/c2t0d0 14 dbbl02:/dev/rdsk/c2t1d0 bash-3. then resetting both the quorum vote counts and the "installmode" property.00# scsetup /dev/did/rdsk/d1 /dev/did/rdsk/d2 /dev/did/rdsk/d2 /dev/did/rdsk/d3 /dev/did/rdsk/d3 /dev/did/rdsk/d4 /dev/did/rdsk/d4 /dev/did/rdsk/d5 /dev/did/rdsk/d5 /dev/did/rdsk/d6 /dev/did/rdsk/d6 /dev/did/rdsk/d7 /dev/did/rdsk/d7 /dev/did/rdsk/d8 /dev/did/rdsk/d8 /dev/did/rdsk/d9 /dev/did/rdsk/d9 /dev/did/rdsk/d10 /dev/did/rdsk/d11 /dev/did/rdsk/d12 /dev/did/rdsk/d13 /dev/did/rdsk/d14 >>> Initial Cluster Setup <<< This program has detected that the cluster "installmode" attribute is still enabled.

clusters. Cluster initialization is complete. Is it okay to continue (yes/no) [yes]? 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. Is it okay to reset "installmode" (yes/no) [yes]? scconf -c -q reset scconf -a -T node=. quorum devices can always be added to the cluster using the regular menu options. However. Type ENTER to proceed to the main menu: *** Main Menu *** Please select from one of the following options: 1) 2) 3) 4) 5) 6) 7) 8) Quorum Resource groups Data Services Cluster interconnect Device groups and volumes Private hostnames New nodes Other cluster properties ?) Help with menu options q) Quit . see the Sun Cluster documentation. Press Enter to continue: 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. You can use a disk containing user data or one that is a member of a device group as a quorum device. clusters with more than two nodes require that SCSI3 PGR disks be used for all disks with more than two node-to-disk paths. Resetting this property fully activates quorum settings and is necessary for the normal and safe operation of the cluster. However. For more information on supported quorum device topologies.

1/sd@5.-------. c1t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e.0 1.600000/scsi@2.0 Specify disk (enter its number): 2 selecting c1t2d0 [disk formatted] .600000/scsi@2. c1t5d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e. c1t4d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e.-------..Quorum Votes by Node -Node Name --------dbbl01 dbbl02 Present Possible Status ------.Option: q bash-3.-----1 1 Online Device votes: bash-3.Quorum Summary -Quorum votes possible: Quorum votes needed: Quorum votes present: -.1/sd@9.0 6.1/sd@8.00# scstat -q -.1/sd@0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e. c1t8d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e.0 8.600000/scsi@2.600000/scsi@2.0 2.600000/scsi@2.0 7.600000/scsi@2/sd@0..0 5.600000/scsi@2. c2t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@1c.-----1 1 Online 1 1 Online 3 2 3 Node votes: Node votes: -.600000/scsi@2.1/sd@2. c1t9d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e.0 3. c2t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@1c.00# format Searching for disks.600000/scsi@2.600000/scsi@2/sd@1.Quorum Votes by Device -Device Name ----------/dev/did/rdsk/d4s2 Present Possible Status ------.1/sd@3.0 9.0 4. c1t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e. c1t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@1e.1/sd@4.done AVAILABLE DISK SELECTIONS: 0.1/sd@1.

71GB 0 0 0 136.255.14086 0 0 0 26 .19MB 136.partition> Current partition table (original): Total disk cylinders available: 14087 + 2 (reserved cylinders) Part Tag 0 root 264576 1 swap 264576 2 backup 286698624 3 unassigned 0 4 unassigned 0 5 unassigned 0 6 usr 286169472 7 unassigned 0 partition> q format> q bash-3. .14086 0 .16.0.46GB 0 Blocks (13/0/0) (13/0/0) (14087/0/0) (0/0/0) (0/0/0) (0/0/0) (14061/0/0) (0/0/0) 0 .0 Cluster private netmask: 255.0 Cluster new node authentication: unix Cluster new node list: <.0.19MB 129.Exclude all nodes> Cluster transport heart beat timeout: 10000 Cluster transport heart beat quantum: 1000 Cluster nodes: dbbl01 dbbl02 Cluster node name: Node ID: Node enabled: Node private hostname: Node quorum vote count: Node reservation key: Node transport adapters: Node transport adapter: Adapter enabled: Adapter transport type: Adapter property: Adapter property: Adapter property: Adapter property: dlpi_heartbeat_timeout=10000 Adapter property: dlpi_heartbeat_quantum=1000 dbbl01 1 yes clusternode1-priv 1 0x480AE57500000001 ce0 ce1 ce0 yes dlpi device_name=ce device_instance=0 lazy_free=1 Flag wm wu wu wm wm wm wm wm Cylinders 0 12 13 25 Size 129.00# scconf -p | more Cluster name: dbbl-clus Cluster ID: 0x480AE575 Cluster install mode: disabled (After install the quorum it automatically be disabled) Cluster private net: 172.

View the owner Node of the Quorum Device: bash-3.1 0 0 yes dbbl02 2 yes clusternode2-priv 1 0x480AE57500000002 ce0 ce1 ce0 yes dlpi device_name=ce device_instance=0 lazy_free=1 6.129 Adapter port names: Adapter port: Port enabled: Node transport adapter: Adapter enabled: Adapter transport type: Adapter property: Adapter property: Adapter property: Adapter property: dlpi_heartbeat_timeout=10000 Adapter property: dlpi_heartbeat_quantum=1000 Adapter property: Adapter property: Adapter property: netmask=255.255.255.255.Adapter property: Adapter property: Adapter property: netmask=255.0./cmm_ctl -g *** Current Cluster State *** Local Node Id : 2 Highest Node Id : 2 Current reconfiguration seqnum : 6 .00# .00# cd /usr/cluster/lib/sc bash-3.16.16.1.128 Adapter property: Adapter port names: Adapter port: Port enabled: Cluster node name: Node ID: Node enabled: Node private hostname: Node quorum vote count: Node reservation key: Node transport adapters: Node transport adapter: Adapter enabled: Adapter transport type: Adapter property: Adapter property: Adapter property: nw_bandwidth=80 bandwidth=70 0 0 yes ce1 yes dlpi device_name=ce device_instance=1 lazy_free=1 nw_bandwidth=80 bandwidth=70 ip_address=172.128 Adapter property: ip_address=172.255.

00# cd es345/ bash-3.gz es345~ar.gz bash-3.sto es345~a2.gz suncl~ar.gz oracl~ar.gz es345~a1.00# gunzip verit~ar.gz bash-3. 0x480ae57500000002 *** Quorum device info *** Quorum device 1 : global device name = '/dev/did/rdsk/d4s2'.00# ls cluster_patch es345 Solaris_sparc bash-3. nodes with configured paths = 0x3. : 13 *** Incarnation Numbers of Current Cluster Members *** Node 1 Node 2 : 1208673844 : 1208675464 *** Cluster Configuration Information *** Max Nodes Supported : 64 Node Fenceoff Timeout : 300 seconds Boot Delay : 60 seconds Node Halt Timeout : 5 seconds Failfast grace time : 10 seconds Failfast panic delay : 30 seconds Orb Stop Timeout : 30 seconds Orb Return Timeout : 30 seconds Orb Abort Timeout : 30 seconds Orb Step Timeout : 120 seconds *** Cluster Quorum Information *** Total configured votes : 3 Current cluster votes : 3 Votes needed for quorum : 2 *** Node quorum info *** Node 1 Node 2 : state = UP.gz verit~ar es345~a1.gz es345~ar.00# cd /dump bash-3. Veritas Volume Manager configuration on Cluster (“Node01”): bash-3. state = ONLINE. reservation_key = votes_configured = 1. reservation_key = : state = UP.00# ls _ds. reservation owner = node 1 7.00# file verit~ar .gz bash-3.gz verit~ar.gz suncl~ar. votes_configured = 1.Max reconfiguration step CMM is in the end state. 0x480ae57500000001 votes_configured = 1.gz oracl~ar.sto es345~a2.00# ls _ds.

tar.00# pkgadd –d .00# cd ses bash-3.gz es345~a1.1/veritas/4.00# cd 4.00# ls authentication_service storage_foundation cluster_management_console storage_foundation_cluster_file_system cluster_server storage_foundation_for_db2 cluster_server_agents storage_foundation_for_oracle file_system storage_foundation_for_oracle_rac getting_started.sto es345~a2.0 README bash-3.0_sunw/pkgs bash-3.00# cd software/ bash-3.gz |tar xvf – bash-3.0_sunw.00# ls software bash-3.00# ls VRTSalloc VRTSfppm VRTSfspro VRTSobgui VRTSvmdoc VRTSvxfs VRTSap VRTSfsdoc VRTSmuob VRTStep VRTSvmman VRTSvxvm VRTSddlpr VRTSfsman VRTSob VRTSvlic VRTSvmpro bash-3.00# cd pkgs/ bash-3.1/veritas bash-3.00# cd vxSF5.00# pwd /dump_3.pdf storage_foundation_for_sybase gnu volume_manager installer volume_replicator .00# ls README storage_solutions_4. --------------------------------------------------------------------------------------------------------------------------------------------bash-3.gz opt suncl~ar.gz es345~ar.gz oracl~ar.00# ls README storage_solutions_4.00# ls copyright patches release_notes support docs pkgs scripts veritas_enabled bash-3.gz storage_solutions_4.00# ls 4.00# cd storage_solutions_4.0_sunw bash-3.0_sunw.0/storage_solutions_4.0_sunw.00# cd opt bash-3.gz bash-3.0_sunw bash-3.00# tar xvf verit~ar bash-3.00# ls _ds.verit~ar: USTAR tar archive bash-3.0/ bash-3.tar.00# ls vxSF5.0 bash-3.00# cd /dump_3.0/ bash-3.00# ls ses bash-3.gz verit~ar bash-3.tar.00# gzcat storage_solutions_4.

00# ls copyright patches scripts veritas_enabled docs pkgs tools installsf release_notes uninstallsf bash-3.tar.tar.00# cd s torage_foundation bash-3.tar.00# ls copyright patches scripts veritas_enabled docs pkgs tools installsf release_notes uninstallsf bash-3.tar.gz VRTSfas..gz VRTScssim.gz VRTSvcsag.tar.tar.tar.tar.tar.tar.gz VRTSfsdoc.tar.gz VRTSobgui.tar.tar.gz VRTSpbx.gz VRTSvrw.00# cd .tar..tar.gz VRTSdcp.gz VRTSvail. bash-3.gz VRTSvmpro.tar.gz VRTSvmman.tar.tar.00# ls copyright patches scripts veritas_enabled .gz VRTSvxvm.tar.tar.gz VRTSllt.gz VRTScmccc.gz VRTSvrdoc.tar.gz VRTSvdid.00# ls info VRTSddlpr.tar.tar.gz VRTSdsm.gz VRTSvailadmin VRTSvxfs.tar.gz VRTSfssdk.gz VRTSmapro.tar.gz VRTScutil.tar.tar.gz VRTSobweb.tar.gz VRTSob.gz VRTSfasdc.gz VRTSvxfen. bash-3.tar.tar.tar.tar.tar.gz VRTSacclib.tar.tar.gz VRTSvrpro.gz VRTSaa.tar.gz VRTSalloc.gz VRTSvcs.00# cd pkgs/ bash-3.gz VRTSvcsvr.perl windows bash-3.gz VRTSgcsha.gz VRTSccg.gz VRTSmh.tar.gz VRTSfasag.gz SYMClma.gz VRTSvcsmg.tar.gz VRTSweb.tar.tar.tar.gz VRTSvxmsa.gz VRTSperl.tar.gz VRTSfspro.tar.gz VRTScs.gz VRTSat.gz VRTSdsa.gz VRTSfsmnd.gz VRTSobc33.tar.tar.gz VRTSdcli.gz VRTSvmdoc.gz VRTSjre15.gz VRTSvcsmn.tar.gz VRTScscw.gz VRTSgab.pdf storage_foundation_for_sybase gnu volume_manager installer volume_replicator perl windows bash-3.gz VRTScscm.tar.00# cd .tar.tar.tar.gz VRTSgcspr.tar.gz VRTSspt.tar.gz VRTSvlic.gz VRTScweb.tar.tar.tar.tar.00# cd vo lume_manager/ bash-3.gz VRTSsmf.gz VRTSgapms.tar.tar.gz VRTSicsco.gz VRTSvcsdc.gz VRTSfsman.tar.gz VRTScsdoc.tar.tar.tar.tar.00# ls authentication_service storage_foundation cluster_management_console storage_foundation_cluster_file_system cluster_server storage_foundation_for_db2 cluster_server_agents storage_foundation_for_oracle file_system storage_foundation_for_oracle_rac getting_started.gz VRTSfsweb.tar.gz VRTSjre.gz VRTSvsvc.gz VRTSvmweb.tar.tar.tar.gz bash-3.gz VRTScmcs.tar.tar.

bash-3.tar.gz bash-3.gz VRTSddlpr.0 Installation Program Copyright (c) 2006 Symantec Corporation.tar.gz VRTSmh.S.tar.7202.gz VRTSvsvc./installsf –rsh (rsh to install other Node02) Veritas Storage Foundation 5.gz VRTSgcsha. bash-3.tar.tar.gz VRTSvmdoc.tar. and other countries.00# ls copyright patches scripts veritas_enabled docs pkgs tools installsf release_notes uninstallsf bash-3.tar.tar.tar.00# cd p kgs/ bash-3.gz VRTSjre15.gz VRTSfspro.gz VRTSdbms3.tar.tar.tar.tar.gz VRTSvrw.00# ls authentication_service storage_foundation cluster_management_console storage_foundation_cluster_file_system cluster_server storage_foundation_for_db2 cluster_server_agents storage_foundation_for_oracle file_system storage_foundation_for_oracle_rac getting_started.tar.tar.tar.gz VRTSob.gz VRTScs.tar.gz VRTSccg. the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.tar.tar. Other names may be trademarks of their respective owners.tar.gz VRTSdcli.tar.tar.gz VRTSweb.tar.gz VRTScweb.tar.gz VRTSobc33.gz VRTSvrdoc.gz VRTSperl.gz VRTSvmpro.tar.tar.gz VRTSvdid.00# ls copyright patches scripts veritas_enabled docs pkgs tools installvm release_notes uninstallvm bash-3.tar.tar..gz VRTSaa.00# ls info VRTSdcp.tar.00# cd .gz VRTSspt.pdf storage_foundation_for_sybase gnu volume_manager installer volume_replicator perl windows bash-3.tar.gz VRTSvrpro.212 and DFARS Section 227.gz VRTSicsco.gz VRTSsmf.tar.tar.gz VRTSat.gz VRTSvlic.tar.00# . All rights reserved.gz VRTSvxvm.tar.tar.gz VRTSvmman.docs pkgs tools installvm release_notes uninstallvm bash-3.gz VRTSdsa.tar.gz SYMClma.tar.tar. The Licensed Software and Documentation are deemed to be "commercial computer software" and "commercial computer software documentation" as defined in FAR Sections 12.00# cd ..tar. .gz VRTSjre.tar.gz VRTSobgui.gz VRTSdsm.gz VRTSobweb.gz VRTSalloc. Logs for installsf are being created in /var/tmp/installsf-kSJIUD.gz VRTSvcsvr.00# cd st orage_foundation bash-3.gz VRTSpbx.gz VRTScsdoc.gz VRTSgcspr. Symantec.tar.gz VRTSvmweb.tar.

0 Installation Program SF can be installed without optional packages to conserve disk space.8. not installed Checking SF installation on dbbl02 .q..q] (n) IRPH-TDRO-PWV8-Y774-V94M-TURC successfully registered on dbbl02 Demo SF license registered on dbbl02 Do you want to enter another license key for dbbl02? [y.0 Installation Program Checking system licensing Installing licensing packages SF is not licensed on dbbl01 Enter a SF license key for dbbl01: IRPH-TDRO-PWV8-Y774-V94M-TURC IRPH-TDRO-PWV8-Y774-V94M-TURC successfully registered on dbbl01 Demo SF license registered on dbbl01 Do you want to enter another license key for dbbl01? [y.... not installed Veritas Storage Foundation 5..?] (2) Veritas Storage Foundation 5......10 Checking SF installation on dbbl01 ....q] (n) Veritas Storage Foundation 5.....1051 MB required Select the packages to be installed on all systems? [1-2. SunOS 5............ Required Veritas Storage Foundation packages ..n................8 Redistribution VRTSvlic Veritas Licensing VRTSicsco Symantec Common Infrastructure VRTSpbx Symantec Private Branch Exchange VRTSsmf Symantec Service Management Framework VRTSat Symantec Product Authentication Service VRTSobc33 Veritas Enterprise Administrator Core Service VRTSob Veritas Enterprise Administrator Service VRTSobgui Veritas Enterprise Administrator VRTSccg Veritas Enterprise Administrator Central Control Grid VRTSmh Veritas Storage Foundation Managed Host by Symantec ........0 Installation Program Checking installed packages on dbbl01 Checking installed packages on dbbl02 Veritas Storage Foundation 5.....0 Installation Program The following SF packages will be installed: VRTSperl Veritas Perl 5.n...1023 MB required All Veritas Storage Foundation packages ......Enter the system names separated by spaces on which to install SF: dbbl01 dbbl02 Initial system check: Checking rsh communication with dbbl02 .

... None It is possible to install SF packages without performing configuration. None Checking for any AP driver issues on dbbl02 .......continued: VRTSdcli Veritas Distributed Command Line Interface VRTSalloc Veritas Volume Manager Intelligent Storage Provisioning VRTSvmpro Veritas Volume Manager Management Services Provider VRTSvsvc Veritas Volume Server and Client Provider VRTSvdid Veritas Device Identification API VRTSddlpr Veritas Device Discovery Layer Services Provider VRTSvrpro Veritas Volume Replicator Client Extension and Provider for Veritas Enterprise Administrator VRTSvcsvr Veritas Cluster Server Agents for VVR VRTSjre Veritas Java Runtime Environment Redistribution VRTSjre15 Veritas Java Runtime Environment Redistribution VRTSweb Veritas Java Web Server VRTSvrw Veritas Volume Replicator Web Console VRTSvrdoc Veritas Volume Replicator Documentation VRTSvxfs Veritas File System VRTSfsman Veritas File System Manual Pages VRTSfsdoc Veritas File System Documentation VRTSfssdk Veritas File System Software Developer Kit VRTSfsmnd Veritas File System Software Developer Kit Manual Pages VRTSvail Veritas Array Integration Layer VRTSfas Veritas FlashSnap Agent for Symmetrix Press [Return] to continue: .. Application Libraries VRTSgapms Veritas Generic Array Plugin VRTSmapro Veritas Storage Foundation GUI for Mapping Press [Return] to continue: Checking for any AP driver issues on dbbl01 ... you can either do so manually or run the installsf -configure command..VRTSaa VRTSspt SYMClma VRTSvxvm VRTSdsa VRTSfspro VRTSvmman VRTSvmdoc Veritas Enterprise Administrator Action Agent Veritas Software Support Tools Symantec License Inventory Agent Veritas Volume Manager Binaries Veritas Datacenter Storage Agent Veritas File System Management Services Provider Veritas Volume Manager Manual Pages Veritas Volume Manager Documentation Press [Return] to continue: ..... It is optional to configure SF now....n..................continued: VRTSfasdc Veritas FlashSnap Agent for Symmetrix Documentation VRTSvxmsa Veritas Mapping Service.0 Installation Program Installation completed successfully on all systems ..... Are you ready to configure SF? [y.... If you choose to configure SF later..q] (y) Veritas Storage Foundation 5..

00# vxdisk list DEVICE TYPE DISK c1t0d0s2 auto:cdsdisk c1t1d0s2 auto:cdsdisk c1t2d0s2 auto:none c1t3d0s2 auto:none c1t4d0s2 auto:none c1t5d0s2 auto:none c1t8d0s2 auto:none c1t9d0s2 auto:none c2t0d0s2 auto:none c2t1d0s2 auto:none - GROUP - STATUS online online online online online online online online online online invalid invalid invalid invalid invalid invalid invalid invalid bash-3.q. It allows one to reference disks using a symbolic name that is more meaningful than the operating system's normal device access name.The enclosure-based naming scheme is a feature of Veritas Volume Manager. This symbolic name is typically derived from the array name.?] (n) Veritas Storage Foundation 5.00# vxdisksetup -i c1t0d0 c1t1d0 bash-3. Do you want to set up the enclosure-based naming scheme? [y.00# vxdg init nfsdg disk01=c1t0d0 disk02=c1t1d0 bash-3.n.00# vxdisk list DEVICE TYPE c1t0d0s2 auto:cdsdisk c1t1d0s2 auto:cdsdisk c1t2d0s2 auto:none c1t3d0s2 auto:none c1t4d0s2 auto:none c1t5d0s2 auto:none c1t8d0s2 auto:none c1t9d0s2 auto:none DISK disk01 disk02 - GROUP nfsdg nfsdg - STATUS online online online online online online online online invalid invalid invalid invalid invalid invalid .00# vxdisk list DEVICE TYPE c1t0d0s2 auto:none c1t1d0s2 auto:none c1t2d0s2 auto:none c1t3d0s2 auto:none c1t4d0s2 auto:none c1t5d0s2 auto:none c1t8d0s2 auto:none c1t9d0s2 auto:none c2t0d0s2 auto:none c2t1d0s2 auto:none DISK GROUP STATUS online online online online online online online online online online invalid invalid invalid invalid invalid invalid invalid invalid invalid invalid bash-3. Create the Disk Group: bash-3. Such commands 8.0 Installation Program Veritas Volume Manager default disk group name configuration: Many Veritas Volume Manager commands affect the contents or configuration of a disk group.

00# vxdisk -o alldgs list DEVICE TYPE DISK GROUP c1t0d0s2 auto:cdsdisk disk01 nfsdg c1t1d0s2 auto:cdsdisk disk02 nfsdg c1t2d0s2 auto:none c1t3d0s2 auto:cdsdisk (webdg) c1t4d0s2 auto:cdsdisk (webdg) c1t5d0s2 auto:none c1t8d0s2 auto:none c1t9d0s2 auto:none c2t0d0s2 auto:none c2t1d0s2 auto:none - STATUS online online online online online online online online online online invalid invalid invalid invalid invalid invalid bash-3.nolog alloc=disk01 disk02 bash-3.00# vxprint -ht Disk group: nfsdg DG NAME ST NAME DM NAME RV NAME RL NAME REM_RLNK CO NAME VT NAME V NAME PREFPLEX PL NAME NCOL/WID SD NAME DEVICE SV NAME MODE SC NAME DEVICE DC NAME SP NAME NCONFIG STATE DEVICE RLINK_CNT RVG CACHEVOL RVG RVG/VSET/CO VOLUME PLEX PLEX MODE PLEX PARENTVOL SNAPVOL NLOG DM_CNT TYPE KSTATE KSTATE KSTATE KSTATE KSTATE KSTATE DISK VOLNAME CACHE LOGVOL DCO MINORS GROUP-ID SPARE_CNT PRIVLEN PUBLEN STATE PRIMARY STATE REM_HOST STATE STATE STATE STATE NVOLUME LENGTH LENGTH APPVOL_CNT STATE DATAVOLS SRL REM_DG UTYPE MODE MODE READPOL LAYOUT [COL/]OFF [COL/]OFF AM/NM [COL/]OFF DISKOFFS LENGTH NVOLLAYR LENGTH DISKOFFS LENGTH .c2t0d0s2 c2t1d0s2 auto:none auto:none - GROUP nfsdg nfsdg - online invalid online invalid STATUS online online online online online online online online online online bash-3.00# vxassist -g nfsdg make nfsvol 1g layout-mirr=mirror.00# vxdisk -o alldgs list DEVICE TYPE DISK c1t0d0s2 auto:cdsdisk disk01 c1t1d0s2 auto:cdsdisk disk02 c1t2d0s2 auto:none c1t3d0s2 auto:none c1t4d0s2 auto:none c1t5d0s2 auto:none c1t8d0s2 auto:none c1t9d0s2 auto:none c2t0d0s2 auto:none c2t1d0s2 auto:none - invalid invalid invalid invalid invalid invalid invalid invalid (After creating the other node disk group) bash-3.

nodelist= dddl01:dbbl02.Device Group Servers -Secondary --------Device group servers: Device group servers: -.00# scconf -a -D type=vxvm.00# vxprint -ht Disk group: nfsdg DG NAME NCONFIG NLOG MINORS GROUP-ID .Multi-owner Device Groups -Device Group -----------Online Status ------------- bash-3.failback=disabled bash-3.00# scstat -D -.00# mkfs -F vxfs /dev/vx/rdsk/nfsdg/nfsvol bash-3.EX NAME STATE SR NAME dg nfsdg dm disk01 dm disk02 v nfsvol fsgen pl nfsvol-01 RW sd disk01-01 c1t0d0 ENA pl nfsvol-02 RW sd disk02-01 c1t1d0 ENA ASSOC KSTATE default c1t0d0s2 c1t1d0s2 nfsvol nfsvol-01 nfsvol nfsvol-02 VC PERMS MODE default auto auto ENABLED ENABLED disk01 ENABLED disk02 51000 65536 65536 ACTIVE ACTIVE 0 ACTIVE 0 1208758891.Device Group Status -Device Group -----------webdg nfsdg Status -----Online Online Device Group -----------webdg nfsdg Primary ------dbbl02 dbbl01 dbbl01 dbbl02 Device group status: Device group status: -.preferenced =true.17.name=nfsdg.dbbl01 286632832 286632832 2097152 2097152 2097152 2097152 2097152 SELECT CONCAT 0 CONCAT 0 - bash-3.

00# scswitch -z -D nfsdg -h dbbl02 bash-3.00# scstat -D -.Device Group Status -Device Group -----------Status ----------------webdg nfsdg Primary ------dbbl02 dbbl02 dbbl01 dbbl01 .17.00# scswitch -z -D nfsdg -h dbbl01 bash-3.Device Group Servers -Device Group Secondary --------Device group servers: Device group servers: -.ST NAME DM NAME RV NAME RL NAME REM_RLNK CO NAME VT NAME V NAME PREFPLEX PL NAME NCOL/WID SD NAME DEVICE SV NAME MODE SC NAME DEVICE DC NAME SP NAME EX NAME STATE SR NAME dg nfsdg dm disk01 dm disk02 STATE DEVICE RLINK_CNT RVG CACHEVOL RVG RVG/VSET/CO UTYPE MODE MODE VOLUME PLEX PLEX PLEX MODE PARENTVOL SNAPVOL ASSOC KSTATE default c1t0d0s2 c1t1d0s2 nfsvol nfsvol-01 nfsvol nfsvol-02 DM_CNT TYPE KSTATE KSTATE KSTATE KSTATE KSTATE KSTATE DISK VOLNAME CACHE LOGVOL DCO VC SPARE_CNT PRIVLEN PUBLEN STATE PRIMARY STATE REM_HOST STATE STATE STATE STATE NVOLUME LENGTH LENGTH APPVOL_CNT STATE DATAVOLS SRL REM_DG READPOL LAYOUT [COL/]OFF [COL/]OFF AM/NM [COL/]OFF DISKOFFS LENGTH NVOLLAYR LENGTH DISKOFFS LENGTH PERMS MODE default auto auto ENABLED ENABLED disk01 ENABLED disk02 1000 65536 65536 ACTIVE ACTIVE 0 ACTIVE 0 1208758891.dbbl01 286632832 286632832 2097152 2097152 2097152 2097152 2097152 SELECT CONCAT 0 CONCAT 0 - v nfsvol fsgen pl nfsvol-01 RW sd disk01-01 c1t0d0 ENA pl nfsvol-02 RW sd disk02-01 c1t1d0 ENA bash-3.

00# vxdisk list DEVICE TYPE c1t0d0s2 auto:cdsdisk c1t1d0s2 auto:cdsdisk c1t2d0s2 auto:none DISK disk01 disk02 - GROUP nfsdg nfsdg - STATUS online online online invalid .17.Multi-owner Device Groups -Device Group -----------bash-3.Device group status: Device group status: webdg nfsdg Online Online -.00# vxprint -ht Disk group: webdg DG NAME ST NAME DM NAME RV NAME RL NAME REM_RLNK CO NAME VT NAME V NAME PREFPLEX PL NAME NCOL/WID SD NAME DEVICE SV NAME MODE SC NAME DEVICE DC NAME SP NAME EX NAME STATE SR NAME dg webdg dm disk01 dm disk02 v webvol fsgen pl webvol-01 RW sd disk01-01 c1t3d0 ENA pl webvol-02 RW sd disk02-01 c1t4d0 ENA NCONFIG STATE DEVICE RLINK_CNT RVG CACHEVOL RVG RVG/VSET/CO VOLUME PLEX PLEX MODE PLEX PARENTVOL SNAPVOL ASSOC KSTATE default c1t3d0s2 c1t4d0s2 webvol webvol-01 webvol webvol-02 default auto auto ENABLED ENABLED disk01 ENABLED disk02 51000 65536 65536 ACTIVE ACTIVE 0 ACTIVE 0 1208759074.dbbl02 286632832 286632832 2097152 2097152 2097152 2097152 2097152 SELECT CONCAT 0 CONCAT 0 NLOG DM_CNT TYPE KSTATE KSTATE KSTATE KSTATE KSTATE KSTATE DISK VOLNAME CACHE LOGVOL DCO VC MINORS GROUP-ID SPARE_CNT PRIVLEN PUBLEN STATE PRIMARY STATE REM_HOST STATE STATE STATE STATE NVOLUME LENGTH LENGTH APPVOL_CNT STATE DATAVOLS SRL REM_DG Online Status ------------- UTYPE MODE MODE READPOL LAYOUT [COL/]OFF [COL/]OFF AM/NM [COL/]OFF DISKOFFS LENGTH NVOLLAYR LENGTH DISKOFFS LENGTH PERMS MODE bash-3.

00# bash-3.00# mount -F vxfs global /dev/vx/dsk/nfsdg/nfsvol /global/nfs bash-3.nodelist=dbbl01:dbbl02.c1t3d0s2 auto:cdsdisk c1t4d0s2 auto:cdsdisk c1t5d0s2 auto:none c1t8d0s2 auto:none c1t9d0s2 auto:none c2t0d0s2 auto:none c2t1d0s2 auto:none bash-3.Device Group Status -Device Group -----------webdg nfsdg -----------webdg nfsdg Primary ------dbbl01 dbbl01 dbbl02 dbbl02 Device group status: Device group status: Status -----Online Online -.00# df -k Filesystem /dev/dsk/c2t0d0s0 /devices ctfs proc mnttab kbytes used avail capacity 50425263 12571911 37349100 26% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% Mounted on / /devices /system/contract /proc /etc/mnttab .name=nfsdg.failback=disabled bash-3.00# mkfs -F vxfs /dev/vx/rdsk/nfsdg/nfsvol version 7 layout 2097152 sectors.00# mount -F vxfs global /dev/vx/dsk/webdg/webvol /global/web (mount from Node02) bash-3.Multi-owner Device Groups -Device Group -----------Online Status ------------- bash-3.00# mkdir /global/web bash-3.00# scstat -D -. log size 16384 blocks largefiles supported bash-3.00# scswitch -z -D webdg -h dbbl02 bash-3.preferenced= =true.00# scconf -a -D type=vxvm.00# scswitch -z -D nfsdg -h dbbl01 bash-3.Device Group Servers -- disk01 disk02 - webdg webdg - online online online online online online online invalid invalid invalid invalid invalid Device Group Secondary --------Device group servers: Device group servers: -. 1048576 blocks of size 1024.00# mkdir /global/nfs bash-3.

devices/node@1 ufs 2 no global bash-3.swap 10952200 /etc/svc/volatile objfs 0 fd 0 swap 10951080 swap 10950792 swap 10950672 swap 10950672 /dev/dsk/c2t0d0s3 2032943 /dev/did/dsk/d10s4 5045478 /global/.Device Group Servers -Device Group Secondary --------Device group servers: Device group servers: -.devices/node@2 /dev/vx/dsk/nfsdg/nfsvol 1048576 /dev/vx/dsk/webdg/webvol 1048576 bash-3.00# vi /etc/vfstab 1528 10950672 0 0 0 0 408 10950672 120 10950672 0 10950672 0 10950672 2065 1969890 7699 4987325 7699 4987325 17750 17750 966407 966407 0% 0% 1% /system/object /dev/fd /tmp /var/run /dev/vx/dmp /dev/vx/rdmp /export/home 1% 1% 0% 0% 1% 1% 1% 2% 2% /global/nfs /global/web bash-3.devices/node@1 /dev/did/dsk/d13s4 5045478 /global/.Device Group Status ------------webdg nfsdg Primary ------dbbl02 dbbl01 dbbl01 dbbl02 .00# scstat -D -.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/.

00# scstat -D -.Device Group Status -Device Group -----------webdg nfsdg Status -----Online Online -----------webdg nfsdg Primary ------dbbl01 dbbl01 dbbl02 dbbl02 Online Status ------------- Device group status: Device group status: -.Multi-owner Device Groups -Device Group -----------bash-3.Multi-owner Device Groups -Device Group -----------Online Status ------------- .Device group status: Device group status: Device Group -----------webdg nfsdg Status -----Online Online -.Device Group Servers -Device Group Secondary --------Device group servers: Device group servers: -.

Sign up to vote on this title
UsefulNot useful