Getting Started Guide for Cisco UCS E-Series Servers, Release 2.x

Getting Started Guide for Cisco UCS E-Series Servers, Release 2.x

First Published: August 09, 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-29450-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 of the UNIX operating system. All rights reserved. Copyright

©

1981, Regents of the University of California.

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

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

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

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

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

HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

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

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

. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

©

2013 Cisco Systems, Inc. All rights reserved.

C O N T E N T S

P r e f a c e

C H A P T E R 1

C H A P T E R 2

C H A P T E R 3

OL-29450-01

Preface ix

Audience

ix

Organization

ix

Conventions

xi

Related Documentation

xii

New and Changed Information

xii

Documentation Feedback

xiii

Configuration Quick Reference

1

Configuration Quick Reference Tasks

2

Cisco UCS E-Series Servers Overview 5

Cisco UCS E-Series Servers Overview

5

Server Software

6

Managing E-Series Servers

7

E-Series Server Options

8

Basic Workflow for Option 1—E-Series Server without a Preinstalled Operating System or

Hypervisor

10

Basic Workflow for Option 2—E-Series Server with a Preinstalled Microsoft Windows

Server

11

Basic Workflow for Option 3—E-Series Server with a Preinstalled VMware vSphere

Hypervisor

12

Common Terms Used in This Guide

13

Installing the E-Series Server into the Router 15

Basic Workflow for Installing the E-Series Server into the Router

15

Verifying the Router, E-Series Server, and Cisco IOS Software Version Compatibility

15

Getting Started Guide for Cisco UCS E-Series Servers, Release 2.x iii

Contents

C H A P T E R 4

C H A P T E R 5

Installing the E-Series Server into the Router

16

Stopping the E-Series Server from Resetting and Updating the CIMC Firmware

18

Verifying E-Series Server Installation

19

Configuration Differences

21

Router Configuration Differences Between the Cisco SRE-V and the E-Series Server—ISR

G2

21

Router Configuration Differences Between the ISR G2 and the Cisco ISR 4451-X

22

VMware vSphere Hypervisor Configuration Differences

23

Configuring CIMC Access 25

Configuring CIMC Access - ISR G2

26

E-Series Server Interfaces Overview—ISR G2

26

CIMC Access Configuration Options—ISR G2

27

Configuring CIMC Access Using the E-Series Server's External Management (Dedicated)

Interface—ISR G2

28

Configuring CIMC Access Using Shared LOM—ISR G2

29

Configuring CIMC Access Using the Router's Internal PCIe Slot/0 Console

Interface—ISR G2

30

Configuring CIMC Access Using the Router's Internal MGF Slot/1 VLAN

Interface—ISR G2

33

Configuring CIMC Access Using the E-Series Server's External GE2 or GE3

Interface—ISR G2

35

Configuring CIMC Access - Cisco ISR 4451-X

37

E-Series Server Interfaces Overview—Cisco ISR 4451-X

37

CIMC Access Configuration Options—Cisco ISR 4451-X

38

Configuring CIMC Access Using the E-Series Server's External Management (Dedicated)

Interface—Cisco ISR 4451-X

39

Configuring CIMC Access Using the E-Series Server's NIC Interfaces—Cisco ISR

4451-X

41

Configuring CIMC Access Using the E-Series Server's Internal GE0 Interface and the Cisco ISR 4451-X ucse slot/0/0 Interface

41

Configuring CIMC Access Using the E-Series Server's Internal GE1 Interface and the Cisco ISR 4451-X ucse slot/0/1 Interface

45

iv


OL-29450-01

Contents

C H A P T E R 6

C H A P T E R 7

C H A P T E R 8

OL-29450-01

Configuring CIMC Access Using the E-Series Server's External GE2 or GE3

Interface—Cisco ISR 4451-X

48

Configuring CIMC Access Using the CIMC Configuration Utility

51

Defining Network Static Settings Using a Script File

53

Accessing CIMC 55

CIMC Overview

55

CIMC GUI

56

CIMC CLI

56

Logging In to the CIMC GUI

56

CIMC Home Page

57

Accessing the Microsoft Windows Server from CIMC

58

Accessing the VMware vSphere Hypervisor from CIMC

58

What to Do Next

59

Managing RAID

61

RAID Options

61

Configuring RAID

65

Configuring RAID Using the CIMC GUI

65

Configuring RAID Using the WebBIOS

68

What to Do Next

69

Installing the Operating System or Hypervisor

71

Operating System or Hypervisor Installation Methods

71

KVM Console

72

Installing an Operating System or Hypervisor Using the KVM Console

72

PXE Installation Servers

74

Installing an Operating System or Hypervisor Using a PXE Installation Server

74

Host Image Mapping

74

Mapping the Host Image

75

Installing Drivers for the Microsoft Windows Server

77

Unmapping the Host Image

78

Basic Workflow for Downloading and Installing the VMware vSphere Hypervisor

79

Downloading the Customized VMware vSphere Hypervisor Image

79

Assigning a Static IP Address to the VMware vSphere Hypervisor

79

Getting Started Guide for Cisco UCS E-Series Servers, Release 2.x v

Contents

C H A P T E R 9

C H A P T E R 1 0

C H A P T E R 1 1

Downloading and Installing the vSphere Client

81

Configuring the Server Boot Order

81

Configuring the Server Boot Order Using the CIMC GUI

81

Configuring the Boot Order Using the BIOS Setup Menu

85

Configuring a Connection Between the Router and the E-Series Server

87

Configuring an Internal Connection Between the ISR G2 and the E-Series Server

87

Configuring an Internal Connection Between the Cisco ISR 4451-X and the E-Series

Server

90

Creating an Ethernet Virtual Circuit Using the Native VLAN Between the E-Series Server and the Cisco ISR 4451-X

93

Creating an Ethernet Virtual Circuit Using a Non-Native VLAN Between the E-Series

Server and the Cisco ISR 4451-X

94

Understanding Network Interface Mapping

96

Determining the MAC Address in Microsoft Windows, Linux, and VMware vSphere Hypervisor

98

BIOS 101

BIOS Overview

101

Determining the Current BIOS Version

102

Options for Obtaining Firmware from Cisco Systems

102

Obtaining Software from Cisco Systems

102

Installing the BIOS Firmware

103

Installing the BIOS Firmware Through the Browser

103

Installing the BIOS Firmware from a TFTP Server

105

Accessing the BIOS Setup Menu

106

Accessing the BIOS Setup Menu from the KVM Console

106

Changing Configuration Using the BIOS Setup Menu

109

Recovering from Corrupt CIMC Firmware 111

CIMC Firmware Image Overview

111

Recovering from a Corrupted CIMC Firmware Image

111

Recovering from a Faulty SD Card

113

Recovering from a Corrupted File System

115

vi


OL-29450-01

Contents

C H A P T E R 1 2

C H A P T E R 1 3

C H A P T E R 1 4

Diagnostic Tests 119

Diagnostic Tests Overview

119

Mapping the Diagnostics Image to the Host

120

Running Diagnostic Tests

122

Cisco IOS Software Command Reference—ISR G2

125

imc ip address default-gateway

125

imc ip address dhcp

126

imc vlan

127

ucse cmos-reset

128

ucse password-reset

128

ucse session

129

ucse shutdown

130

ucse statistics

130

ucse status

131

ucse stop

132

Cisco IOS Software Command Reference—Cisco ISR 4451-X

133

debug platform software ucse

133

hw-module subslot session

134

imc ip dhcp

135

show interfaces ucse

136

ucse subslot imc password-reset

138

ucse subslot server

138

ucse subslot server password-reset

140

ucse subslot shutdown

141

ucse subslot statistics

141

ucse subslot status

142

OL-29450-01

Getting Started Guide for Cisco UCS E-Series Servers, Release 2.x vii

Contents viii


OL-29450-01

Preface

This preface includes the following sections:

•

Audience, page ix

•

Organization, page ix

•

Conventions, page xi

•

Related Documentation, page xii

•

New and Changed Information, page xii

•

Documentation Feedback, page xiii

Audience

This guide is intended primarily for data center administrators with responsibilities and expertise in one or more of the following:

• Server administration

• Storage administration

• Network administration

• Network security

Organization

This document includes the following chapters:

Chapter

Chapter 1

Title

Configuration Quick

Reference

Description

Provides a list of commands and steps to quickly setup and use the E-Series Server.

Chapter 2 Cisco UCS E-Series

Servers Overview

Provides an overview of the E-Series Server, hardware and software requirements, and E-Series Server options.

Getting Started Guide for Cisco UCS E-Series Servers, Release 2.x ix OL-29450-01

Organization

Preface

Chapter

Chapter 3

Chapter 4

Chapter 5

Chapter 6

Chapter 7

Chapter 8

Chapter 9

Chapter 10

Chapter 11

Chapter 12

Chapter 13

Chapter 14

Title Description

Installing the E-Series

Server into the Router

Describes how to install the E-Series Server into the router.

Configuration

Differences

Provides configuration differences between the Cisco SRE-V and the E-Series Server and between ISR G2 and the Cisco ISR

4451-X.

Configuring CIMC

Access

Accessing CIMC

Provides options to configure CIMC access.

Managing RAID

Provides an overview of CIMC and describes how to log into

CIMC.

Describes RAID options and how to configure RAID.

Installing the Operating

System

Describes how to install an operating system.

Configuring a

Connection Between the Router and the

E-Series Server

Describes how to configure a connection between the router and the E-Series Server.

BIOS Provides an overview of BIOS, how to install the BIOS firmware, and how to access the BIOS setup menu.

Describes how to recover from corrupt CIMC firmware.

Recovering from

Corrupt CIMC

Firmware

Diagnostic Tests

Cisco IOS Software

Command

Reference—ISR G2

Describes how to run diagnostic tests.

Provides a list of Cisco IOS commands used to configure the ISR

G2 and the E-Series Server.

Cisco IOS Software

Command

Reference—Cisco ISR

4451-X

Provides a list of Cisco IOS commands used to configure the

Cisco ISR 4451-X and the E-Series Server.

x


OL-29450-01

Preface

Conventions

Conventions

Text Type

GUI elements

User input

Document titles

System output

CLI commands

[ ]

{x | y | z}

[x | y | z] string

< >

[ ]

!, #

Indication

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

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

Text the user should enter exactly as shown or keys a user should press appear in this font.

Document titles appear in this font.

Terminal sessions and information that the system displays appear in this font

.

CLI command keywords appear in this font.

Variables in a CLI command appear in this font.

Elements in square brackets are optional.

Required alternative keywords are grouped in braces and separated by vertical bars.

Optional alternative keywords are grouped in brackets and separated by vertical bars.

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

Nonprinting characters such as passwords are in angle brackets.

Default responses to system prompts are in square brackets.

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

Note

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

Tip

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

Getting Started Guide for Cisco UCS E-Series Servers, Release 2.x xi OL-29450-01

Preface

Related Documentation

Caution

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

Timesaver

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

Warning

IMPORTANT SAFETY INSTRUCTIONS

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

SAVE THESE INSTRUCTIONS

Related Documentation

The http://www.cisco.com/en/US/docs/unified_computing/ucs/e/1.0/roadmap/e_series_road_map.html

provides links to all E-Series Server documentation:

• Release Notes for Cisco UCS E-Series Servers

• Getting Started Guide for Cisco UCS E-Series Servers

• Hardware Installation Guide for Cisco UCS E-Series Servers

• Cisco Network Modules, Server Modules, and Interface Cards Regulatory Compliance and Safety

Information

• Host Upgrade Utility Guide for Cisco UCS E-Series Servers

• GUI Configuration Guide for Cisco UCS E-Series Servers Integrated Management Controller

• CLI Configuration Guide for Cisco UCS E-Series Servers Integrated Management Controller

• CIMC XML API Programmer’s Guide for Cisco UCS E-Series Servers

• Troubleshooting Guide for Cisco UCS E-Series Servers

• Open Source Used in Cisco UCS E-Series Servers

New and Changed Information

The following table provides an overview of the significant changes to this guide for the current release:

xii


OL-29450-01

Preface

Documentation Feedback

Table 1: New Features and Significant Changes in the Getting Started Guide for Cisco UCS E-Series Servers, Release 2.0

Feature

Combined Getting Started Guide

Configuring CIMC Access

Description Where Documented

One Getting Started Guide for all the platforms that the E-Series Server supports—Cisco 2900 and 3900 Integrated

Services Routers (ISR G2) and the Cisco

4451-X Integrated Services Router (Cisco

ISR 4451-X).

This guide.

Provides the following information:

• Configuring CIMC Access—ISR G2

• Configuring CIMC Access—Cisco

ISR 4451-X

Configuring CIMC Access, on page 25

Configuring a Connection Between the

Router and the E-Series Server

Provides the following information:

• Configuring an Internal Connection

Between the ISR G2 and the E-Series

Server

Configuring a Connection Between the

Router and the E-Series Server, on page

87

• Configuring an Internal Connection

Between the Cisco ISR 4451-X and the E-Series Server

RAID


Host Image Mapping

Enhanced RAID feature.

Mapping the Diagnostics Image to the Host Enhanced Diagnostics Image Mapping feature.

Managing RAID, on page 61

Support added for booting the server from specific devices within a device category.

Installing the Operating System or

Hypervisor, on page 71

Enhanced Host Image Mapping feature.

Installing the Operating System or

Hypervisor, on page 71

Diagnostic Tests, on page 119


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

Getting Started Guide for Cisco UCS E-Series Servers, Release 2.x xiii OL-29450-01


Preface xiv


OL-29450-01

C H A P T E R

1


Use this configuration quick reference chapter if you just need a list of commands and steps to quickly set up and use the Cisco UCS E-Series Server (E-Series Server). Detailed information about each of the configuration steps is provided in subsequent chapters.

Note

Use this configuration quick reference chapter if you purchased Option 1 (E-Series Server without preinstalled operating system or hypervisor). Some of the configuration steps are different if you purchased

Option 2 (E-Series Server with preinstalled Microsoft Windows Server), or Option 3 (E-Series Server with preinstalled VMware vSphere Hypervisor

™

).

This chapter includes the following sections:

•

Configuration Quick Reference Tasks, page 2

OL-29450-01


1


Configuration Quick Reference Tasks


The following figure shows the basic workflow for Option 1—E-Series Server without preinstalled operating system or hypervisor.

Figure 1: Basic Workflow—Option 1

Procedure

Step 1

Install the E-Series Server into the router.

Step 2

Configure the CIMC IP address for CIMC access. Use one of the following methods:

2


OL-29450-01



• If you are a remote user, use the Cisco IOS CLI to configure CIMC access. Enter the following commands:

Note

Note

This configuration shows you how to configure CIMC access using the E-Series Server’s Console interface (shared LOM). For details, see

Configuring CIMC Access Using the Router's Internal

PCIe Slot/0 Console Interface—ISR G2, on page 30

.

To use another interface, see

Configuring CIMC Access, on page

25 .

◦enable

◦configure terminal

◦interface ucse slot/port

◦imc ip address cimc-ip-address subnet-mask default-gateway cimc-gateway-ip-address

◦imc access-port shared-lom console

◦no shut

◦end

• If you are a local user, use one of the following methods:

◦Connect a keyboard and monitor to the front panel of the E-Series Server, and then use the CIMC

Configuration Utility to configure CIMC access. See

Configuring CIMC Access Using the CIMC

Configuration Utility, on page 51

.

◦Use the Cisco IOS CLI to configure CIMC access (see the configuration for a remote user above).

Step 3

In your web browser, enter the IP address that you configured in Step 2 to access CIMC.

Step 4

Configure RAID and make the disk drive bootable. See


.

Step 5

Install the operating system or Hypervisor and if needed, install drivers. See

Installing the Operating System or Hypervisor, on page 71

.

Step 6

Do one of the following:

• If you do not want the traffic to your application or operating system to flow through the router, use the server’s host operating system to configure the E-Series Server’s external GE2 or GE3 interface.

• If you want the traffic to your application or operating system to flow through the router, use the Cisco

IOS CLI to configure an internal connection between the router and the E-Series Server. See

Configuring a Connection Between the Router and the E-Series Server, on page 87

.

OL-29450-01


3



4


OL-29450-01

C H A P T E R

2

Cisco UCS E-Series Servers Overview


•

Cisco UCS E-Series Servers Overview, page 5

•

Server Software, page 6

•

Managing E-Series Servers, page 7

•

E-Series Server Options, page 8

•

Common Terms Used in This Guide, page 13


The Cisco UCS E-Series Servers (E-Series Servers) are the next generation of Cisco UCS Express servers.

E-Series Servers are a family of size, weight, and power-efficient blade servers that are housed within the

Generation 2 Cisco Integrated Services Routers (ISR G2) and the Cisco 4451-X Integrated Services Router

(Cisco ISR 4451-X). These servers provide a general purpose compute platform for branch-office applications deployed either as bare-metal on operating systems, such as Microsoft Windows or Linux, or as virtual machines on hypervisors, such as VMware vSphere Hypervisor

™

, Microsoft Hyper-V, or Citrix XenServer.

OL-29450-01


5

Server Software


The following figure shows an example of an E-Series Server Hypervisor deployment.

Figure 2: Example of an E-Series Server Hypervisor Deployment

1

2

3

Client Devices 4

E-Series Server Management Console

Cisco ISR G2 Router with E-Series Server running a Hypervisor or Bare-Metal Operating

System

5

Virtual Machines Hosted on the E-Series

Server (applicable only if Hypervisor is running on the E-Series Server)

Enterprise Storage Device

Note

For information about the supported E-Series Servers and the maximum number of E-Series Servers that can be installed per ISR, see the "Hardware Requirements" section in the Release Notes for Cisco UCS

E-Series Servers.

Server Software

E-Series Servers require three major software systems:

• CIMC Firmware

• BIOS Firmware

• Operating System or Hypervisor

6


OL-29450-01


Managing E-Series Servers

The following figure shows how the software interacts with the E-Series Server.

Figure 3: Server Software

CIMC Firmware

Cisco Integrated Management Controller (CIMC) is a separate management module built into the motherboard of the E-Series Server. A dedicated ARM-based processor, separate from the main server CPU, runs the CIMC firmware. The system ships with a running version of the CIMC firmware. You can update the CIMC firmware, but no initial installation is needed.

CIMC is the management service for the E-Series Servers. You can use a web-based GUI or SSH-based CLI to access, configure, administer, and monitor the server.

BIOS Firmware

BIOS initializes the hardware in the system, discovers bootable devices, and boots them in the provided sequence. It boots the operating system and configures the hardware for the operating system to use. BIOS manageability features allow you to interact with the hardware and use it. In addition, BIOS provides options to configure the system, manage firmware, and create BIOS error reports.

The system ships with a running version of the BIOS firmware. You can update the BIOS firmware, but no initial installation is needed.

Operating System or Hypervisor

The main server CPU runs on an operating system, such as Microsoft Windows or Linux; or on a Hypervisor.

You can purchase an E-Series Server with pre-installed Microsoft Windows Server or VMware vSphere

Hypervisor

™

, or you can install your own platform.

Note

For information about the platforms that have been tested on the E-Series Servers, see the "Software

Requirements" section in the Release Notes for Cisco UCS E-Series Servers.

Managing E-Series Servers

The following table lists the management interfaces used by the E-Series Server.


7 OL-29450-01


E-Series Server Options

Table 2: E-Series Server Management Interfaces

Management Interface

Cisco IOS CLI

CIMC GUI

CIMC CLI

SNMP

Description

Configures the host router and the E-Series Server.

Web-based GUI used to access, configure, administer, and monitor the E-Series Server.

SSH-based CLI used to access, configure, administer, and monitor the E-Series Server.

Allows you to view server configuration and status, and send fault and alert information through Simple Network Management Protocol (SNMP) traps.


E-Series Servers are available in the following options:

• Option 1—E-Series Server without a preinstalled operating system or hypervisor

• Option 2—E-Series Server with a preinstalled Microsoft Windows Server

At the time of purchase, you can choose the appropriate RAID option that you want enabled on the

E-Series Server.

Note

If you purchase this option, the Microsoft Windows Server license is preactivated.

• Option 3—E-Series Server with a preinstalled VMware vSphere Hypervisor

™

At the time of purchase, you can choose the appropriate RAID option that you want enabled on the

E-Series Server.

Note

The default username for the preinstalled VMware vSphere Hypervisor

™ is root, which cannot be changed, and the default password is password. After you log in, we recommend that you change the password.

8


OL-29450-01


The following figure shows the E-Series Server options.

Figure 4: E-Series Server Options


OL-29450-01


9

Basic Workflow for Option 1—E-Series Server without a Preinstalled Operating System or Hypervisor


Basic Workflow for Option 1—E-Series Server without a Preinstalled Operating

System or Hypervisor

The following figure shows the basic workflow for Option 1—E-Series Server without a preinstalled operating system or hypervisor.

Figure 5: Basic Workflow—Option 1

The following procedure provides the references for the tasks that you must perform when you purchase

Option 1—hardware only (E-Series Server without a preinstalled operating system or hypervisor).

10


OL-29450-01


Basic Workflow for Option 2—E-Series Server with a Preinstalled Microsoft Windows Server

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Procedure

Command or Action Purpose


See

Installing the E-Series Server into the Router, on page

15 .

Configure the CIMC IP address for

CIMC access.

See


.

Access CIMC.

See

Accessing CIMC, on page 55

.

Configure RAID and make the disk drive bootable.

See


.

Install the operating system and if needed, install the drivers.

See

Installing the Operating System or Hypervisor, on page

71 .

Configure an internal connection between the router and the E-Series

Server.

Depending on whether you want the traffic to flow through the router or not, do one of the following:

• If you do not want the traffic to your application or operating system to flow through the router, use the server’s host operating system to configure the

E-Series Server’s external GE2 or GE3 interface.

• If you want the traffic to your application or operating system to flow through the router, use the Cisco IOS

CLI to configure an internal connection between the router and the E-Series Server. See

Configuring a

Connection Between the Router and the E-Series

Server, on page 87

.

Basic Workflow for Option 2—E-Series Server with a Preinstalled Microsoft

Windows Server


Option 2—E-Series Server with a preinstalled Microsoft Windows Server.

Procedure

Step 1

Step 2



See


15 .


CIMC access.

See


.

OL-29450-01


11

Basic Workflow for Option 3—E-Series Server with a Preinstalled VMware vSphere Hypervisor


Step 3

Step 4



Server.


• If you do not want the traffic to your application or operating system to flow through the router, use the server’s host operating system to configure the E-Series

Server’s external GE2 or GE3 interface.



Configuring a


Server, on page 87

.

Access CIMC, and then access the

Microsoft Windows Server from

CIMC.

See


.

Basic Workflow for Option 3—E-Series Server with a Preinstalled VMware

vSphere Hypervisor


Option 3—E-Series Server with a preinstalled VMware vSphere Hypervisor

™

.

Procedure

Step 1

Step 2

Step 3



See


15 .


CIMC access.

See


.


Server.


• If you do not want the traffic to your application or operating system to flow through the router, use the server’s host operating system to configure the E-Series

Server’s external GE2 or GE3 interface.



Configuring a

12


OL-29450-01


Common Terms Used in This Guide

Step 4



Server, on page 87

.

Access CIMC, and then access the

VMware vSphere Hypervisor

™ from CIMC.

See


.


The following table provides the common terms used in this guide.

Table 3: Common Terms

Terms

CIMC

CLI

IMC

BMC

LOM

RAID

Description

Cisco Integrated Management Controller.

CIMC is the management service for the E-Series Server. CIMC runs within the server. You can use

CIMC to access, configure, administer, and monitor the server.

Command-Line Interface.

Integrated Management Controller.

IMC is used in the Cisco IOS commands to configure CIMC.

Board Management Controller.

LAN on Motherboard.

Shared LOM interfaces are used to configure CIMC access.

Redundant Array of Inexpensive Disks.

RAID is used to store E-Series Server data files.


13 OL-29450-01



14


OL-29450-01

C H A P T E R

3

Installing the E-Series Server into the Router


•

Basic Workflow for Installing the E-Series Server into the Router, page 15

•

Verifying the Router, E-Series Server, and Cisco IOS Software Version Compatibility, page 15

•

Installing the E-Series Server into the Router, page 16

•

Stopping the E-Series Server from Resetting and Updating the CIMC Firmware, page 18

•

Verifying E-Series Server Installation, page 19

Basic Workflow for Installing the E-Series Server into the Router

1

Verify that the router, the E-Series Server, and the Cisco IOS software version that is installed on the router are compatible.

2


Important

If you are migrating the E-Series Server from an ISR G2 into a Cisco ISR 4451-X, you must first update the CIMC firmware image to release 2.0(1.20130626092411) or the latest version and the BIOS firmware image to release 1.5.0.2 or the latest version—while the E-Series Server is still installed in the ISR G2—and then migrate it into the Cisco ISR 4451-X. For CIMC firmware installation instructions, see the "CIMC

Firmware Management" chapter in the GUI Configuration Guide for Cisco UCS E-Series Servers Integrated

Management Controller on Cisco.com.

3

Verify that the E-Series Server is correctly detected by the router.

Verifying the Router, E-Series Server, and Cisco IOS Software

Version Compatibility

The following table provides the router, the E-Series Server, and the Cisco IOS software version compatibility information.


15 OL-29450-01



3925

3925e

3945

3945e

4451

Table 4: Router, E-Series Server, and Cisco IOS Version Compatibility

Router

2911

2921

2951

Cisco IOS Software Version for

Single-Wide E-Series Servers

15.2(4)M and later versions







XE 3.9S and later versions

Cisco IOS Software Version for Double-Wide

E-Series Servers

—


Note

Supports 4-core only


Note

Supports 4-core only





XE 3.9S and later versions


The following figure shows how to install the E-Series Server into a router. For detailed information, see the

Hardware Installation Guide for Cisco UCS E-Series Servers on Cisco.com.

16


OL-29450-01



Important

If you are migrating the E-Series Server from an ISR G2 into a Cisco ISR 4451-X, you must first update the CIMC firmware image to release 2.0(1.20130626092411) or the latest version and the BIOS firmware image to release 1.5.0.2 or the latest version—while the E-Series Server is still installed in the ISR G2—and then migrate it into the Cisco ISR 4451-X. For CIMC firmware installation instructions, see the "CIMC

Firmware Management" chapter in the GUI Configuration Guide for Cisco UCS E-Series Servers Integrated

Management Controller on Cisco.com.

We strongly recommend that you upgrade both the CIMC and the BIOS firmware images.

If you migrate the E-Series Server into the Cisco ISR 4451-X without first updating the CIMC firmware, the E-Series Server will continuously reset. To stop the reset and install the firmware, see

Stopping the

E-Series Server from Resetting and Updating the CIMC Firmware, on page 18

.

Figure 6: Double-Wide E-Series Server in an ISR G2

OL-29450-01


17


Stopping the E-Series Server from Resetting and Updating the CIMC Firmware

Caution

Before you install or remove the E-Series Server from a Cisco 2900 series ISR G2, make sure that you first power down the router, and then install or remove the E-Series Server.

Figure 7: Double-Wide E-Series Server in a Cisco ISR 4451-X

Stopping the E-Series Server from Resetting and Updating the

CIMC Firmware

If you migrate the E-Series Server into the Cisco ISR 4451-X without first updating the CIMC firmware, the

E-Series Server will continuously reset. Use this procedure to stop the reset and install the firmware.

Note

Some of the steps in this procedure are performed from the router, and other steps are performed from the

E-Series Server.

Procedure

Step 1

Step 2

Command or Action

Router# hw-module subslot

slot/subslot maintenance enable


slot/subslot session imc

Purpose

Disables error recovery, which stops the E-Series

Server from being reset.

Note

Enter the commands in Step 1 and Step 2 from the router.

Starts a CIMC session.

18


OL-29450-01


Verifying E-Series Server Installation

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10


Server# scope cimc

Server/cimc # scope firmware

Server/cimc/firmware # update

tftp-ip-address path-and-filename

Purpose

Enters CIMC command mode.

Note

Enter the commands in Step 3 through Step

8 from the E-Series Server.

Enters CIMC firmware command mode.

Starts CIMC firmware update. The server will obtain the update firmware at the specified path and filename from the TFTP server at the specified IP address.

Server/cimc/firmware # show [detail] Displays the available firmware and status.

Server/cimc/firmware # activate [1 |

2]

Activates the selected image. If no image number is specified, the server activates the currently inactive image.

Exits the CIMC session.

Click Ctrl a Ctrl q.


slot/subslot maintenance disable


slot/subslot reload

Enables error recovery.

Note

Enter the commands in Step 9 and Step 10 from the router.

Reloads the E-Series Server.

Note

This reload power-cycles the E-Series

Server.


Before You Begin

• Install the E-Series Server into the router.

• Load a compatible Cisco IOS image.

• Power on the server.

To verify the E-Series Server installation, use one of the following commands:

• To display a high-level overview of the entire physical system, use the show platform command:

Router#

show platform

Chassis type: ISR4451/K9

Slot Type State Insert time (ago)

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

0 ISR4451/K9 ok 1d01h

1

0/0 ISR4400-4X1GE

ISR4451/K9 ok ok

1d01h

1d01h

2

1/0

R0

UCS-E160DP-M1/K9

ISR4451/K9

ISR4451/K9 ok ok ok, active

1d01h

1d01h

1d01h


19 OL-29450-01



F0

P0

P1

P2

ISR4451/K9

XXX-XXXX-XX

Unknown

ACS-4450-FANASSY ok, active ok ps, ok

1d01h

1d01h

1d01h

1d01h

Slot CPLD Version Firmware Version

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

0 12090323 12.2(20120829:165313)

1

2

R0

F0

12090323

12090323

12090323

12090323

12.2(20120829:165313)

12.2(20120829:165313)

12.2(20120829:165313)

12.2(20120829:165313)

• To verify that the router recognizes the E-Series Server, use the show hw-module subslot all oir command:

Router#

show hw-module subslot all oir

Module Model Operational Status

------------- -------------------- -----------------------subslot 0/0 ISR4451-X-4X1GE subslot 1/0 UCS-E140S-M1/K9 subslot 2/0 UCS-E140S-M1/K9 ok ok ok

20


OL-29450-01

C H A P T E R

4



•

Router Configuration Differences Between the Cisco SRE-V and the E-Series Server—ISR G2, page

21

•

Router Configuration Differences Between the ISR G2 and the Cisco ISR 4451-X, page 22

•

VMware vSphere Hypervisor Configuration Differences, page 23

Router Configuration Differences Between the Cisco SRE-V and

the E-Series Server—ISR G2

The examples in the following table provide the key differences between the Cisco SRE-V and the E-Series

Server configuration.

Table 5: Differences in Router Configuration Between the Cisco SRE-V and the E-Series Server—ISR G2

Cisco SRE-V Configuration Cisco E-Series Server Configuration

interface GigabitEthernet0/0 ip address 10.0.0.1 255.0.0.0

interface sm 1/0 ip unnumbered GigabitEthernet0/0 service-module ip address 10.0.0.2 255.0.0.0

service-module ip default-gateway 10.0.0.1


interface ucse 1/0 ip unnumbered GigabitEthernet0/0 imc ip address 10.0.0.2 255.0.0.0 default-gateway

10.0.0.1

imc access-port shared-lom console interface SM1/1 switchport mode trunk ip route 10.0.0.2 255.255.255.255 sm1/0 interface ucse1/1 switchport mode trunk ip route 10.0.0.2 255.255.255.255 ucse1/0

Note the following differences:

• In the E-Series Server, the sm slot/port command is replaced by the ucse slot/port command.


21 OL-29450-01


Router Configuration Differences Between the ISR G2 and the Cisco ISR 4451-X

• In the E-Series Server, the service-module keyword is replaced by the imc keyword.

• In the E-Series Server, the default gateway command resides in the same command line as the imc ip

address command.

• Since the E-Series Server has different external interfaces, you must specify the access port using the

imc access-port command.

• In the E-Series Server, you can either use the dedicated interface or one of the shared local area network on motherboard (shared LOM) interfaces to configure CIMC access. See

Configuring CIMC Access,

on page 25 .

In the above example, the imc access-port shared-lom console command uses the console interface for CIMC access, where:

◦imc access-port—is the physical Ethernet connection to the E-Series Server.

◦shared-lom—is shared LOM.

◦console—is the router interface.

The command to session into the server has also changed:

• Cisco SRE-V uses the service-module sm slot/0 session command to session into the server.

• E-Series Server uses the ucse slot session {imc | host} command to session into the server.

Router Configuration Differences Between the ISR G2 and the

Cisco ISR 4451-X

The examples in the following table provide the key differences between the ISR G2 configuration and the

Cisco ISR 4451-X configuration.

Table 6: Differences in Router Configuration Between the ISR G2 and the Cisco ISR 4451-X

Cisco ISR G2 Configuration Cisco ISR 4451-X Configuration


interface ucse 1/0 ip unnumbered GigabitEthernet0/0 imc ip address 10.0.0.2 255.0.0.0 default-gateway

10.0.0.1

imc access-port shared-lom console interface ucse1/1 switchport mode trunk ip route 10.0.0.2 255.255.255.255 ucse1/0 interface GigabitEthernet 0/0/0 ip address 10.0.0.1 255.0.0.0

ucse subslot 1/0 imc access-port ge0 imc ip address 10.0.0.2 255.0.0.0 default-gateway

10.0.0.1

interface ucse1/0/0 ip unnumbered GigabitEthernet0/0/0 no negotiation auto switchport mode trunk ip route 10.0.0.2 255.255.255.255 ucse1/0/0

Note the following differences:

22


OL-29450-01


VMware vSphere Hypervisor Configuration Differences

• In the Cisco ISR 4451-X, the interface ucse slot/port command is replaced by the ucse subslot slot/port and the interface ucse slot/port/subport commands.

• In the Cisco ISR 4451-X (with Cisco IOS XE Release 3.9S), the imc access-port shared-lom command is replaced by the imc access-port command.

• In the ISR G2, you can use either the dedicated interface or one of the shared local area network on motherboard (shared LOM) interfaces to configure CIMC access.

In the Cisco ISR 4451-X, you can use either the management interface or one of the NIC interfaces to configure CIMC access. See


.

In the above example, the command configures CIMC access using the E-Series Server's internal GE0

NIC interface, where:

◦imc access-port—CIMC access port configuration.

◦ge0—E-Series Server's internal GE0 NIC interface.

The command to session into the server has also changed:

• In the ISR G2, you use the ucse slot session {imc | host} command to session into the server.

• In the Cisco ISR 4451-X, you use the hw-module subslot slot/0 session {imc | server} command to session into the server.


In the Cisco SRE-V, the IP address of the VMware vSphere Hypervisor

™ host is the same as the IP address of the service module. For example, in the Cisco SRE-V, service-module ip address 10.0.0.2 (see table) is also assigned to the VMware vSphere Hypervisor

™ host.

Table 7: Differences in Router Configuration Between the Cisco SRE-V and the E-Series Server—ISR G2

Cisco SRE-V Configuration Cisco E-Series Server Configuration


interface sm 1/0 ip unnumbered GigabitEthernet0/0

service-module ip address 10.0.0.2 255.0.0.0

service-module ip default-gateway 10.0.0.1


interface ucse 1/0 ip unnumbered GigabitEthernet0/0

imc ip address 10.0.0.2 255.0.0.0 default-gateway

10.0.0.1

imc access-port shared-lom console interface SM1/1 switchport mode trunk ip route 10.0.0.2 255.255.255.255 sm1/0 interface ucse1/1 switchport mode trunk ip route 10.0.0.2 255.255.255.255 ucse1/0

However, with the E-Series Server, the IMC IP address, which is also 10.0.0.2 (see the example above), is reserved for CIMC access. You enter this IP address (10.0.0.2) on your web browser to access the CIMC GUI.


23 OL-29450-01



In the E-Series Server, either the VMware vSphere Hypervisor

™ assigns an IP address to the host using DHCP, or you can choose to assign a static IP address to the VMware vSphere Hypervisor

™ host. See

Assigning a

Static IP Address to the VMware vSphere Hypervisor, on page 79

.

24


OL-29450-01

C H A P T E R

5

Configuring CIMC Access

This chapter provides an overview of the E-Series Server interfaces and provides procedures to configure

CIMC access when the E-Series Server is installed in ISR G2 and the Cisco ISR 4451-X. It contains the following sections:

•

Configuring CIMC Access - ISR G2, page 26

•

Configuring CIMC Access - Cisco ISR 4451-X, page 37

•

Configuring CIMC Access Using the CIMC Configuration Utility, page 51

•

Defining Network Static Settings Using a Script File, page 53

OL-29450-01


25


Configuring CIMC Access - ISR G2

Configuring CIMC Access - ISR G2

E-Series Server Interfaces Overview—ISR G2

The following figure shows the interfaces in a double-wide E-Series Server and the ISR G2 host router.

Figure 8: Interfaces in a Double-Wide E-Series Server

1

Interface Interface Location

Router’s PCIe slot/0 Interface Internal Interface

2

3

Router’s MGF slot/1 VLAN

Interface

Management (Dedicated)

Interface

Internal Interface

External Interface

Description

Also called Console interface. This interface connects the router’s PCIe interface to the E-Series Server. The

PCIe interface provides an internal

Layer 3 GE link between the router and the E-Series Server. It can be used both for CIMC configuration and for host operating system configuration.

Used to access CIMC over a high-speed backplane switch. The

MGF VLAN interface provides an internal Layer 2 GE link between the router and the E-Series Server. This interface can be used both for CIMC configuration and for host operating system configuration.

Used for CIMC configuration and management.

26


OL-29450-01


CIMC Access Configuration Options—ISR G2

4 GE3 Interface

5 GE2 Interface

External Interface

External Interface

Used as a primary interface or as a backup interface. This interface can be used both for CIMC configuration and for host operating system configuration.

Note

The GE3 interface is only available on the double-wide E-Series

Servers.

Used as a primary interface or as a backup interface. This interface can be used both for CIMC configuration and for host operating system configuration.


Depending on whether you are a remote user or a local user, do one of the following to configure CIMC access.

• If you are a remote user, use either the external Management (dedicated) interface or one of the following shared LOM interfaces to configure CIMC access:

◦Router’s internal PCIe slot/0 Console interface

◦Router's internal MGF slot/1 VLAN interface

◦E-Series Server’s external GE2 or GE3 interface

• If you are a local user, use the Cisco IOS CLI or the CIMC Configuration Utility to configure CIMC access.

OL-29450-01


27



Configuring CIMC Access Using the E-Series Server's External Management (Dedicated)

Interface—ISR G2

See the following figure and the procedure that follows to configure CIMC access using the E-Series Server's external Management (dedicated) interface.

Figure 9: Configuring CIMC Access Using the E-Series Server's External Management (Dedicated) Interface


Make sure that you have the following information:

• IP address of CIMC.

• Username and password for logging in to the router.

• Slot and port number of the E-Series Server.

Procedure

Step 1

Step 2


Router> enable

Router# configure terminal

Purpose

Enters privileged EXEC mode on the host router. Enter your password if prompted.

Enters global configuration mode on the host router.

28


OL-29450-01



Step 6

Step 7

Step 8

Step 9

Step 3

Step 4

Step 5


Router (config)# interface ucse

slot/port

Purpose

Enters interface configuration mode for the slot and port where the E-Series Server is installed.

Router (config-if)# imc ip address

cimc-ip-address subnet-mask

default-gateway

cimc-gateway-ip-address

Specifies the IP address of CIMC and the IP address of the default gateway that CIMC must use.

• cimc-ip-address—IP address of CIMC.

• subnet-mask—Subnet mask used to append to the

IP address; must be in the same subnet as the host router.

• cimc-gateway-ip-address— IP address for the default gateway.

Router (config-if)# imc access-port

dedicated

Configures CIMC access through the server’s external

Management (dedicated) interface. See # 3 in

E-Series

Server Interfaces Overview—ISR G2

.

Router (config-if)# no shut Causes the interface to be administratively up.

Router (config-if)# end

Router# show running-config

Router# copy running-config

startup-config

Exits configuration mode.

Displays the running configuration of the router so that you can verify the address configurations.

(Optional) Saves the new running configuration of the router as the startup configuration.

This example shows how to configure CIMC access using the server’s external IMC dedicated interface:

Router>

enable

Router> password

Router#

configure terminal

Router(config)#

interface ucse 2/0

Router(config-if)#

imc ip address 10.0.0.1 255.0.0.0 default-gateway 10.0.0.2

Router(config-if)#

imc access-port dedicated

Router(config-if)#

no shut

Router(config-if)#

end

Router#

show running-config

Router#

copy running-config startup-config

Configuring CIMC Access Using Shared LOM—ISR G2

Use one of the following shared LOM interfaces to configure CIMC access:

• Router’s internal PCIe slot/0 Console interface

• Router's internal MGF slot/1 VLAN interface

OL-29450-01


29



• E-Series Server’s external GE2 or GE3 interface

Configuring CIMC Access Using the Router's Internal PCIe Slot/0 Console Interface—ISR G2

See the following figure and the procedure that follows to configure CIMC access using the router's internal

PCIe slot/0 Console interface.

Figure 10: Configuring CIMC Access Using the Router's Internal PCIe Slot/0 Console Interface

Step 1

Step 2

Step 3

Step 4






Procedure


Router> enable


Router (config)# interface

GigabitEthernet0/0

Router (config-if)# ip address

ip-address subnet mask

Purpose



Enters interface configuration mode for Gigabit Ethernet

0/0.

Specifies the IP address and subnet mask of the interface.

30


OL-29450-01



Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

Step 11

Step 12

Step 13

Step 14

Step 15


Router (config-if)# no shut



Purpose

Causes the interface to be administratively up.




slot/port


Router (config-if)# ip

unnumbered type number

The ip unnumbered command enables IP processing on an interface without assigning an explicit IP address to that interface.

• type—Type of interface on which the router has an assigned IP address.

• number—Number of the interface and subinterface on which the router has an assigned IP address.

Note

The unnumbered interface must be unique. It cannot be another unnumbered interface.

When you use the ip unnumbered command, you must use the ip route command to create a static route.

Caution

The ip unnumbered and ipv6 unnumbered commands create a point-to-point interface between devices. Broadcasting is not supported.



default-gateway




• subnet-mask—Subnet mask used to append to the IP address; must be in the same subnet as the host router.


Router (config-if)# imc

access-port shared-lom console

Configures CIMC access using the router's PCIe slot/0

(console) interface. See # 1 in

E-Series Server Interfaces

Overview—ISR G2

.


Router (config-if)# end Exits configuration mode.

Router# configure terminal Enters global configuration mode on the host router.

Router (config)# ip route

cimc-ip-address subnet-mask ucse

slot/port

Creates a static route.


OL-29450-01


31



Step 16

Step 17

Step 18

Step 19


• slot/port—Slot and port where the E-Series Server is installed.


Router# ping cimc-ip-address



startup-config


Verifies connection from the router to CIMC through the router's internal PCIe slot/0 console interface.



This example shows how to configure CIMC access using the server’s internal PCIe slot/0 console interface:

Router>

enable

Router> password

Router#


Router(config)#

interface GigabitEthernet0/0

Router(config-if)#

ip address 10.0.0.1 255.0.0.0

Router(config-if)#

no shut

Router(config-if)#

end

Router#


Router(config)#


Router(config)#

ip unnumbered GigabitEthernet0/0

Router(config-if)#


Router(config-if)#

imc access-port shared-lom console

Router(config-if)#

no shut

Router(config)#

end

Router#


Router(config)#

ip route 10.0.0.2 255.255.255.255 ucse 2/0

Router(config)#

end

Router#

ping 10.0.0.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.0.0.2, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

Router#


Router#


32


OL-29450-01



Configuring CIMC Access Using the Router's Internal MGF Slot/1 VLAN Interface—ISR G2

See the following figure and the procedure that follows to configure CIMC access using the router's internal

MGF slot/1 VLAN interface.

Figure 11: Configuring CIMC Access Using the Router's Internal MGF Slot/1 VLAN Interface

OL-29450-01

Note

* For a list of supported Cisco EtherSwitch EHWICs, see Supported Cisco EtherSwitch EHWIC and Cisco

EtherSwitch Service Modules .






Procedure

Step 1

Step 2

Step 3


Router> enable

Router# show vlan-switch


Purpose


Displays VLANs.



33



Step 11

Step 12

Step 13

Step 14

Step 15

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10


Router (config)# interface vlan

vlan-number


vlan-ip-address subnet mask

Purpose

Enters VLAN configuration mode for the specified

VLAN number.

Specifies the IP address for the VLAN.

• vlan-ip-address—IP address of the VLAN.

• subnet-mask—Subnet mask to append to the IP address.




slot/port





default-gateway








shared-lom GE1

Configures CIMC access using the router’s internal

slot/1 MGF VLAN interface. See # 2 in

E-Series Server

Interfaces Overview—ISR G2 .






startup-config


Verifies connection from the router to CIMC through the router's internal MGFslot/1 VLAN interface.



This example shows how to configure CIMC access using the router's internal MGF slot/1 VLAN interface:

Router>

enable

Router> password

Router>

show vlan-switch

VLAN Name Status Ports

34


OL-29450-01



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

1 default active Gi0/0/0, Gi0/0/1, Gi0/0/2

Gi0/0/3, uc2/1

Router#


Router(config)#

interface vlan 1

Router(config-if)#

ip address 10.0.0.1 255.0.0.0

Router(config-if)#

end

Router#


Router(config)#


Router(config-if)#


Router(config-if)#

imc access-port shared-lom GE1

Router(config-if)#

no shut

Router(config-if)#

end

Router#

ping 10.0.0.2



!!!!!


Router#


Router#


Configuring CIMC Access Using the E-Series Server's External GE2 or GE3 Interface—ISR G2

See the following figure and the procedure that follows to configure CIMC access using the E-Series Server's external GE2 or GE3 interface.

Note

This figure shows how to configure CIMC access using the E-Series Server's external GE2 interface.

Figure 12: Configuring CIMC Access Using the E-Series Server's External GE2 Interface

OL-29450-01


35



Step 1

Step 2

Step 3

Step 4






Procedure

Step 5

Step 6

Step 7

Step 8

Step 9


Router> enable

Purpose





slot/port




default-gateway








shared-lom {GE2 | GE3}

Configures CIMC access through E-Series Server's external GE2 or GE3 interface. See # 4 and 5 in

E-Series

Server Interfaces Overview—ISR G2 .







startup-config



This example shows how to configure CIMC access using the server's external GE2 interface:

Router>

enable

Router> password

Router#


Router(config)#


36


OL-29450-01


Configuring CIMC Access - Cisco ISR 4451-X

Router(config-if)#


Router(config-if)#


Router(config-if)#

no shut

Router(config-if)#

end

Router#


Router#


Configuring CIMC Access - Cisco ISR 4451-X

E-Series Server Interfaces Overview—Cisco ISR 4451-X

The following figure shows the interfaces in a double-wide E-Series Server and the Cisco ISR 4451-X host router.

Figure 13: Interfaces in a Double-Wide E-Series Server

OL-29450-01

1

Interface

Router’s ucse slot/0/0

Interface

Interface Location

Internal Interface

Description


MGF interface provides an internal

Layer 2 GE link between the router and the E-Series Server. This interface can be used both for CIMC configuration and for host operating system configuration.

Note

This interface is used to access the E-Series Server's internal GE0 interface.


37


CIMC Access Configuration Options—Cisco ISR 4451-X

2 Router’s ucse slot/0/1 Interface Internal Interface

3 GE0 and GE1 Interfaces Internal Interfaces

4

5

Management (Dedicated)

Interface

GE3 Interface

External Interface

External Interface

6 GE2 Interface External Interface


MGF interface provides an internal

Layer 2 GE link between the router and the E-Series Server. This interface can be used both for CIMC configuration and for host operating system configuration.

Note

This interface is used to access the E-Series Server's internal GE1 interface.

E-Series Server's internal NIC interfaces.

Used for CIMC configuration and management.

Can be used both for CIMC configuration and for host operating system configuration.

Note

The GE3 interface is only available on the double-wide E-Series

Servers.

Can be used both for CIMC configuration and for host operating system configuration.


Depending on whether you are a remote user or a local user, do one of the following to configure CIMC access.

• If you are a remote user, use the Cisco IOS CLI to configure CIMC access by using one of the following interfaces:

◦CIMC Management (dedicated) interface

◦E-Series Server’s internal GE0 and the router's ucse slot/0/0 interface

◦E-Series Server’s internal GE1 interface and the router's ucse slot/0/1 interface

◦E-Series Server’s external GE2 or GE3 interface

• If you are a local user, use the CIMC Configuration Utility or the Cisco IOS CLI (mentioned above) to configure CIMC access.

38


OL-29450-01



Configuring CIMC Access Using the E-Series Server's External Management (Dedicated)

Interface—Cisco ISR 4451-X

See the following figure and the procedure that follows to configure CIMC access using the E-Series Server's external Management (dedicated) interface.

Figure 14: Configuring CIMC Access Using the E-Series Server's External Management (Dedicated) Interface

OL-29450-01






Procedure

Step 1

Step 2


Router> enable


Purpose




39



Step 3

Step 4

Step 5

Step 6

Step 7

Step 8


Router (config)# ucse subslot

slot/port

Router (config-ucse)# imc ip

address cimc-ip-address

subnet-mask default-gateway


Router (config-ucse)# imc

access-port mgmt or Router

(config-ucse)# imc access-port

dedicated

Configures CIMC access through the server’s external

Management (dedicated) interface. See # 4 in

E-Series

Server Interfaces Overview—Cisco ISR 4451-X, on page

37 .

• Use the imc access-port mgmt command if you installed the Cisco IOS XE Release 3.9S.

• Use the imc access-port dedicated command if you installed the Cisco IOS XE Release 3.10S and later versions.

Router (config-ucse)# end



startup-config

Purpose

Enters ucse interface configuration mode for the slot and port where the E-Series Server is installed.




• cimc-gateway-ip-address—IP address for the default gateway.

Returns to privileged EXEC mode on the host router.



This example shows how to configure CIMC access using the server’s external management interface—Applicable only with Cisco IOS XE Release 3.9S:

Router>

enable

Router> password

Router#


Router(config)#

ucse subslot 1/0

Router(config-ucse)#



imc access-port mgmt


end

Router#


Router#


This example shows how to configure CIMC access using the server’s external dedicated interface—Applicable with Cisco IOS XE Release 3.10S and later versions:

Router>

enable

40


OL-29450-01



Router> password

Router#


Router(config)#





imc access-port dedicated


end

Router#


Router#


Configuring CIMC Access Using the E-Series Server's NIC Interfaces—Cisco ISR 4451-X

Use one of the following E-Series Server's NIC interfaces to access CIMC:

• E-Series Server’s internal GE0 and the router's ucse slot/0/0 interface

• E-Series Server’s internal GE1 interface and the router's ucse slot/0/1 interface

• E-Series Server’s external GE2 or GE3 interface

Configuring CIMC Access Using the E-Series Server's Internal GE0 Interface and the Cisco ISR 4451-X ucse slot /0/0

Interface

See the following figure and the procedure that follows to configure CIMC access using the E-Series Server's internal GE0 interface and the router's ucse slot/0/0 interface.

Figure 15: Configuring CIMC Access Using the E-Series Server's Internal GE0 Interface and the Router's ucse slot/0/0

Interface

OL-29450-01






41



Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8


Procedure

Step 9

Step 10

Step 11

Step 12


Router> enable



GigabitEthernet 0/0/0


ip-address subnet-mask


Purpose



Enters interface configuration mode for Gigabit Ethernet interface 0/0/0.



Router (config-if)# exit Exits interface configuration mode.


slot/0/0

Enters ucse interface configuration mode for the slot, port, and subport where the E-Series Server is installed.







Router (config-if)# exit


slot/port





Note



Caution



Exits interface configuration mode.





42


OL-29450-01



OL-29450-01

Step 13

Step 14

Step 15

Step 16

Step 17

Step 18

Step 19




access-port ge0 or Router


shared-lom console

Configures CIMC access using the E-Series Server's internal

GE0 or console interface. See # 3 in

E-Series Server

Interfaces Overview—Cisco ISR 4451-X, on page 37

.

• Use the imc access-port ge0 command if you installed the Cisco IOS XE Release 3.9S.

• Use the imc access-port shared-lom console command if you installed the Cisco IOS XE Release

3.10S and later versions.

Router (config-ucse)# exit Exits ucse interface configuration mode.



slot/port/subport



• slot/port/subport—Slot, port, and subport where the

E-Series Server is installed.

Router (config)# end




startup-config


Verifies the connection from the router to CIMC through the ucse slot/0/0 interface.



This example shows how to configure CIMC access using the E-Series Server's internal GE0 interface and the router's ucse slot/0/0 interface—Applicable only with Cisco IOS XE Release 3.9S:

Router>

enable

Router> password

Router#


Router(config)#

interface GigabitEthernet0/0/0

Router(config-if)#

ip address 10.0.0.1 255.0.0.0

Router(config-if)#

no shut

Router(config-if)#

exit

Router(config)#

interface ucse 1/0/0

Router(config-if)#

ip unnumbered GigabitEthernet0/0/0

Router(config-if)#

no shut

Router(config-if)#

exit

Router(config)#





imc access-port ge0


43




exit

Router(config)#

ip route 10.0.0.2 255.255.255.255 ucse 1/0/0

Router(config)#

end

Router#

ping 10.0.0.2



!!!!!


Router#


Router#


This example shows how to configure CIMC access using the E-Series Server's internal console interface and the router's ucse slot/0/0 interface—Applicable with Cisco IOS XE Release 3.10S and later versions:

Router>

enable

Router> password

Router#


Router(config)#


Router(config-if)#

ip address 10.0.0.1 255.0.0.0

Router(config-if)#

no shut

Router(config-if)#

exit

Router(config)#


Router(config-if)#


Router(config-if)#

no shut

Router(config-if)#

exit

Router(config)#





imc access-port shared-lom console


exit

Router(config)#

ip route 10.0.0.2 255.255.255.255 ucse 1/0/0

Router(config)#

end

Router#

ping 10.0.0.2



!!!!!


Router#


Router#


44


OL-29450-01



Configuring CIMC Access Using the E-Series Server's Internal GE1 Interface and the Cisco ISR 4451-X ucse slot

/0/1

Interface

See the following figure and the procedure that follows to configure CIMC access using the E-Series Server's internal GE1 interface and the router's ucse slot/0/1 interface.

Figure 16: Configuring CIMC Access Using the E-Series Server's Internal GE1 Interface and the Router's ucse slot/0/1

Interface

OL-29450-01

Step 1

Step 2

Step 3

Step 4

Step 5






Procedure


Router> enable



GigabitEthernet 0/0/0


ip-address subnet-mask


Purpose



Enters interface configuration mode for Gigabit Ethernet interface 0/0/0.




45



Step 6

Step 7

Step 8

Step 9

Step 10

Step 11

Step 12

Step 13



Purpose



slot/0/1

Enters ucse interface configuration mode for the slot, port, and subport where the E-Series Server is installed.









slot/port





Note



Caution










access-port ge1 or Router


shared-lom ge1

Configures CIMC access using the E-Series Server's internal

GE1 interface. See # 3 in

E-Series Server Interfaces

Overview—Cisco ISR 4451-X, on page 37

.

• Use the imc access-port ge1 command if you installed the Cisco IOS XE Release 3.9S.

• Use the imc access-port shared-lom ge1 command if you installed the Cisco IOS XE Release 3.10S and later versions.

46


OL-29450-01



OL-29450-01

Step 14

Step 15

Step 16

Step 17

Step 18

Step 19


Router (config-ucse)# exit

Purpose

Exits ucse interface configuration mode.



slot/port/subport



• slot/port/subport—Slot, port, and subport where the

E-Series Server is installed.

Router (config)# end




startup-config


Verifies the connection from the router to CIMC through the ucse slot/0/1 interface.



This example shows how to configure CIMC access using the E-Series Server's internal GE1 interface and the router's ucse slot/0/1 interface—Applicable only with Cisco IOS XE Release 3.9S:

Router>

enable

Router> password

Router#


Router(config)#


Router(config-if)#

ip address 10.0.0.1 255.0.0.0

Router(config-if)#

no shut

Router(config-if)#

exit

Router(config)#


Router(config-if)#


Router(config-if)#

no shut

Router(config-if)#

exit

Router(config)#





imc access-port ge1


exit

Router(config)#

ip route 10.0.0.2 255.255.255.255 ucse 1/0/1

Router(config)#

end

Router#

ping 10.0.0.2



!!!!!


Router#


Router#


This example shows how to configure CIMC access using the E-Series Server's internal GE1 interface and the router's ucse slot/0/1 interface—Applicable with Cisco IOS XE Release 3.10S and later releases:

Router>

enable


47



Router> password

Router#


Router(config)#


Router(config-if)#

ip address 10.0.0.1 255.0.0.0

Router(config-if)#

no shut

Router(config-if)#

exit

Router(config)#


Router(config-if)#


Router(config-if)#

no shut

Router(config-if)#

exit

Router(config)#





imc access-port shared-lom ge1


exit

Router(config)#

ip route 10.0.0.2 255.255.255.255 ucse 1/0/1

Router(config)#

end

Router#

ping 10.0.0.2



!!!!!


Router#


Router#


Configuring CIMC Access Using the E-Series Server's External GE2 or GE3 Interface—Cisco ISR 4451-X

See the following figure and the procedure that follows to configure CIMC access using the E-Series Server's external GE2 or GE3 interface.

48


OL-29450-01



Note

This figure shows how to configure CIMC access using the E-Series Server's external GE2 interface.

Figure 17: Configuring CIMC Access Using the E-Series Server's External GE2 Interface

OL-29450-01






Procedure

Step 1

Step 2

Step 3


Router> enable



slot/port

Purpose





49



Step 4

Step 5

Step 6

Step 7






Purpose






access-port {GE2 | GE3} or


access-port shared-lom {GE2 |

GE3}

Configures CIMC access through the E-Series Server's external GE2 or GE3 interface. See # 5 and 6 in

E-Series

Server Interfaces Overview—Cisco ISR 4451-X, on page

37 .

• Use the imc access-port {GE2 | GE3} command if you installed the Cisco IOS XE Release 3.9S.

• Use the imc access-port shared-lom {GE2 | GE3} command if you installed the Cisco IOS XE Release

3.10S and later versions.

Router (config-ucse)# end


Returns to privileged EXEC mode on the host router.


This example shows how to configure CIMC access using the server's external GE2 interface—Applicable only with Cisco IOS XE Release 3.9S:

Router>

enable

Router> password

Router#


Router(config)#





imc access-port GE2


no shut


end

Router#


This example shows how to configure CIMC access using the server's external GE2 interface—Applicable with Cisco IOS XE Release 3.10S and later releases:

Router>

enable

Router> password

Router#


Router(config)#







no shut


end

50


OL-29450-01


Configuring CIMC Access Using the CIMC Configuration Utility

Router#



If you are a local user, you can use either the Cisco IOS CLI or the CIMC Configuration Utility to configure

CIMC access. To configure CIMC access using the Cisco IOS CLI, see Configuring CIMC Access Using the

Cisco IOS CLI .

Note

When you use the CIMC Configuration Utility to configure CIMC access, the configuration is not reflected as Cisco IOS configuration. In other words, if you execute the show running-config command from the

Cisco IOS CLI, the changes that you made using the CIMC Configuration Utility are not reflected.

Procedure

Step 1

Power on the router.

Step 2

Connect a keyboard and monitor to the front panel of the E-Series Server.

Step 3

Press the Power button to boot the E-Series Server. During bootup, watch for the prompt to press F8.

Step 4

When you see the prompt, press F8.

OL-29450-01


51


The CIMC Configuration Utility appears.

Figure 18: CIMC Configuration Utility


Step 5

Use the CIMC configuration Utility to set the NIC mode and NIC redundancy, and to choose whether to enable DHCP or set static network settings.

a) From the NIC mode area, choose a port to access CIMC. Options are:

• Dedicated—The 10/100 IMC port is used to access CIMC.

• Shared LOM (default)—The four 1Gb Ethernet ports are used to access the CIMC. This is the factory default setting.

b) From the NIC redundancy area, choose the NIC redundancy. Options are:

• None—The Ethernet ports operate independently and do not fail over if there is a problem.

• Active-standby—If an active Ethernet port fails, the traffic falls over to a standby port. This is the factory default setting.

c) From the IPV4 (Basic) area, do one of the following:

• DHCP Enabled—Select this option to enable DHCP for dynamic network settings. Before you enable

DHCP, your DHCP server must be preconfigured with the range of MAC addresses for this server.

The MAC address is printed on a label on the rear of the server. This server has a range of six MAC

52


OL-29450-01


Defining Network Static Settings Using a Script File

addresses assigned to CIMC. The MAC address printed on the label is the beginning of the range of six contiguous MAC addresses.

• CIMC IP—IP address of CIMC.

Subnet Mask—Enter the subnet mask to append to the CIMC IP address; must be in the same subnet as the host router.

Gateway—IP address of the default gateway router.

d) (Optional) From the VLAN (Advanced) area, configure VLAN settings.

e) Press F5 to refresh the page and have the new settings appear.

The page refresh takes approximately 45 seconds.

f) Press F10 to save your settings and reboot the server.

If you chose to enable DHCP, the dynamically assigned IP and MAC addresses are displayed on the console screen during bootup.

Step 6

Using the ports that you selected for the NIC Mode settings in Step 5, substep a, connect Ethernet cables from your LAN to the E-Series Server.

Step 7

In your web browser, enter the IP address that you configured to access CIMC. The CIMC IP address is based upon the settings that you configured in Step 5, substep c (either a static IP address or the IP address assigned by your DHCP server).

The default user name to log into CIMC is admin and the default password is password.

Step 8

Use the CIMC GUI or CIMC CLI to manage and monitor the server.

See the GUI Configuration Guide for Cisco UCS E-Series Servers or the CLI Configuration Guide for Cisco

UCS E-Series Servers.


Use this procedure to define static network settings for multiple servers by automating the configuration process with a script file.

Procedure

Step 1

Use a text editor to create a file named network.cfg.

Step 2

Create the contents of network.cfg in the following format by using only the tags that you want to set: dhcp-enabled: v4-addr: v4-netmask: v4-gateway: vlan-enabled: vlan-id: vlan-priority: password: mode: redundancy:


53 OL-29450-01



For example, to disable DHCP, set the IP address, subnet mask, gateway, and user password, use the following sample values: dhcp-enabled: 0 v4-addr: 10.193.70.102

v4-netmask: 255.255.255.0

v4-gateway: 10.193.70.1

password: nonpasswd mode: redundancy:

Step 3

Use a text editor to create a file named startup.nsh with the following contents: fs0: cimcconfig

Step 4

Copy your network.cfg file and your startup.nsh file to a USB thumb drive.

Step 5

Insert the USB thumb drive into a USB port on the server.

Step 6

Press and release the Power button to boot the server.

Step 7

Observe the booting process and press F6 when prompted to enter the BIOS Boot Manager.

Step 8

Select EFI as the boot device and then press Enter.

The server power-cycles and launches the configuration utility, which runs the startup.nsh file. Any errors are displayed on the screen and on an errors.txt file.

Step 9

Remove the USB thumb drive, alter the network.cfg file with your next IP address, and then insert the USB thumb drive into the next server that you want to configure.

Step 10 After the server has been assigned an IP address, you can use that address to access the service processor's

GUI or CLI management system.

54


OL-29450-01

C H A P T E R

6

Accessing CIMC


•

CIMC Overview, page 55

•

Logging In to the CIMC GUI, page 56

•

CIMC Home Page, page 57

•

Accessing the Microsoft Windows Server from CIMC, page 58

•

Accessing the VMware vSphere Hypervisor from CIMC, page 58

•

What to Do Next, page 59

CIMC Overview

The Cisco Integrated Management Controller (CIMC) is the management service for the E-Series Servers.

CIMC runs within the server. You can use a web-based GUI or the SSH-based CLI to access, configure, administer, and monitor the server.

You can use CIMC to perform the following server management tasks:

• Power on, power off, power cycle, reset, and shut down the server

• Configure the server boot order

• Manage RAID levels

• View server properties and sensors

• Manage remote presence

• Create and manage local user accounts, and enable remote user authentication through the Active

Directory

• Configure network-related settings, including NIC properties, IPv4, VLANs, and network security

• Configure communication services, including HTTP, SSH, IPMI over LAN, and SNMP

• Manage certificates

• Configure platform event filters


55 OL-29450-01

Accessing CIMC

CIMC GUI

• Update CIMC firmware

• Update BIOS firmware

• Install the host image from an internal repository

• Monitor faults, alarms, and server status

• Collect technical support data in the event of server failure

Almost all tasks can be performed in either the GUI interface or CLI interface, and the results of tasks performed in one interface are displayed in another. However, you cannot:

• Use the CIMC GUI to invoke the CIMC CLI

• View a command that has been invoked through the CIMC CLI in the CIMC GUI

• Generate CIMC CLI output from the CIMC GUI

CIMC GUI

The CIMC GUI is a web-based management interface for E-Series Servers. You can launch the CIMC GUI and manage the server from any remote host that meets the following minimum requirements:

• Java 1.6 or later

• HTTP and HTTPS enabled

• Adobe Flash Player 10 or later

CIMC CLI

The CIMC CLI is a command-line management interface for E-Series Servers. You can launch the CIMC

CLI in the following ways:

• By the serial port.

• Over the network by SSH.

• From the router by using the hw-module subslot slot/port session imc command.

A CLI user can have one of the three roles: admin, user (can control but cannot configure), and read-only.

Logging In to the CIMC GUI


• Make sure that you have configured the IP address to access CIMC.

• If not installed, install Adobe Flash Player 10 or later on your local machine.

56


OL-29450-01

Accessing CIMC

CIMC Home Page

Procedure

Step 1

In your web browser, enter the IP address that you configured to access CIMC during initial setup.

Step 2

If a security dialog box displays, do the following: a) (Optional) Check the check box to accept all content from Cisco.

b) Click Yes to accept the certificate and continue.

Step 3

In the log in window, enter your username and password.

Tip

When logging in for the first time to an unconfigured system, use admin as the username and password as the password.

Step 4

Click Log In.

The Change Password dialog box appears.

Note

The Change Password dialog box only appears the first time you log into CIMC. It does not appear for subsequent reboots.

Step 5

In the New Password field, enter your new password.

Step 6

In the Confirm Password field, enter the password again to confirm it.

Step 7

Click Save Changes.

The Server Summary page appears, which is the CIMC home page. See

CIMC Home Page, on page 57

.

CIMC Home Page

Figure 19: CIMC Home Page

OL-29450-01


57

Accessing CIMC

Accessing the Microsoft Windows Server from CIMC

Accessing the Microsoft Windows Server from CIMC


• CIMC IP address is configured for CIMC access.

• Microsoft Windows Server is installed on the E-Series Server.

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Summary.

Step 3

From the Actions area of the Server Summary page, click the Launch KVM Console icon.

The KVM Console opens in a separate window.

Step 4

From the KVM console, access the installed Microsoft Windows Server operating system.

Accessing the VMware vSphere Hypervisor from CIMC


• CIMC IP address is configured for CIMC access.

• VMware vSphere Hypervisor is installed on the E-Series Server.

Procedure

Step 1


Step 2


Step 3



Step 4

From the KVM console, click the KVM tab.

The VMware vSphere Hypervisor

™

Direct Console User Interface (DCUI) appears. If VMware vSphere

Hypervisor

™ has assigned an IP address to the host, then that IP address is displayed on the DCUI page, or you can specify a static IP address. See

Assigning a Static IP Address to the VMware vSphere Hypervisor,

on page 79 .

Step 5

Make sure that you have installed vSphere Client. If not, install it. See

Downloading and Installing the vSphere

Client, on page 81

.

Step 6

From the vSphere Client, log into the VMware vSphere Hypervisor

™

.

To log in, use either the IP address that is assigned by VMware vSphere Hypervisor

™ that you specified in Step 4.

or the static IP address

58


OL-29450-01

Accessing CIMC

What to Do Next

Note


™ is root, which cannot be changed and the default password is password. After you login, we recommend that you change the password.

What to Do Next

Do one of the following as appropriate:

• If you purchased E-Series Server Option 2 (E-Series Server with preinstalled Microsoft Windows Server) or Option 3 (E-Series Server with preinstalled VMware vSphere Hypervisor

™

), use the CIMC GUI or

CIMC CLI to manage and monitor the server.

See the GUI Configuration Guide for Cisco UCS E-Series Server Integrated Management Controller or the CLI Configuration Guide for Cisco UCS E-Series Server Integrated Management Controller.

• If you purchased E-Series Server Option 1 (E-Series Server without preinstalled operating system or hypervisor), configure RAID. See


.

OL-29450-01


59

What to Do Next

Accessing CIMC

60


OL-29450-01

C H A P T E R

7

Managing RAID

Note

If you purchased E-Series Server Option 1 (E-Series Server without preinstalled operating system or hypervisor), and you want to store data files on local Redundant Array of Inexpensive Disks (RAID), you must configure RAID.


•

RAID Options, page 61

•

Configuring RAID, page 65

•

What to Do Next, page 69

RAID Options

You can choose to store the E-Series Server data files on local Redundant Array of Inexpensive Disks (RAID).

The following RAID levels are supported:

• The single-wide E-Series Server supports RAID 0 and RAID 1 levels.

• The double-wide E-Series Server supports RAID 0, RAID 1, and RAID 5 levels.

• The double-wide E-Series Server with the PCIe option supports RAID 0 and RAID 1 levels.

OL-29450-01


61

RAID Options

Managing RAID

RAID 0

With RAID 0, the data is stored evenly in stripe blocks across one or more disk drives without redundancy

(mirroring). The data in all of the disk drives is different.

Figure 20: RAID 0

Compared to RAID 1, RAID 0 provides additional storage because both disk drives are used to store data.

The performance is improved because the read and write operation occurs in parallel within the two disk drives.

However, there is no fault tolerance, error checking, hot spare, or hot-swapping. If one disk drive fails, the data in the entire array is destroyed. Because there is no error checking or hot-swapping, the array is susceptible to unrecoverable errors.

RAID 1

RAID 1 creates a mirrored set of disk drives, where the data in both the disk drives is identical, providing redundancy and high availability. If one disk drive fails, the other disk drive takes over, preserving the data.

62


OL-29450-01

Managing RAID

RAID Options

RAID 1 also allows you to use a hot spare disk drive. The hot spare drive is always active and is held in readiness as a hot standby drive during a failover.


RAID 1 supports fault tolerance and hot-swapping. When one disk drive fails, you can remove the faulty disk drive and replace it with a new disk drive.

However, compared to RAID 0, there is less storage space because only half of the total potential disk space is available for storage and there is an impact on performance.

RAID 5

With RAID 5, the data is stored in stripe blocks with parity data staggered across all disk drives, providing redundancy at a low cost.


OL-29450-01


63

RAID Options

Managing RAID

RAID 5 provides more data storage capacity than RAID 1 and better data protection than RAID 0. It also supports hot swapping; however, RAID 1 offers better performance.

Non-RAID

When the disk drives of a computer are not configured as RAID, the computer is in non-RAID mode. Non-RAID mode is also referred to as Just a Bunch of Disks or Just a Bunch of Drives (JBOD). Non-RAID mode does not support fault tolerance, error checking, hot-swapping, hot spare, or redundancy.

Summary of RAID Options

RAID Option

RAID 0

Description

Data stored evenly in stripe blocks without redundancy

Advantages

• Better storage

• Improved performance

Disadvantages

• No error checking

• No fault tolerance

• No hot-swapping

• No redundancy

• No hot spare

RAID 1 Mirrored set of disk drives and an optional hot spare disk drive

• High availability

• Fault tolerance

• Hot spare

• Hot-swapping

• Less storage

• Performance impact

RAID 5 Data stored in stripe blocks with parity data staggered across all disk drives

• Better storage efficiency than

RAID 1

• Better fault tolerance than

RAID 0

• Low cost of redundancy

• Hot-swapping

• Slow performance

Non-RAID Disk drives not configured for RAID

Also referred to as JBOD

• Portable • No error checking

• No fault tolerance

• No hot-swapping

• No redundancy

• No hot spare

64


OL-29450-01

Managing RAID

Configuring RAID

Configuring RAID

You can use the CIMC GUI or the WebBIOS, which is accessible from the KVM console, to configure RAID.

Configuring RAID Using the CIMC GUI

Use this procedure to configure the RAID level, strip size, host access privileges, drive caching, and initialization parameters on a virtual drive. You can also use this procedure to designate the drive as a hot spare drive and to make the drive bootable.

Procedure

Step 1


Step 2

On the Server tab, click RAID. Do one of the following:

• If the Configure Virtual Drive dialog box does not appear, proceed to the next step.

• If the Configure Virtual Drive dialog box appears, and the virtual drives are not configured, complete the fields as shown in Step 5.

Step 3

In the tabbed menu of the Storage Cards area, click the Virtual Drive Info tab.

Figure 23: Virtual Drive Info Tab

OL-29450-01

Step 4

In the Actions area of the Virtual Drive Info tab, click Create.


65


The Configure Virtual Drive dialog box appears.

Figure 24: Configure Virtual Drive Dialog Box

Managing RAID

Step 5

Complete the following fields as appropriate:

Name Description

Available Drives table Displays the drives that are available for RAID configuration.

Note

To move a drive, click and drag a drive to the appropriate table.

Selected Drives table

RAID Level drop-down list

Displays the drives that are selected for RAID configuration.

Note

To move a drive, click and drag a drive to the appropriate table.

The RAID level options. This can be one of the following:

• RAID 0—Block striping.

• RAID 1—Mirroring.

• RAID 5—Block striping with parity.

Note

The single-wide E-Series Server supports RAID 0 and RAID

1 levels. The double-wide E-Series Server supports RAID 0,

RAID 1, and RAID 5 levels. The double-wide E-Series Server with the PCIe option supports RAID 0 and RAID 1 levels.

66


OL-29450-01

Managing RAID


Name

Name field

Strip Size drop-down list

Initialization drop-down list

Drive Cache drop-down list

Description

The name of the virtual drive.

Enter a maximum of 15 characters. The characters can have numbers and upper- or lower-case letters. Special characters are not supported.

The strip size options. This can be one of the following:

• 64 KB

• 32 KB

• 16 KB

• 8 KB

How the controller initializes the drives. This can be one of the following:

• Quick—The controller initializes the drive quickly. This is the default and recommended option.

• Full—The controller does a complete initialization of the new configuration.

Note

Depending on the size of the drives, full initialization can take several hours to complete. To view the progress, see the Initialize Progress and Initialize Time Elapsed fields in the General area.

• None—The controller does not initialize the drives.

How the controller handles drive caching. This can be one of the following:

• Disable—Caching is disabled on the drives.

Note

This is the default and recommended option.

• Unchanged—The controller uses the caching policy specified on the drive. This is the default and recommended option.

• Enable—Caching is enabled on the drives. This option minimizes the delay in accessing data.

Caution

Enabling Drive Cache, voids all warranty on the hard disk drives. This configuration option is not supported.

Use this option at your own risk.

OL-29450-01


67

Managing RAID

Configuring RAID Using the WebBIOS

Name

Access Policy drop-down list

Description

Configures host access privileges. This can be one of the following:

• Read-Write—The host has full access to the drive.

• Read Only—The host can read only data from the drive.

• Blocked—The host cannot access the drive.

Set this Virtual Drive Bootable

check box

How the controller boots the drive. This can be one of the following:

• Enable—The controller makes this drive bootable.

• Disable—This drive is not bootable.

Note

If you plan to install an operating system or Hypervisor into the RAID array, we recommend that you check this check box.

Use the Remaining Drive as Hot

Spare check box

Designates the drive that is in the Available Drives table as a hot spare drive.

Note

Applicable for RAID 1 only. This check box is greyed out for other RAID levels.

Applicable for double-wide E-Series Servers.

Step 6

Review the RAID configuration, and then click Confirm to accept the changes.

Configuring RAID Using the WebBIOS

Procedure

Step 1


Step 2


Step 3

From the Actions area, click Launch KVM Console.


Step 4

From the Server Summary page, click Power Cycle Server to reboot the server.

Step 5

Press the Ctrl key, and then press H during bootup to access the WebBIOS.

68


OL-29450-01

Managing RAID

What to Do Next

The Adapter Selection page from LSI Logic appears, which allows you to configure RAID. For information about this page, see the LSI Logic documentation.

Figure 25: WebBIOS

What to Do Next

If you purchased E-Series Server Option 1 (E-Series Server without preinstalled operating system or hypervisor), install the operating system. See

Installing the Operating System or Hypervisor, on page 71

.


69 OL-29450-01

What to Do Next

Managing RAID

70


OL-29450-01

C H A P T E R

8


Note

If you purchased E-Series Server Option 1 (E-Series Server without preinstalled operating system or hypervisor), you must install an operating system or hypervisor.


•

Operating System or Hypervisor Installation Methods, page 71

•

KVM Console, page 72

•

PXE Installation Servers, page 74

•

Host Image Mapping, page 74

•

Basic Workflow for Downloading and Installing the VMware vSphere Hypervisor, page 79

•

Configuring the Server Boot Order, page 81

Operating System or Hypervisor Installation Methods

E-Series Servers support several operating systems and hypervisors. Regardless of the platform being installed, you can install it on your server using one of the following methods:

• KVM console

• PXE installation server

• Host image mapping

Caution

You must use only one method to map virtual drives. For example, you must use either the KVM console or the Host Image Mapping method. Using a combination of methods will cause the server to be in an undefined state.


71 OL-29450-01


KVM Console

KVM Console

The KVM console is an interface accessible from the CIMC that emulates a direct keyboard, video, and mouse connection to the server. The KVM console allows you to connect to the server from a remote location. Instead of using CD/DVD or floppy drives physically connected to the server, the KVM console uses virtual media, which are actual disk drives or disk image files that are mapped to virtual CD/DVD or floppy drives. You can map any of the following to a virtual drive:

• CD/DVD or floppy drive on your computer

• Disk image files (ISO or IMG files) on your computer

• USB flash drive on your computer

You can use the KVM console to install an operating system or hypervisor on the server and to do the following:

• Access the BIOS setup menu by pressing F2 during bootup.

• Access the CIMC Configuration Utility by pressing F8 during bootup.

• Access the WebBIOS to configure RAID, by pressing the Ctrl and H keys during bootup.

Installing an Operating System or Hypervisor Using the KVM Console


Locate the operating system or hypervisor installation disk or disk image file.

Note


™ requires a customized image. To download the customized image, see

Downloading the Customized VMware vSphere Hypervisor Image, on page 79

.

Procedure

Step 1

Load the operating system or hypervisor installation disk into your CD/DVD drive, or copy the disk image files to your computer.

Step 2

If CIMC is not open, log into the CIMC GUI.

Step 3


Step 4


Step 5



Step 6

From the KVM console, click the Virtual Media tab.

72


OL-29450-01


Installing an Operating System or Hypervisor Using the KVM Console

OL-29450-01

Step 7

In the Virtual Media tab, map the virtual media using either of the following methods:

• Check the Mapped check box for the CD/DVD drive containing the operating system or hypervisor installation disk.

• Click Add Image, navigate to and select the operating system or hypervisor installation disk image, click Open to mount the disk image, and then check the Mapped check box for the mounted disk image.

Note

You must keep the Virtual Media tab open during the installation process. Closing the tab unmaps all virtual media.

Step 8

Set the boot order to make the virtual CD/DVD drive as the boot device.

To set the boot order, see

Configuring the Server Boot Order, on page 81

.

Step 9

Reboot the server.

When the server reboots, it begins the installation process from the virtual CD/DVD drive. Refer to the installation guide for the platform being installed to guide you through the rest of the installation process.

Step 10 If disk drives are not displayed after you install the operating system or hypervisor, you must install drivers.

See the appropriate operating system or hypervisor documentation for instructions on how to install drivers.

For instructions on how to install drivers on a Microsoft Windows operating system, see

Installing Drivers for the Microsoft Windows Server, on page 77

.

What to Do Next

After the installation is complete, reset the virtual media boot order to its original setting.


73


PXE Installation Servers

PXE Installation Servers

A Preboot Execution Environment (PXE) installation server allows a client to boot and install an operating system or hypervisor from a remote location. To use this method, a PXE environment must be configured and available on your VLAN, typically a dedicated provisioning VLAN. In addition, the server must be set to boot from the network. When the server boots, it sends a PXE request across the network. The PXE installation server acknowledges the request, and starts a sequence of events that installs the operating system or hypervisor on the server.

PXE servers can use installation disks, disk images, or scripts to install the operating system or hypervisor.

Proprietary disk images can also be used to install the platform, additional components, or applications.

Note

PXE installation is an efficient method for installing a platform on a large number of servers. However, considering that this method requires setting up a PXE environment, it might be easier to use another installation method.

Installing an Operating System or Hypervisor Using a PXE Installation Server


Verify that the server can be reached over a VLAN.

Note




.

Procedure

Step 1

Set the boot order to PXE.

Step 2

Reboot the server.

If a PXE install server is available on the VLAN, the installation process begins when the server reboots. PXE installations are typically automated and require no additional user input. Refer to the installation guide for the operating system or hypervisor being installed to guide you through the rest of the installation process.

What to Do Next

After the installation is complete, reset the LAN boot order to its original setting.

Host Image Mapping

The Host Image Mapping feature allows you to download, map, unmap, or delete a host image. Download a host image, such as Microsoft Windows, Linux, or VMware from a remote FTP or HTTP server onto the

74


OL-29450-01


Mapping the Host Image

CIMC internal repository, and then map the image onto the virtual drive of a USB controller in the E-Series

Server. After you map the image, set the boot order to make the virtual drive, in which the image is mounted, as the first boot device, and then reboot the server. The host image must have .iso or .img as the file extension.

The Host Image Mapping feature also allows you to download and mount a diagnostics image. The diagnostics image must have .diag as the file extension.



• Log into CIMC as a user with admin privileges.

• Obtain the host image file from the appropriate third-party.

Note




.

Note

If you start an image update while an update is already in process, both updates will fail.

Procedure

Step 1


Step 2

On the Server tab, click Host Image Mapping.

Figure 26: Host Image Mapping

OL-29450-01

Step 3

From the Host Image Mapping page, click Add Image.


75



The Download Image dialog box opens. Complete the following fields:

Name Description

Download Image From

drop-down list

The type of remote server on which the image is located. This can be one of the following:

• FTP

• HTTP

Note

Depending on the remote server that you select, the fields that display change.

FTP or HTTP Server IP Address field

The IP address of the remote FTP or HTTP server.

FTP or HTTP File Path field The path and filename of the remote FTP or HTTP server.

The path and filename can contain up to 80 characters.

• If you are installing a host image, that image must have .iso or

.img as the file extension.

• If you are installing a diagnostics image, that image must have

.diag as the file extension.

Username field

Password field

The username of the remote server.

The username can contain 1 to 20 characters.

Note

If the username is not configured, enter anonymous for the username and any character(s) for the password.

The password for the username.

The password can contain 1 to 20 characters.

Note


Step 4

Click Download.

The Host Image Mapping page opens. You can view the status of the image download in the Host Image

Mapping Status area. After the image is downloaded and processed successfully, refresh the page. After the page refreshes, the new image displays in the Image Information area.

Step 5

From the Image Information area, select the image to map, and then click Map Selected Image.

The image is mapped and mounted on the virtual drive of a USB controller. The virtual drive can be one of the following:

• HDD—Hard disk drive

• FDD—Floppy disk drive

• CD/DVD—Bootable CD-ROM or DVD drive

Step 6

Set the boot order to make the virtual drive in which the image is mounted as the first boot device.

76


OL-29450-01


Installing Drivers for the Microsoft Windows Server


Configuring the Server Boot Order, on page 81

.

Tip

To determine in which virtual drive the image is mounted, see the Host Image Update Status area in the Host Image Mapping page.

Step 7

Reboot the server.

Step 8

If the image contains an answer file, the operating system or hypervisor installation is automated and the image is installed. Otherwise, the installation wizard is displayed. Follow the wizard steps to install the image.

Step 9

If disk drives are not displayed after you install the operating system or hypervisor, you must install drivers.

See the appropriate operating system or hypervisor documentation for instructions on how to install drivers.

For instructions on how to install drivers on a Microsoft Windows operating system, see

Installing Drivers for the Microsoft Windows Server, on page 77

.

What to Do Next

• After the installation is complete, reset the virtual media boot order to its original setting.

• Unmap the host image. See

Unmapping the Host Image, on page 78

.

Installing Drivers for the Microsoft Windows Server

Note

If you purchased E-Series Server Option 1 (E-Series Server without a preinstalled operating system or hypervisor), and you installed your own version of the Microsoft Windows Server, you must install drivers.

The Microsoft Windows operating system requires that you install three drivers:

• On-Board Network Drivers for Windows 2008 R2

• LSI Drivers (On-Board Hardware RAID Controller) for Windows 2008 R2

• Intel Drivers for Windows 2008 R2

Note

Additional drivers are not needed for Windows 2012.

If you have purchased a 10-Gigabit add-on card, you must also install the 10G PCIe Network Drivers for

Windows 2008 R2.

Procedure

Step 1

Download the drivers from Cisco.com. See

Obtaining Software from Cisco Systems, on page 102

.

Step 2

Copy the driver files into a USB flash drive.

Step 3

Install your own version of Microsoft Windows Server.

During the installation process, you will be prompted for the LSI Drivers.

OL-29450-01


77


Unmapping the Host Image

Step 4

Plug the USB flash drive into the USB slot in the E-Series Server, and then install the LSI Drivers.

Step 5

After the Microsoft Windows Server installation is complete, install the On-Board Network Drivers (Broadcom) and the Intel Drivers.

Unmapping the Host Image


Log in to CIMC as a user with admin privileges.

Procedure

Step 1


Step 2



Step 3

Click Unmap Image.

The mapped image is unmounted from the virtual drive of the USB controller.

78


OL-29450-01


Basic Workflow for Downloading and Installing the VMware vSphere Hypervisor

Basic Workflow for Downloading and Installing the VMware vSphere Hypervisor

Caution

If you are using VMware FL-SRE-V-HOST license (equivalent to VMware vSphere Hypervisor

™

5.X), make sure that the RAM that you are using is 32GB or less. If the RAM is more than 32GB, you will get an error message, and you will not be able to apply the license. If you want to use 48GB RAM, upgrade your license to FL-SRE-V-HOSTVC.

• Download the customized VMware vSphere Hypervisor

™ image.

• Install the VMware vSphere Hypervisor image.

• Assign a static IP address to the VMware vSphere Hypervisor

™

.

• Download and install the vSphere Client.

Downloading the Customized VMware vSphere Hypervisor Image

Procedure

Step 1

Navigate to https://my.vmware.com/web/vmware/login .

The VMware login page appears.

Step 2

Enter your VMware credentials, and then click Log In.

If you do not have an account with VMware, click Register to create a free account.

Step 3

Under the Support Requests pane, click Knowledge Base.

Step 4

In the Search field located on the top right corner, enter ESXi-5.0.0-623860-custom-Cisco-2.0.1.6.iso, and then click Search.

Step 5

From the Search Results, click Download VMware View 5.1 to download the customized VMware vSpere

Hypervisor

™ image.

What to Do Next

Install the VMware vSpere Hypervisor

™ image. For installation instructions, see Mapping the Host Image .

Assigning a Static IP Address to the VMware vSphere Hypervisor

Use this procedure to assign a static IP address to the VMware vSphere Hypervisor

™

.


79 OL-29450-01


Assigning a Static IP Address to the VMware vSphere Hypervisor


• Download the customized VMware vSphere Hypervisor

™

VMware vSphere Hypervisor Image, on page 79

.

image. See

Downloading the Customized

Note

You must have an account with VMware to download the customized image.

• Install the image onto the E-Series Server. For installation instructions, see Mapping the Host Image .

Procedure

Step 1

In your web browser, enter the IP address that you configured to access CIMC during initial setup and then log into CIMC.

The CIMC Home page, which is the Server Summary page, appears.

Step 2



Step 3

From the KVM console, click the KVM tab, and then do the following to configure the IP address: a) Press F2 to access the VMware vSphere Hypervisor

™

The DCUI login page appears.

DCUI customization menu.

b) Log into the DCUI.

The System Customization page appears.

c) From the System Customization page, click Configure Management Network.

The Configure Management Network page appears, which has several menu options, including Network

Adapter. The Network Adapter menu option allows you to view the existing network adapters and activate them.

Note

By default, the network adapter, vmnic0, is activated. Make sure that it stays activated.

d) From the Configure Management Network page, click the IP Configuration menu option.

To assign a static IP address, do the following:

• In the IP Configuration dialog box, click the radio box to specify that a static IP address will be used.

• In the appropriate fields, enter the IP address, network mask, and the gateway IP address, and then press Enter. The Configure Management Network page appears.

• In the Configure Management Network page, click the ESC key. The Configure Management

Network Confirm dialog box appears.

• Enter y to accept the changes and restart the management network.

e) In the router configuration, add a route to the VMware vSphere Hypervisor

™ host IP address.

For example, if the host IP address is 192.168.1.25 and the ucse interface is ucse 2/0, add the following route:

ip route 192.168.1.25 255.255.255.255 ucse2/0

80


OL-29450-01


Downloading and Installing the vSphere Client

f) Install the vSphere Client. See

Downloading and Installing the vSphere Client, on page 81

. From the vSphere Client, use the host IP address to log into the VMware vSphere Hypervisor

™

.

Downloading and Installing the vSphere Client

Use this procedure to download and install the vSphere Client.


• Make sure that you have assigned a static IP address to VMware vSphere Hypervisor

™

. See

Assigning a Static IP Address to the VMware vSphere Hypervisor, on page 79

.

• Verify that you have network connectivity. To download the vSphere Client, connection to the Internet is required.

Note

The vSphere Client contains an online tutorial for first time users. It also contains embedded in-line getting started assistance, which allows you to set up your virtual infrastructure through an easy to use, step-by-step process. If you are an experienced user, you can choose to turn-off the getting started in-line assistance.

Procedure

Step 1

Go to https://hypervisor-ip-address. You are directed to the VMware website and the Welcome page opens.

Step 2

Click Download vSphere Client, and then click Run to download the vSphere Client. The VMware vSphere

Client is installed and a shortcut icon to the client appears on your desktop.

Step 3

Click the VMware vSphere Client icon to open the login window.

Step 4

To manage the VMware vSphere Hypervisor

™

, enter the IP address or hostname of the VMware vSphere

Hypervisor

Note

™ and the username and password, and then click Login. The vSphere Client GUI opens.


™ is root, which cannot be changed; and the default password is password. After you login, we recommend that you change the password.

Configuring the Server Boot Order

You can use the CIMC GUI or the BIOS setup menu to configure the server boot order.

Configuring the Server Boot Order Using the CIMC GUI


Log into CIMC as a user with admin privileges.


81 OL-29450-01


Procedure

Step 1


Step 2

On the Server tab, click BIOS.

Figure 28: BIOS


Step 3

In the Actions area, click Configure Boot Order.

82


OL-29450-01


The Configure Boot Order dialog box appears.

Figure 29: Configure Boot Order Dialog Box


Step 4

In the Configure Boot Order dialog box, complete the following fields as appropriate:

OL-29450-01


83



Name

Device Types table

Add >

< Remove

Boot Order table

Up

Down

Step 5

Click Apply.

Description

The server boot options. This can be the following:

• HDD—Hard disk drive. Contains the following options:

• Cypress

• PCI RAID Adapter

• Linux Virtual FDD/HDD

• FDD—Floppy disk drive. Contains the following option:

◦Linux Virtual Floppy

• CD/DVD—Bootable CD-ROM. Contains the following option:

◦Linux Virtual CD/DVD

• Network Devices (PXE)—PXE boot. Contains the following options:

◦Console or GE0

• Console—Applicable for the Cisco 2900 and Cisco

3900 series ISR G2.

• GE0—Applicable for the Cisco 4400 series ISR.

◦GE1

◦GE2

◦GE3—Applicable for double-wide E-Series Servers.

• Internal EFI Shell—Internal Extensible Firmware Interface.

Moves the selected device type to the Boot Order table.

Removes the selected device type from the Boot Order table.

Displays the device types from which this server can boot, in the order in which the boot will be attempted.

Moves the selected device type to a higher priority in the Boot Order table.

Moves the selected device type to a lower priority in the Boot Order table.

84


OL-29450-01


Configuring the Boot Order Using the BIOS Setup Menu

Additional device types may be appended to the actual boot order, depending on what devices you have connected to your server.

What to Do Next

• Reboot the server to boot with your new boot order.


Use this procedure if you want the server to boot from an external bootable device, such as an USB or an external CD ROM drive that is directly connected to the E-Series Server.

Procedure

Step 1


Step 2


Step 3



Step 4


Step 5

When prompted, press F2 during bootup to access the BIOS setup menu.

OL-29450-01


85



The Aptio Setup Utility appears, which provides the BIOS setup menu options.

Figure 30: BIOS Setup Menu

Step 6

Click the Boot tab.

Step 7

Scroll down to the bottom of the page below the Boot Options Priority area. The following boot option priorities are listed:

• Floppy Drive BBS Priorities

• Network Device BBS Priorities

• Hard Drive BBS Priorities

• CD/DVD ROM Drive BBS Priorities

Step 8

Use the Up or Down arrow keys on your keyboard to highlight the appropriate option.

Step 9

Press Enter to select the highlighted field.

Step 10 Choose the appropriate device as Boot Option 1.

Step 11 Press F4 to save changes and exit.

The Main tab of the BIOS setup displays the device that you configured as Boot Option 1.

86


OL-29450-01

C H A P T E R

9


This chapter provides procedures to configure an internal connection between the ISR G2 and the E-Series

Server and between the Cisco ISR 4451-X and the E-Series Server. It contains the following sections:

•

Configuring an Internal Connection Between the ISR G2 and the E-Series Server, page 87

•

Configuring an Internal Connection Between the Cisco ISR 4451-X and the E-Series Server, page 90

•

Understanding Network Interface Mapping, page 96

•

Determining the MAC Address in Microsoft Windows, Linux, and VMware vSphere Hypervisor , page

98

Configuring an Internal Connection Between the ISR G2 and the E-Series Server

Use this configuration if you want the traffic to your application or operating system to flow through the ISR

G2. To configure an internal connection between the ISR G2 and the E-Series Server, you must configure these IP addresses:

• For traffic to flow through the PCIe connection (see next figure), configure the following:

◦IP address of the router's internal PCIe interface that connects the router to the E-Series Server's

GE0 interface.

◦IP address of the E-Series Server's GE0 interface.

• For traffic to flow through the MGF connection (see next figure), configure the following:

◦IP address of the router's internal MGF VLAN interface.



87 OL-29450-01



The following figure shows the internal connection between the router and the E-Series Server.

Figure 31: Internal Connection Between the ISR G2 and the E-Series Server

Step 1

Step 2

Step 3

Step 4

Procedure


Router> enable


Purpose

Enters privileged EXEC mode on the host router.

Enter your password if prompted.


Router (config)# interface ucse slot/0 Enters the ucse interface configuration mode for the router’s PCIe slot/0 interface.

Enter one of the following commands:

• Router (config-if)# ip address

router-to-e-series-server-interface-ip-address subnet mask

The ip address command specifies the IP address of the router's internal PCIe interface that connects the router to the E-Series Server's GE0 interface. See figure above.

or

• Router (config-if)# ip unnumbered

type number



• number—Number of the interface on which the router has an assigned IP address.

Note

Caution


The ip unnumbered command creates a point-to-point interface between devices. Broadcasting is not supported.

88


OL-29450-01



Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

Step 11

Step 12

Step 13

Step 14

Step 15

Step 16

Step 17

Step 18



Purpose



Use the server’s operating system to configure the E-Series Server’s GE0 interface. See figure above.

—

Router (config)# interface ucse slot/1

Enters ucse interface configuration mode for the router’s MGF slot/1 VLAN interface. See figure above.

Router (config-if)# switchport mode trunk Puts the port into permanent trunking mode. The default configuration is access mode.

Router (config-if)# [switchport trunk

allowed vlan vlan-numbers]

(Optional) Allows trunking on the specified

VLANs.

• vlan-numbers—VLAN numbers on which to allow trunking.





Router (config)# interface vlan vlan-number Enters VLAN configuration mode for the specified VLAN number.


vlan-ip-address subnet-mask

Specifies the IP address for the VLAN. See figure above.

• vlan-ip-address—IP address of the VLAN.

• subnet-mask—Subnet mask to append to the IP address.






—

Router# show running-config Displays the running configuration of the router so that you can verify the address configurations.

This example shows how to configure an internal connection between the router and the E-Series Server.

OL-29450-01


89


Configuring an Internal Connection Between the Cisco ISR 4451-X and the E-Series Server

Note

The IP addresses in this configuration example are for reference only and might not be valid.

Router>

enable

Router#


Router(config)#


Router(config-if)#

ip address 10.0.0.1 255.0.0.0

Router(config-if)#

no shut

Router(config-if)#

end

Use the server

’s operating system to configure the E-Series Server’s GE0 interface

Router(config)#


Router(config-if)#

switchport mode trunk

Router(config-if)#

exit

Router#


Router(config)#

interface vlan 1

Router(config-if)#

ip address 20.0.0.1 255.255.255.0

Router(config-if)#

no shut

Router(config-if)#

end

Use the server

’s operating system to configure the E-Series Server’s GE1 interface.

Router#


Configuring an Internal Connection Between the Cisco ISR

4451-X and the E-Series Server

Use this configuration if you want the traffic to your application or operating system to flow through the Cisco

ISR 4451-X. To configure an internal connection between the Cisco ISR 4451-X and the E-Series Server, you must configure these IP addresses:

• For traffic to flow through the router's ucse slot/0/0 and the E-Series Server's internal GE0 interface (see next figure), configure the following:

◦IP address of the router's ucse slot/0/0 interface that connects the router to the E-Series Server's

GE0 interface.


• For traffic to flow through the router's ucse slot/0/1 and the E-Series Server's internal GE1 interface (see next figure), configure the following:

◦IP address of the router's ucse slot/0/1 interface.


90


OL-29450-01



The following figure shows the internal connection between the router and the E-Series Server.

Figure 32: Internal Connection Between the Cisco ISR 4451-X and the E-Series Server

OL-29450-01

Step 1

Step 2

Step 3

Step 4

Procedure


Router> enable


Purpose




Router (config)# interface ucse slot/0/0 Enters interface configuration mode for the router’s ucse slot/0/0 interface.


• Router (config-if)# ip address

router-to-e-series-server-interface-ip-address subnet-mask

Specify the IP address of the router's ucse slot 0/0 interface that connects the router to the E-Series

Server's GE0 interface. See figure above.

or

• Router (config-if)# ip unnumbered

type number



• number—Number of the interface on which the router has an assigned IP address.

Note

Caution


The ip unnumbered command creates a point-to-point interface between devices. Broadcasting is not supported.


91



Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

Step 11

Step 12



Purpose




—

Router (config)# interface ucse slot/0/1

Enters ucse interface configuration mode for the router’s ucse slot/0/1 interface. See figure above.






—


This example shows how to configure an internal connection between the router and the E-Series Server.

Note

The IP addresses in this configuration example are for reference only and might not be valid.

Router>

enable

Router#


Router(config)#


Router(config-if)#

ip address 10.0.0.1 255.0.0.0

Router(config-if)#

no shut

Router(config-if)#

end

Use the server's operating system to configure the E-Series Server's

GE0 interface.

Router(config)#


Router(config-if)#

ip address 11.0.0.1 255.255.255.0

Router(config-if)#

no shut

Router(config-if)#

end

Use the server's operating system to configure the E-Series Server's GE1 interface.

Router#


92


OL-29450-01


Creating an Ethernet Virtual Circuit Using the Native VLAN Between the E-Series Server and the Cisco ISR 4451-X

Creating an Ethernet Virtual Circuit Using the Native VLAN Between the

E-Series Server and the Cisco ISR 4451-X

Use this procedure if you have added the native VLAN to encapsulate and transport selected data either to the operating system installed on the E-Series Server, or to the virtual machines created on the installed hypervisor.


Configure an internal connection between the Cisco ISR 4451-X and the E-Series Server.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

Step 11

Step 12

Step 13


Router> enable


Purpose




Router (config)# interface ucse slot/0/0 Enters ucse interface configuration mode for the router’s ucse slot/0/0 interface.

Router (config-if)# service instance id

ethernet

Configures an Ethernet service instance on an interface and enters Ethernet service configuration mode.

Defines the encapsulation type.

Router (config-if-srv)# encapsulation

encapsulation-type vlan-id

Router (config-if-srv)# bridge-domain

bridge-id

Router (config-if-srv)# exit

Router (config-if)# interface BDI

bridge-id


bdi-interface-ip-address



Configures the bridge domain.

Exits Ethernet service configuration mode.

Enters the bridge domain interface.

Specifies the IP address of the BDI interface.


Returns to global configuration mode on the host router.

— Use the server’s operating system to configure the E-Series Server’s GE0 interface. See figure above.


OL-29450-01


93


Creating an Ethernet Virtual Circuit Using a Non-Native VLAN Between the E-Series Server and the Cisco ISR 4451-X

This example shows how to create an Ethernet Virtual Circuit using the native VLAN between the E-Series

Server and the Cisco ISR 4451-X.

Note

The IP addresses in this configuration example are for reference only.

Router>

enable

Router#


Router(config)#


Router(config-if)#

service instance 1 ethernet

Router(config-if-srv)#

encapsulation untagged


bridge-domain 1


exit

Router(config-if)#

interface BDI 1

Router(config-if)#

ip address 10.0.0.1 255.0.0.0

Router(config-if)#

no shut

Router(config-if)#

end

Use the server's operating system to configure the E-Series Server's GE0 interface.

Router#


Creating an Ethernet Virtual Circuit Using a Non-Native VLAN Between the

E-Series Server and the Cisco ISR 4451-X

Use this procedure if you have added a non-native VLAN to encapsulate and transport selected data either to the operating system installed on the E-Series Server, or to the virtual machines created on the installed hypervisor.


Configure an internal connection between the Cisco ISR 4451-X and the E-Series Server.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5


Router> enable


Purpose




Router (config)# interface ucse slot/0/0 Enters ucse interface configuration mode for the router’s ucse slot/0/0 interface.

Router (config-if)# no ip address Removes an IP address or disables IP processing.

Router (config-if)# no negotiation auto Disables automatic negotiation on the interface.

94


OL-29450-01


Creating an Ethernet Virtual Circuit Using a Non-Native VLAN Between the E-Series Server and the Cisco ISR 4451-X

Step 10

Step 11

Step 12

Step 13

Step 14

Step 15

Step 16

Step 17

Step 18

Step 19

Step 6

Step 7

Step 8

Step 9


Router (config-if)# switchport mode

trunk

Router (config-if)# service instance id

ethernet

Purpose

Puts the port into permanent trunking mode.

Configures an Ethernet service instance on an interface and enters Ethernet service configuration mode.

Defines the encapsulation type.

Router (config-if-srv)# encapsulation

dot1q encapsulation-type vlan-id


• Router (config-if-srv)# rewrite

egress tag push dot1q


• Router (config-if-srv)# rewrite

ingress tag pop 1 symmetric


• The rewrite egress tag push dot1q command specifies the encapsulation adjustment to be performed on a frame that is egressing a service instance.

• The rewrite ingress tag pop 1 symmetric command specifies the encapsulation adjustment to be performed on a frame that is ingressing a service instance.

Router (config-if-srv)# bridge-domain

bridge-id

Router (config-if-srv)# exit

Router (config-if)# interface BDI

bridge-id


bdi-interface-ip-address



Configures the bridge domain.

Exits Ethernet service configuration mode.

Enters the bridge domain interface.

Specifies the IP address of the BDI interface.


Returns to global configuration mode on the host router.

Use the server’s operating system to configure the E-Series Server’s NIC interface.

Router# ping server's-NIC-interface

—

Router# show arp

Shows if connection is established with the

E-Series Server’s NIC interface.

Displays the Access Resolution Protocol (ARP).

Router# show bridge-domain bridge-id Displays bridge domain information.

This example shows how to create an Ethernet Virtual Circuit using a non-native VLAN between the E-Series

Server and the Cisco ISR 4451-X.

OL-29450-01


95


Understanding Network Interface Mapping

Note

The IP addresses in this configuration example are for reference only.

Router>

enable

Router#


Router(config)#


Router(config-if)#

no ip address

Router(config-if)#

no negotiation auto

Router(config-if)#

switchport mode trunk

Router(config-if)#

service instance 10 ethernet


encapsulation dot1q 10


rewrite egress tag push dot1q 10


bridge-domain 10


exit

Router(config-if)#

interface BDI10

Router(config-if)#

ip address 192.168.1.1 255.255.255.0

Router(config-if)#

no shut

Router(config-if)#

end

Use the server

’s operating system to configure the E-Series Server’s NIC interface.

Router#

ping 192.168.1.2



!!!!!


Router#

show arp

Protocol Address

Internet 192.168.1.1

Internet 192.168.1.2

Age (min)

-

1

Hardware Addr

0022.bdfb.2783

0022.bde6.07b4

Type

ARPA

ARPA

Interface

BDI10

BDI10

Router#

show bridge-domain 10

Bridge-domain 10 (2 ports in all)

State: UP Mac learning: Enabled

Aging-Timer: 300 second(s)

BDI10 (up) ucse2/0/0 service instance 10

MAC address Policy Tag Age Pseudoport

0022.BDE6.07B4 forward dynamic 246 ucse2/0/0.EFP10

0022.BDFB.2783 to_bdi static 0 BDI10

Note

For additional details about the rewrite commands, see http://www.cisco.com/en/US/docs/ios-xml/ios/ cether/command/ce-cr-book.html

.


This section shows you how to determine the network interface mapping for the following devices:

• E-Series Server's Console, GE1, GE2, and GE3 interfaces—ISR G2

• E-Series Server's GE0, GE1, GE2, and GE3 interfaces—Cisco ISR 4451-X

• NetXtreme II 1 Gigabit Server (PCIe Card)

• NetXtreme II 10 Gigabit Server (PCIe Card)

96


OL-29450-01



Determining Network Interface Mapping for the E-Series Server's Console, GE1, GE2, and GE3 Interfaces—ISR

G2

You can determine the port numbering of the E-Series Server by looking at the MAC addresses of the network interfaces. Note the following:

• Lowest numbered MAC address corresponds to the router's Console interface.

• Second lowest MAC address corresponds to the E-Series Server's GE1 interface.

• Third lowest MAC address corresponds to the E-Series Server's GE2 interface.

• Fourth lowest MAC address corresponds to the E-Series Server's GE3 interface.

Note

To determine the MAC address of an interface, see the

Determining the MAC Address in Microsoft

Windows, Linux, and VMware vSphere Hypervisor , on page 98

section, or the appropriate platform documentation.

Determining Network Interface Mapping for the E-Series Server's GE0, GE1, GE2, and GE3 Interfaces—Cisco

ISR 4451-X

You can determine the port numbering of the E-Series Server by looking at the MAC addresses of the network interfaces. Note the following:

• Lowest numbered MAC address corresponds to the E-Series Server's GE0 interface.

• Second lowest MAC address corresponds to the E-Series Server's GE1 interface.

• Third lowest MAC address corresponds to the E-Series Server's GE2 interface.

• Fourth lowest MAC address corresponds to the E-Series Server's GE3 interface.

Note

To determine the MAC address of an interface, see the

Determining the MAC Address in Microsoft

Windows, Linux, and VMware vSphere Hypervisor , on page 98

section, or the appropriate platform documentation.

Determining the Interface Name and Port Mapping for the NetXtreme II 1 Gigabit Server

To determine which interface name maps to which port number in the NetXtreme II 1 Gigabit Server (PCIe card), do the following:

1

Connect the PCIe card's port 0 to an external network device using a network cable.

2

From the host operating system, check the status of the interface to determine which interface is connected.

3

Repeat Step 2 for ports 1, 2, and 3.

Note

For information about how to determine the status of the interface, see the appropriate operating system documentation.

OL-29450-01


97


Determining the MAC Address in Microsoft Windows, Linux, and VMware vSphere Hypervisor

Determining the Interface Name and Port Mapping for the NetXtreme II 10 Gigabit Server

Note

Only one port is enabled in the NetXtreme II 10 Gigabit Server (PCIe card).

To determine which interface name maps to which port number in the NetXtreme II 10 Gigabit Server (PCIe card), do the following:

1

Connect the PCIe card's port 0 to an external network device using a network cable.

2

From the host operating system, check the status of the interface to determine which interface is connected.

Note

For information about how to determine the status of the interface, see the appropriate operating system documentation.


This section shows you how to determine the MAC addresses in Microsoft Windows, Linux, and VMware vSphere Hypervisor

™

.

Determining the MAC Address in the Microsoft Windows Operating System

To determine the MAC address of an interface in the Microsoft Windows operating systems, open a command window, and then enter the ipconfig /all command.

Determining the MAC Address in the Linux Operating System

To determine the MAC address of an interface in the Linux operating systems, open a terminal window, and then enter the ifconfig -a command to display the MAC address of all interfaces or ifconfig interface-name to display the MAC address of a particular interface.

Determining the MAC Address in the VMware vSphere Hypervisor

To determine the MAC address of an interface in the VMware vSphere Hypervisor

™

, do the following:

1

In your web browser, enter the IP address that you configured to access CIMC during initial setup and then log into CIMC.

The CIMC Home page, which is the Server Summary page, appears.

2



3

From the KVM Console, click the KVM tab, and then do the following:

• Press F2 to access the VMware vSphere Hypervisor

™ page appears.

DCUI customization menu. The DCUI login

• Log into the DCUI. The System Customization page appears.

98


OL-29450-01



• From the System Customization page, click Configure Management Network.

The Configure Management Network page appears, which has several menu options, including

Network Adapter. The Network Adapter menu option allows you to view the MAC address of the interfaces.

OL-29450-01


99



100


OL-29450-01

C H A P T E R

10

BIOS


•

BIOS Overview, page 101

•

Determining the Current BIOS Version, page 102

•

Options for Obtaining Firmware from Cisco Systems, page 102

•

Obtaining Software from Cisco Systems, page 102

•

Installing the BIOS Firmware, page 103

•

Accessing the BIOS Setup Menu, page 106

•

Changing Configuration Using the BIOS Setup Menu, page 109

BIOS Overview

BIOS initializes the hardware in the system. After it initializes the CPU, other chips on the motherboard get initialized. BIOS discovers bootable devices in the system and boots them in the provided sequence. It boots the operating system and configures the hardware for the operating system to use. BIOS manageability features allow you to interact with the hardware and use it. In addition, BIOS provides options to configure the system, manage firmware, and create BIOS error reports.

BIOS provides the following features:

• Option ROM to provide PCI connected device boot

• Manage virtual and physical boot devices: SCSI, FC, network, and USB

• Processor Settings

• Memory Settings

• Power Management (C-states)

BIOS supports the following standard PC compatible functionality:

• ACPI 3.0, SMBIOS 2.5, WHEA, and USB 2.0

• EFI Shell boot


101 OL-29450-01

BIOS

Determining the Current BIOS Version

• EFI native operating system boot

Determining the Current BIOS Version

To view the current version and build number of the BIOS, press F2 during server bootup. The BIOS setup

utility appears. The listing on the Main page displays the current version and build number of the BIOS.

Options for Obtaining Firmware from Cisco Systems

• We recommend that you use the HUU ISO file to upgrade all firmware components, which includes the

BIOS and CIMC firmware. For detailed instructions for upgrading the firmware using the HUU, see the

"Upgrading the Firmware Using the HUU" section in the Host Upgrade Utility User Guide for Cisco

UCS E-Series Servers at http://www.cisco.com/en/US/products/ps12629/prod_installation_guides_ list.html

.

Note

The HUU is supported on CIMC, release 2.1.0 and later releases.

• If you choose to upgrade the CIMC and BIOS firmware manually, see

Obtaining Software from Cisco

Systems, on page 102

.

Obtaining Software from Cisco Systems

Use this procedure to download drivers, BIOS and CIMC firmware, and the diagnostics image.

Procedure

Step 1

Navigate to http://www.cisco.com/ .

Step 2

If you are not already logged in, click Log In at the top right-hand edge of the page and log in using your

Cisco.com credentials.

Step 3

In the menu bar at the top, click Support.

A roll-down menu appears.

Step 4

From the Downloads (center) pane, click All Downloads (located at the bottom right corner).

The Download Software page appears.

Step 5

From the left pane, click Products.

Step 6

From the center pane, click Unified Computing and Servers.

Step 7

From the right pane, click Cisco UCS E-Series Software.

Step 8

From the right pane, click the name of the server model for which you want to download the software.

The Download Software page appears with the following categories.

• Unified Computing System (UCSE) Server Drivers—Contains drivers.

102


OL-29450-01

BIOS

Installing the BIOS Firmware

• Unified Computing System (UCSE) Server Firmware—Contains the Host Upgrade Utility and the

BIOS and CIMC firmware images.

• Unified Computing System (UCSE) Utilites—Contains the diagnostics image.

Step 9

Click the appropriate software category link.

Step 10 Click the Download button associated with software image that you want to download.

The End User License Agreement dialog box appears.

Step 11 (Optional) To download multiple software images, do the following: a) Click the Add to cart button associated with the software images that you want to download.

b) Click the Download Cart button located on the top right .

All the images that you added to the cart display.

c) Click the Download All button located at the bottom right corner to download all the images.

The End User License Agreement dialog box appears.

Step 12 Click Accept License Agreement.

Step 13 Do one of the following as appropriate:

• Save the software image file to a local drive.

• If you plan to install the software image from a TFTP server, copy the file to the TFTP server that you want to use.

The server must have read permission for the destination folder on the TFTP server.

What to Do Next

Install the software image.

Installing the BIOS Firmware

You can install the BIOS firmware through the browser or from a TFTP server.

Installing the BIOS Firmware Through the Browser

Note

To avoid potential problems, we strongly recommend that you use the Host Upgrade Utility (HUU), which upgrades the CIMC, BIOS, and other firmware components to compatible levels. For detailed information about this utility, see the Host Upgrade Utility User Guide for Cisco UCS E-Series Servers at http:// www.cisco.com/en/US/products/ps12629/prod_installation_guides_list.html

. This guide also provides information about the compatible HUU, CIMC, and BIOS software releases.

If you choose to upgrade the CIMC and BIOS firmware manually—instead of using the HUU—you must update the CIMC firmware first, and then the BIOS firmware. Do not install the new BIOS firmware until after you have activated the compatible CIMC firmware or the server will not boot.


103 OL-29450-01

BIOS

Installing the BIOS Firmware Through the Browser


• Log in to CIMC as a user with admin privileges.

• Obtain the CIMC firmware file from Cisco Systems. See

Obtaining Software from Cisco Systems, on

page 102 .

• Unzip the proper upgrade file to your local machine.

Procedure

Step 1


Step 2


Figure 33: BIOS

Step 3

In the Firmware Actions area, click Install BIOS Firmware through Browser Client.

Step 4

In the Install BIOS Firmware dialog box, click Browse and use the Choose File dialog box to select the file to install.

Step 5

Click Install Firmware.

The BIOS is downloaded, the host is powered off, the BIOS is upgraded, and then the host is powered on.

104


OL-29450-01

BIOS

Installing the BIOS Firmware from a TFTP Server

Installing the BIOS Firmware from a TFTP Server

Note

To avoid potential problems, we strongly recommend that you use the Host Upgrade Utility (HUU), which upgrades the CIMC, BIOS, and other firmware components to compatible levels. For detailed information about this utility, see the Host Upgrade Utility User Guide for Cisco UCS E-Series Servers at http:// www.cisco.com/en/US/products/ps12629/prod_installation_guides_list.html

. This guide also provides information about the compatible HUU, CIMC, and BIOS software releases.

If you choose to upgrade the CIMC and BIOS firmware manually—instead of using the HUU—you must update the CIMC firmware first, and then the BIOS firmware. Do not install the new BIOS firmware until after you have activated the compatible CIMC firmware or the server will not boot.



• Obtain the CIMC firmware file from Cisco Systems. See

Obtaining Software from Cisco Systems, on

page 102 .

• Unzip the proper upgrade file on your TFTP server.

Procedure

Step 1


Step 2


Figure 34: BIOS

OL-29450-01

Step 3

In the Firmware Actions area, click Install BIOS Firmware from TFTP Server.

Step 4

In the Install BIOS Firmware dialog box, complete the following fields:


105

BIOS

Accessing the BIOS Setup Menu

Name

TFTP Server IP Address field

Description

The IP address of the TFTP server on which the BIOS firmware image resides.

Image Path and Filename field The BIOS firmware image filename on the server. When you enter this name, include the relative path for the image file from the top of the

TFTP tree to the file location.

Step 5

Click Install Firmware.

The BIOS is downloaded, the host is powered off, the BIOS is upgraded, and then the host is powered on.

Accessing the BIOS Setup Menu

You can access the BIOS Setup menu in two ways:

• Through CIMC from the KVM console.

• Through a console that is physically attached to the E-Series Server.

Accessing the BIOS Setup Menu from the KVM Console

Procedure

Step 1


Step 2


Step 3



Step 4


Step 5

To access the BIOS setup menu, press F2 during bootup.

106


OL-29450-01

BIOS




OL-29450-01

The following table provides information about the BIOS setup menu tabs.

Tabs Description

Main tab Provides the following:

• General information about the BIOS version, system memory, and access level

• Settings to define the system date, time, and language

Advanced tab Allows you to do the following:

• Enable or disable boot option for legacy network devices and legacy mass storage devices with option ROM

• Configure PCI, PCI-X, and PCI express, trusted computing settings, and WHEA configuration settings

• Configure CPU, thermal, USB, and system IO chip parameters

• Configure runtime error logging support setup options

• Configure console redirection to the serial port


107

BIOS


Chipset tab

Server Mgmt tab

Boot tab

Security tab

Save & Exit tab

Allows you to do the following:

• Define North Bridge, South Bridge, and ME subsystem parameters

Provides the self test status of CIMC and allows you to do the following:

• Enable or disable interfaces to communicate with CIMC

• Enable or disable FRB-2 timer

• Configure the FRB-2 timer expiration value and configure how the system responds when the FRB-2 timer expires

• Enable or disable the OS watchdog timer

• Log the report returned by the CIMC self test command

• Change the system event log configuration


• Configure the time in seconds the system should wait for the setup activation key

• Enable or disable the keyboard NumLock keys

• Define boot order rules

• Configure Gate A20 parameters

• Enable or disable CSM support

• Define boot order for devices in the following groups: hard disk drives, network devices, CDROM, DVD, and floppy drives


• Define or change the BIOS administrator and user passwords

Provides options to do the following:

• Save changes, discard changes, or restore the configuration to its default settings

108


OL-29450-01

BIOS

Changing Configuration Using the BIOS Setup Menu


Use this procedure to change the BIOS settings for your server. Detailed instructions are also printed on the

BIOS pages.

Procedure

Step 1


Step 2


Step 3



Step 4


Step 5

To access the BIOS setup menu, press F2 during bootup.



OL-29450-01

Step 6

To navigate between menu items, use the right or left arrow keys on your keyboard.

Step 7

To modify a field, do the following: a) Use the Up or Down arrow keys on your keyboard to highlight the field to be modified.

b) Press Enter to select the highlighted field, and then change the value in the field.

c) Do one of the following:


109


• To save changes and exit the BIOS setup, press F4.

• To exit without saving changes, press Esc.

Step 8

To enable or disable a field, press the space bar on your keyboard.

BIOS

110


OL-29450-01

C H A P T E R

11

Recovering from Corrupt CIMC Firmware


•

CIMC Firmware Image Overview, page 111

•

Recovering from a Corrupted CIMC Firmware Image, page 111

•

Recovering from a Faulty SD Card, page 113

•

Recovering from a Corrupted File System, page 115

CIMC Firmware Image Overview

If you have problems booting the E-Series Server, it could be that the CIMC firmware image is corrupted, or the SD card is faulty, or the file system is corrupted, or the CIMC firmware installation did not complete successfully. To recover from a corrupt CIMC firmware image, do one of the following as appropriate:

Important

Due to security considerations, the boot backup command is disabled.

• If the CIMC firmware image is corrupted, see

Recovering from a Corrupted CIMC Firmware Image,

on page 111 .

• If the SD card is faulty, see Recovering from a Faulty SD Card .

• If the file system is corrupted, see

Recovering from a Corrupted File System, on page 115

.

• If the CIMC firmware installation did not complete successfully, reinstall the CIMC firmware.

Recovering from a Corrupted CIMC Firmware Image


• Connect the E-Series Server to your PC. Depending on the type of E-Series Server, do one of the following as appropriate:


111 OL-29450-01


Recovering from a Corrupted CIMC Firmware Image

• Double-wide—Connect one end of the serial cable to the E-Series Server's serial port and the other end to your PC.

• Single-wide—First, connect a KVM connector to the E-Series Server's KVM port; and then connect one end of a serial cable to the DB9 port of the KVM connector and the other end to your PC.

• Attach an Ethernet cable into the Management (dedicated) port of the E-Series Server.

• To view the serial output, start the Hyper Terminal or Minicom as appropriate. Do one of the following:

• Microsoft Windows—Start Hyper Terminal.

• Linux—Start Minicom.

• Make sure that the communications settings are configured as: 9600 baud, 8 bits, No parity, and 1 stop bit.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7


Router# hw-module sm slot

oir-stop


oir-start

***

Purpose

Shuts down the power to the specified E-Series Server.

Note

The Cisco 2900 series ISR G2 does not support OIR of the E-Series Servers. To avoid damaging the router, turn off the electrical power on the router and disconnect network cables before inserting or removing the E-Series Server from the Cisco 2900

ISR G2.

Restarts the specified E-Series Server.

Note


ISR G2.

From the Hyper Terminal or Minicom, enter the *** command to enter the bootloader prompt.

ucse-cimc > boot current

recovery

Boots the E-Series Server from the current image.

Recovery-shell #

dedicated-interface

management-interface-ip-address netmask gateway-ip-address

Specifies the IP address, subnet mask, and the gateway IP address of the E-Series Server's Management (dedicated) interface.

Recovery-shell # ping

tftp-ip-address

Pings the remote TFTP server in which the CIMC firmware is located to verify network connectivity.

Recovery-shell # update

tftp-ip-address image-filename

Installs the CIMC firmware image, which is located on a remote tftp server.

112


OL-29450-01


Recovering from a Faulty SD Card

Step 8


Recovery-shell # reboot

Purpose

Reboots CIMC.

This example recovers the CIMC firmware image:

Router#

hw-module subslot 2/0 stop

Router#

hw-module subslot 2/0 start

***

ucse-cimc >

boot current recovery

recovery-shell#

dedicated-interface 192.168.0.138 255.255.255.0 192.168.0.1

Network configuration:

IP config: addr: 192.168.0.138 Mask: 255.255.255.0

Gateway: 192.168.0.1

recovery-shell#

ping 10.20.34.56

PING 10.20.34.56 (10.20.34.56): 56 data bytes

64 bytes from 10.20.34.56: seq=0 ttl=60 time=10.000 ms


--- 10.20.34.56 ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max = 0.000/1.000/10.000 ms recovery-shell#

update 10.20.34.56 update_pkg-cimc.combined.bin

downloading firmware image "update_pkg-cimc.combined.bin" from " 10.20.34.56 " download firmware image done, size in bytes: 22384144 installing firmware image, please wait ...

activating installed image done

Stage: NONE

Status: SUCCESS

Error: Success recovery-shell#

reboot


If you have problems booting the E-Series Server, it could be because the SD card is faulty. Use this procedure to recover the CIMC firmware image on a new SD card.










113 OL-29450-01




Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9



oir-stop

Purpose


Note

The Cisco 2900 series ISR G2 does not support

OIR of the E-Series Servers. To avoid damaging the router, turn off the electrical power on the router and disconnect network cables before inserting or removing the E-Series Server from the Cisco 2900 ISR G2.

Replaces the faulty SD card.

Remove the faulty SD card and insert a new one.


oir-start

***


Note

The Cisco 2900 series ISR G2 does not support

OIR of the E-Series Servers. To avoid damaging the router, turn off the electrical power on the router and disconnect network cables before inserting or removing the E-Series Server from the Cisco 2900 ISR G2.



recovery

Recovery-shell #




tftp-ip-address







Recovery-shell # reboot Reboots CIMC.

This example recovers the CIMC firmware from the current image:

Router#

hw-module subslot 2/0 stop

Router#

hw-module subslot 2/0 start

***

ucse-cimc >


recovery-shell#

dedicated-interface 192.168.0.138 255.255.255.0 192.168.0.1

Network configuration:

114


OL-29450-01


Recovering from a Corrupted File System

IP config: addr: 192.168.0.138 Mask: 255.255.255.0

Gateway: 192.168.0.1

recovery-shell#

ping 10.20.34.56

PING 10.20.34.56 (10.20.34.56): 56 data bytes



--- 10.20.34.56 ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max = 0.000/1.000/10.000 ms recovery-shell#

update 10.20.34.56 update_pkg-cimc.combined.bin

downloading firmware image "update_pkg-cimc.combined.bin" from " 10.20.34.56 " download firmware image done, size in bytes: 22384144 installing firmware image, please wait ...

activating installed image done

Stage: NONE

Status: SUCCESS

Error: Success recovery-shell#

reboot


Use this procedure if you see the following error message in the CIMC boot log files.

UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY










Procedure

Step 1



oir-stop

Purpose



115 OL-29450-01



Step 2

Step 3

Step 4

Step 5



oir-start

***

Purpose

Note


ISR G2.


Note


ISR G2.



recovery


To check the file system of the specified partition and recover the corrupted file system, enter these commands.

1

Recovery-shell # fs-check [p3 | p4]

Note

You can only use p3 and p4 partitions with this command. Use this command on the partition that is corrupted. The corrupted partition is the one that displays the run fsk error message during

CIMC bootup.

2

Do the following:

• If the command output displays clean, it indicates that the corrupted files are recovered. Enter the

reboot command to reboot CIMC.

Note

Skip the steps that follow.

• If the command output does not display clean, proceed to Step 6.

Step 6

(Optional) If the fs-check [p3 | p4] command does not recover the corrupted file system, and the output does not display clean, enter these commands to format the partitions.

1

Recovery-shell # sd-card format [p3 | p4]

Formats the specified corrupted partition on the SD card.

Note

The corrupted partition is the one that displays the run fsk error message during CIMC bootup.

2


Reboots CIMC.

Note

Note

Skip the steps that follow.

When the p3 partition is formatted, the CIMC configuration is lost.

116


OL-29450-01



Step 7

Step 8

Step 9

Step 10

Step 11


(Optional) If the sd-card format

[p3 | p4] command does not recover the corrupted file system, enter these commands to partition and format the SD card.

1

Recovery-shell # sd-card partition

2

Creates partitions on the SD card.

Recovery-shell # sd-card format p3

Formats the p3 partition on the SD card.

3

Recovery-shell # sd-card format p4

Formats the p4 partition on the SD card.

4


Reboots CIMC.

5

(Optional) Recovery-shell # sd-partition show

Displays the current partition on the SD card.

Note

When you partition the SD card, the contents of the

SD card, such as, the configuration and ISO file, are lost.

Recovery-shell #





tftp-ip-address





Recovery-shell # reboot Reboots CIMC.

This example recovers the CIMC firmware from the current image using the fs-check p3 command:

Router#

hw-module sm 2 oir-stop

Router#

hw-module sm 2 oir-start

***

ucse-cimc >


recovery-shell#

fs-check p3

e2fsck 1.41.14 (22-Dec-2010)

/dev/mmcblk0p3: recovering journal

/dev/mmcblk0p3: clean, 429/7840 files, 3331/31296 blocks recovery-shell#

fs-check p4

e2fsck 1.41.14 (22-Dec-2010)

/dev/mmcblk0p4: clean, 51/506912 files, 1880262/2025296 blocks recovery-shell#

reboot

OL-29450-01


117



118


OL-29450-01

C H A P T E R

12

Diagnostic Tests


•

Diagnostic Tests Overview, page 119

•

Mapping the Diagnostics Image to the Host, page 120

•

Running Diagnostic Tests, page 122

Diagnostic Tests Overview

Diagnostics is a standalone utility that runs on the E-Series Server independent of the operating system or applications running on the server. If you experience problems with the E-Series Server, you can use diagnostics tests to run a preliminary check and isolate the problem. Diagnostic tests can be executed on the server CPU, memory, and block devices. Block devices include hard drive, USB drive, and SD cards.

If the diagnostic tests pass successfully, it indicates that there is no problem with the server CPU, memory, or block devices. The problem could be with some other hardware component or with the software configuration.

Open a service request with Cisco Technical Assistance Center (TAC) at: http://www.cisco.com/cisco/web/ support/index.html

to isolate the problem.

If the diagnostic tests fail, open a service request with Cisco TAC for further assistance.

Caution

Diagnostic tests are non-destructive, but if there is a power or equipment failure when the tests are running, there is a possibility that the disk data might get corrupted. We highly recommend that you backup the data before running these tests.

Basic Workflow for Executing Diagnostic Tests

1

Backup data.

2

The diagnostics image is pre-installed on the E-Series Server at the time of purchase. You can also choose to download the most current diagnostics image from a specified FTP or HTTP server onto the CIMC internal repository.

3

Mount the diagnostics image onto the HDD virtual drive of a USB controller.


119 OL-29450-01


Mapping the Diagnostics Image to the Host

4

Set the boot order to make EFI Shell as the first boot device.

5

Reboot the server.

6

Run diagnostic tests from the EFI Shell.

7

Reset the virtual media boot order to its original setting.



• Backup data.


• The diagnostics image is pre-installed on the E-Series Server at the time of purchase. You can also choose to download the most current diagnostics image from a specified FTP or HTTP server onto the

CIMC internal repository. See

Obtaining Software from Cisco Systems

.

Note

If you start an image update while an update is already in process, both updates will fail.

Procedure

Step 1


Step 2



Step 3

From the Host Image Mapping page, click Add Image.

The Download Image dialog box opens. Complete the following fields:

120


OL-29450-01



Name

Download Image From

drop-down list

Description

The type of remote server on which the image is located. This can be one of the following:

• FTP

• HTTP

Note

Depending on the remote server that you select, the fields that display change.

FTP or HTTP Server IP Address field

The IP address of the remote FTP or HTTP server.

FTP or HTTP File Path field The path and filename of the remote FTP or HTTP server.

The path and filename can contain up to 80 characters.

• If you are installing a host image, that image must have .iso or

.img as the file extension.

• If you are installing a diagnostics image, that image must have

.diag as the file extension.

Username field

Password field

The username of the remote server.

The username can contain 1 to 20 characters.

Note


The password for the username.

The password can contain 1 to 20 characters.

Note


Step 4

Click Download.

The Host Image Mapping page opens. You can view the status of the image download in the Host Image

Mapping Status area. After the image is downloaded and processed successfully, refresh the page. After the page refreshes, the new image displays in the Image Information area.

Step 5

From the Image Information area, select the image to map, and then click Map Selected Image.

The image is mapped and mounted on the virtual drive of a USB controller.

Step 6

Set the boot order to make EFI Shell as the first boot device.



.

Step 7

Reboot the server.

The EFI Shell appears.

OL-29450-01


121


Running Diagnostic Tests

What to Do Next

Run diagnostic tests.


From the EFI shell, use the following procedure to run diagnostic tests.


• Back up data. All tests are non-destructive, but if there is power or equipment failure when the tests are running, there is a possibility that the disk data might get corrupted. We highly recommend that you back up data before executing these tests.

• Use the CIMC CLI or the CIMC GUI to download and map the diagnostics image onto the HDD virtual drive of the USB controller.

• Reboot the server. The EFI shell displays.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5


Shell > dir

virtual-media-drive-name:

Displays all the file packages that exist in the specified virtual media drive. The drive name starts with fs0 and can be fs0, fs1, fs2, and so on.

Note

Make sure that you add a colon after the virtual media drive name. For example, dir fs1:

Shell >

virtual-media-drive-name:

Enters the virtual media drive in which the diagnostic file is located.

Virtual Media Drive :\> cp

package-file-name dsh.pkg

Copies the package file for which you are running diagnostics into the diagnostics shell package file.

Virtual Media Drive :\>

dsh

Server: SRV > run all

Enters the Diagnostics Shell. At the confirmation prompt, answer

y.

Executes all available diagnostic tests and displays the progress and status of the tests. Diagnostic tests are run on the server CPU, memory, and block devices. Block devices include hard drive, USB drive, and SD cards.

To execute a specific diagnostic test on the server, use the run

test-name command where test-name can be one of the following:

• cpux64—CPU diagnostic test.

• diskx64—Block devices diagnostic test. Block devices include hard drive, USB drive, and SD cards.

• memoryx64—Memory diagnostic test.

122


OL-29450-01



OL-29450-01

Step 6

Step 7

Step 8

Step 9


(Optional) Server: SRV >

results

(Optional) Server: SRV >

show

Server: SRV > exit

Purpose

Note

Diagnostic tests can run for approximately 10 minutes.

Displays a summary of the diagnostic test with Passed or Failed test status.

Note

The summary report indicates the number of tests that failed and passed. It does not provide information about which tests failed or passed. To determine which tests failed and passed, see the output of the run all command.

Displays a list of global parameters and diagnostic test modules that were administered on the server.

Exits from Diagnostic Shell.

Open a service request with

Cisco TAC.

If the diagnostic tests pass successfully, it indicates that there is no problem with the server CPU, memory, or block devices. The problem could be with some other hardware component or with the software configuration. Open a service request with Cisco TAC to isolate the problem.

If the diagnostic tests fail, open a service request with Cisco TAC for further assistance.

This example runs all diagnostic tests:

Shell >

dir fs1:

06/27/12

06/27/12

06/25/12

06/27/12

07:48p

08:03p

06:00p

08:04p

1,435,424 Dsh.efi

10,036 dsh-e140d.pkg

10,140 dsh-e140s.pkg

10,042 dsh-e160d.pkg

4 File(s) 1,465,642 bytes

Shell >

fs1:

fs1:\>

cp dsh-e140d.pkg dsh.pkg

copying fs0:\OBD\dsh-e140d.pkg -> fs0:\OBD\dsh.pkg

- [ok] fs1:\>

dsh

Diagnostics is a standalone utility that runs on the server module independent of the operating system or applications running on the module.All tests are non-destructive, but there is a possibility of disk datacorruption during power or equipment failure when the tests are in progress. Therefore, before executing these tests, we highly recommend that you backup the data.

For questions or concerns with this utility, please open a Service Request with Cisco TAC at http://www.cisco.com/cisco/web/support/index.html

(Y)es to continue test. (N)o to exit(y/n):

Y

Cisco Diagnostics Shell 1.03(0.3) Thu 06/28/-16:35:[email protected]

UCS-E140D-M1/K9:SRV>

Server: SRV >

run all

Server: SRV >

results

Test Name

Test Status

: all

: Passed

Failed/Run History : 0/17

Start Time : 06/27/12 14:38:19

End Time

Diag Version

: 06/27/12 14:43:36

: 1.03(0.3) Mon 04/02/-17:07:[email protected]


123


Board S/N

Server: SRV >

show

Server: SRV >

exit

: FOC160724BY

What to Do Next

Reset the virtual media boot order to its original setting.


124


OL-29450-01

C H A P T E R

13

Cisco IOS Software Command Reference—ISR

G2

This chapter provides the new Cisco IOS commands that were introduced for the E-Series Servers installed in the ISR G2.

Note

The Cisco IOS commands are sometimes updated after original publication; therefore, for updated content, review the Cisco IOS Interface and Hardware Component Command Reference at http://www.cisco.com/ en/US/docs/ios-xml/ios/interface/command/ir-cr-book.html

.


•

imc ip address default-gateway, page 125

•

imc ip address dhcp, page 126

•

imc vlan, page 127

•

ucse cmos-reset, page 128

•

ucse password-reset, page 128

•

ucse session, page 129

•

ucse shutdown, page 130

•

ucse statistics, page 130

•

ucse status, page 131

•

ucse stop, page 132

imc ip address default-gateway

To configure a static IP address for CIMC and the IP address of the default gateway router that CIMC must use, use the imc ip address default-gateway command from interface configuration mode .

imc ip address i ip_address subnet_mask default-gateway gateway_address


125 OL-29450-01


imc ip address dhcp

no imc ip address i p_address subnet_mask default-gateway gateway_address

Syntax Description

ip_address subnet_mask gateway_address

IP address of CIMC.

Subnet mask to append to the IP address; must be in the same subnet as the host router.

IP address of the default gateway router.

Command Modes

Interface configuration mode.

Command History

Release

15.2(4)M

Modification

This command was introduced.

Usage Guidelines

Use this command from interface configuration mode:

Router(config)# interface ucse

slot/port

If you do not enable DHCP, you must specify a static IP address and subnet mask.

The following example shows how to configure a static IP address for CIMC:

Router(config)# interface ucse 2/0

Router(config-if)# imc ip address 10.0.0.2 255.0.0.0 default-gateway 10.0.0.1

imc ip address dhcp

To configure a dynamic IP address for CIMC, use the imc ip address dhcp command from interface configuration mode .

imc ip address dhcp no imc ip address


This command has no arguments.

Command Modes


126


OL-29450-01


imc vlan

Command History

Release

15.2(4)M

Modification





slot/port

The following example shows how to configure the DHCP ip address for CIMC:


Router(config-if)# imc ip address dhcp

imc vlan

To enter VLAN configuration mode for the specified VLAN number, use the imc vlan command from interface configuration mode .

imc vlan vlan_number

no imc vlan


vlan_number

IP address of the remote manager.

Command Modes


Command History

Release

15.2(4)M

Modification





slot/port

The following example shows how to enter the VLAN configuration mode in CIMC for a specified VLAN:


Router(config-if)# interface vlan 40


127 OL-29450-01


ucse cmos-reset

ucse cmos-reset

To reset the BIOS CMOS of the Cisco E-Series Server, use the ucse cmos-reset command in EXEC mode.

ucse slot cmos-reset


slot

Router slot number in which the Cisco E-Series

Server is installed.

Command Modes

Privileged EXEC mode.

Command History

Release

15.2(4)M

Modification



This command sets the BIOS (Basic Input Output System) back to the factory defaults. User changes made in the BIOS will be lost.

The following example shows how to reset the BIOS CMOS:

Router#

ucse 2 cmos-reset

ucse password-reset

To reset the BIOS, CIMC, or RAID password, use the ucse password-reset command in EXEC mode.

ucse slot password-reset {BIOS| BMC| RAID}


slot

BIOS

BMC

RAID

Router slot number in which the server module is installed.

Resets the BIOS password.

Resets the CIMC password.

Resets the RAID password.

128


OL-29450-01


ucse session

Command Modes


Command History

Release

15.2(4)M

Modification

This command was first introduced in the Cisco UCS E-Series Servers.


After this command has been entered, the system requests that a new password be set when accessing the

BIOS or BMC.

The following example shows how to reset the BIOS password:

Router#

ucse 2 password-reset BIOS

Reset command sent

ucse session

To start or close a Cisco E-Series Server host or CIMC session, use the ucse session command in EXEC mode.

ucse slot session {imc [clear]| host [clear]}


slot

imc imc clear host host clear



Starts a session with CIMC.

Clears the existing CIMC session.

Starts a session with the host Cisco E-Series Server.

Clears the host Cisco E-Series Server session.

Command Modes


Command History

Release

15.2(4)M

Modification



129 OL-29450-01


ucse shutdown


The imc clear and host clear commands close the active session of the CIMC or the host. As a result, the system closes the sessions of any other users currently logged in.

Only one active session is allowed in the CIMC or host at any time. If you receive a “connection refused” message when sessioning in, close the current active session by entering the imc clear or host clear commands.

The following example shows how to clear the CIMC session:

Router# ucse 2 session imc clear

ucse shutdown

To shut down the Cisco E-Series Server system gracefully, use the ucse shutdown command in EXEC mode.

ucse slot shutdown


slot



Command Modes


Command History

Release

15.2(4)M

Modification



Use this command when removing or replacing a hot-swappable module during online insertion and removal

(OIR).

The following example shows how to gracefully shut down the server:

Router# ucse 2 shutdown

ucse statistics

To display or clear the reset and reload information of the Cisco E-Series Server, use the ucse statistics command in EXEC mode.

ucse slot statistics clear

130


OL-29450-01


ucse status


slot

clear



Clears the Cisco E-Series Server’s reset and reload information.

Command Modes


Command History

Release

15.2(4)M

Modification



None.

The following example shows how to display the server statistics:

Router#

ucse 2 statistics

Module Reset Statistics:

CLI reset count = 0

CLI reload count = 0

Registration request timeout reset count = 0

Error recovery timeout reset count = 0

Module registration count = 1

ucse status

To display configuration information related to the hardware and software on the Cisco E-Series Server, use the ucse status command in EXEC mode.

ucse slot status [detailed]


slot

detailed



Displays detail information about the Cisco E-Series

Server such as the status of the service module and settings of the reset and heartbeat-reset flags.

Command Modes



131 OL-29450-01


ucse stop

Command History

Release

15.2(4)M

Modification



None.

The following example shows how to display server status:

Router#

ucse 2 status

Service Module is Cisco ucse 2/0

Service Module supports session via TTY line 131

Service Module is in Steady state

Service Module reset on error is disabled

Service Module heartbeat-reset is enabled

ucse stop

To power down the Cisco E-Series Server immediately, use the ucse stop command in EXEC mode.

ucse slot stop


slot



Command Modes


Command History

Release

15.2(4)M

Modification



None.

The following example shows how to power down the server:

Router#

ucse 2 stop

Send server stop command

132


OL-29450-01

C H A P T E R

14

Cisco IOS Software Command Reference—Cisco

ISR 4451-X

This chapter provides the new Cisco IOS commands that were introduced for the E-Series Servers installed in the Cisco ISR 4451-X.

Note

The Cisco IOS commands are sometimes updated after original publication; therefore, for updated content, review the Cisco IOS Interface and Hardware Component Command Reference at http://www.cisco.com/ en/US/docs/ios-xml/ios/interface/command/ir-cr-book.html

.


•

debug platform software ucse, page 133

•

hw-module subslot session, page 134

•

imc ip dhcp, page 135

•

show interfaces ucse, page 136

•

ucse subslot imc password-reset, page 138

•

ucse subslot server, page 138

•

ucse subslot server password-reset, page 140

•

ucse subslot shutdown, page 141

•

ucse subslot statistics, page 141

•

ucse subslot status, page 142

debug platform software ucse

To debug the Cisco UCS E-Series Server (UCSE) platform software and display debug messages, use the

debug platform software ucse command in privileged EXEC mode. To disable debug, use the no form of this command.


133 OL-29450-01


hw-module subslot session

debug platform software ucse {all| error| normal}

no debug platform software ucse {all| error| normal}

Syntax Description all error normal

Displays all platform debug messages.

Displays error debug messages.

Displays normal debug messages.

Command Modes

Privileged EXEC (#)

Command History

Release

Cisco IOS XE Release 3.9S

Modification

This command was introduced on the Cisco UCS E-Series Servers installed in the Cisco 4400 Series Integrated Services Router (ISR).


After you use the debug platform software ucse all command, use the appropriate ucse command to display debug messages.

The following example shows how to display debug messages for the ucse subslot imc password-reset command:

Router#

debug platform software ucse all

Router#

Router#

ucse subslot 2/0 imc password-reset

ucse2/0/0

Password reset command sent.

Router#

IMC ACK: UCSE password reset successful for IMC

ACK received for UCSE: Password Reset Command

hw-module subslot session

To start or close a Cisco Integrated Management Controller (CIMC) or host server module session, use the

hw-module subslot session command in privileged EXEC mode.

hw-module subslot slot/port-adapter session {imc| server}


slot/ Number of the router slot in which the server module is installed.

134


OL-29450-01


imc ip dhcp

port-adapter

imc server

Number of the port adapter.

Note

For Cisco UCS E-Series Servers, the port adapter number is 0.

Starts a session with CIMC.

Starts a session with the host server module.

Command Modes

Privileged EXEC (#)

Command History

Release


Modification



Only one active session is allowed in the CIMC or server module at any time.

The following example shows how to start a CIMC session:

Router#

hardware-module subslot 1/0 session imc

The following example shows how to start a server module session:

Router#

hardware-module subslot 1/0 session server

imc ip dhcp

To configure a dynamic IP address for the Cisco Integrated Management Controller (CIMC), use the imc ip

dhcp command in UCSE configuration mode. To unconfigure the dynamic IP address, use the no form of this command.

imc ip dhcp no imc ip dhcp


This command has no arguments or keywords.

Command Modes

UCSE configuration (config-ucse)


135 OL-29450-01


show interfaces ucse

Command History

Release


Modification


The following example shows how to configure a dynamic IP address for CIMC:

Router#


Enter configuration commands, one per line.

End with CNTL/Z.

Router(config)#



imc ip dhcp


IMC ACK: DHCP enable received for IMC.

IMC ACK: UCSE setting DHCP enable for IMC successful.

show interfaces ucse

To display Cisco UCS E-Series Server (UCSE) interface statistics, use the show interfaces ucse command in privileged EXEC mode.

show interfaces ucse slot/port-adapter/ucse-interface [accounting| controller| counters| crb| dampening|

description| etherchannel| history| irb| mac-accounting| monitor| mpls-exp| precedence| stats| summary|

switchport]


slot/

port-adapter/

ucse-interface

accounting controller counters crb

Number of the router slot in which the server module is installed.


Note


Number of the UCSE interface.

Note

For Cisco UCS E-Series Servers, the UCSE interface number can be 0 or 1.

(Optional) Displays the number of packets of each protocol type that have been sent through the interface.

(Optional) Displays the interface, configuration, and controller status.

(Optional) Displays the interface counters.

(Optional) Displays interface routing or bridging information.

136


OL-29450-01


show interfaces ucse dampening description etherchannel history irb mac-accounting monitor mpls-exp precedence stats summary switchport

(Optional) Displays interface dampening information.

(Optional) Displays the interface description.

(Optional) Displays interface Ether Channel information.

(Optional) Displays interface history.

(Optional) Displays interface routing or bridging information.

(Optional) Displays interface MAC accounting information.

(Optional) Displays interface continuously.

(Optional) Displays interface Multiprotocol Label

Switching (MPLS) experimental accounting information.

(Optional) Displays interface precedence accounting information.

(Optional) Displays the switching path, the packets in and packets out, and the characters in and characters out.

(Optional) Displays the interface summary.

(Optional) Displays the switch port interface information.

Command Modes

Privileged EXEC (#)

Command History

Release


Modification


The following example provides sample output from the show interfaces ucse slot/0/0 switchport command.

Router#

show interfaces ucse 1/0/0 switchport

Name: ucse 1/0/0

Switchport: Enabled

Administrative mode: trunk

OL-29450-01


137


ucse subslot imc password-reset

Operational Mode: trunk

Administrative Trunking Encapsulation: dot1q

Operational Trunking Encapsulation: native

Negotiation of Trunking: Disabled

Trunking Native Mode VLAN: 2352

Trunking VLANs Enabled: 1-2349,2450-4094

Voice VLAN: none

ucse subslot imc password-reset

To reset the Cisco Integrated Management Controller (CIMC) password, use the ucse subslot imc

password-reset command in privileged EXEC mode.

ucse subslot slot/port-adapter imc password-reset


slot/

port-adapter



Note


Command Modes

Privileged EXEC (#)

Command History

Release


Modification



After you enter this command, at the next login, the system requests that you set a new password to access

CIMC.

The following example shows how to reset the CIMC password:

Router#

ucse subslot 1/0 imc password-reset

Router#

IMC ACK: UCSE password reset successful for IMC

ucse subslot server

To reload, reset, start, or stop the hardware on the server module, use the ucse subslot server command in privileged EXEC mode.

ucse subslot slot/port-adapter server {reload| reset| start| stop}

138


OL-29450-01


ucse subslot server


slot/

port-adapter

reload reset start stop



Note


Gracefully shuts down the server module and then powers it on.

Resets the hardware on the server module.

Powers on the server module.

Immediately powers down the server module.

Command Modes

Privileged EXEC (#)

Command History

Release


Modification



Use the reset keyword only to recover from a shutdown or failed state.

Caution

Using the reset keyword does not provide an orderly software shutdown and may impact file operations that are in progress.

The following example shows how to reload the server:

Router#

ucse subslot 1/0 server reload

Router#

IMC ACK: UCSE Server reload successful.

The following example shows how to reset the server:

Router#

ucse subslot 1/0 server reset

Router#

IMC ACK: UCSE Server reset successful.

The following example shows how to start the server:

Router#

ucse subslot 1/0 server start

Router#

OL-29450-01


139


ucse subslot server password-reset

IMC ACK: UCSE Server start successful.

The following example shows how to stop the server:

Router#

ucse subslot 1/0 server stop

Router#

IMC ACK: UCSE Server stop successful.

ucse subslot server password-reset

To reset the BIOS or RAID password, use the ucse subslot server password-reset command in privileged

EXEC mode.

ucse subslot slot/port-adapter server password-reset {BIOS| RAID}


slot/

port-adapter

BIOS

RAID



Note


Resets the BIOS password.

Resets the RAID password.

Command Modes

Privileged EXEC (#)

Command History

Release


Modification



After you enter this command, at the next login, the system requests that you set a new password to access

BIOS or configure RAID.

The following example shows how to reset the BIOS password:

Router#

ucse subslot 1/0 server password-reset BIOS

Router#

IMC ACK: UCSE password reset successful for BIOS

140


OL-29450-01


ucse subslot shutdown

The following example shows how to reset the RAID password:

Router#

ucse subslot 1/0 server password-reset RAID

Router#

IMC ACK: UCSE password reset successful for RAID

ucse subslot shutdown

To gracefully shut down the server module, use the ucse subslot shutdown command in privileged EXEC mode.

ucse subslot slot/port-adapter shutdown


slot/

port-adapter



Note


Command Modes

Privileged EXEC (#)

Command History

Release


Modification


The following example shows how to shut down the server module:

Router#

ucse subslot 1/0 shutdown

Router#

IMC ACK: UCSE Server shutdown successful.

ucse subslot statistics

To display or clear server module statistics, use the ucse subslot statistics command in privileged EXEC mode.

ucse subslot slot/port-adapter statistics [clear]


slot/ Number of the router slot in which the server module is installed.


141 OL-29450-01


ucse subslot status

port-adapter

clear


Note


(Optional) Clears the server module statistics.

Command Modes

Privileged EXEC (#)

Command History

Release


Modification


The following example shows how to display the server module statistics:

Router#

ucse subslot 1/0 statistics

Count of number of shutdowns command : 1

Count of number of status commands : 0

Count of number of server raid password : 1

Count of number of imc password-reset : 2

Count of number of server bios password reset : 1

Count of number of server reload : 1

Count of number of server reset : 1

Count of number of server start : 1

Count of number of server stop : 1

Count of number of vlan commands : 0

Count of number of access-port commands : 1

Count of number of IMC configured IP or DHCP commands: 1


To display configuration information related to the hardware and software on the server module, use the ucse

subslot status command in privileged EXEC mode.

ucse subslot slot/port-adapter status [detailed]


slot/

port-adapter

detailed



Note


(Optional) Displays detailed information about the server module, such as its status and settings of the reset and heartbeat-reset flags.

142


OL-29450-01



Command Modes

Privileged EXEC (#)

Command History

Release


Modification


The following example shows how to display server status:

Router#

ucse subslot 1/0 status

CPU info

Name Cores Version

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

CPU1 4 Intel(R) Xeon(R) CPU E5-2418L 0 @ 2.00GHz

Memory info

Name Capacity Channel Speed (MHz) Channel Type

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

Node0_Dimm0 Not Installed Unknown Unknown

Node0_Dimm1

Node0_Dimm2

16384 MB

8192 MB

1333

1333

DDR3

DDR3

Hard drive info

Slot Number Controller Status Manufacturer Model

Firmware Coerced Size Type SED

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

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

1 SLOT-5 online

2

952720 MB HDD false

SLOT-5 online

ATA

ATA

ST91000640NS

ST91000640NS

Drive

CC02

CC02

3

952720 MB

952720 MB

HDD false

SLOT-5 online

HDD false

ATA ST91000640NS CC02

Virtual drive info

Virtual Drive Status Name Size RAID Level

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

0 Optimal 1905440 MB RAID 5

PCI card info

Name

Name

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

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

PCIe Adapter1

5719 1 Gbps 4...

0 0xe414 0x5716

PCIe Adapter2

MegaRAID S...

2

Slot Vendor ID

0x0010

Device ID

0x7300

Product

Broadcom

LSI 9240-8i

Network Setting

IPv4 Address: 10.1.1.2

IPv4 Netmask: 255.255.255.0

IPv4 Gateway: 10.1.1.1

NIC Mode: shared_lom

NIC Redundancy: none

NIC Interface: ge1

OL-29450-01


143



144


OL-29450-01

I N D E X

A

accessing

106

B

basic workflow

10, 11, 12, 15

installing the E-Series Server into router

15

option 1

10

option 2

11

option 3

12

BIOS

102, 103, 105

firmware

103, 105

installing from TFTP server

105

installing through browser

103

obtaining firmware from Cisco

102

obtaining firmware from Cisco options

102

BIOS firmware

103, 105

installing from TFTP server

105

installing through browser

103

BIOS setup

85, 106, 109

boot order, configuring

81

C

changing configuration

109

CIMC

18, 102

firmware

18

updating

18

CIMC access

27, 28, 29, 30, 33, 35, 38, 39, 41, 45, 48, 51

configuration options

27, 38

NIC interface configuration options

41

shared LOM configuration options

29

using CIMC Configuration Utility

51

using console interface

30

using G2 or G3 interface

35, 48

using internal MGF VLAN interface

33

using management (dedicated) interface

28, 39

CIMC CLI

56

OL-29450-01

CIMC firmware

111

recovering from corrupted image

111

CIMC GUI

56, 57

CIMC overview

55

common terms

13

compatibility

15

verifying

15

configuration quick reference

2

configuring boot order

85

D

diagnostics

120, 122

mapping to host

120

test, running

122

E

E-Series Server

5, 7, 8, 16, 19

installing into the router

16

managing

7

options

8

overview

5

verifying, installation

19

E-Series Server interfaces

26, 37

overview

26, 37

EVC using native VLAN between the server and the Cisco

ISR-4451-X

93

creating

93

EVC using non-native VLAN between the server and the Cisco

ISR-4451-X

94

creating

94

F

firmware

18, 102

obtaining from Cisco

102

updating

18


IN-1

Index

firmware options

102

obtaining from Cisco

102

H

host image

74, 78

unmapping

78

host image, mapping

75

O

operating system installation

72

OS installation

71, 72, 74

KVM console

72

methods

71

PXE

74

I

installing

81

interface

28, 30, 33, 35, 39, 41, 45, 48

CIMC access using console interface

30

CIMC access using E-Series Server's internal GE0 interface and router's ucse /0/0 interface

41

CIMC access using E-Series Server's internal GE1 interface and router's ucse /0/1 interface

45

CIMC access using G2 or G3 interface

35, 48

CIMC access using internal MGF VLAN interface

33

CIMC access using management interface

28, 39

K

KVM console

72

P

PXE installation

74

R

RAID options

61

RAID, configuring

65, 68

using CIMC GUI

65

using WebBIOS

68

recovering from corrupt firmware

111

reset

18

stopping

18

router and e-series server

87, 90

configuring connection

87, 90

router configuration

21, 22

differences between SRE-V and E-Series Server

21, 22

L

Linux

98

logging in

56

S

SD Card

113, 115

recovering from faulty

113, 115

server management

81

configuring the boot order

81

server software

6

software

79

obtaining from VMware

79

M

mapping

74

Microsoft Windows

98

Microsoft Windows Server, accessing

58

option 2

58

U

using CIMC GUI

81

N

network interface mapping

96

Network Static Settings

53

defining, using a script file

53

V

VMware

79

obtaining software

79


58, 79, 98

accessing

58

assigning a static IP address

79

installation, basic workflow

79

IN-2


OL-29450-01

Index

VMware vSphere Hypervisor (continued) option 3

58

VMware vSphere Hypervisor configuration

23

differences between SRE-V and E-Series Server

23

vSphere client

81

downloading

81

OL-29450-01


IN-3

Index

IN-4


OL-29450-01

Getting Started Guide for Cisco UCS E-Series Servers, Release 2.x

Getting Started Guide for Cisco UCS E-Series Servers, Release 2.x

Preface

Audience

Organization

Conventions

Related Documentation

New and Changed Information

Documentation Feedback

Configuration Quick Reference

Configuration Quick Reference Tasks

Cisco UCS E-Series Servers Overview

Cisco UCS E-Series Servers Overview

Server Software

Managing E-Series Servers

E-Series Server Options

Basic Workflow for Option 1—E-Series Server without a Preinstalled Operating

System or Hypervisor

Basic Workflow for Option 2—E-Series Server with a Preinstalled Microsoft

Windows Server

Basic Workflow for Option 3—E-Series Server with a Preinstalled VMware

vSphere Hypervisor

Common Terms Used in This Guide

Installing the E-Series Server into the Router

Basic Workflow for Installing the E-Series Server into the Router

Verifying the Router, E-Series Server, and Cisco IOS Software

Version Compatibility

Installing the E-Series Server into the Router

Stopping the E-Series Server from Resetting and Updating the

CIMC Firmware

Verifying E-Series Server Installation

Configuration Differences

Router Configuration Differences Between the Cisco SRE-V and

the E-Series Server—ISR G2

Router Configuration Differences Between the ISR G2 and the

Cisco ISR 4451-X

VMware vSphere Hypervisor Configuration Differences

Configuring CIMC Access

Configuring CIMC Access - ISR G2

E-Series Server Interfaces Overview—ISR G2

CIMC Access Configuration Options—ISR G2

Configuring CIMC Access Using the E-Series Server's External Management (Dedicated)

Interface—ISR G2

Configuring CIMC Access Using Shared LOM—ISR G2

Configuring CIMC Access - Cisco ISR 4451-X

E-Series Server Interfaces Overview—Cisco ISR 4451-X

CIMC Access Configuration Options—Cisco ISR 4451-X

Configuring CIMC Access Using the E-Series Server's External Management (Dedicated)

Interface—Cisco ISR 4451-X

Configuring CIMC Access Using the E-Series Server's NIC Interfaces—Cisco ISR 4451-X

Configuring CIMC Access Using the CIMC Configuration Utility

Defining Network Static Settings Using a Script File

Accessing CIMC

CIMC Overview

CIMC GUI

CIMC CLI

Logging In to the CIMC GUI

CIMC Home Page

Accessing the Microsoft Windows Server from CIMC

Accessing the VMware vSphere Hypervisor from CIMC

What to Do Next

Managing RAID

RAID Options

Configuring RAID

Configuring RAID Using the CIMC GUI

Configuring RAID Using the WebBIOS

What to Do Next

Installing the Operating System or Hypervisor

Operating System or Hypervisor Installation Methods

KVM Console

Installing an Operating System or Hypervisor Using the KVM Console

PXE Installation Servers

Installing an Operating System or Hypervisor Using a PXE Installation Server

Host Image Mapping

Mapping the Host Image

Installing Drivers for the Microsoft Windows Server

Unmapping the Host Image

Basic Workflow for Downloading and Installing the VMware vSphere Hypervisor

Downloading the Customized VMware vSphere Hypervisor Image

Assigning a Static IP Address to the VMware vSphere Hypervisor