Double checking myself here -
A Frontside Handler has the Secondary IP of 10.0.1.3. This Secondary IP resides on the actual NIC of 10.0.1.2.
When the service leaves the appliance, it leaves the appliance on the Secondary IP it came in on, being 10.0.1.3, not the physical NIC of 10.0.1.2 ?
This is with Destination Based routing turned off, and Interface Isolation set to only use the IP the data was received on.
This topic has been locked.
1 reply Latest Post - 2012-12-11T17:39:41Z by SystemAdmin
Pinned topic Datapower Secondary IP - networking flow
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-11T17:39:41Z at 2012-12-11T17:39:41Z by SystemAdmin
SystemAdmin 110000D4XK6772 PostsACCEPTED ANSWER
Re: Datapower Secondary IP - networking flow2012-12-11T17:39:41Z in response to SystemAdminAfter some discussion, using Source-Based routing, and my Interface Isolation settings configured appropriately, the guarantee of the packet returning back to the client via response, on the same IP it came in on via the request, is what I needed to know. The packet 'leaving' the appliance to it's Destination, not to the client, but the backend, can be controlled with static routes if needed. Considering all of the orchestration going on anyway inside the appliance, such as changing from one FSH/IP to another FSH/IP, etc., my question of 'What will the Destination see IP-wise coming from the appliance, is dependent on the services and where the packet 'is' by the time it is ready for the Destination/Backend. So, almost a moot question from my end once I started thinking about it.