Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
edgerouter:bgp [2018/05/15 18:49]
brielle
edgerouter:bgp [2018/05/15 18:57] (current)
brielle
Line 148: Line 148:
 } }
 </​code>​ </​code>​
 +
 +In the above example, our local router has the IPv4 address of 100.64.100.2 and the IPv6 address of fd00::2 with an ASN of 65501. ​ The BGP enabled router on our ISP side is 100.64.100.1 and fd00::1 with an ASN of 65502. ​ We are assuming that our routers are connected over a non-shared link within one hop.  If the BGP router is more than one hop away, you need to configure '​ebgp-multihop'​ with the appropriate amount of hops away your ISP's router is.
 +
 +===== Showing BGP Information =====
 +<​code>​user@router1:​~$ show ip bgp neighbor
 +BGP neighbor is 100.64.100.2,​ remote AS 65502, local AS 65501, external link
 +  BGP version 4, remote router ID 100.64.100.2
 +  BGP state = Established,​ up for 01w0d05h
 +  Last read 01w0d05h, hold time is 90, keepalive interval is 30 seconds
 +  Neighbor capabilities:​
 +    Route refresh: advertised and received (old and new)
 +    4-Octet ASN Capability: advertised and received
 +    Address family IPv4 Unicast: advertised and received
 +    Address family IPv4 Multicast: received
 +  Received 2838376 messages, 0 notifications,​ 0 in queue
 +  Sent 20788 messages, 0 notifications,​ 0 in queue
 +  Route refresh request: received 0, sent 0
 +  Minimum time between advertisement runs is 30 seconds
 +  Update source is 100.64.100.1
 + For address family: IPv4 Unicast
 +  BGP table version 6603726, neighbor version 6603716
 +  Index 2, Offset 0, Mask 0x4
 +  Inbound soft reconfiguration allowed
 +  Community attribute sent to this neighbor (both)
 +  Inbound path policy configured
 +  Outbound path policy configured
 +  Route map for incoming advertisements is *BGP-ISP-From
 +  Route map for outgoing advertisements is *BGP-ISP-To
 +  688930 accepted prefixes
 +  1 announced prefixes
 +
 + ​Connections established 1; dropped 0
 +  External BGP neighbor may be up to 1 hops away.
 +Local host: 100.64.100.2,​ Local port: 60803
 +Foreign host: 100.64.100.1,​ Foreign port: 179
 +Nexthop: 100.64.100.1
 +BGP connection: shared network
 +
 +BGP neighbor is fd00::1, remote AS 65502, local AS 65501, external link
 +  BGP version 4, remote router ID 100.64.100.1
 +  BGP state = Established,​ up for 01w0d05h
 +  Last read 01w0d05h, hold time is 180, keepalive interval is 60 seconds
 +  Neighbor capabilities:​
 +    Route refresh: advertised and received (old and new)
 +    4-Octet ASN Capability: advertised and received
 +    Address family IPv4 Unicast: advertised
 +    Address family IPv6 Unicast: advertised and received
 +  Received 686685 messages, 0 notifications,​ 0 in queue
 +  Sent 10394 messages, 0 notifications,​ 0 in queue
 +  Route refresh request: received 0, sent 0
 +  Minimum time between advertisement runs is 30 seconds
 +  Update source is fd00::2
 + For address family: IPv4 Unicast
 +  BGP table version 6603726, neighbor version 6603716
 +  Index 1, Offset 0, Mask 0x2
 +  Inbound soft reconfiguration allowed
 +  Community attribute sent to this neighbor (both)
 +  0 accepted prefixes
 +  0 announced prefixes
 +
 + For address family: IPv6 Unicast
 +  BGP table version 858622, neighbor version 858620
 +  Index 1, Offset 0, Mask 0x2
 +  Community attribute sent to this neighbor (both)
 +  Inbound path policy configured
 +  Outbound path policy configured
 +  Route map for incoming advertisements is *BGP-ISPv6-From
 +  Route map for outgoing advertisements is *BGP-ISPv6-To
 +  49892 accepted prefixes
 +  1 announced prefixes
 +
 + ​Connections established 1; dropped 0
 +Local host: fd00::2, Local port: 179
 +Foreign host: fd00::1, Foreign port: 8044
 +Nexthop: 100.64.100.1
 +Nexthop global: fd00::1
 +BGP connection: shared network
 +</​code>​
 +
  • edgerouter/bgp.txt
  • Last modified: 2018/05/15 18:57
  • by brielle