Pre-Collected Device Configuration Files
  
Pre-Collected Device Configuration Files
This section describes how to import previously collected device configuration files and other CLI device data into NetIM.
Config files and other CLI data files must meet certain criteria for NetIM to recognize them.
Links are not created automatically when device data is imported. For more information about how link and connection inference uses device data stored in the NetIM database to infer connections, see “How NetIM Infers Links and Connections".
Input File Criteria for CLI Files
When input files are supplied, the files contain required fields needed for NetIM to recognize and import supported formats. When you supply CLI data files that you have obtained using another mechanism—a custom archiving environment, script, or network management system—you must ensure that the input files meet the following criteria:
• The output of each show command must be stored in a separate file with the exception of version and memory data which may be stored in the same file.
• Each file must begin or end with a device prompt.
• For a file to be parsed and imported into NetIM, it must be obtained by executing a configuration command supported by NetIM for that data type and vendor. See System-Defined Device Drivers for the supported commands for each system-defined device driver. Other commands can be collected and archived, but will not be imported.
Short versions of commands are not supported.
• Each file must contain the device console (“show”) command that was used to collect the output.
• Files for the same device must use the same root filename. As an example, an appropriate naming scheme for CLI data for a device named routerA is: routerA.cfg, routerA.cdp, routerA.interface, etc.
A file named routerA.lab.opnet.com.version will not merge with a file name routerA.cfg.
• Each file must have a specific file extension to designate the file type.
The following table lists the default CLI command types for NetIM and provides the required file extension for each. You can add your own command types using the “Command Type Manager". If you add a command type, the file extension for input files you supply must match the file extension defined in the command type manager.
Data Type
File Extension
Alarms
alarms
All Contexts Configuration
allContexts
APS
aps
ARP Table
arp
Asymmetric Route
asymRoute
BGP RIB
bgpRib
CAM Table
cam
CDP
cdp
CheckPoint Rules
rules.C
CheckPoint Objects
objects.C
Configuration
cfg
FEX
fex
Frame-Relay Map
frMap
HSRP Standby
standby
HTTP
http
ifIndex
ifIndex
IGMP Group
igmpGroup
Interface
interface
IP Route
ipRoute
IPv6 Interface
ipv6Interface
ipv6Route
ipv6Route
LACP
lacp
LLDP
lldp
Module
module
MPLS TE Tunnels
mplstetunnels
Multicast route
multicastRoute
Next Hop
nextHop
Objects.C
objects.C
Redundancy
redundancy
Rules.C
rules.C
SRP
srp
Startup Configuration
startup
STP
stp
Trace Route
trc
Trunk
trunk
Version
version
VLAN
vlan
VTP
vtp
WAN Optimization Neighbors
wanoptNeighbors
WAN Optimization Peers
wanoptPeers
Pre-Collected Files
If you have a custom archiving environment or other source of device configuration files, you may choose to run a cron job or write your own program to copy input files to the appropriate location on NetIM core, making them available for import.
Requirements for Pre-Collected Files Import
The Pre-Collected Files Adapter has the following requirements:
• Input files must be placed in the following input file directory:
/data1/riverbed/NetIM/op_admin/tmp/vne/Input
Files may be placed in subdirectories (for example, by device or by type) within the specified input directory, but this is not required. For example you may put all of the configuration files in a subdirectory named Input/Configs.
• Files must meet certain criteria, described in “Input File Criteria for CLI Files".
Perform the following procedure to import pre-collected device configuration files using the Pre-Collected Files Adapter.
Importing Pre-Collected Device Configuration Files
1. Ensure that input files meet “Input File Criteria for CLI Files".
2. Place the files to be imported in the input directory. The default input directory for the Pre-Collected Files Adapter is /data1/riverbed/NetIM/op_admin/tmp/vne/Input.
You must copy new input files into this directory on a regular basis to keep NetIM up to date.
During the scheduled collection (set in the Basic Setup wizard), NetIM will import your pre-collected configuration files.