Monitoring ADSL interfaces

Question

Hi,

I was wondering if anyone has a solution for monitoring ADSL nodes where the ATM interface has a different up/down speed. We use Cisco routers and the ifSpeed mib only reports the egress speed and then NPM puts that speed in for both receive and transmit. We can manually change them but then when the device re-syncs they may change. As we have 3000 ADSL routers modifying them each time is not feasible. Has anyone found a way to populate the ATM interface speeds automatically?. I raised a ticket (347342) but was advised that it can not be done.

Regards

Tom

amandil · Answer

Hi RichT,

Have you ever seen the router report this data backwards. IE..

adslAtucCurrAttainableRate reports the upstream data and adslAturCurrAttainableRate reports the downstream data?

I had this working on our Cisco 877's but seems to be reported backwards on the new C880 models the ISP is using...

Do you think it's me or Cisco/ISP screwing something up?

RichT · Answer

Hi Tom,

We have a similar scenario. The best method I've found so far is to set up a Universal Device Poller which queries the following ADSL-LINE-MIB objects:

adslAtucCurrAttainableRate (1.3.6.1.2.1.10.94.1.1.2.1.8) for Downstream

adslAturCurrAttainableRate (1.3.6.1.2.1.10.94.1.1.3.1.8) for Upstream

For us these are close enough to the speeds returned by the Cisco 'show dsl interface' to track the worst sites across the estate. We use the min/max history of these values to see which sites are most impacted by retraining variance.

You can pull line attenuation, SNR margin, signal losses etc. from the MIB for other general line quality reports.

HTH