Use these commands to configure external sessions of the protocol (between routers in different autonomous systems):
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 |
Parameters
Parameter |
Description |
|---|---|
|
The autonomous system number of the external peer group. Enter an integer from 1‑65535. |
|
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. |
|
You can enter a brief text description of the group. |
|
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 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.
|
|
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.
|
|
Disables outdelay. |
Use these commands to configure BGP peers.
Gaia supports IPv4 and IPv6 addresses for BGP peers.
Notes:
set bgp external remote‑as <as_number> peer <ip_address>
{on | off}
med‑out {<0—4294967294> | default}
outgoing-interface <finterface> {on | off}
accept‑med {on | off}
multihop {on | off}
peer-local-as as {{<1-4294967295> | <0.1-65535.65535>} on | off}
peer-local-as {dual peering | inbound-peer-local | outbound-local} {on | off}
as-override {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
Parameter |
Description |
|---|---|
|
A specified peer <ip_address> for the group. |
|
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 a metric specified by the redistribute policy. External peers use MED values to know which of the available entry points into an autonomous system is preferred. A lower MED value is preferred over a higher MED value.
|
|
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 |
|
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. |
|
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 configure the multihop session in the Time to Live (TTL) parameter, that is, the number of hops to the EBGP peer. This option can also be used to set up peers for EBGP load balancing.
|
|
Configures the connection to a remote peer with a Peer Local ASN, on a per-peer basis. The Peer Local ASN replaces the Local ASN in the BGP session. |
|
|
|
To prevent loops in BGP, routers examine the AS number in the AS Path. If a router sees its own AS number in the AS Path of the BGP packet, it drops the packet. Overrides the peer's AS number with the router's AS number in the outbound AS path. This helps multiple sites in the same AS accept the routes. If the Peer Local AS feature is enabled, the router uses the configured Peer Local AS to override the remote peer's AS number.
|
|
Use the TTL (Time to Live) parameter to limit the number of hops over which the External BGP (EBGP) multihop session is created. 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.
|
|
The router's aggregate attribute as zero (rather than the router ID value). This option prevents the creation of aggregate routes with different AS paths by different routers in an AS. |
|
The BGP holdtime interval, in seconds, during the negotiation of 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.
|
|
The keepalive option is an alternative way to enter a holdtime value in seconds during the negotiation of 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.
|
|
Ignore the first AS number in the AS path for routes learned from the corresponding peer. Set this option only if you peer with a route server in transparent mode. In transparent mode, the route server redistributes routes from multiple other autonomous systems and does not prepend its own ASN. |
|
The router always sends keepalive messages even when an update message is sufficient. This option lets the router interoperate with other routers that do not strictly follow protocol specifications regarding updates. |
|
The router dynamically requests BGP route updates from peers or responds to requests for BGP route updates. |
|
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 and not wait for a route refresh request from the peer. |
|
An inbound BGP policy route if one is not already configured. Enter Enter |
|
The router waits for the specified peer to issue an open message. The router does not initiate tcp connections. |
|
Remove private AS numbers from BGP update messages to external peers. |
|
Do not use an authentication scheme between peers. If you use an authentication scheme, routing information is accepted only from trusted peers.
|
|
Use md5 authentication between peers. In general, peers must agree on the authentication configuration to and from peer adjacencies. If you use an authentication scheme, routing information is accepted only from trusted peers. Note - TCP MD5 is not supported on BGP IPv6 peers. |
|
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. |
|
Do NOT generate a default route when the peer receives a valid update from its peer. |
|
The router generates a log message when a peer enters or leaves the established state. |
|
The router generates a log message when there is a warning scenario in the codepath. |
|
Tracing options for the BGP implementation. Log messages are saved in the |
|
On each peer, configure the type of routes (Multiprotocol capability) to interchange between peers. Select one of these:
To create peering, the routers must share a capability. |
|
Sets the Check Point system to maintain the forwarding state advertised by peer routers even when they restart. This minimizes the negative effects caused by the restart of peer routers. |
|
The maximum seconds that routes previously received from a restarting router are kept so that they can be revalidated. The timer starts after the peer sends an indication that it recovered. |
Use these commands to configure BGP confederations:
You can configure a BGP confederation in conjunction with external 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 synchronizat |
Parameters
Parameter |
Description |
|---|---|
|
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. |
|
Disables the confederation identifier. |
|
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. |
|
Specifies a value of 1. |
|
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. |
|
Disables the routing-domain identifier. |
|
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. |
|
Specifies a value of 1. |
|
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. |
Use these commands to configure BGP confederation peers:
|
Note - The IP address of a peer can be an IPv4 or an IPv6 address. |
Syntax:
set bgp confederation member-as <as_id> [on | off] description [off | "<description">] interface <int> [on | off] local-address <IP_addr> [off | on] med [default | <value>] nexthop-self [off | on] outdelay [off | <delay>] peer <IP_addr> [off | on] accept-routes [all | none] authtype [none | md5 secret <passwd>] capability [ipv4-unicast | ipv6-unicast] [off | on] graceful-restart [off | on] graceful-restart-stalepath-time [default | <time>] holdtime [default | <time>] ignore-first-ashop [off | on] keepalive [default | <time>] local-address <local_IP_addr> [off | on] log-state-transitions [off | on] log-warnings [off | on] no-aggregator-id [off | on] outgoing-interface <int> [off | on] passive-tcp [off | on] peer-type [none] [off | on] [reflector-client] [off | on] [no-client-reflector] [off | on] ping [off | on] route-refresh [off | on] send-keepalives [off | on] send-route-refresh request [all | ipv4 | ipv6] unicast route-update [all | ipv4 | ipv6] unicast throttle-count [off | <count>] trace [all | keepalive | open | packets | update | general | normal | policy | route | state | task | timer] [off | on] weight <weight> comment "<comment>" protocol [all | bgp | direct | rip | static | ospf | ospfase] |
Parameters
Parameter |
Description |
|---|---|
|
Creates ( |
|
Sets the peer group description to <description>, or turns off the description ( |
|
Sets a gateway interface (<int>: eth1, eth2, etc.) as the peer group interface, and turns it on or off. |
|
Sets a peer group with an IP address on the local gateway. |
|
Sets the peer group local Multi-Exit Discriminator. The default is 0. |
|
Sets ( |
|
Sets or removes the out-delay value (in seconds). Set this value to enforce rate limiting. |
|
Creates a peer group with the specified gateway ( |
|
Sets an internal peer group protocol. |
|
Accepts routes from peers only if there is an inbound BGP route policy. In the absence of a configured import policy for this peer, specify
|
|
Sets peer authentication between the local gateway and the specified peer gateway (<IP_addr>). You can set it to MD5 and specify the password ( |
|
Configures peer multiprotocol capabilities ( |
|
Turns graceful restart on and off between the local gateway and the specified peer ( |
|
Sets graceful restart stalepath time (in seconds) with the specified peer (
|
|
Sets the maximal amount of time (in seconds) that can elapse between messages from the specified peer ( |
|
Sets the router to ignore the first AS number in the AS_PATH for routes learned from the specified peer. Use this option for a route server peer in so-called transparent mode. The route server is configured to redistribute routes from multiple ASs and does not prepend its own AS number. |
|
Sets the keepalive timer (in seconds) for the specified peer (
|
|
Sets a local IP address ( |
|
Turns logging of peer state transitions |
|
Turns logging of warnings |
|
Sets the specified peer ( |
|
Sets a specific outgoing interface ( |
|
Sets peer passive behavior. If |
|
Sets the local gateway's peer type in the relation to the specified peer (
|
|
Sets ping capability between the local gateway and the specified peer (
|
|
Sets route refresh capability between the local gateway and the specified peer ( |
|
Sets the gateway to always send keepalive messages to the specified peer ( |
|
Sets the local gateway to request BGP route updates from the specified peer (
|
|
Sets the local gateway to respond to requests for BGP route updates from the specified peer (
|
|
Sets the maximal number of BGP updates that can be sent at one time to the specified peer ( |
|
Sets the types of packets to trace from the specified peer ( |
|
Sets the weight for the specified peer ( |
|
Sets a comment associated with the specified peer ( |
Use these commands to configure BGP route reflection:
You can configure route reflection as an alternative to BGP confederations. Route reflection supports both internal and external BGP routing groups.
set bgp internal peer <ip_address> peer-type none no-client-reflector reflector-client cluster-id {<ip_address> | off} default-med {<0-65535> | off} default-route-gateway {<ip_address> | off} |
Parameters
Parameter |
Description |
|---|---|
|
The peer router |
|
An advanced option. |
|
The peer router |
|
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 |
|
Disable the cluster ID. |
|
The multi-exit discriminator (MED) metric used to advertise routes through BGP. |
|
Disable the specified MED metric. |
|
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 |
|
Disables the configured default BGP route. |
Use these commands to configure BGP route dampening:
BGP route dampening maintains a history of flapping routes and prevents advertising these routes. A route is considered to be flapping when it is repeatedly transitioning from available to unavailable or vice versa.
{on | off} suppress-above {<2-32> | default} reuse-below {<1-32> | default} max-flat {<3-64> | default} reachable-decay {<1-900> | default} unreachable-decay [<1-2700> | default} keep-history {<2-5400> | default} |
Parameters
Note: BGP route dampening is only supported for External BGP (EBGP).
Parameter |
Description |
|---|---|
|
Specifies whether to enable or disable BGP route dampening. |
|
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. |
|
Specifies an instability metric value for suppressing routes of 3. |
|
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. |
|
Specifies an instability metric value for announcing previously suppressed routes of 2. |
|
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. |
|
Specifies the upper limit of the instability metric as 16. |
|
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. |
|
Specifies a value of 300. |
|
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. |
|
Specifies a value of 900 |
|
Specifies the period for which route flapping history is maintained for a given route. |
|
Specifies a value of 1800. |
Use the following commands to configure internal BGP sessions, that is, between routers within the same autonomous system.
set bgp internal
{on | off}
description <text>
med <0‑65535> | default
outdelay <0‑65535> | 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}
peer <ip_address>
peer_type {on | off}
weight <0‑65535> | off
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]
Parameter |
Description |
|---|---|
|
Enable or disable an internal BGP group. |
|
Optional: A brief text description of the group. |
|
|
|
|
|
The amount of time in seconds that a route must be present in the
|
|
Disables outdelay. |
|
This router sends one of its own IP addresses as the BGP next hop.
|
|
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 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.
|
|
Enable or disable the specified internal peer group on all interfaces or a specific interface. |
|
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: |
|
An internal peer address and peer type. Enter |
|
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. |
|
Disables the weight associated with the specified peer. |
|
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
|
|
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. |
|
A holdtime of 180 seconds. |
|
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. |
|
A keepalive interval of 60 seconds. |
|
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. |
|
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. |
|
The router dynamically request BGP route updates from peers or respond to requests for BGP route updates. |
|
An inbound BGP policy route if one is not already configured. Enter |
|
An inbound BGP policy route if one is not already configured. Enter |
|
The router waits for the specified peer to issue an open message. No tcp connections are initiated by the router.
|
|
Do not use an authentication scheme between peers. Using an authentication scheme guarantees that routing information is accepted only from trusted peers. |
|
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. |
|
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. |
|
Disables the throttle count option. |
|
The router generates a log message whenever a peer enters or leave the established state. |
|
The router generates a log message whenever a warning scenario is encountered in the codepath. |
|
Tracing options for the BGP implementation. Log messages are saved in the |
|
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. |
|
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. |
|
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. |
Use this command to configure BGP communities:
A BGP community is a group of destinations that share the same property. However, a community is not restricted to one network or autonomous system. Use communities to simplify the BGP inbound and route redistribution policies. Use the BGP communities commands together with inbound policy and route redistribution.
set bgp communities {on | off} |
Parameters
Parameter |
Description |
|---|---|
|
Enable BGP policy options based on communities. |
|
Disable BGP policy options based on communities. |
Use these commands to monitor and troubleshoot your BGP implementation:
show bgp groups memory errors paths stats peer <ip_address> advertise detailed received peers advertise detailed established received summary |
show ipv6 route bgp all aspath communities detailed metrics suppressed |