Cabletron Systems CoreWatch, Руководство пользователя

Страница: 283 / 495

CoreWatch User’s Manual 283
Chapter 15: Configuring BGP on the SSR
available options and their descriptions:
Table 35. Add Host to BGP Group options
Option Description
Ignore First AS Hop Specifying this option (here or on the Advanced tab
of either the BGP Peer Group Definition panel or
Add Host to Peer Group panel) tells GateD not to
drop routes from Route Servers (servers that are
able to propagate route without appending their
own autonomous system to the path).
Note:
This option should only be used if it is
positively known that the peer is a route
server and not a normal router.
Set the Router as the Next hop
Router Specifies that the next hop in route advertisements
for this peer or group of peers is to be this SSR, even
if it would normally be possible to send a third-
party next hop. This option may be useful in cases
that deal with broken bridged interconnect media
(in cases where the routers on the shared medium
do not really have full connectivity to each other) or
broken political situations.
Note:
This option may cause inefficient routes to
be followed. Cabletron recommends that
you use this option only for external groups.
Show Warnings This option instructs GateD to issue warning
messages when receiving questionable BGP updates
such as duplicate routes and/or non-existing route
deletions. Normally, these events are silently
ignored.
No Router ID in Aggregate
Attribute This option instructs GateD to specify the router
identification in the aggregate attribute to be 0
(instead of its router identification). This action
prevents different routers in an autonomous system
from creating aggregate routes with different
autonomous system paths.
Always Send Keep-Alives This option instructs GateD to consistently send
Keep-Alive messages, even when an update might
have been a viable substitute. This allows
interoperability with routers that do not completely
obey the protocol specifications on this point.