Switches / Hubs
--
Questions
--
Followers
Top Experts
Trunking Between Cisco 3750 and HP GbE2c
I'm trying to set up a trunk between a Cisco 3750 switch and an HP GbE2c Layer 2/3 Ethernet Blade Switch. The trunk will replace an existing, single-port connection, so that more bandwidth is available. At first, the trunk will use only one port on each switch, and once I know it's working, I'll add more ports.
The problem is that, while the trunk is active and the status looks good on both switches, no traffic gets through, so I'm missing something pretty basic.
On the GbE2c switch, I ran the following commands:
/cfg/l2/vlan
name
192.168.200.0 Subnet
add 22
ena
/cfg/l2/lacp/port 22
mode passive
adminkey 2
/cfg/port 22
tag
e
apply
save
On the Cisco switch:
int gi2/0/8
desc EtherChannel to C7000 GbE2c switch 1
channel-group 2 mode active
exit
interface Port-channel2
description EtherChannel to C7000 GbE2c switch 1
switchport access vlan 200
exit
end
Running "/info/l2/trunk" on the HP switch shows the trunk is active. On the Cisco switch, I ran:
show etherchannel sum
show etherchannel port-channel
This shows the trunk is active as well.
Yet no traffic goes through.
The hashing algorithm is "src-dst-mac" on the Cisco side, which corresponds to "smac dmac" on the HP side.
Any suggestions?
The problem is that, while the trunk is active and the status looks good on both switches, no traffic gets through, so I'm missing something pretty basic.
On the GbE2c switch, I ran the following commands:
/cfg/l2/vlan
name
192.168.200.0 Subnet
add 22
ena
/cfg/l2/lacp/port 22
mode passive
adminkey 2
/cfg/port 22
tag
e
apply
save
On the Cisco switch:
int gi2/0/8
desc EtherChannel to C7000 GbE2c switch 1
channel-group 2 mode active
exit
interface Port-channel2
description EtherChannel to C7000 GbE2c switch 1
switchport access vlan 200
exit
end
Running "/info/l2/trunk" on the HP switch shows the trunk is active. On the Cisco switch, I ran:
show etherchannel sum
show etherchannel port-channel
This shows the trunk is active as well.
Yet no traffic goes through.
The hashing algorithm is "src-dst-mac" on the Cisco side, which corresponds to "smac dmac" on the HP side.
Any suggestions?
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Check the vlan config on the GbE2c, especially the TAG_PVID part.
Tamas
Tamas
I have to admit that I do not know the HP part of your config. But I read something that says tag and e which in my opinion means tagging enabled. If you want to have a tagged interface on the Cisco side it looks like that:
interface Port-channel2
description EtherChannel to C7000 GbE2c switch 1
switchport trunk encapsualtion dot1q
switchport mode trunk
If you want to limit the forwarding only to VLAN 200 you may add
switchport trunk allowed vlan 200
Your issues might be caused by the word "trunk" which in HP terms means interface bonding and in Cisco terms means tagged VLAN transport over an interface.
interface Port-channel2
description EtherChannel to C7000 GbE2c switch 1
switchport trunk encapsualtion dot1q
switchport mode trunk
If you want to limit the forwarding only to VLAN 200 you may add
switchport trunk allowed vlan 200
Your issues might be caused by the word "trunk" which in HP terms means interface bonding and in Cisco terms means tagged VLAN transport over an interface.
You folks gave me some things to check. I really don't care which VLAN the traffic belongs to; I want all traffic between these two switches to pass on EtherChannel (in Cisco-speak) or trunk (in HP-speak). So I removed the VLAN coding.
The relevant part of the HP config follows.
=== snip ===
/c/l2/thash/set
smac enabled
dmac enabled
/c/l2/lacp/port 22
mode passive
adminkey 2
=== snip ===
The relevant part of the Cisco config follows.
=== snip ===
interface Port-channel2
description EtherChannel to C7000 GbE2c switch 1
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet2/0/8
description EtherChannel to C7000 GbE2c switch 1
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 2 mode active
!
#show etherchannel sum
Flags: D - down P - in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
Number of channel-groups in use: 2
Number of aggregators: 2
Group Port-channel Protocol Ports
------+-------------+-----
2 Po2(SU) LACP Gi2/0/8(P)
=== snip ===
Note that the etherchannel is up (the P status)and in use (the U).
Port 22 on the HP switch is connected to 2/0/8 on the Cisco switch.
Thoughts?
The relevant part of the HP config follows.
=== snip ===
/c/l2/thash/set
smac enabled
dmac enabled
/c/l2/lacp/port 22
mode passive
adminkey 2
=== snip ===
The relevant part of the Cisco config follows.
=== snip ===
interface Port-channel2
description EtherChannel to C7000 GbE2c switch 1
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet2/0/8
description EtherChannel to C7000 GbE2c switch 1
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 2 mode active
!
#show etherchannel sum
Flags: D - down P - in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
Number of channel-groups in use: 2
Number of aggregators: 2
Group Port-channel Protocol Ports
------+-------------+-----
2 Po2(SU) LACP Gi2/0/8(P)
=== snip ===
Note that the etherchannel is up (the P status)and in use (the U).
Port 22 on the HP switch is connected to 2/0/8 on the Cisco switch.
Thoughts?
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Okay, so you remove the vlan tagging on the HP? The cisco config reads " switchport mode trunk", so that tags. Or maybe I'm misunderstanding.
Can you post a full config from the HP? The config of these AOS based switches is kinda hard for me to comprehend in snippets... :)
Can you post a full config from the HP? The config of these AOS based switches is kinda hard for me to comprehend in snippets... :)
The following items must match before a port-channel can form:
- same speed/duplex
- Access VLAN (if not trunked)
- Same trunking type (802.1q/DOT1.q), allowed VLAN and native VLAN (if trunked)
- Each port must have the same STP cost per VLAN with-in the portchannel
- No SPAN ports
Use:
channel-group [#] mode on (disables PagP and uses LACP) it will start to send LACP packets)
Example:
3750(config)#interface range gigabitethernet 1/0/2 - 4
3750(config-if-range)#chan
3750(config-if-range)#swit
3750(config-if-range)#swit
3750(config-if-range)#swit
First type the channel-group command. After that all interface commands will be automatically duplicated on all the interfaces group in the channel-group.
Using:
channel-group [#] mode passive (use LACP in a passive mode, it will wait until a PAgP packet will be send). PAgP is Cisco's Proprietary EtherChannel protocol and is not compatible.
The key here is creating a dynamic LAG using 802.1ad (LACP). On the HP side make sure you are using the compatible dynamic 802.1ad LACP settings. Any setting referring to Static or Passive won't work given that the open standard is dynamic in nature.
- same speed/duplex
- Access VLAN (if not trunked)
- Same trunking type (802.1q/DOT1.q), allowed VLAN and native VLAN (if trunked)
- Each port must have the same STP cost per VLAN with-in the portchannel
- No SPAN ports
Use:
channel-group [#] mode on (disables PagP and uses LACP) it will start to send LACP packets)
Example:
3750(config)#interface range gigabitethernet 1/0/2 - 4
3750(config-if-range)#chan
3750(config-if-range)#swit
3750(config-if-range)#swit
3750(config-if-range)#swit
First type the channel-group command. After that all interface commands will be automatically duplicated on all the interfaces group in the channel-group.
Using:
channel-group [#] mode passive (use LACP in a passive mode, it will wait until a PAgP packet will be send). PAgP is Cisco's Proprietary EtherChannel protocol and is not compatible.
The key here is creating a dynamic LAG using 802.1ad (LACP). On the HP side make sure you are using the compatible dynamic 802.1ad LACP settings. Any setting referring to Static or Passive won't work given that the open standard is dynamic in nature.
Correction: I meant 802.3ad not 802.1ad
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Basic VLANing Notes:
1) Ports are either 'Tagged' with one or more VLAN IDs and/or 'Untagged' with a single VLAN ID. The packet header either has a VLAN ID or NOT (with is considered 'Tagged' and without is considered 'Untagged').
2) Only a single VLAN ID can be assigned and identified as an 'Untagged' VLAN, which is also identified as the Native VLAN. Any connected port or device assumes the network of an untagged VLAN. This assumes the connected port or device/NIC is also untagged (has no VLAN assignment).
3) Multiple VLAN IDs can be Tagged on a signal port with no more than one Untagged VLAN (i.e. Native VLAN).
4) On Tagged VLANs interfaces, the connected switch port or device/NIC requires matching Tagged VLAN IDs. This could be between two or multile switches interface connections to eachother or a switch port connecting up to a server or other device. Example: an ESX server passing multiple VLANs up to a virtual ESX vSwitch. VLANs identified in the vSwitch with a VLAN ID are considered tagged.
Note: In the non-Cisco world, most vendors identify VLANs in either a tagged or untagged manner as opposed to Cisco using a confusing term like Trunking (ISL Trunk or DOT1q Trunk). Trunking in the non-Cisco world is typically referred to as Link Aggregation Groups (LAGs) or LACP Trunks vs Cisco's EtherChannel.
1) Ports are either 'Tagged' with one or more VLAN IDs and/or 'Untagged' with a single VLAN ID. The packet header either has a VLAN ID or NOT (with is considered 'Tagged' and without is considered 'Untagged').
2) Only a single VLAN ID can be assigned and identified as an 'Untagged' VLAN, which is also identified as the Native VLAN. Any connected port or device assumes the network of an untagged VLAN. This assumes the connected port or device/NIC is also untagged (has no VLAN assignment).
3) Multiple VLAN IDs can be Tagged on a signal port with no more than one Untagged VLAN (i.e. Native VLAN).
4) On Tagged VLANs interfaces, the connected switch port or device/NIC requires matching Tagged VLAN IDs. This could be between two or multile switches interface connections to eachother or a switch port connecting up to a server or other device. Example: an ESX server passing multiple VLANs up to a virtual ESX vSwitch. VLANs identified in the vSwitch with a VLAN ID are considered tagged.
Note: In the non-Cisco world, most vendors identify VLANs in either a tagged or untagged manner as opposed to Cisco using a confusing term like Trunking (ISL Trunk or DOT1q Trunk). Trunking in the non-Cisco world is typically referred to as Link Aggregation Groups (LAGs) or LACP Trunks vs Cisco's EtherChannel.
Either both sides are tagged or both sides are untagged. You seem to have untagged the HP side and tagged the Cisco now.
On the HP side VLAN 200 is not defined. You need to define common Native VLAN IDs and tagged VLANs on both the HP and Cisco switches. Also, on the HP switch LACP mode is set to passive which isn't compatible with Cisco; needs to be set to dynamic.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Okay, I'm confused. I already have an EtherChannel between this switch and another Cisco switch, and that's working fine. The working EtherChannel's config looks like this:
interface Port-channel1
switchport trunk encapsulation dot1q
switchport mode trunk
So apparently this is tagging traffic to a VLAN? It must be the default of 1, because traffic from many VLANs goes through this EtherChannel.
I figured that the configuration for my Cisco-HP EtherChannel should be the same on the Cisco side, since I don't care about VLANs here.
My current configuration for the EtherChannel is:
interface Port-channel2
description EtherChannel to C7000 GbE2c switch 1
switchport trunk encapsulation dot1q
switchport mode trunk
exit
And for the one port using it:
int gi2/0/8
desc EtherChannel to C7000 GbE2c switch 1
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 2 mode active
The current config of the HP switch is this:
/c/l2/stp 128/port 19/cost 4
/c/l2/thash/set
smac enabled
dmac enabled
sip disabled
dip disabled
/c/l2/lacp/port 22
mode passive
adminkey 2
I've deleted some lines pertaining to SNMP, syslog, text prompts, and other irrelevant stuff.
interface Port-channel1
switchport trunk encapsulation dot1q
switchport mode trunk
So apparently this is tagging traffic to a VLAN? It must be the default of 1, because traffic from many VLANs goes through this EtherChannel.
I figured that the configuration for my Cisco-HP EtherChannel should be the same on the Cisco side, since I don't care about VLANs here.
My current configuration for the EtherChannel is:
interface Port-channel2
description EtherChannel to C7000 GbE2c switch 1
switchport trunk encapsulation dot1q
switchport mode trunk
exit
And for the one port using it:
int gi2/0/8
desc EtherChannel to C7000 GbE2c switch 1
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 2 mode active
The current config of the HP switch is this:
/c/l2/stp 128/port 19/cost 4
/c/l2/thash/set
smac enabled
dmac enabled
sip disabled
dip disabled
/c/l2/lacp/port 22
mode passive
adminkey 2
I've deleted some lines pertaining to SNMP, syslog, text prompts, and other irrelevant stuff.
gsmartin:
The HP switch won't let me use dynamic LACP. My options are active, passive, or off.
all:
I appreciate your wisdom and advice here. There's something fundamental that I'm missing (other than that I should have stuck to Cisco switches throughout). If it's VLAN-tagging, I can enable that on both switches, but then I don't understand why my other EtherChannel (which is Cisco-Cisco) works.
The HP switch won't let me use dynamic LACP. My options are active, passive, or off.
all:
I appreciate your wisdom and advice here. There's something fundamental that I'm missing (other than that I should have stuck to Cisco switches throughout). If it's VLAN-tagging, I can enable that on both switches, but then I don't understand why my other EtherChannel (which is Cisco-Cisco) works.
use active this should be equivalent to dynamic. Cisco to Cisco EtherChannel use PagP vs LACP to communicate this is different. PagP is Cisco Proprietary protocol and LACP is IEEE open standard dynamic aggregation protocol.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Change the Cisco side from mode Active to Mode On. This will disable PagP and use LACP only.
The mode type doesn't have anything to do with VLANs.
You only define tagged VLANs assuming both switches will be sharing VLAN traffic. Otherwise, if you are only using a default Native VLAN then it can be left untagged on both sides. But, understand their is a difference between tagged vs untagged.
The mode type doesn't have anything to do with VLANs.
You only define tagged VLANs assuming both switches will be sharing VLAN traffic. Otherwise, if you are only using a default Native VLAN then it can be left untagged on both sides. But, understand their is a difference between tagged vs untagged.
Let's look at the three thing that are in the discussion:
1. Negotiation of the Etherchannel (LACP/PagP discussion):
To establish an EtherChannel (HP term: trunk) the standard protocol LACP (802.3ad) is needed. If I read the HP manual correctly the HP switch is not capable of using the Cisco proprietary protocol PagP (see http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=115&prodSeriesId=3707371&prodTypeId=3709945&objectID=c01182403).
The Cisco EtherChannel keywords do not easily tell you if you are using PagP or LACP. "active" or "passive" are used for LACP; lloking at the example from HP I'd prefer "active". (see http://www.cisco.com/en/US/products/hw/switches/ps663/products_configuration_example09186a0080094aec.shtml#modes)
2. Tagged (Cisco term trunk) or untagged (Cisco term access)
Whether you want to send tagged or untagged traffic is a matter of your network design. If multiple VLAN need to be sent over the link (in this case the EtherChannel) then you have a tagged interface, if only one VLAN needs to be sent then you may use the interface untagged. The important thing is that both ends of the link (in your case the Cisco and the HP) agree if it is tagged or untagged.
The tag contains the VLAN number so the switch at the end of the link can decide which frame belongs to which VLAN. If there is no tag in the frame (untagged) the switch at the end of the link can only look in its own configuration to see what VLAN is assigned to the port on which it received the frame.
3. Native VLAN
Native VLAN are a specialty for tagged links. Normally you would assume that on a tagged link only frames with tag travel from one side to the other. However with funny network designs (i.e. by adding a hub between the two switches) you could introduce the possiblity that untagged frames could be sent to the switch (i.e. by a PC that is attached to the hub). Now the native VLAN instructs the switch to assign frames without a VLAN tag to the native VLAN. Cisco sets VLAN 1 as the default native VLAN but you also can configure another VLAN to be the native VLAN. HP to my knowledge does not have a default native VLAN (see https://www.experts-exchange.com/questions/27523389/Configure-port-trunking-between-HP-Gbe2c-and-Cisco-cat-2950.html)
1. Negotiation of the Etherchannel (LACP/PagP discussion):
To establish an EtherChannel (HP term: trunk) the standard protocol LACP (802.3ad) is needed. If I read the HP manual correctly the HP switch is not capable of using the Cisco proprietary protocol PagP (see http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=115&prodSeriesId=3707371&prodTypeId=3709945&objectID=c01182403).
The Cisco EtherChannel keywords do not easily tell you if you are using PagP or LACP. "active" or "passive" are used for LACP; lloking at the example from HP I'd prefer "active". (see http://www.cisco.com/en/US/products/hw/switches/ps663/products_configuration_example09186a0080094aec.shtml#modes)
2. Tagged (Cisco term trunk) or untagged (Cisco term access)
Whether you want to send tagged or untagged traffic is a matter of your network design. If multiple VLAN need to be sent over the link (in this case the EtherChannel) then you have a tagged interface, if only one VLAN needs to be sent then you may use the interface untagged. The important thing is that both ends of the link (in your case the Cisco and the HP) agree if it is tagged or untagged.
The tag contains the VLAN number so the switch at the end of the link can decide which frame belongs to which VLAN. If there is no tag in the frame (untagged) the switch at the end of the link can only look in its own configuration to see what VLAN is assigned to the port on which it received the frame.
3. Native VLAN
Native VLAN are a specialty for tagged links. Normally you would assume that on a tagged link only frames with tag travel from one side to the other. However with funny network designs (i.e. by adding a hub between the two switches) you could introduce the possiblity that untagged frames could be sent to the switch (i.e. by a PC that is attached to the hub). Now the native VLAN instructs the switch to assign frames without a VLAN tag to the native VLAN. Cisco sets VLAN 1 as the default native VLAN but you also can configure another VLAN to be the native VLAN. HP to my knowledge does not have a default native VLAN (see https://www.experts-exchange.com/questions/27523389/Configure-port-trunking-between-HP-Gbe2c-and-Cisco-cat-2950.html)
Thanks for reiterrating our points. For the most part, we are on the same page of what needs to be configured. With the exception of default/native VLAN. HP uses a default primary VLAN ID of 1. Note the term 'Primary' this is the trem HP uses vs. Native for the default VLAN that Cisco uses. Given that Cisco also uses VLAN 1 for it's default Native VLAN. So wither you change the default VLAN IDs or not the same VLAN needs to be configured on both Cisco and HP connected switch ports. Your default native or primary VLAN is configured as untagged and then configure all other VLANs that are shared between switches as tagged (HP) or trunked on (Cisco). You only need to tag additional VLAN IDs, only if other VLANs need to transverse between access layer switch environments.
Here are some links for HP and Cisco switch configurations:
http://www.hp.com/rnd/support/config_examples/primary_vlan.pdf
http://www.buildabox.net/2011/08/vlan-trunking-between-cisco-and-procurve-switches/
https://supportforums.cisco.com/thread/2044720
http://arstechnica.com/civis/viewtopic.php?f=10&t=119616
http://www.buildabox.net/2011/08/vlan-trunking-between-cisco-and-procurve-switches/
Here are some links for HP and Cisco switch configurations:
http://www.hp.com/rnd/support/config_examples/primary_vlan.pdf
http://www.buildabox.net/2011/08/vlan-trunking-between-cisco-and-procurve-switches/
https://supportforums.cisco.com/thread/2044720
http://arstechnica.com/civis/viewtopic.php?f=10&t=119616
http://www.buildabox.net/2011/08/vlan-trunking-between-cisco-and-procurve-switches/
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Hello, all. I believe I have now configured the VLAN tagging (or lack thereof) and LACP settings correctly. Both switches now use active LACP mode, and that appears to be working, and the VLAN settings look right. Here are some queries I ran on the HP switch:
/info/l2/trunk
Trunk group 1: Enabled
Protocol - Static
port state:
17: STG 1 DOWN
Reminder: Port 17 needs to be enabled.
18: STG 1 DOWN
Reminder: Port 18 needs to be enabled.
Trunk group 13: Enabled
Protocol - LACP
port state:
22: STG 1 forwarding
[COMMENT: Not sure if the STP value here is correct]
# /info/l2/lacp
--------------------------
[LACP Menu]
aggr - Show LACP aggregator information for the port
port - Show LACP port information
dump - Show all LACP ports information
# port 22
port 22
--------------------------
lacp_enabled - TRUE
lacp_admin_enabled - TRUE
Actor System ID - 00:18:b1:27:07:00
Actor System Priority - 32768
Actor Admin Key - 2
Actor Oper Key - 2
Actor Port Number - 22
Actor Port Priority - 32768
Partner Oper System Priority - 32768
Partner Oper System ID - 00:11:20:fb:b9:80
Partner Oper Key - 2
Partner Oper Port Number - 60
Partner Oper Port Priority - 32768
Press q to quit, any other key to continue Actor Admin Port state
Activity: Active Timeout: Long Aggregation: TRUE
Synchronization:FALSE Collecting: FALSE Distributing: FALSE
Defaulted: FALSE Expired: FALSE
Actor Oper Port state
Activity: Active Timeout: Long Aggregation: TRUE
Synchronization:TRUE Collecting: TRUE Distributing: TRUE
Defaulted: FALSE Expired: FALSE
Partner Oper Port state
Activity: Active Timeout: Long Aggregation: TRUE
Synchronization:TRUE Collecting: TRUE Distributing: TRUE
Defaulted: FALSE Expired: FALSE
Individual - FALSE
Selected Aggregator ID - 2
Attached Aggregator ID - 2
ready_n - TRUE
ntt - FALSE
selected - Selected
port_moved - FALSE
Collision and Detection state turned ON!
Rx machine state - LACP_RX_CURRENT_STATE
Mux machine state - LACP_MUX_COL_DIS_STATE
Periodic machine state - LACP_PERIODIC_SLOW_STATE
# /info/l2/vlan
VLAN Name Status Ports
---- --------------------------
1 Default VLAN ena 1-18 20-24
Reminder: Port 17 needs to be enabled.
Reminder: Port 18 needs to be enabled.
4095 Mgmt VLAN ena 19
As you can see, port 22 (the one I'm working on) can see its LACP partner on the Cisco switch, and belongs to the default VLAN of 1. I'm not sure if the STP value of "forwarding" is correct here, though.
On the Cisco side, here's the current config:
port-channel load-balance src-dst-mac
!
spanning-tree mode pvst
no spanning-tree optimize bpdu transmission
spanning-tree extend system-id
spanning-tree vlan 41-42,200,225,230 forward-time 5
!
vlan internal allocation policy ascending
!
interface Port-channel2
description EtherChannel to C7000 GbE2c switch 1
switchport trunk encapsulation dot1q
switchport mode access
!
interface GigabitEthernet2/0/8
description EtherChannel to C7000 GbE2c switch 1
switchport trunk encapsulation dot1q
switchport mode access
channel-group 2 mode active
!
switch3750-42#show etherchannel summ
Flags: D - down P - in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
Number of channel-groups in use: 2
Number of aggregators: 2
Group Port-channel Protocol Ports
------+-------------+-----
1 Po1(SU) LACP Gi1/0/25(P) Gi1/0/26(P)
2 Po2(SU) LACP Gi2/0/8(P)
switch3750-42#show etherchannel port-channel
Channel-group listing:
----------------------
Group: 1
----------
Port-channels in the group:
--------------------------
Port-channel: Po1 (Primary Aggregator)
------------
Age of the Port-channel = 35d:08h:39m:26s
Logical slot/port = 10/1 Number of ports = 2
HotStandBy port = null
Port state = Port-channel Ag-Inuse
Protocol = LACP
Ports in the Port-channel:
Index Load Port EC state No of bits
------+------+------+-----
0 00 Gi1/0/25 Active 0
0 00 Gi1/0/26 Active 0
Time since last port bundled: 35d:03h:31m:59s Gi1/0/26
Time since last port Un-bundled: 35d:03h:34m:57s Gi1/0/26
Group: 2
----------
Port-channels in the group:
--------------------------
Port-channel: Po2 (Primary Aggregator)
------------
Age of the Port-channel = 32d:21h:00m:08s
Logical slot/port = 10/2 Number of ports = 1
HotStandBy port = null
Port state = Port-channel Ag-Inuse
Protocol = LACP
Ports in the Port-channel:
Index Load Port EC state No of bits
------+------+------+-----
0 00 Gi2/0/8 Active 0
Time since last port bundled: 00d:00h:10m:15s Gi2/0/8
Time since last port Un-bundled: 00d:00h:10m:19s Gi2/0/8
switch3750-42#show lacp neighbor
Flags: S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode P - Device is in Passive mode
Channel group 1 neighbors
Partner's information:
LACP port Oper Port Port
Port Flags Priority Dev ID Age Key Number State
Gi1/0/25 SP 32768 0014.69cc.6600 12s 0x1 0x19 0x3C
Gi1/0/26 SP 32768 0014.69cc.6600 21s 0x1 0x1A 0x3C
Channel group 2 neighbors
Partner's information:
LACP port Oper Port Port
Port Flags Priority Dev ID Age Key Number State
Gi2/0/8 SA 32768 0018.b127.0700 4s 0x2 0x16 0x3D
Still, no traffic flows over this Etherchannel/trunk.
Any suggestions?
/info/l2/trunk
Trunk group 1: Enabled
Protocol - Static
port state:
17: STG 1 DOWN
Reminder: Port 17 needs to be enabled.
18: STG 1 DOWN
Reminder: Port 18 needs to be enabled.
Trunk group 13: Enabled
Protocol - LACP
port state:
22: STG 1 forwarding
[COMMENT: Not sure if the STP value here is correct]
# /info/l2/lacp
--------------------------
[LACP Menu]
aggr - Show LACP aggregator information for the port
port - Show LACP port information
dump - Show all LACP ports information
# port 22
port 22
--------------------------
lacp_enabled - TRUE
lacp_admin_enabled - TRUE
Actor System ID - 00:18:b1:27:07:00
Actor System Priority - 32768
Actor Admin Key - 2
Actor Oper Key - 2
Actor Port Number - 22
Actor Port Priority - 32768
Partner Oper System Priority - 32768
Partner Oper System ID - 00:11:20:fb:b9:80
Partner Oper Key - 2
Partner Oper Port Number - 60
Partner Oper Port Priority - 32768
Press q to quit, any other key to continue Actor Admin Port state
Activity: Active Timeout: Long Aggregation: TRUE
Synchronization:FALSE Collecting: FALSE Distributing: FALSE
Defaulted: FALSE Expired: FALSE
Actor Oper Port state
Activity: Active Timeout: Long Aggregation: TRUE
Synchronization:TRUE Collecting: TRUE Distributing: TRUE
Defaulted: FALSE Expired: FALSE
Partner Oper Port state
Activity: Active Timeout: Long Aggregation: TRUE
Synchronization:TRUE Collecting: TRUE Distributing: TRUE
Defaulted: FALSE Expired: FALSE
Individual - FALSE
Selected Aggregator ID - 2
Attached Aggregator ID - 2
ready_n - TRUE
ntt - FALSE
selected - Selected
port_moved - FALSE
Collision and Detection state turned ON!
Rx machine state - LACP_RX_CURRENT_STATE
Mux machine state - LACP_MUX_COL_DIS_STATE
Periodic machine state - LACP_PERIODIC_SLOW_STATE
# /info/l2/vlan
VLAN Name Status Ports
---- --------------------------
1 Default VLAN ena 1-18 20-24
Reminder: Port 17 needs to be enabled.
Reminder: Port 18 needs to be enabled.
4095 Mgmt VLAN ena 19
As you can see, port 22 (the one I'm working on) can see its LACP partner on the Cisco switch, and belongs to the default VLAN of 1. I'm not sure if the STP value of "forwarding" is correct here, though.
On the Cisco side, here's the current config:
port-channel load-balance src-dst-mac
!
spanning-tree mode pvst
no spanning-tree optimize bpdu transmission
spanning-tree extend system-id
spanning-tree vlan 41-42,200,225,230 forward-time 5
!
vlan internal allocation policy ascending
!
interface Port-channel2
description EtherChannel to C7000 GbE2c switch 1
switchport trunk encapsulation dot1q
switchport mode access
!
interface GigabitEthernet2/0/8
description EtherChannel to C7000 GbE2c switch 1
switchport trunk encapsulation dot1q
switchport mode access
channel-group 2 mode active
!
switch3750-42#show etherchannel summ
Flags: D - down P - in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
Number of channel-groups in use: 2
Number of aggregators: 2
Group Port-channel Protocol Ports
------+-------------+-----
1 Po1(SU) LACP Gi1/0/25(P) Gi1/0/26(P)
2 Po2(SU) LACP Gi2/0/8(P)
switch3750-42#show etherchannel port-channel
Channel-group listing:
----------------------
Group: 1
----------
Port-channels in the group:
--------------------------
Port-channel: Po1 (Primary Aggregator)
------------
Age of the Port-channel = 35d:08h:39m:26s
Logical slot/port = 10/1 Number of ports = 2
HotStandBy port = null
Port state = Port-channel Ag-Inuse
Protocol = LACP
Ports in the Port-channel:
Index Load Port EC state No of bits
------+------+------+-----
0 00 Gi1/0/25 Active 0
0 00 Gi1/0/26 Active 0
Time since last port bundled: 35d:03h:31m:59s Gi1/0/26
Time since last port Un-bundled: 35d:03h:34m:57s Gi1/0/26
Group: 2
----------
Port-channels in the group:
--------------------------
Port-channel: Po2 (Primary Aggregator)
------------
Age of the Port-channel = 32d:21h:00m:08s
Logical slot/port = 10/2 Number of ports = 1
HotStandBy port = null
Port state = Port-channel Ag-Inuse
Protocol = LACP
Ports in the Port-channel:
Index Load Port EC state No of bits
------+------+------+-----
0 00 Gi2/0/8 Active 0
Time since last port bundled: 00d:00h:10m:15s Gi2/0/8
Time since last port Un-bundled: 00d:00h:10m:19s Gi2/0/8
switch3750-42#show lacp neighbor
Flags: S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode P - Device is in Passive mode
Channel group 1 neighbors
Partner's information:
LACP port Oper Port Port
Port Flags Priority Dev ID Age Key Number State
Gi1/0/25 SP 32768 0014.69cc.6600 12s 0x1 0x19 0x3C
Gi1/0/26 SP 32768 0014.69cc.6600 21s 0x1 0x1A 0x3C
Channel group 2 neighbors
Partner's information:
LACP port Oper Port Port
Port Flags Priority Dev ID Age Key Number State
Gi2/0/8 SA 32768 0018.b127.0700 4s 0x2 0x16 0x3D
Still, no traffic flows over this Etherchannel/trunk.
Any suggestions?
STP forwarding is correct. Trying using 'on' vs 'active' for the mode type on the Cisco side. Also note, when using LACP or EtherChannel you no longer require Spanning-tree. STP is only used for redundant switchport links that are not using LACP.
Also, the on the HP side is indicating it is using Static LACP not dynamic.
Please show the VLAN configuration for the HP LACP LAG ports.
Also, the on the HP side is indicating it is using Static LACP not dynamic.
Please show the VLAN configuration for the HP LACP LAG ports.
Possibly stupid question regarding the topology in the blade:
HP c-class blades usually ship with 2 GbE2c switches, in the first two slots. The half-width blades (like the BL460c) have 2 NICs, one terminating on each switch.
The ports 17-18 ("Trunk group 1" in your config) are the hardwired cross-connect between the 2 switches.
Now, if you use the NIC in the server, that's connected to switch1, and configure the LACP uplink on switch2, but the connection between the switches is disabled (as in your current config), then traffic will be blocked.
I'm absolutely not sure if this is the current case, just checking with you.
Tamas
HP c-class blades usually ship with 2 GbE2c switches, in the first two slots. The half-width blades (like the BL460c) have 2 NICs, one terminating on each switch.
The ports 17-18 ("Trunk group 1" in your config) are the hardwired cross-connect between the 2 switches.
Now, if you use the NIC in the server, that's connected to switch1, and configure the LACP uplink on switch2, but the connection between the switches is disabled (as in your current config), then traffic will be blocked.
I'm absolutely not sure if this is the current case, just checking with you.
Tamas
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
On my c7000 I don't have the GbE2c switch modules, but have the HP Flex-10 switch modules. Although they are different there may be some similarities. When testing LAG configurations I found that I could only create a LACP dynamic LAG with two ports on the same switch module vs creating a LAG with a port from each switch module; resulting in an active/ standby failiover configuration. Plus, on my Brocade RX-16 required a LACP dynamic setting; static LACP setting failed to create the LAG as expected.
gsmartin: Both the Cisco and HP LACP modes are set to 'active'. I suspect the HP reports being static because that was the result of the LACP negotiation. On the HP side, port 22 is a member of VLAN 1 (the default) and no other.
TimotiSt: My C7000 does, as you suspect, have two GbE2c switches in slots 1 and 2. I'm using the server blade NICs attached to switch 1, but the trunk involves the external switch ports (initally port 22, but I'll add more once I get this working) of switch 1 only.
Switch 2's crosslink to switch 1 (ports 17-18) is disabled, so the two switches should be independent. Each blade server is connected to both switches (for redundancy).
My plan is to create the trunk (HP)/EtherChannel (Cisco) on switch 1 first. Once that's working, I'll create a similar one on switch 2, but I'll leave the crosslink disabled, so they'll be independent.
gsmartin (post #2): That's my plan as well.
TimotiSt: My C7000 does, as you suspect, have two GbE2c switches in slots 1 and 2. I'm using the server blade NICs attached to switch 1, but the trunk involves the external switch ports (initally port 22, but I'll add more once I get this working) of switch 1 only.
Switch 2's crosslink to switch 1 (ports 17-18) is disabled, so the two switches should be independent. Each blade server is connected to both switches (for redundancy).
My plan is to create the trunk (HP)/EtherChannel (Cisco) on switch 1 first. Once that's working, I'll create a similar one on switch 2, but I'll leave the crosslink disabled, so they'll be independent.
gsmartin (post #2): That's my plan as well.
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
I received some excellent suggestions from EE members on things to check, but none of them identified the MTU problem.
If possible, I'd like to spread the 500 points among the EE contributors to this issue, as their knowledge was very educational.
If possible, I'd like to spread the 500 points among the EE contributors to this issue, as their knowledge was very educational.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Switches / Hubs
--
Questions
--
Followers
Top Experts
A switch is a device that filters and forwards packets of data between LAN segments. Switches operate at the data link layer or the network layer of the Open Systems Interconnection (OSI) Reference Model and therefore support any packet protocol. LANs that use switches to join segments are called switched LANs or, in the case of Ethernet networks, switched Ethernet LANs. A hub is a connection point for devices in a network. Hubs are commonly used to connect segments of a LAN. A hub contains multiple ports; when a packet arrives at one port, it is copied to the other ports so that all segments of the LAN can see all packets.