Instruction/ maintenance manual of the product OL-25712-04 Cisco Systems
Go to page of 768
Cisco UCS Manager GUI Configuration Guide, Release 2.0 First Published: September 06, 201 1 Last Modified: September 04, 2012 Americas Headquarters Cisco Systems, Inc.
THE SPECIFICA TIONS AND INFORMA TION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL ST A TEMENTS, INFORMA TION, AND RECOMMENDA TIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURA TE BUT ARE PRESENTED WITHOUT W ARRANTY OF ANY KIND, EXPRESS OR IMPLIED.
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.
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 D.
UUID Suffix Pools 32 WWN Pools 32 Management IP Pool 33 T raffic Management 33 Oversubscription 33 Oversubscription Considerations 33 Guidelines for Estimating Oversubscription 34 Pinning 35 Pinning S.
Status Bar 50 T able 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 throu.
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 Switc.
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 Disabl.
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 .
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 Pr.
Organizations in a Multi-T enancy Environment 155 Hierarchical Name Resolution in a Multi-T enancy Environment 156 Creating an Organization under the Root Organization 157 Creating an Organization und.
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 C.
V erifying the Status of I/O Modules 203 V erifying the Status of Servers 203 V erifying the Status of Adapters on Servers in a Chassis 204 Downloading and Managing Firmware Packages 204 Obtaining Sof.
Adding Firmware Packages to an Existing Service Profile 229 V erifying Firmware V ersions on Components 230 Managing the Capability Catalog 230 Capability Catalog 230 Contents of the Capability Catalo.
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.
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.
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 Serv.
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.
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 CHAPT.
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 Ser.
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 C.
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.
Configuring a LAN Boot for a Boot Policy 465 Local Disk Boot 465 Configuring a Local Disk Boot for a Boot Policy 466 V irtual Media Boot 466 Configuring a V irtual Media Boot for a Boot Policy 466 Del.
Creating Service Profiles 489 Creating a Service Profile with the Expert W izard 489 Page 1: Identifying the Service Profile 490 Page 2: Configuring the Storage Options 491 Page 3: Configuring the Net.
Resetting the UUID Assigned to a Service Profile from a Pool in a Service Profile T emplate 549 Modifying the Boot Order in a Service Profile 550 Creating a vNIC for a Service Profile 553 Resetting th.
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.
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 .
Renumbering a Rack-Mount Server 606 Removing a Non-Existent Rack-Mount Server from the Configuration Database 607 T urning the Locator LED for a Rack-Mount Server On and Of f 607 Resetting the CMOS fo.
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 .
Support for Disk Drive Monitoring 658 Prerequisites for Disk Drive Monitoring 659 V iewing the Status of a Disk Drive 659 Interpreting the Status of a Monitored Disk Drive 660 CHAPTER 44 Configuring S.
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: C.
Cisco UCS Manager GUI Configuration Guide, Release 2.0 xxxii OL-25712-04 Contents.
Preface This preface includes the following sections: • Audience, page xxxiii • Conventions, page xxxiii • Related Cisco UCS Documentation, page xxxv • Documentation Feedback, page xxxv • Ob.
Indication Convention T erminal sessions and information that the system displays appear in courier font. courier font Elements in square brackets are optional. [ ] 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.
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 .
Cisco UCS Manager GUI Configuration Guide, Release 2.0 xxxvi OL-25712-04 Preface Obtaining Documentation and Submitting a Service Request.
P ART 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, p.
.
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.
T able 2: New Features and Significant Behavioral Changes in Cisco UCS, Release 2.0(2) Where Documented Description Feature iSCSI Boot, on page 443 Adds support for IQN pools in Cisco UCS domains configured for iSCSI boot.
Where Documented Description Feature iSCSI Boot, on page 443 iSCSI boot enables a server to boot its operating system from an iSCSI target machine located remotely over a network. iSCSI Boot Licenses, on page 247 Updated information for new UCS hardware.
Where Documented Description Feature This feature is now documented in the following installation guides: • Cisco UCS Manager Interface Car d Drivers for ESX Installation Guide • Cisco UCS Manager.
Where Documented Description Feature This feature is documented in the following configuration guides: • Cisco UCS Manager 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 UCS Manager GUI Configuration Guide, Release 2.0 8 OL-25712-04 New and Changed Information for this Release.
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.
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.
At the fabric interconnect, the server-facing Ethernet port receives the Ethernet and Fibre Channel traf fic. 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.
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.
Y ou do not need to configure these hardware components directly . Server Identity Management through Service Profiles Y ou can use the network and device identities burned into the server hardware at.
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. Y ou do not need to reconfigure any component or application on your network to begin using the new server .
Service Profile T emplates W ith 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.
• 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.
T able 4: Chassis Discovery Policy and Chassis Links Platform-Max Discovery Policy 8-Link Chassis Discovery Policy 4-Link Chassis Discovery Policy 2-Link Chassis Discovery Policy 1-Link Chassis Discov.
Platform-Max Discovery Policy 8-Link Chassis Discovery Policy 4-Link Chassis Discovery Policy 2-Link Chassis Discovery Policy 1-Link Chassis Discovery Policy Number of Links Wired for the Chassis 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.
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.
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 a.
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).
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 .
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.
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, release 1.
For more information about power supply redundancy , see Cisco UCS 5108 Server Chassis Har dwar e Installation Guide . Quality of Service Policy A quality of service (QoS) policy assigns a system class to the outgoing traf fic for a vNIC or vHBA. This system class determines the quality of service for that traffic.
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.
• Server inheritance policy • Server pool policy vHBA T emplate 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. Y ou need to include this policy in a service profile for it to take effect.
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.
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.
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.
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.
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.
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 . Y ou can configure service profiles and service profile templates to use IP addresses from the management IP pool.
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.
Network T ype The network type is only relevant to traf fic on uplink ports, because FCoE does not exist outside Cisco UCS. The rest of the data center network only dif ferentiates between LAN and SAN traf fic. Therefore, you do not need to take the network type into consideration when you estimate oversubscription of a fabric interconnect port.
Link 8 Link 7 Link 6 Link 5 Link 4 Link 3 Link 2 Link 1 / Fabric Port Channel Links on Chassis None None None None None None Server slots 2, 4, 6, and 8 Server slots 1, 3, 5, and 7 2 links None None N.
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 sys.
Quality of Service Policy A quality of service (QoS) policy assigns a system class to the outgoing traf fic 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.
• MAC address (used for LAN connectivity) • W orld Wide Names (used for SAN connectivity) • Boot settings Stateless computing creates a dynamic server environment with highly flexible servers.
access any policies in the Finance or ganization. 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 .
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).
Cisco UCS Manager GUI Configuration Guide, Release 2.0 42 OL-25712-04 Virtualization in Cisco UCS.
CHAPTER 3 Overview of Cisco UCS Manager This chapter includes the following sections: • About Cisco UCS Manager , page 43 • T asks Y ou Can Perform in Cisco UCS Manager , page 44 • T asks Y ou C.
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.
• Ports • Interface cards • I/O modules Cisco UCS Resource Management Y ou can use Cisco UCS Manager to create and manage all resources within a Cisco UCS domain, including the following: • Se.
• Create the pools and policies related to the network configuration, such as WWN pools and Fibre Channel adapter profiles T asks Y ou Cannot Perform in Cisco UCS Manager Y ou cannot use Cisco UCS Manager to perform certain system management tasks that are not specifically related to device management within a Cisco UCS domain.
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.
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.
The major nodes below the Equipment node in this tab are the following: • Chassis • Fabric Interconnects Servers T ab 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.
Admin T ab This tab contains system-wide settings, such as user manager and communication services, and troubleshooting components, such as faults and events.
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 .
Description Name 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 Wildcard option Displays only that content in the column which is less than the value specified.
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.
a) (Optional) Check the check box to accept all content from Cisco. b) Click Y es 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.
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 .
Pre-Login Banner W ith a pre-login banner , when a user logs into Cisco UCS Manager GUI, Cisco UCS Manager displays the banner text in the Create Pr e-Login Banner dialog box and waits until the user dismisses that dialog box before it prompts for the username and password.
Deleting the Pre-Login Banner Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > User Management . Step 3 Click the User Services node. Step 4 In the W ork pane, click the Banners tab. Step 5 In the Actions area, click Delete .
Description Name 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.
Description Name If checked, Cisco UCS Manager GUI displays a confirmation when operations are successful. Confirm Successful Operations check box Step 4 Click OK . Configuring Properties for External Applications Cisco UCS Manager GUI uses these properties to connect with external applications, such as SSH.
Description Name The number of tabs the system should store in memory for use with the Forward and Back toolbar buttons. Max History Size field If checked, all labels are right-aligned with respect to one another . Otherwise all labels are left-aligned.
Procedure Step 1 In the Navigation pane, click the policy whose usage you want to view . Step 2 In the W ork pane, click the General tab. Step 3 In the Actions area, click Show Policy Usage . Cisco UCS Manager GUI displays the Service Profiles/T emplates dialog box that shows the associated service profiles and service profile templates.
Cisco UCS Manager GUI Configuration Guide, Release 2.0 62 OL-25712-04 Copying the XML.
P ART II System Configuration • Configuring the Fabric Interconnects, page 65 • Configuring Ports and Port Channels, page 77 • Configuring Communication Services, page 113 • Configuring Authen.
.
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, pa.
• Default domain name Setup Mode Y ou 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.
Performing an Initial System Setup for a Standalone Configuration Before Y ou Begin 1 V erify the following physical connections on the fabric interconnect: • The console port is physically connecte.
Step 5 Copy the web link from the prompt into a supported web browser and go to the Cisco UCS Manager GUI launch page. Step 6 On the Cisco UCS Manager GUI launch page, select Express Setup . Step 7 On the Express Setup page, select Initial Setup and click Submit .
Initial System Setup for a Cluster Configuration Performing an Initial System Setup on the First Fabric Interconnect Before Y ou Begin 1 V erify the following physical connections on the fabric interc.
Y ou will see the power on self-test messages as the fabric interconnect boots. Step 3 At the installation method prompt, enter gui. Step 4 If the system cannot access a DHCP server , you are prompted.
Description Field The name of the domain in which the fabric interconnect resides. Domain Name field Step 10 Click Submit . A page displays the results of your setup operation.
A page displays the results of your setup operation. Enabling a Standalone Fabric Interconnect for Cluster Configuration Y ou can add a second fabric interconnect to an existing Cisco UCS domain that uses a single standalone fabric interconnect.
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 .
The link for the current mode is dimmed. Step 5 In the dialog box, click Y es . Cisco UCS Manager restarts the fabric interconnect, logs you out, and disconnects Cisco UCS Manager GUI.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .
Description Name The associated gateway . Default Gateway field Step 8 Click OK . Step 9 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.
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 Se.
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 . Note 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.
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.
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 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.
Configuring Port Modes for a 6248 Fabric Interconnect 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.
What to Do Next Configure the port types for the ports. Y ou can right-click on any port in the module display above the slider and configure that port for an available port type.
• 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.
Server Ports Configuring Server Ports Y ou 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. Y ou can also configure ports from a right-click menu, from the General tab for the port, or in the LAN Uplinks Manager .
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.
Fixed Module • • Expansion Module Step 4 Click the port or ports you want to reconfigure. Step 5 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.
The port or ports are enabled. Data traf fic 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.
Unconfiguring a Port on a Fabric Interconnect Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .
Description Name 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 The admin speed can be changed only for certain ports, and not all speeds are available on all systems.
Description Name The MAC address for the endpoint. MAC Address field 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.
Description Name 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 The admin speed can be changed only for certain ports, and not all speeds are available on all systems.
Step 9 Click OK . FCoE and Fibre Channel Storage Ports Configuring an FCoE Storage Port Y ou 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. Y ou can also configure FCoE storage ports from the General tab for the port.
Before Y ou 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 On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name .
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.
Disabling Default Zoning Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 In the SAN tab, click the SAN node. Step 3 In the W ork pane, click the VSANs tab.
Creating an Uplink Ethernet Port Channel Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 On the LAN tab, expand LAN > LAN Cloud . Step 3 Expand the node for the fabric interconnect where you want to add the port channel. Step 4 Right-click the Port Channels node and choose Create Port Channel .
Enabling an Uplink Ethernet Port Channel Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 On the LAN tab, expand LAN > LAN Cloud . Step 3 Expand the node for the fabric interconnect that includes the port channel you want to enable.
• T o 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.
Description Name A user-defined name for the port channel. This name can be between 1 and 16 alphanumeric characters. Y ou 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 Name Check the check box in this column for each VLAN you want to use. Select column The name of the VLAN. Name column T o designate one of the VLANs as the native VLAN, click the radio button in this column. Native VLAN column c) If you clicked the access radio button, choose a VLAN from the Select VLAN drop-down list.
Enabling an Appliance Port Channel Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 On the LAN tab, expand LAN > Appliances . Step 3 Expand the node for the fabric interconnect that includes the port channel you want to enable. Step 4 Expand the Port Channels node.
• T o 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.
Description Name 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. ID field A user-defined name for the port channel. This name can be between 1 and 16 alphanumeric characters.
Disabling a Fibre Channel Port Channel Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 On the SAN tab, expand SAN > SAN Cloud > Fabric > FC Port Channels . Step 3 Click the port channel you want to disable. Step 4 In the W ork pane, click the General tab.
Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 On the SAN tab, expand SAN > SAN Cloud > Fabric > FC Port Channels . Step 3 Click the port channel that you want to modify .
Adapter Port Channels An adapter port channel groups all the physical links from a Cisco UCS V irtual 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.
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.
What to Do Next T o 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.
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.
Unconfiguring a Server Port with the Internal Fabric Manager Procedure Step 1 In the Internal Fabric Manager , click the server port in the Server Ports table. Step 2 Click Unconfigure Port . Step 3 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Y es .
CHAPTER 7 Configuring Communication Services This chapter includes the following sections: • Communication Services, page 113 • Configuring CIM-XML, page 114 • Configuring HTTP , page 115 • Co.
Description Communication Service This service is enabled on port 80 by default. Y ou 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 .
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.
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.
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 On the Admin tab, expand All > Key Management . Step 3 Click the key ring for which you want to create a certificate request.
Description Name The organizational unit. Enter up to 64 characters. Y ou 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).
Description Name The certificate information for this trusted point. The certificate must be in Base64 encoded X.509 (CER) format. Important Certificate Chain field 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.
Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > Communication Management > Communication Services . Step 3 Select the Communication Services tab. Step 4 In the HTTPS area, click the enabled radio button.
Step 6 Click Save Changes . Deleting a Key Ring Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > Key Management . Step 3 Right-click the key ring you want to delete and choose Delete . Step 4 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Y es .
• 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 .
• 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.
What Happens Encryption Authentication Level Model 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.
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, of fers a choice of DES or 128-bit AES encryption for SNMP security encryption.
Description Name The location of the host on which the SNMP agent (server) runs. Enter an alphanumeric string up to 510 characters. System Location field Step 5 Click Save Changes . What to Do Next Create SNMP traps and users. Creating an SNMP T rap Procedure Step 1 In the Navigation pane, click the Admin tab.
Description Name If you select V2c or V3 for the version, the type of trap to send. This can be one of the following: • T raps • Informs T ype field If you select V3 for the version, the privilege associated with the trap.
Creating an SNMPv3 user Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > Communication Management > Communication Services . Step 3 Select the Communication Services tab. Step 4 In the SNMP Users area, click + .
Deleting an SNMPv3 User Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > Communication Management > Communication Services . Step 3 Select the Communication Services tab. Step 4 In the SNMP Users area, click the row in the table that corresponds to the user you want to delete.
Cisco UCS Manager GUI Configuration Guide, Release 2.0 130 OL-25712-04 Disabling Communication Services.
CHAPTER 8 Configuring Authentication This chapter includes the following sections: • Authentication Services, page 131 • Guidelines and Recommendations for Remote Authentication Providers, page 13.
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.
Attribute ID Requirements Schema Extension Custom Attribute Authentication Provider The vendor ID for the Cisco RADIUS implementation is 009 and the vendor ID for the attribute is 001.
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 .
Description Name 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.
• 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 On the Admin tab, expand All > User Management > LDAP .
Description Name 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. Filter field An LDAP attribute that stores the values for the user roles and locales.
Description Name 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.
Changing the LDAP Group Rule for an LDAP Provider Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > User Management > LDAP . Step 3 Expand LDAP Providers and choose the LDAP provider for which you want to change the group rule.
Step 6 Click Save Changes . Deleting an LDAP Provider Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > User Management > LDAP . Step 3 Expand LDAP Providers . Step 4 Right-click the LDAP provider you want to delete and choose Delete .
Creating an LDAP Group Map Before Y ou 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).
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.
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.
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.
What to Do Next Create an T ACACS+ provider . Creating a T ACACS+ Provider Cisco UCS Manager supports a maximum of 16 T ACACS+ providers. Before Y ou Begin Perform the following configuration in the T ACACS+ server: • Create the cisco-av-pair attribute.
Description Name The port through which Cisco UCS should communicate with the T ACACS+ database. Enter an integer between 1 and 65535. The default port is 49. Port field The length of time in seconds the system should spend trying to contact the T ACACS+ database before it times out.
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 .
Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > User Management > LDAP . Step 3 Expand LDAP Provider Gr oups . Step 4 Right-click the LDAP provider group you want to delete and choose Delete . Step 5 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Y es .
Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > User Management > RADIUS . Step 3 Expand RADIUS Provider Gr oups . Step 4 Right-click the RADIUS provider group you want to delete and choose Delete .
Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > User Management > T ACACS+ . Step 3 Expand T ACACS+ Provider Gr oups . Step 4 Right-click the T ACACS+ provider group you want to delete and choose Delete .
Description Name 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.
Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > User Management > Authentication . Step 3 Click Native Authentication .
Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > User Management > Authentication . Step 3 Click Native Authentication .
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.
CHAPTER 9 Configuring Organizations This chapter includes the following sections: • Organizations in a Multi-T enancy Environment, page 155 • Hierarchical Name Resolution in a Multi-T enancy Envir.
• Service profile templates The root organization is always the top level organization. Hierarchical Name Resolution in a Multi-T enancy Environment In a multi-tenant environment, Cisco UCS uses the hierarchy of an organization to resolve the names of policies and resource pools.
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 .
This name can be between 1 and 16 alphanumeric characters. Y ou 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 In the Description field, enter a description for the organization.
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.
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.
• The unique username for each user account cannot be all-numeric. Y ou 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.
• 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.
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.
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.
Default Role Assignment Description Privilege Storage Administrator External SAN security ext-san-security Operations Alarms and alarm policies fault Operations Logs and Smart Call Home operations Net.
Default Role Assignment Description Privilege Server Profile Administrator Service profile server management service-profile-server Server Profile Administrator Service profile consumer service-profil.
Configuring User Roles Creating a User Role Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > User Management > User Services . Step 3 Right-click User Services and choose Create Role . Y ou can also right-click Roles to access that option.
Adding Privileges to a User Role Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > User Management > User Services . Step 3 Expand the Roles node. Step 4 Choose the role to which you want to add privileges.
Configuring Locales Creating a Locale Before Y ou 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 On the Admin tab, expand All > User Management > User Services .
Assigning an Organization to a Locale Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > User Management > User Services . Step 3 Expand the Locales node and click the locale to which you want to add an or ganization.
Deleting a Locale Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > User Management > User Services . Step 3 Expand the Locales node. Step 4 Right-click the locale you want to delete and choose Delete .
Description Name 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) ◦ .
Description Name 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.
Step 5 In the Roles area, check one or more boxes to assign roles and privileges to the user account. Do not assign locales to users with an admin or aaa role. Note Step 6 (Optional) If the system includes organizations, check one or more check boxes in the Locales area to assign the user to the appropriate locales.
Description Name The maximum number of concurrent HTTP and HTTPS sessions allowed for each user . Enter an integer between 1 and 256. Maximum Sessions Per User field The maximum number of concurrent HTTP and HTTPS sessions allowed for all users within the system.
Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > User Management > User Services > Locally Authenticated Users . Step 3 Click the user account that you want to modify . Step 4 In the W ork pane, click the General tab.
Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > User Management > User Services > Locally Authenticated Users . Step 3 Click the user that you want to disable. Step 4 In the W ork pane, click the General tab.
Y ou 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. Note Password History Count The password history count allows you to prevent locally authenticated users from reusing the same password over and over again.
Configuring the Maximum Number of Password Changes for a Change Interval Y ou 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.
Configuring the Password History Count Y ou 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 On the Admin tab, expand All > User Management > User Services .
Description Name 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.
Cisco UCS Manager GUI Configuration Guide, Release 2.0 182 OL-25712-04 Monitoring User Sessions.
CHAPTER 11 Managing Firmware This chapter includes the following sections: • Overview of Firmware, page 183 • Firmware Image Management, page 184 • Firmware V ersions, page 186 • Firmware Upgr.
• 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 in.
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.
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.
Firmware V ersions in the Fabric Interconnect and Cisco UCS Manager Y ou 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.
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. T o avoid faults and other issues, we recommend that you make any required changes before you upgrade.
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 T eaming Are Both Enab.
No Server or Chassis Maintenance 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.
Determine Appropriate T ype 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.
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.
• 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.
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.
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. Y ou cannot directly upgrade an endpoint if the service profile associated with the server includes a firmware package.
When you configure Set Startup V ersion 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 V ersion Only for an I/O module, the I/O module reboots and disrupts traffic.
• Any activities being performed on the server through the KVM console and vMedia are interrupted. • Any monitoring or IPMI polling is interrupted.
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.
Service Profile Association During this stage, you include the firmware packages in a service profile, and then associate the service profile with a server .
• 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.
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 button.
V erifying the Overall Status of the Fabric Interconnects Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Fabric Interconnects . Step 3 Click the node for the fabric interconnect that you want to verify .
V erifying the Status of I/O Modules Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis . Step 3 Click on the chassis for which you want to verify the status of the I/O modules.
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 .
• 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.
Downloading Firmware Images to the Fabric Interconnect from a Remote Location 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.
Description Name 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 .
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, click the Equipment node. Step 3 In the W ork pane, click the Firmware Management tab. Step 4 Click the Installed Firmware tab. Step 5 Click Download Firmware .
Determining the Contents of a Firmware Package Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, click the Equipment node. Step 3 In the W ork pane, click the Firmware Management tab. Step 4 On the Packages subtab, click the + icon next to a package to view its contents.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, click the Equipment node. Step 3 In the W ork pane, click the Firmware Management tab. Step 4 On the Firmware Management tab, click the Packages tab. Step 5 In the table, click the package that you want to delete.
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.
What to Do Next Activate the firmware. Updating the Firmware on an Adapter 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.
Activating the Firmware on an Adapter Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers . Step 3 Expand the node for the server that includes the adapter for which you want to activate the updated firmware.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers . Step 3 Expand the node for the server for which you want to update the BIOS firmware. Step 4 On the General tab, click the Inventory tab.
d) Click OK . Updating the CIMC Firmware on a Server 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.
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.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > IO Modules . Step 3 Click the I/O module that you want to update. Step 4 In the General tab, click Update Firmware .
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.
Activating the Cisco UCS Manager Software Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, click the Equipment node. Step 3 In the W ork pane, click the Firmware Management tab. Step 4 On the Installed Firmware tab, click Activate Firmwar e .
Step 5 From the Filter drop-down list on the menu bar , choose Fabric Inter connects . Step 6 On the menu bar , check the Ignore Compatibility Check check box.
Step 2 From the Filter drop-down list on the menu bar , choose Fabric Inter connects . Step 3 On the menu bar , check the Ignore Compatibility Check check box.
Description Name Choose the version that you want to use for the kernel. Kernel V ersion drop-down list By default, Cisco UCS makes sure that the firmware version is compatible with everything running on the server before it activates that version.
• FC Adapters • HBA Option ROM • Storage Controller Y ou 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.
The following table describes the most common options for upgrading servers with a host or management firmware package. Upgrade Actions Maintenance Policy Service Profile After you update the firmware.
Upgrade Actions Maintenance Policy Service Profile The following occurs when you update the firmware package: 1 The changes to the firmware package take effect as soon as you save them. 2 Cisco UCS Manager verifies the model numbers and vendor against all servers associated with service profiles that include this policy .
Upgrade Actions Maintenance Policy Service Profile 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.
This name can be between 1 and 16 alphanumeric characters. Y ou cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and .
Manager updates the firmware according to the settings in the maintenance policies included in the service profiles. Creating a Management Firmware Package Before Y ou Begin Ensure that the appropriate firmware has been downloaded to the fabric interconnect.
Before Y ou 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 On the Servers tab, expand Servers > Policies . Step 3 Expand the node for the organization that includes the policy you want to update.
Step 4 Click the service profile to which you want to add the firmware packages. Step 5 In the W ork pane, click the Policies tab. Step 6 Click the down arrows to expand the Firmware Policies section. Step 7 T o add a host firmware package, select the desired policy from the Host Firmware drop-down list.
Implementation-Specific T unable Parameters • Power and thermal constraints • Slot ranges and numbering • Adapter capacities Hardware-Specific Rules • Firmware compatibility for components suc.
Activating a Capability Catalog Update Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All . Step 3 Click the Capability Catalog node. Step 4 In the W ork pane, click the Catalog Update T asks tab. Step 5 Click Activate Catalog .
Viewing a Capability Catalog Provider Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > Capability Catalog .
Updating the Capability Catalog from a Remote Location Y ou 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 .
Step 8 Click OK . Cisco UCS Manager downloads the image and updates the Capability Catalog. Y ou 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 Y ou cannot perform a partial update to the Capability Catalog.
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.
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 Y ou need to specify an external DNS server for each Cisco UCS domain to use if the system requires name resolution of hostnames.
Deleting a DNS Server Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 In the Admin tab, expand All > Communication Services . Step 3 Click DNS Management . Step 4 In the W ork pane, click the General tab. Step 5 In the DNS Server area, right-click the DNS server you want to delete and choose Delete .
CHAPTER 13 Configuring System-Related Policies This chapter includes the following sections: • Configuring the Chassis Discovery Policy , page 239 • Configuring the Chassis Connectivity Policy , p.
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 pol.
Platform-Max Discovery Policy 8-Link Chassis Discovery Policy 4-Link Chassis Discovery Policy 2-Link Chassis Discovery Policy 1-Link Chassis Discovery Policy Number of Links Wired for the Chassis 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.
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.
Step 6 Click Save Changes . What to Do Next T o customize fabric port channel connectivity for a specific chassis, configure the chassis connectivity 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 .
Step 6 Click Save Changes . Configuring the Aging T ime for the MAC Address T able Aging T ime for the MAC Address T able T o efficiently switch packets between ports, the fabric interconnect maintains a MAC address table.
Step 6 Click Save Changes . Cisco UCS Manager GUI Configuration Guide, Release 2.0 246 OL-25712-04 Configuring the Aging T ime for the MAC Address T able.
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 • Do.
• 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.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Fabric Interconnects . Step 3 Click the node for the fabric interconnect for which you want to obtain the host ID. Step 4 In the W ork pane, click the General tab.
Downloading Licenses to the Fabric Interconnect from the Local File System 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.
Downloading Licenses to the Fabric Interconnect from a Remote Location 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.
Description Name The username the system should use to log in to the remote server . This field does not apply if the protocol is TFTP . User field The password for the remote server username. This field does not apply if the protocol is TFTP . Password field Step 8 Click OK .
V iewing the Licenses Installed on a Fabric Interconnect Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > License Management .
Description Name 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 T AC.
Description Name The Product Authentication Key (P AK) associated with this license, if available. P AK column The signature key associated with the licenses of the given type. Signature column The company that issued the license package file. V endor column The version of the license package file.
Description Name The number of licenses on the peer fabric interconnect compared to this fabric interconnect. This can be one of the following: • exceeds —the peer fabric interconnect has more lic.
Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > License Management . Step 3 In the W ork pane, click the Installed Licenses tab. Step 4 Choose the license you want to uninstall from the table. Step 5 Click the Clear License button.
Cisco UCS Manager GUI Configuration Guide, Release 2.0 258 OL-25712-04 Uninstalling a License.
CHAPTER 15 Managing V irtual Interfaces This chapter includes the following sections: • V irtual Interfaces, page 259 • V irtual Interface Subscription Management and Error Handling, page 259 V ir.
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.
P ART 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 • Configurin.
.
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 Swi.
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 On the LAN tab, click the LAN node.
Procedure Step 1 In the LAN Uplinks Manager , click the LAN Uplinks tab. Step 2 In the Ports area, click the down arrows to expand the Unconfigured Ports section.
Disabling a Server Port with the LAN Uplinks Manager Procedure Step 1 In the LAN Uplinks Manager , click the LAN Uplinks tab. Step 2 In the Ports area, click the down arrows to expand the Server Ports section. Step 3 Expand Fabric Interconnects > Fabric_Interconnect_Name .
Disabling an Uplink Ethernet Port with the LAN Uplinks Manager Procedure Step 1 In the LAN Uplinks Manager , click the LAN Uplinks tab. Step 2 In the Port Channels and Uplinks area, expand Interfaces > Fabric Interconnects > Fabric_Interconnect_Name .
• 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: Description Name 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.
Disabling a Port Channel with the LAN Uplinks Manager Procedure Step 1 In the LAN Uplinks Manager , click the LAN Uplinks tab. Step 2 In the Port Channels and Uplinks area, expand Port Channels > Fabric Interconnects > Fabric_Interconnect_Name .
Removing Ports from a Port Channel with the LAN Uplinks Manager Procedure Step 1 In the LAN Uplinks Manager , click the LAN Uplinks tab. Step 2 In the Port Channels and Uplinks area, expand Port Channels > Fabric Interconnects > Fabric_Interconnect_Name .
Procedure Step 1 In the LAN Uplinks Manager , click the LAN Uplinks tab. Step 2 In the Port Channels and Uplinks area, click Create Pin Gr oup . Step 3 In the Create LAN Pin Gr oup dialog box, enter a unique name and description for the pin group.
Y ou 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 traf fic disruption for all vNICs and uplink ports using that VLAN.
Description Name T o create one VLAN, enter a single numeric ID. T o create multiple VLANs, enter individual IDs or ranges of IDs separated by commas. A VLAN ID can: • Be between 1 and 3967 • Be b.
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.
Description Name 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 interconnec.
Description Name 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.
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 2.
Guidelines for VLAN IDs Y ou 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 traf fic disruption for all vNICs and uplink ports using that VLAN.
• VIFs on VNT AG adapters can have only one isolated VLAN. Guidelines for VLAN IDs Y ou 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.
• 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 se.
Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 On the LAN tab, click the LAN node. Step 3 In the W ork 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.
Description Name T o create one VLAN, enter a single numeric ID. T o create multiple VLANs, enter individual IDs or ranges of IDs separated by commas. A VLAN ID can: • Be between 1 and 3967 • Be b.
Description Name 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.
• 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.
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. Y ou cannot create VLANs with IDs from 3968 to 4047.
Description Name Y ou 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.
Description Name Click this button to determine whether the VLAN ID overlaps with any other IDs on the system. Check Overlap button Step 6 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.
Description Name The full path to the VSAN. Click the link in this column to view the properties for the VSAN. DN column 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.
Description Name 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. Y ou cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and .
Description Name 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.
Description Name 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.
Description Name The maximum number of VLAN ports allowed on this fabric interconnect. VLAN Port Limit field The number of available VLAN access ports. Access VLAN Port Count field The number of available VLAN border ports. Border VLAN Port Count field The VLAN port allocation status.
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 G.
Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 On the LAN tab, expand LAN > LAN Cloud . Step 3 Right-click LAN Pin Groups and select Cr eate LAN Pin Group . Step 4 In the Create LAN Pin Gr oup dialog box, enter a unique name and description for the pin group.
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 .
Step 4 Right-click MAC Pools and select Create MAC Pool . Step 5 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 .
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 Pol.
T able 10: System Classes Description System Class A configurable set of system classes that you can include in the QoS policy for a service profile. Each system class manages one lane of traffic. All properties of these system classes are available for you to assign custom settings and policies.
Description Name 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 interconnec.
Description Name 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.
Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 In the LAN tab, expand LAN > LAN Cloud . Step 3 Select the QoS System Class node. Step 4 In the W ork pane, click the General tab. Step 5 Uncheck the Enabled check box for the QoS system that you want to disable.
Description Name 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 .
Description Name 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.
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.
Description Name 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 .
Cisco UCS Manager GUI Configuration Guide, Release 2.0 306 OL-25712-04 Configuring Flow Control Policies.
CHAPTER 21 Configuring Network-Related Policies This chapter includes the following sections: • Configuring vNIC T emplates, page 307 • Configuring Ethernet Adapter Policies, page 312 • Configuring Network Control Policies, page 317 Configuring vNIC T emplates vNIC T emplate This policy defines how a vNIC on a server connects to the LAN.
• 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 On the LAN tab, expand LAN > Policies . Step 3 Expand the node for the organization where you want to create the policy .
Description Name 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.
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: Description Name Check the check box in this column for each VLAN that you want to use. Select column The name of the VLAN.
What to Do Next Include the vNIC template in a service profile. Deleting a vNIC T emplate Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 On the LAN tab, expand LAN > Policies > Or ganization_Name . Step 3 Expand the vNIC T emplates node.
b) Click OK . Step 9 In the warning dialog box, click Y es 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 T emplate Procedure Step 1 In the Navigation pane, click the Servers tab.
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 a.
Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Policies . Step 3 Expand the node for the organization where you want to create the policy . If the system does not include multitenancy , expand the root node.
Description Name 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.
Description Name 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.
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 > Or ganization_Name . Step 3 Expand the Adapter Policies node. Step 4 Right-click the Ethernet adapter policy that you want to delete and choose Delete .
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.
Description Name This option determines whether Cisco Discovery Protocol (CDP) is enabled on servers associated with a service profile that includes this policy .
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.
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 Disjoi.
that is specifically assigned to that VLAN, and is selectively excluded from all other uplink ports and port channels. However , traf fic 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.
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.
• 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.
Procedure Purpose Command or Action The Ethernet switching mode must be in End-Host Mode for Cisco UCS to be able to communicate with upstream disjoint L2 networks. Configure Ethernet switching mode for both fabric interconnects in Ethernet End-Host Mode.
The LAN Uplinks Manager opens in a separate window . Step 4 In the LAN Uplinks Manager , click VLANs > VLAN Manager . Step 5 On the icon bar to the right of the table, click + .
Description Name 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.
Description Subtab Displays the ports, port channels, and VLANs that are accessible to fabric interconnect B. Fabric B Step 6 In the Ports and Port Channels table, do the following: • T o 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.
Description Subtab Displays the ports, port channels, and VLANs that are accessible to fabric interconnect A. Fabric A Displays the ports, port channels, and VLANs that are accessible to fabric interconnect B. Fabric B Step 6 In the VLANs table, expand the appropriate node and the VLAN from which you want to remove a port or port channel.
Cisco UCS Manager GUI Configuration Guide, Release 2.0 330 OL-25712-04 Viewing Ports and Port Channels Assigned to VLANs.
P ART 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 T runking for Named VSANs, page 334 • Guidelines and Recommendatio.
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.
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 T ransfers all non-operational VSANs to the default VSAN. 4 T ransfers all vHBAs associated with the non-operational VSANs to the default VSAN.
Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 On the SAN tab, expand SAN > SAN Cloud . Step 3 In the W ork 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.
Description Name 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.
Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 On the SAN tab, expand SAN > Storage Cloud . Step 3 In the W ork 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.
Description Name 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.
Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 In the SAN tab, click the SAN node. Step 3 In the W ork pane, click the VSANs tab. Step 4 Click one of the following subtabs, depending upon what type of VSAN you want to delete: Description Subtab Displays all VSANs in the Cisco UCS domain.
• 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.
Cisco UCS Manager GUI Configuration Guide, Release 2.0 342 OL-25712-04 Disabling Fibre Channel Uplink T runking.
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 traf fic from a vHBA on a server to an uplink Fibre Channel port on the fabric interconnect.
Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 In the SAN tab, expand SAN > SAN Cloud . Step 3 Right-click SAN Pin Groups and select Cr eate SAN Pin Group .
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.
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.
Adding a WWN Block to a WWNN Pool 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 .
Adding a WWNN Initiator to a WWNN Pool 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 .
Deleting a WWNN Initiator from a WWNN Pool Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 In the SAN tab, expand SAN > Pools > Organization_Name . Step 3 Expand the WWPN Pools node. Step 4 Choose the WWNN pool from which you want to delete a WWNN initiator .
Configuring WWPN Pools Creating a WWPN Pool 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.
Adding a WWN Block to a WWPN Pool 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 .
Adding a WWPN Initiator to a WWPN Pool 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 .
Deleting a WWPN Initiator from a WWPN Pool Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 In the SAN tab, expand SAN > Pools > Organization_Name . Step 3 Expand the WWPN Pools node. Step 4 Choose the WWPN pool from which you want to delete a WWPN initiator .
Cisco UCS Manager GUI Configuration Guide, Release 2.0 354 OL-25712-04 Configuring WWPN Pools.
CHAPTER 26 Configuring Storage-Related Policies This chapter includes the following sections: • Configuring vHBA T emplates, page 355 • Configuring Fibre Channel Adapter Policies, page 358 Configuring vHBA T emplates vHBA T emplate This template is a policy that defines how a vHBA on a server connects to the SAN.
If the system does not include multitenancy , expand the root node. Step 4 Right-click the vHBA T emplates node and choose Cr eate vHBA T emplate . Step 5 In the Create vHBA T emplate dialog box, complete the following fields: Description Name The name of the virtual HBA template.
Step 6 Click OK . What to Do Next Include the vHBA template in a service profile. Deleting a vHBA T emplate Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 On the SAN tab, expand SAN > Policies > Organization_Name . Step 3 Expand the vHBA T emplates node.
a) From the vHBA T emplate 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 Y es to acknowledge that Cisco UCS Manager may need to reboot the server if the binding causes the vHBA to be reconfigured.
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 a.
Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Policies . Step 3 Expand the node for the organization where you want to create the policy . If the system does not include multitenancy , expand the root node.
Description Name The number of SCSI IO queue resources the system should allocate. Enter an integer between 1 and 8. The default is 1. At this time, the Cisco UCS M81KR V irtual Interface Card adapter supports only one SCSI I/O queue. Note SCSI I/O Queues field The number of descriptors in each SCSI I/O queue.
Description Name 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. W e recommend you consult your storage array documentation for the optimal value for this parameter .
Description Name 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. W e recommend you consult your storage array documentation for the optimal value for this parameter .
Description Name 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. W e recommend that you select this option if the operating system on the server supports it.
P ART V Server Configuration • Configuring Server-Related Pools, page 367 • Setting the Management IP Address, page 373 • Configuring Server-Related Policies, page 381 • Configuring Server Boo.
.
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.
Step 4 Right-click the Server Pools node and select Create Server Pool . Step 5 On the Set Name and Description page of the Create Server Pool wizard, complete the following fields: Description Name The name of the server pool. This name can be between 1 and 32 alphanumeric characters.
Adding Servers to a Server Pool Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Pools > Organization_Name . Step 3 Right-click the pool to which you want to add one or more servers and select Add Servers to Server Pool .
Creating a UUID Suffix Pool Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Pools . Step 3 Expand the node for the organization where you want to create the pool. If the system does not include multitenancy , expand the root node.
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.
Cisco UCS Manager GUI Configuration Guide, Release 2.0 372 OL-25712-04 Configuring UUID Suffix Pools.
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 .
Y ou 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.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers . Step 3 Click the server that you want to configure to use the management IP pool. Step 4 In the W ork pane, click the Inventory tab.
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 On the Equipment tab, expand Equipment > Rack Mounts > Servers .
Description Field The static IPv4 address to be assigned to the service profile IP Address The subnet mask for the IP address. Subnet Mask The default gateway that the IP address should use.
Y ou can configure service profiles and service profile templates to use IP addresses from the management IP pool. Y ou 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.
Deleting an IP Address Block from the Management IP Pool Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 In the Admin tab, expand All > Communication Services > Management IP Pool (ext-mgmt) . Step 3 Right-click the IP address block that you want to delete and select Delete .
Cisco UCS Manager GUI Configuration Guide, Release 2.0 380 OL-25712-04 Configuring the Management IP Pool.
CHAPTER 29 Configuring Server -Related Policies This chapter includes the following sections: • Configuring BIOS Settings, page 381 • Configuring IPMI Access Profiles, page 405 • Configuring Loc.
Cisco UCS Manager pushes BIOS configuration changes through a BIOS policy or default BIOS settings to the Cisco Integrated Management Controller (CIMC) buf fer .
Description Name 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 .
Description Name Whether the BIOS publishes the ACPI 1.0 version of F ADT 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.
Description Name Whether the processor uses Enhanced Intel SpeedStep T echnology , 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.
Description Name 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 .
Description Name 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.
Description Name 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.
Description Name 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.
Description Name 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 .
Description Name Whether the processor supports Intel VT-d Interrupt Remapping. This can be one of the following: • disabled —The processor does not support remapping.
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: Description Name How the memory reliability , availability , and serviceability (RAS) is configured for the server .
Description Name 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.
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: Description Name Whether serial port A is enabled or disabled. This can be one of the following: • disabled —The serial port is disabled.
Description Name 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.
Description Name Whether the BIOS maximizes memory usage below 4GB for an operating system without P AE 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 P AE support.
Description Name 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.
General Settings Description Name 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.
Description Name 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.
Console Redirection Settings Description Name 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.
Description Name 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.
BIOS Policy The BIOS policy is a policy that automates the configuration of BIOS settings for a server or group of servers. Y ou 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 .
Creating a BIOS Policy Cisco UCS Manager pushes BIOS configuration changes through a BIOS policy or default BIOS settings to the Cisco Integrated Management Controller (CIMC) buf fer . These changes remain in the buf fer and do not take effect until the server is rebooted.
Modifying the BIOS Defaults W e 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 Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers . Step 3 Choose the server for which you want to view the actual BIOS settings. Step 4 On the W ork pane, click the Inventory tab.
a) Enter a unique name and description for the profile. b) Click OK . Step 6 In the IPMI Profile Users area of the navigator , click + . Step 7 In the User Properties dialog box: a) Complete the following fields: Description Name The username to associate with this IPMI profile.
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.
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 prope.
T o 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.
Creating a Local Disk Configuration Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Policies . Step 3 Expand the node for the organization where you want to create the policy . If the system does not include multitenancy , expand the root node.
Description Name 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.
Description Name 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 .
Description Option Enables you to create a local disk configuration policy that can only be accessed by the selected service profile. Create a Local Disk Policy Does not use a local disk configuration policy for the selected service profile. No Disk Policy Step 8 Click OK .
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.
Step 6 Click OK . Deleting a Scrub Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Policies > Organization_Name . Step 3 Expand the Scrub Policies node. Step 4 Right-click the policy you want to delete and select Delete .
Description Name The name of the policy . This name can be between 1 and 16 alphanumeric characters. Y ou 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.
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 .
Description Name A description of the policy . W e recommend that you include information about where and when the policy should be used. Enter up to 256 characters.
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 .
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 On the Equipment tab, click the Equipment node. Step 3 In the W ork pane, click the Policies tab.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, click the Equipment node. Step 3 In the W ork pane, click the Policies tab. Step 4 Click the Server Inheritance Policies subtab. Step 5 On the icon bar to the right of the table, click + .
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 tar get pool specified in the policy .
Description Name 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. Qualification drop-down list Step 6 Click OK . Deleting a Server Pool Policy Procedure Step 1 In the Navigation pane, click the Servers tab.
• Server model Depending upon the implementation, you may configure several policies with server pool policy qualifications including the following: • Autoconfiguration policy • Chassis discover.
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 .
Description Name The minimum memory capacity required, in megabytes. Min Cap field The maximum memory capacity allowed, in megabytes. Max Cap field The minimum width of the data bus. W idth field The unit of measure to associate with the value in the Width field.
c) Click OK . Step 11 (Optional) T o 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: Description Name Whether the available storage must be diskless.
a) Click Create Power Gr oup Qualifications . b) In the Create Power Group Qualifications dialog box, choose a power gruup from the Power Group drop-down list.
Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Policies > Organization_Name . Step 3 Expand the Server Pool Policy Qualifications node. Step 4 Choose the policy you want to modify . Step 5 In the W ork pane, choose the Qualifications tab.
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 .
T o 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. Y ou can configure the vCons through a vNIC/vHBA placement policy or in the service profile associated with the server .
Implicit Assignment of vNICs in a Mixed Adapter Environment The implicit assignment of vNICs functions dif ferently 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.
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 On the Servers tab, expand Servers > Policies .
Deleting a vNIC/vHBA Placement Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Policies > Organization_Name . Step 3 Expand the vNIC/vHBA Placement Policies node. Step 4 Right-click the policy you want to delete and choose Delete .
Description Name 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.
Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Service Profiles . Step 3 Expand the node for the organization which contains the service profile whose vHBAs you want to explicitly assign to a vCon.
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 Configuring vNIC/vHBA Placement Policies.
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 • LA.
Creating a Boot Policy Y ou 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.
• V irtual Media Boot —T o boot from virtual media that mimics the insertion of a physical CD or floppy drive into a server , continue with Configuring a V irtual Media Boot for a Boot Policy, on page 466 . What to Do Next Include the boot policy in a service profile and/or template.
Before Y ou Begin 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 .
Description Name 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.
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.
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 .
Enabling MPIO on Windows If you change the networking hardware, W indows may fail to boot from an iSCSI drive. For more information, see Microsoft support Article ID: 976042 . Note Before Y ou Begin The server on which you enable MPIO must have a Cisco VIC driver .
Purpose Command or Action For more information about creating a boot policy that can be used in any service profile, see Creating an iSCSI Boot Policy, on page 451 . Create a boot policy that can be used in any service profile. Alternatively , you can create a local boot policy only for the specific service policy .
Description Name The name of the policy . This name can be between 1 and 16 alphanumeric characters. Y ou 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.
Deleting an iSCSI Adapter Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Policies . Step 3 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 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 On the Servers tab, expand Servers > Policies .
Description Name 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. Subnet Mask field The default gateway associated with the IP addresses in the block.
This name can be between 1 and 16 alphanumeric characters. Y ou cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and .
Description Name The name of the iSCSI vNIC. This name can be between 1 and 16 alphanumeric characters. Y ou 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.
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.
Description Name The name of the associated authentication profile. Authentication Profile drop-down list Click this link to create a new authentication profile policy that will be available to all iSCSI vNICs.
Description Option An IPv4 address is assigned to the iSCSI boot vNIC from the management IP address pool. Proceed to Step 13. Pool Step 12 If you chose Static from the Initiator IP Address Policy drop-down list, complete the following fields: Description Name The IPv4 address assigned to the iSCSI boot vNIC.
Description Name A regular expression that defines the iSCSI Qualified Name (IQN) or Extended Unique Identifier (EUI) name of the iSCSI target. Y ou 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.
Modifying iSCSI Boot Parameters Y ou 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.
Description Name Select how the iSCSI boot initiator name is assigned. Choose one of the following methods: • Manual —Y ou 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.
Description Name The default gateway associated with the IPv4 address. Default Gateway field The primary DNS server address. Primary DNS field The secondary DNS server address.
Description Name The system-assigned priority for the iSCSI target. Priority field The port associated with the iSCSI target. Enter an integer between 1 and 65535.
Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 On the SAN tab, expand SAN > Pools . Step 3 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 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.
• The vNIC or vHBA is assigned to a different pool. Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 On the SAN tab, expand SAN > Pools . Step 3 Expand the node for the organization containing the pool. If the system does not include multitenancy , expand the root node.
LAN Boot Y ou 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 . Y ou can add more than one type of boot device to a LAN boot policy .
Configuring a Local Disk Boot for a Boot Policy Y ou 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.
V irtual Media requires the USB to be enabled. If you modify the BIOS settings that affect the USB functionality , you also affect the V irtual Media. Therefore, we recommend that you leave the follow.
Cisco UCS Manager GUI Configuration Guide, Release 2.0 468 OL-25712-04 Deleting a Boot Policy.
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 • C.
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 .
Pending Activities If you configure deferred deployment in a Cisco UCS domain, Cisco UCS Manager enables you to view all pending activities. Y ou can see activities that are waiting for user acknowledgement and those that have been scheduled.
Cannot Perform Partial Deployment of Pending Activity Cisco UCS Manager applies all changes made to a service profile in the scheduled maintenance window . Y ou cannot make several changes to a service profile at the same time and then have those changes be spread across several maintenance windows.
a) Complete the following fields: Description Name The name of the one time occurrence of this schedule. This name can be between 1 and 16 alphanumeric characters. Y ou cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and .
Description Name 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.
Description Name The day on which Cisco UCS runs an occurrence of this schedule. This can be one of the following: • every day • Monday • T uesday • W ednesday • Thursday • Friday • Saturday • Sunday • odd days • even days Day field The hour of the specified day at which this occurrence of the schedule starts.
Description Name 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.
Creating a One T ime Occurrence for a Schedule 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.
Description Name 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.
Creating a Recurring Occurrence for a Schedule Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Schedules . Step 3 Right-click the schedule to which you want to add an occurrence and choose Cr eate a Recurring Occurrence .
Description Name The minute of the hour at which the schedule occurrence starts. This can be an integer between 0 and 60. Minute field Step 5 Click the down arrows to expand the Options area. Step 6 In the Options area, complete the following fields: Description Name The maximum length of time that each occurrence of this schedule can run.
Description Name 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.
Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Schedules > Schedule_Name . Step 3 Expand Recurring Occurrences . Step 4 Right-click the occurrence you want to delete and choose Delete . Step 5 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Y es .
Description Name The name of the policy . This name can be between 1 and 16 alphanumeric characters. Y ou 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.
Deleting a Maintenance Policy Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Policies > Organization_Name . Step 3 Expand Maintenance Policies . Step 4 Right-click the maintenance policy you want to delete and choose Delete .
Procedure Step 1 On the toolbar , click Pending Activities . Step 2 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 .
Procedure Step 1 On the toolbar , click Pending Activities . Step 2 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 .
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 , .
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. Y ou can associate these service profiles with either a rack-mount server or a blade server .
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 .
• 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 P.
Description Option 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.
Description Option Assigns the default local disk storage policy to this service profile. Continue with Step 4. Select Local Storage Policy to use Enables you to create a local disk policy that can only be accessed by this service profile. Continue with Step 2.
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.
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 W orld Wide Node Name field. Y ou 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 .
Description Name Check this check box if you want to use a template to create the vHBA. Cisco UCS Manager GUI displays the vHBA T emplate 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.
Description Name This can be one of the following: • Disabled • Enabled Persistent Binding field The maximum size of the Fibre Channel frame payload bytes that the vHBA supports.
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 dro.
e) Continue with Step 4. Step 4 In the How would you like to configure LAN connectivity? field, click one of the following options: Description Option Allows you to create a maximum of two vNICs, in dual fabric mode, for this service profile. Continue with Step 5.
Description Name Check this check box if you want to use a template to create the vNIC. Cisco UCS Manager GUI displays the vNIC T emplate 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.
Description Name 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 —T o designate one of the VLANs as the native VLAN, click the radio button in this column.
Description Name Click this link if you want to create a network control policy . Create Network Contr ol 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 .
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 .
Description Name Moves the selected vNIC or VHBA to a higher priority in the list. Move Up button Moves the selected vNIC or vHBA to a lower priority in the list. Move Down button Deletes the selected vNIC or vHBA. Delete button Returns all vNICs and vHBAs to their original order .
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. Y ou can assign them explicitly through the service profile or the properties of the vNIC or vHBA.
Description Option Enables you to create a local boot policy that can only be accessed by this service profile. Continue with Step 3. Create a Specific Boot Policy Assigns an existing boot policy to the service profile. If you choose this option, Cisco UCS Manager displays the details of the policy .
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 .
Description Name 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.
Procedure Step 1 From the Maintenance Policy drop-down list, choose one of the following: Description Option Assigns the default maintenance policy to this service profile. Continue with Step 4. Select a Maintenance Policy to Use (default policy shown) Assigns an existing maintenance policy to the service profile.
Description Name 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.
Description Option Allows you to assign a server after you have created and configured the service profile. Continue with Step 6. Assign Later Specifies the chassis and slot that contains the server which will be assigned to the service profile.
Description Name T o associate a host firmware package with this service profile, choose its name from the drop-down list. Host Firmware drop-down list Click this link if you want to create a host firmware package.
For more information about how to create an IPMI profile, see Creating an IPMI Access Profile, on page 405 . Step 4 T o add a Serial over LAN policy to the service profile, do one of the following: • T o add an existing policy , select the desired Serial over LAN policy from the SoL Configuration Profile drop-down list.
Step 7 T o 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: • T o add an existing policy , select the desired power control policy from the Power Contr ol Policy drop-down list.
Description Name 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. Primary vNIC check box The name of the vNIC. This name can be between 1 and 16 alphanumeric characters.
Description Name The fabric interconnect that this vHBA is associated with. Do not associate the primary vHBA with the same fabric as the secondary vHBA. Fabric field Secondary vHBA Section Check this check box if you want to create a second vHBA for this service profile.
Description Name If T ype 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 boo.
Creating a Hardware Based Service Profile for a Blade Server Y ou cannot move a hardware based service profile to another server . Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers .
a) From the Create Service Pr ofile 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.
Page 1: Identifying the Service Profile T emplate This procedure directly follows the steps in Creating a Service Profile T emplate, on page 518 . It describes how to set the identity of a service profile template on the Identify Service Profile T emplate page of the Create Service Pr ofile T emplate wizard.
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 T emplate, on page 519 .
• 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.
Description Option 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.
Description Name The name of this vHBA. This name can be between 1 and 16 alphanumeric characters. Y ou 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 Name Click this link if you want to create a pin group. Create SAN Pin Gr oup link This can be one of the following: • Disabled • Enabled Persistent Binding field The maximum size of the Fibre Channel frame payload bytes that the vHBA supports.
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 Dyna.
e) Continue with Step 4. Step 4 In the How would you like to configure LAN connectivity? field, click one of the following options: Description Option Allows you to create a maximum of two vNICs, in dual fabric mode, for every service profile created from this template.
Description Name Check this check box if you want to use a template to create the vNIC. Cisco UCS Manager GUI displays the vNIC T emplate 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.
Description Name 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 —T o designate one of the VLANs as the native VLAN, click the radio button in this column.
Description Name Click this link if you want to create a network control policy . Create Network Contr ol 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 .
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 .
a) Use one or more of the following buttons to adjust the order of the vNICs and vHBAs: Description Name Moves the selected vNIC or VHBA to a higher priority in the list. Move Up button Moves the selected vNIC or vHBA to a lower priority in the list. Move Down button Deletes the selected vNIC or vHBA.
b) In the Selection Prefer ence column for each V irtual 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.
Description Option 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. Create a Specific Boot Policy Assigns an existing boot policy to every service profile created from this template.
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 .
Description Name 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.
Procedure Step 1 From the Maintenance Policy drop-down list, choose one of the following: Description Option Assigns the default maintenance policy to this service profile. Continue with Step 4. Select a Maintenance Policy to Use (default policy shown) Assigns an existing maintenance policy to the service profile.
Description Name 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.
Procedure Step 1 From the Pool Assignment drop-down list, choose one of the following: Description Option Allows you to assign a server after you have created and configured the service profile template. Continue with Step 2. Assign Later Select a server pool from the list at the bottom of the drop-down list.
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 .
For more information about how to create a serial over LAN policy , see Creating a Serial over LAN Policy, on page 415 . Step 5 T o configure the management IP required for external access to the CIMC.
Creating One or More Service Profiles from a Service Profile T emplate Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Service Profile T emplates .
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers . Step 3 Choose the server for which you want to create a template based service profile. Step 4 In the W ork pane, click the General tab.
Creating a Service Profile T emplate from a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Service Profiles . Step 3 Expand the node for the organization that contains the service profile that you want to use as the basis for your template.
Managing Service Profiles Cloning a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Service Profiles . Step 3 Expand the node for the organization where you want to create the service profile.
Description Option 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 Pool Navigate to the desired available server in the navigation tree and select the server which will be assigned to the service profile.
Step 4 Right-click the service profile you want to disassociate from a server and select Disassociate Service Pr ofile . Step 5 In the Disassociate Service Profile dialog box, click Y es to confirm that you want to disassociate the service profile.
Disassociating a Service Profile T emplate from its Server Pool Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Service Profile T emplates . Step 3 Expand the node for the organization that contains the service profile that you want to disassociate from its server pool.
Description Option 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 .
Step 4 Choose the service profile template whose UUID assignment you want to change. Step 5 In the W ork pane, click the General tab. Step 6 In the Actions area, click Change UUID . Step 7 From the UUID Assignment drop-down list, choose one of the following: Description Option Assigns a UUID from the default UUID Suffix pool.
Step 4 Choose the service profile that requires the UUID for the associated server to be reset to a different UUID suffix pool. Step 5 In the W ork pane, click the General tab.
This name can be between 1 and 16 alphanumeric characters. Y ou cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and .
Description Name 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.
Creating a vNIC for a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Service Profiles . Step 3 Expand the node for the organization that contains the service profile for which you want to create a vNIC.
b) Complete the following fields to specify the fabric connection information: Description Name 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.
Description Name The statistics collection policy with which this vNIC is associated. Stats Thr eshold Policy drop-down list c) In the Adapter Performance Profile area, complete the following fields: Description Name The Ethernet adapter policy with which this vNIC is associated.
Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Service Profiles . Step 3 Expand the node for the organization that contains the service profile for which you want to reset the MAC address.
a) Complete the following fields to specify the identity information for the vHBA: Description Name The name of this vHBA. This name can be between 1 and 16 alphanumeric characters. Y ou cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and .
Description Name The pin group with which this vHBA is associated. Pin Group drop-down list box Click this link if you want to create a pin group. Create SAN Pin Gr oup link This can be one of the following: • Disabled • Enabled Persistent Binding field The maximum size of the Fibre Channel frame payload bytes that the vHBA supports.
Changing the WWPN for a vHBA Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Service Profiles . Step 3 Expand the node for the organization that contains the service profile for which you want to change the WWPN.
Resetting the WWPN Assigned to a vHBA from a Pool in a Service Profile T emplate 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.
Deleting a vHBA from a Service Profile Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Service Profiles . Step 3 Expand the node for the organization that contains the service profile from which you want to delete a vHBA.
Unbinding a Service Profile from a Service Profile T emplate Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Service Profiles . Step 3 Expand the node for the organization that includes the service profile you want to unbind.
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 Precau.
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 Har dwar e Installation Guide .
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. Important Configuring the Global Cap Policy Procedure Step 1 In the Navigation pane, click the Equipment tab.
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 .
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, click the Equipment node. Step 3 In the W ork pane, click the Policies tab. Step 4 Click the Power Groups subtab. Step 5 On the icon bar to the right of the table, click + .
Adding a Chassis to a Power Group Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, click the Equipment node. Step 3 In the W ork pane, click the Power Groups tab. Step 4 Right-click the power group to which you want to add a chassis and choose Add Chassis Members .
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.
Description Name 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.
The following configuration options are available: Enabled Y ou 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 1 100 watts. Disabled No power usage limitations are imposed upon the server .
Step 6 Click Save Changes . Viewing the Blade-Level Power Cap Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis . Step 3 Choose the chassis for which you want to view the server power usage.
P ART VI System Management • Managing T ime Zones, page 575 • Managing the Chassis, page 577 • Managing Blade Servers, page 585 • Managing Rack-Mount Servers, page 599 • Starting the KVM Con.
.
CHAPTER 34 Managing T ime Zones This chapter includes the following sections: • T ime Zones, page 575 • Setting the T ime Zone, page 575 • Adding an NTP Server , page 576 • Deleting an NTP Ser.
Adding an NTP Server Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 In the Admin tab, expand All . Step 3 Click Timezone Management . Step 4 In the W ork pane, click the General tab. Step 5 In the NTP Servers area, click the + button on the table icon bar .
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 5.
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. Y ou cannot remove a chassis from Cisco UCS Manager if it is physically present and connected.
Decommissioning a Chassis Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis . Step 3 Choose the chassis that you want to decommission. Step 4 In the W ork pane, click the General tab.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 In the Equipment tab, expand the Equipment node. Step 3 Click the Chassis node. Step 4 In the W ork 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 .
Renumbering a Chassis Y ou 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. T o renumber a blade server , you must physically move the server to a different slot in the chassis.
T oggling the Locator LED T urning on the Locator LED for a Chassis Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis . Step 3 Click the chassis that you need to locate. Step 4 In the W ork pane, click the General tab.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis . Step 3 Choose the chassis for which you want to view the POST results. Step 4 In the W ork pane, click the General tab. Step 5 In the Actions area, click V iew POST Results .
Cisco UCS Manager GUI Configuration Guide, Release 2.0 584 OL-25712-04 Viewing the POST Results for a Chassis.
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 • Bootin.
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. Y ou can also reacknowledge the slot to resolve server mismatch errors and to have Cisco UCS Manager rediscover the blade server in the slot.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers . Step 3 Choose the server that you want to boot. Step 4 In the W ork pane, click the General tab.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers . Step 3 Click the server for which you want to determine the boot order . Step 4 In the W ork pane, click the General tab.
Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Service Profiles . Step 3 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.
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. A voiding Unexpected Server Power Changes If a serve.
Server Power State After Communication Is Disrupted Current Server Power State Desired Power State in Service Profile Powered On Running servers are not shut down regardless of the desired power state in the service profile.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers . Step 3 Choose the server that you want to remove from the chassis. Step 4 In the W ork pane, click the General tab.
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 On the Equipment tab, click the Chassis node. Step 3 In the W ork pane, click the Decommissioned tab.
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 . Y ou cannot perform this procedure if the server is physically present.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers . Step 3 Choose the server for which you want to reset the CMOS. Step 4 In the W ork pane, click the General tab.
Before Y ou Begin 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. Important Procedure Step 1 In the Navigation pane, click the Equipment tab.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers . Step 3 Choose the server for which you want to view the POST results. Step 4 In the W ork pane, click the General tab.
Cisco UCS Manager GUI Configuration Guide, Release 2.0 598 OL-25712-04 Issuing an NMI from a Blade Server.
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.
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.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Rack Mounts > Servers . Step 3 Choose the server that you want to boot. Step 4 In the W ork pane, click the General tab. Step 5 In the Actions area, click Boot Server .
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Rack Mounts > Servers . Step 3 Click the server for which you want to determine the boot order . Step 4 In the W ork pane, click the General tab.
Procedure Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, expand Servers > Service Profiles . Step 3 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.
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. A voiding Unexpected Server Power Changes If a serve.
Server Power State After Communication Is Disrupted Current Server Power State Desired Power State in Service Profile Powered On Running servers are not shut down regardless of the desired power state in the service profile.
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 On the Equipment tab, click the Rack-Mounts node.
Step 4 Choose the rack-mount server that you want to renumber . Step 5 On the Equipment tab, click the Rack-Mounts node. Step 6 In the W ork pane, click the Decommissioned tab.
• T urn on Locator LED • T urn 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.
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 .
V iewing the POST Results for a Rack-Mount Server Y ou can view any errors collected during the Power On Self-T est process for a server and its adapters. Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Rack Mounts > Servers .
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 Se.
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 .
Description Name 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 V iew table. Check the check box in the Mapped column to complete the mapping process.
Description Menu Item 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 W indowed mode. Fit Macros Menu on the KVM T ab Select the keyboard shortcut you want to execute on the remote system.
Starting the KVM Console from a Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers . Step 3 Choose the server that you want to access through the KVM console.
Before Y ou Begin T o 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.
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 • V iewing the P.
Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > IO Modules . Step 3 Choose the I/O module for which you want to view the POST results. Step 4 In the W ork pane, click the General tab.
CHAPTER 40 Backing Up and Restoring the Configuration This chapter includes the following sections: • Backup and Export Configuration, page 619 • Backup T ypes, page 619 • Considerations and Rec.
• All configuration —An XML file that includes all system and logical configuration settings. Y ou can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect.
Import Configuration Y ou 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.
Backup Operations Creating a Backup Operation Before Y ou Begin Obtain the backup server IP address and authentication credentials. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the W ork pane, click the General tab.
Description Name 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. Y ou can use the file generated from this backup to restore the system during disaster recovery .
Description Name The protocol to use when communicating with the remote server . This can be one of the following: • FTP • TFTP • SCP • SFTP Protocol field The hostname or IP address of the location where the backup file is stored.
Running a Backup Operation Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the W ork pane, click the General tab. Step 4 In the Actions area, click Backup . Step 5 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 Pr operties area. If the backup operation is in a disabled state, the fields are dimmed. Step 6 In the Admin State field, click the enabled radio button. Step 7 Modify the appropriate fields.
• Logical configuration Before Y ou 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.
Description Name 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.
a) If the operation does not automatically display in the Pr operties 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.
Modifying an Import Operation Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the W ork pane, click the General tab.
Description Option Deletes the selected import operations and closes the dialog box. OK Restoring the Configuration for a Fabric Interconnect Before Y ou Begin Collect the following information that y.
• FTP • SFTP Step 9 In the Server Information area, complete the following fields: Description Name 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.
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.
Determining the Leadership Role of a Fabric Interconnect Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 In the Equipment tab, expand Equipment > Fabric Interconnects . Step 3 Click the fabric interconnect for which you want to identify the role.
• The firmware system version T o find this information, you can log in with any user account on the Cisco UCS domain. T ip Procedure Step 1 Connect to the console port. Step 2 Power cycle the fabric interconnect: a) T urn off the power to the fabric interconnect.
Example: Fabric(boot)# load /installables/switch/ ucs-6100-k9-system.4.1.3.N2.1.0.211.bin Step 9 After the system image loads, log in to Cisco UCS Manager.
Ctrl+l • • Ctrl+Shift+r Y ou 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.
Cisco UCS Manager GUI Configuration Guide, Release 2.0 638 OL-25712-04 Recovering a Lost Password.
P ART VII System Monitoring • Monitoring T raffic, page 641 • Monitoring Hardware, page 647 • Configuring Statistics-Related Policies, page 663 • Configuring Call Home, page 675 • Managing t.
.
CHAPTER 42 Monitoring T raffic This chapter includes the following sections: • T raffic Monitoring, page 641 • Guidelines and Recommendations for Traf fic Monitoring, page 642 • Creating an Ethe.
• Service profile vHBA • FCoE port • Port channels • Server port A Fibre Channel traffic monitoring session can monitor any of the following traf fic sources: • Uplink Fibre Channel port •.
• 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 traf fic monitoring session after upgrading. T raffic monitoring can impose a significant load on your system resources.
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 T raffic Monitoring Session Procedure Step 1 In the Navigation pane, click the SAN tab. Step 2 On the LAN tab, expand SAN > T raffic Monitoring Sessions > Fabric_Interconnect_Name .
Step 5 Click OK . What to Do Next • Add traffic sources to the traffic monitoring session. • Activate the traffic monitoring session. Adding T raffic Sources to a Monitoring Session Y ou can choose multiple sources from more than one source type to be monitored by a traffic monitoring session.
Activating a T raffic Monitoring Session This procedure describes how to activate an Ethernet traffic monitoring session. T o activate a Fibre Channel monitoring session, select the SAN tab instead of the LAN tab in Step 2. Note Before Y ou Begin A traffic monitoring session must be created.
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 .
Description Option 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 Physical Ports tab Displays the status of all fan modules in the fabric interconnect.
Description Option Displays the status and selected properties of all servers in the chassis. Servers tab Displays the status of the service profiles associated with servers in the chassis. Service Profiles tab Displays the status and selected properties of all IO modules in the chassis.
Monitoring a Blade Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers .
Description Option 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. Y ou can also recover corrupt BIOS firmware from this subtab.
Description Option Displays an overview of the events generated by the server . Y ou can click any event to view additional information. Events tab Provides details about the current FSM task running on the server , including the status of that task. Y ou can use this information to diagnose errors with those tasks.
Description Option 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. Y ou can also recover corrupt BIOS firmware from this subtab.
Description Option Displays an overview of the events generated by the server . Y ou can click any event to view additional information. Events tab Provides details about the current FSM task running on the server , including the status of that task. Y ou can use this information to diagnose errors with those tasks.
Description Option Displays the status and selected properties of all fabric ports in the I/O module. Fabric Ports tab Displays the status and selected properties of all backplane ports in the I/O module. Backplane Ports tab Provides details of faults generated by the I/O module.
In the event of a management interface failure on a fabric interconnect, the managing instance may not change if one of the following occurs: Important • A path to the end-point through the subordinate fabric interconnect does not exist. • The management interface for the subordinate fabric interconnect has failed.
Description Name 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.
Description Name 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.
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 .
Description Name 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.
Interpretation Presence Status Operability Status 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 .
Cisco UCS Manager GUI Configuration Guide, Release 2.0 662 OL-25712-04 Server Disk Drive Monitoring.
CHAPTER 44 Configuring Statistics-Related Policies This chapter includes the following sections: • Configuring Statistics Collection Policies, page 663 • Configuring Statistics Threshold Policies,.
Modifying a Statistics Collection Policy Cisco UCS Manager has one default statistics collection policy for each of the five functional areas. Y ou cannot create additional statistics collection policies and you cannot delete the existing default policies.
Description Name 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 M.
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. Y ou can set both minimum and maximum thresholds.
Description Name The name of the policy . This name can be between 1 and 16 alphanumeric characters. Y ou 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.
• 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: • T o define another threshold property for the class, repeat Step 7. • If you have defined all required properties for the class, click Finish Stage .
• Major • Minor • W arning • Condition • Info e) In the Up and Down fields, enter the range of values that should trigger the alarm. f) In the Alarm T riggers (Below Normal V alue) field, ch.
Adding a Threshold Class to the Uplink Ethernet Port Threshold Policy Y ou cannot create an uplink Ethernet port threshold policy . Y ou can only modify or delete the default policy . T ip Procedure Step 1 In the Navigation pane, click the LAN tab. Step 2 On the LAN tab, expand LAN > LAN Cloud .
• 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: • T o define another threshold property for the class, repeat Step 6. • If you have defined all required properties for the class, click Finish Stage .
• Minor • W arning • Condition • Info e) In the Up and Down fields, enter the range of values that should trigger the alarm. f) In the Alarm T riggers (Below Normal V alue) field, check one or.
b) Click Next . Step 6 In the Threshold Definitions page, do the following: a) Click Add . The Create Thr eshold Definition dialog box opens. b) From the Property T ype field, choose the threshold property that you want to define for the class. c) In the Normal V alue field, enter the desired value for the property type.
Cisco UCS Manager GUI Configuration Guide, Release 2.0 674 OL-25712-04 Configuring Statistics Threshold Policies.
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.
• 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.
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 T riggered Call Home Considerations and Guidelines How you configure Call Home depends on how you intend to use the feature.
Destination Profile Y ou 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.
Call Home Meaning Cisco UCS Fault Call Home Severity Critical conditions, immediate attention needed. Critical (6) Critical Major conditions. Major (5) Major Minor conditions. Minor (4) Minor W arning conditions. W arning (3) W arning Basic notifications and informational messages.
• Configure the contact information. • Configure the email information. • Configure the SMTP server information. • Configure the default CiscoT AC-1 profile.
Description Name 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.
Description Name The email address for the main contact. Cisco Smart Call Home sends the registration email to this email address. 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.
Description Name The IP address or hostname of the SMTP server . If you use a hostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager. Note Host field The port number the system should use to talk to the SMTP server . Enter an integer between 1 and 65535.
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 On the Admin tab, expand All > Communication Management > Call Home .
The system inventory message is sent only to those recipients defined in CiscoT AC-1 profile. Note Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > Communication Management > Call Home . Step 3 In the W ork pane, click the System Inventory tab.
Creating a Call Home Profile By default, you must configure the Cisco T AC-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.
Description Name The group or groups that are alerted based on this Call Home profile. This can be one or more of the following: • Cisco T ac • Diagnostic • Environmental • Inventory • Licen.
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.
Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > Communication Management > Call Home . Step 3 In the W ork pane, click the Policies tab. Step 4 On the icon bar to the right of the table, click + .
Enabling a Call Home Policy Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > Communication Management > Call Home . Step 3 In the W ork pane, click the Policies tab. Step 4 Click the policy that you want to enable and choose Show Navigator .
• Alerts • Critical • Debugging • Emergencies • Errors • Information • Notifications • W arnings Step 5 In the Contact Information area, complete the following fields with the required contact information: Description Name The main Call Home contact person.
Step 7 In the Email Addresses area, complete the following fields with the email information for Smart Call Home alert messages: Description Name The email address that should appear in the From field on Call Home alert messages sent by the system.
Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > Communication Management > Call Home . Step 3 In the W ork pane, click the Profiles tab. Step 4 Right-click the Cisco T AC-1 profile and choose Recipient .
Description Name The date and time for the upcoming data collection. This field is displayed after the first inventory has been sent. Note Next Scheduled field Step 5 Click Save Changes . Registering Smart Call Home Procedure Step 1 In the Navigation pane, click the Admin tab.
CHAPTER 46 Managing the System Event Log This chapter includes the following sections: • System Event Log, page 695 • V iewing the System Event Log for an Individual Server , page 696 • V iewing.
V iewing the System Event Log for an Individual Server Procedure Step 1 In the Navigation pane, click the Equipment tab. Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers . Step 3 Click the server for which you want to view the system event log.
Description Name The protocol to use when communicating with the remote server . This can be one of the following: • FTP • TFTP • SCP • SFTP Protocol 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.
Description Name The username the system should use to log in to the remote server . This field does not apply if the protocol is TFTP . User field The password for the remote server username.
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 After Cisco UCS Manager GUI displays the system event log in the SEL Logs tab, click Print .
Procedure After Cisco UCS Manager GUI displays the system event log in the SEL Logs tab, click Clear . This action triggers an automatic backup if Clear is enabled in the SEL policy Action option box. Note Cisco UCS Manager GUI Configuration Guide, Release 2.
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 .
Configuring the Fault Collection Policy Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > Faults, Events, and Audit Log .
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.
Disabling the Core File Exporter Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 On the Admin tab, expand All > Faults, Events, and Audit Log . Step 3 Click Settings . Step 4 In the W ork pane, click the Settings tab. Step 5 In the TFTP Core Exporter area, click the disabled radio button in the Admin State field.
Description Name 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. Admin State field If the Admin State field is enabled , select the lowest message level that you want displayed.
Description Name 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.
Description Name 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 • Ale.
Cisco UCS Manager GUI Configuration Guide, Release 2.0 708 OL-25712-04 Configuring the Syslog.
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 authe.
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 .
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 5.
CIMC (continued) Management IP (continued) service profiles 376 resetting 595, 608 updating firmware 215 Cisco Discovery Protocol 23, 317, 318 Cisco T AC-1 profile, configuring 692 Cisco UCS Manager 4.
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 server.
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, 20.
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 s.
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 .
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 acces.
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.
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.
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 d.
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,.
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 .
primary authentication (continued) RADIUS provider 142, 144 remote 131 selecting console 151 selecting default 152 T ACACS provider 146 T ACACS+ provider 145 primary VLAN 285 printing system event log.
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 33.
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 47.
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 disasso.
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 .
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.
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.
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, 3.
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 .
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 3.
An important point after buying a device Cisco Systems OL-25712-04 (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought Cisco Systems OL-25712-04 yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data Cisco Systems OL-25712-04 - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, Cisco Systems OL-25712-04 you will learn all the available features of the product, as well as information on its operation. The information that you get Cisco Systems OL-25712-04 will certainly help you make a decision on the purchase.
If you already are a holder of Cisco Systems OL-25712-04, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime Cisco Systems OL-25712-04.
However, one of the most important roles played by the user manual is to help in solving problems with Cisco Systems OL-25712-04. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device Cisco Systems OL-25712-04 along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
