Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

4839

October 18th, 2010 06:00

Zone virtual fibre channel using NPIV from an AIX VIO server on Cisco MDS switches?

There are a couple other posts regarding this.  I haven't been able to find the details on setting up MDS switches for NPIV zoning.

I tried this already, and we have 2 AIX VIO server physical hba logged into the switches.  The tech created the Virtual LPAR and created the vWWN's.  I don't see the these vWWN's on my switches under FLOGI information or FCNS database.    I do see the physical adapters logged into the port.

Just wondering what I'm missing, and how I can correlate one handshake to the next with NPIV.  Could someone go through the settings for NPIV from AIX VIO on an MDS 9505?   Where they verify that logins are happening/etc. ?  

On the MDS we're at

  BIOS:      version 1.0.5

  system:    version 3.1(2)

Thanks,

Ron

1 Rookie

 • 

20.4K Posts

October 18th, 2010 07:00

i think the switch side is fine ...something needs to be tweaked in AIX

1 Rookie

 • 

20.4K Posts

October 18th, 2010 06:00

npv logins should be listed with "show flogi database" ..is NPIV enabled on the switch itself "show npiv status"

4 Posts

October 18th, 2010 07:00

Thanks for the response Dynamox

I don't have that command on my MDS (tried it in config too).   Maybe because I'm still at 3.1?

CISCO9509BOT# show npiv status
                   ^
% invalid command detected at '^' marker.

But, I know that NPIV has been enabled (config t; npiv enable).

From show flogi database,  7/12 is the port that should show the virtual logins, but, I only see this;

...

fc7/11     50    0x84000f  10:00:00:00:c9:7a:b7:cf  20:00:00:00:c9:7a:b7:cf
fc7/12     100   0x420048  10:00:00:00:c9:c0:b6:be  20:00:00:00:c9:c0:b6:be
fc7/13     50    0x840002  21:01:00:1b:32:3b:74:36  20:01:00:1b:32:3b:74:36
...

Any specific port settings?     It doesn't mention requiring one, but, does the MDS need a reboot after setting NPIV?

4 Posts

October 18th, 2010 07:00

Ok,  Thanks.    That's what I thought that it should look like under show flogi.    So, we are missing that initial connect.

I do see the physical wwn.   Is it possible the VIO server isn't "broadcasting" somehow?

CISCO9509BOT# show system internal feature-mgr feature state
Feature               State     Reason
--------------------  --------  --------------------
ivr                   enabled   success
fcip                  disabled  feature never enabled
fcsp                  disabled  feature never enabled
ficon                 disabled  feature never enabled
iscsi                 disabled  feature never enabled
tacacs                disabled  feature never enabled
qos-manager           disabled  feature never enabled
port-security         disabled  feature never enabled
fabric-binding        disabled  feature never enabled
ike                   disabled  feature never enabled
isns-server           disabled  feature never enabled
ipsec                 disabled  feature never enabled
port_track            disabled  feature never enabled
scheduler             disabled  feature never enabled
npiv                  enabled   success
san_ext_tuner         disabled  feature never enabled
dpvm                  disabled  feature never enabled
extended_credit       disabled  feature never enabled
cloud-discovery       disabled  feature never enabled
sdv                   disabled  feature never enabled

1 Rookie

 • 

20.4K Posts

October 18th, 2010 07:00

nah, not reboot is required. Can you run "show feature"  ..is NPIV listed ?

While i am not doing NPIV with AIX ..we are using NPV with blades switches. So i suspect when you have it working it should look something like this where multiple WWNs are logged-in through the same physical interface.

9134switchA# show flogi data
--------------------------------------------------------------------------------
INTERFACE        VSAN    FCID           PORT NAME               NODE NAME
--------------------------------------------------------------------------------
fc1/9            14    0x9a0300  50:00:09:72:08:22:29:1c 50:00:09:72:08:22:28:00
fc1/10           14    0x9a0400  50:00:09:72:08:22:29:18 50:00:09:72:08:22:28:00
fc1/11           14    0x9a0000  20:0a:00:0d:ec:ee:b4:c0 20:0e:00:0d:ec:ee:b4:c1
fc1/11           14    0x9a0001  50:01:43:80:06:2f:73:68 50:01:43:80:06:2f:73:69
fc1/11           14    0x9a0002  50:01:43:80:06:2f:61:fc 50:01:43:80:06:2f:61:fd
fc1/11           14    0x9a0004  50:01:43:80:06:2f:62:08 50:01:43:80:06:2f:62:09
fc1/11           14    0x9a0008  50:01:43:80:06:2f:44:cc 50:01:43:80:06:2f:44:cd
fc1/11           14    0x9a000f  50:01:43:80:06:2f:62:28 50:01:43:80:06:2f:62:29
fc1/11           14    0x9a0010  50:01:43:80:06:2f:61:f0 50:01:43:80:06:2f:61:f1
fc1/11           14    0x9a0017  50:01:43:80:06:2f:62:6c 50:01:43:80:06:2f:62:6d
fc1/12           14    0x9a0200  20:0a:00:0d:ec:f0:8b:40 20:0e:00:0d:ec:f0:8b:41
fc1/12           14    0x9a0201  50:01:43:80:04:26:ae:70 50:01:43:80:04:26:ae:71
fc1/12           14    0x9a0202  50:01:43:80:04:26:ad:48 50:01:43:80:04:26:ad:49
fc1/12           14    0x9a0204  50:01:43:80:06:2f:62:78 50:01:43:80:06:2f:62:79

4 Posts

October 18th, 2010 12:00

That was correct.   This is our initial run, and we had the LPAR in a inbetween state.    It logged in with the physical wwn's, and then the virtuals were created, but, the host never rebooted/reset again.

After we reset it,  it logged into the switch with all the wwn's.

1 Rookie

 • 

20.4K Posts

October 18th, 2010 12:00

good deal Ron.  Interesting to test if you reboot just the LPAR itself ..i would hope that i would log back in and not require another physical server reboot/reset.

No Events found!

Top