Installation Guide
Table Of Contents
- Contents
- About this Document
- Product Overview
- Installing a Brocade MLX Router
- Installation precautions
- Installing 2x100GbE interface modules in Brocade MLX routers
- Installing a Brocade MLX-4 router
- Installing a Brocade MLX-8 router
- Installing a Brocade MLX-16 router
- Installing a Brocade MLX-32 router
- Installing a Brocade MLX-32 router
- Preparing the installation site
- Brocade MLX-32 router shipping carton contents
- Unpacking your Brocade MLX-32 router
- Installing a Brocade MLX-32 router in a rack
- Installing Brocade MLX-32 router modules
- Brocade MLX-32 cable management
- Accessing modules for service
- Installing power supplies in a Brocade MLX-32 router
- Connecting AC power
- Connecting DC power
- Removing Brocade MLX-32 router DC power supplies
- Final steps
- Attaching a management station
- Activating the power source
- Verifying proper operation
- Installing a NetIron XMR Router
- Installation precautions
- Installing 2x100GbE interface modules in NetIron XMR routers
- Installing a NetIron XMR 4000 router
- Installing a NetIron XMR 8000 router
- Installing a NetIron XMR 16000 router
- Installing a NetIron XMR 32000 router
- Preparing the installation site
- Unpacking a NetIron XMR 32000 router
- Installing a NetIron XMR 32000 router in a rack
- Installing NetIron XMR 32000 modules
- NetIron XMR 32000 cable management
- Accessing modules for service
- Installing NetIron XMR 32000 router power supplies
- Removing NetIron XMR 32000 router DC power supplies
- Final steps
- Attaching a management station
- Activating the power source
- Verifying proper operation
- Using Brocade Structured Cabling Components
- Cable cinch overview
- mRJ21 procedures
- RJ45 procedures
- Cable cinch with one group of RJ45 cables
- Cable cinch with two groups of RJ45 cables
- Cable cinch with three groups of RJ45 cables
- Cable cinch with four groups of RJ45 cables
- Cable cinch with five groups of RJ45 cables
- Cable cinch with six groups of RJ45 cables
- Cable cinch with seven groups of RJ45 cables
- Cable cinch with eight groups of RJ45 cables
- Connecting a Router to a Network Device
- Managing Routers and Modules
- Managing the device
- Enabling and disabling a DC Power Source
- Disabling and re-enabling power to interface modules
- Monitoring I2C failures on management modules
- Displaying device status and temperature readings
- Displaying the Syslog configuration and static and dynamic buffers
- MP Presence from LP Detection (Headless Router Operation)
- Rolling Reboot
- Line Module Configuration Deletion in Interactive Boot Mode
- Managing switch fabric modules
- Managing the cooling system
- Managing interface modules
- Monitoring Link Status
- Using alarms to collect and monitor device status
- Displaying MR2 management module memory usage
- Enabling and disabling management module CPU usage calculations
- Displaying management module CPU usage
- Removing MAC address entries
- Simplified Upgrade
- Managing the device
- Maintenance and Field Replacement
- Hardware Specifications
- Regulatory Statements
- Caution and Danger Notices
Brocade MLX Series and Brocade NetIron XMR Installation Guide 249
53-1004195-03
Simplified Upgrade
6) Installed /XMR-MLX/Application/InterfaceModule/xmlp05600b296.bin to LP Primar
y on all LP slots
7) Skipped LP FPGA Bundled, same version exists.
8) Installed /XMR-MLX/FPGA/ManagementModule/mbridge_05600b296.xsvf to FPGA MBRID
GE
Checking for coherence...
Done.
Option to Ignore the Version
By default, the upgrade operation will perform a version check. An optional parameter to ignore the version field will be available in the CLI
command as well as SNMP MIB.
The user may choose to perform a forced upgrade.
Similarly, if the specified manifest file does not have a version field, it will perform a forced upgrade for backward compatibility.
Supported Images
The version comparison is done for the following images:
•
Interface Module FPGA (LP FPGA)
•
Management Module FPGA (MBRIDGE and MBRIDGE-32)
NOTE
Simplified Upgrade (single-command) must be performed before LP Auto-Upgrade can be configured. The later one uses the
manifest file that the former one downloaded in the system flash.
Single-Command Package Upgrade
The CLI command is modified to have an optional parameter to ignore or bypass version checking.
Full syntax (using a TFTP server as the source):
NetIron# copy tftp system [all-images] <server-ip-address>
manifest <File name> [lp-sec | mp-sec | secondary]
[skip-version-check]
Full syntax (using a removable storage device as the source):
NetIron# copy <slot1 | slot2> system [all-images]
manifest <File name> [lp-sec | mp-sec | secondary]
[skip-version-check]
Interface Module Auto-Upgrade
NOTE
Interface Module Auto-Upgrade does not support LP Auto-Upgrade, which allows the system to automatically upgrade the Boot
and FPGA images of an inserted interface module.
In a full-system upgrade where an external set of images (or, release package) is to be applied to the system, it makes sense to perform a
version comparison between what is currently running in the system and the release package (while LP Auto-Upgrade compares the
image version in LP and that of the system).