OID VIEW Web Information

ciscoBgp4MIB	1.3.6.1.4.1.9.9.187
ciscoBgp4NotifyPrefix	1.3.6.1.4.1.9.9.187.0
cbgpFsmStateChange	1.3.6.1.4.1.9.9.187.0.1
cbgpBackwardTransition	1.3.6.1.4.1.9.9.187.0.2
cbgpPrefixThresholdExceeded	1.3.6.1.4.1.9.9.187.0.3
cbgpPrefixThresholdClear	1.3.6.1.4.1.9.9.187.0.4
ciscoBgp4MIBObjects	1.3.6.1.4.1.9.9.187.1
cbgpRoute	1.3.6.1.4.1.9.9.187.1.1
cbgpRouteTable	1.3.6.1.4.1.9.9.187.1.1.1
cbgpRouteEntry	1.3.6.1.4.1.9.9.187.1.1.1.1
cbgpRouteAfi	1.3.6.1.4.1.9.9.187.1.1.1.1.1
cbgpRouteMedPresent	1.3.6.1.4.1.9.9.187.1.1.1.1.10
cbgpRouteMultiExitDisc	1.3.6.1.4.1.9.9.187.1.1.1.1.11
cbgpRouteLocalPrefPresent	1.3.6.1.4.1.9.9.187.1.1.1.1.12
cbgpRouteLocalPref	1.3.6.1.4.1.9.9.187.1.1.1.1.13
cbgpRouteAtomicAggregate	1.3.6.1.4.1.9.9.187.1.1.1.1.14
cbgpRouteAggregatorAS	1.3.6.1.4.1.9.9.187.1.1.1.1.15
cbgpRouteAggregatorAddrType	1.3.6.1.4.1.9.9.187.1.1.1.1.16
cbgpRouteAggregatorAddr	1.3.6.1.4.1.9.9.187.1.1.1.1.17
cbgpRouteBest	1.3.6.1.4.1.9.9.187.1.1.1.1.18
cbgpRouteUnknownAttr	1.3.6.1.4.1.9.9.187.1.1.1.1.19
cbgpRouteSafi	1.3.6.1.4.1.9.9.187.1.1.1.1.2
cbgpRoutePeerType	1.3.6.1.4.1.9.9.187.1.1.1.1.3
cbgpRoutePeer	1.3.6.1.4.1.9.9.187.1.1.1.1.4
cbgpRouteAddrPrefix	1.3.6.1.4.1.9.9.187.1.1.1.1.5
cbgpRouteAddrPrefixLen	1.3.6.1.4.1.9.9.187.1.1.1.1.6
cbgpRouteOrigin	1.3.6.1.4.1.9.9.187.1.1.1.1.7
cbgpRouteASPathSegment	1.3.6.1.4.1.9.9.187.1.1.1.1.8
cbgpRouteNextHop	1.3.6.1.4.1.9.9.187.1.1.1.1.9
cbgpPeer	1.3.6.1.4.1.9.9.187.1.2
cbgpPeerTable	1.3.6.1.4.1.9.9.187.1.2.1
cbgpPeerEntry	1.3.6.1.4.1.9.9.187.1.2.1.1
cbgpPeerPrefixAccepted	1.3.6.1.4.1.9.9.187.1.2.1.1.1
cbgpPeerPrefixDenied	1.3.6.1.4.1.9.9.187.1.2.1.1.2
cbgpPeerPrefixLimit	1.3.6.1.4.1.9.9.187.1.2.1.1.3
cbgpPeerPrefixAdvertised	1.3.6.1.4.1.9.9.187.1.2.1.1.4
cbgpPeerPrefixSuppressed	1.3.6.1.4.1.9.9.187.1.2.1.1.5
cbgpPeerPrefixWithdrawn	1.3.6.1.4.1.9.9.187.1.2.1.1.6
cbgpPeerLastErrorTxt	1.3.6.1.4.1.9.9.187.1.2.1.1.7
cbgpPeerPrevState	1.3.6.1.4.1.9.9.187.1.2.1.1.8
cbgpPeerCapsTable	1.3.6.1.4.1.9.9.187.1.2.2
cbgpPeerCapsEntry	1.3.6.1.4.1.9.9.187.1.2.2.1
cbgpPeerCapCode	1.3.6.1.4.1.9.9.187.1.2.2.1.1
cbgpPeerCapIndex	1.3.6.1.4.1.9.9.187.1.2.2.1.2
cbgpPeerCapValue	1.3.6.1.4.1.9.9.187.1.2.2.1.3
cbgpPeerAddrFamilyTable	1.3.6.1.4.1.9.9.187.1.2.3
cbgpPeerAddrFamilyEntry	1.3.6.1.4.1.9.9.187.1.2.3.1
cbgpPeerAddrFamilyAfi	1.3.6.1.4.1.9.9.187.1.2.3.1.1
cbgpPeerAddrFamilySafi	1.3.6.1.4.1.9.9.187.1.2.3.1.2
cbgpPeerAddrFamilyName	1.3.6.1.4.1.9.9.187.1.2.3.1.3
cbgpPeerAddrFamilyPrefixTable	1.3.6.1.4.1.9.9.187.1.2.4
cbgpPeerAddrFamilyPrefixEntry	1.3.6.1.4.1.9.9.187.1.2.4.1
cbgpPeerAcceptedPrefixes	1.3.6.1.4.1.9.9.187.1.2.4.1.1
cbgpPeerDeniedPrefixes	1.3.6.1.4.1.9.9.187.1.2.4.1.2
cbgpPeerPrefixAdminLimit	1.3.6.1.4.1.9.9.187.1.2.4.1.3
cbgpPeerPrefixThreshold	1.3.6.1.4.1.9.9.187.1.2.4.1.4
cbgpPeerPrefixClearThreshold	1.3.6.1.4.1.9.9.187.1.2.4.1.5
cbgpPeerAdvertisedPrefixes	1.3.6.1.4.1.9.9.187.1.2.4.1.6
cbgpPeerSuppressedPrefixes	1.3.6.1.4.1.9.9.187.1.2.4.1.7
cbgpPeerWithdrawnPrefixes	1.3.6.1.4.1.9.9.187.1.2.4.1.8
ciscoBgp4NotificationPrefix	1.3.6.1.4.1.9.9.187.2
ciscoBgp4MIBConformance	1.3.6.1.4.1.9.9.187.3
ciscoBgp4MIBCompliances	1.3.6.1.4.1.9.9.187.3.1
ciscoBgp4MIBCompliance	1.3.6.1.4.1.9.9.187.3.1.1
ciscoBgp4MIBComplianceRev1	1.3.6.1.4.1.9.9.187.3.1.2
ciscoBgp4MIBComplianceRev2	1.3.6.1.4.1.9.9.187.3.1.3
ciscoBgp4MIBGroups	1.3.6.1.4.1.9.9.187.3.2
ciscoBgp4RouteGroup	1.3.6.1.4.1.9.9.187.3.2.1
ciscoBgp4PeerGroup	1.3.6.1.4.1.9.9.187.3.2.2
ciscoBgp4NotificationsGroup	1.3.6.1.4.1.9.9.187.3.2.3
ciscoBgp4PeerGroup1	1.3.6.1.4.1.9.9.187.3.2.4
ciscoBgp4NotificationsGroup1	1.3.6.1.4.1.9.9.187.3.2.5

This is my CFG File.

The complete OID is 1.3.6.1.4.1.9.9.187.1.2.4.1.1.192.168.150.164.1.1
The OID of Accepted BGP Routes : 1.3.6.1.4.1.9.9.187.1.2.4.1.1
The OID of Max BGP Routes : 1.3.6.1.4.1.9.9.187.1.2.4.1.3
[well this not really important as this just to make the mrtg capturing to work, since mrtg MRTG needs to graph two variables/OIDs].
The IP Address of the BGP Peer being monitored : 192.168.150.164
The version of IP & Routing Type : 1.1 > IPv4 & Unicast.

mrtg# vi /export/cfg/bgp-prefix.cfg

WorkDir: /var/data-mrtg/bgp
LogFormat: rrdtool
PathAdd: /usr/local/bin/
LibAdd: /usr/local/lib/perl5/5.8.8
Interval: 5
Refresh: 300
Forks: 4

Options[_]: gauge, nopercent, integer
Unscaled[_]: ymwd
YLegend[_]: Number of Prefix
ShortLegend[_]:
LegendI[_]:   Received Prefixes
LegendO[_]:   Withdrawn Prefixes
Legend1[_]: Number of Accepted Prefixes
Legend2[_]: Withdrawn

### as999
Target[bgp-as999]: 1.3.6.1.4.1.9.9.187.1.2.4.1.1.192.168.150.164.1.1&1.3.6.1.4.1.9.9.187.1.2.4.1.3.192.168.150.164.1.1:public@192.168.150.129
MaxBytes[bgp-as999]: 1250
Title[bgp-as999]: BGP Prefixes AS999
PageTop[bgp-as999]:

BGP Prefixes AS999

=================== Options Information ======================
More information on : MRTG Website

gauge

Treat the values gathered from target as ‘current status’ measurements
and not as ever incrementing counters.
This would be useful to monitor things like disk space, BGP Prefixes,
processor load, temperature, and the like …

integer

Print summary lines below graph as integers without commas, if you missed this on your option… MRTG would print / plot the value with additional x.000 for example 50 prefixes > 50.000 prefixes.
nopercent

Don’t print usage percentages.

==================== Router IOS Version =======================

3750-GW#sh ver
Cisco IOS Software, 3700 Software (C3725-ADVIPSERVICESK9-M), Version 12.4(3), RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by Cisco Systems, Inc.
Compiled Fri 22-Jul-05 02:27 by hqluong

ROM: System Bootstrap, Version 12.2(8r)T2, RELEASE SOFTWARE (fc1)

3750-GW uptime is 20 weeks, 19 hours, 34 minutes
System returned to ROM by power-on
System restarted at 11:04:16 UTC Wed Mar 10 2010
System image file is “flash:c3725-advipservicesk9-mz.124-3.bin”

It’s 12.4-3 Version….

a. rahman isnaini r.sutan

============== 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

Read the rest of this entry »

MRTG RRD Intermittent Graph may caused by higher Bytes graph to be captured / plotted compared to Max Bytes set in your cfg.
Let say your real utilization is more than 200 Mbps.
Your Max Bytes set to : 25000000 > 200 Mbps

If your MRTG RRD needs to graph the traffic over 200 Mbps, it can’t.
Therefor you’ll never see the graph under 200 Mbps in which the value you’ll see : 0 byte
Anyway, your MRTG wouldn’t tell you any of error such below :

mrtg# /usr/local/bin/mrtg /export/cfg/total.cfg
ERROR: AbsMax: 25000000 is smaller than MaxBytes: 50000000

Untill you have changed your MaxBytes higher than AbsMax default values.
And [AFAIK] AbsMax by default is also : 25000000
So the solution is set your cfg file this way :

AbsMax[total]: 50000000 [just add AbsMax]
MaxBytes[total]: 50000000

Have fun with continues graph and higher graph plotted compared to previous one

a. rahman isnaini r.sutan
Thanks IPP

Negating a Normal MRTG Graph which created using MIB in a cfg file is pretty much easier.
You have to put a “-” minus on the front of Target.

“Target[customer-a]: -7:YOURNET@10.165.251.75:”

Somehow you don’t have this MIB to create a graph of customer usage.
For example, Mikrotik Traffic Shapping can be graphed using MRTG by OIDs.
Mikrotik has two OIDs for incoming and outgoing traffic separately. Not just like one MIB can graph all In/Out integrated.
Printing the OID you have :

3    bytes-in=.1.3.6.1.4.1.14988.1.1.2.1.1.2.7
bytes-out=.1.3.6.1.4.1.14988.1.1.2.1.1.8.7

Normally, using above OIDs the graph realy shows exactly in traffic & out traffic.
The order is :

Target[customer-a]: 1.3.6.1.4.1.14988.1.1.2.1.1.2.7&1.3.6.1.4.1.14988.1.1.2.1.1.8.7:YOURNET@10.165.251.75:

How to invert the graph, I tried to use negation “-” string on the front of the target.
Some of errors appeared on mrtg console which says it’s not possible to do OIDs negation.
So how to solve this is, change the target order where bytes-out on the first entry…
Just like this :

Target[customer-a]: 1.3.6.1.4.1.14988.1.1.2.1.1.8.7&1.3.6.1.4.1.14988.1.1.2.1.1.2.7:YOURNET@10.165.251.75:

You will now have an Inverted Graph [Out be In & In be Out]

a. rahman isnaini r.sutan
* Thanks to Indrajaya PP. & Ebenz Tufiq”

PFSense by default will block snmp communication to it self.

It has a real time traffic in RRD graph at Status> RRD Graphs> which shows you LAN & WAN daily, weekly, monthly and of course annually.
But for some reasons you need to capture from your own MRTG engine.

Here the steps you need to follow :

1. Create Firewall Rule in WAN Interface to allow your MRTG Engine IP Address to have access to PFSense Box’s SNMP Daemon.
2. Put on the top of everything.

3. On the Services> SNMP> set System Location, System Contact, Trap Server [MRTG Engine IP Address] and of course community string.

4. Check if your MRTG Engine IP Address blocked on SNORT blocked IP List in Services.
5. If yes, create this IP in SNORT whitelist
6. Remove This IP from SNORT blocked IP List by clicking the left ‘button’ near to IP information.

Now you should be able to pull all SNMP information from PFSense, on Open Source UTM.

a. rahman isnaini r.sutan

### Global Config Options

WorkDir: /export/www/mrtg/data
Icondir: http:/mrtg/icon/
LogFormat: rrdtool
PathAdd: /usr/local/bin/
LibAdd: /usr/local/lib/perl5/5.8.8
Interval: 1
Refresh: 300
Forks: 4

### Global Defaults

#  to get bits instead of bytes and graphs growing to the right
Options[_]: growright, bits, nopercent
Xsize[_]: 420
Ysize[_]: 100
AbsMax[_]: 25000000

###################################################################################################
# Total Traffic
##################################################################################################
Target[total]:  22:users08@172.16.24.98 +  50:sup09@11.1.24.110 + 3:users08@172.16.51.14: + 217:users08@172.16.2
4.98 + 232:users08@172.16.34.98:
MaxBytes[total]: 25000000
Title[total]: Traffic TOTAL USERS
PageTop[total]: <H1>Traffic TOTAL USERS</H1>
<TABLE>
<TR><TD>Description:</TD><TD>Total Traffic</TD></TR>
<TR><TD>Max Speed:</TD>  <TD>D: Mbps U: Mbps</TD></TR>
</TABLE>

ERROR 1:

CFG Error Unknown Option “988.1.1.2.1.1.8.777&1.3.6.1.4.1.14988.1.1.2.1.1.9.777″ on line 21 or above.
Check doc/reference.txt for Help

Solution : for a long raw, make sure to have everything continuous perfectly written, copy & paste from a notepad sometimes unix doesn’t understand. Try to edit the configuration file with proper editor and while pasting to unix console, they are not separated.

ERROR 2 :

cannot encode Object ID .3.6.1.4.1.14988.1.1.2.1.1.8.778: first subid too big in Object ID 3.6.1.4.1.14988.1.1.2.1.1.8.778 at /usr/local/bin/mrtg line 1980

Solution : check this line : 251.6 +.3.6.1.4.1.14988.1.1.2.1.1.8.778& > after “+” there should be 1.3.6.1.4… fix it (you have missed 1 character).
ERROR 3:

USE OF UNINITIALIZED VALUE in DIVISION
[Fixed by adding another OID - usualy in/out bytes - math not working only with one OID]

ERROR: Target[f1-http][_IN_] ‘1.3.6.1.4.1.14988.1.1.2.2.1.5. $target->[0]{$mode}  / 8′ (warn): Use of uninitialized value in division (/) at (eval 11) line 1.
ERROR: Target[f1-http][_OUT_] ‘1.3.6.1.4.1.14988.1.1.2.2.1.5. $target->[0]{$mode}  / 8′ (warn): Use of uninitialized value in division (/) at (eval 12) line 1.

1.3.6.1.4.1.14988.1.1.2.2.1.5.16777231:MRTG08@192.168.1.243 / 2176000 [before]

1.3.6.1.4.1.14988.1.1.2.2.1.5.16777231&1.3.6.1.4.1.14988.1.1.2.2.1.6.16777231:MRTG08@192.168.1.243 / 2176000 [after]

ERROR 4 :
SYNTAX ERROR :
[Fixed by removing ":" at the end of line 1, since using math formula no need ":" at the end]

ERROR: Target[f1-http][_IN_] ‘1.3.6.1.4.1.14988.1.1.2.2.1.5. $target->[0]{$mode}  /2176000:’ (eval): syntax error at (eval 11) line 1, near “2176000:”

ERROR: Target[f1-http][_OUT_] ‘1.3.6.1.4.1.14988.1.1.2.2.1.5. $target->[0]{$mode}  /2176000:’ (eval): syntax error at (eval 12) line 1, near “2176000:”

a. rahman isnaini r.sutan

WorkDir: /export/www/mrtg/data
Icondir: http://mrtg/icon/
LogFormat: rrdtool
PathAdd: /usr/local/bin/
LibAdd: /usr/local/lib/perl5/5.8.8
Interval: 1
Refresh: 300
Forks: 4

Options[_]: growright, bits, nopercent
Xsize[_]: 420
Ysize[_]: 100
AbsMax[_]: 25000000

# total traffic international corporate customers
##################################################################################################
Target[total-start-connect]: 1.3.6.1.4.1.14988.1.1.2.1.1.8.736&1.3.6.1.4.1.14988.1.1.2.1.1.9.736:corpo08@192.168.251.6 +  1.3.6.1.4.1.14
988.1.1.2.1.1.8.777&1.3.6.1.4.1.14988.1.1.2.1.1.9.777:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.778&1.3.6.1.4.1.14988.1.1.2.
1.1.9.778:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.735&1.3.6.1.4.1.14988.1.1.2.1.1.9.735:corpo08@192.168.251.6 + 1.3.6.1.4.1.14
988.1.1.2.1.1.8.779&1.3.6.1.4.1.14988.1.1.2.1.1.9.779:corpo08@192.168.251.6  + 1.3.6.1.4.1.14988.1.1.2.1.1.8.780&1.3.6.1.4.1.14988.1.1.2
.1.1.9.780:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.781&1.3.6.1.4.1.14988.1.1.2.1.1.9.781:corpo08@192.168.251.6 + 1.3.6.1.4.1.1
4988.1.1.2.1.1.8.749&1.3.6.1.4.1.14988.1.1.2.1.1.9.749:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.703&1.3.6.1.4.1.14988.1.1.2
.1.1.9.703:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.725&1.3.6.1.4.1.14988.1.1.2.1.1.9.725:corpo08@192.168.251.6 + 1.3.6.1.4.1.1
4988.1.1.2.1.1.8.782&1.3.6.1.4.1.14988.1.1.2.1.1.9.782:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.783&1.3.6.1.4.1.14988.1.1.2
.1.1.9.783:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.784&1.3.6.1.4.1.14988.1.1.2.1.1.9.784:corpo08@192.168.251.6 + 1.3.6.1.4.1.1
4988.1.1.2.1.1.8.779&1.3.6.1.4.1.14988.1.1.2.1.1.9.779:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.785&1.3.6.1.4.1.14988.1.1.2
.1.1.9.785:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.763&1.3.6.1.4.1.14988.1.1.2.1.1.9.763:corpo08@192.168.251.6 + 1.3.6.1.4.1.1
4988.1.1.2.1.1.8.773&1.3.6.1.4.1.14988.1.1.2.1.1.9.773:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.774&1.3.6.1.4.1.14988.1.1.2
.1.1.9.774:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.764&1.3.6.1.4.1.14988.1.1.2.1.1.9.764:corpo08@192.168.251.6 + 1.3.6.1.4.1.1
4988.1.1.2.1.1.8.695&1.3.6.1.4.1.14988.1.1.2.1.1.9.695:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.786&1.3.6.1.4.1.14988.1.1.2
.1.1.9.786:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.617&1.3.6.1.4.1.14988.1.1.2.1.1.9.617:corpo08@192.168.251.6 + 1.3.6.1.4.1.1
4988.1.1.2.1.1.8.739&1.3.6.1.4.1.14988.1.1.2.1.1.9.739:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.787&1.3.6.1.4.1.14988.1.1.2
.1.1.9.787:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.776&1.3.6.1.4.1.14988.1.1.2.1.1.9.776:corpo08@192.168.251.6 + 1.3.6.1.4.1.1
4988.1.1.2.1.1.8.788&1.3.6.1.4.1.14988.1.1.2.1.1.9.788:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.789&1.3.6.1.4.1.14988.1.1.2
.1.1.9.789:corpo08@192.168.251.6 + 1.3.6.1.4.1.14988.1.1.2.1.1.8.790&1.3.6.1.4.1.14988.1.1.2.1.1.9.790:corpo08@192.168.251.6:

Trying to run your cfg config, having this such of error :

SNMP Error:
Received SNMP response with error code
error status: noSuchName
index 1 (OID: 1.3.6.1.2.1.2.2.1.10.694)
SNMPv1_Session (remote host: “192.168.7.6″ [192.168.7.6].161)
community: “doi46″
request ID: 1833102968
PDU bufsize: 8000 bytes
timeout: 2s
retries: 5
backoff: 1)
at /usr/local/lib/perl5/site_perl/5.8.8/SNMP_util.pm line 490
SNMPGET Problem for ifInOctets.694 ifOutOctets.694 on doi46@192.168.7.6::::::v4only
at /usr/local/bin/mrtg line 1980
ERROR: Target[total-onezone][_IN_] ‘ $target->[0]{$mode}  +  $target->[1]{$mode}  +   $target->[2]{$mode}  + 1.3.6.1.4.1.14988.1.1.2.1.1.8.694& 1.3.6.1.4.1.14988.1.1.2.1.1.9. $target->[10]{$mode}  +  $target->[3]{$mode}  +   $target->[4]{$mode}  +  $target->[5]{$mode}  +  $target->[6]{$mode}  +  $target->[7]{$mode}  +  $target->[8]{$mode}  +  $target->[9]{$mode} ‘ (warn): Use of uninitialized value in concatenation (.) or string at (eval 11) line 1.
ERROR: Target[total-onezone][_OUT_] ‘ $target->[0]{$mode}  +  $target->[1]{$mode}  +   $target->[2]{$mode}  + 1.3.6.1.4.1.14988.1.1.2.1.1.8.694& 1.3.6.1.4.1.14988.1.1.2.1.1.9. $target->[10]{$mode}  +  $target->[3]{$mode}  +   $target->[4]{$mode}  +  $target->[5]{$mode}  +  $target->[6]{$mode}  +  $target->[7]{$mode}  +  $target->[8]{$mode}  +  $target->[9]{$mode} ‘ (warn): Use of uninitialized value in concatenation (.) or string at (eval 12) line 1.

Action : Please check your config (OID) and Remove ’space’ betwen & (make sure no space).

1.3.6.1.4.1.14988.1.1.2.1.1.8.694& 1.3.6.1.4.1.14988.1.1.2.1.1.9.694
1.3.6.1.4.1.14988.1.1.2.1.1.8.694&1.3.6.1.4.1.14988.1.1.2.1.1.9.694

Should work

a. rahman isnaini r.sutan