Re: 'Inter-Tables indexing' and perl

Quoting Dave Shield <[email protected]>:

>> # 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.

Is there any way I can modify the index in such a way
that only need one table? Making more than one table
for that will complicate the next table:

----- s n i p -----
# Statistic counters index
OID_BASE.5.1.1.1 1
OID_BASE.5.1.1.2 2
OID_BASE.5.1.1.3 3
OID_BASE.5.1.1.4 4
OID_BASE.5.1.1.5 5
# Statistic counters name
OID_BASE.5.1.2.1 start_date
OID_BASE.5.1.2.2 end_date
OID_BASE.5.1.2.3 duration
OID_BASE.5.1.2.4 files
OID_BASE.5.1.2.5 bytes
# Statistic counters - job ID
OID_BASE.5.1.3.1.1.1 Client1_System.2005-09-13_01.05.06
OID_BASE.5.1.3.1.1.2 Client1_System.2005-09-14_01.05.06
OID_BASE.5.1.3.2.1.1 Client2_System.2005-09-13_01.05.05
OID_BASE.5.1.3.2.1.2 Client2_System.2005-09-14_01.05.05
# Statitistc counters - start date
OID_BASE.5.1.4.1.1.1 20050913045016Z
OID_BASE.5.1.4.1.1.2 20050914010954Z
OID_BASE.5.1.4.2.1.1 20050913030645Z
OID_BASE.5.1.4.2.1.2 20050914010804Z
# Statitistc counters - end date
OID_BASE.5.1.5.1.1.1 20050913053919Z
OID_BASE.5.1.5.1.1.2 20050914011728Z
OID_BASE.5.1.5.2.1.1 20050913045016Z
OID_BASE.5.1.5.2.1.2 20050914010954Z
# [etc, etc for the rest of the Statistic counters name]
----- s n i p -----

Here, the statsTable is in the format:

OID_BASE.statsTable.statsEntry.CounterType.ClientID.JobJame.jobID


There's an 'infinite' number of Job ID's and corresponding
counters... Making 'infinite' number of tables will be...
UGGLY! :)


In LDAP (which I now know better than SQL), I would have
written the whole thing as:
----- s n i p -----
+- client1
   +- Client1_System
      +- Client1_System.2005-09-13_01.05.06
         +- [start date]
         +- [end date]
         +- [duration]
         +- [files]
         +- [bytes]
      +- Client1_System.2005-09-14_01.05.06
         +- [start date]
         +- [end date]
         +- [duration]
         +- [files]
         +- [bytes]
[etc, etc for each client, each job name and each job ID]
----- s n i p -----

But how would I do that in SNMP?
-- 
KGB iodine Marxist PLO spy congress FSF subway cryptographic NORAD
Panama NSA colonel supercomputer CIA
[See http://www.aclu.org/echelonwatch/index.html for more about this]
[Or http://www.europarl.eu.int/tempcom/echelon/pdf/rapport_echelon_en.pdf]
If neither of these works, try http://www.aclu.org and search for echelon.


-------------------------------------------------------
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