That is what i thought... but assuming all the odd ports were assigned to VLAN1 (as they should be), would that configuration with the config:

interface FastEthernet1/0/1
   switchport access vlan 1
   switchport trunk native vlan 1

still allow both VLAN1 and VLAN2 to access each other without any interference?

That should work.

Just curious why they are all trunk ports?  Typically would see trunk ports on an access switch in a VMWare environment.

With the native VLAN 1 in there it should be fine.

James

This was a setup done by someone else... I am helping out.  I am open to redo the entire config the proper way... I am just not sure what the proper way should be

So if the setup should be different than it is, please recommend what each port should look like.

Thanks for the help!

If it is not a VM environment then the config example by Jon below is right (his posts are all very good).

But, if it is a VM environment where you have VM servers at the other end of these ports, then consider keeping the trunking as putting a port into a trunk will usually take it offline for a second.

If it is basic config with just some workstations or non-VM servers, then make them all access ports:

enable

config t

switch(config)#int range g1/0/1 - 48

switch(config-int)# switchport

switch(config-int)# switchport mode access

switch(config-int)# switchport access vlan 1

switch(config-int)# ctrl-z

switch# write

You will have to do the "NO" command of the trunk commands on each port to remove the old config.

Good luck.

James

There may be a case where they need a trunk to work...  There is a 24 port switch physically seperated from this switch only connected by a single pair of fiber that needs to have both VLANs on it.  In that case, do we need to keep trunking on (or just on for that port)?

Thanks again.

Yes, keep the trunking up on that port.  Any time you want multiple VLANs to leave a switch you must either trunk them or have them layer 3 routed.  Keep the trunking in place.

James

Sean

Can you post "sh ip route"  from the switch.

Also your switchports should be configured as follows -

For vlan 1

========

int fa1/0/1

switchport mode access

switchport access vlan 1

For vlan 2

========

int fa1/0/2

switchport mode access

switchport access vlan 2

A PC in vlan 1 should have an IP from sunbet 10.1.0.0/16 with a default-gateway of 10.1.1.1

A PC in vlan 2 should have an IP from subnet 10.2.0.0/16 with a default-gateway of 10.2.1.1

Jon

I cannot get the sh ip route at the moment (maybe later tonight), but will try your suggestions and post back asap. 

This switch will not have a default route to another hop (it will not be connected to anything else as it is a closed network).

Last time I left it, computers in VLAN 2 could communicate fine with all other nodes in VLAN2 and likewise with VLAN1 .... a computer in VLAN2 could ping VLAN1's gateway 10.1.1.1..... and computers in VLAN1 could ping VLAN2's gateway 10.2.1.1.... but a computer in VLAN1 could not ping a computer in VLAN2.