For recent versions of Nways, this can be forced from the map. For
the Nways Topololy (where the Java Device Managers are), there is
a menu pick (under Tools, I think) to refresh the topology. For the ATM
and Hubs displays, I would use the smitty cml entries to Clear Hubs
Topology and Clear ATM Topology. When you restart the associated
daemons, those topologies are repopulated from the Netview database
and the icons appear, first flat and blue, then green and puffy. This state
usually, but not always, carries over to the IP topology as well.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
noelt@be.ibm.com@tkg.com on 11/24/2000 06:15:40 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: nv-l@tkg.com
cc:
Subject: [NV-L] OVwSetSymbolBehavior and NWays
Hello forum readers.
When you install products like CiscoView or Nways on top of NetView, you
all know that as a result, the icons of the managed devices (Ciscos or IBM
hardware) become executable. I assume this is done by the installation
program(s) using the OVwSetSymbolBehavior routine which is described in the
NetView programmers guide.
Now, I wonder how to force that process to re-run (after an upgrade or so).
Is there another way to force all ciscos or IBM devices icons to become
executable than using directly OVwSetSymbolBehavior ? Is there a .sh or
.bat file available with Nways and/or Ciscoview ?
Thanks in advance.
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|