> But now,I'm having trouble monitoring the switches by VPI/VCI. I've actually 
> tried getting the data by using OIDs. Here's how I do it :
> 
> "OID_1.<port_number>&OID_2.<port_number>:Community_name@IP_address."
> 

First, it is not really a port number. Keep that in mind. It is an instance
and you should think of it as an index into an array. It may or may not
equal your port numbers.

The format you used looks okay (that is, if you do not enter OID but
translate this into numbers and dots).

Make sure to use an external tool such as snmpget, snmpwalk, snmputil
or whatever comes to hand. If you can collect data with this, you can
do it with mrtg.

You could check the OID used by doing:

          snmpget ip_address community_name .OID_1.instance

(mind the leading dot that should be added for snmpget, it is NOT part
of the OID and should NOT be used inside MRTG)

If this returns an error, you may be able to figure out why.

Try "snmpget address community .1.3.6.1.2.1.1.1.0" to see if the device
responds to queries. Use "snmpwalk address community .1.3.6.1.2.1.2.2.1.2"
to get interface descriptions (not always useful).

Inside mrtg.cfg, you could change

  Target[x]: 1:public@router
into
  Target[x]: 1.3.6.1.2.1.2.2.1.10.1&1.3.6.1.2.1.2.2.1.16.1:public@router

without really changing anything.

Regards,
Alex

--
* To unsubscribe from the mrtg mailing list, send a message with the
  subject: unsubscribe to mrtg-request@list.ee.ethz.ch
* The mailing list archive is at http://www.ee.ethz.ch/~slist/mrtg