09-03-2019
Native AIX TL Upgrade on a VIO Server
What happens if we perform a Native AIX TL Upgrade on a VIO server? I mean instead of updateios I logged into oem_setup_env and ran a update_all to a new TL.
10 More Discussions You Might Find Interesting
1. AIX
Hello
I need to be able to take control of the native X server ( :0.0 ) on AIX5.3 workstations via VNC to be able to assist users...seeing what they are doing is much better than them telling me what they are doing.
I know that this can be done on linux so it should doable on AIX.
On linux... (0 Replies)
Discussion started by: art
0 Replies
2. AIX
Hi all,
Sorry if this is in the wrong place but needed to make sure lots of people saw this so that hopefully someone will be able to help.
Basically i've upgraded a test server from 4.3 to 5.3 TL04.
The server has hdisk0 and 1 as rootvg locally but then has another vg setup on our ESS... (5 Replies)
Discussion started by: djdavies
5 Replies
3. AIX
Hi folks,
does anybody have a link to a documentation how to implement native MPIO on AIX? We are using EMC PowerPath and Datacore SanSymphony/Cambex for this so far and I wasn't able to find a good description on that topic. All I know so far is that mkpath, chpath and lspath are used to... (3 Replies)
Discussion started by: zaxxon
3 Replies
4. AIX
is it possible to find out memory frequency(speed) in vio server in aix?
Regards
Manoj (0 Replies)
Discussion started by: manoj.solaris
0 Replies
5. AIX
Hi,
I want to know wheather partition size for installation of vio client can be specified on vio server
example
If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Discussion started by: manoj.solaris
1 Replies
6. AIX
Hi,
I was trying to uninstall the native MPIO driver on the AIX 6.1 machine we have in our lab and ran into a whole bunch dependent filesets initially. I deleted the disks, fcsX, fscsiX, fcnetX and tried again, but ran into the same error.
Subsequently, I figured out that the OS disks in... (4 Replies)
Discussion started by: ronykris
4 Replies
7. AIX
We have AIX 6.1 system attached to SAN disks (DS4700 and DS8100) thru SVC.
Initially when the system was I forgot to install sddpcm drivers. and wanted to know how can i go with the installation of the sddpcm drivers.
My understandin going thru the manual ... (3 Replies)
Discussion started by: mk8570
3 Replies
8. AIX
Hi
What are the steps to be followed when upgrading MQ version from 6 to 7 in aix server?
cbsdbprd01 # oslevel -s
5300-10-01-0921
cbsdbprd01 # lslpp -l | grep -i mq
mqm.base.runtime 6.0.2.1 COMMITTED WebSphere MQ Runtime for
mqm.base.samples 6.0.2.1 ... (0 Replies)
Discussion started by: samsungsamsung
0 Replies
9. AIX
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies
10. AIX
The company I work for has various AIX servers that I've recently migrated to AIX 7.1 (from 6.1). Some are powerHA clusters some are not. Likewise, the systems engineer that I replaced had net-snmp installed on said clustered systems. Long story short I am re-invoking AIX's native SNMP (v3) for... (1 Reply)
Discussion started by: davix
1 Replies
LEARN ABOUT SUNOS
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)