[no] bgp
config>router
Supported on all 7210 SAS platforms as described in this document
This command enables the BGP protocol instance and BGP configuration context. BGP is administratively enabled upon creation.
The no form of this command deletes the BGP protocol instance and removes all configuration parameters for the BGP instance. BGP must be shutdown before deleting the BGP instance. An error occurs if BGP is not shutdown first.
[no] add-paths
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command enables the add-paths configuration context and enables add-paths to be configured for one or more BGP route types. The BGP add-paths capability allows the router to send and receive multiple paths per prefix to and from a peer.
The no form of this command (no add-paths) removes add-paths from the configuration of BGP, the group, or the neighbor, causing sessions established using add-paths to go down and come back up without the add-paths capability.
no add-paths
ipv4 send send-limit receive [none]
ipv4 send send-limit
no ipv4
config>router>bgp>add-paths
config>router>bgp>group>add-paths
config>router>bgp>group>neighbor>add-paths
Supported on all 7210 SAS platforms as described in this document.
This command configures the add-paths capability for IPv4 routes. By default, the add-paths capability is disabled for IPv4 routes.
Add-paths are supported only for the label-IPv4 family.
The maximum number of paths to send per IPv4 NLRI is the configured send-limit, which is a mandatory parameter. The capability to receive multiple paths per prefix from a peer is configurable using the optional receive keyword. If the receive keyword is not included in the command, the receive capability is enabled by default.
The no form of this command disables add-paths support for IPv4 routes, causing sessions established using add-paths for IPv4 to go down and come back up without the add-paths capability.
no ipv4
Specifies the maximum number of paths per IPv4 NLRI that are allowed to be advertised to add-path peers. The actual number of advertised routes may be less depending on the next-hop diversity requirement, other configuration options, route policies, and route advertisement rules.
Keyword to specify that the router negotiates the add-paths receive capability for IPv4 routes with its peers.
Keyword to specify that the router does not negotiate the add-paths receive capability for IPv4 routes with its peers.
ipv6 send send-limit receive [none]
ipv6 send send-limit
no ipv6
config>router>bgp>add-paths
config>router>bgp>group>add-paths
config>router>bgp>group>neighbor>add-paths
Supported on all 7210 SAS platforms as described in this document.
This command configures the add-paths capability for IPv6 routes. By default, the add-paths capability is disabled for IPv6 routes.
Add-paths are supported only for the label-IPv4 family.
The maximum number of paths to send per IPv6 NLRI is the configured send-limit, which is a mandatory parameter. The capability to receive multiple paths per prefix from a peer is configurable using the optional receive keyword. If the receive keyword is not included in the command, the receive capability is enabled by default.
The no form of this command disables add-paths support for IPv6 routes, causing sessions established using add-paths for IPv6 to go down and come back up without the add-paths capability.
no ipv4
Specifies the maximum number of paths per IPv6 NLRI that are allowed to be advertised to add-path peers. The actual number of advertised routes may be less depending on the next-hop diversity requirement, other configuration options, route policies, and route advertisement rules.
Keyword to specify that the router negotiates the add-paths receive capability for IPv6 routes with its peers.
Keyword to specify that the router does not negotiate the add-paths receive capability for IPv6 routes with its peers.
vpn-ipv4 send send-limit receive [none]
vpn-ipv4 send send-limit
no vpn-ipv4
config>router>bgp>add-paths
config>router>bgp>group>add-paths
config>router>bgp>group>neighbor>add-paths
Supported on all 7210 SAS platforms as described in this document
This command configures the add-paths capability for VPN-IPv4 routes. By default, add-paths is not enabled for VPN-IPv4 routes.
The maximum number of paths per VPN-IPv4 NLRI to send is the configured send-limit, which is a mandatory parameter. The capability to receive multiple paths per prefix from a peer is configurable using the optional receive keyword. If the receive keyword is not included in the command, the receive capability is enabled by default.
The no form of this command disables add-paths support for VPN-IPv4 routes, causing sessions established using add-paths for VPN-IPv4 to go down and come back up without the add-paths capability.
no vpn-ipv4
Specifies the maximum number of paths per VPN-IPv4 NLRI that are allowed to be advertised to add-paths peers (the actual number of advertised routes may be less depending on the next-hop diversity requirement, other configuration options, route policies, or route advertisement rules).
Keyword to specify the router negotiates the add-paths receive capability for VPN-IPv4 routes with its peers.
Keyword to specify the router does not negotiate the add-paths receive capability for VPN-IPv4 routes with its peers.
vpn-ipv6 send send-limit receive [none]
vpn-ipv6 send send-limit
no vpn-ipv6
config>router>bgp>add-paths
config>router>bgp>group>add-paths
config>router>bgp>group>neighbor>add-paths
Supported on all 7210 SAS platforms as described in this document
This command configures the add-paths capability for VPN-IPv6 routes. By default, add-paths is not enabled for VPN-IPv6 routes.
The maximum number of paths per VPN-IPv6 NLRI to send is the configured send-limit, which is a mandatory parameter. The capability to receive multiple paths per prefix from a peer is configurable using the optional receive keyword. If the receive keyword is not included in the command the receive capability is enabled by default.
The no form of this command disables add-paths support for VPN-IPv6 routes, causing sessions established using add-paths for VPN-IPv6 to go down and come back up without the add-paths capability.
no vpn-ipv6
Specifies the maximum number of paths per VPN-IPv6 NLRI that are allowed to be advertised to add-paths peers (the actual number of advertised routes may be less depending on the next-hop diversity requirement, other configuration options, route policies and/or route advertisement rules).
Keyword to specify the router negotiates the add-paths receive capability for VPN-IPv6 routes with its peers.
Keyword to specify the router does not negotiate the Add-Paths receive capability for VPN-IPv6 routes with its peers.
[no] advertise-inactive
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command enables the advertising of inactive BGP routes to other BGP peers. By default, BGP only advertises BGP routes to other BGP peers if a specific BGP route is chosen by the route table manager as the most preferred route within the system and is active in the forwarding plane. This command allows system administrators to advertise a BGP route even though it is not the most preferred route within the system for a specific destination.
The no form of this command disables the advertising of inactive BGP routers to other BGP peers.
no advertise-inactive
advertise-label [ipv4 [use-svc-routes]] [ipv6]
no advertise-label
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures the IPv4 or IPv6 transport peers to exchange RFC 3107-labeled IPv4 or IPv6 routes.
If IPv4 is enabled, all IPv4 routes advertised to the remote BGP peer are sent with an RFC 3107-formatted label for the destination route.
If IPv6 is enabled, all IPv6 routes advertised to the remote BGP peer are sent with an RFC 3107-formatted label for the destination route.
The optional use-svc-routes parameter limits the number of BGP 3107 IPv4 labeled routes that are installed in the MPLS FIB. If this parameter is specified, only those BGP 3107 labeled routes that are required by services or required for establishing a BGP session with a configured neighbor are installed in the MPLS FIB. The following conditions trigger the installation of the MPLS label into the MPLS FIB for the received BGP 3107 IPv4 labeled route:
configuration of SDP to use a BGP tunnel to the far end
dynamic creation of spoke-SDP binding when a route is received through BGP AD and the far end of the SDP binding is reachable using the labeled route
installation of VPN-IPv4 routes received from a PE that is reachable using the labeled route
configuration of a BGP session to a BGP peer, using the bgp>neighbor CLI command, and the BGP peer is reachable using the labeled route
on the 7210 SAS-R6 and 7210 SAS-R12, if this command is enabled along with the config router bgp enable-rr-vpn-forwarding command, only those BGP 3107 routes that are required to resolve the VPN-IPv4 or VPN-IPv6 routes, and for which the 7210 SAS node is swapping the VPN label, are added to the FIB (the rest are only held in the RIB)
other IP applications, such as FTP and SSH, do not trigger the installation of the IPv4 labeled routes into the MPLS FIB
The no form of this command disables all configured options.
no advertise-label
Keyword to specify the advertisement label address family for core IPv4 routes. This keyword can be specified only for an IPv4 peer.
Keyword to enable the user to limit the number of BGP 3107 labeled routes that are installed in the MPLS FIB.
Keyword to specify the advertisement label address family for core IPv6 routes. This keyword can be specified only for an IPv6 peer.
[no] aggregator-id-zero
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command sets the router ID in the BGP aggregator path attribute to zero when BGP aggregates routes. This prevents different routers within an AS from creating aggregate routes that contain different AS paths.
When BGP is aggregating routes, it adds the aggregator path attribute to the BGP update messages. By default, BGP adds the ASN and router ID to the aggregator path attribute.
When this command is enabled, BGP adds the router ID to the aggregator path attribute. This command is used at the group level to revert to the value defined under the global level, while this command is used at the neighbor level to revert to the value defined under the group level.
The no form of this command used at the global level reverts to default where BGP adds the ASN and router ID to the aggregator path attribute.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
no aggregator-id-zero
[no] aigp
config>router>bgp>group
config>router>bgp>group>neighbor
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
This command enables accumulated Interior Gateway Protocol (AIGP) path attribute support with one or more BGP peers. BGP path selection among routes with an associated AIGP metric is based on the end-to-end IGP metrics of the different BGP paths, even when these BGP paths span more than one AS and IGP instance.
The no form of this command disables AIGP path attribute support, removes the AIGP attribute from advertised routes, and causes the AIGP attribute in received routes to be ignored.
no aigp
auth-keychain name
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures a TCP authentication keychain to use for the session. The keychain allows the rollover of authentication keys during the lifetime of a session.
no auth-keychain
Specifies the name of the keychain, up to 32 characters, to use for the specified TCP session or sessions.
authentication-key [authentication-key | hash-key] [hash | hash2]
no authentication-key
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures the BGP authentication key.
Authentication is performed between neighboring routers before setting up the BGP session by verifying the password. Authentication is performed using the MD-5 message based digest.
The no form of this command reverts to the default value.
MD5 Authentication disabled
Specifies the authentication key. The key can be any combination of ASCII characters up to 255 characters (unencrypted). If spaces are used in the string, enclose the entire string in quotation marks (‟ ”).
Specifies the hash key. The key can be any combination of ASCII characters up to 342 characters (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (‟ ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
Keyword to specify that the key is entered in an encrypted form. If the hash parameter is not used, the key is assumed to be in a non-encrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash parameter specified.
Keyword to specify that the key is entered in a more complex encrypted form. If the hash2 parameter is not used, the less encrypted hash form is assumed.
[no] backup-path [ipv4]
config>router>bgp
Supported on all 7210 SAS platforms as described in this document
This command enables the computation and use of a backup path for labeled IPv4 BGP-learned prefixes belonging to the base router. Multiple paths must be received for a prefix to take advantage of this feature. When a prefix has a backup path and its primary paths fail, the affected traffic is rapidly diverted to the backup path without waiting for control plane reconvergence to occur. When many prefixes share the same primary paths, and in some cases also the same backup path, the time to failover traffic to the backup path is independent of the number of prefixes.
By default, IPv4 prefixes do not have a backup path installed in the IOM.
The no form of this command disables the use of a backup path.
no backup-path
Keyword that enables BGP fast reroute for labeled IPv4 routes.
best-path-selection
config>router>bgp
Supported on all 7210 SAS platforms as described in this document
This command enables path selection configuration.
always-compare-med {zero | infinity}
no always-compare-med strict-as {zero | infinity}
no always-compare-med
config>router>bgp>best-path-selection
Supported on all 7210 SAS platforms as described in this document
This command configures the comparison of BGP routes based on the Multi-Exit Discriminator (MED) path attribute.
The default behavior of 7210 SAS (equivalent to the no form of this command) is to only compare two routes on the basis of MED if they have the same neighbor AS (the first non-confed AS in the received AS_PATH attribute). Also by default, a route without a MED attribute is handled the same as though it had a MED attribute with the value 0.
This command without the strict-as keyword allows MED to be compared even if the paths have a different neighbor AS; in this case, if neither the zero nor infinity keyword is specified, the zero option is inferred, meaning a route without a MED is handled as though it had a MED attribute with the value 0. When the strict-as keyword is present, MED is only compared between paths from the same neighbor AS; in this case, zero or infinity is mandatory and tells BGP how to interpret paths without a MED attribute.
The no form of this command only compares two routes on the basis of MED if they have the same neighbor AS.
no always-compare-med
Keyword to specify that for routes learned without a MED attribute, a zero (0) value is used in the MED comparison. The routes with the lowest metric are the most preferred.
Keyword to specify that for routes learned without a MED attribute, a value of infinity (2^32-1) is used in the MED comparison. This in effect makes these routes the least desirable.
Keyword to specify that BGP paths are to be compared even with different neighbor AS.
as-path-ignore [ipv4] [vpn-ipv4] [l2-vpn] [mvpn-ipv4]
no as-path-ignore
config>router>bgp>best-path-selection
Supported on all 7210 SAS platforms as described in this document
This command specifies whether the AS path is used to determine the best BGP route.
If this command is enabled, the AS paths of incoming routes are not used in the route selection process.
The no form of this command removes the parameter from the configuration.
no as-path-ignore
Keyword to specify that the AS-path length is ignored for all IPv4 routes.
Keyword to specify that the length AS-path is ignored for all IPv4 VPRN routes.
Keyword to specify that the AS-path length is ignored for all L2-VPN NLRIs.
Keyword to specify that the AS-path length is ignored for all mVPN IPv4 multicast routes. Supported on 7210 SAS-T, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp devices only.
ignore-nh-metric
no ignore-nh-metric
config>router>bgp>best-path-selection
Supported on all 7210 SAS platforms as described in this document
This command configures BGP to disregard the resolved distance to the BGP next hop in its decision process for selecting the best route to a destination.
When configured in the config>router>bgp>best-path-selection context, this command applies to the comparison of two BGP routes with the same NLRI learned from base router BGP peers. When configured in the config>service>vprn context, this command applies to the comparison of two BGP-VPN routes for the same IP prefix imported into the VPRN from the base router BGP instance. When configured in the config>service>vprn>bgp>best-path-selection context, this command applies to the comparison of two BGP routes for the same IP prefix learned from VPRN BGP peers.
The no form of this command reverts to the default behavior whereby BGP factors the distance to the next hop into its decision process.
no ignore-nh-metric
ignore-router-id
no ignore-router-id
config>router>bgp>best-path-selection
Supported on all 7210 SAS platforms as described in this document
This command modifies the route selection behavior.
When the this command is enabled and the current best path to a destination was learned from eBGP peer X with BGP identifier x, new paths that are received from eBGP peer Y with BGP identifier y and are equivalent do not change the best path even if y is less than x during BGP identifier comparison.
The no form of this command reverts to the default behavior of selecting the route with the lowest BGP identifier (y) as best.
no ignore-router-id
cluster cluster-id
no cluster
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
7210 SAS-R6 and 7210 SAS-R12
This command configures the cluster ID for a route reflector server.
Route reflectors reduce the number of iBGP sessions required within an AS. Normally, all BGP speakers within an AS must have a BGP peering with every other BGP speaker in an AS. A route reflector and its clients form a cluster. Peers that are not part of the cluster are considered to be non-clients.
When a route reflector receives a route, it must first select the best path from all the paths received. If the route was received from a non-client peer, the route reflector sends the route to all clients in the cluster. If the route came from a client peer, the route reflector sends the route to all non-client peers and to all client peers except the originator.
For redundancy, a cluster can have multiple route reflectors.
The no form of this command deletes the cluster ID and disables the route reflection at the global BGP level or for the specified group or neighbor.
no cluster
Specifies the route reflector cluster ID, expressed in dotted-decimal notation.
connect-retry seconds
no connect-retry
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures the BGP connect retry timer value.
When this timer expires, BGP tries to reconnect to the configured peer. This configuration parameter can be set at three levels: global level (applies to all peers), peer-group level (applies to all peers in group) or neighbor level (only applies to specified peer). The most specific value is used.
The no form of this command used at the global level reverts to the default value.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
connect-retry 120
Specifies the BGP connect retry timer value, in seconds, expressed as a decimal integer.
[no] damping
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command enables BGP route damping for learned routes that are defined within the route policy. Use damping to reduce the number of update messages sent between BGP peers and reduce the load on peers without affecting the route convergence time for stable routes. Damping parameters are set through route policy definition.
The no form of this command used at the global level reverts route damping.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
When damping is enabled and the route policy does not specify a damping profile, the default damping profile is used. This profile is always present and consists of the following parameters:
Half-life: |
15 minutes |
Max-suppress: |
60 minutes |
Suppress-threshold: |
3000 |
Reuse-threshold: |
750 |
no damping
[no] default-route-target
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command originates the default RTC route (zero prefix length) toward the selected peers.
The no form of this command disables the advertisement of the default RTC route.
no default-route-target
description description-string
no description
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command enables a text description stored in the configuration file for a configuration context.
The no form of this command removes the description string from the context.
Specifies the description character string. Allowed values are any string up to 80 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
[no] disable-4byte-asn
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command disables the use of 4-byte ASNs. It can be configured at all three level of the hierarchy so it can be specified down to the per peer basis.
If this command is enabled, 4-byte ASN support should not be negotiated with the associated remote peers.
The no form of this command reverts to the default behavior, which is to enable the use of 4-byte ASN.
[no] disable-capability-negotiation
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command disables the exchange of capabilities when the command is enabled. After the peering is flapped, any new capabilities are not negotiated and strictly support IPv4 routing exchanges with that peer.
The no form of this command removes this command from the configuration and reverts to the default behavior.
no disable-capability-negotiation
[no] disable-client-reflect
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
7210 SAS-R6 and 7210 SAS-R12
This command disables the reflection of routes by the route reflector at the BGP, group, or neighbor level.
This command only disables the reflection of routes from other client peers. Routes learned from non-client peers are still reflected to all clients.
The no form of this command re-enables client reflection of routes.
no disable-client-reflect
disable-communities [standard] [extended]
no disable-communities
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures BGP to disable sending communities.
Keyword to specify standard communities that existed before VPRNs or 2547.
Keyword to specify BGP communities used were expanded after the concept of 2547 was introduced, to include handling the VRF target.
[no]disable-fast-external-failover
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures BGP fast external failover.
[no] disallow-igp
config>router>bgp
Supported on all 7210 SAS platforms as described in this document
This command enables the use of the IGP next hop to the BGP next hop as the next hop of last resort.
[no] enable-peer-tracking
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command enables BGP peer tracking. BGP peer tracking allows a BGP peer to be dropped immediately if the route used to resolve the BGP peer address is removed from the IP routing table, and there is no alternative available. The BGP peer does not wait for the hold timer to expire; therefore, the BGP reconvergence process is accelerated.
The no form of this command disables peer tracking.
no enable-peer-tracking
[no] enable-rr-vpn-forwarding
config>router>bgp
7210 SAS-R6 and 7210 SAS-R12
This command enables a route reflector of VPN-IP routes to be deployed in the datapath between two BGP peers (a peer X and a peer Y) in a next-hop resolution.
Scaling and convergence should be considered before enabling this command.
When this command is configured, all received VPN-IP routes, regardless of route target, are imported into the dummy VRF, where the BGP next hops are resolved. The label-route-transport-tunnel command in the config>router>bgp>next-hop-resolution context determines what types of tunnels are eligible to resolve the next hops.
If a received VPN-IP route from iBGP peer X is resolved and selected as best so that it can be readvertised to an iBGP peer Y, and the BGP next hop is modified toward peer Y (by using the next-hop-self command in the Y group or neighbor context, or by using the next-hop action command in an export policy applied to Y), BGP allocates a new VPN service label value for the route, signals that new label value to Y, and programs the IOM to do the corresponding label swap operation. The supported combinations of X and Y are the following:
from X (client) to Y (client)
from X (client) to Y (non-client)
from X (non-client) to Y (client)
The no form of this command causes the route to be readvertised without a new service label, or a new service label to not be advertised between the two peers.
no enable-rr-vpn-forwarding
export policy-name [policy-name…up to 15 max]
no export [policy-name]
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command specifies the export route policy used to determine which routes are advertised to peers. Route policies are configured in the config>router>policy-options context.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group), or neighbor level (only applies to specified peer). The most specific level is used.
When multiple policy names are specified, the policies are evaluated in the order they are specified. A maximum of 15 policy names can be configured. The first policy that matches is applied.
When multiple export commands are issued, the last command entered overrides the previous command.
When no export policies are specified, BGP routes are advertised and non-BGP routes are not advertised by default.
The no form of this command removes the policy association with the BGP instance. To remove association of all policies, use the no export command without arguments.
no export
Specifies the route policy name. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
family [ipv4] [vpn-ipv4] [ipv6] [vpn-ipv6] [l2-vpn] [ms-pw] [mvpn-ipv4] [route-target]
no family
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command specifies the address family or families to support over BGP peerings in the base router. This command is additive; entering the family command adds the specified address family to the list.
The no form of this command removes the specified address family from the associated BGP peerings. If an address family is not specified, the supported address family is reset back to the default.
family ipv4
Keyword to provision support for IPv4 routing information.
Keyword word to exchange IPv4 VPN routing information.
Keyword to exchange dynamic MS-PW related information.
Keyword to exchange IPv6 routing information.
Keyword to exchange IPv6 VPN routing information.
Keyword to exchange Layer 2 VPN information.
Keyword to exchange multicast VPN related information. This keyword is supported only on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), and 7210 SAS-T (network). This family is not supported for 7210 SAS-Sx 10/100GE devices.
Keyword to exchange RT constrained route information.
[no] split-horizon
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
7210 SAS-R6 and 7210 SAS-R12
This command enables the use of split horizon. Split horizon prevents routes from being reflected back to a peer that sends the best route. It applies to routes of all address families and to eBGP or iBGP sending peers.
The no form of this command means that no effort is taken to prevent a best route from being reflected back to the sending peer.
no split-horizon
[no] vpn-apply-export
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command causes the base instance BGP export route policies to be applied to VPN-IPv4 routes.
The no form of this command disables the application of the base instance BGP route policies to VPN-IPv4 routes.
no vpn-apply-export
[no] vpn-apply-import
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command causes the base instance BGP import route policies to be applied to VPN-IPv4 routes.
The no form of this command disables the application of the base instance BGP import route policies to VPN-IPv4 routes.
no vpn-apply-import
[no] group name
config>router>bgp
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure a BGP peer group.
The no form of this command deletes the specified peer group and all configurations associated with the peer group. The group must be shutdown before it can be deleted.
Specifies the peer group name. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
hold-time seconds [strict]
no hold-time
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures the BGP hold time, expressed in seconds.
The BGP hold time specifies the maximum time BGP waits between successive messages (either keepalive or update) from its peer, before closing the connection. This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in group), or neighbor level (only applies to specified peer). The most specific value is used.
Even though the 7210 SAS implementation allows setting the keepalive time separately, the configured keepalive timer is overridden by the hold-time value under the following circumstances.
If the specified hold-time is less than the configured keepalive time, the operational keepalive time is set to a third of the hold-time; the configured keepalive time is not changed.
If the hold-time is set to zero, the operational value of the keepalive time is set to zero; the configured keepalive time is not changed. This means that the connection with the peer is up permanently and no keepalive packets are sent to the peer.
The no form of this command used at the global level reverts to the default value.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
hold-time 90
Specifies the hold-time, in seconds, expressed as a decimal integer. A value of 0 indicates the connection to the peer is up permanently.
Keyword to specify that the advertised BGP hold-time from the far-end BGP peer must be greater than or equal to the specified value.
import policy-name [policy-name…up to 15 max]
no import [policy-name]
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command specifies the import route policy to use to determine which routes are accepted from peers. Route policies are configured in the config>router>policy-options context.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group), or neighbor level (only applies to specified peer). The most specific level is used.
When multiple policy names are specified, the policies are evaluated in the order they are specified. A maximum of 15 policy names can be specified. The first policy that matches is applied.
When multiple import commands are issued, the last command entered overrides the previous command.
When an import policy is not specified, BGP routes are accepted by default.
The no form of this command removes the policy association with the BGP instance. To remove association of all policies, use no import without arguments.
no import
Specifies the route policy name. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
keepalive seconds
no keepalive
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures the BGP keepalive timer. A keepalive message is sent every time this timer expires.
The keepalive parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group), or neighbor level (only applies to specified peer). The most specific value is used.
The keepalive value is generally one third of the hold-time interval. The 7210 SAS implementation allows the keepalive value and the hold-time interval to be independently set; however, under the following circumstances, the configured keepalive value is overridden by the hold-time value.
If the specified keepalive value is greater than the configured hold-time, the specified value is ignored, and keepalive is set to one-third of the current hold-time value.
If the specified hold-time interval is less than the configured keepalive value, the keepalive value is reset to one third of the specified hold-time interval.
If the hold-time interval is set to zero, the configured the keepalive value is ignored. This means that the connection with the peer is up permanently and no keepalive packets are sent to the peer.
The no form of this command used at the global level reverts to the default value.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
keepalive 30
Specifies the keepalive timer, in seconds, expressed as a decimal integer.
local-address ip-address
no local-address
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures the local IP address used by the group or neighbor when communicating with BGP peers.
Outgoing connections use the local-address as the source of the TCP connection when initiating connections with a peer.
When a local address is not specified, 7210 SAS uses the system IP address when communicating with iBGP peers and uses the interface address for directly connected EBGP peers. This command is used at the neighbor level to revert to the value defined under the group level.
The no form of this command removes the configured local address for BGP.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
no local-address
Specifies the local address expressed in dotted decimal notation. Allowed value is a valid routable IP address on the router, either an interface or system IP address.
local-as as-number [private]
no local-as
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures a BGP virtual autonomous system (AS) number.
In addition to the ASN configured for BGP in the config>router>autonomous-system context, a virtual (local) ASN is configured.The virtual ASN is added to the as-path message before the router ASN makes the virtual AS the second AS in the as-path.
This command can be configured at three levels: global level (applies to all peers), group level (applies to all peers in peer-group), or neighbor level (only applies to specified peer). By specifying this command at each neighbor level, it is possible to have a separate AS number for each eBGP session.
When a command is entered multiple times for the same AS, the last command entered is used in the configuration. Add or remove the private keyword dynamically by reissuing the command.
Changing the local AS at the global level in an active BGP instance causes the BGP instance to restart with the new local ASN. Changing the local AS at the global level in an active BGP instance causes BGP to reestablish the peer relationships with all peers in the group with the new local ASN. Changing the local AS at the neighbor level in an active BGP instance causes BGP to reestablish the peer relationship with the new local ASN.
This is an optional command and can be used in a circumstance like the following example. Provider router P is moved from AS1 to AS2. The customer router that is connected to P, however, is configured to belong to AS1. To avoid reconfiguring the customer router, the local-as value on router P can be set to AS1. Therefore, router P adds AS1 to the as-path message for routes it advertises to the customer router.
The no form of this command used at the global level removes any virtual ASN configured.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
no local-as
Specifies the virtual AS number, expressed as a decimal integer.
Keyword to specify that the local AS is hidden in paths learned from the peering.
local-preference local-preference
no local-preference
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures the BGP local preference attribute in incoming routes, if not specified, and configures the default value for the attribute.
This command is used if the BGP route arrives from a BGP peer without the local-preference command configured.
The specified value can be overridden by any value set via a route policy. This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group), or neighbor level (only applies to specified peer). The most specific value is used.
The no form of this command at the global level specifies that incoming routes with local-preference set are not overridden, and routes arriving without local-preference set are interpreted as if the route had local-preference value of 100.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
no local-preference
Specifies the local preference value to use as the override value, expressed as a decimal integer.
loop-detect {drop-peer | discard-route | ignore-loop | off}
no loop-detect
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures how the BGP peer session handles loop detection in the AS path.
This command can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group), or neighbor level (only applies to specified peer). The most specific value is used.
Dynamic configuration changes of loop-detect are not recognized.
The no form of this command used at the global level reverts to the default value.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
loop-detect ignore-loop
Keyword that sends a notification to the remote peer and drops the session.
Keyword that discards routes received from a peer with the same ASN as the router. This option prevents routes looped back to the router from being added to the routing information base and consuming memory. When this option is changed, the change is not active for an established peer until the connection is reestablished for the peer.
Keyword that ignores routes with loops in the AS path but maintains peering.
Keyword that disables loop detection.
med-out {number | igp-cost}
no med-out
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command enables advertising the MED and assigns the value used for the path attribute for the MED advertised to BGP peers if the MED is not already set.
The specified value can be overridden by any value set via a route policy.
This command can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group), or neighbor level (only applies to specified peer). The most specific value is used.
The no form of this command used at the global level reverts to default where the MED is not advertised.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
no med-out
Specifies the MED path attribute value expressed as a decimal integer.
Keyword to specify the MED is set to the IGP cost of the specific IP prefix.
min-as-origination seconds
no min-as-origination
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures the minimum interval at which a path attribute, originated by the local router, can be advertised to a peer.
This command can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group), or neighbor level (only applies to specified peer). The most specific value is used.
The no form of this command used at the global level reverts to the default value.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
min-as-origination 15
Specifies the minimum path attribute advertising interval, in seconds, expressed as a decimal integer.
min-route-advertisement seconds
no min-route-advertisement
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures the minimum interval at which a prefix can be advertised to a peer.
This command can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group), or neighbor level (only applies to specified peer). The most specific value is used.
The no form of this command used at the global level reverts to default value.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
min-route-advertisement 30
Specifies the minimum route advertising interval, in seconds, expressed as a decimal integer.
[no] mp-bgp-keep
config>router>bgp
When this command is enabled, route refresh messages are not required or issued when VPN route policy changes are made; RIB-IN retains all MP-BGP routes.
The no form of this command disables the feature.
no mp-bgp-keep
multihop ttl-value
no multihop
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures the time to live (TTL) value entered in the IP header of packets sent to an eBGP peer multiple hops away.
The no form of this command conveys to the BGP instance that the eBGP peers are directly connected.
The no form of this command used at the global level reverts to the default value.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
multihop 1 (eBGP peers are directly connected)
multihop 64 (iBGP)
Specifies the TTL value, expressed as a decimal integer.
[no] next-hop-self
config>router>bgp>group
config>router>bgp>group>neighbor
7210 SAS-R6 and 7210 SAS-R12
This command configures BGP to advertise routes to members of a group or to a specific neighbor using a local address of the BGP instance as the BGP next-hop address. This command is set regardless of the route source (eBGP or iBGP) or its family. When used with VPN-IPv4 and VPN-IPv6 routes, the enable-rr-vpn-forwarding command should also be configured.
The no form of this command uses standard protocol behavior to decide whether to set next-hop-self in advertised routes.
no next-hop-self
next-hop-resolution
config>router>bgp
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure next-hop resolution.
label-route-transport-tunnel
config>router>bgp>next-hop-resolution
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure the binding of BGP labeled routes to tunnels.
family family
config>router>bgp>next-hop-res>label-route-transport-tunnel
Supported on all 7210 SAS platforms as described in this document
This command configures the binding of BGP labeled routes to tunnels for a specific family.
family ipv4
Specifies the family.
resolution {any | filter | disabled}
config>router>bgp>next-hop-res>lbl-rt-tunn>family
Supported on all 7210 SAS platforms as described in this document
This command configures the resolution state of BGP labeled routes using tunnels to BGP peers.
resolution filter
Keyword that enables binding to any supported tunnel type in the BGP label route context following TTM preference.
Keyword that enables binding to the subset of tunnel types configured under the resolution-filter context.
Keyword that disables the resolution of BGP label routes using tunnels to BGP peers.
resolution-filter
config>router>bgp>next-hop-res>lbl-rt-tunn>family
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure the subset of tunnel types used in the resolution of BGP label routes using tunnels to BGP peers.
[no] ldp
config>router>bgp>next-hop-res>lbl-rt-tunn>family>resolution-filter
Supported on all 7210 SAS platforms as described in this document
This command configures LDP tunneling for next-hop resolution.
[no] rsvp
config>router>bgp>next-hop-res>lbl-rt-tunn>family>resolution-filter
Supported on all 7210 SAS platforms as described in this document
This command configures RSVP tunneling for next-hop resolution.
no rsvp
[no] sr-isis
config>router>bgp>next-hop-res>lbl-rt-tunn>family>resolution-filter
7210 SAS-Mxp
This command selects the SR tunnel type programmed by an IS-IS instance in the TTM for next-hop resolution and specifies SR tunnels (shortest path) to destinations reachable by the IS-IS protocol.
This command allows BGP to use the SR tunnel in the tunnel table submitted by the lowest preference IS-IS instance or, in the case of IS-IS instances with the same lowest preference, the IS-IS instance with the lowest ID number.
no sr-isis
[no] sr-ospf
config>router>bgp>next-hop-res>lbl-rt-tunn>family>resolution-filter
7210 SAS-Mxp
This command selects the SR tunnel type programmed by an OSPF instance in the TTM for next-hop resolution and specifies SR tunnels (shortest path) to destinations reachable by the OSPF protocol.
This command allows BGP to use the SR tunnel in the tunnel table submitted by the lowest preference OSPF instance or, in the case of OSPF instances with the same lowest preference, the OSPF instance with the lowest ID number.
no sr-ospf
[no] outbound-route-filtering
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command opens the configuration tree for sending or accepting BGP filter lists from peers (outbound route filtering).
no outbound-route-filtering
[no] extended-community
config>router>bgp>orf
config>router>bgp>group>orf
config>router>bgp>group>neighbor>orf
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure sending or accepting extended-community-based BGP filters.
For the no form of the command to work, all subcommands (send-orf, accept-orf) must be removed first.
[no] accept-orf
config>router>bgp>orf>ext-comm
config>router>bgp>group>orf>ext-comm
config>router>bgp>group>neighbor>orf>ext-comm
Supported on all 7210 SAS platforms as described in this document
This command instructs the router to negotiate the receive capability in the BGP ORF negotiation with a peer and to accept filters that the peer wants to send.
The no form of this command causes the router to remove the accept capability in the BGP ORF negotiation with a peer and to clear any existing ORF filters that are currently in place.
send-orf [comm-id...(up to 32 max)]
no send-orf [comm-id]
config>router>bgp>orf>ext-comm
config>router>bgp>group>orf>ext-comm
config>router>bgp>group>neighbor>orf>ext-comm
Supported on all 7210 SAS platforms as described in this document
This command instructs the router to negotiate the send capability in the BGP outbound route filtering (ORF) negotiation with a peer.
This command also causes the router to send a community filter, prefix filter, or AS path filter configured as an inbound filter on the BGP session to its peer as an ORF Action ADD.
The no form of this command causes the router to remove the send capability in the BGP ORF negotiation with a peer.
The no form also causes the router to send an ORF remove action for a community filter, prefix filter, or AS path filter configured as an inbound filter on the BGP session to its peer.
If the comm-id parameters are not exclusively route target communities, the router extracts appropriate route targets and uses those. If the comm-id parameters specified contain no route targets, the router does not send an ORF.
no send-orf
Specifies a community policy that consists exclusively of route target extended communities. If the policy is not specified, the ORF policy is automatically generated from configured route target lists, accepted client route target ORFs, and locally configured route targets.
[no] neighbor ip-address
config>router>bgp>group
Supported on all 7210 SAS platforms as described in this document
This command creates a BGP peer/neighbor instance within the context of the BGP group.
This command can be issued repeatedly to create multiple peers and their associated configuration.
The no form of this command removes the specified neighbor and the entire configuration associated with the neighbor. The neighbor must be administratively shut down before attempting to delete it. If the neighbor is not shut down, the command does not result in any action except a warning message on the console indicating that the neighbor is still administratively up.
Specifies the IP address of the BGP peer router, in dotted decimal notation.
peer-as as-number
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures the AS number for the remote peer. The peer AS number must be configured for each configured peer.
For eBGP peers, the peer AS number configured must be different from the AS number configured for this router under the global level, because the peer is in a different AS than this router.
For iBGP peers, the peer AS number must be the same as the AS number of this router configured under the global level.
This is a required command for each configured peer. This command can be configured under the group level for all neighbors in a particular group.
Specifies the AS number, expressed as a decimal integer.
[no] path-mtu-discovery
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command enables path MTU discovery for the associated TCP connections. In doing so, the MTU for the associated TCP session is initially set to the egress interface MTU. The DF bit is also set so that if a router along the path of the TCP connection cannot handle a packet of a particular size without fragmenting, an ICMP message is sent back to set the path MTU for the specific session to a lower value that can be forwarded without fragmenting.
The no form of this command disables path MTU discovery.
no path-mtu-discovery
[no] preference preference
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures the route preference for routes learned from the configured peers.
This command can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group), or neighbor level (only applies to specified peer). The most specific value is used.
The lower the preference, the higher the chance of the route being the active route. The 7210 SAS assigns BGP routes highest default preference compared to routes that are direct, static, or learned through MPLS or OSPF.
The no form of this command used at the global level reverts to default value.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
preference 170
Specifies the route preference, expressed as a decimal integer.
[no] purge-timer minutes
config>router>bgp
Supported on all 7210 SAS platforms as described in this document
This command configures the maximum time before stale routes are purged.
Specifies the duration of the purge timer, in minutes.
rapid-update [l2-vpn] [mvpn-ipv4] [evpn]
no rapid-update
config>router>bgp
Supported on all 7210 SAS platforms as described in this document
This command enables BGP rapid update for specified address families.
If rapid update is enabled for a set of address families, and a route belonging to a family in that set is received by the router and chosen for propagation to specific BGP peers, the remaining time on the MRAI timer of these peers is ignored and the route is transmitted immediately, along with all other pending routes for these peers, including routes of address families not specified in the rapid-update command.
The rapid-update command overrides the peer-level time and applies the minimum setting of 0 seconds to routes belonging to specified address families; routes of other address families continue to be advertised according to the session-level MRAI setting.
The no form of this command disables rapid update for all address families.
no rapid-update
Keyword to enable the BGP rapid update for the 12-byte Virtual Switch Instance identifier (VSI-ID) value, which consists of the 8-byte route distinguisher (RD) followed by a 4-byte value.
Keyword to enable the BGP rapid update for the MVPN-IPv4 address family. The MVPN-IPv4 address is a variable size value consisting of the 1-byte route type, 1-byte length, and variable size that is route type specific. Route type defines encoding for the route type specific field. Length indicates the length in octets of the route type specific field.
This keyword is supported only on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), and 7210 SAS-T (network). This family is not supported for 7210 SAS-Sx 10/100GE devices.
Keyword to enable the BGP rapid update for the EVPN address family by including EVPN routes from the set of routes that can trigger rapid update. This keyword is supported only on the 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12.
[no] rapid-withdrawal
config>router>bgp
Supported on all 7210 SAS platforms as described in this document
This command disables the delay (Minimum Route Advertisement) on sending BGP withdrawals. Normal route withdrawals may be delayed up to the minimum route advertisement to allow for efficient packing of BGP updates.
The no form of this command removes this command from the configuration and reverts withdrawal processing to the normal behavior.
no rapid-withdrawal
prefix-limit limit [log-only] [threshold percentage]
no prefix-limit
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command configures the maximum number of routes BGP can learn from a peer.
When the number of routes reaches 90% of this limit, an SNMP trap is sent. When the limit is exceeded, the BGP peering is dropped and disabled.
The no form of this command removes the configuration.
no prefix-limit
Specifies the number of routes that can be learned from a peer, expressed as a decimal integer.
Keyword that enables the warning message to be sent at the specified threshold percentage, and also when the limit is exceeded. However, the BGP peering is not dropped.
Specifies the threshold value (as a percentage) that triggers a warning message to be sent.
[no] remove-private [limited]
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command enables private ASNs to be removed from the AS path before advertising them to BGP peers.
When this command is set at the global level, it applies to all peers regardless of group or neighbor configuration. When the command is set at the group level, it applies to all peers in the group regardless of the neighbor configuration.
7210 SAS software recognizes the set of ASNs that are defined by IANA as private. These are ASNs in the range of 64512 through 65535, inclusive.
The no form of this command used at the global level reverts to the default value.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
no remove-private
Optional keyword that removes private ASNs up to the first public ASN encountered, at which point it stops removing private ASNs.
router-id ip-address
no router-id
config>router>bgp
Supported on all 7210 SAS platforms as described in this document
This command specifies the router ID to be used with this BGP instance.
Changing the BGP router ID on an active BGP instance causes the BGP instance to restart with the new router ID. The router ID must be set to a valid host address. By default, no router ID is configured for BGP; the system interface IP address is used.
Specifies the router ID, expressed in dotted decimal notation. Allowed value is a valid routable IP address on the router, either an interface or system IP address. Nokia highly recommends that this address be the system IP address.
[no] shutdown
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.
The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.
Unlike other commands and parameters where the default state is not indicated in the configuration file, the shutdown and no shutdown states are always indicated in system-generated configuration files.
Default administrative states for services and service entities are described in Special Cases.
The no form of this command places an entity in an administratively enabled state.
On all 7210 SAS platforms, BGP is created in the no shutdown state.
On the 7210 SAS-Mxp, the protocol is handled as follows.
The configure router bgp command instantiates the protocol in the no shutdown state, and resources are allocated to enable the node to process the protocol.
To deallocate resources, issue the configure router bgp shutdown and configure router no bgp commands to allow the node to boot up correctly after the reboot. It is not sufficient to only issue a configure router bgp shutdown command.
The resources for BGP are allocated when the BGP context is enabled either in the base routing instance or the VPRN service instance. Resources are deallocated when the configuration of the last BGP context under either base routing instances or VPRN service is removed or shut down.
The BGP protocol is created in the no shutdown state on all 7210 SAS platforms.
BGP groups are created in the no shutdown state.
BGP neighbors/peers are created in the no shutdown state.
[no] type {internal | external}
config>router>bgp>group
config>router>bgp>group>neighbor
Supported on all 7210 SAS platforms as described in this document
This command designates the BGP peer as type internal or external.
Specifying the internal parameter type indicates the peer is an iBGP peer; specifying the external parameter type indicates the peer is an eBGP peer.
By default, 7210 SAS derives the type of neighbor based on the local AS specified. If the local AS specified is the same as the AS of the router, the peer is considered internal. If the local AS is different, the peer is considered external.
The no form of this command used at the group level reverts to the default value.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
no type
Keyword that configures the peer as internal.
Keyword that configures the peer as external.