Hi Ellis, When using several UDP (or TCP) transport mappings you should make sure, that you use only the Snmp methods that take the transport mapping as parameter. Then you can choose the mapping you want to use.
The default NotificationOriginator however, will not distinguish between those mappings. You will have to write your own NotificationOriginator to choose the transport mapping according to some self defined rules. Best regards, Frank Ellis Corey wrote: > Hi, > > > > I have setup multiple transport mappings for the purpose of sending out > traps over multiple interfaces. Everything is working fine, accept that > the source ip of my trap that is going out of one interface is using the > ip address of another interface. > > > > Example of what is occurring. My machine has two interfaces (admin and > hsbn) > > > > Admin = 10.1.1.1 > > HSBN = 10.2.2.2 > > > > When I send out a trap it goes out on both interfaces, but the trap > going out of the admin network has source ip of 10.2.2.2 instead of > 10.1.1.1 > > > > I am building my UdpAddress(adminIP, port), I was expecting that the IP > I define in the UdpAddress will be the one that is used as the source ip > when the trap is sent, but it seems like this is not the case. > > > > Any ideas, how I can control the source IP when sending out the trap > over multiple interfaces. > > > > Corey Ellis > Engineering Development Manager > > OA&M and Security, Billing > Comverse > Office: 856-608-2580 > > Mobile: 609-319-6513 > > > > _______________________________________________ > SNMP4J mailing list > [email protected] > http://lists.agentpp.org/mailman/listinfo/snmp4j -- AGENT++ http://www.agentpp.com http://www.snmp4j.com http://www.mibexplorer.com http://www.mibdesigner.com _______________________________________________ SNMP4J mailing list [email protected] http://lists.agentpp.org/mailman/listinfo/snmp4j
