Problem:

• Product Name: VisiBroker
• Product Version: 6.0 and later
• Product Component: Smart Agent
• Platform/OS Version: All

When setting the "-a <ipaddr>" option, osagent is not effective in using the "ipaddr" value. Instead, it will pick up one of the current Virtual IPs on the host machine instead. This information is visible when using the command "osfind -a".

If the initial Virtual IP bound by the osagent is reassigned to another host machine, the osagent will not be able to serve any request because it is unawared of the reassignment. The command "osfind -a" will list the answer as "no agent in the domain". If the bound Virtual IP is switched back to the original host machine where the osagent is running, then the request will be responded and the command "osfind -a" will get back the same initial answer with the same wrong host name associated with the Virtual IP.

Resolution:

There is an enhancement made in 6.0 osagent to make configuration for a single/multiple interface addresses consistent by using the localaddr file.

In prior versions like 4.x or 5.x, the use of "-a" option allows osagent to bind to a specified local IP address rather than performing a wildcard address binding. From version 6.0 or later, the option will no longer work.

To bound to a single network interface or multiple NIs in version 6.0 or later. Either the environment variable OSAGENT_LOCAL_FILE or the property vbroker.agent.localFile could be used for the purpose.

The change request CR4443 has been raised in order to update the documentation to reflect the new changes.

Please refer to the article [[knowledge_base: VisiBroker localaddr file FAQ]] on how set up on binding Smart Agent to either the single or multiple network interfaces.

Related Articles

[[knowledge_base: Guidelines for Use of the osagent]]

[[knowledge_base: VBC 5.2.1: Osagent problems with multihomed Windows server]]