× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 3/23/2018 2:35 PM, Monty G. James wrote:
He is what it appears to me: On the Hosting LPAR you have a virtual
SERVER SCSI adapter and associated Network server that is sharing
your virtual optical device. On the Client LPAR you have a virtual
Client SCSI adapter assigned that ties back the virtual Server SCSI.

That makes a lot of sense.

I looked at the management partition and see that it has "Server SCSI" virtual adapters... one for each guest partition. The guest partition has a "Client SCSI" virtual adapter.

The guest partition's Client SCSI uses adapter id 7, it's server/client partition is Management, the partner adapter is 7, and it's not required.

The management partition's Server SCSI adapter is 7, server/client partition is SV2(7), partner adapter is 8, and it's not required.

Take a look at the config for each partition on the HMC and validate
that the virtual CLIENT SCSI adapter is tagged as your alternate
restart device.

I looked at the settings for the guest partition and in the "Tagged I/O" section, it's showing a load source of slot 7 / Virtual I/O, alternate restart Slot 7 / Virtual I/O, and console Slot 1 / Virtual I/O.

Can I assume this means that the client scsi that's in virtual slot 7 can be used as an alternate IPL device and the upgrade will use it if I select IPLSRC(D) when I do the PWRDWNSYS?

Thanks!

david


As an Amazon Associate we earn from qualifying purchases.

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-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.