NSX – Configure an application profile and rules

You create an application profile to define the behavior of a particular type of network traffic. After configuring a profile, you associate the profile with a virtual server. The virtual server then processes traffic according to the values specified in the profile. Using profiles enhances your control over managing network traffic, and makes traffic-management tasks easier and more efficient.

Procedure

1 Log in to the vSphere Web Client.

2 Click Networking & Security and then click NSX Edges.

3 Double-click an NSX Edge.

4 Click Manage and then click the Load Balancer tab.

5 In the left navigation panel, click Application Profiles.

6 Click the Add icon.

7 Type a name for the profile and select the traffic type for which you are creating the profile.

8 Type the URL to which you want to re-direct HTTP traffic. For example, you can direct traffic from http://myweb.com to https://myweb.com.

9 Specify persistence for the profile. Persistence tracks and stores session data, such as the specific pool member that serviced a client request. This ensures that client requests are directed to the same pool member throughout the life of a session or during subsequent sessions.

Cookie persistence inserts a cookie to uniquely identify the session the first time a client accessed the site and then refers to that cookie in subsequent requests to persist the connection to the appropriate server. Type the cookie name and select the mode by which the cookie should be inserted. The following cookie insertion modes are supported:

Insert – NSX Edge sends a cookie. If the server sends one or more cookie, the client will receive one extra cookie (the server cookie(s) + the Edge cookie). If the server does not send any cookie, the client will receive the Edge cookie.

Prefix – This option is selected if your client does not support more than one cookie.

App Sesssion – In this option, the server does not send a cookie; instead, it sends the user session information as a URL. For example,  http://mysite.com/admin/UpdateUserServlet;jsessionid=OI24D, where jsessionid is the user session information and is used for the persistence. It is not possible to see the App Session persistence table for troubleshooting.

SOURCEIP persistence tracks sessions based on the source IP address. When a client requests a connection to a virtual server that supports source address affinity persistence, the load balancer checks to see if that client previously connected, and if so, returns the client to the same pool member.

Add an Application Rule

You can write an application rule to directly manipulate and manage IP application traffic.

1 Log in to the vSphere Web Client.

2 Click Networking & Security and then click NSX Edges.

3 Double-click an NSX Edge.

4 Click Manage and then click the Load Balancer tab.

5 In the left navigation panel, click Application Rules and click the Add icon.

6 Type the name and script for the rule.

7 Click OK.

Leave a Reply

Your email address will not be published. Required fields are marked *