# Subscriber Management Commands

This section describes the commands that you use to configure subscriber management. For commands related to a specific component, see the appropriate documentation.

- DHCP—DHCP Overview Information
- Policies—JunosE Policy Management Configuration Guide
- QoS—JunosE Quality of Service Configuration Guide
- Route maps—JunosE IP Services Configuration Guide
- SRC software—SRC software documentation set

clear ip demux

- Use to clear all dynamically created demultiplexer table entries associated with the route-map processing of the set ip source-prefix command.
  - deny—Drop addresses that appear in the source address range
  - primary—Associate the source prefix with the primary IP interface
- Example
  host1(config-if)#clear ip demux
- There is no no version.
- See clear ip demux

domain

- Use to specify a domain for an IP service profile.
- The domain is included in a username that is dynamically created by JunosE subscriber management.
- Specify a domain name with up to 32 ASCII characters.
- Example
  host1(config-service-profile)#domain eastcoast
- Use the no version to remove the domain from the IP service profile.
- See domain

include circuit-identifier

- Use to include the circuit identifier in the username that is dynamically created by JunosE subscriber management.
- Specify one of the following circuit types: atm or vlan.
- Use the optional prepend-circuit-type keyword to specify that the circuit type is prepended to the circuit identifier in the username.
- Example
  host1(config-service-profile)#include circuit-identifier atm prepend-circuit-type
- Use the no version to disable inclusion of the circuit identifier in the username.
- See include circuit-identifier

include dhcp-option 82

- Use to include a suboption of the DHCP relay agent information option (option 82) in the username that is dynamically created by JunosE subscriber management.
- Specify one of the following suboptions: agent-circuit-id or agent-remote-id.
- Example
  host1(config-service-profile)#include dhcp-option 82 agent-circuit-id
- Use the no version to disable inclusion of the suboption in the username.
- See include dhcp-option 82

include hostname

- Use to include the router hostname in the username that is dynamically created by JunosE subscriber management.
- Example
  host1(config-service-profile)#include hostname
- Use the no version to disable inclusion of the router hostname in the username.
- See include hostname

include ip-address

- Use to include the IP address in the username that is dynamically created by JunosE subscriber management.
- Example
  host1(config-service-profile)#include ip-address
- Use the no version to disable inclusion of the IP address in the username.
- See include ip-address

include mac-address

- Use to include the MAC address identifier in the username that is dynamically created by JunosE subscriber management.
- Example
  host1(config-service-profile)#include mac-address
- Use the no version to disable inclusion of the MAC address in the username.
- See include mac-address

include virtual-router-name

- Use to include the virtual router name in the username that is dynamically created by JunosE subscriber management.
- Example
  host1(config-service-profile)#include virtual-router-name
- Use the no version to disable inclusion of the virtual router name in the username.
- See include virtual-router-name

ip auto-configure ip-subscriber

- Use to configure an IP interface to support creation of dynamic subscriber interfaces. The specified IP interface is considered the primary interface.
- The router creates the required dynamic subscriber interfaces when the IP address is assigned to the associated subscriber. The address might be assigned by an external DHCP server, the DHCP local server, or the packet detect feature.
- Use the include-primary keyword to specify that the primary interface can be assigned to a subscriber. Use the exclude-primary keyword to specify that the primary interface cannot be used for subscribers. The primary interface is not assigned to a subscriber by default.
- You can issue this command from Interface Configuration mode, Subinterface Configuration mode, or Profile Configuration mode.
- Example
  host1(config-if)#ip auto-configure ip-subscriber include-primary
- Use the no version to disable creation of dynamic subscriber interfaces associated with this primary IP interface. Use the no version with the include-primary keyword to specify that the primary interface is not assigned to a subscriber. Use the no version with the exclude-primary keyword to specify that the primary interface is assigned to a subscriber.
- See ip auto-configure ip-subscriber

ip auto-detect ip-subscriber

- Use to set the router packet detect feature and specify that IP automatically detect packets that do not match any entries in the demultiplexer table. When an unmatched packet is detected, an event is generated that determines whether to create a dynamic subscriber interface or configure an existing interface.
- You can issue this command from Interface Configuration mode or Profile Configuration mode.
- Example
  host1(config-if)#ip auto-detect ip-subscriber
- Use the no version to restore the default, in which packet detection is disabled.
- See ip auto-detect ip-subscriber

ip destination-prefix

- Use to specify a destination address for a subscriber interface or for a primary IP interface.
- Use the deny keyword to drop all packets that match the command.
- On the ERX1440 Broadband Services Router or the E320 router, you can configure up to 1024 subnets for static subscriber interfaces per primary IP interface when each subnet has a variable network mask that is less than /32. The number of subnets identifying a single route (/32) is still limited by the global maximum of 16,000 hosts per line module.
- Example
  host1(config-if)#ip destination-prefix 10.0.0.0 255.0.0.0
- Use the no version to remove the association between the interface and the specified IP destination address and mask.
- See ip destination-prefix

ip inactivity-timer

- Use to configure the inactivity timer value for an IP interface.
- A dynamically created subscriber interface is deleted if it is inactive for a period longer than the inactivity timer value. IP polls the dynamic interface at the configured interval to determine whether the interface was active during the interval. Inactive interfaces are deleted only when the period of inactivity is equal to or greater than the configured value.

  For example, if you configure an inactivity timer of 15 minutes, IP polls the interface every 15 minutes. If a poll determines that the interface was last active 14 minutes earlier, the inactive time is less than the configured value so nothing happens. IP polls again 15 minutes later. If the interface is still inactive then the total period of inactivity is now 29 minutes. This is greater than the configured value and the interface is deleted.

- On static interfaces, the subscriber’s access route is removed when the inactivity timer is exceeded. When the subscriber logs back in, the timer is restarted.
- The timer value can in the range 0–65335 minutes. A timer value of 0 specifies that dynamically created subscriber interfaces are never deleted by the inactivity timer.
- Example
  host1(config-if)#ip inactivity-timer 100
- Use the no version to restore the default, in which inactivity timer feature is disabled.
- See ip inactivity-timer

ip re-authenticate-auto-detect ip-subscriber

- Use to re-authenticate the auto-detected subscribers or Dynamic Subscriber Interfaces (DSIs) created on static and dynamic primary IP interfaces, using the DHCP options when the DHCP external application manages the DSIs following a cold boot. The no version negates the command or restores the defaults.
- You can issue this command from Interface Configuration mode or Profile Configuration mode.
- Example
  host1(config-if)#ip re-authenticate-auto-detect ip-subscriber
- Use the no version negate the command or restore the defaults.

ip route-map ip-subscriber

- Use to configure an interface to perform route-map processing, and to specify the route map that is applied to the IP interface subscriber. If no route map is specified, then all packets trigger the creation of a dynamic subscriber interface.
- You can issue this command from Interface Configuration mode or Profile Configuration mode.
- Example
  host1(config-if)#ip route-map ip-subscriber bostonRouteMap
- Use the no version to delete the route map.
- See ip route-map ip-subscriber

ip service-profile

- Use to specify a service profile name and to enter IP Service Profile Configuration mode. Service profiles contain user and password information, and are used in route maps for subscriber management and to authenticate subscribers with RADIUS.
- You can specify a service profile name with up to 32 ASCII characters.
- To use the subscriber management application to configure IP subscribers on dynamic bridged Ethernet interfaces to support RADIUS authentication, you can create an IP service profile and assign it to a dynamic bridged Ethernet interface profile. If your router is running stateful SRP switchover (high availability), using an IP service profile to configure subscriber authentication is preferable to using either the subscriber command or the atm atm1483 subscriber command because these commands can suspend stateful SRP switchover on the router or prevent it from becoming active.

  For more information, see the Authenticating Subscribers on Dynamic Bridged Ethernet over Static ATM Interfaces section or the Authenticating Subscribers on Dynamic Bridged Ethernet over Dynamic ATM Interfaces section in JunosE Link Layer Configuration Guide.

- Example
  host1(config)#ip service-profile class1Service host1(config-service-profile)#
- Use the no version to delete the service profile.
- See ip service-profile

ip source-prefix

- Use to specify a source address for a subscriber interface.
- Use the deny keyword to drop all packets that match the command.
- On the ERX1440 router or the E320 router, you can configure up to 1024 subnets for static subscriber interfaces per primary IP interface when each subnet has a variable network mask that is less than /32. The number of subnets identifying a single route (/32) is still limited by the global maximum of 16,000 hosts per line module.
- Example
  host1(config-if)#ip source-prefix 10.0.0.0 255.0.0.0
- Use the no version to remove the association between the interface and the specified IP source address and mask.
- See ip source-prefix

ip use-framed-routes ip-subscriber

- Use to configure a static primary IP interface to use framed routes as source IP addresses when creating dynamic subscriber interfaces. The router uses the Framed-Route RADIUS attribute [22] sent in Access-Accept messages to apply framed routes to subscriber interfaces associated with the primary interface.
- Example
  host1(config-if)#ip use-framed-routes ip-subscriber
- Use the no version to disable the use of framed routes when creating dynamic subscriber interfaces associated with this primary IP interface.
- See ip use-framed-routes ip-subscriber

password

- Use to specify the password for an IP service profile. The password is used as the dynamically created password by JunosE subscriber management.
- You can specify a password with up to 32 ASCII characters.
- Example
  host1(config-service-profile)#password mypassword
- Use the no version to remove the password from the IP service profile.
- See password

set ip interface-profile

- Use to specify a dynamic subscriber interface profile that is used in the route map.
- Example
  host1(config)#route-map mapForEPort host1(config-route-map)#set ip interface-profile disableUser
- Use the no version to delete the interface profile from the route map.
- See set ip interface-profile

set ip service-profile

- Use to specify the name of a subscriber’s service profile that is used in the route map.
- You can specify a service profile name with up to 32 ASCII characters.
- Example
  host1(config-route-map)#set ip service-profile yourServiceProfile
- Use the no version to remove the service profile from the route map.
- See set ip service-profile

set ip source-prefix

- Use to specify a source address range to be inserted into a specific interface, and the action to take with the range.
  - deny—Drop addresses that appear in the source address range
  - primary—Associate the source prefix with the primary IP interface
- Example
  host1(config-route-map)#set ip source-prefix 10.10.30.0 255.255.255.0 primary
- Use the no version to remove the source address range from the route map.
- See set ip source-prefix

user-name

- Use to specify the username for an IP service profile. The username is used as the dynamically created username by JunosE subscriber management.
- You can specify a username with up to 32 ASCII characters.
- Example
  host1(config-service-profile)#user-name westford211
- Use the no version to remove the user name from the IP service profile.
- See user-name

user-prefix

- Use to specify a user prefix for an IP service profile.
- This command appends the user prefix to the username that is dynamically created by JunosE subscriber management.
- Example
  host1(config-service-profile)#user-prefix xyz.atl
- Use the no version to remove the user prefix from the IP service profile.
- See user-prefix

vlan service-profile

- Use to assign an IP service profile to a VLAN subinterface. Service profiles contain user and password information, and are used in route maps for subscriber management and to authenticate subscribers with RADIUS.
- You can specify a service profile name with up to 32 ASCII characters.
- Example
  host1(config-profile)#vlan service-profile vlanClass1Service host1(config-profile)#
- Use the no version to remove the service profile from the VLAN subinterface.
- See vlan service-profile