We have loopback lo0.20 configured in routing instance as132847 with both ipv4 and ipv6 address. ipv4 address is advertised to iBGP peers, ipv6 is not. It was never weorking on this chassis. -- eBGP advertisement that is correctly sent to iBGP neighbors.

VRF lo0.20 inet6 interface address (prefix) is not advertised to iBGP neighbors as inet6 VPN routes.

To advertise VRF direct/static/redistributed to iBGP neighbors as inet/inet6 VPN routes:

1) we need to specify them in related BGP export policy;

2) we need attach the right target communities to the prefix.

routing-instances {

  as132847 {

    instance-type vrf;

       […]

    interface lo0.20;

    route-distinguisher 132847L:65535;

    vrf-export inf_rm4-vrf-export-as132847;    <<<<<<<<<< export policy

    vrf-target import target:132847L:65535;

    vrf-table-label;

  }

}

policy-options {

  policy-statement inf_rm4-vrf-export-as132847 {

    term 10 {

      from {

        route-filter 0.0.0.0/0 exact;

      }

      then {

        community add target:132847L:65535;

        community add target:132847L:65534;

        accept;

      }

    }

    term 20 {

      from policy inf_rm4-nsg-originated-subnets;

      then {

        community add target:132847L:65535;

        community add target:132847L:65534;

        accept;

      }

    }

    term 30 {

      from policy inf_rm4-public-p2p-subnets;

      then {

        community add target:132847L:65535;

        community add target:132847L:65534;

        accept;

      }

    }

    term 40 {

      from policy inf_rm4-nested-vrf-export-as132847;

      then {

        community add target:132847L:65535;

        community add target:132847L:65534;

        accept;

      }

    }

    then default-action reject;                           <<<<<<<< default reject and NOT attach the target communities

  }

}

1.0 - Draft.

N/A.