Hi Folks, I am still awaited for your reply on the below said issue.
Thanks in advance. Regards, Sagar Kupati On Thu, Jul 31, 2014 at 6:47 PM, Sagar Kupati <[email protected]> wrote: > Hi Team, > > Greeting for the day, > > I am facing one issue in MRTG while pulling the graphical data. > I am using cisco WS-3750 switch, one of my interface traffic is around 100 > MB where graph is pulling properly and there is no issue. > But there is one another interface traffic is around 800-900 MB and my > MRTG is not pulling the same. > I am using MRTG ver 2.16.4 > > Kindly assist. > > please find the attached graph. > > Regards, > Sagar Kupati > > > > On Tue, Jul 22, 2014 at 10:23 PM, <[email protected]> wrote: > >> 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. Re: migrating MRTG (Jay Hennigan) >> 2. Re: migrating MRTG (Ian Diddams) >> 3. Re: migrating MRTG (Alex van den Bogaerdt) >> 4. Re: migrating MRTG (Ian Diddams) >> 5. Re: migrating MRTG (Alex van den Bogaerdt) >> 6. Re: migrating MRTG (Jay Hennigan) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Mon, 21 Jul 2014 15:37:19 -0700 >> From: Jay Hennigan <[email protected]> >> Subject: Re: [mrtg] migrating MRTG >> To: [email protected] >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset=windows-1252 >> >> On 7/21/14 9:04 AM, Ian Diddams wrote: >> > I?m moving MRTG from a solaris box to a linux (centos 6) server, running >> > mrtg 2.17.4 as a fresh installation. >> > >> > It?s all working fine BUT ? I would rather like the old history from >> > the previous server to be migrated too, so that we get the full >> > last-year-graph as well. >> > >> > I?ve tested an idea for the cpu logs we have by concatenation the old >> > file beneath the new file? but while I can see from the epoch dates in >> > it the logged data is ?there? it doesn?t result in a yearly/monthly file >> > etc. >> > >> > What need I be doing to achieve this? >> >> Assuming classic MRTG, most likely just wait. If you did the >> concatenation correctly by removing the top line and any duplicate lines >> so that the entries are in correct order, it will work. If not, you'll >> get a log error about the file not being in sorted order. >> >> However, the weekly graph is generated every 30 minutes, the monthly >> graph every two hours, and the yearly just once a day so you will need >> to wait for them to be generated. >> >> -- >> Jay Hennigan - CCIE #7880 - Network Engineering - [email protected] >> Impulse Internet Service - http://www.impulse.net/ >> Your local telephone and internet company - 805 884-6323 - WB6RDV >> >> >> >> ------------------------------ >> >> Message: 2 >> Date: Tue, 22 Jul 2014 10:07:09 +0100 >> From: Ian Diddams <[email protected]> >> Subject: Re: [mrtg] migrating MRTG >> To: "'Jay Hennigan'" <[email protected]>, "[email protected]" >> <[email protected]> >> Message-ID: >> < >> 6ac8a3c3272c414cad402086507233bf67b92...@issexch01.win.issolutions.co.uk> >> >> Content-Type: text/plain; charset="us-ascii" >> >> Thanks for that Jay. >> >> >Assuming classic MRTG, most likely just wait. >> Something is clearly not correct because this has been running for over a >> week now without any history showing n the graphs. >> >> When you say >> >> >If you did the concatenation correctly by removing the top line >> >> The top[ line of the "old" log, or the "new" one? Or both? >> >> >> Cheers >> >> Ian >> >> Disclaimer: >> >> This message is intended for the addressee only. It may contain >> information of a confidential or legally privileged nature. If you have >> received this message in error please notify the sender and destroy the >> message immediately. All attachments have been scanned for viruses. However >> IS Solutions plc cannot accept liability for any loss or damage you may >> incur as a result of virus infection. >> >> >> >> ------------------------------ >> >> Message: 3 >> Date: Tue, 22 Jul 2014 16:12:23 +0200 >> From: "Alex van den Bogaerdt" <[email protected]> >> Subject: Re: [mrtg] migrating MRTG >> To: <[email protected]> >> Message-ID: <51D6AFA8C9CB4E74A242C1B04B93ED72@DESK> >> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; >> reply-type=original >> >> >> ----- Original Message ----- >> From: "Ian Diddams" <[email protected]> >> To: "'Jay Hennigan'" <[email protected]>; <[email protected]> >> Sent: Tuesday, July 22, 2014 11:07 AM >> Subject: Re: [mrtg] migrating MRTG >> >> >> > Thanks for that Jay. >> > >> >>Assuming classic MRTG, most likely just wait. >> > Something is clearly not correct because this has been running for over >> a >> > week now without any history showing n the graphs. >> >> Is the old server still running? If so, do the following. Do a couple of >> iterations and script it so that you can do this excercise fast, inbetween >> two MRTG runs. >> >> Wait some time for comments on this email, and test the procedure well, as >> it has been years ago since I performed this action. Things may have >> changed, including my memory. >> >> 1: run mrtg once on the old server, simultaneously with the new server. >> This is important, doing this will sync the 2 files' timestamps. >> The goal is to have lines 3 and beyond look the same, except for the >> actual >> rates. >> >> 2: find the line where the old server still had data >> 3: generate a new file from two parts: >> 3a: the new file, upto but not including the line found in (1) >> 3b: the old file, from the line found in (1) and beyond (= older) >> >> Once you are confident that you did steps 1..3 right and you end up with a >> valid log file: >> 4: replace the log file on the new server with the one you just created >> 5: delete the graphs >> 6: wait until MRTG runs again, and look at the newly created images >> >> It goes without saying that you should make copies of your files before >> screwing up, so that you can revert this action and try again. >> >> HTH >> Alex >> >> >> >> ------------------------------ >> >> Message: 4 >> Date: Tue, 22 Jul 2014 15:16:18 +0100 >> From: Ian Diddams <[email protected]> >> Subject: Re: [mrtg] migrating MRTG >> To: "'Alex van den Bogaerdt'" <[email protected]>, >> "[email protected]" <[email protected]> >> Message-ID: >> < >> 6ac8a3c3272c414cad402086507233bf67b92...@issexch01.win.issolutions.co.uk> >> >> Content-Type: text/plain; charset="us-ascii" >> >> Unfortunately the old server is very dead. >> >> In a nutshell I've inherited a few mrtg servers, all set up by the same >> bloke quite some ago, with no documentation from him how he did it. This >> one has died a death so all I have is backups of the files from it etc >> >> Cheers >> >> ian >> >> >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On >> Behalf Of Alex van den Bogaerdt >> Sent: 22 July 2014 15:12 >> To: [email protected] >> Subject: Re: [mrtg] migrating MRTG >> >> >> ----- Original Message ----- >> From: "Ian Diddams" <[email protected]> >> To: "'Jay Hennigan'" <[email protected]>; <[email protected]> >> Sent: Tuesday, July 22, 2014 11:07 AM >> Subject: Re: [mrtg] migrating MRTG >> >> >> > Thanks for that Jay. >> > >> >>Assuming classic MRTG, most likely just wait. >> > Something is clearly not correct because this has been running for over >> a >> > week now without any history showing n the graphs. >> >> Is the old server still running? If so, do the following. Do a couple of >> iterations and script it so that you can do this excercise fast, inbetween >> two MRTG runs. >> >> Wait some time for comments on this email, and test the procedure well, as >> it has been years ago since I performed this action. Things may have >> changed, including my memory. >> >> 1: run mrtg once on the old server, simultaneously with the new server. >> This is important, doing this will sync the 2 files' timestamps. >> The goal is to have lines 3 and beyond look the same, except for the >> actual >> rates. >> >> 2: find the line where the old server still had data >> 3: generate a new file from two parts: >> 3a: the new file, upto but not including the line found in (1) >> 3b: the old file, from the line found in (1) and beyond (= older) >> >> Once you are confident that you did steps 1..3 right and you end up with a >> valid log file: >> 4: replace the log file on the new server with the one you just created >> 5: delete the graphs >> 6: wait until MRTG runs again, and look at the newly created images >> >> It goes without saying that you should make copies of your files before >> screwing up, so that you can revert this action and try again. >> >> HTH >> Alex >> >> _______________________________________________ >> mrtg mailing list >> [email protected] >> https://lists.oetiker.ch/cgi-bin/listinfo/mrtg >> >> ______________________________________________________________________ >> This email has been scanned by the Symantec Email Security.cloud service. >> For more information please visit http://www.symanteccloud.com >> ______________________________________________________________________ >> >> Disclaimer: >> >> This message is intended for the addressee only. It may contain >> information of a confidential or legally privileged nature. If you have >> received this message in error please notify the sender and destroy the >> message immediately. All attachments have been scanned for viruses. However >> IS Solutions plc cannot accept liability for any loss or damage you may >> incur as a result of virus infection. >> >> >> >> ------------------------------ >> >> Message: 5 >> Date: Tue, 22 Jul 2014 16:32:01 +0200 >> From: "Alex van den Bogaerdt" <[email protected]> >> Subject: Re: [mrtg] migrating MRTG >> To: <[email protected]> >> Message-ID: <C7205BCDFBE3495080036B74041E301A@DESK> >> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; >> reply-type=original >> >> Not a problem. >> Create a duplicate of your current mrtg target. >> Replace the .log file and the .old file with those from your backup. >> Then proceed as I described below. >> >> ----- Original Message ----- >> From: "Ian Diddams" <[email protected]> >> To: "'Alex van den Bogaerdt'" <[email protected]>; >> <[email protected]> >> Sent: Tuesday, July 22, 2014 4:16 PM >> Subject: RE: [mrtg] migrating MRTG >> >> >> Unfortunately the old server is very dead. >> >> In a nutshell I've inherited a few mrtg servers, all set up by the same >> bloke quite some ago, with no documentation from him how he did it. This >> one >> has died a death so all I have is backups of the files from it etc >> >> Cheers >> >> ian >> >> >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On >> Behalf Of Alex van den Bogaerdt >> Sent: 22 July 2014 15:12 >> To: [email protected] >> Subject: Re: [mrtg] migrating MRTG >> >> >> ----- Original Message ----- >> From: "Ian Diddams" <[email protected]> >> To: "'Jay Hennigan'" <[email protected]>; <[email protected]> >> Sent: Tuesday, July 22, 2014 11:07 AM >> Subject: Re: [mrtg] migrating MRTG >> >> >> > Thanks for that Jay. >> > >> >>Assuming classic MRTG, most likely just wait. >> > Something is clearly not correct because this has been running for over >> a >> > week now without any history showing n the graphs. >> >> Is the old server still running? If so, do the following. Do a couple of >> iterations and script it so that you can do this excercise fast, inbetween >> two MRTG runs. >> >> Wait some time for comments on this email, and test the procedure well, as >> it has been years ago since I performed this action. Things may have >> changed, including my memory. >> >> 1: run mrtg once on the old server, simultaneously with the new server. >> This is important, doing this will sync the 2 files' timestamps. >> The goal is to have lines 3 and beyond look the same, except for the >> actual >> rates. >> >> 2: find the line where the old server still had data >> 3: generate a new file from two parts: >> 3a: the new file, upto but not including the line found in (1) >> 3b: the old file, from the line found in (1) and beyond (= older) >> >> Once you are confident that you did steps 1..3 right and you end up with a >> valid log file: >> 4: replace the log file on the new server with the one you just created >> 5: delete the graphs >> 6: wait until MRTG runs again, and look at the newly created images >> >> It goes without saying that you should make copies of your files before >> screwing up, so that you can revert this action and try again. >> >> HTH >> Alex >> >> _______________________________________________ >> mrtg mailing list >> [email protected] >> https://lists.oetiker.ch/cgi-bin/listinfo/mrtg >> >> ______________________________________________________________________ >> This email has been scanned by the Symantec Email Security.cloud service. >> For more information please visit http://www.symanteccloud.com >> ______________________________________________________________________ >> >> Disclaimer: >> >> This message is intended for the addressee only. It may contain >> information >> of a confidential or legally privileged nature. If you have received this >> message in error please notify the sender and destroy the message >> immediately. All attachments have been scanned for viruses. However IS >> Solutions plc cannot accept liability for any loss or damage you may incur >> as a result of virus infection. >> >> >> >> ------------------------------ >> >> Message: 6 >> Date: Tue, 22 Jul 2014 09:53:08 -0700 >> From: Jay Hennigan <[email protected]> >> Subject: Re: [mrtg] migrating MRTG >> To: Ian Diddams <[email protected]>, >> "[email protected]" <[email protected]> >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> On 7/22/14 2:07 AM, Ian Diddams wrote: >> > Thanks for that Jay. >> > >> >> Assuming classic MRTG, most likely just wait. >> > Something is clearly not correct because this has been running for over >> a week now without any history showing n the graphs. >> > >> > When you say >> > >> >> If you did the concatenation correctly by removing the top line >> > >> > The top[ line of the "old" log, or the "new" one? Or both? >> >> The top line of the old log, and any duplicate timestamps between the >> two, throw out the invalid or zero ones. >> >> What you want is to have a file where the top line is essentially "now" >> in terms of UNIX timestamp and has three integers, timestamp plus two >> data points. Below that are timestamps going back in history >> (decreasing numbers) each with five integers, timestamp followed by four >> data points. >> >> What I do: >> >> On "new" logfile, leave beginning intact. You'll find a point where >> that instance started and everything below it has just a timestamp >> followed by four zeros. Delete the lines with zeros. >> >> On the "old" logfile, delete all lines from the beginning up to and >> including the last timestamp in the "new" file so that no timestamps are >> duplicated or overlap. >> >> Concatenate them with the new file first, and replace the .log and .old >> with this result. >> >> Wait five minutes, 30 minutes. two hours, and one day for all graphs to >> generate. >> >> >> >> -- >> -- >> Jay Hennigan - CCIE #7880 - Network Engineering - [email protected] >> Impulse Internet Service - http://www.impulse.net/ >> Your local telephone and internet company - 805 884-6323 - WB6RDV >> >> >> >> ------------------------------ >> >> _______________________________________________ >> mrtg mailing list >> [email protected] >> https://lists.oetiker.ch/cgi-bin/listinfo/mrtg >> >> >> End of mrtg Digest, Vol 90, Issue 3 >> *********************************** >> > >
_______________________________________________ mrtg mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
