Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

No FC4-TYPE feature 6140 and MDS9148

All,

We have B Series UCS, version 2.0(1s) with 6140s.  Two connections from 6140A to MDS1 and two connections from 6140B to MDS2.  The physical link is up, the VSAN ids match.

The MDS 9148 is running version 5.0(4).

I found the pwwn in the flogi database and added it to the zone on the MDS.

However we can not establish connectivity to the SAN.  We have noticed that in the fcns database the first server, and the one having troulbe on this new system does not have an FC4-TYPE: Feature.  It is blank and it is the only one.  NPIV is enabled on the MDS. 

XX-XXX-MDS1# show fcns database vsan 410

VSAN 410:

--------------------------------------------------------------------------

FCID        TYPE  PWWN                    (VENDOR)        FC4-TYPE:FEATURE

--------------------------------------------------------------------------

0x2d2800    N     20:81:54:7f:ee:45:9a:00 (Cisco)         npv

0x2d2801    N     20:00:00:25:b5:0e:01:df                                           <--- why blank?

0x2d2900    N     20:82:54:7f:ee:45:9a:00 (Cisco)         npv

show flogi internal event-history msgs

42) Event:E_FLOGI_FAIL, length:20, at 566066 usecs after Thu Feb  9 19:53:03 2012

    WWN: 20:00:00:25:b5:0e:01:df  VSAN: 410  ifindex: fc1/43  ev_id: 38

    rjt reason: 45 OPC: MTS_OPC_NULL(0)

------------------------

VSAN:410   FCID:0x2d2801

------------------------

port-wwn (vendor)           :20:00:00:25:b5:0e:01:df

node-wwn                    :20:00:00:25:b5:0d:00:ff

class                       :3

node-ip-addr                :0.0.0.0

ipa                         :ff ff ff ff ff ff ff ff

fc4-types:fc4_features      :   <---- something should be here, correct?

symbolic-port-name          :

symbolic-node-name          :

port-type                   :N

port-ip-addr                :0.0.0.0

fabric-port-wwn             :20:2b:00:05:9b:24:3d:b0

hard-addr                   :0x000000

permanent-port-wwn (vendor) :20:81:54:7f:ee:45:9a:00 (Cisco)

Connected Interface         :fc1/43

Switch Name (IP address)    :XX-XXX-MDS1 (10.4.x.x)

Comparison to working UCS server on this MDS, running 1.4

------------------------

VSAN:410   FCID:0x2d0d0f

------------------------

port-wwn (vendor)           :20:00:00:25:b5:0c:00:2f

node-wwn                    :20:00:00:25:b5:0b:00:2f

class                       :3

node-ip-addr                :0.0.0.0

ipa                         :ff ff ff ff ff ff ff ff

fc4-types:fc4_features      :scsi-fcp fc-gs  <---- why is the one above missing this feature?

symbolic-port-name          :

symbolic-node-name          :

port-type                   :N

port-ip-addr                :0.0.0.0

fabric-port-wwn             :20:19:00:05:9b:24:3d:b0

hard-addr                   :0x000000

permanent-port-wwn (vendor) :20:41:00:05:73:a9:31:c0 (Cisco)

Connected Interface         :fc1/25

Switch Name (IP address)    :XX-XXX-MDS1 (10.4.x.x)

Everyone's tags (6)
9 REPLIES
New Member

No FC4-TYPE feature 6140 and MDS9148

It appears NPV is not enabled on the MDS 9000.  Is that my issue?

show run

feature npiv

feature npv <-- not enabled

show npiv status - NPIV is enabled

do not have the option for the commands

show tech-support NPV

show npv traffic-map

show npv flogi-table

Cisco Employee

No FC4-TYPE feature 6140 and MDS9148

Dulmer,

     Have a look at the following link:

https://supportforums.cisco.com/docs/DOC-6186

Please let me know if this helps.

N-Port Virtualization (NPV) Mode

The  fabric interconnect operates in N-Port Virtualization (NPV) mode and  not as a FC switch in the fabric. This means that it does not require a  FC domain ID to keep the number of domain IDs in the SAN fabric the  same. The fabric interconnect joins the fabric through a normal FLOGI.  The FLOGIs that comes from the server blade adapters is translated by  the NPV process into FDISC into the fabric.

Make  sure that upstream MDS switches are NPIV enabled, and assign the  selected interface to the Cisco UCS with the appropriate VSAN number.

New Member

No FC4-TYPE feature 6140 and MDS9148

Anikas,

Thank you for the help, unfortunately this doesn't really get to the root issue or solve the problem.  We don't have an upstream MDS.  We just have multiple UCS (6120s and 6140s) connected to a pair of MDS 9148.  The other UCS are working and the MDS is set for NPIV mode.  This 6140 is new.  Not sure why the feature type is being set when the WWPN registers in the flogi database. 

Odd

Thank you

David

New Member

No FC4-TYPE feature 6140 and MDS9148

All,

I went through this document (Cisco MDS 9000 Family Troubleshooting Guide)and ran the below debug.  It all seems to go well until the MDS attempts a discovery on the UCS fabric port, last line in debug.  Are there any additional debugs to run on the MDS?  I did a show tech support on the UCS but that is a lot of info.  Is there anything more specific for this issue I can do on the UCS?

XX-XXX-MDS1# debug fcns events register vsan 410

XX-XXX-MDS1# 2012 Feb 13 14:27:47.365449 fcns: vsan 410: Deleted entry for port-id 0x2d2801

2012 Feb 13 14:27:47.367341 fcns: vsan 410: Deleting entry from pss

2012 Feb 13 14:27:47.367542 fcns: vsan 410: Sending sync message to the standby

2012 Feb 13 14:27:47.367613 fcns: vsan 410: Deleting entry from ext db pss

2012 Feb 13 14:27:47.367725 fcns: vsan 410: Sending ext sync message to the standby

2012 Feb 13 14:29:20.990623 fcns: vsan 410: reg timer started for port-id 0x2d2801

2012 Feb 13 14:29:20.994541 fcns: vsan 410: Created entry for port-id 0x2d2801

2012 Feb 13 14:29:20.994608 fcns: vsan 410: Got Entry for port-id 0x2d2801

2012 Feb 13 14:29:20.994668 fcns: vsan 410: Registered port-name 20:00:00:25:b5:0e:01:df for port-id 0x2d2801

2012 Feb 13 14:29:20.994723 fcns: vsan 410: Registered node-name 20:00:00:25:b5:0d:00:ff for port-id 0x2d2801

2012 Feb 13 14:29:20.994764 fcns: vsan 410: Registered cos 8 for port-id 0x2d2801

2012 Feb 13 14:29:20.994805 fcns: vsan 410: Registered port-type 1 for port-id 0x2d2801

2012 Feb 13 14:29:20.995067 fcns: vsan 410: Reading configuration for entry with port-name 20:00:00:25:b5:0e:01:df, node-name 20:00:00:25:b5:0d:00:ff

2012 Feb 13 14:29:20.995111 fcns: vsan 410: No configuration present for this portname

2012 Feb 13 14:29:20.995148 fcns: vsan 410: No configuration present for this nodename

2012 Feb 13 14:29:20.995193 fcns: vsan 410: Saving new entry into pss

2012 Feb 13 14:29:20.995316 fcns: vsan 410: Sending sync message to the standby

2012 Feb 13 14:29:20.995382 fcns: vsan 410: Saving new entry into ext db pss

2012 Feb 13 14:29:20.995483 fcns: vsan 410: Sending ext sync message to the standby

2012 Feb 13 14:29:21.029169 fcns: vsan 410: received registration command NS_CMD_RPN_ID

2012 Feb 13 14:29:21.039411 fcns: vsan 410: Registered port-name 20:00:00:25:b5:0e:01:df for port-id 0x2d2801

2012 Feb 13 14:29:21.039463 fcns: vsan 410: sending accept response to port-id 0x2d2801

2012 Feb 13 14:29:21.049134 fcns: vsan 410: received registration command NS_CMD_RNN_ID

2012 Feb 13 14:29:21.059924 fcns: vsan 410: Registered node-name 20:00:00:25:b5:0d:00:ff for port-id 0x2d2801

2012 Feb 13 14:29:21.059982 fcns: vsan 410: sending accept response to port-id 0x2d2801

2012 Feb 13 14:29:22.299089 fcns: vsan 410: reg timer expired for port-id 0x2d2801

2012 Feb 13 14:29:22.299175 fcns: vsan 410: initiating discovery on port-id 0x2d2801

Bronze

Hello

Hello

I know it is a long time ago, but has this ever been resolved ?

We are seeing the same (no FC4 registration) with Brocade (NPIV) and Nexus (NPV)

regards,

Geert

New Member

No FC4-TYPE feature 6140 and MDS9148

We rebuilt the entire UCS system after erasing the config on the 6140 and upgraded to the latest version, 2.0.1w, the issue/error remains.  Not sure what we will do at this point.

New Member

No FC4-TYPE feature 6140 and MDS9148

Resolved, after an hour the fcns started appearing correctly.  Not sure why.

New Member

No FC4-TYPE feature 6140 and MDS9148

Is it a SAN-BOOT? As my understanding is that if the UCS is a boot from SAN type of device then the FC4 features types will not be registered until the OS boots.

New Member

No FC4-TYPE feature 6140 and MDS9148

I'm seeing the same: Blank fc4-type info on our Nexus 5k's from A new UCS pod version 2.0(4b). Have a blade booting to local disk to see if it populates then but no joy.

Any idea what the issue may be?

2552
Views
0
Helpful
9
Replies
CreatePlease login to create content