MDS Phantom Device Alias and PWWN results

[emperor1431]

I am getting some odd results when zoning currently and was looking for feedback!

So just an example.  Here is a new zone I wanna put in.

zone name ESXUCSD10-VPLEX-E1-B0-FE03 vsan 102

member device-alias ESXUCSD10

member device-alias VPLEX-E1-B0-FE03

But when I look at that same zone that was just created...

sh zone name ESXUCSD10-VPLEX-E1-B0-FE03 vsan 102

zone name ESXUCSD10-VPLEX-E1-B0-FE03 vsan 102

  pwwn 20:00:00:25:b5:2d:b0:09 [ESXUCSD9] < -WTF?

  pwwn 50:00:14:42:b0:60:2a:03 [VPLEX-E1-B0-FE03]

Where did the D9 blade come from?

Different WWN names in the aliases!

 sh device-alias database | inc ESXUCSD10

device-alias name ESXUCSD10 pwwn 20:00:00:25:b5:2d:b0:0a

 sh device-alias database | inc ESXUCSD9

device-alias name ESXUCSD9 pwwn 20:00:00:25:b5:2d:b0:09

Device alias database has the correct PWWN for D9 and D10 blades but it is pulling this from somewhere. I have searched the configs on both switches in the fabric - everything matches up as it should except this example.

Thoughts?

Thank you!

[dakester]

Hi,

Try these commands:

show device-alias database | i 20:00:00:25:b5:2d:b0:09|ESXUCSD9|ESXUCSD10|20:00:00:25:b5:2d:b0:0a|Total

show zone internal ddas-table | i 20:00:00:25:b5:2d:b0:09|ESXUCSD9|ESXUCSD10|20:00:00:25:b5:2d:b0:0a|Total

Might be this bug.

CSCua02159 Dev's zoned by device-alias don't work after port flap or zone activate

There is a new command in the Resolution Summary you can try.  It does not provide output, so re-issue the above commands if needed.

zone internal ddas-table cleanup duplicate-entries

[emperor1431]

We are at version 6.2(11b) I think we are past that bug?

Thanks!