Tip Means the following information will help you solve a problem . The tips information might not be troubleshooting or even an action, but could be useful information, similar to a Timesaver.

Timesaver Means the described action saves time . You can save time by performing the action described in the paragraph.

Caution Means reader be careful . In this situation, you might perform an action that could result in equipment damage or loss of data.

Warning IMPORTANT SAFETY INSTRUCTIONS

This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device.

SAVE THESE INSTRUCTIONS xiv

Cisco UCS Manager Storage Management Guide, Release 4.2

Preface

Related Cisco UCS Documentation

Documentation Roadmaps

For a complete list of all B-Series documentation, see the Cisco UCS B-Series Servers Documentation Roadmap available at the following URL: https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/overview/ guide/UCS_roadmap.html

For a complete list of all C-Series documentation, see the Cisco UCS C-Series Servers Documentation Roadmap available at the following URL: https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/overview/ guide/ucs_rack_roadmap.html

For information on supported firmware versions and supported UCS Manager versions for the rack servers that are integrated with the UCS Manager for management, refer to Release Bundle Contents for Cisco UCS

Software .

Other Documentation Resources

Follow Cisco UCS Docs on Twitter to receive document update notifications.

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to [email protected]

. We appreciate your feedback.

Cisco UCS Manager Storage Management Guide, Release 4.2

Documentation Feedback

Preface xvi

Cisco UCS Manager Storage Management Guide, Release 4.2

C H A P T E R

New and Changed Information

•

New and Changed Information, on page 1

New and Changed Information

This section provides information on new features and changed behavior in Cisco UCS Manager, Release

4.2.1.

Table 1: New Features and Changed Behavior in Cisco UCS Manager, Release 4.2(1i)

Feature

Cisco UCS M6 Controllers

Description

Cisco UCS Manager now supports

Cisco UCS C245 M6 Server with:

• UCS C245 M6SX

• UCS-M2-HWRAID

Where Documented

•

Cisco Boot Optimized M.2

RAID Controller, on page 118

•

Controller Constraints and

Limitations, on page 129

Table 2: New Features and Changed Behavior in Cisco UCS Manager, Release 4.2(1f)

Feature Description Where Documented

Disable Local Storage RAID level Added Disable Local Storage to support PCH SATA Controller

(AHCI mode).

Creating a Storage Profile PCH

Controller Definition, on page 147

and

Modifying a Service Profile

PCH Controller Definition, on page

151

Table 3: New Features and Changed Behavior in Cisco UCS Manager, Release 4.2(1d)

Feature

Cisco UCS M6 Servers

Description Where Documented

Cisco UCS Manager now supports

Cisco UCS C220 M6 and UCS

C240 M6 C-series servers.

Cisco Boot Optimized M.2 RAID

Controller, on page 118

Cisco UCS Manager Storage Management Guide, Release 4.2

New and Changed Information

Feature

Cisco UCS M6 controllers

Description Where Documented

Cisco UCS Manager now supports

Cisco UCSC-C220-M6,

UCSC-C240-M6, and

UCSB-MRAID12G-M6 controllers.

Controller Constraints and

Limitations, on page 129

Autoconfiguration Mode for Aero

Storage Controllers

Cisco UCS Manager now supports creating storage profiles to enable automatic configuration of newly inserted disks on Cisco UCS

C220M6/C240M6 C-series M6 servers with Aero PCIe

SAS316-port storage controllers.

Autoconfiguration Mode for Aero

Storage Controllers, on page 143

Security Protocol and Data Model

(SPDM)

SPDM can now be used for authentication with the storage controller. It can be used either natively or by uploading outside security certificates.

SPDM Authentication, on page 145

Cisco UCS Manager Storage Management Guide, Release 4.2

C H A P T E R

Overview

•

Overview, on page 3

•

Cisco UCS Manager User Documentation, on page 3

•

Storage Options, on page 4

•

Storage Design Considerations, on page 6

•

Storage Configuration Sequence, on page 6

•

Storage Protocols, on page 7

•

The UCS Manager SAN Tab, on page 7

Overview

This guide describes how to configure the following storage management tasks:

• Ports and Port Channels

• Named VSANs

• SAN Pin Groups

• SAN Uplinks

• Pools

• FC Identity Assignment

• Storage-Related Policies

• Storage Profiles

• FlexFlash SD Card Support

• Direct Attached Storage

• Storage Inventory

Cisco UCS Manager User Documentation

Cisco UCS Manager offers you a new set of smaller, use-case based documentation described in the following table:

Cisco UCS Manager Storage Management Guide, Release 4.2

Overview

Storage Options

Guide

Cisco UCS Manager Getting Started Guide

Cisco UCS Manager Administration Guide

Description

Discusses Cisco UCS architecture and Day 0 operations, including Cisco UCS Manager initial configuration and configuration best practices.

Discusses password management, role-based access configuration, remote authentication, communication services, CIMC session management, organizations, backup and restore, scheduling options, BIOS tokens, and deferred deployments.

Cisco UCS Manager Infrastructure Management Guide Discusses physical and virtual infrastructure components used and managed by Cisco UCS

Manager.

Cisco UCS Manager Firmware Management Guide Discusses downloading and managing firmware, upgrading through Auto Install, upgrading through service profiles, directly upgrading at endpoints using firmware auto sync, managing the capability catalog, deployment scenarios, and troubleshooting.

Cisco UCS Manager Server Management Guide

Cisco UCS Manager Storage Management Guide

Discusses the new licenses, registering Cisco UCS domain with Cisco UCS Central, power capping, server boot, server profiles, and server-related policies.

Discusses all aspects of storage management, such as SAN and VSAN in Cisco UCS Manager.

Cisco UCS Manager Network Management Guide

Cisco UCS Manager System Monitoring Guide

Cisco UCS S3260 Server Integration with Cisco UCS

Manager

Discusses all aspects of network management, such as LAN and VLAN connectivity in Cisco UCS

Manager.

Discusses all aspects of system and health monitoring, including system statistics in Cisco

UCS Manager.

Discusses all aspects of management of UCS

S-Series servers that are managed through Cisco

UCS Manager.

Storage Options

The following are the UCS Manager storage options and the benefits of each.

Cisco UCS Manager Storage Management Guide, Release 4.2

Overview

Figure 1: Cisco UCS Manager Storage Options

Storage Options

• Direct Attached Storage (DAS) —This is the storage available inside a server and is directly connected to the system through the motherboard within a parallel SCSI implementation. DAS is commonly described as captive storage. Devices in a captive storage topology do not have direct access to the storage network and do not support efficient sharing of storage. To access data with DAS, a user must go through a front-end network. DAS devices provide little or no mobility to other servers and little scalability.

DAS devices limit file sharing and can be complex to implement and manage. For example, to support data backups, DAS devices require resources on the host and spare disk systems that other systems cannot use. The cost and performance of this storage depends upon the disks and RAID controller cards inside the servers. DAS is less expensive and is simple to configure; however, it lacks the scalability, performance, and advanced features provided by high-end storage.

• Network Attached Storage (NAS) —This storage is usually an appliance providing file system access.

This storage could be as simple as an Network File System (NFS) or Common Internet File System

(CIFS) share available to the servers. Typical NAS devices are cost-effective devices with not very high performance but have very high capacity with some redundancy for reliability. NAS is usually moderately expensive, simple to configure, and provides some advanced features; however, it also lacks scalability, performance, and advanced features provided by SAN.

• Storage Area Network (SAN) —A SAN is a specialized, high-speed network that attaches servers and storage devices. A SAN allows an any-to-any connection across the network by using interconnect elements, such as switches and directors. It eliminates the traditional dedicated connection between a server and storage, and the concept that the server effectively owns and manages the storage devices. It also eliminates any restriction to the amount of data that a server can access, currently limited by the number of storage devices that are attached to the individual server. Instead, a SAN introduces the flexibility of networking to enable one server or many heterogeneous servers to share a common storage utility. A network might include many storage devices, including disk, tape, and optical storage.

Additionally, the storage utility might be located far from the servers that it uses. This type of storage

Cisco UCS Manager Storage Management Guide, Release 4.2

Overview

Storage Design Considerations provides maximum reliability, expandability, and performance. The cost of SAN is also very high compared to other storage options.

SAN is the most resilient, highly scalable, and high performance storage; however, it is also the most expensive and complex to manage.

Storage Design Considerations

UCS storage physical connectivity has a slightly different design consideration as compared to LAN physical connectivity. The following are some design considerations for SAN connectivity:

• Northbound storage physical connectivity does not support virtual port channels (vPCs) like LAN connectivity.

• Port channels or trunking is possible to combine multiple storage uplink ports that provide physical link redundancy.

• Redundancy of storage resources is handled by the storage itself and varies from vendor to vendor.

• Connect storage through northbound Cisco storage devices, such as Nexus or MDS Fabric Switches.

• It is possible to connect storage directly to UCS Fabric Interconnects, which is recommended for small implementations because of the fabric interconnect physical ports consumption and increased processing requirements.

• Software configuration including VSANs and zoning is required for providing access to storage resources.

Storage Configuration Sequence

Follow the suggested sequence to configure a storage network:

Configure and enable server ports, uplink ports, and FC ports.

Create a management IP address pool (typically on the same subnet as the UCS Manager Admin IP address).

Create an UUID Pool, MAC Pool, WWNN Pool, WWPN Pool (or populate the corresponding "default" pools). Embed domain ID's. Use Fabric-specific Pools for MAC and WWPN (for example, Fabric-A,

Fabric-B).

For SAN boot, create a unique "Boot Policy" for each storage array boot target.

Create VNIC templates (for example, eth0-A, eth1-B) that both draw from the above MAC Pool, and are associated with Fabric-A and Fabric-B respectively.

Create VHBA templates (for example, fc0-A, fc1-B) that both draw from the above WWPN Pool, and are associated with Fabric-A and Fabric-B respectively.

Create service profile templates that draw from all earlier established pools, policies and templates, as appropriate.

Instantiate the service profile from the template and associate the service profile to a given blade, or set the service profile template to associate with a particular server pool.

Cisco UCS Manager Storage Management Guide, Release 4.2

Overview

Storage Protocols

Fiber Channel, iSCSI, and Fiber Channel over Ethernet are protocols for SAN connectivity.

• iSCSI —An industry standard protocol for attaching various I/O peripherals such as printers, scanners, tape drives, and storage devices. The most common SCSI devices are disks and tape libraries.

SCSI is the core protocol to connect raw hard disk storage with the servers. To control remote storage with the SCSI protocol, different technologies are used as wrappers to encapsulate commands, such as

FC and iSCSI.

Fiber Channel protocol provides the infrastructure to encapsulate the SCSI traffic and provided connectivity between computers and storage. FC operates at speeds of 2, 4, 8, and 16 Gbps.

• Fiber Channel (FC) consists of the following:

• Hard disk arrays that provide raw storage capacity.

• Storage processors to manage hard disks and provide storage LUNs and masking for the servers.

• Fiber Channel Switches (also known as Fabric) that provide connectivity between storage processors and server HBAs.

• Fiber Channel Host Bus Adapters: They are installed in the computer and provide connectivity to the SAN.

Fiber Channel identifies infrastructure components with World Wide Numbers (WWN) . WWNs are

64-bit addresses which uniquely identify the FC devices. Like MAC addresses, it has bits assigned to vendors to identify their devices. Each end device (like an HBA port) is given a World Wide Port Number

(WWPN) and each connectivity device (like a Fabric switch) is given a World Wide Node Number

(WWNN).

A Fiber Chanel HBA used for connecting to a SAN is known as an initiator, and Fiber Channel SAN providing disks as LUNs is known as a target. The Fiber Channel protocol is different from Ethernet or

TCP/IP protocols.

• Fiber Channel over Ethernet (FCoE) transport replaces the Fibre Channel cabling with 10 Gigabit

Ethernet cables and provides lossless delivery over unified I/O. Ethernet is widely used in networking.

With some advancement such as Data Center Ethernet (DCE) and Priority Flow Control (PFC) in Ethernet to make it more reliable for the datacenter, Fiber Channel is now also implemented on top of Ethernet.

This implementation is known as FCoE.

The UCS Manager SAN Tab

From the SAN tab, you the UCS administrator can create, modify, and delete configuration elements related to SANs (FC, iSCSI) or direct attached FC/FCoE, NAS appliances, and communications.

The major nodes in this tab are the following:

• SAN Cloud —Ths node allows you to:

• Configure SAN uplinks, including storage ports and port channels and SAN pin groups.

• View the FC identity assignment

Cisco UCS Manager Storage Management Guide, Release 4.2

Overview

The UCS Manager SAN Tab

• Configure WWN Pools, including WWPN, WWxN, and WWxN, and iSCSI Qualified Name (IQN), pools.

• View the FSM details for a particular end point to determine if a task succeeded or failed and use the FSM to troubleshoot any failures.

• Monitor storage events and faults for health management.

• Storage Cloud —This node allows you to:

• Configure storage FC links and storage FCoE interfaces (using SAN Storage Manager.

• Configure VSAN settings.

• Monitor SAN cloud events for health management.

• Policies —This node allows you to:

• Configure threshold policies, classes, and properties and monitor events.

• Configure threshold organization and sub-organization storage policies, including default VHBA, behavior, FC adaptor, LACP, SAN connectivity, SAN connector, and VHBA templates.

• Pools —This node allows you to configure pools defined in the system, including IQN, IQN suffix,

WWNN, WWPN, and WWxN.

• Traffic Monitoring Sessions —This node allows you to configure port traffic monitoring sessions defined in the system.

Cisco UCS Manager Storage Management Guide, Release 4.2

C H A P T E R

SAN Ports and Port Channels

•

Port Modes, on page 9

•

Port Types, on page 9

•

Server Ports, on page 11

•

Reconfiguring a Port on a Fabric Interconnect, on page 11

•

Enabling or Disabling a Port on a Fabric Interconnect, on page 12

•

Unconfiguring a Port on a Fabric Interconnect, on page 13

•

Appliance Ports, on page 13

•

FCoE and Fibre Channel Storage Ports, on page 15

•

FC Links Rebalancing, on page 17

•

Configuring FC Uplink Ports, on page 17

•

FCoE Uplink Ports, on page 18

•

Unified Storage Ports, on page 19

•

Unified Uplink Ports, on page 21

•

Policy-Based Port Error Handling, on page 23

•

Fibre Channel Port Channels, on page 24

•

FCoE Port Channels, on page 29

•

Unified Uplink Port Channel, on page 30

Port Modes

The port mode determines whether a unified port on the fabric interconnect is configured to carry Ethernet or Fibre Channel traffic. You configure the port mode in Cisco UCS Manager. However, the fabric interconnect does not automatically discover the port mode.

Changing the port mode deletes the existing port configuration and replaces it with a new logical port. Any objects associated with that port configuration, such as VLANs and VSANS, are also removed. There is no restriction on the number of times you can change the port mode for a unified port.

Port Types

The port type defines the type of traffic carried over a unified port connection.

Cisco UCS Manager Storage Management Guide, Release 4.2

Port Types

SAN Ports and Port Channels

By default, unified ports changed to Ethernet port mode are set to the Ethernet uplink port type. Unified ports changed to Fibre Channel port mode are set to the Fibre Channel uplink port type. You cannot unconfigure

Fibre Channel ports.

Changing the port type does not require a reboot.

Ethernet Port Mode

When you set the port mode to Ethernet, you can configure the following port types:

• Server ports

• Ethernet uplink ports

• Ethernet port channel members

• FCoE ports

• Appliance ports

• Appliance port channel members

• SPAN destination ports

• SPAN source ports

Note For SPAN source ports, configure one of the port types and then configure the port as SPAN source.

Fibre Channel Port Mode

When you set the port mode to Fibre Channel, you can configure the following port types:

• Fibre Channel uplink ports

• Fibre Channel port channel members

• Fibre Channel storage ports

• FCoE Uplink ports

• SPAN source ports

Note For SPAN source ports, configure one of the port types and then configure the port as SPAN source.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Server Ports

Configuring Server Ports

All of the port types listed are configurable on both the fixed module and expansion module, including the server ports.

This task describes only one method of configuring ports. You can also configure ports from a right-click menu, or in the LAN Uplinks Manager.

SUMMARY STEPS

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name > Fixed Module > Ethernet

Ports .

Click a port under the Ethernet Ports node.

In the Work pane, click the General tab.

In the Actions area, click Reconfigure .

From the drop-down list, choose Configure as Server Port .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name > Fixed Module > Ethernet Ports .

Click a port under the Ethernet Ports node.

In the Work pane, click the General tab.

In the Actions area, click Reconfigure .

From the drop-down list, choose Configure as Server Port .

Reconfiguring a Port on a Fabric Interconnect

SUMMARY STEPS

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the ports that you want to reconfigure.

Click the port or ports that you want to reconfigure.

In the Work pane, click the General tab.

In the Actions area, click Reconfigure .

From the drop-down list, choose which way you want the port reconfigured.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Enabling or Disabling a Port on a Fabric Interconnect

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the ports that you want to reconfigure.

Click the port or ports that you want to reconfigure.

In the Work pane, click the General tab.

In the Actions area, click Reconfigure .

From the drop-down list, choose which way you want the port reconfigured.

Example: Reconfiguring an Uplink Ethernet Port as a Server Port

Expand the Ethernet Ports node and select the port you want to reconfigure.

Follow steps 5 and 6 above.

From the drop-down list choose Configure as Server Port .

Enabling or Disabling a Port on a Fabric Interconnect

After you enable or disable a port on a fabric interconnect, wait for at least 1 minute before you re-acknowledge the chassis. If you re-acknowledge the chassis too soon, the pinning of server traffic from the chassis might not get updated with the changes to the port that you enabled or disabled.

You can enable or disable a port only when it is configured. If the port is unconfigured, the enable and disable options are not active.

SUMMARY STEPS

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the ports that you want to enable or disable.

Under the Ethernet Ports node, select a port.

In the Work pane, click the General tab.

In the Actions area, click Enable Port or Disable Port .

If a confirmation dialog box displays, click Yes .

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the ports that you want to enable or disable.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Unconfiguring a Port on a Fabric Interconnect

Step 4

Step 5

Step 6

Step 7

Step 8

Under the Ethernet Ports node, select a port.

In the Work pane, click the General tab.

In the Actions area, click Enable Port or Disable Port .

If a confirmation dialog box displays, click Yes .

Click OK .

Unconfiguring a Port on a Fabric Interconnect

SUMMARY STEPS

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the ports that you want to unconfigure.

Under the Ethernet Ports node, select a port.

In the Work pane, click the General tab.

In the Actions area, click Unconfigure .

If a confirmation dialog box displays, click Yes .

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the ports that you want to unconfigure.

Under the Ethernet Ports node, select a port.

In the Work pane, click the General tab.

In the Actions area, click Unconfigure .

If a confirmation dialog box displays, click Yes .

Click OK .

Appliance Ports

Appliance ports are only used to connect fabric interconnects to directly attached NFS storage.

Note When you create a new appliance VLAN, its IEEE VLAN ID is not added to the LAN Cloud. Therefore, appliance ports that are configured with the new VLAN remain down, by default, due to a pinning failure.

To bring up these appliance ports, you have to configure a VLAN in the LAN Cloud with the same IEEE

VLAN ID.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Configuring an Appliance Port

Cisco UCS Manager supports up to four appliance ports per fabric interconnect.

Configuring an Appliance Port

You can configure Appliance ports on either the fixed module or an expansion module.

This task describes only one method of configuring appliance ports. You can also configure appliance ports from the General tab for the port.

Note If you configure an appliance port when the uplink port is down, Cisco UCS Manager may display an error message stating that the appliance port has failed. This message is controlled by the Action on Uplink Fail option in the associated Network Control Policy.

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

Step 11

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the ports that you want to configure.

Under the Ethernet Ports node, select a port.

If you want to reconfigure a server port, uplink Ethernet port, or FCoE storage port, expand the appropriate node.

In the Work pane, click the General tab.

In the Actions area, click Reconfigure .

From the drop-down list, click Configure as Appliance Port .

If a confirmation dialog box displays, click Yes .

In the Configure as Appliance Port dialog box, complete the required fields.

In the VLANs area, do the following: a) In the Port Mode field, click one of the following radio buttons to select the mode you want to use for the port channel:

• Trunk —Cisco UCS Manager GUI displays the VLANs Table that lets you choose the VLANs you want to use.

• Access —Cisco UCS Manager GUI displays the Select VLAN drop-down list that allows you to choose a

VLAN to associate with this port or port channel.

With either mode, you can click the Create VLAN link to create a new VLAN.

Note If traffic for the appliance port needs to traverse the uplink ports, you must also define each VLAN used by this port in the LAN cloud. For example, you need the traffic to traverse the uplink ports if the storage is also used by other servers, or if you want to ensure that traffic fails over to the secondary fabric interconnect if the storage controller for the primary fabric interconnect fails.

b) If you clicked the Trunk radio button, complete the required fields in the VLANs table.

c) If you clicked the Access radio button, choose a VLAN from the Select VLAN drop-down list.

(Optional) If you want to add an endpoint, check the Ethernet Target Endpoint check box and specify the name and

MAC address.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Modifying the Properties of an Appliance Port

Step 12 Click OK .

Modifying the Properties of an Appliance Port

SUMMARY STEPS

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the appliance port that you want to modify.

Expand Ethernet Ports .

Click the appliance port for which you want to modify the properties.

In the Work pane, click the General tab.

In the Actions area, click Show Interface .

In the Properties dialog box, modify the values as needed.

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the appliance port that you want to modify.

Expand Ethernet Ports .

Click the appliance port for which you want to modify the properties.

In the Work pane, click the General tab.

In the Actions area, click Show Interface .

You may need to expand the pane or use the scroll bars in the Properties dialog box to see all the fields.

In the Properties dialog box, modify the values as needed.

Click OK .

FCoE and Fibre Channel Storage Ports

Configuring an Ethernet Port as an FCoE Storage Port

You can configure FCoE storage ports on either the fixed module or an expansion module.

This task describes only one method of configuring FCoE storage ports. You can also configure FCoE storage ports from the General tab for the port.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Configuring a Fibre Channel Storage Port

Before you begin

The Fibre Channel switching mode must be set to Switching for these ports to be valid. The storage ports cannot function in end-host mode.

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Depending upon the location of the ports you want to configure, expand one of the following:

• Fixed Module

• Expansion Module

Click one or more of the ports under the Ethernet Ports node.

If you want to reconfigure an uplink Ethernet port, server port, or appliance port, expand the appropriate node.

Right-click the selected port or ports and choose Configure as FCoE Storage Port .

On Cisco UCS 6454 Fabric Interconnects, ports 49-54 cannot be configured as FCoE storage ports.

On Cisco UCS 64108 Fabric Interconnects, port 97-108 cannot be configured as FCoE storage ports.

If a confirmation dialog box displays, click Yes .

Click OK .

Configuring a Fibre Channel Storage Port

This task describes only one method of configuring FC storage ports. You can also configure FC storage ports from the General tab for the port.

Before you begin

The Fibre Channel switching mode must be set to Switching for these ports to be valid. The storage ports cannot function in end-host mode.

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the Expansion Module node.

Click one or more of the ports under the FC Ports node.

Right-click the selected port or ports and choose Configure as FC Storage Port .

If a confirmation dialog box displays, click Yes .

Click OK .

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Restoring an Uplink Fibre Channel Port

This task describes only one method of restoring an FC storage port to function as an uplink FC port. You can also reconfigure FC storage ports from the General tab for the port.

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the Expansion Module node.

Click one or more of the ports under the FC Ports node.

Right-click the selected port or ports and choose Configure as Uplink Port .

If a confirmation dialog box displays, click Yes .

Click OK .

FC Links Rebalancing

The FC uplinks balance automatically when FC Port Channels are utilized. To create FC Port Channels, refer to

Creating a Fibre Channel Port Channel, on page 24

For the FC uplinks that are not members of the Port Channels (Individual ISLs), load balancing is done according to the FC uplinks balancing algorithm. For a vHBA of a host or service profile to choose an available

FC uplink, when FC uplink trunking is disabled, the uplink and vHBA must belong to the same VSAN

For each vHBA, the algorithm searches for an FC uplink in the following order:

Least used FC uplink based on the number of vHBAs currently bound to the uplink.

If FC uplinks are equally balanced, then round robin is used.

This process continues for all the other vHBAs. The algorithm also considers other parameters such as pre-fip/fip adapters and number of flogis. You may not see the least-used component when there are less than six flogis.

After a port configuration or any other uplink state changes, if the traffic passing through the FC uplinks is no longer balanced, you can re-balance the traffic by resetting the vHBA(s) on each adapter and allow the load balancing algorithm to evaluate for the current state of the FC uplinks.

Configuring FC Uplink Ports

You can configure an FC Uplink port on either a fixed module or an expansion module.

This task describes only one method of configuring FC Uplink ports. You can also configure FC uplink ports from a right-click menu for the port.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

FCoE Uplink Ports

Important For Cisco UCS 6400 Series fabric interconnect, if the FC uplink speed is 8 Gbps, set the fill pattern as IDLE on the uplink switch. If the fill pattern is not set as IDLE, FC uplinks operating at 8 Gbps might go to an errDisabled state, lose SYNC intermittently, or notice errors or bad packets.

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the ports that you want to configure.

Under the FC Ports node, select any Storage port.

In the Work pane, click the General tab.

From the Actions area, select Configure as Uplink Port .

If a confirmation dialog box displays, click Yes .

The Cisco UCS Manager GUI displays a success message.

In the Actions area, Configure as Uplink Port becomes grayed out and Configure as FC Storage Port becomes active.

FCoE Uplink Ports

FCoE uplink ports are physical Ethernet interfaces between the fabric interconnects and the upstream Ethernet switch, used for carrying FCoE traffic. With this support the same physical Ethernet port can carry both

Ethernet traffic and Fibre Channel traffic.

FCoE uplink ports connect to upstream Ethernet switches using the FCoE protocol for Fibre Channel traffic.

This allows both the Fibre Channel traffic and Ethernet traffic to flow on the same physical Ethernet link.

Note FCoE uplinks and unified uplinks enable the multi-hop FCoE feature, by extending the unified fabric up to the distribution layer switch.

You can configure the same Ethernet port as any of the following:

• FCoE uplink port —As an FCoE uplink port for only Fibre Channel traffic.

• Uplink port —As an Ethernet port for only Ethernet traffic.

• Unified uplink port —As a unified uplink port to carry both Ethernet and Fibre Channel traffic.

Configuring FCoE Uplink Ports

You can configure an FCoE Uplink port on either a fixed module or an expansion module.

This task describes only one method of configuring FCoE Uplink ports. You can also configure FCoE uplink ports from a right-click menu or from the General tab for the port.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Unified Storage Ports

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the ports that you want to configure.

Under the Ethernet Ports node, select any Unconfigured port.

In the Work pane, click the General tab.

In the Actions area, click Reconfigure .

From the drop down options, select Configure as FCoE Uplink Port .

If a confirmation dialog box displays, click Yes .

The Cisco UCS Manager GUI displays a success message.

In the Properties area, the Role changes to Fcoe Uplink .

Unified Storage Ports

Unified storage involves configuring the same physical port as both an Ethernet storage interface and an FCoE storage interface. You can configure any appliance port or FCoE storage port as a unified storage port, on either a fixed module or an expansion module. To configure a unified storage port, you must have the fabric interconnect in Fibre Channel switching mode.

In a unified storage port, you can enable or disable individual FCoE storage or appliance interfaces.

• In an unified storage port, if you do not specify a non-default VLAN for the appliance port, the

FCoE-storage-native-vlan will be assigned as the native VLAN on the unified storage port. If the appliance port has a non-default native VLAN specified as native VLAN, this will be assigned as the native VLAN for the unified storage port.

• When you enable or disable the appliance interface, the corresponding physical port is enabled or disabled.

So when you disable the appliance interface in unified storage, even if the FCoE storage is enabled, it goes down with the physical port.

• When you enable or disable the FCoE storage interface, the corresponding VFC is enabled or disabled.

So when the FCoE storage interface is disabled in a unified storage port, the appliance interface will continue to function normally.

Configuring an Appliance Port as a Unified Storage Port

You can configure a unified storage port either from an appliance port or from an FCoE storage port. You can also configure the unified storage port from an unconfigured port. If you start from an unconfigured port, you will assign either an appliance configuration or an FCoE storage configuration to the port, and then will add another configuration to enable it as a unified storage port.

Important Make sure the fabric interconnect is in Fibre Channel switching mode.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Unconfiguring a Unified Storage Port

SUMMARY STEPS

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Depending on the location of the ports you want to configure, expand one of the following:

Under the Ethernet Ports node, select any the port that is already configured as an appliance port.

In the Actions area, click Reconfigure .

From the pop-up menu, select Configure as FCoE Storage port.

If a confirmation dialog box displays, click Yes .

The Cisco UCS Manager GUI displays a success message. In the Properties area, the Role changes to

Unified Storage .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Depending on the location of the ports you want to configure, expand one of the following:

• Fixed Module

• Expansion Module

Under the Ethernet Ports node, select any the port that is already configured as an appliance port.

In the Work pane, under the General tab, in the Properties area, the Role will show as Appliance Storage .

In the Actions area, click Reconfigure .

From the pop-up menu, select Configure as FCoE Storage port.

If a confirmation dialog box displays, click Yes .

The Cisco UCS Manager GUI displays a success message. In the Properties area, the Role changes to Unified Storage .

Unconfiguring a Unified Storage Port

You can unconfigure and remove both configurations from the unified connect port. Or you can unconfigure either of them and retain the other on the port.

SUMMARY STEPS

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the ports that you want to unconfigure.

Under the Ethernet Ports node, select the port that you want to unconfigure.

In the Work pane, click the General tab.

In the Actions area, click Unconfigure . You will see the following options:

Select one of the unconfigure options.

If a confirmation dialog box displays, click Yes .

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Unified Uplink Ports

The Cisco UCS Manager GUI displays a success message. In the Properties area, the Role changes to based on your unconfigure selection.

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the ports that you want to unconfigure.

Under the Ethernet Ports node, select the port that you want to unconfigure.

In the Work pane, click the General tab.

In the Actions area, click Unconfigure . You will see the following options:

• Unconfigure FCoE Storage Port

• Unconfigure Appliance Port

• Unconfigure both

Select one of the unconfigure options.

If a confirmation dialog box displays, click Yes .

The Cisco UCS Manager GUI displays a success message. In the Properties area, the Role changes to based on your unconfigure selection.

Unified Uplink Ports

When you configure an Ethernet uplink and an FCoE uplink on the same physical Ethernet port, it is called a unified uplink port. You can individually enable or disable either the FCoE or Ethernet interfaces independently.

• Enabling or disabling the FCoE uplink results in the corresponding VFC being enabled or disabled.

• Enabling or disabling an Ethernet uplink results in the corresponding physical port being enabled or disabled.

If you disable an Ethernet uplink, it disables the underlying physical port in a unified uplink. Therefore, even when the FCoE uplink is enabled, the FCoE uplink also goes down. But if you disable an FCoE uplink, only the VFC goes down. If the Ethernet uplink is enabled, it can still function properly in the unified uplink port.

Configuring Unified Uplink Ports

You can configure the unified uplink port from either of the following:

• From an existing FCoE uplink port or Ethernet uplink port

• From an unconfigured uplink port

You can configure the unified uplink port on either a fixed module or on an expansion module.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Unconfiguring Unified Uplink Port

SUMMARY STEPS

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the ports that you want to configure.

Under the Ethernet Ports node, select a port.

In the Work pane, click the General tab.

In the Properties area, make sure the Role shows as Fcoe Uplink .

In the Actions area, click Reconfigure .

From the drop-down options, select Configure as Uplink Port .

If a confirmation dialog box displays, click Yes .

10.

The Cisco UCS Manager GUI displays a success message.

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the ports that you want to configure.

Under the Ethernet Ports node, select a port.

In the Work pane, click the General tab.

In the Properties area, make sure the Role shows as Fcoe Uplink .

In the Actions area, click Reconfigure .

From the drop-down options, select Configure as Uplink Port .

If a confirmation dialog box displays, click Yes .

The Cisco UCS Manager GUI displays a success message.

In the Properties area, the Role changes to Unified Uplink .

Unconfiguring Unified Uplink Port

You can unconfigure and remove both configurations from the unified uplink port. Or you can unconfigure either the FCoE configuration or Ethernet port configuration and retain the other on the port.

SUMMARY STEPS

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the ports that you want to unconfigure.

Under the Ethernet Ports node, select the port you want to unconfigure.

In the Work pane, click the General tab.

In the Actions area, click Unconfigure . Select one of the following options:

If a confirmation dialog box displays, click Yes .

The Cisco UCS Manager GUI displays a success message. In the Properties area, the Role changes based on your unconfigure selection.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Policy-Based Port Error Handling

Click Save Changes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

In the Navigation pane, click Equipment .

Expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .

Expand the node for the ports that you want to unconfigure.

Under the Ethernet Ports node, select the port you want to unconfigure.

In the Work pane, click the General tab.

In the Actions area, click Unconfigure . Select one of the following options:

• Unconfigure FCoE Uplink Port

• Unconfigure Uplink Port

• Unconfigure both

If a confirmation dialog box displays, click Yes .

The Cisco UCS Manager GUI displays a success message. In the Properties area, the Role changes based on your unconfigure selection.

Click Save Changes .

Policy-Based Port Error Handling

If Cisco UCS Manager detects any errors on active network interface (NI) ports, and if the error-disable feature has been implemented, Cisco UCS Manager automatically disables the respective fabric interconnect port that is connected to the NI port that had errors. When a fabric interconnect port is error disabled, it is effectively shut down and no traffic is sent or received on that port.

The error-disable function serves two purposes:

• It lets you know which fabric interconnect port is error-disabled and that the connected NI Port has errors.

• It eliminates the possibility that this port can cause the failure of other ports other ports connected to the same Chassis/FEX. Such a failure can occur when the NI port has errors, which can ultimately cause serious network issues. The error-disable function helps prevent these situations.

Configuring Error-Based Action

Step 1

Step 2

Step 3

Step 4

In the Navigation pane, click Admin .

Expand Admin > All > Stats Management > fabric > Internal LAN > thr-policy-default > etherNiErrStats .

Select a delta property.

In the Work pane, click the General tab.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Fibre Channel Port Channels

Step 5

Step 6

Step 7

Step 8

To implement an error-disable state on a fabric interconnect port, check the Disable FI port when fault is raised check box.

To enable auto recovery, in the Enable Auto Recovery field, select Enable .

To specify the time after which the port can automatically be re-enabled, in the Time (in minutes) field, type the desired value.

Click Save Changes .

Fibre Channel Port Channels

A Fibre Channel port channel allows you to group several physical Fibre Channel ports (link aggregation) to create one logical Fibre Channel link to provide fault-tolerance and high-speed connectivity. In Cisco UCS

Manager, you create a port channel first and then add Fibre Channel ports to the port channel.

Note Fibre Channel port channels are not compatible with non-Cisco technology.

You can create up to four Fibre Channel port channels in each Cisco UCS domain with Cisco UCS 6200,

6300, and 6400 Series Fabric Interconnects. Each Fibre Channel port channel can include a maximum of 16 uplink Fibre Channel ports.

You can create up to two Fibre Channel port channels in each Cisco UCS domain with Cisco UCS 6324 fabric interconnects. Each Fibre Channel port channel can include a maximum of four uplink Fibre Channel ports.

Ensure that the Fibre Channel port channel on the upstream NPIV switch is configured with its channel mode as active . If both the member port(s) and peer port(s) do not have the same channel mode configured, the port channel will not come up. When the channel mode is configured as active , the member ports initiate port channel protocol negotiation with the peer port(s) regardless of the channel group mode of the peer port. If the peer port, while configured in a channel group, does not support the port channel protocol, or responds with a nonnegotiable status, it defaults to the On mode behavior. The active port channel mode allows automatic recovery without explicitly enabling and disabling the port channel member ports at either end.

This example shows how to configure channel mode as active: switch(config)# int po114 switch(config-if)# channel mode active

Creating a Fibre Channel Port Channel

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud .

Expand the node for the fabric where you want to create the port channel.

Right-click the FC Port Channels node and choose Create Port Channel .

In the Set Port Channel Name panel, specify the ID and name, then click Next .

In the Add Ports panel, specify the port channel admin speed, and add ports to the port channel.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Enabling a Fibre Channel Port Channel

Click Finish .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud .

Expand the node for the fabric where you want to create the port channel.

Right-click the FC Port Channels node and choose Create Port Channel .

In the Set Port Channel Name panel, specify the ID and name, then click Next .

In the Add Ports panel, specify the port channel admin speed, and add ports to the port channel.

Port Channel Admin Speed 1 Gbps and 2 Gbps are not available for Cisco UCS 6400 Series Fabric Interconnect.

Port

Channel Admin Speed 16 Gbps and 32 Gbps are available only for Cisco UCS 6400 Series Fabric Interconnect.

Click Finish .

Enabling a Fibre Channel Port Channel

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud > Fabric > FC Port Channels .

Click the port channel you want to enable.

In the Work pane, click the General tab.

In the Actions area, click Enable Port Channel .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud > Fabric > FC Port Channels .

Click the port channel you want to enable.

In the Work pane, click the General tab.

In the Actions area, click Enable Port Channel .

If a confirmation dialog box displays, click Yes .

Disabling a Fibre Channel Port Channel

SUMMARY STEPS

In the Navigation pane, click SAN .

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Adding Ports to and Removing Ports from a Fibre Channel Port Channel

Expand SAN > SAN Cloud > Fabric > FC Port Channels .

Click the port channel you want to disable.

In the Work pane, click the General tab.

In the Actions area, click Disable Port Channel .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud > Fabric > FC Port Channels .

Click the port channel you want to disable.

In the Work pane, click the General tab.

In the Actions area, click Disable Port Channel .

If a confirmation dialog box displays, click Yes .

Adding Ports to and Removing Ports from a Fibre Channel Port Channel

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud > Fabric > FC Port Channels .

Click the port channel to which you want to add or remove ports.

In the Work pane, click the General tab.

In the Actions area, click Add Ports .

In the Add Ports dialog box, do one of the following:

• To add ports, choose one or more ports in the Ports table, and then click the >> button to add the ports to the Ports in the port channel table.

• To remove ports, choose one or more ports in the Ports in the port channel table, and then click the << button to remove the ports from the port channel and add them to the Ports table.

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud > Fabric > FC Port Channels .

Click the port channel to which you want to add or remove ports.

In the Work pane, click the General tab.

In the Actions area, click Add Ports .

In the Add Ports dialog box, do one of the following:

• To add ports, choose one or more ports in the Ports table, and then click the >> button to add the ports to the Ports in the port channel table.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Modifying the Properties of a Fibre Channel Port Channel

Step 7

• To remove ports, choose one or more ports in the Ports in the port channel table, and then click the << button to remove the ports from the port channel and add them to the Ports table.

Click OK .

Modifying the Properties of a Fibre Channel Port Channel

Note If you are connecting two Fibre Channel port channels, the admin speed for both port channels must match for the link to operate. If the admin speed for one or both of the Fibre Channel port channels is set to auto,

Cisco UCS adjusts the admin speed automatically.

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud > Fabric > FC Port Channels .

Click the port channel that you want to modify.

In the Work pane, click the General tab.

In the Properties area, change the values in one or more of the following fields:

Click Save Changes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud > Fabric > FC Port Channels .

Click the port channel that you want to modify.

In the Work pane, click the General tab.

In the Properties area, change the values in one or more of the following fields:

Name

Name field

Description

The user-defined name given to the port channel. This name can be between 1 and 16 alphanumeric characters.

VSAN drop-down list The VSAN associated with the port channel.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Deleting a Fibre Channel Port Channel

Name

Port Channel Admin Speed drop-down list

Description

The admin speed of the port channel. This can be:

• 1 Gbps

Note Not available for Cisco UCS 6400 Series

Fabric Interconnect.

• 2 Gbps

Note Not available for Cisco UCS 6400 Series

Fabric Interconnect.

• 4 Gbps

• 8 Gbps

• 16 Gbps

Note Available only for Cisco UCS 6400 Series

Fabric Interconnect.

• 32 Gpbs

Note Available only for Cisco UCS 6400 Series

Fabric Interconnect.

• auto

Note Not available for Cisco UCS 6400 Series

Fabric Interconnect.

Step 6 Click Save Changes .

Deleting a Fibre Channel Port Channel

SUMMARY STEPS

In the Navigation pane, click LAN .

Expand SAN > SAN Cloud > Fabric > FC Port Channels .

Right-click the port channel you want to delete and choose Delete .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

In the Navigation pane, click LAN .

Expand SAN > SAN Cloud > Fabric > FC Port Channels .

Right-click the port channel you want to delete and choose Delete .

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

FCoE Port Channels

Step 4 If a confirmation dialog box displays, click Yes .

FCoE Port Channels

An FCoE port channel allows you to group several physical FCoE ports to create one logical FCoE port channel. At a physical level, the FCoE port channel carries FCoE traffic over an Ethernet port channel. So an

FCoE port channel with a set of members is essentially an Ethernet port channel with the same members. This

Ethernet port channel is used as a physical transport for FCoE traffic.

For each FCoE port channel, Cisco UCS Manager creates a VFC internally and binds it to an Ethernet port channel. FCoE traffic received from the hosts is sent over the VFC the same way as the FCoE traffic is sent over Fibre Channel uplinks.

Creating an FCoE Port Channel

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud .

Expand the node for the fabric where you want to create the port channel.

Right-click the FCoE Port Channels node and choose Create FCoE Port Channel .

In the Set Port Channel Name panel of the Create FCoE Port Channel wizard, specify the ID and name, then click Next .

In the Add Ports panel of the Create FCoE Port Channel wizard, specify the ports that you want to add.

Click Finish .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud .

Expand the node for the fabric where you want to create the port channel.

Right-click the FCoE Port Channels node and choose Create FCoE Port Channel .

In the Set Port Channel Name panel of the Create FCoE Port Channel wizard, specify the ID and name, then click

Next .

In the Add Ports panel of the Create FCoE Port Channel wizard, specify the ports that you want to add.

Click Finish .

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Ports and Port Channels

Deleting an FCoE Port Channel

SUMMARY STEPS

In the Navigation pane, click SAN .

On the SAN tab, expand SAN > SAN Cloud > Fabric > FCoE Port Channels .

Right-click the port channel you want to delete and choose Delete .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

In the Navigation pane, click SAN .

On the SAN tab, expand SAN > SAN Cloud > Fabric > FCoE Port Channels .

Right-click the port channel you want to delete and choose Delete .

If a confirmation dialog box displays, click Yes .

Unified Uplink Port Channel

When you create an Ethernet port channel and an FCoE port channel with the same ID, it is called a unified uplink port channel. When the unified port channel is created, a physical Ethernet port channel and a VFC are created on the fabric interconnect with the specified members. The physical Ethernet port channel is used to carry both Ethernet and FCoE traffic. The VFC binds FCoE traffic to the Ethernet port channel.

The following rules will apply to the member port sets of the unified uplink port channel:

• The Ethernet port channel and FCoE port channel on the same ID, must have the same set of member ports.

• When you add a member port channel to the Ethernet port channel, Cisco UCS Manager adds the same port channel to FCoE port channel as well. Similarly, adding a member to the FCoE port channel adds the member port to the Ethernet port channel.

• When you delete a member port from one of the port channels, Cisco UCS Manager automatically deletes the member port from the other port channel.

If you disable an Ethernet uplink port channel, it disables the underlying physical port channel in a unified uplink port channel. Therefore, even when the FCoE uplink is enabled, the FCoE uplink port channel also goes down. If you disable an FCoE uplink port channel, only the VFC goes down. If the Ethernet uplink port channel is enabled, it can still function properly in the unified uplink port channel.

Cisco UCS Manager Storage Management Guide, Release 4.2

C H A P T E R

Fibre Channel Zoning

•

Information About Fibre Channel Zoning, on page 31

•

Support for Fibre Channel Zoning in Cisco UCS Manager, on page 32

•

Guidelines and recommendations for Cisco UCS Manager-Based Fibre Channel Zoning, on page 34

•

Configuring Fibre Channel Zoning, on page 34

•

Creating a VSAN for Fibre Channel Zoning, on page 35

•

Creating a New Fibre Channel Zone Profile, on page 37

•

Deleting a Fibre Channel Zone Profile, on page 40

•

Deleting a Fibre Channel User Zone, on page 40

•

Fibre Channel Storage Connection Policies, on page 41

Information About Fibre Channel Zoning

Fibre Channel zoning allows you to partition the Fibre Channel fabric into one or more zones. Each zone defines the set of Fibre Channel initiators and Fibre Channel targets that can communicate with each other in a VSAN. Zoning also enables you to set up access control between hosts and storage devices or user groups.

The access and data traffic control provided by zoning does the following:

• Enhances SAN network security

• Helps prevent data loss or corruption

• Reduces performance issues

Information About Zones

A zone consists of multiple zone members and has the following characteristics:

• Members in a zone can access each other; members in different zones cannot access each other.

• Zones can vary in size.

• Devices can belong to more than one zone.

• A physical fabric can have a maximum of 8,000 zones.

Cisco UCS Manager Storage Management Guide, Release 4.2

Fibre Channel Zoning

Information About Zone Sets

Each zone set consists of one or more zones. You can use zone sets to enforce access control within the Fibre

Channel fabric. In addition, zone sets provide you with the following advantages:

• Only one zone set can be active at any time.

• All zones in a zone set can be activated or deactivated as a single entity across all switches in the fabric.

• Changes to a zone set are not applied until the zone set has been activated. If you make changes to the active zone set, you must reactivate that zone set to apply the changes.

• A zone can be a member of more than one zone set.

• A switch in a zone can have a maximum of 500 zone sets.

Support for Fibre Channel Zoning in Cisco UCS Manager

Cisco UCS Manager supports switch-based Fibre Channel zoning and Cisco UCS Manager-based Fibre

Channel zoning. You cannot configure a combination of zoning types in the same Cisco UCS domain. You can configure a Cisco UCS domain with one of the following types of zoning:

• Cisco UCS Manager-based Fibre Channel zoning—This configuration combines direct attach storage with local zoning. Fibre Channel or FCoE storage is directly connected to the fabric interconnects and zoning is performed in Cisco UCS Manager, using Cisco UCS local zoning. Any existing Fibre Channel or FCoE uplink connections need to be disabled. Cisco UCS does not currently support active Fibre

Channel or FCoE uplink connections coexisting with the utilization of the UCS Local Zoning feature.

• Switch-based Fibre Channel zoning—This configuration combines direct attach storage with uplink zoning. The Fibre Channel or FCoE storage is directly connected to the fabric interconnects and zoning is performed externally to the Cisco UCS domain through an MDS or Nexus 5000 switch. This configuration does not support local zoning in the Cisco UCS domain.

Note Zoning is configured on a per-VSAN basis. You cannot enable zoning at the fabric level.

Cisco UCS Manager-Based Fibre Channel Zoning

With Cisco UCS Manager-based zoning, Cisco UCS Manager controls the Fibre Channel zoning configuration for the Cisco UCS domain, including creating and activating zones for all VSANs that you set up with this type of zoning. This type of zoning is also know as local zoning or direct attach storage with local zoning.

Note You cannot implement Cisco UCS Manager-based zoning if the VSAN is also configured to communicate with a VSAN on an upstream switch and includes Fibre Channel or FCoE uplink ports.

Cisco UCS Manager Storage Management Guide, Release 4.2

Fibre Channel Zoning vHBA Initiator Groups

Supported Fibre Channel Zoning Modes

Cisco UCS Manager-based zoning supports the following types of zoning:

• Single initiator single target—Cisco UCS Manager automatically creates one zone for each vHBA and storage port pair. Each zone has two members. We recommend that you configure this type of zoning unless you expect the number of zones to exceed the maximum supported.

• Single initiator multiple targets—Cisco UCS Manager automatically creates one zone for each vHBA.

We recommend that you configure this type of zoning if you expect the number of zones to reach or exceed the maximum supported.

vHBA Initiator Groups vHBA initiator groups determine the Fibre Channel zoning configuration for all vHBAs in a service profile.

Cisco UCS Manager does not include any default vHBA initiator groups. You must create vHBA initiator groups in any service profile that is to be assigned to servers included in a zone.

The configuration in a vHBA initiator group determines the following:

• The vHBAs included in the initiator group, which are sometimes referred to as vHBA initiators.

• A Fibre Channel storage connection policy, which includes the associated VSAN and the Fibre Channel target ports on the storage array.

• The type of Fibre Channel zoning to be configured for the vHBAs included in the group.

Fibre Channel Storage Connection Policy

The Fibre Channel storage connection policy contains a collection of target storage ports on storage arrays that you use to configure Cisco UCS Manager-based Fibre Channel zoning. You can create this policy under an organization or an initiator group.

The storage arrays in these zones must be directly connected to the fabric interconnects. The target storage ports on these arrays that you include in the Fibre Channel storage connection policy can be either Fibre

Channel storage ports or FCoE storage ports. You use the WWN of a port to add it to the policy and to identify the port for the Fibre Channel zone.

Note Cisco UCS Manager does not create default Fibre Channel storage.

Fibre Channel Active Zone Set Configuration

In each VSAN that has been enabled for Fibre Channel zoning, Cisco UCS Manager automatically configures one zone set and multiple zones. The zone membership specifies the set of initiators and targets that are allowed to communicate with each other. Cisco UCS Manager automatically activates that zone set.

Cisco UCS Manager processes the user-configured vHBA initiator groups and their associated Fibre Channel storage connection policy to determine the desired connectivity between Fibre Channel initiators and targets.

Cisco UCS Manager uses the following information to build pair-wise zone membership between initiators and targets:

• The port WWNs of the vHBA initiators derived from the vHBA initiator groups.

Cisco UCS Manager Storage Management Guide, Release 4.2

Fibre Channel Zoning

Switch-Based Fibre Channel Zoning

• The port WWNs of the storage array derived from the storage connection policy.

Switch-Based Fibre Channel Zoning

With switch-based zoning, a Cisco UCS domain inherits the zoning configuration from the upstream switch.

You cannot configure or view information about your zoning configuration in Cisco UCS Manager. You have to disable zoning on a VSAN in Cisco UCS Manager to use switch-based zoning for that VSAN.

GuidelinesandrecommendationsforCiscoUCSManager-Based

Fibre Channel Zoning

When you plan your configuration for Fibre Channel zoning, consider the following guidelines and recommendations:

Fibre Channel Switching Mode Must Be Switch Mode for Cisco UCS Manager Configurations

If you want Cisco UCS Manager to handle Fibre Channel zoning, the fabric interconnects must be in Fibre

Channel Switch mode. You cannot configure Fibre Channel zoning in End-Host mode.

Symmetrical Configuration Is Recommended for High Availability

If a Cisco UCS domain is configured for high availability with two fabric interconnects, we recommend that both fabric interconnects are configured with the same set of VSANs.

Configuring Fibre Channel Zoning

Note This procedure provides a high level overview of the steps required to configure a Cisco UCS domain for

Fibre Channel zoning that is controlled by Cisco UCS Manager. You must ensure that you complete all of the following steps.

Step 1

Step 2

Procedure

Command or Action

If you have not already done so, disconnect the fabric interconnects in the Cisco UCS domain from any external

Fibre Channel switches, such as an MDS.

Purpose

If the Cisco UCS domain still includes zones that were managed by the external Fibre Channel switch, run the clear-unmanaged-fc-zone-all command on every affected

VSAN to remove those zones.

This functionality is not currently available in the Cisco

UCS Manager GUI. You must perform this step in the Cisco

UCS Manager CLI.

Cisco UCS Manager Storage Management Guide, Release 4.2

Fibre Channel Zoning

Creating a VSAN for Fibre Channel Zoning

Step 3

Step 4

Step 5

Step 6

Step 7

Command or Action Purpose

Configure the Fibre Channel switching mode for both fabric interconnects in Fibre Channel Switch mode.

You cannot configure Fibre Channel zoning in End-Host mode. See

Configuring Fibre Channel Switching Mode, on page 182

Configure the Fibre Channel and FCoE storage ports that you require to carry traffic for the Fibre Channel zones.

See

Configuring an Ethernet Port as an FCoE Storage Port, on page 15

and

Configuring a Fibre Channel Storage Port, on page 16

Create one or more VSANs and enable Fibre Channel zoning on all VSANs that you require to carry traffic for the Fibre Channel zones.

Create one or more Fibre Channel storage connection policies.

For a cluster configuration, we recommend that you create the VSANs that you intend to include in a Fibre Channel zone in the SAN Uplinks Manager and use the common/global configuration to ensure they are accessible to both fabric interconnects. See

Creating a VSAN for Fibre

Channel Zoning, on page 35 .

You can perform this step when you configure Fibre

Channel zoning in the service profiles, if you prefer. See

Creating a VSAN for Fibre Channel Zoning, on page 35 .

Configure zoning in service profiles or service profile templates for servers that need to communicate through

Fibre Channel zones.

Complete the following steps to complete this configuration:

• Enable zoning in the VSAN or VSANs assigned to the vHBAs. See

Creating a VSAN for Fibre Channel

Zoning, on page 35

• Configure one or more vHBA initiator groups. See

Creating a Service Profile with the Expert Wizard, on page 189 .

Creating a VSAN for Fibre Channel Zoning

Note FCoE VLANs in the SAN cloud and VLANs in the LAN cloud must have different IDs. Using the same ID for an FCoE VLAN in a VSAN and a VLAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that FCoE VLAN. Ethernet traffic is dropped on any VLAN with an ID that overlaps with an FCoE VLAN ID.

SUMMARY STEPS

In the Navigation pane, click SAN .

On the SAN tab, click the SAN node.

In the Work pane, click the SAN Uplinks Manager link on the SAN Uplinks tab.

In the SAN Uplinks Manager, click the VSAN tab.

On the icon bar to the right of the table, click + .

In the Create VSAN dialog box, complete the following fields:

Click OK .

Cisco UCS Manager Storage Management Guide, Release 4.2

Fibre Channel Zoning

Creating a VSAN for Fibre Channel Zoning

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click SAN .

On the SAN tab, click the SAN node.

In the Work pane, click the SAN Uplinks Manager link on the SAN Uplinks tab.

The SAN Uplinks Manager opens in a separate window.

In the SAN Uplinks Manager, click the VSAN tab.

You can create the VSAN on any of the subtabs. However, if you use the All subtab, you can view all of the configured

VSANs in the table.

On the icon bar to the right of the table, click + .

If the + icon is disabled, click an entry in the table to enable it.

In the Create VSAN dialog box, complete the following fields:

Name

Name field

FC Zoning field

Description

The name assigned to the network.

This name can be between 1 and 32 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.

Click the radio button to determine whether Cisco UCS Manager configures

Fibre Channel zoning for the Cisco UCS domain. This can be one of the following:

• Disabled —The upstream switch handles Fibre Channel zoning, or Fibre

Channel zoning is not implemented for the Cisco UCS domain. Cisco UCS

Manager does not configure Fibre Channel zoning.

• Enabled —Cisco UCS Manager configures and controls Fibre Channel zoning for the Cisco UCS domain.

Note If you enable Fibre Channel zoning through Cisco UCS Manager, do not configure the upstream switch with any VSANs that are being used for Fibre Channel zoning.

Cisco UCS Manager Storage Management Guide, Release 4.2

Fibre Channel Zoning

Creating a New Fibre Channel Zone Profile

Name

Type radio button

VSAN ID field

FCoE VLAN field

Description

Click the radio button to determine how the VSAN should be configured. This can be one of the following:

• Common/Global —The VSAN maps to the same VSAN ID in all available fabrics.

• Fabric A —The VSAN maps to the a VSAN ID that exists only in fabric

• Fabric B —The VSAN maps to the a VSAN ID that exists only in fabric

• Both Fabrics Configured Differently —The VSAN maps to a different

VSAN ID in each available fabric. If you choose this option, Cisco UCS

Manager GUI displays a VSAN ID field and a FCoE VLAN field for each fabric.

The unique identifier assigned to the network.

The ID can be between 1 and 4078, or between 4080 and 4093. 4079 is a reserved VSAN ID. In addition, if you plan to use FC end-host mode, the range between 3840 to 4079 is also a reserved VSAN ID range.

The unique identifier assigned to the VLAN used for Fibre Channel connections.

VLAN 4048 is user configurable. However, Cisco UCS Manager uses VLAN

4048 for the following default values. If you want to assign 4048 to a VLAN, you must reconfigure these values:

• After an upgrade to Cisco UCS, Release 2.0—The FCoE storage port native

VLAN uses VLAN 4048 by default. If the default FCoE VSAN was set to use VLAN 1 before the upgrade, you must change it to a VLAN ID that is not used or reserved. For example, consider changing the default to 4049 if that VLAN ID is not in use.

• After a fresh install of Cisco UCS, Release 2.0—The FCoE VLAN for the default VSAN uses VLAN 4048 by default. The FCoE storage port native

VLAN uses VLAN 4049.

For FIP-capable, converged network adapters, such as the Cisco UCS CNA

M72KR-Q and the Cisco UCS CNA M72KR-E, the named VSAN must be configured with a named VLAN that is not the native VLAN for the FCoE

VLAN ID. This configuration ensures that FCoE traffic can pass through these adapters.

Step 7 Click OK .

Creating a New Fibre Channel Zone Profile

Perform the following procedure to create a new Fibre Channel Zone Profile.

Cisco UCS Manager Storage Management Guide, Release 4.2

Fibre Channel Zoning

Creating a New Fibre Channel Zone Profile

Before you begin

Ensure that the VSAN is created for the Fiber Channel Zoning.

SUMMARY STEPS

In the Navigation pane, click SAN .

On the SAN tab, click Storage Cloud .

Right-click FC Zone Profiles and choose Create FC Zone Profile .

In the Create FC Zone Profile dialog box, complete the following fields:

Complete the following fields in the Create FC User Zone dialog box:

Click OK for Create FC Zone Member window.

Click OK for Create FC User Zone window.

Click OK for Create FC Zone Profile window.

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click SAN .

On the SAN tab, click Storage Cloud .

Right-click FC Zone Profiles and choose Create FC Zone Profile .

In the Create FC Zone Profile dialog box, complete the following fields:

Field Description

Name field

Description field

A name for the profile.

This name can be between 1 and 32 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.

This field is optional. Enter a brief description of the zone profile.

FC Zoning radio button

FC User Zones

Select the desired state of the zone profile.

Click the + icon on the right of the table to create FC User

Zone. The Create FC User Zone window is displayed.

Continue to next step for details to create FC user zone.

Note If + icon is disabled, click an entry in the table to enable it.

Complete the following fields in the Create FC User Zone dialog box:

Cisco UCS Manager Storage Management Guide, Release 4.2

Fibre Channel Zoning

Creating a New Fibre Channel Zone Profile

Field

Name

Path field radio button

Description

A name for the FC Zone.

This name can be between 1 and 32 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.

Click the radio button to determine how the VSAN should be configured. Following options are available:

• Path A —The VSAN path to the VSAN ID that exists only in fabric A.

• Path B —The VSAN path to the VSAN ID that exists only in fabric B.

Note Perform one of the following to select a VSAN:

• Select VSAN

• Create VSAN

• Create Storage VSAN

Select VSAN drop-down list

Create VSAN link

Create Storage VSAN

Member WWPNs link

The unique identifier assigned to the VSANs that exists already in the network.

The ID can be between 1 and 4078, or between 4080 and

4093. 4079 is a reserved VSAN ID. You cannot configure fibre channel zoning in end-host mode.

Click the + icon to create a new VSAN in a new window.

This allows you to perform the same task as in

Creating a

VSAN for Fibre Channel Zoning, on page 35 . After creating

the VSAN, you can return here and continue creating channel zone profile.

Click the + icon to create a new storage VSAN in a new window. This allows you to perform the same task as in

Creating a VSAN for Fibre Channel Zoning, on page 35 .

After creating the VSAN, you can return here and continue creating channel zone profile.

Click the + icon on the right of the table to create World

Wide Port Name (WWPN). The Create FC Zone Member window is displayed.

Enter the WWPN for this zone.

Step 6

Step 7

Click OK for Create FC Zone Member window.

Click OK for Create FC User Zone window.

Cisco UCS Manager Storage Management Guide, Release 4.2

Deleting a Fibre Channel Zone Profile

Step 8 Click OK for Create FC Zone Profile window.

The new Fibre Channel Zone Profile created is listed under FC Zone Profiles .

Deleting a Fibre Channel Zone Profile

Perform the following procedure to delete a Fibre Channel Zone Profile.

SUMMARY STEPS

In the Navigation pane, click SAN .

On the SAN tab, click Storage Cloud .

Click FC Zone Profiles .

In the Work pane, right-click the name of the zone profile you wish to delete.

Choose Delete and click Yes to confirm.

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click SAN .

On the SAN tab, click Storage Cloud .

Click FC Zone Profiles .

In the Work pane, right-click the name of the zone profile you wish to delete.

Choose Delete and click Yes to confirm.

The zone profile is deleted from the system.

Deleting a Fibre Channel User Zone

Perform the following procedure to delete a Fibre Channel User Zone.

SUMMARY STEPS

In the Navigation pane, click SAN .

On the SAN tab, click Storage Cloud .

Click FC Zone Profiles .

In the Work pane, select the zone profile.

Navigate to FC User Zones.

Right-click the name of the user zone you wish to delete.

Choose Delete and click Yes to confirm.

Fibre Channel Zoning

Cisco UCS Manager Storage Management Guide, Release 4.2

Fibre Channel Zoning

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click SAN .

On the SAN tab, click Storage Cloud .

Click FC Zone Profiles .

In the Work pane, select the zone profile.

Navigate to FC User Zones.

Right-click the name of the user zone you wish to delete.

Choose Delete and click Yes to confirm.

The user zone is deleted from the system.

Fibre Channel Storage Connection Policies

Deleting a Fibre Channel Storage Connection Policy

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > Policies > Organization_Name .

Expand the Storage Connection Policies node.

Right-click the policy you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click SAN .

Expand SAN > Policies > Organization_Name .

Expand the Storage Connection Policies node.

Right-click the policy you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

Fibre Channel Storage Connection Policies

Cisco UCS Manager Storage Management Guide, Release 4.2

Deleting a Fibre Channel Storage Connection Policy

Fibre Channel Zoning

Cisco UCS Manager Storage Management Guide, Release 4.2

C H A P T E R

Named VSANs

•

Named VSANs, on page 43

•

Fibre Channel Uplink Trunking for Named VSANs, on page 44

•

Guidelines and Recommendations for VSANs, on page 44

•

Creating a Named VSAN, on page 45

•

Creating a Storage VSAN, on page 46

•

Deleting a Named VSAN, on page 47

•

Changing the VLAN ID for the FCoE VLAN for a Storage VSAN, on page 48

•

Enabling Fibre Channel Uplink Trunking, on page 48

•

Disabling Fibre Channel Uplink Trunking, on page 49

Named VSANs

A named VSAN creates a connection to a specific external SAN. The VSAN isolates traffic to that external

SAN, including broadcast traffic. The traffic on one named VSAN knows that the traffic on another named

VSAN exists, but cannot read or access that traffic.

Like a named VLAN, the name that you assign to a VSAN ID adds a layer of abstraction that allows you to globally update all servers associated with service profiles that use the named VSAN. You do not need to reconfigure the servers individually to maintain communication with the external SAN. You can create more than one named VSAN with the same VSAN ID.

Named VSANs in Cluster Configurations

In a cluster configuration, a named VSAN can be configured to be accessible only to the Fibre Channel uplink ports on one fabric interconnect or to the Fibre Channel uplink ports on both fabric interconnects.

Named VSANs and the FCoE VLAN ID

You must configure each named VSAN with an FCoE VLAN ID. This property determines which VLAN is used for transporting the VSAN and its Fibre Channel packets.

For FIP-capable, converged network adapters, such as the Cisco UCS CNA M72KR-Q and the Cisco UCS

CNA M72KR-E, the named VSAN must be configured with a named VLAN that is not the native VLAN for the FCoE VLAN ID. This configuration ensures that FCoE traffic can pass through these adapters.

In the following sample configuration, a service profile with a vNIC and vHBA mapped to fabric A is associated with a server that has FIP capable, converged network adapters:

Cisco UCS Manager Storage Management Guide, Release 4.2

Named VSANs

Fibre Channel Uplink Trunking for Named VSANs

• The vNIC is configured to use VLAN 10.

• VLAN 10 is also designated as the native VLAN for the vNIC.

• The vHBA is configured to use VSAN 2.

• Therefore, VSAN 2 cannot be configured with VLAN 10 as the FCoE VLAN ID. VSAN 2 can be mapped to any other VLAN configured on fabric A.

Fibre Channel Uplink Trunking for Named VSANs

You can configure Fibre Channel uplink trunking for the named VSANs on each fabric interconnect. If you enable trunking on a fabric interconnect, all named VSANs in a Cisco UCS domain are allowed on all Fibre

Channel uplink ports on that fabric interconnect.

Guidelines and Recommendations for VSANs

The following guidelines and recommendations apply to all named VSANs, including storage VSANs.

VSAN 4079 is a Reserved VSAN ID

Do not configure a VSAN as 4079. This VSAN is reserved and cannot be used in either FC switch mode or

FC end-host mode.

If you create a named VSAN with ID 4079, Cisco UCS Manager marks that VSAN with an error and raises a fault.

Reserved VSAN Range for Named VSANs in FC Switch Mode

If you plan to use FC switch mode in a Cisco UCS domain, do not configure VSANs with an ID in the range from 3040 to 4078.

VSANs in that range are not operational if the fabric interconnects are configured to operate in FC switch mode. Cisco UCS Manager marks that VSAN with an error and raises a fault.

Reserved VSAN Range for Named VSANs in FC End-Host Mode

If you plan to use FC end-host mode in a Cisco UCS domain, do not configure VSANs with an ID in the range from 3840 to 4079.

VSANs in that range are not operational if the following conditions exist in a Cisco UCS domain:

• The fabric interconnects are configured to operate in FC end-host mode.

• The Cisco UCS domain is configured with Fibre Channel trunking or SAN port channels.

If these configurations exist, Cisco UCS Manager does the following:

Renders all VSANs with an ID in the range from 3840 to 4079 non-operational.

Raises a fault against the non-operational VSANs.

Transfers all non-operational VSANs to the default VSAN.

Cisco UCS Manager Storage Management Guide, Release 4.2

Named VSANs

Creating a Named VSAN

Transfers all vHBAs associated with the non-operational VSANs to the default VSAN.

If you disable Fibre Channel trunking and delete any existing SAN port channels, Cisco UCS Manager returns all VSANs in the range from 3840 to 4078 to an operational state and restores any associated vHBAs back to those VSANs.

Range Restrictions for Named VSAN IDs in FC Switch Mode

If you plan to use FC switch mode in a Cisco UCS domain, do not configure VSANs in the range from 3040 to 4078.

When a fabric interconnect operating in FC switch mode is connected to MDS as the upstream switch, VSANs configured in Cisco UCS Manager in the range from 3040 to 4078 and assigned as port VSANs cannot be created in MDS. This configuration results in a possible port VSAN mismatch.

Guidelines for FCoE VLAN IDs

VLAN 4048 is user configurable. However, Cisco UCS Manager uses VLAN 4048 for the following default values. If you want to assign 4048 to a VLAN, you must reconfigure these values:

• After an upgrade to Cisco UCS, Release 2.0—The FCoE storage port native VLAN uses VLAN 4048 by default. If the default FCoE VSAN was set to use VLAN 1 before the upgrade, you must change it to a VLAN ID that is not used or reserved. For example, consider changing the default to 4049 if that

VLAN ID is not in use.

• After a fresh install of Cisco UCS, Release 2.0—The FCoE VLAN for the default VSAN uses VLAN

4048 by default. The FCoE storage port native VLAN uses VLAN 4049.

Creating a Named VSAN

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud .

In the Work pane, click the VSANs tab.

On the icon bar to the right of the table, click + .

Cisco UCS Manager Storage Management Guide, Release 4.2

Named VSANs

Creating a Storage VSAN

In the Create VSAN dialog box, complete the required.

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud .

In the Work pane, click the VSANs tab.

On the icon bar to the right of the table, click + .

If the + icon is disabled, click an entry in the table to enable it.

In the Create VSAN dialog box, complete the required.

Click OK .

Cisco UCS Manager GUI adds the VSAN to one of the following VSANs nodes:

• The SAN Cloud > VSANs node for a storage VSAN accessible to both fabric interconnects.

• The SAN Cloud > Fabric_Name > VSANs node for a VSAN accessible to only one fabric interconnect.

Creating a Storage VSAN

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click SAN .

On the SAN tab, expand SAN > Storage Cloud .

In the Work pane, click the VSANs tab.

On the icon bar to the right of the table, click + .

If the + icon is disabled, click an entry in the table to enable it.

In the Create VSAN dialog box, complete the required fields.

Click OK .

Cisco UCS Manager GUI adds the VSAN to one of the following VSANs nodes:

• The Storage Cloud > VSANs node for a storage VSAN accessible to both fabric interconnects.

Cisco UCS Manager Storage Management Guide, Release 4.2

Named VSANs

Deleting a Named VSAN

• The Storage Cloud > Fabric_Name > VSANs node for a VSAN accessible to only one fabric interconnect.

Deleting a Named VSAN

If Cisco UCS Manager includes a named VSAN with the same VSAN ID as the one you delete, the VSAN is not removed from the fabric interconnect configuration until all named VSANs with that ID are deleted.

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, click the SAN node.

In the Work pane, click the VSANs tab.

Click one of the following subtabs, depending upon what type of VSAN you want to delete:

In the table, click the VSAN you want to delete.

Right-click the highlighted VSAN or VSANs and choose Delete .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click SAN .

In the SAN tab, click the SAN node.

In the Work pane, click the VSANs tab.

Click one of the following subtabs, depending upon what type of VSAN you want to delete:

Subtab Description

All Displays all VSANs in the Cisco UCS domain.

Displays the VSANs that are accessible to both fabric interconnects.

Dual Mode

Switch A

Switch B

Displays the VSANs that are accessible to only fabric interconnect A.

Displays the VSANs that are accessible to only fabric interconnect B.

In the table, click the VSAN you want to delete.

You can use the Shift key or Ctrl key to select multiple entries.

Right-click the highlighted VSAN or VSANs and choose Delete .

If a confirmation dialog box displays, click Yes .

Cisco UCS Manager Storage Management Guide, Release 4.2

Named VSANs

Changing the VLAN ID for the FCoE VLAN for a Storage VSAN

Caution Changing the VLAN ID of the FCoE VLAN for a storage VSAN causes an brief traffic outage. FCoE VLANs in the SAN cloud and VLANs in the LAN cloud must have different IDs. Using the same ID for an FCoE

VLAN in a VSAN results in a critical fault and traffic disrupt for all NICs and uplink ports using that FCoE

VLAN. Ethernet traffic drops on any VLAN with an ID that overlaps with an FCoE VLAN ID.

Changing the FCoE VLAN for the default VSAN or any configured VSAN under a global policy may result in storage disconnect or complete shut down.

SUMMARY STEPS

In the Navigation pane, click SAN .

On the SAN tab, expand SAN > Storage Cloud > VSANs .

Choose the VSAN for which you want to modify the FCoE VLAN ID.

In the Work pane, click the General tab.

In the FCoE VLAN field, enter the desired VLAN ID.

Click Save Changes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click SAN .

On the SAN tab, expand SAN > Storage Cloud > VSANs .

Choose the VSAN for which you want to modify the FCoE VLAN ID.

In the Work pane, click the General tab.

In the FCoE VLAN field, enter the desired VLAN ID.

Click Save Changes .

Enabling Fibre Channel Uplink Trunking

Note If the fabric interconnects are configured for Fibre Channel end-host mode, enabling Fibre Channel uplink trunking renders all VSANs with an ID in the range from 3840 to 4079 non-operational.

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud .

Click the node for the fabric where you want to enable FC uplink trunking.

Cisco UCS Manager Storage Management Guide, Release 4.2

Named VSANs

Disabling Fibre Channel Uplink Trunking

In the Work pane, click the General tab.

In the Actions area, click Enable FC Uplink Trunking .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud .

Click the node for the fabric where you want to enable FC uplink trunking.

In the Work pane, click the General tab.

In the Actions area, click Enable FC Uplink Trunking .

If a confirmation dialog box displays, click Yes .

Disabling Fibre Channel Uplink Trunking

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud .

Click the node for the fabric where you want to disable Fibre Channel uplink trunking.

In the Work pane, click the General tab.

In the Actions area, click Disable FC Uplink Trunking .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click SAN .

Expand SAN > SAN Cloud .

Click the node for the fabric where you want to disable Fibre Channel uplink trunking.

In the Work pane, click the General tab.

In the Actions area, click Disable FC Uplink Trunking .

If a confirmation dialog box displays, click Yes .

Cisco UCS Manager Storage Management Guide, Release 4.2

Disabling Fibre Channel Uplink Trunking

Named VSANs

Cisco UCS Manager Storage Management Guide, Release 4.2

C H A P T E R

SAN Pin Groups

•

SAN Pin Groups, on page 51

SAN Pin Groups

Cisco UCS uses SAN pin groups to pin Fibre Channel traffic from a vHBA on a server to an uplink Fibre

Channel port on the fabric interconnect. You can use this pinning to manage the distribution of traffic from the servers.

Note In Fibre Channel switch mode, SAN pin groups are irrelevant. Any existing SAN pin groups will be ignored.

To configure pinning for a server, you must include the SAN pin group in a vHBA policy. The vHBA policy is then included in the service profile assigned to that server. All traffic from the vHBA will travel through the I/O module to the specified uplink Fibre Channel port.

You can assign the same pin group to multiple vHBA policies. As a result, you do not need to manually pin the traffic for each vHBA.

Important Changing the target interface for an existing SAN pin group disrupts traffic for all vHBAs which use that pin group. The fabric interconnect performs a log in and log out for the Fibre Channel protocols to re-pin the traffic.

Creating a SAN Pin Group

In a system with two fabric interconnects, you can associate the pin group with only one fabric interconnect or with both fabric interconnects.

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > SAN Cloud .

Right-click SAN Pin Groups and select Create SAN Pin Group .

Enter a unique name and description for the pin group.

Cisco UCS Manager Storage Management Guide, Release 4.2

SAN Pin Groups

Deleting a SAN Pin Group

To pin traffic for fabric interconnect A, do the following in the Targets area:

To pin traffic for fabric interconnect B, do the following in the Targets area:

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > SAN Cloud .

Right-click SAN Pin Groups and select Create SAN Pin Group .

Enter a unique name and description for the pin group.

To pin traffic for fabric interconnect A, do the following in the Targets area: a) Check the Fabric A check box.

b) Click the drop-down arrow on the Interface field and navigate through the tree-style browser to select the uplink

Fibre Channel port you want to associate with the pin group.

To pin traffic for fabric interconnect B, do the following in the Targets area: a) Check the Fabric B check box.

b) Click the drop-down arrow on the Interface field and navigate through the tree-style browser to select the uplink

Fibre Channel port you want to associate with the pin group.

Click OK .

What to do next

Include the pin group in a vHBA template.

Deleting a SAN Pin Group

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > SAN Cloud > SAN Pin Groups .

Right-click the SAN pin group you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > SAN Cloud > SAN Pin Groups .

Right-click the SAN pin group you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

Cisco UCS Manager Storage Management Guide, Release 4.2

C H A P T E R

FC Identity Assignment

•

Fibre Channel Identity, on page 53

Fibre Channel Identity

A Fibre Channel node and port must have a globally unique World Wide Number (WWN). In Cisco UCS

WWNs are created as identity pools. A Fibre Channel node (a whole server, storage array) must have a World

Wide Node Name (WWNN) and a Fibre Channel port must have a World Wide Port Name (WWPN). Both

WWNNs and WWPNs are physical entities; hence, they have a 64-bit address.

The WWNN pool is created as one large pool for the Cisco UCS domain. You can use the default pool in the

Cisco UCS Manager SAN tab. However, it is recommended to create a custom WWNN pool for that UCS domain.

A communicating device is a node. A host bus adapter in a server constitutes a Fibre Channel node. For servers and hosts, WWNN is unique foe each host bus adapter (HBA). For a SAN switch, the WWNN is common for the chassis. For midrange storage, the WWNN is common for each controller unit. For enterprise storage, the WWNN is unique for the entire array.

Each server has a unique WWPN for each port of the HBA. For a SAN switch, the WWPN is available for each port in the chassis. For storage, each port has an individual.

The FC Identity Tab in Cisco UCS Manager displays the FC Identity of the devices in the Cisco UCS domain

SAN cloud, including the:

• Selected device WWNN or WWPN identifier.

• Whether the identifier is assigned ti a vHBA.

• vHBA to which the identifier is assigned.

Cisco UCS Manager Storage Management Guide, Release 4.2

Fibre Channel Identity

FC Identity Assignment

Cisco UCS Manager Storage Management Guide, Release 4.2

C H A P T E R

WWN Pools

•

WWN Pools, on page 55

•

WWPN Pools, on page 61

•

WWxN Pools, on page 67

WWN Pools

A World Wide Name (WWN) pool is a collection of WWNs for use by the Fibre Channel vHBAs in a Cisco

UCS domain. You create separate pools for the following:

• WW node names assigned to the vHBA

• WW port names assigned to the vHBA

• Both WW node names and WW port names

Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to

20:FF:00:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:00:FF:FF:FF:FF:FF. All other WWN ranges are reserved. When fibre channel traffic is sent through the Cisco UCS infrastructure, the source WWPN is converted to a MAC address. You cannot use WWPN pool which can translate to a source multicast MAC address. To ensure the uniqueness of the Cisco UCS WWNNs and WWPNs in the SAN fabric, Cisco recommends using the following WWN prefix for all blocks in a pool: 20:00:00:25:B5:XX:XX:XX

If you use WWN pools in service profiles, you do not have to manually configure the WWNs that will be used by the server associated with the service profile. In a system that implements multi-tenancy, you can use a WWN pool to control the WWNs used by each organization.

You assign WWNs to pools in blocks.

WWNN Pools

A WWNN pool is a WWN pool that contains only WW node names. If you include a pool of WWNNs in a service profile, the associated server is assigned a WWNN from that pool.

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

Creating a WWNN Pool

WWPN Pools

A WWPN pool is a WWN pool that contains only WW port names. If you include a pool of WWPNs in a service profile, the port on each vHBA of the associated server is assigned a WWPN from that pool.

WWxN Pools

A WWxN pool is a WWN pool that contains both WW node names and WW port names. You can specify how many ports per node are created with WWxN pools. The pool size must be a multiple of ports-per-node

+ 1. For example, if you specify 7 ports per node, the pool size must be a multiple of 8. If you specify 63 ports per node, the pool size must be a multiple of 64.

You can use a WWxN pool whenever you select a WWNN or WWPN pool. The WWxN pool must be created before it can be assigned.

• For WWNN pools, the WWxN pool is displayed as an option in the WWNN Assignment drop-down list.

• For WWPN pools, choose Derived in the WWPN Assignment drop-down list.

Creating a WWNN Pool

Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools .

Expand the node for the organization where you want to create the pool.

Right-click WWNN Pools and select Create WWNN Pool .

In the Define Name and Description dialog box of the Create WWNN Pool wizard, complete the following fields:

Click Next .

In the Add WWN Blocks page of the Create WWNN Pool wizard, click Add .

In the Create WWN Block dialog box, complete the following fields:

Click OK .

10.

Click Finish .

DETAILED STEPS

Step 1

Step 2

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools .

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

Creating a WWNN Pool

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

Expand the node for the organization where you want to create the pool.

If the system does not include multi tenancy, expand the root node.

Right-click WWNN Pools and select Create WWNN Pool .

In the Define Name and Description dialog box of the Create WWNN Pool wizard, complete the following fields:

Name

Name field

Description

The name of the World Wide Node Name pool.

Description field

Assignment Order field

A description of the pool.

Enter up to 256 characters. You can use any characters or spaces except `

(accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign), >

(greater than), < (less than), or ' (single quote).

This can be one of the following:

• Default —Cisco UCS Manager selects a random identity from the pool.

• Sequential —Cisco UCS Manager selects the lowest available identity from the pool.

Click Next .

In the Add WWN Blocks page of the Create WWNN Pool wizard, click Add .

In the Create WWN Block dialog box, complete the following fields:

Name

From

Size field field

Description

The first WWN in the block.

The number of WWNs in the block.

For WWxN pools, the pool size must be a multiple of ports-per-node + 1. For example, if there are 7 ports per node, the pool size must be a multiple of 8.

If there are 63 ports per node, the pool size must be a multiple of 64.

Click OK .

Click Finish .

What to do next

Include the WWNN pool in a service profile and template.

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

Adding a WWN Block to a WWNN Pool

Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWNN Pools node.

Right-click the WWNN pool to which you want to add a WWN block and select Create WWN Block .

In the Create WWN Block dialog box, complete the following fields:

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWNN Pools node.

Right-click the WWNN pool to which you want to add a WWN block and select Create WWN Block .

In the Create WWN Block dialog box, complete the following fields:

Name

From field

Description

The first WWN in the block.

Size field The number of WWNs in the block.

For WWxN pools, the pool size must be a multiple of ports-per-node + 1. For example, if there are 7 ports per node, the pool size must be a multiple of 8. If there are 63 ports per node, the pool size must be a multiple of 64.

Click OK .

Deleting a WWN Block from a WWNN Pool

If you delete an address block from a pool, Cisco UCS Manager does not reallocate any addresses in that block that were assigned to vNICs or vHBAs. All assigned addresses from a deleted block remain with the vNIC or vHBA to which they are assigned until one of the following occurs:

• The associated service profiles are deleted.

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

Adding a WWNN Initiator to a WWNN Pool

• The vNIC or vHBA to which the address is assigned is deleted.

• The vNIC or vHBA is assigned to a different pool.

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name > WWNN Pools > WWNN_Pool_Name

Right-click the WWN block that you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name > WWNN Pools > WWNN_Pool_Name .

Right-click the WWN block that you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

Adding a WWNN Initiator to a WWNN Pool

Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWNN Pools node.

Right-click the WWNN pool to which you want to add a WWNN initiator and select Create WWNN

Initiator .

In the Create WWNN Initiator dialog box, complete the following fields:

Click OK .

DETAILED STEPS

Step 1

Step 2

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

Deleting a WWPN Initiator from a WWPN Pool

Step 3

Step 4

Step 5

Step 6

Expand the WWNN Pools node.

Right-click the WWNN pool to which you want to add a WWNN initiator and select Create WWNN Initiator .

In the Create WWNN Initiator dialog box, complete the following fields:

Name

World Wide Name field

Description

The WWN.

Name field

Description field

The name of the WWNN initiator.

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.

A user-defined description of the WWNN initiator.

Enter up to 256 characters. You can use any characters or spaces except ` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign), > (greater than),

< (less than), or ' (single quote).

Click OK .

Deleting a WWPN Initiator from a WWPN Pool

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWPN Pools node.

Choose the WWPN pool from which you want to delete a WWPN initiator.

In the Work pane, click the Initiators tab.

Right-click the initiator that you want to delete and choose Delete .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWPN Pools node.

Choose the WWPN pool from which you want to delete a WWPN initiator.

In the Work pane, click the Initiators tab.

Right-click the initiator that you want to delete and choose Delete .

If a confirmation dialog box displays, click Yes .

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

Deleting a WWNN Pool

If you delete a pool, Cisco UCS Manager does not reallocate any addresses from that pool that were assigned to vNICs or vHBAs. All assigned addresses from a deleted pool remain with the vNIC or vHBA to which they are assigned until one of the following occurs:

• The associated service profiles are deleted.

• The vNIC or vHBA to which the address is assigned is deleted.

• The vNIC or vHBA is assigned to a different pool.

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWNN Pools node.

Right-click the WWNN pool you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWNN Pools node.

Right-click the WWNN pool you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

WWPN Pools

Creating a WWPN Pool

Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to

SUMMARY STEPS

In the Navigation pane, click SAN .

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

Creating a WWPN Pool

In the SAN tab, expand SAN > Pools .

Expand the node for the organization where you want to create the pool.

Right-click WWPN Pools and select Create WWPN Pool .

In the Define Name and Description page of the Create WWPN Pool wizard, complete the following fields:

Click Next .

In the Add WWN Blocks page of the Create WWPN Pool wizard, click Add .

In the Create WWN Block dialog box, complete the following fields:

Click OK .

10.

Click Finish .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools .

Expand the node for the organization where you want to create the pool.

If the system does not include multi tenancy, expand the root node.

Right-click WWPN Pools and select Create WWPN Pool .

In the Define Name and Description page of the Create WWPN Pool wizard, complete the following fields:

Name

Name field

Description field

Description

The name of the World Wide Port Name pool.

A description of the pool.

Enter up to 256 characters. You can use any characters or spaces except `

(accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign), >

(greater than), < (less than), or ' (single quote).

Assignment Order field This can be one of the following:

• Default —Cisco UCS Manager selects a random identity from the pool.

• Sequential —Cisco UCS Manager selects the lowest available identity from the pool.

Click Next .

In the Add WWN Blocks page of the Create WWPN Pool wizard, click Add .

In the Create WWN Block dialog box, complete the following fields:

Name

From field

Description

The first WWN in the block.

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

Adding a WWN Block to a WWPN Pool

Name

Size field

Description

The number of WWNs in the block.

For WWxN pools, the pool size must be a multiple of ports-per-node + 1. For example, if there are 7 ports per node, the pool size must be a multiple of 8.

If there are 63 ports per node, the pool size must be a multiple of 64.

Step 9

Step 10

Click OK .

Click Finish .

What to do next

Include the WWPN pool in a vHBA template.

Adding a WWN Block to a WWPN Pool

Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWPN Pools node.

Right-click the WWPN pool to which you want to add a WWN block and select Create WWN Block .

In the Create WWN Block dialog box, complete the following fields:

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWPN Pools node.

Right-click the WWPN pool to which you want to add a WWN block and select Create WWN Block .

In the Create WWN Block dialog box, complete the following fields:

Name

From field

Description

The first WWN in the block.

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

Deleting a WWN Block from a WWPN Pool

Name

Size field

Description

The number of WWNs in the block.

Step 6 Click OK .

Deleting a WWN Block from a WWPN Pool

• The associated service profiles are deleted.

• The vNIC or vHBA to which the address is assigned is deleted.

• The vNIC or vHBA is assigned to a different pool.

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name > WWPN Pools > WWPN_Pool_Name

Right-click the WWN block that you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name > WWPN Pools > WWPN_Pool_Name .

Right-click the WWN block that you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

Adding a WWPN Initiator to a WWPN Pool

Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWPN Pools node.

Right-click the WWPN pool to which you want to add a WWPN initiator and select Create WWPN

Initiator .

In the Create WWPN Initiator dialog box, complete the following fields:

If you want to add a SAN boot target, expand the Boot Target area and complete the following fields:

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWPN Pools node.

Right-click the WWPN pool to which you want to add a WWPN initiator and select Create WWPN Initiator .

In the Create WWPN Initiator dialog box, complete the following fields:

Name

World Wide Name field

Description

The WWN.

Name field

Description field

The name of the WWPN initiator.

A user-defined description of the WWPN initiator.

Enter up to 256 characters. You can use any characters or spaces except ` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign), > (greater than),

< (less than), or ' (single quote).

If you want to add a SAN boot target, expand the Boot Target area and complete the following fields:

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

Deleting a WWPN Initiator from a WWPN Pool

Step 7

Name

Boot Target WWPN field

Boot Target LUN field

Click OK .

Description

The WWPN that corresponds to the location of the boot image.

The LUN that corresponds to the location of the boot image.

Deleting a WWPN Initiator from a WWPN Pool

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWPN Pools node.

Choose the WWPN pool from which you want to delete a WWPN initiator.

In the Work pane, click the Initiators tab.

Right-click the initiator that you want to delete and choose Delete .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWPN Pools node.

Choose the WWPN pool from which you want to delete a WWPN initiator.

In the Work pane, click the Initiators tab.

Right-click the initiator that you want to delete and choose Delete .

If a confirmation dialog box displays, click Yes .

Deleting a WWPN Pool

• The associated service profiles are deleted.

• The vNIC or vHBA to which the address is assigned is deleted.

• The vNIC or vHBA is assigned to a different pool.

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

WWxN Pools

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWPN Pools node.

Right-click the WWPN pool you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWPN Pools node.

Right-click the WWPN pool you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

WWxN Pools

Creating a WWxN Pool

Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools .

Expand the node for the organization where you want to create the pool.

Right-click WWxN Pools and select Create WWxN Pool .

In the Define Name and Description page of the Create WWxN Pool wizard, complete the following fields:

Click Next .

In the Add WWN Blocks page of the Create WWxN Pool wizard, click Add .

In the Create WWN Block dialog box, complete the following fields:

Click OK .

10.

Click Finish .

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

Creating a WWxN Pool

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools .

Expand the node for the organization where you want to create the pool.

If the system does not include multi tenancy, expand the root node.

Right-click WWxN Pools and select Create WWxN Pool .

In the Define Name and Description page of the Create WWxN Pool wizard, complete the following fields:

Name

Name field

Description

The name of the World Wide Port Name pool.

Description field

Max Ports per Node field

A description of the pool.

Enter up to 256 characters. You can use any characters or spaces except `

(accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign), >

(greater than), < (less than), or ' (single quote).

The maximum number of ports that can be assigned to each node name in this pool.

You cannot change this value once the object has been saved.

Assignment Order field This can be one of the following:

• Default —Cisco UCS Manager selects a random identity from the pool.

• Sequential —Cisco UCS Manager selects the lowest available identity from the pool.

Click Next .

In the Add WWN Blocks page of the Create WWxN Pool wizard, click Add .

In the Create WWN Block dialog box, complete the following fields:

Name

From

Size field field

Description

The first WWN in the block.

The number of WWNs in the block.

For WWxN pools, the pool size must be a multiple of ports-per-node + 1. For example, if there are 7 ports per node, the pool size must be a multiple of 8.

If there are 63 ports per node, the pool size must be a multiple of 64.

Click OK .

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

Adding a WWN Block to a WWxN Pool

Step 10 Click Finish .

What to do next

Include the WWxN pool in a service profile and template.

Adding a WWN Block to a WWxN Pool

Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWxN Pools node.

Right-click the WWxN pool to which you want to add a WWN block and select Create WWN Block .

In the Create WWN Block dialog box, complete the following fields:

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWxN Pools node.

Right-click the WWxN pool to which you want to add a WWN block and select Create WWN Block .

In the Create WWN Block dialog box, complete the following fields:

Name

From field

Description

The first WWN in the block.

Size field The number of WWNs in the block.

Click OK .

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

Deleting a WWN Block from a WWxN Pool

• The associated service profiles are deleted.

• The vNIC or vHBA to which the address is assigned is deleted.

• The vNIC or vHBA is assigned to a different pool.

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name > WWxN Pools > WWxN_Pool_Name

Right-click the WWN block that you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name > WWxN Pools > WWxN_Pool_Name .

Right-click the WWN block that you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

Deleting a WWxN Pool

• The associated service profiles are deleted.

• The vNIC or vHBA to which the address is assigned is deleted.

• The vNIC or vHBA is assigned to a different pool.

SUMMARY STEPS

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWxN Pools node.

Right-click the WWxN pool you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

Cisco UCS Manager Storage Management Guide, Release 4.2

WWN Pools

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click SAN .

In the SAN tab, expand SAN > Pools > Organization_Name .

Expand the WWxN Pools node.

Right-click the WWxN pool you want to delete and select Delete .

If a confirmation dialog box displays, click Yes .

Deleting a WWxN Pool

Cisco UCS Manager Storage Management Guide, Release 4.2

Deleting a WWxN Pool

WWN Pools

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

C H A P T E R

•

About vHBA Templates, on page 73

•

Fibre Channel Adapter Policies, on page 77

•

About the Default vHBA Behavior Policy, on page 86

•

SPDM Security Policy, on page 87

•

SAN Connectivity Policies, on page 90

About vHBA Templates vHBA Template

This template is a policy that defines how a vHBA on a server connects to the SAN. It is also referred to as a vHBA SAN connectivity template.

You must include this policy in a service profile for it to take effect.

Creating a vHBA Template

Before you begin

This policy requires that one or more of the following resources already exist in the system:

• Named VSAN

• WWNN pool or WWPN pool

• SAN pin group

• Statistics threshold policy

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > Policies .

Expand the node for the organization where you want to create the policy.

Right-click the vHBA Templates node and choose Create vHBA Template .

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Creating a vHBA Template

In the Create vHBA Template dialog box, complete the following fields:

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click SAN .

Expand SAN > Policies .

Expand the node for the organization where you want to create the policy.

If the system does not include multi tenancy, expand the root node.

Right-click the vHBA Templates node and choose Create vHBA Template .

In the Create vHBA Template dialog box, complete the following fields:

Name

Name field

Description

The name of the virtual HBA template.

Description field A user-defined description of the template.

Enter up to 256 characters. You can use any characters or spaces except ` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign), > (greater than),

< (less than), or ' (single quote).

Fabric ID field

Select VSAN drop-down list

The name of the fabric interconnect that vHBAs created with this template are associated with.

The VSAN to associate with vHBAs created from this template.

Create VSAN link

Template Type field

Click this link if you want to create a VSAN.

This can be one of the following:

• Initial Template —vHBAs created from this template are not updated if the template changes.

• Updating Template —vHBAs created from this template are updated if the template changes.

Max Data Field Size field

WWPN Pool

QoS Policy

Pin Group drop-down list drop-down list drop-down list

The maximum size of the Fibre Channel frame payload bytes that the vHBA supports.

Enter an integer between 256 and 2112. The default is 2048.

The WWPN pool that a vHBA created from this template uses to derive its

WWPN address.

The QoS policy that is associated with vHBAs created from this template.

The SAN pin group that is associated with vHBAs created from this template.

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Binding a vHBA to a vHBA Template

Step 6

Name Description

Stats Threshold Policy drop-down list The statistics collection policy that is associated with vHBAs created from this template.

Click OK .

What to do next

Include the vHBA template in a service profile.

Binding a vHBA to a vHBA Template

You can bind a vHBA associated with a service profile to a vHBA template. When you bind the vHBA to a vHBA template, Cisco UCS Manager configures the vHBA with the values defined in the vHBA template.

If the existing vHBA configuration does not match the vHBA template, Cisco UCS Manager reconfigures the vHBA. You can only change the configuration of a bound vHBA through the associated vHBA template.

You cannot bind a vHBA to a vHBA template if the service profile that includes the vHBA is already bound to a service profile template.

Important If the vHBA is reconfigured when you bind it to a template, Cisco UCS Manager reboots the server associated with the service profile.

SUMMARY STEPS

In the Navigation pane, click Servers .

Expand Servers > Service Profiles .

Expand the node for the organization that includes the service profile with the vHBA you want to bind.

Expand Service_Profile_Name > vHBAs .

Click the vHBA you want to bind to a template.

In the Work pane, click the General tab.

In the Actions area, click Bind to a Template .

In the Bind to a vHBA Template dialog box, do the following:

In the warning dialog box, click Yes to acknowledge that Cisco UCS Manager may need to reboot the server if the binding causes the vHBA to be reconfigured.

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

In the Navigation pane, click Servers .

Expand Servers > Service Profiles .

Expand the node for the organization that includes the service profile with the vHBA you want to bind.

If the system does not include multi-tenancy, expand the root node.

Expand Service_Profile_Name > vHBAs .

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Unbinding a vHBA from a vHBA Template

Step 5

Step 6

Step 7

Step 8

Step 9

Click the vHBA you want to bind to a template.

In the Work pane, click the General tab.

In the Actions area, click Bind to a Template .

In the Bind to a vHBA Template dialog box, do the following: a) From the vHBA Template drop-down list, choose the template to which you want to bind the vHBA.

b) Click OK .

In the warning dialog box, click Yes to acknowledge that Cisco UCS Manager may need to reboot the server if the binding causes the vHBA to be reconfigured.

Unbinding a vHBA from a vHBA Template

SUMMARY STEPS

In the Navigation pane, click Servers .

Expand Servers > Service Profiles .

Expand the node for the organization that includes the service profile with the vHBA you want to unbind.

Expand Service_Profile_Name > vHBAs .

Click the vHBA you want to unbind from a template.

In the Work pane, click the General tab.

In the Actions area, click Unbind from a Template .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

In the Navigation pane, click Servers .

Expand Servers > Service Profiles .

Expand the node for the organization that includes the service profile with the vHBA you want to unbind.

If the system does not include multi-tenancy, expand the root node.

Expand Service_Profile_Name > vHBAs .

Click the vHBA you want to unbind from a template.

In the Work pane, click the General tab.

In the Actions area, click Unbind from a Template .

If a confirmation dialog box displays, click Yes .

Deleting a vHBA Template

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > Policies > Organization_Name .

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Fibre Channel Adapter Policies

Expand the vHBA Templates node.

Right-click the vHBA template that you want to delete and choose Delete .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click SAN .

Expand SAN > Policies > Organization_Name .

Expand the vHBA Templates node.

Right-click the vHBA template that you want to delete and choose Delete .

If a confirmation dialog box displays, click Yes .

Fibre Channel Adapter Policies

Ethernet and Fibre Channel Adapter Policies

These policies govern the host-side behavior of the adapter, including how the adapter handles traffic. For example, you can use these policies to change default settings for the following:

• Queues

• Interrupt handling

• Performance enhancement

• RSS hash

• Failover in a cluster configuration with two fabric interconnects

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Ethernet and Fibre Channel Adapter Policies

Note For Fibre Channel adapter policies, the values displayed by Cisco UCS Manager may not match those displayed by applications such as QLogic SANsurfer. For example, the following values may result in an apparent mismatch between SANsurfer and Cisco UCS Manager:

• Max LUNs Per Target—SANsurfer has a maximum of 256 LUNs and does not display more than that number. Cisco UCS Manager supports a higher maximum number of LUNs. This parameter is applicable only for FC-Initiator.

• Link Down Timeout—In SANsurfer, you configure the timeout threshold for link down in seconds. In

Cisco UCS Manager, you configure this value in milliseconds. Therefore, a value of 5500 ms in Cisco

UCS Manager displays as 5s in SANsurfer.

• Max Data Field Size—SANsurfer has allowed values of 512, 1024, and 2048. Cisco UCS Manager allows you to set values of any size. Therefore, a value of 900 in Cisco UCS Manager displays as 512 in SANsurfer.

• LUN Queue Depth—The LUN queue depth setting is available for Windows system FC adapter policies.

Queue depth is the number of commands that the HBA can send and receive in a single transmission per

LUN. Windows Storport driver sets this to a default value of 20 for physical miniports and to 250 for virtual miniports. This setting adjusts the initial queue depth for all LUNs on the adapter. Valid range for this value is 1 - 254. The default LUN queue depth is 20. This feature only works with Cisco UCS

Manager version 3.1(2) and higher. This parameter is applicable only for FC-Initiator.

• IO TimeOut Retry—When the target device does not respond to an IO request within the specified timeout, the FC adapter cancels the pending command then resends the same IO after the timer expires.

The FC adapter valid range for this value is 1 - 59 seconds. The default IO retry timeout is 5 seconds.

This feature only works with Cisco UCS Manager version 3.1(2) and higher.

Operating System Specific Adapter Policies

By default, Cisco UCS provides a set of Ethernet adapter policies and Fibre Channel adapter policies. These policies include the recommended settings for each supported server operating system. Operating systems are sensitive to the settings in these policies. Storage vendors typically require non-default adapter settings. You can find the details of these required settings on the support list provided by those vendors.

Important We recommend that you use the values in these policies for the applicable operating system. Do not modify any of the values in the default policies unless directed to do so by Cisco Technical Support.

However, if you are creating an Ethernet adapter policy for an OS (instead of using the default adapter policy), you must use the following formulas to calculate values that work for that OS.

Depending on the UCS firmware, your driver interrupt calculations may be different. Newer UCS firmware uses a calculation that differs from previous versions. Later driver release versions on Linux operating systems now use a different formula to calculate the Interrupt Count. In this formula, the Interrupt Count is the maximum of either the Transmit Queue or the Receive Queue plus 2.

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Ethernet and Fibre Channel Adapter Policies

Interrupt Count in Linux Adapter Policies

Drivers on Linux operating systems use differing formulas to calculate the Interrupt Count, depending on the eNIC driver version. The UCS 3.2 release increased the number of Tx and Rx queues for the eNIC driver from 8 to 256 each.

Use one of the following strategies, according to your driver version.

For Linux drivers before the UCS 3.2 firmware release, use the following formula to calculate the Interrupt

Count.

Completion Queues = Transmit Queues + Receive Queues

Interrupt Count = (Completion Queues + 2) rounded up to nearest power of 2

For example, if Transmit Queues = 1 and Receive Queues = 8 then:

Completion Queues = 1 + 8 = 9

Interrupt Count = (9 + 2) rounded up to the nearest power of 2 = 16

On drivers for UCS firmware release 3.2 and higher, the Linux eNIC drivers use the following formula to calculate the Interrupt Count.

Interrupt Count = (#Tx or Rx Queues) + 2

For example:

Interrupt Count wq = 32, rq = 32, cq = 64 - then Interrupt Count = Max(32, 32) + 2 = 34

Interrupt Count wq = 64, rq = 8, cq = 72 – then Interrupt Count = Max(64, 8) + 2 = 66

Interrupt Count wq = 1, rq = 16, cq = 17 - then Interrupt count = Max(1, 16) + 2 = 18

Interrupt Count in Windows Adapter Policies

For Windows OS, the recommended adapter policy in UCS Manager for VIC1400 series adapters is Win-HPN and if RDMA is used, the recommended policy is Win-HPN-SMB. For VIC 1400 series adapters, the recommended interrupt value setting is 512 and the Windows VIC driver takes care of allocating the required number of Interrupts.

For VIC 1300 and VIC 1200 series adapters, the recommended UCS Manager adapter policy is Windows and the Interrupt would be TX + RX + 2, rounded to closest power of 2. The maximum supported Windows queues is 8 for Rx Queues and 1 for Tx Queues.

Example for VIC 1200 and VIC 1300 series adapters:

Tx = 1, Rx = 4, CQ = 5, Interrupt = 8 ( 1 + 4 rounded to nearest power of 2), Enable RSS

Example for VIC 1400 series adapters:

Tx = 1, Rx = 4, CQ = 5, Interrupt = 512 , Enable RSS

NVMe over Fabrics using Fibre Channel

The NVM Express (NVMe) interface allows host software to communicate with a non-volatile memory subsystem. This interface is optimized for Enterprise non-volatile storage, which is typically attached as a register level interface to the PCI Express (PCIe) interface.

NVMe over Fabrics using Fibre Channel (FC-NVMe) defines a mapping protocol for applying the NVMe interface to Fibre Channel. This protocol defines how Fibre Channel services and specified Information Units

(IUs) are used to perform the services defined by NVMe over a Fibre Channel fabric. NVMe initiators can access and transfer information to NVMe targets over Fibre Channel.

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Creating a Fibre Channel Adapter Policy

FC-NVMe combines the advantages of Fibre Channel and NVMe. You get the improved performance of

NVMe along with the flexibility and the scalability of the shared storage architecture. Cisco UCS Manager

Release 4.0(2) supports NVMe over Fabrics using Fibre Channel on UCS VIC 14xx adapters.

Cisco UCS Manager provides the recommended FcNVMe adapter policies in the list of pre-configured adapter policies. To create a new FcNVMe adapter policy, follow the steps in the Creating a Fibre Channel Adapter

Policy section.

NVMe over Fabrics Using RDMA

NVMe over Fabrics (NVMeoF) is a communication protocol that allows one computer to access NVMe namespaces available on another computer. NVMeoF is similar to NVMe, but differs in the network-related steps involved in using the NVMeoF storage devices. The commands for discovering, connecting, and disconnecting a NVMeoF storage device are integrated into the nvme utility provided in Linux..

The NVMeoF fabric that Cisco supports is RDMA over Converged Ethernet version 2 (RoCEv2). RoCEv2 is a fabric protocol that runs over UDP. It requires a no-drop policy.

The eNIC RDMA driver works in conjunction with the eNIC driver, which must be loaded first when configuring NVMeoF.

Cisco UCS Manager provides the default Linux-NVMe-RoCE adapter policy for creating NVMe RoCEv2 interfaces. Do not use the default Linux adapter policy. For complete information on configuring RoCEv2 over NVMeoF, refer to the Cisco UCS Manager Configuration Guide for RDMA over Converged Ethernet

(RoCE) v2 .

NVMeoF using RDMA is supported on M5 B-Series or C-Series Servers with Cisco UCS VIC 1400 Series adapters.

Creating a Fibre Channel Adapter Policy

SUMMARY STEPS

Tip If the fields in an area do not display, click the Expand icon to the right of the heading.

In the Navigation pane, click Servers .

Expand Servers > Policies .

Expand the node for the organization where you want to create the policy.

Right-click Adapter Policies and choose Create Fibre Channel Adapter Policy .

Enter a name and description for the policy in the following fields:

(Optional) In the Resources area, adjust the following values:

(Optional) In the Options area, adjust the following values:

Click OK .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1 In the Navigation pane, click Servers .

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Creating a Fibre Channel Adapter Policy

Step 2

Step 3

Step 4

Step 5

Step 6

Expand Servers > Policies .

Expand the node for the organization where you want to create the policy.

If the system does not include multi tenancy, expand the root node.

Right-click Adapter Policies and choose Create Fibre Channel Adapter Policy .

Enter a name and description for the policy in the following fields:

Table 4:

Name

Name field

Description field

Description

The name of the policy.

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.

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

Enter up to 256 characters. You can use any characters or spaces except `

(accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign), >

(greater than), < (less than), or ' (single quote).

(Optional) In the Resources area, adjust the following values:

Name

Transmit Queues field

Description

The number of transmit queue resources to allocate.

This value cannot be changed.

Ring Size field

Receive Queues field

The number of descriptors in each transmit queue. This parameter applies to

Extended Link Services (ELS) and Common Transport (CT) fibre channel frames for generic services. It does not affect adapter performance.

Enter an integer between 64 and 128. The default is 64.

The number of receive queue resources to allocate.

This value cannot be changed.

Ring Size field

I/O Queues field

The number of descriptors in each receive queue. This parameter applies to

Extended Link Services (ELS) and Common Transport (CT) fibre channel frames for generic services. It does not affect adapter performance.

Enter an integer between 64 and 2048. The default is 64.

The number of IO queue resources the system should allocate.

Enter an integer between 1 and 64. The default is 16.

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Creating a Fibre Channel Adapter Policy

Name

Ring Size field

Description

The number of descriptors in each I/O queue.

Enter an integer between 64 and 512. The default is 512.

Note The number of descriptors can affect the performance of the adapter, so we recommend that you do not change the default value.

Step 7 (Optional) In the Options area, adjust the following values:

Name

FCP Error Recovery field

Description

Whether the system uses FCP Sequence Level Error Recovery (FC-TAPE) protocol for sequence level error recovery with tape devices. This enables or disables the Read Exchange Concise (REC) and Sequence Retransmission

Request (SRR) functions on the VIC firmware. This can be one of the following:

• Disabled —This is the default.

• Enabled —You should select this option if your system is connected to one or more tape drive libraries.

Note This parameter only applies to a server with a Virtual Interface Card

(VIC) adapter.

Flogi Retries field

Flogi Timeout (ms)

Plogi Retries field field

The number of times that the system tries to log in to the fabric after the first failure.

Enter any integer. To specify that the system continue to try indefinitely, enter infinite in this field. We recommend you consult your storage array documentation for the optimal value for this parameter.

Note This parameter only applies to a server with a VIC adapter, or a converged network adapter.

The number of milliseconds that the system waits before it tries to log in again.

Enter an integer between 1000 and 255000. The default is 4,000. We recommend you consult your storage array documentation for the optimal value for this parameter.

Note This parameter only applies to a server with a VIC adapter or a converged network adapter.

When a Flogi timeout value of 20 seconds or more is configured for a boot vHBA, it could lead to a SAN boot failure if the adapter does not receive an accept to the initial Flogi. For a boot-enabled vHBA, the recommended timeout values is 5 seconds or less.

The number of times that the system tries to log into a port after the first failure.

Enter an integer between 0 and 255. The default is 8. We recommend you consult your storage array documentation for the optimal value for this parameter.

Note This parameter only applies to a server with a VIC adapter.

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Creating a Fibre Channel Adapter Policy

Name

Plogi Timeout (ms) field

Port Down Timeout (ms) field

IO Retry Timeout (seconds)

Port Down IO Retry field

Description

The number of milliseconds that the system waits before it tries to log in again.

Enter an integer between 1000 and 255000. The default is 20,000. We recommend you consult your storage array documentation for the optimal value for this parameter.

For an HBA that is going to be used to boot a Windows OS from SAN, the recommended value for this field is 4,000 ms.

Note This parameter only applies to a server with a VIC adapter.

When a Plogi timeout value of 20 seconds or more is configured for a boot vHBA, it could lead to a SAN boot failure if the adapter does not receive an accept to the initial Plogi. For a boot-enabled vHBA, the recommended timeout values is 5 seconds or less.

The number of milliseconds a remote Fibre Channel port should be offline before informing the SCSI upper layer that the port is unavailable. This parameter is important for host multi-pathing drivers and it is one of the key indicators used for error processing.

Enter an integer between 0 and 240000. The default is 30,000. For a server with a VIC adapter running ESX, the recommended value is 10,000.

For a server with a port that is going to be used to boot a Windows OS from

SAN, the recommended value for this field is 5000 milliseconds.

We recommend you consult your storage array documentation for the optimal value for this parameter.

Note This parameter only applies to a server with a VIC adapter.

The number of seconds that the FC adapter waits before aborting the pending command and resending the same IO. This happens when the network device does not responding to an IO request within the specified time.

Enter an integer between 0 and 59 seconds. The default IO retry timeout is 5 seconds.

The number of times an IO request to a port is returned because the port is busy before the system decides the port is unavailable.

Enter an integer between 0 and 255. The default is 8. We recommend you consult your storage array documentation for the optimal value for this parameter.

Note This parameter only applies to a server with a VIC adapter running

Windows.

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Creating a Fibre Channel Adapter Policy

Name

Link Down Timeout (ms) field

IO Throttle Count

Max LUNs Per Target

LUN Queue Depth field field field

Description

The number of milliseconds the uplink port should be offline before it informs the system that the uplink port is down and fabric connectivity has been lost.

Enter an integer between 0 and 240000. The default is 30,000. We recommend you consult your storage array documentation for the optimal value for this parameter.

Note This parameter only applies to a server with a VIC adapter running

Windows.

The maximum number of data or control I/O operations that can be pending in the vHBA at one time. If this value is exceeded, the additional I/O operations wait in the queue until the number of pending I/O operations decreases and the additional operations can be processed.

Note This parameter is not the same as the LUN queue depth, which is controlled by Cisco UCS Manager based on the operating system installed on the server.

Enter an integer between 256 and 1024. The default is 256. We recommend you consult your storage array documentation for the optimal value for this parameter.

The maximum number of LUNs that the Fibre Channel driver will export or show. The maximum number of LUNs is usually controlled by the operating system running on the server.

Enter an integer between 1 and 1024. The default value is 256. For servers running ESX or Linux, the recommended value is 1024.

We recommend you consult your operating system documentation for the optimal value for this parameter.

Note • This parameter only applies to a server with a VIC adapter or a network adapter.

• This parameter is applicable only for FC-Initiator.

The number of commands that the HBA can send and receive in a single transmission per LUN.

Enter an integer between 1 and 254. The default LUN queue depth is 20.

Note This parameter is applicable only for FC-Initiator.

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Deleting a Fibre Channel Adapter Policy

Step 8

Step 9

Name

Interrupt Mode vHBA Type radio button radio button

Description

The method used to send interrupts to the operating system from the driver.

This can be one of the following:

• MSI-X —Message Signaled Interrupts (MSI) with the optional extension.

We recommend that you select this option if the operating system on the server supports it.

• MSI —MSI only.

• INTx —PCI INTx interrupts.

Note This parameter only applies to a server with a VIC adapter or a network adapter running an operating system other than Windows.

The Windows operating system ignores this parameter.

The vHBA type used in this policy. vHBAs supporting FC and FC-NVMe can now be created on the same adapter. The vHBA type used in this policy can be one of the following:

• FC Initiator—Legacy SCSI FC vHBA initiator

• FC Target—vHBA that supports SCSI FC target functionality

Note This option is available as a Tech Preview.

• FC NVME Initiator—vHBA that is an FC NVME initiator, which discovers

FC NVME targets and connects to them

• FC NVME Target—vHBA that acts as an FC NVME target and provides connectivity to the NVME storage

Note This option is available as a Tech Preview.

vHBA type is supported only on UCS VIC 14xx adapters.

Click OK .

If a confirmation dialog box displays, click Yes .

Deleting a Fibre Channel Adapter Policy

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > Policies > Organization_Name .

Expand the Fibre Channel Policies node.

Right-click the policy you want to delete and choose Delete .

If a confirmation dialog box displays, click Yes .

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

About the Default vHBA Behavior Policy

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click SAN .

Expand SAN > Policies > Organization_Name .

Expand the Fibre Channel Policies node.

Right-click the policy you want to delete and choose Delete .

If a confirmation dialog box displays, click Yes .

About the Default vHBA Behavior Policy

Default vHBA Behavior Policy

Default vHBA behavior policy allow you to configure how vHBAs are created for a service profile. You can choose to create vHBAs manually, or you can allow them to be created automatically.

You can configure the default vHBA behavior policy to define how vHBAs are created. This can be one of the following:

• None —Cisco UCS Manager does not create default vHBAs for a service profile. All vHBAs must be explicitly created.

• HW Inherit —If a service profile requires vHBAs and none have been explicitly defined, Cisco UCS

Manager creates the required vHBAs based on the adapter installed in the server associated with the service profile.

Note If you do not specify a default behavior policy for vHBAs, none is used by default.

Configuring a Default vHBA Behavior Policy

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > Policies .

Expand the root node.

Click Default vHBA Behavior .

On the General Tab , in the Properties area, click one of the following radio buttons in the Action field:

Click Save Changes .

DETAILED STEPS

Step 1 In the Navigation pane, click SAN .

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

SPDM Security Policy

Step 2

Step 3

Step 4

Step 5

Step 6

Expand SAN > Policies .

Expand the root node.

You can configure only the default vHBA behavior policy in the root organization. You cannot configure the default vHBA behavior policy in a sub-organization.

Click Default vHBA Behavior .

On the General Tab , in the Properties area, click one of the following radio buttons in the Action field:

• None —Cisco UCS Manager does not create default vHBAs for a service profile. All vHBAs must be explicitly created.

• HW Inherit —If a service profile requires vHBAs and none have been explicitly defined, Cisco UCS Manager creates the required vHBAs based on the adapter installed in the server associated with the service profile.

Click Save Changes .

SPDM Security Policy

SPDM Security

Cisco UCS M6 Servers can contain mutable components that could provide vectors for attack against a device itself or use of a device to attack another device within the system. To defend against these attacks, the Security

Protocol and Data Model (SPDM) Specification enables a secure transport implementation that challenges a device to prove its identity and the correctness of its mutable component configuration. This feature is supported on Cisco UCS C220 and C240 M6 Servers starting with in Cisco UCS Manager, Release 4.2(1d).

Note SPDM is currently not supported on the Cisco UCS C245 M6 Server.

SPDM defines messages, data objects, and sequences for performing message exchanges between devices over a variety of transport and physical media. It orchestrates message exchanges between Baseboard

Management Controllers (BMC) and end-point devices over a Management Component Transport Protocol

(MCTP). Message exchanges include authentication of hardware identities accessing the BMC. The SPDM enables access to low-level security capabilities and operations by specifying a managed level for device authentication, firmware measurement, and certificate management. Endpoint devices are challenged to provide authentication. and BMC authenticates the endpoints and only allows access for trusted entities.

The UCS Manager optionally allows uploads of external security certificates to BMC. A maximum of 40

SPDM certificates is allowed, including native internal certificates. Once the limit is reached, no more certificates can be uploaded. User uploaded certificates can be deleted but internal/default certificates cannot.

A SPDM security policy allows you to specify one of three Security level settings. Security can be set at one of the three levels listed below:

• Full Security:

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Creating a SPDM Security Policy

This is the highest MCTP security setting. When you select this setting, a fault is generated when any endpoint authentication failure or firmware measurement failure is detected. A fault will also be generated if any of the endpoints do not support either endpoint authentication or firmware measurements.

• Partial Security (default):

When you select this setting, a fault is generated when any endpoint authentication failure or firmware measurement failure is detected. There will NOT be a fault generated when the endpoint doesn’t support endpoint authentication or firmware measurements.

• No Security

When you select this setting, there will NOT be a fault generated for any failure (either endpoint measurement or firmware measurement failures).

You can also upload the content of one or more external/device certificates into BMC. Using a SPDM policy allows you to change or delete security certificates or settings as desired. Certificates can be deleted or replaced when no longer needed.

Certificates are listed in all user interfaces on a system.

Creating a SPDM Security Policy

This step creates a SPDM policy.

Note You can upload up to 40 SPDM certificates (including native certificates).

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

In the Navigation pane, click Servers .

Go to Policies . Expand the root node.

Right-click SPDM Certificate Policies and select Create SPDM Policy .

Enter a name for this policy and select a Fault Alert Setting for the security level: Disabled , Partial , or Full .

The default is Partial .

Click on Add in the Create Policy window. The Add SPDM Certificate window will open.

Name the certificate.

UCS Manager supports only Pem certificates.

Paste the contents of the certificate into the Certificate field.

Click OK to add the certificate and return to the Create SPDM Policy window.

You can add up to 40 certificates.

In the Create SPDM Policy menu, click Okay .

After the SPDM policy is created, it will be listed immediately, along with its Alert setting, when you select SPDM

Certificate Policy under the Server root Policies.

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Associating the Security Policy with a Server

What to do next

Assign the Certificate to a Service Profile. The Service Profile must be associated with a server for it to take effect.

Associating the Security Policy with a Server

Before you begin

Create the SPDM security policy.

Step 1

Step 2

Step 3

Step 4

In the Navigation pane, click Servers .

Go to Service Profiles . Expand the root node.

Select the Service Profile you want to associate with the Policy you created.

a) On the Policies tab, scroll down and expand SPDM Certificate Policy . In the SPDM Certificate Policy dropdown, select the desired policy to associate with this Service Profile.

Click OK .

The SPDM Policy will now be associated with the service profile.

What to do next

Check the fault alert level to make sure it is set to the desired setting.

Viewing the Fault Alert Settings

You can view the Fault Alert setting associated with a specific chassis.

Before you begin

Create a policy and associate it with a Service Profile.

Step 1

Step 2

Step 3

In the Navigation pane, click Equipment .

Select a Rack-Mount Server.

On the Inventory tab, select CIMC . .

User uploaded certificates are listed and information for specific certificates can be selected and viewed.

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

SAN Connectivity Policies

About the LAN and SAN Connectivity Policies

Connectivity policies determine the connections and the network communication resources between the server and the LAN or SAN on the network. These policies use pools to assign MAC addresses, WWNs, and WWPNs to servers and to identify the vNICs and vHBAs that the servers use to communicate with the network.

Note We do not recommend that you use static IDs in connectivity policies, because these policies are included in service profiles and service profile templates and can be used to configure multiple servers.

Privileges Required for LAN and SAN Connectivity Policies

Connectivity policies enable users without network or storage privileges to create and modify service profiles and service profile templates with network and storage connections. However, users must have the appropriate network and storage privileges to create connectivity policies.

Privileges Required to Create Connectivity Policies

Connectivity policies require the same privileges as other network and storage configurations. For example, you must have at least one of the following privileges to create connectivity policies:

• admin—Can create LAN and SAN connectivity policies

• ls-server—Can create LAN and SAN connectivity policies

• ls-network—Can create LAN connectivity policies

• ls-storage—Can create SAN connectivity policies

Privileges Required to Add Connectivity Policies to Service Profiles

After the connectivity policies have been created, a user with ls-compute privileges can include them in a service profile or service profile template. However, a user with only ls-compute privileges cannot create connectivity policies.

Interactions between Service Profiles and Connectivity Policies

You can configure the LAN and SAN connectivity for a service profile through either of the following methods:

• LAN and SAN connectivity policies that are referenced in the service profile

• Local vNICs and vHBAs that are created in the service profile

• Local vNICs and a SAN connectivity policy

• Local vHBAs and a LAN connectivity policy

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Creating a SAN Connectivity Policy

Cisco UCS maintains mutual exclusivity between connectivity policies and local vNIC and vHBA configuration in the service profile. You cannot have a combination of connectivity policies and locally created vNICs or vHBAs. When you include a LAN connectivity policy in a service profile, all existing vNIC configuration is erased, and when you include a SAN connectivity policy, all existing vHBA configuration in that service profile is erased.

Creating a SAN Connectivity Policy

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > Policies .

Expand the node for the organization where you want to create the policy.

Right-click SAN Connectivity Policies and choose Create SAN Connectivity Policy .

In the Create SAN Connectivity Policy dialog box, enter a name and optional description.

From the WWNN Assignment drop-down list in the World Wide Node Name area, choose one of the following:

In the vHBAs table, click Add .

In the Create vHBAs dialog box, enter the name and optional description.

Choose the Fabric ID , Select VSAN , Pin Group , Persistent Binding , and Max Data Field Size .

10.

In the Operational Parameters area, choose the Stats Threshold Policy .

11.

In the Adapter Performance Profile area, choose the Adapter Policy and QoS Policy .

12.

After you have created all the vHBAs you need for the policy, click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click SAN .

Expand SAN > Policies .

Expand the node for the organization where you want to create the policy.

If the system does not include multi tenancy, expand the root node.

Right-click SAN Connectivity Policies and choose Create SAN Connectivity Policy .

In the Create SAN Connectivity Policy dialog box, enter a name and optional description.

From the WWNN Assignment drop-down list in the World Wide Node Name area, choose one of the following:

• Choose Select (pool default used by default) to use the default WWN pool.

• Choose one of the options listed under Manual Using OUI and then enter the WWN in the World Wide Node

Name field.

You can specify a WWNN in the range from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from

50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. You can click the here link to verify that the WWNN you specified is available.

• Choose a WWN pool name from the list to have a WWN assigned from the specified pool. Each pool name is followed by two numbers in parentheses that show the number of WWNs still available in the pool and the total number of WWNs in the pool.

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Creating a vHBA for a SAN Connectivity Policy

Step 7

Step 8

Step 9

Step 10

Step 11

Step 12

In the vHBAs table, click Add .

In the Create vHBAs dialog box, enter the name and optional description.

Choose the Fabric ID , Select VSAN , Pin Group , Persistent Binding , and Max Data Field Size .

You can also create a VSAN or SAN pin group from this area.

In the Operational Parameters area, choose the Stats Threshold Policy .

In the Adapter Performance Profile area, choose the Adapter Policy and QoS Policy .

You can also create a fibre channel adapter policy or QoS policy from this area.

After you have created all the vHBAs you need for the policy, click OK .

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

What to do next

Include the policy in a service profile or service profile template.

Creating a vHBA for a SAN Connectivity Policy

SUMMARY STEPS

In the Navigation pane, click SAN .

On the SAN tab, expand SAN > Policies > Organization_Name > San Connectivity Policies .

Choose the policy for which you want to create a vHBA.

In the Work pane, click the General tab.

In the table icon bar, click the + button.

In the Create vHBAs dialog box, enter the name and optional description.

Choose the Fabric ID , Select VSAN , Pin Group , Persistent Binding , and Max Data Field Size .

In the Operational Parameters area, choose the Stats Threshold Policy .

In the Adapter Performance Profile area, choose the Adapter Policy and QoS Policy .

10.

Click Save Changes .

DETAILED STEPS

Step 8

Step 9

In the Navigation pane, click SAN .

On the SAN tab, expand SAN > Policies > Organization_Name > San Connectivity Policies .

Choose the policy for which you want to create a vHBA.

In the Work pane, click the General tab.

In the table icon bar, click the + button.

In the Create vHBAs dialog box, enter the name and optional description.

Choose the Fabric ID , Select VSAN , Pin Group , Persistent Binding , and Max Data Field Size .

You can also create a VSAN or SAN pin group from this area.

In the Operational Parameters area, choose the Stats Threshold Policy .

In the Adapter Performance Profile area, choose the Adapter Policy and QoS Policy .

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Deleting a vHBA from a SAN Connectivity Policy

Step 10

You can also create a fibre channel adapter policy or QoS policy from this area.

Click Save Changes .

Deleting a vHBA from a SAN Connectivity Policy

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > Policies > Organization_Name .

Choose the policy from which you want to delete the vHBA.

In the Work pane, click the General tab.

In the vHBAs table, do the following:

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click SAN .

Expand SAN > Policies > Organization_Name .

Choose the policy from which you want to delete the vHBA.

In the Work pane, click the General tab.

In the vHBAs table, do the following: a) Click the vHBA that you want to delete.

b) On the icon bar, click Delete .

If a confirmation dialog box displays, click Yes .

Creating an Initiator Group for a SAN Connectivity Policy

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > Policies > Organization_Name .

Choose the policy for which you want to create an initiator group.

In the Work pane, click the vHBA Initiator Groups tab.

In the table icon bar, click the + button.

In the Create vHBA Initiator Group dialog box, complete the following fields:

Click OK .

DETAILED STEPS

Step 1 In the Navigation pane, click SAN .

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Deleting an Initiator Group from a SAN Connectivity Policy

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Expand SAN > Policies > Organization_Name .

Choose the policy for which you want to create an initiator group.

In the Work pane, click the vHBA Initiator Groups tab.

In the table icon bar, click the + button.

In the Create vHBA Initiator Group dialog box, complete the following fields:

Name

Name field

Description

The name of the vHBA initiator group.

Description field A description of the group.

Enter up to 256 characters. You can use any characters or spaces except ` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign), > (greater than),

< (less than), or ' (single quote).

Check the check box in the Select column for each vHBA that you want to use.

Select vHBA Initiators table

Storage Connection Policy drop-down list

The storage connection policy associated with this vHBA initiator group. If you want to:

• Use an existing storage connection policy, then choose that policy from the drop-down list. The Cisco UCS Manager GUI displays information about the policy and its FC target endpoints in the Global Storage

Connection Policy area.

Create a new storage connection policy that will be globally available, then click the Create Storage Connection Policy link.

• Create a local storage connection policy that is available only to this vHBA initiator group, then choose the Specific Storage Connection Policy option.

The Cisco UCS Manager GUI displays the Specific Storage Connection

Policy area that allows you to configure the local storage connection policy.

Create Storage Connection Policy link

Click this link to create a new storage connection policy that will be available to all service profiles and service profile templates.

Click OK .

Deleting an Initiator Group from a SAN Connectivity Policy

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > Policies > Organization_Name .

Choose the policy from which you want to delete the initiator group

In the Work pane, click the vHBA Initiator Groups tab.

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Deleting a SAN Connectivity Policy

In the table, do the following:

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click SAN .

Expand SAN > Policies > Organization_Name .

Choose the policy from which you want to delete the initiator group

In the Work pane, click the vHBA Initiator Groups tab.

In the table, do the following: a) Click the initiator group that you want to delete.

b) On the icon bar, click Delete .

If a confirmation dialog box displays, click Yes .

Deleting a SAN Connectivity Policy

If you delete a SAN connectivity policy that is included in a service profile, it also deletes all vHBAs from that service profile and disrupts SAN data traffic for the server associated with the service profile.

SUMMARY STEPS

In the Navigation pane, click SAN .

Expand SAN > Policies > Organization_Name .

Expand the SAN Connectivity Policies node.

Right-click the policy that you want to delete and choose Delete .

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click SAN .

Expand SAN > Policies > Organization_Name .

Expand the SAN Connectivity Policies node.

Right-click the policy that you want to delete and choose Delete .

If a confirmation dialog box displays, click Yes .

Enabling Intel ® Volume Management Device

Volume Management Device (VMD) Setup

The Intel ® Volume Management Device (VMD) is a tool that provides NVMe drivers to manage PCIe Solid

State Drives attached to VMD-enabled domains. This includes Surprise hot-plug of PCIe drives and configuring

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Enabling VMD on UCS Manager blinking patterns to report status. PCIe Solid State Drive (SSD) storage lacks a standardized method to blink

LEDs to represent the status of the device. With VMD, you can control LED indicators on both direct attached and switch attached PCIe storage using a simple command-line tool.

To use VMD, you must first enable VMD through a UCS Manager BIOS policy and set the UEFI boot options.

Enabling VMD provides Surprise hot plug and optional LED status management for PCIe SSD storage that is attached to the root port. VMD Passthrough mode provides the ability to manage drives on guest VMs.

Enabling VMD also allows configuration of Intel ® on Intel ® Xeon ®

Virtual RAID on CPU (VRoC), a hybrid RAID architecture

Scalable Processors. Documentation on the use and configuration of VRoC can be found at the Intel website.

IMPORTANT : VMD must be enabled in the UCS Manager BIOS settings before Operating System install.

If enabled after OS installation, the server will fail to boot. This restriction applies to both standard VMD and

VMD Passthrough. Likewise, once enabled, you cannot disable VMD without a loss of system function.

Enabling VMD on UCS Manager

To configure a BIOS and local boot Policy for VMD in UCS Manager, use the following procedure. The

VMD platform default is disabled.

Note VMD must be enabled before OS installation.

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

In the Navigation pane, click Servers .

Expand the node for the organization where you want to create the policy.

If the system does not include multi tenancy, expand the root node.

Configure the BIOS policy for VMD: select a service profile and go to the Policies tab. In the Policies section, right-click the BIOS Policy section and select Create BIOS Policy from the popup. In the BIOS Policy form, enter a name and optional description. Click OK to create the policy.

Go to Policies > Root > BIOS Policies and select the new policy.

Expand BIOS Policies and select Advanced and LOM and PCle Slots from the submenus.

Scroll down to VMD Enable and select Enable .

Click Save Changes to enable VMD functions.

In the Boot Policy tab, create a local boot policy. Select Uefi for the Boot Mode and Add NVMe from the Local Devices menu. Click Save Changes to create the policy.

Enabling Volume Management Device (VMD) in Passthrough Mode

Volume Management Device (VMD) Passthrough Mode

The Intel ® Volume Management Device (VMD) driver release package for Direct Device Assignment contains the Intel VMD UEFI Driver version for Direct Assign (PCIe PassThru) in VMware ESXi Hypervisor. The

Intel VMD NVMe driver assists in the management of CPU-attached Intel PCIe NVMe SSDs.

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Configuring VMD Passthrough

The Intel VMD driver is required to enable the Direct Assign and discovery of the VMD physical addresses from a supported guest VM. Drivers are only provided for Passthrough mode for ESXi support of Red Hat

Linux or Ubuntu. VMD Passthrough is enabled by configuring a UCS Manager BIOS policy before loading the Operating System. Once the Operating System has been loaded, you cannot enable or disable the VMD

Passthrough option.

Note Passthrough mode is enabled by default, but you should always confirm that it is enabled before proceding.

Configuring VMD Passthrough

Passthrough mode is only supported on ESXi drivers for Red Hat Linux or Ubuntu guest operating systems.

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

In the Navigation pane, click Servers .

Expand the node for the organization where you want to create the policy.

If the system does not include multi tenancy, expand the root node.

Go to Policies > Root > BIOS Policies and select the new policy.

Expand BIOS Policies and select Advanced and LOM and PCle Slots from the submenus.

Scroll down to VMD Enable and select Enable .

Click Save Changes to enable VMD functions.

To finish enabling VMD Passthrough mode, select Advanced and Intel Directed IO from the submenus and scroll down to Intel VT Directed IO . Verify that the dropdown is set to Enabled . If not, set it.

Click Save Changes to enable the VMD Passthrough policy.

In the Boot Policy tab, create a local boot policy. Select Uefi for the Boot Mode . Click OK to create the policy.

Downloading VMD Drivers

Intel ® Volume Management Device Drivers

Intel ® Volume Management Device (VMD) for NVMe enables drive management options using hardware logic inside the Intel Xeon processor. Specific drivers are available for the following operating systems:

• Linux

• Windows 2016, 2019

• VMWare

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Intel ® Virtual RAID on CPU (VRoC) with VMD

Note The latest VMWare drivers are available directly from the VMWare site.

Following links in the VMWare driver download on the Cisco download site will take you directly to the VMWare login page.

For guest Operating Systems on ESXi, use VMD Passthrough mode. Supported Operating Systems for VMD

Passthrough are:

• Red Hat Linux

• Ubuntu

To use the features of Intel VMD, you must:

• Enable VMD by creating a BIOS policy in the UCS Manager.

Note The system will fail to boot if VMD is enabled or disabled after OS installation.

Do not change the BIOS setting after OS installation.

• Install the appropriate VMD NVMe driver.

• Install the appropriate management tools for the driver package.

• Boot from UEFI.

Intel ® Virtual RAID on CPU (VRoC) with VMD

Intel ® Virtual RAID on CPU (VRoC) allows you to create and manage RAID volumes within the BIOS of

VMD-enabled Intel NVMe SSD drives using hardware logic inside the Intel Xeon processor. More information on Intel VRoC can be found at: https://www.intel.com/content/www/us/en/support/products/122484/ memory-and-storage/ssd-software/intel-virtual-raid-on-cpu-intel-vroc.html

The User Guides for Intel VRoC can be accessed at the direct link at: https://www.intel.com/content/www/ us/en/support/articles/000030445/memory-and-storage/ssd-software.html?productId=122484&localeCode=us_ en

The Windows and Linux user documentation also contains information on how to configure Intel VRoC in the pre-boot environment. Creation of RAID volumes in VRoC is through the HII interface. The Windows documentation provides information on using the BIOS HII option to set up and configure RAID volumes in

VRoC.

To use Intel VRoC, you must:

• Enable VMD in the BIOS settings

• Use UEFI boot mode

• Have sufficient drive resources to create the volume

• Use the BIOS HII option to set up and configure VRoC.

The Cisco implementation of Intel VRoC supports RAID 0 (striping), RAID 1 (mirroring), RAID 5 (striping with parity) and RAID 10 (combined mirroring and striping).

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Downloading the Linux VMD Drivers

Complete these steps to download and install the driver bundle:

Before you begin

Make sure that VMD is enabled in the BIOS settings.

Note The system will fail to boot if VMD is enabled or disabled after OS installation. Do not change the BIOS setting after OS installation.

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

In a web browser, navigate to https://software.cisco.com/download/home .

Search on UCS B-Series Blade Server Software or UCS C-Series Rack-Mount UCS-Managed Server Software , depending on your platform.

Choose the UCS drivers from the Software Type selections: Unified Computing System (UCS) Drivers .

Click on the latest release in the left panel.

Note The ISO image for VMD on blade servers is available from the 4.0(4f) release onward.

Click on ISO image of UCS-related linux drivers only and download the driver bundle.

When the driver bundle is downloaded, open it and select Storage > Intel > VMD > RHELx.x .

Click on the version of Red Hat Linux that you wish to install.

Extract the contents of the folder. The folder contains both the driver package and associated documentation. Follow the installation procedure packaged with the drivers.

What to do next

The Intel ® Virtual RAID on CPU (VRoC) Linux Software User Guide can be found with the user documentation at: https://www.intel.com/content/www/us/en/support/articles/000030445/memory-and-storage/ ssd-software.html?productId=122484&localeCode=us_en . It provides information on performing BIOS HII

VRoC setup in the pre-boot environment, as well as how to install and use the programmable LED utility.

Downloading the Windows VMD Drivers

Complete these steps to download the driver bundle:

Before you begin

Make sure that VMD is enabled in the BIOS settings.

Note The system will fail to boot if VMD is enabled or disabled after OS installation. Do not change the BIOS setting after OS installation.

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Downloading the VMD Passthrough Drivers

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

In a web browser, navigate to https://software.cisco.com/download/home .

Search on UCS B-Series Blade Server Software or UCS C-Series Rack-Mount UCS-Managed Server Software , depending on your platform.

Choose the UCS drivers from the Software Type selections: Unified Computing System (UCS) Drivers .

Click on the latest release in the left panel.

The ISO image for VMD is available from the 4.0(4f) release onward.

Click on ISO image of UCS-related windows drivers only and download the driver bundle.

When the driver bundle is downloaded, open it and select Storage > Intel > VMD > KIT_x_x_x_xxxx .

Extract the contents of the folder.

Click on the entry for the kit and KIT > Install .

The folder contains both the driver package and associated documentation. Expand the zip file for

VROC_x_x_x_xxxxInstall .

Follow the installation procedure packaged with the drivers.

What to do next

For setting up Intel ® Virtual RAID on CPU (VRoC), refer to the online instructions at https://www.intel.com/ content/www/us/en/support/products/122484/memory-and-storage/ssd-software/ intel-virtual-raid-on-cpu-intel-vroc.html

Information on VRoC RAID features and management can be found in the Windows Intel Virtual RAID on

CPU Software User's Guide at https://www.intel.com/content/dam/support/us/en/documents/ memory-and-storage/ssd-software/Windows_VROC_User_Guide.pdf

Downloading the VMD Passthrough Drivers

Complete these steps to download and install the driver bundle for VMD Passthrough mode:

Note The VMD Passthrough driver bundle includes packages for both ESXi and Ubuntu.

Before you begin

Note The system will fail to boot if VMD is enabled or disabled after OS installation. Do not change the BIOS setting after OS installation.

Step 1

Step 2

Step 3

In a web browser, navigate to https://software.cisco.com/download/home .

Search on Servers - Unified Computing.

Search on UCS B-Series Blade Server Software or UCS C-Series Rack-Mount UCS-Managed Server Software , depending on your platform.

100

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Custom LED Status with VMD on NVMe

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Choose the UCS utilities from the Software Type selections: Unified Computing System (UCS) Utilities .

Click on the latest release in the left panel.

Note The ISO image for VMD is available from UCSM 4.0(4f) release onward.

Click on ISO image of UCS-related vmware utilities only and download the utilities bundle.

When the driver bundle is downloaded, open it and select Storage > Intel > VMD .

The bundle provides both the driver installation package for the desired version of ESXi or VMD Direct Asssign with

Ubuntu, passthrough mode, and the Signed LED Offline bundle. Also included is a pdf that provides steps to configure an Ubuntu Virtual Machine in ESXi.

Click on either the version of ESXi that you wish to install or the zip file for Ubuntu.

For ESXi versions, Click on ESXi _ x > Direct Assign and chose the desired zip file.

Extract the contents of the folder. Follow the installation procedure packaged with the driver software.

What to do next

Extract the contents of the LED management tools zip file. Install the management tools according to the instructions included with the driver package.

Before using the command line tools, the ESXi command line shell should be enabled from either the vSphere client or from the direct console of the ESXi host system.

Custom LED Status with VMD on NVMe

Once you have set up VMD, you can customize LED blinking patterns on PCIe NVMe drives. Information on LED customization can be found in the User Guides included in the driver packages.

LED Blinking

PCIe SSD drives lack a standard way to manage the LEDs that indicate drive status and health. Without this, there is a risk of removing the wrong drive, resulting in data loss. SSD drives have two indicators, the first being a green activity LED whose signals come directly from the SSD, and the second being a status LED whose signals come from the backplane. VMD manages only the status LEDs, not the activity LEDs.

LED Management only applies to NVMe and/or SATA drives. It does not support drives that are connected either by an I/O cable, PCIe add-in card or plugged directly into the motherboard .

LED Activity During Drive Hot-plug

VMD with NVMe supports Surprise hot-plugging. When a disk is hot-removed, then re-inserted into the same slot, the fault LED blinks for 10 seconds. This is expected behavior.The fail state is imposed on a slot’s LEDs when the drive is removed, but the backplanes require the drive to be present in the slot for a LED to blink.

Thus, the fail state exists once the drive is removed, but a LED blinks only when the new drive is inserted and discovered. The LED will return to normal once hot-plug event is handled.

Cisco UCS Manager Storage Management Guide, Release 4.2

101

Storage-Related Policies

Custom LED Status with VMD on NVMe

Custom Blinking Patterns

VRoC with VMD allows you to perform basic LED management configuration of the status LEDs on compatible backplanes. Once the VMD NVMe driver is installed, you can install the VMD LED Management Tool, which lets you manage the LED through a command line interface. VMD allows you to customize LED blinking patterns on PCIe NVMe drives to better identify failing drives.

The tables below provide some brief guidelines for customized blinking on the various platforms. As individualized patterns are programmable, these tables provide only representative guidelines.

Table 5: LED Blinking Patterns: Windows

Status LED

"Activate LED"

Drive Failure

RAID volume Initialization or

Verify and Repair Process

Managed unplug

Behavior Options

Identifies a specific device in an enclosure by blinking the status

LED of that drive in a designated pattern.

1-3600 seconds. Values outside this range default to 12 seconds.

Default = 12 seconds

Indicates a drive that is in a degraded or failed state by lighting the status LED of that device in a defined failure pattern.

The failure pattern is displayed until:

• 1. It is physically removed.

or the RAID volume, that contains the failed drive, is either deleted or physically removed.

• 2. From the time when a non-failed drive that is part of a RAID volume is removed, or the failed drive is identified and removed. It remains in failure state until a new drive is inserted into the same slot or the platform is rebooted.

Default = Option 1

When a RAID volume is in Rebuild state, the status LEDs blink in the defined Rebuild pattern on either the specific drive being rebuilt or on the entire RAID volume that is being rebuilt.

Default = Enabled

Can be:

1. Disabled (only on one drive)

2. Enabled (on all drives)

During a managed hot unplug, the status LED of the managed drive blinks in the defined Locate pattern until the drive is physically ejected.

None. Enabled by default.

102

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage-Related Policies

Custom LED Status with VMD on NVMe

Status LED

RAID volume is migrating

Rebuild

Behavior

Only the migrating drive blinks.

Options

During RAID volume migration, the status LEDs blink in the defined

Rebuild pattern on all drives until the process is complete.

Default = Enabled

Can be:

1. Disabled (No Status LED

Blinking)

2. Enabled (Blinks Status LEDs)

Default = Disabled

Table 6: LED Blinking Patterns: Linux

Status LED Behavior Options

Skip/exclude controller

BLACKLIST ledmon will exclude scanning controllers listed on the blacklist.

When the whitelist is also set in the config file, the blacklist is ignored.

Exclude controllers on the blacklist.

Default = Support all controllers

RAID volume is initializing, verifying, or verifying and fixing

BLINK_ON_INIT

Rebuild pattern on all drives in

RAID volume (until initialization, verify, or verify and fix finishes).

1. True/Enabled (on all drives)

2. False/Disabled (no drives)

Default = True/Enabled

Set ledmon scan interval

INVERVAL

Defines the time interval between ledmon sysfs scans.

The value is given in seconds.

10s (5s maximum)

Default = 10s

RAID volume is rebuilding

REBUILD_BLINK_ON_ALL

RAID volume is migrating

BLINK_ON_MIGR

Rebuild pattern on a single drive to which RAID volume rebuilds

1. False/Disabled (on one drive)

2. True/Enabled (on all drives)

Default = False/Disabled

Rebuild pattern on all drives in

RAID volume (until migration finishes).

1. True/Enabled (on all drives)

2. False/Disabled (no drives)

Default = True/Enabled

Set ledmon debug level

LOG_LEVEL

Corresponds with –log-level flag from ledmon

Acceptable values are: quiet, error, warning, info, debug, all - 0 means

‘quiet’ and 5 means ‘all

Default = 2

Set manage one RAID member or

All RAID

RAID_MEMBRES_ONLY

If the flag is set to ledmon true, will limit monitoring only to drives that are RAID members.

1. False / (all RAID member and

PT)

2. True / (RAID member only)

Default = False

Cisco UCS Manager Storage Management Guide, Release 4.2

103

Storage-Related Policies

Custom LED Status with VMD on NVMe

Status LED

Limited scans only to specific controllers

WHITELIST

Table 7: LED Blinking Patterns: ESXi

Status LED

"Identify"

"Off"

Behavior ledmon limits changing the LED state to controllers listed on whitelist.

Options

Limit changing LED state in whitelist controller.

Default = No limit.

Behavior Options

The ability to identify a specific device in an enclosure by blinking the status LED of that drive in the defined Locate pattern.

None. Default is Off.

The ability to turn off the "Identify"

LED once a specific device in an enclosure has been located.

None. Default is Off.

104

Cisco UCS Manager Storage Management Guide, Release 4.2

C H A P T E R

SED Security Policies

•

Security Policies for Self-Encrypting Drives, on page 105

•

Security Flags of the Controller and Disk, on page 106

•

Managing Local Security Policies, on page 106

•

KMIP Client Certificate Policy, on page 108

•

Managing Remote Security Policies, on page 111

•

Enabling and Disabling Security on Disks, on page 113

•

Disabling Security on a Controller, on page 114

•

Unlocking a Locked Disk, on page 114

•

Erasing a Secure Foreign Configuration Disk, on page 115

•

Secure Data Deletion, on page 116

Security Policies for Self-Encrypting Drives

Self-Encrypting Drives (SEDs) have special hardware that encrypts incoming data and decrypts outgoing data in real-time. The data on the disk is always encrypted in the disk and stored in the encrypted form. The encrypted data is always decrypted on the way out of the disk. A media encryption key controls this encryption and decryption. This key is never stored in the processor or memory. Cisco UCS Manager supports SED security policies on Cisco UCS C-Series servers, B-Series M5 servers, and S-Series servers.

SEDs must be locked by providing a security key. The security key, which is also known as Key-Encryption

Key or an authentication passphrase, is used to encrypt the media encryption key. If the disk is not locked, no key is required to fetch the data.

Cisco UCS Manager enables you to configure security keys locally or remotely. When you configure the key locally, you must remember the key. If you forget the key, it cannot be retrieved, and the data is lost. You can configure the key remotely by using a key management server (also known as KMIP server). This method addresses the issues related to safe-keeping and retrieval of the keys in the local management.

The encryption and decryption for SEDs is done through the hardware. Thus, it does not affect the overall system performance. SEDs reduce the disk retirement and redeployment costs through instantaneous cryptographic erasure. Cryptographic erasure is done by changing the media encryption key. When the media encryption key of a disk is changed, the data on the disk cannot be decrypted, and is immediately rendered unusable. With Cisco UCS Manager Release 3.1(3), SEDs offer disk theft protection for C-Series and S-Series servers. For HX servers, SEDs offer node theft protection. Cisco UCS Manager Release 4.0(2) extends the

SED security policies to UCS B-Series M5 servers.

Cisco UCS Manager Storage Management Guide, Release 4.2

105

SED Security Policies

Security Flags of the Controller and Disk

Security flags indicate the current security status of the storage controller and disks.

The storage controller and disks have the following security flags:

• Security Capable—Indicates that the controller or disk is capable of supporting SED management.

• Security Enable—Indicates that the security-key is programmed on the controller or disk, and security is enabled on the device. This flag is set when you configure a security policy and associate it to a server, making the controller and disk secure. This flag is not set on an HX device.

• Secured—Indicates that the security-key is programmed on the controller or disk, and security is enabled on the HX device.

The following security flags are exclusive to storage disks:

• Locked—Indicates that the disk key does not match the key on the controller. This happens when you move disks across servers that are programmed with different keys. The data on a locked disk is inaccessible and the operating system cannot use the disk. To use this disk, you must either unlock the disk or secure erase the foreign configuration.

• Foreign Secured—Indicates that a secure disk is in foreign configuration. This happens when you unlock a locked disk with the right key, but the disk is in a foreign configuration state and the data on it is encrypted. To use this disk, you can either import the foreign configuration or clear the foreign config.

Managing Local Security Policies

Creating a Local Security Policy

Before you begin

You can create a local policy on a new or existing storage profile.

SUMMARY STEPS

In the Navigation pane, click Storage > Storage Profiles .

Choose the storage profile where you want to create the policy.

Click the Security Policy tab and then click Create Security Policy or right-click the storage profile and select Create Security Policy .

Click the Local Policy option.

DETAILED STEPS

Step 1

Step 2

In the Navigation pane, click Storage > Storage Profiles .

Choose the storage profile where you want to create the policy.

106

Cisco UCS Manager Storage Management Guide, Release 4.2

SED Security Policies

Modifying a Local Security Policy

Step 3

Step 4

Click the Security Policy tab and then click Create Security Policy or right-click the storage profile and select Create

Security Policy .

Click the Local Policy option.

a) Enter Key .

The key must consist of 32 alphanumeric characters.

b) Click OK .

What to do next

The key thus created is associated to the storage profile for that server and is deployed under storage controller.

To verify this, go to Server ID > Inventory > Storage > Controller and select a SAS storage controller. Go to the General tab and check whether the Security field shows as drive security enable .

Modifying a Local Security Policy

SUMMARY STEPS

In the Navigation pane, click Storage > Storage Profiles .

Choose the storage profile where you have created the policy.

Click the Security Policy tab.

(Optional) To modify the key for the local policy, in the Local Policy area:

(Optional) To change the security policy from Local Policy to Remote Policy :

Click Save Changes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click Storage > Storage Profiles .

Choose the storage profile where you have created the policy.

Click the Security Policy tab.

(Optional) To modify the key for the local policy, in the Local Policy area: a) Enter a new security key for the database in the Key field.

b) Enter the current security key for the database in the Deployed Key field.

(Optional) To change the security policy from Local Policy to Remote Policy : a) Click the Remote Policy option.

b) Enter the primary server details in the IP Address/Hostname field.

c) (Optional) Enter the secondary server details in the IP Address/Hostname field.

d) (Optional) Enter the current security key for the database in the Deployed Key field.

e) (Optional) Enter the port number of the server in the Port field.

f) Enter the contents of the KMIP certificate in the KMIP Server Public Certificate field.

g) (Optional) Enter user credentials by clicking Add Login Details .

Click Save Changes .

Cisco UCS Manager Storage Management Guide, Release 4.2

107

SED Security Policies

Inserting a Secured Disk into a Server with a Local Security Policy

When you insert a secured disk into a server, one of the following will occur:

• The security-key on the drive matches that of the server and it automatically gets unlocked.

• The security-key on the disk is different from the security-key on the server. The disk will appear as a locked disk. You can do one of the following on a locked disk:

• Erase the secure foreign configuration to delete all data on the disk.

• Unlock the disk by providing the correct key of the disk. After unlocking the disk, the disk will be in the Foreign Secured state. You must immediately import or clear the foreign configuration for these disks.

Note If you unlock another set of disks before importing the foreign configuration for the current set of disks, the current set of disks become locked again and go in to the Locked state.

KMIP Client Certificate Policy

You can configure the key remotely by using a key management server, which is also known as KMIP server.

You must create a KMIP client certificate policy before creating a remote policy. The hostname that is used for generating the certificate is the serial number of the KMIP server.

You can create a certificate policy from two separate scopes:

• Global scope—You can initially create a global certificate policy in this scope. Any modification of the certificate in this scope will not result in the regeneration of the certificate.

• Server scope—You can create or modify a certificate policy in this scope. This will result in a regeneration of the certificates. Such a certificate is specific to the server, and, for this server, overrides the global certificate.

After you create a KMIP client certificate policy, do one of the following:

• Copy the generated certificate to the KMIP Server.

• Use the generated Certificate Signing Request to get a CA-signed certificate. Copy this CA-signed certificate to the CIMC.

Creating a Global KMIP Client Certificate Policy

You can create a global KMIP client certificate policy.

The hostname that used to create the certificate when using this policy is the serial number of the server.

SUMMARY STEPS

In the Navigation pane, click Equipment .

108

Cisco UCS Manager Storage Management Guide, Release 4.2

SED Security Policies

Creating a KMIP Client Certificate Policy for a Server

In the Work pane, click the Policies tab.

Click the Security subtab.

Click Create KMIP Client Cert Policy .

In the Create KMIP Client Cert Policy dialog box that appears, enter the following information:

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click Equipment .

In the Work pane, click the Policies tab.

Click the Security subtab.

Click Create KMIP Client Cert Policy .

In the Create KMIP Client Cert Policy dialog box that appears, enter the following information:

Name

Country Code

Description

The country code corresponding to the country in which the company resides.

Enter two alphabetic characters in upper case.

State The state or province in which the company requesting the certificate is headquartered.

Enter up to 32 characters.

Locality

Organization Name

Organization Unit Name

The city or town in which the company requesting the certificate is headquartered.

Enter up to 32 characters.

The organization requesting the certificate.

Enter up to 32 characters.

The organizational unit.

Enter up to 64 characters.

The email address associated with the request.

Email

Validity The validity period of the certificate.

Click OK .

Creating a KMIP Client Certificate Policy for a Server

You can create a KMIP client certificate policy for a server. This certificate is applicable only to the specific server, and overrides the global KMIP client certificate.

The hostname that used to create the certificate when using this policy is the serial number of the server.

Cisco UCS Manager Storage Management Guide, Release 4.2

109

SED Security Policies

Creating a KMIP Client Certificate Policy for a Server

SUMMARY STEPS

In the Navigation pane, click Equipment .

For C-Series and S-Series servers, expand Equipment > Rack-Mounts > Servers > Server ID .

For B-Series servers, expand Equipment > Chassis > Chassis ID > Servers > Server ID

In the Work pane, click the Inventory tab and then the Storage subtab.

Click the Security subtab.

Click Create KMIP Client Cert Policy .

In the Create KMIP Client Cert Policy dialog box that appears, enter the following information:

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click Equipment .

For C-Series and S-Series servers, expand Equipment > Rack-Mounts > Servers > Server ID .

For B-Series servers, expand Equipment > Chassis > Chassis ID > Servers > Server ID

In the Work pane, click the Inventory tab and then the Storage subtab.

Click the Security subtab.

Click Create KMIP Client Cert Policy .

In the Create KMIP Client Cert Policy dialog box that appears, enter the following information:

Name Description

Country Code

State

Locality

Organization Name

The country code corresponding to the country in which the company resides.

Enter two alphabetic characters in upper case.

The state or province in which the company requesting the certificate is headquartered.

Enter up to 32 characters.

The city or town in which the company requesting the certificate is headquartered.

Enter up to 32 characters.

The organization requesting the certificate.

Enter up to 32 characters.

Organization Unit Name

Email

Validity

The organizational unit.

Enter up to 64 characters.

The email address associated with the request.

The validity period of the certificate.

110

Cisco UCS Manager Storage Management Guide, Release 4.2

SED Security Policies

Managing Remote Security Policies

Step 8 Click OK .

Managing Remote Security Policies

Creating a Remote Security Policy

You can create a remote policy on a new or existing storage profile.

Before you begin

Ensure that you have created a KMIP client certificate policy.

SUMMARY STEPS

In the Navigation pane, click Storage > Storage Profiles .

Choose the storage profile where you want to create the policy.

Click the Security Policy tab and then click Create Security Policy or right-click the storage profile and select Create Security Policy .

Click the Remote Policy option.

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

In the Navigation pane, click Storage > Storage Profiles .

Choose the storage profile where you want to create the policy.

Click the Security Policy tab and then click Create Security Policy or right-click the storage profile and select Create

Security Policy .

Click the Remote Policy option.

a) Enter the primary server details in the IP Address/Hostname field.

b) (Optional) Enter the secondary server details in the IP Address/Hostname field.

c) (Optional) Enter the port number of the server in the Port field.

d) Enter the contents of the KMIP certificate in the KMIP Server Public Certificate field.

e) (Optional) Enter user credentials by clicking Add Login Details .

f) Click OK .

A message that policy was created successfully is displayed.

What to do next

The key thus created is associated to the storage profile for that server and is deployed under storage controller.

To verify this, go to Server ID > Inventory > Storage > Controller and select a SAS storage controller. Go to General tab and check whether the Security field shows as drive security enable .

Cisco UCS Manager Storage Management Guide, Release 4.2

111

SED Security Policies

Modifying a Remote Security Policy

SUMMARY STEPS

In the Navigation pane, click Storage > Storage Profiles .

Choose the storage profile where you have created the policy.

Click the Security Policy tab.

To modify the remote policy, in the Remote Policy area:

To change the security policy from Remote Policy to Local Policy :

Click Save Changes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click Storage > Storage Profiles .

Choose the storage profile where you have created the policy.

Click the Security Policy tab.

To modify the remote policy, in the Remote Policy area: a) Enter the primary server details in the IP Address/Hostname field.

b) (Optional) Enter the secondary server details in the IP Address/Hostname field.

c) (Optional) Enter the port number of the server in the Port field.

d) Enter the contents of the KMIP certificate in the KMIP Server Public Certificate field.

Save this certificate from the browser in base-64 format.

e) (Optional) Enter user credentials by clicking Add Login Details .

To change the security policy from Remote Policy to Local Policy : a) Click the Local Policy option.

b) Enter a new security key for the controller in the Key field.

Click Save Changes .

Modifying a Remote Security Key

SUMMARY STEPS

In the Navigation pane, click Equipment .

For C-Series and S-Series servers, expand Equipment > Rack-Mounts > Servers > Server ID .

For B-Series servers, expand Equipment > Chassis > Chassis ID > Servers > Server ID

In the Work area, click the Inventory tab.

Click the Storage subtab.

In the Controllers tab, select a SAS controller.

In the General tab, click Modify Remote Key .

112

Cisco UCS Manager Storage Management Guide, Release 4.2

SED Security Policies

Inserting a Secured Disk into a Server with a Remote Security Policy

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click Equipment .

For C-Series and S-Series servers, expand Equipment > Rack-Mounts > Servers > Server ID .

For B-Series servers, expand Equipment > Chassis > Chassis ID > Servers > Server ID

In the Work area, click the Inventory tab.

Click the Storage subtab.

In the Controllers tab, select a SAS controller.

In the General tab, click Modify Remote Key .

Inserting a Secured Disk into a Server with a Remote Security Policy

When you insert a secured disk into a server with a remote security policy, the storage disk will appear as a locked disk. Do one of the following:

• Unlock the disk manually with the local key if the disk was previously locked using the local key.

• Unlock using the remote KMIP server.

When you move a secured disk from a server with a local security policy to a server with a remote security policy, the disk will come up as locked. Unlock the disk manually with the local key.

Enabling and Disabling Security on Disks

Before you begin

• To enable security on a disk, ensure that the disk is a JBOD.

• To secure erase a disk, the disk must be in an unconfigured good state.

SUMMARY STEPS

In the Navigation pane, click Equipment .

For C-Series and S-Series servers, expand Equipment > Rack-Mounts > Servers > Server ID .

For B-Series servers, expand Equipment > Chassis > Chassis ID > Servers > Server ID

In the Work area, click the Inventory tab.

Click the Storage subtab.

In the Disks tab, select a disk.

In the Details area, click Enable Encryption .

To disable a secure disk, click Secure Erase .

DETAILED STEPS

Step 1 In the Navigation pane, click Equipment .

Cisco UCS Manager Storage Management Guide, Release 4.2

113

SED Security Policies

Disabling Security on a Controller

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

For C-Series and S-Series servers, expand Equipment > Rack-Mounts > Servers > Server ID .

For B-Series servers, expand Equipment > Chassis > Chassis ID > Servers > Server ID

In the Work area, click the Inventory tab.

Click the Storage subtab.

In the Disks tab, select a disk.

In the Details area, click Enable Encryption .

To disable a secure disk, click Secure Erase .

Disabling Security on a Controller

Before you begin

You can disable security only on SAS controllers. To disable security on controller, you must first disable security on all the secure disks and and delete all the secure virtual drives under the controller.

SUMMARY STEPS

In the Navigation pane, click Equipment .

For C-Series and S-Series servers, expand Equipment > Rack-Mounts > Servers > Server ID .

For B-Series servers, expand Equipment > Chassis > Chassis ID > Servers > Server ID

In the Work area, click the Inventory tab.

Click the Storage subtab.

In the Controllers tab, select a SAS controller.

In the General tab, click Disable Security .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click Equipment .

For C-Series and S-Series servers, expand Equipment > Rack-Mounts > Servers > Server ID .

For B-Series servers, expand Equipment > Chassis > Chassis ID > Servers > Server ID

In the Work area, click the Inventory tab.

Click the Storage subtab.

In the Controllers tab, select a SAS controller.

In the General tab, click Disable Security .

Unlocking a Locked Disk

When the key of an SED does not match the key on the controller, it shows the disk as Locked, Foreign Secure.

You must unlock the disks either by providing the security-key for that disk, or by using the remote KMIP server. After unlocking the disk, import or clear the foreign configuration.

114

Cisco UCS Manager Storage Management Guide, Release 4.2

SED Security Policies

Erasing a Secure Foreign Configuration Disk

SUMMARY STEPS

In the Navigation pane, click Equipment .

Expand Equipment > Rack-Mounts > Servers > Server Number .

In the Work area, click the Inventory tab.

Click the Storage subtab.

In the Controller tab, select a SAS controller.

To unlock a disk that is secured with a local security policy:

To unlock a disk that is secured with a remote KMIP server, in the General tab, click Unlock For Remote .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click Equipment .

Expand Equipment > Rack-Mounts > Servers > Server Number .

In the Work area, click the Inventory tab.

Click the Storage subtab.

In the Controller tab, select a SAS controller.

To unlock a disk that is secured with a local security policy: a) In the General tab, click Unlock Disk .

b) In the Key text box, provide the key that was used to lock the disk.

c) Click OK .

To unlock a disk that is secured with a remote KMIP server, in the General tab, click Unlock For Remote .

After you unlock a locked disk, the security status of the disk will show as Foreign Secure.

What to do next

Import or clear foreign configuration.

Erasing a Secure Foreign Configuration Disk

You can erase a secure foreign configuration disk when you have a disk in locked state and you want to use the disk without accessing the existing data.

SUMMARY STEPS

In the Navigation pane, click Equipment .

For C-Series and S-Series servers, expand Equipment > Rack-Mounts > Servers > Server ID .

For B-Series servers, expand Equipment > Chassis > Chassis ID > Servers > Server ID

In the Work area, click the Inventory tab.

Click the Storage subtab.

In the Disks tab, select a disk.

In the General tab, click Secure Erase Foreign Configuration .

Cisco UCS Manager Storage Management Guide, Release 4.2

115

SED Security Policies

Secure Data Deletion

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

In the Navigation pane, click Equipment .

For C-Series and S-Series servers, expand Equipment > Rack-Mounts > Servers > Server ID .

For B-Series servers, expand Equipment > Chassis > Chassis ID > Servers > Server ID

In the Work area, click the Inventory tab.

Click the Storage subtab.

In the Disks tab, select a disk.

In the General tab, click Secure Erase Foreign Configuration .

Secure Data Deletion

The Commission Regulation (EU) 2019/424 requires that data be securely disposed of.

Secure data disposal is accomplished by using commonly available tools that erase the data from the various/drives, memory, and storage in the Cisco UCS servers and reset them to factory settings.

Secure data deletion for compliance with Commission Regulation (EU) 2019/424 is supported for the followingCisco UCS servers:

• Cisco UCS B200

• Cisco UCS B480

• Cisco UCS C125

• Cisco UCS C220

• Cisco UCS C240

• Cisco UCS C480

• Cisco UCS S3260

You must be familiar with what devices are present in your UCS server and run the appropriate tools for secure data deletion. In some cases, you may need to run multiple tools.

Full instructions on how to securely erase data are available at: https://www.cisco.com/web/dofc/18794277.pdf

116

Cisco UCS Manager Storage Management Guide, Release 4.2

C H A P T E R

Storage Profiles

•

Storage Profiles, on page 117

•

Cisco Boot Optimized M.2 RAID Controller, on page 118

•

Disk Groups and Disk Group Configuration Policies, on page 118

•

RAID Levels, on page 124

•

Automatic Disk Selection, on page 125

•

Supported LUN Modifications, on page 126

•

Unsupported LUN Modifications, on page 126

•

Disk Insertion Handling, on page 127

•

Virtual Drive Naming, on page 128

•

LUN Dereferencing, on page 129

•

Controller Constraints and Limitations, on page 129

•

Storage Profiles, on page 131

•

Configuring Storage Profiles, on page 160

Storage Profiles

To allow flexibility in defining the number of storage disks, roles and usage of these disks, and other storage parameters, you can create and use storage profiles. A storage profile encapsulates the storage requirements for one or more service profiles. LUNs configured in a storage profile can be used as boot LUNs or data

LUNs, and can be dedicated to a specific server. You can also specify a local LUN as a boot device. However,

LUN resizing is not supported. The introduction of storage profiles allows you to do the following:

• Configure multiple virtual drives and select the physical drives that are used by a virtual drive. You can also configure the storage capacity of a virtual drive.

• Configure the number, type and role of disks in a disk group.

• Associate a storage profile with a service profile.

You can create a storage profile both at an org level and at a service-profile level. A service profile can have a dedicated storage profile as well as a storage profile at an org level.

Cisco UCS Manager Storage Management Guide, Release 4.2

117

Storage Profiles

Cisco Boot Optimized M.2 RAID Controller

Beginning with 4.0(4a), Cisco UCS Manager supports Cisco boot optimized M.2 RAID controller

(UCS-M2-HWRAID), which is based on Marvell 88SE92xx PCIe to SATA 6Gb/s controller. It is supported on the following servers:

• Cisco UCS C245 M6 Server

• Cisco UCS C220 M6 Server

• Cisco UCS C240 M6 Server

• Cisco UCS C220 M5 Server

• Cisco UCS C240 M5 Server

• Cisco UCS C480 M5 Server

• Cisco UCS B200 M5 Server

• Cisco UCS B480 M5 Server

The following M.2 drives are managed by the Cisco boot optimized M.2 RAID controller:

• 240GB M.2 6G SATA SSD

• 960GB M.2 6G SATA SSD

The Cisco boot optimized M.2 RAID controller supports only RAID1/JBOD (default - JBOD) mode and only

UEFI boot mode.

Limitations of Cisco boot optimized M.2 RAID controller

• Existing LUN migration is not supported.

• Local Disk Configuration policy is not supported.

• The number of LUNs that can be created is limited to one because creating a single LUN uses the entire disk capacity.

• LUN is created using the Local LUN tab (see

Configuring Local LUNs, on page 133 ) under storage

profile and not using the controller definitions.

• You cannot mix different capacity M.2 drives.

• You cannot rename an orphan virtual drive on a blade or a rack server.

Disk Groups and Disk Group Configuration Policies

Servers in a chassis can use storage that is centralized in that chassis. You can select and configure the disks to be used for storage. A logical collection of these physical disks is called a disk group. Disk groups allow you to organize local disks. The storage controller controls the creation and configuration of disk groups.

118

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

Virtual Drives

A disk group configuration policy defines how a disk group is created and configured. The policy specifies the RAID level to be used for the disk group. It also specifies either a manual or an automatic selection of disks for the disk group, and roles for disks. You can use a disk group policy to manage multiple disk groups.

However, a single disk group can be managed only by one disk group policy.

A hot spare is an unused extra disk that can be used by a disk group in the case of failure of a disk in the disk group. Hot spares can be used only in disk groups that support a fault-tolerant RAID level. In addition, a disk can be allocated as a global hot spare, which means that it can be used by any disk group.

Virtual Drives

A disk group can be partitioned into virtual drives. Each virtual drive appears as an individual physical device to the Operating System.

All virtual drives in a disk group must be managed by using a single disk group policy.

Configuration States

Indicates the configuration states of a virtual drive. Virtual drives can have the following configuration states:

• Applying—Creation of the virtual drive is in progress.

• Applied—Creation of the virtual drive is complete, or virtual disk policy changes are configured and applied successfully.

• Failed to apply—Creation, deletion, or renaming of a virtual drive has failed due to errors in the underlying storage subsystem.

• Orphaned—The service profile that contained this virtual drive is deleted or the service profile is no longer associated with a storage profile.

Note Orphaned LUNs cannot be used for booting OS. Although an image can be installed on these LUNs, booting from these drives will fail. To use any specific orphaned LUN, you must reassociate the storage profile, which will return it to the “Equipped” presence state.

• Not in use—The service profile that contained this virtual drive is in the disassociated state.

Deployment States

Indicates the actions that you are performing on virtual drives. Virtual drives can have the following deployment states:

• No action—No pending work items for the virtual drive.

• Creating—Creation of the virtual drive is in progress.

• Deleting—Deletion of the virtual drive is in progress.

• Modifying—Modification of the virtual drive is in progress.

• Apply-Failed—Creation or modification of the virtual drive has failed.

Cisco UCS Manager Storage Management Guide, Release 4.2

119

Storage Profiles

Configuring a Disk Group Policy

Operability States

Indicates the operating condition of a virtual drive. Virtual drives can have the following operability states:

• Optimal—The virtual drive operating condition is good. All configured drives are online.

• Degraded—The virtual drive operating condition is not optimal. One of the configured drives has failed or is offline.

• Cache-degraded—The virtual drive has been created with a write policy of write back mode, but the

BBU has failed, or there is no BBU.

Note This state does not occur if you select the always write back mode.

• Partially degraded—The operating condition in a RAID 6 virtual drive is not optimal. One of the configured drives has failed or is offline. RAID 6 can tolerate up to two drive failures.

• Offline—The virtual drive is not available to the RAID controller. This is essentially a failed state.

• Unknown—The state of the virtual drive is not known.

Presence States

Indicates the presence of virtual drive components. Virtual drives have the following presence states:

• Equipped—The virtual drive is available.

• Mismatched—A virtual drive deployed state is different from its configured state.

• Missing—Virtual drive is missing.

Configuring a Disk Group Policy

You can configure the disks in a disk group policy automatically or manually.

SUMMARY STEPS

In the Navigation pane, click Storage .

Expand Storage > Storage Provisioning > Storage Policies

Expand the node for the organization where you want to create the disk group policy.

Right-click Disk Group Policies in the organization and select Create Disk Group Policy .

In the Create Disk Group Policy dialog box, specify the following:

To automatically configure the disks in a disk group policy, select Disk Group Configuration (Automatic) and specify the following:

To manually configure the disks in a disk group policy, select Disk Group Configuration (Manual) and do the following:

In the Virtual Drive Configuration area, specify the following:

Click OK .

120

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

Configuring a Disk Group Policy

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click Storage .

Expand Storage > Storage Provisioning > Storage Policies

Expand the node for the organization where you want to create the disk group policy.

Right-click Disk Group Policies in the organization and select Create Disk Group Policy .

In the Create Disk Group Policy dialog box, specify the following:

Name Description

Name field The name of the policy

Description field A description of the policy. We recommend that you include information about where and when the policy should be used.

Enter up to 256 characters. You can use any characters or spaces except `(accent mark), \

(backslash), ^ (carat), " (double quote), = (equal sign), > (greater than), < (less than), or ' (single quote).

RAID Level drop-down list

This can be one of the following:

• RAID 0 Striped

• RAID 1 Mirrored

Note The Cisco boot optimized M.2 RAID controller (UCS-M2-HWRAID) supports only RAID1.

Note

• RAID 5 Striped Parity

• RAID 6 Striped Dual Parity

• RAID 10 Mirrored and Striped

When you create a disk group with RAID 1 policy and configure four disks for it, a

RAID 1E configuration is created internally by the storage controller.

Step 6 To automatically configure the disks in a disk group policy, select Disk Group Configuration (Automatic) and specify the following:

Note If you have a setup with the Cisco Boot Optimized M.2 Raid Controller (UCS-M2-HWRAID), then go to

Step 7, on page 122

Name Description

Number of drives field Specifies the number of drives for the disk group.

The range for drives is from 0 to 24 drives.

Unspecified is the default number of drives. When you select the number of drives as Unspecified , the number of drives will be selected according to the disk selection process.

Cisco UCS Manager Storage Management Guide, Release 4.2

121

Storage Profiles

Configuring a Disk Group Policy

Step 7

Name

Drive Type field

Description

Drive type for the disk group. You can select:

• HDD

• SSD

• Unspecified

Unspecified is the default type of drive. When you select the drive type as Unspecified , the first available drive is selected. After this drive is selected, subsequent drives will be of a compatible type. For example, if the first was SSD, all subsequent drives would be SSD.

Number of Hot Spares field

Number of dedicated hot spares for the disk group.

The range for dedicated hot spares is from 0 to 24 hot spares.

Unspecified is the default number of dedicated hot spares. When you select the number of dedicated hot spares as

Unspecified , the hot spares will be selected according to the disk selection process.

Min Drive Size field Minimum drive size for the disk group. Only disks that match this criteria are available for selection.

The range for minimum drive size is from 0 to 10240 GB.

Unspecified is the default minimum drive size. When you select the minimum drive size as Unspecified , drives of all sizes will be available for selection.

To manually configure the disks in a disk group policy, select Disk Group Configuration (Manual) and do the following: a) On the icon bar to the right of the table, click + b) In the Create Local Disk Configuration Reference dialog box, complete the following fields:

Name Description

Slot field Slot for which the local disk reference is configured.

Note M.2 drives typically have Slot IDs = 253, 254.

Additionally, verify the Slot IDs by navigating to Equipment > Server servernumber >

Inventory > Storage > Disks

Role field Note If you have a setup with the Cisco Boot Optimized M.2 Raid Controller

(UCS-M2-HWRAID), then select Normal (default). Selecting any other value results in configuration error.

Role of the local disk in the disk group. You can select:

• Normal

• Dedicated Hot Spare

• Global Hot Spare

Span ID field Note If you have a setup with the Cisco Boot Optimized M.2 Raid Controller

(UCS-M2-HWRAID), then this field does not apply. Leave the Span ID field as unspecified . Selecting any value results in configuration error.

122

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

Configuring a Disk Group Policy

Step 8

Name Description

Span ID for the local disk. The values range from 0 to 8.

Unspecified is the default Span ID of the local disk. Use this only when spanning information is not required.

In the Virtual Drive Configuration area, specify the following:

Note If you have a setup with the Cisco Boot Optimized M.2 Raid Controller (UCS-M2-HWRAID), then:

• You can create only one virtual drive

• For Strip Size (KB) , select 64KB or 32KB . Selecting any other value results in configuration error.

• For Access Policy , Read Policy , Write Cache Policy , IO Policy , and Drive Cache , select Platform

Default . Selecting any other value results in configuration error.

Name

Strip Size (KB) field

Access Policy field

Read Policy

Write Cache Policy

IO Policy field field field

Description

Stripe size for a virtual drive. This can only be Platform Default .

Access policy for a virtual drive. This can be one of the following:

• Platform Default

• Read Write

• Read Only

• Blocked

Read policy for a virtual drive. This can be one of the following:

• Platform Default

• Read Ahead

• Normal

Write-cache-policy for a virtual drive. This can be one of the following:

• Platform Default

• Write Through

• Write Back Good Bbu

• Always Write Back

I/O policy for a virtual drive. This can be one of the following:

• Platform Default

• Direct

• Cached

Cisco UCS Manager Storage Management Guide, Release 4.2

123

Storage Profiles

RAID Levels

Name

Drive Cache field

Description

State of the drive cache. This can be one of the following:

• Platform Default

• No Change

• Enable

• Disable

Step 9

All virtual drives in a disk group should be managed by using the same disk group policy.

Click OK .

Note When you accept the virtual drive (VD) default values and associate the disk group policy to a service profile, you can modify the VD configuration after it is associated to a service profile. If you modify the VD default values from the WebBIOS to use the non-default values, a properties fault is not generated to verify the changed values.

RAID Levels

The RAID level of a disk group describes how the data is organized on the disk group for the purpose of ensuring availability, redundancy of data, and I/O performance.

The following are features provided by RAID:

• Striping—Segmenting data across multiple physical devices. This improves performance by increasing throughput due to simultaneous device access.

• Mirroring—Writing the same data to multiple devices to accomplish data redundancy.

• Parity—Storing of redundant data on an additional device for the purpose of error correction in the event of device failure. Parity does not provide full redundancy, but it allows for error recovery in some scenarios.

• Spanning—Allows multiple drives to function like a larger one. For example, four 20 GB drives can be combined to appear as a single 80 GB drive.

The supported RAID levels include the following:

• RAID 0 Striped—Data is striped across all disks in the array, providing fast throughput. There is no data redundancy, and all data is lost if any disk fails.

• RAID 1 Mirrored—Data is written to two disks, providing complete data redundancy if one disk fails.

The maximum array size is equal to the available space on the smaller of the two drives.

• RAID 5 Striped Parity—Data is striped across all disks in the array. Part of the capacity of each disk stores parity information that can be used to reconstruct data if a disk fails. RAID 5 provides good data throughput for applications with high read request rates.

124

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

Automatic Disk Selection

RAID 5 distributes parity data blocks among the disks that are part of a RAID-5 group and requires a minimum of three disks.

• RAID 6 Striped Dual Parity—Data is striped across all disks in the array and two sets of parity data are used to provide protection against failure of up to two physical disks. In each row of data blocks, two sets of parity data are stored.

Other than addition of a second parity block, RAID 6 is identical to RAID 5 . A minimum of four disks are required for RAID 6.

• RAID 10 Mirrored and Striped—RAID 10 uses mirrored pairs of disks to provide complete data redundancy and high throughput rates through block-level striping. RAID 10 is mirroring without parity and block-level striping. A minimum of four disks are required for RAID 10.

• RAID 50 Striped Parity and Striped—Data is striped across multiple striped parity disk sets to provide high throughput and multiple disk failure tolerance.

• RAID 60 Striped Dual Parity and Striped—Data is striped across multiple striped dual parity disk sets to provide high throughput and greater disk failure tolerance.

Automatic Disk Selection

When you specify a disk group configuration, and do not specify the local disks in it, Cisco UCS Manager determines the disks to be used based on the criteria specified in the disk group configuration policy. Cisco

UCS Manager can make this selection of disks in multiple ways.

When all qualifiers match for a set of disks, then disks are selected sequentially according to their slot number.

Regular disks and dedicated hot spares are selected by using the lowest numbered slot.

The following is the disk selection process:

Iterate over all local LUNs that require the creation of a new virtual drive. Iteration is based on the following criteria, in order: a.

Disk type b.

Minimum disk size from highest to lowest c.

Space required from highest to lowest d.

Disk group qualifier name, in alphabetical order e.

Local LUN name, in alphabetical order

Select regular disks depending on the minimum number of disks and minimum disk size. Disks are selected sequentially starting from the lowest numbered disk slot that satisfies the search criteria.

Note If you specify Any as the type of drive, the first available drive is selected. After this drive is selected, subsequent drives will be of a compatible type. For example, if the first drive was SATA, all subsequent drives would be SATA. Cisco UCS Manager Release 2.5 supports only SATA and SAS.

Cisco UCS Manager Release 2.5 does not support RAID migration.

Cisco UCS Manager Storage Management Guide, Release 4.2

125

Storage Profiles

Supported LUN Modifications

Select dedicated hot spares by using the same method as normal disks. Disks are only selected if they are in an Unconfigured Good state.

If a provisioned LUN has the same disk group policy as a deployed virtual drive, then try to deploy the new virtual drive in the same disk group. Otherwise, try to find new disks for deployment.

Supported LUN Modifications

Some modifications that are made to the LUN configuration when LUNs are already deployed on an associated server are supported.

The following are the types of modifications that can be performed:

• Creation of a new virtual drive.

• Deletion of an existing virtual drive, which is in the orphaned state.

• Non-disruptive changes to an existing virtual drive. These changes can be made on an existing virtual drive without loss of data, and without performance degradation:

• Policy changes. For example, changing the write cache policy.

• Modification of boot parameters

The removal of a LUN will cause a warning to be displayed. Ensure that you take action to avoid loss of data.

Unsupported LUN Modifications

Some modifications to existing LUNs are not possible without destroying the original virtual drive and creating a new one. All data is lost in these types of modification, and these modifications are not supported.

Disruptive modifications to an existing virtual drive are not supported. The following are unsupported disruptive changes:

• Any supported RAID level change that can be handled through reconstruction. For example, RAID0 to

RAID1.

• Increasing the size of a virtual drive through reconstruction.

• Addition and removal of disks through reconstruction.

• Expand To Available option is not supported for already deployed LUN.

Destructive modifications are also not supported. The following are unsupported destructive modifications:

• RAID-level changes that do not support reconstruction. For example, RAID5 to RAID1.

• Shrinking the size of a virtual drive.

• RAID-level changes that support reconstruction, but where there are other virtual drives present on the same drive group.

• Disk removal when there is not enough space left on the disk group to accommodate the virtual drive.

• Explicit change in the set of disks used by the virtual drive.

126

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

Disk Insertion Handling

When the following sequence of events takes place:

The LUN is created in one of the following ways: a.

You specify the slot specifically by using a local disk reference b.

The system selects the slot based on criteria specified by you

The LUN is successfully deployed, which means that a virtual drive is created, which uses the slot.

You remove a disk from the slot, possibly because the disk failed.

You insert a new working disk into the same slot.

The following scenarios are possible:

•

Non-Redundant Virtual Drives, on page 127

•

Redundant Virtual Drives with No Hot Spare Drives, on page 127

•

Redundant Virtual Drives with Hot Spare Drives, on page 127

•

Replacing Hot Spare Drives, on page 128

•

Inserting Physical Drives into Unused Slots, on page 128

Non-Redundant Virtual Drives

For non-redundant virtual drives (RAID 0), when a physical drive is removed, the state of the virtual drive is

Inoperable . When a new working drive is inserted, the new physical drive goes to an Unconfigured Good state.

For non-redundant virtual drives, there is no way to recover the virtual drive. You must delete the virtual drive and re-create it.

Redundant Virtual Drives with No Hot Spare Drives

For redundant virtual drives (RAID 1, RAID 5, RAID 6, RAID 10, RAID 50, RAID 60) with no hot spare drives assigned, virtual drive mismatch, virtual drive member missing, and local disk missing faults appear until you insert a working physical drive into the same slot from which the old physical drive was removed.

If the physical drive size is greater than or equal to that of the old drive, the storage controller automatically uses the new drive for the virtual drive. The new drive goes into the Rebuilding state. After rebuild is complete, the virtual drive goes back into the Online state.

Redundant Virtual Drives with Hot Spare Drives

For redundant virtual drives (RAID 1, RAID 5, RAID 6, RAID 10, RAID 50, RAID 60) with hot spare drives assigned, when a drive fails, or when you remove a drive, the dedicated hot spare drive, if available, goes into

Cisco UCS Manager Storage Management Guide, Release 4.2

127

Storage Profiles

Replacing Hot Spare Drives the Rebuilding state with the virtual drive in the Degraded state. After rebuilding is complete, that drive goes to the Online state.

Cisco UCSM raises a disk missing and virtual drive mismatch fault because although the virtual drive is operational, it does not match the physical configuration that Cisco UCSM expects.

if you insert a new disk in the slot with the disk missing, automatic copy back starts from the earlier hot spare disk to the newly inserted disk. After copy back, the hot spare disk is restored. In this state all faults are cleared.

If automatic copy back does not start, and the newly inserted disk remains in the Unconfigured Good , JBOD , or Foreign Configuration state, remove the new disk from the slot, reinsert the earlier hot spare disk into the slot, and import foreign configuration. This initiates the rebuilding process and the drive state becomes Online .

Now, insert the new disk in the hot spare slot and mark it as hot spare to match it exactly with the information available in Cisco UCSM.

Replacing Hot Spare Drives

If a hot spare drive is replaced, the new hot spare drive will go to the Unconfigured Good , Unconfigured

Bad , JBOD , or Foreign Configuration state.

Cisco UCSM will raise a virtual drive mismatch or virtual drive member mismatch fault because the hot spare drive is in a state different from the state configured in Cisco UCSM.

You must manually clear the fault. To do this, you must perform the following actions:

Clear the state on the newly inserted drive to Unconfigured Good .

Configure the newly inserted drive as a hot spare drive to match what is expected by Cisco UCSM.

Inserting Physical Drives into Unused Slots

If you insert new physical drives into unused slots, neither the storage controller nor Cisco UCSM will make use of the new drive even if the drive is in the Unconfigured Good state and there are virtual drives that are missing good physical drives.

The drive will simply go into the Unconfigured Good state. To make use of the new drive, you will need to modify or create LUNs to reference the newly inserted drive.

Virtual Drive Naming

When you use Cisco UCS Manager to create a virtual drive, Cisco UCS Manager assigns a unique ID that can be used to reliably identify the virtual drive for further operations. Cisco UCS Manager also provides the flexibility to provide a name to the virtual drive at the time of service profile association. Any virtual drive without a service profile or a server reference is marked as an orphan virtual drive.

In addition to a unique ID, a name is assigned to the drive. Names can be assigned in two ways:

• When configuring a virtual drive, you can explicitly assign a name that can be referenced in storage profiles.

• If you have not preprovisioned a name for the virtual drive, Cisco UCS Manager generates a unique name for the virtual drive.

128

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

LUN Dereferencing

You can rename an orphan virtual drive on a blade or a rack server that are not referenced by any service profile or server.

Note The renaming an orphan virtual drive is not supported for Cisco boot optimized M.2 Raid controller

(UCS-M2-HWRAID).

LUN Dereferencing

A LUN is dereferenced when it is no longer used by any service profile. This can occur as part of the following scenarios:

• The LUN is no longer referenced from the storage profile

• The storage profile is no longer referenced from the service profile

• The server is disassociated from the service profile

• The server is decommissioned

When the LUN is no longer referenced, but the server is still associated, re-association occurs.

When the service profile that contained the LUN is disassociated, the LUN state is changed to Not in use .

When the service profile that contained the LUN is deleted, the LUN state is changed to Orphaned .

Controller Constraints and Limitations

• The following table provides the maximum supported virtual drives for servers:

Servers/Storage Controllers Maximum Virtual Drives

UCSB-MRAID12G-M6

UCSC-C220-M6, UCSC-C240-M6

UCSC-C240-M5, UCSC-C480-M5

UCS-S3260-M5, UCSC-C3X60-M4,

UCSC-C3K-M4

UCSC-C240-M4, UCSC-C240-M3,

UCSC-C24-M3

UCSB-MRAID12G

UCS-M2-HWRAID

For all other servers.

Cisco UCS Manager Storage Management Guide, Release 4.2

129

Storage Profiles

Controller Constraints and Limitations

Note • Storage controllers support the check max feature.

• When servers with multiple storage controllers are managed by the same storage profile, the maximum virtual drives are limited to the maximum value supported by the server.

• UCS-MSTOR-M2 and UCS-MSTOR-SD controllers are not supported on

M6 servers.

• The maximum supported storage controllers for the Cisco UCS C245 M6 Server C-series server is as follows:

Servers/Storage Controllers Maximum Virtual Drives

Cisco UCS C245 M6 Server • Dual UCS C245 M6SX

16 SAS/SATA HDD

• UCS C245 M6SX Plus

28 SAS/SATA HDD

• 2 M.2 2280 Drives on UCS-M2-HWRAID

• Directly Attached NVMe on rear risers(up to

4 NVMe SSD)

• The following table provides the maximum supported storage drives for the Cisco UCS C245 M6 Server

Servers/Storage Controllers Maximum Virtual Drives

UCS Cisco UCS C245 M6 x 28 HDD/SDD backplane

Up to 24 x 2.5-inch 12-Gbps Front load HDDs or

SSDs and 4 rear hot-swappable 2.5-inch NVMe drives, Total of 8 ( 4 front +4 rear) NVMe SSDs

Dual UCS C245 M6SX

12 SAS3 drives (12 per controller)

Cisco UCS C245 M6 x 24 HDD/SDD backplane UCS C245 M6SX Plus

24 SAS3 drives

UCS-M2-HWRAID M.2 modules with RAID 0/1 support

Only UCS-M2-HWRAID M.2 module support on

4 Front NVMe and 4 Rear NVMe drives

C245 M6

• In Cisco UCS Manager Release 2.2(4), blade servers do not support drives with a block size of 4K, but rack-mount servers support such drives. If a drive with a block size of 4K is inserted into a blade server, discovery fails and the following error message appears: Unable to get Scsi Device

Information from the system .

130

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

• In Cisco UCS Manager Release 3.1(2) and later releases, RAID Controller that does not support Out of band inventory (OOB) in C240 M4, M5, and M6 servers, display Operability as NA and Drive State as

Unknown .

Storage Profiles

Creating a Storage Profile

You can create storage profile policies from the Storage tab in the Navigation pane. Additionally, you can also configure the default storage profile that is specific to a service profile from the Servers tab.

Caution If you have a Cisco UCS blade or rack server with a default local disk configuration present in a Service

Profile or Service Profile Template from an earlier release of UCS Manager and you upgrade to the 3.1 release and later releases, you can successfully create a Storage Profile with local LUNs in the same Service Profile or Service Profile Template if you change the Local Disk Configuration Default policy to Any Configuration instead of RAID level options in the local disk policy. The legacy LUN is thereafter part of the storage inventory.

SUMMARY STEPS

In the Navigation pane, click Storage .

Expand Storage > Storage Profiles

Expand the node for the organization where you want to create the storage profile.

Right-click the organization and select Create Storage Profile .

In the Create Storage Profile dialog box, specify the storage profile Name . You can provide an optional

Description for this storage profile.

(Optional) In the LUNs area, create Local LUNs and add them to this storage profile.

(Optional) In the LUN Set area, create LUN Set and add them to this storage profile.

In the LUNs area, create Controller Definitions and add them to this storage profile.

In the LUNs area, create Security Policy and add them to this storage profile.

10.

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click Storage .

Expand Storage > Storage Profiles

Expand the node for the organization where you want to create the storage profile.

If the system does not include multi tenancy, expand the root node.

Right-click the organization and select Create Storage Profile .

In the Create Storage Profile dialog box, specify the storage profile Name . You can provide an optional Description for this storage profile.

Cisco UCS Manager Storage Management Guide, Release 4.2

131

Storage Profiles

Creating a Specific Storage Profile

Step 6

Step 7

Step 8

Step 9

Step 10

(Optional) In the LUNs area, create Local LUNs and add them to this storage profile.

See

Configuring Local LUNs, on page 133

for more information.

(Optional) In the LUN Set area, create LUN Set and add them to this storage profile.

See

Creating a LUN Set, on page 137

for more information.

In the LUNs area, create Controller Definitions and add them to this storage profile.

See

Creating a Storage Profile PCH Controller Definition, on page 147

for more information.

In the LUNs area, create Security Policy and add them to this storage profile.

See

Creating a Local Security Policy, on page 106

and

Creating a Remote Security Policy, on page 111

for more information.

Click OK .

Creating a Specific Storage Profile

SUMMARY STEPS

Expand Servers > Service Profiles .

Expand the node for the organization that contains the service profile for which you want to create a specific storage profile.

Choose the service profile for which you want to create a specific storage profile.

In the Work pane, click the Storage > LUN Configuration tab.

In the Actions area, click Modify Storage Profile .

In the Modify Storage Profile dialog box, click the Specific Storage Profile tab.

Click Create Specific Storage Profile .

(Optional) In the Specific Storage Profile area, complete the Description field to set the description of the storage profile.

In the Storage Items area, Create Local LUNs and add them to this storage profile.

10.

Click OK .

11.

If a confirmation dialog box displays, click Yes .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Expand Servers > Service Profiles .

Expand the node for the organization that contains the service profile for which you want to create a specific storage profile.

If the system does not include multi tenancy, expand the root node.

Choose the service profile for which you want to create a specific storage profile.

In the Work pane, click the Storage > LUN Configuration tab.

In the Actions area, click Modify Storage Profile .

In the Modify Storage Profile dialog box, click the Specific Storage Profile tab.

132

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

Deleting a Storage Profile

Step 7

Step 8

Step 9

Step 10

Step 11

Click Create Specific Storage Profile .

(Optional) In the Specific Storage Profile area, complete the Description field to set the description of the storage profile.

Each service profile can have only one specific storage profile. Hence, the name of this storage profile is provided by default.

In the Storage Items area, Create Local LUNs and add them to this storage profile.

Click OK .

If a confirmation dialog box displays, click Yes .

Deleting a Storage Profile

SUMMARY STEPS

In the Navigation pane, click Storage .

Expand Storage > Storage Profiles

Expand the node for the organization that contains the storage profile that you want to delete.

Right-click the storage profile that you want to delete and select Delete .

Click Yes in the confirmation box that appears.

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click Storage .

Expand Storage > Storage Profiles

Expand the node for the organization that contains the storage profile that you want to delete.

Right-click the storage profile that you want to delete and select Delete .

Click Yes in the confirmation box that appears.

Local LUNs

Configuring Local LUNs

You can create local LUNs within a storage profile policy from the Storage tab in the Navigation pane.

Additionally, you can also create local LUNs within the default storage profile that is specific to a service profile from the Servers tab.

SUMMARY STEPS

In the Navigation pane, click Storage .

Expand Storage > Storage Profiles

Expand the node for the organization that contains the storage profile within which you want to create a local LUN.

In the Work pane, click the General tab.

Cisco UCS Manager Storage Management Guide, Release 4.2

133

Storage Profiles

Configuring Local LUNs

In the Actions area, click Create Local LUN .

In the Create Local LUN dialog box, complete the following fields:

(Optional) Click Create Disk Group Policy to create a new disk group policy for this local LUN.

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click Storage .

Expand Storage > Storage Profiles

Expand the node for the organization that contains the storage profile within which you want to create a local LUN.

In the Work pane, click the General tab.

In the Actions area, click Create Local LUN .

In the Create Local LUN dialog box, complete the following fields:

Name

Create Local LUN option

Description

(Appears when you create a local LUN) Selected by default when you create a local LUN.

Prepare Claim Local LUN option

Name field

(Appears when you create a local LUN) Select when you want to claim an orphan LUN.

The name of the local LUN.

This name can be between 1 and 10 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 has been saved.

Note If the name given in Prepare Claim Local LUN is different from the name to be claimed, this LUN name and the Virtual drive name appearing in the LUN properties are different.

Size (GB) field Size of this LUN in GB. The size can range from 1 to 245760 GB.

Note You do not need to specify a LUN size while claiming an orphaned

LUN.

Note In a setup with the Cisco boot optimized M.2 Raid controller, this field is not grayed out. However, you do not have to populate this field. The system uses the full disk capacity to create the LUN, irrespective of the size specified.

Fractional Size (MB) field The fractional size of this LUN in MB.

134

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

Displaying Details of All Local LUNs Inherited By a Service Profile

Step 7

Step 8

Name

Auto Deploy radio buttons

Expand To Available checkbox

Select Disk Group Configuration drop-down list

Create Disk Group Policy link

Description

Whether the local LUN should be automatically deployed or not. This can be one of the following:

• Auto Deploy

—Automatically deploys the local LUN.

• No Auto Deploy

—Does no automatically deploy the local LUN.

(Only available for rack and blade servers) Specifies that this LUN can be expanded to use the entire available disk group.

For each service profile, only one LUN can use this option.

Expand To Available option is not supported for already deployed LUN.

Chose the disk group configuration to be applied to this local LUN from the drop-down list.

Displays the Create Disk Group Policy dialog box to create a new disk group.

(Optional) Click Create Disk Group Policy to create a new disk group policy for this local LUN.

Click OK .

Displaying Details of All Local LUNs Inherited By a Service Profile

Storage profiles can be defined under org and as a dedicated storage profile under service profile. Thus, a service profile inherits local LUNs from both possible storage profiles. It can have a maximum of 2 such local

LUNs. You can display the details of all local LUNs inherited by a service profile by using the following command:

SUMMARY STEPS

In the Navigation pane, click Servers .

Expand Servers > Service Profiles .

Expand the node for the organization that contains the service profile that you want to display.

Choose the service profile whose inherited local LUNs you want to display.

In the Work pane, click the Storage tab.

Click the Storage Profiles subtab, and then click the Local LUNs tab.

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

In the Navigation pane, click Servers .

Expand Servers > Service Profiles .

Expand the node for the organization that contains the service profile that you want to display.

Choose the service profile whose inherited local LUNs you want to display.

In the Work pane, click the Storage tab.

Cisco UCS Manager Storage Management Guide, Release 4.2

135

Storage Profiles

Deleting Local LUNs

Step 6 Click the Storage Profiles subtab, and then click the Local LUNs tab.

Displays the following detailed information about all the local LUNs inherited by the specified service profile:

• Name —LUN name in the storage profile.

• RAID Level —Summary of the RAID level of the disk group used.

• Size (MB) —Size, in MB, of the LUN specified in the storage profile.

• Config State —State of LUN configuration. The states can be one of the following:

• Applying —Admin state is online, the LUN is associated with a server, and the virtual drive is being created.

• Applied —Admin state is online, the LUN is associated with a server, and the virtual drive is created.

• Apply Failed —Admin stage is online, the LUN is associated with a server, but the virtual drive creation failed.

• Not Applied —The LUN is not associated with a server, or the LUN is associated with a service profile, but admin state is undeployed.

• Deploy Name —The virtual drive name after deployment.

• LUN ID —LUN ID.

• Drive State —State of the virtual drive. The states are:

• Unknown

• Optimal

• Degraded

• Inoperable

• Partially Degraded

Deleting Local LUNs

SUMMARY STEPS

In the Navigation pane, click Storage .

Expand Storage > Storage Profiles

Expand the node for the organization that contains the storage profile from which you want to delete a local LUN.

Expand Local LUNs for the storage profile that you want and select the LUN that you want to delete.

Right-click the LUN that you want to delete and select Delete .

Click Yes .

DETAILED STEPS

Step 1 In the Navigation pane, click Storage .

136

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

LUN Set

Step 2

Step 3

Step 4

Step 5

Step 6

Expand Storage > Storage Profiles

Expand the node for the organization that contains the storage profile from which you want to delete a local LUN.

Expand Local LUNs for the storage profile that you want and select the LUN that you want to delete.

Right-click the LUN that you want to delete and select Delete .

A confirmation dialog box appears.

Click Yes .

LUN Set

Beginning with release 4.0(2a), Cisco UCS Manager provides the ability to configure a range of disk slots into individual RAID0 LUNs using LUN Set option.

The following guidelines should be considered while creating a LUN Set:

• Only SSD and HDD types of disks are allowed.

• Upto 60 disks are allowed in one range.

• You cannot add the same set of disks in range under two different LUN Set configurations.

• If a disk is set in the disk slot range of LUN Set, then you cannot configure the same disk set in Local

LUN configuration under the same storage policy. Similarly, if a disk is set in Local LUN configuration, then you cannot use the same disk in the disk slot range of LUN Set.

• The server, in which the LUN Set is configured, should support OOB storage operations.

• You cannot configure a Local Disk Policy along with a Storage Policy in the same Service Profile.

• You cannot have the same name for a Local LUN and LUN Set.

• In S-series server PCH controllers, slots 201 and 202 do not support LUN Set.

Limitations of LUN Set

Cisco UCS Manager has the following limitations with LUN Set:

• You cannot claim orphaned Local LUNs into a LUN Set.

• Once created, you cannot modify a LUN Set. You should delete and create a new LUN Set with desired parameters.

• OS boot is not supported from LUN Set.

Creating a LUN Set

You can create LUN Set within a storage profile policy from the Storage tab in the Navigation pane.

Additionally, you can also create LUN Set within the default storage profile that is specific to a service profile from the Servers tab.

Cisco UCS Manager Storage Management Guide, Release 4.2

137

Storage Profiles

Creating a LUN Set

Before you begin

Ensure that the disk set which you are going to use to create LUN Set is in UnConfigured Good or JBOD drive state

Note If the disk drive state is in JBOD state, then you may experience data loss if you use the same disk in the slot range.

SUMMARY STEPS

In the Navigation pane, click Storage .

Expand Storage > Storage Profiles

Expand the node for the organization that contains the storage profile within which you want to create a

LUN Set.

In the Work pane, click the General tab.

In the Actions area, click Create LUN Set .

In the Create LUN Set dialog box, complete the following fields:

Click OK .

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click Storage .

Expand Storage > Storage Profiles

Expand the node for the organization that contains the storage profile within which you want to create a LUN Set.

In the Work pane, click the General tab.

In the Actions area, click Create LUN Set .

In the Create LUN Set dialog box, complete the following fields:

Name Description

Name field

RAID Level option

Disk Slot Range field

The name of the LUN Set.

This name can be between 1 and 10 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 has been saved.

Currently Cisco UCS Manager supports only RAID 0

Striped option.

The slot range for the disk.

138

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

Name

Strip Size (KB) drop-down list

Access Policy option

Read Policy option

Write Cache Policy option

Creating a LUN Set

Description

For striped virtual drives, the portion of the striped data segment that resides on each physical disk.

• Platform Default

• 8KB

• 16KB

• 32KB

• 64KB

• 128KB

• 256KB

• 512KB

• 1024KB

The type of access allowed. This can be one of the following:

• Platform Default

• Read Write

• Read only

• Blocked

The read-ahead cache mode. This can be one of the following:

• Platform Default

• Read Ahead

• Normal

This can be one of the following:

• Platform Default

• Write Through

• Write Back Good Bbu

• Always Write Back

Cisco UCS Manager Storage Management Guide, Release 4.2

139

Storage Profiles

Displaying the Details of a LUN Set

Name

IO Policy option

Drive Cache option

Description

This can be one of the following:

• Platform Default

• Direct

• Cached

This can be one of the following:

• Platform Default

• No Change

• Enable

• Disable

Select this check box to secure a virtual drive.

Step 7

Security checkbox

Click OK .

Displaying the Details of a LUN Set

SUMMARY STEPS

In the Navigation pane, click Servers .

Expand Servers > Service Profiles .

Expand the node for the organization that contains the service profile that you want to display.

Choose the service profile whose inherited local LUNs you want to display.

In the Work pane, click the Storage tab.

Click the Storage Profiles subtab, and then click the LUN Set tab.

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click Servers .

Expand Servers > Service Profiles .

Expand the node for the organization that contains the service profile that you want to display.

Choose the service profile whose inherited local LUNs you want to display.

In the Work pane, click the Storage tab.

Click the Storage Profiles subtab, and then click the LUN Set tab.

Displays the following detailed information about all the LUN Set inherited by the specified service profile:

140

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

Displaying the Details of a LUN Set

Table 8: LUN Set

Name

Name column

RAID Level option

Disk Slot Range field

Name

Name field

RAID Level option

Disk Slot Range field

Strip Size (KB) drop-down list

Access Policy option

Description

The name of the LUN Set.

Currently Cisco UCS Manager supports only RAID 0 Striped option.

The slot range for the disk.

Description

The name of the LUN Set.

This name can be between 1 and 10 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 has been saved.

Currently Cisco UCS Manager supports only RAID 0

Striped option.

The slot range for the disk.

For striped virtual drives, the portion of the striped data segment that resides on each physical disk.

• Platform Default

• 8KB

• 16KB

• 32KB

• 64KB

• 128KB

• 256KB

• 512KB

• 1024KB

The type of access allowed. This can be one of the following:

• Platform Default

• Read Write

• Read only

• Blocked

Cisco UCS Manager Storage Management Guide, Release 4.2

141

Storage Profiles

Deleting a LUN Set

Name

Read Policy option

Write Cache Policy option

IO Policy option

Drive Cache option

Description

The read-ahead cache mode. This can be one of the following:

• Platform Default

• Read Ahead

• Normal

This can be one of the following:

• Platform Default

• Write Through

• Write Back Good Bbu

• Always Write Back

This can be one of the following:

• Platform Default

• Direct

• Cached

This can be one of the following:

• Platform Default

• No Change

• Enable

• Disable

Select this check box to secure a virtual drive.

Security checkbox

Deleting a LUN Set

SUMMARY STEPS

In the Navigation pane, click Storage .

Expand Storage > Storage Profiles

Expand the node for the organization that contains the storage profile from which you want to delete a

LUN Set.

Expand LUN Set for the storage profile that you want and select the LUN Set that you want to delete.

Right-click the LUN Set that you want to delete and select Delete .

Click Yes .

142

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

Configuring Aero Controllers

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

In the Navigation pane, click Storage .

Expand Storage > Storage Profiles

Expand the node for the organization that contains the storage profile from which you want to delete a LUN Set.

Expand LUN Set for the storage profile that you want and select the LUN Set that you want to delete.

Right-click the LUN Set that you want to delete and select Delete .

A confirmation dialog box appears.

Click Yes .

Configuring Aero Controllers

Autoconfiguration Mode for Aero Storage Controllers

Cisco UCS C220M6/C240M6 C-series M6 servers support Aero PCIe SAS316-port storage controllers for

Direct Attached Storage. Aero controllers support an Autoconfiguration mode in which the state of a newly inserted disk is automatically moved to the Unconfigured-good state.

Because of this, you can choose whether or not to use Autoconfiguration by creating a Storage Profile and associating it with the server. The default is that the automatic configuration feature is disabled, which retains the drive state when the server is rebooted.

If Autoconfiguration is used, you must select a drive state from one of the following:

• unconfigured-good

• JBOD

• raid0-writeback

This is because the Aero firmware changes the behavior of systemPD to EPD-PT. EPD-PT is internally a

RAID0 volume without any drive DDF metadata. The controller stores the metadata for identifying it as a

RAID0 volume. The EPD-PT drives are considered as JBOD drives so the drive status is reported as JBOD and online.

The table below shows the behavior of Autoconfiguration in different scenarios.

Autoconfig Mode unconfigured-good (OFF)

Reboot/OCR

• All UG drives remain UG.

• All previously configured EPD remain EPD.

Hotplug

• Inserted drive remains UG

• EPD from a different server remains UG on this controller.

User Action

Disabling Autoconfig has no impact on the existing configuration

Cisco UCS Manager Storage Management Guide, Release 4.2

143

Storage Profiles

Creating an Autoconfiguration Storage Profile

Autoconfig Mode jbod (EPD-PT) raid0-writeback (RAID0

WB)

Reboot/OCR Hotplug User Action

• All UG are converted to EPD.

• Any UG will remain

UG until next boot.

Inserted device converted to EPD.

All UG drives on the controller while running

Autoconfig will be converted to EPD.

• During boot, UG is converted to UPD.

• All UG converted to

RAID0 WB.

• Any UG will remain

UG across control boot.

Inserted device converted to RAID0 WB.

All UG drives on the controller while running

Autoconfig will be converted to RAID0 WB.

Selecting EPD-PT (JBOD) as the default configuration does not retain the unconfigured-good state across host reboot. The drive state can be retained by disabling the automatic configuration feature. If the Autoconfig option is used, the default automatic configuration will always mark a drive as unconfigured-good.

When Autoconfig is selected, then the drive is configured to the desired drive state, the JBOD and unconfigured drives will set the drive state accordingly on the next controller boot or OCR,

The following table shows sample use cases for different Autoconfig scenarios.

Use Case Scenario

Using the server for JBOD Only (for example:

Hyper converged, Hadoop data node etc )

Autoconfig Option jbod

Using the server for RAID volume (for example:

SAP HANA database) unconfigured-good

Using the server for Mixed JBOD and RAID volume unconfigured-good

Using the server for per drive R0 WB (for example:

Hadoop data node) raid0-writeback

Creating an Autoconfiguration Storage Profile

The Autoconfiguration (Auto Config) mode option for storage is only available on Cisco UCS M6 servers with Aero controllers.

Step 1

Step 2

Step 3

Step 4

In the Navigation pane, click Storage .

Go to Profiles . Expand the root node.

Right click on Storage .

In the Create Storage Profile menu, name the profile. The menu will come up with Auto Config Mode marked as

Unspecified .

144

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

SPDM Authentication

Step 5

Step 6

To enable the Auto Config Mode option with a specific state to be retained on reboot, de-select Unspecified , then choose the desired state: Unconfigured Good, JBOD, or RAID 0. The state selection will be pushed to the BMC when the system is rebooted.

If Auto Config is left as Unspecified , it will retain whatever state was configured prior to reboot.

Note Service profile association will fail if no Aero controllers are present.

Click OK .

SPDM Authentication

The Security Protocol and Data Model (SPDM) is used by the BMC for authentication with the storage controller. It requires that the storage controller firmware is secure booted as well as having a Broadcom certificate chain installed in the slot0. During a firmware update, the Broadcom firmware will retain the older measurements for the storage firmware until the OCR or host reboots. If device authentication fails, the firmware will allow only inventory related commands and no set operations can be performed.

PCH Controller Definitions

PCH SSD Controller Definition

Cisco UCS Manager Platform Controller Hub (PCH) Solid State Drive (SSD) Controller Definition provides a local storage configuration in storage profiles where you can configure all the disks in a single RAID or in a JBOD disk array.

Note You must re-acknowledge the server if you remove or insert disks managed by the PCH Controller.

The PCH Controller Definition configuration provides the following features:

• Ability to configure a single LUN RAID across two internal SSDs connected to the onboard PCH controller

• A way to configure the controller in two modes: AHCI (JBOD) and SWRAID (RAID).

• Ability to configure the PCH storage device in an Embedded Local LUN and Embedded Local Disk boot policy so precision control for boot order is achieved even with the presence of other bootable local storage devices in the server. Do not use the Local LUN or the Local JBOD options to boot from PCH disks

• Scrub policy support for the internal SSD drives. This is applicable only for the SWRAID mode. This does not apply for the AHCI and NORAID of PCH Controller modes.

See the UCS Manager Server

Management Guide.

• Firmware upgrade support for the internal SSD drives.

• For M4 and below servers, disk firmware upgrade is supported only when the PCH Controller is in

SWRAID mode. It is not supported for AHCI mode.

• For M5 and higher servers, disk firmware upgrade is supported in both SWRAID and AHCI mode

(except Cisco UCS C125 M5 Server, which supports only AHCI mode) .

Cisco UCS Manager Storage Management Guide, Release 4.2

145

Storage Profiles

FCH Controller Configuration

You can configure PCH controller SSDs in a storage profile policy. You can enable or disable protect configuration which saves the LUN configuration even after a service profile disassociation. You choose a controller mode. The PCH controller configuration supports only these two RAID options: RAID0 and RAID1.

Use No RAID configuration option for AHCI mode where all the disks connected to the controller configured as JBOD disks. The configuration deployment happens as part of the storage profile association to a service profile process.

Cisco UCS Manager supports PCH managed internal SSDs in the following M4 servers:

• UCSC-C240-M4L

• UCSC-C240-M4SX

Cisco UCS Manager supports the following PCH managed SSDs on the M.2 card for all M5 and M6 servers

(except Cisco UCS C125 M5 Server):

• 240GB M.2 6G SATA SSD

• 960GB M.2 6G SATA SSD

Note You cannot have software RAID configuration in the controller definition and legacy boot mode configuration in boot policy together in M5 and M6 servers. Only UEFI boot mode is supported with software RAID configuration in the controller definition. This condition is applicable even if the drives are not used as boot drive.

For the PCH Controller Definition configuration in a Cisco UCS Manager boot policy two new devices exist to select: PCH LUN and PCH Disk.

EmbeddedLocalLun represents the boot device in SWRAID mode and

EmbeddedLocalDisk represent the boot devices in AHCI mode.

The system uses the same scrub policy is used to scrub supported SSDs. If the scrub is Yes, configured LUNs are destroyed as part of disassociation or re-discovery. If the scrub is No, configured LUNs are saved during disassociation and re-discovery.

Cisco UCS Manager supports firmware upgrade for the internal SSDs only when the PCH Controller is in

SWRAID mode. It is not supported in AHCI mode.

FCH Controller Configuration

Fusion Controller Hub (FCH) SSD Controller Definition provides a local storage configuration in storage profiles for AMD based Cisco UCS C125 M5 Server. For AMD processor based servers, the PCH controller is referred to as FCH controller. The controller type remains as PCH in the Cisco UCS Manager GUI.

The FCH Controller works the same as PCH Controller except for the following differences:

• FCH is only in AHCI (JBOD) mode.

Note Cisco UCS Manager GUI shows the RAID support as RAID0, RAID1 , however,

Cisco UCS C125 M5 Server supports only AHCI mode.

146

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

Creating a Storage Profile PCH Controller Definition

Note You must re-acknowledge the server if you remove or insert disks managed by the PCH Controller.

• There are two FCH controllers:

• First PCH controller manages SATA disks in the front panel (in the absence of a separate PCIe storage controller)

• Second PCH controller manages the M.2 SSDs

Note For Cisco UCS C125 M5 Server, the PCH IDs are 3 and 4.

Note Further information and procedures related to PCH controller in this document are applicable to both Intel and AMD based servers.

Creating a Storage Profile PCH Controller Definition

The PCH Controller Definition provides a storage configuration in Storage Profiles where you can configure internal SSDs connected to a PCH controller. You create a name for the controller definition, specify whether you want the storage profile to retain the configuration even if the storage profile is disassociated from the service profile, and chose the RAID level to indicate the controller mode.

Step 1

Step 2

Step 3

Step 4

In the Navigation pane, click Storage > Storage Profiles .

Choose the storage profile where you want to create the controller definition.

Click the Controller Definitions tab and then click Add at the bottom of the panel or right-click the storage profile and select Create Controller Definition .

In Create Controller Definition dialog box, configure the following information:

Name

Name field

Description

The name of the storage controller.

Note Once you save a PCH Controller Definition, you cannot modify the name from the General Tab Properties area.

Enter up to 16 characters. You can use any alphanumeric characters. Special characters and spaces are not supported.

Cisco UCS Manager Storage Management Guide, Release 4.2

147

Storage Profiles

Creating a Storage Profile PCH Controller Definition

Name

Protect Configuration check box

Description

If checked, the storage profile retains the configuration even if the storage profile is disassociated from the service profile.

Note If you disassociate the storage profile from a service profile with this option enabled, and then associate it with a new service profile that includes a local disk configuration policy with different properties, the server returns a configuration mismatch error and the association fails.

148

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

Name

RAID Level drop-down list

Description

Creating a Storage Profile PCH Controller Definition

Cisco UCS Manager Storage Management Guide, Release 4.2

149

Storage Profiles

Creating a Storage Profile PCH Controller Definition

Name Description

This can be one of the following disk policy modes:

• Disable Local Storage —(Supported for PCH SSD Controller Definition)

This disk policy mode is to disable the SATA AHCI Controller. This mode can be set only when disks are not present under the SATA AHCI controller. To re-enable this controller and to bring the controller back to its default value (AHCI), you can select No RAID or No Local Storage mode.

• No Local Storage —(Supported for PCH SSD Controller Definition) For a diskless server or a SAN only configuration. If you select this option, you cannot associate any service profile which uses this policy with a server that has a local disk.

• RAID 0 Striped —(Supported for PCH SSD Controller Definition) Data is striped across all disks in the array, providing fast throughput. There is no data redundancy, and all data is lost if any disk fails.

• RAID 1 Mirrored —(Supported for PCH SSD Controller Definition) Data is written to two disks, providing complete data redundancy if one disk fails. The maximum array size is equal to the available space on the smaller of the two drives.

• Any Configuration —(Supported for PCH SSD Controller Definition) For a server configuration that carries forward the local disk configuration without any changes.

• No RAID —(Supported for PCH SSD Controller Definition) All the disks can be used individually without interdependency similar to JBOD disks.

If you choose No RAID and you apply this policy to a server that already has an operating system with RAID storage configured, the system does not remove the disk contents. Therefore, there may be no visible differences on the server after you apply the No RAID mode. This can lead to a mismatch between the RAID configuration in the policy and the actual disk configuration shown in the Inventory > Storage tab for the server.

To make sure that any previous RAID configuration information is removed from a disk, apply a scrub policy that removes all disk information after you apply the No RAID configuration mode.

• RAID 5 Striped Parity —(Not supported for PCH SSD Controller

Definition) Data is striped across all disks in the array. Part of the capacity of each disk stores parity information that can be used to reconstruct data if a disk fails. RAID 5 provides good data throughput for applications with high read request rates.

• RAID 6 Striped Dual Parity —(Not supported for PCH SSD Controller

Definition) Data is striped across all disks in the array and two parity disks are used to provide protection against the failure of up to two physical disks. In each row of data blocks, two sets of parity data are stored.

• RAID 10 Mirrored and Striped —(Not supported for PCH SSD Controller

Definition) RAID 10 uses mirrored pairs of disks to provide complete data redundancy and high throughput rates.

150

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

Modifying a Service Profile PCH Controller Definition

Name Description

• RAID 50 Striped Parity and Striped —(Not supported for PCH SSD

Controller Definition) Data is striped across multiple striped parity disk sets to provide high throughput and multiple disk failure tolerance.

• RAID 60 Striped Dual Parity and Striped —(Not supported for PCH

SSD Controller Definition) Data is striped across multiple striped dual parity disk sets to provide high throughput and greater disk failure tolerance.

Note Some Cisco UCS servers require a license for certain RAID configuration options. When Cisco UCS Manager associates a service profile containing this local disk policy with a server,

Cisco UCS Manager verifies that the selected RAID option is properly licensed. If there are issues, Cisco UCS Manager displays a configuration error during the service profile association.

For RAID license information for a specific Cisco UCS server, see the Hardware Installation Guide for that server.

Step 5 Click OK.

The new PCH Controller Definition appears in the navigation pane.

What to do next

For specific operating system software RAID driver installation procedures, see:

• Installing LSI MegaSR Drivers for Windows and Linux section in the Cisco UCS C240 M4 Server

Installation and Service Guide

• Installing LSI MegaSR Drivers For Windows and Linux section in the Cisco UCS C220 M5 Server

Installation and Service Guide

• Installing LSI MegaSR Drivers For Windows and Linux section in the Cisco UCS C240 M5 Server

Installation and Service Guide

• Installing LSI MegaSR Drivers For Windows and Linux section in the Cisco UCS C480 M5 Server

Installation and Service Guide

Note For Cisco UCS B200 M5 Server and Cisco UCS B480 M5 Server software RAID driver installation, follow the same procedure as any of the above M5 servers.

Modifying a Service Profile PCH Controller Definition

Before you begin

If you want to modify RAID level from RAID 0 Striped or RAID 1 Mirrored to NO RAID , then perform the following steps before starting the procedure:

Cisco UCS Manager Storage Management Guide, Release 4.2

151

Storage Profiles

Modifying a Service Profile PCH Controller Definition

Ensure that you have a scrub policy in the associated service profile. Refer Creating a Service Profile with the Expert Wizard in Cisco UCS Manager Server Management Guide .

Disassociate the server from the service profile. Refer Disassociating a Service Profile from a Server or

Server Pool in Cisco UCS Manager Server Management Guide .

SUMMARY STEPS

In the Navigation pane, click the Storage tab.

Expand Storage Profiles to the specific storage profile name that you want.

Expand Controller Definitions and click the specific controller definition that you want.

On the General tab, modify the following information:

Click OK.

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

In the Navigation pane, click the Storage tab.

Expand Storage Profiles to the specific storage profile name that you want.

Expand Controller Definitions and click the specific controller definition that you want.

On the General tab, modify the following information:

Name

Name field

Description

The name of the storage controller.

Note Once you save a PCH Controller Definition, you cannot modify the name from the General Tab Properties area.

Protect Configuration check box

Enter up to 16 characters. You can use any alphanumeric characters. Special characters and spaces are not supported.

If checked, the storage profile retains the configuration even if the storage profile is disassociated from the service profile.

152

Cisco UCS Manager Storage Management Guide, Release 4.2

Storage Profiles

Name

RAID Level drop-down list

Description

Modifying a Service Profile PCH Controller Definition

Cisco UCS Manager Storage Management Guide, Release 4.2

153