<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=windows-1252" http-equiv=Content-Type>
<META content="MSHTML 5.00.2314.1000" name=GENERATOR></HEAD>
<BODY>
<DIV>Well not a full config - but here's a typical 56k line, looking at DLCI 100
on port 3 :</DIV>
<DIV> </DIV>
<DIV>MRTG is reading octets from the device (Since that's what the mib supports)
so I am using the 'bits' option to multiply these values by 8 to convert to
bits. Maxbytes is set to 7000, not 56000 because we're getting values in in
Octets (56/8=7). The multiplication is done -after- the conversions - so that's
why I had to put it in as 7000.</DIV>
<DIV> </DIV>
<DIV>It works pretty good on our routers, hope it works for you.</DIV>
<DIV> </DIV>
<DIV><FONT face="Courier New">Target[foo]: <A
href="mailto:frInOctets.3.100&frOutOctets.3.100:public@1.1.1.1">frInOctets.3.100&frOutOctets.3.100:public@1.1.1.1</A></FONT></DIV>
<DIV><FONT face="Courier New">MaxBytes[foo]: 7000<BR>Title[foo]: Router
Port 3 - Frame Relay Interface DLCI 100<BR>Options[foo]: transparent bits
growright<BR>PageTop[foo]: <H1>Traffic Analysis for Frame Relay Interface
3 DLCI 100 </<BR>H1><BR> <TABLE><BR>
<TR><TD>System:</TD><TD> SuperRouter
</TD></TR><BR>
<TR><TD>Maintainer:</TD><TD> Neil Calvert
</TD></TR><BR>
<TR><TD>Interface:</TD><TD>Frame Relay Interface
(3)</TD></TR><BR>
<TR><TD>IP:</TD><TD> SuperRouter (1.1.1.1)
TD></TR><BR> <TR><TD>Max
Speed:</TD><BR> <TD>56.0 kBits/s
(frame-relay)</TD></TR><BR> </TABLE><BR>YLegend[foo]:
Bits<BR>ShortLegend[foo]: Frame Use<BR>Legend1[foo]: Incoming Traffic in Bits
per Second<BR>Legend2[foo]: Outgoing Traffic in Bits per Second<BR>Legend3[foo]:
Maximal Incoming Traffic in poll cycle<BR>Legend4[foo]: Maximal Outgoing Traffic
in poll cycle<BR>LegendI[foo]: &nbsp;Bits/s: </FONT></DIV>
<DIV><FONT face="Courier New">Legend0[foo]: &nbsp;Bits/s:
</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT size=2><FONT face="Courier New">-----Original Message-----<BR>From:
Landa, Brian <<A
href="mailto:Landa@trendcs.com">Landa@trendcs.com</A>><BR>To: Neil Calvert
<<A
href="mailto:ncalvert@cabletron.com">ncalvert@cabletron.com</A>><BR>Date:
Friday, September 24, 1999 1:28 PM<BR>Subject: RE: [mrtg] MRTG Frame Relay
graphing - frCircuitState<BR><BR></FONT></DIV></FONT>>Do you have a full
config I can look at?????<BR>> <BR>>Brian Landa<BR>>Trend Consulting
Services Inc.<BR>>Centre Plaza North, Suite #201<BR>>Eastlake, OH
44095<BR>>T: 440.942.4040 X243<BR>>F: 440.942.4848<BR>>Pager:
440.303.5426<BR>>Email: <A
href="mailto:landa@trendcs.com">landa@trendcs.com</A> < <A
href="mailto:landa@trendcs.com">mailto:landa@trendcs.com</A><BR>><<A
href="mailto:landa@trendcs.com">mailto:landa@trendcs.com</A>>
><BR>>Network Support Specialist <BR>>WE make the NET * work
<BR>><BR>><BR>>-----Original Message-----<BR>>From: Neil Calvert [<A
href="mailto:ncalvert@cabletron.com">mailto:ncalvert@cabletron.com</A>]<BR>>Sent:
Friday, September 24, 1999 11:43 AM<BR>>To: mrtglist<BR>>Subject: [mrtg]
MRTG Frame Relay graphing - frCircuitState<BR>><BR>><BR>>Hi all<BR>>
<BR>>I've been working a lot with Frame Relay devices of late, and MRTG's
been<BR>>doing well at modeling links. What would be nice is to graph the
circuit<BR>>state, too. Now this can be done out of the box using
OID<BR>>1.3.6.1.2.1.10.32.2.1.3.pp.dlci (frCircuitState). The down side is
that this<BR>>OID will return 1=invalid 2=up 3=down - kinda like
ifAdminStatus and<BR>>ifOperStatus. <BR>> <BR>>Tobi did a little hack
to 'massage' the admin and oper values so it returned<BR>>1=up and 2=down, or
otherwise hosed. Has anyone looked at this hack and<BR>>modified it to work
with frCircuitState? If not, how hard might this be? I'm<BR>>not a coder type
so I haven't rummaged through the code myself. I'd be<BR>>interested to hear
everyones thoughts on it though - for my money, a<BR>>'frCircuitHack' option
would be real useful...<BR>> <BR>> <BR>>Neil<BR>></BODY></HTML>