cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
802
Views
0
Helpful
6
Replies

DCNM lists devices under wrong tab

DrPepper1234
Level 1
Level 1

Hello all,

I'm using Cisco DCNM 7.2(1) to manage SAN fabrics.

We have just plugged new appliances (they are named RPA, vendor is EMC), to the SAN, on both Fabrics.

Each appliance has 2 ports n Fabric 1 and 2 ports on Fabric 2.

There's something strange with DCNM...

Under Fabric 1 all the RPA ports are listed under "host ports" tab.

Under Fabric 2 some ports are listed under "host ports" tab, while others are listed under "storage ports" tab.

Any suggestion?

1 Accepted Solution

Accepted Solutions

jihicks
Cisco Employee
Cisco Employee

Two things come to mind:

(1)OUI - See this link:

Troubleshooting Issues with DCNM SAN

Cisco DCNM cannot recognize the new Cisco switch or end device based on the unknown OUIs from WWN. To add new OUIs for Cisco switches or add a new device type, edit $Installation\dcm\fm\conf\server.properties:

# Add new OUIs for discovering switch, end device with format: 
# 0xhhhhhh vendor_name devicetypes h(host)|d(disk)|t(tape)|s(switch)|g(gateway)|m(cisco mds)
# for example: newOUIs=0x00E069 JNI h|d; 0x000ded Cisco m;\
# 0x006069 Brocade s;
newOUIs = 0x000ded Cisco m -- is to add switch new OUI
newOUIs = 0x00E069 JNI h|d  -- is to add host or disk device new OUI

After you finish the edits, restart the Cisco DCNM-SAN server.

(2)Check the FCNS ( Fibre Channel Name Server ) on the switch to see what FC4 features the new RPA is registering with the name server.  The command is:

 show fcns database

Best regards,

Jim

View solution in original post

6 Replies 6

jihicks
Cisco Employee
Cisco Employee

Two things come to mind:

(1)OUI - See this link:

Troubleshooting Issues with DCNM SAN

Cisco DCNM cannot recognize the new Cisco switch or end device based on the unknown OUIs from WWN. To add new OUIs for Cisco switches or add a new device type, edit $Installation\dcm\fm\conf\server.properties:

# Add new OUIs for discovering switch, end device with format: 
# 0xhhhhhh vendor_name devicetypes h(host)|d(disk)|t(tape)|s(switch)|g(gateway)|m(cisco mds)
# for example: newOUIs=0x00E069 JNI h|d; 0x000ded Cisco m;\
# 0x006069 Brocade s;
newOUIs = 0x000ded Cisco m -- is to add switch new OUI
newOUIs = 0x00E069 JNI h|d  -- is to add host or disk device new OUI

After you finish the edits, restart the Cisco DCNM-SAN server.

(2)Check the FCNS ( Fibre Channel Name Server ) on the switch to see what FC4 features the new RPA is registering with the name server.  The command is:

 show fcns database

Best regards,

Jim

Great answer :-)

This is very useful, thanks.

Still there's something strange... and I'm not sure that it depends on RPAs.

The ones listed under "host ports" are using scsi-fcp FC4 feature.

The ones listed under "storage ports" are using scsi-fcp:both FC4 feature.

As we're talking of exactly identical devices, I don't understand is why some ports have scsi-fcp and others scsi-fcp:both

EDIT:
I tried to add EMC's OUI to the list, but nothing has changed in DCNM :-(

Here's what I added: newOUIs=0x001248 Kashya d

That value is the one I took from "vendor" column in DCNM. I altro tried to test that OUI with Wireshard OUI lookup tool, and it confirms it's by EMC/Kashya.

The device registers the FC4 featrures, so that would be a question for EMC I guess.

Best regards,

Jim

I'll try to raise the issue with them... anyway this is not a big issue I guess.

BTW: I still can't manage to move those targets in the correct tab :-(

Modification to OUI list doesn't have effect on that.

Did you restart DCNM after making the change?

You may not be able to move them with the oui, because of the FC4 feature types.

Yes, I have restarted DCNM server a couple of times, and after that I have also restarted the whole VM.

No luck...