InfoScale™ Cluster Server 9.0 Bundled Agents Reference Guide - Solaris

Failback

If the value of the attribute is 1, the virtual IP addresses are failed back to the original physical interface whenever possible. A value of 0 disables this behavior.

Type and dimension: integer-scalar

Default: 0

IgnoreLinkStatus

If the value of the attribute is 1, the agent ignores the driver-reported interface status while testing the interfaces. If the value of the attribute is 0, the agent reports the interface status as DOWN if the driver-reported interface status indicates the DOWN state. Using interface status for link testing may considerably speed up failovers.

When you use trunked interfaces, you must set the value of this attribute to 1. Otherwise set it to 0.

Type and dimension: integer-scalar

Default: 1

LinkTestRatio

This attribute is the ratio of:

At all other times, the agent tests the link by checking the "link-status" as reported by the device driver. Checking the "link-status" is a faster way to check the interfaces, but only detects cable disconnection failures.

If the value of the attribute is 1, packets are sent during every monitor cycle.

If the value of the attribute is 0, packets are never sent during a monitor cycle. Do not set the value of this attribute to 0 when its corresponding IPMultiNICB resource's IgnoreMultiNICBFailure attribute has a value of 1.

Value of this attribute has no effect when IgnoreLinkStatus attribute is set to 1. In such scenario, packets are sent during every monitor cycle to determine the state of an interface.

Type and dimension: integer-scalar

Default: 1

Example: "3"

In this example, if monitor entry-point invoking is numbered as 1, 2, 3, 4, 5, 6, ..., the actual packet send test is done at 3, 6, etc. monitor agent functions. For LinkTestRatio=4, the packet send test is done at 4, 8, etc., monitor agent functions.

NetworkHosts

List of host IP addresses on the IP subnet that are pinged to determine if the interfaces work. NetworkHosts only accepts IP addresses to avoid DNS lookup delays. The IP addresses must be directly present on the IP subnet of interfaces (the hosts must respond to ARP requests).

If IP addresses are not provided, the hosts are automatically determined by sending a broadcast ping (unless the NoBroadcast attribute is set to 1). The first host to reply serves as the ping destination.

Type and dimension: string-vector

Example: { "2620:128:f0a2:9001::1", "10.209.72.1" }

NetworkTimeout

Timeout for ARP and ICMP packets in milliseconds. MultiNICB waits for response to ICMP and ARP packets only during this time period.

Assign NetworkTimeout a value in the order of tens of milliseconds (given the ICMP and ARP destinations are required to be on the local network). Increasing this value increases the time for failover.

Type and dimension: integer-scalar

Default: 100

NoBroadcast

If the value of the attribute is 1, NoBroadcast prevents MultiNICB from sending broadcast ICMP packets. Note that MultiNICB can still send ARP requests.

If NetworkHosts are not specified and NoBroadcast is set to 1, the MultiNICB agent cannot function properly.

Type and dimension: integer-scalar

Default: 0

OfflineTestRepeatCount

Number of times the test is repeated if the interface status changes from UP to DOWN. For every repetition of the test, the next NetworkHost is selected in round-robin manner. At the end of this process, broadcast is performed if NoBroadcast is set to 0. A greater value prevents spurious changes, but also increases the response time.

Type and dimension: integer-scalar

Default: 3

OnlineTestRepeatCount

Number of times the test is repeated if the interface status changes from DOWN to UP. This test helps to avoid oscillations in the status of the interface.

Type and dimension: integer-scalar

Default: 3