09-14-2018 06:01 AM - edited 03-08-2019 04:09 PM
I have a 3560cx switch at a property (I'm not onsite) that keeps rebooting 1 or 2 times a day. When I do show version it says "Last reload reason: Power-on"
Any ideas on what would cause it to reboot this frequently?
Thank you
Solved! Go to Solution.
09-19-2018 12:10 PM
Thank you for the additional information. It certainly confirms that the switch is booting multiple times a day and producing crashinfo files. There should be information in the crashing files that would identify the problem. Interpreting the files can be challenging. If you have a service contract on these switches the easy thing to do would be to open a case with Cisco and let a TAC engineer work through the analysis.
HTH
Rick
09-14-2018 06:10 AM
Do you have any logs or crashinfo logs in the flash?
If the reason is "Last reload reason: Power-on" the cause should be a power issue.
My suggestion is:
1) clean the fans, remove duster and chage the power point, the electrical socket
2) try to install a little UPS to check if the issue is on the power supplier
3) if the issue is not fixed replace the power supply
Regards.
09-14-2018 08:44 AM
It looks power issue. Make sure it has got proper power UPS .
09-14-2018 06:23 AM
09-14-2018 06:56 AM
We have tried moving it to a new UPS and it's pretty clean not really any dirt or dust in it.
The IOS is 15.2(4r)E3
We are using this to connect to our ISP, not nat just a /30 on one end and our subnet on the other end.
If we were to buy a ISR 4321 to do this would we be limited to the license that is on that 4321 as far as the throughput? We have a 300Mbps up and down connection. Typically we use 1921 routers for these deployments but those are getting long in the tooth.
Thank you
09-14-2018 03:57 PM - edited 09-14-2018 03:58 PM
@jkay18041 wrote:
The IOS is 15.2(4r)E3
This is not the IOS version, rather, this is the bootstrap version.
Post the complete output to the following commands:
09-19-2018 10:04 AM
Here is the IOS
System image file is "flash:/c3560cx-universalk9-mz.152-4.E2.bin"
I have 2 of these, both at different locations that reboot every 3 to 4 hours for no reason.
09-19-2018 10:21 AM
It would be nice if we could figure out what is causing this rebooting. So the request for logs is a very reasonable step. Also the request from Leo for the output of dir might show if there are crashing files which might have helpful content.
But your mention that you have two switches running this version of code and that both are exhibiting the rebooting issue suggests that it might be a code issue (perhaps a memory leak or something). It might be worth it to upgrade the switches to a different version of code.
HTH
Rick
09-19-2018 11:14 AM
Cisco IOS Software, C3560CX Software (C3560CX-UNIVERSALK9-M), Version 15.2(4)E2, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2016 by Cisco Systems, Inc.
Compiled Mon 27-Jun-16 09:08 by prod_rel_team
ROM: Bootstrap program is C3560CX boot loader
BOOTLDR: C3560CX Boot Loader (C3560CX-HBOOT-M) Version 15.2(4r)E3, RELEASE SOFTWARE (fc1)
SWITCH uptime is 23 minutes
System returned to ROM by power-on
System restarted at 12:52:29 Eastern Wed Sep 19 2018
System image file is "flash:/c3560cx-universalk9-mz.152-4.E2.bin"
Last reload reason: power-on
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.
License Level: ipbase
License Type: Default. No valid license found.
Next reload license Level: ipbase
cisco WS-C3560CX-8TC-S (APM86XXX) processor (revision H0) with 524288K bytes of memory.
Processor board ID FOC2052Y2
Last reset from power-on
1 Virtual Ethernet interface
12 Gigabit Ethernet interfaces
The password-recovery mechanism is enabled.
512K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address : 2C:86:D2:70:43:00
Motherboard assembly number : 73-100858-04
Power supply part number : 341-0208-03
Motherboard serial number : FOC20497K
Power supply serial number : LIT20452K
Model revision number : H0
Motherboard revision number : A0
Model number : WS-C3560CX-8TC-S
System serial number : FOC2052Y2
Top Assembly Part Number : 68-100566-01
Top Assembly Revision Number : A0
Version ID : V04
CLEI Code Number : CMM1P10DRB
Hardware Board Revision Number : 0x09
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 12 WS-C3560CX-8TC-S 15.2(4)E2 C3560CX-UNIVERSALK9-M
Configuration register is 0xF
Directory of flash:/
2 -rwx 21456896 Sep 28 2017 15:41:15 -05:00 c3560cx-universalk9-mz.152-4.E2.bin
59 -rwx 3096 Sep 19 2018 12:53:33 -05:00 multiple-fs
3 -rwx 17 Apr 7 2018 06:49:15 -05:00 smi_post_install.txt
4 -rwx 1918 Sep 17 2018 15:07:25 -05:00 private-config.text
5 drwx 4096 Sep 7 2018 08:51:40 -05:00 crashinfo_ext
56 -rwx 556 Sep 19 2018 12:53:28 -05:00 vlan.dat
58 -rwx 3591 Sep 17 2018 15:07:24 -05:00 config.text
122185728 bytes total (83224064 bytes free)
Is this what you are looking for?
Thank you for the help.
09-19-2018 11:27 AM
This is certainly a good start. The dir does show that there is a folder for crashinfo
5 drwx 4096 Sep 7 2018 08:51:40 -05:00 crashinfo_ext
Can you post the directory listing of the contents of this folder?
HTH
Rick
09-19-2018 11:47 AM
6 -rwx 366702 Sep 7 2018 08:51:40 -05:00 crashinfo_ext_1
7 -rwx 348539 Sep 7 2018 12:50:59 -05:00 crashinfo_ext_2
8 -rwx 342372 Sep 7 2018 18:50:17 -05:00 crashinfo_ext_3
9 -rwx 341613 Sep 8 2018 00:50:08 -05:00 crashinfo_ext_4
10 -rwx 322170 Sep 8 2018 06:49:44 -05:00 crashinfo_ext_5
11 -rwx 332738 Sep 8 2018 12:40:34 -05:00 crashinfo_ext_6
12 -rwx 341131 Sep 8 2018 18:50:26 -05:00 crashinfo_ext_7
13 -rwx 336734 Sep 9 2018 00:50:39 -05:00 crashinfo_ext_8
14 -rwx 350794 Sep 9 2018 06:50:27 -05:00 crashinfo_ext_9
15 -rwx 355405 Sep 9 2018 12:49:42 -05:00 crashinfo_ext_10
16 -rwx 322230 Sep 9 2018 18:49:56 -05:00 crashinfo_ext_11
17 -rwx 365818 Sep 10 2018 00:50:33 -05:00 crashinfo_ext_12
18 -rwx 331902 Sep 10 2018 06:49:55 -05:00 crashinfo_ext_13
19 -rwx 351945 Sep 10 2018 12:49:58 -05:00 crashinfo_ext_14
20 -rwx 316059 Sep 10 2018 18:50:28 -05:00 crashinfo_ext_15
21 -rwx 349038 Sep 11 2018 00:49:42 -05:00 crashinfo_ext_16
22 -rwx 330432 Sep 11 2018 06:50:04 -05:00 crashinfo_ext_17
23 -rwx 350825 Sep 11 2018 12:50:42 -05:00 crashinfo_ext_18
24 -rwx 346239 Sep 11 2018 18:48:49 -05:00 crashinfo_ext_19
25 -rwx 332219 Sep 12 2018 00:51:06 -05:00 crashinfo_ext_20
26 -rwx 334129 Sep 12 2018 06:49:43 -05:00 crashinfo_ext_21
27 -rwx 346674 Sep 12 2018 12:50:47 -05:00 crashinfo_ext_22
28 -rwx 345991 Sep 12 2018 18:51:07 -05:00 crashinfo_ext_23
29 -rwx 345924 Sep 13 2018 00:51:08 -05:00 crashinfo_ext_24
30 -rwx 316484 Sep 13 2018 06:50:25 -05:00 crashinfo_ext_25
31 -rwx 319059 Sep 13 2018 12:50:14 -05:00 crashinfo_ext_26
32 -rwx 338461 Sep 13 2018 18:49:46 -05:00 crashinfo_ext_27
33 -rwx 356052 Sep 14 2018 00:50:05 -05:00 crashinfo_ext_28
34 -rwx 377125 Sep 14 2018 06:50:03 -05:00 crashinfo_ext_29
35 -rwx 346929 Sep 14 2018 12:50:31 -05:00 crashinfo_ext_30
36 -rwx 313776 Sep 14 2018 18:50:13 -05:00 crashinfo_ext_31
37 -rwx 335927 Sep 15 2018 00:40:23 -05:00 crashinfo_ext_32
38 -rwx 359938 Sep 15 2018 06:50:17 -05:00 crashinfo_ext_33
39 -rwx 326189 Sep 15 2018 12:50:42 -05:00 crashinfo_ext_34
40 -rwx 325198 Sep 15 2018 18:51:13 -05:00 crashinfo_ext_35
41 -rwx 358143 Sep 16 2018 00:51:50 -05:00 crashinfo_ext_36
42 -rwx 353108 Sep 16 2018 06:50:49 -05:00 crashinfo_ext_37
43 -rwx 356872 Sep 16 2018 12:51:36 -05:00 crashinfo_ext_38
44 -rwx 338170 Sep 16 2018 18:51:21 -05:00 crashinfo_ext_39
45 -rwx 350764 Sep 17 2018 00:50:46 -05:00 crashinfo_ext_40
46 -rwx 346091 Sep 17 2018 06:49:48 -05:00 crashinfo_ext_41
47 -rwx 353885 Sep 17 2018 12:50:22 -05:00 crashinfo_ext_42
48 -rwx 368355 Sep 17 2018 18:49:45 -05:00 crashinfo_ext_43
49 -rwx 327869 Sep 18 2018 00:50:28 -05:00 crashinfo_ext_44
50 -rwx 329144 Sep 18 2018 06:50:52 -05:00 crashinfo_ext_45
51 -rwx 351616 Sep 18 2018 12:50:50 -05:00 crashinfo_ext_46
52 -rwx 346155 Sep 18 2018 18:50:19 -05:00 crashinfo_ext_47
53 -rwx 330357 Sep 19 2018 00:39:51 -05:00 crashinfo_ext_48
54 -rwx 357891 Sep 19 2018 06:50:09 -05:00 crashinfo_ext_49
55 -rwx 353499 Sep 19 2018 12:49:59 -05:00 crashinfo_ext_50
09-19-2018 12:10 PM
Thank you for the additional information. It certainly confirms that the switch is booting multiple times a day and producing crashinfo files. There should be information in the crashing files that would identify the problem. Interpreting the files can be challenging. If you have a service contract on these switches the easy thing to do would be to open a case with Cisco and let a TAC engineer work through the analysis.
HTH
Rick
09-19-2018 04:34 PM
09-19-2018 06:04 PM
09-19-2018 06:21 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide