After you register a service, you must deploy an instance of the service on an NSX transport node for the service to start processing network traffic.
Deploy partner service VM at tier-0 or tier-1 logical router that acts as a gateway between the physical world and the logical network on VMware vCenter. After you deploy the SVM as a standalone service instance or an active-standby service instance, you can create redirection rules to redirect traffic to the SVM for network introspection.
Prerequisites
-
All hosts are managed by a VMware vCenter.
-
Partner services are registered with NSX and are ready for deployment.
-
NSX administrators can access partner services.
-
High Availability mode for logical router must be in active-standby mode.
- Turn on the Distributed Resource Scheduler utility.
-
Ensure only one overlay transport zone is connected to hosts that are running the partner service.
-
Ensure only one service segment is used to connect guest VMs for network introspection.
- Starting with NSX 3.1, on clusters that span physical servers placed in different racks, you can override the transport node profile applied on a per-host basis.
- Starting with NSX 3.0, you must prepare clusters (cluster-based or host-based deployment methods) by applying a transport node profile.
- With NSX 2.5.x or earlier, before you deploy service VMs on each host using host-based service deployment method, configure each host of the cluster with NSX by applying a transport node profile.
- When upgrading the third-party service, the existing service will continue to be functional even if transport node profile is not applied to the cluster.
Procedure
Results
Alternatively, go to the VMware vCenter and verify the deployment status.
What to do next
Add redirection rules for north-south traffic. See Add Redirection Rules for North-South Traffic.