BGP Multisession - Networks Baseline - Cisco Engineers Live

10/24/2016 BGP Multisession ~ << Networks Baseline Cisco Engineers Live >>
Privacy Policy
BGP Multisession
UNDEFINED
UNDEFINEDNo comments
UNDEFINED
categories: BGP
Share This:  Facebook  Twitter  Google+  Stumble  Digg
Introduction
BGP Multisession is the capability of BGP having multiple BGP sessions (and hence TCP sessions)
between one pair of BGP speakers, even if there is only one BGP neighbor statement defined between
the BGP speakers in the configuration. This feature was introduced together with Multi Topology
Routing (MTR). The BGP multisession functionality is needed to make MTR work when BGP is used as
the routing protocol where MTR is enabled.
Introduction to MTR
A topology is defined as an independent routing domain that defines a path that the traffic will take
across a common physical network. Each topology has its own routing table (RIB) and data
forwarding table (CEF table). Figure 1 shows an example network with MTR enabled. There are 3
topologies throughout the network.
Figure1.jpg
BGP and the IGPs have been made MTR-aware, so that they can all exchange prefixes per topology.
For BGP to be able to exchange the prefixes per topology and keep them separated from one another,
one separate BGP session is created between a pair of BGP speakers per topology. At the same time
of introducing topologies, the feature was added for BGP to create one session per address family
shared between a pair of BGP speakers. So, there could be as many BGP sessions as the number of
topologies times the number of address families which are shared between a pair of BGP speakers.
Multisession BGP is explained in the draft draft-ietf-idr-bgp-multisession-05 (expired).
There is always the base topology. The user can further add topologies as needed.
Figure 2 shows the topology used throughout this document.
http://www.networksbaseline.in/2012/07/bgpmultisession.html 1/21
Figure2.jpg
Capability
The multisession capability exchanged in the OPEN message by a BGP speaker indicates if it is
capable of running multisession BGP. The capability code is 131.
Let's have a look at this capability exchanged in the OPEN message, in the topology of Figure 2.
R1#debug ip bgp 10.100.1.2
BGP debugging is on for neighbor 10.100.1.2 for address family: IPv4 Unicast

We clear the BGP session.
BGP: 10.100.1.2 passive rcv OPEN, version 4, holdtime 180 seconds
BGP: 10.100.1.2 passive rcv OPEN w/ OPTION parameter len: 35
BGP: 10.100.1.2 passive rcvd OPEN w/ optional parameter type 2 (Capability) len 4
BGP: 10.100.1.2 passive OPEN has CAPABILITY code: 132, length 2
BGP: 10.100.1.2 passive OPEN has TID CAP for: 2
BGP: 10.100.1.2 passive OPEN has MP_EXT CAP for afi/safi: 1/1
BGP: 10.100.1.2 passive OPEN has ROUTEREFRESH capability(old) for all address
families
BGP: 10.100.1.2 passive OPEN has ROUTEREFRESH capability(new) for all address
families
BGP: 10.100.1.2 passive OPEN has MULTISESSION capability, without grouping
BGP: 10.100.1.2 passive OPEN has 4byte ASN CAP for: 1
BGP: nbr global 10.100.1.2 neighbor does not have IPv4 MDT topology activated
BGP: 10.100.1.2 passive rcvd OPEN w/ remote AS 1, 4byte remote AS 1
R1#show ip bgp neighbors 10.100.1.2
BGP neighbor is 10.100.1.2, remote AS 1, internal link
Neighbor capabilities:
Route refresh: advertised and received(new) on session 1, 2, 3
Fouroctets ASN Capability: advertised and received on session 1, 2, 3
Address family IPv4 Unicast: advertised and received
Multisession Capability: advertised and received
Example of MTR with BGP
Here's an example where MTR is configured for BGP in the network used in this document. Address
family IPv4 has three topologies, base, voice and video.
R1#
!
globaladdressfamily ipv4
topology video
!
topology voice
!
iterface Ethernet0/0
ip address 10.1.1.1 255.255.255.0
!
topology ipv4 unicast voice
!
!
topology ipv4 unicast video
!
!
router bgp 1
!
scope global
neighbor 10.100.1.2 remoteas 1
neighbor 10.100.1.2 updatesource Loopback0
!
addressfamily ipv4
!
topology base
neighbor 10.100.1.2 activate
!
topology voice
bgp tid 32
!
topology video
bgp tid 33
!
!
!
There is only one address family (IPv4) shared between the pair of BGP speakers, but there are 3
shared topologies. This leads to three BGP sessions.
R2#show bgp ipv4 unicast neighbors
BGP neighbor is 10.100.1.1, remote AS 1, internal link
BGP version 4, remote router ID 10.200.200.1
Session state = Established, up for 00:05:43
Last read 00:00:09, last write 00:00:06, hold time is 180, keepalive interval is
60 seconds
BGP multisession with 3 sessions (3 established), first up for 00:05:43
Neighbor sessions:
3 active, is multisession capable
Session: 10.100.1.1 session 1
Topology IPv4 Unicast
Topology IPv4 Unicast voice
Topology IPv4 Unicast video
BGP Multisession without MTR
If MTR is not deployed for BGP, BGP does not have topologies. However, there could still be multiple
address families shared between a pair of BGP speakers. Multisession BGP is enabled by default in
IOS releases where the MTR feature is present, until CSCsz76118. This can lead to multiple sessions
between the the pair of BGP speakers. If there are for example 3 shared address families, then there
could be up to a maximum of 3 BGP sessions. This is a maximum, there could be less than 3 sessions.
It could be 2 or only 1 session. Let's have a look at the reason behind these different possibilities.
In the following example, MTR is not enabled, and the set of shared address families are IPv4, IPv6
and vpnv4. Depending on the way BGP starts up the address families, there will be 1, 2 or 3 sessions.
R1#
router bgp 1
!
addressfamily ipv4
exitaddressfamily
!
addressfamily vpnv4
neighbor 10.100.1.2 sendcommunity extended
exitaddressfamily
!
addressfamily ipv6
exitaddressfamily
R2#
router bgp 1
!
addressfamily ipv4
exitaddressfamily
!
addressfamily vpnv4
exitaddressfamily
!
addressfamily ipv6
exitaddressfamily
Possibility 1 : one BGP session
In this example, the configuration for all 3 address families is added on both routers. We then enable
the neighbor.
R1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#router bgp 1
R1(configrouter)#no neighbor 10.100.1.2 shutdown
%BGP5ADJCHANGE: neighbor 10.100.1.2 Up
R1(configrouter)#end
We see that the BGP OPEN message contains all 3 address families. The result is that BGP opens one
session, containing all 3 address families. AFI/SAFI 1/1 for IPv4 unicast, AFI/SAFI 2/1 for IPv6 unicast
and AFI/SAFI 1/128 for vpnv4.
R2#
BGP: 10.100.1.1 passive open to 10.100.1.2
BGP: ses global 10.100.1.1 (0x461CC60:0) pas Receive OPEN
...
BGP: 10.100.1.1 passive OPEN has ROUTEREFRESH capability(old) for all address
families
BGP: 10.100.1.1 passive OPEN has ROUTEREFRESH capability(new) for all address
families
BGP: ses global 10.100.1.1 (0x461CC60:1) Up
R2#show ip bgp neighbors 10.100.1.1 | include session|address family
Neighbor sessions:
For address family: IPv4 Unicast
For address family: VPNv4 Unicast
Last reset 00:01:57, due to Peer closed the session of session 1
Possibility 2 : two BGP sessions
In this example, we start with the neighbor activated in the first 2 address families.
R1#sh run | s bgp
router bgp 1
!
addressfamily ipv4
exitaddressfamily
!
addressfamily ipv6
exitaddressfamily
R2#sh run | s bgp
router bgp 1
!
addressfamily ipv4
no autosummary
exitaddressfamily
!
addressfamily vpnv4
exitaddressfamily
!
addressfamily ipv6
exitaddressfamily
Neighbor sessions:
We see that there is one BGP session for the 2 address families IPv4 and IPv6.
We now activate the neighbor in address family vpnv4.
R1#conf t
R1(configrouter)#addressfamily vpnv4
R1(configrouteraf)#neighbor 10.100.1.2 activate
R1(configrouteraf)#end
R2#
BGP: ses global 10.100.1.1 (0x4FC2198:0) pas Receive OPEN
...
...
BGP: ses global 10.100.1.1 (0x4FC2198:2) Up
R2#
%BGP5ADJCHANGE: neighbor 10.100.1.1 session 2 Up
We see that the routers created a second BGP session, carrying address family vpnv4. This new
OPEN message only carried AFI/SAFI 1/128. We end up with 2 BGP sessions.
Neighbor sessions:
Route refresh: advertised and received(new) on session 1, 2
Fouroctets ASN Capability: advertised and received on session 1, 2
Message statistics for 10.100.1.1 session 1, state Established:
session 1 member
session 1 member
session 2 member
Possibility 3 : three BGP sessions
In this example, we activate the neighbor in each address family one by one. We start with the
following configuration.
R1#sh run | s bgp
router bgp 1
!
addressfamily ipv4
exitaddressfamily
Neighbor sessions:
R1#conf t
R1(configrouter)#addressfamily ipv6
R1(configrouteraf)# neighbor 10.100.1.2 activate
R2#
...
...
BGP: ses global 10.100.1.1 (0x4FC2198:0) pas Adding topology IPv6 Unicast:base
...
Neighbor sessions:
Route refresh: advertised and received(new) on session 1, 2
Fouroctets ASN Capability: advertised and received on session 1, 2
session 1 member
session 2 member
R1#conf t
R1(configrouter)# addressfamily vpnv4
R1(configrouteraf)# neighbor 10.100.1.2 activate
R2#
...
BGP: ses global 10.100.1.1 (0x3FBFF98:0) pas Receive OPEN
...
...
...
BGP: ses global 10.100.1.1 (0x3FBFF98:0) pas Adding topology VPNv4 Unicast:base
...
Neighbor sessions:
Route refresh: advertised and received(new) on session 1, 2, 3
Fouroctets ASN Capability: advertised and received on session 1, 2, 3
session 1 member
session 2 member
session 3 member
We see that there is one BGP session for each of the 3 address families IPv4, IPv6 and vpnv4.
However, if you now clear the BGP neighbor, then the OPEN message will contain all address
families, leading to one session for all 3 address familes again.
R1#clear ip bgp 10.100.1.2
R2#
...
...
...
BGP: ses global 10.100.1.1 (0x461CC60:0) pas Adding topology IPv4 Unicast:base
BGP: ses global 10.100.1.1 (0x461CC60:0) pas Adding topology VPNv4 Unicast:base
...
Neighbor sessions:
Last reset 00:00:23, due to Peer closed the session of session 3
Multi Session vs Single Session
Multisession BGP is enabled by default in IOS with MTR-capable code, until CSCsz76118 . If you want
to have strictly one session per address family, then configure "transport multisession" for the BGP
neighbor. This will force the OPEN message to contain only one address family. Hence, this will force
one session per address family at all times.
R1#sh run | s bgp
router bgp 1
neighbor 10.100.1.2 transport multisession
!
addressfamily ipv4
exitaddressfamily
!
addressfamily vpnv4
exitaddressfamily
!
addressfamily ipv6
exitaddressfamily
R2#
...
...
...
...
...
BGP: ses global 10.100.1.1 (0x4FC2198:0) pas Adding topology IPv6 Unicast:base
BGP: 10.100.1.1 active went from Idle to Active
...
BGP: 10.100.1.1 active rcvd OPEN w/ optional parameter type 2 (Capability) len 6
BGP: 10.100.1.1 active OPEN has CAPABILITY code: 1, length 4
BGP: 10.100.1.1 active OPEN has MP_EXT CAP for afi/safi: 1/128
...
BGP: 10.100.1.1 active rcvd OPEN w/ optional parameter type 2 (Capability) len 3
BGP: 10.100.1.1 active OPEN has CAPABILITY code: 131, length 1
BGP: 10.100.1.1 active OPEN has MULTISESSION capability, without grouping
R2 received 3 separate OPEN messages, each containing one of the 3 address families. Hence, this
forces one session per address family.
Hower, if MTR is not used, one can revert back to the old behavior of always having only one BGP
session between a pair of BGP speakers by configuring the following command neighbor x.x.x.x
transport single-session under router bgp.
R1#conf t
R1(configrouter)# neighbor 10.100.1.2 transport singlesession
R1(configrouter)#end
Neighbor sessions:
1 active, is multisession capable (disabled)
Multisession Capability: and received
Last reset 00:00:51, due to Capability changed of session 3
Benefits of Multisession BGP
Multisession BGP allows more granularity in managing BGP.

In one of the previous examples we saw one benefit of multisession BGP, namely that address
families can be added incrementally to a pair of BGP speakers, without having BGP to reset
completely between the pair of speakers and therefore resetting all the address families.
When address families are each on a separate TCP session, one can have the opportunity to reset
only one TCP session and hence only one address family between a pair of BGP speakers without
interrupting the other address families.
Also, if BGP receives a malformed update, it needs to reset the session. In the case of one session per
address family, then only the session for the address family where the malformed update was seen,
needs to be reset. At the same time, the other sessions are left intact.
In the last example, there were 3 BGP sessions, hence 3 TCP sessions, between the pair of BGP
speakers.
R2#show tcp brief
TCB Local Address Foreign Address (state)
04FA2BB0 10.100.1.2.179 10.100.1.1.19690 ESTAB
049AFD98 10.100.1.2.37284 10.100.1.1.179 ESTAB
03FBF968 10.100.1.2.179 10.100.1.1.56475 ESTAB
TCP port 179 is the port used by BGP. So, these 3 TCP sessions are BGP sessions. Let's have a look at
one of them.
R2#show tcp tcb 04FA2BB0
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Connection is ECN Disabled
Mininum incoming TTL 0, Outgoing TTL 255
Local host: 10.100.1.2, Local port: 179
Foreign host: 10.100.1.1, Foreign port: 19690
Connection tableid (VRF): 0
Enqueued packets for retransmit: 0, input: 0 misordered: 0 (0 bytes)
Event Timers (current time is 0x839E68):
Timer Starts Wakeups Next
Retrans 4 0 0x0
TimeWait 0 0 0x0
AckHold 3 1 0x0
SendWnd 0 0 0x0
KeepAlive 0 0 0x0
GiveUp 0 0 0x0
PmtuAger 0 0 0x0
DeadWait 0 0 0x0
Linger 0 0 0x0
iss: 3729262629 snduna: 3729262774 sndnxt: 3729262774 sndwnd: 16240
irs: 4070011050 rcvnxt: 4070011195 rcvwnd: 16240 delrcvwnd: 144
SRTT: 124 ms, RTTO: 1405 ms, RTV: 1281 ms, KRTT: 0 ms
minRTT: 0 ms, maxRTT: 300 ms, ACK hold: 200 ms
Status Flags: passive open, gen tcbs
Option Flags: nagle, path mtu capable
Datagrams (max data segment is 1460 bytes):
Rcvd: 9 (out of order: 0), with data: 5, total data bytes: 144
Sent: 7 (retransmit: 0 fastretransmit: 0),with data: 5, total data bytes: 144
One could clear only one of these TCP sessions.
R2#clear tcp tcb 04FA2BB0
[confirm]
[OK]
R2#show tcp brief
TCB Local Address Foreign Address (state)
049AFD98 10.100.1.2.37284 10.100.1.1.179 ESTAB
03FBF968 10.100.1.2.179 10.100.1.1.56475 ESTAB
04FA2BB0 10.100.1.2.59982 10.100.1.1.179 ESTAB
We see that one TCP session/BGP session re-established.
New behavior
In later IOS code -code with CSCsz76118- the default behavior is to use single-session. You'll get
multi-session only when explicitely configuring "transport multi-session".
The command neighbor x.x.x.x transport single-session will get removed/obsoleted gradually.It will be
hidden first (by CSCtn66618) and then removed in a later IOS release.
Conclusion:
IOS without MTR feature
A pair of BGP speakers always have one TCP session between them.
IOS with MTR feature, before CSCsz76118
When multi-session is configured, we have one session for each shared address family.
When single-session is configured, there is always only one session.
When in the default mode (no transport session command), there could be one or multiple sessions,
depending on the conditions described above.
IOS after CSCsz76118
By default, the transport mode is single-session, hence there is one session.

When multisession is configured, we have one session for each shared address family.
+1 Recommend this on Google
Related Posts:
BGP Multi-homing: Design and Troubleshooting - Questions and Answers from live
Webcast
BGP Multi-homing Q. Why when we try to set up eBGP peers through interface
loopback, BGP session does not come up even when I use command mult… Read More
Redistributing Internal BGP Routes Into OSPF

Introduction This document shows how to redistribute Internal BGP routes into OSPF process. Like in
other IGP to IGP redistribution the behavior… Read More
Design Inter-Domain Multicast redundancy using MBGP and MSDP

Overview: This document will discuss the design concept and configurations of
redundant Multicast paths between two multi-homed BGP autonomous s… Read More
BGP Multisession
Introduction BGP Multisession is the capability of BGP having multiple BGP sessions (and
hence TCP sessions) between one pair of BGP speakers, ev… Read More
BGP Confederations Erick N.Borgard CCNP With iBGP, every router in the BGP
autonomous system must be fully meshed. The reason for this is be… Read More
Newer Post Home Older Post
0 comments:
Post a Comment
Enter your comment...
Comment as: Unknown (Google) Sign out
Publish Preview Notify me
Links to this post

Links to this post

Create a Link
Subscribe to: Post Comments (Atom)

Popular Posts
OSI Model
The Open Systems Interconnection model ( OSI )is a conceptual model that characterizes
and standardizes the inner functions of a communica...
Secure Socket Layer ( SSL) Connection Setup

SSL (Secure Sockets Layer) is a standard security technology for establishing an
encrypted link between a server and a client—typically a w...
Traceroute
Traceroute, by default, sends a sequence of User Datagram Protocol (UDP) packets
addressed to a destination host; ICMP Echo Request or TCP ...
F5 Load Balancers: LTM vs GTM

F5® BIG-IP® Global Traffic Manager™ (GTM) distributes DNS and user application
requests based on business policies, data center and cloud s...
Comparison of Routers Cisco, Juniper and Huawei

Comparison of Routers Cisco, Juniper and Huawei # Cisco , Juniper and Huawei Router
comparison # CCI E Candidates only # MPLS requireme...
OSPF : "34 Things to remember"

Open Shortest Path First (OSPF) is a routing protocol for Internet Protocol (IP) networks. It uses a link
state routing algorithm and fal...
Cisco ASR 1002-X Basics

Cisco ASR 1002-X # Cisco Routers #CCIE Candidates # ASR Routers Specifications #
Capacity and Utilization # RP and ESP Processors ...
Interview questions for Networking Engineer's( CCNA/CCNP and CCIE candidates )

Please find some of the questions who are preparing for the interviews ( CCNA/CCNP) These are the
questions for the Network Engineer bas...
CISCO-JUNIPER COMMANDS REF

Cisco Command Juniper Command Co-Ordinating Definition show ip interface brief show interface
terse displays the status of interface...
LACP and PAgP

Hi so we have the Following descriptions of all these what is LACP and PAgP. What is Ether Channel?
Ether Channel links shaped while or...

Search Search
TOTAL PAGEVIEWS
1,561,322
BLOG ARCHIVE
Blog Archive
LIKE US !!
NetworksBaseline
82,630 likes
Liked Sign Up
You like this
CATEGORIES
access Lists (3) ADSL (3) Alcatel-Lucent (2) ARP (4) ASA (8) ATM (2) Basic Commands (3) Basics (13)
BGP (31) Brocade (1) Cables (1) CatOS (1) CCIE (3) CCIE Datacenter (22) CCNA (7)
CCNP (1) Checkpoint (3) Cisco (4) Cisco ASR (7) Cisco Icons (1) Cisco MDS Switch Cisco Routers (12)
(1)
Cisco Switches (7) Cisco Wireless (2) Cloud Computing (2) Data Center (17) DHCP (4) DWDM (1)
EIGRP (7) Etherchannel (3) F5 (2) Fiber Optics (1) Firewall (2) Fortinet (1) GLBP (5) GNS3 (2) Huawei (4)
interview Questions (1) IOS (1) IOS Upgradation (3) IoT (1) IP Addressing (2) IPV6 (2) Juniper (13) LABS (2)
Load Balancing (5) MPLS (21) MPLS Traffic Engg. (3) MTU (5) Multicast (3) Nexus (20) OSI
OSPF (22)
Model (1) OSPF (22) OTV (2) Palo-Alto (2) Password Recovery (1) Physical (1) PPP (2) Riverbed (3) RSTP
(2) SDN & NFV (2) SSL (1) Stack (1) subnetting (3) Switching (9) TACACS (1) TCP (2) TCP and UDP ports (2)
Technology (1) Terminal Server (1) Topologies (5) Traceroute (2) VLAN (4) VPN (3) VRRP (4) WAN
optimization (4)
FEEDJIT
Live Traffic Feed
A visitor from Islamabad
arrived 3 mins ago
A visitor from Stockton,
California viewed "Pointto
Point Protocol (PPP), the
Link Control Protocol (LCP)
and CHAP (Challenge
A visitor from Lansing,
Handshake Authentication
Michigan viewed "The
Protocol) ~" 7 mins ago
Concept of PHP (Penultimate
Hop Popping) MPLS ~" 7
A visitor from United States
mins ago
viewed "F5 Load Balancers:
LTM vs GTM ~" 12 mins ago
A visitor from La Paz viewed
"BGP: Path Selection Criteria
Path Vector Protocol ~" 12
A visitor from Ramsis, Al
mins ago
Buhayrah viewed ": BGP" 13
mins ago
A visitor from Pune,
Maharashtra viewed "F5 Load
Balancers: LTM vs GTM ~"
16 mins ago
A visitor from Karachi, Sindh
viewed "OSPF Area and LSAs
Propagation. ~" 26 mins ago
A visitor from Doha, Ad
Dawhah viewed "25 Things to
remember about EIGRP:
Short and Simple ~" 29 mins
A visitor from San Diego,
ago
California viewed "Pointto
Point Protocol (PPP), the
Link Control Protocol (LCP)
and CHAP (Challenge
Realtime view · Get Feedjit
ALEXA
Copyright@ 2006-2015 Networks-Baseline. Powered by Blogger.
Copyright © 2016 << Networks Baseline - Cisco Engineers Live >> | Powered by Blogger
Design by BluChic | Blogger Theme by Lasantha - PremiumBloggerTemplates.com | BTheme.net | Distributed
By Gooyaabi Templates

BGP Multisession - Networks Baseline - Cisco Engineers Live

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

BGP Multisession - Networks Baseline - Cisco Engineers Live

Încărcat de

Drepturi de autor:

Formate disponibile

10/24/2016 BGP Multisession ~ << Networks Baseline ­ Cisco Engineers Live >>

Share This:  Facebook  Twitter  Google+  Stumble  Digg

Figure 2 shows the topology used throughout this document.

Example of MTR with BGP

BGP Multisession without MTR

Possibility 1 : one BGP session

Possibility 2 : two BGP sessions

Possibility 3 : three BGP sessions

Multi Session vs Single Session

Benefits of Multisession BGP

Multisession BGP allows more granularity in managing BGP.

One could clear only one of these TCP sessions.

We see that one TCP session/BGP session re-established.

IOS without MTR feature

IOS with MTR feature, before CSCsz76118

IOS after CSCsz76118

By default, the transport mode is single-session, hence there is one session.

+1 Recommend this on Google

Redistributing Internal BGP Routes Into OSPF

Design Inter-Domain Multicast redundancy using MBGP and MSDP

Newer Post Home Older Post

Comment as: Unknown (Google) Sign out

Publish Preview Notify me

Links to this post

Links to this post

Subscribe to: Post Comments (Atom)

Secure Socket Layer ( SSL) Connection Setup

F5 Load Balancers: LTM vs GTM

Comparison of Routers Cisco, Juniper and Huawei

OSPF : "34 Things to remember"

Cisco ASR 1002-X Basics

Interview questions for Networking Engineer's( CCNA/CCNP and CCIE candidates )

CISCO-JUNIPER COMMANDS REF

LACP and PAgP

Copyright@ 2006-2015 Networks-Baseline. Powered by Blogger.

S-ar putea să vă placă și

10/24/2016 BGP Multisession ~ << Networks Baseline Cisco Engineers Live >>