Adding a new VLAN for CCTV

[fiza]

So we have CCTV installed which is completely separate wiring to the network. They have said we can connect the DVRs to our network so that SLT can login and view footage when required. They have recommended using a separate VLAN to do this.

 

Our current VLANs were configured by a 3rd party. My question is : Can I get away with only putting details of the new VLAN on the edge switch that connects to the DVRs and the Core switch or do I need to put details into every edge switch? I am thinking every switch as SLT may want to login from anywhere in the School to the DVRs.

[RobD]

Just the core and the edge, when you contact an IP in a vlan so long as the route is on the core switch it should be able to route to it.

[fiza]

Just the core and the edge, when you contact an IP in a vlan so long as the route is on the core switch it should be able to route to it.

That sounds simpler. So just the edge switch that the DVRs connect to and the Core need know about the new VLAN?

[fiza]

So the DVR is on port 3 of edgeswitch1. The VLAN ID will be 50. So do I need to tag VLAN 50 onto port 3?

Which ports on the core do I need to tag with VLAN 50? Just the backbone link that connects to edgeswitch1 or more?

[LytchettNM]

Have a very good look at the configuration for the current production VLANs and make sure you understand what they are doing before you add any new VLANs to a production network.

If the DVR is already connected on port 3 of your edge switch then I can’t see why you should need to add a new VLAN?

The DVR should request a IP address from your DHCP server of the VLAN that’s configured for that port, you might not need to do anything more than you have already done!

But to address you question, on an edge switch the port facing a computer / DVR device would normally be an access port and not tagged with the port from the edge switch to the core switch / router would be a trunk port and would be tagged for the new VLAN.

On the core switch that the edge switch is connected to you will need to same VLAN added to the trunk interface and this will need to be tagged, that VLAN would then need an IP address on the core switch to act as the gateway for that VLAN and the core switch would need a route to allow traffic between the current subnets and the new subnet your creating.

I hope this helps.

Edited February 21, 2018 by Techforyou

[fiza]

We only have a couple of vlans for byod. Port 3 is on our main data vlan which includes printers. Connecting the DVR in has caused issues with the printers and the CCTV company has said the DVR should be on separate vlan.

[RobD]

So the DVR is on port 3 of edgeswitch1. The VLAN ID will be 50. So do I need to tag VLAN 50 onto port 3?

Which ports on the core do I need to tag with VLAN 50? Just the backbone link that connects to edgeswitch1 or more?

 

 

You need to:

On the Edge:

Create vlan 50

Untag vlan 50 on port 3.

tag vlan 50 on the uplink trunk to the core,

 

On the Core:

Create vlan with a interface IP

tag vlan 50 on the downlink trunk to the edge.

Add a IP helper to the DHCP (if needed) and use the vlan 50 IP as the gateway,

 

 

Think thats it from the top of my head.

 

Edit: Sorry just read the post by @Techforyou and he's already said all this.

Edited February 21, 2018 by RobD

[fiza]

You need to:

On the Edge:

Create vlan 50

Untag vlan 50 on port 3.

tag vlan 50 on the uplink trunk to the core,

 

On the Core:

Create vlan with a interface IP

tag vlan 50 on the downlink trunk to the edge.

Add a IP helper to the DHCP (if needed) and use the vlan 50 IP as the gateway,

 

 

Think thats it from the top of my head.

 

Edit: Sorry just read the post by @Techforyou and he's already said all this.

 

First chance to do this today after the adverse weather. Have followed the steps and tested using a laptop. The laptop picked up an IP in the new VLAN so looks good. Just need to test with the CCTV later in the week.

 

Thanks for the help.