Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) RIP route filters (P50/MAX1800)
Why not have the CISCO's run HSRP and if one fails over the other
one will become the default route, that way you can disable them
listening to RIP have them just sending RIP updates instead of
listening thus you don't need RIP filters.
Jason Nealis
Erols Internet
On Sun, 1 Feb 1998, S.T.Balbach wrote:
>
> Would like to filter routes. Specifically inbound RIP announcements.
>
> Is there any mechanism for filtering RIP routes with Ascend?
>
> Here is the scenario:
>
> [border cisco1] [border cisco2]
> | |
> | |
> ------------|--------------
> |
> [max18001]
> [max18002]
> [etc..]
>
>
> cisco1 is the default gateway, unless it goes down and then cisco2
> auto-falls over. Each cisco announces 0.0.0.0 via RIP, with cisco2
> announcing with a higher prefrence/metric --
>
> We only want the max1800's to listen to default and nothing else.
> otherwise the max1800 routing tables have unnecesary routes from the
> other 1800's which slows performance and reliability and cranks up CPU as
> the 1800's chatter back and forth.
>
> >From what Ive seen of the existing filters they only filter protocols, not
> routes. Is this correct? New feature perhaps (nudge)? Controlling route
> propegation is key.
>
> Stb
>
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd: <http://www.nealis.net/ascend/faq>
>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
Follow-Ups:
References: