cisco nexus 9000 series nx-os ip fabric for media solution … › c › en › us › td › docs...

Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide,Releases 7.0(3)I4(5), 7.0(3)F2(1), and Later 7.x ReleasesFirst Published: 2016-12-22

Last Modified: 2018-02-09

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

C O N T E N T S

New and Changed Information 1C H A P T E R 1

New and Changed Information 1

Overview of Cisco’s IP Fabric for Media Solution 3C H A P T E R 2

About the IP Fabric for Media Solution 3

Deployment Types 3

Spine-Leaf Topology with DCNMMedia Controller 4

Spine-Leaf Topology without DCNMMedia Controller 4

Single Modular Switch Topology with DCNMMedia Controller 5

Single Modular Switch Topology without DCNMMedia Controller 5

IP Fabric for Media Solution Components 5

Cisco Nexus 9000 Series Switches 5

DCNMMedia Controller 7

Recommended Software Releases 8

Failure Handling 8

Benefits of the IP Fabric for Media Solution 8

Related Documentation 9

Setting Up the IP Fabric for Media 11C H A P T E R 3

Determining the Number and Types of Leaf Switches Required in the IP Fabric 11

Determining the Number of Achievable Flows in the IP Fabric 14

Configuring IP Fabric for Media 15C H A P T E R 4

Prerequisites 15

Guidelines and Limitations 16

Guidelines and Limitations for Unicast PTP 18

Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Releases 7.0(3)I4(5), 7.0(3)F2(1), and Later 7.x Releasesiii

Guidelines and Limitations for the DCNMMedia Controller 18

Licensing Requirements 19

Configuring NBM 20

Configuring NBM for a Spine-Leaf Deployment with DCNM 20

Configuring NBM for a Spine-Leaf Topology without DCNM 21

Configuring PIM on Spine and Leaf Switches 24

Configuring MSDP on Spine Switches 26

Configuring NBM for a Single Modular Switch with DCNM 27

Configuring NBM for a Single Modular Switch without DCNM 29

Enabling Multicast and Unicast Flows (Optional) 31

Verifying the NBM Configuration 35

Sample Output for Show Commands 36

Sample Output for Switches Running Cisco NX-OS Release 7.0(3)F2(1) or Later 36

Sample Output for Switches Running Cisco NX-OS Release 7.0(3)I6(1) or Later 37

Sample XML Output for Switches Running Cisco NX-OS Release 7.0(3)I7(1) or Later 38

Configuring Fabric and Host Interfaces 42

Configuring a Fabric Interface 42

Configuring a Layer 3 Host Interface 44

Configuring a Layer 2 with SVI Host Interface 45

Configuring PTP for Media (Optional) 48

Configuring Unicast PTP Peers 52

Media Controller 55C H A P T E R 5

Topology 56

PMN Hosts 57

Add PMN Hosts 58

Edit PMN Hosts 58

Delete PMN Hosts 59

Import PMN Hosts 59

Export PMN Hosts 59

Flow Alias 60

Add Flow Alias 60

Edit Flow Alias 61

Delete Flow Alias 61

Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Releases 7.0(3)I4(5), 7.0(3)F2(1), and Later 7.x Releasesiv

Contents

Export Flow Alias 61

Import Flow Alias 62

Policies 62

Host Policies 62

Add Host Policy 64

Edit Host Policy 65

Delete Host Policy 66

Import Host Policy 66

Export Host Policy 66

Flow Policies 67

Add Flow Policy 68

Edit Flow Policy 69

Delete Flow Policy 70

Import Flow Policy 70

Export Flow Policy 71

Flow Status 71

Events 75

Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Releases 7.0(3)I4(5), 7.0(3)F2(1), and Later 7.x Releasesv

Contents

Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Releases 7.0(3)I4(5), 7.0(3)F2(1), and Later 7.x Releasesvi

Contents

C H A P T E R 1New and Changed Information

This chapter provides release-specific information for each new and changed feature in the Cisco Nexus 9000Series NX-OS IP Fabric for Media Solution Guide.

• New and Changed Information, on page 1

New and Changed InformationThis table summarizes the new and changed features for the Cisco Nexus 9000 Series NX-OS IP Fabric forMedia Solution Guide and tells you where they are documented.

Table 1: New and Changed Features

Where DocumentedChanged inRelease

DescriptionFeature

Overview of Cisco’s IP Fabricfor Media Solution, on page 3

Configuring IP Fabric forMedia, on page 15

7.0(3)F2(2)Added support for the Cisco Nexus9508 switch (with theN9K-X9636C-R andN9K-X9636Q-R line cards) as asingle modular switch with theDCNMMedia Controller.

IP fabric for media

Configuring a Layer 2 with SVIHost Interface, on page 45

7.0(3)F2(2)Added support for connecting anendpoint to a Layer 2 port with anSVI.

IP fabric for media



7.0(3)F2(1)Added support for the Cisco Nexus9508 switch (with theN9K-X9636C-R andN9K-X9636Q-R line cards) as aspine switch or as a single modularswitch.

IP fabric for media



7.0(3)I7(3)Added support for the Cisco Nexus9364C as a spine or leaf switch andthe Cisco Nexus 9348GC-FXP,93108TC-FX, and 93180YC-FX asleaf switches.

IP fabric for media

Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Releases 7.0(3)I4(5), 7.0(3)F2(1), and Later 7.x Releases1

Where DocumentedChanged inRelease

DescriptionFeature

Deployment Types, on page 3

Configuring NBM for aSpine-Leaf Topology withoutDCNM, on page 21

7.0(3)I7(3)Added support for PIM activemode,which supports a spine-leaf topologywith variable flow size without theDCNMMedia Controller.

IP fabric for media

Configuring NBM for aSpine-Leaf Deployment withDCNM, on page 20

7.0(3)I7(2)Added the ability to configure leafswitches as border leafs in order toconnect multiple fabrics togetherand to support the exchange ofmedia flows between an IP fabricfor media and external systems.

IP fabric for media

Media ControllerDCNM 10.4(2)Introduced this feature to supportthe exchange of media flowsbetween an IP fabric for media andexternal systems.

PIM router

Prerequisites, on page 15

Guidelines and Limitations, onpage 16

7.0(3)I7(1)Added support for Source-SpecificMulticast (SSM) groups so twosources can transmit to the samemulticast group.

IP fabric for media

EnablingMulticast and UnicastFlows (Optional), on page 31

7.0(3)I7(1)Added queuing support for bothmulticast and unicast flows.

IP fabric for media

Sample XML Output forSwitches Running CiscoNX-OS Release 7.0(3)I7(1) orLater, on page 38

7.0(3)I7(1)Added XML support for the NBMshow commands.

IP fabric for media



7.0(3)I6(1)Added support for the Cisco Nexus93180LC-EX switch as a leaf switchand the Cisco Nexus 9500 Seriesswitches (with theN9K-X9732C-EX,N9K-X9736C-EX, andN9K-X97160YC-EX line cards) asspine switches or as single modularswitches.

IP fabric for media

Media ControllerDCNM 10.2(1)Introduced these features.Flow alias andbandwidth tracking

7.0(3)I4(5)First release with DCNMMediaController.

IP fabric for media


New and Changed InformationNew and Changed Information

C H A P T E R 2Overview 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, on page 3• IP Fabric for Media Solution Components, on page 5• Failure Handling, on page 8• Benefits of the IP Fabric for Media Solution, on page 8• Related Documentation, on page 9

About the IP Fabric for Media SolutionToday, the broadcast industry uses a serial digital interface (SDI) router and SDI cables to transport videoand audio traffic. The SDI cables can carry only a single unidirectional signal. As a result, many cables,frequently stretched over long distances, are required, making it difficult and time-consuming to expand orchange an SDI-based infrastructure.

Cisco’s IP fabric for media solution helps transition from an SDI router to an IP-based infrastructure. In anIP-based infrastructure, a single cable can carry multiple bidirectional traffic flows and can support differentflow sizes without requiring changes to the physical infrastructure.

The IP fabric for media solution consists of a flexible spine and leaf architecture or a single modular switchtopology. The solution uses Cisco Nexus 9000 Series switches with the Cisco non-blocking multicast (NBM)algorithm (an intelligent traffic management algorithm) and with or without the Cisco Data Center NetworkManager (DCNM)Media Controller. Using open APIs, the Cisco DCNMMedia Controller can integrate withvarious broadcast controllers. The solution provides a highly reliable (zero drop multicast), highly visible,highly secure, and highly available network.

Deployment TypesCisco’s IP fabric for media solution supports the following types of deployments:

• Spine-leaf topology with DCNMMedia Controller—Flexible architecture for large-scale deploymentsthat are typically seen in an IP studio.

• Spine-leaf topology without DCNMMedia Controller—Single or multi-spine deployment method withvariable flow size without the DCNMMedia Controller.


Cisco NX-OS Release 7.0(3)I7(3) supports only this deployment method.Note

• Single modular switch with DCNMMedia Controller—Architecture suitable for fixed deployments,with the controller providing features such as flow visibility, security, and monitoring.

• Single modular switch without DCNMMedia Controller—Simple deployment method for environmentssuch as outside broadcasting (OB) vans.

Spine-Leaf Topology with DCNM Media ControllerCisco's IP fabric for media solution supports a spine-leaf topology that consists of multiple spine and leafswitches and the DCNMMedia Controller. The topology supports any combination of leaf switches, includingusing just one type of leaf switch.

Media sources and receivers connect to the leaf switches, and receivers initiate IGMP join requests to the leafswitches in order to receive the media traffic.

Spine-Leaf Topology without DCNM Media ControllerBeginning with Cisco NX-OS Release 7.0(3)I7(3), Cisco's IP fabric for media solution supports a spine-leaftopology that consists of spine and leaf switches without the DCNMMedia Controller. This topology providesmulticast flow setup intelligence within the fabric.


Overview of Cisco’s IP Fabric for Media SolutionSpine-Leaf Topology with DCNM Media Controller

Single Modular Switch Topology with DCNM Media ControllerCisco's IP fabric for media solution supports a single modular switch topology that consists of one CiscoNexus 9500 Series switch that runs Cisco NX-OS Release 7.0(3)F2(2) or a later release or Cisco NX-OSRelease 7.0(3)I6(1) or a later release and uses the DCNMMedia Controller.

Single Modular Switch Topology without DCNM Media ControllerCisco's IP fabric for media solution supports a single modular switch topology that consists of one CiscoNexus 9500 Series switch that runs Cisco NX-OS Release 7.0(3)F2(1) or a later release or Cisco NX-OSRelease 7.0(3)I6(1) or a later release and does not use the DCNMMedia Controller.

IP Fabric for Media Solution Components

Cisco Nexus 9000 Series SwitchesThe following Cisco Nexus 9000 Series switches are used to transport video and audio traffic through the IPfabric:


Overview of Cisco’s IP Fabric for Media SolutionSingle Modular Switch Topology with DCNM Media Controller

Role in TopologyInitial Cisco NX-OSRelease

Number and Size of PortsCisco Nexus 9000 SeriesSwitch

Spine or leaf in spine-leaftopology with or withoutDCNMMedia Controller

7.0(3)I4(5)*36 x 40/100-Gbps portsCisco Nexus 9236Cswitch

Spine or leaf in spine-leaftopology with or withoutDCNMMedia Controller

7.0(3)I4(5)*72 x 40-Gbps portsCisco Nexus 9272Qswitch

Leaf in spine-leaftopology with or withoutDCNMMedia Controller

7.0(3)I4(5)*48 x 1/10/25-Gbps portsCisco Nexus 92160YC-Xswitch


7.0(3)I7(3)48 x 100-Mbps/1-Gbpsports

Cisco Nexus9348GC-FXP switch

Spine in spine-leaftopology with or withoutDCNMMedia Controller

7.0(3)I7(3)64 x 40/100-Gbps portsCisco Nexus 9364Cswitch


7.0(3)I4(5)*48 x 1/10-Gbps portsCisco Nexus93108TC-EX switch


7.0(3)I7(3)48 x 10-Gbps portsCisco Nexus93108TC-FX switch


7.0(3)I6(1)32 x 40/100-Gbps portsCisco Nexus93180LC-EX switch


7.0(3)I4(5)*48 x 1/10/25-Gbps portsCisco Nexus93180YC-EX switch


7.0(3)I7(3)48 x 10/25-Gbps portsCisco Nexus93180YC-FX switch


Overview of Cisco’s IP Fabric for Media SolutionCisco Nexus 9000 Series Switches

Role in TopologyInitial Cisco NX-OSRelease

Number and Size of PortsCisco Nexus 9000 SeriesSwitch

Spine in spine-leaftopology with DCNMMedia Controller

Single modular switchwithout DCNMMediaController, beginningwithCisco NX-OS Release7.0(3)F2(1)

Single modular switchwith DCNMMediaController, beginningwithCisco NX-OS Release7.0(3)F2(2)

7.0(3)F2(1)36 x 100-Gbps ports (forN9K-X9636C-R linecards)**

36 x 40-Gbps ports (forN9K-X9636Q-R linecards)**

CiscoNexus 9504 or 9508switch with the followingline cards:

• N9K-X9636C-R

• N9K-X9636Q-R

Single modular switchwith or without DCNMMedia Controller

7.0(3)I6(1)32 x 40-Gbps ports (forN9K-X9732C-EX linecards)

36 x 40-Gbps ports (forN9K-X9736C-EX linecards)

48 x 10/25-Gbps ports(for N9K-X97160YC-EXline cards)

Cisco Nexus 9500 Seriesswitches with thefollowing line cards:

• N9K-X9732C-EX

• N9K-X9736C-EX

• N9K-X97160YC-EX

*Leaf switches must run Cisco NX-OS 7.0(3)I6(1) or a later release when used with spine switches that arerunning Cisco NX-OS Release 7.0(3)F2(1) or a later release.

**For the latest breakout and optics support, see https://www.cisco.com/c/en/us/support/interfaces-modules/transceiver-modules/products-device-support-tables-list.html.

DCNM Media ControllerThrough open APIs, the Cisco DCNMMedia Controller seamlessly integrates with the broadcast controllerand provides a similar operator workflow with all the benefits of an IP-based infrastructure. The DCNMMedia Controller features an intuitive GUI that enables you to configure your IP fabric using predefinedtemplates that are designed for media networks.

The DCNMMedia Controller enables you to do the following:

• Configure secure generic or multicast-specific policies for individual hosts and allow or deny hosts basedon their role.

• Configure secure multicast-specific policies for multiple hosts and flows.

• View the traffic flow and bandwidth utilization to identify problem areas (such as link failures oroversubscriptions) in your fabric.

• Use flow analytics to measure and store bit rates and to display the details for individual traffic flows.


Overview of Cisco’s IP Fabric for Media SolutionDCNM Media Controller

https://www.cisco.com/c/en/us/support/interfaces-modules/transceiver-modules/products-device-support-tables-list.html

https://www.cisco.com/c/en/us/support/interfaces-modules/transceiver-modules/products-device-support-tables-list.html

• View an audit log of actions that are performed on the fabric.

Recommended Software ReleasesThe following software releases are recommended for deployments with or without the DCNMMediaController.

Recommended ReleaseDeployment Method

NX-OS 7.0(3)I7(2) or 7.0(3)F3(3)

DCNM 10.4(2)

With the DCNMMedia Controller

NX-OS 7.0(3)I7(3)Without the DCNMMedia Controller

Failure HandlingCisco's IP fabric for media solution supports deterministic failure handling.

During a link or switch failure, the affected flows are moved to alternate links, provided sufficient bandwidthis available. With SMPTE 2022-7, redundancy is built on the endpoints, which ensures that the link or switchfailure does not affect production traffic.

Benefits of the IP Fabric for Media SolutionCisco'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.

• Supports the latest video technologies, including 4K and 8K ultra HD.

• 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 leafand the spine.

• Supports the coexistence of live and file-based traffic flows for postproduction 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.


Overview of Cisco’s IP Fabric for Media SolutionRecommended Software Releases

Related DocumentationDocument TitleRelated Topic

Cisco IP Fabric for Media Solution videoIP fabric for media

Cisco DCNM Installation Guide

Cisco DCNM online help

Cisco DCNM API Reference

Cisco DCNMMedia Controller

Cisco Nexus 9000 Series NX-OS IP Fabric forMediaRelease Notes

Cisco NX-OS release information

Cisco Nexus 9000 Series NX-OS Software Upgradeand Downgrade Guide

Cisco NX-OS software upgrades

Cisco Nexus 9000 Series NX-OS Multicast RoutingConfiguration Guide

IGMP snooping and PIM

Cisco Nexus 9000 Series NX-OS Unicast RoutingConfiguration Guide

OSPF

CiscoNexus 9000 SeriesNX-OSSystemManagementConfiguration Guide

PTP

Cisco Nexus 9000 Series NX-OS Quality of ServiceConfiguration Guide

QoS

Cisco Nexus 9000 Series NX-OS SecurityConfiguration Guide

TCAM carving

Cisco Nexus 9000 Series NX-OS Layer 2 SwitchingConfiguration Guide

VLANs


Overview of Cisco’s IP Fabric for Media SolutionRelated Documentation

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/hw/videos/ip_fabric_for_media/cisco_ip_fabric_for_media_solution2.html

http://www.cisco.com/c/en/us/support/cloud-systems-management/prime-data-center-network-manager/products-installation-guides-list.html

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/DCNM_OLH/Web_Client/b_DCNM_web_client_olh/Media_Controller.html

https://developer.cisco.com/site/data-center-network-manager/index.gsp#rest-apis

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-release-notes-list.html

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-release-notes-list.html

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/upgrade/guide/b_Cisco_Nexus_9000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guide_Release_7x.html

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/upgrade/guide/b_Cisco_Nexus_9000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guide_Release_7x.html

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/multicast/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Multicast_Routing_Configuration_Guide_7x.html


https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/unicast/configuration/guide/l3_cli_nxos.html

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/unicast/configuration/guide/l3_cli_nxos.html

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/system_management/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_System_Management_Configuration_Guide_7x/b_Cisco_Nexus_9000_Series_NX-OS_System_Management_Configuration_Guide_7x_chapter_0100.html

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/system_management/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_System_Management_Configuration_Guide_7x/b_Cisco_Nexus_9000_Series_NX-OS_System_Management_Configuration_Guide_7x_chapter_0100.html

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/qos/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Quality_of_Service_Configuration_Guide_7x.html

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/qos/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Quality_of_Service_Configuration_Guide_7x.html

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/security/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Security_Configuration_Guide_7x.html

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/security/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Security_Configuration_Guide_7x.html

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/layer2/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Layer_2_Switching_Configuration_Guide_7x.html



Overview of Cisco’s IP Fabric for Media SolutionRelated Documentation

C H A P T E R 3Setting 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, on page 11• Determining the Number of Achievable Flows in the IP Fabric, on page 14

Determining the Number and Types of Leaf Switches Requiredin the IP Fabric

The number and types of leaf switches required in your IP fabric depend on the number and types of endpointsin your broadcasting center.

Follow these steps to help determine how many leaf switches you need:

1. Count the number of endpoints (cameras, microphones, and so on) in your broadcasting center (for example,360 10-Gbps endpoints and 50 40-Gbps endpoints).

2. Determine the type of leaf switches required based on the type of endpoints in your broadcasting center.

• For 1-Gbps endpoints, use the Cisco Nexus 9348GC-FXP leaf switch.

• For 10-Gbps endpoints, use the CiscoNexus 92160YC-X, 93108TC-EX, 93108TC-FX, 93180YC-FX,or 93180YC-EX leaf switches.

• For 40-Gbps endpoints, use the Cisco Nexus 9236C, 9272Q, 9364C, or 93180LC-EX leaf switches.

3. Determine the number of leaf switches required based on the number of endpoints and uplinks that eachleaf switch supports.

The uplink and downlink numbers in the following table are a recommendation. There are no technicallimitations to use certain ports as uplinks or host-facing links.

Note


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 endpointsCisco Nexus 9272Q switch

4 x 100-Gbps (400-Gbps) uplinks40 x 10-Gbps endpointsCisco Nexus 92160YC-Xswitch

2 x 100-Gbps (200-Gbps) uplinks48 x 1-Gbps/100-Mbps endpointsCisco Nexus 9348GC-FXPswitch


Not applicableCisco Nexus 9364C switch1

6 x 100-Gbps (600-Gbps) uplinks48 x 10-Gbps endpointsCisco Nexus 93108TC-EXswitch

6 x 100-Gbps (600-Gbps) uplinks48 x 1/10-Gbps endpointsCisco Nexus 93108TC-FXswitch

4 x 100-Gbps (400-Gbps) uplinks32 x 40-Gbps endpointsCisco Nexus 93180LC-EXswitch

6 x 100-Gbps (600-Gbps) uplinks48 x 10-Gbps endpointsCisco Nexus 93180YC-EXswitch

6 x 100-Gbps (600-Gbps) uplinks48 x 10/25-Gbps endpointsCisco Nexus 93180YC-FXswitch

1 The Cisco Nexus 9364C switch does not support breakout.

For example:

• For 360 10-Gbps endpoints, you need eight Cisco Nexus 93180YC-EX leaf switches because eachswitch can support up to 48 10-Gbps endpoints.

• For 50 40-Gbps endpoints, you need two Cisco Nexus 9236C leaf switches because each switch cansupport up to 25 40-Gbps endpoints.

4. Make sure that the uplink bandwidth (toward the spine switch) is greater than or equal to the downstreambandwidth (toward the endpoints).

a. Use this equation to determine the uplink bandwidth:

Uplink Capacity per Leaf Switch x Number of Leaf Switches = Uplink Bandwidth

For example:

600 Gbps (uplink capacity for each Cisco Nexus 93180YC-EX switch) x eight Cisco Nexus93180YC-EX leaf switches = 4800-Gbps uplink bandwidth


Setting Up the IP Fabric for MediaDetermining the Number and Types of Leaf Switches Required in the IP Fabric

1000 Gbps (uplink capacity for each Cisco Nexus 9236C switch) x two Cisco Nexus 9236C leafswitches = 2000-Gbps uplink bandwidth

4800-Gbps uplink bandwidth (for eight Cisco Nexus 93180YC-EX leaf switches) + 2000-Gbps uplinkbandwidth (for two Cisco Nexus 9236C leaf switches) = 6800-Gbps total uplink bandwidth

b. Use this equation to determine the downstream bandwidth:

Endpoint Capacity per Leaf Switch x Number of Leaf Switches = Downstream Bandwidth

For example:

48 x 10 Gbps (480-Gbps endpoint capacity) for each Cisco Nexus 93180YC-EX leaf switch x eightleaf switches = 3840-Gbps downstream bandwidth

25 x 40 Gbps (1000-Gbps endpoint capacity) for each Cisco Nexus 9236C leaf switch x two leafswitches = 2000-Gbps downstream bandwidth

3840-Gbps downstream bandwidth (for eight Cisco Nexus 93180YC-EX leaf switches) + 2000-Gbpsdownstream bandwidth (for two Cisco Nexus 9236C leaf switches) = 5840-Gbps total downstreambandwidth

5. If the total uplink bandwidth is greater than or equal to the total downstream bandwidth, your topologyis valid. You can now determine the number of achievable flows. If the uplink bandwidth is less than thedownstream bandwidth, rework your topology until the upstream bandwidth is equal to or greater thanthe downstream bandwidth.

The following topology uses the examples in this section:

The following diagram shows an example topology with a Cisco Nexus 9508 spine switch and anN9K-X9636C-R line card:


Setting Up the IP Fabric for MediaDetermining the Number and Types of Leaf Switches Required in the IP Fabric

Determining the Number of Achievable Flows in the IP FabricUse 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 that is used in yourbroadcasting center.

Table 3: Flow Sizes Per Video Technology

Flow SizeTechnology

1.5 Gbps (1500 Mbps)HD video

3 Gbps (3000 Mbps)3G HD video

12 Gbps (12,000 Mbps)4K ultra HD video

48 Gbps (48,000 Mbps)8K ultra HD video

For example:

7200-Gbps total bandwidth ÷ 1.5-Gbps flow size (for HD video) = 4800 possible flows


Setting Up the IP Fabric for MediaDetermining the Number of Achievable Flows in the IP Fabric

C H A P T E R 4Configuring IP Fabric for Media

This chapter describes how to configure the Cisco Nexus 9000 Series switches for Cisco's IP fabric for mediasolution.

• Prerequisites, on page 15• Guidelines and Limitations, on page 16• Licensing Requirements, on page 19• Configuring NBM, on page 20• Configuring Fabric and Host Interfaces, on page 42• Configuring PTP for Media (Optional), on page 48• Configuring Unicast PTP Peers, on page 52

PrerequisitesCisco's IP fabric for media solution has the following prerequisites:

• Cisco Nexus 9200 and 9300 Series leaf and spine switches must be running Cisco NX-OS Release7.0(3)I4(5) or a later release.

Leaf switches must run Cisco NX-OS Release 7.0(3)I6(1) or a later release whenused with spine switches that are running Cisco NX-OS Release 7.0(3)F2(1) ora later release.

Note

• Cisco Nexus 9500 Series spine switches (with N9K-X9732C-EX, N9K-X9736C-EX, andN9K-X97160YC-EX line cards) must be running Cisco NX-OS Release 7.0(3)I6(1) or a later release.

• The Cisco Nexus 9508 spine switch (with N9K-X9636C-R and N9K-X9636Q-R line cards) must berunning Cisco NX-OS Release 7.0(3)F2(1) or a later release.

• TCAM carvingmust be configured on leaf switches using the hardware access-list tcam region ing-racl512 and hardware access-list tcam region ing-nbm 1536 commands. For more information on TCAMcarving, see the Cisco Nexus 9000 Series NX-OS Security Configuration Guide.

• For Cisco Nexus 9500 Series switches with N9K-X9732C-EX, N9K-X9736C-EX, andN9K-X97160YC-EX line cards, enable the multicast NBM template using the system routingtemplate-multicast-nbm command. For more information, see the Cisco Nexus 9000 Series MulticastRouting Configuration Guide.


http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/security/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Security_Configuration_Guide_7x/b_Cisco_Nexus_9000_Series_NX-OS_Security_Configuration_Guide_7x_chapter_01001.html



• To use PIM SSM, which is supported beginning with Cisco NX-OS Release 7.0(3)I7(1), you must definean SSM group on the switch. For more information, see the Cisco Nexus 9000 Series Multicast RoutingConfiguration Guide.

The default SSM multicast group range is 232.0.0.0/8. If you do not want to usethe default range, you must use the ip pim ssm command to change it across thefabric.

Note

• For controller-based deployments, you must install one of the following Cisco DCNM Releases. Forinstallation instructions, see the Cisco DCNM Installation Guide for your DCNM release.

Cisco DCNM ReleaseCisco NX-OS Release Running on Switches

10.17.0(3)I4(5)

10.2(1) or later7.0(3)F2(1) or a later release

or

7.0(3)I6(1) or a later release

10.4(2) or later7.0(3)I7(2) or a later release

• After the DCNMOVA file is installed, you must SSH into the DCNMVM as root and enter the appmgrset-mode media-controller command on the DCNM server to enable the DCNMMedia Controller.

Guidelines and LimitationsCisco's IP fabric for media solution has the following guidelines and limitations:

• The number of leaf switches depends on the number of uplinks that are used and the number of portsavailable on the spine switch.

• Make sure that there is always connectivity to the controller by ensuring redundant paths.

• Cisco Nexus 9508 switches with the N9K-X9636C-R and N9K-X9636Q-R line cards do not supportPTP, policing, DSCP remarking, and flow statistics.

• We recommend using a Layer 3 routed port to an endpoint.

• For a deployment of Cisco Nexus 9508 switches with N9K-X9636C-R and N9K-X9636Q-R line cardsand with SVIs and endpoints that are connected using a Layer 2 port, the maximum number of flows is2000.

• SVIs are not supported for CiscoNexus 9500 platform switcheswithN9K-X9732C-EX,N9K-X9736C-EX,and N9K-X97160YC-EX line cards. (This restriction does not apply to Cisco Nexus 9508 switches withN9K-X9636C-R and N9K-X9636Q-R line cards.)

• For Cisco Nexus 9508 switches with N9K-X9636C-R and N9K-X9636Q-R line cards, six fabric modulesare needed when all six ports of a 100G line card are connected to an ASIC and forwarding multicasttraffic with full capacity (600G). Five fabric modules are needed when all 12 ports of 40G line cards areconnected to an ASIC and forwarding multicast traffic with full capacity (480G).


Configuring IP Fabric for MediaGuidelines and Limitations




• To ensure non-blocking performance, make sure that the uplink bandwidth from each leaf switch isgreater than or equal to the bandwidth provided to the endpoints.

• When possible, spread the endpoints across different leaf switches such that there is an equal distributionof sources and receivers on all leaf switches.

• If possible, we recommend 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 tothe endpoint and another to the switch interface.

• Design redundant IP networks (2022-7), and do not connect the two networks together. They are meantto be independent.

• The network is designed primarily to carry multicast flows. Ensure that there is minimal unicast trafficas the bandwidth management does not track unicast flows.

• The solution supports IGMPv2 and IGMPv3 joins and PIM Any Source Multicast (ASM), which allowsonly one source to send to a given multicast group. Beginning with Cisco NX-OS Release 7.0(3)I7(1),the solution also supports PIM SSM, which allows two sources to transmit to the same multicast groupat once.

• Statistics are available only on the switch where senders are connected.

• The host cannot be connected to the spine.

• Other than the configuration required to set up the fabric, do not use custom ACL or QoS policies. Suchpolicies are pushed from the host or flow policy in DCNM (and not from CLI commands).

• Once the host is deleted from DCNM, the switch does not repunt the ARP to DCNM. To repunt the ARP,use the clear ip arp force-delete host-ip-address command on the switch.

• Do not use CLI commands to modify any policy that is pushed from DCNM. Any modifications mustbe made using DCNM.

• NBM is not supported with enhanced ISSU. Do not use the [no] boot mode lxc command in IP fabricfor media setups.

• Before moving from a noncontroller deployment to a controller deployment (or conversely), delete theexisting configuration from the switches (by performing a write erase and reload) and then reconfigurethe switches using POAP or Cisco NX-OS CLI commands.

• The exchange of flows between the fabric and an external network using a border leaf works only withthe PIM SSM range. There is no support for flow exchange with PIM ASM.

• To conserve resources when running Cisco NX-OS Release 7.0(3)I7(2) or a later release, we recommenddisabling statistics when using the service-policy type qos command.

• Cisco NX-OS Release 7.0(3)I7(2) supports only one border leaf per fabric. Multiple border leafs perfabric are not supported. In a 2022-7/Redundant Network deployment, each fabric can have a singleborder leaf.

• Cisco NX-OS Release 7.0(3)I7(3) supports only the spine-leaf topology without the DCNMMediaController. To use a different deployment method, use a release prior to Cisco NX-OSRelease 7.0(3)I7(3).


Configuring IP Fabric for MediaGuidelines and Limitations

Guidelines and Limitations for Unicast PTPThe following guidelines and limitations apply to unicast PTP:

• Configure every unicast PTP interface with a unique PTP unicast source address.

• The global PTP source and the unicast interface PTP source should not be the same.

• Unicast and multicast are not supported on the same interface.

• Unicast PTP is supported only for the following platforms:

• Cisco Nexus 9236C, 9272Q, and 92160YC-X switches

• Cisco Nexus 9348GC-FXP, 9364C, 93108TC-FX, and 93180YC-FX switches

• Cisco Nexus 9500 Series switches with the N9K-X9732C-EX, N9K-X9736C-EX, andN9K-X97160YC-EX line cards

Guidelines and Limitations for the DCNM Media ControllerThe following guidelines and limitations apply to DCNM in general:

• Make sure that there is always connectivity to the controller by ensuring redundant paths.

• Do not use CLI commands to modify any policy that is pushed from DCNM. Make any modificationsusing DCNM.

• When you change any IP fabric for media-related server properties using DCNM Administration >DCNM Server > Server Properties, you must restart DCNM by running appmgr restart dcnm on astandalone DCNM or appmgr restart ha-apps on a native HA DCNM.

The following guidelines and limitations apply to the flow setup:

• DCNMnotifies the broadcast controller or user if an API call is unsuccessful, which requires the broadcastcontroller or user to retry.

• When the receiver leaf switch reloads, flows must be set up again by reinitiating the API call after theswitch reboots. This statement applies to DCNM 10.1 only.

• Static API is not supported with SVIs.

• VM snapshot is not supported. You cannot roll back to a previous DCNM snapshot.

The following guidelines and limitations apply to the flow policy:

• As a best practice, make any default policy changes before flows are active on the fabric.

• A flow policy cannot be modified when the flow is active. Modification is possible when the sender stopsthe flow and all receivers unsubscribe the flow.

• Account for 5% more than the flow bit rate to accommodate a certain amount of burst without the flowbeing policed. For example, provision a 3G flow as 3.15 Gbps.

• Ensure that any changes to the default flow policy are completed before any flow is active on the network.

The following guidelines and limitations apply to the host policy:


Configuring IP Fabric for MediaGuidelines and Limitations for Unicast PTP

• When a sender host policy changes from “allow” to “deny,” the flow is deleted immediately.

• When a receiver host policy is applied to a host connected via a Layer 2 port and an SVI, the policyapplies to all joins sent by all hosts on that VLAN and cannot be applied to a single receiver.

• If no ARP request or reply comes from the host when an allowed policy is installed, the host is not addedin DCNM, and IGMP packets are dropped. For allowed policies, you must add the host through ARPbefore sending IGMP joins.

• Ensure that any changes to the default host policy are completed before any active host appears on thenetwork. Define default host policy definitions ("deny all default" versus "allow all default") before thehosts are added to the network. Changes to host-specific policies are allowed at any time; however, thedefault policy edits are allowed only before hosts are introduced into the DCNM system.

The following guidelines and limitations apply to network and DCNM connections:

• Make sure that switches are discovered by DCNM before any hosts are detected or flows are set up onthe fabric.

• The DCNM HA pair must be on the same VLAN.

• The advantage of using MGMT as the interconnect is the ability to separate the management or controlplane and the data plane.

• The advantage of using INBAND is added redundancy.

• Latency between the switch and DCNM must be less than 1 ms to ensure that flow programming takesplace within an acceptable delay.

• Once the switch has been discovered, do not delete it from the DCNMdatabase. In order to decommissiona switch, make sure that all switch interfaces that are connected to endpoints are shut down and flowsage out. Once flows age out, delete the hosts that are discovered on the switch and then delete the switchfrom the DCNM LAN switch database.

Licensing RequirementsLicense RequirementProduct

The IP fabric for media solution requires a LANEnterprise Services license and a Network Serviceslicense. For a complete explanation of the CiscoNX-OS licensing scheme and how to obtain and applylicenses, see the Cisco NX-OS Licensing Guide.

Cisco NX-OS

The Cisco DCNMMedia Controller requires theAdvanced Server DCNM license. For moreinformation on this license, see the Cisco DCNMInstallation Guide.

Cisco DCNM


Configuring IP Fabric for MediaLicensing Requirements

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/nx-os/licensing/guide/b_Cisco_NX-OS_Licensing_Guide.html



Configuring NBMThe procedure for configuring non-blockingmulticast (NBM) varies depending onwhich deployment methodyou are using for your IP fabric for media solution.

• Spine-leaf topology (with or without the DCNMMedia Controller)

• Single modular switch (with or without the DCNMMedia Controller)

Configuring NBM for a Spine-Leaf Deployment with DCNMAfter you have set up the IP fabric, you must enable the non-blocking multicast (NBM) feature and establisha connection to the DCNM server. The NBM feature ensures that the bandwidth that is coming into the fabricis exactly the same as the bandwidth that is going out.

Follow this procedure to configure NBM for switches in a spine-leaf deployment with DCNM.

Before you begin

Enable the PIM feature (using the feature pim command).

Enable the OSPF feature (using the feature ospf command), if you are using the OSPF unicast routing protocol.

SUMMARY STEPS

1. configure terminal2. [no] feature nxapi3. [no] feature nbm4. nbm mode controller5. controller ip dcnm-server-ip-or-vip vrf management6. controller-credentials username username password [0 | 7] password

7. (Optional) switch-role border-leaf

DETAILED STEPS

PurposeCommand or Action

Enters global configuration mode.configure terminal

Example:

Step 1

switch# configure terminalswitch(config)#

Enables the NX-API feature. The no form of this commanddisables this feature.

[no] feature nxapi

Example:

Step 2

switch(config)# feature nxapi

Enables the NBM feature. The no form of this commanddisables this feature.

[no] feature nbm

Example:

Step 3

switch(config)# feature nbm


Configuring IP Fabric for MediaConfiguring NBM


Informs the switch of the presence of the DCNMMediaController.

nbm mode controller

Example:

Step 4

switch(config)# nbm mode controllerswitch(config-nbm-controller)#

Specifies the IP address of the DCNM server or the virtualIP address of the DCNM native HA server.

controller ip dcnm-server-ip-or-vip vrf management

Example:

Step 5

switch(config-nbm-controller)# controller ip10.1.1.1 vrf management

Configures the login information for the DCNM server.controller-credentials username username password [0| 7] password

Step 6

The 0 option indicates that the password is clear text, andthe 7 option indicates that the password is encrypted. Thedefault is 0 (clear text).

Example:switch(config-nbm-controller)#controller-credentials username admin password 77h56ab9

Configures a leaf switch as a border leaf in order to connectmultiple fabrics directly to each other.

(Optional) switch-role border-leaf

Example:

Step 7

This command is supported beginning with Cisco NX-OSRelease 7.0(3)I7(2). In previous releases, you can only

switch(config-nbm-controller)# switch-roleborder-leaf

exchange traffic that is directly connected to the fabric itself.Any remote traffic that comes in is not seen on the fabric.This command allows you to have two separate installations,both of them as IP fabric for media or one that is IP fabricfor media and another with an external Layer 3 networkthat is directly connected and has the traffic flowing throughit.

To support the exchange of media flows betweenan IP fabric for media and external systems,make sure to configure the ip pim sparse-modecommand on the WAN links and the ip pimpassive command only on the NBM fabricinterfaces (and not toward the external systems).

Note

Configuring NBM for a Spine-Leaf Topology without DCNMFollow this procedure to configure NBM for switches in a spine-leaf deployment without DCNM. In thismode, you can enable PIM active mode on spine and leaf switches. This feature provides multicast flow setupintelligence within the fabric. It supports multiple spines and variable flow size.

The spine-leaf topology without DCNM deployment model utilizes NBM in conjunction with ProtocolIndependentMulticast (PIM) andMulticast Source Discovery Protocol (MSDP) for provisioning flows withinthe fabric. The fabric must be configured with the PIM sparse mode and MSDP configurations described inConfiguring PIM on Spine and Leaf Switches, on page 24 and Configuring MSDP on Spine Switches, onpage 26.


Configuring IP Fabric for MediaConfiguring NBM for a Spine-Leaf Topology without DCNM

Before you begin



SUMMARY STEPS

1. configure terminal2. [no] feature nbm3. (Optional) [no] nbm reserve unicast fabric bandwidth value

4. (Optional) [no] nbm flow asm range [group-range-prefixes]5. [no] nbm flow bandwidth flow-bandwidth

6. [no] nbm flow-policy7. [no] policy policy-name

8. [no] bandwidth flow-bandwidth

9. [no] dscp value

10. [no] ip group-range ip-address to ip-address

DETAILED STEPS



Example:

Step 1


Enables the NBM feature and PIM active mode, whichallows the NBM fabric to form a multicast flow withoutassistance from an external controller.

[no] feature nbm

Example:switch(config)# feature nbm

Step 2

When you enter the feature nbm command, the followingcommands are also enabled automatically:

• nbm mode pim-active

• ip multicast multipath nbm

• ip pim ssm range none

• ip pim prune-on-expiry

• cdp enable

The no form of this command disables the followingcommands: feature nbm, nbm mode pim-active, ipmulticast multipath nbm, ip pim ssm range none, andip pim prune-on-expiry.

Reserves a percentage of bandwidth on fabric ports forunicast flows. NBM flow management does not use this

(Optional) [no] nbm reserve unicast fabric bandwidthvalue

Step 3

bandwidth for flow setup and reserves it on all fabricExample:



PurposeCommand or Actionswitch(config)# nbm reserve unicast fabricbandwidth 2

interfaces for the unicast traffic. The range is from 0 to100 percent, and the default value is 0.

Programs the NBM ASM group range for *,G joins. TheIGMP joins in this group range are expected to be V2 joins

(Optional) [no] nbm flow asm range[group-range-prefixes]

Step 4

or (*, G) joins. You can configure up to 20 group ranges.The default is no configured group range.Example:

switch(config)# nbm flow asm range 224.0.0.0/8225.0.0.0/8 226.0.0.0/8 227.0.0.0/8

Configures the global NBM flow bandwidth in Mbps. Ifany of the flows do not match the NBMmode flow group

[no] nbm flow bandwidth flow-bandwidth

Example:

Step 5

range, the default flow bandwidth is used for bandwidthswitch(config)# nbm flow bandwidth 3000 management and flow setup. The range is from 1 to 25,000

Mbps, and the default value is 3000 Mbps.

TheNBM flow bandwidth should be configuredwhen you are initially setting up the IP fabricand should not be changed at random. Also, anychange to the existing flow bandwidth valuetakes effect only after the device is rebooted.

Note

Configures the flow bandwidth per flow.[no] nbm flow-policy

Example:

Step 6

switch(config)# nbm flow-policyswitch(config-nbm-flow)#

Configures the NBM flow policy. You can specify amaximum of 63 alphanumeric characters for the policyname.

[no] policy policy-name

Example:switch(config-nbm-flow)# policy nbmflow10switch(config-nbm-flow-policy)#

Step 7

Configures the flow bandwidth in Mbps for multicastgroups matching this policy. The range is from 1 to 25,000Mbps.

[no] bandwidth flow-bandwidth

Example:switch(config-nbm-flow-policy)# bandwidth 10

Step 8

Configures the differentiated services code point (DSCP)value on the first-hop redundancy for flows matching inthe group range below.

[no] dscp value

Example:switch(config-nbm-flow-policy)# dscp 10

Step 9

Specifies the IP address range for multicast groupsassociated to this policy.

[no] ip group-range ip-address to ip-address

Example:

Step 10

switch(config-nbm-flow-policy)# ip group-range224.19.10.1 to 224.19.255.1switch(config-nbm-flow-policy)# ip group-range224.20.10.1 to 224.20.255.1



What to do next

Configure PIM and MSDP.

Configuring PIM on Spine and Leaf SwitchesFollow these steps to configure PIM for spine and leaf switches in a spine-leaf topology without the DCNMMedia Controller. The configuration should be the same on all nodes.

Before you begin

Configure NBM for a spine-leaf topology without DCNM.

SUMMARY STEPS

1. configure terminal2. ip pim rp-address rp-address group-list ip-prefix

3. ip pim ssm range none4. ip pim spt-threshold infinity group-list route-map-name

5. route-map policy-name permit sequence-number

6. match ip multicast group policy-name permit sequence-number

7. interface interface-type slot/port

8. mtu mtu-size

9. ip address ip-prefix

10. ip ospf passive-interface11. ip router ospf instance-tag area area-id

12. ip pim sparse-mode13. ip igmp version number

14. ip igmp immediate-leave15. ip pim pre-build-spt force16. Configure an RP interface.

DETAILED STEPS



Example:

Step 1


Configures a PIM static RP address for a multicast grouprange.

ip pim rp-address rp-address group-list ip-prefix

Example:

Step 2

switch(config)# ip pim rp-address 1.2.1.1group-list 224.0.0.0/4

Removes all group ranges for SSM.ip pim ssm range none

Example:

Step 3

switch(config)# ip pim ssm range none


Configuring IP Fabric for MediaConfiguring PIM on Spine and Leaf Switches


Creates the IPv4 PIM (*, G) state only, for the groupprefixes defined in the specified route map.

ip pim spt-threshold infinity group-list route-map-name

Example:

Step 4

switch(config)# ip pim spt-threshold infinitygroup-list mcast-all

Enters route-map configuration mode.route-map policy-name permit sequence-number

Example:

Step 5

switch(config)# route-map mcast-all permit 10switch(config-route-map)#

Matches the group specified.Make sure that the route-mapgroup address matches the NBM flow ASM range groupaddress.

match ip multicast group policy-name permitsequence-number

Example:

Step 6

switch(config-route-map)# match ip multicast group224.0.0.0/4

Specifies an interface to configure and enters interfaceconfiguration mode.

interface interface-type slot/port

Example:

Step 7

switch(config)# interface ethernet 2/1switch(config-if)#

Configures anMTU size to support jumbo traffic. It shouldbe configured on all host and fabric interfaces.

mtu mtu-size

Example:

Step 8

switch(config-if)# mtu 9216

Configures an IP address for this interface.ip address ip-prefix

Example:

Step 9

switch(config-if)# ip address 10.3.10.1/24

Suppresses routing updates on the interface. This commandoverrides the router or VRF commandmode configuration.

ip ospf passive-interface

Example:

Step 10

OSPF runs passive on host-facing interfaces only. Thisswitch(config-if)# ip ospf passive-interface configuration is needed only on endpoint interfaces and is

not needed on fabric interfaces.

Enables OSPF on the interface.ip router ospf instance-tag area area-id

Example:

Step 11

switch(config-if)# ip router ospf p1 area 0.0.0.0

Enables PIM sparse mode on the interface.ip pim sparse-mode

Example:

Step 12

switch(config-if)# ip pim sparse-mode

Enables IGMPv3 packet support on endpoint interfacesonly.

ip igmp version number

Example:

Step 13

switch(config-if)# ip igmp version 3


Configuring IP Fabric for MediaConfiguring PIM on Spine and Leaf Switches


Configures IGMP immediate leave on endpoint interfacesonly.

ip igmp immediate-leave

Example:

Step 14

switch(config-if)# ip igmp immediate-leave

Prebuilds the shortest path tree (SPT) for all known (S,G)routes in the routing table by triggering PIM joinsupstream.

ip pim pre-build-spt force

Example:switch(config)# ip pim pre-build-spt force

Step 15

Enter this command only on spine switches.Note

Make sure that the RP interface IP address is the same oneach spine switch.

Configure an RP interface.

Example:

Step 16

Enter this configuration only on spine switches.Noteswitch(config)# interface loopback0ip address 1.2.1.1/32ip router ospf p1 area 0.0.0.0ip pim sparse-mode

Configuring MSDP on Spine SwitchesFollow these steps to configure MSDP for spine switches in a spine-leaf topology without the DCNMMediaController.

MSDP is only needed in a multi-spine deployment that uses an ASM range. In a single-spine deployment,MSDP is not needed.

Note

Before you begin

Enable the MSDP feature (using the feature msdp command).

SUMMARY STEPS

1. configure terminal2. Configure a loopback interface to establish an MSDP session between the spine switches.3. ip msdp originator-id interface

4. ip msdp peer peer-ip-address connect-source interface

5. ip msdp sa-policy peer-ip-address policy-name out6. route-map policy-name permit sequence-number

7. match ip multicast group policy-name permit sequence-number

DETAILED STEPS



Example:

Step 1


Configuring IP Fabric for MediaConfiguring MSDP on Spine Switches

PurposeCommand or Actionswitch# configure terminalswitch(config)#

Establishes an MSDP session between the spine switches.Configure a loopback interface to establish an MSDPsession between the spine switches.

Step 2

Example:interface loopback1ip address 2.2.3.3/32ip router ospf p1 area 0.0.0.0ip pim sparse-mode

Configures the IP address used in the RP field of aSource-Active (SA) message entry.

ip msdp originator-id interface

Example:

Step 3

switch(config)# ip msdp originator-id loopback1

Configures an MSDP peer with the specified peer IPaddress.

ip msdp peer peer-ip-address connect-source interface

Example:

Step 4

switch(config)# ip msdp peer 2.2.1.1 connect-sourceloopback1

Enables a route-map policy for outgoing SA messages. Bydefault, all registered sources are sent in SA messages.

ip msdp sa-policy peer-ip-address policy-name out

Example:

Step 5

switch(config)# ip msdp sa-policy 2.2.1.1msdp-mcast-all out

Enters route-map configuration mode.route-map policy-name permit sequence-number

Example:

Step 6

switch(config)# route-map msdp-mcast-all permit 10switch(config-route-map)#

Matches the group specified. Make sure that the route-mapgroup address matches the NBM flow ASM range groupaddress.

match ip multicast group policy-name permitsequence-number

Example:

Step 7

switch(config-route-map)# match ip multicast group224.0.0.0/8

Configuring NBM for a Single Modular Switch with DCNMAfter you have set up the IP fabric, you must enable the non-blocking multicast (NBM) feature and establisha connection to the DCNM server. The NBM feature ensures that the bandwidth that is coming into the fabricis exactly the same as the bandwidth that is going out.

Follow this procedure to configure NBM for a single modular switch with the DCNMMedia Controller.

Before you begin




Configuring IP Fabric for MediaConfiguring NBM for a Single Modular Switch with DCNM

SUMMARY STEPS

1. configure terminal2. [no] feature nxapi3. [no] feature nbm4. nbm mode controller5. controller ip dcnm-server-ip-or-vip vrf management6. controller-credentials username username password [0 | 7] password

7. (Optional) show nbm controller

DETAILED STEPS



Example:

Step 1


Enables the NX-API feature. The no form of this commanddisables this feature.

[no] feature nxapi

Example:

Step 2

switch(config)# feature nxapi


[no] feature nbm

Example:

Step 3


Informs the switch of the presence of the DCNMMediaController.

nbm mode controller

Example:

Step 4

switch(config)# nbm mode controllerswitch(config-nbm-controller)#

Specifies the IP address of the DCNM server or the virtualIP address of the DCNM native HA server.

controller ip dcnm-server-ip-or-vip vrf management

Example:

Step 5

switch(config-nbm-controller)# controller ip10.1.1.1 vrf management

Configures the login information for the DCNM server.controller-credentials username username password [0| 7] password

Step 6

The 0 option indicates that the password is clear text, andthe 7 option indicates that the password is encrypted. Thedefault is 0 (clear text).

Example:switch(config-nbm-controller)#controller-credentials username admin password 77h56ab9

Displays the status of the DCNMMedia Controller.(Optional) show nbm controller

Example:

Step 7

switch(config-nbm-controller)# show nbm controllerVRF IP Role StatusOnline-Since--- --- ---- ------


Configuring IP Fabric for MediaConfiguring NBM for a Single Modular Switch with DCNM

PurposeCommand or Action------------management 10.10.10.1 ACTIVE ONLINE 2016-11-0417:08:33.080791

Configuring NBM for a Single Modular Switch without DCNMAfter you have set up the IP fabric, you must enable the NBM feature on the switch. The NBM feature ensuresthat the bandwidth that is coming into the fabric is exactly the same as the bandwidth that is going out.

Follow this procedure to configure NBM for a single modular switch without the DCNMMedia Controller.

Steps 3 through 8 in this procedure are not applicable to the Cisco Nexus 9508 switch with N9K-X9636C-Rand N9K-X9636Q-R line cards.

Note

Before you begin



SUMMARY STEPS

1. configure terminal2. [no] feature nbm3. [no] nbm flow bandwidth flow-bandwidth

4. [no] nbm flow-policy5. [no] policy policy-name

6. [no] bandwidth flow-bandwidth

7. [no] ip group ip-address

8. [no] ip group-range ip-address to ip-address

9. (Optional) show nbm flows bandwidth

DETAILED STEPS



Example:

Step 1



[no] feature nbm

Example:

Step 2



Configuring IP Fabric for MediaConfiguring NBM for a Single Modular Switch without DCNM


Configures the global NBM flow bandwidth in Mbps. Therange is from 1 to 25,000 Mbps, and the default value is3000 Mbps.

[no] nbm flow bandwidth flow-bandwidth

Example:switch(config)# nbm flow bandwidth 150

Step 3

The NBM flow bandwidth should be configuredwhen you are initially setting up the IP fabric. Itshould not be changed at random. Also, anychange to the existing flow bandwidth valuetakes effect only after the device is rebooted.

Note

Configures the flow bandwidth per flow.[no] nbm flow-policy

Example:

Step 4

switch(config)# nbm flow-policyswitch(config-nbm-flow)#

Configures the NBM flow policy. You can specify amaximum of 63 alphanumeric characters for the policyname.

[no] policy policy-name

Example:switch(config-nbm-flow)# policy 1.5gbpsswitch(config-nbm-flow-policy)#

Step 5

Configures the flow bandwidth inMbps for multicast groupsmatching this policy. The range is from 1 to 25,000 Mbps.

[no] bandwidth flow-bandwidth

Example:

Step 6

switch(config-nbm-flow-policy)# bandwidth 1500

Specifies the IP address for /32 multicast groups.[no] ip group ip-address

Example:

Step 7

switch(config-nbm-flow-policy)# ip group 228.0.0.15switch(config-nbm-flow-policy)# ip group228.0.255.15

Specifies the IP address range for multicast groupsassociated to this policy.

[no] ip group-range ip-address to ip-address

Example:

Step 8

switch(config-nbm-flow-policy)# ip group-range239.255.255.121 to 239.255.255.130switch(config-nbm-flow-policy)# ip group-range239.255.255.131 to 239.255.255.140switch(config-nbm-flow-policy)# ip group-range239.255.255.141 to 239.255.255.150switch(config-nbm-flow-policy)# ip group-range239.255.255.151 to 239.255.255.160

Displays the configured and applied NBM bandwidth perflow.

(Optional) show nbm flows bandwidth

Example:

Step 9

switch(config-nbm-flow-policy)# show nbm flowsbandwidth


Configuring IP Fabric for MediaConfiguring NBM for a Single Modular Switch without DCNM

Example

The following example shows a sample configuration:nbm flow-policypolicy Audiobandwidth 2ip group-range 225.3.5.2 to 225.3.5.255

policy Videobandwidth 3000ip group-range 228.255.255.1 to 228.255.255.255

Enabling Multicast and Unicast Flows (Optional)Beginning with Cisco NX-OS Release 7.0(3)I7(1), IP fabric for media can be used for multicast as well asunicast flows. You can assign multicast traffic to a priority queue (7) and unicast traffic to the default queue(0). This configuration ensures that unicast traffic does not congest multicast traffic.

For spine switches, traffic classification is based on access control list (ACL) and Differentiated ServicesCode Point (DSCP) values. For sender leaf switches, classification andmarking are based on flow programming(S,G) from the DCNMMedia Controller.

Note

Before you begin

For spine switches, configure TCAM carving using the following command, save the configuration, and reloadthe switch:

• hardware access-list tcam region ing-racl 256

• hardware access-list tcam region ing-l3-vlan-qos 256

For leaf switches, configure TCAM carving using the following commands, save the configuration, and reloadthe switch:

• hardware access-list tcam region ing-racl 256

• hardware access-list tcam region ing-l3-vlan-qos 256

• hardware access-list tcam region ing-nbm 1536

We recommend the TCAM sizes shown above, but you can adjust the values tomeet your network requirements.For more information on ACLTCAM regions, see the Cisco Nexus 9000 Series NX-OS Security ConfigurationGuide.

Note

SUMMARY STEPS

1. configure terminal2. ip access-list acl-name


Configuring IP Fabric for MediaEnabling Multicast and Unicast Flows (Optional)

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/security/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Security_Configuration_Guide_7x.html

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/security/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Security_Configuration_Guide_7x.html

3. sequence-number permit protocol source destination

4. exit5. ip access-list acl-name

6. sequence-number permit protocol source destination

7. exit8. class-map type qos match-all unicast-class-name

9. match access-group name acl-name

10. exit11. class-map type qos match-any multicast-class-name

12. match access-group name acl-name

13. exit14. policy-map type qos policy-map-name

15. class unicast-class-map-name

16. set qos-group 017. exit18. class multicast-class-map-name

19. set qos-group 720. exit21. exit22. interface ethernet slot/port

23. service-policy type qos input policy-map-name

24. (Optional) copy running-config startup-config

DETAILED STEPS



Example:

Step 1


Creates an IP ACL and enters IP ACL configurationmode.ip access-list acl-name

Example:

Step 2

switch(config)# ip access-list pmn-ucastswitch(config-acl)#

Creates a rule in the IP ACL to match all unicast IPaddresses (Class A, B, and C).

sequence-number permit protocol source destination

Example:

Step 3

switch(config-acl)# 10 permit ip any 0.0.0.0/1switch(config-acl)# 20 permit ip any 128.0.0.0/2switch(config-acl)# 30 permit ip any 192.0.0.0/3

Exits IP ACL configuration mode.exit

Example:

Step 4

switch(config-acl)# exitswitch(config)#




Creates an IP ACL and enters IP ACL configurationmode.ip access-list acl-name

Example:

Step 5

switch(config)# ip access-list pmn-mcastswitch(config-acl)#

Creates a rule to match all multicast flows.sequence-number permit protocol source destination

Example:

Step 6

switch(config-acl)# 2 permit ip any 224.0.0.0/4

Exits IP ACL configuration mode.exit

Example:

Step 7

switch(config-acl)# exitswitch(config)#

Creates a class map for unicast traffic and enters class-mapconfiguration mode.

class-map type qos match-all unicast-class-name

Example:

Step 8

switch(config)# class-map type qos match-allpmn-ucastswitch(config-cmap-qos)#

Configures the traffic class by matching packets based onthe ACL for unicast traffic.

match access-group name acl-name

Example:

Step 9

switch(config-cmap-qos)# match access-group namepmn-ucast

Exits class-map configuration mode.exit

Example:

Step 10

switch(config-cmap-qos)# exitswitch(config)#

Creates a class map for multicast traffic and entersclass-map configuration mode.

class-map type qos match-any multicast-class-name

Example:

Step 11

switch(config)# class-map type qos match-anypmn-mcastswitch(config-cmap-qos)#

Configures the traffic class by matching packets based onthe ACL for multicast traffic.

match access-group name acl-name

Example:

Step 12

switch(config-cmap-qos)# match access-group namepmn-mcast

Exits class-map configuration mode.exit

Example:

Step 13

switch(config-cmap-qos)# exitswitch(config)#




Creates a policy map and enters policy-map configurationmode.

policy-map type qos policy-map-name

Example:

Step 14

switch(config)# policy-map type qos pmn-qosswitch(config-pmap-qos)#

Creates a class for unicast traffic and enters policy-mapclass configuration mode.

class unicast-class-map-name

Example:

Step 15

switch(config-pmap-qos)# class pmn-ucastswitch(config-pmap-c-qos)#

Configures the QoS group value to match on forclassification of traffic into the PMN unicast class map.

set qos-group 0

Example:

Step 16

switch(config-pmap-c-qos)# set qos-group 0

Exits policy-map class configuration mode.exit

Example:

Step 17

switch(config-pmap-c-qos)# exitswitch(config-pmap-qos)#

Creates a class for multicast traffic and enters policy-mapclass configuration mode.

class multicast-class-map-name

Example:

Step 18

switch(config-pmap-qos)# class pmn-mcastswitch(config-pmap-c-qos)#

Configures the QoS group value to match on forclassification of traffic into the PMN multicast class map.

set qos-group 7

Example:

Step 19

switch(config-pmap-c-qos)# set qos-group 7

Exits policy-map class configuration mode.exit

Example:

Step 20

switch(config-pmap-c-qos)# exitswitch(config-pmap-qos)#

Exits policy-map configuration mode.exit

Example:

Step 21

switch(config-pmap-qos)# exitswitch(config)#

Creates an interface and enters interface configurationmode. This command should be used only for fabricinterfaces.

interface ethernet slot/port

Example:switch(config)# interface ethernet 1/49switch(config-if)#

Step 22

Adds the policy-map name to the input packets of theinterface.

service-policy type qos input policy-map-name

Example:

Step 23

switch(config-if)# service-policy type qos inputpmn-qos




Copies the running configuration to the startupconfiguration.

(Optional) copy running-config startup-config

Example:

Step 24

switch(config-if)# copy running-configstartup-config

Example

Configuration example:ip access-list pmn-ucast10 permit ip any 0.0.0.0 31.255.255.25520 permit ip any 128.0.0.0 31.255.255.25530 permit ip any 192.0.0.0 31.255.255.255

ip access-list pmn-mcast10 permit ip any 224.0.0.0/4

class-map type qos match-all pmn-ucastmatch access-group name pmn-ucast

class-map type qos match-any pmn-mcastmatch access-group name pmn-ucast

policy-map type qos pmn-qosclass pmn-ucastset qos-group 0

class pmn-mcastset qos-group 7

interface ethernet 1/49service-policy type qos input pmn-qos

Verifying the NBM ConfigurationTo display the NBM configuration information, perform one of the following tasks.

Displays the NBM flows.show nbm flows [active [interface type slot/port] | all [interface typeslot/port] | detail [interface type slot/port] | group multicast-group |group-based [interface type slot/port] | inactive [interface typeslot/port] | interface type slot/port | m-group multicast-group |no-receiver [interface type slot/port] |source ip-address]

Displays the configured and appliedNBM bandwidth per flow.

This command is notsupported for CiscoNexus 9508 switcheswith N9K-X9636C-Rand N9K-X9636Q-Rline cards.

Note

show nbm flows bandwidth


Configuring IP Fabric for MediaVerifying the NBM Configuration

Displays the NBM flow statistics.

This command is notsupported for spineswitches in a spine-leaftopology and for singlemodular switches withN9K-X9636C-R andN9K-X9636Q-R linecards.

Note

show nbm flows statistics

Displays the running configurationinformation for NBM.

show running-config nbm

Sample Output for Show CommandsThis section provides output examples for single modular switches without the DCNMMedia Controller. Incontroller-based deployments, statistics are available in the DCNMMedia Controller GUI.

Sample Output for Switches Running Cisco NX-OS Release 7.0(3)F2(1) or LaterThis example shows sample output for the show nbm flows command:switch# show nbm flowsNBM Active Source-Group-Based Flows :Start-Time Src-Intf Mcast-Group Src-IP LID Status Num Rx Bw Mbps CFGBw Mbps Src-slot Unit Slice04/27 05:32:01.536 Eth3/13/1 230.13.2.244 210.1.1.2 1070 ACTIVE 1 3000.0003000.000 3 1 004/27 05:32:01.535 Eth3/13/1 230.13.2.243 210.1.1.2 582 ACTIVE 1 3000.0003000.000 3 1 004/27 05:32:01.535 Eth3/13/1 230.13.2.242 210.1.1.2 1298 ACTIVE 1 3000.0003000.000 3 1 004/27 05:32:01.534 Eth3/13/1 230.13.2.241 210.1.1.2 1407 ACTIVE 1 3000.0003000.000 3 1 0

This example shows sample output for the show nbm flows group multicast-group command:switch# show nbm flows group 230.13.2.244NBM Active Source-Group-Based Flows :Start-Time Src-Intf Mcast-Group Src-IP LID Status Num Rx Bw Mbps CFGBw Mbps Src-slot Unit Slice04/27 05:32:01.536 Eth3/13/1 230.13.2.244 210.1.1.2 1070 ACTIVE 1 3000.000 3000.000

3 1 0

This example shows sample output for the show ip igmp groups command:switch# show ip igmp groupsIGMP Connected Group Membership for VRF "default" - 500 total entriesType: S - Static, D - Dynamic, L - Local, T - SSM TranslatedGroup Address Type Interface Uptime Expires Last Reporter230.13.2.241 D Ethernet4/25/1 00:08:16 00:02:54 210.13.1.2230.13.2.242 D Ethernet4/25/1 00:08:16 00:02:58 210.13.1.2230.13.2.243 D Ethernet4/25/1 00:08:16 00:02:56 210.13.1.2230.13.2.244 D Ethernet4/25/1 00:08:16 00:02:54 210.13.1.2


Configuring IP Fabric for MediaSample Output for Show Commands

This example shows sample output for the show ip igmp groups interface command:switch# show ip igmp groups eth4/25/1IGMP Connected Group Membership for Interface "Eth4/25/1" - 500 total entriesType: S - Static, D - Dynamic, L - Local, T - SSM TranslatedGroup Address Type Interface Uptime Expires Last Reporter230.13.2.241 D Ethernet4/25/1 00:08:16 00:02:54 210.13.1.2230.13.2.242 D Ethernet4/25/1 00:08:16 00:02:58 210.13.1.2230.13.2.243 D Ethernet4/25/1 00:08:16 00:02:56 210.13.1.2230.13.2.244 D Ethernet4/25/1 00:08:16 00:02:54 210.13.1.2

This example shows sample output for the show ip igmp groups multicast-group command:switch# show ip igmp groups 230.13.2.244IGMP Connected Group Membership for VRF "default" - matching Group "230.13.2.244"Type: S - Static, D - Dynamic, L - Local, T - SSM TranslatedGroup Address Type Interface Uptime Expires Last Reporter230.13.2.244 D Ethernet4/25/1 00:09:09 00:03:55 210.13.1.2

This example shows sample output for the show running-config nbm command:switch# show running-config nbm!Command: show running-config nbm!Time: Thu Apr 27 05:39:23 2017

version 7.0(3)F2(1)feature nbm

Sample Output for Switches Running Cisco NX-OS Release 7.0(3)I6(1) or LaterThis example shows sample output for the show nbm controller command:switch# show nbm controllerVRF IP Status Online-Since--- --- ------ ------------management 172.31.203.198 ONLINE 2017-08-23 16:19:22.488835

This example shows sample output for the show nbm flows command:switch# show nbm flowsNBM Active Source-Group-Based Flows :Mcast-Group Src-IP Start-Time Src-Intf L4-S L4-D LID Status Num Rx Bw Mbps CFG Bw MbpsSrc-slot Unit Slice DSCP QOS228.2.10.3 10.12.85.10 08/21 18:45:27.429 Vlan1000 0 0 0 ACTIVE 7 66.000 66.000 1 0 0 48 7

228.1.3.3 10.10.85.10 08/21 18:45:27.324 Vlan1000 0 0 0 ACTIVE 8 18.000 18.000 1 0 0 24 7228.1.4.1 10.10.85.10 08/21 18:45:27.068 Vlan1000 0 0 0 ACTIVE 8 19.000 19.000 1 0 0 32 7228.1.9.1 10.10.85.10 08/21 18:45:26.732 Vlan1000 0 0 0 ACTIVE 8 31.000 31.000 1 0 0 32 7

This example shows sample output for the show nbm flows group multicast-group command:switch# show nbm flows group 228.2.10.3NBM Active Source-Group-Based Flows :Mcast-Group Src-IP Start-Time Src-Intf L4-S L4-D LID Status Num Rx Bw Mbps CFG Bw MbpsSrc-slot Unit Slice DSCP QOS228.2.10.3 10.12.85.10 08/21 18:45:27.429 Vlan1000 0 0 0 ACTIVE 7 66.000 66.000 1 0 0 48 7

This example shows sample output for the show ip igmp groups command:


Configuring IP Fabric for MediaSample Output for Switches Running Cisco NX-OS Release 7.0(3)I6(1) or Later

switch# show ip igmp groupsIGMP Connected Group Membership for VRF "default" - 61520 total entriesType: S - Static, D - Dynamic, L - Local, T - SSM TranslatedGroup Address Type Interface Uptime Expires Last Reporter225.3.5.1 D Ethernet3/5 11:48:07 00:03:36 3.5.1.6225.3.5.2 D Ethernet3/5 11:48:07 00:03:36 3.5.1.6225.3.5.3 D Ethernet3/5 11:48:07 00:03:36 3.5.1.6225.3.5.4 D Ethernet3/5 11:48:07 00:03:36 3.5.1.6

This example shows sample output for the show ip igmp groups interface command:switch# show ip igmp groups eth3/5IGMP Connected Group Membership for Interface "Eth3/5" - 1165 total entriesType: S - Static, D - Dynamic, L - Local, T - SSM TranslatedGroup Address Type Interface Uptime Expires Last Reporter225.3.5.1 D Ethernet3/5 11:51:22 00:02:24 3.5.1.6225.3.5.2 D Ethernet3/5 11:51:22 00:02:24 3.5.1.6225.3.5.3 D Ethernet3/5 11:51:22 00:02:24 3.5.1.6225.3.5.4 D Ethernet3/5 11:51:22 00:02:24 3.5.1.6

This example shows sample output for the show ip igmp groups multicast-group command:switch# show ip igmp groups 225.3.5.1IGMP Connected Group Membership for VRF "default" - matching Group "225.3.5.1"Type: S - Static, D - Dynamic, L - Local, T - SSM TranslatedGroup Address Type Interface Uptime Expires Last Reporter225.3.5.1 D Ethernet3/5 00:05:20 00:10:10 3.5.1.6

This example shows sample output for the show running-config nbm command:switch# show running-config nbm!Command: show running-config nbm!Time: Sat May 6 23:10:33 2017

version 7.0(3)I6(1)feature nbm

nbm flow bandwidth 55nbm flow-policypolicy 0mbpsbandwidth 2ip group 225.3.5.1ip group-range 225.3.5.2 to 225.3.5.255

policy 3000bandwidth 130ip group-range 228.255.255.1 to 228.255.255.255

Sample XML Output for Switches Running Cisco NX-OS Release 7.0(3)I7(1) or LaterThis example shows sample XML output for the show nbm controller | xml command:switch# show nbm controller | xml<?xml version="1.0" encoding="ISO-8859-1"?><nf:rpc-reply xmlns="http://www.cisco.com/nxos:1.0:pmn" xmlns:nf="urn:ietf:params:xml:ns:netconf:base:1.0"><nf:data><show><nbm><controller><__XML__OPT_Cmd_show_nbm_controller___readonly__><__readonly__>


Configuring IP Fabric for MediaSample XML Output for Switches Running Cisco NX-OS Release 7.0(3)I7(1) or Later

<vrf>management</vrf><ip>172.31.203.198</ip><status>ONLINE</status><online_since>2017-08-23 16:19:22.488835</online_since></__readonly__></__XML__OPT_Cmd_show_nbm_controller___readonly__></controller></nbm></show>

</nf:data></nf:rpc-reply>]]>]]>

This example shows sample XML output for the show nbm flow | xml command:switch# show nbm flow | xml<?xml version="1.0" encoding="ISO-8859-1"?><nf:rpc-reply xmlns="http://www.cisco.com/nxos:1.0:pmn"xmlns:nf="urn:ietf:params:xml:ns:netconf:base:1.0"><nf:data><show><nbm><flows><__XML__OPT_Cmd_show_nbm_flow_info_all><__XML__OPT_Cmd_show_nbm_flow_info_interface><__XML__OPT_Cmd_show_nbm_flow_info___readonly__><__readonly__><TABLE_flows><ROW_flows><mcast_grp_src_ip>232.10.255.50 9.11.0.10 </mcast_grp_src_ip><start_time>08/23 16:48:54.275</start_time><src_intf>Vlan1000</src_intf><l4_sport>0</l4_sport><l4_dport>0</l4_dport><lid>0</lid><status>ACTIVE</status><num_rx>1</num_rx><bw_mbps>333.234</bw_mbps><cfg_mbps>333.234</cfg_mbps><src_slot>1</src_slot><unit>0</unit><slice>0</slice><dscp>8</dscp><qos>7</qos>

This example shows sample XML output for the show nbm flow m-group multicast-group | xml command:switch# show nbm flow m-group 232.10.255.1 | xml<nf:rpc-reply xmlns="http://www.cisco.com/nxos:1.0:pmn"xmlns:nf="urn:ietf:params:xml:ns:netconf:base:1.0"><nf:data><show><nbm><flows><__XML__OPT_Cmd_show_nbm_flow_info_all><m-group><group-ip-id>232.10.255.1</group-ip-id></m-group><__XML__OPT_Cmd_show_nbm_flow_info_interface><__XML__OPT_Cmd_show_nbm_flow_info___readonly__><__readonly__><TABLE_flows><ROW_flows>



<mcast_grp_src_ip>232.10.255.1 9.11.0.10 </mcast_grp_src_ip><start_time>08/23 16:48:53.602</start_time><src_intf>Vlan1000</src_intf><l4_sport>0</l4_sport><l4_dport>0</l4_dport><lid>0</lid><status>ACTIVE</status><num_rx>1</num_rx><bw_mbps>333.234</bw_mbps><cfg_mbps>333.234</cfg_mbps><src_slot>1</src_slot><unit>0</unit><slice>0</slice><dscp>8</dscp><qos>7</qos></ROW_flows>

This example shows sample XML output for the show nbm flow group multicast-group source ip-address| xml command:switch# show nbm flow group 232.10.255.1 source 9.11.0.10 | xml<?xml version="1.0" encoding="ISO-8859-1"?><nf:rpc-reply xmlns="http://www.cisco.com/nxos:1.0:pmn"xmlns:nf="urn:ietf:params:xml:ns:netconf:base:1.0"><nf:data><show><nbm><flows><__XML__OPT_Cmd_show_nbm_flow_info_all><__XML__OPT_Cmd_show_nbm_flow_info_source><group><group-ip><__XML__PARAM_value>232.10.255.1</__XML__PARAM_value><__XML__OPT_Cmd_show_nbm_flow_info_source><source><source-ip>9.11.0.10</source-ip></source></__XML__OPT_Cmd_show_nbm_flow_info_source></group-ip></group></__XML__OPT_Cmd_show_nbm_flow_info_source><__XML__OPT_Cmd_show_nbm_flow_info_interface><__XML__OPT_Cmd_show_nbm_flow_info___readonly__><__readonly__><TABLE_flows><ROW_flows><mcast_grp_src_ip>232.10.255.1 9.11.0.10 </mcast_grp_src_ip><start_time>08/23 16:48:53.602</start_time><src_intf>Vlan1000</src_intf><l4_sport>0</l4_sport><l4_dport>0</l4_dport><lid>0</lid><status>ACTIVE</status><num_rx>1</num_rx><bw_mbps>333.234</bw_mbps><cfg_mbps>333.234</cfg_mbps><src_slot>1</src_slot><unit>0</unit><slice>0</slice><dscp>8</dscp><qos>7</qos></ROW_flows></TABLE_flows>



</__readonly__></__XML__OPT_Cmd_show_nbm_flow_info___readonly__></__XML__OPT_Cmd_show_nbm_flow_info_interface></__XML__OPT_Cmd_show_nbm_flow_info_all></flows></nbm></show>


This example shows sample XML output for the show nbm flow statistics m-group multicast-group | xmlcommand:switch# show nbm flow statistics m-group 232.10.255.10 | xml<?xml version="1.0" encoding="ISO-8859-1"?><nf:rpc-reply xmlns="http://www.cisco.com/nxos:1.0:pmn"xmlns:nf="urn:ietf:params:xml:ns:netconf:base:1.0"><nf:data><show><nbm><flows><statistics><__XML__OPT_Cmd_show_nbm_flow_stats_group-based><m-group><group-ip-id>232.10.255.10</group-ip-id></m-group><__XML__OPT_Cmd_show_nbm_flow_stats_interface><__XML__OPT_Cmd_show_nbm_flow_stats___readonly__><__readonly__><TABLE_stats><ROW_stats><mcast_grp_src_ip>232.10.255.10 9.10.96.10 </mcast_grp_src_ip><start_time>08/23 16:28:47.016</start_time><src_intf>Vlan1096</src_intf><packets>54462</packets><bytes>27231000</bytes><allow_bytes>27219500</allow_bytes><drop_bytes>0</drop_bytes></ROW_stats><ROW_stats><mcast_grp_src_ip>232.10.255.10 9.10.97.10 </mcast_grp_src_ip><start_time>08/23 16:28:49.358</start_time><src_intf>Vlan1097</src_intf><packets>53843</packets><bytes>26921500</bytes><allow_bytes>26910000</allow_bytes><drop_bytes>0</drop_bytes></ROW_stats><ROW_stats><mcast_grp_src_ip>232.10.255.10 9.10.98.10 </mcast_grp_src_ip><start_time>08/23 16:28:55.976</start_time><src_intf>Vlan1098</src_intf><packets>53509</packets><bytes>26754500</bytes><allow_bytes>26743000</allow_bytes><drop_bytes>0</drop_bytes></ROW_stats><ROW_stats><mcast_grp_src_ip>232.10.255.10 9.10.99.10 </mcast_grp_src_ip><start_time>08/23 16:28:56.176</start_time><src_intf>Vlan1099</src_intf><packets>51821</packets>



<bytes>25910500</bytes><allow_bytes>25899000</allow_bytes><drop_bytes>0</drop_bytes></ROW_stats><ROW_stats><mcast_grp_src_ip>232.10.255.10 9.11.0.10 </mcast_grp_src_ip><start_time>08/23 16:28:53.548</start_time><src_intf>Vlan1100</src_intf><packets>51141</packets><bytes>25570500</bytes><allow_bytes>25558500</allow_bytes><drop_bytes>0</drop_bytes></ROW_stats></TABLE_stats></__readonly__></__XML__OPT_Cmd_show_nbm_flow_stats___readonly__></__XML__OPT_Cmd_show_nbm_flow_stats_interface></__XML__OPT_Cmd_show_nbm_flow_stats_group-based></statistics></flows></nbm></show>


Configuring Fabric and Host InterfacesYou can configure the fabric and host interfaces using the CLI commands in this section or use the DCNMMedia Controller to autoprovision these configurations.

We recommend using a Layer 3 routed port to an endpoint.Note

Configuring a Fabric InterfaceYou must configure the fabric interface on each leaf switch. This interface goes from the leaf switch to thespine switch.

If you want to be able to exchange media flows between an IP fabric for media and external systems, whichis supported beginning with Cisco NX-OSRelease 7.0(3)I7(2), make sure to configure the ip pim sparse-modecommand on the WAN links and the ip pim passive command only on the NBM fabric interfaces (and nottoward the external systems).

Note

SUMMARY STEPS

1. configure terminal2. interface ethernet slot/port

3. ip address ip-prefix/length


Configuring IP Fabric for MediaConfiguring Fabric and Host Interfaces

4. ip router ospf instance-tag area area-id

5. ip pim sparse-mode6. [no] ip pim passive7. no shutdown

DETAILED STEPS



Example:

Step 1


Specifies the fabric interface and enters interfaceconfiguration mode.


Example:

Step 2


Assigns an IP address and subnet mask to this interface.ip address ip-prefix/length

Example:

Step 3


Adds the interface to the OSPFv2 instance and area.ip router ospf instance-tag area area-id

Example:

Step 4

switch(config-if)# ip router ospf 100 area 0.0.0.0

Enables PIM sparse mode on this interface.ip pim sparse-mode

Example:

Step 5


Prevents the switch from sending PIM messages on thisinterface and from accepting PIM messages from other

[no] ip pim passive

Example:

Step 6

switches across this interface. This command is required asswitch(config-if)# ip pim passive the DCNMMedia Controller (rather than the PIM protocol)

statically provisions the flow end to end.

If you want to exchange media flows betweenan IP fabric for media and external systems,configure the no ip pim passive command onthe interfaces toward the external systems.

Note

Enables the interface.no shutdown

Example:

Step 7

switch(config-if)# no shutdown


Configuring IP Fabric for MediaConfiguring a Fabric Interface

Configuring a Layer 3 Host InterfaceYou must configure the Layer 3 routed host interface on each leaf switch. This interface goes from the leafswitch to an endpoint.

SUMMARY STEPS


3. ip igmp version 34. ip address ip-prefix/length

5. ip router ospf instance-tag area area-id

6. ip pim sparse-mode7. ip pim passive8. ip igmp immediate-leave9. no shutdown

DETAILED STEPS



Example:

Step 1


Specifies the host interface and enters interfaceconfiguration mode.


Example:

Step 2


Sets the IGMP version to 3.ip igmp version 3

Example:

Step 3


Assigns an IP address and subnet mask to this interface.ip address ip-prefix/length

Example:

Step 4



Example:

Step 5

switch(config-if)# ip router ospf 100 area 0.0.0.0

Enables PIM sparse mode on this interface.ip pim sparse-mode

Example:

Step 6



Configuring IP Fabric for MediaConfiguring a Layer 3 Host Interface


Prevents the switch from sending PIM messages on thisinterface and from accepting PIM messages from other

ip pim passive

Example:

Step 7

switches across this interface. This command is required asswitch(config-if)# ip pim passive the DCNMMedia Controller (rather than the PIM protocol)

statically provisions the flow end to end.

Enables the switch to remove the group entry from themulticast routing table immediately upon receiving a leavemessage for the group.

ip igmp immediate-leave

Example:switch(config-if)# ip igmp immediate-leave

Step 8

Enables the interface.no shutdown

Example:

Step 9

switch(config-if)# no shutdown

Configuring a Layer 2 with SVI Host InterfaceYou must configure the Layer 2 with SVI host interface on each leaf switch. This interface goes from the leafswitch to an endpoint.

SUMMARY STEPS

1. configure terminal2. feature interface-vlan3. vlan vlan-id

4. exit5. vlan configuration vlan-id

6. ip igmp snooping7. ip igmp snooping fast-leave8. exit9. interface vlan vlan-id

10. (Optional) ip igmp version 311. ip router ospf instance-tag area area-id

12. ip address ip-address

13. ip pim sparse-mode14. ip pim passive15. ip igmp suppress v3-gsq16. no shutdown17. exit18. interface ethernet port/slot

19. switchport20. switchport mode {access | trunk}21. switchport {access | trunk allowed} vlan vlan-id

22. no shutdown23. exit


Configuring IP Fabric for MediaConfiguring a Layer 2 with SVI Host Interface

DETAILED STEPS



Example:

Step 1


Enables the creation of VLAN interfaces.feature interface-vlan

Example:

Step 2

switch(config)# feature interface-vlan

Creates a VLAN. The range is from 2 to 3967. VLAN 1is the default VLAN and cannot be created or deleted. For

vlan vlan-id

Example:

Step 3

more information on VLANs, see the Cisco Nexus 9000Series NX-OS Layer 2 Switching Configuration Guide.switch(config)# vlan 5

switch(config-vlan)#

Exits the VLAN mode.exit

Example:

Step 4

switch(config-vlan)# exitswitch(config)#

Allows you to configure VLANswithout actually creatingthem.

vlan configuration vlan-id

Example:

Step 5

switch(config)# vlan configuration 5switch(config-vlan-config)#

Enables IGMP snooping on the device for the specificVLAN. For more information on IGMP snooping, see the

ip igmp snooping

Example:

Step 6

Cisco Nexus 9000 Series NX-OS Multicast RoutingConfiguration Guide.switch(config-vlan-config)# ip igmp snooping

Supports IGMPv2 hosts that cannot be explicitly trackedbecause of the host report suppression mechanism of the

ip igmp snooping fast-leave

Example:

Step 7

IGMPv2 protocol. When you enable fast leave, the IGMPswitch(config-vlan-config)# ip igmp snoopingfast-leave

software assumes that not more than one host is presenton eachVLAN port. The default is disabled for all VLANs.

Exits VLAN configuration mode.exit

Example:

Step 8

switch(config-vlan-config)# exitswitch(config)#

Creates a VLAN interface and enters interfaceconfiguration mode. The range is from 2 and 3967.

interface vlan vlan-id

Example:

Step 9

switch(config)# interface vlan 5switch(config-if)#








Sets the IGMP version to 3. Enter this command if youare using IGMP version 3.

(Optional) ip igmp version 3

Example:

Step 10



Example:

Step 11

switch(config-if)# ip router ospf 201 area0.0.0.15

Configures an IP address for this interface.ip address ip-address

Example:

Step 12


Enables PIM sparse mode on this interface. For moreinformation on PIM, see the Cisco Nexus 9000 SeriesNX-OS Multicast Routing Configuration Guide.

ip pim sparse-mode

Example:switch(config-if)# ip pim sparse-mode

Step 13

Prevents the device from sending PIM messages on theinterface or accepting PIM messages from other devices

ip pim passive

Example:

Step 14

across this interface. The device instead considers that itswitch(config-if)# ip pim passive is the only PIM device on the network and acts as the

designated router and designated forwarder for all BidirPIM group ranges.

Prevents the router from generating a query when itreceives an IGMPv3 leave report.

ip igmp suppress v3-gsq

Example:

Step 15

switch(config-if)# ip igmp suppress v3-gsq

Clears the errors on the interfaces and VLANs wherepolicies correspondwith hardware policies. This command

no shutdown

Example:

Step 16

allows policy programming to continue and the port tocome up.switch(config-if)# no shutdown

Apply this command only after you haveentered the previous multicast commands.

Note

Exits the VLAN interface configuration mode.exit

Example:

Step 17

switch(config-if)# exitswitch(config)#

Configures an Ethernet interface.interface ethernet port/slot

Example:

Step 18

switch(config-if)# interface ethernet 2/1

Sets the interface as a Layer 2 interface.switchport

Example:

Step 19





PurposeCommand or Actionswitch(config-if)# switchport

Configures one of the following options:switchport mode {access | trunk}Step 20

Example: access—Sets the interface as a nontrunking, nontagged,single-VLAN Layer 2 interface. An access port can carryswitch(config-if)# switchport mode trunktraffic in one VLAN only. By default, an access port carriestraffic for VLAN 1.

trunk—Sets the interface as a Layer 2 trunk port. A trunkport can carry traffic in one or more VLANs on the samephysical link. (VLANs are based on the trunk-allowedVLANs list.) By default, a trunk interface can carry trafficfor all VLANs.

Configures one of the following options:switchport {access | trunk allowed} vlan vlan-idStep 21

Example: access—Specifies the VLAN for which this access portwill carry traffic. If you do not enter this command, theaccess port carries traffic on VLAN 1 only.

switch(config-if)# switchport trunk allowed vlan5

trunk allowed—Specifies the allowed VLANs for thetrunk interface. The default is to allow all VLANs on thetrunk interface: 1 to 3967 and 4048 to 4094. VLANs 3968to 4047 are the default VLANs reserved for internal useby default.

Clears the errors on the interfaces and VLANs wherepolicies correspondwith hardware policies. This command

no shutdown

Example:

Step 22

allows policy programming to continue and the port tocome up.switch(config-if)# no shutdown

Exits the interface configuration mode.exit

Example:

Step 23

switch(config-if)# exitswitch(config)#

Configuring PTP for Media (Optional)Cisco's IP fabric for media solution supports the following IEEE 1588 PTP profiles:

• Audio Engineering Society 67 profile (AES67) - For high-performance streaming audio over IP

• Professional Broadcast Environment profile (SMPTE-2059-2) - For high-performance streaming videoover IP

The solution also introduces mixed mode PTP support with multicast sync and announce messages as wellas unicast delay request and response messages.

To configure PTP for media, you should use one of these profiles.


Configuring IP Fabric for MediaConfiguring PTP for Media (Optional)

The PTP configuration for media is different from the PTP configuration for a non-media network. However,you can refer to the Cisco Nexus 9000 Series NX-OS System Management Configuration Guide for moreinformation on PTP.

Note

Before you begin

Enable PTP boundary mode functionality on the switch. PTP packets cannot be routed as regular multicastpackets within the fabric.

SUMMARY STEPS

1. configure terminal2. [no] feature ptp3. [no] ptp source ip-address [vrf vrf]4. (Optional) [no] ptp offload5. interface ethernet slot/port

6. [no] ptp7. (Optional) [no] ptp announce interval [aes67 | smpte-2059] log-seconds

8. (Optional) [no] ptp announce timeout [aes67 | smpte-2059] count

9. (Optional) [no] ptp delay-request minimum interval [aes67 | smpte-2059] log-seconds

10. (Optional) [no] ptp sync interval [aes67 | smpte-2059] log-seconds

11. (Optional) [no] ptp vlan vlan-id

12. (Optional) show ptp brief13. (Optional) show ptp port interface interface slot/port


DETAILED STEPS



Example:

Step 1


Enables or disables PTP on the device.[no] feature ptpStep 2

Example: Enabling PTP on the switch does not enablePTP on each interface.

Note

switch(config)# feature ptp

Configures the source IPv4 address for all PTP packets.We recommend that the source IP address be a valid IPaddress for any interface on the switch.

[no] ptp source ip-address [vrf vrf]

Example:switch(config)# ptp source 10.10.10.1

Step 3

Increases the number of PTP sessions by offloading sometimers to the line card.

(Optional) [no] ptp offload

Example:

Step 4



http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/system_management/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_System_Management_Configuration_Guide_7x.html

PurposeCommand or Actionswitch(config)# ptp offload This command is supported only for Cisco

Nexus 9500 Series switches with X9700-EXline cards, beginning with Cisco NX-OSRelease 7.0(3)I6(1).

Note

Specifies the interface on which you are enabling PTP andenters the interface configuration mode.


Example:

Step 5


Enables or disables PTP on an interface.[no] ptp

Example:

Step 6

switch(config-if)# ptp

Configures the interval between PTP announce messageson an interface.

(Optional) [no] ptp announce interval [aes67 |smpte-2059] log-seconds

Step 7

Example: Table 4: PTP Announcement Interval Range and Default Values

Default ValueRangeOptionswitch(config-if)# ptp announce interval aes67 3

1 log second0 to 4 log secondsaes67

1 log second–3 to 1 logseconds

smpte-2059

1 log second0 to 4 log secondsWithout the aes67or smpte-2059option

Configures the number of PTP intervals before a timeoutoccurs on an interface.

(Optional) [no] ptp announce timeout [aes67 |smpte-2059] count

Step 8

Example: Table 5: PTP Announcement Timeout Range and Default Values

Default ValueRangeOptionswitch(config-if)# ptp announce timeout aes67 2

3 intervals2 to 10 intervalsaes67

3 intervals2 to 10 intervalssmpte-2059

3 intervals2 to 4 intervalsWithout the aes67or smpte-2059option

Configures the minimum interval allowed between PTPdelay messages when the port is in the master state.

(Optional) [no] ptp delay-request minimum interval[aes67 | smpte-2059] log-seconds

Step 9

Example:



PurposeCommand or ActionTable 6: PTP Delay-Request Minimum Interval Range and Default Values

Default ValueRangeOption

switch(config-if)# ptp delay-request minimuminterval aes67 -1

0 log seconds–4 to 5 logseconds

aes67

0 log seconds–4 to 5 logseconds

smpte-2059

0 log seconds–1 to 6 logseconds (where –1= 1 frame persecond)

Without the aes67or smpte-2059option

Configures the interval between PTP synchronizationmessages on an interface.

(Optional) [no] ptp sync interval [aes67 | smpte-2059]log-seconds

Step 10

Example: Table 7: PTP Synchronization Interval Range and Default Values

Default ValueRangeOptionswitch(config-if)# ptp sync interval aes67 1

–2 log seconds–4 to 1 logseconds

aes67

–2 log seconds–4 to –1 logseconds

smpte-2059

–2 log seconds–3 to 1 logseconds

Without the aes67or smpte-2059option

Specifies the VLAN for the interface where PTP is beingenabled. You can enable PTP only on one VLAN on aninterface.

(Optional) [no] ptp vlan vlan-id

Example:switch(config-if)# ptp vlan 1

Step 11

The range is from 1 to 4094.

Displays the PTP status.(Optional) show ptp brief

Example:

Step 12

switch(config-if)# show ptp brief

Displays the status of the PTP port.(Optional) show ptp port interface interface slot/port

Example:

Step 13

switch(config-if)# show ptp port interfaceethernet 2/1



Example:

Step 14



PurposeCommand or Actionswitch(config-if)# copy running-configstartup-config

Configuring Unicast PTP PeersYou must configure both master and slave unicast PTP peers.

SUMMARY STEPS


3. ptp transport ipv4 ucast {master | slave}4. {master | slave} ipv4 ip-address

5. ptp ucast-source ip-address

6. (Optional) show ptp brief7. (Optional) show ptp counters interface ethernet slot/port ipv4 ip-address


DETAILED STEPS



Example:

Step 1


Specifies the interface on which you are enabling unicastPTP and enters the interface configuration mode.


Example:

Step 2


Configures the master or slave unicast PTP peer.ptp transport ipv4 ucast {master | slave}

Example:

Step 3

switch(config-if)# ptp transport ipv4 ucast master

Specifies the IP address of the master or slave unicast PTPpeer.

{master | slave} ipv4 ip-address

Example:

Step 4

switch(config-if)# slave ipv4 81.0.0.2

Specifies the IP address of the PTP unicast source.ptp ucast-source ip-address

Example:

Step 5

switch(config-if)# ptp ucast-source 81.0.0.1


Configuring IP Fabric for MediaConfiguring Unicast PTP Peers


Displays the PTP status.(Optional) show ptp brief

Example:

Step 6

switch(config-if)# show ptp brief

Displays the unicast PTP counters.(Optional) show ptp counters interface ethernet slot/portipv4 ip-address

Step 7

Example:switch(config-if)# show ptp counters interfaceethernet 1/1 ipv4 81.0.0.2



Example:

Step 8

switch(config-if)# copy running-configstartup-config

Example

The following example shows how to configure master and slave unicast PTP peers:interface Ethernet1/1ptp transport ipv4 ucast masterslave ipv4 81.0.0.2

ptp ucast-source 81.0.0.1ip address 81.0.0.1/24ip router ospf 1 area 0.0.0.2no shutdown

interface Ethernet1/2ptp transport ipv4 ucast slavemaster ipv4 83.0.0.2

ptp ucast-source 83.0.0.1ip address 83.0.0.1/24no shutdown

show ptp counters interface eth1/1 ipv4 81.0.0.2PTP Packet Counters of IP 81.0.0.2:----------------------------------------------------------------Packet Type TX RX---------------- -------------------- --------------------Announce 9 0Sync 70 0FollowUp 70 0Delay Request 0 18Delay Response 18 0PDelay Request 0 0PDelay Response 0 0PDelay Followup 0 0Management 0 0----------------------------------------------------------------



C H A P T E R 5Media Controller

This section describes the DCNMMedia Controller.

This feature is available only if you have enabled the Media Controller feature explicitly, after the CiscoDCNM OVA/ISO installation is complete. For more information, see the Cisco DCNM Installation Guide.

Note

This feature is available only if you have enabled Media Controller during the installation process. To enableMedia Controller, you have to choose the IP-Fabric Media Controller installation option during the OVA/ISOinstallation for DCNM. The appmgr set-mode media-controller command, used in earlier releases, is notavailable in DCNM 10.4(2).

To bring up the devices from the basic configuration using POAP, you must define the templates and publishthe POAP definition through Cisco DCNM Web Client > Configure > Deploy > POAP Definitions.

Specific POAP templates for Leaf and Spine for the Media Controller deployment are packaged with theCisco DCNM Software.

Note

If you have configured the Cisco DCNM server in Media Controller mode and performed the procedure thatis mentioned in the "POAP Launchpad" section, you will be able to see the Media Controller templates. CiscoDCNMWeb Client allows you to choose the required templates, edit them as required, and publish the POAPdefinition.

For information about the Media Controller APIs, see the Cisco DCNMMedia Controller API reference onCisco DevNet.

NX-OS Streaming Telemetry and DCNM

Using streaming telemetry, NBM process on the switch informs DCNM its state using which DCNM is ableto show discovered hosts and flows across the IP fabric. The POAP and pmn_telemetry_snmp CLItemplate, which are packaged in DCNM, generate the necessary telemetry configuration on the switch. Anexample of the generated configuration is as shown in the following sample:feature telemetry

telemetrydestination-profileuse-vrf management


https://developer.cisco.com/site/data-center-network-manager/

destination-group 200ip address 1.2.3.4 port 50051 protocol gRPC encoding GPB

sensor-group 200path sys/nbm/show/appliedpolicies depth unboundedpath sys/nbm/show/stats depth unbounded

sensor-group 201path sys/nbm/show/flows query-condition

rsp-subtree-filter=eq(nbmNbmFlow.bucket,"1")&rsp-subtree=fullsensor-group 202path sys/nbm/show/flows query-condition



rsp-subtree-filter=eq(nbmNbmFlow.bucket,"4")&rsp-subtree=fullsensor-group 205path sys/nbm/show/endpoints depth unbounded

subscription 201dst-grp 200snsr-grp 200 sample-interval 60000snsr-grp 201 sample-interval 30000snsr-grp 205 sample-interval 30000

subscription 202dst-grp 200snsr-grp 202 sample-interval 30000



• Topology, on page 56• PMN Hosts, on page 57• Flow Alias, on page 60• Policies, on page 62• Flow Status, on page 71• Events, on page 75

TopologyYou can view the Media Controller topology on the Web UI > Media Controller > Topology page. Thistopology is specific to the operations performed by DCNM as a Media Controller.

• If you remove a device from the Inventory, the Policy deployment status for that switch is removed.However, you must clear the policy configuration on the switch also.

Note

Quick Search

Enter the search string to highlight relevant devices.

The following fields are available to search on: switch or hostname, switch or host IP address, switchMAC, and switch serial number.


Media ControllerTopology

Multicast Group

Right-click (or press Return Key) in the field. A list of Multicast Addresses are displayed. You can choosethe multicast IP address for which you need to view the topology.

The devices under this multicast IP address, and links to spine and leaf are highlighted. The dotted movinglines depict the flow of traffic in the Media Controller topology.

You can search or filter based on flow alias name in the Topology. When you search for Multicast Group,you can search using the IP address or flow alias name.

PMN HostsCisco DCNM allows you to create hosts for Media Controller. The active transmitting and receiving devicesare termed as hosts. The hosts can be configured on Cisco Web Client > Media Controller > Hosts.

The PMN Hosts table is auto-populated once the traffic begins.Note

The following table describes the fields that appear on this page.

Table 8: Operations on PMN Hosts

DescriptionField

Allows you to add a new host.Add

Allows you to view or edit the selected hostparameters.

Edit

Allows you to remove the host from the fabric.Delete

Allows you to import host parameters from your localdirectory.

Import

Allows you to export host parameters information toyour local directory.

The exported file is in .csv format.

Export

Table 9: PMN Hosts Table Field and Description

DescriptionField

Specifies the configured name for the host device.Hostname

Specifies the IP address for the host.

You should not create a host using a WANinterface IP address since any host policythat is subsequently created using theWAN interface IP address may result inunexpected behavior.

Attention

IP Address


Media ControllerPMN Hosts

DescriptionField

Specifies the MAC address of the host switch.MAC Address

Specifies the name of the switch.Switch Name

Specifies the name of switch interface which the hostis associated with.

Interface Name

Specifies if the host is local to the DCNM managedfabric or belongs to an external fabric.

A remote host can be identified by the Remote labelon the host icon in the Topology page.

Remote Host

This section contains the following:

Starting from DCNM 10.4(2), the multisite option is supported. With this option, flows can be provisionedacross multiple sites. You need to enable multisite support and receiver bandwidth management by settingthe pmn.multi-site.enabled and pmn.host.port.policing.enabled functions to true, using the Administration>DCNM Server > Server Properties option, and restarting DCNM. The sender side bandwidthmanagementfor multisite is enforced by the switch and is enabled by default. Multisite support is only available for SourceSpecific Multicast (SSM), and border leaf switches. DCNM detects the PMN border leaf switch role duringdiscovery and depicts the PMN border leaf switch separately on the topology screen.

Note

Add PMN HostsTo add hosts from the Cisco DCNMWeb UI, perform the following steps:

Step 1 Choose Media controller > Hosts.

The Hosts window is displayed.

Step 2 Click the Add host icon.Step 3 In the Add Hosts window, specify the parameters in the following fields.

• Name: Specify a unique name for the host device.

• IP Address: Specify the IP Address of the host device.

• (Optional) MAC Address: Specify the MAC address of the host device.

Step 4 Click Save to configure the host.

Edit PMN HostsTo edit or view the host parameters from the Cisco DCNMWeb UI, perform the following steps:


Media ControllerAdd PMN Hosts



Step 2 Check the check box next to the host name, that you need to edit.Step 3 Click Edit host icon.Step 4 In the Edit Hosts window, edit the parameters in the Name and MAC Address fields.Step 5 Click Save to save the changes. Click Cancel to revert the host with same parameters.

Delete PMN HostsTo delete a host from the Cisco DCNMWeb UI, perform the following steps:



Step 2 Check the check box next to the hostname, to delete.

You can select more than one host to delete.

Step 3 Click the Delete host icon.Step 4 In the delete notification, click Yes to delete the host. Click No to cancel this action.

A Delete Host successful message appears at the bottom of the page.

Import PMN HostsTo import hosts, perform the steps below.

Step 1 From the menu bar, select Media Controller > Hosts.Step 2 Click Import host icon.Step 3 Browse the directory and select the file which contains the Host configuration information.Step 4 Click Open.

The host(s) configuration is imported and displayed on Media Controller > Hosts on the Cisco DCNMWeb Client.

Export PMN HostsTo export hosts, perform the steps below.


Media ControllerDelete PMN Hosts

Step 1 From the menu bar, select Media Controller > Hosts.Step 2 Click Export host icon.

A notification window appears.

Step 3 Select a location on your directory to store the Hosts configuration file.Step 4 Click OK.

The host(s) configuration file is exported to your local directory. The file name is appended with the date on which thefile is exported. The format of the exported file is .csv.

Flow AliasUsing the Flow Alias feature, you can specify names for multicast groups. The multicast IP addresses aredifficult to remember, thus by assigning a name to the multicast IP address, you can search and add policiesbased on the name.

You can configure a flow alias on Media Controller > Flow Alias.


Table 10: Flow Alias Table Field and Description

DescriptionField

Specifies the name of the Flow Alias.Flow Alias

Specifies the multicast IP address for the traffic.Multicast IP Address

Description added to the Flow Alias.Description

Specifies the date on which the flow alias was lastupdated.

Last Updated at


Add Flow AliasTo add flow alias from the Cisco DCNMWeb UI, perform the following steps:

Step 1 Choose Media controller > Flow Alias.

The Flow Alias window is displayed.

Step 2 Click the Add Flow Alias icon.Step 3 In the Add Flow Alias window, specify the parameters in the following fields.

• Flow Name: Specifies a unique flow alias name.


Media ControllerFlow Alias

• Multicast IP Address: Specifies the multicast IP Address for the flow alias.

• Description: Specifies the description that you add for the flow alias.

Step 4 Click Save to save the flow alias.

Click Cancel to discard.

Edit Flow AliasTo edit a flow alias from the Cisco DCNMWeb UI, perform the following steps:



Step 2 Check the check box next to the flow alias name, that you need to edit.Step 3 Click Edit Flow Alias icon.Step 4 In the Edit Flow Alias window, edit the Name, Multicast IP, Description fields.Step 5 Click Save to save the new configuration.

Click Cancel to discard the changes.

Delete Flow AliasTo delete flow alias from the Cisco DCNMWeb UI, perform the following steps:



Step 2 Check the check box next to the flow alias, that you need to delete.

You can select more than one flow alias to delete.

Step 3 Click Delete Flow Alias icon.

The flow alias is deleted.

Export Flow AliasTo export host alias from the Cisco DCNMWeb UI, perform the following steps:


Media ControllerEdit Flow Alias



Step 2 Click Export flow alias icon.


Step 3 Select a location on your directory to store the Alias details file.Step 4 Click OK.

The flow alias file is exported to your local directory. The filename is appended with the date on which the file is exported.The format of the exported file is .csv.

Import Flow AliasTo import flow alias from the Cisco DCNMWeb UI, perform the following steps:



Step 2 Click Import flow alias icon.Step 3 Browse the directory and select the file which contains the Flow Alias configuration information.Step 4 Click Open.

The flow alias configuration is imported and displayed on the Media controller > Flow Alias window, on the CiscoDCNMWeb Client.

Policies

Host PoliciesYou can add policies to the host devices. Navigate toMedia Controller > Policies > Host Policies to configurethe host policies.

By default, the sequence numbers for policies are auto-generated by DCNM and Multicast mask/prefix istaken as /32. The server property pmn.hostpolicy.multicast-ranges.enabled underAdministration > DCNMServer > Server Properties must be set to 'true' for the user to be able to provide sequence numbers andmulticast mask/prefix. When the server property is set to True, the fields to enter the sequence number andthe multicast mask/prefix is available in the Media Controller > Host > Host Policies > Add and MediaController > Host > Host Policies > Edit pages.


Media ControllerImport Flow Alias

The default host policies must be deployed successfully to the switch before you deploy the custom hostpolicies on that switch. Otherwise, the custom policies will fail to deploy. Ensure that you deploy all defaultpolicies successfully to all the switches before you add, edit, import, or deploy custom policies.


Table 11: Host Policies Operations

DescriptionField

Allows you to add a new host policy.Add

Allows you to view or edit the selected host policy parameters.Edit

Allows you to delete the user-defined host policy.

Note • Undeploy policies from all switches before deletingthem from DCNM.

• You can undeploy the default policy, but you cannotdelete the default policy. You can delete andundeploy only the custom policies.

• When you undeploy the default policies, All DefaultPolicies will be reset to have default permission(Allow).

Delete

Allows you to import host policies from a CSV file to DCNM.

After import, all policies imported from a CSV file areapplied to all managed switches automatically.

Note

Import

Allows you to export host policies from DCNM to a CSV file.Export

Table 12: Host Policies Table Field and Description

DescriptionField

Specifies the policy name for the host, as defined by the user.Policy Name

Specifies the host ID.Host Name

Specifies the multicast IP address for the host.Multicast IP


Specifies the IP Address of the sender.Sender IP

Specifies the host device role. The host device role is either one ofthe following:

• Sender

• Receiver

•

Host Acting As


Media ControllerHost Policies

DescriptionField

Specifies if the operation of the host policy. The policy has thefollowing operations:

• Permit

• Deny

Operation

Specifies the sequence number of the custom policy when themulticast range is selected.

Sequence #

Specifies the action performed on the switch for that host policy.

• Create─The policy is deployed on the switch.

• Delete─The policy is undeployed from the switch.

Deployment Action

Specifies the number of devices to which this policy is applied.Devices Applied To

Specifies if Protocol Independent Multicast (PIM) configuration isapplicable for the host policy.

PIM Policy

Specifies the date and time at which the host policy was last updated.

The format is Day MMM DD YYYY HH:MM:SS Timezone.

Last Updated


Add Host PolicyBy default, the sequence number for policies is auto-generated by DCNM, and Multicast mask/prefix is /32by default. The server property pmn.hostpolicy.multicast-ranges.enabled underAdministration > DCNMServer > Server Properties must be set to 'true' for the user to be able to provide sequence numbers andmulticast mask/prefix. When the server property is set to true, the fields to enter the sequence number andthe multicast mask/prefix are available in the Media Controller > Host > Host Policies > Add and MediaController > Host > Host Policies > Edit windows.

The default host policies must be deployed successfully to the switch before you deploy the custom hostpolicies on that switch. Otherwise, the custom policies will fail to deploy. Ensure that you deploy all defaultpolicies successfully to all the switches before you add custom policies.

To add Host policy from the Cisco DCNMWeb UI, perform the following steps:

Step 1 Choose Media Controller > Policies > Host Policies.

The Host Policies window is displayed.

Step 2 Click the Add icon.Step 3 In the Add Host Policy window, specify the parameters in the following fields.

• Policy Name: Specifies a unique policy name for the host policy.

• Host Role: Specifies the host as a multicast sender or receiver. Select one of the following:


Media ControllerAdd Host Policy

• Sender

• Receiver-Local

• Receiver-External

• PIM Policy: Select the check box if PIM configuration is needed for the host policy. The PIM Policy checkbox isonly applicable for the receiver role. If PIM policy is enabled, the Host field is disabled since the PIM policy is onlyapplicable for the receiver and it is applied to the multicast group.

• Host: Specifies the host to which the policy is applied. If a destination host is detected, you can choose the hostnamefrom the drop-down list.

Do not select hosts that are discovered as remote receivers to create receiver or sender host policies.However, hosts that are discovered as remote senders can be used for creating sender host policies.

Note

• Multicast IP: Specifies the multicast IP Address for the host policy.

• Allow/Deny: Click the radio button to choose, if the policy must Allow or Deny the traffic flow.

Step 4 Click Save to configure the host policy.Step 5 Click Save & Deploy to configure and deploy the Policy.

Click to discard the new policy.

Edit Host PolicyThe default host policies must be deployed successfully to the switch before you deploy the custom hostpolicies on that switch. Otherwise, the custom policies will fail to deploy. Ensure that you deploy all defaultpolicies successfully to all the switches before you edit custom policies.

To edit host policy from the Cisco DCNMWeb UI, perform the following steps:



Step 2 Check the check box next to the host policy name, that you need to edit.Step 3 Click Edit Host policy icon.Step 4 In the Edit Host Policy window, edit to specify if the policy will Allow or Deny traffic.

The changes made to Host Policy are applied immediately. If the policy is already applied to any device, thechanges may impact the existing flows.

Note

Step 5 Click Save to save the new configuration.Step 6 Click Save & Deploy to configure and deploy the Policy.

Click to discard the changes.


Media ControllerEdit Host Policy

Delete Host PolicyTo delete host policy from the Cisco DCNMWeb UI, perform the following steps:

You can delete only user-defined Host Policies.Note



Step 2 Check the check box next to the host policy name, that you need to delete.

You can select more than one host policy to delete.

Step 3 Click Delete Host policy icon.

Step 4 In the delete notification, click OK to delete the host policy. Click Cancel to return to the Host Policies page.

Deleting a host policy from DCNM does not undeploy the policy from the switches on which it is deployed.It is highly recommended to undeploy the policy on the switches before deleting it from DCNM.

Note

A Delete Host policy successful message appears at the bottom of the page.

Import Host PolicyThe default host policies must be deployed successfully to the switch before you deploy the custom hostpolicies on that switch. Otherwise, the custom policies will fail to deploy. Ensure that you deploy all defaultpolicies successfully to all the switches before you add custom policies.

To import host policies from the Cisco DCNMWeb UI, perform the following steps:



Step 2 Click the Import host policy icon.Step 3 Browse the directory and select the .csv format file which contains the Host Policy configuration information.

The policy will not be imported if the format in the .csv file is incorrect.

Step 4 Click Open.

The imported policies are automatically deployed to all the switches in the fabric.

Export Host PolicyTo export host policies from the Cisco DCNMWeb UI, perform the following steps:


Media ControllerDelete Host Policy



Step 2 Click the Export host policy icon.


Step 3 Select a location on your directory to store the Host Policy details file.Step 4 Click OK.

The host policy file is exported to your local directory. The filename is appended with the date on which the file isexported. The format of the exported file is .csv.

Flow PoliciesYou can configure the flow policies on Media controller > Flow Policies.

The default policies are displayed on the Flow policy page. By default, the bandwidth of these policies is 0.You can configure the bandwidth such that any flow that matches the default flow policy will accordinglyuse the bandwidth and QOS/DSCP parameters. The policy is deployed to all the devices when you save theconfiguration.

The default flow policies must be deployed successfully to the switch before you deploy the custom flowpolicies on that switch. Otherwise, the custom policies will fail to deploy. Ensure that you deploy all defaultpolicies successfully to all the switches before you add, edit, import, or deploy custom policies.

When you undeploy a default policy, it will be reset to default values, that is, Bandwidth:0gbps, DSCP:BestEffort, and Policer:Enabled.

Note


Table 13: Flow Policies Operations

DescriptionField

Allows you to add a new flow policy.Add

Allows you to view or edit the selected flow policyparameters.

Edit

Allows you to delete the user-defined flow policy.

Note • You cannot delete the default flowpolicies.

• Undeploy policies from all switchesbefore deleting them from DCNM.

Delete


Media ControllerFlow Policies

DescriptionField

Allows you to import flow policies from a CSV file.

After import, all policies imported from aCSV file are applied to all managedswitches automatically.

Note

Import

Allows you to export flow policies to a CSV file.Export

Table 14: Flow Policies Table Field and Description

DescriptionField

Specifies the flow policy name.Policy Name

Specifies the multicast IP address for the traffic.Multicast IP


Specifies the bandwidth that is allotted for the traffic.Bandwidth

Specifies the Switch-defined QoS Policy.QoS/DSCP

Specifies the action that is performed on the switchfor that host policy.

• Create─The policy is deployed on the switch.

• Delete─The policy is undeployed from theswitch.

Deployment Action

Specifies the date and time at which the flow policywas last updated.

The format is Day MMM DD YYYY HH:MM:SSTimezone.

Last Updated

A new flow policy or an edited flow policy is effective only under the following circumstances.

• If the new flow matches the existing flow policy.

• If the flow expires and reforms, while the new policy is already added or edited, that matches with theflow policy.

Note


Add Flow PolicyThe default host policies must be deployed successfully to the switch before you deploy the custom hostpolicies on that switch. Otherwise, the custom policies will fail to deploy. Ensure that you deploy all defaultpolicies successfully to all the switches before you add custom policies.


Media ControllerAdd Flow Policy

To add flow policy from the Cisco DCNMWeb UI, perform the following steps:

Step 1 Choose Media controller > Flow Policies.

The Flow Policies window is displayed.

Step 2 Click the Add Flow policy icon.Step 3 In the Add Flow Policy window, specify the parameters in the following fields.

• Policy Name: Specifies a unique policy name for the flow policy.

• Multicast IP: Specifies the multicast IP Address for the flow policy.

• Bandwidth: Specifies the bandwidth that is allocated for the flow policy. Select of the radio buttons to chooseGbpsor Mbps.

Step 4 From the QoS/DSCP drop-down list, choose an appropriate ENUM value.Step 5 Click Save to configure the flow policy.

Edit Flow PolicyThe default flow policies must be deployed successfully to the switch before you deploy the custom flowpolicies on that switch. Otherwise, the custom policies will fail to deploy. Ensure that you deploy all defaultpolicies successfully to all the switches before you edit custom policies.

To add flow policy from the Cisco DCNMWeb UI, perform the following steps:

SUMMARY STEPS

1. Choose Media controller > Flow Policies.2. Check the check box next to the flow policy name, that you need to edit.3. Click Edit Flow policy icon.4. In the Edit Flow Policy window, edit the Multicast IP, Bandwidth, QoS/DSCP fields.5. Click Save to configure the flow policy.

DETAILED STEPS



Step 2 Check the check box next to the flow policy name, that you need to edit.Step 3 Click Edit Flow policy icon.Step 4 In the Edit Flow Policy window, edit the Multicast IP, Bandwidth, QoS/DSCP fields.Step 5 Click Save to configure the flow policy.


Media ControllerEdit Flow Policy

Delete Flow PolicyTo delete flow policy from the Cisco DCNMWeb UI, perform the following steps:



Step 2 Check the check box next to the flow policy name, that you need to delete.

You can select more than one flow policy to delete.

You cannot delete the default policies.Note

Step 3 Click Delete icon to delete the selected flow policy.

Click Delete All icon to delete all the flow policies at a single instance.

Import Flow PolicyThe default flow policies must be deployed successfully to the switch before you deploy the custom flowpolicies on that switch. Otherwise, the custom policies will fail to deploy. Ensure that you deploy all defaultpolicies successfully to all the switches before you import custom policies.

To import flow policies from the Cisco DCNMWeb UI, perform the following steps:

SUMMARY STEPS

1. Choose Media controller > Flow Policies.2. Click the Import flow policy icon.3. Browse the directory and select the file which contains the Flow Policy configuration information.4. Click Open.

DETAILED STEPS



Step 2 Click the Import flow policy icon.Step 3 Browse the directory and select the file which contains the Flow Policy configuration information.Step 4 Click Open.

The flow policy configuration is imported and displayed on the Media controller > Flow Policies window, on the CiscoDCNMWeb Client.

The imported policies are automatically deployed to all the switches in the fabric.


Media ControllerDelete Flow Policy

Export Flow PolicyTo export host policies from the Cisco DCNMWeb UI, perform the following steps:



Step 2 Click the Export flow policy icon.


Step 3 Select a location on your directory to store the Flow Policy details file.Step 4 Click OK.

The flow policy file is exported to your local directory. The filename is appended with the date on which the file isexported. The format of the exported file is .csv.

Flow StatusCisco DCNM allows you to view the flow status pictorially and statistically. The flow status is available onMedia Controller > Flow Status.

The flow status collection frequency and cache size can be specified via cisco.pmn-stats-interval andcisco.pmn-stats-cache-size respectively in theAdministration > DCNM Server > Server Properties page.

Note

The following table describes the fields that appear on the Active tab.


Media ControllerExport Flow Policy

Table 15: Active Tab

DescriptionField

Click Show Chart icon to view the graphicalrepresentation of the Flow Status.

The data refers to the sender leaf when thesender starts broadcasting. Please see thereceiver start time in the flow status tableto find when the receiver started gettingdata.

Note

Click the Show drop-down list to view the flow statusinformation in one of the following formats─Chart,Table, or Chart and Table.

Click Chart Type icon to view the various charttypes. Select a chart type to view the flow statusinformation that is depicted in that chart format. Youcan choose a chart option to see filled patterns or datamarkers.

Click Actions icon to print the report or excel chartinformation to your local directory.

Show Chart

Specifies the multicast IP address for the flow.

You can click the wave link next to theMulticast IP address to view the pictorialrepresentation of flow statistics.

Note

Multicast IP


Specifies the IP Address or the Host alias of the senderfor the multicast group.

Sender

Specifies the IP Address or the Host alias of thereceiver joining the group.

Receiver


Specifies the Switch-defined QoS Policy.QOS/DSCP

Specifies the state of the flow link.

ClickREADY link state to view the network diagramof the Sender and Receiver.

Flow Link State

Specifies the policy ID applied to the multicast IP.Policy ID

Displays the time from when the receiver begins toreceive data.

Receiver Start Time

The following table describes the fields that appear on the Inactive tab.


Media ControllerFlow Status

Table 16: Inactive Tab

DescriptionField

Click Show Chart icon to view the graphicalrepresentation of the Flow Status.

The data refers to the sender leaf when thesender starts broadcasting. Please see thereceiver start time in the flow status tableto find when the receiver started gettingdata.

Note

Click the Show drop-down list to view the flow statusinformation in one of the following formats─Chart,Table, or Chart and Table.

Click Chart Type icon to view the various charttypes. Select a chart type to view the flow statusinformation that is depicted in that chart format. Youcan choose a chart option to see filled patterns or datamarkers.

Click Actions icon to print the report or excel chartinformation to your local directory.

Show Chart

Specifies the multicast IP address of the flow.Multicast IP


Specifies the IP Address or the Host alias of the senderfor the multicast groups.

Sender

Specifies the IP Address or the Host alias of thereceiver.

Receiver

Specifies the potential multicast receivers that havesubscribed to this group.

Waiting Receivers


Click the READY link state to view the networkdiagram of the Sender and Receiver.

The dotted line displays the direction of the flow oftraffic.

Flow Link State




DescriptionField

Specifies reason for the inactive flow.

Cisco DCNMdetermines the inactive flow if both thesender and receiver mroute exists with any of thefollowing combinations.

• Receiver IIF is null

• Receiver OIF is null

• Sender IIF is null

• Sender OIF is null

In this scenario, the switch will not have any faultreason. Therefore, there is no fault reason for suchinactive flows.

Fault Reason

The following table describes the fields that appear on the Sender Only tab.

Table 17: Sender Only Tab

DescriptionField

Specifies the multicast IP address for the flow.Multicast IP


Specifies the name of the sender.Name

Specifies the IP address of the sender that initiates themulticast flow.

Sender Leaf IP

Specifies the name of the sender leaf.Sender Leaf Name

Specifies the IP address of the sender switch.Sender Switch

Specifies the name of the sender ingress interface.Sender Ingress Interface

Specifies the flow link state, if it is allow or deny.Flow Link State



Specifies the state of the flow link.State

The following table describes the fields that appear on the Receiver Only tab.

Table 18: Receiver Only Tab

DescriptionField

Specifies the multicast IP address for the flow.Multicast IP



DescriptionField


Specifies the receiver ID. If the multicast receiver isremote, theRemote label can be seen next to its name.

Name

Specifies the IP address of the destination switch thatreceives the multicast flow.

Receiver Leaf IP

Specifies the name of the destination switch interface.Receiver Interface

Specifies the IP address of the receiver switch.Receiver Switch

Specifies the name of the leaf switch to which themulticast receiver is attached.

Receiver Leaf Name

Specifies the IP address of the multicast sender.Source Specific Sender



Specifies the time at which the receiver joined.Receiver Join Time

Specifies the number of receivers that are allotted forthe traffic.

Number of Receivers

Specifies the state of the flow link.State

Click theShow drop-down list in the statistical representation area to display the statistical data in variousformats.

Click the arrow to export the statistical data. You can export it in .csv or .pdf formats.

Cisco DCNMholds the Flow statistics values in the DCNM server internal memory. Therefore, after a DCNMRestart or HA switch over, the Flow statistics will not show previously collected values. However, you cansee the Flow statistics that are collected after the server Restart or HA switch over.

If the new flow joins before the uplinks between the switches that are detected in DCNM, a messageBW_UNAVAIL appears. This is resolved after the uplinks between the switches are detected by DCNM afterdiscovery of the devices.

Note

EventsCisco DCNM allows you to view and purge the various events between the Host and Flow. The Events arerecorded on Media Controller > Events.

The PMN Events table is updated real-time.

The maximum stored PMN events and cleanup frequency can be specified via pmn.rows.limit andpmn.delete.interval respectively in the Administration > DCNM Server > Server Properties page.


Media ControllerEvents


DescriptionField

Click to remove the old/unwanted events.

If the DCNM server restarts, by default a maximum of 5000event entries are retained for 6 hours.

Note

Click one of the radio buttons to choose the Purge options.

• Max # of Records—Enter the maximum number of records to delete.

• # of Days—Enter the number of days for which you need to deletethe events.

• Delete all data from the previous date—Specifies a date beforewhich all the data is deleted.

Click Purge to delete/retain PMN events information.

Purge

Specifies if the event category.Category

Specifies the severity of the event.Severity

Specifies the description of the event.

The sample description appears as:

Creating flow for FlowRequest:The flowRequest isfor hostId:<<IP_Address>>hostInterface:<<Host_Int_ID>> mcastIp:<<MulticastIP>> Is sender role:false originating fromswitch:<<Host IP Address>>

Description

Specifies the impacted flows due to this event.Impacted Flows

Specifies the date and time at which the event was last modified.

The format is Day MMM DD YYYY HH:MM:SS Timezone.

Last Update Time

Allows you to download the events to a local directory path.

The filename is appended with the date on which the file is exported. Theformat of the exported file is .xls.

Export


Media ControllerEvents

I N D E X

B

bandwidth 23, 30

C

class 32, 34class-map type qos match-all 32, 33class-map type qos match-any 32, 33controller ip 21, 28controller-credentials username 21, 28

D

dscp 23

F

feature interface-vlan 45, 46feature nbm 21, 22, 28, 29feature nxapi 20, 28feature ptp 49

I

interface vlan 45, 46ip access-list 31, 32, 33ip address 24, 25, 42, 43, 44, 45, 47ip group 30ip group-range 23, 30ip igmp immediate-leave 24, 26, 44, 45ip igmp snooping 45, 46ip igmp snooping fast-leave 45, 46ip igmp suppress v3-gsq 45, 47ip igmp version 24, 25ip igmp version 3 44, 45, 47ip ospf passive-interface 24, 25ip pim passive 43, 44, 45, 47ip pim pre-build-spt force 24, 26ip pim rp-address 24ip pim sparse-mode 24, 25, 43, 44, 45, 47ip pim spt-threshold infinity group-list 24, 25ip pim ssm range none 24ip router ospf 24, 25, 43, 44, 45, 47

M

master ipv4 52match access-group name 32, 33match ip multicast group 24, 25

N

nbm flow asm range 23nbm flow bandwidth 23, 30nbm flow-policy 23, 30nbm mode controller 21, 28nbm reserve unicast fabric bandwidth 23no shutdown 43, 44, 45, 47, 48

P

permit 32, 33policy 23, 30policy-map type qos 32, 34ptp 50ptp announce interval 50ptp announce timeout 50ptp delay-request minimum interval 51ptp offload 50ptp source 49ptp sync interval 51ptp transport ipv4 ucast master 52ptp ucast-source 52ptp vlan 51

R

route-map 24, 25

S

service-policy type qos input 32, 34set qos-group 32, 34show nbm controller 29show nbm flows 35show nbm flows bandwidth 29, 30, 35show nbm flows statistics 36show ptp brief 51, 53

Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Releases 7.0(3)I4(5), 7.0(3)F2(1), and Later 7.x ReleasesIN-1

show ptp counters interface ethernet 53show ptp port interface 51show running-config nbm 36slave ipv4 52switch-role border-leaf 21switchport 45, 47switchport access vlan 45, 48

switchport mode 45, 48switchport trunk allowed vlan 45, 48

V

vlan configuration 45, 46

Cisco Nexus 9000 Series NX-OS IP Fabric for Media Solution Guide, Releases 7.0(3)I4(5), 7.0(3)F2(1), and Later 7.x ReleasesIN-2

INDEX

cisco nexus 9000 series nx-os ip fabric for media solution … › c › en › us › td › docs...

Documents