RE: [Devmon] TABLE: Order of data shown

[Aiello, S. \(G. C. consultant\) <ste...@ge...>]

That helps things tremendously.

> -----Original Message-----
> From: dev...@li...=20
> [mailto:dev...@li...] On Behalf=20
> Of Schwimmer, Eric E *HS
> Sent: Tuesday, May 23, 2006 2:42 PM
> To: dev...@li...
> Subject: RE: [Devmon] TABLE: Order of data shown
>=20
>=20
>=20
> Since they are non numeric, they aren't sorted, since that=20
> causes some "non-numeric value in sort" problems, though.
>=20
> However, you might want to try this:  Assuming you are=20
> running 0.2.2, try changing line 2071 of dm_tests.pm from:
>=20
> @table_leaves =3D keys %{$oids->{$pri}{'val'}};
>=20
> to:
>=20
> @table_leaves =3D sort keys %{$oids->{$pri}{'val'}};
>=20
> Let me know if that makes it better.
>=20
> -Eric
>=20
> > -----Original Message-----
> > From: dev...@li...
> > [mailto:dev...@li...] On Behalf=20
> > Of Aiello, Steve (GE, Corporate, consultant)
> > Sent: Tuesday, May 23, 2006 9:22 AM
> > To: dev...@li...
> > Subject: RE: [Devmon] TABLE: Order of data shown
> >=20
> > So my issues stems from the fact that my repeating data
> > primary alias is
> > returning "1.1, 1.2, 1.3 ... 2.1, 2.2, 2.3 ..." , and I think=20
> > devmon can
> > only handle when the return data return from primary repeater is
> > "1,2,3,4,5". Is this correct ?
> >=20
> > > -----Original Message-----
> > > From: dev...@li...
> > > [mailto:dev...@li...] On Behalf=20
> > > Of Aiello, Steve (GE, Corporate, consultant)
> > > Sent: Friday, May 19, 2006 4:30 PM
> > > To: dev...@li...
> > > Subject: RE: [Devmon] TABLE: Order of data shown
> > >=20
> > >=20
> > > Using the snmpwalk tool on .1.3.6.1.4.1.232.2.2.4.5.1.2 I
> > > see: SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.1.1 =3D INTEGER: 1=20
> > > SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.1.2 =3D INTEGER: 2=20
> > > SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.1.3 =3D INTEGER: 3=20
> > > SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.1.4 =3D INTEGER: 4=20
> > > SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.1.5 =3D INTEGER: 5=20
> > > SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.1.6 =3D INTEGER: 6=20
> > > SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.1.7 =3D INTEGER: 7=20
> > > SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.1.8 =3D INTEGER: 8=20
> > > SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.2.1 =3D INTEGER: 1=20
> > > SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.2.2 =3D INTEGER: 2=20
> > > SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.2.3 =3D INTEGER: 3=20
> > > SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.2.4 =3D INTEGER: 4=20
> > > SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.2.5 =3D INTEGER: 5=20
> > > SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.2.6 =3D INTEGER: 6=20
> > > SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.2.7 =3D INTEGER: 7=20
> > > SNMPv2-SMI::enterprises.232.2.2.4.5.1.2.2.8 =3D INTEGER: 8=20
> > > (truncated, you get the jist)
> > >=20
> > > My report looks like this tho:
> > > Memory:
> > > ID	Board	Type	Size	Speed	Technology=09
> ECCStatus
> > > 8	1	DIMM	0	0	Synchronous	NonECC
> > > 6	5	DIMM	0	0	Synchronous	NonECC
> > > 8	5	DIMM	0	0	Synchronous	NonECC
> > > 5	3	DIMM	0	0	Synchronous	NonECC
> > > 7	3	DIMM	0	0	Synchronous	NonECC
> > > 2	2	DIMM	524288	133	Synchronous	NonECC
> > > 3	2	DIMM	2097152	133	Synchronous	NonECC
> > > 2	5	DIMM	524288	133	Synchronous	NonECC
> > > 4	5	DIMM	2097152	133	Synchronous	NonECC
> > > 7	1	DIMM	0	0	Synchronous	NonECC
> > > 1	4	DIMM	524288	133	Synchronous	NonECC
> > > (truncated too)
> > >=20
> > >=20
> > >=20
> > > Oh wait I think I see my problem...  when walking on the oid
> > > I am getting more that one node (i.e. .1 .2 .3 .4 .5) I am=20
> > > getting .1.1 .1.2 .1.3 ...... .2.1 .2.2 .2.3 ......  More=20
> > > like I need to nest a table in a table....
> > >=20