Migrating local domain resource pool to global resource pool

[Walter Dey]

I've seen once a paper (maybe best practise for Cisco Central), how to migrate a local domain resource pool (eg. mac) to a global Cisco Central resource pool, in a non disruptive fashion. Use case: customer would like to use global service profiles.     

can some elaborate, if this is possible, and if yes, officially supported ?

Thanks

Walter.            

[padramas]

Hello Walter,

Check out the section " Migrating from Existing ID Pools " in the following guide

Cisco UCS Central Best Practices

Updated for Release 1.1(1a)

Revision 2.05

https://communities.cisco.com/docs/DOC-35264

Attached same document to this thread.

Padma

[Jeffrey Silberman]

Hi Walter,

For this to work in a non-disruptive manner, you *must* be at UCSM 2.1.3

In addition, after pointing to the Global Pool, you will still need to do a "Reset Address" (for MAC or WWPN) in order for the global referencing to complete.

Please also take note of Chapter 8 and keep in mind that for the time being, we are recommending that existing workload be kept in locally managed mode.    Operational policies (think"Admin" tab) can be easily globalized.   But existing local policies can only be globalized manually, until the next release.

Hope this helps,

   -Jeff

[Walter Dey]

Thanks Jeff

In addition, after pointing to the Global Pool, you will still need to do a "Reset Address" (for MAC or WWPN) in order for the global referencing to complete.

Is this disruptive

Please also take note of Chapter 8 and keep in mind that for the time being, we are recommending that existing workload be kept in locally managed mode.    Operational policies (think"Admin" tab) can be easily globalized.   But existing local policies can only be globalized manually, until the next release.

Do I understand you correctly ? Global SP using global pool is ok today !

Customer usually introduced a UCS domain id, for the local resource pools, to be sure, therefore its values are globally unique.

What is best practise ? should this be done, even with global pools becoming available ? or are global pools just to be used for global SP ?

[Jeffrey Silberman]

Walter,

"Reset Address" will not be disruptive --- *assuming* you are on 2.1.3, and have created Global ID Pools in the manner outlined in the Best Practice Guide.   If the same ID exists in both the Local and the Global Pool, and if you change the pool reference from Local to Global, and if the same Global ID is unused --- then the "Reset Address" will not be disruptive under UCSM 2.1.3 and above.

Do I understand you correctly ? Global SP using global pool is ok today !

(???)

Global SP can only be deployed with Global ID Pools.    Local SP's "can" reference Global ID pools, and "can" reference Global Policies --- but they will still be Local SP's, owned by the local UCSM, and cannot move between domains.

Customer usually introduced a UCS domain id, for the local resource pools, to be sure, therefore its values are globally unique.

What is best practise ? should this be done, even with global pools becoming available ? or are global pools just to be used for global SP ?

Please check out the Best Practice Guide, page 16 for a discussion on this point of creating easily differentiated Global versus Local ID Pools.

Hope this helps,

    -Jeff

[Walter Dey]

Thanks Jeff

Is this correct: Global Mac pool, consisting of 4 block each having 512 addresses.

If 4 UCS domains are connected to UCS Central, I can achieve with a ID Range qualification, that each domain, gets addresses out of his block of mac ? correct ?

Is there a way to have sequential alloaction per block ?

Walter.

[Jeffrey Silberman]

Walter,

The ID Range Qualifier only applies for Local Service Profiles, interestingly enough --- not Global Service Profiles.    So you can partition Local Service Profiles by Global MAC ID pools, as you describe --- but you can't do that for Global Service Profiles.   Please note.

No way I can see to have sequential allocation.

-Jeff