nvserverd has been setting "origin" to the IP address of the NetView box
for several releases now. Certainly for all of 7.1.4 if not for all of 7.1
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
ray.smith@clorox.
com
Sent by: To
owner-nv-l@lists. nv-l@lists.us.ibm.com
us.ibm.com cc
Subject
11/03/2005 10:32 [nv-l] Origin Event Slot in TEC
AM
Please respond to
nv-l
We are running NV 7.1.4 fp03 on solaris 8.
Tec is 3.9 also running on solaris 8.
The curious thing is;
On Some events that post to Tec identify netview as the origin in the Root
Slot table for event attributes. While most devices the Root Slot is the
name or ip of the Device that netview is reporting on.
The question is;
Should not the origin always be the device that is being reported on and
not the netview server? And if not the device origin why the netview
server?
example
11/2/2005 8:15:53 AM tec
TEC Event TEC_ITS_NODE_STATUS received with the message: Node Down.
=====---=====
[Root Slots]
adapter_host=my.netview.server.name;
hostname=The.Switch.Isthat.Down;
origin=x.x.x.81;
source=nvserverd;
sub_origin='';
sub_source=N;
=====---=====
[Event Slots]
date='11/02/05 08:07:54 AM';
date_reception=Wed Nov 2 08:07:54 2005;
repeat_count=0;
severity=FATAL;
=====---=====
[Adapter-Specific Slots]
category=netmon;
fqhostname=the.switch.that.isdown;
iflist=[ 'x.x.x.4'];
nodestatus=DOWN;
nv_generic=0;
nv_specific=0;
nvhostname=x.x.x.81;
Ray Smith
"baciare"
This e-mail (including any attachments) may contain information
confidential to The Clorox Company and is intended only for the use of the
intended recipient(s). If the reader of this message is not the intended
recipient(s), you are notified that you have received this message in error
and that any review, dissemination, distribution or copying of this message
is strictly prohibited. If you have received this message in error, please
delete this message and notify the sender immediately.
|