> Hi all,
> by the look of things it seems that our rulesets inside of
> /usr/OV/ESE.automation occasionally stop to work. We opened a PMR for this
> problem. By the way we are running netview 7.1.3 with fixpack 1 on solaris
> based machines.
>
> In the meantime we would like to implement a kind of check, that is doing the
> following:
> 1) sends self-made traps to the netview box, where the trap runs through all
> rulesets
> 2) finally an event is sent to the TEC server.
>
> In case no event out of this check is received by the TEC server within a
> specified time intervall, a FATAL event is created and handeled by our
> operation team, meaning that there might be a problem with our ESE.automation
> rulesets.
>
> My question is:
> is there a way to configure what "slots" should finally be inserted into a
> netview event, which is sent to the TEC?
>
> Sure we can create a separate event class, that covers all slots that can be
> sent by our netview event inside of our check machanism, but it would be best
> to adjust the internal netview event, that is going to be sent to the TEC,
> cause we already have such an event class in place for checking our tec rules
> / tec processes.
>
> I don´t think that a trap can be adjusted like this in the trapd.conf file
> directly, so only solution is creating a separate event class - right?
>
> Thanks for your help and time.
>
> best regards,
> Thorsten Mildeberger
>
> EMS Solutions - SMC Tools & Automation
> GOSD - Central Region
> EDS Deutschland GmbH
> Eisenstr. 43
> 65428 Rüsselsheim
> Tel.: +49 (0) 6142 80-3706
> Fax.: +49 (0) 6142 80-3030
> mailto:thorsten.mildeberger@eds.com
>
|