Storage Foundation for Oracle® RAC 7.4.1 Configuration and Upgrade Guide - Solaris
- Section I. Configuring SF Oracle RAC
- Preparing to configure SF Oracle RAC
- Configuring SF Oracle RAC using the script-based installer
- Configuring the SF Oracle RAC components using the script-based installer
- Configuring the SF Oracle RAC cluster
- Configuring SF Oracle RAC in secure mode
- Configuring a secure cluster node by node
- Configuring the SF Oracle RAC cluster
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Configuring the SF Oracle RAC components using the script-based installer
- Performing an automated SF Oracle RAC configuration
- Section II. Post-installation and configuration tasks
- Verifying the installation
- Performing additional post-installation and configuration tasks
- Section III. Upgrade of SF Oracle RAC
- Planning to upgrade SF Oracle RAC
- Performing a full upgrade of SF Oracle RAC using the product installer
- Performing an automated full upgrade of SF Oracle RAC using response files
- Performing a phased upgrade of SF Oracle RAC
- Performing a phased upgrade of SF Oracle RAC from version 6.2.1 and later release
- Performing a rolling upgrade of SF Oracle RAC
- Upgrading SF Oracle RAC using Live Upgrade or Boot Environment upgrade
- Performing post-upgrade tasks
- Section IV. Installation and upgrade of Oracle RAC
- Before installing Oracle RAC
- Preparing to install Oracle RAC using the SF Oracle RAC installer or manually
- Creating users and groups for Oracle RAC
- Creating storage for OCR and voting disk
- Configuring private IP addresses for Oracle RAC 11.2.0.1
- Configuring private IP addresses for Oracle RAC 11.2.0.2 and later versions
- Installing Oracle RAC
- Performing an automated Oracle RAC installation
- Performing Oracle RAC post-installation tasks
- Configuring the CSSD resource
- Relinking the SF Oracle RAC libraries with Oracle RAC
- Configuring VCS service groups for Oracle RAC
- Upgrading Oracle RAC
- Before installing Oracle RAC
- Section V. Adding and removing nodes
- Adding a node to SF Oracle RAC clusters
- Adding a node to a cluster using the Veritas InfoScale installer
- Adding the node to a cluster manually
- Setting up the node to run in secure mode
- Configuring server-based fencing on the new node
- Preparing the new node manually for installing Oracle RAC
- Adding a node to the cluster using the SF Oracle RAC response file
- Configuring private IP addresses for Oracle RAC 11.2.0.2 and later versions on the new node
- Removing a node from SF Oracle RAC clusters
- Adding a node to SF Oracle RAC clusters
- Section VI. Configuration of disaster recovery environments
- Configuring disaster recovery environments
- Configuring disaster recovery environments
- Section VII. Installation reference
- Appendix A. Installation scripts
- Appendix B. Tunable files for installation
- Appendix C. Sample installation and configuration values
- SF Oracle RAC worksheet
- Appendix D. Configuration files
- Sample configuration files
- Sample configuration files for CP server
- Appendix E. Configuring the secure shell or the remote shell for communications
- Appendix F. Automatic Storage Management
- Appendix G. Creating a test database
- Appendix H. High availability agent information
- About agents
- CVMCluster agent
- CVMVxconfigd agent
- CVMVolDg agent
- CFSMount agent
- CFSfsckd agent
- PrivNIC agent
- MultiPrivNIC agent
- CSSD agent
- VCS agents for Oracle
- Oracle agent functions
- Resource type definition for the Oracle agent
- Resource type definition for the Netlsnr agent
- Resource type definition for the ASMDG agent
- Oracle agent functions
- CRSResource agent
- Appendix I. SF Oracle RAC deployment scenarios
- Configuration diagrams for setting up server-based I/O fencing
Required attributes of the MultiPrivNIC agent
Table: MultiPrivNIC agent attribute definitions below describes the required attributes of the MultiPrivNIC resource type that can be modified.
The MultiPrivNIC agent also has a set of optional attributes, same as the PrivNIC agent, that can be modified.
For the list of optional attributes:
See Optional attributes of the PrivNIC agent.
Table: MultiPrivNIC agent attribute definitions
Attribute | Dimension | Description |
---|---|---|
Device | string-association | The device attribute specifies the network interface displayed by the ifconfig command and the network ID associated with the interface. The network IDs of the interfaces connected to the same physical network must match. The interfaces specified in the MultiPrivNIC configuration should be exactly the same in name and total number as those which have been used for LLT configuration. An example of the device attribute is as follows: Device@sys1 = {net1=0, net2=1, net3=2} Device@sys2 = {net1=0, net2=1, net3=2} |
Address | string-association | The numerical private IP address and its preferred device. The agent verifies that the IP addresses are valid addresses. When you configure private IP addresses, ensure that the addresses do not have a leading 0 in any of the octets that comprise the IP address. The IP address must be in the format " X.X.X.X". In the following example, 0 and 1 indicates the ID of the device on which the IP address is hosted. If the device is unavailable, the agent automatically reconfigures the IP address on one of the available devices. The available device is determined based on the UseLoadBalance attribute setting. An example of the address attribute is as follows: Address @sys1 = { "192.168.12.1" =0, "192.168.2.1" =0, "192.168.3.1" =1 } Address @sys2 = { "192.168.12.2" =0, "192.168.2.2" =0, "192.168.3.2" =1 } |
Netmask | string-association | The netmask attribute is the numerical netmask for the private IP address. For example, Netmask = "255.255.255.0". |
UseLoadBalance | integer-scalar | Value 0 or 1. In the event that the preferred device is unavailable and multiple links see maximum nodes during failover:
Note: If the preferred device becomes available, the IP address is failed back to the preferred device regardless of the value of UseLoadBalance. |
MTU | string-association | The maximum packet size, in bytes, that can be transmitted over LLT links. This value overrides the default MTU size of the network interface. |
EnableUseTroubleState | Boolean | Value 1 or 0. The value 1 indicates that the MultiPrivNIC agent fails over the IP address of a failed link even when the link state is marked trouble. The default value is 1. The value 0 indicates that the MultiPrivNIC agent fails over the IP address of a failed link only when the link state is marked down. |