× 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.



ah, Best Practices, that's a good thing to do.
The LUN booting idea has some drawbacks (especially when debugging an FC
problem...), so it's best to just have the split backplane and be done with
it.


On Fri, Nov 14, 2014 at 4:42 PM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

I do know that but that does not really offer the kind of redundancy we
suggest to our customers.

This box is a "do unto yourself before doing unto customer" box. I need to
get the configuration done properly so the other engineers at Agile can
practice doing all the normal maintenance and management needed in that
environment.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Roberto José Etcheverry Romero
Sent: Friday, November 14, 2014 1:26 PM
To: Midrange Systems Technical Discussion
Subject: Re: VIOS iSCSI vs. Fibre Channel with NPIV

Remember that if the POWER 7 box doesnt have the split backplane or you
don't have the extra SAS controller you can always boot from a lun on the
storage.

On Fri, Nov 14, 2014 at 4:13 PM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

I did 100% of the drive mapping on the HMC, removing the vSCSI drives
from the partition and mapping the Fibre devices to the correct ports.
You are correct it's really easy.

The command line in VIOS is an unmitigated disaster. You can't use
even the most rudimentary actions that any Unix has, IE: arrow up to
bring back the last command, backspace over a line to correct a typing
error etc. Sadly they could put a decent shell in there but alas, I
guess us non Unix types are too stupid to understand (I actually think
it's the other way around, the Unix guys seem to think that behavior
is OK)

I just completed a second partition conversion from internal DASD
vSCSI to NPIV and decided to not bring up the VIOS console and use
only the HMC to accomplish the job, and was successful, so it can be done
and it was easy.

Now off to setup the split backplane on the POWER 7 box to build the
dual VIOS.....

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Sue Baker
Sent: Friday, November 14, 2014 12:21 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: VIOS iSCSI vs. Fibre Channel with NPIV

"Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx> wrote on Fri, 14 Nov
2014
14:26:56 GMT:

I have to admit, VIOS is starting to win me over particularly with
the management mainly in the HMC code. The only command I had to
run on the VIOS side was CFGDEV then a command or two to verify the
Fibre logged in (it did).


Sorry that I misunderstood about where you were coming from storage-wise.

You know you can see all the mappings via the HMC and change them too
for NPIV?

While I like ... well like isn't really the appropriate term ...
using the command line because it feels faster, I'm forcing myself to
attempt to be VIOS command line free.

cfgdev normally runs without intervention due to a DLPAR operation.
If not, there's the operations -> run vios command to take care of it.

select no LPARs (V7R7xx HMCs) and navigate Configuration -> Virtual
Resources -> Virtual storage management -> Virtual Fibre Channel tab.

The new V8R810 code does it different, but gives lots more information
about the VFCs.

Next release of HMC code is even better.

--
Sue
IBM Americas Advanced Technical Sales Support (ATS) Power Systems
Rochester, MN
--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.