NATS Network Communications

This topic describes NATS internal network communication paths with other Pivotal Application Service (PAS) components.

Publish Communications

The following table lists network communications that are published to NATS.

Source VM Destination VM Port Transport Layer Protocol App Layer Protocol Security and Authentication
cloud_controller
(Route Registrar)
nats 4222 TCP NATS Basic authentication
loggregator_trafficcontroller
(Route Registrar)
nats 4222 TCP NATS Basic authentication
mysql_proxy
(Route Registrar)*
nats 4222 TCP NATS Basic authentication
nfs_server
(Route Registrar)
nats 4222 TCP NATS Basic authentication
uaa
(Route Registrar)
nats 4222 TCP NATS Basic authentication
diego_cell
(local Route Emitter)
nats 4222 TCP NATS Basic authentication

*Applies only to deployments where internal MySQL is selected as the database.

Applies only to deployments where the internal NFS server is selected for file storage.

Subscribe Communications

The following table lists network communications that are subscribed to NATS.

Source VM Destination VM Port Transport Layer Protocol App Layer Protocol Security and Authentication
router nats 4222 TCP NATS Basic authentication

BOSH DNS Communications

By default, PAS components and app containers look up services using the BOSH DNS service discovery mechanism. To support this lookup, BOSH Director colocates a BOSH DNS server on every deployed VM. For more information, see BOSH DNS Network Communications.

Consul Communications

If you disabled BOSH DNS for PAS components and other VMs by selecting Disable BOSH DNS server for troubleshooting purposes in the BOSH Director tile Director Config pane, PAS components call out to Consul for service discovery. For more information, see Consul Network Communications.

Create a pull request or raise an issue on the source for this page in GitHub