RFC 4761 on Virtual Private LAN Service (VPLS) Using BGP for Auto Discouvery

Virtual Private LAN Service (VPLS), also known as Transparent LAN Service and Virtual Private Switched Network service, is a useful Service Provider offering. The service offers a Layer 2 Virtual Private Network (VPN); however, in the case of VPLS, the customers in the VPN are connected by a multipoint Ethernet LAN, in contrast to the usual Layer 2 VPNs, which are point-to-point in nature.

This document describes the functions required to offer VPLS, a mechanism for signaling a VPLS, and rules for forwarding VPLS frames across a packet switched network.

See complete of RFC VPLS Using BGP

Multi AS backbone: Option B // EBGP redistribution of labeled VPN-IPv4 routes

Option B: EBGP redistribution of labeled VPN-IPv4 routes.

I will put my lab again as i promised in the previous post. I have done with option B.

VPN IPv4 routes are exchanged in the ASBR.

References for labeled unicast can be found in http://www.juniper.net/techpubs/software/junos/junos74/swconfig74-vpns/html/cofc-config.html#1013124

you can find the topology below:

RSVP tunnel configured in the PE1 to PE3, vice versa. Also for connection between PE2 and PE4.
EBGP running between PE2 and PE4.

Objectives:

CE1 can be reached by CE4, CE2 by CE4… vice versa.

All Status

LSP Status

enugadi@enugadi# run show mpls lsp logical-router all

——————— output truncate————————

logical-router: pe1
Ingress LSP: 1 sessions
To              From            State Rt ActivePath       P     LSPname
3.3.3.3         1.1.1.1         Up     0                  *     1-to-3
Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions
To              From            State   Rt Style Labelin Labelout LSPname
1.1.1.1         3.3.3.3         Up       0  1 FF       3        – 3-to-1
Total 1 displayed, Up 1, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
——-

logical-router: pe4

Ingress LSP: 1 sessions
To              From            State Rt ActivePath       P     LSPname
2.2.2.2         4.4.4.4         Up     0                  *     4-to-2
Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions
To              From            State   Rt Style Labelin Labelout LSPname
4.4.4.4         2.2.2.2         Up       0  1 FF       3        – 2-to-4
Total 1 displayed, Up 1, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
——-

logical-router: pe2

Ingress LSP: 1 sessions
To              From            State Rt ActivePath       P     LSPname
4.4.4.4         2.2.2.2         Up     0                  *     2-to-4
Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions
To              From            State   Rt Style Labelin Labelout LSPname
2.2.2.2         4.4.4.4         Up       0  1 FF       3        – 4-to-2
Total 1 displayed, Up 1, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
——-

logical-router: pe3

Ingress LSP: 1 sessions
To              From            State Rt ActivePath       P     LSPname
1.1.1.1         3.3.3.3         Up     0                  *     3-to-1
Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions
To              From            State   Rt Style Labelin Labelout LSPname
3.3.3.3         1.1.1.1         Up       0  1 FF       3        – 1-to-3
Total 1 displayed, Up 1, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
——-

BGP Status

enugadi@enugadi# run show bgp summary logical-router all

———output truncate————

logical-router: pe1
Groups: 1 Peers: 1 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
bgp.l3vpn.0           16         16          0          0          0          0
inet.0                 0          0          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
3.3.3.3           100        140         80       0       2       31:34 Establ
bgp.l3vpn.0: 16/16/0
blue.inet.0: 14/14/0
grey.inet.0: 2/2/0
——-

logical-router: pe4
Groups: 2 Peers: 2 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
bgp.l3vpn.0           20         20          0          0          0          0
inet.0                 0          0          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
2.2.2.2           200        100        153       0       0       39:26 Establ
bgp.l3vpn.0: 16/16/0
11.0.0.9          100         72         77       0       0       29:13 Establ
bgp.l3vpn.0: 4/4/0
——-

logical-router: pe2
Groups: 1 Peers: 1 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
bgp.l3vpn.0            4          4          0          0          0          0
inet.0                 0          0          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
4.4.4.4           200        152        102       0       0       39:26 Establ
bgp.l3vpn.0: 4/4/0
blue.inet.0: 2/2/0
grey.inet.0: 2/2/0
——-

logical-router: pe3
Groups: 2 Peers: 2 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
bgp.l3vpn.0           20         20          0          0          0          0
inet.0                 0          0          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
1.1.1.1           100        108        187       0       2       31:34 Establ
bgp.l3vpn.0: 4/4/0
11.0.0.10         200         76         74       0       1       29:13 Establ
bgp.l3vpn.0: 16/16/0
——-

Routing tables

enugadi@enugadi# run show route logical-router ce3

inet.0: 19 destinations, 19 routes (19 active, 0 holddown, 0 hidden)
+ = Active Route, – = Last Active, * = Both

10.0.0.0/30        *[OSPF/150] 00:22:12, metric 0, tag 3489661128
> to 10.0.0.6 via fxp2.3
10.0.0.4/30        *[Direct/0] 05:38:29
> via fxp2.3
10.0.0.5/32        *[Local/0] 05:38:30
Local via fxp2.3
10.10.10.10/32     *[OSPF/10] 00:22:12, metric 1
> to 10.0.0.6 via fxp2.3
30.30.30.30/32     *[Direct/0] 05:38:30
> via lo0.30
192.168.1.0/24     *[Direct/0] 05:21:21
> via fxp2.9
192.168.1.1/32     *[Local/0] 05:21:21
Local via fxp2.9
192.168.100.0/24   *[Static/5] 03:45:24
Reject
192.168.101.0/24   *[Static/5] 03:45:24
Reject
192.168.102.0/24   *[Static/5] 03:45:24
Reject
192.168.103.0/24   *[Static/5] 03:45:24
Reject
192.168.104.0/24   *[Static/5] 03:45:24
Reject
192.168.105.0/24   *[Static/5] 03:45:24
Reject
192.168.106.0/24   *[Static/5] 03:45:24
Reject
192.168.107.0/24   *[Static/5] 03:45:24
Reject
192.168.108.0/24   *[Static/5] 03:45:24
Reject
192.168.109.0/24   *[Static/5] 03:45:24
Reject
192.168.110.0/24   *[Static/5] 03:45:24
Reject
224.0.0.5/32       *[OSPF/10] 05:38:31, metric 1
MultiRecv

[edit logical-routers pe2]
enugadi@enugadi# run show route logical-router ce2

inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, – = Last Active, * = Both

10.0.0.8/30        *[Direct/0] 05:38:34
> via fxp1.2
10.0.0.9/32        *[Local/0] 05:38:35
Local via fxp1.2
10.0.0.12/30       *[OSPF/150] 00:22:17, metric 0, tag 3489661028
> to 10.0.0.10 via fxp1.2
20.20.20.20/32     *[Direct/0] 05:38:35
> via lo0.20
40.40.40.40/32     *[OSPF/10] 00:22:17, metric 1
> to 10.0.0.10 via fxp1.2
224.0.0.5/32       *[OSPF/10] 05:38:35, metric 1
MultiRecv

[edit logical-routers pe2]
enugadi@enugadi# run show route logical-router ce4

inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, – = Last Active, * = Both

10.0.0.8/30        *[OSPF/150] 00:22:20, metric 0, tag 3489661128
> to 10.0.0.14 via fxp2.4
10.0.0.12/30       *[Direct/0] 05:38:37
> via fxp2.4
10.0.0.13/32       *[Local/0] 05:38:38
Local via fxp2.4
20.20.20.20/32     *[OSPF/10] 00:22:20, metric 1
> to 10.0.0.14 via fxp2.4
40.40.40.40/32     *[Direct/0] 05:38:38
> via lo0.40
224.0.0.5/32       *[OSPF/10] 05:38:38, metric 1
MultiRecv

Result:

enugadi@enugadi# …ping 30.30.30.30 logical-router ce1 rapid count 100
PING 30.30.30.30 (30.30.30.30): 56 data bytes
!
—- 30.30.30.30 ping statistics—-
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.437/0.457/0.922/0.048 ms

[edit logical-routers pe2]
enugadi@enugadi# run traceroute 30.30.30.30 logical-router ce1
traceroute to 30.30.30.30 (30.30.30.30), 30 hops max, 40 byte packets
1  10.0.0.2 (10.0.0.2)  0.151 ms  0.108 ms  0.107 ms
2  11.0.0.2 (11.0.0.2)  0.438 ms  0.417 ms  0.418 ms
MPLS Label=100512 CoS=0 TTL=1 S=1
3  11.0.0.10 (11.0.0.10)  0.413 ms  0.407 ms  0.411 ms
MPLS Label=100480 CoS=0 TTL=1 S=1
4  30.30.30.30 (30.30.30.30)  0.432 ms  0.425 ms  0.434 ms

[edit logical-routers pe2]
enugadi@enugadi# run ping 40.40.40.40 logical-router ce2 rapid count 100
PING 40.40.40.40 (40.40.40.40): 56 data bytes
!
—- 40.40.40.40 ping statistics—-
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.437/0.451/0.514/0.010 ms

[edit logical-routers pe2]
enugadi@enugadi# run traceroute 40.40.40.40 logical-router ce2
traceroute to 40.40.40.40 (40.40.40.40), 30 hops max, 40 byte packets
1  10.0.0.10 (10.0.0.10)  0.149 ms  0.111 ms  0.107 ms
2  11.0.0.2 (11.0.0.2)  0.432 ms  0.417 ms  0.418 ms
MPLS Label=100528 CoS=0 TTL=1 S=1
3  11.0.0.10 (11.0.0.10)  0.413 ms  0.406 ms  0.413 ms
MPLS Label=100496 CoS=0 TTL=1 S=1
4  40.40.40.40 (40.40.40.40)  0.459 ms  0.425 ms  0.425 ms

Cheersss…………..

Multi AS backbone: Option A VRF to VRF connection

I will explain what i have done with VRF to VRF connections between 2 providers.

The characteristics of this option is you have to configuring per-VPN on each ASBR or the PE which connected to different AS.

In diagram you will seeing there are two providers which have AS100 and AS200.

Each provider have 2 customer connected, customer Grey and Blue.

The Customers Grey and Blue are connected to the PE1 and PE2. The PE3 of AS100 has directly connected to the PE4 of AS200.

Here you go…

Objective:

CE1 can be reached by CE3 one another, also CE2 to CE4.

Status of each routers

BGP Status

enugadi@enugadi# run show bgp summary logical-router all

——output truncate———-

logical-router: pe1
Groups: 1 Peers: 1 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
bgp.l3vpn.0           18         18          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
3.3.3.3           100        272        262       0       0     2:00:09 Establ
bgp.l3vpn.0: 18/18/0
blue.inet.0: 15/15/0
grey.inet.0: 3/3/0
——-

logical-router: pe4
Groups: 1 Peers: 1 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
bgp.l3vpn.0           16         16          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
2.2.2.2           200        693        660       0       0     3:39:27 Establ
bgp.l3vpn.0: 16/16/0
blue.inet.0: 14/14/0
grey.inet.0: 2/2/0
——-

logical-router: pe2
Groups: 1 Peers: 1 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
bgp.l3vpn.0            6          6          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
4.4.4.4           200        658        694       0       0     3:39:27 Establ
bgp.l3vpn.0: 6/6/0
blue.inet.0: 3/3/0
grey.inet.0: 3/3/0
——-

logical-router: pe3
Groups: 1 Peers: 1 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
bgp.l3vpn.0            4          4          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
1.1.1.1           100        260        273       0       0     2:00:09 Establ
bgp.l3vpn.0: 4/4/0
blue.inet.0: 2/2/0
grey.inet.0: 2/2/0
——-

Connection status

enugadi@enugadi# run ping 30.30.30.30 logical-router ce1
PING 30.30.30.30 (30.30.30.30): 56 data bytes
64 bytes from 30.30.30.30: icmp_seq=0 ttl=253 time=0.497 ms
64 bytes from 30.30.30.30: icmp_seq=1 ttl=253 time=0.467 ms
64 bytes from 30.30.30.30: icmp_seq=2 ttl=253 time=0.435 ms
64 bytes from 30.30.30.30: icmp_seq=3 ttl=253 time=0.436 ms
^{C
—- 30.30.30.30 ping statistics—-
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.435/0.459/0.497/0.026 ms}

^{[edit]
enugadi@enugadi# run traceroute 30.30.30.30 logical-router ce1
traceroute to 30.30.30.30 (30.30.30.30), 30 hops max, 40 byte packets
1  10.0.0.2 (10.0.0.2)  0.150 ms  0.109 ms  0.109 ms
2  11.0.0.14 (11.0.0.14)  0.279 ms  0.266 ms  0.272 ms
3  30.30.30.30 (30.30.30.30)  0.439 ms  0.427 ms  0.426 ms}

^{[edit]
enugadi@enugadi# run ping 40.40.40.40 logical-router ce2
PING 40.40.40.40 (40.40.40.40): 56 data bytes
64 bytes from 40.40.40.40: icmp_seq=0 ttl=253 time=0.513 ms
64 bytes from 40.40.40.40: icmp_seq=1 ttl=253 time=0.461 ms
64 bytes from 40.40.40.40: icmp_seq=2 ttl=253 time=0.435 ms
64 bytes from 40.40.40.40: icmp_seq=3 ttl=253 time=0.434 ms}
C
—- 40.40.40.40 ping statistics—-
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.434/0.461/0.513/0.032 ms

[edit]
enugadi@enugadi# run traceroute 40.40.40.40 logical-router ce2
traceroute to 40.40.40.40 (40.40.40.40), 30 hops max, 40 byte packets
1  10.0.0.10 (10.0.0.10)  0.155 ms  0.109 ms  0.110 ms
2  11.0.0.10 (11.0.0.10)  0.285 ms  0.264 ms  0.271 ms
3  40.40.40.40 (40.40.40.40)  0.437 ms  0.427 ms  0.428 ms

OSPF Database

[edit]
enugadi@enugadi# run show ospf database logical-router pe3 instance blue

OSPF link state database, area 1.1.1.1
Type       ID               Adv Rtr           Seq      Age  Opt  Cksum  Len
Router  *11.0.0.13        11.0.0.13        0×80000035   720  0×2  0xb406  36
Router   11.0.0.14        11.0.0.14        0×80000032   721  0×2  0xb802  36
Network  11.0.0.14        11.0.0.14        0×80000005  2052  0×2  0×9d58  32
OSPF AS SCOPE link state database
Type       ID               Adv Rtr           Seq      Age  Opt  Cksum  Len
Extern  *10.0.0.0         11.0.0.13        0×8000000a   174  0×2  0×8a20  36
Extern   10.0.0.4         11.0.0.14        0×8000000e  1632  0×2  0×544d  36
Extern  *10.10.10.10      11.0.0.13        0×80000009   474  0×2  0xd930  36
Extern   30.30.30.30      11.0.0.14        0×80000005  1932  0×2  0×407c  36
Extern   192.168.1.0      11.0.0.14        0×80000005  1752  0×2  0xf6d2  36
Extern   192.168.100.0    11.0.0.14        0×80000004  1332  0×2  0×23c5  36
Extern   192.168.101.0    11.0.0.14        0×80000004  1152  0×2  0×18cf  36
Extern   192.168.102.0    11.0.0.14        0×80000004  1032  0×2  0xdd9   36
Extern   192.168.103.0    11.0.0.14        0×80000004   852  0×2  0×2e3   36
Extern   192.168.104.0    11.0.0.14        0×80000004   732  0×2  0xf6ed  36
Extern   192.168.105.0    11.0.0.14        0×80000004   552  0×2  0xebf7  36
Extern   192.168.106.0    11.0.0.14        0×80000004   432  0×2  0xe002  36
Extern   192.168.107.0    11.0.0.14        0×80000004   252  0×2  0xd50c  36
Extern   192.168.108.0    11.0.0.14        0×80000004   132  0×2  0xca16  36
Extern   192.168.109.0    11.0.0.14        0×80000003  2352  0×2  0xc11f  36
Extern   192.168.110.0    11.0.0.14        0×80000003  2232  0×2  0xb629  36

The character marked with yellow, are convert from LSA type 3 to LSA type 5. Domain ID are used to convert this.

If you wanna know more information about Domain ID and domain-vpn-tag, please refer to:

http://www.juniper.net/techpubs/software/junos/junos73/swconfig73-routing/html/instance-config24.html

Cheersss….

Yahoo Mesenger Version 7.x

After installing new OS, i tried to install Yahoo Mesenger from Yahoo.com. But, why version available are only 8.x. Honestly, I hate YM version 8, YM8 only would made my PC getting slow and slowwww. I like to used YM version 7 than 8. I found some link which i can download YM7, here it is http://filehippo.com/download_yahoo_messenger/

I’m sure one of you hate YM 8.

Multi AS backbone: Option C // EBGP Multihop

In this experiment, i wanna running EBGP Multihop between PE edge router. VPN IPV4 routes are exchanged directly between each PE. The ASBR maintain EBGP session with labeled unicast. IPV4 routes are exchanged in this ASBR, so PE1 will reach loopback address of the PE2. EBGP Multihop between the PE1 and PE2 require IPv4 connection between them.

BGP Status:

Note: No VPN routes exchanged in th  PE3 and PE4.

enugadi@enugadi# run show bgp summary logical-router all

—————————-output truncate——————————

logical-router: pe1
Groups: 2 Peers: 2 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
inet.0                 1          0          0          0          0          0
bgp.l3vpn.0           16         16          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
2.2.2.2           200         32         32       0       0       12:34 Establ
bgp.l3vpn.0: 16/16/0
blue.inet.0: 14/14/0
grey.inet.0: 2/2/0
3.3.3.3           100         18         19       0       0        8:22 Establ
inet.0: 0/1/0
——-

logical-router: pe2
Groups: 2 Peers: 2 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
inet.0                 1          0          0          0          0          0
bgp.l3vpn.0            4          4          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
1.1.1.1           100         31         34       0       0       12:34 Establ
bgp.l3vpn.0: 4/4/0
blue.inet.0: 2/2/0
grey.inet.0: 2/2/0
4.4.4.4           200         28         28       0       0       12:38 Establ
inet.0: 0/1/0
——-

logical-router: pe3
Groups: 2 Peers: 2 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
inet.0                 1          1          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
1.1.1.1           100         18         20       0       0        8:22 Establ
inet.0: 0/0/0
11.0.0.10         200         28         30       0       0       13:17 Establ
inet.0: 1/1/0
——-

logical-router: pe4
Groups: 2 Peers: 2 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
inet.0                 1          1          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
2.2.2.2           200         26         29       0       0       12:38 Establ
inet.0: 0/0/0
11.0.0.9          100         29         30       0       0       13:17 Establ
inet.0: 1/1/0
——-

Testing connectivity:

enugadi@enugadi# run ping 30.30.30.30 logical-router ce1 rapid count 100
PING 30.30.30.30 (30.30.30.30): 56 data bytes
!
—- 30.30.30.30 ping statistics—-
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.438/0.450/0.513/0.010 ms

[edit]
enugadi@enugadi# run traceroute 30.30.30.30 logical-router ce1
traceroute to 30.30.30.30 (30.30.30.30), 30 hops max, 40 byte packets
1  10.0.0.2 (10.0.0.2)  0.149 ms  0.134 ms  0.107 ms
2  11.0.0.2 (11.0.0.2)  0.440 ms  0.418 ms  0.421 ms
MPLS Label=100032 CoS=0 TTL=1 S=0
MPLS Label=1024 CoS=0 TTL=1 S=1
3  11.0.0.10 (11.0.0.10)  0.414 ms  0.408 ms  0.412 ms
MPLS Label=100000 CoS=0 TTL=1 S=0
MPLS Label=1024 CoS=0 TTL=2 S=1
4  30.30.30.30 (30.30.30.30)  0.431 ms  0.425 ms  0.435 ms

[edit]
enugadi@enugadi# run ping 40.40.40.40 logical-router ce2 rapid count 100
PING 40.40.40.40 (40.40.40.40): 56 data bytes
!
—- 40.40.40.40 ping statistics—-
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.438/0.450/0.510/0.011 ms

[edit]
enugadi@enugadi# run traceroute 40.40.40.40 logical-router ce2
traceroute to 40.40.40.40 (40.40.40.40), 30 hops max, 40 byte packets
1  10.0.0.10 (10.0.0.10)  0.145 ms  0.109 ms  0.107 ms
2  11.0.0.2 (11.0.0.2)  0.436 ms  0.411 ms  0.419 ms
MPLS Label=100032 CoS=0 TTL=1 S=0
MPLS Label=1025 CoS=0 TTL=1 S=1
3  11.0.0.10 (11.0.0.10)  0.418 ms  0.408 ms  0.412 ms
MPLS Label=100000 CoS=0 TTL=1 S=0
MPLS Label=1025 CoS=0 TTL=2 S=1
4  40.40.40.40 (40.40.40.40)  0.442 ms  0.425 ms  0.424 ms

Multi AS backbone

According to Ina Minei Book, The MPLS Enabled Application, there are 3 option for deploying Multi AS VPN.

Option A: VRF to VRF connections at the ASBR.

This is the simplest method to exchange the VPN routes across AS boundary.
ASBR maintain all vpn connected towards the other AS. ASBR or Edge PE would be directly connected to the other ASBR via logical connection per VRF. Therefore, each VRF will need minumum 1 logical connection to exchange the VPN routes. In fact, this option is only manipulating IPv4 routes. This option is simple but not scalable, because one logical connection should be connected for every VRF. If provider need to add one new VRF, they require to manages logical connection in the ASBR.

Option B: EBGP redistribution of labeled IPv4 routes.

This option would eliminated behaviour in the option A. The ASBR doesn’t have VRF configuration. The option B uses a single EBGP session between ASBR to carry VPN-IPv4 routes. SO the ASBR will maintain state of all VPN routes.

Option C: multihop EBGP redistribution of labeled VPN-IPv4 routes between the source and destination AS, with EBGP redistribution of labeled IPv4 routes from one AS to the neighboring AS.

In this option, the customer uses the Multihop EBGP session between each PE router to carry external prefixes. This option eliminated option B that ASBR should be maintain state of all vpn routes.

In the next post, i will try to present my lab of all option above in detail.

If you have to know the basic of Multi AS in detail, you should have Ina Minei book, and read from this book. Its very good book.