[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


NIC Agents Used in the NIC Configuration Scenarios

When you configure a NIC configuration scenario, you use the basic configuration for each NIC agent in the scenario, but modify properties such as directory properties to make the agent configuration compatible with your SRC configuration. The NIC configuration scenario that you use determines which agents appear in your configuration.

Table 12 lists all agents that are available in the various configuration scenarios.




Table 12: NIC Agents 
Agent Name
Type of Agent
Type of Information

AcctIdIp

SAE plug-in

Mappings of accounting IDs of a subscribers to the SAE IOR and subscriber IP addresses to accounting ID(s)

DnVr

SAE plug-in

Mappings of enterprise access DNs to VRs

Enterprise

Directory

List of enterprise names

IpAcctId

SAE plug-in

Mappings of subscriber IP addresses to accounting IDs

IpLoginName

SAE plug-in

Mappings of IP addresses to login names

IpVr

SAE plug-in

Mappings of IP addresses to VRs

LoginNameVr

SAE plug-in

Mappings of login names to VRs

PoolVr

Directory

Mappings of IP pools to VRs

UserNameVr

SAE plug-in

Mappings of subscriber IP addresses to accounting IDs

VrSaeId

Directory

Reads information about virtual routers and the mappings between virtual routers and SAEs

Table 13 shows the types of agents that each configuration scenario uses.




Table 13: Agents in Configuration Scenarios 
NIC Configuration Scenario
Directory Agents
SAE Plug-In Agents

OnePop

PoolVr, VrSaeId

OnePopAcctId

PoolVr, VrSaeId

AcctIdIp, IpAcctId

OnePopDnSharedIp

PoolVr, VrSaeId, Enterprise

DnVr

OnePopDynamicIp

PoolVr, VrSaeId

OnePopLogin

Pool, VrSaeId

IpLoginName, LoginNameVr

OnePopPcmm

PoolVr, VrSaeId

OnePopSharedIp

PoolVr, VrSaeId

IpVr

MultiPop

PoolVr, VrSaeId, site-specific versions of PoolVr and VrSaeId

IpVr

OnePopAllRealms

PoolVr, VrSaeId, Enterprise

IpVr

OnePopPrimaryUser

VrSaeId

UserNameVr

OnePopStaticRouteIp

VrSaeId, PoolInterface


NOTE: If you use a configuration scenario that includes an SAE plug-in agent, make sure that your network has a CORBA naming server that includes the names of the servers that host the SAE plug-in agents. The SRC software distribution includes a CORBA naming server in the omniORB package.


[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]