Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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

    OnePopStaticRouteIp Scenario

    The OnePopStaticRouteIp configuration scenario for NIC resolves an assigned IP address for a subscriber 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 accommodates the situation in which the network publisher component gathers interface information for the 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.

    Figure 1 shows the resolution graph for this realm.

    Figure 1: Resolution Process for the StaticRouteIp Realm

    Resolution Process for the StaticRouteIp
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 External Application Requirements for NIC.

    The OnePopStaticRouteIp 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 to resolver A1.
    2. Resolver A1 obtains an IP pool for the IP address.
    3. Resolver AI forwards the IP pool name to Resolver B1.
    4. Resolver B1 obtains the interface ID for the IP pool and returns this value to resolver A1.
    5. Resolver A1 forwards the interface ID to Resolver C1.
    6. Resolver C1 resolves the interface ID to the VR name and returns the VR name to resolver A1.
    7. Resolver A1 forwards the VR name to resolver D1.
    8. Resolver D1 obtains a reference for the SAE managing the VR and returns the SAE reference to resolver A1.
    9. Resolver A1 passes the SAE reference to its host.
    10. The host returns the SAE reference to the NIC proxy.

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

    Figure 2: OnePopStaticRouteIp Centralized Configuration

    OnePopStaticRouteIp Centralized Configuration

    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 Configuration

    Modified: 2012-11-23