The information in this document is subject to change without notice. The statements, configurations, technical
data, and recommendations in this document a re believed to be accurate and reliable, but are presented without
express or implied warranty. Users must take full responsibility for their applications of any products specified in this
document. The information in this document is proprietary to Nortel Networks .
The software described in this document is furnished under a license agreement and may be used only in accordance
with the terms of that license. The software license agreement is included in this document.
Restricted rights legend
Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.
Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer
software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth
in the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.
Statement of conditions
In the interest of improving internal design, operational function, and/or reliability, Nortel Networks reserves the right
to make changes to the products described in this document without notice.
Nortel Networks does not assume any liability that may occur due to the use or application of the product(s) or
circuit layout(s) described herein.
Nortel Networks software license agreement
This Software License Agreement ("License Agreement") is between you, the end user ("Customer") and Nortel
Networks Corporation and its subsidiaries and affiliates ("Nortel Networks"). PLEASE READ THE FOLLOWING
CAREFULLY. YOU MUST ACCEPT THESE LICENSE TERMS IN ORDER TO DOWNLOAD AND/OR USE THE
SOFTWARE. USE OF THE SOFTWARE CONSTITUTES YOUR ACCEPTANCE OF THIS LICENSE AGREEMENT.
If you do not accept these terms and conditions, return the Software, unused and in the original shipping container,
within 30 days of purchase to obtain a credit for the full purchase price.
"Software" is owned or licensed by Nortel Networks, its parent or one of its subsidiaries or affiliates, and is
copyrighted and licensed, not sold. Software consists of machine-readable instructions, its components, data,
audio-visual content (such as images, text, recordings or pictures) and related licensed materials including all whole
or partial copies. Nortel Networks grants you a license to use the Software only in the country where you acquired the
Software. You obtain no rights other than those granted to you under this License Agreement. You are responsible for
the selection of the Software and for the installation of, use of, and results obtained from the Software.
1. Licensed Use of Software. Nortel Networks grants Customer a nonexclusive license to use a copy of the
Software on only one machine at any one time or to the extent of the activation or authorized usage level, whichever
is applicable. To the extent Software is furnished for use with designated hardware or Customer furnished equipment
("CFE"), Customer is granted a nonexclusive license to use Software only on such hardware or CFE, as applicable.
Software contains trade secrets and Customer agrees to treat Software as confidential information using the same
care and discretion Customer uses with its own similar information that it does not wish to disclose, publish or
disseminate. Customer will ensure that anyone who uses the Software does so only in compliance with the terms of
this Agreement. Customer shall not a) use, copy, modify, transfer or distribute the Software except as expressly
authorized; b) reverse assemble, reverse compile, reverse engineer or otherwise translate the Software; c) create
derivative works or modifications unless expressly authorized; or d) sublicense, rent or lease the Software. Licensors
of intellectual property to Nortel Networks are beneficiaries of this provision. Upon termination or breach of the
license by Customer or in the event designated hardware or CFE is no longer in use, Customer will promptly return
the Software to Nortel Networks or certify its destruction. Nortel Networks may audit by remote polling or other
reasonable means to determine Customer’s Software activation or usage levels. If suppliers of third party software
included in Software require Nortel Networks to include additional or different terms, Customer agrees to abide by
such terms provided by Nortel Networks with respect to such third party software.
2. Warranty. Except as may be otherwise expressly agreed to in writing between Nortel Networks and Customer,
Software is provided "AS IS" without any warranties (conditions) of any kind. NORTEL NETWORKS DISCLAIMS
ALL WARRANTIES (CONDITIONS) FOR THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT
NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE AND ANY WARRANTY OF NON-INFRINGEMENT.Nortel Networks is not obligated to provide support of
any kind for the Software. Some jurisdictions do not allow exclusion of implied warranties, and, in such event, the
above exclusions may not apply.
3. Limitation of Remedies. IN NO EVENT SHALL NORTEL NETWORKS OR ITS AGENTS OR SUPPLIERS BE
LIABLE FOR ANY OF THE FOLLOWING: a) DAMAGES BASED ON ANY THIRD PARTY CLAIM; b) LOSS OF, OR
DAMAGE TO, CUSTOMER’S RECORDS, FILES OR DATA; OR c) DIRECT, INDIRECT, SPECIAL, INCIDENTAL,
PUNITIVE, OR CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), WHETHER IN
CONTRACT, TORT OR OTHERWISE (INCLUDING NEGLIGENCE) ARISING OUT OF YOUR USE OF THE
SOFTWARE, EVEN IF NORTEL NETWORKS, ITS AGENTS OR SUPPLIERS HAVE BEEN ADVISED OF THEIR
POSSIBILITY. The forgoing limitations of remedies also apply to any developer and/or supplier of the Software. Such
developer and/or supplier is an intended beneficiary of this Section. Some jurisdictions do not allow these limitations
or exclusions and, in such event, they may not apply.
4. General
a) If Customer is the United States Government, the following paragraph shall apply: All Nortel Networks Software
available under this License Agreement is commercial computer software and commercial computer software
documentation and, in the event Software is licensed for or on behalf of the United States Government, the respective
rights to the software and software documentation are governed by Nortel Networks standard commercial license
in accordance with U.S. Federal Regulations at 48 C.F.R. Sections 12.212 (for non-DoD entities) and 48 C.F.R.
227.7202 (for DoD entities).
b) Customer may terminate the license at any time. Nortel Networks may terminate the license if Customer fails to
comply with the terms and conditions of this license. In either event, upon termination, Customer must either return
the Software to Nortel Networks or certify its destruction.
c) Customer is responsible for payment of any taxes, including personal property taxes, resulting from Customer’s
use of the Software. Customer agrees to comply with all applicable laws including all applicable export and import
laws and regulations.
d) Neither party may bring an action, regardless of form, more than two years after the cause of the action arose.
e) The terms and conditions of this License Agreement form the complete and exclusive agreement between
Customer and Nortel Networks.
f) This License Agreement is governed by the laws of the country in which Customer acquires the Software. If
the Software is acquired in the United States, then this License Agreement is governed by the laws of the state
of New York.
This document provides information and instructions on the configuration
of IP Routing on the 5500 Series Nortel Ethernet Routing Switch. Consult
any documentation included with the switch and the product release notes
(see "Related publications" (page 10)) for any errata before beginning the
configuration process.
Nortel Ethernet Routing Switch 5500 Series
"5500 Series Switch Platforms" (page 9)outlines the switches that are part
of the 5500 Series of Nortel Ethernet Routing Switches
5500 Series Switch Platforms
9
5500 Series Switch Model
Nortel Ethernet Routing Switch
5510-24T
Nortel Ethernet Routing Switch
5510-48T
Nortel Ethernet Routing Switch
5520-24T-PWR
Nortel Ethernet Routing Switch
5520-48T-PWR
Nortel Ethernet Routing Switch
5530-24TFD
Key Features
A 24 port, 10/100/1GBase-T, Layer 4,
diffserv-capable, stackable Ethernet switch.
This switch contains two shared SFP ports.
A 48 port, 10/100/1GBase-T, Layer 4,
diffserv-capable, stackable Ethernet switch.
This switch contains two shared SFP ports.
A 24 port, 10/100/1GBase-T, Layer 4,
diffserv-capable, stackable Ethernet switch with
full Power over Ethernet (PoE) capability on all
copper ports. This switch contains four shared
SFP ports.
A 48 port, 10/100/1GBase-T, Layer 4,
diffserv-capable, stackable Ethernet switch with
full Power over Ethernet (PoE) capability on all
copper ports. This switch contains four shared
SFP ports.
A 24 port, 10/100/1GBase-T, Layer 4,
diffserv-capable, stackable Ethernet switch.
This switch contains twelve shared SFP ports
and two XFP ports.
For more information about the management, configuration, and use of the
Nortel Ethernet Routing Switch 5500 Series, refer to the publications listed
in"Nortel Ethernet Routing Switch 5500 Series Documentation" (page 10).
Nortel Ethernet Routing Switch 5500 Series Documentation
TitleDescriptionPart Number
Nortel Ethernet
Routing Switch 5500
Series Release 5.1
Installation
Nortel Ethernet
Routing Switch 5500
Release 5.1 Series
Configuration-System
Nortel Ethernet
Routing Switch
5500 Release 5.1
Series Configuration Security
Nortel Ethernet
Routing Switch 5500
Series Release 5.1
Configuration-VLANs,
Spanning Tree, and
Link Aggregation
Instructions for the installation of
a switch in the Nortel Ethernet
Routing Switch 5500 Series. It also
provides an overview of hardware
key to the installation, configuration,
and maintenance of the switch.
Instructions for the general
configuration of switches in the 5500
Series that are not covered by the
other documentation.
Instructions for the configuration
and management of security for
switches in the 5500 Series.
Instructions for the configuration of
spanning and trunking protocols on
5500 Series switches
Instructions for the configuration of
IP routing protocols on 5500 Series
switches.
NN47200-300
NN47200-500
NN47200-501
NN47200-502
NN47200-503
Nortel Ethernet
Routing Switch 5500
Series Release 5.1
Configuration - Quality
of Service
Nortel Ethernet
Routing Switch
5500 Release 5.1
Configuration- System
Monitoring
Provides an overview of new
features, fixes, and limitations of
the 5500 Series switches. Also
included are any supplementary
documentation and document
errata.
Instructions for the installation and
use of the Nortel Ethernet RPS 15.
Instructions for the installation and
use of the DC-DC power converter.
Instructions for the installation and
use of SFP transceivers.
NN47200-400
217070-A
215081-A
NN47200-302
You can access technical documentation online at the Nortel Technical
Support web site, located at http://www.nortel.com/support. Use the
followingprocedure to access documents on the Technical Support web site:
•
If it is not already selected, click the Browse product support tab.
•
From the list provided in the product family box, select Nortel Ethernet
Routing Switch.
•From the product list, select the desired 5500 Series Switch.
•
From the content list, select Documentation.
•
Click Go.
You can view documents online, download them for future reference, or
printed them. All documents available on the Technical Support web site are
in Adobe Portable Document Format (PDF) format.
Finding the latest updates on the Nortel web site
The content of this documentation was current at the time of release. To
check for updates to the documentation and software for the Nortel Ethernet
Routing Switch 5500 Series, use the links provided in the following table.
SoftwareNortel Ethernet Routing Switch 5500 Series Software
Documentation"Nortel Ethernet Routing Switch 5500 Series
If a service contract for the Nortel product has been purchased from a
distributor or authorized reseller, contact the technical support staff for that
distributor or reseller for assistance.
If a Nortel service program was purchased, contact Nortel Technical
Support.
The following information is available online:
•
•
•
An ERC is available for many Nortel products and services. When an ERC
is used, the call is routed to technical support personnel who specialize
in supporting the service or product. The ERC for a particular product or
service is available online.
The main Nortel support portal is availableat http://www.nortel.com/support.
contact information for Nortel Technical Support
information about the Nortel Technical Solutions Centers
information about the Express Routing Code (ERC) for your product
This chapter provides an introduction to IP routing and IP routing protocols
used in the Nortel Ethernet Routing Switch 5500 Series. Subsequent
chapters will provide a more detailed description of switch capabilities and
configuration procedures.
IP routing
To configure IP routing on the Nortel Ethernet Routing Switch 5500 Series,
use virtual local area networks (VLAN) to create virtual router interfaces by
assigning an IP address to the VLAN. This section discusses this concept
in depth.
For a more detailed description about VLANs and their use, consult Nortel
Ethernet Routing Switch 5500 Series Release 5.1 Configuration - VLANs,
Spanning Tree, and Link Aggregation.
IP addressing
An IP version 4 (IPv4) address consists of 32 bits expressed in a
dotted-decimal format (XXX.XXX.XXX.XXX). The IPv4 address space is
divided into classes, with classes A, B, and C reserved for unicast addresses
and accounting for 87.5 percent of the 32-bit IP address space. Class D
is reserved for multicast addressing. " IP address classifications" (page
13)lists the breakdown of the IP address space by address range and mask.
IP address classifications
Class
A
Note: Although technically part of Class A addressing, network 127 is reserved
for loopback.
Note: Class D addresses are primarily reserved for multicast operations although
the addresses 224.0.0.5 and 224.0.0.6 are used by OSPF and 224.0.0.9 is used
by RIP.
E
Note: Class E addresses are reserved for research purposes.
Address RangeMask
224.0.0.0 -
239.255.255.254
240.0.0.0 -
240.255.255.255
Number of
Networks
Nodes per
Network
To express an IP address in dotted-decimal notation, each octet of the
IP address is converted to a decimal number and separated by decimal
points. For example, the 32-bit IP address 10000000 00100000 00001010
10100111 is expressed in dotted-decimal notation as 128.32.10.167.
Each IP address class, when expressed in binary notation, has a different
boundary point between the network and host portions of the address, as
illustrated in "Network and host boundaries in IP address classes" (page
14). The network portion is a network number field from 8 through 24 bits.
The remaining 8 through 24 bits identify a specific host on the network.
Network and host boundaries in IP address classes
Subnet addressing
Subnetworks (or subnets) are an extension of the IP addressing scheme.
Subnets allow an organization to use one IP address range for multiple
networks. Subnets are two or more physical networks that share a common
network-identification field (the network portion of the 32-bit IP address).
A subnet address is created by increasing the network portion to include
a subnet address, thus decreasing the host portion of the IP address. For
example, in the address 128.32.10.0, the network portion is 128.32, while
the subnet is found in the first octet of the host portion (10). A subnet mask
is applied to the IP address and identifies the network and host portions
of the address.
" Subnet masks for Class B and Class C IP addresses" (page 15)illustrates
how subnet masks used with Class B and Class C addresses can create
differing numbers of subnets and hosts. This example shows the use of the
zero subnet, which is permitted on a Nortel Ethernet Routing Switch 5510.
Subnet masks for Class B and Class C IP addresses
Number
of bits
Subnet Mask
Number of Subnets
(Recommended)
Number of Hosts
per Subnet
Class B
2255.255.192.0216 382
3255.255.224.068 190
4255.255.240.0144 094
5
Variable-length subnet masking (VLSM) is the ability to divide an intranet
into pieces that match network requirements. Routing is based on the
longest subnet mask or network that matches.
IP routing using VLANs
The Nortel Ethernet Routing Switch 5500 Series supports wire-speed IP
routing between virtual LANs (VLAN). This type of routing is also referred to
as virtual routing. When a virtual router interface is created for a specified
VLAN, a specific IP address is associated with the specific VLAN. In this
release, the Nortel Ethernet Routing Switch 5500 Series supports static
routing, in which the identifiers of the devices being routed between are
entered manually.
This virtual router interface does not have an association with any specified
port or set of ports (it is called a virtual router interface because it is not
associated with any particular port). The VLAN IP address can be reached
through any of the ports in the VLAN specified as a virtual router interface,
and the assigned IP address is the gateway through which packets are
routed out of that VLAN. Routed traffic can be forwarded to another VLAN
within the switch or stack of Nortel Ethernet Routing Switch 5500 Series.
Once routing is enabled on two VLANs by assigning IP addresses, routing
can be performed between those two VLANs (refer to "IP routing with
VLANs" (page 16)).
IP routing with VLANs
IP routing is enabled or disabled globally on the Nortel Ethernet Routing
Switch 5500 Series. By default, IP routing is disabled.
Note: All IP routing parameters can be configured on the Nortel
Ethernet Routing Switch 5500 Series before routing is actually enabled
on the switch.
There is no longer a one-to-one correspondence between the physical
port and the router interface, because a given port can belong to multiple
VLANs. The VLANs may be configured for routing on the switch.
As with any IP address, virtual router interface addresses are also used for
device management. For management over IP, any virtual router interface
IP address can be used to access the switch as long as routing is enabled.
When the Nortel Ethernet Routing Switch 5500 Series switch or stack is
used without routing enabled, the Management VLAN is reachable only
through the switch or stack IP address. With IP routing enabled on the
switch or stack, any of the virtual router IP interfaces can be used for
management over IP.
Once routing is enabled on the Nortel Ethernet Routing Switch 5500 Series
switches, the Management VLAN behaves like all other routable VLANs.
The IP address is reachable through any virtual router interface, as long as
a route is available. Actually, all virtual router interfaces can be used as the
Management VLAN over IP.
Multinetting
The Nortel Ethernet Routing Switch 5500 Series supports the definition
and configuration of up to eight secondary interfaces on each VLAN
(multinetting). With IP multinetting, you can associate multiple IP subnets
with one VLAN. That is, connected hosts can belong to different IP subnets
on the same VLAN.
Multinetting can be configured using the CLI or the Device Manager.
The following diagram illustrates a network with configured IP multinetting.
You can configure a static route with the next hop on the secondary
interface. You can also add static ARP for a given IP address in the same
subnet of a secondary interface.
Here are some limitations when you are working with secondary interfaces:
•
you can have a maximum of eight secondary interfaces on each VLAN
•
you can have a total maximum of 256 IP interfaces (including primary
and secondary)
•
all of the secondary interfaces on a VLAN are enabled or disabled
together. There is no provision for configuring the administrative state of
the secondary IP interfaces individually.
•
dynamic routing is not available for secondary IP interfaces
•secondary interfaces are not supported on brouters
•
a primary IP interface must be in place before secondary IP interfaces
can be added; secondary interfaces must be deleted before you can
delete the primary
If secondary interfaces are configured on the management VLAN, routing
cannot be disabled globally or on the management VLAN. Secondary IP
interfaces on the management VLAN are purged from NVRAM when
•
a unit leaves the stack and the switch does not have a manually
configured IP
•
the switch fails to get the IP address through the BootP mode
The following are not supported on secondary interfaces:
•
DHCRP
•
Proxy ARP
•
UDP broadcast
•
IPFIX
•
VRRP, OSPF, RIP
For information about configuring secondary interfaces on VLANs, see "IP
routing using VLANs" (page 16).
Brouter port
The Nortel Ethernet Routing Switch 5500 Series supports the concept
of brouter ports. A brouter port is a single-port VLAN that can route IP
packets as well as bridge all non-routable traffic. The difference between
a brouter port and a standard IP protocol-based VLAN configured to do
routing is that the routing interface of the brouter port is not subject to
the spanning tree state of the port. A brouter port can be in the blocking
state for non-routable traffic and still be able to route IP traffic. This feature
removes any interruptions caused by Spanning Tree Protocol recalculations
in routed traffic. A brouter port is actually a one-port VLAN; therefore, each
brouter port decreases the number of available VLANs by one and uses
one VLAN ID.
When a brouter port is created, the following actions are also taking place
on the switch:
•
A port-based VLAN is created.
•
The brouter port is added to the new port-based VLAN.
•
The PVID of the brouter port is changed to the VLAN ID of the new
VLAN.
•
The STP participation of the brouter port is disabled.
Prior to Software Release 4.0, the Management VLAN was the only VLAN
that was used to carry the management traffic, including Telnet, Web,
SNMP, BootP and TFTP for the switch. The Management VLAN always
exists on the switch and cannot be removed. All IP settings, including switch
IP address, stack IP address, subnet mask and default gateway, apply only
to the Management VLAN.
In this release of Nortel Ethernet Routing Switch 5500 Series, a regular
Layer 2 (L2) VLAN behaves like a routable L3 VLAN if a pair of IP addresses
and a MAC address are attached to the VLAN. When routing is enabled in
L3 mode, every L3 VLAN is capable of doing routing as well as carrying the
management traffic. Any L3 VLAN can be used instead of the Management
VLAN to manage the switch.
Layer 2 versus Layer 3 mode
When the Nortel Ethernet Routing Switch 5500 Series is configured to route
IP traffic between different VLANs, the switch is considered to be running in
L3 mode; otherwise, the switch runs in L2 mode.
The L3 manager determines in which mode a switch or a stack should be
run. The mode is determined based on the user settings and events. But
the general rule is to select:
•
L3 mode: if routing is turned on globally for the switch or stack.
•
L2 mode: if routing is turned off globally for the switch or stack.
Routing and management
In L3 mode, the Management VLAN, as well as all other L3 VLANs, has the
capability to route and carry the management traffic. In this release of the
Nortel Ethernet Routing Switch 5500 Series, the settings apply to all L3
VLANs or only to the Management VLAN. "VLAN settings" (page 20)shows
all possible settings and default settings for each type of VLAN.
VLAN settings
VLAN/Feature
Management VLAN
(L2 mode)
Management VLAN
(L3 mode)
L3 VLANOn/off (on)On/off (on)Yes (global)
Setting IP routing
To set IP routing (or L3 VLANs), take the following steps:
Enable IP routing globally.
Assign an IP address to the specific VLAN or brouter port.
Enable IP routing on the interface.
Refer to subsequent chapters in this document for detailed instructions on
configuring IP routes.
Address Resolution Protocol (ARP)
Address Resolution Protocol (ARP)
Network stations using the IP protocol need both a physical address and an
IP address to transmit a packet. If a network station knows only a network
host’s IP address, the Address Resolution Protocol (ARP) enables the
network station to determine a network host’s physical address and bind
the 32-bit IP address to a 48-bit MAC address. A network station can use
ARP across a single network only, and the network hardware must support
physical broadcasts.
If a network station wants to send a packet to a host but knows only the
host’s IP address, the network station uses ARP to determine the host’s
physical address as follows:
—End—
1. The network station broadcasts a special packet, called an ARP request,
that asks thehost at the specified IP address to respond with its physical
address.
2. All network hosts receive the broadcast message.
3. Only the specified host responds with its hardware address.
4. The network station then maps the host’s IP address to its physical
address and saves the results in an address resolution table for future
use.
5. The network station’s ARP table displays the association of the known
MAC addresses to IP addresses.
Note: The default timeout value for ARP entries is 6 hours.
Static ARP entries can be created and individual ARP entries deleted.
Proxy ARP allows a network station to respond to an ARP request from a
locally attached host or end station for a remote destination. It does so by
sending an ARP response back to the local host with its own MAC address
of the network station interface for the subnet on which the ARP request
was received. The reply is generated only if the switch has an active route
to the destination network.
The figure below is an example of proxy ARP operation. In this example,
host C with a 24-bit mask appears to be locally attached to host B with a
16-bit mask, so host B sends an ARP request for host C. However, the 5500
Series switch is between the two hosts. To enable communication between
the two hosts, the 5500 Series switch would respond to the ARP request
with host C’s IP address but with its own MAC address.
Proxy ARP Operation
Static routes
Once routable VLANs are created though IP address assignment, static
routes can be created. Static routes allow for the manual creation of specific
routes to a destination IP address. Static routes can also be used to specify
a route to all networks for which there are no explicit routes in the Forwarding
Information Base or the routing table. This static default route is a route to
the network address 0.0.0.0 as defined by the IEEE RFC 1812 standard.
Because of their static nature, this type of solution is not scalable. Thus,
in a large or growing network this type of route management may not be
desirable. Also, static routes do not have the capacity to determine the
failure of paths. Thus, a router can still attempt to use a path after it has
failed.
The Nortel Ethernet Routing Switch 5500 Series supports the usage of
non-local static routes. A non-local static route is almost identical to a
static route with the exception that the next hop of the route is not directly
connected to the network entity. Non-local static routes are useful in
situations where there are multiple paths to a network and the number
of static routes could be reduced by using only one route with a remote
gateway.
Because of their static nature, this type of solution is not scalable. Thus,
in a large or growing network this type of route management may not
be desirable. Also, non-local static routes do not have the capacity to
determine the failure of paths. Thus, a router can still attempt to use a path
after it has failed.
Routing Information Protocol (RIP)
Routing Information Protocol (RIP) is a standard, dynamic routing protocol
based on the Bellman-Ford (or distance vector) algorithm. It is used as an
Interior Gateway Protocol (IGP). RIP allows routers to exchange information
to compute routes through an IPv4-based network. The hop count, or
distance, is used as a metric to determine the best path to a remote network
or host. The hop count cannot exceed 15 hops (assuming a cost of one
hop for each network).
IP routing 23
RIP is defined in RFC 1058 for RIP version 1 and RFC 2453 for RIP version
2. The most significant difference between the two versions is that RIP
version 2 supports subnet masks and next hop information in the RIP
packet.
RIP operation
RIP uses User Datagram Protocol (UDP) data packets to exchange
routing information. Each router maintains a routing table, which lists the
optimal route to every destination in the system. Each router advertises
its routing information by sending a routing information update at regular
intervals. Neighboring routers use this information to recalculate their
routing tables and retransmit the routing information. For RIP version 1,
no mask information is exchanged; the natural mask is always applied by
the router receiving the update. For RIP version 2, mask information is
always included.
The sequence of processes governed by the routing algorithm is as follows:
1. When a router starts, it initializes the RIP data structures and then waits
for indications from lower-level protocols that its interfaces are functional.
2. RIP advertisements are send on all the interfaces that are configured to
send routing information.
3. The neighbors will send their routing tables and the new router will
update its routing table based on the advertisements received.
4. From now on periodic updates are send by each router in the network to
ensure a correct routing database.
If a router does not receive an update from another router within a timeout
period, it deletes the routes served by the nonupdating router from its
routing table. However, it keeps these routes temporarily in a garbage list
and continues to advertise them with a metric of 16 for a holddown period,
so that neighbors know that the routes are unreachable. If a valid update
for a garbage route is received within the holddown period, the router adds
the route back into its routing table. If no update is received, the router
completely deletes all garbage list entries for the nonupdating router.
To prevent routing loops and to promote fast convergence, RIP uses
the mechanisms of split horizon, with or without poisoned reverse, and
triggered updates. Simple split horizon means that IP routes learned from a
neighbor are not advertised back in updates to that neighbor. Split horizon
with poisoned reverse means that these routes are advertised back to the
neighbor, but they are “poisoned” with a metric of 16, which represents
infinite hops in the network. The receiver neighbor therefore ignores this
route. Triggered updates means that a router is required to send update
messages whenever it changes the metric for a route, even if it is not yet
time for a regular update message.
RIP sends routing information updates every 30 seconds. These updates
contain information about known networks and the distances (hop count)
associated with each. For RIP version 1, no mask information is exchanged;
the natural mask is always applied by the router receiving the update. Mask
information is always included for RIP version 2.
If information about a network is not received for within the allotted timeout
period (180 seconds by default), it is removed from the routing table and the
route is moved to the garbage list . From the garbage list it will be advertised
for the allotted holdown period (120 seconds by default) with metric set to
infinity (16). These timers can be changed by configuring the RIP Interface
Timeout Timer and Holddown Timer parameters.
RIP supports the following standard behavior:
•
periodic RIP updates about effective best routes
•
garbage collection
•
split horizon with or without poisoned reverse
•
triggered update for changed RIP routes
•
unicast to the specific query requestor
•
broadcast/multicast of regular and triggered updates
routing table update based on the received RIP message
•
global update timer
•
holddown timer and timeout timer per device and per interface
•
cost per device and per interface
The Nortel Ethernet Routing Switch 5500 Series implementation of RIP
also supports the following features:
•
in and out routing policies
•
auto-aggregation (also known as auto-summarization) of groups of
adjacent routes into single entries
Many RIP features are configurable. The actual behavior of the protocol
depends on the feature configurations.
RIP metrics
RIP is known as a distance vector protocol. The vector is the network
number and next hop, and the distance is the cost associated with the
network number. RIP identifies network reachability based on cost, and
cost is defined as hop count. The distance from one router to the next is
considered to be one hop. This cost or hop count is known as the metric The
illustration below depicts the hop counts between various units in a network.
RIP hop counts
A directly connected network has a metric of zero. An unreachable network
has a metric of 16. Therefore, 15 hops or 15 routers is the highest possible
metric between any two networks.
RIP can be configured to use a number of different send and receive modes
depending on the specifics of the network configuration. The following table
lists the send and receive modes supported.
RIP send and receive modes
Send Mode
DescriptionResult
rip1compThis mode is used to
broadcast RIP version
2 updates using RFC
1058 route consumption
rules. This is the default
send mode for the Nortel
Ethernet Routing Switch
5500 Series.
rip1This mode is used to
broadcast RIP updates
that are compliant with
RFC 1058.
•
Destination MAC is a broadcast,
ff-ff-ff-ff-ff-ff
•
Destination IP is a broadcast
for the network (for example,
192.1.2.255)
•
RIP Update is formed as a
RIP version 2 update, including
network mask
•
RIP version = 2
•Destination MAC is a broadcast,
ff-ff-ff-ff-ff-ff
•Destination IP is a broadcast
for the network (for example,
192.1.2.255)
•
RIP Update is formed as a RIP
version 1 update, no network
mask included
Destination IP is the RIP version
2 multicast address, 224.0.0.9
•
RIP Update is formed as a
RIP version 2 update including
network mask
•
RIP version = 2
None
on the interface.
Result
Nortel Ethernet Routing Switch 5500 Series
Configuration-IP Routing Protocols
NN47200-503 03.01 Standard
5.1 27 August 2007
rip1OrRip2RIP version 1 or RIP version 2 updates are accepted.
rip1RIP version 1 and RIP version 1 compatible updates only are
accepted.
rip2RIP version 2 updates only are accepted.
Limitations
RIP has the following limitations:
•
The protocol is limited to networks whose longest path is 15 hops.
•
The protocol depends on counting to infinity to resolve certain unusual
situations.
•
The protocol uses fixed metrics (the hop number)to compare alternative
routes, as opposed to real-time parameters such as measured delay,
reliability, or load.
•
RIP does not support address-less links.
Open Shortest Path First (OSPF) protocol
The Open Shortest Path First (OSPF) Protocol is an Interior Gateway
Protocol (IGP) that distributes routing information between routers belonging
to a single autonomous system (AS). Intended for use in large networks,
OSPF is a link-state protocol which supports IP subnetting and the tagging
of externally-derived routing information.
IP routing 27
Note: The Nortel Ethernet Routing Switch 5500 Series implementation
of OSPF only supports broadcast and passive interfaces. Point-to-point
and NBMA interfaces are not supported.
Overview
In an OSPF network, each router maintains a link-state database that
describes the topology of the autonomous system (AS). The database
contains the local state for each router in the AS, including the router’s
usable interfaces and reachable neighbors.
Each router periodically checks for changes in its local state and shares any
changes detected by flooding link-state advertisements (LSAs) throughout
the AS. Routers synchronize their topological databases based on the
sharing of information from LSAs.
From the topological database, each router constructs a shortest-path tree,
with itself as the root. The shortest-path tree gives the optimal route to each
destination in the AS. Routing information from outside the AS appears on
the tree as leaves.
OSPF routes IP traffic based solely on the destination IP address and
subnet mask contained in the IP packet header.
Benefits in large networks OSPF offers the following benefits:
•
Fast convergence
In the event of topological changes, OSPF recalculates routes quickly.
•
Minimal routing protocol traffic
Unlike distance vector routing protocols such as RIP, OSPF generates a
minimum of routing protocol traffic.
•
Load sharing
OSPF provides support for equal-cost multipath routing. If several
equal-cost routes to a destination exist, traffic is distributed equally
among them.
•
Because OSPF does not use hop count in its calculation, the routing
domain is scalable.
OSPF routing algorithm
A separate copy of the OSPF routing algorithm runs in each area. Routers
which are connected to multiple areas run multiple copies of the algorithm.
The sequence of processes governed by the routing algorithm is as follows:
1. When a router starts, it initializes the OSPF data structures and then
waits for indications from lower-level protocols that its interfaces are
functional.
2. A router then uses the Hello Protocol to discover neighbors. On
point-to-point and broadcast networks the router dynamically detects
its neighbors by sending hello packets to the multicast address
AllSPFRouters. On non-broadcast multiaccess networks, some
configuration information is required in order to discover neighbors.
3. On all multiaccess networks (broadcast or non-broadcast), the Hello
Protocol also elects a DR for the network.
4. The router attempts to form adjacencies with some of its neighbors.
On multiaccess networks, the DR determines which routers become
adjacent. This behavior does not occur if a router is configured as a
passive interface, because passive interfaces do not form adjacencies.
5. Adjacent neighbors synchronize their topological databases.
6. The router periodically advertises its link-state, and also does so when
its local state changes. LSAs include information about adjacencies
enabling quick detection of dead routers on the network.
7. LSAs are flooded throughout the area, ensuring that all routers in an
area have exactly the same topological database.
8. From this database each router calculates a shortest-path tree, with
itself as root. This shortest-path tree in turn yields a routing table for
the protocol.
OSPF router types
Routers in an OSPF network can take on different roles depending their
configuration. The following table describes the router types in an OSPF
network.
OSPF router types
Router TypeDescription
Autonomous System
Boundary Router
(ASBR)
Area Border Router
(ABR)
Internal Router (IR)A router that has interfaces only within a single area
Designated Router
(DR)
Backup Designated
Router (BDR)
A router attached at the edge of an OSPF network
is called an AS boundary router (ASBR). An ASBR
generally has one or more interfaces that run an
inter-domain routing protocol. In addition, any router
distributing static routes or RIP routes into OSPF is
considered an ASBR. The ASBR forwards external
routes into the OSPF domain. In this way, routers inside
the OSPF network learn about destinations outside their
domain.
A router attached to two or more areas inside an OSPF
network is considered an area border router (ABR). ABRs
play an important role in OSPF networks by condensing
the amount of OSPF information that is disseminated.
inside an OSPF network is considered an internal router
(IR). Unlike ABRs, IRs have topological information only
about the area in which they are contained.
In a broadcast network a single router is elected to
be the designated router (DR) for that network. A DR
assumes the responsibility of making sure all routers on
the network are synchronized with one another and also
advertises that network to the rest of the AS.
A backup designated router (BDR) is elected in addition
to the designated router (DR) and, in the event of failure
of the DR, will assume its role quickly.
OSPF host route
An OSPF router with hosts directly attached to its interfaces can use host
routes to advertise the attached hosts to its neighbors. You can configure
up to 32 host routes.
Host routes are managed with Nortel Networks Command Line Interface
(NNCLI) commands and SNMP MIBs and are identified by the host IP
address and the configured route type of service (TOS). For each host
directly connected to the router, configure the cost of the link to the host
during host creation. You cannot modify this cost.
Note: Always set TOS to 0 because TOS-based routing is not
supported.
When a host is added to, or deleted from, a host route, the router updates
the router LSAs and floods them to neighbors in each area where that
router has an interface.
Followingis an exampleof parameters fora host route advertised in the LSA.
Host route in LSA
•
Type: 3 (stub network)
•
LinkID: IP address of host directly connected to router
•
Link Data: 0xFFFFFFFF
•
Metric: configured cost of host
OSPF Enhancements
•
Host route - Allows a router to advertise to its neighbors all hosts that
are directly attached to that router’s interfaces. Up to 32 host routes
can be configured.
•
Virtual links - The OSPF network can be partitioned into multiple
areas. However, a backbone area must exist and be contiguous, and
every non-backbone area must be connected to the backbone area
using either a physical or a logical link. In a network where a physical
connection between the non-backbone area and backbone area is
impossible, use of a virtual link provides the logical connection through
another non-backbone area, called the transit area. Virtual links can be
created manually or automatically. The 5500 Series switch supports
up to 16 virtual links.
When 5500 Series switches are stacked, and a unit leaves the stack and
becomes standalone, the router ID is automatically changed to its default
value if IP blocking is turned off and OSPF is globally enabled. This
prevents duplication of a router ID in the OSPF routing domain. The new
router ID value is temporary, that is, it is not saved to NVRAM. Therefore,
upon reset, the old router ID is restored. Configurable using NNCLI, ACG,
and Device Manager.
Example configurationsThe following is an example for creating a host
route:
R3(config)#router ospf
R3(config-router)#host-route 11.11.11.111 metric 10
R3(config-router)#show ip ospf host-route
Host IPMetric
11.11.11.11110
R3(config-router)#
The following is an example for deleting a host route:
Deleting Host Route
Example : 1
R3(config-router)#no host-route 11.11.11.111
R3(config-router)#show ip ospf host-route
Host IPMetric
IP routing 31
R3(config-router)#
OSPF virtual link
On an OSPF network, a router acting as an area boundary router (ABR)
must be directly connected to the backbone. If no physical connection is
available, you can create a virtual link.
A virtual link is established between two endpoint ABRs and is a logical
connection to the backbone area through a non-backbone area called a
transit area. In the following diagram, non-backbone ABR 2 establishes a
virtual link with backbone ABR1 across transition area, area 1. The virtual
link connects area 2 to area 0.
A virtual link can be created manually or automatically.
Manual virtual link creation can conserve resources and provide specific
control of virtual link placement in the OSPF configuration.
To add a virtual link manually, configure both endpoint ABRs with a neighbor
router ID and transit area ID. You can configure up to 16 virtual links.
Note: You can modify parameters for manually added virtual links.
To accept automatic virtual link creation, enable automatic virtual link on
both endpoint ABRs (the default value is disabled). Automatic virtual links
are removed when the transit area is deleted, auto virtual link is disabled,
or the router is no longer an ABR.
Note: Auto-created virtual links use default settings that cannot be
modified.
In this case, R4 in Area2 cannot be physically connected to Area0 (for some
reason) and it will be connected to R3 which is NOT a backbone ABR (like
R1 is for instance). As Area2 is not directly connected to backboneArea0 or
directly connected to a backbone ABR router, clients from Area2 will not be
able to access anything outside Area2. Also, router R3 is an ABR router
connected to two non-backbone areas.
In order to solve these problems, virtual-link must be configured between
router R3 and R1 which are both ABRs. Virtual-link cannot be configured
on non-ABR routers.
Consider the following Router IDs:
•
R1 : 1.0.0.0
•
R3 : 3.0.1.0
•
R4 : 4.0.2.0
Virtual-link can be configured in two ways on ABR routers :
•
Configuring virtual link manually
•
Configuring virtual link automatically
The following is an example for creating an auto virtual link:
Creating auto virtual link
R1 (config-router)#auto-vlink
Example : 1
R1(config)#show ip ospf
Router ID:1.0.0.0
Admin Status:Enabled
Version Number:2
Area Border Router Oper Status:True
AS Boundary Router Config Status:False
External Link-State Advertisements:0
External Link-State Checksum:0(0x0)
Type-of-Service (TOS) Routing Supported:False
Originated Link-State Advertisements:67
New Link-State Advertisements Received:722
Router ID:3.0.1.0
Admin Status:Enabled
Version Number:2
Area Border Router Oper Status:True
AS Boundary Router Config Status:False
External Link-State Advertisements:0
External Link-State Checksum:0(0x0)
Type-of-Service (TOS) Routing Supported:False
Originated Link-State Advertisements:67
New Link-State Advertisements Received:722
OSPF Traps:Disabled
Auto Virtual Link Creation:Disabled
SPF Hold-Down Time:10
RFC 1583 Compatibility:Enabled
Virtual-Link can also be configured using the Java Device Manager (JDM).
Just go under IP Routing > OSPF menu. There you can find : ‘General’ tab
for Auto-Vlink creation, ‘Virtual If’ tab, and ‘Virtual Neighbors’ tab.
Route policies
Route policies are a Nortel proprietary improvement on existing routing
schemes. Using existing routing schemes, packets are forwarded based
on routes that have been learned by the router through routing protocols
such as RIP and OSPF or through the introduction of static routes. Route
policies introduce the ability to forward packets based on rule sets created
by the network administrator. These rule sets, or policies, are then applied
to the learned or static routes.
IP routing 35
Route policies on the Nortel Ethernet Routing Switch 5500 Series supports
the Routing Information Protocol (RIP) and Open Shortest Path First
(OSPF) protocol. When used in conjunction with these protocols, route
policies can be used to perform the following tasks that are not possible
using traditional routing methods:
•
Listen for routing updates from specific gateways.
•
Listen for routing updates from specific networks.
•
Assign a specific subnet mask to be included with a network in the
routing table.
•
Advertise routing updates from specific gateways.
•
Advertise routing updates to specific networks.
•
Assign a specific subnet mask to be included in the route summary
packets.
•
Advertise routes learned by one protocol to another.
Route policies supports the following types of policies:
•Accept (In) Policies
Accept polices are applied to incoming routing updates before they are
applied to the routing table. In the case of RIP, accept policies can be
applied to all incoming packets and only one policy can be created
for each RIP interface. In the case of OSPF, accept policies are only
applied to Type 5 External routes based on the advertising router ID.
There can only be one OSPF accept policy per switch and the policy
is applied before updates are added to the routing table from the link
state database.
•Announce (Out) Policies
Announce policies are applied to outgoing routing updates before
the routing update packets are actually transmitted from the switch.
In the case of RIP, announce policies can be applied to all outgoing
packets and only one policy can be created for each RIP interface.
Announce policies are not supported for OSPF as OSPF requires
routing information to be consistent throughout the OSPF domain.
•Redistribution Policies
Redistribution policies are used to provide notification of addition or
deletion of a route in the routing table by one protocol to another
protocol. OSPF redistribution policies send redistributed routes as Type
5 External routes. There can be only one OSPF redistribution route per
switch and it must be configured as a ASBR with redistribution enabled.
Route policies consist of the following items:
•Prefix Lists
— List of IP addresses with subnet masks.
— Identified by a prefix list name and unique identifier.
— Prefix lists support the comparison of ranges of incoming masks.
•Route Maps
— Contain a set of match and set parameters.
— Match and set parameters can contain several prefix lists.
— A set of match and set parameters are identified by a sequence
number.
— Accept and deny actions are associated with each sequenced
parameter set.
— Sequence numbers act as a preference setting. Sets with a lower
sequence number are preferred over those with a higher sequence
number.
To configure routing policies, create the appropriate prefix lists and then
assign those prefix lists to route maps. Once all route maps have been
created, assign them to the appropriate type of policy.
In a stacked environment, the following rules are applied to routing policies:
•
The policy database is stored in all stack units.
•
Policy configuration is supported from only the base unit. The base
unit sends updates to non-base units to update the policy database in
each stack unit.
•
During database updates, only the database in the base unit is
synchronized with the non-base unit. The database in the non-base
units are deleted during the exchange.
•
Only the policies stored in the base unit are used by RIP and OSPF
for policy application.
Virtual Router Redundancy Protocol (VRRP)
The Virtual Router Redundancy Protocol (VRRP) is designed to eliminate
the single point of failure that can occur when the single static default
gateway router for an end station is lost. VRRP introduces the concept of
a virtual IP address (transparent to users) shared between two or more
routers connecting a common subnet to the enterprise network. With the
virtual IP address as the default gateway on end hosts, VRRP provides
dynamic default gateway redundancy in the event of failure.
IP routing 37
VRRP uses the following terms:
•VRRP router - a router running the VRRP protocol.
•
Virtual router - the abstract object managed by VRRP that is assigned
the virtual IP address and that acts as the default router for a set of IP
addresses across a common network. Each virtual router is assigned a
virtual router ID.
•
Virtual router master - the VRRP router that assumes responsibility
for forwarding packets sent to the IP address associated with the virtual
router. The master router also responds to packets sent to the virtual
router IP address and answers ARP requests for this IP address.
•
Virtual router backup - the router or routers that can serve as the
failover router if the master router becomes unavailable. If the master
router fails, an election process provides a dynamic transition of
forwarding responsibility to a new master router.
•Priority - an 8-bit value assigned to all VRRP routers. A higher value
represents a higher priority for election to the master router. The priority
can be a value from 1 to 255. When a master router fails, an election
process takes place among the backup routers to dynamically reassign
the role of the master router.
The Equal Cost MultiPath (ECMP) feature allows routers to determine equal
cost paths to the same destination prefix. The multiple paths can be used
for load sharing of traffic and allows faster convergence to other active paths
in case of network failure. By maximizing load sharing among equal-cost
paths, links between routers can be used more efficiently when sending
IP traffic. The ECMP feature supports and complements the following
protocols types:
•
Open Shortest Path First (OSPF)
•
Routing Information Protocol (RIP)
•
Static Routes
ECMP is only supported on the Nortel Ethernet Routing Switch 5520 and
5530. ECMP will work in a mixed stack but will not run on any Nortel
Ethernet Routing Switch 5510 units in the stack.
UDP broadcast forwarding
Some network applications, such as the NetBIOS name service, rely
on User Datagram Protocol (UDP) broadcasts to request a service or
locate a application. If a host is on a network, subnet segment, or VLAN
that includes a server for the service, UDP broadcasts are by default not
forwarded to the server located on a different network segment or VLAN.
This is resolved by forwarding the broadcasts to the server through physical
or virtual interfaces.
UDP broadcast forwarding is a general mechanism for selectively forwarding
limited UDP broadcasts received on an IP interface to a configured IP
address. The packet is sent as a unicast packet to the server.
The following are the basic steps for UDP broadcast forwarding
configuration:
1. Enter the UDP protocols to be forwarded.
2. Create forwarding policies by defining UDP protocol and server pairs.
3. Assemble these policies into lists.
4. Apply these lists to the appropriate interfaces.
When a UDP broadcast is received on a router interface, it must meet the
following criteria if it is to be considered for forwarding:
For each ingress interface and protocol, the UDP broadcast packets are
forwarded only to a unicast host address (the unicast IP address of the
server for example).
The Dynamic Host Configuration Protocol (DHCP) is an extension of the
Bootstrap protocol (BootP) and provides host configuration information to
workstations on a dynamic basis. To lower administrative overhead, network
managers prefer to configure a small number of DHCP servers in a central
location. It is necessary for routers to support the BootP/DHCP relay
function so that hosts can access configuration information from servers
several router hops away.
Differences between DHCP and BootP
The following differences between DHCP and BootP are specified in RFC
2131 and include functions that BootP does not address:
•
The Nortel Ethernet Routing Switch 5500 Series supports the Bootstrap
protocol (BootP). BootP enables the retrieval of an ASCII configuration
file name and configuration server address.
•
A properly configured BootP server enables the switch to automatically
learn its assigned IP address, subnet mask and the IP address of the
default router (default gateway).
•
DHCP defines mechanisms through which clients can be assigned a
network address for a finite lease (allowing for reuse of IP addresses).
•
DHCP provides the mechanism for clients to acquire all of the IP
configuration parameters needed to operate.
DHCP uses the BootP message format defined in RFC 951. The remainder
of the options field consists of a list of tagged parameters that are called
"options" (RFC 2131).
Summary of DHCP relay operation
BootP/DHCP clients (workstations) generally use UDP/IP broadcasts to
determine their IP addresses and configuration information. If such a host
is on a network or a subnet segment (or VLAN) that does not include a
DHCP server, the UDP broadcasts are by default not forwarded to the
server located on a different network segment or VLAN. The Nortel Ethernet
Routing Switch 5500 Series can be configured to resolve this issue by
forwarding the broadcasts to the server. The router interfaces can be
configured to forward DHCP broadcasts to other locally connected network
segments or directly to the server’s IP address. DHCP must be enabled
on a per-VLAN basis.
"DHCP operation" (page 40)Figure DHCP operation shows an end station
connected to subnet 1, corresponding to VLAN 1. The Nortel Ethernet
Routing Switch 5500 Series connects two subnets by means of the virtual
routing function. When the end station generates a DHCP request as a
limited UDP broadcast to the IP address of all 1s (that is, 255.255.255.255)
with the DHCP relay function configured, the Nortel Ethernet Routing Switch
5500 Series forwards DHCP requests to subnet 2 or to the host address of
the DHCP server, depending on the configuration.
DHCP operation
Forwarding DHCP packets
In the example shown in "Forwarding DHCP packets" (page 40), the agent
address is 10.10.1.254. To configure the Nortel Ethernet Routing Switch
5500 Series to forward DHCP packets from the end station to the server,
use 10.10.2.1 as the server address.
Forwarding DHCP packets
All BootP broadcast packets, including DHCP packets that appear on the
VLAN 1 router interface (10.10.1.254), will be forwarded to the DHCP
server. In this case, the DHCP packets are forwarded as unicast to the
DHCP server’s IP address.
Multiple BootP-DHCP servers
Most enterprise networks use multiple BootP/DHCP servers for fault
tolerance. The Nortel Ethernet Routing Switch 5500 Series allows switch
configuration to forward BootP/DHCP requests to multiple servers. Up to 10
servers can be configured to receive copies of the forwarded BootP/DHCP
messages.
If a DHCP client is connected to a routable interface, to configure DHCP
requests to be sent to up to 512 different routable interfaces or 512 different
server IP addresses, enable DHCP on the client (agent address) and then
enable DHCP from the client to each of the interfaces or IP addresses
(server addresses).
In the example shown in "Multiple BootP/DHCP servers" (page 41),two
DHCP servers are located on two different subnets. To configure the
Nortel Ethernet Routing Switch 5500 Series to forward the copies of the
BootP/DHCP packets from the end station to both servers, specify the switch
(10.10.1.254) as the agent address. Then enable DHCP to each of the
DHCP servers by entering 10.10.2.1 and 10.10.3.1 as the server addresses.
Multiple BootP/DHCP servers
Setting DHCP
To set DHCP, take the following steps:
StepAction
1EnableIP routing on the Nortel Ethernet Routing Switch 5500 Series
and on the target VLAN interface.
2
3
4
5
6
Enable DHCP globally.
Note: DHCP is enabled by default.
Set the DHCP forwarding paths, using the VLAN IP as the starting
point, or agent IP.
Set the mode for each DHCP forwarding path.
Enable DHCP for the specific VLAN.
Enable the DHCP broadcast message for the specific VLAN.
Any of the Nortel Ethernet Routing Switch 5500 Series switch management
systems can be used to set DHCP.
DHCP relay
DHCP (Dynamic Host Configuration Protocol) is a mechanism to assign
network IP addresses to clients who request an address. It is built on top
of the existing BOOTP protocol and can be specified for DHCP, BOOTP,
or both.
The DHCP relay feature relays client requests to DHCP servers on different
L3 VLANs. It also relays server replies back to the clients.
DHCP relay can be configured through Command Line Interface or Java
Device Manager. DHCP can only be configured on the base unit from
CLI, like all L3 commands. There are three parts in the DHCP relay
configurations. They are:
•
global DHCP enable/disable
•interface configurations
•
forward path configurations
To relay DHCP messages, two VLANs must be created and IP addresses
assigned to them. The client and server must reside on different L3 VLANS
to use DHCP relay. IP routing and global DHCP relay must be enabled
on both the client as well as server.
Note: The DHCP Relay feature shares resources with QoS. If the
DHCP Relay feature is enabled, a QoS policy with a precedence of 11
cannot be installed.
For further information on QoS policies refer to Nortel Ethernet RoutingSwitch 5500 Series Configuration - Quality of Service (Part Number
NN47200-504).
Global DHCP relay configurationThis configuration enables or disables
DHCP relay for the entire unit or stack. Once DHCP relay is disabled, the
switch/stack will not relay DHCP/BOOTP " Global DHCP relay commands"
(page 42)across L3 VLANs. However, the settings will still be configurable.
describes the global DHCP relay commands.
Global DHCP relay commands
Command
show ip dhcp-relayshows global DHCP relay state
Description
no ip dhcp-relaydisables DHCP relay globally
ip dhcp-relayenables DHCP relay globally
These commands must be executed in the Global Configuration command
mode.
Interface DHCP relay configurationsThese configurations are
associated with the L3 VLAN that the client or server resides on. IP routing
must be enabled and a valid IP address must be assigned to the L3 VLAN
before it generates the default settings for DHCP relay.
"Interface DHCP relay commands" (page 43)describes the interface DHCP
relay commands. To change the interface DHCP relay configurations, switch
to the Interface Configuration command mode.
Interface DHCP relay commands
Command
show vlan dhcp-relayshows vlan dhcp relay state
ip dhcp-relay min-sec 30sets min-sec to 30
ip dhcp-relay mode dhcpsets mode to dhcp
no ip dhcp-relaydisables ip dhcp-relay
ip dhcp-relay broadcastenables broadcast for this interface
Description
DHCP Relay forward path configurationsThese configurations are
made per interface IP address and server IP address. " DHCP relay forward
DHCP relay uses a hardware resource that is shared by switch Quality of
Service applications. When DHCP relay is enabled globally, the Quality
of Service filter manager will not be able to use precedence 11 for
configurations. For the filter manager to be able to use this resource, DHCP
relay must be disabled for the entire unit or stack.
Avoiding duplicate IP addresses
The Nortel Ethernet Routing Switch 5500 Series has built-in safeguards to
avoid issuing duplicate IP addresses, because the switch functions as a
stack as well as a stand-alone system. These safeguards apply to stack
configuration changes (for example, when a stack is forming or after a unit
is removed from a stack).
The system allows the use of an existing IP address under the following
conditions:
•
When a unit leaves a stack:
— If the unit was the acting Base Unit (BU) of the stack and the stack
consisted of only two units.
— If the IP blocking mode in the stack was set to none.
•
When a unit boots up:
— If the unit was never in a stack.
— If IP blocking was manually turned off prior to the current boot.
— If the unit was the designated Base Unit (BU); that is, selected by
hardware switch on the unit, either on the back or on the UI button
on the front; and the stack consisted of only two units.
— If the IP blocking mode was set to none.
If the desired switch IP address is blocked by the system, then the address
must be configured manually in the command line interface.
Automatic router ID change
If a unit leaves the stack and becomes standalone (when the stack disjoins),
the router ID is automatically changed to its default value. This prevents
router ID duplication in the OSPF routing domain.
Prerequisites: IP blocking must be turned off (set to none) and OSPF
must be globally enabled.
TIP: The change in router ID is temporary (not saved in non-volatile random
access memory) and, upon reset, the router ID is restored.
IP Blocking is a Layer 3 feature of the Nortel Ethernet Routing Switch
5500 Series that provides built-in safeguards for the usage of duplicate IP
addresses in a stacked environment. IP Blocking is used whenever a unit
leaves a stack or is rebooting inside the context of a stack. Depending on
the setting in use, Layer 3 functionality is either continued or blocked by
this feature.
IP Blocking can exist in either a none or full condition. When IP Blocking
is set to none, duplicate IP addresses are permitted in the stack
unconditionally. When the full condition is set, duplicate IP addresses are
blocked in the stack unconditionally.
In a stack environment, Nortel recommends that IP blocking mode none be
used in a stack of 2 units. In such a stack environment and IP blocking
mode combination, the following functional characteristics can be expected:
•
IP routing 45
If the stack base unit becomes non-operational the following will occur:
— Layer 3 functionality will continue to run on the non-base unit.
— Dynamic routing protocols still run on the non-base unit.
•
If the stack non-base unit becomes non-operational the following will
occur:
— Layer 3 functionality will continue to run on the base unit.
— Dynamic routing protocols run on the base unit.
A disadvantage of this configuration is that if the non-operational unit does
not rejoin the stack, address duplication will occur.
In stack environments of more than 2 units, Nortel recommends using IP
blocking mode full. In such a stack environment and IP blocking mode
combination, the following functional characteristics can be expected:
•If the stack base unit becomes non-operational the following will occur:
— The temporary base unit takes over base unit duties.
— The temporary base unit runs the Layer 3 and DRP functionality.
— The takeover of the temporary base unit will cause the MAC
addresses of the Layer 3 interfaces to change and the MAC
addresses from the temporary base unit MAC address pool are
used. This may cause a minor disruption in routing traffic. To
facilitate quick failoverin this instance, gratuitous ARP messages are
sent out for each interface for 5 minutes at 15 second intervals.
•
If a stack non-base unit becomes non-operational the following will
occur:
— The stack will continue to run normally with the base unit controlling
Layer 3 and DRP functionality.
— If the non-operational non-base unit does not rejoin the stack, no
Layer 3 or DRP functionality will run on it.
IGMP snooping
The Nortel Ethernet Routing Switch 5500 Series can sense Internet Group
Management Protocol (IGMP) host membership reports from attached
stations and use this information to set up a dedicated path between the
requesting station and a local IP Multicast router. After the pathway is
established, the Nortel Ethernet Routing Switch 5500 Series switch blocks
the IP Multicast stream from exiting any other port that does not connect to
another host member, thus conserving bandwidth. The following section
describes how Nortel Ethernet Routing Switch 5500 Series switches provide
the same benefit as IP Multicast routers, but in the local area.
IGMP is used by IP Multicast routers to learn about the existence of host
group members on their directly attached subnets (see RFC 2236). The IP
Multicast routers get this information by broadcasting IGMP queries and
listening for IP hosts reporting their host group memberships. This process
is used to set up a client/server relationship between an IP Multicast source
that provides the data streams and the clients that want to receive the data.
By default, unknown multicast traffic is flooded to all ports in a VLAN. In
situations in which there is a multicast transmitter that is not doing IGMP
and there are no multicast receivers, the traffic transmitted by the transmitter
is flooded.
The CLI commands for IGMP allow the sending of all unknown multicast
traffic to IGMP static router ports only. This traffic will not be forwarded to
dynamically discovered m-router ports. If it is desirable to forward unknown
unicast traffic to certain ports only, those ports can be set as static m-router
ports.
•When disabled, the Nortel Ethernet Routing Switch 5500 Series switch
treats unknown multicast traffic as it does broadcast traffic (flood). This
is the default behavior.
•
User settings for the Unknown Multicast No Flood feature is stored in
NVRAM. In a stack, if settings on different units differ, the Base Unit
setting will take precedence. This feature can be enabled or disabled
at any time.
•
Nortel Networks recommends this feature be enabled when IGMP
snooping is enabled.
"IP multicast propagation with IGMP routing" (page 47)shows how IGMP
is used to set up the path between the client and server. As shown in this
example, the IGMP host provides an IP Multicast stream to designated
routers that forward the IP Multicast stream on their local network only
if there is a recipient.
The client/server path is set up as follows:
1. The designated router sends out a host membership query to the subnet
and receives host membership reports from end stations on the subnet.
2. The designated routers then set up a path between the IP Multicast
stream source and the end stations.
3. Periodically, the router continues to query end stations about whether
to continue participation.
4. As long as any client continues to participate, all clients, including
non-participating end stations on that subnet, receive the IP Multicast
stream.
Note: Although the non-participating end stations can filter the IP
Multicast traffic, the IP Multicast traffic still exists on the subnet and
consumes bandwidth.
IP Multicast can be optimized in a LAN by using IP Multicast filtering
switches, such as the Nortel Ethernet Routing Switch 5500 Series.
As shown in "IP multicast propagation with IGMP routing" (page 47),a
non-IP Multicast filtering switch causes IP Multicast traffic to be sent to
all segments on the local subnet.
The Nortel Ethernet Routing Switch 5500 Series can automatically set up IP
Multicast filters so the IP Multicast traffic is only directed to the participating
end nodes (see ).
In , "5500 Series switch filtering IP multicast streams (1 of 2)" (page
48)switches S1 to S4 represent a LAN connected to an IP Multicast router.
The router periodically sends Host Membership Queries to the LAN and
listens for a response from end stations. All of the clients connected to
switches S1 to S4 are aware of the queries from the router.
One client, connected to S2, responds with a host membership report.
Switch S2 intercepts the report from that port, and generates a proxy report
to its upstream neighbor, S1. Also, two clients connected to S4 respond
with host membership reports, causing S4 to intercept the reports and to
generate a consolidated proxy report to its upstream neighbor, S1.
5500 Series switch filtering IP multicast streams (1 of 2)
Switch S1 treats the consolidated proxy reports from S2 and S4 as if
they were reports from any client connected to its ports, and generates a
consolidated proxy report to the designated router. In this way, the router
receives a single consolidated report from that entire subnet.
After the switches learn which ports are requesting access to the IP
Multicast stream, all other ports not responding to the queries are blocked
from receiving the IP Multicast ("5500 Series switch filtering IP multicast
5500 Series switch filtering IP multicast streams (2 of 2)
The consolidated proxy report generated by the switch remains transparent
to Layer 3 of the International Standardization Organization, Open Systems
Interconnection (ISO/OSI) model. (The switch IP address and MAC address
are not part of proxy report generation.) The last reporting IGMP group
member in each VLAN represents all of the hosts in that VLAN and IGMP
group.
IGMP snooping configuration rules
The IGMP snooping feature operates according to specific configuration
rules. When configuring the switch for IGMP snooping, consider the
following rules that determine how the configuration reacts in any network
topology:
•
There is a maximum of 240 groups on the Nortel Ethernet Routing
Switch 5500 Series.
•
A port that is configured for port mirroring cannot be configured as
a static router port.
•
If a MultiLink Trunk member is configured as a static router port, all of
the MultiLink trunk members are configured as static router ports. Also,
if a static router port is removed, and it is a MultiLink Trunk member, all
MultiLink trunk members are removed as static router port members,
automatically.
•
Static router ports must be port members of at least one VLAN.
•
The IGMP snooping feature is not STP dependent.
•
The IGMP snooping feature is not Rate Limiting dependent.
This chapter describes the configuration and management of IP routing in
the Nortel Ethernet Routing Switch 5500 Series. IP Routing configuration
is accomplished through the Command Line Interface (CLI), Web-based
Management Interface, or the Java Device Manager (JDM).
This chapter contains the following topics:
•
"IP routing initial configuration" (page 51)
•
"IP routing configuration examples" (page 120)
•
"IP routing configuration using the Java Device Manager" (page 206)
IP routing initial configuration
This section provides step by step instructions for the initial configuration of
the IP routing protocols supported by the Nortel Ethernet Routing Switch
5500 Series. For conceptual information about IP routing topics covered
in this section, refer to "An Introduction to IP Routing Protocols" (page 13).
This section contains the following topics:
51
•
"Global IP routing configuration" (page 51)
•
"Open Shortest Path First (OSPF) initial configuration" (page 52)
This chapter also contains in-depth configuration examples that can aid in
the advanced configuration of the switch. Refer to "IP routing configuration
examples" (page 120)for these advanced examples.
Global IP routing configuration
Before IP routing configuration can take place, IP routing must be globally
enabled on the switch. Use the set of commands outlined below to enter the
Global Configuration mode of the switch and enable IP routing.
5530-24TFD# enable
5530-24TFD# config terminal
5530-24TFD(config)# ip routing
Open Shortest Path First (OSPF) initial configuration
This section contains the steps necessary for the initial configuration of
OSPF on the switch. More advanced configuration examples can be found
in the "IP routing configuration examples" (page 120)section.
Basic OSPF configuration
A basic OSPF configuration will learn OSPF routes from other OSPF
devices and propagate routes to other OSPF devices. The following
procedure outlines the creation of a basic OSPF configuration:
StepAction
1Log into User EXEC mode.
5530-24TFD> enable
2Log into Global Configuration mode.
5530-24TFD# config terminal
The switch will respond with the following line:
Enter configuration commands, one per line.End with
CNTL/Z.
3
4
5
Enable IP routing globally.
5530-24TFD(config)# ip routing
Enable OSPF globally.
5530-24TFD(config)# router ospf en
Log into the OSPF router configuration mode. It is not necessary to
make any changes at this time but entering the router configuration
mode is a good way to verify that the mode has been activated.
5530-24TFD(config)# router ospf
Note: The remainder of this procedure refers to VLAN 35.
Although VLAN 35 is used for this example, any port type VLAN
could be used.
6
Create a port type VLAN as VLAN number 35 in spanning tree
protocol group 1.
5530-24TFD(config)# vlan create 35 type port 1
7
8
Log into the Interface Configuration mode for VLAN 35.
By default all ports belong to a newly created VLAN. This command
removes all of the ports from VLAN 35 .
5530-24TFD(config)# vlan members remove 35 all
13
Add ports 1 through 10 to VLAN 35.
5530-24TFD(config)# vlan members add 35 1-10
—End—
Basic ASBR configuration
The Autonomous System Boundary Router (ASBR) is used in OSPF to
import routes that come from non-OSPF sources such as:
•
Local interfaces that are not part of OSPF.
•
RIP interfaces.
•
RIP learned routes.
•
Static routes.
This quick reference will help in the configuration of OSPF to import these
types of routes. This will allow the rest of the OSPF network to learn them as
OSPF routes. To create a basic ASBR configuration, follow this procedure:
StepAction
1
2
Log into User EXEC mode.
5530-24TFD> enable
Log into Global Configuration mode.
5530-24TFD# config terminal
The switch will respond with the following line:
Enter configuration commands, one per line.End with
CNTL/Z.
This command tells the router to use up to two paths to get to any
OSPF network destination.
4
The configuration can be verified using the following command.
5530-24TFD(config)# show ecmp
IP routing configuration using the CLI
This section describes the various Command Line Interface commands
available for the configuration and management of IP routing. Depending
on the type of command and the context in which it is being used, these
commands are executed in the various CLI command modes.
IP configuration commands
This section describes the commands for the global IP configuration at
the switch level.
ip routing command
The ip routing command enables global routing at the switch level.
The syntax for the ip routing command is:
ip routing
—End—
The ip routing command is executed in the Global Configuration
command mode.
no ip routing command
The no ip routing command disables IP routing.
The syntax for the no ip routing command is:
no ip routing
The no ip routing command is executed in the Global Configuration
command mode.
ip blocking-mode command
Use this command to set the level of IP blocking to perform in the stack. The
syntax for this command is:
ip blocking-mode {full | none}
The following table outlines the parameters for this command.
fullSelect this parameter to set IP blocking to full. This
none
This command is executed in the Global Configuration command mode.
Layer 3 routable VLANs
The Nortel Ethernet Routing Switch 5500 Series are Layer 3 (L3) switches.
This means that a regular L2 VLAN becomes a routable L3 VLAN if an
IP address and MAC address are attached to the VLAN. When routing is
enabled in L3 mode, every L3 VLAN is capable of routing as well as carrying
the management traffic. The user can use any L3 VLAN instead of the
Management VLAN to manage the switch.
This section covers the commands that are used to set up and configure
routable VLANs.
never allows a duplicate IP address in a stack.
Select this parameter to set IP blocking to none.
This allows duplicate IP addresses unconditionally.
interface vlan command
The interface vlan command only takes to the interface config mode.
The ip routing command in the interface-config mode enables routing
on a specific vlan.
The syntax for the interface VLAN command is:
interface vlan <1 - 4094>
The interface VLAN command is executed in the Global Configuration
command mode.
ip address command
The ip address command enables routing on a VLAN.
The syntax for the ip address command is:
ip address<A.B.C.D> <W.X.Y.Z>[<1 - 256>] [secondary]
The ip address command is executed in the Interface Configuration
command mode.
The following table describes the parameters for this command.
<A.B.C.D>The IP address to attach to the VLAN.
<W.X.Y.Z>The subnet mask to attach to the VLAN
<1 - 256>
secondaryUse this option to set up a secondary IP interface
The MAC offset value. Specify the value 1 for the
Management VLAN only.
on a VLAN. You can have a maximum of eight
secondary IP interfaces for every primary and
the primary must be set up before any secondary
interfaces are configured.
no ip address command
The no ip address command disables routing on a VLAN.
The syntax for the no ip address command is:
no ip address<A.B.C.D> <W.X.Y.Z >
The following table describes the parameters for this command.
no ip address parameters
ParameterDescription
<A.B.C.D>The IP address to disable routing on.
<W.X.Y.Z >The subnet mask to disable routing on.
The no ip address command is executed in the Interface Configuration
command mode.
Multinetting
To add a secondary IP interface to a VLAN, known as Multinetting, use the
following procedure:
Adding secondary IP interfaces
StepAction
1
2
Put the switch into interface mode for the specific VLAN.
interface vlan <vlan #>
Create a primary interface before adding secondary interfaces (if a
primary interface has not yet been created).
ip address <ip address> <mask> [<mac offset>] secondary
Example Adding secondary IP interfaces to a VLAN
Primary and secondary interfaces must reside on different subnets. In
the following example, 4.1.0.10 is the primary IP and 4.1.1.10 is the
secondary IP.
interface vlan 4
ip address 4.1.0.10 255.255.255.0 6
ip address 4.1.0.10 255.255.255.0 6
Removing primary IP interfaces from a VLAN when secondary
interfaces are configured
StepAction
—End—
1
2
3
Put the switch into interface mode for the VLAN.
interface vlan <vlan #>
Remove the secondary IP interface from the VLAN.
no ip address <ip address secondary> <mask>
Remove the primary IP interface from the VLAN.
no ip address <ip address primary> <mask> [<mac
offset>]
—End—
Example removing primary IP interface from a VLAN when secondary
interfaces are configured
In the following example, 4.1.0.10 is the primary IP and 4.1.1.10 is the
secondary IP.
interface vlan 4
no ip address 4.1.0.10 255.255.255.0
no ip address 4.1.1.10 255.255.255.0
Example removing secondary IP interface only from a VLAN
interface vlan 4
no ip address 4.1.0.10 255.255.255.0
show vlan ip command
The show vlan ip command shows routable VLAN configurations.
The following table describes the parameters for this command.
traceroute parameters
ParameterDescription
HostnameEnter the name of the remote host.
A.B.C.D.Enter the A.B.C.D. name of the remote host.
ipEnter the IP address of the remote host.
-m
-p
-q
-v
-w
Specifies the maximum time to live (ttl). The value for this
parameter is in the rage from 1-255. The default value is 10.
Example: traceroute 10.3.2.134 -m 10
Specifies the base UDP port number. The value for this
parameter is in the range from 0-65535.
Example: traceroute 1.2.3.4 -p 87
Specifies the number of probes per time to live. The value for
this parameter is in the range from 1-255. The default value is 3.
Example: traceroute 10.3.2.134 -q 3
Specifies the wait time per probe. The value for this parameter
is in the range from 1-255. The default value is 5 seconds.
Example: traceroute 10.3.2.134 -w 15
<1-1464>
ip route weight command
The ip route weight command changes the weight, or cost, of a static
route.
The syntax for the ip route weight command is:
ip route <A.B.C.D> <W.X.Y.Z> <O.P.Q.R> weight <1-65535>
The following table outlines the parameters for this command.
ip route weight parameters
ParameterDescription
<A.B.C.D>Enter IP address of the destination point of the route
<W.X.Y.Z>Enter subnet mask address of the destination node
The no ip arp-proxy command is executed in the Layer 3 IP VLAN
Interface Configuration mode.
default ip arp-proxy command
The default ip arp-proxy command is used to return the switch to the
default proxy ARP settings.
The syntax of the default ip arp-proxy command is:
default ip arp-proxy [enable]
The default ip arp-proxy command is executed in the Layer 3 IP
VLAN Interface Configuration mode.
show ip arp-proxy interface command
The show ip arp-proxy interface command is used to display the
status of proxy ARP on an interface.
The syntax of the show ip arp-proxy interface command is:
show ip arp-proxy interface [vlan <vlan_id>]
The show ip arp-proxy interface command is executed in the User
EXEC mode.
Routing Information Protocol (RIP) commands
This section describes the CLI commands used to configure and manage
the Routing Information Protocol (RIP) on the Nortel Ethernet Routing
Switch 5500 Series. RIP is a distance vector protocol used to dynamically
discover network routes based on information passed between routers in
the network. RIP is useful in network environments where using static route
administration would be difficult.
router rip enable command
The router rip enable command is used to globally enable RIP on
the switch. RIP must be globally enabled on the switch before it becomes
operational.
The syntax of the router rip enable command is:
router rip enable
The router rip enable command is executed in the Global
Configuration command mode.
The router rip command is used to enter the Router Configuration
mode for RIP. Router Configuration mode is used to configure various
aspects of RIP, OSPF (router ospf command), and VRRP (routervrrp command).
The syntax of the router rip command is:
router rip
The router rip command is executed in the Global Configuration
command mode.
network command
The network command is used to enable RIP on an IP interface.
The syntax of the network command is:
network <ip_address>
The <ip_address> parameter represents the IP address of the interface
to be configured.
The network command is executed in the Router Configuration mode.
no network command
The no network command is used to disable RIP on an IP interface.
The syntax of the no network command is:
no network <ip_address>
The <ip_address> parameter represents the IP address of the interface
to be disabled.
The no network command is executed in the Router Configuration mode.
timers basic holddown command
The timers basic holddown command is used to set the RIP holddown
timer.
The syntax of the timers basic holddown command is:
timers basic holddown <timer_value>
The <timer_value> parameter represents a value between 0 and 360
seconds.
The timers basic holddown command is executed in the Router
Configuration mode.
timers basic timeout command
The timers basic timeout command is used to set the RIP timeout
timer.
The syntax of the timers basic timeout command is:
timers basic timeout <timer_value>
The <timer_value> parameter represents a value between 15 and
259200 seconds.
The timers basic timeout command is executed in the Router
Configuration mode.
timers basic update command
The timers basic update command is used to set the RIP update timer.
The syntax of the timers basic update command is:
timers basic update <timer_value>
The <timer_value> parameter represents a value between 0 and 360
seconds.
The default timers basic update command is executed in the
Router Configuration mode.
ip rip advertise-when-down command
The ip rip advertise-when-down command is used to enable RIP
advertisements on the interface being configured even when that interface
is not operational. The subnet on which the switch has a RIP enabled
interface is advertised even if that particular network is no longer connected
(no link in the connected VLAN is in the Link-Up state). This setting will
take effect whenever the value is changed by the user or after the first
Link-Down transition.
The syntax of the ip rip advertise-when-down command is:
ip rip advertise-when-down {enable}
Advertise when down functionality is disabled by default.
The ip rip advertise-when-down command is executed in the
The ip rip advertise-when-down command is used to disable RIP
advertisements on the interface being configured even when that interface
is not operational.
The syntax of the no ip rip advertise-when-down command is:
no ip rip advertise-when-down {enable}
The no ip rip advertise-when-down command is executed in the
Interface Configuration mode.
ip rip auto-aggregation command
The ip rip auto-aggregation command is used to enable auto
aggregation on the RIP interface. This allows for the automatic aggregation
of routes to their natural net mask when they are advertised on an interface
in a different class network.
The syntax of the ip rip auto-aggregation command is:
ip rip auto-aggregation {enable}
Auto aggregation is disabled by default.
The ip rip auto-aggregation command is executed in the Interface
Configuration mode.
no ip rip auto-aggregation command
The no ip rip auto-aggregation command is used to disable
auto-aggregation on the RIP interface.
The syntax of the no ip rip auto-aggregation command is:
no ip rip auto-aggregation {enable}
The no ip rip auto-aggregation command is executed in the
Interface Configuration mode.
ip rip cost command
The ip rip cost command is used to set the administrative path cost
of the interface.
The syntax of the ip rip cost command is:
ip rip cost <path_cost>
The <path_cost> parameter represents a value between 1 and 15.
The default path cost is 1.
The ip rip poison command is executed in the Interface Configuration
mode.
no ip rip poison command
The no ip rip poison command is used to disable poison reverse on
this RIP interface.
The syntax of the no ip rip poison command is:
no ip rip poison {enable}
The no ip rip poison command is executed in the Interface
Configuration mode.
ip rip proxy-announce command
The ip rip proxy-announce command is used to enable proxy
announcements on this RIP interface. When proxy announcements are
enabled, the source of a route and its next hop are treated as the same
when processing received updates. So, instead of the advertising router
being used as the source, the next hop is.
The syntax of the ip rip proxy-announce command is:
ip rip proxy-announce {enable}
Proxy announcements are disabled by default.
The ip rip proxy-announce command is executed in the Interface
Configuration mode.
no ip rip proxy-announce command
The no ip rip proxy-announce command is used to disable proxy
announcements on this RIP interface.
The syntax of the no ip rip proxy-announce command is:
no ip rip proxy-announce {enable}
The no ip rip proxy-announce command is executed in the Interface
Configuration mode.
ip rip receive command
The ip rip receive command is used to set the RIP version received
on this interface.
The default ip rip timeout command is used to restore the default
RIP timeout setting for the interface.
The syntax of the default ip rip timeout command is:
default ip rip timeout
The default ip rip timeout command is executed in the Interface
Configuration mode.
default ip rip triggered command
The default ip rip triggered command is used disabled triggered
updates on this switch.
The syntax of the default ip rip triggered command is:
default ip rip triggered enable
The default ip rip triggered command is executed in the Interface
Configuration mode.
Open Shortest Path First (OSPF) commands
This section describes the CLI commands used to configure and manage
the Open Shortest Path First (OSPF) protocol on the Nortel Ethernet
Routing Switch 5500 Series. The Open Shortest Path First (OSPF) Protocol
is an Interior Gateway Protocol (IGP) that distributes routing information
between routers belonging to a single autonomous system (AS). Intended
for use in large networks, OSPF is a link-state protocol which supports IP
subnetting and the tagging of externally-derived routing information.
Note: OSPFcommands used during the configuration and management
of VLANs in the Interface Configuration mode can be used to configure
any VLAN regardless of the one used to log into the command mode.
Insert the keyword vlan with the number of the VLAN to be configured
after the command keywords ip ospf. The current VLAN will remain at
the one used to log into the Interface Configuration command mode
after the command execution.
ip ospf apply accept command
The ip ospf apply accept command is used to apply OSPF accept
policies to the switch.
The syntax of the ip ospf apply accept command is:
The following table outlines the parameters for this command.
accept adv-rtr parameters
ParameterDescription
router_ip_addressThis parameter represents the IP address of the router
advertisements will be accepted from. The value 0.0.0.0
denotes that advertisements from all routers will be
accepted.
enableEnables the accept entry for the router specified in the
<ip_address> parameter.
metric-type {any |
type1 | type2}
route-policy
{policy_name}
Indicates the type of OSPF external routes that will be
accepted from this router.
Specifies the name of the route policy to be used for
filtering external routes advertised by the specified
advertising router before accepting them into the routing
table.
The accept adv-rtr command is executed in the Router Configuration
mode.
no accept adv-rtr command
The no accept adv-rtr command is used to configure the router to not
accept advertisements from another router in the system.
The syntax of the no accept adv-rtr command is:
no accept adv-rtr <router_ip_address> enable
The <router_ip_address> parameter represents the address of the router
from which advertisements will no longer be accepted. The value 0.0.0.0
denotes that advertisements from all routers will be blocked.
The no accept adv-rtr command is executed in the Router
Configuration mode.
area command
The area command is used to configure OSPF area parameters.
The syntax of the area command is:
The default cost associated with an OSPF stub area.
The area’s support for importing Autonomous System
external link state advertisements.
Controls the import of summary link state advertisements
into stub areas. This setting has no effect on other areas.
Used to specify range parameters for the OSPF area.
The area command is executed in the Router Configuration mode.
Note: The configuration of a totally stubby area (no summary
advertising) is a two step process. First, define an area with the
import flag set to noexternal. Second, disable import summaries
in the same area with the command no area <ip_address>import-summaries enable.
no area command
The no area command is used to disable configured OSPF area
parameters.
The syntax of the no area command is:
no area <ip_address> [import-summaries {enable} | range
{subnet_mask} {nssa-entlink | summary-link}]
The following table outlines the parameters for this command.
<A.B.C.D.>Specifiesthe transit area ID expressed as an IP address.
<A.B.C.D./0-32>Specifies the neighbor router ID expressed as an IP
address.
authentication-key
<WORD>
Specifies the unique identifier assigned to the
authentication key.
authentication-typeSpecifies one of the following authentication types:
•
none
•
simple
•
password
•message digest MD5
TIP: Up to 2 MD5 keys are allowed for message digest.
The default authentication type is none.
primary-md5-keySpecifies the user-selected key used to encrypt OSPF
protocol packets for transmission.
dead-intervalSpecifies the time interval, in seconds, that a Hello
packethas not been transmitted from the virtual interface
before its neighbors declare it down. Expressed as an
integer from 0-2147483647, the default dead interval
value is 60 seconds.
hello-intervalSpecifies the time interval, in seconds, between
transmission of Hello packets from the virtual interface.
Expressed as an integer from 1-65535, the hello-interval
default value is 10 seconds.
retransmit-intervalSpecifies the time interval, in seconds, between link
transit-delaySpecifies the estimated number of seconds required
The area vitual-link command is executedin the Router Configuration
mode.
no area virtual-link command
Use the no area virtual-link command to delete a virtual interface.
The syntax for the no area virtual link command is:
stage advertisement retransmissions for adjacencies
belonging to the virtual interface. Expressed as an
integer from 0-3600, the default value is 5 seconds.
to transmit a link state update packet over the virtual
interface. Expressed as an integer from 0-3600, the
default value is 1 second.
Nortel Ethernet Routing Switch 5500 Series
Configuration-IP Routing Protocols
NN47200-503 03.01 Standard
5.1 27 August 2007
94IP Routing Configuration and Management
no area virtual-link <A.B.C.D.> <W.X.Y.Z> [authenticationkey]
no area virtual-link command parameters
ParameterDescription
<A.B.C.D.>Specifies the transit area Id expressed as an IP address.
<W.X.Y.Z>Specifies the neighbor router ID expressed as an IP
address.
authentication-keySpecifies the unique identifier assigned to the
authentication key
The no area virtual-link command is executed in the Router
Configuration mode.
area virtual-link message-digest-key command
Use the area virtual-link message-digest-key command to
create a virtual interface message digest key.
The syntax for the area virtual-link message-digest-key
command is:
area virtual-link message-digest-key <A.B.C.D.> <A.B.C.D./032> <1-255> md5-key <WORD>
area virtual-link message-digest key command parameters
ParameterDescription
<A.B.C.D.>Specifies the transit area Id expressed as an IP address.
<W.X.Y.Z>Specifies the neighbor router ID expressed as an IP
address.
<1-255>
md5-key <WORD>Specifies the user-selected key used to encrypt OSPF
Specifies the primary MD5 key value, expressed as an
integer from 1-255.
protocol packets for transmission.
The area virtual-link message-digest-key command is executed
in the Router Configuration mode.
no area virtual-link message-digest-key command
Use the no area virtual-link message-digest-key command to
delete a virtual interface message digest key.
The syntax for the no area virtual-link message-digest-key
command is:
no area virtual-link message-digest-key <A.B.C.D.> <W.X.Y.Z>
<1-255>
no area virtual-link message-digest-key command parameters
ParameterDescription
<A.B.C.D.>Specifiesthe transit area ID expressed as an IP address.
<W.X.Y.Z>Specifies the neighbor router ID expressed as an IP
address.
<1-255>
Specifies the primary MD5 key value, expressed as an
integer from 1-255.
The no area virtual-link message-digest-key command is
executed in the Router Configuration mode.
auto-vlink command
Use the auto-vlink command to enable global automatic Virtual Link creation.
For more information about Virtual Link, see "OSPF virtual link" (page 31)
The syntax for the auto-vlink command is:
auto-vlink
The auto-vlink command is executed in the Router Configuration mode.
no auto-vlink command
Use the no auto-vlink command to disable global automatic Virtual
Link creation.
The syntax for the no auto-vlink command is:
no auto-vlink
The no auto-vlink command is executed in the Router Configuration
mode.
ip ospf advertise-when-down command
The ip ospf advertise-when-down command is used to enable
advertisement of the OSPF interface evenwhen the interfaceis operationally
unavailable.
The syntax of the ip ospf advertise-when-down command is:
ip ospf advertise-when-down enable
The ip ospf advertise-when-down command is executed in the
Interface Configuration mode.
The ip ospf area command is used to assign an interface to an OSPF
area.
The syntax of the ip ospf area command is:
ip ospf area <ip_address>
The <ip_address> parameter represents the unique ID of the area to
which the interface connects. An area ID of 0.0.0.0 indicates the OSPF area
backbone and is created automatically by the switch.
The ip ospf area command is executed in the Interface Configuration
mode.
ip ospf authentication-key command
The ip ospf authentication-key command is used to configure an
interface authentication password.
The syntax of the ip ospf authentication-key command is:
ip opsf authentication-key <password>
The <password> parameter is the password to be configured. This
password can be up to 8 characters in length.
The ip opsf authentication-key command is executed in the
Interface Configuration mode.
ip ospf authentication-type command
The ip ospf authentication-type command is used to configure the
interface authentication type.
The syntax of the ip ospf authentication-type command is:
ip ospf authentication-type {message-digest | simple | none}
The ip ospf authentication-type command is executed in the
Interface Configuration mode.
ip ospf cost command
The ip ospf cost command is used to assign a cost to an interface.
The syntax of the ip ospf cost command is:
ip ospf cost <interface_cost>
The <interface_cost> parameter is the cost assigned to the interface.
This is an integer value between 1 and 65535.
The ip ospf cost command is executed in the Interface Configuration
mode.
ip ospf dead-interval command
The ip ospf dead-interval command is used to configure a dead
interval for the interface. This is the interval of time that a Hello packet has
not been transmitted from this interface before its neighbors declare it down.
The syntax of the ip ospf dead-interval command is:
ip ospf dead-interval <interval>
The <interval> parameter represents the amount of time in seconds to
set this interval at. This is an integer value between 0 and 2147483647.
The ip ospf dead-interval command is executed in the Interface
Configuration mode.
ip ospf hello-interval command
The ip ospf hello-interval command is used to configure the
amount of time between transmission of hello packets from this interface.
The syntax of the ip ospf hello-interval command is:
ip ospf hello-interval <interval>
The <interval> parameter is the amount of time in seconds between
hello packets. This is an integer value between 1 and 65535.
The ip ospf hello-interval command is executed in the Interface
Configuration mode.
ip ospf mtu-ignore command
The ip ospf mtu-ignore command is used to instruct the interface to
ignore the packet MTU size specified in Database Descriptors.
The syntax of the ip ospf mtu-ignore command is:
ip ospf mtu-ignore enable
The ip ospf mtu-ignore command is executed in the Interface
Configuration mode.
ip ospf network command
The ip ospf network command is used to define the type of OSPF
interface this interface is.
The ip ospf network command is executed in the Interface
Configuration mode.
ip ospf primary-md5-key command
The ip ospf primary-md5-key command is used to configure the
primary MD5 key to use for authentication in instances where interface
authentication uses an MD5 key.
The syntax of the ip ospf primary-md5-key command is:
ip ospf primary-md5-key <key_value>
The <key_value> parameter is an integer value between 1 and 255.
The ip ospf primary-md5-key command is executed in the Interface
Configuration mode.
ip ospf priority command
The ip ospf priority command is used to assign a priority to the
interface for the purposes of Designated Router election.
The syntax of the ip ospf priority command is:
ip ospf priority <priority_value>
The <priority_value> parameter is the priority value assigned to the
interface. This is an integer value between 0 and 255.
The ip ospf priority command is executed in the Interface
Configuration mode.
ip ospf retransmit-interval command
The ip ospf retransmit-interval command is used to define the
number of seconds between link state advertisement retransmissions for
adjacencies belonging to this interface.
The syntax of the ip ospf retransmit-interval command is:
ip ospf retransmit-interval <interval>
The <interval> parameter is the number of seconds between
retransmissions. This is an integer value between 0 and 3600.
The ip ospf retransmit-interval command is executed in the
Interface Configuration mode.
The ip ospf transmit-delay command is used to define the transmit
delay for this OSPF interface.
The syntax of the ip ospf transmit-delay command is:
ip ospf transmit-delay <interval>
The <interval> parameter is the transmit delay in seconds. This is an
integer value between 0 and 3600.
The ip ospf transmit-delay command is executed in the Interface
Configuration mode.
ip ospf message-digest-key command
The ip ospf message-digest-key command is used to define the
MD5 keys referenced in the ip ospf primary-md5-key command.
The syntax of the ip ospf message-digest-key command is:
ip ospf message-digest-key <key_number> md5 <key_value>
The <key_number> parameter represents the MD5 key to be configured.
This is an integer value between 1 and 255. The <key_value> parameter
represents the value of the key being configured. This is a string value of up
to 16 characters in length.
The ip ospf message-digest-key command is executed in the
Interface Configuration mode.
OSPF show commands
OSPF functionality provides a wide range of commands used to display
statistics and configured parameters for the router. These commands are
available for use in any command mode. OSPF Show commands are
outlined in the table below.
OSPF show commands
Command
show ip ospfDisplays general information on OSPF
show ip ospf acceptDisplays information on OSPF advertising
show ip ospf area
<ip_address>
Description
configuration.
routers.
Displays configuration information about the
OSPF area specified in the <ip_address>
parameter. Omitting this parameter displays
information for all OSPF areas.
Displays configuration information about the
OSPF area range specified in the <ip_address>
parameter. Omitting this parameter displays
information for all OSPF area ranges.
show ip ospf aseDisplays information about the OSPF
Autonomous System external links state
advertisements.
show ip ospf defaultDisplays OSPF default metrics associated with
various port types.
show ip ospf default-costDisplays the default costs associated with
various port types.
show ip ospf ifstats
<ip_address> {detail |
mismatch}
Displays OSPF interface statistics. All
parameters for this command are optional. Not
specifying an address of an area will display
statistics for the backbone area.
show ip ospf int-authDisplays the authentication type and key for
each OSPF interface.
show ip ospf int-timersDisplays the configured timers for each OSPF
show ip ospf neighborDisplays information about the router’s OSPF
show ip ospf redistributeDisplays information about OSPF redistribution
show ip ospf statsDisplays OSPF statistics.
show ip ospf timer interfaceDisplays configured OSPF timers.
show ip ospf authentication
interface
show ip ospf interfaceDisplays general OSPF interface information.
show ip ospf virtual-linksDisplays OSPF virtual link information.
show ip ospf timer virtual-linksDisplays OSPF transit delay,retransmit interval,