Usage Guidelines
Note |
The
set
default-afi command is used to specify the default address family
for the session, and the
set
default-safi command is used to specify the default subaddress
family for the session. See the
System Management Command Reference for Cisco NCS 6000 Series Routers for
detailed information and syntax for the
set
default-afi
and
set
default-safi
commands. If you do not specify a default address family,
the default address family is IPv4. If you do not specify a default subaddress
family, the default subaddress family is unicast.
|
BGP contains a
separate routing table for each configured address family and subaddress family
combination. The address family and subaddress family options specify which
routing table should be examined. If the
all keyword
is specified for address family or subaddress family, each matching routing
table is examined in turn.
Use the
show bgp
neighbors command to display detailed information about all
neighbors or a specific neighbor. Use the
performance-statistics keyword to display
information about the work related to specific neighbors done by the BGP
process.
Use the
show bgp
neighbors command with the
ip-address
received
prefix-filter
argument and keyword to display the Outbound Route Filter
(ORF) received from a neighbor.
Use the
advertised-routes
keyword to display a summary of the routes advertised to the
specified neighbor.
Use the
dampened-routes
keyword to display routes received from the specified neighbor
that have been suppressed due to dampening. For more details, see the
show bgp
dampened-paths
command.
To display
information about flapping routes received from a neighbor, use the
flap-statistics
keyword. For more details, see the
show bgp
flap-statistics
command.
To display the
routes received from a neighbor, use the
routes
keyword. For more details, see the
show
bgp
command.
Use the
show bgp
neighbor
command with the
ip-address
configuration
argument and keyword to display the effective configuration of
a neighbor, including configuration inherited from session groups, neighbor
groups, or af-groups through application of the
use
command. Use the
defaults
keyword to display the value of all configurations for the
neighbor, including default configuration. Use the
nvgen
keyword to display configuration output format of the
show
running-config
command. Output in this format is suitable for cutting and
pasting into a configuration session. Use the
show bgp
neighbors
command with the
ip-address
inheritance
argument and keyword to display the session groups, neighbor
groups, and af-groups from which the specified neighbor inherits configuration.
Examples
The following is
sample output from the
show bgp
neighbors
command:
RP/0/RP0/CPU0:router# show bgp neighbors 10.0.101.1
BGP neighbor is 10.0.101.1, remote AS 2, local AS 1, external link
Description: routem neighbor
Remote router ID 10.0.101.1
BGP state = Established, up for 00:00:56
TCP open mode: passive only
BGP neighbor is 1.1.1.2
Remote AS 300, local AS 100, external link
Remote router ID 0.0.0.0
BGP state = Idle (LC/FIB for the neighbor in reloading)
Last read 00:00:00, Last read before reset 00:05:12
Hold time is 180, keepalive interval is 60 seconds
Configured hold time: 180, keepalive: 60, min acceptable hold time: 3
BFD enabled (session initializing)
Last read 00:00:55, hold time is 180, keepalive interval is 60 seconds
DMZ-link bandwidth is 1000 Mb/s
Neighbor capabilities:
Route refresh: advertised
4-byte AS: advertised and received
Address family IPv4 Unicast: advertised and received
Received 119 messages, 0 notifications, 0 in queue
Sent 119 messages, 22 notifications, 0 in queue
Minimum time between advertisement runs is 60 seconds
For Address Family: IPv4 Unicast
BGP neighbor version 137
Update group: 1.3
Community attribute sent to this neighbor
AF-dependant capabilities:
Outbound Route Filter (ORF) type (128) Prefix-list:
Send-mode: advertised
Receive-mode: advertised
Route refresh request: received 0, sent 0
Policy for incoming advertisements is pass-all
Policy for outgoing advertisements is pass-all
5 accepted prefixes, 5 are bestpaths
Prefix advertised 3, suppressed 0, withdrawn 0, maximum limit 1000000
Threshold for warning message 75%
This table
describes the significant fields shown in the display.
Table 15. show bgp
neighbors Field Descriptions
|
Field
|
Description
|
|
BGP
neighbor
|
IP address
of the BGP neighbor and its autonomous system number. If the neighbor is in the
same autonomous system as the router, then the link between them is internal;
otherwise, it is considered external.
|
|
Description
|
Neighbor
specific description.
|
|
remote AS
|
- Number of the autonomous
system to which the neighbor belongs.
- Range for 2-byte Autonomous
system numbers (ASNs) is 1 to 65535.
- Range for 4-byte Autonomous
system numbers (ASNs) in asplain format is 1 to 4294967295.
- Range for 4-byte Autonomous
system numbers (ASNs) is asdot format is 1.0 to 65535.65535.
|
|
local AS
|
Autonomous
system number of the local system.
- Range for 2-byte Autonomous
system numbers (ASNs) is 1 to 65535.
- Range for 4-byte Autonomous
system numbers (ASNs) in asplain format is 1 to 4294967295.
- Range for 4-byte Autonomous
system numbers (ASNs) is asdot format is 1.0 to 65535.65535.
|
|
internal
link
|
Neighbor
is an internal BGP peer.
|
|
external
link
|
Neighbor
is an external BGP peer.
|
|
Administratively shut down
|
Neighbor
connection is disabled using the
shutdown
command.
|
|
remote
router ID
|
Router ID
(an IP address) of the neighbor.
|
|
Neighbor
under common administration
|
Neighbor
is internal or a confederation peer.
|
|
BGP state
|
Internal
state of this BGP connection.
|
|
BFD
enabled
|
Status of
bidirectional forwarding detection.
|
|
TCP open
mode
|
TCP mode
used in establishing the BGP session. The following valid TCP mode are
supported:
- default—Accept
active/passive connections
- passive-only—Accept only
passive connections
- active-only—Accept only
active connections initiated by the router
|
|
Last read
|
Time since
BGP last read a message from this neighbor.
|
|
hold time
|
Hold time
(in seconds) used on the connection with this neighbor.
|
|
keepalive
interval
|
Interval
for sending keepalives to this neighbor.
|
|
DMZ-link
bandwidth
|
DMZ link
bandwidth for this neighbor.
|
|
Neighbor
capabilities
|
BGP
capabilities advertised and received from this neighbor. The following valid
BGP capabilities are supported:
- Multi-protocol
- Route refresh
- Graceful restart
- Outbound Route Filter (ORF)
type (128) Prefix
|
|
Route
refresh
|
Indicates
that the neighbor supports dynamic soft reset using the route refresh
capability.
|
|
4-byte AS
|
Indicates
that the neighbor supports the 4-byte AS capability.
|
|
Address
family
|
Indicates
that the local system supports the displayed address family capability. If
“received” is displayed, the neighbor also supports the displayed address
family.
|
|
Received
|
Number of
messages received from this neighbor, the number of notification messages
received and processed from this neighbor, and the number of messages that have
been received, but not yet processed.
|
|
Sent
|
Number of
messages sent to this neighbor, the number of notification messages generated
to be sent to this neighbor, and the number of messages queued to be sent to
this neighbor.
|
|
Minimum
time between advertisement runs
|
Advertisement interval (in seconds) for this neighbor.
|
|
For
Address Family
|
Information that follows is specific to the displayed address
family.
|
|
BGP
neighbor version
|
Last
version of the BGP database that was sent to the neighbor for the specified
address family.
|
|
Update
group
|
Update
group to which the neighbor belongs.
|
|
Route
reflector client
|
Indicates
that the local system is acting as a route reflector for this neighbor.
|
|
Inbound
soft reconfiguration allowed
|
Indicates
that soft reconfiguration is enabled for routes received from this neighbor.
| Note
|
If the
neighbor has route refresh capability, then soft configuration received-only
routes are not stored by the local system unless “override route refresh” is
displayed.
|
|
|
eBGP
neighbor with no inbound or outbound policy: defaults to drop
|
Indicates
that the neighbor does not have an inbound or outbound policy configured using
the
route-policy (BGP)
command. Hence, no routes are accepted from or
advertised to this neighbor.
|
|
Private AS
number removed from updates to this neighbor
|
Indicates
that remove-private-AS is configured on the specified address family for this
neighbor.
|
|
NEXT_HOP
is always this router
|
Indicates
that next-hop-self is configured on the specified address family for this
neighbor.
|
|
Community
attribute sent to this neighbor
|
Indicates
that send-community-ebgp is configured on the specified address family for this
neighbor.
|
|
Extended
community attribute sent to this neighbor
|
Indicates
that send-extended-community-ebgp is configured on the specified address family
for this neighbor.
|
|
Default
information originate
|
Indicates
that default-originate is configured on the specified address family for this
neighbor, together with the policy used, if one was specified in the
default-originate configuration. An indication of whether the default route has
been advertised to the neighbor is also shown.
|
|
AF-dependant capabilities
|
BGP
capabilities that are specific to a particular address family. The following
valid AF-dependent BGP capabilities are supported:
- route refresh capability
- route refresh capability
OLD value
|
|
Outbound
Route Filter
|
Neighbor
has the Outbound Route Filter (ORF) capability for the specified address
family. Details of the capabilities supported are also shown:
Send-mode—“advertised” is shown if the local system can send an
outbound route filter to the neighbor. “received” is shown if the neighbor can
send an outbound route filter to the local system.
Receive-mode—“advertised” is shown if the local system can
receive an outbound route filter from the neighbor. “received” is shown if the
neighbor can receive an outbound route filter from the local system.
|
|
Graceful
Restart Capability
|
Indicates
whether graceful restart capability has been advertised to and received from
the neighbor for the specified address family.
|
|
Neighbor
preserved the forwarding state during latest restart
|
Indicates
that when the neighbor connection was last established, the neighbor indicated
that it preserved its forwarding state for the specified address family.
|
|
Local
restart time
|
Restart
time (in seconds) advertised to this neighbor.
|
|
RIB purge
time
|
RIB purge
time (in seconds) used for graceful restarts.
|
|
Maximum
stalepath time
|
Maximum
time (in seconds) a path received from this neighbor may be marked as stale if
the neighbor restarts.
|
|
Remote
Restart time
|
Restart
time received from this neighbor.
|
|
Route
refresh request
|
Number of
route refresh requests sent and received from this neighbor.
|
|
Outbound
Route Filter (ORF)
|
“sent”
indicates that an outbound route filter has been sent to this neighbor.
“received” indicates that an outbound route filter has been received from this
neighbor.
| Note
|
A
received outbound route filter may be displayed using the
show bgp neighbors
command with the
received prefix-filter
keywords.
|
|
|
First
update is deferred until ORF or ROUTE-REFRESH is received
|
If the
local system advertised the receive capability and the neighbor has advertised
send capability, no updates are generated until specifically asked by the
neighbor (using a ROUTE-REFRESH or ORF with immediate request).
|
|
Scheduled
to send the Prefix-list filter
|
Indicates
the local system is due to send an outbound route filter request in order to
receive updates from the neighbor.
|
|
Inbound
path policy
|
Indicates
if an inbound path policy is configured.
|
|
Outbound
path policy
|
Indicates
if an outbound path policy is configured.
|
|
Incoming
update prefix filter list
|
Indicates
a prefix list is configured to filter inbound updates from the neighbor.
|
|
Default
weight
|
Default
weight for routes received from the neighbor.
|
|
Policy for
incoming advertisements
|
Indicates
a route policy is configured to be applied to inbound updates from the
neighbor.
|
|
Policy for
outgoing advertisements
|
Indicates
a route policy is configured to be applied to outbound updates to the neighbor.
|
|
Type
|
Indicates
whether the condition map selects routes that should be advertised, or routes
that should not be advertised:
Exist—Routes advertised if permitted by the condition route map.
Non-exist—Routes advertised if denied by the condition route
map.
|
|
accepted
prefixes
|
Number of
prefixes accepted.
|
|
Prefix
advertised
|
Number of
prefixes advertised to the neighbor during the lifetime of the current
connection with the neighbor.
|
|
suppressed
|
Number of
prefix updates that were suppressed because no transitive attributes changed
from one best path to the next.
| Note
|
Update
suppression occurs only for external BGP neighbors.
|
|
|
withdrawn
|
Number of
prefixes withdrawn from the neighbor during the lifetime of the current
connection with the neighbor.
|
|
maximum
limit
|
Maximum
number of prefixes that may be received from the neighbor. If “(warning-only)”
is displayed, a warning message is generated when the limit is exceeded,
otherwise the neighbor connection is shut down when the limit is exceeded.
|
|
Threshold
for warning message
|
Percentage
of maximum prefix limit for the neighbor at which a warning message is
generated.
|
|
Connections established
|
Number of
times the router has established a BGP peering session with the neighbor.
|
|
dropped
|
Number of
times that a good connection has failed or been taken down.
|
|
Last reset
due to
|
Reason
that the connection with the neighbor was last reset.
|
|
Time since
last notification sent to neighbor
|
Amount of
time since a notification message was last sent to the neighbor.
|
|
Error Code
|
Type of
notification that was sent. The notification data, if any, is also displayed.
|
|
Time since
last notification received from neighbor
|
Amount of
time since a notification message was last received from the neighbor.
|
|
Error Code
|
Type of
notification that was received. The notification data received, if any, is also
displayed
|
|
External
BGP neighbor may be up to <n> hops away
|
Indicates
ebgp-multihop is configured for the neighbor.
|
|
External
BGP neighbor not directly connected
|
Indicates
that the neighbor is not directly attached to the local system.
|
|
Notification data sent:
|
Data
providing more details on the error along with the error notification sent to
the neighbor.
|
The following is
sample output from the
show bgp
neighbors
command with the
advertised-routes
keyword:
RP/0/RP0/CPU0:router# show bgp neighbors 172.20.16.178 routes
BGP router identifier 172.20.16.181, local AS number 1
BGP main routing table version 27
BGP scan interval 60 secs
Status codes: s suppressed, d damped, h history, * valid, > best
i - internal, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 10.0.0.0 172.20.16.178 40 0 10 ?
*> 10.22.0.0 172.20.16.178 40 0 10 ?
The following is
sample output from the
show bgp
neighbors
command with the
routes
keyword:
RP/0/RP0/CPU0:router# show bgp neighbors 10.0.101.1 dampened-routes
BGP router identifier 10.0.0.5, local AS number 1
BGP main routing table version 48
Dampening enabled
BGP scan interval 60 secs
Status codes: s suppressed, d damped, h history, * valid, > best
i - internal, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network From Reuse Path
*d 10.0.0.0 10.0.101.1 00:59:30 2 100 1000 i
*d 11.0.0.0 10.0.101.1 00:59:30 2 100 1000 i
*d 12.0.0.0 10.0.101.1 00:59:30 2 100 1000 i
*d 13.0.0.0 10.0.101.1 00:59:30 2 100 1000 i
*d 14.0.0.0 10.0.101.1 00:59:30 2 100 1000 i
This table
describes the significant fields shown in the display.
Table 16. show bgp
neighbors routes Field Descriptions
|
Field
|
Description
|
|
BGP router
identifier
|
BGP
identifier for the local system.
|
|
local AS
number
|
Autonomous
system number for the local system.
|
|
BGP main
routing table version
|
Last
version of the BGP database that was installed into the main routing table.
|
|
Dampening
enabled
|
Displayed
if dampening is enabled for the routes in this BGP routing table.
|
|
BGP scan
interval
|
Interval
(in seconds) between scans of the BGP table specified by the address family and
subaddress family.
|
|
Status
codes
|
Status of
the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is
stale, indicating that a graceful restart is in progress with the peer from
which the route was learned.
s—Path is
more specific than a locally sourced aggregate route and has been suppressed.
*—Path is
valid.
The second
character may be (in order of precedence):
>—Path
is the best path to use for that network.
d—Path is
dampened.
h—Path is
a history entry, representing a route that is currently withdrawn, but that is
being maintained to preserve dampening information. Such routes should never be
marked as valid.
The third
character may be:
i—Path was
learned by an internal BGP (iBGP) session.
|
|
Origin
codes
|
Origin of
the path. The origin code is displayed at the end of each line in the table. It
can be one of the following values:
i—Path
originated from an Interior Gateway Protocol (IGP) and was advertised with a
network or
aggregate-address
command.
e—Path
originated from an Exterior Gateway Protocol (EGP).
?—Origin
of the path is not clear. Usually, this is a route that is redistributed into
BGP from an IGP.
|
|
Network
|
IP prefix
and prefix length for a network.
|
|
Next Hop
|
IP address
of the next system that is used when a packet is forwarded to the destination
network. An entry of 0.0.0.0 indicates that the router has a non-BGP route to
this network.
|
|
Metric
|
Value of
the interautonomous system metric, otherwise known as the Multi Exit
Discriminator (MED) metric.
|
|
LocPrf
|
Local
preference value. This is used to determine the preferred exit point from the
local autonomous system. It is propagated throughout the local autonomous
system.
|
|
Weight
|
Path
weight. Weight is used in choosing the preferred path to a route. It is not
advertised to any neighbor.
|
|
Path
|
Autonomous
system path to the destination network. At the end of the path is the origin
code for the path.
|
The following is
sample output from the
show bgp
neighbors
command with the
dampened-routes
keyword:
RP/0/RP0/CPU0:router# show bgp neighbors 10.0.101.1 flap-statistics
BGP router identifier 10.0.0.5, local AS number 1
BGP main routing table version 48
Dampening enabled
BGP scan interval 60 secs
Status codes: s suppressed, d damped, h history, * valid, > best
i - internal, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network From Flaps Duration Reuse Path
h 10.1.0.0 10.0.101.1 5008 2d02h 2 5000 1000
h 10.2.0.0 10.0.101.1 5008 2d02h 2 2000 3000
h 10.2.0.0 10.0.101.1 5008 2d02h 2 9000 6000
*d 10.0.0.0 10.0.101.1 5008 2d02h 00:59:30 2 100 1000
h 10.0.0.0/16 10.0.101.1 5008 2d02h 2 100 102
*d 10.11.0.0 10.0.101.1 5008 2d02h 00:59:30 2 100 1000
*d 10.12.0.0 10.0.101.1 5008 2d02h 00:59:30 2 100 1000
*d 10.13.0.0 10.0.101.1 5008 2d02h 00:59:30 2 100 1000
*d 10.14.0.0 10.0.101.1 5008 2d02h 00:59:30 2 100 1000
h 192.168.0.0/16 10.0.101.1 5008 2d02h 2 100 101
This table
describes the significant fields shown in the display.
Table 17. show bgp
neighbors dampened-routes Field Descriptions
|
Field
|
Description
|
|
BGP router
identifier
|
BGP
identifier for the local system.
|
|
local AS
number
|
Autonomous
system number for the local system.
|
|
BGP main
routing table version
|
Last
version of the BGP database that was installed into the main routing table.
|
|
Dampening
enabled
|
Displayed
if dampening is enabled for the routes in this BGP routing table.
|
|
BGP scan
interval
|
Interval
(in seconds) between scans of the BGP table specified by the address family and
subaddress family.
|
|
Status
codes
|
Status of
the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is
stale, indicating that a graceful restart is in progress with the peer from
which the route was learned.
s—Path is
more specific than a locally sourced aggregate route and has been suppressed.
*—Path is
valid.
The second
character may be (in order of precedence):
>—Path
is the best path to use for that network.
d—Path is
dampened.
h—Path is
a history entry, representing a route that is currently withdrawn, but that is
being maintained to preserve dampening information. Such routes should never be
marked as valid.
The third
character may be:
i—Path was
learned by an internal BGP (iBGP) session.
|
|
Origin
codes
|
Origin of
the path. The origin code is displayed at the end of each line in the table. It
can be one of the following values:
i—Path
originated from an Interior Gateway Protocol (IGP) and was advertised with a
network
or
aggregate-address
command.
e—Path
originated from an Exterior Gateway Protocol (EGP).
?—Origin
of the path is not clear. Usually, this is a route that is redistributed into
BGP from an IGP.
|
|
Network
|
IP prefix
and prefix length for a network.
|
|
From
|
Neighbor
from which the route was received.
|
|
Reuse
|
Time (in
hours:minutes:seconds) after which the path is made available.
|
|
Path
|
Autonomous
system path to the destination network. At the end of the path is the origin
code for the path.
|
The following is
sample output from the
show bgp
neighbors
command with the
flap-statistics
keyword:
RP/0/RP0/CPU0:router# show bgp neighbors 10.0.101.2 performance-statistics
BGP neighbor is 10.0.101.2, remote AS 1
Read 3023 messages (58639 bytes) in 3019 calls (time spent: 1.312 secs)
Read throttled 0 times
Processed 3023 inbound messages (time spent: 0.198 secs)
Wrote 58410 bytes in 6062 calls (time spent: 3.041 secs)
Processing write list: wrote 0 messages in 0 calls (time spent: 0.000 secs)
Processing write queue: wrote 3040 messages in 3040 calls (time spent: 0.055 secs)
Received 3023 messages, 0 notifications, 0 in queue
Sent 3040 messages, 0 notifications, 0 in queue
This table
describes the significant fields shown in the display.
Table 18. show bgp
neighbors flap-statistics Field Descriptions
|
Field
|
Description
|
|
BGP route
identifier
|
BGP
identifier for the local system.
|
|
local AS
number
|
Autonomous
system number for the local system.
|
|
BGP main
routing table version
|
Last
version of the BGP database that was installed into the main routing table.
|
|
Dampening
enabled
|
Displayed
if dampening has been enabled for the routes in this BGP routing table.
|
|
BGP scan
interval
|
Interval
(in seconds) between when the BGP process scans for the specified address
family and subaddress family.
|
|
Status
codes
|
Status of
the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is
stale, indicating that a graceful restart is in progress with the peer from
which the route was learned.
s—Path is
more specific than a locally sourced aggregate route and has been suppressed.
*—Path is
valid.
The second
character may be (in order of precedence):
d—Path is
dampened.
h—Path is
a history entry, representing a route that is currently withdrawn, but that is
being maintained to preserve dampening information. Such routes should never be
marked as valid.
The third
character may be:
i—Path was
learned by an internal BGP (iBGP) session.
|
|
Origin
codes
|
Origin of
the path. The origin code is displayed at the end of each line in the table. It
can be one of the following values:
i—Path
originated from an Interior Gateway Protocol (IGP) and was advertised with a
network
command.
e—Path
originated from an Exterior Gateway Protocol (EGP).
?—Origin
of the path is not clear. Usually, this is a route that is redistributed into
BGP from an IGP.
|
|
Network
|
IP prefix
and prefix length for a network.
|
|
From
|
IP address
of the peer that advertised this route.
|
|
Flaps
|
Number of
times the route has flapped.
|
|
Duration
|
Time (in
hours:minutes:seconds) since the router noticed the first flap.
|
|
Reuse
|
Time (in
hours:minutes:seconds) after which the path is made available.
|
|
Path
|
Autonomous
system path to reach the destination network.
|
The following is
sample output from the
show bgp
neighbors
command with the
performance-statistics
keyword:
RP/0/RP0/CPU0:router# show bgp neighbors 10.0.101.2 performance-statistics
BGP neighbor is 10.0.101.2, remote AS 1
Read 3023 messages (58639 bytes) in 3019 calls (time spent: 1.312 secs)
Read throttled 0 times
Processed 3023 inbound messages (time spent: 0.198 secs)
Wrote 58410 bytes in 6062 calls (time spent: 3.041 secs)
Processing write list: wrote 0 messages in 0 calls (time spent: 0.000 secs)
Processing write queue: wrote 3040 messages in 3040 calls (time spent: 0.055 secs)
Received 3023 messages, 0 notifications, 0 in queue
Sent 3040 messages, 0 notifications, 0 in queue
This table
describes the significant fields shown in the display.
Table 19. show bgp
neighbors performance-statistics Field Descriptions
|
Field
|
Description
|
|
Read
|
Indicates
the number of messages received from the neighbor, the total size of received
messages, the number of read operations performed, and the real time spent (in
seconds) by the process performing read operations for this neighbor.
|
|
Read
throttled
|
Number of
times that reading from the TCP connection to this neighbor has been throttled.
Throttling is due to a backlog of messages that have been read but not
processed.
|
|
inbound
messages
|
Number of
read messages that have been processed, and the real time spent processing
inbound messages for this neighbor.
|
|
Wrote
|
Amount of
data that has been sent to this neighbor, number of write operations performed,
and the real time spent by the process performing write operations for this
neighbor.
|
|
Processing
write list
|
Number of
messages written from the write list to this neighbor, number of times the
write list has been processed, and real time spent processing the write list.
| Note
|
Write
lists typically contain only update messages.
|
|
|
Processing
write queue
|
Number of
messages written from the write queue to this neighbor, number of times the
write queue has been processed, and real time spent processing the write queue.
|
|
Received
|
Number of
messages received from this neighbor, number of notification messages received
and processed from this neighbor, and number of messages that have been
received, but not yet processed.
|
|
Sent
|
Number of
messages sent to this neighbor, number of notification messages generated to be
sent to this neighbor, and number of messages queued to be sent to this
neighbor.
|
The following is
sample output from the
show bgp
neighbors
command with the
configuration
keyword:
RP/0/RP0/CPU0:router# show bgp neighbors 10.0.101.1 configuration
neighbor 10.0.101.1
remote-as 2 []
bfd fast-detect []
address-family ipv4 unicast []
policy pass-all in []
policy pass-all out []
policy pass-all in []
policy pass-all out []
This table
describes the significant fields shown in the display.
Table 20. show bgp
neighbors configuration Field Descriptions
|
Field
|
Description
|
|
neighbor
|
IP address
configuration of the neighbor.
|
|
remote-as
|
Remote
autonomous system configured on the neighbor.
|
|
bfd
fast-detect
|
BFD
parameter configured on the neighbor.
|
|
address-family
|
Address
family and subsequent address family configured on the router.
|
|
route-policy pass-all in
|
Route
policy configured for inbound updates.
|
|
route-policy pass-all out
|
Route
policy configured for outbound updates.
|
This sample output
from the
show bgp
neighbor command displays TCP MSS information for the specified
neighbor:
RP/0/RP0/CPU0:router#show bgp neighbor 10.0.0.2
BGP neighbor is 10.0.0.2
Remote AS 1, local AS 1, internal link
Remote router ID 10.0.0.2
BGP state = Established, up for 00:09:17
Last read 00:00:16, Last read before reset 00:00:00
Hold time is 180, keepalive interval is 60 seconds
Configured hold time: 180, keepalive: 60, min acceptable hold time: 3
Last write 00:00:16, attempted 19, written 19
Second last write 00:01:16, attempted 19, written 19
Last write before reset 00:00:00, attempted 0, written 0
Second last write before reset 00:00:00, attempted 0, written 0
Last write pulse rcvd Dec 7 11:58:42.411 last full not set pulse count 23
Last write pulse rcvd before reset 00:00:00
Socket not armed for io, armed for read, armed for write
Last write thread event before reset 00:00:00, second last 00:00:00
Last KA expiry before reset 00:00:00, second last 00:00:00
Last KA error before reset 00:00:00, KA not sent 00:00:00
Last KA start before reset 00:00:00, second last 00:00:00
Precedence: internet
Multi-protocol capability received
Neighbor capabilities:
Route refresh: advertised (old + new) and received (old + new)
Graceful Restart (GR Awareness): advertised and received
4-byte AS: advertised and received
Address family IPv4 Unicast: advertised and received
Received 12 messages, 0 notifications, 0 in queue
Sent 12 messages, 0 notifications, 0 in queue
Minimum time between advertisement runs is 0 secs
TCP Maximum Segment Size 500
For Address Family: IPv4 Unicast
BGP neighbor version 4
Update group: 0.2 Filter-group: 0.1 No Refresh request being processed
Route refresh request: received 0, sent 0
0 accepted prefixes, 0 are bestpaths
Cumulative no. of prefixes denied: 0.
Prefix advertised 0, suppressed 0, withdrawn 0
Maximum prefixes allowed 1048576
Threshold for warning message 75%, restart interval 0 min
AIGP is enabled
An EoR was received during read-only mode
Last ack version 4, Last synced ack version 0
Outstanding version objects: current 0, max 0
Additional-paths operation: None
Send Multicast Attributes
This sample output
from the
show bgp
neighbor command with the
configuration
keyword displays TCP MSS configuration:
RP/0/RP0/CPU0:router#show bgp neighbor 10.0.0.2 configuration
neighbor 10.0.0.2
remote-as 1 []
tcp-mss 400 [n:n1]
address-family IPv4 Unicast []
Feedback