| I don't know if they need that for alarm definition or not but if it's the
case, it will be more easier for you you define alarm on event instead of
polling.\
Since this is a DECnet network over x.25, you'll be notified when a node
goes down (circuit down and so on).Therefore, you'll not gonna have to poll
for the alarm definiton.
I hope this help
francois
|
| Hi Francois,
Thanks for your reply, my problem (..customer problem) isn't to
reduce the overload due to MCC, he only wants numbers, a figure
of the numbers of packets caused by MCC during daily operation,
SHOWs xxx, SET xxx, TEST xxx, he also wants to use the COLLECTOR
to receive data from remote applications.
Don't ask me why he wants numbers, I think it's an accounting
problem, perhaps he wants to produce the bills to his customers
using the number of packets and want to exclude the MCC overload....
So, it isn't only alarms, I already use for other customers the
event logging sink, but for example I don't know the overload
on the remote CPU and on the network of a:
SHOW entity ALL STATISTICS
Thanks again,
Ciao Luciano
I'm only partialy involved in this
I know that
Since this is a DECnet network over x.25, you'll be notified when a node
goes down (circuit down and so on).Therefore, you'll not gonna have to poll
for the alarm definiton.
|