InfoScale™ Cluster Server 9.0 Bundled Agents Reference Guide - AIX
- Introducing bundled agents
- Storage agents
- DiskGroup agent
- Notes for DiskGroup agent
- Sample configurations for DiskGroup agent
- DiskGroupSnap agent
- Notes for DiskGroupSnap agent
- Sample configurations for DiskGroupSnap agent
- Volume agent
- VolumeSet agent
- Sample configurations for VolumeSet agent
- LVMVG agent
- Notes for LVMVG agent
- Mount agent
- Sample configurations for Mount agent
- SFCache agent
- Network agents
- About the network agents
- IP agent
- NIC agent
- IPMultiNIC agent
- MultiNICA 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
- Notes for configuring the Samba agents
- SambaServer agent
- SambaShare agent
- NetBios agent
- Service and application agents
- Apache HTTP server agent
- Application agent
- Notes for Application agent
- Sample configurations for Application agent
- CoordPoint agent
- LPAR agent
- Notes for LPAR agent
- MemCPUAllocator agent
- MemCPUAllocator agent notes
- Process agent
- Usage notes for Process agent
- Sample configurations for Process agent
- ProcessOnOnly agent
- RestServer agent
- WPAR agent
- Infrastructure and support agents
- Testing agents
- Replication agents
Using the DiskGroup agent with NFS
If the file systems on the VxVM volumes are shared using NFS, you must make sure that the major number of all the volumes across the cluster nodes are consistent. By making the vxio driver numbers consistent for all nodes in a VCS cluster, it makes volume major numbers consistent on all the cluster nodes.
NFS clients know the major and minor numbers of the block device containing the file system exported by the NFS server, so when making the NFS server highly available, it is important to make sure that all nodes in the cluster that can act as NFS servers have the same major and minor numbers for the volume block device.
To determine the current value assigned to the vxio driver, enter:
# haremajor -v
For example:
# haremajor -v 43
To determine the available major numbers on the system, enter:
# haremajor -a
For example:
# haremajor -a 51...
To reassign the vxio driver number on the system to a specified number, enter:
# haremajor -s vxio-major-number
For example:
# haremajor -s 51 vxio major number changed to 51 reboot the system so VxVM can restart its volumes using this major number
For more information, refer to the haremajor command manual page.