draft-ietf-bmwg-igp-dataplane-conv-meth-11.txt   draft-ietf-bmwg-igp-dataplane-conv-meth-12.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: November 2006 Expires in: August 2007
Intended Status: Informational
Scott Poretsky Scott Poretsky
Reef Point Systems Reef Point Systems
Brent Imhoff Brent Imhoff
Juniper Networks Juniper Networks
February 2007
Benchmarking Methodology for Benchmarking Methodology for
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-meth-11.txt> <draft-ietf-bmwg-igp-dataplane-conv-meth-12.txt>
Intellectual Property Rights (IPR) statement: Intellectual Property Rights (IPR) statement:
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Status of this Memo Status of this Memo
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 40 skipping to change at page 1, line 44
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "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.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
ABSTRACT ABSTRACT
This dpcument describes the methodology for benchmarking IGP This document describes the methodology for benchmarking Interior
Route Convergence as described in Applicability document [1] and Gateway Protocol (IGP) Route Convergence. The methodology is to
Terminology document [2]. The methodology and terminology are be used for benchmarking IGP convergence time through externally
to be used for benchmarking route convergence and can be applied observable (black box) data plane measurements. The methodology
to any link-state IGP such as ISIS [3] and OSPF [4]. The terms can be applied to any link-state IGP, such as ISIS and OSPF.
used in the procedures provided within this document are
defined in [2].
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..................................................7 4. Test Cases..................................................7
4.1 Convergence Due to Link Failure............................7 4.1 Convergence Due to Link Failure............................7
4.1.1 Convergence Due to Local Interface Failure...............7 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..............8 4.1.3 Convergence Due to Remote Interface Failure..............8
4.2 Convergence Due to Layer 2 Session Failure.................9 4.2 Convergence Due to Layer 2 Session Failure.................9
4.3 Convergence Due to IGP Adjacency Failure...................10 4.3 Convergence Due to IGP Adjacency Failure...................10
4.4 Convergence Due to Route Withdrawal........................10 4.4 Convergence Due to Route Withdrawal........................10
4.5 Convergence Due to Cost Change.............................11 4.5 Convergence Due to Cost Change.............................11
4.6 Convergence Due to ECMP Member Interface Failure...........12 4.6 Convergence Due to ECMP Member Interface Failure...........11
4.7 Convergence Due to Parallel Link Interface Failure.........12 4.7 Convergence Due to Parallel Link Interface Failure.........12
5. IANA Considerations.........................................13 5. IANA Considerations.........................................13
6. Security Considerations.....................................13 6. Security Considerations.....................................13
7. Acknowledgements............................................13 7. Acknowledgements............................................13
8. Normative References........................................13 8. Normative References........................................13
9. Author's Address............................................14 9. Author's Address............................................14
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]. [Po07a] and the new terminology that it introduces is defined in
Service Providers use IGP Convergence time as a key metric of [Po07t]. Service Providers use IGP Convergence time as a key metric
router design and architecture. Customers of Service Providers of 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 [Po07a]. The
black-box test designs benchmark the data plane and account for black-box test designs benchmark the data plane and account 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 [Po07a]. 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 [Ca90]
and OSPF [4]. These methodologies apply to IPv4 and IPv6 traffic and OSPF [Mo98]. 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", "MAY", 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. The term Throughput is defined in RFC 2544. document. The term Throughput is defined in RFC 2544 [Br99].
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 to local Convergence Events such as SONET Link Failure, Layer 2
Session Failure, IGP Adjacency Failure, Route Withdrawal, and route Session Failure, IGP Adjacency Failure, Route Withdrawal, and route
cost change. These test cases discussed in section 4 provide route cost 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
skipping to change at page 4, line 55 skipping to change at page 4, line 55
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 may 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 are 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 Convergence because convergence for the entire IGP route table
is measured. To obtain results similar to those that would be is measured. To obtain results similar to those that would be
observed in an operational network, it is recommended that the observed in an operational network, it is recommended that the
number of installed routes closely approximate that for routers number of installed routes closely approximates that for routers
in the network. The number of areas (for OSPF) and levels (for in the network. The number of areas (for OSPF) and levels (for
ISIS) can impact the benchmark results. ISIS) can impact the benchmark results.
3.2.4 Timers 3.2.4 Timers
There are some timers that will impact the measured IGP Convergence There are some timers that will impact the measured IGP Convergence
time. The following timers should be configured to the minimum value time. The following timers should be configured to the minimum value
prior to beginning execution of the test cases: prior to beginning execution of the test cases:
Timer Recommended Value Timer Recommended Value
----- ----------------- ----- -----------------
Link Failure Indication Delay <10milliseconds Link Failure Indication Delay <10milliseconds
IGP Hello Timer 1 second IGP Hello Timer 1 second
IGP Dead-Interval 3 seconds IGP Dead-Interval 3 seconds
LSA Generation Delay 0 LSA Generation Delay 0
LSA Flood Packet Pacing 0 LSA Flood Packet Pacing 0
LSA Retransmission Packet Pacing 0 LSA Retransmission Packet Pacing 0
SPF Delay 0 SPF Delay 0
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 [Po07t] is
100 milliseconds. Rate-Derived Convergence Time [2] is the 100 milliseconds. Rate-Derived Convergence Time [Po07t] 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 [Po07t]
<= 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 [Po07t] must be reported. The Packet Sampling
Interval value MUST be reported as the smallest measurable Interval value MUST be reported as the smallest measurable
convergence time. convergence time.
3.2.6 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 may 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
Throughput [5,6] for each test case. Media and protocols MUST Throughput [Br91][Br99] for each test case. Media and protocols MUST
be configured for minimum failure detection delay to minimize be configured for minimum failure detection delay to minimize
the contribution to the measured Convergence time. For example, the contribution to the measured Convergence time. For example,
configure SONET with minimum carrier-loss-delay or Bi-directional configure SONET with minimum carrier-loss-delay or Bi-directional
Forwarding Detection (BFD). Forwarding Detection (BFD).
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
3.2.7 Offered Load 3.2.7 Offered Load
The offered Load MUST be the Throughput of the device as defined The offered Load MUST be the Throughput of the device as defined
in [5] and benchmarked in [6] at a fixed packet size. in [Br91] and benchmarked in [Br99] at a fixed packet size.
Packet size is measured in bytes and includes the IP header and Packet size is measured in bytes and includes the IP header and
payload. The packet size is selectable and MUST be recorded. payload. The packet size is selectable and MUST be recorded.
The Forwarding Rate [7] MUST be measured at the Preferred Egress The Forwarding Rate [Ma98] MUST be measured at the Preferred Egress
Interface and the Next-Best Egress Interface. The duration of Interface and the Next-Best Egress Interface. The duration of
offered load MUST be greater than the convergence time. The offered load MUST be greater than the convergence time. The
destination addresses for the offered load MUST be distributed destination addresses for the offered load MUST be distributed
such that all routes are matched. This enables Full Convergence such that all routes are matched. This enables Full Convergence
[2] to be observed. [Po07t] 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 is 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 offered to DUT bytes Packet Size offered to DUT bytes
IGP Routes advertised to DUT number of IGP routes IGP Routes advertised to DUT number of IGP routes
Packet Sampling Interval on Tester seconds or milliseconds Packet Sampling Interval on Tester seconds or milliseconds
IGP Timer Values configured on DUT IGP Timer Values configured on DUT
SONET Failure Indication Delay seconds or milliseconds SONET Failure Indication Delay seconds or milliseconds
skipping to change at page 7, line 10 skipping to change at page 7, line 10
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 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
failure event at the DUT's Local Interface. 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 [Po07t] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [Po07t] 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 offered load at measured Throughput with fixed packet 2. Send offered load at measured Throughput with fixed packet
size to destinations matching all IGP routes from Tester to size to destinations matching all IGP routes from Tester to
DUT on Ingress Interface [2]. DUT on Ingress Interface [Po07t].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Remove Preferred Egress link on DUT's Local Interface [2] by 4. Remove Preferred Egress link on DUT's Local Interface [Po07t] by
performing an administrative shutdown of the interface. performing an administrative shutdown of the interface.
5. Measure Rate-Derived Convergence Time [2] as DUT detects the 5. Measure Rate-Derived Convergence Time [Po07t] 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 Preferred Egress link on DUT's Local Interface by 7. Restore Preferred Egress link on DUT's Local Interface by
administratively enabling the interface. administratively enabling the interface.
8. Measure Restoration Convergence Time [2] as DUT detects the 8. Measure Restoration Convergence Time [Po07t] as DUT detects the
link up event and converges all IGP routes and traffic back link up event and converges all IGP routes and traffic back
to the Preferred Egress Interface. to 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
link failure indication, SPF delay, SPF Holdtime, SPF Execution link failure indication, SPF delay, SPF Holdtime, SPF Execution
Time, Tree Build Time, and Hardware Update Time [1]. Time, Tree Build Time, and Hardware Update Time [Po07a].
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 [Po07t] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [Po07t] 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 offered load at measured Throughput with fixed packet 2. Send offered load at measured Throughput with fixed packet
size to destinations matching all IGP routes from Tester to size to destinations matching all IGP routes from Tester to
DUT on Ingress Interface [2]. DUT on Ingress Interface [Po07t].
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. Remove link on Tester's Neighbor Interface [2] connected to 4. Remove link on Tester's Neighbor Interface [Po07t] 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 [Po07t] 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 link 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 [Po07t] as DUT detects the
link up event and converges all IGP routes and traffic back link up event and converges all IGP routes and traffic back
to the Preferred Egress Interface. to 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
link failure indication, SPF delay, SPF Holdtime, SPF Execution link failure indication, SPF delay, SPF Holdtime, SPF Execution
Time, Tree Build Time, and Hardware Update Time [1]. Time, Tree Build Time, and Hardware Update Time [Po07a].
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 [Po07t] and Next-Best Egress Interface
[2] using the topology shown in Figure 2. Set the cost of [Po07t] using the topology shown in Figure 2. 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 offered load at measured Throughput with fixed packet 2. Send offered load at measured Throughput with fixed packet
size to destinations matching all IGP routes from Tester to size to destinations matching all IGP routes from Tester to
DUT on Ingress Interface [2]. DUT on Ingress Interface [Po07t].
3. Verify traffic is routed over Preferred Egress Interface. 3. Verify traffic is routed over Preferred Egress Interface.
4. Remove link on Tester's Neighbor Interface [2] connected to 4. Remove link on Tester's Neighbor Interface [Po07t] 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 [Po07t] 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 link 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 [Po07t] as DUT detects the
link up event and converges all IGP routes and traffic back link up event and converges all IGP routes and traffic back
to the Preferred Egress Interface. to the Preferred Egress Interface.
IGP Data Plane Route Convergence 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
link failure failure indication, LSA/LSP Flood Packet Pacing, link 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 [1]. The additional Build Time, and Hardware Update Time [Po07a]. 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 To obtain the IGP Route Convergence due to a Local Layer 2
Session failure event. Session 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 [Po07t] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [Po07t] 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 offered load at measured Throughput with fixed packet 2. Send offered load at measured Throughput with fixed packet
size to destinations matching all IGP routes from Tester to size to destinations matching all IGP routes from Tester to
DUT on Ingress Interface [2]. DUT on Ingress Interface [Po07t].
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 [Po07t]
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 [Po07t] 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 [Po07t] as DUT detects the
session up event and converges all IGP routes and traffic session up event and converges all IGP routes and traffic
over the Preferred Egress Interface. over the Preferred Egress Interface.
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 [1]. Time, Tree Build Time, and Hardware Update Time [Po07a].
IGP Data Plane Route Convergence 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 [Po07t] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [Po07t] 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 offered load at measured Throughput with fixed packet 2. Send offered load at measured Throughput with fixed packet
size to destinations matching all IGP routes from Tester to size to destinations matching all IGP routes from Tester to
DUT on Ingress Interface [2]. DUT on Ingress Interface [Po07t].
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 [Po07t]
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 [Po07t] 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 [Po07t] as DUT detects the
session up event and converges all IGP routes and traffic session up event and converges all IGP routes and traffic
over the Preferred Egress Interface. over the Preferred Egress Interface.
Results Results
The measured IGP Convergence time is influenced by the IGP Hello The measured IGP Convergence time is influenced by the IGP Hello
Interval, IGP Dead Interval, SPF delay, SPF Holdtime, SPF Interval, IGP Dead Interval, SPF delay, SPF Holdtime, SPF
Execution Time, Tree Build Time, and Hardware Update Time [1]. Execution Time, Tree Build Time, and Hardware Update Time [Po07a].
4.4 Convergence Due to Route Withdrawal 4.4 Convergence Due to Route Withdrawal
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 [Po07t] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [Po07t] 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 offered load at measured Throughput with fixed packet 2. Send offered load at measured Throughput with fixed packet
size to destinations matching all IGP routes from Tester to size to destinations matching all IGP routes from Tester to
DUT on Ingress Interface [2]. DUT on Ingress Interface [Po07t].
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 withdraws
IGP Data Plane Route Convergence
5. Measure Rate-Derived Convergence Time [Po07t] as DUT withdraws
routes and converges all IGP routes and traffic over the routes and converges all IGP routes and traffic over the
Next-Best Egress Interface. 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 [Po07t] 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, SPF Update time as influenced by the SPF delay, SPF Holdtime, SPF
Execution Time, Tree Build Time, and Hardware Update Time [1]. Execution Time, Tree Build Time, and Hardware Update Time [Po07a].
4.5 Convergence Due to Cost Change 4.5 Convergence Due to Cost Change
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 [Po07t] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [Po07t] 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 offered load at measured Throughput with fixed packet 2. Send offered load at measured Throughput with fixed packet
size to destinations matching all IGP routes from Tester to size to destinations matching all IGP routes from Tester to
DUT on Ingress Interface [2]. DUT on Ingress Interface [Po07t].
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 [Po07t] 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 [Po07t] 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 externally observable IGP Route Convergence There should be no externally observable IGP Route Convergence
and no measured packet loss for this case. and no measured packet loss for this case.
IGP Data Plane Route Convergence
4.6 Convergence Due to ECMP Member Interface Failure 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
failure event of an ECMP Member. 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 offered load at measured Throughput with fixed packet 3. Send offered load at measured Throughput with fixed packet
size to destinations matching all IGP routes from Tester to size to destinations matching all IGP routes from Tester to
DUT on Ingress Interface [2]. DUT on Ingress Interface [Po07t].
4. Verify traffic routed over all members of ECMP Set. 4. Verify traffic routed over all members of ECMP Set.
5. Remove link on Tester's Neighbor Interface [2] connected to 5. Remove link on Tester's Neighbor Interface [Po07t] 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 [Po07t] 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 link 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 [Po07t] 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 Local link The measured IGP Convergence time is influenced by Local link
failure indication, Tree Build Time, and Hardware Update Time failure indication, Tree Build Time, and Hardware Update Time
[1]. [Po07a].
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 event for a Member of a Parallel Link. The links can be used
for data Load Balancing for 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 offered load at measured Throughput with fixed packet 3. Send offered load at measured Throughput with fixed packet
size to destinations matching all IGP routes from Tester to size to destinations matching all IGP routes from Tester to
DUT on Ingress Interface [2]. DUT on Ingress Interface [Po07t].
4. Verify traffic routed over all members of Parallel Link. 4. Verify traffic routed over all members of Parallel Link.
5. Remove link on Tester's Neighbor Interface [2] connected to 5. Remove link on Tester's Neighbor Interface [Po07t] 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 [Po07t] 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 link 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 9. Measure Restoration Convergence Time [Po07t] as DUT detects the
DUT's Parallel Link member interface.
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
link failure indication, Tree Build Time, and Hardware Update link failure indication, Tree Build Time, and Hardware Update
Time [1]. Time [Po07a].
5. IANA Considerations 5. IANA Considerations
This document requires no IANA considerations. This document requires no IANA considerations.
6. Security Considerations 6. 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.
7. Acknowledgements 7. Acknowledgements
Thanks to Sue Hares, Al Morton, Kevin Dubray, and participants of Thanks to Sue Hares, Al Morton, Kevin Dubray, and participants of
the BMWG for their contributions to this work. the BMWG for their contributions to this work.
8. References 8. References
8.1 Normative References 8.1 Normative References
[1] Poretsky, S., "Considerations for Benchmarking IGP
Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-11,
work in progress, May 2006.
[2] Poretsky, S., Imhoff, B., "Benchmarking Terminology for IGP [Br91] Bradner, S., "Benchmarking Terminology for Network
Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-11, Interconnection Devices", RFC 1242, IETF, March 1991.
work in progress, May 2006.
[3] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and Dual [Br97] Bradner, S., "Key words for use in RFCs to Indicate
[Br99] Bradner, S. and McQuaid, J., "Benchmarking Methodology for
Network Interconnect Devices", RFC 2544, IETF, March 1999.
[Ca90] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and Dual
Environments", RFC 1195, IETF, December 1990. Environments", RFC 1195, IETF, December 1990.
[4] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998. [Ma98] Mandeville, R., "Benchmarking Terminology for LAN
Switching Devices", RFC 2285, February 1998.
[5] Bradner, S., "Benchmarking Terminology for Network [Mo98] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998.
Interconnection Devices", RFC 1242, IETF, March 1991.
[6] Bradner, S. and McQuaid, J., "Benchmarking Methodology for [Po07a] Poretsky, S., "Considerations for Benchmarking IGP
Network Interconnect Devices", RFC 2544, IETF, March 1999. Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-12,
work in progress, February 2007.
[7] Mandeville, R., "Benchmarking Terminology for LAN [Po07t] Poretsky, S., Imhoff, B., "Benchmarking Terminology for IGP
Switching Devices", RFC 2285, February 1998. Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-12,
work in progress, February 2007.
8.2 Informative References 8.2 Informative References
None None
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
9. Author's Address 9. Author's Address
Scott Poretsky Scott Poretsky
Reef Point Systems Reef Point Systems
8 New England Executive Park 8 New England Executive Park
skipping to change at page 14, line 26 skipping to change at page 14, line 26
Brent Imhoff Brent Imhoff
Juniper Networks Juniper Networks
1194 North Mathilda Ave 1194 North Mathilda Ave
Sunnyvale, CA 94089 Sunnyvale, CA 94089
USA USA
Phone: + 1 314 378 2571 Phone: + 1 314 378 2571
EMail: bimhoff@planetspork.com EMail: bimhoff@planetspork.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights 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 might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
 End of changes. 84 change blocks. 
121 lines changed or deleted 125 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/