Chapter 1. Overview

Cisco UCS Director Express for Big Data Bare Metal Agent

Minimum System Requirements

Guidelines and Limitations

Upgrade of Bare Metal Agent

Chapter 2. Installation of Cisco UCS Director Express for Big Data Bare Metal Agent

Installing Cisco UCS Director Express for Big Data Bare Metal Agent on VMware vSphere

NTP Server Configuration on Cisco UCS Director Express for Big Data Bare Metal Agent

Adding Oracle JDK Software Versions to Bare Metal Agent

Installation of User-Defined Software Post Hadoop Cluster Creation

Configuring the Network Interface using Shelladmin

Configuring the DHCP Server for a Bare Metal Agent Account

Setup and Configuration for PXE Boot Requests

Adding a New Red Hat Version for Hadoop Cluster

New RHEL Version

Upgrading Bare Metal Agent to Release 6.0

Chapter 3. Network Configuration for Cisco UCS Director Express Bare Metal Agent

About the Network Configuration Options

Separate Networks for Management and PXE

Prerequisites and Assumptions for a Separate Network Configuration

Preface

Audience

Conventions

Related Documentation

Documentation Feedback

Obtaining Documentation and Submitting a Service Request

Copyright Page

Chapter 1. Overview

This chapter contains the following sections:

- Cisco UCS Director Express for Big Data Bare Metal Agent

- Minimum System Requirements

- Guidelines and Limitations

- Upgrade of Bare Metal Agent

Cisco UCS Director Express for Big Data Bare Metal Agent

Cisco UCS Director Express for Big Data Bare Metal Agent (BMA) automates the process of using a Preboot Execution Environment (PXE) to install operating systems on bare metal servers or virtual machines. Bare Metal Agent provides the following services that are required for a functional PXE install environment:

- Dynamic Host Control Protocol (DHCP)

- Hypertext Transfer Protocol (HTTP)

- Trivial File Transfer Protocol (TFTP)

When this environment is operational and Bare Metal Agent and Cisco UCS Director Express for Big Data are correctly configured, you can build PXE installation tasks into any Cisco UCS Director Express for Big Data infrastructure workflow.

You can access Bare Metal Agent through Secure Shell (SSH). You can also perform services on Bare Metal Agent, such as DHCP configuration and starting and stopping services, through Cisco UCS Director Express for Big Data. A single Cisco UCS Director Express for Big Data node can support multiple Bare Metal Agent applications.

Minimum System Requirements

For proper installation and operation of Bare Metal Agent, your environment must meet the minimum system requirements.

Minimum Requirements for VMware vSphere

Name

Requirements

VMware vCenter Server

4.0 and later

Minimum reservation in VMware vCenter

Minimum number of CPUs—2

Memory—3 GB

Hard disk—40 GB

Guidelines and Limitations

Before you install Bare Metal Agent, take note of the following guidelines and limitations.

Bare Metal Agent Connections

Each Bare Metal Agent application can connect to only one Cisco UCS Director Express for Big Data node.

Network Availability

After installation and configuration, your environment must have the following network availability:

- Bare Metal Agent must be able to reach Cisco UCS Director Express for Big Data over the network.

- Cisco UCS Director Express for Big Data must be able to reach Bare Metal Agent over the network.

- The bare metal servers (blade or rack) must be able to reach the DHCP network of the Bare Metal Agent during the initial stage of operating system installation over PXE.

DHCP Configuration

If you use DHCP, locate a DHCP server in the same PXE VLAN as Bare Metal Agent. Then configure that DHCP server with the IP address range required by your DHCP server.

VLAN Configuration

When setting up the network configuration, the most common configuration uses one PXE VLAN and one Management VLAN (separate VLANs). However, Bare Metal Agent supports one VLAN for both, if you prefer.

Configure the VLANs end-to-end between Cisco UCS, Cisco UCS Director Express for Big Data, and Bare Metal Agent. However, when you configure Bare Metal Agent, do not assume that routing occurs between the PXE_VLAN Layer 2 network and the Management VLAN network.

If you configure Bare Metal Agent to use DHCP, locate and configure the DHCP server in the PXE VLAN and its subnet. This DHCP server serves the transient IP address required for the PXE process. In an environment with two VLANs, the server is allocated an IP address from the subnet of the Management VLAN. An IP address pool managed by Cisco UCS Director Express for Big Data assigns this IP address.

If you configure Bare Metal Agent with two VLANs, set up two IP address attributes:

- An IP address for Bare Metal Agent in the PXE VLAN

- A second IP address for Bare Metal Agent in the Management VLAN

TFTP Server

With Bare Metal Agent, use the Cisco UCS Director Express for Big Data TFTP server to ensure that configurations such as dynamic variables function properly.

When you add a Bare Metal Agent account, Bare Metal Agent configures the TFTP server when services are started.

Upgrade of Bare Metal Agent

For detailed information on upgrading Bare Metal Agent, see the Cisco UCS Director Upgrade Guide.

Chapter 2. Installation of Cisco UCS Director Express for Big Data Bare Metal Agent

This chapter contains the following sections:

- Installing Cisco UCS Director Express for Big Data Bare Metal Agent on VMware vSphere

- NTP Server Configuration on Cisco UCS Director Express for Big Data Bare Metal Agent

- Adding Oracle JDK Software Versions to Bare Metal Agent

- Installation of User-Defined Software Post Hadoop Cluster Creation

- Configuring the Network Interface using Shelladmin

- Configuring the DHCP Server for a Bare Metal Agent Account

- Setup and Configuration for PXE Boot Requests

- Adding a New Red Hat Version for Hadoop Cluster

- Upgrading Bare Metal Agent to Release 6.0

Installing Cisco UCS Director Express for Big Data Bare Metal Agent on VMware vSphere

Before You Begin

- You must have system administrator privileges for VMware vSphere or vCenter.

- If you want to use a static IP address rather than DHCP, you must know the following information:

- IP address

- Subnet mask

- Default gateway

Step 1

On the Cisco.com download site for Cisco UCS Director, download Cisco UCS Director Bare Metal Agent and unzip the OVF file.

Step 2

Log in to VMware vSphere Client.

Step 3

In the Navigation pane, click the vSphere host on which you want to deploy Cisco UCS Director Express for Big Data Bare Metal Agent.

Step 4

Choose File > Deploy OVF Template.

Step 5

In the Source screen of the Deploy OVF Template window, do one of the following to choose your OVF source location and then click Next:

- If the OVF file is stored on your local computer, browse to the location, choose the file, and click Open.

- If the OVF file is stored on a server on your local area network, enter the location of the file including the IP address or fully qualified domain name of the server.

Step 6

In the OVF Template Details screen, verify the details and click Next.

Step 7

In the End User License Agreement screen, review the license agreement and click Accept.

Step 8

In the Name and Location screen, do the following:

1. In the Name field, enter a unique name for the VM.

2. In the Inventory Location area, choose the location where you want the VM to reside.

3. Click Next.

Step 9

In the Storage screen, choose the storage location for the VM and click Next.

Step 10

In the Disk Format screen, click Next to accept the default radio button for Thick Provision (Lazy Zeroed) format.

Step 11

In the Network Mapping screen, choose the network for the VM and click Next.

Step 12

In the Properties screen, do the following:

1. In the BMA Root User Password field, enter the password that you want to use as the root password.

2. Configure the IP addresses for both the NICs (eth0 and eth1) that you want to assign, as follows:

- To use DHCP to assign the IP addresses, leave the default of 0.0.0.0 in the IP address fields.

- To use static IP addresses, enter the desired IP addresses in the IP address fields. If you only want to configure one NIC, only complete one set of IP addresses and leave the second set at the default.

3. Click Next.

Step 13

In the Ready to Complete screen, verify the settings and click Finish.
A message appears to indicate that Cisco UCS Director Express for Big Data Bare Metal Agent is being deployed.

Step 14

Log in to the Cisco UCS Director Express for Big Data Bare Metal Agent server with root privileges, and check if you are able to ping the Cisco UCS Director Express for Big Data Bare Metal Agent server.

Step 15

In the Navigation pane, right-click the Cisco UCS Director Express for Big Data Bare Metal Agent server and choose Edit Settings.

1. Choose the Resources tab.

2. In the Resource Allocation window, set CPU and Memory Reservation settings to the maximum.

3. Click OK.

Step 16

Power on the VM.

NTP Server Configuration on Cisco UCS Director Express for Big Data Bare Metal Agent

You can configure Cisco UCS Director Express for Big Data Bare Metal Agent to have its clock synchronized to an external NTP server. This ensures that the correct calendar time is maintained on the Bare Metal Agent.

Ensure that you synchronize Cisco UCS Director Express for Big Data and Cisco UCS Director Express for Big Data Bare Metal Agent before you deploy any Hadoop cluster. It is recommended that you also synchronize Cisco UCS Manager and Cisco UCS Director Express for Big Data on the configured NTP server.

Follow the steps to locate the ntp_server_config.sh:

- Locate /opt/cnsaroot/bigdata_templates/ntp_server_config.sh

- Add execute permissions (chmod+x ntp_server_config.sh)

- Execute ( ./ntp_server_config.sh <ntp_server_ip or hostname>) on the Cisco UCS Director Express for Big Data Bare Metal Agent server.

Adding Oracle JDK Software Versions to Bare Metal Agent

You can upload Oracle JDK software and use Oracle JDK for all Hadoop distributions (Cloudera, MapR, and Hortonworks) through an instant Hadoop cluster and customized Hadoop cluster creation actions. You can also add new nodes to the existing cluster and support upgrading existing clusters.

Step 1

Log in to the Cisco UCS Director Bare Metal Agent server.

Step 2

Create a JDK folder in /opt/cnsaroot/bd-sw-rep/.
For example, create a JDK folder in /opt/cnsaroot/bd-sw-rep/JDK in the Bare Metal Agent.

Step 3

Navigate to Solutions > Big Data > Settings and click the Software Catalogs tab to create JDK software version folder names for each version.

Step 4

Copy JDK files in .rpm or .gz format to the respective version folders.

Step 5

On the menu bar, choose Administration > Integration to track software uploads.

Step 6

Click the Change Record tab to track the software upload in progress and verify if completed, failed, or timeout.

Installation of User-Defined Software Post Hadoop Cluster Creation

Cisco UCS Director Express for Big Data provides an option to add user-defined installation packages (RPMs) post Hadoop cluster creation specific to a version. In Cisco UCS Director Express for Big Data, you cannot install more Hadoop related software other than what is required for the selected type of Hadoop distribution when creating an instant Hadoop cluster or customizing a Hadoop cluster.

To install user-defined Hadoop related software, you can specify a list of RPMs in the HadoopDistributionRPM.txt file. This modifiable list defines the required packages for each version of a Hadoop distribution. You can locate the HadoopDistributionRPM.txt here: /opt/cnsaroot/bigdata_templates/common_templates in the Cisco UCS Director Express for Big Data Bare Metal Agent server.

For example, you can specify a list of RPMs in the HadoopDistributionRPM.txt file for MapR-5.0.0:

- mapr-v5.0.0GA.rpm.tgz

- mapr-ecosystem-5.x-20150709.rpm.tgz

- mapr-whirr-0.8.1.18380-GA.noarch.rpm

Configuring the Network Interface using Shelladmin

This procedure is optional.

Step 1

Log in to the Cisco UCS Director Express for Big Data VM console with the following credentials:

1. User—shelladmin

2. Password—changeme

If you have already logged into the shelladmin and changed the default password, use your new password instead.

After you have logged in, you can choose Change shelladmin password to change the default password.

Step 2

Choose Configure Network Interface.

Step 3

At the Do you want to Configure DHCP/STATIC IP [D/S] prompt, enter one of the following choices:

- If DHCP is enabled, enter D (IP addresses are assigned automatically)

- To configure static IP, enter S, and then choose the interface you want to configure at the next prompt followed by the option to select IPv4 or IPv6. This is followed by the confirmation of the interface selected and the version of IP for which you select Y to continue. Then enter the following details:

- IP address

- Netmask

- Gateway

- DNS Server 1

- DNS Server 2

Step 4

Confirm when prompted.

Configuring the DHCP Server for a Bare Metal Agent Account

Note

For a multi-home DHCP configuration, use this procedure to configure the first subnet for the DHCP server. For the remaining subnets, you must manually edit the DHCP configuration file (/etc/dhcpd.conf).

Before You Begin

To provide required DHCP services, ensure that at least one DHCP server is located in the same PXE VLAN as Bare Metal Agent. Configure the DHCP server with an appropriate IP address range. The DHCP server, together with the TFTP server, is used to communicate with a PXE server.

Step 1

Log in to the Cisco UCS Director Express for Big Data server with the following credentials:

1. User—admin

2. Password—admin

Step 2

On the menu bar, choose Administration > Physical Accounts.

Step 3

Click the Bare Metal Agents tab.

Step 4

Click the row for the Bare Metal Agent account for which you want to configure the DHCP server.

Step 5

Click Service Status to verify that services for the Bare Metal Agent account are stopped.

Step 6

Click Configure DHCP.

Step 7

In the Configure DHCP dialog box, complete the following fields and click Submit.

- DHCP Subnet

- DHCP Netmask

- DHCP Start IP

- DHCP End IP

- Router IP Address

The DHCP IP address assignments are updated, and the DHCP service is restarted.

Step 8

Click the row for the Bare Metal Agent account and click Start Services.

Step 9

After the services have started, do the following:

- Verify that the status of the account in the Status column is Active.

- Verify that the Enabled Services column shows that all services are running. If this status indicates that one or more services are stopped, verify the configuration of your DHCP server and try again.

- Click Service Status to verify that the status of all expected services is up:

- Network Services status in the Bare Metal Agent appliance

- Database connectivity status from the Bare Metal Agent appliance

What to Do Next

Set up PXE boot requests.

Setup and Configuration for PXE Boot Requests

You can use Cisco UCS Director Express for Big Data Bare Metal Agent (Bare Metal Agent) to create and send a request through the DHCP server for a PXE boot for a specified operating system (OS).

Before you can create and send a PXE boot request, the OS image that you want to use in a given PXE boot request must be configured correctly and be available in Bare Metal Agent. If the OS image that you want to PXE boot is not listed as an available OS type, you must first create the OS image template in Bare Metal Agent,

Note

Although you can perform all the OS image setup procedures manually, we recommend that you use Bare Metal Agent to set up your OS images.

Adding a New Red Hat Version for Hadoop Cluster

For more information on uploading supported Red Hat Enterprise Linux versions, see Chapter 12, Managing Hadoop and Splunk Clusters in Cisco UCS Director Express for Big Data Management Guide.

Step 1

On the menu bar, choose Solutions > Big Data > Settings.

Step 2

Click the Software Catalogs tab.

Step 3

Click Add.

Step 4

Click Upload.

Step 5

Choose the target Cisco UCS Director Express for Big Data Bare Metal Agent from the Target BMA drop-down list.

Step 6

Check the Restart BMA Services check box to restart Cisco UCS Director Express for Big Data Bare Metal Agent after uploading the required files.

Step 7

To verify that the new Red Hat version (operating system software) is available in the Cisco UCS Director Express for Big Data server, perform the following:

1. Log in to the Cisco UCS Director Express for Big Data user interface.

2. On the menu bar, choose Administration > Physical Accounts.

3. Click the Bare Metal Agents tab.

You can find the new Red Hat version listed in the Image Catalogs column of the Bare Metal Agents report.

- New RHEL Version

New RHEL Version

Red Hat Enterprise Linux 7.2

Download the following file:

- rhel-server-7.2-x86_64-dvd.iso from Red Hat Enterprise Linux

Upgrading Bare Metal Agent to Release 6.0

Before You Begin

- Upgrade Cisco UCS Director to Release 6.0.

If your system is running versions prior to release 5.4, then you must first migrate to Release 5.4, then upgrade to Release 5.5 and then upgrade to Release 6.0. For information on upgrading to release 5.4, see the Cisco UCS Director Release 5.4 Upgrade Guide available at: Click Here

Step 1

Download the Bare Metal Agent, Release 6.0 patch to the existing Bare Metal Agent.

Step 2

Log in to the Bare Metal Agent console through PuTTY or another Secure Shell (SSH) client, using the default root credentials shown or the root credentials for your system.

Username: root
Password: pxeboot

Step 3

Navigate to the /opt/infra directory and run StopInfraAll.sh to stop the services.

Step 4

Unzip the patch.

Step 5

Navigate to the directory of the unzipped file.

cd ucsd_bma_patch_6_0_0_0

Step 6

Run ./applyPatch.sh to apply the patch to Bare Metal Agent.

Step 7

Wait for the installation to complete.

Step 8

Navigate to the /opt/infra directory.

Step 9

Run ./showBMAVersion.sh to verify that you have the correct version of Bare Metal Agent.

Step 10

Run startInfraAll.sh to start the BMA services.

Step 11

Run statusInfra.sh to check the status of the BMA services.

Step 12

Log in to Cisco UCS Director, Release 6.0, and choose Administration > Physical Accounts > Bare Metal Agents.

Step 13

Choose the account for the Bare Metal Agent that you have upgraded.
If your system has more than one instance of Bare Metal Agent, you can identify the correct account by the IP address.

Step 14

Confirm that the Bare Metal Agent account is reachable from Cisco UCS Director and then stop and start the services for that account.

Chapter 3. Network Configuration for Cisco UCS Director Express Bare Metal Agent

This chapter contains the following sections:

- About the Network Configuration Options

- Separate Networks for Management and PXE

About the Network Configuration Options

You can choose Separate networks for management and Preboot Execution Environment (PXE) network configuration option for Cisco UCS Director Express for Big Data Bare Metal Agent.

Separate Networks for Management and PXE

We recommend that you choose this network configuration option if your environment does not permit the following to be hosted on the same network interface and Layer 2 network (see the following figure):

- On the PXE network, services provided by Bare Metal Agent, such as DHCP, TFTP, and HTTP

- On the Management network, traffic between Bare Metal Agent and Cisco UCS Director Express for Big Data or other devices and appliances

Sample Topology for Separate PXE and Management Networks

- Prerequisites and Assumptions for a Separate Network Configuration

Prerequisites and Assumptions for a Separate Network Configuration

If you plan to configure Bare Metal Agent with a separate network configuration, make sure that your environment meets the following prerequisites:

- Cisco UCS Director Express for Big Data has been installed and the network interface configured, as described in the appropriate Cisco UCS Director Express for Big Data installation guide.

- Cisco UCS Director Express for Big Data Bare Metal Agent is reachable through a web browser and you can log in.

- Bare Metal Agent has been installed, as described in the Cisco UCS Director Express for Big Data Baremetal Agent Installation and Configuration Guide, and no additional configuration has been performed.

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

- Management (MGMT) network—Used for traffic between Bare Metal Agent and Cisco UCS Director Express for Big Data

- PXE network—Used for PXE services traffic, such as DHCP, HTTP, and TFTP

Preface

- Audience

- Conventions

- Related Documentation

- Documentation Feedback

- Obtaining Documentation and Submitting a Service Request

Audience

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

- Server administration

- Storage administration

- Network administration

- Network security

- Virtualization and virtual machines

Conventions

Text Type

Indication

GUI elements

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.

Document titles

Document titles appear in this font.

TUI elements

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

System output

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

CLI commands

CLI command keywords appear in this font.

Variables in a CLI command appear in this font.

[ ]

Elements in square brackets are optional.

{x | y | z}

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

[x | y | z]

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

string

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

< >

Nonprinting characters such as passwords are in angle brackets.

[ ]

Default responses to system prompts are in square brackets.

!, #

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

Note

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

Caution

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

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.

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

Cisco UCS Director Documentation Roadmap

For a complete list of Cisco UCS Director documentation, see the Cisco UCS Director Documentation Roadmap available at the following URL: Click Here .

Cisco UCS Documentation Roadmaps

For a complete list of all B-Series documentation, see the Cisco UCS B-Series Servers Documentation Roadmap available at the following URL: Click Here .

For a complete list of all C-Series documentation, see the Cisco UCS C-Series Servers Documentation Roadmap available at the following URL: Click Here .

Note

The Cisco UCS B-Series Servers Documentation Roadmap includes links to documentation for Cisco UCS Manager and Cisco UCS Central. The Cisco UCS C-Series Servers Documentation Roadmap includes links to documentation for Cisco Integrated Management Controller.

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to ucs-director-docfeedback@cisco.com. We appreciate your feedback.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What's New in Cisco Product Documentation RSS feed. RSS feeds are a free service.

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: Click Here . 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)