Paxton Net2 IPV6 Intercom Video Feed/Routing Issue

[supra21]

I have been trying to get all of our intercom video feeds to be available on the handset in the main reception. However, the handset in the reception can only see the video feeds from the ACU's that are plugged into the same switch as the handset. We have another two intercoms plugged into an ACU that are connected to a different switch and those video feeds do not appear.

If we plug the handset into the switch that has those two intercoms connected to the feeds appear but none of the other intercom feeds from the main reception area appear.

This seems to be a routing issue as plugging the handset directly into our core switch we get nothing.

I have enabled IPV6 on our Access control VLAN on the core switch but this seems to make no difference. I am pretty new to IPV6 and would like to know if anyone can shed some light on any specific IPV6 routing configurations on the core to allow the ipv6 traffic between all switches in the network?

 

We did have this working at one point when we were using the Zyxel XGS4528F as our core switch (which had minimal IPV6 configuration options, pretty much enable/disable.

We have recently replaced this switch with the newer Zyxel XGS4600-32F and this has much more IPV6 configuration options but after speaking to Paxton they say as long as IPV6 is enabled is "it should just work" with default settings.

Edited June 21, 2017 by supra21

[Lardboy]

Hello Supra21

 

Other than doing the IPV6 "answer" (which is the stock goto for Paxton), did you get a work around as since I moved to my new switches, what you are describing is exactly what is happening to me?

 

Cheers

[K-ITS]

Hi there, do you have any old small switches anywhere that might not support IPV6? If the traffic hits them it may be what knocks it off? We have all of our switches (a mix of Netgear, Unifi and TP-Link...) all set to enable IPV6 but no other config. All of them are only a few years old however.

[Lardboy]

I still have my old HP switches (swapped out for Dell across the board). When we had our Dell cores go down, we put the old HP cores back in and the gate worked again. The moment the Dell cores went back in, it stopped.

 

We are still IPV4. It just seems like there is something silly on the cores that is not "allowing" the (for want of a better word) signal through but I cannot for the life of me work out what it is rather than it have the need to turn on IPV6.

[K-ITS]

We are still IPV4 across the school as well so I feel your pain. The only thing IPV6 is the Paxton intercom system and the entry monitors. The new Dell switches dont have MAC address filtering on them? It sounds like there is a configuration within the Dell switches that is causing your issue. Apologies I cant be of more help. we have all of our video panels routed through several switches back to the server and they work fine for the most part.

[Lardboy]

This is the issue and Paxton Support might just as well have a recorded message that just repeats the word IPV6 over and over again.

 

I have come to the conclusion that running a CAT cable from one building to the other will be much easier than working round switch after switch after switch just to get it working.

 

I just had my fingers crossed that someone had done a better job than Paxton.

 

Cheers K-ITS

[supra21]

This is the issue and Paxton Support might just as well have a recorded message that just repeats the word IPV6 over and over again.

 

I have come to the conclusion that running a CAT cable from one building to the other will be much easier than working round switch after switch after switch just to get it working.

 

I just had my fingers crossed that someone had done a better job than Paxton.

 

Cheers K-ITS

 

Yep that's exactly what I had to do in the end, ran a fibre from the switch which had 2 gates and intercoms to the switch which had the other gates and doors the receptionists needed to be able to see and open from the paxton handsets in the main reception.

 

Other than that all I can suggest (if you haven't already) is ensure your Paxton ACU's are on their own independent VLAN. I have since replaced the Zyxel core switch with an Aruba 6300M and everything is working. To be honest Zyxel was having alot of issues aside from the paxton ipv6 stuff.

[TJ-Diggers]

Assuming the ACU and monitors are all on the same VLAN? and the uplink is a trunk or the VLAN tagged on the new switches?

[supra21]

Yes all on same VLAN and tagged on the uplink.

[Lardboy]

Assuming the ACU and monitors are all on the same VLAN? and the uplink is a trunk or the VLAN tagged on the new switches?

 

Yep...it just doesn't want to work and they are very unhelpful.

 

I have got someone coming out to put a cable in now as it just seems like the easiest option.

[Lardboy]

After pulling most of my hair out, I decided to speak to Dell and see if there is anything hidden in the security of new switches that old ones didn't have.

 

It turns out that they do. The Dell engineer logged into my core switches, stopped igmp snooping on the VLAN that we use for the cameras and everything came up.

 

I hope that helps someone as I know how much it bugged the **** out of me.

[mullet_man]

After pulling most of my hair out, I decided to speak to Dell and see if there is anything hidden in the security of new switches that old ones didn't have.

 

It turns out that they do. The Dell engineer logged into my core switches, stopped igmp snooping on the VLAN that we use for the cameras and everything came up.

 

I hope that helps someone as I know how much it bugged the **** out of me.

 

Our building owners have swapped out their switches which house the cameras and Paxton door entry system and it's stopped worked, so am wondering if it's something switch related. The old switches were Zyxel's and the new ones are ifs.