10-17-2014
Don't take this as a definitive process. I really recommend that you talk to your supplier. Suggest it to them if you wish, but make sure that they confirm the official sequence.
I may have left something out and you should not rely on my thoughts for something so critical that may be difficult to recover from.
Regards,
Robin
9 More Discussions You Might Find Interesting
1. High Performance Computing
Weird question I know, but I'm intrigued.
Say for instance you have an Application in an SG with the usual start/stop/monitor. To successfully probe does it just check for existence of the script/file ?
Thanks... (1 Reply)
Discussion started by: itsupplies
1 Replies
2. Solaris
Hi,
Is it possible to have a Solaris cluster of 2 nodes at SITE-A using SVM and creating metaset using say 2 LUNs (on SAN). Then replicating these 2 LUNs to remote site SITE-B via storage based replication and then using these LUNs by importing them as a metaset on a server at SITE-B which is... (0 Replies)
Discussion started by: dn2011
0 Replies
3. Solaris
:)Hi,
can someone please explain VCS clustering and where do we need VCS clusters ..?
:o:)Thanks in advance :o:) (1 Reply)
Discussion started by: amitbisht9
1 Replies
4. Solaris
hi, dear all
I get a problem "VCS ERROR V-16-2-13077 " on VCS 4.1 for Solaris 10.
I can not offline the host2 when the raid is bad.
I don't know the reason and how to offline host2 and switch to host1.
please help me, thank you!
the message of engine_A.log is :
... (2 Replies)
Discussion started by: ForgetChen
2 Replies
5. UNIX for Advanced & Expert Users
We have two node cluster with OS disk mirrored under SVM. There is slight disk problem on one of the mirror disk causing cluster to panic.
Failure of one mirror disk causing VCS to panic the node. Why VCS is not able to write /var filesystem, as one of the disk is healthy.
... (1 Reply)
Discussion started by: amlanroy
1 Replies
6. Homework & Coursework Questions
Hi Experts,
I am in need of running a script from one node say node 1 via node 2.
My scheduling tool dont have access to node2 , so i need to invoke the list file from node1 but the script needs to run from node2. because the server to which i am hitting, is having access only for the node... (5 Replies)
Discussion started by: arun1377
5 Replies
7. HP-UX
Hi,
We have HP UX service guard cluster on OS 11.23. Recently 40+ LUNs presented to both nodes by SAN team but I was asked to mount them on only one node. I created required VGs/LVs, created VxFS and mounted all of them and they are working fine. Now client requested those FS on 2nd node as... (4 Replies)
Discussion started by: prvnrk
4 Replies
8. AIX
Hi Folks,
I'm currently in a position where I am building the seed equipment for a Data Centre Migration, I'm familiar with some of the equipment - all of which I've listed below.
SAN Storage - EMC VNX5800
SAN Switches - Brocade DCX 8510-4
SAN Management - IBM SVC 2145-DH8 four node cluster... (2 Replies)
Discussion started by: gull04
2 Replies
9. Solaris
Dear All,
My current system run Solaris 9 SPARC 64 bit , and VXVM , VCS 4.1. I check all the node information .
ls -l /etc/vx/*.exclude
/etc/vx/*.exclude: No such file or directory
root@devuardbs01 # vxdctl license
All features are available:
Mirroring
Root Mirroring
Concatenation... (0 Replies)
Discussion started by: linux_user
0 Replies
TALK(1) BSD General Commands Manual TALK(1)
NAME
talk -- talk to another user
SYNOPSIS
talk person [ttyname]
DESCRIPTION
talk is a visual communication program which copies lines from your terminal to that of another user.
Options available:
person If you wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on
another host, then person is of the form 'user@host'.
ttyname If you wish to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal
name, where ttyname is of the form 'ttyXX'.
When first called, talk sends the message
Message from TalkDaemon@his_machine...
talk: connection requested by your_name@your_machine.
talk: respond with: talk your_name@your_machine
to the user you wish to talk to. At this point, the recipient of the message should reply by typing
talk your_name@your_machine
It doesn't matter from which machine the recipient replies, as long as his login-name is the same. Once communication is established, the
two parties may type simultaneously, with their output appearing in separate windows. Typing control-L '^L' will cause the screen to be
reprinted, while your erase, kill, and word kill characters will behave normally. To exit, just type your interrupt character; talk then
moves the cursor to the bottom of the screen and restores the terminal to its previous state.
Permission to talk may be denied or granted by use of the mesg(1) command. At the outset talking is allowed. Certain commands, in particu-
lar nroff(1) and pr(1), disallow messages in order to prevent messy output.
ENVIRONMENT
If the TALKHOST environment variable is set, its value is used as the hostname the talk packets appear to be originating from. This is use-
ful if you wish to talk to someone on another machine and your internal hostname does not resolve to the address of your external interface
as seen from the other machine.
FILES
/etc/hosts to find the recipient's machine
/var/run/utmp to find the recipient's tty
SEE ALSO
mail(1), mesg(1), who(1), write(1)
HISTORY
The talk command appeared in 4.2BSD.
BUGS
The version of talk released with 4.3BSD uses a protocol that is incompatible with the protocol used in the version released with 4.2BSD.
BSD
January 7, 2007 BSD