07-14-2022 02:43 PM
Hallo,
This is a rather basic question but I will ask it anyway
Thanks.
Solved! Go to Solution.
07-14-2022
03:16 PM
- last edited on
07-15-2022
11:26 AM
by
Translator
Yes, You Must have L2 VLANs in database before the SVIs? Or SVI vlan x will stay down until you add vlan x. Also, there must be an active port in vlan x for SVI x to be up up. you can change this default behavior with
no switchport autostate
or
switchport autostate exclude
command. This port can be access port or a trunk but for sure vlan x must exist in vlan database (stored in flash of a device).
Regards, ML
**Please Rate All Helpful Responses **
07-14-2022
02:51 PM
- last edited on
07-15-2022
11:22 AM
by
Translator
Running-config
doesn't cover vlan database, so without
interface vlan x
ip add x.x.x.x/prefix-length
command it will not work.
07-14-2022 02:54 PM - edited 07-14-2022 02:55 PM
for the SW you can start with L3 SVI or L2 VLAN, AND for router I think it same you can config the SVI then this SVI is down until you add L2 VLAN to router which turn UP.
07-14-2022
03:16 PM
- last edited on
07-15-2022
11:26 AM
by
Translator
Yes, You Must have L2 VLANs in database before the SVIs? Or SVI vlan x will stay down until you add vlan x. Also, there must be an active port in vlan x for SVI x to be up up. you can change this default behavior with
no switchport autostate
or
switchport autostate exclude
command. This port can be access port or a trunk but for sure vlan x must exist in vlan database (stored in flash of a device).
Regards, ML
**Please Rate All Helpful Responses **
07-14-2022 11:33 PM
Thank you all for the responses. I now understand where the problem was
07-15-2022 12:36 AM
Hello
L3 switch in particular , you need to create the L2 vlan as its not created as/when you create its L3 svi equivalent
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