You configure how the username is formed. The username serves as the username for all static subscribers that are created and is included in the Access-Request message sent to AAA to authenticate all static subscribers. This value can be overridden for a group of static subscribers when a different username is configured for that group.
The username must include at least one of the five possible elements. The value of each element is concatenated in a specific order; the resulting string is the username. If you specify their inclusion, the interface name, logical system name, and routing instance name are derived from the configuration context. The elements are ordered as follows:
user-prefix.interface.logical-system-name.routing-instance-name@domain-name
To configure the username for all static subscribers:
- [edit system services static-subscribers authentication
username-include]
- user@host# set user-prefix Building5
- [edit system services static-subscribers authentication
username-include]
- user@host# set interface
- [edit system services static-subscribers authentication
username-include]
- user@host# set logical-system-name
- [edit system services static-subscribers authentication
username-include]
- user@host# set routing-instance-name
- [edit system services static-subscribers authentication
username-include]
- user@host# set domain-name campus.example.com
Configured in the default logical system and master routing instance for interface ge-0/1/1.100, this sample configuration generates the following username:
Building5.ge-0-1-1-100.default.master.campus.example.com