Environment
Novell ZENworks Asset Management 7 - ZAM7
Situation
Network
Discovery scan does not move Client Not Found to Client found after
a
subsequent rescan. Below is an example of what a customer may see:
subsequent rescan. Below is an example of what a customer may see:
Discovery
said this computer does not have the client installed. But
when looked up in "Discovery-->Reports-->Find Device", this
DNS computer name had two entries, one for the wireless connection
and one for the hardwire connection. One said the client was
installed and the other said not installed.
Resolution
The source
of this bug was the Network Discovery Engine, NetDisc.dll. It
was reporting a bogus MAC address for SNMP enabled devices which
did not return a valid MAC address.
Fixed in IR9 -
Please also see note at end of resolution.
Fixed in ZAM 7.0 IR 9.
If downloading the Interim Release manually fromhttps://download.novell.com, the filename is ZAM700SP1ir9.EXE. The Interim releases can also be set up within the ZAM Manager for the Task server to check the site on a scheduled basis, and download and apply them automatically. Please refer to the Help Section for details of how to set up automatic downloads if desired.
Each interim release is cumulative. If Interim Release 9 is not available due to a newer interim release being placed on the website, be assured that the code needed is in the later release.
If downloading the Interim Release manually fromhttps://download.novell.com, the filename is ZAM700SP1ir9.EXE. The Interim releases can also be set up within the ZAM Manager for the Task server to check the site on a scheduled basis, and download and apply them automatically. Please refer to the Help Section for details of how to set up automatic downloads if desired.
Each interim release is cumulative. If Interim Release 9 is not available due to a newer interim release being placed on the website, be assured that the code needed is in the later release.
The Network
Discovery Loader attempts to match a scanned device to devices
previously scanned and already loaded into the database. If
the information gathered from a network device by the Network
Discovery Engine includes the MAC address, the Loader will not
reconcile it to previously loaded data unless the MAC address
values match. Unless the Engine created the same bogus MAC
address for devices that SNMP enabled devices that did not return
their MAC address, then the Loader would not reconcile it to
previously scanned data, so added another instance of the same
device.
With this fix the Engine initializes the receiving memory locations and verifies that the call succeeded before creating the displayable MAC address.
With this fix the Engine initializes the receiving memory locations and verifies that the call succeeded before creating the displayable MAC address.
NOTE: Customers having this problem would do
well to use WebConsole to delete duplicate devices or an entire
segment's data prior to rescanning with this fix.