n7k Unicast Config Basic BGP
n7k Unicast Config Basic BGP
destination while detecting and avoiding paths with routing loops. The routing information includes the actual
route prefix for a destination, the path of autonomous systems to the destination, and additional path attributes.
BGP selects a single path, by default, as the best path to a destination host or network. Each path carries
well-known mandatory, well-known discretionary, and optional transitive attributes that are used in BGP
best-path analysis. You can influence BGP path selection by altering some of these attributes by configuring
BGP policies.
BGP also supports load balancing or equal-cost multipath (ECMP).
For information on configuring BGP in an MPLS network, see the Cisco Nexus 7000 Series NX-OS MPLS
Configuration Guide.
Administrative Distance
An administrative distance is a rating of the trustworthiness of a routing information source. By default, BGP
uses the administrative distances shown in the table.
Note The administrative distance does not influence the BGP path selection algorithm, but it does influence whether
BGP-learned routes are installed in the IP routing table.
BGP Peers
A BGP speaker does not discover another BGP speaker automatically. You must configure the relationships
between BGP speakers. A BGP peer is a BGP speaker that has an active TCP connection to another BGP
speaker.
BGP Sessions
BGP uses TCP port 179 to create a TCP session with a peer. When a TCP connection is established between
peers, each BGP peer initially exchanges all of its routes—the complete BGP routing table—with the other
peer. After this initial exchange, the BGP peers send only incremental updates when a topology change occurs
in the network or when a routing policy change occurs. In the periods of inactivity between these updates,
peers exchange special messages called keepalives. The hold time is the maximum time limit that can elapse
between receiving consecutive BGP update or keepalive messages.
Cisco NX-OS supports the following peer configuration options:
• Individual IPv4 or IPv4 address—BGP establishes a session with the BGP speaker that matches the
remote address and AS number.
• IPv4 or IPv6 prefix peers for a single AS number—BGP establishes sessions with BGP speakers that
match the prefix and the AS number.
• Dynamic AS number prefix peers—BGP establishes sessions with BGP speakers that match the prefix
and an AS number from a list of configured AS numbers.
Note The dynamic AS number prefix peer configuration overrides the individual AS number configuration that is
inherited from a BGP template.
Note Beginning with Cisco NX-OS Release 6.1, BGP supports sending and receiving multiple paths per prefix and
advertising such paths.
The best-path algorithm runs each time that a path is added or withdrawn for a given network. The best-path
algorithm also runs if you change the BGP configuration. BGP selects the best path from the set of valid paths
available for a given network.
Beginning with Cisco NX-OS Release 8.4(1), the behavior of the BGP pre-best path point of insertion (POI)
is changed. In this release, the NX-OS RPM, BGP, and HMM software uses a single cost community ID
(either 128 for internal routes or 129 for external routes) to identify a BGP VPNv4 route as an EIGRP originated
route.
Only the routes that have the pre-best path value set to cost community ID 128 or 129 are installed in the
URIB along with the cost extcommunity. Any non-eigrp originated route carrying the above described cost
community ID would be installed in URIB along with pre-best path cost community. As a result, URIB would
use this cost to identify the better route between the route learnt through the iBGP and backdoor-EIGRP
instead of the administrative distance.
Cisco NX-OS implements the BGP best-path algorithm in the following steps:
1. Compares two paths to determine which is better.
2. Explores all paths and determines in which order to compare the paths to select the overall best path.
3. Determines whether the old and new best paths differ enough so that the new best path should be used.
Note The order of comparison determined in Part 2 is important. Consider the case where you have three paths, A,
B, and C. When Cisco NX-OS compares A and B, it chooses A. When Cisco NX-OS compares B and C, it
chooses B. But when Cisco NX-OS compares A and C, it might not choose A because some BGP metrics
apply only among paths from the same neighboring autonomous system and not among all paths.
The path selection uses the BGP AS-path attribute. The AS-path attribute includes the list of autonomous
system numbers (AS numbers) traversed in the advertised path. If you subdivide your BGP autonomous system
into a collection or confederation of autonomous systems, the AS-path contains confederation segments that
list these locally defined autonomous systems.
3. Cisco NX-OS chooses the path with the highest local preference.
4. If one of the paths is locally originated, Cisco NX-OS chooses that path.
5. Cisco NX-OS chooses the path with the shorter AS path.
Note When calculating the length of the AS-path, Cisco NX-OS ignores confederation segments and counts AS
sets as 1.
6. Cisco NX-OS chooses the path with the lower origin. Interior Gateway Protocol (IGP) is considered
lower than EGP.
7. Cisco NX-OS chooses the path with the lower multiexit discriminator (MED).
You can configure a number of options that affect whether or not this step is performed. In general,
Cisco NX-OS compares the MED of both paths if the paths were received from peers in the same
autonomous system; otherwise, Cisco NX-OS skips the MED comparison.
You can configure Cisco NX-OS to always perform the best-path algorithm MED comparison, regardless
of the peer autonomous system in the paths. Otherwise, Cisco NX-OS performs a MED comparison
that depends on the AS-path attributes of the two paths being compared:
a. If a path has no AS-path or the AS-path starts with an AS_SET, the path is internal and Cisco NX-OS
compares the MED to other internal paths.
b. If the AS-path starts with an AS_SEQUENCE, the peer autonomous system is the first AS number
in the sequence and Cisco NX-OS compares the MED to other paths that have the same peer
autonomous system.
c. If the AS-path contains only confederation segments or starts with confederation segments followed
by an AS_SET, the path is internal and Cisco NX-OS compares the MED to other internal paths.
d. If the AS-path starts with confederation segments that are followed by an AS_SEQUENCE, the
peer autonomous system is the first AS number in the AS_SEQUENCE and Cisco NX-OS compares
the MED to other paths that have the same peer autonomous system.
Note If Cisco NX-OS receives no MED attribute with the path, Cisco NX-OS considers the MED to be 0 unless
you configure the best-path algorithm to set a missing MED to the highest possible value.
e. If the non-deterministic MED comparison feature is enabled, the best-path algorithm uses the Cisco
IOS style of MED comparison.
8. If one path is from an internal peer and the other path is from an external peer, Cisco NX-OS chooses
the path from the external peer.
9. If the paths have different IGP metrics to their next-hop addresses, Cisco NX-OS chooses the path with
the lower IGP metric.
10. Cisco NX-OS uses the path that was selected by the best-path algorithm the last time it was run.
11. If all path parameters in Step 1 through Step 9 are the same, and there is no current best path (for example,
the current best path can be lost when the neighbor that offers the current best path goes down), then
the route from the BGP router with the lowest router ID is chosen. If the path includes an originator
attribute, Cisco NX-OS uses that attribute as the router ID to compare to; otherwise, Cisco NX-OS uses
the router ID of the peer that sent the path. If the paths have different router IDs, Cisco NX-OS chooses
the path with the lower router ID.
Note When using the attribute originator as the router ID, it is possible that two paths have the same router ID. It
is also possible to have two BGP sessions with the same peer router, so you could receive two paths with the
same router ID.
12. Cisco NX-OS selects the path with the shorter cluster length. If a path was not received with a cluster
list attribute, the cluster length is 0.
13. Cisco NX-OS chooses the path received from the peer with the lower IP address. Locally generated
paths (for example, redistributed paths) have a peer IP address of 0.
Note Paths that are equal after Step 9 can be used for multipath if you configure multipath.
PIC core ensures fast convergence for BGP routes when there is a link or node failure in the core that causes
a change in the IGP reachability to a remote BGP next-hop address.
PIC edge ensures fast convergence to a BGP backup path when an external (eBGP) edge link or an external
neighbor node fails.
BGP PIC IPv4 Unicast IPv6 Unicast VPNv4 (per VPNv6 (per VPNv4 (per VPNv6 (per
prefix) prefix) VRF) VRF)
BGP PIC IPv4 Unicast IPv6 Unicast VPNv4 (per VPNv6 (per VPNv4 (per VPNv6 (per
prefix) prefix) VRF) VRF)
For additional considerations when using BGP PIC core in MPLS networks, see the Cisco Nexus 7000 Series
NX-OS MPLS Configuration Guide.
Note From Cisco NX-OS Release 7.3(0)D1(1) onwards BGP PIC Edge feature supports both IPv4 and IPv6 address
families.
If BGP PIC edge is configured, BGP calculates an additional second best-path (the backup path) along with
the primary best-path. BGP installs both best and backup paths for the prefixes with PIC support into the BGP
RIB. BGP also downloads the backup path along with the RNH via APIs to the URIB, which then updates
the FIB with the next hop marked as a backup. The backup path provides a fast reroute mechanism to counter
a singular network failure.
This feature detects both the local interface failure and remote interface/link failure and triggers the use of
the backup path.
In this example, S3 advertises to S2 the prefixes Z1…Zn to reach with itself as the next hop. BGP on S2, with
BGP PIC feature enabled, installs both bestpath (via S4) and backup path (via S3/S5) towards the AS6500
into the RIB and then the RIB downloads both routes to the FIB.
When the S2-S4 link goes down, the FIB on S2 detects the link failure. It automatically switches from the
primary path to the backup/alternate and points to the new next hop S3. Traffic is quickly rerouted due to the
local fast re-convergence in FIB. After learning the link failure event, BGP on S2 recomputes the bestpath
(which is the previous backup path), removing the next hop S4 from RIB and reinstalling S3 as the primary
next hop into RIB. It also computes a new backup/alternate path, if any, and notifies RIB. With the support
of the BGP PIC feature, the FIB can switch to the available backup route instantly upon detection of link
failure on the primary route without waiting for BGP to select new bestpath and converge, and achieve a fast
reroute.
In the above topology, there are six paths for a given prefix as follows:
• eBGP paths: e1, e2, e3
• iBGP paths: i1, i2, i3
BGP Virtualization
BGP supports virtual routing and forwarding (VRF) instances. VRFs exist within virtual device contexts
(VDCs). By default, Cisco NX-OS places you in the default VDC and default VRF unless you specifically
configure another VDC and VRF. For more information, see the Cisco Nexus 7000 Series NX-OS Virtual
Device Context Configuration Guide.
• You must configure at least one IGP that is capable of recursive next-hop resolution.
• You must configure an address family under a neighbor for the BGP session establishment.
Default Settings
Table 2: Default BGP Parameters
Parameters Default
BGP supports Virtual Routing and Forwarding (VRF). You can configure BGP within the appropriate VRF
if you are using VRFs in your network.
This example shows how to enter VRF configuration mode:
switch(config)# router bgp 64497
switch(config-router)# vrf vrf_A
switch(config-router-vrf)#
You must configure the address families if you are using route redistribution, address aggregation, load
balancing, and other advanced features.
The following example shows how to enter address family configuration mode from the router configuration
mode:
switch(config)# router bgp 64496
switch(config-router)# address-family ipv6 unicast
switch(config-router-af)#
The following example shows how to enter VRF address family configuration mode if you are using VRFs:
The following example shows how to enter VRF neighbor configuration mode:
switch(config)# router bgp 64497
switch(config-router)# vrf vrf_A
switch(config-router-vrf)# neighbor 192.0.2.1
switch(config-router-vrf-neighbor)#
This example shows how to enter VRF neighbor address family configuration mode:
switch(config)# router bgp 64497
switch(config-router)# vrf vrf_A
switch(config-router-vrf)# neighbor 209.165.201.1
switch(config-router-vrf-neighbor)# address-family ipv4 unicast
switch(config-router-vrf-neighbor-af)#
Note If you are familiar with the Cisco IOS CLI, be aware that the Cisco NX-OS commands for this feature might
differ from the Cisco IOS commands that you would use.
Enabling BGP
You must enable BGP before you can configure BGP.
Procedure
Step 3 (Optional) switch(config)# show feature (Optional) Displays enabled and disabled
features.
Step 4 (Optional) switch(config)# copy Saves the change persistently through reboots
running-config startup-config and restarts by copying the running
configuration to the startup configuration.
Procedure
Step 2 switch(config)# router Enables BGP and assigns the AS number to the
bgpautonomous-system-number local BGP speaker. The AS number can be a
16-bit integer or a 32-bit integer in the form of
a higher 16-bit decimal number and a lower
16-bit decimal number in xx.xx format.
Use the no form of this command to disable this
feature.
Step 3 switch(config-router)# router-id ip-address (Optional) Configures the BGP router ID. This
IP address identifies this BGP speaker.
Step 6 switch(config-router-af)# show bgp all (Optional) Displays information about all BGP
address families.
Step 7 (Optional) switch(config)# copy Saves the change persistently through reboots
running-config startup-config and restarts by copying the running
configuration to the startup configuration.
Example
This example shows how to enable BGP with the IPv4 unicast address family and manually add one
network to advertise:
switch# configure terminal
switch(config)# router bgp 64496
switch(config-router)# address-family ipv4 unicast
switch(config-router-af)# network 192.0.2.0
switch(config-router-af)# copy running-config startup-config
Procedure
Procedure
Note You must configure the address family under neighbor configuration mode for each peer.
Procedure
Step 2 switch(config)# router bgp Enables BGP and assigns the AS number to
autonomous-system-number the local BGP speaker. The AS number can be
a 16-bit integer or a 32-bit integer in the form
of a higher 16-bit decimal number and a lower
16-bit decimal number in xx.xx format.
Step 3 switch(config-router)# neighbor {ip-address Configures the IPv4 or IPv6 address and AS
| ipv6-address} remote-as as-number number for a remote BGP peer. The ip-address
format is x.x.x.x. The ipv6-address format is
A:B::C:D.
Step 5 switch(config-router-neighbor)# timers (Optional) Adds the keepalive and hold time
keepalive-time hold-time BGP timer values for the neighbor. The range
is from 0 to 3600 seconds. The default is 60
seconds for the keepalive time and 180 seconds
for the hold time.
Example
The following example shows how to configure a BGP peer:
switch# configure terminal
switch(config)# router bgp 64496
switch(config-router)# neighbor 192.0.2.1 remote-as 64497
switch(config-router-neighbor)# description Peer Router B
switch(config-router-neighbor)# address-family ipv4 unicast
Procedure
Step 3 (Optional) switch(config)# copy Saves the change persistently through reboots
running-config startup-config and restarts by copying the running
configuration to the startup configuration.
Example
The following example configures AS numbers in asdot notation.
Procedure
Step 2 switch(config)# router bgp Enables BGP and assigns the AS number to the
autonomous-system-number local BGP speaker. The AS number can be a
16-bit integer or a 32-bit integer in the form of
a higher 16-bit decimal number and a lower
16-bit decimal number in xx.xx format.
Step 3 switch(config-router)# neighbor prefix Configures the IPv4 or IPv6 prefix and a route
remote-as route-map map-name map for the list of accepted AS numbers for the
remote BGP peers. The prefix format for IPv4
is x.x.x.x/length. The length range is from 1 to
32. The prefix format for IPv6 is
A:B::C:D/length. The length range is from 1 to
128.
The map-name can be any case-sensitive,
alphanumeric string up to 63 characters.
Example
This example shows how to configure dynamic AS numbers for a prefix peer:
switch# configure terminal
switch(config)# route-map BGPPeers
switch(config-route-map)# match as-number 64496, 64501-64510
switch(config-route-map)# match as-number as-path-list List1, List2
switch(config-route-map)# exit
switch(config)# router bgp 64496
switch(config-router)# neighbor 192.0.2.0/8 remote-as route-map BGPPeers
switch(config-router-neighbor)# description Peer Router B
switch(config-router-neighbor)# address-family ipv4 unicast
switch(config-router-neighbor-af)# copy running-config startup-config
Note The BGP PIC Edge feature only supports IPv4 address families.
Procedure
Step 2 Enable BGP and assign the autonomous system number to the local BGP speaker:
switch(config)# router bgp autonomous-system-number
Step 3 Enter router address family configuration mode for the IPv4 unicast address family:
switch(config-router)# address-family ipv4 unicast
Step 4 Enable BGP to install the backup path to the routing table:
switch(config-router-af)# additional-paths install backup
Example
This example shows how to configure the device to support BGP PIC Edge in IPv4 network:
interface Ethernet2/2
ip address 1.1.1.5/24
no shutdown
interface Ethernet2/3
ip address 2.2.2.5/24
no shutdown
If BGP receives the same prefix (for example, 99.0.0.0/24) from the two neighbors 1.1.1.6 and 2.2.2.6,
both paths will be installed in the URIB—one as the primary path and the other as the backup path.
BGP output:
switch(config)# show ip bgp 99.0.0.0/24
BGP routing table information for VRF default, address family IPv4 Unicast
BGP routing table entry for 99.0.0.0/24, version 4
Path type: internal, path is valid, not best reason: Internal path, backup path
AS-Path: 200 , path sourced external to AS
2.2.2.6 (metric 0) from 2.2.2.6 (2.2.2.6)
Origin IGP, MED not set, localpref 100, weight 0
Advertised path-id 1
Path type: external, path is valid, is best path
AS-Path: 200 , path sourced external to AS
1.1.1.6 (metric 0) from 1.1.1.6 (99.0.0.1)
Origin IGP, MED not set, localpref 100, weight 0
URIB output:
URIB output:
switch(config)# show ip route 99.0.0.0/24
IP Route Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>
UFIB output:
switch# show forwarding route 123.1.1.0 detail module 8
Command Purpose
clear bgp all {neighbor | * | as-number | Clears one or more neighbors from all address
peer-template name | prefix} [vrf vrf-name] families. * clears all neighbors in all address families.
The arguments are as follows:
• neighbor—IPv4 or IPv6 address of a neighbor.
• as-number— Autonomous system number. The
AS number can be a 16-bit integer or a 32-bit
integer in the form of higher 16-bit decimal
number and a lower 16-bit decimal number in
xx.xx format.
• name—Peer template name. The name can be
any case-sensitive, alphanumeric string up to 64
characters.
• prefix—IPv4 or IPv6 prefix. All neighbors within
that prefix are cleared.
• vrf-name—VRF name. All neighbors in that VRF
are cleared. The name can be any case-sensitive,
alphanumeric string up to 64 characters.
clear bgp all dampening [vrf vrf-name] Clears route flap dampening networks in all address
families. The vrf-name can be any case-sensitive,
alphanumeric string up to 64 characters.
clear bgp all flap-statistics [vrf vrf-name] Clears route flap statistics in all address families. The
vrf-name can be any case-sensitive, alphanumeric
string up to 64 characters.
clear bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Clears route flap dampening networks in the selected
multicast} dampening [vrf vrf-name] address family. The vrf-name can be any
case-sensitive, alphanumeric string up to 64
characters.
clear bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Clears route flap statistics in the selected address
multicast} flap-statistics [vrf vrf-name] family. The vrf-name can be any case-sensitive,
alphanumeric string up to 64 characters.
Command Purpose
clear bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {neighbor Clears one or more neighbors from the selected
|* | as-number | peer-template name | prefix} [vrf address family. * clears all neighbors in the address
vrf-name] family. The arguments are as follows:
• neighbor—IPv4 or IPv6 address of a neighbor.
• as-number— Autonomous system number. The
AS number can be a 16-bit integer or a 32-bit
integer in the form of higher 16-bit decimal
number and a lower 16-bit decimal number in
xx.xx format.
• name—Peer template name. The name can be
any case-sensitive, alphanumeric string up to 64
characters.
• prefix—IPv4 or IPv6 prefix. All neighbors within
that prefix are cleared.
• vrf-name—VRF name. All neighbors in that VRF
are cleared. The name can be any case-sensitive,
alphanumeric string up to 64 characters.
clear bgp {ip {unicast | multicast}} {neighbor |* Clears one or more neighbors. * clears all neighbors
|as-number | peer-template name | prefix} [vrf in the address family. The arguments are as follows:
vrf-name]
• neighbor—IPv4 or IPv6 address of a neighbor.
• as-numbe— Autonomous system number. The
AS number can be a 16-bit integer or a 32-bit
integer in the form of higher 16-bit decimal
number and a lower 16-bit decimal number in
xx.xx format.
• name—Peer template name. The name can be
any case-sensitive, alphanumeric string up to 64
characters.
• prefix—IPv4 or IPv6 prefix. All neighbors within
that prefix are cleared.
• vrf-name—VRF name. All neighbors in that VRF
are cleared. The name can be any case-sensitive,
alphanumeric string up to 64 characters.
Command Purpose
clear bgp dampening [ip-neighbor |ip-prefix] [vrf Clears route flap dampening in one or more networks.
vrf-name] The arguments are as follows:
• ip-neighbor—IPv4 address of a neighbor.
• ip-prefix—IPv4. All neighbors within that prefix
are cleared.
• vrf-name—VRF name. All neighbors in that VRF
are cleared. The name can be any case-sensitive,
alphanumeric string up to 64 characters.
clear bgp flap-statistics [ip-neighbor |ip-prefix] [vrf Clears route flap statistics in one or more networks.
vrf-name] The arguments are as follows:
• ip-neighbor—IPv4 address of a neighbor.
• ip-prefix—IPv4. All neighbors within that prefix
are cleared.
• vrf-name—VRF name. All neighbors in that VRF
are cleared. The name can be any case-sensitive,
alphanumeric string up to 64 characters.
clear ip mbgp {ip {unicast | multicast}} {neighbor • neighbor—IPv4 or IPv6 address of a neighbor.
|* |as-number | peer-template name | prefix} [vrf
vrf-name] • as-number— Autonomous system number. The
AS number can be a 16-bit integer or a 32-bit
integer in the form of higher 16-bit decimal
number and a lower 16-bit decimal number in
xx.xx format.
• name—Peer template name. The name can be
any case-sensitive, alphanumeric string up to 64
characters.
• prefix—IPv4 or IPv6 prefix. All neighbors within
that prefix are cleared.
• vrf-name—VRF name. All neighbors in that VRF
are cleared. The name can be any case-sensitive,
alphanumeric string up to 64 characters.
clear ip mbgp dampening [ip-neighbor |ip-prefix] Clears route flap dampening in one or more networks.
[vrf vrf-name] The arguments are as follows:
• ip-neighbor—IPv4 address of a neighbor.
• ip-prefix—IPv4. All neighbors within that prefix
are cleared.
• vrf-name—VRF name. All neighbors in that VRF
are cleared. The name can be any case-sensitive,
alphanumeric string up to 64 characters.
Command Purpose
clear ip mbgp flap-statistics [ip-neighbor |ip-prefix] Clears route flap statistics one or more networks. The
[vrf vrf-name] arguments are as follows:
• ip-neighbor—IPv4 address of a neighbor.
• ip-prefix—IPv4. All neighbors within that prefix
are cleared.
• vrf-name—VRF name. All neighbors in that VRF
are cleared. The name can be any case-sensitive,
alphanumeric string up to 64 characters.
Command Purpose
show bgp all [summary] [vrf vrf-name] Displays the BGP information for all address families.
show bgp convergence [vrf vrf-name] Displays the BGP information for all address families.
show bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Displays the BGP routes that match a BGP
multicast} [ip-address | ipv6-prefix community community.
[regexp expression | [community] [no-advertise]
[no-export] [no-export-subconfed]} [vrf vrf-name]
show bgp [vrf vrf-name] {ipv4 | ipv6 | vpnv4 | Displays the BGP routes that match a BGP community
vpnv6} {unicast | multicast} [ip-address | list.
ipv6-prefix] community-list list-name [vrf vrf-name]
show bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Displays the BGP routes that match a BGP extended
multicast} [ip-address | ipv6-prefix extcommunity community.
[regexp expression | [generic [non-transitive |
transitive] aa4:nn [exact-match]} [vrf vrf-name]
show bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Displays the BGP routes that match a BGP extended
multicast} [ip-address | ipv6-prefix community list.
extcommunity-list list-name [exact-match]} [vrf
vrf-name]
show bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Displays the information for BGP route dampening.
multicast} [ip-address | ipv6-prefix {dampening Use the clear bgp dampening command to clear the
dampened-paths [regexp expression]} [vrf vrf-name] route flap dampening information.
show bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Displays the BGP route history paths.
multicast} [ip-address | ipv6-prefix history-paths
[regexp expression] [vrf vrf-name]
Command Purpose
show bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Displays the information for the BGP filter list.
multicast} [ip-address | ipv6-prefix filter-list
list-name [vrf vrf-name]
show bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Displays the information for BGP peers. Use the clear
multicast} [ip-address | ipv6-prefix] neighbors bgp neighbors command to clear these neighbors.
[ip-address | ipv6-prefix] [vrf vrf-name]
show bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Displays the information for the BGP route next hop.
multicast} [ip-address | ipv6-prefix] neighbors
[ip-address | ipv6-prefix] {nexthop |
nexthop-database} [vrf vrf-name]
show bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Displays the BGP policy information. Use the clear
multicast} [ip-address | ipv6-prefix] policy name [vrf bgp policy command to clear the policy information.
vrf-name]
show bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Displays the BGP routes that match the prefix list.
multicast} [ip-address | ipv6-prefix] prefix-list
list-name [vrf vrf-name]
show bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Displays the BGP paths stored for soft reconfiguration.
multicast} [ip-address | ipv6-prefix] received-paths
[vrf vrf-name]
show bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Displays the BGP routes that match the AS_path
multicast} [ip-address | ipv6-prefix] regexp regular expression.
expression [vrf vrf-name]
show bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Displays the BGP routes that match the route map.
multicast} [ip-address | ipv6-prefix] route-map
map-name [vrf vrf-name]
show bgp peer-policy name [vrf vrf-name] Displays the information about BGP peer policies.
show bgp peer-session name [vrf vrf-name] Displays the information about BGP peer sessions.
show bgp peer-template name [vrf vrf-name] Displays the information about BGP peer templates.
Use the clear bgp peer-template command to clear
all neighbors in a peer template.
show {ipv | ipv6} bgp options Displays the BGP status and configuration
information. This command has multiple options. See
the Cisco Nexus 7000 Series NX-OS Unicast Routing
Command Reference, for more information.
Command Purpose
show {ipv | ipv6} mbgp options Displays the BGP status and configuration
information. This command has multiple options. See
the Cisco Nexus 7000 Series NX-OS Unicast Routing
Command Reference, for more information.
Command Purpose
show bgp {ipv4 | ipv6 | vpnv4 | vpnv6} {unicast | Displays the BGP route flap statistics. Use the clear
multicast} [ip-address | ipv6-prefix] flap-statistics bgp flap-statistics command to clear these statistics.
[vrf vrf-name]
show bgp sessions [vrf vrf-name] Displays the BGP sessions for all peers. Use the clear
bgp sessions command to clear these statistics.
VDCs and VRFs Cisco Nexus 7000 Series NX-OS Virtual Device
Context Configuration Guide, Release 5.x
MIBs
MIBs MIBs Link
BGP4-MIB To locate and download MIBs, go to the following
URL:
CISCO-BGP4-MIB
http://www.cisco.com/public/sw-center/netmgmt/
CISCO-BGP-MIBv2
cmtk/mibs.shtml