On 10/18/07 11:06 AM, "Chet Luther" <[EMAIL PROTECTED]> wrote:
>> I'm trying to monitor a server with a number of interfaces/Ips, and >> running >> into a problem with zenstatus. Let's say the host's main IP is >> 10.1.1.1, and >> that's the device's IP within Zenoss. Now let's also say that it's >> running >> http on 10.1.2.4, and smtp on 10.1.3.5. I wish to monitor all of >> those. As >> it is now, I only have the main IP in zenoss as a device. If I enable >> monitoring of IPServices for http and smtp, I get failures on those >> ports. >> >> For http specifically, I see the following line in the IPServices >> panel: >> http tcp 80 10.1.2.4 World Wide Web >> HTTP (RED) >> >> When I do tcpdumps on it, I see that zenstatus is using the device's >> hostname to connect to the port, rather than the IP listed. This >> happens >> across the board in situations like this for me. Ips of 127.0.0.1 >> don't let >> you monitor, so I know it uses the IP for something. Why doesn't it >> use it >> for the actuall tcp connection? > > The following changeset enables monitoring of the first real IP. It > is tagged for inclusion in 2.1.1. > Sweet, but what if I want to monitor ssh on that machines as well, where there're multiple IPs listed? Can it iterate through all the real ones, or will it just use the first? Geoff Franks Sr. Systems Administrator Hauptman Woodward Institute _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
