Part No. 060187-10, Rev D
March 2005
OmniSwitch 6600 Family
Advanced Routing
Configuration Guide
Contents
.................................................................................................................................Index-iii
About This Guide ........................................................................................................... v
How is the Information Organized? .................................................................................vii
Documentation Roadmap .................................................................................................vii
Related Documentation ..................................................................................................... ix
User Manual CD ................................................................................................................ x
Technical Support .............................................................................................................. x
Configuring OSPF .......................................................................................................1-1
In This Chapter ................................................................................................................1-1
OSPF Specifications ........................................................................................................1-2
OSPF Defaults Table .......................................................................................................1-3
OSPF Quick Steps ...........................................................................................................1-4
OSPF Overview ..............................................................................................................1-7
OSPF Areas ..............................................................................................................1-8
Classification of Routers ..........................................................................................1-9
Virtual Links ..........................................................................................................1-10
Stub Areas ..............................................................................................................1-11
Not-So-Stubby-Areas ......................................................................................1-12
Totally Stubby Areas .......................................................................................1-12
Equal Cost Multi-Path (ECMP) Routing ...............................................................1-13
Non Broadcast OSPF Routing ................................................................................1-13
Configuring OSPF .........................................................................................................1-15
Preparing the Network for OSPF ...........................................................................1-16
Activating OSPF ....................................................................................................1-17
Creating an OSPF Area ..........................................................................................1-18
Creating OSPF Interfaces .......................................................................................1-22
Creating Virtual Links ............................................................................................1-25
Creating Redistribution Policies and Filters ...........................................................1-26
Configuring Router Capabilities ............................................................................1-29
Configuring Static Neighbors .................................................................................1-30
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
iii
Contents
OSPF Application Example ..........................................................................................1-32
Step 1: Prepare the Routers .............................................................................1-33
Step 2: Enable OSPF .......................................................................................1-35
Step 5: Examine the Network ..........................................................................1-37
Verifying OSPF Configuration .....................................................................................1-38
Alcatel License Agreement ............................................................................................A-1
ALCATEL INTERNETWORKING, INC. (“AII”)
SOFTWARE LICENSE AGREEMENT ...............................................................A-1
Third Party Licenses and Notices ..................................................................................A-4
C. Linux ..................................................................................................................A-5
E. University of California ...................................................................................A-10
F. Carnegie-Mellon University ............................................................................A-10
G. Random.c .........................................................................................................A-10
H. Apptitude, Inc. .................................................................................................A-11
I. Agranat .............................................................................................................A-11
J. RSA Security Inc. ............................................................................................A-11
K. Sun Microsystems, Inc. ....................................................................................A-11
L. Wind River Systems, Inc. ................................................................................A-12
M. Network Time Protocol Version 4 ...................................................................A-12
Index ...................................................................................................................... Index-1
iv
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
About This Guide
This OmniSwitch 6600 Family Advanced Routing Configuration Guide describes how to set up and moni-
tor advanced routing protocols for operation in a live network environment. The routing protocols
described in this manual are purchased as an add-on package to the base switch software.
Supported Platforms
This information in this guide applies to the following products:
• OmniSwitch 6624
• OmniSwitch 6648
• OmniSwitch 6600-U24
• OmniSwitch 6600-P24
• OmniSwitch 6602-24
• OmniSwitch 6602-48
OmniSwitch 6600 Family switches are next generation enterprise edge/workgroup switches. The
OmniSwitch 6624 and 6602-24 offer 24 copper 10/100 ports, the 6600-P24 offers 24 copper 10/100 Power
over Ethernet (PoE) ports, the 6648 and 6602-48 offer 48 copper 10/100 ports, and the 6600-U24 offers 24
fiber 100 ports.
In addition, OmniSwitch 6624/6600-U24/6648/6600-P24 switches have one expansion port that can be
used for a Gigabit Ethernet uplink module and another expansion port that can be used for a Gigabit Ether-
net uplink or a stacking module while the 6602-24/6602-48 switches offer fixed Gigabit Ethernet uplinks
and fixed stacking ports. The stacking ports on all OmniSwitch 6600 Family switches allow two to eight
OmniSwitch 6600 Family switches to be configured as one virtual chassis known as a stack.
Note. All references to OmniSwitch 6624 and 6648 switches also apply to the OmniSwitch 6600-U24,
6600-P24, 6602-24, and 6602-48 unless specified otherwise.
Unsupported Platforms
The information in this guide does not apply to the following products:
• OmniSwitch 6800, 7700, 7800, or 8800
• OmniSwitch (original version with no numeric model name)
• Omni Switch/Router
• OmniStack
• OmniAccess
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page v
Who Should Read this Manual?
About This Guide
Who Should Read this Manual?
The audience for this user guide is network administrators and IT support personnel who need to config-
ure, maintain, and monitor switches and routers in a live network. However, anyone wishing to gain
knowledge on how advanced routing software features are implemented in the OmniSwitch 6600 Family
will benefit from the material in this configuration guide.
When Should I Read this Manual?
Read this guide as soon as you are ready to integrate your OmniSwitch into your network and you are
ready to set advanced routing protocols. You should already be familiar with the basics of managing a
single OmniSwitch as described in the OmniSwitch 6600 Family Switch Management Guide.
The topics and procedures in this manual assume an understanding of the OmniSwitch directory structure
and basic switch administration commands and procedures. This manual will help you set up your
switches to route on the network using protocols.
What is in this Manual?
This configuration guide includes information about configuring Open Shortest Path First (OSPF) for rout-
ing.
What is Not in this Manual?
The configuration procedures in this manual use Command Line Interface (CLI) commands in all exam-
ples. CLI commands are text-based commands used to manage the switch through serial (console port)
connections or via Telnet sessions. Procedures for other switch management methods, such as web-based
(WebView or OmniVista) or SNMP, are outside the scope of this guide.
For information on WebView and SNMP switch management methods consult the OmniSwitch 6600
Family Switch Management Guide. Information on using WebView and OmniVista can be found in the
context-sensitive on-line help available with those network management applications.
This guide provides overview material on software features, how-to procedures, and application examples
that will enable you to begin configuring your OmniSwitch. It is not intended as a comprehensive refer-
ence to all CLI commands available in the OmniSwitch. For such a reference to all OmniSwitch 6600
Family CLI commands, consult the OmniSwitch CLI Reference Guide.
page vi
OmniSwitch 6600 Family Advanced Routing Configuration Guide March 2005
About This Guide
How is the Information Organized?
How is the Information Organized?
Quick Information. The chapter includes a specifications table that lists RFCs and IEEE specifications
supported by the software feature. In addition, this table includes other pertinent information such as mini-
mum and maximum values and sub-feature support. The chapter also includes a defaults table that lists the
default values for important parameters along with the CLI command used to configure the parameter. It
also includes a Quick Steps section, which is a procedure covering the basic steps required to get a soft-
ware feature up and running.
In-Depth Information. The chapter includes an overview section on the software feature as well as on
selected topics of that software feature. Topical sections may often lead into procedure sections that
describe how to configure the feature just described. Serious readers and advanced users will also find the
many application examples, located near the end of chapters, helpful. Application examples include
diagrams of real networks and then provide solutions using the CLI to configure a particular feature, or
more than one feature, within the illustrated network.
Documentation Roadmap
The OmniSwitch user documentation suite was designed to supply you with information at several critical
junctures of the configuration process. The following section outlines a roadmap of the manuals that will
help you at each stage of the configuration process. Under each stage, we point you to the manual or
manuals that will be most helpful to you.
Stage 1: Using the Switch for the First Time
Pertinent Documentation: OmniSwitch 6600 Family Getting Started Guide
Release Notes
A hard-copy OmniSwitch 6600 Family Getting Started Guide is included with OmniSwitch 6600 Family
switches; these guides provide all the information you need to get your switch up and running the first
time. These guides provide information on unpacking the switch, rack mounting the switch, installing
uplink and stacking modules, unlocking access control, setting the switch’s IP address, setting up a pass-
word, and setting up stacks. They also include succinct overview information on fundamental aspects of
the switch, such as hardware LEDs, the software directory structure, CLI conventions, and web-based
management.
At this time you should also familiarize yourself with the Release Notes that accompanied your switch.
This document includes important information on feature limitations that are not included in other user
guides.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page vii
Documentation Roadmap
About This Guide
Stage 2: Gaining Familiarity with Basic Switch Functions
Pertinent Documentation: OmniSwitch 6600 Family Hardware Users Guide
OmniSwitch 6600 Family Switch Management Guide
Once you have your switch up and running, you will want to begin investigating basic aspects of its hard
ware and software. Information about OmniSwitch 6600 Family hardware is provided in the OmniSwitch
6600 Family Hardware Users Guide. This guide provides specifications, illustrations, and descriptions of
all hardware components—chassis, power supplies, uplink and stacking modules, and cooling fans. They
also include steps for common procedures, such as removing and installing switch components.
The OmniSwitch 6600 Family Switch Management Guide is the primary user guide for the basic software
features on a single switch. This guide contains information on the switch directory structure, basic file
and directory utilities, switch access security, SNMP, and web-based management. It is recommended that
you read this guide before connecting your switch to the network.
Note. The OmniSwitch 6600 Family Switch Management Guide was originally known as the “OmniSwitch
6624/6648 Switch Management Guide.”
Stage 3: Integrating the Switch Into a Network
Pertinent Documentation: OmniSwitch 6600 Family Network Configuration Guide
OmniSwitch 6600 Family Advanced Routing Configuration Guide
When you are ready to connect your switch to the network, you will need to learn how the OmniSwitch
implements fundamental software features, such as 802.1Q, VLANs, Spanning Tree, and network routing
protocols. The OmniSwitch 6600 Family Network Configuration Guide contains overview information,
procedures and examples on how standard networking technologies are configured in the OmniSwitch
6600 Family.
Note. The OmniSwitch 6600 Family Network Configuration Guide was originally known as the
“OmniSwitch 6624/6648 Network Configuration Guide.”
The OmniSwitch 6600 Family Advanced Routing Configuration Guide includes configuration information
for networks using Open Shortest Path First (OSPF).
Note. The OmniSwitch 6600 Family Advanced Routing Configuration Guide was originally known as the
“OmniSwitch 66/24/6648 Advanced Routing Configuration Guide”
Anytime
The OmniSwitch CLI Reference Guide contains comprehensive information on all CLI commands
supported by the switch. This guide includes syntax, default, usage, example, related CLI command, and
CLI-to-MIB variable mapping information for all CLI commands supported by the switch. This guide can
be consulted anytime during the configuration process to find detailed and specific information on each
CLI command.
page viii
OmniSwitch 6600 Family Advanced Routing Configuration Guide March 2005
About This Guide
Related Documentation
Related Documentation
The following are the titles and descriptions of all the OmniSwitch 6600 Family user manuals:
• OmniSwitch 6600 Family Getting Started Guide
Describes the hardware and software procedures for getting an OmniSwitch 6600 Family switch up
and running. Also provides information on fundamental aspects of OmniSwitch software and stacking
architecture.
• OmniSwitch 6600 Family Hardware Users Guide
Complete technical specifications and procedures for all OmniSwitch 6600 Family chassis, power
supplies, fans, and uplink and stacking modules.
• OmniSwitch CLI Reference Guide
Complete reference to all CLI commands supported on the OmniSwitch 6600, 6800, 7700, 7800, and
8800. Includes syntax definitions, default values, examples, usage guidelines, and CLI-to-MIB vari-
able mappings.
• OmniSwitch 6600 Family Switch Management Guide
Includes procedures for readying an individual switch for integration into a network. Topics include
the software directory architecture, image rollback protections, authenticated switch access, managing
switch files, system configuration, using SNMP, and using web management software (WebView).
• OmniSwitch 6600 Family Network Configuration Guide
Includes network configuration procedures and descriptive information on all the major software
features and protocols included in the base software package. Chapters cover Layer 2 information
(Ethernet and VLAN configuration), Layer 3 information, security options (authenticated VLANs),
Quality of Service (QoS), and link aggregation.
• OmniSwitch 6600 Family Advanced Routing Configuration Guide
Includes network configuration procedures and descriptive information on all the software features and
protocols included in the advanced routing software package OSPF.
• Technical Tips, Field Notices
Includes information published by Alcatel’s Customer Support group.
• Release Note
Includes critical Open Problem Reports, feature exceptions, and other important information on the
features supported in the current release and any limitations to their support.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page ix
User Manual CD
About This Guide
User Manual CD
All user guides for the OmniSwitch 6600 Family are included on the User Manual CD that accompanied
your switch. This CD also includes user guides for other Alcatel data enterprise products. In addition, it
contains a stand-alone version of the on-line help system that is embedded in the OmniVista network
management application.
Besides the OmniVista documentation, all documentation on the User Manual CD is in PDF format and
requires the Adobe Acrobat Reader program for viewing. Acrobat Reader freeware is available at
Note. In order to take advantage of the documentation CD’s global search feature, it is recommended that
you select the option for searching PDF files before downloading Acrobat Reader freeware.
To verify that you are using Acrobat Reader with the global search option, look for the following button in
the toolbar:
Note. When printing pages from the documentation PDFs, de-select Fit to Page if it is selected in your
print dialog. Otherwise pages may print with slightly smaller margins.
Technical Support
An Alcatel service agreement brings your company the assurance of 7x24 no-excuses technical support.
You’ll also receive regular software updates to maintain and maximize your Alcatel product’s features and
functionality and on-site hardware replacement through our global network of highly qualified service
delivery partners. Additionally, with 24-hour-a-day access to Alcatel’s Service and Support web page,
you’ll be able to view and update any case (open or closed) that you have reported to Alcatel’s technical
support, open a new case or access helpful release notes, technical bulletins, and manuals. For more infor-
mation on Alcatel’s Service Programs, see our web page at eservice.ind.alcatel.com, call us at 1-800-995-
2696, or email us at [email protected].
page x
OmniSwitch 6600 Family Advanced Routing Configuration Guide March 2005
1 Configuring OSPF
Open Shortest Path First routing (OSPF) is a shortest path first (SPF), or link state, protocol. OSPF is an
interior gateway protocol (IGP) that distributes routing information between routers in a single Autono-
mous System (AS). OSPF chooses the least-cost path as the best path. OSPF is suitable for complex
networks with large numbers of routers since it provides faster convergence where multiple flows to a
single destination can be forwarded on one or more interfaces simultaneously.
In This Chapter
This chapter describes the basic components of OSPF and how to configure them through the Command
Line Interface (CLI). CLI commands are used in the configuration examples; for more details about the
syntax of commands, see the OmniSwitch CLI Reference Guide.
Configuration procedures described in this chapter include:
For information on creating and managing VLANs, see “Configuring VLANs” in the OmniSwitch 6600
Family Network Configuration Guide.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-1
OSPF Specifications
Configuring OSPF
OSPF Specifications
RFCs Supported
1370—Applicability Statement for OSPF
1587—The OSPF NSSA Option
1850—OSPF Version 2 Management Information
Base
2328—OSPF Version 2
3101—The OSPF Not-So-Stubby Area (NSSA)
Option
3623 — Graceful OSPF Restart
Maximum number of Areas (per router)
3
Maximum number of Interfaces (per router) 5
Maximum number of Link State Database
entries (per router)
5000
Maximum number of adjacencies (per
router)
16
Maximum number of ECMP gateways (per
destination)
4
Maximum number of neighbors (per router) 16
Maximum number of routes (per router) 4000 (Depending on the number of interfaces/
neighbors, this value may vary.)
page 1-2
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
OSPF Defaults Table
OSPF Defaults Table
The following table shows the default settings of the configurable OSPF parameters.
Parameter Description
Command
Default Value/Comments
ip ospf status
disabled
disabled
disabled
disabled
0
Enables OSPF.
ip ospf area status
Enables an area.
ip ospf interface status
ip ospf redist status
ip ospf exit-overflow-interval
ip ospf extlsdb-limit
Enables an interface.
Enables OSPF redistribution.
Sets the overflow interval value.
Assigns a limit to the number of
External Link-State Database
(LSDB) entries.
-1
Configures timers for Shortest Path ip ospf spf-timer
First (SPF) calculation.
delay: 5
hold: 10
Creates or deletes an area default
metric.
ip ospf area default-metric
ToS: 0
Type: OSPF
Cost: 1
Configures OSPF interface dead
interval.
ip ospf interface dead-interval
ip ospf interface hello-interval
40 seconds (broadcast and
point-to-point)
120 seconds (NBMA and
point-to-multipoint)
Configures OSPF interface hello
interval.
10 seconds (broadcast and
point-to-point)
30 seconds (NBMA and point-
to-multipoint)
Configures the OSPF interface cost. ip ospf interface cost
1
Configures the OSPF poll interval. ip ospf interface poll-interval
120 seconds
1
Configures the OSPF interface pri- ip ospf interface priority
ority.
Configures OSPF interface retrans- ip ospf interface retrans-interval 5 seconds
mit interval.
Configures the OSPF interface tran- ip ospf interface transit-delay
1 second
sit delay.
Configures the OSPF interface type. ip ospf interface type
broadcast
Disabled
Configures graceful restart on
redundant switches in a stack
ip ospf restart-support
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-3
OSPF Quick Steps
Configuring OSPF
OSPF Quick Steps
The followings steps are designed to show the user the necessary set of commands for setting up a router
to use OSPF:
1 Create a VLAN using the vlan command. For example:
-> vlan 5
-> vlan 5 enable
2 Assign a router IP address and subnet mask to the VLAN using the ip interface command. For exam-
ple:
-> ip interface vlan-5 vlan 5 address 120.1.4.1 mask 255.0.0.0
3 Assign a port to the created VLANs using the vlan command. For example:
-> vlan 5 port default 2/1
Note. The port will be statically assigned to the VLAN, as a VLAN must have a physical port assigned to
it in order for the router port to function. However, the router could be set up in such a way that mobile
ports are dynamically assigned to VLANs using VLAN rules. See the chapter titled “Defining VLAN
Rules” in the OmniSwitch 6600 Family Network Configuration Guide.
4 Assign a router ID to the router using the ip router router-id command. For example:
-> ip router router-id 1.1.1.1
5 Load and enable OSPF using the ip load ospf and the ip ospf status commands. For example:
-> ip load ospf
-> ip ospf status enable
6 Create a backbone to connect this router to others, and an area for the router’s traffic, using the ip ospf
area command. (Backbones are always labeled area 0.0.0.0.) For example:
-> ip ospf area 0.0.0.0
-> ip ospf area 0.0.0.1
7 Enable the backbone and area using the ip ospf area status command. For example:
-> ip ospf area 0.0.0.0 status enable
-> ip ospf area 0.0.0.1 status enable
8 Create an OSPF interface for each VLAN created in Step 1, using the ip ospf interface command. The
OSPF interface should use the same IP address or interface name used for the VLAN router IP created in
Step 2. For example:
-> ip ospf interface 120.1.4.1
or
-> ip ospf interface vlan-5
page 1-4
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
OSPF Quick Steps
9 Assign the OSPF interface to the area and the backbone using the ip ospf interface area command.
For example:
-> ip ospf interface 120.1.4.1 area 0.0.0.0
or
-> ip ospf interface vlan-5 area 0.0.0.0
10Enable the OSPF interfaces using the ip ospf interface status command. For example:
-> ip ospf interface 120.1.4.1 status enable
or
-> ip ospf interface vlan-5 status enable
11You can now display the router OSPF settings by using the show ip ospf command. The output gener-
ated is similar to the following:
-> show ip ospf
Router ID
As set in Step 5
Router Id
OSPF Version Number
Admin Status
Area Border Router?
AS Border Router Status
Route Redistribution Status
Route Tag
= 1.1.1.1,
= 2,
= Enabled,
= Yes,
= Disabled,
= Disabled,
= 0,
SPF Hold Time (in seconds)
SPF Delay Time (in seconds)
MTU Checking
= 10,
= 5,
= Disabled,
= 0,
# of Routes
# of AS-External LSAs
# of self-originated LSAs
# of LSAs received
External LSDB Limit
Exit Overflow Interval
# of SPF calculations done
= 0,
= 0,
= 0,
= -1,
= 0,
= 1,
# of Incr SPF calculations done = 0,
# of Init State Nbrs
# of 2-Way State Nbrs
# of Exchange State Nbrs
# of Full State Nbrs
# of attached areas
# of Active areas
= 0,
= 0,
= 0,
= 0,
= 2,
= 2,
= 0,
= 0
# of Transit areas
# of attached NSSAs
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-5
OSPF Quick Steps
Configuring OSPF
12You can display OSPF area settings using the show ip ospf area command. For example:
-> show ip ospf area 0.0.0.0
Area ID
As set in Step 7
Area Identifier
Admin Status
Operational Status
Area Type
Area Summary
Time since last SPF Run
# of Area Border Routers known
# of AS Border Routers known
# of LSAs in area
= 0.0.0.0,
= Enabled,
= Up,
= normal,
= Enabled,
= 00h:08m:37s,
= 1,
Area Status
As set in Step 8
= 0,
= 1,
# of SPF Calculations done
= 1,
# of Incremental SPF Calculations done = 0,
# of Neighbors in Init State
# of Neighbors in 2-Way State
# of Neighbors in Exchange State
# of Neighbors in Full State
# of Interfaces attached
= 0,
= 0,
= 0,
= 0
= 1
13You can display OSPF interface settings using the show ip ospf interface command. For example:
-> show ip ospf interface 120.1.4.1
VLAN ID
As set in Step 1
Interface IP Name
VLAN Id
= vlan-5
= 5,
Interface ID
Interface IP Address
Interface IP Mask
Admin Status
Operational Status
OSPF Interface State
Interface Type
Area Id
Designated Router IP Address
Designated Router RouterId
= 120.1.4.1,
= 255.0.0.0,
= Enabled,
= Down,
As set in Step 9
Interface Status
As set in Step 11
= Down,
= Broadcast,
= 0.0.0.0,
= 0.0.0.0,
= 0.0.0.0,
Area ID
As set in Step 7
Backup Designated Router IP Address = 0.0.0.0,
Backup Designated Router RouterId
MTU (bytes)
Metric Cost
= 0.0.0.0,
= 1500,
= 1,
Priority
= 1,
Hello Interval (seconds)
Transit Delay (seconds)
Retrans Interval (seconds)
Dead Interval (seconds)
Poll Interval (seconds)
Link Type
= 10,
= 1,
= 5,
= 40,
= 120,
= Broadcast,
= none,
= 0,
Authentication Type
# of Events
# of Init State Neighbors
# of 2-Way State Neighbors
# of Exchange State Neighbors
# of Full State Neighbors
= 0,
= 0,
= 0,
= 0
page 1-6
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
OSPF Overview
OSPF Overview
Open Shortest Path First routing (OSPF) is a shortest path first (SPF), or link-state, protocol. OSPF is an
interior gateway protocol (IGP) that distributes routing information between routers in a Single Autono-
mous System (AS). OSPF chooses the least-cost path as the best path.
Each participating router distributes its local state (i.e., the router’s usable interfaces, local networks, and
reachable neighbors) throughout the AS by flooding. In a link-state protocol, each router maintains a data-
base describing the entire topology. This database is built from the collected link state advertisements of
all routers. Each multi-access network that has at least two attached routers has a designated router and a
backup designated router. The designated router floods a link state advertisement for the multi-access
network.
When a router starts, it uses the OSPF Hello Protocol to discover neighbors. The router sends Hello pack-
ets to its neighbors, and in turn receives their Hello packets. On broadcast and point-to-point networks, the
router dynamically detects its neighboring routers by sending Hello packets to a multicast address. On
nonbroadcast and point-to-multipoint networks, some configuration information is necessary in order to
configure neighbors. On all networks (broadcast or nonbroadcast), the Hello Protocol also elects a desig-
nated router for the network.
Hello. Please respond...
Are you a neighbor...
My link state is...
Hello. Please respond...
Are you a neighbor...
My link state is...
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OSPF Hello Protocol
The router will attempt to form full adjacencies with all of its newly acquired neighbors. Only some pairs,
however, will be successful in forming full adjacencies. Topological databases are synchronized between
pairs of fully adjacent routers.
Adjacencies control the distribution of routing protocol packets. Routing protocol packets are sent and
received only on adjacencies. In particular, distribution of topological database updates proceeds along
adjacencies.
Link state is also advertised when a router’s state changes. A router’s adjacencies are reflected in the
contents of its link state advertisements. This relationship between adjacencies and link state allows the
protocol to detect downed routers in a timely fashion.
Link state advertisements are flooded throughout the AS. The flooding algorithm ensures that all routers
have exactly the same topological database. This database consists of the collection of link state advertise-
ments received from each router belonging to the area. From this database each router calculates a short-
est-path tree, with itself as root. This shortest-path tree in turn yields a routing table for the protocol.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-7
OSPF Overview
Configuring OSPF
OSPF Areas
OSPF allows collections of contiguous networks and hosts to be grouped together as an area. Each area
runs a separate copy of the basic link-state routing algorithm (usually called SPF). This means that each
area has its own topological database, as explained in the previous section.
Inter-Area Routing
Intra-Area
Routing
Intra-Area
Routing
Router 3
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
Backbone
Router 1
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
Link State
Messages
Link State
Messages
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
Router 2
Router 4
Area 1
Area 2
OSPF Intra-Area and Inter-Area Routing
An area’s topology is visible only to the members of the area. Conversely, routers internal to a given area
know nothing of the detailed topology external to the area. This isolation of knowledge enables the proto-
col to reduce routing traffic by concentrating on small areas of an AS, as compared to treating the entire
AS as a single link-state domain.
Areas cause routers to maintain a separate topological database for each area to which they are connected.
(Routers connected to multiple areas are called area border routers). Two routers belonging to the same
area have identical area topological databases.
Different areas communicate with each other through a backbone. The backbone consists of routers with
contacts between multiple areas. A backbone must be contiguous (i.e., it must be linked to all areas).
The backbone is responsible for distributing routing information between areas. The backbone itself has all
of the properties of an area. The topology of the backbone is invisible to each of the areas, while the back-
bone itself knows nothing of the topology of the areas.
All routers in an area must agree on that area’s parameters. Since a separate copy of the link-state algo-
rithm is run in each area, most configuration parameters are defined on a per-router basis. All routers
belonging to an area must agree on that area’s configuration. Misconfiguration will keep neighbors from
forming adjacencies between themselves, and OSPF will not function.
page 1-8
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
OSPF Overview
Classification of Routers
When an AS is split into OSPF areas, the routers are further divided according to function into the follow-
ing four overlapping categories:
• Internal routers. A router with all directly connected networks belonging to the same area. These
routers run a single copy of the SPF algorithm.
• Area border routers. A router that attaches to multiple areas. Area border routers run multiple copies
of the SPF algorithm, one copy for each attached area. Area border routers condense the topological
information of their attached areas for flooding to other areas.
• Backbone routers. A router that has an interface to the backbone. This includes all routers that inter-
face to more than one area (i.e., area border routers). However, backbone routers do not have to be area
border routers. Routers with all interfaces connected to the backbone are considered to be internal rout-
ers.
• AS boundary routers. A router that exchanges routing information with routers belonging to other
Autonomous Systems. Such a router has AS external routes that are advertised throughout the Autono-
mous System. The path to each AS boundary router is known by every router in the AS. This classifi-
cation is completely independent of the previous classifications (i.e., internal, area border, and
backbone routers). AS boundary routers may be internal or area border routers, and may or may not
participate in the backbone.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-9
OSPF Overview
Configuring OSPF
Virtual Links
It is possible to define areas in such a way that the backbone is no longer contiguous. (This is not an ideal
OSPF configuration, and maximum effort should be made to avoid this situation.) In this case the system
administrator must restore backbone connectivity by configuring virtual links.
Virtual links can be configured between any two backbone routers that have a connection to a common
non-backbone area. The protocol treats two routers joined by a virtual link as if they were connected by an
unnumbered point-to-point network. The routing protocol traffic that flows along the virtual link uses
intra-area routing only, and the physical connection between the two routers is not managed by the
network administrator (i.e., there is no dedicated connection between the routers as there is with the OSPF
backbone).
Router B
Router A
Area 1
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
Virtual Link
Backbone
Backbone
OSPF Routers Connected with a Virtual Link
In the above diagram, Router A and Router B are connected via a virtual link in Area 1, which is known as
page 1-10
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
OSPF Overview
Stub Areas
OSPF allows certain areas to be configured as stub areas. A stub area is an area with routers that have no
AS external Link State Advertisements (LSAs).
In order to take advantage of the OSPF stub area support, default routing must be used in the stub area.
This is accomplished by configuring only one of the stub area’s border routers to advertise a default route
into the stub area. The default routes will match any destination that is not explicitly reachable by an intra-
area or inter-area path (i.e., AS external destinations).
OmniSwitch 6648
Backbone
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
mniSwitch 6648
mniSwitch 6648
OmniSwitch 6648
mniSwitch 6648
mniSwitch 6648
OmniSwitch 6648
mniSwitch 6648
mniSwitch 6648
OmniSwitch 6648
mniSwitch 6648
mniSwitch 6648
Backbone
Area 3
(stub)
Area 1
(stub)
Area 2
OSPF Stub Area
Area 1 and Area 3 could be configured as stub areas. Stub areas are configured using the OSPF ip ospf
The OSPF protocol ensures that all routers belonging to an area agree on whether the area has been
configured as a stub. This guarantees that no confusion will arise in the flooding of AS external advertise-
ments.
Two restrictions on the use of stub areas are:
• Virtual links cannot be configured through stub areas.
• AS boundary routers cannot be placed internal to stub areas.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-11
OSPF Overview
Configuring OSPF
Not-So-Stubby-Areas
NSSA, or not-so-stubby area, is an extension to the base OSPF specification and is defined in RFC 1587.
An NSSA is similar to a stub area in many ways: AS-external LSAs are not flooded into an NSSA and
virtual links are not allowed in an NSSA. The primary difference is that selected external routing informa-
tion can be imported into an NSSA and then redistributed into the rest of the OSPF routing domain. These
routes are imported into the NSSA using a new LSA type: Type-7 LSA. Type-7 LSAs are flooded within
the NSSA and are translated at the NSSA boundary into AS-external LSAs so as to convey the external
routing information to other areas.
NSSAs enable routers with limited resources to participate in OSPF routing while also allowing the import
of a selected number of external routes into the area. For example, an area which connects to a small exter-
nal routing domain running RIP may be configured as an NSSA. This will allow the import of RIP routes
into this area and the rest of the OSPF routing domain and at the same time, prevent the flooding of other
external routing information (learned, for example, through IP) into this area.
All routers in an NSSA must have their OSPF area defined as an NSSA. To configure otherwise will
ensure that the router will be unsuccessful in establishing an adjacent in the OSPF domain.
Totally Stubby Areas
In Totally Stubby Areas the ABR advertises a default route to the routers in the totally stubby area but
does not advertise any inter-area or external LSAs. As a result, routers in a totally stubby area know only
the routes for destination networks in the stub area and have a default route for any other destination
outside the stub.
Note. Virtual links cannot be configured through totally stubby areas.
The router memory is saved when using stub area networks by filtering Type 4 and 5 LSAs. This concept
has been extended with Totally Stubby Areas by filtering Type 3 LSAs (Network Summary LSA) in addi-
tion to Type 4 and 5 with the exception of one single Type 3 LSA used to advertise a default route within
the area.
The following is an example of a simple totally stubby configuration with Router B being an ABR
between the backbone area 0 and the stub area 1. Router A is in area 1.1.1.1, totally stubby area:
OSPF Area 0
192.168.50.0/24
OSPF Area 1
Totally Stubby
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
192.168.12.1
192.168.12.2
Router A
Router B
Totally Stubby Area Example
Stubby Areas.
page 1-12
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
OSPF Overview
Equal Cost Multi-Path (ECMP) Routing
Using information from its continuously updated databases, OSPF calculates the shortest path to a given
destination. Shortest path is determined from metric values at each hop along a path. At times, two or
more paths to the same destination will have the same metric cost.
In the network illustration below, there are two paths from Source router A to Destination router B. One
path traverses two hops at routers X and Y and the second path traverses two hops at M and N. If the total
cost through X and Y to B is the same as the cost via M and N to B, then these two paths have equal cost.
In this version of OSPF both paths will be stored and used to transmit data.
X
Y
OmniSwitch 6648
OmniSwitch 6648
mniSwitch 6648
mniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
A-> X-> Y-> B = A-> M-> N-> B
Source (A)
Destination (B)
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
M
N
Multiple Equal Cost Paths
Delivery of packets along equal paths is based on flows rather than a round-robin scheme. Equal cost is
determined based on standard routing metrics. However, other variables, such as line speed, are not
considered. So it is possible for OSPF to decide two paths have an equal cost even though one may
contain faster links than another.
Non Broadcast OSPF Routing
OSPF can operate in two modes on non-broadcast networks: NBMA and point-to-multipoint. The inter-
face type for the corresponding network segment should be set to non broadcast or point-to-point, respec-
tively.
For non-broadcast networks neighbors should be statically configured. For NBMA neighbors the eligibil-
ity option must be enabled for the neighboring router to participate in Designated Router (DR) election.
For the correct working of an OSPF NBMA network, a fully meshed network is mandatory. Also, the
neighbor eligibility configuration for a router on every other router should match the routers interface
priority configuration.
See “Configuring Static Neighbors” on page 1-30 for more information and setting up static neighbors.
Graceful Restart on Stacks with Redundant Switches
OmniSwitch 6600 Family stacks with two or more switches can support redundancy where if the primary
switch fails or goes offline for any reason, the secondary switch is instantly notified. The secondary switch
automatically assumes the primary role. This switch between the primary and secondary switches is
known as takeover.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-13
OSPF Overview
Configuring OSPF
When a takeover occurs, which can be planned (e.g., the users performs the takeover) or unplanned (e.g.,
the primary switch unexpectedly fails), an OSPF router must reestablish full adjacencies with all its previ-
ously fully adjacent neighbors. This time period between the restart and the reestablishment of adjacen-
cies is termed graceful restart.
In the network illustration below, a helper router, Router Y, monitors the network for topology changes.
As long as there are none, it continues to advertise its LSAs as if the restarting router, Router X, had
remained in continuous OSPF operation (i.e., Router Y’s LSAs continue to list an adjacency to Router X
over network segment S, regardless of the adjacency’s current synchronization state.)
Router B
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
Restarting Router X
Helping Router Y
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
Network Segment S
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
Router C
Router A
OSPF Graceful Restart Helping and Restarting Router Example
If the restarting router, Router X, was the Designated Router (DR) on network segment S when the help-
ing relationship began, the helper neighbor, Router Y, maintains Router X as the DR until the helping rela-
tionship is terminated. If there are multiple adjacencies with the restarting Router X, Router Y will act as a
helper on all other adjacencies.
Continuous forwarding during a graceful restart depends on several factors. If the secondary module has a
different router MAC than the primary module, or if one or more ports of a VLAN belonged to the
primary module, spanning tree re-convergence might disrupt forwarding state, even though OSPF
performs a graceful restart.
Note. See “Configuring Redundant Switches in a Stack for Graceful Restart” on page 1-31 for more infor-
mation on configuring graceful restart.
page 1-14
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
Configuring OSPF
Configuring OSPF
Configuring OSPF on a router requires several steps. Depending on your requirements, you may not need
to perform all of the steps listed below.
By default, OSPF is disabled on the router. Configuring OSPF consists of these tasks:
• Set up the basics of the OSPF network by configuring the required VLANs, assigning ports to the
VLANs, and assigning router identification numbers to the routers involved. This is described in
• Enable OSPF. When the image file for advanced routing (Hadvrout.img) is installed, you must load
the code and enable OSPF. The commands for enabling OSPF are described in “Activating OSPF” on
• Create an OSPF area and the backbone. The commands to create areas and backbones are described in
• Set area parameters (optional). OSPF will run with the default area parameters, but different networks
may benefit from modifying the parameters. Modifying area parameters is described in “Configuring
• Create OSPF interfaces. OSPF interfaces are created and assigned to areas. Creating areas is described
in “Creating an Interface” on page 1-22, and assigning areas is described in “Assigning an Interface to
• Set interface parameters (optional). OSPF will run with the default interface parameters, but different
networks may benefit from modifying the parameters. Also, it is possible to set authentication on an
interface. Setting interface authentication is described in “Interface Authentication” on page 1-23, and
• Configure virtual links (optional). A virtual link is used to establish backbone connectivity when two
backbone routers are not physically contiguous. To create a virtual link, see “Creating Virtual Links”
• Create a redistribution policy (optional). A redistribution policy allows for the control of how routes
are advertised into OSPF from outside the Autonomous System. Once a policy is created, redistribu-
tion must be enabled. Creating a redistribution policy is described in “Creating A Redistribution
• Create redistribution filters (optional). A redistribution filter controls whether routes are advertised in
the OSPF network. Creating a redistribution filter is described in “Creating a Redistribution Filter” on
• Configuring router capabilities (optional). There are several commands that influence router operation.
• Creating static neighbors (optional). These commands allow you to statically configure neighbors. See
• Configuring redundant switches in a stack for graceful OSPF restart (optional). Configuring stacks
with redundant switches for graceful restart is described in “Configuring Redundant Switches in a
At the end of the chapter is a simple OSPF network diagram with instructions on how it was created on a
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-15
Configuring OSPF
Configuring OSPF
Preparing the Network for OSPF
OSPF operates on top of normal switch functions, using existing ports, virtual ports, VLANs, etc. The
following network components should already be configured:
• Configure VLANs that are to be used in the OSPF network. VLANS should be created for both the
backbone interfaces and all other connected devices that will participate in the OSPF network. A
VLAN should exist for each instance in which the backbone connects two routers. VLAN configura-
tion is described in “Configuring VLANs,” in the OmniSwitch 6600 Family Network Configuration
Guide.
• Assign IP interfaces to the VLANs. IP interfaces, or router ports, must be assigned to the VLAN.
Assigning IP interfaces is described in “Configuring VLANs,” in the OmniSwitch 6600 Family
Network Configuration Guide.
• Assign ports to the VLANs. The physical ports participating in the OSPF network must be assigned to
the created VLANs. Assigning ports to a VLAN is described in “Assigning Ports to VLANs,” in the
OmniSwitch 6600 Family Network Configuration Guide.
• Set the router identification number. (optional) The routers participating in the OSPF network must
be assigned a router identification number. This number can be any number, as long as it is in standard
dotted decimal format (e.g., 1.1.1.1). Router identification number assignment is discussed in “Config-
uring IP,” in the OmniSwitch 6600 Family Network Configuration Guide. If this is not done, the router
identification number is automatically the primary interface address.
page 1-16
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
Configuring OSPF
Activating OSPF
For OSPF to run on the router, the advanced routing image (Hadvrout.img) must be installed. (For infor-
mation on how to install image files, see “Managing System Files” in the OmniSwitch 6600 Family Switch
Management Guide.)
After the image file has been installed onto the router, you will need to load the OSPF software into
memory and enable it, as described below.
Loading the Software
To load the OSPF software into the router’s running configuration, enter the ip load ospf command at the
system prompt:
-> ip load ospf
The OPSF software is now loaded into memory, and can be enabled.
Enabling OSPF
Once the OSPF software has been loaded into the router’s running configuration (either through the CLI
or on startup), it must be enabled. To enable OSPF on a router, enter the ip ospf status command at the
CLI prompt, as shown:
-> ip ospf status enable
Once OSPF is enabled, you can begin to set up OSPF parameters. To disable OSPF, enter the following:
-> ip ospf status disable
Removing OSPF from Memory
To remove OSPF from the router memory, it is necessary to manually edit the boot.cfg file. The boot.cfg
file is an ASCII text-based file that controls many of the switch parameters. Open the file and delete all
references to OSPF.
For the operation to take effect the switch needs to be rebooted.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-17
Configuring OSPF
Configuring OSPF
Creating an OSPF Area
OSPF allows a set of network devices in an AS system to be grouped together in areas.
There can be more than one router in an area. Likewise, there can be more than one area on a single router
(in effect, making the router the Area Border Router (ABR) for the areas involved), but standard network-
ing design does not recommended that more than three areas be handled on a single router.
Areas are named using 32-bit dotted decimal format (e.g., 1.1.1.1). Area 0.0.0.0 is reserved for the back-
bone.
Creating an Area
To create an area and associate it with a router, enter the ip ospf area command with the area identifica-
tion number at the CLI prompt, as shown:
-> ip ospf area 1.1.1.1
Area 1.1.1.1 will now be created on the router with the default parameters.
The backbone is always area 0.0.0.0. To create this area on a router, you would use the above command,
but specify the backbone, as shown:
-> ip ospf area 0.0.0.0
The backbone would now be attached to the router, making it an Area Border Router (ABR).
Enabling an Area
Once an area is created, it must be enabled using the ip ospf area status command, as shown:
-> ip ospf area 0.0.0.0 status enable
Specifying an Area Type
When creating areas, an area type can be specified (normal, stub, or NSSA). Area types are described
-> ip ospf area 1.1.1.1 type stub
Note. By default, an area is a normal area. The type keyword would be used to change a stub or NSSA
area into a normal area.
page 1-18
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
Configuring OSPF
Enabling and Disabling Summarization
Summarization can also be enabled or disabled when creating an area. Enabling summarization allows for
ranges to be used by Area Border Routers (ABRs) for advertising routes as a single route rather than
multiple routes, while disabling summarization prevents set ranges from functioning in stub and NSSA
For example, to enable summarization for Area 1.1.1.1, enter the following:
-> ip ospf area 1.1.1.1 summary enable
To disable summarization for the same area, enter the following:
-> ip ospf area 1.1.1.1 summary disable
Note. By default, an area has summarization enabled. Disabling summarization for an area is useful when
ranges need to be deactivated, but not deleted.
Displaying Area Status
You can check the status of the newly created area by using the show command, as demonstrated:
-> show ip ospf area 1.1.1.1
or
-> show ip ospf area
The first example gives specifics about area 1.1.1.1, and the second example shows all areas configured on
the router.
To display a stub area’s parameters, use the show ip ospf area stub command as follows:
-> show ip ospf area 1.1.1.1 stub
Deleting an Area
To delete an area, enter the ip ospf area command as shown:
-> no ip ospf area 1.1.1.1
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-19
Configuring OSPF
Configuring OSPF
Configuring Stub Area Default Metrics
The default metric configures the type of cost metric that a default area border router (ABR) will advertise
in the default summary Link State Advertisement (LSA). Use the ip ospf area default-metric command
to create or delete a default metric for stub or Not So Stubby Area (NSSA) area. Specify the stub area and
select a cost value or a route type, as shown:
-> ip ospf area 1.1.1.1 default-metric 0 cost 50
or
-> ip ospf area 1.1.1.1 default-metric 0 type type1
A route has a preset metric associated to it depending on its type. The first example, the stub area is given
a default metric of 0 (this is Type of Service 0) and a cost of 50 added to routes from the area. The second
example specifies that the cost associated with Type 1 routes should be applied to routes from the area.
Note. At this time, only the default metric of ToS 0 is supported.
To remove the area default-metric setting, enter the ip ospf area default-metric command using the no
command, as shown:
-> no ip ospf area 1.1.1.1 default-metric 0
Setting Area Ranges
Area ranges are used to summarize many area routes into a single advertisement at an area boundary.
Ranges are advertised as summaries or NSSAs. Ranges also act as filters that either allow the summary to
be advertised or not. Ranges are created using the ip ospf area range command. An area and the summary
IP address and IP mask must be specified. For example, to create a summary range with IP address
192.5.40.1 and an IP mask of 255.255.255.0 for area 1.1.1.1, the following commands would be entered at
the CLI prompt:
-> ip ospf area 1.1.1.1 range summary 192.5.40.1 255.255.255.0
-> ip ospf area 1.1.1.1 range summary 192.5.40.1 255.255.255.0 effect noMatching
To view the configured ranges for an area, use the show ip ospf area range command as demonstrated:
-> show ip ospf area 1.1.1.1 range
Configuring a Totally Stubby Area
In order to configure a totally stubby area you need to configure the area as stub on the ABR and disable
summarization. By doing so the ABR will generate a default route in the totally stubby area. In addition,
the other routers within the totally stubby area must only have their area configured as stub.
For example, to configure the simple totally stubby configuration shown in the figure in “Configuring a
Totally Stubby Area” on page 1-20 where Router B is an ABR between the backbone area 0 and the stub
area 1 and Router A is in Totally Stubby Area 1.1.1.1 follow the steps below:
page 1-20
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
Configuring OSPF
1 Enter the following commands on Router B:
-> ip load ospf
-> ip ospf area 0.0.0.0
-> ip ospf area 0.0.0.0 status enable
-> ip ospf area 1.1.1.1
-> ip ospf area 1.1.1.1 type stub
-> ip ospf area 1.1.1.1 summary disable
-> ip ospf area 1.1.1.1 status enable
-> ip ospf area 1.1.1.1 default-metric 0
-> ip ospf interface 192.168.12.2
-> ip ospf interface 192.168.12.2 area 1.1.1.1
-> ip ospf interface 192.168.12.2 status enable
-> ip ospf interface 192.168.50.2
-> ip ospf interface 192.168.50.2 area 0.0.0.0
-> ip ospf interface 192.168.50.2 status enable
-> ip ospf status enable
2 Enter the following on Router A:
-> ip load ospf
-> ip ospf area 1.1.1.1
-> ip ospf area 1.1.1.1 type stub
-> ip ospf area 1.1.1.1 status enable
-> ip ospf interface 192.168.12.1
-> ip ospf interface 192.168.12.1 area 1.1.1.1
-> ip ospf interface 192.168.12.1 status enable
-> ip ospf status enable
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-21
Configuring OSPF
Configuring OSPF
Creating OSPF Interfaces
Once areas have been established, interfaces need to be created and assigned to the areas.
Creating an Interface
To create an interface, enter the ip ospf interface command with an IP address or interface name, as
shown:
-> ip ospf interface 120.5.80.1
-> ip ospf interface vlan-213
The interface can be deleted the by using the no keyword, as shown:
-> no ip ospf interface 120.5.80.1
Assigning an Interface to an Area
Once an interface is created, it must be assigned to an area. (Creating areas is described in “Creating an
Area” on page 1-18 above.)
To assign an interface to an area, enter the ip ospf interface area command with the interface IP address
or interface name and area identification number at the CLI prompt. For example to add interface
120.5.80.1 to area 1.1.1.1, enter the following:
-> ip ospf interface 120.5.80.1 area 1.1.1.1
An interface can be removed from an area by reassigning it to a new area.
Once an interface has been created and enabled, you can check its status and configuration by using the
show ip ospf interface command, as demonstrated:
-> show ip ospf interface 120.5.80.1
Instructions for configuring authentication are given in “Interface Authentication” on page 1-23, and inter-
Activating an Interface
Once the interface is created and assigned to an area, it must be activated using the ip ospf interface
status command with the interface IP address or interface name, as shown:
-> ip ospf interface 120.5.80.1 status enable
The interface can be disabled using the disable keyword in place of the enable keyword.
page 1-22
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
Configuring OSPF
Interface Authentication
OSPF allows for the use of authentication on configured interfaces. When authentication is enabled, only
neighbors using the same type of authentication and the matching passwords or keys can communicate.
There are two types of authentication: simple and MD5. Simple authentication requires only a text string
as a password, while MD5 is a form of encrypted authentication that requires a key and a password. Both
types of authentication require the use of more than one command.
Simple Authentication
To enable simple authentication on an interface, enter the ip ospf interface auth-type command with the
interface IP address or interface name, as shown:
-> ip ospf interface 120.5.80.1 auth-type simple
Once simple authentication is enabled, the password must be set with the ip ospf interface auth-key
command, as shown:
-> ip ospf interface 120.5.80.1 auth-key test
In the above instance, only other interfaces with simple authentication and a password of “test” will be
able to use the configured interface.
MD5 Encryption
To configure the same interface for MD5 encryption, enter the ip ospf interface auth-type as shown:
-> ip ospf interface 120.5.80.1 auth-type md5
Once MD5 authentication is set, a key identification and key string must be set with the ip ospf interface
md5 key command. For example to set interface 120.5.80.1 to use MD5 authentication with a key identifi-
cation of 7 and key string of “test”, enter:
-> ip ospf interface 120.5.80.1 md5 7
and
-> ip ospf interface 120.5.80.1 md5 7 key "test"
Note that setting the key ID and key string must be done in two separate commands. Once the key ID and
key string have been set, MD5 authentication is enabled. To disable it, use the ip ospf interface md5
command, as shown:
-> ip ospf interface 120.5.80.1 md5 7 disable
To remove all authentication, enter the ip ospf interface auth-type as follows:
-> ip ospf interface 120.5.80.1 auth-type none
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-23
Configuring OSPF
Configuring OSPF
Modifying Interface Parameters
There are several interface parameters that can be modified on a specified interface. Most of these deal
with timer settings.
The cost parameter and the priority parameter help to determine the cost of the route using this interface,
and the chance that this interface’s router will become the designated router, respectively.
The following table shows the various interface parameters that can be set:
ip ospf interface dead-interval
Configures OSPF interface dead interval. If no hello packets are
received in this interval from a neighboring router the neighbor is con-
sidered dead.
ip ospf interface hello-interval
ip ospf interface cost
Configures the OSPF interface interval for NBMA segments.
Configures the OSPF interface cost. A cost metric refers to the net-
work path preference assigned to certain types of traffic.
ip ospf interface poll-interval
ip ospf interface priority
Configures the OSPF poll interval.
Configures the OSPF interface priority. The priority number helps
determine if this router will become the designated router.
ip ospf interface retrans-interval Configures OSPF interface retransmit interval. The number of sec-
onds between link state advertisement retransmissions for adjacencies
belonging to this interface.
ip ospf interface transit-delay
Configures the OSPF interface transit delay. The estimated number of
seconds required to transmit a link state update over this interface.
These parameters can be added any time. (See “Creating OSPF Interfaces” on page 1-22 for more informa-
tion.) For example, to set an the dead interval to 50 and the cost to 100 on interface 120.5.80.1, enter the
following:
-> ip ospf interface 120.5.80.1 dead-interval 50 cost 100
To set an the poll interval to 25, the priority to 100, and the retransmit interval to 10 on interface
120.5.80.1, enter the following:
-> ip ospf interface 120.5.80.1 poll-interval 25 priority 100 retrans-interval
10
To set the hello interval to 5000 on interface 120.5.80.1, enter the following:
-> ip ospf interface 120.5.80.1 hello-interval 5000
To reset any parameter to its default value, enter the keyword with no parameter value, as shown:
-> ip ospf interface 120.5.80.1 dead-interval
Note. Although you can configure several parameters at once, you can only reset them to the default one at
a time.
page 1-24
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
Configuring OSPF
Creating Virtual Links
A virtual link is a link between two backbones through a transit area. Use the ip ospf virtual-link
command to create or delete a virtual link.
Accepted network design theory states that virtual links are the option of last resort. For more information
Creating a Virtual Link
To create a virtual link, commands must be submitted to the routers at both ends of the link. The router
being configured should point to the other end of the link, and both routers must have a common area.
When entering the ip ospf virtual-link command, it is necessary to enter the Router ID of the far end of
the link, and the area ID that both ends of the link share.
For example, a virtual link needs to be created between Router A (router ID 1.1.1.1) and Router B (router
ID 2.2.2.2). We must:
1 Establish a transit area between the two routers using the commands discussed in “Creating an OSPF
Area” on page 1-18 (in this example, we will use Area 0.0.0.1).
2 Then use the ip ospf virtual-link command on Router A as shown:
ip ospf virtual-link 0.0.0.1 2.2.2.2
3 Next, enter the following command on Router B:
ip ospf virtual-link 0.0.0.1 1.1.1.1
Now there is a virtual link across Area 0.0.0.1 linking Router A and Router B.
4 To display virtual links configured on a router, enter the following show command:
show ip ospf virtual-link
5 To delete a virtual link, enter the ip ospf virtual-link command with the area and far end router infor-
mation, as shown:
no ip ospf virtual-link 0.0.0.1 2.2.2.2
Modifying Virtual Link Parameters
There are several parameters for a virtual link (such as authentication type and cost) that can be modified
at the time of the link creation. They are described in the ip ospf virtual-link command description.These
parameters are identical in function to their counterparts in the section “Modifying Interface Parameters”
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-25
Configuring OSPF
Configuring OSPF
Creating Redistribution Policies and Filters
Redistribution in OSPF controls the way routes are learned and distributed in the OSPF network. Non
OSPF routers can be advertised into the OSPF network as AS-external or NSSA-external routes. NSSA-
external routes are advertised only in OSPF-NSSA areas. Redistribution policies are set on Autonomous
System Boundary Routers (ASBRs) and control how routes from outside the Autonomous System (AS)
are learned and distributed. Redistribution Filters are set on any OSPF router and control how routes on
the router are distributed to other routers in the OSPF network.
To set up redistribution on a router:
on page 1-26. (For redistribution policies only.)
3 Create a redistribution policy or filter, as described in “Creating A Redistribution Policy” on page 1-27
Specifying an Autonomous System Boundary Router
Redistribution policies can only be created on ASBRs. ASBRs are routers that are directly connected to a
network outside of the AS (e.g., the internet). To configure a router to be an ASBR, enter the ip ospf asbr
command at the CLI prompt, as shown:
-> ip ospf asbr
You can check to see if a router is an ASBR router by using the show ip ospf command.
Enabling Redistribution
Before using any type of redistribution policy or filter, you must enable redistribution on the router, using
the ip ospf redist status command. To enable redistribution, enter the command at the CLI prompt as
shown:
-> ip ospf redist status enable
To disable redistribution, enter the command as shown:
-> ip ospf redist status disable
page 1-26
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
Configuring OSPF
Creating A Redistribution Policy
Once a router is set as an ASBR and redistribution is enabled, a redistribution policy can be created. This
is done using the ip ospf redist command. When setting up a redistribution policy, choose the type of
route or protocol that will be redistributed as an OSPF route in the OSPF network. For example, to redis-
tribute RIP routes, enter the following:
-> ip ospf redist rip
To redistribute static routes, enter the following:
-> ip ospf redist static
A cost metric can be added to the redistributed route, either as a set number or by specifying a route type
(route types have preassigned metrics and other rule that control how they are redistributed). For example,
to add a cost metric of 50 to RIP routes, enter the following:
-> ip ospf redist rip metric 50
To set RIP route redistribution as type 1 routes, enter the following:
-> ip ospf redist rip metric-type type1
For more information on route types, see the ip ospf redist command in the OmniSwitch CLI Reference
Guide.
To display the redistribution policies on a router, enter the show ip ospf redist command at the CLI
prompt.
To delete a redistribution policy, enter the ip ospf redist command with the route or protocol type, and the
no keyword, as shown:
-> no ip ospf redist rip
Creating a Redistribution Filter
Redistribution filters are used by routers to control which routes are advertised to the rest of the network.
Filters can be created on any OSPF router that has redistribution enabled.
Filters are created using the ip ospf redist-filter command.When using a filter, a route or protocol type
must be specified, along with the IP address and mask. Only routes matching the specified criteria will be
advertised. For example, to create a filter for RIP routes 1.1.0.0 with a mask of 255.255.0.0, enter the
following:
-> ip ospf redist-filter rip 1.1.0.0 255.255.0.0
Filters can also be used to prevent routes from being advertised by using the effect keyword. Using the
above example, to prevent RIP routes learned from 1.1.0.0 being advertised, enter the following:
-> ip ospf redist-filter rip 1.1.0.0 255.255.0.0 effect deny
This filter would stop the advertisement of RIP routes learned within the range 1.1.0.0 with a mask of
255.255.0.0. All other routes would be advertised normally.
Note. By default, filters are set to permit. If permit is the filter action desired, it is not necessary to use
the effect keyword.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-27
Configuring OSPF
Configuring OSPF
In certain cases, redistribution can either be an adjacent route or a subnet. In these cases, the redistributed
route can correspond to several routes. It is possible to advertise these routes separately or not with the
redist-control keyword.
If it is desired to advertise only an aggregated route instead of all the routes to comprise the aggregate, use
the ip ospf redist-filter command with the redist-control aggregate keyword, as shown (you will also
need to enter the route information as above):
-> ip ospf redist-filter rip 1.1.0.0 255.255.0.0 redist-control aggregate
If it is desired that the subnet routes that fall within the aggregate range should not be advertised, use the
ip ospf redist-filter command with the redist-control keyword as shown (you will also need to enter the
route information as above):
-> ip ospf redist-filter rip 1.1.0.0 255.255.0.0 redist-control no-subnets
Note. By default, filters are set to allow subnet routes to be advertised. If this is the filter action desired, it
is not necessary to use the redist-control keyword.
A cost metric and route tag can be assigned to the routes that are allowed to pass through the filter, by
using the metric and route-tag keywords, as shown (these options are described in the ip ospf redist-
filter command):
-> ip ospf redist-filter rip 1.1.0.0 255.255.0.0 metric 100 route-tag 5
To display all of the configured filters on a router, enter the show ip ospf redist-filter command as shown:
-> show ip ospf redist-filter
To display the configured filters for a specific route or protocol type, enter the show command and the
route or protocol type:
-> show ip ospf redist-filter rip
To display a specific filter, enter the show command with the route or protocol type and the ip address and
mask, as demonstrated:
-> show ip ospf redist-filter rip 1.1.0.0 255.255.0.0
To delete a redistribution filter, enter the ip ospf redist-filter command with the route or protocol type and
its associated IP address and mask, as shown:
-> no ip ospf redist-filter rip 1.1.0.0 255.255.0.0
page 1-28
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
Configuring OSPF
Configuring Router Capabilities
The following list shows various commands that can be useful in tailoring a router’s performance capabili-
ties. All of the listed parameters have defaults that are acceptable for running an OSPF network.
ip ospf exit-overflow-interval Sets the overflow interval value. The overflow interval is the time
whereby the router will wait before attempting to leave the database
overflow state.
ip ospf extlsdb-limit
Sets a limit to the number of external Link State Databases entries
learned by the router. An external LSDB entry is created when the
router learns a link address that exists outside of its Autonomous System
(AS).
ip ospf host
Creates and deletes an OSPF entry for directly attached hosts.
ip ospf mtu-checking
Enables or disables the use of Maximum Transfer Unit (MTU) checking
on received OSPF database description packets.
ip ospf route-tag
ip ospf spf-timer
Configures a tag value for Autonomous System External (ASE) routes
created.
Configures timers for Shortest Path First (SPF) calculation.
To configure a router parameter, enter the parameter at the CLI prompt with the new value or required
variables. For example to set the exit overflow interval to 40, enter:
-> ip ospf exit-overflow-interval 40
To enable MTU checking, enter:
-> ip ospf mtu-checking
To set the route tag to 5, enter:
-> ip ospf route-tag 5
To set the SPF timer delay to 3 and the hold time to 6, enter:
-> ip ospf spf-timer delay 3 hold 6
To return a parameter to its default setting, enter the command with no parameter value, as shown:
-> ip ospf spf-timer
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-29
Configuring OSPF
Configuring OSPF
Configuring Static Neighbors
It is possible to configure neighbors statically on Non Broadcast Multi Access (NBMA), point-to-point,
and point-to-multipoint networks.
NBMA requires all routers attached to the network to communicate directly (unicast), and every attached
router in this network becomes aware of all of its neighbors through configuration. It also requires a
Designated Router (DR) “eligibility” flag to be set for every neighbor.
To set up a router to use NBMA routing, follow the following steps:
1 Create an OSPF interface using the CLI command ip ospf interface and perform all the normal config-
uration for the interface as with broadcast networks (attaching it to an area, enabling the status, etc.).
2 The OSPF interface type for this interface should be set to non-broadcast using the CLI
ip ospf interface type command. For example, to set interface 1.1.1.1 to be an NBMA interface, enter the
following:
-> ip ospf interface 1.1.1.1 type non-broadcast
3 Configure static neighbors for every OSPF router in the network using the ip ospf neighbor command.
For example, to set an OSPF neighbor with an IP address of 1.1.1.8 to be a static neighbor, enter the
following:
-> ip ospf neighbor 1.1.1.8 eligible
The neighbor attaches itself to the right interface by matching the network address of the neighbor and the
interface. If the interface has not yet been created, the neighbor gets attached to the interface as and when
the interface comes up.
If this neighbor is not required to participate in DR election, configure it as non-eligible. The eligibility
can be changed at any time as long as the interface it is attached to is in the disabled state.
page 1-30
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
Configuring OSPF
Configuring Redundant Switches in a Stack for Graceful Restart
By default, OSPF graceful restart is disabled. To configure OSPF graceful restart support use the ip ospf
restart-support command by entering ip ospf restart-support followed by either planned-unplanned
(the default) or planned-only.
For example, to modify OSPF graceful restart so that it only supports planned restarts enter:
-> ip ospf restart-support planned-only
To disable support for graceful restart use the no form of the ip ospf restart-support command by enter-
ing:
-> no ip ospf restart-support
Continuous forwarding during a graceful restart depends on several factors. If the secondary module has a
different router MAC than the primary module, or if one or more ports of a VLAN belonged to the
primary module, spanning tree re-convergence might disrupt forwarding state, even though OSPF
performs a graceful restart.
Note. Graceful restart is only supported on active ports (i.e., interfaces), which are on the secondary or
idle switches in a stack during a takeover. It is not supported on ports on a primary switch in a stack.
Optionally, you can configure graceful restart parameters with the following CLI commands:
ip ospf restart-interval
Configures the grace period for achieving a graceful OSPF restart.
ip ospf restart-helper status
Administratively enables and disables the capability of an OSPF router
to operate in helper mode in response to a router performing a graceful
restart.
ip ospf restart-helper strict-lsa- Administratively enables and disables whether or not a changed Link
checking-status
State Advertisement (LSA) will result in termination of graceful restart
by a helping router.
ip ospf restart initiate
Initiates a planned graceful restart.
For more information about graceful restart commands, see the “OSPF Commands” chapter in the
OmniSwitch CLI Reference Guide.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-31
OSPF Application Example
Configuring OSPF
OSPF Application Example
This section will demonstrate how to set up a simple OSPF network. It uses three routers, each with an
area. Each router uses three VLANs. A backbone connects all the routers. This section will demonstrate
how to set it up by explaining the necessary commands for each router.
The following diagram is a simple OSPF network. It will be created by the steps listed on the following
pages.
VLAN 10
Interface 10.0.0.1
Area 0.0.0.1
Router 1
Router ID 1.1.1.1
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
VLAN 12
Interface 12.x.x.x
VLAN 31
Interface 31.x.x.x
Backbone Area
(Area 0.0.0.0)
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
OmniSwitch 6648
VLAN 23
Interface 23.x.x.x
Area 0.0.0.2
Router 2
Router ID 20.0.0.1
Area 0.0.0.3
Router 3
Router ID 3.3.3.3
VLAN 20
Interface 20.0.0.1
VLAN 30
Interface 30.0.0.1
Three Area OSPF Network
page 1-32
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
OSPF Application Example
Step 1: Prepare the Routers
The first step is to create the VLANs on each router, add an IP interface to the VLAN, assign a port to the
VLAN, and assign a router identification number to the routers. For the backbone, the network design in
this case uses slot 2, port 1 as the egress port and slot 2, port 2 as ingress port on each router. Router 1
connects to Router 2, Router 2 connects to Router 3, and Router 3 connects to Router 1 using 10/100
Ethernet cables.
Note. The ports will be statically assigned to the router, as a VLAN must have a physical port assigned to
it in order for the router port to function. However, the router could be set up in such a way that mobile
ports are dynamically assigned to VLANs using VLAN rules. See the chapter titled “Defining VLAN
Rules” in the OmniSwitch 6600 Family Network Configuration Guide.
The commands setting up VLANs are shown below:
Router 1 (using ports 2/1 and 2/2 for the backbone, and ports 2/3-5 for end devices):
-> vlan 31
-> ip interface vlan-31 vlan 31 address 31.0.0.1 mask 255.0.0.0
-> vlan 31 port default 2/1
-> vlan 12
-> ip interface vlan-12 vlan 12 address 12.0.0.1 mask 255.0.0.0
-> vlan 12 port default 2/2
-> vlan 10
-> ip interface vlan-10 vlan 10 address 10.0.0.1 mask 255.0.0.0
-> vlan 10 port default 2/3-5
-> ip router router-id 1.1.1.1
These commands created VLANs 31, 12, and 10.
• VLAN 31 handles the backbone connection from Router 1 to Router 3, using the IP router port
31.0.0.1 and physical port 2/1.
• VLAN 12 handles the backbone connection from Router 1 to Router 2, using the IP router port
12.0.0.1 and physical port 2/2.
• VLAN 10 handles the device connections to Router 1, using the IP router port 10.0.0.1 and physical
ports 2/3-5. More ports could be added at a later time if necessary.
The router was assigned the Router ID of 1.1.1.1.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-33
OSPF Application Example
Configuring OSPF
Router 2 (using ports 2/1 and 2/2 for the backbone, and ports 2/3-5 for end devices):
-> vlan 12
-> ip interface vlan-12 vlan 12 address 12.0.0.2 mask 255.0.0.0
-> vlan 12 port default 2/1
-> vlan 23
-> ip interface vlan-23 vlan 23 address 23.0.0.2 mask 255.0.0.0
-> vlan 23 port default 2/2
-> vlan 20
-> ip interface vlan-20 vlan 20 address 20.0.0.2 mask 255.0.0.0
-> vlan 20 port default 2/3-5
-> ip router router-id 2.2.2.2
These commands created VLANs 12, 23, and 20.
• VLAN 12 handles the backbone connection from Router 1 to Router 2, using the IP router port 12.0.0.2
and physical port 2/1.
• VLAN 23 handles the backbone connection from Router 2 to Router 3, using the IP router port 23.0.0.2
and physical port 2/2.
• VLAN 20 handles the device connections to Router 2, using the IP router port 20.0.0.2 and physical
ports 2/3-5. More ports could be added at a later time if necessary.
The router was assigned the Router ID of 2.2.2.2.
Router 3 (using ports 2/1 and 2/2 for the backbone, and ports 2/3-5 for end devices)
-> vlan 23
-> ip interface vlan-23 vlan 23 address 23.0.0.3 mask 255.0.0.0
-> vlan 23 port default 2/1
-> vlan 31
-> ip interface vlan-31 vlan 31 address 31.0.0.3 mask 255.0.0.0
-> vlan 31 port default 2/2
-> vlan 30
-> ip interface vlan-30 vlan 30 address 30.0.0.3 mask 255.0.0.0
-> vlan 30 port default 2/3-5
-> ip router router-id 3.3.3.3
These commands created VLANs 23, 31, and 30.
• VLAN 23 handles the backbone connection from Router 2 to Router 3, using the IP router port 23.0.0.3
and physical port 2/1.
• VLAN 31 handles the backbone connection from Router 3 to Router 1, using the IP router port 31.0.0.3
and physical port 2/2.
• VLAN 30 handles the device connections to Router 3, using the IP router port 30.0.0.3 and physical
ports 2/3-5. More ports could be added at a later time if necessary.
The router was assigned the Router ID of 3.3.3.3.
page 1-34
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
OSPF Application Example
Step 2: Enable OSPF
The next step is to load and enable OSPF on each router. The commands for this step are below (the
commands are the same on each router):
-> ip load ospf
-> ip ospf status enable
Step 3: Create and Enable the Areas and Backbone
Now the areas should be created and enabled. In this case, we will create an area for each router, and a
backbone (area 0.0.0.0) that connects the areas.
The commands for this step are below:
Router 1
-> ip ospf area 0.0.0.0
-> ip ospf area 0.0.0.0 status enable
-> ip ospf area 0.0.0.1
-> ip ospf area 0.0.0.1 status enable
These commands created area 0.0.0.0 (the backbone) and area 0.0.0.1 (the area for Router 1). Both of
these areas are also enabled.
Router 2
-> ip ospf area 0.0.0.0
-> ip ospf area 0.0.0.0 status enable
-> ip ospf area 0.0.0.2
-> ip ospf area 0.0.0.2 status enable
These commands created Area 0.0.0.0 (the backbone) and Area 0.0.0.2 (the area for Router 2). Both of
these areas are also enabled.
Router 3
-> ip ospf area 0.0.0.0
-> ip ospf area 0.0.0.0 status enable
-> ip ospf area 0.0.0.3
-> ip ospf area 0.0.0.3 status enable
These commands created Area 0.0.0.0 (the backbone) and Area 0.0.0.3 (the area for Router 3). Both of
these areas are also enabled.
Step 4: Create, Enable, and Assign Interfaces
Next, OSPF interfaces must be created, enabled, and assigned to the areas. The OSPF interfaces should
have the same IP address as the IP router ports created above in “Step 1: Prepare the Routers” on
Router 1
-> ip ospf interface 31.0.0.1
-> ip ospf interface 31.0.0.1 area 0.0.0.0
-> ip ospf interface 31.0.0.1 status enable
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-35
OSPF Application Example
Configuring OSPF
-> ip ospf interface 12.0.0.1
-> ip ospf interface 12.0.0.1 area 0.0.0.0
-> ip ospf interface 12.0.0.1 status enable
-> ip ospf interface 10.0.0.1
-> ip ospf interface 10.0.0.1 area 0.0.0.1
-> ip ospf interface 10.0.0.1 status enable
IP router port 31.0.0.1 was associated to OSPF interface 31.0.0.1, enabled, and assigned to the backbone.
IP router port 12.0.0.1 was associated to OSPF interface 12.0.0.1, enabled, and assigned to the backbone.
IP router port 10.0.0.1 which connects to end stations and attached network devices, was associated to
OSPF interface 10.0.0.1, enabled, and assigned to Area 0.0.0.1.
Alternatively, you can also configure Router 1 with the interface name instead of the IP address as shown
below:
-> ip ospf interface vlan-12
-> ip ospf interface vlan-12 area 0.0.0.0
-> ip ospf interface vlan-12 status enable
-> ip ospf interface vlan-12
-> ip ospf interface vlan-12 area 0.0.0.0
-> ip ospf interface vlan-12 status enable
-> ip ospf interface vlan-10
-> ip ospf interface vlan-10 area 0.0.0.1
-> ip ospf interface vlan-10 status enable
Router 2
-> ip ospf interface 12.0.0.2
-> ip ospf interface 12.0.0.2 area 0.0.0.0
-> ip ospf interface 12.0.0.2 status enable
-> ip ospf interface 23.0.0.2
-> ip ospf interface 23.0.0.2 area 0.0.0.0
-> ip ospf interface 23.0.0.2 status enable
-> ip ospf interface 20.0.0.2
-> ip ospf interface 20.0.0.2 area 0.0.0.2
-> ip ospf interface 20.0.0.2 status enable
IP router port 12.0.0.2 was associated to OSPF interface 12.0.0.2, enabled, and assigned to the backbone.
IP router port 23.0.0.2 was associated to OSPF interface 23.0.0.2, enabled, and assigned to the backbone.
IP router port 20.0.0.2, which connects to end stations and attached network devices, was associated to
OSPF interface 20.0.0.2, enabled, and assigned to Area 0.0.0.2.
Alternatively, you can also configure Router 2 with the interface name instead of the IP address as shown
below:
-> ip ospf interface vlan-12
-> ip ospf interface vlan-12 area 0.0.0.0
-> ip ospf interface vlan-12 status enable
-> ip ospf interface vlan-23
-> ip ospf interface vlan-23 area 0.0.0.0
-> ip ospf interface vlan-23 status enable
page 1-36
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Configuring OSPF
OSPF Application Example
-> ip ospf interface vlan-20
-> ip ospf interface vlan-20 area 0.0.0.2
-> ip ospf interface vlan-20 status enable
Router 3
-> ip ospf interface 23.0.0.3
-> ip ospf interface 23.0.0.3 area 0.0.0.0
-> ip ospf interface 23.0.0.3 status enable
-> ip ospf interface 31.0.0.3
-> ip ospf interface 31.0.0.3 area 0.0.0.0
-> ip ospf interface 31.0.0.3 status enable
-> ip ospf interface 30.0.0.3
-> ip ospf interface 30.0.0.3 area 0.0.0.3
-> ip ospf interface 30.0.0.3 status enable
IP router port 23.0.0.3 was associated to OSPF interface 23.0.0.3, enabled, and assigned to the backbone.
IP router port 31.0.0.3 was associated to OSPF interface 31.0.0.3, enabled, and assigned to the backbone.
IP router port 30.0.0.3, which connects to end stations and attached network devices, was associated to
OSPF interface 30.0.0.3, enabled, and assigned to Area 0.0.0.3.
Alternatively, you can also configure Router 3 with the interface name instead of the IP address as shown
below:
-> ip ospf interface vlan-23
-> ip ospf interface vlan-23 area 0.0.0.0
-> ip ospf interface vlan-23 status enable
-> ip ospf interface vlan-31
-> ip ospf interface vlan-31 area 0.0.0.0
-> ip ospf interface vlan-31 status enable
-> ip ospf interface vlan-30
-> ip ospf interface vlan-30 area 0.0.0.3
-> ip ospf interface vlan-30 status enable
Step 5: Examine the Network
After the network has been created, you can check various aspects of it using show commands:
• For OSPF in general, use the show ip ospf command.
• For areas, use the show ip ospf area command.
• For interfaces, use the show ip ospf interface command.
• To check for adjacencies formed with neighbors, use the show ip ospf neighbor command.
• For routes, use the show ip ospf routes command.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page 1-37
Verifying OSPF Configuration
Configuring OSPF
Verifying OSPF Configuration
To display information about areas, interfaces, virtual links, redistribution, or OPSF in general, use the
show commands listed in the following table:
show ip ospf
Displays OSPF status and general configuration parameters.
Displays information regarding all or specified border routers.
show ip ospf border-routers
show ip ospf ext-lsdb
Displays external Link State Advertisements from the areas to which the
router is attached.
show ip ospf host
Displays information on directly attached hosts.
show ip ospf lsdb
Displays LSAs in the Link State Database associated with each area.
Displays information on OSPF non-virtual neighbor routers
Displays OSPF redistribution filter attributes.
show ip ospf neighbor
show ip ospf redist-filter
show ip ospf redist
Displays the specified redistribution instance that allows routes to be
redistributed into OSPF.
show ip ospf routes
Displays OSPF routes known to the router.
Displays virtual link information.
show ip ospf virtual-link
show ip ospf virtual-neighbor Displays OSPF virtual neighbors.
show ip ospf area
Displays either all OSPF areas, or a specified OSPF area.
show ip ospf area range
Displays all or specified configured area address range summaries for
the given area.
show ip ospf area stub
show ip ospf interface
show ip ospf restart
Displays stub area status.
Displays OSPF interface information.
Displays the OSPF graceful restart related configuration and status.
For more information about the resulting displays form these commands, see the “OSPF Commands”
chapter in the OmniSwitch CLI Reference Guide.
Examples of the show ip ospf, show ip ospf area, and show ip ospf interface command outputs are given
page 1-38
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
A Software License and
Copyright Statements
This appendix contains Alcatel and third-party software vendor license and copyright statements.
Alcatel License Agreement
ALCATEL INTERNETWORKING, INC. (“AII”)
SOFTWARE LICENSE AGREEMENT
IMPORTANT. Please read the terms and conditions of this license agreement carefully before opening
this package.
By opening this package, you accept and agree to the terms of this license agreement. If you are not
willing to be bound by the terms of this license agreement, do not open this package. Please
promptly return the product and any materials in unopened form to the place where you obtained it
for a full refund.
1. License Grant. This is a license, not a sales agreement, between you (the “Licensee”) and AII. AII
hereby grants to Licensee, and Licensee accepts, a non-exclusive license to use program media and
computer software contained therein (the “Licensed Files”) and the accompanying user documentation
(collectively the “Licensed Materials”), only as authorized in this License Agreement. Licensee, subject to
the terms of this License Agreement, may use one copy of the Licensed Files on the Licensee’s system.
Licensee agrees not to assign, sublicense, transfer, pledge, lease, rent, or share their rights under this
License Agreement. Licensee may retain the program media for backup purposes with retention of the
copyright and other proprietary notices. Except as authorized under this paragraph, no copies of the
Licensed Materials or any portions thereof may be made by Licensee and Licensee shall not modify,
decompile, disassemble, reverse engineer, or otherwise attempt to derive the Source Code. Licensee is also
advised that AII products contain embedded software known as firmware which resides in silicon.
Licensee may not copy the firmware or transfer the firmware to another medium.
2. AII’s Rights. Licensee acknowledges and agrees that the Licensed Materials are the sole property of
AII and its licensors (herein “its licensors”), protected by U.S. copyright law, trademark law, and are
licensed on a right to use basis. Licensee further acknowledges and agrees that all rights, title, and interest
in and to the Licensed Materials are and shall remain with AII and its licensors and that no such right,
license, or interest shall be asserted with respect to such copyrights and trademarks. This License Agree-
ment does not convey to Licensee an interest in or to the Licensed Materials, but only a limited right to use
revocable in accordance with the terms of this License Agreement.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page A-1
Alcatel License Agreement
Software License and Copyright Statements
3. Confidentiality. AII considers the Licensed Files to contain valuable trade secrets of AII, the unautho-
rized disclosure of which could cause irreparable harm to AII. Except as expressly set forth herein,
Licensee agrees to use reasonable efforts not to disclose the Licensed Files to any third party and not to
use the Licensed Files other than for the purpose authorized by this License Agreement. This confidential-
ity obligation shall continue after any termination of this License Agreement.
4. Indemnity. Licensee agrees to indemnify, defend and hold AII harmless from any claim, lawsuit, legal
proceeding, settlement or judgment (including without limitation AII’s reasonable United States and local
attorneys’ and expert witnesses’ fees and costs) arising out of or in connection with the unauthorized copy-
ing, marketing, performance or distribution of the Licensed Files.
5. Limited Warranty. AII warrants, for Licensee’s benefit alone, that the program media shall, for a
period of ninety (90) days from the date of commencement of this License Agreement (referred to as the
Warranty Period), be free from defects in material and workmanship. AII further warrants, for Licensee
benefit alone, that during the Warranty Period the Licensed Files shall operate substantially in accordance
with the functional specifications in the User Guide. If during the Warranty Period, a defect in the
Licensed Files appears, Licensee may return the Licensed Files to AII for either replacement or, if so
elected by AII, refund of amounts paid by Licensee under this License Agreement. EXCEPT FOR THE
WARRANTIES SET FORTH ABOVE, THE LICENSED MATERIALS ARE LICENSED “AS IS” AND
AII AND ITS LICENSORS DISCLAIM ANY AND ALL OTHER WARRANTIES, WHETHER
EXPRESS OR IMPLIED, INCLUDING (WITHOUT LIMITATION) ANY IMPLIED WARRANTIES
OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT
ALLOW THE EXCLUSION OF IMPLIED WARRANTIES SO THE ABOVE EXCLUSIONS MAY
NOT APPLY TO LICENSEE. THIS WARRANTY GIVES THE LICENSEE SPECIFIC LEGAL
RIGHTS. LICENSEE MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM STATE TO
STATE.
6. Limitation of Liability. AII’s cumulative liability to Licensee or any other party for any loss or
damages resulting from any claims, demands, or actions arising out of or relating to this License Agree-
ment shall not exceed the license fee paid to AII for the Licensed Materials. IN NO EVENT SHALL AII
BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, OR EXEM-
PLARY DAMAGES OR LOST PROFITS, EVEN IF AII HAS BEEN ADVISED OF THE POSSIBIL-
ITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE LIMITATION OR EXCLUSION
OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITA-
TION OR EXCLUSION TO INCIDENTAL OR CONSEQUENTIAL DAMAGES MAY NOT APPLY
TO LICENSEE.
7. Export Control. This product is subject to the jurisdiction of the United States. Licensee may not
export or reexport the Licensed Files, without complying with all United States export laws and regula-
tions, including but not limited to (i) obtaining prior authorization from the U.S. Department of Commerce
if a validated export license is required, and (ii) obtaining “written assurances” from licensees, if required.
8. Support and Maintenance. Except as may be provided in a separate agreement between AII and
Licensee, if any, AII is under no obligation to maintain or support the copies of the Licensed Files made
and distributed hereunder and AII has no obligation to furnish Licensee with any further assistance, docu-
mentation or information of any nature or kind.
9. Term. This License Agreement is effective upon Licensee opening this package and shall continue until
terminated. Licensee may terminate this License Agreement at any time by returning the Licensed Materi-
als and all copies thereof and extracts therefrom to AII and certifying to AII in writing that all Licensed
Materials and all copies thereof and extracts therefrom have been returned or erased by the memory of
Licensee’s computer or made non-readable. AII may terminate this License Agreement upon the breach by
Licensee of any term hereof. Upon such termination by AII, Licensee agrees to return to AII or destroy the
Licensed Materials and all copies and portions thereof.
page A-2
OmniSwitch 6600 Family Advanced Routing Configuration Guide March 2005
Software License and Copyright Statements
Alcatel License Agreement
10. Governing Law. This License Agreement shall be construed and governed in accordance with the
laws of the State of California.
11. Severability. Should any term of this License Agreement be declared void or unenforceable by any
court of competent jurisdiction, such declaration shall have no effect on the remaining terms herein.
12. No Waiver. The failure of either party to enforce any rights granted hereunder or to take action against
the other party in the event of any breach hereunder shall not be deemed a waiver by that party as to
subsequent enforcement of rights or subsequent actions in the event of future breaches.
13. Notes to United States Government Users. Software and documentation are provided with restricted
rights. Use, duplication or disclosure by the government is subject to (i) restrictions set forth in GSA ADP
Schedule Contract with AII’s reseller(s), or (ii) restrictions set forth in subparagraph (c) (1) and (2) of 48
CFR 52.227-19, as applicable.
14.Third Party Materials. Licensee is notified that the Licensed Files contain third party software and
materials licensed to AII by certain third party licensors. Some third party licensors (e.g., Wind River and
their licensors with respect to the Run-Time Module) are third part beneficiaries to this License Agree-
ment with full rights of enforcement. Please refer to the section entitled “Third Party Licenses and
Notices” on page A-4 for the third party license and notice terms.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page A-3
Third Party Licenses and Notices
Software License and Copyright Statements
Third Party Licenses and Notices
The licenses and notices related only to such third party software are set forth below:
A.Booting and Debugging Non-Proprietary Software
A small, separate software portion aggregated with the core software in this product and primarily used for
initial booting and debugging constitutes non-proprietary software, some of which may be obtained in
source code format from AII for a limited period of time. AII will provide a machine-readable copy of the
applicable non-proprietary software to any requester for a cost of copying, shipping and handling. This
offer will expire 3 years from the date of the first shipment of this product.
B. The OpenLDAP Public License: Version 2.4, 8 December 2000
Redistribution and use of this software and associated documentation (“Software”), with or without modi-
fication, are permitted provided that the following conditions are met:
1 Redistributions of source code must retain copyright statements and notices.
2 Redistributions in binary form must reproduce applicable copyright statements and notices, this list of
conditions, and the following disclaimer in the documentation and/or other materials provided with the
distribution.
3 Redistributions must contain a verbatim copy of this document.
4 The names and trademarks of the authors and copyright holders must not be used in advertising or
otherwise to promote the sale, use or other dealing in this Software without specific, written prior permis-
sion.
5 Due credit should be given to the OpenLDAP Project.
6 The OpenLDAP Foundation may revise this license from time to time. Each revision is distinguished
by a version number. You may use the Software under terms of this license revision or under the terms of
any subsequent revision of the license.
THIS SOFTWARE IS PROVIDED BY THE OPENLDAP FOUNDATION AND CONTRIBUTORS “AS
IS” AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OPENLDAP FOUNDATION OR ITS
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEM-
PLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCURE-
MENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
OpenLDAP is a trademark of the OpenLDAP Foundation.
Copyright 1999-2000 The OpenLDAP Foundation, Redwood City,
California, USA. All Rights Reserved. Permission to copy and
distributed verbatim copies of this document is granted.
page A-4
OmniSwitch 6600 Family Advanced Routing Configuration Guide March 2005
Software License and Copyright Statements
Third Party Licenses and Notices
C. Linux
Linux is written and distributed under the GNU General Public License which means that its source code
is freely-distributed and available to the general public.
D. GNU GENERAL PUBLIC LICENSE: Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is
not allowed.
Preamble
The licenses for most software are designed to take away your freedom to share and change it. By
contrast, the GNU General Public License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This General Public License applies to most of
the Free Software Foundation’s software and to any other program whose authors commit to using it.
(Some other Free Software Foundation software is covered by the GNU Library General Public License
instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are
designed to make sure that you have the freedom to distribute copies of free software (and charge for this
service if you wish), that you receive source code or can get it if you want it, that you can change the soft-
ware or use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask
you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute
copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the
recipients all the rights that you have. You must make sure that they, too, receive or can get the source
code. And you must show them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which
gives you legal permission to copy, distribute and/or modify the software.
Also, for each author’s protection and ours, we want to make certain that everyone understands that there
is no warranty for this free software. If the software is modified by someone else and passed on, we want
its recipients to know that what they have is not the original, so that any problems introduced by others
will not reflect on the original authors’ reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that
redistributors of a free program will individually obtain patent licenses, in effect making the program
proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone’s free use
or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow.
GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING,
DISTRIBUTION AND MODIFICATION
0 This License applies to any program or other work which contains a notice placed by the copyright
holder saying it may be distributed under the terms of this General Public License. The “Program”, below,
refers to any such program or work, and a “work based on the Program” means either the Program or any
derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page A-5
Third Party Licenses and Notices
Software License and Copyright Statements
verbatim or with modifications and/or translated into another language. (Hereinafter, translation is
included without limitation in the term “modification”.) Each licensee is addressed as “you”.
Activities other than copying, distribution and modification are not covered by this License; they are
outside its scope. The act of running the Program is not restricted, and the output from the Program is
covered only if its contents constitute a work based on the Program (independent of having been made by
running the Program). Whether that is true depends on what the Program does.
1 You may copy and distribute verbatim copies of the Program’s source code as you receive it, in any
medium, provided that you conspicuously and appropriately publish on each copy an appropriate copy-
right notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the
absence of any warranty; and give any other recipients of the Program a copy of this License along with
the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer
warranty protection in exchange for a fee.
2 You may modify your copy or copies of the Program or any portion of it, thus forming a work based on
the Program, and copy and distribute such modifications or work under the terms of Section 1 above,
provided that you also meet all of these conditions:
a You must cause the modified files to carry prominent notices stating that you changed the files and
the date of any change.
b You must cause any work that you distribute or publish, that in whole or in part contains or is
derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties
under the terms of this License.
c If the modified program normally reads commands interactively when run, you must cause it, when
started running for such interactive use in the most ordinary way, to print or display an announcement
including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you
provide a warranty) and that users may redistribute the program under these conditions, and telling the
user how to view a copy of this License. (Exception: if the Program itself is interactive but does not
normally print such an announcement, your work based on the Program is not required to print an
announcement.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not
derived from the Program, and can be reasonably considered independent and separate works in them-
selves, then this License, and its terms, do not apply to those sections when you distribute them as sepa-
rate works. But when you distribute the same sections as part of a whole which is a work based on the
Program, the distribution of the whole must be on the terms of this License, whose permissions for other
licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is
not the intent of this section to claim rights or contest your rights to work written entirely by you; rather,
the intent is to exercise the right to control the distribution of derivative or collective works based on the
Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work
based on the Program) on a volume of a storage or distribution medium does not bring the other work
under the scope of this License.
3 You may copy and distribute the Program (or a work based on it, under Section 2) in object code or
executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a Accompany it with the complete corresponding machine-readable source code, which must be
distributed under the terms of Sections 1 and 2 above on a medium customarily used for software inter-
change; or,
page A-6
OmniSwitch 6600 Family Advanced Routing Configuration Guide March 2005
Software License and Copyright Statements
Third Party Licenses and Notices
b Accompany it with a written offer, valid for at least three years, to give any third party, for a charge
no more than your cost of physically performing source distribution, a complete machine-readable
copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange; or,
c Accompany it with the information you received as to the offer to distribute corresponding source
code. (This alternative is allowed only for noncommercial distribution and only if you received the
program in object code or executable form with such an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to it. For an
executable work, complete source code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to control compilation and installation of the
executable. However, as a special exception, the source code distributed need not include anything that is
normally distributed (in either source or binary form) with the major components (compiler, kernel, and so
on) of the operating system on which the executable runs, unless that component itself accompanies the
executable.
If distribution of executable or object code is made by offering access to copy from a designated place,
then offering equivalent access to copy the source code from the same place counts as distribution of the
source code, even though third parties are not compelled to copy the source along with the object code.
4 You may not copy, modify, sublicense, or distribute the Program except as expressly provided under
this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will
automatically terminate your rights under this License. However, parties who have received copies, or
rights, from you under this License will not have their licenses terminated so long as such parties remain
in full compliance.
5 You are not required to accept this License, since you have not signed it. However, nothing else grants
you permission to modify or distribute the Program or its derivative works. These actions are prohibited
by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any
work based on the Program), you indicate your acceptance of this License to do so, and all its terms and
conditions for copying, distributing or modifying the Program or works based on it.
6 Each time you redistribute the Program (or any work based on the Program), the recipient automati-
cally receives a license from the original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further restrictions on the recipients’ exercise of the
rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
7 If, as a consequence of a court judgment or allegation of patent infringement or for any other reason
(not limited to patent issues), conditions are imposed on you (whether by court order, agreement or other-
wise) that contradict the conditions of this License, they do not excuse you from the conditions of this
License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and
any other pertinent obligations, then as a consequence you may not distribute the Program at all. For
example, if a patent license would not permit royalty-free redistribution of the Program by all those who
receive copies directly or indirectly through you, then the only way you could satisfy both it and this
License would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the
balance of the section is intended to apply and the section as a whole is intended to apply in other circum-
stances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or
to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the
free software distribution system, which is implemented by public license practices. Many people have
made generous contributions to the wide range of software distributed through that system in reliance on
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page A-7
Third Party Licenses and Notices
Software License and Copyright Statements
consistent application of that system; it is up to the author/donor to decide if he or she is willing to distrib-
ute software through any other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this
License.
8 If the distribution and/or use of the Program is restricted in certain countries either by patents or by
copyrighted interfaces, the original copyright holder who places the Program under this License may add
an explicit geographical distribution limitation excluding those countries, so that distribution is permitted
only in or among countries not thus excluded. In such case, this License incorporates the limitation as if
written in the body of this License.
9 The Free Software Foundation may publish revised and/or new versions of the General Public License
from time to time. Such new versions will be similar in spirit to the present version, but may differ in
detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies a version number of this
License which applies to it and “any later version”, you have the option of following the terms and condi-
tions either of that version or of any later version published by the Free Software Foundation. If the
Program does not specify a version number of this License, you may choose any version ever published by
the Free Software Foundation.
10If you wish to incorporate parts of the Program into other free programs whose distribution conditions
are different, write to the author to ask for permission. For software which is copyrighted by the Free Soft-
ware Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status of all derivatives of our free soft-
ware and of promoting the sharing and reuse of software generally.
NO WARRANTY
11BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR
THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO
THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARIS-
ING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT
LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES
SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
page A-8
OmniSwitch 6600 Family Advanced Routing Configuration Guide March 2005
Software License and Copyright Statements
Third Party Licenses and Notices
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way
to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source
file to most effectively convey the exclusion of warranty; and each file should have at least the “copy-
right” line and a pointer to where the full notice is found.
<one line to give the program’s name and a brief idea of what it does.> Copyright (C)
19yy <name of author>
This program is free software; you can redistribute it and/or modify it under the terms of
the GNU General Public License as published by the Free Software Foundation; either
version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
for more details.
You should have received a copy of the GNU General Public License along with this
program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge,
MA 02139, USA.
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision comes with
ABSOLUTELY NO WARRANTY; for details type ‘show w’. This is free software,
and you are welcome to redistribute it under certain conditions; type ‘show c’ for details.
The hypothetical commands ‘show w’ and ‘show c’ should show the appropriate parts of the General
Public License. Of course, the commands you use may be called something other than ‘show w’ and
‘show c’; they could even be mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your school, if any, to sign a “copy-
right disclaimer” for the program, if necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program ‘Gnomovision’
(which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into proprietary programs. If
your program is a subroutine library, you may consider it more useful to permit linking proprietary appli-
cations with the library. If this is what you want to do, use the GNU Library General Public License
instead of this License.
URLWatch:
For notice when this page changes, fill in your email address.
Maintained by: Webmaster, Linux Online Inc.
Last modified: 09-Aug-2000 02:03AM.
Views since 16-Aug-2000: 177203.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page A-9
Third Party Licenses and Notices
Software License and Copyright Statements
Material copyright Linux Online Inc.
Design and compilation copyright (c)1994-2002 Linux Online Inc.
Linux is a registered trademark of Linus Torvalds
Tux the Penguin, featured in our logo, was created by Larry Ewing
Consult our privacy statement
URLWatch provided by URLWatch Services.
All rights reserved.
E. University of California
Provided with this product is certain TCP input and Telnet client software developed by the University of
California, Berkeley.
F. Carnegie-Mellon University
Provided with this product is certain BOOTP Relay software developed by Carnegie-Mellon University.
G.Random.c
PR 30872 B Kesner created May 5 2000
PR 30872 B Kesner June 16 2000 moved batch_entropy_process to own task iWhirlpool to make code
more efficient
random.c -- A strong random number generator
Version 1.89, last modified 19-Sep-99
Copyright Theodore Ts’o, 1994, 1995, 1996, 1997, 1998, 1999. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided
that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, and the entire permission notice
in its entirety, including the disclaimer of warranties.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
3. The name of the author may not be used to endorse or promote products derived from this software
without specific prior written permission. ALTERNATIVELY, this product may be distributed under the
terms of the GNU Public License, in which case the provisions of the GPL are required INSTEAD OF the
above restrictions. (This clause is necessary due to a potential bad interaction between the GPL and the
restrictions contained in a BSD-style copyright.)
THIS SOFTWARE IS PROVIDED “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE, ALL OF WHICH ARE HEREBY DISCLAIMED. IN
NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROF-
ITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABIL-
ITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF NOT
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
page A-10
OmniSwitch 6600 Family Advanced Routing Configuration Guide March 2005
Software License and Copyright Statements
Third Party Licenses and Notices
H.Apptitude, Inc.
Provided with this product is certain network monitoring software (“MeterWorks/RMON”) licensed from
Apptitude, Inc., whose copyright notice is as follows: Copyright (C) 1997-1999 by Apptitude, Inc. All
Rights Reserved. Licensee is notified that Apptitude, Inc. (formerly, Technically Elite, Inc.), a California
corporation with principal offices at 6330 San Ignacio Avenue, San Jose, California, is a third party bene-
ficiary to the Software License Agreement. The provisions of the Software License Agreement as applied
to MeterWorks/RMON are made expressly for the benefit of Apptitude, Inc., and are enforceable by
Apptitude, Inc. in addition to AII. IN NO EVENT SHALL APPTITUDE, INC. OR ITS SUPPLIERS BE
LIABLE FOR ANY DAMAGES, INCLUDING COSTS OF PROCUREMENT OF SUBSTITUTE
PRODUCTS OR SERVICES, LOST PROFITS, OR ANY SPECIAL, INDIRECT, CONSEQUENTIAL
OR INCIDENTAL DAMAGES, HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
ARISING IN ANY WAY OUT OF THIS AGREEMENT.
I. Agranat
Provided with this product is certain web server software (“EMWEB PRODUCT”) licensed from Agranat
Systems, Inc. (“Agranat”). Agranat has granted to AII certain warranties of performance, which warran-
ties [or portion thereof] AII now extends to Licensee. IN NO EVENT, HOWEVER, SHALL AGRANAT
BE LIABLE TO LICENSEE FOR ANY INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES
OF LICENSEE OR A THIRD PARTY AGAINST LICENSEE ARISING OUT OF, OR IN CONNEC-
TION WITH, THIS DISTRIBUTION OF EMWEB PRODUCT TO LICENSEE. In case of any termina-
tion of the Software License Agreement between AII and Licensee, Licensee shall immediately return the
EMWEB Product and any back-up copy to AII, and will certify to AII in writing that all EMWEB Prod-
uct components and any copies of the software have been returned or erased by the memory of Licensee’s
computer or made non-readable.
J. RSA Security Inc.
Provided with this product is certain security software (“RSA Software”) licensed from RSA Security Inc.
RSA SECURITY INC. PROVIDES RSA SOFTWARE “AS IS” WITHOUT ANY WARRANTY WHAT-
SOEVER. RSA SECURITY INC. DISCLAIMS ALL WARRANTIES, EXPRESS, IMPLIED OR STAT-
UTORY, AS TO ANY MATTER WHATSOEVER INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT OF
THIRD PARTY RIGHTS.
K.Sun Microsystems, Inc.
This product contains Coronado ASIC, which includes a component derived from designs licensed from
Sun Microsystems, Inc.
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
page A-11
Third Party Licenses and Notices
Software License and Copyright Statements
L. Wind River Systems, Inc.
Provided with this product is certain software (“Run-Time Module”) licensed from Wind River Systems,
Inc. Licensee is prohibited from: (i) copying the Run-Time Module, except for archive purposes consis-
tent with Licensee’s archive procedures; (ii) transferring the Run-Time Module to a third party apart from
the product; (iii) modifying, decompiling, disassembling, reverse engineering or otherwise attempting to
derive the source code of the Run-Time Module; (iv) exporting the Run-Time Module or underlying tech-
nology in contravention of applicable U.S. and foreign export laws and regulations; and (v) using the Run-
Time Module other than in connection with operation of the product. In addition, please be advised that:
(i) the Run-Time Module is licensed, not sold and that AII and its licensors retain ownership of all copies
of the Run-Time Module; (ii) WIND RIVER DISCLAIMS ALL IMPLIED WARRANTIES, INCLUD-
ING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE, (iii) The SOFTWARE LICENSE AGREEMENT EXCLUDES
LIABILITY FOR ANY SPECIAL, INDIRECT, PUNITIVE, INCIDENTAL AND CONSEQUENTIAL
DAMAGES; and (iv) any further distribution of the Run-Time Module shall be subject to the same restric-
tions set forth herein. With respect to the Run-Time Module, Wind River and its licensors are third party
beneficiaries of the License Agreement and the provisions related to the Run-Time Module are made
expressly for the benefit of, and are enforceable by, Wind River and its licensors.
M.Network Time Protocol Version 4
The following copyright notice applies to all files collectively called the Network Time Protocol Version 4
Distribution. Unless specifically declared otherwise in an individual file, this notice applies as if the text
was explicitly included in the file.
***********************************************************************
*
*
*
*
* Copyright (c) David L. Mills 1992-2003
*
* Permission to use, copy, modify, and distribute this software and *
* its documentation for any purpose and without fee is hereby
* granted, provided that the above copyright notice appears in all
* copies and that both the copyright notice and this permission
* notice appear in supporting documentation, and that the name
* University of Delaware not be used in advertising or publicity
* pertaining to distribution of the software without specific,
* written prior permission. The University of Delaware makes no
* representations about the suitability this software for any
* purpose. It is provided "as is" without express or implied
* warranty.
*
*
*
*
*
*
*
*
*
*
*
*
*************************************************************************
page A-12
OmniSwitch 6600 Family Advanced Routing Configuration Guide March 2005
I
Index
interior gateway protocols
OSPF 1-7
A
application examples
OSPF 1-4, 1-32
areas 1-8
backbones 1-8
creating 1-18
deleting 1-19
enabling 1-18
NSSAs 1-12
ranges 1-20
status 1-19
stub 1-11
summarization 1-19
ASBRs 1-26
authentication 1-23
simple 1-23
Autonomous System Boundary Router
see ASBRs
autonomous systems
see AS
L
B
backbones 1-8
M
D
N
defaults
OSPF 1-3
Not-So-Stubby-Areas
see NSSAs
NSSAs 1-12
E
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
Index-1
Index
O
R
Open Shortest Path First
see OSPF
routers
OSPF 1-1
ASBRs 1-9
activating 1-17
OSPF 1-9
areas 1-8
authentication 1-23
backbones 1-8
configuring 1-15
defaults 1-3
S
enabling 1-17
filters 1-26
interfaces 1-22
T
NSSAs 1-12
V
creating 1-25
deleting 1-25
modifying 1-25
overview 1-7
routers 1-9
specifications 1-2
creating 1-27
deleting 1-28
enabling 1-26
authentication 1-23
creating 1-22
deleting 1-22
enabling 1-22
modifying 1-24
creating 1-27
deleting 1-27
enabling 1-26
Index-2
OmniSwitch 6600 Family Advanced Routing Configuration Guide
March 2005
|