04-03-2009
Veritas Cluster Server Management Console IP Failover
I have just completed a first RTFM of "Veritas Cluster Server Management Console Implementation Guide" 5.1, with a view to assessing it to possibly make our working lives easier.
Unfortunately, at my organisation, getting a test installation would be worse than pulling teeth, so I can't just go and suck it and see.
If one uses this product to failover a SG from a local cluster to a remote one cluster, how are the changes to the attributes of the IP resources handled?
e.g.
local SG = sg_local
IP resource name = ip_local
ip_local has attributes address=192.168.1.2, netmask 255.255.255.0
But suppose I fail sg_local to a remote cluster at our DR site, we require
address = 168.1.2.3, netmask 255.255.255.0
Can one configure this information?
Currently we do such failover manually, and we maintain the "DR-version" of main.cf on the target DR cluster.
10 More Discussions You Might Find Interesting
1. High Performance Computing
Hello,
This might not be the right place to post my questions.
- I installed VCS 5.0 on the 2 nodes. What's next? I want to test the HA of NFS: i.e. the shared disk always accessible if one node goes down. How to do that?
- The management console was not installed. This is the GUI to manage... (2 Replies)
Discussion started by: melanie_pfefer
2 Replies
2. Solaris
Is it possible to configure veritas cluster server using 2 Ldoms on same host? I just want to test and learn VCS. We can do a cluster (sun cluster3.2 ) in a box using 2 Ldoms but i 'm not sure if thats possible with veritas cluster or not ? (1 Reply)
Discussion started by: fugitive
1 Replies
3. Solaris
Hi,
We have two sun SPARC server in Clustered (Sun Cluster 3.1). For some reason, System 1 failed over to System 2. Where can I find the logs which could tell me the reason for this failover?
Thanks (5 Replies)
Discussion started by: Mack1982
5 Replies
4. Solaris
Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC.
Am thinking how to migrate to sun cluster setup instead.
My plan as follows leave the existing vcs intact as a fallback plan.
Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies
5. Gentoo
How to failover the cluster ? GNU/Linux
By which command,
My Linux version
2008 x86_64 x86_64 x86_64 GNU/Linux
What are the prerequisites we need to take while failover ?
if any
Regards (3 Replies)
Discussion started by: sidharthmellam
3 Replies
6. UNIX for Advanced & Expert Users
Hello,
Usually I use "vxresize" to grow vxfs directory in a stand-alone server without any problems, but I am just told to grow vxfs directorys in Veritas Cluster nodes.
Since I never done it before, would like to ask all the experts here to make sure the concept and steps will be fine... (1 Reply)
Discussion started by: sunnychen98
1 Replies
7. Solaris
Hello experts -
I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts.
(1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over)
(2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies
8. Solaris
Until I really began to explore the practical implications of using ZFS with VCS, I would not have necessarily realised the obstacles that would be put in my path. Data integrity is a must-have for storage in a shared host environment, so it surprised me to learn as I opened this particular... (0 Replies)
Discussion started by: cambridge
0 Replies
9. Red Hat
Hi Guys,
I am not much aware of clusters but i have few questions can someone provide the overview as it would be very helpful for me.
How can i perform cluster failover test to see all the services are failing back to other node ? If it is using veritas cluster then what kind of... (2 Replies)
Discussion started by: munna529
2 Replies
10. UNIX for Beginners Questions & Answers
Hi Experts,
I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system.
#hastatus -sum
-- System State Frozen
A node1 running 0
A node2 running 0
-- Group State
-- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies
LEARN ABOUT HPUX
securenets
securenets(4) Kernel Interfaces Manual securenets(4)
NAME
securenets - NIS map security file
DESCRIPTION
The file defines networks and hosts that can access the NIS maps on a server. Each line in the file gives a network mask and a net
address. For example:
The format of the file is as follows:
o Lines beginning with the character are treated as comments.
o Lines that are not comment lines contain two fields separated by white space. The first field is a netmask, and the second field is a
network.
o The netmask field can be one of the following:
o 255.255.255.255 (IPv4)
o ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff (IPv6)
o the string indicating that the second field is a specific host to be allowed access.
The file can have any number of netmask/net pairs.
When is started on the server, it checks for the existence of and reads its contents into memory if it exists. must be stopped and
restarted for any changes in to take effect.
Upon startup, the netmask and the net address are converted to binary format and logical ANDed. The result must equal the net address (the
second address) to be legal.
If the netmask is 255.255.255.255 (all 1's in binary), any address in the net address argument will match it. If any field in the netmask
is 0, the corresponding field in the net address must be 0. When used in this way, the portion of the addresses given as 0 acts as a wild
card.
When a client attempts to bind to the server, checks the client's IP against those given in the file. Again, the address is converted to
binary and logical ANDed with the netmask. The result must equal the net address given in the file. If the client address does not match
any pairs in the file, the binding is refused with the message, "no such map in server's NIS domain".
The file can be used to limit access to specific hosts or to subnets using the wildcard capability.
If there are syntax errors in the file, messages are logged to the logging file (default and is not started.
If a host has multiple interfaces, each interface address must be allowed in the securenets file for that host to have reliable NIS access.
EXAMPLES
The following examples show entries for the file.
Either of the following entries provides access only to the host with address 192.33.33.33:
or
The following entry allows access by any host on the 192.33.33 subnet:
For broader access, such as an entire enterprise, the following entry allows any host whose address begins with "15" to be served:
Either of the following entries allows access for an individual IPv6 address:
or
The following entry allows access for all IPv6 addresses starting with "fec0":
SEE ALSO
ypserv(1M).
securenets(4)