HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

How to avoid duplicated MAC and WWN range of Virtual Connect

 
chuckk281
Trusted Contributor

How to avoid duplicated MAC and WWN range of Virtual Connect

Nelson had a question :

 

*********

 

Other than using VCEM, what is the usual practice for enterprise customer to avoid duplicated MAC and WWN range selection in VC setup?  Can you share how your customer manage these virtualized addressing?

 

*****************

 

Reply from David:

 

***********

 

Without VCEM, it’s a manual process.  Whether than means paper, a spreadsheet or a database, it’s still manual.  I’d say most I’ve run into use a spreadsheet to track.

 

***************

 

Input from Chris:

 

**************

 

Further to David’s comment, it is important that the domain of allocation control is correctly established. 

 

The natural domain of allocation control for MAC addresses will be the data center or if they use Layer 2 stretched bridged networks then it is the set of data centers that the stretched bridged network spans.

 

For WWNs it is similar.  The SAN fabrics spanning multiple data centers for replication should be considered one domain of control.

 

Very often it is just 2 data centers.   I have a customer with two data centers who adopted a useful convention of allocating even range numbers for one DC and odd ones for the other DC.  In my view it is also useful to allocate the same range number for MAC and WWNs ranges for the same enclosure. 

 

The records of ranges are still kept manually of course – typically as a spreadsheet.

 

***************

 

Questions or comments?