Hi,

I'm setting up two VMs (datapower OVA, v10.0.5.x) as gateways in a apic cloud. The customer only have capacity for two VMs. The two datapower VMs are sitting behind a loadbalancer and both will be active. The requirement is also to separate internal and external api services. Each VM has separate interfaces for internal and external traffic + one for management.

So in each datapower VM I created two domains, one for internal and one for external (same domain names in both VMs). In each domain I created a gateway-service. I followed the documentation about configuration (Configuring DataPower API Gateway) and registered the gateway services in the cloud manager as 4 separate.

Their objective is to have two loadbalanced gateways for internal resp. external api traffic.

Questions:
-Is this is a valid setup?
-Do I need to create all peering object for each gateway-service? If not, how do I configure?
-What is the disadvantage with a setup like this? if it is valid... rate-limit could be one..?

Regards,
Rikard Almroth

Hi Richard,

Please see this article that discusses this setup:

https://chrisphillips-cminion.github.io/apiconnect/2022/10/19/APIC-DataPowerQuorum2Node0.html

Respective gateway peerings need to be configured between the two datapowers.

From my perspective you would need to implement some operational procedures to make this work well.

Regards

Hi,

I'm setting up two VMs (datapower OVA, v10.0.5.x) as gateways in a apic cloud. The customer only have capacity for two VMs. The two datapower VMs are sitting behind a loadbalancer and both will be active. The requirement is also to separate internal and external api services. Each VM has separate interfaces for internal and external traffic + one for management.

So in each datapower VM I created two domains, one for internal and one for external (same domain names in both VMs). In each domain I created a gateway-service. I followed the documentation about configuration (Configuring DataPower API Gateway) and registered the gateway services in the cloud manager as 4 separate.

Their objective is to have two loadbalanced gateways for internal resp. external api traffic.

Questions:
-Is this is a valid setup?
-Do I need to create all peering object for each gateway-service? If not, how do I configure?
-What is the disadvantage with a setup like this? if it is valid... rate-limit could be one..?

Regards,
Rikard Almroth

Hi Szymon,

Thank you, I have read this article - and maybe the second option is what I should go for.
But what if I choose to just configure them as separate gateway services - one internal and one external in each datapower vm. 
Would that be a valid setup? 

Regards,
Rikard

Hi Richard,

Please see this article that discusses this setup:

https://chrisphillips-cminion.github.io/apiconnect/2022/10/19/APIC-DataPowerQuorum2Node0.html

Respective gateway peerings need to be configured between the two datapowers.

From my perspective you would need to implement some operational procedures to make this work well.

Regards

Hi,

I'm setting up two VMs (datapower OVA, v10.0.5.x) as gateways in a apic cloud. The customer only have capacity for two VMs. The two datapower VMs are sitting behind a loadbalancer and both will be active. The requirement is also to separate internal and external api services. Each VM has separate interfaces for internal and external traffic + one for management.

So in each datapower VM I created two domains, one for internal and one for external (same domain names in both VMs). In each domain I created a gateway-service. I followed the documentation about configuration (Configuring DataPower API Gateway) and registered the gateway services in the cloud manager as 4 separate.

Their objective is to have two loadbalanced gateways for internal resp. external api traffic.

Questions:
-Is this is a valid setup?
-Do I need to create all peering object for each gateway-service? If not, how do I configure?
-What is the disadvantage with a setup like this? if it is valid... rate-limit could be one..?

Regards,
Rikard Almroth

Hi,

I'm setting up two VMs (datapower OVA, v10.0.5.x) as gateways in a apic cloud. The customer only have capacity for two VMs. The two datapower VMs are sitting behind a loadbalancer and both will be active. The requirement is also to separate internal and external api services. Each VM has separate interfaces for internal and external traffic + one for management.

So in each datapower VM I created two domains, one for internal and one for external (same domain names in both VMs). In each domain I created a gateway-service. I followed the documentation about configuration (Configuring DataPower API Gateway) and registered the gateway services in the cloud manager as 4 separate.

Their objective is to have two loadbalanced gateways for internal resp. external api traffic.

Questions:
-Is this is a valid setup?
-Do I need to create all peering object for each gateway-service? If not, how do I configure?
-What is the disadvantage with a setup like this? if it is valid... rate-limit could be one..?

Regards,
Rikard Almroth