the situation is the same. after setting zIpServiceMapMaxPort on the
device, i still need to add and set 3389 ipservice manually. and it
would be deleted after remodeling if i didn't lock it.
What version of Zenoss are you running? I can't seem to replicate this
behavior locally, and the portscan.IpServiceMap collector plugin
hasn't been updated in a very long time. There are a couple more
things you could check.
First, is it possible that Zenoss is discovering these ports and just
not displaying them? Have you tried removing the check mark from
"Monitored" on the table header of IP Services on the OS tab to see if
the ports are there and just not monitored?
Second, the portscan might be taking longer than the default 180
seconds configured in zCollectorClientTimeout. Could you increase this
limit to see if it can then find more ports?
You can also run this command as the zenoss user to get more feedback
on what's happening during the modeling.
zenmodeler run -v 10 --collect=portscan.IpServiceMap --
device=yourDeviceName
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
