Domain Mapping Overview
Domain mapping enables you to configure a map that specifies access options and session-specific parameters. The map is based on the domain name of subscriber sessions — the router applies the mapped options and parameters to sessions for subscribers that have the specified domains. For example, you might configure a domain map that is based on the domain name xyz.com. The options and parameters in that domain map are then applied when subscribers with the specified domain name (for example, bob@xyz.com, raj@xyz.com, and juan@xyz.com) request an AAA service.
The domain map provides efficiency, and enables you to make changes for a large number of subscribers in one operation. For example, if an address assignment pool becomes exhausted due to the number of subscribers obtaining addresses from the pool, you can create a domain map that specifies that subscribers in a particular domain obtain addresses from a different pool. In another use of the domain map, you might create a new dynamic profile and then configure the domain map to specify which subscribers (by their domain) use that dynamic profile.
 | Note: Subscriber management is supported in the default logical system only. The documentation for the subscriber management domain mapping feature describes using the aaa-logical-system and target-logical-system statements to configure mapping to a non-default logical system. These statements are for future extensions of subscriber management and are not supported in current Junos OS releases. |
Table 1 describes the access options and parameters you can configure in the domain map.
Table 1: Domain Map Options and Parameters
Option | Description |
|---|---|
AAA logical system/routing instance | Logical system/routing instance in which AAA sends authentication and accounting requests for the subscriber sessions. Subscriber management is supported in the default logical system only. |
Access profile | Access profile applied to subscriber sessions. |
Address pool | Address pool used to allocate addresses to subscribers. |
Domain name rules | Rules for domain name usage, including domain name stripping, supported delimiters, and parse direction (delimiters and the parse direction are configured globally). |
Dynamic profile | Dynamic profile applied to subscriber sessions. |
PADN parameters | PPPoE route information for subscriber sessions. |
Target logical system/routing instance | Logical system/routing instance to which the subscriber interface is attached. Subscriber management is supported in the default logical system only. |
Tunnel profile | Tunnel profile applied to subscriber sessions. |
Default Domain Map
You can configure a default domain map that the router uses for subscribers whose domain name does not explicitly match any existing domain map. The router also uses the default domain map when a subscriber username does not include a domain name.
You might configure the default domain map to provide limited feature support for guest subscribers, such as a specific address pool used for guests or the routing instance that provides AAA services. When the router is unable to match a subscriber request to a domain map, the router then uses the rules specified in the default domain map configuration to handle the subscriber request.
