Configuring BGP Peers

Gaia Embedded supports IPv4 addresses for BGP peers.

Syntax:

set bgp external remote-as <AS Number> peer <IP Address>

accept-med {off | on}

accept-routes {all | none}

authtype none

capability {default | ipv4-unicast}

graceful-restart-helper {off | on}

graceful-restart-helper-stalepath-time <Seconds>

holdtime <6-65535 | default>

ignore-first-ashop {off | on}

keepalive <2-21845 | default>

log-state-transitions {off | on}

log-warnings {off | on}

med-out <0-4294967294 | default>

multihop {off | on}

no-aggregator-id {off | on}

{off | on}

passive-tcp {off | on}

removeprivateas {off | on}

route-refresh {off | on}

send-keepalives {off | on}

send-route-refresh {request | route-update} {ipv4 | ipv6 | All} unicast

suppress-default-originate {off | on}

throttle-count <0-65535 | off>

trace <BGP Trace Option> {off | on}

ttl <1-255 | default>

Parameters:

Parameter	Description
`accept-med {off \| on}`	Specifies that MED be accepted from the specified peer address. If you do not enable this option, the MED is stripped from the advertisement before the update is added to the routing table.
`accept-routes <all \| none>`	Specifies an inbound BGP policy route if one is not already configured. `all` Accept routes and installing them with an invalid preference. Depending on the local inbound route policy, these routes are then made active or inactive. `none` Delete routes learned from a peer. This option saves memory overhead when many routes are rejected because no inbound policy exists.
`authtype none`	Specifies not to use an authentication scheme between peers. Using an authentication scheme guarantees that routing information is accepted only from trusted peers.
`capability {default \| ipv4-unicast}`	Specifies capabilities setting. Only IPv4 unicast is supported.
`graceful-restart-helper-stalepath-time <Seconds>`	Specifies the maximum amount of time that routes previously received from a restarting router are kept so that they can be revalidated. The timer is started after the peer sends an indication that it has recovered.
`graceful-restart-helper {off \| on}`	Specifies whether the Check Point system should maintain the forwarding state advertised by peer routers even when they restart to minimize the negative effects caused by peer routers restarting.
`holdtime <6-65535 \| default>`	Specifies the BGP holdtime interval, in seconds, when negotiating a connection with the specified peer. If the BGP speaker does not receive a keepalive update or notification message from its peer within the period specified in the holdtime field of the BGP open message, the BGP connection is closed. Range: 6-65535 seconds Default: 180 seconds
`ignore-first-ashop {off \| on}`	Specifies to ignore the first autonomous system number in the autonomous system path for routes learned from the corresponding peer. Set this option only if you are peering with a route server in transparent mode, that is, when the route server is configured to redistribute routes from multiple other autonomous systems without prepending its own autonomous system number.
`keepalive <2-21945 \| default>`	The keepalive option is an alternative way to specify a holdtime value in seconds when negotiating a connection with the specified peer. You can use the keepalive interval instead of the holdtime interval. You can also use both intervals, but the holdtime value must be 3 times the keepalive interval value. Range: 2-21945 seconds Default: 60 seconds
`log-state-transitions {off \| on}`	Specifies for the router to log a message whenever a peer enters or leave the established state.
`log-warnings {off \| on}`	Specifies for the router to log a message whenever a warning scenario is encountered in the codepath.
`med-out <0-4294967294 \| default>`	Specifies the multi-exit discriminator (MED) metric used as the primary metric on all routes sent to the specified peer address. This metric overrides the default metric on any metric specified by the redistribute policy. External peers uses MED values to decide which of the available entry points into an autonomous system is preferred. A lower MED value is preferred over a higher MED value. Range: 0-4294967294 Default: 4294967294
`multihop {off \| on}`	Enables multihop connections with external BGP peers more than one hop away. By default, external BGP peers are expected to be directly connected. This option can also be used for external load-balancing.
`no-aggregator-id {off \| on}`	Specifies the router's aggregate attribute as zero (rather than the router ID value). This option prevents different routers in an AS from creating aggregate routes with different AS paths.
`{off \| on}`	Disables (`off`) or enables (`on`) the configuration of the specified peer.
`passive-tcp {off \| on}`	Specifies for the router to wait for the specified peer to issue an open message. No TCP connections are initiated by the router.
`peer <IP Address>`	Specifies the peer for the group.
`remote-as <AS Number>`	Specifies the Autonomous System.
`removeprivateas {off \| on}`	Specifies that private AS numbers be removed from BGP update messages to external peers.
`route-refresh {off \| on}`	Re-learns routes previously sent by the BGP peer or refreshes the routing table of the peer. The peer responds to the message with the current routing table. Similarly, if a peer sends a route refresh request the current routing table is re-sent. A user can also trigger a route update without having to wait for a route refresh request from the peer.
`send-keepalives {off \| on}`	Specifies for this router always to send keepalive messages even when an update message is sufficient. This option allows interoperability with routers that do not strictly adhere to protocol specifications regarding updates.
`send-route-refresh {request \| route-update} {ipv4 \| ipv6 \| All} unicast`	Specifies that the router dynamically request BGP route updates from peers or respond to requests for BGP route updates.
`suppress-default-originate {off \| on}`	Specifies NOT to generate a default route when the peer receives a valid update from its peer.
`throttle-count <0-65535 \| off>`	Specifies number of BGP updates to send at one time. This option limits the number of BGP updates when there are many BGP peers. The value "`off`" disables the throttle count option.
`trace <BGP Trace Option> {off \| on}`	Specifies tracing options for your BGP implementation. Log messages are saved in the `var/log/routed/` directory. Enter the following words to set each trace option: `all` - to trace all the message types `general` - to trace message related to Route and Normal `keepalive` - to trace all the keepalive messages to this peer `normal` - to trace normal protocol occurrences (abnormal protocol occurrences are always traced) `open` - to trace all the BGP open messages to this peer `packets` - to trace all BGP packets to this peer `policy` - to trace application of the protocol and user-specified policy to routes being imported and exported. `route` - to trace routing table changes for routes installed by this peer `state` - to trace state machine transitions in the protocol `update` - to trace all the BGP update messages to this peer
`ttl <1-255 \| default>`	Specifies the value of the TTL (time to live) parameter, the number of hops over which the external BGP multihop session is established. Configure this value only if you enabled the "`multihop`" option. Range: 1-255 Default: 64