All of these questions seem to be Solaris related and not Veritas Cluster.
Why on earth would you want to nfs share swap? IMHO, not a good idea, even if you might be able to accomplish this. Swap should be a partition on local disk.
Copy bash from another system.
Change zone ip - again, Solaris question...
http://learningsolaris.com/zones-unofficial-faq/#3.5
3.5 : Can I change a non-global zone IP while it is running?
Yes. Just use the “ifconfig” command from the Global zone. Don’t forget to also update the non-global zone’s configuration if you want the change to be persistent.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows. Handy NBU links
Swap space is disk space where the process manager puts main memory pieces to provide more available RAM to the online processes. Swap space has no internal structure, the process manager (or to be more accurate: the memory manager of the operating system) writes data without any organizational structures to this space. The only one who knows where the data is is the memory manager.
And there is the main problem in accessing swap space. The access to those data is not "blocked" in any way. That means, that you have a extremely differing "access size" to the swapped data, and this cannot be handled very good by the I/O drivers. Optimization in the drivers and for the NFS filesystem is not possible. It is said, that swap space because of the many small I/O's, has a very big impact to the "networked filesystem", no matter if networked means SAN, NFS, iSCSI. So keep away from networked swap as long as you can, for sake of networking performance and system health!
And IP in zones: a zone from the abstract view is a normal OS instance. Just use the normal instruments like ifconfig.
The mkfile command creates a file that is suitable for use either as an NFS-mounted or local swap area. The sticky bit is set, and the file is filled with zeros. You can specify the size of the swap file in bytes (the default) or in kilobytes, blocks, or megabytes using the k, b, or m suffixes, respectively.
The table below shows the options to the mkfile command.
Option
Description
-n
Creates an empty file. The size is noted, but the disk blocks are not allocated until data is written to them.
-v
Verbose. Reports the names and sizes of created files.
Use the -n option only when creating an NFS swap file.
Re adding the zone ip :
Run the below command on global zone to add the IP temporarily in local zone:
# ifconfig <cex:x> <ip/subnetmask> + up zone <zone name>
For adding ip permanently, update the local zone configuration.
Comments
All of these questions seem
All of these questions seem to be Solaris related and not Veritas Cluster.
Why on earth would you want to nfs share swap? IMHO, not a good idea, even if you might be able to accomplish this. Swap should be a partition on local disk.
Copy bash from another system.
Change zone ip - again, Solaris question...
http://learningsolaris.com/zones-unofficial-faq/#3.5
3.5 : Can I change a non-global zone IP while it is running?
Yes. Just use the “ifconfig” command from the Global zone. Don’t forget to also update the non-global zone’s configuration if you want the change to be persistent.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
Never share swap!
Swap space is disk space where the process manager puts main memory pieces to provide more available RAM to the online processes. Swap space has no internal structure, the process manager (or to be more accurate: the memory manager of the operating system) writes data without any organizational structures to this space. The only one who knows where the data is is the memory manager.
And there is the main problem in accessing swap space. The access to those data is not "blocked" in any way. That means, that you have a extremely differing "access size" to the swapped data, and this cannot be handled very good by the I/O drivers. Optimization in the drivers and for the NFS filesystem is not possible. It is said, that swap space because of the many small I/O's, has a very big impact to the "networked filesystem", no matter if networked means SAN, NFS, iSCSI. So keep away from networked swap as long as you can, for sake of networking performance and system health!
And IP in zones: a zone from the abstract view is a normal OS instance. Just use the normal instruments like ifconfig.
You can use NFS for swap but not suggestable.
Create a file using mkfile with -n option.
The mkfile command creates a file that is suitable for use either as an NFS-mounted or local swap area. The sticky bit is set, and the file is filled with zeros. You can specify the size of the swap file in bytes (the default) or in kilobytes, blocks, or megabytes using the k, b, or m suffixes, respectively.
The table below shows the options to the mkfile command.
Use the -n option only when creating an NFS swap file.
Re adding the zone ip :
Run the below command on global zone to add the IP temporarily in local zone:
# ifconfig <cex:x> <ip/subnetmask> + up zone <zone name>
For adding ip permanently, update the local zone configuration.
Would you like to reply?
Login or Register to post your comment.