nv-l
[Top] [All Lists]

RE: [nv-l] nvsniffer / servmon

To: <nv-l@lists.us.ibm.com>
Subject: RE: [nv-l] nvsniffer / servmon
From: "Barr, Scott" <Scott_Barr@csgsystems.com>
Date: Fri, 31 Oct 2003 14:37:30 -0600
Delivery-date: Fri, 31 Oct 2003 20:46:25 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l-digest@lists.us.ibm.com
Thread-index: AcOf7G+wrLEMBSW8RSWfVf1mSCl7OAAACZcQ
Thread-topic: [nv-l] nvsniffer / servmon
Well, I'm still digging!
 
It appears that discovery works. The config file says the second field in the config is the "service smartset" and describes it as the "smartset to create if the service is discovered" to exist. My smartset IS being populated and when I right clikc -> monitor -> network ->services - the ports show up. The only thing that does not appear to be working is the creation of the service icon as part of the node. Here is my config if anyone wants to take a stab at whether it's "right"
 
isCICS_Gateway|5000,5503,7000,7020,7050,7051|CICS_Services|CICS_Gateway_Service|||Production_OS390|5
 
The address of the nodes listed in the "Production_OS390" smartset are all multi-homed with the services actually responding on the real interface, not the SNMP address which is the virtual.
 
OBJECT: 859
FIELD ID FIELD NAME FIELD VALUE
10 Selection Name "fdt-osa-sy2.csgsystems.com"
11 IP Hostname "fdt-osa-sy2.csgsystems.com"
14 OVW Maps Exists 1
15 OVW Maps Managed 1
75 IP Status Normal(2)
78 isIPRouter TRUE
128 isIBM TRUE
136 isFtpServer TRUE
180 vendor IBM(1)
192 isNode TRUE
194 isComputer TRUE
195 isConnector TRUE
196 isBridge FALSE
197 isRouter TRUE
198 isHub FALSE
204 isMainFrame TRUE
219 routerSysName "csg-OSA-sy2 205.144.149.130 - Comm. Srv for z/OS V1R3"
220 isIP TRUE
239 isSNMPSupported TRUE
241 SNMP sysDescr "SNMPv3 agent version 1.0 with DPI version 2.0"
242 SNMP sysLocation xxxxxxxxxx
243 SNMP sysContact xxxxxxxxxxx
244 SNMP sysObjectID "1.3.6.1.4.1.2.3.13"
245 SNMPAgent Unset(0)
251 SNMP ipAddress "205.144.149.130"
252 isMLM FALSE
253 isSYSMON FALSE
254 isSIA FALSE
255 isManager FALSE
257 isSLM FALSE
258 isSIAOS2 FALSE
297 TopM Interface Count 3
303 TopM Interface List "Virtual Up 205.144.149.130 255.255.255.252 <None> IB"
"IP Up 10.8.4.10 255.255.255.0 0x000255098BDF et"
"IP Up 10.8.4.11 255.255.255.0 0x00025509E369 et"
317 XXMAP Protocol List "IP"
341 isZOS TRUE
344 MVS TcpipProcName "TCPIPOSA"
841 IP Name "fdt-osa-sy2.csgsystems.com"
1299 default IP Symbol List 3730
3731
3732
3734
3735
3812
3817
3823
3813
3819
3825
459457 isCICS_Gateway TRUE
root[ntv-denver02:/usr/OV/CSG/seed_files]#
 
-----Original Message-----
From: owner-nv-l-digest@lists.us.ibm.com [mailto:owner-nv-l-digest@lists.us.ibm.com]On Behalf Of James Shanks
Sent: Friday, October 31, 2003 2:15 PM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] nvsniffer / servmon


I'm not the expert on this, partly because it is so new, and partly because I don't work with it.  But I don't think the first version of servmon is as flexible as you might like it to be.  According to my understanding, in the case of raw port tests, it appears that only the SNMP address is tested.  The raw port test does not test all IP addresses on a node.


James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group



"Barr, Scott" <Scott_Barr@csgsystems.com>
Sent by: owner-nv-l-digest@lists.us.ibm.com

10/30/2003 04:55 PM
Please respond to nv-l

       
        To:        <nv-l@lists.us.ibm.com>
        cc:        
        Subject:        [nv-l] nvsniffer / servmon




NetView v7.1.4 /  Solaris 2.8
 
Greetings. There is  a new enhancement /  replacement for nvsniffer that I am having trouble  getting to work. The concept is to detect whether a particular TCP port is  accepting connections and report an event if it is not. It looks to me like  servmon will now do this. nvsniffer as I recall will discover but not  monitor port level applications.
 
The problem is  this:
 
The servmon  configuration requires that you specify what port the application runs on and  what smartset contains the nodes that are considered "targets" for the servmon  application.
I have a smartset  created that has 3 Unix servers.
Each of the Unix  servers has multiple instances of the software running on multiple different  ports.
Each of the Unix  servers is multi-homed (4 physical and 12 virtual  addresses).
Each instance of the  software is tied to a virtual address.
Each instance of the  software uses one or more ports.
In my configuraiton,  I specify I am interested on port 26001 (for instance).
 
Since the boxes are  multi-homed, I don't think servmon can tell which interface/IP address to probe  for port 26001 activitiy
The creation of the  smarset means that the nodes listed are the right boxes, but not the right  interfaces for activity on those ports.
 
SO my question is -  is servmon smart enough to figure out the traffic is NOT on the interface that  is resolved in DNS and thus located in my smartset? Since servmon actually adds  a field in ovwdb (field name drivin by servmon.conf) I cannot specify an  interface in the servmon config or the smartset - only a node name since it  doesn't appear to add a field to an interface object, only to a node  object.
 
 
 
 


Scott  Barr

Distributed  Network Engineer

CSG Systems  Inc.

scott_barr@csgsystems.com

Voice:  402-431-7939

Fax:  402-431-7413


 


#### Barr, Scott.vcf has been removed from this note on October 31, 2003 by James Shanks

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web