Anonymous_User Absent Member.
Absent Member.
2620 views

ZAM 7.5 Network Discovery Quits

Have ZAM 7.5 running on a VM (Windows Server 2003 SP1) as a VMWare Server
1.0.1 guest. Bridged network. VMWare host is Windows Server 2003 SP1. The
host is also running ZENworks Patch Management 6.3 natively. 3GB of RAM
and 3.4GHz Pentium 4 Only 100+ workstation in 11 locations connected by a
private WAN (no Internet).

ZENworks Patch Management is working OK. ZAM Workstation inventory
scanning is working OK. ZAM Network Discovery has run successfully on just
3 subnets. On all of the others it stops...usually gets to 80%+ completed
before it freezes. All I can do is to remove the network scan task.

The network subnets are on a private WAN (no Internet involved) and it is
not having any other problems...GroupWise email OK, ZENworks Remote
Management of PCs is OK, Web-browsing OK, rsync traffic OK, eDirectory
traffic OK.

The ZAM 7.5 documentation is pretty thin on this product given that Novell
acquired Tally Systems almost two years ago.

One gripe I have about ZAM is the requirement for a Windows server to
handle the backend and database. I can understand the necessity of doing
this for ZENworks Patch Management as Novell OEMs the product, but they own
ZAM and they ought to be pretty serious about making the backend processes
run on SLES10 and NW65 and use MySQL or PostgreSQL for the database engine.

I have read some comments here about the Network Discovery problem that
suggested just scanning for Windows devices and/or reducing the size of the
subnet being searched. I'm trying these suggestions but I don't really
think this ought to be a requirement to get Network Discovery to work.

Thanks for any suggestions.

Tim



0 Likes
5 Replies
Anonymous_User Absent Member.
Absent Member.

Re: ZAM 7.5 Network Discovery Quits

twessels@symquest.com,

>One gripe I have about ZAM is the requirement for a Windows server to
>handle the backend and database. I can understand the necessity of doing
>this for ZENworks Patch Management as Novell OEMs the product, but they own
>ZAM and they ought to be pretty serious about making the backend processes
>run on SLES10 and NW65 and use MySQL or PostgreSQL for the database engine.


I know this requirement will change in the next version of ZEN. I do
understand your gripe, but changes are happening for the better.

As for the network discovery....How many machines are on this subnet?
Have you looked at any of the task logs?

--
Jared Jennings - Data Technique, Inc.
Novell Support Forums Sysop
My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: ZAM 7.5 Network Discovery Quits

Glad to know that Novell will make backend server changes for ZAM with the
next release of ZENworks.

There are a number of different log file names in the logs folder for ZAM.
Are you interested in any one log type in particular?

ColsvrCoreEvent...
LoaderEvent...
NetCMgrEvent...
TaskServerCoreEvent...
TSCMgrEvent...
UnloaderEvent...

BTW, since posting my original message I have sub-divided the address range
of each subnet into a 1-127 and 128-254 for the private Class C and B
networks in use. I also checked only those device types that would likely
be found on those segments. This method has resulted in good results so
far. I'm not opposed to dividing each subnet into two halves if ZAM will
run the network discovery task reliably.

To answer your question, there are 10 remote office networks plus the main
office network. I'm estimating the total number of devices to be approx.
150. This would include PCs, servers, printers, routers.

Thanks.

Tim


> twessels@symquest.com,
>
> >One gripe I have about ZAM is the requirement for a Windows server to
> >handle the backend and database. I can understand the necessity of doing
> >this for ZENworks Patch Management as Novell OEMs the product, but they own
> >ZAM and they ought to be pretty serious about making the backend processes
> >run on SLES10 and NW65 and use MySQL or PostgreSQL for the database engine.

>
> I know this requirement will change in the next version of ZEN. I do
> understand your gripe, but changes are happening for the better.
>
> As for the network discovery....How many machines are on this subnet?
> Have you looked at any of the task logs?
>
> --
> Jared Jennings - Data Technique, Inc.
> Novell Support Forums Sysop
> My Blog and Wiki with Tips, Tricks, and Tutorials
> http://jaredjennings.org


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: ZAM 7.5 Network Discovery Quits

twessels@symquest.com,

>NetCMgrEvent...
>TaskServerCoreEvent...
>TSCMgrEvent...


Send me these three logs if you are still having this problem.

jaredljennings at gmail dot com

--
Jared Jennings - Data Technique, Inc.
Novell Support Forums Sysop
My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: ZAM 7.5 Network Discovery Quits


IS there just not any devices showing up in the network discovery or is
the network discovery not starting etc?


--
JFrench
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: ZAM 7.5 Network Discovery Quits

When the network discovery fails to complete...stops at some percentage, no
devices are found. If it completes, devices are discovered. The problem
is getting the network discovery tasks to complete.

In the meantime we have installed the most recent IR for ZAM 7.5 and
noticed no difference.

Tim

>
> IS there just not any devices showing up in the network discovery or is
> the network discovery not starting etc?
>
>
> --
> JFrench


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.