I am working to make my AV Control network more robust by replacing consumer grade routers with business class hardware. Disclaimer, I am not a networking professional and am self taught via this forum, YouTube etc. My current setup is as follows:
Cisco SG300 switches (all linked via trunks) running 4x VLANs:
- Control and Data network
- Medical Devices
- Presentation Devices
- DANTE audio network (no DHCP/no Internet)
I am adding a Cisco RV130 Router/Gateway to serve DHCP and Gateway server for 3x VLANs (via LAN4 as a Trunk to a Trunk port on the SG300)
The current parameters for each VLAN are:
- 192.168.3.1, 255.255.0.0 with DHCP from 192.168.3.200 - 192.168.3.250
- 192.168.169.1, 255.255.255.0 with DHCP from 100 - 200 (no gateway/no internet access)
- 192.168.19.1, 255.255.255.0 with DHCP from 100 - 200
- Static 192.168.23.x, 255.255.0.0
For VLAN 1, I am using a 255.255.0.0 subnet as each device type is on its own octet i.e.
- Touch panels = 192.168.20.x
- Display Controllers = 192.168.21.x
This has all been working well for me, however if I setup VLAN 1 as 255.255.0.0, the RV130 will refuse to allow me to setup other VLANS on 192.168.x.x as it claims the interface is already in use. I am assuming this is because 192.168.3.1 on 255.255.0.0 could allow for 192.168.3.1 - 192.168.255.255 , even though I've only set it to issue DHCP addresses to the 192.168.3.100 - 192.168.3.200 range.
My current work around is to use my existing TP-Link router for 192.168.3.1 255.255.0.0 and the Cisco RV130 for the other VLANs, but the whole point of this exercise is to have one device to manage all DHCP for all VLANs.
Any guidance would be appreciated on the best way to make this happen.
No comments:
Post a Comment