trapsink/trap2sink table MIB?

[Alex Ruzin]

Does anybody have a MIB for trapsink/trap2sink table?
Is anybody going to design/implement it in future?

Best regards, Alex

[Alex Ruzin]

Does anybody have a MIB for trapsink/trap2sink table?
Is anybody going to design/implement it in future?
What about trapDestTable from RMON2-MIB.txt?
Alex

[Dave Shield]

Post by Alex Ruzin
Does anybody have a MIB for trapsink/trap2sink table?

Yup - how about the SNMP-NOTIFICATION-MIB?

Post by Alex Ruzin
Is anybody going to design/implement it in future?

Already done - see agent/mibgroups/notification.

Although our configuration syntax doesn't match this MIB
directly (if only because it predates the MIB), it's used
to populate the same set of tables.
Remember that a MIB is just a view of some underlying data.
There's nothing to say that a different handling of the same
data has to use the precise same organisation.

Post by Alex Ruzin
What about trapDestTable from RMON2-MIB.txt?

Well, you're the expert on RMON as far as this project is
concerned :-) But I would expect that any implementation
of this table should probably report on the same underlying
data.
So creating a new row in RMON2-MIB::trapDestTable might well
result in a new row appearing in various SNMP-NOTIFICATION-MIB
tables (and vice versa).
This would obviously require a certain degree of cooperation
between the two implementations - though this might be as simple
as the rmon handler calling 'snmpNotifyTable_add', and similar.


That's how I see things anyway - others may think differently.

Dave

[Ali Chanaui]

At 14 Mar 2002 Dave Shield wrote:
Dave> I would expect that any implementation
Dave> of this table should probably report on the same
Dave> underlying data.
Dave> So creating a new row in
RMON2-MIB::trapDestTable
Dave> might well result in a new row appearing in
various
Dave> SNMP-NOTIFICATION-MIB
Dave> tables (and vice versa).
Dave> This would obviously require a certain degree
of
Dave> cooperation between the two
Dave> implementations - though this might
Dave> be as simple
Dave> as the rmon handler calling
'snmpNotifyTable_add',
Dave> and similar.
Dave>
Dave>
Dave> That's how I see things anyway - others may
think
Dave> differently.

I tried to understand the trapsink/trap2sink table and

it puts me to confusion: I may observe
two (independent?!!) tables:
a) list of "struct trap_sink" - located in
agent/agent_trap.c and
b) snmpNotifyTableStorage - located in
mibgroup/notification/...

And what is more - agent/agent_trap.c for sending
looks
over two these tables, one after other.
May anyone explain this solusion?
Which table have I to managed?

Yours sincerely, Ali



__________________________________________________
Do You Yahoo!?
Yahoo! Movies - coverage of the 74th Academy Awards�
http://movies.yahoo.com/