But i bet the internal AIX version of those VIOS is 6.1, that must be what
the 6.1.0.0 is... I have all my lab shutdown for the weekend so i can't
check but i would bet it's that...

On Mon, Dec 8, 2014 at 3:15 PM, <rob@xxxxxxxxx> wrote:

Ok, I went into the HMC and updates, "Change Licensed Internal Code for
the current release". And started stepping through the options for
concurrent update from IBM site. Got to
I/O LIC (Linux and AIX partitions only)
Current I/O selection impact: Take specified I/O offline.

Ok, this looks like the way to apply these I/O updates but concurrent it's
not (unless you consider dropping all ethernet for all lpars something you
can do concurrently). I can deal with that. It will just take some extra
documentation.
Well, maybe it can be done concurrently if you only drop one vios lpar (or
update one card) at a time.

Sure would be nice if this interface upgraded VIOS also.

Having a tough time wrapping my head around
Partition 001 vios31
where "Current level" and "Available level" are both 6.1.0.0
when ioslevel is showing 2.2.3.3
What is "6.1.0.0" indicating?

Even though the 'partition' rows in "Licensed internal code survey
results" shows a radio button by "Partition 001 vios31 " the small print
at the bottom says
"Click in the Select column of a table row and then click on View
Information to see detailed information about the device. Partition rows
cannot be selected."

FYI, none of my lpars anywhere are running 6.1 of IBM i.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 12/08/2014 10:33 AM
Subject: RE: Cross product dependencies
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I would, but.....

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Monday, December 08, 2014 9:25 AM
To: Midrange Systems Technical Discussion
Subject: RE: Cross product dependencies

So I should download this fix and apply it then?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 12/08/2014 10:17 AM
Subject: RE: Cross product dependencies
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



It applies to any Unix OS(AIS, VIOS, Linux). IBM I has its dependencies
too, but they are a bit more tolerant.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Monday, December 08, 2014 8:39 AM
To: Midrange Systems Technical Discussion
Subject: Re: Cross product dependencies

When you go to upgrade firmware and it has this cross dependency
recommendation, should I be concerned about it if I am running AIX and IBM

i
or is that something that only applies to Linux where one is accustomed to
having to patch the OS together with various device drivers?


I/O:
- Device: PCIe2 4-Port (10GbE SFP+ & 1GbE RJ45) Adapter Feature Codes:
EN0S EN0T EN0U EN0V Version: 30090140 (or higher) An enhancement added to
support Network Installation on 1GB speed switch ports.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].