Manual Cisco Ucsd Vblock Mgt Gd

Cisco UCS Director Vblock Management Guide, Release 4.1First Published: March 26, 2014

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000 800 553-NETS (6387)Fax: 408 527-0883

Text Part Number: OL-31365-01

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITEDWARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITHTHE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

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

NOTWITHSTANDINGANYOTHERWARRANTYHEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS"WITH ALL FAULTS.CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OFMERCHANTABILITY, FITNESS FORA PARTICULAR PURPOSEANDNONINFRINGEMENTORARISING FROMACOURSEOFDEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUTLIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERSHAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

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

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnershiprelationship between Cisco and any other company. (1110R)

2014 Cisco Systems, Inc. All rights reserved.

C O N T E N T S

P r e f a c e Preface vii

Audience vii

Conventions vii

Related Documentation ix

Documentation Feedback ix

Obtaining Documentation and Submitting a Service Request ix

C H A P T E R 1 Overview 1

About Vblock 1

PowerPath Virtual Environment Support 2

C H A P T E R 2 Configuration 5

Prerequisites 5

System Requirements 7

Adding a Pod 7

Cisco UCS Manager Accounts 8

Adding a Cisco UCS Manager Account 9

Testing the Connection to an Account 10

Verifying the Discovery of a Cisco UCS Manager Account 11

Viewing the Topology and Connectivity of Devices in a Cisco UCS Domain 11

Exporting the Configuration of a Cisco UCS Manager Account 12

Importing the Configuration of a Cisco UCS Manager Account 13

Vblock Support 13

Adding a Vblock Account 14

Verifying Vblock Account Discovery 15

Network Configuration 16

Adding a Network Device to a Pod 16

Cisco UCS Director Vblock Management Guide, Release 4.1 OL-31365-01 iii

Verifying Network Device Details in a Pod Environment 17

C H A P T E R 3 Network Configuration for Cisco UCS Director Baremetal Agent 19

About the Network Configuration Options 19

Single Network for Management and PXE 19

Prerequisites and Assumptions for a Single Network Configuration 20

Configuring Cisco UCS Director Baremetal Agent for a Single Network 21

Separate Networks for Management and PXE 23

Prerequisites and Assumptions for a Separate Network Configuration 24

Configuring Cisco UCS Director Baremetal Agent for Separate Networks 25

Configuring Cisco UCS Director Baremetal Agent as a DHCP Server 29

Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address 29

C H A P T E R 4 Operations and Management 31

Vblock Operations Task Roadmap 31

Creating an Organization 34

Configuring the Chassis/FEX Discovery Policy 35

Creating a UUID Pool 35

Creating a MAC Pool 36

Creating a WWNN Pool 37

Creating a WWPN Pool 37

Creating a Network Control Policy 38

Creating a vNIC Template 40

Creating a VSAN 43

Creating a vHBA Template 44

Creating a LAN Boot Policy 46

Creating a SAN Boot Policy 47

Creating a vNIC 49

Creating a vHBA 49

Creating a Network Policy 50

Creating a Storage Policy 52

C H A P T E R 5 Sample Orchestration Workflows 55

Navigating to a Predefined Orchestration Workflow 55

Provisioning a Stateless Blade Server Orchestration Workflow 56

Cisco UCS Director Vblock Management Guide, Release 4.1iv OL-31365-01

Contents

Stateless Blade Server Orchestration Workflow Overview 56

Modifying the Workflow Priority 58

Creating the UCS Service Profile Task 59

Choosing the Cisco UCS Server 60

Associating the Cisco UCS Service Profile 61

Powering Off the Cisco UCS Server 62

Setting Up PXE Boot 63

Creating a VNX LUN 65

Creating a VNX Storage Group 66

Adding a VNX Host Initiator Entry 67

Configuring Generic Storage Area Network Zoning 68

Adding Hosts to a VNX Storage Group 70

Adding a LUN to a VNX Storage Group 71

Modifying the Cisco UCS Service Profile Boot Policy 72

Modifying the Cisco UCS Boot Policy LUN ID 73

Resetting the UCS Server 74

Monitoring PXE Boot 75

Adding a VLAN to a Service Profile 76

Disassociating the Cisco UCS Service Profile 77

Configuring the Waiting for Specific Duration Task 78

Provisioning a File System Mounting Orchestration Workflow 79

File System Mounting Orchestration Workflow Overview 79

Creating a VNX File System 80

Adding a VNX NFS Export Task 81

Mounting the NFS Datastore 82

Validating and Executing an Orchestration Workflow 83

C H A P T E R 6 Troubleshooting 85

Troubleshooting Cisco UCS Director Connectivity 85

Troubleshooting Cisco UCS Director Baremetal Agent Connectivity 86

Cisco UCS Director Vblock Management Guide, Release 4.1 OL-31365-01 v

Contents

Cisco UCS Director Vblock Management Guide, Release 4.1vi OL-31365-01

Contents

Preface

This preface contains the following sections:

Audience, page vii

Conventions, page vii

Related Documentation, page ix

Documentation Feedback, page ix

Obtaining Documentation and Submitting a Service Request, page ix

AudienceThis guide is intended primarily for data center administrators who use Cisco UCS Director and/or CiscoUCS Director Express and who have responsibilities and expertise in one or more of the following:

Server administration

Storage administration

Network administration

Network security

Virtualization and virtual machines

ConventionsIndicationText Type

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

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

GUI elements

Document titles appear in this font.Document titles

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

Cisco UCS Director Vblock Management Guide, Release 4.1 OL-31365-01 vii

IndicationText Type

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

System output

CLI command keywords appear in this font.

Variables in a CLI command appear in this font.

CLI commands

Elements in square brackets are optional.[ ]

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

{x | y | z}

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

[x | y | z]

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

string

Nonprinting characters such as passwords are in angle brackets.< >

Default responses to system prompts are in square brackets.[ ]

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

!, #

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

Note

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

Tip

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

Caution

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

Timesaver

Cisco UCS Director Vblock Management Guide, Release 4.1viii OL-31365-01

PrefaceConventions

IMPORTANT SAFETY INSTRUCTIONS

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

SAVE THESE INSTRUCTIONS

Warning

Related DocumentationCisco UCS Director Documentation Roadmap

For a complete list of Cisco UCS Director documentation, see the Cisco UCS Director DocumentationRoadmap available at the following URL: http://www.cisco.com/en/US/docs/unified_computing/ucs/ucs-director/doc-roadmap/b_UCSDirectorDocRoadmap.html.

Cisco UCS Documentation Roadmaps

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

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

The Cisco UCS B-Series Servers Documentation Roadmap includes links to documentation for CiscoUCSManager and Cisco UCSCentral. TheCiscoUCSC-Series Servers Documentation Roadmap includeslinks to documentation for Cisco Integrated Management Controller.

Note

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

Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, submitting a service request, and gathering additional information,see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Ciscotechnical documentation.

Subscribe to theWhat's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feedand set content to be delivered directly to your desktop using a reader application. The RSS feeds are a freeservice and Cisco currently supports RSS version 2.0.

Cisco UCS Director Vblock Management Guide, Release 4.1 OL-31365-01 ix

PrefaceRelated Documentation

Cisco UCS Director Vblock Management Guide, Release 4.1x OL-31365-01

PrefaceObtaining Documentation and Submitting a Service Request

C H A P T E R 1Overview

This chapter contains the following sections:

About Vblock, page 1

PowerPath Virtual Environment Support, page 2

About VblockVblock is an integrated hardware and software environment that you can use for virtualized and nonvirtualizedconverged computing, networking, and storage solutions. You can use Vblock for the following:

Data centers that need high availability and scalable Vblock storage solutions to reduce operating costsand converge the infrastructure so that it supports hybrid cloud computing.

Interface to private cloud services that provides computing resources for end users and virtualizedapplications.

The hardware deployed for the Vbock environment is highly modular and varies depending on the specificVblock rack-mount scheme needed for each customer deployment. For more information, see CiscoValidated Designs on the web.

Note

The Vblock environment has the following components:

Cisco UCSDirector and Cisco UCSDirector Baremetal Agent that are installed and configured on eithera VMware vCenter host or Hyper-V host to standardize and simplify the configuration of networking,storage, and security settings for multiple hosts and to monitor the host compliance. See the Cisco UCSDirector Installation Guide andCisco UCSDirector Baremetal Agent Setup Guide for more information.

The Vblock virtualization software, computing, and the following Vblock components that are locatedin one rack to provide scalable storage:

Vblock System 200 Series with EMC VNX storage.

Vblock System 300 Series with EMC VNX storage.

Vblock System 720 Series with EMC Symmetrix VMAX 10K and 20K storage.

Cisco UCS Director Vblock Management Guide, Release 4.1 OL-31365-01 1

Cisco Nexus components that provide routing and switching functionality.

Cisco UCS Manager that provides unified, embedded management of all software and hardwarecomponents in Cisco UCS Director including virtual machines (VMs). The following figure shows theVblock hardware and software components.

Figure 1: Vblock System Series Hardware and Software Component with EMC VNX Storage

PowerPath Virtual Environment SupportPowerPath Virtual Environment (VE) is an EMC feature that is enabled between the EMC storage componentand VMware host. EMC PowerPath VE automates and optimizes data path pools in virtual environments byautomating failover and recovery operations, optimizing load balancing, and standardizing path management.

The PowerPath VE software is installed on the VMware host. Once the PowerPath VE feature is enabled, ahost can discover the EMC storage component. Fromwithin Cisco UCSDirector, the storage can be discoveredand associated as a data store.

Cisco UCS Director Vblock Management Guide, Release 4.12 OL-31365-01

OverviewPowerPath Virtual Environment Support

Configuring PowerPath VE on the VMware host and EMC storage component is outside the scope ofCisco UCS Director.

Note



C H A P T E R 2Configuration


The procedures in this chapter assume you are logged into Cisco UCS Director.Note

Prerequisites, page 5

System Requirements, page 7

Adding a Pod, page 7

Cisco UCS Manager Accounts, page 8

Vblock Support, page 13

Network Configuration, page 16

PrerequisitesDescriptionPrerequisite

For more information, see the VCE Vblock Series700 Technical Specifications, VCE Vblock Series300 Technical Specifications.

Hardware Connectivity

For more information about pod licenses, see CiscoUCS Director Install and Upgrade Guides.

Vblock License

Verify that network connectivity conforms to theEMCVNXSeries Technical Specifications and EMCSymetrix VMAX 10K and 20K specifications.

One DHCP server is permitted in the VLAN whereCisco UCS Director Baremetal Agent is installed.

Network Connectivity


DescriptionPrerequisite

Verify Cisco UCSDirector connects to the following:

Cisco UCS Manager

EMC VNX unified storage system

EMCSymmetrix VMAX 10K and 20K storage

Cisco UCS Director Baremetal Agent

Cisco Nexus 5000 and 5500 Series switchesand Cisco Nexus 1000V switch

Servers must be reachable from Cisco UCS Director.See the Cisco UCS Director Baremetal AgentInstallation Guide for more information aboutestablishing this connectivity.

Verify CiscoUCSDirector Baremetal Agent connectsto Cisco UCS Director.

Servers must be reachable from Cisco UCS DirectorBaremetal Agent. See the Cisco UCS DirectorBaremetal Agent Installation Guide for moreinformation about establishing this connectivity.

Verify baremetal provisioning is on the same networkas Cisco UCS Director Baremetal Agent.

Baremetal provisioning reachability.

Configure the DHCP server with the appropriate IPaddress range on Cisco UCS Director BaremetalAgent. The DHCP server can also be configured touse Cisco UCSDirector Baremetal Agent as the nextserver. For more information, see the NetworkConfiguration for Cisco UCS Director BaremetalAgent chapter for more information.

DHCP setup

Enable remote database access on Cisco UCSDirector Baremetal Agent. For more information, seethe Network Configuration for Cisco UCS DirectorBaremetal Agent chapter for more information.

Cisco UCS Director database setup

Add an entry for Cisco UCS Director BaremetalAgent (reachable IP address on the same VLAN).For more information, see the Network Configurationfor Cisco UCS Director Baremetal Agent chapter formore information.

Cisco UCS Director /etc/hosts file

Add an entry for Cisco UCS Director (reachable IPaddress on the same VLAN). See the NetworkConfiguration for Cisco UCS Director BaremetalAgent chapter for more information.

Cisco UCS Director Baremetal Agent /etc/hosts file

All versions are supported from ESXI 4.0 to ESXi5.5.

VMware (vCenter Server/ESXI/ESXi)


ConfigurationPrerequisites

System RequirementsRequirementComponent

Two Cisco Nexus 5000/5500 Series switches

Two Cisco UCS 6100 or 6200 Series FabricInterconnects

Cisco Nexus 1000V switch

Networking

One or multiple Cisco UCS chassis with modulesthat have two Fabric Extenders per chassis

Computing

EMC VNX unified storage systemStorage

Version 2.5.0.2 and later versionsCisco UCS Director

Version 2.5.0.2 and later versionsCisco UCS Director Baremetal Agent

2 GB memory and minimum 3000-GHz CPUCisco UCS Directorresource reservation

2 GB memory and minimum 2000-GHz CPUCisco UCS Director Baremetal Agentresourcereservation

All versions are supported from ESXI 4.0 to ESXi5.5.

VMware (vCenter Server/ESXI/ESXi)

Adding a Pod

Step 1 On the menu bar, choose Administration > Physical Accounts.Step 2 Click the Pods tab.Step 3 Click Add.Step 4 In the Add Pod dialog box, complete the following fields:

DescriptionName

A descriptive name for the pod.Name field

Choose the site where you want to add the pod. If your environment doesnot include sites, you can omit this step.

Site drop-down list


ConfigurationSystem Requirements

DescriptionName

Choose the type of pod that you want to add. This can be one of thefollowing supported types:

Generic

VSPEX

Vblock

If you choose any type of pod except the generic type, you must have alicense for that pod type. In addition, the nongeneric pod types accommodateonly specific physical and virtual components. A generic pod does notrequire a specific pod license. You can add any type of physical or virtualcomponent to a generic pod. For more information about pod licenses, seeCisco UCS Director Install and Upgrade Guides.

Type drop-down list

(Optional) A description of the pod.Description field

The physical location of the pod. For example, this field could include thecity or other internal identification used for the pod.

Address field

Check this check box to hide the pod if you do not want it to show in theConverged Check View. You can continue to add or delete accounts fromthe pod.

For example, you can use this check box to ensure that a pod that does nothave any physical or virtual elements is not displayed in the ConvergedView.

Hide Pod check box

Step 5 Click Add.

What to Do Next

Add one or more accounts to the pod.

Cisco UCS Manager AccountsEach Cisco UCS Manager account represents a single Cisco UCS domain that you want to have managed by.

For an environment that does not include Cisco UCS Central, you create Cisco UCS Manager accounts in apod.

For an environment that includes Cisco UCS Central, you must create a Cisco UCS Central account undermulti-domain managers. All Cisco UCS domains that are registered with that Cisco UCS Central, and theirrelated Cisco UCS Manager accounts are brought into when the Cisco UCS Central account is created. You


ConfigurationCisco UCS Manager Accounts

can assign one or more of those Cisco UCS Manager accounts from the Cisco UCS Central account to a podif needed. You can also register a Cisco UCS Manager account with a Cisco UCS Central account.

Adding a Cisco UCS Manager Account

Before You Begin

Add the pod to which this Cisco UCS Manager account belongs.

Step 1 On the menu bar, choose Administration > Physical Accounts.Step 2 Click the Physical Accounts tab.Step 3 Click Add.Step 4 In the Add Account dialog box, complete the following fields:

DescriptionName

Choose the pod to which this account belongs.Pod drop-down list

Choose the category type. You must choose Computing. This is the typeof infrastructure for the account.

Category Type drop-down list

Choose the account type. You must choose UCSM.Account Type drop-down list

Choose the type of authentication to be used for this account. This can beone of the following:

Locally AuthenticatedA locally authenticated user account isauthenticated directly through the fabric interconnect and can beenabled or disabled by anyone with admin or AAA privileges.

Remotely AuthenticatedA remotely authenticated user account isany user account that is authenticated through LDAP, RADIUS, orTACACS+.

Authentication Type drop-down list

Choose how you want to have the servers in this account managed. Thiscan be one of the following:

All ServersAll servers are managed by . This option is the default.If you choose this option, all servers are added in the Managed state.

Selected ServersOnly selected servers are managed by . You canadd and remove servers from the managed server list as needed. Ifyou choose this option, all servers are added in the Unmanaged state.

Server Management drop-down list

A unique name that you assign to this account.Account Name field

The IP address of Cisco UCS Manager. For a cluster configuration, this isthe virtual IP address.

Server Address field


ConfigurationAdding a Cisco UCS Manager Account

DescriptionName

The username that this account will use to access Cisco UCSManager. Thisusername must be a valid account in Cisco UCS Manager.

User ID field

The password associated with the username.Password field

The authentication domain for the remotely authenticated account.

This field is not displayed if you are using a locally authenticated account.

UCS Authentication Domain field

Choose the transport type that you want to use for this account. This can beone of the following:

http

https

Transport Type drop-down list

The port used to access Cisco UCS Manager.Port field

(Optional) A description of this account.Description field

The email address that you can use to contact the administrator or otherperson responsible for this account.

Contact Email field

The location of this account.Location field

(Optional) The name of the service provider associated with this account,if any.

Service Provider field

Step 5 Click Add.

Cisco UCS Director tests the connection to Cisco UCS Manager. If that test is successful, it adds the CiscoUCS Manager account and discovers all infrastructure elements in Cisco UCS Manager that are associatedwith that account, including chassis, servers, fabric interconnects, service profiles, and pools. This discoveryprocess and inventory collection cycle takes approximately five minutes to complete.

The polling interval configured on the System Tasks tab specifies the frequency of inventory collection.

Testing the Connection to an AccountYou can test the connection at any time after you add an account to a pod.

Step 1 On the menu bar, choose Administration > Physical Accounts.Step 2 Click the tab for the type of account you want to test.


ConfigurationTesting the Connection to an Account

For example, click the Physical Accounts tab or theMulti-Domain Managers tab.

Step 3 In the table, click the row of the account for which you want to test the connection.Step 4 Click Test Connection.Step 5 When the connection test has completed, click Close.

What to Do Next

If the connection fails, verify the configuration of the account, including the username and password. If thoseare correct, determine whether there is a network connectivity problem.

Verifying the Discovery of a Cisco UCS Manager Account

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left column, choose the pod that includes the Cisco UCS Manager account that you want to verify.

The left column tree structure lists nodes for Sites, Unassigned Pods, andMulti-Domain Managers. When aSites node is expanded, all the pods for that site node are displayed. When you expand an Unassigned Podsnode, all the pods that are not assigned to any site are displayed. When you expand the Multi-DomainManagerslist, all multi-domain manager account types that you added to Cisco UCS Director are displayed.

Note

Step 3 Click the Compute Accounts tab.Step 4 In the table, click the row of the account that you want to verify.Step 5 Click View Details.

Cisco UCS Director displays a set of tabs that contain information about the components of that account that it hasdiscovered.

Step 6 Click Back to return to the Compute Accounts tab.

Viewing the Topology and Connectivity of Devices in a Cisco UCS Domain

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left column, choose the pod that includes the Cisco UCSManager account for which you want to view the topology.Step 3 Click the Compute Accounts tab.Step 4 In the table, click the row of the account.Step 5 Click View Connectivity.

The Topology View - UCS Device Connectivity dialog box is displayed with a view of the topology and connectivityof the devices in the Cisco UCS Domain.

Step 6 If desired, you can modify the following view options:


ConfigurationVerifying the Discovery of a Cisco UCS Manager Account

View Mode drop-down listAdjusts the spacing and positioning of the devices. The mode determines whichoptions are available for you to customize the topology view. You can choose between the following view modes:

Hierarchical

Concentric

Circular

Force Directed

Show Link Labels check boxShows or hides labels on the links between devices. These labels might not displayon some view modes.

Allow Item Spacing check boxIncreases the distance between devices for the Hierarchical view mode.

Distance controlAdjusts the distance between devices for the Concentric view mode.

Radius controlChanges the radius of the circle and therefore adjusts the distance between devices for the Circularview mode.

Rigidity controlAdjusts the rigidity for the Force Directed view.

Force Distance controlAdjusts the distance between devices for the Force Directed view.

Step 7 Click Close to return to the Compute Accounts tab.

Exporting the Configuration of a Cisco UCS Manager AccountCisco UCS Director exports a file named Ucs-Timestamp-configuration.zip to the locationconfigured for downloads in your browser.

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left pane, choose the pod that includes the Cisco UCS Manager account for which you want to export the

configuration.

Step 3 In the right pane, click the Compute Accounts tab.Step 4 In the table, click the row for the account.Step 5 Click Export Configuration.Step 6 In the Export UCS Configuration dialog box, click Submit.Step 7 When the configuration export is complete, click Close.


ConfigurationExporting the Configuration of a Cisco UCS Manager Account

Importing the Configuration of a Cisco UCS Manager AccountYou can import a configuration that has been exported from a Cisco UCS Manager account in Cisco UCSDirector, or from Cisco UCS Manager.

When you import a configuration into a Cisco UCS Manager account, you overwrite any existingconfiguration in that account.

Note

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left column, choose the pod that includes the Cisco UCS Manager account for which you want to import the

configuration.

Step 3 Click the Compute Accounts tab.Step 4 In the table, click the row of the account for which you want to import the configuration.Step 5 Click Import Configuration.Step 6 On the Upload Configuration screen of the Import UCS Configuration wizard, do the following:

a) Click Browse and navigate to the configuration file that you want to import.b) Click Upload.c) When the file upload is complete, click OK.d) Click Next.

Step 7 On the Select Configuration screen of the Import UCSConfigurationwizard, check one of the following check boxes:

DescriptionOption

Imports all configuration settings in the file.Import All Configuration

Imports only the configuration settings that you choose.Customize Import

Step 8 Click Submit.Step 9 When the configuration import is complete, click Close.

Vblock SupportCisco UCS Director helps support the unified storage systems in the following ways:

Auto-discovery

Monitoring

Visibly manage all the VNX componentsRAID groups, storage pools, logical unit numbers (LUNs),storage groups, initiators, file systems, volumes, Network File System (NFS) and Common Internet FileSystem (CIFS).


ConfigurationImporting the Configuration of a Cisco UCS Manager Account

Make sure that you create a pod before you add a Vblock account. For more information, see Adding aPod.

Note

Adding a Vblock Account

Before You Begin

Make sure that you create a pod before you add a Vblock account. For more information, see Adding a Pod.

Step 1 On the menu bar, choose Administration > Physical Accounts.Step 2 In the Physical Acccounts tab, click Add.Step 3 In the Add Account dialog box, complete the following fields:

DescriptionName

Choose Vblock for this account.Pod drop-down list

Choose Storage.Category drop-down list

The account type EMC VNX is selected for you when Storage is selected asthe category.

Account Type drop-down list

Choose from the following VNX account subtypes:

VNX FileX-Blade enclosured, 2 to 8 blades, configurable failoveroptions, and flexible I/O connectivity. There is one datamover per license.

VNX BlockStorage or data processor enclosure, dual active storageprocessors, automatic failover, and flexible I/O connectivity. There are twoservice providers per license.

VNX UnifiedSingle platform for VNX File and VNX Block. There aretwo service providers per license.

Account Sub Type drop-down list

Choose the Authentication Type for this account.Authentication Type drop-down list

The account name.Account Name field

The IP address of the Vblock server.Server Address field

The user ID of the Vblock server.User ID field

The password for the Vblock server.Password field


ConfigurationAdding a Vblock Account

DescriptionName

Choose the transport type that you want to use for the account. This can be oneof the following:

http

https

Transport Type drop-down list

The port (80 is the default).Port field

The account description.Description field

The contact's email.Contact Email field

The site location for this account.Location field

The service provider name, if any.Service Provider field

Step 4 Click Add.Cisco UCS Director automatically discovers all storage elements in the Vblock account, including aggregates, disks,volumes, LUNs, and Qtree.

Step 5 In the Physical Acccounts pane, click the account.Step 6 Click Test Connection.

What to Do Next

Verify that the account has been discovered. The discovery process typically takes a few minutes.

Verifying Vblock Account DiscoveryAfter you add a Cisco UCSManager to a Cisco UCSDirector Vblock environment, all discovered componentsof this environment are displayed at the account level.

Step 1 On the menu bar, choose Physical > Storage.Step 2 In the Storage pane, click the Vblock account.Step 3 Click the System Summary tab.

The Summary reports for this account appear.


ConfigurationVerifying Vblock Account Discovery

Network ConfigurationCisco UCS Director enables the management, orchestration, and monitoring of multiple network devices andfabric platforms from Cisco and select vendors:

Cisco network and fabric support for Cisco Nexus switches.

Brocade network and fabric support.

Cisco UCS fabric interconnects that operate in the N-Port Virtualization (NPV) mode in which the serverFibre Channel traffic is either manually or automatically pinned to a specific Fibre Channel over Ethernet(FCoE) uplink.

The network installation includes the following tasks:

Adding a Cisco Nexus device to Cisco UCS Director

Verifying managed network device details

See Compatibility Matrix for Cisco UCS Director for more specific network support information.Note

Adding a Network Device to a Pod

Step 1 On the menu bar, choose Administration > Physical Accounts.Step 2 In theManaged Network Elements tab, click the Add Network Element icon.Step 3 In the Add Network Element dialog box, complete the following fields:

DescriptionName

Choose a pod.Pod drop-down list

Choose one of the following network device options:

Brocade Fabric OS

Brocade Network OS

Force10 (FTOS)

Cisco IOS

Cisco Nexus OS

Cisco ASA

Device Category drop-down list

The IP address of the device.Device IP field

Choose the protocol to use to communicate with the device (telnet or ssh).Protocol drop-down list


ConfigurationNetwork Configuration

DescriptionName

The port number for the device. The default is port 23.Port field

The login username.Login field

The login password for the device.Password field

The enable password for the device.Enable Password field

Step 4 Click Submit.Step 5 In the Converged pane, click the pod.

The pod infrastructure details appear.

What to Do Next

Verify that the managed network devices are configured properly.

Verifying Network Device Details in a Pod EnvironmentAfter the network device is added to the pod, all discovered components of the pod environment are displayedat the account level.

Step 1 On the menu bar, choose Physical > Network.Step 2 In the Network pane, click the pod.Step 3 Click theManaged Network Elements tab.Step 4 Click the network device, and click View Details.

All information about the device appears in the Summary tab. You can choose other tabs to see specific details, suchas interfaces, modules, VLANs, port profiles, and so on, depending on the network device.


ConfigurationVerifying Network Device Details in a Pod Environment


ConfigurationVerifying Network Device Details in a Pod Environment

C H A P T E R 3Network Configuration for Cisco UCS DirectorBaremetal Agent


About the Network Configuration Options, page 19

Single Network for Management and PXE, page 19

Separate Networks for Management and PXE, page 23

Configuring Cisco UCS Director Baremetal Agent as a DHCP Server, page 29

Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address, page 29

About the Network Configuration OptionsYou can choose between the following network configuration options for Cisco UCS Director BaremetalAgent:

Single network for management and PXE

Separate networks for management and PXE

You should choose the network configuration option that best meets the requirements of your environment.

Single Network for Management and PXEWe recommend that you choose this network configuration option if your environment permits the followingto be hosted on the same network interface and layer 2 network:

Services provided by Cisco UCS Director Baremetal Agent, such as DHCP, TFTP, and HTTP


Management traffic between Cisco UCS Director Baremetal Agent and Cisco UCS Director or otherdevices and appliances

Figure 2: Sample Topology for a Single Network

Prerequisites and Assumptions for a Single Network ConfigurationIf you plan to configure Cisco UCS Director Baremetal Agent with a single network configuration, ensurethat your environment meets the following prerequisites and assumptions:

Cisco UCS Director has been installed and the network interface configured, as described in theappropriate Cisco UCS Director installation guide.

Cisco UCS Director is reachable through a web browser and you can log in.

Cisco UCS Director Baremetal Agent has been installed, as described in Installation of Cisco UCSDirector Baremetal Agent and no additional configuration has been performed.

The required single Management and PXE VLAN is provisioned and available as a virtual port groupor port profile that VMs can be attached to or leverage.


Network Configuration for Cisco UCS Director Baremetal AgentPrerequisites and Assumptions for a Single Network Configuration

Configuring Cisco UCS Director Baremetal Agent for a Single Network

This procedure assumes that the VMs have been created in the VMware vSphere 5.1 hypervisor. Althoughconfigurations on other releases of VMware vSphere or on other hypervisors may vary slightly, the requiredsteps are applicable to all supported hypervisors and supported releases.

Note

Step 1 If necessary, power on the Cisco UCS Director Baremetal Agent VM.Step 2 Open the VMware vSphere VM Console for the Cisco UCS Director Baremetal Agent VM.Step 3 When prompted, configure the network interface as necessary.

By default, this interface is set to use DHCP as described in Configuring Cisco UCS Director Baremetal Agent as aDHCP Server, on page 29. However, you can configure a static IP address, if required, as described in ConfiguringCisco UCS Director Baremetal Agent to Use a Static IP Address, on page 29

Step 4 After the network is configured and the Cisco UCS Director Baremetal Agent VM has completely booted up, close theVMware vSphere VM Console.The VM is fully booted up when you see a screen that prompts with the following text: To manage this VMbrowse to https://IP_address:443/, where IP_address represents the IP address of the CiscoUCSDirectorBaremetal Agent VM.

Step 5 Open an SSH session to the IP Address for the Cisco UCS Director Baremetal Agent VM, and use the following defaultcredentials if you have not already changed them:

User nameroot

Passwordpxeboot

Step 6 Use ifconfig to verify that the network interface eth0 is configured properly and make a note of the IP address.Step 7 Navigate to the /opt/infra/networkServices/ directory.

Step 8 In the run.sh file, enter the IP address of the Cisco UCS Director Baremetal Agent eth0 interface for the followingparameters:

-DpxeServer.ip=

-DpxeServer.mgmt_vlan_ip=

Step 9 Open a new SSH session to the IP address for the Cisco UCS Director VM.In a multi-node setup, you need to open the SSH session to the VM for the Inventory databasenode.

Note

The following default credentials for this VMmight have been changed during the configuration of Cisco UCS Director:

User nameshelladmin

Passwordchangeme

Step 10 In the shelladmin, do the following to add the Cisco UCS Director Baremetal Agent hostname and IP address:a) From the menu, choose the option for Add Cisco UCS Director Baremetal Agent Hostname/IP

and press Enter.


Network Configuration for Cisco UCS Director Baremetal AgentConfiguring Cisco UCS Director Baremetal Agent for a Single Network

b) When prompted, enter the IP Address and Hostname of the Cisco UCS Director Baremetal Agent VM.

Step 11 In the shelladmin, do the following to enable the database for Cisco UCS Director Baremetal Agent:In a multi-node setup, you need to perform this step on the Inventory databasenode.

Note

a) From the menu, choose the option for Enable Database for Cisco UCS Director BaremetalAgent and press Enter.

b) Enter y for yes.c) When prompted, enter the IP Address or Hostname of the Cisco UCS Director Baremetal Agent VM.

Step 12 From the shelladmin menu, choose the option for Quit and exit the console.Step 13 Return to the SSH console for the Cisco UCS Director Baremetal Agent VM.Step 14 Navigate to the /etc/ directory.

Step 15 Copy the dhcpd.conf.sample file, as follows: cp ./dhcpd.conf.sample ./dhcpd.conf

Step 16 Edit the dhcpd.conf file to set up the DHCP services that are required for PXE booting.The following sample dhcpd.conf file includes the DHCP services.

The next-server line is required and must include the IP address of the Cisco UCS Director BaremetalAgent VM.

Note

#

# DHCP Server Configuration file.

# see /usr/share/doc/dhcp*/dhcpd.conf.sample

#

ddns-update-style interim;

ignore client-updates;

subnet 209.165.202.158 netmask 255.255.255.224 {

option routers 209.165.200.254;

option subnet-mask 255.255.255.224;

option nis-domain "domain.org";

option domain-name "domain.org";

option domain-name-servers 209.165.201.1;

option time-offset -18000; # Eastern Standard Time

range dynamic-bootp 209.165.200.225 209.165.200.254;

default-lease-time 21600;

max-lease-time 43200;

allow booting;

allow bootp;

next-server 209.165.201.30; # IP of my PXE server

filename "/pxelinux.0";

}


Network Configuration for Cisco UCS Director Baremetal AgentConfiguring Cisco UCS Director Baremetal Agent for a Single Network

Step 17 At the prompt, enter service dhcpd restart to restart the DHCP services.Step 18 If DNS is not configured on Cisco UCS Director Baremetal Agent, add the hostname and IP address of Cisco UCS

Director to the /etc/hosts file to ensure DNS hostname to IP address resolution.

Step 19 Navigate to the /opt/infra/ directory.

Step 20 Run the configure.sh script and, when prompted, provide the IP address of Cisco UCS Director as a parameter.In a multi-node setup, you need to perform this step on the Inventory databasenode.

Note

Step 21 In a web browser, navigate to the IP address for Cisco UCS Director and verify that Cisco UCS Director BaremetalAgent is available and active, as follows:

a) Login as a user with admin privileges.b) From the menu bar, choose Administration > Physical Accounts.c) Click the Network Services Agent tab.d) Verify that the list includes Cisco UCS Director Baremetal Agent and that the status is Active.e) If you do not see Cisco UCS Director Baremetal Agent in the list, click Refresh to add it to the list of available

network services agents.

Separate Networks for Management and PXEWe recommend that you choose this network configuration option if your environment does not permit thefollowing to be hosted on the same network interface and layer 2 network:

On the PXE network, services provided by Cisco UCS Director Baremetal Agent, such as DHCP, TFTP,and HTTP


Network Configuration for Cisco UCS Director Baremetal AgentSeparate Networks for Management and PXE

On the Management network, traffic between Cisco UCS Director Baremetal Agent and Cisco UCSDirector or other devices and appliances

Figure 3: Sample Topology for Separate PXE and Management Networks

Prerequisites and Assumptions for a Separate Network ConfigurationIf you plan to configure Cisco UCS Director Baremetal Agent with a separate network configuration, ensurethat your environment meets the following prerequisites and assumptions:

Cisco UCS Director has been installed and the network interface configured, as described in theappropriate Cisco UCS Director installation guide.

Cisco UCS Director is reachable through a web browser and you can log in.

Cisco UCS Director Baremetal Agent has been installed, as described in Installation of Cisco UCSDirector Baremetal Agent, no additional configuration has been performed and the VM is powered off.

The following networks are provisioned and available as a virtual port group or port profile that VMscan be attached to or leverage:

Management (MGMT) networkUsed for traffic between Cisco UCS Director Baremetal Agentand Cisco UCS Director

PXE networkUsed for PXE services traffic, such as DHCP, HTTP, and TFTP


Network Configuration for Cisco UCS Director Baremetal AgentPrerequisites and Assumptions for a Separate Network Configuration

The PXE network/VLANmust be configured as the native, or default, VLAN on the server. For example,for a Cisco UCS server, edit the vNIC template associated with the server and choose the PXEnetwork/VLAN as the native VLAN. You can perform this configuration in Cisco UCSManager or CiscoUCS Director.

Note

Configuring Cisco UCS Director Baremetal Agent for Separate Networks

This procedure assumes that the VMs have been created in the VMware vSphere 5.1 hypervisor. Althoughconfigurations on other releases of VMware vSphere or on other hypervisors may vary slightly, the requiredsteps are applicable to all supported hypervisors and supported releases.

Note

Step 1 In the VMware vSphere Client interface, right-click the Cisco UCS Director Baremetal Agent VM and choose EditSettings.

Step 2 On the Hardware tab of the Virtual Machine Properties dialog box, click Add.Step 3 On the Device Type page of the Add Hardware dialog box, choose Network Adapter and click Next.

The network adapter option might read Ethernet Adapter.

Step 4 On the Network Type page of the Add Hardware dialog box, do the following:a) From the Type drop-down list, choose an adapter type.

You can accept the default value of Flexible.

b) From the Network Label drop-down list, choose the network/VLAN associated with PXE traffic to which you wantto connect this network interface.

c) Click Next.

Step 5 Review the summary and click Finish to add the network adapter to the VM.Step 6 Click OK to close the Virtual Machine Properties dialog box for the VM.Step 7 Power on the Cisco UCS Director Baremetal Agent VM.Step 8 Open the VMware vSphere VM Console for the Cisco UCS Director Baremetal Agent VM.Step 9 When prompted, configure the network interface as necessary.

By default, this interface is set to use DHCP as described in Configuring Cisco UCS Director Baremetal Agent as aDHCP Server, on page 29. However, you can configure a static IP address, if required, as described in ConfiguringCisco UCS Director Baremetal Agent to Use a Static IP Address, on page 29

Step 10 After the network is configured and the Cisco UCS Director Baremetal Agent VM has completely booted up, close theVMware vSphere VM Console.The VM is fully booted up when you see a screen that prompts with the following text: To manage this VMbrowse to https://IP_address:443/, where IP_address represents the IP address of the CiscoUCSDirectorBaremetal Agent VM.

Step 11 Open an SSH session to the IP Address for the Cisco UCS Director Baremetal Agent VM, and use the following defaultcredentials if you have not already changed them:


Network Configuration for Cisco UCS Director Baremetal AgentConfiguring Cisco UCS Director Baremetal Agent for Separate Networks

User nameroot

Passwordpxeboot

Step 12 Use ifconfig to verify that the network interface eth0 is configured properly and make a note of the IP address.Step 13 Navigate to the etc/sysconfig/nework-scripts/ directory.

Step 14 Copy the ifcfg-eth0 file to ifcfg-eth1, as follows: cp ./ifcfg-eth0 ./ifcfg-eth1

Step 15 Edit the ifcfg-eth1 file to set up the PXE traffic interface.The following sample ifcfg-eth1 file shows the values that you need to update in the file.

If you defined the GATEWAY variable for the eth0 interface, do not define that variable for the eth1 interface.Note

DEVICE=eth [number]

BOOTPROTO=[static or DHCP]

ONBOOT=yes

IPADDR=[if static]

GATEWAY=[if static]

NETMASK=[if static]

TYPE=Ethernet

PEERDNS=yes

USERCTL=no

IPV6INIT=no

Step 16 At the prompt, enter ifup eth1 to bring the eth1 interface online.Step 17 Use ifconfig to verify that the network interfaces are configured properly.

The following example shows correctly configured network interfaces:

eth0 Link encap:Ethernet HWaddr F0:50:56:AB:26:45

inet addr:209.165.202.158 Bcast:209.165.202.159 Mask:255.255.255.224

inet6 addr: fb80::250:56ff:faeb:2654/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:20264 errors:0 dropped:0 overruns:0 frame:0

TX packets:2318 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:1088996 (1.7 KiB) TX bytes:554021 (541.0 KiB)

Interrupt: 59 Base address:0x2024

eth1 Link encap:Ethernet HWaddr 00:50:56:AB:61:1D

inet addr:209.165.202.156 Bcast:209.165.202.159 Mask:255.255.255.224

inet6 addr: fb80::250:56ff:faeb:611d/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1





Interrupt: 67 Base address:0x20c4

lo Link encap:Local loopback

inet addr:172.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host



UP LOOPBACK RUNNING MTU:1636 Metric:1





Step 18 Navigate to the /opt/infra/networkServices/ directory.

Step 19 In the run.sh file, enter the IP address of the Cisco UCS Director Baremetal Agent eth0 interface for the followingparameters:

-DpxeServer.ip=

-DpxeServer.mgmt_vlan_ip=

Step 20 Open a new SSH session to the IP address for the Cisco UCS Director VM.In a multi-node setup, you need to open the SSH session to the VM for the Inventory databasenode.

Note

The following default credentials for this VMmight have been changed during the configuration of Cisco UCS Director:

User nameshelladmin

Passwordchangeme

Step 21 In the shelladmin, do the following to add the Cisco UCS Director Baremetal Agent hostname and IP address:a) From the menu, choose the option for Add Cisco UCS Director Baremetal Agent Hostname/IP

and press Enter.b) When prompted, enter the IP Address and Hostname of the Cisco UCS Director Baremetal Agent VM.

Step 22 In the shelladmin, do the following to enable the database for Cisco UCS Director Baremetal Agent:In a multi-node setup, you need to perform this step on the Inventory databasenode.

Note

a) From the menu, choose the option for Enable Database for Cisco UCS Director BaremetalAgent and press Enter.

b) Enter y for yes.c) When prompted, enter the IP Address or Hostname of the Cisco UCS Director Baremetal Agent VM.

Step 23 From the shelladmin menu, choose the option for Quit and exit the console.Step 24 Return to the SSH console for the Cisco UCS Director Baremetal Agent VM.Step 25 Navigate to the /etc/ directory.

Step 26 Copy the dhcpd.conf.sample file, as follows: cp ./dhcpd.conf.sample ./dhcpd.conf

Step 27 Edit the dhcpd.conf file to set up the DHCP services that are required for PXE booting.The following sample dhcpd.conf file includes the DHCP services.

The next-server line is required and must include the IP address of eth1, the PXE interface, for the CiscoUCS Director Baremetal Agent VM.

Note

#

# DHCP Server Configuration file.

# see /usr/share/doc/dhcp*/dhcpd.conf.sample

#



ddns-update-style interim;

ignore client-updates;

subnet 209.165.202.158 netmask 255.255.255.224 {

option routers 209.165.200.254;

option subnet-mask 255.255.255.224;

option nis-domain "domain.org";

option domain-name "domain.org";

option domain-name-servers 209.165.201.1;

option time-offset -18000; # Eastern Standard Time

range dynamic-bootp 209.165.200.225 209.165.200.254;

default-lease-time 21600;

max-lease-time 43200;

allow booting;

allow bootp;

next-server 209.165.201.30; # IP of my PXE server

filename "/pxelinux.0";

}

Step 28 Navigate to the /etc/sysconfig/ directory.

Step 29 Edit the dhcpd file to add eth1 to the DHCPDARGS= parameter.

Step 30 At the prompt, enter service dhcpd restart to restart the DHCP services.Step 31 Navigate to the /opt/infra/ directory.

Step 32 Run the configure.sh script and, when prompted, provide the IP address of Cisco UCS Director as a parameter.In a multi-node setup, you need to perform this step on the Inventory databasenode.

Note

Step 33 In a web browser, navigate to the IP address for Cisco UCS Director and verify that Cisco UCS Director BaremetalAgent is available and active, as follows:

a) Login as a user with admin privileges.b) From the menu bar, choose Administration > Physical Accounts.c) Click the Network Services Agent tab.d) Verify that the list includes Cisco UCS Director Baremetal Agent and that the status is Active.e) If you do not see Cisco UCS Director Baremetal Agent in the list, click Refresh to add it to the list of available

network services agents.



Configuring Cisco UCS Director Baremetal Agent as a DHCPServer

Perform this task if you want to use Cisco UCS Director Baremetal Agent as a DHCP server and did notconfigure it during installation.

Step 1 Log in to Cisco UCS Director Baremetal Agent.Step 2 In the shelladmin, navigate to the /etc directory.

cd /etc

Step 3 Copy the dhcpd.conf.sample file to dhcpd.conf so that the existing file can be overwritten.cp /etc/dhcpd.conf.sample /etc/dhcpd.conf

Step 4 When you are prompted to overwrite dhcpd.conf, enter yes.

Step 5 Edit the dhcpd.conf file, using vi or another editor.

Example:vi dhcpd.conf

Step 6 Edit the following parameters to match your network:

Option router

Subnet mask

Domain name server

Dynamic-bootp range

Step 7 Start the DHCP server./etc/init.d/dhcpd start

Configuring Cisco UCS Director Baremetal Agent to Use a StaticIP Address

Perform this task if you want to use a static IP address and did not configure it when you installed Cisco UCSDirector Baremetal Agent.

Step 1 In VMware vCenter, right-click on the Cisco UCS Director Baremetal Agent VM and choose Open Console.Step 2 Navigate to the etc/sysconfig/nework-scripts/ directory.

Step 3 Edit the ifcfg-interface_number file with the static IP address you want to assign.


Network Configuration for Cisco UCS Director Baremetal AgentConfiguring Cisco UCS Director Baremetal Agent as a DHCP Server

The following sample ifcfg-eth1 file shows the configuration for a static IP address.

DEVICE=eth1

BOOTPROTO=none

ONBOOT=yes

TYPE=Ethernet

PEERDNS=yes

USERCTL=no

IPV6INIT=yes

IPV6ADDR=2001:0db8:2f6a:4c03::4/63

#IPV6_AUTOCONF=no

IPADDR=209.165.202.139

NETMASK=255.255.255.224

GATEWAY=209.165.202.245

BROADCAST=209.165.202.159

Step 4 When you are prompted about whether to configure a static IP address, enter yes and then enter the following information:

IP address

Gateway

Netmask


Network Configuration for Cisco UCS Director Baremetal AgentConfiguring Cisco UCS Director Baremetal Agent to Use a Static IP Address

C H A P T E R 4Operations and Management


Vblock Operations Task Roadmap, page 31

Creating an Organization, page 34

Configuring the Chassis/FEX Discovery Policy, page 35

Creating a UUID Pool, page 35

Creating a MAC Pool, page 36

Creating a WWNN Pool, page 37

Creating a WWPN Pool, page 37

Creating a Network Control Policy, page 38

Creating a vNIC Template, page 40

Creating a VSAN, page 43

Creating a vHBA Template, page 44

Creating a LAN Boot Policy, page 46

Creating a SAN Boot Policy, page 47

Creating a vNIC, page 49

Creating a vHBA, page 49

Creating a Network Policy, page 50

Creating a Storage Policy, page 52

Vblock Operations Task RoadmapThe following table provides a Cisco UCS Director configuration task roadmap for implementing Vblockoperations. The configuration notes explain important configuration details related to each task.


For more information related to the following tasks, see the Cisco UCS Director Management Guide forCisco UCS Manager.

Tip

Configuration NotesTask

Create a top-level organization which is the root. The policies andpools created in this root are system-wide and are available to allorganizations in the system.

Creating an Organization, on page 34

A chassis policy is configured to specify how the system reacts whena new chassis is added. Ensure that the 2-link option is selected fromthe Action drop-down list.

Configuring the Chassis/FEXDiscovery Policy, on page 35

Create a universally unique identifier (UUID) suffix pool with aname that is less than 16 characters. The default settings can be used.The UUID suffix pool ensures that UUID suffix variable values areunique for each server associated with a service profile. The serviceprofile uses the UUID suffix pool to avoid conflicts.

Creating a UUID Pool, on page 35

Create two MAC pools for each fabric interconnect. For example,fabric interconnect A and B. Specify 2 in the Size field(recommended).

Creating a MAC Pool, on page 36

Create two worldwide node name (WWNN) pools for each fabricinterconnect. Specify 2 in the Size field (recommended).

Creating a WWNN Pool, on page 37

Create two worldwide port name (WWPN) pools for each fabricinterconnect. Specify 2 in the Size field (recommended).

Creating a WWPN Pool, on page 37

Create the network control policy with the Cisco Discovery Protocol(CDP) enabled.

Creating a Network Control Policy,on page 38

Create two vNIC templates for each fabric interconnect. For example,fabric interconnect A and B. Follow the instructions in the task anduse the following configuration guidelines:

For theTarget check boxes, choose both theAdapter andVMparameters.

From the Template Type drop-down list, choose the InitialTemplate.

In theMTU field, we recommend that you enter 9000.

If the PXE server and the Cisco UCS server are in separateVLANs, you must create separate vNIC templates for bothservers in each fabric interconnect.

Note

Creating a vNIC Template, on page40

Create a virtual storage area network (VSAN) for each fabricinterconnect. For example, fabric interconnect A and B.

Creating a VSAN, on page 43


Operations and ManagementVblock Operations Task Roadmap


Associate each VSAN with each fabric interconnect.Associating the VSANs to the FabricInterconnects

Create a vHBA template for each fabric interconnect. Follow theinstructions in the task and use the following configurationguidelines:

From the Template Type drop-down list, choose the InitialTemplate.

In theMax Data Field Size field, enter 2048.

Creating a vHBA Template, on page44

Create a LAN boot policy for each fabric interconnect.Creating a LANBoot Policy, on page46

Create a SAN boot policy for each fabric interconnect.Creating a SAN Boot Policy, on page47

Create a vNIC for each fabric interconnect. Follow the instructionsin the task and use the following configuration guideline:

From the Adapter Policy drop-down list, choose VMware.


Note

Creating a vNIC, on page 49

Create a vHBA for each fabric interconnect. Follow the instructionsin the task and use the following configuration guideline:

From the Adapter Policy drop-down list, choose VMware.

Creating a vHBA, on page 49

Follow the instructions in the task and use the following configurationguidelines:

From the LAN Connectivity Type drop-down list, chooseExpert.

In theAdd vNIC field, specify the number of vNICs (for eachfabric interconnect) that you want to add to the network policy.

From the Template For vNIC1/vNIC2/vNIC3/vNIC4drop-down list, choose the vNIC template that you created.


Note

Creating a Network Policy, on page50


Operations and ManagementVblock Operations Task Roadmap


Follow the instructions in the task and use the following configurationguidelines:

From the SAN Connectivity Type drop-down list, chooseExpert.

From theWWNN Pool drop-down list, choose the WWNNpool that you created previously.

In the Add vHBA field, specify the number of vHBAs (foreach fabric interconnect) that you want to add to the storagepolicy.

From the Template For vHBA1/vHBA2/vHBA3/vHBA4drop-down list, choose the vHBA template you created.


Note

Creating a Storage Policy, on page 52

Creating an Organization

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left pane, expand the pod and then click the Cisco UCS Manager account.Step 3 In the right pane, click the Organizations tab.Step 4 Click Add.Step 5 In the Add Organization dialog box, complete the following fields:

a) In the Name field, enter a name for the organization.b) In the Description field, enter a description for the organization.c) From the Parent Organization drop-down list, choose the organization under which this organization will reside.


Operations and ManagementCreating an Organization

Configuring the Chassis/FEX Discovery Policy

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left pane, expand the pod and then click the Cisco UCS Manager account.Step 3 In the right pane, click the Equipment Global Policies tab.Step 4 Check the Chassis/FEX Discovery Policy check box.Step 5 From the Action drop-list, choose theminimum threshold for the number of links between the chassis or Fabric Extender

(FEX) and the fabric interconnect:

1-link

2-link

4-link

8-link

Step 6 From the Link Grouping Preference drop-down list, choose whether the links from the IOMs or FEXes to the fabricinterconnects are grouped in a port channel.

The link grouping preference takes effect only if both sides of the links between an IOM or FEX and the fabricinterconnect support fabric port channels. If one side of the links does not support fabric port channels, thispreference is ignored and the links are not grouped in a port channel.

Note

Step 7 Click Save.

Creating a UUID Pool

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left pane, expand the pod and then click the Cisco UCS Manager account.Step 3 In the right pane, click the Organizations tab.Step 4 Click the organization in which you want to create the pool and then click View Details.Step 5 Click the UUID Pools tab.Step 6 Click Add.Step 7 In the Add UUID Pool dialog box, complete the following fields:

DescriptionName

A unique name for the pool.Name field

A description for the pool.Description field


Operations and ManagementConfiguring the Chassis/FEX Discovery Policy

DescriptionName

Choose how the prefix is created. This can be one of thefollowing:

DerivedThe system creates the prefix.

OtherYou specify the desired prefix. If you selectthis option, a text field displays where you can enterthe desired prefix, in the formatXXXXXXXX-XXXX-XXXX.

Prefix drop-down list

The first UUID address in the block.From field

The number of UUID addresses in the block.Size field

Step 8 Click Submit.

Creating a MAC Pool

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left pane, expand the pod and then click the Cisco UCS Manager account.Step 3 In the right pane, click the Organizations tab.Step 4 Click the organization in which you want to create the pool and then click View Details.Step 5 Click theMAC Pools tab.Step 6 Click Add.Step 7 In the Add MAC Pool dialog box, complete the following fields:

DescriptionName



The first MAC address in the block.First MAC Address field

The number of MAC addresses in the block.Size field



Operations and ManagementCreating a MAC Pool

Creating a WWNN Pool

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left pane, expand the pod and then click the Cisco UCS Manager account.Step 3 In the right pane, click the Organizations tab.Step 4 Click the organization in which you want to create the pool and then click View Details.Step 5 Click theWWNN Pools tab.Step 6 Click Add.Step 7 In the Add WWNN Pool dialog box, complete the following fields:

DescriptionName



The first WWNN address in the block.From field

The number of WWNN addresses in the block.Size field


Creating a WWPN Pool

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left pane, expand the pod and then click the Cisco UCS Manager account.Step 3 In the right pane, click the Organizations tab.Step 4 Click the organization in which you want to create the pool and then click View Details.Step 5 Click theWWPN Pools tab.Step 6 Click Add.Step 7 In the Add WWPN Pool dialog box, complete the following fields:

DescriptionName



Operations and ManagementCreating a WWNN Pool

DescriptionName


The first WWPN address in the block.From field

The number of WWPN addresses in the block.Size field


Creating a Network Control PolicyMAC address-based port security for Emulex Converged Network Adapters (N20-AE0102) is not supported.When MAC address-based port security is enabled, the fabric interconnect restricts traffic to packets thatcontain theMAC address that it first learns, which is either the sourceMAC address used in the Fibre Channelover Ethernet (FCoE) Initialization Protocol packet or the MAC address in an Ethernet packet, whichever issent first by the adapter. This configuration can result in either FCoE or Ethernet packets being dropped.

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left pane, expand the pod and then click the Cisco UCS Manager account.Step 3 In the right pane, click the Organizations tab.Step 4 Click the organization in which you want to create the policy and then click View Details.Step 5 Click the Network Control Policies tab.Step 6 Click Add.Step 7 In the Add Network Control Policy dialog box, complete the following fields:

DescriptionName

A unique name for the policy.Name field

Choose whether the Cisco Discovery Protocol (CDP) isenabled on servers associated with a service profile thatincludes this policy. This can be one of the following:

Disabled

Enabled

CDP drop-down list


Operations and ManagementCreating a Network Control Policy

DescriptionName

Choose how the virtual interface (VIF) behaves if no uplinkport is available when the fabric interconnect is in end-hostmode. This can be one of the following:

LinkDownChanges the operational state of a vNICto downwhen uplink connectivity is lost on the fabricinterconnect, and enables a fabric failover for vNICs.

WarningMaintains server-to-server connectivityeven when no uplink port is available, and disablesa fabric failover when uplink connectivity is lost onthe fabric interconnect.

The default is Link Down.

If your implementation includes those types ofnon-VM-FEXcapable converged network adaptersand the adapter is expected to handle both Ethernetand FCoE traffic, we recommend that youconfigure the Action on Uplink Fail property witha value ofWarning. Note that this configurationmight result in an Ethernet teaming driver notbeing able to detect a link failure when the borderport goes down.

Note

Action on Uplink Fail drop-down list

Choose whether forged MAC addresses are allowed ordenied when packets are sent from the server to the fabricinterconnect. This can be one of the following:

AllowAll server packets are accepted by the fabricinterconnect, regardless of the MAC addressassociated with the packets.

DenyAfter the first packet has been sent to thefabric interconnect, all other packets must use thesame MAC address or they will be silently rejectedby the fabric interconnect. This option enables portsecurity for the associated vNIC.

If you plan to install VMware ESX on the associated server,you must configureMAC Security to allow for the networkcontrol policy applied to the default vNIC. If you do notconfigure MAC Security to Allow, the ESX installationmight fail because the MAC Security permits only oneMAC address while the installation process requires morethan one MAC address.

Forge drop-down list



Operations and ManagementCreating a Network Control Policy

Creating a vNIC TemplateBefore You Begin

One or more of the following resources must already exist:

Named VLAN

MAC pool

QoS policy

LAN pin group

Statistics threshold policy

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left pane, expand the pod and then click the Cisco UCS Manager account.Step 3 In the right pane, click the Organizations tab.Step 4 Click the organization in which you want to create the policy and then click View Details.Step 5 Click the vNIC Templates tab.Step 6 Click Add.Step 7 In the Add vNIC Template dialog box, complete the following fields:

DescriptionName


A description for the policy.Description field


Operations and ManagementCreating a vNIC Template

DescriptionName

Choose the fabric interconnect that vNICs created with thistemplate are associated with.

If you want vNICs created from this template to be able toaccess the second fabric interconnect if the default one isunavailable, check the Enable Failover check box.

Do not enable vNIC fabric failover under thefollowing circumstances:

Note

If the Cisco UCS domain is running inEthernet Switch Mode. vNIC fabric failoveris not supported in that mode. If all Ethernetuplinks on one fabric interconnect fail, thevNICs do not fail over to the other.

If you plan to associate one or more vNICscreated from this template with a serveradapter that does not support a fabricfailover, such as the CiscoUCS 82598KR-CI10-Gigabit Ethernet Adapter. If you do so,Cisco UCS Manager generates aconfiguration fault when you associate theservice profile with the server.

Fabric ID drop-down list

If checked, the target that you choose determines whethera VM-FEX port profile is automatically created with theappropriate settings for the vNIC template. This can be oneof the following:

AdapterThe vNICs apply to all adapters. NoVM-FEX port profile is created if you choose thisoption.

VMThe vNICs apply to all virtual machines. AVM-FEX port profile is created if you choose thisoption.

Target check boxes

Choose the type of template. This can be one of thefollowing:

Initial TemplatevNICs created from this templateare not updated if the template changes.

Updating TemplatevNICs created from thistemplate are updated if the template changes.

Template Type drop-down list

Step 8 In the VLANs area, do the following to select the VLAN to be assigned to vNICs created from this template:



a) Click Add.b) In the Add Entry to VLANs dialog box, complete the following fields and click Submit:

Name drop-down listChoose the VLAN that you want to associate with the vNIC template.

Set as Native VLAN check boxCheck the check box if you want this VLAN to be the native VLAN for theport.

Step 9 To associate policies with vNICs created from this template, complete the following fields:

DescriptionName

The maximum transmission unit (MTU), or packet size,that vNICs created from this vNIC template should use.

Enter an integer between 1500 and 9216.

If the vNIC template has an associated QoS policy,the MTU specified here must be equal to or lessthan the MTU specified in the associated QoSsystem class. If thisMTU value exceeds theMTUvalue in the QoS system class, packets might bedropped during data transmission.

Note

MTU field

Choose the MAC address pool that vNICs created fromthis vNIC template should use.

MAC Pool drop-down list

Choose the quality of service policy that vNICs createdfrom this vNIC template should use.

QoS Policy drop-down list

Choose the network control policy that vNICs created fromthis vNIC template should use.

Network Control Policy drop-down list

Choose the LAN pin group that vNICs created from thisvNIC template should use.

Pin Group drop-down list

Choose the statistics collection policy that vNICs createdfrom this vNIC template should use.

Stats Threshold Policy drop-down list


What to Do Next

Include the vNIC template in a network policy.



Creating a VSAN

Fibre Channel over Ethernet (FCoE) VLANs in the SAN cloud and VLANs in the LAN cloud must havedifferent IDs. Using the same ID for an FCoE VLAN in a VSAN and a VLAN results in a critical faultand traffic disruption for all vNICs and uplink ports using that FCoE VLAN. Ethernet traffic is droppedon any VLAN that has an ID that overlaps with an FCoE VLAN ID.

Note

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left pane, expand the pod and then click the Cisco UCS Manager account.Step 3 In the right pane, click the VSANs tab.Step 4 Click Add.Step 5 In the Add VSAN dialog box, complete the following fields:

DescriptionName

A unique name for the VSAN.VSAN Name field

The unique identifier assigned to the network.VSAN ID field

Choose the type of VSAN. This can be one of thefollowing:

SAN Cloud

Storage Cloud

If you are creating a VSAN for Fibre Channel zoning, werecommend that you choose Storage Cloud.

Type drop-down list

Choose how the VSAN should be configured. This can beone of the following:

Common/GlobalThe VSAN maps to the sameVSAN ID in all available fabrics.

Fabric AThe VSAN maps to a VSAN ID thatexists only in fabric A.

Fabric BThe VSAN maps to a VSAN ID thatexists only in fabric B.



Operations and ManagementCreating a VSAN

DescriptionName

The unique identifier assigned to the VLAN used for FibreChannel connections.

For FCoE Initialization Protocol (FIP)-capable, convergednetwork adapters, such as the Cisco UCS CNAM72KR-Qand the Cisco UCS CNA M72KR-E, the named VSANmust be configured with a named VLAN that is not thenative VLAN for the FCoE VLAN ID. This configurationensures that FCoE traffic can pass through these adapters.

FCoE VLAN field


What to Do Next

If you plan to use this VSAN for Fibre Channel zoning, see Configuring a VSAN for Fibre Channel Zoning.

Creating a vHBA TemplateBefore You Begin

One or more of the following resources must already exist:

VSAN

WWPN pool

SAN pin group

Statistics threshold policy

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left pane, expand the pod and then click the Cisco UCS Manager account.Step 3 In the right pane, click the Organizations tab.Step 4 Click the organization in which you want to create the policy and then click View Details.Step 5 Click the vHBA Templates tab.Step 6 Click Add.Step 7 In the Add vHBA Template dialog box, complete the following fields:

DescriptionName




Operations and ManagementCreating a vHBA Template

DescriptionName

Choose the fabric interconnect that vHBAs created withthis template are associated with.


Choose the VSAN that you want to associate with vHBAscreated from this template.

VSAN drop-down list

Choose the type of template that you want to use. This canbe one of the following:

Initial TemplatevHBAs created from this templateare not updated if the template changes.

Updating TemplatevHBAs created from thistemplate are updated if the template changes.

Template Type drop-down list

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

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

Max Data Field Size field

Choose the WWPN pool that a vHBA created from thistemplate uses to derive its WWPN address.

WWPN Pool drop-down list

Choose the QoS policy that is associated with vHBAscreated from this template.

QoS Policy drop-down list

Choose the SAN pin group that is associated with vHBAscreated from this template.

Pin Group drop-down list

Choose the statistics threshold policy that is associated withvHBAs created from this template.

Stats Threshold Policy drop-down list


What to Do Next

Include the vHBA template in a storage policy.


Operations and ManagementCreating a vHBA Template

Creating a LAN Boot PolicyYou can add more than one type of boot device to a boot policy. For example, you could add a local disk bootas a secondary boot device.

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left pane, expand the pod and then click the Cisco UCS Manager account.Step 3 In the right pane, click the Organizations tab.Step 4 Click the organization in which you want to create the policy and then click View Details.Step 5 Click the Boot Policies tab.Step 6 Click Add.Step 7 In the Add Boot Policy dialog box, complete the following fields:

DescriptionName



If checked, reboots all servers that use this boot policy afteryou make changes to the boot order.

If this check box is checked and if CD-ROM or Floppy isthe last device in the boot order, deleting or adding thedevice does not directly affect the boot order and the serverdoes not reboot.

Reboot on Order Change check box

If checked, a configuration error is displayed if one or moreof the vNICs, vHBAs, or iSCSI vNICs listed in the BootOrder table matches the server configuration in the serviceprofile.

If this check box is not checked, the policy uses the vNICs,vHBAs, or iSCSI vNICs (as appropriate for the boot option)from the server configuration in the service profile. It doesnot report whether the vNICs, vHBAs, or iSCSI vNICsspecified in the boot policy match the server configurationin the service profile.

Enforce vNIC/vHBA Name check box

Step 8 In the Add Boot Device area, check the Add LAN Boot check box.Step 9 In the Primary vNIC field, enter the name of the vNIC that you want to use as the first address defined for the LAN

boot location.

Step 10 In the Secondary vNIC field, enter the name of the vNIC that you want to use as the second address defined for theLAN boot location.



Operations and ManagementCreating a LAN Boot Policy

Creating a SAN Boot Policy

We recommend that the boot order in a boot policy include either a local disk or a SAN LUN, but notboth, to avoid the possibility of the server booting from the wrong storage type. If you configure a localdisk and a SAN LUN for the boot order storage type and the operating system or logical volume manager(LVM) is configured incorrectly, the server might boot from the local disk rather than the SAN LUN.

For example, on a server with Red Hat Linux installed, where the LVM is configured with default LVnames and the boot order is configured with a SAN LUN and a local disk, Linux reports that there aretwo LVs with the same name and boots from the LV with the lowest SCSI ID, which could be the localdisk.

Tip

Before You Begin

If you are creating a boot policy that boots the server from a SAN LUN and you require reliable SAN bootoperations, we recommend that you first remove all local disks from servers associated with a service profilethat includes the boot policy.

Step 1 On the menu bar, choose Physical > Compute.Step 2 In the left pane, expand the pod and then click the Cisco UCS Manager account.Step 3 In the right pane, click the Organizations tab.Step 4 Click the organization in which you want to create the policy and then click View Details.Step 5 Click the Boot Policies tab.Step 6 Click Add.Step 7 In the Add Boot Policy dialog box, complete the following fields:

DescriptionName



If checked, reboots all servers that use this boot policy afteryou make changes to the boot order.

If this check box is checked and if CD-ROM or Floppy isthe last device in the boot order, deleting or adding thedevice does not directly affect the boot order and the serverdoes not reboot.

Reboot on Order Change check box


Operations and ManagementCreating a SAN Boot Policy

Manual Cisco Ucsd Vblock Mgt Gd

Documents

Transcript of Manual Cisco Ucsd Vblock Mgt Gd