02-08-2011 07:26 AM - edited 03-06-2019 03:25 PM
Hi,
Can anyone tell my why it creates a "B" portchannel?
Here is come configuration:
***************************************************************************************
core-server01#sh etherchannel 225 summ
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use N - not in use, no aggregation
f - failed to allocate aggregator
M - not in use, no aggregation due to minimum links not met
m - not in use, port not aggregated due to minimum links not met
u - unsuitable for bundling
d - default port
w - waiting to be aggregated
Number of channel-groups in use: 7
Number of aggregators: 8
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
225 Po225(SU) LACP Gi3/44(P) Gi3/45(P)
225 Po225B(SU) LACP Gi3/46(P) Gi3/47(P) Gi3/48(P)
**************************************************************************************
interface Port-channel225
description portchannel mod BLC02
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10-50
switchport mode trunk
**************************************************************************************
interface GigabitEthernet3/44
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10-50
switchport mode trunk
no mdix auto
channel-protocol lacp
channel-group 225 mode active
spanning-tree portfast edge trunk
end
**************************************************************************************
interface GigabitEthernet3/46
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10-50
switchport mode trunk
no mdix auto
channel-protocol lacp
channel-group 225 mode active
spanning-tree portfast edge trunk
end
It is an etherchannel for HP Blade on a Catalyst 6509e running IOS 12.2(33)SXI3.
Our problem is that we can't reach all of our servers on blade center.
Regards
Thomas
Solved! Go to Solution.
02-08-2011 07:41 AM
The answer that has been reported in the forums is that for some reasons the link members under for example 225B had one minor difference at the moment of forming the bundle.
Hope to Help !!
Ganesh.H
02-08-2011 07:41 AM
The answer that has been reported in the forums is that for some reasons the link members under for example 225B had one minor difference at the moment of forming the bundle.
Hope to Help !!
Ganesh.H
02-22-2011 06:32 AM
Hi Ganesh.H
Sorry for my late answer.
It turns out that there was a misconfig on some of the NICs in Virtual Connect on the Blade center.
Regards
Thomas
02-08-2011 07:46 AM
Hi Thomas,
The B in port channe;l when LACP is configured is basically due to changes made in ether channel and also due to difference in config of the menber interfaces in ether channel.
Please check the logs if you are getting any error message.
Regards,
Swati
Please rate if you find content useful
02-08-2011 11:15 AM
Hi Thomas,
Have your issue solved yet??
can you please the check the algo that u r using for LACP. on both side is it src-dst-ip based on both the sides?
coz it cisco uses mac based by default please make cisco switch load-balacing to src-dst-ip based and see the same is configured on the HP also.
if you find this useful please rate me
thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide