Cisco Systems 57712 Users Manual

57712 to the manual 1ee0a164-283d-4b55-ba06-e901862c9a63

2015-01-05

: Cisco-Systems Cisco-Systems-57712-Users-Manual-202319 cisco-systems-57712-users-manual-202319 cisco-systems pdf

Open the PDF directly: View PDF .
Page Count: 288 [warning: Documents this large are best viewed by clicking the View PDF Link!]

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5
Contents
Preface
- Audience
- Conventions
- New and Changed Information for this Release
- Related Cisco UCS Documentation
Overview
- Overview of the Cisco UCS C-Series Rack-Mount Servers
- Overview of the Server Software
- Cisco Integrated Management Controller
- CIMC CLI
Installing the Server OS
- OS Installation Methods
- KVM Console
- PXE Installation Servers
  - Installing an OS Using a PXE Installation Server
Managing the Server
- Toggling the Locator LED
- Toggling the Locator LED for a Hard Drive
- Managing the Server Boot Order
- Resetting the Server
- Shutting Down the Server
- Managing Server Power
- Configuring Power Policies
- Managing the Flexible Flash Controller
- Configuring BIOS Settings
Viewing Server Properties
- Viewing Server Properties
- Viewing CIMC Properties
- Viewing CPU Properties
- Viewing Memory Properties
- Viewing Power Supply Properties
- Viewing Storage Properties
- Viewing PCI Adapter Properties
- Viewing Network Related Properties
  - Viewing LOM Properties
Viewing Server Sensors
- Viewing Power Supply Sensors
- Viewing Fan Sensors
- Viewing Temperature Sensors
- Viewing Voltage Sensors
- Viewing Current Sensors
- Viewing Storage Sensors
Managing Remote Presence
- Managing the Virtual KVM
- Configuring Virtual Media
- Managing Serial over LAN
Managing User Accounts
- Configuring Local Users
- Configuring Active Directory
- Viewing User Sessions
- Terminating a User Session
Configuring Network-Related Settings
- Server NIC Configuration
  - Server NICs
  - Configuring Server NICs
- Configuring Common Properties
- Configuring IPv4
- Configuring the Server VLAN
- Connecting to a Port Profile
- Network Security Configuration
  - Network Security
  - Configuring Network Security
- Network Time Protocol Configuration
  - Configuring Network Time Protocol Settings
Managing Network Adapters
- Overview of the Cisco UCS C-Series Network Adapters
- Viewing Network Adapter Properties
- Configuring Network Adapter Properties
- Managing vHBAs
- Managing vNICs
- Managing VM FEX
- Managing Storage Adapters
- Backing Up and Restoring the Adapter Configuration
- Managing Adapter Firmware
- Resetting the Adapter
Configuring Communication Services
- Configuring HTTP
- Configuring SSH
- Configuring XML API
  - XML API for CIMC
  - Enabling XML API
- Configuring IPMI
  - IPMI Over LAN
  - Configuring IPMI over LAN
- Configuring SNMP
Managing Certificates
- Managing the Server Certificate
- Generating a Certificate Signing Request
- Creating a Self-Signed Certificate
- Uploading a Server Certificate
Configuring Platform Event Filters
- Platform Event Filters
- Enabling Platform Event Alerts
- Disabling Platform Event Alerts
- Configuring Platform Event Filters
- Configuring Platform Event Trap Settings
- Interpreting Platform Event Traps
CIMC Firmware Management
- Overview of Firmware
- Obtaining Firmware from Cisco
- Installing CIMC Firmware from a Remote Server
- Activating Installed CIMC Firmware
- Installing BIOS Firmware from a Remote Server
Viewing Logs
- Viewing the Faults and Logs Summary
- CIMC Log
- System Event Log
  - Viewing the System Event Log
  - Clearing the System Event Log
Server Utilities
- Exporting Technical Support Data
- Rebooting the CIMC
- Clearing the BIOS CMOS
- Recovering from a Corrupted BIOS
- Resetting the CIMC to Factory Defaults
- Exporting and Importing the CIMC Configuration
- Generating Non maskable Interrupts to the Host
BIOS Parameters by Server Model
- C22 and C24 Servers
- C220 and C240 Servers
- C260 Servers
- C420 Servers
- C460 Servers
INDEX

Cisco UCS C-Series Servers Integrated Management Controller CLI

Configuration Guide, Release 1.5

First Published: March 04, 2013

Americas Headquarters

Cisco Systems, Inc.

170 West Tasman Drive

San Jose, CA 95134-1706

USA

http://www.cisco.com

Tel: 408 526-4000

800 553-NETS (6387)

Fax: 408 527-0883

Text Part Number: OL-28893-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 LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH

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

CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version

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

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

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

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

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

HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

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

www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership

relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown

for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

CONTENTS

Preface

Preface xi

Audience xi

Conventions xi

New and Changed Information for this Release xiii

directory

•Path of the remote file corresponding to the exported

directory.

•(Optional) Mapping options

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 59

Managing Remote Presence

Configuring Network Mounted vMedia Mapping

PurposeCommand or Action

•Username and password to connect to the server

This example shows how to create a CIFS network mounted vMedia mapping:

Server # scope vmedia

Server /vmedia # map-cifs sample-volume //10.10.10.10/project /test/sample

Server username:

Server password: ****

Confirm password: ****

Server /vmedia #

Viewing Network Mount vMedia Mapping Properties

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the virtual media command mode.Server # scope vmedia

Step 1

Displays information on all the vmedia mapping

that are configured.

Server /vmedia # show mappings detail

Step 2

This example shows how to view the properties of all the configured vmedia mapping:

Server # scope vmedia

Server /vmedia # show mappings

Volume Map-status Drive-type remote-share remote-file mount-type

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

Huu OK removable http://10.104.236.99/ rhel-server-6.1-x86_6.iso www

Rhel OK CD http://10.104.236.99/ rhel-server-6.1-x86_6.iso www

Removing Network Mounted vMedia Mapping

Before You Begin

You must log in with admin privileges to perform this task.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

60 OL-28893-01

Managing Remote Presence

Viewing Network Mount vMedia Mapping Properties

Procedure

PurposeCommand or Action

Enters the virtual media command mode.Server # scope vmedia

Step 1

Specifies the volume name to unmap.

Server /vmedia # unmap volume_name

Step 2

This example shows how to unmap a local vmedia volume:

Server # scope vmedia

Server /vmedia # show mappings

Volume Map-status Drive-type remote-share remote-file mount-type

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

Huu OK removable http://10.104.236.99/ rhel-server-6.1-x86_6.iso www

Rhel OK CD http://10.104.236.99/ rhel-server-6.1-x86_6.iso www

Server /vmedia # unmap huu

Server /vmedia # show mappings

Volume Map-status Drive-type remote-share remote-file mount-type

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

Rhel OK CD http://10.104.236.99/ rhel-server-6.1-x86_6.iso www

Server /vmedia #

Managing Serial over LAN

Serial Over LAN

Serial over LAN (SoL) is a mechanism that enables the input and output of the serial port of a managed system

to be redirected via an SSH session over IP. SoL provides a means of reaching the host console via CIMC.

Guidelines and Restrictions for Serial Over LAN

For redirection to SoL, the server console must have the following configuration:

•console redirection to serial port A

•no flow control

•baud rate the same as configured for SoL

•VT-100 terminal type

•legacy OS redirection disabled

The SoL session will display line-oriented information such as boot messages, and character-oriented screen

menus such as BIOS setup menus. If the server boots an operating system or application with a bitmap-oriented

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 61

Managing Remote Presence

Managing Serial over LAN

display, such as Windows, the SoL session will no longer display. If the server boots a command-line-oriented

operating system (OS), such as Linux, you may need to perform additional configuration of the OS in order

to properly display in an SoL session.

In the SoL session, your keystrokes are transmitted to the console except for the function key F2. To send an

F2 to the console, press the Escape key, then press 2.

Configuring Serial Over LAN

Before You Begin

You must log in as a user with admin privileges to configure serial over LAN (SoL).

Procedure

PurposeCommand or Action

Enters SoL command mode.Server# scope sol

Step 1

Enables or disables SoL on this server.Server /sol # set enabled

{yes |no}

Step 2

Sets the serial baud rate the system uses for SoL communication.Server /sol # set baud-rate

{9600 |19200 |38400 |

57600 |115200}

Step 3

The baud rate must match the baud rate configured in the

server serial console.

Note

(Optional)

Sets the serial port through which the system routes SoL

communications.

Server /sol # set comport

{com0 |com1

Step 4

This field is only available on some C-Series servers. If it

is not available, the server always uses COM port 0 for

SoL communication.

Note

You can specify:

•com0—SoL communication is routed through COM port 0,

an externally accessible serial port that supports either a

physical RJ45 connection to an external device or a virtual

SoL connection to a network device.

If you select this option, the system enables SoL and disables

the RJ45 connection, which means that the server can no

longer support an external serial device.

•com1—SoL communication is routed through COM port 1,

an internal port accessible only through SoL.

If you select this option, you can use SoL on COM port 1 and

the physical RJ45 connection on COM port 0.

Changing the comport setting disconnects any existing

SoL sessions.

Note

Commits the transaction to the system configuration.Server /sol # commit

Step 5

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

62 OL-28893-01

Managing Remote Presence

Configuring Serial Over LAN

PurposeCommand or Action

(Optional) Displays the SoL settings.Server /sol # show [detail]

Step 6

This example configures SoL:

Server# scope sol

Server /sol # set enabled yes

Server /sol *# set baud-rate 115200

Server /sol *# commit

Server /sol # show

Enabled Baud Rate(bps) Com Port

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

yes 115200 com2

Server /sol # show detail

Serial Over LAN:

Enabled: yes

Baud Rate(bps): 115200

Com Port: com2

Server /sol #

Launching Serial Over LAN

Procedure

PurposeCommand or Action

Opens a serial over LAN (SoL) connection to the redirected

server console port. You can enter this command in any

command mode.

Server# connect host

Step 1

What to Do Next

To end the SoL session, you must close the CLI session. For example, to end an SoL session over an SSH

connection, disconnect the SSH connection.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 63

Managing Remote Presence

Launching Serial Over LAN

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

64 OL-28893-01

Managing Remote Presence

Launching Serial Over LAN

CHAPTER 7

Managing User Accounts

This chapter includes the following sections:

•Configuring Local Users, page 65

•Configuring Active Directory, page 66

•Viewing User Sessions, page 71

•Terminating a User Session, page 71

Configuring Local Users

Before You Begin

You must log in as a user with admin privileges to configure or modify local user accounts.

Procedure

PurposeCommand or Action

Enters user command mode for user number usernumber.Server# scope user usernumber

Step 1

Enables or disables the user account on the CIMC.Server /user # set enabled {yes

|no}

Step 2

Specifies the username for the user.Server /user # set name

username

Step 3

You are prompted to enter the password twice.Server /user # set password

Step 4

Specifies the role assigned to the user. The roles are as

follows:

Server /user # set role {readonly

|user |admin}

Step 5

•readonly—This user can view information but cannot

make any changes.

•user—This user can do the following:

•View all information

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 65

PurposeCommand or Action

•Manage the power control options such as power

on, power cycle, and power off

•Launch the KVM console and virtual media

•Clear all logs

•Toggle the locator LED

•admin—This user can perform all actions available

through the GUI, CLI, and IPMI.

Commits the transaction to the system configuration.Server /user # commit

Step 6

This example configures user 5 as an admin:

Server# scope user 5

Server /user # set enabled yes

Server /user *# set name john

Server /user *# set password

Please enter password:

Please confirm password:

Server /user *# set role readonly

Server /user *# commit

Server /user # show

User Name Role Enabled

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

5 john readonly yes

Configuring Active Directory

Active Directory

Active Directory is a technology that provides a variety of network services including LDAP-like directory

services, Kerberos-based authentication, and DNS-based naming. The CIMC utilizes the Kerberos-based

authentication service of Active Directory.

When Active Directory is enabled in the CIMC, user authentication and role authorization is performed by

Active Directory for user accounts not found in the local user database.

you can require the server to encrypt data sent to Active Directory.

Configuring the Active Directory Server

The CIMC can be configured to use Active Directory for user authentication and authorization. To use Active

Directory, configure users with an attribute that holds the user role and locale information for the CIMC. You

can use an existing LDAP attribute that is mapped to the CIMC user roles and locales or you can modify the

Active Directory schema to add a new custom attribute, such as the CiscoAVPair attribute, which has an

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

66 OL-28893-01

Managing User Accounts

Configuring Active Directory

attribute ID of 1.3.6.1.4.1.9.287247.1. For more information about altering the Active Directory schema, see

the article at http://technet.microsoft.com/en-us/library/bb727064.aspx.

The following steps are to be performed on the Active Directory server.

This example creates a custom attribute named CiscoAVPair, but you can also use an existing LDAP

attribute that is mapped to the CIMC user roles and locales.

Note

Procedure

Step 1 Ensure that the Active Directory schema snap-in is installed.

Step 2 Using the Active Directory schema snap-in, add a new attribute with the following properties:

ValueProperties

CiscoAVPairCommon Name

CiscoAVPairLDAP Display Name

1.3.6.1.4.1.9.287247.1Unique X500 Object ID

CiscoAVPairDescription

Case Sensitive StringSyntax

Step 3 Add the CiscoAVPair attribute to the user class using the Active Directory snap-in:

a) Expand the Classes node in the left pane and type U to select the user class.

b) Click the Attributes tab and click Add.

c) Type C to select the CiscoAVPair attribute.

d) Click OK.

Step 4 Add the following user role values to the CiscoAVPair attribute, for the users that you want to have access

to CIMC:

CiscoAVPair Attribute ValueRole

shell:roles="admin"admin

shell:roles="user"user

shell:roles="read-only"read-only

For more information about adding values to attributes, see the article at http://technet.microsoft.com/

en-us/library/bb727064.aspx.

Note

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 67

Managing User Accounts

Configuring the Active Directory Server

What to Do Next

Use the CIMC to configure Active Directory.

Configuring Active Directory in CIMC

Configure Active Directory (AD) in CIMC when you want to use an AD server for local user authentication

and authorization.

Before You Begin

You must log in as a user with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the LDAP command mode for AD configuration.Server# scope ldap

Step 1

Enables or disables AD. When AD is enabled, user

authentication and role authorization is performed by AD for

user accounts not found in the local user database.

Server /ldap # set enabled

{yes |no}

Step 2

Specifies an Active Directory domain controller (DC) host

name or IP address. You can specify up to three DCs using

index nvalues from 1 to 3.

Server /ldap # set dcn dc-host

Step 3

Specifies an Active Directory global catalog (GC) server host

name or IP address. You can specify up to three GCs using

index nvalues from 1 to 3.

Server /ldap # set gcn gc-host

Step 4

Specifies the number of seconds the CIMC waits until the

LDAP search operation times out.

Server /ldap # set timeout

seconds

Step 5

If encryption is enabled, the server encrypts all information

sent to AD.

Server /ldap # set encrypted

{yes |no}

Step 6

Specifies the domain that all users must be in.Server /ldap # set base-dn

domain-name

Step 7

Specify an LDAP attribute that contains the role and locale

information for the user. This property is always a name-value

Server /ldap # set attribute

name

Step 8

pair. The system queries the user record for the value that

matches this attribute name.

You can use an existing LDAP attribute that is mapped to the

CIMC user roles and locales or you can create a custom

attribute, such as the CiscoAVPair attribute, which has the

following attribute ID:

1.3.6.1.4.1.9.287247.1

If you do not specify this property, user access is

restricted to read-only.

Note

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

68 OL-28893-01

Managing User Accounts

Configuring Active Directory in CIMC

PurposeCommand or Action

Commits the transaction to the system configuration.Server /ldap # commit

Step 9

(Optional) Displays the AD configuration.Server /ldap # show [detail]

Step 10

This example configures AD using the CiscoAVPair attribute:

Server# scope ldap

Server /ldap # set enabled yes

Server /ldap *# set dc1 192.0.20.123

Server /ldap *# set gc1 192.0.20.11

Server /ldap *# set timeout 60

Server /ldap *# set encrypted yes

Server /ldap *# set base-dn example.com

Server /ldap *# set attribute CiscoAVPair

Server /ldap *# commit

Server /ldap # show detail

LDAP Settings:

Domain Controller 1: 192.0.20.123

Domain Controller 2: 0.0.0.0

Domain Controller 3: 0.0.0.0

BaseDN: example.com

Encrypted: yes

Timeout: 60

Enabled: yes

Attribute: CiscoAvPair

Group Authorization: no

Global Catalog 1: 192.0.20.11

Global Catalog 2: 0.0.0.0

Global Catalog 3: 0.0.0.0

Server /ldap #

What to Do Next

If you want to use Active Directory groups for group authorization, see Configuring Active Directory Groups

in CIMC.

Configuring Active Directory Groups in CIMC

When Active Directory (AD) group authorization is enabled and configured, user authentication is also

done on the group level for users that are not found in the local user database or who are not individually

authorized to use CIMC in the Active Directory.

Note

Before You Begin

•You must log in as a user with admin privileges to perform this task.

•Active Directory (or LDAP) must be enabled and configured.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 69

Managing User Accounts

Configuring Active Directory Groups in CIMC

Procedure

PurposeCommand or Action

Enters the LDAP command mode for AD configuration.Server# scope ldap

Step 1

Enables or disables AD group authorization.Server /ldap # set group-auth

{yes |no}

Step 2

Selects one of the five available group profiles for

configuration, where index is a number between 1 and 5.

Server /ldap # scope role-group

index

Step 3

Specifies the name of the group in the AD database that is

authorized to access the server.

Server /ldap/role-group # set name

group-name

Step 4

Specifies the AD domain the group must reside in.Server /ldap/role-group # set

domain domain-name

Step 5

Specifies the permission level (role) assigned to all users in

this AD group. This can be one of the following:

Server /ldap/role-group # set role

{admin |user |readonly}

Step 6

•admin—The user can perform all actions available.

•user—The user can perform the following tasks:

◦View all information

◦Manage the power control options such as power

on, power cycle, and power off

◦Launch the KVM console and virtual media

◦Clear all logs

◦Toggle the locator LED

•readonly—The user can view information but cannot

make any changes.

Commits the transaction to the system configuration.Server /ldap/role-group # commit

Step 7

This example shows how to configure AD group authorization:

Server# scope ldap

Server /ldap # set group-auth yes

Server /ldap *# scope role-group 5

Server /ldap/role-group *# set name Training

Server /ldap/role-group *# set domain example.com

Server /ldap/role-group *# set role readonly

Server /ldap/role-group *# commit

ucs-c250-M2 /ldap # show role-group

Group Name Domain Role

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

1 (n/a) (n/a) admin

2 (n/a) (n/a) user

3 (n/a) (n/a) readonly

4 (n/a) (n/a) (n/a)

5 Training example.com readonly

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

70 OL-28893-01

Managing User Accounts

Configuring Active Directory Groups in CIMC

Server /ldap/role-group #

Viewing User Sessions

Procedure

PurposeCommand or Action

Displays information about current user sessions.Server# show user-session

Step 1

The command output displays the following information about current user sessions:

DescriptionName

The unique identifier for the session.Session ID column

The username for the user.Username column

The IP address from which the user accessed the server.IP Address column

The method by which the user accessed the server.Type column

If your user account is assigned the admin user role, this column

displays Terminate if you can force the associated user session to end.

Otherwise it displays N/A.

You cannot terminate your current session from this

tab.

Note

Action column

This example displays information about current user sessions:

Server# show user-session

ID Name IP Address Type Killable

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

15 admin 10.20.30.138 CLI yes

Server /user #

Terminating a User Session

Before You Begin

You must log in as a user with admin privileges to terminate a user session.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 71

Managing User Accounts

Viewing User Sessions

Procedure

PurposeCommand or Action

Displays information about current user sessions. The

user session to be terminated must be eligible to be

terminated (killable) and must not be your own session.

Server# show user-session

Step 1

Enters user session command mode for the numbered

user session that you want to terminate.

Server /user-session # scope

user-session session-number

Step 2

Terminates the user session.Server /user-session # terminate

Step 3

This example shows how the admin at user session 10 terminates user session 15:

Server# show user-session

ID Name IP Address Type Killable

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

10 admin 10.20.41.234 CLI yes

15 admin 10.20.30.138 CLI yes

Server# scope user-session 15

Server /user-session # terminate

User session 15 terminated.

Server /user-session #

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

72 OL-28893-01

Managing User Accounts

Terminating a User Session

CHAPTER 8

Configuring Network-Related Settings

This chapter includes the following sections:

•Server NIC Configuration, page 73

•Configuring Common Properties, page 75

•Configuring IPv4, page 76

•Configuring the Server VLAN, page 77

•Connecting to a Port Profile, page 78

•Network Security Configuration, page 80

•Network Time Protocol Configuration, page 81

Server NIC Configuration

Server NICs

NIC Mode

The NIC mode setting determines which ports can reach the CIMC. The following network mode options are

available, depending on your platform:

•Dedicated—The management port is used to access the CIMC.

•Shared LOM—Any LOM (LAN On Motherboard) port can be used to access the CIMC.

•Shared LOM 10G—Any 10G LOM port can be used to access the CIMC. This option is only available

for some adapter cards.

•Cisco Card—Any port on the adapter card can be used to access the CIMC. The Cisco adapter card has

to be installed in a slot with Network Communications Services Interface protocol (NCSI) support.

•Shared LOM Extended—Any LOM port or adapter card port can be used to access the CIMC. The

Cisco adapter card has to be installed in a slot with NCSI support.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 73

NIC Redundancy

The following NIC redundancy options are available, depending on the selected NIC mode and your platform:

•none—Each port associated with the configured NIC mode operates independently. The ports do not

fail over if there is a problem.

•active-active—If supported, all ports associated with the configured NIC mode operate simultaneously.

This increases throughput and provides multiple paths to the CIMC.

•active-standby—If a port associated with the configured NIC mode fails, traffic will fail over to one

of the other ports associated with the NIC mode.

If you select this option, make sure all ports associated with the configured NIC mode

are connected to the same subnet to ensure that traffic is secure regardless of which port

is used.

Note

The available redundancy modes vary depending on the selected network mode and your platform. For the

available modes, see the Hardware Installation Guide (HIG) for the type of server you are using. The C-Series

HIGs are available at the following URL: http://www.cisco.com/en/US/products/ps10493/prod_installation_

guides_list.html

Configuring Server NICs

Configure a server NIC when you want to set the NIC mode and NIC redundancy.

Before You Begin

You must log in as a user with admin privileges to configure the NIC.

Procedure

PurposeCommand or Action

Enters the CIMC command mode.Server# scope cimc

Step 1

Enters the CIMC network command mode.Server /cimc # scope network

Step 2

Sets the NIC mode to one of the following:Server /cimc/network # set

mode {dedicated |

Step 3

•Dedicated—The management Ethernet port is used to access

the CIMC.

shared_lom |

shared_lom_10g |shipping |

cisco_card}•Shared LOM—The LAN On Motherboard (LOM) Ethernet

host ports are used to access the CIMC.

If you select Shared LOM, make sure that all host

ports belong to the same subnet.

Note

•Shared LOM 10G—The 10G LOM Ethernet host ports are

used to access the CIMC.

•Shipping—A limited configuration for initial connection.

Select another mode for normal operation.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

74 OL-28893-01

Configuring Network-Related Settings

Configuring Server NICs

PurposeCommand or Action

•Cisco card—The ports on the adapter card are used to access

the CIMC.

Sets the NIC redundancy mode when the NIC mode is Shared

LOM. The redundancy mode can be one of the following:

Server /cimc/network # set

redundancy {none |

Step 4

active-active |

active-standby}•none—The LOM Ethernet ports operate independently and

do not fail over if there is a problem.

•active-active—If supported, all LOM Ethernet ports are

utilized.

•active-standby—If one LOM Ethernet port fails, traffic fails

over to another LOM port.

Commits the transaction to the system configuration.Server /cimc/network #

commit

Step 5

The available NIC mode and NIC redundancy mode

options may vary depending on your platform. If you

select a mode not supported by your server, an error

message displays when you save your changes.

Note

This example configures the CIMC network interface:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set mode dedicated

Server /cimc/network *# commit

Server /cimc/network #

Configuring Common Properties

Use common properties to describe your server.

Before You Begin

You must log in as a user with admin privileges to configure common properties.

Procedure

PurposeCommand or Action

Enters the CIMC command mode.Server# scope cimc

Step 1

Enters the CIMC network command mode.Server /cimc # scope network

Step 2

Specifies the name of the host.Server /cimc/network # set hostname

host-name

Step 3

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 75

Configuring Network-Related Settings

Configuring Common Properties

PurposeCommand or Action

Commits the transaction to the system

configuration.

Server /cimc/network # commit

Step 4

This example configures the common properties:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set hostname Server

Server /cimc/network *# commit

Server /cimc/network #

Configuring IPv4

Before You Begin

You must log in as a user with admin privileges to configure IPv4 network settings.

Procedure

PurposeCommand or Action

Enters the CIMC command mode.Server# scope cimc

Step 1

Enters the CIMC network command mode.Server /cimc # scope network

Step 2

Selects whether the CIMC uses DHCP.

If DHCP is enabled, we recommend that

the DHCP server be configured to reserve

a single IP address for the CIMC. If the

CIMC is reachable through multiple ports

on the server, the single IP address must

be reserved for the full range of MAC

addresses of those ports.

Note

Server /cimc/network # set dhcp-enabled

{yes |no}

Step 3

Specifies the IP address for the CIMC.Server /cimc/network # set v4-addr

ipv4-address

Step 4

Specifies the subnet mask for the IP address.Server /cimc/network # set v4-netmask

ipv4-netmask

Step 5

Specifies the gateway for the IP address.Server /cimc/network # set v4-gateway

gateway-ipv4-address

Step 6

Selects whether the CIMC retrieves the DNS server

addresses from DHCP.

Server /cimc/network # set dns-use-dhcp

{yes |no}

Step 7

Specifies the IP address of the primary DNS server.Server /cimc/network # set

preferred-dns-server dns1-ipv4-address

Step 8

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

76 OL-28893-01

Configuring Network-Related Settings

Configuring IPv4

PurposeCommand or Action

Specifies the IP address of the secondary DNS

server.

Server /cimc/network # set

alternate-dns-server dns2-ipv4-address

Step 9

Commits the transaction to the system

configuration.

Server /cimc/network # commit

Step 10

(Optional) Displays the IPv4 network settings.Server /cimc/network # show [detail]

Step 11

This example configures and displays the IPv4 network settings:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set dhcp-enabled yes

Server /cimc/network *# set v4-addr 10.20.30.11

Server /cimc/network *# set v4-netmask 255.255.248.0

Server /cimc/network *# set v4-gateway 10.20.30.1

Server /cimc/network *# set dns-use-dhcp-enabled no

Server /cimc/network *# set preferred-dns-server 192.168.30.31

Server /cimc/network *# set alternate-dns-server 192.168.30.32

Server /cimc/network *# commit

Server /cimc/network # show detail

Network Setting:

IPv4 Address: 10.20.30.11

IPv4 Netmask: 255.255.248.0

IPv4 Gateway: 10.20.30.1

DHCP Enabled: yes

Obtain DNS Server by DHCP: no

Preferred DNS: 192.168.30.31

Alternate DNS: 192.168.30.32

VLAN Enabled: no

VLAN ID: 1

VLAN Priority: 0

Hostname: Server

MAC Address: 01:23:45:67:89:AB

NIC Mode: dedicated

NIC Redundancy: none

Server /cimc/network #

Configuring the Server VLAN

Before You Begin

You must be logged in as admin to configure the server VLAN.

Procedure

PurposeCommand or Action

Enters the CIMC command mode.Server# scope cimc

Step 1

Enters the CIMC network command mode.Server /cimc # scope network

Step 2

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 77

Configuring Network-Related Settings

Configuring the Server VLAN

PurposeCommand or Action

Selects whether the CIMC is connected to a

VLAN.

Server /cimc/network # set vlan-enabled

{yes |no}

Step 3

Specifies the VLAN number.

Server /cimc/network # set vlan-id id

Step 4

Specifies the priority of this system on the

VLAN.

Server /cimc/network # set vlan-priority

priority

Step 5

Commits the transaction to the system

configuration.

Server /cimc/network # commit

Step 6

(Optional) Displays the network settings.Server /cimc/network # show [detail]

Step 7

This example configures the server VLAN:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set vlan-enabled yes

Server /cimc/network *# set vlan-id 10

Server /cimc/network *# set vlan-priority 32

Server /cimc/network *# commit

Server /cimc/network # show detail

Network Setting:

IPv4 Address: 10.20.30.11

IPv4 Netmask: 255.255.248.0

IPv4 Gateway: 10.20.30.1

DHCP Enabled: yes

Obtain DNS Server by DHCP: no

Preferred DNS: 192.168.30.31

Alternate DNS: 192.168.30.32

VLAN Enabled: yes

VLAN ID: 10

VLAN Priority: 32

Hostname: Server

MAC Address: 01:23:45:67:89:AB

NIC Mode: dedicated

NIC Redundancy: none

Server /cimc/network #

Connecting to a Port Profile

You can configure a port profile or a VLAN, but you cannot use both. If you want to use a port profile,

make sure the set vlan-enabled command is set to no.

Note

Before You Begin

You must be logged in as admin to connect to a port profile.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

78 OL-28893-01

Configuring Network-Related Settings

Connecting to a Port Profile

Procedure

PurposeCommand or Action

Enters the CIMC command mode.Server# scope cimc

Step 1

Enters the CIMC network command mode.Server /cimc # scope network

Step 2

Specifies the port profile CIMC should use to configure the

management interface, the virtual Ethernet, and the VIF on

Server /cimc/network # set

port-profile port_profile_name

Step 3

supported adapter cards such as the Cisco UCS VIC1225

Virtual Interface Card.

Enter up to 80 alphanumeric characters. You cannot use

spaces or other special characters except for - (hyphen) and

_ (underscore). In addition, the port profile name cannot begin

with a hyphen.

The port profile must be defined on the switch to

which this server is connected.

Note

Commits the transaction to the system configuration.Server /cimc/network # commit

Step 4

(Optional)

Displays the network settings.

Server /cimc/network # show

[detail]

Step 5

This example connects to port profile abcde12345:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # set port-profile abcde12345

Server /cimc/network *# commit

Server /cimc/network # show detail

Network Setting:

IPv4 Address: 10.193.66.174

IPv4 Netmask: 255.255.248.0

IPv4 Gateway: 10.193.64.1

DHCP Enabled: no

Obtain DNS Server by DHCP: no

Preferred DNS: 0.0.0.0

Alternate DNS: 0.0.0.0

VLAN Enabled: no

VLAN ID: 1

VLAN Priority: 0

Port Profile: abcde12345

Hostname: Server

MAC Address: 50:3D:E5:9D:63:3C

NIC Mode: dedicated

NIC Redundancy: none

Server /cimc/network #

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 79

Configuring Network-Related Settings

Connecting to a Port Profile

Network Security Configuration

Network Security

The CIMC uses IP blocking as network security. IP blocking prevents the connection between a server or

website and certain IP addresses or ranges of addresses. IP blocking effectively bans undesired connections

from those computers to a website, mail server, or other Internet servers.

IP banning is commonly used to protect against denial of service (DoS) attacks. CIMC bans IP addresses by

setting up an IP blocking fail count.

Configuring Network Security

Configure network security if you want to set up an IP blocking fail count.

Before You Begin

You must log in as a user with admin privileges to configure network security.

Procedure

PurposeCommand or Action

Enters the CIMC command mode.Server# scope cimc

Step 1

Enters the CIMC network command mode.Server /cimc # scope network

Step 2

Enters the IP blocking command mode.Server /cimc/network # scope

ipblocking

Step 3

Enables or disables IP blocking.Server /cimc/network/ipblocking #

set enabled {yes |no}

Step 4

Sets the number of times a user can attempt to log in

unsuccessfully before the system locks that user out for

a specified length of time.

Server /cimc/network/ipblocking #

set fail-count fail-count

Step 5

The number of unsuccessful login attempts must occur

within the time frame specified in the IP Blocking Fail

Window field.

Enter an integer between 3 and 10.

Sets the length of time, in seconds, in which the

unsuccessful login attempts must occur in order for the

user to be locked out.

Server /cimc/network/ipblocking #

set fail-window fail-seconds

Step 6

Enter an integer between 60 and 120.

Sets the number of seconds the user remains locked out

if they exceed the maximum number of login attempts

within the specified time window.

Server /cimc/network/ipblocking #

set penalty-time penalty-seconds

Step 7

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

80 OL-28893-01

Configuring Network-Related Settings

Network Security Configuration

PurposeCommand or Action

Enter an integer between 300 and 900.

Commits the transaction to the system configuration.Server /cimc/network/ipblocking #

commit

Step 8

This example configures IP blocking:

Server# scope cimc

Server /cimc # scope network

Server /cimc/network # scope ipblocking

Server /cimc/network/ipblocking # set enabled yes

Server /cimc/network/ipblocking *# set fail-count 5

Server /cimc/network/ipblocking *# set fail-window 90

Server /cimc/network/ipblocking *# set penalty-time 600

Server /cimc/network/ipblocking *# commit

Server /cimc/network/ipblocking #

Network Time Protocol Configuration

Configuring Network Time Protocol Settings

By default, when CIMC is reset, it synchronizes the time with the host. With the introduction of the NTP

service, you can configure CIMC to synchronize the time with an NTP server. The NTP server does not run

in CIMC by default. You must enable and configure the NTP service by specifying the IP/DNS address of at

least one server or a maximum of four servers that function as NTP servers or time source servers. When you

enable the NTP service, CIMC synchronizes the time with the configured NTP server. The NTP service can

be modified only through CIMC.

To enable the NTP service, it is preferable to specify the IP address of a server rather than the DNS address.Note

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters CIMC command mode.Server # scope cimc

Step 1

Enters network command mode.Server /cimc # scope network

Step 2

Enters NTP service command mode.Server /cimc/network # scope ntp

Step 3

Enables the NTP service on the server.Server /cimc/network/ntp # set enabled

yes

Step 4

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 81

Configuring Network-Related Settings

Network Time Protocol Configuration

PurposeCommand or Action

Commits the transaction.Server /cimc/network/ntp* # commit

Step 5

Specifies the IP/DNS address of one of the four

servers that act as an NTP server or the time source

server.

Server /cimc/network/ntp # set server-1

10.120.33.44

Step 6

Specifies the IP/DNS address of one of the four

servers that act as an NTP server or the time source

server.

Server /cimc/network/ntp # set server-2

10.120.34.45

Step 7

Specifies the IP/DNS address of one of the four

servers that act as an NTP server or the time source

server.

Server /cimc/network/ntp # set server-3

10.120.35.46

Step 8

Specifies the IP/DNS address of one of the four

servers that act as an NTP server or the time source

server.

Server /cimc/network/ntp # set server-4

10.120.36.48

Step 9

Commits the transaction.Server /cimc/network/ntp # commit

Step 10

This example shows how to configure the NTP service:

Server # scope cimc

Server /cimc # scope network

Server /cimc/network # scope ntp

Server /cimc/network/ntp # set enabled yes

Warning: IPMI Set SEL Time Command will be

disabled if NTP is enabled.

Do you wish to continue? [y|N]

Server /cimc/network/ntp* # commit

Server /cimc/network/ntp # set server-1 10.120.33.44

Server /cimc/network/ntp* # set server-2 10.120.34.45

Server /cimc/network/ntp* # set server-3 10.120.35.46

Server /cimc/network/ntp* # set server-4 10.120.36.48

Server /cimc/network/ntp* # commit

Server /cimc/network/ntp #

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

82 OL-28893-01

Configuring Network-Related Settings

Configuring Network Time Protocol Settings

CHAPTER 9

Managing Network Adapters

This chapter includes the following sections:

•Overview of the Cisco UCS C-Series Network Adapters, page 83

•Viewing Network Adapter Properties, page 85

•Configuring Network Adapter Properties, page 85

•Managing vHBAs, page 86

•Managing vNICs, page 99

•Managing VM FEX, page 109

•Managing Storage Adapters, page 115

•Backing Up and Restoring the Adapter Configuration, page 127

•Managing Adapter Firmware, page 130

•Resetting the Adapter, page 131

Overview of the Cisco UCS C-Series Network Adapters

The procedures in this chapter are available only when a Cisco UCS C-Series network adapter is installed

in the chassis.

Note

A Cisco UCS C-Series network adapter can be installed to provide options for I/O consolidation and

virtualization support. The following adapters are available:

•Cisco UCS P81E Virtual Interface Card

•Cisco UCS VIC1225 Virtual Interface Card

The interactive UCS Hardware and Software Interoperability Utility lets you view the supported components

and configurations for a selected server model and software release. The utility is available at the following

URL: http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 83

Cisco UCS P81E Virtual Interface Card

The Cisco UCS P81E Virtual Interface Card is optimized for virtualized environments, for organizations that

seek increased mobility in their physical environments, and for data centers that want reduced costs through

NIC, HBA, cabling, and switch reduction and reduced management overhead. This Fibre Channel over Ethernet

(FCoE) PCIe card offers the following benefits:

•Allows up to 16 virtual Fibre Channel and 16 virtual Ethernet adapters to be provisioned in virtualized

or nonvirtualized environments using just-in-time provisioning, providing tremendous system flexibility

and allowing consolidation of multiple physical adapters.

•Delivers uncompromising virtualization support, including hardware-based implementation of Cisco

VN-Link technology and pass-through switching.

•Improves system security and manageability by providing visibility and portability of network polices

and security all the way to the virtual machine.

The virtual interface card makes Cisco VN-Link connections to the parent fabric interconnects, which allows

virtual links to connect virtual NICs in virtual machines to virtual interfaces in the interconnect. In a Cisco

Unified Computing System environment, virtual links then can be managed, network profiles applied, and

interfaces dynamically reprovisioned as virtual machines move between servers in the system.

Cisco UCS VIC1225 Virtual Interface Card

The Cisco UCS VIC1225 Virtual Interface Card is a high-performance, converged network adapter that

provides acceleration for the various new operational modes introduced by server virtualization. It brings

superior flexibility, performance, and bandwidth to the new generation of Cisco UCS C-Series Rack-Mount

Servers.

The Cisco UCS VIC 1225 implements the Cisco Virtual Machine Fabric Extender (VM-FEX), which unifies

virtual and physical networking into a single infrastructure. It provides virtual-machine visibility from the

physical network and a consistent network operations model for physical and virtual servers. In virtualized

environments, this highly configurable and self-virtualized adapter provides integrated, modular LAN interfaces

on Cisco UCS C-Series Rack-Mount Servers. Additional features and capabilities include:

•Supports up to 256 PCIe virtual devices, either virtual network interface cards (vNICs) or virtual host

bus adapters (vHBAs), with high I/O operations per second (IOPS), support for lossless Ethernet, and

20 Gbps to servers.

•PCIe Gen2 x16 helps assure optimal bandwidth to the host for network-intensive applications with a

redundant path to the fabric interconnect.

•Half-height design reserves full-height slots in servers for Cisco certified third-party adapters.

•Centrally managed by Cisco UCS Manager with support for Microsoft Windows, Red Hat Enterprise

Linux, SUSE Linux, VMware vSphere, and Citrix XenServer.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

84 OL-28893-01

Managing Network Adapters

Overview of the Cisco UCS C-Series Network Adapters

Viewing Network Adapter Properties

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Displays adapter properties. To display the properties

of a single adapter, specify the PCI slot number as the

index argument.

Server /chassis # show adapter

[index] [detail]

Step 2

This example displays the properties of adapter 2:

Server# scope chassis

Server /chassis # show adapter

PCI Slot Product Name Serial Number Product ID Vendor

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

1 UCS VIC 1225 FCH1613796C UCSC-PCIE-C... Cisco Systems Inc

Server /chassis # show adapter 2 detail

PCI Slot 2:

Product Name: UCS VIC 1225

Serial Number: FCH1613796C

Product ID: UCSC-PCIE-CSC-02

Adapter Hardware Revision: 4

Current FW Version: 2.1(0.291)

NIV: Disabled

FIP: Enabled

Configuration Pending: no

CIMC Management Enabled : no

VID: V00

Vendor: Cisco Systems Inc

Description:

Bootloader Version: 2.1(0.291)

FW Image 1 Version: 2.1(0.291)

FW Image 1 State: RUNNING ACTIVATED

FW Image 2 Version: 1.6(0.547)

FW Image 2 State: BACKUP INACTIVATED

FW Update Status: Idle

FW Update Error: No error

FW Update Stage: No operation (0%)

FW Update Overall Progress: 0%

Server /chassis #

Configuring Network Adapter Properties

Before You Begin

•You must log in with admin privileges to perform this task.

•A supported Virtual Interface Card (VIC) must be installed in the chassis and the server must be powered

on.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 85

Managing Network Adapters

Viewing Network Adapter Properties

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

(Optional) Displays the available adapter devices.Server /chassis # show adapter

Step 2

Enters the command mode for the adapter card at the PCI

slot number specified by index.

Server /chassis # scope adapter

index

Step 3

The server must be powered on before you can view

or change adapter settings.

Note

Enables or disables FCoE Initialization Protocol (FIP) on

the adapter card. FIP is enabled by default.

Server /chassis/adapter # set

fip-mode {disable |enable}

Step 4

We recommend that you disable this option only

when explicitly directed to do so by a technical

support representative.

Note

Enables or disables Network Interface Virtualization (NIV)

on the adapter card. NIV is disabled by default.

Server /chassis/adapter # set

niv-mode {disable |enable}

Step 5

If NIV mode is enabled, vNICs:

•Can be assigned to a specific channel

•Can be associated with a port profile

•Can fail over to another vNIC if there are

communication problems

If NIV mode is enabled, port-count specifies the number of

VM FEX interfaces you want CIMC to create, from 0 to 112.

Server /chassis/adapter #

configure-vmfex port-count

Step 6

Commits the transaction to the system configuration.Server /chassis/adapter # commit

Step 7

This example configures the properties of adapter 1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # set fip-mode enable

Server /chassis/adapter *# commit

Server /chassis/adapter #

Managing vHBAs

Guidelines for Managing vHBAs

When managing vHBAs, consider the following guidelines and restrictions:

•The Cisco UCS P81E Virtual Interface Card and Cisco UCS VIC1225 Virtual Interface Card provide

two vHBAs (fc0 and fc1). You can create up to 16 additional vHBAs on these adapter cards.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

86 OL-28893-01

Managing Network Adapters

Managing vHBAs

If Network Interface Virtualization (NIV) mode is enabled for the adapter, you must

assign a channel number to a vHBA when you create it.

Note

•When using the Cisco UCS P81E Virtual Interface Card or Cisco UCS VIC1225 Virtual Interface Card

in an FCoE application, you must associate the vHBA with the FCoE VLAN. Follow the instructions

in to assign the VLAN.

•After making configuration changes, you must reboot the host for settings to take effect.

Viewing vHBA Properties

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at the

PCI slot number specified by index.

Server /chassis # scope adapter index

Step 2

The server must be powered on before you

can view or change adapter settings.

Note

Displays properties of a single vHBA, if specified, or

all vHBAs.

Server /chassis/adapter # show

host-fc-if [fc0 |fc1 |name] [detail]

Step 3

This example displays all vHBAs on adapter card 1 and the detailed properties of fc0:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # show host-fc-if

Name World Wide Port Name FC SAN Boot Uplink Port

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

fc0 20:00:00:22:BD:D6:5C:35 Disabled 0

fc1 20:00:00:22:BD:D6:5C:36 Disabled 1

Server /chassis/adapter # show host-fc-if fc0 detail

Name fc0:

World Wide Node Name: 10:00:00:22:BD:D6:5C:35

World Wide Port Name: 20:00:00:22:BD:D6:5C:35

FC SAN Boot: Disabled

Persistent LUN Binding: Disabled

Uplink Port: 0

MAC Address: 00:22:BD:D6:5C:35

CoS: 3

VLAN: NONE

Rate Limiting: OFF

PCIe Device Order: ANY

EDTOV: 2000

RATOV: 10000

Maximum Data Field Size: 2112

Channel Number: 3

Port Profile:

Server /chassis/adapter #

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 87

Managing Network Adapters

Viewing vHBA Properties

Modifying vHBA Properties

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

(Optional) Displays the available adapter devices.Server /chassis # show adapter

Step 2

Enters the command mode for the adapter card at the

PCI slot number specified by index.

Server /chassis # scope adapter index

Step 3

The server must be powered on before you

can view or change adapter settings.

Note

Enters the host Fibre Channel interface command

mode for the specified vHBA.

Server /chassis/adapter # scope host-fc-if

{fc0 |fc1 |name}

Step 4

Specifies a unique World Wide Node Name (WWNN)

for the adapter in the form hh:hh:hh:hh:hh:hh:hh:hh.

Server /chassis/adapter/host-fc-if # set

wwnn wwnn

Step 5

Unless specified by this command, the WWNN is

generated automatically by the system.

Specifies a unique World Wide Port Name (WWPN)

for the adapter in the form hh:hh:hh:hh:hh:hh:hh:hh.

Server /chassis/adapter/host-fc-if # set

wwpn wwpn

Step 6

Unless specified by this command, the WWPN is

generated automatically by the system.

Enables or disables FC SAN boot. The default is

disable.

Server /chassis/adapter/host-fc-if # set

boot {disable |enable}

Step 7

Enables or disables persistent LUN binding. The

default is disable.

Server /chassis/adapter/host-fc-if # set

persistent-lun-binding {disable |

enable}

Step 8

Specifies a MAC address for the vHBA.Server /chassis/adapter/host-fc-if # set

mac-addr mac-addr

Step 9

Specifies the default VLAN for this vHBA. Valid

VLAN numbers are 1 to 4094; the default is none.

Server /chassis/adapter/host-fc-if # set

vlan {none |vlan-id}

Step 10

Specifies the class of service (CoS) value to be marked

on received packets unless the vHBA is configured

Server /chassis/adapter/host-fc-if # set

cos cos-value

Step 11

to trust host CoS. Valid CoS values are 0 to 6; the

default is 0. Higher values indicate more important

traffic.

This setting is not functional in NIV mode.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

88 OL-28893-01

Managing Network Adapters

Modifying vHBA Properties

PurposeCommand or Action

Specifies a maximum data rate for the vHBA. The

range is 1 to 10000 Mbps; the default is off.

Server /chassis/adapter/host-fc-if # set

rate-limit {off |rate}

Step 12

This setting is not functional in NIV mode.

Specifies the relative order of this device for PCIe bus

device number assignment; the default is any.

Server /chassis/adapter/host-fc-if # set

order {any |0-99}

Step 13

Specifies the error detect timeout value (EDTOV),

the number of milliseconds to wait before the system

Server /chassis/adapter/host-fc-if # set

error-detect-timeout msec

Step 14

assumes that an error has occurred. The range is 1000

to 100000; the default is 2000 milliseconds.

Specifies the resource allocation timeout value

(RATOV), the number of milliseconds to wait before

Server /chassis/adapter/host-fc-if # set

resource-allocation-timeout msec

Step 15

the system assumes that a resource cannot be properly

allocated. The range is 5000 to 100000; the default is

10000 milliseconds.

Specifies the maximum size of the Fibre Channel

frame payload (in bytes) that the vHBA supports. The

range is 1 to 2112; the default is 2112 bytes.

Server /chassis/adapter/host-fc-if # set

max-field-size size

Step 16

Enters the Fibre Channel error recovery command

mode.

Server /chassis/adapter/host-fc-if # scope

error-recovery

Step 17

Enables or disables FCP Error Recovery. The default

is disable.

Server

/chassis/adapter/host-fc-if/error-recovery

#set fcp-error-recovery {disable |

enable}

Step 18

Specifies the link down timeout value, the number of

milliseconds the uplink port should be offline before

Server

/chassis/adapter/host-fc-if/error-recovery

#set link-down-timeout msec

Step 19

it informs the system that the uplink port is down and

fabric connectivity has been lost. The range is 0 to

240000; the default is 30000 milliseconds.

Specifies the port down I/O retries value, the number

of times an I/O request to a port is returned because

Server

/chassis/adapter/host-fc-if/error-recovery

#set port-down-io-retry-count count

Step 20

the port is busy before the system decides the port is

unavailable. The range is 0 to 255; the default is 8

retries.

Specifies the port down timeout value, the number of

milliseconds a remote Fibre Channel port should be

Server

/chassis/adapter/host-fc-if/error-recovery

#set port-down-timeout msec

Step 21

offline before informing the SCSI upper layer that the

port is unavailable. The range is 0 to 240000; the

default is 10000 milliseconds.

Exits to the host Fibre Channel interface command

mode.

Server

/chassis/adapter/host-fc-if/error-recovery

#exit

Step 22

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 89

Managing Network Adapters

Modifying vHBA Properties

PurposeCommand or Action

Enters the interrupt command mode.Server /chassis/adapter/host-fc-if # scope

interrupt

Step 23

Specifies the Fibre Channel interrupt mode. The

modes are as follows:

Server

/chassis/adapter/host-fc-if/interrupt # set

interrupt-mode {intx |msi |msix}

Step 24

•intx —Line-based interrupt (INTx)

•msi —Message-Signaled Interrupt (MSI)

•msix —Message Signaled Interrupts with the

optional extension (MSIx). This is the

recommended and default option.

Exits to the host Fibre Channel interface command

mode.

Server

/chassis/adapter/host-fc-if/interrupt # exit

Step 25

Enters the Fibre Channel port command mode.Server /chassis/adapter/host-fc-if # scope

port

Step 26

Specifies the I/O throttle count, the number of I/O

operations that can be pending in the vHBA at one

Server /chassis/adapter/host-fc-if/port #

set outstanding-io-count count

Step 27

time. The range is 1 to 1024; the default is 512

operations.

Specifies the maximum logical unit numbers (LUNs)

per target, the maximum number of LUNs that the

Server /chassis/adapter/host-fc-if/port #

set max-target-luns count

Step 28

driver will discover. This is usually an operating

system platform limitation. The range is 1 to 1024;

the default is 256 LUNs.

Exits to the host Fibre Channel interface command

mode.

Server /chassis/adapter/host-fc-if/port #

exit

Step 29

Enters the Fibre Channel fabric login command mode.Server /chassis/adapter/host-fc-if # scope

port-f-logi

Step 30

Specifies the fabric login (FLOGI) retries value, the

number of times that the system tries to log in to the

Server

/chassis/adapter/host-fc-if/port-f-logi #

set flogi-retries {infinite |count}

Step 31

fabric after the first failure. Enter a number between

0 and 4294967295 or enter infinite ; the default is

infinite retries.

Specifies the fabric login (FLOGI) timeout value, the

number of milliseconds that the system waits before

Server

/chassis/adapter/host-fc-if/port-f-logi #

set flogi-timeout msec

Step 32

it tries to log in again. The range is 1 to 255000; the

default is 2000 milliseconds.

Exits to the host Fibre Channel interface command

mode.

Server

/chassis/adapter/host-fc-if/port-f-logi #

exit

Step 33

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

90 OL-28893-01

Managing Network Adapters

Modifying vHBA Properties

PurposeCommand or Action

Enters the Fibre Channel port login command mode.Server /chassis/adapter/host-fc-if # scope

port-p-logi

Step 34

Specifies the port login (PLOGI) retries value, the

number of times that the system tries to log in to the

Server

/chassis/adapter/host-fc-if/port-p-logi #

set plogi-retries count

Step 35

fabric after the first failure. The range is 0 and 255;

the default is 8 retries.

Specifies the port login (PLOGI) timeout value, the

number of milliseconds that the system waits before

Server

/chassis/adapter/host-fc-if/port-p-logi #

set plogi-timeout msec

Step 36

it tries to log in again. The range is 1 to 255000; the

default is 2000 milliseconds.

Exits to the host Fibre Channel interface command

mode.

Server

/chassis/adapter/host-fc-if/port-p-logi #

exit

Step 37

Enters the SCSI I/O command mode.Server /chassis/adapter/host-fc-if # scope

scsi-io

Step 38

The number of command descriptor block (CDB)

transmit queue resources to allocate. The range is 1

to 8; the default is 1.

Server /chassis/adapter/host-fc-if/scsi-io

#set cdb-wq-count count

Step 39

The number of descriptors in the command descriptor

block (CDB) transmit queue. The range is 64 to 512;

the default is 512.

Server /chassis/adapter/host-fc-if/scsi-io

#set cdb-wq-ring-size size

Step 40

Exits to the host Fibre Channel interface command

mode.

Server /chassis/adapter/host-fc-if/scsi-io

#exit

Step 41

Enters the Fibre Channel transmit queue command

mode.

Server /chassis/adapter/host-fc-if # scope

trans-queue

Step 42

The number of descriptors in the Fibre Channel

transmit queue. The range is 64 to 128; the default is

64.

Server

/chassis/adapter/host-fc-if/trans-queue #

set fc-wq-ring-size size

Step 43

Exits to the host Fibre Channel interface command

mode.

Server

/chassis/adapter/host-fc-if/trans-queue #

exit

Step 44

Enters the Fibre Channel receive queue command

mode.

Server /chassis/adapter/host-fc-if # scope

recv-queue

Step 45

The number of descriptors in the Fibre Channel

receive queue. The range is 64 to 128; the default is

64.

Server

/chassis/adapter/host-fc-if/recv-queue #

set fc-rq-ring-size size

Step 46

Exits to the host Fibre Channel interface command

mode.

Server

/chassis/adapter/host-fc-if/recv-queue #

exit

Step 47

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 91

Managing Network Adapters

Modifying vHBA Properties

PurposeCommand or Action

Commits the transaction to the system configuration.Server /chassis/adapter/host-fc-if #

commit

Step 48

The changes will take effect upon the next

server reboot.

Note

This example configures the properties of a vHBA:

Server# scope chassis

Server /chassis # show adapter

PCI Slot Product Name Serial Number Product ID Vendor

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

1 UCS VIC P81E QCI1417A0QK N2XX-ACPCI01 Cisco Systems Inc

Server /chassis # scope adapter 1

Server /chassis/adapter # scope host-fc-if fc1

Server /chassis/adapter/host-fc-if # set boot enable

Server /chassis/adapter/host-fc-if *# scope scsi-io

Server /chassis/adapter/host-fc-if/scsi-io *# set cdb-wq-count 2

Server /chassis/adapter/host-fc-if/scsi-io *# exit

Server /chassis/adapter/host-fc-if *# commit

Server /chassis/adapter/host-fc-if #

What to Do Next

Reboot the server to apply the changes.

Creating a vHBA

The adapter provides two permanent vHBAs. If NIV mode is enabled, you can create up to 16 additional

vHBAs.

Before You Begin

You must log in with user or admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at the PCI

slot number specified by index.

Server /chassis # scope adapter

index

Step 2

The server must be powered on before you can

view or change adapter settings.

Note

Creates a vHBA and enters the host Fibre Channel

interface command mode. The name argument can be up

to 32 ASCII characters.

Server /chassis/adapter # create

host-fc-if name

Step 3

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

92 OL-28893-01

Managing Network Adapters

Creating a vHBA

PurposeCommand or Action

(Optional)

If NIV mode is enabled for the adapter, you must assign

a channel number to this vHBA. The range is 1 to 1000.

Server /chassis/adapter/host-fc-if #

set channel-number number

Step 4

Commits the transaction to the system configuration.Server /chassis/adapter/host-fc-if #

commit

Step 5

The changes will take effect upon the next server

reboot.

Note

This example creates a vHBA on adapter 1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # create host-fc-if Vhba5

Server /chassis/adapter/host-fc-if *# commit

New host-fc-if settings will take effect upon the next server reset

Server /chassis/adapter/host-fc-if #

What to Do Next

•Reboot the server to create the vHBA.

•If configuration changes are required, configure the new vHBA as described in Modifying vHBA

Properties, on page 88.

Deleting a vHBA

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at the PCI

slot number specified by index.

Server /chassis # scope adapter

index

Step 2

The server must be powered on before you can

view or change adapter settings.

Note

Deletes the specified vHBA.Server /chassis/adapter # delete

host-fc-if name

Step 3

You cannot delete either of the two default

vHBAs, fc0 or fc1.

Note

Commits the transaction to the system configuration.Server /chassis/adapter # commit

Step 4

The changes will take effect upon the next server

reboot.

Note

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 93

Managing Network Adapters

Deleting a vHBA

This example deletes a vHBA on adapter 1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # delete host-fc-if Vhba5

Server /chassis/adapter *# commit

Server /chassis/adapter #

vHBA Boot Table

In the vHBA boot table, you can specify up to four LUNs from which the server can boot.

Viewing the Boot Table

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at the

PCI slot number specified by index.

Server /chassis # scope adapter index

Step 2

The server must be powered on before you

can view or change adapter settings.

Note

Enters the host Fibre Channel interface command mode

for the specified vHBA.

Server /chassis/adapter # scope

host-fc-if {fc0 |fc1 |name}

Step 3

Displays the boot table of the Fibre Channel interface.Server /chassis/adapter/host-fc-if #

show boot

Step 4

This example displays the boot table for a vHBA:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # scope host-fc-if fc1

Server /chassis/adapter/host-fc-if # show boot

Boot Table Entry Boot Target WWPN Boot LUN ID

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

0 20:00:00:11:22:33:44:55 3

1 20:00:00:11:22:33:44:56 5

Server /chassis/adapter/host-fc-if #

Creating a Boot Table Entry

You can create up to four boot table entries.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

94 OL-28893-01

Managing Network Adapters

vHBA Boot Table

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at the PCI

slot number specified by index.

Server /chassis # scope adapter

index

Step 2

The server must be powered on before you can

view or change adapter settings.

Note

Enters the host Fibre Channel interface command mode

for the specified vHBA.

Server /chassis/adapter # scope

host-fc-if {fc0 |fc1 |name}

Step 3

Creates a boot table entry.Server /chassis/adapter/host-fc-if #

create-boot-entry wwpn lun-id

Step 4

•wwpn —The World Wide Port Name (WWPN) for

the boot target in the form hh:hh:hh:hh:hh:hh:hh:hh.

•lun-id —The LUN ID of the boot LUN. The range

is 0 to 255.

Commits the transaction to the system configuration.Server /chassis/adapter/host-fc-if #

commit

Step 5

The changes will take effect upon the next server

reboot.

Note

This example creates a boot table entry for vHBA fc1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # scope host-fc-if fc1

Server /chassis/adapter/host-fc-if # create-boot-entry 20:00:00:11:22:33:44:55 3

Server /chassis/adapter/host-fc-if *# commit

New boot table entry will take effect upon the next server reset

Server /chassis/adapter/host-fc-if #

Deleting a Boot Table Entry

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at the PCI

slot number specified by index.

Server /chassis # scope adapter

index

Step 2

The server must be powered on before you can

view or change adapter settings.

Note

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 95

Managing Network Adapters

Deleting a Boot Table Entry

PurposeCommand or Action

Enters the host Fibre Channel interface command mode

for the specified vHBA.

Server /chassis/adapter # scope

host-fc-if {fc0 |fc1 |name}

Step 3

Displays the boot table. From the Boot Table Entry field,

locate the number of the entry to be deleted.

Server /chassis/adapter/host-fc-if #

show boot

Step 4

Deletes the boot table entry at the specified position in

the table. The range of entry is 0 to 3. The change will

take effect upon the next server reset.

Server /chassis/adapter/host-fc-if #

delete boot entry

Step 5

Commits the transaction to the system configuration.Server /chassis/adapter/host-fc-if #

commit

Step 6

The changes will take effect upon the next server

reboot.

Note

This example deletes boot table entry number 1 for the vHBA fc1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # scope host-fc-if fc1

Server /chassis/adapter/host-fc-if # show boot

Boot Table Entry Boot Target WWPN Boot LUN ID

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

0 20:00:00:11:22:33:44:55 3

1 20:00:00:11:22:33:44:56 5

Server /chassis/adapter/host-fc-if # delete boot 1

Server /chassis/adapter/host-fc-if *# commit

New host-fc-if settings will take effect upon the next server reset

Server /chassis/adapter/host-fc-if # show boot

Boot Table Entry Boot Target WWPN Boot LUN ID

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

0 20:00:00:11:22:33:44:55 3

Server /chassis/adapter/host-fc-if #

What to Do Next

Reboot the server to apply the changes.

vHBA Persistent Binding

Persistent binding ensures that the system-assigned mapping of Fibre Channel targets is maintained after a

reboot.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

96 OL-28893-01

Managing Network Adapters

vHBA Persistent Binding

Enabling Persistent Binding

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at

the PCI slot number specified by index.

Server /chassis # scope adapter index

Step 2

The server must be powered on before you

can view or change adapter settings.

Note

Enters the host Fibre Channel interface command

mode for the specified vHBA.

Server /chassis/adapter # scope host-fc-if

{fc0 |fc1 |name}

Step 3

Enters the persistent binding command mode for

the vHBA.

Server /chassis/adapter/host-fc-if # scope

perbi

Step 4

Enables persistent binding for the vHBA.Server /chassis/adapter/host-fc-if/perbi #

set persistent-lun-binding enable

Step 5

Commits the transaction to the system

configuration.

Server /chassis/adapter/host-fc-if/perbi #

commit

Step 6

This example enables persistent binding for a vHBA:

Server# scope chassis

Server /chassis # scope adapter 4

Server /chassis/adapter # scope host-fc-if fc1

Server /chassis/adapter/host-fc-if # scope perbi

Server /chassis/adapter/host-fc-if/perbi # set persistent-lun-binding enable

Server /chassis/adapter/host-fc-if/perbi *# commit

Server /chassis/adapter/host-fc-if/perbi #

Disabling Persistent Binding

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at

the PCI slot number specified by index.

Server /chassis # scope adapter index

Step 2

The server must be powered on before you

can view or change adapter settings.

Note

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 97

Managing Network Adapters

Enabling Persistent Binding

PurposeCommand or Action

Enters the host Fibre Channel interface command

mode for the specified vHBA.

Server /chassis/adapter # scope host-fc-if

{fc0 |fc1 |name}

Step 3

Enters the persistent binding command mode for

the vHBA.

Server /chassis/adapter/host-fc-if # scope

perbi

Step 4

Disables persistent binding for the vHBA.Server /chassis/adapter/host-fc-if/perbi #

set persistent-lun-binding disable

Step 5

Commits the transaction to the system

configuration.

Server /chassis/adapter/host-fc-if/perbi #

commit

Step 6

This example disables persistent binding for a vHBA:

Server# scope chassis

Server /chassis # scope adapter 4

Server /chassis/adapter # scope host-fc-if fc1

Server /chassis/adapter/host-fc-if # scope perbi

Server /chassis/adapter/host-fc-if/perbi # set persistent-lun-binding disable

Server /chassis/adapter/host-fc-if/perbi *# commit

Server /chassis/adapter/host-fc-if/perbi #

Rebuilding Persistent Binding

Before You Begin

Persistent binding must be enabled in the vHBA properties.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at the

PCI slot number specified by index.

Server /chassis # scope adapter index

Step 2

The server must be powered on before you

can view or change adapter settings.

Note

Enters the host Fibre Channel interface command

mode for the specified vHBA.

Server /chassis/adapter # scope

host-fc-if {fc0 |fc1 |name}

Step 3

Enters the persistent binding command mode for the

vHBA.

Server /chassis/adapter/host-fc-if #

scope perbi

Step 4

Rebuilds the persistent binding table for the vHBA.Server /chassis/adapter/host-fc-if/perbi

#rebuild

Step 5

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

98 OL-28893-01

Managing Network Adapters

Rebuilding Persistent Binding

This example rebuilds the persistent binding table for a vHBA:

Server# scope chassis

Server /chassis # scope adapter 4

Server /chassis/adapter # scope host-fc-if fc1

Server /chassis/adapter/host-fc-if # scope perbi

Server /chassis/adapter/host-fc-if/perbi # rebuild

Server /chassis/adapter/host-fc-if/perbi #

Managing vNICs

Guidelines for Managing vNICs

When managing vNICs, consider the following guidelines and restrictions:

•The Cisco UCS P81E Virtual Interface Card and Cisco UCS VIC1225 Virtual Interface Card provide

two default vNICs (eth0 and eth1). You can create up to 16 additional vNICs on these adapter cards.

If Network Interface Virtualization (NIV) mode is enabled for the adapter, you must

assign a channel number to a vNIC when you create it.

Note

•After making configuration changes, you must reboot the host for settings to take effect.

Viewing vNIC Properties

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at the

PCI slot number specified by index.

Server /chassis # scope adapter index

Step 2

The server must be powered on before you

can view or change adapter settings.

Note

Displays properties of a single vNIC, if specified, or

all vNICs.

Server /chassis/adapter # show

host-eth-if [eth0 |eth1 |name] [detail]

Step 3

This example displays the brief properties of all vNICs and the detailed properties of eth0:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # show host-eth-if

Name MTU Uplink Port MAC Address CoS VLAN PXE Boot

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

eth0 1500 0 00:22:BD:D6:5C:33 0 NONE Enabled

eth1 1500 1 00:22:BD:D6:5C:34 0 NONE Enabled

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 99

Managing Network Adapters

Managing vNICs

Server /chassis/adapter # show host-eth-if eth0 detail

Name eth0:

MTU: 1500

Uplink Port: 0

MAC Address: 00:22:BD:D6:5C:33

CoS: 0

Trust Host CoS: disabled

PCI Order: ANY

VLAN: NONE

VLAN Mode: TRUNK

Rate Limiting: OFF

PXE Boot: enabled

Channel Number: N/A

Port Profile: N/A

Uplink Failover: N/A

Uplink Failback Timeout: N/A

Server /chassis/adapter #

Modifying vNIC Properties

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

(Optional) Displays the available adapter devices.Server /chassis # show adapter

Step 2

Enters the command mode for the adapter card at the

PCI slot number specified by index.

Server /chassis # scope adapter index

Step 3

The server must be powered on before you can

view or change adapter settings.

Note

Enters the host Ethernet interface command mode for

the specified vNIC.

Server /chassis/adapter # scope

host-eth-if {eth0 |eth1 |name}

Step 4

Specifies the maximum transmission unit (MTU) or

packet size that the vNIC accepts. Valid MTU values

are 1500 to 9000 bytes; the default is 1500.

Server /chassis/adapter/host-eth-if # set

mtu mtu-value

Step 5

Specifies the uplink port associated with this vNIC. All

traffic for this vNIC goes through this uplink port.

Server /chassis/adapter/host-eth-if # set

uplink {0|1}

Step 6

Specifies a MAC address for the vNIC in the form

hh:hh:hh:hh:hh:hh or hhhh:hhhh:hhhh.

Server /chassis/adapter/host-eth-if # set

mac-addr mac-addr

Step 7

Specifies the class of service (CoS) value to be marked

on received packets unless the vNIC is configured to

Server /chassis/adapter/host-eth-if # set

cos cos-value

Step 8

trust host CoS. Valid CoS values are 0 to 6; the default

is 0. Higher values indicate more important traffic.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

100 OL-28893-01

Managing Network Adapters

Modifying vNIC Properties

PurposeCommand or Action

If NIV is enabled, this setting is determined

by the switch, and the command is ignored.

Note

Specifies whether the vNIC will trust host CoS or will

remark packets. The behavior is as follows:

Server /chassis/adapter/host-eth-if # set

trust-host-cos {disable |enable}

Step 9

•disable —Received packets are remarked with

the configured CoS. This is the default.

•enable —The existing CoS value of received

packets (host CoS) is preserved.

Specifies the relative order of this device for PCI bus

device number assignment; the default is any.

Server /chassis/adapter/host-eth-if # set

order {any |0-99}

Step 10

Specifies the default VLAN for this vNIC. Valid VLAN

numbers are 1 to 4094; the default is none.

Server /chassis/adapter/host-eth-if # set

vlan {none |vlan-id}

Step 11

If NIV is enabled, this setting is determined

by the switch, and the command is ignored.

Note

Specifies the VLAN mode for the vNIC. The modes

are as follows:

Server /chassis/adapter/host-eth-if # set

vlan-mode {access |trunk}

Step 12

•access —The vNIC belongs to only one VLAN.

•trunk —The vNIC can belong to more than one

VLAN. This is the default.

If NIV is enabled, this setting is determined

by the switch, and the command is ignored.

Note

Specifies a maximum data rate for the vNIC. The range

is 1 to 10000 Mbps; the default is off.

Server /chassis/adapter/host-eth-if # set

rate-limit {off |rate}

Step 13

If NIV is enabled, this setting is determined

by the switch, and the command is ignored.

Note

Specifies whether the vNIC can be used to perform a

PXE boot. The default is enable for the two default

vNICs, and disable for user-created vNICs.

Server /chassis/adapter/host-eth-if # set

boot {disable |enable}

Step 14

If NIV mode is enabled for the adapter, select the

channel number that will be assigned to this vNIC. The

range is 1 to 1000.

Server /chassis/adapter/host-eth-if # set

channel-number number

Step 15

If NIV mode is enabled for the adapter, select the port

profile that should be associated with the vNIC.

Server /chassis/adapter/host-eth-if # set

port-profile name

Step 16

The name must be a port profile defined on

the switch to which this server is connected.

Note

If NIV mode is enabled for the adapter, enable this

setting if traffic on this vNIC should fail over to the

Server /chassis/adapter/host-eth-if # set

uplink-failover {disable |enable}

Step 17

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 101

Managing Network Adapters

Modifying vNIC Properties

PurposeCommand or Action

secondary interface if there are communication

problems.

After a vNIC has started using its secondary interface,

this setting controls how long the primary interface

Server /chassis/adapter/host-eth-if # set

uplink-failback-timeout seconds

Step 18

must be available before the system resumes using the

primary interface for the vNIC.

Enter a number of seconds between 0 and 600.

Enters the interrupt command mode.Server /chassis/adapter/host-eth-if #

scope interrupt

Step 19

Specifies the number of interrupt resources. The range

is 1 to 514; the default is 8. In general, you should

Server

/chassis/adapter/host-eth-if/interrupt #

set interrupt-count count

Step 20

allocate one interrupt resource for each completion

queue.

The time to wait between interrupts or the idle period

that must be encountered before an interrupt is sent.

Server

/chassis/adapter/host-eth-if/interrupt #

set coalescing-time usec

Step 21

The range is 1 to 65535 microseconds; the default is

125. To turn off coalescing, enter 0 (zero).

The coalescing types are as follows:Server

/chassis/adapter/host-eth-if/interrupt #

set coalescing-type {idle |min}

Step 22

•idle —The system does not send an interrupt until

there is a period of no activity lasting as least as

long as the time specified in the coalescing time

configuration.

•min —The system waits for the time specified in

the coalescing time configuration before sending

another interrupt event. This is the default.

Specifies the Ethernet interrupt mode. The modes are

as follows:

Server

/chassis/adapter/host-eth-if/interrupt #

set interrupt-mode {intx |msi |msix}

Step 23

•intx —Line-based interrupt (PCI INTx)

•msi —Message-Signaled Interrupt (MSI)

•msix —Message Signaled Interrupts with the

optional extension (MSI-X). This is the

recommended and default option.

Exits to the host Ethernet interface command mode.Server

/chassis/adapter/host-eth-if/interrupt #

exit

Step 24

Enters receive queue command mode.Server /chassis/adapter/host-eth-if #

scope recv-queue

Step 25

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

102 OL-28893-01

Managing Network Adapters

Modifying vNIC Properties

PurposeCommand or Action

The number of receive queue resources to allocate. The

range is 1 to 256; the default is 4.

Server

/chassis/adapter/host-eth-if/recv-queue

#set rq-count count

Step 26

The number of descriptors in the receive queue. The

range is 64 to 4094; the default is 512.

Server

/chassis/adapter/host-eth-if/recv-queue

#set rq-ring-size size

Step 27

Exits to the host Ethernet interface command mode.Server

/chassis/adapter/host-eth-if/recv-queue

#exit

Step 28

Enters transmit queue command mode.Server /chassis/adapter/host-eth-if #

scope trans-queue

Step 29

The number of transmit queue resources to allocate.

The range is 1 to 256; the default is 1.

Server

/chassis/adapter/host-eth-if/trans-queue

#set wq-count count

Step 30

The number of descriptors in the transmit queue. The

range is 64 to 4094; the default is 256.

Server

/chassis/adapter/host-eth-if/trans-queue

#set wq-ring-size size

Step 31

Exits to the host Ethernet interface command mode.Server

/chassis/adapter/host-eth-if/trans-queue

#exit

Step 32

Enters completion queue command mode.Server /chassis/adapter/host-eth-if #

scope comp-queue

Step 33

The number of completion queue resources to allocate.

The range is 1 to 512; the default is 5.

Server

/chassis/adapter/host-eth-if/comp-queue

#set cq-count count

Step 34

In general, the number of completion queues equals the

number of transmit queues plus the number of receive

queues.

Exits to the host Ethernet interface command mode.Server

/chassis/adapter/host-eth-if/comp-queue

#exit

Step 35

Enters TCP offload command mode.Server /chassis/adapter/host-eth-if #

scope offload

Step 36

Enables or disables TCP Segmentation Offload as

follows:

Server

/chassis/adapter/host-eth-if/offload #

set tcp-segment-offload {disable |

enable}

Step 37

•disable —The CPU segments large TCP packets.

•enable —The CPU sends large TCP packets to

the hardware to be segmented. This option may

reduce CPU overhead and increase throughput

rate. This is the default.

This option is also known as Large Send

Offload (LSO).

Note

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 103

Managing Network Adapters

Modifying vNIC Properties

PurposeCommand or Action

Enables or disables TCP Receive Offload Checksum

Validation as follows:

Server

/chassis/adapter/host-eth-if/offload #

set tcp-rx-checksum-offload {disable

|enable}

Step 38

•disable —The CPU validates all packet

checksums.

•enable —The CPU sends all packet checksums

to the hardware for validation. This option may

reduce CPU overhead. This is the default.

Enables or disables TCP Transmit Offload Checksum

Validation as follows:

Server

/chassis/adapter/host-eth-if/offload #

set tcp-tx-checksum-offload {disable

|enable}

Step 39

•disable —The CPU validates all packet

checksums.

•enable —The CPU sends all packet checksums

to the hardware for validation. This option may

reduce CPU overhead. This is the default.

Enables or disables TCP Large Packet Receive Offload

as follows:

Server

/chassis/adapter/host-eth-if/offload #

set tcp-large-receive-offload {disable

|enable}

Step 40

•disable —The CPU processes all large packets.

•enable —The hardware reassembles all segmented

packets before sending them to the CPU. This

option may reduce CPU utilization and increase

inbound throughput. This is the default.

Exits to the host Ethernet interface command mode.Server

/chassis/adapter/host-eth-if/offload #

exit

Step 41

Enters Receive-side Scaling (RSS) command mode.Server /chassis/adapter/host-eth-if #

scope rss

Step 42

Enables or disables RSS, which allows the efficient

distribution of network receive processing across

Server /chassis/adapter/host-eth-if/rss #

set rss {disable |enable}

Step 43

multiple CPUs in multiprocessor systems. The default

is enable for the two default vNICs, and disable for

user-created vNICs.

Enables or disables IPv4 RSS. The default is enable.Server /chassis/adapter/host-eth-if/rss #

set rss-hash-ipv4 {disable |enable}

Step 44

Enables or disables TCP/IPv4 RSS. The default is

enable.

Server /chassis/adapter/host-eth-if/rss #

set rss-hash-tcp-ipv4 {disable |

enable}

Step 45

Enables or disables IPv6 RSS. The default is enable.Server /chassis/adapter/host-eth-if/rss #

set rss-hash-ipv6 {disable |enable}

Step 46

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

104 OL-28893-01

Managing Network Adapters

Modifying vNIC Properties

PurposeCommand or Action

Enables or disables TCP/IPv6 RSS. The default is

enable.

Server /chassis/adapter/host-eth-if/rss #

set rss-hash-tcp-ipv6 {disable |

enable}

Step 47

Enables or disables IPv6 Extension RSS. The default

is disable.

Server /chassis/adapter/host-eth-if/rss #

set rss-hash-ipv6-ex {disable |enable}

Step 48

Enables or disables TCP/IPv6 Extension RSS. The

default is disable.

Server /chassis/adapter/host-eth-if/rss #

set rss-hash-tcp-ipv6-ex {disable |

enable}

Step 49

Exits to the host Ethernet interface command mode.Server /chassis/adapter/host-eth-if/rss #

exit

Step 50

Commits the transaction to the system configuration.Server /chassis/adapter/host-eth-if #

commit

Step 51

The changes will take effect upon the next

server reboot.

Note

This example configures the properties of a vNIC:

Server# scope chassis

Server /chassis # show adapter

PCI Slot Product Name Serial Number Product ID Vendor

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

1 UCS VIC P81E QCI1417A0QK N2XX-ACPCI01 Cisco Systems Inc

Server /chassis # scope adapter 1

Server /chassis/adapter # scope host-eth-if Test1

Server /chassis/adapter/host-eth-if # set uplink 1

Server /chassis/adapter/host-eth-if *# scope offload

Server /chassis/adapter/host-eth-if/offload *# set tcp-segment-offload enable

Server /chassis/adapter/host-eth-if/offload *# exit

Server /chassis/adapter/host-eth-if *# commit

Server /chassis/adapter/host-eth-if #

What to Do Next

Reboot the server to apply the changes.

Creating a vNIC

The adapter provides two permanent vNICs. You can create up to 16 additional vNICs.

Before You Begin

You must log in with user or admin privileges to perform this task.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 105

Managing Network Adapters

Creating a vNIC

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at the PCI

slot number specified by index.

Server /chassis # scope adapter

index

Step 2

The server must be powered on before you can

view or change adapter settings.

Note

Creates a vNIC and enters the host Ethernet interface

command mode. The name argument can be up to 32

ASCII characters.

Server /chassis/adapter # create

host-eth-if name

Step 3

(Optional)

If NIV mode is enabled for the adapter, you must assign

a channel number to this vNIC. The range is 1 to 1000.

Server /chassis/adapter/host-eth-if #

set channel-number number

Step 4

Commits the transaction to the system configuration.Server /chassis/adapter/host-eth-if #

commit

Step 5

The changes will take effect upon the next server

reboot.

Note

This example creates a vNIC on adapter 1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # create host-eth-if Vnic5

Server /chassis/adapter/host-eth-if *# commit

New host-eth-if settings will take effect upon the next server reset

Server /chassis/adapter/host-eth-if #

Deleting a vNIC

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at the PCI

slot number specified by index.

Server /chassis # scope adapter

index

Step 2

The server must be powered on before you can

view or change adapter settings.

Note

Deletes the specified vNIC.Server /chassis/adapter # delete

host-eth-if name

Step 3

You cannot delete either of the two default vNICs,

eth0 or eth1.

Note

Commits the transaction to the system configuration.Server /chassis/adapter # commit

Step 4

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

106 OL-28893-01

Managing Network Adapters

Deleting a vNIC

PurposeCommand or Action

The changes will take effect upon the next server

reboot.

Note

This example deletes a vNIC on adapter 1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # delete host-eth-if Vnic5

Server /chassis/adapter *# commit

Server /chassis/adapter #

Configuring iSCSI Boot Capability

Configuring iSCSI Boot Capability for vNICs

When the rack-servers are configured in a standalone mode, and when the VIC adapters are directly attached

to the Nexus 5000 family of switches, you can configure these VIC adapters to boot the servers remotely from

iSCSI storage targets. You can configure Ethernet vNICs to enable a rack server to load the host OS image

from remote iSCSI target devices.

To configure the iSCSI boot capability on a vNIC:

•You must log in with admin privileges to perform this task.

•To configure a vNIC to boot a server remotely from an iSCSI storage target, you must enable the PXE

boot option on the vNIC.

You can configure a maximum of 2 iSCSI vNICs for each host.Note

Configuring iSCSI Boot Capability on a vNIC

You can configure a maximum of 2 iSCSI vNICs for each host.

Before You Begin

•To configure a vNIC to boot a server remotely from an iSCSI storage target, you must enable the PXE

boot option on the vNIC.

•You must log in with admin privileges to perform this task.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 107

Managing Network Adapters

Configuring iSCSI Boot Capability

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at

the PCI slot number specified by index.

Server /chassis # scope adapter index

Step 2

The server must be powered on before

you can view or change adapter settings.

Note

Enters the host Ethernet interface command mode

for the specified vNIC.

Server /chassis/adapter # scope host-eth-if

{eth0 |eth1 |name}

Step 3

Creates the iSCSI boot index for the vNIC. At this

moment, only 0 is allowed as the index.

Server /chassis/adapter/host-eth-if # create

iscsi-boot index

Step 4

Creates an iSCSI target for the vNIC. The value

can either be 0 or 1.

Server

/chassis/adapter/host-eth-if/iscsi-boot* #

create iscsi-target index

Step 5

Enables the DHCP network settings for the iSCSI

boot.

Server

/chassis/adapter/host-eth-if/iscsi-boot* # set

dhcp-net-settings enabled

Step 6

Sets the initiator name. It cannot be more than 223

characters.

Server

/chassis/adapter/host-eth-if/iscsi-boot* # set

initiator-name string

Step 7

Enables the DHCP iSCSI settings.Server

/chassis/adapter/host-eth-if/iscsi-boot* # set

dhcp-iscsi-settings enabled

Step 8

Commits the transaction to the system

configuration.

Server

/chassis/adapter/host-eth-if/iscsi-boot* #

commit

Step 9

The changes will take effect upon the

next server reboot.

Note

This example shows how to configure the iSCSI boot capability for a vNIC:

Server # scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # scope host-eth-if eth0

Server /chassis/adapter/host-eth-if # create iscsi-boot 0

Server /adapter/host-eth-if/iscsi-boot *# set dhcp-net-settings enabled

Server /adapter/host-eth-if/iscsi-boot *# set initiator-name iqn.2012-01.com.adser:abcde

Server /adapter/host-eth-if/iscsi-boot *# set dhcp-iscsi-settings enabled

Server /adapter/host-eth-if/iscsi-boot *# commit

New host-eth-if settings will take effect upon the next server reset

Server /adapter/host-eth-if/iscsi-boot #

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

108 OL-28893-01

Managing Network Adapters

Configuring iSCSI Boot Capability

Deleting an iSCSI Boot Configuration for a vNIC

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at the

PCI slot number specified by index.

Server /chassis # scope adapter index

Step 2

The server must be powered on before you

can view or change adapter settings.

Note

Enters the host Ethernet interface command mode for

the specified vNIC.

Server /chassis/adapter # scope

host-eth-if {eth0 |eth1 |name}

Step 3

Deletes the iSCSI boot capability for the vNIC.Server /chassis/adapter/host-eth-if #

delete iscsi-boot 0

Step 4

Commits the transaction to the system configurationServer /chassis/adapter/host-eth-if* #

commit

Step 5

The changes will take effect upon the next

server reboot.

Note

This example shows how to delete the iSCSI boot capability for a vNIC:

Server # scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # scope host-eth-if eth0

Server /chassis/adapter/host-eth-if # delete iscsi-boot 0

Server /adapter/host-eth-if/iscsi-boot *# commit

New host-eth-if settings will take effect upon the next server reset

Server /adapter/host-eth-if/iscsi-boot #

Managing VM FEX

Virtual Machine Fabric Extender

Cisco Virtual Machine Fabric Extender (VM FEX) extends the (prestandard) IEEE 802.1Qbh port extender

architecture to virtual machines. In this architecture, each VM interface is provided with a virtual Peripheral

Component Interconnect Express (PCIe) device and a virtual port on a switch.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 109

Managing Network Adapters

Managing VM FEX

Viewing VM FEX Properties

Before You Begin

•The server must be powered on, or the properties will not display.

•A supported Virtual Interface Card (VIC) must be installed in the chassis and the server must be powered

on.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at the

PCI slot number specified by index.

Server /chassis # scope adapter index

Step 2

The server must be powered on before you can

view or change adapter settings.

Note

Displays the general VM FEX properties. For field

descriptions, see General Properties Settings, on page

111.

Server /chassis/adapter # show vmfex

[detail]

Step 3

Enters the command mode for the specified VM FEX

interface.

Server /chassis/adapter # scope vmfex

name

Step 4

Displays Ethernet interrupt settings. For field

descriptions, see Ethernet Interrupt Settings, on page

112.

Server /chassis/adapter/vmfex # show

interrupt [detail]

Step 5

Displays Ethernet receive queue settings. For field

descriptions, see Ethernet Receive Queue Settings, on

page 113.

Server /chassis/adapter/vmfex # show

recv-queue [detail]

Step 6

Displays Ethernet transmit queue settings. For field

descriptions, see Ethernet Transmit Queue Settings, on

page 113.

Server /chassis/adapter/vmfex # show

trans-queue [detail]

Step 7

Displays completion queue settings. For field

descriptions, see Completion Queue Settings, on page

113.

Server /chassis/adapter/vmfex # show

comp-queue [detail]

Step 8

Displays TCP offload settings. For field descriptions,

see TCP Offload Settings, on page 114.

Server /chassis/adapter/vmfex # show

offload [detail]

Step 9

Displays RSS settings. For field descriptions, see

Receive Side Scaling Settings, on page 114.

Server /chassis/adapter/vmfex # show

rss [detail]

Step 10

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

110 OL-28893-01

Managing Network Adapters

Viewing VM FEX Properties

This example displays the VM FEX properties:

Server /chassis/adapter # show vmfex detail

Name pts0:

MTU: 1500

Uplink Port: 0

MAC Address: 00:00:00:00:00:00

CoS: N/A

Trust Host CoS:

PCI Order:

VLAN: N/A

VLAN Mode: N/A

Rate Limiting:

PXE Boot: disabled

Channel Number: 0

Port Profile:

Uplink Failover: Enabled

Uplink Failback Timeout: 5

Server /chassis/adapter # scope vmfex pts0

Server /chassis/adapter/vmfex # show interrupt

Interrupt Count Coalescing Time (us) Coalescing Type Interrupt Mode

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

6 125 MIN MSI

Server /chassis/adapter/vmfex # show recv-queue

Receive Queue Count Receive Queue Ring Size

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

4 512

Server /chassis/adapter/vmfex # show trans-queue

Transmit Queue Count Transmit Queue Ring Size

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

1 256

Server /chassis/adapter/vmfex # show comp-queue

Completion Queue Count Completion Queue Ring Size

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

5 1

Server /chassis/adapter/vmfex # show offload

TCP Segment Offload TCP Rx Checksum TCP Tx Checksum Large Receive

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

enabled enabled enabled enabled

Server /chassis/adapter/vmfex # show rss

TCP Rx Side Scaling

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

enabled

Server /chassis/adapter/vmfex #

VM FEX Settings

The following tables describe the VM FEX settings that you can view.

General Properties Settings

DescriptionName

A user-defined name for the VM FEX.Name

The maximum transmission unit, or packet size, that this VM FEX

accepts.

MTU

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 111

Managing Network Adapters

VM FEX Settings

DescriptionName

The uplink port associated with this VM FEX. All traffic for this VM

FEX goes through this uplink port.

Uplink Port

The MAC address associated with the VM FEX.MAC Address

The class of service to associate with traffic from this VM FEX.Class of Service

Whether the VM FEX can use the class of service provided by the host

operating system.

Trust Host CoS

The order in which this VM FEX will be used.PCI Order

The default VLAN for this VM FEX.Default VLAN

Whether VLAN trunking or access is configured.VLAN Mode

If rate limiting is configured, the maximum rate.Rate Limit

Whether the VM FEX can be used to perform a PXE boot.Enable PXE Boot

If NIV mode is enabled for the adapter, the channel number assigned

to this VM FEX.

Channel Number

If NIV mode is enabled for the adapter, the port profile associated with

theVM FEX.

This field displays the port profiles defined on the switch to

which this server is connected.

Note

Port Profile

If NIV mode is enabled for the adapter, whether traffic on this VM FEX

should fail over to the secondary interface if there are communication

problems.

Enable Uplink Failover

After a VM FEX has started using its secondary interface, this setting

controls how long the primary interface must be available before the

system resumes using the primary interface for the VM FEX.

Failback Timeout

Ethernet Interrupt Settings

DescriptionName

The number of interrupt resources allocated to this VM FEX.Interrupt Count field

The time CIMC waits between interrupts or the idle period that must

be encountered before an interrupt is sent.

Coalescing Time field

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

112 OL-28893-01

Managing Network Adapters

VM FEX Settings

DescriptionName

This can be one of the following:

•MIN—The system waits for the time specified in the Coalescing

Time field before sending another interrupt event.

•IDLE—The system does not send an interrupt until there is a

period of no activity lasting as least as long as the time specified

in the Coalescing Time field.

Coalescing Type field

The preferred driver interrupt mode. This can be one of the following:

•MSIx—Message Signaled Interrupts (MSI) with the optional

extension.

•MSI—MSI only.

•INTx—PCI INTx interrupts.

Interrupt Mode field

Ethernet Receive Queue Settings

DescriptionName

The number of receive queue resources allocated to this VM FEX.Receive Queue Count field

The number of descriptors in each receive queue.Receive Queue Ring Size field

Ethernet Transmit Queue Settings

DescriptionName

The number of transmit queue resources allocated to this VM FEX.Transmit Queue Count field

The number of descriptors in each transmit queue.Transmit Queue Ring Size field

Completion Queue Settings

DescriptionName

The number of completion queue resources allocated to this VM FEX.Completion Queue Count field

The number of descriptors in each completion queue.Completion Queue Ring Size

field

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 113

Managing Network Adapters

VM FEX Settings

TCP Offload Settings

DescriptionName

If enabled, the CPU sends large TCP packets to the hardware to be

segmented. If disabled, the CPU segments large packets.

This option is also known as Large Send Offload

(LSO).

Note

Enable TCP Segmentation

Offload field

If enabled, the CPU sends all packet checksums to the hardware for

validation. If disabled, the CPU validates all packet checksums.

Enable TCP Rx Offload

Checksum Validation field

If enabled, the CPU sends all packets to the hardware so that the

checksum can be calculated. If disabled, the CPU calculates all packet

checksums.

Enable TCP Tx Offload

Checksum Generation field

If enabled, the hardware reassembles all segmented packets before

sending them to the CPU. If disabled, the CPU processes all large

packets.

Enable Large Receive field

Receive Side Scaling Settings

DescriptionName

Receive Side Scaling (RSS) distributes network receive processing

across multiple CPUs in multiprocessor systems.

If enabled, network receive processing is shared across processors

whenever possible. If disabled, network receive processing is always

handled by a single processor even if additional processors are available.

Enable TCP Receive Side Scaling

field

If enabled, RSS is enabled on IPv4 networks.Enable IPv4 RSS field

If enabled, RSS is enabled for TCP transmissions across IPv4 networks.Enable TCP-IPv4 RSS field

If enabled, RSS is enabled on IPv6 networks.Enable IPv6 RSS field

If enabled, RSS is enabled for TCP transmissions across IPv6 networks.Enable TCP-IPv6 RSS field

If enabled, RSS is enabled for IPv6 extensions.Enable IPv6 Extension RSS field

If enabled, RSS is enabled for TCP transmissions across IPv6 networks.Enable TCP-IPv6 Extension RSS

field

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

114 OL-28893-01

Managing Network Adapters

VM FEX Settings

Managing Storage Adapters

Create Virtual Drive from Unused Physical Drives

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed storage card.Server /chassis # scope

storageadapter slot

Step 2

At this point, you are prompted to enter information

corresponding to the RAID level, the physical drives to be

Server /chassis/storageadapter #

create virtual-drive

Step 3

used, the size and the write policy for the new virtual drive.

Enter the appropriate information at each prompt.

When you have finished specifying the virtual drive

information, you are prompted to confirm that the

information is correct. Enter y(yes) to confirm, or n(no)

to cancel the operation.

Displays the existing virtual drives.Server /chassis/storageadapter #

show virtual-drive

Step 4

This example shows how to create a new virtual drive that spans two unused physical drives.

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # create-virtual-drive

Please enter RAID level

(0, 1, 5, 6, 10, 50, 60) --> 1

Please choose from the following 2 unused physical drives:

Slot 6: size 68664 MB

Slot 7: size 68664 MB

Specify physical disks for span 0:

Enter comma-separated PDs from above list--> 6,7

Please enter Virtual Drive name (15 characters maximum)--> test_v_drive

Please enter Virtual Drive size in MB, GB, or TB

Example format: '400 GB' --> 1000 MB

Optional attribute:

Write Policy: defaults to Write Back

OK? (y or n)--> n

0: Write Through

1: Write Back

2: Write Back with Bad BBU

3: Write Back Adaptive

Choose number from above options--> 2

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 115

Managing Network Adapters

Managing Storage Adapters

Write Policy will be set to Write Back with Bad BBU (2 and 'write-policy\:2')

New virtual drive will have the following characteristics:

- Spans: '[6.7]'

- RAID level: '1'

- Name: 'test_v_drive'

- Size: 1000 MB

- Write Policy: Write Back with Bad BBU

OK? (y or n)--> y

Server /chassis/storageadapter # show virtual-drive

Virtual Drive Health Status Name Size RAID Level

Boot Drive

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

----------

0 Good Optimal 150528 MB RAID 0

false

1 Good Optimal 20480 MB RAID 0

true

2 Good Optimal 114140 MB RAID 0

false

3 Good Optimal test_v_drive 1000 MB RAID 1

false

4 Good Optimal new_from_test 500 MB RAID 1

false

Server /chassis/storageadapter #

Create Virtual Drive from an Existing Drive Group

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed storage card.Server /chassis # scope

storageadapter slot

Step 2

At this point, you are prompted to enter information

corresponding to the virtual drives to be used, and the size

Server /chassis/storageadapter #

carve-virtual-drive

Step 3

and the write policy for the new virtual drive. Enter the

appropriate information at each prompt.

When you have finished specifying the virtual drive

information, you are prompted to confirm that the

information is correct. Enter y(yes) to confirm, or n(no)

to cancel the operation.

Displays the existing virtual drives.Server /chassis/storageadapter #

show virtual-drive

Step 4

This example shows how to carve a new virtual drive out of unused space in an existing RAID 1 drive group:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

116 OL-28893-01

Managing Network Adapters

Create Virtual Drive from an Existing Drive Group

Server /chassis/storageadapter # carve-virtual-drive

< Fetching virtual drives...>

ID Name RL VDSize MaxPossibleSize PD(s)

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

3 test_v_drive 1 1000 MB 67664 MB 6,7

Please choose from the above list the virtual drive number

whose space the new virtual drive will share--> 3

New virtual drive will share space with VD 3

Please enter Virtual Drive name (15 characters maximum)--> new_from_test

Please enter Virtual Drive size in MB, GB, or TB (maximum: 67664 MB)

Example format: '400 GB' --> 500 MB

Optional attribute:

Write Policy: defaults to Write Back

OK? (y or n)--> y

New virtual drive will have the following characteristics:

- It will share space with virtual drive 3

- Name: 'new_from_test'

- Size: 500 MB

OK? (y or n)--> y

Server /chassis/storageadapter # show virtual-drive

Virtual Drive Health Status Name Size RAID Level

Boot Drive

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

----------

0 Good Optimal 150528 MB RAID 0

false

1 Good Optimal 20480 MB RAID 0

true

2 Good Optimal 114140 MB RAID 0

false

3 Good Optimal test_v_drive 1000 MB RAID 1

false

4 Good Optimal new_from_test 500 MB RAID 1

false

Server /chassis/storageadapter #

Clearing Foreign Configuration

This task clears all foreign configuration on the controller. Also, all configuration information from all

physical drives hosting foreign configuration is deleted. This action cannot be reverted.

Important

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed storage card.Server /chassis # scope storageadapter

slot

Step 2

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 117

Managing Network Adapters

Clearing Foreign Configuration

PurposeCommand or Action

You are prompted to confirm the action. Enter yes

to confirm.

Server /chassis/storageadapter #

clear-foreign-config

Step 3

If you do not enter yes, the action is

aborted.

Note

This example shows how to clear all foreign configurations on the MegaRAID controller in slot 3:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # clear-foreign-config

Are you sure you want to clear all foreign configurations on this controller?

All data on the drive(s) will be lost.

Enter 'yes' to confirm -> yes

Server /chassis/storageadapter #

Deleting a Virtual Drive

This task deletes a virtual drive, including the drives that run the booted operating system. So back up any

data that you want to retain before you delete a virtual drive.

Important

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed storage

card.

Server /chassis # scope storageadapter slot

Step 2

Enters command mode for the specified virtual

drive.

Server /chassis/storageadapter # scope

virtual-drive drive-number

Step 3

You are prompted to confirm the action. Enter

yes to confirm.

Server /chassis/storageadapter/virtual-drive

#delete-virtual-drive

Step 4

If you do not enter yes, the action is

aborted.

Note

This example shows how to delete virtual drive 3.

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope virtual-drive 3

Server /chassis/storageadapter/virtual-drive # delete-virtual-drive

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

118 OL-28893-01

Managing Network Adapters

Deleting a Virtual Drive

Are you sure you want to delete virtual drive 3?

All data on the drive will be lost. Enter 'yes' to confirm -> yes

Server /chassis/storageadapter/virtual-drive #

Initializing a Virtual Drive

All data on a virtual drive is lost when you initialize the drive. Before you run an initialization, back up any

data on the virtual drive that you want to save.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed

storage card.

Server /chassis # scope storageadapter slot

Step 2

Enters command mode for the specified

virtual drive.

Server /chassis/storageadapter # scope

virtual-drive drive-number

Step 3

Initializes the specified virtual drive.Server /chassis/storageadapter/virtual-drive #

start-initialization

Step 4

(Optional) Cancels the initialization of the

specified virtual drive.

Server /chassis/storageadapter/virtual-drive #

cancel-initialization

Step 5

Displays the status of the task that is in

progress on the drive.

Server /chassis/storageadapter/physical-drive

#get-operation-status

Step 6

This example shows how to initialize virtual drive 3 using fast initialization:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope virtual-drive 3

Server /chassis/storageadapter/virtual-drive # start-initialization

Are you sure you want to initialize virtual drive 3?

All data on the drive will be lost. Enter 'yes' to confirm -> yes

Fast (0) or full (1) initialization? -> 0

Server /chassis/storageadapter/virtual-drive # get-operation-status

progress-percent: 20%

elapsed -seconds: 30

operation-in-progress: initializing virtual drive

Server /chassis/storageadapter/virtual-drive #

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 119

Managing Network Adapters

Initializing a Virtual Drive

Set as Boot Drive

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed storage

card.

Server /chassis # scope storageadapter slot

Step 2

Enters command mode for the specified virtual

drive.

Server /chassis/storageadapter # scope

virtual-drive drive-number

Step 3

Specifies the controller to boot from this

virtual drive.

Server /chassis/storageadapter #

set-boot-drive

Step 4

This example shows how to specify the controller to boot from virtual drive 3:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope virtual-drive 3

Server /chassis/storageadapter/virtual-drive # set-boot-drive

Are you sure you want to set virtual drive 3 as the boot drive?

Enter 'yes' to confirm -> yes

Server /chassis/storageadapter/virtual-drive #

Modifying Attributes of a Virtual Drive

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed

storage card.

Server /chassis # scope storageadapter slot

Step 2

Enters the command mode for the virtual

drive.

Server /chassis/storageadapter # scope

virtual-drive 3

Step 3

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

120 OL-28893-01

Managing Network Adapters

Set as Boot Drive

PurposeCommand or Action

Prompts you to select a different current

policy.

Server /chassis/storageadapter/virtual-drive #

modify-attributes

Step 4

This example shows how to carve a new virtual drive out of unused space in an existing RAID 1 drive group:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope virtual-drive

Server /chassis/storageadapter/virtual-drive # modify-attributes

Current write policy: Write Back

0: Write Through

1: Write Back

2: Write Back even if Bad BBU

Choose number from above options --> 0

The following attribute will be modified:

- Write policy: Write Through

OK? (y or n) --> y

operation in progress.

Server /chassis/storageadapter/virtual-drive #

Making a Dedicated Hot Spare

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed storage

card.

Server /chassis # scope storageadapter slot

Step 2

Enters command mode for the specified

physical drive.

Server /chassis/storageadapter # scope

physical-drive drive-number

Step 3

You are prompted to choose a virtual drive for

which the dedicated hot spare is being created.

Server /chassis/storageadapter/physical-drive

#make-dedicated-hot-spare

Step 4

This example shows how to make physical drive 3 a dedicated hot spare for virtual drive 6:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 121

Managing Network Adapters

Making a Dedicated Hot Spare

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive # make-dedicated-hot-spare

5: VD_OS_1, RAID 0, 102400 MB, physical disks: 1

6: VD_OS_2, RAID 0, 12288 MB, physical disks: 1

7: VD_OS_3, RAID 0, 12288 MB, physical disks: 1

8: VD_DATA_1, RAID 0, 12512 MB, physical disks: 1

9: RAID1_2358, RAID 1, 40000 MB, physical disks: 2,3,5,8

11: JFB_RAID1_67, RAID 1, 20000 MB, physical disks: 6,7

12: JFB_Crv_R1_40, RAID 1, 40000 MB, physical disks: 6,7

13: JFB_R1_10GB, RAID 1, 10000 MB, physical disks: 6,7

Please choose from the above 8 virtual drives-->6

Server /chassis/storageadapter/physical-drive #

Making a Global Hot Spare

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed

storage card.

Server /chassis # scope storageadapter slot

Step 2

Enters command mode for the specified

physical drive.

Server /chassis/storageadapter # scope

physical-drive drive-number

Step 3

Server /chassis/storageadapter/physical-drive #

make-global-hot-spare

Step 4

Displays the status of the task that is in

progress on the drive.

Server /chassis/storageadapter/physical-drive #

get-operation-status

Step 5

This example shows how to make physical drive 3 a global hot spare:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive # make-global-hot-spare

Server /chassis/storageadapter/physical-drive #

Preparing a Drive for Removal

You can confirm this task only on physical drives that display the Unconfigured Good status.

Before You Begin

You must log in with admin privileges to perform this task.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

122 OL-28893-01

Managing Network Adapters

Making a Global Hot Spare

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed

storage card.

Server /chassis # scope storageadapter slot

Step 2

Enters command mode for the specified

physical drive.

Server /chassis/storageadapter # scope

physical-drive drive-number

Step 3

Server /chassis/storageadapter/physical-drive #

prepare-for-removal

Step 4

This example shows how to prepare physical drive 3 for removal.

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive # prepare-for-removal

Server /chassis/storageadapter/physical-drive #

Removing a Drive from Hot Spare Pools

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed

storage card.

Server /chassis # scope storageadapter slot

Step 2

Enters command mode for the specified

physical drive.

Server /chassis/storageadapter # scope

physical-drive drive-number

Step 3

Removes a drive from the host spare pool.Server /chassis/storageadapter/physical-drive

#remove-hot-spare

Step 4

This example shows how to remove physical drive 3 from the hot spare pools:

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive # remove-hot-spare

Server /chassis/storageadapter/physical-drive #

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 123

Managing Network Adapters

Removing a Drive from Hot Spare Pools

Undo Preparing a Drive for Removal

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed

storage card.

Server /chassis # scope storageadapter slot

Step 2

Enters command mode for the specified

physical drive.

Server /chassis/storageadapter # scope

physical-drive drive-number

Step 3

Server /chassis/storageadapter/physical-drive #

undo-prepare-for-removal

Step 4

This example shows how to respin physical drive 3 after preparing the drive for removal.

Server# scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive # undo-prepare-for-removal

Server /chassis/storageadapter/physical-drive #

Enabling Auto Learn Cycles for the Battery Backup Unit

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed storage

card.

Server /chassis # scope storageadapter slot

Step 2

Enter the battery backup unit command mode.Server /chassis/storageadapter # scope bbu

Step 3

Enables the battery auto-learn cyclesServer /chassis/storageadapter #

enable-auto-learn

Step 4

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

124 OL-28893-01

Managing Network Adapters

Undo Preparing a Drive for Removal

This example shows how to enable the battery auto-learn cycles:

Server # scope chassis

Server /chassis # scope storageadapter SLOT-2

Server /chassis/storageadapter # scope bbu

Server /chassis/storageadapter/bbu # enable-auto-learn

Automatic BBU learn cycles will occur without notice if enabled.

Are you sure? [y/n] --> y

enable-auto-learn initiated

Server /chassis/storageadapter/bbu #

Disabling Auto Learn Cycles for the Battery Backup Unit

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed storage

card.

Server /chassis # scope storageadapter slot

Step 2

Enter the battery backup unit command mode.Server /chassis/storageadapter # scope bbu

Step 3

Disables the battery auto-learn cyclesServer /chassis/storageadapter #

disable-auto-learn

Step 4

This example shows how to disables the battery auto-learn cycles:

Server # scope chassis

Server /chassis # scope storageadapter SLOT-2

Server /chassis/storageadapter # scope bbu

Server /chassis/storageadapter/bbu # disable-auto-learn

Automatic BBU learn cycles will no longer occur if disabled.

Are you sure? [y/n] --> y

disable-auto-learn initiated

Server /chassis/storageadapter/bbu #

Starting a Learn Cycle for a Battery Backup Unit

Before You Begin

You must be logged in as an admin to use this command.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 125

Managing Network Adapters

Disabling Auto Learn Cycles for the Battery Backup Unit

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed storage

card.

Server /chassis # scope storageadapter slot

Step 2

Enter the battery backup unit command mode.Server /chassis/storageadapter # scope bbu

Step 3

Starts the learn cycle for the battery.Server /chassis/storageadapter #

start-learn-cycle

Step 4

This example shows how to initiate the learn cycles for a battery:

Server # scope chassis

Server /chassis # scope storageadapter SLOT-2

Server /chassis/storageadapter # scope bbu

Server /chassis/storageadapter/bbu # start-learn-cycle

Server /chassis/storageadapter/bbu #

Toggling the Locator LED for a Physical Drive

Before You Begin

You must be logged in as an admin to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed

storage card.

Server /chassis # scope storageadapter slot

Step 2

Enters the physical drive command mode.Server /chassis/storageadapter # scope

physical-drive 3

Step 3

Enables or disables the physical drive locator

LED.

Server /chassis/storageadapter/physical-drive

#locator-led {on | off}

Step 4

This example shows how to enable the locator LED for physical drive 3:

Server # scope chassis

Server /chassis # scope storageadapter SLOT-2

Server /chassis/storageadapter # scope physical-drive 3

Server /chassis/storageadapter/physical-drive # locator-led on

Server /chassis/storageadapter/physical-drive* # commit

Server /chassis/storageadapter/physical-drive #

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

126 OL-28893-01

Managing Network Adapters

Toggling the Locator LED for a Physical Drive

Viewing Storage Controller Logs

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters command mode for an installed storage

card.

Server /chassis # scope storageadapter slot

Step 2

Displays the storage controller logs.Server /chassis/storageadapter # show log

Step 3

This example shows how to display storage controller logs:

Server # scope chassis

Server /chassis # scope storageadapter SLOT-3

Server /chassis/storageadapter # show log

Time Severity Description

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

Fri March 1 09:52:19 2013 Warning Predictive Failure

Fri March 1 07:50:19 2013 Info Battery charge complete

Fri March 1 07:50:19 2013 Info Battery charge started

Fri March 1 07:48:19 2013 Info Battery relearn complete

Fri March 1 07:47:19 2013 Info Battery is discharging

Fri March 1 07:45:19 2013 Info Battery relearn started

Server /chassis/storageadapter #

Backing Up and Restoring the Adapter Configuration

Exporting the Adapter Configuration

The adapter configuration can be exported as an XML file to a TFTP server.

If any firmware or BIOS updates are in progress, do not export the adapter configuration until those tasks

are complete.

Important

Before You Begin

A supported Virtual Interface Card (VIC) must be installed in the chassis and the server must be powered on.

Obtain the TFTP server IP address.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 127

Managing Network Adapters

Viewing Storage Controller Logs

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at the PCI

slot number specified by index.

Server /chassis # scope adapter

index

Step 2

The server must be powered on before you can view

or change adapter settings.

Note

Starts the export operation. The adapter configuration file

will be stored at the specified path and filename on the remote

Server /chassis/adapter #

export-vnic protocol remote

server IP address

Step 3

server at the specified IP address. The protocol can be one

of the following:

•TFTP

•FTP

•SFTP

•SCP

•HTTP

This example exports the configuration of adapter 1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # export-vnic ftp 192.0.20.34 //test/dnld-ucs-k9-bundle.1.0.2h.bin

Server /chassis/adapter #

Importing the Adapter Configuration

If any firmware or BIOS updates are in progress, do not import the adapter configuration until those tasks

are complete.

Important

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Enters the command mode for the adapter card at the PCI

slot number specified by index.

Server /chassis # scope adapter

index

Step 2

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

128 OL-28893-01

Managing Network Adapters

Importing the Adapter Configuration

PurposeCommand or Action

The server must be powered on before you can

view or change adapter settings.

Note

Starts the import operation. The adapter downloads the

configuration file from the specified path on the TFTP server

Server /chassis/adapter #

import-vnic tftp-ip-address

path-and-filename

Step 3

at the specified IP address. The configuration will be

installed during the next server reboot.

This example imports a configuration for the adapter in PCI slot 1:

Server# scope chassis

Server /chassis # scope adapter 1

Server /chassis/adapter # import-vnic 192.0.2.34 /ucs/backups/adapter4.xml

Import succeeded.

New VNIC adapter settings will take effect upon the next server reset.

Server /chassis/adapter #

What to Do Next

Reboot the server to apply the imported configuration.

Restoring Adapter Defaults

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Restores factory default settings for the adapter at

the PCI slot number specified by the index

argument.

Server /chassis #

adapter-reset-defaults index

Step 2

This example restores the default configuration of the adapter in PCI slot 1:

Server# scope chassis

Server /chassis # adapter-reset-defaults 1

This operation will reset the adapter to factory default.

All your configuration will be lost.

Continue?[y|N] y

Server /chassis #

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 129

Managing Network Adapters

Restoring Adapter Defaults

Managing Adapter Firmware

Adapter Firmware

A Cisco UCS C-Series network adapter contains the following firmware components:

•Adapter firmware—The main operating firmware, consisting of an active and a backup image, can be

installed from the CIMC GUI or CLI interface or from the Host Upgrade Utility (HUU). You can upload

a firmware image from either a local file system or a TFTP server.

•Bootloader firmware—The bootloader firmware cannot be installed from the CIMC GUI or CLI. You

can install this firmware using the Host Upgrade Utility.

Installing Adapter Firmware

If any firmware or BIOS updates are in progress, do not install the adapter firmware until those tasks are

complete.

Important

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Downloads the specified adapter firmware file from the

TFTP server, then installs the firmware as the backup

Server /chassis # update-adapter-fw

tftp-ip-address path-and-filename

Step 2

image on one or two specified adapters or, if no adapter

{activate |no-activate} [ pci-slot ]

[pci-slot ]is specified, on all adapters. If the activate keyword is

specified, the new firmware is activated after installation.

(Optional)

Clears an incomplete firmware update condition on one

or two specified adapters or, if no adapter is specified,

on all adapters.

Server /chassis #

recover-adapter-update [pci-slot ]

[pci-slot ]

Step 3

This example begins an adapter firmware upgrade on the adapter in PCI slot 1:

Server# scope chassis

Server /chassis # update-adapter-fw 192.0.2.34 /ucs/adapters/adapter4.bin activate 1

Server /chassis #

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

130 OL-28893-01

Managing Network Adapters

Managing Adapter Firmware

What to Do Next

To activate the new firmware, see Activating Adapter Firmware, on page 131.

Activating Adapter Firmware

While the activation is in progress, do not:Important

•Reset, power off, or shut down the server.

•Reboot or reset CIMC.

•Activate any other firmware.

•Export technical support or configuration data.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Activates adapter firmware image 1 or 2 on the adapter

in the specified PCI slot.

Server /chassis # activate-adapter-fw

pci-slot {1|2}

Step 2

The changes will take effect upon the next

server reboot.

Note

This example activates adapter firmware image 2 on the adapter in PCI slot 1:

Server# scope chassis

Server /chassis # activate-adapter-fw 1 2

Firmware image activation suceeded

Please reset the server to run the activated image

Server /chassis #

What to Do Next

Reboot the server to apply the changes.

Resetting the Adapter

Before You Begin

You must log in with admin privileges to perform this task.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 131

Managing Network Adapters

Activating Adapter Firmware

Procedure

PurposeCommand or Action

Enters the chassis command mode.Server# scope chassis

Step 1

Resets the adapter at the PCI slot number specified by

the index argument.

Server/chassis # adapter-reset index

Step 2

Resetting the adapter also resets the

host.

Note

This example resets the adapter in PCI slot 1:

Server# scope chassis

Server /chassis # adapter-reset 1

This operation will reset the adapter and the host if it is on.

You may lose connectivity to the CIMC and may have to log in again.

Continue?[y|N] y

Server /chassis #

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

132 OL-28893-01

Managing Network Adapters

Resetting the Adapter

CHAPTER 10

Configuring Communication Services

This chapter includes the following sections:

•Configuring HTTP, page 133

•Configuring SSH, page 134

•Configuring XML API, page 135

•Configuring IPMI, page 136

•Configuring SNMP, page 137

Configuring HTTP

Before You Begin

You must log in as a user with admin privileges to configure HTTP.

Procedure

PurposeCommand or Action

Enters the HTTP command mode.Server# scope http

Step 1

Enables or disables HTTP and HTTPS service on the

CIMC.

Server /http # set enabled {yes |no}

Step 2

Sets the port to use for HTTP communication. The

default is 80.

Server /http # set http-port number

Step 3

Sets the port to use for HTTPS communication. The

default is 443.

Server /http # set https-port number

Step 4

Enables or disables the redirection of an HTTP request

to HTTPS.

Server /http # set http-redirect {yes

|no}

Step 5

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 133

PurposeCommand or Action

Sets the number of seconds to wait between HTTP

requests before the CIMC times out and terminates the

session.

Server /http # set timeout seconds

Step 6

Enter an integer between 60 and 10,800. The default is

1,800 seconds.

Commits the transaction to the system configuration.Server /http # commit

Step 7

This example configures HTTP for the CIMC:

Server# scope http

Server /http # set enabled yes

Server /http *# set http-port 80

Server /http *# set https-port 443

Server /http *# set http-redirect yes

Server /http *# set timeout 1800

Server /http *# commit

Server /http # show

HTTP Port HTTPS Port Timeout Active Sessions Enabled HTTP Redirected

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

80 443 1800 0 yes yes

Server /http #

Configuring SSH

Before You Begin

You must log in as a user with admin privileges to configure SSH.

Procedure

PurposeCommand or Action

Enters the SSH command mode.Server# scope ssh

Step 1

Enables or disables SSH on the CIMC.Server /ssh # set enabled {yes |no}

Step 2

Sets the port to use for secure shell access. The default

is 22.

Server /ssh # set ssh-port number

Step 3

Sets the number of seconds to wait before the system

considers an SSH request to have timed out.

Server /ssh # set timeout seconds

Step 4

Enter an integer between 60 and 10,800. The default

is 300 seconds.

Commits the transaction to the system configuration.Server /ssh # commit

Step 5

(Optional) Displays the SSH configuration.Server /ssh # show [detail]

Step 6

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

134 OL-28893-01

Configuring Communication Services

Configuring SSH

This example configures SSH for the CIMC:

Server# scope ssh

Server /ssh # set enabled yes

Server /ssh *# set ssh-port 22

Server /ssh *# set timeout 600

Server /ssh *# commit

Server /ssh # show

SSH Port Timeout Active Sessions Enabled

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

22 600 1 yes

Server /ssh #

Configuring XML API

XML API for CIMC

The Cisco CIMC XML application programming interface (API) is a programmatic interface to CIMC for a

C-Series Rack-Mount Server. The API accepts XML documents through HTTP or HTTPS.

For detailed information about the XML API, see Cisco UCS Rack-Mount Servers CIMC XML API

Programmer’s Guide.

Enabling XML API

Before You Begin

You must log in as a user with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters XML API command mode.Server# scope xmlapi

Step 1

Enables or disables XML API control of CIMC.Server /xmlapi # set enabled {yes |no}

Step 2

Commits the transaction to the system

configuration.

Server /xmlapi # commit

Step 3

This example enables XML API control of CIMC and commits the transaction:

Server# scope xmlapi

Server /xmlapi # set enabled yes

Server /xmlapi *# commit

Server /xmlapi # show detail

XMLAPI Settings:

Enabled: yes

Active Sessions: 0

Max Sessions: 4

Server /xmlapi #

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 135

Configuring Communication Services

Configuring XML API

Configuring IPMI

IPMI Over LAN

Intelligent Platform Management Interface (IPMI) defines the protocols for interfacing with a service processor

embedded in a server platform. This service processor is called a Baseboard Management Controller (BMC)

and resides on the server motherboard. The BMC links to a main processor and other on-board elements using

a simple serial bus.

During normal operations, IPMI lets a server operating system obtain information about system health and

control system hardware. For example, IPMI enables the monitoring of sensors, such as temperature, fan

speeds and voltages, for proactive problem detection. If server temperature rises above specified levels, the

server operating system can direct the BMC to increase fan speed or reduce processor speed to address the

problem.

Configuring IPMI over LAN

Configure IPMI over LAN when you want to manage the CIMC with IPMI messages.

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the IPMI command mode.Server# scope ipmi

Step 1

Enables or disables IPMI access on this server.Server /ipmi # set enabled

{yes |no}

Step 2

Specifies the highest privilege level that can be assigned to an IPMI

session on this server. This can be:

Server /ipmi # set

privilege-level {readonly |

user |admin}

Step 3

•readonly —IPMI users can view information but cannot

make any changes. If you select this option, IPMI users with

the "Administrator", "Operator", or "User" user roles can only

create read-only IPMI sessions, regardless of their other IPMI

privileges.

•user —IPMI users can perform some functions but cannot

perform administrative tasks. If you select this option, IPMI

users with the "Administrator" or "Operator" user role can

create user and read-only sessions on this server.

•admin —IPMI users can perform all available actions. If you

select this option, IPMI users with the "Administrator" user

role can create admin, user, and read-only sessions on this

server.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

136 OL-28893-01

Configuring Communication Services

Configuring IPMI

PurposeCommand or Action

Sets the IPMI encryption key to use for IPMI communications. The

key value must be 40 hexadecimal numbers.

Server /ipmi # set

encryption-key key

Step 4

Commits the transaction to the system configuration.Server /ipmi # commit

Step 5

This example configures IPMI over LAN for the CIMC:

Server# scope ipmi

Server /ipmi # set enabled yes

Server /ipmi *# set privilege-level admin

Server /ipmi *# set encryption-key abcdef01234567890abcdef01234567890abcdef

Server /ipmi *# commit

Server /ipmi # show

Enabled Encryption Key Privilege Level Limit

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

yes abcdef01234567890abcdef01234567890abcdef admin

Server /ipmi #

Configuring SNMP

SNMP

The Cisco UCS C-Series Rack-Mount Servers support the Simple Network Management Protocol (SNMP)

for viewing server configuration and status and for sending fault and alert information by SNMP traps. For

information on Management Information Base (MIB) files supported by CIMC, see the MIB Quick Reference

for Cisco UCS at this URL: http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/mib/reference/UCS_

MIBRef.html.

Configuring SNMP Properties

Before You Begin

You must log in as a user with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters SNMP command mode.Server# scope snmp

Step 1

Enables or disables SNMP.Server /snmp # set enabled {yes

|no}

Step 2

SNMP must be enabled and saved before additional

SNMP configuration commands are accepted.

Note

Commits the transaction to the system configuration.Server /snmp # commit

Step 3

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 137

Configuring Communication Services

Configuring SNMP

PurposeCommand or Action

Specifies the default SNMP v1 or v2c community name that

CIMC includes on any trap messages it sends to the SNMP

host. The name can be up to 18 characters.

Server /snmp # set

community-str community

Step 4

This can be one of the following : Disabled, Limited, or Full.Server /snmp #

setcommunity-access

Step 5

Specifies the SNMP community group to which trap

information should be sent. The name can be up to 18

characters

Server /snmp #

settrap-community-str

Step 6

Specifies the system contact person responsible for the SNMP

implementation. The contact information can be up to 254

Server /snmp # set sys-contact

contact

Step 7

characters, such as an email address or a name and telephone

number. To enter a value that contains spaces, you must

enclose the entry with quotation marks.

Specifies the location of the host on which the SNMP agent

(server) runs. The location information can be up to 254

Server /snmp # set sys-location

location

Step 8

characters. To enter a value that contains spaces, you must

enclose the entry with quotation marks.

Commits the transaction to the system configuration.Server /snmp # commit

Step 9

This example configures the SNMP properties and commits the transaction:

Server# scope snmp

Server /snmp # set enabled yes

Server /snmp *# commit

Server /snmp # set community-str cimcpublic

Server /snmp # set community-access Full

Server /snmp # set trap-community-str public

Server /snmp *# set sys-contact "User Name <username@example.com> +1-408-555-1212"

Server /snmp *# set sys-location "San Jose, California"

Server /snmp *# commit

Server /snmp # show detail

SNMP Settings:

SNMP Port: 161

System Contact: User Name <username@example.com> +1-408-555-1212

System Location: San Jose, California

SNMP Community: cimcpublic

SNMP Trap community: public

SNMP Community access: Full

Enabled: yes

Server /snmp #

What to Do Next

Configure SNMP trap settings as described in Configuring SNMP Trap Settings, on page 139.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

138 OL-28893-01

Configuring Communication Services

Configuring SNMP Properties

Configuring SNMP Trap Settings

Before You Begin

•You must log in with admin privileges to perform this task.

•SNMP must be enabled and saved before trap settings can be configured.

Procedure

PurposeCommand or Action

Enters the SNMP command mode.Server# scope snmp

Step 1

Enters the SNMP trap destination command mode for

the specified destination. Four SNMP trap destinations

Server /snmp # scope

trap-destinations number

Step 2

are available. The destination number is an integer

between 1 and 15.

Enables or disables the SNMP trap destination.Server /snmp/trap-destinations # set

enabled {yes |no}

Step 3

Specify the desired SNMP version of the trap message.Server /snmp/trap-destinations # set

version {1|2|3}

Step 4

SNMPv3 traps will be delivered only to

locations where the SNMPv3 user and key

values are configured correctly.

Note

Specifies whether SNMP notification messages are

sent as simple traps or as inform requests requiring

acknowledgment by the receiver.

Server /snmp/trap-destinations # set

type {trap |inform}

Step 5

The inform option can be chosen only for V2

users.

Note

Server /snmp/trap-destinations # set

user user

Step 6

Specifies the destination IP address to which SNMP

trap information is sent.

Server /snmp/trap-destination # set

v4-addr ip-address

Step 7

Commits the transaction to the system configuration.Server /snmp/trap-destination #

commit

Step 8

This example configures general SNMP trap settings and trap destination number 1 and commits the transaction:

Server# scope snmp

Server /snmp # Scope trap-destinations 1

Server /snmp/trap-destination *# set enabled yes

Server /snmp/trap-destination *# set version 2

Server /snmp/trap-destination *# set type inform

Server /snmp/trap-destination *# set user user1

Server /snmp/trap-destination *# set v4-addr 192.2.3.4

Server /snmp/trap-destination *# commit

Server /snmp/trap-destination # show detail

Trap Destination 1:

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 139

Configuring Communication Services

Configuring SNMP Trap Settings

Enabled: yes

SNMP version: 2

Trap type: inform

SNMP user: user1

IPv4 Address: 192.2.3.4

Delete Trap: no

Server /snmp/trap-destination #

Sending a Test SNMP Trap Message

Before You Begin

You must log in with admin privileges to perform this task.

Procedure

PurposeCommand or Action

Enters the SNMP command mode.Server# scope snmp

Step 1

Sends an SNMP test trap to the configured SNMP trap

destination that are enabled.

Server /snmp # sendSNMPtrap

Step 2

The trap must be configured and enabled in order

to send a test message.

Note

This example sends a test message to all the enabled SNMP trap destinations:

Server# scope snmp

Server /snmp # sendSNMPtrap

SNMP Test Trap sent to the destination.

Server /snmp #

Configuring SNMPv3 Users

Before You Begin

•You must log in as a user with admin privileges to perform this task.

•SNMP must be enabled and saved before these configuration commands are accepted.

Procedure

PurposeCommand or Action

Enters the SNMP command mode.Server# scope snmp

Step 1

Enters the SNMPv3 users command mode for the

specified user number.

Server /snmp # scope v3users

number

Step 2

Adds or deletes an SNMPv3 user. This can be one of the

following:

Server /snmp/v3users # set v3add

{yes |no}

Step 3

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

140 OL-28893-01

Configuring Communication Services

Sending a Test SNMP Trap Message

PurposeCommand or Action

•yes—This user is enabled as an SNMPv3 user and

is allowed to access the SNMP OID tree.

The security name and security level must

also be configured at this time or the user

addition will fail.

Note

•no—This user configuration is deleted.

Enter an SNMP username for this user.Server /snmp/v3users # set

v3security-name security-name

Step 4

Select a security level for this user. This can be one of the

following:

Server /snmp/v3users # set

v3security-level {noauthnopriv |

authnopriv |authpriv}

Step 5

•noauthnopriv—The user does not require an

authorization or privacy password.

•authnopriv—The user requires an authorization

password but not a privacy password. If you select

this option, you must configure an authentication

key.

•authpriv—The user requires both an authorization

password and a privacy password. If you select this

option, you must configure an authentication key

and a private encryption key.

Select an authentication protocol for this user.Server /snmp/v3users # set v3proto

{MD5 |SHA}

Step 6

Enter an authorization password for this user.Server /snmp/v3users # set

v3auth-key auth-key

Step 7

Select an encryption protocol for this user.Server /snmp/v3users # set

v3priv-proto {DES |AES}

Step 8

Enter a private encryption key (privacy password) for this

user.

Server /snmp/v3users # set

v3priv-auth-key priv-auth-key

Step 9

Commits the transaction to the system configuration.Server /snmp/v3users # commit

Step 10

This example configures SNMPv3 user number 2 and commits the transaction:

Server# scope snmp

Server /snmp # scope v3users 2

Server /snmp/v3users # set v3add yes

Server /snmp/v3users *# set v3security-name ucsSNMPV3user

Server /snmp/v3users *# set v3security-level authpriv

Server /snmp/v3users *# set v3proto SHA

Server /snmp/v3users *# set v3auth-key

Please enter v3auth-key:ex4mp1ek3y

Please confirm v3auth-key:ex4mp1ek3y

Server /snmp/v3users *# set v3priv-proto AES

Server /snmp/v3users *# set v3priv-auth-key

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 141

Configuring Communication Services

Configuring SNMPv3 Users

Please enter v3priv-auth-key:!1@2#3$4%5^6&7*8

Please confirm v3priv-auth-key:!1@2#3$4%5^6&7*8

Server /snmp/v3users *# commit

Settings are being applied ... allow a few minutes for the process to complete

Server /snmp/v3users # show detail

User 2:

Add User: yes

Security Name: ucsSNMPV3user

Security Level: authpriv

Auth Type: SHA

Auth Key: ******

Encryption: AES

Private Key: ******

Server /snmp/v3users #

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

142 OL-28893-01

Configuring Communication Services

Configuring SNMPv3 Users

CHAPTER 11

Managing Certificates

This chapter includes the following sections:

•Managing the Server Certificate, page 143

•Generating a Certificate Signing Request, page 143

•Creating a Self-Signed Certificate, page 145

•Uploading a Server Certificate, page 147

Managing the Server Certificate

You can generate a certificate signing request (CSR) to obtain a new certificate, and you can upload the new

certificate to the CIMC to replace the current server certificate. The server certificate may be signed either

by a public Certificate Authority (CA), such as Verisign, or by your own certificate authority.

Procedure

Step 1 Generate the CSR from the CIMC.

Step 2 Submit the CSR file to a certificate authority that will issue and sign your certificate. If your organization

generates its own self-signed certificates, you can use the CSR file to generate a self-signed certificate.

Step 3 Upload the new certificate to the CIMC.

The uploaded certificate must be created from a CSR generated by the CIMC. Do not upload a

certificate that was not created by this method.

Note

Generating a Certificate Signing Request

Before You Begin

You must log in as a user with admin privileges to configure certificates.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 143

Procedure

PurposeCommand or Action

Enters the certificate command mode.Server# scope certificate

Step 1

Launches a dialog for the generation of a certificate

signing request (CSR).

Server /certificate # generate-csr

Step 2

You will be prompted to enter the following information for the certificate signing request:

The fully qualified hostname of the CIMC.Common Name (CN)

The organization requesting the certificate.Organization Name (O)

The organizational unit.Organization Unit (OU)

The city or town in which the company requesting

the certificate is headquartered.

Locality (L)

The state or province in which the company

requesting the certificate is headquartered.

StateName (S)

The two-letter ISO country code for the country in

which the company is headquartered.

Country Code (CC)

The administrative email contact at the company.Email

After you have entered the requested information, the system will generate and display a certificate signing

request in the console output. A CSR file will not be created, but you can copy the CSR information from the

console output and paste the information into a text file.

This example generates a certificate signing request:

Server# scope certificate

Server /certificate # generate-csr

Common Name (CN): test.example.com

Organization Name (O): Example, Inc.

Organization Unit (OU): Test Department

Locality (L): San Jose

StateName (S): CA

Country Code (CC): US

Email: user@example.com

Continue to generate CSR?[y|N]y

-----BEGIN CERTIFICATE REQUEST-----

MIIB/zCCAWgCAQAwgZkxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTEVMBMGA1UE

BxMMU2FuIEpvc2UsIENBMRUwEwYDVQQKEwxFeGFtcGxlIEluYy4xEzARBgNVBAsT

ClRlc3QgR3JvdXAxGTAXBgNVBAMTEHRlc3QuZXhhbXBsZS5jb20xHzAdBgkqhkiG

9w0BCQEWEHVzZXJAZXhhbXBsZS5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJ

AoGBAMZw4nTepNIDhVzb0j7Z2Je4xAG56zmSHRMQeOGHemdh66u2/XAoLx7YCcYU

ZgAMivyCsKgb/6CjQtsofvzxmC/eAehuK3/SINv7wd6Vv2pBt6ZpXgD4VBNKONDl

GMbkPayVlQjbG4MD2dx2+H8EH3LMtdZrgKvPxPTE+bF5wZVNAgMBAAGgJTAjBgkq

hkiG9w0BCQcxFhMUQSBjaGFsbGVuZ2UgcGFzc3dvcmQwDQYJKoZIhvcNAQEFBQAD

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

144 OL-28893-01

Managing Certificates

Generating a Certificate Signing Request

gYEAG61CaJoJaVMhzCl903O6Mg51zq1zXcz75+VFj2I6rH9asckCld3mkOVx5gJU

Ptt5CVQpNgNLdvbDPSsXretysOhqHmp9+CLv8FDuy1CDYfuaLtvlWvfhevskV0j6

mK3Ku+YiORnv6DhxrOoqau8r/hyI/L43l7IPN1HhOi3oha4=

-----END CERTIFICATE REQUEST-----

Copy everything from "-----BEGIN ..." to "END CERTIFICATE REQUEST-----",

paste to a file, send to your chosen CA for signing,

and finally upload the signed certificate via upload command.

---OR---

Continue to self sign CSR and overwrite the current certificate?

All HTTPS and SSH sessions will be disconnected. [y|N]N

What to Do Next

Perform one of the following tasks:

•If you do not want to obtain a certificate from a public certificate authority, and if your organization

does not operate its own certificate authority, you can allow CIMC to internally generate a self-signed

certificate from the CSR and upload it immediately to the server. Type yafter the final prompt in the

example to perform this action.

•If your organization operates its own certificate server for generating self-signed certificates, copy the

command output from "-----BEGIN ..." to "END CERTIFICATE REQUEST-----" and paste to a file

named csr.txt. Input the CSR file to your certificate server to generate a self-signed certificate.

•If you will obtain a certificate from a public certificate authority, copy the command output from

"-----BEGIN ..." to "END CERTIFICATE REQUEST-----" and paste to a file named csr.txt. Submit the

CSR file to the certificate authority to obtain a signed certificate.

If you did not use the first option, in which CIMC internally generates and uploads a self-signed certificate,

you must upload the new certificate using the upload command in certificate command mode.

Creating a Self-Signed Certificate

As an alternative to using a public Certificate Authority (CA) to generate and sign a server certificate, you

can operate your own CA and sign your own certificates. This section shows commands for creating a CA

and generating a server certificate using the OpenSSL certificate server running on Linux. For detailed

information about OpenSSL, see http://www.openssl.org.

These commands are to be entered on a Linux server with the OpenSSL package, not in the CIMC CLI.Note

Before You Begin

Obtain and install a certificate server software package on a server within your organization.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 145

Managing Certificates

Creating a Self-Signed Certificate

Procedure

PurposeCommand or Action

This command generates an RSA private key that will

be used by the CA.

To allow the CA to access the key without user

input, do not use the -des3 option for this

command.

Note

openssl genrsa -out CA_keyfilename

keysize

Example:

# openssl genrsa -out ca.key 1024

Step 1

The specified file name contains an RSA key of the

specified key size.

This command generates a new self-signed certificate

for the CA using the specified key. The certificate is

openssl req -new -x509 -days numdays

-key CA_keyfilename -out CA_certfilename

Step 2

valid for the specified period. The command prompts

the user for additional certificate information.

Example:

# openssl req -new -x509 -days 365

-key ca.key -out ca.crt The certificate server is an active CA.

This command adds a line to the OpenSSL configuration

file to designate the certificate as a server-only

echo "nsCertType = server" >

openssl.conf

Step 3

certificate. This designation is a defense against a

Example:

# echo "nsCertType = server" >

openssl.conf

man-in-the-middle attack, in which an authorized client

attempts to impersonate the server.

The OpenSSL configuration file openssl.conf contains

the statement "nsCertType = server".

This command directs the CA to use your CSR file to

generate a server certificate.

openssl x509 -req -days numdays -in

CSR_filename -CA CA_certfilename

Step 4

-set_serial 04 -CAkey CA_keyfilename -out

server_certfilename -extfile openssl.conf Your server certificate is contained in the output file.

Example:

# openssl x509 -req -days 365 -in

csr.txt -CA ca.crt -set_serial 04

-CAkey ca.key -out myserver05.crt

-extfile openssl.conf

This example shows how to create a CA and to generate a server certificate signed by the new CA. These

commands are entered on a Linux server running OpenSSL.

#/usr/bin/openssl genrsa -out ca.key 1024

Generating RSA private key, 1024 bit long modulus

.............++++++

.....++++++

e is 65537 (0x10001)

#/usr/bin/openssl req -new -x509 -days 365 -key ca.key -out ca.crt

You are about to be asked to enter information that will be incorporated

into your certificate request.

What you are about to enter is what is called a Distinguished Name or a

DN.

There are quite a few fields but you can leave some blank

For some fields there will be a default value,

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

146 OL-28893-01

Managing Certificates

Creating a Self-Signed Certificate

If you enter '.', the field will be left blank.

-----

Country Name (2 letter code) [GB]:US

State or Province Name (full name) [Berkshire]:California

Locality Name (eg, city) [Newbury]:San Jose

Organization Name (eg, company) [My Company Ltd]:Example Incorporated

Organizational Unit Name (eg, section) []:Unit A

Common Name (eg, your name or your server's hostname) []:example.com

Email Address []:admin@example.com

#echo "nsCertType = server" > openssl.conf

#/usr/bin/openssl x509 -req -days 365 -in csr.txt -CA ca.crt -set_serial 01 -CAkey ca.key -out server.crt

-extfile openssl.conf

Signature ok

subject=/C=US/ST=California/L=San Jose/O=Example Inc./OU=Unit

A/CN=example.com/emailAddress=john@example.com

Getting CA Private Key

What to Do Next

Upload the new certificate to the CIMC.

Uploading a Server Certificate

Before You Begin

You must log in as a user with admin privileges to upload a certificate.

The certificate to be uploaded must be available as readable text. During the upload procedure, you will copy

the certificate text and paste it into the CLI.

You must first generate a CSR using the CIMC certificate management CSR generation procedure, and

you must use that CSR to obtain the certificate for uploading. Do not upload a certificate that was not

obtained by this method.

Note

All current HTTPS and SSH sessions are disconnected when the new server certificate is uploaded.Note

Procedure

PurposeCommand or Action

Enters the certificate command mode.Server# scope certificate

Step 1

Launches a dialog for entering and uploading the

new server certificate.

Server /certificate # upload

Step 2

Copy the certificate text, paste it into the console when prompted, and type CTRL+D to upload the certificate.

Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5

OL-28893-01 147

Managing Certificates

Uploading a Server Certificate

This example uploads a new certificate to the server:

Server# scope certificate

Server /certificate # upload

Please paste your certificate here, when finished, press CTRL+D.

-----BEGIN CERTIFICATE-----