Hi again Aman,

Thank you for your reporting.

Hmmm... I read some GoBGP's source codes and (as far as I read) GoBGP does not
have feature for auto MPLS labels assignment.
GoBGP assigns always zero label when paths are imported from VRF to global RIB.
https://github.com/osrg/gobgp/blob/b391322bcbf56d623ca0a6b667c026b92f1e9e4d/table/path.go#L1149
In other words, it seems that GoBGP assumes that MPLS labels should be specified
through APIs.

FYI, the auto assignment feature seems to be posted, but not merged.
(sorry, I don't know why...)
https://github.com/osrg/gobgp/pull/366

A part from the auto assignment feature, the problem is there is no way to
assign MPLS labels for the received routes, right?
If we can assign MPLS labels when VRF creation, does it solve this problem?
For example,
  # Specify MPLS label(s) which assigned to paths on this VRF
  $ gobgp vrf add blue rd 65000:100 rt both 65000:100 label 100

Thanks,
Iwase

On 2018年01月26日 01:29, SHAIKH, AMAN  (AMAN) wrote:
Hi

I have noticed that GoBGP is assigning MPLS label of zero to all VPNv4 routes that are imported from VRF RIBs into the default RIB.

In my testbed, I have a PE (vsp-west-pe) connected to two CEs in two different VRFs named ‘blue’ and ‘red’. Each CE sends a route to the PE for prefix 192.168.0.0/24.

Here’s the RIB for blue VRF on vsp-west-pe:

[ashaikh@vsp-vpe-west ~]$ gobgp vrf blue rib

    Network              Next Hop             AS_PATH              Age        
Attrs

   192.168.0.0/24       10.200.0.2           65001                00:51:30 [{Origin: i} {Med: 0}]

Similarly, here’s the RIB for red VRF:

[ashaikh@vsp-vpe-west ~]$ gobgp vrf red rib

    Network              Next Hop             AS_PATH              Age        
Attrs

   192.168.0.0/24       10.201.0.3           65003                00:52:22 [{Origin: i} {Med: 0}]

Finally, here’s the list of VPNv4 routes in the default RIB:

[ashaikh@vsp-vpe-west ~]$ gobgp global rib -a vpnv4

   Network              Labels     Next Hop             AS_PATH Age        Attrs

*> 100:1:192.168.0.0/24 [0]        10.200.0.2           65001 00:53:05   [{Origin: i} {Med: 0} {Extcomms: [100:1]}]

*> 100:2:192.168.0.0/24 [0]        10.201.0.3           65003 00:53:05   [{Origin: i} {Med: 0} {Extcomms: [100:2]}]

As you can see the label stack for each route has a single label whose value is zero.

thx

aman



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot



_______________________________________________
gobgp-devel mailing list
gobgp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gobgp-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
gobgp-devel mailing list
gobgp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gobgp-devel

Reply via email to