Feedback
Table Of Contents
Cisco IOS Intelligent Services Gateway Commands
aaa authorization radius-proxy
aaa authorization subscriber-service
aaa server radius dynamic-author
aaa server radius policy-device
authenticate (control policy-map class)
authenticate (service policy-map)
clear subscriber policy dpm statistics
clear subscriber policy peer session
clear subscriber trace history
debug subscriber aaa authorization
debug subscriber policy dpm timestamps
ip portbundle (service policy-map)
ip vrf forwarding (service policy map)
Cisco IOS Intelligent Services Gateway Commands
aaa authorization radius-proxy
To configure authentication, authorization, and accounting (AAA) authorization methods for Intelligent Services Gateway (ISG) RADIUS proxy subscribers, use the aaa authorization radius-proxy command in global configuration mode. To remove authorization methods for ISG RADIUS proxy subscribers, use the no form of this command.
aaa authorization radius-proxy {default | list-name} method1 [method2 [method3...]]
no aaa authorization radius-proxy {default | list-name} method [method2 [method3...]]
Syntax Description
Command Default
A AAA method list for ISG RADIUS proxy clients is not specified.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the aaa authorization radius-proxy command to enable authorization and to create named method lists, which define authorization methods that are used to authorize ISG RADIUS proxy subscribers. Method lists for authorization define the ways in which authorization is performed and the sequence in which these methods are performed. A method list is a named list describing the authorization methods to be used, in sequence. Cisco IOS software uses the first method listed to authorize users for specific network services; if that method fails to respond, the Cisco IOS software selects the next method listed in the method list. This process continues until there is successful communication with a listed authorization method, or all methods defined are exhausted.
Examples
The following example configures an ISG RADIUS proxy authorization method list called "RP". The server group called "EAP" is the method specified in that method list. The control policy called "PROXYRULE" contains a policy rule to send RADIUS proxy packets to the method list "RP".
aaa group server radius EAP server 10.2.36.253 auth-port 1812 acct-port 1813aaa authorization radius-proxy RP group EAPpolicy-map type control PROXYRULEclass type control always event session-start1 proxy aaa list RPRelated Commands
aaa authorization subscriber-service
To specify one or more authentication, authorization, and accounting (AAA) authorization methods for Intelligent Services Gateway (ISG) to use in providing subscriber service, use the aaa authorization subscriber-service command in global configuration mode. To remove this specification, use the no form of this command.
aaa authorization subscriber-service {default {cache | group | local} | list-name} method1 [method2...]
no aaa authorization subscriber-service {default {cache | group | local} | list-name} method1 [method2...]
Syntax Description
default
Used with either the cache, group or local keywords to select the default authorization method.
cache
Specifies the cached-group for the default authorization method.
group
Specifies the server-group for the default authorization method.
local
Specifies the local database for the default authorization method.
list-name
Character string used to name the list of authorization methods.
method1 [method2...]
Specifies an authorization method or (optionally) multiple authorization methods to be used for authorization. A method may be any one of the keywords listed in Table 1.
Command Default
A method list is not specified.
Command Modes
Global configuration
Command History
Usage Guidelines
Table 1 lists the keywords that can be used with the aaa authorization subscriber-service command to specify authorization methods.
Cisco IOS software supports the following methods of authorization of ISG subscriber services:
•
RADIUS—The network access server requests authorization information from the RADIUS security server group. RADIUS authorization defines specific rights for users by associating attributes, which are stored in a database on the RADIUS server, with the appropriate user.
•
•
When you create a named method list, you are defining a particular list of authorization methods for the indicated authorization type.
Once defined, method lists must be applied to specific lines or interfaces before any of the defined methods will be performed.
The authorization aaa subscriber-service command causes a request packet containing a series of AV pairs to be sent to the RADIUS or TACACS daemon as part of the authorization process. The daemon can do one of the following:
•
•
•
Examples
The following example defines the subscriber service authorization method list named "mygroup", which specifies RADIUS authorization. If the RADIUS server fails to respond, local authorization will be performed.
aaa authorization subscriber-service mygroup group radius localRelated Commands
aaa server radius dynamic-author
To configure a device as an authentication, authorization, and accounting (AAA) server to facilitate interaction with an external policy server, use the aaa server radius dynamic-author command in global configuration mode. To remove this configuration, use the no form of this command.
aaa server radius dynamic-author
no aaa server radius dynamic-author
Syntax Description
This command has no arguments or keywords.
Command Default
The device will not function as a server when interacting with external policy servers.
Command Modes
Global configuration
Command History
Usage Guidelines
Dynamic authorization allows an external policy server to dynamically send updates to a device. Once the aaa server radius dynamic-author command is configured, dynamic authorization local server configuration mode is entered. Once in this mode, the RADIUS application commands can be configured.
Dynamic Authorization for the Intelligent Services Gateway (ISG)
ISG works with external devices, referred to as policy servers, that store per-subscriber and per-service information. ISG supports two models of interaction between the ISG device and external policy servers: initial authorization and dynamic authorization.
The dynamic authorization model allows an external policy server to dynamically send policies to the ISG. These operations can be initiated in-band by subscribers (through service selection) or through the actions of an administrator, or applications can change policies on the basis of an algorithm (for example, change session quality of service (QoS) at a certain time of day). This model is facilitated by the Change of Authorization (CoA) RADIUS extension. CoA introduced peer-to-peer capability to RADIUS, enabling ISG and the external policy server each to act as a RADIUS client and server.
Examples
The following example configures the ISG to act as a AAA server when interacting with the client at IP address 10.12.12.12:
aaa server radius dynamic-authorclient 10.12.12.12 key ciscomessage-authenticator ignoreRelated Commands
aaa server radius policy-device
To enable Intelligent Services Gateway (ISG) RADIUS server configuration mode, in which the ISG RADIUS server parameters can be configured, use the aaa server radius policy-device command in global configuration mode. To remove the RADIUS server configuration, use the no form of this command.
aaa server radius policy-device
no aaa server radius policy-device
Syntax Description
This command has no arguments or keywords.
Command Default
RADIUS ISG parameters are not configured. No external policy device is configured.
Command Modes
Global configuration (config)
Command History
12.2(33)SRC
This command was introduced.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB
Usage Guidelines
The aaa server radius policy-device command enables ISG RADIUS server configuration mode, in which global ISG RADIUS server parameters can be configured.
Examples
The following example configures a shared encryption key for the RADIUS client and specifies authentication details.
Router(config)#aaa server radius policy-deviceRouter(config-locsvr-policy-device-radius)#key ciscoRouter(config-locsvr-policy-device-radius)#client 10.1.1.13Router(config-locsvr-policy-device-radius)#message-authenticator ignoreRelated Commands
key
Configures a shared encryption key for the RADIUS clients.
client
Allows modification of RADIUS clients at run time.
message-authenticator
Authenticates messages from clients.
aaa server radius proxy
To enable Intelligent Services Gateway (ISG) RADIUS proxy configuration mode, in which ISG RADIUS proxy parameters can be configured, use the aaa server radius proxy command in global configuration mode. To remove the ISG RADIUS proxy configuration, use the no form of this command.
aaa server radius proxy
no aaa server radius proxy
Syntax Description
This command has no arguments or keywords.
Command Default
ISG RADIUS proxy parameters are not configured, and ISG does not serve as a RADIUS proxy.
Command Modes
Global configuration
Command History
Usage Guidelines
The aaa server radius proxy command enables ISG RADIUS proxy server configuration mode, in which global RADIUS proxy parameters can be configured. The client command can be used in RADIUS proxy server configuration mode to specify a client for which RADIUS proxy parameters can be configured. Client-specific RADIUS proxy configurations take precedence over the global RADIUS proxy server configuration.
Examples
The following example configures the accounting port to be used by ISG for all RADIUS proxy clients:
aaa server radius proxyaccounting port 1200accounting aaa list
To enable Intelligent Services Gateway (ISG) accounting and specify an authentication, authorization, and accounting (AAA) method list to which accounting updates will be forwarded, use the accounting aaa list command in service policy-map configuration or service policy traffic class configuration mode. To disable ISG accounting, use the no form of this command.
accounting aaa list aaa-method-list
no accounting aaa list aaa-method-list
Syntax Description
aaa-method-list
AAA method list to which Accounting-Start, interim, and Accounting-Stop records will be sent.
Command Default
ISG accounting is not enabled.
Command Modes
Service policy-map configuration
Service policy traffic class configurationCommand History
Usage Guidelines
An ISG sends accounting records to the AAA method list specified by the accounting aaa list command. A AAA method list must also be configured by using the aaa accounting command. See the Cisco IOS Security Command Reference for more information.
Use the accounting aaa list command to enable per-session accounting by configuring the command in service policy-map configuration mode. Per-session accounting can also be configured on a remote AAA server by adding the ISG accounting attribute to a user profile or to a service profile that does not include a traffic class.
To enable per-flow accounting, enter the accounting aaa list command in service policy traffic class configuration mode. Per-flow accounting can also be configured on a remote AAA server by adding the ISG accounting attribute to a service profile that includes a traffic class.
Examples
The following example shows ISG per-session accounting configured for a service called "video1":
policy-map type service video1accounting aaa list mlist1The following example shows ISG per-flow accounting configured for a service called "video1":
class-map type traffic match-any video1match access-group output 101match access-group input 100!policy-map type service video1class type traffic video1accounting aaa list mlist1Related Commands
aaa accounting
Enables AAA accounting of requested services for billing or security purposes when you use RADIUS or TACACS+.
accounting method-list
To configure Intelligent Services Gateway (ISG) to forward accounting packets from RADIUS proxy clients to a specified server, use the accounting method-list command in RADIUS proxy server configuration mode or RADIUS proxy client configuration mode. To disable the forwarding of accounting packets from RADIUS proxy clients, use the no form of this command.
accounting method-list {list-name | default}
no accounting method-list {list-name | default}
Syntax Description
list-name
Name of the method list to which accounting packets are sent.
default
Specifies that accounting packets will be forwarded to the default RADIUS server.
Command Default
ISG RADIUS proxy handles accounting packets locally.
Command Modes
RADIUS proxy server configuration
RADIUS proxy client configurationCommand History
Usage Guidelines
By default, ISG RADIUS proxy responds locally to accounting packets it receives. The accounting method-list command configures ISG to forward accounting packets from RADIUS proxy clients to a specified method list. Forwarding of accounting packets can be configured globally for all RADIUS proxy clients or on a per-client basis. The per-client configuration of this command overrides the global configuration.
The default method list is configured with the aaa accounting command.
Examples
The following example shows the ISG configured to forward accounting packets from all RADIUS proxy clients to the method list "RP-ACCT-MLIST":
aaa group server radius RP-BILLINGserver 10.52.199.147 auth-port 1645 acct-port 1646server 10.52.199.148 auth-port 1812 acct-port 1813!aaa group server radius RP-BILLING-HOTSTANDBYserver 10.52.200.20 auth-port 1645 acct-port 1646server 10.52.200.21 auth-port 1812 acct-port 1813!...aaa accounting network RP-ACCT-MLIST start-stop broadcast group RP-BILLING group RP-BILLING-HOTSTANDBY...aaa server radius proxykey ciscoaccounting method-list RP-ACCT-MLISTclient 10.52.100.20!...radius-server host 10.52.199.147 auth-port 1645 acct-port 1646 key troyradius-server host 10.52.199.148 auth-port 1812 acct-port 1813 key tempestradius-server host 10.52.200.20 auth-port 1645 acct-port 1646 key captainradius-server host 10.52.200.21 auth-port 1812 acct-port 11813 key scarletRelated Commands
accounting port
To specify the port on which Intelligent Services Gateway (ISG) listens for accounting packets from RADIUS proxy clients, use the accounting port command in RADIUS proxy server configuration or RADIUS proxy client configuration mode. To return to the default value, use the no form of this command.
accounting port port-number
no accounting port
Syntax Description
port-number
Port on which ISG listens for accounting packets from RADIUS proxy clients. The default is 1646.
Command Default
ISG listens for accounting packets from RADIUS proxy clients on port 1646.
Command Modes
RADIUS proxy server configuration (config-locsvr-proxy-radius)
RADIUS proxy client configuration (config-locsvr-radius-client)Command History
Usage Guidelines
The accounting port can be specified globally for all RADIUS proxy clients, or it can be specified per client. The per-client configuration of this command overrides the global configuration.
Examples
The following example configures ISG to listen for accounting packets on port 1200 for all RADIUS proxy clients:
aaa server radius proxyaccounting port 1200The following example configures ISG to listen for accounting packets on port 1200 for the RADIUS proxy client with the IP address 10.10.10.10:
aaa server radius proxyclient 10.10.10.10accounting port 1200Related Commands
arp ignore local
To prevent Intelligent Services Gateway (ISG) from replying to incoming Address Resolution Protocol (ARP) requests for destinations on the same interface, use the arp ignore local command in IP subscriber configuration mode. To reset to the default, use the no form of this command.
arp ignore local
no arp ignore local
Syntax Description
This command has no arguments or keywords.
Command Default
ISG replies to incoming ARP requests for destinations on the same interface.
Command Modes
IP subscriber configuration (config-subscriber)
Command History
Usage Guidelines
The arp ignore local command blocks ISG from replying to ARP requests received on an interface if the source and destination IP addresses for an ARP request are on the same VLAN that the interface is connected to, or if the destination IP address is in a different subnet but is routable from the interface where the ARP is received. ISG does, however, reply to ARP requests when the source and destination IP addresses are in the same subnet if the IP addresses belong to different VLANs.
If the arp ignore local command is configured and a subscriber session is in virtual routing and forwarding (VRF) transfer mode, ISG will reply to an ARP request from the customer premises equipment (CPE) if:
•
•
When the CPE receives the ARP reply and routes the corresponding IP packets to ISG, ISG routes the packets in the VRF domain.
Examples
The following example shows how to configure ISG to ignore ARP requests received on Ethernet interface 0/0.1 if the source and destination are in the same subnet:
Router(config)# interface ethernet 0/0.1Router(config-subif)# ip subscriber l2-connectedRouter(config-subscriber)# arp ignore localRelated Commands
authenticate (control policy-map class)
To initiate an authentication request for an Intelligent Services Gateway (ISG) subscriber session, use the authenticate command in control policy-map class configuration mode. To remove an authentication request for an ISG subscriber session, use the no form of this command.
action-number authenticate [variable varname] [aaa list {list-name | default}]
no action-number authenticate [variable varname] [aaa list {list-name | default}]
Syntax Description
Command Default
The control policy will not initiate authentication.
Command Modes
Control policy-map class configuration
Command History
12.2(28)SB
This command was introduced.
12.2(31)SB2
The variable keyword and varname argument were added.
Usage Guidelines
The authenticate command configures an action in a control policy map.
Control policies define the actions the system will take in response to specified events and conditions. A control policy map is used to configure an ISG control policy. A control policy is made of one or more control policy rules. A control policy rule is an association of a control class and one or more actions. The control class defines the conditions that must be met before the actions will be executed. The actions are numbered and executed sequentially within the policy rule.
Note that if you specify the default method list, the default list will not appear in the output of the show running-config command. For example, if you configure the following command:
Router(config-control-policymap-class-control)# 1 authenticate aaa list defaultthe following will display in the output for the show running-config command:
1 authenticateNamed method lists will display in the show running-config command output.
Examples
The following example shows an ISG configured to initiate an authentication request upon account logon. The authentication request will be sent to the AAA method list called AUTH-LIST.
policy-map type control LOGINclass type control always event account-logon1 authenticate aaa list AUTH-LIST2 service-policy type service unapply BLIND-RDTThe following example shows the policy map configured to initiate an authentication request using a name stored in the variable NEWNAME, instead of unauthenticated-username, using the AAA list EXAMPLE. The authenticate statement is shown in bold:
policy-map type control REPLACE_WITH_example.comclass type control always event session-start1 collect identifier unauthenticated-username2 set NEWNAME identifier unauthenticated-username3 substitute NEWNAME "(.*@).*" "\1example.com"4 authenticate variable NEWNAME aaa list EXAMPLE5 service-policy type service name examplepolicy-map type service abcservice vpdn group 1bba-group pppoe globalvirtual-template 1!interface Virtual-Template1service-policy type control REPLACE_WITH_example.comRelated Commands
authenticate (service policy-map)
To specify authentication as a condition of service activation and initiate authentication requests for Intelligent Services Gateway (ISG) subscribers accessing a service, use the authenticate command in service policy-map configuration mode. To remove this specification, use the no form of this command.
authenticate aaa list name-of-list
no authenticate aaa list name-of-list
Syntax Description
Command Default
Authentication is not specified as a condition of service activation.
Command Modes
Service policy-map configuration
Command History
Usage Guidelines
The authenticate (service policy-map) command specifies authentication as a condition of service activation in an ISG service policy map. Service policy maps define ISG subscriber services. Services can also be defined in service profiles. Service policy maps and service profiles serve the same purpose; the only difference between them is that a service policy map is defined on the local device using the policy-map type service command, and a service profile is configured on an external device, such as a AAA server.
Examples
The following example specifies authentication as a condition of service activation in the ISG service called "service1":
policy-map type service service1authenticate aaa list mlistRelated Commands
authentication port
To specify the port on which Intelligent Services Gateway (ISG) listens for authentication packets from RADIUS proxy clients, use the authentication port command in RADIUS proxy server configuration or RADIUS proxy client configuration mode. To return to the default setting in which ISG listens for accounting packets on port 1645, use the no form of this command.
authentication port port-number
no authentication port port-number
Syntax Description
port-number
Port on which ISG listens for authentication packets from RADIUS proxy clients. The default is 1645.
Command Default
ISG listens for authentication packets from RADIUS proxy clients on port 1645.
Command Modes
RADIUS proxy server configuration
RADIUS proxy client configurationCommand History
Usage Guidelines
The authentication port can be specified globally for all RADIUS proxy clients, or it can be specified per client. The per-client configuration of this command overrides the global configuration.
Examples
The following example configures ISG to listen for authentication packets on port 1200 for all RADIUS proxy clients:
aaa server radius proxyauthentication port 1200The following example configures ISG to listen for authentication packets on port 1200 for the RADIUS proxy client with the IP address 10.10.10.10 :
aaa server radius proxyclient 10.10.10.10authentication port 1200Related Commands
authorize identifier
To initiate a request for authorization based on a specified identifier in an Intelligent Services Gateway (ISG) control policy, use the authorize identifier command in control policy-map class configuration mode. To remove this action from the control policy map, use the no form of this command.
action-number authorize [aaa {list-name | list {list-name | default}} [password password]] [upon network-service-found {continue | stop}] [use method authorization-type] identifier identifier-type [plus identifier-type]
no action-number
Syntax Description
Command Default
The control policy will not initiate authorization.
Command Modes
Control policy-map class configuration (config-control-policymap-class-control)
Command History
12.2(28)SB
This command was introduced.
12.2(33)SRD
The vendor-class-id keyword was added.
Cisco IOS XE Release 2.2
This command was integrated into Cisco IOS XE Release 2.2.
Usage Guidelines
The authorize identifier command configures an action in a control policy map. A control policy map is used to configure an ISG control policy, which defines the actions the system takes in response to specified events and conditions.
For sessions triggered by an unrecognized IP address, the MAC address should be used only when the subscriber is one hop away.
The auto-detect keyword allows authorization to be performed on Cisco Catalyst switches with remote-ID:circuit-ID and on DSL Forum switches with circuit-ID only.
Note that if you specify the default method list, the default list will not appear in the output of the show running-config command. For example, if you configure the following command:
Router(config-control-policymap-class-control)# 1 authorize aaa list default password ABC identifier nas-portthe following will display in the output for the show running-config command:
1 authorize aaa password ABC identifier nas-portNamed method lists will display in the show running-config command output.
When ISG automatic subscriber login is configured using the authorize identifier command, the ISG uses specified identifiers in place of the username in authorization requests, enabling a user profile to be downloaded from a AAA server as soon as packets are received from a subscriber.
Examples
In the following example, ISG is configured to send a request for authorization on the basis of the source IP address. The system will perform this action at session start when the conditions that are defined in control class "CONDA" are met.
policy-map type control RULEAclass type control CONDA event session-start1 authorize aaa list TAL_LIST password cisco identifier source-ip-address2 service-policy type service aaa list LOCAL service redirectprofileRelated Commands
auth-type (ISG)
To specify the type of authorization Intelligent Services Gateway (ISG) will use for RADIUS clients, use the auth-type command in dynamic authorization local server configuration mode. To return to the default authorization type, use the no form of this command.
auth-type {all | any | session-key}
no auth-type
Syntax Description
Command Default
All attributes must match for authorization to be successful.
Command Modes
Dynamic authorization local server configuration (config-locsvr-da-radius)
Command History
Usage Guidelines
An ISG can be configured to allow external policy servers to dynamically send policies to the ISG. This functionality is facilitated by the Change of Authorization (CoA) RADIUS extension. CoA introduced peer to peer capability to RADIUS, enabling ISG and the external policy server each to act as a RADIUS client and server. Use the auth-type command to specify the type of authorization ISG will use for RADIUS clients.
Examples
The following example configures the ISG authorization type:
aaa server radius dynamic-authorclient 10.0.0.1auth-type anyRelated Commands
aaa server radius dynamic-author
Configures an ISG as a AAA server to facilitate interaction with an external policy server.
available
To create a condition in an Intelligent Services Gateway (ISG) control policy that will evaluate true if the specified subscriber identifier is locally available, use the available command in control class-map configuration mode. To remove this condition, use the no form of this command.
available {authen-status | authenticated-domain | authenticated-username | dnis | media | mlp-negotiated | nas-port | no-username | protocol | service-name | source-ip-address | timer | tunnel-name | unauthenticated-domain | unauthenticated-username}
no available {authen-status | authenticated-domain | authenticated-username | dnis | media | mlp-negotiated | nas-port | no-username | protocol | service-name | source-ip-address | timer | tunnel-name | unauthenticated-domain | unauthenticated-username}
Syntax Description
Command Default
A condition that will evaluate true if the specified subscriber identifier is locally available is not created.
Command Modes
Control class-map configuration
Command History
Usage Guidelines
The available command is used to configure a condition within a control class map. A control class map, which is configured with the class-map type control command, specifies conditions that must be met for a control policy to be activated, and, optionally, the event that causes the class to be evaluated. A control class map can contain multiple conditions, each of which will evaluate to either true or false. Match directives can be used to specify whether all, any, or none of the conditions must evaluate true in order for the class as whole to evaluate true.
The class type control command is used to associate a control class map with a policy control map.
Examples
The following example shows a control class map called "class3" configured with three conditions. The match-all keyword indicates that all of the conditions must evaluate true before the class evaluates true. The class type control command associates "class3" with the control policy map called "rule4".
class-map type control match-all class3match access-type pppoematch domain cisco.comavailable nas-port-id!policy-map type control rule4class type control class3authorize nas-port-id!Related Commands
calling-station-id format
To specify the format of the Calling-Station-ID in attribute 31, use the calling-station-id format command in RADIUS proxy server configuration mode or RADIUS proxy client configuration mode. To return to the default format, use the no form of this command.
calling-station-id format {mac-address | msisdn}
no calling-station-id format {mac-address | msisdn}
Syntax Description
mac-address
Specifies the MAC address in attribute 31.
msisdn
Specifies the Mobile Subscriber Integrated Services Digital Network Number (MSISDN) in attribute 31.
Command Default
The default format is MAC address.
Command Modes
RADIUS proxy server configuration (config-locsvr-proxy-radius)
RADIUS proxy client configuration (config-locsvr-radius-client)Command History
Usage Guidelines
Use the calling-station-id format command to differentiate and identify the session based on the downstream device type and receive the values in attribute 31. For example, if the downstream device type is Public Wireless LAN (PWLAN), then the Intelligent Services Gateway (ISG) RADIUS proxy identifies the value in attribute 31 as MAC address and MSISDN for the Gateway GPRS Support Node (GGSN) device type.
Examples
The following example shows how to configure ISG to specify MSISDN as the calling station ID for a RADIUS proxy server:
Router(config)# aaa new-modelRouter(config)# aaa server radius proxyRouter(config-locsvr-proxy-radius)# calling-station-id format msisdnRelated Commands
class type control
To specify a control class for which actions may be configured in an Intelligent Services Gateway (ISG) control policy, use the class type control command in control policy-map configuration mode. To remove the control class from the control policy map, use the no form of this command.
class type control {control-class-name | always} [event {access-reject | account-logoff | account-logon | acct-notification | credit-exhausted | dummy-event | quota-depleted | radius-timeout | service-failed | service-start | service-stop | session-default-service | session-restart | session-service-found | session-start | timed-policy-expiry}]
no class type control {control-class-name | always} [event {access-reject | account-logoff | account-logon | acct-notification | credit-exhausted | dummy-event | quota-depleted | radius-timeout | service-failed | service-start | service-stop | session-default-service | session-restart | session-service-found | session-start | timed-policy-expiry}]
Syntax Description
Command Default
A control class is not specified in a control policy map.
Command Modes
Control policy-map configuration (config-control-policymap)
Command History
Usage Guidelines
A control class map defines the conditions that must be met and events that must occur before a set of actions will be executed. Use the class type control command to associate a control class map with one or more actions in a control policy map. The association of a control class and a set of actions is called a control policy rule.
Using the class type control command with the always keyword creates a control policy rule that will always be treated as the lowest-priority rule in a control policy map.
To create a named control class map, use the class-map type control command.
The session-restart keyword applies to DHCP-initiated IP sessions only.
Using the class type control command with the acct-notification keyword causes the control class to be evaluated upon occurrence of an accounting notification.
Examples
The following example shows the configuration of a class map called "class3". The class type control command adds "class3" to the control policy map "policy1". When "class3" evaluates true, the action associated with the class will be executed.
class-map type control match-all class3match access-type pppoematch domain cisco.comavailable nas-port-id!policy-map type control policy1class type control class3authorize nas-port-id!service-policy type control rule4Related Commands
class type traffic
To specify the Intelligent Services Gateway (ISG) traffic class whose policy you want to create or change or to specify the default traffic class in order to configure its policy, use the class type traffic command in service policy-map configuration mode. To remove a class from the service policy map, use the no form of this command.
[priority] class type traffic {class-map-name | default {in-out | input | output}}
no [priority] class type traffic {class-map-name | default {in-out | input | output}}
Syntax Description
Command Default
A traffic class is not specified.
Command Modes
Service policy-map configuration
Command History
Usage Guidelines
Before you can specify a named traffic class map in a service policy map, the traffic class map must be configured using the class-map type traffic command.
The priority of a traffic class determines which class will be used first for a specified match in cases where more than one traffic policy has been activated for a single session. In other words, if a packet matches more than one traffic class, it will be classified to the class with the higher priority. The priority should be specified if packets must match a traffic class based on the order of the service policy.
The default traffic class map is applied if none of the other configured classes matches the traffic. At least one other traffic class must be configured. The default traffic class map is not applied if there are no other traffic classes configured. It cannot be assigned a priority because by default it is the lowest priority class. The default policy of the default traffic class is to pass traffic. You can also configure the default traffic class to drop traffic.
Examples
The following example shows the configuration of the traffic class "UNAUTHORIZED_TRAFFIC":
class-map type traffic UNAUTHORIZED_TRAFFICmatch access-group input 100policy-map type service UNAUTHORIZED_REDIRECT_SVCclass type traffic UNAUTHORIZED_TRAFFICredirect to ip 10.0.0.148 port 8080The following example shows the configuration of the default traffic class:
policy-map type service SERVICE1class type traffic CLASS1prepaid-config PREPAIDclass type traffic default in-outdropRelated Commands
class-map type control
To create an Intelligent Services Gateway (ISG) control class map, which defines the conditions under which the actions of a control policy map will be executed, use the class-map type control command in global configuration mode. To remove a control class map, use the no form of this command.
class-map type control [match-all | match-any | match-none] class-map-name
no class-map type control [match-all | match-any | match-none] class-map-name
Syntax Description
Command Default
A control class map is not created.
Command Modes
Global configuration
Command History
Usage Guidelines
A control class map specifies conditions that must be met for a control policy to be activated, and, optionally, the event that causes the class to be evaluated. A control class map can contain multiple conditions, each of which will evaluate to either true or false. Use the match-any, match-all, and match-none keywords to specify which, if any, conditions must evaluate true before the control policy will be executed.
A control policy map, which is configured with the policy-map type control command, contains one or more control policy rules. A control policy rule associates a control class map with one or more actions. Use the class type control command to associate a control class map with a control policy map.
Examples
The following example shows how to configure a control policy in which virtual private dial-up network (VPDN) forwarding is applied to anyone dialing in from "xyz.com":
class-map type control match-all MY-FORWARDED-USERSmatch unauthenticated-domain "xyz.com"!policy-map type control MY-POLICYclass type control MY-FORWARDED-USERS event session-start1 apply identifier nas-port2 service local!interface Dialer1service-policy type control MY-POLICYRelated Commands
class-map type traffic
To create or modify a traffic class map, which is used for matching packets to a specified Intelligent Services Gateway (ISG) traffic class, use the class-map type traffic command in global configuration mode. To remove a traffic class map, use the no form of this command.
class-map type traffic match-any class-map-name
no class-map type traffic match-any class-map-name
Syntax Description
match-any
Indicates that packets must meet one of the match criteria in order to be considered a member of the class.
class-map-name
Name of the class map.
Command Default
A traffic class map is not created.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the class-map type traffic command to specify the name of the ISG traffic class for which you want to create or modify traffic class map match criteria. Use of the class-map type traffic command enables traffic class-map configuration mode, in which you can enter match commands to configure the match criteria for this class. Packets are checked against the match criteria configured for a class map to determine if the packet belongs to that traffic class.
ISG traffic classes allow subscriber session traffic to be subclassified so that ISG features can be applied to constituent flows. Traffic policies, which define the handling of data packets, contain a traffic class and one or more features.
Once a traffic class map has been defined, use the class type traffic command to associate the traffic class map with a service policy map. A service can contain one traffic class, and the default class.
Examples
The following example shows the configuration of a traffic class map called "CLASS-ACL-101". The class map is defined so that input traffic matching access list 101 will match the class. The traffic class map is then referenced in service policy map "mp3".
class-map type traffic CLASS-ACL-101match access-group input 101!policy-map type service mp3class type traffic CLASS-ACL-101authentication method-list cp-mlistaccounting method-list cp-mlistprepaid conf-prepaidRelated Commands
classname
To associate a Dynamic Host Configuration Protocol (DHCP) pool or remote DHCP server with an Intelligent Services Gateway (ISG) service policy map, use the classname command in service policy-map configuration mode. To remove this association, use the no form of this command.
classname class-name
no classname class-name
Syntax Description
Command Default
An ISG service is not associated with a DHCP pool.
Command Modes
Service policy-map configuration
Command History
Usage Guidelines
ISG can influence the IP address pool and the DHCP server that are used to assign subscriber IP addresses. To enable ISG to influence the IP addresses assigned to subscribers, you associate a DHCP address pool class with an address domain. The DHCP address pool class must also be configured in a service policy map, service profile, or user profile, which is associated with a subscriber. When a DHCP request is received from a subscriber, DHCP uses the address pool class that is associated with the subscriber to determine which DHCP address pool should be used to service the request. As a result, on a per-request basis, an IP address is provided by the local DHCP server or relayed to a remote DHCP server that is defined in the selected pool.
Examples
In the following example, the DHCP class "blue" is specified in the service "my_service". When "my_service" is activated, the local DHCP component will provide a new IP address from the pool "blue-pool" because (a) the classes match and (b) the subnet defined in "relay source" corresponds to one of the subnets defined at the interface. Hence the DHCP DISCOVER packet is relayed to the server at address 10.10.2.1, and the local DHCP component acts as a relay.
ip dhcp pool blue-poolrelay source 10.1.0.0 255.255.0.0class bluerelay destination 10.10.2.1 vrf bluepolicy-map type service my_serviceclassname blueRelated Commands
policy-map type service
Creates or modifies a service policy map, which is used to define an ISG service.
clear class-map control
To clear the Intelligent Services Gateway (ISG) control class map counters, use the clear class-map control command in privileged EXEC mode.
clear class-map control
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to clear the control class map counters:
Router# clear class-map controlRelated Commands
clear ip subscriber
To disconnect and remove all or specified Intelligent Services Gateway (ISG) IP subscriber sessions, use the clear ip subscriber command in privileged EXEC mode.
clear ip subscriber [interface interface-name | mac mac-address | slot slot-number no-hardware | [vrf vrf-name] [dangling seconds | ip ip-address | statistics]]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
A session that has not been fully established within a specified period of time is referred to as a dangling session. The clear ip subscriber command can be used with the dangling keyword to disconnect and remove dangling sessions. The seconds argument allows you to specify how long the session has to remain unestablished before it is considered dangling.
Session Removal: Cisco 7600 Series Routers Only
This command removes only IP sessions (MAC or IP), not IP interface sessions.
The interface and slot no-hardware keywords are available only on Cisco 7600 series routers.
Examples
The following example shows how to clear all dangling sessions that are associated with vrf1:
Router# clear ip subscriber vrf vrf1 dangling 10Examples for Cisco 7600 Series Routers Only
The following example shows how to clear sessions that are associated with Gigabit Ethernet interface 0/1 on a Cisco 7600 series router:
Router# clear ip subscriber interface GigabitEthernet 0/1The following example shows how to clear sessions that are associated with a line card that was removed from slot 1 on a Cisco 7600 series router:
Router# clear ip subscriber slot 1 no-hardwareRelated Commands
clear radius-proxy client
To clear all Intelligent Services Gateway (ISG) RADIUS proxy sessions for a specific client, use the clear radius-proxy client command in privileged EXEC mode.
clear radius-proxy client ip-address [vrf vrf-name]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example clears all sessions associated with the RADIUS proxy client that has the IP address 10.10.10.10 and associated is with the VRF "blue":
clear radius-proxy client 10.10.10.10 vrf blueRelated Commands
clear radius-proxy session
To clear specific Intelligent Services Gateway (ISG) RADIUS proxy sessions, use the clear radius-proxy session command in privileged EXEC mode.
clear radius-proxy session {id radius-proxy-ID | ip ip-address [vrf vrf-name]}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The RADIUS proxy session ID can be identified in the output of the show radius-proxy client command.
Examples
The following example shows how to identify the RADIUS proxy session ID by using the show radius-proxy client command:
show radius-proxy client 10.45.45.3Configuration details for client 10.45.45.3Shared secret: radprxykey Msg Auth Ignore: NoLocal auth port: 1111 Local acct port: 1646Acct method list: FWDACCTSession Summary:RP ID IP Address1. 1694498816 unassigned ----> 1694498816 is the session idThe following example clears the ISG RADIUS proxy session with the ID 1694498816:
clear radius-proxy session id 1694498816Related Commands
clear radius-proxy client
Clears all ISG RADIUS proxy sessions for a specific client.
show radius-proxy client
Displays information about ISG RADIUS proxy client devices.
clear subscriber policy dpm statistics
To clear the statistics for DHCP policy module (DPM) session contexts, use the clear subscriber policy dpm statistics command in privileged EXEC mode.
clear subscriber policy dpm statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The clear subscriber policy dpm statistics command resets all DPM event trace counters to zero. To display the cumulative statistics for DPM session contexts, use the show subscriber policy dpm statistics command.
Examples
The following example shows how to clear DPM event trace statistics:
Router# clear subscriber policy dpm statisticsRelated Commands
show subscriber policy dpm context
Displays event traces for DPM session contexts.
show subscriber policy dpm statistics
Displays statistics for DPM event traces.
clear subscriber policy peer
To clear the display of the details of a subscriber policy peer connection, use the clear subscriber policy peer command in privileged EXEC mode.
clear subscriber policy peer {address ip-address | handle connection-handle-id | session | all}
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.2(33)SRC
This command was introduced.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB
Usage Guidelines
The clear subscriber policy peer command ends the peering relationship between the Intelligent Services Gateway (ISG) device and selected Service Control Engine (SCE) devices. However, the SCE will attempt to reconnect with the ISG device after a configured amount of time. The clear subscriber policy peer command can remove select session associations from a particular SCE device.
Examples
The following example shows how the clear subscriber policy peer command is used at the router prompt to clear the display of all details of the subscriber policy peer connection.
Router# clear subscriber policy peer allRelated Commands
show subscriber-policy peer
Displays the details of a subscriber policy peer.
subscriber-policy
Defines or modifies the forward and filter decisions of the subscriber policy.
clear subscriber policy peer session
To clear the display of the details of a subscriber policy peer session, use the clear subscriber policy peer session command in privileged EXEC mode.
clear subscriber policy peer session {guid guid-value | all} [address ip-address | handle connection-handle-id | all]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.2(33)SRC
This command was introduced.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB.
Usage Guidelines
The clear subscriber policy peer session command ends the peering relationship between the Intelligent Services Gateway (ISG) device and selected Service Control Engine (SCE) devices. However, the SCE will attempt to reconnect with the ISG device after a configured amount of time. The clear subscriber policy peer session command can remove select session associations from a particular SCE.
Examples
The following example shows how the clear subscriber policy peer session command is used at the router prompt to clear the display of all the details of a subscriber policy peer session.
Router# clear subscriber policy peer session allRelated Commands
clear subscriber trace history
To clear the event trace history logs for Intelligent Services Gateway (ISG) subscriber sessions, use the clear subscriber trace history command in privileged EXEC mode.
clear subscriber trace history {dpm | pm}
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The clear subscriber trace history command deletes all event traces that are stored in the specified module's history log. This command also clears the current records counter and current log size counter for the show subscriber trace statistics command.
Examples
The following example shows how to clear the trace history for the DPM.
Router# clear subscriber trace history dpmRelated Commands
client
To specify a RADIUS client from which a device will accept Change of Authorization (CoA) and disconnect requests, use the client command in dynamic authorization local server configuration mode. To remove this specification, use the no form of this command.
client {name | ip-address} [key [0 | 7] word] [vrf vrf-id]
no client {name | ip-address} [key [0 | 7 ] word] [vrf vrf-id]
Syntax Description
Command Default
CoA and disconnect requests are dropped.
Command Modes
Dynamic authorization local server configuration
Command History
12.2(28)SB
This command was introduced.
Cisco IOS XE Release 2.6
This command was integrated into Cisco IOS XE Release 2.6.
Usage Guidelines
A device (such as a router) can be configured to allow an external policy server to dynamically send updates to the router. This functionality is facilitated by the CoA RADIUS extension. CoA introduced peer-to-peer capability to RADIUS, enabling a router and external policy server each to act as a RADIUS client and server. Use the client command to specify the RADIUS clients for which the router will act as server.
Examples
The following example configures the router to accept requests from the RADIUS client at IP address 10.0.0.1:
aaa server radius dynamic-authorclient 10.0.0.1 key ciscoRelated Commands
aaa server radius dynamic-author
Configures an ISG as a AAA server to facilitate interaction with an external policy server.
client (ISG RADIUS proxy)
To enter RADIUS proxy client configuration mode, in which client-specific RADIUS proxy parameters can be specified, use the client command in RADIUS proxy server configuration mode. To remove the RADIUS proxy client and configuration, use the no form of this command.
client {ip-address | hostname} [subnet-mask] [vrf vrf-name]
no client {ip-address | hostname} [subnet-mask] [vrf vrf-name]
Syntax Description
Command Default
The global RADIUS proxy server configuration is used.
Command Modes
RADIUS proxy server configuration
Command History
Usage Guidelines
Use the client command in RADIUS proxy server configuration mode to specify a client for which RADIUS proxy parameters can be configured. Client-specific RADIUS proxy configurations take precedence over the global RADIUS proxy server configuration.
In cases where Intelligent Services Gateway (ISG) is acting as a proxy for more than one client device, all of which reside on the same subnet, client-specific parameters may be configured using a subnet definition rather than a discrete IP address for each device. This configuration method results in the sharing of a single configuration by all the client devices on the subnet. ISG is able to differentiate traffic from these devices based on the source and NAS IP address of RADIUS packets. To configure a client subnet, use the client command with the subnet-mask argument.
Examples
The following example shows the configuration of global RADIUS proxy parameters and client-specific parameters for two RADIUS proxy clients. Client 10.1.1.1 is configured to listen for accounting packets on port 1813 and authentication packets on port 1812. Because a shared secret is not configured specifically for client 10.1.1.1, it will inherit the shared secret specification, which is "cisco", from the global RADIUS proxy configuration. Client 10.2.2.2 will use "systems" as the shared secret and will use the default ports for listening for accounting and authentication packets.
aaa server radius proxykey ciscoclient 10.1.1.1accounting port 1813authentication port 1812!client 10.2.2.2key systems!Related Commands
aaa server radius proxy
Enables ISG RADIUS proxy configuration mode, in which ISG RADIUS proxy parameters can be configured.
collect identifier
To enable a control policy map to collect subscriber identifiers, use the collect identifier command in control policy-map class configuration mode. To disable a control policy from collecting subscriber identifiers, use the no form of this command.
action-number collect [aaa list list-name] identifier {authen-status | authenticated-domain | authenticated-username | dnis | mac-address | media | mlp-negotiated | nas-port | no-username | protocol | service-name | source-ip-address | timer | tunnel-name | unauthenticated-domain | unauthenticated-username}
no action-number collect [aaa list list-name] identifier {authen-status | authenticated-domain | authenticated-username | dnis | media | mlp-negotiated | nas-port | no-username | protocol | service-name | source-ip-address | timer | tunnel-name | unauthenticated-domain | unauthenticated-username}
Syntax Description
Command Default
Control policies do not collect subscriber identifiers.
Command Modes
Control policy-map class configuration (config-control-policymap-class-control)
Command History
Usage Guidelines
The collect identifier command configures an action in a control policy map.
Control policies define the actions the system will take in response to specified events and conditions. A control policy map is used to configure an Intelligent Services Gateway (ISG) control policy. A control policy is made of one or more control policy rules. A control policy rule is an association of a control class and one or more actions. The control class defines the conditions that must be met before the actions will be executed. The actions are numbered and executed sequentially within the policy rule.
Note that if you specify the default method list, the default list will not appear in the output of the show running-config command. For example, if you configure the following command:
Router(config-control-policymap-class-control)# 1 collect aaa list defaultThe following will display in the output for the show running-config command:
1 collectNamed method lists will display in the show running-config command output.
Examples
The following example shows how to configure ISG to collect a subscriber's authentication status at session start:
Router(config)# policy-map type control policy1Router(config-control-policymap)# class type control always event session-startRouter(config-control-policymap-class-control)# 1 collect identifier authen-statusRelated Commands
debug ip subscriber
To enable Intelligent Services Gateway (ISG) IP subscriber session debugging, use the debug ip subscriber command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ip subscriber {all | error | event | fsm | packet}
no debug ip subscriber {all | error | event | fsm | packet}
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example show sample output for the debug ip subscriber command:
Router# debug ip subscriber packetPacket debugs:1d07h: IPSUB_DP: [Et0/0:I:CEF:0000.0000.0002] Rx driver forwarded packet via les, return code = 01d07h: IPSUB_DP: [Et0/0:I:PROC:0000.0000.0002] Packet classified, results = 0x181d07h: IPSUB_DP: [ms1:I:PROC:0000.0000.0002] Rx driver forwarded the packet1d07h: IPSUB_DP: [ms1:I:PROC:0000.0000.0002] Packet classified, results = 0x421d07h: IPSUB_DP: [ms1:O:PROC:RED:50.0.0.3] Packet classified, results = 0x14Router#1d07h: IPSUB_DP: [ms1:O:PROC:RED:50.0.0.3] Subscriber features executed, return code = 01d07h: IPSUB_DP: [ms1:O:PROC:RED:50.0.0.3] Tx driver forwarding the packet1d07h: IPSUB_DP: [Et0/0:O:PROC:RED:50.0.0.3] Packet classified, results = 0x14Related Commands
debug radius-proxy
To display debugging messages for Intelligent Services Gateway (ISG) RADIUS proxy functionality, use the debug radius-proxy command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug radius-proxy {events | errors}
no debug radius-proxy {events | errors}
Syntax Description
events
Displays debug messages related to ISG RADIUS proxy events.
errors
Displays debug messages related to ISG RADIUS proxy errors.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
See the following caution before using debug commands.
Caution
Examples
The following example shows output for the debug radius-proxy command with the events keyword:
Router# debug radius-proxy events*Nov 7 07:53:11.411: RP-EVENT: Parse Request: Username = 12345679@cisco*Nov 7 07:53:11.411: RP-EVENT: Parse Request: Caller ID = 12345679@cisco*Nov 7 07:53:11.411: RP-EVENT: Parse Request: NAS id = localhost*Nov 7 07:53:11.411: RP-EVENT: Found matching context for user Caller ID:12345679@cisco Name:aa*Nov 7 07:53:11.411: RP-EVENT: Received event client Access-Request in state activated*Nov 7 07:53:11.411: RP-EVENT: User Caller ID:12345679@cisco Name:12 re-authenticating*Nov 7 07:53:11.411: RP-EVENT: Forwarding Request to method list (handle=1979711512)*Nov 7 07:53:11.411: RP-EVENT: Sending request to server group EAP*Nov 7 07:53:11.411: RP-EVENT: State changed activated --> wait for Access-Responsedebug sgi
To debug Service Gateway Interface (SGI), use the debug sgi command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug sgi [error | info | xml | gsi | isg-api | all]
no debug sgi
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The xml keyword turns on debugging for the Cisco Networking Services (CNS) XML parser and provides additional XML parsing debugging for SGI.
Examples
The following example shows all debugging options enabled and shows the output that is received when a message is sent.
Router# debug sgi allRouter# show debug SGI:SGI All debugging is onSGI Errors debugging is onSGI XML debugging is onSGI Informational debugging is onSGI Generic Service Interface debugging is onSGI ISG_API Events debugging is onSGI ISG_API Errors debugging is onRouter#Router#*Jul 1 20:55:11.364: SGI: Session created, session Id 7*Jul 1 20:55:11.372: sgi beep listen app beep[0x66245188]: frame_available: type=M number=1 answer=-1 more=* size=1400*Jul 1 20:55:11.372: sgi beep listen app beep[0x66245188]: Content-Type: application/xml<?xml version="1.0" encoding="UTF-8"?>...*Jul 1 20:55:11.372: sgi beep listen app beep[0x66245188]: frame_available: type=M number=1 answer=-1 more=. size=111*Jul 1 20:55:11.372: sgi beep listen app beep[0x66245188]: gitypes:policyGroup></objects></sgiops:insertPolicyObjectsRequest>...*Jul 1 20:55:11.372: SGI: GSI message received, msgid 1, session 7*Jul 1 20:55:11.376: SGI: XML parsed successfully, request insertPolicyObjectsRequest, msgid 1*Jul 1 20:55:11.376: SGI: authentication request sent to AAA*Jul 1 20:55:11.376: SGI: req = [0x67454088] authentication succeeded*Jul 1 20:55:11.376: SGI: Processing insertPolicyObjectsRequest*Jul 1 20:55:11.376: SGI: insertPolicyObjectsRequest processing policyGroup:VPDN1, type 1, result: 0*Jul 1 20:55:11.376: SGI: Processing insertPolicyObjectsResponse*Jul 1 20:55:11.376: SGI: GSI message sent, msgid 1, session 7*Jul 1 20:55:12.088: sgi beep listen app beep[0x66245188]: close confirmation: status=+ no error origin=L scope=C*Jul 1 20:55:12.088: SGI: Session terminating, session Id 7Router#Related Commands
debug ssm
To display diagnostic information about the Segment Switching Manager (SSM) for switched Layer 2 segments, use the debug ssm command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ssm {cm errors | cm events | fhm errors | fhm events | sm errors | sm events | sm counters | xdr}
no debug ssm {cm errors | cm events | fhm errors | fhm events | sm errors | sm events | sm counters | xdr}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The SSM manages the data-plane component of the Layer 2 Virtual Private Network (L2VPN) configuration. The CM tracks the connection-level errors and events that occur on an xconnect. The SM tracks the per-segment events and errors on the xconnect.
Use the debug ssm command to troubleshoot problems in bringing up the data plane.
This command is generally used only by Cisco engineers for internal debugging of SSM processes.
Examples
The following example shows sample output for the debug ssm xdr command:
Router# debug ssm xdrSSM xdr debugging is on2w5d: SSM XDR: [4096] deallocate segment, len 162w5d: SSM XDR: [8193] deallocate segment, len 162w5d: %LINK-3-UPDOWN: Interface FastEthernet2/1, changed state to down2w5d: %LINK-3-UPDOWN: Interface FastEthernet2/1, changed state to up2w5d: SSM XDR: [4102] provision segment, switch 4101, len 1062w5d: SSM XDR: [4102] update segment status, len 172w5d: SSM XDR: [8199] provision segment, switch 4101, len 2062w5d: SSM XDR: [4102] update segment status, len 172w5d: %SYS-5-CONFIG_I: Configured from console by console2w5d: %LINK-3-UPDOWN: Interface FastEthernet2/1, changed state to down2w5d: SSM XDR: [4102] update segment status, len 172w5d: %LINK-3-UPDOWN: Interface FastEthernet2/1, changed state to up2w5d: SSM XDR: [4102] deallocate segment, len 162w5d: SSM XDR: [8199] deallocate segment, len 162w5d: SSM XDR: [4104] provision segment, switch 4102, len 1062w5d: SSM XDR: [4104] update segment status, len 172w5d: SSM XDR: [8201] provision segment, switch 4102, len 2062w5d: SSM XDR: [4104] update segment status, len 172w5d: SSM XDR: [4104] update segment status, len 172w5d: %SYS-5-CONFIG_I: Configured from console by consoleThe following example shows the events that occur on the segment manager when an Any Transport over MPLS (AToM) virtual circuit (VC) configured for Ethernet over MPLS is shut down and then enabled:
Router# debug ssm sm eventsSSM Connection Manager events debugging is onRouter(config)# interface fastethernet 0/1/0.1Router(config-subif)# shutdown09:13:38.159: SSM SM: [SSS:AToM:36928] event Unprovison segment09:13:38.159: SSM SM: [SSS:Ethernet Vlan:4146] event Unbind segment09:13:38.159: SSM SM: [SSS:AToM:36928] free segment class09:13:38.159: SSM SM: [SSS:AToM:36928] free segment09:13:38.159: SSM SM: [SSS:AToM:36928] event Free segment09:13:38.159: SSM SM: last segment class freed09:13:38.159: SSM SM: [SSS:Ethernet Vlan:4146] segment ready09:13:38.159: SSM SM: [SSS:Ethernet Vlan:4146] event Found segment dataRouter(config-subif)# no shutdown09:13:45.815: SSM SM: [SSS:AToM:36929] event Provison segment09:13:45.815: label_oce_get_label_bundle: flags 14 label 1609:13:45.815: SSM SM: [SSS:AToM:36929] segment ready09:13:45.815: SSM SM: [SSS:AToM:36929] event Found segment data09:13:45.815: SSM SM: [SSS:AToM:36929] event Bind segment09:13:45.815: SSM SM: [SSS:Ethernet Vlan:4146] event Bind segmentThe following example shows the events that occur on the CM when an AToM VC configured for Ethernet over MPLS is shut down and then enabled:
Router(config)# interface fastethernet 0/1/0.1Router(config-subif)# shutdown09:17:20.179: SSM CM: [AToM] unprovision segment, id 3692909:17:20.179: SSM CM: CM FSM: state Open - event Free segment09:17:20.179: SSM CM: [SSS:AToM:36929] unprovision segment 109:17:20.179: SSM CM: [SSS:AToM] shQ request send unprovision complete event09:17:20.179: SSM CM: [SSS:Ethernet Vlan:4146] unbind segment 209:17:20.179: SSM CM: [SSS:Ethernet Vlan] shQ request send ready event09:17:20.179: SSM CM: SM msg event send unprovision complete event09:17:20.179: SSM CM: SM msg event send ready eventRouter(config-subif)# no shutdown09:17:35.879: SSM CM: Query AToM to Ethernet Vlan switching, enabled09:17:35.879: SSM CM: [AToM] provision second segment, id 3693009:17:35.879: SSM CM: CM FSM: state Down - event Provision segment09:17:35.879: SSM CM: [SSS:AToM:36930] provision segment 209:17:35.879: SSM CM: [AToM] send client event 6, id 3693009:17:35.879: SSM CM: [SSS:AToM] shQ request send ready event09:17:35.883: SSM CM: SM msg event send ready event09:17:35.883: SSM CM: [AToM] send client event 3, id 36930The following example shows the events that occur on the CM and SM when an AToM VC is provisioned and then unprovisioned:
Router# debug ssm cm eventsSSM Connection Manager events debugging is onRouter# debug ssm sm eventsSSM Segment Manager events debugging is onRouter# configure terminalRouter(config)# interface ethernet1/0Router(config-if)# xconnect 10.55.55.2 101 pw-class mpls16:57:34: SSM CM: provision switch event, switch id 8604016:57:34: SSM CM: [Ethernet] provision first segment, id 1231316:57:34: SSM CM: CM FSM: state Idle - event Provision segment16:57:34: SSM CM: [SSS:Ethernet:12313] provision segment 116:57:34: SSM SM: [SSS:Ethernet:12313] event Provison segment16:57:34: SSM CM: [SSS:Ethernet] shQ request send ready event16:57:34: SSM CM: SM msg event send ready event16:57:34: SSM SM: [SSS:Ethernet:12313] segment ready16:57:34: SSM SM: [SSS:Ethernet:12313] event Found segment data16:57:34: SSM CM: Query AToM to Ethernet switching, enabled16:57:34: SSM CM: [AToM] provision second segment, id 1641016:57:34: SSM CM: CM FSM: state Down - event Provision segment16:57:34: SSM CM: [SSS:AToM:16410] provision segment 216:57:34: SSM SM: [SSS:AToM:16410] event Provison segment16:57:34: SSM CM: [AToM] send client event 6, id 1641016:57:34: label_oce_get_label_bundle: flags 14 label 1916:57:34: SSM CM: [SSS:AToM] shQ request send ready event16:57:34: SSM CM: SM msg event send ready event16:57:34: SSM SM: [SSS:AToM:16410] segment ready16:57:34: SSM SM: [SSS:AToM:16410] event Found segment data16:57:34: SSM SM: [SSS:AToM:16410] event Bind segment16:57:34: SSM SM: [SSS:Ethernet:12313] event Bind segment16:57:34: SSM CM: [AToM] send client event 3, id 16410Router# configure terminalRouter(config)# interface e1/0Router(config-if)# no xconnect16:57:26: SSM CM: [Ethernet] unprovision segment, id 1638716:57:26: SSM CM: CM FSM: state Open - event Free segment16:57:26: SSM CM: [SSS:Ethernet:16387] unprovision segment 116:57:26: SSM SM: [SSS:Ethernet:16387] event Unprovison segment16:57:26: SSM CM: [SSS:Ethernet] shQ request send unprovision complete event16:57:26: SSM CM: [SSS:AToM:86036] unbind segment 216:57:26: SSM SM: [SSS:AToM:86036] event Unbind segment16:57:26: SSM CM: SM msg event send unprovision complete event16:57:26: SSM SM: [SSS:Ethernet:16387] free segment class16:57:26: SSM SM: [SSS:Ethernet:16387] free segment16:57:26: SSM SM: [SSS:Ethernet:16387] event Free segment16:57:26: SSM SM: last segment class freed16:57:26: SSM CM: unprovision switch event, switch id 1229016:57:26: SSM CM: [SSS:AToM] shQ request send unready event16:57:26: SSM CM: SM msg event send unready event16:57:26: SSM SM: [SSS:AToM:86036] event Unbind segment16:57:26: SSM CM: [AToM] unprovision segment, id 8603616:57:26: SSM CM: CM FSM: state Down - event Free segment16:57:26: SSM CM: [SSS:AToM:86036] unprovision segment 216:57:26: SSM SM: [SSS:AToM:86036] event Unprovison segment16:57:26: SSM CM: [SSS:AToM] shQ request send unprovision complete event16:57:26: SSM CM: SM msg event send unprovision complete event16:57:26: SSM SM: [SSS:AToM:86036] free segment class16:57:26: SSM SM: [SSS:AToM:86036] free segment16:57:26: SSM SM: [SSS:AToM:86036] event Free segment16:57:26: SSM SM: last segment class freedRelated Commands
debug subscriber aaa authorization
To display diagnostic information about authentication, authorization, and accounting (AAA) authorization of Intelligent Services Gateway (ISG) subscriber sessions, use the debug subscriber aaa authorization command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug subscriber aaa authorization {event | fsm}
no debug sss aaa authorization {event | fsm}
Syntax Description
event
Display information about AAA authorization events that occur during ISG session establishment.
fsm
Display information about AAA authorization state changes for ISG subscriber sessions.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output of several debug subscriber commands, including the debug subscriber aaa authorization command. The reports from these commands should be sent to technical personnel at Cisco Systems for evaluation.
Router# debug subscriber eventRouter# debug subscriber errorRouter# debug subscriber stateRouter# debug subscriber aaa authorization eventRouter# debug subscriber aaa authorization fsmSSS:SSS events debugging is onSSS error debugging is onSSS fsm debugging is onSSS AAA authorization event debugging is onSSS AAA authorization FSM debugging is on*Mar 4 21:33:18.248: SSS INFO: Element type is Access-Type, long value is 3*Mar 4 21:33:18.248: SSS INFO: Element type is Switch-Id, long value is -1509949436*Mar 4 21:33:18.248: SSS INFO: Element type is Nasport, ptr value is 6396882C*Mar 4 21:33:18.248: SSS INFO: Element type is AAA-Id, long value is 7*Mar 4 21:33:18.248: SSS INFO: Element type is AAA-ACCT_ENBL, long value is 1*Mar 4 21:33:18.248: SSS INFO: Element type is AccIe-Hdl, ptr value is 78000006*Mar 4 21:33:18.248: SSS MGR [uid:7]: Event service-request, state changed from wait-for-req to wait-for-auth*Mar 4 21:33:18.248: SSS MGR [uid:7]: Handling Policy Authorize (1 pending sessions)*Mar 4 21:33:18.248: SSS PM [uid:7]: Need the following key: Unauth-User*Mar 4 21:33:18.248: SSS PM [uid:7]: Received Service Request*Mar 4 21:33:18.248: SSS PM [uid:7]: Event <need keys>, State: initial-req to need-init-keys*Mar 4 21:33:18.248: SSS PM [uid:7]: Policy reply - Need more keys*Mar 4 21:33:18.248: SSS MGR [uid:7]: Got reply Need-More-Keys from PM*Mar 4 21:33:18.248: SSS MGR [uid:7]: Event policy-or-mgr-more-keys, state changed from wait-for-auth to wait-for-req*Mar 4 21:33:18.248: SSS MGR [uid:7]: Handling More-Keys event*Mar 4 21:33:20.256: SSS INFO: Element type is Unauth-User, string value is nobody2@xyz.com*Mar 4 21:33:20.256: SSS INFO: Element type is AccIe-Hdl, ptr value is 78000006*Mar 4 21:33:20.256: SSS INFO: Element type is AAA-Id, long value is 7*Mar 4 21:33:20.256: SSS INFO: Element type is Access-Type, long value is 0*Mar 4 21:33:20.256: SSS MGR [uid:7]: Event service-request, state changed from wait-for-req to wait-for-auth*Mar 4 21:33:20.256: SSS MGR [uid:7]: Handling Policy Authorize (1 pending sessions)*Mar 4 21:33:20.256: SSS PM [uid:7]: Received More Initial Keys*Mar 4 21:33:20.256: SSS PM [uid:7]: Event <rcvd keys>, State: need-init-keys to check-auth-needed*Mar 4 21:33:20.256: SSS PM [uid:7]: Handling Authorization Check*Mar 4 21:33:20.256: SSS PM [uid:7]: Event <send auth>, State: check-auth-needed to authorizing*Mar 4 21:33:20.256: SSS PM [uid:7]: Handling AAA service Authorization*Mar 4 21:33:20.256: SSS PM [uid:7]: Sending authorization request for 'xyz.com'*Mar 4 21:33:20.256: SSS AAA AUTHOR [uid:7]:Event <make request>, state changed from idle to authorizing*Mar 4 21:33:20.256: SSS AAA AUTHOR [uid:7]:Authorizing key xyz.com*Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:AAA request sent for key xyz.com*Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:Received an AAA pass*Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:Event <found service>, state changed from authorizing to complete*Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:Found service info for key xyz.com*Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:Event <free request>, state changed from complete to terminal*Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:Free request*Mar 4 21:33:20.264: SSS PM [uid:7]: Event <found>, State: authorizing to end*Mar 4 21:33:20.264: SSS PM [uid:7]: Handling Service Direction*Mar 4 21:33:20.264: SSS PM [uid:7]: Policy reply - Forwarding*Mar 4 21:33:20.264: SSS MGR [uid:7]: Got reply Forwarding from PM*Mar 4 21:33:20.264: SSS MGR [uid:7]: Event policy-start-service-fsp, state changed from wait-for-auth to wait-for-service*Mar 4 21:33:20.264: SSS MGR [uid:7]: Handling Connect-Forwarding-Service event*Mar 4 21:33:20.272: SSS MGR [uid:7]: Event service-fsp-connected, state changed from wait-for-service to connected*Mar 4 21:33:20.272: SSS MGR [uid:7]: Handling Forwarding-Service-Connected eventRelated Commands
debug subscriber error
To display diagnostic information about errors that may occur during Intelligent Services Gateway (ISG) subscriber session setup, use the debug subscriber error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug subscriber error
no debug subscriber error
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following sample output for the debug subscriber error command indicates that the session is stale since the session handle has already been destroyed.
Router# debug subscriber error*Sep 20 22:39:49.455: SSS MGR: Session handle [EF000002] destroyed alreadyRelated Commands
debug subscriber event
To display diagnostic information about Intelligent Services Gateway (ISG) subscriber session setup events, use the debug subscriber event command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug subscriber event
no debug subscriber event
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following sample output for the debug subscriber event commands indicates that the system has determined that the session should be locally terminated. The local termination module determines that an interface description block (IDB) is not required for this session, and it sets up the data plane for packet switching.
Router# debug subscriber event*Sep 20 22:21:08.223: SSS MGR [uid:2]: Handling Connect Local Service action*Sep 20 22:21:08.223: SSS LTERM [uid:2]: Processing Local termination request*Sep 20 22:21:08.223: SSS LTERM [uid:2]: L3 session - IDB not required for setting up service*Sep 20 22:21:08.223: SSS LTERM [uid:2]: Interface already present or not required for service*Sep 20 22:21:08.223: SSS LTERM [uid:2]: Segment provision successfulRelated Commands
debug subscriber feature
To display diagnostic information about the installation and removal of Intelligent Services Gateway (ISG) features on ISG subscriber sessions, use the debug subscriber feature command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug subscriber feature {all | detail | error | event | name name-of-feature {detail | error | event | packet} | packet [detail | full] [issu {event | error}] [ccm {event | error}]}
no debug subscriber feature {all | detail | error | event | name name-of-feature {detail | error | event | packet} | packet [detail | full] [issu {event | error}] [ccm {event | error}]}
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(28)SB
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS Release12.2(33)SRC.
Examples
The following sample output for the debug subscriber feature command indicates that the idle timeout feature has been successfully installed on the inbound segment.
Router# debug subscriber feature event*Sep 20 22:28:57.903: SSF[myservice/uid:6/Idle Timeout]: Group feature install*Sep 20 22:28:57.903: SSF[uid:6/Idle Timeout]: Adding feature to inbound segment(s)debug subscriber fsm
To display diagnostic information about Intelligent Services Gateway (ISG) subscriber session state change, use the debug subscriber fsm command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug subscriber fsm
no debug subscriber fsm
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following sample output for the debug subscriber fsm command indicates that the session has been disconnected by the client, and the system is cleaning up the session by disconnecting the network service and removing any installed features.
Router# debug subscriber fsm*Sep 20 22:35:10.495: SSS MGR [uid:5]: Event client-disconnect, state changed from connected to disconnecting-fsp-featdebug subscriber packet
To display information about packets as they traverse the subscriber service switch (SSS) path, use the debug subscriber packet command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug subscriber packet {detail | error | event | full}
no debug subscriber packet {detail | error | event | full}
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example show sample output for the debug subscriber packet command with the full keyword. This output is for a PPPoE session configured with forwarding.
SSS Switch: Pak encap size, old: 60, new: 24SSS Switch: Pak 0285C458 sz 66 encap 14*Feb 9 15:47:13.659: 000000 AA BB CC 00 0B 01 AA BB D.......*Feb 9 15:47:13.659: 000008 CC 00 0C 01 08 00 45 00 ......N.*Feb 9 15:47:13.659: 000010 00 34 00 28 00 00 FE 11 .4.(....*Feb 9 15:47:13.659: 000018 F2 9D AC 12 B8 E7 AC 12 ........*Feb 9 15:47:13.659: 000020 B8 E6 06 A5 06 A5 00 20 .......*Feb 9 15:47:13.659: 000028 00 00 C0 01 02 00 00 02 ........*Feb 9 15:47:13.659: 000030 00 01 00 18 00 00 FC A7 ........*Feb 9 15:47:13.659: 000038 2E B3 FF 03 C2 23 03 01 .....#..*Feb 9 15:47:13.659: 000040 00 04 ..SSS Switch: Pak encap size, old: 60, new: 24SSS Switch: Pak 0285C458 sz 72 encap 14*Feb 9 15:47:13.691: 000000 AA BB CC 00 0B 01 AA BB D.......*Feb 9 15:47:13.691: 000008 CC 00 0C 01 08 00 45 00 ......N.*Feb 9 15:47:13.691: 000010 00 3A 00 2A 00 00 FE 11 .:.*....*Feb 9 15:47:13.691: 000018 F2 95 AC 12 B8 E7 AC 12 ........*Feb 9 15:47:13.691: 000020 B8 E6 06 A5 06 A5 00 26 .......&*Feb 9 15:47:13.691: 000028 00 00 C0 01 02 00 00 02 ........*Feb 9 15:47:13.691: 000030 00 01 00 1E 00 00 FC A7 ........*Feb 9 15:47:13.691: 000038 2E B3 FF 03 80 21 01 01 .....!..*Feb 9 15:47:13.691: 000040 00 0A 03 06 3A 3A 3A 3A ....::::SSS Switch: Pak encap size, old: 24, new: 46SSS Switch: Pak 027A5BE8 sz 36 encap 18*Feb 9 15:47:13.691: 000000 AA BB CC 00 0B 00 AA BB D.......*Feb 9 15:47:13.691: 000008 CC 00 0A 00 81 00 01 41 .......a*Feb 9 15:47:13.691: 000010 88 64 11 00 00 01 00 0C .dN.....*Feb 9 15:47:13.691: 000018 80 21 01 01 00 0A 03 06 .!......*Feb 9 15:47:13.691: 000020 00 00 00 00 ....SSS Switch: Pak encap size, old: 60, new: 24SSS Switch: Pak 0285C458 sz 72 encap 14*Feb 9 15:47:13.691: 000000 AA BB CC 00 0B 01 AA BB D.......*Feb 9 15:47:13.691: 000008 CC 00 0C 01 08 00 45 00 ......N.*Feb 9 15:47:13.691: 000010 00 3A 00 2C 00 00 FE 11 .:.,....*Feb 9 15:47:13.691: 000018 F2 93 AC 12 B8 E7 AC 12 ........*Feb 9 15:47:13.691: 000020 B8 E6 06 A5 06 A5 00 26 .......&*Feb 9 15:47:13.691: 000028 00 00 C0 01 02 00 00 02 ........*Feb 9 15:47:13.691: 000030 00 01 00 1E 00 00 FC A7 ........*Feb 9 15:47:13.691: 000038 2E B3 FF 03 80 21 03 01 .....!..*Feb 9 15:47:13.691: 000040 00 0A 03 06 09 00 00 1F ........Related Commands
debug subscriber feature
Displays diagnostic information about the installation and removal of ISG features on subscriber sessions.
debug subscriber policy
To display diagnostic information about policy execution related to Intelligent Services Gateway (ISG) subscriber sessions, use the debug subscriber policy command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug subscriber policy {all | detail | error | event | fsm | prepaid | {condition | idmgr | profile | push | rule | service} [detail | error | event] | dpm [error | event] | webportal {detail | error | event}}
no debug subscriber policy {all | detail | error | event | fsm | prepaid | {condition | idmgr | profile | push | rule | service} [detail | error | event] | dpm [error | event] | webportal {detail | error | event}}
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example shows sample output for the debug subscriber policy command with the events keyword. This output indicates the creation of a new session. "Updated key list" indicates important attributes and information associated with the session.
*Feb 7 18:58:24.519: SSS PM [0413FC58]: Create context 0413FC58*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Authen status update; is now "unauthen"*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Updated NAS port for AAA ID 14*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Updated key list:*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Access-Type = 15 (IP)*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Protocol-Type = 4 (IP)*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Media-Type = 2 (IP)*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: IP-Address = 10.0.0.2 (0A000002)*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: IP-Address-VRF = IP 10.0.0.2:0*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: source-ip-address = 037FBB78*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Mac-Address = aabb.cc00.6500*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Final = 1 (YES)*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Authen-Status = 1 (Unauthenticated)*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Nasport = PPPoEoE: slot 0 adapter 0 port 0*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Updated key list:*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Access-Type = 15 (IP)*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Protocol-Type = 4 (IP)*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Media-Type = 2 (IP)*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: IP-Address = 10.0.0.2 (0A000002)*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: IP-Address-VRF = IP 10.0.0.2:0*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: source-ip-address = 037FBB78*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Mac-Address = aabb.cc00.6500*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Final = 1 (YES)*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Authen-Status = 1 (Unauthenticated)*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Nasport = PPPoEoE: slot 0 adapter 0 port 0*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Session-Handle = 486539268 (1D000004)*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: SM Policy invoke - Service Selection Request*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Access type IP*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Access type IP: final key*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Received Service Request*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Handling Authorization Check*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: SIP [IP] can NOT provide more keys*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: SIP [IP] can NOT provide more keys*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Handling Default Service*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Providing Service*Feb 7 18:58:24.519: SSS PM [uid:4][0413FC58]: Policy reply - Local Terminate*Feb 7 18:58:24.523: SSS PM [uid:4][0413FC58]: SM Policy invoke - Apply Config Success*Feb 7 18:58:24.523: SSS PM [uid:4][0413FC58]: Handling Apply Config; SUCCESSdebug subscriber policy dpm timestamps
To include timestamp information for DHCP policy module (DPM) messages in debugging output, use the debug subscriber policy dpm timestamps command in privileged EXEC mode. To remove timestamp information from output, use the no form of this command.
debug subscriber policy dpm timestamps
no debug subscriber policy dpm timestamps
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The debug subscriber policy dpm timestamps command enables the timestamp information for the latest DPM message that was received to be saved after a session is established. The timestamp for DPM messages is displayed in debugging output, including output from the show subscriber policy dpm context command.
Timestamp information is removed by default after a session is established. Enabling this command preserves the timestamp information so that it can be included in debugging output. This command does not display any debugging output; it enables timestamp output for other debug and show commands.
Examples
The following example shows how to include timestamp information in debug output:
Router# debug subscriber policy dpm timestampsSG dhcp message timestamps debugging is onRelated Commands
show subscriber policy dpm context
Displays event traces for DPM session contexts.
debug subscriber service
To display diagnostic information about the service profile database in an Intelligent Services Gateway (ISG), use the debug subscriber service command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug subscriber service
no debug subscriber service
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug subscriber service command to diagnose problems with service profiles or service policy maps.
Examples
The following example shows sample output for the debug subscriber service command. This output indicates that a service logon has occurred for the service "prep_service".
*Feb 7 18:52:31.067: SVM [prep_service]: needs downloading *Feb 7 18:52:31.067: SVM [D6000000/prep_service]: allocated version 1 *Feb 7 18:52:31.067: SVM [D6000000/prep_service]: [8A000002]: client queued *Feb 7 18:52:31.067: SVM [D6000000/prep_service]: [PM-Download:8A000002] locked 0->1 *Feb 7 18:52:31.067: SVM [D6000000/prep_service]: [AAA-Download:040DD9D0] locked 0->1 *Feb 7 18:52:31.127: SVM [D6000000/prep_service]: TC feature info found *Feb 7 18:52:31.127: SVM [D0000001/prep_service]: added child *Feb 7 18:52:31.127: SVM [D6000000/prep_service]: [TC-Child:040DD130] locked 0->1 *Feb 7 18:52:31.127: SVM [D0000001/CHILD/prep_service]: [TC-Parent:040DD1A8] locked 0->1 *Feb 7 18:52:31.127: SVM [D6000000/prep_service]: TC flow feature info not found *Feb 7 18:52:31.127: SVM [D6000000/prep_service]: downloaded first version *Feb 7 18:52:31.127: SVM [D6000000/prep_service]: [8A000002]: client download ok *Feb 7 18:52:31.127: SVM [D6000000/prep_service]: [SVM-to-client-msg:8A000002] locked 0->1 *Feb 7 18:52:31.127: SVM [D6000000/prep_service]: [AAA-Download:040DD9D0] unlocked 1->0 *Feb 7 18:52:31.131: SVM [D6000000/prep_service]: alloc feature info *Feb 7 18:52:31.131: SVM [D6000000/prep_service]: [SVM-Feature-Info:040E2E80] locked 0->1 *Feb 7 18:52:31.131: SVM [D6000000/prep_service]: has Policy info *Feb 7 18:52:31.131: SVM [D6000000/prep_service]: [PM-Info:0416BAB0] locked 0->1 *Feb 7 18:52:31.131: SVM [D6000000/prep_service]: populated client *Feb 7 18:52:31.131: SVM [D6000000/prep_service]: [PM-Download:8A000002] unlocked 1->0 *Feb 7 18:52:31.131: SVM [D6000000/prep_service]: [SVM-to-client-msg:8A000002] unlocked 1->0 *Feb 7 18:52:31.131: SVM [D6000000/prep_service]: [PM-Service:040E31E0] locked 0->1 *Feb 7 18:52:31.131: SVM [D0000001/CHILD/prep_service]: [SM-SIP-Apply:D0000001] locked 0->1 *Feb 7 18:52:31.131: SVM [D6000000/prep_service]: [FM-Bind:82000002] locked 0->1 *Feb 7 18:52:31.131: SVM [D6000000/prep_service]: [SVM-Feature-Info:040E2E80] unlocked 1->0 *Feb 7 18:52:31.139: SVM [D0000001/CHILD/prep_service]: alloc feature info *Feb 7 18:52:31.139: SVM [D0000001/CHILD/prep_service]: [SVM-Feature-Info:040E2E80] locked 0->1 *Feb 7 18:52:31.159: SVM [D0000001/CHILD/prep_service]: [FM-Bind:2C000003] locked 0->1 *Feb 7 18:52:31.159: SVM [D0000001/CHILD/prep_service]: [SVM-Feature-Info:040E2E80] unlocked 1->0 *Feb 7 18:52:31.159: SVM [D0000001/CHILD/prep_service]: [SM-SIP-Apply:D0000001] unlocked 1->0debug subscriber testing
To display diagnostic information for Intelligent Services Gateway (ISG) simulator testing, use the debug subscriber testing command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug subscriber testing
no debug subscriber testing
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows the configuration of the debug subscriber testing command:
Router# debug subscriber testingdrop (ISG)
To configure an Intelligent Services Gateway (ISG) to discard packets belonging to the default traffic class, use the drop command in service policy-map class configuration mode. To disable the packet-discarding action, use the no form of this command.
drop
no drop
Syntax Description
This command has no arguments or keywords.
Command Default
Packets will be passed.
Command Modes
Service policy-map configuration
Command History
Usage Guidelines
The drop command can only be configured in the default class of an ISG service policy map. The default traffic class handles all the traffic that is not handled by other traffic classes in a service.
Examples
The following example shows the default class configured to drop traffic for the service "SERVICE1":
policy-map type service SERVICE1class type traffic CLASS1prepaid-config PREPAIDclass type traffic defaultdropRelated Commands
greater-than
To create a condition that will evaluate true if the subscriber network access server (NAS) port identifier is greater than the specified value, use the greater-than command in control class-map configuration mode. To remove the condition, use the no form of this command.
greater-than [not] nas-port {adapter adapter-number | channel channel-number | ipaddr ip-address | port port-number | shelf shelf-number | slot slot-number | sub-interface sub-interface-number | type interface-type | vci vci-number | vlan vlan-id | vpi vpi-number}
no greater-than [not] nas-port {adapter adapter-number | channel channel-number | ipaddr ip-address | port port-number | shelf shelf-number | slot slot-number | sub-interface sub-interface-number | type interface-type | vci vci-number | vlan vlan-id | vpi vpi-number}
Syntax Description
Command Default
A condition that will evaluate true if the subscriber NAS port identifier is greater than the specified value is not created.
Command Modes
Control class-map configuration
Command History
Usage Guidelines
The greater-than command is used to configure a condition within a control class map. A control class map, which is configured with the class-map type control command, specifies conditions that must be met for a control policy to be activated, and, optionally, the event that causes the class to be evaluated. A control class map can contain multiple conditions, each of which will evaluate to either true or false. Match directives can be used to specify whether all, any, or none of the conditions must evaluate true in order for the class as whole to evaluate true.
The class type control command is used to associate a control class map with a policy control map.
Examples
The following example shows a control class map that evaluates true for only a specific range of ATM permanent virtual circuit (PVC) VCIs, 101-104 inclusive:
class-map type type control match-any MY-CONDITIONgreater-than nas-port type atm vpi 200 vci 100less-than nas-port type atm vpi 200 vci 105Related Commands
greater-than-or-equal
To create a condition that will evaluate true if the subscriber identifier is greater than or equal to the specified value, use the greater-than-or-equal command in control class-map configuration mode. To remove the condition, use the no form of this command.
greater-than-or-equal [not] nas-port {adapter adapter-number | channel channel-number | ipaddr ip-address | port port-number | shelf shelf-number | slot slot-number | sub-interface sub-interface-number | type interface-type | vci vci-number | vlan vlan-id | vpi vpi-number}
no greater-than-or-equal [not] nas-port {adapter adapter-number | channel channel-number | ipaddr ip-address | port port-number | shelf shelf-number | slot slot-number | sub-interface sub-interface-number | type interface-type | vci vci-number | vlan vlan-id | vpi vpi-number}
Syntax Description
Command Default
A condition that will evaluate true if the subscriber identifier is greater than or equal to the specified value is not created.
Command Modes
Control class-map configuration
Command History
Usage Guidelines
The greater-than-or-equal command is used to configure a condition within a control class map. A control class map, which is configured with the class-map type control command, specifies conditions that must be met for a control policy to be activated, and, optionally, the event that causes the class to be evaluated. A control class map can contain multiple conditions, each of which will evaluate to either true or false. Match directives can be used to specify whether all, any, or none of the conditions must evaluate true in order for the class as whole to evaluate true.
The class type control command is used to associate a control class map with a policy control map.
Examples
The following example shows a control class map called "class3" configured with three conditions. The match-all keyword indicates that all of the conditions must evaluate true before the class evaluates true. The class type control command associates "class3" with the control policy map called "rule4".
class-map type control match-all class3greater-than-or-equal nas-port port 1000!policy-map type control rule4class type control class3 event session-start1 authorize identifier nas-port!Related Commands
identifier interface
Note
To create an Intelligent Service Agent (ISG) IP interface session, use the identifier interface command in IP subscriber configuration mode. To remove the IP interface session, use the no form of this command.
identifier interface
no identifier interface
Syntax Description
This command has no arguments or keywords.
Command Default
An ISG IP interface session is not created.
Command Modes
IP subscriber configuration
Command History
12.2(28)SB
This command was introduced.
12.2(31)SB2
This command was replaced by the ip subscriber interface command.
Usage Guidelines
An IP interface session includes all IP traffic received on a specific physical or virtual interface. IP interface sessions are provisioned through the command-line interface (CLI), that is, the session is created when the IP interface session commands are entered.
IP interface sessions might be used in situations in which a subscriber is represented by an interface (with the exception of PPP) and communicates using more than one IP address. For example, a subscriber using routed bridge encapsulation (RBE) access might have a dedicated ATM virtual circuit (VC) to home customer premises equipment (CPE) that is hosting multiple PCs.
Examples
The following example shows an IP interface session configured on Ethernet interface 0/0:
interface ethernet0/0ip subscriberidentifier interfaceRelated Commands
identifier ip src-addr
Note
To enable an Intelligent Services Gateway (ISG) to create an IP session upon detection of the first IP packet from an unidentified subscriber, use the identifier ip src-addr command in IP subscriber configuration mode. To disable IP session creation upon receipt of IP packets from unidentified subscribers, use the no form of this command.
identifier ip src-addr [match access-list-number]
no identifier ip src-addr [match access-list-number]
Syntax Description
match access-list-number
(Optional) Causes IP sessions to be created only for subscriber traffic matching the access list.
Command Default
An ISG does not create IP sessions upon detection of the first IP packet from an unidentified subscriber.
Command Modes
IP subscriber configuration
Command History
12.2(28)SB
This command was introduced.
12.2(31)SB2
This command was replaced by the initiator command.
Usage Guidelines
An ISG subscriber IP session includes all the traffic that is associated with a single subscriber IP address. An IP subnet session includes all the IP traffic that is associated with a single IP subnet.
IP subnet sessions are created the same way as IP sessions, except that when a subscriber is authorized or authenticated and the Framed-IP-Netmask attribute is present in the user or service profile, the ISG converts the source-IP-based session into a subnet session with the subnet value in the Framed-IP-Netmask attribute.
Examples
The following example shows how to configure an ISG to create IP sessions upon detection of the first IP packet from unidentified subscribers:
interface ethernet0/0ip subscriberidentifier ip src-addrRelated Commands
identifier interface
Creates an ISG IP interface session.
ip subscriber
Enables ISG IP subscriber configuration mode.
if upon network-service-found
To specify whether the system should continue processing policy rules once a subscriber's network service has been identified, use the if upon network-service-found command in control policy-map class configuration mode. To remove this action from the control policy map, use the no form of this command.
action-number if upon network-service-found {continue | stop}
no action-number if upon network-service-found {continue | stop}
Syntax Description
Command Default
Actions will continue to be executed when a subscriber's network service is identified.
Command Modes
Control policy-map class configuration
Command History
Usage Guidelines
The if upon network-service-found command configures an action in a control policy map.
Control policies define the actions the system will take in response to specified events and conditions. A control policy map is used to configure an Intelligent Services Gateway (ISG) control policy. A control policy is made of one or more control policy rules. A control policy rule is an association of a control class and one or more actions. The control class defines the conditions that must be met before the actions will be executed. The actions are numbered and executed sequentially within the policy rule.
Examples
The following example shows how to configure ISG to stop executing actions once the subscriber's network service has been found:
policy-map type control policy1class type control always event session-start1 if upon network-service-found stopignore (ISG)
To configure an Intelligent Services Gateway (ISG) to ignore specific parameters in requests from RADIUS clients, use the ignore command in dynamic authorization local server configuration mode. To reinstate the default behavior, use the no form of this command.
ignore {session-key | server-key}
no ignore {session-key | server-key}
Syntax Description
session-key
Configures ISG to ignore the session key.
server-key
Configures ISG to ignore the server key.
Command Default
The ISG will not ignore the session key or server key.
Command Modes
Dynamic authorization local server configuration
Command History
Usage Guidelines
An ISG can be configured to allow external policy servers to dynamically send policies to the ISG. This functionality is facilitated by the Change of Authorization (CoA) RADIUS extension. CoA introduced peer to peer capability to RADIUS, enabling ISG and the external policy server each to act as a RADIUS client and server. Use the ignore command to configure the ISG to ignore the server key or session key in requests from RADIUS clients.
Examples
The following example configures ISG to ignore the server key in requests from RADIUS clients:
aaa server radius dynamic-authorclient 10.0.0.1ignore server-keyRelated Commands
aaa server radius dynamic-author
Configures an ISG as a AAA server to facilitate interaction with an external policy server.
initiator
To enable Intelligent Services Gateway (ISG) to create an IP subscriber session upon receipt of a specified type of packet, use the initiator command in IP subscriber configuration mode. To disable IP session creation in response to specified packets, use the no form of this command.
initiator {dhcp [class-aware] | radius-proxy | static ip subscriber list listname | unclassified ip | unclassified mac}
no initiator {dhcp [class-aware] | radius-proxy | static ip subscriber list listname | unclassified ip | unclassified mac}
Syntax Description
Command Default
IP sessions are not created upon receipt of specified packets.
Command Modes
IP subscriber configuration (config-subscriber)
Command History
Usage Guidelines
DHCP and ISG IP Session Creation
If the following conditions are met, receipt of a DHCP DISCOVER packet will trigger the creation of an IP session:
•
•
•
Note
DHCP and ISG IP Address Assignment
When ISG is in the path of DHCP requests (either as a DHCP server or as a relay), ISG can influence the IP address pool and the DHCP server that is used to assign subscriber IP addresses. To enable ISG to influence the IP addresses assigned to subscribers, you associate a DHCP address pool class with an address domain. When a DHCP request is received from a subscriber, DHCP uses the address pool class that is associated with the subscriber to determine which DHCP address pool should be used to service the request. As a result, on a per-request basis, an IP address is provided by the local DHCP server or relayed to a remote DHCP server that is defined in the selected pool. The class-aware keyword enables the ISG to provide DHCP with a class name.
Examples
The following example shows how to configure ISG to create IP sessions for subscribers who connect to ISG on Gigabit Ethernet interface 0/1.401 through a routed access network. ISG will create IP sessions upon receipt of DHCP DISCOVER packets, incoming valid IP packets, and RADIUS Access-Request packets.
interface GigabitEthernet0/1.401ip subscriber routedinitiator dhcp class-awareinitiator unclassified ip-addressinitiator radius-proxyinitiator static ip subscriber list mylistRelated Commands
interface multiservice
To create a multiservice interface, which enables dynamic virtual private network (VPN) selection on an Intelligent Services Gateway (ISG), use the interface multiservice command in global configuration mode. To remove a multiservice interface, use the no form of this command.
interface multiservice interface-number
no interface multiservice interface-number
Syntax Description
Command Default
A multiservice interface is not created.
Command Modes
Global configuration
Command History
Usage Guidelines
IP interface features (such as quality of service (QoS) and access lists) are not supported on multiservice interfaces.
For a subscriber without a static VPN configuration, a multiservice interface must be configured on the ISG device to map the IP subscriber session to a VRF. The multiservice interface represents a boundary between a VPN routing domain and the default routing domain. In cases where an IP subscriber may be associated with several routing domains throughout the duration of a connection, multiservice interfaces serve as demarcation points for the IP subscriber to switch from one VPN domain to another.
One multiservice interface must be configured for each VPN routing domain.
Examples
The following example shows the configuration of two multiservice interfaces:
interface multiservice 1ip address 10.69.10.1 255.255.255.0!interface multiservice 2ip vrf forwarding Corporate-VPNip address 10.1.1.1 255.255.255.0interim-interval
To specify the interval at which the Intelligent Services Gateway (ISG) sends interim prepaid accounting records, use the interim-interval command in prepaid configuration mode. To disable interim prepaid accounting, use the no form of this command.
interim-interval number-of-minutes
no interim-interval number-of-minutes
Syntax Description
number-of-minutes
Interval, in minutes, between prepaid accounting record updates. Range is from 1 to 1440.
Command Default
Interim prepaid accounting is not enabled.
Command Modes
Prepaid configuration
Command History
Usage Guidelines
When the interim-interval command is configured, the ISG sends accounting records at the specified interval so there will be written log of accounting events that occurred between the Accounting-Start and Accounting-Stop records.
Examples
The following example shows an ISG prepaid feature configuration in which the interval for interim prepaid accounting is set to 5 minutes:
subscriber feature prepaid conf-prepaidinterim-interval 5threshold time 20threshold volume 0method-list accounting ap-mlistmethod-list authorization defaultpassword ciscoRelated Commands
ip access-group
To apply an IP access list or object group access control list (OGACL) to an interface or a service policy map, use the ip access-group command in the appropriate configuration mode. To remove an IP access list or OGACL, use the no form of this command.
ip access-group {access-list-name | access-list-number} {in | out}
no ip access-group {access-list-number | access-list-name} {in | out}
Syntax Description
Command Default
An access list is not applied.
Command Modes
Interface configuration (config-if)
Service policy-map configuration (config-service-policymap)Command History
Usage Guidelines
If the specified access list does not exist, all packets are passed (no warning message is issued).
Applying Access Lists to Interfaces
Access lists or OGACLs are applied on either outbound or inbound interfaces. For standard inbound access lists, after an interface receives a packet, the Cisco IOS software checks the source address of the packet against the access list. For extended access lists or OGACLs, the networking device also checks the destination access list or OGACL. If the access list or OGACL permits the address, the software continues to process the packet. If the access list or OGACL rejects the address, the software discards the packet and returns an Internet Control Management Protocol (ICMP) host unreachable message.
For standard outbound access lists, after a device receives and routes a packet to a controlled interface, the software checks the source address of the packet against the access list. For extended access lists or OGACLs, the networking device also checks the destination access list or OGACL. If the access list or OGACL permits the address, the software sends the packet. If the access list or OGACL rejects the address, the software discards the packet and returns an ICMP host unreachable message.
When you enable outbound access lists or OGACLs, you automatically disable autonomous switching for that interface. When you enable inbound access lists or OGACLs on any CBus or CxBus interface, you automatically disable autonomous switching for all interfaces (with one exception—a Storage Services Enabler (SSE) configured with simple access lists can still switch packets, on output only).
Applying Access Lists or OGACLs to Service Policy Maps
You can use the ip access-group command to configure Intelligent Services Gateway (ISG) per-subscriber firewalls. Per-subscriber firewalls are Cisco IOS IP access lists or OGACLs that are used to prevent subscribers, services, and pass-through traffic from accessing specific IP addresses and ports.
ACLs and OGACLs can be configured in user profiles or service profiles on an authentication, authorization, and accounting (AAA) server or in service policy maps on an ISG. OGACLS or numbered or named IP access lists can be configured on the ISG, or the ACL or OGACL statements can be included in the profile configuration.
When an ACL or OGACL is added to a service, all subscribers of that service are prevented from accessing the specified IP address, subnet mask, and port combinations through the service.
Examples
The following example applies list 101 on packets outbound from Ethernet interface 0:
Router> enableRouter# configure terminalRouter(config)# interface ethernet 0Router(config-if)# ip access-group 101 outRelated Commands
ip portbundle (global)
To enable portbundle configuration mode, in which Intelligent Services Gateway (ISG) port-bundle host key parameters can be configured, use the ip portbundle command in global configuration mode. To remove the configuration of the port-bundle host key parameters and release all the port bundles in use, use the no form of this command.
ip portbundle
no ip portbundle
Syntax Description
This command has no arguments or keywords.
Command Default
Portbundle configuration mode is not enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Entering the no ip portbundle command in global configuration mode removes the configuration of port-bundle host key parameters and releases all the port bundles in use by the sessions.
Examples
The following example shows how to configure the ISG Port-Bundle Host Key feature to apply to all sessions:
policy-map type service ISGPBHKServiceip portbundle!policy-map type control PBHKRuleclass type control always event session-start1 service-policy type service ISGPBHKService!service-policy type control PBHKRuleinterface ethernet0/0ip address 10.1.1.1 255.255.255.0ip portbundle outside!ip portbundlematch access-list 101length 5source ethernet0/0Related Commands
ip portbundle (service policy-map)
To enable the Intelligent Services Gateway (ISG) Port-Bundle Host Key feature for a service, use the ip portbundle command in service policy-map configuration mode. To disable the ISG Port-Bundle Host Key feature, use the no form of this command.
ip portbundle
no ip portbundle
Syntax Description
This command has no arguments or keywords.
Command Default
ISG Port-Bundle Host Key feature is not enabled.
Command Modes
Service policy-map configuration
Command History
Usage Guidelines
When the ISG Port-Bundle Host Key feature is configured, TCP packets from subscribers are mapped to a local IP address for the ISG and a range of ports. This mapping allows the portal to identify the ISG gateway from which the session originated.
The ISG Port-Bundle Host Key feature can be enabled in a service policy map on the router by using the ip portbundle command. The feature can also be enabled in a service profile or user profile on a AAA server.
Examples
The following example shows how to configure the ISG Port-Bundle Host Key feature to apply to all sessions. The ISG Port-Bundle Host Key feature is enabled in the service policy map called "ISGPBHKService".
policy-map type service ISGPBHKServiceip portbundle!policy-map type control PBHKRuleclass type control always event session-start1 service-policy type service ISGPBHKService!service-policy type control PBHKRuleinterface ethernet0/0ip address 10.1.1.1 255.255.255.0ip portbundle outside!ip portbundlematch access-list 101length 5source ethernet0/0Related Commands
ip portbundle outside
To configure an Intelligent Services Gateway (ISG) to translate the destination IP address and TCP port to the actual subscriber IP address and TCP port for traffic going from the portal to the subscriber, use the ip portbundle outside command in interface configuration mode. To disable ISG port-bundle host key translation, use the no form of this command.
ip portbundle outside
no ip portbundle outside
Syntax Description
This command has no arguments or keywords.
Command Default
Translation does not occur.
Command Modes
Interface configuration
Command History
Usage Guidelines
The ip portbundle outside command must be configured on ISG interfaces that reach the portal.
Examples
The following example configures ISG to translate the destination IP address and TCP port to the actual subscriber IP address and TCP port for traffic going from the portal to the subscriber. Ethernet interface 0/0 is an interface that reaches the portal.
interface ethernet0/0ip address 10.1.1.1 255.255.255.0ip portbundle outsideRelated Commands
ip route-cache
To control the use of switching methods for forwarding IP packets, use the ip route-cache command in interface configuration mode. To disable any of these switching methods, use the no form of this command.
ip route-cache [cef | distributed | flow | policy | same-interface]
no ip route-cache [cef | distributed | flow | policy | same-interface]
Syntax Description
Command Default
The switching method is not controlled.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
IP Route Cache
Note
Using the route cache is often called fast switching. The route cache allows outgoing packets to be load-balanced on a per-destination basis rather than on a per-packet basis. The ip route-cache command with no additional keywords enables fast switching.
Entering the ip route-cache command has no effect on a subinterface. Subinterfaces accept the no form of the command; however, this disables Cisco Express Forwarding or distributed Cisco Express Forwarding on the physical interface and all subinterfaces associated with the physical interface
The default behavior for Fast Switching varies by interface and media.
Note
IP Route Cache Same Interface
You can enable IP fast switching when the input and output interfaces are the same interface, using the ip route-cache same-interface command. This configuration normally is not recommended, although it is useful when you have partially meshed media, such as Frame Relay or you are running Web Cache Communication Protocol (WCCP) redirection. You could use this feature on other interfaces, although it is not recommended because it would interfere with redirection of packets to the optimal path.
IP Route Cache Flow
The flow caching option can be used in conjunction with Cisco Express Forwarding switching to enable NetFlow, which allows statistics to be gathered with a finer granularity. The statistics include IP subprotocols, well-known ports, total flows, average number of packets per flow, and average flow lifetime.
Note
ip flow ingress command is configured, both commands will appear in the output of the
show running-config command.IP Route Cache Distributed
The distributed option is supported on Cisco routers with line cards and Versatile Interface Processors (VIPs) that support Cisco Express Forwarding switching.
On Cisco routers with Route/Switch Processor (RSP) and VIP controllers, the VIP hardware can be configured to switch packets received by the VIP with no per-packet intervention on the part of the RSP. When VIP distributed switching is enabled, the input VIP interface tries to switch IP packets instead of forwarding them to the RSP for switching. Distributed switching helps decrease the demand on the RSP.
If the ip route-cache distributed, ip cef distributed, and ip route-cache flow commands are configured, the VIP performs distributed Cisco Express Forwarding switching and collects a finer granularity of flow statistics.
IP Route-Cache Cisco Express Forwarding
In some instances, you might want to disable Cisco Express Forwarding or distributed Cisco Express Forwarding on a particular interface because that interface is configured with a feature that
Cisco Express Forwarding or distributed Cisco Express Forwarding does not support. Because all interfaces that support Cisco Express Forwarding or distributed Cisco Express Forwarding are enabled by default when you enable Cisco Express Forwarding or distributed Cisco Express Forwarding operation globally, you must use the no form of the ip route-cache distributed command in the interface configuration mode to turn Cisco Express Forwarding or distributed Cisco Express Forwarding operation off a particular interface.Disabling Cisco Express Forwarding or distributed Cisco Express Forwarding on an interface disables Cisco Express Forwarding or distributed Cisco Express Forwarding switching for packets forwarded to the interface, but does not affect packets forwarded out of the interface.
Additionally, when you disable distributed Cisco Express Forwarding on the RSP, Cisco IOS software switches packets using the next-fastest switch path (Cisco Express Forwarding).
Enabling Cisco Express Forwarding globally disables distributed Cisco Express Forwarding on all interfaces. Disabling Cisco Express Forwarding or distributed Cisco Express Forwarding globally enables process switching on all interfaces.
Note
IP Route Cache Policy
If Cisco Express Forwarding is already enabled, the ip route-cache route command is not required because PBR packets are Cisco Express Forwarding-switched by default.
Before you can enable fast-switched PBR, you must first configure PBR.
FSPBR supports all of PBR's match commands and most of PBR's set commands, with the following restrictions:
•
•
Also, at the process level, the routing table is consulted to determine if the interface is on a reasonable path to the destination. During fast switching, the software does not make this check. Instead, if the packet matches, the software blindly forwards the packet to the specified interface.
Note
Examples
Configuring Fast Switching and Disabling Cisco Express Forwarding Switching
The following example shows how to enable fast switching and disable Cisco Express Forwarding switching:
Router(config)# interface ethernet 0/0/0Router(config-if)# ip route-cacheThe following example shows that fast switching is enabled:
Router# show ip interface fastEthernet 0/0/0FastEthernet0/0/0 is up, line protocol is upInternet address is 10.1.1.254/24Broadcast address is 255.255.255.224Address determined by non-volatile memoryMTU is 1500 bytesHelper address is not setDirected broadcast forwarding is disabledMulticast reserved groups joined: 224.0.0.10Outgoing access list is not setInbound access list is not setProxy ARP is enabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is disabledIP Flow switching is disabledIP Distributed switching is disabledIP Feature Fast switching turbo vectorIP Null turbo vectorIP multicast fast switching is enabledThe following example shows that Cisco Express Forwarding switching is disabled:
Router# show cef interface fastEthernet 0/0/0FastEthernet0/0/0 is up (if_number 3)Corresponding hwidb fast_if_number 3Corresponding hwidb firstsw->if_number 3Internet address is 10.1.1.254/24ICMP redirects are always sentPer packet load-sharing is disabledIP unicast RPF check is disabledInbound access list is not setOutbound access list is not setIP policy routing is disabledHardware idb is FastEthernet0/0/0Fast switching type 1, interface type 18IP CEF switching disabledIP Feature Fast switching turbo vectorIP Null turbo vectorInput fast flags 0x0, Output fast flags 0x0ifindex 1(1)Slot 0 Slot unit 0 VC -1Transmit limit accumulator 0x48001A02 (0x48001A02)IP MTU 1500The following example shows the configuration information for interface fastethernet 0/0/0:
Router# show running-config..!interface FastEthernet0/0/0ip address 10.1.1.254 255.255.255.0no ip route-cache cefno ip route-cache distributed!The following example shows how to enable Cisco Express Forwarding (and to disable distributed
Cisco Express Forwarding if it is enabled):Router(config-if)# ip route-cache cefThe following example shows how to enable VIP distributed Cisco Express Forwarding and per-flow accounting on an interface (regardless of the previous switching type enabled on the interface):
Router(config)# interface e0Router(config-if)# ip address 10.252.245.2 255.255.255.0Router(config-if)# ip route-cache distributedRouter(config-if)# ip route-cache flowThe following example shows how to enable Cisco Express Forwarding on the router globally (which also disables distributed Cisco Express Forwarding on any interfaces that are running distributed
Cisco Express Forwarding), and disable Cisco Express Forwarding (which enables process switching) on Ethernet interface 0:Router(config)# ip cefRouter(config)# interface e0Router(config-if)# no ip route-cache cefThe following example shows how to enable distributed Cisco Express Forwarding operation on the router (globally), and disable Cisco Express Forwarding operation on Ethernet interface 0:
Router(config)# ip cef distributedRouter(config)# interface e0Router(config-if)# no ip route-cache cefThe following example shows how to reenable distributed Cisco Express Forwarding operation on Ethernet interface 0:
Router(config)# ip cef distributedRouter(config)# interface e0Router(config-if)# ip route-cache distributedConfiguring Fast Switching for Traffic That Is Received and Transmitted over the Same Interface
The following example shows how to enable fast switching and disable Cisco Express Forwarding switching:
Router(config)# interface ethernet 0/0/0Router(config-if)# ip route-cache same-interfaceThe following example shows that fast switching on the same interface is enabled for interface fastethernet 0/0/0:
Router# show ip interface fastEthernet 0/0/0FastEthernet0/0/0 is up, line protocol is upInternet address is 10.1.1.254/24Broadcast address is 255.255.255.224Address determined by non-volatile memoryMTU is 1500 bytesHelper address is not setDirected broadcast forwarding is disabledMulticast reserved groups joined: 224.0.0.10Outgoing access list is not setInbound access list is not setProxy ARP is enabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is enabledIP Flow switching is disabledIP Distributed switching is disabledIP Feature Fast switching turbo vectorIP Null turbo vectorIP multicast fast switching is enabledIP multicast distributed fast switching is disabledIP route-cache flags are FastRouter Discovery is disabledIP output packet accounting is disabledIP access violation accounting is disabledTCP/IP header compression is disabledRTP/IP header compression is disabledProbe proxy name replies are disabledPolicy routing is disabledNetwork address translation is disabledWCCP Redirect outbound is disabledWCCP Redirect inbound is disabledWCCP Redirect exclude is disabledBGP Policy Mapping is disabledIP multicast multilayer switching is disabledThe following example shows the configuration information for interface fastethernet 0/0/0:
Router# show running-config..!interface FastEthernet0/0/0ip address 10.1.1.254 255.255.255.0ip route-cache same-interfaceno ip route-cache cefno ip route-cache distributed!Enabling NetFlow Accounting
The following example shows how to enable NetFlow switching:
Router(config)# interface ethernet 0/0/0Router(config-if)# ip route-cache flowThe following example shows that NetFlow accounting is enabled for interface fastethernet 0/0/0:
Router# show ip interface fastEthernet 0/0/0FastEthernet0/0/0 is up, line protocol is upInternet address is 10.1.1.254/24Broadcast address is 255.255.255.224Address determined by non-volatile memoryMTU is 1500 bytesHelper address is not setDirected broadcast forwarding is disabledMulticast reserved groups joined: 224.0.0.10Outgoing access list is not setInbound access list is not setProxy ARP is enabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is disabledIP Flow switching is enabledIP Distributed switching is disabledIP Flow switching turbo vectorIP Null turbo vectorIP multicast fast switching is enabledIP multicast distributed fast switching is disabledIP route-cache flags are Fast, FlowRouter Discovery is disabledIP output packet accounting is disabledIP access violation accounting is disabledTCP/IP header compression is disabledRTP/IP header compression is disabledProbe proxy name replies are disabledPolicy routing is disabledNetwork address translation is disabledWCCP Redirect outbound is disabledWCCP Redirect inbound is disabledWCCP Redirect exclude is disabledBGP Policy Mapping is disabledIP multicast multilayer switching is disabledConfiguring Distributed Switching
The following example shows how to enable distributed switching:
Router(config)# ip cef distributedRouter(config)# interface ethernet 0/0/0Router(config-if)# ip route-cache distributedThe following example shows that distributed Cisco Express Forwarding switching is for interface fastethernet 0/0/0:
Router# show cef interface fastEthernet 0/0/0FastEthernet0/0/0 is up (if_number 3)Corresponding hwidb fast_if_number 3Corresponding hwidb firstsw->if_number 3Internet address is 10.1.1.254/24ICMP redirects are always sentPer packet load-sharing is disabledIP unicast RPF check is disabledInbound access list is not setOutbound access list is not setIP policy routing is disabledHardware idb is FastEthernet0/0/0Fast switching type 1, interface type 18IP Distributed CEF switching enabledIP Feature Fast switching turbo vectorIP Feature CEF switching turbo vectorInput fast flags 0x0, Output fast flags 0x0ifindex 1(1)Slot 0 Slot unit 0 VC -1Transmit limit accumulator 0x48001A02 (0x48001A02)IP MTU 1500Configuring Fast Switching for PBR
The following example shows how to configure a simple policy-based routing scheme and to enable FSPBR:
Router(config)# access-list 1 permit 10.1.1.0 0.0.0.255Router(config)# route-map mypbrtag permit 10Router(config-route-map)# match ip address 1Router(config-route-map)# set ip next-hop 10.1.1.195Router(config-route-map)# exitRouter(config)# interface fastethernet 0/0/0Router(config-if)# ip route-cache policyRouter(config-if)# ip policy route-map mypbrtagThe following example shows that FSPBR is enabled for interface fastethernet 0/0/0:
Router# show ip interface fastEthernet 0/0/0FastEthernet0/0/0 is up, line protocol is upInternet address is 10.1.1.254/24Broadcast address is 255.255.255.255Address determined by non-volatile memoryMTU is 1500 bytesHelper address is not setDirected broadcast forwarding is disabledMulticast reserved groups joined: 224.0.0.10Outgoing access list is not setInbound access list is not setProxy ARP is enabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is disabledIP Flow switching is disabledIP CEF switching is enabledIP Distributed switching is enabledIP Feature Fast switching turbo vectorIP Feature CEF switching turbo vectorIP multicast fast switching is enabledIP multicast distributed fast switching is disabledIP route-cache flags are Fast, Distributed, Policy, CEFRouter Discovery is disabledIP output packet accounting is disabledIP access violation accounting is disabledTCP/IP header compression is disabledRTP/IP header compression is disabledProbe proxy name replies are disabledPolicy routing is enabled, using route map my_pbr_tagNetwork address translation is disabledWCCP Redirect outbound is disabledWCCP Redirect inbound is disabledWCCP Redirect exclude is disabledBGP Policy Mapping is disabledIP multicast multilayer switching is disabledRelated Commands
ip source
To create a static session server source address, use the ip source command in server list configuration mode. To remove the static session server source address, use the no form of this command.
ip source ip-address [mac mac-address | mask network-mask]
no ip source ip-address [mac mac-address | mask network-mask]
Syntax Description
ip-address
Static session server ip-address.
mac mac-address
(Optional) Static session server mac address.
mask mask-address
(Optional) Static session server network mask.
Command Default
A static session server source address is not created.
Command Modes
Server list configuration (config-server-list)
Command History
12.2(33)SRE
This command was introduced.
Cisco IOS XE Release 2.5
This command was integrated into Cisco IOS XE Release 2.5.
Usage Guidelines
The static session source address can be created only after creating an ip subscriber static server list name. The keyword mask needs to be used for routed interfaces and mac needs to be used for l2-connected interfaces.
Examples
In the following example a static session server source address for a routed interface list routed-server-list-name is created:
Router(config)# ip subscriber list my-connected-server-listRouter(config-server-list)# ip source 209.165.200.225 mask 255.255.255.224Related Commands
ip subscriber
To enable Intelligent Services Gateway (ISG) IP subscriber support on an interface and to specify the access method that IP subscribers will use to connect to ISG on an interface, use the ip subscriber command in interface configuration mode. To disable ISG IP session support on an interface, use the no form of this command.
ip subscriber {l2-connected | routed}
no ip subscriber {l2-connected | routed}
Syntax Description
Command Default
An IP subscriber access method is not specified.
Command Modes
Interface configuration
Command History
Usage Guidelines
One access method may be specified on an interface at a time.
The ip subscriber command enables IP subscriber configuration mode, in which the triggers for IP session initiation can be configured.
Use the no ip subscriber command to disable IP session support on the interface. Entering the no ip subscriber command removes the commands that were entered in IP subscriber configuration submode from the configuration. It also removes the ip subscriber command from the configuration. After the no ip subscriber command has been entered, no new IP sessions will be created on the interface. IP sessions that were already created will not be brought down, but ISG will not execute any features on those sessions.
Note
Examples
The following example shows how to configure ISG to create IP sessions for subscribers who connect to ISG on Gigabit Ethernet interface 0/1.401 through a Layer 2 connected access network. ISG will create IP sessions upon receipt of any frame with a valid source MAC address.
interface GigabitEthernet0/1.401ip subscriber l2-connectedinitiator unclassified mac-addressRelated Commands
initiator
Enables ISG to create an IP subscriber session upon receipt of a specified type of packet.
ip subscriber interface
Creates an ISG IP interface session.
ip subscriber interface
To create an Intelligent Services Gateway (ISG) IP interface session, use the ip subscriber interface command in interface configuration mode. To remove the IP interface session, use the no form of this command.
ip subscriber interface
no ip subscriber interface
Syntax Description
This command has no keywords or arguments.
Command Default
An IP interface session is not created.
Command Modes
Interface configuration
Command History
Usage Guidelines
An IP interface session includes all IP traffic received on a specific physical or virtual interface. IP interface sessions are provisioned through the command-line interface (CLI); that is, a session is created when the IP interface session commands are entered, and the session is continuous, even when the interface is shut down. By default, IP interface sessions come up in the state "unauthenticated" with full network access.
When access interfaces are used to identify IP subscribers, each access interface corresponds to a single IP subscriber. As soon as the access interface becomes available, ISG creates an IP session using the interface as the key, and associates all IP traffic coming into and going out of this interface to the IP session. For interface IP sessions, ISG classifies IP traffic as follows:
•
•
IP interface sessions might be used in situations in which a subscriber is represented by an interface (with the exception of PPP) and communicates using more than one IP address. For example, a subscriber using routed bridge encapsulation (RBE) access might have a dedicated ATM virtual circuit (VC) to home customer premises equipment (CPE) that is hosting multiple PCs.
Examples
The following example shows an IP interface session configured on Ethernet interface 0/0:
interface ethernet0/0ip subscriber interfaceRelated Commands
ip subscriber
Enables ISG IP subscriber support on an interface and specifies the access method that IP subscribers will use to connect to ISG on an interface.
ip subscriber list
To create an ip subscriber static server list group name, use the ip subscriber list command in global configuration mode. To remove a static server list group, use the no form of this command.
ip subscriber list server-list-name
no ip subscriber list server-list-name
Syntax Description
Command Default
A static session server list group is not created.
Command Modes
Global configuration (config)
Command History
12.2(33)SRE
This command was introduced.
Cisco IOS XE Release 2.5
This command was integrated into Cisco IOS XE Release 2.5.
Usage Guidelines
Static sessions are removed for all interfaces associated with the current list when you exit the ip subscriber list mode. The no ip subscriber list command is rejected if the server list is used by any other interface.
Examples
In the following example a static server list group called my-connected-server-list is created:
Router(config)# ip subscriber list my-connected-server-listRelated Commands
ip vrf autoclassify
To enable Virtual Routing and Forwarding (VRF) autoclassify on a source interface, use the ip vrf autoclassify command in interface configuration mode. To remove VRF autoclassify, use the no form of this command.
ip vrf autoclassify source
no ip vrf autoclassify source
Syntax Description
Command Default
The VFR autoclassify functionality is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
The ip vrf autoclassify command enables the capability to map packets from connected hosts to VRFs that are different from the VRF defined on the ingress interface. It also enables the configuration of policies that are required for the mapping of packets to the VRFs depending on whether the source address of the packet belong to those connected routes.
The routing information can be learned dynamically or statically defined.
Examples
In the following example, the Fast Ethernet interface 0/0 is configured with two secondary addresses, 1.1.1.1/24 and 2.1.1.1/24. The first address, 1.1.1.1/24, is assigned to VRF red, while the other, 2.1.1.1/24, is assigned to VRF green. So in the VRF red table, a connected route 1.1.1.0/24 is installed, while in VRF green, 2.1.1.0/24 is installed:
interface fast ethernet0/0ip address 1.1.1.1 255.255.255.0 secondary vrf redip address 2.1.1.1 255.255.255.0 secondary vrf greenip vrf autoclassify sourceThere is a default route in VRF red that directs all traffic to Fast Ethernet interface 1/0, while in VRF green, another default route directs all traffic to Fast Ethernet interface 1/1. When packets arrive at Fast Ethernet interface 0/0, they are mapped to either VRF red or VRF green based on their source address. If the source address is 1.1.1.2, connected route 1.1.1.0/24 is used, and the packet is mapped to VRF red. Following the default route, it is forwarded out of Fast Ethernet interface 1/0.
The return packets are mapped to the VRF configured on the downstream interface. Refer to the ip vrf forwarding command for more information in the Cisco IOS Switching Services Command Reference, Release 12.3T.
Related Commands
ip vrf forwarding (service policy map)
To associate a virtual routing/forwarding instance (VRF) with an Intelligent Services Gateway (ISG) service policy map, use the ip vrf forwarding command in service policy map configuration mode. To disassociate a VRF, use the no form of this command.
ip vrf forwarding vrf-name
no ip vrf forwarding vrf-name
Syntax Description
Command Default
A VRF is not specified.
Command Modes
Service policy map configuration
Command History
Usage Guidelines
Use the ip vrf forwarding command to configure a network-forwarding policy for IP sessions in an ISG service policy map.
Examples
The following example shows a service policy map configured with a network-forwarding policy for IP sessions:
policy-map type service my_serviceip vrf forwarding vrf1Related Commands
keepalive (ISG)
To enable keepalive packets and to specify their transmission attributes, use the keepalive command in service policy map configuration mode. To disable keepalive packets, use the no form of this command.
keepalive [idle idle-seconds] [attempts max-retries] [interval retry-seconds] [protocol {ARP | ICMP [broadcast]}]
no keepalive
Syntax Description
Command Default
Keepalive messages are not enabled.
Command Modes
Service policy map configuration (config-service-policymap)
Command History
Usage Guidelines
If you enter only the keepalive command with no keywords or arguments, default values are set. Values are platform and release-specific. For more information, use the question mark (?) online help function.
Keepalive Message Protocol
For a directly connected host, ARP must be used. When the session is established and the keepalive feature is configured to use ARP, the keepalive feature saves the ARP entry as a valid original entry for verifying future ARP responses.
Note
For routed hosts, you can configure ICMP as the protocol for keepalive messages. If ICMP is configured, the ICMP "hello" request is sent to the subscriber and checked for a response, until the configured maximum number of attempts is exceeded.
For IP subnet sessions, the peer (destination) IP address to be used for ICMP "hello" requests will be all the IP addresses within the subnet. This means "hello" requests will be sent sequentially (not simultaneously) to all the possible hosts within that subnet. If there is no response from any host in that subnet, the session will be disconnected.
There is an option to configure ICMP directed broadcast for keepalive requests. If the subscriber hosts recognize the IP subnet broadcast address, the ISG can send the ICMP "hello" request to the subnet broadcast address. The subscribers need not be on the same subnet as the ISG for this configuration to work. A directed broadcast keepalive request can work multiple hops away as long as the following conditions are satisfied:
•
•
When these two conditions are satisfied, you can optimize the ICMP keepalive configuration to minimize the number of ICMP packets.
Note
Examples
The following example shows how to set the idle time to 120 seconds with 5 retry attempts at 5 second intervals using ARP protocol. Examples of both On Box and AAA Server configurations are provided:
<On Box Configuration>policy-map type service Keepalivekeepalive idle 120 attempts 5 interval 5 protocol ARP<AAA Server Configuration>vsa cisco generic 1 string "subscriber:keepalive=idle 120 attempts 5 interval 5 protocol ARP"key (ISG RADIUS proxy)
To configure the shared key between Intelligent Services Gateway (ISG) and a RADIUS proxy client, use the key command in RADIUS proxy server configuration mode or RADIUS proxy client configuration mode. To remove this configuration, use the no form of this command.
key [0 | 7] word
no key [0 | 7] word
Syntax Description
0
(Optional) An unencrypted key will follow.
7
(Optional) A hidden key will follow.
word
Unencrypted shared key.
Command Default
A shared key is not configured.
Command Modes
RADIUS proxy server configuration
RADIUS proxy client configurationCommand History
Usage Guidelines
The shared key can be specified globally for all RADIUS proxy clients, or it can be specified per client. The per-client configuration of this command overrides the global configuration.
Examples
The following example shows the configuration of global RADIUS proxy parameters and client-specific parameters for two RADIUS proxy clients. Because a shared secret is not configured specifically for client 10.1.1.1, it will inherit the shared secret specification, which is "cisco", from the global RADIUS proxy configuration. Client 10.2.2.2 will use "systems" as the shared secret.
aaa server radius proxykey ciscoclient 10.1.1.1accounting port 1813authentication port 1812!client 10.2.2.2key systems!Related Commands
length (ISG)
To specify the Intelligent Services Gateway (ISG) port-bundle length, which determines the number of bundles per group and the number of ports per bundle, use the length command in portbundle configuration mode. To return the port-bundle length to the default value, use the no form of this command.
length bits
no length bits
Syntax Description
Command Default
The port-bundle length has a default value of 4 bits.
Command Modes
Portbundle configuration
Command History
Usage Guidelines
The port-bundle length is used to determine the number of bundles in one group and the number of ports in one bundle. The number of ports in a bundle is the number of simultaneous TCP sessions that a subscriber can have. By default, the port-bundle length is 4 bits. The maximum port-bundle length is 10 bits. See Table 2 for available port-bundle length values and the resulting port-per-bundle and bundle-per-group values. Increasing the port-bundle length can be useful when you see frequent error messages about running out of ports in a port bundle, but note that the new value does not take effect until ISG next reloads and the portal server restarts.
Note
Examples
The following example results in 64 ports per bundle and 1008 bundles per group:
ip portbundlelength 6Related Commands
less-than
To create a condition that will evaluate true if the subscriber network access server (NAS) port identifier is less than the specified value, use the less-than command in control class-map configuration mode. To remove the condition, use the no form of this command.
less-than [not] nas-port {adapter adapter-number | channel channel-number | ipaddr ip-address | port port-number | shelf shelf-number | slot slot-number | sub-interface sub-interface-number | type interface-type | vci vci-number | vlan vlan-id | vpi vpi-number}
no less-than [not] nas-port {adapter adapter-number | channel channel-number | ipaddr ip-address | port port-number | shelf shelf-number | slot slot-number | sub-interface sub-interface-number | type interface-type | vci vci-number | vlan vlan-id | vpi vpi-number}
Syntax Description
Command Default
A condition that will evaluate true if the subscriber network access server (NAS) port identifier is less than the specified value is not created.
Command Modes
Control class-map configuration
Command History
Usage Guidelines
The less-than command is used to configure a condition within a control class map. A control class map, which is configured with the class-map type control command, specifies conditions that must be met for a control policy to be activated, and, optionally, the event that causes the class to be evaluated. A control class map can contain multiple conditions, each of which will evaluate to either true or false. Match directives can be used to specify whether all, any, or none of the conditions must evaluate true in order for the class as whole to evaluate true.
The class type control command is used to associate a control class map with a policy control map.
Examples
The following example shows a control class map that evaluates true for only a specific range of ATM permanent virtual circuit (PVC) VCIs, 101-104 inclusive:
class-map type type control match-any MY-CONDITIONgreater-than nas-port type atm vpi 200 vci 100less-than nas-port type atm vpi 200 vci 105Related Commands
less-than-or-equal
To create a condition that will evaluate true if the subscriber network access server (NAS) port identifier is less than or equal to the specified value, use the less-than-or-equal command in control class-map configuration mode. To remove the condition, use the no form of this command.
less-than-or-equal [not] nas-port {adapter adapter-number | channel channel-number | ipaddr ip-address | port port-number | shelf shelf-number | slot slot-number | sub-interface sub-interface-number | type interface-type | vci vci-number | vlan vlan-id | vpi vpi-number}
no less-than-or-equal [not] nas-port {adapter adapter-number | channel channel-number | ipaddr ip-address | port port-number | shelf shelf-number | slot slot-number | sub-interface sub-interface-number | type interface-type | vci vci-number | vlan vlan-id | vpi vpi-number}
Syntax Description
Command Default
A condition that will evaluate true if the subscriber NAS port identifier is less than or equal to the specified value is not created.
Command Modes
Control class-map configuration
Command History
Usage Guidelines
The less-than-or-equal command is used to configure a condition within a control class map. A control class map, which is configured with the class-map type control command, specifies conditions that must be met for a control policy to be activated, and, optionally, the event that causes the class to be evaluated. A control class map can contain multiple conditions, each of which will evaluate to either true or false. Match directives can be used to specify whether all, any, or none of the conditions must evaluate true in order for the class as whole to evaluate true.
The class type control command is used to associate a control class map with a policy control map.
Examples
The following example shows a control class map called "class3" configured with three conditions. The match-all keyword indicates that all of the conditions must evaluate true before the class evaluates true. The class type control command associates "class3" with the control policy map called "rule4".
class-map type control match-all class3less-than-or-equal nas-port port 1000!policy-map type control rule4class type control class3 event session-start1 authorize identifier nas-portRelated Commands
