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


Classifying Subscribers

Changes that you make to subscriber classification scripts do not affect subscriber sessions that are already established. One effect of this behavior is that static IP subscriber sessions are not closed if the classification script is changed in a way that would no longer cause the SAE to load a profile for certain subscribers.

On JUNOSe routers that use the COPS-PR or COPS XDR router drivers, you can create a subscriber session for the router interface to start services such as script services and aggregate services. The SAE creates the router interface, but does not install any policies on it. You can create a subscriber classification rule, but not an interface classification rule for this interface.

To define subscriber classification scripts with SDX Admin:

  1. In the SDX Admin navigation pane, access the SAE object I=SAE, ou=staticConfiguration, ou=configuration, o=management, o=umc.
  2. In this folder, click on the I=POP-ID object associated with this SAE.

The SSP Configuration pane appears.

  1. Click the User Classification tab.

The following screen appears.

Use the information in Selecting Subscriber Classification Criteria and Configuring Subscriber Classification Targets to configure the subscriber classification script for an SAE object.

Selecting Subscriber Classification Criteria

Subscriber classification criteria define match criteria that are used to find the subscriber profile. Use the fields in this section to define classification criteria.

dhcp

domainName

ifAlias

ifDesc

interfaceName

For JUNOS routing platforms: interfaceName="fe-0/1/0.0"

For forwarding interface: interfaceName="FORWARDING_INTERFACE"

loginName

The loginName can also be used to identify a subscriber session through the SAE CORBA remote API.

loginType

macAddress

nasPortId

radiusClass

retailerDn

serviceBundle

unauthenticatedUserDn

userName

virtualRouterName

For JUNOS routing platforms: name of the routing instance

Sending DHCP Options to the JUNOSe Router

Subscriber classification scripts support DHCP options conveyed through COPS. When COPS reports an address, the JUNOSe router sends DHCP options received for DHCP requests for that address. The DHCP options are available in the subscriber classification context for selecting the subscriber profile to load.

The fields in Table 14 are in the user classification context of subscriber classification scripts.




Table 14: DHCP Options in UserClassificationContext Field 
DHCP Option
UserClassificationContext Field
Comments

giAddr

dhcp.giAddr

Relay agent gateway address

Option 82 data

dhcp.getOption(82)

Content is accessible with getSubOptions()

Client ID

dhcp.getOption(61).getString()

Lease time

dhcp.getOption(51).getInt()

Client requested parameter list

dhcp.getOption(55).getBytes()

Domain name sent to client

dhcp.getOption(12).getString() dhcp.getOption(15).getString()

12 = HostName 15 = DomainName

DNS server address(es) sent to client

dhcp.getOption(6).getIpAddresses()

Subnet mask

dhcp.getOption(1).getIpAddress()

NetBios name server address(es) sent to client

dhcp.getOption(44).getIpAddresses()

NetBios node type

dhcp.getOption(46).getBytes()

Default router address(es) sent to client

dhcp.getOption(3).getIpAddresses()

The DHCP options are accessible for the subscriber classification script with the following syntax:

dhcp.giAddr = "match"

# interpret option 61 as string
dhcp[61].string = "match"

# interpret option 1 (subnet) as dotted decimal IP
dhcp[1].ipAddress = "match"

# option 82, suboption 1, interpreted as string
dhcp[82].subOptions[1].string = "match"

The received DHCP options are also stored in the UserSession and are available through the portal API (method User.getDhcpOptions).

Configuring Subscriber Classification Targets

The target of the subscriber classification script is an LDAP search string. The search string uses a syntax similar to an LDAP URL (see RFC 2255—The LDAP URL Format (December 1997)). The syntax is:

baseDN [ ? [ attributes ] [ ? [ scope ] [ ? [ filter ] ] ] ]

With the exception of baseDN all the fields are optional.

The result of the LDAP search must be exactly one directory object. If no object or more than one object is found, the subscriber session is terminated.

Example: Subscriber Classification Scripts for Static IP Subscriber

In cases such as bridged 1483 DSL with a single subscriber, you can write the subscriber classification script so that it loads a specific subscriber profile. If the interface is matched to a subscriber profile, a subscriber session is immediately established. An SAE application (for example, a portal) can still force the subscriber with this subscriber profile to perform a Web login.

One way to achieve the mapping of subscriber interface to subscriber profile is to provision the assigned interface name in the associated subscriber profile in LDAP. In this case the subscriber classification script can include a rule like this:

[retailerName=default,o=Users,o=umc??sub?(interfaceName=<-interfaceName->)]

# all fastEthernet interfaces are connected to static IP subscriber

loginType = INTF

& interfaceName = fastEthernet*


Another way may include a special encoding of the interface alias (ifAlias) field of the subscriber interface. This encoding must then be provisioned when the interface for the subscriber is provisioned. In this example, the encoding SSP-username is chosen for ifAlias; for example, for subscriber juser the interface alias would be set to SSP-juser. The match is performed with a regular expression, which separates the user ID from the ifAlias prefix.

[retailerName=default,o=Users,o=umc??sub?(uniqueID=<-userId->)]

loginType = INTF

& ifAlias =~ SSP-(?P<userId>.*)

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