cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
271
Views
0
Helpful
12
Replies

WS-C2960S-24PS-L PoE Issue

Aman21081992
Beginner
Beginner

Hi All,

I have installed 2 Sophos APs (AP320X) on Cisco 2960S-24P Switches individually.

Everyday this APs went offline, i have spoken to Sophos support team, they have replaced it as well. So at the moment we have installed 2 new APs at client office. these 2 are PoE APs. 

When i see power status at switch, it shows 15.4W is max we can get on 24 port switch. Does anyone know, is it known issue for Cisco 2960S series switches? or something else?

12 Replies 12

Leo Laohoo
VIP Community Legend VIP Community Legend
VIP Community Legend

Post the complete output to the following commands:

  1. sh version
  2. sh post
  3. sh interface <PORTS>

Aman21081992
Beginner
Beginner

Hi @Leo Laohoo 

PFA.

1st AP is connected to Switch1 port 2 & 2nd AP is connected to Switch 2 port 19.

Do the following: 

  1. test cable tdr interface <AP PORT>
  2. Wait for about 5 to 7 seconds for the process to complete
  3. show cable tdr interface <AP PORT>
  4. Post the complete output to #3. 

Post the output from the relevant ports only.

 

Aman21081992
Beginner
Beginner

Hi @Leo Laohoo 

MUR-SAN-SW01#test cable tdr interface gigabitEthernet 1/0/2
TDR test started on interface Gi1/0/2
A TDR test can take a few seconds to run on an interface
Use 'show cable-diagnostics tdr' to read the TDR results.
MUR-SAN-SW01#show c
MUR-SAN-SW01#show cabl
MUR-SAN-SW01#show cable-diagnostics tdf
MUR-SAN-SW01#show cable-diagnostics tdr
MUR-SAN-SW01#show cable-diagnostics tdr inter
MUR-SAN-SW01#show cable-diagnostics tdr interface gi
MUR-SAN-SW01#show cable-diagnostics tdr interface gigabitEthernet 1/0/2
TDR test last run on: May 01 20:38:30

Interface Speed Local pair Pair length Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi1/0/2 1000M Pair A 0 +/- 0 meters Pair A Normal
Pair B 0 +/- 0 meters Pair B Normal
Pair C 0 +/- 0 meters Pair C Normal
Pair D 0 +/- 0 meters Pair D Normal

 

 

MUR-SAN-SW02#test cable tdr interface gigabitEthernet 1/0/19
TDR test started on interface Gi1/0/19
A TDR test can take a few seconds to run on an interface
Use 'show cable-diagnostics tdr' to read the TDR results.
MUR-SAN-SW02#show ca
MUR-SAN-SW02#show cable
MUR-SAN-SW02#show cable-diagnostics tr
MUR-SAN-SW02#show cable-diagnostics tdr
MUR-SAN-SW02#show cable-diagnostics tdr inter
MUR-SAN-SW02#show cable-diagnostics tdr interface gi
MUR-SAN-SW02#show cable-diagnostics tdr interface gigabitEthernet 1/0/19
TDR test last run on: August 18 11:43:34

Interface Speed Local pair Pair length Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi1/0/19 1000M Pair A 16 +/- 0 meters Pair B Normal
Pair B 14 +/- 0 meters Pair A Normal
Pair C 15 +/- 0 meters Pair D Normal
Pair D 15 +/- 0 meters Pair C Normal

 

Do those APs reboot at the same time?

Aman21081992
Beginner
Beginner

@Leo Laohoo 

No. it not rebooting.
it is just shutting them down (I think from PoE side).


@Aman21081992 wrote:
No. it not rebooting.
it is just shutting them down (I think from PoE side).

So the port goes into error disable?

Aman21081992
Beginner
Beginner

@Leo Laohoo not sure, because when i see port status at the time when APs are showing offline in Sophos portal, port status is showing Connected. 


@Aman21081992 wrote:

@Leo Laohoo not sure, because when i see port status at the time when APs are showing offline in Sophos portal, port status is showing Connected. 


The next time this happens, post the following output: 

  1. sh interface status err
  2. sh power inline
  3. sh log

HI @Leo Laohoo 

FYI. These APs are offline again, where as ports are showing connected and transmitting power. 

MUR-SAN-SW01#show power inline

Module Available Used Remaining
(Watts) (Watts) (Watts)
------ --------- -------- ---------
1 370.0 15.4 354.6
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi1/0/1 auto off 0.0 n/a n/a 30.0
Gi1/0/2 auto on 15.4 Ieee PD 3 30.0
Gi1/0/3 auto off 0.0 n/a n/a 30.0

 

MUR-SAN-SW01#show log
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

 

No Inactive Message Discriminator.


Console logging: level debugging, 28279 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 28279 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
File logging: disabled
Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 28272 message lines logged
Logging Source-Interface: VRF Name:

Log Buffer (4096 bytes):
ce GigabitEthernet1/0/18, changed state to down
*May 2 17:29:55.250: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/18, changed state to up
*May 2 17:29:58.401: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/18, changed state to down
*May 2 17:29:59.407: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/18, changed state to down
*May 2 17:30:01.960: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/18, changed state to up
*May 2 17:30:02.962: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/18, changed state to up
*May 2 17:53:20.210: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to down
*May 2 17:53:21.201: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to down
*May 2 17:54:13.195: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to up
*May 2 17:54:14.196: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to up
*May 2 17:55:26.669: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to down
*May 2 17:55:27.675: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to down
*May 2 17:55:50.613: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to up
*May 2 17:55:51.614: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to up
*May 2 17:56:12.460: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to down
*May 2 17:56:13.467: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to down
*May 2 17:57:29.022: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to up
*May 2 17:57:30.023: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to up
*May 2 18:00:01.763: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to down
*May 2 18:00:05.412: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to down
*May 2 18:00:55.780: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to up
*May 2 18:00:56.781: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to up
*May 2 18:01:53.577: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to down
*May 2 18:01:54.584: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to down
*May 2 18:04:01.855: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to up
*May 2 18:04:02.856: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to up
*May 2 18:04:35.394: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to down
*May 2 18:04:36.406: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to down
*May 2 18:04:58.478: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to up
*May 2 18:04:59.479: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to up
*May 2 18:12:52.544: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to down
*May 2 18:12:56.267: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to down
*May 2 18:13:47.647: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to up
*May 2 18:13:48.649: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to up
*May 2 18:34:47.385: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to down
*May 2 18:34:49.393: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to up
*May 2 18:34:50.987: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to down
*May 2 18:34:51.994: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to down
*May 2 18:35:44.664: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to up
*May 2 18:35:45.665: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to up

 


MUR-SAN-SW02#show power inline

Module Available Used Remaining
(Watts) (Watts) (Watts)
------ --------- -------- ---------
1 370.0 15.4 354.6
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi1/0/1 auto off 0.0 n/a n/a 30.0
Gi1/0/2 auto off 0.0 n/a n/a 30.0
Gi1/0/3 auto off 0.0 n/a n/a 30.0
Gi1/0/4 auto off 0.0 n/a n/a 30.0
Gi1/0/5 auto off 0.0 n/a n/a 30.0
Gi1/0/6 auto off 0.0 n/a n/a 30.0
Gi1/0/7 auto off 0.0 n/a n/a 30.0
Gi1/0/8 auto off 0.0 n/a n/a 30.0
Gi1/0/9 auto off 0.0 n/a n/a 30.0
Gi1/0/10 auto off 0.0 n/a n/a 30.0
Gi1/0/11 auto off 0.0 n/a n/a 30.0
Gi1/0/12 auto off 0.0 n/a n/a 30.0
Gi1/0/13 auto off 0.0 n/a n/a 30.0
Gi1/0/14 auto off 0.0 n/a n/a 30.0
Gi1/0/15 auto off 0.0 n/a n/a 30.0
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi1/0/16 auto off 0.0 n/a n/a 30.0
Gi1/0/17 auto off 0.0 n/a n/a 30.0
Gi1/0/18 auto off 0.0 n/a n/a 30.0
Gi1/0/19 auto on 15.4 Ieee PD 3 30.0

 

MUR-SAN-SW02#show log
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

 

No Inactive Message Discriminator.


Console logging: level debugging, 611 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 611 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
File logging: disabled
Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 610 message lines logged
Logging Source-Interface: VRF Name:

Log Buffer (4096 bytes):
protocol on Interface GigabitEthernet1/0/19, changed state to down
Aug 16 23:21:58.281: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to down
Aug 16 23:22:01.028: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to up
Aug 16 23:22:02.030: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up
Aug 17 00:12:57.359: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to down
Aug 17 00:12:58.366: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to down
Aug 17 00:13:02.235: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to up
Aug 17 00:13:03.237: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to up
Aug 17 00:13:24.393: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to down
Aug 17 00:13:25.394: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to down
Aug 17 00:13:33.872: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to up
Aug 17 00:13:34.874: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to up
Aug 17 22:50:11.570: %LINK-5-CHANGED: Interface GigabitEthernet1/0/19, changed state to administratively down
Aug 17 22:50:12.572: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down
Aug 17 22:50:16.195: %ILPOWER-7-DETECT: Interface Gi1/0/19: Power Device detected: IEEE PD
Aug 17 22:50:16.929: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to down
Aug 17 22:50:16.945: %SYS-5-CONFIG_I: Configured from console by cisco on vty0 (10.254.102.29)
Aug 17 22:50:17.243: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/19: Power granted
Aug 17 22:50:22.990: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to up
Aug 17 22:50:23.991: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up
Aug 17 22:51:39.436: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down
Aug 17 22:51:40.442: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to down
Aug 17 22:51:42.713: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to up
Aug 17 22:51:43.714: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up
Aug 17 22:51:55.281: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down
Aug 17 22:51:56.287: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to down
Aug 17 22:51:59.077: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to up
Aug 17 22:52:00.078: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up
Aug 17 22:53:28.940: %SYS-5-CONFIG_I: Configured from console by cisco on vty0 (10.254.102.29)
Aug 18 01:43:38.437: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down
Aug 18 01:43:39.443: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to down
Aug 18 01:43:42.317: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to up
Aug 18 01:43:43.318: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up
Aug 18 07:03:33.413: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to down
Aug 18 07:03:34.419: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to down
Aug 18 07:03:38.446: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to up
Aug 18 07:03:39.448: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to up
Aug 18 07:04:26.400: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to down
Aug 18 07:04:27.407: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to down
Aug 18 07:04:35.760: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to up
Aug 18 07:04:36.761: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/20, changed state to up

 

Jitendra Kumar
Rising star
Rising star

APX 320x is required for the POE+ power Switch.

Power consumption 18.9 W (max.)
Power over Ethernet
(PoE) requirements
802.3

To ensure safe operation, this product is intended to be used only with Listed,
IEEE 802.3at-compliant, Power over Ethernet Power Sourcing Equipment that is
designed for connection to outdoor devices

In this there .3at complaint power required that the issue there will not be issue with Switch.

What is the difference between PoE and PoE+?
  • PoE is the 802.3af standard, and PoE+ is the 802.3at standard.
  • The main difference between the 802.3af (PoE) and 802.3at (PoE+) standards is the maximum amount of power they provide over the Cat5 cabling. 
  • The maximum amount of power for the 802.3af (PoE) standard is 15.4 watts. 
  • The maximum for the 802.3at (PoE+) standard is 25.5 watts.

What you can do buy a power injector from the sophos.

 

Thanks,
Jitendra

Leo Laohoo
VIP Community Legend VIP Community Legend
VIP Community Legend

If these are the only two APs having problems, I'd recommend getting the a TDR on the two cable runs.  

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers