Unsupported content
This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.
If an agent is running on a computer that has multiple network interface cards (perhaps one dedicated to a private network and another dedicated to a public network), you must instruct the agent about which one to use when connecting to consoles and other utilities.
Note
You must create the BindToAddress and PortConnectType variables. They are not created during the installation of the PATROL Agent. For more information about these variables, see List of BMC PATROL Agent variables.
Specify network card IP address
The /AgentSetup/BindToAddress configuration variable specifies which IP Address, and thus which network card, the PATROL Agent uses to communicate with consoles or other utilities in a system with multiple network cards. You can specify an IPv4 or an IPv6 address.
Note
Before defining the BindToAddress pconfig variable, back up your agent Configuration Change File (user-defined_filename.cfg), which contains any customizations that you made to agent configuration variables. Backing up this file ensures that you can restore the agent to its previous state if your BindToAddress definition produces unexpected or undesirable result.
| Format and type of data | Numeric, IP address |
| Default value | None Accepts two types of IP addresses to bind with, one of which must be an IPv4 address and other must be an IPv6 address. You can specify more than one address separated by commas. PATROL Agent considers the valid values from only first two entries and ignores the further entries. If you provide first two values as IPv4 address, then only first valid value is considered, that means PATROL Agent gets one IPv4 address to bind with. Same is applicable for the IPv6 address. Default is none and PATROL Agent listens to both the IPv4 and IPv6 addresses. |
| Minimum and maximum | Not applicable |
| Dependencies | AgentSetup/PortConnectType determines the communication protocol used when establishing a connection through the port specified by this variable |
| Recommendation | If you type in the wrong IP address (make a typographical error), the agent does not start. |
Incorrect IP address
If the IP address is incorrect, the PATROL Agent starts. However, the PATROL Agent cannot listen on any default IP address. It writes error messages, similar to the following ones, to the PATROL Agent Error Log.
Example 1:
Tue Apr 19 20:24:37 2011: ID 102011: E: TCP listener failed err = -14/10049 Tue Apr 19 20:24:37 2011: PatrolAgent-W-EINTERNAL: Sess Init failed: err = -14/10049
Example 2:
Tue Apr 19 19:36:55 2011 PatrolAgent-W-EINTERNAL: Sess Init failed: err = -14/99 (/local-build/Patrol/3.9.00/src/agent/mainloop.c 443) Tue Apr 19 19:36:55 2011: ID 102011: E: TCP listener failed err = -14/99 Tue Apr 19 19:36:55 2011: PatrolAgent-W-EINTERNAL: Sess Init failed: err = -14/99
Set communication protocol
The /AgentSetup/PortConnectType configuration variable specifies the communication protocol for a connection established through the port specified by the BindToAddress configuration variable
| Value | The valid communication protocols for establishing a connection include TCP, UDP, and BOTH. |
| Default value | BOTH |
| Minimum and maximum | Not applicable |
| Dependencies | AgentSetup/BindToAddress sets the IP address for which PortConnectType determines the communication protocol |
| Recommendation | None |
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks