Use Case: Shared Compute Infrastructure and Shared Security
This use case allows you to logically isolate traffic from two tenants that share an ESXi cluster and have a common set of security policies. In order to isolate traffic from each tenant you need to create a service definition with a template stack that includes two zones. Zone-based traffic separation makes it possible to distinguish traffic between virtual machines that belong to separate tenants, when it traverses through the firewall. The firewall is able to distinguish traffic between tenant virtual machines based on a service profiles and security groups created on the NSX-V Manager, which are available as match criteria in Dynamic Address Groups on the firewall. Therefore, even with overlapping IP addresses, you can segregate traffic from each tenant and secure each tenant’s virtual machines using zone-base policy rules (source and destination zones must be the same) and dynamic address groups.
- This is one-time task and is required if you have not enabled access between the NSX-V Manager and Panorama.
- Log in to the Panorama web interface.
- Selectto add a template stack. This use case has a template stack named NSX-Template.PanoramaTemplates
- Selectand add device group. This use case has a device group named NSX-DG.PanoramaDevice Groups
- Create two zones within the template stack. To isolate traffic for each tenant, you need two zones in this use case.
- Select the correct template stack in theTemplatedrop-down.
- SelectAddand enter a zoneName. For example,Tenant1.
- Sets the interfaceTypetoVirtual Wire.
- Repeat the steps to add another zone, for example,Tenant2.
- Verify that the zones are attached to the correct template stack.
- Select.PanoramaVMware NSX-VService Definitions
- SelectAddand fill in the details.
- ClickCommit, and selectPanoramaas theCommit Typeto save the changes to the running configuration on Panorama.
- Selectand Set Up Dynamic Address Groups on Panorama for each tenant’s virtual machines. For example, this use case has two security groups per tenant; one security group for the web servers and the other security group for the application servers.ObjectsAddress Groups
- Selectto set up security policy rules for sending traffic to the VM-Series firewall.PoliciesSecurityPre Rules
- Selectand clickPanoramaVMware NSX-VSteering RulesAuto-Generate Steering Rules.
- Commityour changes
- The ESXi hosts in the cluster must have the necessary NSX-V components that allow the NSX-V firewall and the VM-Series firewall to work together. The NSX-V Manager will install the components— the Ethernet Adapter Module (.eam) and the SDK —required to deploy the VM-Series firewall.
- Select.Networking and SecurityInstallationService Deployments
- ClickNew Service Deployment(green plus icon), and select the service definition for the Palo Alto Networks next generation firewall you want to deploy,Palo Alto Networks NGFW Test 1in this example, make your selections including the appropriate ESXi cluster to which you want to deploy the firewall and clickFinish.
- Verify that the NSX-V Manager reports theInstallation StatusasSuccessful.
- Verify that the VM-Series firewall is successfully deployed.
- On the vCenter server, selectHosts and Clustersto check that every host in the cluster(s) has one instance of the firewall.
- View the management IP address(es) and the PAN-OS version running on the firewall directly from vCenter server. VMware Tools is bundled with the PAN-OS software image and is automatically enabled when you launch the VM-Series firewall.
- Create Dynamic Address groups for each tenant on Panorama. The dynamic address group(s) that match on the name of the security group(s) you defined on the NSX-V Manager.
- On Panorama, select.ObjectsAddress Groups
- Select the correctDevice Groupfrom the drop-down and clickAdd.
- Add aNamefor the address group and set Type asDynamicandAdd Match Criteria. Verify that you select the correct tags for each tenant, the tag includes the service profile ID, the security group name and the security group ID. For example, for this use case there are four dynamic address groups:
- On Panorama, create security policy rules and use the dynamic address groups as source or destination address objects in security policy rules and push it to the firewalls.
- Selectand clickPoliciesSecurityPrerulesAdd.
- Create rules for each tenant. This use case has the following policy rules:
- Click Commit, and select Commit Type as Device Groups. Select the device group, NSX-DG in this example and click OK.
- Verify that traffic from each tenant is secured.
- Log in to the CLI on the firewall and enter the following command to view the subinterfaces on the firewall:show interface alltotal configured hardware interfaces: 2 name id speed/duplex/state mac address --------------------------------------------------- ethernet1/1 16 auto/auto/up d4:f4:be:c6:af:10 ethernet1/2 17 auto/auto/up d4:f4:be:c6:af:11 aggregation groups: 0 total configured logical interfaces: 6 name id vsys zone forwarding ------------------- ----- ---- ----------------- ethernet1/1 16 1 vwire:ethernet1/2 ethernet1/1.3 4099 1 TENANT-1 vwire:ethernet1/2.3 ethernet1/1.4 4100 1 TENANT-2 vwire:ethernet1/2.4 ethernet1/2 17 1 vwire:ethernet1/1 ethernet1/2.3 4355 1 TENANT-1 vwire:ethernet1/1.3 ethernet1/2.4 4356 1 TENANT-2 vwire:ethernet1/1.4
- On the web interface of the VM-Series firewall, selectand verify that you can view the IP address for the members of each Dynamic Address Group. The following is an example of duplicate IP addresses in dynamic address groups across both tenants.ObjectsAddress Groups
- View theACCand the. Filter on the zone name to ensure that traffic from the virtual machines for each tenant is secured.MonitorLogsTraffic
Recommended For You
Recommended videos not found.