Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    OnePopVrfIp Scenario

    The OnePopVrfIp configuration scenario for NIC resolves an assigned IP address for a subscriber to IP pools or network whose traffic enters the network through an interface on a device running Junos OS to a reference for the SAE that manages the interface. The realm for this configuration utilizes routing information collected by the network publisher from particular devices running Junos OS. The resolution process takes a subscriber’s IP address as a key and returns a reference to the SAE that manages the interface.

    This configuration scenario is very similar to the OnePopStatic RouteIp scenario. During resolution, the OnePopVrfIp scenario filters interfaces the VPN identifier of the VPN that carries subscriber traffic.

    Figure 1shows the resolution graph for this realm.

    Figure 1: Resolution Process for the VrfIp Realm

Process for the VrfIp Realm

    The following agents collect information for resolvers in this realm:

    • Directory agent PoolInterface collects and publishes information about the mappings of IP address pools to interfaces.
    • Directory agent VrSaeId collects and publishes information about the mappings of VRs to SAEs.

    The agents obtain information from the interfaceConfiguration attribute of the EdgeRouter entry in the directory and read an XML document that conforms to the networkConfig.xsd schema. If this scenario is used with a different router type, you can edit the XML document.

    For information about the XML document, see Files Used to Test Network Publisher.

    The OnePopVrfIp scenario provides two host configurations: a centralized configuration and a distributed configuration.

    Centralized Configuration

    In this configuration, the single host DemoHost supports all agents and resolvers. When the NIC proxy sends a subscriber’s IP address to host DemoHost, the following sequence of events occurs:

    1. The host passes the subscriber’s IP address and VPN ID to resolver A1.
    2. Resolver A1 obtains all IP pools that match the IP address.
    3. Resolver AI forwards the IP pool names and VPN ID to Resolver B1.
    4. Resolver B1 obtains the all interface IDs for the IP pools and filters all interfaces that match the VPN ID.
    5. Resolver A1 forwards the interface IDs to Resolver C1.
    6. Resolver C1 resolves the interface IDs to the VR name and returns the VR name to resolver A1.
    7. Resolver A1 forwards the VR names to resolver D1.
    8. Resolver D1 obtains references for the SAEs managing the VRs and returns the SAE reference to resolver A1.
    9. Resolver A1 passes the SAE references to its host.
    10. The host returns the SAE references to the NIC proxy.

    Figure 2 shows the interactions of the NIC components for this realm.

    Figure 2: OnePopVrfIp Centralized Configuration

    OnePopVrfIp Centralized

    Distributed Configuration

    In this configuration, the agents and resolvers are distributed among two hosts. When a NIC proxy sends a subscriber IP address to host OnePopBO, the resolvers execute the same actions as they do in the centralized configuration. Figure 3 illustrates the interactions of the NIC components for this realm.

    Figure 3: OnePopStaticRouteIp Distributed Configuration

    OnePopStaticRouteIp Distributed

    Published: 2014-12-10