|
Required information
|
Description
|
|---|
|
To install SF Oracle RAC depots
|
System names on which to install SF Oracle RAC
|
Example: galaxy, nebula
|
License keys
|
License keys could be one of the following types:
-
Valid license keys for each system in the cluster
-
Valid site license key
-
Valid demo license key
If you want to configure global clusters and enable disaster recovery, you must enter appropriate license keys.
See Obtaining SF Oracle RAC license keys
|
Do you want to install required SF Oracle RAC depots or all SF Oracle RAC depots?
|
Install only the required depots if you do not want to configure any optional components or features.
Default option is to install all depots.
|
|
To configure Veritas Cluster Server component
|
Name of the cluster
|
The name must begin with a letter of the alphabet (a-z, A-Z) and contain only the characters a through z, A through Z, and 1 through 0, hyphen (-), and underscore (_).
Example: rac_cluster101
|
Unique ID number for the cluster
|
Number in the range of 0-65535. Within the site containing the cluster, each cluster must have a unique ID.
Example: 101
|
Device names of the NICs used by the private networks among systems
|
Do not enter the network interface card that is used for the public network, which is typically lan0.
Example: lan1, lan2
|
|
To configure SF Oracle RAC clusters in secure mode (optional)
|
Which mode do you want to choose to configure Authentication Service?
|
The installer provides you three modes to configure Authentication Service in the SF Oracle RAC clusters.
-
automatic mode
-
semiautomatic mode using encrypted files
-
semiautomatic mode without using encrypted files
Default option is automatic mode.
See Symantec Product Authentication Service
|
Host name of the Symantec Product Authentication Service Root Broker System
|
Example: venus
|
|
To add SF Oracle RAC users (required if you did not configure the cluster in secure mode)
|
User name
|
Example: smith
|
User password
|
Enter the password at the prompt.
|
User privilege
|
Users have three levels of privileges: A=Administrator, O=Operator, or G=Guest.
Example: A
|
|
To configure the Cluster Management Console cluster connector (optional)
|
Management Server network address for Cluster Management Console
|
Example: mgmtserver1.symantecexample.com
|
Cluster Management Console service account password
|
You must have set this account password while installing the management server.
|
Root hash of the management server
|
You can use vssat showbrokerhash command and copy the root hash of the management server.
|
|
To configure the Cluster Management Console (optional)
|
Name of the public NIC for each node in the cluster
|
The device name for the NIC that provides public network access.
Example: lan0
|
Virtual IP address of the NIC for Cluster Management Console
|
This virtual IP address becomes a resource for use by the ClusterService group that includes the Cluster Management Console. The "Cluster Virtual IP address" can fail over to another cluster system, making the Web Console highly available.
Example: 10.10.12.1
|
Netmask for the virtual IP address
|
The subnet used with the virtual address.
Example: 255.255.240.0
|
NetworkHosts IP addreses to check the connection
|
This IP address is used to check the adapter connections.
Example: 10.10.12.12
|
|
To configure SMTP email notification (optional)
|
Domain-based address of the SMTP server
|
The SMTP server sends notification email about the events within the cluster.
Example: smtp.symantecexample.com
|
Email address of each SMTP recipient to be notified
|
Example: john@symantecexample.com
|
Minimum severity of events for SMTP email notification
|
Events have four levels of severity: I=Information, W=Warning, E=Error, and S=SevereError.
Example: E
|
|
To configure SNMP trap notification (optional)
|
Port number for the SNMP trap daemon
|
Default port number is 162.
|
Machine name for each SNMP console
|
Example: neptune
|
Minimum severity of events for SNMP trap notification
|
Events have four levels of severity: I=Information, W=Warning, E=Error, and S=SevereError.
Example: E
|
|
To configure global cluster option (optional)
|
Name of the public NIC
|
You may use the same NIC that you configured for the ClusterService group. Otherwise, you must specify appropriate values for the NIC when you are prompted.
Example: lan0
|
Virtual IP address of the NIC
|
You may use the same virtual IP address that you configured for the ClusterService group. Otherwise, you must specify appropriate values for the virtual IP address when you are prompted.
Example: 10.10.12.1
|
Netmask for the virtual IP address
|
You may use the same netmask as configured for the ClusterService group. Otherwise, you must specify appropriate values for the netmask when you are prompted.
Example: 255.255.240.0
|
NetworkHosts IP addreses
|
You may use the same NetworkHosts IP address as configured for the ClusterService group. Otherwise, you must specify appropriate values for the netmask when you are prompted.
Example: 10.10.12.2
|
|
To configure Cluster Volume Manager
|
CVM cluster reconfiguration timeout in seconds
|
Default is 200.
|
Do you want to configure enclosure-based naming scheme?
|
Dynamic Multipathing (DMP) is a prerequisite for enclosure-based naming schemes.
|
|
To configure Veritas Volume Replicator (optional)
|
Frequency of VVR statistics collection
|
Default is 10 seconds.
|
Number of days to preserve the collected statistics
|
Default is 3 days.
|
|
To configure I/O fencing
|
Name of three disks that will form the coordinator disk group
|
Example: c1t1d0, c2t1d0, c3t1d0
|
DMP nodes names for each disk in the coordinator disk group (if using DMP)
|
Example: /dev/vx/dmp
|
