UCS replicating tamplate / service profile

Hello Experts
I have about 50 datacenters deployed with Cisco UCS
All datacenter have the same exec hardware and using the same UUID pools same MACs
the only diffrence between them is the IP scheme
I want to create a new template or service profile for only one of the B200 Blades and inject it to each one of my datacenters
I have tried to do it with command line script but not much luck
I am familiar with the backup and restore options but I am unable to export only one of the service profile only all of them
Is what I am asking possible ?
Thanks ahead and best wishes
Mitch

Mitch,
Couple of comments - I would use extreme caution when using duplicate MACs. If you ever have to interconnect your DCs you're going to be in a mess of trouble. Since you can craft your own MACs people will normally use one octect to designate the "site".
Ex. 00:25:B5:AA:BB:BB
00:25:B5 = Cisco's OUI
AA = Site ID
BB:BB = Unique Identifier
You should be able to use a Power shell script to inject the new profile to each of your UCSM domains.
Jeremy Waldrop has done a great job utlizing this. Check out his blog. He's put together an incredible PowerShell script you should be able to re-use with some slight modifications.
http://jeremywaldrop.wordpress.com/2012/04/05/cisco-ucs-powershell-configuration-script/
You'll also find some great reference commands in the Quick Start guide:
Regards,
Robert

Similar Messages

UCS Central: How Global Service Profile match DG

Hi
I'm pretty new to UCS Central and I've got a rudimentary UCS Central question.
I wonder how Global Service Profiles match/relate to domain groups.
To what I've read so far we use different domain groups to apply different operational policies to differenent UCS systems.
How does this relate/interact with global service profiles?
Is there a way to make sure that some service profiles could be associated just to UCS servers belonging to one DG?
Or is everything which is related to global service profiles like MAC-adresses, policies and the service profiles themselves always at the root and therefore can always be applied to all UCS servers managed within one UCS Central installation?
best regards
Dani

Hi Dani,
Global Service Profiles fall under the Organization structure.     And the Organization structure/hierarchy has no relationship/dependency to Domain Groups.
So limitting visibility of Global Service Profiles/Templates to certain Domain Groups --- no, you'd have to limit them within an Organizational context.
Hope this helps,
       -Jeff

Change Boot Policy and Firmware Version for Service Profile using UCS PowerTool

I'm looking for the PowerTool syntax to modify both of these values on individual service profiles. The documentation behind most of these cmdlests is almosts non-existent.
I believe the boot policy may be able to be changed like this:
Set-UcsServiceProfile -BootPolicyName
As for the host firmware version under the policies tab of the SP... I have no idea what that cmdlet would be.
See attached images for examples.
Thanks in advance,
JD

Hello,
One version of the User guide for UCS powertool can be found here:
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/msft_tools/powertools/ucs_powertool_book/ucs_pwrtool_bkl1.html
That guide makes notes of the following commands in regards to HFPs:
Host Firmware Package
Create a Host Firmware package and set IgnoreCompCheck to No.
$host_firm_pack = Add-UcsFirmwareComputeHostPack -Name host_firm_pack -IgnoreCompCheck no
Add a Host Firmware pack item.
$host_firm_pack | Add-UcsFirmwarePackItem -Type adaptor -HwModel N20-AC0002 -HwVendor "Cisco Systems Inc"
-Version '1.4(1i)'
Set version of Host Firmware pack item.
$host_firm_pack | Get-UcsFirmwarePackItem -HwModel N20-AC0002 | Set-UcsFirmwarePackItem -Version '2.0(1t)'
Remove Host Firmware package.
$host_firm_pack | Remove-UcsFirmwareComputeHostPack
I would also like to recommend the Cisco Developed integrations section which may be more specific to the powertool:
https://communities.cisco.com/community/technology/datacenter/ucs_management/cisco_ucs_developed_integrations/content?filterID=contentstatus[published]~category[ucs-powertool]
As well as the Cisco Developers Network:
https://developer.cisco.com/site/devnet/home/index.gsp
Regards,
-Gabriel

Managing service profiles and servers through UCS Central

Hello,
I am designing a workflow for automating server installations through PXE boot with global service profiles.
it creates a (global) SP and assigns a server for it, but then changing boot policy for the SP does not work, I assume because the SP is created from a template. Also Director seems to miss the required tasks to boot the SP/server through Central, and server assign return ucs server identity as empty so the UCS tasks do not work either.
Any suggestions how this can be done besides using local SPs in manager?

Hi Dani,
Global Service Profiles fall under the Organization structure. And the Organization structure/hierarchy has no relationship/dependency to Domain Groups.
So limitting visibility of Global Service Profiles/Templates to certain Domain Groups --- no, you'd have to limit them within an Organizational context.
Hope this helps,
-Jeff

How to move a standalone Cisco C series to UCS managed service profile without losing data?

Hi,
We currently have a standalone cisco C series server with Windows 2012 installed on the local disks. We need to move this server to Cisco UCS managed with a service profile but cannot lose the existing data and OS boot method.
Does anyone know how to do this?
Thanks

Hi Adrian,
To be able to accomplish this set the local disk policy to "Any Configuration" this way UCSM won't overwrite the current raid configuration on the server.
See link below
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/gui/config/guide/2-1/b_UCSM_GUI_Configuration_Guide_2_1/b_UCSM_GUI_Configuration_Guide_2_1_chapter_011110.html#task_897FABF194524BDF8C0EF72E755972F0
Let it me know if this helps

UCS 1.4 and Custom Service Profile Numbers

Is there a way to customze the numbers that get appended a Service profile either at creation or after the fact?

Doesn't look like there is a way to change the name once it is created. You can give it a user Label under properties which will describe what the Service Profile is being used for in greater detail.
I assume you are creating Service Profiles from a template?
It looks like you can say how many you want and it will give it your name and number starting with 1, and counting up.
If you are looking to create unique names with your own numbering scheme it looks like you will have to clone an existing service profile, or create unique service profiles.
Mat

How to change power state in a Service Profile Template

I'd like to change the setting "Power State" in a Service Profile Template. While I can change nearly every other aspect of the template, I can't find this in the UCS Manager GUI. Is this an immutable decision while creating the template? Can I change it via the CLI?

Hi Joernclausen,
What is the firmware version of your UCS?
From the CLI try the following and let me know if it works.
Go into the FI CLI and perform the steps below, ensure to enter your own template_name and select appropriate type of template followed by setting the power up or down
sj-ucs-r13-mon-A# scope org
sj-ucs-r13-mon-A /org # enter service-profile template_name initial-template
sj-ucs-r13-mon-A /org/service-profile # power up
sj-ucs-r13-mon-A /org/service-profile* # commit-buffer
sj-ucs-r13-mon-A /org/service-profile # power down
sj-ucs-r13-mon-A /org/service-profile* # commit-buffer
You may also be able to change the power state from the individual service profiles
Go to the service profile and use "Change Initial Power State" button for modifying the desired-power value.
see attached screenshot

Service Profiles Migration between Server M2 and M3

Hi Cisco Top Guns!!!
I have tried to migrate some service profiles between servers M2 (with M81KR) to M3 (with Vic 1240 and Vic 1280) and Windows 2008 R2 recognized the interfaces on M3 as new interfaces.
The ghost devices interfaces (old interfaces) still presents on Windows and to rename the new interfaces or apply the same IP configurations, I need to remove the ghosts interrfaces.
On my opinion, this change goes against the UCS philosophy.
I have a case opened with Cisco Developed Team and now Im sharing this issue with the community. Anyone have benn passed for this problem too?
Regards,
Fábio Henrique Teixeira - System ITS

This is a hardware change to the operating system. While UCSM can abstract the MAC/WWPN/WWNN information, the operating system recognizes a hardware adapter difference and will instatiate new devices. This is an OS issue. Some OS's (Linux) will allow you to set a flag to ignore the hardware change. I'm not aware of whether and what versions of Windows that will allow the same behavor. We cannot modfy the hardware identification change, as we use it within UCSM to manage allowable firmware bundles and adapter polices (vnics/vhbas/fabric failover)

Handling Service Profiles & RBA

Hi Togheter,
We are using the using the version 1.4(1j) and have the service profile structured like this:
- Environment A
     -Service Profile1
     -Service Profile2
     -Service Profile3
- Environment B
     -Service Profile10
     -Service Profile11
     -Service Profile12
- Environment C
     -Service Profile21
     -Service Profile22
     -Service Profile23
Let's focus on the environment A. There is for example an exchange administrator whos got 2 server (service profile1 & 3). I want to give him the option to administrate his server over the UCS (well just console & reboot in case he is facing some problems). But he only should be authorized to his 2 servers.
The only way I see to handle it that way is to reoganize the structure like this:
-Enironment A
     - Service Exchange
          -Service Profile1
          -Service Profile 3
     - Service B
Now I can create a locale which is refering to "Service Exchange", combine that with the server-profile role and map this to the "exchange-user".
But is it even possible to move an existing service-profile to a sub ou? I just the "copy" possibility which is going to change all values like MAC-address, UUID, WWPN, and so on.
Can somebody give me an input?
Thanks in advanced
Philippe

Hi Tony,
You need a service profile for each esxi server, template only provides a blue print.
As a best practise you can deploy service profiles from a template to maintain uniformity and consistency and reduce any errors while creating the sp.
Initial template is static and updating is dynamic I.e any change made to the updating template will also be updated on the sp deployed using that template which will not happen with the initial.
Hope this helps!
./abhinav
Sent from Cisco Technical Support iPad App

No Local Service Profiles

I have 4 x 2.1(2a) UCS Domains connected to aUCS Central 1.1a server. Everything is showing up correctly EXECPT for the Servers tab. It is only showing templates in the "Local Service Profile Templates" section. There are no "Local Service Profiles" showing up in the list for any of the 231 servers on the 4 domains.
The UCS Central software was updated to version 1.1a from 1.0a after the upgrade of the 4 UCS domains to 2.1(2a).
Any troubleshooting help or direction would be appreciated.
- Chris

Hello Chris,
As CLI displays it correctly, can you please accessing Central from different system / web browser and verify the outcome ?
If the outcome is same on different system / web browsers, please collect UCS Central techsupport and open a TAC service request.
Collecting Central Techsupport bundle
http://www.cisco.com/en/US/products/ps12502/products_tech_note09186a0080c0c917.shtml
Padma

Are UCS hardware upgrades service disruptive?

Hi Community,
Is fabric interconnect hardware upgrade from dual (clustered) 6120XP to dual 6248 service disruptive?
Is adding a new 5108 chassis to the existing UCS configuration with dual 6120XP service disruptive?

Thanks Kenny.
1). I have actually been using this document for my project, and I think I worked out a pretty good migration plan based on it, but there are some grey areas/questions, MARKED IN BOLD CAPS. Could you clarify them for me?
Step 1 Upgrade UCS firmware across all the devices to the same version - 2.1(1f). THE NEW 6248S CAN BE TEMPORARY CONFIGURED AS STANDALONE OR IN A CLUSTER FOR THE FIRMWARE UPGRADE, AND THEN THE CONFIGURATION SHOULD BE WIPED OUT AND THE FABRIC INTERCONNECTS POWERED OFF.
Step 2 Using either the UCS manager CLI or GUI, verify the state (subordinate or active) of the existing (production) fabric interconnects.
!!! Step 3 Back up the software configuration information and the UCS Manager software !!!
Step 4 Disable the server ports on the subordinate fabric interconnect – NEW or EXISTING? THIS STEP IS CONFUSING AND IT IS REFERENCED IN STEP 17.
Step 5 Power down the EXISTING subordinate fabric interconnect by unplugging it from the power source. If you are monitoring the upgrade using a KVM session, you may need to reconnect the KVM session when you power down the fabric interconnect.
THE NEW FABRIC INTERCONNECT(S) SHOULD BE POWERED OFF AT THIS POINT
Step 6 Disconnect the cables running from the chassis IO Modules to the subordinate fabric interconnect ports in slot 1 (the old EXISTING fabric interconnect).
Step 7 Connect these cables into the corresponding ports in slot 1 on one of the new Cisco UCS 6248 UP fabric interconnect, using the connection records to preserve the port mapping and the configured server pinning.
See Fabric Interconnect Port Connection Record, on page 7.
See Fabric Interconnect Upgrade Considerations, on page 1.
Step 8 Disconnect the L1/L2, M1 management, and Console cables on the old fabric interconnect. The ports for these connections are on the opposite side of the interconnect, so if your cables are just barely long enough to connect two rack-adjacent UCS 6120 interconnects you will probably need new cables.
Step 9 Connect the M1 management, and Console cables to the new Cisco UCS 6248 UP.
Step 10 Connect the L1/L2 cables that were disconnected to the new Cisco UCS 6248 UP. L1 connects to L1, L2 connects to L2.
Step 11 Disconnect the Ethernet or FC cables from slot 2 of the old fabric interconnect.
Step 12 Connect the Ethernet or FC cables to the corresponding ports in slot 2 of the new Cisco UCS 6248 UP. Some may go to slot 1, depending on the mappings planned out earlier in the process
I HAVE NO SLOT 2 ON THE NEW FABRIC INTERCONNECTS ON THE OLD ONES, SIX PORTS IN SLOT 2 ARE CONFIGURED AS FIBER CHANNEL PORTS. WILL I NEED TO MANUALLY CONFIGURE LAST SIX PORTS AS FC PORTS? IF YES, AT WHAT STEP IS THIS CONFIGURATION DONE, AND ARE THE FIBER CHANNEL CABLES SUPPOSED TO BE PLUGGED IN BEFORE OR AFTER THE PORTS ARE CONFIGURED AS FC PORTS?
Step 13 Connect the power to the new Cisco UCS 6248 UP, it will automatically boot and run POST tests.
Important: Directly connect the console cable to a terminal and observe the boot sequence. You should at some point see the Basic System Configuration Dialog, where you will configure the switch as a subordinate interconnect. - IS THIS THE WIZARD THAT RUNS ON EVERY UNCONFIGURED FABRIC INTERCONNECT WHEN YOU POWER IT ON, WHEN YOU HAVE TO GIVE IP, NAME, DNS, ETC.? CAN I USE THE SAME IP THAT WAS ON THE OLD FABRIC INTERCONNECT?
If you do not see this dialog, you either have different builds of software on your old primary and new subordinate, or the new subordinate has previously been part of a cluster and will need to have all configuration information wiped before it can be added to a cluster as a subordinate. In either case, immediately disconnect the L1 and L2 connections and complete the bringup as a standalone fabric interconnect, then correct the issue before proceeding further.
I AM NOT SURE IF THE NEXT STEP IS APPLICABLE TO ME AT ALL, AS I DO NOT HAVE N10-E0440, I HAVE N10-E0060. COULD YOU COMMENT ON THIS?
Step 14 (Optional) Remap UCS 6100 fabric interconnect FC ports 2/1 to 2/4 on a N10-E0440 expansion module or any slot 3 ports onto the new fabric interconnect expansion module.
a) Use UCS Manager to delete the ports on the subordinate fabric interconnect that you will need to move within the configuration - WHERER DO I DELETE THE PORTS - ON THE NEW ONE?
b) For each port you have just deleted, create new ports on either slot 1 or slot 2. These ports must use the same port type definitions as the old ports, but will use different port numbers.
c) For recently moved Ethernet server ports, reconfigure the associated service profile to use the new port number for the appropriate LAN pin group.
d) For recently moved uplink Ethernet ports, reconfigure the port channel settings to use the new ports.
e) For recently moved uplink FC ports, reconfigure the associated service profile SAN pin group to use the new ports.
f) Re-acknowledge chassis for blade servers and fabric extender for rack servers.
This will be disruptive to traffic, but is necessary in this specific scenario. DO I LOOSE CONNECTIVITY FOR THE ENTIRE CHASSIS, OR JUST ONE FABRIC?
Step 15 The new subordinate fabric interconnect will automatically synchronize the configuration and database/state information from the primary fabric interconnect. Synchronization between primary and subordinate fabric interconnects can take several minutes. The port configuration is copied from the subordinate switch to the new hardware.
Step 16 Verify that the data path is ready.
See Verifying that the Data Path is Ready.
Make sure all faults are resolved before proceeding.
a) Verify and if necessary reconfigure the SAN pin group for FC ports in the associated service profile.
b) Verify and if necessary reconfigure the LAN pin group for Ethernet ports in the associated service profile.
c) Verify and if necessary reconfigure the port channel for uplink Ethernet ports.
THE FOLLOWING STEP IS ALSO CONFUSING. IF IT IS TALKING ABOUT THE OLD SUBORDINATE FABRIC INTERCONNECT THAT IS BEING REPLACED, WHY DO WE NEED TO ENABLE THE SERVER PORTS ON IT, THERE IS NOTHING CONNECTED TO IT. IF IT IS TALKING ABOUT THE NEW ONE - 6248, THEN, IT MEANS THEY HAVE TO BE DISABLED IN STEP 4, BUT IT MAKES NO SENSE, BECAUSE THEY ARE NOT SUPPOSED TO HAVE ANY CONFIGURATION ON IT. CAN YOU CLARIFY?
Step 17 Enable the server ports that had been disabled in Step 4. -
a) If you have changed port mappings, you may need to re-acknowledge the chassis or rack server connected to the subordinate fabric interconnect. DOES IT APPLY TO ALL TYPES OF PORTS – FC, SERVER, UPLINK ETHERNET PORTS?
b) Verify and if necessary reconfigure Ethernet ports as server ports.
Step 18 Promote the subordinate fabric interconnect to active, and repeat the process on the second Cisco UCS 6248 UP. Cable the second new fabric interconnect identically to the first, and allow the reconfiguration done to be applied to the second new fabric interconnect as well. DOES THE SECOND NEW 6248 NEED TO BE OFF OR ON WHEN CABLING IT? DO I NEED TO GO THROUGH THE WIZARD AT THE POWER ON TO MAKE IT A PART OF THE CLUSTER?
See Forcing a Fabric Interconnect Failover.
2). Does CISCO have a document outlining the steps for adding a chassis?
Regards,
Maxim.

Can't auto decommission and move service profile to new server

When blade hardware is fail service profile will move to new server in server pool. but before service profile move to new server ,administrator must approve by click Decommission link in server pool configuration. If i tested by click Decommission in Server Maintennance Menu it work fine but tested by Unmount Blade Server ,Unmount HDD ,Power button don't work service profile don't move to new server.
I need automatic decommission function and how i config it?
When service profile move to new server if blade hardware fail?

Thank you for answer.
I has open TAC and then answer from Cisco support is no auto decommission in UCSM.
I think is Weakness of cisco ucs system.
UCS Develop team can you provide simple script auto decommission for me and another customer ?

Service Profiles and Cisco Unified Communications

Hi All,
I need some information on Service Profile configuration for ESXi hosts that will be running Cisco Unified Communications Manager and associated applications (Unity Connections and Presence)
The B-Series Chassis will initially host 2 B200M2 blades for this purpose and I'm after best practice for the Service Profiles. The blades are running the M81KR Virtual Interface Card.
Any help is appreciated, or if someone can point me in the direction of the documentation that would also be appreciated.
Cheers
Darren

It's quite straightforward:
- you must boot from local disk
- bundle your local drives in a RAID-1 group
- assign a pair of vHBAs to your profile for connectivity to your FC SAN (one to SAN "A", one to SAN "B")
- as far as networking in concerned, you have "carte blanche" (UC VMs use a single nic and Nexus 1000V is optional)
--> you could for instance create 6 vnics: 2 for service console, 2 for vmotion, 2 for vmdata. Or just 2 vnics and have Nexus 1000V "own" them. Any other scheme you find suitable is ok.
Most restrictions aren't on the UCS side but rather on specific VMware features currently supported by the solution.
See
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html
http://docwiki.cisco.com/wiki/Unified_Communications_VMWare_Requirements
The OVA templates for the UC VMs are at http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29 --> you'll get an idea of storage capacity and vCPU requirements

Service profiles auto association

Hi, if a server goes down, is it possible to configure the service profile for moving automatically to another server from the servers pool?

No. UCS will not do automation like this. The reason is because its a tough call to determine what qualifies a server as "being down" - loss of networking, loss of management, loss of power, OS crash etc We wouldn't want UCSM moving around hosts unless certain criteria were met. This has been heavily discussed internally and it was decided that UCSM would not touch SP movement pertaining to host failures.
There are other management Apps that can handle the orchestration piece like this - which tie into UCSM very nicely via the XML API.
Regards,
Robert

Jabber 4 Everyone default service profile

Hello all,
A customer running UCM 9.1.2 with IM&P 9.1.2. They have rolled out Jabber Desktop as the default application for IM and Presence for the organization. We have setup several "SERVICE PROFILES" inside of UCM to differentiate between Ehanced Presence for employees that have both IP Phones and Jabber, and just Regular Presence for employees that do not have an IP Phone on the system. We made the Regular Presence the "DEFAULT SERVICE PROFILE" and then we ran a bulk update to update all users "currently" in the directory to have the option
HOME CLUSTER and ENABLE User for Unified CM IM and Presence.
CUCM is AD integrated so all the users come from AD
The issue we are experiencing is for any new hires, the account gets created in AD then eventually sync'ed into CUCM. We can't find a switch that allows us to make sure new users have certain "DEFAULT USER" settings namely "HOME CLUSTER" and "Enable User for Unified CM IM and Presence. So these new users are not getting this setting and can not login to Jabber until this occures
Thanks

Hi Ryan,
I have the same issue and at the moment no solution for that.
I have a bulk user template, so everytime new users come in, I bulk the setting over the new users.
Would be nice to see, if someone has another solution.
Best regards
Ben

UCS replicating tamplate / service profile

Similar Messages

Maybe you are looking for