Configure communication broker ports

Overview

Management servers and nodes that have HTTPS agents both include communication brokers that listen for inbound connections on port 383, as the figure below shows. The communication broker on a management server (1) handles all inbound connections from nodes that have HTTPS agents, and also from other management servers. The communication broker on a node that has the HTTPS (2) agent handles all inbound connections from management servers.

You can configure any communication broker to listen on a port other than 383. If you do this, you must also configure the other management servers and nodes in the environment, so that their outbound connections are destined for the correct port. For example, if you configure a node's communication broker to listen on port 5000, you must also configure the management server so that it connects to port 5000 when it communicates with this node.

PORTS parameter syntax

You configure communication broker ports by setting the PORTS parameter in the bbc.cb.ports name space on all management servers and nodes that communicate with each other. You can configure this parameter in the following ways:

• Configure the values in the HTTPS agent installation defaults. This is recommended if you need to configure communication broker ports for large numbers of nodes. You must plan and configure the installation defaults before you create or migrate your nodes.
• Use ovconfchg or ovconfpar at a command prompt.

The values must contain one or more host names or IP addresses and have the following format:

<host>:<port>[,<host>:<port>] ...

The <host> can be either a domain name or IP address. For example, to configure the communication broker port to 5000 on a management server with the host name manager1.emea.example.com, use the following command on the management server itself, and also any other management servers and nodes that open connections to it:

ovconfchg -ns bbc.cb.ports -set PORTS manager1.emea.example.com:5000

If you need to configure communication broker ports on multiple systems, you can use wildcards and ranges, as follows:

• You use a wildcard at the start of a domain name by adding an asterisk (*). For example:
  • *.emea.example.com:5000
  • *.test.com:5001
  • *:5002
• You can use wildcards at the end of an IP address by adding up to three asterisks (*). For example:
  • 192.168.1.*:5003
  • 192.168.*.*:5004
  • 10.*.*.*:5005
• You can replace one octet in an IP address with a range. The range must be before any wildcards. For example:
  • 192.168.1.0-127:5006
  • 172.16-31.*.*:5007

If you specify multiple values for the PORTS parameter, separate each with a comma (,). For example:

ovconfchg -ns bbc.cb.ports -set PORTS *.emea.example.com:5000,10.*.*.*:5005

When you specify multiple values using wildcards and ranges that overlap, the management server or node selects the port to use in the following order:

• Fully qualified domain names.
• Domain names with wildcards.
• Complete IP addresses.
• IP addresses with ranges.
• IP addresses with wildcards.

For example, if you configure communication broker ports on all management servers and nodes with the following command:

ovconfchg -ns bbc.cb.ports -set PORTS *.emea.example.com:6000,10.*.*.*:6001,manager1.emea.example.com:6002,10.0-127.*.*:6003

the following ports are used:

• Host name: node1.asia.example.com
IP address: 10.127.1.1
Communication broker port: 6003.
• Host name: manager1.emea.example.com
IP address: 10.1.1.1
Communication broker port: 6002.
• Host name: node1.test.com
IP address: 192.168.1.1
Communication broker port: 383.

To find out which port is currently configured, type the following command:

bbcutil -getcbport <host>

Tip:
To organize settings for many communication broker ports, you can add parameters of any name in the bbc.cb.ports name space. The value of any parameter in the name space is evaluated. The PORTS parameter is optional.

To configure communication broker ports using ovconfchg

1. Open a command prompt on the management server or node.
2. On nodes that run a UNIX or Linux operating system, ensure that the PATH variable contains the path to the agent commands.
   • On HP-UX, Solaris, or Linux, type export PATH=/opt/OV/bin:$PATH and then press Enter.
   • On AIX, type export PATH=/usr/lpp/OV/bin:$PATH and then press Enter.
   • On Tru64, type export PATH=/usr/opt/OV/bin:$PATH and then press Enter.

3. Specify the communication broker ports by typing the following command:

   ovconfchg -ns bbc.cb.ports -set PORTS <host>:<port>[,<host>:<port>] ...

NOTE:
When you use the command ovconfchg on a management server that runs in a cluster, add the parameter -ovrg server

Related Topics:

• Configure HTTPS agent installation defaults
• ovconfchg
• ovconfpar