nv-l
[Top] [All Lists]

Re: Slightly OT - CiscoWorks2000 and Netview

To: nv-l@lists.tivoli.com
Subject: Re: Slightly OT - CiscoWorks2000 and Netview
From: Kent_Allison@advantra.com.au
Date: Sun, 15 Jul 2001 09:16:29 +1000
Folks,


A thousand apologies for the garbage that got posted in my previous attempt
(I wont be a bad tradesman and try and blame for at I also use the
nvdbformat utility and a custom format file to pull all my Cisco devices
out of NetView (on Solaris) into a csv file which can then be very easily
used to import the devices into RME.  Passwords and community strings can
be a pain as mentioned, but if most of your devices have the same
configuration then using a csv file is probably quicker than adding them
via the GUI.



Here's a sample format file:



###########################################################

#

# NVDBFormat Sample Input File

# Advantra Pty. Ltd., 2001

#

# Usage:  nvdbformat -f <filename>

#

# This specific file would be processed by:

#

#        nvdbformat -f ciscoworks.format

#

###########################################################

#    Select rule(s):

#

#    Format:

#    -------

#    SELECTRULE:<OVW Field Name><RELATION><VALUE>

#

#       *or*

#

#    SELECTRULE:Collection=<VALUE>

#

#       *or*

#

#    SELECTRULE:SmartSet=<VALUE>

#

#    Relations:     =         EQUALS

#              !         DOES NOT EQUAL

#              ~         CONTAINS

#              ^         DOES NOT CONTAIN

#

#    Multiple SELECTRULES are combined with AND logic.

#

###########################################################

SELECTRULE:isNode=TRUE

SELECTRULE:vendor~cisco

SELECTFIELD:1:Object ID

SELECTFIELD:2:Selection Name

HEADER:;

HEADER:; This file is generated by the export utility

HEADER:; If you edit this file, be sure you know what you are doing

HEADER:;

HEADER:Cisco Systems NM data import, source = import utility; Version =
2.0; Type = Csv

HEADER:;

HEADER:; Here are the columns of the table.

HEADER:;   Columns 1 and 2 are required.

HEADER:;   Columns 3 through 19 are optional.

HEADER:; Col# = 1: Name (including domain or simply an IP)

HEADER:; Col# = 2: RO community string

HEADER:; Col# = 3: RW community string

HEADER:; Col# = 4: Serial Number

HEADER:; Col# = 5: User Field 1

HEADER:; Col# = 6: User Field 2

HEADER:; Col# = 7: User Field 3

HEADER:; Col# = 8: User Field 4

HEADER:; Col# = 9; Name = Telnet password

HEADER:; Col# = 10; Name = Enable password

HEADER:; Col# = 11; Name = Enable secret

HEADER:; Col# = 12; Name = Tacacs user

HEADER:; Col# = 13; Name = Tacacs password

HEADER:; Col# = 14; Name = Tacacs enable user

HEADER:; Col# = 15; Name = Tacacs enable password

HEADER:; Col# = 16; Name = Local user

HEADER:; Col# = 17; Name = Local password

HEADER:; Col# = 18; Name = Rcp user

HEADER:; Col# = 19; Name = Rcp password

HEADER:;

HEADER:; Here are the rows of data.

HEADER:;

OUTPUT:${2},public,private,,,,,,cisco,cisco,cisco,!{[NOVALUE]}!,!
{[NOVALUE]}!,!{[NOVALUE]}!,!{[NOVALUE]}!,password,password,!{[NOVALUE]}!,!
{[NOVALUE]}!




Note the fifth header line - it IS required.  The others can be got rid of.




Regards,
               Kent

Network Management Specialist
Phone: +61 2 988 25822  Fax: +61 2 988 25999
Mobile: +408 406 663
Notes:Kent Allison/AdvInt/Advantra@Advantra
Mailto:Kent_Allison@advantra.com.au


<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web