Preparing Your Firewall

Page last updated:

This topic describes how to configure your firewall for Pivotal Platform and how to verify that Pivotal Platform resolves DNS entries behind your firewall.

Configure Your Firewall for Pivotal Platform

Ops Manager and Pivotal Application Service (PAS) require the following open TCP ports:

  • 25555: Routes from Ops Manager to the BOSH Director.
  • 443: Routes to HAProxy or, if configured, your own load balancer.
  • 80: Routes to HAProxy or, if configured, your own load balancer.
  • 8844: Routes from Ops Manager to BOSH CredHub.
  • 8443: Routes from Ops Manager to BOSH Director UAA.
  • 6868: Routes to the BOSH Agent.
  • 2222: Necessary for using Application SSH. For more information, see How Diego Runs an App in Diego Components and Architecture.
  • 25595: Routes from the Traffic Controller to the BOSH Director, to enable sending BOSH health metrics to the Firehose.
  • For vSphere Only: Ops Manager requires that the NSX firewall routes are not blocked. All communication between Ops Manager VMs and vCenter or ESXi hosts route through the NSX firewall and are blocked by default. For more information on which ports to allow, see VMware Ports and Protocols for vSphere.

UDP port 123 must be open if you want to use an external NTP server.

For more information about required ports for additional installed products, see Network Communication Paths in Ops Manager in Network Security.

Example: Configure Firewall with iptables

The following example procedure uses iptables commands to configure a firewall.

Note: GATEWAY_EXTERNAL_IP is a placeholder. Replace this value with your PUBLIC_IP.

  1. Open /etc/sysctl.conf, a file that contains configurations for Linux kernel settings, with the command below:

    $ sudo vi /etc/sysctl.conf

  2. Add the line net.ipv4.ip_forward=1 to /etc/sysctl.conf and save the file.

  3. If you want to remove all existing filtering or Network Address Translation (NAT) rules, run the following commands:

    $ iptables --flush
    $ iptables --flush -t nat

  4. Add environment variables to use when creating the IP rules:

    $ export PIVOTALCF_IP=
    $ export HA_PROXY_IP=

  5. Run the following commands to configure IP rules for the specified chains:

    • FORWARD:
    $ iptables -A FORWARD -i eth1 -j ACCEPT
    $ iptables -A FORWARD -o eth1 -j ACCEPT
    $ iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
            -p tcp --dport 80 -j SNAT --to $GATEWAY_INTERNAL_IP
            -p tcp --dport 443 -j SNAT --to $GATEWAY_INTERNAL_IP
    $ iptables -t nat -A PREROUTING -d $GATEWAY_EXTERNAL_IP -p tcp --dport \
             25555 -j DNAT --to $PIVOTALCF_IP
    $ iptables -t nat -A PREROUTING -d $GATEWAY_EXTERNAL_IP -p tcp --dport \
             443 -j DNAT --to $HA_PROXY_IP
    $ iptables -t nat -A PREROUTING -d $GATEWAY_EXTERNAL_IP -p tcp --dport \
             80 -j DNAT --to $HA_PROXY_IP
    $ iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 8443 -j DNAT \
          --to $PIVOTALCF_IP:443
    $ iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT \
          --to $HA_PROXY_IP:80
    $ iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 8022 -j DNAT \
          --to $PIVOTALCF_IP:22
    $ iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 8080 -j DNAT \
          --to $PIVOTALCF_IP:80
  6. Run the following command to save the iptables:

    $ service iptables save

For more information about administering IP tables with iptables, refer to the iptables documentation.

Verify Ops Manager Resolves DNS Entries Behind a Firewall

When you install Ops Manager in an environment that uses a strong firewall, the firewall might block DNS resolution. For example, if you use to test your DNS configuration, the tests will fail without warning if the firewall prevents PAS from accessing *

To verify that PAS can correctly resolve DNS entries:

  1. SSH into the Ops Manager VM. For more information, see Log Into the Ops Manager VM.

  2. Run any of the following network administration commands with the IP address of the VM:

    • nslookup
    • dig
    • host
    • The appropriate traceroute command for your OS
  3. Review the output of the command and fix any blocked routes. If the output displays an error message, review the firewall logs to determine which blocked route or routes you need to clear.

  4. Repeat steps 1-3 with the BOSH Director VM and the HAProxy VM.