The goal of this article is to show inter-operable trunk port configurations for Cisco and 3com SuperStack III switches. This information will specifically focus on connecting a Cisco switch to a 3com switch and establishing an 802.1q trunk.
Goal:
Workstations configured for vlan 10 and Servers configured for vlan 11 are connected to a Cisco Switch. Another switch has to be added for capacity reasons, however it is a 3com. Additional Workstations and Servers need to be connected to the new 3com switch, using the same vlan separation configured on the Cisco access switch. The workstations in vlan 10 must communicate to each other across both switches. The Servers must also communicate across switches, which are in vlan 11.
In this example:
- The Cisco switch is connected to the 3com switch using port 1 on each side.
- Create two vlans locally on each switch
- Vlan 10 (for Workstations)
- Vlan 11 (for Servers)
- Configure port 1 on each switch for 802.1q trunking
Cisco switch configuration:
vlan 10 name Workstations vlan 11 name Servers interface FastEthernet0/1 description Connected to 3com switch switchport trunk encapsulation dot1q switchport mode trunk
interface FastEthernet0/2 description Workstation switchport access vlan 10 interface FastEthernet0/3 description Server switchport access vlan 11
3com SuperStack III configuration steps:
Select menu option (bridge/vlan): create Select VLAN ID (2-4094)[3]: 10 Enter VLAN Name [VLAN 10]: Workstations
Select menu option (bridge/vlan): create Select VLAN ID (2-4094)[3]: 11 Enter VLAN Name [VLAN 11]: Servers Select menu option (bridge/vlan/modify): add Select VLAN ID (1-2,116,120)[1]: 10 Select bridge ports (AL1-AL4,unit:port...,?): 1:2 Enter tag type (untagged, tagged): untagged
Select menu option (bridge/vlan/modify): add Select VLAN ID (1-2,116,120)[1]: 11 Select bridge ports (AL1-AL4,unit:port...,?): 1:3 Enter tag type (untagged, tagged): untagged
Select menu option (bridge/vlan/modify): add Select VLAN ID (1-2,116,120)[1]: 10-11 Select bridge ports (AL1-AL4,unit:port...,?): 1:1 Enter tag type (untagged,tagged): tagged


Print This Post
July 5th, 2010 at 3:11 pm
Hi Scott very useful infomation about cisco and 3com switches, but
i need more about the commands of 3com thanks.
June 22nd, 2011 at 5:57 pm
Hi,your post was really useful. Congratulations for your experience!. Now I’m looking for a solution to an issue that happened once I made the trunking configuration, I can’t access the 3com switch telnetting the ip address of the switch any more, I don’t have idea why.
And by now I don’t have the cable needed to connect to the console of the switch.
Any suggestion
Thank you
June 23rd, 2011 at 8:57 am
I tried to telnet the switch once I connected to a port in VLAN 1 and it worked!!! Before I was trying to access the switch while connected to a port in different VLAN, maybe it’s why I couldn’t.
Thanks
September 7th, 2011 at 4:52 pm
Hi Scott, with this excelent example, is it possible with this scenario that Vlan 10 and 11 can communicate with each other? Or its necessary to add a router or L3 switch? Thanks in advance for your help.
September 8th, 2011 at 1:04 pm
Thanks for the comment! Yes, a layer3 device would be required. The example did not include the assumed gateway allowing the clients and servers to communicate.
October 20th, 2011 at 10:22 am
Hi Scott!
Looking this scenario, I try to communicate 3Com 3812 and 3Com 7700 swithes. But result is unsuccessfull.
3Com 770 switch:
vlan 1
#
vlan 2
description LAN-172-16-3-0
protocol-vlan 0 ip 172.16.3.11 255.255.255.0
#
vlan 3
description LAN-1
broadcast-suppression 50
#
vlan 4
description GUESTS
broadcast-suppression 50
#
interface Vlan-interface2
ip address 172.16.3.11 255.255.255.0
#
interface GigabitEthernet2/0/1
port link-type trunk
port trunk permit vlan 2 to 4
I can’t to communicate with 7700 through 3812 (pc – 3812 – 7700).
October 21st, 2011 at 3:49 am
Hi all!
Problem were solved, by adding default GW on a switch 3812