How many API Connect Gateway services (“domains”) can I deploy to one DataPower appliance?

Per https://www.ibm.com/support/knowledgecenter/en/SSMNED_5.0.0/com.ibm.apic.cmc.doc/create_multiple_gateway_clusters.html it seems to be supported to deploy multiple API Connect Gateway services (“domains”) to one DataPower appliance.
Is there any recommended upper limited determined in performance testing, e.g. comparing a virtual DataPower Gateway with let’s say 8 vCPU / 8 GB RAM vs a physical DataPower Gateway (m/t 8436) which owns more cores and RAM?
For example, is 13 such domains still working well or showed troubles? (and please don’t say number 13 will certainly cause issues just because it is 13) ;-P
Or is this a new range (10-20) that yet needs to be tested and finally as always just depends on individual configuration and traffic pattern?
Thanks for your thoughts.

Related:

Node Red – Send Device to Gateway Publish/Subscribe – IBM Bluemix simulator

The requirement is to create Node red app to read a message from n devices and m gateways and publish to IBM IOT as MQTT using MQTT node, also process and store it in cloudant DB. If there any update then the device should subscribe for the commands. I read from IBM blue mix portal and was able to send and receive the message for gateways using MQTT node to IBM IOT node.
Need clarification on the below,

1. Can use node red simulator to send
message from device/gateway
simultaneously? (because gateway will
send the message directly to IBM
Watson IOT but devices always will
send a message to gateway)

2. How to identify or differentiate the
message received from device
/Gateway in Watson IOT node

3. How the sequence of the message
published? is in FIFO order?

4. Time to live for the message? If
MQTT broker disconnected then how
the message will be published like
i.e how many messages can be queued
and size of the queue?

5. How can we notify MQTT /device
disconnected to the other end

Thanks in Advance

Related:

Bluemix container docker connect to the ibm network

I would like to connect a docker container to the IBM LAN. Unfortunately, bluemix uses an own ip space. Is there a gateway or a possibility for that.

I mean a connection from the 172 network to the 9 network
A public address is not a solution
With public adr can I connect the docker from the 9 network
but A connect from the 172 to the 9 isn’t possible

Related:

Windows Server 2003 multiple gateways possible solutions

I have the following problem that keeps me sleepless for the last few nights.

I inherited some servers from the guy who retired, and I noticed that one of the interfaces sometimes gets frozen on one of the servers, making people unable to connect to it.

Now, the details:
We have 3 servers- one is the Database server, which hosts only the DB, and its connected to the Access Server, which also has some IIS-based webserver, which again provides .aspx-based controls for the customers, who visit out 3rd server, on which we host the website. I think the following picture will describe it better:
Network graph

The problem is that the Access Server is configured with 2 default gateways (sic!), but after all, according to route print, it uses the first ISP gateway:

Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0   bb.bbb.bbb.241   bb.bbb.bbb.243     10
          0.0.0.0          0.0.0.0   aaa.aa.aaa.129   aaa.aa.aaa.130     10
   bb.bbb.bbb.240  255.255.255.248   bb.bbb.bbb.243   bb.bbb.bbb.243     10
   bb.bbb.bbb.243  255.255.255.255        127.0.0.1        127.0.0.1     10
   bb.255.255.255  255.255.255.255   bb.bbb.bbb.243   bb.bbb.bbb.243     10
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
      192.168.0.0    255.255.255.0     192.168.0.97     192.168.0.97     10
     192.168.0.97  255.255.255.255        127.0.0.1        127.0.0.1     10
    192.168.0.255  255.255.255.255     192.168.0.97     192.168.0.97     10
   aaa.aa.aaa.128  255.255.255.248   aaa.aa.aaa.130   aaa.aa.aaa.130     10
   aaa.aa.aaa.130  255.255.255.255        127.0.0.1        127.0.0.1     10
   aaa.aa.aaa.255  255.255.255.255   aaa.aa.aaa.130   aaa.aa.aaa.130     10
        224.0.0.0        240.0.0.0   bb.bbb.bbb.243   bb.bbb.bbb.243     10
        224.0.0.0        240.0.0.0     192.168.0.97     192.168.0.97     10
        224.0.0.0        240.0.0.0   aaa.aa.aaa.130   aaa.aa.aaa.130     10
  255.255.255.255  255.255.255.255   bb.bbb.bbb.243   bb.bbb.bbb.243      1
  255.255.255.255  255.255.255.255     192.168.0.97     192.168.0.97      1
  255.255.255.255  255.255.255.255   aaa.aa.aaa.130   aaa.aa.aaa.130      1
Default Gateway:    aaa.aa.aaa.129

Now here is the deal – how can I make it work “normally”, or at least as close to normal as it can (So I won’t have to RDPlogin and restart the .129 adapter everyday)?

At first, I thought of a simple watchdog script, which will ping the freezing NIC from the second source address, but it failed miserably, because in WS2003 the ping command is still retarded and allows only IPv6 with -S parameter. It looks like there is no fix around that, not even a 3rd party solution, and getting ping.exe straight from Windows 7 doesn’t work (Really, I tried that too!)

Then I thought about buying a dual-WAN router, plugging it in between server and ISPs’ routers, and forward specified ports to one LAN connection – It should work, as long as we assume that current problems are caused by the NIC in that server, but that’s pretty easy to sort out, because we have the WWW server on the same connection, and its uptime is almost 100% for the last year (excluding not-company related failures), but even if I set failover on that interface, the clients’ application still uses IP to connect, so it will still report unresponsive to the client, but we would have the main problem fixed.

The third option is doing some magic to the Load Balancing options, using some other software, but AFAIK, it never worked good on windows (and freezing adapters are quite common for me)

There is also fourth option, which is nuking everything and getting a new server and/or system, but here the biggest problem would be license – we are hosting SQL Server DB behind it, server backend which communicates with that DB and returns tables for customers on the web AND our employees (about 200+) who use our company program to communicate with the databases. This obviously needs separate CAL licenses, and W2003 was the last one which didn’t need that in Web Edition.

Can anyone point me in the right direction?

Related:

Connect your Docker container to enterprise services with the Bluemix Secure Gateway

The Bluemix Secure Gateway service offers a flexible means to
securely expose back-end enterprise services to your Bluemix applications.
Creating the Secure Gateway is relatively straightforward through the Bluemix
user interface. Ensuring that the gateway is secure and then leveraging the
gateway require some additional steps. This tutorial shows you how to
configure the gateway, how to add destinations to local enterprise services,
how to leverage a Docker container to establish the connection from your
enterprise, and how to access the service from your applications.

Related:

Use specific interface for outbound connections (Ubuntu 9.04)

I have two ethernet interfaces in my computer, which is running Ubuntu 9.04. Both interfaces sport static IPs, but use separate gateways. My /etc/network/interfaces file looks something like this:

auto eth0 eth1
iface eth0 inet static
  address 10.0.0.5
  netmask 255.255.255.0
  gateway 10.0.0.1

iface eth1 inet static
  address 192.168.2.5
  netmask 255.255.255.0
  gateway 192.168.2.1

I want to have all traffic going to the internet-at-large run through eth0, but it seems to want to go through eth1. Is there a way that I can channel my general outbound traffic through eth0 instead and only use eth1 for traffic to its subnet?

The answer should be persistent; that is to say, it should survive reboot without a superuser needing to run a command after restart.

EDIT: as requested, here is the output of my route -n command:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 eth1
0.0.0.0         192.168.2.1     0.0.0.0         UG    100    0        0 eth1
0.0.0.0         10.0.0.1        0.0.0.0         UG    100    0        0 eth0

Related: