Re: [Devmon] Repeater table without primary column?

[Buchan M. <bg...@st...>]

On Monday, 19 December 2011 12:40:51 Thomas Kähn wrote:
> Hi Buchan,
> 
> On Mon, Dec 12, 2011 at 09:12:08AM +0100, Buchan Milne wrote:
> > On Thursday, 8 December 2011 18:56:41 Thomas K hn wrote:
> > > is it possible to use a repeater table when there is no primary column?
> > 
> > There is no real specefic requirement for a 'primary' OID besides
> > uniqueness.
> 
> thanks for your reply. The problem is, that my primary column isn't
> unique because it doesn't exist :-(

False ...

> I only have the data column in this table as seen in the output below.
> 
> The slot/port combination can only be deduced from the last three
> numbers in the OID.

Before I look at the MIB, from your explanation, the last three numbers should 
be accessible in devmon by using the INDEX operator (as the index of the SNMP 
table). If not, you aren't looking at an SNMP table.

> > > E.g. I want to monitor the PPP sessions on individual interfaces
> > > on a Juniper E320 BRAS system.
> > > However there is no ifName or ifIndex column in this table. Instead the
> > > the last three numbers in the returned OID is the interface name:
> > > 
> > > $ snmpwalk e320bras 1.3.6.1.4.1.4874.2.2.20.1.8.8
> > > SNMPv2-SMI::enterprises.4874.2.2.20.1.8.8.1.2.3.1.0.1 = Gauge32: 4928
> > > SNMPv2-SMI::enterprises.4874.2.2.20.1.8.8.1.2.3.1.0.2 = Gauge32: 3232

After looking for this MIB at mibdepot.com, it seems this 
(1.3.6.1.4.1.4874.2.2.20.1.8.8) is juniAaaSubscriberLocationSummaryTable, and 
each entry in the table has a juniAaaSubscriberLocationSummaryLocationIndex 
(1.3.6.1.4.1.4874.2.2.20.1.8.8.1.1) and juniAaaSubscriberLocationSummaryCount 
(1.3.6.1.4.1.4874.2.2.20.1.8.8.1.2).

If you can't get juniAaaSubscriberLocationSummaryLocationIndex, then you 
should use the INDEX operator on juniAaaSubscriberLocationSummaryCount.

Regards,
Buchan