Cisco Cisco Network Services Manager 5.0 Referencia técnica

Page 13

OL-28510-02

Base Configuration

The devices that are managed by Network Services Manager need to have been configured in the

device stack and have certain standard base configurations applied to them. Device

configurations should be saved before Network Services Manager begins to automate tenant

activity configurations to provide a clean, unconfigured start state on the device.

Note

Network Services Manager does not save the configurations but instead keeps them in

running configuration. A good practice is to save the running configuration before

Network Services Manager begins to manage the device to avoid having tenant artifacts

saved on the devices.

Network Services Manager automates deploying tenant logical containers on a preconfigured

stack of equipment. It does not do bare-metal configuration.
The following sections capture the base configuration prerequisites that apply to each device.

Preserving Static Routes on Devices

Prerequisite

Enable the "shell" password-protected access by using the shell_enable command

as follows:

od-l1-dsc/admin# shell_enable

Enter a password for shell access :

Confirm the password again :

Info: Shell access password was set successfully. Use shell command to access

shell

od-l1-dsc/admin#

Known Issue

The controller, upon connecting to devices in the Router or Distribution switch role,

deletes static routes present in the devices' default VRF. If the device routing tables

are populated with routes that must remain untouched by the controller, create a

boilerplate for each device to preserve the desired routes. When static routes are added

manually to the routers, you must also configure new boilerplates on the controller to

ensure that it does not remove them.

The boilerplate configuration is stored on the controller at:

/etc/overdrive/controller/boilerplates.xml

A sample boilerplate that will preserve six different static routes on a router with IP address

10.17.217.98 would look like this:

<action>write-routes</action>

<property key="remoteLogin.targetAddress"

match="exactly">10.17.217.98</property>

</filter>