User Manual

Table Of Contents
Perform Maintenance Tasks
347
Insight Managed 28-Port and 52-Port Gigabit Ethernet Smart Cloud Switches
13. If you selected SFTP or SCP from the Transfer Mode menu, specify the following
credentials:
User Name. The user name to log in the server.
Password. The password to log in the server.
14. Select the Start File Transfer check box.
15. Click the Apply button.
The file transfer begins.
The page displays information about the progress of the file transfer. The page refreshes
automatically when the file transfer completes (or if it fails).
To activate a software image that you downloaded to the switch, see Manage Software
Images on page 350.
Upgrade the Software or Download a File to the Switch Using
HTTP
You can upgrade software and download the image file, the configuration files, and SSL files
to the switch through an HTTP session by using your web browser.
To upgrade the software or download a file to the switch using HTTP:
1. Connect your computer to the same network as the switch.
You can use a WiFi or wired connection to connect your computer to the network, or
connect directly to a switch that is off-network using an Ethernet cable.
2. Launch a web browser.
3. In the address field of your web browser, enter the IP address of the switch.
If you do not know the IP address of the switch, see Access the Switch on page 13.
The login window opens.
4. Enter the switch’s password in the password field.
The default password is password. If you added the switch to a network on the Insight
app before and you did not yet change the password through the local browser interface,
enter your Insight network password.
The System Information page displays.
5. Select Maintenance > Upgrade > HTTP File Upgrade.
The HTTP File Upgrade page displays.
6. From the File Type menu, select the type of file:
Software. The system software image, which is saved in one of two flash sectors
called images (image1 and image2). The active image stores the active copy, the
other image stores a second copy. The device boots and runs from the active image.
If the active image is corrupted, the system automatically boots from the nonactive