WAAS mobile 3.5 source IP transparency option

[mario-leitao]

Have some questions about the new feature (Source IP transparency option) bellow released on the 3.5 version:

–Source IP transparency option. TCP connections from the WAAS Mobile server to applications and content are generated with the user's source IP address and port number.

1 - How is this performed?

2 - Does the waas mobile needs to be inline?

3 - Does it send the packets with the source ip on the header or use another option on the header?

4 - How is the mobile server located on the topology?

5 - How can we add redundancy if the waas mobile is inline?

6 - Can the waas mobile server use the fail-to-wire feature?

I apreciate if you can answer part or all the questions.

[Kenneth Lanzillo · Accepted solution]

1 - How is this performed? 

A driver on the WAAS Mobile Server initiates TCP connections to the application and content server using the user’s source IP.

2 - Does the waas mobile needs to be inline?

We do not recommend deploying WAAS Mobile inline. When the source IP transparency option is selected, the WAAS Mobile server should be deployed in conjunction with a Layer 4 switch such as a Cisco ACE with mac-sticky capability that redirects traffic back to the WAAS Mobile server.  The Layer 4 switch could be inline.

3 - Does it send the packets with the source ip on the header or use another option on the header? 

Yes, the user’s source IP is in the header.

4 - How is the mobile server located on the topology? See response above.

5 - How can we add redundancy if the waas mobile is inline? Multiple WAAS Mobile servers may be deployed using ACE server load balancing to provide redundancy.

6 - Can the waas mobile server use the fail-to-wire feature?  WAAS Mobile servers are not recommended to be deployed inline.