08-22-2010
No Luck,
Any one, Did any details required in my questions
?
---------- Post updated at 05:02 PM ---------- Previous update was at 04:35 PM ----------
My Linux version
Red Hat Enterprise Linux Server release 5.2 (Tikanga)
Regards
10 More Discussions You Might Find Interesting
1. High Performance Computing
I have rcently setup a 4 node cluster running sun cluster 3.2
and I have installed 4 zones on each node. when installing the zones I had to install the zone on all nodes the on the last node do a zlogin -C <zonename>
this worked ok.
theni I tried to siwitch the zone to node a thei work... (14 Replies)
Discussion started by: lesliek
14 Replies
2. High Performance Computing
Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris.
More... (0 Replies)
Discussion started by: Linux Bot
0 Replies
3. HP-UX
I have a 2-node ServiceGuard cluster. One of the cluster packages has a volume group assigned to it. When I fail the package over to the other node, the volume group does not come up automatically on the other node.
I have to manually do a "vgchange -a y vgname" on the node before the package... (5 Replies)
Discussion started by: Wotan31
5 Replies
4. High Performance Computing
Dear All,
Can anyone explain about Pros and Cons of SUN and Veritas Cluster ?
Any comparison chart is highly appreciated.
Regards,
RAA (4 Replies)
Discussion started by: RAA
4 Replies
5. High Performance Computing
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... (2 Replies)
Discussion started by: Beast Of Bodmin
2 Replies
6. 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
7. 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
8. 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
9. Solaris
Dear Experts,
If there is a possible Solaris Cluster failover to second node based on scan rate?
I need the documentation If solaris cluster can do this.
Thank You in Advance
Edy (3 Replies)
Discussion started by: edydsuranta
3 Replies
10. 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
LEARN ABOUT CENTOS
rhnreg_ks
RHNREG_KS(8) Red Hat, Inc. RHNREG_KS(8)
NAME
rhnreg_ks - A program for non interactively registering systems to Spacewalk Server, Red Hat Satellite or Red Hat Network Classic.
SYNOPSIS
rhnreg_ks [options]
DESCRIPTION
rhnreg_ks is a utility for registering a system with the "Spacewalk Server", "Red Hat Satellite" or "Red Hat Network Classic". It is
designed to be used in a non-interactive environment (a kickstart style install, for example). All the information can be specified on
the command line or stdin.
OPTIONS
--profilename
Specify the profile name that should be used as an identifier for the system in Spacewalk Server, Red Hat Satellite or Red Hat Net-
work Classic
--username
The username to register the system with under Spacewalk Server, Red Hat Satellite or Red Hat Network Classic. This can be an exist-
ing Spacewalk, Red Hat Satellite or Red Hat Network Classic username, or a new username.
--password
The password associated with the username specified with the --username option. This is an unencrypted password.
--activationkey
Specify/use a serial number to associate with the system. This is optional, but activation keys can really simplify the registration
process. Learn more about activation keys in the online RHN documentation.
--contactinfo
This option has been deprecated. Please login to the server web user interface and update your contactinfo.
--nohardware
Do not probe or upload any hardware information.
--nopackages
Do not profile or upload any package information.
--novirtinfo
Do not profile or upload any virtualization information.
--norhnsd
Do not start rhnsd after completion.
--force
Register the system even if it has already been registered.
--version
Show the version of rhnreg_ks.
--proxy
Specify a HTTP proxy to use.
--proxyUser
Specify a username to use with an authenticated HTTP proxy.
--proxyPassword
Specify a password to use with an authenticated HTTP proxy.
--sslCACert
Specify a path to a SSL CA certificate to use.
--serverUrl
Specify a URL to as the server.
-h, --help
Show a help message and exit.
FILES
/etc/sysconfig/rhn/systemid
The digital server ID for this machine if the system has been registered onto "Spacewalk Server", "Red Hat Satellite" or "Red Hat
Network Classic". This file does not exist otherwise.
/etc/sysconfig/rhn/up2date
The common configuration file used by RHN client programs.
EXAMPLES
Register a new system to Spacewalk / Red Hat Satellite / Red Hat Network Classic:
rhnreg_ks --profilename "example_profile_name" --username "someexampleuser" --password "foobar"
SEE ALSO
rhn_check(8), rhn_register(8), rhnsd(8), rhn-profile-sync(8), rhnplugin(8), up2date(5).
AUTHORS
See the AUTHORS file included with this software.
This manual page was written by Adrian Likins <alikins@redhat.com> and James Bowes <jbowes@redhat.com>
BUGS
Report bugs to <http://bugzilla.redhat.com>.
COPYRIGHT
Copyright (C) 1999-2011 Red Hat, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
Linux 2011 February 4 RHNREG_KS(8)