Forum Discussion
RoutingLoop_179
Cirrus
Feb 13, 2013Linking Universal persistence across different dataflows and virtual servers
Hi I've been trying to look at getting this working but sort of going round in circles at the logic.
Basically i essentially have three flows of traffic in this order.
1st Radius - containi...
RoutingLoop_179
Cirrus
Feb 15, 2013Brilliant thanks, i've made very small modification and rather than using scan the to grab the IP out i just use node in the lookup and pull the node straight then. e.g
when CLIENT_ACCEPTED { USER MAC - radius attribute 31 Calling-Station-Id client-IP - radius attribute 8 Framed-IP log local0. "Client: [IP::client_addr] Framed-Ip-Address \[RADIUS::avp 8\]: [RADIUS::avp 8] MAC \[RADIUS::avp 31\]: [RADIUS::avp 31]" persist uie [RADIUS::avp 31] if { [RADIUS::avp 8] ne "" } { set node [persist lookup uie "[RADIUS::avp 31] any virtual" node] log local0. "node: $node" table add [RADIUS::avp 8] $node log local0. "created tabledata for framed-ip-address:[RADIUS::avp 8] associated with: $node" } }
so the rule seems to be working but i have seen some unexpected behavior regarding the persistence on just the radius traffic flow which should be persistent on MAC attribute. Even if there is a UIE persistence record for the mac attribute, I don't have radius server on the other the server side so on event LB_SELECTED it seems bigip (or client) is retrying and sending the request (i'm a bit unsure why) but it seems to be bigIP doing the retry as i only see retries on LB_SELECTED, but looking at my logs on each retry it seems to round robin across my two live nodes.
Feb 15 11:12:45 tmm info tmm[6932]: Rule /Common/radius_persist2 : [persist lookup uie [RADIUS::avp 31] any virtual node]: 192.168.71.12
Feb 15 11:12:45 tmm info tmm[6932]: Rule /Common/radius_persist2 : ClientIP: 10.12.13.4 LB to: 192.168.71.12
Feb 15 11:12:50 tmm info tmm[6932]: Rule /Common/radius_persist2 : [persist lookup uie [RADIUS::avp 31] any virtual node]: 192.168.71.12
Feb 15 11:12:50 tmm info tmm[6932]: Rule /Common/radius_persist2 : ClientIP: 10.12.13.4 LB to: 192.168.71.11
Feb 15 11:12:55 tmm info tmm[6932]: Rule /Common/radius_persist2 : [persist lookup uie [RADIUS::avp 31] any virtual node]: 192.168.71.12
Feb 15 11:12:55 tmm info tmm[6932]: Rule /Common/radius_persist2 : ClientIP: 10.12.13.4 LB to: 192.168.71.12
any ideas?
I'm using VE with 11.2.1 - no hotfixes.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects