(Originally posted in the 1500 subforum, deleted and reposted here. Apologies for the mistake.)
Greetings, I have an extremely serious problem with a 6 Switch DGS-1510-52XMP stack. I have no longer web access and CLI commands, although issued, are ineffective. The file system shows 0 bytes free and doesn't accept delete/copy commands. I am stuck with the present configuration that, although working, is unchangeable. The network is rather large and complex (hundreds of devices, 3 VLANs, 1 wireless ethernet bridge, 2 internet connections, 4 rack cabinets connected via 10 Gb/sec fiber), so I need to gain access back in a reasonable time. This happens at boot:
Boot Procedure V1.00.016
-------------------------------------------------------------------------------
Power On Self Test ........................................ 100 %
MAC Address : 78-32-1B-B4-B0-60
H/W Version : A1
Please Wait, Loading V1.70.B023 Runtime Image ............. 100 %
UART init ................................................. 100 %
Starting runtime image
Caution: Failed to initialize web server. The web service is unavailable. The web files are perhaps damaged. Please re-download the firmware.543
Device Discovery .......................................... /
I isolated and reset the second switch of the stack. Using the reset switch, a pressure and immediate release reboots the switch. Still, there's no change at all.
Pressure between 1 and 10 seconds: the switch blinks all leds yellow at the 5 second mark, on the console (via serial adapter) I can see this after this 7-8 second pressure:
Clear running configuration start.
On the master stack, no reboot really happens. The configuration is cleared. INo real change can be made to the file system (still unable to delete), but at that point I didn't want to risk losing the highest priority (and most important, connectivity wise) stack with a working configuration, so I rebooted without trying to copy the reset running configuration to the startup configuration.
This happened after a firmware update, but probably the image is corrupted or partial.
I tried changing via CLI the boot image, but no variation appears in the running configuration, but this happens:
Customer#dir
Directory of /c:
1 -rw 9791996 Jan 01 2000 00:35:54 DGS-1510_Run_1_60_012.had
2 -rw 9966832 Jan 01 2000 00:04:50 runtime.had
3 -rw 9751496 Aug 06 2021 07:18:13 DGS-1510_1_70_B023.had
4 -rw 15922 Aug 06 2021 07:28:37 config.cfg
5 d-- 0 Jan 01 2019 00:00:02 system
30656000 bytes total (0 bytes free)
Customer#conf t
Customer(config)#boot image DGS-1510_Run_1_60_012.had
Customer(config)#exit
Customer#copy running-config startup-config
Destination filename startup-config? [y/n]: y
Saving all configurations to NV-RAM.......... 0 %
ERROR: Not enough space.
No change ensues. Trying to manually delete a firmware version yields this result:
Customer#dir
Directory of /c:
1 -rw 9791996 Jan 01 2000 00:35:54 DGS-1510_Run_1_60_012.had
2 -rw 9966832 Jan 01 2000 00:04:50 runtime.had
3 -rw 9751496 Aug 06 2021 07:18:13 DGS-1510_1_70_B023.had
4 -rw 15922 Aug 06 2021 07:28:37 config.cfg
5 d-- 0 Jan 01 2019 00:00:02 system
30656000 bytes total (0 bytes free)
Customer#delete runtime.had
Delete runtime.had? (y/n) [n] y
Failure.
Customer#dir
Directory of /c:
1 -rw 9791996 Jan 01 2000 00:35:54 DGS-1510_Run_1_60_012.had
2 -rw 9751496 Aug 06 2021 07:18:13 DGS-1510_1_70_B023.had
3 -rw 15922 Aug 06 2021 07:28:37 config.cfg
4 d-- 0 Jan 01 2019 00:00:02 system
30656000 bytes total (0 bytes free)
Customer#
The file is no longer visible from the command dir, but it is still there. A reboot followed by the dir command would show the file runtime.had despite the previous delete request.
The running config cannot be modified too, commands are accepted but configuration change (or file configuration change) doesn't occur. Everything seems read-only.
The update procedure was done via web, the web server was available for half an hour, then logging in became impossibile. The update procedure went presumably well since no error was reported via WEB and everything seemed correct, although I found entries indicating the contrary on the log:
#5549 2019-01-01 00:01:56 CRIT(2) Unit 2, System started up
#5548 2019-01-01 00:01:56 CRIT(2) Unit 2, System warm start
#5547 2021-08-06 07:16:12 WARN(4) Unit 6, Firmware upgraded by WEB unsuccessfully (Username: admin, IP: 192.168.0.95, MAC: 6C-4B-90-AA-37-5B, Server IP: 192.168.0.95, File Name: DGS-1510_1_70_B023.had)
#5546 2021-08-06 07:16:12 WARN(4) Unit 4, Firmware upgraded by WEB unsuccessfully (Username: admin, IP: 192.168.0.95, MAC: 6C-4B-90-AA-37-5B, Server IP: 192.168.0.95, File Name: DGS-1510_1_70_B023.had)
#5545 2021-08-06 07:16:12 WARN(4) Unit 1, Firmware upgraded by WEB unsuccessfully (Username: admin, IP: 192.168.0.95, MAC: 6C-4B-90-AA-37-5B, Server IP: 192.168.0.95, File Name: DGS-1510_1_70_B023.had)
#5544 2021-08-06 07:16:12 WARN(4) Unit 5, Firmware upgraded by WEB unsuccessfully (Username: admin, IP: 192.168.0.95, MAC: 6C-4B-90-AA-37-5B, Server IP: 192.168.0.95, File Name: DGS-1510_1_70_B023.had)
#5543 2021-08-06 07:16:12 WARN(4) Unit 3, Firmware upgraded by WEB unsuccessfully (Username: admin, IP: 192.168.0.95, MAC: 6C-4B-90-AA-37-5B, Server IP: 192.168.0.95, File Name: DGS-1510_1_70_B023.had)
#5542 2021-08-06 07:16:12 WARN(4) Unit 2, Firmware upgraded by WEB unsuccessfully (Username: admin, IP: 192.168.0.95, MAC: 6C-4B-90-AA-37-5B, Server IP: 192.168.0.95, File Name: DGS-1510_1_70_B023.had)
#5541 2021-08-06 07:13:27 WARN(4) Unit 3, Firmware upgraded by WEB unsuccessfully (Username: admin, IP: 192.168.0.95, MAC: 6C-4B-90-AA-37-5B, Server IP: 192.168.0.95, File Name: DGS-1510_Run_1_70_B023(0407112009).had)
#5540 2021-08-06 07:13:27 WARN(4) Unit 4, Firmware upgraded by WEB unsuccessfully (Username: admin, IP: 192.168.0.95, MAC: 6C-4B-90-AA-37-5B, Server IP: 192.168.0.95, File Name: DGS-1510_Run_1_70_B023(0407112009).had)
#5539 2021-08-06 07:13:26 WARN(4) Unit 1, Firmware upgraded by WEB unsuccessfully (Username: admin, IP: 192.168.0.95, MAC: 6C-4B-90-AA-37-5B, Server IP: 192.168.0.95, File Name: DGS-1510_Run_1_70_B023(0407112009).had)
#5538 2021-08-06 07:13:26 WARN(4) Unit 6, Firmware upgraded by WEB unsuccessfully (Username: admin, IP: 192.168.0.95, MAC: 6C-4B-90-AA-37-5B, Server IP: 192.168.0.95, File Name: DGS-1510_Run_1_70_B023(0407112009).had)
#5537 2021-08-06 07:13:26 WARN(4) Unit 5, Firmware upgraded by WEB unsuccessfully (Username: admin, IP: 192.168.0.95, MAC: 6C-4B-90-AA-37-5B, Server IP: 192.168.0.95, File Name: DGS-1510_Run_1_70_B023(0407112009).had)
#5536 2021-08-06 07:13:26 WARN(4) Unit 2, Firmware upgraded by WEB unsuccessfully (Username: admin, IP: 192.168.0.95, MAC: 6C-4B-90-AA-37-5B, Server IP: 192.168.0.95, File Name: DGS-1510_Run_1_70_B023(0407112009).had)
#5535 2021-07-29 12:14:58 WARN(4) ASV: Port eth1/0/10 Half duplex detected
At this point, there's nothing more I can try. I need a hard reset procedure that can be done via CLI/Serial to apply, after that, the configuration backup I saved before upgrading in order to restore the switch stack, or access to the file system of the switches in order to gain control of the machine and boot a good firmware. Any advice or help in resetting the switches (one by one would be preferrable in order not to disrupt the network services, which are currently working) and bringing them back to normal management abilities would be appreciated.
Author
Topic: Web access not working, CLI commands ineffective after firmware update (Read 6215 times)