Monday, March 15, 2010

Cisco IOS Load Balancing for Blue Coat SGOS

August 12, 2009 by Greg Ferro · 4 Comments 

A reg­u­lar ques­tion for Blue Coat is how to achieve high avail­ab­il­ity. One of the answers is use a load bal­an­cer, and most net­works already have a load bal­an­cer but don’t know about it.

The IOS Server Load Balancing (SLB) is good for most cases requir­ing load bal­an­cing and for load bal­an­cing two ProxySG makes an excel­lent solu­tion for small and medium networks.

Using Cisco IOS Load Balancer

This fea­ture seems to unknown to most net­work engin­eers. Cisco’s IOS has a SLB func­tion in cer­tain IOS images in IOS Modular Routers and Catalyst switches. I have used the fea­ture in the C6500 Supervisor sev­eral times and have been very happy with the results.

It doesn’t have a lot of the fea­tures that Cisco ACE or an F5 LTM load bal­an­cers will have but TCP or IP load bal­an­cing it works perfectly.

Performance

The IOS SLB fea­ture in the C6500 per­forms well in excess of 500 Megabits per second in my exper­i­ence on a Supervisor 720 at about 30% CPU util­isa­tion. This sug­gests that peak per­form­ance could be much higher. On a Supervisor II I have seen up to 200 Mbps at about 25% aver­age CPU, again imply­ing a much higher max­imum or peak rate.

Diagram

Configuration

Here is what the IOS con­fig­ur­a­tion looks like:


interface Vlan  11
ip address 192.168.1.254 255.255.255.0

interface Vlan 12
ip address 192.168.2.254 255.255.255.0

ip slb serverfarm SOPROXY
nat server
real 192.168.1.1
faildetect numconns 2
retry 15
inservice
!
real 192.168.1.2
faildetect numconns 2
retry 15
inservice
!
ip slb vserver SOWPAD
virtual 192.168.2.10 tcp www
serverfarm SOPROXY
idle 10
delay 5
inservice

And that is it. This is a simple load bal­an­cing con­fig­ur­a­tion for IP con­nec­tions. It will detect the fail­ure of Proxy server when a cer­tain num­ber of TCP SYNs fail to achieve a con­nec­tion and auto­mat­ic­ally dir­ect con­nec­tions to the other server(note: bad when installing and test­ing, but works fine in real life).

Protocol and Application Issues

You should note that the HTTP Protocol does not require state to be pre­served, its a state­less pro­tocol, and the Bluecoat ProxySG uses NTLM trans­par­ent authen­tic­a­tion so that when the user switch from one proxy to the other there is no loss of ser­vice. Hypothetically, the cach­ing on the ProxySG may not be optimal since the con­tent may not have been pre­vi­ously reques­ted through this unit, but this remains trans­par­ent to the user as the con­tent is auto­mat­ic­ally refreshed.

You can always weight the real serv­ers or you can con­fig­ure a ‘backup server’ con­fig­ur­a­tion to address this use case.

Lots of Options

You can find the full con­fig­ur­a­tion details at the Cisco web site where this is doc­u­mented in a lot of detail. This con­fig­ur­a­tion is very simple since it uses in-​​line ser­vice detec­tion. But I wanted to show you how easy it is to use IOS SLB. You don’t need to buy an F5 LTM or Cisco Application Control Engine for load bal­an­cing, about half the time some IOS Server Load Balancing is more than enough.

Go and do it.

Please rate this post:

  Why Rate Posts?
1 Star - It\\\'s Crud2 Stars - It\\\'s Tosh3 Stars - Something\\\'s missing4 Stars - Needs works5 Stars - Good Enough6 Stars - Good7 Stars - Excellent8 Stars - Brilliant9 Stars - Astonishing10 Stars - Awesomely Godlike? (5 votes, average: 9.60 out of 10)
Loading ... Loading ...

Comments

4 Responses to “Cisco IOS Load Balancing for Blue Coat SGOS”
  1. Ruairi says:

    Hey,

    I was just passing through your site (*cough* rub­ber duckie troubleshoot­ing method..) and I noticed this. Now if I remem­ber right, Bluecoat can speak WCCP, which might be a bet­ter approach to con­fig­ur­ing a cache farm. Config guide is here: http://​www​.cisco​.com/​e​n​/​U​S​/​d​o​c​s​/​i​o​s​/​1​2​_​2​/​c​o​n​f​i​g​f​u​n​/​c​o​n​f​i​g​u​r​a​t​i​o​n​/​g​u​i​d​e​/​f​c​f​0​1​8​_​p​s​1​8​3​5​_​T​S​D​_​P​r​o​d​u​c​t​s​_​C​o​n​f​i​g​u​r​a​t​i​o​n​_​G​u​i​d​e​_​C​h​apter.html .

    Of course, I’m sure you’re aware of this, and you needed to use IOS SLB for this :)
    /​Ruairi

    • Greg Ferro says:

      Hey, thanks for the com­ment. WCCP is for trans­par­ent redir­ec­tion and is not com­monly used in large com­pan­ies for vari­ous reas­ons. Mostly becuase it relies on a default route in the net­work to send traffic down to the point where the WCCP device can inter­cept traffic. If you aren’t /can’t use trans­par­ent redir­ec­tion then you need to use expli­cit mode. If you want expli­cit mode with active/​active for two or more units, then using IOS SLB is (mostly) per­fect. No need to waste money on load balancers.

      Does that help ?

  2. Charles says:

    Hello,
    please pay atten­tion that you need a license (FR-​​IOSSLB) for using the fea­ture. There is also an end-​​of-​​life announce­ment for this fea­ture (search for FR-​​IOSSLB on Cisco’s net­work site). Cisco appar­ently wants to move people to the ACE module.

    • Greg Ferro says:

      FR-​​IOSSLB is only needed if you are a Service Provider and using IOS-​​SLB to load bal­ance the fol­low­ing applic­a­tions. It is an advanced license upgrade (sim­ilar to Advanced SSL for VPN’s and so on).

      • Cisco Service Exchange Framework for Mobile (Mobile SEF) com­pon­ents:
       – Cisco Content Services Gateway (CSG)
       – Cisco Gateway GPRS Support Node (GGSN)
       – Cisco Packet Data Serving Node (PDSN)
       – Cisco Home Agents
      • Other com­pon­ents for mobile access

      I sus­pect that these advanced fea­tures will be mov­ing to the ACE but the stand­ard pro­tocol is unlikely to go away.

Speak Your Mind

Tell us what you're thinking...
and oh, if you want a pic to show with your comment, go get a gravatar!