Major Description
I enable discovery module "cisco-vrf" for my JunOS routers and it's work! GREAT!
But the same VRF (for example, CLIENT1) is stored like diferent VRF for each router.
On all routers we have this VRF with the same RouteTarget (RT) but with different RouteDistinguasher (RD).
So on page .../routing/protocol=vrf/ system does not aggregate the same VRF as one entity, I see new VRF for each router with the same name.
I think we need to fix it.
RT is avaliable via SNMP in MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRTTable
for example:
snmpbulkwalk -v2c -c *** -M mibs/rfc:mibs/net-snmp junos-router MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRT
|
MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRT."CLIENT1".1.both = STRING: "65551:1001" |
Attachments
Activity
On the same MPLS network there may be
VRF1 with route-target 65000:1 and uniq RD on each router
and
VRF2 with route-target 65000:2 and same RD on each router
A route-target extended community, or route target, is a type of BGP extended community that you use to define VPN membership.
...
PE 1 advertises the customer site addresses by prepending information to the addresses as advertised by CE 1, thus creating labeled VPN-IPv4 prefixes. The prepended information consists of a route distinguisher and an MPLS label.Because the CE router uses IPv4 addresses from the VPN’s private address space, these addresses can be duplicated in other VPNs to which PE 1 is attached. PE 1 associates a route distinguisher with each IPv4 address to create a globally unique address. In this example, the RD consists of the AS that PE 1 belongs to and a number that PE 1 assigns. The RD is prepended immediately before the IPv4 address.
PE routers assign MPLS labels to each VRF. In this example, the label for the VRF associated with customer site 1 is 16. The MPLS label is prepended immediately before the route distinguisher.
Example: Distribution of Routes and Labels with BGP
RD is not an identifier for VRFs!
RT (tables) not avialable for mostly devices.. currently I found only Huawei devices support it :/