I do similar but for the name I add the VLAN number with a dash, VOIP-20 for 10.61.20.0/24 and VOIP-21 - 10.61.21.0/24 .. Also with cisco the INCLUDE case matters so all upper or lower but never both! I also dedicate a 10.x.0.0/16 for every office location (Good IP schema = better routing). For example all networks in a company office in Houston would be 10.61.x.x, 2ND_OCTET = SITE ID.
Great Jeremy! I just completed the CBT Nuggets CCNA course and it was great! Jeremy, Keith and Chuck were great instructors and really can get the information through to you.
What do you think about using round numbers when Vlans? E.g. 2/4/8 Clients, 4/8/16 VoIP etc. In that case, you can easily extend your subnetting scheme in this case. You can't easily summarize 10-13, but 8-11 can be done nicely
Thanks for the cool useful videos, however regarding network growth, for example VOIP vlan 20 we don't need to creat new vlan 21 to expand it! we can just have a bigger subnet for example 192.168.20.0/21 ... vlan 20 ... VOIP 192.168.30.0/23 ... vlan 30 ... Guest way better than 192.168.20.0/24 ... vlan 20 .. VOIP1 192.168.21.0/24 ... vlan 21 .. VOIP2 192.168.22.0/24 ... vlan 22 .. VOIP3 so we need to creat bigger subnet but same vlan. Creating multiple vlans and multiple subnets for the same purpose ist never a good practice, the traffic now will always be routed, and later if you have firewall you need to add more subnets in the ACL and now we have extra management, maybe for small environment/network it doesn't matter and looks cool too but believe that's never a good design for enterprise. thanks one more time for your brilliant video. big fan. cheers
Increasing subnet size is only practical to a certain point. At some point you will reach a number of mac addresses that exceeds the capacity of the CAM table of the switch, which will cause an issue with the ability of the device to recognize individual hosts. I used to do router/switch support for an IP device OEM. I worked with a customer who had a flat single vlan for most of their network traffic. The address table was capable of holding 16,000 mac addresses, which the customer had reached, and then some. Every switch on the network, because the vlan was flat, had the mac addresses for EVERY device in the network, which meant every switch had an overflowing address table. As a best practice you might want to keep the CAM table no more than 50% utilized. So, that would be 8,000 devices learned, in my example. If you have a /21 subnet, you're already at 2046 devices that can be learned on that vlan per switch, which would effectively use 25% of the table capacity in my example. That might be the right choice, in some cases, but over time, such large vlans can lead to memory performance issues. Another consideration is broadcast storms. When your vlan is a potential 2046 users, every user, and network device, in the vlan can be affected in the event of a broadcast storm. Further, it's much easier to secure a 254 user vlan versus a 2046 user vlan. So, there are many practical reasons to keep vlans and subnets from getting too large.
Jeremy, This seems to cover VLANS using IPv4. Do you have a video that covers creating VLANS for IPv6? If not, there's your next video idea. (Well, add it to the huge list your probably already have.)
This is superb. One thing: don't forget about the black hole VLAN. That's the one where you put all unused interfaces for security reasons.
I do similar but for the name I add the VLAN number with a dash, VOIP-20 for 10.61.20.0/24 and VOIP-21 - 10.61.21.0/24 .. Also with cisco the INCLUDE case matters so all upper or lower but never both! I also dedicate a 10.x.0.0/16 for every office location (Good IP schema = better routing). For example all networks in a company office in Houston would be 10.61.x.x, 2ND_OCTET = SITE ID.
Great Jeremy! I just completed the CBT Nuggets CCNA course and it was great! Jeremy, Keith and Chuck were great instructors and really can get the information through to you.
Hi; Are you doing the new CCNP ? If so please let me know.
You’re a great teacher Jeremy!
What do you think about using round numbers when Vlans?
E.g. 2/4/8 Clients, 4/8/16 VoIP etc.
In that case, you can easily extend your subnetting scheme in this case.
You can't easily summarize 10-13, but 8-11 can be done nicely
Man.. U still great .. just like before .. keep going u God of Cisco
Valuable and useful! Thanks Jeremy!
Thanks again! Love this series ❤️
Hello Jeremy
I have question on which layer BGP works..
Could you please make video on it..
I will be thankful.. expecting your acknowledgement
Love you Jeremy 😊
Awesome!!
Can you make a video about loggserver, what is the best way to secure and check who is logging to the switch?
Did this apply for the networks that you did not do?
Wow thank you sir for this am really grateful. You are Great sir
Hi Jeremy. I need some clarity on "managed VLAN" and "internal" VLAN. What's the difference.
Thanks for the cool useful videos, however regarding network growth, for example VOIP vlan 20 we don't need to creat new vlan 21 to expand it! we can just have a bigger subnet for example
192.168.20.0/21 ... vlan 20 ... VOIP
192.168.30.0/23 ... vlan 30 ... Guest
way better than
192.168.20.0/24 ... vlan 20 .. VOIP1
192.168.21.0/24 ... vlan 21 .. VOIP2
192.168.22.0/24 ... vlan 22 .. VOIP3
so we need to creat bigger subnet but same vlan. Creating multiple vlans and multiple subnets for the same purpose ist never a good practice, the traffic now will always be routed, and later if you have firewall you need to add more subnets in the ACL and now we have extra management, maybe for small environment/network it doesn't matter and looks cool too but believe that's never a good design for enterprise.
thanks one more time for your brilliant video. big fan. cheers
Increasing subnet size is only practical to a certain point. At some point you will reach a number of mac addresses that exceeds the capacity of the CAM table of the switch, which will cause an issue with the ability of the device to recognize individual hosts. I used to do router/switch support for an IP device OEM. I worked with a customer who had a flat single vlan for most of their network traffic. The address table was capable of holding 16,000 mac addresses, which the customer had reached, and then some. Every switch on the network, because the vlan was flat, had the mac addresses for EVERY device in the network, which meant every switch had an overflowing address table. As a best practice you might want to keep the CAM table no more than 50% utilized. So, that would be 8,000 devices learned, in my example. If you have a /21 subnet, you're already at 2046 devices that can be learned on that vlan per switch, which would effectively use 25% of the table capacity in my example. That might be the right choice, in some cases, but over time, such large vlans can lead to memory performance issues. Another consideration is broadcast storms. When your vlan is a potential 2046 users, every user, and network device, in the vlan can be affected in the event of a broadcast storm. Further, it's much easier to secure a 254 user vlan versus a 2046 user vlan. So, there are many practical reasons to keep vlans and subnets from getting too large.
Jeremy, This seems to cover VLANS using IPv4. Do you have a video that covers creating VLANS for IPv6? If not, there's your next video idea. (Well, add it to the huge list your probably already have.)
Thank you, This was a really good video for noobs like me!
You lost me at "nugget." I couldn't watch anymore after hearing it for the second time.