Forum Discussion
13 Replies
Sort By
- hooleylistCirrostratusI'm thinking you could define the nodes on port any (0) and then use the standard cookie insert persistence profile, but I haven't tested this.
- Susan_Cahill_82NimbostratusThe nodes aren't where the port is defined, our configuration defines that at the Virtual Server level.
- hooleylistCirrostratusIf the VIPs are configured on the same IP address (and domain), you could define the nodes on port 0 and use the same pool for both VIPs. Then configure cookie insert persistence on both VIPs.
- Susan_Cahill_82NimbostratusUnfortunately, can't define the node to port 80 since we're using the Big-IP for SSL termination.
- hooleylistCirrostratusIf you define the port on a single pool to 0 and disable address translation, the connection to the pool will be made using the same destination port as the VIP. So if you have two pools currently: one on port 443 and the other on port 80, you could replace them with a single pool on port 0. The persistence record added to the cookie will then be valid for both VIPs.
- Susan_Cahill_82NimbostratusHi,
- hooleylistCirrostratusThanks for the clarification. I think this is your current configuration:
- Susan_Cahill_82NimbostratusThe request initally hits the VIP:80 and then is redirected with the IRule, but a cookie gets passed back from the first request on port 80. The cookie does not get persisted and the user gets a message:
- hooleylistCirrostratusIt sounds like the web app requires statefulness between HTTP and HTTPS requests. I'm also guessing that the issue isn't with the BIG-IP's persistence cookie, but the web app's.
- Susan_Cahill_82NimbostratusHere's the answers to your questions: