Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cisco: NSP

Link aggregation question

 

 

Cisco nsp RSS feed   Index | Next | Previous | View Threaded


mike-cisconsplist at tiedyenetworks

May 28, 2012, 7:38 AM

Post #1 of 3 (298 views)
Permalink
Link aggregation question

Hello,

I have 2 3560's that have dual links between them. Each link is
100mbps and I want to aggregate the bandwidth and have failover as well.
From my read, most link aggregation will use mac addresses to hash and
determine which port to forward thru. I belive however I have the worst
case scenario since traffic IN will have 1500 different source macs but
1 destination, and traffic OUT will have 1 source mac and 1500
destination macs. Even worse, this traffic is PPPoE and not IP,
eliminating any sort of ip based selection criteria. This means, to my
read anyways, I would have course grained load sharing in 1 direction,
sort of defeating the point here. I was wondering if anyone had any
ideas for this platform and suggestions how I might get better
performance in this situation.

Thanks.

Mike-
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


philxor at gmail

May 28, 2012, 8:54 AM

Post #2 of 3 (282 views)
Permalink
Re: Link aggregation question [In reply to]

According to this doc you can set the switch to use dst mac, src mac, or a combination of the two on the 3560.

http://www.cisco.com/en/US/tech/tk389/tk213/technologies_tech_note09186a0080094714.shtml


On May 28, 2012, at 10:38 AM, Mike <mike-cisconsplist [at] tiedyenetworks> wrote:

> Hello,
>
> I have 2 3560's that have dual links between them. Each link is 100mbps and I want to aggregate the bandwidth and have failover as well. From my read, most link aggregation will use mac addresses to hash and determine which port to forward thru. I belive however I have the worst case scenario since traffic IN will have 1500 different source macs but 1 destination, and traffic OUT will have 1 source mac and 1500 destination macs. Even worse, this traffic is PPPoE and not IP, eliminating any sort of ip based selection criteria. This means, to my read anyways, I would have course grained load sharing in 1 direction, sort of defeating the point here. I was wondering if anyone had any ideas for this platform and suggestions how I might get better performance in this situation.
>
> Thanks.
>
> Mike-
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


peter at rathlev

May 28, 2012, 9:01 AM

Post #3 of 3 (278 views)
Permalink
Re: Link aggregation question [In reply to]

On Mon, 2012-05-28 at 07:38 -0700, Mike wrote:
> I have 2 3560's that have dual links between them. Each link is
> 100mbps and I want to aggregate the bandwidth and have failover as
> well. From my read, most link aggregation will use mac addresses to
> hash and determine which port to forward thru. I belive however I have
> the worst case scenario since traffic IN will have 1500 different
> source macs but 1 destination, and traffic OUT will have 1 source mac
> and 1500 destination macs.

Just use "port-channel load-balance src-mac" on one side "load-balance
dst-mac" on the other side.

--
Peter


_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Cisco nsp RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.