Ethernet Switching
Highlighted
Ethernet Switching

Multicast Configuration for Crestron NVX Equipment

‎09-10-2020 07:36 AM

We are implementing an A/V over IP solution from Crestron with the NVX products. Crestron provided our A/V company with a sample single-switch Cisco configuration as well as a guide to network design. The guide isn't very help but gives the following minimum network requirements:

Network switch:

1-gig port for every connect NVX endpoint

Nonblocking backplane

Layer 3

IGMPv2 Implementation

Network Switch Settings:

IGMPv2 snooping enabled

IGMPv2 querier enabled

Fast-leave/immediate-leave enabled

Inter-switch Uplinks:

Sufficient bandwidth

Uplinks must be configured properly to support multicast traffic

 

My question is how do I properly configure multicast so that the traffic travels across the network as it should?

 

I've attached a diagram that includes the switches that NVX traffic touches in one of the larger spaces.

The A/V rack has an EX2300 with NVX transmitters/receivers attached.

That EX2300 connects to an EX3300 VC in that floor's IDF.

The IDF connects to our core EX4300 VC.

Also connected to the core is an EX3300 VC from a server rack that houses the Crestron XIO director. The XIO is a server that controls where NVX traffic is routed.

 

Crestron recommends putting control traffic and NVX traffic on different VLANs. Control traffic would be things like touch panels that allow users to turn on A/V systems and select inputs and outputs. NVX is the actual video/audio traffic. I created VLAN 30 Multimedia for control traffic and VLAN 31 Crestron_NVX for NVX traffic.

 

The relevant sample Cisco configuration is below. 

bridge multicast filtering

vlan 30-31

!

interface vlan 30

ip address 192.168.1.1 255.255.0.0

!

interface vlan 31

ip igmp version 2

!

interface GigabitEthernet1/0/1

bridge multicast unregistered filtering 

switchport access vlan 31

ip igmp version 2

!

---All of the interface ports in their sample are the same

The trunk port is:

interface TengigabitEthernet1/0/1
bridge multicast unregistered filtering
spanning-tree link-type point-to-point
switchport mode trunk
switchport access vlan none
ip igmp version 2

 

The IGMP config is:

ip igmp snooping
ip igmp snooping vlan 31
ip igmp snooping vlan 31 forbidden mrouter interface gi1/0/11
ip igmp snooping vlan 31 immediate-leave
ip igmp snooping vlan 31 querier
ip igmp snooping vlan 31 querier address 192.168.1.1

 

 

Based on that, this is what I have:

CORE

protocols {

 igmp-snooping {

  vlan default; (this was on the switch out of the box)

  vlan Crestron_NVX {

   l2-querier {

    source-address 172.29.1.1; (this is the switch's IP)

    }

   immediate-leave;

  }

 }

}

vlans {

 Creston_NVX {

  vlan-id 31;

 }

 Multimedia {

  vlan-id 30;

  l3-interface irb.30;

 }

}

interfaces {

 unit 30 {

  description Multimedia;

  family inet {

   address 172.30.1.1/16;

  }

 }

}

 

Originally I had an irb attached to vlan 31 to allow routing between the VLANs. The XIO server has several ports on it that allows for connecting to switchports in different VLANs. I connected the server to the server rack switch in two ports. One port in VLAN 30 and one in VLAN 31. A loop of some sorts was obviously created in this scenario. I removed irb 31 at that point.

 

SWITCH 3 - Server Rack

protocols {

 igmp-snooping {

  vlan all; (this was on the switch out of the box)

  vlan Crestron_NVX {

   immediate-leave;

  }

 }

}

vlans {

 Creston_NVX {

  vlan-id 31;

 }

 Multimedia {

  vlan-id 30;

 }

}

 

SWITCH 1 - IDF

protocols {

 igmp-snooping {

  vlan all; (this was on the switch out of the box)

  vlan Crestron_NVX {

   immediate-leave;

  }

 }

}

vlans {

 Creston_NVX {

  vlan-id 31;

 }

 Multimedia {

  vlan-id 30;

 }

}

 

 

SWITCH 2 - A/V Rack

protocols {

 igmp-snooping {

  vlan default; (this was on the switch out of the box)

  vlan Crestron_NVX {

   immediate-leave;

  }

 }

}

vlans {

 Creston_NVX {

  vlan-id 31;

 }

 Multimedia {

  vlan-id 30;

 }

}

forwarding-options {

 storm-control-profiles unreg_multicast {

  all {

   bandwidth-percentage 80;

   no-unregistered-multicast;  

}

}

 

I applied that storm control profile to all of the interfaces except the trunk port.

}

 

 

I know this is a long question so appreciate any help!!

Attachments

Feedback