From: Sean M. <se...@br...> - 2009-07-23 21:07:38
|
On Thu, 2009-07-23 at 17:10 +0100, Jethro R Binks wrote: > On Thu, 23 Jul 2009, Sean Millichamp wrote: > > > The Juniper patch enables macsuck to work properly. I have successfully > > tested arpsuck and macsuck against a Juniper EX4200 switch with this > > patch. The problem is that JunOS lists the ifIndex value in the bridge > > MAC tables instead of the bridge index value. > > Interesting, I think I have this same problem in some 3Com 5500 code > versions. I wrote something a bit hackish to work around it, I will > review your code too. Hmm... hold on that Juniper patch. It seems that they have fixed the index numbering issue between JunOS 9.5R1 and 9.5R2 and now that it is fixed the patch with bp_index breaks things. I did notice another issue though, the VLAN membership list shows the VLAN index name, not the VLAN ID or name. JunOS uses an index value for VLANs just like ifIndex, etc. There is a table for mapping index to tag, but it isn't clear to me where/how I should perform this lookup in Netdisco. If I am reading it correctly, it seems to make some inherent assumptions about the index value in the VLAN tables equaling the VLAN tag value. Any suggestions on how I should go about fixing this? The SNMP index->tag lookup table is at jnxVlanMIBObjects in JUNIPER-VLAN-MIB (not in the currently supplied batch of MIBs - they are outdated). Thanks, Sean |