ok, I did figure out an easier way to do some of this. I can't access a Zenoss server right now so I'm going to try this off the top of my head. You have to change the max port that it does port scans on when it models. That is a field in the zProperties of individual devices or in device classes. Obviously, it will take longer to model a device, the more ports that it scans. This will allow it to automatically detect ports higher than 1024 which is the default. This will get everything working with the same name.
I'm not sure about having different names for duplicate port numbers....I've never tried it before. If somehow you do get the right names for the services applied to the right servers, you will want to lock those IP services from deletion and updates. If I remember, I can check in to this after Christmas....but I'll probably forget so you might want to reply to this post after that. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=14658#14658 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
