The vlan database mode is an older mode of configuring VLANs which is being deprecated on all recent Catalyst platforms and replaced with the VLAN configuration in the global configuration mode. For backward compatibility purposes, it is still being kept in some older IOS versions and possibly on IOSes running on routers. However, it is now recommended to avoid using the vlan database and instead, configure all VLAN settings in the global configuration mode along with all other settings.
Functionally, the vlan database is a subset of capabilities that can be configured for VLANs in the global config mode (for example, the vlan database mode does not recognize or support private VLANs to my best knowledge).
There are two mode, VLAN databse mode and VLAN confguration mode.When you configure VLANs in VLAN database mode, the VLAN configuration is saved in the vlan.dat file, not the running-config or startup-config files (in VLAN configuration mode with vtp transparent, vlan will save in running or startup configuration). Vlan databse mode and VLAN Database mode supports configuration of Vlan normal range(from 1 to 1001), but not the extended range (from 1006 to 4094) (you can configure extended range in VLAN configuration mode)
Re: difference between vlan<vid> and vlan database?
There are two mode, VLAN databse mode and VLAN confguration mode.When you configure VLANs in VLAN database mode, the VLAN configuration is saved in the vlan.dat file, not the running-config or startup-config files (in VLAN configuration mode with vtp transparent, vlan will save in running or startup configuration).
I respectfully disagree here. The situation is more complex.
First of all, the mode of VLAN configuration - either the vlan database or the global configuration mode - has absolutely no effect whatsoever on the operation of these VLANs or on the way of storing them. I am stressing it again: regardless of how you configure a VLAN, it will operate in the same way and it will always be stored in the same storage.
Second, because of historical reasons, the VLANs are divided into two groups on Cisco devices: normal range VLANs (1-1005) and extended range VLANs (1006-4094). Normal range VLANs are always stored in the vlan.dat file, and in addition, if the switch operates in VTP Transparent mode, they also appear in the running-config. They can be created both in the vlan database and in global config mode.
Extended range VLANs are always stored in the running-configuration, and if VTPv3 is used, also in the vlan.dat file (not with older VTP versions). They can be created only in the global configuration mode, not in the vlan database mode.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.