Weird VTP Behavior

flurrballflurrball Posts: 50Member ■■□□□□□□□□
Hey, I was just reading Odom's ICND2, and it said instead of typing the following to create a VLAN:
Sw(config)# vlan 40
you could type the following:
Sw(config)# int fa 0/16
Sw(config-if)#switchport access vlan 40
and VLAN 40 would be created if it didn't already exist. So naturally, I jumped into Packet Tracer to try it. While fooling around, I did it on a VTP client switch, which I thought couldn't create VLANs, but for some reason it created it. I was wondering if this was a Packet Tracer bug, or if real switches do this too.

Comments

  • remyforbes777remyforbes777 Posts: 499Member
    You cannot create a vlan on a switch configured as a client.
  • marlon23marlon23 Posts: 164Member
    On a 3560 for example, it will let you asign the port to non-existing vlan but it doesnt create one. It can depends on platform, some switches will complain you that you are in a clinet mode when doing this.
    LAB: 7609-S, 7606-S, 10008, 2x 7301, 7204, 7201 + bunch of ISRs & CAT switches
  • flurrballflurrball Posts: 50Member ■■□□□□□□□□
    Thanks, I guess its just a Packet Tracer error.
Sign In or Register to comment.