InfoScale™ Cluster Server 9.0 Bundled Agents Reference Guide - Solaris
- Introducing bundled agents
- Storage agents
- DiskGroup agent
- DiskGroupSnap agent
- Notes for DiskGroupSnap agent
- Sample configurations for DiskGroupSnap agent
- Disk agent
- Volume agent
- VolumeSet agent
- Sample configurations for VolumeSet agent
- Mount agent
- Sample configurations for Mount agent
- Zpool agent
- VMwareDisks agent
- SFCache agent
- Network agents
- About the network agents
- IP agent
- NIC agent
- About the IPMultiNICB and MultiNICB agents
- IPMultiNICB agent
- Sample configurations for IPMultiNICB agent
- MultiNICB agent
- Sample configurations for MultiNICB agent
- DNS agent
- Agent notes for DNS agent
- About using the VCS DNS agent on UNIX with a secure Windows DNS server
- Sample configurations for DNS agent
- File share agents
- NFS agent
- NFSRestart agent
- Share agent
- About the Samba agents
- NetBios agent
- Service and application agents
- AlternateIO agent
- Apache HTTP server agent
- Application agent
- Notes for Application agent
- Sample configurations for Application agent
- CoordPoint agent
- LDom agent
- Dependencies
- Process agent
- Usage notes for Process agent
- Sample configurations for Process agent
- ProcessOnOnly agent
- Project agent
- RestServer agent
- Zone agent
- Infrastructure and support agents
- Testing agents
- Replication agents
Attributes for NIC agent
Table: Required attributes
Required attribute | Description |
---|---|
Device | Name of the NIC that you want to monitor. Type and dimension: string-scalar Example: "e1000g0" |
Table: Optional attributes
Optional attribute | Description |
---|---|
BroadcastTest | Specifies whether to perform a ping test on the broadcast address that is present on the NIC as part the monitor operation. The ping test determines whether the network connection is alive. This attribute is used if the ping test on the hosts specified in the NetworkHosts attribute fails. Disable this attribute if you want to perform the ping test only on the hosts provided in NetworkHosts. Type-dimension: boolean-scalar Default: 1 |
ExclusiveIPZone | ExclusiveIPZone Specifies that a resource is configured for an exclusive IP zone. Set this value to 1 if a resource is configured for exclusive IP zone. When set to 1, it requires a valid ContainerInfo to be configured in the service group. Type-dimension: boolean-scalar Default: 0 |
NetworkHosts | List of hosts on the network that are pinged to determine if the network connection is alive. You can use this attribute to help to save network capacity and reduce monitor time. Arctera recommends that you use the outgoing gateway routers for this value. Enter the IP address of the host, instead of the host name, to prevent the monitor from timing out. DNS causes the ping to hang. If more than one network host is listed, the monitor returns ONLINE if at least one of the hosts is alive. If an invalid network host address is specified, the resource enters an UNKNOWN state. If you do not specify network hosts, the monitor tests the NIC by sending pings to the broadcast address on the NIC. Type and dimension: string-vector Example: { "166.93.2.1", "166.99.1.2", "2620:128:f0a2:9005::1" } |
NetworkType | Type of network. VCS supports only Ethernet. Type and dimension: string-scalar Default: "ether" |
PingOptimize |
Determines whether to ping during every monitor cycle. The value can be:
Type and dimension: integer-scalar Default: 1 |
PingTest | Specifies whether to perform a ping test on the NIC:
Type-dimension: boolean-scalar Default: 1 |
LinkTest | Determines whether the network connection is alive by checking the link status on the data-link layer.
Type and dimension: boolean-scalar Default: 0 |