7.4 Configuration loss or startup failure
If the device enters "miniboot" mode during startup, it indicates that the primary image is damaged. You can re upload the image through XMODEM or USB.
Regularly backup the configuration to the TFTP server (copy running config tftp) and enable configuration logging for audit rollback.
Software Upgrade Operation Specification
Upgrading AOS is a necessary step for expanding functionality (such as enabling Metro features) and fixing security vulnerabilities. The standard process is as follows:
Confirm the hardware compatibility between the current version (show version) and the target version.
Backup current configuration and image: copy running config, copy flash to external storage.
Upload new image: Place the. img file into the flash/working/directory via FTP/SFTP.
Specify the next boot image: boot system working.
Restart verification (reload) and observe whether the stack members are synchronously upgraded. If rollback is required, set boot system backup and restart.
Key reminder: In stacked scenarios, the backup members should be upgraded and switched to the primary use first, and then the original primary use should be upgraded to ensure uninterrupted business operations. Before upgrading, be sure to read the version release notes and pay attention to any configuration command changes.
Monitoring and daily inspection suggestions
Environmental monitoring: Check the device temperature (show temperature) and fan speed (show fan). The OS6450-48 model has 4 fans, and if any of them are abnormal, they should be replaced as soon as possible.
Log analysis: Configure the Syslog server, set the level to info, and focus on monitoring ERR and CRIT messages.
Performance baseline: Establish a normal traffic baseline using RMON and sFlow for quick comparison in case of anomalies.
