1.1.3.5 Manually Configuring the Oracle VM Agent to Support the Secondary Domain

You can use the ovs-agent-secondary command to assist you with the process of setting the Oracle VM Agent to support the secondary domain, see Section 1.1.3.6, “Using the ovs-agent-secondary Command To Setup A Secondary Domain”. The instructions that follow describe how to configure the Oracle VM Agent manually.

  1. Create a configuration file in /etc/ovs-agent/shadow.conf on the primary domain. This configuration file is in JSON format and at absolute minimum should contain the following content to enable support for the secondary domain:

    {
        "enabled": true
    }
    1. Each network link in the primary domain should have a corresponding network link in the secondary domain connected to the same physical network. By default, a network link in the primary domain is associated with the network link with the same name in the secondary domain. If a network link in the primary domain should be associated with a network link in the secondary domain with a different name, then you need to define a network link mapping. To define a network mapping, you need to add a 'nic-mapping' entry in /etc/ovs-agent/shadow.conf. Typically, entries of this sort look similar to the following:

      {
          enabled": true,
          nic-mapping": [
            ["^net4$", "net2" ],
            ["^net5$", "net3" ]
          ]
      }

      In the above example, net4 is a network interface in the primary domain and is connected to the same physical network as the network interface named net2 in the secondary domain. Equally, net5 is a network interface in the primary domain and is connected to the same physical network as the network interface named net3 in the secondary domain. Note that network interface names in the primary domain are encapsulated with the regular expression characters caret (^) and dollar ($) to ensure an exact match for the network interface name in the primary domain. Ensure that the JSON file is properly formatted as defined at http://json.org/.

    2. Each Fibre Channel (FC) disk accessible from the primary domain domain should also be accessible from the secondary domain. By default, a FC disk is accessed using the same device path in the primary domain and in the secondary domain. In particular, each disk is accessed using the same disk controller name. If a disk controller in the primary domain should be associated with a disk controller in the secondary domain with a different name, then you need to define a disk controller mapping.

      It is recommended that Solaris I/O multipathing is enabled in the primary and in the secondary domain on all multipath-capable controller ports, in particular on all FC ports. In that case, all FC disks appear under a single disk controller (usually c0), and disk controller mapping is usually not needed in that case.

      To define a disk controller mapping, add a 'disk-mapping' entry in the /etc/ovs-agent/shadow.conf file. For example:

      {
          "enabled": true,
          "disk-mapping": [
              [ "c0t", "c1t" ]
          ]
      }

      In the above example, c0t is a disk controller in the primary domain that is connected to the same FC disk as the disk controller named c1t in the secondary domain. Ensure that the JSON file is properly formatted as defined at http://json.org/.

    3. An example of an /etc/ovs-agent/shadow.conf file that requires both network interface and disk controller mapping follows:

      {
          "enabled": true,
          "nic-mapping": [
              [ "^net4$", "net2" ],
              [ "^net5$", "net3" ]
          ],
          "disk-mapping": [
              [ "c0t", "c1t" ]
          ]
      }
  2. Save the LDoms configuration with the secondary service domain to the service processor.

    Warning

    Before saving the configuration, ensure that the secondary service domain is active. If the configuration is saved while the secondary service domain is not active, then the secondary service domain won't start automatically after a power-cycle of the server

    # ldm add-spconfig ovm-shadow
  3. To complete the configuration, reconfigure the Oracle VM Agent by running the following command:

    # ovs-agent-setup configure

    The configuration values that are used for this process map onto the values that you entered for the configuration steps when you first configured Oracle VM Agent for your primary control domain, as described in Configuring Oracle VM Agent for SPARC in the Oracle VM Installation and Upgrade Guide.

When the Oracle VM Agent configuration has completed, the secondary domain is running and Oracle VM Agent is able to use it in the case that the primary domain becomes unavailable.