Cisco UCS Manager CLI Unified Computing System Configuration Guide

PDF

مستند

Cisco UCS Manager CLI Configuration Guide, Release 2.2

First Published: 2013-12-11

Last Modified: 2016-07-27

Americas Headquarters

Cisco Systems, Inc.

170 West Tasman Drive

San Jose, CA 95134-1706

USA http://www.cisco.com

Tel: 408 526-4000

800 553-NETS (6387)

Fax: 408 527-0883

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,

INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,

EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH

THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,

CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright

1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.

CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT

LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS

HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http:// www.cisco.com/go/trademarks

. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

C O N T E N T S

P r e f a c e

C H A P T E R 1

Preface xxxiii

Audience

xxxiii

Conventions

xxxiii

Preface

•

Audience, page xxxiii

•

Conventions, page xxxiii

•

Documentation Feedback, page xxxv

Audience

This guide is intended primarily for data center administrators with responsibilities and expertise in one or more of the following:

• Server administration

• Storage administration

• Network administration

• Network security

Conventions

Text Type

GUI elements

Document titles

TUI elements

System output

Indication

GUI elements such as tab titles, area names, and field labels appear in this font.

Main titles such as window, dialog box, and wizard titles appear in this font.

Document titles appear in this font.

In a Text-based User Interface, text the system displays appears in this font.

Terminal sessions and information that the system displays appear in this font

Cisco UCS Manager CLI Configuration Guide, Release 2.2 xxxiii

Preface

Conventions

Text Type

CLI commands

[ ]

{x | y | z}

[x | y | z] string

< >

[ ]

!, #

Indication

CLI command keywords appear in this font.

Variables in a CLI command appear in this font.

Elements in square brackets are optional.

Required alternative keywords are grouped in braces and separated by vertical bars.

Optional alternative keywords are grouped in brackets and separated by vertical bars.

A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.

Nonprinting characters such as passwords are in angle brackets.

Default responses to system prompts are in square brackets.

An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line.

Note

Means reader take note. Notes contain helpful suggestions or references to material not covered in the document.

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.

xxxiv

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Preface

Related Cisco UCS Documentation

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

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 CLI Configuration Guide, Release 2.2 xxxv

Documentation Feedback

Preface xxxvi

Cisco UCS Manager CLI Configuration Guide, Release 2.2

C H A P T E R

Overview of Cisco Unified Computing System

This chapter includes the following sections:

•

About Cisco Unified Computing System , page 1

•

Unified Fabric, page 2

•

IPv6 Compliance, page 4

•

Server Architecture and Connectivity, page 5

•

CIMC Inband Management, page 10

•

Traffic Management, page 11

•

Opt-In Features, page 16

•

Virtualization in Cisco UCS , page 18

About Cisco Unified Computing System

Cisco Unified Computing System (Cisco UCS) fuses access layer networking and servers. This high-performance, next-generation server system provides a data center with a high degree of workload agility and scalability.

The hardware and software components support Cisco's unified fabric, which runs multiple types of data center traffic over a single converged network adapter.

Architectural Simplification

The simplified architecture of Cisco UCS reduces the number of required devices and centralizes switching resources. By eliminating switching inside a chassis, network access-layer fragmentation is significantly reduced.

Cisco UCS implements Cisco unified fabric within racks and groups of racks, supporting Ethernet and Fibre

Channel protocols over 10 Gigabit Cisco Data Center Ethernet and Fibre Channel over Ethernet (FCoE) links.

This radical simplification reduces the number of switches, cables, adapters, and management points by up to two-thirds. All devices in a Cisco UCS domain remain under a single management domain, which remains highly available through the use of redundant components.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Unified Fabric

High Availability

The management and data plane of Cisco UCS is designed for high availability and redundant access layer fabric interconnects. In addition, Cisco UCS supports existing high availability and disaster recovery solutions for the data center, such as data replication and application-level clustering technologies.

Scalability

A single Cisco UCS domain supports multiple chassis and their servers, all of which are administered through one Cisco UCS Manager. For more detailed information about the scalability, speak to your Cisco representative.

Flexibility

A Cisco UCS domain allows you to quickly align computing resources in the data center with rapidly changing business requirements. This built-in flexibility is determined by whether you choose to fully implement the stateless computing feature.

Pools of servers and other system resources can be applied as necessary to respond to workload fluctuations, support new applications, scale existing software and business services, and accommodate both scheduled and unscheduled downtime. Server identity can be abstracted into a mobile service profile that can be moved from server to server with minimal downtime and no need for additional network configuration.

With this level of flexibility, you can quickly and easily scale server capacity without having to change the server identity or reconfigure the server, LAN, or SAN. During a maintenance window, you can quickly do the following:

• Deploy new servers to meet unexpected workload demand and rebalance resources and traffic.

• Shut down an application, such as a database management system, on one server and then boot it up again on another server with increased I/O capacity and memory resources.

Optimized for Server Virtualization

Cisco UCS has been optimized to implement VM-FEX technology. This technology provides improved support for server virtualization, including better policy-based configuration and security, conformance with a company's operational model, and accommodation for VMware's VMotion.

Unified Fabric

With unified fabric, multiple types of data center traffic can run over a single Data Center Ethernet (DCE) network. Instead of having a series of different host bus adapters (HBAs) and network interface cards (NICs) present in a server, unified fabric uses a single converged network adapter. This type of adapter can carry

LAN and SAN traffic on the same cable.

Cisco UCS uses Fibre Channel over Ethernet (FCoE) to carry Fibre Channel and Ethernet traffic on the same physical Ethernet connection between the fabric interconnect and the server. This connection terminates at a converged network adapter on the server, and the unified fabric terminates on the uplink ports of the fabric interconnect. On the core network, the LAN and SAN traffic remains separated. Cisco UCS does not require that you implement unified fabric across the data center.

The converged network adapter presents an Ethernet interface and Fibre Channel interface to the operating system. At the server, the operating system is not aware of the FCoE encapsulation because it sees a standard

Fibre Channel HBA.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Fibre Channel over Ethernet

At the fabric interconnect, the server-facing Ethernet port receives the Ethernet and Fibre Channel traffic. The fabric interconnect (using Ethertype to differentiate the frames) separates the two traffic types. Ethernet frames and Fibre Channel frames are switched to their respective uplink interfaces.

Fibre Channel over Ethernet

Cisco UCS leverages Fibre Channel over Ethernet (FCoE) standard protocol to deliver Fibre Channel. The upper Fibre Channel layers are unchanged, so the Fibre Channel operational model is maintained. FCoE network management and configuration is similar to a native Fibre Channel network.

FCoE encapsulates Fibre Channel traffic over a physical Ethernet link. FCoE is encapsulated over Ethernet with the use of a dedicated Ethertype, 0x8906, so that FCoE traffic and standard Ethernet traffic can be carried on the same link. FCoE has been standardized by the ANSI T11 Standards Committee.

Fibre Channel traffic requires a lossless transport layer. Instead of the buffer-to-buffer credit system used by native Fibre Channel, FCoE depends upon the Ethernet link to implement lossless service.

Ethernet links on the fabric interconnect provide two mechanisms to ensure lossless transport for FCoE traffic:

• Link-level flow control

• Priority flow control

Link-Level Flow Control

IEEE 802.3x link-level flow control allows a congested receiver to signal the endpoint to pause data transmission for a short time. This link-level flow control pauses all traffic on the link.

The transmit and receive directions are separately configurable. By default, link-level flow control is disabled for both directions.

On each Ethernet interface, the fabric interconnect can enable either priority flow control or link-level flow control (but not both).

Priority Flow Control

The priority flow control (PFC) feature applies pause functionality to specific classes of traffic on the Ethernet link. For example, PFC can provide lossless service for the FCoE traffic, and best-effort service for the standard

Ethernet traffic. PFC can provide different levels of service to specific classes of Ethernet traffic (using IEEE

802.1p traffic classes).

PFC decides whether to apply pause based on the IEEE 802.1p CoS value. When the fabric interconnect enables PFC, it configures the connected adapter to apply the pause functionality to packets with specific CoS values.

By default, the fabric interconnect negotiates to enable the PFC capability. If the negotiation succeeds, PFC is enabled and link-level flow control remains disabled (regardless of its configuration settings). If the PFC negotiation fails, you can either force PFC to be enabled on the interface or you can enable IEEE 802.x

link-level flow control.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

IPv6 Compliance

IPv6 Compliance

Cisco UCS Manager supports IPv6 addressing. This is important for the following reasons:

• IPv4 addresses have a shorter address space than IPv6 addresses.

• The number of unique IPv4 addresses is finite, and the allocation scheme used by the Internet addressing body has exacerbated the decline of available addresses.

• IPv6 addresses have a larger address space, and the pool of available IPv6 addresses is much greater than the pool of IPv4 addresses.

• Some customers require that all networking software they purchase be IPv6 standards compliant.

All features in Cisco UCS Manager that support IPv4 addressing also support IPv6.

Note

Only public global unicast IPv6 addresses are supported.

IPv6 addresses can be used to configure inband access to management interfaces, the Cisco Cisco UCS

Manager GUI, the KVM Console, and SSH over SoL.

Note

IPv6 addresses are not supported for out-of-band access to CIMC.

Services Supported

Services that support IPv6 addresses include:

• HTTP and HTTPS

• SSH

• Telnet

• CIM XML

• SNMP

• Flash policy server

Client Support

External clients that support IPv6 addresses include:

• NTP

• DNS

• DHCP

• LDAP

• RADIUS

• TACACS+

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Server Architecture and Connectivity

• SSH

• Syslog

• vCenter

• Call Home

• NFS

Fabric Interconnects

Initial setup of the fabric interconnects supports the use of IPv6 addresses for the management IP address, default gateway and DNS servers.

In a cluster setup, if Fabric A is configured using IPv6 addresses and a cluster configuration is enabled, when

Fabric B is subsequently configured, the setup process retrieves the address type from Fabric A, and prompts you to use IPv6 addresses. IPv4 addresses then need to be configured for both fabric interconnects for out-of-band (OOB) access after initial setup is complete.

Cisco UCS Manager and the fabric interconnects support OOB access over both IPv4 and IPv6 addresses.

Configurations that Support IPv6 Addressing

IPv6 addresses can be used to configure key ring certificate requests, SNMP traps, management IP pools and address blocks, service profiles, service profile templates, VLAN groups, backup and restore operations, the core file exporter, the Cisco UCS Manager Syslog, NTP servers, ARP targets in the Management Interface

Monitoring policy, System Event Log (SEL) management, license management, firmware download, Call

Home, and vCenter.

LDAP, RADIUS and TACACS+ authentication service provider configurations all support IPv6 addressing.

Servers

Cisco UCS blade and rack servers can be configured to use static IPv6 addresses. Inband access to the server

Cisco Integrated Management Controller (CIMC) is possible using IPv6 addresses. Inband access is faster because management traffic flows between the fabric interconnects and the servers using the higher-bandwidth uplink port.

Note

Only Cisco UCS M3 and M4 servers support IPv6 addresses. IPv6 addressing for Cisco UCS M1 and M2 servers is not supported.

Server Architecture and Connectivity

Overview of Service Profiles

Service profiles are the central concept of Cisco UCS. Each service profile serves a specific purpose: ensuring that the associated server hardware has the configuration required to support the applications it will host.

The service profile maintains configuration information about the server hardware, interfaces, fabric connectivity, and server and network identity. This information is stored in a format that you can manage

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Overview of Service Profiles

through Cisco UCS Manager. All service profiles are centrally managed and stored in a database on the fabric interconnect.

Every server must be associated with a service profile.

Important

At any given time, each server can be associated with only one service profile. Similarly, each service profile can be associated with only one server at a time.

After you associate a service profile with a server, the server is ready to have an operating system and applications installed, and you can use the service profile to review the configuration of the server. If the server associated with a service profile fails, the service profile does not automatically fail over to another server.

When a service profile is disassociated from a server, the identity and connectivity information for the server is reset to factory defaults.

Network Connectivity through Service Profiles

Each service profile specifies the LAN and SAN network connections for the server through the Cisco UCS infrastructure and out to the external network. You do not need to manually configure the network connections for Cisco UCS servers and other components. All network configuration is performed through the service profile.

When you associate a service profile with a server, the Cisco UCS internal fabric is configured with the information in the service profile. If the profile was previously associated with a different server, the network infrastructure reconfigures to support identical network connectivity to the new server.

Configuration through Service Profiles

A service profile can take advantage of resource pools and policies to handle server and connectivity configuration.

Hardware Components Configured by Service Profiles

When a service profile is associated with a server, the following components are configured according to the data in the profile:

• Server, including BIOS and CIMC

• Adapters

• Fabric interconnects

You do not need to configure these hardware components directly.

Server Identity Management through Service Profiles

You can use the network and device identities burned into the server hardware at manufacture or you can use identities that you specify in the associated service profile either directly or through identity pools, such as

MAC, WWN, and UUID.

The following are examples of configuration information that you can include in a service profile:

• Profile name and description

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Overview of Service Profiles

• Unique server identity (UUID)

• LAN connectivity attributes, such as the MAC address

• SAN connectivity attributes, such as the WWN

Operational Aspects configured by Service Profiles

You can configure some of the operational functions for a server in a service profile, such as the following:

• Firmware packages and versions

• Operating system boot order and configuration

• IPMI and KVM access

vNIC Configuration by Service Profiles

A vNIC is a virtualized network interface that is configured on a physical network adapter and appears to be a physical NIC to the operating system of the server. The type of adapter in the system determines how many vNICs you can create. For example, a converged network adapter has two NICs, which means you can create a maximum of two vNICs for each adapter.

A vNIC communicates over Ethernet and handles LAN traffic. At a minimum, each vNIC must be configured with a name and with fabric and network connectivity.

vHBA Configuration by Service Profiles

A vHBA is a virtualized host bus adapter that is configured on a physical network adapter and appears to be a physical HBA to the operating system of the server. The type of adapter in the system determines how many vHBAs you can create. For example, a converged network adapter has two HBAs, which means you can create a maximum of two vHBAs for each of those adapters. In contrast, a network interface card does not have any HBAs, which means you cannot create any vHBAs for those adapters.

A vHBA communicates over FCoE and handles SAN traffic. At a minimum, each vHBA must be configured with a name and fabric connectivity.

Service Profiles that Override Server Identity

This type of service profile provides the maximum amount of flexibility and control. This profile allows you to override the identity values that are on the server at the time of association and use the resource pools and policies set up in Cisco UCS Manager to automate some administration tasks.

You can disassociate this service profile from one server, then associate it with another server. This re-association can be done either manually or through an automated server pool policy. The burned-in settings, such as UUID and MAC address on the new server are overwritten with the configuration in the service profile.

As a result, the change in the server is transparent to your network. You do not need to reconfigure any component or application on your network to begin using the new server.

This profile allows you to take advantage of and manage system resources through resource pools and policies, such as the following:

• Virtualized identity information, including pools of MAC addresses, WWN addresses, and UUIDs

• Ethernet and Fibre Channel adapter profile policies

• Firmware package policies

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Overview of Service Profiles

• Operating system boot order policies

Unless the service profile contains power management policies, a server pool qualification policy, or another policy that requires a specific hardware configuration, you can use the profile for any type of server in the

Cisco UCS domain.

You can associate these service profiles with either a rack-mount server or a blade server. The ability to migrate the service profile depends upon whether you choose to restrict migration of the service profile.

Note

If you choose not to restrict migration, Cisco UCS Manager does not perform any compatibility checks on the new server before migrating the existing service profile. If the hardware of both servers are not similar, the association might fail.

Service Profiles that Inherit Server Identity

This hardware-based service profile is the simplest to use and create. This profile uses the default values in the server and mimics the management of a rack-mounted server. It is tied to a specific server and cannot be moved or migrated to another server.

You do not need to create pools or configuration policies to use this service profile.

This service profile inherits and applies the identity and configuration information that is present at the time of association, such as the following:

• MAC addresses for the two NICs

• For a converged network adapter or a virtual interface card, the WWN addresses for the two HBAs

• BIOS versions

• Server UUID

Important

The server identity and configuration information inherited through this service profile might not have the values burned into the server hardware at the manufacturer if those values were changed before this profile is associated with the server.

Initial and Existing Templates

With a service profile template, you can quickly create several service profiles with the same basic parameters, such as the number of vNICs and vHBAs, and with identity information drawn from the same pools.

Tip

If you need only one service profile with similar values to an existing service profile, you can clone a service profile in the Cisco UCS Manager GUI.

For example, if you need several service profiles with similar values to configure servers to host database software, you can create a service profile template, either manually or from an existing service profile. You then use the template to create the service profiles.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Policies

Policies

Cisco UCS supports the following types of service profile templates:

Initial template

Service profiles created from an initial template inherit all the properties of the template. Service profiles created from an initial service profile template are bound to the template. However, changes to the initial template do not automatically propagate to the bound service profiles. If you want to propagate changes to bound service profiles, unbind and rebind the service profile to the initial template.

Updating template

Service profiles created from an updating template inherit all the properties of the template and remain connected to the template. Any changes to the template automatically update the service profiles created from the template.

Note

Service profiles that are created from the initial template and normal service profiles fetch the lowest available IDs in the sequential pool when you presReset.

Service profiles created from updating template might attempt to retain the same ID when you pressReset even when lower IDs of sequential pool are free.

Policies determine how Cisco UCS components will act in specific circumstances. You can create multiple instances of most policies. For example, you might want different boot policies, so that some servers can PXE boot, some can SAN boot, and others can boot from local storage.

Policies allow separation of functions within the system. A subject matter expert can define policies that are used in a service profile, which is created by someone without that subject matter expertise. For example, a

LAN administrator can create adapter policies and quality of service policies for the system. These policies can then be used in a service profile that is created by someone who has limited or no subject matter expertise with LAN administration.

You can create and use two types of policies in Cisco UCS Manager:

• Configuration policies that configure the servers and other components

• Operational policies that control certain management, monitoring, and access control functions

Pools

Pools are collections of identities, or physical or logical resources, that are available in the system. All pools increase the flexibility of service profiles and allow you to centrally manage your system resources.

You can use pools to segment unconfigured servers or available ranges of server identity information into groupings that make sense for the data center. For example, if you create a pool of unconfigured servers with similar characteristics and include that pool in a service profile, you can use a policy to associate that service profile with an available, unconfigured server.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

CIMC Inband Management

If you pool identifying information, such as MAC addresses, you can preassign ranges for servers that host specific applications. For example, you can configure all database servers within the same range of MAC addresses, UUIDs, and WWNs.

Domain Pools

Domain Pools are defined locally in a Cisco UCS domain, and can only be used in that Cisco UCS domain.

Global Pools

Global Pools are defined in Cisco UCS Central, and can be shared between Cisco UCS domains. If a Cisco

UCS domain is registered with Cisco UCS Central, you can assign Global Pools in Cisco UCS Manager.

CIMC Inband Management

A driving factor for providing inband management access to Cisco Integrated Management Controller (CIMC) is the desire to separate tenant traffic from provider traffic in multi-tenant, public or private service provider cloud deployments. Out-of-band (OOB) management traffic moves in and out of the fabric interconnects and traverses the management plane via the management port. This has the potential to cause bottlenecks and affect the CPU bandwidth in the management ports.

Inband management allows CIMC traffic to take the same path as the data traffic, entering and exiting the fabric interconnects via the uplink ports. The higher bandwidth available to the uplink ports means that inband access greatly speeds up management traffic, and reduces the risk of traffic bottlenecks and CPU stress. Both out-of-band (OOB) and inband address pools can be configured for management access in Cisco UCS Manager.

Out-of-band access only supports IPv4 addresses. Inband access supports both IPv4 and IPv6 addresses, which allows for single or dual stack management.

The two OOB management interface addresses that can be configured in Cisco UCS Manager blade and rack servers are:

• An OOB IPv4 address assigned to the physical server via the global ext-mgmt pool

• An OOB IPv4 address derived from a service profile associated with the physical server

In addition, up to four inband management interface addresses can be configured:

• An inband IPv4 address assigned to the physical server

• An inband IPv4 address derived from a service profile associated with the physical server

• An inband IPv6 address assigned to the physical server

• An inband IPv6 address derived from a service profile associated with the physical server

Multiple inband management IP addresses for each server support additional CIMC sessions. When you configure both OOB and inband addresses, users can choose from a list of those addresses in the KVM Console dialog box when they launch KVM from a server, SSH to SoL, a service profile, the KVM Launch Manager, or from the Cisco UCS Manager GUI web URL.

CIMC inband access supports the following services:

• KVM Console

• SSH to CIMC for SoL

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Inband Management Support

• vMedia for ISO, virtual CD/DVD, removable disk, and floppy

Note

Only Cisco UCS M3 and M4 servers support inband CIMC access. Inband CIMC access for Cisco UCS

M1 and M2 servers is not supported.

You can configure inband IP pools of IPv4 or IPv6 addresses and use them to assign addresses to servers.

You can configure inband VLAN groups and assign them to servers using service profiles.

You need to configure an Inband Profile with an Inband VLAN group to select an Inband Network (VLAN) in Service Profiles and Service Profile templates.

You can configure the network and IP pool name in an Inband profile to assign Inband CIMC addresses to

Cisco UCS M3 and M4 servers.

Inband Management Support

Inband management access is supported in Cisco UCS Manager for the following external services:

• KVM

• vMedia for ISO, virtual CD/DVD, removable disk, and floppy

• SSH to SoL

You can configure inband IP pools of IPv4 or IPv6 addresses and use them to assign addresses to servers.

You can configure inband VLAN groups and assign them to servers using service profiles.

Traffic Management

Oversubscription

Oversubscription occurs when multiple network devices are connected to the same fabric interconnect port.

This practice optimizes fabric interconnect use, since ports rarely run at maximum speed for any length of time. As a result, when configured correctly, oversubscription allows you to take advantage of unused bandwidth. However, incorrectly configured oversubscription can result in contention for bandwidth and a lower quality of service to all services that use the oversubscribed port.

For example, oversubscription can occur if four servers share a single uplink port, and all four servers attempt to send data at a cumulative rate higher than available bandwidth of uplink port.

Oversubscription Considerations

The following elements can impact how you configure oversubscription in a Cisco UCS domain:

Ratio of Server-Facing Ports to Uplink Ports

You need to know what how many server-facing ports and uplink ports are in the system, because that ratio can impact performance. For example, if your system has twenty ports that can communicate down to the

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Oversubscription

servers and only two ports that can communicate up to the network, your uplink ports will be oversubscribed.

In this situation, the amount of traffic created by the servers can also affect performance.

Number of Uplink Ports from Fabric Interconnect to Network

You can choose to add more uplink ports between the Cisco UCS fabric interconnect and the upper layers of the LAN to increase bandwidth. In Cisco UCS, you must have at least one uplink port per fabric interconnect to ensure that all servers and NICs to have access to the LAN. The number of LAN uplinks should be determined by the aggregate bandwidth needed by all Cisco UCS servers.

For the 6100 series fabric interconnects, Fibre Channel uplink ports are available on the expansion slots only.

You must add more expansion slots to increase number of available Fibre Channel uplinks. Ethernet uplink ports can exist on the fixed slot and on expansion slots.

For the 6200 series fabric interconnects running Cisco UCS Manager, version 2.0 and higher, Ethernet uplink ports and Fibre Channel uplink ports are both configurable on the base module, as well as on the expansion module.

For example, if you have two Cisco UCS 5100 series chassis that are fully populated with half width Cisco

UCS B200-M1 servers, you have 16 servers. In a cluster configuration, with one LAN uplink per fabric interconnect, these 16 servers share 20GbE of LAN bandwidth. If more capacity is needed, more uplinks from the fabric interconnect should be added. We recommend that you have symmetric configuration of the uplink in cluster configurations. In the same example, if 4 uplinks are used in each fabric interconnect, the 16 servers are sharing 80 GB of bandwidth, so each has approximately 5 GB of capacity. When multiple uplinks are used on a Cisco UCS fabric interconnect the network design team should consider using a port channel to make best use of the capacity.

Number of Uplink Ports from I/O Module to Fabric Interconnect

You can choose to add more bandwidth between I/O module and fabric interconnect by using more uplink ports and increasing the number of cables. In Cisco UCS, you can have one, two, or four cables connecting a I/O module to a Cisco UCS 6100 series fabric interconnect. You can have up to eight cables if you're connecting a 2208 I/O module and a 6248 fabric interconnect. The number of cables determines the number of active uplink ports and the oversubscription ratio.

Number of Active Links from Server to Fabric Interconnect

The amount of non-oversubscribed bandwidth available to each server depends on the number of I/O modules used and the number of cables used to connect those I/O modules to the fabric interconnects. Having a second

I/O module in place provides additional bandwidth and redundancy to the servers. This level of flexibility in design ensures that you can provide anywhere from 80 Gbps (two I/O modules with four links each) to 10

Gbps (one I/O module with one link) to the chassis.

With 80 Gbps to the chassis, each half-width server in the Cisco UCS domain can get up to 10 Gbps in a non-oversubscribed configuration, with an ability to use up to 20 Gbps with 2:1 oversubscription.

Guidelines for Estimating Oversubscription

When you estimate the optimal oversubscription ratio for a fabric interconnect port, consider the following guidelines:

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Pinning

Cost/Performance Slider

The prioritization of cost and performance is different for each data center and has a direct impact on the configuration of oversubscription. When you plan hardware usage for oversubscription, you need to know where the data center is located on this slider. For example, oversubscription can be minimized if the data center is more concerned with performance than cost. However, cost is a significant factor in most data centers, and oversubscription requires careful planning.

Bandwidth Usage

The estimated bandwidth that you expect each server to actually use is important when you determine the assignment of each server to a fabric interconnect port and, as a result, the oversubscription ratio of the ports.

For oversubscription, you must consider how many GBs of traffic the server will consume on average, the ratio of configured bandwidth to used bandwidth, and the times when high bandwidth use will occur.

Network Type

The network type is only relevant to traffic on uplink ports, because FCoE does not exist outside Cisco UCS.

The rest of the data center network only differentiates between LAN and SAN traffic. Therefore, you do not need to take the network type into consideration when you estimate oversubscription of a fabric interconnect port.

Pinning

Pinning in Cisco UCS is only relevant to uplink ports. You can pin Ethernet or FCoE traffic from a given server to a specific uplink Ethernet port or uplink FC port.

When you pin the NIC and HBA of both physical and virtual servers to uplink ports, you give the fabric interconnect greater control over the unified fabric. This control ensures more optimal utilization of uplink port bandwidth.

Cisco UCS uses pin groups to manage which NICs, vNICs, HBAs, and vHBAs are pinned to an uplink port.

To configure pinning for a server, you can either assign a pin group directly, or include a pin group in a vNIC policy, and then add that vNIC policy to the service profile assigned to that server. All traffic from the vNIC or vHBA on the server travels through the I/O module to the same uplink port.

Guidelines for Pinning

When you determine the optimal configuration for pin groups and pinning for an uplink port, consider the estimated bandwidth usage for the servers. If you know that some servers in the system will use a lot of bandwidth, ensure that you pin these servers to different uplink ports.

Quality of Service

Cisco UCS provides the following methods to implement quality of service:

• System classes that specify the global configuration for certain types of traffic across the entire system

• QoS policies that assign system classes for individual vNICs

• Flow control policies that determine how uplink Ethernet ports handle pause frames

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Quality of Service

Global QoS changes made to the QoS system class may result in brief data-plane interruptions for all traffic.

Some examples of such changes are:

• Changing the MTU size for an enabled class

• Changing packet drop for an enabled class

• Changing the CoS value for an enabled class

Guidelines and Limitations for Quality of Service on Cisco UCS 6300 Series Fabric Interconnect

• Cisco UCS 6300 Series Fabric Interconnect uses a shared buffer for all system classes.

• Multicast optimization is not supported.

• When you change the QoS parameters for any class causes traffic disruption to all classes. The following table lists the changes in the QoS system class and the conditions that trigger a system reboot.

QoS System class status

Enabled

Condition

Change between drop and no drop

FI Reboot Status

Yes

No-drop Yes

Enable and no-drop

Change between enable and disable

Change in MTU size Yes

• The subordinate FI reboots first as a result of the change in the QoS system class. The primary FI reboots only after you acknowledge it in Pending Activities.

Guidelines and Limitations for Quality of Service on Cisco UCS Mini

• Cisco UCS Mini uses a shared buffer for all system classes.

• The bronze class shares the buffer with SPAN. We recommend using either SPAN or the bronze class.

• Multicast optimization is not supported.

• Changing the QoS parameters for any class causes traffic disruption to all classes.

• When mixing Ethernet and FC or FCoE traffic, the bandwidth distribution is not equal.

• Multiple streams of traffic from the same class may not be distributed equally.

• Use the same CoS values for all no-drop policies to avoid any FC or FCoE performance issues.

• Only the platinum and gold classes support no-drop policies.

System Classes

Cisco UCS uses Data Center Ethernet (DCE) to handle all traffic inside a Cisco UCS domain. This industry standard enhancement to Ethernet divides the bandwidth of the Ethernet pipe into eight virtual lanes. Two virtual lanes are reserved for internal system and management traffic. You can configure quality of service

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Quality of Service

(QoS) for the other six virtual lanes. System classes determine how the DCE bandwidth in these six virtual lanes is allocated across the entire Cisco UCS domain.

Each system class reserves a specific segment of the bandwidth for a specific type of traffic, which provides a level of traffic management, even in an oversubscribed system. For example, you can configure the Fibre

Channel Priority system class to determine the percentage of DCE bandwidth allocated to FCoE traffic.

The following table describes the system classes that you can configure.

Table 1: System Classes

System Class

Platinum

Gold

Silver

Bronze

Best Effort

Fibre Channel

Description

A configurable set of system classes that you can include in the QoS policy for a service profile. Each system class manages one lane of traffic.

All properties of these system classes are available for you to assign custom settings and policies.

For Cisco UCS Mini, packet drop can only be disabled on the platinum and gold classes. Only one platinum and one gold class can be configured as a no drop class at a time.

A system class that sets the quality of service for the lane reserved for basic

Ethernet traffic.

Some properties of this system class are preset and cannot be modified. For example, this class has a drop policy that allows it to drop data packets if required. You cannot disable this system class.

A system class that sets the quality of service for the lane reserved for Fibre

Channel over Ethernet traffic.

Some properties of this system class are preset and cannot be modified. For example, this class has a no-drop policy that ensures it never drops data packets.

You cannot disable this system class.

Note

FCoE traffic has a reserved QoS system class that should not be used by any other type of traffic. If any other type of traffic has a CoS value that is used by FCoE, the value is remarked to 0.

Quality of Service Policy

A quality of service (QoS) policy assigns a system class to the outgoing traffic for a vNIC or vHBA. This system class determines the quality of service for that traffic. For certain adapters, you can also specify additional controls on the outgoing traffic, such as burst and rate.

You must include a QoS policy in a vNIC policy or vHBA policy and then include that policy in a service profile to configure the vNIC or vHBA.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Opt-In Features

Flow Control Policy

Flow control policies determine whether the uplink Ethernet ports in a Cisco UCS domain send and receive

IEEE 802.3x pause frames when the receive buffer for a port fills. These pause frames request that the transmitting port stop sending data for a few milliseconds until the buffer clears.

For flow control to work between a LAN port and an uplink Ethernet port, you must enable the corresponding receive and send flow control parameters for both ports. For Cisco UCS, the flow control policies configure these parameters.

When you enable the send function, the uplink Ethernet port sends a pause request to the network port if the incoming packet rate becomes too high. The pause remains in effect for a few milliseconds before traffic is reset to normal levels. If you enable the receive function, the uplink Ethernet port honors all pause requests from the network port. All traffic is halted on that uplink port until the network port cancels the pause request.

Because you assign the flow control policy to the port, changes to the policy have an immediate effect on how the port reacts to a pause frame or a full receive buffer.

Opt-In Features

Each Cisco UCS domain is licensed for all functionality. Depending upon how the system is configured, you can decide to opt in to some features or opt out of them for easier integration into existing environment. If a process change happens, you can change your system configuration and include one or both of the opt-in features.

The opt-in features are as follows:

• Stateless computing, which takes advantage of mobile service profiles with pools and policies where each component, such as a server or an adapter, is stateless.

• Multi-tenancy, which uses organizations and role-based access control to divide the system into smaller logical segments.

Stateless Computing

Stateless computing allows you to use a service profile to apply the personality of one server to a different server in the same Cisco UCS domain. The personality of the server includes the elements that identify that server and make it unique in the Cisco UCS domain. If you change any of these elements, the server could lose its ability to access, use, or even achieve booted status.

The elements that make up a server's personality include the following:

• Firmware versions

• UUID (used for server identification)

• MAC address (used for LAN connectivity)

• World Wide Names (used for SAN connectivity)

• Boot settings

Stateless computing creates a dynamic server environment with highly flexible servers. Every physical server in a Cisco UCS domain remains anonymous until you associate a service profile with it, then the server gets

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Multitenancy

the identity configured in the service profile. If you no longer need a business service on that server, you can shut it down, disassociate the service profile, and then associate another service profile to create a different identity for the same physical server. The "new" server can then host another business service.

To take full advantage of the flexibility of statelessness, the optional local disks on the servers should only be used for swap or temp space and not to store operating system or application data.

You can choose to fully implement stateless computing for all physical servers in a Cisco UCS domain, to not have any stateless servers, or to have a mix of the two types.

If You Opt In to Stateless Computing

Each physical server in the Cisco UCS domain is defined through a service profile. Any server can be used to host one set of applications, then reassigned to another set of applications or business services, if required by the needs of the data center.

You create service profiles that point to policies and pools of resources that are defined in the Cisco UCS domain. The server pools, WWN pools, and MAC pools ensure that all unassigned resources are available on an as-needed basis. For example, if a physical server fails, you can immediately assign the service profile to another server. Because the service profile provides the new server with the same identity as the original server, including WWN and MAC address, the rest of the data center infrastructure sees it as the same server and you do not need to make any configuration changes in the LAN or SAN.

If You Opt Out of Stateless Computing

Each server in the Cisco UCS domain is treated as a traditional rack mount server.

You create service profiles that inherit the identify information burned into the hardware and use these profiles to configure LAN or SAN connectivity for the server. However, if the server hardware fails, you cannot reassign the service profile to a new server.

Multitenancy

Multi-tenancy allows you to divide the large physical infrastructure of an Cisco UCS domain into logical entities known as organizations. As a result, you can achieve a logical isolation between organizations without providing a dedicated physical infrastructure for each organization.

You can assign unique resources to each tenant through the related organization in the multi-tenant environment.

These resources can include different policies, pools, and quality of service definitions. You can also implement locales to assign or restrict user privileges and roles by organization, if you do not want all users to have access to all organizations.

If you set up a multi-tenant environment, all organizations are hierarchical. The top-level organization is always root. The policies and pools that you create in root are system-wide and are available to all organizations in the system. However, any policies and pools created in other organizations are only available to organizations that are above it in the same hierarchy. For example, if a system has organizations named Finance and HR that are not in the same hierarchy, Finance cannot use any policies in the HR organization, and HR cannot access any policies in the Finance organization. However, both Finance and HR can use policies and pools in the root organization.

If you create organizations in a mult-itenant environment, you can also set up one or more of the following for each organization or for a sub-organization in the same hierarchy:

• Resource pools

• Policies

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Virtualization in Cisco UCS

• Service profiles

• Service profile templates

If You Opt In to Multitenancy

Each Cisco UCS domain is divided into several distinct organizations. The types of organizations you create in a multitenancy implementation depends upon the business needs of the company. Examples include organizations that represent the following:

• Enterprise groups or divisions within a company, such as marketing, finance, engineering, or human resources

• Different customers or name service domains, for service providers

You can create locales to ensure that users have access only to those organizations that they are authorized to administer.

If You Opt Out of Multitenancy

The Cisco UCS domain remains a single logical entity with everything in the root organization. All policies and resource pools can be assigned to any server in the Cisco UCS domain.

Virtualization in Cisco UCS

Overview of Virtualization

Virtualization allows you to create multiple Virtual Machines (VMs) to run in isolation, side by side on the same physical machine.

Each virtual machine has its own set of virtual hardware (RAM, CPU, NIC) upon which an operating system and fully configured applications are loaded. The operating system sees a consistent, normalized set of hardware regardless of the actual physical hardware components.

In a virtual machine, both hardware and software are encapsulated in a single file for rapid provisioning and moving between physical servers. You can move a virtual machine, within seconds, from one physical server to another for zero-downtime maintenance and continuous workload consolidation.

The virtual hardware makes it possible for many servers, each running in an independent virtual machine, to run on a single physical server. The advantages of virtualization include better use of computing resources, greater server density, and seamless server migration.

Overview of Cisco Virtual Machine Fabric Extender

A virtualized server implementation consists of one or more VMs that run as guests on a single physical server.

The guest VMs are hosted and managed by a software layer called the hypervisor or virtual machine manager

(VMM). Typically, the hypervisor presents a virtual network interface to each VM and performs Layer 2 switching of traffic from a VM to other local VMs or to another interface to the external network.

Working with a Cisco virtual interface card (VIC) adapter, the Cisco Virtual Machine Fabric Extender

(VM-FEX) bypasses software-based switching of VM traffic by the hypervisor for external hardware-based

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco Unified Computing System

Virtualization with Network Interface Cards and Converged Network Adapters

switching in the fabric interconnect. This method reduces the load on the server CPU, provides faster switching, and enables you to apply a rich set of network management features to local and remote traffic.

VM-FEX extends the IEEE 802.1Qbh port extender architecture to the VMs by providing each VM interface with a virtual Peripheral Component Interconnect Express (PCIe) device and a virtual port on a switch. This solution allows precise rate limiting and quality of service (QoS) guarantees on the VM interface.

Virtualization with Network Interface Cards and Converged Network Adapters

Network interface card (NIC) and converged network adapters support virtualized environments with the standard VMware integration with ESX installed on the server and all virtual machine management performed through the VC.

Portability of Virtual Machines

If you implement service profiles you retain the ability to easily move a server identity from one server to another. After you image the new server, the ESX treats that server as if it were the original.

Communication between Virtual Machines on the Same Server

These adapters implement the standard communications between virtual machines on the same server. If an

ESX host includes multiple virtual machines, all communications must go through the virtual switch on the server.

If the system uses the native VMware drivers, the virtual switch is out of the network administrator's domain and is not subject to any network policies. As a result, for example, QoS policies on the network are not applied to any data packets traveling from VM1 to VM2 through the virtual switch.

If the system includes another virtual switch, such as the Nexus 1000, that virtual switch is subject to the network policies configured on that switch by the network administrator.

Virtualization with a Virtual Interface Card Adapter

A Cisco VIC adapter is a converged network adapter (CNA) that is designed for both bare metal and VM-based deployments. The VIC adapter supports static or dynamic virtualized interfaces, which includes up to 128 virtual network interface cards (vNICs).

There are two types of vNICs used with the VIC adapter—static and dynamic. A static vNIC is a device that is visible to the OS or hypervisor. Dynamic vNICs are used for VM-FEX by which a VM is connected to a veth port on the Fabric Interconnect.

VIC adapters support VM-FEX to provide hardware-based switching of traffic to and from virtual machine interfaces.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Virtualization with a Virtual Interface Card Adapter

Overview of Cisco Unified Computing System

Cisco UCS Manager CLI Configuration Guide, Release 2.2

C H A P T E R

Overview of Cisco UCS Manager

This chapter includes the following sections:

•

About Cisco UCS Manager , page 21

•

Tasks You Can Perform in Cisco UCS Manager , page 22

•

Tasks You Cannot Perform in Cisco UCS Manager , page 24

•

Cisco UCS Manager in a High Availability Environment, page 24

About Cisco UCS Manager

Cisco UCS Manager is the management system for all components in a Cisco UCS domain. Cisco UCS

Manager runs within the fabric interconnect. You can use any of the interfaces available with this management service to access, configure, administer, and monitor the network and server resources for all chassis connected to the fabric interconnect.

Multiple Management Interfaces

Cisco UCS Manager includes the following interfaces you can use to manage a Cisco UCS domain:

• Cisco UCS Manager GUI

• Cisco UCS Manager CLI

• XML API

• KVM

• IPMI

Almost all tasks can be performed in any of the interfaces, and the results of tasks performed in one interface are automatically displayed in another.

However, you cannot do the following:

• Use Cisco UCS Manager GUI to invoke Cisco UCS Manager CLI.

• View the results of a command invoked through Cisco UCS Manager CLI in Cisco UCS Manager GUI.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco UCS Manager

Tasks You Can Perform in Cisco UCS Manager

• Generate CLI output from Cisco UCS Manager GUI.

Centralized Management

Cisco UCS Manager centralizes the management of resources and devices, rather than using multiple management points. This centralized management includes management of the following devices in a Cisco

UCS domain:

• Fabric interconnects.

• Software switches for virtual servers.

• Power and environmental management for chassis and servers.

• Configuration and firmware updates for server network interfaces (Ethernet NICs and converged network adapters).

• Firmware and BIOS settings for servers.

Support for Virtual and Physical Servers

Cisco UCS Manager abstracts server state information—including server identity, I/O configuration, MAC addresses and World Wide Names, firmware revision, and network profiles—into a service profile. You can apply the service profile to any server resource in the system, providing the same flexibility and support to physical servers, virtual servers, and virtual machines connected to a virtual device provided by a VIC adapter.

Role-Based Administration and Multi-Tenancy Support

Cisco UCS Manager supports flexibly defined roles so that data centers can use the same best practices with which they manage discrete servers, storage, and networks to operate a Cisco UCS domain. You can create user roles with privileges that reflect user responsibilities in the data center. For example, you can create the following:

• Server administrator roles with control over server-related configurations.

• Storage administrator roles with control over tasks related to the SAN.

• Network administrator roles with control over tasks related to the LAN.

Cisco UCS is multi-tenancy ready, exposing primitives that allow systems management software using the

API to get controlled access to Cisco UCS resources. In a multi-tenancy environment, Cisco UCS Manager enables you to create locales for user roles that can limit the scope of a user to a particular organization.

Tasks You Can Perform in Cisco UCS Manager

You can use Cisco UCS Manager to perform management tasks for all physical and virtual devices within a

Cisco UCS domain.

Cisco UCS Hardware Management

You can use Cisco UCS Manager to manage all hardware within a Cisco UCS domain, including the following:

• Chassis

• Servers

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco UCS Manager

Tasks You Can Perform in Cisco UCS Manager

• Fabric interconnects

• Fans

• Ports

• Interface cards

• I/O modules

Cisco UCS Resource Management

You can use Cisco UCS Manager to create and manage all resources within a Cisco UCS domain, including the following:

• Servers

• WWN addresses

• MAC addresses

• UUIDs

• Bandwidth

Server Administration

A server administrator can use Cisco UCS Manager to perform server management tasks within a Cisco UCS domain, including the following:

• Create server pools and policies related to those pools, such as qualification policies

• Create policies for the servers, such as discovery policies, scrub policies, and IPMI policies

• Create service profiles and, if desired, service profile templates

• Apply service profiles to servers

• Monitor faults, alarms, and the status of equipment

Network Administration

A network administrator can use Cisco UCS Manager to perform tasks required to create LAN configuration for a Cisco UCS domain, including the following:

• Configure uplink ports, port channels, and LAN PIN groups

• Create VLANs

• Configure the quality of service classes and definitions

• Create the pools and policies related to network configuration, such as MAC address pools and Ethernet adapter profiles

Storage Administration

A storage administrator can use Cisco UCS Manager to perform tasks required to create SAN configuration for a Cisco UCS domain, including the following:

• Configure ports, port channels, and SAN PIN groups

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco UCS Manager

Tasks You Cannot Perform in Cisco UCS Manager

• Create VSANs

• Configure the quality of service classes and definitions

• Create the pools and policies related to the network configuration, such as WWN pools and Fibre Channel adapter profiles

Tasks You Cannot Perform in Cisco UCS Manager

You cannot use Cisco UCS Manager to perform certain system management tasks that are not specifically related to device management within a Cisco UCS domain.

No Cross-System Management

You cannot use Cisco UCS Manager to manage systems or devices that are outside the Cisco UCS domain where Cisco UCS Manager is located. For example, you cannot manage heterogeneous environments, such as non-Cisco UCS x86 systems, SPARC systems, or PowerPC systems.

No Operating System or Application Provisioning or Management

Cisco UCS Manager provisions servers and, as a result, exists below the operating system on a server. Therefore, you cannot use it to provision or manage operating systems or applications on servers. For example, you cannot do the following:

• Deploy an OS, such as Windows or Linux

• Deploy patches for software, such as an OS or an application

• Install base software components, such as anti-virus software, monitoring agents, or backup clients

• Install software applications, such as databases, application server software, or web servers

• Perform operator actions, including restarting an Oracle database, restarting printer queues, or handling non-Cisco UCS user accounts

• Configure or manage external storage on the SAN or NAS storage

Cisco UCS Manager in a High Availability Environment

In a high availability environment with two fabric interconnects, you can run a separate instance of Cisco

UCS Manager on each fabric interconnect. The Cisco UCS Manager on the primary fabric interconnect acts as the primary management instance, and the Cisco UCS Manager on the other fabric interconnect is the subordinate management instance.

The two instances of Cisco UCS Manager communicate across a private network between the L1 and L2

Ethernet ports on the fabric interconnects. Configuration and status information is communicated across this private network to ensure that all management information is replicated. This ongoing communication ensures that the management information for Cisco UCS persists even if the primary fabric interconnect fails. In addition, the "floating" management IP address that runs on the primary Cisco UCS Manager ensures a smooth transition in the event of a failover to the subordinate fabric interconnect.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

C H A P T E R

Overview of Cisco UCS Manager CLI

This chapter includes the following sections:

•

Managed Objects, page 25

•

Command Modes, page 25

•

Object Commands, page 27

•

Complete a Command, page 28

•

Command History, page 28

•

Committing, Discarding, and Viewing Pending Commands, page 29

•

Online Help for the CLI, page 29

•

CLI Session Limits, page 29

•

Web Session Limits, page 29

•

Pre-Login Banner, page 30

Managed Objects

Cisco UCS uses a managed object model, where managed objects are abstract representations of physical or logical entities that can be managed. For example, servers, chassis, I/O cards, and processors are physical entities represented as managed objects, and resource pools, user roles, service profiles, and policies are logical entities represented as managed objects.

Managed objects may have one or more associated properties that can be configured.

Command Modes

The CLI is organized into a hierarchy of command modes, with the EXEC mode being the highest-level mode of the hierarchy. Higher-level modes branch into lower-level modes. You use create, enter, and scope commands to move from higher-level modes to modes in the next lower level , and you use the exit command to move up one level in the mode hierarchy.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco UCS Manager CLI

Command Modes

Note

Most command modes are associated with managed objects, so you must create an object before you can access the mode associated with that object. You use create and enter commands to create managed objects for the modes being accessed. The scope commands do not create managed objects and can only access modes for which managed objects already exist.

Each mode contains a set of commands that can be entered in that mode. Most of the commands available in each mode pertain to the associated managed object. Depending on your assigned role and locale, you may have access to only a subset of the commands available in a mode; commands to which you do not have access are hidden.

The CLI prompt for each mode shows the full path down the mode hierarchy to the current mode. This helps you to determine where you are in the command mode hierarchy, and it can be an invaluable tool when you need to navigate through the hierarchy.

The following table lists the main command modes, the commands used to access each mode, and the CLI prompt associated with each mode.

Table 2: Main Command Modes and Prompts

Mode Name

EXEC adapter chassis

Ethernet server

Ethernet uplink fabric-interconnect

Fibre Channel uplink firmware

Host Ethernet interface

Host Fibre Channel interface

Commands Used to Access

top command from any mode

Mode Prompt

/adapter # scope adapter command from

EXEC mode

scope chassis command from

EXEC mode

/chassis #

scope eth-server command from

EXEC mode

/eth-server #

scope eth-uplink command from

EXEC mode

/eth-uplink #

scope fabric-interconnect

command from EXEC mode

/fabric-interconnect #

scope fc-uplink command from

EXEC mode

scope firmware command from

EXEC mode

/fc-uplink #

/firmware #

scope host-eth-if command from

EXEC mode

/host-eth-if #

scope host-fc-if command from

EXEC mode

/host-fc-if #

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco UCS Manager CLI

Object Commands

Mode Name

monitoring organization security server service-profile system virtual HBA virtual NIC

Commands Used to Access Mode Prompt

scope monitoring command from

EXEC mode

/monitoring #

scope org command from EXEC mode

/org #

scope security command from

EXEC mode

/security #

scope server command from

EXEC mode

scope service-profile command from EXEC mode

/server #

/service-profile #

scope system command from

EXEC mode

/system #

scope vhba command from EXEC mode

/vhba #

scope vnic command from EXEC mode

/vnic #

Object Commands

Four general commands are available for object management:

• create object

• delete object

• enter object

• scope object

You can use the scope command with any managed object, whether a permanent object or a user-instantiated object. The other commands allow you to create and manage user-instantiated objects. For every create object command, a corresponding delete object and enter object command exists.

In the management of user-instantiated objects, the behavior of these commands depends on whether the object exists, as described in the following tables:

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco UCS Manager CLI

Complete a Command

Table 3: Command behavior if the object does not exist

Command

create object

delete object

enter object

scope object

Behavior

The object is created and its configuration mode, if applicable, is entered.

An error message is generated.

The object is created and its configuration mode, if applicable, is entered.

An error message is generated.

Table 4: Command behavior if the object exists

Command

create object

delete object

enter object

scope object

Behavior

An error message is generated.

The object is deleted.

The configuration mode, if applicable, of the object is entered.

The configuration mode of the object is entered.

Complete a Command

You can use the Tab key in any mode to complete a command. Partially typing a command name and pressing

Tab causes the command to be displayed in full or to the point where another keyword must be chosen or an argument value must be entered.

Command History

The CLI stores all commands used in the current session. You can step through the previously used commands by using the Up Arrow or Down Arrow keys. The Up Arrow key steps to the previous command in the history, and the Down Arrow key steps to the next command in the history. If you get to the end of the history, pressing the Down Arrow key does nothing.

All commands in the history can be entered again by simply stepping through the history to recall the desired command and pressing Enter. The command is entered as if you had manually typed it. You can also recall a command and change it before you press Enter.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco UCS Manager CLI

Committing, Discarding, and Viewing Pending Commands

Committing, Discarding, and Viewing Pending Commands

When you enter a configuration command in the CLI, the command is not applied until you enter the

commit-buffer command. Until committed, a configuration command is pending and can be discarded by entering a discard-buffer command.

You can accumulate pending changes in multiple command modes and apply them together with a single

commit-buffer command. You can view the pending commands by entering the show configuration pending command in any command mode.

Note

Committing multiple commands together is not an atomic operation. If any command fails, the successful commands are applied despite the failure. Failed commands are reported in an error message.

While any commands are pending, an asterisk (*) appears before the command prompt. The asterisk disappears when you enter the commit-buffer command.

The following example shows how the prompts change during the command entry process: switch-1#

scope chassis 1

switch-1 /chassis #

enable locator-led

switch-1 /chassis* #

show configuration pending

scope chassis 1

+ exit enable locator-led switch-1 /chassis* #

commit-buffer

switch-1 /chassis #

Online Help for the CLI

At any time, you can type the ? character to display the options available at the current state of the command syntax.

If you have not typed anything at the prompt, typing ? lists all available commands for the mode you are in.

If you have partially typed a command, typing ? lists all available keywords and arguments available at your current position in the command syntax.

CLI Session Limits

Cisco UCS Manager limits the number of CLI sessions that can be active at one time to 32 total sessions. This value is not configurable.

Web Session Limits

Web session limits are used by Cisco UCS Manager to restrict the number of web sessions (both GUI and

XML) permitted access to the system at any one time.

By default, the number of concurrent web sessions allowed by Cisco UCS Manager is set to the maximum value: 256.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco UCS Manager CLI

Setting the Web Session Limit for Cisco UCS Manager from the CLI

Setting the Web Session Limit for Cisco UCS Manager from the CLI

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

UCS-A# scope system

Purpose

Enters system mode.

UCS-A /system # scope services Enters system services mode.

UCS-A /system/services # scope

web-session-limits

Enters system services web session limits mode.

UCS-A /system/services/web-session-limits

# set total num-of-logins-total

The maximum number of concurrent HTTP and

HTTPS sessions allowed for all users within the system.

Enter an integer between 1 and 256.

UCS-A /system/services/web-session-limits

# commit-buffer

Commits the transaction to the system configuration.

The following example sets the maximum number of HTTP and HTTPS sessions allowed by the system to

200 and commits the transaction:

UCS-A#

scope system

UCS-A /system #

scope services

UCS-A /system/services #

scope web-session-limits

UCS-A /system/services/web-session-limits* #

set total 200

UCS-A /system/services/web-session-limits* #

commit-buffer

UCS-A /system/services/web-session-limits #

Pre-Login Banner

With a pre-login banner, when a user logs into Cisco UCS Manager GUI, Cisco UCS Manager displays the banner text in the Create Pre-Login Banner dialog box and waits until the user dismisses that dialog box before it prompts for the username and password. When a user logs into Cisco UCS Manager CLI, Cisco UCS

Manager displays the banner text in a dialog box and waits for the user to dismiss that dialog box before it prompts for the password. It then repeats the banner text above the copyright block that it displays to the user.

Creating the Pre-Login Banner

Procedure

Step 1

Command or Action

UCS-A# scope security

Purpose

Enters security mode.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco UCS Manager CLI

Modifying the Pre-Login Banner

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

UCS-A /security # scope banner

Purpose

Enters banner security mode.

UCS-A /security/banner # create

pre-login-banner

Creates a pre login banner.

UCS-A

/security/banner/pre-login-banner # set

message

Specifies the message that Cisco UCS Manager displays to the user before it displays the login prompt for the Cisco UCS Manager GUI or CLI.

You can enter any standard ASCII character in this field.

Launches a dialog for entering the pre-login banner message text.

At the prompt, type a pre-login banner message and press Enter.

On the line following your input, type ENDOFBUF to finish.

Press Ctrl and C to cancel out of the set message dialog.

UCS-A

/security/banner/pre-login-banner #

commit-buffer

Commits the transaction to the system configuration.

The following example creates the pre-login banner:

UCS-A#

scope security

UCS-A /security #

scope banner

UCS-A /security/banner #

create pre-login-banner

UCS-A /security/banner/pre-login-banner* #

set message

Enter lines one at a time. Enter ENDOFBUF to finish. Press ^C to abort.

Enter prelogin banner:

>Welcome to UCS System 1

>ENDOFBUF

UCS-A /security/banner/pre-login-banner* #

commit-buffer

UCS-A /security/banner/pre-login-banner #

Modifying the Pre-Login Banner

Procedure

Step 1

Step 2

Step 3

Command or Action

UCS-A# scope security

UCS-A /security # scope banner

UCS-A /security/banner # scope

pre-login-banner

Purpose

Enters security mode.

Enters banner security mode.

Enters pre-login-banner banner security mode.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco UCS Manager CLI

Deleting the Pre-Login Banner

Step 4

Step 5

Step 6

Command or Action Purpose

UCS-A

/security/banner/pre-login-banner # set

message

Specifies the message that Cisco UCS Manager displays to the user before it displays the login prompt for the Cisco UCS Manager GUI or CLI.

You can enter any standard ASCII character in this field.

Launches a dialog for entering the pre-login banner message text.

At the prompt, modify the pre-login banner message and press Enter.

On the line following your input, type ENDOFBUF to finish.

Press Ctrl and C to cancel out of the set message dialog.

Commits the transaction to the system configuration.

UCS-A

/security/banner/pre-login-banner #

commit-buffer

The following example modifies the pre-login banner:

UCS-A#

scope security

UCS-A /security #

scope banner

UCS-A /security/banner #

create pre-login-banner

UCS-A /security/banner/pre-login-banner* #

set message

Enter lines one at a time. Enter ENDOFBUF to finish. Press ^C to abort.

Enter prelogin banner:

Welcome to UCS System 1

ENDOFBUF

UCS-A /security/banner/pre-login-banner* #

commit-buffer

UCS-A /security/banner/pre-login-banner #

Deleting the Pre-Login Banner

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope security

UCS-A /security # scope banner

UCS-A /security/banner # delete

pre-login-banner

UCS-A /security/banner # commit-buffer

Purpose

Enters security mode.

Enters banner security mode.

Deletes the pre-login banner from the system.

Commits the transaction to the system configuration.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Overview of Cisco UCS Manager CLI

The following example deletes the pre-login banner:

UCS-A#

scope security

UCS-A /security #

scope banner

UCS-A /security/banner #

delete pre-login-banner

UCS-A /security/banner* #

commit-buffer

UCS-A /security/banner #

Deleting the Pre-Login Banner

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Deleting the Pre-Login Banner

Overview of Cisco UCS Manager CLI

Cisco UCS Manager CLI Configuration Guide, Release 2.2

C H A P T E R

Configuring the Fabric Interconnects

This chapter includes the following sections:

•

Initial System Setup, page 35

•

Performing an Initial System Setup for a Standalone Configuration, page 37

•

Initial System Setup for a Cluster Configuration, page 39

•

Enabling a Standalone Fabric Interconnect for Cluster Configuration, page 44

•

Changing the System Name, page 45

•

Changing the Management Subnet of a Cluster, page 46

•

Changing the Management Prefix of a Cluster, page 47

•

Configuring the Information Policy on the Fabric Interconnect, page 48

•

Fabric Evacuation, page 51

•

Ethernet Switching Mode, page 56

•

Configuring Ethernet Switching Mode, page 57

•

Fibre Channel Switching Mode, page 58

•

Configuring Fibre Channel Switching Mode, page 59

Initial System Setup

The first time that you access a fabric interconnect in a Cisco UCS domain, a setup wizard prompts you for the following information required to configure the system:

• Installation method (GUI or CLI)

• Setup mode (restore from full system backup or initial setup)

• System configuration type (standalone or cluster configuration)

• System name

• Admin password

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Setup Mode

• Management port IPv4 address and subnet mask, or IPv6 address and prefix

• Default gateway IPv4 or IPv6 address

• DNS Server IPv4 or IPv6 address

• Default domain name

Setup Mode

You can choose to either restore the system configuration from an existing backup file, or manually set up the system by going through the Setup wizard. If you choose to restore the system, the backup file must be reachable from the management network.

System Configuration Type

You can configure a Cisco UCS domain to use a single fabric interconnect in a standalone configuration or to use a redundant pair of fabric interconnects in a cluster configuration.

A cluster configuration provides high availability. If one fabric interconnect becomes unavailable, the other takes over. Only one management port (Mgmt0) connection is required to support a cluster configuration; however, both Mgmt0 ports should be connected to provide link-level redundancy.

In addition, a cluster configuration actively enhances failover recovery time for redundant virtual interface

(VIF) connections. When an adapter has an active VIF connection to one fabric interconnect and a standby

VIF connection to the second, the learned MAC addresses of the active VIF are replicated but not installed on the second fabric interconnect. If the active VIF fails, the second fabric interconnect installs the replicated

MAC addresses and broadcasts them to the network through gratuitous ARP messages, shortening the switchover time.

Note

The cluster configuration provides redundancy only for the management plane. Data redundancy is dependent on the user configuration and might require a third-party tool to support data redundancy.

To use the cluster configuration, you must directly connect the two fabric interconnects together using Ethernet cables between the L1 (L1-to-L1) and L2 (L2-to-L2) high-availability ports, with no other fabric interconnects in between. Also you can connect the fabric interconnects directly through a patch panel to allow the two fabric interconnects to continuously monitor the status of each other and quickly know when one has failed.

Both fabric interconnects in a cluster configuration must go through the initial setup process. You must enable the first fabric interconnect that you set up for a cluster configuration. When you set up the second fabric interconnect, it detects the first fabric interconnect as a peer fabric interconnect in the cluster.

For more information, see to the Cisco UCS 6100 Series Fabric Interconnect Hardware Installation Guide.

Management Port IP Address

In a standalone configuration, you must specify only one IPv4 address, gateway, and subnet mask, or only one IPv6 address, gateway, and network prefix for the single management port on the fabric interconnect.

You can configure either an IPv4 or an IPv6 address for the management port IP address.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Performing an Initial System Setup for a Standalone Configuration

In a cluster configuration, you must specify the following three IPv4 addresses in the same subnet, or three

IPv6 addresses with the same prefix:

• Management port IP address for fabric interconnect A

• Management port IP address for fabric interconnect B

• Cluster IP address

Note

In a cluster configuration, the management port for both fabric interconnects must be configured with the same address type, either IPv4 or IPv6. If you configure the first FI with an IPv4 address then attempt to configure the second FI with an IPv6 address, the configuration will fail.

Performing an Initial System Setup for a Standalone

Configuration

Before You Begin

Verify the following physical connections on the fabric interconnect:

• The console port is physically connected to a computer terminal or console server

• The management Ethernet port (mgmt0) is connected to an external hub, switch, or router

For more information, refer to the Cisco UCS Hardware Installation Guide for your fabric interconnect.

Verify that the console port parameters on the computer terminal (or console server) attached to the console port are as follows:

• 9600 baud

• 8 data bits

• No parity

• 1 stop bit

Collect the following information that you will need to supply during the initial setup:

• System name

• Password for the admin account. Choose a strong password that meets the guidelines for Cisco UCS

Manager passwords. This password cannot be blank.

• Management port IPv4 and subnet mask, or IPv6 address and prefix.

• Default gateway IPv4 or IPv6 address.

• DNS server IPv4 or IPv6 address (optional).

• Domain name for the system (optional).

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Performing an Initial System Setup for a Standalone Configuration

Procedure

Step 1

Connect to the console port.

Step 2

Power on the fabric interconnect.

You will see the power on self-test messages as the fabric interconnect boots. The system will run a DHCP client to check for a lease.

Step 3

When the unconfigured system boots, it prompts you for the setup method to be used. Enter console to continue the initial setup using the console CLI.

Step 4

Enter setup to continue as an initial system setup.

Step 5

Enter y to confirm that you want to continue the initial setup.

Step 6

Enter the password for the admin account.

Step 7

To confirm, re-enter the password for the admin account.

Step 8

Enter no to continue the initial setup for a standalone configuration.

Step 9

Enter the system name.

Step 10 Enter the IPv4 or IPv6 address for the management port of the fabric interconnect.

If you enter an IPv4 address, you will be prompted to enter an IPv4 subnet mask. If you enter an IPv6 address, you will be prompted to enter an IPv6 network prefix.

Step 11 Enter the respective IPv4 subnet mask or IPv6 network prefix, then press Enter.

You are prompted for an IPv4 or IPv6 address for the default gateway, depending on the address type you entered for the management port of the fabric interconnect.

Step 12 Enter either the:

• IPv4 address of the default gateway

• IPv6 address of the default gateway

Step 13 Enter yes if you want to specify the IP address for the DNS server, or no if you do not.

Step 14 (Optional) Enter the IPv4 or IPv6 address for the DNS server.

The address type must be the same as the address type of the management port of the fabric interconnect.

Step 15 Enter yes if you want to specify the default domain name, or no if you do not.

Step 16 (Optional) Enter the default domain name.

Step 17 Enter yes if you want to join the centralized management environment (Cisco UCS Central), or no if you do not.

Step 18 Review the setup summary and enter yes to save and apply the settings, or enter no to go through the Setup wizard again to change some of the settings.

If you choose to go through the Setup wizard again, it provides the values you previously entered, and the values appear in brackets. To accept previously entered values, press Enter.

The following example sets up a standalone configuration using the console setup method and IPv4 management addresses:

Enter the installation method (console/gui)?

console

Enter the setup mode (restore from backup or initial setup) [restore/setup]?

setup

You have chosen to setup a new switch.

Continue? (y/n):

Enter the password for "admin":

adminpassword%958

Confirm the password for "admin":

adminpassword%958

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Initial System Setup for a Cluster Configuration

Do you want to create a new cluster on this switch (select 'no' for standalone setup or if you want this switch to be added to an existing cluster)? (yes/no) [n]:

Enter the system name:

foo

Mgmt0 address:

192.168.10.10

Mgmt0 IPv4 netmask:

255.255.255.0

IPv4 address of the default gateway:

192.168.10.1

Configure the DNS Server IPv4 address? (yes/no) [n]:

yes

DNS IP address:

20.10.20.10

Configure the default domain name? (yes/no) [n]:

yes

Default domain name:

domainname.com

Join centralized management environment (UCS Central)? (yes/no) [n]:

Following configurations will be applied:

Switch Fabric=A

System Name=foo

Physical Switch Mgmt0 IP Address=192.168.10.10

Physical Switch Mgmt0 IP Netmask=255.255.255.0

Default Gateway=192.168.10.1

DNS Server=20.10.20.10

Domain Name=domainname.com

Apply and save the configuration (select 'no' if you want to re-enter)? (yes/no):

yes

The following example sets up a standalone configuration using the console setup method and IPv6 management addresses:

Enter the installation method (console/gui)?

console

Enter the setup mode (restore from backup or initial setup) [restore/setup]?

setup

You have chosen to setup a new switch.

Continue? (y/n):

Enter the password for "admin":

adminpassword%652

Confirm the password for "admin":

adminpassword%652

Do you want to create a new cluster on this switch (select 'no' for standalone setup or if you want this switch to be added to an existing cluster)? (yes/no) [n]:

Enter the system name:

foo

Mgmt0 address:

2001::107

Mgmt0 IPv6 prefix:

IPv6 address of the default gateway:

2001::1

Configure the DNS Server IPv6 address? (yes/no) [n]:

yes

DNS IP address:

2001::101

Configure the default domain name? (yes/no) [n]:

yes

Default domain name:

domainname.com

Join centralized management environment (UCS Central)? (yes/no) [n]:

Following configurations will be applied:

Switch Fabric=A

System Name=foo

Enforced Strong Password=no

Physical Switch Mgmt0 IPv6 Address=2001::107

Physical Switch Mgmt0 IPv6 Prefix=64

Default Gateway=2001::1

Ipv6 value=1

DNS Server=2001::101

Domain Name=domainname.com

Apply and save the configuration (select 'no' if you want to re-enter)? (yes/no):

yes

Initial System Setup for a Cluster Configuration

Performing an Initial System Setup for the First Fabric Interconnect

This procedure describes setting up the first fabric interconnect using IPv4 or IPv6 addresses for the management port, the default gateway, and the DNS server.

Before You Begin

Verify the following physical connections on the fabric interconnect:

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Performing an Initial System Setup for the First Fabric Interconnect

• A console port on the first fabric interconnect is physically connected to a computer terminal or console server

• The management Ethernet port (mgmt0) is connected to an external hub, switch, or router

• The L1 ports on both fabric interconnects are directly connected to each other

• The L2 ports on both fabric interconnects are directly connected to each other

For more information, refer to the Cisco UCS Hardware Installation Guide for your fabric interconnect.

Verify that the console port parameters on the computer terminal (or console server) attached to the console port are as follows:

• 9600 baud

• 8 data bits

• No parity

• 1 stop bit

Collect the following information that you will need to supply during the initial setup:

• System name.

• Password for the admin account. Choose a strong password that meets the guidelines for Cisco UCS

Manager passwords. This password cannot be blank.

• Three static IPv4 or IPv6 addresses: two for the management port on both fabric interconnects (one per fabric interconnect) and one for the cluster IP address used by Cisco UCS Manager.

• Subnet mask for the three static IPv4 addresses, or network prefix for the three static IPv6 addresses.

• Default gateway IPv4 or IPv6 address.

• DNS server IPv4 or IPv6 address (optional).

• Domain name for the system (optional).

Procedure

Step 1

Connect to the console port.

Step 2

Power on the fabric interconnect.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Performing an Initial System Setup for the First Fabric Interconnect

You will see the power on self-test messages as the fabric interconnect boots. The system will run a DHCP client to check for a lease.

Step 3

When the unconfigured system boots, it prompts you for the setup method to be used. Enter console to continue the initial setup using the console CLI.

Step 4

Enter setup to continue as an initial system setup.

Step 5

Enter y to confirm that you want to continue the initial setup.

Step 6

Enter the password for the admin account.

Step 7

To confirm, re-enter the password for the admin account.

Step 8

Enter yes to continue the initial setup for a cluster configuration.

Step 9

Enter the fabric interconnect fabric (either A or B ).

Step 10 Enter the system name.

Step 11 Enter the IPv4 or IPv6 address for the management port of the fabric interconnect.

If you enter an IPv4 address, you will be prompted to enter an IPv4 subnet mask. If you enter an IPv6 address, you will be prompted to enter an IPv6 network prefix.

Step 12 Enter the respective IPv4 subnet mask or IPv6 network prefix, then press Enter.

You are prompted for an IPv4 or IPv6 address for the default gateway, depending on the address type you entered for the management port of the fabric interconnect.

Step 13 Enter either the:

• IPv4 address of the default gateway

• IPv6 address of the default gateway

Step 14 Enter yes if you want to specify the IP address for the DNS server, or no if you do not.

Step 15 (Optional) Enter the IPv4 or IPv6 address for the DNS server.

The address type must be the same as the address type of the management port of the fabric interconnect.

Step 16 Enter yes if you want to specify the default domain name, or no if you do not.

Step 17 (Optional) Enter the default domain name.

Step 18 Review the setup summary and enter yes to save and apply the settings, or enter no to go through the Setup wizard again to change some of the settings.

If you choose to go through the Setup wizard again, it provides the values you previously entered, and the values appear in brackets. To accept previously entered values, press Enter.

The following example sets up the first fabric interconnect for a cluster configuration using the console and

IPv4 management addresses:

Enter the installation method (console/gui)?

console

Enter the setup mode (restore from backup or initial setup) [restore/setup]?

setup

You have chosen to setup a new switch.

Continue? (y/n):

Enter the password for "admin":

adminpassword%958

Confirm the password for "admin":

adminpassword%958

Do you want to create a new cluster on this switch (select 'no' for standalone setup or if you want this switch to be added to an existing cluster)? (yes/no) [n]:

yes

Enter the switch fabric (A/B):

Enter the system name:

foo

Mgmt0 IPv4 address:

192.168.10.10

Mgmt0 IPv4 netmask:

255.255.255.0

IPv4 address of the default gateway:

192.168.10.1

Virtual IPv4 address:

192.168.10.12

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Performing an Initial System Setup for the Second Fabric Interconnect

Configure the DNS Server IPv4 address? (yes/no) [n]:

yes

DNS IPv4 address:

20.10.20.10

Configure the default domain name? (yes/no) [n]:

yes

Default domain name:

domainname.com

Join centralized management environment (UCS Central)? (yes/no) [n]:

Following configurations will be applied:

Switch Fabric=A

System Name=foo

Management IP Address=192.168.10.10

Management IP Netmask=255.255.255.0

Default Gateway=192.168.10.1

Cluster Enabled=yes

Virtual Ip Address=192.168.10.12

DNS Server=20.10.20.10

Domain Name=domainname.com

Apply and save the configuration (select 'no' if you want to re-enter)? (yes/no):

yes

The following example sets up the first fabric interconnect for a cluster configuration using the console and

IPv6 management addresses:

Enter the installation method (console/gui)?

console

Enter the setup mode (restore from backup or initial setup) [restore/setup]?

setup

You have chosen to setup a new switch.

Continue? (y/n):

Enter the password for "admin":

adminpassword%652

Confirm the password for "admin":

adminpassword%652

Do you want to create a new cluster on this switch (select 'no' for standalone setup or if you want this switch to be added to an existing cluster)? (yes/no) [n]:

yes

Enter the switch fabric (A/B):

Enter the system name:

foo

Mgmt0 address:

2001::107

Mgmt0 IPv6 prefix:

IPv6 address of the default gateway:

2001::1

Configure the DNS Server IPv6 address? (yes/no) [n]:

yes

DNS IP address:

2001::101

Configure the default domain name? (yes/no) [n]:

yes

Default domain name:

domainname.com

Join centralized management environment (UCS Central)? (yes/no) [n]:

Following configurations will be applied:

Switch Fabric=A

System Name=foo

Enforced Strong Password=no

Physical Switch Mgmt0 IPv6 Address=2001::107

Physical Switch Mgmt0 IPv6 Prefix=64

Default Gateway=2001::1

Ipv6 value=1

DNS Server=2001::101

Domain Name=domainname.com

Apply and save the configuration (select 'no' if you want to re-enter)? (yes/no):

yes

Performing an Initial System Setup for the Second Fabric Interconnect

This procedure describes setting up the second fabric interconnect using IPv4 or IPv6 addresses for the management port.

Before You Begin

Verify the following physical connections on the fabric interconnect:

• A console port on the second fabric interconnect is physically connected to a computer terminal or console server

• The management Ethernet port (mgmt0) is connected to an external hub, switch, or router

• The L1 ports on both fabric interconnects are directly connected to each other

• The L2 ports on both fabric interconnects are directly connected to each other

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Performing an Initial System Setup for the Second Fabric Interconnect

For more information, refer to the Cisco UCS Hardware Installation Guide for your fabric interconnect.

Verify that the console port parameters on the computer terminal (or console server) attached to the console port are as follows:

• 9600 baud

• 8 data bits

• No parity

• 1 stop bit

Collect the following information that you will need to supply during the initial setup:

• Password for the admin account of the peer fabric interconnect. Choose a strong password that meets the guidelines for Cisco UCS Manager passwords. This password cannot be blank.

• Management port IPv4 address in the same subnet, or management port IPv6 with the same network prefix as the peer fabric interconnect.

Procedure

Step 1

Connect to the console port.

Step 2

Power on the fabric interconnect.

You will see the power on self-test messages as the fabric interconnect boots. The system will run a DHCP client to check for a lease.

Step 3

When the unconfigured system boots, it prompts you for the setup method to be used. Enter console to continue the initial setup using the console CLI.

Note

The fabric interconnect should detect the peer fabric interconnect in the cluster. If it does not, check the physical connections between the L1 and L2 ports, and verify that the peer fabric interconnect has been enabled for a cluster configuration.

Step 4

Enter y to add the subordinate fabric interconnect to the cluster.

Step 5

Enter the admin password of the peer fabric interconnect.

Step 6

Enter the IP address for the management port on the subordinate fabric interconnect.

Step 7

Review the setup summary and enter yes to save and apply the settings, or enter no to go through the Setup wizard again to change some of the settings.

If you choose to go through the Setup wizard again, it provides the values you previously entered, and the values appear in brackets. To accept previously entered values, press Enter.

The following example sets up the second fabric interconnect for a cluster configuration using the console and the IPv4 address of the peer:

Enter the installation method (console/gui)?

console

Installer has detected the presence of a peer Fabric interconnect. This Fabric interconnect will be added to the cluster. Continue (y/n) ?

Enter the admin password of the peer Fabric Interconnect:

adminpassword%958

Peer Fabric interconnect Mgmt0 IPv4 Address:

192.168.10.11

Apply and save the configuration (select 'no' if you want to re-enter)? (yes/no):

yes

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Adding Out-of-band IPv4 Addresses to a Fabric Interconnect

The following example sets up the second fabric interconnect for a cluster configuration using the console and the IPv6 address of the peer:

Enter the installation method (console/gui)?

console

Installer has detected the presence of a peer Fabric interconnect. This Fabric interconnect will be added to the cluster. Continue (y/n) ?

Enter the admin password of the peer Fabric Interconnect:

adminpassword%958

Peer Fabric interconnect Mgmt0 IPv6 Address:

2001::107

Apply and save the configuration (select 'no' if you want to re-enter)? (yes/no):

yes

Adding Out-of-band IPv4 Addresses to a Fabric Interconnect

All fabric interconnects require an OOB IPv4 address, network mask and gateway. This procedure describes how to configure an OOB IPv4 address for a fabric interconnect that was set up with static IPv6 addresses.

Before You Begin

Collect the out-of-band (OOB) IPv4 address you want to assign to the fabric interconnect.

Procedure

Step 1

Step 2

Step 3

Command or Action

UCS-A # scope fabric interconnect a

UCS-A/fabric-interconnect # set

out-of-band ip ip-addr netmask

ip-addrgw ip-addr

UCS-A/fabric-interconnect #

commit-buffer

Purpose

Enters fabric configuration mode for Fabric A.

Sets the OOB IPv4 address, network mask and gateway address.

The system warns that the console session change may be disconnected when the change is committed.

Commits the transaction to the system configuration.

The following example shows configuring an OOB IPv4 address for fabric interconnect A:

UCS-A#

scope fabric-interconnect a

UCS-A /fabric-interconnect #

set out-of-band ip 10.105.214.107 netmask 255.255.255.0 gw

10.105.214.1

Warning: When committed, this change may disconnect the current CLI session

UCS-A /fabric-interconnect* #

commit-buffer

Enabling a Standalone Fabric Interconnect for Cluster

Configuration

You can add a second fabric interconnect to an existing Cisco UCS domain that uses a single standalone fabric interconnect. To do this, you must enable the standalone fabric interconnect for cluster operation by configuring it with the virtual IP or IPv6 address of the cluster, and then add the second fabric interconnect to the cluster.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Changing the System Name

Procedure

Step 1

Step 2

Command or Action

UCS-A# connect local-mgmt

Purpose

Enters local management mode.

UCS-A(local-mgmt) # enable

cluster

{virtual-ip-addr|virtual-ip6-addr}

Enables cluster operation on the standalone fabric interconnect with the specified IPv4 or IPv6 address. When you enter this command, you are prompted to confirm that you want to enable cluster operation. Type yes to confirm.

The IP address must be the virtual IPv4 or IPv6 address for the cluster configuration, not the IP address assigned to the fabric interconnect that you are adding to the cluster.

The following example enables a standalone fabric interconnect with a virtual IPv4 address of 192.168.1.101

for cluster operation:

UCS-A#

connect local-mgmt

UCS-A(local-mgmt)#

enable cluster 192.168.1.101

This command will enable cluster mode on this setup. You cannot change it back to stand-alone. Also, any GUI or KVM sessions may be terminated. Are you sure you want to continue? (yes/no):

yes

UCS-A(local-mgmt)#

The following example enables a standalone fabric interconnect with a virtual IPv6 address of 192.168.1.101

for cluster operation:

UCS-A#

connect local-mgmt

UCS-A(local-mgmt)#

enable cluster ipv6 2001::109

This command will enable IPv6 cluster mode on this setup. You cannot change it back to stand-alone. Also, any GUI or KVM sessions may be terminated. Are you sure you want to continue? (yes/no):

yes

UCS-A(local-mgmt)#

What to Do Next

Add the second fabric interconnect to the cluster.

Changing the System Name

Procedure

Step 1

Step 2

Step 3

Command or Action

UCS-A # scope system

UCS-A /system # set name name

UCS-A /system # commit-buffer

Purpose

Enters system mode.

Sets the system name.

Commits the transaction to the system configuration.

The name is updated on both fabric interconnects within about 30 seconds after the transaction is committed.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Changing the Management Subnet of a Cluster

The following example changes the system name and commits the transaction:

UCS-A#

scope system

UCS-A /system* #

set name SanJose5

UCS-A /system* #

commit-buffer

UCS-A /system #

Changing the Management Subnet of a Cluster

When changing the IPv4 management subnet in a cluster configuration, you must change the following three

IPv4 addresses simultaneously and you must configure all three in the same subnet:

• Management port IP address for fabric interconnect A

• Management port IP address for fabric interconnect B

• Cluster IP (virtual IP) address

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Command or Action

UCS-A# scope fabric-interconnect a

Purpose

Enters fabric interconnect mode for fabric

UCS-A /fabric-interconnect # set out-of-band

ip ip-address netmask netmask gw

gateway-ip-address

Sets the IP address, network mask, and gateway IP address of the fabric interconnect.

UCS-A /fabric-interconnect # scope

fabric-interconnect b

Enters fabric interconnect mode for fabric B.

UCS-A /fabric-interconnect # set out-of-band

ip ip-address netmask netmask gw

gateway-ip-address

Sets the IP address, netmask, and gateway

IP address of the fabric interconnect.

UCS-A /fabric-interconnect # scope system Enters system mode.

UCS-A /system # set virtual-ip vip-address

UCS-A /system # commit-buffer

Sets the virtual IP address for the cluster.

Commits the transaction to the system configuration.

When you commit the transaction, you are disconnected from the management session. Reconnect at the new management IP address.

This example changes both fabric-interconnect IP addresses, changes the virtual IP address, and commits the transaction, disconnecting the session:

UCS-A#

scope fabric-interconnect a

UCS-A /fabric-interconnect #

set out-of-band ip 192.0.2.111 netmask 255.255.255.0 gw 192.0.2.1

UCS-A /fabric-interconnect* #

scope fabric-interconnect b

UCS-A /fabric-interconnect* #

set out-of-band ip 192.0.2.112 netmask 255.255.255.0 gw

192.0.2.1

UCS-A /fabric-interconnect* #

scope system

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Changing the Management Prefix of a Cluster

UCS-A /system* #

set virtual-ip 192.0.2.113

UCS-A /system* #

commit-buffer

Changing the Management Prefix of a Cluster

When changing the IPv6 management prefix in a cluster configuration, you must change the following three

IPv6 addresses simultaneously and you must configure all three with the same network prefix:

• Management port IPv6 address for fabric interconnect A

• Management port IPv6 address for fabric interconnect B

• Cluster IPv6 (virtual IPv6) address

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Command or Action

UCS-A# scope fabric-interconnect a

Purpose

Enters fabric interconnect mode for fabric

UCS-A fabric-interconnect # scope ipv6-config Enters IPv6 configuration mode for fabric

UCS-A fabric-interconnect/ ipv6-config # set

out-of-band ipv6 ipv6-addr ipv6-gw

ipv6-gw-addr ipv6-prefix prefix

Sets the management IPv6 address, gateway

IPv6 address, and network prefix for fabric

UCS-A fabric-interconnect/ipv6-config # scope

fabric-interconnect b

Enter fabric interconnect mode for fabric B.

UCS-A fabric-interconnect/ # scope ipv6-config Enter IPv6 configuration mode for fabric B

UCS-A/fabric-interconnect/ipv6-config # set

out-of-band ipv6 ipv6-addr ipv6-gw

ipv6-gw-addr ipv6-prefix prefix

Sets the management IPv6 address, gateway

IPv6 address, and network prefix for fabric

UCS-A/fabric-interconnect/ipv6-config # scope

system

Enters system mode.

Sets the virtual IPv6 address for the cluster.

UCS-A/system # set virtual-ip ipv6

virtual-ip6-addr

UCS-A/system # commit-buffer Commits the transaction to the system configuration.

When you commit the transaction, you are disconnected from the management session. Reconnect at the new management IPv6 address.

This example changes both management IPv6 addresses, changes the virtual IPv6 address, and commits the transaction:

UCS-A# scope fabric-interconnect a

UCS-A /fabric-interconnect #

scope ipv6-config

UCS-A /fabric-interconnect/ipv6-config #

set out-of-band ipv6 2001:10::157

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Configuring the Information Policy on the Fabric Interconnect

UCS-A /fabric-interconnect/ipv6-config* #

set out-of-band ipv6-gw 2001:10::1

UCS-A /fabric-interconnect/ipv6-config* #

set out-of-band ipv6-prefix 64

UCS-A /fabric-interconnect/ipv6-config* #

scope fabric-interconnect b

UCS-A /fabric-interconnect* #

scope ipv6-config

UCS-A /fabric-interconnect/ipv6-config* #

set out-of-band ipv6 2001:10::158

UCS-A /fabric-interconnect/ipv6-config* #

set out-of-band ipv6-gw 2001:10::1

UCS-A /fabric-interconnect/ipv6-config* #

set out-of-band ipv6-prefix 64

UCS-A /fabric-interconnect/ipv6-config* #

scope system

UCS-A /system* #

set virtual-ip ipv6 2001:10::156

UCS-A /system* #

commit-buffer

UCS-A /system #

Configuring the Information Policy on the Fabric Interconnect

You must configure the information policy to display the uplink switches that are connected to Cisco UCS.

Important

You must enable the information policy on the fabric interconnect to view the SAN, LAN, and LLDP neighbors of the fabric interconnect.

Enabling the Information Policy on the Fabric Interconnect

Note

By default, the information policy is disabled on the fabric interconnect.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

UCS-A # scope system

UCS-A/system # scope info-policy

UCS-A/system/info-policy # show

UCS-A/system/info-policy # enable

UCS-A/system/info-policy* #

commit-buffer

Purpose

Enters system mode.

Enters the information policy state.

(Optional)

Displays if the information policy is enabled or disabled.

Determines if the information policy can enabled on the fabric interconnect.

Enables the information policy on the fabric interconnect.

The following example shows how to enable the information policy on the fabric interconnect:

UCS-A#

scope system

UCS-A/system #

scope info-policy

UCS-A/system/info-policy #

show

Info Policy:

State: Disabled

UCS-A/system/info-policy #

enable

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Disabling the Information Policy on the Fabric Interconnect

UCS-A/system/info-policy* #

commit-buffer

UCS-A/system/info-policy #

Disabling the Information Policy on the Fabric Interconnect

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

UCS-A # scope system

UCS-A/system # scope info-policy

UCS-A/system/info-policy # show

UCS-A/system/info-policy # disable

UCS-A/system/info-policy* #

commit-buffer

Purpose

Enters system mode.

Enters the information policy state.

(Optional)

Displays if the information policy is enabled or disabled.

Determines if the information policy can disabled on the fabric interconnect.

Disables information policy on the fabric interconnect.

The following example shows how to disable the information policy on the fabric interconnect:

UCS-A#

scope system

UCS-A/system #

scope info-policy

UCS-A/system/info-policy #

show

Info Policy:

State: Enabled

UCS-A/system/info-policy #

disable

UCS-A/system/info-policy* #

commit-buffer

UCS-A/system/info-policy #

Viewing the Information Policy on the Fabric Interconnect

You can view the information policy state of the fabric interconnect.

Procedure

Step 1

Step 2

Step 3

Command or Action

UCS-A # scope system

UCS-A/system # scope info-policy

UCS-A/system/info-policy # show

Purpose

Enters system mode.

Enters the information policy state.

Displays if the information policy is enabled or disabled.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Viewing the LAN Neighbors of the Fabric Interconnect

The following example shows how to view the information policy state on the fabric interconnect:

UCS-A#

scope system

UCS-A/system #

scope info-policy

UCS-A/system/info-policy #

show

Info Policy:

State: Enabled

Viewing the LAN Neighbors of the Fabric Interconnect

You must enable the information policy on the fabric interconnect to view the LAN neighbors.

Procedure

Step 1

Step 2

Command or Action Purpose

UCS-A# scope fabric-interconnect {a | b} Enters fabric interconnect mode for the specified fabric interconnect.

UCS-A/fabric-interconnect # show

lan-neighbors

Displays the fabric interconnect LAN neighbors.

The following example shows how to display the LAN neighbors of the fabric interconnect:

UCS-A #

scope fabric-interconnect a

UCS-Afabric-interconnect #

show lan-neighbors

Info Policy:Enabled

Lan Neighbors:

Local Interface: Ethernet1/2

Device Id: bgl-samc02-B(SSI140305YK)

IPv4 Address: 10.105.214.105

FI Port DN: sys/switch-A/slot-1/switch-ether/port-2

Viewing the SAN Neighbors of the Fabric Interconnect

You must enable the information policy on the fabric interconnect to view the SAN neighbors.

Procedure

Step 1

Step 2

Command or Action Purpose

UCS-A# scope fabric-interconnect {a | b} Enters fabric interconnect mode for the specified fabric interconnect.

UCS-A/fabric-interconnect # show

san-neighbors

Displays the fabric interconnect SAN neighbors.

The following example shows how to display the SAN neighbors of the fabric interconnect :

UCS-A #

scope fabric-interconnect a

UCS-A/fabric-interconnect #

show san-neighbors

Info Policy: Enabled

San neighbors:

Local Interface: fc2/1

Port VSAN: 100

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Viewing the LLDP Neighbors of the Fabric Interconnect

Fabric Mgmt Addr: 10.65.124.252

Fabric pwwn: 20:02:00:05:9b:22:ad:C0

Fabric nwwn: 20:64:00:05:9b:22:ad:C1

My pwwn: 20:41:00:0d:ec:ee:dd:00

My nwwn: 20:64:00:0d:ec:ee:dd:01

FI Port DN: sys/switch-A/slot-2/switch-fc/port-1

Viewing the LLDP Neighbors of the Fabric Interconnect

You must enable the information policy on the fabric interconnect to view the LLDP neighbors.

Procedure

Step 1

Step 2

Command or Action Purpose

UCS-A# scope fabric-interconnect {a | b} Enters fabric interconnect mode for the specified fabric interconnect.

UCS-A/fabric-interconnect # show

lldp-neighbors

Displays the fabric interconnect LLDP neighbors.

The following example shows how to display the LLDP neighbors of the fabric interconnect :

UCS-A #

scope fabric-interconnect a

UCS-A/fabric-interconnect #

show lldp-neighbors

Info Policy: Enabled

Lldp Neighbors:

Local Interface: Eth1/5

Chassis Id: 000d.ecff.5e90

Remote Interface: Eth1/9

Remote Port Description: Ethernet1/9

System Name: bgl-samc02-B

System Capabilities: B

Enabled Capabilities: B

Native VLAN: 1

IPv4 Mgmt Address: 10.105.214.105

FI Port DN: sys/switch-A/slot-1/switch-ether/port-5

Fabric Evacuation

Cisco UCS Manager 2.2(4) introduces fabric evacuation, which is the ability to evacuate all traffic that flows through a Fabric Interconnect from all servers attached to it through an IOM or FEX while upgrading a system.

Upgrading the secondary Fabric Interconnect in a system disrupts the traffic that is active on the Fabric

Interconnect. This traffic fails over to the primary Fabric Interconnect. You can use fabric evacuation as follows during the upgrade process:

Stop all the traffic that is active through a Fabric Interconnect.

For vNICs configured with failover, verify that the traffic has failed over by using Cisco UCS Manager or tools such as vCenter.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Stopping Traffic on a Fabric Interconnect

Upgrade the secondary Fabric Interconnect.

Restart all the stopped traffic flows.

Change the cluster lead to the secondary Fabric Interconnect.

Repeat steps 1 to 4 and upgrade the other Fabric Interconnect.

Note

Fabric evacuation is supported only with the following:

• Manual install

• Cluster configuration

Stopping Traffic on a Fabric Interconnect

Procedure

Step 1

Step 2

Step 3

Command or Action Purpose

UCS-A # scope fabric-interconnect {a

| b}

Enters fabric interconnect mode for the specified Fabric

Interconnect.

UCS-A /fabric-interconnect # stop

server traffic [force]

UCS-A /fabric-interconnect #

commit-buffer

Stops all the traffic that is active through the specified

Fabric Interconnect.

Use the force option to evacuate a Fabric Interconnect irrespective of its current evacuation state.

Commits the transaction to the system configuration.

This example shows how to stop all traffic that is active through Fabric Interconnect B:

UCS-A#

scope fabric-interconnect b

UCS-A /fabric-interconnect #

stop server traffic

Warning: Enabling fabric evacuation will stop all traffic through this Fabric Interconnect from servers attached through IOM/FEX. The traffic will fail over to the Primary Fabric

Interconnect for fail over vnics.

UCS-A /fabric-interconnect #

commit-buffer

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Displaying the Status of Evacuation at a Fabric Interconnect

Displaying the Status of Evacuation at a Fabric Interconnect

Procedure

Step 1

Step 2

Command or Action

UCS-A # scope fabric-interconnect {a |

Purpose

Enters fabric interconnect mode for the specified

Fabric Interconnect.

UCS-A /fabric-interconnect # show detail Displays details about the specified Fabric

Interconnect.

This example shows how to display the detailed status of a Fabric Interconnect.

Note

Admin Evacuation and Oper Evacuation show the status of evacuation at the Fabric Interconnect.

UCS-A /fabric-interconnect #

show detail

Fabric Interconnect:

ID: B

Product Name: Cisco UCS 6248UP

PID: UCS-FI-6248UP

VID: V01

Vendor: Cisco Systems, Inc.

Serial (SN): SSI171400HG

HW Revision: 0

Total Memory (MB): 16165

OOB IP Addr: 10.193.32.172

OOB Gateway: 10.193.32.1

OOB Netmask: 255.255.255.0

OOB IPv6 Address: ::

OOB IPv6 Gateway: ::

Prefix: 64

Operability: Operable

Thermal Status: Ok

Admin Evacuation: On

Oper Evacuation: On

Current Task 1:

Current Task 2:

Current Task 3:

Displaying the Status of Evacuation at an IOM

Procedure

Step 1

Command or Action

UCS-A# scope chassis chassis-num

Purpose

Enters chassis mode for the specified chassis.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Verifying Fabric Evacuation

Step 2

Step 3

Command or Action

UCS-A /chassis # scope iom iom-id

UCS-A /chassis/iom # show detail

Purpose

Enters chassis IOM mode for the specified

IOM.

Displays details about the specified IOM.

This example shows how to display the detailed status of an IOM.

Note

Oper Evacuation shows the operational status of evacuation at the IOM.

UCS-A#

scope chassis 1

UCS-A /chassis #

scope iom 1

UCS-A /chassis/iom #

show detail

IOM:

ID: 1

Side: Left

Fabric ID: A

User Label:

Overall Status: Fabric Conn Problem

Oper qualifier: Server Port Problem

Operability: Operable

Presence: Equipped

Thermal Status: OK

Discovery: Online

Config State: Ok

Peer Comm Status: Connected

Product Name: Cisco UCS 2204XP

PID: UCS-IOM-2204XP

VID: V02

Part Number: 73-14488-02

Vendor: Cisco Systems Inc

Serial (SN): FCH1718J9FT

HW Revision: 0

Mfg Date: 2013-05-12T00:00:00.000

Controller Subject: Iocard

Fabric Port Aggregation Capability: Port Channel

Oper Evacuation: On

Current Task 1:

Current Task 2:

Verifying Fabric Evacuation

Procedure

Step 1

Command or Action

UCS-A# show service-profile circuit

server server-id

Purpose

Shows the network circuit information for the service profile associated with the specified server.

This example shows the VIF paths before fabric evacuation.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Verifying Fabric Evacuation

Note

• VIF at Fabric Interconnect A shows that traffic is initially active through the Fabric interconnect.

• VIF at Fabric Interconnect B is passive before evacuation.

UCS-A#

show service-profile circuit server 1/6

Service Profile: test1

Server: 1/6

Fabric ID: A

Path ID: 1

VIF vNIC

Pin Oper Pin Transport

Link State Oper State Prot State Prot Role Admin

---------- --------------- ----------- ---------- ------------- ----------- ----------

---------- ---------

692 eth0 Up Active Active Primary 0/0

1/15

Fabric ID: B

Ether

Path ID: 1

VIF vNIC Link State Oper State Prot State Prot Role Admin

Pin Oper Pin Transport

---------- --------------- ----------- ---------- ------------- ----------- ----------

---------- ---------

1/15

UCS-A#

693 eth0

Ether

Up Active Passive Backup 0/0

This example shows the VIF paths after Fabric Interconnect A is evacuated.

Note

• After fail over, the VIF state at Fabric Interconnect A goes into error.

• VIF at Fabric Interconnect B takes over as active.

UCS-A#

show service-profile circuit server 1/6

Service Profile: test1

Server: 1/6

Fabric ID: A

Path ID: 1

VIF vNIC

Pin Oper Pin Transport

Link State Oper State Prot State Prot Role Admin

---------- --------------- ----------- ---------- ------------- ----------- ----------

---------- ---------

Error Error Active Primary 0/0 692 eth0

0/0

Fabric ID: B

Ether

Path ID: 1

VIF vNIC

Pin Oper Pin Transport

Link State Oper State Prot State Prot Role Admin

---------- --------------- ----------- ---------- ------------- ----------- ----------

---------- ---------

693 eth0

1/15

UCS-A#

Ether

Up Active Passive Backup 0/0

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Restarting Traffic on a Fabric Interconnect

Restarting Traffic on a Fabric Interconnect

Procedure

Step 1

Step 2

Step 3

Command or Action

UCS-A # scope fabric-interconnect {a |

Purpose

Enters fabric interconnect mode for the specified

Fabric Interconnect.

UCS-A /fabric-interconnect # start server

traffic

Restarts traffic through the specified Fabric

Interconnect.

UCS-A /fabric-interconnect #

commit-buffer

Commits the transaction to the system configuration.

This example shows how to restart traffic through Fabric Interconnect B:

UCS-A#

scope fabric-interconnect b

UCS-A /fabric-interconnect #

start server traffic

Warning: Resetting fabric evacuation will cause server traffic that failed over to the

Primary Fabric Interconnect to fail back to this Fabric Interconnect.

UCS-A /fabric-interconnect #

commit-buffer

Ethernet Switching Mode

The Ethernet switching mode determines how the fabric interconnect behaves as a switching device between the servers and the network. The fabric interconnect operates in either of the following Ethernet switching modes:

End-Host Mode

End-host mode allows the fabric interconnect to act as an end host to the network, representing all servers

(hosts) connected to it through vNICs. This behavior is achieved by pinning (either dynamically pinned or hard pinned) vNICs to uplink ports, which provides redundancy to the network, and makes the uplink ports appear as server ports to the rest of the fabric. In end-host mode, the fabric interconnect does not run the

Spanning Tree Protocol (STP) but it avoids loops by denying uplink ports from forwarding traffic to each other and by denying egress server traffic on more than one uplink port at a time. End-host mode is the default

Ethernet switching mode and should be used if either of the following are used upstream:

• Layer 2 switching for Layer 2 aggregation

• Virtual Switching System (VSS) aggregation layer

Note

When you enable end-host mode, if a vNIC is hard pinned to an uplink port and this uplink port goes down, the system cannot repin the vNIC, and the vNIC remains down.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Configuring Ethernet Switching Mode

Switch Mode

Switch mode is the traditional Ethernet switching mode. The fabric interconnect runs STP to avoid loops, and broadcast and multicast packets are handled in the traditional way. Switch mode is not the default Ethernet switching mode, and should be used only if the fabric interconnect is directly connected to a router, or if either of the following are used upstream:

• Layer 3 aggregation

• VLAN in a box

Note

For both Ethernet switching modes, even when vNICs are hard pinned to uplink ports, all server-to-server unicast traffic in the server array is sent only through the fabric interconnect and is never sent through uplink ports. Server-to-server multicast and broadcast traffic is sent through all uplink ports in the same

VLAN.

Configuring Ethernet Switching Mode

Important

When you change the Ethernet switching mode, Cisco UCS Manager logs you out and restarts the fabric interconnect. For a cluster configuration, Cisco UCS Manager restarts both fabric interconnects. The subordinate fabric interconnect reboots first as a result of the change in switching mode. The primary fabric interconnect reboots only after you acknowledge it in Pending Activities. The primary fabric interconnect can take several minutes to complete the change in Ethernet switching mode and become system ready. The existing configuration is retained.

While the fabric interconnects are rebooting, all blade servers lose LAN and SAN connectivity, causing a complete outage of all services on the blades. This might cause the operating system to fail.

Procedure

Step 1

Step 2

Step 3

Command or Action

UCS-A# scope eth-uplink

UCS-A /eth-uplink # set mode

{end-host | switch}

Purpose

Enters Ethernet uplink mode.

Sets the fabric interconnect to the specified switching mode.

UCS-A /eth-uplink # commit-buffer Commits the transaction to the system configuration.

Cisco UCS Manager restarts the fabric interconnect, logs you out, and disconnects Cisco UCS Manager

CLI.

The following example sets the fabric interconnect to end-host mode and commits the transaction:

UCS-A#

scope eth-uplink

UCS-A /eth-uplink #

set mode end-host

Warning: When committed, this change will cause the switch to reboot

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Fibre Channel Switching Mode

UCS-A /eth-uplink* #

commit-buffer

UCS-A /eth-uplink #

Fibre Channel Switching Mode

The Fibre Channel switching mode determines how the fabric interconnect behaves as a switching device between the servers and storage devices. The fabric interconnect operates in either of the following Fibre

Channel switching modes:

End-Host Mode

End-host mode allows the fabric interconnect to act as an end host to the connected fibre channel networks, representing all servers (hosts) connected to it through virtual host bus adapters (vHBAs). This behavior is achieved by pinning (either dynamically pinned or hard pinned) vHBAs to Fibre Channel uplink ports, which makes the Fibre Channel ports appear as server ports (N-ports) to the rest of the fabric. When in end-host mode, the fabric interconnect avoids loops by denying uplink ports from receiving traffic from one another.

End-host mode is synonymous with N Port Virtualization (NPV) mode. This mode is the default Fibre Channel

Switching mode.

Note

When you enable end-host mode, if a vHBA is hard pinned to an uplink Fibre Channel port and this uplink port goes down, the system cannot repin the vHBA, and the vHBA remains down.

Switch Mode

Switch mode is the traditional Fibre Channel switching mode. Switch mode allows the fabric interconnect to connect directly to a storage device. Enabling Fibre Channel switch mode is useful in Pod models where there is no SAN (for example, a single Cisco UCS domain that is connected directly to storage), or where a SAN exists (with an upstream MDS).

Switch mode is not the default Fibre Channel switching mode.

Note

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

Cisco UCS Fabric Interconnect in Switch Mode with Cisco MDS 9000 Family Fibre Channel Switching Modules

While creating a port channel between a Cisco MDS 9000 family FC switching module and a Cisco UCS

Fabric Interconnect in switch mode, use the following order:

Create the port channel on the MDS side.

Add the port channel member ports.

Create the port channel on the Fabric Interconnect side.

Add the port channel member ports.

If you create the port channel on the Fabric Interconnect side first, the ports will go into a suspended state.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring the Fabric Interconnects

Configuring Fibre Channel Switching Mode

When the Cisco UCS Fabric Interconnect is in switch mode, the port channel mode can only be in ON mode and not Active. However, to get the peer wwn information for the Fabric Interconnect, the port channel must be in Active mode.

Configuring Fibre Channel Switching Mode

Note

When the Fibre Channel switching mode is changed, both Cisco UCS fabric interconnects reload simultaneously. Reloading the fabric interconnects will cause a system-wide downtime for approximately

10 to 15 minutes.

Procedure

Step 1

Step 2

Step 3

Command or Action

UCS-A# scope fc-uplink

Purpose

Enters Fibre Channel uplink mode.

UCS-A /fc-uplink # set mode

{end-host | switch}

Sets the fabric interconnect to the specified switching mode.

UCS-A /fc-uplink # commit-buffer Commits the transaction to the system configuration.

Cisco UCS Manager restarts the fabric interconnect, logs you out, and disconnects Cisco UCS Manager CLI.

The following example shows how to set the fabric interconnect to end-host mode and commit the transaction:

UCS-A #

scope fc-uplink

UCS-A /fc-uplink #

set mode end-host

UCS-A /fc-uplink* #

commit-buffer

UCS-A /fc-uplink #

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Fibre Channel Switching Mode

Configuring the Fabric Interconnects

Cisco UCS Manager CLI Configuration Guide, Release 2.2

C H A P T E R

Configuring Ports and Port Channels

This chapter includes the following sections:

•

Server and Uplink Ports on the 6100 Series Fabric Interconnect, page 61

•

Unified Ports on the Fabric Interconnect, page 63

•

Physical and Backplane Ports, page 71

•

Server Ports, page 74

•

Uplink Ethernet Ports, page 76

•

Appliance Ports, page 77

•

FCoE Uplink Ports, page 82

•

Unified Storage Ports, page 84

•

Unified Uplink Ports, page 85

•

FCoE and Fibre Channel Storage Ports, page 86

•

Uplink Ethernet Port Channels, page 88

•

Appliance Port Channels, page 91

•

Fibre Channel Port Channels, page 96

•

FCoE Port Channels, page 100

•

Unified Uplink Port Channel, page 102

•

Event Detection and Action, page 103

•

Adapter Port Channels, page 108

•

Fabric Port Channels, page 109

Server and Uplink Ports on the 6100 Series Fabric Interconnect

Each Cisco UCS 6100 Series Fabric Interconnect has a set of ports in a fixed port module that you can configure as either server ports or uplink Ethernet ports. These ports are not reserved. They cannot be used by a Cisco

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Server and Uplink Ports on the 6100 Series Fabric Interconnect

UCS domain until you configure them. You can add expansion modules to increase the number of uplink ports on the fabric interconnect or to add uplink Fibre Channel ports to the fabric interconnect.

Note

When you configure a port on a fabric interconnect, the administrative state is automatically set to enabled.

If the port is connected to another device, this may cause traffic disruption. You can disable the port after configuring it.

You need to create LAN pin groups and SAN pin groups to pin traffic from servers to an uplink port.

Note

Ports on the Cisco UCS 6100 Series Fabric Interconnect are not unified. For more information on Unified

Ports, see

Unified Ports on the Fabric Interconnect

Each fabric interconnect can include the following port types:

Server Ports

Server ports handle data traffic between the fabric interconnect and the adapter cards on the servers.

You can only configure server ports on the fixed port module. Expansion modules do not include server ports.

Uplink Ethernet Ports

Uplink Ethernet ports handle Ethernet traffic between the fabric interconnect and the next layer of the network. All network-bound Ethernet traffic is pinned to one of these ports.

By default, Ethernet ports are unconfigured. However, you can configure them to function in the following ways:

• Uplink

• FCoE

• Appliance

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

Uplink Fibre Channel Ports

Uplink Fibre Channel ports handle FCoE traffic between the fabric interconnect and the next layer of the storage area network. All network-bound FCoE traffic is pinned to one of these ports.

By default, Fibre Channel ports are uplink. However, you can configure them to function as Fibre

Channel storage ports. This is useful in cases where Cisco UCS requires a connection to a Direct-Attached

Storage (DAS) device.

You can only configure uplink Fibre Channel ports on an expansion module. The fixed module does not include uplink Fibre Channel ports.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Unified Ports on the Fabric Interconnect

Unified Ports on the Fabric Interconnect

Unified ports are ports on the fabric interconnect that can be configured to carry either Ethernet or Fibre

Channel traffic. These ports are not reserved. A Cisco UCS domain cannot use these ports until you configure them.

Note

When you configure a port on a fabric interconnect, the administrative state is automatically set to enabled.

If the port is connected to another device, this may cause traffic disruption. You can disable the port after configuring it.

Configurable beacon LEDs indicate which unified ports are configured for the selected port mode.

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.

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

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Beacon LEDs for Unified 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.

Beacon LEDs for Unified Ports

Each port on the 6200 series fabric interconnect has a corresponding beacon LED. When the Beacon LED property is configured, the beacon LEDs illuminate, showing you which ports are configured in a given port mode.

You can configure the Beacon LED property to show you which ports are grouped in one port mode: either

Ethernet or Fibre Channel. By default, the Beacon LED property is set to Off.

Note

For unified ports on the expansion module, you can reset the Beacon LED property to the default value of Off during expansion module reboot.

Guidelines for Configuring Unified Ports

Consider the following guidelines and restrictions when configuring unified ports:

Hardware and Software Requirements

Unified ports are supported on the 6200 series fabric interconnect with Cisco UCS Manager, version 2.0.

Unified ports are not supported on 6100 series fabric interconnects, even if they are running Cisco UCS

Manager, version 2.0.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Cautions and Guidelines for Configuring Unified Uplink Ports and Unified Storage Ports

Port Mode Placement

Because the Cisco UCS Manager GUI interface uses a slider to configure the port mode for unified ports on a fixed or expansion module, it automatically enforces the following restrictions which limits how port modes can be assigned to unified ports. When using the Cisco UCS Manager CLI interface, these restrictions are enforced when you commit the transaction to the system configuration. If the port mode configuration violates any of the following restrictions, the Cisco UCS Manager CLI displays an error:

• Ethernet ports must be grouped together in a block. For each module (fixed or expansion), the Ethernet port block must start with the first port and end with an even numbered port.

• Fibre Channel ports must be grouped together in a block. For each module (fixed or expansion), the first port in the Fibre Channel port block must follow the last Ethernet port and extend to include the rest of the ports in the module. For configurations that include only Fibre Channel ports, the Fibre Channel block must start with the first port on the fixed or expansion module.

• Alternating Ethernet and Fibre Channel ports is not supported on a single module.

Example of a valid configuration— Might include unified ports 1–16 on the fixed module configured in

Ethernet port mode and ports 17–32 in Fibre Channel port mode. On the expansion module you could configure ports 1–4 in Ethernet port mode and then configure ports 5–16 in Fibre Channel mode. The rule about alternating

Ethernet and Fibre Channel port types is not violated because this port arrangement complies with the rules on each individual module.

Example of an invalid configuration— Might include a block of Fibre Channel ports starting with port 16.

Because each block of ports has to start with an odd-numbered port, you would have to start the block with port 17.

Note

The total number of uplink Ethernet ports and uplink Ethernet port channel members that can be configured on each fabric interconnect is limited to 31. This limitation includes uplink Ethernet ports and uplink

Ethernet port channel members configured on the expansion module.

Special Considerations for UCS Manager CLI Users

Because the Cisco UCS Manager CLI does not validate port mode changes until you commit the buffer to the system configuration, it is easy to violate the grouping restrictions if you attempt to commit the buffer before creating at least two new interfaces. To prevent errors, we recommend that you wait to commit your changes to the system configuration until you have created new interfaces for all of the unified ports changing from one port mode to another.

Commiting the buffer before configuring multiple interfaces will result in an error, but you do not need to start over. You can continue to configure unified ports until the configuration satisfies the aforementioned requirements.

Cautions and Guidelines for Configuring Unified Uplink Ports and Unified

Storage Ports

The following are cautions and guidelines to follow while working with unified uplink ports and unified storage ports:

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Effect of Port Mode Changes on Data Traffic

• In an unified uplink port, if you enable one component as a SPAN source, the other component will automatically become a SPAN source.

Note

If you create or delete a SPAN source under the Ethernet uplink port, Cisco UCS Manager automatically creates or deletes a SPAN source under the FCoE uplink port. The same happens when you create a SPAN source on the FCOE uplink port.

• You must configure a non default native VLAN on FCoE and unified uplink ports. This VLAN is not used for any traffic. Cisco UCS Manager will reuse an existing fcoe-storage-native-vlan for this purpose.

This fcoe-storage-native-vlan will be used as a native VLAN on FCoE and unified uplinks.

• In an unified uplink port, if you do not specify a non default VLAN for the Ethernet uplink port the fcoe-storage-native-vlan will be assigned as the native VLAN on the unified uplink port. If the Ethernet port has a non default native VLAN specified as native VLAN, this will be assigned as the native VLAN for unified uplink port.

• When you create or delete a member port under an Ethernet port channel, Cisco UCS Manager automatically creates or deletes the member port under FCoE port channel. The same happens when you create or delete a member port in FCoE port channel.

• When you configure an Ethernet port as a standalone port, such as server port, Ethernet uplink, FCoE uplink or FCoE storage and make it as a member port for an Ethernet or FCOE port channel, Cisco UCS

Manager automatically makes this port as a member of both Ethernet and FCoE port channels.

• When you remove the membership for a member port from being a member of server uplink, Ethernet uplink, FCoE uplink or FCoE storage, Cisco UCS Manager deletes the corresponding members ports from Ethernet port channel and FCoE port channel and creates a new standalone port.

• If you downgrade Cisco UCS Manager from release 2.1 to any of the prior releases, all unified uplink ports and port channels will be converted to Ethernet ports and Ethernet port channels when the downgrade is complete. Similarly, all the unified storage ports will be converted to appliance ports.

• For unified uplink ports and unified storage ports, when you create two interfaces, only one license is checked out. As long as either interface is enabled, the license remains checked out. The license will be released only if both the interfaces are disabled for a unified uplink port or a unified storage port.

• Cisco UCS 6100 series fabric interconnect switch can only support 1VF or 1VF-PO facing same downstream NPV switch.

Effect of Port Mode Changes on Data Traffic

Port mode changes can cause an interruption to the data traffic for the Cisco UCS domain. The length of the interruption and the traffic that is affected depend upon the configuration of the Cisco UCS domain and the module on which you made the port mode changes.

Tip

To minimize the traffic disruption during system changes, form a Fibre Channel uplink port-channel across the fixed and expansion modules.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

FC Links Rebalancing

Impact of Port Mode Changes on an Expansion Module

After you make port mode changes on an expansion module, the module reboots. All traffic through ports on the expansion module is interrupted for approximately one minute while the module reboots.

Impact of Port Mode Changes on the Fixed Module in a Cluster Configuration

A cluster configuration has two fabric interconnects. After you make port changes to the fixed module, the fabric interconnect reboots. The impact on the data traffic depends upon whether or not you have configured the server vNICs to failover to the other fabric interconnect when one fails.

If you change the port modes on the expansion module of one fabric interconnect and then wait for that to reboot before changing the port modes on the second fabric interconnect, the following occurs:

• With server vNIC failover, traffic fails over to the other fabric interconnect and no interruption occurs.

• Without server vNIC failover, all data traffic through the fabric interconnect on which you changed the port modes is interrupted for approximately eight minutes while the fabric interconnect reboots.

If you change the port modes on the fixed modules of both fabric interconnects simultaneously, all data traffic through the fabric interconnects are interrupted for approximately eight minutes while the fabric interconnects reboot.

Impact of Port Mode Changes on the Fixed Module in a Standalone Configuration

A standalone configuration has only one fabric interconnect. After you make port changes to the fixed module, the fabric interconnect reboots. All data traffic through the fabric interconnect is interrupted for approximately eight minutes while the fabric interconnect reboots.

FC Links Rebalancing

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

Configuring a Fibre Channel Port Channel, on page 96

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.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Configuring the Port Mode

Configuring the Port Mode

Caution

Changing the port mode on either module can cause an interruption in data traffic because changes to the fixed module require a reboot of the fabric interconnect and changes on an expansion module require a reboot of that module .

If the Cisco UCS domain has a cluster configuration that is set up for high availability and servers with service profiles that are configured for failover, traffic fails over to the other fabric interconnect and data traffic is not interrupted when the port mode is changed on the fixed module.

In the Cisco UCS Manager CLI, there are no new commands to support Unified Ports. Instead, you change the port mode by scoping to the mode for the desired port type and then creating a new interface. When you create a new interface for an already configured slot ID and port ID, UCS Manager deletes the previously configured interface and creates a new one. If a port mode change is required because you configure a port that previously operated in Ethernet port mode to a port type in Fibre Channel port mode, UCS Manager notes the change.

Procedure

Step 1

Command or Action Purpose

UCS-A# scope port-type-mode Enters the specified port type mode for one of the following port types:

eth-server

For configuring server ports.

eth-storage

For configuring Ethernet storage ports and Ethernet storage port channels.

eth-traffic-mon

For configuring Ethernet SPAN ports.

eth-uplink

For configuring Ethernet uplink ports.

fc-storage

For configuring Fibre Channel storage ports.

fc-traffic-mon

For configuring Fibre Channel SPAN ports.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Configuring the Port Mode

Step 2

Step 3

Step 4

Step 5

Command or Action Purpose fc-uplink

For configuring Fibre Channel uplink ports and Fibre

Channel uplink port channels.

UCS-A /port-type-mode # scope

fabric {a | b}

Enters the specified port type mode for the specified fabric.

UCS-A /port-type-mode/fabric

# create interface slot-id

port-id

Creates an interface for the specified port type.

If you are changing the port type from Ethernet port mode to Fibre

Channel port mode, or vice-versa, the following warning appears:

Warning: This operation will change the port mode (from

Ethernet to FC or vice-versa). When committed, this change will require the module to restart.

Create new interfaces for other ports belonging to the Ethernet or Fibre Channel port block.

There are several restrictions that govern how Ethernet and Fibre

Channel ports can be arranged on a fixed or expansion module.

Among other restrictions, it is required that you change ports in groups of two. Violating any of the restrictions outlined in the

Guidelines for Configuring Unified Ports

section will result in an error.

UCS-A

/port-type-mode/fabric/interface

# commit-buffer

Commits the transaction to the system configuration.

Based on the module for which you configured the port modes, data traffic for the Cisco UCS domain is interrupted as follows:

• Fixed module—The fabric interconnect reboots. All data traffic through that fabric interconnect is interrupted. In a cluster configuration that provides high availability and includes servers with vNICs that are configured for failover, traffic fails over to the other fabric interconnect and no interruption occurs. Changing the port mode for both sides at once results in both fabric interconnects rebooting simultaneously and a complete loss of traffic until both fabric interconnects are brought back up.

It takes about 8 minutes for the fixed module to reboot.

• Expansion module—The module reboots. All data traffic through ports in that module is interrupted.

It takes about 1 minute for the expansion module to reboot.

The following example changes ports 3 and 4 on slot 1 from Ethernet uplink ports in Ethernet port mode to uplink Fibre Channel ports in Fibre Channel port mode:

UCS-A#

scope fc-uplink

UCS-A /fc-uplink #

scope fabric a

UCS-A /fc-uplink/fabric #

create interface 1 3

Warning: This operation will change the port mode (from Ethernet to FC or vice-versa).

When committed, this change will require the fixed module to restart.

UCS-A /fc-uplink/fabric/interface* #

UCS-A /fc-uplink/fabric* #

create interface 1 4

Warning: This operation will change the port mode (from Ethernet to FC or vice-versa).

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Configuring the Beacon LEDs for Unified Ports

When committed, this change will require the fixed module to restart.

UCS-A /fc-uplink/fabric/interface* #

commit-buffer

Configuring the Beacon LEDs for Unified Ports

Complete the following task for each module for which you want to configure beacon LEDs.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope fabric-interconnect

{a | b}

UCS-A /fabric # scope card slot-id

Purpose

Enters fabric interconnect mode for the specified fabric.

UCS-A /fabric/card # scope

beacon-led

UCS-A /fabric/card/beacon-led # set

admin-state {eth | fc | off}

Enters card mode for the specified fixed or expansion module.

Enters beacon LED mode.

Specifies which port mode is represented by illuminated beacon LED lights.

eth

All of the Unified Ports configured in Ethernet mode illuminate.

All of the Unified Ports configured in Fibre

Channel mode illuminate.

Step 5

UCS-A /fabric/card/beacon-led #

commit-buffer off

Beacon LED lights for all ports on the module are turned off.

Commits the transaction to the system configuration.

The following example illuminates all of the beacon lights for Unified Ports in Ethernet port mode and commits the transaction:

UCS-A#

scope fabric-interconnect a

UCS-A /fabric #

scope card 1

UCS-A /fabric/card #

scope beacon-led

UCS-A /fabric/card/beacon-led #

set admin-state eth

UCS-A /fabric/card/beacon-led* #

commit-buffer

UCS-A /fabric/card/beacon-led #

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Physical and Backplane Ports

Physical and Backplane Ports

Displaying Physical Port Statistics Obtained From the ASIC

Procedure

Step 1

Step 2

Command or Action Purpose

UCS-A /fabric-interconnect # connect nxos

{a | b}

Enters NX-OS mode for the fabric interconnect.

UCS-A(nxos)# show interface ethernet

slot/port

Displays physical port statistics that are obtained from the ASIC.

The following example shows how to display physical port statistics that are obtained from the ASIC:

UCS-A /fabric-interconnect #

connect nxos a

UCS-A(nxos)#

show interface ethernet 1/11

Ethernet1/11 is up

Dedicated Interface

Hardware: 40000 Ethernet, address: a46c.2ae3.0e1a (bia a46c.2ae3.0e1a)

Description: S: Server

MTU 1500 bytes, BW 40000000 Kbit, DLY 10 usec reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA

Port mode is fex-fabric full-duplex, 40 Gb/s, media type is 40G

Beacon is turned off

Input flow-control is off, output flow-control is off

Rate mode is dedicated

Switchport monitor is off

EtherType is 0x8100

Last link flapped 01:25:42

Last clearing of "show interface" counters never

2 interface resets

30 seconds input rate 22664 bits/sec, 2833 bytes/sec, 3 packets/sec

30 seconds output rate 9512 bits/sec, 1189 bytes/sec, 1189 bytes/sec, 4 packets/sec

Load-Interval #2: 5 minute (300 seconds) input rate 33.80 Kbps, 5 pps; output rate 1.23 Mbps, 71 pps

126057 unicast packets 1744 multicast packets 12877 broadcast packets

140693 input packets 28702696 bytes

3351 jumbo packets 0 storm suppression bytes

0 runts 0 giants 0 CRC 0 no buffer

0 input error 0 short frame 0 overrun 0 underrun 0 ignored

0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop

0 input with dribble 184 input discard

0 Rx pause

919778 unicast packets 6991 multicast packets 29 broadcast packets

926798 output packets 1237109219 bytes

794275 jumbo packets

0 output errors 0 collision 0 deferred 0 late collision

0 lost carrier 0 no carrier 0 babble 0 output discard

0 Tx pause

Errors on Peer port (NIF):

8300 toolong frames 8400 undersize frames 8500 fragment frames

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Displaying Physical Ports on the Fabric Interconnect That Correspond to Physical Ports on BCM

8600 crcErr_not_stomped frames 8700 crcErr_stomped frames 8800 inRangeErr frames

8200 frames_with_error

Displaying Physical Ports on the Fabric Interconnect That Correspond to

Physical Ports on BCM

Procedure

Step 1

Step 2

Command or Action Purpose

UCS-A /fabric-interconnect # connect nxos {a

| b}

Enters NX-OS mode for the fabric interconnect.

UCS-A(nxos)# show hardware internal

bcm-usd info port-info | grep interface_slot_id

Displays physical ports on a fabric interconnect that correspond to physical ports on BCM.

The following example shows how to display physical ports on a fabric interconnect that correspond to physical ports on BCM:

UCS-A /fabric-interconnect #

connect nxos a

UCS-A(nxos)#

show hardware internal bcm-usd info port-info | grep Eth 1/11

Eth1/11 0x1a00a000 ena 40G 40G up

41 xe-40 57 CR4 sw 4044 0 uta 2240 0 fd dis blk dis dis

Verifying Status of Backplane Ports

Procedure

Step 1

Step 2

Command or Action

UCS-A /fabric-interconnect # connect

nxos {a | b}

UCS-A(nxos)# show interface br

Purpose

Enters NX-OS mode for the fabric interconnect.

Displays the configuration of the interface, including the speed and status of the backplane ports.

The following example shows how to verify the status of backplane ports for fabric interconnect A:

UCS-A /fabric-interconnect #

connect nxos a

UCS-A(nxos)#

show interface br

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Verifying Status of Backplane Ports

--------------------------------------------------------------------------------

Ethernet VLAN Type Mode Status Reason Speed Port

Interface Ch #

--------------------------------------------------------------------------------

Eth1/1 1 eth access down SFP not inserted 40G(D) --

Eth1/2 1

Br-Eth1/3/1 1 eth eth access down access down

SFP not inserted

Administratively down

40G(D) --

10G(D) --

Br-Eth1/3/2 1

Br-Eth1/3/3 1

Br-Eth1/3/4 1 eth access down eth access down eth access down

Administratively down

10G(D) --

Eth1/4 1

Br-Eth1/5/1 4044

Br-Eth1/5/2 4044

Br-Eth1/5/3 4044

Br-Eth1/5/4 4044

Eth1/6 1

Eth1/7

Eth1/8

Eth1/9

Eth1/10

Eth1/11

1 eth eth eth eth eth eth eth eth eth access down eth access down eth access down trunk trunk trunk trunk down down down down access down access down access down fabric up

SFP not inserted

Link not connected

SFP not inserted

SFP not inserted none

40G(D) --

10G(D) --

40G(D) --

Eth1/12

Eth1/13

Eth1/14

Eth1/15

Eth1/16

Eth1/17

Eth1/18

Eth1/19

Eth1/20

Br-Eth1/21/1 1

Br-Eth1/21/2 1

Br-Eth1/21/3 1

Br-Eth1/21/4 1

Eth1/22 1

Eth1/23

Eth1/24

Eth1/25

Eth1/26

Eth1/27

Eth1/28

Eth1/29

Eth1/30

Eth1/31

Eth1/32

1 eth eth eth eth eth eth eth eth access down eth access down eth trunk up eth trunk up eth trunk down eth trunk up eth eth eth eth eth eth eth eth eth eth eth access down access down access down access down access down access down access down access down access down access down access down access down access down access down access down access down access down access down

SFP not inserted

SFP not inserted none none

Link not connected none

SFP not inserted

40G(D) --

10G(D) --

40G(D) --

--------------------------------------------------------------------------------

Port-channel VLAN Type Mode Status Reason Speed Protocol

Interface

--------------------------------------------------------------------------------

Po1285

Po1286

Po1287

Po1288

Po1289

1 eth eth eth eth eth vntag vntag vntag vntag vntag up up up up up none none none none none a-10G(D) a-10G(D) a-10G(D) a-10G(D) a-10G(D) none none none none none

--------------------------------------------------------------------------------

Port VRF Status IP Address Speed MTU

-------------------------------------------------------------------------------mgmt0 -down 10.197.157.252

-1500

--------------------------------------------------------------------------------

Vethernet VLAN Type Mode Status Reason Speed

--------------------------------------------------------------------------------

Veth691

Veth692

4047

4047 virt trunk virt trunk down up nonParticipating none auto auto

Veth693

Veth695

Veth699

1 virt trunk down virt trunk up virt trunk up nonParticipating none none auto auto auto

-------------------------------------------------------------------------------

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Server Ports

Interface Secondary VLAN(Type) Status Reason

-------------------------------------------------------------------------------

Vlan1 -down Administratively down

Eth1/1/16

Eth1/1/17

Eth1/1/18

Eth1/1/19

Eth1/1/20

Eth1/1/21

Eth1/1/22

Eth1/1/23

Eth1/1/24

Eth1/1/25

Eth1/1/26

Eth1/1/27

Eth1/1/28

Eth1/1/29

Eth1/1/30

Eth1/1/31

Eth1/1/32

Eth1/1/33

--------------------------------------------------------------------------------

Ethernet

Interface

VLAN Type Mode Status Reason Speed Port

Ch #

--------------------------------------------------------------------------------

Eth1/1/1 1 eth vntag up none 10G(D) 1286

Eth1/1/2

Eth1/1/3

Eth1/1/4

1 eth access down eth vntag up eth access down

Administratively down none

Administratively down

10G(D) --

10G(D) 1286

10G(D) --

Eth1/1/5

Eth1/1/6

Eth1/1/7

Eth1/1/8

Eth1/1/9

Eth1/1/10

Eth1/1/11

Eth1/1/12

Eth1/1/13

Eth1/1/14

Eth1/1/15

1 eth eth eth eth eth eth eth eth eth vntag up eth access down eth vntag access down vntag access down vntag access down vntag access down vntag up up up up up none

Administratively down none

10G(D) 1287

10G(D) --

10G(D) 1287

10G(D) --

10G(D) 1289

10G(D) --

10G(D) 1289

10G(D) --

10G(D) 1285

10G(D) --

10G(D) 1285

4044 eth access down eth access down eth vntag up eth access down eth vntag up eth access down eth access down eth access down eth access down eth access down eth access down eth access down eth access down eth access down eth access down eth access down eth access down eth trunk up

Administratively down

Administratively down none

Administratively down

Administratively down none

10G(D) --

10G(D) 1288

10G(D) --

10G(D) 1288

10G(D) --

1000(D) --

Server Ports

Configuring a Server Port

All of the port types listed are configurable on both the fixed and expansion module, including server ports, which are not configurable on the 6100 series fabric interconnect expansion module, but are configurable on the 6200 series fabric interconnect expansion module.

Procedure

Step 1

Command or Action

UCS-A# scope eth-server

Purpose

Enters Ethernet server mode.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Unconfiguring a Server Port

Step 2

Step 3

Step 4

Command or Action

UCS-A /eth-server # scope fabric {a | b}

Purpose

Enters Ethernet server fabric mode for the specified fabric.

UCS-A /eth-server/fabric # create interface

slot-num port-num

Creates an interface for the specified Ethernet server port.

UCS-A /eth-server/fabric # commit-buffer Commits the transaction to the system configuration.

The following example shows how to create an interface for Ethernet server port 4 on slot 1 of fabric B and commit the transaction:

UCS-A#

scope eth-server

UCS-A /eth-server #

scope fabric b

UCS-A /eth-server/fabric #

create interface 1 4

UCS-A /eth-server/fabric* #

commit-buffer

UCS-A /eth-server/fabric #

Unconfiguring a Server Port

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope eth-server

UCS-A /eth-server # scope fabric {a | b}

Purpose

Enters Ethernet server mode.

Enters Ethernet server fabric mode for the specified fabric.

UCS-A /eth-server/fabric # delete interface

slot-num port-num

Deletes the interface for the specified Ethernet server port.

UCS-A /eth-server/fabric # commit-buffer Commits the transaction to the system configuration.

The following example unconfigures Ethernet server port 12 on slot 1 of fabric B and commits the transaction:

UCS-A#

scope eth-server

UCS-A /eth-server #

scope fabric b

UCS-A /eth-server/fabric #

delete interface 1 12

UCS-A /eth-server/fabric* #

commit-buffer

UCS-A /eth-server/fabric #

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Uplink Ethernet Ports

Uplink Ethernet Ports

Configuring an Uplink Ethernet Port

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

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

UCS-A# scope eth-uplink

Purpose

Enters Ethernet uplink mode.

UCS-A /eth-uplink # scope fabric a |

Enters Ethernet uplink fabric mode for the specified fabric.

UCS-A /eth-uplink/fabric # create

interface slot-num port-num

Creates an interface for the specified Ethernet uplink port.

UCS-A /eth-uplink/fabric # set speed

{10gbps | 1gbps}

(Optional)

Sets the speed for the specified Ethernet uplink port.

Note

For the 6100 series fabric interconnects, the admin speed is only configurable for the first eight ports on a 20-port fabric interconnect and the first 16 ports on a 40-port fabric interconnect.

UCS-A /eth-uplink/fabric #

commit-buffer

Commits the transaction to the system configuration.

The following example shows how to create an interface for Ethernet uplink port 3 on slot 2 of fabric B, set the speed to 10 gbps, and commit the transaction:

UCS-A#

scope eth-uplink

UCS-A /eth-uplink #

scope fabric b

UCS-A /eth-uplink/fabric #

create interface 2 3

UCS-A /eth-uplink/fabric #

set speed 10gbps

UCS-A /eth-uplink/fabric* #

commit-buffer

UCS-A /eth-uplink/fabric #

Unconfiguring an Uplink Ethernet Port

Procedure

Step 1

Command or Action

UCS-A# scope eth-uplink

Purpose

Enters Ethernet uplink mode.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Appliance Ports

Step 2

Step 3

Step 4

Command or Action

UCS-A /eth-uplink # scope fabric {a | b}

Purpose

Enters Ethernet uplink fabric mode for the specified fabric.

UCS-A /eth-uplink/fabric # delete interface

slot-num port-num

Deletes the interface for the specified Ethernet uplink port.

UCS-A /eth-uplink/fabric # commit-buffer Commits the transaction to the system configuration.

The following example unconfigures Ethernet uplink port 3 on slot 2 of fabric B and commits the transaction:

UCS-A#

scope eth-uplink

UCS-A /eth-uplink #

scope fabric b

UCS-A /eth-uplink/fabric #

delete interface 2 3

UCS-A /eth-uplink/fabric* #

commit-buffer

UCS-A /eth-uplink/fabric #

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 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.

Procedure

Step 1

Step 2

Step 3

Command or Action

UCS-A# scope eth-storage

UCS-A /eth-storage # scope

fabric{a | b}

UCS-A /eth-storage/fabric #

create interface slot-num

port-num

Purpose

Enters Ethernet storage mode.

Enters Ethernet storage mode for the specified fabric.

Creates an interface for the specified appliance port.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Configuring an Appliance Port

Step 4

Step 5

Step 6

Step 7

Step 8

Command or Action Purpose

UCS-A

/eth-storage/fabric/interface # set

portmode {access | trunk}

(Optional)

Specifies whether the port mode is access or trunk. By default, the mode is set to trunk.

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.

UCS-A

/eth-storage/fabric/interface # set

pingroupname pin-group name

(Optional)

Specifies the appliance pin target to the specified fabric and port, or fabric and port channel.

UCS-A

/eth-storage/fabric/interface # set

prio sys-class-name

(Optional)

Specifies the QoS class for the appliance port. By default, the priority is set to best-effort.

The sys-class-name argument can be one of the following class keywords:

• Fc—Use this priority for QoS policies that control vHBA traffic only.

• Platinum—Use this priority for QoS policies that control vNIC traffic only.

• Gold—Use this priority for QoS policies that control vNIC traffic only.

• Silver—Use this priority for QoS policies that control vNIC traffic only.

• Bronze—Use this priority for QoS policies that control vNIC traffic only.

• Best Effort—Do not use this priority. It is reserved for the Basic Ethernet traffic lane. If you assign this priority to a QoS policy and configure another system class as CoS

0, Cisco UCS Manager does not default to this system class. It defaults to the priority with CoS 0 for that traffic.

UCS-A

/eth-storage/fabric/interface # set

adminspeed {10gbps | 1 gbps}

(Optional)

Specifies the admin speed for the interface. By default, the admin speed is set to 10gbps.

UCS-A

/eth-storage/fabric/interface #

commit buffer

Commits the transaction to the system configuration.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Assigning a Target MAC Address to an Appliance Port or Appliance Port Channel

The following example creates an interface for an appliance port 2 on slot 3 of fabric B, sets the port mode to access, pins the appliance port to a pin group called pingroup1, sets the QoS class to fc, sets the admin speed to 10 gbps, and commits the transaction:

UCS-A#

scope eth-storage

UCS-A /eth-storage #

scope fabric b

UCS-A /eth-storage/fabric #

create interface 3 2

UCS-A /eth-storage/fabric* #

set portmode access

UCS-A /eth-storage/fabric* #

set pingroupname pingroup1

UCS-A /eth-storage/fabric* #

set prio fc

UCS-A /eth-storage/fabric* #

set adminspeed 10gbps

UCS-A /eth-storage/fabric* #

commit-buffer

UCS-A /eth-storage/fabric #

What to Do Next

Assign a VLAN or target MAC address for the appliance port.

Assigning a Target MAC Address to an Appliance Port or Appliance Port

Channel

The following procedure assigns a target MAC address to an appliance port. To assign a target MAC address to an appliance port channel, scope to the port channel instead of the interface.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

UCS-A# scope eth-storage

UCS-A

/eth-storage/fabric/interface/eth-target #

set mac-address mac-address

Purpose

Enters Ethernet storage mode.

UCS-A /eth-storage # scope fabric{a | b} Enters Ethernet storage mode for the specified fabric.

UCS-A /eth-storage/fabric # scope

interface slot-id port-id

Enters Ethernet interface mode for the specified interface.

Note

To assign a target MAC address to an appliance port channel, use the scope

port-channel command instead of scope

interface .

UCS-A /eth-storage/fabric/interface #

create eth-target eth-target name

Specifies the name for the specified MAC address target.

Specifies the MAC address in nn:nn:nn:nn:nn:nn format.

The following example assigns a target MAC address for an appliance device on port 3, slot 2 of fabric B and commits the transaction:

UCS-A#

scope eth-storage

UCS-A /eth-storage* #

scope fabric b

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Creating an Appliance Port

UCS-A /eth-storage/fabric* #

scope interface 2 3

UCS-A /eth-storage/fabric/interface* #

create eth-target macname

UCS-A /eth-storage/fabric/interface* #

set mac-address 01:23:45:67:89:ab

UCS-A /eth-storage/fabric/interface* #

commit-buffer

UCS-A /eth-storage/fabric #

The following example assigns a target MAC address for appliance devices on port channel 13 of fabric B and commits the transaction:

UCS-A#

scope eth-storage

UCS-A /eth-storage* #

scope fabric b

UCS-A /eth-storage/fabric* #

scope port-channel 13

UCS-A /eth-storage/fabric/port-channel* #

create eth-target macname

UCS-A /eth-storage/fabric/port-channel* #

set mac-address 01:23:45:67:89:ab

UCS-A /eth-storage/fabric/port-channel* #

commit-buffer

UCS-A /eth-storage/fabric #

Creating an Appliance Port

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Command or Action

UCS-A# scope eth-storage

Purpose

Enters Ethernet storage mode.

UCS-A/eth-storage# create vlan

vlan-name vlan-id

UCS-A/eth-storage# create vlan

vlan-name vlan-id

Creates a named VLAN, specifies the VLAN name and VLAN ID, and enters Ethernet storage

VLAN mode

UCS-A/eth-storage/vlan# set sharing

primary

Saves the changes.

UCS-A/eth-storage/vlan# commit buffer Commits the transaction to the system configuration.

Creates a named VLAN, specifies the VLAN name and VLAN ID, and enters Ethernet storage

VLAN mode .

UCS-A/eth-storage/vlan# set sharing

community

Associates the primary VLAN to the secondary

VLAN that you are creating.

UCS-A/eth-storage/vlan# set pubnwname

primary vlan-name

Specifies the primary VLAN to be associated with this secondary VLAN.

UCS-A/eth-storage/vlan# commit buffer Commits the transaction to the system configuration.

The following example creates an appliance port:

UCS-A#

scope eth-storage

UCS-A/eth-storage#

create vlan PRI600 600

UCS-A/eth-storage/vlan* #

set sharing primary

UCS-A/eth-storage/vlan* #

commit-buffer

UCS-A/eth-storage #

create vlan COM602 602

UCS-A/eth-storage/vlan* #

set sharing isolated

UCS-A/eth-storage/vlan* #

set pubnwname PRI600

UCS-A/eth-storage/vlan* #

commit-buffer

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Mapping an Appliance Port to a Community VLAN

Mapping an Appliance Port to a Community VLAN

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Command or Action

UCS-A# scope eth-storage

Purpose

Enters Ethernet storage mode.

UCS-A/eth-storage# scope fabric {a|b} Enters Ethernet storage fabric interconnect mode for the specified fabric interconnect.

UCS-A/eth-storage/fabric# create

interface slot-num port-num

Creates an interface for the specified Ethernet server port.

UCS-A/eth-storage/fabric/interface# exit Exits from the interface.

Note

Ensure you commit the transaction after associating with the VLAN.

UCS-A/eth-storage/fabric# exit Exits from the fabric.

UCS-A/eth-storage# scope vlan

vlan-name

Enters the specified VLAN.

Note

Ensure community VLAN is created in the appliance cloud.

UCS-A/eth-storage/vlan# create

member-port fabric slot-num port-num

Creates the member port for the specified fabric, assigns the slot number, and port number and enters member port configuration.

UCS-A/eth-storage/vlan/member-port#

commit

Commits the transaction to the system configuration.

The following example maps an appliance port to an community VLAN:

UCS-A# scope eth-storage

UCS-A/eth-storage#

scope fabric a

UCS-A/eth-storage/fabric#

create interface 1 22

UCS-A/eth-storage/fabric/interface*#

exit

UCS-A/eth-storage/fabric*#

exit

UCS-A/eth-storage*#

scope vlan COM602

UCS-A/eth-storage/vlan*#

create member-port a 1 22

UCS-A/eth-storage/vlan/member-port*

commit

Unconfiguring an Appliance Port

Procedure

Step 1

Command or Action

UCS-A # scope eth-storage

Purpose

Enters Ethernet storage mode.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

FCoE Uplink Ports

Step 2

Step 3

Step 4

Command or Action

UCS-A /eth-storage # scope fabric {a | b}

Purpose

Enters Ethernet storage mode for the specified fabric.

UCS-A /eth-storage/fabric # delete

eth-interface slot-num port-num

Deletes the interface for the specified appliance port.

UCS-A /eth-storage/fabric # commit-buffer Commits the transaction to the system configuration.

The following example unconfigures appliance port 3 on slot 2 of fabric B and commits the transaction:

UCS-A#

scope eth-storage

UCS-A /eth-storage #

scope fabric b

UCS-A /eth-storage/fabric #

delete eth-interface 2 3

UCS-A /eth-storage/fabric* #

commit-buffer

UCS-A /eth-storage/fabric #

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 a FCoE Uplink Port

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Unconfiguring a FCoE Uplink Port

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope fc-uplink

Purpose

Enters FC Uplink mode.

UCS-A /fc-uplink # scope fabric{a | b} Enters FC - Uplink mode for the specific fabric.

UCS-A /fc-uplink/fabric # create fcoeinterface

slot-numberport-number

Creates interface for the specified FCoE uplink port.

UCS-A /fc-uplink/fabric/fabricinterface #

commit-buffer

Commits the transaction to the system configuration.

The following example creates an interface for FCoE uplink port 1 on slot 8 of fabric A and commits the transaction:

UCS-A#

scope fc-uplink

UCS-A /fc-uplink #

scope fabric a

UCS-A /fc-uplink/fabric #

create fcoeinterface 1 8

UCS-A /fc-uplink/fabric/fcoeinterface* #

commit-buffer

UCS-A /fc-uplink/fabric/fcoeinterface #

Unconfiguring a FCoE Uplink Port

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope fc-uplink

Purpose

Enters FC Uplink mode.

UCS-A /fc-uplink # scope fabric{a | b} Enters FC - Uplink mode for the specific fabric.

UCS-A /fc-uplink/fabric # delete fcoeinterface

slot-numberport-number

Deletes the specified interface.

UCS-A /fc-uplink/fabric/fabricinterface #

commit-buffer

Commits the transaction to the system configuration.

The following example deletes the FCoE uplink interface on port 1 on slot 8 of fabric A and commits the transaction:

UCS-A#

scope fc-uplink

UCS-A /fc-uplink #

scope fabric a

UCS-A /fc-uplink/fabric #

delete fcoeinterface 1 8

UCS-A /fc-uplink/fabric/fcoeinterface* #

commit-buffer

UCS-A /fc-uplink/fabric/fcoeinterface #

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Viewing FCoE Uplink Ports

Viewing FCoE Uplink Ports

Procedure

Step 1

Step 2

Step 3

Command or Action

UCS-A# scope fc-uplink

Purpose

Enters FC Uplink mode.

UCS-A /fc-uplink # scope fabric{a | b} Enters FC - Uplink mode for the specific fabric.

UCS-A /fc-uplink/fabric # show fcoeinterface Lists the available interfaces.

The following example displays the available FCoE uplink interfaces on fabric A:

UCS-A#

scope fc-uplink

UCS-A /fc-uplink #

scope fabric a

UCS-A /fc-uplink/fabric #

show fcoeinterface

FCoE Interface:

Slot Id c State

Port Id Admin State Operational State Operational State Reason Li

Grace Prd

---------- ---------- ----------- ----------------- ------------------------- --

------------------ --------cense Ok

1 26 Enabled

Indeterminate Li

Fcoe Member Port:

Port-channel Slot Port Oper State State Reason

------------ ----- ----- --------------- ------------

10 Sfp Not Present Unknown

3 Sfp Not Present Unknown

4 Sfp Not Present Unknown

6 Sfp Not Present Unknown

8 Sfp Not Present Unknown

2 1 7 Sfp Not Present Unknown

UCS-A /fc-uplink/fabric #

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.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Configuring a Unified Storage 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 a Unified Storage Port

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Command or Action

UCS-A# scope eth-storage

UCS-A /eth-storage # scope fabric{a | b}

Purpose

Enters Ethernet storage mode.

Enters Ethernet storage mode for the specified fabric.

UCS-A /eth-storage/fabric # create interface

slot-num port-num

Creates an interface for the specified appliance port.

UCS-A /eth-storage/fabric/interface* #

commit buffer

Commits the transaction to the system configuration.

UCS-A /eth-storage/fabric/interface* # scope

fc-storage

Enters FC storage mode.

UCS-A /fc-storage* # scope fabric{a | b} Enters Ethernet storage mode for the specific appliance port.

UCS-A /fc-storage/fabric # create interface

fcoe slot-num port-num

Adds FCoE storage port mode on the appliance port mode and creates a unified storage port..

The following example creates an interface for an appliance port 2 on slot 3 of fabric A, adds fc storage to the same port to convert it as an unified port , and commits the transaction:

UCS-A#

scope eth-storage

UCS-A /eth-storage #

scope fabric a

UCS-A /eth-storage/fabric #

create interface 3 2

UCS-A /eth-storage/fabric* #

commit-buffer

UCS-A /eth-storage/fabric* #

scope fc-storage

UCS-A /fc-storage*#

scope fabric a

UCS-A /fc-storage/fabric* #

create interface fcoe 3 2

UCS-A /fc-storage/fabric* #

commit-buffer

UCS-A /fc-storage/fabric*

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.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Configuring a Unified Uplink Port

• 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 a Unified Uplink Port

To configure a unified uplink port, you will convert an existing FCoE uplink port as a unified port.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope eth-uplink

UCS-A /eth-uplink # scope fabric {a | b}

Purpose

Enters Ethernet uplink mode.

Enters Ethernet uplink fabric mode for the specified fabric.

UCS-A /eth-uplink/fabric # create interface

Converts the FCoE uplink port as a unified port.

UCS-A /eth-uplink/fabric/port-channel #

commit-buffer

Commits the transaction to the system configuration.

The following example creates a unified uplink port on an existing FCoE port:

UCS-A#

scope eth-uplink

UCS-A /eth-uplink #

scope fabric b

UCS-A /eth-uplink/fabric #

create interface 1 5

UCS-A /eth-uplink/fabric/interface* #

commit-buffer

UCS-A /eth-uplink/interface #

FCoE and Fibre Channel Storage Ports

Configuring a Fibre Channel Storage or FCoE Port

Procedure

Step 1

Step 2

Command or Action

UCS-A# scope fc-storage

UCS-A /fc-storage # scope fabric {a | b}

Purpose

Enters Fibre Channel storage mode.

Enters Fibre Channel storage mode for the specified fabric.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Unconfiguring a Fibre Channel Storage or FCoE Port

Step 3

Step 4

Command or Action Purpose

UCS-A /fc-storage/fabric # create interface

{fc | fcoe} slot-num port-num

Creates an interface for the specified Fibre

Channel storage port.

UCS-A /fc-storage/fabric # commit-buffer Commits the transaction.

The following example creates an interface for Fibre Channel storage port 10 on slot 2 of fabric A and commits the transaction:

UCS-A#

scope fc-storage

UCS-A /fc-storage #

scope fabric a

UCS-A /fc-storage/fabric* #

create interface fc 2 10

UCS-A /fc-storage/fabric #

commit-buffer

What to Do Next

Assign a VSAN.

Unconfiguring a Fibre Channel Storage or FCoE Port

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope fc-storage

UCS-A /fc-storage # scope fabric {a | b}

Purpose

Enters Fibre Channel storage mode.

Enters Fibre Channel storage mode for the specified fabric.

UCS-A /fc-storage/fabric # delete interface

{fc | fcoe} slot-num port-num

Deletes the interface for the specified Fibre

Channel or FCoE storage port.

UCS-A /fc-storage/fabric # commit-buffer Commits the transaction.

The following example unconfigures Fibre Channel storage port 10 on slot 2 of fabric A and commits the transaction:

UCS-A#

scope fc-storage

UCS-A /fc-storage #

scope fabric a

UCS-A /fc-storage/fabric* #

delete interface fc 2 10

UCS-A /fc-storage/fabric #

commit-buffer

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Restoring a Fibre Channel Storage Port Back to an Uplink Fibre Channel Port

Restoring a Fibre Channel Storage Port Back to an Uplink Fibre Channel Port

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope fc-uplink

Purpose

Enters Fibre Channel uplink mode.

UCS-A /fc-uplink # scope fabric {a | b} Enters Fibre Channel uplink mode for the specified fabric.

UCS-A /fc-uplink/fabric # create interface

slot-num port-num

Creates an interface for the specified Fibre

Channel uplink port.

UCS-A /fc-uplink/fabric # commit-buffer Commits the transaction.

The following example creates an interface for Fibre Channel uplink port 10 on slot 2 of fabric A and commits the transaction:

UCS-A#

scope fc-uplink

UCS-A /fc-uplink #

scope fabric a

UCS-A /fc-uplink/fabric* #

create interface 2 10

UCS-A /fc-uplink/fabric #

commit-buffer

Uplink Ethernet Port Channels

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

Manager, you create a port channel first and then add uplink Ethernet ports to the port channel. You can add up to 16 uplink Ethernet ports to a port channel.

Important

The state of a configured port changes to unconfigured in the following scenarios:

• The port is deleted or removed from a port channel. The port channel can be of any type, such as, uplink or storage.

• A port channel is deleted.

Note

Cisco UCS uses Link Aggregation Control Protocol (LACP), not Port Aggregation Protocol (PAgP), to group the uplink Ethernet ports into a port channel. If the ports on the upstream switch are not configured for LACP, the fabric interconnects treat all ports in an uplink Ethernet port channel as individual ports, and therefore forward packets.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Configuring an Uplink Ethernet Port Channel

Configuring an Uplink Ethernet Port Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Command or Action

UCS-A# scope eth-uplink

UCS-A /eth-uplink # scope fabric {a | b } Enters Ethernet uplink fabric mode for the specified fabric.

UCS-A /eth-uplink/fabric # create

port-channel port-num

Creates a port channel on the specified Ethernet uplink port, and enters Ethernet uplink fabric port channel mode.

UCS-A /eth-uplink/fabric/port-channel #

{enable | disable}

Purpose

Enters Ethernet uplink mode.

UCS-A /eth-uplink/fabric/port-channel #

set name port-chan-name

UCS-A /eth-uplink/fabric/port-channel #

set flow-control-policy policy-name

UCS-A /eth-uplink/fabric/port-channel #

commit-buffer

(Optional)

Enables or disables the administrative state of the port channel. The port channel is disabled by default.

(Optional)

Specifies the name for the port channel.

(Optional)

Assigns the specified flow control policy to the port channel.

Commits the transaction to the system configuration.

The following example creates a port channel on port 13 of fabric A, sets the name to portchan13a, enables the administrative state, assigns the flow control policy named flow-con-pol432 to the port channel, and commits the transaction:

UCS-A#

scope eth-uplink

UCS-A /eth-uplink #

scope fabric a

UCS-A /eth-uplink/fabric #

create port-channel 13

UCS-A /eth-uplink/fabric/port-channel* #

enable

UCS-A /eth-uplink/fabric/port-channel* #

set name portchan13a

UCS-A /eth-uplink/fabric/port-channel* #

set flow-control-policy flow-con-pol432

UCS-A /eth-uplink/fabric/port-channel* #

commit-buffer

UCS-A /eth-uplink/fabric/port-channel #

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Unconfiguring an Uplink Ethernet Port Channel

Unconfiguring an Uplink Ethernet Port Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope eth-uplink

Purpose

Enters Ethernet uplink mode.

UCS-A /eth-uplink # scope fabric {a | b } Enters Ethernet uplink fabric mode for the specified fabric.

UCS-A /eth-uplink/fabric # delete

port-channel port-num

Deletes the port channel on the specified

Ethernet uplink port.

UCS-A /eth-uplink/fabric # commit-buffer Commits the transaction to the system configuration.

The following example unconfigures the port channel on port 13 of fabric A and commits the transaction:

UCS-A#

scope eth-uplink

UCS-A /eth-uplink #

scope fabric a

UCS-A /eth-uplink/fabric #

delete port-channel 13

UCS-A /eth-uplink/fabric* #

commit-buffer

UCS-A /eth-uplink/fabric #

Adding a Member Port to an Uplink Ethernet Port Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

UCS-A# scope eth-uplink

UCS-A /eth-uplink/fabric/port-channel #

commit-buffer

Purpose

Enters Ethernet uplink mode.

UCS-A /eth-uplink # scope fabric {a | b } Enters Ethernet uplink fabric mode for the specified fabric.

UCS-A /eth-uplink/fabric # scope

port-channel port-num

Enters Ethernet uplink fabric port channel mode for the specified port channel.

UCS-A /eth-uplink/fabric/port-channel #

create member-port slot-num port-num

Creates the specified member port from the port channel and enters Ethernet uplink fabric port channel member port mode.

Commits the transaction to the system configuration.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Deleting a Member Port from an Uplink Ethernet Port Channel

The following example adds the member port on slot 1, port 7 to the port channel on port 13 of fabric A and commits the transaction.

UCS-A#

scope eth-uplink

UCS-A /eth-uplink #

scope fabric a

UCS-A /eth-uplink/fabric #

scope port-channel 13

UCS-A /eth-uplink/fabric/port-channel #

create member-port 1 7

UCS-A /eth-uplink/fabric/port-channel* #

commit-buffer

UCS-A /eth-uplink/fabric/port-channel #

Deleting a Member Port from an Uplink Ethernet Port Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

UCS-A# scope eth-uplink

UCS-A /eth-uplink # scope fabric {a | b }

UCS-A /eth-uplink/fabric # scope

port-channel port-num

UCS-A /eth-uplink/fabric/port-channel #

delete member-port slot-num port-num

UCS-A /eth-uplink/fabric/port-channel #

commit-buffer

Purpose

Enters Ethernet uplink mode.

Enters Ethernet uplink fabric mode for the specified fabric.

Enters Ethernet uplink fabric port channel mode for the specified port channel.

Deletes the specified member port from the port channel.

Commits the transaction to the system configuration.

The following example deletes a member port from the port channel on port 13 of fabric A and commits the transaction:

UCS-A#

scope eth-uplink

UCS-A /eth-uplink #

scope fabric a

UCS-A /eth-uplink/fabric #

scope port-channel 13

UCS-A /eth-uplink/fabric/port-channel #

delete member-port 1 7

UCS-A /eth-uplink/fabric/port-channel* #

commit-buffer

UCS-A /eth-uplink/fabric/port-channel #

Appliance Port Channels

An appliance port channel allows you to group several physical appliance ports to create one logical Ethernet storage link for the purpose of providing fault-tolerance and high-speed connectivity. In Cisco UCS Manager, you create a port channel first and then add appliance ports to the port channel. You can add up to eight appliance ports to a port channel.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Configuring an Appliance Port Channel

Configuring an Appliance Port Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Command or Action

UCS-A# scope eth-storage

Purpose

Enters Ethernet storage mode.

UCS-A /eth-storage # scope fabric

{a | b }

UCS-A /eth-storage/fabric # create

port-channel port-num

Enters Ethernet storage fabric mode for the specified fabric.

Creates a port channel on the specified Ethernet storage port, and enters Ethernet storage fabric port channel mode.

UCS-A

/eth-storage/fabric/port-channel #

{enable | disable}

(Optional)

Enables or disables the administrative state of the port channel. The port channel is disabled by default.

UCS-A

/eth-storage/fabric/port-channel # set

name port-chan-name

(Optional)

Specifies the name for the port channel.

UCS-A

/eth-storage/fabric/port-channel # set

pingroupname pin-group name

(Optional)

Specifies the appliance pin target to the specified fabric and port, or fabric and port channel.

UCS-A

/eth-storage/fabric/port-channel # set

portmode {access | trunk}

(Optional)

Specifies whether the port mode is access or trunk. By default, the mode is set to trunk.

UCS-A

/eth-storage/fabric/port-channel # set

prio sys-class-name

(Optional)

Specifies the QoS class for the appliance port. By default, the priority is set to best-effort.

The sys-class-name argument can be one of the following class keywords:

• Fc—Use this priority for QoS policies that control vHBA traffic only.

• Platinum—Use this priority for QoS policies that control vNIC traffic only.

• Gold—Use this priority for QoS policies that control vNIC traffic only.

• Silver—Use this priority for QoS policies that control vNIC traffic only.

• Bronze—Use this priority for QoS policies that control vNIC traffic only.

• Best Effort—Do not use this priority. It is reserved for the Basic Ethernet traffic lane. If you assign this priority to a QoS policy and configure another system

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Unconfiguring an Appliance Port Channel

Step 9

Step 10

Command or Action Purpose

class as CoS 0, Cisco UCS Manager does not default to this system class. It defaults to the priority with

CoS 0 for that traffic.

UCS-A

/eth-storage/fabric/port-channel # set

speed {1gbps | 2gbps | 4gbps | 8gbps

| auto}

(Optional)

Specifies the speed for the port channel.

UCS-A

/eth-storage/fabric/port-channel #

commit-buffer

Commits the transaction to the system configuration.

The following example creates a port channel on port 13 of fabric A and commits the transaction:

UCS-A#

scope eth-storage

UCS-A /eth-storage #

scope fabric a

UCS-A /eth-storage/fabric #

create port-channel 13

UCS-A /eth-storage/fabric/port-channel* #

enable

UCS-A /eth-storage/fabric/port-channel* #

set name portchan13a

UCS-A /eth-storage/fabric/port-channel* #

set pingroupname pingroup1

UCS-A /eth-storage/fabric/port-channel* #

set portmode access

UCS-A /eth-storage/fabric/port-channel* #

set prio fc

UCS-A /eth-storage/fabric/port-channel* #

set speed 2gbps

UCS-A /eth-storage/fabric/port-channel* #

commit-buffer

UCS-A /eth-storage/fabric/port-channel #

Unconfiguring an Appliance Port Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope eth-storage

Purpose

Enters Ethernet storage mode.

UCS-A /eth-storage # scope fabric {a | b } Enters Ethernet storage fabric mode for the specified fabric.

UCS-A /eth-storage/fabric # delete

port-channel port-num

Deletes the port channel from the specified

Ethernet storage port.

UCS-A /eth-storage/fabric # commit-buffer Commits the transaction to the system configuration.

The following example unconfigures the port channel on port 13 of fabric A and commits the transaction:

UCS-A#

scope eth-storage

UCS-A /eth-storage #

scope fabric a

UCS-A /eth-storage/fabric #

delete port-channel 13

UCS-A /eth-storage/fabric* #

commit-buffer

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Enabling or Disabling an Appliance Port Channel

UCS-A /eth-storage/fabric #

Enabling or Disabling an Appliance Port Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

UCS-A# scope eth-storage

Purpose

Enters Ethernet storage mode.

UCS-A /eth-storage # scope fabric {a | b } Enters Ethernet storage mode for the specified fabric.

Enters Ethernet storage port channel mode.

UCS-A /eth-storage/fabric # scope

port-channel port-chan-name

UCS-A /eth-storage/fabric/port-channel #

{enable | disable }

UCS-A /eth-storage/fabric/port-channel #

commit-buffer

Enables or disables the administrative state of the port channel. The port channel is disabled by default.

Commits the transaction to the system configuration.

The following example enables port channel 13 on fabric A and commits the transaction:

UCS-A#

scope eth-storage

UCS-A /eth-storage #

scope fabric a

UCS-A /eth-storage/fabric #

scope port-channel 13

UCS-A /eth-storage/fabric/port-channel* #

enable

UCS-A /eth-storage/fabric/port-channel* #

commit-buffer

UCS-A /eth-storage/fabric/port-channel #

Adding a Member Port to an Appliance Port Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope eth-storage

Purpose

Enters Ethernet storage mode.

UCS-A /eth-storage # scope fabric {a | b

}

Enters Ethernet storage fabric mode for the specified fabric.

UCS-A /eth-storage/fabric # scope

port-channel port-num

UCS-A /eth-storage/fabric/port-channel #

create member-port slot-num port-num

Enters Ethernet storage fabric port channel mode for the specified port channel.

Creates the specified member port from the port channel and enters Ethernet storage fabric port channel member port mode.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Deleting a Member Port from an Appliance Port Channel

Step 5

Command or Action

UCS-A /eth-storage/fabric/port-channel #

commit-buffer

Purpose

Commits the transaction to the system configuration.

The following example adds the member port on slot 1, port 7 to the port channel on port 13 of fabric A and commits the transaction.

UCS-A#

scope eth-storage

UCS-A /eth-storage #

scope fabric a

UCS-A /eth-storage/fabric #

scope port-channel 13

UCS-A /eth-storage/fabric/port-channel #

create member-port 1 7

UCS-A /eth-storage/fabric/port-channel* #

commit-buffer

UCS-A /eth-storage/fabric/port-channel #

Deleting a Member Port from an Appliance Port Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

UCS-A# scope eth-storage

Purpose

Enters Ethernet storage mode.

UCS-A /eth-storage # scope fabric {a | b } Enters Ethernet storage fabric mode for the specified fabric.

UCS-A /eth-storage/fabric # scope

port-channel port-num

UCS-A /eth-storage/fabric/port-channel #

delete member-port slot-num port-num

UCS-A /eth-storage/fabric/port-channel #

commit-buffer

Enters Ethernet storage fabric port channel mode for the specified port channel.

Deletes the specified member port from the port channel.

Commits the transaction to the system configuration.

The following example deletes a member port from the port channel on port 13 of fabric A and commits the transaction:

UCS-A#

scope eth-storage

UCS-A /eth-storage #

scope fabric a

UCS-A /eth-storage/fabric #

scope port-channel 13

UCS-A /eth-storage/fabric/port-channel #

delete member-port 1 7

UCS-A /eth-storage/fabric/port-channel* #

commit-buffer

UCS-A /eth-storage/fabric/port-channel #

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Fibre Channel Port Channels

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 and

6300 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

Configuring 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.

Procedure

Step 1

Step 2

Step 3

Command or Action

UCS-A# scope fc-uplink

Purpose

Enters Fibre Channel uplink mode.

UCS-A /fc-uplink # scope fabric {a | b } Enters Fibre Channel uplink fabric mode for the specified fabric.

UCS-A /fc-uplink/fabric # create

port-channel port-num

Creates a port channel on the specified Fibre

Channel uplink port, and enters Fibre Channel uplink fabric port channel mode.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Unconfiguring a Fibre Channel Port Channel

Step 5

Step 6

Step 7

Step 4

Command or Action

UCS-A /fc-uplink/fabric/port-channel #

{enable | disable}

Purpose

(Optional)

Enables or disables the administrative state of the port channel. The port channel is disabled by default.

UCS-A /fc-uplink/fabric/port-channel # set

name port-chan-name

(Optional)

Specifies the name for the port channel.

UCS-A /fc-uplink/fabric/port-channel # set

speed {1gbps | 2gbps | 4gbps | 8gbps |

auto}

(Optional)

Specifies the speed for the port channel.

UCS-A /fc-uplink/fabric/port-channel #

commit-buffer

Commits the transaction to the system configuration.

The following example creates port channel 13 on fabric A, sets the name to portchan13a, enables the administrative state, sets the speed to 2 Gbps, and commits the transaction:

UCS-A#

scope fc-uplink

UCS-A /fc-uplink #

scope fabric a

UCS-A /fc-uplink/fabric #

create port-channel 13

UCS-A /fc-uplink/fabric/port-channel* #

enable

UCS-A /fc-uplink/fabric/port-channel* #

set name portchan13a

UCS-A /fc-uplink/fabric/port-channel* #

set speed 2gbps

UCS-A /fc-uplink/fabric/port-channel* #

commit-buffer

UCS-A /fc-uplink/fabric/port-channel #

Unconfiguring a Fibre Channel Port Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope fc-uplink

Purpose

Enters Fibre Channel uplink mode.

UCS-A /fc-uplink # scope fabric {a | b } Enters Fibre Channel uplink fabric mode for the specified fabric.

UCS-A /fc-uplink/fabric # delete

port-channel port-num

Deletes the port channel on the specified Fibre

Channel uplink port.

UCS-A /fc-uplink/fabric # commit-buffer Commits the transaction to the system configuration.

The following example unconfigures port channel 13 on fabric A and commits the transaction:

UCS-A#

scope fc-uplink

UCS-A /fc-uplink #

scope fabric a

UCS-A /fc-uplink/fabric #

delete port-channel 13

UCS-A /fc-uplink/fabric* #

commit-buffer

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Adding Channel Mode Active To The Upstream NPIV Fibre Channel Port Channel

UCS-A /fc-uplink/fabric #

Adding Channel Mode Active To The Upstream NPIV Fibre Channel Port

Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Command or Action

UCS-A# scope fc-uplink

Purpose

Enters Fibre Channel uplink mode.

UCS-A /fc-uplink # scope fabric {a | b } Enters Fibre Channel uplink fabric mode for the specified fabric.

UCS-A /fc-uplink/fabric # create

port-channel port-num

Creates a port channel on the specified Fibre

Channel uplink port, and enters Fibre Channel uplink fabric port channel mode.

UCS-A /fc-uplink/fabric/port-channel #

{enable | disable}

UCS-A /fc-uplink/fabric/port-channel #

commit-buffer

(Optional)

Enables or disables the administrative state of the port channel. The port channel is disabled by default.

UCS-A /fc-uplink/fabric/port-channel # set

name port-chan-name

(Optional)

Specifies the name for the port channel.

UCS-A /fc-uplink/fabric/port-channel #

scope port-chan-name

(Optional)

Specifies the name for the port channel.

UCS-A /fc-uplink/fabric/port-channel #

channel mode {active}

(Optional)

Configures the channel-mode active on the upstream NPIV switch.

Commits the transaction to the system configuration.

The following example enables channel mode to active:

UCS-A#

scope fc-uplink

UCS-A /fc-uplink #

scope fabric a

UCS-A /fc-uplink/fabric #

create port-channel 13

UCS-A /fc-uplink/fabric/port-channel* #

enable

UCS-A /fc-uplink/fabric/port-channel* #

set name portchan13a

UCS-A /fc-uplink/fabric/port-channel* #

channel mode active

UCS-A /fc-uplink/fabric/port-channel* #

commit-buffer

UCS-A /fc-uplink/fabric/port-channel #

exit

UCS-A /fc-uplink/fabric/ #

show port-channel database

portchan13a

Administrative channel mode is active

Operational channel mode is active

UCS-A /fc-uplink/fabric/ #

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Enabling or Disabling a Fibre Channel Port Channel

Enabling or Disabling a Fibre Channel Port Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope fc-uplink

Purpose

Enters Fibre Channel uplink mode.

UCS-A /fc-uplink # scope fabric {a | b } Enters Fibre Channel uplink mode for the specified fabric.

UCS-A /fc-uplink/fabric # scope

port-channel port-chan-name

UCS-A /fc-uplink/fabric/port-channel #

{enable | disable }

Enters Fibre Channel uplink port channel mode.

Enables or disables the administrative state of the port channel. The port channel is disabled by default.

The following example enables port channel 13 on fabric A and commits the transaction:

UCS-A#

scope fc-uplink

UCS-A /fc-uplink #

scope fabric a

UCS-A /fc-uplink/fabric #

scope port-channel 13

UCS-A /fc-uplink/fabric/port-channel* #

enable

UCS-A /fc-uplink/fabric/port-channel* #

commit-buffer

UCS-A /fc-uplink/fabric/port-channel #

Adding a Member Port to a Fibre Channel Port Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

UCS-A# scope fc-uplink

Purpose

Enters Fibre Channel uplink mode.

UCS-A /fc-uplink # scope fabric {a | b } Enters Fibre Channel uplink fabric mode for the specified fabric.

UCS-A /fc-uplink/fabric # scope

port-channel port-num

UCS-A /fc-uplink/fabric/port-channel #

create member-port slot-num port-num

UCS-A /fc-uplink/fabric/port-channel #

commit-buffer

Enters Fibre Channel uplink fabric port channel mode for the specified port channel.

Creates the specified member port from the port channel and enters Fibre Channel uplink fabric port channel member port mode.

Commits the transaction to the system configuration.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Deleting a Member Port from a Fibre Channel Port Channel

The following example adds the member port on slot 1, port 7 to port channel 13 on fabric A and commits the transaction.

UCS-A#

scope fc-uplink

UCS-A /fc-uplink #

scope fabric a

UCS-A /fc-uplink/fabric #

scope port-channel 13

UCS-A /fc-uplink/fabric #

create member-port 1 7

UCS-A /fc-uplink/fabric/port-channel* #

commit-buffer

UCS-A /fc-uplink/fabric/port-channel #

Deleting a Member Port from a Fibre Channel Port Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

UCS-A# scope fc-uplink

UCS-A /fc-uplink # scope fabric {a | b}

UCS-A /fc-uplink/fabric # scope

port-channel port-num

UCS-A /fc-uplink/fabric/port-channel #

delete member-port slot-num port-num

UCS-A /fc-uplink/fabric/port-channel #

commit-buffer

Purpose

Enters Fibre Channel uplink mode.

Enters Fibre Channel uplink fabric mode for the specified fabric.

Enters Fibre Channel uplink fabric port channel mode for the specified port channel.

Deletes the specified member port from the port channel.

Commits the transaction to the system configuration.

The following example deletes a member port from port channel 13 on fabric A and commits the transaction:

UCS-A#

scope fc-uplink

UCS-A /fc-uplink #

scope fabric a

UCS-A /fc-uplink/fabric #

scope port-channel 13

UCS-A /fc-uplink/fabric #

delete member-port 1 7

UCS-A /fc-uplink/fabric/port-channel* #

commit-buffer

UCS-A /fc-uplink/fabric/port-channel #

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.

100

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Configuring a FCoE Port Channel

Configuring a FCoE Port Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope fc-uplink

UCS-A /fc-uplink # scope fabric{a | b}

UCS-A /fc-uplink/fabric # create

fcoe-port-channel number

UCS-A /fc-uplink/fabric/fabricinterface #

commit-buffer

Purpose

Enters FC Uplink mode.

Enters FC - Uplink mode for the specific fabric.

Creates port channel for the specified FCoE uplink port.

Commits the transaction to the system configuration.

The following example creates an interface for FCoE uplink port 1 on slot 4 of fabric A and commits the transaction:

UCS-A#

scope fc-uplink

UCS-A /fc-uplink #

scope fabric a

UCS-A /fc-uplink/fabric #

create fcoe-port-channel 4

UCS-A /fc-uplink/fabric/fcoe-port-channel* #

commit-buffer

UCS-A /fc-uplink/fabric/fcoe-port-channel #

Adding a Member Port to a FCoE Uplink Port Channel

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope fc-uplink

Purpose

Enters Fibre Channel uplink mode.

UCS-A /fc-uplink # scope fabric {a |

b }

Enters Fibre Channel uplink fabric mode for the specified fabric.

UCS-A /fc-uplink/fabric # scope

fcoe-port-channel ID

UCS-A

/fc-uplink/fabric/fcoe-port-channel #

create member-port slot-num

port-num

Enters FCoE uplink port channel mode for the specified port channel.

Creates the specified member port from the port channel and enters FCoE uplink fabric port channel member port mode.

Note

If the FCoE uplink port channel is a unified uplink port channel, you will get the following message:

Warning: if this is a unified port channel then member will be added to the ethernet port channel of the same id as well.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

101

Configuring Ports and Port Channels

Unified Uplink Port Channel

Step 5

Command or Action

UCS-A

/fc-uplink/fabric/fcoe-port-channel #

commit-buffer

Purpose

Commits the transaction to the system configuration.

The following example adds the member port on slot 1, port 7 to FCoE port channel 13 on fabric A and commits the transaction.

UCS-A#

scope fc-uplink

UCS-A /fc-uplink #

scope fabric a

UCS-A /fc-uplink/fabric #

scope fcoe-port-channel 13

UCS-A /fc-uplink/fabric #

create member-port 1 7

UCS-A /fc-uplink/fabric/fcoe-port-channel* #

commit-buffer

UCS-A /fc-uplink/fabric/fcoe-port-channel #

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.

Configuring a Unified Uplink Port Channel

To configure a unified uplink port channel, you will convert an existing FCoE uplink port channel as a unified port channel.

102

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Event Detection and Action

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope eth-uplink

Purpose

Enters Ethernet uplink mode.

UCS-A /eth-uplink # scope fabric {a | b} Enters Ethernet uplink fabric mode for the specified fabric.

UCS-A /eth-uplink/fabric # create

port-channel ID

Creates a port channel for the specified

Ethernet uplink port.

UCS-A /eth-uplink/fabric/port-channel #

commit-buffer

Commits the transaction to the system configuration.

The following example creates a unified uplink port channel on an existing FCoE port channel:

UCS-A#

scope eth-uplink

UCS-A /eth-uplink #

scope fabric b

UCS-A /eth-uplink/fabric #

create port-channel 2

UCS-A /eth-uplink/fabric/port-channel* #

commit-buffer

UCS-A /eth-uplink/fabric #

Event Detection and Action

Cisco UCS Manager uses the statistics collection policy to monitor and trigger an alarm when there are faults in the network interface ports connected from the I/O module (IOM) to the fabric interconnect.

The error statistics for the network interface ports is called NiErrStats and consists of the following errors:

NiErrStats Error Name

frameTx

Description

Collects the TX_FRM_ERROR counter values.

tooLong tooShort

Crc inRange

Collects the RX_TOOLONG counter values.

Collects the sum of RX_UNDERSIZE and

RX_FRAGMENT counter values.

Collects the sum of RX_CRERR_NOT_STOMPED and RX_CRCERR_STOMPED counter values.

Collects the RX_INRANGEERR counter values.

Note

The network interface port statistics is collected only from active ports and the information is sent to Cisco

UCS Manager.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

103

Configuring Ports and Port Channels

Policy-Based Port Error Handling

Policy-Based Port Error Handling

If Cisco UCS Manager detects any errors on active NI ports, and if the error-disable feature is enabled, Cisco

UCS Manager automatically disables the respective FI port that is connected to the NI port that had errors.

When a FI 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 FI port is error-disabled and that the connected NI Port has errors.

• It eliminates the possibility that this port can cause other ports, which are connected to the same

Chassis/FEX, to fail. 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.

Creating Threshold Definition

Procedure

Command or Action

Step 1

UCS-A # scope eth-server

Step 2

UCS-A/eth-server # scope stats-threshold-policy default

Step 3

UCSA/eth-server/stats-threshold-policy # create class class-name

Step 4

Step 5

UCS-A/eth-server/stats-threshold-policy/class # create property

property-name

UCS-A/eth-server/stats-threshold-policy/class/property # set

normal-value value

Purpose

Enters Ethernet storage mode.

Enters statistics threshold policy mode.

Creates the specified statistics threshold policy class and enters the organization statistics threshold policy class mode. To see a list of the available class name keywords, enter the create

class ? command in organization threshold policy mode.

Creates the specified statistics threshold policy class property and enters the organization statistics threshold policy class property mode. To see a list of the available property name keywords, enter the

create property ? command in organization threshold policy class mode.

Specifies the normal value for the class property. The value format can vary depending on

104

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Creating Threshold Definition

Command or Action Purpose

the class property being configured. To see the required format, enter the set

normal-value ? command in organization statistics threshold policy class property mode.

Step 6

UCS-A/eth-server/stats-threshold-policy/class/property # create

threshold-value {above-normal | below-normal} {cleared | condition

| critical | info | major | minor | warning}

Creates the specified threshold value for the class property and enters the organization statistics threshold policy class property threshold value mode.

Step 7

UCS-A/eth-server/stats-threshold-policy/class/property/threshold-value

# set {deescalating | escalating} value

Specifies the deescalating and escalating class property threshold value. The value format can vary depending on the class property threshold value being configured. To see the required format, enter the set deescalating ? or set

escalating ? command in the organization statistics threshold policy class property threshold value mode.

Step 8

UCS-A/eth-server/stats-threshold-policy/class/property/threshold-value

# commit-buffer

Commits the transaction to the system configuration.

The following example shows how to create a threshold definition:

UCS-A #

scope eth-server

UCS-A /eth-server #

scope stats-threshold-policy default

UCS-A /eth-server/stats-threshold-policy #

create class ni-ether-error-stats

UCS-A /eth-server/stats-threshold-policy/class* #

create property crc-delta

UCS-A /eth-server/stats-threshold-policy/class/property* #

set normal-value 0

UCS-A /eth-server/stats-threshold-policy/class/property* #

create threshold-value above-normal major

UCS-A /eth-server/stats-threshold-policy/class/property/threshold-value* #

set escalating

UCS-A /eth-server/stats-threshold-policy/class/property/threshold-value* #

set deescalating

UCS-A /eth-server/stats-threshold-policy/class/property/threshold-value* #

commit-buffer

Cisco UCS Manager CLI Configuration Guide, Release 2.2

105

Configuring Ports and Port Channels

Configuring Error Disable on a Fabric Interconnect Port

Configuring Error Disable on a Fabric Interconnect Port

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

UCS-A # scope eth-server

UCS-A/eth-server # scope stats-threshold-policy

default

UCSA/eth-server/stats-threshold-policy # scope class

class-name

Purpose

Enters Ethernet storage mode.

Enters statistics threshold policy mode.

Enters the organization statistics threshold policy class mode for the specified statistics threshold policy class.

UCS-A/eth-server/stats-threshold-policy/class # scope

property property-name

Enters the organization statistics threshold policy class property mode for the specified statistics threshold policy class property.

UCS-A/eth-server/stats-threshold-policy/class/property

# set error-disable-fi-port {yes | no}

Specifies the error disable state for the class property.

Use the no option to disable error disable for the class property.

UCS-A/eth-server/stats-threshold-policy/class/property*

# commit-buffer

Commits the transaction to the system configuration.

The following example shows how to enable error disable on an FI port:

UCS-A #

scope eth-server

UCS-A /eth-server #

scope stats-threshold-policy default

UCS-A /eth-server/stats-threshold-policy #

scope class ni-ether-error-stats

UCS-A /eth-server/stats-threshold-policy/class #

scope property crc-delta

UCS-A /eth-server/stats-threshold-policy/class/property #

set error-disable-fi-port yes

UCS-A /eth-server/stats-threshold-policy/class/property* #

commit-buffer

Configuring Auto Recovery on a Fabric Interconnect Port

Procedure

Step 1

Step 2

Command or Action

UCS-A # scope eth-server

UCS-A/eth-server # scope stats-threshold-policy

default

Purpose

Enters Ethernet storage mode.

Enters statistics threshold policy mode.

106

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Viewing the Network Interface Port Error Counters

Step 3

Step 4

Step 5

Step 6

Step 7

Command or Action

UCSA/eth-server/stats-threshold-policy # scope class

class-name

Purpose

Enters the organization statistics threshold policy class mode for the specified statistics threshold policy class.

UCS-A/eth-server/stats-threshold-policy/class # scope

property property-name

Enters the organization statistics threshold policy class property mode for the specified statistics threshold policy class property.

UCS-A/eth-server/stats-threshold-policy/class/property

# set auto-recovery {enabled | disabled}

Specifies the auto recovery state for the class property.

Use the disabled option to disable auto recovery for the class property.

UCS-A/eth-server/stats-threshold-policy/class/property*

# set auto-recovery-time time

Specifies the time in minutes after which the port is automatically re-enabled. The auto recovery time can range from 0 minutes to 4294967295 minutes.

UCS-A/eth-server/stats-threshold-policy/class/property*

# commit-buffer

Commits the transaction to the system configuration.

The following example shows how to configure auto recovery on an FI port:

UCS-A #

scope eth-server

UCS-A /eth-server #

scope stats-threshold-policy default

UCS-A /eth-server/stats-threshold-policy #

scope class ni-ether-error-stats

UCS-A /eth-server/stats-threshold-policy/class #

scope property crc-delta

UCS-A /eth-server/stats-threshold-policy/class/property #

set auto-recovery enabled

UCS-A /eth-server/stats-threshold-policy/class/property* #

set auto-recovery-time 5

UCS-A /eth-server/stats-threshold-policy/class/property* #

commit-buffer

Viewing the Network Interface Port Error Counters

Procedure

Step 1

Step 2

Step 3

Command or Action

UCS-A # scope chassis chassis-num

UCS-A/chassis # scope iom {a | b}

UCS-A/chassis/iom # scope port-group

fabric

Purpose

Enters chassis mode for the specified chassis.

Enters chassis IOM mode for the specified

IOM.

Enters the network interface port.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

107

Configuring Ports and Port Channels

Adapter Port Channels

Step 4

Step 5

Command or Action

UCS-A/chassis/iom/port-group # scope

fabric-if fabric-if number

UCS-A/chassis/iom/port-group/fabric-if #

show stats

Purpose

Enters the specified network interface port number.

Displays the error counters for the network interface port.

The following example shows how to display the statistics for the network interface ports:

UCS-A #

scope chassis 1

UCS-A/chassis #

scope iom a

UCS-A/chassis/iom #

scope port-group fabric

UCS-A/chassis/iom/port-group #

scope faric-if 1

UCS-A/chassis/iom/port-group/fabric-if #

show stats

NI Ether Error Stats:

Time Collected: 2014-08-20T15:37:24:688

Monitored Object: sys/chassis-1/slot-1/fabric/port-1/ni-err-stats

Suspect: Yes

Crc (errors): 5000

Frame Tx (errors): 0

Too Long (errors): 0

Too Short (errors): 0

In Range (errors): 0

Thresholded: 0

Adapter Port Channels

An adapter port channel groups into one logical link all the physical links going from a Cisco UCS Virtual

Interface Card (VIC) into an I/O.

Adapter port channels are created and managed internally by Cisco UCS Manager when it detects that the correct hardware is present. Adapter port channels cannot be configured manually. Adapter port channels are viewable using the Cisco UCS Manager GUI or the Cisco UCS Manager CLI.

Viewing Adapter Port Channels

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope chassis chassis-num

UCS-A /chassis # scope iom {a b}

UCS-A /chassis/iom # scope port group

UCS-A /chassis/iom/port group # show

host-port-channel [detail | expand]

Purpose

Enters chassis mode for the specified chassis.

Enters chassis IOM mode for the specified

IOM.

Enters port group mode for the specified port group.

Displays the adapter port channels on the specified chassis.

108

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Fabric Port Channels

This following example shows how to display information on host port channels within a port group mode:

UCS-A #

scope chassis 1

UCS-A /chassis #

scope iom a

UCS-A /chassis/iom #

scope port group

UCS-A /chassis/iom/port group #

show host-port-channel

Host Port channel:

Port Channel Id Fabric ID Oper State State Reason

--------------- --------- ---------------- ------------

1289 B

1290 B

1306 B

1307 B

1309 B

1315 B

UCS-A /chassis/iom/port group #

Fabric Port Channels

Fabric port channels allow you to group several of the physical links from an IOM to a fabric interconnect into one logical link for redundancy and bandwidth sharing. As long as one link in the fabric port channel remains active, the fabric port channel continues to operate.

If the correct hardware is connected, fabric port channels are created by Cisco UCS Manager in the following ways:

• During chassis discovery according to the settings configured in the chassis discovery policy.

• After chassis discovery according to the settings configured in the chassis connectivity policy for a specific chassis.

For each IOM there is a single fabric port channel. Each uplink connecting an IOM to a fabric interconnect can be configured as a discrete link or included in the port channel, but an uplink cannot belong to more than one fabric port channel. For example, if a chassis with two IOMs is discovered and the chassis discovery policy is configured to create fabric port channels, Cisco UCS Manager creates two separate fabric port channels: one for the uplinks connecting IOM-1 and another for the uplinks connecting IOM-2. No other chassis can join these fabric port channels. Similarly, uplinks belonging to the fabric port channel for IOM-1 cannot join the fabric port channel for IOM-2.

Load Balancing Over Ports

Load balancing traffic among ports between IOMs and fabric interconnects uses the following criteria for hashing.

• For Ethernet traffic:

Layer 2 source and destination address

Layer 3 source and destination address

Layer 4 source and destination ports

• For FCoE traffic:

Cisco UCS Manager CLI Configuration Guide, Release 2.2

109

Configuring Ports and Port Channels

Cabling Considerations for Fabric Port Channels

Layer 2 source and destination address

Source and destination IDs (SID and DID) and Originator Exchange ID (OXID)

In this example, a 2200 Series IOM module is verified by connecting iom X (where X is the chassis number).

show platform software fwmctrl nifport

(....)

Hash Parameters: l2_da: 1 l2_sa: 1 l2_vlan: 0 l3_da: 1 l3_sa: 1 l4_da: 1 l4_sa: 1

FCoE l2_da: 1 l2_sa: 1 l2_vlan: 0

FCoE l3_did: 1 l3_sid: 1 l3_oxid: 1

Cabling Considerations for Fabric Port Channels

When you configure the links between the Cisco UCS 2200 Series FEX and a Cisco UCS 6200 series fabric interconnect in fabric port channel mode, the available virtual interface namespace (VIF) on the adapter varies depending on where the FEX uplinks are connected to the fabric interconnect ports.

Inside the 6248 fabric interconnect there are six sets of eight contiguous ports, with each set of ports managed by a single chip. When all uplinks from an FEX are connected to a set of ports managed by a single chip,

Cisco UCS Manager maximizes the number of VIFs used in service profiles deployed on the blades in the chassis. If uplink connections from an IOM are distributed across ports managed by separate chips, the VIF count is decreased.

Figure 1: Port Groups for Fabric Port Channels

Caution

Adding a second link to a fabric-port-channel port group is disruptive and will automatically increase the available amount of VIF namespace from 63 to 118. Adding further links is not disruptive and the VIF namespace stays at 118.

Caution

Linking a chassis to two fabric-port-channel port groups does not affect the VIF namespace unless it is manually acknowledged. The VIF namespace is then automatically set to the smaller size fabric port-channel port group usage (either 63 or 118 VIFs) of the two groups.

For high availability cluster-mode applications, we strongly recommend symmetric cabling configurations.

If the cabling is asymmetric, the maximum number of VIFs available is the smaller of the two cabling configurations.

For more information on the maximum number of VIFs for your Cisco UCS environment, see the Configuration

Limits document for your hardware and software configuration.

110

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Ports and Port Channels

Configuring a Fabric Port Channel

Configuring a Fabric Port Channel

Procedure

Step 1

To include all links from the IOM to the fabric interconnect in a fabric port channel during chassis discovery, set the link grouping preference in the chassis discovery policy to port channel.

Step 2

To include links from individual chassis in a fabric port channel during chassis discovery, set the link grouping preference in the chassis connectivity policy to port channel.

Step 3

After chassis discovery, enable or disable additional fabric port channel member ports.

What to Do Next

To add or remove chassis links from a fabric port channel after making a change to the chassis discovery policy or the chassis connectivity policy, reacknowledge the chassis. Chassis reacknowledgement is not required to enable or disable chassis member ports from a fabric port channel

Viewing Fabric Port Channels

Procedure

Step 1

Step 2

Step 3

Command or Action

UCS-A# scope eth-server

UCS-A /eth-server # scope fabric {a | b}

UCS-A /eth-server/fabric # show

fabric-port-channel [detail | expand]

Purpose

Enters Ethernet server mode.

Enters Ethernet server fabric mode for the specified fabric.

Displays fabric port channels on the specified fabric interconnect.

The following example displays information about configured fabric port channels on fabric interconnect A:

UCS-A#

scope eth-server

UCS-A /eth-server #

scope fabric a

UCS-A /eth-server/fabric #

show fabric-port-channel

Fabric Port Channel:

Port Channel Id Chassis Id Admin State Oper State State Reason

--------------- ---------- ----------- ---------------- ------------

1025 1

1026 2

Enabled

Failed

No operational members

UCS-A /eth-server/fabric #

Cisco UCS Manager CLI Configuration Guide, Release 2.2

111

Configuring Ports and Port Channels

Enabling or Disabling a Fabric Port Channel Member Port

Enabling or Disabling a Fabric Port Channel Member Port

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command or Action

UCS-A# scope eth-server

Purpose

Enters Ethernet server mode.

UCS-A /eth-server # scope fabric {a | b}

UCS-A /eth-server/fabric # scope

fabric-port-channel port-chan-id

Enters Ethernet server fabric mode for the specified fabric.

Enters Ethernet server fabric, fabric port channel mode for the specified fabric.

UCS-A /eth-server/fabric/fabric-port-channel

# scope member-port slot-id port-id

Enters Ethernet server fabric, fabric port channel mode for the specified member port.

UCS-A /eth-server/fabric/fabric-port-channel

# {enable | disable}

Enables or disables the specified member port.

UCS-A /eth-server/fabric/fabric-port-channel

# commit-buffer

Commits the transaction to the system configuration.

The following example disables fabric channel member port 1 31 on fabric port channel 1025 and commits the transaction:

UCS-A#

scope eth-server

UCS-A /eth-server #

scope fabric a

UCS-A /eth-server/fabric #

scope fabric-port-channel 1025

UCS-A /eth-server/fabric/fabric-port-channel #

scope member-port 1 31

UCS-A /eth-server/fabric/fabric-port-channel/member-port #

disable

UCS-A /eth-server/fabric/fabric-port-channel/member-port* #

commit-buffer

UCS-A /eth-server/fabric/fabric-port-channel/member-port #

112

Cisco UCS Manager CLI Configuration Guide, Release 2.2

C H A P T E R

Configuring Communication Services

This chapter includes the following sections:

•

Communication Services, page 114

•

Configuring CIM XML, page 115

•

Configuring HTTP, page 116

•

Unconfiguring HTTP, page 116

•

Configuring HTTPS, page 117

•

Enabling HTTP Redirection to HTTPS, page 126

•

SNMP Functional Overview, page 127

•

SNMP Notifications, page 128

•

SNMP Security Levels and Privileges, page 128

•

Supported Combinations of SNMP Security Models and Levels, page 128

•

SNMPv3 Security Features, page 129

•

SNMP Support in Cisco UCS , page 130

•

Enabling SNMP and Configuring SNMP Properties, page 130

•

Creating an SNMP Trap, page 131

•

Deleting an SNMP Trap, page 133

•

Creating an SNMPv3 User, page 133

•

Deleting an SNMPv3 User, page 134

•

Enabling Telnet, page 135

•

Enabling the CIMC Web Service, page 135

•

Disabling the CIMC Web Service, page 136

•

Disabling Communication Services, page 137

Cisco UCS Manager CLI Configuration Guide, Release 2.2

113

Configuring Communication Services

Communication Services

Communication Services

You can use the communication services defined below to interface third-party applications with Cisco UCS.

Cisco UCS Manager supports IPv4 and IPv6 address access for the following services:

• CIM XML

• HTTP

• HTTPS

• SNMP

• SSH

• Telnet

Cisco UCS Manager supports out-of-band IPv4 address access to the Cisco UCS KVM Direct launch page from a web browser. To provide this access, you must enable the following service:

• CIMC Web Service

Communication Service

CIM XML

Description

The Common Information Model (CIM) XML) service is disabled by default and is only available in read-only mode. The default port is 5988.

The CIM XML is a standards-based protocol for exchanging CIM information that the Distributed Management Task Force defines.

CIMC Web Service

HTTP

This service is disabled by default.

When this service is enabled, users can directly access a server CIMC using one of the out-of-band management IP addresses assigned directly to the server, or associated with the server through a service profile.

Note

CIMC Web Service can only be enabled or disabled globally. You cannot configure KVM direct access for individual CIMC IP addresses.

By default, HTTP is enabled on port 80.

You can run the Cisco UCS Manager GUI in an HTTP or HTTPS browser. If you select HTTP, all data is exchanged in clear text mode.

For a secure browser session, we recommend that you enable HTTPS and disable

HTTP.

By default, Cisco UCS implements a browser redirects to an HTTPS equivalent and recommends that you do not change this behavior.

Note

If you are upgrading to Cisco UCS, version 1.4(1), the browser redirect to a secure browser does not occur by default. To redirect the HTTP browser to an HTTPS equivalent, enable the Redirect HTTP to HTTPS in Cisco UCS Manager.

114

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Communication Services

Configuring CIM XML

Communication Service

HTTPS

Description

By default, HTTPS is enabled on port.

With HTTPS, all data is exchanged in encrypted mode through a secure server.

For a secure browser session, We recommend that you only use HTTPS and either disable or redirect HTTP communications.

SMASH CLP

SNMP

This service is enabled for read-only access and supports a limited subset of the protocols, such as the show command. You cannot disable it.

This shell service is one of the standards that the Distributed Management Task

Force defines.

By default, this service is disabled. If enabled, the default port is 161. You must configure the community and at least one SNMP trap.

Enable this service only if your system includes integration with an SNMP server.

SSH

Telnet

This service is enabled on port 22. You cannot disable it, and you cannot change the default port.

This service provides access to the Cisco UCS Manager CLI.

By default, this service is disabled.

This service provides access to the Cisco UCS Manager CLI.

Configuring CIM XML

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

UCS-A# scope system

UCS-A /system # scope services

Purpose

Enters system mode.

Enters system services mode.

UCS-A /system/services # enable cimxml Enables the CIM XLM service.

UCS-A /system/services # set cimxml port

port-num

Specifies the port for the CIM XML connection.

UCS-A /system/services # commit-buffer Commits the transaction to the system configuration.

The following example enables CIM XML, sets the port number to 5988, and commits the transaction:

UCS-A#

scope system

UCS-A /system #

scope services

UCS-A /system/services #

enable cimxml

Cisco UCS Manager CLI Configuration Guide, Release 2.2

115

Configuring Communication Services

Configuring HTTP

UCS-A /system/services* #

set cimxml port 5988

UCS-A /system/services* #

commit-buffer

UCS-A /system/services #

Configuring HTTP

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

UCS-A# scope system

UCS-A /system # scope services

Purpose

Enters system mode.

Enters system services mode.

UCS-A /system/services # enable http

UCS-A /system/services # set http port

port-num

Enables the HTTP service.

Specifies the port to be used for the HTTP connection.

UCS-A /system/services # commit-buffer Commits the transaction to the system configuration.

The following example enables HTTP, sets the port number to 80, and commits the transaction:

UCS-A#

scope system

UCS-A /system #

scope services

UCS-A /system/services #

enable http

UCS-A /system/services* #

set http port 80

Warning: When committed, this closes all the web sessions.

UCS-A /system/services* #

commit-buffer

UCS-A /system/services #

Unconfiguring HTTP

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope system

UCS-A /system # scope services

UCS-A /system/services # disable http

UCS-A /system/services # commit-buffer

Purpose

Enters system mode.

Enters system services mode.

Disables the HTTP service.

Commits the transaction to the system configuration.

The following example disables HTTP and commits the transaction:

UCS-A#

scope system

UCS-A /system #

scope services

116

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Communication Services

Configuring HTTPS

UCS-A /system/services #

disable http

UCS-A /system/services* #

commit-buffer

UCS-A /system/services #

Configuring HTTPS

Certificates, Key Rings, and Trusted Points

HTTPS uses components of the Public Key Infrastructure (PKI) to establish secure communications between two devices, such as a client's browser and Cisco UCS Manager.

Encryption Keys and Key Rings

Each PKI device holds a pair of asymmetric Rivest-Shamir-Adleman (RSA) encryption keys, one kept private and one made public, stored in an internal key ring. A message encrypted with either key can be decrypted with the other key. To send an encrypted message, the sender encrypts the message with the receiver's public key, and the receiver decrypts the message using its own private key. A sender can also prove its ownership of a public key by encrypting (also called 'signing') a known message with its own private key. If a receiver can successfully decrypt the message using the public key in question, the sender's possession of the corresponding private key is proven. Encryption keys can vary in length, with typical lengths from 512 bits to 2048 bits. In general, a longer key is more secure than a shorter key. Cisco UCS Manager provides a default key ring with an initial 1024-bit key pair, and allows you to create additional key rings.

The default key ring certificate must be manually regenerated if the cluster name changes or the certificate expires.

This operation is only available in the UCS Manager CLI.

Certificates

To prepare for secure communications, two devices first exchange their digital certificates. A certificate is a file containing a device's public key along with signed information about the device's identity. To merely support encrypted communications, a device can generate its own key pair and its own self-signed certificate.

When a remote user connects to a device that presents a self-signed certificate, the user has no easy method to verify the identity of the device, and the user's browser will initially display an authentication warning. By default, Cisco UCS Manager contains a built-in self-signed certificate containing the public key from the default key ring.

Trusted Points

To provide stronger authentication for Cisco UCS Manager, you can obtain and install a third-party certificate from a trusted source, or trusted point, that affirms the identity of your device. The third-party certificate is signed by the issuing trusted point, which can be a root certificate authority (CA) or an intermediate CA or trust anchor that is part of a trust chain that leads to a root CA. To obtain a new certificate, you must generate a certificate request through Cisco UCS Manager and submit the request to a trusted point.

Important

The certificate must be in Base64 encoded X.509 (CER) format.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

117

Configuring Communication Services

Creating a Key Ring

Creating a Key Ring

Cisco UCS Manager supports a maximum of 8 key rings, including the default key ring.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope security

Purpose

Enters security mode.

UCS-A /security # create keyring keyring-name Creates and names the key ring.

UCS-A /security/keyring # set modulus {mod1024

| mod1536 | mod2048 | mod512}

Sets the SSL key length in bits.

UCS-A /security/keyring # commit-buffer Commits the transaction.

The following example creates a keyring with a key size of 1024 bits:

UCS-A#

scope security

UCS-A /security #

create keyring kr220

UCS-A /security/keyring* #

set modulus mod1024

UCS-A /security/keyring* #

commit-buffer

UCS-A /security/keyring #

What to Do Next

Create a certificate request for this key ring.

Regenerating the Default Key Ring

The default key ring certificate must be manually regenerated if the cluster name changes or the certificate expires.

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope security

UCS-A /security # scope keyring default

Purpose

Enters security mode.

Enters key ring security mode for the default key ring.

UCS-A /security/keyring # set regenerate yes Regenerates the default key ring.

UCS-A /security/keyring # commit-buffer Commits the transaction.

The following example regenerates the default key ring:

UCS-A#

scope security

UCS-A /security #

scope keyring default

UCS-A /security/keyring* #

set regenerate yes

118

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Communication Services

Creating a Certificate Request for a Key Ring

UCS-A /security/keyring* #

commit-buffer

UCS-A /security/keyring #

Creating a Certificate Request for a Key Ring

Creating a Certificate Request for a Key Ring with Basic Options

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

UCS-A# scope security

Purpose

Enters security mode.

UCS-A /security # scope keyring

keyring-name

Enters configuration mode for the key ring.

UCS-A /security/keyring # create certreq

{ip [ipv4-addr | ipv6-v6] |subject-name

name}

Creates a certificate request using the IPv4 or IPv6 address specified, or the name of the fabric interconnect. You are prompted to enter a password for the certificate request.

UCS-A /security/keyring/certreq #

commit-buffer

Commits the transaction.

UCS-A /security/keyring # show certreq Displays the certificate request, which you can copy and send to a trust anchor or certificate authority.

The following example creates and displays a certificate request with an IPv4 address for a key ring, with basic options:

UCS-A#

scope security

UCS-A /security #

scope keyring kr220

UCS-A /security/keyring #

create certreq ip 192.168.200.123 subject-name sjc04

Certificate request password:

Confirm certificate request password:

UCS-A /security/keyring* #

commit-buffer

UCS-A /security/keyring #

show certreq

Certificate request subject name: sjc04

Certificate request ip address: 192.168.200.123

Certificate request e-mail name:

Certificate request country name:

State, province or county (full name):

Locality (eg, city):

Organization name (eg, company):

Organization Unit name (eg, section):

Request:

-----BEGIN CERTIFICATE REQUEST-----

MIIBfTCB5wIBADARMQ8wDQYDVQQDEwZzYW1jMDQwgZ8wDQYJKoZIhvcNAQEBBQAD gY0AMIGJAoGBALpKn1t8qMZO4UGqILKFXQQc2c8b/vW2rnRF8OPhKbhghLA1YZ1F

JqcYEG5Yl1+vgohLBTd45s0GC8m4RTLJWHo4SwccAUXQ5Zngf45YtX1WsylwUWV4

0re/zgTk/WCd56RfOBvWR2Dtztu2pGA14sd761zLxt29K7R8mzj6CAUVAgMBAAGg

LTArBgkqhkiG9w0BCQ4xHjAcMBoGA1UdEQEB/wQQMA6CBnNhbWMwNIcECsEiXjAN

BgkqhkiG9w0BAQQFAAOBgQCsxN0qUHYGFoQw56RwQueLTNPnrndqUwuZHUO03Teg nhsyu4satpyiPqVV9viKZ+spvc6x5PWIcTWgHhH8BimOb/0OKuG8kwfIGGsEDlAv

TTYvUP+BZ9OFiPbRIA718S+V8ndXr1HejiQGxlDNqoN+odCXPc5kjoXD0lZTL09H

BA==

-----END CERTIFICATE REQUEST-----

Cisco UCS Manager CLI Configuration Guide, Release 2.2

119

Configuring Communication Services

Creating a Certificate Request for a Key Ring

UCS-A /security/keyring #

Creating a Certificate Request for a Key Ring with Advanced Options

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

Step 11

Step 12

Step 13

Step 14

Command or Action

UCS-A# scope security

UCS-A /security # scope keyring

keyring-name

UCS-A /security/keyring # create certreq

Purpose

Enters security mode.

Enters configuration mode for the key ring.

UCS-A /security/keyring/certreq* # set

country country name

UCS-A /security/keyring/certreq* # set dns

DNS Name

Creates a certificate request.

Specifies the country code of the country in which the company resides.

Specifies the Domain Name Server (DNS) address associated with the request.

UCS-A /security/keyring/certreq* # set e-mail

E-mail name

Specifies the email address associated with the certificate request.

UCS-A /security/keyring/certreq* # set ip

{certificate request ip-address|certificate

request ip6-address }

Specifies the IP address of the Fabric

Interconnect.

UCS-A /security/keyring/certreq* # set locality

locality name (eg, city)

Specifies the city or town in which the company requesting the certificate is headquartered.

UCS-A /security/keyring/certreq* # set

org-name organization name

Specifies the organization requesting the certificate.

Specifies the organizational unit.

UCS-A /security/keyring/certreq* # set

org-unit-name organizational unit name

UCS-A /security/keyring/certreq* # set

password certificate request password

Specifies an optional password for the certificate request.

UCS-A /security/keyring/certreq* # set state

state, province or county

Specifies the state or province in which the company requesting the certificate is headquartered.

UCS-A /security/keyring/certreq* # set

subject-name certificate request name

UCS-A /security/keyring/certreq* #

commit-buffer

Specifies the fully qualified domain name of the Fabric Interconnect.

Commits the transaction.

120

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Communication Services

Creating a Certificate Request for a Key Ring

Step 15

Command or Action

UCS-A /security/keyring # show certreq

Purpose

Displays the certificate request, which you can copy and send to a trust anchor or certificate authority.

The following example creates and displays a certificate request with an IPv4 address for a key ring, with advanced options:

UCS-A#

scope security

UCS-A /security #

scope keyring kr220

UCS-A /security/keyring #

create certreq

UCS-A /security/keyring/certreq* #

set ip 192.168.200.123

UCS-A /security/keyring/certreq* #

set subject-name sjc04

UCS-A /security/keyring/certreq* #

set country US

UCS-A /security/keyring/certreq* #

set dns bg1-samc-15A

UCS-A /security/keyring/certreq* #

set email [email protected]

UCS-A /security/keyring/certreq* #

set locality new york city

UCS-A /security/keyring/certreq* #

set org-name "Cisco Systems"

UCS-A /security/keyring/certreq* #

set org-unit-name Testing

UCS-A /security/keyring/certreq* #

set state new york

UCS-A /security/keyring/certreq* #

commit-buffer

UCS-A /security/keyring/certreq #

show certreq

Certificate request subject name: sjc04

Certificate request ip address: 192.168.200.123

Certificate request e-mail name: [email protected]

Certificate request country name: US

State, province or county (full name): New York

Locality name (eg, city): new york city

Organization name (eg, company): Cisco

Organization Unit name (eg, section): Testing

Request:

-----BEGIN CERTIFICATE REQUEST-----

MIIBfTCB5wIBADARMQ8wDQYDVQQDEwZzYW1jMDQwgZ8wDQYJKoZIhvcNAQEBBQAD gY0AMIGJAoGBALpKn1t8qMZO4UGqILKFXQQc2c8b/vW2rnRF8OPhKbhghLA1YZ1F

JqcYEG5Yl1+vgohLBTd45s0GC8m4RTLJWHo4SwccAUXQ5Zngf45YtX1WsylwUWV4

0re/zgTk/WCd56RfOBvWR2Dtztu2pGA14sd761zLxt29K7R8mzj6CAUVAgMBAAGg

LTArBgkqhkiG9w0BCQ4xHjAcMBoGA1UdEQEB/wQQMA6CBnNhbWMwNIcECsEiXjAN

BgkqhkiG9w0BAQQFAAOBgQCsxN0qUHYGFoQw56RwQueLTNPnrndqUwuZHUO03Teg nhsyu4satpyiPqVV9viKZ+spvc6x5PWIcTWgHhH8BimOb/0OKuG8kwfIGGsEDlAv

TTYvUP+BZ9OFiPbRIA718S+V8ndXr1HejiQGxlDNqoN+odCXPc5kjoXD0lZTL09H

BA==

-----END CERTIFICATE REQUEST-----

UCS-A /security/keyring/certreq #

What to Do Next

• Copy the text of the certificate request, including the BEGIN and END lines, and save it in a file. Send the file with the certificate request to a trust anchor or certificate authority to obtain a certificate for the key ring.

• Create a trusted point and set the certificate chain for the certificate of trust received from the trust anchor.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

121

Configuring Communication Services

Creating a Trusted Point

Creating a Trusted Point

Procedure

Step 1

Step 2

Step 3

Step 4

Command or Action

UCS-A# scope security

Purpose

Enters security mode.

UCS-A /security # create trustpoint

name

Creates and names a trusted point.

UCS-A /security/trustpoint # set

certchain [ certchain ]

Specifies certificate information for this trusted point.

If you do not specify certificate information in the command, you are prompted to enter a certificate or a list of trustpoints defining a certification path to the root certificate authority (CA). On the next line following your input, type ENDOFBUF to finish.

UCS-A /security/trustpoint #

commit-buffer

Important

The certificate must be in Base64 encoded

X.509 (CER) format.

Commits the transaction.

The following example creates a trusted point and provides a certificate for the trusted point:

UCS-A#

scope security

UCS-A /security #

create trustpoint tPoint10

UCS-A /security/trustpoint* #

set certchain

Enter lines one at a time. Enter ENDOFBUF to finish. Press ^C to abort.

Trustpoint Certificate Chain:

-----BEGIN CERTIFICATE-----

MIIDMDCCApmgAwIBAgIBADANBgkqhkiG9w0BAQQFADB0MQswCQYDVQQGEwJVUzEL

BxMMU2FuIEpvc2UsIENBMRUwEwYDVQQKEwxFeGFtcGxlIEluYy4xEzARBgNVBAsT

ClRlc3QgR3JvdXAxGTAXBgNVBAMTEHRlc3QuZXhhbXBsZS5jb20xHzAdBgkqhkiG

9w0BCQEWEHVzZXJAZXhhbXBsZS5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJ

AoGBAMZw4nTepNIDhVzb0j7Z2Je4xAG56zmSHRMQeOGHemdh66u2/XAoLx7YCcYU

ZgAMivyCsKgb/6CjQtsofvtrmC/eAehuK3/SINv7wd6Vv2pBt6ZpXgD4VBNKONDl

GMbkPayVlQjbG4MD2dx2+H8EH3LMtdZrgKvPxPTE+bF5wZVNAgMBAAGgJTAjBgkq

hkiG9w0BCQcxFhMUQSBjaGFsbGVuZ2UgcGFzc3dvcmQwDQYJKoZIhvcNAQEFBQAD

gYEAG61CaJoJaVMhzCl903O6Mg51zq1zXcz75+VFj2I6rH9asckCld3mkOVx5gJU

Ptt5CVQpNgNLdvbDPSsXretysOhqHmp9+CLv8FDuy1CDYfuaLtvlWvfhevskV0j6

jtcEMyZ+f7+3yh421ido3nO4MIGeBgNVHSMEgZYwgZOAFLlNjtcEMyZ+f7+3yh42

1ido3nO4oXikdjB0MQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0ExFDASBgNVBAcT

C1NhbnRhIENsYXJhMRswGQYDVQQKExJOdW92YSBTeXN0ZW1zIEluYy4xFDASBgNV

BAsTC0VuZ2luZWVyaW5nMQ8wDQYDVQQDEwZ0ZXN0Q0GCAQAwDAYDVR0TBAUwAwEB

/zANBgkqhkiG9w0BAQQFAAOBgQAhWaRwXNR6B4g6Lsnr+fptHv+WVhB5fKqGQqXc

wR4pYiO4z42/j9Ijenh75tCKMhW51az8copP1EBmOcyuhf5C6vasrenn1ddkkYt4

PR0vxGc40whuiozBolesmsmjBbedUCwQgdFDWhDIZJwK5+N3x/kfa2EHU6id1avt

4YL5Jg==

-----END CERTIFICATE-----

ENDOFBUF

UCS-A /security/trustpoint* #

commit-buffer

UCS-A /security/trustpoint #

What to Do Next

Obtain a key ring certificate from the trust anchor or certificate authority and import it into the key ring.

122

Cisco UCS Manager CLI Configuration Guide, Release 2.2

Configuring Communication Services

Importing a Certificate into a Key Ring

Importing a Certificate into a Key Ring

Before You Begin

• Configure a trusted point that contains the certificate chain for the key ring certificate.

• Obtain a key ring certificate from a trust anchor or certificate authority.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Command or Action

UCS-A# scope security

Purpose

Enters security mode.

UCS-A /security # scope keyring

keyring-name

Enters configuration mode for the key ring that will receive the certificate.

UCS-A /security/keyring # set

trustpoint name

Specifies the trusted point for the trust anchor or certificate authority from which the key ring certificate was obtained.

UCS-A /security/keyring # set cert Launches a dialog for entering and uploading the key ring certificate.

At the prompt, paste the certificate text that you received from the trust anchor or certificate authority. On the next line following the certificate, type ENDOFBUF to complete the certificate input.

UCS-A /security/keyring #

commit-buffer

Important

The certificate must be in Base64 encoded

X.509 (CER) format.

Commits the transaction.

The following example specifies the trust point and imports a certificate into a key ring:

UCS-A#

scope security

UCS-A /security #

scope keyring kr220

UCS-A /security/keyring #

set trustpoint tPoint10

UCS-A /security/keyring* #

set cert

Enter lines one at a time. Enter ENDOFBUF to finish. Press ^C to abort.

Keyring certificate:

-----BEGIN CERTIFICATE-----

MIIB/zCCAWgCAQAwgZkxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTEVMBMGA1UE