Forum Discussion

Nimbostratus

Mar 26, 2015

Two sync-falover groups (LTM) and one sync-group (for asm sync) setup

Hi All, I'm trying to create a setup where I have two pairs of F5s running ASM and LTM with the LTMs sync'd in two groups (sync-failover) and the ASMs sync'd in a single sync-only group. The url be...

Nimbostratus

Mar 28, 2015

Hi Scott, I've stripped back the sync groups and re-peered everything so now I have devices A and B in a HA pair and C and D in a second HA pair. I also have a sync-only group for all ASMs so the groups are all configured. So HA failover is working fine for both HA pairs. When I try and sync the ASMs I see the HA pair that I made the last ASM change on appear to be sync'd but the second pair fail sync even though I can see the ASM policies have been synchronised. If I then make a change on the second HA pair which failed the sync I then see the second pair are now in sync and the first pair are out of sync. The error message I get is 'the request folder cd01-tg01 was not found'. The name of this folder is the same as admin partition 1 so I guess the message relates to that partition and there are six admin partitions. It looks like the systems are functioning and ASM is synchronising but I don't like the sync failure messages. Is this what I should be expecting to see?

gsharri
Altostratus
Mar 30, 2015
So the sync error pertains to the sync-only group containing the 4 ASMs? Are the admin partition lists identical on both ASMs?
neil_t_66364
Nimbostratus
Mar 30, 2015
The sync error is Sync error on x.x.x.x.net: Load failed from y.y.y.y.net 01020036:3: The requested folder (/DD01-TG01) was not found. x.x.x.x being the destination device and y.y.y.y being the source device. A second error lists the same issue with the second device at the second DC. the name DD01-TG01 is an admin partition and this prefix is identical on all four devices. I'm wondering if this is listed as it's the first error discovered and every partition will fail or whether it's the only error
gsharri
Altostratus
Mar 30, 2015
Where these admin partitions manually created on each HA pair and predated the sync-only group setup? Are the partition names absolutely identical on each HA pair down to upper/lower case? Everything on bigip is case-sensitive.
neil_t_66364
Nimbostratus
Mar 31, 2015
The partitions were created prior to the sync-only setup being created. Here are the partition details and you can see they are identical across sites. DC01-Device-01 active for /Common/CD01-TG01 •active for /Common/CD05-TG01 •active for /Common/CD03-TG01 DC01-Device-02 active for /Common/traffic-group-1 •active for /Common/CD02-TG01 •active for /Common/CD04-TG01 •active for /Common/CD06-TG01 DC02-Device-01 active for /Common/CD01-TG01 •active for /Common/CD03-TG01 •active for /Common/CD05-TG01 DC02-Device-02 active for /Common/traffic-group-1 •active for /Common/CD02-TG01 •active for /Common/CD04-TG01 •active for /Common/CD06-TG01
neil_t_66364
Nimbostratus
Mar 31, 2015
Note, the use of DD01-TG01 in the previous comments was to hide the actual partition names. Here is the actual error output. The sync was done from DC01-device-01 Sync error on DC02-device-02: Load failed from DC01-device-01 01020036:3: The requested folder (/CD01-TG01) was not found. Sync error on DC02-device-01: Load failed from DC01-device-01 01020036:3: The requested folder (/CD01-TG01) was not found.
neil_t_66364
Nimbostratus
Apr 01, 2015
Hi Scott, I've raised a case with F5 support and they state this is a known issue, No. 506041 and they will be working on a hotfix. Thank you so much for help