Blu-32 not connecting via net gear switch
abiggerjimjr
Posts: 2
I'll try to keep this as short as I can.
I have had a BLU-80 -> Netgear switch -> two BLU-32s setup working perfectly for several years now. Yesterday I removed the switch to replace it with a new one, and now the devices aren't connecting to each other. I reloaded the programming from my PC and uploaded the firmware to try to solve the problem with no luck. I can plug the BLU-80 directly into (no switch) one of the BLU-32s and it works fine, but as soon as I put the switch back in the signal path, I can't get audio anymore. I am fairly familiar with setting up and building with the London Architect software, but I just don't know what to look for to try and solve this. Please help! I need this system to work again for church services this Sunday!
If it makes any difference, when I connect the Cat5 cable directly from the BLU-80 to the BLU-32, the orange light on the left of the primary jack on the BLU-32 is solid orange. But when I put the switch in, the orange light flashes. It seems to me like that means something, but I can't seem to find something that tells me what.
I have had a BLU-80 -> Netgear switch -> two BLU-32s setup working perfectly for several years now. Yesterday I removed the switch to replace it with a new one, and now the devices aren't connecting to each other. I reloaded the programming from my PC and uploaded the firmware to try to solve the problem with no luck. I can plug the BLU-80 directly into (no switch) one of the BLU-32s and it works fine, but as soon as I put the switch back in the signal path, I can't get audio anymore. I am fairly familiar with setting up and building with the London Architect software, but I just don't know what to look for to try and solve this. Please help! I need this system to work again for church services this Sunday!
If it makes any difference, when I connect the Cat5 cable directly from the BLU-80 to the BLU-32, the orange light on the left of the primary jack on the BLU-32 is solid orange. But when I put the switch in, the orange light flashes. It seems to me like that means something, but I can't seem to find something that tells me what.
0
Comments
It's a quite difficult answer to give, as there are so many things influencing the network.
First off all, you should know, that the interface making the cobranet within the blu-s is the \"CM-1\" if you do a little google, you'll find out quite a lot about this device.
Then, to start realy simple. did you restart the devices, with pluged into the new switch? Cobranet is a protocol binding to layer 2 of the OSI Modell, so there is a lot of ARP-handling and if the arp resoulution fails, there is no sound.
Then, what type of switch are you using now, I would realy advise you to use a managed switch such as the HP 25xx or higher series. They are quite cheap by now and you are able to control the ports, one by one.
Respecting this advise, I would set the Port connected to the CM-1 to \"Auto-100\" this will disable the Gigabit Autosensing, the CM-1 is 100Mbit anyway.
Well, finaly, why the hell did you change the switch??? You know, never (and i mean never-ever!) touch a running system, if you don't have reason for doing so. If you have any reason, please tell, as this might be the key.
I have a far more complex setup by now, with 10 switches, spanning-tree and so on, and it's all running fine, there has to be something you didn't care about...
Is the switch the exact same model?
Is the switch configure the same?
Cobranet needs a switch that meets the following requirements:
NON-BLOCKING - No filtering of any traffic or protocols
WIRESPEED - The switch must be able to withstand the combined traffic of all cobranet ports a full duplex 100MB traffic. Technically it is 100MB[Cobranet is fixed @ 100MB] x 2[full duplex] x number of ports. This will sometimes be listed in the spec as switch speed, meshing speed or switching fabric speed.
From your discription it sounds like your switch is blocking UDP and/or multicast traffic