Configuring Secure Domain Routers on Cisco IOS XR Software
How to Configure Secure Domain Routers
SMC-157
Cisco IOS XR System Management Configuration Guide
Configuring a Username and Password for a Non-Owner SDR
After you create an SDR, you can create a username and password on that SDR. When you assign root-lr
privileges to that username, the user can administer the non-owner SDR and create additional users if
necessary.
Note Only users with root-system privileges can access Administration modes to add or remove SDRs. SDR
users cannot add or remove SDRs.
To create a username and password for the new non-owner SDR.
1. On the owner SDR, enable admin plane authentication. This allows you to log in to the non-owner
SDR and create local usernames and passwords.
2. Log in to the non-owner SDR.
3. Configure a new username and password on the non-owner SDR. Assign the username to the root-lr
group to allow the creation of additional usernames on that SDR.
4. To verify the new username, log out and log back in to the non-owner SDR using the new username
and password.
5. Provide the username and password to the SDR user.
Complete the following steps to create usernames and passwords on a non-owner SDR.
SUMMARY STEPS
1. Connect a terminal to the console port of the DSC (DSDRSC of the owner SDR).
2. admin
3. configure
4. aaa authentication login remote local
Step4 end
or
commit
Example:
RP/0/RP0/CPU0:router (admin-config)# end
or
RP/0/RP0/CPU0:router(admin-config)# commit
Saves configuration changes.
When you issue the end command, the system prompts
you to commit changes:
Uncommitted changes found. Commit them?
Entering yes saves configuration changes to the
running configuration file, exits the configuration
session, and returns the router to EXEC mode.
Entering no exits the configuration session and
returns the router to EXEC mode without
committing the configuration changes.
Entering cancel leaves the user in the same
command mode without committing the
configuration changes.
Use the commit command to save the configuration
changes to the running configuration file and remain
within the configuration session.
Command or Action Purpose