Login or Register to Ask a Question and Join Our Community


Solaris

Veritas I/O fencing issue on Solaris10

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris Veritas I/O fencing issue on Solaris10
# 1  
Old 01-28-2011
Veritas I/O fencing issue on Solaris10
I have 2 clusters running on solaris10 servers. VCS is working fine but when i configure I/O fencing with co-ordinated disks only one node have the keys on the disks at time where as both the nodes shuld have keys there what could be the reason for this ?

like in the following o/p only Node2's reservation are seen .. and if i will restart the vxfencing on node1 .. it will show node1's keys


Code:
vxfenadm -s all -f /etc/vxfentab
 
Device Name: /dev/vx/rdmp/emc_clariion0_17s2
Total Number Of Keys: 1
key[0]:
        [Numeric Format]:  86,70,48,48,48,49,48,49
        [Character Format]: VF000101
   *    [Node Format]: Cluster ID: 1     Node ID: 1   Node Name: Node2
 
Device Name: /dev/vx/rdmp/emc_clariion0_18s2
Total Number Of Keys: 1
key[0]:
        [Numeric Format]:  86,70,48,48,48,49,48,49
        [Character Format]: VF000101
   *    [Node Format]: Cluster ID: 1     Node ID: 1   Node Name: Node2
 
Device Name: /dev/vx/rdmp/emc_clariion0_19s2
Total Number Of Keys: 1
key[0]:
        [Numeric Format]:  86,70,48,48,48,49,48,49
        [Character Format]: VF000101
   *    [Node Format]: Cluster ID: 1     Node ID: 1   Node Name: Node2


P.S:Mods ,If this is not the rt place to post my question for Veritas plz delete this thread.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

How to extend a disk in veritas volume manager in veritas cluster?

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

2. Solaris

VNC issue on solaris10

M running solaris 10 u8 my vncserver is running on :0 .. and when i try to connect it through tight vncview i can see just see the screen .. with no terminal .. what could be the issue for it ? and what i need to check for it ? (2 Replies)
Discussion started by: fugitive
2 Replies

3. Solaris

Swap issue on a Solaris10 box

One of our system is running 3 oracle db instances. And as per prstat o/p the system is approximately using 78G of swap memory # prstat -J -n 2,15 PROJID NPROC SWAP RSS MEMORY TIME CPU PROJECT 4038 557 31G 29G 22% 113:23:43 10% proj1 4036 466 20G 19G... (2 Replies)
Discussion started by: fugitive
2 Replies

4. Solaris

/tmp issue on solaris10 box

I have a T5240 server with following swap configuration $ grep tmp /etc/vfstab swap - /tmp tmpfs - yes - $ swap -l swapfile dev swaplo blocks free /dev/swap 4294967295,4294967295 16 213909472 213909472 ... (4 Replies)
Discussion started by: fugitive
4 Replies

5. Solaris

Memory issue on solaris10 box

my system has 128G of installed memory. top, vmstat shows the system has just over 10G of free memory on the system. but as per prstat o/p the usage is just 50-55G is there anyway i can find which process/zone is using more memory ? System has 3 zones and all running application servers. ... (1 Reply)
Discussion started by: fugitive
1 Replies

6. Solaris

Solaris10

Hi All How can we verify if any of the parameters we have change in Solaris10 after reboot. Like is there any command? Please advice Thanks (3 Replies)
Discussion started by: imran721
3 Replies

7. Solaris

Modify the swap on Solaris10 on a volume VERITAS

Hi Community, Do you know a procedure to modify the swap on Solaris10 on a volume VERITAS? Please help me I'm currently working on this issue. Thank you for your availability! (1 Reply)
Discussion started by: Sunb3
1 Replies

8. Shell Programming and Scripting

portability issue linux(2.6) solaris10

the following simple scripts work fine on linux but fail on solaris: #!/bin/bash eval /usr/bin/time -f \'bt=\"%U + %S\"\' ./JUNK >> ./LOG 2>&1 cp ./LOG ./LOG_joe LC_joe=`cat ./LOG | wc -l` LC_joe=`echo $LC_joe-1|bc` tail -1 ./LOG > ./tmp head -$LC_joe ./LOG_joe > ./LOG rm ./LOG_joe ... (1 Reply)
Discussion started by: joepareti
1 Replies

9. Red Hat

Redhat Cluster Fencing failed

Hello; I have 2 node Redhat Cluster (RHEL4 U4 and Cluster Suite) I'm using mc_data fiber channel switch for fencing when I want to fence manually using fence_mcdata -a x.x.x. -l xxx -p xxxx -n 5 -o disable following messages appears fencing node "test1" agent "fence_mcdata" reports:... (0 Replies)
Discussion started by: sakir19
0 Replies

10. Solaris

help,win2003 and solaris10 in a pc?

sorry,my english is poor. who can install win2003 and solaris10 in one pc ? my win2000server in hda1 so frist install win2003 in hda5 second install solaris10 in hda2 but after install over,the win2003 can't logon in. alway let me press<ctrl>+<alt>+<del>. why? (1 Reply)
Discussion started by: keyi
1 Replies
Login or Register to Ask a Question

LEARN ABOUT CENTOS

fence_kdump

fence_kdump(8)						      System Manager's Manual						    fence_kdump(8)

NAME

       fence_kdump - fencing agent for use with kdump crash recovery service

SYNOPSIS

       fence_kdump [OPTIONS]...

DESCRIPTION

       fence_kdump is an I/O fencing agent to be used with the kdump crash recovery service. When the fence_kdump agent is invoked, it will listen
       for a message from the failed node that acknowledges that the failed node it executing the kdump crash kernel.  Note  that  fence_kdump	is
       not  a  replacement for traditional fencing methods. The fence_kdump agent can only detect that a node has entered the kdump crash recovery
       service. This allows the kdump crash recovery service complete without being preempted by traditional power fencing methods.

OPTIONS

       -n, --nodename=NODE
	      Name or IP address of node to be fenced. This option is required for the "off" action. (default: none)

       -p, --ipport=PORT
	      IP port number that the fence_kdump agent will use to listen for messages. (default: 7410)

       -f, --family=FAMILY
	      IP network family. Force the fence_kdump agent to use a specific family. The value for FAMILY can  be  "auto",  "ipv4",  or  "ipv6".
	      (default: auto)

       -o, --action=ACTION
	      Fencing action to perform. The value for ACTION can be either "off" or "metadata". (default: off)

       -t, --timeout=TIMEOUT
	      Numer  of  seconds  to  wait  for  message from failed node. If no message is received within TIMEOUT seconds, the fence_kdump agent
	      returns failure. (default: 60)

       -v, --verbose
	      Print verbose output.

       -V, --version
	      Print version and exit.

       -h, --help
	      Print usage and exit.

STDIN PARAMETERS

       These parameters are passed to fence_kdump via standard input if no command-line options are present.

       nodename=NODE
	      Name or IP address of node to be fenced. This option is required for the "off" action. (default: none)

       ipport=PORT
	      IP port number that the fence_kdump agent will use to listen for messages. (default: 7410)

       action=ACTION
	      Fencing action to perform. The value for ACTION can be either "off" or "metadata". (default: off)

       timeout=TIMEOUT
	      Numer of seconds to wait for message from failed node. If no message is received	within	TIMEOUT  seconds,  the	fence_kdump  agent
	      returns failure. (default: 60)

ACTIONS

       off    Listen  for message from failed node that acknowledges node has entered kdump crash recovery service. If a valid message is received
	      from the failed node, the node is considered to be fenced and the agent returns success. Failure to receive a valid message from the
	      failed node in the given timeout period results in fencing failure.

       metadata
	      Print XML metadata to standard output.

AUTHOR

       Ryan O'Hara <rohara@redhat.com>

SEE ALSO

       fence_kdump_send(8), fenced(8), fence_node(8)

																    fence_kdump(8)