CPUG

The Check Point User Group

A Resource For The Check Point Community.  Fast.  Useful.  Independent.

1. CCSA/CCSE One-Week Dual-Certification Training Course with CPUG in San Francisco!
    Courses Starting 12/8, (2009) 1/19, 2/9, 3/9, 4/6, 5/4, 6/8, 7/6, 8/3.
2. Join Us On LinkedIn - We now have a CPUG group.


Go Back   CPUG: The Check Point User Group > Check Point Firewall-1/VPN-1 And Related Products > ISP Redundancy
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 2006-07-18
Member
 
Join Date: 2006-02-05
Posts: 74
Rep Power: 3
jmcgrady has an average reputation (10+)
Default ISP Redundancy vs BGP routers

I'm designing a firewall solution with two SPLAT checkpoint NGX firewalls connecting through two cisco routers to two ISPs. The client has asked for some traffic to be routed to ISP B and all other traffic to route to ISP A. I'm configuring BGP routing between all three parties.

I'm not sure if i will be able to selectively route without getting split routing on the return traffic. So i'm thinking of making ISP A the default for all traffic with ISP B as the backup (i will convince the client). I'm trying to decide whether i would be better off using Checkpoint's ISP redundancy. I dont like the idea of having to NAT all traffic, but the facility does look robust.

What do people here think? Is ISP redundancy a solid mechanism? Would it provide benefit in my case?
Reply With Quote
  #2 (permalink)  
Old 2006-07-19
Senior Member
 
Join Date: 2006-02-02
Posts: 204
Rep Power: 3
RobertGraham has an average reputation (10+)
Send a message via MSN to RobertGraham Send a message via Yahoo to RobertGraham
Default Re: ISP Redundancy vs BGP routers

I had to do this once, it was with Nokia devices on R53, so I didn't have the option of CheckPoint's ISP Redundancy at that time.

The result was that I had to resort to loading the full BGP table all 190000 entries then(no idea how big it is now). IMO, this is the only real professional and scalable way to do this. I contend that "ISP Redundancy" is an ugly kludge that shouldn't be used. This is my opinion and I'm sticking to it.

Why is that? Firewalls in contrast to routers don't work well with asymmetric routing(because of the state tables). This is what ISP Redundancy is trying to cover up. If you put a router in front that performs the routing without issue and keep the firewall ignorant of the whole thing, it's a much more resilient solution. There are also many benefits of BGP in and of itself, but that's left as further reading.

Regardless, you do have to consider the costs of BGP:

<> Powerful router to carry whole table with lots of RAM
<> BGP migration (planning, testing, downtime, etc)
<> Network admin versed in the arts of BGP to set it up
<> Network admin versed in the arts of BGP to maintain it


If you can afford the extra cost with a solid business case, definitely go for BGP. Otherwise, if you're on a small budget, you could try to get by with ISP Redundancy.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


All times are GMT -7. The time now is 09:44.


Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.2.0