Do you want to poll all those machine on all 3 IP Adresses? You will get all IP Adresses listed on the Node Details Page. Or is this a requirement to "probe" all IP Adresses, either way it is the same Node just with different Interfaces as the polling interface, right?
Yes, you are correct. This will be same node with different polling IP address. I forgot to mentioned that nodes are already added via vlan ip and requirement is that branch router will be polled via all three ip address and via SNMP
i know It sounds ridiculous (having one device with 3 different ip and via SNMP, that cost 2 valuable node space)
but it is a requirement.
If it is a requirement we need to find a way... I assume discovery checks the additional IP addresses on the nodes and marks them as "duplicates" because this device is already managed (over the "main polling IP"). So I guess we need to get rid of the additional IP addresses on the node, then we might to be able to add the nodes again with a different IP.
One thing that makes me scratch my head is -> once the rediscovery runs, the additional IP Addresses will be added again, so we need to increase the rediscovery interval so that we will be able to add the nodes.
Do you have a list with the IP addresses and additional Information so that you could possibly add the nodes by an API-Script? This might make life a little easier.
by API-Scricpt? how?
i have the list.
2 of 2 people found this helpful
thanks this is quite helpful collection of scripts.
I found another article on orion website that helped me to resolve this.
I changed the default and current weight values to 0 of following settingid in setting table
discovery worked although there was an exception warning but nodes were successfully added. After this I faced "redirection to error page" after every page refresh event. To avoid this I revert back the default values and every thing back to normal again.