Hello...
Following the recent(ish) upgrade to CH which allows a Home processor to deal with devices across VLANs, we have implemented VLANs on a larger site.
The site was running multiple NVX devices on an already busy network. ?Previously we were seeing some packet loss and lag but the new VLAN arrangement has much improved these symptoms. ?General network performance is improved too (outside of the Crestron stuff).
Aside from having to change the Processor to an IP address (instead of the default hostname) in each NVX/NAX device web GUI, this was a straightforward change and everything came online ok.
However: ?we are now unable to connect to NVX AES67 streams from the NAX. ?On the web GUI of the NAX we just see 'Connecting' under the Stream Status table.
Multicast addresses are all correct. ?System was set up natively in CH (authentication, chdevice etc.) but we have tried a few manual tweaks as well.
Video is working fine, Airplay working fine. ?Multicast / IGMP appears to be right; there's no network flooding or crashing and the NVX is streaming video perfectly happily.
Since the Multicast addresses are populating correctly, perhaps this hanging on 'Connecting' might be an authentication issue... however, the only user in the user table is the system-generated chdevice. ?(I did try adding the chdevice user to the 'connects' group as well, but no avail)
This was working fine before we put the VLANs in. ?
We are using dual ethernet ports on the NAX. ?1=Management, 2=AES67. ?Note the Management VLAN is our General Access network, for Airplay etc, *not* our Control System VLAN which is seperate again. ?So I suppose we could put the NVX/NAX back onto our control system subnet but we'd prefer not to.
Has anyone else seen/overcome this?
