Chet, I made it. Thanks! I agree that this should be in Wiki, and it will save others a lot of time.
Ian On 1/19/07, Ian Chen <[EMAIL PROTECTED]> wrote:
Great thanks! I'll have a try this morning. Ian On 1/18/07, Chet Luther <[EMAIL PROTECTED]> wrote: > > On 1/18/07, Ian Chen <[EMAIL PROTECTED]> wrote: > > > > I wish to use server B to collect performance data from device C and > view > > the results in server A. > > Is it even possible? > > > > I add device C to Zenoss in A, and changed "Performance Monitor" to B. > > > In server B, I changed etc/zenperfsnmp.conf to: > > > > #PARAMETER VALUE > > monitor A > > zopeurl > > http://A:8080/zport/dmd/Monitors/Performance/B > > zopeusername USERNAME > > zopepassword PASSWORD > > zem http://A:8080/zport/dmd/ZenEventManager > > > > What I get is RRD files written to server B and there are data point > in > > those RRD files. > > And no RRD files in server A. > > > > I try to view performace data at > > http://A:8080/zport/dmd/Devices/Server/Linux/devices/C/viewDevicePerformance > > > There is no graphic. > > Ian, > > I had some trouble making this work myself. Here are the steps I > needed to take. Please stop all Zenoss processes on B before starting. > > 1. Create DNS CNAMEs for all of you Zenoss hosts so cookies can be > shared. > Host A: zenoss.yourdomain.com > Host B: B.zenoss.yourdomain.com > > 2. Allow B to access the MySQL server on A. > mysql> grant all privileges on events.* to [EMAIL PROTECTED] identified by > 'password'; > > 3. Point B to the correct database server. > On A's web interface go to Event Manager and change the database > hostname to zenoss.yourdomain.com instead of localhost. > > 4. Configure B's zenperfsnmp.conf and zenxevent.conf properly. > monitor B.zenoss.yourdomain.com > host zenoss.yourdomain.com > > 5. Create the performance monitor for B. > On A's web interface create a performance monitor named > B.zenoss.yourdomain.com. > Change the RenderUrl to > http://B.yourdomain.com:8080/zport/RenderServer > Set the Render User/Password to a Zenoss user with the admin role. > > 6. Modify the CookieAuthHelper.py to play nicely with Firefox's > draconian cookie support. > Edit > $ZENHOME/Products/PluggableAuthService/plugins/CookieAuthHelper.py > Search for the only line containing "setCookie" and change it to > the following: > response.setCookie(self.cookie_name, quote(cookie_val), > path='/', domain='zenoss.yourdomain.com') > > 7. Have Zope on B use the ZODB server on A: > Edit $ZENHOME/etc/zope.conf on B: > Search for the zeoclient section and change the server to > zenoss.yourdomain.com > > 8. Modify the Zenoss startup on B to exclude unneeded services. > Edit $ZENHOME/bin/zenoss > Comment out the following lines: > #C="$C zeoctl" > #C="$C zenmodeler" > #C="$C zenperfxmlrpc" > #C="$C zenprocess" > #C="$C zenping" > #C="$C zensyslog" > #C="$C zenstatus" > #C="$C zenactions" > #C="$C zentrap" > #C="$C zencommand" > This leaves only zopectl, zenxevent and zenperfsnmp enabled. > > 9. Start Zenoss on B: > zenoss start > > That should be it if I remember correctly. You'll notice that this > still creates the RRD files on B, but through the magic of a shared > zodb, a cookie and the RenderUrl the web interface on A can actually > show the appropriate graphs from B. The RenderUser/Password stuff is > for XMLRPC and only used for the sysUpTime display currently. > > I hope this helps. It should probably be in the Wiki at the least. > > -- > Chet Luther > [EMAIL PROTECTED] > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users >
_______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
