draft-ietf-bmwg-ospfconv-intraarea-06.txt   draft-ietf-bmwg-ospfconv-intraarea-07.txt 
Network Working Group Vishwas Manral Network Working Group Vishwas Manral
Internet Draft Netplane Systems Internet Draft Sinett Semiconductors
Russ White Russ White
Cisco Systems Cisco Systems
Aman Shaikh Aman Shaikh
Expiration Date: December 2003 University of California Expiration Date: May 2004 University of California
File Name: draft-ietf-bmwg-ospfconv-intraarea-06.txt June 2003 File Name: draft-ietf-bmwg-ospfconv-intraarea-07.txt November 2003
Benchmarking Basic OPSF Single Router Control Plane Convergence Benchmarking Basic OSPF Single Router Control Plane Convergence
draft-ietf-bmwg-ospfconv-intraarea-06.txt draft-ietf-bmwg-ospfconv-intraarea-07.txt
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet Drafts are working documents of the Internet Engineering Internet Drafts are working documents of the Internet Engineering
Task Force (IETF), its Areas, and its Working Groups. Note that other Task Force (IETF), its Areas, and its Working Groups. Note that other
groups may also distribute working documents as Internet Drafts. groups may also distribute working documents as Internet Drafts.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
draft" or "work in progress". draft" or "work in progress".
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
2. Abstract 2. Abstract
This draft establishes standards for measuring OSPF single router This draft provides suggestions for measuring OSPF single router
control plane convergence [TERM]. Its initial emphasis is on the control plane convergence. Its initial emphasis is on the control
control plane of single OSPF routers. We do not address forwarding plane of single OSPF routers. We do not address forwarding plane
plane performance. performance.
NOTE: Within this document, the word convergence relates to single NOTE: Within this document, the word convergence relates to single
router control plane convergence only. router control plane convergence only.
3. Motivation 3. Motivation
There is a growing interest in routing protocol convergence testing, There is a growing interest in routing protocol convergence testing,
with many people looking at various tests to determine how long it with many people looking at various tests to determine how long it
takes for a network to converge after various conditions occur. The takes for a network to converge after various conditions occur. The
major problem with this sort of testing is that the framework of the major problem with this sort of testing is that the framework of the
skipping to change at page 2, line 29 skipping to change at page 2, line 29
measured. The motivation of the draft is to provide a set of tests measured. The motivation of the draft is to provide a set of tests
that can provide the user comparable data from various vendors with that can provide the user comparable data from various vendors with
which to evaluate the OSPF protocol performance on the devices. which to evaluate the OSPF protocol performance on the devices.
4. Overview & Scope 4. Overview & Scope
While this document describes a specific set of tests aimed at While this document describes a specific set of tests aimed at
characterizing the single router control plane convergence characterizing the single router control plane convergence
performance of OSPF processes in routers or other boxes that performance of OSPF processes in routers or other boxes that
incorporate OSPF functionality, a key objective is to propose incorporate OSPF functionality, a key objective is to propose
methodology that will standardize the conducting and reporting of methodologies that will prdouce directly comparable convergence
convergence-related measurements. related measurements.
Things which are outside the scope of this document include: Things which are outside the scope of this document include:
o The interactions of convergence and forwarding; testing is o The interactions of convergence and forwarding; testing is
restricted to events occurring within the control plane. For- restricted to events occurring within the control plane. For-
warding performance is the primary focus in [INTERCONNECT] warding performance is the primary focus in [INTERCONNECT]
and it is expected to be dealt with in work that ensues from and it is expected to be dealt with in work that ensues from
[FIB-TERM]. [FIB-TERM].
o Inter area route generation, AS-external route generation, o Inter-area route generation, AS-external route generation,
and simultaneous traffic on the control and data paths within and simultaneous traffic on the control and data paths within
the DUT. While the tests outlined in this document measure the DUT. While the tests outlined in this document measure
SPF time, flooding times, and other aspects of all OSPF con- SPF time, flooding times, and other aspects of all OSPF con-
vergence performance, it does not provide tests for measuring vergence performance, it does not provide tests for measuring
external or summary route generation, route translation, or external or summary route generation, route translation, or
other OSPF interarea and external routing performance. These other OSPF inter-area and external routing performance. These
are expected to be dealt with in a later draft. are expected to be dealt with in a later draft.
Other drafts in the future may cover some of the items noted as not Other drafts in the future may cover some of the items noted as not
covered in the scope of this draft. For a discussion of the covered in the scope of this draft. For a discussion of the
terminology used in this draft (in relation to the tests themselves), terminology used in this draft (in relation to the tests themselves),
refer to [TERM]. For a discussion of the applicability of this draft, refer to [TERM]. For a discussion of the applicability of this draft,
refer to [APPLICABILITY]. refer to [APPLICABILITY].
While this draft assumes OSPFv2, which only carries routing informa- While this draft assumes OSPFv2, which only carries routing informa-
tion for IPv4 destinations, nothing in this draft precludes it from tion for IPv4 destinations, nothing in this draft precludes it from
skipping to change at page 6, line 16 skipping to change at page 6, line 16
o Inject a new set of LSAs from the generator towards the o Inject a new set of LSAs from the generator towards the
collector and the DUT. collector and the DUT.
o On the collector, note the time the flooding is complete o On the collector, note the time the flooding is complete
across the link to the generator. Also note the time the across the link to the generator. Also note the time the
flooding is complete across the link from the DUT. flooding is complete across the link from the DUT.
Two measurements can be taken from this test: Two measurements can be taken from this test:
o The time between the last LSA is received on the collec- o The time between the last LSA is received on the collector
tor from the generator and the time the last LSA is from the generator and the time the last LSA is received
received on the collector from the DUT. on the collector from the DUT.
o The time between the last LSA is received on the collector o The time between the last LSA is received on the collector
from the generator and the time the first LSA is received from the generator and the time the first LSA is received
on the collector from the DUT. on the collector from the DUT.
Depending on the number of LSAs flooded, the sizes of the Depending on the number of LSAs flooded, the sizes of the
LSAs, and the rate of flooding, these numbers could vary by LSAs, the number of LSUs, and the rate of flooding, these
some amount. The settings and variances of these numbers numbers could vary by some amount. The settings and variances
should be reported with the test results. of these numbers should be reported with the test results.
This time is important in link state protocols, since the This time is important in link state protocols, since the
loop free nature of the network is reliant on the speed at loop free nature of the network is reliant on the speed at
which revised topology information is flooded. which revised topology information is flooded.
7.3. Shortest Path First Computation Time 7.3. Shortest Path First Computation Time
o Use reference topology 1 (Emulated Toplogy), beginning o Use reference topology 1 (Emulated Toplogy), beginning
with the DUT and the generator fully adjacent. with the DUT and the generator fully adjacent.
skipping to change at page 11, line 29 skipping to change at page 11, line 29
o Note the time of the last hello received from R1 on R2. o Note the time of the last hello received from R1 on R2.
o Note the time of the first network LSA generated by the o Note the time of the first network LSA generated by the
DUT as received on R2. DUT as received on R2.
The time between the last hello received on R2 and the first The time between the last hello received on R2 and the first
network LSA generated by the DUT should be taken as the network LSA generated by the DUT should be taken as the
amount of time required for the DUT to complete a designated amount of time required for the DUT to complete a designated
router election computation. Note this test includes the dead router election computation. Note this test includes the dead
interval timer at the DUT, so this time can be factored out, interval timer at the DUT, so this time may be factored out,
or the hello and dead intervals reduced to make these timers or the hello and dead intervals reduced to make these timers
impact the overall test times less. All changed timers, the impact the overall test times less. All changed timers, the
number of routers connected to the link, and other variable number of routers connected to the link, and other variable
factors should be noted in the test results. factors should be noted in the test results.
8.5. Initial convergence Time on a Designated Router Electing (Broad- 8.5. Initial Convergence Time on a Broadcast Network, Test 1
cast) Network
o Using reference topology 3 (Broadcast Network), begin with o Using reference topology 3 (Broadcast Network), begin with
the DUT connected to the network with OSPF enabled. OSPF the DUT connected to the network with OSPF enabled. OSPF
should be enabled on R1, but the broadcast link should be should be enabled on R1, but the broadcast link should be
disabled. disabled.
o Enable the broadcast link between R1 and the DUT. Note the o Enable the broadcast link between R1 and the DUT. Note the
time of the first hello received by R1. time of the first hello received by R1.
o Note the time the first network LSA is flooded by the DUT o Note the time the first network LSA is flooded by the DUT
skipping to change at page 12, line 25 skipping to change at page 12, line 25
attached to the broadcast network, and varying sets of LSAs attached to the broadcast network, and varying sets of LSAs
being advertised to the DUT from the routers attached to the being advertised to the DUT from the routers attached to the
broadcast network. Variations in the LSA sets and other fac- broadcast network. Variations in the LSA sets and other fac-
tors should be noted in the test results. tors should be noted in the test results.
The time required to elect a designated router, as measured The time required to elect a designated router, as measured
in Designated Router Election Time on A Broadcast Network, in Designated Router Election Time on A Broadcast Network,
above, may be subtracted from the results of this test to above, may be subtracted from the results of this test to
provide just the convergence time across a broadcast network. provide just the convergence time across a broadcast network.
8.6. Link Down with Layer 2 Detection 8.6. Initial Convergence Time on a Broadcast Network, Test 2
o Using reference topology 3 (Broadcast Network), begin with
the DUT connected to the network with OSPF enabled. OSPF
should be enabled on R1, but the broadcast link should be
disabled.
o Enable the broadcast link between R1 and the DUT. Note the
time of the first hello transmitted by the DUT with a
designated router listed.
o Note the time the first network LSA is flooded by the DUT
at R1.
o The differential between the first hello with a designated
router lists and the first network LSA is the time
required by the DUT to converge on this new topology.
8.7. Link Down with Layer 2 Detection
o Using reference topology 4 (Parallel Links), begin with o Using reference topology 4 (Parallel Links), begin with
OSPF in the full state between the generator and the DUT. OSPF in the full state between the generator and the DUT.
Both links should be point-to-point links with the ability Both links should be point-to-point links with the ability
to notify the operating system immediately upon link to notify the operating system immediately upon link
failure. failure.
o Disable link 1; this should be done in such a way that the o Disable link 1; this should be done in such a way that the
keepalive timers at the data link layer will have no keepalive timers at the data link layer will have no
impact on the DUT recognizing the link failure (the impact on the DUT recognizing the link failure (the
skipping to change at page 13, line 5 skipping to change at page 13, line 25
o At the generator, note the time of the receipt of the new o At the generator, note the time of the receipt of the new
router LSA from the DUT notifying the generator of the router LSA from the DUT notifying the generator of the
link 2 failure. link 2 failure.
The difference in the time between the initial link failure The difference in the time between the initial link failure
and the receipt of the LSA on the generator across link 2 and the receipt of the LSA on the generator across link 2
should be taken as the time required for an OSPF implementa- should be taken as the time required for an OSPF implementa-
tion to recognize and process a link failure. tion to recognize and process a link failure.
8.7. Link Down with Layer 3 Detection 8.8. Link Down with Layer 3 Detection
o Using reference topology 4 (Parallel Links), begin with o Using reference topology 4 (Parallel Links), begin with
OSPF in the full state between the generator and the DUT. OSPF in the full state between the generator and the DUT.
o Disable OSPF processing on link 1 from the generator. This o Disable OSPF processing on link 1 from the generator. This
should be done in such a way so it does not affect link should be done in such a way so it does not affect link
status; the DUT must note the failure of the adjacency status; the DUT must note the failure of the adjacency
through the dead interval. through the dead interval.
o At the generator, note the time of the receipt of the new o At the generator, note the time of the receipt of the new
skipping to change at page 13, line 38 skipping to change at page 14, line 19
10. Acknowledgements 10. Acknowledgements
Thanks to Howard Berkowitz, (hcb@clark.net), for his encouragement Thanks to Howard Berkowitz, (hcb@clark.net), for his encouragement
and support. Thanks also to Gurpreet Singh and support. Thanks also to Gurpreet Singh
(Gurpreet.Singh@SpirentCom.COM) and Yasuhiro Ohara (Gurpreet.Singh@SpirentCom.COM) and Yasuhiro Ohara
(yasu@sfc.wide.ad.jp) for their comments as well. (yasu@sfc.wide.ad.jp) for their comments as well.
11. Normative References 11. Normative References
[OPSF]Moy, J., "OSPF Version 2", RFC 2328, April 1998. [OSPF]Moy, J., "OSPF Version 2", RFC 2328, April 1998.
[TERM]Manral, V., "OSPF Convergence Testing Terminiology and Concepts", [TERM]Manral, V., "OSPF Convergence Testing Terminiology and Concepts",
draft-ietf-bmwg-ospfconv-term-04, March 2003 draft-ietf-bmwg-ospfconv-term-04, March 2003
[APPLICABILITY] [APPLICABILITY]
Manral, V., "Benchmarking Applicability for Basic OSPF Conver- Manral, V., "Benchmarking Applicability for Basic OSPF Conver-
gence", draft-ietf-bmwg-ospfconv-applicability-03, March 2003 gence", draft-ietf-bmwg-ospfconv-applicability-03, March 2003
12. Informative References 12. Informative References
skipping to change at page 14, line 26 skipping to change at page 15, line 10
Trotter, G., "Terminology for Forwarding Information Base (FIB) Trotter, G., "Terminology for Forwarding Information Base (FIB)
based Router Performance", RFC3222, October 2001. based Router Performance", RFC3222, October 2001.
[BLACKBOX] [BLACKBOX]
Shaikh, Aman, Greenberg, Albert, "Experience in Black-Box OSPF Shaikh, Aman, Greenberg, Albert, "Experience in Black-Box OSPF
measurement" measurement"
13. Authors' Addresses 13. Authors' Addresses
Vishwas Manral Vishwas Manral
Netplane Systems Sinett Semiconductors
189 Prashasan Nagar 1st floor, Embassy Icon Annex, 2/1 Infantry Road,
Road number 72 Bangalore, India
Jubilee Hills
Hyderabad, India
vmanral@netplane.com email: vishwas@sinett.com
Russ White Russ White
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Rd. 7025 Kit Creek Rd.
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
riw@cisco.com riw@cisco.com
Aman Shaikh Aman Shaikh
University of California University of California
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/