VLAN's not advertised in spite of VTP-server-client config.
We placed 2 new 3550-switches in our existing network. Configured them both as vtp-clients. But no newly made or already-existing Vlan's are available after connecting to the router (which is configured as VTP-server, 3550-12G).
VTP-Revisions are checked and ok, all switches have same IOS.
In test-envirement both switches did pick-up all VLan-information from a VTP-server and so do all the other switches in our network.
We already tried a complete reset to factory-defaults, erasing all vlan-information, reconfigure and reload.
nothing works so far, except putting in the neccessary vlans manually in vtp-server-mode per switch.
Re: VLAN's not advertised in spite of VTP-server-client config.
You mentioned the test network. Did you get rid of all VLAN database information before you placed the switch in to production? Erasing the startup config is not enough to get back to factory defaults. Look in flash (show flash:). Look for a file called 'vlan.dat'. This is where your VTP information is stored. Delete this file to get to factory default. Then reconfigure the VTP information. My guess is that you have the incorrect VTP domain or the wrong VTP password. You can look at the VTP information if you like - 'sh vtp status'. You can also do 'more' on the file in flash.
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.