a) if you mean you want to change the IP address of the server to poll from the new IP address then just add the interface to the server and it'll use the windows routing tables to use that interface as appropriate.
b) if you mean that you have two IP addresses configured on your switches then it'll only use whichever IP address you have configured on the switch -- you can change the polling address to make it use the new address, but it will only use one address to poll a device.
what are you trying to do?
'b' answers my question. I intended to try and use an additional IP address for trap listening, along with the existing polling address, but it sounds like that isn't possible.
Well, not in the manner you are speaking directly. You can stand up an additional poller, using that IP address. Enable Solarwinds Trap service on that machine, as well as shift part of your polling load over there. If you are going to do quite a few traps - would limit the polling load on it though. Traps and syslog can degrade your server pretty well, if you are marginal on the SQL server specs
Oh, that's possible -- as long as your routing infrastructure supports it, but are you really getting more and 1Gbps of traps?
Traps are UDP-based, and you only need to get the packet TO the solarwinds server.
The trap receiver listens on all IP addresses and will accept the trap.
It'll then match the incoming IP address with one of the IP addresses on the source switch and traps will be associated with it.
I'm still not sure why you need more than one management address on a switch -- 1Gbps is really a lot of management traffic. Here our switches are configured into a management VLAN and we use that to segregate and QoS their traffic.
Be careful on how you configure that "second ip" on the nodes. Ie, in Cisco, if you configure 2 ip for traps, it'll send traps to both IP. That will double your traffic coming from that node.