Important - Enabling multihop BGP connections is dangerous because BGP speakers might establish a BGP connection through a third-party AS. This can violate policy considerations and introduce forwarding loops.

Note - BGP route dampening is supported only for EBGP. It is not supported for IBGP.

Note - Not all fields are shown in all cases.

Router ID

The Router ID uniquely identifies the router in the autonomous system. The BGP and OSPF protocols use the router ID. Best Practice - set the router ID rather and rather then rely on the default setting. This prevents changes in the router ID if the interface used for the router ID goes down. Use an address on a loopback interface that is not the loopback address (127.0.0.1).

Note - In a cluster, you must select a router ID and make sure that it is the same on all cluster members.

• Range: Dotted-quad.([0-255].[0-255].[0-255].[0-255]). Do not use 0.0.0.0
• Default: The interface address of one of the local interfaces.

Cluster ID for Route Reflectors

The cluster ID used for route reflection. The default cluster ID is the router ID. You must override this default value if the cluster contains more than one route reflector.

Typically, a single router acts as the reflector for a set, or cluster, of clients. However, for redundancy two or more routers can also be configured as reflectors for the same cluster. In this case, you must select a cluster ID to identify all reflectors serving the cluster.

Gratuitous use of multiple redundant reflectors is not advised, for this situation can cause an increase in the memory required to store routes on the redundant reflectors peers.

• Range: Dotted-quad ([0-255].[0-255].[0-255].[0-255])
• Default: Router ID

Local Autonomous System Number

The local autonomous system number of the router.

Unconfigured

Local Autonomous System Number

The local autonomous system number of the router. This setting is mutually exclusive from the Confederation and Routing Domain Identifier. The router can be configured with either the autonomous system number or the member of confederation, not both.

Caution: When you change the autonomous system number, all current peer sessions are reset and all BGP routes are deleted.

• Range: 1-65535
• Default: No default

Confederation

The identifier for the entire confederation system. This identifier is used as the AS in external BGP sessions. To the outside world, the confederation ID is the AS number of the single, large AS. For this reason, the confederation ID must be a globally unique, normally assigned AS number.

• Range: 1-65535
• Default: No default

Number of loops permitted in AS_PATH

For the confederation: The number of times the local autonomous system can appear in an AS path for BGP-learned routes. If the number of times the local autonomous system appears in an AS path is more than the number in this field, the corresponding routes are discarded or rejected.

• Range: 1-10
• Default: 1

Routing Domain Identifier

The routing domain identifier (RDI) of this router. This value is required only if BGP confederations are in use. The RDI does not have to be globally unique since it is never used outside the domain of the confederation system. However, the configured RDI must be unique within the confederation. The routing-domain identifier and autonomous system number are mutually exclusive values; that is, the router can be configured with either the autonomous system number or the member of confederation, not both. If confederations are in use, the RDI is used wherever the autonomous system would be used to communicate with peers within the confederation, including group-type confederation peers and the various internal-type peers. For correct operation of the router in confederations you must configure both the routing-domain identifier and the confederation.

• Range: 1-65535
• Default: No default

Number of loops permitted in AS_PATH

For the routing domain identifier: The number of times the local autonomous system can appear in an AS path for BGP-learned routes. If the number of times the local autonomous system appears in an AS path is more than the number in this field, the corresponding routes are discarded or rejected.

• Range: 1-10
• Default: 1

Default MED

Defines the metric (MED) used when advertising routes through BGP. If you do not specify a value, no metric is propagated. A metric specified on the neighbor configuration or in the redistribution configuration might override the metric you configure.

• Range: 0-65535

Default Gateway:

A default route is generated when any BGP peer is up. This route has a higher rank than the default configured in the static routing page. If a specific BGP peer should not be considered for generating the default route, you should explicitly suppress the option in the peer-specific configuration.

• Range: Dotted-quad ([0-255].[0-255].[0-255].[0-255]).
• No Default.

Enable IGP Synchronization

Select this option to make internal and configured BGP peers check for a matching route from IGP protocols before installing a given route.

• Default: Unselected

Enable communities

Enables communities-based policy options.

• Default: Unselected

Enable Weighted Route Dampening

Weighted route dampening minimizes the propagation of flapping routes across an internetwork. A route is considered to be flapping when it is repeatedly transitioning from available to unavailable or vice versa. Only routes learned through BGP are subjected to weighted route dampening.

Note: BGP route dampening is only supported for External BGP (EBGP).

When this option is selected, the other Route Dampening fields show.

Reuse-below metric

The value of the instability metric at which a suppressed route becomes unsuppressed if it is reachable but currently suppressed. The value assigned to the reuse-below metric must be less than the suppress-above value.

• Range: 1-32
• Default: 2

Suppress-above metric

The value of the instability metric at which a route is suppressed; a route is not installed in the FIB or announced even if it is reachable during the period that it is suppressed.

• Range: 2-32
• Default: 3

Max-flap metric

The upper limit of the instability. The value must be higher than one plus the suppress-above value. The metric assigned to the suppress-above, reuse-below, and max-flap metric values is a floating point number, in units of flaps. Each time a route becomes unreachable, one is added to the current instability metric.

• Range: 3-64
• Default: 16

Reachable decay time

A value that determines the length of time it takes for the instability metric value to reach one half of its current value when the route is reachable. This half-life value determines the rate at which the metric value is decayed. A smaller half-life value makes a suppressed route reusable sooner than a larger value.

• Range: 1-900
• Default: 300

Unreachable decay time

The rate at which the instability metric is decayed when a route is unreachable. This value must be equal to or greater than the reach-decay value.

• Range: 1-2700
• Default: 900

Keep history time

The period over which the route flapping history is maintained for a given route. The size of the configuration arrays described below is directly affected by this value.

• Range: 2-5400
• Default: 1800

Peer

IP address of the peer.

Peer Type

Configure whether or not the peer router is a reflector client of the local router.

• Range:
  • Reflector Client: The peer router is a reflector client.
  • None: The peer router is not a reflector client.
  • No Client Reflector: An advanced option.
• Default: None

Outgoing interface

IPv6 peer with FE80: local address only: All peer interfaces have a local address and a global address. All the peer interfaces can have the same local address, which starts with FE80:. To use the local address, you must specify the outgoing interface for the local address.

Comment

A free-text description of the peer.

IPv4 Unicast Only

Only IPv4 unicast routes can be sent to and received from this peer.

• Default: Selected

IPv6 Unicast Only

Only IPv6 unicast routes can be sent to and received from this peer.

• Default: Cleared

Both IPv4 and IPv6

IPv4 and IPv6 unicast routes can be sent to and received from this peer.

• Default: Cleared

Local Address

The address used on the local end of the TCP connection with the peer. For external peers that do not have multihop enabled, the local address must be
on an interface that is shared with the peer or with the peer's gateway when the gateway parameter is used. A session with an external peer is opened only when an interface with a local address through which the peer or gateway address is directly reachable is operating.

For other types of peers, a peer session is maintained when any interface with the specified local address is operating. In either case, incoming connections are recognized as matching a configured peer only if they are addressed to the configured local address.

Note: If running BGP in a cluster you must not configure the local address.

Default: None

Weight

The default weight associated with each route accepted from this peer. This value can be overridden by the weight specified in the import policy.

• Range: 0-65535

Accept MED from External Peer

MED should be accepted from this external neighbor. MEDs are always accepted from routing-type and confederation neighbors. If this parameter is not used with an external neighbor, the MED is stripped before the update is added to the routing table. If this parameter is added or deleted and routed is reconfigured, the affected peering sessions are automatically restarted.

• Default: Cleared

MED Sent Out

The primary metric used on all routes sent to the specified peer. This metric overrides the default metric on any route specified by the redistribute policy.

• Range: 0-4294967294
• Default: 4294967294

EBGP Multihop

Enable multihop connections with external BGP (EBGP) peers that are not directly connected. By default, external BGP peers are expected to be directly connected. You can refine the multihop session by configuring the Time to Live (TTL), that is, the number of hops to the EBGP peer. This option can also be used to set up peers for EBGP load balancing.

• Default: Cleared

Time to Live

Use the TTL (Time to Live) parameter to limit the number of hops over which the External BGP (EBGP) multihop session is established. You can configure the TTL only if EBGP multihop is enabled. The default TTL is 64. When multihop is disabled the default TTL is 1.

• Range: 1-255
• Default: 64

No Aggregator ID

Select to force this router to specify the router ID in the aggregator attribute as zero, rather than the actual router ID. This option prevents different routers in an AS from creating aggregate routes with different AS paths.

• Default: Cleared

ASPATH prepend count

The number of times this router adds to the AS path on EBGP external or CBGP confederation sessions. Use this setting to bias the degree of preference some downstream routers have for the routes originated by this router. Some implementations prefer to select routes with shorter AS paths. This parameter has no effect when used with IBGP peers.

• Range: 1-25
• Default: 1

Remove Private AS

Remove private AS numbers from the outgoing updates to this peer. Following conditions apply when this feature is enabled:

• If the AS path includes both public and private AS numbers, private AS numbers will not be removed.
• If the AS path contains the AS number of the destination peer, private AS numbers will not be removed.
• If the AS path contains only confederations and private AS numbers, private AS numbers will be removed.

• Default: Cleared

Keep Alive Timer

An alternative way to specify a Hold Time value, in seconds, to use when negotiating the connection with this peer. The keepalive interval equals one-third the value of the holdtime. The keepalive interval is often used instead of the holdtime value, but you can specify both values, provided the value for the holdtime is three times the keepalive interval. The value must be 0, that is, no keepalives are sent, or at least 2.

• Range: 0, 2-21845
• Default: 60

Hold Time

The BGP holdtime value, in seconds, to use when negotiating a connection with this peer. According to the specification, if the BGP speaker does not receive a keepalive update or notification message from its peer within the period specified by the holdtime value in the BGP Open message, the BGP connection is closed. The value must be either 0, that is, no keepalives are sent, or at least 6.

• Range: 0, 6-65535
• Default: 180

Ignore First AS Hop

Select to force this router to ignore the first AS number in the AS_PATH for routes learned from the corresponding peer. Select this option only if you are peering with a route server in so-called transparent mode, that is, when the route server is configured to redistribute routes from multiple ASs without prepending its own AS number.

• Default: Cleared

Keep Alive Always

Select to force this router always to send keepalives even when an update can substitute. This setting allows interoperability with routers that do not completely adhere to the protocol specifications on this point.

• Default: Cleared

Accept Routes Received From the Peer

Routes received from peer routes are accepted if there is an inbound BGP route policy. If an inbound policy to accept the route does not exist, you can select All or None.

• All - Specifies to accept and install routes with an invalid preference. Depending on the local BGP inbound policy the routes could become active or inactive.
• None - Specifies to delete routes learned from a peer when no explicit local BGP inbound policy exists. This option is used to save memory overhead when many routes are rejected because there is no local policy. These routes can be relearned only by restarting the BGP session.

• Default: All

Passive

Select to force this router to wait for the peer to issue an open. By default all explicitly configured peers are active and periodically send open messages until the peer responds. Modifying this option will reset the peer connection.

• Default: Cleared

Authentication type

The type of authentication scheme to use between given peers. In general peers must agree on the authentication configuration to form peer adjacencies. This feature guarantees that routing information is accepted only from trusted peers. If the Auth type selected is TCP MD5 the Password field appears. When you enter a password, TCP MD5 authentication is used with the given peer.

Note - TCP MD5 is not supported on BGP IPv6 peers.

• Options: None / MD5
• Default: None

Throttle count

Throttles the network traffic when there are many BGP peers. Throttle count determines the number of BGP updates sent at a time.

• Range: 0-65535
• Default: No default

Route Refresh

Route refresh is used to either re-learn routes from the BGP peer or to refresh the routing table of the peer without tearing down the BGP session. Both peers must support the BGP route refresh capability and should have advertised this at the time peering was established.

Re-learning of routes previously sent by the peer is accomplished by sending a BGP route refresh message. 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.

You can also trigger a route update without having to wait for a route refresh request from the peer.

Both peers must support the same address and subsequent address families. For example a request for IPv6 unicast routes from a peer that did not advertise the capability during session establishment will be ignored.

Note: Clicking a Route Refresh button sends a trigger to the routing daemon. It does not change the configuration of the router.

Helper

Routes received from peer are preserved if the peer goes down till either the session is re-established (OPEN message is received from the peer after it comes back up) or the graceful restart timer expires.

• Default: Cleared

Stalepath Time

Maximal time for which routes previously received from a restarting router are kept unless they are re-validated. The timer is started after the peer sends indication that it is up again.

• Range: 60 - 65535
• Default: 360

Log bgp peer transitions

Select to force this router to log a message whenever a BGP peer enters or leaves the ESTABLISHED state.

• Default: Cleared

Log warnings

Select to force this router to log a message whenever a warning scenario is encountered in the codepath.

• Default: Cleared

Peer AS Number

The autonomous system number of the external peer group. Enter an integer from 1-65535.

Peer Group Type

One of

• Unconfigured
• Local Autonomous System Number
• Confederation

Description

A free-text description of the peer group.

Local address

The address used on the local end of the TCP connection with the peer. For external peers that do not have multihop enabled, the local address must be on an interface that is shared with the peer or with the peer's gateway, when the gateway parameter is used. A session with an external peer opens only when an interface with a local address through which you can reach the peer or gateway address directly operates.

For other types of peers, a peer session opens when an interface with the specified local address operates. In both external and other types of peers, incoming connections are recognized as matching a configured peer only if they are addressed to the configured local address.

Note - If you run BGP in a cluster, you must not configure the local address.

• Default: None

Out Delay

The length of time in seconds that a route must be present in the routing database before it is redistributed to BGP. This value applies to all neighbors configured in this group. The default value is zero, which means that this feature is disabled. This feature dampens route fluctuations.

• Range: 0-65535
• Default: 0

Peer

Configure peers. Each peer inherits as defaults all parameters configured on a group. To change the values of a peer's parameters, select the peer and click Edit.

set bgp external remote-as as_number

	<on | off>

	aspath-prepend-count <1-25 | default>

	description text

	local-address ip_address <on | off>

	outdelay <0-65535>

	outdelay off

as_number <on | off>

The autonomous system number of the external peer group. Enter an integer from 1‑65535.

aspath-prepend-count <1-25 | default>

The number of times this router adds to the autonomous system path on external BGP sessions. Use this option to bias the degree of preference some downstream routers have for the routes originated by this router. Some implementations prefer to select paths with shorter autonomous system paths. Default is 1.

description text

You can enter a brief text description of the group.

local-address ip_address <on | off>

The address used on the local end of the TCP connection with the peer. For external peers that do not have multihop enabled, the local address must be
on an interface that is shared with the peer or with the peer's gateway when the gateway parameter is used. A session with an external peer is opened only when an interface with a local address through which the peer or gateway address is directly reachable is operating.

For other types of peers, a peer session is maintained when any interface with the specified local address is operating. In either case, incoming connections are recognized as matching a configured peer only if they are addressed to the configured local address.

Note: If running BGP in a cluster you must not configure the local address.

Default: Off

outdelay <0-65535>

The amount of time in seconds that a route must be present in the routing database before it is redistributed to BGP. The configured value applies to all peers configured in this group. This feature dampens route fluctuation. The value zero (0) disables this feature.

Default: 0

outdelay off

Disables outdelay.

set bgp external remote-as <as_number> peer <ip_address>

	<on | off>

	med-out <0—4294967294 | default>

	outgoing-interface <interface> <on | off>

	accept-med <on | off>

	multihop <on | off>

	ttl <1-255 | default>

	no-aggregator-id <on | off>

	holdtime <6—65535 | default>

	keepalive <2—21845 | default>

	ignore-first-ashop <on | off>

	send-keepalives <on | off>

	send-route-refresh [request|route-update][ipv4 | ipv6 | All] [unicast]

	route-refresh <on | off>

	accept-routes <all | none>

	passive-tcp <on | off>

	removeprivateas <on | off>

	authtype none

	authtype md5 secret secret

	throttle-count <0—65535 | off>

	suppress-default-originate <on | off>

	log-state-transitions <on | off>

	log-warnings <on | off>

	trace bgp_traceoption <on | off>

	capability <default | ipv4-unicast | ipv6-unicast>

	graceful-restart-helper <on | off>

	graceful-restart-helper-stalepath-time seconds

ip_address <on | off>

A specific peer <ip_address> for the group.

med-out <0-4294967294 | default>

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 use 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.

Default: 4294967294

outgoing-interface <interface> <on | off>

IPv6 peer with FE80: local address only: All peer interfaces have a local address and a global address. All the peer interfaces can have the same local address, which starts with FE80:. To use the local address, you must specify the outgoing interface for the local address.

accept-med <on | off>

Accept MED from the specified peer address. If you do not set this option, the MED is stripped from the advertisement before the update is added to the routing table.

multihop <on | off>

Enable multihop connections with external BGP (EBGP) peers that are not directly connected. By default, external BGP peers are expected to be directly connected. You can refine the multihop session by configuring the Time to Live (TTL), that is, the number of hops to the EBGP peer. This option can also be used to set up peers for EBGP load balancing.

Default: Off

ttl <1-255 | default>

Use the TTL (Time to Live) parameter to limit the number of hops over which the External BGP (EBGP) multihop session is established. You can configure the TTL only if EBGP multihop is enabled. The default TTL is 64. When multihop is disabled the default TTL is 1.

Default: 64

no-aggregator-id <on | off>

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.

holdtime <6-65535 | default>

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.

Default: 180 seconds

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.

Default: 60 seconds

ignore-first-ashop <on | off>

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.

send-keepalives <on | off>

This router always sends 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]

The router dynamically request BGP route updates from peers or respond to requests for BGP route updates.

route-refresh <on | off>

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.

accept-routes <all | none>

An inbound BGP policy route if one is not already configured.

Enter all to specify accepting routes and installing them with an invalid preference. Depending on the local inbound route policy, these routes are then made active or inactive.

Enter none to delete routes learned from a peer. This option saves memory overhead when many routes are rejected because no inbound policy exists.

passive-tcp <on | off>

The router waits for the specified peer to issue an open message. No tcp connections are initiated by the router.

removeprivateas <on | off>

Remove private AS numbers from BGP update messages to external peers.

authtype none

Do not use an authentication scheme between peers. Using an authentication scheme guarantees that routing information is accepted only from trusted peers.

Default: none

authtype md5 secret secret

Use md5 authentication between peers. In general, peers must agree on the authentication configuration to and from peer adjacencies. Using an authentication scheme guarantees that routing information is accepted only from trusted peers.

Note - TCP MD5 is not supported on BGP IPv6 peers.

throttle-count <0-65535 | off>

The number of BGP updates to send at one time. This option limits the number of BGP updates when there are many BGP peers. Off disables the throttle count option.

suppress-default-originate <on | off>

Do NOT to generate a default route when the peer receives a valid update from its peer.

log-state-transitions <on | off>

The router generates a log message whenever a peer enters or leave the established state.

log-warnings <on | off>

The router generates a log message whenever a warning scenario is encountered in the codepath.

trace bgp_traceoption <on | off>

Tracing options for the BGP implementation. Log messages are saved in the /var/log/routed.log.* files. See Configuring Trace Options - Gaia Clish.

capability <default | ipv4-unicast | ipv6-unicast>

On each peer, configure the type of routes (Multiprotocol capability) to exchange between peers. Choose one of these:

• IPv4 Unicast Only (the default)
• IPv6 Unicast Only
• Both IPv4 and IPv6

For peering to be established, the routers must share a capability.

graceful-restart-helper <on | off>

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.

graceful-restart-helper-stalepath-time seconds

The maximal 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.

set bgp

	confederation identifier as_number

	confederation identifier off

	confederation aspath‑loops‑permitted <1‑10>

	confederation aspath‑loops‑permitted default

	routing‑domain identifier as_number

	routing‑domain identifier off

	routing‑domain aspath‑loops‑permitted <1‑10>

	routing‑domain aspath‑loops‑permitted default

	synchronization <on | off>

confederation identifier as_number

Specifies the identifier for the entire confederation. This identifier is used as the autonomous system number in external BGP sessions. Outside the confederation, the confederation id is the autonomous system number of a single, large autonomous system. Thus the confederation id must be a globally unique, typically assigned autonomous system number.

confederation identifier off

Disables the confederation identifier.

confederation aspath‑loops permitted <1‑10>

Specifies the number of times the local autonomous system can appear in an autonomous system path for BGP‑learned routes. If this number is higher than the number of times the local autonomous system appears in an autonomous system path, the corresponding routes are discarded or rejected.

confederation aspath loops‑permitted default

Specifies a value of 1.

routing‑domain identifier as_number

Specifies the routing domain identifier (RDI) for this router. You must specify the RDI if you are using BGP confederations. The RDI does not need to be globally unique since it is used only within the domain of the confederation.

routing‑domain identifier off

Disables the routing‑domain identifier.

routing‑domain aspath‑loops‑permitted <1‑10>

Specifies the number of times the local autonomous system can appear in an autonomous system path for BGP‑learned routes. If this number is higher than the number of times the local autonomous system appears in an autonomous system path, the corresponding routes are discarded or rejected.

routing‑domain aspath‑loops‑permitted default

Specifies a value of 1.

synchronization <on | off>

Enables IGP synchronization. Set this option On to cause internal and confederation BGP peers to check for a matching route from IGP protocol before installing a BGP learned route.

Note - The IP address of a peer can be an IPv4 or an IPv6 address.

set bgp confederation member-as <as_id>

	[on|off]

	description [off|<description>]

	interface <int> [off|on]

	local-address <IP_addr> [off|on]

med [default|<value>]
nexthop-self [off|on]
outdelay [off|<delay>]
peer <IP_addr> [off|on]
protocol [all|bgp|direct|rip|static|ospf|ospfase]
peer <IP_addr> accept-routes [all|none]
peer <IP_addr> authtype [none|md5 secret <passwd>]
peer <IP_addr> capability [ipv4-unicast|ipv6-unicast] [off|on]
peer <IP_addr> graceful-restart [off|on]
peer <IP_addr> graceful-restart-stalepath-time [default|<time>]
peer <IP_addr> holdtime [default|<time>]
peer <IP_addr> ignore-first-ashop [off|on]
peer <IP_addr> keepalive [default|<time>]
peer <IP_addr> local-address <local_IP_addr> [off|on]
peer <IP_addr> log-state-transitions [off|on]
peer <IP_addr> log-warnings [off|on]
peer <IP_addr> no-aggregator-id [off|on]
peer <IP_addr> outgoing-interface <int> [off|on]
peer <IP_addr> passive-tcp [off|on]
peer <IP_addr> peer-type [none|reflector-client|no-client-reflector] [off|on]
peer <IP_addr> ping [off|on]
peer <IP_addr> route-refresh [off|on]
peer <IP_addr> send-keepalives [off|on]
peer <IP_addr> send-route-refresh request [all|ipv4|ipv6] unicast
peer <IP_addr> send-route-refresh route-update [all|ipv4|ipv6] unicast
peer <IP_addr> throttle-count [off|<count>]
peer <IP_addr> trace [keepalive|open|packets|update|all|general|normal|policy|route|state| task|timer] [off|on]
peer <IP_addr> weight <weight>
peer <IP_addr> comment <comment>

<on|off>

Creates (on) or removes (off) a peer group with AS id <as_id>.

description [off|<description>]

Sets the peer group description to <description>, or turns off the description (off).

interface <int> [off|on]

Sets a gateway interface (<int>: eth1, eth2, etc.) as the peer group interface, and turns it on or off.

local-address <IP_addr> [off|on]

Sets a peer group with an IP address on the local gateway.

med [default|<value>]

Sets the peer group local Multi-Exit Discriminator. The default is 0.

nexthop-self [off|on]

Sets (on) or removes (off) the local gateway as the default exit gateway for the peer group.

outdelay [off|<delay>]

Sets or removes the out-delay value (in seconds). Set this value to enforce rate limiting.

peer <IP_addr> [off|on]

Creates a peer group with the specified gateway (<IP_addr>).

protocol [all|bgp|direct|rip|static|ospf|ospfase]

Set an internal peer group protocol.

peer <IP_addr> accept-routes [all|none]

peer <IP_addr> authtype [none|md5 secret <passwd>]

Set peer authentication between the local gateway and the specified peer gateway (<IP_addr>). You can set it to MD5 and specify the password (<passwd>), or you can turn it off (none).

peer <IP_addr> capability [ipv4-unicast|ipv6-unicast] [off|on]

Configure peer multiprotocol capabilities (ipv4-unicast or ipv6-unicast) with the specified peer (<IP_addr>). Turn these on or off, if necessary.

peer <IP_addr> graceful-restart [off|on]

Turn graceful restart on and off between the local gateway and the specified peer (<IP_addr>).

peer <IP_addr> graceful-restart-stalepath-time [default|<time>]

Set graceful restart stalepath time (in seconds) with the specified peer (<IP_addr>).

peer <IP_addr> holdtime [default|<time>]

Set the maximum amount of time (in seconds) that can elapse between messages from the specified peer (<IP_addr>).

peer <IP_addr> ignore-first-ashop [off|on]

peer <IP_addr> keepalive [default|<time>]

Set the keepalive timer (in seconds) for the specified peer (<IP_addr>). The default is

peer <IP_addr> local-address <local_IP_addr> [off|on]

Sets a local IP address (<local_IP_addr>) for the specified peer (<IP_addr>).

peer <IP_addr> log-state-transitions [off|on]

Turns logging of peer state transitions on or off for the specified peer (<IP_addr>).

peer <IP_addr> log-warnings [off|on]

Turns logging of warnings on or off for the specified peer (<IP_addr>).

peer <IP_addr> no-aggregator-id [off|on]

Sets the specified peer (<IP_addr>) to not aggregate AS routes (on). If set to off, the peer will create aggregate routes.

peer <IP_addr> outgoing-interface <int> [off|on]

Sets a specific outgoing interface (<int>) to the specified peer (<IP_addr>).

peer <IP_addr> passive-tcp [off|on]

Sets peer passive behavior. If on, the gateway does not initialize connections to the specified remote peer (<IP_addr>). The default is off.

peer <IP_addr> peer-type [none|reflector-client|no-client-reflector] [off|on]

Sets the local gateway's peer type in the relation to the specified peer (<IP_addr>). The default is

peer <IP_addr> ping [off|on]

Sets ping capability between the local gateway and the specified peer (<IP_addr>). The default is

peer <IP_addr> route-refresh [off|on]

Sets route refresh capability between the local gateway and the specified peer (<IP_addr>). The default is

peer <IP_addr> send-keepalives [off|on]

Sets the gateway to always send keepalive messages to the specified peer (<IP_addr>). The default is

peer <IP_addr> send-route-refresh request [all|ipv4|ipv6] unicast

Sets the local gateway to request BGP route updates from the specified peer (<IP_addr>).

peer <IP_addr> send-route-refresh route-update [all|ipv4|ipv6] unicast

Sets the local gateway to respond to requests for BGP route updates from the specified peer (<IP_addr>).

peer <IP_addr> throttle-count [off|<count>]

Sets the maximum number of BGP updates that can be sent at one time tot he specified peer (<IP_addr>). The range for the <count> is 0-65535. The default is

peer <IP_addr> trace [keepalive|open|packets|update|all|general|normal|policy|route|state| task|timer] [off|on]

Sets the types of packets to trace from the specified peer (<IP_addr>).

peer <IP_addr> weight <weight>

Sets the weight for the specified peer (<IP_addr>). The value range for the <weight> is 0-65535.

peer <IP_addr> comment <comment>

Sets a comment associated with the specified peer (<IP_addr>).

internal peer <peer ip_address>
peer-type reflector-client

The peer router <peer ip_address> is a reflector client of the local router.

internal peer <peer ip_address>
peer-type none

The peer router <peer ip_address> is not a reflector client of the local router. This is the default.

internal peer <peer ip_address>
peer-type no-client-reflector

An advanced option.

cluster-id ip_address

The cluster ID used for route reflection. The cluster ID default is that of the router id. Override the default if the cluster has more than one route reflector

cluster-id off

Disable the cluster ID.

default-med <0-65535>

The multi-exit discriminator (MED) metric used to advertise routes through BGP.

default-med off

Disable the specified MED metric.

default-route-gateway ip_address

The default route. This route has a higher rank than any configured default static route for this router. If you do not want a BGP peer considered for generating the default route, use the peer <ip_address> suppress-default-originate on command.

default-route-gateway off

Disables the configured default BGP route.

<on | off>

Specifies whether to enable or disable BGP route dampening.

suppress-above <2-32>

Specifies the value of the instability metric at which route suppression takes place. A route is not installed in the forwarding table or announced even if it reachable during the period that it is suppressed.

suppress-above default

Specifies an instability metric value for suppressing routes of 3.

reuse-below metric <1-32>

Specifies the value of the instability metric at which a suppressed route becomes unsuppressed if it is reachable but currently suppressed. The value assigned to the reuse-below metric must be lower than the suppress-above value.

reuse-below metric default

Specifies an instability metric value for announcing previously suppressed routes of 2.

max-flap <3-64>

Specifies the upper limit of the instability metric. The value must be greater than the suppress-above value plus 1. Each time a route becomes unreachable, 1 is added to the current instability metric.

max-flat default

Specifies the upper limit of the instability metric as 16.

reachable-decay <1-900>

Specifies the time for the instability metric to reach half of its value when the route is reachable. The smaller the value the sooner a suppressed route becomes reusable.

reachable-decay default

Specifies a value of 300.

unreachable-decay <1-2700>

Specifies the time for the instability metric to reach half its value when the route is NOT reachable. The value must be equal to or higher than the reachable-decay value.

unreachable-decay default

Specifies a value of 900

keep-history <2-5400>

Specifies the period for which route flapping history is maintained for a given route.

keep-history default

Specifies a value of 1800.

set bgp internal

   <on | off>

   description text

   med <0-65535>

   med default

   outdelay <0-65535>

   outdelay off

   nexthop-self <on | off>

   local-address ip_address <on | off>

   interface [all | if_name] <on | off>

   protocol [all | bgp_internal_protocol] <on | off>

   graceful-restart-helper  <on | off>

   graceful-restart-helper-stalepath-time seconds

   route-refresh <on | off>

set bgp internal peer <ip_address> 

   peer_type <on | off>

   weight <0-65535>

   weight off

   no-aggregator id <on | off>

   holdtime <6-65535>

   holdtime default

   keepalive <2-21845>

   keepalive default

   ignore-first-ashop <on | off>

   send-keepalives <on | off>

   send-route-refresh [request | route-update] [ipv4|ipv6|All] [unicast]

   accept-routes all

   accept-routes none

   passive-tcp <on | off>

   authtype none

   authtype md5 secret secret

   throttle-count <0-65535>

   throttle count off

   log-state-transitions <on | off>

   log-warnings <on | off>

   trace bgp_traceoption <on | off>

<on | off>

Enable or disable an internal BGP group.

description text

Optional: A brief text description of the group.

med <0-65535>

med default

outdelay <0-65535>

The amount of time in seconds that a route must be present in the
routing database before it is redistributed to BGP. The configured value
applies to all peers configured in this group. This feature dampens route
fluctuation. Zero (0), which means that this feature is disabled.

Default: 0

outdelay off

Disables outdelay.

nexthop-self
on | off>

This router sends one of its own IP addresses as the BGP next hop.

Default: off

local-address
ip_address <on | off>

The address used on the local end of the TCP connection with the peer. For external peers that do not have multihop enabled, the local address must be
on an interface that is shared with the peer or with the peer's gateway when the gateway parameter is used. A session with an external peer is opened only when an interface with a local address through which the peer or gateway address is directly reachable is operating.

For other types of peers, a peer session is maintained when any interface with the specified local address is operating. In either case, incoming connections are recognized as matching a configured peer only if they are addressed to the configured local address.

Note: If running BGP in a cluster you must not configure the local address.

Default: Off

interface [all |
if_name] <on | off>

Enable or disable the specified internal peer group on all interfaces or a specific interface.

protocol [all
bgp_internal_protocol] <on | off>

Enable or disable all internal routing protocols on the specified internal peer group or specific internal protocols. You can enter the following specific internal protocols: direct, rip, static, ospf, and ospfase.

peer ip_address
peer_type <on | off>

An internal peer address and peer type. Enter reflector-client to specify that the local router acts as a route reflector for the group of peers named. That is, the local router is the route reflection server, and the named peers are route reflection clients. Normally, the routing daemon readvertises, or reflects, routes it receives from one of its clients to all other IBGP peers, including the other peers in that client's group.
Enter no-client-reflector to specify that a reflection client's routes are reflected only to internal BGP peers in other groups. Clients in the group are assumed to be direct IBGP peers of each other.
Enter none if you do not want to specify route reflection.

peer_ip_address weight
<0-65535>

The weight associated with the specified peer. BGP implicitly stores any rejected routes by not mentioning them in a route filter. BGP explicitly mentions them within the routing table by using a restrict keyword with a negative weight. A negative weight prevents a route from becoming active, which prevents it from being installed in the forwarding table or exported to other protocols. This eliminates the need to break and reestablish a session upon reconfiguration if import route policy is changed.

peer ip_address weight
off

Disables the weight associated with the specified peer.

peer ip_address
aggregator id
<on | off>

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

Default: off

peer ip_address
holdtime <6-65535>

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.

peer ip_address
holdtime default

A holdtime of 180 seconds.

peer ip_address
keepalive <2-21845>

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 interval, but the holdtime value must be 3 times the keepalive interval value.

peer
ip_address_keepalive
default

A keepalive interval of 60 seconds.

peer ip_address
ignore-first-ashop
<on | off>

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.

peer ip_address
send-keepalives
<on | off>

This router always sends keepalive messages even when an update message is sufficient. This option allows interoperability with routers that do not strictly adhere to protocol specifications regarding update.

send-route-refresh
[request | route-update
[ipv4|ipv6|all]
[unicast]

The router dynamically request BGP route updates from peers or respond to requests for BGP route updates.

peer ip_address 
accept-routes all

An inbound BGP policy route if one is not already configured. Enter all to specify accepting routes and installing them with an invalid preference. Depending on the local inbound route policy, these routes are then made active or inactive.

peer ip_address 
accept-routes none

An inbound BGP policy route if one is not already configured. Enter none to specify deleting routes learned from a peer. This option saves memory overhead when many routes are rejected because no inbound policy exists.

peer ip_address 

passive-tcp <on | off>

The router waits for the specified peer to issue an open message. No tcp connections are initiated by the router.

Default: off

peer ip_address
authtype none

Do not use an authentication scheme between peers. Using an authentication scheme guarantees that routing information is accepted only from trusted peers.

peer ip_address
authtype md5 secret
secret

Use md5 authentication between peers. In general, peers must agree on the authentication configuration to and from peer adjacencies. Using an authentication scheme guarantees that routing information is accepted only from trusted peers.

Note - TCP MD5 is not supported on BGP IPv6 peers.

peer ip_address
throttle-count
<0-65535>

The number of BGP updates to send at one time. The throttle count option limits the number of BGP updates when there are many BGP peers.

peer ip_address
throttle count off

Disables the throttle count option.

peer ip_address
log-state-transitions
<on | off>

The router generates a log message whenever a peer enters or leave the established state.

peer ip_address
log-warnings <on | off>

The router generates a log message whenever a warning scenario is encountered in the codepath.

peer ip_address trace
bgp_traceoption
<on | off>

Tracing options for the BGP implementation. Log messages are saved in the /var/log/routed.log.* files. See Configuring Trace Options - Gaia Clish.

graceful-restart-helper
<on | off>

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.

graceful-restart-helper
-stalepath-time seconds

The maximal 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.

route-refresh <on |
off>

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.

<on | off>

Enable or disable BGP policy options based on communities.