Normally what this says is not "netmon connected to trapd" but
"netmon-related application connected to trapd" , but you changed that by
specifying the source flag of "N", when you added "-s N" to the command.
The default source flag of "d" for "demo" results in the more usual
message.
The event command traces the same path that all the NetView daemons do --
it opens a tcp connection to trapd, sends its events(s), and then
disconnects. Unlike snmptrap, the event never leaves the NetView box. The
connected and disconnected messages are the same ones the daemons send when
they connect and disconnect. event was designed as a test tool to mirror
the event flow that the daemons use, which is why it works the way it does.
If you want to mirror the external trap flow, and issue a trap, that
actually leaves the box and comes back in over UDP, then use snmptrap. In
that case there will be no connected nor disconnected messages.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
"Haseneder,
Martina"
<martina.hasenede To
r@datev.de>
Sent by: nv-l@lists.us.ibm.com
owner-nv-l@lists. cc
us.ibm.com
03/30/05 06:49 AM
Subject
Please respond to [nv-l] netmon connected to trapd
nv-l
Hi folks,
to check EventForwarding I put out a "Node Up" Event of the NetView-Server
itself every 10 Minutes like:
event -h un102 -E 58916864 -s N
Now in the trapd.log with every NV-Server Node Up Event I find these lines:
1112170937 7 Wed Mar 30 10:22:17 2005 <none> N netmon
connected to trapd.
1112170937 3 Wed Mar 30 10:22:17 2005 un102 N Node Up
1112170937 7 Wed Mar 30 10:22:17 2005 <none> N netmon
disconnecting from trapd.
Should it make me nervous?
--
Martina Haseneder
P542 Datennetz-/Systemprogrammierung
Datev e.G.
email: Martina.Haseneder@datev.de
Tel: 0911 / 276-1063
|