Forum Discussion
NimbostratusDouble Persistence on RADIUS
I have 2 VS for Radius Services ( 1812-Authentication / 1813- Accounting)
- 100.1.1.1:1812
- 100.1.1.1:1813
With pool Servers (1812/1813) 1.10.10.10.1 2.10.10.10.2 3.10.10.10.3
Both VS are using same servers. Requirement is any user transaction that goes on server1 on 1812, the next transaction of 1813 with the same user, should go to server1 as well.
Next user can use server2, but persistency on both 1812/1813 ports on server2 as well. This is like user persistence on 2 VS, going on the same server all the time. Tried to search for irule on this with similar requirement, but no luck.
2 Replies
tatmotivCirrostratus
You don't need an irule for that. Just enable persist across virtuals in the persistence profile.
dyobbs_25515tatmotiv, this works if you have source / destination address defined. However, my first persistence is based the calling station ID of a radius packet. This was done on using radius profile with "calling station ID" attribute. I'm looking for a way to match across virtuals using affinity on the calling station ID of a radius profile. Is that possivble?
