Input file criteria for CLI files
When input files are supplied by Device Config File Collection or a collection adapter that integrates with a network management system (for example, Opsware NAS or Alcatel 5620 SAM-O), the files contain required fields needed for the CLI Data Import adapters 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 for which NetIM does not provide a collection adapter—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
Configuring 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, and so on.
A file named routerA.lab.opnet.com.version will not merge with a filename 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 |
Traceroute | trc |
Trace Route | trc |
Trunk | trunk |
Version | version |
VLAN | vlan |
VTP | vtp |
WAN Optimization Neighbors | wanoptNeighbors |
WAN Optimization Peers | wanoptPeers |