Menu
Reply
  • 2
  • 0
  • 0
Allenvik
Joining in
273 Views
Message 1 of 3
Flag for a moderator

SuperHub no longer connecting to an POe CCTV Switch after a reset.

Hi There,

We have an SuperHub2 (VMDG485) for couple of years. We also have 2 Ethernet IP cameras connected via a POe network switch, which is connected via ethernet to the SuperHub.

At some point couple weeks ago, our internet slowed down in speed a bit, and after trying few things, we decided to reset the hub to manufacture settings. The speed problem ended up not being related to the hub ('apparently') but to a maintenance being done in the local network. Anyway the hard reset was done and eventually the speed went back up again. The problem was the CCTV, that never came back !

The HUB can no longer see the cameras or the switch as 'wired devices'! Before we could see the cameras IPs, but not the switch IP. (Does the switch POe has an IP anyway?)

We have tested the line in which the switch is connected to the hub and the POe switch itself, both are working fine, so the issue is really the hub lost configuration. Also we have tried ANOTHER switch, different maker, with the same outcome.

When we look at the connected devices on the hub, it shows only the wireless devices, but not the switch or either the cameras, if we bypass the switch it works and the ip shows up. So it's an specific problem of communication between the hub and the switch, the hub is closed for the switch some how.

Finally, we remember that there was a 'port 80 or 8080' ? port forwarding setup and also a DHCP configuration too... but we don't know how to get it set properly, and we fail to take a note of it before the reset. :-(

We think is a easy setup, for someone with CCTV/SUPERHUB2 experience.

Can someone give us a hand please?

Much appreciated to anyone that attempt to help us.

E.Alen

0 Kudos
Reply
  • 10.82K
  • 308
  • 631
Forum Team
Forum Team
239 Views
Message 2 of 3
Flag for a moderator

Re: SuperHub no longer connecting to an POe CCTV Switch after a reset.

Hi Allenvik,

 

Thanks for posting and a warm welcome to the community.

 

Sorry to read that you are having issues with setting up your switch and IP camera's.

 

Are you still having this issue since you posted?

If so, I can see that you mentioned that the Super Hub won't see any wired devices? Have you tried a PC/laptop direct to the Super Hub to see if that will work?

If it now finds an IP address and you need to open ports, you can take a look at this link > Setting up Port Forwarding for a guide on how to do this.

 

Let us know how you get on

Sam


New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply
  • 2
  • 0
  • 0
Allenvik
Joining in
231 Views
Message 3 of 3
Flag for a moderator

Re: SuperHub no longer connecting to an POe CCTV Switch after a reset.

Hi Sam,

Thank you for your response!

Up to date the CCTV still not working... unfortunately...

Regarding your suggestion and question:

The super hub is able to see any PC, Laptop or individual camera wired directly to the same line where the POe switch is connected. The IPs of any wired device appears normally under the 'wired devices', as it should be. ONLY when the switch is place in between the 'whatever device' and the hub, that the IP(s) disappear, meaning the switch blocks the device to be seen by the HUB.

Before the reset, we were able to see the ips for all Cameras connected to the Switch normally, in other words, if we had 3 cameras connected to the switch, we would be able to see 3 IPS for the cameras in the 'wired devices'. It's important to know however, that the IP for switch itself never appeared... meaning to us that the switch doesn't have an IP, rather works as a gate alone. Because the switch, a POe (Power Over Ethernet) is not only a passive device, but also it sends a power signal, we think that the hub is getting confused, and needs a special rule to open the line for the devices connected to the switch, like we said before the reset we had a rule making this possible.

Coming back to the instructions suggested for port forwarding, we have tried to set it up couple of times, for 80, 8080, etc,  however one of the requirements is one existing connected IP, and the switch doesn't have one... we can't ping it either... so we are in a chicken and egg situation.

(http://help.virginmedia.com/system/selfservice.controller?CONFIGURATION=1001&PARTITION_ID=1&secureFl...)

INSTRUCTIONS SUGGEST ADDING A RULE ADDRESSING IT TO AN IP:
"IP Address: enter the local IP address for the computer that is using the service. "

In our opinion we had a 'general' port forward rule now lost, with some 'ghost ip info?' that was enabling the switch to function...

Despite the confusion with the issue, we think the problem to be just a just a missing rule issue, as suggested, that we couldn't figure out yet...

We appreciate any support.

Regards,

E.Alen

0 Kudos
Reply