Cisco Nexus 9200 Series User manual

Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide,
Release 7.0(3)I4(2)
First Published: 2016-07-15
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: [phone]
800 553-NETS (6387)
Fax: [phone]

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.
This product includes cryptographic software written by Eric Young ([email protected]).
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)
This product includes software written by Tim Hudson ([email protected]).
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)
©2016 Cisco Systems, Inc. All rights reserved.

CONTENTS
Preface Preface v
Audience v
Document Conventions v
Related Documentation for Cisco Nexus 9000 Series Switches vi
Documentation Feedback vi
Obtaining Documentation and Submitting a Service Request vii
CHAPTER 1 New and Changed Information 1
New and Changed Information 1
CHAPTER 2 Overview of Cisco’s IP Fabric for Media Solution 3
About the IP Fabric for Media Solution 3
Cisco Nexus 9200 Series Switches 3
IP Fabric for Media Topology 4
Failure Handling 4
Benefits of the IP Fabric for Media Solution 5
CHAPTER 3 Setting Up the IP Fabric for Media 7
Determining the Number and Types of Leaf Switches Required in the IP Fabric 7
Determining the Number of Achievable Flows in the IP Fabric 9
CHAPTER 4 Configuring IP Fabric for Media 11
Prerequisites 11
Guidelines and Limitations 11
Configuring NBM 12
Licensing Requirements 12
Configuring NBM 12
Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
iii

Verifying the NBM Configuration 14
Displaying NBM Flows and Flow Statistics 14
Configuring PTP for Media 15
Configuration Example 18
Related Documentation 18
Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
iv
Contents

Preface
This preface includes the following sections:
•Audience, page v
•Document Conventions, page v
•Related Documentation for Cisco Nexus 9000 Series Switches, page vi
•Documentation Feedback, page vi
•Obtaining Documentation and Submitting a Service Request, page vii
Audience
This publication is for network administrators who install, configure, and maintain Cisco Nexus switches.
Document Conventions
Command descriptions use the following conventions:
DescriptionConvention
Bold text indicates the commands and keywords that you enter literally
as shown.
bold
Italic text indicates arguments for which the user supplies the values.
Italic
Square brackets enclose an optional element (keyword or argument).[x]
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}
Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
v

DescriptionConvention
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.
[x {y | z}]
Indicates a variable for which you supply values, in context where italics
cannot be used.
variable
A nonquoted set of characters. Do not use quotation marks around the
string or the string will include the quotation marks.
string
Examples use the following conventions:
DescriptionConvention
Terminal sessions and information the switch displays are in screen font.screen font
Information you must enter is in boldface screen font.boldface screen font
Arguments for which you supply values are in italic screen font.
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.
!, #
Related Documentation for Cisco Nexus 9000 Series Switches
The entire Cisco Nexus 9000 Series switch documentation set is available at the following URL:
http://www.cisco.com/en/US/products/ps13386/tsd_products_support_series_home.html
Documentation Feedback
To provide technical feedback on this document, or to report an error or omission, please send your comments
to [email protected]. We appreciate your feedback.
Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
vi
Preface
Related Documentation for Cisco Nexus 9000 Series Switches

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: http://
www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical
documentation as an RSS feed and delivers content directly to your desktop using a reader application. The
RSS feeds are a free service.
Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
vii
Preface
Obtaining Documentation and Submitting a Service Request

Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
viii
Preface
Obtaining Documentation and Submitting a Service Request

CHAPTER 1
New and Changed Information
This chapter provides release-specific information for each new and changed feature in the Cisco Nexus
9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2).
•New and Changed Information, page 1
New and Changed Information
This table summarizes the new and changed features for the Cisco Nexus 9000 Series NX-OS IP Fabric for
Media Solution Guide, Release 7.0(3)I4(2) and tells you where they are documented.
Table 1: New and Changed Features for Cisco NX-OS Release 7.0(3)I4(2)
Where DocumentedChanged in
Release
DescriptionFeature
7.0(3)I4(2)First release.
.
IP fabric for media
Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
1

Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
2
New and Changed Information
New and Changed Information

CHAPTER 2
Overview of Cisco’s IP Fabric for Media Solution
This chapter contains information about Cisco's IP fabric for media solution.
•About the IP Fabric for Media Solution, page 3
•Cisco Nexus 9200 Series Switches, page 3
•IP Fabric for Media Topology, page 4
•Failure Handling, page 4
•Benefits of the IP Fabric for Media Solution, page 5
About the IP Fabric for Media Solution
Today, the broadcast industry uses a serial digital interface (SDI) router and SDI cables to transport video
and audio traffic. The SDI cables can carry only a single unidirectional signal. As a result, a large number of
cables, frequently stretched over long distances, are required, making it difficult and time-consuming to expand
or change an SDI-based infrastructure.
Cisco’s IP fabric for media solution replaces the SDI router in live production studios. In an IP-based
infrastructure, a single cable has the capacity to carry multiple bidirectional traffic flows and can support
different flow sizes without requiring changes to the physical infrastructure. The Cisco Nexus 9000 Series
switches in conjunction with the Cisco non-blocking multicast (NBM) algorithm (an intelligent traffic
management algorithm) provide a reliable, scalable IP fabric for the broadcast industry. In addition, this IP
fabric solution provides zero-drop multicast transport and support for PTP media profiles.
Cisco Nexus 9200 Series Switches
The following Cisco Nexus 9200 Series switches are used to transport video and audio traffic through the IP
fabric:
Number and Size of PortsCisco Nexus 9200 Series Switch
36 x 40/100-Gbps portsCisco Nexus 9236C switch
72 x 40-Gbps portsCisco Nexus 9272Q switch
Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
3

Number and Size of PortsCisco Nexus 9200 Series Switch
48 x 1/10/25-Gbps portsCisco Nexus 92160YC-X switch
IP Fabric for Media Topology
Cisco's IP fabric for media solution supports a spine-leaf topology that consists of one spine switch and up to
nine leaf switches.
The Cisco Nexus 9236C or 9272Q switch can serve as the spine switch. The Cisco Nexus 9236C, 9272Q,
and 92160YC-X switches can act as leaf switches. The topology supports any combination of these leaf
switches, including using just one type of leaf switch.
Figure 1: IP Fabric for Media Topology
Media sources and receivers connect to the leaf switches, and receivers initiate IGMP join requests to the leaf
switches in order to receive the media traffic.
Failure Handling
Cisco's IP fabric for media solution supports deterministic failure handling. When a link fails, the following
actions occur:
•When a link fails between a source leaf switch and the spine switch, the spine switch executes the NBM
algorithm and requests for flows on other links, provided sufficient bandwidth is available.
•When a link fails between the spine switch and a receiver leaf switch, the leaf switch executes the NBM
algorithm and requests for flows on other links, provided sufficient bandwidth is available.
•Flows that are not impacted are not moved to other links.
•When a link comes up, only new flows are forwarded across it, and previous flows are not moved back
to the link.
Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
4
Overview of Cisco’s IP Fabric for Media Solution
IP Fabric for Media Topology

Benefits of the IP Fabric for Media Solution
Cisco's IP fabric for media solution provides the following benefits:
•Replaces specialized hardware (SDI routers) with a general-purpose switching infrastructure.
•Supports various types and sizes of broadcasting equipment endpoints with port speeds up to 100 Gbps.
•Provides up to 3.6 Tb of bandwidth to support the latest video technologies, including 4K and 8K ultra
HD.
For example, the bandwidth needed to replace an existing SDI router can be calculated
as follows: a 1024 x 1024 SDI router with HD flows would require a bandwidth
equivalent to 1024 x 1.5 Gbps = 1.5 Tbps. Using a Cisco Nexus 9236C switch as the
spine switch, the topology would support a bandwidth of 3.6 Tbps, or the equivalent of
a 2400 x 2400 SDI router.
Note
•Scales horizontally. When you need more capacity, you can add a leaf switch to support more endpoints.
•Provides a deterministic network with zero packet loss, ultra low latency, and minimal jitter.
•Capable of synchronizing all media sources and receivers.
•Provides deterministic failure handling that sends traffic to the receiver when a link fails between a leaf
and the spine.
•Supports the coexistence of live and file-based traffic flows for post-production work.
•Offers increased network security.
•Provides a non-blocking network design to prevent the oversubscription of links.
•Requires no changes to the existing operator workflow.
Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
5
Overview of Cisco’s IP Fabric for Media Solution
Benefits of the IP Fabric for Media Solution

Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
6
Overview of Cisco’s IP Fabric for Media Solution
Benefits of the IP Fabric for Media Solution

CHAPTER 3
Setting Up the IP Fabric for Media
This chapter describes how to set up an IP fabric for media network.
•Determining the Number and Types of Leaf Switches Required in the IP Fabric, page 7
•Determining the Number of Achievable Flows in the IP Fabric, page 9
Determining the Number and Types of Leaf Switches Required
in the IP Fabric
The number and types of leaf switches required in your IP fabric depend on the number and types of endpoints
in your broadcasting center.
Follow these steps to help determine how many leaf switches you need:
1Count the number of endpoints (cameras, microphones, etc.) in your broadcasting center (for example, 90
10-Gbps endpoints and 30 40-Gbps endpoints).
2Determine the type of leaf switches required based on the type of endpoints in your broadcasting center.
•For 10-Gbps endpoints, you need to use the Cisco Nexus 92160YC-X leaf switches.
•For 40-Gbps endpoints, you can use the Cisco Nexus 9236C or 9272Q leaf switches.
3Determine the number of leaf switches required based on the number of endpoints and uplinks that each
leaf switch supports.
Table 2: Endpoints and Uplinks Supported per Leaf Switch
Uplink CapacityEndpoint CapacityLeaf Switch
10 x 100-Gbps (1000-Gbps)
uplinks
25 x 40-Gbps endpointsCisco Nexus 9236C switch
36 x 40-Gbps (1440-Gbps)
uplinks
36 x 40-Gbps endpointsCisco Nexus 9272Q switch
Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
7

Uplink CapacityEndpoint CapacityLeaf Switch
4 x 100-Gbps (400-Gbps) uplinks40 x 10-Gbps endpointsCisco Nexus 92160YC-X
switch
For example:
•For 90 10-Gbps endpoints, you need three Cisco Nexus 92160YC-X leaf switches because each
switch can support up to 40 10-Gbps endpoints.
•For 30 40-Gbps endpoints, you need two Cisco Nexus 9236C leaf switches because each switch can
support up to 25 40-Gbps endpoints or one Cisco Nexus 9272Q leaf switch because each switch can
support up to 36 40-Gbps endpoints.
4Make sure that the uplink bandwidth (toward the spine switch) and the downstream bandwidth (toward
the endpoints) are equal.
aUse this equation to determine the uplink bandwidth:
Uplink Capacity per Leaf Switch x Number of Leaf Switches = Uplink Bandwidth
For example:
400 Gbps (uplink capacity for each Cisco Nexus 92160YC-X switch) x 3 Cisco Nexus 92160YC-X
leaf switches = 1200-Gbps uplink bandwidth
1000 Gbps (uplink capacity for each Cisco Nexus 9236C switch) x 2 Cisco Nexus 9236C leaf switches
= 2000-Gbps uplink bandwidth
1200-Gbps uplink bandwidth (for 3 Cisco Nexus 92160YC-X leaf switches) + 1200-Gbps uplink
bandwidth (for 2 Cisco Nexus 9236C leaf switches) = 2400-Gbps total uplink bandwidth
bUse this equation to determine the downstream bandwidth:
Endpoint Capacity per Leaf Switch x Number of Leaf Switches = Downstream Bandwidth
For example:
40 x 10-Gbps (400-Gbps endpoint capacity) for each Cisco Nexus 92160YC-X leaf switch x 3 leaf
switches = 1200-Gbps downstream bandwidth
25 x 40-Gbps (1000-Gbps endpoint capacity) for each Cisco Nexus 9236C leaf switch x 2 leaf switches
= 2000-Gbps downstream bandwidth
1200-Gbps downstream bandwidth (for 3 Cisco Nexus 92160YC-X leaf switches) + 1200-Gbps
downstream bandwidth (for 2 Cisco Nexus 9236C leaf switches) = 2400-Gbps total downstream
bandwidth
5If the total uplink bandwidth and downstream bandwidth are equal, your topology is valid. You can now
determine the number of achievable flows. If the uplink bandwidth and downstream bandwidth are not
equal, you must rework your topology until it is valid.
Using the examples provided in this section, the topology would look like this:
Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
8
Setting Up the IP Fabric for Media
Determining the Number and Types of Leaf Switches Required in the IP Fabric

Determining the Number of Achievable Flows in the IP Fabric
Use this equation to determine the number of possible flows in your IP fabric:
Total Bandwidth ÷ Flow Size = Number of Achievable Flows
The flow size is configurable and is typically based on the type of video technology used in your broadcasting
center. For more information, see Configuring NBM.
For example:
3200-Gbps total bandwidth ÷ 1.5-Gbps flow size (for HD video) = 2133 possible flows
Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
9
Setting Up the IP Fabric for Media
Determining the Number of Achievable Flows in the IP Fabric

Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
10
Setting Up the IP Fabric for Media
Determining the Number of Achievable Flows in the IP Fabric

CHAPTER 4
Configuring IP Fabric for Media
This chapter describes how to configure the Cisco Nexus 9200 Series switches for Cisco's IP fabric for media
solution.
•Prerequisites, page 11
•Guidelines and Limitations, page 11
•Configuring NBM, page 12
•Configuring PTP for Media, page 15
•Configuration Example, page 18
•Related Documentation, page 18
Prerequisites
Cisco's IP fabric for media solution has the following prerequisites:
•The Cisco Nexus 9200 Series switches must be running Cisco NX-OS Release 7.0(3)I4(2) or a later
release.
•TCAM carving must be configured on the spine switch and each leaf switch using the hardware
access-list tcam region ing-ifacl 2048 command. The following example shows how you might provision
the TCAM. For more information on TCAM carving, see the Cisco Nexus 9000 Series NX-OS Security
Configuration Guide.
hardware access-list tcam region ing-l2-qos 0
hardware access-list tcam region ing-l3-vlan-qos 256
hardware access-list tcam region ing-racl 256
hardware access-list tcam region ing-ifacl 2048
Guidelines and Limitations
Cisco's IP fabric for media solution has the following guidelines and limitations:
•Only the Cisco Nexus 9236C and 9272Q can be spine switches.
•Only the Cisco Nexus 9236C, 9272Q, and 92160YC-X can be leaf switches.
Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
11

•The number of leaf switches depends on the number of uplinks used and the number of ports available
on the spine switch.
•The uplink bandwidth from each leaf switch must be equal to the bandwidth provided to the endpoints.
•If possible, Cisco recommends overprovisioning uplinks to account for failures.
•As a best practice, use Layer 3 ports that go to the endpoints with a /30 mask. Assign one IP address to
the endpoint and another to the switch interface.
•Cisco recommends that you choose the maximum bandwidth per flow. A constant or almost constant
bandwidth rate is assumed. If you expect bursts of traffic in your IP fabric, consider reserving this value
at a peak rate to prevent congestion.
•No two sources can transmit to the same multicast group at the same time. Also, when a given source
stops transmitting traffic, the multicast group must time out before a new source can start transmitting
to the same group.
Configuring NBM
Licensing Requirements
License RequirementProduct
The IP fabric for media solution requires an Enterprise Services license and a Network
Services license. For a complete explanation of the Cisco NX-OS licensing scheme and how
to obtain and apply licenses, see the Cisco NX-OS Licensing Guide.
Cisco
NX-OS
Configuring NBM
After you have set up the IP fabric, you must enable the NBM feature and set the flow bandwidth on the spine
switch and each leaf switch. The NBM feature ensures that the bandwidth that is coming into the fabric is
exactly the same as the bandwidth that is going out.
Before You Begin
Enable the SPT threshold infinity using the ip pim spt-threshold infinity command.
Procedure
PurposeCommand or Action
Enters global configuration mode.configure terminal
Example:
switch# configure terminal
switch(config)#
Step 1
Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Release 7.0(3)I4(2)
12
Configuring IP Fabric for Media
Configuring NBM