Device 

List of devices and associated base IP addresses. This attribute must be specified separately for each system in the SystemList. You must specify the devices in the list in the order of priority. The first device that the agent determines is "up" becomes the active device, to which the agent assigns a corresponding IP address. 

For IP Conservation Mode (ICM): if all the NICs configured in the Device attribute are down, the MultiNICA agent faults the resource after a 2-3 minute interval. This delay occurs because the MultiNICA agent tests the failed NIC several times before it marks the resource offline. The engine log records messages that provide a detailed description of the failover events. Find the engine log in /var/VRTSvcs/log/engine_A.log. 

Type and dimension: string-association 

Examples: 

• IPv4

  Device@vcsonelnx1={ eth1 = "10.212.100.178", eth2 = "10.212.100.179" }

  Device@vcsonelnx2 ={ eth2 = "10.212.100.180", eth3 = "10.212.100.181" }

• IPv6

  Device@vcsonelnx1={ eth1 = "1234::5678", eth2 = "1234::5679" }

  Device@vcsonelnx2={ eth3 = "1234::5680", eth4 = "1234::5681"}

You can use IPv4 or IPv6 base addresses in the Device attribute, but make sure all of the base addresses use a common IP version. 

NetMask 

Specifies the netmask that is associated with the base IP address. The value must be specified in decimal (base 10). 

Configure this attribute only if the IP address is an IPv4 address.  

Type and dimension: string-scalar 

DualDevice 

The DualDevice attribute specifies the list of devices and associated IPv6 base addresses.  

Specify the following: 

• this attribute separately for each system in the SystemList.
• the devices in the list in the order of priority.

The first device that the agent determines is up becomes the active device, to which the agent assigns a corresponding IP address. 

NICs in Device and DualDevice attributes should be identical and in the same order. 

Use the DualDevice attribute only when configuring mixed IPv4/IPv6 stacks. In that case, use the Device attribute to configure the IPv4 stack and the DualDevice attribute to configure the IPv6 stack. 

Example:  

Device@vcsonelinux1={ eth1 = 2001::DB8, eth2 = 2001::DB9} 

Device@vcsonelinux2={ eth3 = 2001::DB10, eth4 = 2001::DB11}  

Failback 

This attribute determines if the active NIC should be changed to a preferred NIC, even though the current NIC is healthy. If operating in the ICM mode, change the value to 0. 

Type and dimension: boolean-scalar 

Default: 1 

IPv4AddrOptions 

The extra options that are passed to the ip addr add command.  

The agent uses this attribute in tandem with the IPv4RouteOptions attribute. 

The ip addr add command generally resembles: 

"ip -4 addr add ipv4addr/prefixlen IPOptions device dev"

Note   If you configure the Options attribute, the agent ignores this attribute.

Type and dimension: string-scalar 

Example: 

• "broadcast 172.20.9.255"
• "scope link"

IPv4RouteOptions 

The extra options that are passed to the ip route add command. 

The agent uses this attribute in tandem with the IPv4AddrOptions attribute. 

The ip route add command generally resembles: 

"ip route add Route IPRouteOptions"

Note   If you configure the Options attribute, the agent ignores this attribute.

Type and dimension: string-scalar 

Example: 

• "default via 172.20.9.1"
• "scope link"

IPv6AddrOptions 

The extra options that are passed to the ip addr add command. The ip addr add command resembles: 

"ip -6 addr add ipv6addr/prefixlen IPv6AddrOptions device dev"

This attribute supports IPv6. 

Type and dimension: string-scalar 

Example: "scope link" 

IPv6RouteOptions 

The extra options that are passed to the ip route add command. The ip route add command generally resembles: 

"ip route add Route IPv6RouteOptions"

This attribute supports IPv6. 

Type and dimension: string-scalar 

Examples: 

• "default via 2001::DB2"
• "scope link"

LinkOptions 

Specifies options for the ip link command, which can bring an interface up or down. The ip link command generally resembles: 

"ip link dev up LinkOptions"

Type and dimension: string-scalar 

Example: 

• "MTU 1024"
• "broadcast 172.20.9.255"

NetworkHosts 

List of hosts on the network that receive pings to determine the state of the NICs. Specify the IP address of the host, not the host name. Include the hosts that all the NICs in the Device list can reach. If more than one network host is listed, monitor returns online if the ping test is successful with at least one of the hosts. 

You can use both IPv4 and IPv6 NetworkHost addresses, and you can configure both types of addresses in the same resource. 

Type and dimension: string-vector 

Options 

The ifconfig options that you want to use when you assign the base IP address to the active device. 

You must configure either this Options attribute or both the IPv4AddrOptions and IPv4RouteOptions attributes. 

This attribute does not support IPv6. 

Note   If you configure this Options attribute, the agent does not use the IPv4Options and IPv4RouteOptions attributes.

Type and dimension: string-scalar 

Example: "broadcast 10.212.100.255" 

PingOptimize 

Determines whether or not a broadcast ping is sent before checking network statistics, which are used to determine the state of the NIC (if MII is not supported and the ping to NetworkHosts does not confirm the NIC is up.) A value of 1 indicates a broadcast ping does not occur, a value of 0 indicates a broadcast ping occurs. 

Type and dimension: integer-scalar 

Default: 1 

RouteOptions 

Assignment of a base IP address to a device, which is followed by a route add command. The command has the options specified for this attribute. RouteOptions are applicable only when configuring the local host as the default gateway. No routes are added if this string is set to NULL. 

The RouteOptions attribute works in tandem with the Options attribute. You must configure the Options attribute when you use this attribute or the agent ignores this attribute. 

Type and dimension: string-scalar 

Example: "default 166.98.16.103"