Configuring an accessible broker address

Prev Next

Sensors cannot communicate with brokers using the default submission interface if your IVX cluster is in an internal network behind a NAT gateway and your sensors are in an external network. In this scenario, you must configure an accessible (public) IP address for each Virtual Execution appliance that functions as a broker. This is the virtual NAT

IP address and port that a network administrator must map to the Virtual Execution internal IP address and port 22.

The enrollment service on the Central Management appliance that manages the IVX cluster uses the accessible IP address (instead of the submission interface IP address) for sensor enrollment. The show mvx node status command output appends (public) to the broker address when an accessible IP address is configured.

Prerequisites

  • Admin access

Configuring an accessible broker address

Use the commands in this section to configure an accessible IP address for a broker.

To configure an accessible IP address for a broker:
  1. Log in to the Virtual Execution (broker) CLI.

  2. Enable the CLI configuration mode:

    vx-hostname > enable
    vx-hostname # configure terminal
  3. Configure the accessible IP address:

    vx-hostname (config) # mvx node broker public-address <public IP addr>
  4. Verify your change:

    vx-hostname (config) # show mvx node status
  5. Save your change:

    vx-hostname (config) # write memory
Example

The following example configures 172.2.3.4 as the accessible IP address for the vx-1 broker whose internal IP address is 10.1.2.3. The accessible IP address is displayed in the Broker Role section, and the internal IP address is displayed in the Node information section.

vx-1 (config) # mvx node broker public-address 172.2.3.4
vx-1 (config) # show mvx node status

MVX Node: vx-2

Cluster IP Address      : 172.2.3.4 (Public)
    IP Address          : 10.13.65.64
    Role                : broker
    Status              : ready
    Version             : 8.3.0

    queue:
        Status              : ready
        utilization         : 0
storage:
    Status             : ready

    compute:
        Status              : ready
        total               : 30
        running             : 0
        utilization         : 0

MVX Node: vx-1

    Cluster IP Address  : 10.13.65.63
    IP Address          : 10.13.65.63
    Role                : compute
    Status              : ready
    Version             : 8.3.0

compute:
        Status              : ready
        total               : 30
        running             : 0
        utilization         : 0
Removing an accessible broker address

Use the commands in this section to remove the accessible IP address from a broker. This restores the default submission interface as the IP address that sensors use to communicate with the broker.

To remove an accessible IP address from a broker:
  1. Log in to the Virtual Execution (broker) CLI.

  2. Enable the CLI configuration mode:

    vx-hostname > enable
    vx-hostname # configure terminal
  3. Remove the accessible IP address:

    vx-hostname (config) # no mvx node broker public-address
  4. Verify your change:

    vx-hostname (config) # show mvx node status
  5. Save your change:

    vx-hostname (config) # write memory
Example

The following example removes the accessible IP address from the vx-1 broker.

vx-1 (config) # no mvx node broker public-address
vx-1 (config) # show mvx node status

MVX Node: vx-2

    Cluster IP Address  : 10.13.65.64
    IP Address          : 10.13.65.64
    Role                : broker
    Status              : ready
    Version             : 8.3.0

    queue:
        Status          : ready
        utilization     : 0

    storage:
        Status         : ready
    
    compute:
        Status          : ready
        total           : 30
        running         : 0
    utilization         : 0

MVX Node: vx-1

Cluster IP Address : 10.13.65.63
    IP Address      : 10.13.65.63
    Role            : compute
    Status          : ready
    Version         : 8.3.0

    compute:
        Status              : ready
        total               : 30
        running             : 0
        utilization         : 0