[afnog] Internet Traffic distribution management

[Frank Kuse]

Hello Mark,
Currently we don't have capacity on our Core for STM64 and however having multiple STM16 also gives us good resilience.Our internet capacity is increasing everyday and even though we have plan to upgrade our core routers this year.We will still have the issues of dealing with two cable providers but multiple internet peers and having to load balance in this same manner and hence a solution hunt being pursued now.. 
Regards,
Frank

Subject: Re: [afnog] Internet Traffic distribution management
To: rombokite at hotmail.com; afnog at afnog.org
From: mark.tinka at seacom.mu
Date: Tue, 29 Sep 2015 10:55:12 +0200


  
    
  
  
    

    

    On 29/Sep/15 09:36, Frank Kuse wrote:

      

    
    
      
      
      Hello All,
        

        
        
          We currently do our Internet traffic load
            balancing by IP prefix preference to our internet peers.
          The AS for the same prefix is prepended a number
            of times on other links to serve as backup with the less
            preferred link given the highest number of prepend.
          

          
          The process above and determining the traffic
            utilization per prefix is manual and does not scale as we
            acquire more internet uplinks.
          

          
          Is there an automatic way of load balancing
            internet traffic per IP prefix on a number of internet links
            as our situation is?
        
      
    
    

    Are you talking about things like these:

    

       
    http://www.internap.com/network-services/ip-services/miro-controller/

    

    I've never used such a thing (and wouldn't ever), but I suspect
    you'll pay top-dollar for this.

    

    
      
        
          

          
          As it stands we have 8 uplinks with planning for
            two additional uplinks.
        
      
    
    

    Why so many upstreams?

    

    Mark.
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.afnog.org/pipermail/afnog/attachments/20150929/fa1412bc/attachment.html>