Last Updated on August 6, 2021 by Admin 3
DRAG DROP
Select each BGP command on the left, and drag it o its corresponding description on the right.
The show ip bgp neighbors command displays the number of keepalive messages exchanged between Border Gateway Protocol (BGP) peers. The keepalive statistics are displayed within the Message statistics block of output. Additional information provided by the show ip bgp neighbors command includes detailed neighbor path, prefix, capability, and attribute information.
The following is sample output from the show ip bgp neighbors command:
The clear ip bgp command rebuilds the BGP routing table. This command can be used to begin soft reconfiguration or a hard reset. Soft reconfiguration uses stored prefix information in order to rebuild BGP routing tables without breaking down any active peering sessions, whereas a hard reset breaks down the active peering sessions and then rebuilds the BGP routing tables.
The aggregateaddress command indicates a summarized route that should be advertised. The syntax of the aggregateaddress command is aggregateaddressipaddresssubnetmask [summaryonly] [asset]. Typically, the aggregateaddresscommand is issued with the optional summaryonly keyword, which prevents the advertisement of routes with longer prefixes within the summarized range. The optional asset keyword enables BGP to detect loops by generating an aggregate address mathematically from a set of autonomous systems (ASes). You can determine whether an aggregate address has been calculated from a set of ASes by examining the output of the show ip bgp command. For example, the following output displays an aggregate address that summarizes AS 600 by using paths through AS 500 and AS 400:
The show ip bgp summary command displays the session state. You can also use the show ip bgp summary command to determine neighbor path, prefix, capability, and attribute information. If the output indicates that network entries and path entries are consuming a lot of memory, the BGP database might be too large; this can occur when the router is attempting to store the entire global BGP routing table. The following is sample output from the show ip bgp summary command: