|
Roberto,
WWPNs appeared just a couple of seconds when starting IBM i LPAR and I
could map them to host configuration.
And you are right... doesn't make sense
Regards
Diego E. KESSELMAN
El 29/07/19 a las 20:45, Roberto José Etcheverry Romero escribió:
Just to clarify, when "enabled" the storwize forces everything (host andso
node traffic) thru the NPIV wwpns, and they don't work without a switch
in a direct attach situation you end up like this. What's weird to me isIf
that you said you were able to see the host's WWPN and map the volumes.
NPIV is active, and therefore the link can't be established due to a lackdiegokesselman@xxxxxxxxx>
of switching, how did you map them?
On Mon, Jul 29, 2019 at 3:48 PM Diego Kesselman <
wrote:fctargetportmode
yes
Thank you both! That was the issue!
I changed the value to "transitional" and worked on first attempt
Regards
Diego E. KESSELMAN
El 29/07/19 a las 12:18, Steve Pavlichek escribió:
Kristopher does bring up a good point. Double check that the FC portsbeing used on the v5000 show as “Host IO Permitted”. The
controller.may be set wrong on the v5000. It must be Disabled or Transitional.
v5000 CLI command
Lsiogrp 0
Look for fctargetportmode
From: Diego Kesselman<mailto:diegokesselman@xxxxxxxxx>
Sent: Monday, July 29, 2019 12:39 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: [Power9 with Direct Attached V50x0
We don't have virtual wwpns. I remember you need a SAN Switch for that.
El 29/07/19 a las 11:33, Kristopher Whitney escribió:
You need to disable the virtual wwpns (NPIV) on the V5K
the
-
message: 1
date: Mon, 29 Jul 2019 15:19:32 +0000
from: Tsvetan Marinov <tsetso.marinov@xxxxxxxxx>
subject: Re: Power9 with Direct Attached V50x0
If this is a new V5K, what version of the firmware it is at
listmoment
--and what firmware version it wa shipped with l?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
--To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
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.