My understanding of TFNC is that it will NOT apply status info to NetView's
maps. However, I believe that SMARTS' "SMART Pinger" add-on used in conjunction
with their IPFM (and maybe with TFNC since that is just Tivoli's repackaging of
IPFM) is supposed to do that.
Date: Wed, 24 Feb 1999 13:02:31 -0600
From: "Prokott, Joe" <Joe.Prokott@WESTGROUP.COM>
Subject: Re: Router down - stopping multiple node downs
This is a fine rule, but it doesn't address a few issues:
(1) The "interface down/up" part of the rule does not consider which
interface the "Reset on Match" is looking at - it only looks at the node
name($2) itself. This may be a problem if you have a router with multiple
interfaces and multiple interfaces go up/down during the same period of
time. I believe one would need to write a script and look at PART of the $3
variable to assure you are matching the correct interface up event with the
correct interface down event.
(2) The rule does not address how color changes are made in the NV maps.
It would be nice if NV would change the devices on the other side of downed
router interface(s) to BLUE, meaning the status is unknown. This makes it
much easier for the operator to identify the source of the problem via the
I do not have a rule that addresses the above issues specifically, but I
know #2 is a complicated issue, involving the "knowing" of the relationships
between objects in the NV database and in the network. We are going to soon
be looking at TFNC and hope that this will assist in doing the work of
correlating the network topology contained in the NV database, as well as
changing corresponding symbol status colors in the NV maps when appropriate.
Can anyone confirm that this is part of what TFNC actually does?
Joe Prokott - West Group
610 Opperman Drive
St. Paul, MN 55123