Boson NetSim...switching woes

Bob_the_Goon

Good evening all,

I'm currently trying to setup a couple of VLANs using Boson NetSim.

The switch is a 2950 using IOS 12.1. The command I believe I should be using is the following:

Switch1#config t
Switch1(Config)#vlan 2

For some reason the sim doesn't like this. In fact the only way I can create a VLAN is by the following means:

Switch1#vlan database

Now I'm sure this shouldn't be the case for a 2950 with IOS 12.1. Are my suspicions correct?

Many thanks,

Bob the Goon

Slowhand

It's very possible that the simulator software is only set up to take the command that way. According to Cisco's site you can enter VLAN configuration mode with either command. In this case, though, you're stuck with what the simulator wants.

rjbarlow

Hi, I have just tried in a 2950 switch in my Boson netsim and it takes well that command, what version You are using of Boson netsim? I'm using v.6.00.

Netstudent

rjbarlow wrote:

Hi, I have just tried in a 2950 switch in my Boson netsim and it takes well that command, what version You are using of Boson netsim? I'm using v.6.00.

What IOS version are you simulating? Maybe you two are simulating different IOS versions.

rjbarlow

Netstudent wrote:

What IOS version are you simulating? Maybe you two are simulating different IOS versions.

Aahm, Version 12.1.

Paul Boz

Anything prior to the full release of version 6 (including 5.xx and the 6.xx betas) don't take VLAN commands like that. You have to set them up the old way.

Bob_the_Goon

Ah that will explain it then.

I'm using Netsim 6.3 Beta and the IOS was 12.1.

Hmmm, looks like I'm going to need to splash some cash on some real kit!! Watch out ebay, Bob the Goon is on his way...

tech-airman

Bob_the_Goon wrote:

Good evening all,

I'm currently trying to setup a couple of VLANs using Boson NetSim.

The switch is a 2950 using IOS 12.1. The command I believe I should be using is the following:

Switch1#config t
Switch1(Config)#vlan 2

For some reason the sim doesn't like this. In fact the only way I can create a VLAN is by the following means:

Switch1#vlan database

Now I'm sure this shouldn't be the case for a 2950 with IOS 12.1. Are my suspicions correct?

Many thanks,

Bob the Goon

Bob the Goon,

How about trying...

Switch1(Confi9g)#int vlan 2

Instead of ...

Switch1(Config)#vlan 2

?

mikej412

tech-airman wrote:

How about trying...

I think the post is about creating the VLANs, the newer "config" method vs the older "vlan database" method.... not the "Administrative VLAN" for layer 2 swithes or SVIs for Layer 3 switches -- apples and oranges

Stotic

A way I like to use is by going into the actual interface and assigning it to a VLAN.

Router(config)#int f0/5
Router(config-if)#switchport mode access
Router(config-if)#switchport access vlan 105

datchcha

Yes, I was having issues with this as well, but not from a simulator stand-point, but from understanding the (2) different methods.

Q: You use the 'vlan database' command when you span vlans accross multipule switches currect? And when you use the 'vlan database' command you are actully modify the database sort of speak?

Netstudent

not necessarily. It's two different ways to do the same thing. The vlan database command is being phased out.

you can use the command YOYO(config)# vlan 10 name sales

and still put vlan10 on another switch.

VTP is used to automatically transfer VLAN information to vtp mode client switches.

dtlokee

VTP is used to automatically transfer VLAN information to vtp mode client switches.

Be careful with this one, VTP transfers the database between switches and the database with the highest revision number wins even of it came from a client switch.

Try this: take 2 switches and configure them for a trunk between them, and put them in the same VTP domain with the same VTP domain password. Create a few vlans on one of the switches and wait for them to be sent to the other switch. Disconnect the link between the two switches and add a few more vlans to one of the switches and change its mode to client. Use the "show vtp status" command to ensure the revision of the client is higher than the server, then connect them back together and see what happens.