10-16-2023 02:58 PM
Hello Expert,
I want to enable DHCP for multiple VLANs
This Lab aims to create multiple SVI-enabled, DHCP and add more switches to the core switch, and create HSRP.
What is the best practice for creating multiple VLANs It should be on the access layer or distribution layer.
Ankit
Solved! Go to Solution.
10-16-2023 09:23 PM - edited 10-16-2023 10:40 PM
yes, you need static route or a routing protocol as mentioned by GP; Also Core switch needs ip routing turn on; ip routing command; this switch model is L2 by default in PT and L3 after ip routing is on; Command ip default-gateway is for L2 switches but not useful for L3 ones.
also, l2 switches need spanning-tree portfast default command to load faster and better yet also change original legacy STP mode to Rapid spanning tree one
Edit: just noticed you do not have same subnet between switches; they have to be on the same network to communicate; I guess 10.10.50.x subnet
Regards, ML
**Please Rate All Helpful Responses **
10-16-2023 03:31 PM
Vlans should be created on both access and distribution switches. Since u have core switch, enable ip routing on it. Technically, at current topology, your core switch can be removed and your router is core.
I would start with static IPs on PCs in multiple vlans, then , if all is OK, set up dhcp server for those vlans, dhcp fir vlans on router may not work in PT.
One subnet range per 1 vlan. L3 switch SVI as default gateway for PCs.
Regards, ML
**Please Rate All Helpful Responses **
10-16-2023 03:48 PM
"What is the best practice for creating multiple VLANs It should be on the access layer or distribution layer."
That's a it depends, answer.
In general, modern networks lean toward using L3 wherever possible rather that L2. One goal of which is to not extend a VLAN across multiple (logical) L2 edge devices.
As you mention HSRP, many networks provide gateway redundancy via using hardware for redundancy. For example, the distro device might be a chassis with redundant everything, except the chassis itself, or dual chassis in a VSS or vPC setup, or perhaps a switch stack.
10-16-2023 07:06 PM
Hello
Thank you for your quick response.
I have enabled SVI and DHCP relay now how can I reach out to the 192.168.1.0 network..?
10-16-2023 08:24 PM
U can attach your PT file here in a zip format a must be
Regards, ML
**Please Rate All Helpful Responses **
10-16-2023 08:28 PM
See the onedrive to download the file
10-16-2023 09:23 PM - edited 10-16-2023 10:40 PM
yes, you need static route or a routing protocol as mentioned by GP; Also Core switch needs ip routing turn on; ip routing command; this switch model is L2 by default in PT and L3 after ip routing is on; Command ip default-gateway is for L2 switches but not useful for L3 ones.
also, l2 switches need spanning-tree portfast default command to load faster and better yet also change original legacy STP mode to Rapid spanning tree one
Edit: just noticed you do not have same subnet between switches; they have to be on the same network to communicate; I guess 10.10.50.x subnet
Regards, ML
**Please Rate All Helpful Responses **
10-16-2023 08:35 PM
Between Distribution switch(fa0/4) and Core switch (Fa0/1) as routed ports and configure a routing protocol (static/ospf/eigrp)....
Now...you have the reachbility.....hope that solve the problem....
Best regards
******* If This Helps, Please Rate *******
10-17-2023 09:27 AM
I was able to set up OSPF on the Distribution layer SW and Core and Router. It seems to be working now. My client's PC can reach out to router . @Martin L @Gopinath_Pigili @Joseph W. Doherty thank you for your support. I will learn more from you guys.
Self-learning is an opportunity to strengthen problem-solving skills
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide