<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=662214003-19092007><FONT face=Arial size=2>Just wondering if
anyone has implemented radius load balancing before. </FONT></SPAN></DIV>
<DIV><SPAN class=662214003-19092007><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=662214003-19092007><FONT face=Arial size=2>This is our current
setup (note: I am trying to implement radius load balance in the ISP
cloud):</FONT></SPAN></DIV>
<DIV><SPAN class=662214003-19092007><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=662214003-19092007><FONT face=Arial size=2>Customer -->
[telco cloud] --> [(ISP cloud) LNS --> core-router --> [radius server
farm] ]</FONT></SPAN></DIV>
<DIV><SPAN class=662214003-19092007><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=662214003-19092007><FONT face=Arial size=2>We've applied the
IOS SLB config on the core-router and found that IOS SLB doesn't work in
our case because the "sticky" feature maps the LNS IP to a radius server, rather
than a customer's Framed-IP to a radius server (which is what we want to see
happen for radius auth/accounting packets).</FONT></SPAN></DIV>
<DIV><SPAN class=662214003-19092007><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=662214003-19092007><FONT face=Arial><FONT size=2>Next we tried
using Cisco's "load-balance method least-outstanding" config but this
meant we had to use an IOS train from the 12.2(28)SB or 12.4(11)T release. The
12.2(28)SB train was missing a command we needed to collect flow stats with and
the 12.4(11)T train appears to be giving us memory problems as seen
below.</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=662214003-19092007><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=662214003-19092007><FONT face=Arial size=2>*Sep 19 14:42:24.232
AEST: %SYS-2-MALLOCFAIL: Memory allocation of 65536 bytes failed from
0x6001C850, alignment 0<BR>Pool: Processor Free: 2425228 Cause:
Memory fragmentation<BR>Alternate Pool: None Free: 0 Cause: No
Alternate pool<BR> -Process= "BGP Router", ipl= 0, pid= 200,
-Traceback= 0x61159874 0x6000A7FC 0x600105F8 0x60010B64 0x6001C858 0x6001D780
0x6001D9B0 0x6188DA4C 0x6189865C 0x60D93D30 0x60D94550 0x60D95668 0x6296F7B8
0x60D95734 0x60D6EEF0 0x623E4250<BR>*Sep 19 14:42:24.324 AEST: %FIB-3-NOMEM:
Malloc Failure, disabling CEF, -Traceback= 0x61159874 0x6144CA44
0x61451E64 0x61459614 0x6145AD44 0x61475F28 0x618BD378
0x6188E120<BR></FONT></SPAN></DIV>
<DIV><SPAN class=662214003-19092007><FONT color=#0000ff><FONT face=Arial
color=#000000 size=2>Has anyone implemented radius load balancing from an ISP's
perspective and what did you end up using? It appears the cisco options don't
seem to be feasible in our situation.</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=662214003-19092007><FONT color=#0000ff><FONT face=Arial
color=#000000 size=2></FONT></FONT></SPAN> </DIV>
<DIV><SPAN class=662214003-19092007><FONT color=#0000ff><FONT face=Arial
color=#000000 size=2>Thanks</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=662214003-19092007><FONT color=#0000ff><FONT face=Arial
color=#000000 size=2></FONT></FONT></SPAN> </DIV>
<DIV><SPAN class=662214003-19092007><FONT color=#0000ff><FONT face=Arial
color=#000000 size=2>Andy</FONT></DIV></FONT></SPAN></BODY><!--[object_id=#staff.netspace.net.au#]--><P align=left><FONT face=Arial size=1>This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the organisation. Finally, the recipient should check this email and any attachments for the presence of viruses. The organisation accepts no liability for any damage caused by any virus transmitted by this email.</FONT></P></HTML>