09-02-2022 12:56 AM
I created vlan 10 in L2 & L3 switches if i just connect L2 switch & L3 , will same vlan on switch communicate?
09-02-2022 02:09 AM
host in vlan 10 can connect to each other not issue, but you must make sure that the trunk between L2 & L3 SW allow VLAN 10
09-02-2022 05:32 AM
In addition to what @MHM Cisco World said if you're also talking about the interface VLAN 10 on the L3 switch then it will also need to be created at L2 and the interface VLAN 10 will need to be turned on (turned off/disabled) by default. But yes they wil communicate if the VLAN is allowed on both sides of the trunk port.
-David
09-02-2022 06:47 AM
". . . the interface VLAN 10 will need to be turned on . . ."
Eh? That's not needed if you only want all VLAN 10 hosts, between the switches to intercommunicate.
However, if you wish to intercommunicate between VLANs, they you'll will need an interface for the VLAN, and since using L3 switches, this would also normally be a SVI (switch virtual interface). Further, you only need one such SVI, likely you already have one (?) on the right most L3 swtich.
09-02-2022 06:54 AM
For Me I recommend even if you have L2 SW assign IP to VLAN SVI, why ?
for troubleshooting,
Sw1-Sw2-Sw3
and each SW have VLAN X
I need to check reachability?
I assign IP for VLAN X SVI in each SW and check reachability even if all are L2.
this give me good indication that the L2 and trunk is work good.
09-02-2022 08:44 AM - edited 09-02-2022 08:47 AM
I dont think you need the SVI to test L2 reachability. You can still ping devices across multiple switches in the same VLAN without an SVI configured. Like @Joseph W. Doherty said its only needed to communicate outside the VLAN. When you ping from the PC it will see the IP address is in its own subnet so even if you added an SVI I would imagine it wouldn't even reach it since it wouldnt need the default gateway to reach the other PC you were testing with.
09-02-2022 09:09 AM - edited 09-02-2022 09:10 AM
in my example
you access to SW1 and you want to test L2 how you do that ?
that why I need SVI.
I access to SW1 and run ping using source SVI same VLAN
this traffic is not routing it bridge and here I can check the L2.
09-02-2022 09:12 AM
OK I see what you are saying. You can ping with a source address of the SVI to test each PC. My method was dont configure an SVI and ping the hosts from other hosts in the same VLAN. Both work, you just configure an extra step of the SVI. I see.
09-02-2022 09:17 AM
Yes My idea no need host connect to SW, you can use SVI in L2 SW to run ping test.
09-02-2022 09:01 AM
Ah, an interesting approach. One I haven't encountered. Normally, for checking L2 switches, I've found a switch management IP, alone, sufficient, but I can see the benefit to what you've described.
09-02-2022 06:57 AM
As @MHM Cisco World and @David Ruess have already noted, (normally) you would provide a trunk link between the L2 and L3 switch. In your diagram, it looks like you'll also want VLAN 14 on that trunk too. Configuration might be identical to, or very similar to, the trunk (?) link you have between your two L3 switches.
By default, Cisco trunks allow all VLANs to use them, but you can control what VLANs are allowed to use a trunk. (Whether to add such restrictions, for your topology, could be debated.)
BTW, although a trunk would be the usual way to span your VLANs, and generally the "better" way, it's not the only way. You could also span a VLAN between switches by interconnecting access ports using the same VLAN on the interconnected ports. (With just two VLANs, you could also use a single access port to support both of them, done using voice VLAN for one of the two VLANs; again, for this purpose, this would be "abnormal".)
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