3.1.3 WWNs format incorrect?

hdtvguy · **Joined:** Sun Jul 29, 2012 9:30 am **Posts:** 576

Anyone notice sine deploying 3.1.3 the WWNS are incorrect

Name VV_WWN VSize_MB Comment
p_db_vg_axxxx.0 60002AC00000000000001EB40000ADEB 51200 rootvg
p_db_vg_axxxx.1 60002AC00000000000001EB50000ADEB 71680 vgapp01

I see this on most of my 3.1.3 arrays, but not one that is replicating with a 3.1.2 array.

I opened a support case as it makes no sense. Show this in CLI and IMC.

Richard Siemers · **Posted:** Fri May 09, 2014 3:15 pm

3.1.2 MU1 output of showvv -d

Code:

SS7200-1 cli% showvv -d
Id Name          Rd Mstr  Prnt Roch Rwch PPrnt PBlkRemain -------------VV_WWN------------- -----CreationTime------
 1 .srdata       RW 0/1/-  ---  ---  ---   ---         -- 60002AC0000000000000000100005F94 2013-05-23 14:00:34 CDT
 0 admin         RW 1/0/-  ---  ---  ---   ---         -- 60002AC0000000000000000000005F94 2013-05-23 13:58:26 CDT
 2 LXSELINEPPD_0 RW 1/0/-  ---  ---  ---   ---         -- 60002AC0000000000000000200005F94 2013-08-14 15:46:13 CDT
 3 LXSELINEPPD_1 RW 0/1/-  ---  ---  ---   ---         -- 60002AC0000000000000000300005F94 2013-08-14 15:46:52 CDT
------------------------------------------------------------------------------------------------------------------
 4 total                                                0

Can you be more specific about whats wrong with them?

apol · **Joined:** Wed May 07, 2014 1:51 am **Posts:** 267

Our VVs still have the normal WWNs. Newly created (with 3.1.3) VVs as well.

But our WWNs are not as long as yours are - ours are 8bytes long, yours 16. Could this be linked to your usage of Snapshots for backup, where you exceeded this max 32768-vvs-limit?

Your WWNs look like they are "filled up with zeros" in the middle, maybe to extend the range of available WWNs for new vvs?? Maybe 3.1.3 converts the old 8byte-WWNs to new 16byte-WWNs if you start using vv-ids > 32768 to allow the usage of the newly supported vv-ids/vv-amounts bigger than that?!

Edit: corrected byte-numbers

hdtvguy · **Joined:** Sun Jul 29, 2012 9:30 am **Posts:** 576

3par got back and said in 3.1.2 there is new extended length WWNs, but my legacy arrays that started as 3.1.1 evidently do not have them even though they are now 3.1.3 and have been 3.1.2 for a year. I wonder if once an array starts with the old length that it keeps that giong froward.

mugurs · **Joined:** Thu Aug 22, 2013 7:17 am **Posts:** 21

3.1.2 MU2 output for showvv -d:
Id Name Rd Mstr Prnt Roch Rwch PPrnt PBlkRemain -----VV_WWN----- ------CreationTime------
1 .srdata RW 0/4/5 --- --- --- --- -- 50002AC000012692 2013-04-04 16:46:28 EEST
0 admin RW 0/4/5 --- --- --- --- -- 50002AC000002692 2013-04-04 14:15:00 EEST

3.1.2 MU3 output for showvv -d:
Id Name Rd Mstr Prnt Roch Rwch PPrnt PBlkRemain -----VV_WWN----- ------CreationTime------
2151 .srdata RW 1/2/3 --- --- --- --- -- 50002AC008672299 2013-07-21 07:12:26 EEST
0 admin RW 0/1/4 --- --- --- --- -- 50002AC000002299 2012-07-13 11:33:58 EEST

so ...

hdtvguy · **Joined:** Sun Jul 29, 2012 9:30 am **Posts:** 576

But what was your array when you got it, I suspect if volumes were created before 3.1.2 introduced the new WWN format that the array will continue to use the old format.

HPE Storage Users Group

3.1.3 WWNs format incorrect?

Who is online