Feedback
Contents
- Configuring Service Profiles
- Service Profiles that Inherit Server Identity
- Service Profiles that Override Server Identity
- Service Profile Templates
- Creating a Service Profile Template
- Creating a Service Profile Instance from a Service Profile Template
- Creating a Service Profile
- Configuring a vNIC for a Service Profile
- Configuring a vHBA for a Service Profile
- Configuring a Local Disk for a Service Profile
- Configuring Serial over LAN for a Service Profile
- Configuring a Boot Definition for a Service Profile
- Configuring a LAN Boot for a Service Profile Boot Definition
- Configuring a Storage Boot for a Service Profile Boot Definition
- Configuring a Virtual Media Boot for a Service Profile Boot Definition
- Deleting a Boot Definition for a Service Profile
- Associating a Service Profile with a Server or Server Pool
- Disassociating a Service Profile from a Server or Server Pool
- Resetting the UUID Assigned to a Service Profile from a Pool in a Service Profile Template
- Resetting the MAC Address Assigned to a vNIC from a Pool in a Service Profile Template
- Resetting the WWPN Assigned to a vHBA from a Pool in a Service Profile Template
Configuring Service Profiles
This chapter includes the following sections:
- Service Profiles that Inherit Server Identity
- Service Profiles that Override Server Identity
- Service Profile Templates
- Creating a Service Profile Template
- Creating a Service Profile Instance from a Service Profile Template
- Creating a Service Profile
- Configuring a vNIC for a Service Profile
- Configuring a vHBA for a Service Profile
- Configuring a Local Disk for a Service Profile
- Configuring Serial over LAN for a Service Profile
- Associating a Service Profile with a Server or Server Pool
- Disassociating a Service Profile from a Server or Server Pool
- Resetting the UUID Assigned to a Service Profile from a Pool in a Service Profile Template
- Resetting the MAC Address Assigned to a vNIC from a Pool in a Service Profile Template
- Resetting the WWPN Assigned to a vHBA from a Pool in a Service Profile Template
- Configuring a Boot Definition for a Service Profile
- Deleting a Boot Definition for a Service Profile
Service Profiles that Inherit Server Identity
This hardware-based service profile is the simplest to use and create. This profile uses the default values in the server and mimics the management of a rack-mounted server. It is tied to a specific server and cannot be moved to another server.
You do not need to create pools or configuration policies to use this service profile.
This service profile inherits and applies the identity and configuration information that is present at the time of association, such as the following:
MAC addresses for the two NICs
For a converged network adapter or a virtual interface card, the WWN addresses for the two HBAs
BIOS versions
Server UUID
Important:The server identity and configuration information inherited through this service profile may not be the values burned into the server hardware at manufacture if those values were changed before this profile is associated with the server.
Service Profiles that Override Server Identity
This type of service profile provides the maximum amount of flexibility and control. This profile allows you to override the identity values that are on the server at the time of association and use the resource pools and policies set up in Cisco UCS Manager to automate some administration tasks.
You can disassociate this service profile from one server and then associate it with another server. This re-association can be done either manually or through an automated server pool policy. The burned-in settings, such as UUID and MAC address, on the new server are overwritten with the configuration in the service profile. As a result, the change in server is transparent to your network. You do not need to reconfigure any component or application on your network to begin using the new server.
This profile allows you to take advantage of and manage system resources through resource pools and policies, such as the following:
Service Profile Templates
With a service profile template, you can quickly create several service profiles with the same basic parameters, such as the number of vNICs and vHBAs, and with identity information drawn from the same pools.
Tip
If you need only one service profile with similar values to an existing service profile, you can clone a service profile in the Cisco UCS Manager GUI.
For example, if you need several service profiles with similar values to configure servers to host database software, you can create a service profile template, either manually or from an existing service profile. You then use the template to create the service profiles.
Cisco UCS supports the following types of service profile templates:
- Initial template
Service profiles created from an initial template inherit all the properties of the template. However, after you create the profile, it is no longer connected to the template. If you need to make changes to one or more profiles created from this template, you must change each profile individually.
- Updating template
Service profiles created from an updating template inherit all the properties of the template and remain connected to the template. Any changes to the template automatically update the service profiles created from the template.
Creating a Service Profile Template
ProcedureWhat to Do NextThe following example creates a service profile template and commits the transaction:
UCS-A# scope org / UCS-A /org* # create service-profile ServTemp2 updating-template UCS-A /org/service-profile* # set boot-policy BootPol32 UCS-A /org/service-profile* # set descr "This is a service profile example." UCS-A /org/service-profile* # set dynamic-vnic-conn-policy MyDynVnicConnPolicy UCS-A /org/service-profile* # set host-fw-policy Epuser987 UCS-A /org/service-profile* # set identity dynamic-uuid derived UCS-A /org/service-profile* # set ipmi-access-profile IpmiProf16 UCS-A /org/service-profile* # set local-disk-policy LocalDiskPol33 UCS-A /org/service-profile* # set mgmt-fw-policy MgmtFwPol75 UCS-A /org/service-profile* # set scrub-policy ScrubPol55 UCS-A /org/service-profile* # set sol-policy SolPol2 UCS-A /org/service-profile* # set stats-policy StatsPol4 UCS-A /org/service-profile* # vcon-profile MyVconnProfile UCS-A /org/service-profile* # commit-buffer UCS-A /org/service-profile #Creating a Service Profile Instance from a Service Profile Template
Before You BeginProcedureVerify that there is a service profile template from which to create a service profile instance.
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 # create service-profile profile-name instance Creates the specified service profile instance and enters organization service profile mode.
Enter a unique profile-name to identify this service profile template.
This name can be between 2 and 32 alphanumeric characters. You cannot use spaces or any special characters, and you cannot change this name after the object has been saved.
Step 3 UCS-A /org/service-profile # set src-templ-name profile-name Specifies the source service profile template to apply to the service profile instance. All configuration settings from the service profile template will be applied to the service profile instance.
Step 4 UCS-A /org/service-profile # commit-buffer Commits the transaction to the system configuration.
What to Do NextThe following example creates a service profile instance named ServProf34, applies the service profile template named ServTemp2, and commits the transaction:
UCS-A# scope org / UCS-A /org* # create service-profile ServProf34 instance UCS-A /org/service-profile* # set src-templ-name ServTemp2 UCS-A /org/service-profile* # commit-buffer UCS-A /org/service-profile #
Associate the service profile to a server or server pool.
Creating a Service Profile
Procedure
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 # create service-profile profile-name instance Creates the specified service profile instance and enters organization service profile mode.
Enter a unique profile-name to identify this service profile template.
This name can be between 2 and 32 alphanumeric characters. You cannot use spaces or any special characters, and you cannot change this name after the object has been saved.
Step 3 UCS-A /org/service-profile # set boot-policy policy-name Associates the specified boot policy with the service profile.
Step 4 UCS-A /org/service-profile # set descr description (Optional) Provides a description for the service profile.
Note If your description includes spaces, special characters, or punctuation, you must begin and end your description with quotation marks. The quotation marks will not appear in the description field of any show command output.
Step 5 UCS-A /org/service-profile # set dynamic-vnic-conn-policy policy-name Associates the specified dynamic vNIC connection policy with the service profile.
Step 6 UCS-A /org/service-profile # set host-fw-policy epuser-name Associates the specified host forwarding policy with the service profile.
Step 7 UCS-A /org/service-profile # set identity {dynamic-uuid {uuid | derived} | dynamic-wwnn {wwnn | derived} | uuid-pool pool-name | wwnn-pool pool-name} Specifies how the server acquires a UUID or WWNN. You can do one of the following:
Create a unique UUID in the form nnnnnnnn-nnnn-nnnn-nnnnnnnnnnnn.
Derive the UUID from the one burned into the hardware at manufacture.
Use a UUID pool.
Create a unique WWNN in the form hh : hh : hh : hh : hh : hh : hh : hh.
Derive the WWNN from one burned into the hardware at manufacture.
Use a WWNN pool.
Step 8 UCS-A /org/service-profile # set ipmi-access-profile profile-name Associates the specified IPMI access profile with the service profile.
Step 9 UCS-A /org/service-profile # set local-disk-policy policy-name Associates the specified local disk policy with the service profile.
Step 10 UCS-A /org/service-profile # set mgmt-fw-policy policy-name Associates the specified management forwarding policy with the service profile.
Step 11 UCS-A /org/service-profile # set scrub-policy policy-name Associates the specified scrub policy with the service profile.
Step 12 UCS-A /org/service-profile # set sol-policy policy-name Associates the specified serial over LAN policy with the service profile.
Step 13 UCS-A /org/service-profile # set stats-policy policy-name Associates the specified statistics policy with the service profile.
Step 14 UCS-A /org/service-profile # set vcon {1 | 2} selection {all | assigned-only | exclude-dynamic | exclude-unassigned} Specifies the selection preference for the specified vCon.
Step 15 UCS-A /org/service-profile # set vcon-profile policy-name Associates the specified vNIC/vHBA placement policy with the service profile.
Note You can either assign a vNIC/vHBA placement profile to the service profile, or set vCon selection preferences for the service profile, but you do not need to do both.
Step 16 UCS-A /org/service-profile # commit-buffer Commits the transaction to the system configuration.
What to Do NextThe following example creates a service profile instance and commits the transaction:
UCS-A# scope org / UCS-A /org* # create service-profile ServInst90 instance UCS-A /org/service-profile* # set boot-policy BootPol32 UCS-A /org/service-profile* # set descr "This is a service profile example." UCS-A /org/service-profile* # set host-fw-policy Epuser987 UCS-A /org/service-profile* # set identity dynamic-uuid derived UCS-A /org/service-profile* # set ipmi-access-profile IpmiProf16 UCS-A /org/service-profile* # set local-disk-policy LocalDiskPol33 UCS-A /org/service-profile* # set mgmt-fw-policy MgmtFwPol75 UCS-A /org/service-profile* # set scrub-policy ScrubPol55 UCS-A /org/service-profile* # set sol-policy SolPol2 UCS-A /org/service-profile* # set stats-policy StatsPol4 UCS-A /org/service-profile* # vcon-profile MyVconnProfile UCS-A /org/service-profile* # commit-buffer UCS-A /org/service-profile #Configuring a vNIC for a Service Profile
Procedure
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 # scope service-profile profile-name Enters organization service profile mode for the specified service.
Step 3 UCS-A /org/service-profile # create vnic vnic-name [eth-if eth-if-name] [fabric {a | b}] Creates a vNIC for the specified service profile and enters organization service profile vNIC mode.
Step 4 UCS-A /org/service-profile/vnic # set adaptor-profile policy-name Specifies the adapter policy to use for the vNIC.
Step 5 UCS-A /org/service-profile/vnic # set identity {dynamic-mac {mac-addr | derived} | mac-pool mac-pool-name} Specifies the identity (MAC address) for the vNIC. You can set the identity using one of the following options:
Step 6 UCS-A /org/service-profile/vnic # set mtu size-num Specified the maximum transmission unit, or packet size, that the vNIC accepts.
Step 7 UCS-A /org/service-profile/vnic # set nw-control-policy policy-name Specifies the network control policy to use for the vNIC.
Step 8 UCS-A /org/service-profile/vnic # set order {order-num | unspecified} Specifies the relative order for the vNIC.
Step 9 UCS-A /org/service-profile/vnic # set pin-group group-name Specifies the pin group to use for the vNIC.
Step 10 UCS-A /org/service-profile/vnic # set qos-policy policy-name Specifies the QoS policy to use for the vNIC.
Step 11 UCS-A /org/service-profile/vnic # set stats-policy policy-name Specifies the stats policy to use for the vNIC.
Step 12 UCS-A /org/service-profile/vnic # set template-name policy-name Specifies the dynamic vNIC connectivity policy to use for the vNIC.
Step 13 UCS-A /org/service-profile/vnic # set vcon {1 | 2 | any} Assigns the vNIC to the specified vCon. Use the any keyword to have Cisco UCS Manager automatically assign the vNIC.
Step 14 UCS-A /org/service-profile/vnic # commit-buffer Commits the transaction to the system configuration.
The following example configures a vNIC for a service profile and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope service-profile ServInst90 UCS-A /org/service-profile* # create vnic vnic3 fabric a UCS-A /org/service-profile/vnic* # set adaptor-profile AdaptPol2 UCS-A /org/service-profile/vnic* # set identity mac-pool MacPool3 UCS-A /org/service-profile/vnic* # set mtu 8900 UCS-A /org/service-profile/vnic* # set nw-control-policy ncp5 UCS-A /org/service-profile/vnic* # set order 0 UCS-A /org/service-profile/vnic* # set pin-group EthPinGroup12 UCS-A /org/service-profile/vnic* # set qos-policy QosPol5 UCS-A /org/service-profile/vnic* # set stats-policy StatsPol2 UCS-A /org/service-profile/vnic* # set template-name VnicConnPol3 UCS-A /org/service-profile/vnic* # set set vcon any UCS-A /org/service-profile/vnic* # commit-buffer UCS-A /org/service-profile/vnic #Configuring a vHBA for a Service Profile
Procedure
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 # scope service-profile profile-name Enters organization service profile mode for the specified service.
Step 3 UCS-A /org/service-profile # create vhba vhba-name [fabric {a | b}] [fc-if fc-if-name] Creates a vHBA for the specified service profile and enters organization service profile vHBA mode.
Step 4 UCS-A /org/service-profile/vhba # set adaptor-profile policy-name Specifies the adapter policy to use for the vHBA.
Step 5 UCS-A /org/service-profile/vhba # set admin-vcon {1 | 2 | any} Assignes the vHBA to one or all virtual network interface connections.
Step 6 UCS-A /org/service-profile/vhba # set identity {dynamic-wwpn {wwpn | derived} | wwpn-pool wwn-pool-name} Specifies the storage identity (world wide port name [WWPN]) for the vHBA. You can set the storage identity using one of the following options:
Step 7 UCS-A /org/service-profile/vhba # set max-field-size size-num Specifies the maximum size of the Fibre Channel frame payload (in bytes) that the vHBA supports.
Step 8 UCS-A /org/service-profile/vhba # set order {order-num | unspecified} Specifies the PCI scan order for the vHBA.
Step 9 UCS-A /org/service-profile/vhba # set pers-bind {disabled | enabled} Disables or enables persistent binding to Fibre Channel targets.
Step 10 UCS-A /org/service-profile/vhba # set pin-group group-name Specifies the pin group to use for the vHBA.
Step 11 UCS-A /org/service-profile/vhba # set qos-policy policy-name Specifies the QoS policy to use for the vHBA.
Step 12 UCS-A /org/service-profile/vhba # set stats-policy policy-name Specifies the stats policy to use for the vHBA.
Step 13 UCS-A /org/service-profile/vhba # set template-name policy-name Specifies the vHBA SAN connectivity policy to use for the vHBA.
Step 14 UCS-A /org/service-profile/vhba # commit-buffer Commits the transaction to the system configuration.
The following example configures a vHBA for a service profile and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope service-profile ServInst90 UCS-A /org/service-profile* # create vhba vhba3 fabric b UCS-A /org/service-profile/vhba* # set adaptor-profile AdaptPol2 UCS-A /org/service-profile/vhba* # set set admin-vcon any UCS-A /org/service-profile/vhba* # set admin-vcon any UCS-A /org/service-profile/vhba* # set identity wwpn-pool SanPool7 UCS-A /org/service-profile/vhba* # set max-field-size 2112 UCS-A /org/service-profile/vhba* # set order 0 UCS-A /org/service-profile/vhba* # set pers-bind enabled UCS-A /org/service-profile/vhba* # set pin-group FcPinGroup12 UCS-A /org/service-profile/vhba* # set qos-policy QosPol5 UCS-A /org/service-profile/vhba* # set stats-policy StatsPol2 UCS-A /org/service-profile/vhba* # set template-name SanConnPol3 UCS-A /org/service-profile/vhba* # commit-buffer UCS-A /org/service-profile/vhba #Configuring a Local Disk for a Service Profile
Procedure
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 # scope service-profile profile-name Enters organization service profile mode for the specified service profile.
Step 3 UCS-A /org/service-profile # create local-disk-config Creates a local disk configuration for the service profile and enters organization service profile local disk configuration mode.
Step 4 UCS-A /org/service-profile/local-disk-config # set descr description (Optional) Provides a description for the local disk configuration.
Step 5 UCS-A /org/service-profile/local-disk-config # set mode {any-configuration | no-local-storage | no-raid | raid-0-striped | raid-1-mirrored | raid-5-striped-parity | raid-6-striped-dual-parity | raid-10-mirrored-and-striped} Specifies the mode for the local disk.
Step 6 UCS-A /org/service-profile/local-disk-config # create partition Creates a partition for the local disk and enters organization service profile local disk configuration partition mode.
Step 7 UCS-A /org/service-profile/local-disk-config/partition # set descr description (Optional) Provides a description for the partition.
Step 8 UCS-A /org/service-profile/local-disk-config/partition # set size {size-num | unspecified} Specifies the partition size in MBytes.
Step 9 UCS-A /org/service-profile/local-disk-config/partition # set type {ext2 | ext3 | fat32 | none | ntfs | swap} Specifies the partition type.
Step 10 UCS-A /org/service-profile/local-disk-config/partition # commit-buffer Commits the transaction to the system configuration.
The following example configures a local disk for a service profile and commits the transaction:
UCS-A# scope org / UCS-A /org # scope service-profile ServInst90 UCS-A /org/service-profile # scope boot-definition UCS-A /org/service-profile # create local-disk-config UCS-A /org/service-profile/local-disk-config* # set mode raid-1-mirrored UCS-A /org/service-profile/local-disk-config* # create partition UCS-A /org/service-profile/local-disk-config/partition* # set size 1000000 UCS-A /org/service-profile/local-disk-config/partition* # set type ntfs UCS-A /org/service-profile/local-disk-config/partition* # commit-buffer UCS-A /org/service-profile/local-disk-config/partition #Configuring Serial over LAN for a Service Profile
Procedure
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 # scope service-profile profile-name Enters organization service profile mode for the specified service.
Step 3 UCS-A /org/service-profile # create sol-config Creates a serial over LAN configuration for the service profile and enters organization service profile SoL configuration mode.
Step 4 UCS-A /org/service-profile/sol-config # {disable | enable} Disables or enables the serial over LAN configuration for the service profile.
Step 5 UCS-A /org/service-profile/sol-config # set descr description (Optional) Provides a description for the serial over LAN configuration.
Step 6 UCS-A /org/service-profile/sol-config # set speed {115200 | 19200 | 38400 | 57600 | 9600} Specifies the serial baud rate.
Step 7 UCS-A /org/service-profile/sol-config # commit-buffer Commits the transaction to the system configuration.
The following example configures serial over LAN for the service profile named ServInst90 and commits the transaction:
UCS-A# scope org / UCS-A /org # scope service-profile ServInst90 UCS-A /org/service-profile # create sol-config UCS-A /org/service-profile/sol-config* # enable UCS-A /org/service-profile/sol-config* # set descr "Sets serial over LAN to 9600 baud." UCS-A /org/service-profile/sol-config* # set speed 9600 UCS-A /org/service-profile/sol-config* # commit-buffer UCS-A /org/service-profile/sol-config #Service Profile Boot Definition Configuration
Configuring a Boot Definition for a Service Profile
Procedure
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 # scope service-profile profile-name Enters organization service profile mode for the the specified service.
Step 3 UCS-A /org/service-profile # create boot-definition Creates a boot definition for the service profile and enters organization service profile boot definition mode.
Step 4 UCS-A /org/service-profile/boot-definition # set descr description (Optional) Provides a description for the boot definition.
Step 5 UCS-A /org/service-profile/boot-definition # set reboot-on-update {no | yes} (Optional) Specifies whether to automatically reboot all servers that use this boot definition after changes are made to the boot order. By default, the reboot on update option is disabled. Step 6 UCS-A /org/service-profile/boot-definition # commit-buffer Commits the transaction to the system configuration.
What to Do NextThe following example configures a boot definition for a service profile and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope service-profile ServInst90 UCS-A /org/service-profile* # create boot-definition UCS-A /org/service-profile/boot-definition* # set descr "This boot definition reboots on update." UCS-A /org/service-profile/boot-definition* # set reboot-on-update yes UCS-A /org/service-profile/boot-definition* # commit-buffer UCS-A /org/service-profile/boot-definition #
Configure one or more of the following boot options for the boot definition and set their boot order:
LAN Boot—Boots from a centralized provisioning server. It is frequently used to install operating systems on a server from that server.
If you choose the LAN Boot option, continue to Configuring a LAN Boot for a Service Profile Boot Definition.
Storage Boot— Boots from an operating system image on the SAN. You can specify a primary and a secondary SAN boot. If the primary boot fails, the server attempts to boot from the secondary.
We recommend that you use a SAN boot, because it offers the most service profile mobility within the system. If you boot from the SAN, when you move a service profile from one server to another, the new server boots from exactly the same operating system image. Therefore, the new server appears to be exactly the same server to the network.
If you choose the Storage Boot option, continue to Configuring a Storage Boot for a Service Profile Boot Definition.
Virtual Media Boot—Mimics the insertion of a physical CD into a server. It is typically used to manually install operating systems on a server.
If you choose the Virtual Media boot option, continue to Configuring a Virtual Media Boot for a Service Profile Boot Definition.
- Configuring a LAN Boot for a Service Profile Boot Definition
- Configuring a Storage Boot for a Service Profile Boot Definition
- Configuring a Virtual Media Boot for a Service Profile Boot Definition
Configuring a LAN Boot for a Service Profile Boot Definition
Procedure
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 # scope service-profile profile-name Enters organization service profile mode for the specified service profile.
Step 3 UCS-A /org/service-profile # scope boot-definition Enters organization service profile boot definition mode.
Step 4 UCS-A /org/service-profile/boot-definition # create lan Creates a LAN boot for the service profile boot definition and enters service profile boot definition LAN mode.
Step 5 UCS-A /org/service-profile/boot-definition/lan # set order {1 | 2 | 3 | 4} Specifies the boot order for the LAN boot.
Step 6 UCS-A /org/service-profile/boot-definition/lan # create path {primary | secondary} Creates a primary or secondary LAN boot path and enters service profile boot definition LAN path mode.
Step 7 UCS-A /org/service-profile/boot-definition/lan/path # set vnic vnic-name Specifies the vNIC to use for the LAN image path.
Step 8 UCS-A /org/service-profile/boot-definition/lan/path # commit-buffer Commits the transaction to the system configuration.
The following example enters the service profile named ServInst90, creates a LAN boot for the service profile boot definition, sets the boot order to 2, creates a primary path, and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope service-profile ServInst90 UCS-A /org/service-profile* # scope boot-definition UCS-A /org/service-profile/boot-definition* # create lan UCS-A /org/service-profile/boot-definition/lan* # set order 2 UCS-A /org/service-profile/boot-definition/lan* # create path primary UCS-A /org/service-profile/boot-definition/lan/path* # set vnic vnic3 UCS-A /org/service-profile/boot-definition/lan/path* # commit-buffer UCS-A /org/service-profile/boot-definition/lan/path #Configuring a Storage Boot for a Service Profile Boot Definition
Procedure
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 # scope service-profile profile-name Enters organization service profile mode for the specified service.
Step 3 UCS-A /org/service-profile # scope boot-definition Enters organization service profile boot definition mode.
Step 4 UCS-A /org/service-profile/boot-definition # create storage Creates a storage boot for the service profile boot definition and enters service profile boot definition storage mode.
Step 5 UCS-A /org/service-profile/boot-definition/storage # set order {1 | 2 | 3 | 4} Specifies the boot order for the storage boot.
Step 6 UCS-A /org/service-profile/boot-definition/storage # create {local | san-image {primary | secondary}} Creates a local storage boot or a SAN image boot. If a SAN image boot is created, it enters service profile boot definition storage SAN image mode.
Step 7 UCS-A /org/service-profile/boot-definition/storage/san-image # create path {primary | secondary} Creates a primary or secondary SAN image path and enters service profile boot definition storage SAN image path mode.
The use of the terms primary or secondary boot devices does not imply a boot order. The effective order of boot devices within the same device class is determined by PCIe bus scan order.
Step 8 UCS-A /org/service-profile/boot-definition/storage/san-image/path # set lun lun-num Specifies the LUN used for the SAN image path.
Step 9 UCS-A /org/service-profile/boot-definition/storage/san-image/path # set vhba vhba-name Specifies the vHBA used for the SAN image path.
Step 10 UCS-A /org/service-profile/boot-definition/storage/san-image/path # set wwn wwn-num Specifies the WWN used for the SAN image path.
Step 11 UCS-A /org/service-profile/boot-definition/storage/san-image/path # commit-buffer Commits the transaction to the system configuration.
The following example enters the service profile named ServInst90, creates a storage boot for the service profile boot definition, sets the boot order to 2, creates a primary path, and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope service-profile ServInst90 UCS-A /org/service-profile* # scope boot-definition UCS-A /org/service-profile/boot-definition* # create storage UCS-A /org/service-profile/boot-definition/storage* # create san-image primary UCS-A /org/service-profile/boot-definition/storage* # set order 2 UCS-A /org/service-profile/boot-definition/storage/san-image* # create path primary UCS-A /org/service-profile/boot-definition/storage/san-image/path* # set lun 27512 UCS-A /org/service-profile/boot-definition/storage/san-image/path* # set vhba vhba3 UCS-A /org/service-profile/boot-definition/storage/san-image/path* # set wwn 20:00:00:00:20:00:00:23 UCS-A /org/service-profile/boot-definition/storage/san-image/path* # commit-buffer UCS-A /org/service-profile/boot-definition/storage/san-image/path #Configuring a Virtual Media Boot for a Service Profile Boot Definition
Procedure
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 # scope service-profile profile-name Enters organization service profile mode for the specified service.
Step 3 UCS-A /org/service-profile # scope boot-definition Enters organization service profile boot definition mode.
Step 4 UCS-A /org/service-profile/boot-definition # create virtual-media {read-only | read-write} Creates a read-only or read-write virtual media boot for the service profile boot definition and enters service profile boot definition virtual media mode.
Step 5 UCS-A /org/service-profile/boot-definition/virtual-media # set order {1 | 2 | 3 | 4} Specifies the boot order for the virtual media boot.
Step 6 UCS-A /org/service-profile/boot-definition/virtual-media # commit-buffer Commits the transaction to the system configuration.
The following example enters the service profile named ServInst90, creates a virtual media boot with read-only privileges for the service profile boot definition, sets the boot order to 3, and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope service-profile ServInst90 UCS-A /org/service-profile* # scope boot-definition UCS-A /org/service-profile/boot-definition* # create virtual-media read-only UCS-A /org/service-profile/boot-definition/virtual-media* # set order 1 UCS-A /org/service-profile/boot-definition/virtual-media* # commit-buffer UCS-A /org/service-profile/boot-definition/virtual-media #Deleting a Boot Definition for a Service Profile
Procedure
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 # scope service-profile profile-name Enters organization service profile mode for the the specified service.
Step 3 UCS-A /org/service-profile # delete boot-definition Deletes the boot definition for the service profile.
Step 4 UCS-A /org/service-profile # commit-buffer Commits the transaction to the system configuration.
Associating a Service Profile with a Server or Server Pool
ProcedureFollow this procedure if you did not associate the service profile with a server or server pool when you created it, or to change the server or server pool with which a service profile is associated.
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 # scope service-profile profile-name Enters organization service profile mode for the specified service profile.
Step 3 UCS-A /org/service-profile # associate {server chassis-id | slot-id | server-pool pool-name qualifier} Associates the service profile with a single server, or to the specified server pool with the specified server pool policy qualifications.
Step 4 UCS-A /org/service-profile # commit-buffer Commits the transaction to the system configuration.
The following example associates the service profile named ServProf34 with the server in slot 4 of chassis 1 and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope service-profile ServProf34 UCS-A /org/service-profile* # associate server 1/4 UCS-A /org/service-profile* # commit-buffer UCS-A /org/service-profile #Disassociating a Service Profile from a Server or Server Pool
Procedure
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 # scope service-profile profile-name Enters organization service profile mode for the specified service profile.
Step 3 UCS-A /org/service-profile # disassociate Disassociates the service profile from a server.
Step 4 UCS-A /org/service-profile # commit-buffer Commits the transaction to the system configuration.
The following example disassociates the service profile named ServProf34 from the server to which it was associated and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope service-profile ServProf34 UCS-A /org/service-profile # disassociate UCS-A /org/service-profile* # commit-buffer UCS-A /org/service-profile #Resetting the UUID Assigned to a Service Profile from a Pool in a Service Profile Template
ProcedureIf you change the UUID suffix pool assigned to an updating service profile template, Cisco UCS Manager does not change the UUID assigned to a service profile created with that template. If you want Cisco UCS Manager to assign a UUID from the newly assigned pool to the service profile, and therefore to the associated server, you must reset the UUID. You can only reset the UUID assigned to a service profile and its associated server under the following circumstances:
The service profile was created from an updating service profile template and includes a UUID assigned from a UUID suffix pool.
The UUID suffix pool name is specified in the service profile. For example, the pool name is not empty.
The UUID value is not 0, and is therefore not derived from the server hardware.
Command or Action Purpose Step 1 UCS-A# scope org org-name Enters the command mode for the organization for which you want to reset the UUID. If the system does not include multi-tenancy, type / as the org-name to enter the root organization.
Step 2 UCS-A /org # scope service-profile profile-name Enters the service profile that requires the UUID for the associated server to be reset to a different UUID suffix pool.
Step 3 UCS-A /org/service-profile # set identity dynamic-uuid derived Specifies that the service profile will obtain a UUID dynamically from a pool.
Step 4 UCS-A /org/service-profile # commit-buffer Commits the transaction to the system configuration.
Resetting the MAC Address Assigned to a vNIC from a Pool in a Service Profile Template
ProcedureIf you change the MAC pool assigned to an updating service profile template, Cisco UCS Manager does not change the MAC address assigned to a service profile created with that template. If you want Cisco UCS Manager to assign a MAC address from the newly assigned pool to the service profile, and therefore to the associated server, you must reset the MAC address. You can only reset the MAC address assigned to a service profile and its associated server under the following circumstances:
The service profile was created from an updating service profile template and includes a MAC address assigned from a MAC pool.
The MAC pool name is specified in the service profile. For example, the pool name is not empty.
The MAC address value is not 0, and is therefore not derived from the server hardware.
Command or Action Purpose Step 1 UCS-A# scope org org-name Enters the command mode for the organization that contains the service profile for which you want to reset the MAC address. If the system does not include multi-tenancy, type / as the org-name to enter the root organization.
Step 2 UCS-A /org # scope service-profile profile-name Enters the command mode for the service profile that requires the MAC address of the associated server to be reset to a different MAC address.
Step 3 UCS-A /org/service-profile # scope vnic vnic-name Enters the command mode for the vNIC for which you want to reset the MAC address.
Step 4 UCS-A /org/service-profile/vnic # set identity dynamic-mac derived Specifies that the vNIC will obtain a MAC address dynamically from a pool.
Step 5 UCS-A /org/service-profile/vnic # commit-buffer Commits the transaction to the system configuration.
This example resets the MAC address of a vNIC in a service profile:
UCS-A# scope org / UCS-A /org # scope service-profile ServInst90 UCS-A /org/service-profile # scope vnic dynamic-prot-001 UCS-A /org/service-profile/vnic # set identity dynamic-mac derived UCS-A /org/service-profile/vnic* # commit-buffer UCS-A /org/service-profile/vnic #Resetting the WWPN Assigned to a vHBA from a Pool in a Service Profile Template
ProcedureIf you change the WWPN pool assigned to an updating service profile template, Cisco UCS Manager does not change the WWPN assigned to a service profile created with that template. If you want Cisco UCS Manager to assign a WWPN from the newly assigned pool to the service profile, and therefore to the associated server, you must reset the WWPN. You can only reset the WWPN assigned to a service profile and its associated server under the following circumstances:
Command or Action Purpose Step 1 UCS-A# scope org org-name Enters the command mode for the organization that contains the service profile for which you want to reset the WWPN. If the system does not include multi-tenancy, type / as the org-name to enter the root organization.
Step 2 UCS-A /org # scope service-profile profile-name Enters the service profile of the vHBA for which you want to reset the WWPN.
Step 3 UCS-A /org/service-profile # scope vhba vhba-name Enters the command mode for vHBA for which you want to reset the WWPN.
Step 4 UCS-A /org/service-profile/vhba # set identity dynamic-wwpn derived Specifies that the vHBA will obtain a WWPN dynamically from a pool.
Step 5 UCS-A /org/service-profile/vhba # commit-buffer Commits the transaction to the system configuration.
This example resets the WWPN of a vHBA in a service profile:
UCS-A# scope org / UCS-A /org # scope service-profile ServInst90 UCS-A /org/service-profile # scope vhba vhba3 UCS-A /org/service-profile/vhba # set identity dynamic-wwpn derived UCS-A /org/service-profile/vhba* # commit-buffer UCS-A /org/service-profile/vhba #
