draft-ietf-bmwg-igp-dataplane-conv-meth-05.txt   draft-ietf-bmwg-igp-dataplane-conv-meth-06.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: October 2005 Expires in: December 2005
Scott Poretsky Scott Poretsky
Quarry Technologies Quarry Technologies
Brent Imhoff Brent Imhoff
LightCore LightCore
February 2005 June 2005
Benchmarking Methodology for Benchmarking Methodology for
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-meth-05.txt> <draft-ietf-bmwg-igp-dataplane-conv-meth-06.txt>
Intellectual Property Rights (IPR) statement: Intellectual Property Rights (IPR) statement:
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which I am aware have been disclosed, or applicable patent or other IPR claims of which he or she is aware
will be disclosed, and any of which I become aware will be disclosed, have been or will be disclosed, and any of which he or she becomes
in accordance with RFC 3668. aware will be disclosed, in accordance with Section 6 of BCP 79.
Status of this Memo 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 Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups June also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and June be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." 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.
skipping to change at page 2, line 14 skipping to change at page 2, line 14
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
Table of Contents Table of Contents
1. Introduction ...............................................2 1. Introduction ...............................................2
2. Existing definitions .......................................2 2. Existing definitions .......................................2
3. Test Setup..................................................3 3. Test Setup..................................................3
3.1 Test Topologies............................................3 3.1 Test Topologies............................................3
3.2 Test Considerations........................................4 3.2 Test Considerations........................................4
3.3 Reporting Format...........................................6 3.3 Reporting Format...........................................6
4. Test Cases..................................................6 4. Test Cases..................................................7
4.1 Convergence Due to Link Failure............................6 4.1 Convergence Due to Link Failure............................7
4.1.1 Convergence Due to Local Interface Failure...............6 4.1.1 Convergence Due to Local Interface Failure...............7
4.1.2 Convergence Due to Neighbor Interface Failure............7 4.1.2 Convergence Due to Neighbor Interface Failure............7
4.1.3 Convergence Due to Remote Interface Failure..............7 4.1.3 Convergence Due to Remote Interface Failure..............8
4.2 Convergence Due to Layer 2 Session Failure.................8 4.2 Convergence Due to Layer 2 Session Failure.................9
4.3 Convergence Due to IGP Adjacency Failure...................9 4.3 Convergence Due to IGP Adjacency Failure...................10
4.4 Convergence Due to Route Withdrawal........................9 4.4 Convergence Due to Route Withdrawal........................10
4.5 Convergence Due to Cost Change.............................10 4.5 Convergence Due to Cost Change.............................11
4.6 Convergence Due to ECMP Member Interface Failure...........10 4.6 Convergence Due to ECMP Member Interface Failure...........12
4.7 Convergence Due to Parallel Link Interface Failure.........11 4.7 Convergence Due to Parallel Link Interface Failure.........12
5. Security Considerations.....................................12 5. Security Considerations.....................................13
6. Normative References........................................12 6. Normative References........................................13
7. Author's Address............................................12 7. Author's Address............................................13
1. Introduction 1. Introduction
This draft describes the methodology for benchmarking IGP Route This draft describes the methodology for benchmarking IGP Route
Convergence. The applicability of this testing is described in Convergence. The applicability of this testing is described in
[1] and the new terminology that it introduces is defined in [2]. [1] and the new terminology that it introduces is defined in [2].
Service Providers use IGP Convergence time as a key metric of Service Providers use IGP Convergence time as a key metric of
router design and architecture. Customers of Service Providers router design and architecture. Customers of Service Providers
observe convergence time by packet loss, so IGP Route Convergence observe convergence time by packet loss, so IGP Route Convergence
is considered a Direct Measure of Quality (DMOQ). The test cases is considered a Direct Measure of Quality (DMOQ). The test cases
in this document are black-box tests that emulate the network in this document are black-box tests that emulate the network
events that cause route convergence, as described in [1]. The events that cause route convergence, as described in [1]. The
black-box test designs benchmark the data plane accounting for black-box test designs benchmark the data plane accounting for
all of the factors contributing to convergence time, as discussed all of the factors contributing to convergence time, as discussed
in [1]. The methodology (and terminology) for benchmarking route in [1]. The methodology (and terminology) for benchmarking route
convergence can be applied to any link-state IGP such as ISIS [3] convergence can be applied to any link-state IGP such as ISIS [3]
and OSPF [4]. These methodologies apply to IPv4 and IPv6 traffic and OSPF [4]. These methodologies apply to IPv4 and IPv6 traffic
as well as IPv4 and IPv6 IGPs. as well as IPv4 and IPv6 IGPs.
2. Existing definitions 2. Existing definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "JUNE", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119 document are to be interpreted as described in BCP 14, RFC 2119
[Br97]. RFC 2119 defines the use of these key words to help make the [Br97]. RFC 2119 defines the use of these key words to help make the
intent of standards track documents as clear as possible. While this intent of standards track documents as clear as possible. While this
document uses these keywords, this document is not a standards track document uses these keywords, this document is not a standards track
document. document.
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
3. Test Setup 3. Test Setup
3.1 Test Topologies 3.1 Test Topologies
Figure 1 shows the test topology to measure IGP Route Convergence due Figure 1 shows the test topology to measure IGP Route Convergence due
to local Convergence Events such as SONET Link Failure, Layer 2 Session to local Convergence Events such as SONET Link Failure, Layer 2 Session
Failure, IGP Adjacency Failure, Route Withdrawal, and route cost Failure, IGP Adjacency Failure, Route Withdrawal, and route cost
change. These test cases discussed in section 4 provide route change. These test cases discussed in section 4 provide route
convergence times that account for the Event Detection time, SPF convergence times that account for the Event Detection time, SPF
Processing time, and FIB Update time. These times are measured Processing time, and FIB Update time. These times are measured
by observing packet loss in the data plane. by observing packet loss in the data plane.
--------- Ingress Interface --------- --------- Ingress Interface ---------
| |<------------------------------| | | |<--------------------------------| |
| | | | | | | |
| | Preferred Egress Interface | | | | Preferred Egress Interface | |
| DUT |------------------------------>|Tester | | DUT |-------------------------------->| Tester|
| | | | | | | |
| |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>| | | |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>| |
| | Next-Best Egress Interface | | | | Next-Best Egress Interface | |
--------- --------- --------- ---------
Figure 1. IGP Route Convergence Test Topology for Local Changes Figure 1. IGP Route Convergence Test Topology for Local Changes
Figure 2 shows the test topology to measure IGP Route Convergence Figure 2 shows the test topology to measure IGP Route Convergence
time due to remote changes in the network topology. These times are time due to remote changes in the network topology. These times are
measured by observing packet loss in the data plane. In this measured by observing packet loss in the data plane. In this
topology the three routers are considered a System Under Test (SUT). topology the three routers are considered a System Under Test (SUT).
NOTE: All routers in the SUT must be the same model and identically configured. NOTE: All routers in the SUT must be the same model and identically
configured.
----- ----------- ----- ---------
| | Preferred | | | | Preferred | |
----- |R2 |---------------------->| | ----- |R2 |---------------------->| |
| |-->| | Egress Interface | | | |-->| | Egress Interface | |
| | ----- | | | | ----- | |
|R1 | | Tester | |R1 | | Tester |
| | ----- | | | | ----- | |
| |-->| | Next-Best | | | |-->| | Next-Best | |
----- |R3 |~~~~~~~~~~~~~~~~~~~~~~>| | ----- |R3 |~~~~~~~~~~~~~~~~~~~~~~>| |
^ | | Egress Interface | | ^ | | Egress Interface | |
| ----- ----------- | ----- ---------
| | | |
|-------------------------------------- |--------------------------------------
Ingress Interface Ingress Interface
Figure 2. IGP Route Convergence Test Topology Figure 2. IGP Route Convergence Test Topology
for Remote Changes for Remote Changes
Figure 3 shows the test topology to measure IGP Route Convergence Figure 3 shows the test topology to measure IGP Route Convergence
time with members of an Equal Cost Multipath (ECMP) Set. These times are time with members of an Equal Cost Multipath (ECMP) Set. These times are
measured by observing packet loss in the data plane. In this topology, measured by observing packet loss in the data plane. In this topology,
skipping to change at page 4, line 54 skipping to change at page 4, line 54
for Parallel Link Convergence for Parallel Link Convergence
3.2 Test Considerations 3.2 Test Considerations
3.2.1 IGP Selection 3.2.1 IGP Selection
The test cases described in section 4 can be used for ISIS or The test cases described in section 4 can be used for ISIS or
OSPF. The Route Convergence test methodology for both is OSPF. The Route Convergence test methodology for both is
identical. The IGP adjacencies are established on the Preferred identical. The IGP adjacencies are established on the Preferred
Egress Interface and Next-Best Egress Interface. Egress Interface and Next-Best Egress Interface.
3.2.2 BGP Configuration 3.2.2 BGP Configuration
The obtained results for IGP Route Convergence may vary if The obtained results for IGP Route Convergence June vary if
BGP routes are installed. It is recommended that the IGP BGP routes are installed. It is recommended that the IGP
Convergence times be benchmarked without BGP routes installed. Convergence times be benchmarked without BGP routes installed.
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
3.2.3 IGP Route Scaling 3.2.3 IGP Route Scaling
The number of IGP routes will impact the measured IGP Route The number of IGP routes will impact the measured IGP Route
Convergence because convergence for the entire IGP route table is Convergence because convergence for the entire IGP route table is
measured. For results similar to those that would be observed in measured. For results similar to those that would be observed in
an operational network it is recommended that the number of an operational network it is recommended that the number of
skipping to change at page 5, line 40 skipping to change at page 5, line 40
3.2.5 Convergence Time Metrics 3.2.5 Convergence Time Metrics
The recommended value for the Packet Sampling Interval [2] is The recommended value for the Packet Sampling Interval [2] is
100 milliseconds. Rate-Derived Convergence Time [2] is the 100 milliseconds. Rate-Derived Convergence Time [2] is the
preferred benchmark for IGP Route Convergence. This benchmark preferred benchmark for IGP Route Convergence. This benchmark
must always be reported when the Packet Sampling Interval [2] must always be reported when the Packet Sampling Interval [2]
<= 100 milliseconds. If the test equipment does not permit <= 100 milliseconds. If the test equipment does not permit
the Packet Sampling Interval to be set as low as 100 msec, the Packet Sampling Interval to be set as low as 100 msec,
then both the Rate-Derived Convergence Time and Loss-Derived then both the Rate-Derived Convergence Time and Loss-Derived
Convergence Time [2] must be reported. The Packet Sampling Convergence Time [2] must be reported. The Packet Sampling
Interval value is the smallest measurable convergence time. Interval value MUST be the smallest measurable convergence
time.
3.2.6 Offered Load
An offered Load of maximum forwarding rate at a fixed packet size
is recommended for accurate measurement. Forwarding Rate must be
measured at the Preferred Egress Interface and the Next-Best
Egress Interface. The duration of offered load must be greater
than the convergence time. The destinations for the offered load
must be distributed such that all routes are matched. This
enables Full Convergence [2] to be observed.
3.2.7 Interface Types 3.2.6 Interface Types
All test cases in this methodology document may be executed with All test cases in this methodology document June be executed with
any interface type. All interfaces MUST BE the same media and any interface type. All interfaces MUST be the same media and
link speed for each test case. Media and protocols MUST be Throughout [5,6] for each test case. Media and protocols MUST
configured for minimum failure detection delay to minimize the be configured for minimum failure detection delay to minimize
contribution to the measured Convergence time. For example, the contribution to the measured Convergence time. For example,
configure SONET with minimum carrier-loss-delay. configure SONET with minimum carrier-loss-delay or Bi-directional
Forwarding Detection (BFD) [7].
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
3.2.7 Offered Load
The offered Load MUST be the Throughput of the device as defined
in [5] and benchmarked in [6] at a fixed packet size. The packet
size is selectable and MUST be recorded. The Throughput MUST be
measured at the Preferred Egress Interface and the Next-Best
Egress Interface. The duration of offered load MUST be greater
than the convergence time. The destination addresses for the
offered load MUST be distributed such that all routes are matched.
This enables Full Convergence [2] to be observed.
3.3 Reporting Format 3.3 Reporting Format
For each test case, it is recommended that the following reporting For each test case, it is recommended that the following reporting
format be completed: format be completed:
Parameter Units Parameter Units
--------- ----- --------- -----
IGP (ISIS or OSPF) IGP (ISIS or OSPF)
Interface Type (GigE, POS, ATM, etc.) Interface Type (GigE, POS, ATM, etc.)
Packet Size bytes Packet Size offered to DUT bytes
IGP Routes number of IGP routes IGP Routes advertised to DUT number of IGP routes
Packet Sampling Interval seconds or milliseconds Packet Sampling Interval on Tester seconds or milliseconds
IGP Timer Values IGP Timer Values configured on DUT
SONET Failure Indication Delay seconds or milliseconds SONET Failure Indication Delay seconds or milliseconds
IGP Hello Timer seconds or milliseconds IGP Hello Timer seconds or milliseconds
IGP Dead-Interval seconds or milliseconds IGP Dead-Interval seconds or milliseconds
LSA Generation Delay seconds or milliseconds LSA Generation Delay seconds or milliseconds
LSA Flood Packet Pacing seconds or milliseconds LSA Flood Packet Pacing seconds or milliseconds
LSA Retransmission Packet Pacing seconds or milliseconds LSA Retransmission Packet Pacing seconds or milliseconds
SPF Delay seconds or milliseconds SPF Delay seconds or milliseconds
Benchmarks Benchmarks
Rate-Derived Convergence Time seconds or milliseconds Rate-Derived Convergence Time seconds or milliseconds
Loss-Derived Convergence Time seconds or milliseconds Loss-Derived Convergence Time seconds or milliseconds
Restoration Convergence Time seconds or milliseconds Restoration Convergence Time seconds or milliseconds
IGP Data Plane Route Convergence
4. Test Cases 4. Test Cases
4.1 Convergence Due to Link Failure 4.1 Convergence Due to Link Failure
4.1.1 Convergence Due to Local Interface Failure 4.1.1 Convergence Due to Local Interface Failure
Objective Objective
To obtain the IGP Route Convergence due to a local link To obtain the IGP Route Convergence due to a local link
failure event at the DUT's Local Interface. failure event at the DUT's Local Interface.
Procedure Procedure
1. Advertise matching IGP routes from Tester to DUT on 1. Advertise matching IGP routes from Tester to DUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of the [2] using the topology shown in Figure 1. Set the cost of the
routes so that the Preferred Egress Interface is the preferred routes so that the Preferred Egress Interface is the preferred
next-hop. next-hop.
2. Send traffic at maximum forwarding rate to destinations 2. Send offered load at measured Throughput with fixed packet size
matching all IGP routes from Tester to DUT on Ingress Interface to destinations matching all IGP routes from Tester to DUT on
[2]. Ingress Interface [2].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Remove SONET on DUT's Local Interface [2] by performing an 4. Remove link on DUT's Local Interface [2] by performing an
administrative shutdown of the interface. administrative shutdown of the interface.
5. Measure Rate-Derived Convergence Time [2] as DUT detects the 5. Measure Rate-Derived Convergence Time [2] as DUT detects the
link down event and converges all IGP routes and traffic over link down event and converges all IGP routes and traffic over
the Next-Best Egress Interface. the Next-Best Egress Interface.
6. Stop offered load. Wait 30 seconds for queues to drain. 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
7. Restore SONET on DUT's Local Interface by administratively 7. Restore link on DUT's Local Interface by administratively
enabling the interface. enabling the interface.
IGP Data Plane Route Convergence
8. Measure Restoration Convergence Time [2] as DUT detects the link 8. Measure Restoration Convergence Time [2] as DUT detects the link
up event and converges all IGP routes and traffic back to the up event and converges all IGP routes and traffic back to the
Preferred Egress Interface. Preferred Egress Interface.
Results Results
The measured IGP Convergence time is influenced by the Local The measured IGP Convergence time is influenced by the Local
SONET indication, SPF delay, SPF Holdtime, SPF Execution link failure indication, SPF delay, SPF Holdtime, SPF Execution
Time, Tree Build Time, and Hardware Update Time. Time, Tree Build Time, and Hardware Update Time.
4.1.2 Convergence Due to Neighbor Interface Failure 4.1.2 Convergence Due to Neighbor Interface Failure
Objective Objective
To obtain the IGP Route Convergence due to a local link To obtain the IGP Route Convergence due to a local link
failure event at the Tester's Neighbor Interface. failure event at the Tester's Neighbor Interface.
Procedure Procedure
1. Advertise matching IGP routes from Tester to DUT on 1. Advertise matching IGP routes from Tester to DUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [2] using the topology shown in Figure 1. Set the cost of
the routes so that the Preferred Egress Interface is the the routes so that the Preferred Egress Interface is the
preferred next-hop. preferred next-hop.
2. Send traffic at maximum forwarding rate to destinations matching 2. Send offered load at measured Throughput with fixed packet size
all IGP routes from Tester to DUT on Ingress Interface [2]. to destinations matching all IGP routes from Tester to DUT on
Ingress Interface [2].
IGP Data Plane Route Convergence
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Remove SONET on Tester's Neighbor Interface [2] connected to 4. Remove link on Tester's Neighbor Interface [2] connected to
DUT' s Preferred Egress Interface. DUT' s Preferred Egress Interface.
5. Measure Rate-Derived Convergence Time [2] as DUT detects the 5. Measure Rate-Derived Convergence Time [2] as DUT detects the
link down event and converges all IGP routes and traffic over link down event and converges all IGP routes and traffic over
the Next-Best Egress Interface. the Next-Best Egress Interface.
6. Stop offered load. Wait 30 seconds for queues to drain. 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
7. Restore SONET on Tester's Neighbor Interface connected to 7. Restore link on Tester's Neighbor Interface connected to
DUT's Preferred Egress Interface. DUT's Preferred Egress Interface.
8. Measure Restoration Convergence Time [2] as DUT detects the 8. Measure Restoration Convergence Time [2] as DUT detects the
link up event and converges all IGP routes and traffic back to link up event and converges all IGP routes and traffic back to
the Preferred Egress Interface. the Preferred Egress Interface.
Results Results
The measured IGP Convergence time is influenced by the Local The measured IGP Convergence time is influenced by the Local
SONET indication, SPF delay, SPF Holdtime, SPF Execution link failure indication, SPF delay, SPF Holdtime, SPF Execution
Time, Tree Build Time, and Hardware Update Time. Time, Tree Build Time, and Hardware Update Time.
4.1.3 Convergence Due to Remote Interface Failure 4.1.3 Convergence Due to Remote Interface Failure
Objective Objective
To obtain the IGP Route Convergence due to a Remote Interface To obtain the IGP Route Convergence due to a Remote Interface
Failure event. Failure event.
Procedure Procedure
1. Advertise matching IGP routes from Tester to SUT on 1. Advertise matching IGP routes from Tester to SUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 2. Set the cost of the [2] using the topology shown in Figure 2. Set the cost of the
routes so that the Preferred Egress Interface is the preferred routes so that the Preferred Egress Interface is the preferred
next-hop. next-hop.
2. Send offered load at measured Throughput with fixed packet size
IGP Data Plane Route Convergence to destinations matching all IGP routes from Tester to DUT on
Ingress Interface [2].
2. Send traffic at maximum forwarding rate to destinations matching
all IGP routes from Tester to DUT on Ingress Interface [2].
3. Verify traffic is routed over Preferred Egress Interface. 3. Verify traffic is routed over Preferred Egress Interface.
4. Remove SONET on Tester's Neighbor Interface [2] connected to 4. Remove link on Tester's Neighbor Interface [2] connected to
SUT' s Preferred Egress Interface. SUT' s Preferred Egress Interface.
5. Measure Rate-Derived Convergence Time [2] as SUT detects 5. Measure Rate-Derived Convergence Time [2] as SUT detects
the link down event and converges all IGP routes and traffic the link down event and converges all IGP routes and traffic
over the Next-Best Egress Interface. over the Next-Best Egress Interface.
6. Stop offered load. Wait 30 seconds for queues to drain. 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
7. Restore SONET on Tester's Neighbor Interface connected to 7. Restore link on Tester's Neighbor Interface connected to
DUT's Preferred Egress Interface. DUT's Preferred Egress Interface.
8. Measure Restoration Convergence Time [2] as DUT detects the 8. Measure Restoration Convergence Time [2] as DUT detects the
link up event and converges all IGP routes and traffic back to link up event and converges all IGP routes and traffic back to
the Preferred Egress Interface. the Preferred Egress Interface.
IGP Data Plane Route Convergence
Results Results
The measured IGP Convergence time is influenced by the The measured IGP Convergence time is influenced by the
SONET failure indication, LSA/LSP Flood Packet Pacing, link failure failure indication, LSA/LSP Flood Packet Pacing,
LSA/LSP Retransmission Packet Pacing, LSA/LSP Generation LSA/LSP Retransmission Packet Pacing, LSA/LSP Generation
time, SPF delay, SPF Holdtime, SPF Execution Time, Tree time, SPF delay, SPF Holdtime, SPF Execution Time, Tree
Build Time, and Hardware Update Time. The additional Build Time, and Hardware Update Time. The additional
convergence time contributed by LSP Propagation can be convergence time contributed by LSP Propagation can be
obtained by subtracting the Rate-Derived Convergence Time obtained by subtracting the Rate-Derived Convergence Time
measured in 4.1.2 (Convergence Due to Neighbor Interface measured in 4.1.2 (Convergence Due to Neighbor Interface
Failure) from the Rate-Derived Convergence Time measured in Failure) from the Rate-Derived Convergence Time measured in
this test case. this test case.
4.2 Convergence Due to Layer 2 Session Failure 4.2 Convergence Due to Layer 2 Session Failure
Objective Objective
To obtain the IGP Route Convergence due to a Local Layer 2 Session To obtain the IGP Route Convergence due to a Local Layer 2 Session
failure event. failure event.
Procedure Procedure
1. Advertise matching IGP routes from Tester to DUT on 1. Advertise matching IGP routes from Tester to DUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [2] using the topology shown in Figure 1. Set the cost of
the routes so that the IGP routes along the Preferred Egress the routes so that the IGP routes along the Preferred Egress
Interface is the preferred next-hop. Interface is the preferred next-hop.
2. Send traffic at maximum forwarding rate to destinations 2. Send offered load at measured Throughput with fixed packet size
matching all IGP routes from Tester to DUT on Ingress to destinations matching all IGP routes from Tester to DUT on
Interface [2]. Ingress Interface [2].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Remove Layer 2 session from Tester's Neighbor Interface [2] 4. Remove Layer 2 session from Tester's Neighbor Interface [2]
connected to Preferred Egress Interface. connected to Preferred Egress Interface.
5. Measure Rate-Derived Convergence Time [2] as DUT detects the 5. Measure Rate-Derived Convergence Time [2] as DUT detects the
Layer 2 session down event and converges all IGP routes and Layer 2 session down event and converges all IGP routes and
traffic over the Next-Best Egress Interface. traffic over the Next-Best Egress Interface.
6. Restore Layer 2 session on DUT's Preferred Egress Interface. 6. Restore Layer 2 session on DUT's Preferred Egress Interface.
7. Measure Restoration Convergence Time [2] as DUT detects the 7. Measure Restoration Convergence Time [2] as DUT detects the
session up event and converges all IGP routes and traffic over session up event and converges all IGP routes and traffic over
the Preferred Egress Interface. the Preferred Egress Interface.
IGP Data Plane Route Convergence
Results Results
The measured IGP Convergence time is influenced by the Layer 2 The measured IGP Convergence time is influenced by the Layer 2
failure indication, SPF delay, SPF Holdtime, SPF Execution failure indication, SPF delay, SPF Holdtime, SPF Execution
Time, Tree Build Time, and Hardware Update Time. Time, Tree Build Time, and Hardware Update Time.
IGP Data Plane Route Convergence
4.3 Convergence Due to IGP Adjacency Failure 4.3 Convergence Due to IGP Adjacency Failure
Objective Objective
To obtain the IGP Route Convergence due to a Local IGP Adjacency To obtain the IGP Route Convergence due to a Local IGP Adjacency
failure event. failure event.
Procedure Procedure
1. Advertise matching IGP routes from Tester to DUT on 1. Advertise matching IGP routes from Tester to DUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [2] using the topology shown in Figure 1. Set the cost of
the routes so that the Preferred Egress Interface is the the routes so that the Preferred Egress Interface is the
preferred next-hop. preferred next-hop.
2. Send traffic at maximum forwarding rate to destinations 2. Send offered load at measured Throughput with fixed packet size
matching all IGP routes from Tester to DUT on Ingress to destinations matching all IGP routes from Tester to DUT on
Interface [2]. Ingress Interface [2].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Remove IGP adjacency from Tester's Neighbor Interface [2] 4. Remove IGP adjacency from Tester's Neighbor Interface [2]
connected to Preferred Egress Interface. connected to Preferred Egress Interface.
5. Measure Rate-Derived Convergence Time [2] as DUT detects the 5. Measure Rate-Derived Convergence Time [2] as DUT detects the
IGP session failure event and converges all IGP routes and IGP session failure event and converges all IGP routes and
traffic over the Next-Best Egress Interface. traffic over the Next-Best Egress Interface.
6. Stop offered load. Wait 30 seconds for queues to drain. 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
7. Restore IGP session on DUT's Preferred Egress Interface. 7. Restore IGP session on DUT's Preferred Egress Interface.
8. Measure Restoration Convergence Time [2] as DUT detects the 8. Measure Restoration Convergence Time [2] as DUT detects the
skipping to change at page 9, line 56 skipping to change at page 10, line 52
Objective Objective
To obtain the IGP Route Convergence due to Route Withdrawal. To obtain the IGP Route Convergence due to Route Withdrawal.
Procedure Procedure
1. Advertise matching IGP routes from Tester to DUT on 1. Advertise matching IGP routes from Tester to DUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [2] using the topology shown in Figure 1. Set the cost of
the routes so that the Preferred Egress Interface is the the routes so that the Preferred Egress Interface is the
preferred next-hop. preferred next-hop.
2. Send traffic at maximum forwarding rate to destinations 2. Send offered load at measured Throughput with fixed packet size
matching all IGP routes from Tester to DUT on Ingress to destinations matching all IGP routes from Tester to DUT on
Interface [2]. Ingress Interface [2].
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Tester withdraws all IGP routes from DUT's Local Interface 4. Tester withdraws all IGP routes from DUT's Local Interface
on Preferred Egress Interface. on Preferred Egress Interface.
5. Measure Rate-Derived Convergence Time [2] as DUT detects the
Layer 2 session down event and converges all IGP routes and
traffic over the Next-Best Egress Interface.
6. Stop offered load. Wait 30 seconds for queues to drain. 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
7. Re-advertise IGP routes to DUT's Preferred Egress Interface. 7. Re-advertise IGP routes to DUT's Preferred Egress Interface.
8. Measure Restoration Convergence Time [2] as DUT converges all 8. Measure Restoration Convergence Time [2] as DUT converges all
IGP routes and traffic over the Preferred Egress Interface. IGP routes and traffic over the Preferred Egress Interface.
Results Results
The measured IGP Convergence time is the SPF Processing and FIB The measured IGP Convergence time is the SPF Processing and FIB
Update time as influenced by the SPF delay, SPF Holdtime, Update time as influenced by the SPF delay, SPF Holdtime,
SPF Execution Time, Tree Build Time, and Hardware Update Time. SPF Execution Time, Tree Build Time, and Hardware Update Time.
skipping to change at page 10, line 32 skipping to change at page 11, line 35
Objective Objective
To obtain the IGP Route Convergence due to route cost change. To obtain the IGP Route Convergence due to route cost change.
Procedure Procedure
1. Advertise matching IGP routes from Tester to DUT on 1. Advertise matching IGP routes from Tester to DUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [2] using the topology shown in Figure 1. Set the cost of
the routes so that the Preferred Egress Interface is the the routes so that the Preferred Egress Interface is the
preferred next-hop. preferred next-hop.
2. Send traffic at maximum forwarding rate to destinations 2. Send offered load at measured Throughput with fixed packet size
matching all IGP routes from Tester to DUT on Ingress to destinations matching all IGP routes from Tester to DUT
Interface [2]. on Ingress Interface [2].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Tester increases cost for all IGP routes at DUT's Preferred 4. Tester increases cost for all IGP routes at DUT's Preferred
Egress Interface so that the Next-Best Egress Interface Egress Interface so that the Next-Best Egress Interface
has lower cost and becomes preferred path. has lower cost and becomes preferred path.
5. Measure Rate-Derived Convergence Time [2] as DUT detects the 5. Measure Rate-Derived Convergence Time [2] as DUT detects the
cost change event and converges all IGP routes and traffic cost change event and converges all IGP routes and traffic
over the Next-Best Egress Interface. over the Next-Best Egress Interface.
6. Stop offered load. Wait 30 seconds for queues to drain. 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
7. Re-advertise IGP routes to DUT's Preferred Egress Interface 7. Re-advertise IGP routes to DUT's Preferred Egress Interface
with original lower cost metric. with original lower cost metric.
8. Measure Restoration Convergence Time [2] as DUT converges all 8. Measure Restoration Convergence Time [2] as DUT converges all
IGP routes and traffic over the Preferred Egress Interface. IGP routes and traffic over the Preferred Egress Interface.
Results Results
There should be no measured packet loss for this case. There should be no measured packet loss for this case.
4.6 Convergence Due to ECMP Member Interface Failure IGP Data Plane Route Convergence
4.6 Convergence Due to ECMP Member Interface Failure
Objective Objective
To obtain the IGP Route Convergence due to a local link To obtain the IGP Route Convergence due to a local link
failure event of an ECMP Member. failure event of an ECMP Member.
IGP Data Plane Route Convergence
Procedure Procedure
1. Configure ECMP Set as shown in Figure 3. 1. Configure ECMP Set as shown in Figure 3.
2. Advertise matching IGP routes from Tester to DUT on 2. Advertise matching IGP routes from Tester to DUT on
each ECMP member. each ECMP member.
3. Send traffic at maximum forwarding rate to destinations 3. Send offered load at measured Throughput with fixed packet size
matching all IGP routes from Tester to DUT on Ingress to destinations matching all IGP routes from Tester to DUT on
Interface [2]. Ingress Interface [2].
4. Verify traffic routed over all members of ECMP Set. 4. Verify traffic routed over all members of ECMP Set.
5. Remove SONET on Tester's Neighbor Interface [2] connected to 5. Remove link on Tester's Neighbor Interface [2] connected to
one of the DUT's ECMP member interfaces. one of the DUT's ECMP member interfaces.
6. Measure Rate-Derived Convergence Time [2] as DUT detects the 6. Measure Rate-Derived Convergence Time [2] as DUT detects the
link down event and converges all IGP routes and traffic link down event and converges all IGP routes and traffic
over the other ECMP members. over the other ECMP members.
7. Stop offered load. Wait 30 seconds for queues to drain. 7. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
8. Restore SONET on Tester's Neighbor Interface connected to 8. Restore link on Tester's Neighbor Interface connected to
DUT's ECMP member interface. DUT's ECMP member interface.
9. Measure Restoration Convergence Time [2] as DUT detects the 9. Measure Restoration Convergence Time [2] as DUT detects the
link up event and converges IGP routes and some distribution link up event and converges IGP routes and some distribution
of traffic over the restored ECMP member. of traffic over the restored ECMP member.
Results Results
The measured IGP Convergence time is influenced by the Local The measured IGP Convergence time is influenced by the Local
SONET indication, Tree Build Time, and Hardware Update Time. link failure indication, Tree Build Time, and Hardware Update Time.
4.7 Convergence Due to Parallel Link Interface Failure 4.7 Convergence Due to Parallel Link Interface Failure
Objective Objective
To obtain the IGP Route Convergence due to a local link failure To obtain the IGP Route Convergence due to a local link failure
event for a Member of a Parallel Link. The links can be used for event for a Member of a Parallel Link. The links can be used for
data Load Balancing data Load Balancing
Procedure Procedure
1. Configure Parallel Link as shown in Figure 4. 1. Configure Parallel Link as shown in Figure 4.
2. Advertise matching IGP routes from Tester to DUT on 2. Advertise matching IGP routes from Tester to DUT on
each Parallel Link member. each Parallel Link member.
3. Send traffic at maximum forwarding rate to destinations 3. Send offered load at measured Throughput with fixed packet size
matching all IGP routes from Tester to DUT on Ingress to destinations matching all IGP routes from Tester to DUT on
Interface [2]. Ingress Interface [2].
4. Verify traffic routed over all members of Parallel Link. 4. Verify traffic routed over all members of Parallel Link.
5. Remove SONET on Tester's Neighbor Interface [2] connected to 5. Remove link on Tester's Neighbor Interface [2] connected to
one of the DUT's Parallel Link member interfaces. one of the DUT's Parallel Link member interfaces.
6. Measure Rate-Derived Convergence Time [2] as DUT detects the 6. Measure Rate-Derived Convergence Time [2] as DUT detects the
link down event and converges all IGP routes and traffic over link down event and converges all IGP routes and traffic over
the other Parallel Link members. the other Parallel Link members.
7. Stop offered load. Wait 30 seconds for queues to drain. 7. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
8. Restore SONET on Tester's Neighbor Interface connected to
DUT's Parallel Link member interface.
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
8. Restore link on Tester's Neighbor Interface connected to
DUT's Parallel Link member interface.
9. Measure Restoration Convergence Time [2] as DUT detects the 9. Measure Restoration Convergence Time [2] as DUT detects the
link up event and converges IGP routes and some distribution link up event and converges IGP routes and some distribution
of traffic over the restored Parallel Link member. of traffic over the restored Parallel Link member.
Results Results
The measured IGP Convergence time is influenced by the Local The measured IGP Convergence time is influenced by the Local
SONET indication, Tree Build Time, and Hardware Update Time. link failure indication, Tree Build Time, and Hardware Update Time.
5. Security Considerations 5. Security Considerations
Documents of this type do not directly affect the security of Documents of this type do not directly affect the security of
the Internet or corporate networks as long as benchmarking the Internet or corporate networks as long as benchmarking
is not performed on devices or systems connected to operating is not performed on devices or systems connected to operating
networks. networks.
6. Normative References 6. Normative References
[1] Poretsky, S., "Benchmarking Applicability for IGP [1] Poretsky, S., "Benchmarking Applicability for IGP
Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-05, work Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-06, work
in progress, February 2005. in progress, June 2005.
[2] Poretsky, S., Imhoff, B., "Benchmarking Terminology for IGP [2] Poretsky, S., Imhoff, B., "Benchmarking Terminology for IGP
Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-05, work Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-06, work
in progress, February 2005 in progress, June 2005
[3] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and Dual [3] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and Dual
Environments", RFC 1195, December 1990. Environments", RFC 1195, IETF, December 1990.
[4] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998. [4] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998.
[5] Bradner, S., "Benchmarking Terminology for Network Interconnection
Devices", RFC 1242, IETF, July 1991.
[6] Bradner, S. and McQuaid, J., "Benchmarking Methodology for
Network Interconnect Devices", RFC 2544, IETF, March 1999.
[7] Katz, D. and Ward, D., "Bidirectional Forwarding Detection",
draft-ietf-bfd-base-02.txt, work in progress, IETF,
March 2005.
7. Author's Address 7. Author's Address
Scott Poretsky Scott Poretsky
Quarry Technologies Quarry Technologies
8 New England Executive Park 8 New England Executive Park
Burlington, MA 01803 Burlington, MA 01803
USA USA
Phone: + 1 781 395 5090 Phone: + 1 781 395 5090
EMail: sporetsky@quarrytech.com EMail: sporetsky@quarrytech.com
IGP Data Plane Route Convergence
Brent Imhoff Brent Imhoff
LightCore LightCore
USA USA
EMail: bimhoff@planetspork.com EMail: bimhoff@planetspork.com
IGP Data Plane Route Convergence
Intellectual Property Statement Full Copyright Statement
The IETF takes no position regarding the validity or scope of any Intel- Copyright (C) The Internet Society (2005).
lectual Property Rights or other rights that might be claimed to pertain
to the implementation or use of the technology described in this docu- This document is subject to the rights, licenses and restrictions
ment or the extent to which any license under such rights might or might contained in BCP 78, and except as set forth therein, the authors
not be available; nor does it represent that it has made any independent retain all their rights.
effort to identify any such rights. Information on the procedures with
respect to rights in RFC documents can be found in BCP 78 and BCP 79. This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an attempt assurances of licenses to be made available, or the result of an
made to obtain a general license or permission for the use of such attempt made to obtain a general license or permission for the use of
proprietary rights by implementers or users of this specification can be such proprietary rights by implementers or users of this
obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights copyrights, patents or patent applications, or other proprietary
that may cover technology that may be required to implement this stan- rights that June cover technology that June be required to implement
dard. Please address the information to the IETF at ietf-ipr@ietf.org. this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Disclaimer of Warranty
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR
IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMA-
TION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Acknowledgement
Copyright (C) The Internet Society (2005). This document is subject to Funding for the RFC Editor function is currently provided by the
the rights, licenses and restrictions contained in BCP 78, and except as Internet Society.
set forth therein, the authors retain all their rights.
 End of changes. 

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