Search <book_title>...

Cluster Server 7.3.1 Bundled Agents Reference Guide - Linux

Last Published: 2019-06-14

Product(s): InfoScale & Storage Foundation (7.3.1)

Platform: Linux

Attributes for MultiNICA agent

While configuring the MultiNICA resource, in addition to the required attributes, you must also configure at least one set of attributes from the following:

For IPv4 configurations:
- The Options attribute and the RouteOptions attribute, or
- The IPv4RouteOptions attribute
For IPv6 configurations:
- The IPv6RouteOptions attribute

Table: Required attributes

Required attribute	Description
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 as "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. For each system you must localize the attribute with a separate base IP address. Type and dimension: string-association Examples: IPv4 Device@sys1={ eth1 = "10.212.100.178", eth2 = "10.212.100.179" } Device@sys2 ={ eth2 = "10.212.100.180", eth3 = "10.212.100.181" } IPv6 Device@sys1={ eth1 = "1234::5678", eth2 = "1234::5679" } Device@sys2={ 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.
One of the following attributes: NetMask: Mandatory only if you configure an IPv4 address. PrefixLen: Mandatory only if you configure an IPv6 address.
NetMask	Specifies the netmask that is associated with the base IP address. The value must be specified in decimal (base 10). Configure this attribute if the IP address is an IPv4 address. Type and dimension: string-scalar Example: "255.255.252.0"
PrefixLen	Specifies the prefix for the IPv6 address represented as the CIDR value. When you use the IPv6 protocol, you must configure a value for this attribute. Type-dimension: integer-scalar Range: 0 - 128 Default: 1000 Note: The default value is intentionally invalid for this attribute. You must set the value of this attribute to a range from 0 to 128 to activate this attribute. Example: 64

Table: Optional attributes

Optional attribute	Description
DualDevice	The DualDevice attribute specifies the list of devices and associated IPv6 base addresses. Specify: 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 as "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: DualDevice@sys1={ eth1 = 2001::DB8, eth2 = 2001::DB9} DualDevice@sys2={ 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 for IPv4 addresses.. The agent uses this attribute in tandem with the IPv4RouteOptions attribute. The ip addr add command generally resembles: "ip addr add ipv4addr/prefixlen IPv4AddrOptions dev device" Note: If you configure this attribute, the agent ignores the Options attribute and uses the ip command instead of ifconfig. 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 for IPv4 addresses. The agent uses this attribute in tandem with the IPv4AddrOptions attribute. The ip route add command generally resembles: "ip route add IPv4RouteOptions dev device" Note: If Options attribute is configured, and none of IPv4AddrOptions and LinkOptions is configured, 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 for IPv6 addresses. The agent uses this attribute in tandem with the IPv6RouteOptions attribute. The ip addr add command resembles: "ip addr add ipv6addr/ prefixlen IPv6AddrOptions dev device" Type and dimension: string-scalar Example: "scope link"
IPv6RouteOptions	The extra options that are passed to the ip route add command for IPv6 addresses. The ip route add command generally resembles: "ip route add IPv6RouteOptions device dev" 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" Note: If you configure this attribute, the agent ignores the Options attribute and uses the ip command instead of ifconfig. 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 Example: NetworkHosts = { "2001::1", "192.123.10.129" }
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 any of the IPv4AddrOptions or LinkOptions attribute, the agent ignores Options attribute and uses ip command instead of ifconfig. 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 followed by a route add command. The command takes the options specified by 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 gw 166.98.16.103""
Mii	Flag that defines whether the NIC maintains its connection status. If this flag is set to 1, the agent uses ethtool and MII hardware registers, instead of the ping and packet count method. The agent uses this method to determine the health of the network card. If the flag is set to 0, the agent does not use ethtool and Mii to monitor the status of the NIC. Type and dimension: boolean-scalar Default: 1