Cisco Systems Ol 25712 04 Users Manual UCS Manager GUI Configuration Guide, Release 2.0
OL-25712-04 to the manual aa743f32-830c-4df6-95d7-752741e4c0aa
2015-01-05
: Cisco-Systems Cisco-Systems-Ol-25712-04-Users-Manual-203185 cisco-systems-ol-25712-04-users-manual-203185 cisco-systems pdf
Open the PDF directly: View PDF .
Page Count: 768
Download | |
Open PDF In Browser | View PDF |
Cisco UCS Manager GUI Configuration Guide, Release 2.0 First Published: September 06, 2011 Last Modified: September 04, 2012 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 Text Part Number: OL-25712-04 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. 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) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. © 2011-2012 Cisco Systems, Inc. All rights reserved. CONTENTS Preface Preface xxxiii Audience xxxiii Conventions xxxiii Related Cisco UCS Documentation xxxv Documentation Feedback xxxv Obtaining Documentation and Submitting a Service Request xxxv PART I CHAPTER 1 Introduction 1 New and Changed Information 3 New and Changed Information for this Release 3 CHAPTER 2 Overview of Cisco Unified Computing System 9 About Cisco Unified Computing System 9 Unified Fabric 10 Fibre Channel over Ethernet 11 Link-Level Flow Control 11 Priority Flow Control 11 Server Architecture and Connectivity 12 Overview of Service Profiles 12 Network Connectivity through Service Profiles 12 Configuration through Service Profiles 12 Service Profiles that Override Server Identity 13 Service Profiles that Inherit Server Identity 14 Service Profile Templates 15 Policies 15 Configuration Policies 15 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 iii Contents Boot Policy 15 Chassis Discovery Policy 16 Dynamic vNIC Connection Policy 19 Ethernet and Fibre Channel Adapter Policies 19 Global Cap Policy 20 Host Firmware Package 21 IPMI Access Profile 21 Local Disk Configuration Policy 22 Management Firmware Package 22 Management Interfaces Monitoring Policy 23 Network Control Policy 23 Power Control Policy 24 Power Policy 24 Quality of Service Policy 25 Rack Server Discovery Policy 25 Server Autoconfiguration Policy 25 Server Discovery Policy 25 Server Inheritance Policy 26 Server Pool Policy 26 Server Pool Policy Qualifications 26 vHBA Template 27 VM Lifecycle Policy 27 vNIC Template 27 vNIC/vHBA Placement Policies 28 Operational Policies 28 Fault Collection Policy 28 Flow Control Policy 29 Maintenance Policy 29 Scrub Policy 29 Serial over LAN Policy 30 Statistics Collection Policy 30 Statistics Threshold Policy 30 Pools 31 Server Pools 31 MAC Pools 31 Cisco UCS Manager GUI Configuration Guide, Release 2.0 iv OL-25712-04 Contents UUID Suffix Pools 32 WWN Pools 32 Management IP Pool 33 Traffic Management 33 Oversubscription 33 Oversubscription Considerations 33 Guidelines for Estimating Oversubscription 34 Pinning 35 Pinning Server Traffic to Server Ports 35 Guidelines for Pinning 36 Quality of Service 37 System Classes 37 Quality of Service Policy 38 Flow Control Policy 38 Opt-In Features 38 Stateless Computing 38 Multi-Tenancy 39 Virtualization in Cisco UCS 40 Overview of Virtualization 40 Overview of Cisco Virtual Machine Fabric Extender 41 Virtualization with Network Interface Cards and Converged Network Adapters 41 Virtualization with a Virtual Interface Card Adapter 41 CHAPTER 3 Overview of Cisco UCS Manager 43 About Cisco UCS Manager 43 Tasks You Can Perform in Cisco UCS Manager 44 Tasks You Cannot Perform in Cisco UCS Manager 46 Cisco UCS Manager in a High Availability Environment 46 CHAPTER 4 Overview of Cisco UCS Manager GUI 47 Overview of Cisco UCS Manager GUI 47 Fault Summary Area 48 Navigation Pane 48 Toolbar 50 Work Pane 50 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 v Contents Status Bar 50 Table Customization 51 LAN Uplinks Manager 52 Internal Fabric Manager 52 Hybrid Display 53 Logging in to Cisco UCS Manager GUI through HTTPS 53 Logging in to Cisco UCS Manager GUI through HTTP 54 Logging Off Cisco UCS Manager GUI 54 Web Session Limits 55 Setting the Web Session Limit for Cisco UCS Manager 55 Pre-Login Banner 56 Creating the Pre-Login Banner 56 Modifying the Pre-Login Banner 56 Deleting the Pre-Login Banner 57 Cisco UCS Manager GUI Properties 57 Configuring the Cisco UCS Manager GUI Session and Log Properties 57 Configuring Properties for Confirmation Messages 58 Configuring Properties for External Applications 59 Customizing the Appearance of Cisco UCS Manager GUI 59 Determining the Acceptable Range of Values for a Field 60 Determining Where a Policy Is Used 60 Determining Where a Pool Is Used 61 Copying the XML 61 System Configuration 63 PART II CHAPTER 5 Configuring the Fabric Interconnects 65 Initial System Setup 65 Setup Mode 66 System Configuration Type 66 Management Port IP Address 66 Performing an Initial System Setup for a Standalone Configuration 67 Initial System Setup for a Cluster Configuration 69 Performing an Initial System Setup on the First Fabric Interconnect 69 Performing an Initial System Setup on the Second Fabric Interconnect 71 Cisco UCS Manager GUI Configuration Guide, Release 2.0 vi OL-25712-04 Contents Enabling a Standalone Fabric Interconnect for Cluster Configuration 72 Ethernet Switching Mode 72 Configuring Ethernet Switching Mode 73 Fibre Channel Switching Mode 74 Configuring Fibre Channel Switching Mode 74 Changing the Properties of the Fabric Interconnects 75 Determining the Leadership Role of a Fabric Interconnect 76 CHAPTER 6 Configuring Ports and Port Channels 77 Server and Uplink Ports on the 6100 Series Fabric Interconnect 77 Unified Ports on the 6200 Series Fabric Interconnect 78 Port Modes 78 Port Types 79 Beacon LEDs for Unified Ports 80 Guidelines for Configuring Unified Ports 80 Effect of Port Mode Changes on Data Traffic 81 Configuring Port Modes for a 6248 Fabric Interconnect 82 Configuring Port Modes for a 6296 Fabric Interconnect 83 Configuring the Beacon LEDs for Unified Ports 84 Server Ports 85 Configuring Server Ports 85 Uplink Ethernet Ports 85 Configuring Uplink Ethernet Ports 85 Changing the Properties of an Uplink Ethernet Port 86 Reconfiguring a Port on a Fabric Interconnect 86 Enabling a Port on a Fabric Interconnect 87 Disabling a Port on a Fabric Interconnect 88 Unconfiguring a Port on a Fabric Interconnect 89 Appliance Ports 89 Configuring an Appliance Port 89 Modifying the Properties of an Appliance Port 92 FCoE and Fibre Channel Storage Ports 94 Configuring an FCoE Storage Port 94 Configuring a Fibre Channel Storage Port 94 Restoring an Uplink Fibre Channel Port 95 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 vii Contents Default Zoning 95 Enabling Default Zoning 96 Disabling Default Zoning 97 Uplink Ethernet Port Channels 97 Creating an Uplink Ethernet Port Channel 98 Enabling an Uplink Ethernet Port Channel 99 Disabling an Uplink Ethernet Port Channel 99 Adding Ports to and Removing Ports from an Uplink Ethernet Port Channel 99 Deleting an Uplink Ethernet Port Channel 100 Appliance Port Channels 100 Creating an Appliance Port Channel 100 Enabling an Appliance Port Channel 103 Disabling an Appliance Port Channel 103 Adding Ports to and Removing Ports from an Appliance Port Channel 103 Deleting an Appliance Port Channel 104 Fibre Channel Port Channels 104 Creating a Fibre Channel Port Channel 104 Enabling a Fibre Channel Port Channel 105 Disabling a Fibre Channel Port Channel 106 Adding Ports to and Removing Ports from a Fibre Channel Port Channel 106 Modifying the Properties of a Fibre Channel Port Channel 106 Deleting a Fibre Channel Port Channel 107 Adapter Port Channels 108 Viewing Adapter Port Channels 108 Fabric Port Channels 108 Cabling Considerations for Fabric Port Channels 109 Configuring a Fabric Port Channel 109 Viewing Fabric Port Channels 110 Enabling or Disabling a Fabric Port Channel Member Port 110 Configuring Server Ports with the Internal Fabric Manager 111 Internal Fabric Manager 111 Launching the Internal Fabric Manager 111 Configuring a Server Port with the Internal Fabric Manager 111 Unconfiguring a Server Port with the Internal Fabric Manager 112 Enabling a Server Port with the Internal Fabric Manager 112 Cisco UCS Manager GUI Configuration Guide, Release 2.0 viii OL-25712-04 Contents Disabling a Server Port with the Internal Fabric Manager 112 CHAPTER 7 Configuring Communication Services 113 Communication Services 113 Configuring CIM-XML 114 Configuring HTTP 115 Configuring HTTPS 115 Certificates, Key Rings, and Trusted Points 115 Creating a Key Ring 116 Creating a Certificate Request for a Key Ring 117 Creating a Trusted Point 118 Importing a Certificate into a Key Ring 119 Configuring HTTPS 119 Deleting a Key Ring 121 Deleting a Trusted Point 121 Configuring SNMP 121 Information about SNMP 121 SNMP Functional Overview 121 SNMP Notifications 122 SNMP Security Levels and Privileges 122 Supported Combinations of SNMP Security Models and Levels 123 SNMPv3 Security Features 124 SNMP Support in Cisco UCS 124 Enabling SNMP and Configuring SNMP Properties 125 Creating an SNMP Trap 126 Deleting an SNMP Trap 127 Creating an SNMPv3 user 128 Deleting an SNMPv3 User 129 Enabling Telnet 129 Disabling Communication Services 129 CHAPTER 8 Configuring Authentication 131 Authentication Services 131 Guidelines and Recommendations for Remote Authentication Providers 131 User Attributes in Remote Authentication Providers 132 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 ix Contents LDAP Group Rule 134 Configuring LDAP Providers 134 Configuring Properties for LDAP Providers 134 Creating an LDAP Provider 135 Changing the LDAP Group Rule for an LDAP Provider 139 Deleting an LDAP Provider 140 LDAP Group Mapping 140 Creating an LDAP Group Map 141 Deleting an LDAP Group Map 141 Configuring RADIUS Providers 142 Configuring Properties for RADIUS Providers 142 Creating a RADIUS Provider 142 Deleting a RADIUS Provider 144 Configuring TACACS+ Providers 144 Configuring Properties for TACACS+ Providers 144 Creating a TACACS+ Provider 145 Deleting a TACACS+ Provider 146 Configuring Multiple Authentication Systems 146 Multiple Authentication Systems 146 Provider Groups 147 Creating an LDAP Provider Group 147 Deleting an LDAP Provider Group 147 Creating a RADIUS Provider Group 148 Deleting a RADIUS Provider Group 148 Creating a TACACS+ Provider Group 149 Deleting a TACACS+ Provider Group 149 Authentication Domains 150 Creating an Authentication Domain 150 Selecting a Primary Authentication Service 151 Selecting the Console Authentication Service 151 Selecting the Default Authentication Service 152 Role Policy for Remote Users 153 Configuring the Role Policy for Remote Users 154 CHAPTER 9 Configuring Organizations 155 Cisco UCS Manager GUI Configuration Guide, Release 2.0 x OL-25712-04 Contents Organizations in a Multi-Tenancy Environment 155 Hierarchical Name Resolution in a Multi-Tenancy Environment 156 Creating an Organization under the Root Organization 157 Creating an Organization under a Sub-Organization 158 Deleting an Organization 158 CHAPTER 10 Configuring Role-Based Access Control 159 Role-Based Access Control 159 User Accounts for Cisco UCS Manager 159 Guidelines for Cisco UCS Manager Usernames 160 Reserved Words: Locally Authenticated User Accounts 161 Guidelines for Cisco UCS Manager Passwords 162 Web Session Limits for User Accounts 162 User Roles 162 Default User Roles 163 Reserved Words: User Roles 164 Privileges 164 User Locales 166 Configuring User Roles 167 Creating a User Role 167 Adding Privileges to a User Role 168 Removing Privileges from a User Role 168 Deleting a User Role 168 Configuring Locales 169 Creating a Locale 169 Assigning an Organization to a Locale 170 Deleting an Organization from a Locale 170 Deleting a Locale 171 Configuring Locally Authenticated User Accounts 171 Creating a User Account 171 Enabling the Password Strength Check for Locally Authenticated Users 174 Setting the Web Session Limits for Cisco UCS Manager GUI Users 174 Changing the Locales Assigned to a Locally Authenticated User Account 175 Changing the Roles Assigned to a Locally Authenticated User Account 175 Enabling a User Account 176 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 xi Contents Disabling a User Account 176 Clearing the Password History for a Locally Authenticated User 177 Deleting a Locally Authenticated User Account 177 Password Profile for Locally Authenticated Users 177 Configuring the Maximum Number of Password Changes for a Change Interval 179 Configuring a No Change Interval for Passwords 179 Configuring the Password History Count 180 Monitoring User Sessions 180 CHAPTER 11 Managing Firmware 183 Overview of Firmware 183 Firmware Image Management 184 Firmware Image Headers 185 Firmware Image Catalog 185 Firmware Versions 186 Firmware Upgrades 187 Cautions, Guidelines, and Best Practices for Firmware Upgrades 187 Configuration Changes and Settings that Can Impact Upgrades 188 Hardware-Related Guidelines and Best Practices for Firmware Upgrades 189 Firmware- and Software-Related Best Practices for Upgrades 190 Required Order of Components for Firmware Activation 192 Required Order for Adding Support for Previously Unsupported Servers 193 Direct Firmware Upgrade at Endpoints 194 Stages of a Direct Firmware Upgrade 195 Outage Impacts of Direct Firmware Upgrades 196 Firmware Upgrades through Service Profiles 197 Host Firmware Package 197 Management Firmware Package 198 Stages of a Firmware Upgrade through Service Profiles 198 Firmware Downgrades 199 Completing the Prerequisites for Upgrading the Firmware 199 Prerequisites for Upgrading and Downgrading Firmware 199 Creating an All Configuration Backup File 200 Verifying the Overall Status of the Fabric Interconnects 202 Verifying the High Availability Status and Roles of a Cluster Configuration 202 Cisco UCS Manager GUI Configuration Guide, Release 2.0 xii OL-25712-04 Contents Verifying the Status of I/O Modules 203 Verifying the Status of Servers 203 Verifying the Status of Adapters on Servers in a Chassis 204 Downloading and Managing Firmware Packages 204 Obtaining Software Bundles from Cisco 204 Downloading Firmware Images to the Fabric Interconnect from a Remote Location 206 Downloading Firmware Images to the Fabric Interconnect from the Local File System 207 Canceling an Image Download 208 Determining the Contents of a Firmware Package 209 Checking the Available Space on a Fabric Interconnect 209 Deleting Firmware Packages from a Fabric Interconnect 209 Deleting Firmware Images from a Fabric Interconnect 210 Directly Upgrading Firmware at Endpoints 210 Updating the Firmware on Multiple Endpoints 210 Updating the Firmware on an Adapter 212 Activating the Firmware on an Adapter 213 Updating the BIOS Firmware on a Server 213 Activating the BIOS Firmware on a Server 214 Updating the CIMC Firmware on a Server 215 Activating the CIMC Firmware on a Server 215 Updating the Firmware on an IOM 216 Activating the Firmware on an IOM 217 Activating the Board Controller Firmware on a Server 218 Activating the Cisco UCS Manager Software 219 Activating the Firmware on a Subordinate Fabric Interconnect 219 Activating the Firmware on a Primary Fabric Interconnect 220 Activating the Firmware on a Standalone Fabric Interconnect 221 Upgrading Firmware through Service Profiles 222 Host Firmware Package 222 Management Firmware Package 223 Effect of Updates to Host Firmware Packages and Management Firmware Packages 223 Creating a Host Firmware Package 226 Updating a Host Firmware Package 227 Creating a Management Firmware Package 228 Updating a Management Firmware Package 228 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 xiii Contents Adding Firmware Packages to an Existing Service Profile 229 Verifying Firmware Versions on Components 230 Managing the Capability Catalog 230 Capability Catalog 230 Contents of the Capability Catalog 230 Updates to the Capability Catalog 231 Activating a Capability Catalog Update 232 Verifying that the Capability Catalog Is Current 232 Viewing a Capability Catalog Provider 233 Downloading Individual Capability Catalog Updates 233 Obtaining Capability Catalog Updates from Cisco 233 Updating the Capability Catalog from a Remote Location 234 Updating the Capability Catalog from the Local File System 235 Updating Management Extensions 235 Management Extensions 235 Activating a Management Extension 236 CHAPTER 12 Configuring DNS Servers 237 DNS Servers in Cisco UCS 237 Adding a DNS Server 237 Deleting a DNS Server 238 CHAPTER 13 Configuring System-Related Policies 239 Configuring the Chassis Discovery Policy 239 Chassis Discovery Policy 239 Configuring the Chassis Discovery Policy 242 Configuring the Chassis Connectivity Policy 243 Chassis Connectivity Policy 243 Configuring a Chassis Connectivity Policy 243 Configuring the Rack Server Discovery Policy 244 Rack Server Discovery Policy 244 Configuring the Rack Server Discovery Policy 244 Configuring the Aging Time for the MAC Address Table 245 Aging Time for the MAC Address Table 245 Configuring the Aging Time for the MAC Address Table 245 Cisco UCS Manager GUI Configuration Guide, Release 2.0 xiv OL-25712-04 Contents CHAPTER 14 Managing Licenses 247 Licenses 247 Obtaining the Host ID for a Fabric Interconnect 248 Obtaining a License 249 Downloading Licenses to the Fabric Interconnect from the Local File System 250 Downloading Licenses to the Fabric Interconnect from a Remote Location 251 Installing a License 252 Viewing the Licenses Installed on a Fabric Interconnect 253 Determining the Grace Period Available for a Port or Feature 255 Determining the Expiry Date of a License 256 Uninstalling a License 256 CHAPTER 15 Managing Virtual Interfaces 259 Virtual Interfaces 259 Virtual Interface Subscription Management and Error Handling 259 PART III CHAPTER 16 Network Configuration 261 Using the LAN Uplinks Manager 263 LAN Uplinks Manager 263 Launching the LAN Uplinks Manager 264 Changing the Ethernet Switching Mode with the LAN Uplinks Manager 264 Configuring a Port with the LAN Uplinks Manager 264 Configuring Server Ports 265 Enabling a Server Port with the LAN Uplinks Manager 265 Disabling a Server Port with the LAN Uplinks Manager 266 Unconfiguring a Server Port with the LAN Uplinks Manager 266 Configuring Uplink Ethernet Ports 266 Enabling an Uplink Ethernet Port with the LAN Uplinks Manager 266 Disabling an Uplink Ethernet Port with the LAN Uplinks Manager 267 Unconfiguring an Uplink Ethernet Port with the LAN Uplinks Manager 267 Configuring Uplink Ethernet Port Channels 267 Creating a Port Channel with the LAN Uplinks Manager 267 Enabling a Port Channel with the LAN Uplinks Manager 268 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 xv Contents Disabling a Port Channel with the LAN Uplinks Manager 269 Adding Ports to a Port Channel with the LAN Uplinks Manager 269 Removing Ports from a Port Channel with the LAN Uplinks Manager 270 Deleting a Port Channel with the LAN Uplinks Manager 270 Configuring LAN Pin Groups 270 Creating a Pin Group with the LAN Uplinks Manager 270 Deleting a Pin Group with the LAN Uplinks Manager 271 Configuring Named VLANs 271 Creating a Named VLAN with the LAN Uplinks Manager 271 Deleting a Named VLAN with the LAN Uplinks Manager 274 Configuring QoS System Classes with the LAN Uplinks Manager 274 CHAPTER 17 Configuring VLANs 277 Named VLANs 277 Private VLANs 278 VLAN Port Limitations 279 Configuring Named VLANs 280 Creating a Named VLAN 280 Deleting a Named VLAN 284 Configuring Private VLANs 285 Creating a Primary VLAN for a Private VLAN 285 Creating a Secondary VLAN for a Private VLAN 288 Viewing the VLAN Port Count 291 CHAPTER 18 Configuring LAN Pin Groups 293 LAN Pin Groups 293 Creating a LAN Pin Group 293 Deleting a LAN Pin Group 294 CHAPTER 19 Configuring MAC Pools 295 MAC Pools 295 Creating a MAC Pool 295 Deleting a MAC Pool 296 CHAPTER 20 Configuring Quality of Service 297 Cisco UCS Manager GUI Configuration Guide, Release 2.0 xvi OL-25712-04 Contents Quality of Service 297 Configuring System Classes 297 System Classes 297 Configuring QoS System Classes 298 Enabling a QoS System Class 300 Disabling a QoS System Class 300 Configuring Quality of Service Policies 301 Quality of Service Policy 301 Creating a QoS Policy 301 Deleting a QoS Policy 303 Configuring Flow Control Policies 304 Flow Control Policy 304 Creating a Flow Control Policy 304 Deleting a Flow Control Policy 305 CHAPTER 21 Configuring Network-Related Policies 307 Configuring vNIC Templates 307 vNIC Template 307 Creating a vNIC Template 307 Deleting a vNIC Template 311 Binding a vNIC to a vNIC Template 311 Unbinding a vNIC from a vNIC Template 312 Configuring Ethernet Adapter Policies 312 Ethernet and Fibre Channel Adapter Policies 312 Creating an Ethernet Adapter Policy 313 Deleting an Ethernet Adapter Policy 317 Configuring Network Control Policies 317 Network Control Policy 317 Creating a Network Control Policy 318 Deleting a Network Control Policy 320 CHAPTER 22 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 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 xvii Contents Configuring Cisco UCS for Upstream Disjoint L2 Networks 324 Creating a VLAN for an Upstream Disjoint L2 Network 325 Assigning Ports and Port Channels to VLANs 327 Removing Ports and Port Channels from VLANs 328 Viewing Ports and Port Channels Assigned to VLANs 329 Storage Configuration 331 PART IV CHAPTER 23 Configuring Named VSANs 333 Named VSANs 333 Fibre Channel Uplink Trunking for Named VSANs 334 Guidelines and Recommendations for VSANs 334 Creating a Named VSAN 335 Creating a Storage VSAN 337 Deleting a VSAN 339 Changing the VLAN ID for the FCoE VLAN for a Storage VSAN 340 Enabling Fibre Channel Uplink Trunking 341 Disabling Fibre Channel Uplink Trunking 341 CHAPTER 24 Configuring SAN Pin Groups 343 SAN Pin Groups 343 Creating a SAN Pin Group 343 Deleting a SAN Pin Group 344 CHAPTER 25 Configuring WWN Pools 345 WWN Pools 345 Configuring WWNN Pools 346 Creating a WWNN Pool 346 Adding a WWN Block to a WWNN Pool 347 Deleting a WWN Block from a WWNN Pool 347 Adding a WWNN Initiator to a WWNN Pool 348 Deleting a WWNN Initiator from a WWNN Pool 349 Deleting a WWNN Pool 349 Configuring WWPN Pools 350 Creating a WWPN Pool 350 Cisco UCS Manager GUI Configuration Guide, Release 2.0 xviii OL-25712-04 Contents Adding a WWN Block to a WWPN Pool 351 Deleting a WWN Block from a WWPN Pool 351 Adding a WWPN Initiator to a WWPN Pool 352 Deleting a WWPN Initiator from a WWPN Pool 353 Deleting a WWPN Pool 353 CHAPTER 26 Configuring Storage-Related Policies 355 Configuring vHBA Templates 355 vHBA Template 355 Creating a vHBA Template 355 Deleting a vHBA Template 357 Binding a vHBA to a vHBA Template 357 Unbinding a vHBA from a vHBA Template 358 Configuring Fibre Channel Adapter Policies 358 Ethernet and Fibre Channel Adapter Policies 358 Creating a Fibre Channel Adapter Policy 359 Deleting a Fibre Channel Adapter Policy 364 PART V CHAPTER 27 Server Configuration 365 Configuring Server-Related Pools 367 Configuring Server Pools 367 Server Pools 367 Creating a Server Pool 367 Deleting a Server Pool 368 Adding Servers to a Server Pool 369 Removing Servers from a Server Pool 369 Configuring UUID Suffix Pools 369 UUID Suffix Pools 369 Creating a UUID Suffix Pool 370 Deleting a UUID Suffix Pool 371 CHAPTER 28 Setting the Management IP Address 373 Management IP Address 373 Configuring the Management IP Address on a Blade Server 374 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 xix Contents Configuring a Blade Server to Use a Static IP Address 374 Configuring a Blade Server to Use the Management IP Pool 374 Configuring the Management IP Address on a Rack Server 375 Configuring a Rack Server to Use a Static IP Address 375 Configuring a Rack Server to Use the Management IP Pool 376 Setting the Management IP Address on a Service Profile 376 Setting the Management IP Address on a Service Profile Template 377 Configuring the Management IP Pool 377 Management IP Pool 377 Creating an IP Address Block in the Management IP Pool 378 Deleting an IP Address Block from the Management IP Pool 379 CHAPTER 29 Configuring Server-Related Policies 381 Configuring BIOS Settings 381 Server BIOS Settings 381 Main BIOS Settings 382 Processor BIOS Settings 384 Intel Directed I/O BIOS Settings 390 RAS Memory BIOS Settings 392 Serial Port BIOS Settings 394 USB BIOS Settings 394 PCI Configuration BIOS Settings 395 Boot Options BIOS Settings 396 Server Management BIOS Settings 397 BIOS Policy 402 Default BIOS Settings 402 Creating a BIOS Policy 403 Modifying the BIOS Defaults 404 Viewing the Actual BIOS Settings for a Server 404 Configuring IPMI Access Profiles 405 IPMI Access Profile 405 Creating an IPMI Access Profile 405 Deleting an IPMI Access Profile 406 Configuring Local Disk Configuration Policies 407 Local Disk Configuration Policy 407 Cisco UCS Manager GUI Configuration Guide, Release 2.0 xx OL-25712-04 Contents Guidelines for all Local Disk Configuration Policies 407 Guidelines for Local Disk Configuration Policies Configured for RAID 408 Creating a Local Disk Configuration Policy 410 Changing a Local Disk Configuration Policy 412 Deleting a Local Disk Configuration Policy 413 Configuring Scrub Policies 413 Scrub Policy 413 Creating a Scrub Policy 414 Deleting a Scrub Policy 415 Configuring Serial over LAN Policies 415 Serial over LAN Policy 415 Creating a Serial over LAN Policy 415 Deleting a Serial over LAN Policy 416 Configuring Server Autoconfiguration Policies 417 Server Autoconfiguration Policy 417 Creating an Autoconfiguration Policy 417 Deleting an Autoconfiguration Policy 418 Configuring Server Discovery Policies 419 Server Discovery Policy 419 Creating a Server Discovery Policy 419 Deleting a Server Discovery Policy 420 Configuring Server Inheritance Policies 420 Server Inheritance Policy 420 Creating a Server Inheritance Policy 420 Deleting a Server Inheritance Policy 421 Configuring Server Pool Policies 422 Server Pool Policy 422 Creating a Server Pool Policy 422 Deleting a Server Pool Policy 423 Configuring Server Pool Policy Qualifications 423 Server Pool Policy Qualifications 423 Creating Server Pool Policy Qualifications 424 Deleting Server Pool Policy Qualifications 428 Deleting Qualifications from Server Pool Policy Qualifications 428 Configuring vNIC/vHBA Placement Policies 429 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 xxi Contents vNIC/vHBA Placement Policies 429 vCon to Adapter Placement 430 vNIC/vHBA to vCon Assignment 430 Creating a vNIC/vHBA Placement Policy 433 Deleting a vNIC/vHBA Placement Policy 434 Explicitly Assigning a vNIC to a vCon 434 Explicitly Assigning a vHBA to a vCon 435 CHAPTER 30 Configuring Server Boot 439 Boot Policy 439 Creating a Boot Policy 440 SAN Boot 441 Configuring a SAN Boot for a Boot Policy 441 iSCSI Boot 443 iSCSI Boot Process 444 iSCSI Boot Guidelines and Prerequisites 444 Enabling MPIO on Windows 446 Configuring iSCSI Boot 446 Creating an iSCSI Adapter Policy 447 Deleting an iSCSI Adapter Policy 449 Creating an Authentication Profile 449 Deleting an Authentication Profile 450 Creating an iSCSI Initiator IP Pool 450 Deleting an iSCSI Initiator IP Pool 451 Creating an iSCSI Boot Policy 451 Creating an iSCSI vNIC for a Service Profile 452 Deleting an iSCSI vNIC from a Service Profile 454 Setting iSCSI Boot Parameters 454 Modifying iSCSI Boot Parameters 458 IQN Pools 461 Creating an IQN Pool 461 Adding a Block to an IQN Pool 463 Deleting a Block from an IQN Pool 463 Deleting an IQN Pool 464 LAN Boot 465 Cisco UCS Manager GUI Configuration Guide, Release 2.0 xxii OL-25712-04 Contents Configuring a LAN Boot for a Boot Policy 465 Local Disk Boot 465 Configuring a Local Disk Boot for a Boot Policy 466 Virtual Media Boot 466 Configuring a Virtual Media Boot for a Boot Policy 466 Deleting a Boot Policy 467 CHAPTER 31 Deferring Deployment of Service Profile Updates 469 Deferred Deployment of Service Profiles 469 Deferred Deployment Schedules 470 Maintenance Policy 470 Pending Activities 471 Guidelines and Limitations for Deferred Deployment 471 Configuring Schedules 472 Creating a Schedule 472 Creating a One Time Occurrence for a Schedule 477 Creating a Recurring Occurrence for a Schedule 479 Deleting a One Time Occurrence from a Schedule 481 Deleting a Recurring Occurrence from a Schedule 481 Deleting a Schedule 482 Configuring Maintenance Policies 482 Creating a Maintenance Policy 482 Deleting a Maintenance Policy 484 Managing Pending Activities 484 Viewing Pending Activities 484 Deploying a Service Profile Change Waiting for User Acknowledgement 484 Deploying All Service Profile Changes Waiting for User Acknowledgement 485 Deploying a Scheduled Service Profile Change Immediately 485 Deploying All Scheduled Service Profile Changes Immediately 486 CHAPTER 32 Configuring Service Profiles 487 Service Profiles that Override Server Identity 487 Service Profiles that Inherit Server Identity 488 Service Profile Templates 488 Guidelines and Recommendations for Service Profiles 489 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 xxiii Contents Creating Service Profiles 489 Creating a Service Profile with the Expert Wizard 489 Page 1: Identifying the Service Profile 490 Page 2: Configuring the Storage Options 491 Page 3: Configuring the Networking Options 496 Page 4: Setting the vNIC/vHBA Placement 502 Page 5: Setting the Server Boot Order 504 Page 6: Adding the Maintenance Policy 507 Page 7: Specifying the Server Assignment 509 Page 8: Adding Operational Policies 511 Creating a Service Profile that Inherits Server Identity 513 Creating a Hardware Based Service Profile for a Blade Server 517 Creating a Hardware Based Service Profile for a Rack-Mount Server 517 Working with Service Profile Templates 518 Creating a Service Profile Template 518 Page 1: Identifying the Service Profile Template 519 Page 2: Specifying the Storage Options 520 Page 3: Specifying the Networking Options 524 Page 4: Setting the vNIC/vHBA Placement 530 Page 5: Setting the Server Boot Order 532 Page 6: Adding the Maintenance Policy 535 Page 7: Specifying the Server Assignment Options 537 Page 8: Adding Operational Policies 539 Creating One or More Service Profiles from a Service Profile Template 541 Creating a Template Based Service Profile for a Blade Server 541 Creating a Template Based Service Profile for a Rack-Mount Server 542 Creating a Service Profile Template from a Service Profile 543 Managing Service Profiles 544 Cloning a Service Profile 544 Associating a Service Profile with a Server or Server Pool 544 Disassociating a Service Profile from a Server or Server Pool 545 Associating a Service Profile Template with a Server Pool 546 Disassociating a Service Profile Template from its Server Pool 547 Changing the UUID in a Service Profile 547 Changing the UUID in a Service Profile Template 548 Cisco UCS Manager GUI Configuration Guide, Release 2.0 xxiv OL-25712-04 Contents Resetting the UUID Assigned to a Service Profile from a Pool in a Service Profile Template 549 Modifying the Boot Order in a Service Profile 550 Creating a vNIC for a Service Profile 553 Resetting the MAC Address Assigned to a vNIC from a Pool in a Service Profile Template 555 Deleting a vNIC from a Service Profile 556 Creating a vHBA for a Service Profile 556 Changing the WWPN for a vHBA 559 Resetting the WWPN Assigned to a vHBA from a Pool in a Service Profile Template 560 Clearing Persistent Binding for a vHBA 560 Deleting a vHBA from a Service Profile 561 Binding a Service Profile to a Service Profile Template 561 Unbinding a Service Profile from a Service Profile Template 562 Deleting a Service Profile 562 CHAPTER 33 Managing Power in Cisco UCS 563 Power Management in Cisco UCS 563 Rack Server Power Management 563 Power Management Precautions 563 Configuring the Power Policy 564 Power Policy 564 Configuring the Power Policy 564 Configuring the Global Cap Policy 564 Global Cap Policy 564 Configuring the Global Cap Policy 565 Configuring Policy-Driven Chassis Group Power Capping 565 Policy-Driven Chassis Group Power Capping 565 Configuring Power Groups 566 Power Groups 566 Creating a Power Group 566 Adding a Chassis to a Power Group 568 Removing a Chassis from a Power Group 568 Deleting a Power Group 568 Configuring Power Control Policies 569 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 xxv Contents Power Control Policy 569 Creating a Power Control Policy 569 Deleting a Power Control Policy 570 Configuring Manual Blade-Level Power Capping 570 Manual Blade-Level Power Capping 570 Setting the Blade-Level Power Cap for a Server 571 Viewing the Blade-Level Power Cap 572 System Management 573 PART VI CHAPTER 34 Managing Time Zones 575 Time Zones 575 Setting the Time Zone 575 Adding an NTP Server 576 Deleting an NTP Server 576 CHAPTER 35 Managing the Chassis 577 Chassis Management in Cisco UCS Manager GUI 577 Guidelines for Removing and Decommissioning Chassis 577 Acknowledging a Chassis 578 Decommissioning a Chassis 579 Removing a Chassis 579 Recommissioning a Single Chassis 579 Recommissioning Multiple Chassis 580 Renumbering a Chassis 581 Toggling the Locator LED 582 Turning on the Locator LED for a Chassis 582 Turning off the Locator LED for a Chassis 582 Viewing the POST Results for a Chassis 582 CHAPTER 36 Managing Blade Servers 585 Blade Server Management 585 Guidelines for Removing and Decommissioning Blade Servers 586 Booting Blade Servers 586 Booting a Blade Server 586 Cisco UCS Manager GUI Configuration Guide, Release 2.0 xxvi OL-25712-04 Contents Booting a Server from the Service Profile 587 Determining the Boot Order of a Blade Server 587 Shutting Down Blade Servers 588 Shutting Down a Blade Server 588 Shutting Down a Server from the Service Profile 588 Resetting a Blade Server 589 Avoiding Unexpected Server Power Changes 590 Reacknowledging a Blade Server 591 Removing a Server from a Chassis 591 Decommissioning a Blade Server 592 Recommissioning a Blade Server 593 Reacknowledging a Server Slot in a Chassis 593 Removing a Non-Existent Blade Server from the Configuration Database 594 Turning the Locator LED for a Blade Server On and Off 594 Resetting the CMOS for a Blade Server 594 Resetting the CIMC for a Blade Server 595 Recovering the Corrupt BIOS on a Blade Server 595 Viewing the POST Results for a Blade Server 596 Issuing an NMI from a Blade Server 597 CHAPTER 37 Managing Rack-Mount Servers 599 Rack-Mount Server Management 599 Guidelines for Removing and Decommissioning Rack-Mount Servers 600 Booting Rack-Mount Servers 600 Booting a Rack-Mount Server 600 Booting a Server from the Service Profile 601 Determining the Boot Order of a Rack-Mount Server 601 Shutting Down Rack-Mount Servers 602 Shutting Down a Rack-Mount Server 602 Shutting Down a Server from the Service Profile 602 Resetting a Rack-Mount Server 603 Avoiding Unexpected Server Power Changes 604 Reacknowledging a Rack-Mount Server 605 Decommissioning a Rack-Mount Server 605 Recommissioning a Rack-Mount Server 606 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 xxvii Contents Renumbering a Rack-Mount Server 606 Removing a Non-Existent Rack-Mount Server from the Configuration Database 607 Turning the Locator LED for a Rack-Mount Server On and Off 607 Resetting the CMOS for a Rack-Mount Server 608 Resetting the CIMC for a Rack-Mount Server 608 Recovering the Corrupt BIOS on a Rack-Mount Server 609 Viewing the POST Results for a Rack-Mount Server 610 Issuing an NMI from a Rack-Mount Server 610 CHAPTER 38 Starting the KVM Console 611 KVM Console 611 Virtual KVM Console 612 Starting the KVM Console from a Server 615 Starting the KVM Console from a Service Profile 615 Starting the KVM Console from the KVM Launch Manager 615 CHAPTER 39 Managing the I/O Modules 617 I/O Module Management in Cisco UCS Manager GUI 617 Resetting an I/O Module 617 Viewing the POST Results for an I/O Module 617 CHAPTER 40 Backing Up and Restoring the Configuration 619 Backup and Export Configuration 619 Backup Types 619 Considerations and Recommendations for Backup Operations 620 Import Configuration 621 Import Methods 621 System Restore 621 Required User Role for Backup and Import Operations 621 Backup Operations 622 Creating a Backup Operation 622 Running a Backup Operation 625 Modifying a Backup Operation 625 Deleting One or More Backup Operations 626 Import Operations 626 Cisco UCS Manager GUI Configuration Guide, Release 2.0 xxviii OL-25712-04 Contents Creating an Import Operation 626 Running an Import Operation 629 Modifying an Import Operation 630 Deleting One or More Import Operations 630 Restoring the Configuration for a Fabric Interconnect 631 CHAPTER 41 Recovering a Lost Password 633 Recovering a Lost Password 633 Password Recovery for the Admin Account 633 Determining the Leadership Role of a Fabric Interconnect 634 Verifying the Firmware Versions on a Fabric Interconnect 634 Recovering the Admin Account Password in a Standalone Configuration 634 Recovering the Admin Account Password in a Cluster Configuration 636 PART VII System Monitoring 639 CHAPTER 42 Monitoring Traffic 641 Traffic Monitoring 641 Guidelines and Recommendations for Traffic Monitoring 642 Creating an Ethernet Traffic Monitoring Session 643 Creating a Fibre Channel Traffic Monitoring Session 644 Adding Traffic Sources to a Monitoring Session 645 Activating a Traffic Monitoring Session 646 Deleting a Traffic Monitoring Session 646 CHAPTER 43 Monitoring Hardware 647 Monitoring a Fabric Interconnect 647 Monitoring a Chassis 648 Monitoring a Blade Server 650 Monitoring a Rack-Mount Server 652 Monitoring an I/O Module 654 Monitoring Management Interfaces 655 Management Interfaces Monitoring Policy 655 Configuring the Management Interfaces Monitoring Policy 656 Server Disk Drive Monitoring 658 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 xxix Contents Support for Disk Drive Monitoring 658 Prerequisites for Disk Drive Monitoring 659 Viewing the Status of a Disk Drive 659 Interpreting the Status of a Monitored Disk Drive 660 CHAPTER 44 Configuring Statistics-Related Policies 663 Configuring Statistics Collection Policies 663 Statistics Collection Policy 663 Modifying a Statistics Collection Policy 664 Configuring Statistics Threshold Policies 666 Statistics Threshold Policy 666 Creating a Server and Server Component Threshold Policy 666 Adding a Threshold Class to an Existing Server and Server Component Threshold Policy 668 Deleting a Server and Server Component Threshold Policy 669 Adding a Threshold Class to the Uplink Ethernet Port Threshold Policy 670 Adding a Threshold Class to the Ethernet Server Port, Chassis, and Fabric Interconnect Threshold Policy 671 Adding a Threshold Class to the Fibre Channel Port Threshold Policy 672 CHAPTER 45 Configuring Call Home 675 Call Home 675 Call Home Considerations and Guidelines 677 Cisco UCS Faults and Call Home Severity Levels 678 Cisco Smart Call Home 679 Configuring Call Home 680 Disabling Call Home 683 Enabling Call Home 683 Configuring System Inventory Messages 684 Configuring System Inventory Messages 684 Sending a System Inventory Message 684 Configuring Call Home Profiles 685 Call Home Profiles 685 Creating a Call Home Profile 686 Deleting a Call Home Profile 688 Cisco UCS Manager GUI Configuration Guide, Release 2.0 xxx OL-25712-04 Contents Configuring Call Home Policies 688 Call Home Policies 688 Configuring a Call Home Policy 688 Disabling a Call Home Policy 689 Enabling a Call Home Policy 690 Deleting a Call Home Policy 690 Example: Configuring Call Home for Smart Call Home 690 Configuring Smart Call Home 690 Configuring the Default Cisco TAC-1 Profile 692 Configuring System Inventory Messages for Smart Call Home 693 Registering Smart Call Home 694 CHAPTER 46 Managing the System Event Log 695 System Event Log 695 Viewing the System Event Log for an Individual Server 696 Viewing the System Event Log for the Servers in a Chassis 696 Configuring the SEL Policy 696 Managing the System Event Log for a Server 698 Copying One or More Entries in the System Event Log 698 Printing the System Event Log 699 Refreshing the System Event Log 699 Manually Backing Up the System Event Log 699 Manually Clearing the System Event Log 699 CHAPTER 47 Configuring Settings for Faults, Events, and Logs 701 Configuring Settings for the Fault Collection Policy 701 Fault Collection Policy 701 Configuring the Fault Collection Policy 702 Configuring Settings for the Core File Exporter 703 Core File Exporter 703 Configuring the Core File Exporter 703 Disabling the Core File Exporter 704 Configuring the Syslog 704 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 xxxi Contents Cisco UCS Manager GUI Configuration Guide, Release 2.0 xxxii OL-25712-04 Preface This preface includes the following sections: • Audience, page xxxiii • Conventions, page xxxiii • Related Cisco UCS Documentation, page xxxv • Documentation Feedback, page xxxv • Obtaining Documentation and Submitting a Service Request, 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 This document uses the following conventions: Convention Indication bold font Commands, keywords, GUI elements, and user-entered text appear in bold font. italic font Document titles, new or emphasized terms, and arguments for which you supply values are in italic font. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 xxxiii Preface Conventions Note Tip Convention Indication courierfont Terminal sessions and information that the system displays appear in courier font. [] Elements in square brackets are optional. {x | y | z} Required alternative keywords are grouped in braces and separated by vertical bars. [x | y | z] Optional alternative keywords are grouped in brackets and separated by vertical bars. string 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. Means reader take note. Means the following information will help you solve a problem. Caution Means reader be careful. In this situation, you might perform an action that could result in equipment damage or loss of data. Timesaver Means the described action saves time. You can save time by performing the action described in the paragraph. Warning Means reader be warned. In this situation, you might perform an action that could result in bodily injury. Cisco UCS Manager GUI Configuration Guide, Release 2.0 xxxiv OL-25712-04 Preface Related Cisco UCS Documentation Related Cisco UCS Documentation Documentation Roadmaps For a complete list of all B-Series documentation, see the Cisco UCS B-Series Servers Documentation Roadmap available at the following URL: http://www.cisco.com/go/unifiedcomputing/b-series-doc. For a complete list of all C-Series documentation, see the Cisco UCS C-Series Servers Documentation Roadmap available at the following URL: http://www.cisco.com/go/unifiedcomputing/c-series-doc . Other Documentation Resources An ISO file containing all B and C-Series documents is available at the following URL: http://www.cisco.com/ cisco/software/type.html?mdfid=283853163&flowid=25821. From this page, click Unified Computing System (UCS) Documentation Roadmap Bundle. The ISO file is updated after every major documentation release. Follow Cisco UCS Docs on Twitter to receive document update notifications. Documentation Feedback To provide technical feedback on this document, or to report an error or omission, please send your comments to ucs-docfeedback@external.cisco.com. We appreciate your feedback. Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation. Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0. Follow Cisco UCS Docs on Twitter to receive document update notifications. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 xxxv Preface Obtaining Documentation and Submitting a Service Request Cisco UCS Manager GUI Configuration Guide, Release 2.0 xxxvi OL-25712-04 PART I Introduction • New and Changed Information, page 3 • Overview of Cisco Unified Computing System, page 9 • Overview of Cisco UCS Manager, page 43 • Overview of Cisco UCS Manager GUI, page 47 CHAPTER 1 New and Changed Information This chapter includes the following sections: • New and Changed Information for this Release, page 3 New and Changed Information for this Release The following table provides an overview of the significant changes to this guide for this current release. The table does not provide an exhaustive list of all changes made to the configuration guides or of the new features in this release. For information about new supported hardware in this release, see the Cisco UCS B-Series Servers Documentation Roadmap available at the following URL: http://www.cisco.com/go/unifiedcomputing/ b-series-doc. Table 1: New Features and Significant Behavioral Changes in Cisco UCS, Release 2.0(3) Feature Description Where Documented Cipher Suite Adds support for Cipher Suite in HTTPS configuration. Configuring Communication Services, on page 113 Web Session Refresh Enables you to configure the web Configuring Authentication, session refresh period and timeout for on page 131 authentication domains. BIOS Settings Adds support for new BIOS settings that can be included in BIOS policies and configured from Cisco UCS Manager. Overview of enabling MPIO High level information added for how Enabling MPIO on Windows, to enable MPIO with iSCSI boot. on page 446 Configuring Server-Related Policies, on page 381 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 3 New and Changed Information for this Release Table 2: New Features and Significant Behavioral Changes in Cisco UCS, Release 2.0(2) Feature Description Where Documented IQN Pools Adds support for IQN pools in Cisco UCS domains configured for iSCSI boot. iSCSI Boot, on page 443 Adapter Port Channels Enables you to group all the physical Configuring Ports and Port links from a Cisco UCS Virtual Channels, on page 77 Interface Card (VIC) to an I/O Module into one logical link. (Requires supported hardware.) Unified Port Support for 6296 Fabric Interconnect Enables you to use the Configure Unified Ports on the 6200 Unified Ports wizard to configure ports Series Fabric Interconnect, on on a 6296 fabric interconnect. page 78 Renumbering for Rack-Mount Servers Enables you to renumber an integrated Managing Rack-Mount rack-mount server. Servers, on page 599 Changes to Behavior for Power State Synchronization Adds information and a caution about power state synchronization, including use of the physical power button or the reset feature on a blade server or an integrated rack-mount server. Managing Blade Servers, on page 585 Adds support for new BIOS settings that can be included in BIOS policies and configured from Cisco UCS Manager. Configuring Server-Related Policies, on page 381 BIOS Settings Managing Rack-Mount Servers, on page 599 Table 3: New Features in Cisco UCS, Release 2.0(1) Feature Description Where Documented Disk Drive Monitoring Support Support for disk drive monitoring on Monitoring Hardware, on page certain blade servers and a specific LSI 647 storage controller firmware level. Fabric Port Channels Enables you to group several of the physical links from a IOM to a fabric interconnect into one logical link for redundancy and bandwidth sharing. (Requires supported hardware.) Firmware Bundle Option Enables you to select a bundle instead Managing Firmware, on page of a version when updating firmware 183 using the Cisco UCS Manager GUI. Configuring Ports and Port Channels, on page 77 Cisco UCS Manager GUI Configuration Guide, Release 2.0 4 OL-25712-04 New and Changed Information for this Release Feature Description Where Documented iSCSI Boot iSCSI boot enables a server to boot its iSCSI Boot, on page 443 operating system from an iSCSI target machine located remotely over a network. Licensing Updated information for new UCS hardware. Pre-login Banner Displays user-defined banner text prior Pre-Login Banner, on page 56 to login when a user logs into Cisco UCS Manager using the GUI or CLI. Unified Ports Unified ports are ports on the 6200 series fabric interconnect that can be configured to carry either Ethernet or Fibre Channel traffic. Upstream Disjoint Layer-2 Networks Enables you to configure Cisco UCS Configuring Upstream Disjoint to communicate with upstream disjoint Layer-2 Networks, on page 321 layer-2 networks. Virtual Interfaces The number of vNICs and vHBAs configurable for a service profile is determined by adapter capability and the amount of virtual interface (VIF) namespace available on the adapter. Licenses, on page 247 Unified Ports on the 6200 Series Fabric Interconnect, on page 78 Managing Virtual Interfaces, on page 259 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 5 New and Changed Information for this Release Feature Description Where Documented Virtual Interface Card Drivers Cisco UCS Virtual Interface Card This feature is now (VIC) drivers facilitate communication documented in the following between supported operating systems installation guides: and Cisco UCS Virtual Interface Cards • Cisco UCS Manager (VICs). Interface Card Drivers for ESX Installation Guide • Cisco UCS Manager Interface Card Drivers for Linux Installation Guide • Cisco UCS Manager Interface Card Drivers for Windows Installation Guide The VIC driver installation guides can be found here: http:/ /www.cisco.com/en/US/ products/ps10281/prod_ installation_guides_list.html VM-FEX Integration for VMware Cisco Virtual Machine Fabric Extender This feature is now (VM-FEX) for VMware provides documented in the following management integration and network configuration guides: communication between Cisco UCS • Cisco UCS Manager Manager and VMware vCenter. VM-FEX for VMware In previous releases, this functionality GUI Configuration was known as VN-Link in Hardware. Guide • Cisco UCS Manager VM-FEX for VMware CLI Configuration Guide The VM-FEX configuration guides can be found here: http:/ /www.cisco.com/en/US/ products/ps10281/products_ installation_and_ configuration_guides_list.html Cisco UCS Manager GUI Configuration Guide, Release 2.0 6 OL-25712-04 New and Changed Information for this Release Feature Description Where Documented VM-FEX Integration for KVM (Red Hat Linux) Cisco Virtual Machine Fabric Extender This feature is documented in (VM-FEX) for VMware provides the following configuration external switching for virtual machines guides: running on a KVM Linux-based • Cisco UCS Manager hypervisor in a Cisco UCS domain. VM-FEX for KVM GUI Configuration Guide • Cisco UCS Manager VM-FEX for KVM CLI Configuration Guide The VM-FEX configuration guides can be found here: http:/ /www.cisco.com/en/US/ products/ps10281/products_ installation_and_ configuration_guides_list.html Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 7 New and Changed Information for this Release Cisco UCS Manager GUI Configuration Guide, Release 2.0 8 OL-25712-04 CHAPTER 2 Overview of Cisco Unified Computing System This chapter includes the following sections: • About Cisco Unified Computing System , page 9 • Unified Fabric, page 10 • Server Architecture and Connectivity, page 12 • Traffic Management, page 33 • Opt-In Features, page 38 • Virtualization in Cisco UCS , page 40 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 GUI Configuration Guide, Release 2.0 OL-25712-04 9 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 GUI Configuration Guide, Release 2.0 10 OL-25712-04 Unified Fabric 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 GUI Configuration Guide, Release 2.0 OL-25712-04 11 Server Architecture and Connectivity 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 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 Cisco UCS Manager GUI Configuration Guide, Release 2.0 12 OL-25712-04 Server Architecture and Connectivity 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 • 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 and then associate it with another server. This re-association can be done either manually or through an automated server pool policy. The burned-in settings, Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 13 Server Architecture and Connectivity such as UUID and MAC address, on the new server are overwritten with the configuration in the service profile. As a result, the change in server is transparent to your network. You do not need to reconfigure any component or application on your network to begin using the new server. This profile allows you to take advantage of and manage system resources through resource pools and policies, such as the following: • 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 another policy that requires a specific hardware configuration, the profile can be used 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 may not be the values burned into the server hardware at manufacture if those values were changed before this profile is associated with the server. Cisco UCS Manager GUI Configuration Guide, Release 2.0 14 OL-25712-04 Server Architecture and Connectivity Service Profile Templates With a service profile template, you can quickly create several service profiles with the same basic parameters, such as the number of vNICs and vHBAs, and with identity information drawn from the same pools. Tip If you need only one service profile with similar values to an existing service profile, you can clone a service profile in the Cisco UCS Manager GUI. For example, if you need several service profiles with similar values to configure servers to host database software, you can create a service profile template, either manually or from an existing service profile. You then use the template to create the service profiles. Cisco UCS supports the following types of service profile templates: Initial template Service profiles created from an initial template inherit all the properties of the template. However, after you create the profile, it is no longer connected to the template. If you need to make changes to one or more profiles created from this template, you must change each profile individually. Updating template Service profiles created from an updating template inherit all the properties of the template and remain connected to the template. Any changes to the template automatically update the service profiles created from the template. Policies 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 Configuration Policies Boot Policy The boot policy determines the following: • Configuration of the boot device Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 15 Server Architecture and Connectivity • Location from which the server boots • Order in which boot devices are invoked For example, you can choose to have associated servers boot from a local device, such as a local disk or CD-ROM (VMedia), or you can select a SAN boot or a LAN (PXE) boot. You must include this policy in a service profile, and that service profile must be associated with a server for it to take effect. If you do not include a boot policy in a service profile, the server uses the default settings in the BIOS to determine the boot order. Important Changes to a boot policy may be propagated to all servers created with an updating service profile template that includes that boot policy. Reassociation of the service profile with the server to rewrite the boot order information in the BIOS is auto-triggered. Chassis Discovery Policy The chassis discovery policy determines how the system reacts when you add a new chassis. Cisco UCS Manager uses the settings in the chassis discovery policy to determine the minimum threshold for the number of links between the chassis and the fabric interconnect and whether to group links from the IOM to the fabric interconnect in a fabric port channel. Chassis Links If you have a Cisco UCS domain that has some chassis wired with 1 link, some with 2 links, some with 4 links, and some with 8 links we recommend that you configure the chassis discovery policy for the minimum number links in the domain so that Cisco UCS Manager can discover all chassis. Tip For Cisco UCS implementations that mix IOMs with different numbers of links, we recommend using the platform max value. Using platform max insures that Cisco UCS Manager uses the maximum number of IOM uplinks available. After the initial discovery, you must reacknowledge the chassis that are wired for a greater number of links and Cisco UCS Manager configures the chassis to use all available links. Cisco UCS Manager cannot discover any chassis that is wired for fewer links than are configured in the chassis discovery policy. For example, if the chassis discovery policy is configured for 4 links, Cisco UCS Manager cannot discover any chassis that is wired for 1 link or 2 links. Reacknowledgement of the chassis does not resolve this issue. The following table provides an overview of how the chassis discovery policy works in a multi-chassis Cisco UCS domain: Cisco UCS Manager GUI Configuration Guide, Release 2.0 16 OL-25712-04 Server Architecture and Connectivity Table 4: Chassis Discovery Policy and Chassis Links Number of 1-Link Chassis 2-Link Chassis 4-Link Chassis 8-Link Chassis Links Wired Discovery Discovery Discovery Discovery Policy for the Chassis Policy Policy Policy Platform-Max Discovery Policy 1 link between IOM and fabric interconnects Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 1 link. Chassis cannot be discovered by Cisco UCS Manager and is not added to the Cisco UCS domain. Chassis cannot be discovered by Cisco UCS Manager and is not added to the Cisco UCS domain. Chassis cannot be discovered by Cisco UCS Manager and is not added to the Cisco UCS domain. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 1 link. 2 links between IOM and fabric interconnects Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 1 link. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 2 link. Chassis cannot be discovered by Cisco UCS Manager and is not added to the Cisco UCS domain. Chassis cannot be discovered by Cisco UCS Manager and is not added to the Cisco UCS domain. Chassis cannot be discovered by Cisco UCS Manager and is not added to the Cisco UCS domain. After initial discovery, reacknowledge the chassis and Cisco UCS Manager recognizes and uses the additional links. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 17 Server Architecture and Connectivity Number of 1-Link Chassis 2-Link Chassis 4-Link Chassis 8-Link Chassis Links Wired Discovery Discovery Discovery Discovery Policy for the Chassis Policy Policy Policy 4 links between IOM and fabric interconnects 8 links between IOM and fabric interconnects Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 1 link. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 2 links. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 4 link. Chassis cannot be discovered by Cisco UCS Manager and is not added to the Cisco UCS domain. After initial discovery, reacknowledge the chassis and Cisco UCS Manager recognizes and uses the additional links. After initial discovery, reacknowledge the chassis and Cisco UCS Manager recognizes and uses the additional links. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 1 link. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 2 links. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 4 links. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 8 links. After initial discovery, reacknowledge the chassis and Cisco UCS Manager recognizes and uses the additional links. After initial discovery, reacknowledge the chassis and Cisco UCS Manager recognizes and uses the additional links. After initial discovery, reacknowledge the chassis and Cisco UCS Manager recognizes and uses the additional links. Platform-Max Discovery Policy If the IOM has 4 links, the chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 4 links. If the IOM has 8 links, the chassis is not fully discovered by Cisco UCS Manager. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 8 links. Link Grouping For hardware configurations that support fabric port channels, link grouping determines whether all of the links from the IOM to the fabric interconnect are grouped into a fabric port channel during chassis discovery. If the link grouping preference is set to port channel, all of the links from the IOM to the fabric interconnect Cisco UCS Manager GUI Configuration Guide, Release 2.0 18 OL-25712-04 Server Architecture and Connectivity are grouped in a fabric port channel. If set to no group, links from the IOM to the fabric interconnect are not grouped in a fabric port channel. Once a fabric port channel is created, links can be added or removed by changing the link group preference and reacknowledging the chassis, or by enabling or disabling the chassis from the port channel. Note The link grouping preference only takes effect if both sides of the links between an IOM or FEX and the fabric interconnect support fabric port channels. If one side of the links does not support fabric port channels, this preference is ignored and the links are not grouped in a port channel. Dynamic vNIC Connection Policy The dynamic vNIC connection policy determines how the connectivity between VMs and dynamic vNICs is configured. This policy is required for Cisco UCS domains that include servers with VIC adapters on which you have installed VMs and configured dynamic vNICs. Each dynamic vNIC connection policy includes an Ethernet adapter policy and designates the number of vNICs that can be configured for any server associated with a service profile that includes the policy. Note If you migrate a server that is configured with dynamic vNICs, the dynamic interface used by the vNICs fails and Cisco UCS Manager notifies you of that failure. When the server comes back up, Cisco UCS Manager assigns new dynamic vNICs to the server. If you are monitoring traffic on the dynamic vNIC, you must reconfigure the monitoring source. Ethernet and Fibre Channel Adapter Policies These policies govern the host-side behavior of the adapter, including how the adapter handles traffic. For example, you can use these policies to change default settings for the following: • Queues • Interrupt handling • Performance enhancement • RSS hash • Failover in an cluster configuration with two fabric interconnects Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 19 Server Architecture and Connectivity Note For Fibre Channel adapter policies, the values displayed by Cisco UCS Manager may not match those displayed by applications such as QLogic SANsurfer. For example, the following values may result in an apparent mismatch between SANsurfer and Cisco UCS Manager: • Max LUNs Per Target—SANsurfer has a maximum of 256 LUNs and does not display more than that number. Cisco UCS Manager supports a higher maximum number of LUNs. • Link Down Timeout—In SANsurfer, you configure the timeout threshold for link down in seconds. In Cisco UCS Manager, you configure this value in milliseconds. Therefore, a value of 5500 ms in Cisco UCS Manager displays as 5s in SANsurfer. • Max Data Field Size—SANsurfer has allowed values of 512, 1024, and 2048. Cisco UCS Manager allows you to set values of any size. Therefore, a value of 900 in Cisco UCS Manager displays as 512 in SANsurfer. Operating System Specific Adapter Policies By default, Cisco UCS provides a set of Ethernet adapter policies and Fibre Channel adapter policies. These policies include the recommended settings for each supported server operating system. Operating systems are sensitive to the settings in these policies. Storage vendors typically require non-default adapter settings. You can find the details of these required settings on the support list provided by those vendors. Important We recommend that you use the values in these policies for the applicable operating system. Do not modify any of the values in the default policies unless directed to do so by Cisco Technical Support. However, if you are creating an Ethernet adapter policy for a Windows OS (instead of using the default Windows adapter policy), you must use the following formulas to calculate values that work with Windows: Completion Queues = Transmit Queues + Receive Queues Interrupt Count = (Completion Queues + 2) rounded up to nearest power of 2 For example, if Transmit Queues = 1 and Receive Queues = 8 then: Completion Queues = 1 + 8 = 9 Interrupt Count = (9 + 2) rounded up to the nearest power of 2 = 16 Global Cap Policy The global cap policy is a global policy that specifies whether policy-driven chassis group power capping or manual blade-level power capping will be applied to all servers in a chassis. We recommend that you use the default power capping method: policy-driven chassis group power capping. Important Any change to the manual blade-level power cap configuration will result in the loss of any groups or configuration options set for policy-driven chassis group power capping. Cisco UCS Manager GUI Configuration Guide, Release 2.0 20 OL-25712-04 Server Architecture and Connectivity Host Firmware Package This policy enables you to specify a set of firmware versions that make up the host firmware package (also known as the host firmware pack). The host firmware includes the following firmware for server and adapter endpoints: • Adapter • BIOS • Board Controller • FC Adapters • HBA Option ROM • Storage Controller Tip You can include more than one type of firmware in the same host firmware package. For example, a host firmware package can include both BIOS firmware and storage controller firmware or adapter firmware for two different models of adapters. However, you can only have one firmware version with the same type, vendor, and model number. The system recognizes which firmware version is required for an endpoint and ignores all other firmware versions. The firmware package is pushed to all servers associated with service profiles that include this policy. This policy ensures that the host firmware is identical on all servers associated with service profiles which use the same policy. Therefore, if you move the service profile from one server to another, the firmware versions are maintained. Also, if you change the firmware version for an endpoint in the firmware package, new versions are applied to all the affected service profiles immediately, which could cause server reboots. You must include this policy in a service profile, and that service profile must be associated with a server for it to take effect. Prerequisites This policy is not dependent upon any other policies. However, you must ensure that the appropriate firmware has been downloaded to the fabric interconnect. If the firmware image is not available when Cisco UCS Manager is associating a server with a service profile, Cisco UCS Manager ignores the firmware upgrade and completes the association. IPMI Access Profile This policy allows you to determine whether IPMI commands can be sent directly to the server, using the IP address. For example, you can send commands to retrieve sensor data from the CIMC. This policy defines the IPMI access, including a username and password that can be authenticated locally on the server, and whether the access is read-only or read-write. You must include this policy in a service profile and that service profile must be associated with a server for it to take effect. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 21 Server Architecture and Connectivity Local Disk Configuration Policy This policy configures any optional SAS local drives that have been installed on a server through the onboard RAID controller of the local drive. This policy enables you to set a local disk mode for all servers that are associated with a service profile that includes the local disk configuration policy. The local disk modes include the following: • No Local Storage—For a diskless server or a SAN only configuration. If you select this option, you cannot associate any service profile which uses this policy with a server that has a local disk. • RAID 0 Striped—Data is striped across all disks in the array, providing fast throughput. There is no data redundancy, and all data is lost if any disk fails. • RAID 1 Mirrored—Data is written to two disks, providing complete data redundancy if one disk fails. The maximum array size is equal to the available space on the smaller of the two drives. • Any Configuration—For a server configuration that carries forward the local disk configuration without any changes. • No RAID—For a server configuration that removes the RAID and leaves the disk MBR and payload unaltered. • RAID 5 Striped Parity—Data is striped across all disks in the array. Part of the capacity of each disk stores parity information that can be used to reconstruct data if a disk fails. RAID 5 provides good data throughput for applications with high read request rates. • RAID 6 Striped Dual Parity—Data is striped across all disks in the array and two parity disks are used to provide protection against the failure of up to two physical disks. In each row of data blocks, two sets of parity data are stored. • RAID10 Mirrored and Striped— RAID 10 uses mirrored pairs of disks to provide complete data redundancy and high throughput rates. You must include this policy in a service profile, and that service profile must be associated with a server for the policy to take effect. Management Firmware Package This policy enables you to specify a set of firmware versions that make up the management firmware package (also known as a management firmware pack). The management firmware package includes the Cisco Integrated Management Controller (CIMC) on the server. You do not need to use this package if you upgrade the CIMC directly. The firmware package is pushed to all servers associated with service profiles that include this policy. This policy ensures that the CIMC firmware is identical on all servers associated with service profiles which use the same policy. Therefore, if you move the service profile from one server to another, the firmware versions are maintained. You must include this policy in a service profile, and that service profile must be associated with a server for it to take effect. This policy is not dependent upon any other policies. However, you must ensure that the appropriate firmware has been downloaded to the fabric interconnect. Cisco UCS Manager GUI Configuration Guide, Release 2.0 22 OL-25712-04 Server Architecture and Connectivity Management Interfaces Monitoring Policy This policy defines how the mgmt0 Ethernet interface on the fabric interconnect should be monitored. If Cisco UCS detects a management interface failure, a failure report is generated. If the configured number of failure reports is reached, the system assumes that the management interface is unavailable and generates a fault. By default, the management interfaces monitoring policy is disabled. If the affected management interface belongs to a fabric interconnect which is the managing instance, Cisco UCS confirms that the subordinate fabric interconnect's status is up, that there are no current failure reports logged against it, and then modifies the managing instance for the end-points. If the affected fabric interconnect is currently the primary inside of a high availability setup, a failover of the management plane is triggered. The data plane is not affected by this failover. You can set the following properties related to monitoring the management interface: • Type of mechanism used to monitor the management interface. • Interval at which the management interface's status is monitored. • Maximum number of monitoring attempts that can fail before the system assumes that the management is unavailable and generates a fault message. Important In the event of a management interface failure on a fabric interconnect, the managing instance may not change if one of the following occurs: • A path to the end-point through the subordinate fabric interconnect does not exist. • The management interface for the subordinate fabric interconnect has failed. • The path to the end-point through the subordinate fabric interconnect has failed. Network Control Policy This policy configures the network control settings for the Cisco UCS domain, including the following: • Whether the Cisco Discovery Protocol (CDP) is enabled or disabled • How the VIF behaves if no uplink port is available in end-host mode • The action that Cisco UCS Manager takes on the remote Ethernet interface, vEthernet interface , or vFibreChannel interface when the associated border port fails • Whether the server can use different MAC addresses when sending packets to the fabric interconnect • Whether MAC registration occurs on a per-VNIC basis or for all VLANs. Action on Uplink Fail By default, the Action on Uplink Fail property in the network control policy is configured with a value of link-down. For adapters such as the Cisco UCS M81KR Virtual Interface Card, this default behavior directs Cisco UCS Manager to bring the vEthernet or vFibreChannel interface down if the associated border port fails. For Cisco UCS systems using a non-VM-FEX capable converged network adapter that supports both Ethernet and FCoE traffic, such as Cisco UCS CNA M72KR-Q and the Cisco UCS CNA M72KR-E, this Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 23 Server Architecture and Connectivity default behavior directs Cisco UCS Manager to bring the remote Ethernet interface down if the associated border port fails. In this scenario, any vFibreChannel interfaces that are bound to the remote Ethernet interface are brought down as well. Note Cisco UCS Manager, release 1.4(2) and earlier did not enforce the Action on Uplink Fail property for those types of non-VM-FEX capable converged network adapters mentioned above. If the Action on Uplink Fail property was set to link-down, Cisco UCS Manager would ignore this setting and instead issue a warning. In the current version of Cisco UCS Manager this setting is enforced. Therefore, if your implementation includes one of those converged network adapters and the adapter is expected to handle both Ethernet and FCoE traffic, we recommend that you configure the Action on Uplink Fail property with a value of warning. Please note that this configuration may result in an Ethernet teaming driver not being able to detect a link failure when the border port goes down. MAC Registration Mode In Cisco UCS Manager, releases 1.4 and earlier, MAC addresses were installed on all of the VLANs belonging to an interface. Starting in release 2.0, MAC addresses are installed only on the native VLAN by default. In most implementations this maximizes the VLAN port count. Note If a trunking driver is being run on the host and the interface is in promiscuous mode, we recommend that you set the Mac Registration Mode to All VLANs. Power Control Policy Cisco UCS uses the priority set in the power control policy, along with the blade type and configuration, to calculate the initial power allocation for each blade within a chassis. During normal operation, the active blades within a chassis can borrow power from idle blades within the same chassis. If all blades are active and reach the power cap, service profiles with higher priority power control policies take precedence over service profiles with lower priority power control policies. Priority is ranked on a scale of 1-10, where 1 indicates the highest priority and 10 indicates lowest priority. The default priority is 5. For mission-critical application a special priority called no-cap is also available. Setting the priority to no-cap prevents Cisco UCS from leveraging unused power from that particular blade server. The server is allocated the maximum amount of power that that blade can reach. Note You must include this policy in a service profile and that service profile must be associated with a server for it to take effect. Power Policy The power policy is a global policy that specifies the redundancy for power supplies in all chassis in the Cisco UCS domain. This policy is also known as the PSU policy. Cisco UCS Manager GUI Configuration Guide, Release 2.0 24 OL-25712-04 Server Architecture and Connectivity For more information about power supply redundancy, see Cisco UCS 5108 Server Chassis Hardware Installation Guide. 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. Rack Server Discovery Policy The rack server discovery policy determines how the system reacts when you add a new rack-mount server. Cisco UCS Manager uses the settings in the rack server discovery policy to determine whether any data on the hard disks are scrubbed and whether server discovery occurs immediately or needs to wait for explicit user acknowledgement. Cisco UCS Manager cannot discover any rack-mount server that has not been correctly cabled and connected to the fabric interconnects. For information about how to integrate a supported Cisco UCS rack-mount server with Cisco UCS Manager, see the hardware installation guide for that server. Server Autoconfiguration Policy Cisco UCS Manager uses this policy to determine how to configure a new server. If you create a server autoconfiguration policy, the following occurs when a new server starts: 1 The qualification in the server autoconfiguration policy is executed against the server. 2 If the server meets the required qualifications, the server is associated with a service profile created from the service profile template configured in the server autoconfiguration policy. The name of that service profile is based on the name given to the server by Cisco UCS Manager. 3 The service profile is assigned to the organization configured in the server autoconfiguration policy. Server Discovery Policy This discovery policy determines how the system reacts when you add a new server. If you create a server discovery policy, you can control whether the system conducts a deep discovery when a server is added to a chassis, or whether a user must first acknowledge the new server. By default, the system conducts a full discovery. If you create a server discovery policy, the following occurs when a new server starts: 1 The qualification in the server discovery policy is executed against the server. 2 If the server meets the required qualifications, Cisco UCS Manager applies the following to the server: • Depending upon the option selected for the action, either discovers the new server immediately or waits for a user to acknowledge the new server • Applies the scrub policy to the server Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 25 Server Architecture and Connectivity Server Inheritance Policy This policy is invoked during the server discovery process to create a service profile for the server. All service profiles created from this policy use the values burned into the blade at manufacture. The policy performs the following: • Analyzes the inventory of the server • If configured, assigns the server to the selected organization • Creates a service profile for the server with the identity burned into the server at manufacture You cannot migrate a service profile created with this policy to another server. Server Pool Policy This policy is invoked during the server discovery process. It determines what happens if server pool policy qualifications match a server to the target pool specified in the policy. If a server qualifies for more than one pool and those pools have server pool policies, the server is added to all those pools. Server Pool Policy Qualifications This policy qualifies servers based on the inventory of a server conducted during the discovery process. The qualifications are individual rules that you configure in the policy to determine whether a server meets the selection criteria. For example, you can create a rule that specifies the minimum memory capacity for servers in a data center pool. Qualifications are used in other policies to place servers, not just by the server pool policies. For example, if a server meets the criteria in a qualification policy, it can be added to one or more server pools or have a service profile automatically associated with it. You can use the server pool policy qualifications to qualify servers according to the following criteria: • Adapter type • Chassis location • Memory type and configuration • Power group • CPU cores, type, and configuration • Storage configuration and capacity • Server model Depending upon the implementation, you may configure several policies with server pool policy qualifications including the following: • Autoconfiguration policy • Chassis discovery policy • Server discovery policy Cisco UCS Manager GUI Configuration Guide, Release 2.0 26 OL-25712-04 Server Architecture and Connectivity • Server inheritance policy • Server pool policy vHBA Template This template is a policy that defines how a vHBA on a server connects to the SAN. It is also referred to as a vHBA SAN connectivity template. You need to include this policy in a service profile for it to take effect. VM Lifecycle Policy The VM lifecycle policy determines how long Cisco UCS Manager retains offline VMs and offline dynamic vNICs in its database. If a VM or dynamic vNIC remains offline after that period, Cisco UCS Manager deletes the object from its database. All virtual machines (VMs) on Cisco UCS servers are managed by vCenter. Cisco UCS Manager cannot determine whether an inactive VM is temporarily shutdown, has been deleted, or is in some other state that renders it inaccessible. Therefore, Cisco UCS Manager considers all inactive VMs to be in an offline state. Cisco UCS Manager considers a dynamic vNIC to be offline when the associated VM is shutdown, or the link between the fabric interconnect and the I/O module fails. On rare occasions, an internal error can also cause Cisco UCS Manager to consider a dynamic vNIC to be offline. The default VM and dynamic vNIC retention period is 15 minutes. You can set that for any period of time between 1 minute and 7200 minutes (or 5 days). Note The VMs that Cisco UCS Manager displays are for information and monitoring only. You cannot manage VMs through Cisco UCS Manager. Therefore, when you delete a VM from the Cisco UCS Manager database, you do not delete the VM from the server or from vCenter. vNIC Template This policy defines how a vNIC on a server connects to the LAN. This policy is also referred to as a vNIC LAN connectivity policy. Beginning in Cisco UCS, Release 2.0(2), Cisco UCS Manager does not automatically create a VM-FEX port profile with the correct settings when you create a vNIC template. If you want to create a VM-FEX port profile, you must configure the target of the vNIC template as a VM. You need to include this policy in a service profile for it to take effect. Note If your server has two Emulex or QLogic NICs (Cisco UCS CNA M71KR-E or Cisco UCS CNA M71KR-Q), you must configure vNIC policies for both adapters in your service profile to get a user-defined MAC address for both NICs. If you do not configure policies for both NICs, Windows still detects both of them in the PCI bus. Then because the second eth is not part of your service profile, Windows assigns it a hardware MAC address. If you then move the service profile to a different server, Windows sees additional NICs because one NIC did not have a user-defined MAC address. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 27 Server Architecture and Connectivity vNIC/vHBA Placement Policies vNIC/vHBA placement policies are used to determine what types of vNICs or vHBAs can be assigned to the physical adapters on a server. Each vNIC/vHBA placement policy contains four virtual network interface connections (vCons) that are virtual representations of the physical adapters. When a vNIC/vHBA placement policy is assigned to a service profile, and the service profile is associated with a server, the vCons in the vNIC/vHBA placement policy are assigned to the physical adapters. If you do not include a vNIC/vHBA placement policy in the service profile or you use the default configuration for a server with two adapters, Cisco UCS Manager defaults to the All configuration and equally distributes the vNICs and vHBAs between the adapters. You can use this policy to assign vNICs or vHBAs to either of the two vCons. Cisco UCS Manager uses the vCon assignment to determine how to assign the vNICs and vHBAs to the physical adapter during service profile association. • All—All configured vNICs and vHBAs can be assigned to the vCon, whether they are explicitly assigned to it, unassigned, or dynamic. • Assigned Only—vNICs and vHBAs must be explicitly assigned to the vCon. You can assign them explicitly through the service profile or the properties of the vNIC or vHBA. • Exclude Dynamic—Dynamic vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for all static vNICs and vHBAs, whether they are unassigned or explicitly assigned to it. • Exclude Unassigned—Unassigned vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for dynamic vNICs and vHBAs and for static vNICs and vHBAs that are explicitly assigned to it. Operational Policies Fault Collection Policy The fault collection policy controls the lifecycle of a fault in a Cisco UCS domain, including when faults are cleared, the flapping interval (the length of time between the fault being raised and the condition being cleared), and the retention interval (the length of time a fault is retained in the system). A fault in Cisco UCS has the following lifecycle: 1 A condition occurs in the system and Cisco UCS Manager raises a fault. This is the active state. 2 When the fault is alleviated, it enters a flapping or soaking interval that is designed to prevent flapping. Flapping occurs when a fault is raised and cleared several times in rapid succession. During the flapping interval, the fault retains its severity for the length of time specified in the fault collection policy. 3 If the condition reoccurs during the flapping interval, the fault returns to the active state. If the condition does not reoccur during the flapping interval, the fault is cleared. 4 The cleared fault enters the retention interval. This interval ensures that the fault reaches the attention of an administrator even if the condition that caused the fault has been alleviated and the fault has not been deleted prematurely. The retention interval retains the cleared fault for the length of time specified in the fault collection policy. 5 If the condition reoccurs during the retention interval, the fault returns to the active state. If the condition does not reoccur, the fault is deleted. Cisco UCS Manager GUI Configuration Guide, Release 2.0 28 OL-25712-04 Server Architecture and Connectivity 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. Maintenance Policy A maintenance policy determines how Cisco UCS Manager reacts when a change that requires a server reboot is made to a service profile associated with a server or to an updating service profile bound to one or more service profiles. The maintenance policy specifies how Cisco UCS Manager deploys the service profile changes. The deployment can occur in one of the following ways: • Immediately • When acknowledged by a user with admin privileges • Automatically at the time specified in the schedule If the maintenance policy is configured to deploy the change during a scheduled maintenance window, the policy must include a valid schedule. The schedule deploys the changes in the first available maintenance window. Scrub Policy This policy determines what happens to local data and to the BIOS settings on a server during the discovery process and when the server is disassociated from a service profile. Depending upon how you configure a scrub policy, the following can occur at those times: Disk Scrub One of the following occurs to the data on any local drives on disassociation: • If enabled, destroys all data on any local drives • If disabled, preserves all data on any local drives, including local storage configuration Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 29 Server Architecture and Connectivity BIOS Settings Scrub One of the following occurs to the BIOS settings when a service profile containing the scrub policy is disassociated from a server: • If enabled, erases all BIOS settings for the server and and resets them to the BIOS defaults for that server type and vendor • If disabled, preserves the existing BIOS settings on the server Serial over LAN Policy This policy sets the configuration for the serial over LAN connection for all servers associated with service profiles that use the policy. By default, the serial over LAN connection is disabled. If you implement a serial over LAN policy, we recommend that you also create an IPMI profile. You must include this policy in a service profile and that service profile must be associated with a server for it to take effect. Statistics Collection Policy A statistics collection policy defines how frequently statistics are to be collected (collection interval) and how frequently the statistics are to be reported (reporting interval). Reporting intervals are longer than collection intervals so that multiple statistical data points can be collected during the reporting interval, which provides Cisco UCS Manager with sufficient data to calculate and report minimum, maximum, and average values. For NIC statistics, Cisco UCS Manager displays the average, minimum, and maximum of the change since the last collection of statistics. If the values are 0, there has been no change since the last collection. Statistics can be collected and reported for the following five functional areas of the Cisco UCS system: • Adapter—statistics related to the adapters • Chassis—statistics related to the blade chassis • Host—this policy is a placeholder for future support • Port—statistics related to the ports, including server ports, uplink Ethernet ports, and uplink Fibre Channel ports • Server—statistics related to servers Note Cisco UCS Manager has one default statistics collection policy for each of the five functional areas. You cannot create additional statistics collection policies and you cannot delete the existing default policies. You can only modify the default policies. Statistics Threshold Policy A statistics threshold policy monitors statistics about certain aspects of the system and generates an event if the threshold is crossed. You can set both minimum and maximum thresholds. For example, you can configure Cisco UCS Manager GUI Configuration Guide, Release 2.0 30 OL-25712-04 Server Architecture and Connectivity the policy to raise an alarm if the CPU temperature exceeds a certain value, or if a server is overutilized or underutilized. These threshold policies do not control the hardware or device-level thresholds enforced by endpoints, such as the CIMC. Those thresholds are burned in to the hardware components at manufacture. Cisco UCS enables you to configure statistics threshold policies for the following components: • Servers and server components • Uplink Ethernet ports • Ethernet server ports, chassis, and fabric interconnects • Fibre Channel port Note You cannot create or delete a statistics threshold policy for Ethernet server ports, uplink Ethernet ports, or uplink Fibre Channel ports. You can only configure the existing default policy. 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. If you pool identifying information, such as MAC addresses, you can pre-assign ranges for servers that will host specific applications. For example, all database servers could be configured within the same range of MAC addresses, UUIDs, and WWNs. Server Pools A server pool contains a set of servers. These servers typically share the same characteristics. Those characteristics can be their location in the chassis, or an attribute such as server type, amount of memory, local storage, type of CPU, or local drive configuration. You can manually assign a server to a server pool, or use server pool policies and server pool policy qualifications to automate the assignment. If your system implements multi-tenancy through organizations, you can designate one or more server pools to be used by a specific organization. For example, a pool that includes all servers with two CPUs could be assigned to the Marketing organization, while all servers with 64 GB memory could be assigned to the Finance organization. A server pool can include servers from any chassis in the system. A given server can belong to multiple server pools. MAC Pools A MAC pool is a collection of network identities, or MAC addresses, that are unique in their layer 2 environment and are available to be assigned to vNICs on a server. If you use MAC pools in service profiles, Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 31 Server Architecture and Connectivity you do not have to manually configure the MAC addresses to be used by the server associated with the service profile. In a system that implements multi-tenancy, you can use the organizational hierarchy to ensure that MAC pools can only be used by specific applications or business services. Cisco UCS Manager uses the name resolution policy to assign MAC addresses from the pool. To assign a MAC address to a server, you must include the MAC pool in a vNIC policy. The vNIC policy is then included in the service profile assigned to that server. You can specify your own MAC addresses or use a group of MAC addresses provided by Cisco. UUID Suffix Pools A UUID suffix pool is a collection of SMBIOS UUIDs that are available to be assigned to servers. The first number of digits that constitute the prefix of the UUID are fixed. The remaining digits, the UUID suffix, are variable. A UUID suffix pool ensures that these variable values are unique for each server associated with a service profile which uses that particular pool to avoid conflicts. If you use UUID suffix pools in service profiles, you do not have to manually configure the UUID of the server associated with the service profile. WWN Pools A WWN pool is a collection of WWNs for use by the Fibre Channel vHBAs in a Cisco UCS domain. You create separate pools for the following: • WW node names assigned to the server • WW port names assigned to the vHBA Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. All other WWN ranges are reserved. To ensure the uniqueness of the Cisco UCS WWNNs and WWPNs in the SAN fabric, we recommend that you use the following WWN prefix for all blocks in a pool: 20:00:00:25:B5:XX:XX:XX If you use WWN pools in service profiles, you do not have to manually configure the WWNs that will be used by the server associated with the service profile. In a system that implements multi-tenancy, you can use a WWN pool to control the WWNs used by each organization. You assign WWNs to pools in blocks. For each block or individual WWN, you can assign a boot target. WWNN Pools A WWNN pool is a WWN pool that contains only WW node names. If you include a pool of WWNNs in a service profile, the associated server is assigned a WWNN from that pool. WWPN Pools A WWPN pool is a WWN pool that contains only WW port names. If you include a pool of WWPNs in a service profile, the port on each vHBA of the associated server is assigned a WWPN from that pool. Cisco UCS Manager GUI Configuration Guide, Release 2.0 32 OL-25712-04 Traffic Management Management IP Pool The management IP pool is a collection of external IP addresses. Cisco UCS Manager reserves each block of IP addresses in the management IP pool for external access that terminates in the CIMC on a server. You can configure service profiles and service profile templates to use IP addresses from the management IP pool. You cannot configure servers to use the management IP pool. All IP addresses in the management IP pool must be in the same subnet as the IP address of the fabric interconnect. Note The management IP pool must not contain any IP addresses that have been assigned as static IP addresses for a server or service profile. 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 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. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 33 Traffic Management 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: 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. Cisco UCS Manager GUI Configuration Guide, Release 2.0 34 OL-25712-04 Traffic Management 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. Pinning Server Traffic to Server Ports All server traffic travels through the I/O module to server ports on the fabric interconnect. The number of links for which the chassis is configured determines how this traffic is pinned. The pinning determines which server traffic goes to which server port on the fabric interconnect. This pinning is fixed. You cannot modify it. As a result, you must consider the server location when you determine the appropriate allocation of bandwidth for a chassis. Note You must review the allocation of ports to links before you allocate servers to slots. The cabled ports are not necessarily port 1 and port 2 on the I/O module. If you change the number of links between the fabric interconnect and the I/O module, you must reacknowledge the chassis to have the traffic rerouted. All port numbers refer to the fabric interconnect-side ports on the I/O module. Chassis with One I/O Module (Not Configured for Fabric Port Channels) Note If the adapter in a server supports and is configured for adapter port channels, those port channels are pinned to the same link as described in the following table. If the I/O module in the chassis supports and is configured for fabric port channels, the server slots are pinned to a fabric port channel rather than to an individual link. Links on Chassis Link 1 / Fabric Port Channel Link 2 Link 3 Link 4 Link 5 Link 6 Link 7 Link 8 1 link All server None slots None None None None None None Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 35 Traffic Management Links on Chassis Link 1 / Fabric Port Channel Link 2 Link 3 Link 4 Link 5 Link 6 Link 7 Link 8 2 links Server Server None slots 1, 3, slots 2, 4, 5, and 7 6, and 8 None None None None None 4 links Server Server Server Server None slots 1 and slots 2 and slots 3 and slots 4 and 5 6 7 8 None None None 8 links Server slot 1 Fabric Port Channel All server N/A slots Server slot 2 Server slot 3 Server slot 4 Server slot 5 Server slot 6 Server slot 7 Server slot 8 N/A N/A N/A N/A N/A N/A Chassis with Two I/O Modules If a chassis has two I/O modules, traffic from one I/O module goes to one of the fabric interconnects and traffic from the other I/O module goes to the second fabric interconnect. You cannot connect two I/O modules to a single fabric interconnect. Fabric Interconnect Configured in vNIC Server Traffic Path A Server traffic goes to fabric interconnect A. If A fails, the server traffic does not fail over to B. B All server traffic goes to fabric interconnect B. If B fails, the server traffic does not fail over to A. A-B All server traffic goes to fabric interconnect A. If A fails, the server traffic fails over to B. B-A All server traffic goes to fabric interconnect B. If B fails, the server traffic fails over to A. 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. Cisco UCS Manager GUI Configuration Guide, Release 2.0 36 OL-25712-04 Traffic Management 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 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 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. This 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 5: System Classes System Class Description Platinum 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. Gold Silver All properties of these system classes are available for you to assign custom settings and policies. Bronze Best Effort 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. Fibre Channel 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. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 37 Opt-In Features 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. 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) Cisco UCS Manager GUI Configuration Guide, Release 2.0 38 OL-25712-04 Opt-In Features • 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 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. Multi-Tenancy Multi-tenancy allows you to divide up 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 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 39 Virtualization in Cisco UCS 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 multi-tenant 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 • Service profiles • Service profile templates If You Opt In to Multi-Tenancy Each Cisco UCS domain is divided into several distinct organizations. The types of organizations you create in a multi-tenancy 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 Multi-Tenancy 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 the creation of 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 copying, 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. Cisco UCS Manager GUI Configuration Guide, Release 2.0 40 OL-25712-04 Virtualization in Cisco UCS Overview of Cisco Virtual Machine Fabric Extender A virtualized server implementation consists of one or more VMs running 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). The hypervisor typically presents a virtual network interface to each VM and performs Layer 2 switching of traffic from a VM to other local VMs or to a physical interface to the external network. Working with a Cisco virtual interface card (VIC) adapter, Cisco Virtual Machine Fabric Extender (VM-FEX) bypasses software-based switching of VM traffic by the hypervisor in favor of external hardware-based switching in the fabric interconnect. This method results in a reduced load on the server CPU, faster switching, and the ability to apply a rich set of network management features to local and remote traffic. VM-FEX extends the (prestandard) IEEE 802.1Qbh port extender architecture to the VMs, 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, such as the Cisco UCS M81KR Virtual Interface Card, is a converged network adapter (CNA) designed for both single-OS and VM-based deployments. The VIC adapter supports static or dynamic virtualized interfaces, including up to 128 virtual network interface cards (vNICs). VIC adapters support VM-FEX to provide hardware-based switching of traffic to and from virtual machine interfaces. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 41 Virtualization in Cisco UCS Cisco UCS Manager GUI Configuration Guide, Release 2.0 42 OL-25712-04 CHAPTER 3 Overview of Cisco UCS Manager This chapter includes the following sections: • About Cisco UCS Manager , page 43 • Tasks You Can Perform in Cisco UCS Manager , page 44 • Tasks You Cannot Perform in Cisco UCS Manager , page 46 • Cisco UCS Manager in a High Availability Environment, page 46 About Cisco UCS Manager Cisco UCS Manager is the management system for all components in a UCS Manager. 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. • Generate CLI output from Cisco UCS Manager GUI. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 43 Tasks You Can Perform in Cisco UCS Manager 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 • Fabric interconnects • Fans Cisco UCS Manager GUI Configuration Guide, Release 2.0 44 OL-25712-04 Tasks You Can Perform in Cisco UCS Manager • 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 • Create VSANs • Configure the quality of service classes and definitions Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 45 Tasks You Cannot Perform in Cisco UCS Manager • 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 GUI Configuration Guide, Release 2.0 46 OL-25712-04 CHAPTER 4 Overview of Cisco UCS Manager GUI This chapter includes the following sections: • Overview of Cisco UCS Manager GUI , page 47 • Logging in to Cisco UCS Manager GUI through HTTPS, page 53 • Logging in to Cisco UCS Manager GUI through HTTP, page 54 • Logging Off Cisco UCS Manager GUI , page 54 • Web Session Limits, page 55 • Pre-Login Banner, page 56 • Cisco UCS Manager GUI Properties, page 57 • Determining the Acceptable Range of Values for a Field, page 60 • Determining Where a Policy Is Used, page 60 • Determining Where a Pool Is Used, page 61 • Copying the XML, page 61 Overview of Cisco UCS Manager GUI Cisco UCS Manager GUI is the Java application that provides a GUI interface to Cisco UCS Manager. You can start and access Cisco UCS Manager GUI from any computer that meets the requirements listed in the System Requirements section of the Cisco UCS Software Release Notes. Each time you start Cisco UCS Manager GUI, Cisco UCS Manager uses Java Web Start technology to cache the current version of the application on your computer. As a result, you do not have to download the application every time you log in. You only have to download the application the first time that you log in from a computer after the Cisco UCS Manager software has been updated on a system. Tip The title bar displays the name of the Cisco UCS domain to which you are connected. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 47 Overview of Cisco UCS Manager GUI Fault Summary Area The Fault Summary area displays in the upper left of Cisco UCS Manager GUI. This area displays a summary of all faults that have occurred in the Cisco UCS domain. Each type of fault is represented by a different icon. The number below each icon indicates how many faults of that type have occurred in the system. If you click an icon, Cisco UCS Manager GUI opens the Faults tab in the Work area and displays the details of all faults of that type. The following table describes the types of faults each icon in the Fault Summary area represents: Tip Fault Type Description Critical Alarms Critical problems exist with one or more components. These issues should be researched and fixed immediately. Major Alarms Serious problems exist with one or more components. These issues should be researched and fixed immediately. Minor Alarms Problems exist with one or more components that might adversely affect system performance. These issues should be researched and fixed as soon as possible before they become major or critical issues. Warning Alarms Potential problems exist with one or more components that might adversely affect system performance if they are allowed to continue. These issues should be researched and fixed as soon as possible before the problem grows worse. If you only want to see faults for a specific object, navigate to that object and then review the Faults tab for that object. Navigation Pane The Navigation pane displays on the left side of Cisco UCS Manager GUI below the Fault Summary area. This pane provides centralized navigation to all equipment and other components in the Cisco UCS domain. When you select a component in the Navigation pane, the object displays in the Work area. The Navigation pane has five tabs. Each tab includes the following elements: • A Filter combo box that you can use to filter the navigation tree to view all nodes or only one node. • An expandable navigation tree that you can use to access all components on that tab. An icon next to an folder indicates that the node or folder has subcomponents. Equipment Tab This tab contains a basic inventory of the equipment in the Cisco UCS domain. A system or server administrator can use this tab to access and manage the chassis, fabric interconnects, servers, and other hardware. A red, orange, or yellow rectangle around a device name indicate that the device has a fault. Cisco UCS Manager GUI Configuration Guide, Release 2.0 48 OL-25712-04 Overview of Cisco UCS Manager GUI The major nodes below the Equipment node in this tab are the following: • Chassis • Fabric Interconnects Servers Tab This tab contains the server-related components, such as service profiles, polices, and pools. A server administrator typically accesses and manages the components on this tab. The major nodes below the Servers node in this tab are the following: • Service Profiles • Service Profile Templates • Policies • Pools LAN Tab This tab contains the components related to LAN configuration, such as LAN pin groups, quality of service classes, VLANs, policies, pools, and the internal domain. A network administrator typically accesses and manages the components on this tab. The major nodes below the LAN node in this tab are the following: • LAN Cloud • Policies • Pools • Internal LAN Domains SAN Tab This tab contains the components related to SAN configuration, such as pin groups, VSANs, policies, and pools. A storage administrator typically accesses and manages the components on this tab. The major nodes below the SAN node in this tab are the following: • SAN Cloud • Policies • Pools VM Tab This tab contains the components required to configure VM-FEX for servers with a VIC adapter. For example, you use components on this tab to configure the connection between Cisco UCS Manager and VMware vCenter, to configure distributed virtual switches, port profiles, and to view the virtual machines hosted on servers in the Cisco UCS domain. The major node below the All node in this tab is the VMware node. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 49 Overview of Cisco UCS Manager GUI Admin Tab This tab contains system-wide settings, such as user manager and communication services, and troubleshooting components, such as faults and events. The system administrator typically accesses and manages the components on this tab. The major nodes below the All node in this tab are the following: • Faults, Events and Audit Log • User Management • Key Management • Communication Management • Stats Management • Timezone Management • Capability Catalog Toolbar The toolbar displays on the right side of Cisco UCS Manager GUI above the Work pane. You can use the menu buttons in the toolbar to perform common actions, including the following actions: • Navigate between previously viewed items in the Work pane • Create elements for the Cisco UCS domain • Set options for Cisco UCS Manager GUI • Access online help for Cisco UCS Manager GUI Work Pane The Work pane displays on the right side of Cisco UCS Manager GUI. This pane displays details about the component selected in the Navigation pane. The Work pane includes the following elements: • A navigation bar that displays the path from the main node of the tab in the Navigation pane to the selected element. You can click any component in this path to display that component in the Work pane. • A content area that displays tabs with information related to the component selected in the Navigation pane. The tabs displayed in the content area depends upon the selected component. You can use these tabs to view information about the component, create components, modify properties of the component, and examine a selected object. Status Bar The status bar displays across the bottom of Cisco UCS Manager GUI. The status bar provides information about the state of the application. Cisco UCS Manager GUI Configuration Guide, Release 2.0 50 OL-25712-04 Overview of Cisco UCS Manager GUI On the left, the status bar displays the following information about your current session in Cisco UCS Manager GUI: • A lock icon that indicates the protocol you used to log in. If the icon is locked, you connected with HTTPS and if the icon is unlocked, you connected with HTTP. • The username you used to log in. • The IP address of the server where you logged in. On the right, the status bar displays the system time. Table Customization Cisco UCS Manager GUI enables you to customize the tables on each tab. You can change the type of content that you view and filter the content. Table Customization Menu Button This menu button in the upper right of every table enables you to control and customize your view of the table. The drop-down menu for this button includes the following options: Menu Item Description Column Name The menu contains an entry for each column in the table. Click a column name to display or hide the column. Horizontal Scroll If selected, adds a horizontal scroll bar to the table. If not selected, when you widen one of the columns, all columns to the right narrow and do not scroll. Pack All Columns Resizes all columns to their default width. Pack Selected Column Resizes only the selected column to its default width. Table Content Filtering The Filter button above each table enables you to filter the content in the table according to the criteria that you set in the Filter dialog box. The dialog box includes the following filtering options: Name Description Disable option No filtering criteria is used on the content of the column. This is the default setting. Equal option Displays only that content in the column which exactly matches the value specified. Not Equal option Displays only that content in the column which does not exactly match the value specified. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 51 Overview of Cisco UCS Manager GUI Name Description Wildcard option The criteria you enter can include one of the following wildcards: • _ (underscore) or ? (question mark)—replaces a single character • % (percent sign) or * (asterisk)—replaces any sequence of characters Less Than option Displays only that content in the column which is less than the value specified. Less Than Or Equal option Displays only that content in the column which is less than or equal to the value specified. Greater Than option Displays only that content in the column which is greater than the value specified. Greater Than Or Equal option Displays only that content in the column which is greater than or equal to the value specified. LAN Uplinks Manager The LAN Uplinks Manager provides a single interface where you can configure the connections between Cisco UCS and the LAN. You can use the LAN Uplinks Manager to create and configure the following: • Ethernet switching mode • Uplink Ethernet ports • Port channels • LAN pin groups • Named VLANs • Server ports • QoS system classes Some of the configuration that you can do in the LAN Uplinks Manager can also be done in nodes on other tabs, such as the Equipment tab or the LAN tab. Internal Fabric Manager The Internal Fabric Manager provides a single interface where you can configure server ports for a fabric interconnect in a Cisco UCS domain. The Internal Fabric Manager is accessible from the General tab for that fabric interconnect. Some of the configuration that you can do in the Internal Fabric Manager can also be done in nodes on the Equipment tab, on the LAN tab, or in the LAN Uplinks Manager. Cisco UCS Manager GUI Configuration Guide, Release 2.0 52 OL-25712-04 Logging in to Cisco UCS Manager GUI through HTTPS Hybrid Display For each chassis in a Cisco UCS domain, Cisco UCS Manager GUI provides a hybrid display that includes both physical components and connections between the chassis and the fabric interconnects. This tab displays detailed information about the connections between the selected chassis and the fabric interconnects. It has an icon for the following: • Each fabric interconnect in the system • The I/O module (IOM) in the selected component, which is shown as an independent unit to make the connection paths easier to see • The selected chassis showing the servers and PSUs The lines between the icons represent the connections between the following: • DCE interface on each server and the associated server port on the IOM. These connections are created by Cisco and cannot be changed. • Server port on the IOM and the associated port on the fabric interconnect. You can change these connections if desired. You can mouse over the icons and lines to view tooltips identifying each component or connection, and you can double-click any component to view properties for that component. If there is a fault associated with the component or any of its subcomponents, Cisco UCS Manager GUI displays a fault icon on top of the appropriate component. If there are multiple fault messages, Cisco UCS Manager GUI displays the icon associated with the most serious fault message in the system. Logging in to Cisco UCS Manager GUI through HTTPS The default HTTPS web link for Cisco UCS Manager GUI is https://UCSManager_IP, where UCSManager_IP represents the IP address assigned to Cisco UCS Manager. This IP address can be one of the following: • Cluster configuration: UCSManager_IP represents the virtual or cluster IP address assigned to Cisco UCS Manager. Do not use the IP addresses assigned to the management port on the fabric interconnects. • Standalone configuration: UCSManager_IP represents the IP address for the management port on the fabric interconnect. Procedure Step 1 Step 2 In your web browser, type the Cisco UCS Manager GUI web link or select the bookmark in your browser. If a Security Alert dialog box appears, click Yes to accept the security certificate and continue. Step 3 In the Cisco UCS Manager launch page, click Launch UCS Manager. Depending upon the web browser you use to log in, you may be prompted to download or save the .JNLP file. Step 4 Step 5 If Cisco UCS Manager displays a pre-login banner, review the message and click OK to close the dialog box. If a Security dialog box displays, do the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 53 Logging in to Cisco UCS Manager GUI through HTTP a) (Optional) Check the check box to accept all content from Cisco. b) Click Yes to accept the certificate and continue. Step 6 In the Login dialog box, do the following: a) Enter your username and password. b) If your Cisco UCS implementation includes multiple domains, select the appropriate domain from the Domain drop-down list. c) Click Login. Logging in to Cisco UCS Manager GUI through HTTP The default HTTP web link for Cisco UCS Manager GUI is http://UCSManager_IP , where UCSManager_IP represents the IP address assigned to Cisco UCS Manager. This IP address can be one of the following: • Cluster configuration: UCSManager_IP represents the virtual or cluster IP address assigned to Cisco UCS Manager. Do not use the IP addresses assigned to the management port on the fabric interconnects. • Standalone configuration: UCSManager_IP represents the IP address for the management port on the fabric interconnect Procedure Step 1 Step 2 Step 3 In your web browser, type the Cisco UCS Manager GUI web link or select the bookmark in your browser. If Cisco UCS Manager displays a pre-login banner, review the message and click OK to close the dialog box. In the Cisco UCS Manager launch page, click Launch UCS Manager. Depending upon the web browser you use to log in, you may be prompted to download or save the .JNLP file. Step 4 In the Login dialog box, do the following: a) Enter your username and password. b) If your Cisco UCS implementation includes multiple domains, select the appropriate domain from the Domain drop-down list. c) Click Login. Logging Off Cisco UCS Manager GUI Procedure Step 1 In Cisco UCS Manager GUI, click Exit in the upper right. Cisco UCS Manager GUI Configuration Guide, Release 2.0 54 OL-25712-04 Web Session Limits Cisco UCS Manager GUI blurs on your screen to indicate that you cannot use it and displays the Exit dialog box. Step 2 From the drop-down list, select one of the following: • Exit to log out and shut down Cisco UCS Manager GUI. • Log Off to log out of Cisco UCS Manager GUI and log in a different user. Step 3 Click OK. 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. Setting the Web Session Limit for Cisco UCS Manager Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Communication Services. In the Work pane, click the Communication Services tab. Step 4 In the Web Session Limits area, complete the following fields: Name Description Maximum Sessions Per User field The maximum number of concurrent HTTP and HTTPS sessions allowed for each user. Enter an integer between 1 and 256. Maximum Sessions field The maximum number of concurrent HTTP and HTTPS sessions allowed for all users within the system. Enter an integer between 1 and 256. Step 5 Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 55 Pre-Login Banner 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 If the Pre-Login Banner area does not appear on the Banners tab, Cisco UCS Manager does not display a pre-login banner when users log in. If the Pre-Login Banner area does appear, you cannot create a second pre-login banner. You can only delete or modify the existing banner. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management. Click the User Services node. In the Work pane, click the Banners tab. Step 5 Step 6 In the Actions area, click Create Pre-Login Banner. In the Create Pre-Login Banner dialog box, click in the text field and enter the message that you want users to see when they log in to Cisco UCS Manager. You can enter any standard ASCII character in this field. Step 7 Click OK. Modifying the Pre-Login Banner Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management. Click the User Services node. In the Work pane, click the Banners tab. Step 5 Click in the text field in the Pre-Login Banner area and make the necessary changes to the text. You can enter any standard ASCII character in this field. Step 6 Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 56 OL-25712-04 Cisco UCS Manager GUI Properties Deleting the Pre-Login Banner Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management. Click the User Services node. In the Work pane, click the Banners tab. Step 5 Step 6 In the Actions area, click Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Properties Configuring the Cisco UCS Manager GUI Session and Log Properties These properties determine how Cisco UCS Manager GUI reacts to session interruptions and inactivity, and configures the Cisco UCS Manager GUI Java message logging. Procedure Step 1 In the toolbar, click Options to open the Properties dialog box. Step 2 Step 3 In the right pane, click Session. In the Session page, update one or more of the following fields: Name Description Automatically Reconnect check box If checked, the system tries to reconnect if communication between the GUI and the fabric interconnect is interrupted. GUI Inactivity Time Out drop-down list The number of minutes the system should wait before ending an inactive session. To specify that the session should not time out regardless of the length of inactivity, choose NEVER. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 57 Cisco UCS Manager GUI Properties Name Description Log Level drop-down list The amount of Java message logging done for Cisco UCS Manager GUI on the user's local machine. This can be one of the following: • All—All relevant Java information for the GUI is logged. There can be a maximum of 10 log files, each of which can be a maximum of 10 MB in size. Once the final file has been filled, Cisco UCS Manager deletes the oldest log file and starts a new one. • Off—Cisco UCS Manager does not create any Java log files for the GUI. Note Step 4 The log file location is determined by the Java runtime settings on the user's local machine. For more information, see the documentation for the version of Java that you are using. Max Log Size drop-down list The maximum size, in megabytes, that Cisco UCS Manager allocates to any of the logs it saves for this Cisco UCS domain. Reconnection Interval field If the Automatically Reconnect check box is checked, this is the number of seconds the system waits before trying to reconnect. Click OK. Configuring Properties for Confirmation Messages These properties determine whether or not Cisco UCS Manager GUI displays a confirmation message after configuration changes and other operations. Procedure Step 1 In the toolbar, click Options to open the Properties dialog box. Step 2 Step 3 In the right pane, click Confirmation Messages. In the Confirmation Messages page, complete the following fields: Name Description Confirm Deletion check box If checked, Cisco UCS Manager GUI requires that you confirm all delete operations. Confirm Discard Changes check If checked, Cisco UCS Manager GUI requires that you confirm before box the system discards any changes. Confirm Modification/Creation check box If checked, Cisco UCS Manager GUI requires that you confirm before the system modifies or creates objects. Cisco UCS Manager GUI Configuration Guide, Release 2.0 58 OL-25712-04 Cisco UCS Manager GUI Properties Step 4 Name Description Confirm Successful Operations check box If checked, Cisco UCS Manager GUI displays a confirmation when operations are successful. Click OK. Configuring Properties for External Applications Cisco UCS Manager GUI uses these properties to connect with external applications, such as SSH. Procedure Step 1 In the toolbar, click Options to open the Properties dialog box. Step 2 Step 3 In the right pane, click External Applications. In the External Applications page, complete the following fields: Step 4 Name Description SSH field The application to use for SSH processing. SSH Parameters field Any parameters to include in all SSH commands. Click OK. Customizing the Appearance of Cisco UCS Manager GUI These properties allow you to customize the some of the visual properties of Cisco UCS Manager GUI. Procedure Step 1 In the toolbar, click Options to open the Properties dialog box. Step 2 Step 3 In the right pane, click Visual Enhancements. In the Visual Enhancements page, update one or more of the following fields: Name Description Automatically Pack Table Columns check box If checked, Cisco UCS Manager GUI automatically resizes all table columns based on their contents. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 59 Determining the Acceptable Range of Values for a Field Name Description Max History Size field The number of tabs the system should store in memory for use with the Forward and Back toolbar buttons. Right Aligned Labels check box If checked, all labels are right-aligned with respect to one another. Otherwise all labels are left-aligned. Show Image while Dragging check box If checked, when you drag an object from one place to another, the GUI displays a transparent version of that object until you drop the object in its new location. Wizard Transition Effects check If checked, when you go to a new page in a wizard the first page fades box out and the new page fades in. Otherwise the page changes without a visible transition. Step 4 Click OK. Determining the Acceptable Range of Values for a Field Some properties have a restricted range of values that you can enter. You can use this procedure to determine that acceptable range for fields in a dialog box, window, or tab. You cannot use this procedure to determine the acceptable range of values for properties listed in a table or tree. Procedure Step 1 Step 2 Place your cursor in the field for which you want to check the range to give focus to that field. Press Alt + Shift + R. Cisco UCS Manager GUI displays the acceptable range of values for a few seconds. The range disappears if you click anywhere on the screen. Determining Where a Policy Is Used You can use this procedure to determine which service profiles and service profile templates are associated with the selected policy. Cisco UCS Manager GUI Configuration Guide, Release 2.0 60 OL-25712-04 Determining Where a Pool Is Used Procedure Step 1 In the Navigation pane, click the policy whose usage you want to view. Step 2 In the Work pane, click the General tab. Step 3 In the Actions area, click Show Policy Usage. Cisco UCS Manager GUI displays the Service Profiles/Templates dialog box that shows the associated service profiles and service profile templates. Determining Where a Pool Is Used You can use this procedure to determine which service profiles and service profile templates are associated with the selected pool. Procedure Step 1 In the Navigation pane, click the pool whose usage you want to view. Step 2 In the Work pane, click the General tab. Step 3 In the Actions area, click Show Pool Usage. Cisco UCS Manager GUI displays the Service Profiles/Templates dialog box that shows the associated service profiles and service profile templates. Copying the XML To assist you in developing scripts or creating applications with the XML API for Cisco UCS, Cisco UCS Manager GUI includes an option to copy the XML used to create an object in Cisco UCS Manager. This option is available on the right-click menu for most object nodes in the Navigation pane, such as the Port Profiles node or the node for a specific service profile. Procedure Step 1 In the Navigation pane, navigate to the object for which you want to copy the XML. Step 2 Step 3 Right-click on that object and choose Copy XML. Paste the XML into an XML editor, Notepad, or another application. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 61 Copying the XML Cisco UCS Manager GUI Configuration Guide, Release 2.0 62 OL-25712-04 PART II System Configuration • Configuring the Fabric Interconnects, page 65 • Configuring Ports and Port Channels, page 77 • Configuring Communication Services, page 113 • Configuring Authentication, page 131 • Configuring Organizations, page 155 • Configuring Role-Based Access Control, page 159 • Managing Firmware, page 183 • Configuring DNS Servers, page 237 • Configuring System-Related Policies, page 239 • Managing Licenses, page 247 • Managing Virtual Interfaces, page 259 CHAPTER 5 Configuring the Fabric Interconnects This chapter includes the following sections: • Initial System Setup, page 65 • Performing an Initial System Setup for a Standalone Configuration, page 67 • Initial System Setup for a Cluster Configuration, page 69 • Enabling a Standalone Fabric Interconnect for Cluster Configuration, page 72 • Ethernet Switching Mode, page 72 • Configuring Ethernet Switching Mode, page 73 • Fibre Channel Switching Mode, page 74 • Configuring Fibre Channel Switching Mode, page 74 • Changing the Properties of the Fabric Interconnects, page 75 • Determining the Leadership Role of a Fabric Interconnect, page 76 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 • Management port IP address and subnet mask • Default gateway IP address • DNS Server IP address Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 65 Initial System Setup • 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 may require a third-party tool to support data redundancy. To use the cluster configuration, the two fabric interconnects must be directly connected 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. This allows 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. The first fabric interconnect to be set up must be enabled for a cluster configuration. Then, when the second fabric interconnect is set up, it detects the first fabric interconnect as a peer fabric interconnect in the cluster. For more information, refer to the Cisco UCS 6100 Series Fabric Interconnect Hardware Installation Guide. Management Port IP Address In a standalone configuration, you must specify only one IP address and the subnet mask for the single management port on the fabric interconnect. In a cluster configuration, you must specify the following three IP addresses in the same subnet: • Management port IP address for fabric interconnect A • Management port IP address for fabric interconnect B • Cluster IP address Cisco UCS Manager GUI Configuration Guide, Release 2.0 66 OL-25712-04 Performing an Initial System Setup for a Standalone Configuration Performing an Initial System Setup for a Standalone Configuration Before You Begin 1 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. 2 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 3 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 IP address and subnet mask. • Default gateway IP address. • DNS server IP address (optional). • Domain name for the system (optional). Procedure Step 1 Step 2 Connect to the console port. Power on the fabric interconnect. You will see the power on self-test messages as the fabric interconnect boots. Step 3 Step 4 At the installation method prompt, enter gui. If the system cannot access a DHCP server, you are prompted to enter the following information: • IP address for the management port on the fabric interconnect • Subnet mask for the management port on the fabric interconnect • IP address for the default gateway assigned to the fabric interconnect Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 67 Performing an Initial System Setup for a Standalone Configuration Step 5 Step 6 Step 7 Copy the web link from the prompt into a supported web browser and go to the Cisco UCS Manager GUI launch page. On the Cisco UCS Manager GUI launch page, select Express Setup. On the Express Setup page, select Initial Setup and click Submit. Step 8 Step 9 In the Cluster and Fabric Setup Area, select the Standalone Mode option. In the System Setup Area, complete the following fields: Field Description System Name field The name assigned to the Cisco UCS domain. In a standalone configuration, the system adds "-A" to the system name. In a cluster configuration, the system adds "-A" to the fabric interconnect assigned to fabric A, and "-B" to the fabric interconnect assigned to fabric B. Admin Password field The password used for the Admin account on the fabric interconnect. Choose a strong password that meets the guidelines for Cisco UCS Manager passwords. This password cannot be blank. Confirm Admin Password field The password used for the Admin account on the fabric interconnect. Mgmt IP Address field The static IP address for the management port on the fabric interconnect. Mgmt IP Netmask field The subnet mask for the management port on the fabric interconnect. Default Gateway field The IP address for the default gateway assigned to the management port on the fabric interconnect. DNS Server IP field The IP address for the DNS server assigned to the fabric interconnect. Domain Name field The name of the domain in which the fabric interconnect resides. Step 10 Click Submit. A page displays the results of your setup operation. Cisco UCS Manager GUI Configuration Guide, Release 2.0 68 OL-25712-04 Initial System Setup for a Cluster Configuration Initial System Setup for a Cluster Configuration Performing an Initial System Setup on the First Fabric Interconnect Before You Begin 1 Verify the following physical connections on the 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. 2 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 3 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 IP 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 IP addresses. • Default gateway IP address. • DNS server IP address (optional). • Domain name for the system (optional). Procedure Step 1 Step 2 Connect to the console port. Power on the fabric interconnect. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 69 Initial System Setup for a Cluster Configuration You will see the power on self-test messages as the fabric interconnect boots. Step 3 Step 4 At the installation method prompt, enter gui. If the system cannot access a DHCP server, you are prompted to enter the following information: • IP address for the management port on the fabric interconnect • Subnet mask for the management port on the fabric interconnect • IP address for the default gateway assigned to the fabric interconnect Step 5 Step 6 Step 7 Copy the web link from the prompt into a web browser and go to the Cisco UCS Manager GUI launch page. On the Cisco UCS Manager GUI launch page, select Express Setup. On the Express Setup page, select Initial Setup and click Submit. Step 8 In the Cluster and Fabric Setup Area: a) Click the Enable Clustering option. b) For the Fabric Setup option, select Fabric A. c) In the Cluster IP Address field, enter the IP address that Cisco UCS Manager will use. Step 9 In the System Setup Area, complete the following fields: Field Description System Name field The name assigned to the Cisco UCS domain. In a standalone configuration, the system adds "-A" to the system name. In a cluster configuration, the system adds "-A" to the fabric interconnect assigned to fabric A, and "-B" to the fabric interconnect assigned to fabric B. Admin Password field The password used for the Admin account on the fabric interconnect. Choose a strong password that meets the guidelines for Cisco UCS Manager passwords. This password cannot be blank. Confirm Admin Password field The password used for the Admin account on the fabric interconnect. Mgmt IP Address field The static IP address for the management port on the fabric interconnect. Mgmt IP Netmask field The subnet mask for the management port on the fabric interconnect. Default Gateway field The IP address for the default gateway assigned to the management port on the fabric interconnect. DNS Server IP field The IP address for the DNS server assigned to the fabric interconnect. Cisco UCS Manager GUI Configuration Guide, Release 2.0 70 OL-25712-04 Initial System Setup for a Cluster Configuration Field Description Domain Name field The name of the domain in which the fabric interconnect resides. Step 10 Click Submit. A page displays the results of your setup operation. Performing an Initial System Setup on the Second Fabric Interconnect Before You Begin You must ensure the following: • A console port on the second fabric interconnect is physically connected to a computer terminal or console server • You know the password for the admin account on the first fabric interconnect that you configured. Procedure Step 1 Step 2 Connect to the console port. Power on the fabric interconnect. You will see the power on self-test messages as the fabric interconnect boots. Step 3 Step 4 At the installation method prompt, enter gui. If the system cannot access a DHCP server, you are prompted to enter the following information: • IP address for the management port on the fabric interconnect • Subnet mask for the management port on the fabric interconnect • IP address for the default gateway assigned to the fabric interconnect Step 5 Step 6 Step 7 Copy the web link from the prompt into a web browser and go to the Cisco UCS Manager GUI launch page. On the Cisco UCS Manager GUI launch page, select Express Setup. On the Express Setup page, select Initial Setup and click Submit. The fabric interconnect should detect the configuration information for the first fabric interconnect. Step 8 In the Cluster and Fabric Setup Area: a) Select the Enable Clustering option. b) For the Fabric Setup option, make sure Fabric B is selected. Step 9 In the System Setup Area, enter the password for the Admin account into the Admin Password of Master field. Step 10 Click Submit. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 71 Enabling a Standalone Fabric Interconnect for Cluster Configuration A page displays the results of your setup operation. 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 address of the cluster, and then add the second fabric interconnect to the cluster. Procedure Command or Action Purpose Step 1 UCS-A# connect local-mgmt Enters local management mode. Step 2 UCS-A(local-mgmt) # enable Enables cluster operation on the standalone fabric interconnect with the specified IP address. When you enter this command, cluster virtual-ip-addr you are prompted to confirm that you want to enable cluster operation. Type yes to confirm. The IP address must be the virtual IP 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 IP 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. 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. 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 server (hosts) connected to it through vNICs. This is achieved by pinning (either dynamically pinned or hard pinned) vNICs to uplink ports, which provides redundancy toward the network, and makes the uplink ports appear as server ports to the rest of the fabric. When in end-host mode, the fabric interconnect does not run the Spanning Tree Protocol (STP) and avoids loops by denying uplink ports from forwarding traffic to each other, and by Cisco UCS Manager GUI Configuration Guide, Release 2.0 72 OL-25712-04 Configuring Ethernet Switching Mode 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 L2 aggregation • Virtual Switching System (VSS) aggregation layer Note When end-host mode is enabled, if a vNIC is hard pinned to an uplink port and this uplink port goes down, the system cannot re-pin the vNIC, and the vNIC remains down. 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 sequentially. The second fabric interconnect can take several minutes to complete the change in Ethernet switching mode and become system ready. The configuration is retained. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. In the Work pane, click the General tab. Step 4 In the Actions area of the General tab, click one of the following links: • Set Ethernet Switching Mode • Set Ethernet End-Host Mode Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 73 Fibre Channel Switching Mode The link for the current mode is dimmed. Step 5 In the dialog box, click Yes. Cisco UCS Manager restarts the fabric interconnect, logs you out, and disconnects Cisco UCS Manager GUI. 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 server (hosts) connected to it through vHBAs. This 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 NPV mode. This is the default Fibre Channel Switching mode. Note When end-host mode is enabled, if a vHBA is hard pinned to a uplink Fibre Channel port and this uplink port goes down, the system cannot re-pin 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 system connected directly to storage), or where a SAN exists (with an upstream MDS). Note In Fibre Channel switch mode, SAN pin groups are irrelevant. Any existing SAN pin groups will be ignored. Switch mode is not the default Fibre Channel switching mode. Configuring Fibre Channel Switching Mode Important When you change the Fibre Channel switching mode, Cisco UCS Manager logs you out and restarts the fabric interconnect. For a cluster configuration, Cisco UCS Manager restarts both fabric interconnects sequentially. The second fabric interconnect can take several minutes to complete the change in Fibre Channel switching mode and become system ready. Cisco UCS Manager GUI Configuration Guide, Release 2.0 74 OL-25712-04 Changing the Properties of the Fabric Interconnects Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. In the Work pane, click the General tab. Step 4 In the Actions area of the General tab, click one of the following links: • Set Fibre Channel Switching Mode • Set Fibre Channel End-Host Mode The link for the current mode is dimmed. Step 5 In the dialog box, click Yes. Cisco UCS Manager restarts the fabric interconnect, logs you out, and disconnects Cisco UCS Manager GUI. Changing the Properties of the Fabric Interconnects Note To change the subnet for a Cisco UCS domain, you must simultaneously change all subnets, the virtual IP address used to access Cisco UCS Manager, and the IP addresses for all fabric interconnects. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, click All. In the Work pane, click the General tab. Step 4 In the Actions area, click Management Interfaces to open the Management Interfaces dialog box. Step 5 To change only the virtual IP address that you use to access Cisco UCS Manager, enter the desired IP address in the IP Address field in the Virtual IP area. To change only the name assigned to the Cisco UCS domain, enter the desired name in the Name field in the Virtual IP area. To change the subnet, IP address, and default gateway assigned to the fabric interconnects, update the following fields: a) In the Virtual IP area, change the IP address used to access Cisco UCS Manager in the IP Address field. b) In the Fabric Interconnect area for each fabric interconnect, update the following fields: Step 6 Step 7 Name Description IP Address field The IP address to use when communicating with the fabric interconnect. Subnet Mask field The associated subnet mask. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 75 Determining the Leadership Role of a Fabric Interconnect Step 8 Step 9 Name Description Default Gateway field The associated gateway. Click OK. Log out of Cisco UCS Manager GUI and log back in again to see your changes. Determining the Leadership Role of a Fabric Interconnect Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 In the Equipment tab, expand Equipment > Fabric Interconnects. Click the fabric interconnect for which you want to identify the role. In the Work pane, click the General tab. Step 5 Step 6 In the General tab, click the down arrows on the High Availability Details bar to expand that area. View the Leadership field to determine whether the fabric interconnect is the primary or subordinate. Cisco UCS Manager GUI Configuration Guide, Release 2.0 76 OL-25712-04 CHAPTER 6 Configuring Ports and Port Channels This chapter includes the following sections: • Server and Uplink Ports on the 6100 Series Fabric Interconnect, page 77 • Unified Ports on the 6200 Series Fabric Interconnect, page 78 • Server Ports, page 85 • Uplink Ethernet Ports, page 85 • Reconfiguring a Port on a Fabric Interconnect, page 86 • Enabling a Port on a Fabric Interconnect, page 87 • Disabling a Port on a Fabric Interconnect, page 88 • Unconfiguring a Port on a Fabric Interconnect, page 89 • Appliance Ports, page 89 • FCoE and Fibre Channel Storage Ports, page 94 • Uplink Ethernet Port Channels, page 97 • Appliance Port Channels, page 100 • Fibre Channel Port Channels, page 104 • Adapter Port Channels, page 108 • Fabric Port Channels, page 108 • Configuring Server Ports with the Internal Fabric Manager, page 111 Server and Uplink Ports on the 6100 Series Fabric Interconnect Each 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 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. You need to create LAN pin groups and SAN pin groups to pin traffic from servers to an uplink port. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 77 Unified Ports on the 6200 Series Fabric Interconnect Note Ports on the 6100 series fabric interconnect are not unified. For more information on Unified Ports, see Unified Ports on the 6200 Series 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. Unified Ports on the 6200 Series Fabric Interconnect Unified ports are ports on the 6200 series fabric interconnect that can be configured to carry either Ethernet or Fibre Channel traffic. These ports are not reserved. They cannot be used by a Cisco UCS domain until you configure them. 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. The port mode is not automatically discovered by the fabric interconnect; it is configured in Cisco UCS Manager. Cisco UCS Manager GUI Configuration Guide, Release 2.0 78 OL-25712-04 Unified Ports on the 6200 Series Fabric Interconnect Changing the port mode results in the existing port configuration being deleted and replaced by a new logical port. Any objects associated with that port configuration, such as VLANs and VSANS, are removed. There is no restriction on the number of times the port mode can be changed for a unified port. Port Types The port type defines the type of traffic carried over a unified port connection. 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. By default, unified ports changed to Ethernet port mode are set to uplink Ethernet port type. unified ports changed to Fibre Channel port mode are set to the Fibre Channel uplink port type. Fibre Channel ports cannot be unconfigured. Changing the port type does not require a reboot. When the port mode is set to Ethernet, you can configure the following port types: • Server ports • Ethernet uplink ports • Ethernet port channel members • FCoE ports • Appliance ports • Appliance port channel members • SPAN destination ports • SPAN source ports Note For SPAN source ports, configure one of the port types and then configure the port as SPAN source. When the port mode is set to Fibre Channel, you can configure the following port types: • Fibre Channel uplink ports • Fibre Channel port channel members • Fibre Channel storage ports • SPAN destination ports • SPAN source ports Note For SPAN source ports, configure one of the port types and then configure the port as SPAN source. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 79 Unified Ports on the 6200 Series Fabric Interconnect 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. The Beacon LED property can be configured 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, the Beacon LED property may be reset 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. 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. Cisco UCS Manager GUI Configuration Guide, Release 2.0 80 OL-25712-04 Unified Ports on the 6200 Series Fabric Interconnect 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. 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. 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. However, 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. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 81 Unified Ports on the 6200 Series Fabric Interconnect Configuring Port Modes for a 6248 Fabric Interconnect 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. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. In the Work pane, click the General tab. Step 4 Step 5 In the Actions area of the General tab, click Configure Unified Ports. Review the confirmation message and click one of the following: • Yes—To continue with configuring the port mode. • No—To exit without configuring the port mode and wait for an appropriate maintenance window. Step 6 Click one of the following buttons to choose the module for which you want to configure the port modes: • Configure Fixed Module • Configure Expansion Module Step 7 Use your mouse to drag the slider along the bar until the displays shows the port mode configuration that you want for the module. If you change the port mode for a previously configured port, the port returns to an unconfigured state. Step 8 Step 9 If you need to configure port modes for the other module, repeat Steps 6 and 7. Click Finish to save your port mode configuration. Depending upon 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. 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. Cisco UCS Manager GUI Configuration Guide, Release 2.0 82 OL-25712-04 Unified Ports on the 6200 Series Fabric Interconnect What to Do Next Configure the port types for the ports. You can right-click on any port in the module display above the slider and configure that port for an available port type. Configuring Port Modes for a 6296 Fabric Interconnect 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. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. In the Work pane, click the General tab. Step 4 Step 5 In the Actions area of the General tab, click Configure Unified Ports. Review the confirmation message and click one of the following: • Yes—To open the Configure Unified Ports wizard and continue with configuring the port mode. • No—To exit without configuring the port mode and wait for an appropriate maintenance window. Step 6 On the Configure Fixed Module Ports page, do the following: a) Use your mouse to drag the slider along the bar until the displays shows the port mode configuration that you want for the fixed module. b) If you want to configure the port type for a port, right-click on any port in the module display above the slider and configure that port for an available port type. c) Do one of the following: • Click Next to configure the port mode for ports in expansion module 1. • If you do not wish to configure the port mode for ports on the expansion modules, continue with Step 9. If you change the port mode for a previously configured port, the port returns to an unconfigured state. Step 7 On the Configure Expansion Module 1 Ports page, do the following: a) Use your mouse to drag the slider along the bar until the displays shows the port mode configuration that you want for the expansion module. b) If you want to configure the port type for a port, right-click on any port in the module display above the slider and configure that port for an available port type. c) Do one of the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 83 Unified Ports on the 6200 Series Fabric Interconnect • Click Next to configure the port mode for ports in expansion module 2. • If you do not wish to configure the port mode for ports on the remaining expansion modules, continue with Step 9. If you change the port mode for a previously configured port, the port returns to an unconfigured state. Step 8 Step 9 If you need to configure port modes for expansion module 3, repeat Step 7. Click Finish to save your port mode configuration. Depending upon 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. 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. 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 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. Depending upon the location of the unified ports for which you want to configure the beacon LEDs, click on one of the following: • Fixed Module • Expansion Module Step 4 In the Work pane, click the General tab. Step 5 In the Properties area, click one of the following radio buttons in the Beacon LED field: • Off—All physical LEDs are off. • Eth—The physical LEDs next to all Ethernet ports are on. • Fc—The physical LEDs next to all Fibre Channel ports are on. Step 6 Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 84 OL-25712-04 Server Ports Server Ports Configuring Server Ports You can only configure server ports on the fixed port module. Expansion modules do not include server ports. This task describes only one method of configuring ports. You can also configure ports from a right-click menu, from the General tab for the port, or in the LAN Uplinks Manager. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 In the Equipment tab, expand Fabric Interconnects > Fabric_Interconnect_Name > Fixed Module > Unconfigured Ports. Click one or more ports under the Unconfigured Ports node. Drag the selected port or ports and drop them in the Server Ports node. The port or ports are configured as server ports, removed from the list of unconfigured ports, and added to the Server Ports node. Step 3 Step 4 Uplink Ethernet Ports Configuring Uplink Ethernet Ports You can configure uplink Ethernet ports on either the fixed module or an expansion module. This task describes only one method of configuring uplink Ethernet ports. You can also configure uplink Ethernet ports from a right-click menu or from the General tab for the port. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. Depending upon the location of the ports you want to configure, expand one of the following: • Fixed Module • Expansion Module Step 4 Click one or more of the ports under the Unconfigured Ethernet Ports node. If you want to reconfigure a server port, appliance port, or FCoE storage port, expand the appropriate node. Step 5 Drag the selected port or ports and drop them in the Uplink Ethernet Ports node. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 85 Reconfiguring a Port on a Fabric Interconnect The port or ports are configured as uplink Ethernet ports, removed from the list of unconfigured ports, and added to the Uplink Ethernet Ports node. What to Do Next If desired, change the properties for the default flow control policy and admin speed of the uplink Ethernet port. Changing the Properties of an Uplink Ethernet Port Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. Depending upon the location of the ports you want to configure, expand one of the following: • Fixed Module • Expansion Module Step 4 Step 5 In the Uplink Ethernet Ports node, click the uplink Ethernet port that you want to change. In the Work pane, click the General tab. Step 6 Step 7 In the Actions area, click Show Interface. In the Properties dialog box, complete the following fields: a) (Optional) In the User Label field, enter a label to identify the port. b) From the Flow Control Policy drop-down list, select a flow control policy to determine how the port sends and receives IEEE 802.3x pause frames when the receive buffer fills. c) In the Admin Speed field, click one of the following radio buttons: • 1Gbps • 10Gbps Step 8 Click OK. Reconfiguring a Port on a Fabric Interconnect Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. Depending upon the location of the ports you want to reconfigure, expand one of the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 86 OL-25712-04 Enabling a Port on a Fabric Interconnect • Fixed Module • Expansion Module Step 4 Step 5 Click the port or ports you want to reconfigure. Drag the selected port or ports and drop them in the appropriate node. The port or ports are reconfigured as the appropriate type of port, removed from the original node, and added to the new node. Example: Reconfiguring an Uplink Ethernet Port as a Server Port 1 Expand the Uplink Ethernet Ports node and select the port you want to reconfigure. 2 Drag the port and drop it into the Server Ports node. Enabling a Port on a Fabric Interconnect After you enable or disable a port on a fabric interconnect, wait for at least 1 minute before you reacknowledge the chassis. If you reacknowledge the chassis too soon, the pinning of server traffic from the chassis may not be updated with the changes to the port that you enabled or disabled. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. Depending upon the location of the ports you want to enable, expand one of the following: • Fixed Module • Expansion Module Step 4 Depending upon the type of port you want to enable, expand one of the following: • Appliance Ports • FCoE Storage Ports • Server Ports • Storage FC Ports • Uplink Ethernet Ports • Uplink FC Ports Step 5 Click the port or ports you want to enable. You can use the Shift key or Ctrl key to select multiple entries. Step 6 Right-click the selected port or ports and choose Enable. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 87 Disabling a Port on a Fabric Interconnect The port or ports are enabled. Data traffic can begin to travel through them. Disabling a Port on a Fabric Interconnect After you enable or disable a port on a fabric interconnect, wait for at least 1 minute before you reacknowledge the chassis. If you reacknowledge the chassis too soon, the pinning of server traffic from the chassis may not be updated with the changes to the port that you enabled or disabled. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. Depending upon the location of the ports you want to disable, expand one of the following: • Fixed Module • Expansion Module Step 4 Depending upon the type of port you want to disable, expand one of the following: • Appliance Ports • FCoE Storage Ports • Server Ports • Storage FC Ports • Uplink Ethernet Ports • Uplink FC Ports Step 5 Click the port or ports you want to disable. You can use the Shift key or Ctrl key to select multiple entries. Step 6 Right-click the selected port or ports and choose Disable. The port or ports are disabled. No data traffic can travel through them. Cisco UCS Manager GUI Configuration Guide, Release 2.0 88 OL-25712-04 Unconfiguring a Port on a Fabric Interconnect Unconfiguring a Port on a Fabric Interconnect Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. Depending upon the location of the ports you want to unconfigure, expand one of the following: • Fixed Module • Expansion Module Step 4 Depending upon the type of port you want to unconfigure, expand one of the following: • Appliance Ports • FCoE Storage Ports • Server Ports • Storage FC Ports • Uplink Ethernet Ports • Uplink FC Ports Step 5 Click the port or ports you want to unconfigure. You can use the Shift key or Ctrl key to select multiple entries. Step 6 Right-click the selected port or ports and choose Unconfigure node. The port or ports are unconfigured, removed from the original node, and added to the Unconfigured Ports node. Appliance Ports Appliance ports are only used to connect fabric interconnects to directly attached NFS storage. Configuring an Appliance Port You can configure Appliance ports on either the fixed module or an expansion module. This task describes only one method of configuring appl ports. You can also configure appliance ports from the General tab for the port. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 89 Appliance Ports Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. Depending upon the location of the ports you want to configure, expand one of the following: • Fixed Module • Expansion Module Step 4 Click one or more of the ports under the Unconfigured Ethernet Ports node. If you want to reconfigure a server port, uplink Ethernet port, or FCoE storage port, expand the appropriate node. Step 5 Step 6 Step 7 Right-click the selected port or ports and choose Configure as Appliance Port. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. In the Configure as Appliance Port dialog box, complete the following fields: Name Description Priority drop-down list The quality of service setting associated with this interface. This can be one of the following: • Fc—Use this priority for vHBA traffic only. • Platinum—Use this priority for vNIC traffic only. • Gold—Use this priority for vNIC traffic only. • Silver—Use this priority for vNIC traffic only. • Bronze—Use this priority for vNIC traffic only. • Best Effort—Do not use this priority. It is reserved for the Basic Ethernet traffic lane. Pin Group drop-down list The LAN pin group that you want to use as the appliance pin target to the specified fabric and port, or fabric and port channel. Create LAN Pin Group link Click this link if you want to create a LAN pin group. Network Control Policy drop-down list The network control policy associated with this port. Create Network Control Policy link Click this link if you want to create a LAN pin group. Cisco UCS Manager GUI Configuration Guide, Release 2.0 90 OL-25712-04 Appliance Ports Name Description Admin Speed field The data transfer rate for the port, which should match the destination to which the port is linked. This can be one of the following: • 1 Gbps • 10 Gbps • 20 Gbps • 40 Gbps Note Step 8 The admin speed can be changed only for certain ports, and not all speeds are available on all systems. For more information, see the Hardware Installation Guide for your fabric interconnect. In the VLANs area, do the following: a) In the Port Mode field, click one of the following radio buttons to select the mode you want to use for the port channel: • Trunk—Cisco UCS Manager GUI displays the VLANs Table that lets you choose the VLANs you want to use. • Access—Cisco UCS Manager GUI displays the Select VLAN drop-down list that allows you to choose a VLAN to associate with this port channel. With either mode, you can click the Create VLAN link to create a new VLAN. b) If you clicked the Trunk radio button, complete the following fields in the VLANs table: Name Description Select column Check the check box in this column for each VLAN you want to use. Name column The name of the VLAN. Native VLAN column To designate one of the VLANs as the native VLAN, click the radio button in this column. c) If you clicked the access radio button, choose a VLAN from the Select VLAN drop-down list. Step 9 (Optional) If you want to add an endpoint, check the Ethernet Target Endpoint check box and complete the following fields: Name Description Name field The name of the endpoint. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 91 Appliance Ports Name Description MAC Address field The MAC address for the endpoint. Step 10 Click OK. The port or ports are configured as Appliance ports, removed from the list of unconfigured ports, and added to the Appliance Ports node. Modifying the Properties of an Appliance Port Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. Depending upon the location of the appliance port you want to modify, expand one of the following: • Fixed Module • Expansion Module Step 4 Step 5 Step 6 Expand Appliance Ports. Click the appliance port for which you want to modify the properties. In the Work pane, click the General tab. Step 7 In the Actions area, click Show Interface. You may need to expand or use the scroll bars in the Properties dialog box to see all the fields. Step 8 In the Properties dialog box, modify the values in one or more of the following fields: Name Description User Label field A user-defined name that can be used for internal tracking or customized identification. Enter up to 32 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Cisco UCS Manager GUI Configuration Guide, Release 2.0 92 OL-25712-04 Appliance Ports Name Description Admin Speed field The data transfer rate for the port, which should match the destination to which the port is linked. This can be one of the following: • 1 Gbps • 10 Gbps • 20 Gbps • 40 Gbps Note Priority drop-down list The admin speed can be changed only for certain ports, and not all speeds are available on all systems. For more information, see the Hardware Installation Guide for your fabric interconnect. The quality of service setting associated with this interface. This can be one of the following: • Fc—Use this priority for vHBA traffic only. • Platinum—Use this priority for vNIC traffic only. • Gold—Use this priority for vNIC traffic only. • Silver—Use this priority for vNIC traffic only. • Bronze—Use this priority for vNIC traffic only. • Best Effort—Do not use this priority. It is reserved for the Basic Ethernet traffic lane. Pin Group drop-down list The LAN pin group that you want to use as the appliance pin target to the specified fabric and port, or fabric and port channel. Network Control Policy drop-down list The network control policy associated with this port. MAC Address field The MAC address for the endpoint. If you do not see this field, the port does not have an Ethernet target endpoint set. Click Add Ethernet Target Endpoint in the Actions area to add an endpoint. Port Mode field The fields displayed in this area depend on the setting of the Port Mode field. If you choose: • Trunk—Cisco UCS Manager GUI displays the VLANs Table that lets you choose the VLANs you want to use. • Access—Cisco UCS Manager GUI displays the Select VLAN drop-down list that allows you to choose a VLAN to associate with this port channel. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 93 FCoE and Fibre Channel Storage Ports Step 9 Click OK. FCoE and Fibre Channel Storage Ports Configuring an FCoE Storage Port You can configure FCoE storage ports on either the fixed module or an expansion module. This task describes only one method of configuring FCoE storage ports. You can also configure FCoE storage ports from the General tab for the port. Before You Begin The Fibre Channel switching mode must be set to Switching for these ports to be valid. The storage ports cannot function in end-host mode. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. Depending upon the location of the ports you want to configure, expand one of the following: • Fixed Module • Expansion Module Step 4 Click one or more of the ports under the Unconfigured Ethernet Ports node. If you want to reconfigure an uplink Ethernet port, server port, or appliance port, expand the appropriate node. Step 5 Step 6 Step 7 Right-click the selected port or ports and choose Configure as FCoE Storage Port. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click OK. The port or ports are configured as FCoE storage ports, removed from the list of unconfigured ports, and added to the FCoE Storage Ports node. Configuring a Fibre Channel Storage Port This task describes only one method of configuring FC storage ports. You can also configure FC storage ports from the General tab for the port. Cisco UCS Manager GUI Configuration Guide, Release 2.0 94 OL-25712-04 FCoE and Fibre Channel Storage Ports Before You Begin The Fibre Channel switching mode must be set to Switching for these ports to be valid. The storage ports cannot function in end-host mode. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. Expand the Expansion Module node. Click one or more of the ports under the Uplink FC Ports node. Right-click the selected port or ports and choose Configure as FC Storage Port. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click OK. The port or ports are configured as FC storage ports, removed from the list of uplink FC ports, and added to the Storage FC Ports node. Restoring an Uplink Fibre Channel Port This task describes only one method of restoring an FC storage port to function as an uplink FC port. You can also reconfigure FC storage ports from the General tab for the port. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. Expand the Expansion Module node. Click one or more of the ports under the Storage FC Ports node. Right-click the selected port or ports and choose Configure as FC Uplink Port. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click OK. The port or ports are configured as uplink FC ports, removed from the list of FC storage ports, and added to the Uplink FC Ports node. Default Zoning Zoning allows you to set up access control between hosts and storage devices. When a zone is configured or the configuration is updated, this information is propagated to all the other switches in the fabric. In Cisco UCS, the zoning configuration is inherited from an upstream switch. You cannot configure zoning or view information about your zoning configuration through Cisco UCS Manager. The only configurable Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 95 FCoE and Fibre Channel Storage Ports zoning option in Cisco UCS Manager is whether the default zone in a VSAN (nodes not assigned to any zone) permits or denies access among its members. When default zoning is enabled, all traffic is permitted among members of the default zone. When default zoning is disabled, all traffic is denied among members of the default zone. Default zoning is applied on a per-VSAN basis. You cannot enable default zoning at the fabric level. Note Default zoned configurations are not recommended for production deployments, which must always use direct connect Fibre Channel topologies with upstream MDS or Nexus 5000 switches. Enabling Default Zoning Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 In the SAN tab, click the SAN node. In the Work pane, click the VSANs tab. Step 4 Click one of the following subtabs, depending upon the type of VSAN for which you want to enable default zoning: Subtab Description All Displays all VSANs in the Cisco UCS domain. Dual Mode Displays the VSANs that are accessible to both fabric interconnects. Switch A Displays the VSANs that are accessible to only fabric interconnect A. Switch B Displays the VSANs that are accessible to only fabric interconnect B. Step 5 In the table, double-click the VSAN. Cisco UCS Manager GUI displays the General tab for the VSAN. Step 6 Step 7 In the Actions area, click Enable Default Zoning. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 96 OL-25712-04 Uplink Ethernet Port Channels Disabling Default Zoning Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 In the SAN tab, click the SAN node. In the Work pane, click the VSANs tab. Step 4 Click one of the following subtabs, depending upon the type of VSAN for which you want to disable default zoning: Subtab Description All Displays all VSANs in the Cisco UCS domain. Dual Mode Displays the VSANs that are accessible to both fabric interconnects. Switch A Displays the VSANs that are accessible to only fabric interconnect A. Switch B Displays the VSANs that are accessible to only fabric interconnect B. Step 5 In the table, double-click the VSAN. Cisco UCS Manager GUI displays the General tab for the VSAN. Step 6 Step 7 In the Actions area, click Disable Default Zoning. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. 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 eight uplink Ethernet ports to a port channel. 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 GUI Configuration Guide, Release 2.0 OL-25712-04 97 Uplink Ethernet Port Channels Creating an Uplink Ethernet Port Channel Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 Step 5 On the LAN tab, expand LAN > LAN Cloud. Expand the node for the fabric interconnect where you want to add the port channel. Right-click the Port Channels node and choose Create Port Channel. In the Set Port Channel Name page of the Create Port Channel wizard, do the following: a) Complete the following fields: Name Description ID field The identifier for the port channel. Enter an integer between 1 and 256. This ID cannot be changed after the port channel has been saved. Name field A user-defined name for the port channel. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. b) Click Next. Step 6 In the Add Ports page of the Create Port Channel wizard, do the following: a) In the Ports table, choose one or more ports to include in the port channel. b) Click the >> button to add the ports to the Ports in the port channel table. You can use the << button to remove ports from the port channel. Note Step 7 Cisco UCS Manager warns you if you select a port that has been configured as a server port. You can click Yes in the dialog box to reconfigure that port as an uplink Ethernet port and include it in the port channel. Click Finish. Cisco UCS Manager GUI Configuration Guide, Release 2.0 98 OL-25712-04 Uplink Ethernet Port Channels Enabling an Uplink Ethernet Port Channel Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 Step 5 Step 6 On the LAN tab, expand LAN > LAN Cloud. Expand the node for the fabric interconnect that includes the port channel you want to enable. Expand the Port Channels node. Right-click the port channel you want to enable and choose Enable Port Channel. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Disabling an Uplink Ethernet Port Channel Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 Step 5 On the LAN tab, expand LAN > LAN Cloud. Expand the node for the fabric interconnect that includes the port channel you want to disable. Expand the Port Channels node. Right-click the port channel you want to disable and choose Enable Port Channel. Adding Ports to and Removing Ports from an Uplink Ethernet Port Channel Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 On the LAN tab, expand LAN > LAN Cloud > Fabric > Port Channels. Click the port channel to which you want to add or remove ports. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Add Ports. In the Add Ports dialog box, do one of the following: • To add ports, choose one or more ports in the Ports table, and then click the >> button to add the ports to the Ports in the port channel table. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 99 Appliance Port Channels • To remove ports, choose one or more ports in the Ports in the port channel table, and then click the << button to remove the ports from the port channel and add them to the Ports table. Step 7 Click OK. Deleting an Uplink Ethernet Port Channel Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 Step 5 Step 6 On the LAN tab, expand LAN > LAN Cloud. Expand the node for the fabric interconnect where you want to delete the port channel. Click the Port Channels node. In the General tab for the Port Channels node, choose the port channel you want to delete. Right-click the port channel and choose Delete. 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. Creating an Appliance Port Channel Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 Step 5 On the LAN tab, expand LAN > Appliances. Expand the node for the fabric interconnect where you want to add the port channel. Right-click the Port Channels node and choose Create Port Channel. In the Set Port Channel Name page of the Create Port Channel wizard, complete the following fields to specify the identity and other properties of the port channel: Name Description ID field The unique identifier of the port channel. Enter an integer between 1 and 256. This ID cannot be changed after the port channel has been saved. Cisco UCS Manager GUI Configuration Guide, Release 2.0 100 OL-25712-04 Appliance Port Channels Name Description Name field A user-defined name for the port channel. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Priority drop-down list The quality of service setting associated with this interface. This can be one of the following: • Fc—Use this priority for vHBA traffic only. • Platinum—Use this priority for vNIC traffic only. • Gold—Use this priority for vNIC traffic only. • Silver—Use this priority for vNIC traffic only. • Bronze—Use this priority for vNIC traffic only. • Best Effort—Do not use this priority. It is reserved for the Basic Ethernet traffic lane. Protocol field The protocol for the port channel. This can be one of the following: • Static • Lacp Step 6 Create LAN Pin Group link Click this link to create a LAN pin group. Network Control Policy drop-down list The network control policy that vNICs created from this vNIC template should use. Create Network Control Policy link Click this link to create a global network control policy that will be available to all port channels. In the VLANs area, do the following: a) In the Port Mode field, click one of the following radio buttons to select the mode you want to use for the port channel: • Trunk—Cisco UCS Manager GUI displays the VLANs Table that lets you choose the VLANs you want to use. • Access—Cisco UCS Manager GUI displays the Select VLAN drop-down list that allows you to choose a VLAN to associate with this port channel. With either mode, you can click the Create VLAN link to create a new VLAN. b) If you clicked the Trunk radio button, complete the following fields in the VLANs table: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 101 Appliance Port Channels Name Description Select column Check the check box in this column for each VLAN you want to use. Name column The name of the VLAN. Native VLAN column To designate one of the VLANs as the native VLAN, click the radio button in this column. c) If you clicked the access radio button, choose a VLAN from the Select VLAN drop-down list. Step 7 (Optional) If you want to add an endpoint, check the Ethernet Target Endpoint check box and complete the following fields: Name Description Name field The name of the endpoint. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. MAC Address field Step 8 Step 9 The MAC address for the endpoint. Click Next. In the Add Ports page of the Create Port Channel wizard, do the following: a) In the Ports table, choose one or more ports to include in the port channel. b) Click the >> button to add the ports to the Ports in the port channel table. You can use the << button to remove ports from the port channel. Note Cisco UCS Manager warns you if your configuration could cause issues with service profiles or port configurations. You can click Yes in the dialog box if you want to create the port channel despite those potential issues. Step 10 Click Finish. Cisco UCS Manager GUI Configuration Guide, Release 2.0 102 OL-25712-04 Appliance Port Channels Enabling an Appliance Port Channel Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 Step 5 Step 6 On the LAN tab, expand LAN > Appliances. Expand the node for the fabric interconnect that includes the port channel you want to enable. Expand the Port Channels node. Right-click the port channel you want to enable and choose Enable Port Channel. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Disabling an Appliance Port Channel Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 Step 5 Step 6 On the LAN tab, expand LAN > Appliances. Expand the node for the fabric interconnect that includes the port channel you want to disable. Expand the Port Channels node. Right-click the port channel you want to disable and choose Disable Port Channel. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Adding Ports to and Removing Ports from an Appliance Port Channel Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 On the LAN tab, expand LAN > Appliances > Fabric > Port Channels. Click the port channel to which you want to add or remove ports. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Add Ports. In the Add Ports dialog box, do one of the following: • To add ports, choose one or more ports in the Ports table, and then click the >> button to add the ports to the Ports in the port channel table. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 103 Fibre Channel Port Channels • To remove ports, choose one or more ports in the Ports in the port channel table, and then click the << button to remove the ports from the port channel and add them to the Ports table. Step 7 Click OK. Deleting an Appliance Port Channel Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 Step 5 Step 6 On the LAN tab, expand LAN > Appliances. Expand the node for the fabric interconnect that includes the port channel you want to enable. Expand the Port Channels node. Right-click the port channel you want to enable and choose Disable Port Channel. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. 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. You can create up to four Fibre Channel port channels in each Cisco UCS domain. Each Fibre Channel port channel can include a maximum of 16 uplink Fibre Channel ports. Creating a Fibre Channel Port Channel Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 Step 5 On the SAN tab, expand SAN > SAN Cloud. Expand the node for the fabric where you want to create the port channel. Right-click the FC Port Channels node and choose Create Port Channel. In the Set Port Channel Name page of the Create Port Channel wizard, do the following: a) Complete the following fields: Cisco UCS Manager GUI Configuration Guide, Release 2.0 104 OL-25712-04 Fibre Channel Port Channels Name Description ID field The identifier for the port channel. Enter an integer between 1 and 256. This ID cannot be changed after the port channel has been saved. Name field A user-defined name for the port channel. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. b) Click Next. Step 6 In the Add Ports page of the Create Port Channel wizard, do the following: a) From the Port Channel Admin Speed drop-down list, select one of the following data transfer rates for traffic on the port channel: • 1 Gbps • 2 Gbps • 4 Gbps • 8 Gbps • Auto—Cisco UCS determines the data transfer rate. b) In the Ports table, choose one or more ports to include in the port channel. c) Click the >> button to add the ports to the Ports in the port channel table. You can use the << button to remove ports from the port channel. Step 7 Click Finish. Enabling a Fibre Channel Port Channel Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 On the SAN tab, expand SAN > SAN Cloud > Fabric > FC Port Channels. Click the port channel you want to enable. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Enable Port Channel. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 105 Fibre Channel Port Channels Disabling a Fibre Channel Port Channel Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 On the SAN tab, expand SAN > SAN Cloud > Fabric > FC Port Channels. Click the port channel you want to disable. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Disable Port Channel. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Adding Ports to and Removing Ports from a Fibre Channel Port Channel Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 On the SAN tab, expand SAN > SAN Cloud > Fabric > FC Port Channels. Click the port channel to which you want to add or remove ports. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Add Ports. In the Add Ports dialog box, do one of the following: • To add ports, choose one or more ports in the Ports table, and then click the >> button to add the ports to the Ports in the port channel table. • To remove ports, choose one or more ports in the Ports in the port channel table, and then click the << button to remove the ports from the port channel and add them to the Ports table. Step 7 Click OK. Modifying the Properties of a Fibre Channel Port Channel Note If you are connecting two Fibre Channel port channels, the admin speed for both port channels must match for the link to operate. If the admin speed for one or both of the Fibre Channel port channels is set to auto, Cisco UCS adjusts the admin speed automatically. Cisco UCS Manager GUI Configuration Guide, Release 2.0 106 OL-25712-04 Fibre Channel Port Channels Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 On the SAN tab, expand SAN > SAN Cloud > Fabric > FC Port Channels. Click the port channel that you want to modify. In the Work pane, click the General tab. Step 5 In the Actions area, change the values in one or more of the following fields: Name Description Name field The user-defined name given to the port channel. This name can be between 1 and 16 alphanumeric characters. VSAN drop-down list The VSAN associated with the port channel. Port Channel Admin Speed drop-down list The admin speed of the port channel. This can be: • 1 Gbps • 2 Gbps • 4 Gbps • 8 Gbps • auto Step 6 Click Save Changes. Deleting a Fibre Channel Port Channel Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 On the SAN tab, expand SAN > SAN Cloud > Fabric > FC Port Channels. Right-click the port channel you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 107 Adapter Port Channels Adapter Port Channels An adapter port channel groups all the physical links from a Cisco UCS Virtual Interface Card (VIC) to an IOM into one logical link. 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 Cisco UCS Manager CLI Viewing Adapter Port Channels Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis_Number > Servers > Server_Number > Interface Cards Click the adapter for which you want to view the adapter port channels. In the Work pane, click the DCE Interfaces tab. Step 5 To view details of the adapter port channel, click the link in the Port Channel column. 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. Cisco UCS Manager GUI Configuration Guide, Release 2.0 108 OL-25712-04 Fabric Port Channels Cabling Considerations for Fabric Port Channels When you configure the links between the Cisco UCS 2200 Series IOM and a Cisco UCS 6200 series fabric interconnect in fabric port channel mode, the available VIF namespace on the adapter varies depending on where the IOM 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 uplinks are connected such that all of the uplinks from an IOM 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 or removing links from a fabric port channel is disruptive and may affect the available amount of VIF namespace. For high availability cluster mode applications, symmetric cabling configurations are strongly recommended. 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 for your hardware and software configuration. 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. Configuring the Chassis Discovery Policy, on page 242 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. Configuring a Chassis Connectivity Policy, on page 243 Step 3 After chassis discovery, enable or disable additional fabric port channel member ports. Enabling or Disabling a Fabric Port Channel Member Port, on page 110 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 109 Fabric Port Channels 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 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > IO Modules. Step 5 To view details of the fabric port channel, click the link in the Port Channel column. Click the IOM for which you want to view the fabric port channels. In the Work pane, click the Fabric Ports tab. Enabling or Disabling a Fabric Port Channel Member Port Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 Step 5 On the LAN tab, expand LAN > Internal LAN > Fabric > Port Channels. Expand the port channel for which you want to enable or disable a member port. Click the ethernet interface for the member port you want to enable or disable. In the Work pane, click the General tab. Step 6 In the Actions area, click one of the following: • Enable Interface • Disable Interface Step 7 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 110 OL-25712-04 Configuring Server Ports with the Internal Fabric Manager Configuring Server Ports with the Internal Fabric Manager Internal Fabric Manager The Internal Fabric Manager provides a single interface where you can configure server ports for a fabric interconnect in a Cisco UCS domain. The Internal Fabric Manager is accessible from the General tab for that fabric interconnect. Some of the configuration that you can do in the Internal Fabric Manager can also be done in nodes on the Equipment tab, on the LAN tab, or in the LAN Uplinks Manager. Launching the Internal Fabric Manager Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name. Click Fixed Module. In the Work pane, click Internal Fabric Manager in the Actions area. The Internal Fabric Manager opens in a separate window. Configuring a Server Port with the Internal Fabric Manager Procedure Step 1 Step 2 Step 3 Step 4 In the Internal Fabric Manager, click the down arrows to expand the Unconfigured Ports area. Right-click the port that you want to configure and choose Configure as Server Port. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. If you have completed all tasks in the Internal Fabric Manager, click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 111 Configuring Server Ports with the Internal Fabric Manager Unconfiguring a Server Port with the Internal Fabric Manager Procedure Step 1 Step 2 Step 3 Step 4 In the Internal Fabric Manager, click the server port in the Server Ports table. Click Unconfigure Port. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. If you have completed all tasks in the Internal Fabric Manager, click OK. Enabling a Server Port with the Internal Fabric Manager Procedure Step 1 Step 2 Step 3 Step 4 In the Internal Fabric Manager, click the server port in the Server Ports table. Click Enable Port. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. If you have completed all tasks in the Internal Fabric Manager, click OK. Disabling a Server Port with the Internal Fabric Manager Procedure Step 1 Step 2 Step 3 Step 4 In the Internal Fabric Manager, click the server port in the Server Ports table. Click Disable Port. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. If you have completed all tasks in the Internal Fabric Manager, click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 112 OL-25712-04 CHAPTER 7 Configuring Communication Services This chapter includes the following sections: • Communication Services, page 113 • Configuring CIM-XML, page 114 • Configuring HTTP, page 115 • Configuring HTTPS, page 115 • Configuring SNMP, page 121 • Enabling Telnet, page 129 • Disabling Communication Services, page 129 Communication Services You can use the following communication services to interface third-party applications with Cisco UCS: Communication Service Description CIM XML This service is disabled by default and is only available in read-only mode. The default port is 5988. This common information model is one of the standards defined by the Distributed Management Task Force. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 113 Configuring CIM-XML Communication Service Description HTTP This service is enabled on port 80 by default. You must enable either HTTP or HTTPS to run Cisco UCS Manager GUI. If you select HTTP, all data is exchanged in clear text mode. For security purposes, we recommend that you enable HTTPS and disable HTTP. By default, Cisco UCS redirects any attempt to communicate via HTTP to the HTTPS equivalent. We recommend that you do not change this behavior. Note HTTPS If you are upgrading to Cisco UCS, version 1.4(1), this does not happen by default. If you want to redirect any attempt to communicate via HTTP to an HTTPS equivalent, you should enable Redirect HTTP to HTTPS in Cisco UCS Manager. This service is enabled on port 443 by default. With HTTPS, all data is exchanged in encrypted mode through a secure server. For security purposes, we recommend that you only use HTTPS and either disable or redirect HTTP communications. SMASH CLP 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 defined by the Distributed Management Task Force. SNMP This service is disabled by default. 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 This service is enabled on port 22. You cannot disable it, nor can you change the default port. This service provides access to the Cisco UCS Manager CLI. Telnet This service is disabled by default. This service provides access to the Cisco UCS Manager CLI. Configuring CIM-XML Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > Communication Management > Communication Services. Select the Communication Services tab. In the CIM-XML area, click the enabled radio button. Cisco UCS Manager GUI Configuration Guide, Release 2.0 114 OL-25712-04 Configuring HTTP The CIM-XML area expands to display the available configuration options. Step 5 (Optional) In the Port field, change the default port that Cisco UCS Manager GUI will use for CIM-XML. The default port is 5988. Step 6 Click Save Changes. Configuring HTTP Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > Communication Management > Communication Services. Click the Communication Services tab. In the HTTP area, click the enabled radio button. The HTTP area expands to display the available configuration options. Step 5 (Optional) In the Port field, change the default port that Cisco UCS Manager GUI uses for HTTP. The default port is 80. Step 6 (Optional) In the Redirect HTTP to HTTPS field, click the enabled radio button. You must also configure and enable HTTPS to enable redirection of HTTP logins to the HTTPS login. Once enabled, you cannot disable the redirection until you have disabled HTTPS. If you redirect HTTP to HTTPS, you cannot use HTTP to access Cisco UCS Manager GUI. Redirection disables HTTP as it automatically redirects to HTTPS. Click Save Changes. Note Step 7 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 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 115 Configuring HTTPS 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. Creating a Key Ring Cisco UCS Manager supports a maximum of 8 key rings, including the default key ring. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > Key Management. Right-click Key Management and choose Create Key Ring. In the Create Key Ring dialog box, do the following: a) In the Name field, enter a unique name for the key ring. b) In the Modulus field, select one of the following radio buttons to specify the SSL key length in bits: • Mod512 • Mod1024 • Mod1536 • Mod2048 Cisco UCS Manager GUI Configuration Guide, Release 2.0 116 OL-25712-04 Configuring HTTPS c) Click OK. What to Do Next Create a certificate request for this key ring. Creating a Certificate Request for a Key Ring Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > Key Management. Step 5 Step 6 In the General tab, click Create Certificate Request. In the Create Certificate Request dialog box, complete the following fields: Click the key ring for which you want to create a certificate request. In the Work pane, click the General tab. Name Description DNS field The Domain Name Server (DNS) address associated with the request. Locality field The city or town in which the company requesting the certificate is headquartered. Enter up to 64 characters. You can use any letters, numbers, or spaces, as well as the following special characters: , (comma), . (period), @ (at sign), ^ (carat), ( (open parenthesis), ) (close parenthesis), - (dash), _ (underscore), + (plus sign), : (colon), / (forward slash). State field The state or province in which the company requesting the certificate is headquartered. Enter up to 64 characters. You can use any letters, numbers, or spaces, as well as the following special characters: , (comma), . (period), @ (at sign), ^ (carat), ( (open parenthesis), ) (close parenthesis), - (dash), _ (underscore), + (plus sign), : (colon), / (forward slash). Country field The country code corresponding to the country in which the company resides. Enter two alphabetic characters. Organization Name field The organization requesting the certificate. Enter up to 64 characters. You can use any letters, numbers, or spaces, as well as the following special characters: , (comma), . (period), @ (at sign), ^ (carat), ( (open parenthesis), ) (close parenthesis), - (dash), _ (underscore), + (plus sign), : (colon), / (forward slash). Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 117 Configuring HTTPS Name Description Organization Unit Name field The organizational unit. Enter up to 64 characters. You can use any letters, numbers, or spaces, as well as the following special characters: , (comma), . (period), @ (at sign), ^ (carat), ( (open parenthesis), ) (close parenthesis), - (dash), _ (underscore), + (plus sign), : (colon), / (forward slash). Step 7 Step 8 Step 9 Email field The email address associated with the request. Password field An optional password for this request. Confirm Password field If you specified a password, enter it again for confirmation. Subject field The fully qualified domain name of the fabric interconnect. IP Address field The IP address of the fabric interconnect. Click OK. Copy the text of the certificate request out of the Request field and save in a file. Send the file with the certificate request to the trust anchor or certificate authority. What to Do Next Create a trusted point and set the certificate chain for the certificate of trust received from the trust anchor. Creating a Trusted Point Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > Key Management. Right-click Key Management and choose Create Trusted Point. In the Create Trusted Point dialog box, complete the following fields: Name Description Name field The name of the trusted point. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Cisco UCS Manager GUI Configuration Guide, Release 2.0 118 OL-25712-04 Configuring HTTPS Name Description Certificate Chain field The certificate information for this trusted point. The certificate must be in Base64 encoded X.509 (CER) format. Important Step 5 Click OK. What to Do Next When you receive the certificate from the trust anchor or certificate authority, import it into the key ring. Importing a Certificate into a Key Ring Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > Key Management. Click the key ring into which you want to import the certificate. In the Work pane, click the General tab. Step 5 In the Certificate area, complete the following fields: a) From the Trusted Point drop-down list, select the trusted point for the trust anchor that granted this certificate. b) In the Certificate field, paste the text from the certificate you received from the trust anchor or certificate authority. Important The certificate must be in Base64 encoded X.509 (CER) format. Tip If the fields in an area are not displayed, click the Expand icon to the right of the heading. Step 6 Click Save Changes. What to Do Next Configure your HTTPS service with the key ring. Configuring HTTPS Caution After you complete the HTTPS configuration, including changing the port and key ring to be used by HTTPS, all current HTTP and HTTPS sessions are closed without warning as soon as you save or commit the transaction. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 119 Configuring HTTPS Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > Communication Management > Communication Services. Select the Communication Services tab. In the HTTPS area, click the enabled radio button. The HTTPS area expands to display the available configuration options. Step 5 Complete the following fields: Name Description Admin State field This can be one of the following: • Enabled • Disabled If Admin State is enabled, Cisco UCS Manager GUI displays the rest of the fields in this section. Port field The port to use for HTTPS connections. Specify an integer between 1 and 65535. This service is enabled on port 443 by default. Key Ring drop-down list The key ring for HTTPS connections. Cipher Suite Mode field The level of Cipher Suite security used by the Cisco UCS domain. This can be one of the following: • High Strength • Medium Strength • Low Strength • Custom—Allows you to specify a user-defined Cipher Suite specification string. Cipher Suite field If you select Custom in the Cipher Suite Mode field, specify the user-defined Cipher Suite specification string in this field. The Cipher Suite specification string can contain up to 256 characters and must conform to the OpenSSL Cipher Suite specifications. You cannot use any spaces or special characters except ! (exclamation point), + (plus sign), - (hyphen), and : (colon). For details, see http:// httpd.apache.org/docs/2.0/mod/mod_ssl.html#sslciphersuite. For example, the medium strength specification string Cisco UCS Manager uses as the default is: ALL:!ADH:!EXPORT56:!LOW:RC4+RSA:+HIGH:+MEDIUM:+EXP:+eNULL Cisco UCS Manager GUI Configuration Guide, Release 2.0 120 OL-25712-04 Configuring SNMP Step 6 Click Save Changes. Deleting a Key Ring Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > Key Management. Right-click the key ring you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Deleting a Trusted Point Before You Begin Ensure that the trusted point is not used by a key ring. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 On the Admin tab, expand All > Key Management. Right-click the trusted point you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click OK. Configuring SNMP Information about SNMP The Simple Network Management Protocol (SNMP) is an application-layer protocol that provides a message format for communication between SNMP managers and agents. SNMP provides a standardized framework and a common language used for the monitoring and management of devices in a network. SNMP Functional Overview The SNMP framework consists of three parts: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 121 Configuring SNMP • An SNMP manager—The system used to control and monitor the activities of network devices using SNMP. • An SNMP agent—The software component within Cisco UCS, the managed device, that maintains the data for Cisco UCS and reports the data, as needed, to the SNMP manager. Cisco UCS includes the agent and a collection of MIBs. To enable the SNMP agent and create the relationship between the manager and agent, enable and configure SNMP in Cisco UCS Manager. • A managed information base (MIB)—The collection of managed objects on the SNMP agent. Cisco UCS release 1.4(1) and higher support a larger number of MIBs than earlier releases. Cisco UCS supports SNMPv1, SNMPv2c and SNMPv3. Both SNMPv1 and SNMPv2c use a community-based form of security. SNMP is defined in the following: • RFC 3410 (http://tools.ietf.org/html/rfc3410) • RFC 3411 (http://tools.ietf.org/html/rfc3411) • RFC 3412 (http://tools.ietf.org/html/rfc3412) • RFC 3413 (http://tools.ietf.org/html/rfc3413) • RFC 3414 (http://tools.ietf.org/html/rfc3414) • RFC 3415 (http://tools.ietf.org/html/rfc3415) • RFC 3416 (http://tools.ietf.org/html/rfc3416) • RFC 3417 (http://tools.ietf.org/html/rfc3417) • RFC 3418 (http://tools.ietf.org/html/rfc3418) • RFC 3584 (http://tools.ietf.org/html/rfc3584) SNMP Notifications A key feature of SNMP is the ability to generate notifications from an SNMP agent. These notifications do not require that requests be sent from the SNMP manager. Notifications can indicate improper user authentication, restarts, the closing of a connection, loss of connection to a neighbor router, or other significant events. Cisco UCS Manager generates SNMP notifications as either traps or informs. Traps are less reliable than informs because the SNMP manager does not send any acknowledgment when it receives a trap, and Cisco UCS Manager cannot determine if the trap was received. An SNMP manager that receives an inform request acknowledges the message with an SNMP response protocol data unit (PDU). If the Cisco UCS Manager does not receive the PDU, it can send the inform request again. SNMP Security Levels and Privileges SNMPv1, SNMPv2c, and SNMPv3 each represent a different security model. The security model combines with the selected security level to determine the security mechanism applied when the SNMP message is processed. The security level determines the privileges required to view the message associated with an SNMP trap. The privilege level determines whether the message needs to be protected from disclosure or authenticated. The supported security level depends upon which security model is implemented. SNMP security levels support one or more of the following privileges: Cisco UCS Manager GUI Configuration Guide, Release 2.0 122 OL-25712-04 Configuring SNMP • noAuthNoPriv—No authentication or encryption • authNoPriv—Authentication but no encryption • authPriv—Authentication and encryption SNMPv3 provides for both security models and security levels. A security model is an authentication strategy that is set up for a user and the role in which the user resides. A security level is the permitted level of security within a security model. A combination of a security model and a security level determines which security mechanism is employed when handling an SNMP packet. Supported Combinations of SNMP Security Models and Levels The following table identifies what the combinations of security models and levels mean. Table 6: SNMP Security Models and Levels Model Level Authentication Encryption What Happens v1 noAuthNoPriv Community string No Uses a community string match for authentication. v2c noAuthNoPriv Community string No Uses a community string match for authentication. v3 noAuthNoPriv Username No Uses a username match for authentication. v3 authNoPriv HMAC-MD5 or HMAC-SHA No Provides authentication based on the Hash-Based Message Authentication Code (HMAC) Message Digest 5 (MD5) algorithm or the HMAC Secure Hash Algorithm (SHA). Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 123 Configuring SNMP Model Level Authentication Encryption What Happens v3 authPriv HMAC-MD5 or HMAC-SHA DES Provides authentication based on the HMAC-MD5 or HMAC-SHA algorithms. Provides Data Encryption Standard (DES) 56-bit encryption in addition to authentication based on the Cipher Block Chaining (CBC) DES (DES-56) standard. SNMPv3 Security Features SNMPv3 provides secure access to devices by a combination of authenticating and encrypting frames over the network. SNMPv3 authorizes management operations only by configured users and encrypts SNMP messages. The SNMPv3 User-Based Security Model (USM) refers to SNMP message-level security and offers the following services: • Message integrity—Ensures that messages have not been altered or destroyed in an unauthorized manner and that data sequences have not been altered to an extent greater than can occur non-maliciously. • Message origin authentication—Ensures that the claimed identity of the user on whose behalf received data was originated is confirmed. • Message confidentiality and encryption—Ensures that information is not made available or disclosed to unauthorized individuals, entities, or processes. SNMP Support in Cisco UCS Cisco UCS provides the following support for SNMP: Support for MIBs Cisco UCS supports read-only access to MIBs. For information about the specific MIBs available for Cisco UCS and where you can obtain them, see the MIB Quick Reference for Cisco UCS. Authentication Protocols for SNMPv3 Users Cisco UCS supports the following authentication protocols for SNMPv3 users: • HMAC-MD5-96 (MD5) • HMAC-SHA-96 (SHA) Cisco UCS Manager GUI Configuration Guide, Release 2.0 124 OL-25712-04 Configuring SNMP AES Privacy Protocol for SNMPv3 Users Cisco UCS uses Advanced Encryption Standard (AES) as one of the privacy protocols for SNMPv3 message encryption and conforms with RFC 3826. The privacy password, or priv option, offers a choice of DES or 128-bit AES encryption for SNMP security encryption. If you enable AES-128 configuration and include a privacy password for an SNMPv3 user, Cisco UCS Manager uses the privacy password to generate a 128-bit AES key. The AES privacy password can have a minimum of eight characters. If the passphrases are specified in clear text, you can specify a maximum of 64 characters. Enabling SNMP and Configuring SNMP Properties SNMP messages from a Cisco UCS domain display the fabric interconnect name rather than the system name. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > Communication Management > Communication Services. Select the Communication Services tab. In the SNMP area, complete the following fields: Name Description Admin State field This can be one of the following: • Enabled • Disabled Enable this service only if your system includes integration with an SNMP server. If Admin State is enabled, Cisco UCS Manager GUI displays the rest of the fields in this section. Port field The port on which Cisco UCS Manager communicates with the SNMP host. You cannot change the default port. Community/Username field The default SNMP v1 or v2c community name or SNMP v3 username Cisco UCS Manager includes on any trap messages it sends to the SNMP host. Enter an alphanumeric string between 1 and 32 characters. Do not use @ (at sign), \ (backslash), " (double quote), ? (question mark) or an empty space. The default is public. System Contact field The system contact person responsible for the SNMP implementation. Enter a string of up to 255 characters, such as an email address or a name and telephone number. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 125 Configuring SNMP Name Description System Location field The location of the host on which the SNMP agent (server) runs. Enter an alphanumeric string up to 510 characters. Step 5 Click Save Changes. What to Do Next Create SNMP traps and users. Creating an SNMP Trap Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 On the Admin tab, expand All > Communication Management > Communication Services. Select the Communication Services tab. In the SNMP Traps area, click +. In the Create SNMP Trap dialog box, complete the following fields: Name Description IP Address field The IP address of the SNMP host to which Cisco UCS Manager should send the trap. Community/Username field The SNMP v1 or v2c community name or the SNMP v3 username Cisco UCS Manager includes when it sends the trap to the SNMP host. This must be the same as the community or username that is configured for the SNMP service. Enter an alphanumeric string between 1 and 32 characters. Do not use @ (at sign), \ (backslash), " (double quote), ? (question mark) or an empty space. Port field The port on which Cisco UCS Manager communicates with the SNMP host for the trap. Enter an integer between 1 and 65535. The default port is 162. Version field The SNMP version and model used for the trap. This can be one of the following: • V1 • V2c • V3 Cisco UCS Manager GUI Configuration Guide, Release 2.0 126 OL-25712-04 Configuring SNMP Name Description Type field If you select V2c or V3 for the version, the type of trap to send. This can be one of the following: • Traps • Informs v3 Privilege field If you select V3 for the version, the privilege associated with the trap. This can be one of the following: • Auth—Authentication but no encryption • Noauth—No authentication or encryption • Priv—Authentication and encryption Step 6 Step 7 Click OK. Click Save Changes. Deleting an SNMP Trap Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 On the Admin tab, expand All > Communication Management > Communication Services. Select the Communication Services tab. In the SNMP Traps area, click the row in the table that corresponds to the user you want to delete. Click the Delete icon to the right of the table. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 127 Configuring SNMP Creating an SNMPv3 user Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 On the Admin tab, expand All > Communication Management > Communication Services. Select the Communication Services tab. In the SNMP Users area, click +. In the Create SNMP User dialog box, complete the following fields: Name Description Name field The username assigned to the SNMP user. Enter up to 32 letters or numbers. The name must begin with a letter and you can also specify _ (underscore), . (period), @ (at sign), and (hyphen). Note Auth Type field You cannot create an SNMP username that is identical to a locally authenticated username. The authorization type. This can be one of the following: • MD5 • SHA Use AES-128 check box If checked, this user uses AES-128 encryption. Password field The password for this user. Confirm Password field The password again for confirmation purposes. Privacy Password field The privacy password for this user. Confirm Privacy Password field The privacy password again for confirmation purposes. Step 6 Step 7 Click OK. Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 128 OL-25712-04 Enabling Telnet Deleting an SNMPv3 User Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 On the Admin tab, expand All > Communication Management > Communication Services. Select the Communication Services tab. In the SNMP Users area, click the row in the table that corresponds to the user you want to delete. Click the Delete icon to the right of the table. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click Save Changes. Enabling Telnet Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 On the Admin tab, expand All > Communication Management > Communication Services. Click the Communication Services tab. In the Telnet area, click the enabled radio button. Click Save Changes. Disabling Communication Services Note We recommend that you disable all communication services that are not required to interface with other network applications. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > Communication Management > Communication Services. On the Communication Services tab, click the disable radio button for each service that you want to disable. Click Save Changes. Step 3 Step 4 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 129 Disabling Communication Services Cisco UCS Manager GUI Configuration Guide, Release 2.0 130 OL-25712-04 CHAPTER 8 Configuring Authentication This chapter includes the following sections: • Authentication Services, page 131 • Guidelines and Recommendations for Remote Authentication Providers, page 131 • User Attributes in Remote Authentication Providers, page 132 • LDAP Group Rule, page 134 • Configuring LDAP Providers, page 134 • Configuring RADIUS Providers, page 142 • Configuring TACACS+ Providers, page 144 • Configuring Multiple Authentication Systems, page 146 • Selecting a Primary Authentication Service, page 151 Authentication Services Cisco UCS supports two methods to authenticate user logins: • Through user accounts local to Cisco UCS Manager • Remotely through one of the following protocols: ◦ LDAP ◦ RADIUS ◦ TACACS+ Guidelines and Recommendations for Remote Authentication Providers If a system is configured for one of the supported remote authentication services, you must create a provider for that service to ensure that Cisco UCS Manager can communicate with it. In addition, you need to be aware of the following guidelines that impact user authorization: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 131 User Attributes in Remote Authentication Providers User Accounts in Remote Authentication Services User accounts can exist locally in Cisco UCS Manager or in the remote authentication server. The temporary sessions for users who log in through remote authentication services can be viewed through Cisco UCS Manager GUI or Cisco UCS Manager CLI. User Roles in Remote Authentication Services If you create user accounts in the remote authentication server, you must ensure that the accounts include the roles those users require for working in Cisco UCS Manager and that the names of those roles match the names used in Cisco UCS Manager. Depending on the role policy, a user may not be allowed to log in or will be granted only read-only privileges. User Attributes in Remote Authentication Providers For RADIUS and TACACS+ configurations, you must configure a user attribute for Cisco UCS in each remote authentication provider through which users log in to Cisco UCS Manager. This user attribute holds the roles and locales assigned to each user. Note This step is not required for LDAP configurations that use LDAP Group Mapping to assign roles and locales. When a user logs in, Cisco UCS Manager does the following: 1 Queries the remote authentication service. 2 Validates the user. 3 If the user is validated, checks for the roles and locales assigned to that user. The following table contains a comparison of the user attribute requirements for the remote authentication providers supported by Cisco UCS. Table 7: Comparison of User Attributes by Remote Authentication Provider Authentication Provider Custom Attribute Schema Extension Attribute ID Requirements LDAP Not required if group mapping is used Optional. You can choose to do either of the following: The Cisco LDAP implementation requires a unicode type attribute. Optional if group mapping is not used • Do not extend the LDAP schema and configure an existing, unused attribute that meets the requirements. If you choose to create the CiscoAVPair custom attribute, use the following attribute ID: 1.3.6.1.4.1.9.287247.1 • Extend the LDAP schema A sample OID is provided in the and create a custom attribute following section. with a unique name, such as CiscoAVPair. Cisco UCS Manager GUI Configuration Guide, Release 2.0 132 OL-25712-04 User Attributes in Remote Authentication Providers Authentication Provider Custom Attribute Schema Extension RADIUS Optional Optional. You can choose to do either of the following: Attribute ID Requirements The vendor ID for the Cisco RADIUS implementation is 009 and the vendor ID for the attribute is • Do not extend the RADIUS 001. schema and use an existing, unused attribute that meets The following syntax example shows how to specify multiples user the requirements. roles and locales if you choose to • Extend the RADIUS schema create the cisco-avpair attribute: and create a custom attribute shell:roles="admin,aaa" with a unique name, such as shell:locales="L1,abc". Use a cisco-avpair. comma "," as the delimiter to separate multiple values. TACACS+ Required Required. You must extend the schema and create a custom attribute with the name cisco-av-pair. The cisco-av-pair name is the string that provides the attribute ID for the TACACS+ provider. The following syntax example shows how to specify multiples user roles and locales when you create the cisco-av-pair attribute: cisco-av-pair=shell:roles="admin aaa" shell:locales*"L1 abc". Using an asterisk (*) in the cisco-av-pair attribute syntax flags the locale as optional, preventing authentication failures for other Cisco devices that use the same authorization profile. Use a space as the delimiter to separate multiple values. Sample OID for LDAP User Attribute The following is a sample OID for a custom CiscoAVPair attribute: CN=CiscoAVPair,CN=Schema, CN=Configuration,CN=X objectClass: top objectClass: attributeSchema cn: CiscoAVPair distinguishedName: CN=CiscoAVPair,CN=Schema,CN=Configuration,CN=X instanceType: 0x4 uSNCreated: 26318654 attributeID: 1.3.6.1.4.1.9.287247.1 attributeSyntax: 2.5.5.12 isSingleValued: TRUE showInAdvancedViewOnly: TRUE adminDisplayName: CiscoAVPair adminDescription: UCS User Authorization Field oMSyntax: 64 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 133 LDAP Group Rule lDAPDisplayName: CiscoAVPair name: CiscoAVPair objectCategory: CN=Attribute-Schema,CN=Schema,CN=Configuration,CN=X LDAP Group Rule The LDAP group rule is used to determine whether Cisco UCS should use LDAP groups when assigning user roles and locales to a remote user. Configuring LDAP Providers Configuring Properties for LDAP Providers The properties that you configure in this task are the default settings for all provider connections of this type defined in Cisco UCS Manager. If an individual provider includes a setting for any of these properties, Cisco UCS uses that setting and ignores the default setting. Before You Begin If you are using Active Directory as your LDAP server, create a user account in the Active Directory server to bind with Cisco UCS. This account should be given a non-expiring password. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > User Management > LDAP. Complete the following fields in the Properties area: Name Description Timeout field The length of time in seconds the system should spend trying to contact the LDAP database before it times out. Enter an integer from 1 to 60 seconds. The default value is 30 seconds. This property is required. Attribute field An LDAP attribute that stores the values for the user roles and locales. This property is always a name-value pair. The system queries the user record for the value that matches this attribute name. If you do not want to extend your LDAP schema, you can configure an existing, unused LDAP attribute with the Cisco UCS roles and locales. Alternatively, you can create an attribute named CiscoAVPair in the remote authentication service with the following attribute ID: 1.3.6.1.4.1.9.287247.1 Cisco UCS Manager GUI Configuration Guide, Release 2.0 134 OL-25712-04 Configuring LDAP Providers Name Description Base DN field The specific distinguished name in the LDAP hierarchy where the server should begin a search when a remote user logs in and the system attempts to get the user's DN based on their username. The maximum supported string length is 127 characters. This property is required. If you do not specify a base DN on this tab then you must specify one on the General tab for every LDAP provider defined in this Cisco UCS domain. Filter field The LDAP search is restricted to those usernames that match the defined filter. This property is required. If you do not specify a filter on this tab then you must specify one on the General tab for every LDAP provider defined in this Cisco UCS domain. Step 4 Click Save Changes. What to Do Next Create an LDAP provider. Creating an LDAP Provider Cisco UCS Manager supports a maximum of 16 LDAP providers. Before You Begin If you are using Active Directory as your LDAP server, create a user account in the Active Directory server to bind with Cisco UCS. This account should be given a non-expiring password. • In the LDAP server, perform one of the following configurations: ◦ Configure LDAP groups. LDAP groups contain user role and locale information. ◦ Configure users with the attribute that holds the user role and locale information for Cisco UCS Manager. You can choose whether to extend the LDAP schema for this attribute. If you do not want to extend the schema, use an existing LDAP attribute to hold the Cisco UCS user roles and locales. If you prefer to extend the schema, create a custom attribute, such as the CiscoAVPair attribute. The Cisco LDAP implementation requires a unicode type attribute. If you choose to create the CiscoAVPair custom attribute, use the following attribute ID: 1.3.6.1.4.1.9.287247.1 ◦ For a cluster configuration, add the management port IP addresses for both fabric interconnects. This configuration ensures that remote users can continue to log in if the first fabric interconnect fails and the system fails over to the second fabric interconnect. All login requests are sourced from these IP addresses, not the virtual IP address used by Cisco UCS Manager. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 135 Configuring LDAP Providers • If you want to use secure communications, create a trusted point containing the certificate of the root certificate authority (CA) of the LDAP server in Cisco UCS Manager. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > User Management > LDAP. In the Work pane, click the General tab. Step 4 Step 5 In the Actions area, click Create LDAP Provider. On the Create LDAP Provider page of the wizard, do the following: a) Complete the following fields with information about the LDAP service you want to use: Name Description Hostname field The hostname or IP address on which the LDAP provider resides. If SSL is enabled, this field must exactly match a Common Name (CN) in the security certificate of the LDAP database. Note Order field If you use a hostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager. The order in which Cisco UCS uses this provider to authenticate users. Enter an integer between 1 and 16, or enter lowest-available or 0 (zero) if you want Cisco UCS to assign the next available order based on the other providers defined in this Cisco UCS domain. Bind DN field The distinguished name (DN) for an LDAP database account that has read and search permissions for all objects under the base DN. The maximum supported string length is 127 ASCII characters. Base DN field The specific distinguished name in the LDAP hierarchy where the server should begin a search when a remote user logs in and the system attempts to get the user's DN based on their username. The maximum supported string length is 127 characters. This value is required unless a default base DN has been set on the LDAP General tab. Port field The port through which Cisco UCS communicates with the LDAP database. The standard port number is 389. Enable SSL check box If checked, encryption is required for communications with the LDAP database. If unchecked, authentication information will be sent as clear text. LDAP uses STARTTLS. This allows encrypted communication using port 389. Cisco UCS Manager GUI Configuration Guide, Release 2.0 136 OL-25712-04 Configuring LDAP Providers Name Description Filter field The LDAP search is restricted to those usernames that match the defined filter. This value is required unless a default filter has been set on the LDAP General tab. Attribute field An LDAP attribute that stores the values for the user roles and locales. This property is always a name-value pair. The system queries the user record for the value that matches this attribute name. If you do not want to extend your LDAP schema, you can configure an existing, unused LDAP attribute with the Cisco UCS roles and locales. Alternatively, you can create an attribute named CiscoAVPair in the remote authentication service with the following attribute ID: 1.3.6.1.4.1.9.287247.1 This value is required unless a default attribute has been set on the LDAP General tab. Password field The password for the LDAP database account specified in the Bind DN field. You can enter any standard ASCII characters except for space, § (section sign), ? (question mark), or = (equal sign). Confirm Password field The LDAP database password repeated for confirmation purposes. Timeout field The length of time in seconds the system should spend trying to contact the LDAP database before it times out. Enter an integer from 1 to 60 seconds, or enter 0 (zero) to use the global timeout value specified on the LDAP General tab. The default is 30 seconds. b) Click Next. Step 6 On the LDAP Group Rule page of the wizard, do the following: a) Complete the following fields: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 137 Configuring LDAP Providers Name Description Group Authorization field Whether Cisco UCS also searches LDAP groups when authenticating and assigning user roles and locales to remote users. This can be one of the following: • Disable—Cisco UCS does not access any LDAP groups. • Enable—Cisco UCS searches all LDAP groups mapped in this Cisco UCS domain. If the remote user is found, Cisco UCS assigns the user roles and locales defined for that LDAP group in the associated LDAP group map. Note Group Recursion field Role and locale assignment is cumulative. If a user is included in multiple groups, or has a role or locale specified in the LDAP attribute, Cisco UCS assigns that user all the roles and locales mapped to any of those groups or attributes. Whether Cisco UCS searches both the mapped groups and their parent groups. This can be one of the following: • Non Recursive—Cisco UCS searches only the groups mapped in this Cisco UCS domain. If none of the groups containing the user explicitly set the user's authorization properties, Cisco UCS uses the default settings. • Recursive—Cisco UCS searches each mapped group and all its parent groups for the user's authorization properties. These properties are cumulative, so for each group Cisco UCS finds with explicit authorization property settings, it applies those settings to the current user. Otherwise it uses the default settings. Target Attribute field The attribute Cisco UCS uses to determine group membership in the LDAP database. The supported string length is 63 characters. The default string is memberOf. b) Click Finish. What to Do Next For implementations involving a single LDAP database, select LDAP as the authentication service. For implementations involving multiple LDAP databases, configure an LDAP provider group. Cisco UCS Manager GUI Configuration Guide, Release 2.0 138 OL-25712-04 Configuring LDAP Providers Changing the LDAP Group Rule for an LDAP Provider Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > LDAP. Expand LDAP Providers and choose the LDAP provider for which you want to change the group rule. In the Work pane, click the General tab. Step 5 In the LDAP Group Rules area, complete the following fields: Name Description Group Authorization field Whether Cisco UCS also searches LDAP groups when authenticating and assigning user roles and locales to remote users. This can be one of the following: • Disable—Cisco UCS does not access any LDAP groups. • Enable—Cisco UCS searches all LDAP groups mapped in this Cisco UCS domain. If the remote user is found, Cisco UCS assigns the user roles and locales defined for that LDAP group in the associated LDAP group map. Note Group Recursion field Role and locale assignment is cumulative. If a user is included in multiple groups, or has a role or locale specified in the LDAP attribute, Cisco UCS assigns that user all the roles and locales mapped to any of those groups or attributes. Whether Cisco UCS searches both the mapped groups and their parent groups. This can be one of the following: • Non Recursive—Cisco UCS searches only the groups mapped in this Cisco UCS domain. If none of the groups containing the user explicitly set the user's authorization properties, Cisco UCS uses the default settings. • Recursive—Cisco UCS searches each mapped group and all its parent groups for the user's authorization properties. These properties are cumulative, so for each group Cisco UCS finds with explicit authorization property settings, it applies those settings to the current user. Otherwise it uses the default settings. Target Attribute field The attribute Cisco UCS uses to determine group membership in the LDAP database. The supported string length is 63 characters. The default string is memberOf. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 139 Configuring LDAP Providers Step 6 Click Save Changes. Deleting an LDAP Provider Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 On the Admin tab, expand All > User Management > LDAP. Expand LDAP Providers. Right-click the LDAP provider you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. LDAP Group Mapping For organizations that already use LDAP groups to restrict access to LDAP databases, group membership information can be used by UCSM to assign a role or locale to an LDAP user during login. This eliminates the need to define role or locale information in the LDAP user object when Cisco UCS Manager is deployed. When a user logs in to Cisco UCS Manager, information about the user's role and locale are pulled from the LDAP group map. If the role and locale criteria match the information in the policy, access is granted. Role and locale definitions are configured locally in Cisco UCS Manager and do not update automatically based on changes to an LDAP directory. When deleting or renaming LDAP groups in an LDAP directory, it is important that you update Cisco UCS Manager with the change. An LDAP group map can be configured to include any of the following combinations of roles and locales: • Roles only • Locales only • Both roles and locales For example, consider an LDAP group representing a group of server administrators at a specific location. The LDAP group map might be configured to include user roles like server-profile and server-equipment. To restrict access to server administrators at a specific location, the locale could be set to a particular site name. Note Cisco UCS Manager includes many out-of-the-box user roles but does not include any locales. Mapping an LDAP provider group to a locale requires that you create a custom locale. Cisco UCS Manager GUI Configuration Guide, Release 2.0 140 OL-25712-04 Configuring LDAP Providers Creating an LDAP Group Map Before You Begin • Create an LDAP group in the LDAP server. • Configure the distinguished name for the LDAP group in the LDAP server. • Create locales in Cisco UCS Manager (optional). • Create custom roles in Cisco UCS Manager (optional). Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > LDAP. Right-click LDAP Group Maps and choose Create LDAP Group Map. In the Create LDAP Group Map dialog box, do the following: a) In the LDAP Group DN field, enter the distinguished name of the group in the LDAP database. Important This name must match the name in the LDAP database exactly. b) In the Roles table, check the check boxes for all roles that you want to assign to users who are included in the group map. c) In the Locales table, check the check boxes for all locales that you want to assign to users who are included in the group map. d) Click OK. What to Do Next Set the LDAP group rule. Deleting an LDAP Group Map Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 On the Admin tab, expand All > User Management > LDAP. Expand LDAP Group Maps. Right-click the LDAP group map you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 141 Configuring RADIUS Providers Configuring RADIUS Providers Configuring Properties for RADIUS Providers The properties that you configure in this task are the default settings for all provider connections of this type defined in Cisco UCS Manager. If an individual provider includes a setting for any of these properties, Cisco UCS uses that setting and ignores the default setting. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 In the Admin tab, expand User Management > RADIUS. Complete the following fields in the Properties area: Name Description Timeout field The length of time in seconds the system should spend trying to contact the RADIUS database before it times out. Enter an integer from 1 to 60 seconds, or enter 0 (zero) to use the global timeout value specified on the RADIUS General tab. The default is 5 seconds. Retries field Step 4 The number of times to retry the connection before the request is considered to have failed. Click Save Changes. What to Do Next Create a RADIUS provider. Creating a RADIUS Provider Cisco UCS Manager supports a maximum of 16 RADIUS providers. Before You Begin Perform the following configuration in the RADIUS server: • Configure users with the attribute that holds the user role and locale information for Cisco UCS Manager. You can choose whether to extend the RADIUS schema for this attribute. If you do not want to extend the schema, use an existing RADIUS attribute to hold the Cisco UCS user roles and locales. If you prefer to extend the schema, create a custom attribute, such as the cisco-avpair attribute. The vendor ID for the Cisco RADIUS implementation is 009 and the vendor ID for the attribute is 001. Cisco UCS Manager GUI Configuration Guide, Release 2.0 142 OL-25712-04 Configuring RADIUS Providers The following syntax example shows how to specify multiples user roles and locales if you choose to create the cisco-avpair attribute: shell:roles="admin,aaa" shell:locales="L1,abc". Use a comma "," as the delimiter to separate multiple values. • For a cluster configuration, add the management port IP addresses for both fabric interconnects. This configuration ensures that remote users can continue to log in if the first fabric interconnect fails and the system fails over to the second fabric interconnect. All login requests are sourced from these IP addresses, not the virtual IP address used by Cisco UCS Manager. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > User Management > RADIUS. In the Create RADIUS Provider dialog box: a) Complete the fields with the information about the RADIUS service you want to use. Name Description Hostname field The hostname or IP address on which the RADIUS provider resides. Note Order field If you use a hostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager. The order in which Cisco UCS uses this provider to authenticate users. Enter an integer between 1 and 16, or enter lowest-available or 0 (zero) if you want Cisco UCS to assign the next available order based on the other providers defined in this Cisco UCS domain. Key field The SSL encryption key for the database. Confirm Key field The SSL encryption key repeated for confirmation purposes. Authorization Port field The port through which Cisco UCS communicates with the RADIUS database. Timeout field The length of time in seconds the system should spend trying to contact the RADIUS database before it times out. Enter an integer from 1 to 60 seconds, or enter 0 (zero) to use the global timeout value specified on the RADIUS General tab. The default is 5 seconds. Retries field The number of times to retry the connection before the request is considered to have failed. If desired, enter an integer between 0 and 5. If you do not specify a value, Cisco UCS uses the value specified on the RADIUS General tab. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 143 Configuring TACACS+ Providers b) Click OK. Step 4 Click Save Changes. What to Do Next For implementations involving a single RADIUS database, select RADIUS as the primary authentication service. For implementations involving multiple RADIUS databases, configure a RADIUS provider group. Deleting a RADIUS Provider Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 In the Admin tab, expand User Management > RADIUS. Right-click the RADIUS provider you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Configuring TACACS+ Providers Configuring Properties for TACACS+ Providers The properties that you configure in this task are the default settings for all provider connections of this type defined in Cisco UCS Manager. If an individual provider includes a setting for any of these properties, Cisco UCS uses that setting and ignores the default setting. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 In the Admin tab, expand User Management > TACACS+. In the Properties area, complete the Timeout field: The length of time in seconds the system should spend trying to contact the TACACS+ database before it times out. Enter an integer from 1 to 60 seconds, or enter 0 (zero) to use the global timeout value specified on the TACACS+ General tab. The default is 5 seconds. Step 4 Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 144 OL-25712-04 Configuring TACACS+ Providers What to Do Next Create an TACACS+ provider. Creating a TACACS+ Provider Cisco UCS Manager supports a maximum of 16 TACACS+ providers. Before You Begin Perform the following configuration in the TACACS+ server: • Create the cisco-av-pair attribute. You cannot use an existing TACACS+ attribute. The cisco-av-pair name is the string that provides the attribute ID for the TACACS+ provider. The following syntax example shows how to specify multiples user roles and locales when you create the cisco-av-pair attribute: cisco-av-pair=shell:roles="admin aaa" shell:locales*"L1 abc". Using an asterisk (*) in the cisco-av-pair attribute syntax flags the locale as optional, preventing authentication failures for other Cisco devices that use the same authorization profile. Use a space as the delimiter to separate multiple values. • For a cluster configuration, add the management port IP addresses for both fabric interconnects. This configuration ensures that remote users can continue to log in if the first fabric interconnect fails and the system fails over to the second fabric interconnect. All login requests are sourced from these IP addresses, not the virtual IP address used by Cisco UCS Manager. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > TACACS+. In the Actions area of the General tab, click Create TACACS+ Provider. In the Create TACACS+ Provider dialog box: a) Complete the fields with the information about the TACACS+ service you want to use. Name Description Hostname field The hostname or IP address on which the TACAS+ provider resides. Note Order field If you use a hostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager. The order in which Cisco UCS uses this provider to authenticate users. Enter an integer between 1 and 16, or enter lowest-available or 0 (zero) if you want Cisco UCS to assign the next available order based on the other providers defined in this Cisco UCS domain. Key field The SSL encryption key for the database. Confirm Key field The SSL encryption key repeated for confirmation purposes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 145 Configuring Multiple Authentication Systems Name Description Port field The port through which Cisco UCS should communicate with the TACACS+ database. Enter an integer between 1 and 65535. The default port is 49. Timeout field The length of time in seconds the system should spend trying to contact the TACACS+ database before it times out. Enter an integer from 1 to 60 seconds, or enter 0 (zero) to use the global timeout value specified on the TACACS+ General tab. The default is 5 seconds. b) Click OK. Step 5 Click Save Changes. What to Do Next For implementations involving a single TACACS+ database, select TACACS+ as the primary authentication service. For implementations involving multiple TACACS+ databases, configure a TACACS+ provider group. Deleting a TACACS+ Provider Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 In the Admin tab, expand User Management > TACACS+. Right-click the TACACS+ provider you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Configuring Multiple Authentication Systems Multiple Authentication Systems You can configure Cisco UCS to use multiple authentication systems by configuring the following features: • Provider groups • Authentication domains Cisco UCS Manager GUI Configuration Guide, Release 2.0 146 OL-25712-04 Configuring Multiple Authentication Systems Provider Groups A provider group is a set of providers that will be used by Cisco UCS during the authentication process. Cisco UCS Manager allows you to create a maximum of 16 provider groups, with a maximum of eight providers allowed per group. During authentication, all the providers within a provider group are tried in order. If all of the configured servers are unavailable or unreachable, Cisco UCS Manager automatically falls back to the local authentication method using the local username and password. Creating an LDAP Provider Group Creating an LDAP provider group allows you to authenticate using multiple LDAP databases. Note Authenticating with a single LDAP database does not require you to set up an LDAP provider group. Before You Begin Create one or more LDAP providers. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > LDAP. Right-click LDAP Provider Groups and choose Create LDAP Provider Group. In the Create LDAP Provider Group dialog box, do the following: a) In the Name field, enter a unique name for the group. This name can be between 1 and 127 characters. b) In the LDAP Providers table, choose one or more providers to include in the group. c) Click the >> button to add the providers to the Included Providers table. You can use the << button to remove providers from the group. d) After you have added all desired providers to the provider group, click OK. What to Do Next Configure an authentication domain or select a default authentication service. Deleting an LDAP Provider Group Before You Begin Remove the provider group from an authentication configuration. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 147 Configuring Multiple Authentication Systems Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 On the Admin tab, expand All > User Management > LDAP. Expand LDAP Provider Groups. Right-click the LDAP provider group you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Creating a RADIUS Provider Group Creating a RADIUS provider group allows you to authenticate using multiple RADIUS databases. Note Authenticating with a single RADIUS database does not require you to set up a RADIUS provider group. Before You Begin Create one or more RADIUS providers. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > RADIUS. Right-click RADIUS Provider Groups and choose Create RADIUS Provider Group. In the Create RADIUS Provider Group dialog box, do the following: a) In the Name field, enter a unique name for the group. This name can be between 1 and 127 ASCII characters. b) In the RADIUS Providers table, choose one or more providers to include in the group. c) Click the >> button to add the providers to the Included Providers table. You can use the << button to remove providers from the group. d) After you have added all desired providers to the provider group, click OK. What to Do Next Configure an authentication domain or select a default authentication service. Deleting a RADIUS Provider Group You cannot delete a provider group if it is being used by an authentication configuration. Cisco UCS Manager GUI Configuration Guide, Release 2.0 148 OL-25712-04 Configuring Multiple Authentication Systems Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 On the Admin tab, expand All > User Management > RADIUS. Expand RADIUS Provider Groups. Right-click the RADIUS provider group you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Creating a TACACS+ Provider Group Creating a TACACS+ provider group allows you to authenticate using multiple TACACS+ databases. Note Authenticating with a single TACACS+ database does not require you to set up a TACACS+ provider group. Before You Begin Create one or more TACACS+ providers. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > TACACS+. Right-click TACACS+ Provider Groups and choose Create TACACS+ Provider Group. In the Create TACACS+ Provider Group dialog box, do the following: a) In the Name field, enter a unique name for the group. This name can be between 1 and 127 ASCII characters. b) In the TACACS+ Providers table, choose one or more providers to include in the group. c) Click the >> button to add the providers to the Included Providers table. You can use the << button to remove providers from the group. d) After you have added all desired providers to the provider group, click OK. Deleting a TACACS+ Provider Group You cannot delete a provider group if it is being used by an authentication configuration. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 149 Configuring Multiple Authentication Systems Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 On the Admin tab, expand All > User Management > TACACS+. Expand TACACS+ Provider Groups. Right-click the TACACS+ provider group you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Authentication Domains Authentication domains are used by Cisco UCS Manager to leverage multiple authentication systems. Each authentication domain is specified and configured during login. If no authentication domain is specified, the default authentication service configuration is used. You can create up to eight authentication domains. Each authentication domain is associated with a provider group and realm in Cisco UCS Manager. If no provider group is specified, all servers within the realm are used. Creating an Authentication Domain Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > Authentication. Right-click Authentication Domains and choose Create a Domain. In the Create a Domain dialog box, complete the following fields: Name Description Name field The name of the domain. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Note For systems using RADIUS as their preferred authentication protocol, the authentication domain name is considered part of the user name and counts toward the 32 character limit for locally created user names. Because Cisco UCS inserts 5 characters for formatting, authentication will fail if the combined total of the domain name plus the user name is more than 27 characters. Cisco UCS Manager GUI Configuration Guide, Release 2.0 150 OL-25712-04 Selecting a Primary Authentication Service Name Description Web Session Refresh Period field When a web client connects to Cisco UCS Manager, the client needs to send refresh requests to Cisco UCS Manager to keep the web session active. This option specifies the maximum amount of time allowed between refresh requests for a user in this domain. If this time limit is exceeded, Cisco UCS Manager considers the web session to be inactive, but it does not terminate the session. Specify an integer between 60 and 172800. The default is 600 seconds. Web Session Timeout field The maximum amount of time that can elapse after the last refresh request before Cisco UCS Manager considers a web session to have ended. If this time limit is exceeded, Cisco UCS Manager automatically terminates the web session. Specify an integer between 60 and 172800. The default is 7200 seconds. Realm field The authentication protocol that will be applied to users in this domain. This can be one of the following: • Local—The user account must be defined locally in this Cisco UCS domain. • Radius—The user must be defined on the RADIUS server specified for this Cisco UCS domain. • Tacacs—The user must be defined on the TACACS+ server specified for this Cisco UCS domain. • Ldap—The user must be defined on the LDAP server specified for this Cisco UCS domain. Provider Group drop-down list Step 5 If the Realm is set to anything other than Local, this field allows you to select the associated provider group, if any. Click OK. Selecting a Primary Authentication Service Selecting the Console Authentication Service Before You Begin If the system uses a remote authentication service, create a provider for that authentication service. If the system uses only local authentication through Cisco UCS, you do not need to create a provider first. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 151 Selecting a Primary Authentication Service Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > Authentication. Click Native Authentication. In the Work pane, click the General tab. Step 5 In the Console Authentication area, complete the following fields: Name Description Realm field The method by which a user logging into the console is authenticated. This can be one of the following: • Local—The user account must be defined locally in this Cisco UCS domain. • Radius—The user must be defined on the RADIUS server specified for this Cisco UCS domain. • Tacacs—The user must be defined on the TACACS+ server specified for this Cisco UCS domain. • Ldap—The user must be defined on the LDAP server specified for this Cisco UCS domain. • None—If the user account is local to this Cisco UCS domain, no password is required when the user logs into the console. Provider Group drop-down list Step 6 The provider group to be used to authenticate a user logging into the console. Click Save Changes. Selecting the Default Authentication Service Before You Begin If the system uses a remote authentication service, create a provider for that authentication service. If the system uses only local authentication through Cisco UCS, you do not need to create a provider first. Cisco UCS Manager GUI Configuration Guide, Release 2.0 152 OL-25712-04 Selecting a Primary Authentication Service Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > Authentication. Click Native Authentication. In the Work pane, click the General tab. Step 5 In the Default Authentication area, complete the following fields: Name Description Realm drop-down list The default method by which a user is authenticated during remote login. This can be one of the following: • Local—The user account must be defined locally in this Cisco UCS domain. • Radius—The user must be defined on the RADIUS server specified for this Cisco UCS domain. • Tacacs—The user must be defined on the TACACS+ server specified for this Cisco UCS domain. • Ldap—The user must be defined on the LDAP server specified for this Cisco UCS domain. • None—If the user account is local to this Cisco UCS domain, no password is required when the user logs in remotely. Provider Group drop-down list Step 6 The default provider group to be used to authenticate the user during remote login. Click Save Changes. Role Policy for Remote Users By default, if user roles are not configured in Cisco UCS Manager read-only access is granted to all users logging in to Cisco UCS Manager from a remote server using the LDAP, RADIUS, or TACACS protocols. For security reasons, it might be desirable to restrict access to those users matching an established user role in Cisco UCS Manager. You can configure the role policy for remote users in the following ways: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 153 Selecting a Primary Authentication Service assign-default-role Does not restrict user access to Cisco UCS Manager based on user roles. Read-only access is granted to all users unless other user roles have been defined in Cisco UCS Manager. This is the default behavior. no-login Restricts user access to Cisco UCS Manager based on user roles. If user roles have not been assigned for the remote authentication system, access is denied. Configuring the Role Policy for Remote Users Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > Authentication. Click Native Authentication. In the Work pane, click the General tab. Step 5 In the Role Policy for Remote Users field, click one of the following radio buttons to determine what happens when a user attempts to log in and the remote authentication provider does not supply a user role with the authentication information: • No Login—The user is not allowed to log in to the system, even if the username and password are correct. • Assign Default Role—The user is allowed to log in with a read-only user role. Step 6 Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 154 OL-25712-04 CHAPTER 9 Configuring Organizations This chapter includes the following sections: • Organizations in a Multi-Tenancy Environment, page 155 • Hierarchical Name Resolution in a Multi-Tenancy Environment, page 156 • Creating an Organization under the Root Organization, page 157 • Creating an Organization under a Sub-Organization, page 158 • Deleting an Organization, page 158 Organizations in a Multi-Tenancy Environment Multi-tenancy allows you to divide up 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 multi-tenant 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 • Service profiles Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 155 Hierarchical Name Resolution in a Multi-Tenancy Environment • Service profile templates The root organization is always the top level organization. Hierarchical Name Resolution in a Multi-Tenancy Environment In a multi-tenant environment, Cisco UCS uses the hierarchy of an organization to resolve the names of policies and resource pools. When Cisco UCS Manager searches for details of a policy or a resource assigned to a pool, the following occurs: 1 Cisco UCS Manager checks for policies and pools with the specified name within the organization assigned to the service profile or policy. 2 If a policy is found or an available resource is inside a pool, Cisco UCS Manager uses that policy or resource. If the pool does not have any available resources at the local level, Cisco UCS Manager moves up in the hierarchy to the parent organization and searches for a pool with the same name. Cisco UCS Manager repeats this step until the search reaches the root organization. 3 If the search reaches the root organization and has not found an available resource or policy, Cisco UCS Manager returns to the local organization and begins to search for a default policy or available resource in the default pool. 4 If an applicable default policy or available resource in a default pool is found, Cisco UCS Manager uses that policy or resource. If the pool does not have any available resources, Cisco UCS Manager moves up in the hierarchy to the parent organization and searches for a default pool. Cisco UCS Manager repeats this step until the search reaches the root organization. 5 If Cisco UCS Manager cannot find an applicable policy or available resource in the hierarchy, it returns an allocation error. Example: Server Pool Name Resolution in a Single-Level Hierarchy In this example, all organizations are at the same level below the root organization. For example, a service provider creates separate organizations for each customer. In this configuration, organizations only have access to the policies and resource pools assigned to that organization and to the root organization. In this example, a service profile in the XYZcustomer organization is configured to use servers from the XYZcustomer server pool. When resource pools and policies are assigned to the service profile, the following occurs: 1 Cisco UCS Manager checks for an available server in the XYZcustomer server pool. 2 If the XYZcustomer server pool has an available server, Cisco UCS Manager associates that server with the service profile and discontinues the search. If the pool does not have an available server, Cisco UCS Manager checks the root organization for a server pool with the same name. 3 If the root organization includes an XYZcustomer server pool and that pool has an available server, Cisco UCS Manager associates that server with the service profile and discontinues the search. If the pool does not have an available server, Cisco UCS Manager returns to the XYZcustomer organization to check the default server pool. 4 If the default pool in the XYZcustomer organization has an available server, Cisco UCS Manager associates that server with the service profile and discontinues the search. If the default pool does not have an available server, Cisco UCS Manager checks the default server pool in the root organization. Cisco UCS Manager GUI Configuration Guide, Release 2.0 156 OL-25712-04 Creating an Organization under the Root Organization 5 If the default server pool in the root organization has an available server, Cisco UCS Manager associates that server with the service profile and discontinues the search. If the default pool does not have an available server, Cisco UCS Manager returns an allocation error. Example: Server Pool Name Resolution in a Multi-Level Hierarchy In this example, each organization includes at least one suborganization. For example, a company could create organizations for each major division in the company and for subdivisions of those divisions. In this configuration, each organization has access to its local policies and resource pools and to the resource pools in the parent hierarchy. In this example, the Finance organization includes two sub-organizations, AccountsPayable and AccountsReceivable. A service profile in the AccountsPayable organization is configured to use servers from the AP server pool. When resource pools and policies are assigned to the service profile, the following occurs: 1 Cisco UCS Manager checks for an available server in the AP server pool defined in the service profile. 2 If the AP server pool has an available server, Cisco UCS Manager associates that server with the service profile and discontinues the search. If the pool does not have an available server, Cisco UCS Manager moves one level up the hierarchy and checks the Finance organization for a pool with the same name. 3 If the Finance organization includes a pool with the same name and that pool has an available server, Cisco UCS Manager associates that server with the service profile and discontinues the search. If the pool does not have an available server, Cisco UCS Manager moves one level up in the hierarchy and checks the root organization for a pool with the same name. 4 If the root organization includes a pool with the same name and that pool has an available server, Cisco UCS Manager associates that server with the service profile and discontinues the search. If the pool does not have an available server, Cisco UCS Manager returns to the AccountsPayable organization to check the default server pool. 5 If the default pool in the AccountsPayable organization has an available server, Cisco UCS Manager associates that server with the service profile and discontinues the search. If the default pool does not have an available server, Cisco UCS Manager moves one level up in the hierarchy and checks the default server pool in the Finance organization. 6 If the default pool in the Finance organization has an available server, Cisco UCS Manager associates that server with the service profile and discontinues the search. If the default pool does not have an available server, Cisco UCS Manager moves one level up in the hierarchy and checks the default server pool in the root organization. 7 If the default server pool in the root organization has an available server, Cisco UCS Manager associates that server with the service profile and discontinues the search. If the default pool does not have an available server, Cisco UCS Manager returns an allocation error. Creating an Organization under the Root Organization Procedure Step 1 Step 2 On the toolbar, choose New > Create Organization. In the Name field of the Create Organization dialog box, enter a unique name for the organization. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 157 Creating an Organization under a Sub-Organization This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Step 3 Step 4 In the Description field, enter a description for the organization. Click OK. Creating an Organization under a Sub-Organization Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 In the Servers tab, expand Service Profiles > root. You can also access the Sub-Organizations node under the Policies or Pools nodes. Step 3 Expand the Sub-Organizations node and do one of the following: • To create an organization directly under root, right-click Sub-Organizations and choose Create Organization. • To create an organization under a lower-level sub-organization, expand the sub-organization nodes in the hierarchy and then right-click the sub-organization under which you want to create the new organization and choose Create Organization. Step 4 In the Name field of the Create Organization dialog box, enter a unique name for the organization. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Step 5 Step 6 In the Description field, enter a description for the organization. Click OK. Deleting an Organization Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Navigate to the organization that you want to delete. Right-click the organization and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 158 OL-25712-04 CHAPTER 10 Configuring Role-Based Access Control This chapter includes the following sections: • Role-Based Access Control, page 159 • User Accounts for Cisco UCS Manager , page 159 • User Roles, page 162 • User Locales, page 166 • Configuring User Roles, page 167 • Configuring Locales, page 169 • Configuring Locally Authenticated User Accounts, page 171 • Password Profile for Locally Authenticated Users, page 177 • Monitoring User Sessions, page 180 Role-Based Access Control Role-Based Access Control (RBAC) is a method of restricting or authorizing system access for users based on user roles and locales. A role defines the privileges of a user in the system and the locale defines the organizations (domains) that a user is allowed access. Because users are not directly assigned privileges, management of individual user privileges is simply a matter of assigning the appropriate roles and locales. A user is granted write access to desired system resources only if the assigned role grants the access privileges and the assigned locale allows access. For example, a user with the Server Administrator role in the Engineering organization could update server configurations in the Engineering organization but could not update server configurations in the Finance organization unless the locales assigned to the user include the Finance organization. User Accounts for Cisco UCS Manager User accounts are used to access the system. Up to 48 user accounts can be configured in each Cisco UCS domain. Each user account must have a unique username and password. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 159 User Accounts for Cisco UCS Manager A user account can be set with a SSH public key. The public key can be set in either of the two formats: OpenSSH and SECSH. Admin Account Each Cisco UCS domain has an admin account. The admin account is a default user account and cannot be modified or deleted. This account is the system administrator or superuser account and has full privileges. There is no default password assigned to the admin account; you must choose the password during the initial system setup. The admin account is always active and does not expire. You cannot configure the admin account as inactive. Locally Authenticated User Accounts A locally authenticated user account is authenticated directly through the fabric interconnect and can be enabled or disabled by anyone with admin or aaa privileges. Once a local user account is disabled, the user cannot log in. Configuration details for disabled local user accounts are not deleted by the database. If you re-enable a disabled local user account, the account becomes active again with the existing configuration, including username and password. Remotely Authenticated User Accounts A remotely authenticated user account is any user account that is authenticated through LDAP, RADIUS, or TACACS+. If a user maintains a local user account and a remote user account simultaneously, the roles defined in the local user account override those maintained in the remote user account. Expiration of User Accounts User accounts can be configured to expire at a predefined time. When the expiration time is reached, the user account is disabled. By default, user accounts do not expire. Note After you configure a user account with an expiration date, you cannot reconfigure the account to not expire. You can, however, configure the account with the latest expiration date available. Guidelines for Cisco UCS Manager Usernames The username is also used as the login ID for Cisco UCS Manager. When you assign usernames to Cisco UCS Manager user accounts, consider the following guidelines and restrictions: • The login ID can contain between 1 and 32 characters, including the following: ◦ Any alphabetic character ◦ Any digit ◦ _ (underscore) ◦ - (dash) ◦ . (dot) Cisco UCS Manager GUI Configuration Guide, Release 2.0 160 OL-25712-04 User Accounts for Cisco UCS Manager • The unique username for each user account cannot be all-numeric. You cannot create a local user with an all-numeric username. • The unique username must start with an alphabetic character. It cannot start with a number or a special character, such as an underscore. After you create a user account, you cannot change the username. You must delete the user account and create a new one. Reserved Words: Locally Authenticated User Accounts The following words cannot be used when creating a local user account in Cisco UCS Manager. • root • bin • daemon • adm • ip • sync • shutdown • halt • news • uucp • operator • games • gopher • nobody • nscd • mailnull • mail • rpcuser • rpc • mtsuser • ftpuser • ftp • man • sys • samdme Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 161 User Roles • debug Guidelines for Cisco UCS Manager Passwords A password is required for each locally authenticated user account. A user with admin or aaa privileges can configure Cisco UCS Manager to perform a password strength check on user passwords. If the password strength check is enabled, each user must have a strong password. Cisco recommends that each user have a strong password. If you enable the password strength check for locally authenticated users, Cisco UCS Manager rejects any password that does not meet the following requirements: • Must contain a minimum of 8 characters and a maximum of 64 characters. • Must contain at least three of the following: ◦ Lower case letters ◦ Upper case letters ◦ Digits ◦ Special characters • Must not contain a character that is repeated more than 3 times consecutively, such as aaabbb. • Must not be identical to the username or the reverse of the username. • Must pass a password dictionary check. For example, the password must not be based on a standard dictionary word. • Must not contain the following symbols: $ (dollar sign), ? (question mark), and = (equals sign). • Should not be blank for local user and admin accounts. Web Session Limits for User Accounts Web session limits are used by Cisco UCS Manager to restrict the number of web sessions (both GUI and XML) a given user account is permitted to access at any one time. By default, the number of concurrent web sessions allowed by Cisco UCS Manager is set to 32; although this value can be configured up to the system maximum of 256. User Roles User roles contain one or more privileges that define the operations allowed for the user who is assigned the role. A user can be assigned one or more roles. A user assigned multiple roles has the combined privileges of all assigned roles. For example, if Role1 has storage related privileges, and Role2 has server related privileges, users who are assigned to both Role1 and Role2 have storage and server related privileges. A Cisco UCS domain can contain up to 48 user roles, including the default user roles. All roles include read access to all configuration settings in the Cisco UCS domain. The difference between the read-only role and other roles is that a user who is only assigned the read-only role cannot modify the system state. A user assigned another role can modify the system state in that user's assigned area or areas. Cisco UCS Manager GUI Configuration Guide, Release 2.0 162 OL-25712-04 User Roles Roles can be created, modified to add new or remove existing privileges, or deleted. When a role is modified, the new privileges are applied to all users assigned to that role. Privilege assignment is not restricted to the privileges defined for the default roles. That is, you can use a custom set of privileges to create a unique role. For example, the default Server Administrator and Storage Administrator roles have different set of privileges, but a new Server and Storage Administrator role can be created that combines the privileges of both roles. If a role is deleted after it has been assigned to users, it is also deleted from those user accounts. User profiles on AAA servers (RADIUS or TACACS+) should be modified to add the roles corresponding to the privileges granted to that user. The attribute is used to store the role information. The AAA servers return this attribute with the request and parse it to get the roles. LDAP servers return the roles in the user profile attributes. Note If a local user account and a remote user account have the same username, any roles assigned to the remote user are overridden by those assigned to the local user. Default User Roles The system contains the following default user roles: AAA Administrator Read-and-write access to users, roles, and AAA configuration. Read access to the rest of the system. Administrator Complete read-and-write access to the entire system. The default admin account is assigned this role by default and it cannot be changed. Facility Manager Read-and-write access to power management operations through the power-mgmt privilege. Read access to the rest of the system. Network Administrator Read-and-write access to fabric interconnect infrastructure and network security operations. Read access to the rest of the system. Operations Read-and-write access to systems logs, including the syslog servers, and faults. Read access to the rest of the system. Read-Only Read-only access to system configuration with no privileges to modify the system state. Server Equipment Administrator Read-and-write access to physical server related operations. Read access to the rest of the system. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 163 User Roles Server Profile Administrator Read-and-write access to logical server related operations. Read access to the rest of the system. Server Security Administrator Read-and-write access to server security related operations. Read access to the rest of the system. Storage Administrator Read-and-write access to storage operations. Read access to the rest of the system. Reserved Words: User Roles The following words cannot be used when creating custom roles in Cisco UCS Manager. • network-admin • network-operator • vdc-admin • vdc-operator • server-admin Privileges Privileges give users assigned to user roles access to specific system resources and permission to perform specific tasks. The following table lists each privilege and the user role given that privilege by default. Table 8: User Privileges Privilege Description Default Role Assignment aaa System security and AAA AAA Administrator admin System administration Administrator ext-lan-config External LAN configuration Network Administrator ext-lan-policy External LAN policy Network Administrator ext-lan-qos External LAN QoS Network Administrator ext-lan-security External LAN security Network Administrator ext-san-config External SAN configuration Storage Administrator ext-san-policy External SAN policy Storage Administrator ext-san-qos External SAN QoS Storage Administrator Cisco UCS Manager GUI Configuration Guide, Release 2.0 164 OL-25712-04 User Roles Privilege Description Default Role Assignment ext-san-security External SAN security Storage Administrator fault Alarms and alarm policies Operations operations Logs and Smart Call Home Operations pod-config Pod configuration Network Administrator pod-policy Pod policy Network Administrator pod-qos Pod QoS Network Administrator pod-security Pod security Network Administrator power-mgmt Read-and-write access to power management operations Facility Manager read-only Read-only access Read-Only Read-only cannot be selected as a privilege; it is assigned to every user role. server-equipment Server hardware management Server Equipment Administrator server-maintenance Server maintenance Server Equipment Administrator server-policy Server policy Server Equipment Administrator server-security Server security Server Security Administrator service-profile-config Service profile configuration Server Profile Administrator service-profile-config-policy Service profile configuration policy Server Profile Administrator service-profile-ext-access Service profile end point access Server Profile Administrator service-profile-network Service profile network Network Administrator service-profile-network-policy Service profile network policy Network Administrator service-profile-qos Service profile QoS Network Administrator service-profile-qos-policy Service profile QoS policy Network Administrator service-profile-security Service profile security Server Security Administrator service-profile-security-policy Service profile security policy Server Security Administrator Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 165 User Locales Privilege Description Default Role Assignment service-profile-server Service profile server management Server Profile Administrator service-profile-server-oper Service profile consumer Server Profile Administrator service-profile-server-policy Service profile pool policy Server Security Administrator service-profile-storage Service profile storage Storage Administrator service-profile-storage-policy Service profile storage policy Storage Administrator User Locales A user can be assigned one or more locales. Each locale defines one or more organizations (domains) the user is allowed access, and access would be limited to the organizations specified in the locale. One exception to this rule is a locale without any organizations, which gives unrestricted access to system resources in all organizations. A Cisco UCS domain can contain up to 48 user locales. Users with AAA privileges (AAA Administrator role) can assign organizations to the locale of other users. The assignment of organizations is restricted to only those in the locale of the user assigning the organizations. For example, if a locale contains only the Engineering organization then a user assigned that locale can only assign the Engineering organization to other users. Note You cannot assign a locale to users with one or more of the following privileges: • aaa • admin • operations You can hierarchically manage organizations. A user that is assigned at a top level organization has automatic access to all organizations under it. For example, an Engineering organization can contain a Software Engineering organization and a Hardware Engineering organization. A locale containing only the Software Engineering organization has access to system resources only within that organization; however, a locale that contains the Engineering organization has access to the resources for both the Software Engineering and Hardware Engineering organizations. Cisco UCS Manager GUI Configuration Guide, Release 2.0 166 OL-25712-04 Configuring User Roles Configuring User Roles Creating a User Role Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > User Management > User Services. Right-click User Services and choose Create Role. You can also right-click Roles to access that option. Step 4 In the Create Role dialog box, complete the following fields: Name Description Name field A user-defined name for this user role. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Privileges list box A list of the privileges defined in the system. Click a privilege to view a description of that privilege. Check the check box to assign that privilege to the selected user. Help Section Description field Step 5 A description of the most recent privilege you clicked in the Privileges list box. Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 167 Configuring User Roles Adding Privileges to a User Role Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 Step 6 On the Admin tab, expand All > User Management > User Services. Expand the Roles node. Choose the role to which you want to add privileges. In the General tab, check the boxes for the privileges you want to add to the role. Click Save Changes. Removing Privileges from a User Role Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 Step 6 On the Admin tab, expand All > User Management > User Services. Expand the Roles node. Choose the role from which you want to remove privileges. In the General tab, uncheck the boxes for the privileges you want to remove from the role. Click Save Changes. Deleting a User Role When you delete a user role, Cisco UCS Manager removes that role from all user accounts to which the role has been assigned. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 On the Admin tab, expand All > User Management > User Services. Expand the Roles node. Right-click the role you want to delete and choose Delete. In the Delete dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 168 OL-25712-04 Configuring Locales Configuring Locales Creating a Locale Before You Begin One or more organizations must exist before you create a locale. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > User Services. Right-click Locales and choose Create a Locale. In the Create Locale page, do the following: a) In the Name field, enter a unique name for the locale. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. b) Click Next. Step 5 In the Assign Organizations dialog box, do the following: a) b) c) d) e) Step 6 Expand the Organizations area to view the organizations in the Cisco UCS domain. Expand the root node to see the sub-organizations. Click an organization that you want to assign to the locale. Drag the organization from the Organizations area and drop it into the design area on the right. Repeat Steps b and c until you have assigned all desired organizations to the locale. Click Finish. What to Do Next Add the locale to one or more user accounts. For more information, see Changing the Locales Assigned to a Locally Authenticated User Account, on page 175. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 169 Configuring Locales Assigning an Organization to a Locale Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > User Services. Expand the Locales node and click the locale to which you want to add an organization. In the Work pane, click the General tab. Step 5 Step 6 In the Organizations area, click + on the table icon bar. In the Assign Organizations dialog box, do the following: a) b) c) d) e) Step 7 Expand the Organizations area to view the organizations in the Cisco UCS domain. Expand the root node to see the sub-organizations. Click an organization that you want to assign to the locale. Drag the organization from the Organizations area and drop it into the design area on the right. Repeat Steps b and c until you have assigned all desired organizations to the locale. Click OK. Deleting an Organization from a Locale Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > User Services. Expand the Locales node and click the locale from which you want to delete an organization. In the Work pane, click the General tab. Step 5 In the Organizations area, right-click the organization that you want to delete from the locale and choose Delete. Click Save Changes. Step 6 Cisco UCS Manager GUI Configuration Guide, Release 2.0 170 OL-25712-04 Configuring Locally Authenticated User Accounts Deleting a Locale Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 On the Admin tab, expand All > User Management > User Services. Expand the Locales node. Right-click the locale you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Configuring Locally Authenticated User Accounts Creating a User Account At a minimum, we recommend that you create the following users: • Server administrator account • Network administrator account • Storage administrator Before You Begin Perform the following tasks, if the system includes any of the following: • Remote authentication services, ensure the users exist in the remote authentication server with the appropriate roles and privileges. • Multi-tenancy with organizations, create one or more locales. If you do not have any locales, all users are created in root and are assigned roles and privileges in all organizations. • SSH authentication, obtain the SSH key. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > User Management > User Services. Right-click User Services and choose Create User to open the User Properties dialog box. You can also right-click Locally Authenticated Users to access that option. Step 4 Complete the following fields with the required information about the user: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 171 Configuring Locally Authenticated User Accounts Name Description Login ID field The account name that is used when logging into this account. This account must be unique and meet the guidelines and restrictions for Cisco UCS Manager user accounts. • The login ID can contain between 1 and 32 characters, including the following: ◦ Any alphabetic character ◦ Any digit ◦ _ (underscore) ◦ - (dash) ◦ . (dot) • The unique username for each user account cannot be all-numeric. You cannot create a local user with an all-numeric username. • The unique username must start with an alphabetic character. It cannot start with a number or a special character, such as an underscore. After you save the user, the login ID cannot be changed. You must delete the user account and create a new one. First Name field The first name of the user. This field can contain up to 32 characters. Last Name field The last name of the user. This field can contain up to 32 characters. Email field The email address for the user. Phone field The telephone number for the user. Cisco UCS Manager GUI Configuration Guide, Release 2.0 172 OL-25712-04 Configuring Locally Authenticated User Accounts Name Description Password field The password associated with this account. If password strength check is enabled, a user's password must be strong and Cisco UCS Manager rejects any password that does not meet the following requirements: • Must contain a minimum of 8 characters and a maximum of 64 characters. • Must contain at least three of the following: ◦ Lower case letters ◦ Upper case letters ◦ Digits ◦ Special characters • Must not contain a character that is repeated more than 3 times consecutively, such as aaabbb. • Must not be identical to the username or the reverse of the username. • Must pass a password dictionary check. For example, the password must not be based on a standard dictionary word. • Must not contain the following symbols: $ (dollar sign), ? (question mark), and = (equals sign). • Should not be blank for local user and admin accounts. Confirm Password field The password a second time for confirmation purposes. Account Status field If the status is set to Active, a user can log into Cisco UCS Manager with this login ID and password. Account Expires check box If checked, this account expires and cannot be used after the date specified in the Expiration Date field. Note Expiration Date field After you configure a user account with an expiration date, you cannot reconfigure the account to not expire. You can, however, configure the account with the latest expiration date available. The date on which the account expires. The date should be in the format yyyy-mm-dd. Click the down arrow at the end of this field to view a calendar that you can use to select the expiration date. Note Cisco UCS Manager GUI displays this field when you check the Account Expires check box. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 173 Configuring Locally Authenticated User Accounts Step 5 Step 6 Step 7 In the Roles area, check one or more boxes to assign roles and privileges to the user account. Note Do not assign locales to users with an admin or aaa role. (Optional) If the system includes organizations, check one or more check boxes in the Locales area to assign the user to the appropriate locales. In the SSH area, complete the following fields: a) In the Type field, do the following: • Password Required—The user must enter a password when they log in. • Key—SSH encryption is used when this user logs in. b) If you chose Key, enter the SSH key in the SSH data field. Step 8 Click OK. Enabling the Password Strength Check for Locally Authenticated Users You must be a user with admin or aaa privileges to enable the password strength check. If the password strength check is enabled, Cisco UCS Manager does not permit a user to choose a password that does not meet the guidelines for a strong password. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > User Services. Click the Locally Authenticated Users node. In the Work pane, check the Password Strength Check check box in the Properties area. Step 5 Click Save Changes. Setting the Web Session Limits for Cisco UCS Manager GUI Users Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > Communication Management > Communication Services. Click the Communication Services tab. In the Web Session Limits area, complete the following fields: Cisco UCS Manager GUI Configuration Guide, Release 2.0 174 OL-25712-04 Configuring Locally Authenticated User Accounts Name Description Maximum Sessions Per User field The maximum number of concurrent HTTP and HTTPS sessions allowed for each user. Enter an integer between 1 and 256. Maximum Sessions field The maximum number of concurrent HTTP and HTTPS sessions allowed for all users within the system. Enter an integer between 1 and 256. Step 5 Click Save Changes. Changing the Locales Assigned to a Locally Authenticated User Account Note Do not assign locales to users with an admin or aaa role. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > User Services > Locally Authenticated Users. Click the user account that you want to modify. In the Work pane, click the General tab. Step 5 In the Locales area, do the following: • To assign a new locale to the user account, check the appropriate check boxes. • To remove a locale from the user account, uncheck the appropriate check boxes. Step 6 Click Save Changes. Changing the Roles Assigned to a Locally Authenticated User Account Changes in user roles and privileges do not take effect until the next time the user logs in. If a user is logged in when you assign a new role to or remove an existing role from a user account, the active session continues with the previous roles and privileges. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 175 Configuring Locally Authenticated User Accounts Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > User Services > Locally Authenticated Users. Click the user account that you want to modify. In the Work pane, click the General tab. Step 5 In the Roles area, do the following: • To assign a new role to the user account, check the appropriate check boxes. • To remove a role from the user account, uncheck the appropriate check boxes. Step 6 Click Save Changes. Enabling a User Account You must be a user with admin or aaa privileges to enable or disable a local user account. Before You Begin Create a local user account. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > User Services > Locally Authenticated Users. Click the user that you want to enable. In the Work pane, click the General tab. Step 5 Step 6 In the Account Status field, click the active radio button. Click Save Changes. Disabling a User Account You must be a user with admin or aaa privileges to enable or disable a local user account. Note If you change the password on a disabled account through the Cisco UCS Manager GUI, the user cannot use this changed password after you enable the account and make it active. The user must enter the required password again after the account is enabled and made active. Cisco UCS Manager GUI Configuration Guide, Release 2.0 176 OL-25712-04 Password Profile for Locally Authenticated Users Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > User Services > Locally Authenticated Users. Click the user that you want to disable. In the Work pane, click the General tab. Step 5 In the Account Status field, click the inactive radio button. The admin user account is always set to active. It cannot be modified. Step 6 Click Save Changes. Clearing the Password History for a Locally Authenticated User Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 On the Admin tab, expand All > User Management > User Services > Locally Authenticated Users. Click the user for whom you want to clear the password history. In the Actions area, click Clear Password History. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Deleting a Locally Authenticated User Account Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 Step 5 On the Admin tab, expand All > User Management > User Services. Expand the Locally Authenticated Users node. Right-click the user account you want to delete and choose Delete. In the Delete dialog box, click Yes. Password Profile for Locally Authenticated Users The password profile contains the password history and password change interval properties for all locally authenticated users of Cisco UCS Manager. You cannot specify a different password profile for each locally authenticated user. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 177 Password Profile for Locally Authenticated Users Note You must have admin or aaa privileges to change the password profile properties. Except for password history, these properties do not apply to users with admin or aaa privileges. Password History Count The password history count allows you to prevent locally authenticated users from reusing the same password over and over again. When this property is configured, Cisco UCS Manager stores passwords that were previously used by locally authenticated users up to a maximum of 15 passwords. The passwords are stored in reverse chronological order with the most recent password first to ensure that the only the oldest password can be reused when the history count threshold is reached. A user must create and use the number of passwords configured in the password history count before being able to reuse one. For example, if you set the password history count to 8, a locally authenticated user cannot reuse the first password until after the ninth password has expired. By default, the password history is set to 0. This value disables the history count and allows users to reuse previously passwords at any time. If necessary, you can clear the password history count for a locally authenticated user and enable reuse of previous passwords. Password Change Interval The password change interval enables you to restrict the number of password changes a locally authenticated user can make within a given number of hours. The following table describes the two configuration options for the password change interval. Interval Configuration Description Example No password change allowed This option does not passwords for locally authenticated users to be changed within a specified number of hours after a password change. For example, to prevent passwords from being changed within 48 hours after a locally authenticated user changes his or her password, set the following: You can specify a no change interval between 1 and 745 hours. By default, the no change interval is 24 hours. • Change during interval to disable This option specifies the maximum number of times that passwords for locally authenticated users can be changed within a pre-defined interval. For example, to allow to be changed a maximum of once within 24 hours after a locally authenticated user changes his or her password, set the following: You can specify a change interval between 1 and 745 hours and a maximum number of password changes between 0 and 10. By default, a locally authenticated user is permitted a maximum of 2 password changes within a 48 hour interval. • Change during interval to enable Password changes allowed within change interval • No change interval to 48 • Change count to 1 • Change interval to 24 Cisco UCS Manager GUI Configuration Guide, Release 2.0 178 OL-25712-04 Password Profile for Locally Authenticated Users Configuring the Maximum Number of Password Changes for a Change Interval You must have admin or aaa privileges to change the password profile properties. Except for password history, these properties do not apply to users with admin or aaa privileges. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > User Services. Click the Locally Authenticated Users node. In the Password Profile area, do the following: a) In the Change During Interval field, click Enable. b) In the Change Count field, enter the maximum number of times a locally authenticated user can change his or her password during the Change Interval. This value can be anywhere from 0 to 10. c) In the Change Interval field, enter the maximum number of hours over which the number of password changes specified in the Change Count field are enforced. This value can be anywhere from 1 to 745 hours. For example, if this field is set to 48 and theChange Count field is set to 2, a locally authenticated user can make no more than 2 password changes within a 48 hour period. Step 5 Click Save Changes. Configuring a No Change Interval for Passwords You must have admin or aaa privileges to change the password profile properties. Except for password history, these properties do not apply to users with admin or aaa privileges. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > User Services. Click the Locally Authenticated Users node. In the Password Profile area, do the following: a) In the Change During Interval field, click Disable. b) In the No Change Interval field, enter the minimum number of hours that a locally authenticated user must wait before changing a newly created password. This value can be anywhere from 1 to 745 hours. This interval is ignored if the Change During Interval property is not set to Disable. Step 5 Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 179 Monitoring User Sessions Configuring the Password History Count You must have admin or aaa privileges to change the password profile properties. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > User Management > User Services. Click the Locally Authenticated Users node. In the Password Profile area, enter the number of unique passwords that a locally authenticated user must create before that user can reuse a previously used password in the History Count field. This value can be anywhere from 0 to 15. By default, the History Count field is set to 0, which disables the history count and allows users to reuse previously used passwords at any time. Step 5 Click Save Changes. Monitoring User Sessions You can monitor Cisco UCS Manager sessions for both locally authenticated users and remotely authenticated users, whether they logged in through the CLI or the GUI. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 In the Admin tab, expand All > User Management. Click the User Services node. In the Work pane, click the Sessions tab. The tab displays the following details of user sessions: Name Description Name column The name for the session. User column The username that is involved in the session. Fabric ID column The fabric interconnect that the user logged in to for the session. Login Time column The date and time the session started. Cisco UCS Manager GUI Configuration Guide, Release 2.0 180 OL-25712-04 Monitoring User Sessions Name Description Refresh Period column When a web client connects to Cisco UCS Manager, the client needs to send refresh requests to Cisco UCS Manager to keep the web session active. This option specifies the maximum amount of time allowed between refresh requests for a user in this domain. If this time limit is exceeded, Cisco UCS Manager considers the web session to be inactive, but it does not terminate the session. Session Timeout column The maximum amount of time that can elapse after the last refresh request before Cisco UCS Manager considers a web session to have ended. If this time limit is exceeded, Cisco UCS Manager automatically terminates the web session. Terminal Type column The kind of terminal the user is logged in through. Host column The IP address from which the user is logged in. Current Session column If this column displays Y, the associated user session is currently active. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 181 Monitoring User Sessions Cisco UCS Manager GUI Configuration Guide, Release 2.0 182 OL-25712-04 CHAPTER 11 Managing Firmware This chapter includes the following sections: • Overview of Firmware, page 183 • Firmware Image Management, page 184 • Firmware Versions, page 186 • Firmware Upgrades, page 187 • Firmware Downgrades, page 199 • Completing the Prerequisites for Upgrading the Firmware, page 199 • Downloading and Managing Firmware Packages, page 204 • Directly Upgrading Firmware at Endpoints, page 210 • Upgrading Firmware through Service Profiles, page 222 • Verifying Firmware Versions on Components, page 230 • Managing the Capability Catalog, page 230 • Updating Management Extensions, page 235 Overview of Firmware Cisco UCS uses firmware obtained from and certified by Cisco to support the endpoints in a Cisco UCS domain. Each endpoint is a component in the Cisco UCS domain that requires firmware to function. The upgrade order for the endpoints in a Cisco UCS domain depends upon the upgrade path, but includes the following: • Cisco UCS Manager • I/O modules • Fabric interconnects • Endpoints physically located on adapters, including NIC and HBA firmware, and Option ROM (where applicable) that can be upgraded through firmware packages included in a service profile Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 183 Firmware Image Management • Endpoints physically located on servers, such as the BIOS, storage controller (RAID controller), and Cisco Integrated Management Controller (CIMC) that can be upgraded through firmware packages included in a service profile See the required order of steps for your upgrade path to determine the appropriate order in which to upgrade the endpoints in your Cisco UCS domain. Note Beginning with Cisco UCS, Release 1.4(1), Cisco is releasing firmware upgrades in multiple bundles, rather than one large firmware package. For more information see Firmware Image Management, on page 184. Cisco maintains a set of best practices for managing firmware images and updates in this document and in the following technical note: Unified Computing System Firmware Management Best Practices. This document uses the following definitions for managing firmware: Upgrade Changes the firmware running on an endpoint to another image, such as a release or patch. Upgrade includes both update and activation. Update Copies the firmware image to the backup partition on an endpoint. Activate Sets the firmware in the backup partition as the active firmware version on the endpoint. Activation can require or cause the reboot of an endpoint. For Management Extensions and Capability Catalog upgrades, update and activate occur simultaneously. You only need to update or activate those upgrades. You do not need to perform both steps. Firmware Image Management Cisco delivers all firmware updates to Cisco UCS components in bundles of images. Cisco UCS firmware updates are available to be downloaded in the following bundles: Cisco UCS Infrastructure Software Bundle This bundle includes the following firmware images that are required to update the following components: • Cisco UCS Manager software • Kernel and system firmware for the fabric interconnects • I/O module firmware Cisco UCS Manager GUI Configuration Guide, Release 2.0 184 OL-25712-04 Firmware Image Management Cisco UCS B-Series Blade Server Software Bundle This bundle includes the following firmware images that are required to update the firmware for the blade servers in a Cisco UCS domain. In addition to the bundles created for a release, these bundles can also be released between infrastructure bundles to enable Cisco UCS Manager to support a blade server that is not included in the most recent infrastructure bundle. • CIMC firmware • BIOS firmware • Adapter firmware • Board controller firmware • Third-party firmware images required by the new server Cisco UCS C-Series Rack-Mount Server Software Bundle This bundle includes the following firmware images that are required to update components on rack-mount servers that have been integrated with and are managed by Cisco UCS Manager: • CIMC firmware • BIOS firmware • Adapter firmware • Storage controller firmware Note You cannot use this bundle for standalone C-series servers. The firmware management system in those servers cannot interpret the header required by Cisco UCS Manager. For information on how to upgrade standalone C-series servers, see the C-series configuration guides. Cisco also provides release notes, which you can obtain on the same website from which you obtained the bundles. Firmware Image Headers Every firmware image has a header, which includes the following: • Checksum • Version information • Compatibility information that the system can use to verify the compatibility of component images and any dependencies Firmware Image Catalog Cisco UCS Manager provides you with two views of the catalog of firmware images and their contents that have been downloaded to the fabric interconnect: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 185 Firmware Versions Packages This view provides you with a read-only representation of the firmware bundles that have been downloaded onto the fabric interconnect. This view is sorted by image, not by the contents of the image. For packages, you can use this view to see which component images are in each downloaded firmware bundle. Images The images view lists the component images available on the system. You cannot use this view to see complete firmware bundles or to group the images by bundle. The information available about each component image includes the name of the component, the image size, the image version, and the vendor and model of the component. You can use this view to identify the firmware updates available for each component. You can also use this view to delete obsolete and unneeded images. Cisco UCS Manager deletes a package after all images in the package have been deleted. Tip Cisco UCS Manager stores the images in bootflash on the fabric interconnect. In a cluster system, space usage in bootflash on both fabric interconnects is the same, because all images are synchronized between them. If Cisco UCS Manager reports that the bootflash is out of space, delete obsolete images to free up space. Firmware Versions The firmware version terminology used depends upon the type of endpoint, as follows: Firmware Versions in CIMC, I/O Modules, and Adapters Each CIMC, I/O module, and adapter has two slots for firmware in flash. Each slot holds a version of firmware. One slot is active and the other is the backup slot. A component boots from whichever slot is designated as active. The following firmware version terminology is used in Cisco UCS Manager: Running Version The running version is the firmware that is active and in use by the endpoint. Startup Version The startup version is the firmware that will be used when the endpoint next boots up. Cisco UCS Manager uses the activate operation to change the startup version. Backup Version The backup version is the firmware in the other slot and is not in use by the endpoint. This version can be firmware that you have updated to the endpoint but have not yet activated, or it can be an older firmware version that was replaced by a recently activated version. Cisco UCS Manager uses the update operation to replace the image in the backup slot. If the endpoint cannot boot from the startup version, it boots from the backup version. Cisco UCS Manager GUI Configuration Guide, Release 2.0 186 OL-25712-04 Firmware Upgrades Firmware Versions in the Fabric Interconnect and Cisco UCS Manager You can only activate the fabric interconnect firmware and Cisco UCS Manager on the fabric interconnect. The fabric interconnect and Cisco UCS Manager firmware do not have backup versions, because all the images are stored on the fabric interconnect. As a result, the number of bootable fabric interconnect images is not limited to two, like the server CIMC and adapters. Instead, the number of bootable fabric interconnect images is limited by the available space in the memory of the fabric interconnect and the number of images stored there. The fabric interconnect and Cisco UCS Manager firmware have running and startup versions of the kernel and system firmware. The kernel and system firmware must run the same versions of firmware. Firmware Upgrades Cisco UCS firmware is upgraded through a combination of the following methods: • Direct upgrade at the endpoints. For a cluster configuration with two fabric interconnects, a direct upgrade can be minimally disruptive to data traffic. However, it requires that the Cisco UCS domain does not include firmware policies for those endpoints that you upgrade directly. You cannot avoid disruption to traffic in a Cisco UCS domain with only one fabric interconnect. Note Direct upgrade is not available for all endpoints, including the server BIOS, storage controller, HBA firmware, and HBA option ROM. You must upgrade those endpoints through the host firmware package included in the service profile associated with the server. • Upgrades to server endpoints through service profiles that include a host firmware package, a management firmware package, or both. This method can be disruptive to data traffic and should be performed during a maintenance window. Note The Cisco UCS Manager GUI does not allow you to choose options that a release does not support. If a Cisco UCS domain includes hardware that is not supported in the release to which you are upgrading, Cisco UCS Manager GUI does not display the firmware as an option for that hardware or allow you to upgrade to it. Cautions, Guidelines, and Best Practices for Firmware Upgrades Before you upgrade the firmware for any endpoint in a Cisco UCS domain, consider the following cautions, guidelines, and best practices: Note The Cisco UCS Manager GUI does not allow you to choose options that a release does not support. If a Cisco UCS domain includes hardware that is not supported in the release to which you are upgrading, Cisco UCS Manager GUI does not display the firmware as an option for that hardware or allow you to upgrade to it. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 187 Firmware Upgrades Configuration Changes and Settings that Can Impact Upgrades Depending upon the configuration of your Cisco UCS domain, the following changes may require you to make configuration changes after you upgrade. To avoid faults and other issues, we recommend that you make any required changes before you upgrade. Overlapping FCoE VLAN IDs and Ethernet VLAN IDs Are No Longer Allowed with Cisco UCS Release 2.0 Caution In Cisco UCS 1.4 and earlier releases, Ethernet VLANs and FCoE VLANs could have overlapping VLAN IDs. However, starting with Cisco UCS release 2.0, overlapping VLAN IDs are not allowed. If Cisco UCS Manager detects overlapping VLAN IDs during an upgrade, it raises a critical fault. If you do not reconfigure your VLAN IDs, Cisco UCS Manager raises a critical fault and drops Ethernet traffic on the overlapped VLANs. Therefore, we recommend that you ensure there are no overlapping Ethernet and FCoE VLAN IDs before you upgrade to Cisco UCS release 2.0. If you did not explicitly configure the FCoE VLAN ID for a VSAN in Cisco UCS 1.4 and earlier releases, Cisco UCS Manager assigned VLAN 1 as the default FCoE VLAN for the default VSAN (with default VSAN ID 1). In those releases, VLAN 1 was also used as the default VLAN for Ethernet traffic. Therefore, if you accepted the default VLAN ID for the FCoE VLAN and one or more Ethernet VLANs, you must reconfigure the VLAN IDs for either the FCoE VLAN(s) on the VSAN(s) or the Ethernet VLAN(s). For a new installation of Cisco UCS release 2.0, the default VLAN IDs are as follows: • The default Ethernet VLAN ID is 1. • The default FCoE VLAN ID is 4048. After an upgrade from Cisco UCS release 1.4, where VLAN ID 4048 was used for FCoE storage port native VLAN, to release 2.0, the default VLAN IDs are as follows: • The default Ethernet VLAN ID is 1. • The current default FCoE VLAN ID is preserved. Cisco UCS Manager raises a critical fault on the conflicting Ethernet VLAN, if any. You must change one of the VLAN IDs to a VLAN ID that is not used or reserved. Note If a Cisco UCS domain uses one of the default VLAN IDs, which results in overlapping VLANs, you can change one or more of the default VLAN IDs to any VLAN ID that is not used or reserved. In release 2.0, VLANs with IDs from 3968 to 4047 are reserved. VSANs with IDs in the Reserved Range are not Operational A VSAN with an ID in the reserved range is not operational after an upgrade. Make sure that none of the VSANs configured in Cisco UCS Manager are in the reserved range, as follows: • If you plan to use FC switch mode in a Cisco UCS domain, do not configure VSANs with an ID in the range from 3040 to 4078. • If you plan to use FC end-host mode in a Cisco UCS domain, do not configure VSANs with an ID in the range from 3840 to 4079. Cisco UCS Manager GUI Configuration Guide, Release 2.0 188 OL-25712-04 Firmware Upgrades If a VSAN has an ID in the reserved range, change that VSAN ID to any VSAN ID that is not used or reserved. All Connectivity May Be Lost During Upgrades if vNIC Failover and NIC Teaming Are Both Enabled All connectivity may be lost during firmware upgrades if you have configured both Enable Failover on one or more vNICs and you have also configured NIC teaming/bonding at the host operating system level. Please design for availability by using one or the other method, but never both. To determine whether you have enabled failover for one or more vNICs in a Cisco UCS domain, verify the configuration of the vNICs within each service profile associated with a server. For more information, see the Cisco UCS Manager configuration guide for the release that you are running. Impact of Upgrade from a Release Prior to Release 1.3(1i) An upgrade from an earlier Cisco UCS firmware release to release 1.3(1i) or higher has the following impact on the Protect Configuration property of the local disk configuration policy the first time servers are associated with service profiles after the upgrade: Unassociated Servers After you upgrade the Cisco UCS domain, the initial server association proceeds without configuration errors whether or not the local disk configuration policy matches the server hardware. Even if you enable the Protect Configuration property, Cisco UCS does not protect the user data on the server if there are configuration mismatches between the local disk configuration policy on the previous service profile and the policy in the new service profile. Note If you enable the Protect Configuration property and the local disk configuration policy encounters mismatches between the previous service profile and the new service profile, all subsequent service profile associations with the server are blocked. Associated Servers Any servers that are already associated with service profiles do not reboot after the upgrade. Cisco UCS Manager does not report any configuration errors if there is a mismatch between the local disk configuration policy and the server hardware. When a service profile is disassociated from a server and a new service profile associated, the setting for the Protect Configuration property in the new service profile takes precedence and overwrites the setting in the previous service profile. Hardware-Related Guidelines and Best Practices for Firmware Upgrades The hardware in a Cisco UCS domain can impact how you upgrade. Before you upgrade any endpoint, consider the following guidelines and best practices: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 189 Firmware Upgrades No Server or Chassis Maintenance Caution Do not remove the hardware that contains the endpoint or perform any maintenance on it until the update process has completed. If the hardware is removed or otherwise unavailable due to maintenance, the firmware update fails. This failure may corrupt the backup partition. You cannot update the firmware on an endpoint with a corrupted backup partition. Avoid Replacing RAID-Configured Hard Disks Prior to Upgrade Under the following circumstances, Cisco UCS Manager may scrub all data on a hard disk as part of the RAID synchronization process during an upgrade of the server firmware: • The hard disks in the server are configured for RAID. • One or more of the RAID-configured hard disks in the server are removed. • The hard disk or disks are replaced with hard disks that are configured with a pre-existing RAID and the local disk configuration policy included in the service profile on the server is not used to configure those hard disks. • The server firmware is upgraded, causing the server to reboot and Cisco UCS Manager to begin the RAID synchronization process. If the original hard disks contained vital data that needs to preserved, avoid inserting new hard disks that are already configured for RAID. Always Upgrade Cisco UCS Gen-2 Adapters through a Host Firmware Package You cannot upgrade Cisco UCS Gen-2 adapters directly at the endpoints. You must upgrade the firmware on those adapters through a host firmware package. Cannot Upgrade Cisco UCS 82598KR-CI 10-Gigabit Ethernet Adapter The firmware on the Cisco UCS 82598KR-CI 10-Gigabit Ethernet Adapter (N20-AI0002), Intel-based adapter card, is burned into the hardware at manufacture. You cannot upgrade the firmware on this adapter. Number of Fabric Interconnects For a cluster configuration with two fabric interconnects, you can take advantage of the failover between the fabric interconnects and perform a direct firmware upgrade of the endpoints without disrupting data traffic. However, you cannot avoid disrupting data traffic for those endpoints which must be upgraded through a host or management firmware package. For a standalone configuration with a single fabric interconnect, you can minimize the disruption to data traffic when you perform a direct firmware upgrade of the endpoints. However, you must reboot the fabric interconnect to complete the upgrade and, therefore, cannot avoid disrupting traffic. Firmware- and Software-Related Best Practices for Upgrades Before you upgrade any endpoint, consider the following guidelines and best practices: Cisco UCS Manager GUI Configuration Guide, Release 2.0 190 OL-25712-04 Firmware Upgrades Determine Appropriate Type of Firmware Upgrade for Each Endpoint Some endpoints, such as adapters and the server CIMC, can be upgraded through either a direct firmware upgrade or a firmware package included in a service profile. The configuration of a Cisco UCS domain determines how you upgrade these endpoints. If the service profiles associated with the servers include a host firmware package, upgrade the adapters for those servers through the firmware package. In the same way, if the service profiles associated with the servers include a management firmware package, upgrade the CIMC for those servers through the firmware package. Upgrades of a CIMC through a management firmware package or an adapter through a firmware package in the service profile associated with the server take precedence over direct firmware upgrades. You cannot directly upgrade an endpoint if the service profile associated with the server includes a firmware package. To perform a direct upgrade, you must remove the firmware package from the service profile. Do Not Activate All Endpoints Simultaneously in Cisco UCS Manager GUI If you use Cisco UCS Manager GUI to update the firmware, do not select ALL from the Filter drop-down list in the Activate Firmware dialog box to activate all endpoints simultaneously. Many firmware releases and patches have dependencies that require the endpoints to be activated in a specific order for the firmware update to succeed. This order can change depending upon the contents of the release or patch. Activating all endpoints does not guarantee that the updates occur in the required order and can disrupt communications between the endpoints and the fabric interconnects and Cisco UCS Manager. For information about the dependencies in a specific release or patch, see the release notes provided with that release or patch. Impact of Activation for Adapters and I/O Modules During a direct upgrade, you should configure Set Startup Version Only for an adapter. With this setting, the activated firmware moves into the pending-next-boot state, and the server is not immediately rebooted. The activated firmware does not become the running version of firmware on the adapter until the server is rebooted. You cannot configure Set Startup Version Only for an adapter in the host firmware package. If a server is not associated with a service profile, the activated firmware remains in the pending-next-boot state. Cisco UCS Manager does not reboot the endpoints or activate the firmware until the server is associated with a service profile. If necessary, you can manually reboot or reset an unassociated server to activate the firmware. When you configure Set Startup Version Only for an I/O module, the I/O module is rebooted when the fabric interconnect in its data path is rebooted. If you do not configure Set Startup Version Only for an I/O module, the I/O module reboots and disrupts traffic. In addition, if Cisco UCS Manager detects a protocol and firmware version mismatch between the fabric interconnect and the I/O module, Cisco UCS Manager automatically updates the I/O module with the firmware version that matches the firmware in the fabric interconnect and then activates the firmware and reboots the I/O module again. Select Ignore Compatibility Check When Upgrading During a direct upgrade to a newer release, we recommend that you choose Ignore Compatibility Check. Newer releases may have incompatible code with older releases. This option ensures that the upgrade can proceed and avoids compatibility issues. Disable Call Home before Upgrading to Avoid Unnecessary Alerts (Optional) When you upgrade a Cisco UCS domain, Cisco UCS Manager restarts the components to complete the upgrade process. This restart causes events that are identical to service disruptions and component failures that trigger Call Home alerts to be sent. If you do not disable Call Home before you begin the upgrade, you can ignore the alerts generated by the upgrade-related component restarts. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 191 Firmware Upgrades Required Order of Components for Firmware Activation If you upgrade firmware by individual components in a Cisco UCS domain, activate the updates in the required order for quicker activation and to avoid potential issues with conflicting firmware versions. Summary of Steps for Upgrading from Cisco UCS, Release 1.0(2) and Later 1 Download the following firmware images: • Cisco UCS Infrastructure Software Bundle—Required for all Cisco UCS domains. • Cisco UCS B-Series Blade Server Software Bundle—Required for all Cisco UCS domains that include blade servers. • Cisco UCS C-Series Rack-Mount Server Software Bundle—Only required for Cisco UCS domains that include integrated rack-mount servers. This bundle contains firmware to enable Cisco UCS Manager to manage those servers and is not applicable to standalone C-Series rack-mount servers. 2 (Optional) Disable Call Home—If the Cisco UCS domain includes Call Home or Smart Call Home, disable Call Home to ensure you do not receive unnecessary alerts when Cisco UCS Manager restarts components. 3 Update adapters, /BMC, and IOMs—If you prefer, you can upgrade the adapters in a host firmware package as part of the last upgrade step. 4 Activate adapters—Choose Ignore Compatibility Check and Set Startup Version Only when performing this step. 5 Activate /BMC—Choose Ignore Compatibility Check when performing this step. 6 Activate Cisco UCS Manager—Choose Ignore Compatibility Check when performing this step. 7 Activate I/O modules—Choose Ignore Compatibility Check and Set Startup Version Only when performing this step. 8 Activate subordinate fabric interconnect—Choose Ignore Compatibility Check when performing this step. 9 Activate primary fabric interconnect—Choose Ignore Compatibility Check when performing this step. 10 Update host firmware package(s) for servers—Must be the last firmware upgraded. We recommend that you upgrade the board controller firmware during this step to avoid an additional reboot of servers with that firmware. You must upgrade the following firmware in a host firmware package: • BIOS • Storage controller • Certain adapters 11 (Optional) Enable Call Home—If you disabled Call Home before the upgrading the firmware, enable Call Home. Summary of Upgrading from Cisco UCS, Release 1.0(1) 1 Download the following firmware images: • Cisco UCS Infrastructure Software Bundle—Required for all Cisco UCS domains. Cisco UCS Manager GUI Configuration Guide, Release 2.0 192 OL-25712-04 Firmware Upgrades • Cisco UCS B-Series Blade Server Software Bundle—Required for all Cisco UCS domains that include blade servers. • Cisco UCS C-Series Rack-Mount Server Software Bundle—Only required for Cisco UCS domains that include integrated rack-mount servers. This bundle contains firmware to enable Cisco UCS Manager to manage those servers and is not applicable to standalone C-Series rack-mount servers. 2 (Optional) Disable Call Home—If the Cisco UCS domain includes Call Home or Smart Call Home, disable Call Home to ensure you do not receive unnecessary alerts when Cisco UCS Manager restarts components. 3 Update adapters, BMC, and IOMs—If you prefer, you can upgrade the adapters in a host firmware package as part of the last upgrade step. 4 Activate adapters—Choose Ignore Compatibility Check and Set Startup Version Only when performing this step. 5 BMC—Choose Ignore Compatibility Check when performing this step. 6 Activate I/O modules—Choose Ignore Compatibility Check and Set Startup Version Only when performing this step. 7 Activate subordinate fabric interconnect—Choose Ignore Compatibility Check when performing this step. 8 Activate primary fabric interconnect—Choose Ignore Compatibility Check when performing this step. 9 Activate Cisco UCS Manager—Choose Ignore Compatibility Check when performing this step. 10 Update host firmware package(s) for servers—Must be the last firmware upgraded. We recommend that you upgrade the board controller firmware during this step to avoid an additional reboot of servers with that firmware. You must upgrade the following firmware in a host firmware package: • BIOS • Storage controller • Certain adapters 11 (Optional) Enable Call Home—If you disabled Call Home before the upgrading the firmware, enable Call Home. Required Order for Adding Support for Previously Unsupported Servers From Cisco UCS, Release 1.4(1) and later, the method for adding support for previously unsupported type of servers, such as a new blade server or a rack-mount server, to an existing Cisco UCS domain requires the following additional steps after you upgrade your existing firmware to the new release. Adding Support for a Previously Unsupported Cisco UCS Blade Server After you upgrade the firmware for the existing components, you can add support for a previously unsupported server that was released between infrastructure bundle releases. When you add the first server of a previously unsupported type of blade server, you must perform the steps to enable Cisco UCS Manager to support that type of server in the following order: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 193 Firmware Upgrades 1 Insert the blade server into the chassis as described in the server installation guide. Cisco UCS Manager cannot discover the server as it is unsupported, and the finite state machine (FSM) for the discovery fails with an unsupported server error. 2 Obtain the B-Series server bundle for the new blade server from Cisco.com and download it to the fabric interconnect. 3 Activate the Capability Catalog image from the server bundle. 4 Activate the Management Extension from the server bundle. 5 Wait for Cisco UCS Manager to retry discovery of the new server. If server discovery does not begin within a few minutes, acknowledge the server. Note You only need to perform these steps for the first server of a previously unsupported type of blade server. Cisco UCS Manager discovers all subsequent servers of that type automatically. IntegratingCisco UCS Rack-Mount Servers After you upgrade the firmware for the existing components, you can integrate one or more Cisco UCS rack-mount servers. When you integrate rack-mount servers, you must perform the steps in the following order: 1 If you have not already done so, configure the rack server discovery policy in Cisco UCS Manager. 2 Follow the instructions in the appropriate rack-mount server installation guide for installing and integrating a rack-mount server in a system managed by Cisco UCS Manager. 3 Wait for Cisco UCS Manager to discover the new server. If server discovery does not begin within a few minutes, acknowledge the server. Direct Firmware Upgrade at Endpoints If you follow the correct procedure and apply the upgrades in the correct order, a direct firmware upgrade and the activation of the new firmware version on the endpoints is minimally disruptive to traffic in a Cisco UCS domain. You can directly upgrade the firmware on the following endpoints: • Adapters • CIMCs • I/O modules • Board controllers • Cisco UCS Manager • Fabric interconnects The adapter and board controller firmware can also be upgraded through the host firmware package in the service profile. If you use a host firmware package to upgrade this firmware, you can reduce the number of times a server needs to be rebooted during the firmware upgrade process. Cisco UCS Manager GUI Configuration Guide, Release 2.0 194 OL-25712-04 Firmware Upgrades Note Upgrades of a CIMC through a management firmware package or an adapter through a firmware package in the service profile associated with the server take precedence over direct firmware upgrades. You cannot directly upgrade an endpoint if the service profile associated with the server includes a firmware package. To perform a direct upgrade, you must remove the firmware package from the service profile. Stages of a Direct Firmware Upgrade Cisco UCS Manager separates the direct upgrade process into two stages to ensure that you can push the firmware to an endpoint while the system is running without affecting uptime on the server or other endpoints. Update During this stage, the system copies the selected firmware version from the primary fabric interconnect to the backup partition in the endpoint and verifies that the firmware image is not corrupt. The update process always overwrites the firmware in the backup slot. The update stage applies only to the following endpoints: • Adapters • CIMCs • I/O modules Caution Do not remove the hardware that contains the endpoint or perform any maintenance on it until the update process has completed. If the hardware is removed or otherwise unavailable due to maintenance, the firmware update fails. This failure may corrupt the backup partition. You cannot update the firmware on an endpoint with a corrupted backup partition. Activate During this stage, the system sets the specified image version (normally the backup version) as the startup version and, if you do not specify Set Startup Version Only, immediately reboots the endpoint. When the endpoint is rebooted, the backup partition becomes the active partition, and the active partition becomes the backup partition. The firmware in the new active partition becomes the startup version and the running version. The following endpoints only require activation because the specified firmware image already exists on the endpoint: • Cisco UCS Manager • Fabric interconnects • Board controllers on those servers that support them When the firmware is activated, the endpoint is rebooted and the new firmware becomes the active kernel version and system version. If the endpoint cannot boot from the startup firmware, it defaults to the backup version and raises a fault. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 195 Firmware Upgrades Caution When you configure Set Startup Version Only for an I/O module, the I/O module is rebooted when the fabric interconnect in its data path is rebooted. If you do not configure Set Startup Version Only for an I/O module, the I/O module reboots and disrupts traffic. In addition, if Cisco UCS Manager detects a protocol and firmware version mismatch between the fabric interconnect and the I/O module, Cisco UCS Manager automatically updates the I/O module with the firmware version that matches the firmware in the fabric interconnect and then activates the firmware and reboots the I/O module again. Outage Impacts of Direct Firmware Upgrades When you perform a direct firmware upgrade on an endpoint, you can disrupt traffic or cause an outage in one or more of the endpoints in the Cisco UCS domain. Outage Impact of a Fabric Interconnect Firmware Upgrade When you upgrade the firmware for a fabric interconnect, you cause the following outage impacts and disruptions: • The fabric interconnect reboots. • The corresponding I/O modules reboot. Outage Impact of a Cisco UCS Manager Firmware Upgrade A firmware upgrade to Cisco UCS Manager causes the following disruptions: • Cisco UCS Manager GUI—All users logged in to Cisco UCS Manager GUI are logged out and their sessions ended. Any unsaved work in progress is lost. • Cisco UCS Manager CLI—All users logged in through telnet are logged out and their sessions ended. Outage Impact of an I/O Module Firmware Upgrade When you upgrade the firmware for an I/O module, you cause the following outage impacts and disruptions: • For a standalone configuration with a single fabric interconnect, data traffic is disrupted when the I/O module reboots. For a cluster configuration with two fabric interconnects, data traffic fails over to the other I/O module and the fabric interconnect in its data path. • If you activate the new firmware as the startup version only, the I/O module reboots when the corresponding fabric interconnect is rebooted. • If you activate the new firmware as the running and startup version, the I/O module reboots immediately. • An I/O module can take up to ten minutes to become available after a firmware upgrade. Outage Impact of a CIMC Firmware Upgrade When you upgrade the firmware for a CIMC in a server, you impact only the CIMC and internal processes. You do not interrupt server traffic. This firmware upgrade causes the following outage impacts and disruptions to the CIMC: Cisco UCS Manager GUI Configuration Guide, Release 2.0 196 OL-25712-04 Firmware Upgrades • Any activities being performed on the server through the KVM console and vMedia are interrupted. • Any monitoring or IPMI polling is interrupted. Outage Impact of an Adapter Firmware Upgrade If you activate the firmware for an adapter and do not configure the Set Startup Version Only option, you cause the following outage impacts and disruptions: • The server reboots. • Server traffic is disrupted. Firmware Upgrades through Service Profiles You can use service profiles to upgrade the server and adapter firmware, including the BIOS on the server, by defining the following policies and including them in the service profile associated with a server: • Host Firmware Package policy • Management Firmware Package policy Note You cannot upgrade the firmware on an I/O module, fabric interconnect, or Cisco UCS Manager through service profiles. You must upgrade the firmware on those endpoints directly. Host Firmware Package This policy enables you to specify a set of firmware versions that make up the host firmware package (also known as the host firmware pack). The host firmware includes the following firmware for server and adapter endpoints: • Adapter • BIOS • Board Controller • FC Adapters • HBA Option ROM • Storage Controller Tip You can include more than one type of firmware in the same host firmware package. For example, a host firmware package can include both BIOS firmware and storage controller firmware or adapter firmware for two different models of adapters. However, you can only have one firmware version with the same type, vendor, and model number. The system recognizes which firmware version is required for an endpoint and ignores all other firmware versions. The firmware package is pushed to all servers associated with service profiles that include this policy. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 197 Firmware Upgrades This policy ensures that the host firmware is identical on all servers associated with service profiles which use the same policy. Therefore, if you move the service profile from one server to another, the firmware versions are maintained. Also, if you change the firmware version for an endpoint in the firmware package, new versions are applied to all the affected service profiles immediately, which could cause server reboots. You must include this policy in a service profile, and that service profile must be associated with a server for it to take effect. Prerequisites This policy is not dependent upon any other policies. However, you must ensure that the appropriate firmware has been downloaded to the fabric interconnect. If the firmware image is not available when Cisco UCS Manager is associating a server with a service profile, Cisco UCS Manager ignores the firmware upgrade and completes the association. Management Firmware Package This policy enables you to specify a set of firmware versions that make up the management firmware package (also known as a management firmware pack). The management firmware package includes the Cisco Integrated Management Controller (CIMC) on the server. You do not need to use this package if you upgrade the CIMC directly. The firmware package is pushed to all servers associated with service profiles that include this policy. This policy ensures that the CIMC firmware is identical on all servers associated with service profiles which use the same policy. Therefore, if you move the service profile from one server to another, the firmware versions are maintained. You must include this policy in a service profile, and that service profile must be associated with a server for it to take effect. This policy is not dependent upon any other policies. However, you must ensure that the appropriate firmware has been downloaded to the fabric interconnect. Stages of a Firmware Upgrade through Service Profiles You can use the host and management firmware package policies in service profiles to upgrade server and adapter firmware. Caution If you modify a host firmware package by adding an endpoint or changing firmware versions for an existing endpoint, Cisco UCS Manager upgrades the endpoints and reboots all servers associated with that firmware package as soon as the changes are saved, disrupting data traffic to and from the servers. New Service Profile For a new service profile, this upgrade takes place over the following stages: Firmware Package Policy Creation During this stage, you create the host and/or management firmware packages and include them in the appropriate firmware policies. Cisco UCS Manager GUI Configuration Guide, Release 2.0 198 OL-25712-04 Firmware Downgrades Service Profile Association During this stage, you include the firmware packages in a service profile, and then associate the service profile with a server. The system pushes the selected firmware versions to the endpoints. For a host firmware package, the server is rebooted to ensure that the endpoints are running the versions specified in the firmware package. Existing Service Profile If the service profile is already associated with a server, Cisco UCS Manager upgrades the firmware as soon as you save the changes to the host firmware packages. For a host firmware package, Cisco UCS Manager reboots the server as soon as the change is saved. Firmware Downgrades You downgrade firmware in a Cisco UCS domain in the same way that you upgrade firmware. The package or version that you select when you update the firmware determines whether you are performing an upgrade or a downgrade. Note The Cisco UCS Manager GUI does not allow you to choose options that a release does not support. If a Cisco UCS domain includes hardware that is not supported in the release to which you are downgrading, Cisco UCS Manager GUI does not display the firmware as an option for that hardware or allow you to downgrade to it. Completing the Prerequisites for Upgrading the Firmware Prerequisites for Upgrading and Downgrading Firmware All endpoints in a Cisco UCS domain must be fully functional and all processes must be complete before you begin a firmware upgrade or downgrade on those endpoints. You cannot upgrade or downgrade an endpoint that is not in a functional state. For example, the firmware on a server that has not been discovered cannot be upgraded or downgraded. An incomplete process, such as an FSM that has failed after the maximum number of retries, can cause the upgrade or downgrade on an endpoint to fail. If an FSM is in progress, Cisco UCS Manager queues up the update and activation and runs them when the FSM has completed successfully. Colored boxes around components on the Equipment tab may indicate that an endpoint on that component cannot be upgraded or downgraded. Verify the status of that component before you attempt to upgrade the endpoints. Note The Installed Firmware tab in Cisco UCS Manager GUI does not provide sufficient information to complete these prerequisites. Before you upgrade or downgrade firmware in a Cisco UCS domain, complete the following prerequisites: • Review the Release Notes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 199 Completing the Prerequisites for Upgrading the Firmware • Back up the configuration into an All Configuration backup file. • For a cluster configuration, verify that the high availability status of the fabric interconnects shows that both are up and running. • For a standalone configuration, verify that the Overall Status of the fabric interconnect is Operable. • Verify that the data path is up and running. For more information, see Verifying that the Data Path is Ready. • Verify that all servers, I/O modules, and adapters are fully functional. An inoperable server cannot be upgraded. • Verify that the Cisco UCS domain does not include any critical or major faults. If such faults exist, you must resolve them before you upgrade the system. A critical or major fault may cause the upgrade to fail. • Verify that all servers have been discovered. They do not need to be powered on or associated with a service profile. • If you want to integrate a rack-mount server into the Cisco UCS domain, follow the instructions in the appropriate rack-mount server installation guide for installing and integrating a rack-mount server in a system managed by Cisco UCS Manager. Creating an All Configuration Backup File This procedure assumes that you do not have an existing backup operation for an All Configuration backup file. Before You Begin Obtain the backup server IP address and authentication credentials. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Click the All node. In the Work pane, click the General tab. Step 4 Step 5 Step 6 In the Actions area, click Backup. In the Backup Configuration dialog box, click Create Backup Operation. In the Create Backup Operation dialog box, do the following: a) Complete the following fields: • Admin State field—Click the Enabled radio button to run the backup operation as soon as you click OK. • Type field—Click the All Configuration radio button to create an XML backup file that includes all system and logical configuration information. • Preserve Identities check box—If the Cisco UCS domain includes any identities derived from pools that you need to preserve, check this check box. Identities such as MAC addresses, WWNNs, WWPNs, or UUIDS are assigned at runtime. If you do not want these identities to change after you import the backup file, you must check this check box. Cisco UCS Manager GUI Configuration Guide, Release 2.0 200 OL-25712-04 Completing the Prerequisites for Upgrading the Firmware If you do not, these identities may be changed after the import and operations such as a PXE boot or a SAN boot may no longer function. • Protocol field—Click the one of the following radio buttons to indicate the protocol you want to use to transfer the file to the backup server: ◦ FTP ◦ TFTP ◦ SCP ◦ SFTP • Hostname field—Enter the IP address or hostname of the location where the backup file is to be stored. This can be a server, storage array, local drive, or any read/write media that the fabric interconnect can access through the network. If you use a hostname, you must configure Cisco UCS Manager to use a DNS server. • Remote File field—Enter the full path to the backup configuration file. This field can contain the filename as well as the path. If you omit the filename, the backup procedure assigns a name to the file. • User field—Enter the username that Cisco UCS Manager should use to log in to the backup location. You do not need to complete this field if you selected TFTP for the protocol. • Password field—Enter the password associated with the username. You do not need to complete this field if you selected TFTP for the protocol. b) Click OK. Step 7 If Cisco UCS Manager displays a confirmation dialog box, click OK. If you set the Admin State field to enabled, Cisco UCS Manager takes a snapshot of the configuration type that you selected and exports the file to the network location. The backup operation displays in the Backup Operations table in the Backup Configuration dialog box. Step 8 (Optional) To view the progress of the backup operation, do the following: a) If the operation does not display in the Properties area, click the operation in the Backup Operations table. b) In the Properties area, click the down arrows on the FSM Details bar. The FSM Details area expands and displays the operation status. Step 9 Click OK to close the Backup Configuration dialog box. The backup operation continues to run until it is completed. To view the progress, re-open the Backup Configuration dialog box. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 201 Completing the Prerequisites for Upgrading the Firmware Verifying the Overall Status of the Fabric Interconnects Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Fabric Interconnects. Click the node for the fabric interconnect that you want to verify. In the Work pane, click the General tab. Step 5 In the Status area, verify that the Overall Status is operable. If the status is not operable, create and download a Tech Support file, and contact Cisco Technical Support. Do not proceed with the firmware upgrade. For more information about Tech Support files, see the Cisco UCS Manager B-Series Troubleshooting Guide. Verifying the High Availability Status and Roles of a Cluster Configuration The high availability status is the same for both fabric interconnects in a cluster configuration. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Fabric Interconnects. Click the node for one of the fabric interconnects in the cluster. In the Work pane, click the General tab. Step 5 If the fields in the High Availability Details area are not displayed, click the Expand icon to the right of the heading. Verify that the following fields display the following values: Step 6 Field Name Required Value Ready field Yes State field Up If the values are different, create and download a Tech Support file, and contact Cisco Technical Support. Do not proceed with the firmware upgrade. For more information about Tech Support files, see the Cisco UCS Manager B-Series Troubleshooting Guide. Step 7 Note the value in the Leadership field to determine whether the fabric interconnect is the primary or subordinate. You need to know this information to upgrade the firmware on the fabric interconnects. Cisco UCS Manager GUI Configuration Guide, Release 2.0 202 OL-25712-04 Completing the Prerequisites for Upgrading the Firmware Verifying the Status of I/O Modules Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis. Click on the chassis for which you want to verify the status of the I/O modules. In the Work pane, click the IO Modules tab. Step 5 For each I/O module, verify that the following columns display the following values: Field Name Desired Value Overall Status column ok Operability column operable If the values are different, create and download a Tech Support file, and contact Cisco Technical Support. Do not proceed with the firmware upgrade. For more information about Tech Support files, see the Cisco UCS Manager B-Series Troubleshooting Guide. Step 6 Repeat Steps 3 through 5 to verify the status of the I/O modules in each chassis. Verifying the Status of Servers If a server is inoperable, you can proceed with the upgrade for other servers in the Cisco UCS domain. However, you cannot upgrade the inoperable server. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click Equipment. In the Work pane, click the Servers tab to display a list of all servers in all chassis. Step 4 For each server, verify that the following columns display the following values: Field Name Desired Value Overall Status column ok, unassociated, or any value that does not indicate a failure. If the value indicates a failure, such as discovery-failed, the endpoints on that server cannot be upgraded. Operability column operable Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 203 Downloading and Managing Firmware Packages Step 5 If you need to verify that a server has been discovered, do the following: a) Right-click the server for which you want to verify the discovery status and choose Show Navigator. b) In the Status Details area of the General tab, verify that the Discovery State field displays a value of complete. If the fields in the Status Details area are not displayed, click the Expand icon to the right of the heading. Verifying the Status of Adapters on Servers in a Chassis Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Click the server for which you want to verify the status of the adapters. In the Work pane, click the Inventory tab. Step 5 Step 6 In the Inventory tab, click the Adapters subtab. For each adapter, verify that the following columns display the following values: Field Name Desired Value Overall Status column ok Operability column operable If the fields show a different value and the adapter is inoperable, you can proceed with the upgrade for other adapters on the servers in the Cisco UCS domain. However, you cannot upgrade the inoperable adapter. Downloading and Managing Firmware Packages Obtaining Software Bundles from Cisco Before You Begin Determine which of the following software bundles you need to update the Cisco UCS domain: • Cisco UCS Infrastructure Software Bundle—Required for all Cisco UCS domains. • Cisco UCS B-Series Blade Server Software Bundle—Required for all Cisco UCS domains that include blade servers. Cisco UCS Manager GUI Configuration Guide, Release 2.0 204 OL-25712-04 Downloading and Managing Firmware Packages • Cisco UCS C-Series Rack-Mount Server Software Bundle—Only required for Cisco UCS domains that include integrated rack-mount servers. This bundle contains firmware to enable Cisco UCS Manager to manage those servers and is not applicable to standalone C-Series rack-mount servers. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 In a web browser, navigate to Cisco.com. Under Support, click All Downloads. In the center pane, click Unified Computing and Servers. If prompted, enter your Cisco.com username and password to log in. In the right pane, click the link for the software bundles you require, as follows: Bundle Navigation Path Cisco UCS Infrastructure Software Bundle Click Cisco UCS Infrastructure and UCS Manager Software > Unified Computing System (UCS) Infrastructure Software Bundle. Cisco UCS B-Series Blade Server Software Bundle Click Cisco UCS B-Series Blade Server Software > Unified Computing System (UCS) Server Software Bundle. Cisco UCS C-Series Rack-Mount Server Click Cisco UCS C-Series Rack-Mount UCS-Managed Server Software Bundle Software > Unified Computing System (UCS) Server Software Bundle. The Unified Computing System (UCS) Documentation Roadmap Bundle, which is accessible through these paths, is a downloadable ISO image of all Cisco UCS documentation. On the first page from which you download a software bundle, click the Release Notes link to download the latest version of the Release Notes. For each software bundle that you want to download, do the following: a) Click the link for the release you want to downloadthe latest release 2.0 software bundle. The release number is followed by a number and a letter in parentheses. The number identifies the maintenance release level, and the letter differentiates between patches of that maintenance release. For more information about what is in each maintenance release and patch, see the latest version of the Release Notes. Tip Step 6 Step 7 b) Click one of the following buttons and follow the instructions provided: • Download Now—Allows you to download the software bundle immediately. • Add to Cart—Adds the software bundle to your cart to be downloaded at a later time. c) Follow the prompts to complete your download of the software bundle(s). Step 8 Read the Release Notes before upgrading your Cisco UCS domain. What to Do Next Download the software bundles to the fabric interconnect. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 205 Downloading and Managing Firmware Packages Downloading Firmware Images to the Fabric Interconnect from a Remote Location Note In a cluster setup, the image file for the firmware bundle is downloaded to both fabric interconnects, regardless of which fabric interconnect is used to initiate the download. Cisco UCS Manager maintains all firmware packages and images in both fabric interconnects in sync. If one fabric interconnect is down, the download still finishes successfully. The images are synced to the other fabric interconnect when it comes back online. Before You Begin Obtain the required firmware bundles from Cisco. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Firmware Management tab. Step 4 Step 5 Step 6 Click the Installed Firmware tab. Click Download Firmware. In the Download Firmware dialog box, click the Remote File System radio button in the Location of the Image File field. Complete the following fields: Step 7 Name Description Protocol field The protocol to use when communicating with the remote server. This can be one of the following: • FTP • TFTP • SCP • SFTP Note Server field If the file came from a remote server, this is the IP address or hostname of the remote server on which the files resides. If the file came from a local source, this field displays "local". Note Filename field TFTP has a file size limitation of 32 MB. Because firmware bundles can be much larger than that, we recommend that you do not choose TFTP for firmware downloads. If you use a hostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager. The name of the firmware file. Cisco UCS Manager GUI Configuration Guide, Release 2.0 206 OL-25712-04 Downloading and Managing Firmware Packages Name Description Path field The absolute path to the file on the remote server. If you use SCP, the absolute path is always required. If you use any other protocol, you may not need to specify a remote path if the file resides in the default download folder. For details about how your file server is configured, contact your system administrator. Step 8 User field The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP. Password field The password for the remote server username. This field does not apply if the protocol is TFTP. Click OK. Cisco UCS Manager GUI begins downloading the firmware bundle to the fabric interconnect. Step 9 (Optional) Monitor the status of the download on the Download Tasks tab. Note If Cisco UCS Manager reports that the bootflash is out of space, delete obsolete bundles on the Packages tab to free up space. To view the available space in bootflash, navigate to the fabric interconnect on the Equipment tab and expand the Local Storage Information area on the General tab. Step 10 Repeat this task until all the required firmware bundles have been downloaded to the fabric interconnect. What to Do Next After the image file for the firmware bundles have downloaded completely, update the firmware on the endpoints. Downloading Firmware Images to the Fabric Interconnect from the Local File System Note In a cluster setup, the image file for the firmware bundle is downloaded to both fabric interconnects, regardless of which fabric interconnect is used to initiate the download. Cisco UCS Manager maintains all firmware packages and images in both fabric interconnects in sync. If one fabric interconnect is down, the download still finishes successfully. The images are synced to the other fabric interconnect when it comes back online. Before You Begin Obtain the required firmware bundles from Cisco. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 207 Downloading and Managing Firmware Packages Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Firmware Management tab. Step 4 Step 5 Step 6 Click the Installed Firmware tab. Click Download Firmware. In the Download Firmware dialog box, click the Local File System radio button in the Location of the Image File field. In the Filename field, type the full path and and name of the image file. If you do not know the exact path to the folder where the firmware image file is located, click Browse and navigate to the file. Step 7 Step 8 Click OK. Cisco UCS Manager GUI begins downloading the firmware bundle to the fabric interconnect. Step 9 (Optional) Monitor the status of the firmware bundle download on the Download Tasks tab. Note If Cisco UCS Manager reports that the bootflash is out of space, delete obsolete bundles on the Packages tab to free up space. To view the available space in bootflash, navigate to the fabric interconnect on the Equipment tab and expand the Local Storage Information area on the General tab. Step 10 Repeat this task until all the required firmware bundles have been downloaded to the fabric interconnect. What to Do Next After the image file for the firmware bundles have downloaded completely, update the firmware on the endpoints. Canceling an Image Download You can cancel the download task for an image only while it is in progress. After the image has downloaded, deleting the download task does not delete the image that was downloaded. You cannot cancel the FSM related to the image download task. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Expand the Equipment node. In the Work pane, click the Firmware Management tab. Step 4 On the Download Tasks tab, right-click the task you want to cancel and select Delete. Cisco UCS Manager GUI Configuration Guide, Release 2.0 208 OL-25712-04 Downloading and Managing Firmware Packages Determining the Contents of a Firmware Package Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Firmware Management tab. Step 4 Step 5 On the Packages subtab, click the + icon next to a package to view its contents. To take a snapshot of the package contents, do the following: a) Highlight the rows that include the image name and its contents. b) Right-click and choose Copy. c) Paste the contents of your clipboard into a text file or other document. Checking the Available Space on a Fabric Interconnect If an image download fails, check whether the bootflash on the fabric interconnect or fabric interconnects in the Cisco UCS has sufficient available space. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Fabric Interconnects. Click the fabric interconnect on which you want to check the available space. In the Work pane, click the General tab. Step 5 Expand the Local Storage Information area. When you download a firmware image bundle, a fabric interconnect needs at least twice as much available space as the size of the firmware image bundle. If the bootflash does not have sufficient space, delete the obsolete firmware, core files, and other unneeded objects from the fabric interconnect. Deleting Firmware Packages from a Fabric Interconnect Use this procedure if you want to delete an entire firmware package or bundle. If you prefer you can also delete one or more of the individual images in a package. For releases prior to Cisco UCS, Release 1.3(1), you cannot delete firmware packages from the Packages tab. After you delete all images from the package, Cisco UCS Manager removes the packages. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 209 Directly Upgrading Firmware at Endpoints Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Firmware Management tab. Step 4 Step 5 On the Firmware Management tab, click the Packages tab. In the table, click the package that you want to delete. You can use the Shift key or Ctrl key to select multiple entries. Step 6 Step 7 Right-click the highlighted package or packages and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager deletes the selected package or packages and all images contained within each package. Deleting Firmware Images from a Fabric Interconnect Use this procedure if you want to delete only a single image from a package. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Firmware Management tab. Step 4 Step 5 On the Firmware Management tab, click the Images tab. In the table, click the image that you want to delete. You can use the Shift key or Ctrl key to select multiple entries. Step 6 Step 7 Right-click the highlighted image or images and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Directly Upgrading Firmware at Endpoints Updating the Firmware on Multiple Endpoints You can use this procedure to update the firmware on the following endpoints: • Adapters • CIMCs • I/O modules Cisco UCS Manager GUI Configuration Guide, Release 2.0 210 OL-25712-04 Directly Upgrading Firmware at Endpoints Caution Do not remove the hardware that contains the endpoint or perform any maintenance on it until the update process has completed. If the hardware is removed or otherwise unavailable due to maintenance, the firmware update fails. This failure may corrupt the backup partition. You cannot update the firmware on an endpoint with a corrupted backup partition. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Firmware Management tab. Step 4 On the Installed Firmware tab, click Update Firmware. Cisco UCS Manager GUI opens the Update Firmware dialog box and verifies the firmware versions for all endpoints in the Cisco UCS domain. This step may take a few minutes, depending upon the number of chassis and servers. Step 5 In the Update Firmware dialog box, do the following: a) From the Filter drop-down list on the menu bar, select ALL. If you want to update all endpoint firmware of a specific type, such as all adapters or server BIOS, select that type from the drop-down list. b) In the Select field, do one of the following: • To activate all endpoints to the same version, click the Version radio button and select the appropriate version from the Set Version drop-down list. • To activate all endpoints to the firmware version included in a specific bundle, click the Bundle radio button and select the appropriate bundle from the Set Bundle drop-down list . c) Click OK. If one or more endpoints cannot be directly updated, Cisco UCS Manager displays a notification message. After you acknowledge the notification message, Cisco UCS Manager updates the firmware for all other endpoints on servers that can be directly updated. Cisco UCS Manager copies the selected firmware image to the backup memory partition and verifies that the image is not corrupt. The image remains as the backup version until you explicitly activate it. Cisco UCS Manager begins all updates at the same time. However, some updates may complete at different times. The update is complete when the Update Firmware dialog box displays ready in the Update Status column for all updated endpoints. Step 6 (Optional) To monitor the progress of the update to a specific endpoint, right-click the endpoint and choose Show Navigator. Cisco UCS Manager displays the progress in the Update Status area on the General tab. If the navigator has an FSM tab, you can also monitor the progress there. An entry in the Retry # field may not indicate that the update has failed. The retry count also includes retries that occur when Cisco UCS Manager retrieves the update status. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 211 Directly Upgrading Firmware at Endpoints What to Do Next Activate the firmware. Updating the Firmware on an Adapter Caution Do not remove the hardware that contains the endpoint or perform any maintenance on it until the update process has completed. If the hardware is removed or otherwise unavailable due to maintenance, the firmware update fails. This failure may corrupt the backup partition. You cannot update the firmware on an endpoint with a corrupted backup partition. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 Step 5 Step 6 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Expand the node for the server which includes the adapter you want to update. Expand Adapters and select the adapter you want to upgrade. In the General tab, click Update Firmware. In the Update Firmware dialog box, do the following: a) From the Version drop-down list, select the firmware version to which you want to update the endpoint. b) (Optional) If you want to update the firmware regardless of any possible incompatibilities or currently executing tasks, check the Ignore Compatibility Check check box. c) Click OK. If one or more endpoints cannot be directly updated, Cisco UCS Manager displays a notification message. After you acknowledge the notification message, Cisco UCS Manager updates the firmware for all other endpoints on servers that can be directly updated. Cisco UCS Manager copies the selected firmware package to the backup memory slot, where it remains until you explicitly activate it. Step 7 (Optional) Monitor the status of the update in the Update Status area. The update process can take several minutes. Do not activate the firmware until the selected firmware package displays in the Backup Version field in the Firmware area of the General tab. What to Do Next Activate the firmware. Cisco UCS Manager GUI Configuration Guide, Release 2.0 212 OL-25712-04 Directly Upgrading Firmware at Endpoints Activating the Firmware on an Adapter Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 Step 5 Step 6 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Expand the node for the server that includes the adapter for which you want to activate the updated firmware. Expand Adapters and select the adapter for which you want to activate the firmware. In the General tab, click Activate Firmware. In the Activate Firmware dialog box, do the following: a) Select the appropriate version from the Version To Be Activated drop-down list. If one or more of the selected endpoints are not configured with the desired version as the backup version, Cisco UCS Manager GUI does not display that version in the Set Version drop-down list. You must select the version from the Startup Version column for each individual endpoint. b) (Optional) If you want to activate the firmware regardless of any possible incompatibilities or currently executing tasks, check the Ignore Compatibility Check check box. c) If you want to set the start up version and not change the version running on the endpoint, check the Set Startup Version Only check box. During a direct upgrade, you should configure Set Startup Version Only for an adapter. With this setting, the activated firmware moves into the pending-next-boot state, and the server is not immediately rebooted. The activated firmware does not become the running version of firmware on the adapter until the server is rebooted. You cannot configure Set Startup Version Only for an adapter in the host firmware package. If a server is not associated with a service profile, the activated firmware remains in the pending-next-boot state. Cisco UCS Manager does not reboot the endpoints or activate the firmware until the server is associated with a service profile. If necessary, you can manually reboot or reset an unassociated server to activate the firmware. d) Click OK. Updating the BIOS Firmware on a Server Caution Do not remove the hardware that contains the endpoint or perform any maintenance on it until the update process has completed. If the hardware is removed or otherwise unavailable due to maintenance, the firmware update fails. This failure may corrupt the backup partition. You cannot update the firmware on an endpoint with a corrupted backup partition. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 213 Directly Upgrading Firmware at Endpoints Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Expand the node for the server for which you want to update the BIOS firmware. On the General tab, click the Inventory tab. Click the Motherboard tab. In the Actions area, click Update Bios Firmware. In the Update Firmware dialog box, do the following: a) From the Version drop-down list, select the firmware version to which you want to update the server BIOS. b) (Optional) If you want to update the firmware regardless of any possible incompatibilities or currently executing tasks, check the Force check box. c) Click OK. Cisco UCS Manager copies the selected server BIOS firmware package to the backup memory slot, where it remains until you explicitly activate it. The update is complete when the BIOS area of the Motherboard tab displays Ready in the Update Status column for the Backup Version. What to Do Next Activate the firmware. Activating the BIOS Firmware on a Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Expand the node for the server for which you want to activate the updated BIOS firmware. On the General tab, click the Inventory tab. Click the Motherboard tab. In the Actions area, click Activate Bios Firmware. In the Activate Firmware dialog box, do the following: a) Select the appropriate server BIOS version from the Version To Be Activated drop-down list. b) (Optional) If you want to activate the firmware regardless of any possible incompatibilities or currently executing tasks, check the Ignore Compatibility Check check box. c) If you want to set the start up version and not change the version running on the server, check the Set Startup Version Only check box. If you configure Set Startup Version Only, the activated firmware moves into the pending-next-reboot state and the server is not immediately rebooted. The activated firmware does not become the running version of firmware until the server is rebooted. Cisco UCS Manager GUI Configuration Guide, Release 2.0 214 OL-25712-04 Directly Upgrading Firmware at Endpoints d) Click OK. Updating the CIMC Firmware on a Server Caution Do not remove the hardware that contains the endpoint or perform any maintenance on it until the update process has completed. If the hardware is removed or otherwise unavailable due to maintenance, the firmware update fails. This failure may corrupt the backup partition. You cannot update the firmware on an endpoint with a corrupted backup partition. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Expand the node for the server for which you want to update the CIMC. In the General tab, click the Inventory tab. Click the CIMC tab. In the Actions area, click Update Firmware. In the Update Firmware dialog box, do the following: a) From the Version drop-down list, select the firmware version to which you want to update the endpoint. b) (Optional) If you want to update the firmware regardless of any possible incompatibilities or currently executing tasks, check the Ignore Compatibility Check check box. c) Click OK. Cisco UCS Manager copies the selected firmware package to the backup memory slot, where it remains until you explicitly activate it. Step 8 (Optional) Monitor the status of the update in the Update Status area. The update process can take several minutes. Do not activate the firmware until the selected firmware package displays in the Backup Version field in the Firmware area of the General tab. What to Do Next Activate the firmware. Activating the CIMC Firmware on a Server The activation of firmware for a CIMC does not disrupt data traffic. However, it will interrupt all KVM sessions and disconnect any vMedia attached to the server. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 215 Directly Upgrading Firmware at Endpoints Caution Do not remove the hardware that contains the endpoint or perform any maintenance on it until the update process has completed. If the hardware is removed or otherwise unavailable due to maintenance, the firmware update fails. This failure may corrupt the backup partition. You cannot update the firmware on an endpoint with a corrupted backup partition. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 Step 5 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Expand the node for the server that includes the CIMC for which you want to activate the updated firmware. On the General tab, click the Inventory tab. Click the CIMC tab. In the Actions area, click Activate Firmware. In the Activate Firmware dialog box, do the following: Step 6 Step 7 a) Select the appropriate version from the Version To Be Activated drop-down list. If one or more of the selected endpoints are not configured with the desired version as the backup version, Cisco UCS Manager GUI does not display that version in the Set Version drop-down list. You must select the version from the Startup Version column for each individual endpoint. b) (Optional) If you want to activate the firmware regardless of any possible incompatibilities or currently executing tasks, check the Ignore Compatibility Check check box. c) If you want to set the start up version and not change the version running on the endpoint, check the Set Startup Version Only check box. If you configure Set Startup Version Only, the activated firmware moves into the pending-next-reboot state and the endpoint is not immediately rebooted. The activated firmware does not become the running version of firmware until the endpoint is rebooted. d) Click OK. Updating the Firmware on an IOM Caution Do not remove the hardware that contains the endpoint or perform any maintenance on it until the update process has completed. If the hardware is removed or otherwise unavailable due to maintenance, the firmware update fails. This failure may corrupt the backup partition. You cannot update the firmware on an endpoint with a corrupted backup partition. Cisco UCS Manager GUI Configuration Guide, Release 2.0 216 OL-25712-04 Directly Upgrading Firmware at Endpoints Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 Step 5 On the Equipment tab, expand Equipment > Chassis > Chassis Number > IO Modules. Click the I/O module that you want to update. In the General tab, click Update Firmware. In the Update Firmware dialog box, do the following: a) From the Version drop-down list, select the firmware version to which you want to update the endpoint. b) (Optional) If you want to update the firmware regardless of any possible incompatibilities or currently executing tasks, check the Ignore Compatibility Check check box. c) Click OK. Cisco UCS Manager copies the selected firmware package to the backup memory slot, where it remains until you explicitly activate it. Step 6 (Optional) Monitor the status of the update in the Update Status area. The update process can take several minutes. Do not activate the firmware until the selected firmware package displays in the Backup Version field in the Firmware area of the General tab. What to Do Next Activate the firmware. Activating the Firmware on an IOM Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 Step 5 On the Equipment tab, expand Equipment > Chassis > Chassis Number > IO Modules. Select the IO Module node that includes the I/O module for which you want to activate the updated firmware. In the General tab, click Activate Firmware. In the Activate Firmware dialog box, do the following: a) Select the appropriate version from the Version To Be Activated drop-down list. If one or more of the selected endpoints are not configured with the desired version as the backup version, Cisco UCS Manager GUI does not display that version in the Set Version drop-down list. You must select the version from the Startup Version column for each individual endpoint. b) (Optional) If you want to activate the firmware regardless of any possible incompatibilities or currently executing tasks, check the Ignore Compatibility Check check box. c) If you want to set the start up version and not change the version running on the endpoint, check the Set Startup Version Only check box. If you configure Set Startup Version Only, the activated firmware moves into the pending-next-reboot state and the endpoint is not immediately rebooted. The activated firmware does not become the running version of firmware until the endpoint is rebooted. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 217 Directly Upgrading Firmware at Endpoints d) Click OK. Activating the Board Controller Firmware on a Server Only certain servers, such as the Cisco UCS B440 High Performance blade server and the Cisco UCS B230 blade server, have board controller firmware. The board controller firmware controls many of the server functions, including eUSBs, LEDs, and I/O connectors. Note This activation procedure causes the server to reboot. Depending upon whether or not the service profile associated with the server includes a maintenance policy, the reboot can occur immediately. To reduce the number of times a server needs to be rebooted during the upgrade process, we recommend that you upgrade the board controller firmware through the host firmware package in the service profile as the last step of upgrading a Cisco UCS domain, along with the server BIOS. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Firmware Management tab. Step 4 On the Installed Firmware tab, click Activate Firmware. Cisco UCS Manager GUI opens the Activate Firmware dialog box and verifies the firmware versions for all endpoints in the Cisco UCS domain. This step may take a few minutes, depending upon the number of chassis and servers. Step 5 From the Filter drop-down list on the menu bar of the Activate Firmware dialog box, select Board Controller. Cisco UCS Manager GUI displays all servers that have board controllers in the Activate Firmware dialog box. Step 6 In the Select field, do one of the following: • To activate the board controller firmware on all servers to the same version, click the Version radio button and select the appropriate version from the Set Version drop-down list. • To activate the board controller firmware on all servers to the firmware version included in a specific bundle, click the Bundle radio button and select the appropriate bundle from the Set Bundle drop-down list . Step 7 Step 8 If you want to activate the firmware regardless of any possible incompatibilities or currently executing tasks, check the Ignore Compatibility Check check box. Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 218 OL-25712-04 Directly Upgrading Firmware at Endpoints Activating the Cisco UCS Manager Software Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Firmware Management tab. Step 4 On the Installed Firmware tab, click Activate Firmware. Cisco UCS Manager GUI opens the Activate Firmware dialog box and verifies the firmware versions for all endpoints in the Cisco UCS domain. This step may take a few minutes, depending upon the number of chassis and servers. Step 5 On the UCS Manager row of the Activate Firmware dialog box, do the following: a) From the drop-down list in the Startup Version column, select the version to which you want to update the software. b) (Optional) If you want to activate the firmware regardless of any possible incompatibilities or currently executing tasks, check the Ignore Compatibility Check check box. c) Click OK. Cisco UCS Manager disconnects all active sessions, logs out all users, and activates the software. When the upgrade is complete, you are prompted to log back in. If you are prompted to re-login immediately after being disconnected, the login will fail. You must wait until the activation of Cisco UCS Manager is completed, which takes a few minutes. Cisco UCS Manager makes the selected version the startup version and schedules the activation to occur when the fabric interconnects are upgraded. Activating the Firmware on a Subordinate Fabric Interconnect Before You Begin Determine which fabric interconnect in the cluster is the subordinate fabric interconnect. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Firmware Management tab. Step 4 On the Installed Firmware tab, click Activate Firmware. Cisco UCS Manager GUI opens the Activate Firmware dialog box and verifies the firmware versions for all endpoints in the Cisco UCS domain. This step may take a few minutes, depending upon the number of chassis and servers. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 219 Directly Upgrading Firmware at Endpoints Step 5 Step 6 Step 7 From the Filter drop-down list on the menu bar, choose Fabric Interconnects. On the menu bar, check the Ignore Compatibility Check check box. On the row of the Activate Firmware dialog box for the subordinate fabric interconnect, do the following: a) In the Kernel row, choose the firmware version to which you want to upgrade from the drop-down list in the Startup Version column. b) In the System row, choose the firmware version to which you want to upgrade from the drop-down list in the Startup Version column. Step 8 Click Apply. Cisco UCS Manager updates and activates the firmware and reboots the fabric interconnect and any I/O module in the data path to that fabric interconnect, disrupting data traffic to and from that fabric interconnect. However, assuming the Cisco UCS domain is configured to permit traffic and port failover, data traffic fails over to the primary fabric interconnect and is not disrupted. Step 9 Verify the high availability status of the subordinate fabric interconnect. If the High Availability Details area for the fabric interconnect does not show the following values, contact Cisco Technical Support immediately. Do not continue to update the primary fabric interconnect. Field Name Required Value Ready field Yes State field Up What to Do Next If the high availability status of the subordinate fabric interconnect contains the required values, update and activate the primary fabric interconnect. Activating the Firmware on a Primary Fabric Interconnect This procedure continues directly from Activating the Firmware on a Subordinate Fabric Interconnect, on page 219 and assumes you are on the Firmware Management tab. Before You Begin Activate the subordinate fabric interconnect. Procedure Step 1 On the Installed Firmware tab, click Activate Firmware. Cisco UCS Manager GUI opens the Activate Firmware dialog box and verifies the firmware versions for all endpoints in the Cisco UCS domain. This step may take a few minutes, depending upon the number of chassis and servers. Cisco UCS Manager GUI Configuration Guide, Release 2.0 220 OL-25712-04 Directly Upgrading Firmware at Endpoints Step 2 Step 3 Step 4 From the Filter drop-down list on the menu bar, choose Fabric Interconnects. On the menu bar, check the Ignore Compatibility Check check box. On the row of the Activate Firmware dialog box for the subordinate fabric interconnect, do the following: a) In the Kernel row, choose the firmware version to which you want to upgrade from the drop-down list in the Startup Version column. b) In the System row, choose the firmware version to which you want to upgrade from the drop-down list in the Startup Version column. Step 5 Click Apply. Cisco UCS Manager updates and activates the firmware and reboots the fabric interconnect and any I/O module in the data path to that fabric interconnect, disrupting data traffic to and from that fabric interconnect. However, assuming the Cisco UCS domain is configured to permit traffic and port failover, data traffic fails over to the other fabric interconnect, which becomes the primary. When it comes back up, this fabric interconnect is the subordinate fabric interconnect. Step 6 Verify the high availability status of the fabric interconnect. If the High Availability Details area for the fabric interconnect does not show the following values, contact Cisco Technical Support immediately. Field Name Required Value Ready field Yes State field Up Activating the Firmware on a Standalone Fabric Interconnect For a standalone configuration with a single fabric interconnect, you can minimize the disruption to data traffic when you perform a direct firmware upgrade of the endpoints. However, you must reboot the fabric interconnect to complete the upgrade and, therefore, cannot avoid disrupting traffic. Tip If you ever need to recover the password to the admin account that was created when you configured the fabric interconnects for the Cisco UCS domain, you must know the running kernel version and the running system version. If you do not plan to create additional accounts, we recommend that you save the path to these firmware versions in a text file so that you can access them if required. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 Step 5 On the Equipment tab, click the Equipment node. Expand the Fabric Interconnects node and click the standalone fabric interconnect. On the General tab, click Activate Firmware. In the Activate Firmware dialog box, complete the following fields: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 221 Upgrading Firmware through Service Profiles Name Description Kernel Version drop-down list Choose the version that you want to use for the kernel. Ignore Compatibility Check check box By default, Cisco UCS makes sure that the firmware version is compatible with everything running on the server before it activates that version. Check this check box if you want Cisco UCS to activate the firmware without making sure that it is compatible first. Note We recommend that you use this option only when explicitly directed to do so by a technical support representative. Force check box If checked, the system performs the activation regardless of any possible incompatibilities or currently-executing tasks. System Version drop-down list Choose the version you want to use for the system. Ignore Compatibility Check check box By default, Cisco UCS makes sure that the firmware version is compatible with everything running on the server before it activates that version. Check this check box if you want Cisco UCS to activate the firmware without making sure that it is compatible first. Note Force check box Step 6 We recommend that you use this option only when explicitly directed to do so by a technical support representative. If checked, the system performs the activation regardless of any possible incompatibilities or currently-executing tasks. Click OK. Cisco UCS Manager activates the firmware and reboots the fabric interconnect and any I/O module in the data path to that fabric interconnect. For a standalone fabric interconnect, this disrupts all data traffic in the Cisco UCS domain. Upgrading Firmware through Service Profiles Host Firmware Package This policy enables you to specify a set of firmware versions that make up the host firmware package (also known as the host firmware pack). The host firmware includes the following firmware for server and adapter endpoints: • Adapter • BIOS • Board Controller Cisco UCS Manager GUI Configuration Guide, Release 2.0 222 OL-25712-04 Upgrading Firmware through Service Profiles • FC Adapters • HBA Option ROM • Storage Controller Tip You can include more than one type of firmware in the same host firmware package. For example, a host firmware package can include both BIOS firmware and storage controller firmware or adapter firmware for two different models of adapters. However, you can only have one firmware version with the same type, vendor, and model number. The system recognizes which firmware version is required for an endpoint and ignores all other firmware versions. The firmware package is pushed to all servers associated with service profiles that include this policy. This policy ensures that the host firmware is identical on all servers associated with service profiles which use the same policy. Therefore, if you move the service profile from one server to another, the firmware versions are maintained. Also, if you change the firmware version for an endpoint in the firmware package, new versions are applied to all the affected service profiles immediately, which could cause server reboots. You must include this policy in a service profile, and that service profile must be associated with a server for it to take effect. Prerequisites This policy is not dependent upon any other policies. However, you must ensure that the appropriate firmware has been downloaded to the fabric interconnect. If the firmware image is not available when Cisco UCS Manager is associating a server with a service profile, Cisco UCS Manager ignores the firmware upgrade and completes the association. Management Firmware Package This policy enables you to specify a set of firmware versions that make up the management firmware package (also known as a management firmware pack). The management firmware package includes the Cisco Integrated Management Controller (CIMC) on the server. You do not need to use this package if you upgrade the CIMC directly. The firmware package is pushed to all servers associated with service profiles that include this policy. This policy ensures that the CIMC firmware is identical on all servers associated with service profiles which use the same policy. Therefore, if you move the service profile from one server to another, the firmware versions are maintained. You must include this policy in a service profile, and that service profile must be associated with a server for it to take effect. This policy is not dependent upon any other policies. However, you must ensure that the appropriate firmware has been downloaded to the fabric interconnect. Effect of Updates to Host Firmware Packages and Management Firmware Packages To update firmware through a host firmware package or a management firmware package, you need to update the firmware in the package. What happens after you save the changes to a host or management firmware package depends upon how the Cisco UCS domain is configured. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 223 Upgrading Firmware through Service Profiles The following table describes the most common options for upgrading servers with a host or management firmware package. Service Profile Maintenance Policy Host or management firmware No maintenance package is not included in a policy service profile or an updating service profile template. OR You want to upgrade the firmware without making any changes to the existing service profile or updating service profile template. Upgrade Actions After you update the firmware package, do one of the following: • To reboot and upgrade some or all servers simultaneously, follow the procedure in the Cisco UCS Manager configuration guides for the appropriate release to add the firmware package to one or more service profiles that are associated with servers or to an updating service profile template. • To reboot and upgrade one server at a time, do the following for each server: 1 Create a new service profile and include the firmware package in that service profile. 2 Dissociate the server from its service profile. 3 Associate the server with the new service profile. 4 After the server has been rebooted and the firmware upgraded, disassociate the server from the new service profile and associate it with its original service profile. Caution If the original service profile includes a scrub policy, this procedure may result in data loss when the disk or the BIOS is scrubbed upon association with the new service profile. Cisco UCS Manager GUI Configuration Guide, Release 2.0 224 OL-25712-04 Upgrading Firmware through Service Profiles Service Profile Maintenance Policy Upgrade Actions Host or management firmware package is included in one or more service profiles, and the service profiles are associated with one or more servers. No maintenance policy The following occurs when you update the firmware package: OR Host or management firmware package is included in an updating service profile template, and the service profiles created from that template are associated with one or more servers. OR 1 The changes to the firmware package take effect as soon as you save them. A maintenance policy configured for 2 Cisco UCS Manager verifies the model numbers immediate updates. and vendor against all servers associated with service profiles that include this policy. If the model numbers and vendor match a firmware version in the policy, Cisco UCS Manager reboots the servers and updates the firmware. All servers associated with service profiles that include the firmware package are rebooted at the same time. Host or management firmware Configured for user package is included in one or acknowledgment more service profiles, and the service profiles are associated with one or more servers. OR Host or management firmware package is included in an updating service profile template, and the service profiles created from that template are associated with one or more servers. The following occurs when you update the firmware package: 1 Cisco UCS Manager asks you to confirm your change and advises that a user-acknowledged reboot of the servers is required. 2 Click the flashing Pending Activities button to select the servers you want to reboot and apply the new firmware. 3 Cisco UCS Manager verifies the model numbers and vendor against all servers associated with service profiles that include this policy. If the model numbers and vendor match a firmware version in the policy, Cisco UCS Manager reboots the server and updates the firmware. A manual reboot of the servers does not cause Cisco UCS Manager to apply the firmware package, nor does it cancel the pending activities. You must acknowledge or cancel the pending activity through the Pending Activities button. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 225 Upgrading Firmware through Service Profiles Service Profile Maintenance Policy Host or management firmware package is included in one or more service profiles, and the service profiles are associated with one or more servers. Configured for The following occurs when you update the changes to take effect firmware package: during a specific 1 Cisco UCS Manager asks you to confirm your maintenance window. change and advises that a user-acknowledged reboot of the servers is required. OR Host or management firmware package is included in an updating service profile template, and the service profiles created from that template are associated with one or more servers. Upgrade Actions 2 Click the flashing Pending Activities button to select the servers you want to reboot and apply the new firmware. 3 Cisco UCS Manager verifies the model numbers and vendor against all servers associated with service profiles that include this policy. If the model numbers and vendor match a firmware version in the policy, Cisco UCS Manager reboots the server and updates the firmware. A manual reboot of the servers does not cause Cisco UCS Manager to apply the firmware package, nor does it cancel the scheduled maintenance activities. Creating a Host Firmware Package Tip You can include more than one type of firmware in the same host firmware package. For example, a host firmware package can include both BIOS firmware and storage controller firmware or adapter firmware for two different models of adapters. However, you can only have one firmware version with the same type, vendor, and model number. The system recognizes which firmware version is required for an endpoint and ignores all other firmware versions. Before You Begin Ensure that the appropriate firmware has been downloaded to the fabric interconnect. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click Host Firmware Packages and choose Create Package. In the Create Host Firmware Package dialog box, enter a unique name and description for the package. Cisco UCS Manager GUI Configuration Guide, Release 2.0 226 OL-25712-04 Upgrading Firmware through Service Profiles This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Step 6 On each sub-tab, do the following for each type of firmware you want to include in the package: a) In the Select column, ensure that the check box for the appropriate lines are checked. b) In the Vendor, Model, and PID columns, verify that the information matches the servers you want to update with this package. The model and model number (PID) must match the servers that are associated with this firmware package. If you select the wrong model or model number, Cisco UCS Manager cannot install the firmware update. c) In the Version column, choose the firmware version to which you want to update the firmware. Step 7 When you have added all the desired firmware to the package, click OK. What to Do Next Include the policy in a service profile and/or template. Updating a Host Firmware Package If the policy is included in one or more service profiles associated with a server and those service profiles do not include maintenance policies, Cisco UCS Manager updates and activates the firmware in the server and adapter with the new versions and reboots the server as soon as you save the host firmware package policy. Before You Begin Ensure that the appropriate firmware has been downloaded to the fabric interconnect. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization that includes the policy you want to update. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Expand Host Firmware Packages and choose the policy you want to update. In the Work pane, click the General tab. Step 6 On each sub-tab, do the following for each type of firmware you want to include in the package: a) In the Select column, ensure that the check box for the appropriate lines are checked. b) In the Vendor, Model, and PID columns, verify that the information matches the servers you want to update with this package. The model and model number (PID) must match the servers that are associated with this firmware package. If you select the wrong model or model number, Cisco UCS Manager cannot install the firmware update. c) In the Version column, choose the firmware version to which you want to update the firmware. Step 7 Click Save Changes. Cisco UCS Manager verifies the model numbers and vendor against all servers associated with service profiles that include this policy. If the model numbers and vendor match a firmware version in the policy, Cisco UCS Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 227 Upgrading Firmware through Service Profiles Manager updates the firmware according to the settings in the maintenance policies included in the service profiles. Creating a Management Firmware Package Before You Begin Ensure that the appropriate firmware has been downloaded to the fabric interconnect. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click Management Firmware Packages and select Create Package. In the Create Management Firmware Package dialog box, enter a unique name and description for the package. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Step 6 In the firmware table, do the following: a) In the Select column, ensure that the check box for the appropriate lines are checked. b) In the Vendor, Model, and PID columns, verify that the information matches the servers you want to update with this package. The model and model number (PID) must match the servers that are associated with this firmware package. If you select the wrong model or model number, Cisco UCS Manager cannot install the firmware update. c) In the Version column, choose the firmware version to which you want to update the firmware. Step 7 When you have added the desired firmware to the package, click OK. What to Do Next Include the policy in a service profile and/or template. Updating a Management Firmware Package If the policy is included in one or more service profiles associated with a server and those service profiles do not include maintenance policies, Cisco UCS Manager updates and activates the management firmware in the server with the new versions and reboots the server as soon as you save the management firmware package policy Cisco UCS Manager GUI Configuration Guide, Release 2.0 228 OL-25712-04 Upgrading Firmware through Service Profiles Before You Begin Ensure that the appropriate firmware has been downloaded to the fabric interconnect. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization that includes the policy you want to update. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Expand Management Firmware Packages and choose the policy you want to update. In the Work pane, click the General tab. Step 6 In the firmware table, do the following: a) In the Select column, ensure that the check box for the appropriate lines are checked. b) In the Vendor, Model, and PID columns, verify that the information matches the servers you want to update with this package. The model and model number (PID) must match the servers that are associated with this firmware package. If you select the wrong model or model number, Cisco UCS Manager cannot install the firmware update. c) In the Version column, choose the firmware version to which you want to update the firmware. Step 7 Click Save Changes. Cisco UCS Manager verifies the model numbers and vendor against all servers associated with service profiles that include this policy. If the model numbers and vendor match a firmware version in the policy, Cisco UCS Manager updates the firmware according to the settings in the maintenance policies included in the service profiles. Adding Firmware Packages to an Existing Service Profile If the service profile does not include a maintenance policy and is associated with a server, Cisco UCS Manager updates and activates the firmware in the server with the new versions and reboots the server as soon as you save the changes to the service profile. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that includes the service profile that you want to update. If the system does not include multitenancy, expand the root node. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 229 Verifying Firmware Versions on Components Step 4 Step 5 Click the service profile to which you want to add the firmware packages. In the Work pane, click the Policies tab. Step 6 Step 7 Step 8 Click the down arrows to expand the Firmware Policies section. To add a host firmware package, select the desired policy from the Host Firmware drop-down list. To add a management firmware package, select the desired policy from the Management Firmware drop-down list. Click Save Changes. Step 9 Verifying Firmware Versions on Components Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Firmware Management tab. Step 4 On the Installed Firmware tab, review the firmware versions listed for each component. Managing the Capability Catalog Capability Catalog The Capability Catalog is a set of tunable parameters, strings, and rules. Cisco UCS Manager uses the catalog to update the display and configurability of components such as newly qualified DIMMs and disk drives for servers. The catalog is divided by hardware components, such as the chassis, CPU, local disk, and I/O module. You can use the catalog to view the list of providers available for that component. There is one provider per hardware component. Each provider is identified by the vendor, model (PID), and revision. For each provider, you can also view details of the equipment manufacturer and the form factor. For information about which hardware components are dependent upon a particular catalog release, see the component support tables in the Service Notes for the B- Series servers. For information about which components are introduced in a specific release, see the Cisco UCS Release Notes. Contents of the Capability Catalog The contents of the Capability Catalog include the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 230 OL-25712-04 Managing the Capability Catalog Implementation-Specific Tunable Parameters • Power and thermal constraints • Slot ranges and numbering • Adapter capacities Hardware-Specific Rules • Firmware compatibility for components such as the BIOS, CIMC, RAID controller, and adapters • Diagnostics • Hardware-specific reboot User Display Strings • Part numbers, such as the CPN, PID/VID • Component descriptions • Physical layout/dimensions • OEM information Updates to the Capability Catalog Capability Catalog updates are included in each Cisco UCS Manager update. Unless otherwise instructed by Cisco Technical Support, you only need to activate the Capability Catalog update after you've downloaded, updated, and activated an Cisco UCS Infrastructure Software Bundle. As soon as you activate a Capability Catalog update, Cisco UCS Manager immediately updates to the new baseline catalog. You do not have to perform any further tasks. Updates to the Capability Catalog do not require you to reboot any component in the Cisco UCS domain or to reinstall Cisco UCS Manager. Each Cisco UCS Manager release contains a baseline catalog. In rare circumstances, Cisco releases an update to the Capability Catalog and makes it available on the same site where you download firmware images. The catalog update is compatible with Cisco UCS, Release 1.3(1) and later. Note The Capability Catalog version is determined by the version of Cisco UCS Manager that you are using. Cisco UCS Manager 2.0 releases work with any 2.0 release of the Capability Catalog, but not with any 1.0 releases of the Capability Catalog. For information about Capability Catalog releases supported by specific Cisco UCS Manager releases, see the Release Notes for Cisco UCS Manager accessible through the Cisco UCS B-Series Servers Documentation Roadmap available at the following URL: http:// www.cisco.com/go/unifiedcomputing/b-series-doc. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 231 Managing the Capability Catalog Activating a Capability Catalog Update Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All. Click the Capability Catalog node. In the Work pane, click the Catalog Update Tasks tab. Step 5 Step 6 Click Activate Catalog. In the Activate Catalog dialog box, choose the capability catalog update that you want to activate from the Version to be Activated drop-down list. Click OK. Step 7 Verifying that the Capability Catalog Is Current Before You Begin Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All. Click the Capability Catalog node. In the Work pane, click the Catalog Update Tasks tab. The current version of the capability catalog is located on the upper right of that tab. Step 5 On Cisco.com, determine the most recent release of the capability catalog available. For more information about the location of capability catalog updates, see Obtaining Capability Catalog Updates from Cisco, on page 233. Step 6 If a more recent version of the capability catalog is available on Cisco.com, update the capability catalog with that version. Cisco UCS Manager GUI Configuration Guide, Release 2.0 232 OL-25712-04 Managing the Capability Catalog Viewing a Capability Catalog Provider Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Capability Catalog. In the Work pane, click the tab for the provider you want to view. Step 4 To view the details of a provider, do the following: a) In the table, click the row with the vendor, model, and revision of the provider you want to view. b) Click the Expand icon to the right of the heading to display the properties for the following areas: • Equipment Manufacturing area • Form Factor area Downloading Individual Capability Catalog Updates Obtaining Capability Catalog Updates from Cisco Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 In a web browser, navigate to Cisco.com. Under Support, click All Downloads. In the center pane, click Unified Computing and Servers. If prompted, enter your Cisco.com username and password to log in. In the right pane, click Cisco UCS Infrastructure and UCS Manager Software > Unified Computing System (UCS) Manager Capability Catalog. Click the link for the latest release of the Capability Catalog. Click one of the following buttons and follow the instructions provided: • Download Now—Allows you to download the catalog update immediately • Add to Cart—Adds the catalog update to your cart to be downloaded at a later time Step 8 Follow the prompts to complete your download of the catalog update. What to Do Next Update the Capability Catalog. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 233 Managing the Capability Catalog Updating the Capability Catalog from a Remote Location You cannot perform a partial update to the Capability Catalog. When you update the Capability Catalog, all components included in the catalog image are updated. A B-series server bundle includes the Capability Catalog update for that server. You do not need to download a separate Capability Catalog update. You only need to activate the Capability Catalog update. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All. Click the Capability Catalog node. In the Work pane, click the Catalog Update Tasks tab. Step 5 Step 6 Click Update Catalog. In the Update Catalog dialog box, click the Remote File System radio button in the Location of the Image File field. Complete the following fields: Step 7 Name Description Protocol field The protocol to use when communicating with the remote server. This can be one of the following: • FTP • TFTP • SCP • SFTP Server field The IP address or hostname of the remote server on which the catalog image resides. Filename field The name of the catalog executable you want to download. Path field The absolute path to the catalog image file on the remote server, if required. If you use SCP, the absolute path is always required. If you use any other protocol, you may not need to specify a remote path if the file resides in the default download folder. For details about how your file server is configured, contact your system administrator. User field The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP. Password field The password for the remote server username. This field does not apply if the protocol is TFTP. Cisco UCS Manager GUI Configuration Guide, Release 2.0 234 OL-25712-04 Updating Management Extensions Step 8 Click OK. Cisco UCS Manager downloads the image and updates the Capability Catalog. You do not need to reboot any hardware components. What to Do Next Activate the Capability Catalog update. Updating the Capability Catalog from the Local File System You cannot perform a partial update to the Capability Catalog. When you update the Capability Catalog, all components included in the catalog image are updated. A B-series server bundle includes the Capability Catalog update for that server. You do not need to download a separate Capability Catalog update. You only need to activate the Capability Catalog update. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All. Click the Capability Catalog node. In the Work pane, click the Catalog Update Tasks tab. Step 5 Step 6 Click Update Catalog. In the Download Firmware dialog box, click the Local File System radio button in the Location of the Image File field. In the Filename field, type the full path and and name of the image file. If you do not know the exact path to the folder where the firmware image file is located, click Browse and navigate to the file. Step 7 Step 8 Click OK. Cisco UCS Manager downloads the image and updates the Capability Catalog. You do not need to reboot any hardware components. What to Do Next Activate the Capability Catalog update. Updating Management Extensions Management Extensions Management Extension updates are included in each Cisco UCS Manager update. Unless otherwise instructed by Cisco Technical Support, you only need to activate the Management Extension update after you've downloaded, updated, and activated an Cisco UCS Infrastructure Software Bundle. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 235 Updating Management Extensions Management Extensions enable you to add support for previously unsupported servers and other hardware to Cisco UCS Manager. For example, you may need to activate a Management Extension if you want to add a new, previously unsupported server to an existing Cisco UCS domain. The Management Extension image contains the images, information, and firmware required by Cisco UCS Manager to be able to manage the new hardware. Cisco UCS Manager may need to access a Management Extension when you activate. Therefore, the Management Extension is locked during the activation and update process. Activating a Management Extension The Management Extension is included in the server bundle that you have already downloaded. You do not need to download the Management Extension separately. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All. Click the Management Extension node. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Activate Management Extension. In the Activate Management Extension dialog box, choose the management extension that you want to activate from the Version to be Activated drop-down list. Click OK. Step 7 Cisco UCS Manager GUI Configuration Guide, Release 2.0 236 OL-25712-04 CHAPTER 12 Configuring DNS Servers This chapter includes the following sections: • DNS Servers in Cisco UCS , page 237 • Adding a DNS Server, page 237 • Deleting a DNS Server, page 238 DNS Servers in Cisco UCS You need to specify an external DNS server for each Cisco UCS domain to use if the system requires name resolution of hostnames. For example, you cannot use a name such as www.cisco.com when you are configuring a setting on a fabric interconnect if you do not configure a DNS server. You would need to use the IP address of the server. Adding a DNS Server Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 In the Admin tab, expand All > Communication Services. Click DNS Management. In the Work pane, click the General tab. Step 5 Step 6 In the DNS Server area, click +. In the Specify DNS Server dialog box, enter the IP address of the DNS server. Step 7 Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 237 Deleting a DNS Server Deleting a DNS Server Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 In the Admin tab, expand All > Communication Services. Click DNS Management. In the Work pane, click the General tab. Step 5 Step 6 Step 7 In the DNS Server area, right-click the DNS server you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 238 OL-25712-04 CHAPTER 13 Configuring System-Related Policies This chapter includes the following sections: • Configuring the Chassis Discovery Policy, page 239 • Configuring the Chassis Connectivity Policy, page 243 • Configuring the Rack Server Discovery Policy, page 244 • Configuring the Aging Time for the MAC Address Table, page 245 Configuring the Chassis Discovery Policy Chassis Discovery Policy The chassis discovery policy determines how the system reacts when you add a new chassis. Cisco UCS Manager uses the settings in the chassis discovery policy to determine the minimum threshold for the number of links between the chassis and the fabric interconnect and whether to group links from the IOM to the fabric interconnect in a fabric port channel. Chassis Links If you have a Cisco UCS domain that has some chassis wired with 1 link, some with 2 links, some with 4 links, and some with 8 links we recommend that you configure the chassis discovery policy for the minimum number links in the domain so that Cisco UCS Manager can discover all chassis. Tip For Cisco UCS implementations that mix IOMs with different numbers of links, we recommend using the platform max value. Using platform max insures that Cisco UCS Manager uses the maximum number of IOM uplinks available. After the initial discovery, you must reacknowledge the chassis that are wired for a greater number of links and Cisco UCS Manager configures the chassis to use all available links. Cisco UCS Manager cannot discover any chassis that is wired for fewer links than are configured in the chassis discovery policy. For example, if the chassis discovery policy is configured for 4 links, Cisco UCS Manager Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 239 Configuring the Chassis Discovery Policy cannot discover any chassis that is wired for 1 link or 2 links. Reacknowledgement of the chassis does not resolve this issue. The following table provides an overview of how the chassis discovery policy works in a multi-chassis Cisco UCS domain: Table 9: Chassis Discovery Policy and Chassis Links Number of 1-Link Chassis 2-Link Chassis 4-Link Chassis 8-Link Chassis Links Wired Discovery Discovery Discovery Discovery Policy for the Chassis Policy Policy Policy Platform-Max Discovery Policy 1 link between IOM and fabric interconnects Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 1 link. Chassis cannot be discovered by Cisco UCS Manager and is not added to the Cisco UCS domain. Chassis cannot be discovered by Cisco UCS Manager and is not added to the Cisco UCS domain. Chassis cannot be discovered by Cisco UCS Manager and is not added to the Cisco UCS domain. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 1 link. 2 links between IOM and fabric interconnects Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 1 link. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 2 link. Chassis cannot be discovered by Cisco UCS Manager and is not added to the Cisco UCS domain. Chassis cannot be discovered by Cisco UCS Manager and is not added to the Cisco UCS domain. Chassis cannot be discovered by Cisco UCS Manager and is not added to the Cisco UCS domain. After initial discovery, reacknowledge the chassis and Cisco UCS Manager recognizes and uses the additional links. Cisco UCS Manager GUI Configuration Guide, Release 2.0 240 OL-25712-04 Configuring the Chassis Discovery Policy Number of 1-Link Chassis 2-Link Chassis 4-Link Chassis 8-Link Chassis Links Wired Discovery Discovery Discovery Discovery Policy for the Chassis Policy Policy Policy 4 links between IOM and fabric interconnects 8 links between IOM and fabric interconnects Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 1 link. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 2 links. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 4 link. Chassis cannot be discovered by Cisco UCS Manager and is not added to the Cisco UCS domain. After initial discovery, reacknowledge the chassis and Cisco UCS Manager recognizes and uses the additional links. After initial discovery, reacknowledge the chassis and Cisco UCS Manager recognizes and uses the additional links. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 1 link. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 2 links. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 4 links. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 8 links. After initial discovery, reacknowledge the chassis and Cisco UCS Manager recognizes and uses the additional links. After initial discovery, reacknowledge the chassis and Cisco UCS Manager recognizes and uses the additional links. After initial discovery, reacknowledge the chassis and Cisco UCS Manager recognizes and uses the additional links. Platform-Max Discovery Policy If the IOM has 4 links, the chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 4 links. If the IOM has 8 links, the chassis is not fully discovered by Cisco UCS Manager. Chassis is discovered by Cisco UCS Manager and added to the Cisco UCS domain as a chassis wired with 8 links. Link Grouping For hardware configurations that support fabric port channels, link grouping determines whether all of the links from the IOM to the fabric interconnect are grouped into a fabric port channel during chassis discovery. If the link grouping preference is set to port channel, all of the links from the IOM to the fabric interconnect Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 241 Configuring the Chassis Discovery Policy are grouped in a fabric port channel. If set to no group, links from the IOM to the fabric interconnect are not grouped in a fabric port channel. Once a fabric port channel is created, links can be added or removed by changing the link group preference and reacknowledging the chassis, or by enabling or disabling the chassis from the port channel. Note The link grouping preference only takes effect if both sides of the links between an IOM or FEX and the fabric interconnect support fabric port channels. If one side of the links does not support fabric port channels, this preference is ignored and the links are not grouped in a port channel. Configuring the Chassis Discovery Policy Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Policies tab. Step 4 Step 5 Click the Global Policies subtab. In the Chassis Discovery Policy area, complete the following fields: Name Description Action field Specifies the minimum threshold for the number of links between the chassis and the fabric interconnect. This can be one of the following: • 1-link • 2-link • 4-link • 8-link • Platform Max Link Grouping Preference field Specifies whether the links from the IOMs to the fabric interconnects are grouped in a port channel. This can be one of the following: • None—No links are grouped in a port channel • Port Channel—All links from an IOM to a fabric interconnect are grouped in a port channel Note The link grouping preference only takes effect if both sides of the links between an IOM or FEX and the fabric interconnect support fabric port channels. If one side of the links does not support fabric port channels, this preference is ignored and the links are not grouped in a port channel. Cisco UCS Manager GUI Configuration Guide, Release 2.0 242 OL-25712-04 Configuring the Chassis Connectivity Policy Step 6 Click Save Changes. What to Do Next To customize fabric port channel connectivity for a specific chassis, configure the chassis connectivity policy. Configuring the Chassis Connectivity Policy Chassis Connectivity Policy The chassis connectivity policy determines the whether a specific chassis is included in a fabric port channel after chassis discovery. This policy is helpful for users who want to configure one or more chassis differently from what is specified in the global chassis discovery policy. The chassis connectivity policy also allows for different connectivity modes per fabric interconnect, further expanding the level of control offered with regards to chassis connectivity. By default, the chassis connectivity policy is set to global. This means that connectivity control is configured when the chassis is newly discovered, using the settings configured in the chassis discovery policy. Once the chassis is discovered, the chassis connectivity policy controls whether the connectivity control is set to none or port channel. Note The chassis connectivity policy is created by Cisco UCS Manager only when the hardware configuration supports fabric port channels. At this time, only the 6200 series fabric interconnects and the 2200 series IOMs support this feature. For all other hardware combinations, Cisco UCS Manager does not create a chassis connectivity policy. Configuring a Chassis Connectivity Policy Changing the connectivity mode for a chassis could result in decreased VIF namespace. Caution Changing the connectivity mode for a chassis results in chassis reacknowledgement. Traffic may be disrupted during this time. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis. Click the chassis for which you want to configure the connectivity between the IOMs and fabric interconnects. In the Work pane, click the Connectivity Policy tab. Step 5 For each IOM in the chassis, choose one of the following values in the Admin State field for the chassis and fabric connectivity: • None—No links are grouped in a port channel Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 243 Configuring the Rack Server Discovery Policy • Port Channel—All links from an IOM to a fabric interconnect are grouped in a port channel. • Global—The chassis inherits this configuration from the chassis discovery policy. This is the default value. Step 6 Click Save Changes. Configuring the Rack Server Discovery Policy Rack Server Discovery Policy The rack server discovery policy determines how the system reacts when you add a new rack-mount server. Cisco UCS Manager uses the settings in the rack server discovery policy to determine whether any data on the hard disks are scrubbed and whether server discovery occurs immediately or needs to wait for explicit user acknowledgement. Cisco UCS Manager cannot discover any rack-mount server that has not been correctly cabled and connected to the fabric interconnects. For information about how to integrate a supported Cisco UCS rack-mount server with Cisco UCS Manager, see the hardware installation guide for that server. Configuring the Rack Server Discovery Policy Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Policies tab. Step 4 Step 5 Click the Global Policies subtab. In the Rack Server Discovery Policy area, complete the following fields: Name Description Action field The way the system reacts when you add a new rack-mount server. This can be one of the following: • Immediate—The system attempts to discover new servers automatically • User Acknowledged—The system waits until the user tells it to search for new servers Scrub Policy drop-down list The scrub policy to run on a newly discovered server if that server meets the criteria in the selected server pool policy qualification. Cisco UCS Manager GUI Configuration Guide, Release 2.0 244 OL-25712-04 Configuring the Aging Time for the MAC Address Table Step 6 Click Save Changes. Configuring the Aging Time for the MAC Address Table Aging Time for the MAC Address Table To efficiently switch packets between ports, the fabric interconnect maintains a MAC address table. It dynamically builds the MAC address table by using the MAC source address from the packets received and the associated port on which the packets were learned. The fabric interconnect uses an aging mechanism, defined by a configurable aging timer, to determine how long an entry remains in the MAC address table. If an address remains inactive for a specified number of seconds, it is removed from the MAC address table. You can configure the amount of time (age) that a MAC address entry (MAC address and associated port) remains in the MAC address table. Configuring the Aging Time for the MAC Address Table Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Policies tab. Step 4 Step 5 Click the Global Policies subtab. In the MAC Address Table Aging area, complete the following fields: Name Description Aging Time field The length of time an idle MAC address remains in the MAC address table before it is removed by Cisco UCS. This can be one of the following: • Never—MAC addresses are never removed from the table regardless of how long they have been idle. • Mode Default—The system uses the default value. If the fabric interconnect is set to end-host mode, the default is 14,500 seconds. If it is set to switching mode, the default is 300 seconds. • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field which allows you to enter a custom value. dd:hh:mm:ss field The length of time a MAC address must remain idle before Cisco UCS removes it from the MAC address table. This field is only visible if you choose other for the aging time. Enter a time in the format days:hours:minutes:seconds. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 245 Configuring the Aging Time for the MAC Address Table Step 6 Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 246 OL-25712-04 CHAPTER 14 Managing Licenses This chapter includes the following sections: • Licenses, page 247 • Obtaining the Host ID for a Fabric Interconnect, page 248 • Obtaining a License, page 249 • Downloading Licenses to the Fabric Interconnect from the Local File System, page 250 • Downloading Licenses to the Fabric Interconnect from a Remote Location, page 251 • Installing a License, page 252 • Viewing the Licenses Installed on a Fabric Interconnect, page 253 • Determining the Grace Period Available for a Port or Feature, page 255 • Determining the Expiry Date of a License, page 256 • Uninstalling a License, page 256 Licenses Each Cisco UCS fabric interconnect comes with several port licenses that are factory installed and shipped with the hardware. Fabric interconnects can be purchased fully licensed or partially licensed. Additional licenses can also be purchased after delivery. At a minimum, each fabric interconnect ships with the following counted licenses pre-installed: • Cisco UCS 6120XP fabric interconnect—pre-installed licenses for the first eight Ethernet ports enabled in Cisco UCS Manager and any Fibre Channel ports on expansion modules • Cisco UCS 6140XP fabric interconnect—pre-installed licenses for the first sixteen Ethernet ports enabled in Cisco UCS Manager and any Fibre Channel ports on expansion modules • Cisco UCS 6248 fabric interconnect—pre-installed licenses for the first twelve unified ports enabled in Cisco UCS Manager. Expansion modules come with eight licenses that can be used on the expansion module or the base module. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 247 Obtaining the Host ID for a Fabric Interconnect • Cisco UCS 6296 fabric interconnect—pre-installed licenses for the first eighteen unified ports enabled in Cisco UCS Manager. Expansion modules come with eight licenses that can be used on the expansion module or the base module. Note The eight default licenses that come with a 6200 series fabric interconnect expansion module can be used to enable ports on the base module, but will travel with the expansion module if it is removed. Upon removal of an expansion module, any default expansion module licenses being used by the base module are removed from the ports on the base module, resulting in unlicensed ports. Port licenses are not bound to physical ports. When you disable a licensed port, that license is then retained for use with the next enabled port. If you want to use additional fixed ports, you must purchase and install licenses for those ports. Important Licenses are not portable across product generations. Licenses purchased for 6100 series fabric interconnects cannot be used to enable ports on 6200 series fabric interconnects or vice-versa. Grace Period If you attempt to use a port that does not have an installed license, Cisco UCS initiates a 120 day grace period. The grace period is measured from the first use of the port without a license and is paused when a valid license file is installed. The amount of time used in the grace period is retained by the system. Note Each physical port has its own grace period. Initiating the grace period on a single port does not initiate the grace period for all ports. If a licensed port is unconfigured, that license is transferred to a port functioning within a grace period. If multiple ports are acting within grace periods, the license is moved to the port whose grace period is closest to expiring. High Availability Configurations To avoid inconsistencies during failover, we recommend that both fabric interconnects in the cluster have the same number of ports licensed. If symmetry is not maintained and failover occurs, Cisco UCS enables the missing licenses and initiates the grace period for each port being used on the failover node. Obtaining the Host ID for a Fabric Interconnect The host ID is also known as the serial number. Cisco UCS Manager GUI Configuration Guide, Release 2.0 248 OL-25712-04 Obtaining a License Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Fabric Interconnects. Click the node for the fabric interconnect for which you want to obtain the host ID. In the Work pane, click the General tab. Step 5 In the Properties area, the host ID is listed in the Serial Number (SN) field. What to Do Next Obtain the required licenses from Cisco. Obtaining a License Note This process may change after the release of this document. If one or more of these steps no longer applies, contact your Cisco representative for information on how to obtain a license file. Before You Begin Obtain the following: • Host ID or serial number for the fabric interconnect • Claim certificate or other proof of purchase document for the fabric interconnect or expansion module Procedure Step 1 Step 2 Step 3 Obtain the product authorization key (PAK) from the claim certificate or other proof of purchase document. Locate the website URL in the claim certificate or proof of purchase document. Access the website URL for the fabric interconnect and enter the serial number and the PAK. Cisco sends you the license file by email. The license file is digitally signed to authorize use on only the requested fabric interconnect. The requested features are also enabled once Cisco UCS Manager accesses the license file. What to Do Next Install the license on the fabric interconnect. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 249 Downloading Licenses to the Fabric Interconnect from the Local File System Downloading Licenses to the Fabric Interconnect from the Local File System Note In a cluster setup, we recommend that you download and install licenses to both fabric interconnects in matching pairs. An individual license is only downloaded to the fabric interconnect that is used to initiate the download. Before You Begin Obtain the required licenses from Cisco. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > License Management. Click the node for the fabric interconnect to which you want to download the license. In the Work pane, click the Download Tasks tab. Step 5 Step 6 Click Download License. In the Download License dialog box, click the Local File System radio button in the Location of the Image File field. In the Filename field, type the full path and and name of the license file. If you do not know the exact path to the folder where the license file is located, click Browse and navigate to the file. Step 7 Step 8 Click OK. Cisco UCS Manager GUI begins downloading the license to the fabric interconnect. Step 9 (Optional) Monitor the status of the download on the Download Tasks tab. Note If Cisco UCS Manager reports that the bootflash is out of space, delete obsolete bundles on the Packages tab to free up space. To view the available space in bootflash, navigate to the fabric interconnect on the Equipment tab and expand the Local Storage Information area on the General tab. Step 10 Repeat this task until all the required licenses have been downloaded to the fabric interconnect. What to Do Next After all of the download tasks have completed, install the licenses. Cisco UCS Manager GUI Configuration Guide, Release 2.0 250 OL-25712-04 Downloading Licenses to the Fabric Interconnect from a Remote Location Downloading Licenses to the Fabric Interconnect from a Remote Location Note In a cluster setup, we recommend that you download and install licenses to both fabric interconnects in matching pairs. An individual license is only downloaded to the fabric interconnect that is used to initiate the download. Before You Begin Obtain the required licenses from Cisco. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > License Management. Click the node for the fabric interconnect to which you want to download the license. In the Work pane, click the Download Tasks tab. Step 5 Step 6 Click Download License. In the Download License dialog box, click the Remote File System radio button in the Location of the Image File field. Complete the following fields: Step 7 Name Description Protocol field The protocol to use when communicating with the remote server. This can be one of the following: • FTP • TFTP • SCP • SFTP Server field The IP address or hostname of the remote server on which the files resides. Note If you use a hostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager. Filename field The name of the license file you want to download. Path field The absolute path to the license file on the remote server, if required. If you use SCP, the absolute path is always required. If you use any other protocol, you may not need to specify a remote path if the file resides in the default download folder. For details about how your file server is configured, contact your system administrator. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 251 Installing a License Step 8 Name Description User field The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP. Password field The password for the remote server username. This field does not apply if the protocol is TFTP. Click OK. Cisco UCS Manager GUI begins downloading the license to the fabric interconnect. Step 9 (Optional) Monitor the status of the download on the Download Tasks tab. Note If Cisco UCS Manager reports that the bootflash is out of space, delete obsolete bundles on the Packages tab to free up space. To view the available space in bootflash, navigate to the fabric interconnect on the Equipment tab and expand the Local Storage Information area on the General tab. Step 10 Repeat this task until all the required licenses have been downloaded to the fabric interconnect. What to Do Next After all of the download tasks have completed, install the licenses. Installing a License Before You Begin Obtain the required licenses from Cisco. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > License Management. In the Work pane, click the Downloaded License Files tab. Step 4 Step 5 Step 6 Choose the license you want to install from the table. Click the Install License button. In the Install License dialog box, click Yes. Cisco UCS Manager GUI installs the license and activates the unlicensed port or feature. Cisco UCS Manager GUI Configuration Guide, Release 2.0 252 OL-25712-04 Viewing the Licenses Installed on a Fabric Interconnect Viewing the Licenses Installed on a Fabric Interconnect Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > License Management. In the Work pane, click the Installed Licenses tab to view the following details of all licenses installed on the fabric interconnect: Name Description License File ID column The unique identifier for the license. Operational State column The operational state of the license. Operational State Description column Details about the operational state. Scope column The fabric on which this license is installed. Version column The version of the license. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 253 Viewing the Licenses Installed on a Fabric Interconnect Name Description Administrative State column The administrative state of the license. This can be one of the following: • Delete Failed—Cisco UCS could not delete the license. If this if the first time the delete failed, resubmit the delete request. If it fails a second time, contact Cisco TAC. • Delete Pending—The user has requested that Cisco UCS delete the license file from this fabric interconnect. • Deleted—Cisco UCS has finished deleting the license file, but it has not yet been removed from the database. • Deleting—Cisco UCS is currently deleting the license. • Install Failed—Cisco UCS could not install the license. If this if the first time the installation failed, reinstall the license. If it fails a second time, contact Cisco TAC. • Install Pending—The license has been downloaded but is not yet installed. • Installed—The license file is installed on the fabric interconnect. • Installing—Cisco UCS is currently installing the license. • Stale—The license file applies to an older fabric interconnect and cannot be used on the current fabric interconnect. The license file should be deleted and, if necessary, replaced with a current license. • Unknown—The state cannot be determined. • Validated—Cisco UCS has verified that this is a valid Cisco license file. Step 4 Click a license in the table to view the following details of that license in the Contents tab below: You may need to expand the license file to view the details of individual licenses in the file. Name Description Name column A navigation tree that lets you view a particular component along with its subcomponents. You can right-click a component to view any actions available for that component. Total Qty column The total number of licenses available in the license package file. Type column The license type. Expiry column The date that the licenses expire. Quantity column The quantity of licenses of the given type in the license package file. Cisco UCS Manager GUI Configuration Guide, Release 2.0 254 OL-25712-04 Determining the Grace Period Available for a Port or Feature Name Description PAK column The Product Authentication Key (PAK) associated with this license, if available. Signature column The signature key associated with the licenses of the given type. Vendor column The company that issued the license package file. Version column The version of the license package file. Determining the Grace Period Available for a Port or Feature Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > License Management. In the Work pane, click the General tab. Step 4 Click a feature in the table to view the following details, including the used grace period, of that feature in the General tab below: Name Description Name field The name of the feature to which the license applies. Scope field The fabric associated with the license. Absolute Quantity field The total number of licenses available. This value is the sum of the number of default licenses plus the number of purchased licenses. Used Quantity field The number of licenses currently being used by the system. If this value exceeds the total number of licenses available, then some ports will stop functioning after their associated grace period expires. Default Quantity field The default number of licenses provided for this Cisco UCS domain. Operational State field The operational state of the license. Grace Period Used field The number of grace period days that this license has used. After the grace period ends, Cisco UCS sends alert messages until a new license is purchased. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 255 Determining the Expiry Date of a License Name Description Peer License Count Comparison The number of licenses on the peer fabric interconnect compared to this field fabric interconnect. This can be one of the following: • exceeds—the peer fabric interconnect has more licenses installed than this fabric interconnect • lacks—the peer fabric interconnect has fewer licenses installed than this fabric interconnect • matching—the same number of licenses are installed on both fabric interconnects Determining the Expiry Date of a License Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > License Management. In the Work pane, click the Installed Licenses tab. Step 4 Step 5 Step 6 Click a license in the table to view the details of that license in the Contents tab below. In the Contents tab, expand the license file to view all licenses in the file. In the Expiry column, view the expiry date of the license. Uninstalling a License Note Permanent licenses cannot be uninstalled if they are in use. You can only uninstall a permanent license that is not in use. If you try to delete a permanent license that is being used, Cisco UCS Manager rejects the request with an error message. Before You Begin • Back up the Cisco UCS Manager configuration. • Disable the feature or port associated with the license you want to uninstall. Cisco UCS Manager GUI Configuration Guide, Release 2.0 256 OL-25712-04 Uninstalling a License Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > License Management. In the Work pane, click the Installed Licenses tab. Step 4 Step 5 Step 6 Choose the license you want to uninstall from the table. Click the Clear License button. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager deactivates the license, removes the license from the list of licenses, and deletes the license from the fabric interconnect. In a cluster setup, you must uninstall the license from the other fabric interconnect. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 257 Uninstalling a License Cisco UCS Manager GUI Configuration Guide, Release 2.0 258 OL-25712-04 CHAPTER 15 Managing Virtual Interfaces This chapter includes the following sections: • Virtual Interfaces, page 259 • Virtual Interface Subscription Management and Error Handling, page 259 Virtual Interfaces In a blade server environment, the number of vNICs and vHBAs configurable for a service profile is determined by adapter capability and the amount of virtual interface (VIF) namespace available on the adapter. In Cisco UCS, portions of VIF namespace are allotted in chunks called VIFs. Depending on your hardware, the maxiumum number of VIFs are allocated on a predefined, per-port basis. The maximum number of VIFs varies based on hardware capability and port connectivity. For each configured vNIC or vHBA, one or two VIFs are allocated. Stand-alone vNICs and vHBAs use one VIF and failover vNICs and vHBAs use two. The following variables affect the number of VIFs available to a blade server, and therefore, how many vNICs and vHBAs you can configure for a service profile. • Maximum number of VIFs supported on your fabric interconnect • How the fabric interconnects are cabled • If your fabric interconnect and IOM are configured in fabric port channel mode For more information about the maximum number of VIFs supported by your hardware configuration, see Cisco UCS 6100 and 6200 Series Configuration Limits for Cisco UCS Manager for your software release. Virtual Interface Subscription Management and Error Handling For fabric interconnects grouped in a port-channel, changes to the way you connect the fabric interconnect to the I/O module could result in a drastic change to the number of VIFs available to a blade server. To help you track the effect of these changes, Cisco UCS Manager maintains the following metrics: • Maximum number of VIFs supported by hardware • Connectivity type Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 259 Virtual Interface Subscription Management and Error Handling If you change your configuration in a way that decreases the number of VIFs available to a blade, UCS Manager will display a warning and ask you if you want to proceed. This includes several scenarios, including times where adding or moving a connection decreases the number of VIFs. Cisco UCS Manager GUI Configuration Guide, Release 2.0 260 OL-25712-04 PART III Network Configuration • Using the LAN Uplinks Manager, page 263 • Configuring VLANs, page 277 • Configuring LAN Pin Groups, page 293 • Configuring MAC Pools, page 295 • Configuring Quality of Service, page 297 • Configuring Network-Related Policies, page 307 • Configuring Upstream Disjoint Layer-2 Networks, page 321 CHAPTER 16 Using the LAN Uplinks Manager This chapter includes the following sections: • LAN Uplinks Manager, page 263 • Launching the LAN Uplinks Manager, page 264 • Changing the Ethernet Switching Mode with the LAN Uplinks Manager, page 264 • Configuring a Port with the LAN Uplinks Manager, page 264 • Configuring Server Ports, page 265 • Configuring Uplink Ethernet Ports, page 266 • Configuring Uplink Ethernet Port Channels, page 267 • Configuring LAN Pin Groups, page 270 • Configuring Named VLANs, page 271 • Configuring QoS System Classes with the LAN Uplinks Manager, page 274 LAN Uplinks Manager The LAN Uplinks Manager provides a single interface where you can configure the connections between Cisco UCS and the LAN. You can use the LAN Uplinks Manager to create and configure the following: • Ethernet switching mode • Uplink Ethernet ports • Port channels • LAN pin groups • Named VLANs • Server ports • QoS system classes Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 263 Launching the LAN Uplinks Manager Some of the configuration that you can do in the LAN Uplinks Manager can also be done in nodes on other tabs, such as the Equipment tab or the LAN tab. Launching the LAN Uplinks Manager Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 On the LAN tab, click the LAN node. In the Work pane, click the LAN Uplinks Manager link on the LAN Uplinks tab. The LAN Uplinks Manager opens in a separate window. Changing the Ethernet Switching Mode with the LAN Uplinks Manager 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 sequentially. The second fabric interconnect can take several minutes to complete the change in Ethernet switching mode and become system ready. The configuration is retained. Procedure Step 1 Step 2 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Uplink Mode area, click one of the following buttons: • Set Ethernet Switching Mode • Set Ethernet End-Host Mode The button for the current switching mode is dimmed. Step 3 In the dialog box, click Yes. Cisco UCS Manager restarts the fabric interconnect, logs you out, and disconnects Cisco UCS Manager GUI. Configuring a Port with the LAN Uplinks Manager You can only configure server ports on the fixed port module. Expansion modules do not include server ports. Cisco UCS Manager GUI Configuration Guide, Release 2.0 264 OL-25712-04 Configuring Server Ports Procedure Step 1 Step 2 Step 3 Step 4 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Ports area, click the down arrows to expand the Unconfigured Ports section. Expand Fabric Interconnects > Fabric_Interconnect_Name . Expand one of the following: • Fixed Module—To configure a port in the fixed module as a server port or an uplink Ethernet port. • Expansion Module Number —To enable a port in an expansion module as an uplink Ethernet port. You cannot configure ports in expansion modules as server ports. If no ports are listed below the node that you expanded, all ports in that module have already been configured. Step 5 Right-click the port that you want to configure and choose one of the following: • Configure as Server Port • Configure as Uplink Port Step 6 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Configuring Server Ports Enabling a Server Port with the LAN Uplinks Manager This procedure assumes that the port has been configured as a server port, but is disabled. Procedure Step 1 Step 2 Step 3 Step 4 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Ports area, click the down arrows to expand the Server Ports section. Expand Fabric Interconnects > Fabric_Interconnect_Name . Right-click the port that you want to enable and choose Enable. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 265 Configuring Uplink Ethernet Ports Disabling a Server Port with the LAN Uplinks Manager Procedure Step 1 Step 2 Step 3 Step 4 Step 5 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Ports area, click the down arrows to expand the Server Ports section. Expand Fabric Interconnects > Fabric_Interconnect_Name . Right-click the port that you want to disable and choose Disable. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Unconfiguring a Server Port with the LAN Uplinks Manager Procedure Step 1 Step 2 Step 3 Step 4 Step 5 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Ports area, click the down arrows to expand the Server Ports section. Expand Fabric Interconnects > Fabric_Interconnect_Name . Right-click the port that you want to unconfigure and choose Unconfigure. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Configuring Uplink Ethernet Ports Enabling an Uplink Ethernet Port with the LAN Uplinks Manager This procedure assumes that the port has been configured as an uplink Ethernet port, but is disabled. Procedure Step 1 Step 2 Step 3 Step 4 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Port Channels and Uplinks area, expand Interfaces > Fabric Interconnects > Fabric_Interconnect_Name . Right-click the port that you want to enable and choose Enable Interface. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 266 OL-25712-04 Configuring Uplink Ethernet Port Channels Disabling an Uplink Ethernet Port with the LAN Uplinks Manager Procedure Step 1 Step 2 Step 3 Step 4 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Port Channels and Uplinks area, expand Interfaces > Fabric Interconnects > Fabric_Interconnect_Name . Right-click the port that you want to disable and choose Disable Interfaces. You can select multiple ports if you want to disable more than one uplink Ethernet port. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. The disabled port is removed from the list of enabled interfaces and returned to the Unconfigured Ports list. Unconfiguring an Uplink Ethernet Port with the LAN Uplinks Manager Procedure Step 1 Step 2 Step 3 Step 4 Step 5 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Port Channels and Uplinks area, expand Interfaces > Fabric Interconnects > Fabric_Interconnect_Name . Click the port that you want to unconfigure. You can select multiple ports if you want to unconfigure more than one uplink Ethernet port. Click Disable Interface. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. The disabled port is removed from the list of enabled interfaces and returned to the Unconfigured Ports list. Configuring Uplink Ethernet Port Channels Creating a Port Channel with the LAN Uplinks Manager Procedure Step 1 Step 2 Step 3 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Port Channels and Uplinks area, click Create Port Channel. From the pop-up menu, select one of the following fabric interconnects where you want to create the port channel: • Fabric Interconnect A Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 267 Configuring Uplink Ethernet Port Channels • Fabric Interconnect B Step 4 In the Set Port Channel Name page of the Create Port Channel wizard, do the following: a) Complete the following fields: Name Description ID field The identifier for the port channel. Enter an integer between 1 and 256. This ID cannot be changed after the port channel has been saved. Name field A user-defined name for the port channel. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. b) Click Next. Step 5 In the Add Ports page of the Create Port Channel wizard, do the following: a) In the Ports table, choose one or more ports to include in the port channel. b) Click the >> button to add the ports to the Ports in the port channel table. You can use the << button to remove ports from the port channel. Note Step 6 Cisco UCS Manager warns you if you select a port that has been configured as a server port. You can click Yes in the dialog box to reconfigure that port as an uplink Ethernet port and include it in the port channel. Click Finish. Enabling a Port Channel with the LAN Uplinks Manager Procedure Step 1 Step 2 Step 3 Step 4 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Port Channels and Uplinks area, expand Port Channels > Fabric Interconnects > Fabric_Interconnect_Name. Right-click the port channel that you want to enable and choose Enable Port Channel. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 268 OL-25712-04 Configuring Uplink Ethernet Port Channels Disabling a Port Channel with the LAN Uplinks Manager Procedure Step 1 Step 2 Step 3 Step 4 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Port Channels and Uplinks area, expand Port Channels > Fabric Interconnects > Fabric_Interconnect_Name. Right-click the port channel that you want to disable and choose Disable Port Channel. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Adding Ports to a Port Channel with the LAN Uplinks Manager Procedure Step 1 Step 2 Step 3 Step 4 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Port Channels and Uplinks area, expand Port Channels > Fabric Interconnects > Fabric_Interconnect_Name. Right-click the port channel to which you want to add ports and choose Add Ports. In the Add Ports dialog box, do the following: a) In the Ports table, choose one or more ports to include in the port channel. b) Click the >> button to add the ports to the Ports in the port channel table. You can use the << button to remove ports from the port channel. Note Step 5 Cisco UCS Manager warns you if you select a port that has been configured as a server port. You can click Yes in the dialog box to reconfigure that port as an uplink Ethernet port and include it in the port channel. Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 269 Configuring LAN Pin Groups Removing Ports from a Port Channel with the LAN Uplinks Manager Procedure Step 1 Step 2 Step 3 Step 4 Step 5 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Port Channels and Uplinks area, expand Port Channels > Fabric Interconnects > Fabric_Interconnect_Name. Expand the port channel from which you want to remove ports. Right-click the port you want to remove from the port channel and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Deleting a Port Channel with the LAN Uplinks Manager Procedure Step 1 Step 2 Step 3 Step 4 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Port Channels and Uplinks area, expand Port Channels > Fabric Interconnects > Fabric_Interconnect_Name. Right-click the port channel you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Configuring LAN Pin Groups Creating a Pin Group with the LAN Uplinks Manager In a system with two fabric interconnects, you can associate the pin group with only one fabric interconnect or with both fabric interconnects. Before You Begin Configure the ports and port channels with which you want to configure the pin group. You can only include ports and port channels configured as uplink ports in a LAN pin group. Cisco UCS Manager GUI Configuration Guide, Release 2.0 270 OL-25712-04 Configuring Named VLANs Procedure Step 1 Step 2 Step 3 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Port Channels and Uplinks area, click Create Pin Group. In the Create LAN Pin Group dialog box, enter a unique name and description for the pin group. Step 4 To pin traffic for fabric interconnect A, do the following in the Targets area: a) Check the Fabric Interconnect A check box. b) Click the drop-down arrow on the Interface field and navigate through the tree-style browser to select the port or port channel you want to associate with the pin group. Step 5 To pin traffic for fabric interconnect B, do the following in the Targets area: a) Check the Fabric Interconnect B check box. b) Click the drop-down arrow on the Interface field and navigate through the tree-style browser to select the port or port channel you want to associate with the pin group. Step 6 Click OK. What to Do Next Include the pin group in a vNIC template. Deleting a Pin Group with the LAN Uplinks Manager Procedure Step 1 Step 2 Step 3 In the LAN Uplinks Manager, click the LAN Uplinks tab. In the Pin Groups area, right-click the pin group you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Configuring Named VLANs Creating a Named VLAN with the LAN Uplinks Manager In a Cisco UCS domain with two switches, you can create a named VLAN that is accessible to both switches or to only one switch. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 271 Configuring Named VLANs Important You cannot create VLANs with IDs from 3968 to 4047. This range of VLAN IDs is reserved. VLANs in the LAN cloud and FCoE VLANs in the SAN cloud must have different IDs. Using the same ID for a VLAN and an FCoE VLAN in a VSAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. Procedure Step 1 Step 2 In the LAN Uplinks Manager, click the VLANs tab. On the icon bar to the right of the table, click +. If the + icon is disabled, click an entry in the table to enable it. Step 3 In the Create VLANs dialog box, complete the following fields: Name Description VLAN Name/Prefix field For a single VLAN, this is the VLAN name. For a range of VLANs, this is the prefix that the system uses for each VLAN name. The VLAN name is case sensitive. This name can be between 1 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Configuration options You can choose one of the following: • Common/Global—The VLANs apply to both fabrics and use the same configuration parameters in both cases • Fabric A—The VLANs only apply to fabric A. • Fabric B—The VLAN only apply to fabric B. • Both Fabrics Configured Differently—The VLANs apply to both fabrics but you can specify different VLAN IDs for each fabric. For upstream disjoint L2 networks, we recommend that you choose Common/Global to create VLANs that apply to both fabrics. Cisco UCS Manager GUI Configuration Guide, Release 2.0 272 OL-25712-04 Configuring Named VLANs Name Description VLAN IDs field To create one VLAN, enter a single numeric ID. To create multiple VLANs, enter individual IDs or ranges of IDs separated by commas. A VLAN ID can: • Be between 1 and 3967 • Be between 4048 and 4093 • Overlap with other VLAN IDs already defined on the system For example, to create six VLANs with the IDs 4, 22, 40, 41, 42, and 43, you would enter 4, 22, 40-43. Important You cannot create VLANs with IDs from 3968 to 4047. This range of VLAN IDs is reserved. VLANs in the LAN cloud and FCoE VLANs in the SAN cloud must have different IDs. Using the same ID for a VLAN and an FCoE VLAN in a VSAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. Sharing Type field Whether this VLAN is subdivided into private or secondary VLANs. This can be one of the following: • None—This VLAN does not have any secondary or private VLANs. • Primary—This VLAN can have one or more secondary VLANs, as shown in the Secondary VLANs area. • Isolated—This is a private VLAN. The primary VLAN with which it is associated is shown in the Primary VLAN drop-down list. Step 4 Primary VLAN drop-down list If the Sharing Type field is set to Isolated, this is the primary VLAN associated with this private VLAN. Check Overlap button Click this button to determine whether the VLAN ID overlaps with any other IDs on the system. Click OK. Cisco UCS Manager adds the VLAN to one of the following VLANs nodes: • The LAN Cloud > VLANs node for a VLAN accessible to both fabric interconnects. • The Fabric_Interconnect_Name > VLANs node for a VLAN accessible to only one fabric interconnect. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 273 Configuring QoS System Classes with the LAN Uplinks Manager Deleting a Named VLAN with the LAN Uplinks Manager If Cisco UCS Manager includes a named VLAN with the same VLAN ID as the one you delete, the VLAN is not removed from the fabric interconnect configuration until all named VLANs with that ID are deleted. Procedure Step 1 Step 2 In the LAN Uplinks Manager, click the VLANs tab. Click one of the following subtabs, depending upon what type of VLAN you want to delete: Subtab Description All Displays all VLANs in the Cisco UCS domain. Dual Mode Displays the VLANs that are accessible to both fabric interconnects. Fabric A Displays the VLANs that are accessible to only fabric interconnect A. Fabric B Displays the VLANs that are accessible to only fabric interconnect B. Step 3 In the table, click the VLAN you want to delete. You can use the Shift key or Ctrl key to select multiple entries. Step 4 Step 5 Right-click the highlighted VLAN or VLANs and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Configuring QoS System Classes with the LAN Uplinks Manager The type of adapter in a server may limit the maximum MTU supported. For example, network MTU above the maximums may cause the packet to be dropped for the following adapters: • The Cisco UCS M71KR CNA adapter, which supports a maximum MTU of 9216. • The Cisco UCS 82598KR-CI adapter, which supports a maximum MTU of 14000. Procedure Step 1 Step 2 In the LAN Uplinks Manager, click the QoS tab. Update the following properties for the system class you want to configure to meet the traffic management needs of the system: Note Some properties may not be configurable for all system classes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 274 OL-25712-04 Configuring QoS System Classes with the LAN Uplinks Manager Name Description Enabled check box If checked, the associated QoS class is configured on the fabric interconnect and can be assigned to a QoS policy. If unchecked, the class is not configured on the fabric interconnect and any QoS policies associated with this class default to Best Effort or, if a system class is configured with a Cos of 0, to the Cos 0 system class. Note CoS field The class of service. You can enter an integer value between 0 and 6, with 0 being the lowest priority and 6 being the highest priority. We recommend that you do not set the value to 0, unless you want that system class to be the default system class for traffic if the QoS policy is deleted or the assigned system class is disabled. Note Packet Drop check box This field is always checked for Best Effort and Fibre Channel. This field is set to 7 for internal traffic and to any for Best Effort. Both of these values are reserved and cannot be assigned to any other priority. If checked, packet drop is allowed for this class. If unchecked, packets cannot be dropped during transmission. This field is always unchecked for the Fibre Channel class, which never allows dropped packets, and always checked for Best Effort, which always allows dropped packets. Weight drop-down list This can be one of the following: • An integer between 1 and 10. If you enter an integer, Cisco UCS determines the percentage of network bandwidth assigned to the priority level as described in the Weight (%) field. • best-effort. • none. Weight (%) field To determine the bandwidth allocated to a channel, Cisco UCS: 1 Adds the weights for all the channels 2 Divides the channel weight by the sum of all weights to get a percentage 3 Allocates that percentage of the bandwidth to the channel Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 275 Configuring QoS System Classes with the LAN Uplinks Manager Name Description MTU drop-down list The maximum transmission unit for the channel. This can be one of the following: • An integer between 1500 and 9216. This value corresponds to the maximum packet size. • fc—A predefined packet size of 2240. • normal—A predefined packet size of 1500. Note Multicast Optimized check box If checked, the class is optimized to send packets to multiple destinations simultaneously. Note Step 3 This field is always set to fc for Fibre Channel. This option is not applicable to the Fibre Channel. Do one of the following: • Click OK to save your changes and exit from the LAN Uplinks Manager. • Click Apply to save your changes without exiting from the LAN Uplinks Manager. Cisco UCS Manager GUI Configuration Guide, Release 2.0 276 OL-25712-04 CHAPTER 17 Configuring VLANs This chapter includes the following sections: • Named VLANs, page 277 • Private VLANs, page 278 • VLAN Port Limitations, page 279 • Configuring Named VLANs, page 280 • Configuring Private VLANs, page 285 • Viewing the VLAN Port Count, page 291 Named VLANs A named VLAN creates a connection to a specific external LAN. The VLAN isolates traffic to that external LAN, including broadcast traffic. The name that you assign to a VLAN ID adds a layer of abstraction that allows you to globally update all servers associated with service profiles that use the named VLAN. You do not need to reconfigure the servers individually to maintain communication with the external LAN. You can create more than one named VLAN with the same VLAN ID. For example, if servers that host business services for HR and Finance need to access the same external LAN, you can create VLANs named HR and Finance with the same VLAN ID. Then, if the network is reconfigured and Finance is assigned to a different LAN, you only have to change the VLAN ID for the named VLAN for Finance. In a cluster configuration, you can configure a named VLAN to be accessible only to one fabric interconnect or to both fabric interconnects. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 277 Private VLANs Guidelines for VLAN IDs Important You cannot create VLANs with IDs from 3968 to 4047. This range of VLAN IDs is reserved. VLANs in the LAN cloud and FCoE VLANs in the SAN cloud must have different IDs. Using the same ID for a VLAN and an FCoE VLAN in a VSAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. VLAN 4048 is user-configurable. However, Cisco UCS Manager uses VLAN 4048 for the following default values. If you want to assign 4048 to a VLAN, you must reconfigure these values: • After an upgrade to Cisco UCS, release 2.0: The FCoE storage port native VLAN uses VLAN 4048 by default. If the default FCoE VSAN was set to use VLAN 1 before the upgrade, you must change it to a VLAN ID that is not used or reserved. For example, consider changing the default to 4049 if that VLAN ID is not in use. • After a fresh install of Cisco UCS, release 2.0: The FCoE VLAN for the default VSAN uses VLAN 4048 by default. The FCoE storage port native VLAN uses VLAN 4049. The VLAN name is case sensitive. Private VLANs A private VLAN (PVLAN) partitions the Ethernet broadcast domain of a VLAN into subdomains and allows you to isolate some ports. Each subdomain in a PVLAN includes a primary VLAN and one or more secondary VLANs. All secondary VLANs in a PVLAN must share the same primary VLAN. The secondary VLAN ID differentiates one subdomain from another. Isolated VLANs All secondary VLANs in a Cisco UCS domain must be isolated VLANs. Cisco UCS does not support community VLANs. Ports on Isolated VLANs Communications on an isolated VLAN can only use the associated port in the primary VLAN. These ports are isolated ports and are not configurable in Cisco UCS Manager. If the primary VLAN includes multiple secondary VLANs, those isolated VLANs cannot communicate directly with each other. An isolated port is a host port that belongs to an isolated secondary VLAN. This port has complete isolation from other ports within the same private VLAN domain. PVLANs block all traffic to isolated ports except traffic from promiscuous ports. Traffic received from an isolated port is forwarded only to promiscuous ports. You can have more than one isolated port in a specified isolated VLAN. Each port is completely isolated from all other ports in the isolated VLAN. Guidelines for Uplink Ports When you create PVLANs, be aware of the following guidelines: • The uplink Ethernet port channel cannot be in promiscuous mode. • Each primary VLAN can have only one isolated VLAN. Cisco UCS Manager GUI Configuration Guide, Release 2.0 278 OL-25712-04 VLAN Port Limitations • VIFs on VNTAG adapters can have only one isolated VLAN. Guidelines for VLAN IDs Important You cannot create VLANs with IDs from 3968 to 4047. This range of VLAN IDs is reserved. VLANs in the LAN cloud and FCoE VLANs in the SAN cloud must have different IDs. Using the same ID for a VLAN and an FCoE VLAN in a VSAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. VLAN 4048 is user-configurable. However, Cisco UCS Manager uses VLAN 4048 for the following default values. If you want to assign 4048 to a VLAN, you must reconfigure these values: • After an upgrade to Cisco UCS, release 2.0: The FCoE storage port native VLAN uses VLAN 4048 by default. If the default FCoE VSAN was set to use VLAN 1 before the upgrade, you must change it to a VLAN ID that is not used or reserved. For example, consider changing the default to 4049 if that VLAN ID is not in use. • After a fresh install of Cisco UCS, release 2.0: The FCoE VLAN for the default VSAN uses VLAN 4048 by default. The FCoE storage port native VLAN uses VLAN 4049. The VLAN name is case sensitive. VLAN Port Limitations Cisco UCS Manager limits the number of VLAN port instances that can be configured under border and server domains on a fabric interconnect to 6000. Types of Ports Included in the VLAN Port Count The following types of ports are counted in the VLAN port calculation: • Border uplink Ethernet ports • Border uplink Ether-channel member ports • FCoE ports in a SAN cloud • Ethernet ports in a NAS cloud • Static and dynamic vNICs created through service profiles • VM vNICs created as part of a port profile in a hypervisor in hypervisor domain Based on the number of VLANs configured for these ports, Cisco UCS Manager keeps track of the cumulative count of VLAN port instances and enforces the VLAN port limit during validation. Cisco UCS Manager reserves some pre-defined VLAN port resources for control traffic. These include management VLANs configured under HIF and NIF ports. VLAN Port Limit Enforcement Cisco UCS Manager validates VLAN port availability during the following operations. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 279 Configuring Named VLANs • Configuring and unconfiguring border ports and border port channels • Adding or removing VLANs from a cloud • Configuring or unconfiguring SAN or NAS ports • Associating or disassociating service profiles that contain configuration changes • Configuring or unconfiguring VLANs under vNICs or vHBAs • Upon receiving creation or deleting notifications from a VMWare vNIC, from an ESX hypervisor Note This is outside the control of Cisco UCS Manager • Fabric interconnect reboot • Cisco UCS Manager upgrade or downgrade Cisco UCS Manager strictly enforces the VLAN port limit on service profile operations. If Cisco UCS Manager detects that you have exceeded the VLAN port limit service profile configuration will fail during deployment. Exceeding the VLAN port count in a border domain is less disruptive. When the VLAN port count is exceeded in a border domainCisco UCS Manager changes the allocation status to Exceeded. In order to change the status back to Available, you should complete one of the following actions: • Unconfigure one or more border ports • Remove VLANs from the LAN cloud • Unconfigure one or more vNICs or vHBAs Configuring Named VLANs Creating a Named VLAN In a Cisco UCS domain that is configured for high availability, you can create a named VLAN that is accessible to both fabric interconnects or to only one fabric interconnect. Important You cannot create VLANs with IDs from 3968 to 4047. This range of VLAN IDs is reserved. VLANs in the LAN cloud and FCoE VLANs in the SAN cloud must have different IDs. Using the same ID for a VLAN and an FCoE VLAN in a VSAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. Cisco UCS Manager GUI Configuration Guide, Release 2.0 280 OL-25712-04 Configuring Named VLANs Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 On the LAN tab, click the LAN node. In the Work pane, click the VLANs tab. Step 4 On the icon bar to the right of the table, click +. If the + icon is disabled, click an entry in the table to enable it. Step 5 In the Create VLANs dialog box, complete the following fields: Name Description VLAN Name/Prefix field For a single VLAN, this is the VLAN name. For a range of VLANs, this is the prefix that the system uses for each VLAN name. The VLAN name is case sensitive. This name can be between 1 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Configuration options You can choose one of the following: • Common/Global—The VLANs apply to both fabrics and use the same configuration parameters in both cases • Fabric A—The VLANs only apply to fabric A. • Fabric B—The VLAN only apply to fabric B. • Both Fabrics Configured Differently—The VLANs apply to both fabrics but you can specify different VLAN IDs for each fabric. For upstream disjoint L2 networks, we recommend that you choose Common/Global to create VLANs that apply to both fabrics. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 281 Configuring Named VLANs Name Description VLAN IDs field To create one VLAN, enter a single numeric ID. To create multiple VLANs, enter individual IDs or ranges of IDs separated by commas. A VLAN ID can: • Be between 1 and 3967 • Be between 4048 and 4093 • Overlap with other VLAN IDs already defined on the system For example, to create six VLANs with the IDs 4, 22, 40, 41, 42, and 43, you would enter 4, 22, 40-43. Important You cannot create VLANs with IDs from 3968 to 4047. This range of VLAN IDs is reserved. VLANs in the LAN cloud and FCoE VLANs in the SAN cloud must have different IDs. Using the same ID for a VLAN and an FCoE VLAN in a VSAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. Sharing Type field Whether this VLAN is subdivided into private or secondary VLANs. This can be one of the following: • None—This VLAN does not have any secondary or private VLANs. • Primary—This VLAN can have one or more secondary VLANs, as shown in the Secondary VLANs area. • Isolated—This is a private VLAN. The primary VLAN with which it is associated is shown in the Primary VLAN drop-down list. Step 6 Primary VLAN drop-down list If the Sharing Type field is set to Isolated, this is the primary VLAN associated with this private VLAN. Check Overlap button Click this button to determine whether the VLAN ID overlaps with any other IDs on the system. If you clicked the Check Overlap button, do the following: a) Click the Overlapping VLANs tab and review the following fields to verify that the VLAN ID does not overlap with any IDs assigned to existing VLANs. Cisco UCS Manager GUI Configuration Guide, Release 2.0 282 OL-25712-04 Configuring Named VLANs Name Description Fabric ID column This can be one of the following: •A •B • Dual—The component is accessible to either fabric interconnect. This setting applies to virtual LAN and SAN networks created at the system level as opposed to the fabric interconnect level. Name column The name of the VLAN. VLAN column The numeric id for the VLAN. DN column The full path to the VLAN. Click the link in this column to view the properties for the VLAN. b) Click the Overlapping VSANs tab and review the following fields to verify that the VLAN ID does not overlap with any FCoE VLAN IDs assigned to existing VSANs: Name Description Fabric ID column This can be one of the following: •A •B • Dual—The component is accessible to either fabric interconnect. This setting applies to virtual LAN and SAN networks created at the system level as opposed to the fabric interconnect level. Name column The name of the VSAN. ID column The numeric id for the VSAN. FCoE VLAN ID column The unique identifier assigned to the VLAN used for Fibre Channel connections. DN column The full path to the VSAN. Click the link in this column to view the properties for the VSAN. c) Click OK. d) If Cisco UCS Manager identified any overlapping VLAN IDs or FCoE VLAN IDs, change the VLAN ID to one that does not overlap with an existing VLAN. Step 7 Click OK. Cisco UCS Manager adds the VLAN to one of the following VLANs nodes: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 283 Configuring Named VLANs • The LAN Cloud > VLANs node for a VLAN accessible to both fabric interconnects. • The Fabric_Interconnect_Name > VLANs node for a VLAN accessible to only one fabric interconnect. Deleting a Named VLAN If Cisco UCS Manager includes a named VLAN with the same VLAN ID as the one you delete, the VLAN is not removed from the fabric interconnect configuration until all named VLANs with that ID are deleted. If you are deleting a private primary VLAN, make sure to reassign the secondary VLANs to another working primary VLAN. Before You Begin Before you delete a VLAN from a fabric interconnect, ensure that the VLAN has been removed from all vNICs and vNIC templates. Note If you delete a VLAN that is assigned to a vNIC or vNIC template, the vNIC could allow that VLAN to flap. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 On the LAN tab, click the LAN node. In the Work pane, click the VLANs tab. Step 4 Click one of the following subtabs, depending upon what type of VLAN you want to delete: Subtab Description All Displays all VLANs in the Cisco UCS domain. Dual Mode Displays the VLANs that are accessible to both fabric interconnects. Fabric A Displays the VLANs that are accessible to only fabric interconnect A. Fabric B Displays the VLANs that are accessible to only fabric interconnect B. Step 5 In the table, click the VLAN you want to delete. You can use the Shift key or Ctrl key to select multiple entries. Step 6 Step 7 Right-click the highlighted VLAN or VLANs and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 284 OL-25712-04 Configuring Private VLANs Configuring Private VLANs Creating a Primary VLAN for a Private VLAN In a Cisco UCS domain that is configured for high availability, you can create a primary VLAN that is accessible to both fabric interconnects or to only one fabric interconnect. Important You cannot create VLANs with IDs from 3968 to 4047. This range of VLAN IDs is reserved. VLANs in the LAN cloud and FCoE VLANs in the SAN cloud must have different IDs. Using the same ID for a VLAN and an FCoE VLAN in a VSAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 On the LAN tab, click the LAN node. In the Work pane, click the VLANs tab. Step 4 On the icon bar to the right of the table, click +. If the + icon is disabled, click an entry in the table to enable it. Step 5 In the Create VLANs dialog box, complete the following fields: Name Description VLAN Name/Prefix field For a single VLAN, this is the VLAN name. For a range of VLANs, this is the prefix that the system uses for each VLAN name. The VLAN name is case sensitive. This name can be between 1 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 285 Configuring Private VLANs Name Description Configuration options You can choose one of the following: • Common/Global—The VLANs apply to both fabrics and use the same configuration parameters in both cases • Fabric A—The VLANs only apply to fabric A. • Fabric B—The VLAN only apply to fabric B. • Both Fabrics Configured Differently—The VLANs apply to both fabrics but you can specify different VLAN IDs for each fabric. For upstream disjoint L2 networks, we recommend that you choose Common/Global to create VLANs that apply to both fabrics. VLAN IDs field To create one VLAN, enter a single numeric ID. To create multiple VLANs, enter individual IDs or ranges of IDs separated by commas. A VLAN ID can: • Be between 1 and 3967 • Be between 4048 and 4093 • Overlap with other VLAN IDs already defined on the system For example, to create six VLANs with the IDs 4, 22, 40, 41, 42, and 43, you would enter 4, 22, 40-43. Important You cannot create VLANs with IDs from 3968 to 4047. This range of VLAN IDs is reserved. VLANs in the LAN cloud and FCoE VLANs in the SAN cloud must have different IDs. Using the same ID for a VLAN and an FCoE VLAN in a VSAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. Sharing Type field Whether this VLAN is subdivided into private or secondary VLANs. This can be one of the following: • None—This VLAN does not have any secondary or private VLANs. • Primary—This VLAN can have one or more secondary VLANs, as shown in the Secondary VLANs area. • Isolated—This is a private VLAN. The primary VLAN with which it is associated is shown in the Primary VLAN drop-down list. Primary VLAN drop-down list If the Sharing Type field is set to Isolated, this is the primary VLAN associated with this private VLAN. Cisco UCS Manager GUI Configuration Guide, Release 2.0 286 OL-25712-04 Configuring Private VLANs Step 6 Name Description Check Overlap button Click this button to determine whether the VLAN ID overlaps with any other IDs on the system. If you clicked the Check Overlap button, do the following: a) Click the Overlapping VLANs tab and review the following fields to verify that the VLAN ID does not overlap with any IDs assigned to existing VLANs. Name Description Fabric ID column This can be one of the following: •A •B • Dual—The component is accessible to either fabric interconnect. This setting applies to virtual LAN and SAN networks created at the system level as opposed to the fabric interconnect level. Name column The name of the VLAN. VLAN column The numeric id for the VLAN. DN column The full path to the VLAN. Click the link in this column to view the properties for the VLAN. b) Click the Overlapping VSANs tab and review the following fields to verify that the VLAN ID does not overlap with any FCoE VLAN IDs assigned to existing VSANs: Name Description Fabric ID column This can be one of the following: •A •B • Dual—The component is accessible to either fabric interconnect. This setting applies to virtual LAN and SAN networks created at the system level as opposed to the fabric interconnect level. Name column The name of the VSAN. ID column The numeric id for the VSAN. FCoE VLAN ID column The unique identifier assigned to the VLAN used for Fibre Channel connections. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 287 Configuring Private VLANs Name Description DN column The full path to the VSAN. Click the link in this column to view the properties for the VSAN. c) Click OK. d) If Cisco UCS Manager identified any overlapping VLAN IDs or FCoE VLAN IDs, change the VLAN ID to one that does not overlap with an existing VLAN. Step 7 Click OK. Cisco UCS Manager adds the primary VLAN to one of the following VLANs nodes: • The LAN Cloud > VLANs node for a primary VLAN accessible to both fabric interconnects. • The Fabric_Interconnect_Name > VLANs node for a primary VLAN accessible to only one fabric interconnect. Creating a Secondary VLAN for a Private VLAN In a Cisco UCS domain that is configured for high availability, you can create a secondary VLAN that is accessible to both fabric interconnects or to only one fabric interconnect. Important You cannot create VLANs with IDs from 3968 to 4047. This range of VLAN IDs is reserved. VLANs in the LAN cloud and FCoE VLANs in the SAN cloud must have different IDs. Using the same ID for a VLAN and an FCoE VLAN in a VSAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. Before You Begin Create the primary VLAN. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 On the LAN tab, click the LAN node. In the Work pane, click the VLANs tab. Step 4 On the icon bar to the right of the table, click +. If the + icon is disabled, click an entry in the table to enable it. Step 5 In the Create VLANs dialog box, complete the following fields: Cisco UCS Manager GUI Configuration Guide, Release 2.0 288 OL-25712-04 Configuring Private VLANs Name Description VLAN Name/Prefix field For a single VLAN, this is the VLAN name. For a range of VLANs, this is the prefix that the system uses for each VLAN name. The VLAN name is case sensitive. This name can be between 1 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Configuration options You can choose one of the following: • Common/Global—The VLANs apply to both fabrics and use the same configuration parameters in both cases • Fabric A—The VLANs only apply to fabric A. • Fabric B—The VLAN only apply to fabric B. • Both Fabrics Configured Differently—The VLANs apply to both fabrics but you can specify different VLAN IDs for each fabric. For upstream disjoint L2 networks, we recommend that you choose Common/Global to create VLANs that apply to both fabrics. VLAN IDs field To create one VLAN, enter a single numeric ID. To create multiple VLANs, enter individual IDs or ranges of IDs separated by commas. A VLAN ID can: • Be between 1 and 3967 • Be between 4048 and 4093 • Overlap with other VLAN IDs already defined on the system For example, to create six VLANs with the IDs 4, 22, 40, 41, 42, and 43, you would enter 4, 22, 40-43. Important You cannot create VLANs with IDs from 3968 to 4047. This range of VLAN IDs is reserved. VLANs in the LAN cloud and FCoE VLANs in the SAN cloud must have different IDs. Using the same ID for a VLAN and an FCoE VLAN in a VSAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 289 Configuring Private VLANs Name Description Sharing Type field Whether this VLAN is subdivided into private or secondary VLANs. This can be one of the following: • None—This VLAN does not have any secondary or private VLANs. • Primary—This VLAN can have one or more secondary VLANs, as shown in the Secondary VLANs area. • Isolated—This is a private VLAN. The primary VLAN with which it is associated is shown in the Primary VLAN drop-down list. Step 6 Primary VLAN drop-down list If the Sharing Type field is set to Isolated, this is the primary VLAN associated with this private VLAN. Check Overlap button Click this button to determine whether the VLAN ID overlaps with any other IDs on the system. If you clicked the Check Overlap button, do the following: a) Click the Overlapping VLANs tab and review the following fields to verify that the VLAN ID does not overlap with any IDs assigned to existing VLANs. Name Description Fabric ID column This can be one of the following: •A •B • Dual—The component is accessible to either fabric interconnect. This setting applies to virtual LAN and SAN networks created at the system level as opposed to the fabric interconnect level. Name column The name of the VLAN. VLAN column The numeric id for the VLAN. DN column The full path to the VLAN. Click the link in this column to view the properties for the VLAN. b) Click the Overlapping VSANs tab and review the following fields to verify that the VLAN ID does not overlap with any FCoE VLAN IDs assigned to existing VSANs: Cisco UCS Manager GUI Configuration Guide, Release 2.0 290 OL-25712-04 Viewing the VLAN Port Count Name Description Fabric ID column This can be one of the following: •A •B • Dual—The component is accessible to either fabric interconnect. This setting applies to virtual LAN and SAN networks created at the system level as opposed to the fabric interconnect level. Name column The name of the VSAN. ID column The numeric id for the VSAN. FCoE VLAN ID column The unique identifier assigned to the VLAN used for Fibre Channel connections. DN column The full path to the VSAN. Click the link in this column to view the properties for the VSAN. c) Click OK. d) If Cisco UCS Manager identified any overlapping VLAN IDs or FCoE VLAN IDs, change the VLAN ID to one that does not overlap with an existing VLAN. Step 7 Click OK. Cisco UCS Manager adds the primary VLAN to one of the following VLANs nodes: • The LAN Cloud > VLANs node for a primary VLAN accessible to both fabric interconnects. • The Fabric_Interconnect_Name > VLANs node for a primary VLAN accessible to only one fabric interconnect. Viewing the VLAN Port Count Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Fabric Interconnects. Click the fabric interconnect for which you want to view the VLAN port count. In the Work pane, click the General tab. Step 5 In the General tab, click the down arrows on the VLAN Port Count bar to expand that area. Cisco UCS Manager GUI displays the following details: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 291 Viewing the VLAN Port Count Name Description VLAN Port Limit field The maximum number of VLAN ports allowed on this fabric interconnect. Access VLAN Port Count field The number of available VLAN access ports. Border VLAN Port Count field The number of available VLAN border ports. Allocation Status field The VLAN port allocation status. Cisco UCS Manager GUI Configuration Guide, Release 2.0 292 OL-25712-04 CHAPTER 18 Configuring LAN Pin Groups This chapter includes the following sections: • LAN Pin Groups, page 293 • Creating a LAN Pin Group, page 293 • Deleting a LAN Pin Group, page 294 LAN Pin Groups Cisco UCS uses LAN pin groups to pin Ethernet traffic from a vNIC on a server to an uplink Ethernet port or port channel on the fabric interconnect. You can use this pinning to manage the distribution of traffic from the servers. To configure pinning for a server, you must include the LAN pin group in a vNIC policy. The vNIC policy is then included in the service profile assigned to that server. All traffic from the vNIC travels through the I/O module to the specified uplink Ethernet port. Note If you do not assign a pin group to a server interface through a vNIC policy, Cisco UCS Manager chooses an uplink Ethernet port or port channel for traffic from that server interface dynamically. This choice is not permanent. A different uplink Ethernet port or port channel may be used for traffic from that server interface after an interface flap or a server reboot. Creating a LAN Pin Group In a system with two fabric interconnects, you can associate the pin group with only one fabric interconnect or with both fabric interconnects. Before You Begin Configure the ports and port channels with which you want to configure the pin group. You can only include ports and port channels configured as uplink ports in a LAN pin group. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 293 Deleting a LAN Pin Group Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 On the LAN tab, expand LAN > LAN Cloud. Right-click LAN Pin Groups and select Create LAN Pin Group. In the Create LAN Pin Group dialog box, enter a unique name and description for the pin group. Step 5 To pin traffic for fabric interconnect A, do the following in the Targets area: a) Check the Fabric Interconnect A check box. b) Click the drop-down arrow on the Interface field and navigate through the tree-style browser to select the port or port channel you want to associate with the pin group. Step 6 To pin traffic for fabric interconnect B, do the following in the Targets area: a) Check the Fabric Interconnect B check box. b) Click the drop-down arrow on the Interface field and navigate through the tree-style browser to select the port or port channel you want to associate with the pin group. Step 7 Click OK. What to Do Next Include the pin group in a vNIC template. Deleting a LAN Pin Group Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 In the LAN tab, expand LAN > LAN Cloud > LAN Pin Groups. Right-click the LAN pin group you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 294 OL-25712-04 CHAPTER 19 Configuring MAC Pools This chapter includes the following sections: • MAC Pools, page 295 • Creating a MAC Pool, page 295 • Deleting a MAC Pool, page 296 MAC Pools A MAC pool is a collection of network identities, or MAC addresses, that are unique in their layer 2 environment and are available to be assigned to vNICs on a server. If you use MAC pools in service profiles, you do not have to manually configure the MAC addresses to be used by the server associated with the service profile. In a system that implements multi-tenancy, you can use the organizational hierarchy to ensure that MAC pools can only be used by specific applications or business services. Cisco UCS Manager uses the name resolution policy to assign MAC addresses from the pool. To assign a MAC address to a server, you must include the MAC pool in a vNIC policy. The vNIC policy is then included in the service profile assigned to that server. You can specify your own MAC addresses or use a group of MAC addresses provided by Cisco. Creating a MAC Pool Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 In the LAN tab, expand LAN > Pools Expand the node for the organization where you want to create the pool. If the system does not include multitenancy, expand the root node. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 295 Deleting a MAC Pool Step 4 Step 5 Right-click MAC Pools and select Create MAC Pool. In the first page of the Create MAC Pool wizard: a) Enter a unique name and description for the MAC Pool. b) Click Next. Step 6 In the second page of the Create MAC Pool wizard: a) Click Add. b) In the Create a Block of MAC Addresses page, enter the first MAC address in the pool and the number of MAC addresses to include in the pool. c) Click OK. d) Click Finish. What to Do Next Include the MAC pool in a vNIC template. Deleting a MAC Pool If you delete a pool, Cisco UCS Manager does not reallocate any addresses from that pool that have been assigned to vNICs or vHBAs. All assigned addresses from a deleted pool remain with the vNIC or vHBA to which they are assigned until one of the following occurs: • The associated service profiles are deleted. • The vNIC or vHBA to which the address is assigned is deleted. • The vNIC or vHBA is assigned to a different pool. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 Step 5 In the LAN tab, expand LAN > Pools > Organization_Name . Expand the MAC Pools node. Right-click the MAC pool you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 296 OL-25712-04 CHAPTER 20 Configuring Quality of Service This chapter includes the following sections: • Quality of Service, page 297 • Configuring System Classes, page 297 • Configuring Quality of Service Policies, page 301 • Configuring Flow Control Policies, page 304 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 Configuring System Classes 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 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. This 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: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 297 Configuring System Classes Table 10: System Classes System Class Description Platinum 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. Gold Silver All properties of these system classes are available for you to assign custom settings and policies. Bronze Best Effort 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. Fibre Channel 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. Configuring QoS System Classes The type of adapter in a server may limit the maximum MTU supported. For example, network MTU above the maximums may cause the packet to be dropped for the following adapters: • The Cisco UCS M71KR CNA adapter, which supports a maximum MTU of 9216. • The Cisco UCS 82598KR-CI adapter, which supports a maximum MTU of 14000. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 In the LAN tab, expand LAN > LAN Cloud. Select the QoS System Class node. In the Work pane, click the General tab. Step 5 Update the following properties for the system class you want to configure to meet the traffic management needs of the system: Note Some properties may not be configurable for all system classes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 298 OL-25712-04 Configuring System Classes Name Description Enabled check box If checked, the associated QoS class is configured on the fabric interconnect and can be assigned to a QoS policy. If unchecked, the class is not configured on the fabric interconnect and any QoS policies associated with this class default to Best Effort or, if a system class is configured with a Cos of 0, to the Cos 0 system class. Note CoS field The class of service. You can enter an integer value between 0 and 6, with 0 being the lowest priority and 6 being the highest priority. We recommend that you do not set the value to 0, unless you want that system class to be the default system class for traffic if the QoS policy is deleted or the assigned system class is disabled. Note Packet Drop check box This field is always checked for Best Effort and Fibre Channel. This field is set to 7 for internal traffic and to any for Best Effort. Both of these values are reserved and cannot be assigned to any other priority. If checked, packet drop is allowed for this class. If unchecked, packets cannot be dropped during transmission. This field is always unchecked for the Fibre Channel class, which never allows dropped packets, and always checked for Best Effort, which always allows dropped packets. Weight drop-down list This can be one of the following: • An integer between 1 and 10. If you enter an integer, Cisco UCS determines the percentage of network bandwidth assigned to the priority level as described in the Weight (%) field. • best-effort. • none. Weight (%) field To determine the bandwidth allocated to a channel, Cisco UCS: 1 Adds the weights for all the channels 2 Divides the channel weight by the sum of all weights to get a percentage 3 Allocates that percentage of the bandwidth to the channel Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 299 Configuring System Classes Name Description MTU drop-down list The maximum transmission unit for the channel. This can be one of the following: • An integer between 1500 and 9216. This value corresponds to the maximum packet size. • fc—A predefined packet size of 2240. • normal—A predefined packet size of 1500. Note Multicast Optimized check box If checked, the class is optimized to send packets to multiple destinations simultaneously. Note Step 6 This field is always set to fc for Fibre Channel. This option is not applicable to the Fibre Channel. Click Save Changes. Enabling a QoS System Class The Best Effort or Fibre Channel system classes are enabled by default. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 In the LAN tab, expand LAN > LAN Cloud. Select the QoS System Class node. In the Work pane, click the General tab. Step 5 Step 6 Check the Enabled check box for the QoS system that you want to enable. Click Save Changes. Disabling a QoS System Class You cannot disable the Best Effort or Fibre Channel system classes. All QoS policies that are associated with a disabled system class default to Best Effort or, if the disabled system class is configured with a Cos of 0, to the Cos 0 system class. Cisco UCS Manager GUI Configuration Guide, Release 2.0 300 OL-25712-04 Configuring Quality of Service Policies Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 In the LAN tab, expand LAN > LAN Cloud. Select the QoS System Class node. In the Work pane, click the General tab. Step 5 Step 6 Uncheck the Enabled check box for the QoS system that you want to disable. Click Save Changes. Configuring Quality of Service Policies 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. Creating a QoS Policy Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 In the LAN tab, expand LAN > Policies. Expand the node for the organization where you want to create the pool. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click QoS Policy and select Create QoS Policy. In the Create QoS Policy dialog box, complete the following fields: Name Description Name field The name of the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 301 Configuring Quality of Service Policies Name Description Priority drop-down list The priority assigned to this QoS definition. This can be one of the following: • 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. ` Burst field The normal burst size for servers which use this policy. This field determines how large traffic bursts can be before some traffic is considered to exceed the rate limit. The default is 10240. The minimum value is 0, and the maximum value is 65535. This setting is not applicable to all adapters. Rate field The expected average rate of traffic. Traffic that falls under this rate will always conform. The default is line-rate, which equals a value of 0 and specifies no rate limiting. The minimum value is 8, and the maximum value is 40,000,000. The granularity for rate limiting on a Cisco UCS M81KR Virtual Interface Card adapter is 1Mbps. These adapters treat the requested rate as a "not-to-exceed" rate. Therefore, a value of 4.5Mbps is interpreted as 4Mbps. Any requested rate of more than 0 and less than 1Mbps is interpreted as 1Mbps, which is the lowest supported hardware rate limit. Rate limiting is not applicable to all adapters. For example, this setting is not supported on the Cisco UCS M82-8P Virtual Interface Card. Cisco UCS Manager GUI Configuration Guide, Release 2.0 302 OL-25712-04 Configuring Quality of Service Policies Name Description Host Control field Whether Cisco UCS controls the class of service (CoS). This can be one of the following: • None—Cisco UCS uses the CoS value associated with the priority selected in the Priority drop-down list regardless of the CoS value assigned by the host. • Full—If the packet has a valid CoS value assigned by the host, Cisco UCS uses that value. Otherwise, Cisco UCS uses the CoS value associated with the priority selected in the Priority drop-down list. This setting is not applicable to all adapters. Step 6 Click OK. What to Do Next Include the QoS policy in a vNIC or vHBA template. Deleting a QoS Policy If you delete a QoS policy that is in use or you disable a system class that is used in a QoS policy, any vNIC or vHBA that uses that QoS policy is assigned to the Best Effort system class or to the system class with a CoS of 0. In a system that implements multi-tenancy, Cisco UCS Manager first attempts to find a matching QoS policy in the organization hierarchy. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Servers > Policies > Organization_Name. Expand the QoS Policies node. Right-click the QoS policy you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 303 Configuring Flow Control Policies Configuring Flow Control Policies 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. Creating a Flow Control Policy Before You Begin Configure the network port with the corresponding setting for the flow control that you need. For example, if you enable the send setting for flow-control pause frames in the policy, make sure that the receive parameter in the network port is set to on or desired. If you want the Cisco UCS port to receive flow-control frames, make sure that the network port has a send parameter set to on or desired. If you do not want to use flow control, you can set the send and receive parameters on the network port to off. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 On the LAN tab, expand LAN > Policies. Expand the root node. You can only create a flow control policy in the root organization. You cannot create a flow control policy in a sub-organization. Step 4 Step 5 Right-click the Flow Control Policies node and select Create Flow Control Policy. In the Create Flow Control Policy wizard, complete the following fields: Name Description Name field The name of the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Cisco UCS Manager GUI Configuration Guide, Release 2.0 304 OL-25712-04 Configuring Flow Control Policies Name Description Priority field This can be one of the following: • Auto—Cisco UCS and the network negotiate whether PPP is used on this fabric interconnect • On—PPP is enabled on this fabric interconnect Receive field This can be one of the following: • Off—Pause requests from the network are ignored and traffic flow continues as normal • On—Pause requests are honored and all traffic is halted on that uplink port until the network cancels the pause request Send field This can be one of the following: • Off—Traffic on the port flows normally regardless of the packet load. • On—Cisco UCS sends a pause request to the network if the incoming packet rate becomes too high. The pause remains in effect for a few milliseconds before traffic is reset to normal levels. Step 6 Click OK. What to Do Next Associate the flow control policy with an uplink Ethernet port or port channel. Deleting a Flow Control Policy Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 On the LAN tab, expand LAN > Policies > Organization_Name. Expand the Flow Control Policies node. Right-click the policy you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Step 3 Step 4 Step 5 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 305 Configuring Flow Control Policies Cisco UCS Manager GUI Configuration Guide, Release 2.0 306 OL-25712-04 CHAPTER 21 Configuring Network-Related Policies This chapter includes the following sections: • Configuring vNIC Templates, page 307 • Configuring Ethernet Adapter Policies, page 312 • Configuring Network Control Policies, page 317 Configuring vNIC Templates vNIC Template This policy defines how a vNIC on a server connects to the LAN. This policy is also referred to as a vNIC LAN connectivity policy. Beginning in Cisco UCS, Release 2.0(2), Cisco UCS Manager does not automatically create a VM-FEX port profile with the correct settings when you create a vNIC template. If you want to create a VM-FEX port profile, you must configure the target of the vNIC template as a VM. You need to include this policy in a service profile for it to take effect. Note If your server has two Emulex or QLogic NICs (Cisco UCS CNA M71KR-E or Cisco UCS CNA M71KR-Q), you must configure vNIC policies for both adapters in your service profile to get a user-defined MAC address for both NICs. If you do not configure policies for both NICs, Windows still detects both of them in the PCI bus. Then because the second eth is not part of your service profile, Windows assigns it a hardware MAC address. If you then move the service profile to a different server, Windows sees additional NICs because one NIC did not have a user-defined MAC address. Creating a vNIC Template Before You Begin This policy requires that one or more of the following resources already exist in the system: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 307 Configuring vNIC Templates • Named VLAN • MAC pool • QoS policy • LAN pin group • Statistics threshold policy Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 On the LAN tab, expand LAN > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click the vNIC Templates node and choose Create vNIC Template. In the Create vNIC Template dialog box: a) In the General area, complete the following fields: Name Description Name field The name of the vNIC template. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A user-defined description of the template. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Cisco UCS Manager GUI Configuration Guide, Release 2.0 308 OL-25712-04 Configuring vNIC Templates Name Description Fabric ID field The fabric interconnect associated with the component. If you want vNICs created from this template to be able to access the second fabric interconnect if the default one is unavailable, check the Enable Failover check box. Note Do not enable vNIC fabric failover under the following circumstances: • If the Cisco UCS domain is running in Ethernet Switch Mode. vNIC fabric failover is not supported in that mode. If all Ethernet uplinks on one fabric interconnect fail, the vNICs do not fail over to the other. • if you plan to associate one or more vNICs created from this template with a server that has an adapter which does not support fabric failover, such as the Cisco UCS 82598KR-CI 10-Gigabit Ethernet Adapter. If you do so, Cisco UCS Manager generates a configuration fault when you associate the service profile with the server. • If the Cisco UCS domain is running in Ethernet Switch Mode. vNIC fabric failover is not supported in that mode. If all Ethernet uplinks on one fabric interconnect fail, the vNICs do not fail over to the other. • if you plan to associate this vNIC configuration with a server that has an adapter which does not support fabric failover, such as the Cisco UCS 82598KR-CI 10-Gigabit Ethernet Adapter. If you do so, Cisco UCS Manager generates a configuration fault when you associate the service profile with the server. Target list box A list of the possible targets for vNICs created from this template. The target you choose determines whether or not Cisco UCS Manager automatically creates a VM-FEX port profile with the appropriate settings for the vNIC template. This can be one of the following: • Adapter—The vNICs apply to all adapters. No VM-FEX port profile is created if you choose this option. • VM—The vNICs apply to all virtual machines. A VM-FEX port profile is created if you choose this option. Template Type field This can be one of the following: • Initial Template—vNICs created from this template are not updated if the template changes. • Updating Template—vNICs created from this template are updated if the template changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 309 Configuring vNIC Templates b) In the VLANs area, use the table to select the VLAN to assign to vNICs created from this template. The table contains the following columns: Name Description Select column Check the check box in this column for each VLAN that you want to use. Name column The name of the VLAN. Native VLAN column To designate one of the VLANs as the native VLAN, click the radio button in this column. Create VLAN link Click this link if you want to create a VLAN. c) In the Policies area, complete the following fields: Name Description MTU field The maximum transmission unit, or packet size, that vNICs created from this vNIC template should use. Enter an integer between 1500 and 9216. Note Step 6 If the vNIC template has an associated QoS policy, the MTU specified here must be equal to or less than the MTU specified in the associated QoS system class. If this MTU value exceeds the MTU value in the QoS system class, packets may be dropped during data transmission. MAC Pool drop-down list The MAC address pool that vNICs created from this vNIC template should use. QoS Policy drop-down list The quality of service policy that vNICs created from this vNIC template should use. Network Control Policy drop-down list The network control policy that vNICs created from this vNIC template should use. Pin Group drop-down list The LAN pin group that vNICs created from this vNIC template should use. Stats Threshold Policy drop-down list The statistics collection policy that vNICs created from this vNIC template should use. Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 310 OL-25712-04 Configuring vNIC Templates What to Do Next Include the vNIC template in a service profile. Deleting a vNIC Template Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 On the LAN tab, expand LAN > Policies > Organization_Name. Expand the vNIC Templates node. Right-click the policy you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Step 3 Step 4 Step 5 Binding a vNIC to a vNIC Template You can bind a vNIC associated with a service profile to a vNIC template. When you bind the vNIC to a vNIC template, Cisco UCS Manager configures the vNIC with the values defined in the vNIC template. If the existing vNIC configuration does not match the vNIC template, Cisco UCS Manager reconfigures the vNIC. You can only change the configuration of a bound vNIC through the associated vNIC template. You cannot bind a vNIC to a vNIC template if the service profile that includes the vNIC is already bound to a service profile template. Important If the vNIC is reconfigured when you bind it to a template, Cisco UCS Manager reboots the server associated with the service profile. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that includes the service profile with the vNIC you want to bind. If the system does not include multi-tenancy, expand the root node. Step 4 Step 5 Step 6 Expand Service_Profile_Name > vNICs. Click the vNIC you want to bind to a template. In the Work pane, click the General tab. Step 7 Step 8 In the Actions area, click Bind to a Template. In the Bind to a vNIC Template dialog box, do the following: a) From the vNIC Template drop-down list, choose the template to which you want to bind the vNIC. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 311 Configuring Ethernet Adapter Policies b) Click OK. Step 9 In the warning dialog box, click Yes to acknowledge that Cisco UCS Manager may need to reboot the server if the binding causes the vNIC to be reconfigured. Unbinding a vNIC from a vNIC Template Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Step 4 Step 5 Step 6 Expand Service_Profile_Name > vNICs. Click the vNIC you want to unbind from a template. In the Work pane, click the General tab. Step 7 Step 8 In the Actions area, click Unbind from a Template. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Expand the node for the organization that includes the service profile with the vNIC you want to unbind. If the system does not include multi-tenancy, expand the root node. Configuring Ethernet Adapter Policies Ethernet and Fibre Channel Adapter Policies These policies govern the host-side behavior of the adapter, including how the adapter handles traffic. For example, you can use these policies to change default settings for the following: • Queues • Interrupt handling • Performance enhancement • RSS hash • Failover in an cluster configuration with two fabric interconnects Cisco UCS Manager GUI Configuration Guide, Release 2.0 312 OL-25712-04 Configuring Ethernet Adapter Policies Note For Fibre Channel adapter policies, the values displayed by Cisco UCS Manager may not match those displayed by applications such as QLogic SANsurfer. For example, the following values may result in an apparent mismatch between SANsurfer and Cisco UCS Manager: • Max LUNs Per Target—SANsurfer has a maximum of 256 LUNs and does not display more than that number. Cisco UCS Manager supports a higher maximum number of LUNs. • Link Down Timeout—In SANsurfer, you configure the timeout threshold for link down in seconds. In Cisco UCS Manager, you configure this value in milliseconds. Therefore, a value of 5500 ms in Cisco UCS Manager displays as 5s in SANsurfer. • Max Data Field Size—SANsurfer has allowed values of 512, 1024, and 2048. Cisco UCS Manager allows you to set values of any size. Therefore, a value of 900 in Cisco UCS Manager displays as 512 in SANsurfer. Operating System Specific Adapter Policies By default, Cisco UCS provides a set of Ethernet adapter policies and Fibre Channel adapter policies. These policies include the recommended settings for each supported server operating system. Operating systems are sensitive to the settings in these policies. Storage vendors typically require non-default adapter settings. You can find the details of these required settings on the support list provided by those vendors. Important We recommend that you use the values in these policies for the applicable operating system. Do not modify any of the values in the default policies unless directed to do so by Cisco Technical Support. However, if you are creating an Ethernet adapter policy for a Windows OS (instead of using the default Windows adapter policy), you must use the following formulas to calculate values that work with Windows: Completion Queues = Transmit Queues + Receive Queues Interrupt Count = (Completion Queues + 2) rounded up to nearest power of 2 For example, if Transmit Queues = 1 and Receive Queues = 8 then: Completion Queues = 1 + 8 = 9 Interrupt Count = (9 + 2) rounded up to the nearest power of 2 = 16 Creating an Ethernet Adapter Policy Tip If the fields in an area are not displayed, click the Expand icon to the right of the heading. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 313 Configuring Ethernet Adapter Policies Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click Adapter Policies and choose Create Ethernet Adapter Policy. Enter a name and description for the policy in the following fields: Name Description Name field The name of the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A description of the policy. We recommend that you include information about where and when the policy should be used. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Step 6 (Optional) In the Resources area, adjust the following values: Name Description Transmit Queues field The number of transmit queue resources to allocate. Enter an integer between 1 and 256. Ring Size field The number of descriptors in each transmit queue. Enter an integer between 64 and 4096. Receive Queues field The number of receive queue resources to allocate. Enter an integer between 1 and 256. Ring Size field The number of descriptors in each receive queue. Enter an integer between 64 and 4096. Completion Queues field The number of completion queue resources to allocate. In general, the number of completion queue resources you should allocate is equal to the number of transmit queue resources plus the number of receive queue resources. Enter an integer between 1 and 512. Cisco UCS Manager GUI Configuration Guide, Release 2.0 314 OL-25712-04 Configuring Ethernet Adapter Policies Name Description Interrupts field The number of interrupt resources to allocate. In general, this value should be equal to the number of completion queue resources. Enter an integer between 1 and 514. Step 7 (Optional) In the Options area, adjust the following values: Name Description Transmit Checksum Offload field This can be one of the following: • Disabled—The CPU calculates all packet checksums. • Enabled—The CPU sends all packets to the hardware so that the checksum can be calculated. This option may reduce CPU overhead. Note This option affects only packets sent from the interface. Receive Checksum Offload field This can be one of the following: • Disabled—The CPU validates all packet checksums. • Enabled—The CPU sends all packet checksums to the hardware for validation. This option may reduce CPU overhead. Note This option affects only packets received by the interface. TCP Segmentation Offload field This can be one of the following: • Disabled—The CPU segments large TCP packets. • Enabled—The CPU sends large TCP packets to the hardware to be segmented. This option may reduce CPU overhead and increase throughput rate. Note This option is also known as Large Send Offload (LSO) and affects only packets sent from the interface. TCP Large Receive Offload field This can be one of the following: • Disabled—The CPU processes all large packets. • Enabled—The hardware reassembles all segmented packets before sending them to the CPU. This option may reduce CPU utilization and increase inbound throughput. Note This option affects only packets received by the interface. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 315 Configuring Ethernet Adapter Policies Name Description Receive Side Scaling field RSS distributes network receive processing across multiple CPUs in multiprocessor systems. This can be one of the following: • Disabled—Network receive processing is always handled by a single processor even if additional processors are available. • Enabled—Network receive processing is shared across processors whenever possible. Failback Timeout field After a vNIC has started using its secondary interface, this setting controls how long the primary interface must be available before the system resumes using the primary interface for the vNIC. Enter a number of seconds between 0 and 600. Interrupt Mode field The preferred driver interrupt mode. This can be one of the following: • MSI X—Message Signaled Interrupts (MSI) with the optional extension. This is the recommended option. • MSI—MSI only. • INTx—PCI INTx interrupts. Interrupt Coalescing Type field This can be one of the following: • Min—The system waits for the time specified in the Interrupt Timer field before sending another interrupt event. • Idle—The system does not send an interrupt until there is a period of no activity lasting as least as long as the time specified in the Interrupt Timer field. Interrupt Timer field The time to wait between interrupts or the idle period that must be encountered before an interrupt is sent. Enter a value between 1 and 65535. To turn off interrupt coalescing, enter 0 (zero) in this field. Step 8 Step 9 Click OK. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 316 OL-25712-04 Configuring Network Control Policies Deleting an Ethernet Adapter Policy Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 On the LAN tab, expand LAN > Policies > Organization_Name. Expand the Adapter Policies node. Right-click the Ethernet adapter policy that you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Step 3 Step 4 Step 5 Configuring Network Control Policies Network Control Policy This policy configures the network control settings for the Cisco UCS domain, including the following: • Whether the Cisco Discovery Protocol (CDP) is enabled or disabled • How the VIF behaves if no uplink port is available in end-host mode • The action that Cisco UCS Manager takes on the remote Ethernet interface, vEthernet interface , or vFibreChannel interface when the associated border port fails • Whether the server can use different MAC addresses when sending packets to the fabric interconnect • Whether MAC registration occurs on a per-VNIC basis or for all VLANs. Action on Uplink Fail By default, the Action on Uplink Fail property in the network control policy is configured with a value of link-down. For adapters such as the Cisco UCS M81KR Virtual Interface Card, this default behavior directs Cisco UCS Manager to bring the vEthernet or vFibreChannel interface down if the associated border port fails. For Cisco UCS systems using a non-VM-FEX capable converged network adapter that supports both Ethernet and FCoE traffic, such as Cisco UCS CNA M72KR-Q and the Cisco UCS CNA M72KR-E, this default behavior directs Cisco UCS Manager to bring the remote Ethernet interface down if the associated border port fails. In this scenario, any vFibreChannel interfaces that are bound to the remote Ethernet interface are brought down as well. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 317 Configuring Network Control Policies Note Cisco UCS Manager, release 1.4(2) and earlier did not enforce the Action on Uplink Fail property for those types of non-VM-FEX capable converged network adapters mentioned above. If the Action on Uplink Fail property was set to link-down, Cisco UCS Manager would ignore this setting and instead issue a warning. In the current version of Cisco UCS Manager this setting is enforced. Therefore, if your implementation includes one of those converged network adapters and the adapter is expected to handle both Ethernet and FCoE traffic, we recommend that you configure the Action on Uplink Fail property with a value of warning. Please note that this configuration may result in an Ethernet teaming driver not being able to detect a link failure when the border port goes down. MAC Registration Mode In Cisco UCS Manager, releases 1.4 and earlier, MAC addresses were installed on all of the VLANs belonging to an interface. Starting in release 2.0, MAC addresses are installed only on the native VLAN by default. In most implementations this maximizes the VLAN port count. Note If a trunking driver is being run on the host and the interface is in promiscuous mode, we recommend that you set the Mac Registration Mode to All VLANs. Creating a Network Control Policy MAC address-based port security for Emulex converged Network Adapters (N20-AE0102) is not supported. When MAC address-based port security is enabled, the fabric interconnect restricts traffic to packets that contain the MAC address that it first learns. This is either the source MAC address used in the FCoE Initialization Protocol packet, or the MAC address in an ethernet packet, whichever is sent first by the adaptor. This configuration can result in either FCoE or Ethernet packets being dropped. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 On the LAN tab, expand LAN > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click the Network Control Policies node and select Create Network Control Policy. In the Create Network Control Policy dialog box, complete the following fields: Name Description Name field The name of the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Cisco UCS Manager GUI Configuration Guide, Release 2.0 318 OL-25712-04 Configuring Network Control Policies Name Description CDP field This option determines whether Cisco Discovery Protocol (CDP) is enabled on servers associated with a service profile that includes this policy. This can be one of the following: • Disabled • Enabled MAC Register Mode field Whether adapter-registered MAC addresses are added only to the native VLAN associated with the interface or added to all VLANs associated with the interface. This can be one of the following: • Only Native Vlan—MAC addresses are only added to the native VLAN. This option is the default, and it maximizes the port+VLAN count. • All Host Vlans—MAC addresses are added to all VLANs with which they are associated. Select this option if your VLANs are configured to use trunking but are not running in Promiscuous mode. Action on Uplink Fail field This option determines how the VIF behaves if no uplink port is available when the fabric interconnect is in end-host mode. This can be one of the following: • Link Down— Changes the operational state of a vNIC to down when uplink connectivity is lost on the fabric interconnect, and enables fabric failover for vNICs. • Warning— Maintains server-to-server connectivity even when no uplink port is available, and disables fabric failover when uplink connectivity is lost on the fabric interconnect. The default is Link Down. Note Cisco UCS Manager, release 1.4(2) and earlier did not enforce the Action on Uplink Fail property for those types of non-VM-FEX capable converged network adapters mentioned above. If the Action on Uplink Fail property was set to link-down, Cisco UCS Manager would ignore this setting and instead issue a warning. In the current version of Cisco UCS Manager this setting is enforced. Therefore, if your implementation includes one of those converged network adapters and the adapter is expected to handle both Ethernet and FCoE traffic, we recommend that you configure the Action on Uplink Fail property with a value of warning. Please note that this configuration may result in an Ethernet teaming driver not being able to detect a link failure when the border port goes down. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 319 Configuring Network Control Policies Step 6 In the MAC Security area, do the following to determine whether the server can use different MAC addresses when sending packets to the fabric interconnect: a) Click the Expand icon to expand the area and display the radio buttons. b) Click one of the following radio buttons to determine whether forged MAC addresses are allowed or denied when packets are sent from the server to the fabric interconnect: • Allow— All server packets are accepted by the fabric interconnect, regardless of the MAC address associated with the packets. • Deny— After the first packet has been sent to the fabric interconnect, all other packets must use the same MAC address or they will be silently rejected by the fabric interconnect. In effect, this option enables port security for the associated vNIC. If you plan to install VMware ESX on the associated server, you must configure the MAC Security to allow for the network control policy applied to the default vNIC. If you do not configure MAC Security for allow, the ESX installation may fail because the MAC security permits only one MAC address while the installation process requires more than one MAC address. Step 7 Click OK. Deleting a Network Control Policy Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 On the LAN tab, expand LAN > Policies > Organization_Name. Expand the Network Control Policies node. Right-click the policy you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Step 3 Step 4 Step 5 Cisco UCS Manager GUI Configuration Guide, Release 2.0 320 OL-25712-04 CHAPTER 22 Configuring Upstream Disjoint Layer-2 Networks This chapter includes the following sections: • Upstream Disjoint Layer-2 Networks, page 321 • Guidelines for Configuring Upstream Disjoint L2 Networks, page 322 • Pinning Considerations for Upstream Disjoint L2 Networks, page 323 • Configuring Cisco UCS for Upstream Disjoint L2 Networks, page 324 • Creating a VLAN for an Upstream Disjoint L2 Network, page 325 • Assigning Ports and Port Channels to VLANs, page 327 • Removing Ports and Port Channels from VLANs, page 328 • Viewing Ports and Port Channels Assigned to VLANs, page 329 Upstream Disjoint Layer-2 Networks Upstream disjoint layer-2 networks (disjoint L2 networks) are required if you have two or more Ethernet “clouds” that never connect, but must be accessed by servers or virtual machines located in the same Cisco UCS domain. For example, you could configure disjoint L2 networks if you require one of the following: • Servers or virtual machines to access a public network and a backup network • In a multi-tenant system, servers or virtual machines for more than one customer are located in the same Cisco UCS domain and need to access the L2 networks for both customers. Note By default, data traffic in Cisco UCS works on a principle of mutual inclusion. All traffic for all VLANs and upstream networks travels along all uplink ports and port channels. If you have upgraded from a release that does not support upstream disjoint layer-2 networks, you must assign the appropriate uplink interfaces to your VLANs, or traffic for those VLANs continues to flow along all uplink ports and port channels. The configuration for disjoint L2 networks works on a principle of selective exclusion. Traffic for a VLAN that is designated as part of a disjoint network can only travel along an uplink Ethernet port or port channel Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 321 Guidelines for Configuring Upstream Disjoint L2 Networks that is specifically assigned to that VLAN, and is selectively excluded from all other uplink ports and port channels. However, traffic for VLANs that are not specifically assigned to an uplink Ethernet port or port channel can still travel on all uplink ports or port channels, including those that carry traffic for the disjoint L2 networks. In Cisco UCS, the VLAN represents the upstream disjoint L2 network. When you design your network topology for disjoint L2 networks, you must assign uplink interfaces to VLANs not the reverse. For information about the maximum number of supported upstream disjoint L2 networks, see Cisco UCS 6100 and 6200 Series Configuration Limits for Cisco UCS Manager, Release 2.0. Guidelines for Configuring Upstream Disjoint L2 Networks When you plan your configuration for upstream disjoint L2 networks, consider the following: Ethernet Switching Mode Must Be End-Host Mode Cisco UCS only supports disjoint L2 networks when the Ethernet switching mode of the fabric interconnects is configured for end-host mode. You cannot connect to disjoint L2 networks if the Ethernet switching mode of the fabric interconnects is switch mode. Symmetrical Configuration Is Recommended for High Availability If a Cisco UCS domain is configured for high availability with two fabric interconnects, we recommend that both fabric interconnects are configured with the same set of VLANs. VLAN Validity Criteria Are the Same for Uplink Ethernet Ports and Port Channels The VLAN used for the disjoint L2 networks must be configured and assigned to an uplink Ethernet port or uplink Ethernet port channel. If the port or port channel does not include the VLAN, Cisco UCS Manager considers the VLAN invalid and does the following: • Displays a configuration warning in the Status Details area for the server. • Ignores the configuration for the port or port channel and drops all traffic for that VLAN. Note The validity criteria are the same for uplink Ethernet ports and uplink Ethernet port channels. Cisco UCS Manager does not differentiate between the two. Overlapping VLANs Are Not Supported Cisco UCS does not support overlapping VLANs in disjoint L2 networks. You must ensure that each VLAN only connects to one upstream disjoint L2 domain. Each vNIC Can Only Communicate with One Disjoint L2 Network A vNIC can only communicate with one disjoint L2 network. If a server needs to communicate with multiple disjoint L2 networks, you must configure a vNIC for each of those networks. To communicate with more than two disjoint L2 networks, a server must have a Cisco VIC adapter that supports more than two vNICs. Cisco UCS Manager GUI Configuration Guide, Release 2.0 322 OL-25712-04 Pinning Considerations for Upstream Disjoint L2 Networks Appliance Port Must Be Configured with the Same VLAN as Uplink Ethernet Port or Port Channel For an appliance port to communicate with a disjoint L2 network, you must ensure that at least one uplink Ethernet port or port channel is in the same network and is therefore assigned to the same VLANs that are used by the appliance port. If Cisco UCS Manager cannot identify an uplink Ethernet port or port channel that includes all VLANs that carry traffic for an appliance port, the appliance port experiences a pinning failure and goes down. For example, a Cisco UCS domain includes a global VLAN named vlan500 with an ID of 500. vlan500 is created as a global VLAN on the uplink Ethernet port. However, Cisco UCS Manager does not propagate this VLAN to appliance ports. To configure an appliance port with vlan500, you must create another VLAN named vlan500 with an ID of 500 for the appliance port. You can create this duplicate VLAN in the Appliances node on the LAN tab of the Cisco UCS Manager GUI or the eth-storage scope in the Cisco UCS Manager CLI. If you are prompted to check for VLAN Overlap, accept the overlap and Cisco UCS Manager creates the duplicate VLAN for the appliance port. Default VLAN 1 Cannot Be Configured Explicitly on an Uplink Ethernet Port or Port Channel Cisco UCS Manager implicitly assigns default VLAN 1 to all uplink ports and port channels. Even if you do not configure any other VLANs, Cisco UCS uses default VLAN 1 to handle data traffic for all uplink ports and port channels. Note After you configure VLANs in a Cisco UCS domain, default VLAN 1 remains implicitly on all uplink ports and port channels. You cannot explicitly assign default VLAN 1 to an uplink port or port channel, nor can you remove it from an uplink port or port channel. If you attempt to assign default VLAN 1 to a specific port or port channel, Cisco UCS Manager raises an Update Failed fault. Therefore, if you configure a Cisco UCS domain for disjoint L2 networks, do not configure any vNICs with default VLAN 1 unless you want all data traffic for that server to be carried on all uplink Ethernet ports and port channels and sent to all upstream networks. Pinning Considerations for Upstream Disjoint L2 Networks Communication with an upstream disjoint L2 network requires that you ensure that the pinning is properly configured. Whether you implement soft pinning or hard pinning, a VLAN membership mismatch causes traffic for one or more VLANs to be dropped. Soft Pinning Soft pinning is the default behavior in Cisco UCS. If you plan to implement soft pinning, you do not need to create LAN pin groups to specify a pin target for a vNIC. Instead, Cisco UCS Manager pins the vNIC to an uplink Ethernet port or port channel according to VLAN membership criteria. With soft pinning, Cisco UCS Manager validates data traffic from a vNIC against the VLAN membership of all uplink Ethernet ports and port channels. If you have configured disjoint L2 networks, Cisco UCS Manager must be able to find an uplink Ethernet port or port channel that is assigned to all VLANS on the vNIC. If no uplink Ethernet port or port channel is configured with all VLANs on the vNIC, Cisco UCS Manager does the following: • Brings the link down. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 323 Configuring Cisco UCS for Upstream Disjoint L2 Networks • Drops the traffic for all of the VLANs on the vNIC. • Raises the following faults: ◦ Link Down ◦ VIF Down Cisco UCS Manager does not raise a fault or warning about the VLAN configuration. For example, a vNIC on a server is configured with VLANs 101, 102, and 103. Interface 1/3 is assigned only to VLAN 102. Interfaces 1/1 and 1/2 are not explicitly assigned to a VLAN, which makes them available for traffic on VLANs 101 and 103. As a result of this configuration, the Cisco UCS domain does not include a border port interface that can carry traffic for all three VLANS for which the vNIC is configured. As a result, Cisco UCS Manager brings down the vNIC, drops traffic for all three VLANs on the vNIC, and raises the Link Down and VIF Down faults. Hard Pinning Hard pinning occurs when you use LAN pin groups to specify the pinning target for the traffic intended for the disjoint L2 networks. In turn, the uplink Ethernet port or port channel that is the pinning target must be configured to communicate with the appropriate disjoint L2 network. With hard pinning, Cisco UCS Manager validates data traffic from a vNIC against the VLAN membership of all uplink Ethernet ports and port channels, and validates the LAN pin group configuration to ensure it includes the VLAN and the uplink Ethernet port or port channel. If the validation fails at any point, Cisco UCS Manager does the following: • Raises a Pinning VLAN Mismatch fault with a severity of Warning. • Drops traffic for the VLAN. • Does not bring the link down, so that traffic for other VLANs can continue to flow along it. For example, if you want to configure hard pinning for an upstream disjoint L2 network that uses VLAN 177, do the following: • Create a LAN pin group with the uplink Ethernet port or port channel that carries the traffic for the disjoint L2 network. • Configure at least one vNIC in the service profile with VLAN 177 and the LAN pin group. • Assign VLAN 177 to an uplink Ethernet port or port channel included in the LAN pin group If the configuration fails at any of these three points, then Cisco UCS Manager warns for a VLAN mismatch for VLAN 177 and drops the traffic for that VLAN only. Configuring Cisco UCS for Upstream Disjoint L2 Networks When you configure a Cisco UCS domain to connect with upstream disjoint L2 networks, you need to ensure that you complete all of the following steps. Before You Begin Before you begin this configuration, ensure that the ports on the fabric interconnects are properly cabled to support your disjoint L2 networks configuration. Cisco UCS Manager GUI Configuration Guide, Release 2.0 324 OL-25712-04 Creating a VLAN for an Upstream Disjoint L2 Network Procedure Command or Action Step 1 Purpose Configure Ethernet switching mode for both The Ethernet switching mode must be in End-Host fabric interconnects in Ethernet End-Host Mode for Cisco UCS to be able to communicate with Mode. upstream disjoint L2 networks. See Configuring Ethernet Switching Mode. Step 2 Configure the ports and port channels that See Configuring Ports and Port Channels, on page you require to carry traffic for the disjoint 77. L2 networks. Step 3 Configure the LAN pin groups required to (Optional) pin the traffic for the appropriate uplink See Configuring LAN Pin Groups, on page 293. Ethernet ports or port channels. Step 4 Create one or more VLANs. These can be named VLANs or private VLANs. For a cluster configuration, we recommend that you create the VLANs in the VLAN Manager and use the Common/Global configuration to ensure they are accessible to both fabric interconnects. See Creating a VLAN for an Upstream Disjoint L2 Network, on page 325. Step 5 Assign the desired ports or port channels When this step is completed, traffic for those VLANs to the VLANs for the disjoint L2 networks. can only be sent through the trunks for the assigned ports and/or port channels. Assigning Ports and Port Channels to VLANs, on page 327 Step 6 Ensure that the service profiles for all servers that need to communicate with the disjoint L2 networks include the correct LAN connectivity configuration to ensure the vNICs send the traffic to the appropriate VLAN. You can complete this configuration through one or more vNIC templates or when you configure the networking options for the service profile. See Configuring Service Profiles. Creating a VLAN for an Upstream Disjoint L2 Network For upstream disjoint L2 networks, we recommend that you create VLANs in the VLAN Manager. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 On the LAN tab, click the LAN node. In the Work pane, click the LAN Uplinks Manager link on the LAN Uplinks tab. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 325 Creating a VLAN for an Upstream Disjoint L2 Network The LAN Uplinks Manager opens in a separate window. Step 4 Step 5 In the LAN Uplinks Manager, click VLANs > VLAN Manager. On the icon bar to the right of the table, click +. If the + icon is disabled, click an entry in the table to enable it. Step 6 In the Create VLANs dialog box, complete the following fields and then click OK: Name Description VLAN Name/Prefix field For a single VLAN, this is the VLAN name. For a range of VLANs, this is the prefix that the system uses for each VLAN name. The VLAN name is case sensitive. This name can be between 1 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Configuration options You can choose one of the following: • Common/Global—The VLANs apply to both fabrics and use the same configuration parameters in both cases • Fabric A—The VLANs only apply to fabric A. • Fabric B—The VLAN only apply to fabric B. • Both Fabrics Configured Differently—The VLANs apply to both fabrics but you can specify different VLAN IDs for each fabric. For upstream disjoint L2 networks, we recommend that you choose Common/Global to create VLANs that apply to both fabrics. VLAN IDs field To create one VLAN, enter a single numeric ID. To create multiple VLANs, enter individual IDs or ranges of IDs separated by commas. A VLAN ID can: • Be between 1 and 3967 • Be between 4048 and 4093 • Overlap with other VLAN IDs already defined on the system For example, to create six VLANs with the IDs 4, 22, 40, 41, 42, and 43, you would enter 4, 22, 40-43. Important You cannot create VLANs with IDs from 3968 to 4047. This range of VLAN IDs is reserved. VLANs in the LAN cloud and FCoE VLANs in the SAN cloud must have different IDs. Using the same ID for a VLAN and an FCoE VLAN in a VSAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. Cisco UCS Manager GUI Configuration Guide, Release 2.0 326 OL-25712-04 Assigning Ports and Port Channels to VLANs Name Description Sharing Type field Whether this VLAN is subdivided into private or secondary VLANs. This can be one of the following: • None—This VLAN does not have any secondary or private VLANs. • Primary—This VLAN can have one or more secondary VLANs, as shown in the Secondary VLANs area. • Isolated—This is a private VLAN. The primary VLAN with which it is associated is shown in the Primary VLAN drop-down list. Step 7 Primary VLAN drop-down list If the Sharing Type field is set to Isolated, this is the primary VLAN associated with this private VLAN. Check Overlap button Click this button to determine whether the VLAN ID overlaps with any other IDs on the system. Repeat Steps 6 and 7 to create additional VLANs. What to Do Next Assign ports and port channels to the VLANs. Assigning Ports and Port Channels to VLANs Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 On the LAN tab, click the LAN node. In the Work pane, click the LAN Uplinks Manager link on the LAN Uplinks tab. The LAN Uplinks Manager opens in a separate window. Step 4 Step 5 In the LAN Uplinks Manager, click VLANs > VLAN Manager. Click one of the following subtabs to configure ports and port channels on that fabric interconnect: Subtab Description Fabric A Displays the ports, port channels, and VLANs that are accessible to fabric interconnect A. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 327 Removing Ports and Port Channels from VLANs Step 6 Subtab Description Fabric B Displays the ports, port channels, and VLANs that are accessible to fabric interconnect B. In the Ports and Port Channels table, do the following: • To assign an Uplink Ethernet port channel to a VLAN, expand the Port Channels node and click the port channel you want to assign to the VLAN. • To assign an Uplink Ethernet port to the VLAN, expand the Uplink Interfaces node and click the port you want to assign to the VLAN You can hold down the Ctrl key and click multiple ports or port channels to assign to them to the same VLAN or set of VLANs . Step 7 In the VLANs table, expand the appropriate node if necessary and click the VLAN to which you want to assign the port or port channel. You can hold down the Ctrl key and click multiple VLANs if you want to assign the same set of ports and/or port channels to them. Step 8 Click the Add to VLAN button. Step 9 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Step 10 To assign additional ports or port channels to VLANs on the same fabric, repeat Steps 6, 7, and 8. Step 11 To assign additional ports or port channels to VLANs on a different fabric, repeat Steps 5 through 8. If the Cisco UCS domain is configured for high availability with two fabric interconnects, we recommend that you create the same set of VLANs on both fabric interconnects. Step 12 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Step 13 Click Apply if you want to continue to work in the VLAN Manager, or click OK to close the window. After a port or port channel is assigned to one or more VLANs, it is removed from all other VLANs. Removing Ports and Port Channels from VLANs Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 On the LAN tab, click the LAN node. In the Work pane, click the LAN Uplinks Manager link on the LAN Uplinks tab. The LAN Uplinks Manager opens in a separate window. Step 4 Step 5 In the LAN Uplinks Manager, click VLANs > VLAN Manager. Click one of the following subtabs to configure ports and port channels on that fabric interconnect: Cisco UCS Manager GUI Configuration Guide, Release 2.0 328 OL-25712-04 Viewing Ports and Port Channels Assigned to VLANs Step 6 Step 7 Subtab Description Fabric A Displays the ports, port channels, and VLANs that are accessible to fabric interconnect A. Fabric B Displays the ports, port channels, and VLANs that are accessible to fabric interconnect B. In the VLANs table, expand the appropriate node and the VLAN from which you want to remove a port or port channel. Click the port or port channel that you want to remove from the VLAN. Hold down the Ctrl key to click multiple ports or port channels. Step 8 Click the Remove from VLAN button. Step 9 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Step 10 Click Apply if you want to continue to work in the VLAN Manager, or click OK to close the window. Important If you remove all port or port channel interfaces from a VLAN, the VLAN returns to the default behavior and data traffic on that VLAN flows on all uplink ports and port channels. Depending upon the configuration in the Cisco UCS domain, this default behavior can cause Cisco UCS Manager to drop traffic for that VLAN. To avoid this occurrence, we recommend that you either assign at least one interface to the VLAN or delete the VLAN. Viewing Ports and Port Channels Assigned to VLANs Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 On the LAN tab, click the LAN node. In the Work pane, click the LAN Uplinks Manager link on the LAN Uplinks tab. The LAN Uplinks Manager opens in a separate window. Step 4 Step 5 In the LAN Uplinks Manager, click VLANs > VLAN Manager. Click one of the following subtabs to configure ports and port channels on that fabric interconnect: Step 6 Subtab Description Fabric A Displays the ports, port channels, and VLANs that are accessible to fabric interconnect A. Fabric B Displays the ports, port channels, and VLANs that are accessible to fabric interconnect B. In the VLANs table, expand the appropriate node and the VLAN for which you want to view the assigned ports or port channels. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 329 Viewing Ports and Port Channels Assigned to VLANs Cisco UCS Manager GUI Configuration Guide, Release 2.0 330 OL-25712-04 PART IV Storage Configuration • Configuring Named VSANs, page 333 • Configuring SAN Pin Groups, page 343 • Configuring WWN Pools, page 345 • Configuring Storage-Related Policies, page 355 CHAPTER 23 Configuring Named VSANs This chapter includes the following sections: • Named VSANs, page 333 • Fibre Channel Uplink Trunking for Named VSANs, page 334 • Guidelines and Recommendations for VSANs, page 334 • Creating a Named VSAN, page 335 • Creating a Storage VSAN, page 337 • Deleting a VSAN, page 339 • Changing the VLAN ID for the FCoE VLAN for a Storage VSAN, page 340 • Enabling Fibre Channel Uplink Trunking, page 341 • Disabling Fibre Channel Uplink Trunking, page 341 Named VSANs A named VSAN creates a connection to a specific external SAN. The VSAN isolates traffic to that external SAN, including broadcast traffic. The traffic on one named VSAN knows that the traffic on another named VSAN exists, but cannot read or access that traffic. Like a named VLAN, the name that you assign to a VSAN ID adds a layer of abstraction that allows you to globally update all servers associated with service profiles that use the named VSAN. You do not need to reconfigure the servers individually to maintain communication with the external SAN. You can create more than one named VSAN with the same VSAN ID. Named VSANs in Cluster Configurations In a cluster configuration, a named VSAN can be configured to be accessible only to the Fibre Channel uplink ports on one fabric interconnect or to the Fibre Channel uplink ports on both fabric interconnects. Named VSANs and the FCoE VLAN ID You must configure each named VSAN with an FCoE VLAN ID. This property determines which VLAN is used for transporting the VSAN and its Fibre Channel packets. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 333 Fibre Channel Uplink Trunking for Named VSANs For FIP capable, converged network adapters, such as the Cisco UCS CNA M72KR-Q and the Cisco UCS CNA M72KR-E, the named VSAN must be configured with a named VLAN that is not the native VLAN for the FCoE VLAN ID. This configuration ensures that FCoE traffic can pass through these adapters. In the following sample configuration, a service profile with a vNIC and vHBA mapped to fabric A is associated with a server that has FIP capable, converged network adapters: • The vNIC is configured to use VLAN 10. • VLAN 10 is also designated as the native VLAN for the vNIC. • The vHBA is configured to use VSAN 2. • Therefore, VSAN 2 cannot be configured with VLAN 10 as the FCoE VLAN ID. VSAN 2 can be mapped to any other VLAN configured on fabric A. Fibre Channel Uplink Trunking for Named VSANs You can configure Fibre Channel uplink trunking for the named VSANs on each fabric interconnect. If you enable trunking on a fabric interconnect, all named VSANs in a Cisco UCS domain are allowed on all Fibre Channel uplink ports on that fabric interconnect. Guidelines and Recommendations for VSANs The following guidelines and recommendations apply to all named VSANs, including storage VSANs. VSAN 4079 is a Reserved VSAN ID Do not configure a VSAN as 4079. This VSAN is reserved and cannot be used in either FC switch mode or FC end-host mode. If you create a named VSAN with ID 4079, Cisco UCS Manager marks that VSAN with an error and raises a fault. Reserved VSAN Range for Named VSANs in FC Switch Mode If you plan to use FC switch mode in a Cisco UCS domain, do not configure VSANs with an ID in the range from 3040 to 4078. VSANs in that range are not operational if the fabric interconnects are configured to operate in FC switch mode. Cisco UCS Manager marks that VSAN with an error and raises a fault. Reserved VSAN Range for Named VSANs in FC End-Host Mode If you plan to use FC end-host mode in a Cisco UCS domain, do not configure VSANs with an ID in the range from 3840 to 4079. VSANs in that range are not operational if the following conditions exist in a Cisco UCS domain: • The fabric interconnects are configured to operate in FC end-host mode. • The Cisco UCS domain is configured with Fibre Channel trunking or SAN port channels. If these configurations exist, Cisco UCS Manager does the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 334 OL-25712-04 Creating a Named VSAN 1 Renders all VSANs with an ID in the range from 3840 to 4079 non-operational. 2 Raises a fault against the non-operational VSANs. 3 Transfers all non-operational VSANs to the default VSAN. 4 Transfers all vHBAs associated with the non-operational VSANs to the default VSAN. If you disable Fibre Channel trunking and delete any existing SAN port channels, Cisco UCS Manager returns all VSANs in the range from 3840 to 4078 to an operational state and restores any associated vHBAs back to those VSANs. Range Restrictions for Named VSAN IDs in FC Switch Mode If you plan to use FC switch mode in a Cisco UCS domain, do not configure VSANs in the range from 3040 to 4078. When a fabric interconnect operating in FC switch mode is connected to MDS as the upstream switch, VSANs configured in Cisco UCS Manager in the range from 3040 to 4078 and assigned as port VSANs cannot be created in MDS. This configuration results in a possible port VSAN mismatch. Guidelines for FCoE VLAN IDs Note FCoE VLANs in the SAN cloud and VLANs in the LAN cloud must have different IDs. Using the same ID for an FCoE VLAN in a VSAN and a VLAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that FCoE VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. VLAN 4048 is user-configurable. However, Cisco UCS Manager uses VLAN 4048 for the following default values. If you want to assign 4048 to a VLAN, you must reconfigure these values: The default FCoE VLAN varies according to the type of VSAN and whether Cisco UCS is a fresh installation or an upgrade, as follows: • After an upgrade to Cisco UCS, release 2.0: The FCoE storage port native VLAN uses VLAN 4048 by default. If the default FCoE VSAN was set to use VLAN 1 before the upgrade, you must change it to a VLAN ID that is not used or reserved. For example, consider changing the default to 4049 if that VLAN ID is not in use. • After a fresh install of Cisco UCS, release 2.0: The FCoE VLAN for the default VSAN uses VLAN 4048 by default. The FCoE storage port native VLAN uses VLAN 4049. Creating a Named VSAN Note FCoE VLANs in the SAN cloud and VLANs in the LAN cloud must have different IDs. Using the same ID for an FCoE VLAN in a VSAN and a VLAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that FCoE VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 335 Creating a Named VSAN Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 On the SAN tab, expand SAN > SAN Cloud. In the Work pane, click the VSANs tab. Step 4 On the icon bar to the right of the table, click +. If the + icon is disabled, click an entry in the table to enable it. Step 5 In the Create VSAN dialog box, complete the following fields: Name Description Name field The name assigned to the network. This name can be between 1 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Default Zoning field Specifies whether the default zone in this VSAN permits or denies access among its members. The default zone includes all nodes not assigned to a specific zone. This can be one of the following: • Enabled—all traffic is permitted among members of the default zone. • Disabled—all traffic is denied among members of the default zone. You cannot change the zoning after the object has been saved. Type radio button Click the radio button to determine how the VSAN should be configured. This can be one of the following: • Common/Global—The VSAN maps to the same VSAN ID in all available fabrics. • Fabric A—The VSAN maps to the a VSAN ID that exists only in fabric A. • Fabric B—The VSAN maps to the a VSAN ID that exists only in fabric B. • Both Fabrics Configured Differently—The VSAN maps to a different VSAN ID in each available fabric. If you choose this option, Cisco UCS Manager GUI displays a VSAN ID field and a FCoE VLAN field for each fabric. Cisco UCS Manager GUI Configuration Guide, Release 2.0 336 OL-25712-04 Creating a Storage VSAN Name Description VSAN ID field The unique identifier assigned to the network. The ID can be between 1 and 4078, or between 4080 and 4093. 4079 is a reserved VSAN ID. In addition, if you plan to use FC end-host mode, the range between 3840 to 4079 is also a reserved VSAN ID range. FCoE VLAN field The unique identifier assigned to the VLAN used for Fibre Channel connections. • After an upgrade to Cisco UCS, release 2.0: The FCoE storage port native VLAN uses VLAN 4048 by default. If the default FCoE VSAN was set to use VLAN 1 before the upgrade, you must change it to a VLAN ID that is not used or reserved. For example, consider changing the default to 4049 if that VLAN ID is not in use. • After a fresh install of Cisco UCS, release 2.0: The FCoE VLAN for the default VSAN uses VLAN 4048 by default. The FCoE storage port native VLAN uses VLAN 4049. For FIP capable, converged network adapters, such as the Cisco UCS CNA M72KR-Q and the Cisco UCS CNA M72KR-E, the named VSAN must be configured with a named VLAN that is not the native VLAN for the FCoE VLAN ID. This configuration ensures that FCoE traffic can pass through these adapters. Step 6 Click OK. Cisco UCS Manager GUI adds the VSAN to one of the following VSANs nodes: • The SAN Cloud > VSANs node for a storage VSAN accessible to both fabric interconnects. • The SAN Cloud > Fabric_Name > VSANs node for a VSAN accessible to only one fabric interconnect. Creating a Storage VSAN Note FCoE VLANs in the SAN cloud and VLANs in the LAN cloud must have different IDs. Using the same ID for an FCoE VLAN in a VSAN and a VLAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that FCoE VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 337 Creating a Storage VSAN Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 On the SAN tab, expand SAN > Storage Cloud. In the Work pane, click the VSANs tab. Step 4 On the icon bar to the right of the table, click +. If the + icon is disabled, click an entry in the table to enable it. Step 5 In the Create VSAN dialog box, complete the following fields: Name Description Name field The name assigned to the network. This name can be between 1 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Default Zoning field Specifies whether the default zone in this VSAN permits or denies access among its members. The default zone includes all nodes not assigned to a specific zone. This can be one of the following: • Enabled—all traffic is permitted among members of the default zone. • Disabled—all traffic is denied among members of the default zone. You cannot change the zoning after the object has been saved. Type radio button Click the radio button to determine how the VSAN should be configured. This can be one of the following: • Common/Global—The VSAN maps to the same VSAN ID in all available fabrics. • Fabric A—The VSAN maps to the a VSAN ID that exists only in fabric A. • Fabric B—The VSAN maps to the a VSAN ID that exists only in fabric B. • Both Fabrics Configured Differently—The VSAN maps to a different VSAN ID in each available fabric. If you choose this option, Cisco UCS Manager GUI displays a VSAN ID field and a FCoE VLAN field for each fabric. Cisco UCS Manager GUI Configuration Guide, Release 2.0 338 OL-25712-04 Deleting a VSAN Name Description VSAN ID field The unique identifier assigned to the network. The ID can be between 1 and 4078, or between 4080 and 4093. 4079 is a reserved VSAN ID. In addition, if you plan to use FC end-host mode, the range between 3840 to 4079 is also a reserved VSAN ID range. FCoE VLAN field The unique identifier assigned to the VLAN used for Fibre Channel connections. • After an upgrade to Cisco UCS, release 2.0: The FCoE storage port native VLAN uses VLAN 4048 by default. If the default FCoE VSAN was set to use VLAN 1 before the upgrade, you must change it to a VLAN ID that is not used or reserved. For example, consider changing the default to 4049 if that VLAN ID is not in use. • After a fresh install of Cisco UCS, release 2.0: The FCoE VLAN for the default VSAN uses VLAN 4048 by default. The FCoE storage port native VLAN uses VLAN 4049. For FIP capable, converged network adapters, such as the Cisco UCS CNA M72KR-Q and the Cisco UCS CNA M72KR-E, the named VSAN must be configured with a named VLAN that is not the native VLAN for the FCoE VLAN ID. This configuration ensures that FCoE traffic can pass through these adapters. Step 6 Click OK. Cisco UCS Manager GUI adds the VSAN to one of the following VSANs nodes: • The Storage Cloud > VSANs node for a storage VSAN accessible to both fabric interconnects. • The Storage Cloud > Fabric_Name > VSANs node for a VSAN accessible to only one fabric interconnect. Deleting a VSAN If Cisco UCS Manager includes a named VSAN with the same VSAN ID as the one you delete, the VSAN is not removed from the fabric interconnect configuration until all named VSANs with that ID are deleted. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 339 Changing the VLAN ID for the FCoE VLAN for a Storage VSAN Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 In the SAN tab, click the SAN node. In the Work pane, click the VSANs tab. Step 4 Click one of the following subtabs, depending upon what type of VSAN you want to delete: Subtab Description All Displays all VSANs in the Cisco UCS domain. Dual Mode Displays the VSANs that are accessible to both fabric interconnects. Switch A Displays the VSANs that are accessible to only fabric interconnect A. Switch B Displays the VSANs that are accessible to only fabric interconnect B. Step 5 In the table, click the VSAN you want to delete. You can use the Shift key or Ctrl key to select multiple entries. Step 6 Step 7 Right-click the highlighted VSAN or VSANs and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Changing the VLAN ID for the FCoE VLAN for a Storage VSAN Note FCoE VLANs in the SAN cloud and VLANs in the LAN cloud must have different IDs. Using the same ID for an FCoE VLAN in a VSAN and a VLAN results in a critical fault and traffic disruption for all vNICs and uplink ports using that FCoE VLAN. Ethernet traffic is dropped on any VLAN which has an ID that overlaps with an FCoE VLAN ID. Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 On the SAN tab, expand SAN > Storage Cloud > VSANs. Choose the VSAN for which you want to modify the FCoE VLAN ID. In the Work pane, click the General tab. Step 5 In the FCoE VLAN field, enter the desired VLAN ID. • After an upgrade to Cisco UCS, release 2.0: The FCoE storage port native VLAN uses VLAN 4048 by default. If the default FCoE VSAN was set to use VLAN 1 before the upgrade, you must change it to a VLAN ID that is not used or reserved. For example, consider changing the default to 4049 if that VLAN ID is not in use. Cisco UCS Manager GUI Configuration Guide, Release 2.0 340 OL-25712-04 Enabling Fibre Channel Uplink Trunking • After a fresh install of Cisco UCS, release 2.0: The FCoE VLAN for the default VSAN uses VLAN 4048 by default. The FCoE storage port native VLAN uses VLAN 4049. Step 6 Click Save Changes. Enabling Fibre Channel Uplink Trunking Note If the fabric interconnects are configured for Fibre Channel end-host mode, enabling Fibre Channel uplink trunking renders all VSANs with an ID in the range from 3840 to 4079 non-operational. Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 On the SAN tab, expand SAN > SAN Cloud. Click the node for the fabric where you want to enable FC uplink trunking. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Enable FC Uplink Trunking. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Disabling Fibre Channel Uplink Trunking Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 On the SAN tab, expand SAN > SAN Cloud. Click the node for the fabric where you want to disable Fibre Channel uplink trunking. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Disable FC Uplink Trunking. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 341 Disabling Fibre Channel Uplink Trunking Cisco UCS Manager GUI Configuration Guide, Release 2.0 342 OL-25712-04 CHAPTER 24 Configuring SAN Pin Groups This chapter includes the following sections: • SAN Pin Groups, page 343 • Creating a SAN Pin Group, page 343 • Deleting a SAN Pin Group, page 344 SAN Pin Groups Cisco UCS uses SAN pin groups to pin Fibre Channel traffic from a vHBA on a server to an uplink Fibre Channel port on the fabric interconnect. You can use this pinning to manage the distribution of traffic from the servers. Note In Fibre Channel switch mode, SAN pin groups are irrelevant. Any existing SAN pin groups will be ignored. To configure pinning for a server, you must include the SAN pin group in a vHBA policy. The vHBA policy is then included in the service profile assigned to that server. All traffic from the vHBA will travel through the I/O module to the specified uplink Fibre Channel port. You can assign the same pin group to multiple vHBA policies. As a result, you do not need to manually pin the traffic for each vHBA. Important Changing the target interface for an existing SAN pin group disrupts traffic for all vHBAs which use that pin group. The fabric interconnect performs a log in and log out for the Fibre Channel protocols to re-pin the traffic. Creating a SAN Pin Group In a system with two fabric interconnects, you can associate the pin group with only one fabric interconnect or with both fabric interconnects. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 343 Deleting a SAN Pin Group Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 Step 5 In the SAN tab, expand SAN > SAN Cloud. Right-click SAN Pin Groups and select Create SAN Pin Group. Enter a unique name and description for the pin group. To pin traffic for fabric interconnect A, do the following in the Targets area: a) Check the Fabric A check box. b) Click the drop-down arrow on the Interface field and navigate through the tree-style browser to select the uplink Fibre Channel port you want to associate with the pin group. Step 6 To pin traffic for fabric interconnect B, do the following in the Targets area: a) Check the Fabric B check box. b) Click the drop-down arrow on the Interface field and navigate through the tree-style browser to select the uplink Fibre Channel port you want to associate with the pin group. Step 7 Click OK. What to Do Next Include the pin group in a vHBA template. Deleting a SAN Pin Group Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 In the SAN tab, expand SAN > SAN Cloud > SAN Pin Groups. Right-click the SAN pin group you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 344 OL-25712-04 CHAPTER 25 Configuring WWN Pools This chapter includes the following sections: • WWN Pools, page 345 • Configuring WWNN Pools, page 346 • Configuring WWPN Pools, page 350 WWN Pools A WWN pool is a collection of WWNs for use by the Fibre Channel vHBAs in a Cisco UCS domain. You create separate pools for the following: • WW node names assigned to the server • WW port names assigned to the vHBA Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. All other WWN ranges are reserved. To ensure the uniqueness of the Cisco UCS WWNNs and WWPNs in the SAN fabric, we recommend that you use the following WWN prefix for all blocks in a pool: 20:00:00:25:B5:XX:XX:XX If you use WWN pools in service profiles, you do not have to manually configure the WWNs that will be used by the server associated with the service profile. In a system that implements multi-tenancy, you can use a WWN pool to control the WWNs used by each organization. You assign WWNs to pools in blocks. For each block or individual WWN, you can assign a boot target. WWNN Pools A WWNN pool is a WWN pool that contains only WW node names. If you include a pool of WWNNs in a service profile, the associated server is assigned a WWNN from that pool. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 345 Configuring WWNN Pools WWPN Pools A WWPN pool is a WWN pool that contains only WW port names. If you include a pool of WWPNs in a service profile, the port on each vHBA of the associated server is assigned a WWPN from that pool. Configuring WWNN Pools Creating a WWNN Pool Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. All other WWN ranges are reserved. To ensure the uniqueness of the Cisco UCS WWNNs and WWPNs in the SAN fabric, we recommend that you use the following WWN prefix for all blocks in a pool: 20:00:00:25:B5:XX:XX:XX Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 In the SAN tab, expand SAN > Pools. Expand the node for the organization where you want to create the pool. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click WWNN Pools and select Create WWNN Pool. In the Define Name and Description page of the Create WWNN Pool wizard: a) Enter a unique name and description for the WWNN Pool. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. b) Click Next. Step 6 In the Add WWN Blocks page of the Create WWNN Pool wizard, click Add. Step 7 In the Create WWN Block page, complete the following fields: a) In the From field, enter the first WWNN in the pool. b) In the Size field, enter the number of WWNNs to include in the pool. c) Click OK. Step 8 Do one of the following: • Repeat Steps 6 through 7 to add another block to the pool. • Click Next to move to the next page. Step 9 Click Finish. Cisco UCS Manager GUI Configuration Guide, Release 2.0 346 OL-25712-04 Configuring WWNN Pools Adding a WWN Block to a WWNN Pool Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. All other WWN ranges are reserved. To ensure the uniqueness of the Cisco UCS WWNNs and WWPNs in the SAN fabric, we recommend that you use the following WWN prefix for all blocks in a pool: 20:00:00:25:B5:XX:XX:XX Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 In the SAN tab, expand SAN > Pools > Organization_Name . Expand the WWNN Pools node. Right-click the WWNN pool to which you want to add a WWN block and select Create WWN Block. In the Create WWN Block page, complete the following fields: Step 3 Step 4 Step 5 a) In the From field, enter the first WWNN in the pool. b) In the Size field, enter the number of WWNNs to include in the pool. c) Click OK. Deleting a WWN Block from a WWNN Pool If you delete an address block from a pool, Cisco UCS Manager does not reallocate any addresses in that block that have been assigned to vNICs or vHBAs. All assigned addresses from a deleted block remain with the vNIC or vHBA to which they are assigned until one of the following occurs: • The associated service profiles are deleted. • The vNIC or vHBA to which the address is assigned is deleted. • The vNIC or vHBA is assigned to a different pool. Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 In the SAN tab, expand SAN > Pools > Organization_Name > WWNN Pools > WWNN_Pool_Name . Right-click the WWN block that you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 347 Configuring WWNN Pools Adding a WWNN Initiator to a WWNN Pool Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. All other WWN ranges are reserved. To ensure the uniqueness of the Cisco UCS WWNNs and WWPNs in the SAN fabric, we recommend that you use the following WWN prefix for all blocks in a pool: 20:00:00:25:B5:XX:XX:XX Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 In the SAN tab, expand SAN > Pools > Organization_Name . Expand the WWNN Pools node. Right-click the WWNN pool to which you want to add a WWNN initiator and select Create WWNN Initiiator. In the Create WWNN Initiator dialog box, complete the following fields: Step 3 Step 4 Step 5 Name Description World Wide Name field The WWN. Name field The name of the WWNN initiator. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A user-defined description of the WWNN initiator. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Step 6 Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 348 OL-25712-04 Configuring WWNN Pools Deleting a WWNN Initiator from a WWNN Pool Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 Step 5 In the SAN tab, expand SAN > Pools > Organization_Name . Expand the WWPN Pools node. Choose the WWNN pool from which you want to delete a WWNN initiator. In the Work pane, click the Initiators tab. Step 6 Step 7 Right-click the initiator that you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Deleting a WWNN Pool If you delete a pool, Cisco UCS Manager does not reallocate any addresses from that pool that have been assigned to vNICs or vHBAs. All assigned addresses from a deleted pool remain with the vNIC or vHBA to which they are assigned until one of the following occurs: • The associated service profiles are deleted. • The vNIC or vHBA to which the address is assigned is deleted. • The vNIC or vHBA is assigned to a different pool. Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 Step 5 In the SAN tab, expand SAN > Pools > Organization_Name . Expand the WWNN Pools node. Right-click the WWNN pool you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 349 Configuring WWPN Pools Configuring WWPN Pools Creating a WWPN Pool Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. All other WWN ranges are reserved. To ensure the uniqueness of the Cisco UCS WWNNs and WWPNs in the SAN fabric, we recommend that you use the following WWN prefix for all blocks in a pool: 20:00:00:25:B5:XX:XX:XX Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 In the SAN tab, expand SAN > Pools. Expand the node for the organization where you want to create the pool. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click WWPN Pools and select Create WWPN Pool. In the Define Name and Description page of the Create WWN Pool wizard: a) Enter a unique name and description for the WWPN Pool. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. b) Click Next. Step 6 In the Add WWN Blocks page of the Create WWPN Pool wizard, click Add. Step 7 In the Create WWN Block page, complete the following fields: a) In the From field, enter the first WWPN in the pool. b) In the Size field, enter the number of WWPNs to include in the pool. c) Click OK. Step 8 Click Finish. What to Do Next Include the WWPN pool in a vHBA template. Cisco UCS Manager GUI Configuration Guide, Release 2.0 350 OL-25712-04 Configuring WWPN Pools Adding a WWN Block to a WWPN Pool Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. All other WWN ranges are reserved. To ensure the uniqueness of the Cisco UCS WWNNs and WWPNs in the SAN fabric, we recommend that you use the following WWN prefix for all blocks in a pool: 20:00:00:25:B5:XX:XX:XX Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 In the SAN tab, expand SAN > Pools > Organization_Name . Expand the WWPN Pools node. Right-click the WWPN pool to which you want to add a WWN block and select Create WWN Block. In the Create WWN Block page, complete the following fields: Step 3 Step 4 Step 5 a) In the From field, enter the first WWPN in the pool. b) In the Size field, enter the number of WWPNs to include in the pool. c) Click OK. Deleting a WWN Block from a WWPN Pool If you delete an address block from a pool, Cisco UCS Manager does not reallocate any addresses in that block that have been assigned to vNICs or vHBAs. All assigned addresses from a deleted block remain with the vNIC or vHBA to which they are assigned until one of the following occurs: • The associated service profiles are deleted. • The vNIC or vHBA to which the address is assigned is deleted. • The vNIC or vHBA is assigned to a different pool. Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 In the SAN tab, expand SAN > Pools > Organization_Name > WWPN Pools > WWPN_Pool_Name . Right-click the WWN block that you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 351 Configuring WWPN Pools Adding a WWPN Initiator to a WWPN Pool Important A WWN pool can include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. All other WWN ranges are reserved. To ensure the uniqueness of the Cisco UCS WWNNs and WWPNs in the SAN fabric, we recommend that you use the following WWN prefix for all blocks in a pool: 20:00:00:25:B5:XX:XX:XX Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 In the SAN tab, expand SAN > Pools > Organization_Name . Expand the WWPN Pools node. Right-click the WWPN pool to which you want to add a WWPN initiator and select Create WWPN Initiator. In the Create WWPN Initiator dialog box, complete the following fields: Step 3 Step 4 Step 5 Name Description World Wide Name field The WWN. Name field The name of the WWPN initiator. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A user-defined description of the WWPN initiator. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Step 6 Step 7 If you want to add a SAN boot target, expand the Boot Target area and complete the following fields: Name Description Boot Target WWPN field The WWPN that corresponds to the location of the boot image. Boot Target LUN field The LUN that corresponds to the location of the boot image. Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 352 OL-25712-04 Configuring WWPN Pools Deleting a WWPN Initiator from a WWPN Pool Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 Step 5 In the SAN tab, expand SAN > Pools > Organization_Name . Expand the WWPN Pools node. Choose the WWPN pool from which you want to delete a WWPN initiator. In the Work pane, click the Initiators tab. Step 6 Step 7 Right-click the initiator that you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Deleting a WWPN Pool If you delete a pool, Cisco UCS Manager does not reallocate any addresses from that pool that have been assigned to vNICs or vHBAs. All assigned addresses from a deleted pool remain with the vNIC or vHBA to which they are assigned until one of the following occurs: • The associated service profiles are deleted. • The vNIC or vHBA to which the address is assigned is deleted. • The vNIC or vHBA is assigned to a different pool. Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 Step 5 In the SAN tab, expand SAN > Pools > Organization_Name . Expand the WWPN Pools node. Right-click the WWPN pool you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 353 Configuring WWPN Pools Cisco UCS Manager GUI Configuration Guide, Release 2.0 354 OL-25712-04 CHAPTER 26 Configuring Storage-Related Policies This chapter includes the following sections: • Configuring vHBA Templates, page 355 • Configuring Fibre Channel Adapter Policies, page 358 Configuring vHBA Templates vHBA Template This template is a policy that defines how a vHBA on a server connects to the SAN. It is also referred to as a vHBA SAN connectivity template. You need to include this policy in a service profile for it to take effect. Creating a vHBA Template Before You Begin This policy requires that one or more of the following resources already exist in the system: • Named VSAN • WWNN pool or WWPN pool • SAN pin group • Statistics threshold policy Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 On the SAN tab, expand SAN > Policies. Expand the node for the organization where you want to create the policy. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 355 Configuring vHBA Templates If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click the vHBA Templates node and choose Create vHBA Template. In the Create vHBA Template dialog box, complete the following fields: Name Description Name field The name of the virtual HBA template. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A user-defined description of the template. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Fabric ID field The name of the fabric interconnect that vHBAs created with this template are associated with. Select VSAN drop-down list The VSAN to associate with vHBAs created from this template. Create VSAN link Click this link if you want to create a VSAN. Template Type field This can be one of the following: • Initial Template—vHBAs created from this template are not updated if the template changes. • Updating Template—vHBAs created from this template are updated if the template changes. Max Data Field Size field The maximum size of the Fibre Channel frame payload bytes that the vHBA supports. Enter an integer between 256 and 2112. The default is 2048. WWN Pool drop-down list The WWN pool that a vHBA created from this template uses to derive its WWN address. QoS Policy drop-down list The QoS policy that is associated with vHBAs created from this template. Pin Group drop-down list The LAN pin group that is associated with vHBAs created from this template. Stats Threshold Policy drop-down The statistics collection policy that is associated with vHBAs created list from this template. Cisco UCS Manager GUI Configuration Guide, Release 2.0 356 OL-25712-04 Configuring vHBA Templates Step 6 Click OK. What to Do Next Include the vHBA template in a service profile. Deleting a vHBA Template Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 Step 5 On the SAN tab, expand SAN > Policies > Organization_Name. Expand the vHBA Templates node. Right-click the vHBA template that you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Binding a vHBA to a vHBA Template You can bind a vHBA associated with a service profile to a vHBA template. When you bind the vHBA to a vHBA template, Cisco UCS Manager configures the vHBA with the values defined in the vHBA template. If the existing vHBA configuration does not match the vHBA template, Cisco UCS Manager reconfigures the vHBA. You can only change the configuration of a bound vHBA through the associated vHBA template. You cannot bind a vHBA to a vHBA template if the service profile that includes the vHBA is already bound to a service profile template. Important If the vHBA is reconfigured when you bind it to a template, Cisco UCS Manager reboots the server associated with the service profile. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that includes the service profile with the vHBA you want to bind. If the system does not include multi-tenancy, expand the root node. Step 4 Step 5 Step 6 Expand Service_Profile_Name > vHBAs. Click the vHBA you want to bind to a template. In the Work pane, click the General tab. Step 7 Step 8 In the Actions area, click Bind to a Template. In the Bind to a vHBA Template dialog box, do the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 357 Configuring Fibre Channel Adapter Policies a) From the vHBA Template drop-down list, choose the template to which you want to bind the vHBA. b) Click OK. Step 9 In the warning dialog box, click Yes to acknowledge that Cisco UCS Manager may need to reboot the server if the binding causes the vHBA to be reconfigured. Unbinding a vHBA from a vHBA Template Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Step 4 Step 5 Step 6 Expand Service_Profile_Name > vHBAs. Click the vHBA you want to unbind from a template. In the Work pane, click the General tab. Step 7 Step 8 In the Actions area, click Unbind from a Template. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Expand the node for the organization that includes the service profile with the vHBA you want to unbind. If the system does not include multi-tenancy, expand the root node. Configuring Fibre Channel Adapter Policies Ethernet and Fibre Channel Adapter Policies These policies govern the host-side behavior of the adapter, including how the adapter handles traffic. For example, you can use these policies to change default settings for the following: • Queues • Interrupt handling • Performance enhancement • RSS hash • Failover in an cluster configuration with two fabric interconnects Cisco UCS Manager GUI Configuration Guide, Release 2.0 358 OL-25712-04 Configuring Fibre Channel Adapter Policies Note For Fibre Channel adapter policies, the values displayed by Cisco UCS Manager may not match those displayed by applications such as QLogic SANsurfer. For example, the following values may result in an apparent mismatch between SANsurfer and Cisco UCS Manager: • Max LUNs Per Target—SANsurfer has a maximum of 256 LUNs and does not display more than that number. Cisco UCS Manager supports a higher maximum number of LUNs. • Link Down Timeout—In SANsurfer, you configure the timeout threshold for link down in seconds. In Cisco UCS Manager, you configure this value in milliseconds. Therefore, a value of 5500 ms in Cisco UCS Manager displays as 5s in SANsurfer. • Max Data Field Size—SANsurfer has allowed values of 512, 1024, and 2048. Cisco UCS Manager allows you to set values of any size. Therefore, a value of 900 in Cisco UCS Manager displays as 512 in SANsurfer. Operating System Specific Adapter Policies By default, Cisco UCS provides a set of Ethernet adapter policies and Fibre Channel adapter policies. These policies include the recommended settings for each supported server operating system. Operating systems are sensitive to the settings in these policies. Storage vendors typically require non-default adapter settings. You can find the details of these required settings on the support list provided by those vendors. Important We recommend that you use the values in these policies for the applicable operating system. Do not modify any of the values in the default policies unless directed to do so by Cisco Technical Support. However, if you are creating an Ethernet adapter policy for a Windows OS (instead of using the default Windows adapter policy), you must use the following formulas to calculate values that work with Windows: Completion Queues = Transmit Queues + Receive Queues Interrupt Count = (Completion Queues + 2) rounded up to nearest power of 2 For example, if Transmit Queues = 1 and Receive Queues = 8 then: Completion Queues = 1 + 8 = 9 Interrupt Count = (9 + 2) rounded up to the nearest power of 2 = 16 Creating a Fibre Channel Adapter Policy Tip If the fields in an area are not displayed, click the Expand icon to the right of the heading. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 359 Configuring Fibre Channel Adapter Policies Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click Fibre Channel Policies and choose Create Fibre Channel Adapter Policy. Enter a name and description for the policy in the following fields: Name Description Name field The name of the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A description of the policy. We recommend that you include information about where and when the policy should be used. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Step 6 (Optional) In the Resources area, adjust the following values: Name Description Transmit Queues field The number of transmit queue resources to allocate. This value cannot be changed. Ring Size field The number of descriptors in each transmit queue. This parameter applies to Extended Link Services (ELS) and Common Transport (CT) fibre channel frames for generic services. It does not affect adapter performance. Enter an integer between 64 and 128. The default is 64. Receive Queues field The number of receive queue resources to allocate. This value cannot be changed. Ring Size field The number of descriptors in each receive queue. This parameter applies to Extended Link Services (ELS) and Common Transport (CT) fibre channel frames for generic services. It does not affect adapter performance. Enter an integer between 64 and 128. The default is 64. Cisco UCS Manager GUI Configuration Guide, Release 2.0 360 OL-25712-04 Configuring Fibre Channel Adapter Policies Name Description SCSI I/O Queues field The number of SCSI IO queue resources the system should allocate. Enter an integer between 1 and 8. The default is 1. Note Ring Size field At this time, the Cisco UCS M81KR Virtual Interface Card adapter supports only one SCSI I/O queue. The number of descriptors in each SCSI I/O queue. Enter an integer between 64 and 512. The default is 512. Note Step 7 The number of descriptors can affect the performance of the adapter, so we recommend that you do not change the default value. (Optional) In the Options area, adjust the following values: Name Description FCP Error Recovery field Whether the system uses FCP Sequence Level Error Recovery (FC-TAPE) protocol for sequence level error recovery with tape devices. This enables or disables the Read Exchange Concise (REC) and Sequence Retransmission Request (SRR) functions on the VIC firmware. This can be one of the following: • Disabled—This is the default. • Enabled—You should select this option if your system is connected to one or more tape drive libraries. Note Flogi Retries field This parameter only applies to a server with a Virtual Interface Card (VIC) adapter, such as the Cisco UCS M81KR Virtual Interface Card. The number of times that the system tries to log in to the fabric after the first failure. Enter any integer. To specify that the system continue to try indefinitely, enter infinite in this field. We recommend you consult your storage array documentation for the optimal value for this parameter. Note Flogi Timeout field This parameter only applies to a server with a VIC adapter, or a converged network adapter such as the Cisco UCS M71KR-E Emulex Converged Network Adapter. The number of milliseconds that the system waits before it tries to log in again. Enter an integer between 1000 and 255000. The default is 4,000. We recommend you consult your storage array documentation for the optimal value for this parameter. Note This parameter only applies to a server with a VIC adapter or a converged network adapter. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 361 Configuring Fibre Channel Adapter Policies Name Description Plogi Retries field The number of times that the system tries to log into a port after the first failure. Enter an integer between 0 and 255. The default is 8. We recommend you consult your storage array documentation for the optimal value for this parameter. Note Plogi Timeout field This parameter only applies to a server with a VIC adapter. The number of milliseconds that the system waits before it tries to log in again. Enter an integer between 1000 and 255000. The default is 20,000. We recommend you consult your storage array documentation for the optimal value for this parameter. Note Error Detect Timeout field This parameter only applies to a server with a VIC adapter. The number of milliseconds to wait before the system assumes that an error has occurred. This value cannot be changed. Port Down Timeout field The number of milliseconds a remote Fibre Channel port should be offline before informing the SCSI upper layer that the port is unavailable. This parameter is important for host multi-pathing drivers and it is one of the key indicators used for error processing. Enter an integer between 0 and 240000. The default is 30,000. For a server with a VIC adapter running ESX, the recommended value is 10,000. We recommend you consult your storage array documentation for the optimal value for this parameter. Note Port Down IO Retry field This parameter only applies to a server with a VIC adapter. The number of times an IO request to a port is returned because the port is busy before the system decides the port is unavailable. Enter an integer between 0 and 255. The default is 8. We recommend you consult your storage array documentation for the optimal value for this parameter. Note This parameter only applies to a server with a VIC adapter running Windows. Cisco UCS Manager GUI Configuration Guide, Release 2.0 362 OL-25712-04 Configuring Fibre Channel Adapter Policies Name Description Link Down Timeout field The number of milliseconds the uplink port should be offline before it informs the system that the uplink port is down and fabric connectivity has been lost. Enter an integer between 0 and 240000. The default is 30,000. We recommend you consult your storage array documentation for the optimal value for this parameter. Note Resource Allocation Timeout field This parameter only applies to a server with a VIC adapter running Windows. The number of milliseconds to wait before the system assumes that a resource cannot be properly allocated. This value cannot be changed. IO Throttle Count field The maximum number of data or control I/O operations that can be pending in the vHBA at one time. If this value is exceeded, the additional I/O operations wait in the queue until the number of pending I/O operations decreases and the additional operations can be processed. This parameter is not the same as the LUN queue depth, which is controlled by Cisco UCS Manager based on the operating system installed on the server. Enter an integer between 1 and 1024. The default is 16. We recommend you consult your storage array documentation for the optimal value for this parameter. Note Note Max LUNs Per Target field This parameter only applies to a server with a network adapter such as the Cisco UCS M71KR-E Emulex Converged Network Adapter or the Cisco UCS M71KR-Q QLogic Converged Network Adapter. Servers with a VIC adapter ignore this parameter. The maximum number of LUNs that the Fibre Channel driver will export or show. The maximum number of LUNs is usually controlled by the operating system running on the server. Enter an integer between 1 and 1024. The default value is 256. For servers running ESX or Linux, the recommended value is 1024. We recommend you consult your operating system documentation for the optimal value for this parameter. Note This parameter only applies to a server with a VIC adapter or a network adapter. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 363 Configuring Fibre Channel Adapter Policies Name Description Interrupt Mode field The method used to send interrupts to the operating system from the driver. This can be one of the following: • MSI-X—Message Signaled Interrupts (MSI) with the optional extension. We recommend that you select this option if the operating system on the server supports it. • MSI—MSI only. • INTx—PCI INTx interrupts. Note Step 8 Step 9 This parameter only applies to a server with a VIC adapter or a network adapter running an operating system other than Windows. The Windows operating system ignores this parameter. Click OK. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Deleting a Fibre Channel Adapter Policy Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 Step 5 On the SAN tab, expand SAN > Policies > Organization_Name. Expand the Fibre Channel Policies node. Right-click the policy you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 364 OL-25712-04 PART V Server Configuration • Configuring Server-Related Pools, page 367 • Setting the Management IP Address, page 373 • Configuring Server-Related Policies, page 381 • Configuring Server Boot, page 439 • Deferring Deployment of Service Profile Updates, page 469 • Configuring Service Profiles, page 487 • Managing Power in Cisco UCS, page 563 CHAPTER 27 Configuring Server-Related Pools This chapter includes the following sections: • Configuring Server Pools, page 367 • Configuring UUID Suffix Pools, page 369 Configuring Server Pools Server Pools A server pool contains a set of servers. These servers typically share the same characteristics. Those characteristics can be their location in the chassis, or an attribute such as server type, amount of memory, local storage, type of CPU, or local drive configuration. You can manually assign a server to a server pool, or use server pool policies and server pool policy qualifications to automate the assignment. If your system implements multi-tenancy through organizations, you can designate one or more server pools to be used by a specific organization. For example, a pool that includes all servers with two CPUs could be assigned to the Marketing organization, while all servers with 64 GB memory could be assigned to the Finance organization. A server pool can include servers from any chassis in the system. A given server can belong to multiple server pools. Creating a Server Pool Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Pools. Expand the node for the organization where you want to create the pool. If the system does not include multitenancy, expand the root node. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 367 Configuring Server Pools Step 4 Step 5 Right-click the Server Pools node and select Create Server Pool. On the Set Name and Description page of the Create Server Pool wizard, complete the following fields: Name Description Name field The name of the server pool. This name can be between 1 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A user-defined description of the server pool. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Step 6 Step 7 Click Next. On the Add Servers page of the Create Server Pool wizard: a) Select one or more servers from the Available Servers table. b) Click the >> button to add the servers to the server pool. c) When you have added all desired servers to the pool, click Finish. Deleting a Server Pool Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Servers > Pools > Organization_Name. Expand the Server Pools node. Right-click the pool you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 368 OL-25712-04 Configuring UUID Suffix Pools Adding Servers to a Server Pool Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 On the Servers tab, expand Servers > Pools > Organization_Name. Right-click the pool to which you want to add one or more servers and select Add Servers to Server Pool. In the Add Servers to Server Pool dialog box, do the following: a) In the Servers table, select the servers that you want to add to the server pool. You can use the Shift key or Ctrl key to select multiple entries. b) Click the >> button to move those servers to the Pooled Servers table and add them to the server pool. c) Click OK. Removing Servers from a Server Pool Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Pools > Organization_Name. Right-click the pool from which you want to remove one or more servers and select Add Servers to Server Pool. In the Add Servers to Server Pool dialog box, do the following: Step 4 a) In the Pooled Servers table, select the servers that you want to remove from the server pool. You can use the Shift key or Ctrl key to select multiple entries. b) Click the << button to move those servers to the Servers table and remove them from the server pool. c) Click OK. Configuring UUID Suffix Pools UUID Suffix Pools A UUID suffix pool is a collection of SMBIOS UUIDs that are available to be assigned to servers. The first number of digits that constitute the prefix of the UUID are fixed. The remaining digits, the UUID suffix, are variable. A UUID suffix pool ensures that these variable values are unique for each server associated with a service profile which uses that particular pool to avoid conflicts. If you use UUID suffix pools in service profiles, you do not have to manually configure the UUID of the server associated with the service profile. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 369 Configuring UUID Suffix Pools Creating a UUID Suffix Pool Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Pools. Expand the node for the organization where you want to create the pool. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click UUID Suffix Pools and select Create UUID Suffix Pool. In the Define Name and Description page of the Create UUID Suffix Pool wizard, fill in the following fields: Name Description Name field The name of the UUID pool. This name can be between 1 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field The user-defined description of the pool. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Prefix field This can be one of the following: • Derived—The system creates the suffix. • other—You specify the desired suffix. If you select this option, Cisco UCS Manager GUI displays a text field where you can enter the desired suffix, in the format XXXXXXXX-XXXX-XXXX. Step 6 In the Add UUID Blocks page of the Create UUID Suffix Pool wizard: a) Click Add. b) In the Create a Block of UUID Suffixes page, enter the first UUID suffix in the pool and the number of UUID suffixes to include in the pool. c) Click OK. d) If you want to add another block to the pool, repeat steps a through c. Step 7 Click Finish to complete the wizard. What to Do Next Include the UUID suffix pool in a service profile and/or template. Cisco UCS Manager GUI Configuration Guide, Release 2.0 370 OL-25712-04 Configuring UUID Suffix Pools Deleting a UUID Suffix Pool If you delete a pool, Cisco UCS Manager does not reallocate any addresses from that pool that have been assigned to vNICs or vHBAs. All assigned addresses from a deleted pool remain with the vNIC or vHBA to which they are assigned until one of the following occurs: • The associated service profiles are deleted. • The vNIC or vHBA to which the address is assigned is deleted. • The vNIC or vHBA is assigned to a different pool. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Servers > Pools > Organization_Name. Expand the UUID Suffix Pools node. Right-click the pool you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 371 Configuring UUID Suffix Pools Cisco UCS Manager GUI Configuration Guide, Release 2.0 372 OL-25712-04 CHAPTER 28 Setting the Management IP Address This chapter includes the following sections: • Management IP Address, page 373 • Configuring the Management IP Address on a Blade Server, page 374 • Configuring the Management IP Address on a Rack Server, page 375 • Setting the Management IP Address on a Service Profile, page 376 • Setting the Management IP Address on a Service Profile Template, page 377 • Configuring the Management IP Pool, page 377 Management IP Address Each server in a Cisco UCS domain must have a management IP address assigned to its Cisco Integrated Management Controller (CIMC) or to the service profile associated with the server. Cisco UCS Manager uses this IP address for external access that terminates in the CIMC. This external access can be through one of the following: • KVM console • Serial over LAN • An IPMI tool The management IP address used to access the CIMC on a server can be one of the following: • A static IPv4 address assigned directly to the server. • A static IPv4 address assigned to a service profile. You cannot configure a service profile template with a static IP address. • An IP address drawn from the management IP address pool and assigned to a service profile or service profile template. You can assign a management IP address to each CIMC on the server and to the service profile associated with the server. If you do so, you must use different IP addresses for each of them. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 373 Configuring the Management IP Address on a Blade Server Note You cannot assign a static IP address to a server or service profile if that IP address has already been assigned to a server or service profile in the Cisco UCS domain. If you attempt to do so, Cisco UCS Manager warns you that the IP address is already in use and rejects the configuration. A management IP address that is assigned to a service profile moves with the service profile. If a KVM or SoL session is active when you migrate the service profile to another server, Cisco UCS Manager terminates that session and does not restart it after the migration is completed. You configure this IP address when you create or modify a service profile. Configuring the Management IP Address on a Blade Server Configuring a Blade Server to Use a Static IP Address If this action is greyed out, the server has already been assigned a static IP address. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Click the server for which you want to configure an IP address. In the Work pane, click the Inventory tab. Step 5 Step 6 Step 7 Click the CIMC subtab. In the Actions area, click Create/Modify Static Management IP. In the Create/Modify Static Management IP dialog box, complete the following fields: Step 8 Field Description IP Address The static IPv4 address to be assigned to the server. Subnet Mask The subnet mask for the IP address. Default Gateway The default gateway that the IP address should use. Click OK. Configuring a Blade Server to Use the Management IP Pool If this action is greyed out, the server is already configured to use the management IP pool. Cisco UCS Manager GUI Configuration Guide, Release 2.0 374 OL-25712-04 Configuring the Management IP Address on a Rack Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Click the server that you want to configure to use the management IP pool. In the Work pane, click the Inventory tab. Step 5 Step 6 Step 7 Step 8 Click the CIMC subtab. In the Actions area, click Use Pooled Management IP. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click OK. Configuring the Management IP Address on a Rack Server Configuring a Rack Server to Use a Static IP Address If this action is greyed out, the server has already been assigned a static IP address. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Click the server for which you want to configure an IP address. In the Work pane, click the Inventory tab. Step 5 Step 6 Step 7 Click the CIMC subtab. In the Actions area, click Create/Modify Static Management IP. In the Create/Modify Static Management IP dialog box, complete the following fields: Step 8 Field Description IP Address The static IPv4 address to be assigned to the server. Subnet Mask The subnet mask for the IP address. Default Gateway The default gateway that the IP address should use. Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 375 Setting the Management IP Address on a Service Profile Configuring a Rack Server to Use the Management IP Pool If this action is greyed out, the server is already configured to use the management IP pool. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Click the server that you want to configure to use the management IP pool. In the Work pane, click the Inventory tab. Step 5 Step 6 Step 7 Click the CIMC subtab. In the Actions area, click Use Pooled Management IP. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click OK. Step 8 Setting the Management IP Address on a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile for which you want to set the management IP address. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Click the service profile for which you want to set the management IP address. In the Work pane, click the General tab. Step 6 Step 7 Expand the Management IP Address area. In the Management IP Address Policy field, click one of the following radio buttons: • None—No management IP address is assigned to the service profile. The management IP address is set based on the CIMC management IP address settings on the server. • Static—A static management IP address is assigned to the service profile, based on the information entered in this area. • Pooled—A management IP address is assigned to the service profile from the management IP address pool. Step 8 If you selected static, complete the following fields: Cisco UCS Manager GUI Configuration Guide, Release 2.0 376 OL-25712-04 Setting the Management IP Address on a Service Profile Template Step 9 Field Description IP Address The static IPv4 address to be assigned to the service profile Subnet Mask The subnet mask for the IP address. Default Gateway The default gateway that the IP address should use. Click Save Changes. Setting the Management IP Address on a Service Profile Template Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profile Templates. Expand the node for the organization that contains the service profile template for which you want to set the management IP address. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Click the service profile template for which you want to set the management IP address. In the Work pane, click the General tab. Step 6 Step 7 Expand the Management IP Address area. In the Management IP Address Policy field, click one of the following radio buttons: • None—No management IP address is assigned to the service profile. The management IP address is set based on the CIMC management IP address settings on the server. • Pooled—A management IP address is assigned to the service profile from the management IP address pool. Step 8 Click Save Changes. Configuring the Management IP Pool Management IP Pool The management IP pool is a collection of external IP addresses. Cisco UCS Manager reserves each block of IP addresses in the management IP pool for external access that terminates in the CIMC on a server. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 377 Configuring the Management IP Pool You can configure service profiles and service profile templates to use IP addresses from the management IP pool. You cannot configure servers to use the management IP pool. All IP addresses in the management IP pool must be in the same subnet as the IP address of the fabric interconnect. Note The management IP pool must not contain any IP addresses that have been assigned as static IP addresses for a server or service profile. Creating an IP Address Block in the Management IP Pool The management IP pool must not contain any IP addresses that have been assigned as static IP addresses for a server or service profile. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 In the Admin tab, expand All > Communication Services. Right-click Management IP Pool (ext-mgmt) and select Create Block of IP Addresses. In the Create a Block of IP Addresses dialog box, complete the following fields: Name Description From field The first IP address in the block. Size field The number of IP addresses in the pool. Subnet Mask field The subnet mask associated with the IP addresses in the block. All IP addresses in the management IP pool must be in the same subnet as the IP address of the fabric interconnect. Default Gateway field Step 5 The default gateway associated with the IP addresses in the block. Click OK. What to Do Next Configure one or more service profiles or service profile templates to obtain the CIMC IP address from the management IP pool. Cisco UCS Manager GUI Configuration Guide, Release 2.0 378 OL-25712-04 Configuring the Management IP Pool Deleting an IP Address Block from the Management IP Pool Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 In the Admin tab, expand All > Communication Services > Management IP Pool (ext-mgmt). Right-click the IP address block that you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 379 Configuring the Management IP Pool Cisco UCS Manager GUI Configuration Guide, Release 2.0 380 OL-25712-04 CHAPTER 29 Configuring Server-Related Policies This chapter includes the following sections: • Configuring BIOS Settings, page 381 • Configuring IPMI Access Profiles, page 405 • Configuring Local Disk Configuration Policies, page 407 • Configuring Scrub Policies, page 413 • Configuring Serial over LAN Policies, page 415 • Configuring Server Autoconfiguration Policies, page 417 • Configuring Server Discovery Policies, page 419 • Configuring Server Inheritance Policies, page 420 • Configuring Server Pool Policies, page 422 • Configuring Server Pool Policy Qualifications, page 423 • Configuring vNIC/vHBA Placement Policies, page 429 Configuring BIOS Settings Server BIOS Settings Cisco UCS provides two methods for making global modifications to the BIOS settings on servers in an Cisco UCS domain. You can create one or more BIOS policies that include a specific grouping of BIOS settings that match the needs of a server or set of servers, or you can use the default BIOS settings for a specific server platform. Both the BIOS policy and the default BIOS settings for a server platform enable you to fine tune the BIOS settings for a server managed by Cisco UCS Manager. Depending upon the needs of the data center, you can configure BIOS policies for some service profiles and use the BIOS defaults in other service profiles in the same Cisco UCS domain, or you can use only one of them. You can also use Cisco UCS Manager to view the actual BIOS settings on a server and determine whether they are meeting current needs. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 381 Configuring BIOS Settings Note Cisco UCS Manager pushes BIOS configuration changes through a BIOS policy or default BIOS settings to the Cisco Integrated Management Controller (CIMC) buffer. These changes remain in the buffer and do not take effect until the server is rebooted. We recommend that you verify the support for BIOS settings in the server that you want to configure. Some settings, such as Mirroring Mode and Sparing Mode for RAS Memory, are not supported by all Cisco UCS servers. Main BIOS Settings The following table lists the main server BIOS settings that you can configure through a BIOS policy or the default BIOS settings: Name Description Reboot on BIOS Settings Change When the server is rebooted after you change one or more BIOS settings. If you enable this setting, the server is rebooted according to the maintenance policy in the server's service profile. For example, if the maintenance policy requires user acknowledgment, the server is not rebooted and the BIOS changes are not applied until a user acknowledges the pending activity. If you do not enable this setting, the BIOS changes are not applied until the next time the server is rebooted, whether as a result of another server configuration change or a manual reboot. Quiet Boot What the BIOS displays during Power On Self-Test (POST). This can be one of the following: • disabled—The BIOS displays all messages and Option ROM information during boot. • enabled—The BIOS displays the logo screen, but does not display any messages or Option ROM information during boot. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Cisco UCS Manager GUI Configuration Guide, Release 2.0 382 OL-25712-04 Configuring BIOS Settings Name Description Post Error Pause What happens when the server encounters a critical error during POST. This can be one of the following: • disabled—The BIOS continues to attempt to boot the server. • enabled—The BIOS pauses the attempt to boot the server and opens the Error Manager when a critical error occurs during POST. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Resume Ac On Power Loss How the server behaves when power is restored after an unexpected power loss. This can be one of the following: • stay-off—The server remains off until manually powered on. • last-state—The server is powered on and the system attempts to restore its last state. • reset—The server is powered on and automatically reset. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Front Panel Lockout Whether the power and reset buttons on the front panel are ignored by the server. This can be one of the following: • disabled—The power and reset buttons on the front panel are active and can be used to affect the server. • enabled—The power and reset buttons are locked out. The server can only be reset or powered on or off from the CIMC GUI. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 383 Configuring BIOS Settings Name Description ACPI10 Support Whether the BIOS publishes the ACPI 1.0 version of FADT in the Root System Description table. This version may be required for compatibility with OS versions that only support ACPI 1.0. This can be one of the following: • disabled—ACPI 1.0 version is not published. • enabled—ACPI 1.0 version is published. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Processor BIOS Settings The following table lists the processor BIOS settings that you can configure through a BIOS policy or the default BIOS settings: Name Description Turbo Boost Whether the processor uses Intel Turbo Boost Technology, which allows the processor to automatically increase its frequency if it is running below power, temperature, or voltage specifications. This can be one of the following: • disabled—The processor does not increase its frequency automatically. • enabled—The processor utilizes Turbo Boost Technology if required. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Cisco UCS Manager GUI Configuration Guide, Release 2.0 384 OL-25712-04 Configuring BIOS Settings Name Description Enhanced Intel Speedstep Whether the processor uses Enhanced Intel SpeedStep Technology, which allows the system to dynamically adjust processor voltage and core frequency. This technology can result in decreased average power consumption and decreased average heat production. This can be one of the following: • disabled—The processor never dynamically adjusts its voltage or frequency. • enabled—The processor utilizes Enhanced Intel SpeedStep Technology and enables all supported processor sleep states to further conserve power. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. We recommend that you contact your operating system vendor to make sure the operating system supports this feature. Hyper Threading Whether the processor uses Intel Hyper-Threading Technology, which allows multithreaded software applications to execute threads in parallel within each processor. This can be one of the following: • disabled—The processor does not permit hyperthreading. • enabled—The processor allows for the parallel execution of multiple threads. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. We recommend that you contact your operating system vendor to make sure the operating system supports this feature. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 385 Configuring BIOS Settings Name Description Core Multi Processing Sets the state of logical processor cores in a package. If you disable this setting, Hyper Threading is also disabled. This can be one of the following: • all—Enables multi processing on all logical processor cores. • 1 through 10—Specifies the number of logical processor cores that can run on the server. To disable multi processing and have only one logical processor core running on the server, select 1. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. We recommend that you contact your operating system vendor to make sure the operating system supports this feature. Execute Disabled Bit Classifies memory areas on the server to specify where where application code can execute. As a result of this classification, the processor disables code execution if a malicious worm attempts to insert code in the buffer. This setting helps to prevent damage, worm propagation, and certain classes of malicious buffer overflow attacks. This can be one of the following: • disabled—The processor does not classify memory areas. • enabled—The processor classifies memory areas. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. We recommend that you contact your operating system vendor to make sure the operating system supports this feature. Virtualization Technology (VT) Whether the processor uses Intel Virtualization Technology, which allows a platform to run multiple operating systems and applications in independent partitions. This can be one of the following: • disabled—The processor does not permit virtualization. • enabled—The processor allows multiple operating systems in independent partitions. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Note If you change this option, you must power cycle the server before the setting takes effect. Cisco UCS Manager GUI Configuration Guide, Release 2.0 386 OL-25712-04 Configuring BIOS Settings Name Description Direct Cache Access Allows processors to increase I/O performance by placing data from I/O devices directly into the processor cache. This setting helps to reduce cache misses. This can be one of the following: • disabled—Data from I/O devices is not placed directly into the processor cache. • enabled—Data from I/O devices is placed directly into the processor cache. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Processor C State Whether the system can enter a power savings mode during idle periods. This can be one of the following: • disabled—The system remains in high performance state even when idle. • enabled—The system can reduce power to system components such as the DIMMs and CPUs. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. We recommend that you contact your operating system vendor to make sure the operating system supports this feature. Processor C1E Allows the processor to transition to its minimum frequency upon entering C1. This setting does not take effect until after you have rebooted the server. This can be one of the following: • disabled—The CPU continues to run at its maximum frequency in C1 state. • enabled—The CPU transitions to its minimum frequency. This option saves the maximum amount of power in C1 state. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 387 Configuring BIOS Settings Name Description Processor C3 Report Whether the processor sends the C3 report to the operating system. This can be one of the following: • disabled—The processor does not send the C3 report. • acpi-c2—The processor sends the C3 report using the ACPI C2 format. • acpi-c3—The processor sends the C3 report using the ACPI C3 format. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. On the B440 server, the BIOS Setup menu uses enabled and disabled for these options. If you specify acpi-c2 or acpi-c2, the server sets the BIOS value for that option to enabled. Processor C6 Report Whether the processor sends the C6 report to the operating system. This can be one of the following: • disabled—The processor does not send the C6 report. • enabled—The processor sends the C6 report. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Processor C7 Report Whether the processor sends the C7 report to the operating system. This can be one of the following: • disabled—The processor does not send the C7 report. • enabled—The processor sends the C7 report. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Cisco UCS Manager GUI Configuration Guide, Release 2.0 388 OL-25712-04 Configuring BIOS Settings Name Description CPU Performance Sets the CPU performance profile for the server. This can be one of the following: • enterprise—All prefetchers and data reuse are disabled. • high-throughput—All prefetchers are enabled, and data reuse is disabled. • hpc—All prefetchers and data reuse are enabled. This setting is also known as high performance computing. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Max Variable MTRR Setting Allows you to select the number of MTRR variables. This can be one of the following: • auto-max—The BIOS uses the default value for the processor. • 8—The BIOS uses the number specified for the variable MTRR. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 389 Configuring BIOS Settings Name Description Package C State Limit The amount of power available to the server components when they are idle. This can be one of the following: • c0—The server provides all server components with full power at all times. This option maintains the highest level of performance and requires the greatest amount of power. • c1—When the CPU is idle, the system slightly reduces the power consumption. This option requires less power than C0 and allows the server to return quickly to high performance mode. • c3—When the CPU is idle, the system reduces the power consumption further than with the C1 option. This requires less power than C1 or C0, but it takes the server slightly longer to return to high performance mode. • c6—When the CPU is idle, the system reduces the power consumption further than with the C3 option. This option saves more power than C0, C1, or C3, but there may be performance issues until the server returns to full power. • no-limit—The server may enter any available C state. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Intel Directed I/O BIOS Settings The following table lists the Intel Directed I/O BIOS settings that you can configure through a BIOS policy or the default BIOS settings: Name Description VT for Directed IO Whether the processor uses Intel Virtualization Technology for Directed I/O (VT-d). This can be one of the following: • disabled—The processor does not use virtualization technology. • enabled—The processor uses virtualization technology. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Note This option must be enabled if you want to change any of the other Intel Directed I/O BIOS settings. Cisco UCS Manager GUI Configuration Guide, Release 2.0 390 OL-25712-04 Configuring BIOS Settings Name Description Interrupt Remap Whether the processor supports Intel VT-d Interrupt Remapping. This can be one of the following: • disabled—The processor does not support remapping. • enabled—The processor uses VT-d Interrupt Remapping as required. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Coherency Support Whether the processor supports Intel VT-d Coherency. This can be one of the following: • disabled—The processor does not support coherency. • enabled—The processor uses VT-d Coherency as required. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. ATS Support Whether the processor supports Intel VT-d Address Translation Services (ATS). This can be one of the following: • disabled—The processor does not support ATS. • enabled—The processor uses VT-d ATS as required. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Pass Through DMA Support Whether the processor supports Intel VT-d Pass-through DMA. This can be one of the following: • disabled—The processor does not support pass-through DMA. • enabled—The processor uses VT-d Pass-through DMA as required. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 391 Configuring BIOS Settings RAS Memory BIOS Settings The following table lists the RAS memory BIOS settings that you can configure through a BIOS policy or the default BIOS settings: Name Description Memory RAS Config How the memory reliability, availability, and serviceability (RAS) is configured for the server. This can be one of the following: • maximum performance—System performance is optimized. • mirroring—System reliability is optimized by using half the system memory as backup. • lockstep—If the DIMM pairs in the server have an identical type, size, and organization and are populated across the SMI channels, you can enable lockstep mode to minimize memory access latency and provide better performance. Lockstep is enabled by default for B440 servers. • sparing—System reliability is enhanced with a degree of memory redundancy while making more memory available to the operating system than mirroring. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. NUMA Whether the BIOS supports NUMA. This can be one of the following: • disabled—The BIOS does not support NUMA. • enabled—The BIOS includes the ACPI tables that are required for NUMA-aware operating systems. If you enable this option, the system must disable Inter-Socket Memory interleaving on some platforms. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Cisco UCS Manager GUI Configuration Guide, Release 2.0 392 OL-25712-04 Configuring BIOS Settings Name Description Mirroring Mode Memory mirroring enhances system reliability by keeping two identical data images in memory. This option is only available if you choose the mirroring option for Memory RAS Config. It can be one of the following: • inter-socket—Memory is mirrored between two Integrated Memory Controllers (IMCs) across CPU sockets. • intra-socket—One IMC is mirrored with another IMC in the same socket. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Sparing Mode Sparing optimizes reliability by holding memory in reserve so that it can be used in case other DIMMs fail. This option provides some memory redundancy, but does not provide as much redundancy as mirroring. The available sparing modes depend on the current memory population. This option is only available if you choose sparing option for Memory RAS Config. It can be one of the following: • dimm-sparing—One DIMM is held in reserve. If a DIMM fails, the contents of a failing DIMM are transferred to the spare DIMM. • rank-sparing—A spare rank of DIMMs is held in reserve. If a rank of DIMMs fails, the contents of the failing rank are transferred to the spare rank. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. LV DDR Mode Whether the system prioritizes low voltage or high frequency memory operations. This can be one of the following: • power-saving-mode—The system prioritizes low voltage memory operations over high frequency memory operations. This mode may lower memory frequency in order to keep the voltage low. • performance-mode—The system prioritizes high frequency operations over low voltage operations. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 393 Configuring BIOS Settings Serial Port BIOS Settings The following table lists the serial port BIOS settings that you can configure through a BIOS policy or the default BIOS settings: Name Description Serial Port A Whether serial port A is enabled or disabled. This can be one of the following: • disabled—The serial port is disabled. • enabled—The serial port is enabled. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. USB BIOS Settings The following table lists the USB BIOS settings that you can configure through a BIOS policy or the default BIOS settings: Name Description Make Device Non Bootable Whether the server can boot from a USB device. This can be one of the following: • disabled—The server can boot from a USB device. • enabled—The server cannot boot from a USB device. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Cisco UCS Manager GUI Configuration Guide, Release 2.0 394 OL-25712-04 Configuring BIOS Settings Name Description USB System Idle Power Optimizing Setting Whether the USB System Idle Power Optimizing setting is used to reduce USB EHCI idle power consumption. Depending upon the value you choose, this setting can have an impact on performance. This can be one of the following: • high-performance—The USB System Idle Power Optimizing setting is disabled, because optimal performance is preferred over power savings. Selecting this option can significantly improve performance. We recommend you select this option unless your site has server power restrictions. • lower-idle-power—The USB System Idle Power Optimizing setting is enabled, because power savings are preferred over optimal performance. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. USB Front Panel Access Lock USB front panel lock is configured to enable or disable the front panel access to USB ports. This can be one of the following: • disabled • enabled • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. PCI Configuration BIOS Settings The following table lists the PCI configuration BIOS settings that you can configure through a BIOS policy or the default BIOS settings: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 395 Configuring BIOS Settings Name Description Max Memory Below 4G Whether the BIOS maximizes memory usage below 4GB for an operating system without PAE support, depending on the system configuration. This can be one of the following: • disabled—Does not maximize memory usage. Choose this option for all operating systems with PAE support. • enabled—Maximizes memory usage below 4GB for an operating system without PAE support. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Memory Mapped IO Above 4Gb Config Whether to enable or disable memory mapped I/O of 64-bit PCI devices to 4GB or greater address space. Legacy option ROMs are not able to access addresses above 4GB. PCI devices that are 64-bit compliant but use a legacy option ROM may not function correctly with this setting enabled. This can be one of the following: • disabled—Does not map I/O of 64-bit PCI devices to 4GB or greater address space. • enabled—Maps I/O of 64-bit PCI devices to 4GB or greater address space. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Boot Options BIOS Settings The following table lists the boot options BIOS settings that you can configure through a BIOS policy or the default BIOS settings: Name Description Boot Option Retry Whether the BIOS retries NON-EFI based boot options without waiting for user input. This can be one of the following: • disabled—Waits for user input before retrying NON-EFI based boot options. • enabled—Continually retries NON-EFI based boot options without waiting for user input. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Cisco UCS Manager GUI Configuration Guide, Release 2.0 396 OL-25712-04 Configuring BIOS Settings Name Description Intel Entry SAS RAID Whether the Intel SAS Entry RAID Module is enabled. This can be one of the following: • disabled—The Intel SAS Entry RAID Module is disabled. • enabled—The Intel SAS Entry RAID Module is enabled. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Intel Entry SAS RAID Module How the Intel SAS Entry RAID Module is configured. This can be one of the following: • it-ir-raid—Configures the RAID module to use Intel IT/IR RAID. • intel-esrtii—Configures the RAID module to use Intel Embedded Server RAID Technology II. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Onboard SCU Storage Support Whether the onboard software RAID controller is available to the server. This can be one of the following: • disabled—The software RAID controller is not available. • enabled—The software RAID controller is available. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Server Management BIOS Settings The following tables list the server management BIOS settings that you can configure through a BIOS policy or the default BIOS settings: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 397 Configuring BIOS Settings General Settings Name Description Assert Nmi on Serr Whether the BIOS generates a non-maskable interrupt (NMI) and logs an error when a system error (SERR) occurs. This can be one of the following: • disabled—The BIOS does not generate an NMI or log an error when a SERR occurs. • enabled—The BIOS generates an NMI and logs an error when a SERR occurs. You must enable this setting if you want to enable Assert Nmi on Perr. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Assert Nmi on Perr Whether the BIOS generates a non-maskable interrupt (NMI) and logs an error when a processor bus parity error (PERR) occurs. This can be one of the following: • disabled—The BIOS does not generate an NMI or log an error when a PERR occurs. • enabled—The BIOS generates an NMI and logs an error when a PERR occurs. You must enable Assert Nmi on Serr to use this setting. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. OS Boot Watchdog Timer Whether the BIOS programs the watchdog timer with a predefined timeout value. If the operating system does not complete booting before the timer expires, the CIMC resets the system and an error is logged. This can be one of the following: • disabled—The watchdog timer is not used to track how long the server takes to boot. • enabled—The watchdog timer tracks how long the server takes to boot. If the server does not boot within the predefined length of time, the CIMC resets the system and logs an error. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. This feature requires either operating system support or Intel Management software. Cisco UCS Manager GUI Configuration Guide, Release 2.0 398 OL-25712-04 Configuring BIOS Settings Name Description OS Boot Watchdog Timer Timeout Policy What action the system takes if the watchdog timer expires. This can be one of the following: • power-off—The server is powered off if the watchdog timer expires during OS boot. • reset—The server is reset if the watchdog timer expires during OS boot. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. This option is only available if you enable the OS Boot Watchdog Timer. OS Boot Watchdog Timer Timeout What timeout value the BIOS uses to configure the watchdog timer. This can be one of the following: • 5-minutes—The watchdog timer expires 5 minutes after the OS begins to boot. • 10-minutes—The watchdog timer expires 10 minutes after the OS begins to boot. • 15-minutes—The watchdog timer expires 15 minutes after the OS begins to boot. • 20-minutes—The watchdog timer expires 20 minutes after the OS begins to boot. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. This option is only available if you enable the OS Boot Watchdog Timer. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 399 Configuring BIOS Settings Console Redirection Settings Name Description Console Redirection Allows a serial port to be used for console redirection during POST and BIOS booting. After the BIOS has booted and the operating system is responsible for the server, console redirection is irrelevant and has no effect. This can be one of the following: • disabled—No console redirection occurs during POST. • serial-port-a—Enables serial port A for console redirection during POST. This option is valid for blade servers and rack-mount servers. • serial-port-b—Enables serial port B for console redirection and allows it to perform server management tasks. This option is only valid for rack-mount servers. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Note Flow Control If you enable this option, you also disable the display of the Quiet Boot logo screen during POST. Whether a handshake protocol is used for flow control. Request to Send / Clear to Send (RTS/CTS) helps to reduce frame collisions that can be introduced by a hidden terminal problem. This can be one of the following: • none—No flow control is used. • rts-cts—RTS/CTS is used for flow control. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Note This setting must match the setting on the remote terminal application. Cisco UCS Manager GUI Configuration Guide, Release 2.0 400 OL-25712-04 Configuring BIOS Settings Name Description BAUD Rate What BAUD rate is used for the serial port transmission speed. If you disable Console Redirection, this option is not available. This can be one of the following: • 9600—A 9600 BAUD rate is used. • 19200—A 19200 BAUD rate is used. • 38400—A 38400 BAUD rate is used. • 57600—A 57600 BAUD rate is used. • 115200—A 115200 BAUD rate is used. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Note Terminal Type This setting must match the setting on the remote terminal application. What type of character formatting is used for console redirection. This can be one of the following: • pc-ansi—The PC-ANSI terminal font is used. • vt100—A supported vt100 video terminal and its character set are used. • vt100-plus—A supported vt100-plus video terminal and its character set are used. • vt-utf8—A video terminal with the UTF-8 character set is used. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Note Legacy OS Redirect This setting must match the setting on the remote terminal application. Whether redirection from a legacy operating system, such as DOS, is enabled on the serial port. This can be one of the following: • disabled—The serial port enabled for console redirection is hidden from the legacy operating system. • enabled— The serial port enabled for console redirection is visible to the legacy operating system. • Platform Default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 401 Configuring BIOS Settings BIOS Policy The BIOS policy is a policy that automates the configuration of BIOS settings for a server or group of servers. You can create global BIOS policies available to all servers in the root organization, or you can create BIOS policies in sub-organizations that are only available to that hierarchy. To use a BIOS policy, do the following: 1 Create the BIOS policy in Cisco UCS Manager. 2 Assign the BIOS policy to one or more service profiles. 3 Associate the service profile with a server. During service profile association, Cisco UCS Manager modifies the BIOS settings on the server to match the configuration in the BIOS policy. If you do not create and assign a BIOS policy to a service profile, the server uses the default BIOS settings for that server platform. Default BIOS Settings Cisco UCS Manager includes a set of default BIOS settings for each type of server supported by Cisco UCS. The default BIOS settings are available only in the root organization and are global. Only one set of default BIOS settings can exist for each server platform supported by Cisco UCS. You can modify the default BIOS settings, but you cannot create an additional set of default BIOS settings. Each set of default BIOS settings are designed for a particular type of supported server and are applied to all servers of that specific type which do not have a BIOS policy included in their service profiles. Unless a Cisco UCS implementation has specific needs that are not met by the server-specific settings, we recommend that you use the default BIOS settings that are designed for each type of server in the Cisco UCS domain. Cisco UCS Manager applies these server platform-specific BIOS settings as follows: • The service profile associated with a server does not include a BIOS policy. • The BIOS policy is configured with the platform-default option for a specific setting. You can modify the default BIOS settings provided by Cisco UCS Manager. However, any changes to the default BIOS settings apply to all servers of that particular type or platform. If you want to modify the BIOS settings for only certain servers, we recommend that you use a BIOS policy. Cisco UCS Manager GUI Configuration Guide, Release 2.0 402 OL-25712-04 Configuring BIOS Settings Creating a BIOS Policy Note Cisco UCS Manager pushes BIOS configuration changes through a BIOS policy or default BIOS settings to the Cisco Integrated Management Controller (CIMC) buffer. These changes remain in the buffer and do not take effect until the server is rebooted. We recommend that you verify the support for BIOS settings in the server that you want to configure. Some settings, such as Mirroring Mode and Sparing Mode for RAS Memory, are not supported by all Cisco UCS servers. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click BIOS Policies and select Create BIOS Policy. On the Main page of the Create BIOS Policy wizard, enter a name for the BIOS policy in the Name field. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Step 6 In the Create BIOS Policy wizard, do the following to configure the BIOS settings: a) If you want to change a BIOS setting, click the desired radio button or make the appropriate choice from the drop-down list. For descriptions and information about the options for each BIOS setting, see the following topics: • Main page: Main BIOS Settings, on page 382 • Processor page: Processor BIOS Settings, on page 384 • Intel Directed IO page: Intel Directed I/O BIOS Settings, on page 390 • RAS Memory page: RAS Memory BIOS Settings, on page 392 • Serial Port page: Serial Port BIOS Settings, on page 394 • USB page: USB BIOS Settings, on page 394 • PCI Configuration page: PCI Configuration BIOS Settings, on page 395 • Boot Options page: Boot Options BIOS Settings, on page 396 • Server Management page: Server Management BIOS Settings, on page 397 b) Click Next after each page to move to the Step 7 After you have configured all of the BIOS settings for the policy, click Finish. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 403 Configuring BIOS Settings Modifying the BIOS Defaults We recommend that you verify the support for BIOS settings in the server that you want to configure. Some settings, such as Mirroring Mode and Sparing Mode for RAS Memory, are not supported by all Cisco UCS servers. Unless a Cisco UCS implementation has specific needs that are not met by the server-specific settings, we recommend that you use the default BIOS settings that are designed for each type of server in the Cisco UCS domain. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Step 4 Expand BIOS Defaults and select the server model number for which you want to modify the default BIOS settings. In the Work pane, click the appropriate tab and then click the desired radio button or make a choice from the drop-down list to modify the defult BIOS settings: For descriptions and information about the options for each BIOS setting, see the following topics. Not all BIOS settings are available for each type of server. Step 5 Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. • Main tab: Main BIOS Settings, on page 382 • Advanced tab: ◦ Processor subtab: Processor BIOS Settings, on page 384 ◦ Intel Directed IO subtab: Intel Directed I/O BIOS Settings, on page 390 ◦ RAS Memory subtab: RAS Memory BIOS Settings, on page 392 ◦ Serial Port subtab: Serial Port BIOS Settings, on page 394 ◦ USB subtab: USB BIOS Settings, on page 394 ◦ PCI Configuration subtab: PCI Configuration BIOS Settings, on page 395 • Boot Options tab: Boot Options BIOS Settings, on page 396 • Server Management tab: Server Management BIOS Settings, on page 397 Step 6 Click Save Changes. Viewing the Actual BIOS Settings for a Server Follow this procedure to see the actual BIOS settings on a server. Cisco UCS Manager GUI Configuration Guide, Release 2.0 404 OL-25712-04 Configuring IPMI Access Profiles Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server for which you want to view the actual BIOS settings. On the Work pane, click the Inventory tab. Step 5 Step 6 Click the Motherboard subtab. In the BIOS Settings area, click the Expand icon to the right of the heading to open that area. Each tab in the BIOS Settings area displays the settings for that server platform. Some of the tabs contain subtabs with additional information. Configuring IPMI Access Profiles IPMI Access Profile This policy allows you to determine whether IPMI commands can be sent directly to the server, using the IP address. For example, you can send commands to retrieve sensor data from the CIMC. This policy defines the IPMI access, including a username and password that can be authenticated locally on the server, and whether the access is read-only or read-write. You must include this policy in a service profile and that service profile must be associated with a server for it to take effect. Creating an IPMI Access Profile Before You Begin An IPMI profile requires that one or more of the following resources already exist in the system: • Username with appropriate permissions that can be authenticated by the operating system of the server • Password for the username • Permissions associated with the username Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click IPMI Profiles and select Create IPMI Profiles. In the Create IPMI Profile dialog box: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 405 Configuring IPMI Access Profiles a) Enter a unique name and description for the profile. b) Click OK. Step 6 Step 7 In the IPMI Profile Users area of the navigator, click +. In the User Properties dialog box: a) Complete the following fields: Name Description Name field The username to associate with this IPMI profile. Enter 1 to 16 alphanumeric characters. You can also use @ (at sign), _ (underscore), and - (hyphen). You cannot change this name once the profile has been saved. Password field The password associated with this username. Enter 1 to 20 standard ASCII characters, except for = (equal sign), $ (dollar sign), and | (vertical bar). Confirm Password field The password a second time for confirmation purposes. Role field The user role. This can be one of the following: • Admin • Read Only b) Click OK. Step 8 Step 9 Repeat Steps 6 and 7 to add another user. Click OK to return to the IPMI profiles in the Work pane. What to Do Next Include the IPMI profile in a service profile and/or template. Deleting an IPMI Access Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 In the Servers tab, expand Servers > Policies > Organization_Name Expand the IPMI Profiles node. Right-click the profile you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 406 OL-25712-04 Configuring Local Disk Configuration Policies Configuring Local Disk Configuration Policies Local Disk Configuration Policy This policy configures any optional SAS local drives that have been installed on a server through the onboard RAID controller of the local drive. This policy enables you to set a local disk mode for all servers that are associated with a service profile that includes the local disk configuration policy. The local disk modes include the following: • No Local Storage—For a diskless server or a SAN only configuration. If you select this option, you cannot associate any service profile which uses this policy with a server that has a local disk. • RAID 0 Striped—Data is striped across all disks in the array, providing fast throughput. There is no data redundancy, and all data is lost if any disk fails. • RAID 1 Mirrored—Data is written to two disks, providing complete data redundancy if one disk fails. The maximum array size is equal to the available space on the smaller of the two drives. • Any Configuration—For a server configuration that carries forward the local disk configuration without any changes. • No RAID—For a server configuration that removes the RAID and leaves the disk MBR and payload unaltered. • RAID 5 Striped Parity—Data is striped across all disks in the array. Part of the capacity of each disk stores parity information that can be used to reconstruct data if a disk fails. RAID 5 provides good data throughput for applications with high read request rates. • RAID 6 Striped Dual Parity—Data is striped across all disks in the array and two parity disks are used to provide protection against the failure of up to two physical disks. In each row of data blocks, two sets of parity data are stored. • RAID10 Mirrored and Striped— RAID 10 uses mirrored pairs of disks to provide complete data redundancy and high throughput rates. You must include this policy in a service profile, and that service profile must be associated with a server for the policy to take effect. Guidelines for all Local Disk Configuration Policies Before you create a local disk configuration policy, consider the following guidelines: No Mixed HDDs and SSDs Do not include HDDs and SSDs in a single server or RAID configuration. Do Not Assign a Service Profile with the Default Local Disk Configuration Policy from a B200 M1 or M2 to a B200 M3 Due to the differences in the RAID/JBOD support provided by the storage controllers of B200 M1 and M2 servers and those of the B200 M3 server, you cannot assign or re-assign a service profile that includes the default local disk configuration policy from a B200M1 or M2 server to a B200 M3 server. The default local disk configuration policy includes those with Any Configuration or JBOD configuration. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 407 Configuring Local Disk Configuration Policies Impact of Upgrade from a Release Prior to Release 1.3(1i) An upgrade from an earlier Cisco UCS firmware release to release 1.3(1i) or higher has the following impact on the Protect Configuration property of the local disk configuration policy the first time servers are associated with service profiles after the upgrade: Unassociated Servers After you upgrade the Cisco UCS domain, the initial server association proceeds without configuration errors whether or not the local disk configuration policy matches the server hardware. Even if you enable the Protect Configuration property, Cisco UCS does not protect the user data on the server if there are configuration mismatches between the local disk configuration policy on the previous service profile and the policy in the new service profile. Note If you enable the Protect Configuration property and the local disk configuration policy encounters mismatches between the previous service profile and the new service profile, all subsequent service profile associations with the server are blocked. Associated Servers Any servers that are already associated with service profiles do not reboot after the upgrade. Cisco UCS Manager does not report any configuration errors if there is a mismatch between the local disk configuration policy and the server hardware. When a service profile is disassociated from a server and a new service profile associated, the setting for the Protect Configuration property in the new service profile takes precedence and overwrites the setting in the previous service profile. Guidelines for Local Disk Configuration Policies Configured for RAID No Mixed HDDs and SSDs Do not include HDDs and SSDs in a single RAID configuration. Do Not Use the Any Configuration Mode on Servers with MegaRAID Storage Controllers If a blade server or rack-mount server in a Cisco UCS domain includes a MegaRAID storage controller, do not configure the local disk configuration policy in the service profile for that server with the Any Configuration mode. If you use this mode for servers with a MegaRAID storage controller, the installer for the operating system cannot detect any local storage on the server. If you want to install an operating system on local storage on a server with a MegaRAID storage controller, you must configure the local disk configuration policy with a mode that creates a RAID LUN (RAID volume) on the server. Server May Not Boot After RAID1 Cluster Migration if Any Configuration Mode Specified in Service Profile After RAID1 clusters are migrated, you need to associate a service profile with the server. If the local disk configuration policy in the service profile is configured with Any Configuration mode rather than RAID1, the RAID LUN remains in "inactive" state during and after association. As a result, the server cannot boot. Cisco UCS Manager GUI Configuration Guide, Release 2.0 408 OL-25712-04 Configuring Local Disk Configuration Policies To avoid this issue, ensure that the service profile you associate with the server contains the identical local disk configuration policy as the original service profile before the migration and does not include the Any Configuration mode. Configure RAID Settings in Local Disk Configuration Policy for Servers with MegaRAID Storage Controllers If a blade server or integrated rack-mount server has a MegaRAID controller, you must configure RAID settings for the drives in the Local Disk Configuration policy included in the service profile for that server. If you do not configure your RAID LUNs before installing the OS, disk discovery failures might occur during the installation and you might see error messages such as “No Device Found.” Do Not Use JBOD Mode on Servers with MegaRAID Storage Controllers Do not configure or use JBOD mode or JBOD operations on any blade server or integrated rack-mount server with a MegaRAID storage controllers. JBOD mode and operations are not intended for nor are they fully functional on these servers. Maximum of One RAID Volume and One RAID Controller in Integrated Rack-Mount Servers A rack-mount server that has been integrated with Cisco UCS Manager can have a maximum of one RAID volume irrespective of how many hard drives are present on the server. All the local hard drives in an integrated rack-mount server must be connected to only one RAID Controller. Integration with Cisco UCS Manager does not support the connection of local hard drives to multiple RAID Controllers in a single rack-mount server. We therefore recommend that you request a single RAID Controller configuration when you order rack-mount servers to be integrated with Cisco UCS Manager. In addition, do not use third party tools to create multiple RAID LUNs on rack-mount servers. Cisco UCS Manager does not support that configuration. Maximum of One RAID Volume and One RAID Controller in Blade Servers A blade server can have a maximum of one RAID volume irrespective of how many drives are present in the server. All the local hard drives must be connected to only one RAID controller. For example, a B200 M3 server has an LSI controller and an Intel Patsburg controller, but only the LSI controller can be used as a RAID controller. In addition, do not use third party tools to create multiple RAID LUNs on blade servers. Cisco UCS Manager does not support that configuration. Number of Disks Selected in Mirrored RAID Should Not Exceed Two If the number of disks selected in the Mirrored RAID exceed two, RAID 1 is created as a RAID 10 LUN. This issue can occur with the Cisco UCS B440 M1 and B440 M2 servers. B420 M3 Server Does Not Support All Configuration Modes The B420 M3 server does not support the following configuration modes in a local disk configuration policy: • No RAID • RAID 6 Striped Dual Parity In addition, the B420 M3 does not support JBOD modes or operations. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 409 Configuring Local Disk Configuration Policies Creating a Local Disk Configuration Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click Local Disk Config Policies and choose Create Local Disk Configuration Policy. In the Create Local Disk Configuration Policy dialog box, complete the following fields: Name Description Name field The name of the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A description of the policy. We recommend that you include information about where and when the policy should be used. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Cisco UCS Manager GUI Configuration Guide, Release 2.0 410 OL-25712-04 Configuring Local Disk Configuration Policies Name Description Mode drop-down list This can be one of the following local disk policy modes: • No Local Storage—For a diskless server or a SAN only configuration. If you select this option, you cannot associate any service profile which uses this policy with a server that has a local disk. • RAID 0 Striped—Data is striped across all disks in the array, providing fast throughput. There is no data redundancy, and all data is lost if any disk fails. • RAID 1 Mirrored—Data is written to two disks, providing complete data redundancy if one disk fails. The maximum array size is equal to the available space on the smaller of the two drives. • Any Configuration—For a server configuration that carries forward the local disk configuration without any changes. • No RAID—For a server configuration that removes the RAID and leaves the disk MBR and payload unaltered. • RAID 5 Striped Parity—Data is striped across all disks in the array. Part of the capacity of each disk stores parity information that can be used to reconstruct data if a disk fails. RAID 5 provides good data throughput for applications with high read request rates. • RAID 6 Striped Dual Parity—Data is striped across all disks in the array and two parity disks are used to provide protection against the failure of up to two physical disks. In each row of data blocks, two sets of parity data are stored. • RAID10 Mirrored and Striped— RAID 10 uses mirrored pairs of disks to provide complete data redundancy and high throughput rates. Note If you choose No RAID and you apply this policy to a server that already has an operating system with RAID storage configured, the system does not remove the disk contents. Therefore, there may be no visible differences on the server after you apply the No RAID mode. This can lead to a mismatch between the RAID configuration in the policy and the actual disk configuration shown in the Inventory > Storage tab for the server. To make sure that any previous RAID configuration information is removed from a disk, apply a scrub policy that removes all disk information after you apply the No RAID configuration mode. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 411 Configuring Local Disk Configuration Policies Name Description Protect Configuration check box If checked, the server retains the configuration in the local disk configuration policy even if the server is disassociated from the service profile. Protect Configuration becomes non-functional if one or more disks in the server are defective or faulty. This property is checked by default. Caution When a service profile is disassociated from a server and a new service profile associated, the setting for the Protect Configuration property in the new service profile takes precedence and overwrites the setting in the previous service profile. Note Step 6 If you disassociate the server from a service profile with this option enabled and then associate it with a new service profile that includes a local disk configuration policy with different properties, the server returns a configuration mismatch error and the association fails. Click OK. Changing a Local Disk Configuration Policy This procedure describes how to change a local disk configuration policy from an associated service profile. You can also change a local disk configuration policy from the Policies node of the Servers tab. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the organization that includes the service service profile with the local disk configuration policy you want to change. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Click the service profile that contains the local disk configuration policy you want to change. In the Work pane, click the Policies tab. Step 6 Step 7 In the Actions area, click Change Local Disk Configuration Policy. In the Change Local Disk Configuration Policy dialog box, choose one of the following options from the Select the Local Disk Configuration Policy drop-down list. Option Description Use a Disk Policy Select an existing local disk configuration policy from the list below this option. Cisco UCS Manager assigns this policy to the service profile. Cisco UCS Manager GUI Configuration Guide, Release 2.0 412 OL-25712-04 Configuring Scrub Policies Step 8 Step 9 Option Description Create a Local Disk Policy Enables you to create a local disk configuration policy that can only be accessed by the selected service profile. No Disk Policy Does not use a local disk configuration policy for the selected service profile. Click OK. (Optional) Expand the Local Disk Configuration Policy area to confirm that the change has been made. Deleting a Local Disk Configuration Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Servers > Policies > Organization_Name. Expand the Local Disk Config Policies node. Right-click the policy you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Configuring Scrub Policies Scrub Policy This policy determines what happens to local data and to the BIOS settings on a server during the discovery process and when the server is disassociated from a service profile. Depending upon how you configure a scrub policy, the following can occur at those times: Disk Scrub One of the following occurs to the data on any local drives on disassociation: • If enabled, destroys all data on any local drives • If disabled, preserves all data on any local drives, including local storage configuration Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 413 Configuring Scrub Policies BIOS Settings Scrub One of the following occurs to the BIOS settings when a service profile containing the scrub policy is disassociated from a server: • If enabled, erases all BIOS settings for the server and and resets them to the BIOS defaults for that server type and vendor • If disabled, preserves the existing BIOS settings on the server Creating a Scrub Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click Scrub Policies and select Create Scrub Policy. In the Create Scrub Policy wizard, complete the following fields: Name Description Name field The name of the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A description of the policy. We recommend that you include information about where and when the policy should be used. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Disk Scrub field If this field is set to Yes, when a service profile containing this scrub policy is disassociated from a server, all data on the server local drives is completely erased. If this field is set to No, the data on the local drives is preserved, including all local storage configuration. BIOS Settings Scrub field If the field is set to Yes, when a service profile containing this scrub policy is disassociated from a server, the BIOS settings for that server are erased and reset to the defaults for that server type and vendor. If this field is set to No, the BIOS settings are preserved. Cisco UCS Manager GUI Configuration Guide, Release 2.0 414 OL-25712-04 Configuring Serial over LAN Policies Step 6 Click OK. Deleting a Scrub Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Servers > Policies > Organization_Name. Expand the Scrub Policies node. Right-click the policy you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Configuring Serial over LAN Policies Serial over LAN Policy This policy sets the configuration for the serial over LAN connection for all servers associated with service profiles that use the policy. By default, the serial over LAN connection is disabled. If you implement a serial over LAN policy, we recommend that you also create an IPMI profile. You must include this policy in a service profile and that service profile must be associated with a server for it to take effect. Creating a Serial over LAN Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click Serial over LAN Policies and select Create Serial over LAN Policy. In the Create Serial over LAN Policy wizard, complete the following fields: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 415 Configuring Serial over LAN Policies Name Description Name field The name of the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A description of the policy. We recommend that you include information about where and when the policy should be used. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Serial over LAN State field This can be one of the following: • Disable—Serial over LAN access is blocked. • Enable—Serial over LAN access is permitted. Speed drop-down list This can be one of the following: • 9600 • 19200 • 38400 • 57600 • 115200 Step 6 Click OK. Deleting a Serial over LAN Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Servers > Policies > Organization_Name. Expand the Serial over LAN Policies node. Right-click the policy you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 416 OL-25712-04 Configuring Server Autoconfiguration Policies Configuring Server Autoconfiguration Policies Server Autoconfiguration Policy Cisco UCS Manager uses this policy to determine how to configure a new server. If you create a server autoconfiguration policy, the following occurs when a new server starts: 1 The qualification in the server autoconfiguration policy is executed against the server. 2 If the server meets the required qualifications, the server is associated with a service profile created from the service profile template configured in the server autoconfiguration policy. The name of that service profile is based on the name given to the server by Cisco UCS Manager. 3 The service profile is assigned to the organization configured in the server autoconfiguration policy. Creating an Autoconfiguration Policy Before You Begin This policy requires that one or more of the following resources already exist in the system: • Server pool policy qualifications • Service profile template • Organizations, if a system implements multi-tenancy Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Policies tab. Step 4 Step 5 Click the Autoconfig Policies subtab. On the icon bar to the right of the table, click +. If the + icon is disabled, click an entry in the table to enable it. Step 6 In the Create Autoconfiguration Policy dialog box, complete the following fields: Name Description Name field The name of the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 417 Configuring Server Autoconfiguration Policies Name Description Description field A description of the policy. We recommend that you include information about where and when the policy should be used. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Qualification drop-down list The server pool policy qualification associated with this auto-configuration policy. If a new server is discovered that matches the criteria specified in the server pool policy qualification, Cisco UCS automatically creates a service profile based on the service profile template selected in the Service Profile Template Name drop-down list and associates the newly created service profile with the server. Org drop-down list The organization associated with this autoconfiguration policy. If Cisco UCS automatically creates a service profile to associate with a server, it places the service profile under the organization selected in this field. Service Profile Template Name drop-down list Step 7 The service profile template associated with this policy. Click OK. Deleting an Autoconfiguration Policy Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Policies tab. Step 4 Step 5 Step 6 Click the Autoconfig Policies subtab. Right-click the autoconfiguration policy that you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 418 OL-25712-04 Configuring Server Discovery Policies Configuring Server Discovery Policies Server Discovery Policy This discovery policy determines how the system reacts when you add a new server. If you create a server discovery policy, you can control whether the system conducts a deep discovery when a server is added to a chassis, or whether a user must first acknowledge the new server. By default, the system conducts a full discovery. If you create a server discovery policy, the following occurs when a new server starts: 1 The qualification in the server discovery policy is executed against the server. 2 If the server meets the required qualifications, Cisco UCS Manager applies the following to the server: • Depending upon the option selected for the action, either discovers the new server immediately or waits for a user to acknowledge the new server • Applies the scrub policy to the server Creating a Server Discovery Policy Before You Begin If you plan to associate this policy with a server pool, create server pool policy qualifications. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Policies tab. Step 4 Step 5 Click the Server Discovery Policies subtab. Click the + icon on the table icon bar to open the Create Server Discovery Policy dialog box. Step 6 Step 7 In the Description field, enter a description for the discovery policy. In the Action field, select one of the following options: • Immediate—The system attempts to discover new servers automatically • User Acknowledged—The system waits until the user tells it to search for new servers Step 8 (Optional) To associate this policy with a server pool, select server pool policy qualifications from the Qualification drop-down list. Step 9 (Optional) To include a scrub policy, select a policy from the Scrub Policy drop-down list. Step 10 Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 419 Configuring Server Inheritance Policies What to Do Next Include the server discovery policy in a service profile and/or template. Deleting a Server Discovery Policy Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Policies tab. Step 4 Step 5 Step 6 Click the Server Discovery Policies subtab. Right-click the server discover policy that you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Configuring Server Inheritance Policies Server Inheritance Policy This policy is invoked during the server discovery process to create a service profile for the server. All service profiles created from this policy use the values burned into the blade at manufacture. The policy performs the following: • Analyzes the inventory of the server • If configured, assigns the server to the selected organization • Creates a service profile for the server with the identity burned into the server at manufacture You cannot migrate a service profile created with this policy to another server. Creating a Server Inheritance Policy A blade server or rack-mount server with a VIC adapter, such as the Cisco UCS M81KR Virtual Interface Card, does not have server identity values burned into the server hardware at manufacture. As a result, the identity of the adapter must be derived from default pools. If the default pools do not include sufficient entries for one to be assigned to the server, service profile association fails with a configuration error. Cisco UCS Manager GUI Configuration Guide, Release 2.0 420 OL-25712-04 Configuring Server Inheritance Policies Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Policies tab. Step 4 Step 5 Click the Server Inheritance Policies subtab. On the icon bar to the right of the table, click +. If the + icon is disabled, click an entry in the table to enable it. Step 6 In the Create Server Inheritance Policy dialog box, complete the following fields: Name Description Name field The name of the policy. Description field A description of the policy. We recommend that you include information about where and when the policy should be used. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Step 7 Qualification drop-down list If you want to associate this policy with one or more specific server pools, choose the server pool qualification policy that identifies these pools from the drop-down list. Org drop-down list If you want to associate an organization with this policy, or if you want to change the current association, choose the desired organization from the drop-down list. Click OK. Deleting a Server Inheritance Policy Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Policies tab. Step 4 Step 5 Step 6 Click the Server Inheritance Policies subtab. Right-click the server inheritance policy that you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 421 Configuring Server Pool Policies Configuring Server Pool Policies Server Pool Policy This policy is invoked during the server discovery process. It determines what happens if server pool policy qualifications match a server to the target pool specified in the policy. If a server qualifies for more than one pool and those pools have server pool policies, the server is added to all those pools. Creating a Server Pool Policy Before You Begin This policy requires that one or more of the following resources already exist in the system: • A minimum of one server pool • Server pool policy qualifications, if you choose to have servers automatically added to pools Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click Server Pool Policies and select Create Server Pool Policy. In the Create Server Pool Policy dialog box, complete the following fields: Name Description Name field The name of the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A description of the policy. We recommend that you include information about where and when the policy should be used. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Target Pool drop-down list If you want to associate this policy with a server pool, select that pool from the drop-down list. Cisco UCS Manager GUI Configuration Guide, Release 2.0 422 OL-25712-04 Configuring Server Pool Policy Qualifications Step 6 Name Description Qualification drop-down list If you want to associate this policy with one or more specific server pools, choose the server pool qualification policy that identifies these pools from the drop-down list. Click OK. Deleting a Server Pool Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Servers > Policies > Organization_Name. Expand the Server Pool Policies node. Right-click the policy you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Configuring Server Pool Policy Qualifications Server Pool Policy Qualifications This policy qualifies servers based on the inventory of a server conducted during the discovery process. The qualifications are individual rules that you configure in the policy to determine whether a server meets the selection criteria. For example, you can create a rule that specifies the minimum memory capacity for servers in a data center pool. Qualifications are used in other policies to place servers, not just by the server pool policies. For example, if a server meets the criteria in a qualification policy, it can be added to one or more server pools or have a service profile automatically associated with it. You can use the server pool policy qualifications to qualify servers according to the following criteria: • Adapter type • Chassis location • Memory type and configuration • Power group • CPU cores, type, and configuration • Storage configuration and capacity Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 423 Configuring Server Pool Policy Qualifications • Server model Depending upon the implementation, you may configure several policies with server pool policy qualifications including the following: • Autoconfiguration policy • Chassis discovery policy • Server discovery policy • Server inheritance policy • Server pool policy Creating Server Pool Policy Qualifications Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click the Server Pool Policy Qualifications node and select Create Server Pool Policy Qualification. In the Create Server Pool Policy Qualification dialog box, enter a unique name and description for the policy. (Optional) To use this policy to qualify servers according to their adapter configuration, do the following: a) Click Create Adapter Qualifications. b) In the Create Adapter Qualifications dialog box, complete the following fields: Step 6 Name Description Type drop-down list The adapter type. Once you save the adapter qualification, this type cannot be changed. PID field A regular expression that the adapter PID must match. Maximum Capacity field The maximum capacity for the selected type. To specify a capacity, choose select and enter the desired maximum capacity. You can enter an integer between 1 and 65535. c) Click OK. Step 7 (Optional) To use this policy to qualify servers according to the chassis in which they physically reside, do the following: a) Click Create Chassis/Server Qualifications. Cisco UCS Manager GUI Configuration Guide, Release 2.0 424 OL-25712-04 Configuring Server Pool Policy Qualifications b) In the Chassis Qualifications area of the Create Chassis and Server Qualifications dialog box, complete the following fields to specify the range of chassis you want to use: • First Chassis ID field—The first chassis ID from which server pools associated with this policy can draw. • Number of Chassis field—The total number of chassis to include in the pool, starting with the chassis identified in the First Chassis ID field. Example: For example, if you want to use chassis 5, 6, 7, and 8, enter 5 in the First Chassis ID field and 4 in the Number of Chassis field. If you want to use only chassis 3, enter 3 in the First Chassis ID field and 1 in the Number of Chassis field. Tip If you want to use chassis 5, 6, and 9, create a chassis/server qualification for the range 5-6 and another qualification for chassis 9. You can add as many chassis/server qualifications as needed. c) Click Finish. Step 8 (Optional) To use this policy to qualify servers according to both the chassis and slot in which they physically reside, do the following: a) Click Create Chassis/Server Qualifications. b) In the Chassis Qualifications area of the Create Chassis and Server Qualifications dialog box, complete the following fields to specify the range of chassis you want to use: • First Chassis ID field—The first chassis ID from which server pools associated with this policy can draw. • Number of Chassis field—The total number of chassis to include in the pool, starting with the chassis identified in the First Chassis ID field. c) In the Server Qualifications table, click Add. d) In the Create Server Qualifications dialog box, complete the following fields to specify the range of server locations you want to use: • First Slot ID field—The first slot ID from which server pools associated with this policy can draw. • Number of Slots field—The total number of slots from which server pools associated with this policy can draw. e) Click Finish Stage. f) To add another range of slots, click Add and repeat steps d and e. g) When you have finished specifying the slot ranges, click Finish. Step 9 (Optional) To use this policy to qualify servers according to their memory configuration, do the following: a) Click Create Memory Qualifications. b) In the Create Memory Qualifications dialog box, complete the following fields: Name Description Clock field The minimum clock speed required, in megahertz. Latency field The maximum latency allowed, in nanoseconds. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 425 Configuring Server Pool Policy Qualifications Name Description Min Cap field The minimum memory capacity required, in megabytes. Max Cap field The maximum memory capacity allowed, in megabytes. Width field The minimum width of the data bus. Units field The unit of measure to associate with the value in the Width field. c) Click OK. Step 10 (Optional) To use this policy to qualify servers according to their CPU/Cores configuration, do the following: a) Click Create CPU/Cores Qualifications. b) In the Create CPU/Cores Qualifications dialog box, complete the following fields: Name Description Processor Architecture drop-down list The CPU architecture to which this policy applies. PID field A regular expression that the processor PID must match. Min Number of Cores field The minimum number of CPU cores required. To specify a capacity, choose select and enter an integer between 1 and 65535 in the associated text field. Max Number of Cores field The maximum number of CPU cores allowed. To specify a capacity, choose select and enter an integer between 1 and 65535 in the associated text field. Min Number of Threads field The minimum number of CPU threads required. To specify a capacity, choose select and enter an integer between 1 and 65535 in the associated text field. Max Number of Threads field The maximum number of CPU threads allowed. To specify a capacity, choose select and enter an integer between 1 and 65535 in the associated text field. CPU Speed field The minimum CPU speed required. To specify a capacity, choose select and enter the minimum CPU speed. CPU Stepping field The minimum CPU version required. To specify a capacity, choose select and enter the maximum CPU speed. Cisco UCS Manager GUI Configuration Guide, Release 2.0 426 OL-25712-04 Configuring Server Pool Policy Qualifications c) Click OK. Step 11 (Optional) To use this policy to qualify servers according to their storage configuration and capacity, do the following: a) Click Create Storage Qualifications. b) In the Create Storage Qualifications dialog box, complete the following fields: Name Description Diskless field Whether the available storage must be diskless. This can be one of the following: • Unspecified—Either storage type is acceptable. • Yes—The storage must be diskless. • No—The storage cannot be diskless. Number of Blocks field The minimum number of blocks required. To specify a capacity, choose select and enter the number of blocks. Block Size field The minimum block size required, in bytes. To specify a capacity, choose select and enter the block size. Min Cap field The minimum storage capacity across all disks in the server, in megabytes. To specify a capacity, choose select and enter the minimum storage capacity. Max Cap field The maximum storage capacity allowed, in megabytes. To specify a capacity, choose select and enter the maximum storage capacity. Per Disk Cap field The minimum storage capacity per disk required, in gigabytes. To specify a capacity, choose select and enter the minimum capacity on each disk. Units field The number of units. To specify a capacity, choose select and enter the desired units. c) Click OK. Step 12 (Optional) To use this policy to qualify servers according to the model of the server, do the following: a) Click Create Server Model Qualifications. b) In the Create Server Model Qualifications dialog box, enter a regular expression that the server model must match in the Model field. c) Click OK. Step 13 (Optional) To use this policy to qualify servers according to power group, do the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 427 Configuring Server Pool Policy Qualifications a) Click Create Power Group Qualifications. b) In the Create Power Group Qualifications dialog box, choose a power gruup from the Power Group drop-down list. c) Click OK. Step 14 (Optional) To use this policy to qualify the rack-mount servers that can be added to the associated server pool, do the following: a) Click Create Rack Qualifications. b) In the Create Rack Qualifications dialog box, complete the following fields: Name Description First Slot ID field The first rack-mount server slot ID from which server pools associated with this policy can draw. Number of Slots field The total number of rack-mount server slots from which server pools associated with this policy can draw. Step 15 Verify the qualifications in the table and correct if necessary. Step 16 Click OK. Deleting Server Pool Policy Qualifications Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Servers > Policies > Organization_Name. Expand the Server Pool Policy Qualifications node. Right-click the policy qualifications you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Deleting Qualifications from Server Pool Policy Qualifications Use this procedure to modify Server Pool Policy Qualifications by deleting one or more sets of qualifications. Cisco UCS Manager GUI Configuration Guide, Release 2.0 428 OL-25712-04 Configuring vNIC/vHBA Placement Policies Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Servers > Policies > Organization_Name. Expand the Server Pool Policy Qualifications node. Choose the policy you want to modify. In the Work pane, choose the Qualifications tab. Step 6 To delete a set of qualifications: a) In the table, choose the row that represents the set of qualifications. b) Right-click the row and select Delete. Step 7 Click Save Changes. Configuring vNIC/vHBA Placement Policies vNIC/vHBA Placement Policies vNIC/vHBA placement policies are used to determine what types of vNICs or vHBAs can be assigned to the physical adapters on a server. Each vNIC/vHBA placement policy contains four virtual network interface connections (vCons) that are virtual representations of the physical adapters. When a vNIC/vHBA placement policy is assigned to a service profile, and the service profile is associated with a server, the vCons in the vNIC/vHBA placement policy are assigned to the physical adapters. If you do not include a vNIC/vHBA placement policy in the service profile or you use the default configuration for a server with two adapters, Cisco UCS Manager defaults to the All configuration and equally distributes the vNICs and vHBAs between the adapters. You can use this policy to assign vNICs or vHBAs to either of the two vCons. Cisco UCS Manager uses the vCon assignment to determine how to assign the vNICs and vHBAs to the physical adapter during service profile association. • All—All configured vNICs and vHBAs can be assigned to the vCon, whether they are explicitly assigned to it, unassigned, or dynamic. • Assigned Only—vNICs and vHBAs must be explicitly assigned to the vCon. You can assign them explicitly through the service profile or the properties of the vNIC or vHBA. • Exclude Dynamic—Dynamic vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for all static vNICs and vHBAs, whether they are unassigned or explicitly assigned to it. • Exclude Unassigned—Unassigned vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for dynamic vNICs and vHBAs and for static vNICs and vHBAs that are explicitly assigned to it. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 429 Configuring vNIC/vHBA Placement Policies vCon to Adapter Placement Cisco UCS Manager maps every vCon in a service profile to a physical adapter on the server. How that mapping occurs and how the vCons are assigned to a specific adapter in a server with two adapters depends upon the type of server. You must consider this placement when you configure the vNIC/vHBA placement policy to assign vNICs and vHBAs to vCons. Note vCon to adapter placement is not dependent upon the PCIE slot number of the adapter. The adapter numbers used for the purpose of vCon placement are not the PCIE slot numbers of the adapters, but the ID assigned to them during server discovery. vCon to Adapter Placement for N20-B6620-2 and N20-B6625-2 Blade Servers In these blade servers, the adapters are numbered left to right, but vCons are numbered right to left. If the server has a single adapter, all vCons are assigned to that adapter. However, if the server has two adapters, the vCons are assigned to the adapters in reverse order, as follows: • Adapter1 is assigned vCon2 and vCon4 • Adapter2 is assigned vCon1 and vCon3 vCon to Adapter Placement for All Other Supported Servers For all other servers supported by Cisco UCS, the vCon assignment depends upon the number of adapters in the server, as follows: Table 11: vCon to Adapter Placement by Number of Adapters in Server Number of Adapters vCon1 Assignment vCon2 Assignment vCon3 Assignment vCon4 Assignment 1 Adapter1 Adapter1 Adapter1 Adapter1 2 Adapter1 Adapter2 Adapter1 Adapter2 3 Adapter1 Adapter2 Adapter3 Adapter2 4 Adapter1 Adapter2 Adapter3 Adapter4 vNIC/vHBA to vCon Assignment Cisco UCS Manager provides two options for assigning vNICs and vHBAs to vCons through the vNIC/vHBA placement policy: explicit assignment and implicit assignment. Explicit Assignment of vNICs and vHBAs With explicit assignment, you specify the vCon and, therefore, the adapter to which a vNIC or vHBA is assigned. Use this assignment option when you need to determine how the vNICs and vHBAs are distributed between the adapters on a server. Cisco UCS Manager GUI Configuration Guide, Release 2.0 430 OL-25712-04 Configuring vNIC/vHBA Placement Policies To configure a vCon and the associated vNICs and vHBAs for explicit assignment, do the following: • Set the vCon configuration to any of the available options. You can configure the vCons through a vNIC/vHBA placement policy or in the service profile associated with the server. If a vCon is configured for All, you can still explicitly assign a vNIC or vHBA to that vCon. • Assign the vNICs and vHBAs to a vCon. You can make this assignment through the Virtual Host Interface Placement properties of the vNIC or vHBA or in the service profile associated with the server. If you attempt to assign a vNIC or vHBA to a vCon that is not configured for that type of vNIC or vHBA, Cisco UCS Manager displays a message box to advise you of the configuration error. During service profile association, Cisco UCS Manager validates the configured placement of the vNICs and vHBAs against the number and capabilities of the physical adapters in the server before assigning the vNICs and vHBAs according to the configuration in the policy. Load distribution is based upon the explicit assignments to the vCons and adapters configured in this policy. If the adapters do not support the assignment of one or more vNICs or vHBAs, Cisco UCS Manager raises a fault against the service profile. Note vCon to adapter assignment occurs in a round-robin order. This order means that vNICs are placed on the adapters in the following order: vcon-1, vcon-3, vcon-2, vcon-4. As a result, under the following circumstances, the PCIE order of vNICs can be different than the explicit assignment configured in Cisco UCS Manager: • In a server with two adapters when vNICs are explicitly assigned to all four vCons. • When a service profile that includes explicit assignment is migrated from a server with a higher number of adapters to one with a lower number of adapters. Implicit Assignment of vNICs and vHBAs With implicit assignment, Cisco UCS Manager determines the vCon and, therefore, the adapter to which a vNIC or vHBA is assigned according to the capability of the adapter. Use this assignment option if the adaptor to which a vNIC or vHBA is assigned is not important to your system configuration. To configure a vCon for implicit assignment, do the following: • Set the vCon configuration to All, Exclude Dynamic, or Exclude Unassigned. You can configure the vCons through a vNIC/vHBA placement policy or in the service profile associated with the server. • Do not set the vCon configuration to Exclude Assigned. Implicit assignment cannot be performed with this setting. • Do not assign any vNICs or vHBAs to a vCon. During service profile association, Cisco UCS Manager verifies the number and capabilities of the physical adapters in the server and assigns the vNICs and vHBAs accordingly. Load distribution is based upon the capabilities of the adapters, and placement of the vNICs and vHBAs is performed according to the actual order determined by the system. For example, if one adapter can accommodate more vNICs than another, that adapter is assigned more vNICs. If the adapters cannot support the number of vNICs and vHBAs configured for that server, Cisco UCS Manager raises a fault against the service profile. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 431 Configuring vNIC/vHBA Placement Policies Implicit Assignment of vNICs in a Mixed Adapter Environment The implicit assignment of vNICs functions differently for a server that has mixed adapters, as follows: • A dual slot server that has one VIC adapter and one non-VIC adapter, which have different capabilities. For example, a server that contains a Cisco UCS M81KR Virtual Interface Card and a Cisco UCS CNA M71KR-E adapter. • A configuration that includes both dynamic vNICs and static vNICs. When you assign vNICs implicitly for a dual slot server that has one VIC adapter and non-VIC adapter, Cisco UCS Manager typically assigns one vNIC to each adapter. The remaining vNICs are assigned according to the relative capabilities of the adapters. The following are examples of the relative capabilities of some of the supported adapters: • Cisco UCS M81KR Virtual Interface Card (128 vNICs) and Cisco UCS CNA M71KR-E Adapter (2 vNICs) have a 64:1 capability ratio • Cisco UCS M81KR Virtual Interface Card and Cisco UCS CNA M72KR-E have a 64:1 capability ratio • Cisco UCS CNA M72KR-E and Cisco UCS CNA M72KR-E have a 1:1 capability ratio • Cisco UCS M82-8P Virtual Interface Card and Cisco UCS CNA M71KR-E adapter have a 128:1 capability ratio • Cisco UCS M82-8P Virtual Interface Card and Cisco UCS M81KR Virtual Interface Card have a 2:1 capability ratio. For example, a Cisco UCS M81KR Virtual Interface Card can handle up to 128 vNICs, while a Cisco UCS CNA M71KR-E can only handle 2 vNICs. This difference gives those adapters a 64:1 ratio. If a dual slot blade server has one of each and you choose to allow implicit assignment of vNICs by Cisco UCS Manager, the load balancing ratio assigns the majority of the vNICs to the Cisco UCS M81KR Virtual Interface Card, as follows: Note Total Number of vNICs vNICs Assigned to Cisco UCS M81KR vNICs Assigned to Cisco UCS CNA Virtual Interface Card M71KR-E Adapter 20 19 1 130 128 2 Exceptions to this implicit assignment occur if you configure the vNICs for fabric failover and if you configure dynamic vNICs for the server. For a configuration that includes vNIC fabric failover where one adapter does not support vNIC failover, Cisco UCS Manager implicitly assigns all vNICs which have fabric failover enabled to the adapter that supports them. If the configuration only includes vNICs that are configured for fabric failover, no vNICs are implicitly assigned to the adapter which does not support them. If some vNICs are configured for fabric failover and some are not, Cisco UCS Manager assigns all failover vNICs to the adapter which supports them and a minimum of one non-failover vNIC to the adapter which does not support them, according to the ratio above. For a configuration that includes dynamic vNICs, the same implicit assignment would occur. Cisco UCS Manager assigns all dynamic vNICs to the adapter that supports them. However, with a combination of Cisco UCS Manager GUI Configuration Guide, Release 2.0 432 OL-25712-04 Configuring vNIC/vHBA Placement Policies dynamic vNICs and static vNICs, at least one static vNIC is assigned to the adapter that does not support dynamic vNICs. Creating a vNIC/vHBA Placement Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click vNIC/vHBA Placement Policies and choose Create Placement Policy. In the Create Placement Policy dialog box, do the following: a) In the Name field, enter a unique name for the placement policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. b) In the Selection Preference column for each Virtual Slot, choose one of the following from the drop-down list: • All—All configured vNICs and vHBAs can be assigned to the vCon, whether they are explicitly assigned to it, unassigned, or dynamic. • Assigned Only—vNICs and vHBAs must be explicitly assigned to the vCon. You can assign them explicitly through the service profile or the properties of the vNIC or vHBA. • Exclude Dynamic—Dynamic vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for all static vNICs and vHBAs, whether they are unassigned or explicitly assigned to it. • Exclude Unassigned—Unassigned vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for dynamic vNICs and vHBAs and for static vNICs and vHBAs that are explicitly assigned to it. c) Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 433 Configuring vNIC/vHBA Placement Policies Deleting a vNIC/vHBA Placement Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Servers > Policies > Organization_Name. Expand the vNIC/vHBA Placement Policies node. Right-click the policy you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Explicitly Assigning a vNIC to a vCon Before You Begin Configure the vCons through a vNIC/vHBA placement policy or in the service profile with one of the following values: • Assigned Only • Exclude Dynamic • Exclude Unassigned If a vCon is configured for All, you can still explicitly assign a vNIC or vHBA to that vCon. However, you have less control with this configuration. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization which contains the service profile whose vNICs you want to explicitly assign to a vCon. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Step 6 Expand Service_Profile_Name > vNICs. Click on the vNIC that you want to explicitly assign to a vCon. In the Work pane, click the General tab. Step 7 In the Virtual Host Interface Placement section, complete the following fields: Cisco UCS Manager GUI Configuration Guide, Release 2.0 434 OL-25712-04 Configuring vNIC/vHBA Placement Policies Name Description Desired Placement drop-down list The user-specified virtual network interface connection (vCon) placement for the vNIC. This can be one of the following: • Any—Allows Cisco UCS Manager to determine the vCon to which the vNIC is assigned. • 1—Explicitly assigns the vNIC to vCon1. • 2—Explicitly assigns the vNIC to vCon2. • 3—Explicitly assigns the vNIC to vCon3. • 4—Explicitly assigns the vNIC to vCon4. Actual Assignment field The actual vCon assignment of the vNIC on the server. If you attempt to assign a vNIC to a vCon that is not configured for that type of vNIC, Cisco UCS Manager displays a message box to advise you of the configuration error. You must either assign the vNIC to another vCon or change the vCon configuration in the service profile. Step 8 In the Order section, complete the following fields: Name Description Desired Order field The user-specified PCI order for the vNIC. Enter an integer between 0 and 128. You cannot create more than 128 vNICs for a server. Actual Order field Step 9 The actual PCI order of the vNIC on the server. Click Save Changes. Explicitly Assigning a vHBA to a vCon Before You Begin Configure the vCons through a vNIC/vHBA placement policy or in the service profile with one of the following values: • Assigned Only • Exclude Dynamic • Exclude Unassigned If a vCon is configured for All, you can still explicitly assign a vNIC or vHBA to that vCon. However, you have less control with this configuration. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 435 Configuring vNIC/vHBA Placement Policies Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization which contains the service profile whose vHBAs you want to explicitly assign to a vCon. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Step 6 Expand Service_Profile_Name > vHBAs. Click on the vHBA that you want to explicitly assign to a vCon. In the Work pane, click the General tab. Step 7 In the Virtual Host Interface Placement section, complete the following fields: Name Description Desired Placement field The user-specified virtual network interface connection (vCon) placement for the vHBA. This can be one of the following: • Any—Allows Cisco UCS Manager to determine the vCon to which the vHBA is assigned. • 1—Explicitly assigns the vHBA to vCon1. • 2—Explicitly assigns the vHBA to vCon2. • 3—Explicitly assigns the vHBA to vCon3. • 4—Explicitly assigns the vHBA to vCon4. Actual Assignment field The actual vCon assignment of the vHBA on the server. If you attempt to assign a vHBA to a vCon that is not configured for that type of vHBA, Cisco UCS Manager displays a message box to advise you of the configuration error. You must either assign the vHBA to another vCon or change the vCon configuration in the service profile. Step 8 In the Order section, complete the following fields: Name Description Desired Order field The user-specified PCI order for the vHBA. Enter an integer between 0 and 128. You cannot create more than 128 vHBAs for a server. Actual Order field Step 9 The actual PCI order of the vHBA on the server. Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 436 OL-25712-04 Configuring vNIC/vHBA Placement Policies Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 437 Configuring vNIC/vHBA Placement Policies Cisco UCS Manager GUI Configuration Guide, Release 2.0 438 OL-25712-04 CHAPTER 30 Configuring Server Boot This chapter includes the following sections: • Boot Policy, page 439 • Creating a Boot Policy, page 440 • SAN Boot, page 441 • iSCSI Boot, page 443 • LAN Boot, page 465 • Local Disk Boot, page 465 • Virtual Media Boot, page 466 • Deleting a Boot Policy, page 467 Boot Policy The boot policy determines the following: • Configuration of the boot device • Location from which the server boots • Order in which boot devices are invoked For example, you can choose to have associated servers boot from a local device, such as a local disk or CD-ROM (VMedia), or you can select a SAN boot or a LAN (PXE) boot. You must include this policy in a service profile, and that service profile must be associated with a server for it to take effect. If you do not include a boot policy in a service profile, the server uses the default settings in the BIOS to determine the boot order. Important Changes to a boot policy may be propagated to all servers created with an updating service profile template that includes that boot policy. Reassociation of the service profile with the server to rewrite the boot order information in the BIOS is auto-triggered. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 439 Creating a Boot Policy Creating a Boot Policy You can also create a local boot policy that is restricted to a service profile or service profile template. However, except for iSCSI boot, we recommend that you create a global boot policy that can be included in multiple service profiles or service profile templates. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Right-click Boot Policies and select Create Boot Policy. The Create Boot Policy wizard displays. Step 5 Enter a unique name and description for the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Step 6 (Optional) To reboot all servers that use this boot policy after you make changes to the boot order, check the Reboot on Boot Order Change check box. In the Cisco UCS Manager GUI, if the Reboot on Boot Order Change check box is checked for a boot policy, and if CD-ROM or Floppy is the last device in the boot order, deleting or adding the device does not directly affect the boot order and the server does not reboot. Step 7 (Optional) If desired, check the Enforce vNIC/vHBA/iSCSI Name check box. • If checked, Cisco UCS Manager displays a configuration error and reports whether one or more of the vNICs, vHBAs, or iSCSI vNICs listed in the Boot Order table match the server configuration in the service profile. • If not checked, Cisco UCS Manager uses the vNICs, vHBAs, or iSCSI vNICs (as appropriate for the boot option) from the server configuration in the service profile. It does not report whether the vNICs, vHBAs, or iSCSI vNICs specified in the boot policy match the server configuration in the service profile. Step 8 Configure one or more of the following boot options for the boot policy and set their boot order: • SAN Boot—To boot from an operating system image on the SAN, continue with Configuring a SAN Boot for a Boot Policy, on page 441. You can specify a primary and a secondary SAN boot. If the primary boot fails, the server attempts to boot from the secondary. • iSCSI Boot—To boot from an iSCSI LUN, continue with Creating an iSCSI Boot Policy, on page 451. • LAN Boot—To boot from a centralized provisioning server, continue with Configuring a LAN Boot for a Boot Policy, on page 465. • Local Disk boot—To boot from the local disk on the server, continue with Configuring a Local Disk Boot for a Boot Policy, on page 466. Cisco UCS Manager GUI Configuration Guide, Release 2.0 440 OL-25712-04 SAN Boot • Virtual Media Boot —To boot from virtual media that mimics the insertion of a physical CD or floppy drive into a server, continue with Configuring a Virtual Media Boot for a Boot Policy, on page 466. What to Do Next Include the boot policy in a service profile and/or template. After a server is associated with a service profile that includes this boot policy, you can verify the actual boot order in the Boot Order Details area on the General tab for the server. SAN Boot You can configure a boot policy to boot one or more servers from an operating system image on the SAN. The boot policy can include a primary and a secondary SAN boot. If the primary boot fails, the server attempts to boot from the secondary. We recommend that you use a SAN boot, because it offers the most service profile mobility within the system. If you boot from the SAN when you move a service profile from one server to another, the new server boots from the exact same operating system image. Therefore, the new server appears to be the exact same server to the network. To use a SAN boot, ensure that the following is configured: • The Cisco UCS domain must be able to communicate with the SAN storage device that hosts the operating system image. • A boot target LUN on the device where the operating system image is located. Configuring a SAN Boot for a Boot Policy You can also create a local boot policy that is restricted to a service profile or service profile template. However, except for iSCSI boot, we recommend that you create a global boot policy that can be included in multiple service profiles or service profile templates. Tip We recommend that the boot order in a boot policy include either a local disk or a SAN LUN, but not both, to avoid the possibility of the server booting from the wrong storage type. If you configure a local disk and a SAN LUN for the boot order storage type and the operating system or logical volume manager (LVM) is configured incorrectly, the server might boot from the local disk rather than the SAN LUN. For example, on a server with Red Hat Linux installed, where the LVM is configured with default LV names and the boot order is configured with a SAN LUN and a local disk, Linux reports that there are two LVs with the same name and boots from the LV with the lowest SCSI ID, which could be the local disk. This procedure continues directly from Creating a Boot Policy, on page 440. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 441 SAN Boot Before You Begin Note If you are creating a boot policy that boots the server from a SAN LUN and you require reliable SAN boot operations, we recommend that you first remove all local disks from servers associated with a service profile that includes the boot policy. Procedure Step 1 Step 2 Step 3 Click the down arrows to expand the vHBAs area. Click the Add SAN Boot link. In the Add SAN Boot dialog box, complete the following fields, and click OK: Name Description vHBA field Enter the name of the vHBA you want to use for the SAN boot. Type field This can be one of the following: • Primary—The first address defined for the associated boot device class. A boot policy can only have one primary LAN, SAN, or iSCSI boot location. • Secondary—The second address defined for the associated boot device class. Each boot policy can have only one secondary LAN or SAN boot location. The use of the terms primary or secondary boot devices does not imply a boot order. The effective order of boot devices within the same device class is determined by PCIe bus scan order. Step 4 If this vHBA points to a bootable SAN image, click the Add SAN Boot Target link and, in the Add SAN Boot Target dialog box, complete the following fields, then click OK: Name Description Boot Target LUN field The LUN that corresponds to the location of the boot image. Boot Target WWPN field The WWPN that corresponds to the location of the boot image. Cisco UCS Manager GUI Configuration Guide, Release 2.0 442 OL-25712-04 iSCSI Boot Name Description Type field This can be one of the following: • Primary—The first address defined for the associated boot device class. A boot policy can only have one primary LAN, SAN, or iSCSI boot location. • Secondary—The second address defined for the associated boot device class. Each boot policy can have only one secondary LAN or SAN boot location. The use of the terms primary or secondary boot devices does not imply a boot order. The effective order of boot devices within the same device class is determined by PCIe bus scan order. Step 5 Do one of the following: • Add another boot device to the Boot Order table. • Click OK to finish. What to Do Next Include the boot policy in a service profile and/or template. After a server is associated with a service profile that includes this boot policy, you can verify the actual boot order in the Boot Order Details area on the General tab for the server. iSCSI Boot iSCSI boot enables a server to boot its operating system from an iSCSI target machine located remotely over a network. iSCSI boot is supported on the following Cisco UCS hardware: • Cisco UCS server blades that have the Cisco UCS M51KR-B Broadcom BCM57711 network adapter and use the default MAC address provided by Broadcom. • Cisco UCS M81KR Virtual Interface Card • Cisco UCS M82-8P Virtual Interface Card There are prerequisites that must be met before you configure iSCSI boot. For a list of these prerequisites, see iSCSI Boot Guidelines and Prerequisites, on page 444. For a high-level procedure for implementing iSCSI boot, see Configuring iSCSI Boot, on page 446. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 443 iSCSI Boot iSCSI Boot Process The Cisco UCS Manager iSCSI vNIC and iSCSI boot information created for the service profile is used in the association process to program the mezzanine adapter, located on the blade server. After the adapter is programmed, the blade server reboots with the latest service profile values. After the power on self-test (POST), the adapter attempts to initialize using these service profile values. If the adapter can use the values and log in to its specified target, the adapter initializes and posts an iSCSI Boot Firmware Table (iBFT) to the host memory and a valid bootable LUN to the system BIOS. The iBFT that is posted to the host memory contains the initiator and target configuration that is programmed on the primary iSCSI VNIC. Note The iBFT only uses the first iSCSI vNIC and only Target 1 for the initiator-to-target initialization. This scenario is true even if a second target (Target 2) exists for the first iSCSI vNIC. The next step, which is the installation of the operating system (OS), requires an OS that is iBFT capable. During installation of the OS, the OS installer scans the host memory for the iBFT table and uses the information in the iBFT to discover the boot device and create an iSCSI path to the target LUN. In some OS's a NIC driver is required to complete this path. If this step is successful, the OS installer finds the iSCSI target LUN on which to install the OS. Note The iBFT works at the OS installation software level and might not work with HBA mode (also known as TCP offload). Whether iBFT works with HBA mode depends on the OS capabilities during installation. Also, for a server that includes a Cisco UCS M51KR-B Broadcom BCM57711 adapter, the iBFT normally works at a maximum transmission unit (MTU) size of 1500, regardless of the MTU jumbo configuration. If the OS supports HBA mode, you might need to set HBA mode (also known as TCP offload), dual-fabric support, and jumbo MTU size after the iSCSI installation process. iSCSI Boot Guidelines and Prerequisites These guidelines and prerequisites must be met before configuring iSCSI boot: • To set up iSCSI boot from a Windows 2008 server where the second vNIC (failover vNIC) must boot from an iSCSI LUN, consult Microsoft Knowledge Base Article 976042. Microsoft has a known issue where Windows might fail to boot from an iSCSI drive or cause a bugcheck error if the networking hardware is changed. To work around this issue, follow the resolution recommended by Microsoft. • The storage array must be licensed for iSCSI boot and the array side LUN masking must be properly configured. • Two IP addresses must be determined, one for each iSCSI initiator. If possible, the IP addresses should be on the same subnet as the storage array. The IP addresses are assigned statically or dynamically using the Dynamic Host Configuration Protocol (DHCP). • You cannot configure boot parameters in the Global boot policy. Instead, after configuring boot parameters, you need to include the boot policy in the appropriate service profile. • The operating system (OS) must be iSCSI Boot Firmware Table (iBFT) compatible. • For Cisco UCS M51KR-B Broadcom BCM57711 network adapters: Cisco UCS Manager GUI Configuration Guide, Release 2.0 444 OL-25712-04 iSCSI Boot ◦ Blades that use iSCSI boot must contain the Cisco UCS M51KR-B Broadcom BCM57711 network adapter. For information on installing or replacing an adapter card, see the Cisco UCS B250 Extended Memory Blade Server Installation and Service Note. The service note is accessible from the Cisco UCS B-Series Servers Documentation Roadmap at http://www.cisco.com/go/ unifiedcomputing/b-series-doc. ◦ Set the MAC addresses on the iSCSI device. ◦ If you are using the DHCP Vendor ID (Option 43), the MAC address of an iSCSI device needs to be configured in /etc/dhcpd.conf. ◦ HBA mode (also known as TCP offload) and the boot to target setting are supported. However, only Windows OS supports HBA mode during installation. ◦ Before installing the OS, disable the boot to target setting in the iSCSI adapter policy, then after installing the OS, reenable the boot to target setting. Note Each time you change an adapter policy setting, the adapter reboots to apply the new setting. ◦ When installing the OS on the iSCSI target, the iSCSI target must be ordered before the device where the OS image resides. For example, if you are installing the OS on the iSCSI target from a CD, the boot order should be the iSCSI target and then the CD. ◦ After the server has been iSCSI booted, do not modify the Initiator Name, Target name, LUN, iSCSI device IP, or Netmask/gateway using the Broadcom tool. ◦ Do not interrupt the POST (power on self-test) process or the Cisco UCS M51KR-B Broadcom BCM57711 network adapter will fail to initialize. • For Cisco UCS M81KR Virtual Interface Card and Cisco UCS M82-8P Virtual Interface Card: • Do not set MAC addresses on the iSCSI device. • HBA mode and the boot to target setting are not supported. • When installing the OS on the iSCSI target, the iSCSI target must be ordered after the device where the OS image resides. For example, if you are installing the OS on the iSCSI target from a CD, the boot order should be the CD and then the iSCSI target. • If you are using the DHCP Vendor ID (Option 43), the MAC address of the overlay vNIC needs to be configured in /etc/dhcpd.conf. • After the server has been iSCSI booted, do not modify the IP details of the overlay vNIC. • The VMware ESX/ESXi operating system does not support storing a core dump file to an iSCSI boot target LUN. Dump files must be written to a local disk. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 445 iSCSI Boot Enabling MPIO on Windows Note If you change the networking hardware, Windows may fail to boot from an iSCSI drive. For more information, see Microsoft support Article ID: 976042. Before You Begin The server on which you enable MPIO must have a Cisco VIC driver. Procedure Step 1 In the service profile associated with the server, configure the primary and secondary iSCSI vNICs. For more information, see Creating an iSCSI vNIC for a Service Profile, on page 452. Step 2 Step 3 Using the primary iSCSI vNIC, install the Windows operating system on the iSCSI target LUN. After Windows installation is completed, use the Microsoft software iSCSI initiator to connect to the secondary iSCSI vNIC. Enable MPIO on the host In the service profile associated with the server, add the secondary iSCSI vNIC to the boot policy. For more information, see Creating an iSCSI Boot Policy, on page 451. Step 4 Step 5 Configuring iSCSI Boot When you configure an adapter or blade in Cisco UCS to iSCSI boot from a LUN target, you need to complete all of the following steps. Procedure Command or Action Purpose Step 1 Configure the iSCSI boot adapter policy. (Optional) For more information, see Creating an iSCSI Adapter Policy, on page 447 Step 2 Configure the authentication profiles to be used by the initiator and target. (Optional) For more information, see Creating an Authentication Profile, on page 449 Step 3 If you plan to configure the iSCSI initiator to (Optional) use an IP address from a pool of IP addresses, For more information, see Creating an iSCSI add a block of IP addresses to the iSCSI Initiator IP Pool, on page 450 initiator pool. Cisco UCS Manager GUI Configuration Guide, Release 2.0 446 OL-25712-04 iSCSI Boot Command or Action Purpose Step 4 Create a boot policy that can be used in any For more information about creating a boot policy service profile. Alternatively, you can create that can be used in any service profile, see a local boot policy only for the specific service Creating an iSCSI Boot Policy, on page 451. policy. However, we recommend that you create a boot policy that can be shared with multiple service profiles. Step 5 If you created a boot policy that can be used You can assign the boot policy to the service in any service profile, you need to assign it to profile while configuring the iSCSI boot and the service profile. Otherwise, proceed to the vNIC parameters in the service profile in step 7. next step. Step 6 Create an iSCSI vNIC in a service profile. For more information, see Creating an iSCSI vNIC for a Service Profile, on page 452 Step 7 Configure the iSCSI boot parameters, including the initiator and target interfaces, and iSCSI vNIC parameters in a service profile in expert mode or service profile template. For more information, see Creating a Service Profile with the Expert Wizard, on page 489 or Creating a Service Profile Template, on page 518, respectively. Step 8 Verify the iSCSI boot operation. For more information, see Verifying iSCSI Boot Step 9 Install the OS on the server. For more information, see one of the following guides: • Cisco UCS B-Series Blade Servers VMware Installation Guide • Cisco UCS B-Series Blade Servers Linux Installation Guide • Cisco UCS B-Series Blade Servers Windows Installation Guide Step 10 Boot the server. Creating an iSCSI Adapter Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click Adapter Policies and choose Create iSCSI Adapter Policy. In the Create iSCSI Adapter Policy dialog box, complete the following fields: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 447 iSCSI Boot Name Description Name field The name of the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Connection Timeout field The number of seconds to wait until Cisco UCS assumes that the initial login has failed and the iSCSI adapter is unavailable. Enter an integer between 0 and 255. If you enter 0, Cisco UCS uses the value set in the adapter firmware (default: 15 seconds). LUN Busy Retry Count field The number of times to retry the connection in case of a failure during iSCSI LUN discovery. Enter an integer between 0 and 60. If you enter 0, Cisco UCS uses the value set in the adapter firmware (default: 15 seconds). DHCP Timeout field The number of seconds to wait before the initiator assumes that the DHCP server is unavailable. Enter an integer between 60 and 300 (default: 60 seconds). Enable TCP Timestamp check box Check this box if you want to use a TCP Timestamp. With this setting, transmitted packets are given a time stamp of when the packet was sent so that the packet's round-trip time can be calculated, when needed. Note HBA Mode check box Check this box to enable HBA mode. Important Boot to Target check box This option should only be enabled for servers with the Cisco UCS NIC M51KR-B adapter running the Windows operating system. Check this box to boot from the iSCSI target. Note Step 6 This option only applies to servers with the Cisco UCS NIC M51KR-B adapter. This option only applies to servers with the Cisco UCS NIC M51KR-B adapter. It should be disabled until you have installed an operating system on the server. Click OK. What to Do Next Include the adapter policy in a service profile and/or template. Cisco UCS Manager GUI Configuration Guide, Release 2.0 448 OL-25712-04 iSCSI Boot Deleting an iSCSI Adapter Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Step 6 Expand the Adapter Policies node. Right-click the adapter policy and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Creating an Authentication Profile For iSCSI boot, you need to create both an initiator and a target authentication profile. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click Authentication Profiles and choose Create Authentication Profile. In the Create Authentication Profile dialog box, complete the following fields: Name Description Name field The name of the authentication profile. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. User Id field The user Id associated with this profile. Enter between 1 and 128 characters, spaces, or special characters. Password field The password associated with this profile. Enter between 12 and 16 characters, including special characters. Confirm Password field The password again for confirmation purposes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 449 iSCSI Boot Step 6 Click OK. What to Do Next Include the authentication profile in a service profile and/or template. Deleting an Authentication Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Step 4 Step 5 Step 6 Expand the Authentication Profiles node. Right-click the IP pool you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Creating an iSCSI Initiator IP Pool You can create a group of IP addresses to be used for iSCSI boot. Cisco UCS Manager reserves the block of IP addresses you specify. The IP pool must not contain any IP addresses that have been assigned as static IP addresses for a server or service profile. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 In the LAN tab, expand LAN > Pools Expand the node for the organization where you want to create the pool. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click IP Pool (iscsi-initiator-pool) and choose Create Block of IP Addresses. In the Create a Block of IP Addresses dialog box, complete the following fields: Name Description From field The first IP address in the block. Size field The number of IP addresses in the pool. Cisco UCS Manager GUI Configuration Guide, Release 2.0 450 OL-25712-04 iSCSI Boot Name Description Subnet Mask field The subnet mask associated with the IP addresses in the block. All IP addresses in the management IP pool must be in the same subnet as the IP address of the fabric interconnect. Default Gateway field Step 6 The default gateway associated with the IP addresses in the block. Click OK. What to Do Next Configure one or more service profiles or service profile templates to obtain the iSCSI initiator IP address from the iSCSI initiator IP pool. Deleting an iSCSI Initiator IP Pool Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 Step 5 In the LAN tab, expand LAN > Pools > Organization_Name . Expand the IP Pools (iscsi-initiator-pools) node. Right-click the IP pool you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Creating an iSCSI Boot Policy You can add up to two iSCSI vNICs per boot policy. One vNIC acts as the primary iSCSI boot source, and the other acts as the secondary iSCSI boot source. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Right-click Boot Policies and choose Create Boot Policy. The Create Boot Policy wizard displays. Step 5 Enter a unique name and description for the policy. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 451 iSCSI Boot This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Step 6 (Optional) To reboot all servers that use this boot policy after you make changes to the boot order, check the Reboot on Boot Order Change check box. In the Cisco UCS Manager GUI, if the Reboot on Boot Order Change check box is checked for a boot policy, and if CD-ROM or Floppy is the last device in the boot order, deleting or adding the device does not directly affect the boot order and the server does not reboot. Step 7 (Optional) If desired, check the Enforce vNIC/vHBA/iSCSI Name check box. • If checked, Cisco UCS Manager displays a configuration error and reports whether one or more of the vNICs, vHBAs, or iSCSI vNICs listed in the Boot Order table match the server configuration in the service profile. • If not checked, Cisco UCS Manager uses the vNICs, vHBAs, or iSCSI vNICs (as appropriate for the boot option) from the server configuration in the service profile. It does not report whether the vNICs, vHBAs, or iSCSI vNICs specified in the boot policy match the server configuration in the service profile. Step 8 To add a iSCSI boot to the boot policy, do the following: a) Click the down arrows to expand the iSCSI vNICs area. b) Click the Add iSCSI Boot link. c) In the Add iSCSI Boot dialog box, enter a name for the iSCSI vNIC, and click OK. d) Repeat steps b and c to create another iSCSI vNIC. What to Do Next Include the boot policy in a service profile and/or template. After a server is associated with a service profile that includes this boot policy, you can verify the actual boot order in the Boot Order Details area on the General tab for the server. Creating an iSCSI vNIC for a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile for which you want to create an iSCSI vNIC. Expand the service profile for which you want to create a iSCSI vNIC. Right-click the iSCSI vNICs node and choose Create vNICs. In the Create iSCSI vNIC dialog box, complete the following fields: Step 4 Step 5 Step 6 Cisco UCS Manager GUI Configuration Guide, Release 2.0 452 OL-25712-04 iSCSI Boot Name Description Name field The name of the iSCSI vNIC. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Overlay vNIC drop-down list The LAN vNIC associated with this iSCSI vNIC, if any. iSCSI Adapter Policy drop-down The iSCSI adapter policy associated with this iSCSI vNIC, if any. list Create iSCSI Adapter Policy link Click this link to create a new iSCSI adapter policy that will be available to all iSCSI vNICs. MAC Address field The MAC address associated with this iSCSI vNIC, if any. If the MAC address is not set, Cisco UCS Manager GUI displays Derived. MAC Pool field The MAC pool associated with this iSCSI vNIC, if any. VLAN drop-down list The virtual LAN associated with this iSCSI vNIC. The default VLAN is default. Note For the Cisco UCS M81KR Virtual Interface Card and the Cisco UCS M82-8P Virtual Interface Card, the VLAN that you specify must be the same as the native VLAN on the overlay vNIC. For the Cisco UCS M51KR-B Broadcom BCM57711 adapter, the VLAN that you specify can be any VLAN assigned to the overlay vNIC. Step 7 In the MAC Address Assignment drop-down list in the iSCSI MAC Address area, choose one of the following: • Leave the MAC address unassigned, select Select (None used by default). Select this option if the server that will be associated with this service profile contains a Cisco UCS M81KR Virtual Interface Card adapter or a Cisco UCS M82-8P Virtual Interface Card. Important If the server that will be associated with this service profile contains a Cisco UCS NIC M51KR-B adapter, you must specify a MAC address. • A specific MAC address, select 00:25:B5:XX:XX:XX and enter the address in the MAC Address field. To verify that this address is available, click the corresponding link. • A MAC address from a pool, select the pool name from the list. Each pool name is followed by a pair of numbers in parentheses. The first number is the number of available MAC addresses in the pool and the second is the total number of MAC addresses in the pool. Step 8 (Optional) If you want to create a MAC pool that will be available to all service profiles, click Create MAC Pool and complete the fields in the Create MAC Pool wizard. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 453 iSCSI Boot For more information, see Creating a MAC Pool, on page 295. Deleting an iSCSI vNIC from a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile from which you want to delete an iSCSI vNIC. Step 4 Step 5 Step 6 Step 7 Expand the service profile from which you want to delete an iSCSI vNIC. Expand the iSCSI vNICs node. Right-click the iSCSI vNIC you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Setting iSCSI Boot Parameters You can set iSCSI boot parameters, including the boot order, boot policy, authentication profile, initiator interface, and target interface for an iSCSI vNIC. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile for which you want to create iSCSI boot parameters. If the system does not include multi-tenancy, expand the root node. Click the service profile for which you want to create iSCSI boot parameters. Click the Boot Order tab. In the Specific Boot Policy area, click the down arrows to expand the iSCSI vNICs area. In the iSCSI vNICs area, double-click the iSCSI vNICs from which you want to boot the server to add them to the Boot Order table. In the iSCSI vNICs area, click the Set Boot Parameters link. If there are two iSCSI vNICs, choose the one for which you want to set boot parameters. Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 In the Set iSCSI Boot Parameters dialog box, complete the following fields: Name Description Name field The name of the iSCSI vNIC for which you are setting the boot parameters. Cisco UCS Manager GUI Configuration Guide, Release 2.0 454 OL-25712-04 iSCSI Boot Name Description Authentication Profile drop-down The name of the associated authentication profile. list Create Authentication Profile link Click this link to create a new authentication profile policy that will be available to all iSCSI vNICs. Step 10 In the Initiator Name area, complete the following fields: Name Description Initiator Name Assignment drop-down list Select how the iSCSI boot initiator name is assigned. Choose one of the following methods: • Manual—You will enter a name in the Initiator Name field. The initiator name can contain up to 223 characters. • Pools—Choose an IQN suffix pool from which the name will be assigned. Create IQN Suffix Pool link Click this link to create a new IQN suffix pool that will be available to all iSCSI vNICs. Initiator Name field A regular expression that defines the name of the iSCSI initiator. You can enter any alphanumeric string as well as the following special characters: • . (period) • : (colon) • - (dash) Step 11 From the Initiator IP Address Policy drop-down list, choose of the following: Option Description Select (DHCP used by default) The system selects an interface automatically using DHCP. Static A static IPv4 address is assigned to the iSCSI boot vNIC based on the information entered in this area. Proceed to Step 13. Proceed to Step 12. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 455 iSCSI Boot Option Description Pool An IPv4 address is assigned to the iSCSI boot vNIC from the management IP address pool. Proceed to Step 13. Step 12 If you chose Static from the Initiator IP Address Policy drop-down list, complete the following fields: Name Description IPv4 Address field The IPv4 address assigned to the iSCSI boot vNIC. If you want to specify this address, you must select Static in the Initiator IP Address Policy drop-down list. Subnet Mask field The subnet mask associated with the IPv4 address. Default Gateway field The default gateway associated with the IPv4 address. Primary DNS field The primary DNS server address. Secondary DNS field The secondary DNS server address. Step 13 For the iSCSI target interface, choose one of the following radio buttons: Option Description iSCSI Static Target Interface The system creates a static target interface that you need to configure. Proceed to Step 14. iSCSI Auto Target Interface The system creates an auto target interface. You need to specify whether the auto target uses an initiator or a DCHP vendor ID. Proceed to Step 16. Step 14 If you chose iSCSI Static Target Interface, in the Static Target Interface table, click Add. Step 15 In the Create iSCSI Static Target dialog box, complete the following fields: Cisco UCS Manager GUI Configuration Guide, Release 2.0 456 OL-25712-04 iSCSI Boot Name Description iSCSI Target Name field A regular expression that defines the iSCSI Qualified Name (IQN) or Extended Unique Identifier (EUI) name of the iSCSI target. You can enter any alphanumeric characters as well as the following special characters: • . (period) • : (colon) • - (dash) This name must be properly formatted using standard IQN or EUI guidelines. The following examples show properly formatted iSCSI target names: Important • iqn.2001-04.com.example • iqn.2001-04.com.example:storage:diskarrays-sn-a8675309 • iqn.2001-04.com.example:storage.tape1.sys1.xyz • iqn.2001-04.com.example:storage.disk2.sys1.xyz • eui.02004567A425678D Priority field The system-assigned priority for the iSCSI target. Port field The port associated with the iSCSI target. Enter an integer between 1 and 65535. The default is 3260. Authentication Profile drop-down The name of the associated authentication profile. list Create Authentication Profile link Click this link to create a new authentication profile policy that will be available to all iSCSI vNICs. IPv4 Address field The IPv4 address assigned to the iSCSI target. LUN Id field The LUN identifier in the iSCSI target. Step 16 If you chose iSCSI Auto Target Interface, enter either the initiator name or the DHCP vendor ID in the DHCP Vendor Id field. The initiator must have already been configured. The vendor ID can be up to 32 alphanumeric characters. Step 17 Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 457 iSCSI Boot Modifying iSCSI Boot Parameters You can modify iSCSI boot parameters, including the boot order, boot policy, authentication profile, initiator interface, and target interface for an iSCSI vNIC. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile for which you want to modify iSCSI boot parameters. If the system does not include multi-tenancy, expand the root node. Click the service profile for which you want to modify iSCSI boot parameters. Click the Boot Order tab. Step 4 Step 5 Step 6 Step 7 In the Specific Boot Policy area, click the down arrows to expand the iSCSI vNICs area. To add or delete an iSCSI vNIC from the boot order or to change the boot order, do one of the following: • To add an iSCSI vNIC, in the iSCSI vNICs area, double-click an iSCSI vNICs to add it to the Boot Order table. • To delete an iSCSI vNIC from the boot order, in the Boot Order table, select the iSCSI vNIC and click Delete. • To change the iSCSI vNIC boot order, in the Boot Order table, select the iSCSI vNIC and click either Move Up or Move Down. Step 8 To change the boot parameters, in the iSCSI vNICs area, click the Set Boot Parameters link. If there are two iSCSI vNICs, choose the one for which you want to change boot parameters. Step 9 In the Set iSCSI Boot Parameters dialog box, change the values in any of the following fields: Name Description Name field The name of the iSCSI vNIC for which you are setting the boot parameters. Authentication Profile drop-down The name of the associated authentication profile. list Create Authentication Profile link Click this link to create a new authentication profile policy that will be available to all iSCSI vNICs. Step 10 In the Initiator Name area, complete the following fields: Cisco UCS Manager GUI Configuration Guide, Release 2.0 458 OL-25712-04 iSCSI Boot Name Description Initiator Name Assignment drop-down list Select how the iSCSI boot initiator name is assigned. Choose one of the following methods: • Manual—You will enter a name in the Initiator Name field. The initiator name can contain up to 223 characters. • Pools—Choose an IQN suffix pool from which the name will be assigned. Create IQN Suffix Pool link Click this link to create a new IQN suffix pool that will be available to all iSCSI vNICs. Initiator Name field A regular expression that defines the name of the iSCSI initiator. You can enter any alphanumeric string as well as the following special characters: • . (period) • : (colon) • - (dash) Step 11 From the Initiator IP Address Policy drop-down list, change the selection to one of the following: Option Description Select (DHCP used by default) The system selects an interface automatically using DHCP. Static A static IPv4 address is assigned to the iSCSI boot vNIC based on the information entered in this area. Proceed to Step 13. Proceed to Step 12. Pool An IPv4 address is assigned to the iSCSI boot vNIC from the management IP address pool. Proceed to Step 13. Step 12 If you chose Static from the Initiator IP Address Policy drop-down list, complete or change the following fields: Name Description IPv4 Address field The IPv4 address assigned to the iSCSI boot vNIC. If you want to specify this address, you must select Static in the Initiator IP Address Policy drop-down list. Subnet Mask field The subnet mask associated with the IPv4 address. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 459 iSCSI Boot Name Description Default Gateway field The default gateway associated with the IPv4 address. Primary DNS field The primary DNS server address. Secondary DNS field The secondary DNS server address. Step 13 For the iSCSI target interface, choose one of the following radio buttons: Option Description iSCSI Static Target Interface The system creates a static target interface that you need to configure. Proceed to Step 14. iSCSI Auto Target Interface The system creates an auto target interface. You need to specify whether the auto target uses an initiator or a DCHP vendor ID. Proceed to Step 15. Step 14 If you chose iSCSI Static Target Interface, do one of the following in the Static Target Interface table: • To add an iSCSI static target interface, click Add or to modify an iSCSI target interface, select the iSCSI target interface that you want to change and click Modify. Then and complete or change the following fields in the Create iSCSI Static Target dialog box: Name Description iSCSI Target Name field A regular expression that defines the iSCSI Qualified Name (IQN) or Extended Unique Identifier (EUI) name of the iSCSI target. You can enter any alphanumeric characters as well as the following special characters: • . (period) • : (colon) • - (dash) This name must be properly formatted using standard IQN or EUI guidelines. The following examples show properly formatted iSCSI target names: Important • iqn.2001-04.com.example • iqn.2001-04.com.example:storage:diskarrays-sn-a8675309 • iqn.2001-04.com.example:storage.tape1.sys1.xyz • iqn.2001-04.com.example:storage.disk2.sys1.xyz • eui.02004567A425678D Cisco UCS Manager GUI Configuration Guide, Release 2.0 460 OL-25712-04 iSCSI Boot Name Description Priority field The system-assigned priority for the iSCSI target. Port field The port associated with the iSCSI target. Enter an integer between 1 and 65535. The default is 3260. Authentication Profile drop-down list The name of the associated authentication profile. Create Authentication Profile link Click this link to create a new authentication profile policy that will be available to all iSCSI vNICs. IPv4 Address field The IPv4 address assigned to the iSCSI target. LUN Id field The LUN identifier in the iSCSI target. • To delete an iSCSI target interface, select the iSCSI target interface that you want to delete and click Delete. If you have two iSCSI static targets and you delete the first priority target, the second priority target becomes the first priority target, although Cisco UCS Manager still shows it as the second priority target. Step 15 If you chose iSCSI Auto Target Interface, change the entry to either the initiator name or the DHCP vendor ID in the DHCP Vendor Id field. The initiator must have already been configured. The vendor ID can be up to 32 alphanumeric characters. Step 16 Click OK. Note IQN Pools An IQN pool is a collection of iSCSI Qualified Names (IQNs) for use as initiator identifiers by iSCSI vNICs in a Cisco UCS domain. IQN pool members are of the form prefix:suffix:number, where you can specify the prefix, suffix, and a block (range) of numbers. An IQN pool can contain more than one IQN block, with different number ranges and different suffixes, but sharing the same prefix. Creating an IQN Pool Note In most cases, the maximum IQN size (prefix + suffix + additional characters) is 223 characters. When using the Cisco UCS NIC M51KR-B adapter, you must limit the IQN size to 128 characters. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 461 iSCSI Boot Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 On the SAN tab, expand SAN > Pools. Expand the node for the organization where you want to create the pool. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click IQN Pools and select Create IQN Suffix Pool. In the Define Name and Description page of the Create IQN Suffix Pool wizard, fill in the following fields: Name Description Name field The name of the iSCSI Qualified Name (IQN) pool. This name can be between 1 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field The user-defined description of the pool. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Prefix field The prefix for any IQN blocks created for this pool. Enter from 1 to 150 characters. You can use any letter or number, as well as the special characters . (period), : (colon), and - (hyphen). For example, you could use iqn1.alpha.com. Step 6 Step 7 Click Next. In the Add IQN Blocks page of the Create IQN Suffix Pool wizard, click Add. Step 8 In the Create a Block of IQN Suffixes dialog box, fill in the following fields: Name Description Suffix field The suffix for this bock of iSCSI Qualified Names (IQNs). Enter from 1 to 64 characters. You can use any letter or number, as well as the special characters . (period), : (colon), and - (hyphen). For example, you could use alphadc-1. From field The first suffix number in the block. Size field The number of suffixes in the pool. Cisco UCS Manager GUI Configuration Guide, Release 2.0 462 OL-25712-04 iSCSI Boot Step 9 Click OK. Step 10 Click Finish to complete the wizard. What to Do Next • (Optional) Add additional blocks of IQN suffixes to the IQN pool. • Include the IQN suffix pool in a service profile and/or template. Adding a Block to an IQN Pool Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 On the SAN tab, expand SAN > Pools. Expand the node for the organization containing the pool. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Step 6 Expand the IQN Pools node. Right-click the desired IQN pool and select Create a Block of IQN Suffixes. In the Create a Block of IQN Suffixes dialog box, fill in the following fields: Name Description Suffix field The suffix for this bock of iSCSI Qualified Names (IQNs). Enter from 1 to 64 characters. You can use any letter or number, as well as the special characters . (period), : (colon), and - (hyphen). For example, you could use alphadc-1. Step 7 From field The first suffix number in the block. Size field The number of suffixes in the pool. Click OK. Deleting a Block from an IQN Pool If you delete an address block from a pool, Cisco UCS Manager does not reallocate any addresses in that block that have been assigned to vNICs or vHBAs. All assigned addresses from a deleted block remain with the vNIC or vHBA to which they are assigned until one of the following occurs: • The associated service profiles are deleted. • The vNIC or vHBA to which the address is assigned is deleted. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 463 iSCSI Boot • The vNIC or vHBA is assigned to a different pool. Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 On the SAN tab, expand SAN > Pools. Expand the node for the organization containing the pool. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Step 6 Expand the IQN Pools node. Choose the IQN pool for which you want to delete a block of IQN suffixes. In the Work pane, click the IQN Blocks tab. Step 7 Right-click the block to be deleted and select Delete. Click Yes to confirm the deletion. Click Save Changes. Step 8 Step 9 Deleting an IQN Pool If you delete a pool, Cisco UCS Manager does not reallocate any addresses from that pool that have been assigned to vNICs or vHBAs. All assigned addresses from a deleted pool remain with the vNIC or vHBA to which they are assigned until one of the following occurs: • The associated service profiles are deleted. • The vNIC or vHBA to which the address is assigned is deleted. • The vNIC or vHBA is assigned to a different pool. Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 On the SAN tab, expand SAN > Pools. Expand the node for the organization containing the pool. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Step 6 Expand the IQN Pools node. Right-click the pool you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 464 OL-25712-04 LAN Boot LAN Boot You can configure a boot policy to boot one or more servers from a centralized provisioning server on the LAN. A LAN (or PXE) boot is frequently used to install operating systems on a server from that LAN server. You can add more than one type of boot device to a LAN boot policy. For example, you could add a local disk or virtual media boot as a secondary boot device. Configuring a LAN Boot for a Boot Policy You can also create a local boot policy that is restricted to a service profile or service profile template. However, except for iSCSI boot, we recommend that you create a global boot policy that can be included in multiple service profiles or service profile templates. You can add more than one type of boot device to a boot policy. For example, you could add a local disk or virtual media boot as a secondary boot device. This procedure continues directly from Creating a Boot Policy, on page 440. Procedure Step 1 Step 2 Step 3 Step 4 Click the down arrows to expand the vNICs area. Click the Add LAN Boot link. In the Add LAN Boot dialog box, enter the name of the vNIC that you want to use for the LAN boot in the vNIC field, then click OK. Do one of the following: • Add another boot device to the Boot Order table. • Click OK to finish. What to Do Next Include the boot policy in a service profile and/or template. After a server is associated with a service profile that includes this boot policy, you can verify the actual boot order in the Boot Order Details area on the General tab for the server. Local Disk Boot If a server has a local drive, you can configure a boot policy to boot the server from that drive. Note Cisco UCS Manager does not differentiate between the types of local drives. If an operating system has been installed on more than one local drive or on an internal USB drive (eUSB), you cannot specify which of these local drives the server should use as the boot drive. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 465 Virtual Media Boot Configuring a Local Disk Boot for a Boot Policy You can also create a local boot policy that is restricted to a service profile or service profile template. However, except for iSCSI boot, we recommend that you create a global boot policy that can be included in multiple service profiles or service profile templates. You can add more than one type of boot device to a boot policy. For example, you could add a virtual media boot as a secondary boot device. This procedure continues directly from Creating a Boot Policy, on page 440. Procedure Step 1 Step 2 Step 3 Click the down arrows to expand the Local Devices area. Click Add Local Disk to add the device to the Boot Order table. Do one of the following: • Add another boot device to the Boot Order table. • Click OK to finish. What to Do Next Include the boot policy in a service profile and/or template. After a server is associated with a service profile that includes this boot policy, you can verify the actual boot order in the Boot Order Details area on the General tab for the server. Virtual Media Boot You can configure a boot policy to boot one or more servers from a virtual media device that is accessible from the server. A virtual media device mimics the insertion of a physical CD-ROM disk (read-only) or floppy disk (read-write) into a server. This type of server boot is typically used to manually install operating systems on a server. Configuring a Virtual Media Boot for a Boot Policy You can also create a local boot policy that is restricted to a service profile or service profile template. However, except for iSCSI boot, we recommend that you create a global boot policy that can be included in multiple service profiles or service profile templates. You can add more than one type of boot device to a boot policy. For example, you could add a local disk boot as a secondary boot device. Cisco UCS Manager GUI Configuration Guide, Release 2.0 466 OL-25712-04 Deleting a Boot Policy Note Virtual Media requires the USB to be enabled. If you modify the BIOS settings that affect the USB functionality, you also affect the Virtual Media. Therefore, we recommend that you leave the following USB BIOS defaults for best performance: • Make Device Non Bootable—set to disabled • USB Idle Power Optimizing Setting—set to high-performance This procedure continues directly from Creating a Boot Policy, on page 440. Procedure Step 1 Click the down arrows to expand the Local Devices area. Step 2 Click one of the following links to add the device to the Boot Order table: • Add CD-ROM • Add Floppy Step 3 Do one of the following: • Add another boot device to the Boot Order table. • Click OK to finish. What to Do Next Include the boot policy in a service profile and/or template. After a server is associated with a service profile that includes this boot policy, you can verify the actual boot order in the Boot Order Details area on the General tab for the server. Deleting a Boot Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Servers > Policies > Organization_Name. Expand the Boot Policies node. Right-click the policy you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 467 Deleting a Boot Policy Cisco UCS Manager GUI Configuration Guide, Release 2.0 468 OL-25712-04 CHAPTER 31 Deferring Deployment of Service Profile Updates This chapter includes the following sections: • Deferred Deployment of Service Profiles, page 469 • Configuring Schedules, page 472 • Configuring Maintenance Policies, page 482 • Managing Pending Activities, page 484 Deferred Deployment of Service Profiles Some modifications to a service profile or to an updating service profile template can be disruptive and require a reboot of the server. You can, however, configure deferred deployment to control when those disruptive configuration changes are implemented. For example, you can choose to deploy the service profile changes immediately or have them deployed during a specified maintenance window. You can also choose whether or not a service profile deployment requires explicit user acknowledgement. Deferred deployment is available for all configuration changes that occur through the association of a service profile with a server. These configuration changes can be prompted by a change to a service profile, to a policy that is included in a service profile, or to an updating service profile template. For example, you can defer the upgrade and activation of firmware through host firmware packages and management firmware packages, such as server BIOS, RAID controller, host HBA, and network adapters. However, you cannot defer the direct deployment of firmware images for components that do not use either of the firmware packages, such as Cisco UCS Manager, fabric interconnects, and I/O modules. Deferred deployment is not available for the following actions which require the reboot of a server: • Initial association of a service profile with a server • Final disassociation of a service profile from a server, without associating the service profile with a different server • Decommissioning a server • Reacknowledging a server • Resetting a server Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 469 Deferred Deployment of Service Profiles If you want to defer the deployment of service profile changes, you must configure one or more maintenance policies and configure each service profile with a maintenance policy. If you want to define the time period when the deployment should occur, you also need to create at least one schedule with one or more recurring occurrences or one time occurrences, and include that schedule in a maintenance policy. Deferred Deployment Schedules A schedule contains a set of occurrences. These occurrences can be one time only or can recur at a specified time and day each week. The options defined in the occurrence, such as the duration of the occurrence or the maximum number of tasks to be run, determine whether a service profile change is deployed. For example, if a change cannot be deployed during a given maintenance window because the maximum duration or number of tasks has been reached, that deployment is carried over to the next maintenance window. Each schedule checks periodically to see whether the Cisco UCS domain has entered one or more maintenance windows. If it has, the schedule executes the deployments that are eligible according to the constraints specified in the maintenance policy A schedule contains one or more occurrences, which determine the maintenance windows associated with that schedule. An occurrence can be one of the following: One Time Occurrence One time occurrences define a single maintenance window. These windows continue until the maximum duration of the window or the maximum number of tasks that can be run in the window has been reached. Recurring Occurrence Recurring occurrences define a series of maintenance windows. These windows continue until the maximum number of tasks or the end of the day specified in the occurrence has been reached. Maintenance Policy A maintenance policy determines how Cisco UCS Manager reacts when a change that requires a server reboot is made to a service profile associated with a server or to an updating service profile bound to one or more service profiles. The maintenance policy specifies how Cisco UCS Manager deploys the service profile changes. The deployment can occur in one of the following ways: • Immediately • When acknowledged by a user with admin privileges • Automatically at the time specified in the schedule If the maintenance policy is configured to deploy the change during a scheduled maintenance window, the policy must include a valid schedule. The schedule deploys the changes in the first available maintenance window. Cisco UCS Manager GUI Configuration Guide, Release 2.0 470 OL-25712-04 Deferred Deployment of Service Profiles Pending Activities If you configure deferred deployment in a Cisco UCS domain, Cisco UCS Manager enables you to view all pending activities. You can see activities that are waiting for user acknowledgement and those that have been scheduled. If a Cisco UCS domain has pending activities, Cisco UCS Manager GUI notifies users with admin privileges when they log in. Cisco UCS Manager displays information about all pending activities, including the following: • Name of the service profile to be deployed and associated with a server • Server affected by the deployment • Disruption caused by the deployment • Change performed by the deployment Note You cannot specify the maintenance window in which a specific pending activity is applied to the server. The maintenance window depends upon how many activities are pending and which maintenance policy is assigned to the service profile. However, any user with admin privileges can manually initiate a pending activity and reboot the server immediately, whether it is waiting for user acknowledgment or for a maintenance window. Guidelines and Limitations for Deferred Deployment Cannot Undo All Changes to Service Profiles or Service Profile Templates If you cancel a pending change, Cisco UCS Manager attempts to roll back the change without rebooting the server. However, for complex changes, Cisco UCS Manager may have to reboot the server a second time to roll back the change. For example, if you delete a vNIC, Cisco UCS Manager reboots the server according to the maintenance policy included in the service profile. You cannot cancel this reboot and change, even if you restore the original vNIC in the service profile. Instead, Cisco UCS Manager schedules a second deployment and reboot of the server. Association of Service Profile Can Exceed Boundaries of Maintenance Window After Cisco UCS Manager begins the association of the service profile, the scheduler and maintenance policy do not have any control over the procedure. If the service profile association does not complete within the allotted maintenance window, the process continues until it is completed. For example, this can occur if the association does not complete in time because of retried stages or other issues. Cannot Specify Order of Pending Activities Scheduled deployments run in parallel and independently. You cannot specify the order in which the deployments occur. You also cannot make the deployment of one service profile change dependent upon the completion of another. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 471 Configuring Schedules Cannot Perform Partial Deployment of Pending Activity Cisco UCS Manager applies all changes made to a service profile in the scheduled maintenance window. You cannot make several changes to a service profile at the same time and then have those changes be spread across several maintenance windows. When Cisco UCS Manager deploys the service profile changes, it updates the service profile to match the most recent configuration in the database. Configuring Schedules Creating a Schedule Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, right-click Schedules and choose Create Schedule. In the Identify Schedule page of the Create Schedule wizard, complete the following fields: Name Description Name field The name of the schedule. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A description of the schedule. We recommend including information about where and when the schedule should be used. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Step 4 Step 5 Click Next. On the One Time Occurrences page, click one of the following: Option Description Next Moves to the next page. Choose this option if you do not want to create a one time occurrence for this schedule. If you choose this option, continue with Step 8. Add Opens the Create a One Time Occurrence dialog box, where you can specify a single time when this schedule should be run. If you choose this option, continue with Step 6. Step 6 (Optional) In the Create a One Time Occurrence dialog box, do the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 472 OL-25712-04 Configuring Schedules a) Complete the following fields: Name Description Name field The name of the one time occurrence of this schedule. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Start Time field The date and time that the occurrence will run. Click the down arrow at the end of the field to select the date from a calendar. b) Click the down arrows to expand the Options area. c) In the Options area, complete the following fields: Name Description Max Duration field The maximum length of time that the scheduled occurrence can run. This can be one of the following: • None—The occurrence runs until all tasks are completed. • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the maximum amount of time that the occurrence can run. Cisco UCS completes as many scheduled tasks as possible within the specified time. By default, the maximum duration is set to none. If you do not change this setting and you do not set a maximum number of tasks, the maintenance window continues until all pending activities are completed. Max Number of Tasks field The maximum number of scheduled tasks that can be run during this occurrence. This can be one of the following: • Unlimited—Cisco UCS runs all scheduled tasks unless those tasks exceed the maximum time specified in the Max Duration field. If Max Duration is set to none and you select this option, the maintenance window continues until all pending activities are completed. • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of tasks that can be run during this occurrence. Enter an integer between 1 and 65535. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 473 Configuring Schedules Name Description Max Number of Concurrent Tasks field The maximum number of tasks that can run concurrently during this occurrence. This can be one of the following: • Unlimited—Cisco UCS runs as many concurrent tasks as the system can handle. • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of concurrent tasks that can be run during this occurrence. Enter an integer between 1 and 65535. Minimum Interval Between Tasks field The minimum length of time that the system should wait before starting a new task. This setting is meaningful only if the maximum number of concurrent tasks is set to a value other than none. This can be one of the following: • None—Cisco UCS runs the next task as soon as possible. • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the minimum amount of time that Cisco UCS will wait between tasks. d) Click OK. Step 7 Step 8 To add another one time occurrence, click Add and repeat step 6. Otherwise, click Next. (Optional) If you want to define a recurring occurrence for this schedule, on the Recurring Occurrences page, click Add. a) In the Create a Recurring Occurrence dialog box, complete the following fields: Name Description Name field The name of the recurring occurrence of this schedule. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Cisco UCS Manager GUI Configuration Guide, Release 2.0 474 OL-25712-04 Configuring Schedules Name Description Day field The day on which Cisco UCS runs an occurrence of this schedule. This can be one of the following: • every day • Monday • Tuesday • Wednesday • Thursday • Friday • Saturday • Sunday • odd days • even days Hour field The hour of the specified day at which this occurrence of the schedule starts. This can be an integer between 0 and 24, where 0 and 24 are both equivalent to midnight. Cisco UCS ends all recurring occurrences on the same day in which they start, even if the maximum duration has not been reached. For example, if you specify a start time of 11 p.m. and a maximum duration of 3 hours, Cisco UCS starts the occurrence at 11 p.m. but ends it at 11:59 p.m. after only 59 minutes. Ensure that the start time you specify is early enough so that the recurring occurrence finishes before 11:59 p.m. Note Minute field The minute of the hour at which the schedule occurrence starts. This can be an integer between 0 and 60. b) Click the down arrows to expand the Options area. c) In the Options area, complete the following fields: Name Description Max Duration field The maximum length of time that each occurrence of this schedule can run. This can be one of the following: • None—The occurrence runs until all tasks are completed. • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the maximum amount of time that the occurrence can run. Cisco UCS completes as many scheduled tasks as possible within the specified time. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 475 Configuring Schedules Name Description Max Number of Tasks field The maximum number of scheduled tasks that can be run during each occurrence. This can be one of the following: • Unlimited—Cisco UCS runs all scheduled tasks unless those tasks exceed the maximum time specified in the Max Duration field. If Max Duration is set to none and you select this option, the maintenance window continues until all pending activities are completed. • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of tasks that can be run during this occurrence. Enter an integer between 1 and 65535. Max Number of Concurrent Tasks field The maximum number of tasks that can run concurrently during each occurrence. This can be one of the following: • Unlimited—Cisco UCS runs as many concurrent tasks as the system can handle. • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of concurrent tasks that can be run during this occurrence. Enter an integer between 1 and 65535. Minimum Interval Between Tasks field The minimum length of time that the system should wait before starting a new task. This setting is meaningful only if the maximum number of concurrent tasks is set to a value other than none. This can be one of the following: • None—Cisco UCS runs the next task as soon as possible. • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the minimum amount of time that Cisco UCS will wait between tasks. d) Click OK. e) To add another recurring occurrence, click Add and repeat this step. Step 9 Click Finish. Cisco UCS Manager GUI Configuration Guide, Release 2.0 476 OL-25712-04 Configuring Schedules Creating a One Time Occurrence for a Schedule Note By default, the maximum duration and the maximum number of tasks are set to none. If you do not change either of these defaults, Cisco UCS Manager does not impose any limit to the length of time that the maintenance window lasts. All pending activities are applied as soon as the scheduled maintenance window begins, and Cisco UCS Manager continues to reboot the servers impacted by the pending activities until all of those tasks are complete. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 On the Servers tab, expand Schedules. Right-click the schedule to which you want to add an occurrence and choose Create a One Time Occurrence. In the Create a One Time Occurrence dialog box, complete the following fields: Name Description Name field The name of the one time occurrence of this schedule. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Start Time field The date and time that the occurrence will run. Click the down arrow at the end of the field to select the date from a calendar. Step 5 Step 6 Click the down arrows to expand the Options area. In the Options area, complete the following fields: Name Description Max Duration field The maximum length of time that the scheduled occurrence can run. This can be one of the following: • None—The occurrence runs until all tasks are completed. • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the maximum amount of time that the occurrence can run. Cisco UCS completes as many scheduled tasks as possible within the specified time. By default, the maximum duration is set to none. If you do not change this setting and you do not set a maximum number of tasks, the maintenance window continues until all pending activities are completed. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 477 Configuring Schedules Name Description Max Number of Tasks field The maximum number of scheduled tasks that can be run during this occurrence. This can be one of the following: • Unlimited—Cisco UCS runs all scheduled tasks unless those tasks exceed the maximum time specified in the Max Duration field. If Max Duration is set to none and you select this option, the maintenance window continues until all pending activities are completed. • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of tasks that can be run during this occurrence. Enter an integer between 1 and 65535. Max Number of Concurrent Tasks field The maximum number of tasks that can run concurrently during this occurrence. This can be one of the following: • Unlimited—Cisco UCS runs as many concurrent tasks as the system can handle. • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of concurrent tasks that can be run during this occurrence. Enter an integer between 1 and 65535. Minimum Interval Between Tasks field The minimum length of time that the system should wait before starting a new task. This setting is meaningful only if the maximum number of concurrent tasks is set to a value other than none. This can be one of the following: • None—Cisco UCS runs the next task as soon as possible. • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the minimum amount of time that Cisco UCS will wait between tasks. Step 7 Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 478 OL-25712-04 Configuring Schedules Creating a Recurring Occurrence for a Schedule Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 On the Servers tab, expand Schedules. Right-click the schedule to which you want to add an occurrence and choose Create a Recurring Occurrence. In the Create a Recurring Occurrence dialog box, complete the following fields: Name Description Name field The name of the recurring occurrence of this schedule. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Day field The day on which Cisco UCS runs an occurrence of this schedule. This can be one of the following: • every day • Monday • Tuesday • Wednesday • Thursday • Friday • Saturday • Sunday • odd days • even days Hour field The hour of the specified day at which this occurrence of the schedule starts. This can be an integer between 0 and 24, where 0 and 24 are both equivalent to midnight. Cisco UCS ends all recurring occurrences on the same day in which they start, even if the maximum duration has not been reached. For example, if you specify a start time of 11 p.m. and a maximum duration of 3 hours, Cisco UCS starts the occurrence at 11 p.m. but ends it at 11:59 p.m. after only 59 minutes. Ensure that the start time you specify is early enough so that the recurring occurrence finishes before 11:59 p.m. Note Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 479 Configuring Schedules Step 5 Step 6 Name Description Minute field The minute of the hour at which the schedule occurrence starts. This can be an integer between 0 and 60. Click the down arrows to expand the Options area. In the Options area, complete the following fields: Name Description Max Duration field The maximum length of time that each occurrence of this schedule can run. This can be one of the following: • None—The occurrence runs until all tasks are completed. • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the maximum amount of time that the occurrence can run. Cisco UCS completes as many scheduled tasks as possible within the specified time. Max Number of Tasks field The maximum number of scheduled tasks that can be run during each occurrence. This can be one of the following: • Unlimited—Cisco UCS runs all scheduled tasks unless those tasks exceed the maximum time specified in the Max Duration field. If Max Duration is set to none and you select this option, the maintenance window continues until all pending activities are completed. • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of tasks that can be run during this occurrence. Enter an integer between 1 and 65535. Max Number of Concurrent Tasks field The maximum number of tasks that can run concurrently during each occurrence. This can be one of the following: • Unlimited—Cisco UCS runs as many concurrent tasks as the system can handle. • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of concurrent tasks that can be run during this occurrence. Enter an integer between 1 and 65535. Cisco UCS Manager GUI Configuration Guide, Release 2.0 480 OL-25712-04 Configuring Schedules Name Description Minimum Interval Between Tasks field The minimum length of time that the system should wait before starting a new task. This setting is meaningful only if the maximum number of concurrent tasks is set to a value other than none. This can be one of the following: • None—Cisco UCS runs the next task as soon as possible. • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the minimum amount of time that Cisco UCS will wait between tasks. Step 7 Click OK. Deleting a One Time Occurrence from a Schedule If this is the only occurrence in a schedule, that schedule is reconfigured with no occurrences. If the schedule is included in a maintenance policy and that policy is assigned to a service profile, any pending activities related to the server associated with the service profile cannot be deployed. You must add a one time ocurrence or a recurring occurrence to the schedule to deploy the pending activity. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Schedules > Schedule_Name. Expand One Time Occurrences. Right-click the occurrence you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Deleting a Recurring Occurrence from a Schedule If this is the only occurrence in a schedule, that schedule is reconfigured with no occurrences. If the schedule is included in a maintenance policy and that policy is assigned to a service profile, any pending activities related to the server associated with the service profile cannot be deployed. You must add a one time ocurrence or a recurring occurrence to the schedule to deploy the pending activity. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 481 Configuring Maintenance Policies Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Schedules > Schedule_Name. Expand Recurring Occurrences. Right-click the occurrence you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Deleting a Schedule If this schedule is included in a maintenance policy, the policy is reconfigured with no schedule. If that policy is assigned to a service profile, any pending activities related to the server associated with the service profile cannot be deployed. You must add a schedule to the maintenance policy to deploy the pending activity. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 On the Servers tab, expand Schedules. Right-click the schedule you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Configuring Maintenance Policies Creating a Maintenance Policy Before You Begin If you plan to configure this maintenance policy for automatic deferred deployment, create a schedule. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click Maintenance Policies and choose Create Maintenance Policy. In the Create Maintenance Policy dialog box, complete the following fields: Cisco UCS Manager GUI Configuration Guide, Release 2.0 482 OL-25712-04 Configuring Maintenance Policies Name Description Name field The name of the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A description of the policy. We recommend that you include information about where and when the policy should be used. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Reboot Policy field When a service profile is associated with a server, or when changes are made to a service profile that is already associated with a server, the server needs to be rebooted to complete the process. The Reboot Policy field determines when the reboot occurs for servers associated with any service profiles that include this maintenance policy. This can be one of the following: • Immediate—The server is rebooted automatically as soon as the service profile association is complete or service profile changes are saved by the user. • User Ack—The user must reboot the server manually after the service profile association is complete or changes are made. • Timer Automatic—Cisco UCS defers all service profile associations and changes until the maintenance window defined by the schedule shown in the Schedule field. Schedule drop-down list Step 6 If the Reboot Policy is set to Timer Automatic, the schedule specifies when maintenance operations can be applied to the server. Cisco UCS reboots the server and completes the service profile changes at the scheduled time. Click OK. What to Do Next Include the policy in a service profile or service profile template. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 483 Managing Pending Activities Deleting a Maintenance Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Servers > Policies > Organization_Name. Expand Maintenance Policies. Right-click the maintenance policy you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Managing Pending Activities Viewing Pending Activities Procedure Step 1 Step 2 On the toolbar, click Pending Activities. Click one of the following tabs: • User Acknowledged Activities—Displays the tasks that require user acknowledgement before they can complete. • Scheduled Activities—Displays the tasks that will be performed based on the associated maintenance schedule. Step 3 Click a row in the table to view the details of that pending activity. If you click the link in the Server column, Cisco UCS Manager displays the properties of that server. Deploying a Service Profile Change Waiting for User Acknowledgement Important You cannot stop Cisco UCS Manager from rebooting the affected server after you acknowledge a pending activity. Cisco UCS Manager GUI Configuration Guide, Release 2.0 484 OL-25712-04 Managing Pending Activities Procedure Step 1 Step 2 On the toolbar, click Pending Activities. In the Pending Activities dialog box, click the User Acknowledged Activities tab. Step 3 In the Reboot Now column of the table, check the Acknowledge All check box for the pending activity you want to deploy immediately. Click OK. Cisco UCS Manager immediately reboots the server affected by the pending activity. Step 4 Deploying All Service Profile Changes Waiting for User Acknowledgement Important You cannot stop Cisco UCS Manager from rebooting the affected server after you acknowledge a pending activity. Procedure Step 1 Step 2 On the toolbar, click Pending Activities. In the Pending Activities dialog box, click the User Acknowledged Activities tab. Step 3 In the toolbar, check the Acknowledge All check box. Cisco UCS Manager GUI checks the Reboot Now check boxes for all pending activities listed in the table. Step 4 Click OK. Cisco UCS Manager immediately reboots all servers affected by the pending activities listed in the table. Deploying a Scheduled Service Profile Change Immediately Important You cannot stop Cisco UCS Manager from rebooting the affected server after you acknowledge a pending activity. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 485 Managing Pending Activities Procedure Step 1 Step 2 On the toolbar, click Pending Activities. In the Pending Activities dialog box, click the Scheduled Activities tab. Step 3 In the Reboot Now column of the table, check the Acknowledge All check box for the pending activity you want to deploy immediately. Click OK. Cisco UCS Manager immediately reboots the server affected by the pending activity. Step 4 Deploying All Scheduled Service Profile Changes Immediately Important You cannot stop Cisco UCS Manager from rebooting the affected server after you acknowledge a pending activity. Procedure Step 1 Step 2 On the toolbar, click Pending Activities. In the Pending Activities dialog box, click the Scheduled Activities tab. Step 3 In the toolbar, check the Acknowledge All check box. Cisco UCS Manager GUI checks the Reboot Now check boxes for all pending activities listed in the table. Step 4 Click OK. Cisco UCS Manager immediately reboots all servers affected by the pending activities listed in the table. Cisco UCS Manager GUI Configuration Guide, Release 2.0 486 OL-25712-04 CHAPTER 32 Configuring Service Profiles This chapter includes the following sections: • Service Profiles that Override Server Identity, page 487 • Service Profiles that Inherit Server Identity, page 488 • Service Profile Templates, page 488 • Guidelines and Recommendations for Service Profiles, page 489 • Creating Service Profiles, page 489 • Working with Service Profile Templates, page 518 • Managing Service Profiles, page 544 Service Profiles that Override Server Identity This type of service profile provides the maximum amount of flexibility and control. This profile allows you to override the identity values that are on the server at the time of association and use the resource pools and policies set up in Cisco UCS Manager to automate some administration tasks. You can disassociate this service profile from one server and then associate it with another server. This re-association can be done either manually or through an automated server pool policy. The burned-in settings, such as UUID and MAC address, on the new server are overwritten with the configuration in the service profile. As a result, the change in server is transparent to your network. You do not need to reconfigure any component or application on your network to begin using the new server. This profile allows you to take advantage of and manage system resources through resource pools and policies, such as the following: • 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 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 487 Service Profiles that Inherit Server Identity Unless the service profile contains power management policies, a server pool qualification policy, or another policy that requires a specific hardware configuration, the profile can be used 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 may not be the values burned into the server hardware at manufacture if those values were changed before this profile is associated with the server. Service Profile Templates With a service profile template, you can quickly create several service profiles with the same basic parameters, such as the number of vNICs and vHBAs, and with identity information drawn from the same pools. Tip If you need only one service profile with similar values to an existing service profile, you can clone a service profile in the Cisco UCS Manager GUI. For example, if you need several service profiles with similar values to configure servers to host database software, you can create a service profile template, either manually or from an existing service profile. You then use the template to create the service profiles. Cisco UCS supports the following types of service profile templates: Cisco UCS Manager GUI Configuration Guide, Release 2.0 488 OL-25712-04 Guidelines and Recommendations for Service Profiles Initial template Service profiles created from an initial template inherit all the properties of the template. However, after you create the profile, it is no longer connected to the template. If you need to make changes to one or more profiles created from this template, you must change each profile individually. Updating template Service profiles created from an updating template inherit all the properties of the template and remain connected to the template. Any changes to the template automatically update the service profiles created from the template. Guidelines and Recommendations for Service Profiles In addition to any guidelines or recommendations that are specific to policies and pools included in service profiles and service profile templates, such as the local disk configuration policy, you need to be aware of the following guidelines and recommendations that impact the ability to associate a service profile with a server: Limit to the Number of vNICs that Can Be Configured on a Rack-Mount Server You can configure up to 56 vNICs per supported adapter, such as the Cisco UCS P81E Virtual Interface Card (N2XX-ACPCI01), on any rack-mount server that is integrated with Cisco UCS Manager. No Power Capping Support for Rack-Mount Servers Power capping is not supported for rack servers. If you include a power control policy in a service profile that is associated with a rack-mount server, the policy is not implemented. Creating Service Profiles Creating a Service Profile with the Expert Wizard Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization where you want to create the service profile. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click the organization and select Create Service Profile (expert). In the Create Service Profile (expert) wizard, complete the following: • Page 1: Identifying the Service Profile , on page 490 • Page 2: Configuring the Storage Options, on page 491 • Page 3: Configuring the Networking Options, on page 496 • Page 4: Setting the vNIC/vHBA Placement, on page 502 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 489 Creating Service Profiles • Page 5: Setting the Server Boot Order, on page 504 • Page 6: Adding the Maintenance Policy, on page 507 • Page 7: Specifying the Server Assignment, on page 509 • Page 8: Adding Operational Policies, on page 511 Page 1: Identifying the Service Profile This procedure directly follows the steps in Creating a Service Profile with the Expert Wizard, on page 489. It describes how to set the identity of a service profile on the Identify Service Profile page of the Create Service Profile (expert) wizard. Procedure Step 1 In the Name field, enter a unique name that you can use to identify the service profile. This name can be between 2 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and this name must be unique across all service profiles and service profile templates within the same organization. This name must be unique within the organization or sub-organization in which you are creating the service profile. Step 2 From the UUID Assignment drop-down list, do one of the following: Option Description Select (pool default used by default) Assigns a UUID from the default UUID Suffix pool. Continue with Step 5. Hardware Default Uses the UUID assigned to the server by the manufacturer. If you choose this option, the UUID remains unassigned until the service profile is associated with a server. At that point, the UUID is set to the UUID value assigned to the server by the manufacturer. If the service profile is later moved to a different server, the UUID is changed to match the new server. Continue with Step 5. XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX Uses the UUID that you manually assign. Continue with Step 3. Cisco UCS Manager GUI Configuration Guide, Release 2.0 490 OL-25712-04 Creating Service Profiles Option Description Pools Pool_Name Assigns a UUID from the UUID Suffix pool that you select from the list at the bottom of the drop-down list. Each pool name is followed by two numbers in parentheses that show the number of UUIDs still available in the pool and the total number of UUIDs in the pool. If you do not want use any of the existing pools, but instead want to create a pool that all serivce profiles can access, continue with Step 4. Otherwise, continue with Step 5. Step 3 (Optional) If you selected the XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX option, do the following: a) In the UUID field, enter the valid UUID that you want to assign to the server which uses this service profile. b) To verify that the selected UUID is available, click the here link. Step 4 (Optional) If you want to create a new UUID Suffix pool to use to use in this service profile, click Create UUID Suffix Pool and complete the fields in the Create UUID Suffix Pool wizard. For more information, see Creating a UUID Suffix Pool, on page 370. Step 5 (Optional) In the text box, enter a description of this service profile. The user-defined description for this service profile. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Step 6 Click Next. What to Do Next Complete the steps in Page 2: Configuring the Storage Options, on page 491. Page 2: Configuring the Storage Options This procedure directly follows Page 1: Identifying the Service Profile , on page 490. It describes how to configure the storage options for a service profile on the Storage page of the Create Service Profile (expert) wizard. Procedure Step 1 From the Local Storage drop-down list, choose one of the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 491 Creating Service Profiles Option Description Select Local Storage Policy to use Assigns the default local disk storage policy to this service profile. Continue with Step 4. Create a Specific Storage Policy Enables you to create a local disk policy that can only be accessed by this service profile. Continue with Step 2. Storage Policies Policy_Name Select an existing local disk policy from the list at the bottom of the drop-down list. Cisco UCS Manager assigns this policy to the service profile. If you do not want use any of the existing policies, but instead want to create a policy that all service profiles can access, continue with Step 3. Otherwise, continue with Step 4. Step 2 (Optional) If you chose Create a Specific Storage Policy and want to create a new policy that can only be used by this service profile, do the following: a) From the Mode drop-down list, choose one of the following: • No Local Storage—For a diskless server or a SAN only configuration. If you select this option, you cannot associate any service profile which uses this policy with a server that has a local disk. • RAID 0 Striped—Data is striped across all disks in the array, providing fast throughput. There is no data redundancy, and all data is lost if any disk fails. • RAID 1 Mirrored—Data is written to two disks, providing complete data redundancy if one disk fails. The maximum array size is equal to the available space on the smaller of the two drives. • Any Configuration—For a server configuration that carries forward the local disk configuration without any changes. • No RAID—For a server configuration that removes the RAID and leaves the disk MBR and payload unaltered. • RAID 5 Striped Parity—Data is striped across all disks in the array. Part of the capacity of each disk stores parity information that can be used to reconstruct data if a disk fails. RAID 5 provides good data throughput for applications with high read request rates. • RAID 6 Striped Dual Parity—Data is striped across all disks in the array and two parity disks are used to provide protection against the failure of up to two physical disks. In each row of data blocks, two sets of parity data are stored. • RAID10 Mirrored and Striped— RAID 10 uses mirrored pairs of disks to provide complete data redundancy and high throughput rates. Cisco UCS Manager GUI Configuration Guide, Release 2.0 492 OL-25712-04 Creating Service Profiles Note If you choose No RAID and you apply this policy to a server that already has an operating system with RAID storage configured, the system does not remove the disk contents. Therefore, there may be no visible differences on the server after you apply the No RAID mode. This can lead to a mismatch between the RAID configuration in the policy and the actual disk configuration shown in the Inventory > Storage tab for the server. To make sure that any previous RAID configuration information is removed from a disk, apply a scrub policy that removes all disk information after you apply the No RAID configuration mode. b) If you want to ensure that the server retains the configuration in the local disk configuration policy even if the server is disassociated from the service profile, check the Protect Configuration check box. When a service profile is disassociated from a server and a new service profile associated, the setting for the Protect Configuration property in the new service profile takes precedence and overwrites the setting in the previous service profile. If you disassociate the server from a service profile with this option enabled and then associate it with a new service profile that includes a local disk configuration policy with different properties, the server returns a configuration mismatch error and the association fails. c) Continue with Step 4. Note Step 3 (Optional) To create a local disk configuration policy that will be available to all service profiles, do the following: a) Click the Create Local Disk Configuration Policy link. b) In the Create Local Disk Configuration dialog box, complete the fields. For more information, see Creating a Local Disk Configuration Policy, on page 410. c) Click OK. d) From the Local Storage drop-down list, choose the policy you created. Step 4 In the How would you like to configure SAN storage? field, click one of the following options: Option Description Simple Allows you to create a maximum of two vHBAs for this service profile. Continue with Step 7. Expert Allows you to create an unlimited number of vHBAs for this service profile. Continue with Step 8. No vHBAs Does not include any vHBAs for connections to a Fibre Channel SAN in the service profile. If you are configuring this service profile/template for iSCSI boot, choose this option. Continue with Step 9. Hardware Inherited Uses the vHBAs assigned to the Fibre Channel adapter profile associated with the server. Continue with Step 9. Step 5 (Optional) If you chose the simple SAN storage option, do the following: a) From the WWNN Assignment drop-down list, choose one of the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 493 Creating Service Profiles • Choose Select (pool default used by default) to use the default WWN pool. • Choose one of the options listed under Manual Using OUI and then enter the WWN in the World Wide Node Name field. You can specify a WWNN in the range from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. You can click the here link to verify that the WWNN you specified is available. • Choose a WWN pool name from the list to have a WWN assigned from the specified pool. Each pool name is followed by two numbers in parentheses that show the number of WWNs still available in the pool and the total number of WWNs in the pool. b) In the vHBA 0 (Fabric A) area, complete the following fields: • In the Name field, enter a unique name for the vHBA. • From the Select VSAN drop-down list, choose the name of the VSAN with which this vHBA should be associated. If the VSAN you need is not in the drop-down list, click the Create VSAN link. For more information, see Creating a Named VSAN, on page 335. c) Repeat Step 7b in the vHBA 1 (Fabric B) area to create a VSAN for that vHBA. d) Continue with Step 9. Step 6 (Optional) If you chose the expert SAN storage option, do the following: a) From the WWNN Assignment drop-down list, choose one of the following: • Choose Select (pool default used by default) to use the default WWN pool. • Choose one of the options listed under Manual Using OUI and then enter the WWN in the World Wide Node Name field. You can specify a WWNN in the range from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. You can click the here link to verify that the WWNN you specified is available. • Choose a WWN pool name from the list to have a WWN assigned from the specified pool. Each pool name is followed by two numbers in parentheses that show the number of WWNs still available in the pool and the total number of WWNs in the pool. b) Click Add on the icon bar of the table to open the Create vHBA dialog box. c) Complete the following fields to specify the identity information for the vHBA: Name Description Name field The name of this vHBA. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Cisco UCS Manager GUI Configuration Guide, Release 2.0 494 OL-25712-04 Creating Service Profiles Name Description Use SAN Connectivity Template Check this check box if you want to use a template to create the check box vHBA. Cisco UCS Manager GUI displays the vHBA Template drop-down list from which you can select the appropriate template, and the Adapter Performance Profile area from which you can select an adapter profile. Note Create vHBA Template link You can only select this option if one or more SAN connectivity templates exist in the system. Click this link if you want to create a vHBA template. WWPN Assignment drop-down If you want to: list • Use the default WWPN pool, leave this field set to Select (pool default used by default). • Use the WWPN assigned to the server by the manufacturer, select Hardware Default. • A specific WWPN, select 20:00:00:25:B5:00:00:00, 20:XX:XX:XX:XX:XX:XX:XX, or 5X:XX:XX:XX:XX:XX:XX:XX and enter the WWPN in the WWPN field. To verify that this WWPN is available, click the corresponding link. • A WWPN from a pool, select the pool name from the list. Each pool name is followed by a pair of numbers in parentheses. The first number is the number of available WWN addresses in the pool and the second is the total number of WWPN addresses in the pool. To create a new WWPN pool, click Create WWPN Pool. d) In the VSAN area, complete the following fields: Name Description Fabric ID field The fabric interconnect associated with the component. Select VSAN drop-down list box The VSAN with which this vHBA is associated. Create VSAN link Click this link if you want to create a VSAN. Pin Group drop-down list box The pin group with which this vHBA is associated. Create SAN Pin Group link Click this link if you want to create a pin group. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 495 Creating Service Profiles Name Description Persistent Binding field This can be one of the following: • Disabled • Enabled Max Data Field Size field The maximum size of the Fibre Channel frame payload bytes that the vHBA supports. Enter an integer between 256 and 2112. The default is 2048. Operational Parameters Section Stats Threshold Policy drop-down list box The threshold policy with which this vHBA is associated. e) In the Adapter Performance Profile area, complete the following fields: Name Description Adapter Policy drop-down list box The Fibre Channel adapter policy with which this vHBA is associated. Create Fibre Channel Adapter Click this link if you want to create a Fibre Channel adapter policy. Policy link QoS drop-down list box The quality of service policy with which this vHBA is associated. Create QoS Policy link Click this link if you want to create a QoS policy. f) Click OK. Step 7 Click Next. What to Do Next Complete Page 3: Configuring the Networking Options, on page 496. Page 3: Configuring the Networking Options This procedure directly follows Page 2: Configuring the Storage Options, on page 491. It describes how to configure the networking options, including LAN connectivity, on the Networking page of the Create Service Profile (expert) wizard. Cisco UCS Manager GUI Configuration Guide, Release 2.0 496 OL-25712-04 Creating Service Profiles Procedure Step 1 (Optional) If you plan to assign this service profile to a server with an adapter that supports dynamic vNICs, choose one of the following options from the Dynamic vNIC Connection drop-down list: Option Description Select a Policy to use Enables you to create a service profile without a dynamic vNIC connection policy for a server with an adapter that does not support dynamic vNICs. This option does not include a dynamic vNIC connection policy in the service profile. If you are configuring this service profile/template for iSCSI boot, choose this option. Continue with Step 4. Create a Specific Dynamic vNIC Connection Policy Enables you to create a dynamic vNIC connection policy that can only be accessed by this service profile. Continue with Step 2. Dynamic vNIC Connection Policies Policy_Name Select an existing dynamic vNIC connection policy from the list at the bottom of the drop-down list. Cisco UCS Manager assigns this policy to the service profile. If you do not want use any of the existing policies, but instead want to create a policy that all service profiles can access, continue with Step 3. Otherwise, continue with Step 4. Step 2 (Optional) If you clicked Create a Specific Dynamic vNIC Connection Policy, do the following to create a new dynamic vNIC connection policy that can only be used by this service profile: a) Complete the following fields: Name Description Number of Dynamic vNICs field The number of dynamic vNICs that this policy affects. Adapter Policy drop-down list The adapter profile associated with this policy. The profile must already exist to be included in the drop-down list. b) Continue with Step 4. Step 3 (Optional) To create a dynamic vNIC connection policy that will be available to all service profiles, do the following: a) Click Create Dynamic vNIC Connection Policy. b) In the Create Dynamic vNIC Connect Policy dialog box, complete the fields. For more information, see Creating a Dynamic vNIC Connection Policy. c) Click OK. d) From the Dynamic vNIC Connection drop-down list, choose the policy you created. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 497 Creating Service Profiles e) Continue with Step 4. Step 4 In the How would you like to configure LAN connectivity? field, click one of the following options: Option Description Simple Allows you to create a maximum of two vNICs, in dual fabric mode, for this service profile. Continue with Step 5. Expert Allows you to create an unlimited number of vNICs for this service profile. If you are configuring this service profile/template for iSCSI boot, choose this option. If you are configuring this service profile for iSCSI boot, continue with Step 7. For all other configurations, continue with Step 6. No vNICs Does not include any vNICs for connections to a LAN in the service profile. Any server associated with this service profile cannot be able to communicate with a LAN unless you modify the service profile to add vNICs. Continue with Step 8. Hardware Inherited Uses the vNICs assigned to the Ethernet adapter profile associated with the server. Continue with Step 8. Step 5 (Optional) If you chose the simple LAN connectivity option, do the following: a) In the vNIC 0 (Fabric A) area, complete the following fields: • In the Name field, enter a unique name for the vNIC. • From the Select Native VLAN drop-down list, choose the name of the VLAN with which this vNIC should communicate. If the VLAN you need is not in the drop-down list, click the Create VLAN link. For more information, see Creating a Named VLAN, on page 280. b) Repeat Step 2a in the vNIC 1 (Fabric B) area to create a VLAN for that vNIC. c) Continue with Step 4. Step 6 If you chose the expert LAN connectivity option and are not configuring this service profile for iSCSI boot, do the following: a) Click Add on the icon bar of the table to open the Create vNICs dialog box. b) Complete the following fields to specify the identity information for the vNIC: Name Description Name field The user-defined name for this vNIC. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Cisco UCS Manager GUI Configuration Guide, Release 2.0 498 OL-25712-04 Creating Service Profiles Name Description Use LAN Connectivity Template check box Check this check box if you want to use a template to create the vNIC. Cisco UCS Manager GUI displays the vNIC Template drop-down list from which you can select the appropriate template, and the Adapter Performance Profile area from which you can select an adapter profile. Note You can only select this option if one or more LAN connectivity templates exist in the system. Create vNIC Template link Click this link if you want to create a vNIC template. MAC Address Assignment drop-down list If you want to: • Use the default MAC address pool, leave this field set to Select (pool default used by default). • Use the MAC address assigned to the server by the manufacturer, select Hardware Default. • A specific MAC address, select 02:25:B5:XX:XX:XX and enter the address in the MAC Address field. To verify that this address is available, click the corresponding link. • A MAC address from a pool, select the pool name from the list. Each pool name is followed by a pair of numbers in parentheses. The first number is the number of available MAC addresses in the pool and the second is the total number of MAC addresses in the pool. c) In the Fabric Interconnect area, complete the following fields: Name Description Fabric ID field The fabric interconnect associated with the component. If you want this vNIC to be able to access the second fabric interconnect if the default one is unavailable, check the Enable Failover check box. Note Do not enable fabric failover for the vNIC under the following circumstances: • If the Cisco UCS domain is running in Ethernet Switch Mode. vNIC fabric failover is not supported in that mode. If all Ethernet uplinks on one fabric interconnect fail, the vNICs do not fail over to the other. • if you plan to associate this vNIC with a server that has an adapter which does not support fabric failover, such as the Cisco UCS 82598KR-CI 10-Gigabit Ethernet Adapter. If you do so, Cisco UCS Manager generates a configuration fault when you associate the service profile with the server. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 499 Creating Service Profiles Name Description VLANs table This table lists the VLANs that can be associated with this vNIC. The columns are: • Select—Check the check box in this column for each VLAN you want to use. • Name—The name of the VLAN. • Native VLAN—To designate one of the VLANs as the native VLAN, click the radio button in this column. Create VLAN link Click this link if you want to create a VLAN. MTU field The maximum transmission unit, or packet size, that this vNIC accepts. Enter an integer between 1500 and 9216. Note If the vNIC has an associated QoS policy, the MTU specified here must be equal to or less than the MTU specified in the associated QoS system class. If this MTU value exceeds the MTU value in the QoS system class, packets may be dropped during data transmission. Pin Group drop-down list Choose the LAN pin group you want associated with this vNIC. Create LAN Pin Group link Click this link if you want to create a LAN pin group. Operational Parameters Section Stats Threshold Policy drop-down list The statistics collection policy with which this vNIC is associated. d) In the Adapter Performance Profile area, complete the following fields: Name Description Adapter Policy drop-down list The Ethernet adapter policy with which this vNIC is associated. Create Ethernet Adapter Policy Click this link if you want to create an Ethernet adapter policy. link QoS drop-down list The quality of service policy with which this vNIC is associated. Create QoS Policy link Click this link if you want to create a quality of service policy. Network Control Policy drop-down list The network control policy with which this vNIC is associated. Cisco UCS Manager GUI Configuration Guide, Release 2.0 500 OL-25712-04 Creating Service Profiles Name Description Create Network Control Policy Click this link if you want to create a network control policy. Policy link e) Click OK. Step 7 If you chose the expert LAN connectivity option and are configuring this service profile for iSCSI boot, do the following: a) Click the down arrows to expand the iSCSI vNICs bar. b) Click Add on the icon bar of the table to open the Create iSCSI vNIC dialog box. c) Complete the following fields to specify the identity information for the iSCSI vNIC: Name Description Name field The name of the iSCSI vNIC. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Overlay vNIC drop-down list The LAN vNIC associated with this iSCSI vNIC, if any. iSCSI Adapter Policy drop-down The iSCSI adapter policy associated with this iSCSI vNIC, if any. list Create iSCSI Adapter Policy link Click this link to create a new iSCSI adapter policy that will be available to all iSCSI vNICs. MAC Address field The MAC address associated with this iSCSI vNIC, if any. If the MAC address is not set, Cisco UCS Manager GUI displays Derived. MAC Pool field The MAC pool associated with this iSCSI vNIC, if any. VLAN drop-down list The virtual LAN associated with this iSCSI vNIC. The default VLAN is default. Note For the Cisco UCS M81KR Virtual Interface Card and the Cisco UCS M82-8P Virtual Interface Card, the VLAN that you specify must be the same as the native VLAN on the overlay vNIC. For the Cisco UCS M51KR-B Broadcom BCM57711 adapter, the VLAN that you specify can be any VLAN assigned to the overlay vNIC. d) Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 501 Creating Service Profiles e) Repeat steps b through d to configure additional iSCSI vNICs. Step 8 Click Next. What to Do Next Complete Page 4: Setting the vNIC/vHBA Placement, on page 502. Page 4: Setting the vNIC/vHBA Placement This procedure directly follows Page 3: Configuring the Networking Options, on page 496. It describes how to set the vNIC and vHBA placement options on the vNIC/vHBA Placement page of the Create Service Profile (expert) wizard. Procedure Step 1 From the Select Placement drop-down list, choose one of the following: Option Description Let System Perform Placement Specifies that Cisco UCS Manager determines the vNIC/vHBA placement for the server associated with the service profile. The placement is determined by the order set in the PCI Order table. If you are configuring this service profile/template for iSCSI boot, choose this option. If you are configuring this service profile for iSCSI boot, continue with Step 5. For all configurations, continue with Step 2. Specify Manually Enables you to do the following: • Explicitly assign the vNICs and vHBAs associated with this service profile to a virtual network interface connection (vCon). • Configure the types of vNICs and vHBAs that can be assigned to a vCon, either manually or through a vNIC/vHBA placement policy. Continue with Step 3. vNIC/vHBA Placement Profiles Placement Profile Name Step 2 Assigns an existing vNIC/vHBA placement policy to the service profile. If you choose this option, Cisco UCS Manager displays the details of the policy. If you do not want use any of the existing policies, but instead want to create a policy that all service profiles can access, click Create Placement Policy and continue with Step 4. Otherwise, continue with Step 5. (Optional) If you chose Let System Perform Placement, do the following: a) Use one or more of the following buttons to adjust the order of the vNICs and vHBAs: Cisco UCS Manager GUI Configuration Guide, Release 2.0 502 OL-25712-04 Creating Service Profiles Name Description Move Up button Moves the selected vNIC or VHBA to a higher priority in the list. Move Down button Moves the selected vNIC or vHBA to a lower priority in the list. Delete button Deletes the selected vNIC or vHBA. Reorder button Returns all vNICs and vHBAs to their original order. Modify button Enables you to modify the currently-selected vNIC or vHBA. Note You can change any options for the vNIC or vHBA except its name. b) Continue with Step 5. Step 3 (Optional) If you chose Specify Manually, do the following: a) On the appropriate tab in the vNIC/vHBA table, click a vNIC or vHBA. b) In the Virtual Host Interface table, click a vCON row and if necessary, choose one of the following values from the Selection Preference column: • All—All configured vNICs and vHBAs can be assigned to the vCon, whether they are explicitly assigned to it, unassigned, or dynamic. • Assigned Only—vNICs and vHBAs must be explicitly assigned to the vCon. You can assign them explicitly through the service profile or the properties of the vNIC or vHBA. • Exclude Dynamic—Dynamic vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for all static vNICs and vHBAs, whether they are unassigned or explicitly assigned to it. • Exclude Unassigned—Unassigned vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for dynamic vNICs and vHBAs and for static vNICs and vHBAs that are explicitly assigned to it. c) Click Assign. If you need to undo an assignment, click Remove. d) Repeat Steps a through c until you have assigned all vNICs and vHBAs. e) When you have specified all vNIC and vHBA placements, continue with Step 5. Step 4 If you clicked Create Placement Policy, do the following in the Create Placement Policy dialog box: a) In the Name field, enter a unique name for the placement policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. b) In the Selection Preference column for each Virtual Slot, choose one of the following from the drop-down list: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 503 Creating Service Profiles • All—All configured vNICs and vHBAs can be assigned to the vCon, whether they are explicitly assigned to it, unassigned, or dynamic. • Assigned Only—vNICs and vHBAs must be explicitly assigned to the vCon. You can assign them explicitly through the service profile or the properties of the vNIC or vHBA. • Exclude Dynamic—Dynamic vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for all static vNICs and vHBAs, whether they are unassigned or explicitly assigned to it. • Exclude Unassigned—Unassigned vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for dynamic vNICs and vHBAs and for static vNICs and vHBAs that are explicitly assigned to it. c) Click OK. d) After the dialog box closes, choose the policy you created from the Select Placement drop-down list. Step 5 Click Next. What to Do Next Complete Page 5: Setting the Server Boot Order, on page 504. Page 5: Setting the Server Boot Order This procedure directly follows Page 4: Setting the vNIC/vHBA Placement, on page 502. It describes how to set the server boot order options on the Server Boot Order page of the Create Service Profile (expert) wizard. Tip We recommend that the boot order in a boot policy include either a local disk or a SAN LUN, but not both, to avoid the possibility of the server booting from the wrong storage type. If you configure a local disk and a SAN LUN for the boot order storage type and the operating system or logical volume manager (LVM) is configured incorrectly, the server might boot from the local disk rather than the SAN LUN. For example, on a server with Red Hat Linux installed, where the LVM is configured with default LV names and the boot order is configured with a SAN LUN and a local disk, Linux reports that there are two LVs with the same name and boots from the LV with the lowest SCSI ID, which could be the local disk. Procedure Step 1 From the Boot Policy drop-down list, choose one of the following: Option Description Select Boot Policy to use Assigns the default boot policy to this service profile. Continue with Step 9. Cisco UCS Manager GUI Configuration Guide, Release 2.0 504 OL-25712-04 Creating Service Profiles Option Description Create a Specific Boot Policy Enables you to create a local boot policy that can only be accessed by this service profile. Continue with Step 3. Boot Policies Policy_Name Assigns an existing boot policy to the service profile. If you choose this option, Cisco UCS Manager displays the details of the policy. If you do not want use any of the existing policies but instead want to create a policy that all service profiles can access, click Create Boot Policy and continue with Step 2. Otherwise, choose a policy from the list and continue with Step 9. Step 2 If you clicked Create Boot Policy to create a boot policy that all service profiles and templates can use, do the following: a) In the Create Boot Policy dialog box, enter a unique name and description for the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. b) Continue with Step 3. Step 3 (Optional) To reboot all servers that use this boot policy after you make changes to the boot order, check the Reboot on Boot Order Change check box. In the Cisco UCS Manager GUI, if the Reboot on Boot Order Change check box is checked for a boot policy, and if CD-ROM or Floppy is the last device in the boot order, deleting or adding the device does not directly affect the boot order and the server does not reboot. Step 4 (Optional) If desired, check the Enforce vNIC/vHBA/iSCSI Name check box. • If checked, Cisco UCS Manager displays a configuration error and reports whether one or more of the vNICs, vHBAs, or iSCSI vNICs listed in the Boot Order table match the server configuration in the service profile. • If not checked, Cisco UCS Manager uses the vNICs, vHBAs, or iSCSI vNICs (as appropriate for the boot option) from the server configuration in the service profile. It does not report whether the vNICs, vHBAs, or iSCSI vNICs specified in the boot policy match the server configuration in the service profile. Step 5 To add a local disk, virtual CD-ROM, or virtual floppy to the boot order, do the following: a) Click the down arrows to expand the Local Devices area. b) Click one of the following links to add the device to the Boot Order table: • Add Local Disk • Add CD-ROM • Add Floppy c) Add another boot device to the Boot Order table, or click OK to finish. Step 6 To add a LAN boot to the boot order, do the following: a) Click the down arrows to expand the vNICs area. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 505 Creating Service Profiles b) Click the Add LAN Boot link. c) In the Add LAN Boot dialog box, enter the name of the vNIC that you want to use for the LAN boot in the vNIC field, then click OK. d) Add another device to the Boot Order table, or click OK to finish. Step 7 To add a SAN boot to the boot order, do the following: a) Click the down arrows to expand the vHBAs area. b) Click the Add SAN Boot link. c) In the Add SAN Boot dialog box, complete the following fields, and click OK: Name Description vHBA field Enter the name of the vHBA you want to use for the SAN boot. Type field This can be one of the following: • Primary—The first address defined for the associated boot device class. A boot policy can only have one primary LAN, SAN, or iSCSI boot location. • Secondary—The second address defined for the associated boot device class. Each boot policy can have only one secondary LAN or SAN boot location. The use of the terms primary or secondary boot devices does not imply a boot order. The effective order of boot devices within the same device class is determined by PCIe bus scan order. d) If this vHBA points to a bootable SAN image, click the Add SAN Boot Target link and, in the Add SAN Boot Target dialog box, complete the following fields, then click OK: Name Description Boot Target LUN field The LUN that corresponds to the location of the boot image. Boot Target WWPN field The WWPN that corresponds to the location of the boot image. Cisco UCS Manager GUI Configuration Guide, Release 2.0 506 OL-25712-04 Creating Service Profiles Name Description Type field This can be one of the following: • Primary—The first address defined for the associated boot device class. A boot policy can only have one primary LAN, SAN, or iSCSI boot location. • Secondary—The second address defined for the associated boot device class. Each boot policy can have only one secondary LAN or SAN boot location. The use of the terms primary or secondary boot devices does not imply a boot order. The effective order of boot devices within the same device class is determined by PCIe bus scan order. e) Add another boot device to the Boot Order table, or click OK to finish. Step 8 To add an iSCSI boot to the boot order, do the following: a) In the Specific Boot Policy area, click the down arrows to expand the iSCSI vNICs area. b) In the iSCSI vNICs area, double-click the iSCSI vNICs from which you want to boot the server to add them to the Boot Order table. c) In the iSCSI vNICs area, click the Set Boot Parameters link. If there are two iSCSI vNICs, choose the one for which you want to set boot parameters. d) Complete the fields in the Set iSCSI Boot Parameters dialog box and click OK. For more information about the fields, see Setting iSCSI Boot Parameters, on page 454. e) (Optional) Repeat steps c and d to set boot parameters for additional iSCSI vNICs. Step 9 If you created a new boot policy accessible to all service profiles and template, choose that policy from the Boot Policy drop-down list. Step 10 Click Next. What to Do Next Complete Page 6: Adding the Maintenance Policy, on page 507. Page 6: Adding the Maintenance Policy This procedure directly follows Page 5: Setting the Server Boot Order, on page 504. It describes how to add a maintenance policy to the service profile on the Maintenance Policy page of the Create Service Profile (expert) wizard. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 507 Creating Service Profiles Procedure Step 1 From the Maintenance Policy drop-down list, choose one of the following: Option Description Select a Maintenance Policy to Assigns the default maintenance policy to this service profile. Use (default policy shown) Continue with Step 4. Maintenance Policies Policy_Name Assigns an existing maintenance policy to the service profile. If you choose this option, Cisco UCS Manager displays the details of the policy. If you do not want use any of the existing policies but instead want to create a policy that all service profiles can access, click Create Maintenance Policy and continue with Step 2. Otherwise, choose a policy from the list and continue with Step 4. Step 2 If you clicked Create Maintenance Policy to create a maintenance policy that all service profiles and templates can use, do the following: a) In the Create Maintenance Policy dialog box, complete the following fields: Name Description Name field The name of the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A description of the policy. We recommend that you include information about where and when the policy should be used. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Cisco UCS Manager GUI Configuration Guide, Release 2.0 508 OL-25712-04 Creating Service Profiles Name Description Reboot Policy field When a service profile is associated with a server, or when changes are made to a service profile that is already associated with a server, the server needs to be rebooted to complete the process. The Reboot Policy field determines when the reboot occurs for servers associated with any service profiles that include this maintenance policy. This can be one of the following: • Immediate—The server is rebooted automatically as soon as the service profile association is complete or service profile changes are saved by the user. • User Ack—The user must reboot the server manually after the service profile association is complete or changes are made. • Timer Automatic—Cisco UCS defers all service profile associations and changes until the maintenance window defined by the schedule shown in the Schedule field. Schedule drop-down list If the Reboot Policy is set to Timer Automatic, the schedule specifies when maintenance operations can be applied to the server. Cisco UCS reboots the server and completes the service profile changes at the scheduled time. b) Click OK and continue with Step 3. Step 3 Step 4 If you created a new boot policy accessible to all service profiles and template, choose that policy from the Maintenance Policy drop-down list. Click Next. What to Do Next Complete Page 7: Specifying the Server Assignment, on page 509. Page 7: Specifying the Server Assignment This procedure directly follows Page 6: Adding the Maintenance Policy, on page 507. It describes how to specify the way a server is assigned and which firmware packages are associated with the service profile on the Server Assignment page of the Create Service Profile (expert) wizard. Procedure Step 1 From the Server Assignment drop-down list, choose one of the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 509 Creating Service Profiles Option Description Assign Later Allows you to assign a server after you have created and configured the service profile. Continue with Step 6. Pre-provision a slot Specifies the chassis and slot that contains the server which will be assigned to the service profile. If the server is not in the slot or is otherwise unavailable, the service profile will be associated with the server when it becomes available. Continue with Step 2. Select existing Server Displays a table of available, unassociated servers that you can use to select the server which will be assigned to the service profile. Continue with Step 3. Select from a Pool Pool_Name Select a server pool from the list at the bottom of the drop-down list. Cisco UCS Manager assigns a server from this pool to the service profile. Continue with Step 4. Step 2 If you chose Pre-provision a slot, do the following: a) In the Chassis Id field, enter the number of the chassis where the selected server is located. b) In the Slot Id field, enter the number of the slot where the selected server is located. c) Continue with Step 4. Step 3 If you chose Select existing Server, do the following: a) In the Select column of the table of available servers, click the radio button for the server that meets the needs of this service profile. b) Continue with Step 4. Step 4 In the Power State field, click one of the following radio buttons to set the power state that will be applied to the server when it is associated with this service profile: • Down if you want the server to be powered down before the profile is associated with the server. • Up if you want the server to be powered up before the profile is associated with the server By default, the server is powered up. Step 5 If you want to restrict the migration of the service profile after it has been associated with a server, check the Restrict Migration. check box. 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. Step 6 (Optional) In the Firmware Management area, do the following to use policies to update the firmware on the server associated with the service profile: a) Click the down arrows on the Firmware Management bar to expand the area. b) Complete the following fields: Cisco UCS Manager GUI Configuration Guide, Release 2.0 510 OL-25712-04 Creating Service Profiles Name Description Host Firmware drop-down list To associate a host firmware package with this service profile, choose its name from the drop-down list. Create Host Firmware Package Click this link if you want to create a host firmware package. link Management Firmware drop-down list To associate a management firmware package with this service profile, choose its name from the drop-down list. Create Management Firmware Click this link if you want to create a management firmware package. Package link Step 7 Click Next. What to Do Next Complete Page 8: Adding Operational Policies, on page 511. Page 8: Adding Operational Policies This procedure directly follows Page 7: Specifying the Server Assignment, on page 509. It describes how to add operational policies to the service profile on the Operational Policies page of the Create Service Profile (expert) wizard. These policies are optional. Procedure Step 1 To override the default BIOS settings and configure them through the service profile, click the down arrows to expand the BIOS Configuration bar and do one of the following: • To add an existing policy, select the desired BIOS policy from the BIOS Policy drop-down list . • To create a BIOS policy that is available to all service profiles, click Create BIOS Policy, complete the fields in the dialog box, and then select that policy from the BIOS Policy drop-down list . For more information about how to create a BIOS policy, see Creating a BIOS Policy, on page 403. Step 2 To provide external access to the CIMC on the server, click the down arrows to expand the External IPMI Management Configuration bar and add an IPMI profile and a serial over LAN policy. If you do not want to provide external access, continue with Step 4. Step 3 To add an IPMI profile to the service profile, do one of the following: • To add an existing policy, select the desired IPMI profile from the IPMI Access Profile drop-down list. • If the IPMI Access Profile drop-down list does not include an IPMI profile with the desired user access, click the Create Access IPMI Profile link to create an IPMI profile that is available to all service profiles and then select that profile from the IPMI Access Profile drop-down list. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 511 Creating Service Profiles For more information about how to create an IPMI profile, see Creating an IPMI Access Profile, on page 405. Step 4 To add a Serial over LAN policy to the service profile, do one of the following: • To add an existing policy, select the desired Serial over LAN policy from the SoL Configuration Profile drop-down list. • To create a Serial over LAN policy that is only available to service profile created from this template, select Create a Specific SoL Policy from the SoL Configuration Profile drop-down list and complete the Admin State field and the Speed drop-down list. • To create a Serial over LAN policy that is available to all service profile templates, click the Create Serial over LAN Policy link, complete the fields in the dialog box, and then select that policy from the SoL Configuration Profile drop-down list. For more information about how to create a serial over LAN policy, see Creating a Serial over LAN Policy, on page 415. Step 5 To configure the management IP required for external access to the CIMC on the server, click the down arrows to expand the Management IP Address bar and do the following: a) Click one of the following radio buttons: • None—No management IP address is assigned to the service profile. The management IP address is set based on the CIMC management IP address settings on the server. • Static—A static management IP address is assigned to the service profile, based on the information entered in this area. • Pooled—A management IP address is assigned to the service profile from the management IP address pool. b) If you selected static, complete the following fields: Step 6 Field Description IP Address The static IPv4 address to be assigned to the service profile Subnet Mask The subnet mask for the IP address. Default Gateway The default gateway that the IP address should use. To monitor thresholds and collect statistics for the associated server, click the down arrows to expand the Monitoring Configuration (Thresholds) bar and do one of the following: • To add an existing policy, select the desired threshold policy from the Threshold Policy drop-down list. • To create a threshold policy that is available to all service profiles, click the Create Threshold Policy link, complete the fields in the dialog box, and then select that policy from the Threshold Policy drop-down list. For more information about how to create a threshold policy, see Creating a Server and Server Component Threshold Policy , on page 666. Cisco UCS Manager GUI Configuration Guide, Release 2.0 512 OL-25712-04 Creating Service Profiles Step 7 To associate a power control policy with the service profile, click the down arrows to expand the Power Control Policy Configuration bar and do one of the following: • To add an existing policy, select the desired power control policy from the Power Control Policy drop-down list. • To create a power control policy that is available to all service profiles, click the Create Power Control Policy link , complete the fields in the dialog box, and then select that policy from the Power Control Policy drop-down list. For more information about how to create a power control policy, see Creating a Power Control Policy, on page 569. Step 8 To associate a scrub policy with the service profile, click the down arrows to expand the Scrub Policy bar and do one of the following: • To add an existing policy, select the desired scrub policy from the Scrub Policy drop-down list . • To create a scrub policy that is available to all service profiles, click the Create Scrub Policy link , complete the fields in the dialog box, and then select that policy from the Scrub Policy drop-down list . For more information about how to create a scrub policy, see Creating a Scrub Policy, on page 414. Step 9 Click Finish. Creating a Service Profile that Inherits Server Identity Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization where you want to create the service profile. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click the organization and select Create Service Profile. In the Naming area of the Create Service Profile dialog box, complete the following fields: a) In the Name field, enter a unique name that you can use to identify the service profile. This name can be between 2 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and this name must be unique across all service profiles and service profile templates within the same organization. b) In the Description field, enter a description of this service profile. Step 6 In the vNICs area of the Create Service Profile dialog box, complete the following fields: Name Description Primary vNIC Section Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 513 Creating Service Profiles Name Description Primary vNIC check box Check this check box if you want to create a vNIC for this service profile. If you check this box, Cisco UCS Manager GUI displays the rest of the fields in this section. Name field The name of the vNIC. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Fabric field The fabric interconnect that this vNIC is associated with. Network drop-down list The LAN that this vNIC is associated with. Secondary vNIC Section Secondary vNIC check box Check this check box if you want to create a second vNIC for this service profile. If you check this box, Cisco UCS Manager GUI displays the rest of the fields in this section. Name field The name of the vNIC. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Step 7 Fabric field The fabric interconnect that this vNIC is associated with. Network drop-down list The LAN that this vNIC is associated with. In the vHBAs area of the Create Service Profile dialog box, complete the following fields: Name Description Primary vHBA Section Primary vHBA check box Check this check box if you want to create a vHBA for this service profile. If you check this box, Cisco UCS Manager GUI displays the rest of the fields in this section. Name field The name of the vHBA. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Cisco UCS Manager GUI Configuration Guide, Release 2.0 514 OL-25712-04 Creating Service Profiles Name Description Fabric field The fabric interconnect that this vHBA is associated with. Do not associate the primary vHBA with the same fabric as the secondary vHBA. Secondary vHBA Section Secondary vHBA check box Check this check box if you want to create a second vHBA for this service profile. If you check this box, Cisco UCS Manager GUI displays the rest of the fields in this section. Name field The name of the vHBA. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Fabric field Step 8 The fabric interconnect that this vHBA is associated with. Do not associate the secondary vHBA with the same fabric as the primary vHBA. In the Boot Order area of the Create Service Profile dialog box, complete the following fields: Name Description Primary Boot Device Section Primary Boot Device check box Check this check box if you want to set a boot device for this service profile. If you check this box, Cisco UCS Manager GUI displays the rest of the fields in this section. Type field This can be one of the following: • local-disk—The server boots from its local disk. Note If you select this option, you cannot select local-disk or san as your secondary boot type. • san—The server boots from an image stored in a SAN. If you select this option, Cisco UCS Manager GUI displays the SAN area. • Lan—The server boots from the LAN. If you select this option, Cisco UCS Manager GUI displays the Network area that lets you specify which vNIC the server should use for the PXE boot. • CD-ROM—The server boots from a virtual CD-ROM. • Floppy—The server boots from a virtual floppy. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 515 Creating Service Profiles Name Description SAN area If Type is set to san, this area contains the following fields: • vHBA—The vHBA used to access the SAN boot image • LUN—The LUN that corresponds to the location of the boot image • WWN—The WWN that corresponds to the location of the boot image Network (PXE) area If Type is set to lan, this area contains the vNIC drop-down list from which you can choose the vNIC from which the server should boot. Secondary Boot Device Section Secondary Boot Device check box Check this check box if you want to set a second boot device for this service profile. If you check this box, Cisco UCS Manager GUI displays the rest of the fields in this section. Type field This can be one of the following: • local-disk—The server boots from its local disk. • san—The server boots from an image stored in a SAN. If you select this option, Cisco UCS Manager GUI displays the SAN area. • Lan—The server boots from the LAN. If you select this option, Cisco UCS Manager GUI displays the Network area that lets you specify which vNIC the server should use for the PXE boot. • CD-ROM—The server boots from a virtual CD-ROM. • Floppy—The server boots from a virtual floppy. SAN area If Type is set to san, this area contains the following field: • vHBA—The vHBA used to access the SAN boot image • LUN—The LUN that corresponds to the location of the boot image • WWN—The WWN that corresponds to the location of the boot image Network (PXE) area If Type is set to Lan, this area contains the vNIC drop-down list from which you can choose the vNIC from which the server should boot. Step 9 (Optional) In the Select column of the Server Association (optional) area, click the radio button for a server to associate this service profile with that server. Step 10 Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 516 OL-25712-04 Creating Service Profiles Creating a Hardware Based Service Profile for a Blade Server You cannot move a hardware based service profile to another server. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server for which you want to create a hardware based service profile. In the Work pane, click the General tab. Step 5 In the Actions area, click Create Service Profile. In the Create Service Profile for Server dialog box, do the following: a) From the Create Service Profile in Organization drop-down list, select the organization in which you want to create the service profile. b) Click the Hardware Based Service Profile radio button. c) In the Name field, enter a unique name for the service profile. This name can be between 2 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and this name must be unique across all service profiles and service profile templates within the same organization. Step 6 d) If you want Cisco UCS Manager to create vNICs for the service profile, check the Create Default vNICs check box. e) If you want Cisco UCS Manager to create vHBAs for the service profile, check the Create Default vHBAs check box. f) Click OK. Cisco UCS Manager inherits and automatically applies the identity and configuration information in the server, creates the service profile, and associates it with the server. Creating a Hardware Based Service Profile for a Rack-Mount Server You cannot move a hardware based service profile to another server. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Choose the server for which you want to create a hardware based service profile. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Create Service Profile. In the Create Service Profile for Server dialog box, do the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 517 Working with Service Profile Templates a) From the Create Service Profile in Organization drop-down list, select the organization in which you want to create the service profile. b) Click the Hardware Based Service Profile radio button. c) In the Name field, enter a unique name for the service profile. This name can be between 2 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and this name must be unique across all service profiles and service profile templates within the same organization. d) If you want Cisco UCS Manager to create vNICs for the service profile, check the Create Default vNICs check box. e) If you want Cisco UCS Manager to create vHBAs for the service profile, check the Create Default vHBAs check box. f) Click OK. Cisco UCS Manager inherits and automatically applies the identity and configuration information in the server, creates the service profile, and associates it with the server. Working with Service Profile Templates Creating a Service Profile Template Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profile Templates. Expand the node for the organization where you want to create the service profile template. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click the organization and choose Create Service Profile Template. In the Create Service Profile Template wizard, complete the following: • Page 1: Identifying the Service Profile Template, on page 519 • Page 2: Specifying the Storage Options, on page 520 • Page 3: Specifying the Networking Options, on page 524 • Page 4: Setting the vNIC/vHBA Placement, on page 530 • Page 5: Setting the Server Boot Order, on page 532 • Page 6: Adding the Maintenance Policy, on page 535 • Page 7: Specifying the Server Assignment Options, on page 537 • Page 8: Adding Operational Policies, on page 539 Cisco UCS Manager GUI Configuration Guide, Release 2.0 518 OL-25712-04 Working with Service Profile Templates Page 1: Identifying the Service Profile Template This procedure directly follows the steps in Creating a Service Profile Template, on page 518. It describes how to set the identity of a service profile template on the Identify Service Profile Template page of the Create Service Profile Template wizard. Procedure Step 1 In the Name field, enter a unique name that you can use to identify this service profile template. This name can be between 2 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and this name must be unique across all service profiles and service profile templates within the same organization. This name must be unique within the organization or sub-organization in which you are creating the service profile. Step 2 In the Type field, click one of the following radio buttons: • Initial Template—Any service profiles created from this template are not updated if the template changes • Updating Template—Any service profiles created from this template are updated if the template changes Step 3 From the UUID Assignment drop-down list, choose one of the following: Option Description Select (pool default used by default) Assigns a UUID from the default UUID Suffix pool. Hardware Default Uses the UUID assigned to the server by the manufacturer. If you choose this option, the UUID remains unassigned until the service profile is associated with a server. At that point, the UUID is set to the UUID value assigned to the server by the manufacturer. If the service profile is later moved to a different server, the UUID is changed to match the new server. Pools Pool_Name Assigns a UUID from the UUID Suffix pool that you select from the list at the bottom of the drop-down list. Each pool name is followed by two numbers in parentheses that show the number of UUIDs still available in the pool and the total number of UUIDs in the pool. Step 4 (Optional) In the text box, enter a description of this service profile template. A user-defined description of the service profile template. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Step 5 Click Next. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 519 Working with Service Profile Templates What to Do Next Complete the steps in Page 2: Specifying the Storage Options, on page 520. Page 2: Specifying the Storage Options This procedure directly follows Page 1: Identifying the Service Profile Template, on page 519. It describes how to configure the storage options for a service profile template on the Storage page of the Create Service Profile Template wizard. Procedure Step 1 From the Local Storage drop-down list, choose one of the following: Option Description Select Local Storage Policy to Assigns the default local disk storage policy to every service profile created use from this template. Continue with Step 4. Create a Specific Storage Policy Enables you to create a local disk policy that can only be accessed by a service profile created from this template. Continue with Step 2. Storage Policies Policy_Name Allows you to choose an existing local disk policy from the list at the bottom of the drop-down list. Cisco UCS Manager assigns this policy to every service profile created from this template. If you do not want use any of the existing policies but instead want to create a new policy that all service profiles and templates can access, continue with Step 3. Otherwise, continue with Step 4. Step 2 (Optional) If you chose Create a Specific Storage Policy and want to create a new policy that can only be used by service profiles created from this service profile template, do the following: a) From the Mode drop-down list, choose one of the following: • No Local Storage—For a diskless server or a SAN only configuration. If you select this option, you cannot associate any service profile which uses this policy with a server that has a local disk. • RAID 0 Striped—Data is striped across all disks in the array, providing fast throughput. There is no data redundancy, and all data is lost if any disk fails. • RAID 1 Mirrored—Data is written to two disks, providing complete data redundancy if one disk fails. The maximum array size is equal to the available space on the smaller of the two drives. • Any Configuration—For a server configuration that carries forward the local disk configuration without any changes. • No RAID—For a server configuration that removes the RAID and leaves the disk MBR and payload unaltered. Cisco UCS Manager GUI Configuration Guide, Release 2.0 520 OL-25712-04 Working with Service Profile Templates • RAID 5 Striped Parity—Data is striped across all disks in the array. Part of the capacity of each disk stores parity information that can be used to reconstruct data if a disk fails. RAID 5 provides good data throughput for applications with high read request rates. • RAID 6 Striped Dual Parity—Data is striped across all disks in the array and two parity disks are used to provide protection against the failure of up to two physical disks. In each row of data blocks, two sets of parity data are stored. • RAID10 Mirrored and Striped— RAID 10 uses mirrored pairs of disks to provide complete data redundancy and high throughput rates. Note If you choose No RAID and you apply this policy to a server that already has an operating system with RAID storage configured, the system does not remove the disk contents. Therefore, there may be no visible differences on the server after you apply the No RAID mode. This can lead to a mismatch between the RAID configuration in the policy and the actual disk configuration shown in the Inventory > Storage tab for the server. To make sure that any previous RAID configuration information is removed from a disk, apply a scrub policy that removes all disk information after you apply the No RAID configuration mode. b) If you want to ensure that the server retains the configuration in the local disk configuration policy even if the server is disassociated from the service profile, check the Protect Configuration check box. When a service profile is disassociated from a server and a new service profile associated, the setting for the Protect Configuration property in the new service profile takes precedence and overwrites the setting in the previous service profile. If you disassociate the server from a service profile with this option enabled and then associate it with a new service profile that includes a local disk configuration policy with different properties, the server returns a configuration mismatch error and the association fails. c) Continue with Step 4. Note Step 3 (Optional) To create a local disk configuration policy that will be available to all service profiles and templates, do the following: a) Click the Create Local Disk Configuration Policy link. b) In the Create Local Disk Configuration dialog box, complete the fields. For more information, see Creating a Local Disk Configuration Policy, on page 410. c) Click OK. d) From the Local Storage drop-down list, choose the policy you created. Step 4 In the How would you like to configure SAN storage? field, click one of the following options: Option Description Simple Allows you to create a maximum of two vHBAs for every service profile created from this template. Continue with Step 5. Expert Allows you to create an unlimited number of vHBAs for every service profile created from this template. Continue with Step 6. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 521 Working with Service Profile Templates Option Description No vHBAs Does not include any vHBAs for connections to a Fibre Channel SAN in a service profile created from this template. If you are configuring this service profile/template for iSCSI boot, choose this option. Continue with Step 7. Step 5 (Optional) If you chose the simple SAN storage option, do the following: a) From the WWNN Assignment drop-down list, choose one of the following: • Choose Select (pool default used by default) to use the default WWN pool. • Choose one of the options listed under Manual Using OUI and then enter the WWN in the World Wide Node Name field. You can specify a WWNN in the range from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. You can click the here link to verify that the WWNN you specified is available. • Choose a WWN pool name from the list to have a WWN assigned from the specified pool. Each pool name is followed by two numbers in parentheses that show the number of WWNs still available in the pool and the total number of WWNs in the pool. b) In the vHBA 0 (Fabric A) area, complete the following fields: • In the Name field, enter a unique name for the vHBA. • From the Select VSAN drop-down list, choose the name of the VSAN with which this vHBA should be associated. If the VSAN you need is not in the drop-down list, click the Create VSAN link. For more information, see Creating a Named VSAN, on page 335. c) Repeat Step 7b in the vHBA 1 (Fabric B) area to create a VSAN for that vHBA. d) Continue with Step 9. Step 6 (Optional) If you chose the expert SAN storage option, do the following: a) From the WWNN Assignment drop-down list, choose one of the following: • Choose Select (pool default used by default) to use the default WWN pool. • Choose one of the options listed under Manual Using OUI and then enter the WWN in the World Wide Node Name field. You can specify a WWNN in the range from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. You can click the here link to verify that the WWNN you specified is available. • Choose a WWN pool name from the list to have a WWN assigned from the specified pool. Each pool name is followed by two numbers in parentheses that show the number of WWNs still available in the pool and the total number of WWNs in the pool. b) Click Add on the icon bar of the table to open the Create vHBA dialog box. c) Complete the following fields to specify the identity information for the vHBA: Cisco UCS Manager GUI Configuration Guide, Release 2.0 522 OL-25712-04 Working with Service Profile Templates Name Description Name field The name of this vHBA. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Use SAN Connectivity Template Check this check box if you want to use a template to create the check box vHBA. Cisco UCS Manager GUI displays the vHBA Template drop-down list from which you can select the appropriate template, and the Adapter Performance Profile area from which you can select an adapter profile. Note Create vHBA Template link You can only select this option if one or more SAN connectivity templates exist in the system. Click this link if you want to create a vHBA template. WWPN Assignment drop-down If you want to: list • Use the default WWPN pool, leave this field set to Select (pool default used by default). • Use the WWPN assigned to the server by the manufacturer, select Hardware Default. • A specific WWPN, select 20:00:00:25:B5:00:00:00, 20:XX:XX:XX:XX:XX:XX:XX, or 5X:XX:XX:XX:XX:XX:XX:XX and enter the WWPN in the WWPN field. To verify that this WWPN is available, click the corresponding link. • A WWPN from a pool, select the pool name from the list. Each pool name is followed by a pair of numbers in parentheses. The first number is the number of available WWN addresses in the pool and the second is the total number of WWPN addresses in the pool. To create a new WWPN pool, click Create WWPN Pool. d) In the VSAN area, complete the following fields: Name Description Fabric ID field The fabric interconnect associated with the component. Select VSAN drop-down list box The VSAN with which this vHBA is associated. Create VSAN link Click this link if you want to create a VSAN. Pin Group drop-down list box The pin group with which this vHBA is associated. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 523 Working with Service Profile Templates Name Description Create SAN Pin Group link Click this link if you want to create a pin group. Persistent Binding field This can be one of the following: • Disabled • Enabled Max Data Field Size field The maximum size of the Fibre Channel frame payload bytes that the vHBA supports. Enter an integer between 256 and 2112. The default is 2048. Operational Parameters Section Stats Threshold Policy drop-down list box The threshold policy with which this vHBA is associated. e) In the Adapter Performance Profile area, complete the following fields: Name Description Adapter Policy drop-down list box The Fibre Channel adapter policy with which this vHBA is associated. Create Fibre Channel Adapter Click this link if you want to create a Fibre Channel adapter policy. Policy link QoS drop-down list box The quality of service policy with which this vHBA is associated. Create QoS Policy link Click this link if you want to create a QoS policy. f) Click OK. Step 7 Click Next. What to Do Next Complete Page 3: Specifying the Networking Options, on page 524. Page 3: Specifying the Networking Options This procedure directly follows Page 2: Specifying the Storage Options, on page 520. It describes how to configure the networking options, including LAN connectivity, on the Networking page of the Create Service Profile Template wizard. Cisco UCS Manager GUI Configuration Guide, Release 2.0 524 OL-25712-04 Working with Service Profile Templates Procedure Step 1 (Optional) If you plan to assign service profiles created from this template to a server with an adapter that supports dynamic vNICs, choose one of the following options from the Dynamic vNIC Connection drop-down list: Option Description Select a Policy to use Enables you to create a service profile template without a dynamic vNIC connection policy for a server with an adapter that does not support dynamic vNICs. This option does not include a dynamic vNIC connection policy in the template. If you are configuring this service profile/template for iSCSI boot, choose this option. Continue with Step 4. Create a Specific Dynamic vNIC Connection Policy Enables you to create a dynamic vNIC connection policy that can only be accessed by this service profile template. Continue with Step 2. Dynamic vNIC Connection Policies Policy_Name Select an existing dynamic vNIC connection policy from the list at the bottom of the drop-down list. Cisco UCS Manager assigns this policy to the service profile template. If you do not want use any of the existing policies, but instead want to create a policy that all service profiles and templates can access, continue with Step 3. Otherwise, continue with Step 4. Step 2 (Optional) If you clicked Create a Specific Dynamic vNIC Connection Policy, do the following to create a new dynamic vNIC connection policy that can only be used by service profiles created from this template: a) Complete the following fields: Name Description Number of Dynamic vNICs field The number of dynamic vNICs that this policy affects. Adapter Policy drop-down list The adapter profile associated with this policy. The profile must already exist to be included in the drop-down list. b) Continue with Step 4. Step 3 (Optional) To create a dynamic vNIC connection policy that will be available to all service profiles and templates, do the following: a) Click Create Dynamic vNIC Connection Policy. b) In the Create Dynamic vNIC Connect Policy dialog box, complete the fields. For more information, see the Cisco UCS Manager VM-FEX configuration guides. c) Click OK. d) From the Dynamic vNIC Connection drop-down list, choose the policy you created. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 525 Working with Service Profile Templates e) Continue with Step 4. Step 4 In the How would you like to configure LAN connectivity? field, click one of the following options: Option Description Simple Allows you to create a maximum of two vNICs, in dual fabric mode, for every service profile created from this template. Continue with Step 5. Expert Allows you to create an unlimited number of vNICs for every service profile created from this template. If you are configuring this service profile for iSCSI boot, continue with Step 7. For all other configurations, continue with Step 6. No vNICs Does not include any vNICs for connections to a LAN in a service profile created from this template. Any server associated with these service profiles cannot communicate with a LAN unless you modify the individual service profile later. Continue with Step 8. Step 5 (Optional) If you chose the simple LAN connectivity option and are not configuring this service profile for iSCSI boot, do the following: a) In the vNIC 0 (Fabric A) area: • In the Name field, enter a unique name for the vNIC. • From the Select Native VLAN drop-down list, choose the name of the VLAN with which this vNIC should communicate. If the VLAN you need is not in the drop-down list, click the Create VLAN link. For more information, see Creating a Named VLAN, on page 280. b) Repeat Step 2a in the vNIC 1 (Fabric B) area to create a VLAN for that vNIC. c) Continue with Step 4. Step 6 If you chose the expert LAN connectivity option, do the following: a) Click Add on the icon bar of the table to open the Create vNICs dialog box. b) Complete the following fields to specify the identity information for the vNIC: Name Description Name field The user-defined name for this vNIC. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Cisco UCS Manager GUI Configuration Guide, Release 2.0 526 OL-25712-04 Working with Service Profile Templates Name Description Use LAN Connectivity Template check box Check this check box if you want to use a template to create the vNIC. Cisco UCS Manager GUI displays the vNIC Template drop-down list from which you can select the appropriate template, and the Adapter Performance Profile area from which you can select an adapter profile. Note You can only select this option if one or more LAN connectivity templates exist in the system. Create vNIC Template link Click this link if you want to create a vNIC template. MAC Address Assignment drop-down list If you want to: • Use the default MAC address pool, leave this field set to Select (pool default used by default). • Use the MAC address assigned to the server by the manufacturer, select Hardware Default. • A specific MAC address, select 02:25:B5:XX:XX:XX and enter the address in the MAC Address field. To verify that this address is available, click the corresponding link. • A MAC address from a pool, select the pool name from the list. Each pool name is followed by a pair of numbers in parentheses. The first number is the number of available MAC addresses in the pool and the second is the total number of MAC addresses in the pool. c) In the Fabric Interconnect area, complete the following fields: Name Description Fabric ID field The fabric interconnect associated with the component. If you want this vNIC to be able to access the second fabric interconnect if the default one is unavailable, check the Enable Failover check box. Note Do not enable fabric failover for the vNIC under the following circumstances: • If the Cisco UCS domain is running in Ethernet Switch Mode. vNIC fabric failover is not supported in that mode. If all Ethernet uplinks on one fabric interconnect fail, the vNICs do not fail over to the other. • if you plan to associate this vNIC with a server that has an adapter which does not support fabric failover, such as the Cisco UCS 82598KR-CI 10-Gigabit Ethernet Adapter. If you do so, Cisco UCS Manager generates a configuration fault when you associate the service profile with the server. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 527 Working with Service Profile Templates Name Description VLANs table This table lists the VLANs that can be associated with this vNIC. The columns are: • Select—Check the check box in this column for each VLAN you want to use. • Name—The name of the VLAN. • Native VLAN—To designate one of the VLANs as the native VLAN, click the radio button in this column. Create VLAN link Click this link if you want to create a VLAN. MTU field The maximum transmission unit, or packet size, that this vNIC accepts. Enter an integer between 1500 and 9216. Note If the vNIC has an associated QoS policy, the MTU specified here must be equal to or less than the MTU specified in the associated QoS system class. If this MTU value exceeds the MTU value in the QoS system class, packets may be dropped during data transmission. Pin Group drop-down list Choose the LAN pin group you want associated with this vNIC. Create LAN Pin Group link Click this link if you want to create a LAN pin group. Operational Parameters Section Stats Threshold Policy drop-down list The statistics collection policy with which this vNIC is associated. d) In the Adapter Performance Profile area, complete the following fields: Name Description Adapter Policy drop-down list The Ethernet adapter policy with which this vNIC is associated. Create Ethernet Adapter Policy Click this link if you want to create an Ethernet adapter policy. link QoS drop-down list The quality of service policy with which this vNIC is associated. Create QoS Policy link Click this link if you want to create a quality of service policy. Network Control Policy drop-down list The network control policy with which this vNIC is associated. Cisco UCS Manager GUI Configuration Guide, Release 2.0 528 OL-25712-04 Working with Service Profile Templates Name Description Create Network Control Policy Click this link if you want to create a network control policy. Policy link e) Click OK. Step 7 If you chose the expert LAN connectivity option and are configuring this service profile for iSCSI boot, do the following: a) Click the down arrows to expand the iSCSI vNICs bar. b) Click Add on the icon bar of the table to open the Create iSCSI vNIC dialog box. c) Complete the following fields to specify the identity information for the iSCSI vNIC: Name Description Name field The name of the iSCSI vNIC. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Overlay vNIC drop-down list The LAN vNIC associated with this iSCSI vNIC, if any. iSCSI Adapter Policy drop-down The iSCSI adapter policy associated with this iSCSI vNIC, if any. list Create iSCSI Adapter Policy link Click this link to create a new iSCSI adapter policy that will be available to all iSCSI vNICs. MAC Address field The MAC address associated with this iSCSI vNIC, if any. If the MAC address is not set, Cisco UCS Manager GUI displays Derived. MAC Pool field The MAC pool associated with this iSCSI vNIC, if any. VLAN drop-down list The virtual LAN associated with this iSCSI vNIC. The default VLAN is default. Note For the Cisco UCS M81KR Virtual Interface Card and the Cisco UCS M82-8P Virtual Interface Card, the VLAN that you specify must be the same as the native VLAN on the overlay vNIC. For the Cisco UCS M51KR-B Broadcom BCM57711 adapter, the VLAN that you specify can be any VLAN assigned to the overlay vNIC. d) Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 529 Working with Service Profile Templates e) Repeat steps b through d to create additional iSCSI vNICs. Step 8 Click Next. What to Do Next Complete Page 4: Setting the vNIC/vHBA Placement, on page 530. Page 4: Setting the vNIC/vHBA Placement This procedure directly follows Page 3: Specifying the Networking Options, on page 524. It describes how to set the vNIC and vHBA placement options on the vNIC/vHBA Placement page of the Create Service Profile Template wizard. Procedure Step 1 From the Select Placement drop-down list, choose one of the following: Option Description Let System Perform Placement Specifies that Cisco UCS Manager determines the vNIC/vHBA placement for all servers associated with a service profile created from this template. The placement is determined by the order set in the PCI Order table. If you are configuring this service profile/template for iSCSI boot, choose this option. If you are configuring this service profile for iSCSI boot, continue with Step 5. For all configurations, continue with Step 2. Specify Manually Enables you to do the following: • Explicitly assign the vNICs and vHBAs associated with this service profile template to a virtual network interface connection (vCon). • Configure the types of vNICs and vHBAs that can be assigned to a vCon, either manually or through a vNIC/vHBA placement policy. Continue with Step 3. vNIC/vHBA Placement Assigns an existing vNIC/vHBA placement policy to a service profile created Profiles Placement from this template. If you choose this option, Cisco UCS Manager displays the Profile Name details of the policy. If a vNIC/vHBA placement policy has not been configured in Cisco UCS Manager, this option may not display in the drop-down list. If you do not want use any of the existing policies, but instead want to create a policy that all service profiles and templates can access, click Create Placement Policy and continue with Step 4. Otherwise, continue with Step 5. Step 2 (Optional) If you chose Let System Perform Placement, do the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 530 OL-25712-04 Working with Service Profile Templates a) Use one or more of the following buttons to adjust the order of the vNICs and vHBAs: Name Description Move Up button Moves the selected vNIC or VHBA to a higher priority in the list. Move Down button Moves the selected vNIC or vHBA to a lower priority in the list. Delete button Deletes the selected vNIC or vHBA. Reorder button Returns all vNICs and vHBAs to their original order. Modify button Enables you to modify the currently-selected vNIC or vHBA. Note You can change any options for the vNIC or vHBA except its name. b) Continue with Step 5. Step 3 (Optional) If you chose Specify Manually, do the following: a) On the appropriate tab in the vNIC/vHBA table, click a vNIC or vHBA. b) In the Virtual Host Interface table, click a vCon row and if necessary, choose one of the following values from the Selection Preference column: • All—All configured vNICs and vHBAs can be assigned to the vCon, whether they are explicitly assigned to it, unassigned, or dynamic. • Assigned Only—vNICs and vHBAs must be explicitly assigned to the vCon. You can assign them explicitly through the service profile or the properties of the vNIC or vHBA. • Exclude Dynamic—Dynamic vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for all static vNICs and vHBAs, whether they are unassigned or explicitly assigned to it. • Exclude Unassigned—Unassigned vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for dynamic vNICs and vHBAs and for static vNICs and vHBAs that are explicitly assigned to it. c) Click Assign. If you need to undo an assignment, click Remove. d) Repeat Steps a through c until you have assigned all vNICs and vHBAs. e) When you have specified all vNIC and vHBA placements, continue with Step 5. Step 4 If you clicked Create Placement Policy, do the following in the Create Placement Policy dialog box: a) In the Name field, enter a unique name for the placement policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 531 Working with Service Profile Templates b) In the Selection Preference column for each Virtual Slot, choose one of the following from the drop-down list: • All—All configured vNICs and vHBAs can be assigned to the vCon, whether they are explicitly assigned to it, unassigned, or dynamic. • Assigned Only—vNICs and vHBAs must be explicitly assigned to the vCon. You can assign them explicitly through the service profile or the properties of the vNIC or vHBA. • Exclude Dynamic—Dynamic vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for all static vNICs and vHBAs, whether they are unassigned or explicitly assigned to it. • Exclude Unassigned—Unassigned vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for dynamic vNICs and vHBAs and for static vNICs and vHBAs that are explicitly assigned to it. c) Click OK. d) After the dialog box closes, choose the policy you created from the Select Placement drop-down list. Step 5 Click Next. What to Do Next Complete Page 5: Setting the Server Boot Order, on page 532 Page 5: Setting the Server Boot Order This procedure directly follows Page 4: Setting the vNIC/vHBA Placement, on page 530. It describes how to set the server boot order options on the Server Boot Order page of the Create Service Profile Template wizard. Tip We recommend that the boot order in a boot policy include either a local disk or a SAN LUN, but not both, to avoid the possibility of the server booting from the wrong storage type. If you configure a local disk and a SAN LUN for the boot order storage type and the operating system or logical volume manager (LVM) is configured incorrectly, the server might boot from the local disk rather than the SAN LUN. For example, on a server with Red Hat Linux installed, where the LVM is configured with default LV names and the boot order is configured with a SAN LUN and a local disk, Linux reports that there are two LVs with the same name and boots from the LV with the lowest SCSI ID, which could be the local disk. Procedure Step 1 From the Boot Policy drop-down list, choose one of the following: Option Description Select Boot Policy to use Assigns the default boot policy to every service profile created from this template. Continue with Step 9. Cisco UCS Manager GUI Configuration Guide, Release 2.0 532 OL-25712-04 Working with Service Profile Templates Option Description Create a Specific Boot Policy Enables you to create a local boot policy that can only be accessed by a service profile created from this template. Continue with Step 3. Boot Policies Policy_Name Assigns an existing boot policy to every service profile created from this template. If you choose this option, Cisco UCS Manager displays the details of the policy. If you do not want use any of the existing policies, but instead want to create a policy that all service profiles and templates can access, continue with Step 2. Otherwise, choose a policy from the list and continue with Step 9. Step 2 If you clicked Create Boot Policy to create a boot policy that all service profiles and templates can use, do the following: a) In the Create Boot Policy dialog box, enter a unique name and description for the policy. This name can be between 1 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. b) Continue with Step 3. Step 3 (Optional) To reboot all servers that use this boot policy after you make changes to the boot order, check the Reboot on Boot Order Change check box. In the Cisco UCS Manager GUI, if the Reboot on Boot Order Change check box is checked for a boot policy, and if CD-ROM or Floppy is the last device in the boot order, deleting or adding the device does not directly affect the boot order and the server does not reboot. Step 4 (Optional) If desired, check the Enforce vNIC/vHBA/iSCSI Name check box. • If checked, Cisco UCS Manager displays a configuration error and reports whether one or more of the vNICs, vHBAs, or iSCSI vNICs listed in the Boot Order table match the server configuration in the service profile. • If not checked, Cisco UCS Manager uses the vNICs, vHBAs, or iSCSI vNICs (as appropriate for the boot option) from the server configuration in the service profile. It does not report whether the vNICs, vHBAs, or iSCSI vNICs specified in the boot policy match the server configuration in the service profile. Step 5 To add a local disk, virtual CD-ROM, or virtual floppy to the boot order, do the following: a) Click the down arrows to expand the Local Devices area. b) Click one of the following links to add the device to the Boot Order table: • Add Local Disk • Add CD-ROM • Add Floppy c) Add another boot device to the Boot Order table, or click OK to finish. Step 6 To add a LAN boot to the boot order, do the following: a) Click the down arrows to expand the vNICs area. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 533 Working with Service Profile Templates b) Click the Add LAN Boot link. c) In the Add LAN Boot dialog box, enter the name of the vNIC that you want to use for the LAN boot in the vNIC field, then click OK. d) Add another device to the Boot Order table, or click OK to finish. Step 7 To add a SAN boot to the boot order, do the following: a) Click the down arrows to expand the vHBAs area. b) Click the Add SAN Boot link. c) In the Add SAN Boot dialog box, complete the following fields, and click OK: Name Description vHBA field Enter the name of the vHBA you want to use for the SAN boot. Type field This can be one of the following: • Primary—The first address defined for the associated boot device class. A boot policy can only have one primary LAN, SAN, or iSCSI boot location. • Secondary—The second address defined for the associated boot device class. Each boot policy can have only one secondary LAN or SAN boot location. The use of the terms primary or secondary boot devices does not imply a boot order. The effective order of boot devices within the same device class is determined by PCIe bus scan order. d) If this vHBA points to a bootable SAN image, click the Add SAN Boot Target link and, in the Add SAN Boot Target dialog box, complete the following fields, then click OK: Name Description Boot Target LUN field The LUN that corresponds to the location of the boot image. Boot Target WWPN field The WWPN that corresponds to the location of the boot image. Cisco UCS Manager GUI Configuration Guide, Release 2.0 534 OL-25712-04 Working with Service Profile Templates Name Description Type field This can be one of the following: • Primary—The first address defined for the associated boot device class. A boot policy can only have one primary LAN, SAN, or iSCSI boot location. • Secondary—The second address defined for the associated boot device class. Each boot policy can have only one secondary LAN or SAN boot location. The use of the terms primary or secondary boot devices does not imply a boot order. The effective order of boot devices within the same device class is determined by PCIe bus scan order. e) Add another boot device to the Boot Order table, or click OK to finish. Step 8 To add an iSCSI boot to the boot order, do the following: a) In the Specific Boot Policy area, click the down arrows to expand the iSCSI vNICs area. b) In the iSCSI vNICs area, double-click the iSCSI vNICs from which you want to boot the server to add them to the Boot Order table. c) In the iSCSI vNICs area, click the Set Boot Parameters link. If there are two iSCSI vNICs, choose the one for which you want to set boot parameters. d) Complete the fields in the Set iSCSI Boot Parameters dialog box and then click OK. For more information about the fields, see Setting iSCSI Boot Parameters, on page 454. e) Repeat steps c and d to set boot parameters for additional iSCSI vNICs. Step 9 If you created a new boot policy accessible to all service profiles and template, choose that policy from the Boot Policy drop-down list. Step 10 Click Next. What to Do Next Complete Page 6: Adding the Maintenance Policy, on page 535. Page 6: Adding the Maintenance Policy This procedure directly follows Page 5: Setting the Server Boot Order, on page 532. It describes how to add a maintenance policy to the service profile on the Maintenance Policy page of the Create Service Profile (expert) wizard. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 535 Working with Service Profile Templates Procedure Step 1 From the Maintenance Policy drop-down list, choose one of the following: Option Description Select a Maintenance Policy to Assigns the default maintenance policy to this service profile. Use (default policy shown) Continue with Step 4. Maintenance Policies Policy_Name Assigns an existing maintenance policy to the service profile. If you choose this option, Cisco UCS Manager displays the details of the policy. If you do not want use any of the existing policies but instead want to create a policy that all service profiles can access, click Create Maintenance Policy and continue with Step 2. Otherwise, choose a policy from the list and continue with Step 4. Step 2 If you clicked Create Maintenance Policy to create a maintenance policy that all service profiles and templates can use, do the following: a) In the Create Maintenance Policy dialog box, complete the following fields: Name Description Name field The name of the policy. This name can be between 1 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A description of the policy. We recommend that you include information about where and when the policy should be used. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Cisco UCS Manager GUI Configuration Guide, Release 2.0 536 OL-25712-04 Working with Service Profile Templates Name Description Reboot Policy field When a service profile is associated with a server, or when changes are made to a service profile that is already associated with a server, the server needs to be rebooted to complete the process. The Reboot Policy field determines when the reboot occurs for servers associated with any service profiles that include this maintenance policy. This can be one of the following: • Immediate—The server is rebooted automatically as soon as the service profile association is complete or service profile changes are saved by the user. • User Ack—The user must reboot the server manually after the service profile association is complete or changes are made. • Timer Automatic—Cisco UCS defers all service profile associations and changes until the maintenance window defined by the schedule shown in the Schedule field. Schedule drop-down list If the Reboot Policy is set to Timer Automatic, the schedule specifies when maintenance operations can be applied to the server. Cisco UCS reboots the server and completes the service profile changes at the scheduled time. b) Click OK and continue with Step 3. Step 3 Step 4 If you created a new boot policy accessible to all service profiles and template, select that policy from the Maintenance Policy drop-down list. Click Next. What to Do Next Complete Page 7: Specifying the Server Assignment, on page 509. Page 7: Specifying the Server Assignment Options This procedure directly follows Page 6: Adding the Maintenance Policy, on page 535. It describes how to specify the way a server is assigned to a service profile created from this template on the Server Assignment page of the Create Service Profile Template wizard. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 537 Working with Service Profile Templates Procedure Step 1 From the Pool Assignment drop-down list, choose one of the following: Option Description Assign Later Allows you to assign a server after you have created and configured the service profile template. Continue with Step 2. Select from a Pool Pool_Name Select a server pool from the list at the bottom of the drop-down list. Cisco UCS Manager assigns a server from this pool to a service profile created from this template. Continue with Step 2. Step 2 In the Power State field, click one of the following radio buttons to set the power state that will be applied to the server when it is associated with a service profile created from this template: • Down if you want the server to be powered down before the profile is associated with the server • Up if you want the server to be powered up before the profile is associated with the server By default, the server is powered up. Step 3 If you want to restrict the migration of the service profile after it has been associated with a server, check the Restrict Migration. check box. 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. Step 4 (Optional) In the Firmware Management area, do the following to use policies to update the firmware on the server associated with a service profile created from this template: a) Click the down arrows on the Firmware Management bar. b) Complete the following fields: Name Description Host Firmware drop-down list To associate a host firmware package with this service profile, choose its name from the drop-down list. Create Host Firmware Package Click this link if you want to create a host firmware package. link Management Firmware drop-down list To associate a management firmware package with this service profile, choose its name from the drop-down list. Create Management Firmware Click this link if you want to create a management firmware package. Package link Cisco UCS Manager GUI Configuration Guide, Release 2.0 538 OL-25712-04 Working with Service Profile Templates Step 5 Click Next. What to Do Next Complete Page 8: Adding Operational Policies, on page 539. Page 8: Adding Operational Policies This procedure directly follows Page 7: Specifying the Server Assignment Options, on page 537. It describes how to add operational policies to the service profile template on the Operational Policies page of the Create Service Profile Template wizard. These policies are optional. Procedure Step 1 To override the default BIOS settings and configure them through the service profile, click the down arrows to expand the BIOS Configuration bar and do one of the following: • To add an existing policy, choose the desired BIOS policy from the BIOS Policy drop-down list . • To create a BIOS policy that is available to all service profiles, click Create BIOS Policy, complete the fields in the dialog box, and then choose the desired BIOS policy from the BIOS Policy drop-down list . For more information about how to create a BIOS policy, see Creating a BIOS Policy, on page 403. Step 2 To provide external access to the CIMC on the server, click the down arrows to expand the External IPMI Management Configuration bar and add an IPMI profile and a serial over LAN policy. If you do not want to provide external access, continue with Step 4. Step 3 To add an IPMI profile to service profiles created from this template, do one of the following: • To add an existing policy, choose the desired IPMI profile from the IPMI Access Profile drop-down list. • If the IPMI Access Profile drop-down list does not include an IPMI profile with the desired user access, click the Create Access IPMI Profile link to create an IPMI profile that is available to all service profiles and then choose that profile from the IPMI Access Profile drop-down list. For more information about how to create an IPMI profile, see Creating an IPMI Access Profile, on page 405. Step 4 To add a Serial over LAN policy to service profiles created from this template, do one of the following: • To add an existing policy, choose the desired Serial over LAN policy from the SoL Configuration Profile drop-down list. • To create a Serial over LAN policy that is only available to service profile created from this template, choose Create a Specific SoL Policy from the SoL Configuration Profile drop-down list and complete the Admin State field and the Speed drop-down list. • To create a Serial over LAN policy that is available to all service profile templates, click the Create Serial over LAN Policy link, complete the fields in the dialog box, and then choose that policy from the SoL Configuration Profile drop-down list. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 539 Working with Service Profile Templates For more information about how to create a serial over LAN policy, see Creating a Serial over LAN Policy, on page 415. Step 5 To configure the management IP required for external access to the CIMC on the server, click the down arrows to expand the Management IP Address bar and click one of the following radio buttons: • None—No management IP address is assigned to the service profile. The management IP address is set based on the CIMC management IP address settings on the server. • Pooled—A management IP address is assigned to the service profile from the management IP address pool. Step 6 To monitor thresholds and collect statistics for the associated server, click the down arrows to expand the Monitoring Configuration bar and do one of the following: • To add an existing policy, choose the desired threshold policy from the Threshold Policy drop-down list. • To create a threshold policy that is available to all service profiles, click the Create Threshold Policy link, complete the fields in the dialog box, and then choose that policy from the Threshold Policy drop-down list. For more information about how to create a threshold policy, see Creating a Server and Server Component Threshold Policy , on page 666. Step 7 To associate a power control policy with the service profile template, click the down arrows to expand the Power Control Policy Configuration bar and do one of the following: • To add an existing policy, choose the desired power control policy from the Power Control Policy drop-down list. • To create a power control policy that is available to all service profiles and templates, click the Create Power Control Policy link , complete the fields in the dialog box, and then choose that policy from the Power Control Policy drop-down list. For more information about how to create a power control policy, see Creating a Power Control Policy, on page 569. Step 8 To associate a scrub policy with the service profile template, click the down arrows to expand the Scrub Policy bar and do one of the following: • To add an existing policy, choose the desired scrub policy from the Scrub Policy drop-down list . • To create a scrub policy that is available to all service profiles and templates, click the Create Scrub Policy link , complete the fields in the dialog box, and then choose that policy from the Scrub Policy drop-down list . For more information about how to create a scrub policy, see Creating a Scrub Policy, on page 414. Step 9 Click Finish. Cisco UCS Manager GUI Configuration Guide, Release 2.0 540 OL-25712-04 Working with Service Profile Templates Creating One or More Service Profiles from a Service Profile Template Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profile Templates. Expand the node for the organization that contains the service profile template that you want to use as the basis for your service profiles. If the system does not include multitenancy, expand the root node. Step 4 Right-click the service profile template from which you want to create the profiles and select Create Service Profiles From Template. In the Create Service Profiles From Template dialog box, complete the following fields: Step 5 Name Description Naming Prefix field The prefix to use for the template name. When the system creates the service profile, it appends a unique numeric identifier to this prefix. Enter between 1 and 29 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period). For example, if you specify the prefix MyProfile and request two profiles, the first service profile would be called MyProfile1 and the second would be MyProfile2. If you return at a later date and create three more profiles with the same prefix, they would be named MyProfile3, MyProfile4, and MyProfile5. Number field The number of service profiles to create. Enter a number between 1 and 255. Step 6 Click OK. Creating a Template Based Service Profile for a Blade Server Before You Begin A qualified service profile template with the desired values must exist in Cisco UCS Manager. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 541 Working with Service Profile Templates Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server for which you want to create a template based service profile. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Create Service Profile. In the Create Service Profile for Server dialog box, do the following: a) Click the Template Based Service Profile radio button. b) In the Name field, enter a unique name for the service profile. This name can be between 2 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and this name must be unique across all service profiles and service profile templates within the same organization. c) From the Service Profile Template drop-down list, select the template from which you want to create the service profile associated with this server. d) Click OK. Creating a Template Based Service Profile for a Rack-Mount Server Before You Begin A qualified service profile template with the desired values must exist in Cisco UCS Manager. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Choose the server for which you want to create a template based service profile. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Create Service Profile. In the Create Service Profile for Server dialog box, do the following: a) Click the Template Based Service Profile radio button. b) In the Name field, enter a unique name for the service profile. This name can be between 2 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and this name must be unique across all service profiles and service profile templates within the same organization. c) From the Service Profile Template drop-down list, select the template from which you want to create the service profile associated with this server. d) Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 542 OL-25712-04 Working with Service Profile Templates Creating a Service Profile Template from a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile that you want to use as the basis for your template. If the system does not include multitenancy, expand the root node. Step 4 Right-click the service profile from which you want to create the template and select Create a Service Profile Template. In the Create Template From Service Profile dialog box, complete the following fields: Step 5 Name Description Service Profile Template Name field The name of the service profile template. Org drop-down list Select the organization that you want this template to be associated with. Type field This can be one of the following: This name can be between 2 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and this name must be unique across all service profiles and service profile templates within the same organization. • Initial Template—Any service profiles created from this template are not updated if the template changes • Updating Template—Any service profiles created from this template are updated if the template changes Step 6 Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 543 Managing Service Profiles Managing Service Profiles Cloning a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization where you want to create the service profile. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click the service profile you want to clone and select Create a Clone. In the Create Clone From Service Profile dialog box: a) Enter the name you want to use for the new profile in the Clone Name field. This name can be between 2 and 32 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and this name must be unique across all service profiles and service profile templates within the same organization. This name must be unique within the organization or sub-organization in which you are creating the service profile. b) Click OK. Step 6 Navigate to the service profile you just created and make sure that all options are correct. Associating a Service Profile with a Server or Server Pool Follow this procedure if you did not associate the service profile with a blade server or server pool when you created it, or to change the blade server or server pool with which a service profile is associated. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile that you want to associate with a new server or server pool. If the system does not include multitenancy, expand the root node. Step 4 Right-click the service profile you want to associate with a server and select Change Service Profile Association. In the Associate Service Profile dialog box, select one of the following options: Step 5 Cisco UCS Manager GUI Configuration Guide, Release 2.0 544 OL-25712-04 Managing Service Profiles Option Description Server Pool Select a server pool from the drop-down list. Cisco UCS Manager assigns a server from this pool to the service profile. Continue with Step 7. Server Navigate to the desired available server in the navigation tree and select the server which will be assigned to the service profile. Continue with Step 7. Custom Server Specifies the chassis and slot that contains the server that will be assigned to the service profile. If the server is not in the slot or is otherwise unavailable, the service profile will be associated with the server when it becomes available. Continue with Step 6. Step 6 If you chose Custom Server, do the following: a) In the Chassis Id field, enter the number of the chassis where the selected server is located. b) In the Server Id field, enter the number of the slot where the selected server is located. Step 7 If you want to restrict the migration of the service profile after it has been associated with a server, check the Restrict Migration. check box. 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. Step 8 Click OK. Disassociating a Service Profile from a Server or Server Pool When you disassociate a service profile, Cisco UCS Manager attempts to shutdown the operating system on the server. If the operating system does not shutdown within a reasonable length of time, Cisco UCS Manager forces the server to shutdown. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile that you want to disassociate from a server or server pool. If the system does not include multitenancy, expand the root node. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 545 Managing Service Profiles Step 4 Step 5 Step 6 Right-click the service profile you want to disassociate from a server and select Disassociate Service Profile. In the Disassociate Service Profile dialog box, click Yes to confirm that you want to disassociate the service profile. (Optional) Monitor the status and FSM for the server to confirm that the disassociation completed. Associating a Service Profile Template with a Server Pool Follow this procedure if you did not associate the service profile template with a server pool when you created it, or to change the server pool with which a service profile created from this template is associated. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profile Templates. Expand the node for the organization that contains the service profile that you want to associate with a server pool. If the system does not include multitenancy, expand the root node. Step 4 Right-click the service profile template you want to associate with a server pool and select Associate with Server Pool. The Associate with Server Pool dialog box opens. Step 5 From the Server Pool section of the Pool Assignment drop-down list, select a server pool. If you select Assign Later, the service profile template is not associated with a server pool. Step 6 Select one of the following radio buttons to determine the power state applied to a server which is associated with a service profile created from this template: • Down • Up Step 7 Step 8 From the Select Qualification drop-down list, select the server pool policy qualifications you want to apply to a server that is associated with a service profile created from this template. Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 546 OL-25712-04 Managing Service Profiles Disassociating a Service Profile Template from its Server Pool Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profile Templates. Expand the node for the organization that contains the service profile that you want to disassociate from its server pool. If the system does not include multitenancy, expand the root node. Step 4 Right-click the service profile template you want to disassociate from its server pool and select Disassociate Template. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Step 5 Changing the UUID in a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile for which you want to change the UUID. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Choose the service profile that requires the UUID for the associated server to be changed. In the Work pane, click the General tab. Step 6 Step 7 In the Actions area, click Change UUID. From the UUID Assignment drop-down list, do one of the following: Option Description Select (pool default used by default) Assigns a UUID from the default UUID Suffix pool. Continue with Step 9. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 547 Managing Service Profiles Option Description Hardware Default Uses the UUID assigned to the server by the manufacturer. If you choose this option, the UUID remains unassigned until the service profile is associated with a server. At that point, the UUID is set to the UUID value assigned to the server by the manufacturer. If the service profile is later moved to a different server, the UUID is changed to match the new server. Continue with Step 9. XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX Uses the UUID that you manually assign. Continue with Step 8. Pools Pool_Name Assigns a UUID from the UUID Suffix pool that you select from the list at the bottom of the drop-down list. Each pool name is followed by two numbers in parentheses that show the number of UUIDs still available in the pool and the total number of UUIDs in the pool. Continue with Step 9. Step 8 (Optional) If you selected the XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX option, do the following: a) In the UUID field, enter the valid UUID that you want to assign to the server which uses this service profile. b) To verify that the selected UUID is available, click the here link. Step 9 Click OK. Changing the UUID in a Service Profile Template Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profile Templates. Expand the node for the organization that contains the service profile template for which you want to change the UUID. If the system does not include multitenancy, expand the root node. Cisco UCS Manager GUI Configuration Guide, Release 2.0 548 OL-25712-04 Managing Service Profiles Step 4 Step 5 Choose the service profile template whose UUID assignment you want to change. In the Work pane, click the General tab. Step 6 Step 7 In the Actions area, click Change UUID. From the UUID Assignment drop-down list, choose one of the following: Option Description Select (pool default used by default) Assigns a UUID from the default UUID Suffix pool. Hardware Default Uses the UUID assigned to the server by the manufacturer. If you choose this option, the UUID remains unassigned until the service profile is associated with a server. At that point, the UUID is set to the UUID value assigned to the server by the manufacturer. If the service profile is later moved to a different server, the UUID is changed to match the new server. Pools Pool_Name Assigns a UUID from the UUID Suffix pool that you select from the list at the bottom of the drop-down list. Each pool name is followed by two numbers in parentheses that show the number of UUIDs still available in the pool and the total number of UUIDs in the pool. Step 8 Click OK. Resetting the UUID Assigned to a Service Profile from a Pool in a Service Profile Template If you change the UUID suffix pool assigned to an updating service profile template, Cisco UCS Manager does not change the UUID assigned to a service profile created with that template. If you want Cisco UCS Manager to assign a UUID from the newly assigned pool to the service profile, and therefore to the associated server, you must reset the UUID. You can only reset the UUID assigned to a service profile and its associated server under the following circumstances: • The service profile was created from an updating service profile template and includes a UUID assigned from a UUID suffix pool. • The UUID suffix pool name is specified in the service profile. For example, the pool name is not empty. • The UUID value is not 0, and is therefore not derived from the server hardware. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile for which you want to reset the UUID. If the system does not include multitenancy, expand the root node. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 549 Managing Service Profiles Step 4 Step 5 Choose the service profile that requires the UUID for the associated server to be reset to a different UUID suffix pool. In the Work pane, click the General tab. Step 6 In the Actions area, click Reset UUID. If this action is not visible, then the UUID configuration in the service profile does not meet the requirements for resetting a UUID. Step 7 Step 8 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click OK Modifying the Boot Order in a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that includes the service profile for which you want to change the boot order. If the system does not include multi-tenancy, expand the root node. Step 4 Step 5 Click the service profile for which you want to change the boot order. In the Work pane, click the Boot Order tab. Step 6 Step 7 Click Modify Boot Policy to change the existing boot policy. In the Modify Boot Policy dialog box, choose one of the following from the Boot Policy drop-down list: Option Description Select Boot Policy to use Assigns the default boot policy to this service profile. Continue with Step 14. Create a Specific Boot Policy Enables you to create a local boot policy that can only be accessed by this service profile. Continue with Step 8. Boot Policies Policy_Name Assigns an existing boot policy to the service profile. If you choose this option, Cisco UCS Manager displays the details of the policy. If you do not want use any of the existing policies, but instead want to create a policy that all service profiles can access, click Create Boot Policy and continue with Step 2. Otherwise, continue with Step 14. Step 8 If you chose to create a boot policy, in the Create Boot Policy dialog box, enter a unique name and description for the policy. Cisco UCS Manager GUI Configuration Guide, Release 2.0 550 OL-25712-04 Managing Service Profiles This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Step 9 (Optional) To reboot all servers that use this boot policy after you make changes to the boot order, check the Reboot on Boot Order Change check box. In the Cisco UCS Manager GUI, if the Reboot on Boot Order Change check box is checked for a boot policy, and if CD-ROM or Floppy is the last device in the boot order, deleting or adding the device does not directly affect the boot order and the server does not reboot. Step 10 (Optional) If desired, check the Enforce vNIC/vHBA/iSCSI Name check box. • If checked, Cisco UCS Manager displays a configuration error and reports whether one or more of the vNICs, vHBAs, or iSCSI vNICs listed in the Boot Order table match the server configuration in the service profile. • If not checked, Cisco UCS Manager uses the vNICs, vHBAs, or iSCSI vNICs (as appropriate for the boot option) from the server configuration in the service profile. It does not report whether the vNICs, vHBAs, or iSCSI vNICs specified in the boot policy match the server configuration in the service profile. Step 11 To add a local disk, virtual CD-ROM, or virtual floppy to the boot order, do the following: a) Click the down arrows to expand the Local Devices area. b) Click one of the following links to add the device to the Boot Order table: • Add Local Disk • Add CD-ROM • Add Floppy c) Add another boot device to the Boot Order table, or click OK to finish. Step 12 To add a LAN boot to the boot order, do the following: a) Click the down arrows to expand the vNICs area. b) Click the Add LAN Boot link. c) In the Add LAN Boot dialog box, enter the name of the vNIC that you want to use for the LAN boot in the vNIC field, then click OK. d) Add another device to the Boot Order table, or click OK to finish. Step 13 To add a SAN boot to the boot order, do the following: a) Click the down arrows to expand the vHBAs area. b) Click the Add SAN Boot link. c) In the Add SAN Boot dialog box, complete the following fields, and click OK: Name Description vHBA field Enter the name of the vHBA you want to use for the SAN boot. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 551 Managing Service Profiles Name Description Type field This can be one of the following: • Primary—The first address defined for the associated boot device class. A boot policy can only have one primary LAN, SAN, or iSCSI boot location. • Secondary—The second address defined for the associated boot device class. Each boot policy can have only one secondary LAN or SAN boot location. The use of the terms primary or secondary boot devices does not imply a boot order. The effective order of boot devices within the same device class is determined by PCIe bus scan order. d) If this vHBA points to a bootable SAN image, click the Add SAN Boot Target link and, in the Add SAN Boot Target dialog box, complete the following fields, then click OK: Name Description Boot Target LUN field The LUN that corresponds to the location of the boot image. Boot Target WWPN field The WWPN that corresponds to the location of the boot image. Type field This can be one of the following: • Primary—The first address defined for the associated boot device class. A boot policy can only have one primary LAN, SAN, or iSCSI boot location. • Secondary—The second address defined for the associated boot device class. Each boot policy can have only one secondary LAN or SAN boot location. The use of the terms primary or secondary boot devices does not imply a boot order. The effective order of boot devices within the same device class is determined by PCIe bus scan order. e) Add another boot device to the Boot Order table, or click OK to finish. Step 14 Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 552 OL-25712-04 Managing Service Profiles Creating a vNIC for a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 Step 6 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile for which you want to create a vNIC. Expand the service profile for which you want to create a vNIC. Right-click the vNICs node and choose Create vNICs. In the Create vNICs dialog box, do the following: a) Complete the following fields to specify the identity information for the vNIC: Name Description Name field The user-defined name for this vNIC. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Use LAN Connectivity Template check box Check this check box if you want to use a template to create the vNIC. Cisco UCS Manager GUI displays the vNIC Template drop-down list from which you can select the appropriate template, and the Adapter Performance Profile area from which you can select an adapter profile. Note You can only select this option if one or more LAN connectivity templates exist in the system. Create vNIC Template link Click this link if you want to create a vNIC template. MAC Address Assignment drop-down list If you want to: • Use the default MAC address pool, leave this field set to Select (pool default used by default). • Use the MAC address assigned to the server by the manufacturer, select Hardware Default. • A specific MAC address, select 02:25:B5:XX:XX:XX and enter the address in the MAC Address field. To verify that this address is available, click the corresponding link. • A MAC address from a pool, select the pool name from the list. Each pool name is followed by a pair of numbers in parentheses. The first number is the number of available MAC addresses in the pool and the second is the total number of MAC addresses in the pool. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 553 Managing Service Profiles b) Complete the following fields to specify the fabric connection information: Name Description Fabric ID field The fabric interconnect associated with the component. If you want this vNIC to be able to access the second fabric interconnect if the default one is unavailable, check the Enable Failover check box. Note Do not enable fabric failover for the vNIC under the following circumstances: • If the Cisco UCS domain is running in Ethernet Switch Mode. vNIC fabric failover is not supported in that mode. If all Ethernet uplinks on one fabric interconnect fail, the vNICs do not fail over to the other. • if you plan to associate this vNIC with a server that has an adapter which does not support fabric failover, such as the Cisco UCS 82598KR-CI 10-Gigabit Ethernet Adapter. If you do so, Cisco UCS Manager generates a configuration fault when you associate the service profile with the server. VLANs table This table lists the VLANs that can be associated with this vNIC. The columns are: • Select—Check the check box in this column for each VLAN you want to use. • Name—The name of the VLAN. • Native VLAN—To designate one of the VLANs as the native VLAN, click the radio button in this column. Create VLAN link Click this link if you want to create a VLAN. MTU field The maximum transmission unit, or packet size, that this vNIC accepts. Enter an integer between 1500 and 9216. Note If the vNIC has an associated QoS policy, the MTU specified here must be equal to or less than the MTU specified in the associated QoS system class. If this MTU value exceeds the MTU value in the QoS system class, packets may be dropped during data transmission. Pin Group drop-down list Choose the LAN pin group you want associated with this vNIC. Create LAN Pin Group link Click this link if you want to create a LAN pin group. Operational Parameters Section Cisco UCS Manager GUI Configuration Guide, Release 2.0 554 OL-25712-04 Managing Service Profiles Name Description Stats Threshold Policy drop-down list The statistics collection policy with which this vNIC is associated. c) In the Adapter Performance Profile area, complete the following fields: Name Description Adapter Policy drop-down list The Ethernet adapter policy with which this vNIC is associated. Create Ethernet Adapter Policy Click this link if you want to create an Ethernet adapter policy. link QoS drop-down list The quality of service policy with which this vNIC is associated. Create QoS Policy link Click this link if you want to create a quality of service policy. Network Control Policy drop-down list The network control policy with which this vNIC is associated. Create Network Control Policy Click this link if you want to create a network control policy. Policy link d) Click OK. Resetting the MAC Address Assigned to a vNIC from a Pool in a Service Profile Template If you change the MAC pool assigned to an updating service profile template, Cisco UCS Manager does not change the MAC address assigned to a service profile created with that template. If you want Cisco UCS Manager to assign a MAC address from the newly assigned pool to the service profile, and therefore to the associated server, you must reset the MAC address. You can only reset the MAC address assigned to a service profile and its associated server under the following circumstances: • The service profile was created from an updating service profile template and includes a MAC address assigned from a MAC pool. • The MAC pool name is specified in the service profile. For example, the pool name is not empty. • The MAC address value is not 0, and is therefore not derived from the server hardware. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 555 Managing Service Profiles Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile for which you want to reset the MAC address. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Step 6 Expand Service_Profile_Name > vNICs. Click the vNIC for which you want to reset the MAC address. In the Work pane, click the General tab. Step 7 Step 8 In the Actions area, click Reset MAC Address. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click OK. Step 9 Deleting a vNIC from a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile from which you want to delete a vNIC. Expand the service profile from which you want to delete a vNIC. Expand the vNICs node. Right-click the vNIC you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Creating a vHBA for a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 Step 6 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile for which you want to create a vHBA. Expand the service profile for which you want to create a vHBA. Right-click the vHBAs node and choose Create vHBAs. In the Create vHBAs dialog box, do the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 556 OL-25712-04 Managing Service Profiles a) Complete the following fields to specify the identity information for the vHBA: Name Description Name field The name of this vHBA. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Use SAN Connectivity Template Check this check box if you want to use a template to create the check box vHBA. Cisco UCS Manager GUI displays the vHBA Template drop-down list from which you can select the appropriate template, and the Adapter Performance Profile area from which you can select an adapter profile. Note Create vHBA Template link You can only select this option if one or more SAN connectivity templates exist in the system. Click this link if you want to create a vHBA template. WWPN Assignment drop-down If you want to: list • Use the default WWPN pool, leave this field set to Select (pool default used by default). • Use the WWPN assigned to the server by the manufacturer, select Hardware Default. • A specific WWPN, select 20:00:00:25:B5:00:00:00, 20:XX:XX:XX:XX:XX:XX:XX, or 5X:XX:XX:XX:XX:XX:XX:XX and enter the WWPN in the WWPN field. To verify that this WWPN is available, click the corresponding link. • A WWPN from a pool, select the pool name from the list. Each pool name is followed by a pair of numbers in parentheses. The first number is the number of available WWN addresses in the pool and the second is the total number of WWPN addresses in the pool. To create a new WWPN pool, click Create WWPN Pool. b) In the VSAN area, complete the following fields: Name Description Fabric ID field The fabric interconnect associated with the component. Select VSAN drop-down list box The VSAN with which this vHBA is associated. Create VSAN link Click this link if you want to create a VSAN. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 557 Managing Service Profiles Name Description Pin Group drop-down list box The pin group with which this vHBA is associated. Create SAN Pin Group link Click this link if you want to create a pin group. Persistent Binding field This can be one of the following: • Disabled • Enabled Max Data Field Size field The maximum size of the Fibre Channel frame payload bytes that the vHBA supports. Enter an integer between 256 and 2112. The default is 2048. Operational Parameters Section Stats Threshold Policy drop-down list box The threshold policy with which this vHBA is associated. c) In the Adapter Performance Profile area, complete the following fields: Name Description Adapter Policy drop-down list box The Fibre Channel adapter policy with which this vHBA is associated. Create Fibre Channel Adapter Click this link if you want to create a Fibre Channel adapter policy. Policy link QoS drop-down list box The quality of service policy with which this vHBA is associated. Create QoS Policy link Click this link if you want to create a QoS policy. d) Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 558 OL-25712-04 Managing Service Profiles Changing the WWPN for a vHBA Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile for which you want to change the WWPN. Expand Service_Profile_Name > vHBAs. Click the vHBA for which you want to change the WWPN. In the Work pane, click the General tab. Step 4 Step 5 Step 6 Step 7 Step 8 In the Actions area, click Change World Wide Name. In the Change World Wide Port Name dialog box, complete the following fields: Name Description WWPN Assignment drop-down list If you want to: • Use the default WWPN pool, choose Select (pool default used by default). • Use a WWPN derived from the manufacturer's specifications, choose Hardware Default. • A WWPN from a pool, select the pool name from the list. Each pool name is followed by number of available/total WWPNs in the pool. • A specific WWPN, choose one of the WWPN templates under Manual using OUI and enter the WWPN in the WWPN field. Note WWPN field If you want the WWPN to be compatible with Cisco MDS Fibre Channel switches, use the manual template and WWPN 20:00:00:25:B5:XX:XX:XX. The manually-assigned WWPN if the WWPN Assignment drop-down list is set to one of the manual templates. You can specify a WWPN in the range from 20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF. To make sure the WWPN is available, click the corresponding link. Step 9 Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 559 Managing Service Profiles Resetting the WWPN Assigned to a vHBA from a Pool in a Service Profile Template If you change the WWPN pool assigned to an updating service profile template, Cisco UCS Manager does not change the WWPN assigned to a service profile created with that template. If you want Cisco UCS Manager to assign a WWPN from the newly assigned pool to the service profile, and therefore to the associated server, you must reset the WWPN. You can only reset the WWPN assigned to a service profile and its associated server under the following circumstances: • The service profile was created from an updating service profile template and includes a WWPN assigned from a WWPN pool. • The WWPN pool name is specified in the service profile. For example, the pool name is not empty. • The WWPN value is not 0, and is therefore not derived from the server hardware. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile for which you want to reset the WWPN. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Step 6 Expand Service_Profile_Name > vHBAs. Click the vHBA for which you want to reset the WWPN. In the Work pane, click the General tab. Step 7 Step 8 Step 9 In the Actions area, click Reset WWPN. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click OK. Clearing Persistent Binding for a vHBA Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 Step 6 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile for which you want to modify the vHBA. Expand Service_Profile_Name > vHBAs. Click the vHBA for which you want to clear the persistent binding. In the Work pane, click the General tab. Step 7 Step 8 In the Actions area, click Clear Persistent Binding. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 560 OL-25712-04 Managing Service Profiles Deleting a vHBA from a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that contains the service profile from which you want to delete a vHBA. Expand the service profile from which you want to delete a vHBA. Expand the vHBAs node. Right-click the vHBA you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Binding a Service Profile to a Service Profile Template You can bind a service profile to a service profile template. When you bind the service profile to a template, Cisco UCS Manager configures the service profile with the values defined in the service profile template. If the existing service profile configuration does not match the template, Cisco UCS Manager reconfigures the service profile. You can only change the configuration of a bound service profile through the associated template. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that includes the service profile you want to bind. If the system does not include multi-tenancy, expand the root node. Step 4 Step 5 Click the service profile you want to bind. In the Work pane, click the General tab. Step 6 Step 7 In the Actions area, click Bind to a Template. In the Bind to a Service Profile Template dialog box, do the following: a) From the Service Profile Template drop-down list, choose the template to which you want to bind the service profile. b) Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 561 Managing Service Profiles Unbinding a Service Profile from a Service Profile Template Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization that includes the service profile you want to unbind. If the system does not include multi-tenancy, expand the root node. Step 4 Step 5 Click the service profile you want to unbind. In the Work pane, click the General tab. Step 6 Step 7 In the Actions area, click Unbind from the Template. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Deleting a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 In the Servers tab, expand Servers > Service Profiles > Organization_Name . Right-click the service profile you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 562 OL-25712-04 CHAPTER 33 Managing Power in Cisco UCS This chapter includes the following sections: • Power Management in Cisco UCS , page 563 • Rack Server Power Management, page 563 • Power Management Precautions, page 563 • Configuring the Power Policy, page 564 • Configuring the Global Cap Policy, page 564 • Configuring Policy-Driven Chassis Group Power Capping, page 565 • Configuring Manual Blade-Level Power Capping, page 570 Power Management in Cisco UCS You can manage power through Cisco UCS Manager by configuring any of the following features: • Power supply redundancy for all chassis in a Cisco UCS domain • Policy-driven chassis-level power capping • Manual blade-level power capping Rack Server Power Management Power capping is not supported for rack servers. Power Management Precautions If the CIMC is reset, the power monitoring functions of Cisco UCS become briefly unavailable for as long as it takes for the CIMC to reboot. While this usually only takes 20 seconds, there is a possibility that the peak power cap could be exceeded during that time. To avoid exceeding the configured power cap in a very low power-capped environment, consider staggering the rebooting or activation of CIMCs. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 563 Configuring the Power Policy Configuring the Power Policy Power Policy The power policy is a global policy that specifies the redundancy for power supplies in all chassis in the Cisco UCS domain. This policy is also known as the PSU policy. For more information about power supply redundancy, see Cisco UCS 5108 Server Chassis Hardware Installation Guide. Configuring the Power Policy Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Policies tab. Step 4 Step 5 Click the Global Policies subtab. In the Power Policy area, click one of the following radio buttons in the Redundancy field: • Non Redundant—All installed power supplies are turned on and the load is evenly balanced. Only smaller configurations (requiring less than 2500W) can be powered by a single power supply. • n+1—The total number of power supplies to satisfy non-redundancy, plus one additional power supply for redundancy, are turned on and equally share the power load for the chassis. If any additional power supplies are installed, Cisco UCS Manager sets them to a "turned-off" state. • Grid—Two power sources are turned on, or the chassis requires greater than N+1 redundancy. If one source fails (which causes a loss of power to one or two power supplies), the surviving power supplies on the other power circuit continue to provide power to the chassis. For more information about power supply redundancy, see Cisco UCS 5108 Server Chassis Hardware Installation Guide. Step 6 Click Save Changes. Configuring the Global Cap Policy Global Cap Policy The global cap policy is a global policy that specifies whether policy-driven chassis group power capping or manual blade-level power capping will be applied to all servers in a chassis. We recommend that you use the default power capping method: policy-driven chassis group power capping. Cisco UCS Manager GUI Configuration Guide, Release 2.0 564 OL-25712-04 Configuring Policy-Driven Chassis Group Power Capping Important Any change to the manual blade-level power cap configuration will result in the loss of any groups or configuration options set for policy-driven chassis group power capping. Configuring the Global Cap Policy Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Policies tab. Step 4 Step 5 Click the Global Policies subtab. In the Global Cap Policy area, click one of the following radio buttons in the Allocation Method field to determine the power cap management mode used in the Cisco UCS domain: • Manual Blade Level Cap—Power allocation is configured on each individual blade server in all chassis. If you select this option, you cannot create power groups. • Policy Driven Chassis Group Cap—Power allocation is configured at the chassis level through power control policies included in the associated service profiles. If you select this option, you can also create power groups that contain one or more chassis in the Cisco UCS domain. By default, power allocation is done for each chassis through a power control policy. Step 6 Click Save Changes. Configuring Policy-Driven Chassis Group Power Capping Policy-Driven Chassis Group Power Capping When policy-driven power chassis group power capping is selected in the global cap policy, Cisco UCS can maintain the oversubscription of servers without risking costly power failures. This is achieved through a two-tier process. At the chassis level, Cisco UCS divides the amount of power available between members of the power group. At the blade level, the amount of power allotted to a chassis is divided between blades based on priority. Each time a service profile is associated or disassociated, UCS Manager recalculates the power allotment for each blade server within the chassis. If necessary, power from lower-priority service profiles is redistributed to higher-priority service profiles. UCS power groups cap power in less than one second in order to safely protect data center circuit breakers. A blade must stay at its cap for 20 seconds before the chassis power distribution is optimized. This is intentionally carried out over a slower timescale to prevent reacting to transient spikes in demand. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 565 Configuring Policy-Driven Chassis Group Power Capping Note The system reserves enough power to boot a server in each slot, even if that slot is empty. This reserved power cannot be leveraged by servers requiring more power. Blades that fail to comply with the power cap are penalized or shut down. Configuring Power Groups Power Groups A power group is a set of chassis that all draw power from the same power distribution unit (PDU). In Cisco UCS Manager, you can create power groups that include one or more chassis and then set a peak power cap in AC watts for that power grouping. Instituting power capping at the chassis level requires the following: • IOM, CIMC, and BIOS version 1.4 or higher • 2 PSUs The peak power cap is a static value that represents the maximum power available to all blade servers within a given power group. If you add or remove a blade from a power group, but do not manually modify the peak power value, the power group adjusts the peak power cap to accommodate the basic power-on requirements of all blades within that power group. A minimum of 3788 AC watts should be set for each chassis. This converts to 3400 watts of DC power, which is the minimum amount of power required to power a fully-populated chassis. If insufficient power is available, Cisco UCS Manager raises an alert. Once a chassis is added to a power group, every service profile associated with that chassis also becomes part of that power group. Similarly, if you add a new blade to a chassis, that blade inherently becomes part of the chassis' power group. Note Creating a power group is not the same as creating a server pool. However, you can populate a server pool with members of the same power group by creating a power qualifier and adding it to server pool policy. Creating a Power Group Before You Begin Make sure the global power allocation policy is set to Policy Driven Chassis Group Cap on the Global Policies tab. Cisco UCS Manager GUI Configuration Guide, Release 2.0 566 OL-25712-04 Configuring Policy-Driven Chassis Group Power Capping Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Policies tab. Step 4 Step 5 Click the Power Groups subtab. On the icon bar to the right of the table, click +. If the + icon is disabled, click an entry in the table to enable it. Step 6 On the first page of the Create Power Group wizard, complete the following fields: a) Enter a unique name and description for the power group. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. b) Click Next. Step 7 On the Add Chassis Members page of the Create Power Group wizard, do the following: a) In the Chassis table, choose one or more chassis to include in the power group. b) Click the >> button to add the chassis to the Selected Chassis table that displays all chassis included in the power group. You can use the << button to remove one or more chassis from the power group. c) Click Next. Step 8 On the Power Group Attributes page of the Create Power Group wizard, do the following: a) Complete the following fields: Name Description Power Cap field The maximum peak power (in watts) available to the power group. Enter an integer between 0 and 10000000. Enable Dynamic Reallocation field This can be one of the following: • Chassis—Cisco UCS monitors power usage and changes the blade allocations as required to maximize power utilization. • None—Blade allocations are not adjusted dynamically. b) Click Finish. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 567 Configuring Policy-Driven Chassis Group Power Capping Adding a Chassis to a Power Group Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Power Groups tab. Step 4 Step 5 Right-click the power group to which you want to add a chassis and choose Add Chassis Members. In the Add Chassis Members dialog box, do the following: a) In the Chassis table, choose one or more chassis to include in the power group. b) Click the >> button to add the chassis to the Selected Chassis table that displays all chassis included in the power group. You can use the << button to remove one or more chassis from the power group. c) Click OK. Removing a Chassis from a Power Group Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Power Groups tab. Step 4 Step 5 Step 6 Expand the power group from which you want to remove a chassis. Right-click the chassis that you want to remove from the power group and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Deleting a Power Group Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Power Groups tab. Step 4 Step 5 Right-click the power group that you want to delete and choose Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 568 OL-25712-04 Configuring Policy-Driven Chassis Group Power Capping Configuring Power Control Policies Power Control Policy Cisco UCS uses the priority set in the power control policy, along with the blade type and configuration, to calculate the initial power allocation for each blade within a chassis. During normal operation, the active blades within a chassis can borrow power from idle blades within the same chassis. If all blades are active and reach the power cap, service profiles with higher priority power control policies take precedence over service profiles with lower priority power control policies. Priority is ranked on a scale of 1-10, where 1 indicates the highest priority and 10 indicates lowest priority. The default priority is 5. For mission-critical application a special priority called no-cap is also available. Setting the priority to no-cap prevents Cisco UCS from leveraging unused power from that particular blade server. The server is allocated the maximum amount of power that that blade can reach. Note You must include this policy in a service profile and that service profile must be associated with a server for it to take effect. Creating a Power Control Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click Power Control Policies and choose Create Power Control Policy. In the Create Power Control Policy dialog box, complete the following fields: Name Description Name field The name of the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A description of the policy. We recommend that you include information about where and when the policy should be used. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 569 Configuring Manual Blade-Level Power Capping Name Description Power Capping field What happens to a server when the demand for power within a power group exceeds the power supply. This can be one of the following: • No Cap—The server runs at full capacity regardless of the power requirements of the other servers in its power group. • cap—The server is allocated a minimum amount of power capacity based on the the server's priority relative to the other servers in its server group. If more power becomes available, Cisco UCS allows the capped servers to exceed their original allocations. It only lowers the allocations if there is a drop in the total power available to the power group. Priority field The priority the server has within its power group when power capping is in effect. Enter an integer between 1 and 10, where 1 is the highest priority. Step 6 Click OK. What to Do Next Include the policy in a service profile or service profile template. Deleting a Power Control Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Servers > Policies > Organization_Name. Expand the Power Control Policies node. Right-click the policy you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Configuring Manual Blade-Level Power Capping Manual Blade-Level Power Capping When manual blade-level power capping is configured in the global cap policy, you can set a power cap for each blade server in a Cisco UCS domain. Cisco UCS Manager GUI Configuration Guide, Release 2.0 570 OL-25712-04 Configuring Manual Blade-Level Power Capping The following configuration options are available: Enabled You can specify the maximum amount of power that the server can consume at one time. This maximum can be any amount between 0 watts and 1100 watts. Disabled No power usage limitations are imposed upon the server. The server can use as much power as it requires. If the server encounters a spike in power usage that meets or exceeds the maximum configured for the server, Cisco UCS Manager does not disconnect or shut down the server. Instead, Cisco UCS Manager reduces the power that is made available to the server. This reduction can slow down the server, including a reduction in CPU speed. Setting the Blade-Level Power Cap for a Server Before You Begin Make sure the global power allocation policy is set to Manual Blade Level Cap on the Global Policies tab. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server for which you want to set the power budget. In the Work pane, click the General tab. Step 5 In the Power Budget area, do the following: a) Click the Expand icon to the right of the heading to display the fields. b) Complete the following fields: Name Description Admin Status field Whether this server is power capped. This can be one of the following: • Unbounded—The server is not power capped under any circumstances. • Enabled—Cisco UCS Manager GUI displays the Watts field. Note Watts field Power capping only goes into effect if there is insufficient power available to the chassis to meet the demand. If there is sufficient power, the server can use as many watts as it requires. The maximum number of watts the server can use if there is not enough power to the chassis to meet the demand. Enter an integer between 0 and 10000000. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 571 Configuring Manual Blade-Level Power Capping Step 6 Click Save Changes. Viewing the Blade-Level Power Cap Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis. Choose the chassis for which you want to view the server power usage. Do one of the following: • To view the power usage for all servers in the chassis, click the Power tab in the Work pane. • To view the power usage for one server in the chassis, expand the chassis and click the server. Then click the Power tab in the Work pane. Step 5 If necessary, expand the Motherboards node to view the power counters. Cisco UCS Manager GUI Configuration Guide, Release 2.0 572 OL-25712-04 PART VI System Management • Managing Time Zones, page 575 • Managing the Chassis, page 577 • Managing Blade Servers, page 585 • Managing Rack-Mount Servers, page 599 • Starting the KVM Console, page 611 • Managing the I/O Modules, page 617 • Backing Up and Restoring the Configuration, page 619 • Recovering a Lost Password, page 633 CHAPTER 34 Managing Time Zones This chapter includes the following sections: • Time Zones, page 575 • Setting the Time Zone, page 575 • Adding an NTP Server, page 576 • Deleting an NTP Server, page 576 Time Zones Cisco UCS requires a domain-specific time zone setting and an NTP server to ensure the correct time display in Cisco UCS Manager. If you do not configure both of these settings in a Cisco UCS domain, the time does not display correctly. Setting the Time Zone Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 In the Admin tab, expand All. Click Timezone Management. In the Work pane, click the General tab. Step 5 Step 6 From the Timezone drop-down list, select the time zone you want to use for the Cisco UCS domain. Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 575 Adding an NTP Server Adding an NTP Server Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 In the Admin tab, expand All. Click Timezone Management. In the Work pane, click the General tab. Step 5 Step 6 In the NTP Servers area, click the + button on the table icon bar. In the Add NTP Server dialog box, do the following: a) In the NTP Server field, enter the IP address or hostname of the NTP server you want to use for this Cisco UCS domain. b) Click OK. Deleting an NTP Server Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 In the Admin tab, expand All. Click Timezone Management. In the Work pane, click the General tab. Step 5 Step 6 Step 7 In the NTP Servers area, right-click the server you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 576 OL-25712-04 CHAPTER 35 Managing the Chassis This chapter includes the following sections: • Chassis Management in Cisco UCS Manager GUI , page 577 • Guidelines for Removing and Decommissioning Chassis, page 577 • Acknowledging a Chassis, page 578 • Decommissioning a Chassis, page 579 • Removing a Chassis, page 579 • Recommissioning a Single Chassis, page 579 • Recommissioning Multiple Chassis, page 580 • Renumbering a Chassis, page 581 • Toggling the Locator LED, page 582 • Viewing the POST Results for a Chassis, page 582 Chassis Management in Cisco UCS Manager GUI You can manage and monitor all chassis in a Cisco UCS domain through Cisco UCS Manager GUI. Guidelines for Removing and Decommissioning Chassis Consider the following guidelines when deciding whether to remove or decommission a chassis using Cisco UCS Manager: Decommissioning a Chassis Decommissioning is performed when a chassis is physically present and connected but you want to temporarily remove it from the configuration. Because it is expected that a decommissioned chassis will be eventually recommissioned, a portion of the chassis' information is retained by Cisco UCS Manager for future use. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 577 Acknowledging a Chassis Removing a Chassis Removing is performed when you physically remove a chassis from the system. Once the physical removal of the chassis is completed, the configuration for that chassis can be removed in Cisco UCS Manager. Note You cannot remove a chassis from Cisco UCS Manager if it is physically present and connected. If you need to add a removed chassis back to the configuration, it must be reconnected and then rediscovered. During rediscovery Cisco UCS Manager will assign the chassis a new ID that may be different from ID that it held before. Acknowledging a Chassis Perform the following procedure if you increase or decrease the number of links that connect the chassis to the fabric interconnect. Acknowledging the chassis ensures that Cisco UCS Manager is aware of the change in the number of links and that traffics flows along all available links. After you enable or disable a port on a fabric interconnect, wait for at least 1 minute before you reacknowledge the chassis. If you reacknowledge the chassis too soon, the pinning of server traffic from the chassis may not be updated with the changes to the port that you enabled or disabled. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis. Choose the chassis that you want to acknowledge. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Acknowledge Chassis. If Cisco UCS Manager displays a confirmation dialog box, click Yes. Cisco UCS Manager disconnects the chassis and then rebuilds the connections between the chassis and the fabric interconnect or fabric interconnects in the system. Cisco UCS Manager GUI Configuration Guide, Release 2.0 578 OL-25712-04 Decommissioning a Chassis Decommissioning a Chassis Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis. Choose the chassis that you want to decommission. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Decommission Chassis. If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. The decommission may take several minutes to complete. After the chassis has been removed from the configuration, Cisco UCS Manager adds the chassis to the Decommissioned tab. Removing a Chassis Before You Begin Physically remove the chassis before performing the following procedure. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis. Choose the chassis that you want to remove. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Remove Chassis. If Cisco UCS Manager displays a confirmation dialog box, click Yes. The removal may take several minutes to complete. Recommissioning a Single Chassis This procedure returns the chassis to the configuration and applies the chassis discovery policy to the chassis. After this procedure, you can access the chassis and any servers in it. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 579 Recommissioning Multiple Chassis Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 In the Equipment tab, expand the Equipment node. Click the Chassis node. In the Work pane, click the Decommissioned tab. Step 5 For the chassis that you want to recommission, do the following: a) Right-click the chassis and choose Re-commission Chassis. b) In the Chassis ID field of the Re-commission Chassis dialog box, type or use the arrows to choose the ID that you want to assign to the chassis c) Click OK. Step 6 If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. This procedure may take several minutes to complete. After the chassis has been recommissioned, Cisco UCS Manager runs the chassis discovery policy and adds the chassis to the list in the Navigation pane. Recommissioning Multiple Chassis This procedure returns the chassis to the configuration and applies the chassis discovery policy to the chassis. After this procedure, you can access the chassis and any servers in it. Note You cannot renumber the chassis when you recommission multiple chassis at the same time. Cisco UCS Manager assigns the same ID that the chassis had previously. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 In the Equipment tab, expand the Equipment node. Click the Chassis node. In the Work pane, click the Decommissioned tab. Step 5 Step 6 Step 7 In the row for each chassis that you want to recommission, check the Re-commission check box. Click Save Changes. If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. This procedure may take several minutes to complete. After the chassis has been recommissioned, Cisco UCS Manager runs the chassis discovery policy and adds the chassis to the list in the Navigation pane. Cisco UCS Manager GUI Configuration Guide, Release 2.0 580 OL-25712-04 Renumbering a Chassis Renumbering a Chassis Note You cannot renumber a blade server through Cisco UCS Manager. The ID assigned to a blade server is determined by its physical slot in the chassis. To renumber a blade server, you must physically move the server to a different slot in the chassis. Before You Begin If you are swapping IDs between chassis, you must first decommission both chassis and then wait for the chassis decommission FSM to complete before proceeding with the renumbering steps. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Chassis. Verify that the Chassis node does not include the following: • The chassis you want to renumber • A chassis with the number you want to use If either of these chassis are listed in the Chassis node, decommission those chassis. You must wait until the decommission FSM is complete and the chassis are not listed in the Chassis node before continuing. This might take several minutes. Step 4 Step 5 On the Equipment tab, click the Chassis node. In the Work pane, click the Decommissioned tab. Step 6 For the chassis that you want to renumber, do the following: a) Right-click the chassis and choose Re-commission Chassis. b) In the Chassis ID field of the Re-commission Chassis dialog box, type or use the arrows to choose the ID that you want to assign to the chassis c) Click OK Step 7 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 581 Toggling the Locator LED Toggling the Locator LED Turning on the Locator LED for a Chassis Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis. Click the chassis that you need to locate. In the Work pane, click the General tab. Step 5 In the Actions area, click Turn on Locator LED. This action is not available if the locator LED is already turned on. The LED on the chassis starts flashing. Turning off the Locator LED for a Chassis Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis. Choose the chassis for which you want to turn off the locator LED. In the Work pane, click the General tab. Step 5 In the Actions area, click Turn off Locator LED. This action is not available if the locator LED is already turned off. The LED on the chassis stops flashing. Viewing the POST Results for a Chassis You can view any errors collected during the Power On Self-Test process for all servers and adapters in a chassis. Cisco UCS Manager GUI Configuration Guide, Release 2.0 582 OL-25712-04 Viewing the POST Results for a Chassis Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis. Choose the chassis for which you want to view the POST results. In the Work pane, click the General tab. Step 5 In the Actions area, click View POST Results. The POST Results dialog box lists the POST results for each server in the chassis and its adapters. Step 6 Step 7 (Optional) Click the link in the Affected Object column to view the properties of that adapter. Click OK to close the POST Results dialog box. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 583 Viewing the POST Results for a Chassis Cisco UCS Manager GUI Configuration Guide, Release 2.0 584 OL-25712-04 CHAPTER 36 Managing Blade Servers This chapter includes the following sections: • Blade Server Management, page 585 • Guidelines for Removing and Decommissioning Blade Servers, page 586 • Booting Blade Servers, page 586 • Shutting Down Blade Servers, page 588 • Resetting a Blade Server, page 589 • Avoiding Unexpected Server Power Changes, page 590 • Reacknowledging a Blade Server, page 591 • Removing a Server from a Chassis, page 591 • Decommissioning a Blade Server, page 592 • Recommissioning a Blade Server, page 593 • Reacknowledging a Server Slot in a Chassis, page 593 • Removing a Non-Existent Blade Server from the Configuration Database, page 594 • Turning the Locator LED for a Blade Server On and Off, page 594 • Resetting the CMOS for a Blade Server, page 594 • Resetting the CIMC for a Blade Server, page 595 • Recovering the Corrupt BIOS on a Blade Server, page 595 • Viewing the POST Results for a Blade Server, page 596 • Issuing an NMI from a Blade Server, page 597 Blade Server Management You can manage and monitor all blade servers in a Cisco UCS domain through Cisco UCS Manager. Some blade server management tasks, such as changes to the power state, can be performed from the server and service profile. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 585 Guidelines for Removing and Decommissioning Blade Servers The remaining management tasks can only be performed on the server. If a blade server slot in a chassis is empty, Cisco UCS Manager provides information, errors, and faults for that slot. You can also reacknowledge the slot to resolve server mismatch errors and to have Cisco UCS Manager rediscover the blade server in the slot. Guidelines for Removing and Decommissioning Blade Servers Consider the following guidelines when deciding whether to remove or decommission a blade server using Cisco UCS Manager: Decommissioning a Blade Server Decommissioning is performed when a blade server is physically present and connected but you want to temporarily remove it from the configuration. Because it is expected that a decommissioned blade server will be eventually recommissioned, a portion of the server's information is retained by Cisco UCS Manager for future use. Removing a Blade Server Removing is performed when you physically remove a blade server from the server by disconnecting it from the chassis. You cannot remove a blade server from Cisco UCS Manager if it is physically present and connected to a chassis. Once the physical removal of the blade server is completed, the configuration for that blade server can be removed in Cisco UCS Manager. During removal, active links to the blade server are disabled, all entries from databases are removed, and the server is automatically removed from any server pools that it was assigned to during discovery. Note Only those servers added to a server pool automatically during discovery will be removed automatically. Servers that have been manually added to a server pool have to be removed manually. If you need to add a removed blade server back to the configuration, it must be reconnected and then rediscovered. When a server is reintroduced to Cisco UCS Manager it is treated like a new server and is subject to the deep discovery process. For this reason, it's possible that Cisco UCS Manager will assign the server a new ID that may be different from the ID that it held before. Booting Blade Servers Booting a Blade Server If the Boot Server link is dimmed in the Actions area, you must shut down the server first. Cisco UCS Manager GUI Configuration Guide, Release 2.0 586 OL-25712-04 Booting Blade Servers Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server that you want to boot. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Boot Server. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. After the server has booted, the Overall Status field on the General tab displays an OK status. Booting a Server from the Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization where you want to create the service profile. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Choose the service profile that requires the associated server to be booted. In the Work pane, click the General tab. Step 6 Step 7 Step 8 In the Actions area, click Boot Server. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click OK in the Boot Server dialog box. After the server has booted, the Overall Status field on the General tab displays an ok status or an up status. Determining the Boot Order of a Blade Server Tip You can also view the boot order tabs from the General tab of the service profile associated with a server. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 587 Shutting Down Blade Servers Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Click the server for which you want to determine the boot order. In the Work pane, click the General tab. Step 5 Step 6 Step 7 If the Boot Order Details area is not expanded, click the Expand icon to the right of the heading. To view the boot order assigned to the server, click the Configured Boot Order tab. To view what will boot from the various devices in the physical server configuration, click the Actual Boot Order tab. Note The Actual Boot Order tab always shows "Internal EFI Shell" at the bottom of the boot order list. Shutting Down Blade Servers Shutting Down a Blade Server When you use this procedure to shut down a server with an installed operating system, Cisco UCS Manager triggers the OS into a graceful shutdown sequence. If the Shutdown Server link is dimmed in the Actions area, the server is not running. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server that you want to shut down. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Shutdown Server. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. After the server has been successfully shut down, the Overall Status field on the General tab displays a power-off status. Shutting Down a Server from the Service Profile When you use this procedure to shut down a server with an installed operating system, Cisco UCS Manager triggers the OS into a graceful shutdown sequence. If the Shutdown Server link is dimmed in the Actions area, the server is not running. Cisco UCS Manager GUI Configuration Guide, Release 2.0 588 OL-25712-04 Resetting a Blade Server Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization where you want to create the service profile. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Choose the service profile that requires the associated server to be shut down. In the Work pane, click the General tab. Step 6 Step 7 In the Actions area, click Shutdown Server. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. After the server has been successfully shut down, the Overall Status field on the General tab displays a down status or a power-off status. Resetting a Blade Server When you reset a server, Cisco UCS Manager sends a pulse on the reset line. You can choose to gracefully shut down the operating system. If the operating system does not support a graceful shut down, the server is power cycled. The option to have Cisco UCS Manager complete all management operations before it resets the server does not guarantee that these operations will be completed before the server is reset. Note If you are trying to boot a server from a power-down state, you should not use Reset. If you continue the power-up with this process, the desired power state of the servers will become out of sync with the actual power state and the servers may unexpectedly shut down at a later time. To safely reboot the selected servers from a power-down state, click Cancel then select the Boot Server action. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server that you want to reset. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Reset. In the Reset Server dialog box, do the following: a) Click the Power Cycle option. b) (Optional) Check the check box if you want Cisco UCS Manager to complete all management operations that are pending on this server. c) Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 589 Avoiding Unexpected Server Power Changes The reset may take several minutes to complete. After the server has been reset, the Overall Status field on the General tab displays an ok status. Avoiding Unexpected Server Power Changes If a server is not associated with a service profile, you can use any available means to change the server power state, including the physical Power or Reset buttons on the server. If a server is associated with, or assigned to, a service profile, you should only use the following methods to change the server power state: • In Cisco UCS Manager GUI, go to the General tab for the server or the service profile associated with the server and select Boot Server or Shutdown Server from the Actions area. • In Cisco UCS Manager CLI, scope to the server or the service profile associated with the server and use the power up or power down commands. Important Do not use any of the following options on an associated server that is currently powered off: • Reset in the GUI • cycle cycle-immediate or reset hard-reset-immediate in the CLI • The physical Power or Reset buttons on the server If you reset, cycle, or use the physical power buttons on a server that is currently powered off, the server's actual power state may become out of sync with the desired power state setting in the service profile. If the communication between the server and Cisco UCS Manager is disrupted or if the service profile configuration changes, Cisco UCS Manager may apply the desired power state from the service profile to the server, causing an unexpected power change. In Cisco UCS release 2.0.1, power synchronization issues can lead to unexpected server shut downs or restarts as shown below: Desired Power State in Service Profile Current Server Power State Server Power State After Communication Is Disrupted Up Powered Off Powered On Down Powered On Powered Off Starting in Cisco UCS release 2.0.2, power synchronization issues can lead to an unexpected server restart, as shown below: Desired Power State in Service Profile Current Server Power State Server Power State After Communication Is Disrupted Up Powered Off Powered On Cisco UCS Manager GUI Configuration Guide, Release 2.0 590 OL-25712-04 Reacknowledging a Blade Server Desired Power State in Service Profile Current Server Power State Server Power State After Communication Is Disrupted Down Powered On Powered On Note Running servers are not shut down regardless of the desired power state in the service profile. Reacknowledging a Blade Server Perform the following procedure if you need to have Cisco UCS Manager rediscover the server and all endpoints in the server. For example, you can use this procedure if a server is stuck in an unexpected state, such as the discovery state. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server that you want to acknowledge. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Server Maintenance. In the Maintenance dialog box, do the following: a) Click Re-acknowledge. b) Click OK. Cisco UCS Manager disconnects the server and then builds the connections between the server and the fabric interconnect or fabric interconnects in the system. The acknowledgment may take several minutes to complete. After the server has been acknowledged, the Overall Status field on the General tab displays an OK status. Removing a Server from a Chassis Before You Begin Physically remove the server from its chassis before performing the following procedure. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 591 Decommissioning a Blade Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server that you want to remove from the chassis. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Server Maintenance. In the Maintenance dialog box, do the following: a) Click Decommission. b) Click OK. The server is removed from the Cisco UCS configuration. Step 7 Go to the physical location of the chassis and remove the server hardware from the slot. For instructions on how to remove the server hardware, see the Cisco UCS Hardware Installation Guide for your chassis. What to Do Next If you physically re-install the blade server, you must re-acknowledge the slot to have Cisco UCS Manager rediscover the server. For more information, see Reacknowledging a Server Slot in a Chassis, on page 593. Decommissioning a Blade Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server that you want to decommission. Step 5 Step 6 In the Actions area, click Server Maintenance. In the Maintenance dialog box, do the following: In the Work pane, click the General tab. a) Click Decommission. b) Click OK. The server is removed from the Cisco UCS configuration. What to Do Next If you physically re-install the blade server, you must re-acknowledge the slot to have Cisco UCS Manager rediscover the server. Cisco UCS Manager GUI Configuration Guide, Release 2.0 592 OL-25712-04 Recommissioning a Blade Server For more information, see Reacknowledging a Server Slot in a Chassis, on page 593. Recommissioning a Blade Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Chassis node. In the Work pane, click the Decommissioned tab. Step 4 On the row for each blade server that you want to recommission, do the following: a) In the Recommission column, check the check box. b) Click Save Changes Step 5 Step 6 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. (Optional) Monitor the progress of the server recommission and discovery on the FSM tab for the server. What to Do Next • Reacknowledging a Server Slot in a Chassis Perform the following procedure if you decommissioned a blade server without removing the physical hardware from the chassis and you want Cisco UCS Manager to rediscover and recommission the server. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server whose slot you want to reacknowledge. If Cisco UCS Manager displays a Resolve Slot Issue dialog box, do one of the following: Option Description The here link in the Situation area Click this link and then click Yes in the confirmation dialog box. Cisco UCS Manager reacknowledges the slot and discovers the server in the slot. OK Click this button if you want to proceed to the General tab. You can use the Reacknowledge Slot link in the Actions area to have Cisco UCS Manager reacknowledge the slot and discover the server in the slot. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 593 Removing a Non-Existent Blade Server from the Configuration Database Removing a Non-Existent Blade Server from the Configuration Database Perform the following procedure if you physically removed the server hardware without first decommissioning the server. You cannot perform this procedure if the server is physically present. If you want to physically remove a server, see Removing a Server from a Chassis, on page 591. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server that you want to remove from the configuration database. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Server Maintenance. In the Maintenance dialog box, do the following: a) Click Remove. b) Click OK. Cisco UCS Manager removes all data about the server from its configuration database. The server slot is now available for you to insert new server hardware. Turning the Locator LED for a Blade Server On and Off Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server for which you want to turn the locator LED on or off. In the Work pane, click the General tab. Step 5 In the Actions area, click one of the following: • Turn on Locator LED • Turn off Locator LED Resetting the CMOS for a Blade Server On rare occasions, troubleshooting a server may require you to reset the CMOS. This procedure is not part of the normal maintenance of a server. Cisco UCS Manager GUI Configuration Guide, Release 2.0 594 OL-25712-04 Resetting the CIMC for a Blade Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server for which you want to reset the CMOS. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Recover Server. In the Recover Server dialog box, do the following: a) Click Reset CMOS. b) Click OK. Resetting the CIMC for a Blade Server On rare occasions, such as an issue with the current running firmware, troubleshooting a server may require you to reset the CIMC. This procedure is not part of the normal maintenance of a server. After you reset the CIMC, the server boots with the running version of the firmware for that server. If the CIMC is reset, the power monitoring functions of Cisco UCS become briefly unavailable for as long as it takes for the CIMC to reboot. While this usually only takes 20 seconds, there is a possibility that the peak power cap could be exceeded during that time. To avoid exceeding the configured power cap in a very low power-capped environment, consider staggering the rebooting or activation of CIMCs. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server for which you want to reset the CIMC. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Recover Server. In the Recover Server dialog box, do the following: a) Click Reset CIMC (Server Controller). b) Click OK. Recovering the Corrupt BIOS on a Blade Server On rare occasions, an issue with a server may require you to recover the corrupted BIOS. This procedure is not part of the normal maintenance of a server. After you recover the BIOS, the server boots with the running version of the firmware for that server. This radio button may be dimmed if the BIOS does not require recovery or the option is not available for a particular server. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 595 Viewing the POST Results for a Blade Server Before You Begin Important Remove all attached or mapped USB storage from a server before you attempt to recover the corrupt BIOS on that server. If an external USB drive is attached or mapped from vMedia to the server, BIOS recovery fails. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server for which you want to recover the BIOS. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Recover Server. In the Recover Server dialog box, do the following: a) Click Recover Corrupt BIOS. Note If this option is not available for a specific server, follow the instructions to update and activate the BIOS for a server. b) Click OK. Step 7 Step 8 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. In the Recover Corrupt BIOS dialog box, do the following: a) Complete the following fields: Name Description Version To Be Activated drop-down list Choose the firmware version that you want to activate from the drop-down list. Ignore Compatibility Check check box By default, Cisco UCS makes sure that the firmware version is compatible with everything running on the server before it activates that version. Check this check box if you want Cisco UCS to activate the firmware without making sure that it is compatible first. Note We recommend that you use this option only when explicitly directed to do so by a technical support representative. b) Click OK. Viewing the POST Results for a Blade Server You can view any errors collected during the Power On Self-Test process for a server and its adapters. Cisco UCS Manager GUI Configuration Guide, Release 2.0 596 OL-25712-04 Issuing an NMI from a Blade Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server for which you want to view the POST results. In the Work pane, click the General tab. Step 5 In the Actions area, click View POST Results. The POST Results dialog box lists the POST results for the server and its adapters. Step 6 Step 7 (Optional) Click the link in the Affected Object column to view the properties of that adapter. Click OK to close the POST Results dialog box. Issuing an NMI from a Blade Server Perform the following procedure if the system remains unresponsive and you need Cisco UCS Manager to issue a Non Maskable Interrupt (NMI) to the BIOS or operating system from the CIMC. This action creates a core dump or stack trace, depending on the operating system installed on the server. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server that you want to issue the NMI. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Server Maintenance. In the Maintenance dialog box, do the following: a) Click Diagnostic Interrupt. b) Click OK. Cisco UCS Manager sends an NMI to the BIOS or operating system. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 597 Issuing an NMI from a Blade Server Cisco UCS Manager GUI Configuration Guide, Release 2.0 598 OL-25712-04 CHAPTER 37 Managing Rack-Mount Servers This chapter includes the following sections: • Rack-Mount Server Management, page 599 • Guidelines for Removing and Decommissioning Rack-Mount Servers, page 600 • Booting Rack-Mount Servers, page 600 • Shutting Down Rack-Mount Servers, page 602 • Resetting a Rack-Mount Server, page 603 • Avoiding Unexpected Server Power Changes, page 604 • Reacknowledging a Rack-Mount Server, page 605 • Decommissioning a Rack-Mount Server, page 605 • Recommissioning a Rack-Mount Server, page 606 • Renumbering a Rack-Mount Server, page 606 • Removing a Non-Existent Rack-Mount Server from the Configuration Database, page 607 • Turning the Locator LED for a Rack-Mount Server On and Off, page 607 • Resetting the CMOS for a Rack-Mount Server, page 608 • Resetting the CIMC for a Rack-Mount Server, page 608 • Recovering the Corrupt BIOS on a Rack-Mount Server, page 609 • Viewing the POST Results for a Rack-Mount Server, page 610 • Issuing an NMI from a Rack-Mount Server, page 610 Rack-Mount Server Management You can manage and monitor all rack-mount servers that have been integrated with a Cisco UCS domain through Cisco UCS Manager. All management and monitoring features are supported for rack-mount servers except power capping. Some rack-mount server management tasks, such as changes to the power state, can Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 599 Guidelines for Removing and Decommissioning Rack-Mount Servers be performed from both the server and service profile. The remaining management tasks can only be performed on the server. Cisco UCS Manager provides information, errors, and faults for each rack-mount server that it has discovered. Tip For information about how to integrate a supported Cisco UCS rack-mount server with Cisco UCS Manager, see the hardware installation guide for that server. Guidelines for Removing and Decommissioning Rack-Mount Servers Consider the following guidelines when deciding whether to remove or decommission a rack-mount server using Cisco UCS Manager: Decommissioning a Rack-Mount server Decommissioning is performed when a rack-mount server is physically present and connected but you want to temporarily remove it from the configuration. Because it is expected that a decommissioned rack-mount server will be eventually recommissioned, a portion of the server's information is retained by Cisco UCS Manager for future use. Removing a Rack-Mount server Removing is performed when you physically remove the server from the system by disconnecting the rack-mount server from the fabric extender. You cannot remove a rack-mount server from Cisco UCS Manager if it is physically present and connected to the fabric extender. Once the rack-mount server is disconnected, the configuration for that rack-mount server can be removed in Cisco UCS Manager. During removal, management interfaces are disconnected, all entries from databases are removed, and the server is automatically removed from any server pools that it was assigned to during discovery. Note Only those servers added to a server pool automatically during discovery will be removed automatically. Servers that have been manually added to a server pool have to be removed manually. If you need to add a removed rack-mount server back to the configuration, it must be reconnected and then rediscovered. When a server is reintroduced to Cisco UCS Manager it is treated like a new server and is subject to the deep discovery process. For this reason, it's possible that Cisco UCS Manager will assign the server a new ID that may be different from the ID that it held before. Booting Rack-Mount Servers Booting a Rack-Mount Server If the Boot Server link is dimmed in the Actions area, you must shut down the server first. Cisco UCS Manager GUI Configuration Guide, Release 2.0 600 OL-25712-04 Booting Rack-Mount Servers Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Choose the server that you want to boot. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Boot Server. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. After the server has booted, the Overall Status field on the General tab displays an OK status. Booting a Server from the Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization where you want to create the service profile. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Choose the service profile that requires the associated server to be booted. In the Work pane, click the General tab. Step 6 Step 7 Step 8 In the Actions area, click Boot Server. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Click OK in the Boot Server dialog box. After the server has booted, the Overall Status field on the General tab displays an ok status or an up status. Determining the Boot Order of a Rack-Mount Server Tip You can also view the boot order tabs from the General tab of the service profile associated with a server. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 601 Shutting Down Rack-Mount Servers Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Click the server for which you want to determine the boot order. In the Work pane, click the General tab. Step 5 Step 6 Step 7 If the Boot Order Details area is not expanded, click the Expand icon to the right of the heading. To view the boot order assigned to the server, click the Configured Boot Order tab. To view what will boot from the various devices in the physical server configuration, click the Actual Boot Order tab. Note The Actual Boot Order tab always shows "Internal EFI Shell" at the bottom of the boot order list. Shutting Down Rack-Mount Servers Shutting Down a Rack-Mount Server When you use this procedure to shut down a server with an installed operating system, Cisco UCS Manager triggers the OS into a graceful shutdown sequence. If the Shutdown server link is dimmed in the Actions area, the server is not running. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Choose the server that you want to shut down. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Shutdown Server. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. After the server has been successfully shut down, the Overall Status field on the General tab displays a power-off status. Shutting Down a Server from the Service Profile When you use this procedure to shut down a server with an installed operating system, Cisco UCS Manager triggers the OS into a graceful shutdown sequence. If the Shutdown Server link is dimmed in the Actions area, the server is not running. Cisco UCS Manager GUI Configuration Guide, Release 2.0 602 OL-25712-04 Resetting a Rack-Mount Server Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization where you want to create the service profile. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Choose the service profile that requires the associated server to be shut down. In the Work pane, click the General tab. Step 6 Step 7 In the Actions area, click Shutdown Server. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. After the server has been successfully shut down, the Overall Status field on the General tab displays a down status or a power-off status. Resetting a Rack-Mount Server When you reset a server, Cisco UCS Manager sends a pulse on the reset line. You can choose to gracefully shut down the operating system. If the operating system does not support a graceful shut down, the server is power cycled. The option to have Cisco UCS Manager complete all management operations before it resets the server does not guarantee that these operations will be completed before the server is reset. Note If you are trying to boot a server from a power-down state, you should not use Reset. If you continue the power-up with this process, the desired power state of the servers will become out of sync with the actual power state and the servers may unexpectedly shut down at a later time. To safely reboot the selected servers from a power-down state, click Cancel then select the Boot Server action. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Choose the server that you want to reset. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Reset. In the Reset Server dialog box, do the following: a) Click the Power Cycle option. b) (Optional) Check the check box if you want Cisco UCS Manager to complete all management operations that are pending on this server. c) Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 603 Avoiding Unexpected Server Power Changes The reset may take several minutes to complete. After the server has been reset, the Overall Status field on the General tab displays an ok status. Avoiding Unexpected Server Power Changes If a server is not associated with a service profile, you can use any available means to change the server power state, including the physical Power or Reset buttons on the server. If a server is associated with, or assigned to, a service profile, you should only use the following methods to change the server power state: • In Cisco UCS Manager GUI, go to the General tab for the server or the service profile associated with the server and select Boot Server or Shutdown Server from the Actions area. • In Cisco UCS Manager CLI, scope to the server or the service profile associated with the server and use the power up or power down commands. Important Do not use any of the following options on an associated server that is currently powered off: • Reset in the GUI • cycle cycle-immediate or reset hard-reset-immediate in the CLI • The physical Power or Reset buttons on the server If you reset, cycle, or use the physical power buttons on a server that is currently powered off, the server's actual power state may become out of sync with the desired power state setting in the service profile. If the communication between the server and Cisco UCS Manager is disrupted or if the service profile configuration changes, Cisco UCS Manager may apply the desired power state from the service profile to the server, causing an unexpected power change. In Cisco UCS release 2.0.1, power synchronization issues can lead to unexpected server shut downs or restarts as shown below: Desired Power State in Service Profile Current Server Power State Server Power State After Communication Is Disrupted Up Powered Off Powered On Down Powered On Powered Off Starting in Cisco UCS release 2.0.2, power synchronization issues can lead to an unexpected server restart, as shown below: Desired Power State in Service Profile Current Server Power State Server Power State After Communication Is Disrupted Up Powered Off Powered On Cisco UCS Manager GUI Configuration Guide, Release 2.0 604 OL-25712-04 Reacknowledging a Rack-Mount Server Desired Power State in Service Profile Current Server Power State Server Power State After Communication Is Disrupted Down Powered On Powered On Note Running servers are not shut down regardless of the desired power state in the service profile. Reacknowledging a Rack-Mount Server Perform the following procedure if you need to have Cisco UCS Manager rediscover the server and all endpoints in the server. For example, you can use this procedure if a server is stuck in an unexpected state, such as the discovery state. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Choose the server that you want to acknowledge. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Server Maintenance. In the Maintenance dialog box, do the following: a) Click Re-acknowledge. b) Click OK. Cisco UCS Manager disconnects the server and then builds the connections between the server and the fabric interconnect or fabric interconnects in the system. The acknowledgment may take several minutes to complete. After the server has been acknowledged, the Overall Status field on the General tab displays an OK status. Decommissioning a Rack-Mount Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Choose the server that you want to decommission. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Server Maintenance. In the Maintenance dialog box, do the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 605 Recommissioning a Rack-Mount Server a) Click Decommission. b) Click OK. The server is removed from the Cisco UCS configuration. Recommissioning a Rack-Mount Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Rack-Mounts node. Step 4 On the row for each rack-mount server that you want to recommission, do the following: a) In the Recommission column, check the check box. b) Click Save Changes Step 5 Step 6 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. (Optional) Monitor the progress of the server recommission and discovery on the FSM tab for the server. In the Work pane, click the Decommissioned tab. Renumbering a Rack-Mount Server Before You Begin If you are swapping IDs between servers, you must first decommission both servers and then wait for the server decommission FSM to complete before proceeding with the renumbering steps. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Expand the Servers node and verify that it does not include the following: • The rack-mount server you want to renumber • A rack-mount server with the number you want to use If either of these servers are listed in the Servers node, decommission those servers. You must wait until the decommission FSM is complete and the servers are not listed in the node before continuing. This might take several minutes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 606 OL-25712-04 Removing a Non-Existent Rack-Mount Server from the Configuration Database Step 4 Step 5 Step 6 Choose the rack-mount server that you want to renumber. On the Equipment tab, click the Rack-Mounts node. In the Work pane, click the Decommissioned tab. Step 7 On the row for each rack-mount server that you want to renumber, do the following: a) Double-click in the ID field, and enter the new number that you want to assign to the rack-mount server. b) In the Recommission column, check the check box. c) Click Save Changes Step 8 Step 9 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. (Optional) Monitor the progress of the server recommission and discovery on the FSM tab for the server. Removing a Non-Existent Rack-Mount Server from the Configuration Database Perform the following procedure if you physically removed the server hardware without first decommissioning the server. You cannot perform this procedure if the server is physically present. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Choose the server that you want to remove from the configuration database. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Server Maintenance. In the Maintenance dialog box, do the following: a) Click Remove. b) Click OK. Cisco UCS Manager removes all data about the server from its configuration database. The server slot is now available for you to insert new server hardware. Turning the Locator LED for a Rack-Mount Server On and Off Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Choose the server for which you want to turn the locator LED on or off. In the Work pane, click the General tab. Step 5 In the Actions area, click one of the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 607 Resetting the CMOS for a Rack-Mount Server • Turn on Locator LED • Turn off Locator LED Resetting the CMOS for a Rack-Mount Server On rare occasions, troubleshooting a server may require you to reset the CMOS. This procedure is not part of the normal maintenance of a server. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Choose the server for which you want to reset the CMOS. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Recover Server. In the Recover Server dialog box, do the following: a) Click Reset CMOS. b) Click OK. Resetting the CIMC for a Rack-Mount Server On rare occasions, such as an issue with the current running firmware, troubleshooting a server may require you to reset the CIMC. This procedure is not part of the normal maintenance of a server. After you reset the CIMC, the server boots with the running version of the firmware for that server. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Choose the server for which you want to reset the CIMC. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Recover Server. In the Recover Server dialog box, do the following: a) Click Reset CIMC (Server Controller). b) Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 608 OL-25712-04 Recovering the Corrupt BIOS on a Rack-Mount Server Recovering the Corrupt BIOS on a Rack-Mount Server On rare occasions, an issue with a server may require you to recover the corrupted BIOS. This procedure is not part of the normal maintenance of a server. After you recover the BIOS, the server boots with the running version of the firmware for that server. This radio button may be dimmed if the BIOS does not require recovery or the option is not available for a particular server. Before You Begin Important Remove all attached or mapped USB storage from a server before you attempt to recover the corrupt BIOS on that server. If an external USB drive is attached or mapped from vMedia to the server, BIOS recovery fails. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Choose the server for which you want to recover the BIOS. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Recover Server. In the Recover Server dialog box, do the following: a) Click Recover Corrupt BIOS. b) Click OK. Step 7 Step 8 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. In the Recover Corrupt BIOS dialog box, do the following: a) Complete the following fields: Name Description Version To Be Activated drop-down list Choose the firmware version that you want to activate from the drop-down list. Ignore Compatibility Check check box By default, Cisco UCS makes sure that the firmware version is compatible with everything running on the server before it activates that version. Check this check box if you want Cisco UCS to activate the firmware without making sure that it is compatible first. Note We recommend that you use this option only when explicitly directed to do so by a technical support representative. b) Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 609 Viewing the POST Results for a Rack-Mount Server Viewing the POST Results for a Rack-Mount Server You can view any errors collected during the Power On Self-Test process for a server and its adapters. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Choose the server for which you want to view the POST results. In the Work pane, click the General tab. Step 5 In the Actions area, click View POST Results. The POST Results dialog box lists the POST results for the server and its adapters. Step 6 Step 7 (Optional) Click the link in the Affected Object column to view the properties of that adapter. Click OK to close the POST Results dialog box. Issuing an NMI from a Rack-Mount Server Perform the following procedure if the system remains unresponsive and you need Cisco UCS Manager to issue a Non Maskable Interrupt (NMI) to the BIOS or operating system from the CIMC. This action creates a core dump or stack trace, depending on the operating system installed on the server. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Choose the server that you want to issue the NMI. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click Server Maintenance. In the Maintenance dialog box, do the following: a) Click Diagnostic Interrupt. b) Click OK. Cisco UCS Manager sends an NMI to the BIOS or operating system. Cisco UCS Manager GUI Configuration Guide, Release 2.0 610 OL-25712-04 CHAPTER 38 Starting the KVM Console This chapter includes the following sections: • KVM Console, page 611 • Starting the KVM Console from a Server, page 615 • Starting the KVM Console from a Service Profile , page 615 • Starting the KVM Console from the KVM Launch Manager, page 615 KVM Console The KVM console is an interface accessible from the Cisco UCS Manager GUI or the KVM Launch Manager that emulates a direct KVM connection. Unlike the KVM dongle, which requires you to be physically connected to the server, the KVM console allows you to connect to the server from a remote location across the network. You must ensure that either the server or the service profile associated with the server is configured with a CIMC IP address if you want to use the KVM console to access the server. The KVM console uses the CIMC IP address assigned to a server or a service profile to identify and connect with the correct server in a Cisco UCS. Instead of using CD/DVD or floppy drives directly connected to the server, the KVM console uses virtual media, which are actual disk drives or disk image files that are mapped to virtual CD/DVD or floppy drives. You can map any of the following to virtual drives: • CD/DVD or floppy drives on your computer • Disk image files on your computer • CD/DVD or floppy drives on the network • Disk image files on the network Recommendations for Using the KVM Console to Install a Server OS To install an OS from a virtual CD/DVD or floppy drive, you must ensure that the virtual CD/DVD or floppy drive is set as the first boot device in the service profile. Installing an OS using the KVM console may be slower than using the KVM dongle because the installation files must be downloaded across the network to the server. If you map a disk drive or disk image file from a Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 611 KVM Console network share to a virtual drive, the installation may be even slower because the installation files must be downloaded from the network to the KVM console (your computer) and then from the KVM console to the server. When using this installation method, we recommend that you have the installation media as close as possible to the system with the KVM console. Virtual KVM Console The KVM console is an interface accessible from CIMC that emulates a direct keyboard, video, and mouse (KVM) connection to the server. It allows you to connect to and control the server from a remote location, and to map physical locations to virtual drives that can by accessed by the server during this KVM session. Important The KVM console requires JRE (Java Runtime Environment) version 1.5.0 or higher. KVM Tab This tab provides command line access to the server. The menu options available in this tab are described below. Virtual Media Tab Instead of using CD/DVD or floppy drives physically connected to the server, the KVM console uses virtual media, which are actual disk drives or disk image files that are mapped to virtual CD/DVD or floppy drives on the server. The Client View table displays the floppy images, floppy drives, CD/DVD drives, and ISO images that are available to the server. Name Description Mapped column If the check box in this column is checked, the associated disk drive or image file can be accessed by the server. Clear the check box to disconnect the server from the drive or image file. Each drive or image file can exist either on the users local computer or on the network, and each falls into one of three categories: • Virtual CD/DVD • Removable Media • Floppy—This category includes USB keys or flash drives. You can enable Virtual Media for one drive or image in each of the three categories, but you cannot virtualize multiple drives or images in the same category. Read Only column If checked, the server cannot write to the Virtual Media device even if the device has write capability. Drive column Displays the path to the device used by the server. Exit button Returns to the KVM tab. Cisco UCS Manager GUI Configuration Guide, Release 2.0 612 OL-25712-04 KVM Console Name Description Create Image button Opens the Open dialog box that lets you navigate to the local folder that you want to map on the server. After the system has created the image, it saves the IMG file on your desktop and adds it to the Client View table. Check the check box in the Mapped column to complete the mapping process. Add Image button Opens the Open dialog box that lets you navigate to the ISO or IMG file you want to the server to access. After you select the file, the system adds it to the Client View table. Check the check box in the Mapped column to complete the mapping process. Remove Image button Removes the selected image from the Client View table. Details button Toggles the display of the Details area. This area contains a table showing the three device categories, their mapped status, read and write statistics, and the length of time that the device has been mapped. USB Reset button Resets all USB devices connected to the server. Note The Details area must be visible in order to use this button. File Menu Menu Item Description Capture to File Opens the Save dialog box that lets you save the current screen as a JPG image. Note Exit This option is only available on the KVM tab. Closes the KVM console. View Menu on the KVM Tab Menu Item Description Refresh Updates the console display with the server's current video output. Full Screen Expands the KVM console so that it fills the entire screen. Windowed Returns the KVM console to Windowed mode where it can be resized. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 613 KVM Console Menu Item Description Fit Resizes the console window to the minimum size needed to display the video image from the server. This option is only available if the console is in Windowed mode. Macros Menu on the KVM Tab Select the keyboard shortcut you want to execute on the remote system. Tools Menu on the KVM Tab Menu Item Description Session Options Opens the Session Options dialog box that lets you specify: • Whether all keystrokes are passed to the target system when the console is in Windowed mode. The default is no. • The termination key when in single cursor mode. The default is F12. • The mouse acceleration to use on the target system. The default is Windows. Single Cursor Turns on the single cursor feature, which offsets mouse alignment issues encountered on some remote operating systems. When you turn this feature on, the mouse pointer is trapped within the viewer window. To turn the feature off, press the termination key specified in the Session Options dialog box. Stats Opens the Stats dialog box, which displays the: • Frame rate measured in number of frames per second • Bandwidth measured in number of KBs per second • Compression measured in the percentage of compression being used • Packet rate measured in number of packets per second Session User List Opens the Session User List dialog box that shows all the user IDs that have an active KVM session. Cisco UCS Manager GUI Configuration Guide, Release 2.0 614 OL-25712-04 Starting the KVM Console from a Server Starting the KVM Console from a Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Choose the server that you want to access through the KVM console. In the Work pane, click the General tab. Step 5 In the Actions area, click KVM Console. The KVM console opens in a separate window. Tip If the Caps Lock key on your keyboard is on when you open a KVM session, and you subsequently turn off your Caps Lock key, the KVM console may continue to act as if Caps Lock is turned on. To synchronize the KVM console and your keyboard, press Caps Lock once without the KVM console in focus and then press Caps Lock again with the KVM console in focus. Starting the KVM Console from a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Service Profiles. Expand the node for the organization which contains the service profile for which you want to launch the KVM console. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Choose the service profile for which you need KVM access to the associated server. In the Work pane, click the General tab. Step 6 In the Actions area, click KVM Console. The KVM console opens in a separate window. Tip If the Caps Lock key on your keyboard is on when you open a KVM session, and you subsequently turn off your Caps Lock key, the KVM console may continue to act as if Caps Lock is turned on. To synchronize the KVM console and your keyboard, press Caps Lock once without the KVM console in focus and then press Caps Lock again with the KVM console in focus. Starting the KVM Console from the KVM Launch Manager The KVM Launch Manager enables you to access a server through the KVM console without logging in to Cisco UCS Manager. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 615 Starting the KVM Console from the KVM Launch Manager Before You Begin To access the KVM console for a server through the KVM Launch Manager, you need the following: • Cisco UCS username and password. • Name of the service profile associated with the server for which you want KVM access. Procedure Step 1 In your web browser, type or select the web link for Cisco UCS Manager GUI. Example: The default web link is http://UCSManager_IP or https://UCSManager_IP . In a standalone configuration, UCSManager_IP is the IP address for the management port on the fabric interconnect. In a cluster configuration, UCSManager_IP is the IP address assigned to Cisco UCS Manager. Step 2 Step 3 On the Cisco UCS Manager launch page, click Launch KVM Manager. If a Security Alert dialog box appears, click Yes to accept the security certificate and continue. Step 4 On the UCS - KVM Launch Manager Login page, do the following: a) Enter your Cisco UCS username and password. b) (Optional) If your Cisco UCS implementation includes multiple domains, select the appropriate domain from the Domain drop-down list. c) Click OK. Step 5 In the Service Profiles table of the KVM Launch Manager, do the following: a) Locate the row containing the service profile and associated server for which you need KVM access. b) In the Launch KVM column for that server, click Launch. The KVM console opens in a separate window. Tip If the Caps Lock key on your keyboard is on when you open a KVM session, and you subsequently turn off your Caps Lock key, the KVM console may continue to act as if Caps Lock is turned on. To synchronize the KVM console and your keyboard, press Caps Lock once without the KVM console in focus and then press Caps Lock again with the KVM console in focus. Cisco UCS Manager GUI Configuration Guide, Release 2.0 616 OL-25712-04 CHAPTER 39 Managing the I/O Modules This chapter includes the following sections: • I/O Module Management in Cisco UCS Manager GUI , page 617 • Resetting an I/O Module, page 617 • Viewing the POST Results for an I/O Module, page 617 I/O Module Management in Cisco UCS Manager GUI You can manage and monitor all I/O modules in a Cisco UCS domain through Cisco UCS Manager GUI. Resetting an I/O Module Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > IO Modules. Choose the I/O module that you want to reset. Step 5 Step 6 In the Actions area, click Reset IO Module. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. In the Work pane, click the General tab. Viewing the POST Results for an I/O Module You can view any errors collected during the Power On Self-Test process for an I/O module. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 617 Viewing the POST Results for an I/O Module Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > IO Modules. Choose the I/O module for which you want to view the POST results. In the Work pane, click the General tab. Step 5 In the Actions area, click View POST Results. The POST Results dialog box lists the POST results for the I/O module. Step 6 Click OK to close the POST Results dialog box. Cisco UCS Manager GUI Configuration Guide, Release 2.0 618 OL-25712-04 CHAPTER 40 Backing Up and Restoring the Configuration This chapter includes the following sections: • Backup and Export Configuration, page 619 • Backup Types, page 619 • Considerations and Recommendations for Backup Operations, page 620 • Import Configuration, page 621 • Import Methods, page 621 • System Restore, page 621 • Required User Role for Backup and Import Operations, page 621 • Backup Operations, page 622 • Import Operations, page 626 • Restoring the Configuration for a Fabric Interconnect, page 631 Backup and Export Configuration When you perform a backup through Cisco UCS Manager, you take a snapshot of all or part of the system configuration and export the file to a location on your network. You cannot use Cisco UCS Manager to back up data on the servers. You can perform a backup while the system is up and running. The backup operation only saves information from the management plane. It does not have any impact on the server or network traffic. Backup Types You can perform one or more of the following types of backups through Cisco UCS Manager: • Full state—A binary file that includes a snapshot of the entire system. You can use the file generated from this backup to restore the system during disaster recovery. This file can restore or rebuild the configuration on the original fabric interconnect, or recreate the configuration on a different fabric interconnect. You cannot use this file for an import. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 619 Considerations and Recommendations for Backup Operations • All configuration—An XML file that includes all system and logical configuration settings. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore. This file does not include passwords for locally authenticated users. • System configuration—An XML file that includes all system configuration settings such as usernames, roles, and locales. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore. • Logical configuration—An XML file that includes all logical configuration settings such as service profiles, VLANs, VSANs, pools, and policies. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore. Considerations and Recommendations for Backup Operations Before you create a backup operation, consider the following: Backup Locations The backup location is the destination or folder on the network where you want Cisco UCS Manager to export the backup file. You can maintain only one backup operation for each location where you plan to save a backup file. Potential to Overwrite Backup Files If you rerun a backup operation without changing the filename, Cisco UCS Manager overwrites the existing file on the server. To avoid overwriting existing backup files, change the filename in the backup operation or copy the existing file to another location. Multiple Types of Backups You can run and export more than one type of backup to the same location. You need to change the backup type before you rerun the backup operation. We recommend that you change the filename for easier identification of the backup type and to avoid overwriting the existing backup file. Scheduled Backups You cannot schedule a backup operation. You can, however, create a backup operation in advance and leave the admin state disabled until you are ready to run the backup. Cisco UCS Manager does not run the backup operation, save, or export the configuration file until you set the admin state of the backup operation to enabled. Incremental Backups You cannot perform incremental backups of the Cisco UCS Manager system configuration. Backwards Compatibility Starting with Release 1.1(1) of the Cisco UCS Manager, full state backups are encrypted so that passwords and other sensitive information are not exported as clear text. As a result, full state backups made from Release 1.1(1) or later cannot be restored to a Cisco UCS domain running an earlier software release. Cisco UCS Manager GUI Configuration Guide, Release 2.0 620 OL-25712-04 Import Configuration Import Configuration You can import any configuration file that was exported from Cisco UCS Manager. The file does not need to have been exported from the same Cisco UCS Manager. The import function is available for all configuration, system configuration, and logical configuration files. You can perform an import while the system is up and running. An import operation modifies information on the management plane only. Some modifications caused by an import operation, such as a change to a vNIC assigned to a server, can cause a server reboot or other operations that disrupt traffic. You cannot schedule an import operation. You can, however, create an import operation in advance and leave the admin state disabled until you are ready to run the import. Cisco UCS Manager will not run the import operation on the configuration file until you set the admin state to enabled. You can maintain only one import operation for each location where you saved a configuration backup file. Import Methods You can use one of the following methods to import and update a system configuration through Cisco UCS Manager: • Merge—The information in the imported configuration file is compared with the existing configuration information. If there are conflicts, the import operation overwrites the information on the Cisco UCS domain with the information in the import configuration file. • Replace—The current configuration information is replaced with the information in the imported configuration file one object at a time. System Restore You can use the restore function for disaster recovery. You can restore a system configuration from any full state backup file that was exported from Cisco UCS Manager. The file does not need to have been exported from the Cisco UCS Manager on the system that you are restoring. When restoring using a backup file that was exported from a different system, we strongly recommend that you use a system with the same or similar system configuration and hardware, including fabric interconnects, servers, adapters, and I/O module or FEX connectivity. Mismatched hardware and/or system configuration can lead to the restored system not fully functioning. If there is a mismatch between the I/O module links or servers on the two systems, acknowledge the chassis and/or servers after the restore operation. The restore function is only available for a full state backup file. You cannot import a full state backup file. You perform a restore through the initial system setup. Required User Role for Backup and Import Operations You must have a user account that includes the admin role to create and run backup and import operations. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 621 Backup Operations Backup Operations Creating a Backup Operation Before You Begin Obtain the backup server IP address and authentication credentials. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Click the All node. In the Work pane, click the General tab. Step 4 Step 5 Step 6 In the Actions area, click Backup. In the Backup Configuration dialog box, click Create Backup Operation. In the Create Backup Operation dialog box, complete the following fields: Name Description Admin State field This can be one of the following: • Enabled—Cisco UCS Manager runs the backup operation as soon as you click OK. • Disabled—Cisco UCS Manager does not run the backup operation when you click OK. If you select this option, all fields in the dialog box remain visible. However, you must manually run the backup from the Backup Configuration dialog box. Cisco UCS Manager GUI Configuration Guide, Release 2.0 622 OL-25712-04 Backup Operations Name Description Type field The information saved in the backup configuration file. This can be one of the following: • Full state—A binary file that includes a snapshot of the entire system. You can use the file generated from this backup to restore the system during disaster recovery. This file can restore or rebuild the configuration on the original fabric interconnect, or recreate the configuration on a different fabric interconnect. You cannot use this file for an import. • All configuration—An XML file that includes all system and logical configuration settings. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore. This file does not include passwords for locally authenticated users. • System configuration—An XML file that includes all system configuration settings such as usernames, roles, and locales. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore. • Logical configuration—An XML file that includes all logical configuration settings such as service profiles, VLANs, VSANs, pools, and policies. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore. Preserve Identities check box If this check box is checked, the backup file preserves all identities derived from pools, including the MAC addresses, WWPN, WWNN, and UUIDs. Location of the Backup File field Where the backup file should be saved. This can be one of the following: • Remote File System—The backup XML file is saved to a remote server. Cisco UCS Manager GUI displays the fields described below that allow you to specify the protocol, host, filename, username, and password for the remote system. • Local File System—The backup XML file is saved locally. Cisco UCS Manager GUI displays the Filename field with an associated Browse button that let you specify the name and location for the backup file. Note Once you click OK, the location cannot be changed. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 623 Backup Operations Name Description Protocol field The protocol to use when communicating with the remote server. This can be one of the following: • FTP • TFTP • SCP • SFTP Hostname field The hostname or IP address of the location where the backup file is stored. This can be a server, storage array, local drive, or any read/write media that the fabric interconnect can access through the network. Note If you use a hostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager. Remote File field The full path to the backup configuration file. This field can contain the filename as well as the path. If you omit the filename, the backup procedure assigns a name to the file. User field The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP. Password field The password for the remote server username. This field does not apply if the protocol is TFTP. Cisco UCS Manager does not store this password. Therefore, you do not need to enter this password unless you intend to enable and run the backup operation immediately. Step 7 Step 8 Click OK. If Cisco UCS Manager displays a confirmation dialog box, click OK. If you set the Admin State field to enabled, Cisco UCS Manager takes a snapshot of the configuration type that you selected and exports the file to the network location. The backup operation displays in the Backup Operations table in the Backup Configuration dialog box. Step 9 (Optional) To view the progress of the backup operation, do the following: a) If the operation does not display in the Properties area, click the operation in the Backup Operations table. b) In the Properties area, click the down arrows on the FSM Details bar. The FSM Details area expands and displays the operation status. Step 10 Click OK to close the Backup Configuration dialog box. The backup operation continues to run until it is completed. To view the progress, re-open the Backup Configuration dialog box. Cisco UCS Manager GUI Configuration Guide, Release 2.0 624 OL-25712-04 Backup Operations Running a Backup Operation Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Click the All node. In the Work pane, click the General tab. Step 4 Step 5 In the Actions area, click Backup. In the Backup Operations table of the Backup Configuration dialog box, click the backup operation that you want to run. The details of the selected backup operation display in the Properties area. Step 6 In the Properties area, complete the following fields: a) In the Admin State field, click the Enabled radio button. b) For all protocols except TFTP, enter the password for the username in the Password field. c) (Optional) Change the content of the other available fields. Step 7 Click Apply. Cisco UCS Manager takes a snapshot of the configuration type that you selected and exports the file to the network location. The backup operation displays in the Backup Operations table in the Backup Configuration dialog box. Step 8 (Optional) To view the progress of the backup operation, click the down arrows on the FSM Details bar. The FSM Details area expands and displays the operation status. Step 9 Click OK to close the Backup Configuration dialog box. The backup operation continues to run until it is completed. To view the progress, re-open the Backup Configuration dialog box. Modifying a Backup Operation You can modify a backup operation to save a file of another backup type to that location or to change the filename and avoid overwriting previous backup files. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Click the All node. In the Work pane, click the General tab. Step 4 Step 5 In the Actions area, click Backup. In the Backup Operations area of the Backup Configuration dialog box, click the backup operation that you want to modify. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 625 Import Operations The details of the selected backup operation display in the Properties area. If the backup operation is in a disabled state, the fields are dimmed. Step 6 Step 7 In the Admin State field, click the enabled radio button. Modify the appropriate fields. You do not have to enter the password unless you want to run the backup operation immediately. Step 8 (Optional) If you do not want to run the backup operation immediately, click the disabled radio button in the Admin State field. Click OK. Step 9 Deleting One or More Backup Operations Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Click the All node. In the Work pane, click the General tab. Step 4 Step 5 In the Actions area, click Backup. In the Backup Operations table of the Backup Configuration dialog box, click the backup operations that you want to delete. Tip You cannot click a backup operation in the table if the admin state of the operation is set to Enabled. Step 6 Step 7 Step 8 Click the Delete icon in the icon bar of the Backup Operations table. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. In the Backup Configuration dialog box, click one of the following: Option Description Apply Deletes the selected backup operations without closing the dialog box. OK Deletes the selected backup operations and closes the dialog box. Import Operations Creating an Import Operation You cannot import a Full State configuration file. You can import any of the following configuration files: • All configuration • System configuration Cisco UCS Manager GUI Configuration Guide, Release 2.0 626 OL-25712-04 Import Operations • Logical configuration Before You Begin Collect the following information that you will need to import a configuration file: • Backup server IP address and authentication credentials • Fully qualified name of a backup file Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Click the All node. In the Work pane, click the General tab. Step 4 Step 5 Step 6 In the Actions area, click Import Configuration. In the Import Configuration dialog box, click Create Import Operation. In the Create Import Operation dialog box, complete the following fields: Name Description Admin State field This can be one of the following: • Enabled—Cisco UCS runs the import operation as soon as you click OK. • Disabled—Cisco UCS does not run the import operation when you click OK. If you select this option, all fields in the dialog box remain visible. However, you must manually run the import from the Import Configuration dialog box. Action field This can be one of the following: • Merge—The configuration information is merged with the existing information. If there are conflicts, the system replaces the information on the current system with the information in the import configuration file. • Replace—The system takes each object in the import configuration file and overwrites the corresponding object in the current configuration. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 627 Import Operations Name Description Location of the Import File field Where the backup file that you want to import is located. This can be one of the following: • Remote File System—The backup XML file is stored on a remote server. Cisco UCS Manager GUI displays the fields described below that allow you to specify the protocol, host, filename, username, and password for the remote system. • Local File System—The backup XML file is stored locally. Cisco UCS Manager GUI displays the Filename field with an associated Browse button that let you specify the name and location for the backup file to be imported. Protocol field The protocol to use when communicating with the remote server. This can be one of the following: • FTP • TFTP • SCP • SFTP Hostname field The hostname or IP address from which the configuration file should be imported. Note If you use a hostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager. Remote File field The name of the XML configuration file. User field The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP. Password field The password for the remote server username. This field does not apply if the protocol is TFTP. Cisco UCS Manager does not store this password. Therefore, you do not need to enter this password unless you intend to enable and run the import operation immediately. Step 7 Step 8 Click OK. In the confirmation dialog box, click OK. If you set the Admin State to enabled, Cisco UCS Manager imports the configuration file from the network location. Depending upon which action you selected, the information in the file is either merged with the existing configuration or replaces the existing configuration. The import operation displays in the Import Operations table of the Import Configuration dialog box. Step 9 (Optional) To view the progress of the import operation, do the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 628 OL-25712-04 Import Operations a) If the operation does not automatically display in the Properties area, click the operation in the Import Operations table. b) In the Properties area, click the down arrows on the FSM Details bar. The FSM Details area expands and displays the operation status. Step 10 Click OK to close the Import Configuration dialog box. The import operation continues to run until it is completed. To view the progress, re-open the Import Configuration dialog box. Running an Import Operation You cannot import a Full State configuration file. You can import any of the following configuration files: • All configuration • System configuration • Logical configuration Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Click the All node. In the Work pane, click the General tab. Step 4 Step 5 In the Actions area, click Import Configuration. In the Import Operations table of the Import Configuration dialog box, click the operation that you want to run. The details of the selected import operation display in the Properties area. Step 6 In the Properties area, complete the following fields: a) In the Admin State field, click the Enabled radio button. b) For all protocols except TFTP, enter the password for the username In the Password field. c) (Optional) Change the content of the other available fields. Step 7 Click Apply. Cisco UCS Manager imports the configuration file from the network location. Depending upon which action you selected, the information in the file is either merged with the existing configuration or replaces the existing configuration. The import operation displays in the Import Operations table of the Import Configuration dialog box. Step 8 (Optional) To view the progress of the import operation, click the down arrows on the FSM Details bar. The FSM Details area expands and displays the operation status. Step 9 Click OK to close the Import Configuration dialog box. The import operation continues to run until it is completed. To view the progress, re-open the Import Configuration dialog box. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 629 Import Operations Modifying an Import Operation Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Click the All node. In the Work pane, click the General tab. Step 4 Step 5 In the Actions area, click Import Configuration. In the Import Operations area of the Import Configuration dialog box, click the import operation that you want to modify. The details of the selected import operation display in the Properties area. If the import operation is in a disabled state, the fields are dimmed. Step 6 Step 7 In the Admin State field, click the enabled radio button. Modify the appropriate fields. You do not have to enter the password unless you want to run the import operation immediately. Step 8 (Optional) If you do not want to run the import operation immediately, click the disabled radio button in the Admin State field. Click OK. Step 9 Deleting One or More Import Operations Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Click the All node. In the Work pane, click the General tab. Step 4 Step 5 In the Actions area, click Import Configuration. In the Import Operations table of the Backup Configuration dialog box, click the import operations that you want to delete. Tip You cannot click an import operation in the table if the admin state of the operation is set to Enabled. Step 6 Step 7 Step 8 Click the Delete icon in the icon bar of the Import Operations table. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. In the Import Configuration dialog box, click one of the following: Option Description Apply Deletes the selected import operations without closing the dialog box. Cisco UCS Manager GUI Configuration Guide, Release 2.0 630 OL-25712-04 Restoring the Configuration for a Fabric Interconnect Option Description OK Deletes the selected import operations and closes the dialog box. Restoring the Configuration for a Fabric Interconnect Before You Begin Collect the following information that you will need to restore the system configuration: • Fabric interconnect management port IP address and subnet mask • Default gateway IP address • Backup server IP address and authentication credentials • Fully qualified name of a Full State backup file Note You must have access to a Full State configuration file to perform a system restore. You cannot perform a system restore with any other type of configuration or backup file. Procedure Step 1 Step 2 Connect to the console port. If the fabric interconnect is off, power on the fabric interconnect. You will see the power on self-test message as the fabric interconnect boots. Step 3 Step 4 At the installation method prompt, enter gui. If the system cannot access a DHCP server, you may be prompted to enter the following information: • IP address for the management port on the fabric interconnect • Subnet mask for the management port on the fabric interconnect • IP address for the default gateway assigned to the fabric interconnect Step 5 Step 6 Step 7 Copy the web link from the prompt into a web browser and go to the Cisco UCS Manager GUI launch page. On the launch page, select Express Setup. On the Express Setup page, select Restore From Backup and click Submit. Step 8 In the Protocol area of the Cisco UCS Manager Initial Setup page, select the protocol you want to use to upload the full state backup file: • SCP • TFTP Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 631 Restoring the Configuration for a Fabric Interconnect • FTP • SFTP Step 9 In the Server Information area, complete the following fields: Name Description Server IP The IP address of the computer where the full state backup file is located. This can be a server, storage array, local drive, or any read/write media that the fabric interconnect can access through the network. Backup File Path The file path where the full state backup file is located, including the folder names and filename. User ID The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP. Password The password for the remote server username. This field does not apply if the protocol is TFTP. Step 10 Click Submit. You can return to the console to watch the progress of the system restore. The fabric interconnect logs in to the backup server, retrieves a copy of the specified full-state backup file, and restores the system configuration. For a cluster configuration, you do not need to restore the secondary fabric interconnect. As soon as the secondary fabric interconnect reboots, Cisco UCS Manager sychronizes the configuration with the primary fabric interconnect. Cisco UCS Manager GUI Configuration Guide, Release 2.0 632 OL-25712-04 CHAPTER 41 Recovering a Lost Password This chapter includes the following sections: • Recovering a Lost Password, page 633 Recovering a Lost Password Password Recovery for the Admin Account The admin account is the system administrator or superuser account. If an administrator loses the password to this account, you can have a serious security issue. As a result, the procedure to recover the password for the admin account requires you to power cycle all fabric interconnects in a Cisco UCS domain. When you recover the password for the admin account, you actually change the password for that account. You cannot retrieve the original password for that account. You can reset the password for all other local accounts through Cisco UCS Manager. However, you must log in to Cisco UCS Manager with an account that includes aaa or admin privileges. Caution This procedure requires you to power down all fabric interconnects in a Cisco UCS domain. As a result, all data transmission in the Cisco UCS domain is stopped until you restart the fabric interconnects. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 633 Recovering a Lost Password Determining the Leadership Role of a Fabric Interconnect Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 In the Equipment tab, expand Equipment > Fabric Interconnects. Click the fabric interconnect for which you want to identify the role. In the Work pane, click the General tab. Step 5 Step 6 In the General tab, click the down arrows on the High Availability Details bar to expand that area. View the Leadership field to determine whether the fabric interconnect is the primary or subordinate. Verifying the Firmware Versions on a Fabric Interconnect You can use the following procedure to verify the firmware versions on all fabric interconnects in a Cisco UCS domain. You can verify the firmware for a single fabric interconnect through the Installed Firmware tab for that fabric interconnect. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 In the Equipment tab, click the Equipment node. In the Work pane, click the Firmware Management tab. Step 4 In the Installed Firmware tab, verify that the following firmware versions for each fabric interconnect match the version to which you updated the firmware: • Kernel version • System version Recovering the Admin Account Password in a Standalone Configuration This procedure will help you to recover the password that you set for the admin account when you performed an initial system setup on the fabric interconnect. The admin account is the system administrator or superuser account. Before You Begin 1 Physically connect the console port on the fabric interconnect to a computer terminal or console server 2 Determine the running versions of the following firmware: • The firmware kernel version on the fabric interconnect Cisco UCS Manager GUI Configuration Guide, Release 2.0 634 OL-25712-04 Recovering a Lost Password • The firmware system version Tip To find this information, you can log in with any user account on the Cisco UCS domain. Procedure Step 1 Step 2 Connect to the console port. Power cycle the fabric interconnect: a) Turn off the power to the fabric interconnect. b) Turn on the power to the fabric interconnect. Step 3 In the console, press one of the following key combinations as it boots to get the loader prompt: • Ctrl+l • Ctrl+Shift+r You may need to press the selected key combination multiple times before your screen displays the loader prompt. Step 4 Boot the kernel firmware version on the fabric interconnect. loader > boot /installables/switch/ kernel_firmware_version Example: loader > Step 5 boot /installables/switch/ucs-6100-k9-kickstart.4.1.3.N2.1.0.11.gbin Enter config terminal mode. Fabric(boot)# config terminal Step 6 Reset the admin password. Fabric(boot)(config)# admin-password password Choose a strong password that includes at least one capital letter and one number. The password cannot be blank. The new password displays in clear text mode. Step 7 Step 8 Exit config terminal mode and return to the boot prompt. Boot the system firmware version on the fabric interconnect. Fabric(boot)# load /installables/switch/ system_firmware_version Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 635 Recovering a Lost Password Example: Fabric(boot)# Step 9 load /installables/switch/ucs-6100-k9-system.4.1.3.N2.1.0.211.bin After the system image loads, log in to Cisco UCS Manager. Recovering the Admin Account Password in a Cluster Configuration This procedure will help you to recover the password that you set for the admin account when you performed an initial system setup on the fabric interconnects. The admin account is the system administrator or superuser account. Before You Begin 1 Physically connect a console port on one of the fabric interconnects to a computer terminal or console server 2 Obtain the following information: • The firmware kernel version on the fabric interconnect • The firmware system version • Which fabric interconnect has the primary leadership role and which is the subordinate Tip To find this information, you can log in with any user account on the Cisco UCS domain. Procedure Step 1 Step 2 Connect to the console port. For the subordinate fabric interconnect: a) Turn off the power to the fabric interconnect. b) Turn on the power to the fabric interconnect. c) In the console, press one of the following key combinations as it boots to get the loader prompt: • Ctrl+l • Ctrl+Shift+r You may need to press the selected key combination multiple times before your screen displays the loader prompt. Step 3 Power cycle the primary fabric interconnect: a) Turn off the power to the fabric interconnect. b) Turn on the power to the fabric interconnect. Step 4 In the console, press one of the following key combinations as it boots to get the loader prompt: Cisco UCS Manager GUI Configuration Guide, Release 2.0 636 OL-25712-04 Recovering a Lost Password • Ctrl+l • Ctrl+Shift+r You may need to press the selected key combination multiple times before your screen displays the loader prompt. Step 5 Boot the kernel firmware version on the primary fabric interconnect. loader > boot /installables/switch/ kernel_firmware_version Example: loader > boot /installables/switch/ucs-6100-k9-kickstart.4.1.3.N2.1.0.11.gbin Step 6 Enter config terminal mode. Fabric(boot)# config terminal Step 7 Reset the admin password. Fabric(boot)(config)# admin-password password Choose a strong password that includes at least one capital letter and one number. The password cannot be blank. The new password displays in clear text mode. Step 8 Step 9 Exit config terminal mode and return to the boot prompt. Boot the system firmware version on the primary fabric interconnect. Fabric(boot)# load /installables/switch/ system_firmware_version Example: Fabric(boot)# load /installables/switch/ucs-6100-k9-system.4.1.3.N2.1.0.211.bin Step 10 After the system image loads, log in to Cisco UCS Manager. Step 11 In the console for the subordinate fabric interconnect, do the following to bring it up: a) Boot the kernel firmware version on the subordinate fabric interconnect. loader > boot /installables/switch/ kernel_firmware_version b) Boot the system firmware version on the subordinate fabric interconnect. Fabric(boot)# load /installables/switch/ system_firmware_version Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 637 Recovering a Lost Password Cisco UCS Manager GUI Configuration Guide, Release 2.0 638 OL-25712-04 PART VII System Monitoring • Monitoring Traffic, page 641 • Monitoring Hardware, page 647 • Configuring Statistics-Related Policies, page 663 • Configuring Call Home, page 675 • Managing the System Event Log, page 695 • Configuring Settings for Faults, Events, and Logs, page 701 CHAPTER 42 Monitoring Traffic This chapter includes the following sections: • Traffic Monitoring, page 641 • Guidelines and Recommendations for Traffic Monitoring, page 642 • Creating an Ethernet Traffic Monitoring Session, page 643 • Creating a Fibre Channel Traffic Monitoring Session, page 644 • Adding Traffic Sources to a Monitoring Session, page 645 • Activating a Traffic Monitoring Session, page 646 • Deleting a Traffic Monitoring Session, page 646 Traffic Monitoring Traffic monitoring copies traffic from one or more sources and sends the copied traffic to a dedicated destination port for analysis by a network analyzer. This feature is also known as Switched Port Analyzer (SPAN). Type of Session When you create a traffic monitoring session, you can choose either an Ethernet or Fibre Channel destination port to receive the traffic. The type of destination port determines the type of session, which in turn determines the types of available traffic sources. For an Ethernet traffic monitoring session, the destination port must be an unconfigured physical port. For a Fibre Channel traffic monitoring session, the destination port must be a Fibre Channel uplink port. Traffic Sources An Ethernet traffic monitoring session can monitor any of the following traffic sources: • Uplink Ethernet port • Ethernet port channel • VLAN • Service profile vNIC Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 641 Guidelines and Recommendations for Traffic Monitoring • Service profile vHBA • FCoE port • Port channels • Server port A Fibre Channel traffic monitoring session can monitor any of the following traffic sources: • Uplink Fibre Channel port • SAN port channel • VSAN • Service profile vHBA • Fibre Channel storage port Guidelines and Recommendations for Traffic Monitoring When configuring or activating traffic monitoring, consider the following guidelines: • You can create and store up to 16 traffic monitoring sessions, but only two can be active at the same time. • A traffic monitoring session is disabled by default when created. To begin monitoring traffic, you must activate the session. • To monitor traffic from a server, add all vNICs from the service profile corresponding to the server. • You can monitor Fibre Channel traffic using either a Fibre Channel traffic analyzer or an Ethernet traffic analyzer. When Fibre Channel traffic is monitored using an Ethernet traffic monitoring session, with an Ethernet destination port, the destination traffic will be FCoE. • Because a traffic monitoring destination is a single physical port, a traffic monitoring session can monitor only a single fabric. To monitor uninterrupted vNIC traffic across a fabric failover, you must create two sessions—one per fabric—and connect two analyzers. Add the vNIC as the traffic source for both sessions. • All traffic sources must be located within the same switch as the destination port. • A port configured as a destination port cannot also be configured as a source port. • A member port of a port channel cannot be configured individually as a source. If the port channel is configured as a source, all member ports are source ports. • A vHBA can be a source for either an Ethernet or Fibre Channel monitoring session, but it cannot be a source for both simultaneously. • A server port can be a source only if it is a non-virtualized rack server adapter-facing port. • A Fibre Channel port on a Cisco UCS 6248 fabric interconnect cannot be configured as a source port. • If you change the port profile of a virtual machine, any associated vNICs being used as source ports are removed from monitoring, and you must reconfigure the monitoring session. Cisco UCS Manager GUI Configuration Guide, Release 2.0 642 OL-25712-04 Creating an Ethernet Traffic Monitoring Session • If a traffic monitoring session was configured on a dynamic vNIC under a release earlier than Cisco UCS Manager Release 2.0, you must reconfigure the traffic monitoring session after upgrading. Note Traffic monitoring can impose a significant load on your system resources. To minimize the load, select sources that carry as little unwanted traffic as possible and disable traffic monitoring when it is not needed. Creating an Ethernet Traffic Monitoring Session Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 On the LAN tab, expand LAN > Traffic Monitoring Sessions > Fabric_Interconnect_Name. Right-click Fabric_Interconnect_Name and choose Create Traffic Monitoring Session. In the Create Traffic Monitoring Session dialog box, complete the following fields: Name Description Name field The name of the traffic monitoring session. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Admin State field Whether traffic will be monitored for the physical port selected in the Destination field. This can be one of the following: • Enabled—Cisco UCS begins monitoring the port activity as soon as some source components are added to the session. • Disabled—Cisco UCS does not monitor the port activity. Destination drop-down list Select the physical port whose communication traffic you want to monitor from the navigation tree. Admin Speed drop-down list The data transfer rate of the port channel to be monitored. This can be one of the following: • 1 Gbps • 10 Gbps • 20 Gbps • 40 Gbps Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 643 Creating a Fibre Channel Traffic Monitoring Session Step 5 Click OK. What to Do Next • Add traffic sources to the traffic monitoring session. • Activate the traffic monitoring session. Creating a Fibre Channel Traffic Monitoring Session Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 On the LAN tab, expand SAN > Traffic Monitoring Sessions > Fabric_Interconnect_Name. Right-click Fabric_Interconnect_Name and choose Create Traffic Monitoring Session. In the Create Traffic Monitoring Session dialog box, complete the following fields: Name Description Name field The name of the traffic monitoring session. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Admin State field Whether traffic will be monitored for the physical port selected in the Destination field. This can be one of the following: • Enabled—Cisco UCS begins monitoring the port activity as soon as some source components are added to the session. • Disabled—Cisco UCS does not monitor the port activity. Destination drop-down list Select the physical port whose communication traffic you want to monitor from the navigation tree. Admin Speed drop-down list The data transfer rate of the port channel to be monitored. This can be one of the following: • 1 Gbps • 2 Gbps • 4 Gbps • 8 Gbps • Auto—Cisco UCS determines the data transfer rate. Cisco UCS Manager GUI Configuration Guide, Release 2.0 644 OL-25712-04 Adding Traffic Sources to a Monitoring Session Step 5 Click OK. What to Do Next • Add traffic sources to the traffic monitoring session. • Activate the traffic monitoring session. Adding Traffic Sources to a Monitoring Session You can choose multiple sources from more than one source type to be monitored by a traffic monitoring session. The available sources depend on the components configured in the Cisco UCS domain. Note This procedure describes how to add sources for Ethernet traffic monitoring sessions. To add sources for a Fibre Channel monitoring session, select the SAN tab instead of the LAN tab in Step 2. Before You Begin A traffic monitoring session must be created. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 On the LAN tab, expand LAN > Traffic Monitoring Sessions > Fabric_Interconnect_Name. Expand Fabric_Interconnect_Name and click the monitor session that you want to configure. In the Work pane, click the General tab. Step 5 In the Sources area, expand the section for the type of traffic source that you want to add. Step 6 To see the components that are available for monitoring, click the + button in the right-hand edge of the table to open the Create Monitoring Session Source dialog box. Step 7 Select a source component and click OK. You can repeat the preceding three steps as needed to add multiple sources from multiple source types. Step 8 Click Save Changes. What to Do Next Activate the traffic monitoring session. If the session is already activated, traffic will be forwarded to the monitoring destination when you add a source. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 645 Activating a Traffic Monitoring Session Activating a Traffic Monitoring Session Note This procedure describes how to activate an Ethernet traffic monitoring session. To activate a Fibre Channel monitoring session, select the SAN tab instead of the LAN tab in Step 2. Before You Begin A traffic monitoring session must be created. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 On the LAN tab, expand LAN > Traffic Monitoring Sessions > Fabric_Interconnect_Name. Expand Fabric_Interconnect_Name and click the monitor session that you want to activate. In the Work pane, click the General tab. Step 5 Step 6 In the Properties area, click the enabled radio button for Admin State. Click Save Changes. If a traffic monitoring source is configured, traffic begins to flow to the traffic monitoring destination port. Deleting a Traffic Monitoring Session Note This procedure describes how to delete an Ethernet traffic monitoring session. To delete a Fibre Channel monitoring session, select the SAN tab instead of the LAN tab in Step 2. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 On the LAN tab, expand LAN > Traffic Monitoring Sessions > Fabric_Interconnect_Name. Expand Fabric_Interconnect_Name and click the monitor session that you want to delete. In the Work pane, click the General tab. Step 5 Step 6 In the Actions area, click the Delete icon. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 646 OL-25712-04 CHAPTER 43 Monitoring Hardware This chapter includes the following sections: • Monitoring a Fabric Interconnect, page 647 • Monitoring a Chassis, page 648 • Monitoring a Blade Server, page 650 • Monitoring a Rack-Mount Server, page 652 • Monitoring an I/O Module, page 654 • Monitoring Management Interfaces, page 655 • Server Disk Drive Monitoring, page 658 Monitoring a Fabric Interconnect Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Fabric Interconnects. Click the node for the fabric interconnect that you want to monitor. In the Work pane, click one of the following tabs to view the status of the fabric interconnect: Option Description General tab Provides an overview of the status of the fabric interconnect, including a summary of any faults, a summary of the fabric interconnect properties, and a physical display of the fabric interconnect and its components. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 647 Monitoring a Chassis Option Description Physical Ports tab Displays the status of all ports on the fabric interconnect. This tab includes the following subtabs: • Uplink Ports tab • Server Ports tab • Fibre Channel Ports tab • Unconfigured Ports tab Fans tab Displays the status of all fan modules in the fabric interconnect. PSUs tab Displays the status of all power supply units in the fabric interconnect. Physical Display tab Provides a graphical view of the fabric interconnect and all ports and other components. If a component has a fault, the fault icon is displayed next to that component. Faults tab Provides details of faults generated by the fabric interconnect. Events tab Provides details of events generated by the fabric interconnect. Statistics tab Provides statistics about the fabric interconnect and its components. You can view these statistics in tabular or chart format. Monitoring a Chassis Tip To monitor an individual component in a chassis, expand the node for that component. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis. Click the chassis that you want to monitor. Click one of the following tabs to view the status of the chassis: Option Description General tab Provides an overview of the status of the chassis, including a summary of any faults, a summary of the chassis properties, and a physical display of the chassis and its components. Cisco UCS Manager GUI Configuration Guide, Release 2.0 648 OL-25712-04 Monitoring a Chassis Option Description Servers tab Displays the status and selected properties of all servers in the chassis. Service Profiles tab Displays the status of the service profiles associated with servers in the chassis. IO Modules tab Displays the status and selected properties of all IO modules in the chassis. Fans tab Displays the status of all fan modules in the chassis. PSUs Displays the status of all power supply units in the chassis. Hybrid Display tab Displays detailed information about the connections between the chassis and the fabric interconnects. The display has an icon for the following: • Each fabric interconnect in the system • The I/O module (IOM) in the selected component, which is shown as an independent unit to make the connection paths easier to see • The selected chassis showing the servers and PSUs Slots tab Displays the status of all slots in the chassis. Installed Firmware tab Displays the current firmware versions on the IO modules and servers in the chassis. You can also use this tab to update and activate the firmware on those components. SEL Logs tab Displays and provides access to the system event logs for the servers in the chassis. Faults tab Provides details of faults generated by the chassis. Events tab Provides details of events generated by the chassis. FSM tab Provides details about and the status of FSM tasks related to the chassis. You can use this information to diagnose errors with those tasks. Statistics tab Provides statistics about the chassis and its components. You can view these statistics in tabular or chart format. Temperatures tab Provides temperature statistics for the components of the chassis. You can view these statistics in tabular or chart format. Power tab Provides power statistics for the components of the chassis. You can view these statistics in tabular or chart format. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 649 Monitoring a Blade Server Monitoring a Blade Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Click the server that you want to monitor. In the Work pane, click one of the following tabs to view the status of the server: Option Description General tab Provides an overview of the status of the server, including a summary of any faults, a summary of the server properties, and a physical display of the server and its components. Cisco UCS Manager GUI Configuration Guide, Release 2.0 650 OL-25712-04 Monitoring a Blade Server Option Description Inventory tab Provides details about the properties and status of the components of the server on the following subtabs: • Motherboard—Information about the motherboard and information about the server BIOS settings. You can also recover corrupt BIOS firmware from this subtab. • CIMC—Information about the CIMC and its firmware, and provides access to the SEL for the server. You can also assign a static or pooled management IP address, and update and activate the CIMC firmware from this subtab. • CPUs—Information about each CPU in the server. • Memory—Information about each memory slot in the server and the DIMM in that slot. • Adapters—Information about each adapter installed in the server. • HBAs—Properties of each HBA and the configuration of that HBA in the service profile associated with the server. • NICs—Properties of each NIC and the configuration of that NIC in the service profile associated with the server. You can expand each row to view information about the associated VIFs and vNICs. • iSCSI vNICs—Properties of each iSCSI vNIC and the configuration of that vNIC in the service profile associated with the server. • Storage—Properties of the storage controller, the local disk configuration policy in the service profile associated with the server, and for each hard disk in the server. Tip If the server contains one or more SATA devices, such as a hard disk drive or solid state drive, Cisco UCS Manager GUI displays the vendor name for the SATA device in the Vendor field. However, Cisco UCS Manager CLI displays ATA in the Vendor field and includes the vendor information, such as the vendor name, in a Vendor Description field. This second field does not exist in Cisco UCS Manager GUI. Virtual Machines tab Displays details about any virtual machines hosted on the server. Installed Firmware Displays the firmware versions on the CIMC, adapters, and other server components. tab You can also use this tab to update and activate the firmware on those components. SEL Logs tab Displays the system event log for the server. VIF Paths tab Displays the VIF paths for the adapters on the server. Faults tab Displays an overview of the faults generated by the server. You can click any fault to view additional information. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 651 Monitoring a Rack-Mount Server Option Description Events tab Displays an overview of the events generated by the server. You can click any event to view additional information. FSM tab Provides details about the current FSM task running on the server, including the status of that task. You can use this information to diagnose errors with those tasks. Statistics tab Displays statistics about the server and its components. You can view these statistics in tabular or chart format. Temperatures tab Displays temperature statistics for the components of the server. You can view these statistics in tabular or chart format. Power tab Displays power statistics for the components of the server. You can view these statistics in tabular or chart format. Step 5 In the Navigation pane, expand Server_ID > Adapters > Adapter_ID . Step 6 In the Work pane, right-click one or more of the following components of the adapter to open the navigator and view the status of the component: • Adapters • DCE interfaces • HBAs • NICs Tip Expand the nodes in the table to view the child nodes. For example, if you expand a NIC node, you can view each VIF created on that NIC. Monitoring a Rack-Mount Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Rack Mounts > Servers. Click the server that you want to monitor. In the Work pane, click one of the following tabs to view the status of the server: Option Description General tab Provides an overview of the status of the server, including a summary of any faults, a summary of the server properties, and a physical display of the server and its components. Cisco UCS Manager GUI Configuration Guide, Release 2.0 652 OL-25712-04 Monitoring a Rack-Mount Server Option Description Inventory tab Provides details about the properties and status of the components of the server on the following subtabs: • Motherboard—Information about the motherboard and information about the server BIOS settings. You can also recover corrupt BIOS firmware from this subtab. • CIMC—Information about the CIMC and its firmware, and provides access to the SEL for the server. You can also assign a static or pooled management IP address, and update and activate the CIMC firmware from this subtab. • CPU—Information about each CPU in the server. • Memory—Information about each memory slot in the server and the DIMM in that slot. • Adapters—Information about each adapter installed in the server. • HBAs—Properties of each HBA and the configuration of that HBA in the service profile associated with the server. • NICs—Properties of each NIC and the configuration of that NIC in the service profile associated with the server. You can expand each row to view information about the associated VIFs and vNICs. • iSCSI vNICs—Properties of each iSCSI vNIC and the configuration of that vNIC in the service profile associated with the server. • Storage—Properties of the storage controller, the local disk configuration policy in the service profile associated with the server, and for each hard disk in the server. Tip If the server contains one or more SATA devices, such as a hard disk drive or solid state drive, Cisco UCS Manager GUI displays the vendor name for the SATA device in the Vendor field. However, Cisco UCS Manager CLI displays ATA in the Vendor field and includes the vendor information, such as the vendor name, in a Vendor Description field. This second field does not exist in Cisco UCS Manager GUI. Virtual Machines tab Displays details about any virtual machines hosted on the server. Installed Firmware Displays the firmware versions on the CIMC, adapters, and other server components. tab You can also use this tab to update and activate the firmware on those components. SEL Logs tab Displays the system event log for the server. VIF Paths tab Displays the VIF paths for the adapters on the server. Faults tab Displays an overview of the faults generated by the server. You can click any fault to view additional information. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 653 Monitoring an I/O Module Option Description Events tab Displays an overview of the events generated by the server. You can click any event to view additional information. FSM tab Provides details about the current FSM task running on the server, including the status of that task. You can use this information to diagnose errors with those tasks. Statistics tab Displays statistics about the server and its components. You can view these statistics in tabular or chart format. Temperatures tab Displays temperature statistics for the components of the server. You can view these statistics in tabular or chart format. Power tab Displays power statistics for the components of the server. You can view these statistics in tabular or chart format. Step 5 In the Navigation pane, expand Server_ID > Adapters > Adapter_ID . Step 6 In the Work pane, right-click one or more of the following components of the adapter to open the navigator and view the status of the component: • Adapters • DCE interfaces • HBAs • NICs Tip Expand the nodes in the table to view the child nodes. For example, if you expand a NIC node, you can view each VIF created on that NIC. Monitoring an I/O Module Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > IO Modules. Click the I/O module that you want to monitor. Click one of the following tabs to view the status of the I/O module: Option Description General tab Provides an overview of the status of the I/O module, including a summary of any faults, a summary of the module properties, and a physical display of the module and its components. Cisco UCS Manager GUI Configuration Guide, Release 2.0 654 OL-25712-04 Monitoring Management Interfaces Option Description Fabric Ports tab Displays the status and selected properties of all fabric ports in the I/O module. Backplane Ports tab Displays the status and selected properties of all backplane ports in the I/O module. Faults tab Provides details of faults generated by the I/O module. Events tab Provides details of events generated by the I/O module. FSM tab Provides details about and the status of FSM tasks related to the I/O module. You can use this information to diagnose errors with those tasks. Statistics tab Provides statistics about the I/O module and its components. You can view these statistics in tabular or chart format. Monitoring Management Interfaces Management Interfaces Monitoring Policy This policy defines how the mgmt0 Ethernet interface on the fabric interconnect should be monitored. If Cisco UCS detects a management interface failure, a failure report is generated. If the configured number of failure reports is reached, the system assumes that the management interface is unavailable and generates a fault. By default, the management interfaces monitoring policy is disabled. If the affected management interface belongs to a fabric interconnect which is the managing instance, Cisco UCS confirms that the subordinate fabric interconnect's status is up, that there are no current failure reports logged against it, and then modifies the managing instance for the end-points. If the affected fabric interconnect is currently the primary inside of a high availability setup, a failover of the management plane is triggered. The data plane is not affected by this failover. You can set the following properties related to monitoring the management interface: • Type of mechanism used to monitor the management interface. • Interval at which the management interface's status is monitored. • Maximum number of monitoring attempts that can fail before the system assumes that the management is unavailable and generates a fault message. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 655 Monitoring Management Interfaces Important In the event of a management interface failure on a fabric interconnect, the managing instance may not change if one of the following occurs: • A path to the end-point through the subordinate fabric interconnect does not exist. • The management interface for the subordinate fabric interconnect has failed. • The path to the end-point through the subordinate fabric interconnect has failed. Configuring the Management Interfaces Monitoring Policy Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 In the Admin tab, expand All > Communication Management. Click Management Interfaces. In the Work pane, click the Management Interfaces Monitoring Policy tab. Step 5 Complete the following fields: Name Description Admin Status field Whether the monitoring policy is enabled or disabled for the management interfaces. Poll Interval field The number of seconds the system should wait between data recordings. Enter an integer between 90 and 300. Max Fail Report Count field The maximum number of monitoring attempts that can fail before the system assumes that the management interface is unavailable and generates a fault message. Enter an integer between 2 and 5. Cisco UCS Manager GUI Configuration Guide, Release 2.0 656 OL-25712-04 Monitoring Management Interfaces Name Description Monitoring Mechanism field The type of monitoring you want the system to use. This can be one of the following: • Mii Status—The system monitors the availability of the Media Independent Interface (MII). If you select this option, Cisco UCS Manager GUI displays the Media Independent Interface Monitoring area. • Ping Arp Targets—The system pings designated targets using the Address Resolution Protocol (ARP). If you select this option, Cisco UCS Manager GUI displays the ARP Target Monitoring area. • Ping Gateway—The system pings the default gateway address specified for this Cisco UCS domain on the Management Interfaces tab. If you select this option, Cisco UCS Manager GUI displays the Gateway Ping Monitoring area. Step 6 If you chose Mii Status for the monitoring mechanism, complete the following fields in the Media Independent Interface Monitoring area: Name Description Retry Interval field The number of seconds the system should wait before requesting another response from the MII if a previous attempt fails. Enter an integer between 3 and 10. Max Retry Count field The number of times the system polls the MII until the system assumes the interface is unavailable. Enter an integer between 1 and 3. Step 7 If you chose Ping Arp Targets for the monitoring mechanism, complete the following fields in the ARP Target Monitoring area: Name Description Target IP 1 field The first IP address the system pings. Target IP 2 field The second IP address the system pings. Target IP 3 field The third IP address the system pings. Number of ARP Requests field The number of ARP requests to send to the target IP addresses. Enter an integer between 1 and 5. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 657 Server Disk Drive Monitoring Name Description Max Deadline Timeout field The number of seconds to wait for responses from the ARP targets until the system assumes they are unavailable. Enter an integer between 5 and 15. Type 0.0.0.0 to remove the ARP target. Step 8 If you chose Ping Gateway for the monitoring mechanism, complete the following fields in the Gateway Ping Monitoring area: Name Description Number of Ping Requests field The number of times the system should ping the gateway. Enter an integer between 1 and 5. Max Deadline Timeout field The number of seconds to wait for a response from the gateway until the system assumes the address is unavailable. Enter an integer between 5 and 15. Step 9 Click Save Changes. Server Disk Drive Monitoring The disk drive monitoring for Cisco UCS provides Cisco UCS Manager with blade-resident disk drive status for supported blade servers in a Cisco UCS domain. Disk drive monitoring provides a unidirectional fault signal from the LSI firmware to Cisco UCS Manager to provide status information. The following server and firmware components gather, send, and aggregate information about the disk drive status in a server: • Physical presence sensor—Determines whether the disk drive is inserted in the server drive bay. • Physical fault sensor—Determines the operability status reported by the LSI storage controller firmware for the disk drive. • IPMI disk drive fault and presence sensors—Sends the sensor results to Cisco UCS Manager. • Disk drive fault LED control and associated IPMI sensors—Controls disk drive fault LED states (on/off) and relays the states to Cisco UCS Manager. Support for Disk Drive Monitoring Disk drive monitoring only supports certain blade servers and a specific LSI storage controller firmware level. Cisco UCS Manager GUI Configuration Guide, Release 2.0 658 OL-25712-04 Server Disk Drive Monitoring Supported Cisco UCS Servers Through Cisco UCS Manager, you can monitor disk drives for the following servers: • B-200 blade server • B-230 blade server • B-250 blade server • B-440 blade server Cisco UCS Manager cannot monitor disk drives in any other blade server or rack-mount server. Storage Controller Firmware Level The storage controller on a supported server must have LSI 1064E firmware. Cisco UCS Manager cannot monitor disk drives in servers with a different level of storage controller firmware. Prerequisites for Disk Drive Monitoring In addition to the supported servers and storage controller firmware version, you must ensure that the following prerequisites have been met for disk drive monitoring to provide useful status information: • The drive must be inserted in the server drive bay. • The server must be powered on. • The server must have completed discovery. • The results of the BIOS POST complete must be TRUE. Viewing the Status of a Disk Drive Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Click the server for which you want to view the status of the disk drive. In the Work pane, click the Inventory tab. Step 5 Step 6 Click the Storage subtab. Click the down arrows to expand the Disks bar and view the following fields in the States section for each disk drive: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 659 Server Disk Drive Monitoring Name Description Operability field The operational state of the disk drive. This can be the following: • Operable—The disk drive is operable. • Inoperable—The disk drive is inoperable, possibly due to a hardware issue such as bad blocks. • N/A—The operability of the disk drive cannot be determined. This could be due to the server or firmware not being support for disk drive monitoring, or because the server is powered off. Note Presence field The Operability field may show the incorrect status for several reasons, such as if the disk is part of a broken RAID set or if the BIOS POST (Power On Self Test) has not completed. The presence of the disk drive, and whether it can be detected in the server drive bay, regardless of its operational state. This can be the following: • Equipped—A disk drive can be detected in the server drive bay. • Missing—No disk drive can be detected in the server drive bay. Interpreting the Status of a Monitored Disk Drive Cisco UCS Manager displays the following properties for each monitored disk drive: • Operability—The operational state of the disk drive. • Presence—The presence of the disk drive, and whether it can be detected in the server drive bay, regardless of its operational state. You need to look at both properties to determine the status of the monitored disk drive. The following table shows the likely interpretations of the property values. Operability Status Presence Status Interpretation Operable Equipped No fault condition. The disk drive is in the server and can be used. Cisco UCS Manager GUI Configuration Guide, Release 2.0 660 OL-25712-04 Server Disk Drive Monitoring Operability Status Presence Status Interpretation Inoperable Equipped Fault condition. The disk drive is in the server, but one of the following could be causing an operability problem: • The disk drive is unusable due to a hardware issue such as bad blocks. • There is a problem with the IPMI link to the storage controller. N/A Missing Fault condition. The server drive bay does not contain a disk drive. N/A Equipped Fault condition. The disk drive is in the server, but one of the following could be causing an operability problem: • The server is powered off. • The storage controller firmware is the wrong version and does not support disk drive monitoring. • The server does not support disk drive monitoring. Note The Operability field may show the incorrect status for several reasons, such as if the disk is part of a broken RAID set or if the BIOS POST (Power On Self Test) has not completed. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 661 Server Disk Drive Monitoring Cisco UCS Manager GUI Configuration Guide, Release 2.0 662 OL-25712-04 CHAPTER 44 Configuring Statistics-Related Policies This chapter includes the following sections: • Configuring Statistics Collection Policies, page 663 • Configuring Statistics Threshold Policies, page 666 Configuring Statistics Collection Policies Statistics Collection Policy A statistics collection policy defines how frequently statistics are to be collected (collection interval) and how frequently the statistics are to be reported (reporting interval). Reporting intervals are longer than collection intervals so that multiple statistical data points can be collected during the reporting interval, which provides Cisco UCS Manager with sufficient data to calculate and report minimum, maximum, and average values. For NIC statistics, Cisco UCS Manager displays the average, minimum, and maximum of the change since the last collection of statistics. If the values are 0, there has been no change since the last collection. Statistics can be collected and reported for the following five functional areas of the Cisco UCS system: • Adapter—statistics related to the adapters • Chassis—statistics related to the blade chassis • Host—this policy is a placeholder for future support • Port—statistics related to the ports, including server ports, uplink Ethernet ports, and uplink Fibre Channel ports • Server—statistics related to servers Note Cisco UCS Manager has one default statistics collection policy for each of the five functional areas. You cannot create additional statistics collection policies and you cannot delete the existing default policies. You can only modify the default policies. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 663 Configuring Statistics Collection Policies Modifying a Statistics Collection Policy Note Cisco UCS Manager has one default statistics collection policy for each of the five functional areas. You cannot create additional statistics collection policies and you cannot delete the existing default policies. You can only modify the default policies. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 In the Admin tab, expand All > Stats Management > Stats. Right-click the policy that you want to modify and select Modify Collection Policy. In the Modify Collection Policy dialog box, complete the following fields: Step 4 Name Description Name field The name of the collection policy. This name is assigned by Cisco UCS and cannot be changed. Collection Interval field The length of time the fabric interconnect should wait between data recordings. This can be one of the following: • 30 Seconds • 1 Minute • 2 Minutes • 5 Minutes Cisco UCS Manager GUI Configuration Guide, Release 2.0 664 OL-25712-04 Configuring Statistics Collection Policies Name Description Reporting Interval field The length of time the fabric interconnect should wait before sending any data collected for the counter to Cisco UCS Manager. This can be one of the following: • 2 Minutes • 15 Minutes • 30 Minutes • 60 Minutes • 2 Hours • 4 Hours • 8 Hours When this time has elapsed, the fabric interconnect groups all data collected since the last time it sent information to Cisco UCS Manager, and it extracts four pieces of information from that group and sends them to Cisco UCS Manager: • The most recent statistic collected • The average of this group of statistics • The maximum value within this group • The minimum value within this group For example, if the collection interval is set to 1 minute and the reporting interval is 15 minutes, the fabric interconnect collects 15 samples in that 15 minute reporting interval. Instead of sending 15 statistics to Cisco UCS Manager, it sends only the most recent recording along with the average, minimum, and maximum values for the entire group. States Section Current Task field This field shows the task that is executing on behalf of this component. For details, see the associated FSM tab. Note Step 5 If there is no current task, this field is not displayed. Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 665 Configuring Statistics Threshold Policies Configuring Statistics Threshold Policies Statistics Threshold Policy A statistics threshold policy monitors statistics about certain aspects of the system and generates an event if the threshold is crossed. You can set both minimum and maximum thresholds. For example, you can configure the policy to raise an alarm if the CPU temperature exceeds a certain value, or if a server is overutilized or underutilized. These threshold policies do not control the hardware or device-level thresholds enforced by endpoints, such as the CIMC. Those thresholds are burned in to the hardware components at manufacture. Cisco UCS enables you to configure statistics threshold policies for the following components: • Servers and server components • Uplink Ethernet ports • Ethernet server ports, chassis, and fabric interconnects • Fibre Channel port Note You cannot create or delete a statistics threshold policy for Ethernet server ports, uplink Ethernet ports, or uplink Fibre Channel ports. You can only configure the existing default policy. Creating a Server and Server Component Threshold Policy Tip This procedure documents how to create a server and server component threshold policy on the Server tab. You can also create and configure these threshold policies within the appropriate organization in the Policies node on the LAN tab, SAN tab, and under the Stats Management node of the Admin tab. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 On the Servers tab, expand Servers > Policies. Expand the node for the organization where you want to create the policy. If the system does not include multitenancy, expand the root node. Step 4 Step 5 Right-click Threshold Policies and choose Create Threshold Policy. In the Define Name and Description page of the Create Threshold Policy wizard, do the following: a) Complete the following fields: Cisco UCS Manager GUI Configuration Guide, Release 2.0 666 OL-25712-04 Configuring Statistics Threshold Policies Name Description Name field The name of the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Description field A description of the policy. We recommend that you include information about where and when the policy should be used. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). b) Click Next. Step 6 In the Threshold Classes page of the Create Threshold Policy wizard, do the following: a) Click Add. b) In the Choose Statistics Class dialog box, choose the statistics class for which you want to configure a custom threshold from the Stat Class drop-down list. c) Click Next. Step 7 In the Threshold Definitions page, do the following: a) Click Add. The Create Threshold Definition dialog box opens. b) From the Property Type field, choose the threshold property that you want to define for the class. c) In the Normal Value field, enter the desired value for the property type. d) In the Alarm Triggers (Above Normal Value) fields, check one or more of the following check boxes: • Critical • Major • Minor • Warning • Condition • Info e) In the Up and Down fields, enter the range of values that should trigger the alarm. f) In the Alarm Triggers (Below Normal Value) fields, check one or more of the following check boxes: • Info • Condition • Warning • Minor • Major Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 667 Configuring Statistics Threshold Policies • Critical g) In the Up and Down fields, enter the range of values that should trigger the alarm. h) Click Finish Stage. i) Do one of the following: • To define another threshold property for the class, repeat Step 7. • If you have defined all required properties for the class, click Finish Stage. Step 8 In the Threshold Classes page of the Create Threshold Policy wizard, do one the following: • To configure another threshold class for the policy, repeat Steps 6 and 7. • If you have configured all required threshold classes for the policy, click Finish. Step 9 Click OK. Adding a Threshold Class to an Existing Server and Server Component Threshold Policy Tip This procedure documents how to add a threshold class to a server and server component threshold policy in the Server tab. You can also create and configure these threshold policies within the appropriate organization in the Policies node on the LAN tab, SAN tab, and under the Stats Management node of the Admin tab. Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 On the Servers tab, expand Servers > Policies > Organization_Name. Expand the Threshold Policies node. Right-click the policy to which you want to add a threshold class and choose Create Threshold Class. In the Choose Statistics Class page of the Create Threshold Class wizard, do the following: Step 5 a) From the Stat Class drop-down list, choose the statistics class for which you want to configure a custom threshold. b) Click Next. Step 6 In the Threshold Definitions page, do the following: a) Click Add. The Create Threshold Definition dialog box opens. b) From the Property Type field, choose the threshold property that you want to define for the class. c) In the Normal Value field, enter the desired value for the property type. d) In the Alarm Triggers (Above Normal Value) field, check one or more of the following check boxes: • Critical Cisco UCS Manager GUI Configuration Guide, Release 2.0 668 OL-25712-04 Configuring Statistics Threshold Policies • Major • Minor • Warning • Condition • Info e) In the Up and Down fields, enter the range of values that should trigger the alarm. f) In the Alarm Triggers (Below Normal Value) field, check one or more of the following check boxes: • Info • Condition • Warning • Minor • Major • Critical g) In the Up and Down fields, enter the range of values that should trigger the alarm. h) Click Finish Stage. i) Do one of the following: • To define another threshold property for the class, repeat Step 6. • If you have defined all required properties for the class, click Finish Stage. Step 7 In the Choose Statistics Class page of the Create Threshold Class wizard, do one the following: • To configure another threshold class for the policy, repeat Steps 5 and 6. • If you have configured all required threshold classes for the policy, click Finish. Step 8 Click OK. Deleting a Server and Server Component Threshold Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 Step 3 Step 4 Step 5 On the Servers tab, expand Servers > Policies > Organization_Name. Expand the Threshold Policies node. Right-click the policy you want to delete and select Delete. If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 669 Configuring Statistics Threshold Policies Adding a Threshold Class to the Uplink Ethernet Port Threshold Policy Tip You cannot create an uplink Ethernet port threshold policy. You can only modify or delete the default policy. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 Step 5 On the LAN tab, expand LAN > LAN Cloud. Expand the Threshold Policies node. Right-click Thr-policy-default and choose the Create Threshold Class. In the Choose Statistics Class page of the Create Threshold Class wizard, do the following: a) From the Stat Class drop-down list, choose the statistics class for which you want to configure a custom threshold. b) Click Next. Step 6 In the Threshold Definitions page, do the following: a) Click Add. The Create Threshold Definition dialog box opens. b) From the Property Type field, choose the threshold property that you want to define for the class. c) In the Normal Value field, enter the desired value for the property type. d) In the Alarm Triggers (Above Normal Value) field, check one or more of the following check boxes: • Critical • Major • Minor • Warning • Condition • Info e) In the Up and Down fields, enter the range of values that should trigger the alarm. f) In the Alarm Triggers (Below Normal Value) field, check one or more of the following check boxes: • Info • Condition • Warning • Minor • Major Cisco UCS Manager GUI Configuration Guide, Release 2.0 670 OL-25712-04 Configuring Statistics Threshold Policies • Critical g) In the Up and Down fields, enter the range of values that should trigger the alarm. h) Click Finish Stage. i) Do one of the following: • To define another threshold property for the class, repeat Step 6. • If you have defined all required properties for the class, click Finish Stage. Step 7 In the Create Threshold Class page of the Create Threshold Policy wizard, do one the following: • To configure another threshold class for the policy, repeat Steps 5 and 6. • If you have configured all required threshold classes for the policy, click Finish. Adding a Threshold Class to the Ethernet Server Port, Chassis, and Fabric Interconnect Threshold Policy Tip You cannot create an Ethernet server port, chassis, and fabric interconnect threshold policy. You can only modify or delete the default policy. Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 Step 3 Step 4 Step 5 In the LAN tab, expand LAN > Internal LAN. Expand the Threshold Policies node. Right-click Thr-policy-default and choose the Create Threshold Class. In the Choose Statistics Class page of the Create Threshold Class wizard, do the following: a) From the Stat Class drop-down list, choose the statistics class for which you want to configure a custom threshold. b) Click Next. Step 6 In the Threshold Definitions page, do the following: a) Click Add. The Create Threshold Definition dialog box opens. b) From the Property Type field, choose the threshold property that you want to define for the class. c) In the Normal Value field, enter the desired value for the property type. d) In the Alarm Triggers (Above Normal Value) field, check one or more of the following check boxes: • Critical • Major Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 671 Configuring Statistics Threshold Policies • Minor • Warning • Condition • Info e) In the Up and Down fields, enter the range of values that should trigger the alarm. f) In the Alarm Triggers (Below Normal Value) field, check one or more of the following check boxes: • Info • Condition • Warning • Minor • Major • Critical g) In the Up and Down fields, enter the range of values that should trigger the alarm. h) Click Finish Stage. i) Do one of the following: • To define another threshold property for the class, repeat Step 6. • If you have defined all required properties for the class, click Finish Stage. Step 7 In the Create Threshold Class page of the Create Threshold Policy wizard, do one the following: • To configure another threshold class for the policy, repeat Steps 5 and 6. • If you have configured all required threshold classes for the policy, click Finish. Adding a Threshold Class to the Fibre Channel Port Threshold Policy You cannot create a Fibre Channel port threshold policy. You can only modify or delete the default policy. Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 Step 3 Step 4 Step 5 On the SAN tab, expand SAN > SAN Cloud. Expand the Threshold Policies node. Right-click Thr-policy-default and choose the Create Threshold Class. In the Choose Statistics Class page of the Create Threshold Class wizard, do the following: a) From the Stat Class drop-down list, choose the statistics class for which you want to configure a custom threshold. Cisco UCS Manager GUI Configuration Guide, Release 2.0 672 OL-25712-04 Configuring Statistics Threshold Policies b) Click Next. Step 6 In the Threshold Definitions page, do the following: a) Click Add. The Create Threshold Definition dialog box opens. b) From the Property Type field, choose the threshold property that you want to define for the class. c) In the Normal Value field, enter the desired value for the property type. d) In the Alarm Triggers (Above Normal Value) field, check one or more of the following check boxes: • Critical • Major • Minor • Warning • Condition • Info e) In the Up and Down fields, enter the range of values that should trigger the alarm. f) In the Alarm Triggers (Below Normal Value) field, check one or more of the following check boxes: • Info • Condition • Warning • Minor • Major • Critical g) In the Up and Down fields, enter the range of values that should trigger the alarm. h) Click Finish Stage. i) Do one of the following: • To define another threshold property for the class, repeat Step 6. • If you have defined all required properties for the class, click Finish Stage. Step 7 In the Create Threshold Class page of the Create Threshold Policy wizard, do one the following: • To configure another threshold class for the policy, repeat Steps 5 and 6. • If you have configured all required threshold classes for the policy, click Finish. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 673 Configuring Statistics Threshold Policies Cisco UCS Manager GUI Configuration Guide, Release 2.0 674 OL-25712-04 CHAPTER 45 Configuring Call Home This chapter includes the following sections: • Call Home, page 675 • Call Home Considerations and Guidelines, page 677 • Cisco UCS Faults and Call Home Severity Levels, page 678 • Cisco Smart Call Home, page 679 • Configuring Call Home, page 680 • Disabling Call Home, page 683 • Enabling Call Home, page 683 • Configuring System Inventory Messages, page 684 • Configuring Call Home Profiles, page 685 • Configuring Call Home Policies, page 688 • Example: Configuring Call Home for Smart Call Home, page 690 Call Home Call Home provides an email-based notification for critical system policies. A range of message formats are available for compatibility with pager services or XML-based automated parsing applications. You can use this feature to page a network support engineer, email a Network Operations Center, or use Cisco Smart Call Home services to generate a case with the Technical Assistance Center. The Call Home feature can deliver alert messages containing information about diagnostics and environmental faults and events. The Call Home feature can deliver alerts to multiple recipients, referred to as Call Home destination profiles. Each profile includes configurable message formats and content categories. A predefined destination profile is provided for sending alerts to the Cisco TAC, but you also can define your own destination profiles. When you configure Call Home to send messages, Cisco UCS Manager executes the appropriate CLI show command and attaches the command output to the message. Cisco UCS delivers Call Home messages in the following formats: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 675 Call Home • Short text format which provides a one or two line description of the fault that is suitable for pagers or printed reports. • Full text format which provides fully formatted message with detailed information that is suitable for human reading. • XML machine readable format that uses Extensible Markup Language (XML) and Adaptive Messaging Language (AML) XML schema definition (XSD). The AML XSD is published on the Cisco.com website. The XML format enables communication with the Cisco Systems Technical Assistance Center. For information about the faults that can trigger Call Home email alerts, see the Cisco UCS Faults and Error Messages Reference. Cisco UCS Manager GUI Configuration Guide, Release 2.0 676 OL-25712-04 Call Home Considerations and Guidelines The following figure shows the flow of events after a Cisco UCS fault is triggered in a system with Call Home configured: Figure 2: Flow of Events after a Fault is Triggered Call Home Considerations and Guidelines How you configure Call Home depends on how you intend to use the feature. The information you need to consider before you configure Call Home includes the following: Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 677 Cisco UCS Faults and Call Home Severity Levels Destination Profile You must configure at least one destination profile. The destination profile or profiles that you use depend upon whether the receiving entity is a pager, email, or automated service such as Cisco Smart Call Home. If the destination profile uses email message delivery, you must specify a Simple Mail Transfer Protocol (SMTP) server when you configure Call Home. Contact Information The contact email, phone, and street address information should be configured so that the receiver can determine the origin of messages received from the Cisco UCS domain. Cisco Smart Call Home sends the registration email to this email address after you send a system inventory to begin the registration process. If an email address includes special characters, such as # (hash), spaces, or & (ampersand), the email server may not be able to deliver email messages to that address. Cisco recommends that you use email addresses which comply with RFC2821 and RFC2822 and include only 7bit ASCII characters. IP Connectivity to Email Server or HTTP Server The fabric interconnect must have IP connectivity to an email server or the destination HTTP server. In a cluster configuration, both fabric interconnects must have IP connectivity. This connectivity ensures that the current, active fabric interconnect can send Call Home email messages. The source of these email messages is always the IP address of a fabric interconnect. The virtual IP address assigned Cisco UCS Manager in a cluster configuration is never the source of the email. Smart Call Home If Cisco Smart Call Home is used, the following are required: • An active service contract must cover the device being configured • The customer ID associated with the Smart Call Home configuration in Cisco UCS must be the CCO (Cisco.com) account name associated with a support contract that includes Smart Call Home Cisco UCS Faults and Call Home Severity Levels Because Call Home is present across several Cisco product lines, Call Home has developed its own standardized severity levels. The following table describes how the underlying Cisco UCS fault levels map to the Call Home severity levels. You need to understand this mapping when you configure the Level setting for Call Home profiles. Table 12: Mapping of Faults and Call Home Severity Levels Call Home Severity Cisco UCS Fault Call Home Meaning (9) Catastrophic N/A Network-wide catastrophic failure. (8) Disaster N/A Significant network impact. (7) Fatal N/A System is unusable. Cisco UCS Manager GUI Configuration Guide, Release 2.0 678 OL-25712-04 Cisco Smart Call Home Call Home Severity Cisco UCS Fault Call Home Meaning (6) Critical Critical Critical conditions, immediate attention needed. (5) Major Major Major conditions. (4) Minor Minor Minor conditions. (3) Warning Warning Warning conditions. (2) Notification Info Basic notifications and informational messages. Possibly independently insignificant. (1) Normal Clear Normal event, signifying a return to normal state. (0) debug N/A Debugging messages. Cisco Smart Call Home Cisco Smart Call Home is a web application which leverages the Call Home feature of Cisco UCS. Smart Call Home offers proactive diagnostics and real-time email alerts of critical system events, which results in higher network availability and increased operational efficiency. Smart Call Home is a secure connected service offered by Cisco Unified Computing Support Service and Cisco Unified Computing Mission Critical Support Service for Cisco UCS. Note Using Smart Call Home requires the following: • A CCO ID associated with a corresponding Cisco Unified Computing Support Service or Cisco Unified Computing Mission Critical Support Service contract for your company. • Cisco Unified Computing Support Service or Cisco Unified Computing Mission Critical Support Service for the device to be registered. You can configure and register Cisco UCS Manager to send Smart Call Home email alerts to either the Smart Call Home System or the secure Transport Gateway. Email alerts sent to the secure Transport Gateway are forwarded to the Smart Call Home System using HTTPS. Note For security reasons, we recommend using the Transport Gateway option. The Transport Gateway can be downloaded from Cisco. To configure Smart Call Home, you must do the following: • Enable the Smart Call Home feature. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 679 Configuring Call Home • Configure the contact information. • Configure the email information. • Configure the SMTP server information. • Configure the default CiscoTAC-1 profile. • Send a Smart Call Home inventory message to start the registration process. • Ensure that the CCO ID you plan to use as the Call Home Customer ID for the Cisco UCS domain has the contract numbers from the registration added to its entitlements. You can update the ID in the account properties under Additional Access in the Profile Manager on CCO. Configuring Call Home Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Call Home. In the Work pane, click the General tab. Step 4 In the Admin area, complete the following fields to enable Call Home: Name Description State field This can be one of the following: • Off—Call Home is not used for this Cisco UCS domain. • On—Cisco UCS generates Call Home alerts based on the Call Home policies and profiles defined in the system. Note Switch Priority drop-down list If this field is set to On, Cisco UCS Manager GUI displays the rest of the fields on this tab. This can be one of the following: • Alerts • Critical • Debugging • Emergencies • Errors • Information • Notifications • Warnings Cisco UCS Manager GUI Configuration Guide, Release 2.0 680 OL-25712-04 Configuring Call Home Name Description Throttling field Whether the system limits the number of duplicate messages received for the same event. This can be one of the following: • On—If the number of duplicate messages sent exceeds 30 messages within a 2-hour time frame, then the system discards further messages for that alert type. • Off—The system sends all duplicate messages, regardless of how many are encountered. a) In the State field, click on. Note If this field is set to On, Cisco UCS Manager GUI displays the rest of the fields on this tab. b) From the Switch Priority drop-down list, select one of the following levels: • Alerts • Critical • Debugging • Emergencies • Errors • Information • Notifications • Warnings For a large Cisco UCS deployment with several pairs of fabric interconnects, this field enables you to attach significance to messages from one particular Cisco UCS domain, so that message recipients can gauge the priority of the message. This field may not be as useful for a small Cisco UCS deployment, such as a single Cisco UCS domain. Step 5 In the Contact Information area, complete the following fields with the required contact information: Name Description Contact field The main Call Home contact person. Enter up to 255 ASCII characters. Phone field The telephone number for the main contact. Enter the number in international format, starting with a + (plus sign) and a country code. You can use hyphens but not parentheses. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 681 Configuring Call Home Name Description Email field The email address for the main contact. Cisco Smart Call Home sends the registration email to this email address. Note Address field If an email address includes special characters, such as # (hash), spaces, or & (ampersand), the email server may not be able to deliver email messages to that address. Cisco recommends that you use email addresses which comply with RFC2821 and RFC2822 and include only 7bit ASCII characters. The mailing address for the main contact. Enter up to 255 ASCII characters. Step 6 In the Ids area, complete the following fields with the identification information that Call Home should use: Tip If you are not configuring Smart Call Home, this step is optional. Name Description Customer Id field The CCO ID that includes the contract numbers for the support contract in its entitlements. Enter up to 510 ASCII characters. Contract Id field The Call Home contract number for the customer. Enter up to 510 ASCII characters. Site Id field The unique Call Home identification number for the customer site. Enter up to 510 ASCII characters. Step 7 Step 8 In the Email Addresses area, complete the following fields with email information for Call Home alert messages: Name Description From field The email address that should appear in the From field on Call Home alert messages sent by the system. Reply To field The return email address that should appear in the From field on Call Home alert messages sent by the system. In the SMTP Server area, complete the following fields with information about the SMTP server where Call Home should send email messages: Cisco UCS Manager GUI Configuration Guide, Release 2.0 682 OL-25712-04 Disabling Call Home Name Description Host field The IP address or hostname of the SMTP server. Note Port field If you use a hostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager. The port number the system should use to talk to the SMTP server. Enter an integer between 1 and 65535. The default is 25. Step 9 Click Save Changes. Disabling Call Home Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Call Home. In the Work pane, click the General tab. Step 4 In the Admin area, click off in the State field. Note If this field is set to off, Cisco UCS Manager hides the rest of the fields on this tab. Click Save Changes. Step 5 Enabling Call Home Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Call Home. In the Work pane, click the General tab. Step 4 In the Admin area, click on in the State field. Note If this field is set to On, Cisco UCS Manager GUI displays the rest of the fields on this tab. Click Save Changes. Step 5 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 683 Configuring System Inventory Messages What to Do Next Ensure that Call Home is fully configured. Configuring System Inventory Messages Configuring System Inventory Messages Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Call Home. Step 4 In the Properties area, complete the following fields: In the Work pane, click the System Inventory tab. Name Description Send Periodically field If this field is set to On, Cisco UCS sends the system inventory to the Call Home database. When the information is sent depends on the other fields in this area. Send Interval field The number of days that should pass between automatic system inventory data collection. Enter an integer between 1 and 30. Hour of Day to Send field The hour that the data should be sent using the 24-hour clock format. Minute of Hour field The number of minutes after the hour that the data should be sent. Time Last Sent field The date and time the information was last sent. Note Next Scheduled field The date and time for the upcoming data collection. Note Step 5 This field is displayed after the first inventory has been sent. This field is displayed after the first inventory has been sent. Click Save Changes. Sending a System Inventory Message Use this procedure if you need to manually send a system inventory message outside of the scheduled messages. Cisco UCS Manager GUI Configuration Guide, Release 2.0 684 OL-25712-04 Configuring Call Home Profiles Note The system inventory message is sent only to those recipients defined in CiscoTAC-1 profile. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Call Home. In the Work pane, click the System Inventory tab. Step 4 In the Actions area, click Send System Inventory Now. Cisco UCS Manager immediately sends a system inventory message to the recipient configured for Call Home. Configuring Call Home Profiles Call Home Profiles Call Home profiles determine which alerts are sent to designated recipients. You can configure the profiles to send email alerts for events and faults at a desired severity level and for specific alert groups that represent categories of alerts. You can also use these profiles to specify the format of the alert for a specific set of recipients and alert groups. Each alert that Cisco UCS generates fits into a category represented by an alert group, such as the following: • Environmental alerts, including fans and power supplies • Diagnostic alerts, such as POST completion failure on a server Alert groups and Call Home profiles enable you to filter the alerts and ensure that a specific profile only receives certain categories of alerts. For example, a data center may have a hardware team that handles issues with fans and power supplies. This hardware team does not care about server POST failures or licensing issues. To ensure that the hardware team only receives relevant alerts, create a Call Home profile for the hardware team and check only the "environmental" alert group. By default, you must configure the Cisco TAC-1 profile. However, you can also create additional profiles to send email alerts to one or more alert groups when events occur at the level that you specify and provide the recipients with the appropriate amount of information about those alerts. For example, you may want to configure two profiles for faults with a major severity: • A profile that sends an alert to the Supervisor alert group in the short text format. Members of this group receive a one- or two-line description of the fault that they can use to track the issue. • A profile that sends an alert to the CiscoTAC alert group in the XML format. Members of this group receive a detailed message in the machine readable format preferred by the Cisco Systems Technical Assistance Center. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 685 Configuring Call Home Profiles Creating a Call Home Profile By default, you must configure the Cisco TAC-1 profile. However, you can also create additional profiles to send email alerts to one or more specified groups when events occur at the level that you specify. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Call Home. In the Work pane, click the Profiles tab. Step 4 On the icon bar to the right of the table, click +. If the + icon is disabled, click an entry in the table to enable it. Step 5 In the Create Call Home Profile dialog box, complete the following information fields: Name Description Name field A user-defined name for this profile. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. Level field Cisco UCS faults that are greater than or equal to this level trigger the profile. This can be one of the following: • Critical • Debug • Disaster • Fatal • Major • Minor • Normal • Notification • Warning Cisco UCS Manager GUI Configuration Guide, Release 2.0 686 OL-25712-04 Configuring Call Home Profiles Name Description Alert Groups field The group or groups that are alerted based on this Call Home profile. This can be one or more of the following: • Cisco Tac • Diagnostic • Environmental • Inventory • License • Life Cycle • Linecard • Supervisor • Syslog Port • System • Test Step 6 In the Email Configuration area, complete the following fields to configure the email alerts: Name Description Format field This can be one of the following: • Xml—A machine readable format that uses Extensible Markup Language (XML) and Adaptive Messaging Language (AML) XML schema definition (XSD). This format enables communication with the Cisco Systems Technical Assistance Center. • Full Txt—A fully formatted message with detailed information that is suitable for human reading. • Short Txt—A one or two line description of the fault that is suitable for pagers or printed reports. Max Message Size field The maximum message size that is sent to the designated Call Home recipients. Enter an integer between 1 and 5000000. The default is 5000000. For full text and XML messages, the maximum recommended size is 5000000. For short text messages, the maximum recommended size is 100000. For the CiscoTAC-1, the maximum message size must be 5000000. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 687 Configuring Call Home Policies Step 7 In the Recipients area, do the following to add one or more email recipients for the email alerts: a) On the icon bar to the right of the table, click +. b) In the Add Email Recipients dialog box, enter the email address to which Call Home alerts should be sent in the Email field. After you save this email address, it can be deleted but it cannot be changed. c) Click OK. Step 8 Click OK. Deleting a Call Home Profile Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Call Home. In the Work pane, click the Profiles tab. Step 4 Step 5 Right-click the profile you want to delete and choose Delete. Click Save Changes. Configuring Call Home Policies Call Home Policies Call Home policies determine whether or not Call Home alerts are sent for a specific type of fault or system event. By default, Call Home is enabled to send alerts for certain types of faults and system events. However, you can configure Cisco UCS not to process certain types. To disable alerts for a type of fault or events, you must create a Call Home policy for that type, and you must first create a policy for that type and then disable the policy. Configuring a Call Home Policy Tip By default, all Call Home policies are enabled to ensure that email alerts are sent for all critical system events. Cisco UCS Manager GUI Configuration Guide, Release 2.0 688 OL-25712-04 Configuring Call Home Policies Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Call Home. In the Work pane, click the Policies tab. Step 4 On the icon bar to the right of the table, click +. If the + icon is disabled, click an entry in the table to enable it. Step 5 In the Create Call Home Policy dialog box, complete the following fields: Step 6 Step 7 Name Description State field If this field is Enabled, the system uses this policy when an error matching the associated cause is encountered. Otherwise, the system ignores this policy even if a matching error occurs. By default, all policies are enabled. Cause field The event that triggers the alert. Each policy defines whether an alert is sent for one type of event. Click OK. Repeat Steps 6 and 7 if you want to configure a Call Home policy for a different type of fault or event. Disabling a Call Home Policy Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Call Home. In the Work pane, click the Policies tab. Step 4 Step 5 Step 6 Click the policy that you want to disable and choose Show Navigator. In the State field, click Disabled. Click OK. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 689 Example: Configuring Call Home for Smart Call Home Enabling a Call Home Policy Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Call Home. In the Work pane, click the Policies tab. Step 4 Step 5 Step 6 Click the policy that you want to enable and choose Show Navigator. In the State field, click Enabled. Click OK. Deleting a Call Home Policy Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Call Home. In the Work pane, click the Policies tab. Step 4 Step 5 Right-click the policy that you want to disable and choose Delete. Click Save Changes. Example: Configuring Call Home for Smart Call Home Configuring Smart Call Home Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Call Home. In the Work pane, click the General tab. Step 4 In the Admin area, do the following to enable Call Home: a) In the State field, click on. Note If this field is set to On, Cisco UCS Manager GUI displays the rest of the fields on this tab. b) From the Switch Priority drop-down list, select one of the following urgency levels: Cisco UCS Manager GUI Configuration Guide, Release 2.0 690 OL-25712-04 Example: Configuring Call Home for Smart Call Home • Alerts • Critical • Debugging • Emergencies • Errors • Information • Notifications • Warnings Step 5 In the Contact Information area, complete the following fields with the required contact information: Name Description Contact field The main Call Home contact person. Enter up to 255 ASCII characters. Phone field The telephone number for the main contact. Enter the number in international format, starting with a + (plus sign) and a country code. You can use hyphens but not parentheses. Email field The email address for the main contact. Cisco Smart Call Home sends the registration email to this email address. Note Address field If an email address includes special characters, such as # (hash), spaces, or & (ampersand), the email server may not be able to deliver email messages to that address. Cisco recommends that you use email addresses which comply with RFC2821 and RFC2822 and include only 7bit ASCII characters. The mailing address for the main contact. Enter up to 255 ASCII characters. Step 6 In the Ids area, complete the following fields with the Smart Call Home identification information: Name Description Customer Id field The CCO ID that includes the contract numbers for the support contract in its entitlements. Enter up to 510 ASCII characters. Contract Id field The Call Home contract number for the customer. Enter up to 510 ASCII characters. Site Id field The unique Call Home identification number for the customer site. Enter up to 510 ASCII characters. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 691 Example: Configuring Call Home for Smart Call Home Step 7 Step 8 In the Email Addresses area, complete the following fields with the email information for Smart Call Home alert messages: Name Description From field The email address that should appear in the From field on Call Home alert messages sent by the system. Reply To field The return email address that should appear in the From field on Call Home alert messages sent by the system. In the SMTP Server area, complete the following fields with information about the SMTP server that Call Home should use to send email messages: Name Description Host field The IP address or hostname of the SMTP server. Note Port field If you use a hostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager. The port number the system should use to talk to the SMTP server. Enter an integer between 1 and 65535. The default is 25. Step 9 Click Save Changes. Configuring the Default Cisco TAC-1 Profile The following are the default settings for the CiscoTAC-1 profile: • Level is normal • Only the CiscoTAC alert group is selected • Format is xml • Maximum message size is 5000000 Cisco UCS Manager GUI Configuration Guide, Release 2.0 692 OL-25712-04 Example: Configuring Call Home for Smart Call Home Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Call Home. In the Work pane, click the Profiles tab. Step 4 Step 5 Right-click the Cisco TAC-1 profile and choose Recipient. In the Add Email Recipients dialog box, do the following: a) In the Email field, enter the email address to which Call Home alerts should be sent. For example, enter callhome@cisco.com. After you save this email address, it can be deleted but it cannot be changed. b) Click OK. Configuring System Inventory Messages for Smart Call Home Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Call Home. In the Work pane, click the System Inventory tab. Step 4 In the Properties area, complete the following fields to specify how system inventory messages will be sent to Smart Call Home: Name Description Send Periodically field If this field is set to On, Cisco UCS sends the system inventory to the Call Home database. When the information is sent depends on the other fields in this area. Send Interval field The number of days that should pass between automatic system inventory data collection. Enter an integer between 1 and 30. Hour of Day to Send field The hour that the data should be sent using the 24-hour clock format. Minute of Hour field The number of minutes after the hour that the data should be sent. Time Last Sent field The date and time the information was last sent. Note This field is displayed after the first inventory has been sent. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 693 Example: Configuring Call Home for Smart Call Home Name Description Next Scheduled field The date and time for the upcoming data collection. Note Step 5 This field is displayed after the first inventory has been sent. Click Save Changes. Registering Smart Call Home Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 On the Admin tab, expand All > Communication Management > Call Home. In the Work pane, click the System Inventory tab. Step 4 In the Actions area, click Send System Inventory Now to start the registration process. When Cisco receives the system inventory, a Smart Call Home registration email is sent to the email address that you configured in the Contact Information area on the General tab. Step 5 When you receive the registration email from Cisco, do the following to complete registration for Smart Call Home: a) Click the link in the email. The link opens the Cisco Smart Call Home portal in your web browser. b) Log into the Cisco Smart Call Home portal. c) Follow the steps provided by Cisco Smart Call Home. After you agree to the terms and conditions, the Cisco Smart Call Home registration for the Cisco UCS domain is complete. Cisco UCS Manager GUI Configuration Guide, Release 2.0 694 OL-25712-04 CHAPTER 46 Managing the System Event Log This chapter includes the following sections: • System Event Log, page 695 • Viewing the System Event Log for an Individual Server, page 696 • Viewing the System Event Log for the Servers in a Chassis, page 696 • Configuring the SEL Policy, page 696 • Managing the System Event Log for a Server, page 698 System Event Log The system event log (SEL) resides on the CIMC in NVRAM. It records most server-related events, such as over and under voltage, temperature events, fan events, and events from BIOS. The SEL is mainly used for troubleshooting purposes. The SEL file is approximately 40KB in size, and no further events can be recorded when it is full. It must be cleared before additional events can be recorded. You can use the SEL policy to backup the SEL to a remote server, and optionally clear the SEL after a backup operation occurs. Backup operations can be triggered based on specific actions, or they can occur at regular intervals. You can also manually backup or clear the SEL. The backup file is automatically generated. The filename format is sel-SystemName-ChassisID-ServerID-ServerSerialNumber-Timestamp; for example, sel-UCS-A-ch01-serv01-QCI12522939-20091121160736. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 695 Viewing the System Event Log for an Individual Server Viewing the System Event Log for an Individual Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 Step 4 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers. Click the server for which you want to view the system event log. In the Work pane, click the SEL Logs tab. Cisco UCS Manager retrieves the system event log for the server and displays the list of events. Viewing the System Event Log for the Servers in a Chassis Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, expand Equipment > Chassis > Chassis_Name . In the Work pane, click the SEL Logs tab. Cisco UCS Manager retrieves the system event log for the server and displays the list of events. Step 4 In the Server table, click the server for which you want to view the system event log. Cisco UCS Manager retrieves the system event log for the server and displays the list of events. Configuring the SEL Policy Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 Step 3 On the Equipment tab, click the Equipment node. In the Work pane, click the Policies tab. Step 4 Step 5 Click the SEL Policy subtab. (Optional) In the General area, type a description of the policy in the Description field. The other fields in this area are read-only. Step 6 In the Backup Configuration area, complete the following fields: Cisco UCS Manager GUI Configuration Guide, Release 2.0 696 OL-25712-04 Configuring the SEL Policy Name Description Protocol field The protocol to use when communicating with the remote server. This can be one of the following: • FTP • TFTP • SCP • SFTP Hostname field The hostname or IP address of the server on which the backup configuration resides. If you use a hostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager. Note The name of the backup file is generated by Cisco UCS. The name is in the following format: sel-system-name-chchassis-idservblade-id-blade-serial -timestamp Remote Path field The absolute path to the file on the remote server, if required. If you use SCP, the absolute path is always required. If you use any other protocol, you may not need to specify a remote path if the file resides in the default download folder. For details about how your file server is configured, contact your system administrator. Backup Interval drop-down list The time to wait between automatic backups. This can be one of the following: • Never—Do not perform any automatic SEL data backups. • 1 Hour • 2 Hours • 4 Hours • 8 Hours • 24 Hours Note Format field If you want the system to create automatic backups, make sure you check the Timer check box in the Action option box. The format to use for the backup file. This can be one of the following: • Ascii • Binary Clear on Backup check box If checked, Cisco UCS clears all system event logs after the backup. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 697 Managing the System Event Log for a Server Name Description User field The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP. Password field The password for the remote server username. This field does not apply if the protocol is TFTP. Action option box For each box that is checked, then the system creates a SEL backup when that event is encountered: • Log Full—The log reaches the maximum size allowed. • On Change of Association—The association between a server and its service profile changes. • On Clear—The user manually clears a system event log. • Timer—The time interval specified in the Backup Interval drop-down list is reached. Reset Configuration button Step 7 Click this button to reset the background configuration information. Click Save Changes. Managing the System Event Log for a Server Copying One or More Entries in the System Event Log This task assumes that you are viewing the system event log for a server from the SEL Logs tab for a server or a chassis. Procedure Step 1 Step 2 Step 3 After Cisco UCS Manager GUI displays the system event log in the SEL Logs tab, use your mouse to highlight the entry or entries that you want to copy from the system event log. Click Copy to copy the highlighted text to the clipboard. Paste the highlighted text into a text editor or other document. Cisco UCS Manager GUI Configuration Guide, Release 2.0 698 OL-25712-04 Managing the System Event Log for a Server Printing the System Event Log This task assumes that you are viewing the system event log for a server from the SEL Logs tab for a server or a chassis. Procedure Step 1 Step 2 After Cisco UCS Manager GUI displays the system event log in the SEL Logs tab, click Print. In the Print dialog box, do the following: a) (Optional) Modify the default printer or any other fields or options. b) Click Print. Refreshing the System Event Log This task assumes that you are viewing the system event log for a server from the SEL Logs tab for a server or a chassis. Procedure After Cisco UCS Manager GUI displays the system event log in the SEL Logs tab, click Refresh. Cisco UCS Manager retrieves the system event log for the server and displays the updated list of events. Manually Backing Up the System Event Log This task assumes that you are viewing the system event log for a server from the SEL Logs tab for a server or a chassis. Before You Begin Configure the system event log policy. The manual backup operation uses the remote destination configured in the system event log policy. Procedure After Cisco UCS Manager GUI displays the system event log in the SEL Logs tab, click Backup. Cisco UCS Manager backs up the system event log to the location specified in the SEL policy. Manually Clearing the System Event Log This task assumes that you are viewing the system event log for a server from the SEL Logs tab for a server or a chassis. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 699 Managing the System Event Log for a Server Procedure After Cisco UCS Manager GUI displays the system event log in the SEL Logs tab, click Clear. Note This action triggers an automatic backup if Clear is enabled in the SEL policy Action option box. Cisco UCS Manager GUI Configuration Guide, Release 2.0 700 OL-25712-04 CHAPTER 47 Configuring Settings for Faults, Events, and Logs This chapter includes the following sections: • Configuring Settings for the Fault Collection Policy, page 701 • Configuring Settings for the Core File Exporter, page 703 • Configuring the Syslog, page 704 Configuring Settings for the Fault Collection Policy Fault Collection Policy The fault collection policy controls the lifecycle of a fault in a Cisco UCS domain, including when faults are cleared, the flapping interval (the length of time between the fault being raised and the condition being cleared), and the retention interval (the length of time a fault is retained in the system). A fault in Cisco UCS has the following lifecycle: 1 A condition occurs in the system and Cisco UCS Manager raises a fault. This is the active state. 2 When the fault is alleviated, it enters a flapping or soaking interval that is designed to prevent flapping. Flapping occurs when a fault is raised and cleared several times in rapid succession. During the flapping interval, the fault retains its severity for the length of time specified in the fault collection policy. 3 If the condition reoccurs during the flapping interval, the fault returns to the active state. If the condition does not reoccur during the flapping interval, the fault is cleared. 4 The cleared fault enters the retention interval. This interval ensures that the fault reaches the attention of an administrator even if the condition that caused the fault has been alleviated and the fault has not been deleted prematurely. The retention interval retains the cleared fault for the length of time specified in the fault collection policy. 5 If the condition reoccurs during the retention interval, the fault returns to the active state. If the condition does not reoccur, the fault is deleted. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 701 Configuring Settings for the Fault Collection Policy Configuring the Fault Collection Policy Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > Faults, Events, and Audit Log. Click Settings. In the Work pane, complete the following fields in the Fault Collection Policy area: Name Description Flapping Interval field Flapping occurs when a fault is raised and cleared several times in rapid succession. To prevent this, the system does not allow a fault to change its state until this amount of time has elapsed since the last state change. If the condition reoccurs during the flapping interval, the fault returns to the active state. If the condition does not reoccur during the flapping interval, the fault is cleared. What happens at that point depends on the setting in the Clear Action field. Enter an integer between 5 and 3,600. The default is 10. Clear Action field The action the system takes when a fault is cleared. This can be one of the following: • Retain—Cisco UCS Manager GUI displays the Length of time to retain cleared faults section. • Delete—The system immediately deletes all fault messages as soon as they are marked as cleared. Length of Time to Retain Cleared Faults Section Retention Interval field If the Clear Action field is set to Retain, this is the length of time the system retains a fault once it is marked as cleared. This can be one of the following: • Forever—The system leaves all cleared fault messages on the fabric interconnect regardless of how long they have been in the system. • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field. dd:hh:mm:ss field Step 5 The number of days, hours, minutes, and seconds that should pass before the system deletes a cleared fault message. Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 702 OL-25712-04 Configuring Settings for the Core File Exporter Configuring Settings for the Core File Exporter Core File Exporter Cisco UCS Manager uses the Core File Exporter to export core files as soon as they occur to a specified location on the network through TFTP. This functionality allows you to export the tar file with the contents of the core file. Configuring the Core File Exporter Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > Faults, Events, and Audit Log. Click Settings. In the Work pane, complete the following fields in the TFTP Core Exporter area: Name Description Admin State field This can be one of the following: • Enabled—If an error causes the server to perform a core dump, the system sends the core dump file via FTP to a given location. When this option is selected, Cisco UCS Manager GUI displays the other fields in this area that enable you to specify the FTP export options. • Disabled—Core dump files are not automatically exported. Description field A user-defined description of the core file. Enter up to 256 characters. You can use any characters or spaces except ^ (carat), \ (backslash), > (greater than), < (less than), ' (single quote), " (double quote), ` (accent mark), or = (equal sign). Port field The port number to use when exporting the core dump file via TFTP. Hostname field The hostname or IP address to connect with via TFTP. Note Path field Step 5 If you use a hostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager. The path to use when storing the core dump file on the remote system. Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 703 Configuring the Syslog Disabling the Core File Exporter Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > Faults, Events, and Audit Log. Click Settings. In the Work pane, click the Settings tab. Step 5 Step 6 In the TFTP Core Exporter area, click the disabled radio button in the Admin State field. Click Save Changes. Configuring the Syslog Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Step 3 Step 4 On the Admin tab, expand All > Faults, Events, and Audit Log. Click Syslog. In the Work pane, click the Syslog tab. Step 5 In the Local Destinations area, complete the following fields: Name Description Console Section Admin State field This can be one of the following: • Enabled • Disabled Level field If the Admin State field is enabled, select the lowest message level that you want displayed. The system displays that level and above on the console. This can be one of the following: • Emergencies • Alerts • Critical Monitor Section Cisco UCS Manager GUI Configuration Guide, Release 2.0 704 OL-25712-04 Configuring the Syslog Name Description Admin State field This can be one of the following: • Enabled • Disabled If Admin State is enabled, Cisco UCS Manager GUI displays the rest of the fields in this section. Level drop-down list If the Admin State field is enabled, select the lowest message level that you want displayed. The system displays that level and above on the monitor. This can be one of the following: • Emergencies • Alerts • Critical • Errors • Warnings • Notifications • Information • Debugging File Section Admin State field This can be one of the following: • Enabled • Disabled If Admin State is enabled, Cisco UCS Manager GUI displays the rest of the fields in this section. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 705 Configuring the Syslog Name Description Level drop-down list Select the lowest message level that you want the system to store. The system stores that level and above in a file on the fabric interconnect. This can be one of the following: • Emergencies • Alerts • Critical • Errors • Warnings • Notifications • Information • Debugging Name field The name of the file in which the messages are logged. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or special characters. Size field The maximum size, in bytes, the file can be before Cisco UCS Manager begins to write over the oldest messages with the newest ones. Enter an integer between 4096 and 4194304. Step 6 In the Remote Destinations area, complete the following fields to configure up to three external logs that can store messages generated by the Cisco UCS components: Name Description Admin State field This can be one of the following: • Enabled • Disabled If Admin State is enabled, Cisco UCS Manager GUI displays the rest of the fields in this section. Cisco UCS Manager GUI Configuration Guide, Release 2.0 706 OL-25712-04 Configuring the Syslog Name Description Level drop-down list Select the lowest message level that you want the system to store. The system stores that level and above in the remote file. This can be one of the following: • Emergencies • Alerts • Critical • Errors • Warnings • Notifications • Information • Debugging Hostname field The hostname or IP address on which the remote log file resides. Note Facility drop-down list If you use a hostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager. This can be one of the following: • Local0 • Local1 • Local2 • Local3 • Local4 • Local5 • Local6 • Local7 Step 7 Click Save Changes. Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 707 Configuring the Syslog Cisco UCS Manager GUI Configuration Guide, Release 2.0 708 OL-25712-04 INDEX A accounts 159, 160, 162, 171, 176, 177, 179, 180 admin 160 creating user 171 deleting local 177 disabling 176 enabling 176 expiration 160 locally authenticated 160, 177, 179, 180 remotely authenticated 160 user 159, 162 username guidelines 160 acknowledging 578, 591, 605 blade servers 591 chassis 578 rack-mount servers 605 activate firmware 186 activating 213, 214, 215, 217, 218, 219, 220, 221, 232, 236 adapter firmware 213 BIOS firmware 214 board controller firmware 218 capability catalog 232 CIMC firmware 215 IOM firmware 217 management extensions 236 primary fabric interconnects 220 standalone fabric interconnects 221 subordinate fabric interconnects 219 activating user accounts 176 activities 471, 484, 485, 486 pending 471, 484, 485, 486 adapter 108 port channels 108 adapter port channels 108 viewing 108 adapters 41, 204, 212, 213, 430 activating firmware 213 NIC 41 updating firmware 212 vCon placement 430 verifying status 204 adapters (continued) VIC 41 virtualization 41 adding 269, 576 NTP servers 576 ports to a port channel 269 admin account 160 administration 43 aging time 245 MAC address table 245 alert groups 685 profiles 685 all configuration 619 API, copying XML 61 appliance port channels 100, 103, 104 adding ports 103 creating 100 deleting 104 disabling 103 enabling 103 removing ports 103 appliance ports 89, 92 configuring 89 modifying 92 architectural simplification 9 area, Fault Summary 48 associating servers 544 authentication 131 primary 131 remote 131 authentication domains 150 about 150 creating 150 authentication profile 449, 450 deleting 450 authentication service 151, 152 console 151 default 152 authentication services 131 about 131 authNoPriv 122 authPriv 122 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 IN-1 Index autoconfiguration policy 25, 417, 418 about 25, 417 creating 417 deleting 418 Automatically Reconnect 57 B backing up 200, 619, 620, 621, 622, 625, 626, 696, 699 about 619 considerations 620 creating operations 200, 622 deleting operation 626 modifying operations 625 running operations 200, 625 system event log 696, 699 manual 699 scheduled 696 types 619 user role 621 backup operations 200, 622, 625, 626 creating 200, 622 deleting 626 modifying 625 running 200, 625 banner 56, 57 pre-login 56, 57 beacon 582, 594, 607 blade servers 594 chassis 582 rack-mount servers 607 beacon leds 80 beacon LEDs 84 best effort system class 37, 298 binding 311, 357, 561 service profiles 561 vHBAs 357 vNICs 311 BIOS 213, 214, 381, 382, 384, 390, 392, 394, 395, 396, 397, 402, 403, 404 activating firmware 214 actual settings 404 creating policy 403 default settings 402 modifying defaults 404 policy 402 settings 381, 382, 384, 390, 392, 394, 395, 396, 397 about 381 boot options 396 Intel Directed I/O 390 main 382 PCI configuration 395 processor 384 BIOS (continued) settings (continued) RAS memory 392 serial port 394 server management 397 USB 394 updating firmware 213 BIOS, recovering 595, 609 blade 572 viewing power cap 572 blade servers 517, 541, 585, 586, 587, 588, 589, 590, 591, 592, 594, 595, 596, 597, 604, 650 decommissioning 592 determining boot order 587 hardware based service profiles 517 issuing an NMI 597 locator LED 594 managing 585, 586 monitoring 650 POST results 596 power cycling 589 reacknowledging 591 recovering BIOS 595 removing 594 from database 594 resetting 594, 595 CIMC 595 CMOS 594 shutting down 588 template based service profiles 541 unexpected power changes 590, 604 blade-level power cap 571 setting for server 571 board controllers, activating firmware 218 boot 441, 465, 466 LAN 465 local disk 465, 466 SAN 441 virtual media 466 boot options, BIOS settings 396 boot order 454, 458, 587, 601 blade servers 587 modifying 458 rack-mount servers 601 setting 454 boot order, modifying 550 boot parameters 454, 458 iSCSI boot 454, 458 modifying 458 setting 454 boot policies 15, 439, 440, 441, 465, 466, 467 about 15, 439 creating 440 deleting 467 Cisco UCS Manager GUI Configuration Guide, Release 2.0 IN-2 OL-25712-04 Index boot policies (continued) LAN boot 465 local disk boot 465, 466 SAN boot 441 virtual media boot 466 boot process 444 iSCSI 444 bootflash, available space 209 booting 586, 587, 600, 601 blade servers 586 determining boot order 587, 601 rack-mount servers 600 servers from service profile 587, 601 bronze system class 37, 298 bundles, firmware 184 burned in values 14, 488 C Cabling Considerations for Port Channel Mode} 109 About 109 Call Home 675, 677, 678, 679, 680, 683, 684, 685, 686, 688, 689, 690, 692, 694 about 675 Cisco TAC-1 profile 692 configuring 680 configuring policies 688 considerations 677 creating profiles 686 deleting policies 690 deleting profiles 688 disabling 683 disabling policies 689 enabling 683 enabling policies 690 policies 688 profiles 685 registering Smart Call Home 694 severity levels 678 Smart Call Home 679 system inventory messages 684 canceling image downloads 208 capability catalog 230, 231, 232, 233, 234, 235 about 230 activating 232 contents 230 updates 231 updating 233, 234, 235 verifying version 232 viewing provider 233 capping server power usage 571 catalog 185, 230, 231 capability 230, 231 firmware images 185 CDP 318 certificate 115, 117 about 115 HTTPS 117 changing 57, 86 ports 86 properties 57 chassis 16, 53, 239, 242, 566, 568, 577, 578, 579, 580, 581, 582, 591, 593, 597, 648 acknowledging 578 acknowledging servers 591 decommissioning 579 discovery policy 16, 239, 242 enabling decommissioned 579, 580 hybrid display 53 issuing an NMI 597 management 577 monitoring 648 POST results 582 power groups 566, 568 adding chassis 568 creating 566 deleting 568 removing chassis 568 reacknowledging slot 593 removing 579 removing server 591 renumbering 581 turning off locator LED 582 turning on locator LED 582 chassis connectivity policy 243 system-related policies 243 chassis 243 chassis discovery policy 16, 239, 242 about 16, 239 configuring 242 chassis management 577, 578, 579, 580, 582, 648 acknowledging 578 enabling decommissioned 579, 580 monitoring 648 removing 579 turning off locator LED 582 turning on locator LED 582 CIM-XML, configuring 114 CIMC 215, 373, 374, 375, 376, 377, 595, 608 activating firmware 215 IP address 373 Management IP 374, 375, 376, 377 blade server 374 rack server 375 service profile templates 377 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 IN-3 Index CIMC (continued) Management IP (continued) service profiles 376 resetting 595, 608 updating firmware 215 Cisco Discovery Protocol 23, 317, 318 Cisco TAC-1 profile, configuring 692 Cisco UCS Manager 43, 47, 196 about 43 GUI 47 impact of firmware upgrade 196 Cisco VM-FEX 41 cisco-av-pair 132 CiscoAVPair 132 clearing licenses 256 clearing system event log 699 cloning service profiles 544 cluster configuration 69, 71, 202 high availability status 202 primary fabric interconnect 69 subordinate fabric interconnect 71 CMOS resetting 594, 608 communication services 55, 113, 114, 115, 116, 117, 118, 119, 125, 126, 128, 129, 174 about 113 CIM-XML 114 configuring 129 HTTP 115 HTTPS 116, 117, 118, 119 SNMP 125, 126, 128, 129 Telnet 129 web session limits 55, 174 community, SNMP 125 component, firmware 184 configuration 200, 621, 622, 625, 626, 631 backing up 200, 622, 625 import methods 621 importing 621 restoring 621, 626, 631 configuration, cluster 69, 71 configuration, standalone 67 configuring 85, 111, 114, 115, 116, 117, 118, 119, 129, 264 CIM-XML 114 communication services 129 HTTP 115 HTTPS 116, 117, 118, 119 ports 111, 264 server ports 85 confirmation messages 58 considerations 620, 677 backup operations 620 Call Home 677 console authentication service 151 console, KVM 611, 615 converged network adapters 41 virtualization 41 copying system event log 698 copying XML 61 Core File Exporter 703, 704 about 703 configuring 703 disabling 704 corrupt BIOS 595, 609 creating 541, 543 service profile templates 543 service profiles 541 custom roles 164 reserved words 164 D database 619, 621 backing up 619 restoring 621 deactivating user accounts 176 decommissioning 579, 592, 605 blade servers 592 chassis 579 rack-mount ervers 605 decommissioning chassis, guidelines 577 decommissioning rack-mount servers 600 decommissioning servers 586 default authentication service 152 default service profiles 14, 488, 517 default zoning 95, 96, 97 about 95 disabling 97 enabling 96 deferring deployment 29, 469, 470, 471, 472, 477, 479, 481, 482, 484, 485, 486 guidelines 471 maintenance policies 29, 470, 482 one time occurrences 477, 481 pending activities 471, 484, 485, 486 deploying 484, 485, 486 viewing 484 recurring occurrences 479, 481 schedules 470, 472, 482 service profiles 469 deleting 562 service profiles 562 determining acceptable range 60 determining policy usage 60 determining pool usage 61 disabling 88, 99, 112, 129, 266, 267, 269, 683, 704 Call Home 683 Cisco UCS Manager GUI Configuration Guide, Release 2.0 IN-4 OL-25712-04 Index disabling (continued) communication services 129 Core File Exporter 704 port channels 269 ports 88, 112 server ports 266 uplink Ethernet port channels 99 uplinkEthernet ports 267 disassociating servers 545 disaster recovery 619, 621 discovery policy 16, 25, 239, 242, 244, 419, 420 chassis 16, 239, 242 rack server 25, 244 server 25, 419, 420 disjoint L2 networks 321, 322, 323, 324, 327, 328, 329 about 321 configuring 324 guidelines 322 pinning considerations 323 VLANs 327, 328, 329 assigning ports and port channels 327 removing ports and port channels 328 viewing port and port channel assignments 329 disk drive monitoring 658, 659, 660 about 658 interpreting results 659, 660 limitations 658 prerequisites 659 support 658 DNS servers 237, 238 about 237 adding 237 deleting 238 domains, disjoint L2 321 downgrading 199 firmware 199 prerequisites 199 download firmware 186 downloading 206, 207, 208, 250, 251 canceling 208 images 206, 207 licenses 250, 251 dynamic vNIC connection policy 19 about 19 E enabling 87, 112, 125, 129, 265, 266, 268, 579, 580, 680, 683, 690, 703 Call Home 680, 683 Core File Exporter 703 decommissioned chassis 579, 580 port channels 268 enabling (continued) ports 87, 112 server ports 265 Smart Call Home 690 SNMP 125 Telnet 129 uplinkEthernet ports 266 end-host mode 73, 74, 264 Ethernet 73 Fibre Channel 74 endpoints 194, 196, 197 direct firmware upgrade 194, 196 service profile upgrade 197 enforcing password strength 174 Ethernet 11, 29, 38, 73, 77, 82, 83, 84, 85, 86, 89, 92, 94, 97, 98, 99, 100, 103, 104, 264, 267, 304 appliance port channels 100, 103, 104 appliance ports 89, 92 beacon LEDs 84 changing uplink ports 86 FCoE storage ports 94 Fibre Channel over 11 flow control policies 29, 38, 304 port mode 82, 83 server ports 85 switching mode 73, 264 uplink port channels 97, 98, 99, 100, 267 adding ports 99 deleting 100 disabling 99 removing ports 99 uplink ports 77, 85 Ethernet adapter policies 19, 312, 313, 317, 358 about 19, 312, 358 creating 313 deleting 317 Ethernet switching mode 72 about 72 events 696, 698, 699 SEL policy 696 system event log 696, 698, 699 backing up 699 clearing 699 copying 698 printing 699 refreshing 699 viewing 696 exiting 54 expiration, accounts 160 explicit assignment 430, 434, 435 exporting 619, 621, 622 backup 622 backup types 619 configuration 619 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 IN-5 Index exporting (continued) user role 621 external applications 59 F fabric 108 port channels 108 fabric failover 318 fabric interconnects 46, 65, 66, 67, 69, 71, 72, 73, 74, 75, 76, 86, 87, 88, 89, 196, 202, 209, 219, 220, 221, 247, 248, 252, 253, 255, 256, 334, 341, 631, 633, 634, 636, 647 admin password recover 634, 636 admin password recovery 633 available space 209 changing 75 subnets 75 virtual IP address 75 changing ports 86 determining leadership role 76, 634 disabling ports 88 enabling ports 87 enabling standalone for cluster 72 Ethernet switching mode 72 failover 66 FC uplink trunking 334, 341 Fibre Channel switching mode 74 high availability 46 high availability status 202 host ID 248 impact of firmware upgrade 196 initial setup 65, 66, 67, 69, 71 about 65 first 69 management port 66 second 71 setup mode 66 standalone 67 licenses 247, 252, 253, 255, 256 clearing 256 expiry date 256 grace period 255 installing 252 viewing 253 mode 73, 74 monitoring 647 overall status 202 ports 255 grace period 255 restoring configuration 631 system configuration type 66 unconfiguring ports 89 fabric interconnects (continued) updating UCS Manager 219 upgrading firmware 219, 220, 221 verifying firmware 634 fabric port channels 110 member ports 110 deleting 110 viewing 110 fabric ports 110 port channels 110 member ports, deleting 110 fault collection policy 28, 701, 702 about 28, 701 configuring 702 Fault Summary area 48 faults 28, 678, 701, 702, 703, 704 Call Home severity levels 678 collection policy 28, 701, 702 Core File Exporter 703, 704 lifecycle 28, 701 FC end-host mode 334 VSAN ID restrictions 334 FC switch mode 334 VSAN ID restrictions 334 FC uplinks 334, 341 trunking 334, 341 about 334 disabling 341 enabling 341 FCoE 11 FCoE storage ports, configuring 94 FCoE VLAN ID 340 changing 340 feature 247 licenses 247 features 38 opt-in 38 stateless computing 38 Fibre Channel 11, 74, 77, 82, 83, 84, 94, 95, 104, 105, 106, 107 beacon LEDs 84 link-level flow control 11 over Ethernet 11 port channels 104, 105, 106, 107 adding ports 106 deleting 107 disabling 106 modifying 106 removing ports 106 port mode 82, 83 priority flow control 11 storage ports 94, 95 switching mode 74 uplink ports 77 Cisco UCS Manager GUI Configuration Guide, Release 2.0 IN-6 OL-25712-04 Index Fibre Channel adapter policies 19, 312, 358, 359, 364 about 19, 312, 358 creating 359 deleting 364 Fibre Channel switching 95 default zoning 95 Fibre Channel switching mode 74 about 74 Fibre Channel system class 37, 298 fields, acceptable range 60 filtering tables 51 finding acceptable range 60 firmware 21, 22, 183, 184, 185, 186, 187, 188, 190, 192, 193, 194, 195, 196, 197, 198, 199, 204, 206, 207, 208, 209, 210, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 226, 227, 228, 230, 235, 634 about 183 activating adapters 213 activating BIOS 214 activating board controller 218 activating CIMC 215 activating IOM 217 bundles 184 canceling image download 208 deleting images 210 deleting packages 209 direct upgrade 194 downgrades 199 downloading packages 206, 207 fabric interconnect 634 guidelines 187, 188, 190 host package 21, 197, 222, 227 host packages 226 image contents 209 image headers 185 images 185 management 186 management extensions 235 management package 22, 198, 223, 228 management packages 228 obtaining packages 204 outage impacts 196 prerequisites 199 service profiles 197 updating 210 updating adapters 212 updating BIOS 213 updating CIMC 215 updating IOM 216 updating UCS Manager 219 upgrade order 192, 193 upgrade stages 195, 198 upgrades 187 upgrading fabric interconnects 219, 220, 221 verifying 230 flexibility 10 flow control 11 link-level 11 priority 11 flow control policy 29, 38, 86, 304, 305 about 29, 38, 304 creating 304 deleting 305 uplink Ethernet ports 86 full state 619 G global cap policy 20, 564, 565 configuring 565 gold system class 37, 298 graceful shutdown 589, 603 group maps 141 LDAP 141 creating 141 deleting 141 GUI 47, 48, 50, 51, 53, 54, 57, 61 about 47 copying XML 61 customizing tables 51 Fault Summary area 48 hybrid display 53 logging in, HTTP 54 logging in, HTTPS 53 logging out 54 Navigation pane 48 session properties 57 status bar 50 toolbar 50 Work pane 50 GUI Inactivity Timeout 57 guidelines 34, 36, 160, 162, 187, 188, 190, 322, 334, 407, 408, 471, 489, 642 deferred deployment 471 disjoint L2 networks 322 firmware upgrades 187, 188, 190 local disk configuration policy 407, 408 named VSANs 334 oversubscription 34 passwords 162 pinning 36 service profiles 489 traffic monitoring 642 usernames 160 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 IN-7 Index H hard reset 589, 603 blade servers 589 rack-mount servers 603 hardware based service profiles 517 hardware-based service profiles 14, 488 hardware, stateless 38 headers, images 185 high availability 10, 46, 66, 69, 71, 202 about 46 fabric interconnect failover 66 initial setup 69, 71 verifying status 202 high availability configuration 46 about 46 history, passwords 178 host firmware package 21, 197, 222 about 21, 197, 222 host firmware packages 226, 227, 229 adding to service profile 229 creating 226 updating 227 host ID, obtaining 248 host port channels 108 viewing 108 HTTP 54, 55, 115, 174 configuring 115 logging in 54 web session limits 55, 174 HTTPS 53, 55, 116, 117, 118, 119, 174 certificate request 117 configuring 119 creating key ring 116 importing certificate 119 logging in 53 trusted point 118 web session limits 55, 174 hybrid display 53 I I/O module 617 management 617 I/O modules 203, 216, 217, 617, 654 activating firmware 217 monitoring 654 POST results 617 resetting 617 updating firmware 216 verifying status 203 IEEE 802.1Qbh 41 IEEE 802.3x link-level flow control 11 images 183, 184, 185, 204, 206, 207, 209, 210 bundle 184 contents 185, 209 deleting 210 downloading 206, 207 headers 185 obtaining 204 packages, deleting with 209 implicit assignment 430 import operations 626, 629, 630 creating 626 deleting 630 modifying 630 running 629 importing 621, 626, 630 about 621 creating operations 626 deleting operation 630 modifying operations 630 restore methods 621 user role 621 informs 122 about 122 inheritance, servers 26, 420 inherited values 14, 488 initial setup 65, 66, 67, 69, 71 about 65 cluster configuration 69, 71 management port IP address 66 setup mode 66 standalone configuration 67 initial templates 15, 488 initiators 348, 349, 352, 353 WWNN 348, 349 WWPN 352, 353 Intel Directed I/O, BIOS settings 390 interface cards, See adapters Internal Fabric Manager 52, 111, 112 about 52, 111 configuring ports 111 disabling ports 112 enabling ports 112 launching 111 unconfiguring ports 112 IOM 203, 216, 217, 617, 654 activating firmware 217 monitoring 654 POST results 617 updating firmware 216 verifying status 203 IP 379 pools 379 IP addresses 33, 66, 373, 377 CIMC 373 Cisco UCS Manager GUI Configuration Guide, Release 2.0 IN-8 OL-25712-04 Index IP addresses (continued) management IP pool 33, 377 management port 66 IP pools 33, 377, 378, 450 creating IP address block 378 creating iSCSI initiator address block 450 management 33, 377 IPMI access profiles 21, 405, 406 about 21, 405 creating 405 deleting 406 IQN pools 461, 463, 464 about 461 adding a block 463 creating 461 deleting 464 deleting a block 463 iSCSI 450 authentication profile 450 deleting 450 iSCSI adapter policies 447, 449 creating 447 deleting 449 iSCSI boot 443, 444, 446, 449 authentication profile 449 configuring 446 high-level tasks 446 overview 443 prerequisites 444 iSCSI boot parameters 454, 458 modifying 458 setting 454 iSCSI boot policies 451 creating 451 iSCSI boot process 444 iSCSI initiator interface 454, 458 modifying 458 setting 454 iSCSI initiator IP addresses 451 deleting pools 451 iSCSI initiator pools 451 deleting 451 iSCSI target interface 454, 458 modifying 458 setting 454 iSCSI vNIC 452 creating for service profile 452 iSCSI vNICs 454 deleting from service profiles 454 isolated VLAN 288 issuing an NMI 597, 610 blade servers 597 rack-mount servers 610 K key ring 115, 116, 117, 118, 119, 121 about 115 certificate request 117 creating 116 deleting 121 importing certificate 119 trusted point 118 KVM console 611, 615 about 611 Launch Manager 615 starting from server 615 starting from service profile 615 KVM Console 373 IP address 373 KVM Launch Manager 611, 615 L L2 networks, disjoint 321 LAN 27, 52, 263, 270, 271, 274, 277, 278, 280, 284, 293, 294, 295, 296, 307, 321, 451 disjoint L2 networks 321 iSCSI initiator pools 451 MAC pools 295, 296 named VLANs 271, 274, 280, 284 creating 271, 280 deleting 274, 284 pin groups 270, 271, 293, 294 creating 270, 293 deleting 271, 294 PVLANs 278 uplinks manager 52, 263 VLANs 277 vNIC policy 27, 307 LAN boot 465 about 465 LAN pin groups 270, 271, 293, 294 creating 270, 293 deleting 271, 294 LAN Uplinks Manager 52, 263, 264, 265, 266, 267, 268, 269, 270, 271, 274 about 52, 263 changing Ethernet switching mode 264 configuring ports 264 disabling server ports 266 disabling uplinkEthernet ports 267 enabling server ports 265 enabling uplink Ethernet ports 266 launching 264 named VLANs 271, 274 creating 271 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 IN-9 Index LAN Uplinks Manager (continued) named VLANs (continued) deleting 274 pin groups 270, 271 creating 270 deleting 271 port channels 267, 268, 269, 270 adding ports 269 creating 267 deleting 270 disabling 269 enabling 268 removing ports 270 system classes, configuring 274 unconfiguring server ports 266 unconfiguring uplink Ethernet ports 267 lanes, virtual 37, 297 Launch Manager, KVM 611, 615 launching 53, 54, 111, 264 GUI, HTTP 54 GUI, HTTPS 53 Internal Fabric Manager 111 LAN Uplinks Manager 264 LDAP 141, 147 group maps 141 creating 141 deleting 141 provider groups 147 creating 147 deleting 147 LDAP group mapping 140 LDAP group rule 134 LDAP provider 131, 132, 134, 135, 140, 141, 147 about 131 configuring properties 134 creating 135 deleting 140 group maps 141 creating 141 deleting 141 groups 147 creating 147 deleting 147 user attribute 132 LED locator 582, 594, 607 blade servers 594 chassis 582 rack-mount servers 607 LEDs, beacon 84 licenses 247, 248, 249, 250, 251, 252, 253, 255, 256 about 247 clearing 256 downloading 250, 251 expiry date 256 licenses (continued) grace period 255 installing 252 obtaining 249 obtaining host ID 248 uninstalling 256 viewing 253 lifecycle, faults 28, 701 link-level flow control 11 local disk boot 465, 466 about 465 configuring 466 local disk configuration policy 22, 407, 408, 410, 412, 413 about 22, 407 changing 412 creating 410 deleting 413 guidelines 407 RAID configuration 408 locales 166, 169, 170, 171, 175 about 166 assigning organizations 170 changing for users 175 creating 169 deleting 171 deleting organizations 170 locally authenticated users 160, 161, 171, 176, 177, 179, 180 accounts 160 change interval 179 clearing password history 177 creating 171 deleting 177 disabling 176 enabling 176 no change interval 179 password history count 180 password profile 177 reserved words for accounts 161 locating 582 chassis 582 log, system 704 log, system event 695 about 695 logging in 53, 54, 56, 57 banner 56, 57 HTTP 54 HTTPS 53 logging out 54 logical configuration 619 logs 57, 696 Cisco UCS Manager GUI 57 system event 696 Cisco UCS Manager GUI Configuration Guide, Release 2.0 IN-10 OL-25712-04 Index M MAC address table 245 aging time, about 245 configuring aging time 245 MAC addresses 31, 295, 296 creating pools 295 deleting pools 296 pools 31, 295 MAC pools 295, 296 creating 295 deleting 296 MAC sync 66 main, BIOS settings 382 maintenance policies 29, 470, 472, 482, 484 about 29, 470 creating 482 deleting 484 schedules 472, 482 management 577, 585, 599, 617 blade servers 585 chassis 577 I/O modules 617 rack-mount servers 599 management extensions 235, 236 about 235 activating 236 management firmware pack 228 updating 228 management firmware package 22, 198, 223 about 22, 198, 223 management firmware packages 228, 229 adding to service profile 229 creating 228 management interfaces monitoring policy 23, 655, 656 about 23, 655 configuring 656 management IP addresses 373 management IP pool 374, 376 blade servers 374 rack servers 376 management IP pools 33, 377, 378, 379, 450 about 33, 377 creating IP address block 378 creating iSCSI initiator IP address block 450 deleting IP address block 379 iSCSI initiator 450 IP address pools 450 management port IP address 66 manual blade-level power capping 570 merging configuration 621 messages, system inventory 684, 693 mobility 38 mode 66, 72, 73, 74, 264 end-host 72, 73, 74, 264 Ethernet switching 72 Fibre Channel switching 74 setup 66 switching 73, 74, 264 monitoring 180, 647, 648, 650, 652, 654, 658, 659, 660 blade servers 650 chassis 648 disk drive 658, 659 disk drives 659, 660 fabric interconnects 647 I/O modules 654 rack-mount servers 652 user sessions 180 multi-tenancy 39, 40, 155, 156, 157, 158 about 39 name resolution 156 opt-in 40 opt-out 40 organizations 155, 157, 158 creating 157, 158 deleting 158 multiple authentication systems 146 mutual inclusion 321 N name resolution 156, 237 named VLANs 271, 274, 277, 280, 284 about 277 creating 271, 280 deleting 274, 284 named VSANs 96, 97, 333, 334, 335, 339, 341 about 333 creating 335 deleting 339 disabling default zoning 97 enabling default zoning 96 FC uplink trunking 334, 341 ID range restrictions 334 named VSANS 340 FCoE VLAN ID 340 NAS ports, configuring 94 NAS ports, See appliance ports 92 Navigation pane 48 network 12, 96, 97, 271, 274, 277, 278, 280, 284, 333, 335, 337, 339 connectivity 12 creating 335, 337 named VLANs 271, 274, 277, 280, 284 creating 271, 280 deleting 274, 284 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 IN-11 Index network (continued) named VSANs 96, 97, 333, 335, 337, 339 deleting 339 disabling default zoning 97 enabling default zoning 96 private VLANs 278 network control policy 23, 317, 318, 320 creating 318 deleting 320 networks, disjoint L2 321 NIC adapters 41 virtualization 41 NMI 597, 610 blade servers 597 rack-mount servers 610 noAuthNoPriv 122 NTP servers 575, 576 about 575 adding 576 deleting 576 O obtaining 204, 233 capability catalog updates 233 firmware image bundles 204 occurrences 470, 477, 479, 481 one time 470, 477, 481 about 470 creating 477 deleting 481 recurring 470, 479, 481 about 470 creating 479 deleting 481 one time occurrences 470, 477, 481 about 470 creating 477 deleting 481 operating system installation 611 KVM console 611 operations 622, 625, 626, 630 backup 622, 625, 626 import 626, 630 operations, confirming 58 opt-in 38, 39, 40 about 38 multi-tenancy 40 stateless computing 39 opt-out 38, 39, 40 multi-tenancy 40 stateless computing 39 organizations 39, 155, 156, 157, 158, 166, 169, 170, 171 about 155 adding to locales 170 creating 157, 158 creating locales 169 deleting 158 deleting fromthe locales 170 deleting locales 171 locales 166 multi-tenancy 39 name resolution 156 OS installation 611 KVM console 611 outage impacts 196 Cisco UCS Manager 196 fabric interconnects 196 firmware upgrade 196 overriding 489 server identity 489 overriding server identity 13, 487, 490 oversubscription 33, 34 about 33 considerations 33 guidelines 34 overview 9 P packages 204, 206, 207, 226, 227, 228, 229 adding to service profiles 229 downloading 206, 207 host firmware 226, 227 management firmware 228 obtaining 204 packs 21, 22, 197, 198, 222, 223, 228 host firmware 21, 197, 222 management firmware 22, 198, 223, 228 pane 48, 50 Navigation 48 Work 50 password profile 177, 179, 180 about 177 change interval 179 clearing password history 177 no change interval 179 password history count 180 passwords 174, 178 change interval 178 history count 178 strength check 174 passwords, guidelines 162 passwords, recovering admin 633, 634, 636 Cisco UCS Manager GUI Configuration Guide, Release 2.0 IN-12 OL-25712-04 Index PCI configuration, BIOS settings 395 pending activities 471, 484, 485, 486 about 471 deploying 484, 485, 486 viewing 484 persistent binding, clearing 560 PFC 11 pin groups 35, 270, 271, 293, 294, 343, 344 about 35 LAN 270, 271, 293, 294 SAN 343, 344 pinning 35, 36, 323 about 35 disjoint L2 networks 323 guidelines 36 servers to server ports 35 PKI 115 platinum system class 37, 298 polices 60 where used 60 policies 15, 16, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 38, 153, 154, 197, 198, 222, 223, 226, 227, 228, 239, 242, 244, 301, 303, 304, 305, 307, 312, 317, 318, 320, 355, 358, 402, 403, 405, 406, 407, 410, 412, 413, 414, 415, 416, 417, 418, 419, 420, 421, 422, 423, 424, 428, 429, 439, 440, 447, 449, 451, 467, 470, 482, 564, 565, 569, 570, 655, 656, 663, 664, 666, 668, 669, 688, 689, 690, 696, 701, 702 about 15 autoconfiguration 25, 417, 418 BIOS 402, 403 boot 15, 439, 440, 467 Call Home 688, 689, 690 chassis discovery 16, 239, 242 dynamic vNIC connection 19 about 19 Ethernet 19, 312, 358 fault collection 28, 701, 702 Fibre Channel adapter 19, 312, 358 flow control 29, 38, 304, 305 global cap 565 global cap policy 20, 564 host firmware 21, 197, 222, 226, 227 IPMI access 21, 405, 406 iSCSI adapter 447, 449 iSCSI boot 451 local disk configuration 22, 407, 410, 412, 413 maintenance 29, 470, 482 management firmware 22, 198, 223, 228 management interfaces monitoring 23, 655, 656 network control 23, 317, 318, 320 power 24, 564 power control 24, 569, 570 PSU 24, 564 QoS 25, 38, 301, 303 rack server discovery 25, 244 policies (continued) role for remote users 153, 154 scrub 29, 413, 414, 415 SEL 696 serial over LAN 30, 415, 416 about 30, 415 creating 415 deleting 416 server discovery 25, 419, 420 server inheritance 26, 420, 421 about 26, 420 creating 420 deleting 421 server pool 26, 422, 423 server pool qualification 26, 423 server pool qualifications 424, 428 statistics collection 30, 663, 664 threshold 30, 666, 668, 669 vHBA 27, 355 VM lifecycle 27 vNIC 27, 307 vNIC/vHBA placement 28, 429 policy-driven chassis group power capping 565 pools 31, 32, 33, 61, 295, 296, 345, 346, 350, 367, 368, 369, 370, 371, 377, 378, 379, 450, 451, 461, 464 about 31 IQN 461, 464 iSCSI initiator 451 iSCSI initiator IP 450 MAC 31, 295, 296 management IP 33, 377, 378, 379 servers 31, 367, 368, 369 UUID suffixes 32, 369, 370, 371 where used 61 WWN 32, 345 WWNN 346 WWPN 350 port channels 97, 98, 99, 100, 103, 104, 105, 106, 107, 108, 110, 267, 268, 269, 270, 325, 327, 328, 329 adapter 108 adding ports 269 appliance 100, 103, 104 adding ports 103 creating 100 deleting 104 disabling 103 enabling 103 removing ports 103 assigning to VLANs 325, 327 creating 267 deleting 270 disabling 269 enabling 268 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 IN-13 Index port channels (continued) Ethernet 99, 100 adding ports 99 deleting 100 disabling 99 removing ports 99 fabric 108, 110 Fibre Channel 104, 105, 106, 107 adding ports 106 creating 104, 105 deleting 107 disabling 106 modifying 106 removing ports 106 removing from VLANs 328 removing ports 270 uplink Ethernet 97, 98, 99 creating 98 enabling 99 viewing VLAN assignment 329 port modes 78, 81 about 78 impact on data traffic 81 port types 79 ports 35, 66, 77, 78, 80, 82, 83, 84, 85, 86, 87, 88, 89, 92, 94, 95, 97, 104, 108, 111, 112, 247, 264, 265, 266, 267, 270, 271, 291, 293, 294, 318, 325, 327, 328, 329, 343, 344, 670, 671, 672 appliance 89 appliance ports 89, 92 appliance, NAS 77 assigning to VLANs 325, 327 beacon LEDs 84 changing 86 changing uplink Ethernet 86 disabling 88, 266, 267 enabling 87, 265, 266 Ethernet server port 671 fabric interconnect 77 FCoE storage ports 94 Fibre Channel port 672 Fibre Channel storage ports 94, 95 licenses 247 MAC security 318 management 66 mode 82, 83 pin groups 270, 271, 293, 294, 343, 344 pinning server traffic 35 port channels 97, 104, 108 Fibre Channel 104 removing from VLANs 328 server 77, 85, 111, 112, 264 unconfiguring 89, 266, 267 unified 78, 80 uplink 77 ports (continued) uplink Ethernet 85, 264, 670 viewing VLAN assignment 329 VLAN, count 291 ports, 110 fabric port channels 110 member ports, deleting 110 POST 582, 596, 610, 617 blade servers 596 rack-mount servers 610 viewing for chassis 582 viewing for I/O modules 617 power cap 572 viewing 572 power capping 565, 570 manual blade-level 570 policy-driven chassis group 565 power control policy 24, 569, 570 creating 569 deleting 570 power groups 566, 568 adding chassis 568 creating 566 deleting 568 removing chassis 568 power management 24, 563, 566, 568, 569, 570 policies 24, 569 power control 24, 569 power control policy 569, 570 creating 569 deleting 570 power groups 566, 568 adding chassis 568 creating 566 deleting 568 removing chassis 568 rack server 563 Power on Self-Test 582, 596, 610, 617 blade servers 596 rack-mount servers 610 viewing for chassis 582 viewing for I/O modules 617 power policy 24, 564 about 24, 564 configuring 564 power state, synchronizing 590, 604 powercycling 589, 603 rack-mount servers 589, 603 pre-login banner 56, 57 creating 56 deleting 57 modifying 56 primary authentication 131, 135, 140, 142, 144, 145, 146, 151, 152 LDAP provider 135, 140 Cisco UCS Manager GUI Configuration Guide, Release 2.0 IN-14 OL-25712-04 Index primary authentication (continued) RADIUS provider 142, 144 remote 131 selecting console 151 selecting default 152 TACACS provider 146 TACACS+ provider 145 primary VLAN 285 printing system event log 699 priority flow control 11 private VLANs 278, 285, 288 about 278 creating primary 285 creating secondary 288 privileges 164, 168 about 164 adding 168 removing 168 processor, BIOS settings 384 profiles 12, 177, 685 Call Home alert groups 685 password 177 properties 57, 58, 59, 75 confirmation messages 58 external applications 59 fabric interconnects 75 session 57 visual enhancements 59 provider 135, 140, 142, 144, 145, 146 LDAP 135, 140 creating 135 RADIUS 142, 144 TACACS 146 TACACS+ 145 provider groups 147, 148, 149, 150 authentication domains 150 LDAP 147 creating 147 deleting 147 RADIUS 148 creating 148 deleting 148 TACACS+ 149 creating 149 deleting 149 provider, capability catalog 230, 233 PSU policy 24, 564 PVLANs 278, 285, 288 about 278 creating primary 285 creating secondary 288 Q QoS policies 25, 38, 301, 303 about 25, 38, 301 creating 301 deleting 303 quality of service 25, 29, 37, 38, 274, 297, 298, 300, 301, 303, 304 about 37, 297 flow control policies 29, 38, 304 policies 25, 38, 301, 303 system classes 37, 274, 297, 298, 300 configuring 298 disabling 300 enabling 300 LAN Uplinks Manager 274 R rack server discovery policy 25, 244 about 25, 244 configuring 244 rack server power management 563 rack-mount servers 25, 193, 244, 489, 517, 542, 599, 600, 601, 602, 603, 605, 607, 608, 609, 610, 652 booting 600 decommissioning 605 determining boot order 601 discovery policy 25, 244 guidelines for service profiles 489 hardware based service profiles 517 integrating 193 issuing an NMI 610 locator LED 607 managing 599 monitoring 652 POST results 610 power cycling 603 reacknowledging 605 recovering BIOS 609 removing 607 from database 607 resetting 608 CIMC 608 CMOS 608 shutting down 602 template based service profiles 542 RADIUS 148 provider groups 148 creating 148 deleting 148 RADIUS provider 131, 132, 142, 144, 148 about 131 configuring properties 142 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 IN-15 Index RADIUS provider (continued) creating 142 deleting 144 groups 148 creating 148 deleting 148 user attribute 132 RAID configurations, local disk configuration policies 408 range restrictions, VSAN IDs 334 range, acceptable 60 RAS memory, BIOS settings 392 reacknowledging 591, 593, 605 blade servers 591 rack-mount servers 605 server slots 593 rebooting 589, 603 blade servers 589 rack-mount servers 603 recommendations 620 backup operations 620 recommissioning 593, 606 blade servers 593 rack-mount servers 606 recommissioning, chassis 579, 580 Reconnection Interval 57 recovering admin password 633, 634, 636 recovering BIOS 595, 609 blade servers 595 rack-mount servers 609 recurring occurrences 470, 479, 481 about 470 creating 479 deleting 481 refreshing system event log 699 registration, Smart Call Home 694 remote authentication 132 user accounts 132 user roles 132 remotely authenticated users 160 accounts 160 removing 270, 579, 591, 594, 607 blade server from configuration 594 chassis 579 ports from port channel 270 rack-mount server from configuration 607 server from chassis 591 removing chassis, guidelines 577 removing rack-mount servers 600 removing servers 586 renumbering 581, 606 blade servers 581 chassis 581 rack-mount servers 606 replacing configuration 621 reserved words 161, 164 custom roles 164 locally authenticated user accounts 161 resetting 589, 594, 595, 603, 608, 617 blade servers 589 CIMC 595, 608 blade servers 595 rack-mount servers 608 CMOS 594, 608 IOM 617 rack-mount servers 603 resolution, name 237 restoring 621, 626, 631 about 621 configuration 631 import operations 626 user role 621 role policy for remote users 153, 154 about 153 configuring 154 role-based access control 159 roles 162, 163, 164, 167, 168, 175, 621 about 162 adding privileges 168 backing up 621 changing for users 175 creating 167 default 163 deleting 168 privileges 164 removing privileges 168 root organization 157 RSA 115 running 625, 629 backup operation 625 import operation 629 S SAN 27, 96, 97, 333, 335, 337, 339, 343, 344, 355 named VSANs 96, 97, 335, 339 creating 335 deleting 339 disabling default zoning 97 enabling default zoning 96 pin groups 343, 344 storage VSANs 337 creating 337 vHBA policy 27, 355 VSANs 333 SAN boot 441 about 441 Cisco UCS Manager GUI Configuration Guide, Release 2.0 IN-16 OL-25712-04 Index SAN boot (continued) configuring 441 SAN pin groups 343, 344 creating 343 deleting 344 scalability 10 schedules 470, 472, 477, 479, 481, 482 about 470 creating 472 deleting 482 one time occurrences 477, 481 creating 477 deleting 481 recurring occurrences 479, 481 creating 479 deleting 481 scrub policy 29, 413, 414, 415 about 29, 413 creating 414 deleting 415 secondary VLAN 288 SEL 695 about 695 SEL policy 696 configuring 696 selecting 151, 152 console authentication service 151 default authentication service 152 selective exclusion 321 serial number, obtaining 248 serial over LAN policy 30, 415, 416 about 30, 415 creating 415 deleting 416 serial port, BIOS settings 394 server 571 setting power blade-level power cap 571 server autoconfiguration policy 25, 417, 418 about 25, 417 creating 417 deleting 418 server discovery policy 25, 419, 420 about 25, 419 creating 419 deleting 420 server inheritance policy 26, 420, 421 about 26, 420 creating 420 deleting 421 server management 585, 599 server management, BIOS settings 397 server pool policy 26, 422, 423 about 26, 422 creating 422 server pool policy (continued) deleting 423 server pool policy qualification 26, 423 about 26, 423 server pool policy qualifications 424, 428 creating 424 deleting 428 deleting qualifications 428 server pools 367, 368, 369, 544, 545, 546, 547 adding servers 369 associating service profile 544 associating service profile templates 546 creating 367 deleting 368 disassociating service profile 545 disassociating service profile templates 547 removing servers 369 server ports 52, 77, 85, 111, 112, 264, 265, 266 about 77 configuring 85, 111, 264 Equipment tab 85 Internal Fabric Manager 111 LAN Uplink Manager 264 disabling 112, 266 Internal Fabric Manager 112 enabling 112, 265 Internal Fabric Manager 112 Internal Fabric Manager 52, 111 unconfiguring 112, 266 Internal Fabric Manager 112 server virtualization 10 servers 12, 13, 15, 21, 22, 25, 26, 31, 35, 38, 39, 193, 203, 237, 238, 367, 368, 369, 374, 375, 376, 381, 382, 384, 390, 392, 394, 395, 396, 397, 402, 403, 404, 405, 406, 407, 410, 412, 413, 419, 420, 422, 423, 424, 428, 439, 440, 447, 449, 451, 467, 469, 487, 489, 490, 513, 517, 518, 519, 541, 542, 543, 544, 545, 547, 549, 562, 585, 586, 587, 588, 589, 590, 591, 592, 593, 594, 595, 596, 597, 599, 600, 601, 602, 603, 604, 605, 606, 607, 608, 609, 610, 615, 650, 652, 658, 659, 660, 666, 668, 669, 696 actual BIOS settings 404 adding previously unsupported 193 adding to pools 369 associating with service profiles 544 BIOS defaults 402, 404 BIOS policies 402 BIOS policy 403 BIOS settings 381, 382, 384, 390, 392, 394, 395, 396, 397 blade 374, 585, 586 booting 586 management IP pool 374 static Management IP 374 boot order 587, 601 boot policies 15, 439, 440, 467 booting 587, 601 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 IN-17 Index servers (continued) changing UUID 547 cloning service profiles 544 configuration 12 creating service profile templates 518, 519 creating service profiles 489, 490, 513 decommissioning 592, 605 disassociating from service profiles 545 discovery policy 25, 419, 420 disk drive monitoring 658, 659 disk drive status 659, 660 disk drive support 658 DNS 237, 238 hard reset 589, 603 hardware based service profiles 517 inheritance policy 26, 420 IPMI access 21, 405, 406 iSCSI adapter policies 447, 449 iSCSI boot policies 451 issuing an NMI 597, 610 KVM console 615 local disk configuration 22, 407, 410, 412, 413 locator LED 594, 607 monitoring 650, 652 multi-tenancy 39 pinning 35 pool policy 26, 422, 423 pool qualifications 26, 423, 424, 428 pools 31, 367, 368 POST results 596, 610 rack 375, 376 management IP pool 376 static Management IP 375 rack-mount 599, 600 booting 600 reacknowledging 591, 605 reacknowledging slots 593 recommissioning 593, 606 recovering BIOS 609 removing 591, 594, 607 from chassis 591 from database 594, 607 removing from pools 369 renumbering 606 resetting 594, 595, 608 CIMC 595, 608 CMOS 594, 608 resetting UUID 549 SEL policy 696 service profiles 12, 13, 469, 487, 562 service profiles from templates 541 shutting down 588, 602 stateless 38 statistics threshold policies 666, 668, 669 servers (continued) system event log 696 template based service profiles 541, 542 template from service profiles 543 unexpected power changes 590, 604 verifying status 203 service profile 452 iSCSI vNIC 452 creating 452 service profile template wizard 518, 519, 520, 524, 530, 532, 535, 537, 539 opening 518 page 1, identity 519 page 2, storage 520 page 3, networking 524 page 4, vNIC/vHBA placement 530 page 5, server boot order 532 page 6, maintenance policy 535 page 7, server assignment 537 page 8, policies 539 service profile templates 60, 61, 377, 518, 519, 520, 524, 530, 532, 535, 537, 539, 546, 547, 548, 561, 562 associating with server pool 546 binding service profiles 561 changing UUID 548 creating 518, 519, 520, 524, 530, 532, 537, 539 identity 519 networking 524 policies 539 server assignment 537 server boot order 532 vNIC/vHBA placement 530 creating with wizard 535 maintenance policy 535 disassociating from server pool 547 policies used by 60 pools used by 61 setting Management IP 377 unbinding service profiles 562 service profile wizard 489, 490, 491, 496, 502, 504, 507, 509, 511 opening 489 page 1, identity 490 page 2, storage 491 page 3, networking 496 page 4, vNIC/vHBA placement 502 page 5, server boot order 504 page 6, maintenance policy 507 page 7, server assignment 509 page 8, policies 511 service profiles 12, 13, 14, 15, 60, 61, 197, 229, 376, 454, 469, 487, 488, 489, 490, 491, 496, 502, 504, 507, 509, 511, 513, 517, 541, 542, 543, 544, 545, 547, 549, 550, 553, 555, 556, 559, 560, 561, 562, 587, 588, 590, 601, 602, 604, 615 about 12 Cisco UCS Manager GUI Configuration Guide, Release 2.0 IN-18 OL-25712-04 Index service profiles (continued) adding firmware packages 229 associating 544 binding to template 561 changing UUID 547 cloning 544 configuration 12 creating from template 541 creating hardware based 517 blade servers 517 rack-mount servers 517 creating template based 541, 542 blade servers 541 rack-mount servers 542 creating template from 543 creating with inherited values 513 creating with wizard 489, 490, 491, 496, 502, 504, 507, 509, 511 identity 490 maintenance policy 507 networking 496 policies 511 server assignment 509 server boot order 504 storage 491 vNIC/vHBA placement 502 deferring deployment 469 disassociating 545 firmware upgrades 197 guidelines 489 inherited values 14, 488 iSCSI vNICs 454 modifying boot order 550 network connectivity 12 override identity 13, 487 policies used by 60 pools used by 61 resetting MAC address 555 resetting UUID 549 resetting WWPN 560 servers 587, 588, 601, 602, 615 booting 587, 601 KVM console 615 shutting down 588, 602 setting Management IP 376 templates 15, 488 unbinding from template 562 unexpected power changes 590, 604 vHBAs 556, 559, 560, 561 vNICs 553, 556 session properties 57 sessions, users 180 setting 57, 58, 59, 73, 74, 264 confirmation messages 58 external application properties 59 setting (continued) session properties 57 switching mode 73, 74, 264 visual enhancement properties 59 setting up 69, 71 primary fabric interconnect 69 subordinate fabric interconnect 71 setup mode 66 severity levels, Call Home 678 shutdown, graceful 589, 603 shutting down 588, 602 blade servers 588 rack-mount servers 602 shutting down servers 588, 602 silver system class 37, 298 Smart Call Home 677, 678, 679, 690, 692, 693, 694 about 679 Cisco TAC-1 profile 692 configuring 690 considerations 677 registering 694 severity levels 678 system inventory messages 693 SNMP 121, 122, 124, 125, 126, 127, 128, 129 about 121 community 125 enabling 125 notifications 122 privileges 122 security levels 122 SNMPv3 users 128, 129 support 121, 124 traps 126, 127 creating 126 deleting 127 users 128, 129 creating 128 deleting 129 Version 3 security features 124 SNMPv3 124 security features 124 software 183 SPAN, See traffic monitoring SSH, properties 59 stages, firmware upgrades 195, 198 standalone configuration 67 starting 53, 54, 111, 264, 615 GUI 53, 54 Internal Fabric Manager 111 KVM console from server 615 KVM console from service profile 615 KVM Launch Manager 615 LAN Uplinks Manager 264 starting servers 586, 587, 600, 601 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 IN-19 Index stateless computing 38, 39 about 38 opt-in 39 opt-out 39 statelessness 38 statistics 30, 666, 668, 669, 670, 671, 672 threshold policies 30, 666, 668, 669, 670, 671, 672 Ethernet server port 671 Fibre Channel port 672 server and server component 666, 668, 669 uplink Ethernet port 670 statistics collection policies 30, 663, 664 about 30, 663 modifying 664 status 202, 203, 204 adapters 204 fabric interconnects 202 I/O modules 203 servers 203 status bar 50 stopping servers 588, 602 storage VSANs 337, 339 creating 337 deleting 339 storage VSANS 340 FCoE VLAN ID 340 subnets, changing 75 subordinate fabric interconnect 71 initial setup 71 suborganization 158 supported tasks 44 switching mode 73, 74, 264 Ethernet 73 Fibre Channel 74 syslog 704 system classes 37, 297, 298, 300 best effort 37, 298 bronze 37, 298 configuring 298 disabling 300 enabling 300 Fibre Channel 37, 298 gold 37, 298 platinum 37, 298 silver 37, 298 system configuration 619 system event log 695 about 695 system inventory messages 684, 693 configuring 684 sending 684 system management 577, 585, 599, 617 blade servers 585 chassis 577 system management (continued) I/O module 617 rack-mount servers 599 T tables 51 customizing 51 customizing tables 51 filtering 51 TACACS provider 144, 146 configuring properties 144 deleting 146 TACACS+ 149 provider groups 149 creating 149 deleting 149 TACACS+ provider 131, 132, 145, 149 about 131 creating 145 groups 149 creating 149 deleting 149 user attribute 132 tasks 44, 46 supported 44 unsupported 46 Telnet, enabling 129 template based service profiles 541, 542 templates 15, 488, 541, 543 creating from service profile 543 creating service profiles 541 service profiles 15, 488 TFTP Core Exporter 703, 704 threshold policies 30, 666, 668, 669, 670, 671, 672 about 30, 666 Ethernet server port 671 adding threshold class 671 Fibre Channel port 672 adding threshold class 672 server and server component 666, 668, 669 adding threshold class 668 creating 666 deleting 669 uplink Ethernet port 670 adding threshold class 670 time zones 575 about 575 setting 575 toolbar 50 traffic management 33, 34, 37, 297 oversubscription 33, 34 Cisco UCS Manager GUI Configuration Guide, Release 2.0 IN-20 OL-25712-04 Index traffic management (continued) quality of service 37, 297 system classes 37, 297 virtual lanes 37, 297 traffic monitoring 641, 642, 643, 644, 645, 646 about 641 activating a session 646 adding sources 645 deleting a session 646 Ethernet session 643 Fibre Channel session 644 guidelines 642 traps 122, 126, 127 about 122 creating 126 deleting 127 trunking 334, 341 Fibre Channel 334, 341 uplink 334, 341 trunking, named VSANs 334, 341 trusted points 115, 118, 121 about 115 creating 118 deleting 121 turning off 582 chassis locator LED 582 turning on 582 chassis locator LED 582 U UCS Manager 47 GUI 47 unbinding 312, 358, 562 service profiles 562 vHBAs 358 vNICs 312 unconfiguring 112 ports 112 unconfiguring ports 89, 266, 267 unexpected power changes, avoiding 590, 604 unified fabric 10, 11 about 10 Fibre Channel 11 unified ports 78, 79, 80, 81, 82, 83, 84 beacon LEDs 84 configuring mode 82, 83 guidelines 80 port modes 78, 81 port types 79 unified ports (continued) ports 80 unified 80 guidelines 80 unsupported tasks 46 updating 192, 193, 227, 228, 233, 234, 235, 469 capability catalog 233, 234, 235 firmware order 192, 193 host firmware package 227 management firmware policy 228 service profiles 469 updating firmware 210, 212, 213, 215, 216, 219 updating templates 15, 488 upgrading 187, 188, 190, 194, 195, 197, 198, 199, 230, 231 capability catalog 230, 231 firmware 187, 195, 198 firmware, direct 194 firmware, guidelines 187, 188, 190 firmware, service profiles 197 prerequisites 199 upgrading firmware 204, 206, 207, 209, 210, 212, 213, 215, 216, 219, 220, 221 adapters 212 BIOS 213 CIMC 215 downloading images 206, 207, 209 fabric interconnects 219, 220, 221 IOM 216 obtaining packages 204 UCS Manager 219 updating 210 uplink Ethernet ports 85, 86, 94, 264, 266, 267 configuring 85, 94, 264 Equipment tab 85 FCoE storage 94 LAN Uplink Manager 264 NAS 94 disabling 267 enabling 266 flow control policy 86 speed 86 unconfiguring 267 uplink Fibre Channel ports 95 restoring 95 uplink port channels 98, 99, 100, 267, 268, 269, 270 adding ports 269 creating 267 deleting 270 disabling 269 enabling 268 Ethernet 98, 99, 100 creating 98 deleting 100 disabling 99 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 IN-21 Index uplink port channels (continued) Ethernet (continued) enabling 99 removing ports 270 uplink ports 29, 38, 77, 85, 97, 270, 271, 293, 294, 304, 343, 344 about 77 Ethernet 85 flow control policies 29, 38, 304 pin groups 270, 271, 293, 294, 343, 344 creating 270, 293 deleting 271, 294 port channels 97 uplink Ethernet 97 uplink trunking 334, 341 Fibre Channel 334, 341 about 334 disabling 341 enabling 341 uplinks, Manager for LAN 52, 263 upstream disjoint L2 networks, See disjoint L2 networks USB, BIOS settings 394 user accounts 159, 160, 162, 171, 175, 176, 177, 179, 180 about 159, 162 changing locales 175 creating 171 deleting 177 disabling 176 enabling 176 password profile 177, 179, 180 username guidelines 160 web session limits 162 user attributes 132 LDAP 132 RADIUS 132 TACACS+ 132 user roles 162, 163, 164, 167, 168 about 162 adding privileges 168 creating 167 default 163 deleting 168 privileges 164 removing privileges 168 usernames, guidelines 160 users 55, 128, 129, 131, 132, 153, 154, 159, 160, 162, 163, 164, 166, 167, 168, 169, 170, 171, 174, 175, 176, 177, 179, 180, 633, 634, 636 access control 159 accounts 159, 162 adding privileges 168 authentication 131 creating accounts 171 creating roles 167 default roles 163 deleting local accounts 177 users (continued) deleting roles 168 disabling accounts 176 enabling accounts 176 guidelines 160 locales 166, 169, 170, 171, 175 about 166 adding organizations 170 changing 175 creating 169 deleting 171 deleting organizations 170 locally authenticated 160, 177, 179, 180 monitoring sessions 180 password strength check 174 privileges 164 recovering admin password 633, 634, 636 remote authentication 132 remote, role policy 153, 154 remotely authenticated 160 removing privileges 168 roles 162, 175 changing 175 SNMPv3 128, 129 web session limits 55, 162, 174 UUID 547, 548, 549 changing 547 changing in service profile template 548 resetting 549 UUID suffix pools 32, 369, 370, 371 about 32, 369 creating 370 deleting 371 V values, range 60 vCons 28, 429, 430, 434, 435 about 28, 429 adapter placement 430 vNIC/vHBA assignment 430, 434, 435 verifying firmware 230 vHBA SAN Connectivity policies 27, 355, 357, 358 about 27, 355 binding vHBAs 357 creating 355 deleting 357 unbinding vHBAs 358 vHBA templates 27, 355, 357, 358 about 27, 355 binding vHBAs 357 creating 355 Cisco UCS Manager GUI Configuration Guide, Release 2.0 IN-22 OL-25712-04 Index vHBA templates (continued) deleting 357 unbinding vHBAs 358 vHBAs 357, 358, 430, 435, 556, 559, 560, 561 assignment to vCon 430, 435 binding to vHBA template 357 changing WWPN 559 clearing persistent binding 560 creating for service profiles 556 deleting from service profiles 561 resetting WWPN 560 unbinding from vHBA template 358 VIC adapters 41 virtualization 41 viewing 572, 696 blade-level power cap 572 system event log 696 VIF status 652, 654 virtual IP address, changing 75 Virtual KVM console 612 virtual lanes 37, 297 virtual machines 40 virtual media boot 466 about 466 configuring 466 virtualization 27, 40, 41 about 40 converged network adapters 41 NIC adapters 41 VIC adapter 41 VM lifecycle policy 27 VM-FEX 41 about 41 visual enhancements 59 VLAN port limitations 279 VLANs 92, 271, 274, 277, 278, 280, 284, 285, 288, 291, 321, 322, 323, 324, 325, 327, 328, 329 appliance ports 92 assigning ports and port channels 327 creating for disjoint L2 networks 325 disjoint L2 networks 321, 322, 323, 324 named 271, 274, 277, 280, 284 about 277 creating 271, 280 deleting 274, 284 port count 291 private 278, 285, 288 about 278 creating primary 285 creating secondary 288 removing ports and port channels 328 viewing ports and port channels 329 VM lifecycle policy 27 about 27 VM-FEX 41 about 41 vNIC 27, 307 policy 27, 307 vNIC LAN Connectivity policies 27, 307, 311, 312 about 27, 307 binding vNICs 311 creating 307 deleting 311 unbinding vNICs 312 vNIC templates 27, 307, 311, 312 about 27, 307 binding vNICs 311 creating 307 deleting 311 unbinding vNICs 312 vNIC/vHBA placement policies 28, 429, 430, 433, 434 about 28, 429 creating 433 deleting 434 vCons 28, 429, 430 vNIC/vHBA assignment 430 vNICs 19, 311, 312, 430, 434, 452, 454, 553, 555, 556 assignment to vCon 430, 434 binding to vNIC template 311 creating for service profiles 553 deleting from service profiles 556 dynamic vNIC connection policy 19 iSCSI 452, 454 creating for service profile 452 deleting from service profiles 454 resetting MAC address 555 unbinding from vNIC template 312 VSANs 96, 97, 333, 334, 335, 337, 339 creating 335, 337 named 335 deleting 339 disabling default zoning 97 enabling default zoning 96 named 333, 334 storage 337 W web session limits 55, 162, 174 Work pane 50 WWN 346, 349, 350, 353 creating 346, 350 WWNN pools 346 WWPN pools 350 deleting 349, 353 WWNN pools 349 Cisco UCS Manager GUI Configuration Guide, Release 2.0 OL-25712-04 IN-23 Index WWN (continued) deleting (continued) WWPN pools 353 WWN block 347, 351 adding to WWNN pool 347 adding to WWPN pool 351 deleting from WWNN pool 347 deleting from WWPN pool 351 WWN pools 32, 345 about 32, 345 WWNN initiators 348, 349 adding to WWNN pool 348 deleting 349 WWNN pools 32, 345, 346, 347, 348, 349 about 32, 345 adding WWN block 347 adding WWNN initiator 348 creating 346 deleting 349 deleting WWN block 347 deleting WWNN initiator 349 WWPN initiators 352, 353 adding to WWPN pool 352 WWPN initiators (continued) deleting 353 WWPN pools 32, 345, 350, 351, 352, 353 about 32, 345 adding WWN block 351 adding WWPN initiator 352 creating 350 deleting 353 deleting WWN block 351 deleting WWPN initiator 353 X XML, copying 61 Z zoning 96, 97 disabling, default 97 enabling, default 96 Cisco UCS Manager GUI Configuration Guide, Release 2.0 IN-24 OL-25712-04
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.4 Linearized : No Modify Date : 2012:09:05 23:12:06 Concept : Keywords : Doc Type : Creator : Unknown Author : Unknown Create Date : 2012:09:05 23:12:06 Content Type : Date : 2011-09-15T14:12:21.000-07:00 Access Level : Guest,Customer,Partner Country : US Title : Cisco UCS Manager GUI Configuration Guide, Release 2.0 Description : Trapped : False Ia Path : Producer : XEP 4.9 build 20070312 Language : en Secondary Concept : Page Count : 768 Page Mode : UseOutlinesEXIF Metadata provided by EXIF.tools