Blade Chassis Discovery, or any NPV device

[DSS_ABROWN]

After upgrading to 6.4.0, all of the uplinks from my HP Blade Chassis now show as HUB_<wwn>, for example HUB_20:03:00:0D:EC:3C:2E:00.  Prior to 6.4, I was able to at least manually identify the uplinks to the physical chassis name, I could not find a way to over-ride this.  The chassis by the way show up under NPV Switches inventory.  Does anyone know how to identify these?  I have over 60 chassis, there's no way I'll remember 280 WWNs. 

This also broke our OCI API calls to get what blades are under what chassis, because the name lookup doesn't work anymore.

Any help is appreciated.

[jonas]

Hi Angelica.

If I'm not mistaken this is a new feature in v6.4 to show npv switches.

Is any of your npv switches showing up under npv?

Mvh

Jonas Enhörning

Duke Systems AB

21 okt 2013 kl. 21:20 skrev "Angelica Brown" <xdl-communities@communities.netapp.com<mailto:xdl-communities@communities.netapp.com>>:

<https://communities.netapp.com/index.jspa>

Blade Chassis Discovery, or any NPV device

created by Angelica Brown<https://communities.netapp.com/people/DSS_ABROWN> in OnCommand Insight - View the full discussion<https://communities.netapp.com/message/118960#118960>

After upgrading to 6.4.0, all of the uplinks from my HP Blade Chassis now show as HUB_<wwn>, for example HUB_20:03:00:0D:EC:3C:2E:00. Prior to 6.4, I was able to at least manually identify the uplinks to the physical chassis name, I could not find a way to over-ride this. The chassis by the way show up under NPV Switches inventory. Does anyone know how to identify these? I have over 60 chassis, there's no way I'll remember 280 WWNs.

This also broke our OCI API calls to get what blades are under what chassis, because the name lookup doesn't work anymore.

Any help is appreciated.

Reply to this message by replying to this email -or- go to the message on NetApp Community<https://communities.netapp.com/message/118960#118960>

Start a new discussion in OnCommand Insight by email<mailto:discussions-community-products_and_solutions-storage_management_software-oncommand--insight@communities.netapp.com> or at NetApp Community<https://communities.netapp.com/choose-container.jspa?contentType=1&containerType=14&container=3203>

[DSS_ABROWN]

Hi Jonas,

Yes, it is a new feature in 6.4, however it disappeared from FC Identify so I can call it something meaningful.  I don't know what HUB_20:03:00:0D:EC:3C:2E:00 is, I want to identify it as its real name like I use to: For example 20:03:00:0D:EC:3C:2E:00 used to show up in FC Identify and then I would call it HPCHassis1_VC1_Uplink1.  Now it's not even in there anymore, it's in it's own NPV section which I cannot identify.

[ostiguy]

There is no way to change what NPV mode devices are named as, unless you can discover the NPV mode device with a data source.

Unfortunately, we do not currently have a HP virtualconnect datasource - is that is what is at the edge of your network between hosts and the actual FC fabric?

[moechnig]

It will require some re-work, but you may be able to accomplish what you need to do through annotations.  Look at what you can annotate to an NPV switch device.  You can even add a custom annotation if none of the existing ones suit. 

[DSS_ABROWN]

Thanks for all the responses all.  Although they are helpful, they are not the answers I want to hear

We have external API calls to OCI to identify what blades and VMs are associated to chassis for Change Management purposes.  We do the lookups via get-host-names methods, now, there is no name anymore, this will now require us to create our own datasource per se to query HP to do the WWN translation.   It seems we have to maintain our own table of what hubs are in what chassis to make this happen.  We've been relying on OCI to do this translation for us, but not so much in this version. More work indeed.

[ostiguy · Accepted solution]

Hey Angelica,

Its unfortunate we cannot crack this nut out of the box with 6.4.x. As James said, using annotations to label the NPV devices may be a usable workaround.

That said, from a Request for Feature Enhancement standpoint, can you confirm what devices are at the edge in your environment? If you could PM me that and the account name I can submit a RFE for you

Matt

[DSS_ABROWN]

Will do!  Thanks very much.