06-12-2015 09:01 AM
Hi, I'm having an issue with this switch rebooting - around once per day it seems.
The log is pasted below - note, i'm using an LTSP server to PXE boot Thin Clients on the network. I'm not sure if this is causing the reboot as the switch is trying to update from it .. can this be disabled?
2147462205 | 2015-Jun-12 16:39:22 | Informational | %INIT-I-Startup: Cold Startup |
2147462331 | 2015-Jun-12 16:38:52 | Warning | %COPY-W-TRAP: The copy operation has failed, aggregated (1) |
2147462487 | 2015-Jun-12 16:38:48 | Alert | %TFTP-A-TftpTxERROR: An error message was sent: 0 <Closed by application>, aggregated (1) |
2147462688 | 2015-Jun-12 16:38:48 | Informational | %COPY-I-FILECPY: Files Copy - source URL tftp://10.5.5.250/ltsp/i386/pxelinux.0 destination URL flash://startup-config, aggregated (1) |
2147462798 | 2015-Jun-12 16:38:22 | Warning | %COPY-W-TRAP: The copy operation has failed |
2147462938 | 2015-Jun-12 16:38:19 | Alert | %TFTP-A-TftpTxERROR: An error message was sent: 0 <Closed by application> |
2147463123 | 2015-Jun-12 16:38:19 | Informational | %COPY-I-FILECPY: Files Copy - source URL tftp://10.5.5.250/ltsp/i386/pxelinux.0 destination URL flash://startup-config |
2147463225 | 2015-Jun-12 16:38:01 | Notice | %SYSLOG-N-LOGGING: Logging started. |
2147463435 | 2015-Jun-12 16:37:59 | Warning | %COPY-W-TRAP: The copy operation has failed |
2147463575 | 2015-Jun-12 16:37:56 | Alert | %TFTP-A-TftpTxERROR: An error message was sent: 0 <Closed by application> |
2147463760 | 2015-Jun-12 16:37:55 | Informational | %COPY-I-FILECPY: Files Copy - source URL tftp://10.5.5.250/ltsp/i386/pxelinux.0 destination URL flash://startup-config |
2147463873 | 2015-Jun-12 16:37:54 | Warning | %STP-W-PORTSTATUS: fa10: STP status Forwarding |
2147463986 | 2015-Jun-12 16:37:53 | Warning | %STP-W-PORTSTATUS: fa11: STP status Forwarding |
2147464099 | 2015-Jun-12 16:37:53 | Warning | %STP-W-PORTSTATUS: fa12: STP status Forwarding |
2147464212 | 2015-Jun-12 16:37:52 | Warning | %STP-W-PORTSTATUS: fa21: STP status Forwarding |
Solved! Go to Solution.
06-15-2015 09:40 AM
Which way do you use for assigning management IP for switch? It is DHCP or statically assigned?
06-15-2015 09:40 AM
Which way do you use for assigning management IP for switch? It is DHCP or statically assigned?
06-16-2015 02:48 AM
Hi and thanks for the reply.
by dhcp but it has a static mapping.
i disabled auto configuration settings and i think the issue has stopped.
06-16-2015 04:16 AM
Yes, that was I trying to point with disabling DHCP. Normally switches should have manual IP assignment without relaying on DHCP. DHCP is really useful for end-users or maybe printers (with static mapping). But for such core devices like switches, routers or servers I would always prefer manual IP assignment.
So with disabling DHCP IP configuration seems your issue is gone... . For me it looks like bug in firmware and probably it could be subject to report to Cisco in order to get it fixed as it have impact to device stability.
06-20-2015 11:33 AM
made your answer correct.. been working flawless every since i disable it.. i've also set static ip now as well.
Thanks
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