Chapter 1. Cisco Application Centric Infrastructure MIB Quick Reference

MIBs and Network Management

SNMP Access Support in ACI

Accessing MIB Variables Through SNMP

SNMP Traps

Interpreting the MIB Structure

Object Identifiers

Tables

SYNTAX Clause

MAX-ACCESS Clause

About Cisco MIB Files

Cisco MIB File Directories

MIB Loading Order

Accessing and Downloading Cisco MIB Files

Enabling Passive FTP on Internet Explorer

Using HTTP to Access and Download the MIB Files from Cisco.com

Using Passive FTP to Access and Download the MIB Files

Understanding the ENTITY-MIB and Extensions

Extending the IF-MIB

Chapter 2. Configuring SNMP in APIC

Configuring the SNMP Policy Using the GUI

Configuring an SNMP Trap Destination Using the GUI

Configuring an SNMP Trap Source Using the GUI

Associating the SNMP Context With a VRF Using the GUI

Accessing the Context-Specific MIBs

Chapter 1. Cisco Application Centric Infrastructure MIB Quick Reference

This document describes the private, or local, SNMP Management Information Base (MIB) files supported by the software.

- MIBs and Network Management

- SNMP Access Support in ACI

- Interpreting the MIB Structure

- About Cisco MIB Files

- Accessing and Downloading Cisco MIB Files

- Understanding the ENTITY-MIB and Extensions

- Extending the IF-MIB

MIBs and Network Management

The MIB list includes Cisco proprietary MIBs and many other Internet Engineering Task Force (IETF) standard MIBs. The IETF standard MIBs are defined in Requests for Comments (RFCs). To find specific MIB information, you must examine the Cisco proprietary MIB structure and related IETF-standard MIBs supported by the software.

Network management takes place between two major types of systems: those systems in control, called managing systems, and those systems that managing systems observe and control, called managed systems. The most common managing system is called a network management system (NMS). Managed systems can include hosts, servers, or network components such as switches and routers.

To promote interoperability, cooperating systems must adhere to a common framework and a common language, called a protocol. In the Internet-standard management framework, that protocol is the Simple Network Management Protocol (SNMP).

The exchange of information between managed network devices and a robust NMS is essential for reliable performance of a managed network. Because some devices have a limited ability to run management software, most of the computer processing burden is assumed by the NMS. The NMS runs the network management applications, such as Cisco Data Center Network Manager, that present management information to network managers and other users.

In a managed device, specialized low-impact software modules, called agents, access information about the device and make it available to the NMS. Managed devices maintain values for a number of variables and report those values, as required, to the NMS. For example, an agent might report such data as the number of bytes and packets sent or received by the device or the number of broadcast messages sent and received. In SNMP, each of these variables is referred to as a managed object. A managed object is anything that can be managed or anything that an agent can access and report back to the NMS. All managed objects are contained in the MIB, which is a database of the managed objects.

An NMS can control a managed device by sending a request to an agent of that managed device, requiring the device to change the value of one or more of its variables. The managed devices can respond to requests such as set or get. The NMS uses the set request to control the device. The NMS uses the get requests to monitor the device. The set and get requests are synchronous events, which means that the NMS initiates the activity, and the SNMP agent responds.

The managed device can send asynchronous events, or SNMP notifications, to the NMS to inform the NMS of some recent event. SNMP notifications (traps or informs) which are included in many MIBs, and allow the NMS to less frequently send get requests to the managed devices.

SNMP Access Support in ACI

SNMP support in ACI is as follows:

- SNMP read queries (Get, Next, Bulk, Walk) are supported by leaf and spine switches and by APIC.

- SNMP write commands (Set) are not supported by leaf and spine switches or by APIC.

- SNMP traps (v1, v2c, and v3) are supported by leaf and spine switches and by APIC.

Note

ACI supports a maximum of 10 trap receivers.

- SNMPv3 is supported by leaf and spine switches and by APIC.

SNMP Support Changes by Cisco APIC Release

Release

Description

1.2(2)

IPv6 support is added for SNMP trap destinations.

1.2(1)

SNMP support for the APIC controller is added. Previous releases support SNMP only for leaf and spine switches.

For the complete list of MIBs supported in ACI, see Click Here .

- Accessing MIB Variables Through SNMP

- SNMP Traps

Accessing MIB Variables Through SNMP

The SNMP system consists of three parts: the SNMP manager, the SNMP agent, and the MIB. You can compile Cisco MIBs with your network management software. If SNMP is configured on a device, the SNMP agent responds to MIB-related queries sent by the NMS.

SNMPv1 was the initial version of the protocol. SNMPv2 added support for 64-bit counters, and SNMPv3 added increased security for access, authentication, and encryption of managed data.

This table describes SNMP operations.

SNMP Operations

Operation

Description

get-request

Retrieves a value from a specific variable.

get-next-request

Retrieves the value following the named variable. Often used to retrieve variables from within a table.[1]

get-bulk[2]

Retrieves large blocks of data, such as multiple rows in a table, which would otherwise require the transmission of many small blocks of data.

trap

Sends an unsolicited message by an SNMP agent to an SNMP manager indicating that some event has occurred.

[1] With this operation, an SNMP manager does not need to know the exact variable name. A sequential search finds the next variable from within the MIB.

[2] The get-bulk command is not a part of SNMPv1

SNMP Traps

You can configure the software to send notifications as SNMP traps to SNMP managers when particular events occur.

Notifications may contain a list of MIB variables, or varbinds, that clarify the status this is relayed by the notification. The list of varbinds associated with a notification is included in the notification definition in the MIB. In the case of standard MIBs, Cisco has enhanced some notifications with additional varbinds that further clarify the cause of the notification.

Use the SNMP-TARGET-MIB to obtain more information on trap destinations.

Note

You must enable most notifications through the CLI.

Interpreting the MIB Structure

A MIB presents the managed data in a logical tree hierarchy, using an IETF standard syntax called the Structure of Management Information (SMI). Branches of this MIB tree are organized into individual tables, which contain the managed data as leaf objects.

- Object Identifiers

- Tables

- SYNTAX Clause

- MAX-ACCESS Clause

Object Identifiers

The MIB structure is logically represented by a tree hierarchy. The root of the tree is unnamed and splits into three main branches: Consultative Committee for International Telegraph and Telephone (CCITT), International Organization for Standardization (ISO), and joint ISO/CCITT.

These branches and those branches that fall below each category have short text strings and integers to identify them. Text strings describe object names, while integers allow computer software to create compact, encoded representations of the names.

Each MIB variable is assigned with an object identifier. The object identifier is the sequence of numeric labels on the nodes along a path from the root to the object. For example, the MIB variable tftpHost is indicated by the number 1. The object identifier for tftpHost is iso.org.dod.internet.private.enterprise.cisco.workgroup products.stack group.tftp group.tftpHost or .1.3.6.1.4.1.9.5.1.5.1. The last value is the number of the MIB variable tftpHost.

Tables

SNMP MIBs organize information into tables. When network management protocols use names of MIB objects in messages, each name has an appended suffix. This suffix is called an instance identifier. It identifies one occurrence of the associated MIB object. For simple scalar objects, the instance identifier 0 refers to the instance of the object with that name (for example, sysUpTime.0).

A MIB can also contain tables of related objects. For example, ifOperStatus is a MIB object inside the ifTable from the IF-MIB. It reports the operational state for an interface on a device. Because devices may have more than one interface, it is necessary to have more than one instance of ifOperStatus. This instance value is added to the end of the MIB object as the instance identifier (for example, ifOperStatus.2 reports the operational state for interface number 2).

Each object in a table is constructed with a set of clauses defined by the SMI. These clauses include the SYNTAX clause, MAX-ACCESS clause, STATUS clause, and DESCRIPTION clause.

An excerpt of the information in the VSAN table (known as vsanTable) from CISCO-VSAN-MIB follows:

vsanTable OBJECT-TYPE
SYNTAX     SEQUENCE OF VsanEntry
MAX-ACCESS not-accessible
STATUS     current
DESCRIPTION
"A table of VSANs configured on this device."
::= { vsanConfiguration 3 }
vsanEntry OBJECT-TYPE
SYNTAX     VsanEntry
MAX-ACCESS not-accessible
STATUS     current
DESCRIPTION
"An entry (conceptual row) in the vsanTable."
INDEX { vsanIndex }
::= { vsanTable 1 }
VsanEntry ::= SEQUENCE {
vsanIndex                 VsanIndex,
vsanName                  SnmpAdminString,
}

In the example, vsanTable contains two variables: vsanIndex and vsanName. (There are more values in the actual vsanTable.) The index for this table is the ID of the VSAN, or vsanIndex. With n number of VSANs configured, n rows are present in the table. If you want to retrieve the vsanName that matches VSAN ID 3 (vsanIndex is 3), then you would issue an SNMP get for vsanName.3.

SYNTAX Clause

The SYNTAX clause describes the format of the information, or value, that is returned when you monitor or set information in a MIB.

The Cisco MIBs are defined with the SNMPv2 Structure of Management Information version 2 (SNMPv2-SMI) defined in RFC 1902. Some examples of SNMPv2-SMI syntax are as follows:

Counter32

A nonnegative integer that increases until it reaches some maximum value. After reaching the maximum value, it rolls over to zero. For example, the variable ifInOctets, with a Counter32 syntax, counts the number of input octets on an interface.

Gauge32

A nonnegative integer that increases until it reaches some maximum value. After reaching the maximum value, it stays fixed (no rollover).

Counter64

A nonnegative 64-bit integer that increases until it reaches some maximum value. After reaching the maximum value, it rolls back to zero. Counter64 is used for MIB objects that can reach high values in a short period of time (for example, a packet counter for a Gigabit Ethernet port).

Integer32

An integer from -232 to 232-1.

IPAddress

An octet string that represents an IP address. For example, the variable hostConfigAddr indicates the IP address of the host that provided the host configuration file for a device.

Timeticks

A nonnegative integer that counts the hundredths of a second that have elapsed since an event. For example, the variable loctcpConnElapsed provides the length of time that a TCP connection has been established.

MAX-ACCESS Clause

The MAX-ACCESS clause identifies the maximum access level for the associated MIB object. This clause can represent one of the following five states: read-create, read-write, read-only, accessible-for-notify, and not-accessible.

read-create

You can read, modify, or create objects as rows in a table.

read-write

You can read or modify this object

read-only

You can only read this object.

accessible-for-notify

You cannot read or write to this object. SNMP notifications can send this object as part of their event information.

not-accessible

You cannot read or write to this object. Table indices are typically objects that are not accessible.

About Cisco MIB Files

MIB II is documented in RFC 1213, Management Information Base for Network Management of TCP/IP-based Internets: MIB-II. Portions of MIB-II have been updated since RFC 1213. See the IETF website Click Here for the latest updates to this MIB.

If your NMS cannot get requested information from a managed device, such as a Cisco switch, the MIB that allows that specific data collection might be missing. Typically, if an NMS cannot retrieve a particular MIB variable, either the NMS does not recognize the MIB variable, or the agent does not support the MIB variable. If the NMS does not recognize a specified MIB variable, you might need to load the MIB into the NMS, usually with a MIB compiler. For example, you might need to load the Cisco private MIB or the supported RFC MIB into the NMS to execute a specified data collection. If the agent does not support a specified MIB variable, you must find out what version of system software that you are running. Different software releases support different MIBs.

Note

Cisco and IETF MIBs are updated frequently. You should download the latest MIBs from Cisco.com whenever you upgrade your software.

- Cisco MIB File Directories

- MIB Loading Order

Cisco MIB File Directories

You can find Cisco MIBs at the following URL:

Click Here

Cisco MIB files are organized into two directories: SNMPv1-SMI MIBs are in the SNMPv1 directory and SNMPv2-SMI MIBs are in the SNMPv2 directory. Cisco also includes supported IETF-standard MIBs at this website. Use this support list to access and download the individual MIB files.

MIB Loading Order

Many MIBs use definitions that are defined in other MIBs. These definitions are listed in the IMPORTS section near the top of the MIB.

For example, if MIB B imports a definition from MIB A, some MIB compilers require you to load MIB A prior to loading MIB B. If you get the MIB loading order wrong, you might get an error message about what was imported, claiming it is undefined or not listed in IMPORTS. If you receive an error, look at the loading order of the MIB definitions from the IMPORTS of the MIB. Make sure that you have loaded all the preceding MIBs first.

Here is a list of MIBs from which many other MIBs import definitions. The MIBs are listed in the order in which you should load them:

- SNMPv2-SMI.my

- SNMPv2-TC.my

- SNMPv2-MIB.my

- RFC1213-MIB.my

- IF-MIB.my

- CISCO-SMI.my

- CISCO-TC.my

- CISCO-ST-TC.my

- ENTITY-MIB.my

If you load the MIBs in this order, you can eliminate most of your load-order definition problems. You can load most other MIBs (those not listed here) in any order.

Accessing and Downloading Cisco MIB Files

You can use either HTTP or passive FTP to access and download the Cisco MIB files.

Note

You can also access and download Cisco MIB files using the SNMP Object Navigator tool located at the following site:
Click Here .

You can use this tool to translate SNMP object identifiers (OIDs) into object names, search object names and descriptions, browse OID trees, and download MIB files.

- Enabling Passive FTP on Internet Explorer

- Using HTTP to Access and Download the MIB Files from Cisco.com

- Using Passive FTP to Access and Download the MIB Files

Enabling Passive FTP on Internet Explorer

Procedure

Step 1

Open Internet Explorer, and choose Tools > Internet Options.

Step 2

Click the Advanced tab at the top of the dialog box.

Step 3

Scroll down to the Browsing category.

Step 4

Check Use Passive FTP [for firewall and DSL modem compatibility] .

Step 5

Click OK to save this change.

Using HTTP to Access and Download the MIB Files from Cisco.com

Procedure

Step 1

Go to the following URL: Click Here

Step 2

Choose the category for your product and select the product from the drop-down menu.

Step 3

Select and save each MIB that you need to download from the product MIB support list.

Using Passive FTP to Access and Download the MIB Files

To access MIB files using passive FTP, you must know the names of the MIB files that you want to download. See the MIB support list for the names of supported MIBs. These steps assume that your passive FTP utility has UNIX-like commands.

Procedure

Step 1

Access ftp.cisco.com using passive FTP.

Step 2

Log in with your Cisco.com username and password, or as anonymous, with your e-mail address.

Step 3

Enter cd /pub/mibs/v2/ to change directories.

Step 4

Use the get command to copy the desired files to your local system.

Step 5

Use the quit command to exit passive FTP.

Understanding the ENTITY-MIB and Extensions

The ENTITY-MIB provides basic management and identification of physical and logical entities within a network device. Cisco NX-OS support for the ENTITY-MIB focuses on the physical entities within a device. This MIB provides details on each module, power supply, and fan tray within a switch chassis. It gives enough information to correctly map the containment of these entities within the switch, building up a chassis view.

Cisco has developed a number of private extensions to the ENTITY-MIB to provide more details for these physical entities. Each MIB extensions shares the common index value, entPhysicalIndex, which allows the management application developer to link information across multiple MIBs.

This table lists the Cisco MIB extensions that are linked to the ENTITY-MIB by entPhysical Index.

ENTITY-MIB Extensions

MIB

Description

CISCO-ENTITY-EXT-MIB

Extends the entityPhysicalTable for modules with processors. For each of these modules, this MIB provides memory statistics and LED information.

CISCO-ENTITY-FRU-CONTROL-MIB

Manages field-replaceable units, such as power supplies, fans, and modules.

CISCO-ENTITY-SENSOR-MIB

Provides sensor data for environmental monitors such as temperature gauges.

Extending the IF-MIB

The IF-MIB provides basic management status and control of interfaces and sublayers within a network device. Multiple standard and Cisco-specific MIBs use ifIndex from the IF-MIB to extend management for specific interface types.

Chapter 2. Configuring SNMP in APIC

- Configuring the SNMP Policy Using the GUI

Configuring the SNMP Policy Using the GUI

This procedure configures and enables the SNMP policy on ACI switches.

Before You Begin

To allow SNMP communications, you must configure the following:

- Configure an out-of-band contract allowing SNMP traffic. SNMP traffic typically uses UDP port 161 for SNMP requests.

- Configure the APIC out-of-band IP addresses in the 'mgmt' tenant. Although the out-of-band addresses are configured during APIC setup, the addresses must be explicitly configured in the 'mgmt' tenant before the out-of-band contract will take effect.

Procedure

Step 1

In the menu bar, click Fabric.

Step 2

In the submenu bar, click Fabric Policies.

Step 3

In the Navigation pane, expand Pod Policies.

Step 4

Under Pod Policies, expand Policies.

Step 5

Right-click SNMP and choose Create SNMP Policy.
As an alternative to creating a new SNMP policy, you can edit the default policy fields in the same manner as described in the following steps.

Step 6

In the SNMP policy dialog box, perform the following actions:

1. In the Name field, enter an SNMP policy name.

2. In the Admin State field, select Enabled.

3. In the Community Policies table, click the + icon, enter a Name and click Update.

4. Optional: In the SNMP v3 Users table, click the + icon, enter a Name, enter the user's authentication data, and click Update.
This step is needed only if SNMPv3 access is required.

Step 7

To configure allowed SNMP management stations, perform the following actions in the SNMP policy dialog box:

1. In the Client Group Policies table, click the + icon to open the Create SNMP Client Group Profile dialog box.

2. In the Name field, enter an SNMP client group profile name.

3. From the Associated Management EPG drop-down list, choose the management EPG.

4. In the Client Entries table, click the + icon.

5. Enter a client's name in the Name field, enter the client's IP address in the Address field, and click Update.
Note:
When an SNMP management station connects with APIC using SNMPv3, APIC does not enforce the client IP address specified in the SNMP client group profile. For SNMPv3, the management station must exist in the Client Entries list, but the IP address need not match, as the SNMPv3 credentials alone are sufficient for access.

Step 8

Click OK.

Step 9

Click Submit.

Step 10

Under Pod Policies, expand Policy Groups and choose a policy group or right-click Policy Groups and choose Create POD Policy Group.
You can create a new pod policy group or you can use an existing group. The pod policy group can contain other pod policies in addition to the SNMP policy.

Step 11

In the pod policy group dialog box, perform the following actions:

1. In the Name field, enter a pod policy group name.

2. From the SNMP Policy drop-down list, choose the SNMP policy that you configured and click Submit.

Step 12

Under Pod Policies, expand Profiles and click default.

Step 13

In the Work pane, from the Fabric Policy Group drop-down list, choose the pod policy group that you created.

Step 14

Click Submit.

Step 15

Click OK.

Configuring an SNMP Trap Destination Using the GUI

This procedure configures the host information for an SNMP manager that will receive SNMP trap notifications.

Note

ACI supports a maximum of 10 trap receivers. If you configure more than 10, some will not receive notifications.

Procedure

Step 1

In the menu bar, click Admin.

Step 2

In the submenu bar, click External Data Collectors.

Step 3

In the Navigation pane, expand Monitoring Destinations.

Step 4

Right-click SNMP and choose Create SNMP Monitoring Destination Group.

Step 5

In the Create SNMP Monitoring Destination Group dialog box, perform the following actions:

1. In the Name field, enter an SNMP destination name and click Next.

2. In the Create Destinations table, click the + icon to open the Create SNMP Trap Destination dialog box.

3. In the Host Name/IP field, enter an IP address or a fully qualified domain name for the destination host.
Note:
Cisco APIC Release 1.2(2) and later releases support IPv6 SNMP trap destinations.

4. Choose the Port number and SNMP Version for the destination.

5. For SNMP v1 or v2c destinations, enter one of the configured community names as Security Name and choose noauth as v3 Security Level.

6. For SNMP v3 destinations, enter one of the configured SNMP v3 user names as Security Name and choose the desired v3 Security Level.

7. From the Management EPG drop-down list, choose the management EPG.

8. Click OK.

9. Click Finish.

Configuring an SNMP Trap Source Using the GUI

This procedure selects and enables a source object within the fabric to generate SNMP trap notifications.

Procedure

Step 1

In the menu bar, click Fabric.

Step 2

In the submenu bar, click Fabric Policies.

Step 3

In the Navigation pane, expand Monitoring Policies. You can create an SNMP source in the Common Policy, the default policy, or you can create a new monitoring policy.

Step 4

Expand the desired monitoring policy and choose Callhome/SNMP/Syslog. If you chose the Common Policy, right-click Common Policy, choose Create SNMP Source, and follow the instructions below for that dialog box.

Step 5

In the Work pane, from the Monitoring Object drop-down list, choose ALL.

Step 6

From the Source Type drop-down list, choose SNMP.

Step 7

In the table, click the + icon to open the Create SNMP Source dialog box.

Step 8

In the Create SNMP Source dialog box, perform the following actions:

1. In the Name field, enter an SNMP policy name.

2. From the Dest Group drop-down list, choose an existing destination for sending notifications or choose Create SNMP Monitoring Destination Group to create a new destination. The steps for creating an SNMP destination group are described in a separate procedure.

3. Click Submit.

Associating the SNMP Context With a VRF Using the GUI

Each context (private network) supports its own instance of a context-specific MIB. To determine which MIBs are context-specific, see the Cisco ACI MIB Support List.

This procedure creates an SNMP context associated with a context within a tenant (VRF).

Procedure

Step 1

On the menu bar, click Tenants and, in the submenu, click the desired tenant.

Step 2

In the Navigation pane, expand Networking and Private Networks.

Step 3

Under Private Networks, select the context to be associated with the context-specific MIBs.

Step 4

Right-click the desired context and choose Create SNMP Context.

Step 5

In the Create SNMP Context dialog box, perform the following actions:

1. In the Name field, type a name for the SNMP context.

2. Optional: In the Community Profiles table, click the + icon, type the name of an existing community.
This step associates the SNMP context with an existing SNMP policy, simplifying the SNMP community string used to access the context-specific MIBs. The SNMP community must already be defined in the SNMP policy applied under Fabric > Fabric Policies > Pod Policies > SNMP.

Note:
With this association, the SNMP community becomes bound to this SNMP context and provides access only to context-specific OIDs, regardless of whether it previously provided access to fabric-level OIDs.

3. Click Submit.

Accessing the Context-Specific MIBs

A context (private network) supports its own instance of a context-specific MIB. You can access the context-specific MIBs using the snmpwalk command.

The following examples show how to access the context-specific BGP MIB using these example settings:

- The SNMP version is SNMPv2c, specified by snmpwalk -v2c.

- The example community name is cisco1.

- An SNMP context has been configured and named snmp-t2-context2 using the procedure described in Associating the SNMP Context With a VRF Using the GUI.

- The SNMP context configuration procedure contains an optional step to associate the SNMP context (snmp-t2-context2) with an existing community profile (cisco1). The examples include an example with this step and an example without this step.

- The SNMP agent of the context is 192.20.0.123.

Example 1

This example shows how to retrieve a non-context-specific MIB named ifTable.

linuxhost:> snmpwalk -v2c -c cisco1 192.20.0.123 ifTable

Example 2

This example shows how to retrieve a context-specific MIB named bgp when the SNMP context has not been associated with the community name. In this case, the context must be addressed using the format community-name@snmp-context-name.

linuxhost:> snmpwalk -v2c -c cisco1@snmp-t2-context2 192.20.0.123 bgp

Example 3

This example shows how to retrieve a context-specific MIB named bgp when the SNMP context has been associated with the community name. In this case, the SNMP context name can be omitted and the context is addressed using only the community name.

linuxhost:> snmpwalk -v2c -c cisco1 192.20.0.123 bgp

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)