I have been using MRTG on a Windows 2003 server platform to monitor different Active Devices and I am trying to install RRDTool into the existing MRTG but I do not know exact procedure of implementing RRDTool with MRTG, in fact, I tried to searched the documentation but couldn't find specific documents for Windows.
Regards, > From: [email protected] > Subject: mrtg Digest, Vol 52, Issue 2 > To: [email protected] > Date: Wed, 13 Apr 2011 15:58:24 +0200 > > Send mrtg mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.oetiker.ch/cgi-bin/listinfo/mrtg > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of mrtg digest..." > > > Today's Topics: > > 1. help on SNMPv3 configurtion in .cfg > (Cihan Subasi (Garanti Teknoloji)) > 2. Re: help on SNMPv3 configurtion in .cfg (Daniel McDonald) > 3. Re: help on SNMPv3 configurtion in .cfg > (Cihan Subasi (Garanti Teknoloji)) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 13 Apr 2011 14:21:38 +0300 > From: "Cihan Subasi \(Garanti Teknoloji\)" <[email protected]> > Subject: [mrtg] help on SNMPv3 configurtion in .cfg > To: <[email protected]> > Message-ID: > <792e0db482e63448902e029f9abaee1c2addc5a...@tekmbxv1.fw.garanti.com.tr> > > Content-Type: text/plain; charset="us-ascii" > > I have not been able to run snmpv3 configured .cfg file, below is mine, can > you share with us a sample .cfg or correct our mistakes below? thank you > > > WorkDir: /export/sun4_share2/testrtr > > #Options[_]:bits,growright > Options[_]:bits,growright > #Options[_]:enablesnmpv3,snmp-options=:::::3,contextengineid=800000090300001BD53DB640 > EnableSnmpV3: yes > Xsize[_]: 550 > Ysize[_]: 250 > Ytics[_]: 10 > Withpeak[_]: ym > #Suppress[_]: y > Interval: 6 > > # > > -------testrtr snmpv3-------------------------------------------------------- > > Target[testrtr-s0101]: \Serial0/1/0\:1:[email protected]:::::3 > SnmpOptions[testrtr-s0101]: > username=>'xxxxxx',authprotocol=>'md5',authkey=>'0x80b746aa503f97bf37e1d93e90438d24',privprotocol=>'3d > es',privkey=>'0x80b746aa503f97bf37e1d93e90438d24daf8f544b59d592dea3aac0de8cbbbb0',contextengineid=>'800000090300001BD5FDB000',privpa > ssword=>'yyyyyyyy' > MaxBytes[testrtr-s0101]: 125000000 > Title[testrtr-s0101]: TestRTR s0/1/0:1 > PageTop[testrtr-s0101]: <H1>Traffic Analysis for TestRTR-s0/1/0:1 - 1Gbps > </H1> > <TABLE> > <TR><TD>System:</TD><TD>1.1.1.1 in </TD></TR> > <TR><TD>Maintainer:</TD><TD></TD></TR> > <TR><TD>Interface:</TD><TD>Serial : 0/1/0:1 </TD></TR> > <TR><TD>IP:</TD><TD> TestRTR - s0/1/0:1 </TD></TR> > <TR><TD>Max Speed:</TD> > <TD>1.0 Gbits/s (ethernetCsmacd)</TD></TR> > </TABLE> > > > This message and attachments are confidential and intended solely for the > individual(s) stated in this message. If you received this message although > you are not the addressee, you are responsible to keep the message > confidential. The sender has no responsibility for the accuracy or > correctness of the information in the message and its attachments. Our > company shall have no liability for any changes or late receiving, loss of > integrity and confidentiality, viruses and any damages caused in anyway to > your computer system. > > Bu mesaj ve ekleri, mesajda gonderildigi belirtilen kisi/kisilere ozeldir ve > gizlidir. Bu mesajin muhatabi olmamaniza ragmen tarafiniza ulasmis olmasi > halinde mesaj iceriginin gizliligi ve bu gizlilik yukumlulugune uyulmasi > zorunlulugu tarafiniz icin de soz konusudur. Mesaj ve eklerinde yer alan > bilgilerin dogrulugu ve guncelligi konusunda gonderenin ya da sirketimizin > herhangi bir sorumlulugu bulunmamaktadir. Sirketimiz mesajin ve bilgilerinin > size degisiklige ugrayarak veya gec ulasmasindan, butunlugunun ve > gizliliginin korunamamasindan, virus icermesinden ve bilgisayar sisteminize > verebilecegi herhangi bir zarardan sorumlu tutulamaz. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.oetiker.ch/pipermail/mrtg/attachments/20110413/a2bee857/attachment-0001.htm > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: logo.gif > Type: image/gif > Size: 1947 bytes > Desc: not available > Url : > http://lists.oetiker.ch/pipermail/mrtg/attachments/20110413/a2bee857/attachment-0001.gif > > > ------------------------------ > > Message: 2 > Date: Wed, 13 Apr 2011 07:27:01 -0500 > From: Daniel McDonald <[email protected]> > Subject: Re: [mrtg] help on SNMPv3 configurtion in .cfg > To: mrtg <[email protected]> > Message-ID: <c9cb00c5.2e63e%[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > On 4/13/11 6:21 AM, "Cihan Subasi (Garanti Teknoloji)" > <[email protected]> wrote: > > > I have not been able to run snmpv3 configured .cfg file, below is mine, can > > you share with us a sample .cfg or correct our mistakes below? thank you > > > > > > WorkDir: /export/sun4_share2/testrtr > > > > #Options[_]:bits,growright > > Options[_]:bits,growright > > #Options[_]:enablesnmpv3,snmp-options=:::::3,contextengineid=800000090300001BD > > 53DB640 > > EnableSnmpV3: yes > > Xsize[_]: 550 > > Ysize[_]: 250 > > Ytics[_]: 10 > > Withpeak[_]: ym > > #Suppress[_]: y > > Interval: 6 > > > > # > > Target[testrtr-s0101]: \Serial0/1/0\:1:[email protected]:::::3 > > SnmpOptions[testrtr-s0101]: > > username=>'xxxxxx',authprotocol=>'md5',authkey=>'0x80b746aa503f97bf37e1d93e904 > > 38d24',privprotocol=>'3d > > es',privkey=>'0x80b746aa503f97bf37e1d93e90438d24daf8f544b59d592dea3aac0de8cbbb > > b0',contextengineid=>'800000090300001BD5FDB000',privpa > > ssword=>'yyyyyyyy' > > > If you are using authkey and privkey, you don?t need privpassword or > contextengineid, as the privkey is the hash of the privpassword and the > contextengineid > > > I?ll also note this from the Net-SNMP 5.2.0 releasenotes: > The non-core modules Crypt::DES, Digest::MD5, Digest::SHA1, and > Digest::HMAC are needed to support SNMPv3. > > In order to support the AES Cipher Algorithm as a SNMPv3 privacy > protocol, the non-core module Crypt::Rijndael is needed. > > > Here is a working sample, sanitized... > Target[router1.example.com.cpu1]: cpmCPUTotal5secRev.1&cpmCPUTotal1mi > nRev.1:[email protected]::3:1:1:3 > SnmpOptions[router1.example.com.cpu1]: > authkey=>'0xf0aba...',authprotocol=>'sha',privprotocol=>'aescfb128',username > => > 'foo',privkey=>'0x03b...? > > > -- > Daniel J McDonald, CCIE # 2495, CISSP # 78281 > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.oetiker.ch/pipermail/mrtg/attachments/20110413/6394db7a/attachment-0001.htm > > > ------------------------------ > > Message: 3 > Date: Wed, 13 Apr 2011 16:58:16 +0300 > From: "Cihan Subasi \(Garanti Teknoloji\)" <[email protected]> > Subject: Re: [mrtg] help on SNMPv3 configurtion in .cfg > To: "'Daniel McDonald'" <[email protected]>, "mrtg" > <[email protected]> > Message-ID: > <792e0db482e63448902e029f9abaee1c2addc5a...@tekmbxv1.fw.garanti.com.tr> > > Content-Type: text/plain; charset="us-ascii" > > Thank you for the help...I managed to get it run > > SnmpOptions[testrtr-s0101]: > authkey=>'0x80b746aa503f97bf37e1d93e90438d24',authprotocol=>'md5',privprotocol=>'des',username=>'xxxx',privkey=>'0x5c6d827205aa3b3fd88529b864b4bb72' > > > > ________________________________ > From: [email protected] > [mailto:[email protected]] On Behalf Of > Daniel McDonald > Sent: Wednesday, April 13, 2011 3:27 PM > To: mrtg > Subject: Re: [mrtg] help on SNMPv3 configurtion in .cfg > > On 4/13/11 6:21 AM, "Cihan Subasi (Garanti Teknoloji)" > <[email protected]> wrote: > > I have not been able to run snmpv3 configured .cfg file, below is mine, can > you share with us a sample .cfg or correct our mistakes below? thank you > > > WorkDir: /export/sun4_share2/testrtr > > #Options[_]:bits,growright > Options[_]:bits,growright > #Options[_]:enablesnmpv3,snmp-options=:::::3,contextengineid=800000090300001BD53DB640 > EnableSnmpV3: yes > Xsize[_]: 550 > Ysize[_]: 250 > Ytics[_]: 10 > Withpeak[_]: ym > #Suppress[_]: y > Interval: 6 > > # > Target[testrtr-s0101]: \Serial0/1/0\:1:[email protected]:::::3 > SnmpOptions[testrtr-s0101]: > username=>'xxxxxx',authprotocol=>'md5',authkey=>'0x80b746aa503f97bf37e1d93e90438d24',privprotocol=>'3d > es',privkey=>'0x80b746aa503f97bf37e1d93e90438d24daf8f544b59d592dea3aac0de8cbbbb0',contextengineid=>'800000090300001BD5FDB000',privpa > ssword=>'yyyyyyyy' > > If you are using authkey and privkey, you don’t need privpassword or > contextengineid, as the privkey is the hash of the privpassword and the > contextengineid > > > I’ll also note this from the Net-SNMP 5.2.0 releasenotes: > The non-core modules Crypt::DES, Digest::MD5, Digest::SHA1, and > Digest::HMAC are needed to support SNMPv3. > > In order to support the AES Cipher Algorithm as a SNMPv3 privacy > protocol, the non-core module Crypt::Rijndael is needed. > > > Here is a working sample, sanitized... > Target[router1.example.com.cpu1]: cpmCPUTotal5secRev.1&cpmCPUTotal1mi > nRev.1:[email protected]::3:1:1:3 > SnmpOptions[router1.example.com.cpu1]: > authkey=>'0xf0aba...',authprotocol=>'sha',privprotocol=>'aescfb128',username=> > 'foo',privkey=>'0x03b...’ > > > -- > Daniel J McDonald, CCIE # 2495, CISSP # 78281 > > > This message and attachments are confidential and intended solely for the > individual(s) stated in this message. If you received this message although > you are not the addressee, you are responsible to keep the message > confidential. The sender has no responsibility for the accuracy or > correctness of the information in the message and its attachments. Our > company shall have no liability for any changes or late receiving, loss of > integrity and confidentiality, viruses and any damages caused in anyway to > your computer system. > > Bu mesaj ve ekleri, mesajda gonderildigi belirtilen kisi/kisilere ozeldir ve > gizlidir. Bu mesajin muhatabi olmamaniza ragmen tarafiniza ulasmis olmasi > halinde mesaj iceriginin gizliligi ve bu gizlilik yukumlulugune uyulmasi > zorunlulugu tarafiniz icin de soz konusudur. Mesaj ve eklerinde yer alan > bilgilerin dogrulugu ve guncelligi konusunda gonderenin ya da sirketimizin > herhangi bir sorumlulugu bulunmamaktadir. Sirketimiz mesajin ve bilgilerinin > size degisiklige ugrayarak veya gec ulasmasindan, butunlugunun ve > gizliliginin korunamamasindan, virus icermesinden ve bilgisayar sisteminize > verebilecegi herhangi bir zarardan sorumlu tutulamaz. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.oetiker.ch/pipermail/mrtg/attachments/20110413/23da003d/attachment.htm > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: logo.gif > Type: image/gif > Size: 1947 bytes > Desc: not available > Url : > http://lists.oetiker.ch/pipermail/mrtg/attachments/20110413/23da003d/attachment.gif > > > ------------------------------ > > _______________________________________________ > mrtg mailing list > [email protected] > https://lists.oetiker.ch/cgi-bin/listinfo/mrtg > > > End of mrtg Digest, Vol 52, Issue 2 > ***********************************
_______________________________________________ mrtg mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
