Chassis Profiles and Templates

About Cisco UCS Storage Servers

A Cisco UCS storage server is a dense storage rack server with dual server nodes, optimized for large datasets used in environments such as big data, cloud, object storage, and content deliver.

A Cisco UCS storage server is designed to operate in a standalone environment and as part of the Cisco Unified Computing System with Cisco UCS Manager integration. The following features are available:

  • System IO Controllers (SIOC).

  • Support of up to two server modules

  • Capability to operate in a standalone mode.

  • Chassis level functionality in the standalone mode—Shared components such as storage adapters, fans and power supply units are configured at the chassis level.

  • Data Center Ethernet connectivity to a server host through a shared dual virtual interface card (VIC).

  • Individual hard disk drives (HDD) can be assigned to either server in the dedicated or shared mode.

    In addition, one of the server slots in the Cisco UCS storage server can be utilized by a storage expansion module for an additional four 3.5" drivers. The server modules can also accommodate two solid state drives (SDD) for internal storage dedicated to that module. The chassis supports Serial Attached SCSI (SAS) expanders that can be configured to assign the 3.5" drives to individual server modules.

    For more information, see the Cisco UCS S3260 Storage Server Installation and Service Guide.

Chassis Profiles

A chassis profile defines the storage, firmware and maintenance characteristics of a chassis. When a chassis profile is associated to a chassis, Cisco UCS Central automatically configures the chassis to match the configuration in the chassis profile.

A chassis profile includes four types of information:

  • Chassis definitions—Defines the specific chassis to which the profile is assigned.

  • Maintenance policy—Includes the maintenance policy to be applied to the profile.

  • Firmware specification—Defines the chassis firmware package that can be applied to a chassis through this profile.

  • Disk zoning policy—Includes the zoning policy to be applied to the storage disks.

Guidelines and Recommendations for Chassis Profiles

In addition to any guidelines or recommendations that are specific to the policies included in chassis profiles and chassis profile templates, such as the disk zoning policy, adherence to the following guidelines that impact the ability to associate a chassis profile with a chassis are recommended:

  • Each chassis can be associated with only one chassis profile. Similarly, each chassis profile can be associated with only one chassis at a time.

  • Chassis profiles are currently supported.

  • C bundles earlier than Cisco UCS Manager Release 3.1(2) are not supported on the Cisco UCS S3260 Storage Server.

Creating a Chassis Profile

Procedure

  Command or Action Purpose

Step 1

UCSC(resource-mgr)# scope org org-name

Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name .

Step 2

UCSC(resource-mgr) /org # create chassis-profile profile-name instance

Creates the specified chassis profile instance and enters organization chassis profile mode.

Enter a unique profile-name to identify this chassis profile.

This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object is saved.

Step 3

(Optional) UCSC(resource-mgr) /org/chassis-profile* # set descr description

(Optional)

Provides a description for the chassis 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 4

(Optional) UCSC(resource-mgr) /org/chassis-profile* # set chassis-fw-policy-name chassis-firmware-policy-name

(Optional)

Associates the specified chassis firmware policy with the chassis profile.

Step 5

(Optional) UCSC(resource-mgr) /org/chassis-profile* # set chassis-profile-maint-policy policy-name

(Optional)

Associates the specified chassis maintenance policy with the chassis profile.

Step 6

(Optional) UCSC(resource-mgr) /org/chassis-profile* # set user-label label-name

(Optional)

Specifies the user label associated with the chassis profile.

Step 7

(Optional) UCSC(resource-mgr) /org/chassis-profile* # set src-templ-name source-chassis-profile-template-name

(Optional)

Binds the specified chassis profile template with the chassis profile.

Step 8

(Optional) UCSC(resource-mgr) /org/chassis-profile* # set disk-zoning-policy disk-zoning-policy-name

(Optional)

Associates the specified disk zoning policy with the chassis profile.

Step 9

UCSC(resource-mgr) /org/chassis-profile* # commit-buffer

Commits the transaction to the system configuration.

Example

The following example shows how to create a chassis profile instance and commit the transaction: 

UCSC(resource-mgr)# scope org /
UCSC(resource-mgr) /org* # create chassis-profile- ChassisProfile1 instance
UCSC(resource-mgr) /org/chassis-profile* # set  descr "This is a chassis profile example."
UCSC(resource-mgr) /org/chassis-profile* # set chassis-profile-maint-policy chassismaintpol4
UCSC(resource-mgr) /org/chassis-profile* # set user-label mycplabel
UCSC(resource-mgr) /org/chassis-profile* # set chassis-fw-policy-name cfp1
UCSC(resource-mgr) /org/chassis-profile* # set src-templ-name chassispt1
UCSC(resource-mgr) /org/chassis-profile* # set disk-zoning-policy dzp1
UCSC(resource-mgr) /org/chassis-profile* # commit-buffer
UCSC(resource-mgr) /org/chassis-profile #

What to do next

Associate the chassis profile with a S3260 chassis.

Renaming a Chassis Profile

When you rename a chassis profile, the following occurs:

  • Event logs and audit logs that reference the previous name for the chassis profile are retained under that name.

  • A new audit record is created to log the rename operation.

  • All records of faults against the chassis profile under its previous name are transferred to the new chassis profile name.


Note

You cannot rename a chassis profile with pending changes.

Procedure

  Command or Action Purpose

Step 1

UCSC(resource-mgr)# scope org org-name

Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name .

Step 2

UCSC(resource-mgr) /org # scope chassis-profile profile-name

Enters organization chassis profile mode for the specified chassis profile.

Step 3

UCSC(resource-mgr) /org/chassis-profile # rename-to new-profile-name

Renames the specified chassis profile.

This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object is saved.

When you enter this command, you are warned that this is a standalone operation and that you may lose all uncommitted changes in this CLI session. Type yes to confirm that you want to continue.

Example

This example shows how to change the name of a chassis profile from CP5 to CP10 and commits the transaction: 

UCSC(resource-mgr)# scope org /
UCSC(resource-mgr) /org # scope chassis-profile CP5
UCSC(resource-mgr) /org/chassis-profile # rename-to CP10
Rename is a standalone operation. You may lose any uncommitted changes in this CLI session.
Do you want to continue? (yes/no): yes
The managed object in the current mode no longer exists. Changing to mode: /org
UCSC(resource-mgr) /org #

Deleting a Chassis Profile

This procedure explains how to delete a chassis profile.

Procedure

  Command or Action Purpose

Step 1

UCSC(resource-mgr)# scope org org-name

Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name .

Step 2

UCSC(resource-mgr) /org # delete chassis-profile profile-name

Deletes the specified chassis profile.

Step 3

UCSC(resource-mgr) /org* # commit-buffer

Commits the transaction to the system configuration.

Example

This example shows how to delete a chassis profile ChasInst90 and commit the transaction: 

UCSC(resource-mgr)# scope org /
UCSC(resource-mgr) /org delete chassis-profile ChasInst90
UCSC(resource-mgr) /org* # commit-buffer
UCSC(resource-mgr) /org #

Associating a Chassis Profile with a Chassis

Follow this procedure if you did not associate the chassis profile with a chassis when you created it, or to change the chassis with which a chassis profile is associated.

Procedure

  Command or Action Purpose

Step 1

UCSC(resource-mgr)# scope org org-name

Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name .

Step 2

UCSC(resource-mgr) /org # scope chassis-profile profile-name

Enters organization chassis profile mode for the specified chassis profile.

Step 3

UCSC(resource-mgr) /org/chassis-profile # associate chassis chassis-id ucs-domain domain-number [restrictmigration]

Associates the chassis profile with a single chassis.

Adding the optional restrictmigration keyword prevents the chassis profile from being migrated to another chassis.

Step 4

UCSC(resource-mgr) /org/chassis-profile* # commit-buffer

Commits the transaction to the system configuration.

Example

The following example associates the chassis profile named ChassisProf1 with chassis 1, and commits the transaction: 

UCSC(resource-mgr)# scope org /
UCSC(resource-mgr) /org* # scope chassis-profile ChassisProf1
UCSC(resource-mgr) /org/chassis-profile # associate chassis 1 ucs-domain 1003
UCSC(resource-mgr) /org/chassis-profile* # commit-buffer
UCSC(resource-mgr) /org/chassis-profile #

Disassociating a Chassis Profile from a Chassis

This procedure covers disassociating a chassis profile from a chassis.


Note

When a chassis is disassociated from a chassis profile, effects of disk zoning policy will be still be persistent in the chassis.

Procedure

  Command or Action Purpose

Step 1

UCSC(resource-mgr)# scope org org-name

Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name.

Step 2

UCSC(resource-mgr) /org # scope chassis-profile profile-name

Enters organization chassis profile mode for the specified chassis profile.

Step 3

UCSC(resource-mgr) /org/chassis-profile # disassociate

Disassociates the chassis profile from the chassis.

Step 4

UCSC(resource-mgr) /org/chassis-profile* # commit-buffer

Commits the transaction to the system configuration.

Example

The following example disassociates the chassis profile named ChassisProf1 from the chassis to which it was associated and commits the transaction: 

UCSC(resource-mgr)# scope org /
UCSC(resource-mgr) /org* # scope chassis-profile ChassisProf1
UCSC(resource-mgr) /org/chassis-profile # disassociate
UCSC(resource-mgr) /org/chassis-profile* # commit-buffer
UCSC(resource-mgr) /org/chassis-profile #

Creating a Chassis Profile Template

Procedure

  Command or Action Purpose

Step 1

UCSC(resource-mgr)# scope org org-name

Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name .

Step 2

UCSC(resource-mgr) /org # create chassis-profile profile-name {initial-template | updating-template}

Creates the specified chassis profile template and enters organization chassis profile mode.

Enter a unique profile-name to identify this chassis profile template.

This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object is saved.

Chassis profile template types are:

  • initial-template —Instances will not automatically update if this template is updated.

  • updating-template —Instances will automatically update if this template is updated.

Step 3

(Optional) UCSC(resource-mgr) /org/chassis-profile* # set descr description

(Optional)

Provides a description for the chassis profile template.

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 4

UCSC(resource-mgr) /org/chassis-profile* # set chassis-fw-policy-name chassis-firmware-policy-name

Associates the specified chassis firmware policy with the chassis profile template.

Step 5

UCSC(resource-mgr) /org/chassis-profile* # set chassis-profile-maint-policy policy-name

Associates the specified chassis maintenance policy with the chassis profile template.

Step 6

UCSC(resource-mgr) /org/chassis-profile* # set user-label label-name

Specifies the user label associated with the chassis profile template.

Step 7

UCSC(resource-mgr) /org/chassis-profile* # set src-templ-name source-chassis-profile-template-name

Binds the specified chassis profile template with the chassis profile.

Step 8

UCSC(resource-mgr) /org/chassis-profile* # set disk-zoning-policy disk-zoning-policy-name

Associates the specified disk zoning policy with the chassis profile template.

Step 9

UCSC(resource-mgr) /org/chassis-profile* # commit-buffer

Commits the transaction to the system configuration.

Example

The following example shows how to create a chassis profile template and commit the transaction: 

UCSC(resource-mgr)# scope org /
UCSC(resource-mgr) /org* # create chassis-profile ChassisProfile1 instance
UCSC(resource-mgr) /org/chassis-profile* # set  descr "This is a chassis profile template example."
UCSC(resource-mgr) /org/chassis-profile* # set chassis-profile-maint-policy chassismaintpol2
UCSC(resource-mgr) /org/chassis-profile* # set user-label mycptlabel
UCSC(resource-mgr) /org/chassis-profile* # set chassis-fw-policy-name cptf1
UCSC(resource-mgr) /org/chassis-profile* # set src-templ-name chassispt1
UCSC(resource-mgr) /org/chassis-profile* # set disk-zoning-policy dzp1
UCSC(resource-mgr) /org/chassis-profile* # commit-buffer
UCSC(resource-mgr) /org/chassis-profile #

What to do next

Create a chassis profile instance from the chassis profile template.

Creating a Chassis Profile Instance from a Chassis Profile Template

Before you begin

Verify that there is a chassis profile template from which to create a chassis profile instance.

Procedure

  Command or Action Purpose

Step 1

UCSC# scope org org-name

Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name .

Step 2

UCSC /org # create chassis-profile profile-name instance

Creates the specified chassis profile instance and enters organization chassis profile mode.

Enter a unique profile-name to identify this chassis profile.

This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object is saved.

Step 3

UCSC /org/chassis-profile* # set src-templ-name profile-name

Specifies the source chassis profile template to apply to the chassis profile instance. All configuration settings from the chassis profile template will be applied to the chassis profile instance.

Step 4

UCSC /org/chassis-profile* # commit-buffer

Commits the transaction to the system configuration.

Example

The following example creates a chassis profile instance named ChassisProf02, applies the chassis profile template named ChassisProfTemp2, and commits the transaction: 

UCSC# scope org /
UCSC /org* # create chassis-profile ChassisProf02 instance
UCSC /org/chassis-profile* # set src-templ-name ChassisProfTemp2
UCSC /org/chassis-profile* # commit-buffer
UCSC /org/chassis-profile #

What to do next

Associate the chassis profile to a chassis.

Binding a Chassis Profile to a Chassis Profile Template

You can bind a chassis profile to a chassis profile template. When you bind the chassis profile to a template, Cisco UCS Central configures the chassis profile with the values defined in the chassis profile template. If the existing chassis profile configuration does not match the template, Cisco UCS Central reconfigures the chassis profile. You can only change the configuration of a bound chassis profile through the associated template.

Procedure

  Command or Action Purpose

Step 1

UCSC(resource-mgr)# scope org org-name

Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name .

Step 2

UCSC(resource-mgr) /org # scope chassis-profile profile-name

Enters organization chassis profile mode for the specified chassis profile.

Step 3

UCSC(resource-mgr) /org/chassis-profile # set src-templ-name chassis-profile-template-name

Binds the chassis profile to the specified chassis profile template.

Step 4

UCSC(resource-mgr) /org/chassis-profile* # commit-buffer

Commits the transaction to the system configuration.

Example

The following example binds the chassis profile named ChassisProf1 to ChassisProfileTemplate1 and commits the transaction: 

UCSC(resource-mgr)# scope org
UCSC(resource-mgr) /org # scope chassis-profile ChassisProf1
UCSC(resource-mgr) /org/chassis-profile # set src-templ-name ChassisProfileTemplate1
UCSC(resource-mgr) /org/chassis-profile* # commit-buffer
UCSC(resource-mgr) /org/chassis-profile #

Unbinding a Chassis Profile from a Chassis Profile Template

To unbind a chassis profile from a chassis profile template, bind the chassis profile to an empty value (quotes without space).

Procedure

  Command or Action Purpose

Step 1

UCSC(resource-mgr)# scope org org-name

Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name .

Step 2

UCSC(resource-mgr) /org # scope chassis-profile profile-name

Enters organization chassis profile mode for the specified chassis profile.

Step 3

UCSC(resource-mgr) /org/chassis-profile # set src-templ-name ""

Unbinds the chassis profile from the chassis profile template.

Step 4

UCSC(resource-mgr) /org/chassis-profile* # commit-buffer

Commits the transaction to the system configuration.

Example

The following example unbinds the chassis profile named ChassisProf1 and commits the transaction: 

UCSC(resource-mgr)# scope org
UCSC(resource-mgr) /org # scope chassis-profile ChassisProf1
UCSC(resource-mgr) /org/chassis-profile # set src-templ-name ""
UCSC(resource-mgr) /org/chassis-profile* # commit-buffer
UCSC(resource-mgr) /org/chassis-profile #

Assigning a Policy to a Chassis Profile

Cisco UCS Central lets you assign a policy to a chassis profile.

Procedure

  Command or Action Purpose

Step 1

UCSC(resource-mgr) # scope org

Enters the organization root.

Step 2

UCSC(resource-mgr) /system # create chassis-profile chassis-profile-name

Creates a chassis profile using a unique name.

Step 3

UCSC(resource-mgr) /org/chassis-profile* # commit buffer

Commits the transaction to the system configuration.

Step 4

UCSC(resource-mgr) /org/chassis-profile* # set chassis-fw-policy policy-name

Sets the policy name to the chassis.

Step 5

UCSC(resource-mgr) /org/chassis-profile* # commit buffer

Commits the transaction to the system.

Step 6

UCSC(resource-mgr) /org/chassis-profile* # show detail

Displays the details of the assigning process.

Example

The following example shows how Cisco UCS Central assigns a policy to a chassis profile: 

UCSC(resource-mgr)# scope org
UCSC(resource-mgr) /org # create chassis-profile CP3
UCSC(resource-mgr) /org/chassis-profile* # com
UCSC(resource-mgr) /org/chassis-profile # set 
  chassis-fw-policy-name        Chassis Firmware Policy 
  chassis-profile-maint-policy  Maintenance Policy 
  compute-conn-policy           Compute Conn Policy 
  descr                         Description 
  disk-zoning-policy            Disk Zoning Policy 
  src-templ-name                Source Template 
  user-label                    User Label 

UCSC(resource-mgr) /org/chassis-profile # set cha
chassis-fw-policy-name        chassis-profile-maint-policy  
UCSC(resource-mgr) /org/chassis-profile # set chassis-fw-policy-name A1
UCSC(resource-mgr) /org/chassis-profile* # com
UCSC(resource-mgr) /org/chassis-profile # show detail 

Chassis Profile:
    Chassis Profile Name: CP3
    Type: Instance
    Chassis Dn:
    Chassis Config Issues: N/A
    Storage Config Issues: N/A
    User Label:
    Description:
    Assign State: Unassigned
    Assoc State: Unassociated
    Chassis Firmware Policy: A1
    Oper Chassis Fw Policy Name: org-root/fw-chassis-pack-global-default
    Disk Zoning Policy: global-default
    Oper Disk Zoning Policy: org-root/disk-zoning-policy-global-default
    Resolve Remote: Yes
    Source Template:
    Oper Src Templ Name:
    Maintenance Policy: global-default
    Oper Maint Policy Name: org-root/chassis-profile-maint-global-default
    Compute Conn Policy: global-default
    Equipment Oper Compute Conn Policy: org-root/compute-conn-policy-global-default
    Current Task: Throttle wait(FSM-STAGE:sam:dme:EquipmentChassisProfileConfigure:ThrottleWait)

Creating a Chassis Profile Maintenance Policy

Procedure

  Command or Action Purpose

Step 1

UCSC(policy-mgr)# scope org org-name

Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name .

Step 2

UCSC(policy-mgr) /org # create chassis-profile-maint-policy policy-name

Creates the specified maintenance policy and enters maintenance policy mode.

Step 3

UCSC(policy-mgr) /org/chassis-profile-maint-policy* # set reboot-policy user-ack

When a policy is associated with a chassis, the chassis needs to be re-acknowledged to complete the association. The user must explicitly acknowledge the changes by using the apply pending-changes command before changes are applied.

Step 4

(Optional) UCSC(policy-mgr) /org/chassis-profile-maint-policy* # set descr description

(Optional)

A description of the policy. Cisco recommends including information about where and when to use the policy.

Step 5

UCSC(policy-mgr) /org/maint-policy #* commit-buffer

Commits the transaction to the system configuration.

Example

The following example creates a maintenance policy called maintenance, and commits the transaction: 

UCSC(policy-mgr)# scope org /
UCSC(policy-mgr) /org # create chassis-profile-maint-policy maintenance
UCSC(policy-mgr) /org/chassis-profile-maint-policy* # set reboot-policy user-ack
UCSC(policy-mgr) /org/chassis-profile-maint-policy* # commit-buffer
UCSC(policy-mgr) /org/maint-policy #

Configuring the Maintenance Policy for a Chassis Profile/Chassis Profile Template

Procedure

  Command or Action Purpose

Step 1

UCSC(resource-mgr)# scope org org-name

Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name .

Step 2

UCSC(resource-mgr) /org # scope chassis-profile profile-name|template-name

Enters organization chassis profile/chassis profile template mode for the specified chassis profile//chassis profile template.

Step 3

UCSC(resource-mgr) /org/chassis-profile # set chassis-profile-maint-policy maintenance-policy-name

Associates the specified maintenance policy with the chassis profile//chassis profile template.

Use an existing maintenance policy name or enter a new policy.

Step 4

UCSC(resource-mgr) /org/chassis-profile* # commit-buffer

Commits the transaction to the system configuration.

Example

The following example shows how to associate a maintenance policy with a chassis profile and commit the transaction: 

UCSC(resource-mgr)# scope org
UCSC(resource-mgr) /org # scope chassis-profile ChassisProfile1
UCSC(resource-mgr) /org/chassis-profile # set chassis-profile-maint-policy default
UCSC(resource-mgr) /org/chassis-profile* # commit-buffer
UCSC(resource-mgr) /org/chassis-profile #

Disk Zoning Policies

Disk zoning policies allow you to manage the disk on your chassis servers when associated in a chassis profile. After a disk zoning policy has been created, you can view the disk zoning policy page to review what is included in the policy.

Depending on the storage controller, the disk types that are supported for your disk zoning policy may vary:

Storage Controller

Supported Disk Types

UCSC-C3X60-R1GB

Supports unassigned, dedicated, and chassis spare disks.

UCS-C3K-M4RAID

Supports unassigned, dedicated, and chassis spare disks on the UCSC-C3K-M4SRB server only.

UCS-C3X60-HBA

Supports shared disks for data storage operations only. LUNs cannot be created on the shared disks.

Creating a Disk Zoning Policy

Procedure

  Command or Action Purpose

Step 1

UCSC# connect policy-mgr

Enters policy manager mode.

Step 2

UCSC(policy-mgr) # scope org org-name

Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name .

Step 3

UCSC(policy-mgr) /org # create disk-zoning-policydiskzoning policy-name

Creates a disk zoning policy name with the specified disk zoning policy name.

Step 4

UCSC(policy-mgr) /org/disk-zoning-policy* # commit-buffer

Commits the transaction to the system.

Example

The following example shows how to create the dzp1 disk zoning policy: 



 UCSC(policy-mgr)# scope org
 UCSC(policy-mgr) /org # create disk-zoning-policy dzp1
 UCSC(policy-mgr) /org/disk-zoning-policy*# commit-buffer 
 UCSC(policy-mgr) /org/disk-zoning-policy#