network and local switch vlans 3

[just1moretime]

When setting up a ethernet switch and creating
vlans on it,do these vlan number have to match the
in use vlan numbers of the existing network? Or are
they just a local identifier to this switch?
IE-data network is using 2 vlans,15 for voip and
12 for general data. Do I need to make my voip vlan to
15 and my general data vlan to 12 on this new ethernet switch? Thank you.

 

[burtsbees]

Yes---the vlans must be the same on the new switch---it is not a local identifier only to the local switch---it is propagated across all switches.

Burt

 

[jimbopalmer]

Tagged packets include the VLAN number, if all packets were untagged, the switches would not notice the VLAN numbers did not match.

On the other hand, you would be hated by generations of network administrators who had to live with your numbering a sensible network topology with incomprehensible VLAN IDs, so be prepared to change YOUR name.

What possible advantage to using different IDs are you hoping for?

I tried to remain child-like, all I acheived was childish.

 

[dearingkr]

Actually, the VLAN names mean nothing, strictly local.
The ID #s are all the network cares about.


MCSE CCNA CCDA

 

[VinceWhirlwind]

I think your best bet would be to have a look at the config on an existing switch.
Pay particular attention to the config of that switch's uplink port, and the config on the remote interface it is connected to.
You will need an uplink port and a remote interface in the same way.