Multicast-optimize on Nexus 5672UP

Wen configuring the following, multicast-optimize command is not support on Nexus 5672UP, while, it is support on Nexus 5548UP
policy-map type network-qos jumbo
    class type network-qos class-default
      mtu 9216
      multicast-optimize
Is there an QoS implementation difference between Nexus 5672UP and 5548UP?
In what situations should the multicast-optimize be used on the switch?
Will it influce unicast traffic when multicast-optimize is enabled?
Does it work on 40G interface?
Kind regards,
Lijun

Thanks Laurent
Em 06/12/2011, às 03:34, laaubert escreveu:
Home
Re: Multicast Filter on Nexus 7K
created by Laurent Aubert in Other Data Center Subjects - View the full discussion
Hi Marcio,
The equivalent of ip multicast boundary in NX-OS is PIM Join/Prune filter:
http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/nx-os/multicast/command/reference/mcr_cmds_i.html#wp1044461
Filtering applies at the control-plane level in this case.
HTH
Laurent.
Reply to this message by going to Home
Start a new discussion in Other Data Center Subjects at Home

Similar Messages

Prime Infrastructure 2.2 with Nexus 5672UP

Hi
I was wondering if anyone have managed to add Nexus 5672UP devices in Prime Infrastructure 2.2?
I noticed that it is not in the device supported list of 2.2.
I did however notice that the device is supported with Update Pack 7 in PI 2.1
Was wondering if one could load Update Pack 7 for PI 2.1 for PI 2.2 or if there is an update pack for PI 2.2 that includes this device?

Hi ,
Device Type: Nexus 5672UP
SYSOID: 1.3.6.1.4.1.9.12.3.1.3.1410
This device will be supported by first or second week of Feb.
Thanks-
Afroz
***Ratings Encourages Contributors ****

Vlan Select & Layer 2 Multicast optimization

I am going to implement this vlan select feature in my campus network. We are running on 7.3 & planning to move into 7.4 WLC code as well. I use below reference document for this task.
WLC 7.2 VLAN Select and Multicast Optimization Features Deployment Guide
I am bit confuse about layer 2 multicast optimization. Document says we can enable/disable by using below CLI commands. "
config network multicast l2mcast <enable|disable > <interface>"
I have 4 interfaces called student-wireless-1 to 4 (vlan 1161-1164) map into single interface group. For layer 3 multicast I will make vlan 1161 as the multicast interface with "multicast vlan feature" enabled. For layer 2 what should I do ? Is layer 2 multicast enable on all these interfaces by default ? If so should I disable l2 multicast on 3 of these interfaces like below ? Would there be any issue of disabling this layer 2 multicast on those interfaces ?
config network multicast l2mcast disable student-wireless-2
config network multicast l2mcast disable student-wireless-3
config network multicast l2mcast disable student-wireless-4
If it is not enabled by default, shoud I go ahead enable it on one interface like below ?
config network multicast l2mcast enable student-wireless-1
If someone can explain this that would be highly appreciated.

Thanks for the help but I found some further information. Some switches (2955, 2960, 3560 or 3750) can act as a "multicast querier", taking place of a multicast router without actually needing to support multicast routing. This means you dont actually need IP Services IOS or a layer 3 switch.
Configuation as per below;
http://www.cisco.com/en/US/customer/products/hw/switches/ps5528/products_configuration_guide_chapter09186a00803a9a29.html#wp1187873
Supported platforms below (look for igmp querier);
http://www.cisco.com/en/US/customer/tech/tk828/technologies_tech_note09186a0080122a70.shtml#topic3
Thanks for putting me on the right track however.

Multicast mac-address Nexus 7k

Hi,
i'm going to use Nexus 7000 in Data Center.
During analysis configuration, I need define mac-address-static configuration for multicast mac address for Firewall Checkpoint cluster.
In "Layer 2 Switching Configuration Guide, Release 4.1.pdf" documentation speak about
"Configuring a Static MAC Address
[..]You cannot configure broadcast or multicast addresses as static MAC addresses[..]"
Have you a suggestion to manage this problem and why is it not possible configure mac address static multicast?
Regards
Dino

Joseph - The ClusterXL A/A configuration is a variation of the StoneSoft or Rainfinity clustering technologies that have been used to cluster Solaris and other *NIX flavored servers and firewalls for years. (In fact, StoneSoft filed suit against Check Point in Europe 8 or 9 years ago for patent violations, and lost.) These configurations were very common on Check Point clusters running on Solaris from the late 90's forward - and, as you describe, have unicast IP's with a multicast MAC for the VIP. Even from the days of installing these on the brand new (at the time) 2900 series switches you had to do exactly as you state above - static MAC entries (or in some cases port mirrors) so traffic was directed to both active switch ports. In Active/Passive mode Check Point ClusterXL clusters are almost always "plug and play" today - rarely do the switches need anything beyond speed/duplex settings. The VIP assumes the MAC of the physical NIC it is currently bound to, and therefore there are no issues as far as switch config or proxy ARP entries on the gateways. All of these issues have to do with traffic flowing to the VIP and through the firewall, and the ability of the switch to correctly identify which physical switch port(s) the VIP is currently patched in to. This is one of three types of traffic associated with ClusterXL itself. The second is state synchronization, which is accomplished through a crossover cable and therefore not relevant. Even when using a switch state sync is a typical TCP 18181 connection from a unicast IP/unicast MAC on one gateway to the other through a dedicated interface pair.
The challenge described by CJ is not with the traffic flowing to the VIP, however. It is an entirely separate process - Check Point Clustering Protocol (aka CPHA if filtering in WireShark) is essentially the heart beat traffic. Every interface pair within a Check Point cluster continually communicates with its "partner" interface on the other cluster members. If any packet takes over 100ms or shows more than a 5% loss the gateway is forced in to "probing" mode where it falls back to ICMP to determine the state of the other cluster member. Depending on the CPHA timing settings an active gateway will failover to the passive in as quickly as 500ms or so. ClusterXL will fail over the entire gateway to the standby to avoid complications with asynchronous routing.
Out of the box, CCP is configured to use multicast, but it supports broadcast as well. To change this in real time (no restart required) simply issue the command:
cphaconf set_ccp {broadcast/multicast}
At the Ethernet level, CCP traffic will always have a source MAC of the Magic MAC of 00:00:00:00:xx:yy where XX is the “Cluster ID” – something identical on each cluster member but unique from one cluster to another, and YY is the cluster priority (00, 01, etc.) based on the priority levels set on cluster members within Dashboard on the cluster object. The destination MAC will always be the Ethernet broadcast of ff:ff:ff:ff:ff:ff.
At the IP level the source of CCP will always appear as 0.0.0.0. The destination will always be the network address (ie, x.x.x.0).
Similarly in multicast mode you will see the same traffic at the IP level but at the Ethernet level the destination will now be a IPv4 multicast MAC (ie, 01:00:5e:4e:c2:1e).
In a tcpdump with the –w flag opened in WireShark and a filter applied of just “cpha” (without the quotes) you should see a continual stream of traffic with the same source and destination IPs on all packets (0.0.0.0 and network IP), the destination of either a bcast or mcast MAC and the source MAC alternating between 00:00:00:00:xx:00 and 00:00:00:00:xx:01.
Long story short, the problem CJ is describing is a behavior on the 7K where a packet capture taken on the Check Point interface itself (ie, tcpdump –i eth0 –w capture.cap) ONLY shows CPHA traffic from it’s own source MAC and no packets from it’s partner. A tcpdump on the 7K itself will show traffic from both.
As CJ mentioned, a simple NxOS upgrade will fix the issue per:
This one:CSCtl67036 basically pryer to NX-OS 5.1(3) the nexus will discard packets that have a source of 0.0.0.0. Which in broadcast mode is exactly what the CCP heartbeat is. We bypassed this one.CSCsx47620 is the bug for the for static multicast MAC address feature but it requires 5.2 code on the 7k
(NOTE:Additional RAM may be required for the 5.2 update)
Also note that Check Point gateways do support IGMP multicast groups, given that you have the correct license. It is a feature of SecurePlatform Professional on the higher end gateways or as a relatively inexpensive upgrade on the lower end boxes or open platforms. For lab purposes you can simply type “pro enable” at the CLI (without the quotes). As of the latest build there is no technical limitation (no license check) so you can enable advanced routing features as needed for testing in a lab. For step by step details on configuring IGMP on SPLAT Pro go to the Check Point support site and search for sk32702.
This can be a frustrating issue to troubleshoot, so hopefully this helps someone avoid the headaches I ran in to.

Cisco Multicast Manager Support for NEXUS

Hi All,
Does Cisco Multicast manager support Nexus devices ?
Please help.

No at this time it does not according to the data sheets:
http://www.cisco.com/en/US/partner/prod/collateral/netmgtsw/ps6504/ps6335/ps6337/q_a_c67-527951.html
You can use cisco data center manager for managing Nexus devices:
http://www.cisco.com/en/US/products/ps9369/index.html
Download software:
http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=281722751

Nexus 5548UP for SAN Switch

We have purchased a Nexus 5548UP switch for our SAN environment. I've only configured it for jumbo frames and currently doing testing on the performance, as some say use jumbo frames while others say do not. My question is, and I know this is a loaded question but how do you guys go about configuring your SAN switches? What exactly are you configuring on it? Such as for performance tuning or the like. The reason I ask, is we have the switch and it's pretty much working, but I'd like to learn more about it and how to tune it and fully take advantage of the switch.

That is correct, between two Dell Optiplex workstations. We also tested between the server that will go into prod and an Optiplex, but once again the Optiplex could be the limiting factor. You think that could be it? Here's my config, so you know how it's setup right now.
version 5.2(1)N1(7)
hostname N5K
feature telnet
feature lldp
feature vtp
username admin password 5 $1$oZ1234567898765432123456/ role network-admin
banner motd #Nexus 5000 Switch
ip domain-lookup
policy-map type network-qos jumbo
class type network-qos class-default
mtu 9216
multicast-optimize
system qos
service-policy type network-qos jumbo
snmp-server user admin network-admin auth md5 0x422842c9d320064123456789fc703d20
priv d3264f23456789000c703d20 localizedkey
vrf context management
port-profile default max-ports 512
interface Ethernet1/1
flowcontrol receive on
flowcontrol send on
interface Ethernet1/2
interface Ethernet1/3
interface Ethernet1/4
interface Ethernet1/5
flowcontrol receive on
flowcontrol send on
interface Ethernet1/6
interface Ethernet1/7
interface Ethernet1/8
interface Ethernet1/9
flowcontrol receive on
flowcontrol send on
interface Ethernet1/10
interface Ethernet1/11
interface Ethernet1/12
interface Ethernet1/13
flowcontrol receive on
flowcontrol send on
interface Ethernet1/14
interface Ethernet1/15
interface Ethernet1/16
interface Ethernet1/17
interface Ethernet1/18
interface Ethernet1/19
interface Ethernet1/20
interface Ethernet1/21
interface Ethernet1/22
interface Ethernet1/23
interface Ethernet1/24
interface Ethernet1/25
interface Ethernet1/26
interface Ethernet1/27
interface Ethernet1/28
interface Ethernet1/29
interface Ethernet1/30
interface Ethernet1/31
interface Ethernet1/32
interface mgmt0
ip address 11.11.11.11/24
line console
exec-timeout 720
line vty
boot kickstart bootflash:/n5000-uk9-kickstart.5.2.1.N1.7.bin
boot system bootflash:/n5000-uk9.5.2.1.N1.7.bin

Multicasting with a guest anchor configuration.

Hi All
First time posting. :-)
I have a guest anchor controller in our DMZ servicing Apple devices. We are looking at options for using Apple TV to display/stream presentations from executive iPads and such. Since it uses bonjour (multicast) would I be able to utilize the new features available in 7.0.116.0 to implement this solution? I have 4 WiSM 1s servicing the headquarters building and one 4402 guest anchor. I believe this is possible based on the note in the document: VLAN Select and Multicast Optimization Features Deployment Guide; specifically the section:
Note: In a Guest Tunneling scenario, roaming between export foreign and export foreign is supported. However, roaming between export foreign and export anchor is not supported with VLAN Select.
In case of Auto Anchor:
Clients joining a foreign WLC, which is exported to an anchor WLC and mapped to a interface group, will receive an IP address in round robin method inside the interface group.
Clients joining a foreign WLC, which is exported to an anchor WLC and mapped to a interface only, will receive an IP address from that interface only.
Clients roaming between two or more foreign controllers mapped to a single anchor WLC with an interface group configured will be able to maintain its IP address.
Since I only have one guest anchor, I would assume based on this that I would fall under the export foreign - export foreign option and implementing this would be possible.
Could someone advise?
Thank you in advance!!

Thank you for information, I have the same problem. So I made a search on EoIP tunnel and Multicast.
http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a00808b4c61.shtml
Q I have a guest tunneling, Ethernet over IP (EoIP) tunnel, configured between my 4400 Wireless LAN Controller (WLC), which acts as the anchor WLC, and several remote WLCs. Can this anchor WLC forward subnet broadcasts through the EoIP tunnel from the wired network to wireless clients associated with the remote controllers?
A. No, the WLC 4400 does not forward IP subnet broadcasts from the wired side to the wireless clients across the EoIP tunnel. This is not a supported feature. Cisco does not support tunneling of subnet broadcast or multicast in guest access topology. Since the guest WLAN forces the client point of presence to a very specific location in the network, mostly outside the firewall, tunneling of subnet broadcast can be a security problem.
unofortunately it seems that multicast over EoIP does not work.

Wlc 5508 multicast/bonjour

hello,
i have a wlc 5508 with code 7.0.220, with multicast enabled in it and on the lan too.I am having a bit of confusion getting bonjour to work on the wireless side. Looking at some of the cisco docs, i still have some questions on how to get it working in my specific enviroment.
I have the wlc conected to the lan via a port-channel. 2 wlan (ssid1 and ssid2) each wlan maps to a specific vlan (dynamic int), the management int (also used for dynamic ap-manager) on a third vlan (vlan x).
The requirement:
I need to get Bonjour working between ssid1 and vlan-x, so my wireless clients (in ssid1 can use bonjour with their laptops) can synch between wireless and wired. I know that you can do this within the same wlan (ssid) but in this case, when a user has a laptop wired into the network he cant comunicate to the wireless device. I read about Vlan Select and Multicast Optimization however, from what i understand i need to setup an interface group and just assign my wlan1 and management int to it, correct?
Is there anyone that has this type of setup working? Can you provide some configs/print screens.
Another scenario that may come into play would also be when or if i need a different segment (vlan y) in my lan to also "bonjour" with ssid1? For this i assume i would need to create a dynamic interface on the wlc using the same IP segment and do the a new interface group?
thanks in advance

Cisco answers user questions about upcoming Apple Bonjour Gateway
How specific can you be about the beta release of the Gateway?
Beta for the v7.4 release will be in Oct/Nov of this year [2012].
[RECORDING]Better Application Device Visibility With Cisco’s Bonjour Gateway-20120724 1704-1

Multicast IGMP

What command turns on IGMP on when configuring Multicast?

For Nexus:
You cannot enable IGMP manually on an interface. IGMP is automatically enabled when you perform one of the following configuration tasks on an interface:
Enable PIM
Statically bind a local multicast group
Enable link-local group reports
Source: http://www.cisco.com/en/US/docs/switches/datacenter/sw/nx-os/multicast/configuration/guide/b_multicast_chapter_011.html
For Catalyst:
By default, IGMP snooping is globally enabled on the switch. When globally enabled or disabled, it is also enabled or disabled in all existing VLAN interfaces. IGMP snooping is by default enabled on all VLANs, but can be enabled and disabled on a per-VLAN basis.
Global IGMP snooping overrides the VLAN IGMP snooping. If global snooping is disabled, you cannot enable VLAN snooping. If global snooping is enabled, you can enable or disable VLAN snooping.
Beginning in privileged EXEC mode, follow these steps to globally enable IGMP snooping on the switch:
conf t
ip igmp snooping !Globally enable IGMP snooping in all existing VLAN interfaces.
end
Source: http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_55_se/configuration/guide/swigmp.html

Link Aggregation with QSFP links on 5672UP

Hi Everyone,
I have a question on my mind for quite some time regarding QSFP aggregation on Nexus 5672UP switch hoping gurus here could shield some light.
According to the data sheet, 5672UP supports 6 true QSFP. I am in a situation where a server require 2xQSFP(40Gbps) links to be bundled together. I wonder with QSFP, can I treat it as normal SFP+ interfaces and aggregate two QSFP links together using vPC to get 80Gbps? If it is possible, it absolutely offers better bandwidth and redundancy.
Thanks,

Hi,
Yes, you can aggregate the 2 QSFPs together in a Portchannel. Just remember if the server has 10Gig SFP+ interfaces, you need a special cable with one side with multiple SFP+ interfaces (4) and the other side 40Gig with MTP interface.
If the server has 40Gig interface than you can go straight from the switch to the server.
HTH

Nexus 56128P Transceiver Support

Hi All,
The documentations (datasheets, compatability matrix and release notes) are not clear so i would like to ask the community if those transceivers are supported and maybe someone use it in productive environment...
- GLC-SX-MM(D) on Nexus 56128P SFP+ Ports is this supported? (there is also no entry for Nexus 5600 Series in 1G Compatability Matrix)
- I'm pretty sure that SFP-10G-SR is working on Nexus 56128P SFP+ Ports but somehow it is missing in the Nexus 5600 Release Notes. It is working right?
Many thanks,
Manuel

Hi,
Based on the information from the data sheets, these switches are only 10/40Gig and not 1Gig.
Cisco Nexus 5672UP Switch: The Cisco Nexus 5672UP (Figure 1) is a 1RU 10 and 40 Gigabit Ethernet switch offering wire-speed performance for up to seventy-two 10 Gigabit Ethernet ports (using Quad Small Form-Factor Pluggable
Link:
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/datasheet-c78-730760.html
HTH

Waiting for flogi

I have one C220 connects to Nexus 5548UP via FCoE, but the vfc is in trunking, and the vsan is waiting for flogi.
Below is the conf,
vlan 1000
fcoe vsan 1000
vsan database
vsan 1000
interface vfc1
bind interface Ethernet1/1
switchport trunk allowed vsan 1000
no shutdown
vsan database
vsan 1000 interface vfc1
interface Ethernet1/1
switchport mode trunk
switchport trunk allowed vlan 1,1000
spanning-tree port type edge trunk
N5548# show int vfc 1 trunk vsan
vfc1 is trunking
    Vsan 1000 is down (waiting for flogi)
Any reason?
Thanks,
Jeff

# sh run ipqos all
!Command: show running-config ipqos all
!Time: Wed Mar 13 16:05:36 2013
version 5.1(3)N2(1c)
class-map type qos class-fcoe
class-map type qos match-any class-default
class-map type qos match-any class-all-flood
class-map type qos match-any class-ip-multicast
class-map type queuing class-fcoe
match qos-group 1
class-map type queuing class-default
match qos-group 0
class-map type queuing class-all-flood
match qos-group 2
class-map type queuing class-ip-multicast
match qos-group 2
policy-map type qos default-in-policy
class class-default
policy-map type qos fcoe-default-in-policy
class class-fcoe
    set qos-group 1
class class-default
policy-map type queuing default-in-policy
class type queuing class-default
    bandwidth percent 100
policy-map type queuing default-out-policy
class type queuing class-default
    bandwidth percent 100
policy-map type queuing fcoe-default-in-policy
class type queuing class-fcoe
    bandwidth percent 50
class type queuing class-default
    bandwidth percent 50
policy-map type queuing fcoe-default-out-policy
class type queuing class-fcoe
    bandwidth percent 50
class type queuing class-default
    bandwidth percent 50
class-map type network-qos class-fcoe
match qos-group 1
class-map type network-qos class-default
match qos-group 0
class-map type network-qos class-all-flood
match qos-group 2
class-map type network-qos class-ip-multicast
match qos-group 2
policy-map type network-qos default-nq-policy
class type network-qos class-default
    multicast-optimize
policy-map type network-qos fcoe-default-nq-policy
class type network-qos class-fcoe
    pause no-drop
    mtu 2158
class type network-qos class-default
    multicast-optimize
system qos
service-policy type qos input fcoe-default-in-policy
service-policy type queuing input fcoe-default-in-policy
service-policy type queuing output fcoe-default-out-policy
service-policy type network-qos fcoe-default-nq-policy
fex queue-limit
interface Ethernet1/1
priority-flow-control mode auto
interface Ethernet1/2
priority-flow-control mode auto
interface Ethernet1/3
priority-flow-control mode auto
interface Ethernet1/4
priority-flow-control mode auto
interface Ethernet1/5
priority-flow-control mode auto
interface Ethernet1/6
priority-flow-control mode auto
interface Ethernet1/7
priority-flow-control mode auto
interface Ethernet1/8
priority-flow-control mode auto
interface Ethernet1/9
priority-flow-control mode auto
interface Ethernet1/10
priority-flow-control mode auto
interface Ethernet1/11
priority-flow-control mode auto
interface Ethernet1/12
priority-flow-control mode auto
interface Ethernet1/13
priority-flow-control mode auto
interface Ethernet1/14
priority-flow-control mode auto
interface Ethernet1/15
priority-flow-control mode auto
interface Ethernet1/16
priority-flow-control mode auto
interface Ethernet1/17
priority-flow-control mode auto
interface Ethernet1/18
priority-flow-control mode auto
interface Ethernet1/19
priority-flow-control mode auto
interface Ethernet1/20
priority-flow-control mode auto
interface Ethernet1/21
priority-flow-control mode auto
interface Ethernet1/22
priority-flow-control mode auto
interface Ethernet1/23
priority-flow-control mode auto
interface Ethernet1/24
priority-flow-control mode auto

RRoCE v2.0 mode was requested, but it is not supported.

Customer is using N5k, connecting W2012 R2 host, as well as a W2012 R2 host acting as a SMB3 fileserver.
They use RDMA over Converged Ethernet (RoCE), and receive the following error message
SingleFunc_32_0_0: RRoCE v2.0 mode was requested, but it is not supported. The NIC starts in RRoCE v1.5 mode.
NOTE: If your environment contains mix of different NIC types, you need to make sure that the whole environment is configured to use the same RoCE mode,
otherwise the traffic between the different NICs does not work.
interface Ethernet1/13
priority-flow-control mode on
flowcontrol send off
flowcontrol receive off
end
Global QoS Config
class-map type qos match-any class-rdma
match cos 3
class-map type queuing class-rdma
match qos-group 4
policy-map type qos rdma-policy
class class-rdma
    set qos-group 4
class class-default
policy-map type queuing rdma-queuing-policy
class type queuing class-rdma
    bandwidth percent 60
class type queuing class-default
    bandwidth percent 40
class-map type network-qos class-rdma
match qos-group 4
policy-map type network-qos rdma-network-policy
class type network-qos class-rdma
    pause no-drop
class type network-qos class-default
    multicast-optimize
system qos
service-policy type network-qos rdma-network-policy
nterface Ethernet1/13
service-policy type qos input rdma-policy
service-policy type queuing input rdma-queuing-policy
service-policy type queuing output rdma-queuing-policy
The end to end link is not working ? Any hints what could be wrong ?

http://www.mozilla.com/en-US/firefox/4.0/system-requirements/
Mac
Operating Systems
* Mac OS X 10.5
* Mac OS X 10.6
Recommended Hardware
* Macintosh computer with an Intel x86 processor
* 512 MB of RAM
* 200 MB hard drive space
For older Macs that aren't supported in Firefox 4.0, try TenFourFox for PowerPC's running Mac 10.4.11 & 10.5.8 . <br />
http://www.floodgap.com/software/tenfourfox/
Or revert to Firefox 3.6.16, which is available here: <br />
http://www.mozilla.com/en-US/firefox/all-older.html

QSFP+ ports, do they support regular SFPs ?

Hi all,
I have a question regarding QSFP+ ports on Nexus 5672UP and 3000 series. Can you plug in a normal 10GE LR SFP in the QSFP+ ports ?
(so the port converts to a regular 10GE port, not 40GE) ?
I am looking in particular to connect a QSFP+ switch with 10GE long-range fiber (other ports are all RJ45, ie C3172TQ) ?
I know there is a 4x 10GE breakout cable, but this is SR, i need LR...
regards,
GN

Hi GN,
there is actually a module that can be used within the QSFP ports to convert QSFP+ to SFP+ or GLC.
Have a look.
CVR-QSFP-SFP10G=
http://www.cisco.com/c/en/us/products/collateral/interfaces-modules/transceiver-modules/data_sheet_c78-729336.html
Regards,
Marco

NEXUS Multicast questions

I have a question in regards to multicast support for the NEXUS 1000V/4001i/5548 w/L3 Daughter card. Before the questions a quick background: We are in the process of buying a IBM blade center with the aforementioned network pieces. We are a modeling and simulations site and the servers we use primarily communicate via multicast. Typically 6 class C’s worth of multicast addresses are reserved for this per event. I was looking at doing layer 3 on the 5548’s but it has a limitation of 2000 multicast entries and I’m not even sure what that means i.e per VLAN/VRF or just total. We have 4 suites - so if we run two events at the same time we will bust that number quick. So we will continue to do layer 3 at the 6509’s for mcast and the nexus family will handle it at layer 2.
My real questions and concerns are these:
The 4001i states it will hold 1000 IGMP (Snooping) entries. What happens when it exceeds this number? Should we just turn IGMP snooping off and let it flood everything in that VLAN (I have my concerns with that).
I cannot find any multicast limitations on the 1000v – are there any?
Any advice/help will be greatly appreciated.
Thanks
Brad

Ex,
Yes, all three Nexus products are available for order as of today.
As for Fabric Path, it's currently only supported on the Nexus 7K, with the F1 Line cards running NXOS 5.1 or later. Fabric Path will be available on the 5548/5596 running 5.1(3)N1(1) codename "Fairhaven" release of NXOS. Currenlty targeting mid-late 2011.
FYI - Fabric Path will require a separate license.
Regards,
Robert

Multicast-optimize on Nexus 5672UP

Similar Messages

Maybe you are looking for