Configuring ISG Policies for Automatic Subscriber Logon
|
||||||||||||||||||||||||||||||||||||||||||||||||||
Contents
Configuring ISG Policies for Automatic Subscriber LogonLast Updated: November 30, 2011
Intelligent Services Gateway (ISG) is a Cisco IOS software feature set that provides a structured framework in which edge devices can deliver flexible and scalable services to subscribers. This module contains information on how to configure ISG to use specified identifiers in place of the username in authorization requests, enabling a user profile to be downloaded from an authentication, authorization, and accounting (AAA) server as soon as packets are received from a subscriber.
Finding Feature InformationYour software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for ISG Automatic Subscriber LogonDepending on your AAA implementation, you may need to configure one of the following identifiers in the password field of the user profile: source IP address, MAC address, remote ID, circuit ID. You may also need to configure a global address in the password field. To use circuit ID and remote ID for authorization for IP sessions, the DSLAM must insert the circuit ID and remote ID in the DHCP Option 82 information. To use remote ID for authorization of PPPoE sessions, the PPPoE client must provide the remote ID information in the PPPoE Tag ID or line ID. Restrictions for ISG Automatic Subscriber LogonThe username field in an authorization request has a limit of 253 characters. Information About ISG Automatic Subscriber Logon
Overview of ISG Automatic Subscriber LogonService providers commonly implement a policy at the start of IP sessions that redirects all subscriber packets to a logon portal for authentication. Following successful authentication, per-subscriber authorization data is typically returned from a AAA server. For some deployments, usually in subscriber networks that are well protected against spoofing and denial-of-service (DoS) attacks, service providers are willing to forgo authentication and trust subscriber identity. ISG automatic subscriber logon allows service providers to grant certain subscribers access to services without requiring the subscribers to log on. ISG automatic subscriber logon enables a specified identifier to be used in place of the username in authorization requests. Enabling the AAA server to authorize subscribers on the basis of a specified identifier allows subscriber profiles to be downloaded from the AAA server as soon as packets are received from subscribers. The event that triggers automatic subscriber logon is session-start. For IP sessions, session-start occurs when a DHCP DISCOVER request is received or when an unrecognized source IP address is detected. For PPPoE sessions, session-start occurs when a client attempts to initiate a session by sending a PPPoE Active Discovery Initiation (PADI) packet. Supported Identifiers for ISG Automatic Subscriber LogonFor IP sessions, an ISG device can be configured to use the following identifiers in place of the username in authorization requests: IP address, MAC address, circuit ID, remote ID, or a combination of the circuit ID and remote ID. For PPPoE sessions, an ISG device can be configured to use the remote ID in place of the username in authorization requests. Authorization Based on Circuit ID and Remote IDThe circuit ID and remote ID fields are part of the DHCP relay agent information option (also referred to as Option 82) and the PPPoE Tag VSA. These fields are inserted into DHCP and PPPoE messages by a DSLAM. An ISG device can be configured to use the circuit ID, remote ID, or a combination of circuit ID and remote ID as the username in authorization requests. By default, the ISG device will use the circuit ID and remote ID that are provided by the Layer 2 edge access device for authorization. If the ip dhcp relay information option command is configured, the ISG device will use the circuit ID and remote ID that are received in a DHCP message. Accounting Behavior When ISG Automatic Subscriber Logon Is ConfiguredAccounting Behavior for MAC-Address-Based AuthorizationIf the MAC address is sent as the username in authorization requests, the MAC address will also be sent as the Calling Station ID in accounting records. Accounting Behavior for Remote-ID- and Circuit-ID-Based AuthorizationFor IP sessions that use DHCP Option 82 authorization, accounting messages are sent to the AAA server with the Circuit ID and Remote ID Cisco VSAs. Although you can configure a combination of circuit ID and remote ID as the username for authorization, the attributes are sent individually in accounting records. You can also configure the circuit ID and remote ID to be sent together in accounting records as the NAS Port ID. For PPPoE sessions, the Remote ID VSA is sent in accounting records, and the remote ID is also sent as the NAS Port ID. If the radius-server attribute 31 remote-id command is configured, the remote ID is sent in accounting records as the Calling Station ID. How to Configure ISG Policies for Automatic Subscriber Logon
Identifying Traffic for Automatic Logon in a Control Policy Class MapPerform this task to configure a control policy class map that specifies the traffic to which ISG automatic subscriber logon will apply.
DETAILED STEPS
Configuring an ISG Control Policy for Automatic Subscriber LogonPerform this task to configure an ISG control policy that initiates subscriber authorization and inserts a specified identifier into the username field of the authorization request. DETAILED STEPS What to Do NextYou must apply the control policy to a context by using the service-policy type control command. For information about applying control policies, see the module "Configuring ISG Control Policies". You may want to configure policies to determine what should happen for autologon subscribers whose IP address or MAC address authorization fails; for example, you may want to redirect the subscriber to the policy server for authentication. Enabling the Remote-ID to Be Sent as the Calling-Station-IDPerform this task to enable the ISG device to send the remote ID in the Calling-Station-ID (attribute 31) field of accounting records and access requests. DETAILED STEPS
Verifying ISG Automatic Subscriber Logon
SUMMARY STEPS
DETAILED STEPS
Configuration Examples for ISG Automatic Subscriber LogonAutomatic Subscriber Logon Based on IP Address ExampleIn the following example, if the client is from the 1.1.1.0 subnet, the ISG sends an authorization request to the list "TAL_LIST" with the subscriber's source IP address as the username. If the authorization request is successful, any automatic-activation services specified in the returned user profile are activated for the session, and the execution of rules within the control policy stops. If the authorization is not successful, the rule execution proceeds, and the subscriber is redirected to the policy server to log in. If the subscriber does not log in within five minutes, the session is disconnected. ISG Configurationinterface Ethernet0/0 service-policy type control RULEA aaa authorization network TAL_LIST group radius aaa authentication login LOCAL local access-list 100 permit ip any any class-map type traffic match-any all-traffic match access-group input 100 match access-group output 100 policy-map type service redirectprofile class type traffic all-traffic redirect to ip 10.0.0.148 port 8080 class-map type control match-all CONDA match source-ip-address 10.1.1.0 255.255.255.0 ! class-map type control match-all CONDF match timer TIMERB match authen-status unauthenticated policy-map type control RULEA class type control CONDA event session-start 1 authorize aaa list TAL_LIST password cisco identifier source-ip-address 2 service-policy type service aaa list LOCAL name redirectprofile 3 set-timer TIMERB 5 minutes ! class type control CONDF event timed-policy-expiry 1 service disconnect Additional ReferencesMIBsTechnical Assistance
Feature Information for ISG Automatic Subscriber LogonThe following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. © 2011 Cisco Systems, Inc. All rights reserved.
|
||||||||||||||||||||||||||||||||||||||||||||||||||