Routing Instances

The Access Gateway Function (AGF) supports placing subscribers in different routing instances where each routing instance has its own routing table, routing policies, and interfaces. You can configure multiple routing instances to support the authentication and registration of subscribers to different Access and Mobility Management Functions (AMFs) and to support the routing of data packets to different user plane functions (UPFs).

To configure routing instances for the Point-to-Point Protocol over Ethernet (PPPoE) subscribers, set the target-routing-instance option at the [edit access domain map] hierarchy level or set the subscriber-context option under the [edit access] hierarchy. You will need to apply authentication attributes to subscribers. To apply attributes to the Point-to-Point Protocol (PPP) subscribers, use the aaa-options statement at the [edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit ppp-options] hierarchy level.

To configure routing instances for the Dynamic Host Configuration Protocol (DHCP) subscribers, set the target-routing-instance option at the [edit access domain map] hierarchy level. The AGF assigns the domain name to the subscriber using the DHCP group configuration.

You can also configure multiple routing instances to route the data packets to different UPFs. To configure the UPF routing instance and local tunnel endpoint for the GPRS tunneling protocol, user plane (GTP-U) tunnel to the UPF, set the routing-instance and ip-address options at the [edit services agf user-planes] hierarchy level.