2014, Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron,
OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and the On-Demand Data Center are trademarks
of Brocade Communications Systems, Inc., in the United States and in other countries. Other brands and product names mentioned may be
trademarks of others.
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. assume no liability or responsibility to any person or entity with respect to the
accuracy of this document or any loss, cost, liability, or damages arising from the information contained herein 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.
The document conventions describe text formatting conventions, command syntax conventions, and
important notice formats used in Brocade technical documentation.
Text formatting conventions
Text formatting conventions such as boldface, italic, or Courier font may be used in the flow of the text
to highlight specific words or phrases.
Format
bold text
italic text
Courier font
Description
Identifies command names
Identifies keywords and operands
Identifies the names of user-manipulated GUI elements
Identifies text to enter at the GUI
Identifies emphasis
Identifies variables and modifiers
Identifies paths and Internet addresses
Identifies document titles
Identifies CLI output
Identifies command syntax examples
Command syntax conventions
Bold and italic text identify command syntax components. Delimiters and operators define groupings of
parameters and their logical relationships.
Convention
bold textIdentifies command names, keywords, and command options.
valueIn Fibre Channel products, a fixed value provided as input to a command
[ ]Syntax components displayed within square brackets are optional.
option is printed in plain text, for example, --show WWN.
Default responses to system prompts are enclosed in square brackets.
{ x | y | z }A choice of required parameters is enclosed in curly brackets separated by
x | yA vertical bar separates mutually exclusive elements.
< >Nonprinting characters, for example, passwords, are enclosed in angle
...
\
vertical bars. You must select one of the options.
In Fibre Channel products, square brackets may be used instead for this
purpose.
brackets.
Repeat the previous element, for example, member[member...].
Indicates a “soft” line break in command examples. If a backslash separates
two lines of a command input, enter the entire command at the prompt without
the backslash.
Notes, cautions, and warnings
Notes, cautions, and warning statements may be used in this document. They are listed in the order of
increasing severity of potential hazards.
NOTE
A Note provides a tip, guidance, or advice, emphasizes important information, or provides a reference
to related information.
ATTENTION
An Attention statement indicates a stronger note, for example, to alert you when traffic might be
interrupted or the device might reboot.
CAUTION
A Caution statement alerts you to situations that can be potentially hazardous to you or cause
damage to hardware, firmware, software, or data.
DANGER
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.
Visit the Brocade website to locate related documentation for your product and additional Brocade
resources.
You can download additional publications supporting your product at www.brocade.com. Select the
Brocade Products tab to locate your product, then click the Brocade product name or image to open the
individual product page. The user manuals are available in the resources module at the bottom of the
page under the Documentation category.
To get up-to-the-minute information on Brocade products and resources, go to MyBrocade. You can
register at no cost to obtain a user ID and password.
Release notes are available on MyBrocade under Product Downloads.
White papers, online demonstrations, and data sheets are available through the Brocade website.
Contacting Brocade Technical Support
Brocade resources
As a Brocade customer, you can contact Brocade Technical Support 24x7 online, by telephone, or by email. Brocade OEM customers contact their OEM/Solutions provider.
Brocade customers
For product support information and the latest information on contacting the Technical Assistance
Center, go to http://www.brocade.com/services-support/index.html.
If you have purchased Brocade product support directly from Brocade, use one of the following methods
to contact the Brocade Technical Assistance Center 24x7.
OnlineTelephoneE-mail
Preferred method of contact for nonurgent issues:
• My Cases through MyBrocade
• Software downloads and licensing
tools
• Knowledge Base
Required for Sev 1-Critical and Sev
2-High issues:
• Continental US: 1-800-752-8061
• Europe, Middle East, Africa, and
Asia Pacific: +800-AT FIBREE
(+800 28 34 27 33)
• For areas unable to access toll
free number: +1-408-333-6061
• Toll-free numbers are available in
many countries.
support@brocade.com
Please include:
• Problem summary
• Serial number
• Installation details
• Environment description
Brocade OEM customers
If you have purchased Brocade product support from a Brocade OEM/Solution Provider, contact your
OEM/Solution Provider for all of your product support needs.
• OEM/Solution Providers are trained and certified by Brocade to support Brocade® products.
• Brocade provides backline support for issues that cannot be resolved by the OEM/Solution Provider.
• Brocade Supplemental Support augments your existing OEM support contract, providing direct
access to Brocade expertise. For more information, contact Brocade or your OEM.
• For questions regarding service levels and response times, contact your OEM/Solution Provider.
Document feedback
To send feedback and report errors in the documentation you can use the feedback form posted with
the document or you can e-mail the documentation team.
Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and
completeness of this document. However, if you find an error or an omission, or you think that a topic
needs further development, we want to hear from you. You can provide feedback in two ways:
• Through the online feedback form in the HTML documents posted on www.brocade.com.
• By sending your feedback to documentation@brocade.com.
Provide the publication title, part number, and as much detail as possible, including the topic heading
and page number if applicable, as well as your suggestions for improvement.
How command information is presented in this guide
Summary of Enhancements in FastIron release 08.0.10dTABLE 1
FeatureDescriptionLocation
DHCPv6 Relay Agent Prefix
Delegation Notification
DHCPv6 Relay Agent Prefix
Delegation Notification allows a
DHCPv6 server to dynamically
delegate IPv6 prefixes to a DHCPv6
client using the DHCPv6 Prefix
Delegation (PD) option.
Described in IPv6 Configuration on
FastIron X Series, FCX, and ICX
Series Switches on page 163
How command information is presented in this guide
For all new content, command syntax and parameters are documented in a separate command
reference section at the end of the publication.
In an effort to provide consistent command line interface (CLI) documentation for all products, Brocade
is in the process of preparing standalone Command References for the IP platforms. This process
involves separating command syntax and parameter descriptions from configuration tasks. Until this
process is completed, command information is presented in two ways:
• For all new content included in this guide, the CLI is documented in separate command pages. The
new command pages follow a standard format to present syntax, parameters, usage guidelines,
examples, and command history. Command pages are compiled in alphabetical order in a separate
command reference chapter at the end of the publication.
• Legacy content continues to include command syntax and parameter descriptions in the chapters
where the features are documented.
If you do not find command syntax information embedded in a configuration task, refer to the
command reference section at the end of this publication for information on CLI syntax and usage.
Domain Name Server (DNS) resolver08.0.0108.0.0108.0.0108.0.0108.0.0108.0.0108.0.10
IP checksum check disableNoNoNoNo08.0.0108.0.0108.0.10
NOTE
References to chassis-based Layer 3 switches apply to the FSX 800 and FSX 1600.
NOTE
The terms Layer 3 Switch and router are used interchangeably in this chapter and mean the same.
Basic IP configuration
IP is enabled by default. Basic configuration consists of adding IP addresses for Layer 3 switches,
enabling a route exchange protocol, such as the Routing Information Protocol (RIP).
If you are configuring a Layer 3 switch, refer to Configuring IP addresses on page 38 to add IP
addresses, then enable and configure the route exchange protocols, as described in other chapters of
this guide.
If you are configuring a Layer 2 switch, refer to Configuring the management IP address and specifying
the default gateway on page 105 to add an IP address for management access through the network
and to specify the default gateway.
The rest of this chapter describes IP and how to configure it in more detail. Use the information in this
chapter if you need to change some of the IP parameters from their default values or you want to view
configuration information or statistics.
IP configuration overview
Brocade Layer 2 switches and Layer 3 switches support Internet Protocol version 4 (IPv4) and IPv6. IP
support on BrocadeLayer 2 switches consists of basic services to support management access and
access to a default gateway.
Full Layer 3 support
IP support on Brocade full Layer 3 switches includes all of the following, in addition to a highly
configurable implementation of basic IP services including Address Resolution Protocol (ARP), ICMP
Router Discovery Protocol (IRDP), and Reverse ARP (RARP):
• Route exchange protocols:
‐Routing Information Protocol (RIP)
‐Open Shortest Path First (OSPF)
‐Border Gateway Protocol version 4 (BGP4)
This section describes IPv4 addresses. For information about IPv6 addresses on FastIron X Series
devices, refer to "IPv6 addressing overview" section in the FastIron Ethernet Switch AdministrationGuide .
Brocade Layer 3 switches and Layer 2 switches allow you to configure IP addresses. On Layer 3
switches, IP addresses are associated with individual interfaces. On Layer 2 switches, a single IP
address serves as the management access address for the entire device.
All Brocade Layer 3 switches and Layer 2 switches support configuration and display of IP addresses in
classical subnet format (for example: 192.168.1.1 255.255.255.0) and Classless Interdomain Routing
(CIDR) format (for example: 192.168.1.1/24). You can use either format when configuring IP address
information. IP addresses are displayed in classical subnet format by default but you can change the
display format to CIDR. Refer to Changing the network mask display to prefix format on page 132.
Brocade Layer 3 switches allow you to configure IP addresses on the following types of interfaces:
• Ethernet ports
• Virtual routing interfaces (used by VLANs to route among one another)
• Loopback interfaces
• GRE tunnels
Each IP address on a Layer 3 switch must be in a different subnet. You can have only one interface
that is in a given subnet. For example, you can configure IP addresses 192.168.1.1/24 and
192.168.2.1/24 on the same Layer 3 switch, but you cannot configure 192.168.1.1/24 and
192.168.1.2/24 on the same Layer 3 switch.
You can configure multiple IP addresses on the same interface.
The number of IP addresses you can configure on an individual interface depends on the Layer 3
switch model. To display the maximum number of IP addresses and other system parameters you can
configure on a Layer 3 switch, refer to "Displaying and modifying system parameter default settings"
section in the FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide .
You can use any of the IP addresses you configure on the Layer 3 switch for Telnet or SNMP access.
Layer 2 switches
You can configure an IP address on a BrocadeLayer 2 switch for management access to the Layer 2
switch. An IP address is required for Telnet access and SNMP access.
You also can specify the default gateway for forwarding traffic to other subnets.
FIGURE 1 IP Packet flow through a Brocade Layer 3 switch
IP packet flow through a Layer 3 switch
1. When the Layer 3 switch receives an IP packet, the Layer 3 switch checks for filters on the receiving
interface.3 If a deny filter on the interface denies the packet, the Layer 3 switch discards the packet
and performs no further processing, except generating a Syslog entry and SNMP message, if logging
is enabled for the filter.
2. If the packet is not denied at the incoming interface, the Layer 3 switch looks in the session table for
an entry that has the same source IP address and TCP or UDP port as the packet. If the session
table contains a matching entry, the Layer 3 switch immediately forwards the packet, by addressing it
to the destination IP address and TCP or UDP port listed in the session table entry and sending the
packet to a queue on the outgoing ports listed in the session table. The Layer 3 switch selects the
queue based on the Quality of Service (QoS) level associated with the session table entry.
3. If the session table does not contain an entry that matches the packet source address and TCP or
UDP port, the Layer 3 switch looks in the IP forwarding cache for an entry that matches the packet
destination IP address. If the forwarding cache contains a matching entry, the Layer 3 switch
forwards the packet to the IP address in the entry. The Layer 3 switch sends the packet to a queue
on the outgoing ports listed in the forwarding cache. The Layer 3 switch selects the queue based on
the Quality of Service (QoS) level associated with the forwarding cache entry.
4. If the IP forwarding cache does not have an entry for the packet, the Layer 3 switch checks the IP
route table for a route to the packet destination. If the IP route table has a route, the Layer 3 switch
3
The filter can be an Access Control List (ACL) or an IP access policy.
makes an entry in the session table or the forwarding cache, and sends the route to a queue on the
outgoing ports:
• ‐If the running-config contains an IP access policy for the packet, the software makes an
‐If the running-config does not contain an IP access policy for the packet, the software
The following sections describe the IP tables and caches:
• ARP cache and static ARP table
• IP route table
• IP forwarding cache
• Layer 4 session table
The software enables you to display these tables. You also can change the capacity of the tables
on an individual basis if needed by changing the memory allocation for the table.
ARP cache and static ARP table
entry in the session table. The Layer 3 switch uses the new session table entry to
forward subsequent packets from the same source to the same destination.
creates a new entry in the forwarding cache. The Layer 3 switch uses the new cache
entry to forward subsequent packets to the same destination.
The ARP cache contains entries that map IP addresses to MAC addresses. Generally, the entries are
for devices that are directly attached to the Layer 3 switch.
An exception is an ARP entry for an interface-based static IP route that goes to a destination that is
one or more router hops away. For this type of entry, the MAC address is either the destination device
MAC address or the MAC address of the router interface that answered an ARP request on behalf of
the device, using proxy ARP.
ARP cache
The ARP cache can contain dynamic (learned) entries and static (user-configured) entries. The
software places a dynamic entry in the ARP cache when the Layer 3 switch learns a device MAC
address from an ARP request or ARP reply from the device.
The software can learn an entry when the Layer 2 switch or Layer 3 switch receives an ARP request
from another IP forwarding device or an ARP reply. Here is an example of a dynamic entry:
IP Address MAC Address Type Age Port
1 10.95.6.102 0000.00fc.ea21 Dynamic 0 6
Each entry contains the destination device IP address and MAC address.
Static ARP table
In addition to the ARP cache, Layer 3 switches have a static ARP table. Entries in the static ARP table
are user-configured. You can add entries to the static ARP table regardless of whether or not the
device the entry is for is connected to the Layer 3 switch.
NOTE
Layer 3 switches have a static ARP table. Layer 2 switches do not.
The software places an entry from the static ARP table into the ARP cache when the entry interface
comes up.
Index IP Address MAC Address Port
1 10.95.6.111 0000.003b.d210 1/1
Each entry lists the information you specified when you created the entry.
IP route table
The IP route table contains paths to IP destinations.
NOTE
Layer 2 switches do not have an IP route table. A Layer 2 switch sends all packets addressed to
another subnet to the default gateway, which you specify when you configure the basic IP information
on the Layer 2 switch.
The IP route table can receive the paths from the following sources:
• A directly-connected destination, which means there are no router hops to the destination
• A static IP route, which is a user-configured route
• A route learned through RIP
• A route learned through OSPF
• A route learned through BGP4
The IP route table contains the best path to a destination:
• When the software receives paths from more than one of the sources listed above, the software
compares the administrative distance of each path and selects the path with the lowest
administrative distance. The administrative distance is a protocol-independent value from 1 through
255.
• When the software receives two or more best paths from the same source and the paths have the
same metric (cost), the software can load share traffic among the paths based on destination host or
network address (based on the configuration and the Layer 3 switch model).
Here is an example of an entry in the IP route table.
Destination NetMask Gateway Port Cost Type
10.1.0.0 255.255.0.0
10.1.1.2 1/1 2 R
Each IP route table entry contains the destination IP address and subnet mask and the IP address of
the next-hop router interface to the destination. Each entry also indicates the port attached to the
destination or the next-hop to the destination, the route IP metric (cost), and the type. The type indicates
how the IP route table received the route.
To increase the size of the IP route table for learned and static routes, refer to the section "Displaying
and modifying system parameter default settings" in the FastIron Ethernet Switch Platform and Layer 2Switching Configuration Guide:
• For learned routes, modify theip-route parameter.
• For static routes, modify the ip-static-route parameter.
IP forwarding cache
The IP forwarding cache provides a fast-path mechanism for forwarding IP packets. The cache contains
entries for IP destinations. When a Brocade Layer 3 switch has completed processing and addressing
for a packet and is ready to forward the packet, the device checks the IP forwarding cache for an entry
to the packet destination:
• If the cache contains an entry with the destination IP address, the device uses the information in the
entry to forward the packet out the ports listed in the entry. The destination IP address is the
address of the packet final destination. The port numbers are the ports through which the
destination can be reached.
• If the cache does not contain an entry and the traffic does not qualify for an entry in the session
table instead, the software can create an entry in the forwarding cache.
Each entry in the IP forwarding cache has an age timer. If the entry remains unused for ten minutes,
the software removes the entry. The age timer is not configurable.
Here is an example of an entry in the IP forwarding cache.
IP Address Next Hop MAC Type Port Vlan Pri
1 192.168.1.11 DIRECT 0000.0000.0000 PU n/a 0
Each IP forwarding cache entry contains the IP address of the destination, and the IP address and
MAC address of the next-hop router interface to the destination. If the destination is actually an
interface configured on the Layer 3 switch itself, as shown here, then next-hop information indicates
this. The port through which the destination is reached is also listed, as well as the VLAN and Layer 4
QoS priority associated with the destination if applicable.
NOTE
You cannot add static entries to the IP forwarding cache, although you can increase the number of
entries the cache can contain. Refer to the section "Displaying and modifying system parameter
default settings" in the FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide .
Layer 4 session table
The Layer 4 session provides a fast path for forwarding packets. A session is an entry that contains
complete Layer 3 and Layer 4 information for a flow of traffic. Layer 3 information includes the source
and destination IP addresses. Layer 4 information includes the source and destination TCP and UDP
ports. For comparison, the IP forwarding cache contains the Layer 3 destination address but does not
contain the other source and destination address information of a Layer 4 session table entry.
The Layer 2 switch or Layer 3 switch selects the session table instead of the IP forwarding table for
fast-path forwarding for the following features:
• Layer 4 Quality-of-Service (QoS) policies
• IP access policies
To increase the size of the session table, refer to the section "Displaying and modifying system
parameter default settings" in the FastIron Ethernet Switch Platform and Layer 2 SwitchingConfiguration Guide . The ip-qos-session parameter controls the size of the session table.
IP route exchange protocols
Brocade Layer 3 switches support the following IP route exchange protocols:
• Routing Information Protocol (RIP)
• Open Shortest Path First (OSPF)
• Border Gateway Protocol version 4 (BGP4)
All these protocols provide routes to the IP route table. You can use one or more of these protocols, in
any combination. The protocols are disabled by default.
For configuration information, refer to chapter "IP Multicast Protocols" in the FastIron Ethernet Switch IPMulticast Configuration Guide .
NOTE
Brocade Layer 3 switches support IGMP and can forward IP multicast packets. Refer to the "IP
Multicast Traffic Reduction" chapter in the FastIron Ethernet Switch IP Multicast Configuration Guide .
IP interface redundancy protocols
You can configure a Brocade Layer 3 switch to back up an IP interface configured on another Brocade
Layer 3 switch. If the link for the backed up interface becomes unavailable, the other Layer 3 switch can
continue service for the interface. This feature is especially useful for providing a backup to a network
default gateway.
Brocade Layer 3 switches support the following IP interface redundancy protocols:
• Virtual Router Redundancy Protocol (VRRP) - A standard router redundancy protocol based on RFC
2338. You can use VRRP to configure Brocade Layer 3 switches and third-party routers to back up
IP interfaces on other Brocade Layer 3 switches or third-party routers.
• Virtual Router Redundancy Protocol Extended (VRRP-E) - A Brocade extension to standard VRRP
that adds additional features and overcomes limitations in standard VRRP. You can use VRRP-E
only on Brocade Layer 3 switches.
ACLs and IP access policies
Brocade Layer 3 switches provide two mechanisms for filtering IP traffic:
• Access Control Lists (ACLs)
• IP access policies
Both methods allow you to filter packets based on Layer 3 and Layer 4 source and destination
information.
ACLs also provide great flexibility by providing the input to various other filtering mechanisms such as
route maps, which are used by BGP4.
IP access policies allow you to configure QoS based on sessions (Layer 4 traffic flows).
Only one of these filtering mechanisms can be enabled on a Brocade device at a time. Brocade devices
can store forwarding information for both methods of filtering in the session table.
For configuration information, refer to the chapter "Rule-Based IP ACLs" in the FastIron Ethernet Switch
Most IP parameters described in this chapter are dynamic. They take effect immediately, as soon as
you enter the CLI command. You can verify that a dynamic change has taken effect by displaying the
running-config. To display the running-config, enter the show running-config or write terminal
command at any CLI prompt.
To save a configuration change permanently so that the change remains in effect following a system
reset or software reload, save the change to the startup-config file:
• To save configuration changes to the startup-config file, enter the write memory command from the
Privileged EXEC level of any configuration level of the CLI.
Changes to memory allocation require you to reload the software after you save the changes to the
startup-config file. When reloading the software is required to complete a configuration change
described in this chapter, the procedure that describes the configuration change includes a step for
reloading the software.