8 More Discussions You Might Find Interesting
1. AIX
Hello,
I did offline HACMP(PowerHA) upgrade 5.4.1 to 5.5 - basically stopped HACMP services and upgraded cluster.* filesets.
Tried to start services again - topsvcs refused to start on second node complaining that node instance numbers are different - and indeed they are different.
This is... (2 Replies)
Discussion started by: vilius
2 Replies
2. AIX
hi,
when I do a failover, hacmp always starts db2 but recently it fails to start db2..noticed the issue is db2nodes.cfg is not modified by hacmp and is still showing primary node..manually changed the node name to secondary after which db2 started immediately..unable to figure out why hacmp is... (4 Replies)
Discussion started by: gkr747
4 Replies
3. AIX
Hi
What is the procedure to upgrade the MQ from 6 to 7 in aix hacmp cluster. Do i need to bring down the cluster
services running in both the nodes and then give #smitty installp in both the nodes separately. Please assist... (0 Replies)
Discussion started by: samsungsamsung
0 Replies
4. AIX
Hi,
I need to upgrade one of my clusters from HACMP 5.41 to HACMP 6.1.
Is there an easy + clean way to do it ? Any hurdles I have to anticipate? What should I read - anything I found so far seems to talk only about HACMP 5.x - and looks pretty straight forward.
Thanks and regards
zxmaus (1 Reply)
Discussion started by: zxmaus
1 Replies
5. AIX
hi
can anyone explain the concepts of HACMP and configuration (step by step) (2 Replies)
Discussion started by: udtyuvaraj
2 Replies
6. AIX
Hi,
Can we use network for heartbeat, I mean can we use different network card for heartbeat. (6 Replies)
Discussion started by: vjm
6 Replies
7. AIX
Hi All,
My company is going to upgrade the db2 on the one node hacmp, I think there's one backup.
After the upgrade of the db2. Do I need to restart cluster and server? I mean, do a graceful shutdown of the cluster, reboot the server and do a cluster start. Is that it? Do I need to reboot... (1 Reply)
Discussion started by: itik
1 Replies
8. AIX
(0 Replies)
Discussion started by: mhenryj
0 Replies
LEARN ABOUT OPENSOLARIS
lustatus
lustatus(1M) System Administration Commands lustatus(1M)
NAME
lustatus - display status of boot environments
SYNOPSIS
/usr/sbin/lustatus [-l error_log] [-o outfile] [BE_name] [-X]
DESCRIPTION
The lustatus command is part of a suite of commands that make up the Live Upgrade feature of the Solaris operating environment. See
live_upgrade(5) for a description of the Live Upgrade feature.
The lustatus command displays the status information of the boot environment (BE) BE_name. If no BE is specified, the status information
for all BEs on the system is displayed.
The headings in the lustatus information display are described as follows:
Boot Environment Name
Name of the BE.
Is Complete
Indicates whether a BE is able to be booted. Any current activity or failure in an lucreate(1M) or luupgrade(1M) operation causes a BE
to be incomplete. For example, if there is a copy operation proceeding on or scheduled for a BE, that BE is considered incomplete.
Active Now
Indicates whether the BE is currently active. The "active" BE is the one currently booted.
Active On Reboot
Indicates whether the BE becomes active upon next reboot of the system.
Can Delete
Indicates that no copy, compare, or upgrade operations are being performed on a BE. Also, none of that BE's file systems are currently
mounted. With all of these conditions in place, the BE can be deleted.
Copy Status
Indicates whether the creation or repopulation of a BE is scheduled or active (that is, in progress). A status of ACTIVE, COMPARING
(from lucompare(1M)), UPGRADING, or SCHEDULED prevents you performing Live Upgrade copy, rename, or upgrade operations.
The following is an example lustatus display:
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
-------------------- -------- ------ --------- ------ ----------
disk_a_S7 yes yes yes no -
disk_b_S7db yes no no no UPGRADING
disk_b_S8 no no no no -
S9testbed yes no no yes -
Note that you could not perform copy, rename, or upgrade operations on disk_b_S8, because it is not complete, nor on disk_b_S7db, because a
Live Upgrade operation is pending.
The lustatus command requires root privileges.
OPTIONS
The lustatus command has the following options:
-l error_log
Error and status messages are sent to error_log, in addition to where they are sent in your current environment.
-o outfile
All command output is sent to outfile, in addition to where it is sent in your current environment.
-X
Enable XML output. Characteristics of XML are defined in DTD, in /usr/share/lib/xml/dtd/lu_cli.dtd.<num>, where <num> is the version
number of the DTD file.
OPERANDS
BE_name
Name of the BE for which to obtain status. If BE_name is omitted, lustatus displays status for all BEs in the system.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
>0 An error occurred.
FILES
/etc/lutab
list of BEs on the system
/usr/share/lib/xml/dtd/lu_cli.dtd.<num>
Live Upgrade DTD (see -X option)
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWluu |
+-----------------------------+-----------------------------+
SEE ALSO
lu(1M), luactivate(1M), lucancel(1M), lucompare(1M), lucreate(1M), lucurr(1M), ludesc(1M), ludelete(1M), lufslist(1M), lumake(1M),
lumount(1M), lurename(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5)
SunOS 5.10 23 Apr 2003 lustatus(1M)