Help finding an OID

Help finding an OID

Post by Christopher Johns » Fri, 18 Apr 2003 06:41:10



I'm using MRTG and would like to graph the traffic being passed
through a particular frame-relay DLCI.  Can anyone help me ascertain
the proper OID to use in my MRTG config?  I'm specifically looking to
monitor the individual "frame-relay map bridge" items under interface
Serial0.1 multipoint. (This is a Cisco 2501.)

An actual OID that will work would be great.  Or, if you'd rather
"teach a man to fish," can someone point me to a fairly
straightforward tutorial on how to drill down through a Cisco 2501's
MIB's and generate the proper OID so that MRTG can monitor it?  I
can't seem to find anything like that...

TIA,
-Chris

Here's a config similar to what I'm using... (The IP address have been
modified to protect the innocent.)

!
interface Serial0
 description BACKHAUL
 no ip address
 no ip directed-broadcast
 encapsulation frame-relay IETF
 no ip route-cache
 no ip mroute-cache
 keepalive 8
 frame-relay lmi-type ansi
!
interface Serial0.1 multipoint
 description BACKHAUL BRIDGE COMPONENT
 no ip directed-broadcast
 no ip route-cache
 no ip mroute-cache
 frame-relay map bridge 71 IETF
 frame-relay map bridge 64 IETF
 frame-relay map bridge 65 IETF
 frame-relay map bridge 66 IETF
 frame-relay map bridge 67 IETF
 frame-relay map bridge 68 IETF
 frame-relay map bridge 69 IETF
 frame-relay map bridge 56 IETF
 bridge-group 2
!
interface Serial0.2 multipoint
 description BACKHAUL IP COMPONENT
 ip address 192.168.54.65 255.255.255.192 secondary
 ip address 192.168.54.129 255.255.255.192
 no ip directed-broadcast
 no ip route-cache
 no ip mroute-cache
 frame-relay map ip 192.168.54.70 61 broadcast IETF
 frame-relay map ip 192.168.54.135 39 broadcast IETF
 frame-relay map ip 192.168.54.72 62 broadcast IETF
 frame-relay map ip 192.168.54.73 63 broadcast IETF
 frame-relay map ip 192.168.54.139 42 broadcast IETF
 frame-relay map ip 192.168.54.140 43 broadcast IETF
 frame-relay map ip 192.168.54.141 44 broadcast IETF
 frame-relay map ip 192.168.54.143 47 broadcast IETF
 frame-relay map ip 192.168.54.146 50 broadcast IETF
 frame-relay map ip 192.168.54.147 51 broadcast IETF
 frame-relay map ip 192.168.54.148 52 broadcast IETF
 frame-relay map ip 192.168.54.149 54 broadcast IETF
 frame-relay map ip 192.168.54.150 55 broadcast IETF
 frame-relay map ip 192.168.54.151 57 broadcast IETF
 frame-relay map ip 192.168.54.152 70 broadcast IETF
 frame-relay map ip 192.168.54.153 72 broadcast IETF
 frame-relay map ip 192.168.54.130 32 broadcast IETF
 frame-relay map ip 192.168.54.66 58 broadcast IETF
 frame-relay map ip 192.168.54.131 34 broadcast IETF
 frame-relay map ip 192.168.54.67 59 broadcast IETF
 frame-relay map ip 192.168.54.132 35 broadcast IETF
 frame-relay map ip 192.168.54.68 60 broadcast IETF
!
interface Serial1
 description No LONGER IN USE
 no ip address
 no ip directed-broadcast
 no keepalive
 shutdown
!
interface BVI2
 ip address 192.168.54.1 255.255.255.192
!
bridge irb
bridge 1 protocol ieee
 bridge 1 route ip
bridge 2 protocol ieee
 bridge 2 route ip
!

 
 
 

Help finding an OID

Post by <i.. » Fri, 18 Apr 2003 08:18:28


Don't know the specific OID, but you could try a SNMPWALK uTil to find out
if you haven't already tried. I think Solarwind have some pretty good Win32
based SNMP utils.


Quote:> I'm using MRTG and would like to graph the traffic being passed
> through a particular frame-relay DLCI.  Can anyone help me ascertain
> the proper OID to use in my MRTG config?  I'm specifically looking to
> monitor the individual "frame-relay map bridge" items under interface
> Serial0.1 multipoint. (This is a Cisco 2501.)

> An actual OID that will work would be great.  Or, if you'd rather
> "teach a man to fish," can someone point me to a fairly
> straightforward tutorial on how to drill down through a Cisco 2501's
> MIB's and generate the proper OID so that MRTG can monitor it?  I
> can't seem to find anything like that...

> TIA,
> -Chris

> Here's a config similar to what I'm using... (The IP address have been
> modified to protect the innocent.)

> !
> interface Serial0
>  description BACKHAUL
>  no ip address
>  no ip directed-broadcast
>  encapsulation frame-relay IETF
>  no ip route-cache
>  no ip mroute-cache
>  keepalive 8
>  frame-relay lmi-type ansi
> !
> interface Serial0.1 multipoint
>  description BACKHAUL BRIDGE COMPONENT
>  no ip directed-broadcast
>  no ip route-cache
>  no ip mroute-cache
>  frame-relay map bridge 71 IETF
>  frame-relay map bridge 64 IETF
>  frame-relay map bridge 65 IETF
>  frame-relay map bridge 66 IETF
>  frame-relay map bridge 67 IETF
>  frame-relay map bridge 68 IETF
>  frame-relay map bridge 69 IETF
>  frame-relay map bridge 56 IETF
>  bridge-group 2
> !
> interface Serial0.2 multipoint
>  description BACKHAUL IP COMPONENT
>  ip address 192.168.54.65 255.255.255.192 secondary
>  ip address 192.168.54.129 255.255.255.192
>  no ip directed-broadcast
>  no ip route-cache
>  no ip mroute-cache
>  frame-relay map ip 192.168.54.70 61 broadcast IETF
>  frame-relay map ip 192.168.54.135 39 broadcast IETF
>  frame-relay map ip 192.168.54.72 62 broadcast IETF
>  frame-relay map ip 192.168.54.73 63 broadcast IETF
>  frame-relay map ip 192.168.54.139 42 broadcast IETF
>  frame-relay map ip 192.168.54.140 43 broadcast IETF
>  frame-relay map ip 192.168.54.141 44 broadcast IETF
>  frame-relay map ip 192.168.54.143 47 broadcast IETF
>  frame-relay map ip 192.168.54.146 50 broadcast IETF
>  frame-relay map ip 192.168.54.147 51 broadcast IETF
>  frame-relay map ip 192.168.54.148 52 broadcast IETF
>  frame-relay map ip 192.168.54.149 54 broadcast IETF
>  frame-relay map ip 192.168.54.150 55 broadcast IETF
>  frame-relay map ip 192.168.54.151 57 broadcast IETF
>  frame-relay map ip 192.168.54.152 70 broadcast IETF
>  frame-relay map ip 192.168.54.153 72 broadcast IETF
>  frame-relay map ip 192.168.54.130 32 broadcast IETF
>  frame-relay map ip 192.168.54.66 58 broadcast IETF
>  frame-relay map ip 192.168.54.131 34 broadcast IETF
>  frame-relay map ip 192.168.54.67 59 broadcast IETF
>  frame-relay map ip 192.168.54.132 35 broadcast IETF
>  frame-relay map ip 192.168.54.68 60 broadcast IETF
> !
> interface Serial1
>  description No LONGER IN USE
>  no ip address
>  no ip directed-broadcast
>  no keepalive
>  shutdown
> !
> interface BVI2
>  ip address 192.168.54.1 255.255.255.192
> !
> bridge irb
> bridge 1 protocol ieee
>  bridge 1 route ip
> bridge 2 protocol ieee
>  bridge 2 route ip
> !


 
 
 

Help finding an OID

Post by Anonymou » Sun, 27 Apr 2003 05:16:02


Download a copy of getif and see if you can find it from there. Search
Google for GetIF


Quote:> I'm using MRTG and would like to graph the traffic being passed
> through a particular frame-relay DLCI.  Can anyone help me ascertain
> the proper OID to use in my MRTG config?  I'm specifically looking to
> monitor the individual "frame-relay map bridge" items under interface
> Serial0.1 multipoint. (This is a Cisco 2501.)

> An actual OID that will work would be great.  Or, if you'd rather
> "teach a man to fish," can someone point me to a fairly
> straightforward tutorial on how to drill down through a Cisco 2501's
> MIB's and generate the proper OID so that MRTG can monitor it?  I
> can't seem to find anything like that...

> TIA,
> -Chris

> Here's a config similar to what I'm using... (The IP address have been
> modified to protect the innocent.)

> !
> interface Serial0
>  description BACKHAUL
>  no ip address
>  no ip directed-broadcast
>  encapsulation frame-relay IETF
>  no ip route-cache
>  no ip mroute-cache
>  keepalive 8
>  frame-relay lmi-type ansi
> !
> interface Serial0.1 multipoint
>  description BACKHAUL BRIDGE COMPONENT
>  no ip directed-broadcast
>  no ip route-cache
>  no ip mroute-cache
>  frame-relay map bridge 71 IETF
>  frame-relay map bridge 64 IETF
>  frame-relay map bridge 65 IETF
>  frame-relay map bridge 66 IETF
>  frame-relay map bridge 67 IETF
>  frame-relay map bridge 68 IETF
>  frame-relay map bridge 69 IETF
>  frame-relay map bridge 56 IETF
>  bridge-group 2
> !
> interface Serial0.2 multipoint
>  description BACKHAUL IP COMPONENT
>  ip address 192.168.54.65 255.255.255.192 secondary
>  ip address 192.168.54.129 255.255.255.192
>  no ip directed-broadcast
>  no ip route-cache
>  no ip mroute-cache
>  frame-relay map ip 192.168.54.70 61 broadcast IETF
>  frame-relay map ip 192.168.54.135 39 broadcast IETF
>  frame-relay map ip 192.168.54.72 62 broadcast IETF
>  frame-relay map ip 192.168.54.73 63 broadcast IETF
>  frame-relay map ip 192.168.54.139 42 broadcast IETF
>  frame-relay map ip 192.168.54.140 43 broadcast IETF
>  frame-relay map ip 192.168.54.141 44 broadcast IETF
>  frame-relay map ip 192.168.54.143 47 broadcast IETF
>  frame-relay map ip 192.168.54.146 50 broadcast IETF
>  frame-relay map ip 192.168.54.147 51 broadcast IETF
>  frame-relay map ip 192.168.54.148 52 broadcast IETF
>  frame-relay map ip 192.168.54.149 54 broadcast IETF
>  frame-relay map ip 192.168.54.150 55 broadcast IETF
>  frame-relay map ip 192.168.54.151 57 broadcast IETF
>  frame-relay map ip 192.168.54.152 70 broadcast IETF
>  frame-relay map ip 192.168.54.153 72 broadcast IETF
>  frame-relay map ip 192.168.54.130 32 broadcast IETF
>  frame-relay map ip 192.168.54.66 58 broadcast IETF
>  frame-relay map ip 192.168.54.131 34 broadcast IETF
>  frame-relay map ip 192.168.54.67 59 broadcast IETF
>  frame-relay map ip 192.168.54.132 35 broadcast IETF
>  frame-relay map ip 192.168.54.68 60 broadcast IETF
> !
> interface Serial1
>  description No LONGER IN USE
>  no ip address
>  no ip directed-broadcast
>  no keepalive
>  shutdown
> !
> interface BVI2
>  ip address 192.168.54.1 255.255.255.192
> !
> bridge irb
> bridge 1 protocol ieee
>  bridge 1 route ip
> bridge 2 protocol ieee
>  bridge 2 route ip
> !