Description

This article explains how to establish EBGP peering using routing-service functionality with Subscriber Management client connections.

In this scenario, the client connection is good and the client IP is reachable from the MX router.

The following configuration example shows the client is assigned IP address 172.32.1.10 and the local-address is associated with lo0.1.

set dynamic-profiles PPPOE interfaces pp0 unit "$junos-interface-unit" routing-service enable
set dynamic-profiles vlan-demux interfaces demux0 unit "$junos-interface-unit" routing-service enable
 
set routing-instances vrf01 instance-type vrf
set routing-instances vrf01 interface xe-1/0/0.1004
set routing-instances vrf01 interface lo0.1
set routing-instances vrf01 route-distinguisher 2001:1001
set routing-instances vrf01 vrf-import vrf01_IMPORT
set routing-instances vrf01 vrf-export vrf01_EXPORT
set routing-instances vrf01 vrf-table-label
set routing-instances vrf01 routing-options router-id 172.32.1.9
set routing-instances vrf01 routing-options auto-export
set routing-instances vrf01 protocols bgp group SITE1 type external
set routing-instances vrf01 protocols bgp group SITE1 family inet unicast
set routing-instances vrf01 protocols bgp group SITE1 neighbor 172.32.1.10 local-address 172.32.1.9
set routing-instances vrf01 protocols bgp group SITE1 neighbor 172.32.1.10 passive
set routing-instances vrf01 protocols bgp group SITE1 neighbor 172.32.1.10 peer-as 65001

Solution

The Subscriber Management routing-service function requires EBGP parameter multihop ttl 2.

set routing-instances vrf01 protocols bgp group SITE1 multihop ttl 2

The routing-service function does not support multihop BGP, but the PFE will be counted as a hop for Subscriber Management clients with JUNOS.