Installation Guide
Table Of Contents
- Extreme Routing MLX Series Hardware Installation Guide
- Preface
- About This Document
- Product Overview
- ExtremeRouting MLX Series device overview
- MLX Series router applications
- Hardware features
- MLX Series 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
- MLX Series 2x100G XPP ILKN monitoring
- MLX Series CPU threshold monitoring
- MLX Series BR-MLX-10Gx4-M IPsec and IKEv2
- MLX Series Encryption and Decryption of IPv4 Unicast Data and Control Packets
- MLX Series IKEv2 Authentication
- MLX Series IPsec and IKEv2 configuration
- MLX Series Configuring Global IKEv2 Options
- MLX Series Configuring the IKEv2 Proposal
- MLX Series Configuring the IKEv2 Policy
- MLX Series Configuring the IKEv2 Profile
- MLX Series Configuring the IKEv2 authentication proposal
- MLX Series Configuring the IPsec Proposal
- MLX Series Configuring the IPsec Profile
- MLX Series IKEv2 Show Commands
- MLX Series IKEv2 Clear Commands
- MLX-10GX4-IPSEC-M Forwarding
- MLX Series 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 MLX Series routers
- NIBI-16-FAN-EXH-A high-speed fan assemblies
- Rack mount kit
- Supported software features
- Installing an ExtremeRouting MLX Series device
- Pre-Installation notice for the ExtremeRouting MLX chassis bundles
- Installation precautions
- Installing 2x100GbE CFP2 interface modules
- Installing BR-MLX-10Gx24-DM interface modules
- Installing an MLXe-4 router
- Installing an MLX-8 router
- Installing an MLXe-16 router
- Mounting the MLX-4, MLX-8 or MLX-16 router in a 4-post rack or EIA rack
- Installing an MLXe-32 router
- Preparing the installation site
- MLXe-32 router shipping carton contents
- Unpacking your MLXe-32 router
- Installing an MLXe-32 router in an EIA rack
- Installing modules in the MLXe-32 router
- MLXe-32 router cable management
- Accessing modules for service
- Installing power supplies in an MLXe-32 router
- Connecting AC power
- Connecting DC power
- Removing the MLXe-32 router DC power supplies
- Final steps
- Attaching a management station
- Activating the power source
- Verifying proper operation
- Using Extreme 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
- ExtremeRouting MLX Series Chassis Bundles
- Regulatory Statements
- Caution and Danger Notices
IPv6 ND Proxy
Enabling the ND proxy feature causes the router to reply on behalf of the target host (if the target host exists).
For nodes on dierent segments, the NS request for resolving the neighbor may not reach another host. The reply will contain the link-
local address of the router interface which is sending the reply, instead of the link-local address of the target host.
When any IPv6 packet is received on a proxy interface, it must be parsed to see whether it is known to be one of the following types:
• ICMPv6 Neighbor Solicitation (NS)
If the received packet is an ICMPv6 Neighbor Solicitation (NS), the NS is processed locally but no NA is generated immediately.
Instead the NS is proxied, and the NA will be proxied when it is received. This ensures that the proxy does not interfere with
hosts moving from one segment to another, since it never responds to an NS based on its own cache.
• ICMPv6 Neighbor Advertisement (NA)
If the received packet is an ICMPv6 Neighbor Advertisement (NA), the neighbor cache on the receiving interface is rst updated
as if the NA were locally destined, and then the NA is proxied.
ND Proxy Example
In the following topology, A and B are nodes on separate segments which are connected by proxy P.
• A and B have link-layer addresses a and b, respectively.
• P has link-layer addresses p1 and p2 on the two segments.
A---|---P---|---B
a p1 p2 b
When A attempts to send an initial IPv6 packet to B, the following actions occur:
• Route look up for destination address B is executed on A. Before the packet can be sent, A needs to resolve B's link-layer
address and sends a Neighbor Solicitation (NS) to the solicited-node multicast address for B. The Source Link-Layer Address
(SLLA) option in the solicitation contains A's link-layer address.
• P receives the solicitation (since it is receiving all link-layer multicast packets) and processes it. Since it is an NS, it creates a
neighbor entry for A on interface 1, and records its link-layer address. It also creates a neighbor entry for B (on an arbitrary proxy
interface) in the INCOMPLETE state. Since the packet is multicast, P then needs to proxy the NS out on all other proxy
interfaces on the subnet. Before sending the packet out on interface 2, it replaces the link-layer address in the SLLA option with
its own link-layer address of p2.
• B receives this NS, processing it as usual. A neighbor entry for A is created and mapped to the link-layer address p2. In
response, a Neighbor Advertisement (NA) is sent to A containing B's link-layer address b. The NA is sent using A's neighbor
entry, i.e. to the link-layer address p2.
• The NA is received by P, which is processed as would occur with any unicast packet; i.e. the NA is forwarded out of interface 1,
based on the neighbor cache. However, before actually sending the packet out, it is inspected to determine if the packet about
to be sent is one that requires proxying. Since it is an NA, it updates its neighbor entry for B to be REACHABLE and records the
link-layer address b. P then replaces the link-layer address in the LLA option with its own link-layer address on the outgoing
interface, p1. The packet is then sent out on interface 1.
• When A receives this NA, it is processed as usual. Hence a neighbor entry is created for B on interface 1 in the REACHABLE
state, and the link-layer address p1 is recorded.
IPv6 ND Proxy
Extreme Routing MLX Series Hardware Installation Guide
236 53-1004203-04