asked on

New vlan, new lookup zone in AD, what am I missing ???

I have a simple network, all flat, using default vlan 1 on my LAN. I do have 2 switches that have a different vlan to separate my camera traffic.

I am implementing 2 more switches, stacked, (vlan 90) that I need them to be able to access the rest of my current network, vlan 1.
I'm going to create the new vlan on the core switch and add an IP address to it. I know that all my uplink ports need to also be trunk ports,
so it can pass all the vlans, I'm guessing, all I need to do is add the new vlan on every current switch in my network and that's all I have to do from a
networking standpoint. I also need to add the IP helper command on my core switch, so I can pass the DHCP info to my DCs. Am I missing anything else
I need to do?

In regards to my AD, I'm running windows server 2012R2 for all 3 of my domains. I'm running DHCP and DNS.
So I'm assuming I need to create a new lookup zone for this new vlan and IP range.
Besides that, am I missing anything? What else would I need to do?

Is there anything else I need to do to make this happen?

SOLUTION

Shaun Vermaak

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Dan

ASKER

Forgot about that, so under sites -> subnets. I have just added it there.

Anything else?

Cliff Galiher

The purpose of VLANs is to separate broadcast domains (layer 2 OSI) so just using trunk ports seems to be breaking down the purpose of using VLANs in the first place. You'd *USUALLY* route between VLANs with a router or a layer 3 switch. Your existing topology seems a bit off kilter. At best it breaks the VLAN barrier and more likely it won't work as expected.

Dan

ASKER

Cliff,

I’m open for suggestions of what is the best thing to do.

The only reason I’m going down this route is because I’m out of IPs in my /22, and I was thinking by creating another subnet, this would give me more IPs. The biggest catch is, the equipment, pc’s and other gear will need to communicate with the rest of my network.

would it help if I provide a complete detailed diagram of my current network?

ASKER CERTIFIED SOLUTION

Cliff Galiher

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Dan

ASKER

Cliff,

so what do you recommend I do?

My core switches, 2 of them, stacked, using etherchannel from all my stacks. My core switches are 3850-24xs-s, so yes, they support layer 3.

I'm using my core switch as my gateway, so all my servers, the default gateway is my core switch, and that sends all the traffic for the internet to my firewall, which then goes out to the internet.

So with my /22 currently and needing to add another /24, what would you recommend?

I just discovered yesterday that the new /24 is a 172.16.x.x network, and I won't be managing it, our vendor will, so I'm not as concerned anymore, as my responsibility will end on my core switch. I will most likely need to create the vlan they will use on my switch, and the port type a trunk port, also adding the IP helper command, and I will still have to setup my DHCP and DNS, but I won't be managing those extreme switches that they are using.

Dan

ASKER

Thanks guys for your help!