Creating vlans

[VeeTeeEye]

I have a Cisco 3850 that needs to talk to multiple Cisco C3650s.

If I were to build 4 VLANs as below, how would I be able to get it all going on both the 3850 and 3650s? Trunking, tagging, access, modes, all that is just wearing me out.

VLAN130 - 192.168.130.1 255.255.255.0

VLAN131 - 192.168.131.1 255.255.255.0

VLAN132 - 192.168.132.1 255.255.255.0

VLAN133 - 192.168.133.1 255.255.255.0

All of the devices are security cameras and do not have a gateway programmed into them.

Thanks for all the help,

[paul driver]

Hello

You would make the 3850 the root switch running the layer3 interfaces for the vlans (svi’s)

Then create their Layer2  equivalent which would populate the vtp database of the switch

The other switches would be inter contended to this root switch with trunks which would by default allow all vlans to traverse these trunks.

laslty with a feature called VTP applied to all the switches this will allow the root switch to advertise those vlans it has i its vtp database to all the other switch’s 

example

3850

interface vlan -131

ip address 192.168.131 254 255.255.255.0

exit

vlan131

exit

vtp mode server 

vtp version 2

 vtp domain TST

interface xx

description trunk to 3650

swichport 

swichport mode trunk

On the other switches you would create the trunk and enable VTP but in client mode which would then allow the vlans created on the root switch populate the 3650switches  to database

[Seb Rupik]

Hi there,

@paul driver suggestion to use VTP is a great one and will simplify your initial deployment, however the protocol can easily be subverted to disastrous effect. A malicious (or incorrectly configured) device advertising a VTP database with a higher revision number will take precedent and if that VTP VLAN database is empty, will cause an outage. For this reason consider running VTP version 3 and setting a password.

cheers,

Seb.