Users Guide

Using HTTP for File Transfers
Stating with Release 9.3(0.1), you can use HTTP to copy les or conguration details to a remote server. Use the copy source-le-
url http://host[:port]/le-path
command to transfer les to an external server.
Enter the following source-le-url keywords and information:
To copy a le from the internal FLASH, enter ash:// followed by the lename.
To copy the running conguration, enter the keyword running-cong.
To copy the startup conguration, enter the keyword startup-cong.
To copy a le on the external FLASH, enter usbash:// followed by the lename.
In the Dell Networking OS release 9.8(0.0), HTTP services are enhanced to support the VRF-aware functionality. If you want the
HTTP server to use a VRF table that is attached to an interface, congure that HTTP server to use a specic routing table. You can
use the ip http vrf command to inform the HTTP server to use a specic routing table. After you congure this setting, the
VRF table is used to look up the destination address.
NOTE: To enable HTTP to be VRF-aware, as a prerequisite you must rst dene the VRF.
You can specify either the management VRF or a nondefault VRF to congure the VRF awareness setting.
When you specify the management VRF, the copy operation that is used to transfer les to and from an HTTP server utilizes the
VRF table corresponding to the Management VRF to look up the destination. When you specify a nondefault VRF, the VRF table
corresponding to that nondefault VRF is used to look up the HTTP server.
However, these changes are backward-compatible and do not aect existing behavior; meaning, you can still use the ip http
source- interface command to communicate with a particular interface even if no VRF is congured on that interface
NOTE: If the HTTP service is not VRF-aware, then it uses the global routing table to perform the look-up.
To enable an HTTP client to look up the VRF table corresponding to either management VRF or any nondefault VRF, use the ip
http vrf
command in CONFIGURATION mode.
Congure an HTTP client with a VRF that is used to connect to the HTTP server.
CONFIGURATION MODE
Dell(conf)#ip http vrf {management | <vrf-name>}
Using Hashes to Validate Software Images
You can use the MD5 message-digest algorithm or SHA256 Secure Hash Algorithm to validate the software image on the ash
drive, after the image has been transferred to the system, but before the image has been installed. The validation calculates a hash
value of the downloaded image le on system’s ash drive, and, optionally, compares it to a Dell Networking published hash for that
le.
The MD5 or SHA256 hash provides a method of validating that you have downloaded the original software. Calculating the hash on
the local image le, and comparing the result to the hash published for that le on iSupport, provides a high level of condence that
the local copy is exactly the same as the published software image. This validation procedure, and the verify {md5 | sha256}
command to support it, can prevent the installation of corrupted or modied images.
The verify {md5 | sha256} command calculates and displays the hash of any le on the specied local ash drive. You can compare
the displayed hash against the appropriate hash published on i-Support. Optionally, the published hash can be included in the
verify {md5 | sha256} command, which will display whether it matches the calculated hash of the indicated le.
To validate a software image:
54
Getting Started