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?
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.
Thanks guys for your help!
Forgot about that, so under sites -> subnets. I have just added it there.
Anything else?