Data Center (SLX)

Roy Noh posted 11-25-2018 23:16

If you have a valid account on extreme portal(https://extremeportal.force.com/), kindly do search proper NOS versions for you to download them.

Current target release of Network OS v4.1 is v4.1.3d but since the NOS you're using is v2.1.1 so there are migration paths for you to follow.

Recommended Migration Paths for Extreme Network OS v4.1.x
Switches operating with earlier versions of Extreme Network OS, including Extreme Network OS v2.1.X, should first be upgraded to Network OS v3.0.1b, then to 4.0.1 and then to Network OS v4.1.x

Steffen Schwade posted 11-26-2018 06:05

hello , i have this versions nos3.0.1 / nos3.0.1a / nos3.0.1c

John Cox posted 11-26-2018 12:41

Craig,

If you have never configured or had the switch in production, you can install any version of code (provided the hardware supports it). You just do it as a new install. It is when the switch has a configuration on it, Extreme (Brocade) forced an upgrade path where you could not skip major NOS releases when upgrading between versions. By hitting each major version any changes in code will upgrade the configuration to support those changes in the upgrade process. I have gone from 3.x to 7.x when configuring a spare switch for production with no issues, but there was no config on the switch at the time.

Just use the firmware install command. See any one of the command reference guides for the specifics, the command had not changed since 2.1.1.

NOTE: Description This command cleans the existing firmware on the system before installing the new firmware. All

configurations in the system is completely lost.

firmware install

Installs new software but deletes all configuration in the system.

CAUTION

Do not use this command unless instructed by Brocade Technical Support.

synopsis firmware install {ftp|scp} host host_ip_address user username password password

ddirectory directory [file file_name] [vcs-mode {0 |1 | 2} ] [vcs-id vcs_id] [rbridge-id rbridge ID]

Operands ftp Specifies FTP as the protocol used to install the firmware.

scp Specifies SCP as the protocol used to install the firmware.

host Specifies the host by DNS name or IP address.

host_ip_address Specifies the host IP address. IPv4 and IPv6 addresses are supported.

user username Specifies the user login name for the host.

password password Specifies the account password.

directory directory Specifies a fully qualified path to the directory where the firmware is

located.

file filename Specifies the firmware .plist file. This parameter is optional; if unspecified,

the default file, release.plist, is used.

[vcs-mode {0 |1 | 2} Specifies the VCS mode for the switch when the new

firmware has been installed. If not set, the platform-dependent default VCS

mode is used. Values you can select are: 0 (fabric cluster mode), 1 (logical

chassis cluster mode), or 2 (standalone mode).

vcs-id vcs_id Specifies the new VCS ID when the new firmware has been installed. If not

set, the platform-dependent default VCS ID is used. Range is 1 to 8192.

rbridge-id rbridge ID Specifies the new Rbridge ID when the new firmware has been installed. If

not set, the platform-dependent default Rbridge ID isused. Range is 1 to

239.

Defaults None

Command Modes Privileged EXEC mode

Description This command cleans the existing firmware on the system before installing the new firmware. All

configurations in the system is completely lost.

314 Network OS Command Reference

53-1003226-01

2 firmware install

Usage Guidelines • In a dual-MM system, after firmware install is completed on both MMs, reboot them at the

same time. Otherwise, the MMs may run into configuration mismatch issue.

• If vcs-id or rbridge-id are specified, vcs-mode cannot be set to 2 (standalone).

• On the Brocade 8770, 6740, 6740T, and 6740T-1G, vcs-mode cannot be set to 2

(standalone).

• If you want to change vcs-mode from standalone to either fabric cluster mode or logical

chassis cluster mode, you must use both the vcs-id and rbridge-id options with this command.

• If you specify at least one of the vcs-mode, vcs-id or rbridge-id parameters, then the remaining

parameters will get their values from the existing configuration — unless you also specify their

values in the command line.

Examples To install new firmware, delete all existing configurations, and to specifiy the vcs mode, vcs ID and

RBridge ID you want the switch to come up in:

switch# firmware install scp host 10.70.4.109 user fvt pass pray4green directory

/buildsjc/sre/SQA/nos/nos4.1.0/nos4.1.0_bld25 vcs-mode 1 vcs-id 6 rbridgeid 10

See Also None

vandi posted 01-11-2021 05:13

I am in a similar station where I’d like to go from 2.1.1 to 4.1.3d, but do not have access to 3.0/4.0 firmware files.

I do not see and option for “firmware install”  I do not have a configuration on my switches at this time, so I’m okay with any wipes, but need to protect the POD licenses on my VDX6720s.

any way to “expose” this “firmware install” option?

Russ posted 10-20-2021 18:11

Hello Steffen Schwade,

Could you share your nos versions nos3.0.1 / nos3.0.1a / nos3.0.1c if you still have them?