VLAN creation

geezer

Hi

Just a question in regards to creating VLANs. As I understand it you use the command #vlan database CR vlan <number> CR name <name> ?

Correct me if wrong as I am using the Todd Lammle book who states that you create vlans from global configuration mode which is completely wrong.

TIA

Netstudent

there are two ways of doing it. The way you are describing is being phased out. IN global config mode you can do (config)#vlan 10 <cr> then name Red

With the vlan database method you can use the "vlan 10 name red" command, whereas with global config mode you have to do vlan 10 enter and then the name

For the test just know both ways.

geezer

I see that the book does it the 'new' way but on my routersim the 1900 and 2950 don't accept this way?

keenon

the use of vlan database is being phase out so know the global config

geezer

Ok, thanks for that - so just remember this way, simpler anyway.

borumas

I found that sometimes if you set a vlan up in global config mode that it will not become active, only after going into vlan database mode and doing the command "vlan 10 state active" will the vlan actually work and show up on a show vlan command (vlan 10 just being an example vlan).

geezer

The problem I experienced was that the command 'vlan 5' was rejected by the IOS on the switch.

borumas

geezer wrote:

The problem I experienced was that the command 'vlan 5' was rejected by the IOS on the switch.

Did you do "int vlan 5" at the global command prompt? I imagine it would be rejected if you just put "vlan 5". The problem I had was that if I did a "int vlan 5" command and did not use "switchport access vlan 5" on one of the interfaces then it would not always make vlan 5 active, only if I went into vlan database mode and used "vlan 5 state active" then exited would it make the vlan 5 active.

PS Just notices your from Ireland, got some extended family living in Dublin myself.

geezer

borumas wrote:

Did you do "int vlan 5" at the global command prompt? I imagine it would be rejected if you just put "vlan 5". The problem I had was that if I did a "int vlan 5" command and did not use "switchport access vlan 5" on one of the interfaces then it would not always make vlan 5 active, only if I went into vlan database mode and used "vlan 5 state active" then exited would it make the vlan 5 active.

PS Just notices your from Ireland, got some extended family living in Dublin myself.

The Sybex book just stated that you type vlan <#> at global configuration and press CR. Then you would have a vlan global config prompt where you type the vlan name and press CR. Bit confusing as it is used extensively in this book so you would assume it is correct but in practice didn't work?

Dublin not too far from here.

mwgood

I'm not sure exactly what the dividing line is - but some switches support only the "old" way - which is the vlan database method, and some support both the "old" and the "new" way - which is the global configuration method.

Both are "correct." But the new way will not work on some switches. On the switches that accept the newer method, they will typically give you a warning if you use the vlan database method - telling you that method is being deprecated (phased out).

Bottom line - use whatever method is available on the switch - but get used to the global config method since that's direction Cisco is moving.

borumas

geezer wrote:

borumas wrote:

Did you do "int vlan 5" at the global command prompt? I imagine it would be rejected if you just put "vlan 5". The problem I had was that if I did a "int vlan 5" command and did not use "switchport access vlan 5" on one of the interfaces then it would not always make vlan 5 active, only if I went into vlan database mode and used "vlan 5 state active" then exited would it make the vlan 5 active.

PS Just notices your from Ireland, got some extended family living in Dublin myself.

The Sybex book just stated that you type vlan <#> at global configuration and press CR. Then you would have a vlan global config prompt where you type the vlan name and press CR. Bit confusing as it is used extensively in this book so you would assume it is correct but in practice didn't work?

Dublin not too far from here.

Ok, just tried this on a 3550 inline powered switch and here is the results:

3524poe-1-2#config t
Enter configuration commands, one per line. End with CNTL/Z.
3524poe-1-2(config)#vlan 37
3524poe-1-2(config-vlan)#?
VLAN configuration commands:
are---- Maximum number of All Route Explorer hops for this VLAN (or zero if none specified)
backupcrf---- Backup CRF mode of the VLAN
bridge---- Bridging characteristics of the VLAN
exit---- Apply changes, bump revision number, and exit mode
media---- Media type of the VLAN
mtu---- VLAN Maximum Transmission Unit
name---- Ascii name of the VLAN
no---- Negate a command or set its defaults
parent---- ID number of the Parent VLAN of FDDI or Token Ring type VLANs
private-vlan---- Configure a private VLAN
remote-span---- Configure as Remote SPAN VLAN
ring---- Ring number of FDDI or Token Ring type VLANs
said---- IEEE 802.10 SAID
shutdown---- Shutdown VLAN switching
state---- Operational state of the VLAN
ste---- Maximum number of Spanning Tree Explorer hops for this VLAN (or zero if none specified)
stp---- Spanning tree characteristics of the VLAN
tb-vlan1---- ID number of the first translational VLAN for this VLAN (or zero if none)
tb-vlan2---- ID number of the second translational VLAN for this VLAN (or zero if none)

3524poe-1-2(config-vlan)#end
3524poe-1-2#config t
Enter configuration commands, one per line. End with CNTL/Z.
3524poe-1-2(config)#int vlan 37
3524poe-1-2(config-if)#?
Interface configuration commands:
arp---- Set arp type (arpa, probe, snap) or timeout
bandwidth---- Set bandwidth informational parameter
carrier-delay---- Specify delay for interface transitions
cdp---- CDP interface subcommands
custom-queue-list---- Assign a custom queue list to an interface
default---- Set a command to its defaults
delay---- Specify interface throughput delay
description---- Interface specific description
exit---- Exit from interface configuration mode
fair-queue---- Enable Fair Queuing on an Interface
help---- Description of the interactive help system
hold-queue---- Set hold queue depth
ip---- Interface Internet Protocol config commands
l2protocol-tunnel---- Tunnel Layer2 protocols
load-interval---- Specify interval for load calculation for an interface
logging---- Configure logging for interface
loopback---- Configure internal loopback on an interface
macro---- Command macro
max-reserved-bandwidth---- Maximum Reservable Bandwidth on an Interface
no---- Negate a command or set its defaults
ntp---- Configure NTP
priority-group---- Assign a priority group to an interface
random-detect---- Enable Weighted Random Early Detection (WRED) on an Interface
service-policy---- Configure QoS Service Policy
shutdown---- Shutdown the selected interface
snmp---- Modify SNMP interface parameters
spanning-tree---- Spanning Tree Subsystem
standby---- HSRP interface configuration commands
tcam---- tcam keyword
timeout---- Define timeout values for this interface

3524poe-1-2(config-if)#

It seems using the "vlan 37" at the global config prompt is nearly the same as using the "vlan database" command as far as the options goes, that's nice to know. I had to use ---- to separate the commands from the descriptions as when I submitted this it just bunches it up together.