The following tables show NATS internal network communication paths with other VMware Tanzu Application Service for VMs (TAS for VMs) components.
For more information about how Cloud Foundry integrates NATS, see TAS for VMs Routing Architecture.
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-4225 | TCP | NATS | Basic authentication |
| loggregator_trafficcontroller (Route Registrar) | nats | 4222-4225 | TCP | NATS | Basic authentication |
| mysql_proxy (Route Registrar)* | nats | 4222-4225 | TCP | NATS | Basic authentication |
| nfs_server (Route Registrar)† | nats | 4222-4225 | TCP | NATS | Basic authentication |
| uaa (Route Registrar) | nats | 4222-4225 | TCP | NATS | Basic authentication |
| diego_cell (local Route Emitter) | nats | 4222-4225 | 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-4225 | TCP | NATS | Basic authentication |
BOSH DNS communications
By default, TAS for VMs components and app containers look up services using the BOSH DNS service discovery mechanism. To support this lookup, BOSH Director co-locates a BOSH DNS server on every deployed VM. For more information, see BOSH DNS network communications.
