On Mon, 9 Jul 2018 12:33:36 +0530 Thommandra wrote:
TG> > Configure can exclude entire MIBs, but not individual OIDs.
TG> > You can modify the code, but make sure you deal with get and
TG> > get-next properly.
TG>
TG> Even if we comment/modify the code for individual OIDs, we
TG> cannot skip OIDs
Thanks Robert.
Response in-line.
>
> Configure can exclude entire MIBs, but not individual OIDs. You can
> modify the code, but make sure you deal with get and get-next
> properly.
>
Even if we comment/modify the code for individual OIDs, we cannot skip OIDs
that are part of a MIB Table. Right?
On Wed, 4 Jul 2018 18:07:51 +0530 Thommandra wrote:
TG> > For snmpd, you can configure VACM views in snmpd.conf to
TG> > exclude certain OIDS. It's not very intuitive, but should be
TG> > possible.
TG>
TG> Can we remove the OIDs at compile time (using configure option)
TG> like we do for modules?
Robert,
Thanks for your reply. More in-line
On Tue, Jul 3, 2018 at 10:01 PM, Robert Story wrote:
> On Tue, 3 Jul 2018 19:05:59 +0530 Thommandra wrote:
> TG> - How can we disable an OID from snmpwalk output?
>
> For snmpd, you can configure VACM views in snmpd.conf to exclude
> certain OIDS. It'
On Tue, 3 Jul 2018 19:05:59 +0530 Thommandra wrote:
TG> - How can we disable an OID from snmpwalk output?
For snmpd, you can configure VACM views in snmpd.conf to exclude
certain OIDS. It's not very intuitive, but should be possible.
For the client, there isn't a way to not query for something du
