Cisco UCS Manager CLI Configuration Guide, Release 2 · Cisco UCS Manager CLI Configuration Guide, Release 2.2 First Published: 2013-12-11 Last Modified: 2016-07-27 Americas Headquarters

Cisco UCS Manager CLI Configuration Guide, Release 2.2First Published: 2013-12-11

Last Modified: 2016-07-27

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 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 LIMITEDWARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITHTHE 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 versionof the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.

NOTWITHSTANDINGANYOTHERWARRANTYHEREIN, 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 OFMERCHANTABILITY, FITNESS FORA PARTICULAR PURPOSEANDNONINFRINGEMENTORARISING FROMACOURSEOFDEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUTLIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERSHAVE 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, networktopology 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 unintentionaland 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 partnershiprelationship between Cisco and any other company. (1110R)

2013-2016 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarkshttp://www.cisco.com/go/trademarks

C O N T E N T S

P r e f a c e Preface xxxiii

Audience xxxiii

Conventions xxxiii

Related Cisco UCS Documentation xxxv

Documentation Feedback xxxv

C H A P T E R 1 Overview of Cisco Unified Computing System 1

About Cisco Unified Computing System 1

Unified Fabric 2

Fibre Channel over Ethernet 3

Link-Level Flow Control 3

Priority Flow Control 3

IPv6 Compliance 4

Server Architecture and Connectivity 5

Overview of Service Profiles 5

Network Connectivity through Service Profiles 6

Configuration through Service Profiles 6

Service Profiles that Override Server Identity 7

Service Profiles that Inherit Server Identity 8

Initial and Existing Templates 8

Policies 9

Pools 9

CIMC Inband Management 10

Inband Management Support 11

Traffic Management 11

Oversubscription 11

Oversubscription Considerations 11

Cisco UCS Manager CLI Configuration Guide, Release 2.2 iii

Guidelines for Estimating Oversubscription 12

Pinning 13

Guidelines for Pinning 13

Quality of Service 13

System Classes 14

Quality of Service Policy 15

Flow Control Policy 16

Opt-In Features 16

Stateless Computing 16

Multitenancy 17

Virtualization in Cisco UCS 18

Overview of Virtualization 18

Overview of Cisco Virtual Machine Fabric Extender 18

Virtualization with Network Interface Cards and Converged Network Adapters 19

Virtualization with a Virtual Interface Card Adapter 19

C H A P T E R 2 Overview of Cisco UCS Manager 21

About Cisco UCS Manager 21

Tasks You Can Perform in Cisco UCS Manager 22

Tasks You Cannot Perform in Cisco UCS Manager 24

Cisco UCS Manager in a High Availability Environment 24

C H A P T E R 3 Overview of Cisco UCS Manager CLI 25

Managed Objects 25

Command Modes 25

Object Commands 27

Complete a Command 28

Command History 28

Committing, Discarding, and Viewing Pending Commands 29

Online Help for the CLI 29

CLI Session Limits 29

Web Session Limits 29

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

Pre-Login Banner 30

Creating the Pre-Login Banner 30

Cisco UCS Manager CLI Configuration Guide, Release 2.2iv

Contents

Modifying the Pre-Login Banner 31

Deleting the Pre-Login Banner 32

C H A P T E R 4 Configuring the Fabric Interconnects 35

Initial System Setup 35

Setup Mode 36

System Configuration Type 36

Management Port IP Address 36

Performing an Initial System Setup for a Standalone Configuration 37

Initial System Setup for a Cluster Configuration 39

Performing an Initial System Setup for the First Fabric Interconnect 39

Performing an Initial System Setup for the Second Fabric Interconnect 42

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

Enabling a Standalone Fabric Interconnect for Cluster Configuration 44

Changing the System Name 45

Changing the Management Subnet of a Cluster 46

Changing the Management Prefix of a Cluster 47

Configuring the Information Policy on the Fabric Interconnect 48

Enabling the Information Policy on the Fabric Interconnect 48

Disabling the Information Policy on the Fabric Interconnect 49

Viewing the Information Policy on the Fabric Interconnect 49

Viewing the LAN Neighbors of the Fabric Interconnect 50

Viewing the SAN Neighbors of the Fabric Interconnect 50

Viewing the LLDP Neighbors of the Fabric Interconnect 51

Fabric Evacuation 51

Stopping Traffic on a Fabric Interconnect 52

Displaying the Status of Evacuation at a Fabric Interconnect 53

Displaying the Status of Evacuation at an IOM 53

Verifying Fabric Evacuation 54

Restarting Traffic on a Fabric Interconnect 56

Ethernet Switching Mode 56

Configuring Ethernet Switching Mode 57

Fibre Channel Switching Mode 58

Configuring Fibre Channel Switching Mode 59

Cisco UCS Manager CLI Configuration Guide, Release 2.2 v

Contents

C H A P T E R 5 Configuring Ports and Port Channels 61

Server and Uplink Ports on the 6100 Series Fabric Interconnect 61

Unified Ports on the Fabric Interconnect 63

Port Modes 63

Port Types 63

Beacon LEDs for Unified Ports 64

Guidelines for Configuring Unified Ports 64

Cautions and Guidelines for Configuring Unified Uplink Ports and Unified Storage

Ports 65

Effect of Port Mode Changes on Data Traffic 66

FC Links Rebalancing 67

Configuring the Port Mode 68

Configuring the Beacon LEDs for Unified Ports 70

Physical and Backplane Ports 71

Displaying Physical Port Statistics Obtained From the ASIC 71

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

BCM 72

Verifying Status of Backplane Ports 72

Server Ports 74

Configuring a Server Port 74

Unconfiguring a Server Port 75

Uplink Ethernet Ports 76

Configuring an Uplink Ethernet Port 76

Unconfiguring an Uplink Ethernet Port 76

Appliance Ports 77

Configuring an Appliance Port 77

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

Creating an Appliance Port 80

Mapping an Appliance Port to a Community VLAN 81

Unconfiguring an Appliance Port 81

FCoE Uplink Ports 82

Configuring a FCoE Uplink Port 82

Unconfiguring a FCoE Uplink Port 83

Viewing FCoE Uplink Ports 84

Cisco UCS Manager CLI Configuration Guide, Release 2.2vi

Contents

Unified Storage Ports 84

Configuring a Unified Storage Port 85

Unified Uplink Ports 85

Configuring a Unified Uplink Port 86

FCoE and Fibre Channel Storage Ports 86

Configuring a Fibre Channel Storage or FCoE Port 86

Unconfiguring a Fibre Channel Storage or FCoE Port 87

Restoring a Fibre Channel Storage Port Back to an Uplink Fibre Channel Port 88

Uplink Ethernet Port Channels 88

Configuring an Uplink Ethernet Port Channel 89

Unconfiguring an Uplink Ethernet Port Channel 90

Adding a Member Port to an Uplink Ethernet Port Channel 90

Deleting a Member Port from an Uplink Ethernet Port Channel 91

Appliance Port Channels 91

Configuring an Appliance Port Channel 92

Unconfiguring an Appliance Port Channel 93

Enabling or Disabling an Appliance Port Channel 94

Adding a Member Port to an Appliance Port Channel 94

Deleting a Member Port from an Appliance Port Channel 95

Fibre Channel Port Channels 96

Configuring a Fibre Channel Port Channel 96

Unconfiguring a Fibre Channel Port Channel 97

Adding Channel Mode Active To The Upstream NPIV Fibre Channel Port Channel 98

Enabling or Disabling a Fibre Channel Port Channel 99

Adding a Member Port to a Fibre Channel Port Channel 99

Deleting a Member Port from a Fibre Channel Port Channel 100

FCoE Port Channels 100

Configuring a FCoE Port Channel 101

Adding a Member Port to a FCoE Uplink Port Channel 101

Unified Uplink Port Channel 102

Configuring a Unified Uplink Port Channel 102

Event Detection and Action 103

Policy-Based Port Error Handling 104

Creating Threshold Definition 104

Configuring Error Disable on a Fabric Interconnect Port 106

Cisco UCS Manager CLI Configuration Guide, Release 2.2 vii

Contents

Configuring Auto Recovery on a Fabric Interconnect Port 106

Viewing the Network Interface Port Error Counters 107

Adapter Port Channels 108

Viewing Adapter Port Channels 108

Fabric Port Channels 109

Load Balancing Over Ports 109

Cabling Considerations for Fabric Port Channels 110

Configuring a Fabric Port Channel 111

Viewing Fabric Port Channels 111

Enabling or Disabling a Fabric Port Channel Member Port 112

C H A P T E R 6 Configuring Communication Services 113

Communication Services 113

Configuring CIM XML 115

Configuring HTTP 115

Unconfiguring HTTP 116

Configuring HTTPS 116

Certificates, Key Rings, and Trusted Points 116

Creating a Key Ring 117

Regenerating the Default Key Ring 118

Creating a Certificate Request for a Key Ring 119

Creating a Certificate Request for a Key Ring with Basic Options 119

Creating a Certificate Request for a Key Ring with Advanced Options 120

Creating a Trusted Point 121

Importing a Certificate into a Key Ring 122

Configuring HTTPS 124

Deleting a Key Ring 125

Deleting a Trusted Point 125

Unconfiguring HTTPS 126

Enabling HTTP Redirection to HTTPS 126

Enabling SNMP 127

SNMP Overview 127

SNMP Functional Overview 127

SNMP Notifications 128

SNMP Security Levels and Privileges 128

Cisco UCS Manager CLI Configuration Guide, Release 2.2viii

Contents

Supported Combinations of SNMP Security Models and Levels 129

SNMPv3 Security Features 130

SNMP Support in Cisco UCS 130

Enabling SNMP and Configuring SNMP Properties 130

Creating an SNMP Trap 131

Deleting an SNMP Trap 133

Creating an SNMPv3 User 133

Deleting an SNMPv3 User 134

Enabling Telnet 135

Enabling the CIMC Web Service 135

Disabling the CIMC Web Service 136

Disabling Communication Services 137

C H A P T E R 7 Configuring Authentication 139

Authentication Services 139

Guidelines and Recommendations for Remote Authentication Providers 140

User Attributes in Remote Authentication Providers 140

Two-Factor Authentication 142

LDAP Group Rule 143

Nested LDAP Groups 143

Configuring LDAP Providers 143

Configuring Properties for LDAP Providers 143

Creating an LDAP Provider 144

Changing the LDAP Group Rule for an LDAP Provider 149

Deleting an LDAP Provider 150

LDAP Group Mapping 150

Creating an LDAP Group Map 151

Deleting an LDAP Group Map 152

Configuring RADIUS Providers 153

Configuring Properties for RADIUS Providers 153

Creating a RADIUS Provider 153

Deleting a RADIUS Provider 155

Configuring TACACS+ Providers 156

Configuring Properties for TACACS+ Providers 156

Creating a TACACS+ Provider 156

Cisco UCS Manager CLI Configuration Guide, Release 2.2 ix

Contents

Deleting a TACACS+ Provider 158

Configuring Multiple Authentication Systems 158

Multiple Authentication Services 158

Configuring Multiple Authentication Systems 159

Provider Groups 159

Creating an LDAP Provider Group 160

Deleting an LDAP Provider Group 161

Creating a RADIUS Provider Group 161

Deleting a RADIUS Provider Group 162

Creating a TACACS Provider Group 163

Deleting a TACACS Provider Group 164

Authentication Domains 164

Creating an Authentication Domain 165

Selecting a Primary Authentication Service 166

Selecting the Console Authentication Service 166

Selecting the Default Authentication Service 168

Role Policy for Remote Users 169

Configuring the Role Policy for Remote Users 170

C H A P T E R 8 Configuring Organizations 171

Organizations in a Multitenancy Environment 171

Hierarchical Name Resolution in a Multi-Tenancy Environment 172

Configuring an Organization Under the Root Organization 174

Configuring an Organization Under an Organization that is not Root 174

Deleting an Organization 175

C H A P T E R 9 Configuring Role-Based Access Control 177

Role-Based Access Control Overview 177

User Accounts for Cisco UCS 177

Guidelines for Cisco UCS Usernames 178

Reserved Words: Locally Authenticated User Accounts 179

Guidelines for Cisco UCS Passwords 180

Web Session Limits for User Accounts 180

User Roles 181

Default User Roles 181

Cisco UCS Manager CLI Configuration Guide, Release 2.2x

Contents

Reserved Words: User Roles 182

Privileges 182

User Locales 185

Configuring User Roles 185

Creating a User Role 185

Adding Privileges to a User Role 186

Replacing Privileges for a User Role 187

Removing Privileges from a User Role 187

Deleting a User Role 188

Configuring Locales 188

Creating a Locale 188

Assigning an Organization to a Locale 189

Deleting an Organization from a Locale 189

Deleting a Locale 190

Configuring Locally Authenticated User Accounts 190

Creating a User Account 190

Enabling the Password Strength Check for Locally Authenticated Users 192

Setting Web Session Limits for User Accounts 193

Assigning a Role to a User Account 194

Assigning a Locale to a User Account 194

Removing a Role from a User Account 195

Removing a Locale from a User Account 196

Enabling or Disabling a User Account 196

Clearing the Password History for a Locally Authenticated User 197

Deleting a User Account 197

Password Profile for Locally Authenticated Users 198

Configuring the Maximum Number of Password Changes for a Change Interval 199

Configuring a No Change Interval for Passwords 200

Configuring the Password History Count 200

Monitoring User Sessions from the CLI 201

C H A P T E R 1 0 Configuring DNS Servers 203

DNS Servers in Cisco UCS 203

Configuring a DNS Server 203

Deleting a DNS Server 204

Cisco UCS Manager CLI Configuration Guide, Release 2.2 xi

Contents

C H A P T E R 1 1 Configuring System-Related Policies 205

Configuring the Chassis/FEX Discovery Policy 205

Chassis/FEX Discovery Policy 205

Configuring the Chassis/FEX Discovery Policy 208

Configuring the Chassis Connectivity Policy 210

Chassis Connectivity Policy 210

Configuring a Chassis Connectivity Policy 210

Configuring the Rack Server Discovery Policy 211

Rack Server Discovery Policy 211

Configuring the Rack Server Discovery Policy 211

Configuring the Aging Time for the MAC Address Table 212

Aging Time for the MAC Address Table 212

Configuring the Aging Time for the MAC Address Table 213

C H A P T E R 1 2 Managing Licenses 215

Licenses 215

C-Direct Rack Licensing Support 217

Obtaining the Host ID for a Fabric Interconnect 218

Obtaining a License 219

Installing a License 219

Viewing the Licenses Installed on a Fabric Interconnect 220

Viewing License Usage for a Fabric Interconnect 221

Uninstalling a License 223

C H A P T E R 1 3 Managing Virtual Interfaces 225

Virtual Interfaces 225

Virtual Interface Subscription Management and Error Handling 225

C H A P T E R 1 4 Registering Cisco UCS Domains with Cisco UCS Central 227

Registration of Cisco UCS Domains 227

Policy Resolution between Cisco UCS Manager and Cisco UCS Central 228

Registering a Cisco UCS Domain with Cisco UCS Central 229

Configuring Policy Resolution between Cisco UCS Manager and Cisco UCS Central 230

Setting Cisco UCS Central Registration Properties in Cisco UCS Manager 232

Cisco UCS Manager CLI Configuration Guide, Release 2.2xii

Contents

Unregistering a Cisco UCS Domain from Cisco UCS Central 233

C H A P T E R 1 5 VLANs 235

Named VLANs 235

Private VLANs 236

VLAN Port Limitations 237

Configuring Named VLANs 239

Creating a Named VLAN Accessible to Both Fabric Interconnects (Uplink Ethernet Mode) 239

Creating a Named VLAN Accessible to Both Fabric Interconnects (Ethernet Storage

Mode) 240

Creating a Named VLAN Accessible to One Fabric Interconnect (Uplink Ethernet Mode) 241

Creating a Named VLAN Accessible to One Fabric Interconnect (Ethernet Storage Mode) 242

Deleting a Named VLAN 243

Configuring Private VLANs 244

Creating a Primary VLAN for a Private VLAN (Accessible to Both Fabric Interconnects) 244

Creating a Primary VLAN for a Private VLAN (Accessible to One Fabric Interconnect) 245

Creating a Secondary VLAN for a Private VLAN (Accessible to Both Fabric

Interconnects) 246

Creating a Secondary VLAN for a Private VLAN (Accessible to One Fabric Interconnect) 247

Community VLANs 248

Creating a Community VLAN 248

Allowing Community VLANs on vNICs 248

Allowing PVLAN on Promiscuous Access or Trunk Port 249

Deleting a Community VLAN 250

Viewing the VLAN Port Count 251

VLAN Port Count Optimization 251

Enabling Port VLAN Count Optimization 252

Disabling Port VLAN Count Optimization 252

Viewing the Port VLAN Count Optimization Groups 253

VLAN Groups 253

Creating a VLAN Group 254

Creating an Inband VLAN Group 254

Deleting a VLAN Group 255

Viewing VLAN Groups 256

VLAN Permissions 256

Cisco UCS Manager CLI Configuration Guide, Release 2.2 xiii

Contents

Creating VLAN Permissions 257

Deleting a VLAN Permission 257

Viewing VLAN Permissions 258

C H A P T E R 1 6 Configuring LAN Pin Groups 259

LAN Pin Groups 259

Configuring a LAN Pin Group 259

C H A P T E R 1 7 Configuring MAC Pools 261

MAC Pools 261

Creating a MAC Pool 261

Deleting a MAC Pool 263

C H A P T E R 1 8 Configuring Quality of Service 265

Quality of Service 265

Configuring System Classes 266

System Classes 266

Configuring a System Class 267

Disabling a System Class 269

Configuring Quality of Service Policies 269

Quality of Service Policy 269

Configuring a QoS Policy 270

Deleting a QoS Policy 271

Configuring Flow Control Policies 272

Flow Control Policy 272

Configuring a Flow Control Policy 272

Deleting a Flow Control Policy 274

C H A P T E R 1 9 Configuring Network-Related Policies 275

Configuring vNIC Templates 275

vNIC Template 275

Configuring a vNIC Template 276

Redundancy Template Pairs 278

Creating vNIC Template Pairs 278

Undo vNIC Template Pairs 280

Cisco UCS Manager CLI Configuration Guide, Release 2.2xiv

Contents

Deleting a vNIC Template 281

Configuring Ethernet Adapter Policies 281

Ethernet and Fibre Channel Adapter Policies 281

Accelerated Receive Flow Steering 283

Guidelines and Limitations for Accelerated Receive Flow Steering 283

Interrupt Coalescing 284

Adaptive Interrupt Coalescing 284

Guidelines and Limitations for Adaptive Interrupt Coalescing 284

RDMA Over Converged Ethernet for SMB Direct 285

Guidelines and Limitations for SMB Direct with RoCE 285

Configuring an Ethernet Adapter Policy 285

Configuring an Ethernet Adapter Policy to Enable eNIC Support forMRQS on LinuxOperating

Systems 288

Configuring an Ethernet Adapter Policy to Enable Stateless Offloads with NVGRE 289

Configuring an Ethernet Adapter Policy to Enable Stateless Offloads with VXLAN 290

Deleting an Ethernet Adapter Policy 291

Configuring the Default vNIC Behavior Policy 292

Default vNIC Behavior Policy 292

Configuring a Default vNIC Behavior Policy 292

Configuring LAN Connectivity Policies 293

About the LAN and SAN Connectivity Policies 293

Privileges Required for LAN and SAN Connectivity Policies 293

Interactions between Service Profiles and Connectivity Policies 294

Creating a LAN Connectivity Policy 294

Creating a vNIC for a LAN Connectivity Policy 295

Deleting a vNIC from a LAN Connectivity Policy 297

Creating an iSCSI vNIC for a LAN Connectivity Policy 298

Deleting an iSCSI vNIC from a LAN Connectivity Policy 300

Deleting a LAN Connectivity Policy 300

Configuring Network Control Policies 301

Network Control Policy 301

Configuring Link Layer Discovery Protocol for Fabric Interconnect vEthernet

Interfaces 302

Configuring a Network Control Policy 302

Displaying Network Control Policy Details 304

Cisco UCS Manager CLI Configuration Guide, Release 2.2 xv

Contents

Deleting a Network Control Policy 305

Configuring Multicast Policies 305

Multicast Policy 305

Creating a Multicast Policy 306

Configuring IGMP Snooping Parameters 306

Modifying Multicast Policy Parameters 307

Assigning a VLAN Multicast Policy 308

Deleting a Multicast Policy 309

Configuring LACP Policies 309

LACP Policy 309

Creating a LACP Policy 310

Editing a LACP Policy 310

Assigning LACP Policy to Port-Channels 311

Configuring UDLD Link Policies 311

Understanding UDLD 311

UDLD Configuration Guidelines 313

Configuring a Link Profile 313

Configuring a UDLD Link Policy 314

Modifying the UDLD System Settings 315

Assigning a Link Profile to a Port Channel Ethernet Interface 316

Assigning a Link Profile to a Port Channel FCoE Interface 316

Assigning a Link Profile to an Uplink Ethernet Interface 317

Assigning a Link Profile to an Uplink FCoE Interface 318

Configuring VMQ Connection Policies 318

VMQ Connection Policy 318

Creating a VMQ Connection Policy 319

NetQueue 319

Information About NetQueue 319

Configuring NetQueue 320

C H A P T E R 2 0 Configuring Upstream Disjoint Layer-2 Networks 321

Upstream Disjoint Layer-2 Networks 321

Guidelines for Configuring Upstream Disjoint L2 Networks 322

Pinning Considerations for Upstream Disjoint L2 Networks 323

Configuring Cisco UCS for Upstream Disjoint L2 Networks 325

Cisco UCS Manager CLI Configuration Guide, Release 2.2xvi

Contents

Assigning Ports and Port Channels to VLANs 326

Removing Ports and Port Channels from VLANs 327

Viewing Ports and Port Channels Assigned to VLANs 327

C H A P T E R 2 1 Configuring Named VSANs 329

Named VSANs 329

Fibre Channel Uplink Trunking for Named VSANs 330

Guidelines and Recommendations for VSANs 330

Creating a Named VSAN Accessible to Both Fabric Interconnects (Fibre Channel Uplink

Mode) 332

Creating a Named VSAN Accessible to Both Fabric Interconnects (Fibre Channel Storage

Mode) 333

Creating a Named VSAN Accessible to One Fabric Interconnect (Fibre Channel Uplink

Mode) 334

Creating a Named VSAN Accessible to One Fabric Interconnect (Fibre Channel Storage

Mode) 335

Deleting a Named VSAN 336

Changing the VLAN ID for the FCoE Native VLAN for a Named VSAN 337

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

Enabling or Disabling Fibre Channel Uplink Trunking 338

C H A P T E R 2 2 Configuring SAN Pin Groups 341

SAN Pin Groups 341

Configuring a SAN Pin Group 342

Configuring a FCoE Pin Group 342

C H A P T E R 2 3 Configuring WWN Pools 345

WWN Pools 345

Creating a WWN Pool 346

Deleting a WWN Pool 348

C H A P T E R 2 4 Configuring Storage-Related Policies 351

Configuring vHBA Templates 351

vHBA Template 351

Configuring a vHBA Template 351

Cisco UCS Manager CLI Configuration Guide, Release 2.2 xvii

Contents

Redundancy Template Pairs 353

Creating vHBA Template Pairs 353

Undo vHBA Template Pairs 355

Deleting a vHBA Template 356

Configuring Fibre Channel Adapter Policies 356

Ethernet and Fibre Channel Adapter Policies 356

Configuring a Fibre Channel Adapter Policy 358

Deleting a Fibre Channel Adapter Policy 359

Configuring the Default vHBA Behavior Policy 360

Default vHBA Behavior Policy 360

Configuring a Default vHBA Behavior Policy 360

Configuring SAN Connectivity Policies 361

About the LAN and SAN Connectivity Policies 361

Privileges Required for LAN and SAN Connectivity Policies 361

Interactions between Service Profiles and Connectivity Policies 362

Creating a SAN Connectivity Policy 362

Creating a vHBA for a SAN Connectivity Policy 363

Deleting a vHBA from a SAN Connectivity Policy 365

Creating an Initiator Group for a SAN Connectivity Policy 366

Deleting an Initiator Group from a SAN Connectivity Policy 369

Deleting a SAN Connectivity Policy 370

C H A P T E R 2 5 Configuring Fibre Channel Zoning 371

Information About Fibre Channel Zoning 371

Information About Zones 371

Information About Zone Sets 372

Support for Fibre Channel Zoning in Cisco UCS Manager 372

Cisco UCS Manager-Based Fibre Channel Zoning 372

vHBA Initiator Groups 373

Fibre Channel Storage Connection Policy 373

Fibre Channel Active Zone Set Configuration 373

Switch-Based Fibre Channel Zoning 374

Guidelines and recommendations for Cisco UCS Manager-Based Fibre Channel Zoning 374

Configuring Cisco UCS Manager Fibre Channel Zoning 374

Removing Unmanaged Zones from a VSAN Accessible to Both Fabric Interconnects 375

Cisco UCS Manager CLI Configuration Guide, Release 2.2xviii

Contents

Removing Unmanaged Zones from a VSAN Accessible to One Fabric Interconnect 376

Configuring Fibre Channel Storage Connection Policies 377

Creating a Fibre Channel Storage Connection Policy 377

Deleting a Fibre Channel Storage Connection Policy 378

C H A P T E R 2 6 Configuring Server-Related Pools 381

Server Pool Configuration 381

Server Pools 381

Creating a Server Pool 382

Deleting a Server Pool 382

UUID Suffix Pool Configuration 383

UUID Suffix Pools 383

Creating a UUID Suffix Pool 383

Deleting a UUID Suffix Pool 384

IP Pool Configuration 385

IP Pools 385

Creating an Inband IP Pool 385

Adding Blocks to an IP Pool 387

Deleting a Block from an IP Pool 388

Deleting an IP Pool 389

C H A P T E R 2 7 Setting the Management IP Address 391

Management IP Address 391

Configuring the Management IP Address on a Blade Server 392

Configuring a Blade Server to Use a Static IP Address 392

Configuring a Blade Server to Use a Static IPv6 Address 393

Configuring a Blade Server to Use the Management IP Pool 393

Configuring the Management IP Address on a Rack Server 394

Configuring a Rack Server to Use a Static IP Address 394

Configuring a Rack Server to Use a Static IPv6 Address 395

Configuring a Rack Server to Use the Management IP Pool 396

Setting the Management IP Address on a Service Profile or Service Profile Template 397

Configuring the Management IP Pool 398

Management IP Pools 398

Configuring IP Address Blocks for the Management IP Pool 398

Cisco UCS Manager CLI Configuration Guide, Release 2.2 xix

Contents

Deleting an IP Address Block from the Management IP Pool 400

C H A P T E R 2 8 Configuring Server-Related Policies 403

Configuring BIOS Settings 403

Server BIOS Settings 403

Main BIOS Settings 404

Processor BIOS Settings 406

Intel Directed I/O BIOS Settings 419

RAS Memory BIOS Settings 421

Serial Port BIOS Settings 423

USB BIOS Settings 424

PCI Configuration BIOS Settings 427

QPI BIOS Settings 429

LOM and PCIe Slots BIOS Settings 430

Graphics Configuration BIOS Settings 437

Boot Options BIOS Settings 438

Server Management BIOS Settings 439

BIOS Policy 444

Default BIOS Settings 445

Creating a BIOS Policy 445

Modifying BIOS Defaults 446

Viewing the Actual BIOS Settings for a Server 448

Configuring Trusted Platform Module 448

Trusted Platform Module 448

Intel Trusted Execution Technology 449

Trusted Platform 449

Enabling or Disabling TPM 449

Enabling or Disabling TXT 450

Consistent Device Naming 451

Guidelines and Limitations for Consistent Device Naming 452

Enabling Consistent Device Naming in a BIOS Policy 454

Associating a BIOS Policy with a Service Profile 454

Configuring Consistent Device Naming for a vNIC 455

Displaying the CDN Name of a vNIC 455

Displaying the Status of a vNIC 456

Cisco UCS Manager CLI Configuration Guide, Release 2.2xx

Contents

CIMC Security Policies 457

IPMI Access Profile 457

Configuring an IPMI Access Profile 457

Deleting an IPMI Access Profile 459

Adding an Endpoint User to an IPMI Access Profile 459

Deleting an Endpoint User from an IPMI Access Profile 460

KVMManagement Policy 461

Configuring a KVM Management Policy 461

Configuring Local Disk Configuration Policies 462

Local Disk Configuration Policy 462

Guidelines for all Local Disk Configuration Policies 463

Guidelines for Local Disk Configuration Policies Configured for RAID 463

Creating a Local Disk Configuration Policy 465

Viewing a Local Disk Configuration Policy 466

Deleting a Local Disk Configuration Policy 467

FlexFlash Support 467

FlexFlash FX3S Support 470

Enabling or Disabling FlexFlash SD Card Support 470

Enabling Auto-Sync 471

Formatting the FlexFlash Cards 472

Resetting the FlexFlash Controller 472

Viewing the FlexFlash Controller Status 473

Configuring Scrub Policies 475

Scrub Policy Settings 475

Creating a Scrub Policy 476

Deleting a Scrub Policy 477

Configuring DIMM Error Management 478

DIMM Correctable Error Handling 478

Resetting Memory Errors 478

DIMM Blacklisting 478

Enabling DIMM Blacklisting 479

Configuring Serial over LAN Policies 480

Serial over LAN Policy Overview 480

Configuring a Serial over LAN Policy 480

Viewing a Serial over LAN Policy 481

Cisco UCS Manager CLI Configuration Guide, Release 2.2 xxi

Contents

Deleting a Serial over LAN Policy 481

Configuring Server Autoconfiguration Policies 482

Server Autoconfiguration Policy Overview 482

Configuring a Server Autoconfiguration Policy 482

Deleting a Server Autoconfiguration Policy 483

Configuring Server Discovery Policies 484

Server Discovery Policy Overview 484

Configuring a Server Discovery Policy 485

Deleting a Server Discovery Policy 486

Configuring Server Inheritance Policies 486

Server Inheritance Policy Overview 486

Configuring a Server Inheritance Policy 486

Deleting a Server Inheritance Policy 488

Configuring Server Pool Policies 488

Server Pool Policy Overview 488

Configuring a Server Pool Policy 488

Deleting a Server Pool Policy 489

Configuring Server Pool Policy Qualifications 490

Server Pool Policy Qualification Overview 490

Creating a Server Pool Policy Qualification 490

Deleting a Server Pool Policy Qualification 491

Creating an Adapter Qualification 492

Deleting an Adapter Qualification 493

Configuring a Chassis Qualification 493

Deleting a Chassis Qualification 494

Creating a CPU Qualification 495

Deleting a CPU Qualification 496

Creating a Power Group Qualification 497

Deleting a Power Group Qualification 497

Creating a Memory Qualification 498

Deleting a Memory Qualification 499

Creating a Physical Qualification 499

Deleting a Physical Qualification 500

Creating a Storage Qualification 501

Deleting a Storage Qualification 502

Cisco UCS Manager CLI Configuration Guide, Release 2.2xxii

Contents

Configuring vNIC/vHBA Placement Policies 503

vNIC/vHBA Placement Policies 503

vCon to Adapter Placement 504

vCon to Adapter Placement for N20-B6620-2 and N20-B6625-2 Blade Servers 504

vCon to Adapter Placement for All Other Supported Servers 504

vNIC/vHBA to vCon Assignment 505

Configuring a vNIC/vHBA Placement Policy 507

Deleting a vNIC/vHBA Placement Policy 510

Explicitly Assigning a vNIC to a vCon 510

Explicitly Assigning a vHBA to a vCon 511

Placing Static vNICs Before Dynamic vNICs 512

vNIC/vHBA Host Port Placement 514

Configuring Host Port Placement 514

CIMC Mounted vMedia 516

Creating a CIMC vMedia Policy 516

C H A P T E R 2 9 Configuring Server Boot 521

Boot Policy 521

UEFI Boot Mode 522

UEFI Secure Boot 523

CIMC Secure Boot 523

Determining the CIMC Secure Boot Status 524

Enabling CIMC Secure Boot 525

Creating a Boot Policy 525

SAN Boot 528

Configuring a SAN Boot for a Boot Policy 528

iSCSI Boot 530

iSCSI Boot Process 531

iSCSI Boot Guidelines and Prerequisites 531

Initiator IQN Configuration 533

Enabling MPIO on Windows 533

Configuring iSCSI Boot 534

Creating an iSCSI Adapter Policy 535

Deleting an iSCSI Adapter Policy 537

Creating an Authentication Profile 537

Cisco UCS Manager CLI Configuration Guide, Release 2.2 xxiii

Contents

Deleting an Authentication Profile 538

Adding a Block of IP Addresses to the Initiator Pool 539

Deleting a Block of IP Addresses from the Initiator Pool 540

Creating an iSCSI Boot Policy 541

Deleting iSCSI Devices from a Boot Policy 543

Setting an Initiator IQN at the Service Profile Level 543

Creating an iSCSI vNIC in a Service Profile 544

Deleting an iSCSI vNIC from a Service Profile 546

Creating an iSCSI Initiator that Boots Using a Static IP Address 546

Deleting the Static IP Address Boot Parameters from an iSCSI Initiator 548

Creating an iSCSI Initiator that Boots Using an IP Address from an IP Pool 548

Deleting the IP Pool Boot Parameter from an iSCSI Initiator 550

Creating an iSCSI Initiator that Boots Using DHCP 550

Deleting the DHCP Boot Parameter from an iSCSI Initiator 551

IQN Pools 552

Creating an IQN Pool 553

Adding a Block to an IQN Pool 554

Deleting a Block from an IQN Pool 555

Deleting an IQN Pool 555

Viewing IQN Pool Usage 556

Creating an iSCSI Static Target 557

Deleting an iSCSI Static Target 559

Creating an iSCSI Auto Target 560

Deleting an iSCSI Auto Target 561

Verifying iSCSI Boot 562

LAN Boot 562

Configuring a LAN Boot for a Boot Policy 562

Local Devices Boot 563

Configuring a Local Disk Boot for a Boot Policy 565

Configuring a Virtual Media Boot for a Boot Policy 567

Creating a CIMC vMedia Boot Policy 568

Viewing a CIMC vMedia Mount 569

Configuring an EFI Shell Boot for a Boot Policy 570

Deleting a Boot Policy 571

UEFI Boot Parameters 571

Cisco UCS Manager CLI Configuration Guide, Release 2.2xxiv

Contents

Guidelines and Limitations for UEFI Boot Parameters 571

Configuring UEFI Boot Parameters for a Local LUN 572

Configuring UEFI Boot Parameters for an iSCSI LUN 574

Configuring UEFI Boot Parameters for a SAN LUN 576

C H A P T E R 3 0 Deferring Deployment of Service Profile Updates 579

Service Profile Deferred Deployments 579

Schedules for Deferred Deployments 580

Maintenance Policy 580

Pending Activities for Deferred Deployments 581

Guidelines and Limitations for Deferred Deployments 582

Configuring Schedules 583

Creating a Schedule 583

Creating a One Time Occurrence for a Schedule 583

Creating a Recurring Occurrence for a Schedule 584

Deleting a One Time Occurrence from a Schedule 586

Deleting a Recurring Occurrence from a Schedule 586

Deleting a Schedule 587

Configuring Maintenance Policies 587

Creating a Maintenance Policy 587

Deleting a Maintenance Policy 589

Managing Pending Activities 589

Viewing Pending Activities 589

Deploying a Service Profile Change Waiting for User Acknowledgement 590

Deploying a Scheduled Service Profile Change Immediately 591

C H A P T E R 3 1 Service Profiles 593

Service Profiles that Override Server Identity 593

Service Profiles that Inherit Server Identity 594

Guidelines and Recommendations for Service Profiles 595

Inband Service Profiles 595

Configuring an Inband Service Profile 595

Configuring an Inband Management Service Profile 596

Deleting the Inband Configuration from a Service Profile 598

Configuring Inband Management on the CIMC 598

Cisco UCS Manager CLI Configuration Guide, Release 2.2 xxv

Contents

Deleting the Inband Configuration from the CIMC 601

Initial and Existing Templates 602

Creating a Service Profile Template 602

Creating a Service Profile Instance from a Service Profile Template 605

Unbinding a Service Profile from a Service Profile Template 606

Creating a Hardware-Based Service Profile 607

Configuring a vNIC for a Service Profile 610

Creating vNIC Pairs on a Service Profile 612

Configuring a vHBA for a Service Profile 613

Creating vHBA Pairs on a Service Profile 615

Configuring a Local Disk for a Service Profile 616

Configuring Serial over LAN for a Service Profile 617

Service Profile Boot Definition Configuration 618

Configuring a Boot Definition for a Service Profile 618

Configuring a LAN Boot for a Service Profile Boot Definition 619

Configuring a Storage Boot for a Service Profile Boot Definition 620

Configuring a Virtual Media Boot for a Service Profile Boot Definition 622

Deleting a Boot Definition for a Service Profile 623

Configuring Fibre Channel Zoning for a Service Profile 623

Configuring a vHBA Initiator Group with an Existing Storage Connection Policy 623

Configuring a vHBA Initiator Group with a local Storage Connection Policy Definition 624

Service Profiles and Service Profile Template Management 626

Associating a Service Profile with a Blade Server or Server Pool 626

Associating a Service Profile with a Rack Server 626

Disassociating a Service Profile from a Server or Server Pool 627

Renaming a Service Profile 628

Resetting the UUID Assigned to a Service Profile from a Pool in a Service Profile

Template 629

Resetting the MAC Address Assigned to a vNIC from a Pool in a Service Profile

Template 630

Resetting the WWPN Assigned to a vHBA from a Pool in a Service Profile Template 631

C H A P T E R 3 2 Configuring Storage Profiles 633

Storage Profiles 633

Disk Groups and Disk Group Configuration Policies 634

Cisco UCS Manager CLI Configuration Guide, Release 2.2xxvi

Contents

Virtual Drives 634

RAID Levels 635

Automatic Disk Selection 636

Supported LUN Modifications 637

Unsupported LUN Modifications 637

Disk Insertion Handling 638

Non-Redundant Virtual Drives 638

Redundant Virtual Drives with No Hot Spare Drives 638

Redundant Virtual Drives with Hot Spare Drives 638

Replacing Hot Spare Drives 639

Inserting Physical Drives into Unused Slots 639

Virtual Drive Naming 639

LUN Dereferencing 640

Controller Constraints and Limitations 640

Configuring Storage Profiles 640

Configuring a Disk Group Policy 640

Setting the RAID Level 641

Automatically Configuring Disks in a Disk Group 641

Manually Configuring Disks in a Disk Group 643

Configuring Virtual Drive Properties 644

Creating a Storage Profile 647

Deleting a Storage Profile 648

Creating a Storage Profile PCH Controller Definition 648

Deleting a Storage Profile PCH Controller Definition 650

Creating Local LUNs 651

Deleting Local LUNs In a Storage Profile 652

Associating a Storage Profile with a Service Profile 653

Displaying Details of All Local LUNs Inherited By a Service Profile 654

Importing Foreign Configurations for a RAID Controller on a Blade Server 655

Importing Foreign Configurations for a RAID Controller on a Rack Server 656

Configuring Local Disk Operations on a Blade Server 656

Configuring Local Disk Operations on a Rack Server 658

Configuring Virtual Drive Operations 659

Deleting an Orphaned Virtual Drive on a Blade Server 659

Deleting an Orphaned Virtual Drive on a Rack Server 662

Cisco UCS Manager CLI Configuration Guide, Release 2.2 xxvii

Contents

Renaming an Orphaned Virtual Drive on a Blade Server 664

Renaming an Orphaned Virtual Drive on a Rack Server 665

Boot Policy for Local Storage 665

Configuring the Boot Policy for a Local LUN 665

Configuring the Boot Policy for a Local JBOD Disk 667

Local LUN Operations in a Service Profile 668

Preprovisioning a LUN Name or Claiming an Orphan LUN 668

Deploying and Undeploying a LUN 669

Renaming a Service Profile Referenced LUN 670

Viewing the Local Disk Locator LED State 671

Turning On the Local Disk Locator LED 671

Turning Off the Local Disk Locator LED 672

C H A P T E R 3 3 Managing Power in Cisco UCS 673

Power Capping in Cisco UCS 674

Viewing Power Measured for Blades 674

Rack Server Power Management 675

Power Management Precautions 675

Configuring the Power Policy 675

Power Policy for Cisco UCS Servers 675

Configuring the Power Policy 675

Viewing and Modifying the Global Power Profiling Policy 676

Configuring the Global Power Allocation Policy 677

Global Power Allocation Policy 677

Configuring the Global Power Allocation Policy 677

Viewing the Power Cap Values for Servers 678

Configuring Policy-Driven Chassis Group Power Capping 678

Policy Driven Chassis Group Power Capping 678

Power Groups in UCS Manager 679

Creating a Power Group 681

Deleting a Power Group 681

Power Control Policy 682

Creating a Power Control Policy 682

Deleting a Power Control Policy 683

Configuring Manual Blade-Level Power Capping 683

Cisco UCS Manager CLI Configuration Guide, Release 2.2xxviii

Contents

Manual Blade Level Power Cap 683

Setting the Blade-Level Power Cap for a Server 684

Viewing the Blade-Level Power Cap 685

Power Sync Policy 685

Power Synchronization Behavior 686

Displaying the Global Power Sync Policy 686

Setting Global Policy Reference for a Service Profile 687

Creating a Power Sync Policy 688

Deleting a Power Sync Policy 689

Displaying All Power Sync Policies 689

Creating a Local Policy 690

Showing a Local Policy 691

Deleting a Local Policy 692

C H A P T E R 3 4 Managing Time Zones 693

Time Zones 693

Setting the Time Zone 693

Adding an NTP Server 695

Deleting an NTP Server 696

Setting the System Clock Manually 696

C H A P T E R 3 5 Managing the Chassis 697

Guidelines for Removing and Decommissioning Chassis 697

Acknowledging a Chassis 698

Decommissioning a Chassis 698

Removing a Chassis 699

Recommissioning a Chassis 699

Renumbering a Chassis 700

Toggling the Locator LED 702

Turning On the Locator LED for a Chassis 702

Turning Off the Locator LED for a Chassis 703

NVMe PCIe SSD Inventory 703

Viewing NVMe PCIe Local Disk Inventory Details 703

Viewing NVMe PCIe SSD RAID Controller Inventory Details 704

Cisco UCS Manager CLI Configuration Guide, Release 2.2 xxix

Contents

C H A P T E R 3 6 Managing Blade Servers 705

Blade Server Management 706

Cisco UCS B460 M4 Blade Server Management 706

Upgrading to a Cisco UCS B460 M4 Blade Server 707

Guidelines for Removing and Decommissioning Blade Servers 707

Recommendations for Avoiding Unexpected Server Power Changes 708

Booting a Blade Server 709

Shutting Down a Blade Server 709

Power Cycling a Blade Server 710

Performing a Hard Reset on a Blade Server 711

Resetting a Blade Server to Factory Default Settings 712

Acknowledging a Blade Server 713

Removing a Blade Server from a Chassis 713

Decommissioning a Blade Server 714

Turning On the Locator LED for a Blade Server 715

Turning Off the Locator LED for a Blade Server 715

Resetting the CMOS for a Blade Server 716

Resetting the CIMC for a Blade Server 716

Clearing TPM for a Blade Server 717

Recovering the Corrupt BIOS on a Blade Server 718

Issuing an NMI from a Blade Server 719

Health LED Alarms 719

Viewing Health LED Status 720

C H A P T E R 3 7 Managing Rack-Mount Servers 721

Rack-Mount Server Management 722

Guidelines for Removing and Decommissioning Rack-Mount Servers 722

Recommendations for Avoiding Unexpected Server Power Changes 723

Booting a Rack-Mount Server 723

Shutting Down a Rack-Mount Server 724

Power Cycling a Rack-Mount Server 725

Performing a Hard Reset on a Rack-Mount Server 725

Acknowledging a Rack-Mount Server 726

Decommissioning a Rack-Mount Server 727

Cisco UCS Manager CLI Configuration Guide, Release 2.2xxx

Contents

Renumbering a Rack-Mount Server 727

Removing a Rack-Mount Server 728

Turning On the Locator LED for a Rack-Mount Server 729

Turning Off the Locator LED for a Rack-Mount Server 730

Resetting the CMOS for a Rack-Mount Server 730

Resetting the CIMC for a Rack-Mount Server 731

Clearing TPM for a Rack-Mount Server 731

Recovering the Corrupt BIOS on a Rack-Mount Server 732

Showing the Status for a Rack-Mount Server 733

Issuing an NMI from a Rack-Mount Server 733

C H A P T E R 3 8 CIMC Session Management 735

CIMC Session Management 735

Viewing the CIMC Sessions Opened by the Local Users 736

Viewing the CIMC Sessions Opened by the Remote Users 737

Viewing the CIMC Sessions Opened by an IPMI User 738

Clearing the CIMC Sessions of a Server 738

Clearing All CIMC Sessions Opened by a Local User 739

Clearing All CIMC Sessions Opened by a Remote User 740

Clearing a Specific CIMC Session Opened by a Local User 740

Clearing a Specific CIMC Session Opened by a Remote User 741

Clearing a CIMC Session Opened by an IPMI User 741

C H A P T E R 3 9 Managing the I/O Modules 743

I/O Module Management in Cisco UCS Manager GUI 743

Acknowledging an IO Module 743

Resetting the I/O Module 744

Resetting an I/O Module from a Peer I/O Module 744

C H A P T E R 4 0 Backing Up and Restoring the Configuration 747

Backup Operations in UCS 747

Backup Types 747

Considerations and Recommendations for Backup Operations 748

Scheduled Backups 749

Full State Backup Policy 749

Cisco UCS Manager CLI Configuration Guide, Release 2.2 xxxi

Contents

All Configuration Export Policy 749

Import Configuration 750

Import Methods 750

System Restore 750

Required User Role for Backup and Import Operations 751

Configuring Backup Operations 751

Creating a Backup Operation 751

Running a Backup Operation 752

Modifying a Backup Operation 753

Deleting a Backup Operation 755

Configuring Scheduled Backups 755

Configuring the Full State Backup Policy 755

Configuring the All Configuration Export Policy 757

Configuring Backup/Export Configuration Reminders 759

Configuring Import Operations 759

Creating an Import Operation 759

Running an Import Operation 761

Modifying an Import Operation 761

Deleting an Import Operation 763

Restoring the Configuration for a Fabric Interconnect 763

Erasing the Configuration 765

C H A P T E R 4 1 Recovering a Lost Password 767

Password Recovery for the Admin Account 767

Determining the Leadership Role of a Fabric Interconnect 768

Recovering the Admin Account Password in a Standalone Configuration 768

Recovering the Admin Account Password in a Cluster Configuration 770

Cisco UCS Manager CLI Configuration Guide, Release 2.2xxxii

Contents

Preface

Audience, page xxxiii

Conventions, page xxxiii

Related Cisco UCS Documentation, page xxxv

Documentation Feedback, page xxxv

AudienceThis guide is intended primarily for data center administrators with responsibilities and expertise in one ormore of the following:

Server administration

Storage administration

Network administration

Network security

ConventionsIndicationText Type

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.

GUI elements

Document titles appear in this font.Document titles

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

Terminal sessions and information that the system displays appear in thisfont.

System output

Cisco UCS Manager CLI Configuration Guide, Release 2.2 xxxiii

IndicationText Type

CLI command keywords appear in this font.

Variables in a CLI command appear in this font.

CLI commands

Elements in square brackets are optional.[ ]

Required alternative keywords are grouped in braces and separated by verticalbars.

{x | y | z}

Optional alternative keywords are grouped in brackets and separated by verticalbars.

[x | y | z]

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

string

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 codeindicates a comment line.

!, #

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

Note

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

Tip

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

Timesaver

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

Caution

Cisco UCS Manager CLI Configuration Guide, Release 2.2xxxiv

PrefaceConventions

IMPORTANT SAFETY INSTRUCTIONS

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

SAVE THESE INSTRUCTIONS

Warning

Related Cisco UCS DocumentationDocumentation Roadmaps

For a complete list of all B-Series documentation, see theCiscoUCS B-Series Servers Documentation Roadmapavailable at the following URL: http://www.cisco.com/go/unifiedcomputing/b-series-doc.

For a complete list of all C-Series documentation, see theCiscoUCSC-Series Servers Documentation Roadmapavailable at the following URL: http://www.cisco.com/go/unifiedcomputing/c-series-doc.

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

Other Documentation Resources

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

Documentation FeedbackTo provide technical feedback on this document, or to report an error or omission, please send your commentsto [email protected]. We appreciate your feedback.

Cisco UCS Manager CLI Configuration Guide, Release 2.2 xxxv

PrefaceRelated Cisco UCS Documentation

http://www.cisco.com/go/unifiedcomputing/b-series-dochttp://www.cisco.com/go/unifiedcomputing/c-series-dochttp://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-manager/products-release-notes-list.htmlhttp://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-manager/products-release-notes-list.htmlhttp://twitter.com/ciscoucsdocsmailto:[email protected]

Cisco UCS Manager CLI Configuration Guide, Release 2.2xxxvi

PrefaceDocumentation Feedback

C H A P T E R 1Overview 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 SystemCisco Unified Computing System (Cisco UCS) fuses access layer networking and servers. Thishigh-performance, next-generation server system provides a data center with a high degree of workload agilityand scalability.

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

Architectural Simplification

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

Cisco UCS implements Cisco unified fabric within racks and groups of racks, supporting Ethernet and FibreChannel 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 upto two-thirds. All devices in a Cisco UCS domain remain under a single management domain, which remainshighly available through the use of redundant components.

Cisco UCS Manager CLI Configuration Guide, Release 2.2 1

High Availability

The management and data plane of Cisco UCS is designed for high availability and redundant access layerfabric interconnects. In addition, Cisco UCS supports existing high availability and disaster recovery solutionsfor 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 throughone CiscoUCSManager. Formore detailed information about the scalability, speak to your Cisco representative.

Flexibility

ACisco UCS domain allows you to quickly align computing resources in the data center with rapidly changingbusiness requirements. This built-in flexibility is determined by whether you choose to fully implement thestateless 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 scheduledand unscheduled downtime. Server identity can be abstracted into a mobile service profile that can be movedfrom 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 theserver identity or reconfigure the server, LAN, or SAN. During a maintenance window, you can quickly dothe 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 upagain 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 improvedsupport for server virtualization, including better policy-based configuration and security, conformance witha company's operational model, and accommodation for VMware's VMotion.

Unified FabricWith 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 carryLAN and SAN traffic on the same cable.

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

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

Cisco UCS Manager CLI Configuration Guide, Release 2.22

Overview of Cisco Unified Computing SystemUnified Fabric

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

Fibre Channel over EthernetCisco UCS leverages Fibre Channel over Ethernet (FCoE) standard protocol to deliver Fibre Channel. Theupper Fibre Channel layers are unchanged, so the Fibre Channel operational model is maintained. FCoEnetwork 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 Ethernetwith the use of a dedicated Ethertype, 0x8906, so that FCoE traffic and standard Ethernet traffic can be carriedon 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 bynative Fibre Channel, FCoE depends upon the Ethernet link to implement lossless service.

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

Link-level flow control

Priority flow control

Link-Level Flow ControlIEEE 802.3x link-level flow control allows a congested receiver to signal the endpoint to pause data transmissionfor 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 disabledfor both directions.

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

Priority Flow ControlThe priority flow control (PFC) feature applies pause functionality to specific classes of traffic on the Ethernetlink. For example, PFC can provide lossless service for the FCoE traffic, and best-effort service for the standardEthernet traffic. PFC can provide different levels of service to specific classes of Ethernet traffic (using IEEE802.1p traffic classes).

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

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


Overview of Cisco Unified Computing SystemFibre Channel over Ethernet

IPv6 ComplianceCisco 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 addressingbody has exacerbated the decline of available addresses.

IPv6 addresses have a larger address space, and the pool of available IPv6 addresses is much greaterthan 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.

Only public global unicast IPv6 addresses are supported.Note

IPv6 addresses can be used to configure inband access to management interfaces, the Cisco Cisco UCSManager GUI, the KVM Console, and SSH over SoL.

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

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+


Overview of Cisco Unified Computing SystemIPv6 Compliance

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, whenFabric B is subsequently configured, the setup process retrieves the address type from Fabric A, and promptsyou to use IPv6 addresses. IPv4 addresses then need to be configured for both fabric interconnects forout-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 andaddress blocks, service profiles, service profile templates, VLAN groups, backup and restore operations, thecore file exporter, the Cisco UCS Manager Syslog, NTP servers, ARP targets in the Management InterfaceMonitoring policy, System Event Log (SEL) management, license management, firmware download, CallHome, 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 serverCisco Integrated Management Controller (CIMC) is possible using IPv6 addresses. Inband access is fasterbecause management traffic flows between the fabric interconnects and the servers using the higher-bandwidthuplink port.

Only Cisco UCSM3 and M4 servers support IPv6 addresses. IPv6 addressing for Cisco UCSM1 and M2servers is not supported.

Note

Server Architecture and Connectivity

Overview of Service ProfilesService profiles are the central concept of Cisco UCS. Each service profile serves a specific purpose: ensuringthat 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, fabricconnectivity, and server and network identity. This information is stored in a format that you can manage


Overview of Cisco Unified Computing SystemServer Architecture and Connectivity

through Cisco UCSManager. All service profiles are centrally managed and stored in a database on the fabricinterconnect.

Every server must be associated with a service profile.

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

Important

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

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

Network Connectivity through Service ProfilesEach service profile specifies the LAN and SAN network connections for the server through the Cisco UCSinfrastructure and out to the external network. You do not need to manually configure the network connectionsfor Cisco UCS servers and other components. All network configuration is performed through the serviceprofile.

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

Configuration through Service ProfilesA service profile can take advantage of resource pools and policies to handle server and connectivityconfiguration.

Hardware Components Configured by Service Profiles

When a service profile is associated with a server, the following components are configured according to thedata 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 useidentities that you specify in the associated service profile either directly or through identity pools, such asMAC, WWN, and UUID.

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

Profile name and description


Overview of Cisco Unified Computing SystemOverview 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 bea physical NIC to the operating system of the server. The type of adapter in the system determines how manyvNICs you can create. For example, a converged network adapter has two NICs, which means you can createa maximum of two vNICs for each adapter.

A vNIC communicates over Ethernet and handles LAN traffic. At a minimum, each vNIC must be configuredwith 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 bea physical HBA to the operating system of the server. The type of adapter in the system determines how manyvHBAs you can create. For example, a converged network adapter has two HBAs, which means you cancreate a maximum of two vHBAs for each of those adapters. In contrast, a network interface card does nothave 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 configuredwith a name and fabric connectivity.

Service Profiles that Override Server IdentityThis type of service profile provides the maximum amount of flexibility and control. This profile allows youto override the identity values that are on the server at the time of association and use the resource pools andpolicies 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. Thisre-association can be done either manually or through an automated server pool policy. The burned-in settings,such as UUID andMAC 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 anycomponent 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



Operating system boot order policies

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

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

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

Note

Service Profiles that Inherit Server IdentityThis hardware-based service profile is the simplest to use and create. This profile uses the default values inthe server and mimics the management of a rack-mounted server. It is tied to a specific server and cannot bemoved 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 timeof 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

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

Important

Initial and Existing TemplatesWith 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.

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

Tip

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



Cisco UCS supports the following types of service profile templates:

Initial template

Service profiles created from an initial template inherit all the properties of the template. Service profilescreated from an initial service profile template are bound to the template. However, changes to theinitial template do not automatically propagate to the bound service profiles. If you want to propagatechanges 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 remainconnected to the template. Any changes to the template automatically update the service profiles createdfrom the template.

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

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

Note

PoliciesPolicies determine how Cisco UCS components will act in specific circumstances. You can create multipleinstances of most policies. For example, you might want different boot policies, so that some servers can PXEboot, 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 areused in a service profile, which is created by someone without that subject matter expertise. For example, aLAN administrator can create adapter policies and quality of service policies for the system. These policiescan then be used in a service profile that is created by someone who has limited or no subject matter expertisewith 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

PoolsPools are collections of identities, or physical or logical resources, that are available in the system. All poolsincrease 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 intogroupings that make sense for the data center. For example, if you create a pool of unconfigured servers withsimilar characteristics and include that pool in a service profile, you can use a policy to associate that serviceprofile with an available, unconfigured server.


Overview of Cisco Unified Computing SystemPolicies

If you pool identifying information, such as MAC addresses, you can preassign ranges for servers that hostspecific applications. For example, you can configure all database servers within the same range of MACaddresses, 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 CiscoUCS domain is registered with Cisco UCS Central, you can assign Global Pools in Cisco UCS Manager.

CIMC Inband ManagementA driving factor for providing inbandmanagement access to Cisco IntegratedManagement Controller (CIMC)is the desire to separate tenant traffic from provider traffic in multi-tenant, public or private service providercloud deployments. Out-of-band (OOB) management traffic moves in and out of the fabric interconnects andtraverses the management plane via the management port. This has the potential to cause bottlenecks andaffect the CPU bandwidth in the management ports.

Inband management allows CIMC traffic to take the same path as the data traffic, entering and exiting thefabric interconnects via the uplink ports. The higher bandwidth available to the uplink ports means that inbandaccess greatly speeds up management traffic, and reduces the risk of traffic bottlenecks and CPU stress. Bothout-of-band (OOB) and inband address pools can be configured for management access in Cisco UCSManager.Out-of-band access only supports IPv4 addresses. Inband access supports both IPv4 and IPv6 addresses, whichallows for single or dual stack management.

The two OOB management interface addresses that can be configured in Cisco UCS Manager blade and rackservers 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 youconfigure both OOB and inband addresses, users can choose from a list of those addresses in the KVMConsoledialog 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


Overview of Cisco Unified Computing SystemCIMC Inband Management

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

Only Cisco UCS M3 and M4 servers support inband CIMC access. Inband CIMC access for Cisco UCSM1 and M2 servers is not supported.

Note

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 toCisco UCS M3 and M4 servers.

Inband Management SupportInband 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

OversubscriptionOversubscription 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 oftime. As a result, when configured correctly, oversubscription allows you to take advantage of unusedbandwidth. However, incorrectly configured oversubscription can result in contention for bandwidth and alower 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 attemptto send data at a cumulative rate higher than available bandwidth of uplink port.

Oversubscription ConsiderationsThe 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 ratiocan impact performance. For example, if your system has twenty ports that can communicate down to the


Overview of Cisco Unified Computing SystemInband Management Support

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 ofthe LAN to increase bandwidth. In Cisco UCS, you must have at least one uplink port per fabric interconnectto ensure that all servers andNICs to have access to the LAN. The number of LAN uplinks should be determinedby 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 uplinkports can exist on the fixed slot and on expansion slots.

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

For example, if you have two Cisco UCS 5100 series chassis that are fully populated with half width CiscoUCS B200-M1 servers, you have 16 servers. In a cluster configuration, with one LAN uplink per fabricinterconnect, these 16 servers share 20GbE of LAN bandwidth. If more capacity is needed, more uplinks fromthe fabric interconnect should be added. We recommend that you have symmetric configuration of the uplinkin cluster configurations. In the same example, if 4 uplinks are used in each fabric interconnect, the 16 serversare sharing 80 GB of bandwidth, so each has approximately 5 GB of capacity. When multiple uplinks areused on a Cisco UCS fabric interconnect the network design team should consider using a port channel tomake 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 uplinkports and increasing the number of cables. In Cisco UCS, you can have one, two, or four cables connectinga I/O module to a Cisco UCS 6100 series fabric interconnect. You can have up to eight cables if you'reconnecting a 2208 I/O module and a 6248 fabric interconnect. The number of cables determines the numberof 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 modulesused and the number of cables used to connect those I/O modules to the fabric interconnects. Having a secondI/O module in place provides additional bandwidth and redundancy to the servers. This level of flexibility indesign ensures that you can provide anywhere from 80 Gbps (two I/O modules with four links each) to 10Gbps (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 anon-oversubscribed configuration, with an ability to use up to 20 Gbps with 2:1 oversubscription.

Guidelines for Estimating OversubscriptionWhen you estimate the optimal oversubscription ratio for a fabric interconnect port, consider the followingguidelines:


Overview of Cisco Unified Computing SystemOversubscription

Cost/Performance Slider

The prioritization of cost and performance is different for each data center and has a direct impact on theconfiguration of oversubscription. When you plan hardware usage for oversubscription, you need to knowwhere the data center is located on this slider. For example, oversubscription can be minimized if the datacenter 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 theassignment 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, theratio 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

Documents

Cisco UCS Manager CLI Configuration Guide, Release 2 · Cisco UCS Manager CLI Configuration Guide, Release 2.2 First Published: 2013-12-11 Last Modified: 2016-07-27 Americas Headquarters