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
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 and vxspec drivers, enter:
# grep '^vx' /etc/name_to_major
The following output is displayed:
.. vxio 327 vxspec 328 ..
To determine the major numbers available on the system, check the /etc/name_to_major
file and use the unassigned numbers.
To reassign the major numbers to the vxio and vxspec drivers, enter:
# haremajor -vx major-number-vxio major-number-vxspec
For example:
# haremajor -vx 338 339 haremajor 1.1 Using the following major number(s): 338 339 Do you want to continue [y/n]? y Updating /etc/name_to_major If there are any problems, you can backout the changes by restoring the following files: - /etc/name_to_major.off.3409 To complete re-majoring, reboot your machine with the following command: reboot
Note:
If you assign a major number, you must reboot the node.
For more information, refer to the haremajor command manual page.