I am at a loss on how to produce an LLD for a abse OID that has the index embedded in the middle of the OID, and then has to also look for a second OID for a string value.
Any help or suggestions will be appreciated.
i have a format like this:
.1.3.6.1.4.1.29631.2.2.0.256.<counterid>.1.0-->name of counter
.1.3.6.1.4.1.29631.2.2.0.256.<counterid>.2.0-->device name, if it is a platform counter it is empty. if it is present, is specific to this device only.
.1.3.6.1.4.1.29631.2.2.0.256.<counterid>.6.0 -->counter value (this is wat is required to graph and capture per item)
I have to use iterative logic somehow, and first get all the counterids and names if present, then discover the items against them.
my normal logic of getting the base oid and running that against an index does not apply here.
normally i will discover the name of the counter, and then just run discovery it against a name.
Any help or suggestions will be appreciated.
i have a format like this:
.1.3.6.1.4.1.29631.2.2.0.256.<counterid>.1.0-->name of counter
.1.3.6.1.4.1.29631.2.2.0.256.<counterid>.2.0-->device name, if it is a platform counter it is empty. if it is present, is specific to this device only.
.1.3.6.1.4.1.29631.2.2.0.256.<counterid>.6.0 -->counter value (this is wat is required to graph and capture per item)
I have to use iterative logic somehow, and first get all the counterids and names if present, then discover the items against them.
my normal logic of getting the base oid and running that against an index does not apply here.
normally i will discover the name of the counter, and then just run discovery it against a name.
, I think you'll need to discover this using a custom LLD with an external script.
Comment