On 16 September 2010 06:54, Mygapula, Sudheer IN BLR SISL <sudheer.mygap...@siemens.com> wrote: > It’s observed that the dot1dTpFdbAddress and dot1dTpFdbPort array sizes are > not same; even though they are columns of the same table our precondition to > build the terminal topology is that the sizes of both these arrays should be > same.
The most likely explanation is that the client tools are querying these two objects at slightly different times - and the underlying data may possibly have changed in the meantime. > Or even though array size coming differently ,is there any logic to process > this data ? > > Can any body help on this? Remember that dot1dTpFdbAddress is the index for the dot1dTpFdbTable So you could simply walk the dot1dTpFdbPort object *only*, and this would give you both Address (index) and Port (value) information in one go. And the two sets would inherently match - since there only one varbind providing both values. Dave ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
