I've never had a problem with it. The danger is when you create the
field and give it flags, including Name (like IP Hostname and Selection
Name
have). A boolean field with the Locate flag is perfectly safe. Also
Stringtype
with Locate. If you always wanted to store accurate location and contact
information in the netview database, or maybe circuit numbers or something,
this is the way to do it. Got some spreadsheets laying around that can be
saved as comma-separated files? Suck them into Netview. If I wanted to
be sure about some of the other flags, like general and capability, I would
look in the online Programmer's Guide. The fields added by the nvdbimport
command on its own have no flags at all. Or so they told us.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
=================================================================
Ooh another cool trick I can really use.
However I wondered if it will cause a problem when I need to delete the
node?
I've seen posts about problems caused when trying to delete a node that has
non standard things added to it? Will this be a problem do you think?
John Creasey.
> -----Original Message-----
> From: owner-nv-l@tkg.com [mailto:owner-nv-l@tkg.com]On Behalf Of
> lclark@us.ibm.com
> Sent: Wednesday, 8 March 2000 22:52
> To: NV-L@tkg.com
> Subject: Re: [NV-L] Node Up/Down Traps
>
>
>
>
> The easiest way is to use the nvdbimport command. If you have
> a file that
> looks like this:
>
> IP Hostname,MaintnenanceTime
> ServerA,TRUE
> ServerB,TRUE
> ServerC,TRUE
>
> and run 'nvdbimport -f <name of this file>'
>
> then Netview will create the field on those nodes and set it
> to true. You
> could further
> automate the generation of that file by maintaining a
> list-type collection
> of the servers
> involved and use nvUtil in a script to generate the file used by
> nvdbimport. Remember
> that you will need to set the field to false later, so you
> will want to
> make two files while
> you are at it. See the man page for nvdbimport. There are a bunch of
> samples in
> /usr/OV/bin/nvdbtools. This is wonderful stuff!
>
> If you also want to be able to use the field for locating
> things, you need
> to define the field
> yourself and give it the Locate capability. Then nvdbimport
> will just use
> the one you
> made. The fields are in /usr/OV/fields/C. Make a file of your
> own in there,
> and copy
> a little stanza from one of the other files. You want to
> define a boolean
> field, and the
> only flag you need is Locate. After changes to fields you
> need to do the
> ovw -fields.
> Making fields is documented in the Programmer's Guide online manual.
>
> If you take this extra step, you will further be able to use
> the field to
> define a Collection
> that contains things for which MaintenanceTime is True. So if
> they are red
> ...etc.
>
> Cordially,
>
> Leslie A. Clark
> IBM Global Services - Systems Mgmt & Networking
> Detroit
> ====================================================================
>
> Leslie,
>
> I like the idea, but this means that I must create a field called :
> MaintWindow
> (Or whatever) for the nodes in my Maintenance collection.
>
> How do I create this field?
>
> Regards
> Wouter de Bruin
> Network Management Consultant
> `Externe E-Mail wordt door DNB niet gebruikt voor het aangaan van
> verplichtingen`
>
> `Any e-mail messages from The Nederlandsche Bank are given in
> good faith
> but shall not be binding
> nor shall they be construed as constituting any obligation on
> the part of
> the Bank.`
>
>
> ______________________________________________________________
> ___________
>
> NV-L List information (unsubscribing, policies, posting,
> digest version,
> searchable archives): http://www.tkg.com/nv-l
>
_________________________________________________________________________
NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l
|