dustaine
asked on
Trunk link aggregation
I have a Cisco 3560 L2/L3 that will be connecting to an HP 2910al access switch.
On the 3560, I have a few VLans set up. because of the amount of data going across the switches, I want to aggregate the link between the switches. I have been looking for information on aggregating trunks and have not found much useful information. I find information on aggregating access ports all day long.
Can someone assist with commands and examples.
Thanks,
On the 3560, I have a few VLans set up. because of the amount of data going across the switches, I want to aggregate the link between the switches. I have been looking for information on aggregating trunks and have not found much useful information. I find information on aggregating access ports all day long.
Can someone assist with commands and examples.
Thanks,
To clarify, you want to trunk the two switches together with a bundled channel-group?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
atlas_shuddered - on the 3560 I have several VLANS configured. say 300 - 309. They will be carrying a lot of data. I want to take ports 46 - 48 on the 3560 and create a port group and aggregate them and allow data from vlans 300-309 to traverse to the HP Switch which will have ports on various vlans.
Port 1-5 might be on vlan 300
port 6-10 might be on vlan 301 etc.
Thanks,
Port 1-5 might be on vlan 300
port 6-10 might be on vlan 301 etc.
Thanks,
ASKER
On the Cisco Side, would it basically look like the following?
interface Port-channel2
description STTS-Switch
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 300-309
switchport mode trunk
Then on the various physical ports:
interface GigabitEthernet0/36
description STTS-Switch
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 300-309
switchport mode trunk
channel-group 2 mode on
interface Port-channel2
description STTS-Switch
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 300-309
switchport mode trunk
Then on the various physical ports:
interface GigabitEthernet0/36
description STTS-Switch
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 300-309
switchport mode trunk
channel-group 2 mode on
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is what I have thus far on the CISCO
interface Port-channel2
description STTS-Link aggregation
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 300-309
switchport mode trunk
!
!
interface GigabitEthernet0/46
description STTS Aggregate Link
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 300-309
switchport mode trunk
channel-group 2 mode active
!
interface GigabitEthernet0/47
description STTS Aggregate Link
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 300-309
switchport mode trunk
channel-group 2 mode active
!
interface GigabitEthernet0/48
description STTS Aggregate Link
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 300-309
switchport mode trunk
channel-group 2 mode active
!
I assume LACP mode provides better traffic compatibility between CISCO and HP?
interface Port-channel2
description STTS-Link aggregation
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 300-309
switchport mode trunk
!
!
interface GigabitEthernet0/46
description STTS Aggregate Link
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 300-309
switchport mode trunk
channel-group 2 mode active
!
interface GigabitEthernet0/47
description STTS Aggregate Link
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 300-309
switchport mode trunk
channel-group 2 mode active
!
interface GigabitEthernet0/48
description STTS Aggregate Link
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 300-309
switchport mode trunk
channel-group 2 mode active
!
I assume LACP mode provides better traffic compatibility between CISCO and HP?
LACP is just a negotiation protocol to automatically setup the etherchannel. It should work fine between a Cisco and HP being a standards based protocol protocol. Mode On, uses no negotiation protocol and is considered a static etherchannel. You will also want to make sure your spanning tree between the two works fine, being Cisco user a Per-vlan based spanning tree. I believe HP's use common spanning tree. I could be wrong here and that's another topic.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
@atlas
Good catch!
Good catch!
@Soulja - LOL, Nah. Just flashbacks of long hours of cranial de-pelting.
@atlas
ROFL!
ROFL!
ASKER
Soulja and Atlas, wanted to report back that everything seems to be up and running on both switches. Communication seems happy and I am happy. Thanks for the verification and pointers.
Awesome. Thanks for the update!
Sounds good. Cheers