That's interesting, to add a new trap to netview forwarded to TEC all we
have done is set the TEC event class, slot mapping and turned forward trap
on. The ruleset defined in /usr/OV/conf/tecint.conf is test.rs. The contents of
which I have included below. I have never
edited this ruleset. I have no idea what it is doing.
Now I know why I can't turn the TEC forwarding off on a trap by turning
off the forward trap in netview. This always seemed odd to me.
RuleSet2 RuleSet EventAttr3
"" 0
EventAttr3 EventAttr EventAttr4
Origin 1 42.231.8.3 "" 0
EventAttr4 EventAttr EventAttr5
Origin 1 42.2.1.12 "" 0
EventAttr5 EventAttr EventAttr6
Origin 1 42.2.1.13 "" 0
EventAttr6 EventAttr ForwardCorr7
Origin 1 0.0.0.0 "" 0
ForwardCorr7 ForwardCorr
""
Sean Lawrence
Systems Automation
Ext 5728
James Shanks <jshanks@us.ibm.com>
Sent by: nv-l-bounces@lists.ca.ibm.com
10/03/2006 06:12 PM
Please respond to Tivoli NetView Discussions
To: Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
cc:
Subject: Re: [NV-L] servmon probably died: ungracefully
disconnected from trapd
No. The "Forward trap" button in xnmtrap is just to identify traps to be
sent to another trapd. It has nothing to do with TEC. But the TEC Event
Class and optional slot mappings are used by the internal TEC adapter,
which is part of nvserverd, to build the event sent to TEC.
To forward to TEC you must include the trap in whatever ruleset you are
using for TEC Forwarding. The name of that ruleset is found in
/usr/OV/conf/tecint.conf, which you created when you used serversetup the
first time to configure TEC Forwarding. You can see it in serversetup if
you click that option again. If you want to add a new trap to that
existing ruleset then you have edit the ruleset using nvrsEdit, the Rule
Set Editor. And then you have to either restart nvserverd or get him to
reload that ruleset with the nvtecia command.
The deal is this. All events are seen by trapd, who gives them to nvcorrd,
who runs them through rulesets on behalf of his client, nvserverd.
nvserverd then gets all the events that were selected and passed by each
ruleset, and distributes those to his clients. His clients are either
event windows or the TEC adapter code. nvserverd is like a waiter who
passes the orders (events) out to customers after they have ordered them.
And he fixes 'em up just the way they like 'em, either formatted for the
event display or formatted for TEC. It's what he does.
Does this help?
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp
sean.lawrence@cantire.com
sean.lawrence@cantire.com
Sent by: nv-l-bounces@lists.ca.ibm.com
10/03/2006 01:07 PM
Please respond to
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
To
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
cc
Subject
Re: [NV-L] servmon probably died: ungracefully disconnected from trapd
Ok that cleared some things up. We are forwarding to TEC. Is the "Forward
trap" option not required to send messages to TEC? This is how our
production
system is setup.
Sean Lawrence
Systems Automation
Ext 5728
James Shanks <jshanks@us.ibm.com>
Sent by: nv-l-bounces@lists.ca.ibm.com
10/03/2006 12:44 PM
Please respond to Tivoli NetView Discussions
To: Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
cc:
Subject: Re: [NV-L] servmon probably died: ungracefully
disconnected from trapd
Well, this forum is not a substitute for IBM service. I think you should
reopen your PMR and get some more help.
Because none of this is relevant to your problem it seems to me.
Are you trying to forward traps to TEC and that isn't working?
Or are you trying to forward traps to another trapd and that isn't
working?
Or neither?
But servmon has nothing to do with any forwarding and my guess is that you
aren't even using him. If his conf file has nothing for him to do, he
shuts down. You can go look in the servmon.log as the ovstatus suggests
and verify that. If you aren't using him then you can remove him from the
startup with
ovdelobj /usr/OV/lrf/servmon.lrf
and then you won't see those messages.
The ugly error message is TEC means that trapd.conf is configured to
forward trap 1.3.6.1.4.1.9.9.42.2, specific trap 2, to another traps, but
trapd has not been configured to
do that. If you trying to forward to another trapd then you must use
serversetup to configure trapd and tell him the hostname of the other
trapd. If you aren't trying to do that, then you can get rid of the
message by using xnmtrap. Apparently this trap has the "Forward trap"
button set on for it in trapd.conf. Use xnmtrap and find enterprise
1.3.6.1.4.1.9.9.42.2, specific trap 2, and click the button to turn it
off. Then that ugly
error message will go away.
Hope this helps. If not, then I'd try Level 2 again and stay with them
until they fix your problem. That's what they are there for.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp
sean.lawrence@cantire.com
sean.lawrence@cantire.com
Sent by: nv-l-bounces@lists.ca.ibm.com
10/03/2006 12:29 PM
Please respond to
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
To
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
cc
Subject
Re: [NV-L] servmon probably died: ungracefully disconnected from trapd
I opened a PMR last week and was told to start netview using /etc/netnmrc
command everything was working. Now forwarding is not working again and
restarting everything is not solving the problem.
When I log into Netview I get the message:
WARNING: The following REGISTERED daemons are not running:
servmon
When a trap should be forwarded to TEC the following message is displayed
in the nvserverd.log and nothing get forwarded.
10/03/06 11:47:33
TEC_ITS_FATAL_ERROR;source=nvserverd;sub_source=T;origin=42.108.20.106;adapter_host=tst161.cs.ctc;host
name=<none>;category=4;date="10/03/06
11:47:33";status=OPEN;nvhostname=42.108.20.106;msg="Event
1.3.6.1.4.1.9.9.42.2, (6
, 2) to be forwarded, but trapd not configured to forwarding event";END
ovstatus shows
object manager name: servmon
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: -
last message: Exited. Please see log file for more info.
exit status: exit(0)
Sean Lawrence
Systems Automation
Ext 5728
James Shanks <jshanks@us.ibm.com>
Sent by: nv-l-bounces@lists.ca.ibm.com
10/03/2006 12:17 PM
Please respond to Tivoli NetView Discussions
To: Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
cc:
Subject: Re: [NV-L] servmon probably died: ungracefully
disconnected from trapd
What problem are you trying to solve?
None of this looks relevant to servmon.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
*** eSafe scanned this email for malicious content ***
*** IMPORTANT: Do not open attachments from unrecognized senders ***
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
*** eSafe scanned this email for malicious content ***
*** IMPORTANT: Do not open attachments from unrecognized senders ***
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
|