UNSOLVED
PowerConnect 5012 and VLAN trunking
I'm trying to use these in a service-provider environment to aggregate multiple L2 switches and trunk into an L3 router. The scenario in question is: Router <> PowerConnect 5012 <> Multiple Cisco 2950 or 3524s. My problem is that the powerconnect does not seem to have any such thing as an 802.1q trunk port. The "trunk" feature of this switch is actually for 802.3ad link aggregation which doesn't do me any good. From my tests, the only way to make the powerconnect operate in this capacity of aggregating multiple gig ports is to make sure that each VLAN on the Cisco is defined in the powerconnect and the router's port and the Cisco's port are joined to the VLAN in question. This scenario is not plausible for us because we run one VLAN per port on the Cisco devices and we would easily reach the 64 simultaneous VLAN limitation of the powerconnect. Further, with no CLI in this device, it would essentially go against all of our existing provisioning scripts. I was hoping to simply be able to put all ports on the powerconnect in trunking mode, a la 'switchport mode trunk' on a Cisco, and have it Just Work(tm). Any ideas?
cerbera_a84f2d
176 Posts
200
0
Posted January 8th, 2007 10:00
Although the 5012 doesn't have the option to configure a port as a trunk port for VLAN purposes, it does support 802.1q tagging.I'm understanding that each Cisco 2950 or 3524 is uplinked to the 5012, with each Cisco being in a spearate VLAN. You then want to take 2 or more ports from the PowerConnect and run them as an 802.3ad aggregate into the router, with all of the VLANs being presented across this aggregate for interVLAN routing?First of all clear any existing VLAN and aggregate configuration, then;Using the web interface...1) on the VLAN & CoS tagging page, using the Show VLAN, declare all of the VLANs you want, adding the port in each VLAN to the 2950s or 3524s as Untagged, and the ports forming the aggregate to the router as tagged....so you will have a group of tagged ports repeated in every VLAN which form the uplink aggregate, and one unique port in each which is the downlink to the 2950/35242)On the Default Port VLAN page, check that the PVID for each of the downlink ports ( to the 2950/3524s ) corresponds to the VLAN that that switch is in; if necessary give the port the PVID to match the VLAN that the appropriate 2950 or 3524 should be in.So a packet arriving at the 5012 fro a 2950/3524 will...if untagged be tagged with a VLAN tag cooresponding to the PVID and the VLAN that that port is in; if tagged then it will be forwarded providing the tag corresponds to the VLAN for that port.The uplink aggregate is now made up of ports tagged for all VLANs, so traffic from all VLANs will be forwarded up to the router as required, and the router will see the port as an 802.1q trunk.Its a few years since I set up a 5012, so this is from memory...so if I've got it worng then my apologies!
colo4jax
4 Posts
200
0
Posted January 6th, 2007 08:00