Device Configuration Imports (DCI)
DCI lets you generate a network model by importing configuration data for
- Juniper JUNOS
- Cisco IOS
- Cisco PIX firewalls
- Cisco Catalyst switches
DCI uses the data in the configuration files to set the NetPlanner attributes that control routing and switching behavior, including
-
System information including DRAM, NVRAM, Flash RAM, operating system type and version, serial number, and module name
Note: Memory information is parsed from the “show version” command. Currently only Cisco devices provide this information through “show version”. Therefore, non-Cisco devices have the memory attributes set to “Unknown” during import.
-
Connections, data rates, and interfaces (including PVCs, aggregate interfaces, loopback interfaces, tunnel interfaces, VLANs, and sub-interfaces)
-
Protocol information for IP, IP Multicast, BGP, EIGRP, OSPF, RIP (versions 1 and 2), IGRP, IPX, Frame Relay, ATM, RSRB, DLSW, NAT, QoS, and VPLS
-
ACLs (access control lists), route maps, and Juniper firewall filters
-
Static routing, default routing, policy routing, and route redistribution
-
VLAN, VLAN trunking protocol (vtp), spanning tree, and bridge configuration information
-
Cisco security: AAA, TACACS+, Radius, Kerberos
DCI Import Topics
The DCI Import section contains the following subsections:
- Supported Commands and Features
- General Workflow for Device Configuration Imports
- Preparing for the Import
- Performing an Import with DCI
- Using the Interface Assistant
- Viewing the Import Summary Report
- Saving Changes from the Interface Assistant to a Model Assistant File
- Troubleshooting the Import
- After the Import
Supported Commands and Features
During import, NetPlanner considers and parses device configurations and translates these into model attributes. Currently, not all specific configuration commands and values are supported.
For information on the commands and features that are supported, see the Riverbed Support website.