Users Guide

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 Verify Software Images Before Installation

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:

1. Download Dell Networking OS software image le from the iSupport page to the local (FTP or TFTP) server. The published

hash for that le is displayed next to the software image le on the iSupport page.

2. Go on to the Dell Networking system and copy the software image to the ash drive, using the copy command.

3. Run the verify {md5 | sha256} [ ash://]img-le [hash-value] command. For example, verify sha256 ash://FTOS-

SE-9.5.0.0.bin

4. Compare the generated hash value to the expected hash value published on the iSupport page.

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, use the verify {md5 | sha256} [ ash://]img-le [hash-value] command in EXEC mode.

• md5: MD5 message-digest algorithm

• sha256: SHA256 Secure Hash Algorithm

• ash: (Optional) Species the ash drive. The default is to use the ash drive. You can just enter the image le name.

• hash-value: (Optional). Specify the relevant hash published on i-Support.

• img-le: Enter the name of the Dell Networking software image le to validate

Examples: Without Entering the Hash Value for Verication

Getting Started