Essentially connecting two routers into one switch.
I have a GS752TPP in a secondary cabinet fed from the first cabinet.
There are two incoming connections into the cabinet giving DHCP.
On this switch
I want to use 24 ports for devices on one network (data 192.168.10.0/24) and 24 ports for devices on another network (telephone 192.168.1.0/24). Is it feasible to configure this switch to do this as there is limited space in a cabinet for two separate switches?
In essence have two routers connected and ports on the switch are completely independent networks. The switch itself has no need to do DHCP as DHCP is given out by the two networks. Hopefully be able to do this via two VLANS?
I have set up the VLANs and each will work if one network is connected. Connect the other network and it causes both networks to stop working. If feasible, some easy instructions on how to achieve this.
The nearest similar situation I have come across is below so it seems as if this is feasible. However, the solution does not seem to be clear and I need a little guidance on whether the Netgear can do this and some simple instructions on how?
Here is the potential solution although not perfect yet!
Set up one of the network (main data network) on the management VLAN 1.
Set up second VLAN for telephone network. No DHCP, No IP, e.g. VLAN 200 and select ports.
Set all ports on VLAN 200 to Access ports.
Remove VLAN 1 from all ports on VLAN 200.
In theory, ready to plug in second DHCP uplink into a port on VLAN 200
This causes entire data network to stop - some sort of loop - errors below.
LLDP-6-NEIGHBOR_DEL proto_lldp.c(4957) %% Neighbor deleted on port GigabitEthernet2: Chassis ID xx:xx:xx:xx:xx:xx, Port ID 0/12 LLDP-6-NEIGHBOR_DEL proto_lldp.c(4957) %% Neighbor deleted on port GigabitEthernet2: Chassis ID 00:00:00:00:00:00, Port ID xx:xx:xx:xx:xx:xx LLDP-6-NEIGHBOR_DEL proto_lldp.c(4957) %% Neighbor deleted on port GigabitEthernet2: Chassis ID xx:xx:xx:xx:xx:xx, Port ID 0/44 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet2 moving from Forwarding to Disabled TRAPMGR-5-PORT_LINK_DOWN ksi_snmp.c(230) %% Interface GigabitEthernet2 link down LLDP-6-NEIGHBOR_DISCOVER proto_lldp.c(5156) %% New neighbor on port GigabitEthernet2: Chassis ID xx:xx:xx:xx:xx:xx, Port ID 0/12 LLDP-6-NEIGHBOR_DISCOVER proto_lldp.c(5156) %% New neighbor on port GigabitEthernet2: Chassis ID 00:00:00:00:00:00, Port ID xx:xx:xx:xx:xx:xx LLDP-6-NEIGHBOR_DISCOVER proto_lldp.c(5156) %% New neighbor on port GigabitEthernet2: Chassis ID xx:xx:xx:xx:xx:xx, Port ID 0/44 TRAPMGR-5-STP_TC ksi_snmp.c(486) %% Bridge topology change. STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet2 moving from Blocking to Forwarding <182>1 2022-04-28T16:43:41.310+1:00Z 192.xxx.xxx.199-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet2 moving from Disabled to Blocking <181>1 2022-04-28T16:43:41.300+1:00Z 192.xxx.xxx.199-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface GigabitEthernet2 link up
Disable Spanning Tree and everything works fine.
I am a little uncomfortable disabling spanning tree and the two VLANs are completely isolated.
Unfortunately your xx-ing of the neighbour MAC (keep at least the vendor OID visible) and the complete RFC1918 Private 192.x.x.x addresses almost the complete world is using does render the log useless.
Spanning Tree STP and RSRP does span the complete phyical network. If STP active does bring down a link there must be a reason - a reason in place even with STP/RSTP disabled, too. So strongly doubt everything is flawless ....
