This image shows the east-west traffic flow from the web or application to the database in a regional hub and spoke topology that uses Palo Alto Networks VM-Series Firewall.

It includes three virtual cloud networks (VCNs):

• Hub VCN (192.168.0.0/16): The Hub VCN houses the Palo Alto Networks VM series firewall. The trust subnet uses VNIC2 for internal traffic to or from the Palo Alto Networks VM series firewall. The hub VCN communicates with spoke VCNs through a local peering gateway (LPG).
• Web or application tier spoke VCN (10.0.0.0/24): The VCN contains a single subnet. An application load balancer manages traffic to the web or application VMs. The application tier VCN is connected to the hub VCN over a local peering gateway.
• Database tier spoke VCN (10.0.1.0/24): The VCN contains a single subnet that contains the primary database system. The database tier VCN is connected to the hub VCN over a local peering gateway.

East-west traffic flow from the web or application to the database:

1. Traffic that moves from the web or application tier to the database tier (10.0.1.10) is routed through the web or application subnet route table (destination 0.0.0.0/0).
2. Traffic moves from the web or application subnet route table to the LPG for the web/application tier spoke VCN.
3. Traffic moves from the web or application LPG to the LPG for the hub VCN (destination 0.0.0.0/0).
4. Traffic moves from the hub LPG to the Palo Alto Networks VM series firewall VMs using internal network load balancer. Network load balancer has more than one backends pointing to trust interfaces (VNIC2) of VM Series Firewall.
5. Traffic from the Palo Alto Networks VM Series Firewall is routed through the trust subnet route table (destination 10.0.0.0/24, 10.0.1.0/24).
6. Traffic moves from the trust subnet route table to the LPG for the hub VCN (destination 0.0.0.0/0).
7. Traffic moves from the hub LPG to the LPG for the database tier spoke VCN.
8. Traffic moves from the database LPG to the database system.