Re: 'Inter-Tables indexing' and perl

On Thu, 2005-10-13 at 10:17 +0200, Turbo Fredriksson wrote:

> Output from 'snmpwalk' (OID_BASE is a shorthand for the
> OID to the 'baculaStats' described below; '.1.3.6.1.4.1.8767.2.3'):
> ----- s n i p -----
> # Number of clients:
> OID_BASE.1.0 = 4
> # Client index:
> OID_BASE.4.1.1.1 = 1
> OID_BASE.4.1.1.2 = 2
> OID_BASE.4.1.1.3 = 3
> OID_BASE.4.1.1.4 = 4
> # Client names:
> OID_BASE.4.1.2.1 = client1
> OID_BASE.4.1.2.2 = client2
> OID_BASE.4.1.2.3 = client3
> OID_BASE.4.1.2.4 = client4

OK - so far.

> # Job names
> OID_BASE.4.1.3.1.1 = Client1_System

BZZZZ

The indexing of this table has suddenly changed. That's
not allowed.   Judging by the MIB definitions below, 
this entry (and the next few) should read

  OID_BASE.4.1.3.1 = Client1_System
  OID_BASE.4.1.3.2 = Client2_System
  OID_BASE.4.1.3.3 = Client3_System
  OID_BASE.4.1.3.4 = Client4_System


> OID_BASE.4.1.3.4.2 = Client4_Web
> OID_BASE.4.1.3.4.3 = Client4_Web_Stats
> OID_BASE.4.1.3.4.4 = Client4_Catalog
> OID_BASE.4.1.3.4.5 = Client4_Devel
> OID_BASE.4.1.3.4.6 = Client4_Homes
> OID_BASE.4.1.3.4.7 = Client4_Mail
> OID_BASE.4.1.3.4.8 = Client4_Old
> OID_BASE.4.1.3.4.9 = Client4_RestoreFiles

If you need to report several "JobName" values for
a single client, then this needs to be defined as
a *separate* table.  You can't shoehorn this into
the main 'baculaClientsTable'


Basic rule - all objects in a given table must use
exactly the same indexing structure.  If the indexing
is different, that means a different table.


Dave


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users