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 DEBIAN
net::ipv4addr
IPv4Addr(3pm) User Contributed Perl Documentation IPv4Addr(3pm)
NAME
Net::IPv4Addr - Perl extension for manipulating IPv4 addresses.
SYNOPSIS
use Net::IPv4Addr qw( :all );
my ($ip,$cidr) = ipv4_parse( "127.0.0.1/24" );
my ($ip,$cidr) = ipv4_parse( "192.168.100.10 / 255.255.255.0" );
my ($net,$msk) = ipv4_network( "192.168.100.30" );
my $broadcast = ipv4_broadcast( "192.168.100.30/26" );
if ( ipv4_in_network( "192.168.100.0", $her_ip ) ) {
print "Welcome !";
}
etc.
DESCRIPTION
Net::IPv4Addr provides functions for parsing IPv4 addresses both in traditional address/netmask format and in the new CIDR format. There
are also methods for calculating the network and broadcast address and also to check if a given address is in a specific network.
ADDRESSES
All of Net::IPv4Addr functions accept addresses in many formats. The parsing is very liberal.
All these addresses would be accepted:
127.0.0.1
192.168.001.010/24
192.168.10.10/255.255.255.0
192.168.30.10 / 21
10.0.0.0 / 255.0.0.0
255.255.0.0
Those wouldn't though:
272.135.234.0
192.168/16
Most functions accepts the address and netmask or masklength in the same scalar value or as separate values. That is either
my($ip,$masklength) = ipv4_parse($cidr_str);
my($ip,$masklength) = ipv4_parse($ip_str,$msk_str);
USING
No functions are exported by default. Either use the ":all" tag to import them all or explicitly import those you need.
FUNCTIONS
ipv4_parse
my ($ip,$msklen) = ipv4_parse($cidr_str);
my $cidr = ipv4_parse($ip_str,$msk_str);
my ($ip) = ipv4_parse($ip_str,$msk_str);
Parse an IPv4 address and return in scalar context the address in CIDR format, in an array context the address and the mask length.
If the parameters doesn't contains a netmask or a mask length, in scalar context only the IPv4 address is returned and in an array
context the mask length is undefined.
If the function cannot parse its input, it croaks. Trap it using "eval" if you don't like that.
ipv4_broadcast
my ($broadcast) = ipv4_broadcast($ip_str);
my $broadcast = ipv4_broadcast($ip_str,$msk_str);
This function returns the broadcast address. If the input doesn't contain a netmask or mask length, the default netmask is assumed.
This function croaks if the input is invalid.
ipv4_network
my $cidr = ipv4_network($ip_str);
my $cidr = ipv4_network($cidr_str);
my ($net,$msk) = ipv4_network( $net_str, $msk_str);
In scalar context, this function returns the network in CIDR format in which the address is. In array context, it returns the network
address and its mask length as a two elements array. If the input is a host without a netmask or mask length, the default netmask is
assumed.
Again, the function croaks if the input is invalid.
ipv4_in_network
print "Yes" if ipv4_in_network( $cidr_str1, $cidr_str2);
print "Yes" if ipv4_in_network( $ip_str1, $mask_str1, $cidr_str2 );
print "Yes" if ipv4_in_network( $ip1, $mask1, $ip2, $msk2 );
This function checks if the second network is contained in the first one and it implements the following semantics :
If net1 or net2 is a magic address (0.0.0.0 or 255.255.255.255)
then this function returns true.
If net1 is a host, net2 will be in the same net only if
it is the same host.
If net2 is a host, it will be contained in net1 only if
it is part of net1.
net2 is only part of net1 if it is entirely contained in
net1.
Trap bad input with "eval" or else.
ipv4_chkip
if ($ip = ipv4_chkip($str) ) {
# Do something
}
Return the IPv4 address in the string or undef if the input doesn't contain a valid IPv4 address.
ipv4_cidr2msk
my $netmask = ipv4_cidr2msk( $cidr );
Returns the netmask corresponding to the mask length given in the input. As usual, croaks if it doesn't like your input (in this case
a number between 0 and 32).
ipv4_msk2cidr
my $masklen = ipv4_msk2cidr( $msk );
Returns the mask length of the netmask in the input. As usual, croaks if it doesn't like your input.
AUTHOR
Francis J. Lacoste <francis.lacoste@iNsu.COM>
COPYRIGHT
Copyright (c) 1999, 2000 iNsu Innovations Inc. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the terms as perl itself.
SEE ALSO
perl(1) ipv4calc(1).
perl v5.10.1 2010-07-26 IPv4Addr(3pm)