Forum Discussion
NimbostratusPersistence entries aren't mirrored to the standby unit when using iRules
Hi
I have an iRule configured on a VIP. This iRule select Pool1 or Pool2 based on the HTTP_Host. I removed any defaultpool configuration on my VIP to make sure only my iRule select them. I also have a default persistence profile attach to my VIP, so I do not add a persistence command into my iRules
On my primary unit I'm able to see all the persistence created but on my standby unit I should see all the same record but with 0sec of age but I didn't see anything. The list is empty on my standby units.
I double-checked on my persistence profile and I have the "Mirror persistence" check box enable.
Is there anyting related with my iRules or it's a basic mirror persistence issue ?
Thanks
24 Replies
shaggydo you use other persistence profiles with mirroring enabled? are those mirrored to the standby unit? make sure that you have properly configured "Primary Local Mirror Address" for each device in the Device Management | Devices configuration.
netadmindetail_Yes my "Primary Local Morror Address" is configured. I also look at my mirror selfIP and it's setup to "Allow All" on both side.
Unfortunately I do not have another active persistence profile on another VIP that I can test
Check if you have connectivity on TCP/1028 between your mirroring self IPs.
gsharriAltostratus
If you have v11.4+ this will be a range of ports starting with TCP 1029. See: https://support.f5.com/kb/en-us/solutions/public/14000/800/sol14894.html- netadmindetail_I'm able to telnet on both port
nitass_89166Noctilucent
I also have a default persistence profile attach to my VIP, so I do not add a persistence command into my iRules
what persistence profile are you using e.g. source, universal, etc?
- netadmindetail_I'm using source-address
- nitass
Employee
I also have a default persistence profile attach to my VIP, so I do not add a persistence command into my iRules
what persistence profile are you using e.g. source, universal, etc?
- netadmindetail_I'm using source-address
- nitass_89166
I'm using source-address
it seems okay here.
active root@(ve11c)(cfg-sync In Sync)(Active)(/Common)(tmos) show ltm persistence persist-records all-properties Sys::Persistent Connections source-address - 172.28.24.10:80 - 200.200.200.111:80 ----------------------------------------------------- TMM 1 Mode source-address Value 192.168.206.48 Age (sec.) 5 Virtual Name /Common/bar Virtual Addr 172.28.24.10:80 Node Addr 200.200.200.111:80 Pool Name /Common/foo2 Client Addr 192.168.206.48 Local entry source-address - 172.28.24.10:80 - 200.200.200.111:80 ----------------------------------------------------- TMM 0 Mode source-address Value 192.168.206.48 Age (sec.) 5 Virtual Name /Common/bar Virtual Addr 172.28.24.10:80 Node Addr 200.200.200.111:80 Pool Name /Common/foo2 Client Addr 192.168.206.48 Owner entry Total records returned: 2 standby root@(ve11b)(cfg-sync In Sync)(Standby)(/Common)(tmos) show ltm persistence persist-records all-properties Sys::Persistent Connections source-address - 172.28.24.10:80 - 200.200.200.111:80 ----------------------------------------------------- TMM 0 Mode source-address Value 192.168.206.48 Age (sec.) 0 Virtual Name /Common/bar Virtual Addr 172.28.24.10:80 Node Addr 200.200.200.111:80 Pool Name /Common/foo2 Client Addr 192.168.206.48 Owner entry Total records returned: 1is virtual address's traffic group set correctly (i.e. traffic-group-1)?
root@(ve11c)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm virtual-address 172.28.24.10 ltm virtual-address 172.28.24.10 { address 172.28.24.10 mask 255.255.255.255 traffic-group traffic-group-1 }- netadmindetail_My Primary Local Mirror Address is link to a mirroring vlan. The self IP configure into that vlan is a "traffic-group-local-only" I have the same kind of self ip on my production environment and the persistence works fine.
- nitass_89166what about virtual address (i.e. virtual server address)? is it set to traffic-group-1?
- netadmindetail_Yes they're set to traffic-group-1
- nitass
I'm using source-address
it seems okay here.
active root@(ve11c)(cfg-sync In Sync)(Active)(/Common)(tmos) show ltm persistence persist-records all-properties Sys::Persistent Connections source-address - 172.28.24.10:80 - 200.200.200.111:80 ----------------------------------------------------- TMM 1 Mode source-address Value 192.168.206.48 Age (sec.) 5 Virtual Name /Common/bar Virtual Addr 172.28.24.10:80 Node Addr 200.200.200.111:80 Pool Name /Common/foo2 Client Addr 192.168.206.48 Local entry source-address - 172.28.24.10:80 - 200.200.200.111:80 ----------------------------------------------------- TMM 0 Mode source-address Value 192.168.206.48 Age (sec.) 5 Virtual Name /Common/bar Virtual Addr 172.28.24.10:80 Node Addr 200.200.200.111:80 Pool Name /Common/foo2 Client Addr 192.168.206.48 Owner entry Total records returned: 2 standby root@(ve11b)(cfg-sync In Sync)(Standby)(/Common)(tmos) show ltm persistence persist-records all-properties Sys::Persistent Connections source-address - 172.28.24.10:80 - 200.200.200.111:80 ----------------------------------------------------- TMM 0 Mode source-address Value 192.168.206.48 Age (sec.) 0 Virtual Name /Common/bar Virtual Addr 172.28.24.10:80 Node Addr 200.200.200.111:80 Pool Name /Common/foo2 Client Addr 192.168.206.48 Owner entry Total records returned: 1is virtual address's traffic group set correctly (i.e. traffic-group-1)?
root@(ve11c)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm virtual-address 172.28.24.10 ltm virtual-address 172.28.24.10 { address 172.28.24.10 mask 255.255.255.255 traffic-group traffic-group-1 }- netadmindetail_My Primary Local Mirror Address is link to a mirroring vlan. The self IP configure into that vlan is a "traffic-group-local-only" I have the same kind of self ip on my production environment and the persistence works fine.
- nitasswhat about virtual address (i.e. virtual server address)? is it set to traffic-group-1?
- netadmindetail_Yes they're set to traffic-group-1
- netadmindetail_
I have a cluster of 3 LTM but one of them was a test and the licence is expired. I don't use it anymore but haven't remove it from the cluster. I have a sync failed for that one but my 2 other one are flaged as green. Could it be a reason (having 1 device out of 3 failed in the cluster sync).
- nitass_89166
I have a cluster of 3 LTM but one of them was a test and the licence is expired. I don't use it anymore but haven't remove it from the cluster. I have a sync failed for that one but my 2 other one are flaged as green.
the expired unit is not a next active device, is it?
root@(ve11c)(cfg-sync In Sync)(Active)(/Common)(tmos) show cm traffic-group ----------------------------------------------------------- CM::Traffic-Group Name Device Status Next Active ----------------------------------------------------------- traffic-group-1 ve11a.acme.local standby false traffic-group-1 ve11b.acme.local standby true traffic-group-1 ve11c.acme.local active false traffic-group-local-only - - -- netadmindetail_No It's not the next active device
- nitass
I have a cluster of 3 LTM but one of them was a test and the licence is expired. I don't use it anymore but haven't remove it from the cluster. I have a sync failed for that one but my 2 other one are flaged as green.
the expired unit is not a next active device, is it?
root@(ve11c)(cfg-sync In Sync)(Active)(/Common)(tmos) show cm traffic-group ----------------------------------------------------------- CM::Traffic-Group Name Device Status Next Active ----------------------------------------------------------- traffic-group-1 ve11a.acme.local standby false traffic-group-1 ve11b.acme.local standby true traffic-group-1 ve11c.acme.local active false traffic-group-local-only - - -- netadmindetail_No It's not the next active device
