This section explains the concept for separating tenants of address pools.
MAC Addresses and WWNs
MAC addresses and WWNs can be stored together in an address pool. However, as the required resources differ based on the types of servers and server virtualization software, when managing different servers, division of the access pool simplifies management. The method of division should be matched to that of the server pool.
MAC address (Media Access Control Address) | WWN | |
|---|---|---|
Blade servers (VIOM is required) | Yes | Yes |
Rack mount servers (VIOM or ISM is required) | Yes | Yes |
Rack mount servers (HBA address rename is required) | No | Yes |
Yes: Necessary
No: Not necessary
MAC Address (Media Access Control Address) | WWN | |
|---|---|---|
RHEL5-Xen, KVM, and Citrix Xen | Yes | No |
Virtualization software other than RHEL5-Xen, KVM, and Citrix Xen | No | No |
Yes: Necessary
No: Not necessary
In the following cases, separate address pools:
When separating the LAN for each tenant, and registering MAC addresses for firewalls etc.
When separating the SAN for each tenant, and setting WWNs for fibre channel switch zoning
When using software that is aware of MAC addresses for license authentication etc.
Note
When multiple address sets are created, design the ranges of addresses so that they do not overlap between the address sets.
When a range of addresses overlaps on the same LAN or SAN network, it may become impossible to communicate correctly, and data may be damaged by same volume access.
When creation of address sets in which overlapping of the range of the MAC addresses is unavoidable, ensure that the following system design is performed, and no MAC address is duplicated on same LAN network.
Separate the network segments (VLAN)
Configure an excluded range of MAC addresses so that a duplicated MAC address is not assigned
