Help troubleshooting device-alias database

[DrPepper1234]

Good morning,

today I see that DCNM-SAN gave an error while distributing the device-alias database through the fabric.

Result: Failure
Reason: Another device-alias already present with the same pwwn.

I'm looking at the troubleshooting guide - http://www.cisco.com/en/US/products/ps5989/prod_troubleshooting_guide_chapter09186a00808348bc.html 

The suggestion is to use the show device-alias database command from the appropriate switch, and then find the conflict there.

Unfortunately my fabric contains hundreds of device-aliases, and it's not easy to find which is the one causing problems.

How do I find the right one?

TIA

[Walter Dey]

Did you check the MDS error log file ?

[DrPepper1234]

The command show logging logfile doesn't show anything useful.

[jj27]

Not sure if this will be helpful or not, but I seem to remember having a similar issue where an enhanced zoning session had started to create the device alias but never committed, then from the GUI the user tried to do the same and got a duplicate device-alias error. The solution was to login to the switch directly and clear the locked database session.

[DrPepper1234]

It was not an issue due to DB lock.

At the end I found the solution: I used Notepad++ to compare the device-alias databases and found the duplicates.

[Marcelo Morais]

Hi DrPepper1234,

 I dind't find any command that could show all the WWPNs and facilitate the process of identify the duplication.

 Although you use Notepad++, it will be great if there is a command for that.

[DrPepper1234]

I didn't find any command neither.

And I cannot believe that such a command does not exist, that's why I came here and ask... I think it's a huge lack.

Such a command is really needed... reading through hundreds of device aliases without any troubleshooting aid it's really a pain.

[Marcelo Morais]

I agree ... I let you know if anything comes up ... meanwhile this "command" is on my "Wish List".

[dakester]

Hi,

Perhaps the enhancement is available in a newer NX-OS release.

My lab switch is running NX-OS 6.2(9)

MDS# show log log | i DEVICE

2015 Feb  2 18:45:43 MDS %DEVICE-ALIAS-3-MERGE_MRESP_REJECTED: conflict between local device-alias agilent1032_renamed pwwn 10:00:00:
00:00:02:00:00 rcvd device-alias  ag103_2 pwwn 10:00:00:00:00:02:00:00

[DrPepper1234]

I'm using MDS switches with 5.2(8b).

The output of the command is the following:

 show log log | i DEVICE
2014 Dec 29 11:36:08 SFSDA1 %DEVICE-ALIAS-3-MERGE_FAILED: Another device-alias already present with the same pwwn
2015 Jan 29 12:19:47 SFSDA1 %DEVICE-ALIAS-3-MERGE_FAILED: Another device-alias already present with the same pwwn
2015 Jan 29 12:33:13 SFSDA1 %DEVICE-ALIAS-3-MERGE_FAILED: Another device-alias already present with the same pwwn

Completely useless :(

[dakester]

What does the other switch say?

[DrPepper1234]

Which other switch? The error message doesn't give the info.

I do have 12 switches in the fabric.

[dakester]

Hi,

I see now.

I was doing a device-alias merge, but you have "DCNM-SAN gave an error while distributing the device-alias database through the fabric."

This may take some time, so if you are still interested in determining why DCNM-SAN did not provide a more specific message, like which device alias name and pwwn was the same, click on the open a TAC case link/button, and provide DCNM-SAN version, exact steps to recreate, and a show tech from the switch.

Regards,

David

[DrPepper1234]

The solution for me was to  use Notepad++ to compare the device-alias databases and found the duplicates.

Opening an SR and waiting for the solution takes too long.

[dakester]

Hi,

Perhaps the enhancement is available in a newer NX-OS release.

My lab switch is running NX-OS 6.2(9)

MDS# show log log | i DEVICE

2015 Feb  2 18:45:43 MDS %DEVICE-ALIAS-3-MERGE_MRESP_REJECTED: conflict between local device-alias agilent1032_renamed pwwn 10:00:00:
00:00:02:00:00 rcvd device-alias  ag103_2 pwwn 10:00:00:00:00:02:00:00