in More Search Options

Bandwidth Gauge v9.2 discovery problem

Last post 04-14-2008 3:52 PM by stegad. 10 replies.
Page 1 of 1 (11 items)
Sort Posts:
  • 04-11-2008 2:40 PM

    • stegad
    • Not Ranked
    • Joined on 07-07-2007
    • Posts 9
    • Points 20

    Bandwidth Gauge v9.2 discovery problem

     I'm trying to add a gauge for a Nortel 5510-24T using generic "Public" SNMP credentials.  The credentials test ok, but on the discovery window it says "Discovering Interfaces/Ports... 24 of 40". 

    Why is it trying to discover non-existent ports?  The discovery never completes and unfortunately I don't have another 5510 around to compare with.

     Any help appreciated.
     

    • Post Points: 3
  • 04-14-2008 8:07 AM In reply to

    Re: Bandwidth Gauge v9.2 discovery problem

     Stagad - we usually get the "40" from IF-MIB:ifNumber (1.3.6.1.2.1.2.1). Is it possible the Nortel is giving us an incorrect value?

     HTH,

    Greg
     

    Greg Newman
    SolarWinds Toolset
    • Post Points: 3
  • 04-14-2008 9:38 AM In reply to

    • stegad
    • Not Ranked
    • Joined on 07-07-2007
    • Posts 9
    • Points 20

    Re: Bandwidth Gauge v9.2 discovery problem

     Hi Greg,

     Not sure.  I'll contact Nortel support and ask them.  I'll post the results.



     

    • Post Points: 3
  • 04-14-2008 10:01 AM In reply to

    Re: Bandwidth Gauge v9.2 discovery problem

     stegad - Could you use the SNMP MIB Browser to query the MIB and verify that the device is giving us the value of 40?

     Thanks,

    Greg
     

    Greg Newman
    SolarWinds Toolset
    • Post Points: 3
  • 04-14-2008 2:26 PM In reply to

    • stegad
    • Not Ranked
    • Joined on 07-07-2007
    • Posts 9
    • Points 20

    Re: Bandwidth Gauge v9.2 discovery problem

    Unless I'm reading it wrong, yes, the value is "40".

    Is there anything I can do about this? 

     

    • Post Points: 3
  • 04-14-2008 3:12 PM In reply to

    Re: Bandwidth Gauge v9.2 discovery problem

    Could you please download the interface table and see if it reports information for 40 interfaces?

    Thanks,

    Greg 

    Greg Newman
    SolarWinds Toolset
    • Post Points: 3
  • 04-14-2008 3:19 PM In reply to

    • stegad
    • Not Ranked
    • Joined on 07-07-2007
    • Posts 9
    • Points 20

    Re: Bandwidth Gauge v9.2 discovery problem

     Sure thing, but could you tell me how to do this?  I'm new to SNMP and not that familiar with the MIB browser.  I know where the IF table is, but I'm not sure how to export it in a meaningful way.

    • Post Points: 3
  • 04-14-2008 3:29 PM In reply to

    Re: Bandwidth Gauge v9.2 discovery problem

     stegad - Sure.

    • In MIB Browser, select Edit... Find...
    • Search by OID
    • Enter 1.3.6.1.2.1.2.2.
    • Once found, click the "Show in MIB Tree" button, then the "Done" button.
    • Click the select device button if you have not selected the device you want to query
    • Click the "Get Table" button

    That will download the IF table. The items in the left most column will be your interface indexes.

    --Greg

     

    Greg Newman
    SolarWinds Toolset
    • Post Points: 1
  • 04-14-2008 3:41 PM In reply to

    • stegad
    • Not Ranked
    • Joined on 07-07-2007
    • Posts 9
    • Points 20

    Re: Bandwidth Gauge v9.2 discovery problem

     I exported the IF table to text. Attached.


    • Post Points: 3
  • 04-14-2008 3:46 PM In reply to

    Re: Bandwidth Gauge v9.2 discovery problem

     Stegad - Looks to me like you have a bug to report to your vendor; the device is reporting it has 40 interfaces, but the ifTable only reports information about 24 of them.

    I will try to make the Bandwidth Gauge not so dependent on the total number of interfaces in a future release to work around this.

    HTH,

    Greg 

    Greg Newman
    SolarWinds Toolset
    • Post Points: 3
  • 04-14-2008 3:52 PM In reply to

    • stegad
    • Not Ranked
    • Joined on 07-07-2007
    • Posts 9
    • Points 20

    Re: Bandwidth Gauge v9.2 discovery problem

    Thanks for your help.  So far, this is the only Nortel switch on which I've noticed this problem.  I'll contact Nortel support.  Perhaps this has already been addressed in a firmware patch.

    • Post Points: 1
Page 1 of 1 (11 items)