L3 Etherchannel (port-channel) Duplex and Speed ?

Lost & Found · ‎11-05-2015

Having some issues with out link configured as L3 etherchannel.

Please see the attached photo.

site A and B was configured as etherchannel. Before it was configured as halfduplex on both interfaces but it causing lots of collision and cause slow connection to other site.

According to our ISP they do not configured or support aggregation also the duplex and speed is set on auto.

so i tried to configured both routers as duplex full.

Result not Successful

Router (Left)

int f0/0/0 - up

int f0/0/1 - up

int port-channel-1 - up BW: 200000Kbit/sec

Router(Right)

int f0/0/0 - down

int f0/0/1 - down

int port-channel-1 - down

So I reconfigure it to duplex Auto

Router (Left)

int f0/0/0 - up BW 100000 Kbit

int f0/0/1 - up BW 100000 Kbit/sec

int port-channel-1 - up BW: 11000 Kbit/sec

show int port-channel 1

No. of active members in this channel: 2

Member 0 : FastEthernet0/0/0 , Full-duplex, 100Mb/s

Member 1 : FastEthernet0/0/1 , Full-duplex, 100Mb/s

Config:

interface Port-channel1

ip address 10.47.250.77 255.255.240.0

interface FastEthernet0/0/0

no ip address

duplex auto

speed auto

channel-group 1

interface FastEthernet0/0/1

no ip address

duplex auto

speed auto

channel-group 1

Router (Right)

int f0/0/0 - up

int f0/0/1 - up

int port-channel-1 - up BW: 200000 Kbit/sec

show int port-channel 1

No. of active members in this channel: 2

Member 0 : FastEthernet0/0/0 , Half-duplex, 100Mb/s

Member 1 : FastEthernet0/0/1 , Half-duplex, 100Mb/s

Config:

interface Port-channel1

ip address 10.47.250.77 255.255.240.0

interface FastEthernet0/0/0

no ip address

duplex auto

speed auto

channel-group 1

interface FastEthernet0/0/1

no ip address

duplex auto

speed auto

channel-group 1

They both have different bandwidth and duplex speed.

I've tried etherchannel over 802.1q. some feature doesnt support.

test(config-if)#channel-group 1 ?

<cr>

test(config-if)#channel-group 1

any idea?

thanks

ppalmerjr · ‎11-22-2015

If your provider does not support link aggregation then you other option would be to run a routing protocol (maybe OSPF) and run two L3 links. At least this way you would have a scenario where you would have traffic going over both links.

Lost & Found · ‎11-26-2015

Hi,

Is it okay to use l2 aggregation (lacp or pagp) on leased line?

thank you

Philip D'Ath · ‎11-26-2015

The "Ether" in Etherchannel is short for Ethernet, and as far as I am aware, only works on Ethernet style networks.

Leased line to me is a serial based service of some kind.

On serial style services take a look at using something like MPPP (Multilink PPP).

Lost & Found · ‎11-26-2015

I see. so i think I should use like hdlc ppp etc wanecap.

thanks for the info

Philip D'Ath · ‎11-22-2015

If the provider is supplying you a layer 2 service then they don't need to do anything for you to use Etherchannel. So it does not matter if they support it or not. You send them a layer 2 frame, they forward it - end of story.

Your first issue you need to resolve is the physical connectivity. Both ends of each link should be:

* fixed speed and fixed duplex; or

* auto/auto

It should either be fixed on both ends OR auto on both ends. If you are having to use a mix then your provider has configured something wrong on their end. This has nothing to do with channeling - this is basic physical connectivity.

Ask you provider if you should be using fixed "100/full" or "auto/auto" at each end of each link - and then use that same setting everwhere. If you then do a "show interface FastEthernet a/b/c" and it does not show as up/up then contact your service provider and report a fault. They have done something wrong. If you have it set to "auto/auto" and "show interface FastEthernet a/b/c" does not report it has auto-detected 100/full then contact your service provider and report a fault. they have done something wrong (or you have a cabling fault).

Once you have all the physical interfaces standing up using the same settings, turn your attention to Etherchannel - which will probbaly work correctly now because your physical connectivity has been sorted.