nv-l
[Top] [All Lists]

[nv-l] Origin Event Slot in TEC

To: nv-l@lists.us.ibm.com
Subject: [nv-l] Origin Event Slot in TEC
From: ray.smith@clorox.com
Date: Thu, 3 Nov 2005 07:32:03 -0800
Delivery-date: Thu, 03 Nov 2005 15:33:20 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com

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.
<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web