FusionHUB-VMWare

HI All

So we have tried to setup a FusionHub for making some SpeedFusion connections, from different devices, this is at the moment just at test setup.

First it worked on the Hyper-V installation, with ip 192.168.10.8 then we installed it on an ESXi server, and now with internal ip 192.168.10.10 we generated a test license on the Incontrol portal the 30 day one.

There is an Balance 20x router in front of the FusionHub, we port forward 32015 and 4500 to the 192.168.10.10 ip, to make sure when traffic comming in external ip, it will go to the FusionHub VMware ip.

It activate the license but we can’t see the device in Incontrol2, it just keep saying offline.

And as we deleted the Hyper-V version, and released and deleted the old license, we can’t go back to the Hyper-V instance witched worked.

Tried to install thou one FusionHub again on the Hyper-V but we end up as the same on the VMware, so better fix the VMware version, as that is where we want to be.

Anyone have an idea, is there a route there is missing or something ? nothing have changed on the Balance 20X after the switch to VMWare, only that we forwarded traffic now to 192.168.10.10.

So the network traffic would be logical.
External IP > Balance 20X > Traffic forwarded on 32015 and 4500 to 192.168.10.10 (Fusionhub)

Firmware 8.3.0.

Hope some one have the magic bullet.
Glenn

1 Like

Hi All

An update this morning everything is working, so this topic can be marked as complete, and also the speedfusion links was up and running, so we are thinking it was routing protocols somewhere.

Hi All

So we found out this one, was due to the problem at Peplink it self, there was a problem on the Amazon cloud.