Highlighted
cobussmit
1 Nickel

Brocade not seeing WWN's

Jump to solution

I have the following scenario: IBM virtual bladecenter with build in Cisco MDS switch as NPV. This Cisco NPV switch is connected with NP port to Cisco MDS Director where I can see NPIV HBA's of different blades. The problem comes in where the  Cisco NPV switch is also connected to a Brocade Director where NPIV is enabled, but the brocade can only see the port PWWN and not the underlying NPIV HBA's.

Please help if this make sense.

Labels (2)
0 Kudos
1 Solution

Accepted Solutions
cobussmit
1 Nickel

Re: Brocade not seeing WWN's

Jump to solution

I got it working by disabling the NP port on either the uplink to the cisco or disabling the uplink to the brocade. The problem is that only one core switch (Cisco or Brocade different fabrics) can see the NPIV HBA's at a time not simultaneously.

0 Kudos
3 Replies
dynamox
6 Gallium

Re: Brocade not seeing WWN's

Jump to solution

on MDS can you verify that a blade is actually trying to connect through the uplink port that goes to Brocade ad not to MDS director. Not sure if you can create manual port mapping where port on internal MDS are mapped to external uplinks going to Brocade.

0 Kudos
cobussmit
1 Nickel

Re: Brocade not seeing WWN's

Jump to solution

I got it working by disabling the NP port on either the uplink to the cisco or disabling the uplink to the brocade. The problem is that only one core switch (Cisco or Brocade different fabrics) can see the NPIV HBA's at a time not simultaneously.

0 Kudos
dynamox
6 Gallium

Re: Brocade not seeing WWN's

Jump to solution

it makes sense that an HBA can only login to one NPIV core switch but i would think you should be able to connect different blades to different core switches by forcing them to use specific uplink (use traffic map functionality). Have you tried that ..i am just curious if that would work.

0 Kudos