Configuring a NIC Scenario with the 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 with the 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: By default, the CORBA naming server on a C-series platform uses port 2809. The NIC host is configured to communicate with this naming server.
To configure a NIC configuration scenario:
- Click Configure, expand Shared >NIC, and click the configuration scenario that you want to configure; for example, Scenario: OnePop.
- In the left pane, expand Agents.
- 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:
- 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:
If you plan to change the event filter for the agent, make sure that you are familiar with:
See SRC-PE Subscribers and Subscriptions Guide, Chapter 11, Configuring Accounting and Authentication Plug-Ins with the SRC CLI.
See the documentation for the SAE CORBA Remote API in the SAE Core API documentation on the Juniper Networks Web site at:
http://www.juniper.net/techpubs/software/management/sdx/api-index.html
Related Topics
- SRC-PE Network Guide, Chapter 9, Locating Subscriber Information with the NIC
- Configuring the NIC with the C-Web Interface
Configuring the SAE to Communicate with SAE Plug-In Agents for NIC Replication with the 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:
See SRC-PE Subscribers and Subscriptions Guide, Chapter 8, Overview of Plug-Ins Included with the SAE.
host
:port-number
/NameService#plugInName
For local host, use the IP address 127.0.0.1.
The default port number is 2809.
Use the format
nicsae_
groupname
/saePort,
wheregroupname
is the name of the replication group. (When replication is not used, the format isnicsae/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
androuter-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 optiondhcp-packet
, only if you are using IPv6 addressing.
Related Topics
- SRC-PE Network Guide, Chapter 9, Locating Subscriber Information with the NIC
- Configuring NIC Replication with the C-Web Interface
- For information about configuring an external plug-in for the SAE, see SRC-PE Subscribers and Subscriptions Guide, Chapter 11, Configuring Accounting and Authentication Plug-Ins with the SRC CLI.
Obtaining Interface Configuration Information for OnePopStaticRouteIp
If you use the OnePopStaticRouteIp configuration scenario, you must obtain JUNOS interface configuration information for the NIC. To get this information, you must run Network Publisher on a Solaris platform to gather the interface information.
To run Network Publisher on a Solaris platform:
See SRC-PE Getting Started Guide, Chapter 33, Installing the SRC Software on a Solaris Platform.
- On the Solaris platform, edit the /opt/UMC/nic/etc/networkPublisher/config.properties file and run Network Publisher. When you specify the directory configuration in the file, configure the connection to the directory on a C-series platform.
See SRC-PE Network Guide, Chapter 12, Obtaining Interface Configuration for OnePopStaticRouteIp on Solaris Platforms.
Related Topics