Hi all,
How (or will) it handle listening for SNMP traps when there are multiple tests running at the same time? Will iTest be able to distinguish between traps intended for one test, from those intended for another?
Thanks,
chris
Hi all,
How (or will) it handle listening for SNMP traps when there are multiple tests running at the same time? Will iTest be able to distinguish between traps intended for one test, from those intended for another?
Thanks,
chris
Traps are identified by the unique Trap OID. For example, .1.3.6.1.6.3.1.1.5.3 for linkDown.
See below for a typical example for a received trap.
Properties Value
----------------------------------------------------------------------------------------------------
Source 10.155.0.223
Version Version1
Time Wed Apr 14 17:12:53 PDT 2010
Community public
TrapOID .1.3.6.1.6.3.1.1.5.3
TrapName .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.linkDown
GenericType linkDown
SpecificType 777
OID Type Value
----------------------------------------------------------------------------------------------------.iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.linkDown.0 OctetString linkDown
If there are multiple tests running at the same time on the same host that generates multiple traps I don't think iTest will be able to distinguish which tests generated which trap if the trapOID is identical.
There are tools that you can generate Traps with user specified "Specific Type" values but in general I would recommend to use a unique Trap OID for each test.
As long as traps are different you are OK. If the traps are same, then you are in trouble. All traps are collected by a single trap listener module per iTest process. Each session requests traps from this module. So if two tests are running at the same time and they cause generation of exactly same traps from two devices on the same UDP port, sessions will get combined list of traps.
Work arounds - run trap tests one at a time.
No one has followed this question yet.