Cisco 2960X and 9200L POE support for Paxton

[Andy Mackie]

Hi,

We currently have a mix of Cisco switches from 2960s, 2960X and now the 9200L.  However we are having issues with our Paxton POE door controllers.

The 2960s work with all of our Paxton Controllers

The 2960X up to hardware version 4 work with the Paxton POE controllers.

2960X Hardware version 5 and higher and 9200L will not power up the Paxton Controllers.

Has anyone else seen this issue? We are currently rolling out more Paxton controllers and struggling to keep up with the demand on power injectors.

Switch details:-

Switch Ports Model SW Version SW Image Mode
------ ----- ----- ---------- ---------- ----
* 1 52 C9200L-48P-4X 16.11.1 CAT9K_LITE_IOSXE INSTALL

Here is the power inline details:-

****#show power inline gig 1/0/23 detail
Interface: Gi1/0/23
Inline Power Mode: auto
Operational status: on
Device Detected: yes
Device Type: Ieee PD
IEEE Class: 4
Discovery mechanism used/configured: Ieee and Cisco
Police: off

Power Allocated
Admin Value: 30.0
Power drawn from the source: 15.4
Power available to the device: 15.4

Actual consumption
Measured at the port: 0.0
Maximum Power drawn by the device since powered on: 0.0

Absent Counter: 0
Over Current Counter: 0
Short Current Counter: 0
Invalid Signature Counter: 0
Power Denied Counter: 0

Power Negotiation Used: None
LLDP Power Negotiation --Sent to PD-- --Rcvd from PD--
Power Type: - -
Power Source: - -
Power Priority: - -
Requested Power(W): - -
Allocated Power(W): - -

Four-Pair PoE Supported: No
Spare Pair Power Enabled: No
Four-Pair PD Architecture: N/A

[Andy Mackie]

CDP is disbaled on all ports except where we have uplinks or Cisco APs.

I have enabled LLDP and still not working.

[girlpower]

Did anyone managed to fix this issue?

we use paxton door entry system and on switches upgrade from zyxel to cisco 9200 they wouldnt come up All door entry devices show short on last two pairs of TDR cable diagnostics.

Is there any workaround??? Shore of using zyxel switches for door entry we are out of ideas.

[david.bean]

Nope, Paxton offered little support and advise replacing all the switches.
I suspect the fault lies with the Paxton side but a workaround would be helpful.

[Andy Mackie]

No luck!!

I keep putting pressure on my account manager to push it with Cisco.  I had a trial of a Meraki switch and they worked fine with them out of the box.  

Our current solution is to but a cheap Netgear POE switch and run the Paxton controllers off this.  Not ideal, still hoping they may come up with a solution as it definitely looks like a Cisco issue due to the fact all other makes seem to work fine.

Cheers

[DugRobb]

Ran Into the Same issue running 9200l on 17.3.1 but it works fine on a no name POE+ switch has anyone from Cisco updated the cause? or am i just out the cost of a cisco switch let alone can't even get the Classic Day0 config to actually work.

[Leo Laohoo]

Do not be mistaken in thinking the 9200/9200L in the same basket as 9300/9300L, 9400, 9500 and 9600.  It is not.  

9200/9200L is a totally different to the rest of the Catalyst 9k family.  

The firmware is different to the rest.  

The bugs of the 9200/9200L were (past tense) present in older firmware versions found in 9300/9300L, 9400, 9500 and 9600. 

[Andy Mackie]

Its actually an issue with the Paxton controllers.. the older Net2 system kit isn't actually fully compliant with POE standards.

We've had to put a single Netgear POE switch in each cabinet to power them.

[curtis.rumble]

We had the same issue with C3850s and Paxton10 controllers. Dell switches provide the controllers with PoE+ no problem but the Cisco switches are flapping. We've just ran this command and has statically set the PoE. 

"power inline static max 30000"

Seems to have resolved the issue. Not getting a load of alerts in the Paxton controller now.

[Switcher2022]

Can you share your full port config? We are still unable to get the Net2 devices to power up with Cisco 9200 switching, even trying static PoE and event-2.

We have dozens of sites to upgrade and hoping to avoid adding a small unmanaged PoE switch at each site. Our old Cisco 2960 switches powered them without any special configuration. Paxton says they don't meet PoE standards and suggested using different switch. 

[curtis.rumble]

We just set the command that I mentioned before (power inline static max 30000). If you have LLDP enabled you can see more specific power requirements for most devices (show power inline [PORT] detail). Running this command shows the LLDP info power info, identifying that the Paxton device is at fault as it isn't requesting the correct power it's just identifying itself as a Class 4 device. I'd send Paxton the info from this and ask them what evidence they have for the switch being at fault.
Ruckus WAP:

#show power inline gi1/0/48 detail

Interface: Gi1/0/48

Inline Power Mode: auto

Operational status: on

Device Detected: yes

Device Type: Ieee PD

IEEE Class: 4

Discovery mechanism used/configured: Ieee and Cisco

Police: off



Power Allocated

Admin Value: 30.0

Power drawn from the source: 29.5

Power available to the device: 29.5



Actual consumption

Measured at the port: 8.0

Maximum Power drawn by the device since powered on: 11.0



Absent Counter: 0

Over Current Counter: 0

Short Current Counter: 0

Invalid Signature Counter: 0

Power Denied Counter: 0



Power Negotiation Used: IEEE 802.3at LLDP

LLDP Power Negotiation --Sent to PD-- --Rcvd from PD--

Power Type: Type 2 PSE Type 2 PD

Power Source: Primary PSE

Power Priority: low unknown

Requested Power(W): 25.0 25.0

Allocated Power(W): 25.0 25.0



Four-Pair PoE Supported: No

Spare Pair Power Enabled: No

Four-Pair PD Architecture: N/A

Paxton Controller:

#show power inline gi1/0/47 detail

Interface: Gi1/0/47

Inline Power Mode: static

Operational status: on

Device Detected: yes

Device Type: Ieee PD

IEEE Class: 4

Discovery mechanism used/configured: Ieee and Cisco

Police: on



Power Allocated

Admin Value: 30.0

Power drawn from the source: 30.0

Power available to the device: 30.0



Actual consumption

Measured at the port: 2.8

Maximum Power drawn by the device since powered on: 7.0



Absent Counter: 0

Over Current Counter: 0

Short Current Counter: 0

Invalid Signature Counter: 0

Power Denied Counter: 0



Power Negotiation Used: None

LLDP Power Negotiation --Sent to PD-- --Rcvd from PD--

Power Type: - -

Power Source: - -

Power Priority: - -

Requested Power(W): - -

Allocated Power(W): - -



Four-Pair PoE Supported: No

Spare Pair Power Enabled: No

[Andy Mackie]

Paxton admitted to me that it was the Paxton Net2 POE Controller that wasn't fully POE compliant, other devices such as handsets and intercoms seem to be fine.

We've given up on finding a solution and now use Netgear POE switches where we have to and have looked at powering the devices from mains.  The main issue with the Netgear switch is during Switch upgrades the Netgear boots first and the doors appear offline, meaning we need to visit each cabinet and reboot the netgear once the upgades have completed.

[Switcher2022]

What model switch and firmware did that work on? I'm still unable to get the Paxton controller to power up on a Cisco 9200 with 17.9.1 and the static command applied to interface. I'll check out if LLDP shows anything, but port never even comes up. 

[Andy Mackie]

The last switch we had working was a 2960X Hardware version 4 with any firmware.  After that We've not been able to get any Net2 controller to be powered.

[bob bob]

Has anyone been able to get this working on a 9200L? I'm running 17.6.3 Have tried lldp, cdp, power inline static max 30000 to no avail. 

Dec 28 17:29:20.483: %ILPOWER-5-DETECT: Interface Gi3/0/3: Power Device detected: IEEE PD
Dec 28 17:29:21.472: %ILPOWER-5-PD_ENTRY_REMOVAL: Interface GigabitEthernet3/0/3: power device entry removed, admin_state=STATIC oper_state=ON
Dec 28 17:29:21.481: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi3/0/3: PD removed

[Leo Laohoo]

Post the complete output to the command "sh version".