Reset Search
 

 

Article

Upgrading to MR2 management modules

« Go Back

Information

 
TitleUpgrading to MR2 management modules
Objective
  • Upgrading the management module in your router to an MR2 management module.
Environment
  • MLXe
  • MR2 Management Module
  • Software 5.2.00c and higher 
Procedure
WARNING:
The following scenarios are not supported and may result in damage to the MR2 management module and other hardware:

Installing the MR2 as a standby management module in a device running code prior to NetIron Release 5.2.00b is not supported
Current minimum code required for MR2 is 5.2.00c

Having both MR2 and MR module in the same device is NOT supported under any circumstance.

If the MR2 router no longer boots, please contact Brocade technical support.

To upgrade to MR2 management modules, perform the following steps:
  1. Perform a basic upgrade of your devices to NetIron Release 5.2.00b and above or your target path as documented in the appropriate chapter in the Multi-Service IronWare Software Upgrade Guide.
  2. Changes in on board storage form factors between MR and MR2 management modules require that you backup the configuration while upgrading. Use a TFTP server or SSH client to store the configuration.To back up the running or startup configurations:
    1. Using TFTP: To copy the startup configuration files from the device to a TFTP server, enter the following command:
      copy startup-config tftp ip-address filename
To copy the running configuration files from the device to an TFTP server, enter the following command:
copy running-config tftp ip-address filename
  1. Using SCP: To copy the running configuration file on a device to a file on the SCP-enabled host:
    C:\> scp userdevice-IpAddress :runConfig dst-file
    To copy the startup configuration file on the device to a file on the SCP-enabled client, enter the following command:
    C:> scp user@device-IpAddress dst-file:startConfig
 
  1. Remove the power supplies or power cords to power down the device and remove the MR management modules and unseat all line cards.For device specific instructions on removing existing management modules, refer to the appropriate chapter in this document for the device you are using (Brocade MLX-e Series Hardware Installation Guide). NOTE: You should label the network, serial, and power cords to ensure that they are reconnected correctly in Step 4 and Step 5.
  2. Install the MR2 management modules. For device specific instructions on installing management modules, refer to the appropriate chapter in the Brocade MLX-e Series Hardware Installation Guide. Once the MR2 management modules are correctly installed in the switch, reconnect to the serial and network connections.
  3. Power the switch back on by installing the power supplies or power cords to power on the device and do not reseat the line cards yet.
  4. Once the device has come up, connect to the serial port and enter the following commands to assign a temporary IP address to interface m 1, and enable the interface:
    enable
    configure terminal
    interface m 1
    ip addresss 10.10.10.2/24
    enable
    exit
     
    ip route 0.0.0.0/0 10.10.10.1
    exit
    You may also need to assign a static route. You should be able to ping the IP address of the TFTP server or SSH client.
  5. Now check the version code that is on the new MR2 module with show version. Determine at this point if you will need upgrading or downgrading.
  6. Start upgrade process (go thru the software upgrade and review manifest file for the upgrade). The files will check all the interface module and management module and install the appropriate software compatible with the Line card modules and Management modules.
  7. Copy the startup or running configuration stored from the SSH client or TFTP server back to the device:
    1. Using TFTP from the privileged exec mode of the console:
      copy tftp startup-config ip-addressfilename
      NOTE: SSH is disabled by default, you will need to configure and enable it before using SCP. • ‐ Using SCP:
    2. Using SCP:
      C:> scp filename user device-ipaddress :config:start
  8. Issue one of the following commands from the Privileged exec mode of the console to reload the device: NOTE: You may wish to check that all interface modules are in the up state, and resolve any incompatible versions found before reloading the device with show interface brief
    1. To load the primary code flash enter the reload command:
      reload
      The reload command boots from the default boot source, which is the primary code flash.
    2. To load the secondary code flash, enter the boot system flash secondary command.
      boot system flash [primary

After the device has reloaded, verify that everything is working in order. Check the status and health of the MLXe using following commands:
Show chassis
Show version
Show module
Show config
Show interface brief

 
Additional notes
There is one more image i.e Boot Image which will not be downloaded using Manifest file. Reason being in the Release notes of NI 5.8.00F it is written that there is no need to upgrade Boot image if the previous running image is 5.7.00. If it was 5.6.00 or lower we need to upgrade Boot image too.

The command which we will be running to upgrade system using manifest file is:
copy tftp system [all-images] <server-ip-address> manifest <File name> [lp-sec | mp-sec | secondary]

 

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255