hai,
I am having a trap defined as follows in my MIB:
myTrap NOTIFICATION-TYPE
OBJECTS {
objectA,
objectB,
objectC,
objectD
}
STATUS current
DESCRIPTION
"my enterprise specific trap"
::= { myEnterpriseTraps 1 }
All the four objects used above are defined in the same MIB as
not-accessible since they are meant to be sent only along with traps.
Now, this MIB is used by two different agents which send traps according
to this MIB. But in one agent the objects objectC and objectD are
irrelevant. They are relevant only in the other agent. We want to avoid
sending an empty string(if it is OCTET-STRING) or sending an invalid
value like -1(if it is INTEGER) by the agent that doesn't support them.
can i achieve this using this single MIB either by defining objectC and
objectD's status as optional instead of current or by appropriate
description in the definition of the trap and making the second agent not
send those two objects along with the trap. Of these which is SNMP
standard compliant?
If not is there any other way of achieving this or we have to write
another MIB or trap which is same as the first but not containing those
two objects?
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Net-snmp-coders mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
