No Fabric Login with virtualized WWN

Unanswered Question
Aug 22nd, 2011

Hi there,

I have virtualized my CNA WWNs to

WWNN=50:00:00:00:00:00:00:c1

WWPN=50:00:00:00:00:00:00:c0

and it looks like there is no Fabric Login possible anymore.

The Nexus 5020 keeps suspending the VFC because of too many invalid FLOGIs.

Does anyone have an idea why?

The response to the FLOGI I see with Wireshark is an LS_RJT (LinkService Reject) but

unfortunately it only contains an unknown reason code. So no help from this side.

Is there anything special about the used WWNs? Because if I use these WWNs on a FC HBA in conjunction wioth a Brocade Fabric

it works perfect. Any hint is highly welcome.

Thx!

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (1 ratings)
PrimergyQA Mon, 08/22/2011 - 23:48

I found the problem:

hpc-nexus5020(config)# show flogi internal errors

2) Event:E_DEBUG, length:145, at 605759 usecs after Mon Aug 22 13:31:59 2011

    [102] Err(NAA=5 and IEEE Company ID is zero)invalid nport name 50:00:00:00:0

0:00:03:10 from interface vfc1; node name is 50:00:00:00:00:00:03:11.

The WWN has to be compliant to the following rules:

http://howto.techworld.com/storage/156/how-to-interpret-worldwide-names/

Actions

Login or Register to take actions

This Discussion

Posted August 22, 2011 at 1:04 AM
Stats:
Replies:2 Avg. Rating:5
Views:855 Votes:0
Shares:0
Tags: nexus, wwn, flogi
+

Related Content

Discussions Leaderboard

Rank Username Points
1 297
2 134
3 133
4 132
5 80
Rank Username Points
10
5
4