-
The number of leaf switches depends on the number of uplinks that are used and the number of ports available on the spine
switch.
-
Before you enable NBM, make sure that no flows are active on the switch. If there are active flows, either turn off the flows
or reload the switch after configuring NBM.
-
We recommend using a Layer 3 routed port to an endpoint.
-
In a single modular switch deployment using -R line cards with SVIs and endpoints that are connected through a Layer 2 port,
the maximum number of flows is 2000.
-
For Cisco Nexus 9504 and 9508 switches with -R line cards, six fabric modules are needed for NBM.
-
To ensure non-blocking performance, the uplink bandwidth from each leaf switch must be greater than or equal to the bandwidth
provided to the endpoints.
-
When possible, spread the endpoints across different leaf switches so that there is an equal distribution of 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 to the endpoint and
another to the switch interface.
-
The solution supports IGMPv2 and IGMPv3 joins and PIM Any Source Multicast (ASM) and PIM Source-Specific Multicast (SSM).
If multiple sources are sending traffic to the same multicast group in the ASM range, the bandwidth in the fabric is accounted
for only one flow. Oversubscription could occur, so take care to avoid multiple senders sending traffic to the same multicast
group in the ASM range. In the SSM range, different sources can transmit to the same group, and the bandwidth in the fabric
is accounted on a per flow basis.
-
Statistics are available only on the switch where senders are connected.
-
NBM is not supported with enhanced ISSU. Do not use the [no] boot mode lxc command in IP fabric for media setups.
-
To conserve resources, we recommend disabling statistics when using the service-policy type qos command.
-
The IP fabric for media solution supports receiver-side bandwidth management, where the IGMP and PIM endpoints on the external
link are bandwidth managed.
-
The IP fabric for media solution supports dynamic flow policy changes for DSCP and flow bandwidth.
-
All supported IP fabric for media platforms allows the sender or receiver end hosts to be connected to the spine.
-
The IP fabric for media solution supports multiple border leafs per fabric.
-
If you change the unicast bandwidth percentage, you must flap the fabric links for the new value to take effect.
-
Only Layer 3 interfaces can be configured as NBM external links. If a Layer 3 interface is changed to a switch port, the NBM
external link configuration is removed.
-
When you configure a Layer 3 interface as an NBM external link, the interface flaps.
-
If an RPF or any of the OIF interfaces cannot accommodate a bandwidth change, the flow is torn down. The next IGMP or PIM
join will initiate flow stitching.
-
When you change the flow policy (bandwidth) for groups with existing flows in the fabric, make the changes in the following
order to reduce the impact on existing flows. Otherwise, oversubscription could occur, depending on the available bandwidth
for the interfaces in use.
-
Change from a lower to higher bandwidth: Modify the policy first on all last hop routers for the existing flows, then on all
spine switches, and then on the rest of the switches.
-
Change from a higher to lower bandwidth: Modify the policy first on all first hop routers for the existing flows, then on
all spine switches, and then on the rest of the switches.
-
Statistics are not available if you disable the NBM flow policer.
-
During a failure, the PMN Flow Prioritization feature tries to recover priority
flows where possible. By design, PMN Flow Prioritization does not bring down
already established flows to accommodate priority flows.
-
Beginning with Cisco Nexus Release 10.1(1) PMN Flow Prioritization with NBM is supported on Cisco Nexus 9300-FX3 platform
switches.
-
Beginning with Cisco NX-OS Release 10.1(2), PMN is supported on the N9K-X9624D-R2, and N9K-C9508-FM-R2 platform switches.
-
Beginning with Cisco NX-OS Release 10.2(1q)F, PMN is supported on the N9K-C9332D-GX2B platform switches.
-
For Cisco Nexus 9500 -R line cards, when configured in NBM Passive mode there will be increasing input discards and this has
been determined to be expected and non-impacting.
-
NBM running on a VXLAN enabled switch is not supported. Feature NBM may disrupt VXLAN underlay multicast forwarding.
-
Beginning with Cisco NX-OS Release 10.3(1)F, the following PMN features are supported on the Cisco Nexus 9808 platform switches:
-
Spine and single-box support (L3 front panel ports only, no L2 ports/SVI support).
-
Flow Policy/Host policy for host administration.
-
Pim-Active and Pim-Passive modes of flow provisioning.
-
Oper MO publishing for flows/ends points published for
NDFC enablement.
-
Beginning with Cisco NX-OS Release 10.4(1)F, this feature is also supported on Cisco Nexus X98900CD-A line cards with Cisco
Nexus 9808 switches.
-
Beginning with Cisco NX-OS Release 10.4(1)F, this feature is supported on Cisco Nexus X98900CD-A and X9836DM-A line cards
with Cisco Nexus 9804 switches.
-
Beginning with Cisco NX-OS Release 10.3(2)F, Multicast service reflection (Multicast NAT) is now extended to sub-interfaces
on all host and fabric ports for NBM mode pim-active and NBM mode pim-passive on Cisco Nexus 9200, 9300, 9408 and 9800 platform
switches, and Cisco Nexus 9504 and 9508 switches with -R line cards.
-
Parent port and its corresponding subinterfaces are expected to be part of the VRFs which are in same nbm pim-active or nbm
pim-passive mode.
For example: If the parent port is part of NBM VRF which is in PIM active mode, its subinterfaces must also be in the VRF
(can be different VRF context) with the same PIM active mode.
-
Beginning with Cisco NX-OS Release 10.3(2)F, Sub-interface type is now supported in NBM mode pim-active and NBM mode pim-passive.
-
Beginning with Cisco NX-OS Release 10.3(2)F, NBM mode pim-active and NBM mode pim-passive can coexist on the same switch.
-
From Cisco NX-OS Release 10.4(1)F, ISIS is supported with NBM.
-
From Cisco NX-OS Release 10.4(1)F, NBM is supported on Cisco Nexus 9348GC-FX3 switch.
-
From Cisco NX-OS Release 10.4(2)F, NBM is supported on Cisco Nexus C93108TC-FX3 switch.
-
Beginning with Cisco NX-OS Release 10.4(2)F, endpoint MOs published based on Interface IP instead of host IP, for the receiver
in SVI interface and reporterIP on the flowMO, the SVI receivers will have interfaceIP instead of hostIP.
-
Beginning from Cisco NX-OS Release 10.4(2)F, with NBM you can now access L2 port information in addition to the existing L3
port flow data, improving better visibility into the flow path. This feature is supported for the following TOR and EOR switches:
-
Nexus 92348GC-X Platform Switches
-
Nexus 9300-EX/FX/FX2/FX3/H1 Platform Switches
-
Nexus 9300C/GX/GX2 Platform Switches
-
Nexus 9700-EX/FX/GX line cards
-
Nexus 9600-R/R2 line cards