Veritas Storage Foundation and High Availability 6.0.1 Configure Program
Copyright (c) 2012 Symantec Corporation. All rights reserved. Symantec, the
Symantec Logo are trademarks or registered trademarks of Symantec Corporation or
its affiliates in the U.S. and other countries. Other names may be trademarks of
their respective owners.
The Licensed Software and Documentation are deemed to be "commercial computer
software" and "commercial computer software documentation" as defined in FAR
Sections 12.212 and DFARS Section 227.7202.
Logs are being written to /var/tmp/installsfha601-201404231512rwa while
installsfha601 is in progress.
Enter the Solaris x64 system names separated by spaces: [q,?] sol2 sol3
Veritas Storage Foundation and High Availability 6.0.1 Configure Program
sol2 sol3
Logs are being written to /var/tmp/installsfha601-201404231512rwa while
installsfha601 is in progress
Verifying systems: 100%
Estimated time remaining: (mm:ss) 0:00 5 of 5
Checking system communication ..................................... Done
Checking release compatibility .................................... Done
Checking installed product ........................................ Done
Checking platform version ......................................... Done
Performing product prechecks ...................................... Done
System verification checks completed successfully
I/O Fencing
It needs to be determined at this time if you plan to configure I/O Fencing in
enabled or disabled mode, as well as help in determining the number of network
interconnects (NICS) required on your systems. If you configure I/O Fencing in
enabled mode, only a single NIC is required, though at least two are
recommended.
A split brain can occur if servers within the cluster become unable to
communicate for any number of reasons. If I/O Fencing is not enabled, you run
the risk of data corruption should a split brain occur. Therefore, to avoid data
corruption due to split brain in CFS environments, I/O Fencing has to be
enabled.
If you do not enable I/O Fencing, you do so at your own risk
See the Administrator's Guide for more information on I/O Fencing
Do you want to configure I/O Fencing in enabled mode? [y,n,q,?] (y)
To configure VCS, answer the set of questions on the next screen.
When [b] is presented after a question, 'b' may be entered to go back to the
first question of the configuration set.
When [?] is presented after a question, '?' may be entered for help or
additional information about the question.
Following each set of questions, the information you have entered will be
presented for confirmation. To repeat the set of questions and correct any
previous errors, enter 'n' at the confirmation prompt.
No configuration changes are made to the systems until all configuration
questions are completed and confirmed.
Press [Enter] to continue:
To configure VCS for SFHA the following information is required:
A unique cluster name
One or more NICs per system used for heartbeat links
A unique cluster ID number between 0-65535
One or more heartbeat links are configured as private links
You can configure one heartbeat link as a low-priority link
All systems are being configured to create one cluster.
Enter the unique cluster name: [q,?] sol
1) Configure heartbeat links using LLT over Ethernet
2) Configure heartbeat links using LLT over UDP
3) Automatically detect configuration for LLT over Ethernet
b) Back to previous menu
How would you like to configure heartbeat links? [1-3,b,q,?] (1)
Discovering NICs on sol2 .................... Discovered e1000g0 e1000g1
Enter the NIC for the first private heartbeat link on sol2: [b,q,?] (e1000g1)
Would you like to configure a second private heartbeat link? [y,n,q,b,?] (n)
Do you want to configure an additional low-priority heartbeat link? [y,n,q,b,?]
(n) y
Enter the NIC for the low-priority heartbeat link on sol2: [b,q,?] (e1000g0)
Are you using the same NICs for private heartbeat links on all systems?
[y,n,q,b,?] (y)
Checking media speed for e1000g1 on sol2 ..................... 1000 Mbps
Checking media speed for e1000g1 on sol3 ..................... 1000 Mbps
Enter a unique cluster ID number between 0-65535: [b,q,?] (27375)
The cluster cannot be configured if the cluster ID 27375 is in use by another
cluster. Installer can perform a check to determine if the cluster ID is
duplicate. The check will take less than a minute to complete.
Would you like to check if the cluster ID is in use by another cluster? [y,n,q]
(y)
Checking cluster ID ............................................... Done
Duplicated cluster ID detection passed. The cluster ID 27375 can be used for the
cluster.
Press [Enter] to continue:
Cluster information verification:
Cluster Name: sol
Cluster ID Number: 27375
Private Heartbeat NICs for sol2:
link1=e1000g1
Low-Priority Heartbeat NIC for sol2:
link-lowpri1=e1000g0
Private Heartbeat NICs for sol3:
link1=e1000g1
Low-Priority Heartbeat NIC for sol3:
link-lowpri1=e1000g0
Is this information correct? [y,n,q,?] (y)
The following data is required to configure the Virtual IP of the Cluster:
A public NIC used by each system in the cluster
A Virtual IP address and netmask
Do you want to configure the Virtual IP? [y,n,q,?] (n) y
Active NIC devices discovered on sol2: e1000g0
Enter the NIC for Virtual IP of the Cluster to use on sol2: [b,q,?] (e1000g0)
Is e1000g0 to be the public NIC used by all systems? [y,n,q,b,?] (y)
Enter the Virtual IP address for the Cluster: [b,q,?] 192.168.1.189
Enter the NetMask for IP 192.168.1.189: [b,q,?] (255.255.255.0)
Cluster Virtual IP verification:
NIC: e1000g0
IP: 192.168.1.189
NetMask: 255.255.255.0
Is this information correct? [y,n,q] (y)
Veritas Cluster Server can be configured in secure mode
Running VCS in Secure Mode guarantees that all inter-system communication is
encrypted, and users are verified with security credentials.
When running VCS in Secure Mode, NIS and system usernames and passwords are used
to verify identity. VCS usernames and passwords are no longer utilized when a
cluster is running in Secure Mode.
Would you like to configure the VCS cluster in secure mode? [y,n,q,?] (n)
The following information is required to add VCS users:
A user name
A password for the user
User privileges (Administrator, Operator, or Guest)
Do you wish to accept the default cluster credentials of 'admin/password'?
[y,n,q] (y)
Do you want to add another user to the cluster? [y,n,q] (n)
VCS User verification:
User: admin Privilege: Administrators
Passwords are not displayed
Is this information correct? [y,n,q] (y)
The following information is required to configure SMTP notification:
The domain-based hostname of the SMTP server
The email address of each SMTP recipient
A minimum severity level of messages to send to each recipient
Do you want to configure SMTP notification? [y,n,q,?] (n)
The following information is required to configure SNMP notification:
System names of SNMP consoles to receive VCS trap messages
SNMP trap daemon port numbers for each console
A minimum severity level of messages to send to each console
Do you want to configure SNMP notification? [y,n,q,?] (n)
All SFHA processes that are currently running must be stopped
Do you want to stop SFHA processes now? [y,n,q,?] (y)
Logs are being written to /var/tmp/installsfha601-201404231512rwa while
installsfha601 is in progress
Starting SFHA: 100%
Estimated time remaining: (mm:ss) 0:00 18 of 18
Starting vxesd .................................................... Done
Starting vxrelocd ................................................. Done
Starting vxconfigbackupd .......................................... Done
Starting vxportal ................................................. Done
Starting fdd ...................................................... Done
Starting llt ...................................................... Done
Starting gab ...................................................... Done
Starting amf ...................................................... Done
Starting had ...................................................... Done
Starting CmdServer ................................................ Done
Starting vxdbd .................................................... Done
Starting odm ...................................................... Done
Performing SFHA poststart tasks ................................... Done
Veritas Storage Foundation and High Availability Startup completed successfully
Veritas Storage Foundation and High Availability 6.0.1 Configure Program
sol2 sol3
Fencing configuration
1) Configure Coordination Point client based fencing
2) Configure disk based fencing
Select the fencing mechanism to be configured in this Application Cluster:
[1-2,q] 2
This fencing configuration option requires a restart of VCS. Installer will stop
VCS at a later stage in this run. Do you want to continue? [y,n,q,b,?] y
Do you have SCSI3 PR enabled disks? [y,n,q,b] (y) n
Since you don't have SCSI3 PR enabled disks, you cannot configure disk based
fencing but you can use Coordination Point client based fencing
Do you want to retry fencing configuration? [y,n,q,b] (n)
The updates to VRTSaslapm package are released via the Symantec SORT web page:
https://sort.symantec.com/asl. To make sure you have the latest version of
VRTSaslapm (for up to date ASLs and APMs), download and install the latest
package from the SORT web page.
installsfha601 log files, summary file, and response file are saved at:
/opt/VRTS/install/logs/installsfha601-201404231512rwa
Would you like to view the summary file? [y,n,q] (n) n
# /opt/VRTSvcs/bin/hastatus -sum
-- SYSTEM STATE
-- System State Frozen
A sol2 RUNNING 0
A sol3 RUNNING 0
-- GROUP STATE
-- Group System Probed AutoDisabled State
B ClusterService sol2 Y N ONLINE
B ClusterService sol3 Y N OFFLINE
# cat /etc/llthosts
0 sol2
1 sol3
# cat /etc/llttab
set-node sol2
set-cluster 27375
link e1000g1 /dev/e1000g:1 - ether - -
link-lowpri e1000g0 /dev/e1000g:0 - ether - -
# cat /etc/gabtab
/sbin/gabconfig -c -n2
# cat /etc/VRTSvcs/conf/config/main.cf
include "OracleASMTypes.cf"
include "types.cf"
include "Db2udbTypes.cf"
include "OracleTypes.cf"
include "SybaseTypes.cf"
cluster sol (
UserNames = { admin = anoGniNkoJooMwoInl }
ClusterAddress = "192.168.1.189"
Administrators = { admin }
)
system sol2 (
)
system sol3 (
)
group ClusterService (
SystemList = { sol2 = 0, sol3 = 1 }
AutoStartList = { sol2, sol3 }
OnlineRetryLimit = 3
OnlineRetryInterval = 120
)
IP webip (
Device = e1000g0
Address = "192.168.1.189"
NetMask = "255.255.255.0"
)
NIC csgnic (
Device = e1000g0
)
webip requires csgnic
// resource dependency tree
//
// group ClusterService
// {
// IP webip
// {
// NIC csgnic
// }
// }
# ping 192.168.1.189 (virtual IP)
192.168.1.189 is alive
# netstat -anp
Net to Media Table: IPv4
Device IP Address Mask Flags Phys Addr
------ -------------------- --------------- -------- ---------------
e1000g0 192.168.1.190 255.255.255.255 o 08:00:27:66:02:a4
e1000g0 192.168.1.102 255.255.255.255 7c:e9:d3:86:3e:12
e1000g0 192.168.1.104 255.255.255.255 o 7c:e9:d3:f7:ac:9b
e1000g0 192.168.1.189 255.255.255.255 SPLA 08:00:27:9a:15:5a
e1000g0 192.168.1.191 255.255.255.255 SPLA 08:00:27:9a:15:5a
e1000g0 224.0.0.0 240.0.0.0 SM 01:00:5e:00:00:00
No comments:
Post a Comment