On the subject of Response Manager, an AIX/Netview application for
monitoring and managing response time [posted 5/1], I received interest from
NV users so began the process of prospecting for an internal path for it out
of Fidelity. I don't know where the road ahead will lead.
The lawyer with whom I've starting emailing has been on vacation, but he
should be back now. Before he left he said that [posting Fidelity s/w as
freeware] has never been asked before, let alone done... which tells me it
could get internally interesting. Nevertheless I hope to be able to post an
upbeat update soon.
* ken.twombly AT fmr DOT com <mailto:ken.twombly AT fmr DOT com>
* 800.SKYPAGE Pin #106-8534
From: Paul Sandler [SMTP:paul AT swebs DOT com]
<mailto:[SMTP:paul AT swebs DOT com]>
Sent: Tuesday, May 23, 2000 8:08 PM
To: ken.twombly AT fmr DOT com <mailto:ken.twombly AT fmr DOT com>
Subject: Fwd: [NV-L] Response Manager?
I would be interested in trying out this product. Have you found
whether Fidelity will allow you to send a copy to others for no
>X-Envelope-To: <paul AT SWEBS DOT COM <mailto:paul AT SWEBS DOT COM> >
>From: "Twombly, Ken" <Ken.Twombly AT FMR DOT COM
<mailto:Ken.Twombly AT FMR DOT COM> >
>To: "'nv-l AT tkg DOT com'" <nv-l AT tkg DOT com <mailto:nv-l AT tkg
DOT com> >
>Subject: [NV-L] Response Manager?
>Date: Mon, 1 May 2000 10:00:26 -0400
>X-Mailer: Internet Mail Service (5.5.2448.0)
>Sender: owner-nv-l AT tkg DOT com <mailto:owner-nv-l AT tkg DOT com>
>Reply-To: IBM NetView Discussion <nv-l AT tkg DOT com
<mailto:nv-l AT tkg DOT com> >
>X-MDaemon-Deliver-To: paul AT swebs DOT com <mailto:paul AT swebs DOT
>We have an application here @Fidelity that is not getting much use,
and I am
>curious how the NV community might feel about either just using it
>I can convince Fidelity to allow it) and/or taking over the source.
>to see it unused as it is quite spiffy. Here is a quick
>Response (which is about 5 years old now) was designed to monitor &
>network response time and packet loss, to provide more end-to-end
>SLA-type data for operations. It requires the cisco ping MIB (e.g.
>cisco router) as PING sources; destinations can be any reliable box
>responds to ping. Metrics supported by cisco PING MIB are: min,
>response time, and packet loss%.
>Response is a GUI-driven Netview app. "Response" submaps are
created by the
>"Response-->New Map" menu item. Then you locate/select/copy/paste
>into the submap(s), and connect them together using either
>NV:Add-->Connector or some of Response's convenience functions
>RM:Connect--> Selected to Acknowledged). Then you configure ping
>and thresholds (RM:Connector-->Configure) , and "activate" the
>(RM:Connector-->Activate Selected or RM:Maps-->Start Selected Map).
>only a few minutes to set up a massive map. Response can be used
>or long-term response time collection, if you don't mind an occ'l
>Connector colors (red, yellow, black) are used to indicate
>packet loss threshold states, so you can watch the map and see how
>stand. Connector line-style (solid, dashed) is used to indicate if
>connector is active or inactive.
>You have lots of control over the generation of SNMP traps.
>You have lots of control over the generation of snmpCollect data.
>"Connector-->Graph Selected" brings up beautiful NV graphs.
>Application options that aren't supported by the menu interface can
>changed via X resources.
>Netview's notion of R/W and Read-Only is supported. User's w/ a R/W
>create, edit, and run Response submap(s) that can generate Traps
>snmpCollect data. RO users can only start up a copy of a response
>BTW duplicates polling) and graph data already collected or being
>(by a RW Response).
>RM is pretty scalable. We've run it for weeks on hundreds of
>no important CPU or disk impact. When NV is brought down for
>breaks and database backups, Response goes down w/ it. This is an
>* It is GUI-driven. There is no way to configure it with vi.
>* Netview GUI must be running. Runs fine on NV 5.1.2/AIX
>* Works today only w/ cisco routers as sources. No RMON. Only
>* Need set community name for sources.
>* Won't work on NT or Solaris unless ported (AIX only)
>* Response submaps can not contain containers, only regular
>and connectors (this should be fixed)
>If you have an interest in this or have questions, pls. respond. If
>anyone willing to manage and extend the source and make it
available to NV
>users without charge, pls. respond as well.
>Depending on interest level, I will poke around to see if it can be
>(or what hoops will need jumping through). We've received quite a
>help over the years from the NV community through this medium, and
>to give something back.
>* ken.twombly AT fmr DOT com <mailto:ken.twombly AT fmr DOT com>
<mailto:ken.twombly AT fmr DOT com <mailto:ken.twombly AT fmr DOT com> >
>* 800.SKYPAGE Pin #106-8534
>NV-L List information (unsubscribing, policies, posting, digest
>searchable archives): http://www.tkg.com/nv-l