Installation Guide
Table Of Contents
- Brocade NetIron MLXe Series Hardware Installation Guide
- Preface
- About This Document
- Product Overview
- Brocade router overview
- Router applications
- Hardware features
- Router modules
- Management modules
- Interface modules
- 2x100GbE CFP2 optics based high density module
- PBIF Recovery
- 2x100GbE CFP2 P2010 specifications
- 2x100GbE CFP2 DDR3 SDRAM memory specifications
- BR-MLX-10GX20-X2 and BR-MLX-100GX2-CFP2-X2 Router Software
- BR-MLX-10GX20-X2 and BR-MLX-100GX2-CFP2-X2 scalability for IPv4 and IPv6 routes
- 2x100G XPP ILKN monitoring
- CPU threshold monitoring
- MLXe BR-MLX-10Gx4-M IPsec and IKEv2
- Encryption and Decryption of IPv4 Unicast Data and Control Packets
- IKEv2 Authentication
- IPsec and IKEv2 configuration
- Configuring Global IKEv2 Options
- Configuring the IKEv2 Proposal
- Configuring the IKEv2 Policy
- Configuring the IKEv2 Profile
- Configuring the IKEv2 authentication proposal
- Configuring the IPsec Proposal
- Configuring the IPsec Profile
- IKEv2 Show Commands
- IKEv2 Clear Commands
- MLX-10GX4-IPSEC-M Forwarding
- 2x100G XPP ILKN monitoring
- 10Gx24-port interface module
- MLX 24-port 10Gbps (BR-MLX-10Gx24-DM) Interface Modules
- 8x10GE-X interface modules
- Gen-1 10Gx2 and 10Gx4 Ethernet interface modules
- BR-MLX-10GX4-X and BR-MLX-10Gx4-X-ML interface module LEDs
- Gen-1.1 4-port 10 Gbps Ethernet interface modules
- 8-port 10 Gbps M and D interface modules
- 24-port 1 Gbps Ethernet copper RJ-45 interface module
- 24-port 1 Gbps fiber interface module
- 20-port 100/1000 Ethernet interface module
- 20-port 10/100/1000 Ethernet interface module
- NI-MLX-1Gx48-T-A interface module
- BR-MLX-40Gx4-M 4-port 40GbE module
- Auto-tuning links
- Forward Error Correction mode
- Switch fabric modules
- High-speed switch fabric modules
- CFP2 to QSFP28 conversion module
- Power supplies
- Rack mounting brackets
- Cooling system for Brocade MLXe Series routers
- NIBI-16-FAN-EXH-A high-speed fan assemblies
- Rack mount kit
- Supported software features
- Installing a Brocade MLXe Router
- Pre-Installation notice for the Brocade MLXe chassis bundles
- Installation precautions
- Installing 2x100GbE CFP2 interface modules in Brocade MLXe Series routers
- Installing BR-MLX-10Gx24-DM interface modules in Brocade MLXe Series routers
- Installing a Brocade MLXe Series-4 router
- Installing a Brocade MLXe Series-8 router
- Installing a Brocade MLXe Series-16 router
- Mounting Brocade MLXe Series-4, -8, or -16 routers in a 4-post EIA rack
- Installing a Brocade MLXe Series-32 router
- Preparing the installation site
- Brocade MLXe Series-32 router shipping carton contents
- Unpacking your Brocade MLXe Series-32 router
- Installing a Brocade MLXe Series-32 router in an EIA rack
- Installing modules in the Brocade MLXe Series-32 router
- Brocade MLXe Series-32 cable management
- Accessing modules for service
- Installing power supplies in a Brocade MLXe Series-32 router
- Connecting AC power
- Connecting DC power
- Removing Brocade MLXe Series-32 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
- RJ-45 procedures
- Cable cinch with one group of RJ-45 cables
- Cable cinch with two groups of RJ-45 cables
- Cable cinch with three groups of RJ-45 cables
- Cable cinch with four groups of RJ-45 cables
- Cable cinch with five groups of RJ-45 cables
- Cable cinch with six groups of RJ-45 cables
- Cable cinch with seven groups of RJ-45 cables
- Cable cinch with eight groups of RJ-45 cables
- Connecting a Router to a Network Device
- Managing Routers and Modules
- Managing the device
- 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
- Router Headless State by MP Presence from LP
- Rolling Reboot
- Line Module Configuration Deletion in Interactive Boot Mode
- Managing switch fabric modules
- Managing the cooling system
- Managing interface modules
- Configuring interface module boot parameters
- Synchronizing the software image between management modules and interface modules
- Changing the boot source
- Specifying an immediate boot
- Specifying an immediate boot from the auxiliary flash slots on the management module
- Specifying an immediate boot from management module flash memory
- Specifying an immediate boot from flash memory on the interface module
- Specifying an immediate boot from a TFTP server
- Specifying an immediate interactive boot
- Configuring an automatic boot
- Configuring an automatic boot from the auxiliary flash slot on the management module
- Configuring an automatic boot from flash memory on the management module
- Configuring an automatic boot from flash memory on the interface module
- Configuring an automatic boot from a TFTP server
- Configuring an automatic interactive boot
- Changing priority of slots for interface modules
- Disabling and re-enabling power to interface modules
- Configuring interface module boot parameters
- Monitoring Link Status
- Traffic Manager XPP link monitoring
- 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
- IPv6 ND Proxy
- DRBG Health Test on IPsec LP
- Managing the device
- Maintenance and Field Replacement
- Maintenance and field replacement overview
- Hardware maintenance schedule
- Replacing a management module
- Replacing an interface module
- Replacing a switch fabric module
- Replacing a fiber-optic transceiver
- Replacing a power supply
- Replacing fan assemblies
- Hardware Specifications
- Brocade MLXe Chassis Bundles
- Regulatory Statements
- Caution and Danger Notices
history log stating that the condition has been removed. If the temperature increases into shutdown range, a critical level alarm is
reported and logged in the alarm logs.
Optics
Alarms and warnings are monitored only for optic devices that support optical monitoring. If optical monitoring is disabled, then no
alarms are generated.
If an optic is removed or not present, a major alarm is reported and logged and any existing alarms are cleared from the current alarm
log.
NOTE
Alarms are not generated for optic device insertion.
Switch fabric element
If a switch fabric element cannot be accessed, a major alarm is reported and logged.
Chassis fans, power supplies, and optics
If there is an indication that a single fan has failed, a major alarm is reported and logged on the tray. If an incompatible fan tray is
detected, a major alarm is reported and logged on the tray. When a fan tray is removed, any existing alarms are cleared and a major
alarm is reported and logged on the tray.
If a power supply is installed but powered down, a minor alarm is reported and logged. If a power supply is installed incorrectly, a major
alarm is reported and logged. If a power supply is not present, a major alarm is reported and logged.
Clearing the alarm history log
Use the clear alarm command to remove some or all of the current alarms. Once the alarm is cleared, it is removed from the current
alarm database and is no longer available even though the condition might still exist. The alarm is kept in the history log.
If you clear all alarms, a single entry is added to the history that indicates all alarms have been cleared.
To clear all alarms from the alarm logs, enter the following command:
device# clear alarm all
For example, if you want to clear all alarms from the alarm logs on a specific optic in slot 9 of the interface module in slot 1, enter the
following command:
device# clear alarm lp 1 optic 9
Disabling SNMP trap generation and logging
With the introduction of the alarm feature, you may want to disable some SNMP trap generation and logging to save space.
To disable SNMP fan change-trap generation, enter the following command:
device(config)# no snmp-server enable traps fan-speed-change
To disable Syslog fan-speed-change logging, enter the following command:
device(config)# no logging enable fan-speed-change
For additional information on SNMP traps and logging, refer to the
Unified MIB Reference
.
Managing Routers and Modules
Brocade NetIron MLXe Series Hardware Installation Guide
53-1004203-03 227