Thanks Matt for your comments about 64-bit counters - that seems to be the best way to go, if I can get it to work!
The two routers, I am trying to get the i/o traffic cumulative stats from, are Cisco 2611s running IOS Version 12. I made an snmpwalk version 2c query of the oids and I got only 32 bit data returned. (The data didn't change whether I made a version 1 or version 2c query :( ). Also, using an snmpwalk version 2c query, all the "Counter64" values returned had zero value. It seems there is something wrong with our Cisco setup - any pointers on what could be wrong with our setup that stops the counters I want from being 64-bit counters? Any response will be appreciated rgds Derek ##################################################### Appendix 1 - we're running slightly different version of IOS 12 on Cisco 2611 hardware platform IOS (tm) C2600 Software (C2600-IS-M), Version 12.1(3a), RELEASE SOFTWARE (fc1) IOS (tm) C2600 Software (C2600-I-M), Version 12.0(4)T, RELEASE SOFTWARE (fc1) cisco 2611 (MPC860) processor (revision 0x203) with 53248K/12288K bytes of memory. ##################################################### -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, 8 October 2003 3:54 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [mrtg] Cumulative graphing issue using "gauge" option - data wrap s > > Dear all > I am trying to graph the cumulative usage im megabytes of the ports from our > routers to our isps. So far my graphs are quite good except that the OIDs in > question that I am monitoring seem to wrap (go back to zero) after they get > to around 4000000000 bytes (2 ^ 32 bytes). Have you considered shifting to 64 bit counters? the MRTG documentation has good information on how to do that, and with most modern gear, there are 64 bit counters for every major incrementing counter, which will not wrap within the lifespan of the equipment itself. ^_^ Just something to think about. :) Matt > I was thinking that I could write a script to tweak the data that is stored > in the .log file to somehow recognise that the counter has wrapped and > simply process the .log data so that the data continues incrementing instead > of going back to zero. > I don't think this would be too hard to do with perl. > > Does any one know the best way I should integrate this script with the mrtg > apllication software so that > (i) mrtg gathers the raw data from the router and updates the .log file (ii) > my script modifies the .log data so that the counter values keep > incrementing instead of wrapping back to zero and then (iii) rateup uses the > processed .log data to make the graph. > > Appreciate anyones's response about this > > thanks > Derek > > ####################################################### > ### Interface 1x >> Descr: 'Ethernet0/0' | Name: 'Et0/0' | Ip: 'ipaddress' | > Eth: 'macaddress' ### > YLegend[routername_Et0_0x]: MegaBytes > ShortLegend[routername_Et0_0x]: Bytes > Factor[routername_Et0_0x]: 1048576 > WithPeak[routername_Et0_0x]: ymw > Options[routername_Et0_0x]: growright, gauge, nopercent > Target[routername_Et0_0x]: > .1.3.6.1.2.1.2.2.1.10.1&.1.3.6.1.2.1.2.2.1.16.1:[EMAIL PROTECTED]: / 1048576 > Directory[routername_Et0_0x]: routername > SetEnv[routername_Et0_0x]: MRTG_INT_IP="ipaddress" MRTG_INT_DESCR="" > MaxBytes[routername_Et0_0x]: 10000000000000000 > Title[routername_Et0_0x]: Ethernet0/0 -- routername - cumulative > Legend1[routername_Et0_0x]: Incoming Traffic in MegaBytes > Legend2[routername_Et0_0x]: Outgoing Traffic in MegaBytes > Legend3[routername_Et0_0x]: > Legend4[routername_Et0_0x]: > LegendI[routername_Et0_0x]: In: > LegendO[routername_Et0_0x]: Out: > PageTop[routername_Et0_0x]: <H1>Ethernet0/0 -- routername - cumulative</H1> > <TABLE> > <TR><TD>System:</TD><TD>routername</TD></TR> > <TR><TD>Description:</TD><TD>Ethernet0/0 Pub/Ext Int to Internet - > cumulative </TD></TR> > <TR><TD>ifType:</TD> <TD>ethernetCsmacd (6)</TD></TR> > <TR><TD>ifName:</TD> <TD></TD></TR> > <TR><TD>Ip:</TD> <TD>ipaddress</TD></TR> > </TABLE> > > > > **************************************************************************** ** > This email is intended for the use of the addressee only. If you receive this email in error, please delete it immediately. This email may contain information which is confidential and/or legally privileged. You must not use or disclose the contents of this email, or add the sender's email address to any database, list or mailing list unless you are expressly authorised to do so. > > The statements or views expressed in this email are those of the individual sender and are not those of Australian Associated Press Pty Ltd (AAP). These statements are not binding on AAP, except where the sender expressly and with authority, states them to be. > > AAP is unable to review the contents of all the email on its system. To the extent permitted by law, AAP disclaims all liability for any loss or damage caused by the contents of this email. > **************************************************************************** ** > > -- > Unsubscribe mailto:[EMAIL PROTECTED] > Archive http://www.ee.ethz.ch/~slist/mrtg > FAQ http://faq.mrtg.org Homepage http://www.mrtg.org > WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi > > -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
