Veritas Volume Manager is a storage management application by Symantec , which allows you to manage physical disks as logical devices called volumes.
VxVM uses two types of objects to perform the storage management
1. Physical objects - are direct mappings to physical disks
2 . Virtual objects - are volumes, plexes, subdisks and diskgroups.
a. Disk groups are composed of Volumes
b. Volumes are composed of Plexes and Subdisks
c. Plexes are composed of SubDisks
d. Subdisks are actual disk space segments of VxVM disk ( directly mapped from the physical disks)
Boot arguments may include more than one string. All argument strings are passed to the secondary boot program; they are not interpreted by OpenBoot. If any arguments are specified on the boot command line, then neither the boot-file nor the diag-file nvram variable is used. The contents of the nvram variables are not merged with command line arguments.
For example, the command
ok boot -s
ignores the settings in both boot-file and diag-file; it interprets the string “-s” as arguments. boot will not use the contents of boot-file or diag-file. The commands
ok boot net
ok boot cdrom
have no arguments; they will use the settings in boot-file or diag-file, if they are set, as default filename and arguments and pass them to boot. Accordingly, if boot-file is set to the 64-bit kernel filename and you attempt to boot the installation CD with boot cdrom, boot will fail if the installation CD contains only a 32-bit kernel.
A. Common boot Syntax
ok boot [device-specifier] [arguments]
This behavior is found on most OpenBoot 2.x and 3.x based systems. Note that differences may occur on some platforms. Full Story
* mpathd error messages in /var/adm/messages:
“No test address configured on interface <interface_name> disabling probe-based failure detection on it”
“Test address address is not unique; disabling probe based failure detection on <interface_name>”
“The link has gone down on <interface_name>”
“Successfully failed over from NIC <interface_name1> to NIC <interface_name2>
“NIC repair detected on <interface_name>”
“Successfully failed back to NIC <interface_name>”
“The link has come up on <interface_name>” Full Story
The command, zonecfg, has no provision for defining the netmask of network resources. Modifying /etc/netmask file resident within the designated zone does not configure the netmask of the new interface. This procedure details how to set the netmask of a network resource within a zone to the desired value. Full Story