[mrtg] RES: RES: RES: MRTG - Frame Relay

Fri Aug 9 15:47:21 MEST 2002

Hi again!!

No one could help on this situation???  I could not resolve it yet!! I think
this is a syntax error on my CFG, when the Target is specified... How must
be specified the information betwen brackets [10.1.0.10_10.203.4.1]when
using the OID to specify the target? And the other parameters, how must them
be specified? (Ex.: MaxBytes[10.1.0.10_10.203.4.1]: 8000). 
I could not find this information neither on MRTG documentation nor on last
posted messages!!

Thank´s

-----Mensagem original-----
De: Alexandre Reichert 
Enviada em: sexta-feira, 2 de agosto de 2002 16:34
Para: 'Rich Adamson'; mrtg at list.ee.ethz.ch
Assunto: [mrtg] RES: RES: MRTG - Frame Relay

Hi everyone!

I´m still trying to fix the problem on monitoring each virtual station on my
frame relay link. I verified the information of the message below, but I
still having problems.. It follows the passage of the file .conf and the
error returned. Thank´s again for any help!

(.conf)

Target[10.1.0.10_10.203.4.1]:
/1.3.6.1.2.1.10.32.2.1.7.6.703&1.3.6.1.2.1.10.32.2.1.9.6.703:hurry070up at 10.1
.0.10:
SetEnv[10.1.0.10_10.203.4.1]: MRTG_INT_IP="10.203.4.1" MRTG_INT_DESCR=""
MaxBytes[10.1.0.10_10.203.4.1]: 8000
Title[10.1.0.10_10.203.4.1]: Análise de Tráfego - PMDF
ThreshMaxI[10.1.0.10_10.203.4.1]: 90%
ThreshProgI[10.1.0.10_10.203.4.1]: c:\mrtg-2.9.18\bin\aspmaillimite.vbs
ThreshMaxO[10.1.0.10_10.203.4.1]:90%
ThreshProgO[10.1.0.10_10.203.4.1]: c:\mrtg-2.9.18\bin\aspmaillimite.vbs
ThreshProgOKI[10.1.0.10_10.203.4.1]: c:\mrtg-2.9.18\bin\aspmailOk.vbs
PageTop[10.1.0.10_10.203.4.1]: <H1>Análise de Tráfego - PMDF</H1>
 <TABLE>
   <TR><TD>Roteador:</TD>     <TD>DESEC10 - CORI</TD></TR>
   <TR><TD>Responsável:</TD>GEINF <TD></TD></TR>
   <TR><TD>Descrição:</TD><TD>  </TD></TR>
   <TR><TD>Tipo da Interface:</TD>     <TD>frame-relay (32)</TD></TR>
   <TR><TD>Nome da Interface:</TD>     <TD></TD></TR>
   <TR><TD>Velocidade Máxima:</TD>  <TD>64 Kbps</TD></TR>
   <TR><TD>Ip:</TD>         <TD>10.203.4.1 ()</TD></TR>
 </TABLE>

(error....)

ERROR: Target[10.1.0.10_10.203.4.1][_IN_] ' $$target[1]{$mode} ' did not
eval in
to defined data
ERROR: Target[10.1.0.10_10.203.4.1][_OUT_] ' $$target[1]{$mode} ' did not
eval i
nto defined data
WARNING: Skipping Update of 10.1.0.10_10.203.4.1, inlast is not defined
WARNING: Skipping Update of 10.1.0.10_10.203.4.1, outlast is not defined

Alexandre 

-----Mensagem original-----
De: Rich Adamson [mailto:radamson at routers.com]
Enviada em: terça-feira, 30 de julho de 2002 15:44
Para: mrtg at list.ee.ethz.ch
Cc: Alexandre Reichert
Assunto: Re: [mrtg] RES: MRTG - Frame Relay

Alexandre,

I believe both Cisco and 3Com use the RFC1315 Mib definitions in their
products. The OID strings would then be:
 1.3.6.1.2.1.10.32.2.1.4.x.y = FECNs Received
 1.3.6.1.2.1.10.32.2.1.5.x.y = BECNs Received
 1.3.6.1.2.1.10.32.2.1.6.x.y = Frames Sent
 1.3.6.1.2.1.10.32.2.1.7.x.y = Octets Sent
 1.3.6.1.2.1.10.32.2.1.8.x.y = Frames Received
 1.3.6.1.2.1.10.32.2.1.9.x.y = Octets Received
   where:
    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 1.3.6.1.2.1.10.32.2.1.1, you will see
those snmp interface numbers. If you do a mibwalk (getnext) on
1.3.6.1.2.1.10.32.2.1.2, you will see the DLCI numbers. If you do a
mibwalk (getnext) on 1.3.6.1.2.1.10.32.2.1.3, 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 &
BECNs.

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.

-- Attached file removed by Listar and put at URL below --
-- Type: text/plain
-- Size: 770 bytes
-- URL : http://www.ee.ethz.ch/~slist/pantomime/28-InterScan_Disclaimer.txt

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

-- Attached file removed by Listar and put at URL below --
-- Type: text/plain
-- Size: 770 bytes
-- URL : http://www.ee.ethz.ch/~slist/pantomime/32-InterScan_Disclaimer.txt

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