Cabletron Systems SSR-GLX19-02, User Manual

Page: 292 / 495

Chapter 15: Configuring BGP on the SSR
292 CoreWatch User’s Manual
Ignore First AS Hop 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.
Set the Router as the Next hop
Router 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.
Show Warnings 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.
No Router ID in Aggregate
Attribute 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.
Always Send Keep-Alives This option instructs GateD to advertise routes
whose autonomous system paths are looped (i.e.
with an autonomous system appearing more than
once in the path) to version 3 external peers.
Note:
This option is ignored when set on internal
groups or peers.
Table 37. BGP Peer-Group options (Continued)
Option Description