Comment by joseignacio.carretero@fiware.org :

The ports are internally opened, the synchronization can be made using
internal IPs 10.0.64.33 (that doesn't cross the firewall), and It
shouldn't work using the external IPs (130.206.84.3x).

Regards,
José Ignacio

El 27/01/17 a las 13:49, Federico Michele Facca escribió:
> dear support team,
> apparently you entirely blocked the access to 27017 tcp port on:
>
> 130.206.84.32 (public ip) / 10.0.64.32 (private ip)
> 130.206.84.33 (public ip) / 10.0.64.33 (private ip)
> 130.206.84.34 (public ip) / 10.0.64.34 (private ip)
>
> can you open it again? the port need to be reachable by the private
> network 10.0.64.0/25 if it is not reachable:
> 1 - the mongodb replicate set breaks
> 2 - the context broker cannot reach the mongodb servers
>
> thanks,
> federico
>
> Dr. Federico Michele Facca
> /Head of Martel Lab/
>
> Martel Innovate
> Dorfstrasse 73 - 3073 Gümligen (Switzerland)
> 0041 78 807 58 38
> 0041 31 994 25 25
> martel-innovate.com <http://martel-innovate.com>
>
>
>
>
>
>

Hi Jose,
thanks, then I may need some help with iptables when I run
nmap -Pn -n -p 27017 --script=mongodb-info,mongodb-databases -T5 10.0.64.32 / 33 / 34

i get that the port is filtered and when I add the member to the cluster, it does not work.

thanks for any hint and help!
federico

Well, the fact is that it is opened. Just try a simpler nmap command, just trying to stablish a full tcp connection:

nmap -sT -p 27017 -T5 10.0.64.32,33,34

You'll see the port is opened and the host is up.

Regards,
José Ignacio

Is the ticket solved?

Comment by federico.facca@martel-consulting.ch :

yes,
thanks!