Chapter 1. Licensing Requirements for Cisco Programmable Fabric

Preface

Audience

Document Conventions

Related Documentation for Cisco Programmable Fabric

Obtaining Documentation and Submitting a Service Request

Copyright Page

Chapter 1. Licensing Requirements for Cisco Programmable Fabric

Following are the licensing requirements for Cisco Programmable Fabric with virtual extensible LAN (VXLAN) Border Gateway Protocol Ethernet VPN (BGP EVPN). Review the hardware and software components of your existing fabric with respect to the Cisco Programmable Fabric release requirements and compatibility constraints. Because Cisco Programmable Fabric implements an architectural solution with a switch topology, devices might be required to perform different roles when used in a Cisco Programmable Fabric implementation, and might be subject to new licensing requirements.

Product

License Requirement

Cisco Nexus 5600 Switches

- For a Cisco Nexus 5600 Switch as a Cisco Programmable Fabric spine, leaf, or border leaf, the Layer-3 Base Services Package (LAN_BASE_SERVICES_PKG) is required.

- For a Cisco Nexus 5600 Switch as a Cisco Programmable Fabric spine, leaf, or border leaf, the Enterprise Services Package (LAN_ENTERPRISE_SERVICES_PKG) is required.

For the Cisco NX-OS licensing scheme and how to obtain and apply licenses, see the Cisco NX-OS Licensing Guide.

Cisco Nexus 7000 Series Switches and Cisco Nexus 7700 Switches [1]

- For a Cisco Nexus 7000 Series Switch and Cisco Nexus 7700 Switch as a Cisco Programmable Fabric spine, leaf, border leaf, or border PE switch, the LAN Enterprise Services Package (LAN_ENTERPRISE_SERVICES_PKG) is required.

- For a Cisco Nexus 7000 Series Switch and Cisco Nexus 7700 Switch as a border PE, the Multiprotocol Label Switching (MPLS) Service Package (MPLS_PKG) is required. The border PE combines an MPLS PE and border leaf functionalities in a single box.

For the Cisco NX-OS licensing scheme and how to obtain and apply licenses, see the Cisco NX-OS Licensing Guide.

Cisco Nexus 9000 Series switches

- For a Cisco Nexus 9000 Series switch as a Cisco Programmable Fabric spine, leaf, or border leaf, the LAN Enterprise Services Package (LAN_ENTERPRISE_SERVICES_PKG) is required.

For the Cisco NX-OS licensing scheme and how to obtain and apply licenses, see the Cisco NX-OS Licensing Guide.

Cisco Data Center Network Manager (DCNM)

Note:
The switch feature licenses must be installed before you install the Cisco DCNM license.

Cisco DCNM includes a base functionality for Cisco Programmable Fabric management, LAN management, and limited SAN or Storage management. You do not have to install an Advanced feature license for the base functionality. The Advanced functionality, including performance monitoring, configuration archive, and extended SAN management, requires an Advanced feature license for LAN or SAN for each managed switch.

For example, if you require the Advanced LAN functionality, and have to manage a Cisco Nexus 5600 Switch, then you should order one process ID (PID) DCNM-LAN-N5K-K9 when you order the PID with the switch or DCNM-LAN-N5K-K9= when you order it as a spare PID.

All LAN operations use this type of Cisco DCNM Server-based license. If you need LAN and SAN functionalities for Cisco Nexus 7000 Series Switches and Cisco Nexus 7700 Switches, order the combination LAN and SAN ('LS') license [for example: DCNM-LS-N77-K9=]. The SAN and Storage functionalities are also available as switch based licenses, where the license is installed on the switch the same way a feature license is installed.

[1] The Cisco Nexus 7000 Series Switches and Cisco Nexus 7700 Switches as a Cisco Programmable Fabric leaf, border leaf, or border PE requires the F3 line card .

Preface

The Preface contains the following sections:

- Audience

- Document Conventions

- Related Documentation for Cisco Programmable Fabric

- Obtaining Documentation and Submitting a Service Request

Audience

This publication is for experienced network administrators who configure and maintain Cisco Programmable Fabric.

Document Conventions

Command descriptions use the following conventions:

Note

As part of our constant endeavor to remodel our documents to meet our customers' requirements, we have modified the manner in which we document configuration tasks. As a result of this, you may find a deviation in the style used to describe these tasks, with the newly included sections of the document following the new format.

Convention

Description

bold

Bold text indicates the commands and keywords that you enter literally as shown.

Italic

Italic text indicates arguments for which the user supplies the values.

[x]

Square brackets enclose an optional element (keyword or argument).

[x | y]

Square brackets enclosing keywords or arguments separated by a vertical bar indicate an optional choice.

{x | y}

Braces enclosing keywords or arguments separated by a vertical bar indicate a required choice.

[x {y | z}]

Nested set of square brackets or braces indicate optional or required choices within optional or required elements. Braces and a vertical bar within square brackets indicate a required choice within an optional element.

variable

Indicates a variable for which you supply values, in context where italics cannot be used.

string

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

Examples use the following conventions:

Convention

Description

screen font

Terminal sessions and information the switch displays are in screen font.

boldface screen font

Information you must enter is in boldface screen font.

italic screen font

Arguments for which you supply values are in italic screen font.

< >

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.

This document uses the following conventions:

Note

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

Caution

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

Related Documentation for Cisco Programmable Fabric

Software Downloads, Release, and General Information

Cisco Programmable Fabric Release Notes:

Click Here

Cisco DCNM Release Notes, Release 10:

Click Here

Install and Upgrade Guides

Cisco DCNM 10 Installation Guide:

Click Here

Configuration Guides

Cisco Programmable Fabric Configuration Guide:

Click Here

Cisco DCNM 10 Fundamentals Guide:

Click Here

Cisco Nexus 1000V VDP Configuration Guide, Release 5.x:

Click Here

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

Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The 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)