Re: RAQMON PDU Notification Objects - Table or Scalar?

"Randy Presuhn" <[email protected]>
Newsgroups gmane.ietf.rmonmib
Message-ID <009101c503e6$8e60d800$7f1afea9@oemcomputer>
Hi -

> From: "Romascanu, Dan (Dan)" <[email protected]>
> To: "Mark Ellison" <[email protected]>
> Cc: <[email protected]>
> Sent: Wednesday, January 26, 2005 10:25 AM
> Subject: RE: [RMONMIB] RAQMON PDU Notification Objects - Table or Scalar?
...
> What I got until now:
>
> - SNMP is optional and not recommended.

I had understood it to be "SNMP is optional" and "use of traps is NOT RECOMMENDED"

> - if SNMP is supported, recommend doing INFORMs

> RDS-MIB structure. three options:
>
> - keep the table as is, define initital and continuous reporting notifications
> - keep table but change indexing as suggested by Mark, initial notification points
>   to subsession identifiers, then continuous notifications use this
> - change to scalar
...

Can you confirm or deny whether it was a goal to, as Mark put it,
"commingle statistics from different (sub)sessions in a single report "?
This, and effectively dropping TRAPs as way of carrying this stuff,
will affect which of the alternatives would make more sense.

Randy
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.