Forum Discussion
Zach_Petersen_1
Nimbostratus
NimbostratusLTM/GTM Combo w/ multiple partitions - Datacenters creation outside Common
I have two F5 BIG-IP Virtual Editions each with LTM and GTM modules. We've created a secondary partition on each to allow for future expansion. All of the LTM config is deployed outside of the common partition. I've managed to make my way through getting the SSL certs shared between both devices with the bigip_add command and have verified with iqdump. The next step was to add the Datacenters to the GTM configuration. I have the secondary (non-common) partition selected, however, when I create the Datacenter objects they are always created in the "Common" partition.
Beings I wasnt able to create the Datacenters in the new partition in any obvious way I ran with the assumption that this was expected behavior. Now when I move on to create the Server objects for the GTM/LTM devices I am able to do so successfully and they pull back and show all VS online.
Moving on to creating pools is where the problems start. When I attempt to create a Pool I get this "An error has occurred while trying to process your request."
I should note that currently each device is configured with a single Self IP and the GTM listener is attached to that IP address. Also, the following is found in the GTM log. No additional log entries are generated when I attempt to create a Pool.
Oct 5 03:16:03 brsl011a alert gtmd[4530]: 011ae0f2:1: Monitor instance /Common/bigip 130.24.107.45:80 UNKNOWN_MONITOR_STATE --> UP from 130.24.107.41 (UP)
Oct 5 03:16:03 brsl011a alert gtmd[4530]: 011a6005:1: SNMP_TRAP: VS /PP2-Main-Exch/cgt-pp2-exch-preprod_app/cgt-pp2-exch-preprod_ad_http (ip:port=130.24.107.45:80) (Server /Common/ns2.wip-pp.contoso.com) state change blue --> green
Oct 5 03:16:04 brsl011a alert gtmd[4530]: 011ae0f2:1: Monitor instance /Common/bigip 130.24.107.50:135 UNKNOWN_MONITOR_STATE --> UP from 130.24.107.41 (UP)
Oct 5 03:16:04 brsl011a alert gtmd[4530]: 011a6005:1: SNMP_TRAP: VS /PP2-Main-Exch/cgt-pp2-exch-preprod_app/cgt-pp2-exch-preprod_rpc (ip:port=130.24.107.50:135) (Server /Common/ns2.wip-pp.contoso.com) state change blue --> green
Oct 5 03:16:07 brsl011a alert gtmd[4530]: 011ae0f2:1: Monitor instance /Common/bigip 130.24.107.42:80 UNKNOWN_MONITOR_STATE --> UP from 130.24.107.41 (UP)
Oct 5 03:16:07 brsl011a alert gtmd[4530]: 011a6005:1: SNMP_TRAP: VS /PP2-Main-Exch/cgt-pp2-exch-preprod_app/cgt-pp2-exch-preprod_owa_http (ip:port=130.24.107.42:80) (Server /Common/ns2.wip-pp.contoso.com) state change blue --> green
Oct 5 03:16:09 brsl011a alert gtmd[4530]: 011ae0f2:1: Monitor instance /Common/bigip 130.24.107.44:443 UNKNOWN_MONITOR_STATE --> UP from 130.24.107.41 (UP)
Oct 5 03:16:09 brsl011a alert gtmd[4530]: 011a6005:1: SNMP_TRAP: VS /PP2-Main-Exch/cgt-pp2-exch-preprod_app/cgt-pp2-exch-preprod_oa_https (ip:port=130.24.107.44:443) (Server /Common/ns2.wip-pp.contoso.com) state change blue --> green
Oct 5 03:16:10 brsl011a alert gtmd[4530]: 011ae0f2:1: Monitor instance /Common/bigip 130.24.107.43:443 UNKNOWN_MONITOR_STATE --> UP from 130.24.107.41 (UP)
Oct 5 03:16:10 brsl011a alert gtmd[4530]: 011a6005:1: SNMP_TRAP: VS /PP2-Main-Exch/cgt-pp2-exch-preprod_app/cgt-pp2-exch-preprod_as_https (ip:port=130.24.107.43:443) (Server /Common/ns2.wip-pp.contoso.com) state change blue --> green
I have a couple of questions.
1) are the Datacenters being created inside the common partition instead of the secondary partition an expected result or should I be able to create Datacenters and have them show in my secondary partition?
2) Knowing the above is currently true (datacenters in common partition) when I go to create the Pools would this be a cause for the error?
Thanks to anyone who actually read this lengthy post and to anyone who can help out!
Cheers
HamishCirrocumulus
I STARTED to create GTM configs outside of the /Common at one stage... And gave up. It just didn't play nicely. And I struggled to justify WHY I'd ever want to do that. (Especially as GTM confgs aren't synced with LTM/APM configs and that's the ONLY reason I've ever used them. To try & control sync/failover).
H
Zach_Petersen_1Thanks, Hamish. Looking at my config a bit more I see that the only thing in GTM that actually went into the second partition are the listeners. Datacenters and Servers objects seem to have ignored the second partition and created in the Common partition.
I am going to recreate the listeners in the Common partition and see if that resolves my issue.
- Zach_Petersen_1
Good news, I guess. I've recreated everything for GTM using only the common partition and I was able to create a pool without issue. Would still be interested in understanding whether or not the scenario above is supported.
- MarvinZach did you ever manage to implement several partitions within ltm and gtm within the common partition? If it's not possible i just use one partition and separate traffic based on route domains in common partition. Please post an update if you found a solution.
Zach, GTM isn't really designed for use with Partitions. We run with heavy use of partitions and getting them all to play nicely with each other was a major pain when it came to GTM. In a nutshell, listeners will respect partitions because they are virtual servers under the hood, wideIPs will do the same, but pools and GTM servers are problematic.
elvis_chavez_18someone know if this case (DATA CENTER with partition) doesnt support BIGIP F5 v12.1.2?? because I have the same issue too. Zach, you comments please..
gsharriAltostratus
This is expected behavior. Certain gslb objects can only be created in the Common partition.
Here's the article: K01990709: Certain GSLB objects can only be created or modified from the default administrative partition
