Cisco Nexus 9000 Series NX-OS IP Fabric for Media Release Notes, Release 9.3(7)

 

This document describes the Cisco IP fabric for media solution, new hardware and software features, upgrade instructions, and caveats for Cisco NX-OS Release 9.3(7) software for use on the following: 

●      Cisco Nexus 92160YC-X switch

●      Cisco Nexus 9236C switch

●      Cisco Nexus 9272Q switch

●      Cisco Nexus 9364C switch

●      Cisco Nexus 93108TC-EX, 93180LC-EX, 93180YC-EX, 93108TC-FX, and 93180YC-FX switches

●      Cisco Nexus 93216TC-FX2, 93240YC-FX2, 93360YC-FX2, 9336C-FX2, 9348GC-FXP, 93180YC-FX3S, and N9K-C93180YC-FX3 switches

●      Cisco Nexus 9316D-GX, 93600CD-GX, and 9364C-GX switches

●      Cisco Nexus 9504 or 9508 switches with the N9K-X9636C-R, N9K-X9636C-RX, and N9K-X9636Q-R line cards

Table 1.             Online History Change

IP Fabric for Media

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, many cables, frequently stretched over long distances, is required, making it difficult and time-consuming to expand or change an SDI-based infrastructure.

Cisco’s IP fabric for media solution helps transition from an SDI router to an IP-based infrastructure. 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 solution uses Cisco Nexus 9000 Series switches in conjunction with the Cisco non-blocking multicast (NBM) algorithm (an intelligent traffic management algorithm) and with or without the Cisco DCNM Media Controller to provide a highly reliable (zero drop multicast), highly visible, highly secure, and highly available network.

Cisco Nexus 9000 Series NX-OS IP Fabric for Media Release 9.3(7) supports two deployment methods:

●      Spine-leaf topology—A single or multi-spine deployment method with variable flow size that allows the NBM fabric to form a multicast flow.

●      Single modular switch—An architecture suitable for fixed deployments, with the controller providing features such as flow visibility, security, and monitoring.

Supported Device Hardware

Table 2 lists the hardware that the Cisco Nexus 9000 Series NX-OS IP Fabric for Media Release 9.3(7) supports. For additional information about the supported hardware, see the Hardware Installation Guide for your Cisco Nexus 9000 Series device.

Table 2.        Cisco Nexus 9000 Series Hardware

New and Enhanced Features

There are no new and enhanced features for Cisco Nexus 9000 Series NX-OS IP Fabric for Media Release 9.3(7).

Open Issues

There are no open issues in Cisco Nexus 9000 Series NX-OS IP Fabric for Media Release 9.3(7).

Resolved Issues

There are no resolved issues in Cisco Nexus 9000 Series NX-OS IP Fabric for Media Release 9.3(7).

Limitations

When using ASM (IGMPv2), the bandwidth is reserved between the receiver leaf switch and the spine switch even when the sender is local to the receiver leaf switch.

NBM static OIF can include an SVI; however, an IGMP snooping entry must be manually created to force the traffic out of the Layer 2 physical interface.

To prevent packet drops for NBM flows, configure 5% more bandwidth than the traffic being sent.

Upgrade Instructions

Follow these steps to upgrade from a Cisco NX-OS 7.x or 9.x release to Cisco NX-OS Release 9.3(7) in an IP fabric for media deployment.

Note:      For Cisco Nexus 9504 and 9508 switches with -R line cards, you must upgrade from Cisco NX-OS Release 7.0(3)F3(4) to a 9.x release.

1.     Shut down the endpoint-facing ports on the switches.

2.     Disable NBM (using the no feature nbm command).

3.     Disable the ip pim pre-build-spt force command on the spine switches in your fabric.

4.     Disable PIM passive mode (using the no ip pim passive command).

5.     Upgrade the switch software from 7.x or 9.x to 9.3(7).

6.     For Cisco Nexus 9504 and 9508 switches with -R line cards, configure these TCAM carving commands in the following order and then reload the switch:

hardware access-list tcam region redirect_v6 0
hardware access-list tcam region ing-nbm 2048

7.     Upgrade DCNM.

8.     Configure PIM and MSDP, if applicable.

9.     Enable NBM (using the feature nbm command).

10.  Configure NBM policies using the CLI or DCNM. (See the Cisco Nexus 9000 Series IP Fabric for Media Solution Guide, Release 10.1(x).)

11.  If you're not using DCNM, disable IGMP static OIF and create an NBM flow definition to establish a flow.

12.  Re-enable all ports facing the endpoints.

Related Documentation

●      Cisco Nexus 9000 Series IP Fabric for Media Solution Guide, Release 10.1(x)

●      Cisco Nexus 9000 Series NX-OS Release Notes, Release 10.1(x)

●      Cisco Nexus 9000 Series NX-OS Verified Scalability Guide, Release 10.1(x)

●      Cisco Nexus 3000 and 9000 Series NX-API REST SDK User Guide and API Reference

●      Cisco DCNM Media Controller Configuration Guide, Release 11.5(1)

●      Cisco DCNM Installation and Upgrade Guide for Media Controller Deployment, Release 11.5(1)

●      The entire Cisco Nexus 9000 Series NX-OS documentation set is available at the following URL:

●      http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/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 nexus9k-docfeedback@cisco.com. We appreciate your feedback.

Legal Information

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: 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. (1721R)

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.

© 2021 Cisco Systems, Inc. All rights reserved.