Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, IronPoint, IronShield, IronView, IronWare, JetCore, NetIron,
SecureIron, ServerIron, StorageX, and TurboIron are registered trademarks, and DCFM, Extraordinary Networks, and SAN Health
are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. All other brands,
products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their
respective owners.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning
any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to
this document at any time, without notice, and assumes no responsibility for its use. This informational document describes
features that may not be currently available. Contact a Brocade sales office for information on feature and product availability.
Export of technical data contained in this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with
respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that
accompany it.
The product described by this document may contain “open source” software covered by the GNU General Public License or other
open source license agreements. To find-out which open source software is included in Brocade products, view the licensing
terms applicable to the open source software, and obtain a copy of the programming source code, please visit
http://www.brocade.com/support/oscd.
Brocade Communications Systems, Incorporated
Corporate and Latin American Headquarters
Brocade Communications Systems, Inc.
130 Holger Way
San Jose, CA 95134
Tel: 1-408-333-8000
Fax: 1-408-333-8101
E-mail: info@brocade.com
European Headquarters
Brocade Communications Switzerland Sàrl
Centre Swissair
Tour B - 4ème étage
29, Route de l'Aéroport
Case Postale 105
CH-1215 Genève 15
Switzerland
Tel: +41 22 799 5640
Fax: +41 22 799 5641
E-mail: emea-info@brocade.com
Asia-Pacific Headquarters
Brocade Communications Systems China HK, Ltd.
No. 1 Guanghua Road
Chao Yang District
Units 2718 and 2818
Beijing 100020, China
Tel: +8610 6588 8888
Fax: +8610 6588 9999
E-mail: china-info@brocade.com
Asia-Pacific Headquarters
Brocade Communications Systems Co., Ltd. (Shenzhen WFOE)
Citic Plaza
No. 233 Tian He Road North
Unit 1308 – 13th Floor
Guangzhou, China
Tel: +8620 3891 2000
Fax: +8620 3891 2111
E-mail: china-info@brocade.com
Document History
TitlePublication numberSummary of changesDate
BigIron RX Series Configuration Guide53-1001986-01Release 02.7.03 featuresAug 2010
BigIron RX Series Configuration Guidexxxix
53-1001986-01
xlBigIron RX Series Configuration Guide
53-1001986-01
About This Document
Audience
This document is designed for system administrators with a working knowledge of Layer 2 and
Layer 3 switching and routing.
If you are using a Brocade Layer 3 Switch, you should be familiar with the following protocols if
applicable to your network – IP, RIP, OSPF, BGP, ISIS, IGMP, PIM, DVMRP, and VRRP.
Supported hardware and software
Although many different software and hardware configurations are tested and supported by
Brocade Communications Systems, Inc., documenting all possible configurations and scenarios is
beyond the scope of this document.
The following hardware platforms are supported by this release of this guide:
• Software release version 02.7.03
List of supported features
Features or options not listed in the Supported features table or documented in this guide are not
supported.
TABLE 1Supported features
CategoryFeature description
System level features
Cisco Discovery Protocol (CDP)Allows you to configure a Brocade device to intercept and display the
contents of CDP packets. This feature is useful for learning device
and interface information for Cisco devices in the network.
CLI Logging
Denial of Service (DoS) protectionProtection from SYN attacks
Protection from Smurf attacks
Foundry Discovery Protocol (FDP)Enables Brocade devices to advertise themselves to other Brocade
devices on the network.
High AvailabilityOS Layer 2 Hitless Software Upgrade
BigIron RX Series Configuration Guidexli
53-1001986-01
TABLE 1Supported features (Continued)
CategoryFeature description
Management OptionsSerial and Telnet access to industry-standard Command Line
Local passwords
RADIUS
Secure Shell (SSH) version 2
Secure Copy (SCP)
TACACS and TACACS+
User accounts
802.1x: All EAP types, including MD5, TLS, TTLS, and PEAP
Multi-device port authentication
AES for SNMPv3, SSHv2, SCP, and HTTPS
Note:Telnet, SSH, Web and SNMP servers are disabled by default,
and can be enabled selectively.
CPU protectionThere are no CLI commands for CPU protection. The device forwards
unknown unicast, broadcast and multicast packets in hardware;
therefore, the CPU is automatically 'protected' from having to handle
too many packets.
SysLogD Server LoggingMultiple SysLogD server logging
sFlowsFLow version 5
Uni-directional Link Detection (UDLD)Monitors a link between two Brocade devices and brings the ports on
both ends of the link down if the link goes down at any point between
the two devices.
Layer 2 features
802.1dSpanning Tree Protocol (STP)
and
Single Spanning Tree Protocol (SSTP)
802.1pQuality of Service (QoS) queue mapping
802.1qSee VLANs, below
802.1sMultiple Spanning Tree Protocol (MSTP)
802.1wRapid Spanning Tree Protocol (RSTP)
802.3adDynamic Link Aggregation on tagged and untagged trunks
Jumbo packetsLayer 2 jumbo packet support
Layer 2 Hitless failover
Layer 2 IGMP Snooping
L2 ACL Filtering based on MAC layer-2 parameters.
MAC Filtering MAC filtering and address-lock filters to enhance network security
MRPMetro Ring Protocol (MRP) Phase 1 and 2
PVST / PVST+Per-VLAN Spanning Tree (PVST)
xliiBigIron RX Series Configuration Guide
53-1001986-01
TABLE 1Supported features (Continued)
CategoryFeature description
Rate LimitingPort-based, port-and-priority based, port-and-vlan-based, and
port-and-ACL-based rate limiting on inbound ports are supported.
SuperSpanA Brocade STP enhancement that allows Service Providers (SPs) to
use STP in both SP networks and customer networks.
Topology GroupsA named set of VLANs that share a Layer 2 topology. You can use
topology groups with the following Layer 2 protocols:
• STP
• Brocade MRP
• VSRP
• 802.1W
Trunk Groups and LAGAllows you to manually configure multiple high-speed load-sharing
links between two Brocade devices or between a Brocade device and
a server.
VLANs802.1Q tagging
Port-based VLANs
Super Aggregated VLANs (SAV)
Dual-mode VLAN ports
Transparent Port Flooding
VLAN ID to MSTP Instance Pre-assignment
Private VLANs
PBRPolicy Based Routing (Release 02.2.01 and later)
RIP versions 1 and 2RIP routes
VRRP and VRRPEVirtual Router Redundancy Protocol (VRRP)
and
VRRP Extended (VRRPE)
IPv6 features
IPv6 ACLsExtended ACLs
IPv6 Routing ProtocolsRIPng
OSPFv3
BGP4+
IPv6 Multicast PIM-SM
MLD
Unsupported features
The following features are not supported in software release 02.7.03
• AppleTalk
• IPX
• Mirroring across VLANs
• MPLS
• NAT
• RARP
• VLAN translation
• Subnet VLANs
• Source IP Port Security
xlivBigIron RX Series Configuration Guide
53-1001986-01
What’s new in this document
The following tables provide brief descriptions of the enhancements added in each BigIron RX
software release and a reference to the specific chapter, and section in the BigIron RX
Configuration Guide or the Brocade BigIron RX Series Installation Guide that contain a detailed
description and operational details for the enhancement.
Enhancements in release 02.7.03
TABLE 2Summary of enhancements in release 02.7.03
EnhancementDescriptionSee page
System Monitoring
Service (SYSMON)
clear ipv6 ospf
command
switchover commandWhen you enter the switchover command, the
Support for active cable
for 16-po rt 10 Gigabit
Ethernet module
Monitoring I2C failure on
a management module
Rebranded show version
command output
Rebranded RADIUS Vendor specific attributes for RADIUS have
This feature was introduced in the 02.6.00c
patch release. It monitors the hardware in the
system to detect, report, and in some cases
isolate and recover hardware errors in the
system. When an error or event occurs,
SYSMON generates Syslog messages, which
must be reported to Brocade Technical Support
This enhancement was introduced in Patch
Release 02.7.02a and has been added to this
issue of the BigIron RX Series Configuration Guide.
The clear ipv6 ospf CLI command has been
deprecated
This enhancement was introduced in Patch
Release 02.7.02c and has been added to this
issue of the BigIron RX Series Configuration Guide.
CLI asks you to confirm your request. Enter Y to
continue or N to cancel your request.
This enhancement was introduced in Patch
Release 02.7.02c and has been added to this
issue of the BigIron RX Series Configuration Guide.
10 Gbps Direct Attached Small Form-Factor
Pluggable (SFP+) copper cable (1m, 3m, 5m) is
available for the 16-port 10 Gigabit Ethernet
module
The show logging command can be use to
monitor I2C failures.
The output of the show version command now
shows "Brocade Communications"
been renamed to "brocade-command-string",
"brocade-privilege-level", and
"brocade-command-exception-flag"
Book: BigIron RX Series
Configuration Guide
Chapter: “Using a Redundant
Management Module”
Section: “System Monitoring
Service”
N/A
Book: BigIron RX Series
Configuration Guide
Chapter: “Using a Redundant
Management Module”
Section: “Manually switching over to
the standby management module”
Book: Brocade BigIron RX Series
Installation Guide
Book: Brocade BigIron RX Series
Installation Guide
Book: Brocade BigIron RX Series
Installation Guide
Book: BigIron RX Configuration
Giuide
Chapter: “Securing Access to
Management Functions”
Section: “Configuring RADIUS
security” on page 100
BigIron RX Series Configuration Guidexlv
53-1001986-01
TABLE 2Summary of enhancements in release 02.7.03
EnhancementDescriptionSee page
MAC Port Security The MAC Port Security feature has been
updated for the 02.7.03 release.
Syslog updateThe System Log has been updated as follows:
• Separate buffers for static and dynamic
logs
• Entries in the static log buffer are cleared
at reset or reload, while entries in the
dynamic log are preserved
Book: BigIron RX Configuration
Giuide
Chapter: “Using the MAC Port
Security Feature and Transparent
Port Flooding” on page 931
Book: BigIron RX Configuration
Giuide
Chapter: “Using Syslog” on
page 1261
• Log buffer size cannot be changed. the log
buffer size is set at 3800 lines
• A show logging command is now available
at the monitor level for Active and Standby
Management Processors
Enhancements in release 02.7.02
TABLE 3Summary of enhancements in release 02.7.02
EnhancementDescriptionSee page
System features
Enhanced spreed-duplex
command
The speed-duplex command has been
enhanced to support 24F and 24HF modules.
The auto (Autonegotiation mode) option has
also been added to allow the user to set the
speed on E1MG-TX media.
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring Interface
Parameters”
Section: “Speed/Duplex
negotiation”
Enhancements in release 02.7.01
TABLE 4Summary of enhancements in release 02.7.01
EnhancementDescriptionSee page
System features
New 16x10G module.iewThe new 16 port 10GE oversubscribed module
provides 4:1 over-subscription on the network
ports. The new module is compatible with all
previous modules on the BigIron RX.
xlviBigIron RX Series Configuration Guide
Book: Brocade BigIron RX
Series Installation Guide
TABLE 4Summary of enhancements in release 02.7.01 (Continued)
EnhancementDescriptionSee page
Network management
128-bit AES encryption
support for SNMP V3
AES Encryption for SSH v2,
Secure Copy (SCP), and
Secure HTTPS (HTTPS)
The Advanced Encryption Standard (AES) provides
one of the most advanced encryption capabilities
available today. This release adds AES for SNMPv3
as specified in RFC 3826.
To enable AES encryption, specify the aes
encryption type when defining an SNMP user
account.
SSH v2, SCP, and HTTPS now supports a very strong
AES encryption algorithm in the following modes:
aes256-cbc, aes192-cbc, and aes128-cbc.
Book: BigIron RX Series
Configuration Guide
Chapter: “Securing SNMP
Access”
Section: “Defining an
SNMP user account”
Book: BigIron RX Series
Configuration Guide
Chapter: “Securing SNMP
Access”
Section:
Enhancements in release 02.7.00
TABLE 5Summary of enhancements in release 02.7.00
EnhancementDescriptionSee page
Layer 1 features
New Optics SupportThe SFP-compliant E1MG-TX fiber-optic module now
supports speeds of 10/100/1000.
UDLD Start-up ModeIn this release, after UDLD is enabled on a port,
UDLD can be configured to be kept in a newly
created suspended state until it receives its first
keep-alive message from the other end.
Multicast, Broadcast, and
Unknown Unicast Rate
Limiting per Module
Link Layer Discovery Protocol
(LLDP)
CLI ChangeTo globally enable MAC port security, the
This release introduces a new hardware (module)
based Multicast/Broadcast/Unknown Unicast
Rate-Limiting for both CPU based flooding and
Hardware based flooding.
Beginning with release 02.7.00, Link Layer
Discovery Protocol (LLDP) is supported. This
protocol enables a station to advertise its
capabilities to, and to discover other LLDP-enabled
stations in the same 802.1AB LAN segments.
global-port-security command has been added. The
port security command is now only used when
configuring MAC port security on specific interfaces.
Book: Brocade BigIron RX
Series Installation Guide
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring
Uni-Directional Link
Detection (UDLD)”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
Traffic Reduction”
Section: “NP based
multicast, broadcast, and
unknown-unicast rate
limiting”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
LLDP”
Book: BigIron RX Series
Configuration Guide
Chapter: “Using the MAC
Port Security Feature and
Transparent Port Flooding”
Section: “Enabling the MAC
Port Security feature”
BigIron RX Series Configuration Guidexlvii
53-1001986-01
TABLE 5Summary of enhancements in release 02.7.00 (Continued)
EnhancementDescriptionSee page
Network management
DHCP Relay EnhancementBeginning with this release, the IP subnet
configured on the port which is directly connected
to the device sending a BootP/DHCP request, does
not have to match the subnet of the IP address
given by the DHCP server.
SNMP MIBs for Layer 2 ACLs
and Filters
The following MIB tables have been added to this
release:
Digital Optical MonitoringBeginning with release 0 2.6.00, Digital Optical
Monitoring will only support newly qualified
1Gigabit optics. Digital Optical Monitoring for
previous 1Gigabit optics that do not include "OM"
after the model numbers will not be able to use this
feature.
BFD for IS-IS, OSPFv2 and
OSPF v3
LACP Continous Fast TimerIn a dynamic or keep-alive LAG, a port's timeout can
Rate Limiting ARP PacketsThis new feature allows you to rate-limit ARP traffic
Layer 2 features
BigIron RX provides support for Bidirectional
Forwarding Detection (BFD) in Version 02.6.00 of
the Multi-Service IronWare software.
be configured as short or long
that is destined for CPU of the BigIron RX router.
Book: Brocade BigIron RX
Series Installation Guide
Chapter: Connecting a
BigIron RX Series Switch
to a Network Device
Section:Digital Optical
Monitoring
Book: BigIron RX Series
Configuration Guide
Chapter: “BiDirectional
Forwarding Detection
(BFD)”
Book: BigIron RX Series
Configuration Guide
Chapter: “Link
Aggregation”
Section: “Configuring an
LACP timeout”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP”
Section:“Apply in g a rate
limit to ARP packets on an
interface”
xlviiiBigIron RX Series Configuration Guide
53-1001986-01
TABLE 6Summary of enhancements in release 02.6.00 (Continued)
EnhancementDescriptionSee page
VSRP Fast StartNon-Brocade or non-VSRP aware devices
connected to a VSRP master can now quickly switch
over to the new master when a VSRP failover
occurs.
LACP EnhancementsBeginning with release 02.6.00 of the Multi-Service
IronWare software, all trunking and link aggegation
configuration has been revamped and placed under
a single interface. This new interface allows you to
configure either of the previously supported LAG
types: Static LAGs and Dynamic LAGs as well as the
new “Keep Alive” LAGs.
The new LAG configuration procedures supersede
the previous configurations procedures for Trunks
and Dynamic Link Aggregation.
Multicast Layer 2 FilterBeginning with release 02.6.00, you can define
multicast boundaries on a per VLAN basis.
Layer 3 features
IPv6 PIM-SMIn Release 02.6.00 of the Multi-Service IronWare
software, the BigIron RX supports IPv6 Protocol
Independent Multicast (PIM) Sparse. IPv6 PIM
Sparse provides multicasting that is especially
suitable for widely distributed multicast
environments
IPv6 Embedded RPThis release supports Embedded RP which allows
the switch to learn RP information using the
multicast group destination address instead of the
statically configured RP.
IPv4 PIM SnoopingPIM SM traffic snooping eliminates the superfluous
traffic by configuring the device to forward IP
multicast group traffic only on the ports that are
attached to receivers for the group
Multicast Listening Discovery
(MLD)
Release 02.6.00 adds support for MLD Snooping
(MLDv1 and MLDv2) on Brocade BigIron RXdevices
running IPv6.
Book: BigIron RX Series
Configuration Guide
Chapter: “Virtual Switch
Redundancy Protocol
(VSRP)”
Section: “VSRP fast start”
Book: BigIron RX Series
Configuration Guide
Chapter: “Link
Aggregation”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP
Multicast Protocols”
Section: “Layer 2 multicast
filters”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IPv6
Multicast Features”
Section: “IPv6 PIM-sparse
mode”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IPv6
Multicast Features”
Section: “Embedded
Rendezvous Point (RP)”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP
Multicast Protocols”
Section: “PIM SM traffic
snooping”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IPv6
Multicast Features”
Section: “Multicast
Listener Discovery and
source specific multicast
protocols (MLDv2)”
BigIron RX Series Configuration Guidexlix
53-1001986-01
TABLE 6Summary of enhancements in release 02.6.00 (Continued)
EnhancementDescriptionSee page
IGMPv3 and IGMP SnoopingIn Release 02.6.00 of the Multi-Service IronWare
software, creating an IGMP static-group allows the
BigIron RX switch having L2 interfaces configured
with snooping to pull traffic from upstream sources
using IGMP joins. When using the uplink option, you
avoid burning a dedicated port. This is supported
for IGMP v2 and v3.
IGMP v3 Static ClientIn Release 02.6.00 of the Multi-Service IronWare
software, creating an IGMP static-group allows the
BigIron RXswitch having L2 interfaces configured
with snooping to pull traffic from upstream sources
using IGMP joins. When using the uplink option, you
avoid burning a dedicated port. This is supported
for IGMP v2 and v3.
IGMP v3 Fast Leave and
Tra ckin g
Static Route ARP Validate
Next Hop
IGMP Proxy per VLAN or
instance
Layer 4 features
Automatic ACL RebindBeginning wirh release 02.6.00, the ACL automatic
Network management
Support for BFD MIB and
SNMP Traps
In Release 02.6.00 of the Multi-Service IronWare
software, you can configure a device running IGMP
Snooping to immediately remove a VLAN from the IP
multicast group when it detects a fast leave
message on a specified VLAN.
Beginning with release 02.6.00, you can configure
the BigIron RX to perform multicast validation
checks on the destination MAC address, the sender
and target IP addresses, and the source MAC
address.
Introduced in version 02.6.00 of the Multi-Service
IronWare software, multicast traffic can be reduced
by configuring an BigIron RX switch to issue IGMP
host messages on behalf of hosts that the
configured router discovers through standard PIM
interfaces. The router is then able to act as a proxy
for the discovered hosts and perform IGMP tasks
upstream of the discovered hosts. Where there are
multiple IGMP hosts downstream, this removes the
need to send multiple messages.
rebind feature allows the newly changed ACL filter
definitions to be automatically applied to the ports
where the ACL was bound.
Support for BFD IETF draft mib version 3
(draft-ietf-bfdmib-03.mib) with this release as
described in the Management Information Base
Reference.
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP
Multicast Protocols”
Section: “IGMP v3”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP
Multicast Protocols”
Section: “Creating a static
IGMP group”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP
Multicast Protocols”
Section:“Enabling
membership tracking and
fast leave”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP
Multicast Protocols”
Section: “Next hop
validation check”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP
Multicast Traffic
Reduction”
Section: “Multicast traffic
reduction per VLAN”
Book: BigIron RX Series
Configuration Guide
Chapter: “Access Control
List”
Section: “ACL automatic
rebind”
Book: MIB Reference
Chapter:
Forwarding
Bidirectional
lBigIron RX Series Configuration Guide
53-1001986-01
Enhancements in patch release 02.5.00c
TABLE 7Summary of enhancements in release 02.5.00c
EnhancementDescriptionSee page
Super ACLsWith this patch release, the Multi-Service IronWare
software supports Super ACLs that can match on
fields in a Layer 2 or Layer 4 packet header.
Book: BigIron RX Series
Configuration Guide
Chapter: “Access Control
List”
Section: “Configuring
super ACLs”
Enhancements in patch release 02.5.00b
TABLE 8Summary of enhancements in release 02.5.00b
EnhancementDescriptionSee page
ACL-based Inbound sFlowWith this patch release, the Multi-Service IronWare
software supports using an IPv4 ACL to select
packets that should be collected as special sFlow
samples, in addition to the regular statistical
sampling of sFlow.
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
sFlow”
Section: “ACL-ba sed
inbound sFlow”
Enhancements in release 02.5.00
TABLE 9Summary of enhancements in release 02.5.00
EnhancementDescriptionSee page
BigIron RX-32
Chassis
New Process for Upgrading
Multi-Service IronWare
Software
SDS Over TelnetBeginning with release 02.5.00 of the Multi-Service
Enhancement on Static ARPIn Release 02.5.00 of the Multi-Service IronWare
Release 02.5.00 introduces the BigIron RX-32
chassis which runs the same Multi-Service
IronWare software as other chassis in the BigIron
RX series.
The new BigIron RX-32 chassis provide support for
up to 32 interface modules.
The software images required for operating the
BigIron RX switch remain the same however,
beginning with version 02.5.00 of the Multi-Service
IronWare software, the upgrading procedures have
been changed. The new procedure is described in
the Release Notes for BigIron RX – Multi-Service
IronWare Software Release 02.5.00.
IronWare software, remote SDS is supported. This
feature will dramatically improve the ability to
troubleshoot issues on the line-card without the
need of a serial cable.
software, static ARP has been enhanced to support
the ability to create a static ARP entry without an
outgoing interface.
New MIB ObjectsThe following MIB objects have been added to the
Beginning with release 02.5.00, you can configure
the BigIron RX to perform validation checks on the
destination MAC address, the sender and target IP
addresses, and the source MAC address.
drivers have been enhanced to optimize utilization
and improve overall performance.
traffic is rate-limited to 1.8 Gbps per packet
processor.
In Release 02.5.00 of the Multi-Service IronWare
software, new option have been added to the copy
tftp image command to enable the user to upgrade
the boot, monitor, and MBRIDGE only when
needed.
Book: MIB Reference
Chapter: Interfaces
Section: Port STP
Configuration Groups
Enhancements in patch release 02.4.00c
TABLE 10Summary of enhancements in release 02.4.00c
EnhancementDescriptionSee page
ACL Based RP assignmentThe rp-address command has been enhanced to
allow multiple static RP configurations.
Route Selection Precedence
for Multicast
liiBigIron RX Series Configuration Guide
In patch 02.4.00c, the route-precedence command
allows the user to specify a precedence table that
dictates how routes are selected for multicast.
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP
Multicast Protocols”
Section: “ACL based RP
assignment”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP
Multicast Protocols”
Section:“Route selection
precedence for multicast”
53-1001986-01
Enhancements in release 02.4.00
TABLE 11Summary of enhancements in release 02.4.00
EnhancementDescriptionSee page
US Daylight Saving Time
scheme
New show boot-image
command
New show image_checksum
command
Private VLANA private VLAN is a VLAN that has the properties of
MRP Phase 2In Metro Ring Protocol (MRP) Phase 2, the same
Outbound Rate Limiting Outbound rate limiting support has been added to
Increase Global Static ARP
Entries
OSPF ABR Type 3 LSA Filtering The OSPF ABR Type 3 LSA Filtering feature extends
The new Daylight Saving Time (DST) change that
went into effect on March 11th, 2007 affects only
networks following the US time zones. However, to
trigger the device to the correct time, the device
must be configured to the US time zone, not the
GMT offset.
Using the show boot-image command displays
which image the device will use for the next reboot
or reload.
The image_checksum command will allow the user
to verify the checksum of a image.
standard Layer 2 port-based VLANs but also
provides additional control over flooding packets on
a VLAN.
physical interface can be shared by multiple rings
belonging to the same VLAN.
this release.
The system max value for ip-static-arp can be
configured to values up to 16,384 beginning with
version 02.4.00 of the BigIron RX Multi-Service
IronWare software.
the ability of an ABR that is running the OSPF
protocol to filter type 3 link-state advertisements
(LSAs) that are sent between different OSPF areas.
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
Basic Parameters”
Section: “New Daylight
Saving Time (DST)”
Book: Brocade BigIron RX
Series Installation Guide
Chapter: Upgrading
Software Images and
Configuration Files
Section: Displaying the
Next Boot Image
Book: Brocade BigIron RX
Series Installation Guide
Chapter: Upgrading
Software Images and
Configuration Files
Section: Verifying the
Checksum of an Image
Book: BigIron RX Series
Configuration Guide
Chapter:“VLANs”
Section: “Private VLANs”
Book: BigIron RX Series
Configuration Guide
Chapter: “Metro Ring
Protocol (MRP) Phase 1
and 2”
Section: “MRP phase 2”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
Traffic Reduction”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP”
Section: “Changing the
maximum transmission
unit on an individual
interface”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
OSPF Version 2 (IPv4)”
Section: “OSPF ABR type 3
LSA filtering”
BigIron RX Series Configuration Guideliii
53-1001986-01
TABLE 11Summary of enhancements in release 02.4.00 (Continued)
EnhancementDescriptionSee page
New show OSPF neighbor by
area command
Track IP route time in show
command
Compare MED for internal BGP
route with empty as-path
OSPF Default Network RouteThis feature enables the BigIron RX to use default
IPv6 Default Route ECMPThis feature allows for load distribution of traffic
IPv6 Tunneling in HardwareManual configuration of IPv6 to IPv4 tunnels is now
IPv6 Load Sharing over ECMP
and Trunks
Directly Attached Host
Resource Allocation
This feature allows OSPF to display the OSPF
neighbors existing in a particular area.
The show ip route command has been enhanced to
include the elapse time since an IP route was
installed.
This new BGP command directs iBGP to take the
MED value into consideration even if the route has
an empty as-path path attribute.
route (0.0.0.0/0) to a resolve static OSPF route.
Note:This differs from the default behavior in
previous versions of Multi-Service IronWare
software.
among the available IPv6 default route next-hops.
supported in this release. These tunnels will be
installed into the hardware route table and tunnel
encapsulation and decapsulation is done in
hardware.
When the device receives traffic for a destination,
and the IPv6 route table contains multiple,
equal-cost paths to that destination, the packets
are load balanced between multiple next-hops
including member ports of a trunk.
The CAM allocations can be re-distributed using the
cam-partition next-hop command.
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
OSPF Version 2 (IPv4)”
Section: “Displaying OSPF
neighbor information”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP”
Section: “Displaying the IP
route table”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
BGP4 (IPv4 and IPv6)”
Section: “Configuring the
device to always compare
MEDs”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
OSPF Version 2 (IPv4)”
Section: “Configuring a
default network route”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
Basic IPv6 Connectivity”
Section: “ECMP load
sharing for IPv6”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP”
Section:“IPv6 over IPv4
tunnels in hardware”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
Basic IPv6 Connectivity”
Section: “ECMP load
sharing for IPv6”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
Basic Parameters”
Section: “Re-distributing
CAM allocations”
livBigIron RX Series Configuration Guide
53-1001986-01
TABLE 11Summary of enhancements in release 02.4.00 (Continued)
EnhancementDescriptionSee page
Multicast BoundariesThe Multicast Boundary feature is designed to
selectively allow or disallow multicast flows to
configured interfaces.
MBGP for IPv6This release supports the Multi-protocol Border
IP Source Guard IP source guard is used on client ports to prevent IP
Dynamic ARP Inspection Dynamic ARP Inspection (DAI) is a security feature
DHCP Snooping with Option 82 This feature allows the device to snoop DHCP
DoS Protection This feature allows for monitoring the hit rate of the
This new feature prevents unwanted multicast
traffic from being sent the CPU by conditionally
dropping unwanted multicast traffic in hardware.
source address spoofing.
that can prevent Man-in-the-Middle (MiM) or ARP
spoofing/poisoning attacks.
packets for Dynamic ARP inspection and allows for
the insertion of DHCP Option 82 attributes into the
DHCP packet prior to relaying to the DHCP server.
ACL and drops matching traffic above a selected
rate and locking the port if the rate exceeds a
maximum allowed amount.
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP
Multicast Protocols”
Section: “IP multicast
boundaries”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IPv6
MBGP”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IPv6
Routes”
Section: “Configuring a
IPv6 multicast route”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP
Multicast Protocols”
Section: “Passive Multicast
Route Insertion (PMRI)”
Book: BigIron RX Series
Configuration Guide
Chapter: “Inspecting and
Tra cki ng D HCP Pac ke ts. ”
Section: “IP source guard”
Book: BigIron RX Series
Configuration Guide
Chapter: “Inspecting and
Tra cki ng D HCP Pac ke ts”
Section: “Dynamic ARP
inspection”
Book: BigIron RX Series
Configuration Guide
Chapter: “Inspecting and
Tra cki ng D HCP Pac ke ts”
Section: “DHCP relay agent
information (DHCP option
82)”
Book: BigIron RX Series
Configuration Guide
Chapter: “Protecting
Against Denial of Service
Attacks”
Section:“ACL-based
DOS-attack prevention”
BigIron RX Series Configuration Guidelv
53-1001986-01
TABLE 11Summary of enhancements in release 02.4.00 (Continued)
EnhancementDescriptionSee page
ACL-Based MirroringWith this release, the Multi-Service IronWare
software supports using an ACL to select traffic for
mirroring from one port to another.
ip dns domain-list commandThis feature is designed to define a list od domain
names that are used in order to resolve a host.
CLI Logging This feature provides the logging of all valid CLI
commands from each user session into the system
log.
Syslog Source InterfaceYou can configure the BigIron RX to use the
lowest-numbered IP or IPv6 address configured on
a loopback interface, virtual interface, or Ethernet
port as the source for all Syslog packets from the
device.
UDLD Traps and SyslogsUDLD state changes will now be logged by default.Book: MIB Reference
New Brocade MIB objectsThe following MIBs have been depreciated by
snAgentCpuUtilTable:
• snAgGblCpuUtil1SecAvg
• snAgGblCpuUtil5SecAvg
• snAgGblCpuUtil1MinAvg
Book: BigIron RX Series
Configuration Guide
Chapter:“Access Control
List”
Section: “AC L-b ased
inbound mirroring”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP”
Section: “Defining a DNS
entry”
Book: BigIron RX Series
Configuration Guide
Chapter: “Using Syslog”
Section:“Logging all CLI
commands to Syslog”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP”
Section:“Configuring an
interface as the source for
Syslog packets”
Chapter: Traps and Objects
to Enable Traps
Section: UDLD Traps
Book: MIB Reference
Chapter: Monitoring and
Logging
Section: Usage Notes on
CPU Utilization and System
CPU Utility Table
lviBigIron RX Series Configuration Guide
53-1001986-01
Enhancements in patch release 02.3.00a
TABLE 12Summary of enhancements in patch release 02.3.00a
EnhancementDescriptionSee...
Transparent Port Flooding When the Transparent Port Flooding feature in
enabled for a port, all MAC learning will be disabled
for that port. This will result in all Layer 2 traffic to
be flooded to all other ports within the VLAN.
Starting with release 02.3.00a.
VLAN ID to MSTP Instance
Pre-assignment
This feature will allow the user to assign a VLAN ID
to a Common Spanning Tree (CIST), or Multiple
Spanning Tree Instance (MSTI) even though a VLAN
has not been created yet. Starting with release
02.3.00a.
Book: BigIron RX Series
Configuration Guide
Chapter: “Using the MAC
Port Security Feature
and Transparent Port
Flooding”
Section:“Transparent
port flooding”
Book: BigIron RX Series
Configuration Guide
Chapter: “Multiple
Spanning Tree Protocol
(MSTP) 802.1s” and
“VLANs”
Section:“Configuring an
MSTP instance”
BigIron RX Series Configuration Guidelvii
53-1001986-01
Enhancements in release 02.3.00
System enhancements
TABLE 13System enhancements
EnhancementDescriptionSee...
New Hardware
Support
The following new hardware is supported with the 02.3.00
software release for the BigIron RX:
110G-XFP-CX4 - part number 10G-XFP-CX4 , A new XFP
Module is available for use in the BigIron RX Series and
10G Interface Modules with the following capabilities:
Book: Brocade BigIron RX
Series Installation Guide
• 10GBASE-CX4 compliant per 802.1ak
• CX4 connector
• Up to 15 meter reach when using CX4 grade copper
cables
• Restriction of Hazardous Substances (RoHS) 5/6
compliant
• Hot pluggable
• Compatible with industry-standard MDI socket for
CX4
• Supports 4 channel full-duplex copper cable
210GBase-ZR – part number 10G-XFP-ZR supports 1550
nm wavelength with a maximum distance of up to 80 km
over single mode fiber (SMF).
310GBase-ZRD – part number 10G-XFP-ZRD supports 40
different wavelengths at 1550 nm.
448-port 1 Gbps Copper Ethernet interface module
Hitless OS Upgrade
for Layer 2
Logging of packets
denied by ACLs.
Modifying ACLsYou can modify ACL entries anywhere in an ACL. Book: BigIron RX Series
SFM FE Monitoring In this release, the Switch Fabric Module monitoring has been
Version 02.5.00 of the Multi-Service IronWare software
supports hitless upgrade of the operating system on a BigIron
RX switch. Using this feature, you can upgrade the
Multi-Service IronWare software without a loss or disruption of
service as described.
You can restrict the number of times a message is logged in
the Syslog due to packets that matches a deny ACL condition.
enhanced. If the SFM fails, it generates a syslog that includes
the status of individual fabric elements on the SFM modules.
Book: Brocade BigIron RX
Series Installation Guide
Chapter: Upgrading
Software Images and
Configuration Files
Section:Layer 2 Hitless OS
Upgrade
Book: BigIron RX Series
Configuration Guide
Chapter: “Access Control
List”
Section: “Enabling the
new logging method”
Configuration Guide
Chapter: “Access Control
List”
Section: “Enabling the
new logging method”
Book: Brocade BigIron RX
Series Installation Guide
lviiiBigIron RX Series Configuration Guide
53-1001986-01
TABLE 13System enhancements (Continued)
EnhancementDescriptionSee...
Enhanced Digital
Optical Monitoring
Re-distributing CAM
Allocations
Enhanced SFM
(power-off)
command
Enhanced
speed-duplex
command
You can configure the BigIron RX to monitor XFPs and SFPs in
the system either globally or by specified port.
In releases prior to 02.3.00, CAM partitioning was not
configurable. Starting in BigIron RX software release 02.3.00,
you can specify the CAM assigned to each of the CAM entry
types globally.
You can disable power to a specified switch fabric module and
then reenable it.
In this release, the speed-duplex command has been
enhanced to include the master and slave parameters.
Book: Brocade BigIron RX
Series Installation Guide
Chapter: Connecting a
BigIron RX Series Switch
to a Network Device
Section: Enhanced Digital
Optical Monitoring
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
Basic Parameters”
Section: “Re-distributing
CAM allocations”
Book: Brocade BigIron RX
Series Installation Guide
Chapter: Managing the
BigIron RX Series Chassis
and Modules
Section: Disabling and
Reenabling Power to the
Switch Fabric Modules
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
Interface Parameters”
Section:“Speed/Duplex
negotiation”
Layer 2 enhancements
TABLE 14 Layer 2 enhancements
EnhancementDescriptionSee...
Flow based MAC LearningIn this release, the cpu-flooding unknown-unicast
command that disables hardware flooding of
unknown unicast on every VLAN has been added.
This will allow MAC learning only where necessary
and at a system level to allow more than 16k MACs.
VSRP Slow-StartThis feature allows for a hold down time before the
backup returns ownership to the master after the
link is seen.
802.1s Multiple Spanning Tree
Protocol (MSTP)
With this release, you can configure multiple STP
instances using MSTP protocol, as defined in IEEE
802.1s
Book: BigIron RX Series
Configuration Guide
Chapter: “VLANs”
Section: “Flow based
MAC learning”
Book: BigIron RX Series
Configuration Guide
Chapter: “Virtual Switch
Redundancy Protocol
(VSRP)”
Section:“VSRP slow
start”
Book: BigIron RX Series
Configuration Guide
Chapter: “Multiple
Spanning Tree Protocol
(MSTP) 802.1s”
BigIron RX Series Configuration Guidelix
53-1001986-01
Layer 3 enhancements
TABLE 15Layer 3 enhancements
EnhancementDescriptionSee...
OSPF NBMAYou can configure an interface to send OSPF
unicast packets rather than broadcast packets to
its neighbor by configuring non-broadcast
multi-access (NBMA) networks.
Layer 3 VSRPVSRP redundancy and sub-second failover for
Layer 3 topologies is available in this release.
VSRP Delay Link EventsThis is a new VSRP command that will delay the
sending of port "up"/"down" events.
IPv6 Hardware Forwarding Forwarding for Layer 3 IP switching technology for
the forwarding of IPv6 packets.See the
"Configuring Basic IPv6 Connectivity" chapter of
the BigIron RX Series Configuration Guide.
OSPF v3IPv6 supports OSPF version 3 (OSPFv3), which
functions similarly to OSPF version 2.
BGP+Brocade’s implementation of IPv6 supports multi
protocol BGP (MBGP) extensions, which allow
IPv6 BGP (known as BGP4+) to distribute routing
information for protocols such as IPv4 BGP.
RIPngIPv6 RIP, known as Routing Information Protocol
Next Generation or RIPng, functions similarly to
IPv4 RIP version 2. RIPng supports IPv6
addresses and prefixes.
ACL Duplication CheckThe acl-duplication-check command has been
changed to acl-duplication-check-disable. With
this command, software checking for duplicate
ACL entries will be disabled after an upgrade.
IPv6 ACLsIn this release you can use an IPv6 ACL to provide
input to other features such as route maps and
distribution lists.
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
OSPF Version 2 (IPv4)”
Section:“Configuring an
OSPF non-broadcast
interface”
Book: BigIron RX Series
Configuration Guide
Chapter: “Virtual Switch
Redundancy Protocol
(VSRP)”
Section:“Enabling Layer 3
VSRP”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
Interface Parameters”
Section:“Port transition
hold timer”
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring
Basic IPv6 Connectivity”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
OSPF Version 3”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
BGP4+”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
RIPng”
Book: BigIron RX Series
Configuration Guide
Chapter: “Access Control
List”
Section:“Enabling ACL
duplication check”
Book: BigIron RX Series
Configuration Guide
Chapter: “IPv6 Access
Control Lists (ACLs)”
lxBigIron RX Series Configuration Guide
53-1001986-01
TABLE 15Layer 3 enhancements (Continued)
EnhancementDescriptionSee...
Default Originate Route for BGPIn this release, if a default route is not present in
the IP routing table, the user can configure a
major route to be used for forwarding packets to
all unknown destination. Starting with release
02.3.00a.
Changes to BGP4 Path Selection
for a Route
BGP allowas-in command The allowas-in command has been added to this
Default Route ECMPThis feature allows for load distribution of traffic
Transparent Firewall Mode The Transparent Firewall mode feature allows
With this release of Multi-Service IronWare, the
process by which BGP selects a path has
changed. The following procedure replaces the
procedure described in the BigIron RX Series Configuration Guide.
release to allow you to set a parameter that
disables the BGP AS_PATH check function for
routes learned from a specified location.
among the available default route next-hops.
users to insert a Firewall in front of their existing
network without changing the statically defined
IP addresses of their network-connected devices.
This will allow the users to permit selected
devices from a subnet to cross the firewall while
access to other devices on the same subnet are
denied.
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
BGP4 (IPv4 and IPv6)”
Section:“Originating the
default route”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
BGP4 (IPv4 and IPv6)”
Section:“How BGP4
selects a path for a route”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring
BGP4 (IPv4 and IPv6)”
Section:“Configuring a
switch to allow routes with
its own AS number”
Book: BigIron RX Series
Configuration Guide
Chapter: “Configuring IP”
Section:“Default route
ECMP”
Book: BigIron RX Series
Configuration Guide
Chapter: “VLANs”
Section:“Transparent
firewall mode”
IP multicast enhancements
TABLE 16IP multicast enhancements
EnhancementDescriptionSee...
MBGP Multiprotocol BGP allows for the inclusion of
information other than IPv4 routes via BGP
packets is available in this release.
Multicast Source Discover Protocol
(MSDP)
BigIron RX Series Configuration Guidelxi
53-1001986-01
This release supports the Multicast Source
Discovery Protocol (MSDP). It is used by
Protocol Independent Multicast (PIM) Sparse
routers to exchange routing information for
PIM Sparse multicast groups across PIM
Sparse domains.
Discovery Protocol (MSDP) Mesh Groups. This
feature allows you to connect several RPs to
each other which reduces the forwarding of
SA messages within a domain.
IGMP v3IGMP v3 provides selective filtering of traffic
based on traffic source.
PIM-SSM v4PIM-SSM is a routing protocol used for source
specific multicast groups and is used in
conjunction with IGMPv3
IGMP v2/v3 Fast Leave IGMP Fast leave allows clients to leave groups
without the three second waiting period, if
certain conditions are met.
MLDv1/v2MLDv2 supports source filtering, and the
ability of a node to send reports on traffic that
is from a specific address source or from all
multicast addresses except the specified
address sources.
Book: BigIron RX Series Configuration Guide
Chapter:“Configuring IP
Multicast Protocols”
Section:“Configuring MSDP
mesh group”
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring IP
Multicast Protocols”
Section:“IGMP v3”
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring IP
Multicast Protocols”
Section:“PIM-SSMv4”
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring IP
Multicast Protocols”
Section:“Enabling
membership tracking and
fast leave”
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring IPv6
Multicast Features”
Section:“MLD version
distinctions”
IP service, security, and Layer 4 enhancements
TABLE 17IP service, security, and Layer 4 enhancements
EnhancementDescriptionSee...
Root Guard This is a security feature that allows a port to
run STP but not allow the connected device to
become the Root.
BPDU Guard BPDU Guard is an extension to the port fast
feature. If a port is in port fast mode of
operation and a BDPU is received, the port is
put into the disabled mode.
lxiiBigIron RX Series Configuration Guide
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring
Spanning Tree Protocol”
Section:“STP root guard”
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring
Spanning Tree Protocol”
Section:“Spanning Tree
Protocol (STP) BPDU guard”
53-1001986-01
TABLE 17IP service, security, and Layer 4 enhancements (Continued)
EnhancementDescriptionSee...
Port Security MAC Violation Limit This feature provides protection against
physical link instability. It allows a user to
configure it to keep a port in a down state in
cases where the port has experienced some
number of state transitions within a configured
amount of time.
IPv6 DHCP GatewayYou can allow a DHCP client to send a message
to a DHCP server by using a DHCP relay agent.
Book: BigIron RX Series
Configuration Guide
Chapter:“Using the MAC Port
Security Feature and
Transparent Port Flooding”
Section:“Restricting
interface access”
Book: BigIron RX Series
Configuration Guide
Chapter:“Inspecting and
Tra cki ng D HCP Pac kets”
Section:“DHCP relay agent
information (DHCP option
82)”
Network management
TABLE 18Network management
EnhancementDescriptionSee...
IPv6 Management TFTP, SSH,
Telnet, AAA, and WEB
You can perform system management tasks for
the BigIron RX using the TFTP, telnet, AAA, and
Secure Shell (SSH).
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring Basic
IPv6 Connectivity”
Enhancements in release 02.2.01
Hardware enhancements
TABLE 19Hardware enhancements
EnhancementDescriptionSee page
New Hardware SupportThe following new hardware is supported with the
02.2.01 software release for the BigIron RX:
• Management module with 2 GB of memory
• 24-port 100/1000 Mbps SFP Ethernet interface
module
• 48-port 1 Gbps Copper Ethernet interface module
• DC Power Supply
• New fan controller
Book: Brocade BigIron RX
Series Installation Guide
BigIron RX Series Configuration Guidelxiii
53-1001986-01
Layer 2 enhancements
TABLE 20Layer 2 enhancements
EnhancementDescriptionSee page
VLAN Byte AccountingWith this release, you can configure a VLAN to account
for the number of bytes received by all the member
ports.
Super Aggregated VLANs
(SAV)
Enhancement to the lacp
system-priority command
Multiple VLANs can be aggregated within another VLAN
to allow you to construct Layer 2 paths and channels.
The lacp system-priority command has been moved
from the interface configuration level to the global
configuration level.
Book: BigIron RX Series
Configuration Guide
Chapter:“VLANs”
Section:“VLAN byte
accounting”
Book: BigIron RX Series
Configuration Guide
Chapter:“VLANs”
Section:“Configuring
super aggregated VLANs”
Book: BigIron RX Series
Configuration Guide
Chapter: See the
Dynamic Link
Aggregation chapter in
the BigIron RX Series Configuration Guide Versions 02.5.00 and
earlier.
Section:Configuring Link
Aggregation Parameters
Layer 3 enhancements
TABLE 21Layer 3 enhancements
EnhancementDescriptionSee page
Graceful RestartWith this release, you can enable Graceful Restart
for OSPF and BGP
BGP Null0 RoutingWith this release, BGP can use null0 to resolve the
next hop and install null0 BGP routes to the routing
table
GRE IP TunnelingThis release supports creation of a GRE tunnel
across an IP network.
lxivBigIron RX Series Configuration Guide
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring
OSPF Version 2 (IPv4)”
and “Configuring BGP4
(IPv4 and IPv6)”
Section: “OSPF graceful
restart” and “Graceful
restart in BGP”
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring
BGP4 (IPv4 and IPv6)”
Section:“BGP Null0
routing”
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring IP”
Section:“GRE IP tunnel”
53-1001986-01
TABLE 21Layer 3 enhancements (Continued)
EnhancementDescriptionSee page
OSPF point-to-pointOSPF point-to-point eliminates the need for
Designated and Backup Designated routers,
allowing for faster convergence of the network.
Neighbor Local ASNeighbor Local Autonomous System (AS) feature
allows a router that is a member of one AS to appear
to be a member of another AS.
Full AS Path information in
sFlow
Policy Based RoutingPolicy-Based Routing (PBR) allows you to use ACLs
In this release, sFlow packets now contain full AP
Path information.
and route maps to selectively modify and route IP
packets in hardware. The ACLs classify the traffic.
Route maps that match on the ACLs set routing
attributes for the traffic.
Multicast enhancement
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring
OSPF Version 2 (IPv4)”
Section: “OSPF
point-to-point links”
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring
BGP4 (IPv4 and IPv6)”
Section:“Neighbor
local-AS”
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring
sFlow”
Section: “Extended
gateway information”
Book: BigIron RX Series
Configuration Guide
Chapter:“Policy-Based
Routing”
TABLE 22Multicast enhancement
EnhancementDescriptionSee page
IGMP Snooping The BigIron RX supports IGMP snooping. Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring IP
Multicast Traffic Reduction”
Section: “Enabling IP
multicast traffic reduction”
Security enhancements
TABLE 23Security enhancements
EnhancementDescriptionSee page
Multi-device Port
Authentication
802.1x Port Security This release allows you to enable 802.1X port
Multi-device port authentication is now supported on
the BigIron RX.
security and multi-device port authentication on the
same interface.
Book: BigIron RX Series
Configuration Guide
Chapter:“Using the MAC
Port Security Feature and
Transparent Port Flooding”
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring
802.1x Port Security”
BigIron RX Series Configuration Guidelxv
53-1001986-01
TABLE 23Security enhancements (Continued)
EnhancementDescriptionSee page
Port Security MAC DenyWith this release, you can configure deny mac
addresses on a global level or on a per port level.
IP Fragmentation ProtectionFragmented IP packets with undersized fragments
and overlapping fragments are dropped.
IP Option Attack PreventionPackets with IP options in their header are
automatically dropped. Enabling the ip
ip-option-process command allows the device to
process packets that use IP options.
IP Receive ACLsYou can use IPv4 ACLs to filter the packets intended
for the management processor to protect the
management module from being overloaded with
heavy traffic that was sent to one of the Layer 3
Switch IP interfaces.
Static Route TaggingStatic routes can be configured with tag values. Book: BigIron RX Series
MTU enhancements for IPv4 In this release, you can configure IPv4 MTU to be
greater than 1500 bytes.
Enhancements to passwords The following have been implemented to enhance the
password features in the BigIron RX:
Book: BigIron RX Series
Configuration Guide
Chapter:“Using the MAC
Port Security Feature and
Transparent Port Flooding”
number of login attempts and have not logged in
successfully.
• Previous passwords used are now stored in the
CLI. When users change their password, they
must select a password that has not been
stored in the CLI.
• A password can now be set to expire
lxviBigIron RX Series Configuration Guide
53-1001986-01
TABLE 23Security enhancements (Continued)
EnhancementDescriptionSee page
Port Security EnhancementsYou can specify how many packets from denied MAC
addresses can be received on a port in a one-second
interval before the BigIron RX shuts the port down.
Larger SSHv2 Crypto Key The size of the SSH v2 crypto key in this release is
larger than crypto key in previous releases.
Therefore, after upgrading to this release, you must
clear the existing crypto key, then regenerate a new
one.
Book: BigIron RX Series
Configuration Guide
Chapter:“Using the MAC
Port Security Feature and
Transparent Port Flooding”
Section:“Defining security
violation actions”
Book: Brocade BigIron RX
Series Installation Guide
System enhancements
TABLE 24System enhancements
EnhancementDescriptionSee page
Unified software image for
software upgrades
Change to the SNMP MIB
objects for trunking
Once the BigIron RX software has been upgraded to
Release 02.2.01, you can use the unified software
image to upgrade the device’s software.
The snMSTrunkTable has been replaced by
snMSTrunkIfTable
Book: Brocade BigIron RX
Series Installation Guide
Book: MIB Reference
Enhancements in release 02.2.00g
TABLE 25Summary of enhancements in 02.2.00g
EnhancementDescriptionSee page
New Hardware SupportThe following new hardware is supported with the 02.2.01
software release for the BigIron RX:
• 2-port 10 Gigabit Ethernet port module
• DC Power Supply
Book: Brocade BigIron RX
Series Installation Guide
BigIron RX Series Configuration Guidelxvii
53-1001986-01
Enhancements in release 02.2.00
TABLE 26Summary of emhancements in 02.2.00
EnhancementDescriptionSee page
Quality of Service (QoS)
Support
Rate-limiting SupportRate-limiting can be performed based on ACL matching of
QoS support on the BigIron RX is different than for the
BigIron MG8.
flows and L2/L3 priority. It operates as on the BigIron
MG8 except:
• Only Inbound rate limiting is supported.
• 802.1p packet priority is used by default
• Rate limit accounting is available if WRED is not
enabled.
CLI changes required for these differences are described
in the page referenced on the next column.
Hardware Forwarding of
Packets
Switching and Routing
Packets
No Support for Core
Device to Copy the QoS
Priority
Trunk Support On the BigIron RX, the switch, server, and per-packet
Multicast Entry Limit1542 multicast entries are limited to IPv4 1542 entries
WAN PHY Mode SupportThis release supports WAN PHY Mode per 10 GB Ethernet
Default behavior on BigIron RX is hardware unknown
unicast and multicast flooding.
Operation of packet switching and routing have changed
with the BigIron RX. Details are described in the page
referenced on the next column.
This feature is not supported on BigIron RX. N/A
options for trunking are not supported.
provided every group has only one destination.
port.
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring
Quality of Service”
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring
Traffic Reduction”
Book: BigIron RX Series
Configuration Guide
Chapter:“VLANs”
Section:“Hardware
flooding for Layer 2
multicast and broadcast
packets”
Book: BigIron RX Series
Configuration Guide
Chapter:“VLANs”
Section:“Unknown
unicast flooding on VLAN
ports”
N/A
N/A
Book: BigIron RX Series
Configuration Guide
Chapter:“Configuring
Interface Parameters”
Section:“Enabling WAN
PHY mode support”
For further information about new features and documentation updates for this release, refer to
the Knowledge Portal at kp.foundrynet.com.
lxviiiBigIron RX Series Configuration Guide
53-1001986-01
Document conventions
NOTE
This section describes text formatting conventions and important notice formats used in this
document.
Text formatting
The narrative-text formatting conventions that are used are as follows:
bold textIdentifies command names
italic textProvides emphasis
code textIdentifies CLI output
For readability, command names in the narrative portions of this guide are presented in bold: for
example, show version.
Identifies the names of user-manipulated GUI elements
Identifies keywords
Identifies text to enter at the GUI or CLI
Identifies variables
Identifies document titles
Command syntax conventions
Command syntax in this manual follows these conventions:
command and
parameters
[ ]Optional parameter.
variableVariables are printed in italics enclosed in angled brackets < >.
...Repeat the previous element, for example “member[;member...]”
|Choose from one of the parameters.
Commands and parameters are printed in bold.
Notes, cautions, and danger notices
The following notices and statements are used in this manual. They are listed below in order of
increasing severity of potential hazards.
A note provides a tip, guidance or advice, emphasizes important information, or provides a reference
to related information.
BigIron RX Series Configuration Guidelxix
53-1001986-01
CAUTION
A Caution statement alerts you to situations that can be potentially hazardous to you or cause
DANGER
NOTE
damage to hardware, firmware, software, or data.
A Danger statement indicates conditions or situations that can be potentially lethal or extremely
hazardous to you. Safety labels are also attached directly to products to warn of these conditions
or situations.
Notice to the reader
This document may contain references to the trademarks of the following corporations. These
trademarks are the properties of their respective companies and corporations.
These references are made for informational purposes only.
CorporationReferenced Trademarks and Products
HPH P Top Too ls
Related publications
The following Brocade documents supplement the information in this guide:
• Brocade BigIron RX Series Installation Guide.
• IronWare MIB Reference.
For the latest edition of these documents, which contain the most up-to-date information, go to
my.Brocade.com, click the Product Documentation tab, then click on the link to the Knowledge
Portal (KP)
Getting technical help or reporting errors
Brocade is committed to ensuring that your investment in our products remains cost-effective. If
you need assistance or find errors in the manuals, contact Brocade using one of the following
options.
lxxBigIron RX Series Configuration Guide
53-1001986-01
Web access
The Knowledge Portal (KP) contains the latest version of this guide and other user guides for the
product. You can also report errors on the KP.
Log in to my.Brocade.com, click the Product Documentation tab, then click on the link to the
Knowledge Portal (KP). Then click on Cases > Create a New Ticket to report an error. Make sure you
specify the document title in the ticket description.
E-mail and telephone access
Go to http://www.brocade.com/services-support/index.page for the latest e-mail and telephone
contact information.
BigIron RX Series Configuration Guidelxxi
53-1001986-01
This user guide assumes that an IP address and default gateway have been assigned to the BigIron
RX when it was installed. If you need to assign an IP address or default gateway to the device, refer
to the Brocade BigIron RX Series Installation Guide.
1
Once an IP address is assigned to the device’s management port, you can access the CLI through a
PC or terminal attached to the management module’s serial (Console) port or
10BaseT/100BaseTX Ethernet (management) port, or from a Telnet or SSH connection to the PC or
terminal.
You can initiate a local Telnet, SSH or SNMP connection by specifying the management port’s IP
address.
The commands in the CLI are organized into the following levels:
• User EXEC – Lets you display information and perform basic tasks such as pings and
traceroutes.
• Privileged EXEC – Lets you use the same commands as those at the User EXEC level plus
configuration commands that do not require saving the changes to the system-config file.
• CONFIG – Lets you make configuration changes to the device. To save the changes across
software reloads and system resets, you need to save them to the system-config file. The
CONFIG level contains sub-levels for individual ports, for VLANs, for routing protocols, and other
configuration areas.
By default, any user who can open a direct or Telnet connection to a BigIron RX Switch can access
all these CLI levels. To secure access, you can configure Enable passwords or local user accounts,
or you can configure the device to use a RADIUS or TACACS o rTACACS+ server for authentication.
Refer to the Security Guide.
BigIron RX Series Configuration Guide1
53-1001986-01
Logging on through the CLI
1
On-line help
To display a list of available commands or command options, enter “?” or press Tab. If you have not
entered part of a command at the command prompt, all the commands supported at the current
CLI level are listed. If you enter part of a command, then enter “?” or press Tab, the CLI lists the
options you can enter at this point in the command string.
If you enter an invalid command followed by ?, a message appears indicating the command was
unrecognized.
BigIron RX(config)# rooter ip
Unrecognized command
Command completion
The CLI supports command completion, so you do not need to enter the entire name of a command
or option. As long as you enter enough characters of the command or option name to avoid
ambiguity with other commands or options, the CLI understands what you are typing.
Scroll control
By default, the CLI uses a page mode to paginate displays that are longer than the number of rows
in your terminal emulation window. For example, if you display a list of all the commands at the
global CONFIG level but your terminal emulation window does not have enough rows to display
them all at once, the page mode stops the display and lists your choices for continuing the display.
default-vlan-id
enable
enable-acl-counter
end
exit
--More--, next page: Space, next line: Return key, quit: Control-c
The software provides the following scrolling options:
• Press the Space bar to display the next page (one screen at time).
• Press the Return or Enter key to display the next line (one line at a time).
• Press Ctrl-C cancel the display.
2BigIron RX Series Configuration Guide
53-1001986-01
EXEC commands
1
Line editing commands
The CLI supports the following line editing commands. To enter a line-editing command, use the
CTRL-key combination for the command by pressing and holding the CTRL key, then pressing the
letter associated with the command.
TABLE 27 CLI line-editing commands
Ctrl-key combinationDescription
Ctrl-AMoves to the first character on the command line.
Ctrl-BMoves the cursor back one character.
Ctrl-CEscapes and terminates command prompts and ongoing tasks (such as
lengthy displays), and displays a fresh command prompt.
Ctrl-DDeletes the character at the cursor.
Ctrl-EMoves to the end of the current command line.
Ctrl-FMoves the cursor forward one character.
Ctrl-KDeletes all characters from the cursor to the end of the command line.
Ctrl-L; Ctrl-RRepeats the current command line on a new line.
Ctrl-NEnters the next command line in the history buffer.
Ctrl-PEnters the previous command line in the history buffer.
Ctrl-U; Ctrl-XDeletes all characters from the cursor to the beginning of the command
line.
Ctrl-WDeletes the last word you typed.
Ctrl-ZMoves from any CONFIG level of the CLI to the Privileged EXEC level; at the
Privileged EXEC level, moves to the User EXEC level.
EXEC commands
There are two different levels of EXEC commands, the User Level and the Privileged Level.
User level
The User level commands are at the top of the CLI hierarchy. These are the first commands that you
have access to when connected to the device through the CLI. For example, when you first connect
to the device, you may see the following prompt.
BigIron RX>
The “BigIron RX“part of the prompt is configurable. Your system may display a different string.
At this level, you can view basic system information and verify connectivity but cannot make any
changes to the device configuration. To make changes to the configuration, you must move to
other levels of the CLI hierarchy. such as the Privileged EXEC level.
Privileged EXEC level
Commands at the Privileged EXEC level enable you to transfer and store software images and
configuration files between the network and the system, and review the configuration.
BigIron RX Series Configuration Guide3
53-1001986-01
CONFIG commands
1
You reach this level by entering the enable [<password>] or enable <username> <password> at
the User EXEC level.
BigIron RX>enable
or
BigIron RX>enable user1 mypassword
After entering the enable command, you see the following prompt.
BigIron RX>#.
The prompt indicates that you are at the Privilege EXEC level.
When you are at the Privilege EXEC level, you can enter commands that are available at that level.
It is also at this level where you enter the configure terminal command to Global Configuration
level.
Global level
The global CONFIG level allows you to globally apply or modify parameters for ports on the device.
You reach this level by entering configure terminal at the privileged EXEC level.
The prompt changes to the Global Configuration level.
BigIron RX(config)#
CONFIG commands
CONFIG commands modify the configuration of a device. Once you are at the Global Configuration
level, you can enter commands to configure the features in the device. This section describes the
following CONFIG CLI levels.
Redundancy level
This redundancy level allows you to configure redundancy parameters for redundant management
modules. You reach this level by entering the redundancy command at the global CONFIG level.
Interface level
The interface level allows you to assign or modify specific port parameters on a port-by-port basis.
You reach this level by entering the following at the global CONFIG level:
• interface ethernet <slot/port>
• interface loopback <num>
• interface management <portnum>
• interface ve <num>
• interface tunnel <tunnel_id>
• interface group-ve <vlan_group_id>
4BigIron RX Series Configuration Guide
53-1001986-01
CONFIG commands
1
Trunk level
The trunk level allows you to change parameters for statically-configured trunk groups. You reach
this level by entering a trunk command with the appropriate port parameters.
Router RIP level
The RIP level allows you to configure parameters for the RIP routing protocol. You reach this level by
entering the router rip command at the global CONFIG level.
Router OSPF level
The OSPF level allows you to configure parameters for the OSPF routing protocol. You reach this
level by entering the router ospf command at the global CONFIG level.
BGP level
The BGP level allows you to configure Border Gateway Protocol version 4 (BGP4) features. You
reach this level by entering the router bgp command at the global CONFIG level.
Global BGP and BGP4 Unicast address family level
The global BGP and BGP4 unicast address family levels are present only on Brocade devices that
support IPv6. The global BGP level allows you to configure the BGP routing protocol. The BGP4
unicast address family level allows you to configure a BGP4 unicast route. For backward
compatibility, you can currently access BGP4 unicast address family commands at both global BGP
configuration and BGP4 unicast address family configuration levels. Therefore, the global BGP and
BGP4 unicast address family commands are documented together.
You reach the global BGP level by entering the router bgp command at the global CONFIG level. You
reach the BGP4 unicast address family level by entering the address-family ipv4 unicast command
at the global BGP level.
BGP4 multicast address family level
The BGP4 multicast address family level allows you to configure BGP4 multicast routes. You reach
this level by entering the address-family ipv4 multicast command at the global BGP, BGP4 unicast
address family, or IPv6 BGP unicast address family levels.
Router DVMRP level
The DVMRP level allows you to configure details for the DVMRP multicast protocol. You reach this
level by entering the router dvmrp command at the global CONFIG level.
Router PIM level
The PIM level allows you to configure parameters for the Protocol Independent Multicast (PIM)
routing protocol. You reach this level by entering the router pim command at the global CONFIG
level.
BigIron RX Series Configuration Guide5
53-1001986-01
CONFIG commands
1
Route Map level
The Route Map level allows you to configure parameters for a BGP4 route map. You reach this level
by entering the route-map <name> command at the global CONFIG level.
Router VRRP level
The VRRP level allows you to configure parameters for the Virtual Router Redundancy Protocol
(VRRP). You reach this level by entering the router vrrp command at the global CONFIG level, then
entering the ip vrrp vrid <num> command at the interface configuration level.
Router VRRPE level
The VRRPE level allows you to configure parameters for VRRP Extended. You reach this level by
entering the router vrrp-extended command at the global CONFIG level, then entering the ip
vrrp-extended vrid <num> command at the interface configuration level.
VLAN level
Policy-based VLANs allow you to assign VLANs to a protocol, port, or 802.1q tags.
You reach this level by entering the vlan <vlan-id> command at the Global CONFIG Level.
Metro ring level
Metro rings provide Layer 2 connectivity and fast failover in ring topologies.
You reach this level by entering the metro-ring <ring-id> command at the Global CONFIG Level.
VSRP level
The VSRP level allows you to configure parameters for the Virtual Switch Redundancy Protocol
(VSRP). You reach this level by entering the vsrp vrid <num> command at the VLAN configuration
level, then entering the vsrp vrid <num> command at the VLAN configuration level.
Topology group level
A topology group enables you to control the Layer 2 protocol configuration and Layer 2 state of a set
of ports in multiple VLANs based on the configuration and states of those ports in a single master
VLAN. One instance of the Layer 2 protocol controls all the VLANs.
You reach this level by entering the topology-group <group-id> command at the Global CONFIG
Level.
802.1x port security level
The 802.1x port security level allows you to configure the 802.1x port security. You reach this level
by entering the dot1x-enable command at the at the Global level.
6BigIron RX Series Configuration Guide
53-1001986-01
MAC port security level
NOTE
The MAC port security level allows you to configure the port security feature. You reach this level by
entering the global-port-security command at the at the Global or Interface levels.
Accessing the CLI
The CLI can be accessed through both serial and Telnet connections. For initial log on, you must
use a serial connection. Once an IP address is assigned, you can access the CLI through Telnet.
Once connectivity to the device is established, you will see the following prompt.
BigIron RX>
When accessing the CLI through Telnet, you maybe prompted for a password. By default, the
password required is the password you enter for general access at initial setup. You also have the
option of assigning a separate password for Telnet access with the enable telnet password
<password> command, found at the Global Level.
At initial log on, all you need to do is type enable at the prompt, then press Return. You only need to
enter a password after a permanent password is entered at the Global CONFIG Level of the CLI.
Accessing the CLI
1
If you install switch code on a router, the command prompt begins with "SW-" to indicate the software
change. This is true even if you change the system name.
To reach the Global CONFIG Level, the uppermost level of the CONFIG commands, enter the
following commands:
• BigIron RX> enable
• BigIron RX# configure terminal
• BigIron RX(config)#
You can then reach all other levels of the CONFIG command structure from this point.
The CLI prompt will change at each level of the CONFIG command structure to easily identify the
current level.
User Level commands
Privileged Level-EXEC commands
Global Level-CONFIG commands
BigIron RX Series Configuration Guide7
53-1001986-01
The CLI prompt at the interface level includes the port speed. The speed is one of the following.
BigIron RX(config-if–e100-5/1)# – The interface is a 10/100 port.
BigIron RX(config-if–e1000-5/1)# – The interface is a Gigabit port.
For simplicity, the port speeds sometimes are not shown in example Interface level prompts in this
manual.
Navigating among command levels
To reach other CLI command levels, you need to enter certain commands. At each level there is a
launch command that allows you to move either up or down to the next level.
CLI command structure
Many CLI commands may require textual or numeral input as part of the command.
Required or optional fields
8BigIron RX Series Configuration Guide
These fields are either required or optional depending on how the information is bracketed. For
clarity, a few CLI command examples are explained below.
When an item is bracketed with “< >” symbols, the information requested is a variable and
required.
When an item is not enclosed by “< >” or “[ ]” symbols, the item is a required keyword.
When an item is bracketed with “[ ]” symbols, the information requested is optional.
53-1001986-01
Searching and filtering output
1
Optional fields
When two or more options are separated by a vertical bar, “| “, you must enter one of the options
as part of the command.
Syntax: priority normal | high
For example, the "normal | high" entry in the Syntax above means that priority can be either priority
normal or priority high. The command in the syntax above requires that you enter either normal or
high as part of the command.
List of available options
To get a quick display of available options at a CLI level or for the next option in a command string,
enter a question mark (?) at the prompt or press TAB.
To view all available commands at the user EXEC level, enter the following or press TAB at the User
EXEC CLI level.
You can filter CLI output from show commands and at the --More-- prompt. You can search for
individual characters, strings, or construct complex regular expressions to filter the output.
Searching and filtering output from show commands
You can filter output from show commands to display lines containing a specified string, lines that
do not contain a specified string, or output starting with a line containing a specified string. The
search string is a regular expression consisting of a single character or string of characters. You can
use special characters to construct complex regular expressions. Refer to “Using special characters
in regular expressions” on page 12 for information on special characters used with regular
expressions.
BigIron RX Series Configuration Guide9
53-1001986-01
Searching and filtering output
NOTE
1
Displaying lines containing a specified string
The following command filters the output of the show interface command for port 3/11 so it
displays only lines containing the word “Internet”. This command can be used to display the IP
address of the interface.
BigIron RX# show interface e 3/11 | include Internet
Internet address is 192.168.1.11/24, MTU 1518 bytes, encapsulation ethernet
Syntax: <show-command> | include <regular-expression>
The vertical bar ( | ) is part of the command.
Note that the regular expression specified as the search string is case sensitive. In the example
above, a search string of “Internet” would match the line containing the IP address.
Displaying lines that do not contain a specified string
The following command filters the output of the show who command so it displays only lines that
do not contain the word “closed”. This command can be used to display open connections to the
Brocade device.
BigIron RX# show who | exclude closed
Console connections:
established
you are connecting to this session
2 seconds in idle
Telnet connections (inbound):
1 established, client ip address 192.168.9.37
27 seconds in idle
Telnet connection (outbound):
SSH connections:
Displaying lines starting with a specified string
The following command filters the output of the show who command so it displays output starting
with the first line that contains the word “SSH”. This command can be used to display information
about SSH connections to the device.
BigIron RX# show who | begin SSH
SSH connections:
1 established, client ip address 192.168.9.210
7 seconds in idle
2 closed
3 closed
4 closed
5 closed
Syntax: <show-command> | begin <regular-expression>
Searching and filtering output at the --More-- prompt
The --More-- prompt is displayed when output extends beyond a single page. From this prompt, you
can press the Space bar to display the next page, the Return or Enter key to display the next line, or
Ctrl-C or Q to cancel the display. You can also search and filter output from this prompt.
10BigIron RX Series Configuration Guide
53-1001986-01
Searching and filtering output
BigIron RX# ?
append Append one file to another
attrib Change file attribute
boot Boot system from bootp/tftp server/flash image
cd Change current working directory
chdir Change current working directory
clear Clear table/statistics/keys
clock Set clock
configure Enter configuration mode
copy Copy between flash, tftp, config/code
cp Copy file commands
debug Enable debugging functions (see also 'undebug')
delete Delete file on flash
dir List files
dm test commands
dot1x 802.1x
erase Erase image/configuration files from flash
exit Exit Privileged mode
fastboot Select fast-reload option
force-sync-standby Sync active flash (pri/sec/mon/startup config/lp images)
to standby
format Format PCMCIA card
hd Hex dump
ipc IPC commands
--More--, next page: Space, next line: Return key, quit: Control-c
--More--, next page: Space, next line: Return key, quit: Control-c
/telnet
searching...
telnet Telnet by name or IP address
terminal Change terminal settings
traceroute TraceRoute to IP node
undelete Recover deleted file
whois WHOIS lookup
write Write running configuration to flash or terminal
--More--, next page: Space, next line: Return key, quit: Control-c
+telnet
filtering...
telnet Telnet by name or IP address
1
At the --More-- prompt, you can press the forward slash key ( / ) and then enter a search string. The
Brocade device displays output starting from the first line that contains the search string, similar to
the begin option for show commands.
The results of the search are displayed.
BigIron RX Series Configuration Guide11
53-1001986-01
To display lines containing only a specified search string (similar to the include option for show
commands) press the plus sign key ( + ) at the --More-- prompt and then enter the search string.
The filtered results are displayed.
To display lines that do not contain a specified search string (similar to the exclude option for show
commands) press the minus sign key ( - ) at the --More-- prompt and then enter the search string.
Searching and filtering output
--More--, next page: Space, next line: Return key, quit: Control-c
-telnet
filtering...
sync-standby Sync active flash (pri/sec/mon/startup config/lp images)
to standby if different
terminal Change terminal settings
traceroute TraceRoute to IP node
undelete Recover deleted file
whois WHOIS lookup
write Write running configuration to flash or terminal
1
The filtered results are displayed.
As with the commands for filtering output from show commands, the search string is a regular
expression consisting of a single character or string of characters. You can use special characters
to construct complex regular expressions. Refer to “Using special characters in regular
expressions” on page 12 for information on special characters used with regular expressions.
Using special characters in regular expressions
You use a regular expression to specify a single character or multiple characters as a search string.
In addition, you can include special characters that influence the way the software matches the
output against the search string. These special characters are listed in the following table.
TABLE 28 Special characters for regular expressions
CharacterOperation
.The period matches on any single character, including a blank space.
For example, the following regular expression matches “aaz”, “abz”, “acz”, and so on, but not just
“az”:
a.z
*The asterisk matches on zero or more sequential instances of a pattern.
For example, the following regular expression matches output that contains the string “abc”,
followed by zero or more Xs:
abcX*
+The plus sign matches on one or more sequential instances of a pattern.
For example, the following regular expression matches output that contains "de", followed by a
sequence of “g”s, such as “deg”, “degg”, “deggg”, and so on:
deg+
?The question mark matches on zero occurrences or one occurrence of a pattern.
For example, the following regular expression matches output that contains "dg" or "deg":
de?g
NOTE: Normally when you type a question mark, the CLI lists the commands or options at that CLI
level that begin with the character or string you entered. However, if you enter Ctrl-V and
then type a question mark, the question mark is inserted into the command line, allowing
you to use it as part of a regular expression.
^A caret (when not used within brackets) matches on the beginning of an input string.
For example, the following regular expression matches output that begins with “deg”:
^deg
12BigIron RX Series Configuration Guide
53-1001986-01
Searching and filtering output
TABLE 28 Special characters for regular expressions (Continued)
CharacterOperation
$A dollar sign matches on the end of an input string.
For example, the following regular expression matches output that ends with “deg”:
deg$
_An underscore matches on one or more of the following:
• , (comma)
• { (left curly brace)
• } (right curly brace)
• ( (left parenthesis)
• ) (right parenthesis)
• The beginning of the input string
• The end of the input string
• A blank space
For example, the following regular expression matches on “100” but not on “1002”, “2100”, and
so on.
[ ]Square brackets enclose a range of single-character patterns.
For example, the following regular expression matches output that contains “1”, “2”, “3”, “4”, or
“5”:
[1-5]
You can use the following expression symbols within the brackets. These symbols are allowed
only inside the brackets.
• ^ – The caret matches on any characters except the ones in the brackets. For example, the
following regular expression matches output that does not contain “1”, “2”, “3”, “4”, or “5”:
[^1-5
• - The hyphen separates the beginning and ending of a range of characters. A match occurs if
any of the characters within the range is present. See the example above.
|A vertical bar separates two alternative values or sets of values. The output can match one or the
other value.
For example, the following regular expression matches output that contains either “abc” or “defg”:
abc|defg
( )Parentheses allow you to create complex expressions.
For example, the following complex expression matches on “abc”, “abcabc”, or “defg”, but not on
“abcdefgdefg”:
((abc)+)|((defg)?)
1
If you want to filter for a special character instead of using the special character as described in the
table above, enter “\” (backslash) in front of the character. For example, to filter on output
containing an asterisk, enter the asterisk portion of the regular expression as “\*”.
BigIron RX# show ip route bgp | include \*
Allowable characters for LAG names
When creating a LAG name, you can use spaces in a file or subdirectory name if you enclose the
name in double quotes. For example, to specify a subdirectory name that contains spaces, enter a
string such as the following: “a long subdirectory name”. The maximum length for a string is 64
characters.
The following characters are valid in file names:
• All upper and lowercase letters
BigIron RX Series Configuration Guide13
53-1001986-01
Searching and filtering output
NOTE
1
Any of the following special characters are valid:
• All digits
• $
• %
• '
• -
• _
• @
• ~
• `
• !
• (
• )
• {
• }
• ^
• #
• &
Syntax shortcuts
A command or parameter can be abbreviated as long as enough text is entered to distinguish it
from other commands at that level. For example, given the possible commands copy tftp… and
config tftp…, possible shortcuts are cop tftp and con tftp respectively. In this case, co does not
properly distinguish the two commands.
Saving configuration changes
You can make configuration changes while the device is running. The type of configuration change
determines whether or not it becomes effective immediately or requires a save to flash (write
memory) and reset of the system (reload), before it becomes active.
This approach in adopting configuration changes:
• Allows you to make configuration changes to the operating or running configuration of the
device to address a short-term requirement or validate a configuration without overwriting the
permanent configuration file, the startup configuration, that is saved in the system flash, and;
• Ensures that dependent or related configuration changes are all cut in at the same time.
In all cases, if you want to make the changes permanent, you need to save the changes to flash
using the write memory command. When you save the configuration changes to flash, this will
become the configuration that is initiated and run at system boot.
Most configuration changes are dynamic and thus do not require a software reload. If a command
requires a software reload to take effect, the documentation states this.
14BigIron RX Series Configuration Guide
53-1001986-01
Chapter
NOTE
Getting Familiar With the BigIron RX Series Switch
Management Applications
How to manage BigIron RX Series switch
This chapter describes the different applications you can use to manage the BigIron RX Series
Switch. The BigIron RX Series Switch supports the same management applications as other
Brocade devices.
As with other Brocade devices, you can manage a BigIron RX Series Switch using any of the
following applications:
• Command Line Interface (CLI) – a text-based interface accessible directly from a PC or terminal
attached to the management module’s serial (Console) port or 10BaseT/100BaseTX Ethernet
(management) port, or from a Telnet connection to the PC or terminal.
• Web management interface – A GUI-based management interface accessible through an HTTP
The following section describes how to log on to these applications.
2
Logging on through the CLI
Once an IP address is assigned to the BigIron RX Series Switch’s management port, you can access
the CLI through a PC or terminal attached to the management module’s serial (Console) port or
10BaseT/100BaseTX Ethernet (management) port, or from a Telnet or SSH connection to the PC or
terminal.
You can initiate a local Telnet, SSH or SNMP connection by specifying the management port’s IP
address.
The commands in the CLI are organized into the following levels:
• User EXEC – Lets you display information and perform basic tasks such as pings and
traceroutes.
• Privileged EXEC – Lets you use the same commands as those at the User EXEC level plus
configuration commands that do not require saving the changes to the system-config file.
• CONFIG – Lets you make configuration changes to the device. To save the changes across
software reloads and system resets, you need to save them to the system-config file. The
CONFIG level contains sub-levels for individual ports, for VLANs, for routing protocols, and other
configuration areas.
By default, any user who can open a direct or Telnet connection to a BigIron RX Series Switch can
access all these CLI levels. To secure access, you can configure Enable passwords or local user
accounts, or you can configure the device to use a RADIUS or TACACS and TACACS+ server for
authentication. Refer to the Security Guide.
BigIron RX Series Configuration Guide15
53-1001986-01
Logging on through the CLI
2
On-line help
To display a list of available commands or command options, enter “?” or press Tab. If you have not
entered part of a command at the command prompt, all the commands supported at the current
CLI level are listed. If you enter part of a command, then enter “?” or press Tab, the CLI lists the
options you can enter at this point in the command string.
If you enter an invalid command followed by ?, a message appears indicating the command was
unrecognized.
BigIron RX(config)# rooter ip
Unrecognized command
Command completion
The CLI supports command completion, so you do not need to enter the entire name of a command
or option. As long as you enter enough characters of the command or option name to avoid
ambiguity with other commands or options, the CLI understands what you are typing.
Scroll control
By default, the CLI uses a page mode to paginate displays that are longer than the number of rows
in your terminal emulation window. For example, if you display a list of all the commands at the
global CONFIG level but your terminal emulation window does not have enough rows to display
them all at once, the page mode stops the display and lists your choices for continuing the display.
default-vlan-id
enable
enable-acl-counter
end
exit
--More--, next page: Space, next line: Return key, quit: Control-c
The software provides the following scrolling options:
• Press the Space bar to display the next page (one screen at time).
• Press the Return or Enter key to display the next line (one line at a time).
• Press Ctrl-C cancel the display.
Line editing commands
The CLI supports the following line editing commands. To enter a line-editing command, use the
CTRL-key combination for the command by pressing and holding the CTRL key, then pressing the
letter associated with the command.
16BigIron RX Series Configuration Guide
53-1001986-01
Logging on through the CLI
NOTE
TABLE 29 CLI line editing commands
Ctrl-key combinationDescription
Ctrl-AMoves to the first character on the command line.
Ctrl-BMoves the cursor back one character.
Ctrl-CEscapes and terminates command prompts and ongoing tasks (such as
lengthy displays), and displays a fresh command prompt.
Ctrl-DDeletes the character at the cursor.
Ctrl-EMoves to the end of the current command line.
Ctrl-FMoves the cursor forward one character.
Ctrl-KDeletes all characters from the cursor to the end of the command line.
Ctrl-L; Ctrl-RRepeats the current command line on a new line.
Ctrl-NEnters the next command line in the history buffer.
Ctrl-PEnters the previous command line in the history buffer.
Ctrl-U; Ctrl-XDeletes all characters from the cursor to the beginning of the command
line.
Ctrl-WDeletes the last word you typed.
Ctrl-ZMoves from any CONFIG level of the CLI to the Privileged EXEC level; at
the Privileged EXEC level, moves to the User EXEC level.
2
For a complete list of CLI commands and syntax information for each command, refer to the Switch and Router Command Line Interface Reference.
Searching and filtering output from CLI commands
You can filter CLI output from show commands and at the --More-- prompt. You can search for
individual characters, strings, or construct complex regular expressions to filter the output.
You can also filter output from show commands to display lines containing a specified string, lines
that do not contain a specified string, or output starting with a line containing a specified string.
The search string is a regular expression consisting of a single character or string of characters.
You can use special characters to construct complex regular expressions. Refer to “Using special
characters in regular expressions” on page 20 for information on special characters used with
regular expressions.
Displaying lines containing a specified string
The following command filters the output of the show interface command for port 3/1 so it displays
only lines containing the word “Internet”. This command can be used to display the IP address of
the interface.
BigIron RX# show interface e 3/1 | include Internet
Internet address is 192.168.1.11/24, MTU 1518 bytes, encapsulation ethernet
Syntax: <show-command> | include <regular-expression>
The vertical bar ( | ) is part of the command.
BigIron RX Series Configuration Guide17
53-1001986-01
Logging on through the CLI
NOTE
BigIron RX# show who | exclude closed
Console connections:
established
you are connecting to this session
2 seconds in idle
Telnet connections (inbound):
1 established, client ip address 192.168.9.37
27 seconds in idle
Telnet connection (outbound):
SSH connections:
BigIron RX# show who | begin SSH
SSH connections:
1 established, client ip address 192.168.9.210
7 seconds in idle
2 closed
3 closed
4 closed
5 closed
2
The regular expression specified as the search string is case sensitive. In the example above, a
search string of “Internet” would match the line containing the IP address, but a search string of
“internet” would not.
Displaying lines that do not contain a specified string
The following command filters the output of the show who command so it displays only lines that
do not contain the word “closed”. This command can be used to display open connections to a
BigIron RX Series Switch.
Displaying lines starting with a specified string
The following command filters the output of the show who command so it displays output starting
with the first line that contains the word “SSH”. This command can be used to display information
about SSH connections to the BigIron RX Series Switch.
Syntax: <show-command> | begin <regular-expression>
Searching and filtering output at the --More-- prompt
The --More-- prompt displays when output extends beyond a single page. From this prompt, you can
press the Space bar to display the next page, the Return or Enter key to display the next line, or
Ctrl-C to cancel the display. In addition, you can search and filter output from this prompt.
18BigIron RX Series Configuration Guide
53-1001986-01
Logging on through the CLI
BigIron RX# ?
append Append one file to another
attrib Change file attribute
boot Boot system from bootp/tftp server/flash image
cd Change current working directory
chdir Change current working directory
clear Clear table/statistics/keys
clock Set clock
configure Enter configuration mode
copy Copy between flash, tftp, config/code
cp Copy file commands
debug Enable debugging functions (see also 'undebug')
delete Delete file on flash
dir List files
dm test commands
dot1x 802.1x
erase Erase image/configuration files from flash
exit Exit Privileged mode
fastboot Select fast-reload option
force-sync-standby Sync active flash (pri/sec/mon/startup config/lp images)
to standby
format Format PCMCIA card
hd Hex dump
ipc IPC commands
--More--, next page: Space, next line: Return key, quit: Control-c
--More--, next page: Space, next line: Return key, quit: Control-c
/telnet
The results of the search are displayed:
searching...
telnet Telnet by name or IP address
terminal Change terminal settings
traceroute TraceRoute to IP node
undelete Recover deleted file
whois WHOIS lookup
write Write running configuration to flash or terminal
--More--, next page: Space, next line: Return key, quit: Control-c
+telnet
filtering...
telnet Telnet by name or IP address
2
At the --More-- prompt, you can press the forward slash key ( / ) and then enter a search string. The
device displays output starting from the first line that contains the search string, similar to the
begin option for show commands. For example:
BigIron RX Series Configuration Guide19
53-1001986-01
To display lines containing only a specified search string (similar to the include option for show
commands) press the plus sign key ( + ) at the --More-- prompt and then enter the search string.
The filtered results are displayed:
To display lines that do not contain a specified search string (similar to the exclude option for show
commands) press the minus sign key ( - ) at the --More-- prompt and then enter the search string.
Logging on through the CLI
--More--, next page: Space, next line: Return key, quit: Control-c
-telnet
filtering...
sync-standby Sync active flash (pri/sec/mon/startup config/lp images)
to standby if different
terminal Change terminal settings
traceroute TraceRoute to IP node
undelete Recover deleted file
whois WHOIS lookup
write Write running configuration to flash or terminal
2
The filtered results are displayed:
As with the commands for filtering output from show commands, the search string is a regular
expression consisting of a single character or string of characters. You can use special characters
to construct complex regular expressions. See the next section for information on special
characters used with regular expressions.
Using special characters in regular expressions
You use a regular expression to specify a single character or multiple characters as a search string.
In addition, you can include special characters that influence the way the software matches the
output against the search string. These special characters are listed in the following table.
TABLE 30 Special characters for regular expressions
CharacterOperation
.The period matches on any single character, including a blank space.
For example, the following regular expression matches “aaz”, “abz”, “acz”, and so on, but not just
“az”:
a.z
*The asterisk matches on zero or more sequential instances of a pattern.
For example, the following regular expression matches output that contains the string “abc”,
followed by zero or more Xs:
abcX*
+The plus sign matches on one or more sequential instances of a pattern.
For example, the following regular expression matches output that contains "de", followed by a
sequence of “g”s, such as “deg”, “degg”, “deggg”, and so on:
deg+
?The question mark matches on zero occurrences or one occurrence of a pattern.
For example, the following regular expression matches output that contains "dg" or "deg":
de?g
NOTE: Normally when you type a question mark, the CLI lists the commands or options at that CLI
level that begin with the character or string you entered. However, if you enter Ctrl-V and then
type a question mark, the question mark is inserted into the command line, allowing you to
use it as part of a regular expression.
^A caret (when not used within brackets) matches on the beginning of an input string.
For example, the following regular expression matches output that begins with “deg”:
^deg
$A dollar sign matches on the end of an input string.
20BigIron RX Series Configuration Guide
For example, the following regular expression matches output that ends with “deg”:
deg$
53-1001986-01
Logging on through the CLI
TABLE 30 Special characters for regular expressions (Continued)
CharacterOperation
_An underscore matches on one or more of the following:
• , (comma)
• { (left curly brace)
• } (right curly brace)
• ( (left parenthesis)
• ) (right parenthesis)
• The beginning of the input string
• The end of the input string
• A blank space
For example, the following regular expression matches on “100” but not on “1002”, “2100”, and so
on:
_100_
[ ]Square brackets enclose a range of single-character patterns.
For example, the following regular expression matches output that contains “1”, “2”, “3”, “4”, or “5”:
[1-5]
You can use the following expression symbols within the brackets. These symbols are allowed only
inside the brackets.
• ^ – The caret matches on any characters except the ones in the brackets. For example, the
following regular expression matches output that does not contain “1”, “2”, “3”, “4”, or “5”:
[^1-5]
• - The hyphen separates the beginning and ending of a range of characters. A matchoccurs if
any of the characters within the range is present. See the example above.
|A vertical bar separates two alternative values or sets of values. The output can match one or the
other value.
For example, the following regular expression matches output that contains either “abc” or “defg”:
abc|defg
( )Parentheses allow you to create complex expressions.
For example, the following complex expression matches on “abc”, “abcabc”, or “defg”, but not on
“abcdefgdefg”:
((abc)+)|((defg)?)
2
If you want to filter for a special character instead of using the special character as described in the
table above, enter “\” (backslash) in front of the character. For example, to filter on output
containing an asterisk, enter the asterisk portion of the regular expression as “\*”.
BigIron RX# show ip route bgp | include \*
Allowable characters for LAG names
When creating a LAG name, you can use spaces in a file or subdirectory name if you enclose the
name in double quotes. For example, to specify a subdirectory name that contains spaces, enter a
string such as the following: “a long subdirectory name”. The maximum length for a string is 64
characters.
The following characters are valid in file names:
• All upper and lowercase letters
• All digits
Any of the following special characters are valid:
• $
BigIron RX Series Configuration Guide21
53-1001986-01
Logging on through the Web Management Interface
NOTE
2
• %
• '
• -
• _
• @
• ~
• `
• !
• (
• )
• {
• }
• ^
• #
• &
Logging on through the Web Management Interface
To use the Web Management Interface, open a Web browser and enter the IP address of a BigIron
RX Series Switch’s management port in the Location or Address field. The Web browser contacts
the device and displays the login panel for the BigIron RX Series Switch, as shown in Figure 1.
FIGURE 1 Web Management Interface login panel
If you are unable to connect with the device through a Web browser due to a proxy problem, it may
be necessary to set your Web browser to direct Internet access instead of using a proxy. For
information on how to change a proxy setting, refer to the on-line help provided with your Web
browser.
To log in, click on the Login link. Figure 2 shows the dialog box that displays.
22BigIron RX Series Configuration Guide
53-1001986-01
Logging on through the Web Management Interface
2
FIGURE 2 Web Management Interface login dialog box
The login username and password you enter depends on whether your device is configured with
AAA authentication for SNMP. If AAA authentication for SNMP is not configured, you can use the
user name “get” and the default read-only password “public” for read-only access. However, for
read-write access, you must enter “set” for the user name, and enter a read-write community string
you have configured on the device for the password. There is no default read-write community
string. You must add one using the CLI. Refer to the Security Guide.
Web Management Interface
When you log into a device, the System configuration panel is displayed. This panel allows you to
enable or disable major system features. You can return to this panel from any other panel by
selecting the Home link.
The Site Map link gives you a view of all available options on a single screen.
Figure 3 displays the Web Management Interface panel for Layer 3 Switch features. This panel
allows you to configure the features supported by the Layer 3 Switch software.
FIGURE 3Panel for Layer 3 Switch features
The left pane of the Web Management Interface window contains a “tree view,” similar to the one
found in Windows Explorer. Configuration options are grouped into folders in the tree view. These
folders, when expanded, reveal additional options. To expand a folder, click on the plus sign to the
left of the folder icon.
BigIron RX Series Configuration Guide23
53-1001986-01
Logging on through IronView Network Manager
2
Logging on through
Refer to the IronView Network Management User’s Guide for information about using IronView
Network Manager.
IronView Network Manager
24BigIron RX Series Configuration Guide
53-1001986-01
Chapter
Using a Redundant Management Module
How management module redundancy works
You can install a redundant management module in slot M1 or M2 of the BigIron RX Series chassis.
By default, the system considers the module installed in slot M1 to be the active management
module and the module installed in slot M2 to be the redundant or standby module. If the active
module becomes unavailable, the standby module automatically takes over management of the
system.
This chapter describes the redundant management module, how it works with the active module,
and how to configure and manage it.
This section explains the following:
• How management module redundancy works under normal operating conditions.
• Events that cause a standby management module to assume the role of the active module and
how the switchover occurs as a result of each event.
• Implications that you should be aware of if a switchover occurs.
3
Management module redundancy overview
When you power on or reload a BigIron RX Series chassis with two management modules installed,
by default, the management module installed in slot M1 becomes the active module and the
module installed in slot M2 becomes the standby module. (You can change the default active slot
from M1 to M2 using the active-management command. For information about performing this
task, refer to “Changing the default active Chassis slot” on page 29.)
After the active and standby modules are determined, both modules boot from the source specified
for the active module. The active management module can boot from the following sources:
• The active management module’s flash memory.
• A PCMCIA flash card inserted in one of the PCMCIA slots in the active management module’s
front panel.
After the modules boot, the active module compares the standby module’s flash code and
system-config file to its own. If differences exist, the active module synchronizes the standby
module’s flash code and system-config file with its own.
During normal operation, the active module handles tasks such as obtaining network topology and
reachability information and determining the best paths to known destinations. The active module
also monitors the standby module.
The standby module functions in an active standby mode. Configuration changes made from the
CLI to the active management module are also written to the standby management module even if
they are not written to flash memory. Keeping the system-config and running-config files on both
modules synchronized allows the standby module to assume the role of active module seamlessly
if necessary.
BigIron RX Series Configuration Guide25
53-1001986-01
How management module redundancy works
3
The interface modules are not reset, as they are with the previous cold-restart redundancy feature.
The interface modules continue to forward traffic while the standby management module takes
over operation of the system. The new now-active management module receives updates from the
interface modules and sends verification information to the interface modules to ensure that they
are synchronized. If the new active management module becomes out-of-sync with an interface
module, information on the interface module can be overwritten in some cases which can cause an
interruption of traffic forwarding.
Management module switchover
The events cause the standby management module to become the active module, which is called a
switchover. Those events are as follows:
• The active module becomes unavailable.
• You perform a manual switchover.
• You remove and replace the active management module.
The following sections explain how the switchover occurs for each event.
Unavailable active module
The following events cause an active module to become unavailable and a switchover to occur:
• An active module experiences a problem significant enough to cause a reset of the module.
• The active module loses power.
Before a switchover occurs, the active module resets itself and sends an interrupt signal to the
standby module. The standby module then becomes the active module and the interface modules
continue to forward traffic.
The new active module begins to manage the system. When the original active module becomes
available again or is replaced, it assumes the role of standby module.
Manual switchover
In some situations, you may want to manually switch the role of active management module from
the currently active module to the standby module. For example, if the module in slot M2 is the
active module and the module in slot M1 is the standby module and you want the module in M1 to
be the active module and the module in M2 to be the standby module, you can perform a manual
switchover using the switchover command. For information about performing this task, refer to
“Manually switching over to the standby management module” on page 32.
When the switchover occurs, the standby module becomes the active module.
This section explains how management module redundancy is affected when you remove and
replace an active or standby management module.
Removal and replacement of an active management module
If you remove the active management module, the standby module automatically assumes the role
of the active module. After you insert a replacement module in the slot from which the original
active module was removed, the replacement module becomes the standby module. The module
boots from the source specified for the active module. The active management module can boot
from the following sources:
26BigIron RX Series Configuration Guide
53-1001986-01
How management module redundancy works
3
• The active management module’s flash memory.
• A PCMCIA flash card inserted in one of the PCMCIA slots in the active management module’s
front panel.
After the replacement module boots, the active module compares the standby module’s flash code
and system-config file to its own. If differences exist, the active module synchronizes the standby
module’s flash code and system-config file with its own.
Removal and replacement of a standby management module
You can remove a standby management module without causing a switchover to occur. The active
module continues to function as is. Communication between the active module and the removed
module stops until the new module is installed in the BigIron RX Series chassis. After the new
module is installed, it assumes the role of standby module. The module boots from the source
specified for the active module. The active management modules can boot from the following
sources:
• The active management module’s flash memory.
• A PCMCIA flash card inserted in one of the PCMCIA slots in the active management module’s
front panel.
After the module boots, the active module compares the standby module’s flash code and
system-config file to its own. If differences exist, the active module synchronizes the standby
module’s flash code and system-config file with its own.
Switchover implications
After the role of the active management module switches from one module to another, you must be
aware of implications that affect the following areas:
• Management sessions
• Syslog and SNMP traps
• MAC addresses
The following sections explain the implications for these areas.
Management sessions
You can establish management sessions with the active management module’s management port.
If a switchover occurs, the management port on the original active module shuts down and all open
CLI, Web management interface, and IronView Network Manager sessions with that port close. You
can open new sessions with the new active module, provided that the new active module has the
same management port connections. (For example, if you were accessing the Web management
interface through a PC connected to the original active module’s management port, you can open a
new session if a PC is connected to the new active module’s management port.)
In the scenario described above, you can open a new session using the same IP address you were
using before the switchover. (You configure an IP address for the active module only; if a switchover
occurs, the IP address is used by the new active module.)
BigIron RX Series Configuration Guide27
53-1001986-01
How management module redundancy works
NOTE
3
Syslog and SNMP traps
When a switchover occurs, the BigIron RX system sends a Syslog message to the local Syslog buffer
and also to the Syslog server, if you have configured the system to use one. In addition, if you have
configured an SNMP trap receiver, the system sends an SNMP trap to the receiver.
When the system is powered on or otherwise reset normally, the system sends a cold start
message and trap. However, if the system is reset as the result of switchover to the standby
management module, the system instead sends a warm start message and trap.
MAC address changes
The MAC addresses in theBigIron RX Series system are based on the MAC address of the BigIron
RX Series chassis. During switchover, the system's MAC addresses change and the system sends
out gratuitous ARP requests to flush the old MAC addresses from the ARP caches on attached IP
devices, and update the caches with the system’s new MAC addresses.
Layer 2 Hitless Failover
The Layer 2 Hitless Failover feature provides automatic failover from the active management
module to the standby management module without interrupting operation of any interface
modules in the chassis. Configuration changes made from the CLI to the active management
module are also written to the standby management module even if they are not written to flash
memory.
Since both the standby and active management modules run the same code, a command that
brings down the active management module will most likely bring down the standby management
module. Because all configuration commands are synchronized from active to standby
management module in real time, both management modules will crash at almost the same time.
This in turn causes the system to reset all interface modules (similar to the behavior when the
'reboot' command is executed) and causes packet loss associated with a system reboot.
Once booted, the redundant management module keeps up-to-date copies of the active module's
running configuration. Layer 2 protocols such as STP, RSTP, MRP, and VSRP are run concurrently on
both the active and standby management modules. Upon the failover of the active management
module, the standby module takes over as the active management module and picks up where the
active module left off, without interrupting any Layer 2 traffic.
The interface modules are not reset, as they are with the previous cold-restart redundancy feature.
The interface modules continue to forward traffic while the standby management module takes
over operation of the system. The new now-active management module receives updates from the
interface modules and sends verification information to the interface modules to ensure that they
are synchronized.
If the new active management module becomes out-of-sync with an interface module, information
on the interface module can be overwritten in some cases which can cause an interruption of
traffic forwarding. Layer 3 hitless failover is not supported in this release. Consequently, a failover
will result in a re-synchronization of Layer 3 data structures
28BigIron RX Series Configuration Guide
53-1001986-01
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.