ip-stories.com

  •  

    September 2010
    M T W T F S S
    « Aug    
     12345
    6789101112
    13141516171819
    20212223242526
    27282930  
  • Web Stat Counter

    • Search This Blog :

    • Add url
    • Add Me on FB

      Rahman Isnaini's Facebook profile
    • Hurricane Electric IPv6 Cert

      IPv6 Certification Badge for risnaini
    • comments

    • Visitors Referred From :

    • Geo Stats

    • Categories

    [SNMP/MRTG] How to Graph Summary of Multiple MIBs over than 650 Mbps

    Posted by admin on July 27th, 2010

    ============== Captured from Cisco Web FAQ ==============

    Q. When should 64-bit counters be used?

    A. RFC 2233 leavingcisco.com adopted expanded 64-bit counters for high capacity interfaces in which 32-bit counters do not provide enough capacity and wrap too fast.

    As the speed of network media increases, the minimum time in which a 32-bit counter wraps decreases. For example, a 10 Mbps stream of back-to-back, full-size packets causes ifInOctets to wrap in just over 57 minutes. At 100 Mbps, the minimum wrap time is 5.7 minutes, and at 1 Gbps, the minimum is 34 seconds.

    Note: The SNMP counters wrap, the command line interface (CLI) counters do not.

    For interfaces that operate at 20,000,000 (20 million) bits per second or less, you must use 32-bit byte and packet counters. For interfaces that operate faster than 20 million bits per second, and slower than 650,000,000 bits per second, you must use 32-bit packet counters and 64-bit octet counters. For interfaces that operate at 650,000,000 bits/second or faster, 64-bit packet and octet counters must be used.

    Correspondingly, Cisco IOS® Software does not support 64-bit counters for interface speeds of less than 20 Mbps. This means that 64-bit counters are not supported on 10 Mb Ethernet ports, only 100 Mb Fast-Ethernet and other high speed ports support 64-bit counters.
    ===================================================================================

    Lately I have a problem with Adding multiple MIB traffic from many devices with many interfaces.
    The purpose is to summarize all of interface traffic volume.
    The problem I have faced was : if the total / summary of all traffic volume more than 650 Mbps [650,000,000 bit/seconds], the graph starts to drop / broken / not smooth.

    So We never saw the real of total traffic in that graph.
    By Default my mrtg engine use snmp v1 to capture dan plot MIB into the graph.
    According to above Cisco Website, I need to change the 32 bit counter to 64 bit counter to graph the traffic above 650 Mbit per second.
    Googling around, We have to add the suffix at the end of MIB in MRTG CFG file with “:::::2″ which means that my engine is now capturing 64 bit counter information [MIB] with version 2.

    There you go :)

    Target[total-traffic]: 10001:public@192.168.3.250:::::2 + 10002:public@192.168.3.250:::::2 + 10003:public@192.168.3.250:::::2 + 10004:public@192.168.3.250:::::2 + 10005:public@192.168.3.250:::::2  +  10006:public@192.168.3.250:::::2 + 10007:public@192.168.3.250:::::2 + 10008:public@192.168.3.250:::::2 + 10009:public@192.168.3.250:::::2 + 10010:public@192.168.3.250:::::2 + 10011:public@192.168.3.250:::::2 + 10012:public@192.168.3.250:::::2 + 10013:public@192.168.3.250:::::2 + 10014:public@192.168.3.250:::::2 + 10015:public@192.168.3.250:::::2 + 10016:public@192.168.3.250:::::2 + 10017:public@192.168.3.250:::::2 + 10018:public@192.168.3.250:::::2 + 10019:public@192.168.3.250:::::2 + 10020:public@192.168.3.250:::::2 + 10021:public@192.168.3.250:::::2 + 10022:public@192.168.3.250:::::2 + 10023:public@192.168.3.250:::::2 + 10024:public@192.168.3.250:::::2 + 10025:public@192.168.3.250:::::2 + 10026:public@192.168.3.250:::::2 + 10027:public@192.168.3.250:::::2 + 10028:public@192.168.3.250:::::2 + 10029:public@192.168.3.250:::::2 + 10030:public@192.168.3.250:::::2 + 10031:public@192.168.3.250:::::2 + 10032:public@192.168.3.250:::::2 + 10033:public@192.168.3.250:::::2 + 10034:public@192.168.3.250:::::2 + 10035:public@192.168.3.250:::::2 + 10036:public@192.168.3.250:::::2 + 10037:public@192.168.3.250:::::2 + 10038:public@192.168.3.250:::::2 + 10039:public@192.168.3.250:::::2 + 10040:public@192.168.3.250:::::2 + 10041:public@192.168.3.250:::::2 + 10042:public@192.168.3.250:::::2 + 10043:public@192.168.3.250:::::2 + 10044:public@192.168.3.250:::::2 + 10045:public@192.168.3.250:::::2 + 10046:public@192.168.3.250:::::2 + 10047:public@192.168.3.250:::::2 + 10048:public@192.168.3.250:::::2 + 10101:public@192.168.3.250:::::2 + 10102:public@192.168.3.250:::::2 + 10103:public@192.168.3.250:::::2 + 10104:public@192.168.3.250:::::2 + 1:public@192.168.3.252:::::2 + 5001:public@192.168.3.252:::::2 + 10001:public@192.168.3.252:::::2 + 10002:public@192.168.3.252:::::2 + 10003:public@192.168.3.252:::::2 + 10004:public@192.168.3.252:::::2 + 10005:public@192.168.3.252:::::2 + 10006:public@192.168.3.252:::::2 + 10007:public@192.168.3.252:::::2 + 10008:public@192.168.3.252:::::2 + 10009:public@192.168.3.252:::::2 + 10010:public@192.168.3.252:::::2 + 10011:public@192.168.3.252:::::2 + 10012:public@192.168.3.252:::::2 + 10013:public@192.168.3.252:::::2 + 10014:public@192.168.3.252:::::2 + 10015:public@192.168.3.252:::::2 + 10016:public@192.168.3.252:::::2 + 10017:public@192.168.3.252:::::2 + 10018:public@192.168.3.252:::::2 + 10019:public@192.168.3.252:::::2 + 10020:public@192.168.3.252:::::2 + 10021:public@192.168.3.252:::::2 + 10022:public@192.168.3.252:::::2 + 10023:public@192.168.3.252:::::2 + 10024:public@192.168.3.252:::::2 + 10025:public@192.168.3.252:::::2 + 10026:public@192.168.3.252:::::2 + 10027:public@192.168.3.252:::::2 + 10028:public@192.168.3.252:::::2 + 10029:public@192.168.3.252:::::2 + 10030:public@192.168.3.252:::::2 + 10031:public@192.168.3.252:::::2 + 10032:public@192.168.3.252:::::2 + 10033:public@192.168.3.252:::::2 + 10034:public@192.168.3.252:::::2 + 10035:public@192.168.3.252:::::2 + 10036:public@192.168.3.252:::::2 + 10037:public@192.168.3.252:::::2 + 10038:public@192.168.3.252:::::2 + 10039:public@192.168.3.252:::::2 + 10040:public@192.168.3.252:::::2 + 10041:public@192.168.3.252:::::2 + 10042:public@192.168.3.252:::::2 + 10043:public@192.168.3.252:::::2 + 10101:public@192.168.3.252:::::2 + 10102:public@192.168.3.252:::::2 + 10103:public@192.168.3.252:::::2

    Please also check if your device support 64-bit counter by :

    mrtg# snmpwalk -v2c -c public 192.168.3.252 ifhcinoctets
    IF-MIB::ifHCInOctets.1 = Counter64: 5271839511
    IF-MIB::ifHCInOctets.5001 = Counter64: 19285262324965
    IF-MIB::ifHCInOctets.10001 = Counter64: 12919676483968
    IF-MIB::ifHCInOctets.10002 = Counter64: 3459432192332
    IF-MIB::ifHCInOctets.10003 = Counter64: 1281890169832
    IF-MIB::ifHCInOctets.10004 = Counter64: 1153220135
    IF-MIB::ifHCInOctets.10005 = Counter64: 0
    IF-MIB::ifHCInOctets.10006 = Counter64: 33399470170
    IF-MIB::ifHCInOctets.10007 = Counter64: 0
    IF-MIB::ifHCInOctets.10008 = Counter64: 66275657
    IF-MIB::ifHCInOctets.10009 = Counter64: 675982530
    IF-MIB::ifHCInOctets.10010 = Counter64: 272311362596
    IF-MIB::ifHCInOctets.10011 = Counter64: 67263986026
    IF-MIB::ifHCInOctets.10012 = Counter64: 91564885477
    IF-MIB::ifHCInOctets.10013 = Counter64: 11703694
    IF-MIB::ifHCInOctets.10014 = Counter64: 1111940271
    IF-MIB::ifHCInOctets.10015 = Counter64: 808087796834
    IF-MIB::ifHCInOctets.10016 = Counter64: 329951153
    IF-MIB::ifHCInOctets.10017 = Counter64: 40798389204
    IF-MIB::ifHCInOctets.10018 = Counter64: 101988149113
    IF-MIB::ifHCInOctets.10019 = Counter64: 0
    IF-MIB::ifHCInOctets.10020 = Counter64: 92328
    IF-MIB::ifHCInOctets.10021 = Counter64: 116124022657
    IF-MIB::ifHCInOctets.10022 = Counter64: 343211068
    IF-MIB::ifHCInOctets.10023 = Counter64: 0
    IF-MIB::ifHCInOctets.10024 = Counter64: 1916449367511
    IF-MIB::ifHCInOctets.10025 = Counter64: 1992573277663
    IF-MIB::ifHCInOctets.10026 = Counter64: 1608418929938
    IF-MIB::ifHCInOctets.10027 = Counter64: 93278180105
    IF-MIB::ifHCInOctets.10028 = Counter64: 2049131083512
    IF-MIB::ifHCInOctets.10029 = Counter64: 2774637437
    IF-MIB::ifHCInOctets.10030 = Counter64: 642167892888
    IF-MIB::ifHCInOctets.10031 = Counter64: 0
    IF-MIB::ifHCInOctets.10032 = Counter64: 1323638333873
    IF-MIB::ifHCInOctets.10033 = Counter64: 25097636
    IF-MIB::ifHCInOctets.10034 = Counter64: 42650627860
    IF-MIB::ifHCInOctets.10035 = Counter64: 3902264390
    IF-MIB::ifHCInOctets.10036 = Counter64: 0
    IF-MIB::ifHCInOctets.10037 = Counter64: 11049288783
    IF-MIB::ifHCInOctets.10038 = Counter64: 16960147512
    IF-MIB::ifHCInOctets.10039 = Counter64: 982641846723
    IF-MIB::ifHCInOctets.10040 = Counter64: 37731767
    IF-MIB::ifHCInOctets.10041 = Counter64: 746897661580
    IF-MIB::ifHCInOctets.10042 = Counter64: 22523459900
    IF-MIB::ifHCInOctets.10043 = Counter64: 93528554047
    IF-MIB::ifHCInOctets.10044 = Counter64: 1103749277819
    IF-MIB::ifHCInOctets.10045 = Counter64: 780476638416
    IF-MIB::ifHCInOctets.10046 = Counter64: 1573739997799
    IF-MIB::ifHCInOctets.10047 = Counter64: 1802180546511

    Note : Don’t forgot to reload your “cron” service in order to keep running periodically with the new bit counter.

    a. rahman isnaini r.sutan
    Thanks to / powered by  Jason Wanardi

    Leave a Reply

    XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>