cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5044
Views
0
Helpful
21
Replies

Cisco 3850 Short-circuit BISP Events on Log

fdharmawan
Level 4
Level 4

Hi Guys,

 

So couple days ago one of my switch unit on the stack suddenly shut down. I unplugged all the cables (stack power, stack data, and power supply). Then I boot up the switch with PSU only, no stack cable attached. After the switch finished booting up, I found the following command repeatedly shown in the console.

 

Nov 4 08:03:55.007 JKT: %PLATFORM_STACKPOWER-4-BISP_PORT_A_SC: Switch 2 experienced a short-circuit BISP event on port 1

Nov 4 08:04:56.825 JKT: %PLATFORM_STACKPOWER-4-BISP_PORT_A_SC: Switch 2 experienced a short-circuit BISP event on port 1
Nov 4 08:05:28.015 JKT: %PLATFORM_STACKPOWER-4-BISP_PORT_A_SC: Switch 2 experienced a short-circuit BISP event on port 1
Nov 4 08:06:00.691 JKT: %PLATFORM_STACKPOWER-4-BISP_PORT_A_SC: Switch 2 experienced a short-circuit BISP event on port 1

 

I thought it only affects the stack power unit, but when I plugged the IP phones and APs back, none of the ports are operational. I checked the log, I got the following message.

%ILPOWER-7-DETECT : Interface Te2/0/1: inline power denied. Reason : insufficient power

 

So I checked the power inline, and discovered it has no power supplied.

Module Available Used Remaining
(Watts) (Watts) (Watts)
------ --------- -------- ---------
2 n/a n/a n/a

 

While on the other unit, I got the power

Module Available Used Remaining
(Watts) (Watts) (Watts)
------ --------- -------- ---------
1 1440.0 187.4 1252.6

 

I tried to disable the stack-power port so I can suppress the alerts by issuing "stack-power switch 2 port 1 disable" command, but the alerts still there.

 

I read the following post https://community.cisco.com/t5/switching/cisco-3850-poe-switch-power-issue-with-ports/td-p/4138611 and the bug related https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvj76259?rfs=iqvred. My current version is 16.3.7 and my unit is WS-C3850-24XU. So if I upgrade to 16.6.X and the issue still persists, does it mean the MOSFET is causing this? Is there any other way to confirm the issue? Thanks.

1 Accepted Solution

Accepted Solutions

RMA the appliance.

View solution in original post

21 Replies 21

Leo Laohoo
Hall of Fame
Hall of Fame

This is not MOSFET. 

If this was MOSFET, the ports would not supply PoE.  

Hi Leo,

It is said that the power available is n/a. Is there any way to pinpoint the issue? Or should I try to upgrade to 16.6X first?

Post the complete output to the following commands: 

  1. sh version
  2. sh log on switch active uptime detail
  3. sh post

Hi Leo,

Below is the output.

Switch#show version
Cisco IOS Software [Denali], Catalyst L3 Switch Software (CAT3K_CAA-UNIVERSALK9- M), Version 16.3.7, RELEASE SOFTWARE (fc4)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2018 by Cisco Systems, Inc.
Compiled Fri 03-Aug-18 23:49 by mcpre


Cisco IOS-XE software, Copyright (c) 2005-2018 by cisco Systems, Inc.
All rights reserved. Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0. The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0. For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
software.


ROM: IOS-XE ROMMON
BOOTLDR: CAT3K_CAA Boot Loader (CAT3K_CAA-HBOOT-M) Version 4.68, RELEASE SOFTWAR E (P)

ID-JKTASW4302 uptime is 12 weeks, 5 days, 2 hours, 31 minutes
Uptime for this control processor is 12 weeks, 5 days, 2 hours, 34 minutes
System returned to ROM by reload at 15:39:22 JKT Sat Aug 7 2021
System restarted at 15:45:03 JKT Sat Aug 7 2021
System image file is "flash:cat3k_caa-universalk9.16.03.07.SPA.bin"
Last reload reason: Reload Command

 

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.


Technology Package License Information:

-----------------------------------------------------------------
Technology-package Technology-package
Current Type Next reboot
------------------------------------------------------------------
lanbasek9 Permanent lanbasek9

cisco WS-C3850-24XU (MIPS) processor (revision J0) with 865683K/6147K bytes of m emory.
Processor board ID Masked
2 Virtual Ethernet interfaces
36 Gigabit Ethernet interfaces
68 Ten Gigabit Ethernet interfaces
4 Forty Gigabit Ethernet interfaces
2048K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
250456K bytes of Crash Files at crashinfo:.
252000K bytes of Crash Files at crashinfo-3:.
1609272K bytes of Flash at flash:.
1611414K bytes of Flash at flash-3:.
0K bytes of at webui:.
250456K bytes of Crash Files at crashinfo-2:.
1609272K bytes of Flash at flash-2:.

Base Ethernet MAC Address : Masked
Motherboard Assembly Number : Masked
Motherboard Serial Number : Masked
Model Revision Number : J0
Motherboard Revision Number : B0
Model Number : WS-C3850-24XU
System Serial Number : Masked


Switch Ports Model SW Version SW Image Mode
------ ----- ----- ---------- ---------- ----
* 1 38 WS-C3850-24XU 16.3.7 CAT3K_CAA-UNIVERSALK9 BUNDLE
2 38 WS-C3850-24XU 16.3.7 CAT3K_CAA-UNIVERSALK9 BUNDLE
3 32 WS-C3850-24T 16.3.7 CAT3K_CAA-UNIVERSALK9 BUNDLE


Switch 02
---------
Switch uptime : 2 days, 10 hours, 40 minutes

Base Ethernet MAC Address : Masked
Motherboard Assembly Number : Masked
Motherboard Serial Number : Masked
Model Revision Number : J0
Motherboard Revision Number : B0
Model Number : WS-C3850-24XU
System Serial Number : Masked

Switch 03
---------
Switch uptime : 12 weeks, 5 days, 2 hours, 34 minutes

Base Ethernet MAC Address : Masked
Motherboard Assembly Number : Masked
Motherboard Serial Number : Masked
Model Revision Number : AC0
Motherboard Revision Number : B0
Model Number : WS-C3850-24T
System Serial Number : Masked

Configuration register is 0x102

 

Switch#show post
Stored system POST messages:

Switch 1
---------

POST: MBIST Tests : Begin
POST: MBIST Tests : End, Status Passed

POST: CRYPTO Tests : Begin
POST: CRYPTO Tests : End, Status Passed

POST: PHY Loopback: loopback Test : Begin
POST: PHY Loopback: loopback Test : End, Status Passed

POST: Inline Power Controller Tests : Begin
POST: Inline Power Controller Tests : End, Status Passed

POST: Thermal, Temperature Tests : Begin
POST: Thermal, Temperature Tests : End, Status Passed

POST: Thermal, Fan Tests : Begin
POST: Thermal, Fan Tests : End, Status Passed

POST: SIF Tests : Begin
POST: SIF Tests : End, Status Passed


Switch 2
---------

POST: MBIST Tests : Begin
POST: MBIST Tests : End, Status Passed

POST: CRYPTO Tests : Begin
POST: CRYPTO Tests : End, Status Passed

POST: PHY Loopback: loopback Test : Begin
POST: PHY Loopback: loopback Test : End, Status Passed

POST: Inline Power Controller Tests : Begin
POST: Inline Power Controller Tests : End, Status Passed

POST: Thermal, Temperature Tests : Begin
POST: Thermal, Temperature Tests : End, Status Passed

POST: Thermal, Fan Tests : Begin
POST: Thermal, Fan Tests : End, Status Passed

POST: SIF Tests : Begin
POST: SIF Tests : End, Status Passed


Switch 3
---------

POST: MBIST Tests : Begin
POST: MBIST Tests : End, Status Passed

POST: CRYPTO Tests : Begin
POST: CRYPTO Tests : End, Status Passed

POST: PHY Loopback: loopback Test : Begin
POST: PHY Loopback: loopback Test : End, Status Passed

POST: Thermal, Temperature Tests : Begin
POST: Thermal, Temperature Tests : End, Status Passed

POST: Thermal, Fan Tests : Begin
POST: Thermal, Fan Tests : End, Status Passed

POST: SIF Tests : Begin
POST: SIF Tests : End, Status Passed

 

Switch#show logging onboard switch active uptime detail
--------------------------------------------------------------------------------
UPTIME SUMMARY INFORMATION
--------------------------------------------------------------------------------
First customer power on : 03/27/2018 21:34:06
Total uptime : 3 years 11 weeks 2 days 17 hours 42 minutes
Total downtime : 0 years 20 weeks 2 days 19 hours 32 minutes
Number of resets : 10
Number of slot changes : 0
Current reset reason : Reload
Current reset timestamp : 08/07/2021 08:43:50
Current slot : 255
Chassis type : 0
Current uptime : 0 years 12 weeks 5 days 2 hours 5 minutes
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
UPTIME CONTINUOUS INFORMATION
--------------------------------------------------------------------------------
Time Stamp | Reset | Uptime
MM/DD/YYYY HH:MM:SS | Reason | years weeks days hours minutes
--------------------------------------------------------------------------------
03/27/2018 21:34:06 Reload 0 0 0 0 0
03/27/2018 21:43:13 Reload 0 0 0 0 5
03/27/2018 21:52:29 Reload 0 0 0 0 0
05/31/2018 07:43:00 Reload 0 0 0 0 0
08/17/2018 13:12:58 Reload 0 0 0 0 5
08/17/2018 13:05:13 Reload 0 0 0 0 5
08/17/2018 15:42:03 Reload 0 0 0 2 5
11/10/2018 01:53:00 Reload 0 12 0 9 4
02/15/2019 20:55:48 Reload 0 13 6 18 4
07/13/2019 20:19:53 Reload 0 21 0 20 4
08/07/2021 08:43:50 Reload 2 3 4 12 3
--------------------------------------------------------------------------------


@fdharmawan wrote:

Switch 02
---------
Switch uptime : 2 days, 10 hours, 40 minutes


Ok, I made a mistake.  The command should be:  sh log on switch 2 uptime detail

Hi Leo,
Below is the output.

Switch#sh logging onboard switch 2 uptime detail
--------------------------------------------------------------------------------
UPTIME SUMMARY INFORMATION
--------------------------------------------------------------------------------
First customer power on : 03/27/2018 09:17:36
Total uptime : 3 years 11 weeks 2 days 16 hours 37 minutes
Total downtime : 0 years 20 weeks 3 days 22 hours 47 minutes
Number of resets : 13
Number of slot changes : 0
Current reset reason : Reload reason not captured
Current reset timestamp : 11/02/2021 00:37:30
Current slot : 255
Chassis type : 0
Current uptime : 0 years 0 weeks 3 days 0 hours 5 minutes
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
UPTIME CONTINUOUS INFORMATION
--------------------------------------------------------------------------------
Time Stamp | Reset | Uptime
MM/DD/YYYY HH:MM:SS | Reason | years weeks days hours minutes
--------------------------------------------------------------------------------
03/27/2018 09:17:36 Reload 0 0 0 0 0
03/27/2018 09:26:34 Reload 0 0 0 0 5
03/27/2018 09:35:27 Reload 0 0 0 0 0
05/31/2018 03:28:32 Reload 0 0 0 0 0
08/17/2018 12:53:10 Reload 0 0 0 0 5
08/17/2018 13:05:12 Reload 0 0 0 0 5
08/17/2018 15:41:55 Reload 0 0 0 2 5
11/10/2018 08:19:42 Reload 0 12 0 9 3
02/15/2019 20:55:42 Reload 0 13 6 18 3
07/13/2019 20:19:44 Reload 0 21 0 20 4
08/07/2021 08:43:45 Reload 2 3 4 12 7
10/27/2021 02:14:50 Reload 0 11 3 2 4
11/02/2021 00:32:41 Reload 0 0 5 22 5
11/02/2021 00:37:30 Reload 0 0 0 0 0
--------------------------------------------------------------------------------


@fdharmawan wrote:

So couple days ago one of my switch unit on the stack suddenly shut down


According to the output, switch 2 reloaded after someone issued the command "reload". 

Hi Leo,

 

We noticed the switch went down since some APs and IP phones were monitored not reachable. So when we check the switch, it was on some kind of powered down state, no response on console and no LEDs were on. So I took off the cables then boot the switch solely on PSU. After monitoring for days, we connect the stack data cables and it went some restarts automatically. Does this count?

Hold on, this does not make sense. 

The switches are WS-C3850-24XU and WS-C3850-24T.  
MOSFET only affects PoE.  

WS-C3850-24T is a non-PoE switch.  

Hi Leo,

 

We have PoE for WS-C3850-24XU, but not for WS-C3850-24T. On our deployment it always has been since the delivery from Cisco. Does WS-C3850-24XU not supposed to have PoE?

Oh no.  I got WS-C3850-24XU confused with WS-C3850-24S!

Is the power stack cable attached?

Hi Leo,

 

No the stack power is not attached, due to %PLATFORM_STACKPOWER-4-BISP_PORT_A_SC: Switch 2 experienced a short-circuit BISP event on port 1 logs. I tried to disabled the stack port from the config, but apparently the issue is from a component inside, since the log still comes up after disabling and dismantling the stack port.

RMA the appliance.