|
|
|
|
|
Configuring VCS, CVM, and CFS involves the following tasks:
Storage Foundation and High Availability Solutions 5.0
Main Menu > Configure SFRAC > Configure VCS, CVM and CFS
. ............................................................... .
After completing VCS, CVM and CFS configuration, the installer will exit. You will need to restart the SFRAC installer
with -configure option to access the Main Menu.
. ............................................................... .
Continue with configuration? [y,n,q,b] (n) y
Stopping Cluster Manager and Agents on galaxy ........... Done
Stopping Cluster Manager and Agents on nebula ........... Done
Stopping glm on galaxy .................................. Done
Stopping glm on nebula .................................. Done
Storage Foundation and High Availability Solutions 5.0
Stopping SFRAC processes. Please wait...
Storage Foundation and High Availability Solutions 5.0
To configure SFRAC, please answer the following sets of questions.
When a [b] is presented after a question, 'b' may be entered to go back to the first question of the configuration set.
When a [?] 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.
Configuring VCS involves the following tasks:
Storage Foundation and High Availability Solutions 5.0
To configure VCS for SFRAC the following is required:
A unique Cluster ID number between 0-65535
Two or more NIC cards per system used for heartbeat links
All systems are being configured to create one cluster
Enter the unique cluster name: [?] rac_cluster101
Enter the unique Cluster ID number between 0-65535: [b,?] 101
Discovering NICs on galaxy ....... discovered lan0 lan1 lan2
Enter the NIC for the first private heartbeat link on galaxy: [b,?] lan1
Would you like to configure a second private heartbeat link? [y,n,q,b,?] (y) y
Enter the NIC for the second private heartbeat link on galaxy: [b,?] lan2
Would you like to configure a third private heartbeat link? [y,n,q,b,?] (n) n
Are you using the same NICs for private heartbeat links on all systems? [y,n,q,b,?] (y) y
Checking Media Speed for lan1 on galaxy ............. 1000000000
Checking Media Speed for lan2 on galaxy ............. 1000000000
Checking Media Speed for lan1 on nebula ............. 1000000000
Checking Media Speed for lan2 on nebula ............. 1000000000
Storage Foundation and High Availability Solutions 5.0
Cluster information verification:
Private Heartbeat NICs for galaxy: link1=lan1 link2=lan2
Private Heartbeat NICs for nebula: link1=lan1 link2=lan2
Is this information correct? [y,n,q] (y) y
Configure cluster in secure mode (optional)
The sample configuration assumes that you have installed the root broker on another system, venus.
Storage Foundation and High Availability Solutions 5.0
Veritas Storage Foundation for Oracle RAC can be configured to utilize Symantec Security Services.
Running SFRAC in Secure Mode guarantees that all inter-system communication is encrypted and that users are verified with security credentials.
When running SFRAC in Secure Mode, NIS and system usernames and passwords are used to verify identity. SFRAC usernames and passwords are no longer utilized when a cluster is running in Secure Mode.
Before configuring a cluster to operate using Symantec Security Services, another system must already have Symantec Security Services installed and be operating as a Root Broker. Refer to the Veritas Cluster Server Installation Guide for more information on configuring a VxSS Root Broker.
Would you like to configure SFRAC to use Symantec Security Services? [y,n,q] (n) y
Storage Foundation and High Availability Solutions 5.0
Security can be configured completely automatically by the installer or it can also be configured semi automatically. In automatic mode, no user intervention is required. In the semi automatic mode, Authentication Broker related setup on Root Broker is expected to be performed by the Root Broker Administrator and CPI will ask for certain information that will be used to configure Authentication Brokers.
1) Configure security completely automatically
2) Provide AB credentials using BLOBs
3) Provide AB credentials without using BLOBs
Select the Security option you would like to perform [1-3,q,?] (1) 1
In order to enable Symantec Security Services on a SFRAC Cluster, Veritas Authentication Services (VRTSat depot) must be installed on a system and operating as a Root Broker. Refer to the Veritas Cluster Server Installation Guide for more information on installing and configuring Veritas Authorization Services.
Enter the name of the VxSS Root Broker system: venus
Checking vxatd process .................................. running
Checking vxatd version ................................. 4.3.22.0
Checking security domain ......... root@venus.symantecexample.com
Systems will use root@venus.symantecexample.com as its VxSS Domain
Note
Installer asks you to add SF Oracle RAC users now if you did not configure cluster in secure mode.
Storage Foundation and High Availability Solutions 5.0
The following information is required to add SFRAC users:
User privileges (Administrator, Operator, or Guest)
Do you want to set the username and/or password for the Admin user
(default username = 'admin', password='password')? [y,n,q] (n) y
Do you want to add another user to the cluster? [y,n,q] (y) y
Enter the user name: [?] smith
Enter the privilege for user smith (A=Administrator, O=Operator, G=Guest): [?] A
Would you like to add another user? [y,n,q] (n) n
User: admin Privilege: Administrators
User: smith Privilege: Administrators
Is this information correct? [y,n,q] (y) y
Configure the Cluster Management Console cluster connector (optional)
The sample configuration assumes that you have installed the Cluster Management Console management server on another system, mgmtserver1.
Storage Foundation and High Availability Solutions 5.0
Setup will now configure Veritas Cluster Management Console. If you have configured a management server, you can configure the cluster to be managed by the management server. You can also configure Veritas Cluster Management Console on cluster nodes to manage the local cluster.
Do you want this cluster to be managed by a management server? Enter 'y' if you have set up a management server. [y,n,q] (y) y
Storage Foundation and High Availability Solutions 5.0
To configure the CMC cluster connector, the following is required:
Enter the network address used by the management server [?] (galaxy) mgmtserver1.symantecexample.com
Management server address: mgmtserver1.symantecexample.com
Is this information correct? [y,n,q] (y) y
Storage Foundation and High Availability Solutions 5.0
The following information is required to set up secure communication with the CMC management server:
Password for the service account created during the management server install (CMC_CC@CMC_SERVICES)
Hash of CMC management server's root broker. See the Veritas Cluster Server Installation Guide for information on how to retrieve the hash.
Enter the password for the CMC service account:
Enter the hash of the management server's root broker [?] xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Root broker hash: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Is this information correct? [y,n,q] (y) y
Configure the Cluster Management Console (optional)
Storage Foundation and High Availability Solutions 5.0
The following information is required to configure the Cluster Management Console:
A public NIC used by each system in the cluster
A Virtual IP address and netmask for the Cluster Management Console
One or more NetworkHosts IP addresses for connection checking
Do you want to configure the Cluster Management Console [y,n,q] (y) y
Active NIC devices discovered on galaxy: lan0
Enter the NIC for Cluster Management Console to use on galaxy: [b,?] (lan0) lan0
Is lan0 to be the public NIC used by all systems [y,n,q,b,?] (y) y
Enter the Virtual IP address for Cluster Management Console: [b,?] (10.182.148.193) 11.136.88.199
Enter the netmask for IP 11.136.88.199: [b,?] (255.255.240.0)
Enter the NetworkHosts IP addresses, separated by spaces: [b,?] 11.136.88.232
Storage Foundation and High Availability Solutions 5.0
Cluster Management Console verification:
Is this information correct? [y,n,q] (y) y
Configure SMTP mail notification (optional)
Storage Foundation and High Availability Solutions 5.0
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] (y) y
Active NIC devices discovered on galaxy: lan0
Enter the NIC for the SFRAC Notifier to use on galaxy: [b,?] (lan0) lan0
Is lan0 to be the public NIC used by all systems [y,n,q,b,?] (y) y
Enter the domain-based hostname of the SMTP server
(example: smtp.yourcompany.com): [b,?] smtp.symantecexample.com
Enter the full email address of the SMTP recipient
(example: user@yourcompany.com): [b,?] ozzie@symantecexample.com
Enter the minimum severity of events for which mail should be
sent to ozzie@symantecexample.com [I=Information, W=Warning,
E=Error, S=SevereError]: [b,?] w
Would you like to add another SMTP recipient? [y,n,q,b] (n) y
Enter the full email address of the SMTP recipient
(example: user@yourcompany.com): [b,?] harriet@symantecexample.com
Enter the minimum severity of events for which mail should be
sent to harriet@symantecexample.com [I=Information, W=Warning,
E=Error, S=SevereError]: [b,?] E
Would you like to add another SMTP recipient? [y,n,q,b] (n) n
SMTP email notification verfication
SMTP Address: smtp.symantecexample.com
Recipient: ozzie@symantecexample.com receives email for Warning or higher events
Recipient: harriet@symantecexample.com receives email for Error or higher events
Is this information correct? [y,n,q] (y) y
Configure SNMP trap notification (optional)
Storage Foundation and High Availability Solutions 5.0
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] (y) y
Active NIC devices discovered on galaxy: lan0
Enter the NIC for the SFRAC Notifier to use on galaxy: [b,?] (lan0) lan0
Is lan0 to be the public NIC used by all systems [y,n,q,b,?] (y) y
Enter the SNMP trap daemon port: [b,?] (162)
Enter the SNMP console system name: [b,?] neptune
Enter the minimum severity of events for which SNMP traps should be sent to saturn [I=Information, W=Warning, E=Error, S=SevereError]: [b,?] E
Would you like to add another SNMP console? [y,n,q,b] (n) y
Enter the SNMP console system name: [b,?] pluto
Enter the minimum severity of events for which SNMP traps should be sent to jupiter [I=Information, W=Warning, E=Error, S=SevereError]: [b,?] S
Would you like to add another SNMP console? [y,n,q,b] (n) n
SNMP trap notification verfication
Console: neptune receives SNMP traps for Error or higher events
Console: pluto receives SNMP traps for SevereError or higher events
Is this information correct? [y,n,q] (y) y
Configure global cluster option (optional)
The sample configuration assumes that you entered a license to configure VCS global clusters.
Storage Foundation and High Availability Solutions 5.0
The following is required to configure the Global Cluster Option:
A public NIC used by each system in the cluster
A Virtual IP address and netmask
The Virtual IP address and NIC may be the same as those configured for Cluster Management Console
Do you want to configure the Global Cluster Option? [y,n,q] (y) y
Enter the Virtual IP address for Cluster Management Console: [b,?] (11.136.88.199) 11.136.88.199
Storage Foundation and High Availability Solutions 5.0
Global Cluster Option configuration verification:
Matching Cluster Management Console Virtual IP configuration
Is this information correct? [y,n,q] (y) y
Storage Foundation and High Availability Solutions 5.0
The following information is required to setup the permission for Veritas Storage Foundation for Oracle RAC Utility to support Oracle Database:
The Veritas Storage Foundation for Oracle RAC utility for database administration requires permission changes to allow database administrators (DBAs) access to the tools. The default settings at installation time for the /opt/VRTSdbed directory allows only the root user access to the directory. You need to change permissions to allow a DBA or a group of DBAs access to the Veritas Storage Foundation for Oracle RAC tools
Do you want to add single user access on galaxy [y,n,q,?] (y) y
Enter login account name for DBA user: oracle
Do you want to add group access on galaxy [y,n,q,?] (y) y
Enter group name for DBA users: dba
Storage Foundation and High Availability Solutions 5.0
The following information is required to setup the permission for Veritas Storage Foundation for Oracle RAC Utility to support Oracle Database:
The Veritas Storage Foundation for Oracle RAC utility for database administration requires permission changes to allow database administrators (DBAs) access to the tools. The default settings at installation time for the /opt/VRTSdbed directory allows only the root user access to the directory. You need to change permissions to allow a DBA or a group of DBAs access to the Veritas Storage Foundation for Oracle RAC tools
Do you want to add single user access on nebula [y,n,q,?] (y) y
Enter login account name for DBA user: oracle
Do you want to add group access on nebula [y,n,q,?] (y) y
Enter group name for DBA users: dba
Storage Foundation and High Availability Solutions 5.0
Enter Cluster Volume Manager cluster reconfiguration timeout (sec): (200) 200
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) y
Do you wish to use the enclosure-based naming scheme for all of the eligible systems? [y,n,q,?] (y) y
Storage Foundation and High Availability Solutions 5.0
Veritas Volume Manager default disk group configuration:
Many Veritas Volume Manager commands affect the contents or configuration of a disk group. Such commands require that the user specify a disk group. This is accomplished by using the -g option of a command or setting the VXVM_DEFAULTDG environment variable. An alternative to these two methods is to configure the default disk group of a system.
Do you want to set up a default disk group for each system? [y,n,q,?] (y) y
Will you specify one disk group name for all eligible systems? [y,n,q,?] (y)y
Specify a default disk group for all systems. [?] xyz_dg
You have decided to specify the default disk groups as follows:
Host: galaxy ................................ Disk group: xyz_dg
Host: nebula ................................ Disk group: xyz_dg
Note: If 'nodg' is displayed, then the host will be configured to have no default disk group.
Is this correct? [y,n,q] (y) y
Storage Foundation and High Availability Solutions 5.0
Following are the default ports that will be used by VVR on galaxy:
Port for VVR heartbeat communication: 4145
Port for vradmind daemon: 8199
Port for vxrsyncd daemon: 8989
Ports for data replication: Anonymous-Ports
The ports indicated for VVR heartbeats and vradmind are IANA assigned.
The port settings should be identical for systems that will be part of the same Replicated Data Set. They should also be identical for all the systems in a cluster.
Do you want to change any of the VVR ports on galaxy? [y,n,q] (n) n
Storage Foundation and High Availability Solutions 5.0
VVR Statistics Collection Tool
The VVR administrative daemon vradmind can collect and maintain various statistics which are helpful in solving VVR performance issues. This collection can be tuned using a few tunables like the frequency for gathering the statistics and the number of days for which the collected statistics should be preserved, after which the earlier statistics are automatically deleted.
The frequency of VVR statistics collection on galaxy is set to per 10 seconds.
Do you want to change the frequency of VVR statistics collection on galaxy ? [y,n,q] (n) n
The maximum number of days for which VVR statistics can be retained is set to 3 on galaxy.
Do you want to change the maximum number of days for retaining VVR statistics on galaxy ? [y,n,q] (n) n
Storage Foundation and High Availability Solutions 5.0
Configuration of VVR tunables (For the advanced user)
Do you want to view or modify VVR tunables on galaxy ? [y,n,q,?] (n) n
Storage Foundation and High Availability Solutions 5.0
Following are the default ports that will be used by VVR on nebula:
Port for VVR heartbeat communication: 4145
Port for vradmind daemon: 8199
Port for vxrsyncd daemon: 8989
Ports for data replication: Anonymous-Ports
The ports indicated for VVR heartbeats and vradmind are IANA assigned.
The port settings should be identical for systems that will be part of the same Replicated Data Set. They should also be identical for all the systems in a cluster.
Do you want to change any of the VVR ports on nebula? [y,n,q] (n)
Storage Foundation and High Availability Solutions 5.0
VVR Statistics Collection Tool
The VVR administrative daemon vradmind can collect and maintain various statistics which are helpful in solving VVR performance issues. This collection can be tuned using a few tunables like the frequency for gathering the statistics and the number of days for which the collected statistics should be preserved, after which the earlier statistics are automatically deleted.
The frequency of VVR statistics collection on nebula is set to per 10 seconds.
Do you want to change the frequency of VVR statistics collection on nebula ? [y,n,q] (n)
The maximum number of days for which VVR statistics can be retained is set to 3 on nebula
Do you want to change the maximum number of days for retaining VVR statistics on nebula ? [y,n,q] (n)
Storage Foundation and High Availability Solutions 5.0
Configuration of VVR tunables (For the advanced user)
Do you want to view or modify VVR tunables on nebula ? [y,n,q,?] (n)
Storage Foundation and High Availability Solutions 5.0
Would you like to start VAILAgent (Array discovery service for Deep mapping) on the target system (once started, this service will be accessible across the domain)? [y,n,q,?] (y) y
Storage Foundation and High Availability Solutions 5.0
Creating nebula security principal on galaxy ................. Done
Starting Symantec Security Services on nebula ................ Done
Creating Veritas Storage Foundation for Oracle RAC
configuration files .......................................... Done
Copying configuration files to galaxy ........................ Done
Copying configuration files to nebula ........................ Done
Storage Foundation and High Availability Solutions 5.0
Verify the install systems Fully Qualified Hostnames.
Querying fully qualified domain name of host "galaxy" .......... ok
Is the fully qualified hostname of system "galaxy" = "galaxy.symantecexample.com"? [y,n,q] (y) y
Querying fully qualified domain name of host "nebula" .......... ok
Is the fully qualified hostname of system "nebula" = "nebula.symantecexample.com"? [y,n,q] (y) y
Checking rsh communication with nebula.symantecexample.com
...................................................... HPUX B.11.23
The sample configuration chooses to manage the hosts in standalone mode.
Note
Make sure to enter n at the prompt to configure standalone hosts. SF Management Server is not available on the Storage Foundation and High Availability Solutions release. You must order SF Management Server separately to configure SF Management Server managed hosts.
Storage Foundation and High Availability Solutions 5.0
Choose how this install will be managed.
This product can configured one of the two following ways:
* Storage Foundation Management Server managed host (Recommended)
Pre-requisites for Storage Foundation Management Server managed host:
* A Storage Foundation Management Server (SFMS) is configured
* SFMS should be currently running and fully operational.
* Authentication Broker that is used by SFMS should be running.
The following information would be requested during configuration:
* Previously set SFMS agent account password
There are no pre-requisites for deploying as a standalone host.
Enabling Storage Foundation Management Server management simplifies and improves management of the complex data center resources, reducing planned and unplanned down time.
Enable Storage Foundation Management Server Management? [y,n,q] (y) n
Storage Foundation and High Availability Solutions 5.0
Verify the install systems Fully Qualified Hostnames.
Configure VEA in STANDALONE mode on galaxy ...................... ok
Configuring gridnode on galaxy .................................. ok
Registering gridnode on galaxy .................................. ok
Configuring actionagent on galaxy ............................... ok
Registering actionagent on galaxy ............................... ok
Registering StorageAgent on galaxy .............................. ok
Registering VAILAgent on galaxy ................................. ok
Deploying CMC service account to nebula:
Copying package to nebula ..................................... Done
Extracting package on nebula .................................. Done
Storage Foundation and High Availability Solutions 5.0
Verify the install systems Fully Qualified Hostnames.
Configure VEA in STANDALONE mode on nebula .......................ok
Configuring gridnode on nebula .................................. ok
Registering gridnode on nebula .................................. ok
Configuring actionagent on nebula ............................... ok
Registering actionagent on nebula ............................... ok
Stopping StorageAgent on nebula ................................. ok
Registering StorageAgent on nebula .............................. ok
Registering VAILAgent on nebula ................................. ok
Storage Foundation and High Availability Solutions 5.0
Do you want to start Veritas Storage Foundation for Oracle RAC processes now? [y,n,q] (y) y
Storage Foundation and High Availability Solutions 5.0
______________________________________ -
Startup completed successfully on all systems
Confirming VxVM configuration daemons startup .. All systems Enabled
Starting CFS agents ....................................... Started
Setting default disk group to xyz_dg on galaxy ............... Done
Setting default disk group to xyz_dg on nebula ............... Done
Storage Foundation and High Availability Solutions 5.0
A string of five or more characters is required to encrypt passwords in the responsefile
Enter five or more characters to be used an encryption key: xxxxxx
This key must be retained in a secure file and referenced using the -enckeyfile option if the generated responsefile is to be used again.
Configuration log files, summary file, and response file are saved at:
/opt/VRTS/install/logs/installer-AF5ZqM
See the Veritas Storage Foundation for Oracle RAC Installation and Configuration Guide for more information.
To continue SFRAC configuration, invoke the installer using -configure flag.