Re: [opennms-devel] Linkd and foundry

Linkd uses some places to find bridge data.
The bridge port table and the spanning tree info are found under:

dot1dbridge base and stp mib:

  Bridge Data             .1.3.6.1.2.1.17.1
  Bridge STP Data    .1.3.6.1.2.1.17.2

The bridge forwarding table is found under two places:

QBridgeDot1tTpFdb Table .1.3.6.1.2.1.17.7.1.2.2.1
Dot1dTpTable                       .1.3.6.1.2.1.17.4.3.1

If Foundry did not put mib data under these oids linkd has no way of  
finding links.

  So you should add some FoundryBase, FoundryStp etc etc for each mib  
foundry uses and then
  rewrite SnmpCollection to use these snmp data if no other data is  
found.

  The main trouble is that you need a lab to test that everythink you  
have written is fine.
  But I've no Foundry switch to test on.

  So you should do the work by yourself.

  I'm going to refactor the linkd ASAP especially to use opennms  
model some work is done.

  And I'd like to add a general feature that tells to the  
nmpCollection class:

  snmpwalk this and put the data into this!

  This is useful escpecially for VLAn so that is very simple to add  
support for other vlan vendor mib.

  But could be very useful also for cases like yours.

  It is a map like this, on the left side is the internal java  
bariabe to be populated and the right side is the external; place  
where to get:

<basePortTable type="table">
    <oids>
       <item javaField="bridgeAddress" oid=".1.3.6.1.2.1.17.2.1.1.3" />
       ....................
      .....................
   <oids>
</basePortTable>

It should be not so complicate in doing it.

Regards

Antonio

Il giorno 23/feb/08, alle ore 00:20, Steven Dean ha scritto:

> Hi,
>
> I'm trying to get the linkd service working and I am running into some
> problems with our foundry switches. I've added in the vlan table  
> information
> and that seems to be working. I am now having a problem because the  
> foundry
> boxes don't use the standard mibs for the spanning tree  
> information. I have
> the mibs and the OIDs that are used for this information and I can  
> see it
> using snmpwalk but I'm not sure how to get this into opennms. Any  
> hints on
> where to start if I want to add this information into the linkd  
> process?
>
> --Steven
>
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-devel mailing list
>
> To *unsubscribe* or change your subscription options, see the  
> bottom of this page:
> https://lists.sourceforge.net/lists/listinfo/opennms-devel

Chiacchiera con i tuoi amici in tempo reale! 
 http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-devel mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel