Router Management Center (MC)
Installation process

The Devices tab, shown in Figure is used to import and manage the inventory of routers to be configured using the Router MC.

  • Device hierarchy – Use this option to view the device hierarchy and to manage the routers within the hierarchy by creating device groups, moving or deleting devices/groups, editing router parameters, and adding unmanaged spokes.
  • Device import – Use this option to import the routers to be configured into Router MC, and to re-import routers when necessary.
  • Credentials – Use this option to edit router credentials or synchronize the credentials of multiple routers from a comma-separated value (CSV) file. Device credentials include the username, password, and enable password.

Use the options in the Configuration tab, shown in Figure to configure VPN and firewall settings and policies for deployment to the routers. Settings and policies can be configured globally for all routers, for groups of routers, or for individual routers. Select the configuration context using the Object Selector, shown in Figure along the left-hand side of the page.

Deployment of VPN and firewall configurations is always done within the context of a deployment job, shown in Figure . When a job is created, the routers or router groups to which the configurations are to be deployed are specified. Router MC translates the committed policy configurations for each router into CLI commands. These CLI commands can be previewed and deployed either directly to the routers in the network or to output files in a specified directory. The deployment tab offers the administrator the following options, shown in Figure .

The Reports tab, shown in Figure is used to view reports on various Router MC functions. This tab presents the following options:

  • Deployment – Use this option to view the deployment status of all managed routers.
  • Activities – Use this option to view the status of existing activities, including the objects locked by each activity. The Router MC uses a locking model, in which the objects for which policies are being defined and all their descendants in the object hierarchy are locked to other users until the activity is approved or deleted. This is important in large networks where several people have the authority to configure routers. It prevents a potential situation where two or more people are making configuration changes to the same objects at the same time.
  • Audit – Use this option to define a query to generate an audit log of user interaction with the Router MC that can include information about routers, activities, policies, deployments, and so forth.
  • Hub-Spoke Assignment – Use this option to generate a report that shows the primary and failover assignment of spokes to selected hubs, or to all hubs in the device hierarchy.

Administrators use the Admin tab, shown in Figure to define various Router MC application settings, and to define Auto Update Server (AUS) settings.

This tab presents the following options:

  • Application Settings – Use this option to define various general application settings, for example, activity and job approval settings, settings for historical jobs and activities, GRE routing range, and others.
  • Auto Update Server Settings – Use this option to define the AUS settings that enable the Router MC to communicate with AUS when managing routers with dynamic IP addresses.