02-02-2023 01:16 PM
Hi Vlan 1400 and vlan 240 are created in the c9200. but vlan 240 cannot be seen in show run. Is this something wrong or .. Thanks
02-02-2023 01:25 PM
Hi,
You should be able to see both vlans. Can you post the output of "sh run" and "sh vlan"?
HTH
02-02-2023 01:26 PM - edited 02-02-2023 01:28 PM
#more vlan.dat <<- check the VLAN is in database, remember the vlan not save with startup but in vlan.dat
if not appear please share
show vtp status
02-02-2023 01:32 PM
@Leftz wrote:
Hi Vlan 1400 and vlan 240 are created in the c9200.
How were the VLANs created, interface-level VLANs or in the VLAN database?
02-02-2023 01:57 PM
Thanks for your reply! show run can see vlan 1400 but cannot see vlan 240. however, both vlan can be seen via show vlan.
I guess vlan with smaller number is located in another site.
02-02-2023 02:04 PM
show run can see vlan 1400,
are you see
vlan 1400
or
interface vlan 1400
there is different
02-02-2023 02:33 PM - edited 02-02-2023 02:35 PM
I guess vlan with smaller number is located in another site.
That should not be the case. Both vlans should show in the "sh run" output.
Try:
sh run | inc 240
if not try to give it a description and try the command again
config t
vlan 240
description user vlan
exit
and run the sh run command again
HTH
02-02-2023 02:35 PM
@Leftz wrote:
Thanks for your reply! show run can see vlan 1400 but cannot see vlan 240.
Ok, this is how I see it.
Person A was the first to configure the switch. He created VLAN 1400 in the VLAN database and then created the VLAN interface and then added the VLAN 1400 into the allowed VLAN.
Person B was next and allowed VLAN 240 in the allowed VLAN and skipping the rest of the process.
Is this how it went?
02-02-2023 03:02 PM
after several test, i can see vlan # which is < 1001 do not show up in output of show run unless it is configured as layer 3. right?
02-02-2023 04:04 PM - edited 02-02-2023 04:13 PM
I think you confuse here,
VLAN is
L2 which we can see via show vlan
L3 which we can see via show run, show interface, show ip route
why there is different because as I mention before the VLAN (L2) is save in VLAN data not in startup.
02-03-2023 06:20 AM
Have you tested at c9300? it might be different with test in simulator.
02-03-2023 02:23 PM
Manage vlan.dat file on Catalyst Switches Running Cisco IOS - Cisco
If both the VLAN database and the configuration file show the VTP mode as transparent and the VTP domain names match, the VLAN database is ignored. The VTP and VLAN configurations in the startup configuration file are used. The VLAN database revision number remains unchanged in the VLAN database.
If the startup VTP mode is server mode, or the startup VTP mode or domain names do not match the VLAN database, VTP mode and VLAN configuration for the first 1005 VLANs are selected by VLAN database information, such as the vlan.dat file. VLANs greater than 1005 are configured from the switch configuration file.
I mention first that VTP status affect VLAN.
anyway check link above and check statement that startup VTP mode or domain not match with VLAN database them you can see some in VLAN database and some (large than 1005) see some in startup.
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