[mrtg] Re: RES: MRTG - Frame Relay

Rich Adamson radamson at routers.com
Tue Jul 30 20:44:06 MEST 2002


I believe both Cisco and 3Com use the RFC1315 Mib definitions in their
products. The OID strings would then be: = FECNs Received = BECNs Received = Frames Sent = Octets Sent = Frames Received = Octets Received
    x is the snmp interface number
    y is the DLCI number

If you can do a mibwalk of a router, you'll see the "snmp interface number"
associated with a readable description. For example, Serial 0/0 might be
snmp interface number 3 (or whatever). The value is determined by your
router and what interfaces you have defined on your router. No one will be
able to tell you what that value is; you have to find it.

If you do a mibwalk (getnext) on, you will see
those snmp interface numbers. If you do a mibwalk (getnext) on, you will see the DLCI numbers. If you do a
mibwalk (getnext) on, it will tell you which
DLCIs are Invalid (1), Active (2), or InActive (3). Using mrtg to poll
the Active DLCIs is what you are looking for.

I'd suggest using mrtg to chart the Octets Sent & Received, and FECNs &

Hope that helps...

> Hi Sebastian!
> I´m using both, CISCO and 3COM Netbuilder. Yes, I want to monitor each
> virtual staton. Do you know where can I get the OID´s for those equipment?
> Alexandre 
> -----Mensagem original-----
> Alexandre:
> What's the brand of your equipment? I think you must monitor each virtual
> station of your frame relay link.  This can be done easily using the
> appropriate MIBs.  I have a configuration exactly like yours and it works
> fine.

Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
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

More information about the mrtg mailing list