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
234 Brocade MLX Series and Brocade NetIron XMR Installation Guide
53-1004195-03
Managing interface modules
•
The slot-number parameter specifies the slot number that contains the interface module to which the immediate synchronization
applies. You can specify 1 – 4 for 4-slot devices, 1 – 8 for 8-slot devices, 1 – 16 for 16-slot devices, or 1 – 32 for 32-slot
devices.
Specifying an immediate shutdown
The management module takes approximately 16-20 seconds to shutdown all interface modules in a device after a reload is issued.
During this time, the interface module continues sending packets. Enter the lp fast-powerdown command to immediately shut down all
interface modules in a device after a reload is issued.
Brocade(config)# lp fast-powerdown
Syntax: [no] lp fast-powerdown
If you do not enter this command, by default, the interface module continues to forward packets for an extended time after the router is
reloaded.
NOTE
You do not need to change the state of the interface module, or synchronize this shutdown with the standby management module.
Changing the boot source
By default, the interface modules boot from the primary image located in flash memory. You can change the boot source of one or all
interface modules to one of the following sources:
•
Management module
-
auxiliary flash card in slot 1 or 2
-
Primary or secondary image in the management module flash memory
•
Interface module
-
Secondary image in interface module flash memory
•
TFTP server
You can also specify an interactive boot, which allows you to enter a separate command after the interface module comes up. The
command specifies the source from which one or all interface modules should boot.
When changing the boot source for one or all interface modules, you can specify one of the following:
•
An immediate boot for one interface module from a specified source
•
An automatic boot for one or all interface modules from a specified source starting with the next software reload or system reset
and each reload or reset after that
The CLI command for specifying an immediate boot for one interface module is the same as that for specifying an automatic boot for one
or all modules. The only difference is the CLI level from which you execute the command. You must specify the command for an
immediate boot in the Privileged EXEC level and the command for an automatic boot in the global CONFIG level.
The following sections explain how to specify an immediate boot and an automatic boot.
Specifying an immediate boot
You can specify an immediate boot for one interface module from a specified source by entering the lp boot system command in the
Privileged EXEC level. The entered command will override the default or configured boot source one time only.
Specifying an immediate boot from the auxiliary flash slots on the management module
To specify an immediate boot for the interface module installed in slot 1 from the auxiliary flash slot on the management module, enter
the lp boot system command at the Privileged EXEC level of the CLI.