[NetScaler Trace Study] - How USIP Looks in a Network Trace

[NetScaler Trace Study] - How USIP Looks in a Network Trace

book

Article ID: CTX233036

calendar_today

Updated On:

Description

This trace study looks at how USIP looks in a trace when it is configured correctly and incorrectly.

This example trace was carried out in a practice lab environment with the following IP addresses:
  • Client IP 10.90.33.156
  • VIP 10.90.46.28
  • SNIP 10.90.46.26
  • Backend server 10.90.46.13

Instructions

When USIP works, you can see the Client IP in the trace communicating directly with the backend. However the source MAC is the NetScaler:

Source MAC is NetScaler

On the backend server we can see the traffic coming from the client:

On the backend server we can see the traffic coming from the client

If the backend server is not configured with the SNIP as the Default Gateway, USIP will fail. This is how it looks in a trace:

If the backend server is not configured with the SNIP as the Default Gateway, USIP will fail

A trace on the backend shows it is resetting the connection as it does not know how to get the packets back to the client:

A trace on the backend shows it is resetting the connection as it does not know how to get the packets back to the client

Issue/Introduction

This trace study looks at how USIP looks in a trace when it is configured correctly and incorrectly.

Additional Information

CTX121974 - FAQ: USIP Address Mode of NetScaler