From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] bgp require in multigateway routing
Date: Thu, 13 Dec 2007 17:09:40 +0000 [thread overview]
Message-ID: <47616754.2090105@riverviewtech.net> (raw)
In-Reply-To: <368077.76072.qm@web32515.mail.mud.yahoo.com>
On 12/13/07 08:12, sonu chouhan wrote:
> my isp doesn't support bgp, so i have a second chance to write a
> script for this, but my question is, if i run a script which will
> detect dead route and then delete that route, all is fine but after
> deleting route how can i know that this route is working again and
> need to add it again. plz help me and if you have any script like
> this plz provide me.
I think you will want to delete the route (or mark it dead) in your
(main?) routing table that gets used by most of your traffic and leave
additional administrative / test routing tables alone. With the
additional administrative / test routing tables you can have your test
traffic go out the routes that would otherwise not be used by your
normal traffic. Thus you can have test scripts see if the routes are
good or not. If the routes are good, you can re-add the routes to your
mail (?) routing table.
Another idea is to use different routing tables based on the connection
status. I.e. have main_both, main_isp_a, and main_isp_b routing tables
that are used for your normal traffic. If something happens, just
change the routing table that is used from main_both to main_isp_<that
is still up>. Changing which routing table is used is probably going to
be easier than altering a routing table.
Just to be clear, you will still want to have test_isp_a and test_isp_b
routing tables so you can direct your test traffic to use either
connection. So all in all, this route, you will have five routing
tables: main_both, main_isp_a, main_isp_b, test_isp_a, and test_isp_b.
Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-12-13 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 12:03 [LARTC] bgp require in multigateway routing sonu chouhan
2007-12-12 14:18 ` Radek 'Goblin' Pieczonka
2007-12-13 14:12 ` sonu chouhan
2007-12-13 17:09 ` Grant Taylor [this message]
2007-12-14 8:49 ` Nickola Kolev
2007-12-14 13:52 ` Manish Kathuria
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47616754.2090105@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.