Redsox 19

This score isn't a Football score, It's MLB score. the redsox almost lose the game, 10 points in the first inning but not enough support to win the game.

CSC part 2

I do something wrong on last post, the backbone carrier pop the label , because the label is pop too early, the ipv4 packet will not reach the correct PE router. so the traffic isn't work.

I check the configuration again, 2 key points on it,
1, In junos, The BGP inet-vpn update will base on inet.3 table, if the next-hop isn't on the table it will not update to peer.

2, The bgp peer configuration include the "resolve-vpn" this mean this prefix will using for next-hop resolve.

example @PE LSR
3:9:192.168.90.0/24 (1 entry, 0 announced)
*BGP Preference: 140/-101
Route Distinguisher: 3:9
Next-hop reference count: 6
Source: 123.123.2.2
Next hop: 123.123.12.2 via fe-0/1/0.12, selected
Label operation: Push 100032, Push 100112, Push 100016(top)
Protocol next hop: 2.2.9.9
Push 100032
Indirect next hop: 8738378 262147
State:
Local AS: 1 Peer AS: 1
Age: 35:47 Metric2: 1
Task: BGP_1.123.123.2.2+179
AS path: 3 I
Communities: target:3:9
VPN Label: 100032
Localpref: 100
Router ID: 123.123.2.2
Secondary Tables: ce1.inet.0
Indirect next hops: 1
Protocol next hop: 2.2.9.9 Metric: 1
Push 100032
Indirect next hop: 8738378 262147
Indirect path forwarding next hops: 1
Next hop: 123.123.12.2 via fe-0/1/0.12
2.2.9.9/32 Originating RIB: inet.3
Metric: 1 Node path count: 1
Indirect nexthops: 1
Protocol Nexthop: 123.123.3.3 Metric: 1 Push 100112
Indirect nexthop: 87381bc 262160
Indirect path forwarding nexthops: 1
Nexthop: 123.123.12.2 via fe-0/1/0.12
123.123.3.3/32 Originating RIB: inet.3
Metric: 1 Node path count: 1
Forwarding nexthops: 1
Nexthop: 123.123.12.2 via fe-0/1/0.12

SG F1 ticket

The SG F1 ticket is here.

CSC

If you are running CSC in MPLS, there are 3 labels in the carrier PE router, which in th follow show result in junos. Before we see the labe swap, This Scenario is Customer Carrier Running MPLS VPN. The backbone Carrier will not see the CE1 & Ce9 routes. this wil reduce Carrier's routing table.

The simple topology is

CE1---R1--R2--R3--R4--R5--R6--R7--R8--R9--CE9

R1,R2,R3 are AS 1
R4,R5,R6 are carrier
R7,R8,R9 are AS 3



R1
bgp.l3vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

3:9:192.168.110.1/32
*[BGP/170] 05:27:51, localpref 100, from 123.123.2.2
AS path: 3 10 I
> to 123.123.12.2 via fe-0/1/0.12, Push 100016, Push 100112(top)


R2
100112 *[LDP/9] 05:24:01, metric 1
> to 123.123.23.3 via fe-0/1/0.23, Swap 100160


R3
100160 *[LDP/9] 05:24:30, metric 1
> to 123.123.34.4 via fe-0/1/0.34, Swap 100144

R4
100144 *[VPN/170] 05:24:49, metric2 1, from 1.1.5.5
> to 1.1.45.5 via fe-0/1/0.45, Swap 100112, Push 100048(top)

R5
100048 *[LDP/9] 05:25:03, metric 1
> to 1.1.56.6 via fe-0/1/0.56, Pop
100048(S=0) *[LDP/9] 05:25:03, metric 1
> to 1.1.56.6 via fe-0/1/0.56, Pop


R6
100112 *[VPN/170] 05:25:46
> to 1.1.67.7 via fe-0/1/0.67, Swap 100208


R7
100208 *[VPN/170] 05:26:05
> to 2.2.78.8 via fe-0/1/0.78, Swap 100112

R8
100112 *[LDP/9] 05:26:20, metric 1
> to 2.2.89.9 via fe-0/1/0.89, Pop
100112(S=0) *[LDP/9] 05:26:20, metric 1
> to 2.2.89.9 via fe-0/1/0.89, Pop


R9
100016 *[VPN/170] 05:31:28
> to 192.168.90.11 via fe-0/1/0.888, Pop