Re: [nv-l] NMAVAILABILITY and decoding availability data files

[Leslie Clark <lclark@us.ibm.com>]

That should be the IP address in decimal
form. An IP address is really an unsigned 32-bit integer.
Use division and the modulo function
to break it down. 
I think these numbers are right, I've
only worked it in the opposite direction.
The leftmost octet is the whole number
divided by 16,777,215
The second octet is the remainder of
that, divided by 65,535.
The third octet is the remainder of
that, divided by 255.
The fourth octet is the remainder of
that. 

So I think that means that your 167772351
is 10.0.0.201. Does that make sense? I trust someone to correct my math
if it is wrong. 

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit

Jane Curry <jane.curry@skills-1st.co.uk>
Sent by: owner-nv-l@lists.us.ibm.com

01/30/2005 07:50 AM

Please respond to
nv-l

To	NetView mailing list <nv-l@lists.us.ibm.com>
cc
Subject	[nv-l] NMAVAILABILITY and decoding availability data files

I am interested in getting availability data - simple
node/interface - 
how long has an element been down.  There is obviously no MIB variable
that will give you this.

On way is to process trapd.log looking for Node / Interface Up/Down 
events and I'm sure some people have done this (anyone willing to 
contribute such a script to the NetView Tivoli User Group website????).

However, if you set the environment variable NMAVAILABILITY=True then 
you get daily files created in /usr/OV/databases with names in the form
availData_yyyymmdd.  These files were originally then fed into Tivoli
Decision Support and now are destined for Data Warehouse.  I don't
need 
all the functionality of these performance reporting programs - I just
want to make sense of the availability files.

Looking at the files, there seem to be 3 fields such as:
167772351    -1  1107083385
167772351     1   1107083647

The last field is time since the epoch.  The 1 / -1 seems to represent
up/down, but how do I code the first field which obviously refers to the
node / interface in question???  I have a suspicion that the first
digit 
is 1 for a node and 2 for an interface - other than that, I have to 
assume that there is some sort of translation from the NetView object id
to the rest of that first entry.  I've never seen this file documented
anywhere (but maybe I've just failed to find it?).  Anyone know how
to 
decode this??  It seems a shame to write my own trapd.log processing
script when NetView obviously already has a good mechanism to generate
availability data files.

Cheers,
Jane

-- 
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2005 Jane Curry <jane.curry@skills-1st.co.uk>.  All
rights reserved.