File Import Format

There are two methods of importing devices into your Cisco Resource Manager network inventory:

Comma Separated Values (CSV) file
Device Integration File (DIF)

For ease of use, Cisco strongly recommends the CSV format. Samples of each type of file are in this appendix. The information in each file type must be presented in the order shown.

Comma-Separated Values (CSV) File Sample

You can create a CSV file to import devices. After you create the CSV file, you can import it using the File Import task.

The CSV format provides the following device information:

Full device name or IP address (required)
RO community string (required)
RW community string (optional)
Serial Number (optional)
User Field 1 (optional)
User Field 2 (optional)
User Field 3 (optional)
User Field 4 (optional)
Telnet, local, and authentication passwords and usernames (optional)

Following is a sample CSV-formatted file.

;  This file was manually generated as a sample.
;
# cisco Systems NM data import, source = Hand edit; Foo = bar; Version = 1.0; Type = Csv
cisco Systems NM data import, source = Hand edit; Version = 1.0; Type = Csv
;
; Here are the columns of the table.
;
;Col# = 1; Name = Full device name or IP address; 
;Col# = 2; Name = RO community string; 
;Col# = 3; Name = RW community string; 
;Col# = 4; Name = Serial Number; 
;Col# = 5; Name = User Field 1; 
;Col# = 6; Name = User Field 2; 
;Col# = 7; Name = User Field 3; 
;Col# = 8; Name = User Field 4; 
;
; Here are the rows of data.
;
national.cisco.com,public,private,,
enm-2501.cisco.com,"Not so, "" public as, thought",private,sn2501,
enm-2502.cisco.com,public,"private",sn2502,
enm-2503.cisco.com,public,private,sn2503,""
enm-2504.cisco.com,public,private,sn2504,
enm-2505.cisco.com,public,private,sn2505,
enm-2507.cisco.com,public,private,sn2507,
enm-2509.cisco.com,public,private,sn2509,
enm-2510.cisco.com,public,private,sn2510,
enm-2511.cisco.com,public,private,sn2511,
enm-2512.cisco.com,public,private,sn2512,
enm-2513.cisco.com,public,private,sn2513,
enm-2514.cisco.com,public,private,sn2514,
enm-2515.cisco.com,public,private,sn2515,
enm-2516.cisco.com,public,private,sn2516,
enm-4000.cisco.com,public,private,,Big Boys
enm-4500.cisco.com,public,private,,Big Boys
enm-7000.cisco.com,public,private,,Big Boys
enm-7010.cisco.com,public,private,,Big Boys
nm2517.cisco.com,public,private,,,nm 25xx
nm2518.cisco.com,public,private,,,nm 25xx
nm2520.cisco.com,public,private,,,nm 25xx
nm2521.cisco.com,public,private,,,nm 25xx
nm2522.cisco.com,public,private,,,nm 25xx
nm2523.cisco.com,public,private,,,nm 25xx
nm2524.cisco.com,public,private,,,nm 25xx
nm2525.cisco.com,public,private,,,nm 25xx
nm4700.cisco.com,public,private,,4700 Field1,,4700 Field3,4700 Field4
nm7206.cisco.com,public,private,,
nm7505.cisco.com,public,private,,,,,7505 Field 4
nm7507.cisco.com,public,private,,
nm7513.cisco.com,public,private,,
nm1200.cisco.com,public,private,,
nm2900.cisco.com,public,private,,
nm3000.cisco.com,public,private,,
nm5000.cisco.com,public,private,,
armory.cisco.com,public,private,,
beasley.cisco.com,public,private,,
boattail.cisco.com,public,private,,
corgi.cisco.com,public,private,,
heckler.cisco.com,public,private,,
hornady.cisco.com,public,private,,
jefferson.cisco.com,public,private,,
springfield.cisco.com,public,private,,
yoda.cisco.com,public,private,,
smith.cisco.com,public,private,,
nova.cisco.com,public,private,,
akita.cisco.com,public,private,,
pitbull.cisco.com,public,private,,
uzo.cisco.com,public,private,,
anaconda.cisco.com,public,private,,
kleck.cisco.com,public,private,,
mallard.cisco.com,public,private,,
browning.cisco.com,public,private,,
seuter.cisco.com,public,private,,
bugfree.cisco.com,public,private,,
172.18.25.241,public,public,,

Device Integration File (DIF) Sample

You can create a DIF to import devices. After you create the DIF, you can import it using the File Import task.

The DIF is currently encoded in the ISO Latin-1 character set using an extended BNF notation described in the Resource Manager online help. The DIF specifies the following characteristics of each device:

Generic format
Generic attributes
Header
Table area
Device table
Group table
User annotation table

Following is a sample DIF, incorporating these characteristics. The sample file was imported from CiscoWorks.

First, the DIF is defined.

cisco Systems NM data import, source=CW; Version = 1.0;

The device table is defined.

Table name = Device basic inventory; Version = 1.0; Column count = 7; Separator = |;

Columns for the device table are defined.

Col# = 1; Name = Row#;
Col# = 2; Name = Device name;
Col# = 3; Name = Domain;
Col# = 4; Name = RO community string;
Col# = 5; Name = RW community string;
Col# = 6; Name = Telnet password;
Col# = 7; Name = Enable password;

Rows of data for the device table are defined.

000001|111.22.333.4||||fooey|more
000002|landfall|cisco.com|public|private||
000003|yet_another_router||read|write|mommy|whoKnows
000004|Pinpointed_router|organized.org|read|write|thickAsABrick|clearAsMud
999999

An administrative domain table is defined.

Table name = Device grouping; Version = 1.0;
Column count = 4; Separator = $

Columns for the domains table are defined.

Col# = 1; Name = Row#
Col# = 2; Name = Group
Col# = 3; Name = Device name
Col# = 4; Name = Domain

Rows of data for the domain table are defined.

000001$CW_World$111.22.333.4$
000002$CW_World$yet_another_router$
000003$CW_World$landfall$cisco.com$
000004$CW_Smaller than world$yet_another_router$
999999

The user annotation table is defined.

Table name = Device annotations; Version = 1.0; Column count = 7; Separator = $

Columns for the annotation table are defined.

Col# = 1; Name = Row#
Col# = 2; Name = Device name
Col# = 3; Name = Domain
Col# = 4; Name = Annotation 1
Col# = 5; Name = Annotation 2
Col# = 6; Name = Annotation 3
Col# = 7; Name = Annotation 4

Rows of data for the annotations table are defined (the first annotation holds location; the second annotation holds the contact name).

000001$111.22.333.4$$San Jose: Bldg F$Joe Smith
000002$yet_another_router$$San Jose: Bldg A$Jill Jones
000003$landfall$cisco.com$San Jose: Bldg F$Joe Smith
000004$yet_another_router$Santa Clara: Bldg 1$George Black
999999

The serial number table is defined.

Table name = Device serial numbers; Version = 1.0; Column count = 4;
Separator = $
Col# = 1; Name = Row#
Col# = 2; Name = Device name
Col# = 3; Name = Domain
Col# = 4; Name = Serial number

The RCP table is defined.

Table name = Device Rcp access data; Version = 1.0; Column count = 5;
Separator = $
Col# = 1; Name = Row#
Col# = 2; Name = Device name
Col# = 3; Name = Domain
Col# = 4; Name = Rcp user
Col# = 5; Name = Rcp password

RCP data is provided.

000001$111.22.333.4$$jsmith$1dasf8
000002$yet_another_router$$jjones$1ruf7dhgd
000003$landfall$cisco.com$jsmith$1dasf8
000004$yet_another_router$gblack$7fghs4
999999

The TACACS table is defined.

Table name = Device Tacacs access data; Version = 1.0; Column count = 7;
Separator = $
Col# = 1; Name = Row#
Col# = 2; Name = Device name
Col# = 3; Name = Domain
Col# = 4; Name = Tacacs user
Col# = 5; Name = Tacacs password
Col# = 6; Name = Tacacs Enable User;
Col# = 7; Name = Tacacs Enable Password;

TACACS data is provided.

000001$111.22.333.4$$jsmith$3dfg6$stillJsmith$butNot3dfg6
000002$yet_another_router$$jjones$adf6789
000003$landfall$cisco.com$jsmith$3dfg6
000004$yet_another_router$gblack$jh3df7
999999

Table of Contents