- Preface
-
- Configuring the Fabric Interconnects
- Configuring Ports and Port Channels
- Configuring Communication Services
- Configuring Authentication
- Configuring Organizations
- Configuring Role-Based Access Control
- Managing Firmware
- Configuring DNS Servers
- Configuring System-Related Policies
- Managing Licenses
- Managing Virtual Interfaces
- Index
Configuring WWN Pools
This chapter includes the following sections:
WWN Pools
A WWN pool is a collection of WWNs for use by the Fibre Channel vHBAs in a Cisco UCS domain. You create separate pools for the following:
A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. All other WWN ranges are reserved. To ensure the uniqueness of the Cisco UCS WWNNs and WWPNs in the SAN fabric, we recommend that you use the following WWN prefix for all blocks in a pool: 20:00:00:25:B5:XX:XX:XX
If you use WWN pools in service profiles, you do not have to manually configure the WWNs that will be used by the server associated with the service profile. In a system that implements multi-tenancy, you can use a WWN pool to control the WWNs used by each organization.
You assign WWNs to pools in blocks. For each block or individual WWN, you can assign a boot target.
WWNN Pools
A WWNN pool is a WWN pool that contains only WW node names. If you include a pool of WWNNs in a service profile, the associated server is assigned a WWNN from that pool.
WWPN Pools
A WWPN pool is a WWN pool that contains only WW port names. If you include a pool of WWPNs in a service profile, the port on each vHBA of the associated server is assigned a WWPN from that pool.
Creating a WWN Pool
A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. All other WWN ranges are reserved. To ensure the uniqueness of the Cisco UCS WWNNs and WWPNs in the SAN fabric, we recommend that you use the following WWN prefix for all blocks in a pool: 20:00:00:25:B5:XX:XX:XX
The following example creates a WWN pool named sanpool, provides a description for the pool, specifies a block of WWNs and an initiator to be used for the pool, and commits the transaction:
UCS-A# scope org / UCS-A /org # create wwn-pool sanpool node-wwn-assignment UCS-A /org/wwn-pool* # set descr "This is my WWNN pool" UCS-A /org/wwn-pool* # create block 23:00:00:05:AD:1E:00:01 23:00:00:05:AD:1E:01:00 UCS-A /org/wwn-pool/block* # exit UCS-A /org/wwn-pool* # create initiator 23:00:00:05:AD:1E:02:00 UCS-A /org/wwn-pool/initiator* # commit-buffer UCS-A /org/wwn-pool/initiator #
Include the WWPN pool in a vHBA template.
Deleting a WWN Pool
If you delete a pool, Cisco UCS Manager does not reallocate any addresses from that pool that have been assigned to vNICs or vHBAs. All assigned addresses from a deleted pool remain with the vNIC or vHBA to which they are assigned until one of the following occurs:
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | UCS-A# scope org org-name | Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name. |
| Step 2 | UCS-A /org # delete wwn-pool pool-name | Deletes the specified WWN pool. |
| Step 3 | UCS-A /org # commit-buffer | Commits the transaction to the system configuration. |
The following example deletes the WWN pool named pool4 and commits the transaction:
UCS-A# scope org / UCS-A /org # delete wwn-pool pool4 UCS-A /org* # commit-buffer UCS-A /org #
Feedback