Filter
Top Products
8-5
User Guide for Resource Manager Essentials 4.1
OL-11714-01
Chapter 8 Archiving Configurations and Managing Them Using Archive Management
Preparing to Use the Archive Management
“Password: ”, “password: ”, “passwd: ”,”Password:” , “password:” , “passwd:”
• Content Networking—Content Engine
“Username: ” ,”login: ”
“Password: ”
• Storage Networking—MDS Devices
“Username:”, “Username: ”
“Password:”, “Password: ”
Note If you enabled TACACS for a device and configured custom TACACS login and passwords prompts, you
may experience Telnet problems, since RME may not recognize the prompts. To make your prompts
recognizable, you must edit the TacacsPrompts.ini file. See the procedure given in the Handling Custom
Telnet Prompts section of the User Guide for Common Services.
Modifying Device Configurations
To enable the configuration archive to gather the configurations, modify the device configurations for
the following:
• Enabling rcp
• Enabling scp
• Enabling https
• Configuring Devices to Send Syslogs
Enabling rcp
To enable the configuration archive to gather the configurations using the rcp protocol, modify your
device configurations.
Make sure the devices are rcp-enabled by entering the following commands in the device configurations:
# ip rcmd rcp-enable
# ip rcmd remote-host local_username {ip-address | host} remote_username [enable]
Where ip_address | host is the IP address/hostname of the machine where RME is installed.
Alternatively, you can enter the hostname instead of the IP address. The default remote_username and
local_username are
cwuser.
Disable the DNS security check for rcp if your RME server and devices are not registered with the DNS
server. To do this, use the command,
no ip rcmd domain-lookup for rcp to fetch the device configuration.
Enabling scp
To enable the configuration archive to gather the configurations using the scp protocol, modify your
device configurations.
To configure local User name:
aaa new-model