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

    Configuring a NIC Scenario (C-Web Interface)

    The following topics provide the procedures for configuring a NIC scenario with the C-Web Interface:

    Defining the NIC Configuration (C-Web Interface)

    To use the NIC to locate subscriber configuration, you must configure one of the NIC configuration scenarios provided with the SRC software. Which agents you configure depends on the NIC configuration scenario that you use.

    The OnePop configuration scenario is the default configuration for the NIC. If you want to use another configuration scenario, you first clear data for the configuration scenario. Anytime you change the configuration scenario, you first clear data for the configuration scenario in use. See Changing NIC Configurations (C-Web Interface).

    When you select a NIC configuration scenario, the software adds the default configuration for most properties. You can modify the NIC properties, including those for agents.

    Note: We recommend that you change only those statements visible at the basic editing level. Contact Juniper Professional Services or Juniper Customer Support before you change any of the NIC statements not visible at the basic editing level.

    Note: By default, the CORBA naming server on a C Series Controller uses port 2809. The NIC host is configured to communicate with this naming server.

    To configure a NIC configuration scenario:

    1. Click Configure, expand Shared >NIC, and click the configuration scenario that you want to configure; for example, Scenario: OnePop.
    2. In the left pane, expand Agents.
    3. For each directory agent that the NIC configuration scenario includes, review and if needed update NIC agent configuration to define properties specific to your environment, such as server identification and authentication information. For example, for the OnePop configuration scenario:
      1. Click Agents, then a specific agent such as Agent:PoolVr, and then Configuration>Directory.

        The Directory pane appears.

      2. Enter information as described in the Help text in the main pane, and click Apply.
    4. For each SAE plug-in agent that the NIC configuration scenario includes, review and if needed update the NIC agent configuration to define properties specific to your environment, such as the event filter and the number of events that the SAE sends to the agent at one time during state synchronization. For example, for the OnePopLogin configuration scenario:
      1. Click Agents, then a specific agent such as Agent:LoginNameVr, and then Configuration>SAE Plug-In.

        The SAE Plug-In pane appears.

        If you plan to change the event filter for the agent, make sure that you are familiar with:

      2. Enter information as described in the Help text in the main pane, and click Apply.

    Configuring the SAE to Communicate with SAE Plug-In Agents for NIC Replication (C-Web Interface)

    For each NIC host that uses SAE plug-in agents, configure a corresponding external plug-in for the SAE. By default, the SAE plug-in agents share events with the single SAE plug-in. You must also configure the SAE to communicate with the SAE plug-in agent in each NIC host that you use in the NIC replication.

    To configure an external plug-in:

    1. Configure an SAE external plug-in.

      See Configuring the SAE for External Plug-Ins (SRC CLI).

    2. Specify the following values for the plug-in:
      • CORBA object reference that has the following syntax:

        host : port-number /NameService# plugInName

        where:

        • host —IP address or name of the machine on which you installed the NIC host that supports the agent

          For local host, use the IP address 127.0.0.1.

        • port-number —Port on which the name server runs

          The default port number is 2809.

        • plugInName —Name under which the agent is registered in the naming service

        Use the format nicsae_groupname /saePort, where groupname is the name of the replication group. (When replication is not used, the format is nicsae/saePort.)

        For example: corbaname::127.0.0.1:2809/NameService#nicsae/saePort

      • Attributes that are sent to the external plug-in for a NIC host. Because the SAE plug-in agents share the event by default, you configure only one for a NIC host.

        Specify the plug-in options that the agent uses. You must specify the options session-id and router-name, and other options that you specified for the agent’s network data types and the agent’s event filter. Specify attributes options of the PAT_OPAQUE attribute type, such as the option dhcp-packet, only if you are using IPv6 addressing.

        Note: Do not include attributes that are not needed.

      • NIC reference as a subscriber tracking plug-in.

    Published: 2014-06-12