draft-ietf-bmwg-igp-dataplane-conv-meth-14.txt   draft-ietf-bmwg-igp-dataplane-conv-meth-15.txt 
Network Working Group Network Working Group S. Poretsky
INTERNET-DRAFT Internet Draft NextPoint Networks
Intended Status: Informational Expires: August 2008
Scott Poretsky Intended Status: Informational Brent Imhoff
Reef Point Systems
Brent Imhoff
Juniper Networks Juniper Networks
November 2007 February 25, 2008
Benchmarking Methodology for Benchmarking Methodology for
Link-State IGP Data Plane Route Convergence Link-State IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-meth-14.txt> <draft-ietf-bmwg-igp-dataplane-conv-meth-15.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 43 skipping to change at page 1, line 40
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 IETF Trust (2007). Copyright (C) The IETF Trust (2008).
ABSTRACT ABSTRACT
This document describes the methodology for benchmarking Interior This document describes the methodology for benchmarking Interior
Gateway Protocol (IGP) Route Convergence. The methodology is to Gateway Protocol (IGP) Route Convergence. The methodology is to
be used for benchmarking IGP convergence time through externally be used for benchmarking IGP convergence time through externally
observable (black box) data plane measurements. The methodology observable (black box) data plane measurements. The methodology
can be applied to any link-state IGP, such as ISIS and OSPF. can be applied to any link-state IGP, such as ISIS and OSPF.
IGP Data Plane Route Convergence Link-State 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........................................5 3.2 Test Considerations........................................5
3.3 Reporting Format...........................................7 3.3 Reporting Format...........................................7
4. Test Cases..................................................7 4. Test Cases..................................................8
4.1 Convergence Due to Link Failure............................8 4.1 Convergence Due to Local Interface Failure.................8
4.1.1 Convergence Due to Local Interface Failure...............8 4.2 Convergence Due to Remote Interface Failure................9
4.1.2 Convergence Due to Neighbor Interface Failure............8 4.3 Convergence Due to Local Administrative Shutdown...........10
4.1.3 Convergence Due to Remote Interface Failure..............9 4.4 Convergence Due to Layer 2 Session Loss....................10
4.2 Convergence Due to Local Administrative Shutdown...........10 4.5 Convergence Due to Loss of IGP Adjacency...................11
4.3 Convergence Due to Layer 2 Session Failure.................11 4.6 Convergence Due to Route Withdrawal........................12
4.4 Convergence Due to IGP Adjacency Failure...................11 4.7 Convergence Due to Cost Change.............................13
4.5 Convergence Due to Route Withdrawal........................12 4.8 Convergence Due to ECMP Member Interface Failure...........13
4.6 Convergence Due to Cost Change.............................13 4.9 Convergence Due to ECMP Member Remote Interface Failure....14
4.7 Convergence Due to ECMP Member Interface Failure...........13 4.10 Convergence Due to Parallel Link Interface Failure........15
4.8 Convergence Due to ECMP Member Remote Interface Failure....14 5. IANA Considerations.........................................16
4.9 Convergence Due to Parallel Link Interface Failure.........15 6. Security Considerations.....................................16
5. IANA Considerations.........................................15 7. Acknowledgements............................................16
6. Security Considerations.....................................15 8. References..................................................16
7. Acknowledgements............................................15 9. Author's Address............................................17
8. Normative References........................................16
9. Author's Address............................................16
1. Introduction 1. Introduction
This document describes the methodology for benchmarking Interior This document describes the methodology for benchmarking Interior
Gateway Protocol (IGP) Route Convergence. The applicability of this Gateway Protocol (IGP) Route Convergence. The applicability of this
testing is described in [Po07a] and the new terminology that it testing is described in [Po07a] and the new terminology that it
introduces is defined in [Po07t]. Service Providers use IGP introduces is defined in [Po07t]. Service Providers use IGP
Convergence time as a key metric of router design and architecture. Convergence time as a key metric of router design and architecture.
Customers of Service Providers observe convergence time by packet Customers of Service Providers observe convergence time by packet
loss, so IGP Route Convergence is considered a Direct Measure of loss, so IGP Route Convergence is considered a Direct Measure of
Quality (DMOQ). The test cases in this document are black-box tests Quality (DMOQ). The test cases in this document are black-box tests
that emulate the network events that cause route convergence, as that emulate the network events that cause route convergence, as
described in [Po07a]. The black-box test designs benchmark the data described in [Po07a]. The black-box test designs benchmark the data
plane and account for all of the factors contributing to convergence plane and account for all of the factors contributing to convergence
time, as discussed in [Po07a]. The methodology (and terminology) for time, as discussed in [Po07a]. The methodology (and terminology) for
benchmarking route convergence can be applied to any link-state IGP benchmarking route convergence can be applied to any link-state IGP
such as ISIS [Ca90] and OSPF [Mo98] and other IGPs such as RIP. such as ISIS [Ca90] and OSPF [Mo98] and others. These methodologies
These methodologies apply to IPv4 and IPv6 traffic and IGPs. apply to IPv4 and IPv6 traffic and 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. document.
IGP Data Plane Route Convergence
This document uses much of the terminology defined in [Po07t]. This document uses much of the terminology defined in [Po07t].
This document uses existing terminology defined in other BMWG This document uses existing terminology defined in other BMWG
work. Examples include, but are not limited to: work. Examples include, but are not limited to:
Link-State IGP Data Plane Route Convergence
Throughput [Ref.[Br91], section 3.17] Throughput [Ref.[Br91], section 3.17]
Device Under Test (DUT) [Ref.[Ma98], section 3.1.1] Device Under Test (DUT) [Ref.[Ma98], section 3.1.1]
System Under Test (SUT) [Ref.[Ma98], section 3.1.2] System Under Test (SUT) [Ref.[Ma98], section 3.1.2]
Out-of-order Packet [Ref.[Po06], section 3.3.2] Out-of-order Packet [Ref.[Po06], section 3.3.2]
Duplicate Packet [Ref.[Po06], section 3.3.3] Duplicate Packet [Ref.[Po06], section 3.3.3]
Packet Loss [Ref.[Po07t], Section 3.5] Packet Loss [Ref.[Po07t], Section 3.5]
This document adopts the definition format in Section 2 of RFC 1242 This document adopts the definition format in Section 2 of RFC 1242
[Br91]. [Br91].
skipping to change at page 3, line 49 skipping to change at page 3, line 45
routers in the SUT must be the same model and identically routers in the SUT must be the same model and identically
configured. configured.
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 time with members of an Equal Cost Multipath (ECMP) Set. These
times are measured by observing packet loss in the data plane at times are measured by observing packet loss in the data plane at
the Tester. In this topology, the DUT is configured with each the Tester. In this topology, the DUT is configured with each
Egress interface as a member of an ECMP set and the Tester emulates Egress interface as a member of an ECMP set and the Tester emulates
multiple next-hop routers (emulates one router for each member). multiple next-hop routers (emulates one router for each member).
Figure 4 shows the test topology to measure IGP Route Convergence
time with members of a Parallel Link. These times are measured by
observing packet loss in the data plane at the Tester. In this
topology, the DUT is configured with each Egress interface as a
member of a Parallel Link and the Tester emulates the single
next-hop router.
IGP Data Plane Route Convergence
--------- Ingress Interface --------- --------- Ingress Interface ---------
| |<--------------------------------| | | |<--------------------------------| |
| | | | | | | |
| | Preferred Egress Interface | | | | Preferred Egress Interface | |
| DUT |-------------------------------->| Tester| | DUT |-------------------------------->| Tester|
| | | | | | | |
| |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>| | | |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>| |
| | Next-Best Egress Interface | | | | Next-Best Egress Interface | |
--------- --------- --------- ---------
Figure 1. Test Topology 1: IGP Convergence Test Topology Figure 1. Test Topology 1: IGP Convergence Test Topology
for Local Changes for Local Changes
Link-State IGP Data Plane Route Convergence
----- --------- ----- ---------
| | Preferred | | | | Preferred | |
----- |R2 |---------------------->| | ----- |R2 |---------------------->| |
| |-->| | Egress Interface | | | |-->| | Egress Interface | |
| | ----- | | | | ----- | |
|R1 | |Tester | |R1 | |Tester |
| | ----- | | | | ----- | |
| |-->| | Next-Best | | | |-->| | Next-Best | |
----- |R3 |~~~~~~~~~~~~~~~~~~~~~~>| | ----- |R3 |~~~~~~~~~~~~~~~~~~~~~~>| |
skipping to change at page 5, line 4 skipping to change at page 4, line 38
| DUT |-------------------------------->| Tester| | DUT |-------------------------------->| Tester|
| | . | | | | . | |
| | . | | | | . | |
| | . | | | | . | |
| |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>| | | |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>| |
| | ECMP Set Interface N | | | | ECMP Set Interface N | |
--------- --------- --------- ---------
Figure 3. Test Topology 3: IGP Convergence Test Topology Figure 3. Test Topology 3: IGP Convergence Test Topology
for ECMP Convergence for ECMP Convergence
IGP Data Plane Route Convergence
--------- Ingress Interface --------- --------- Ingress Interface ---------
| |<--------------------------------| | | |<--------------------------------| |
| | | | | | | |
| | Parallel Link Interface 1 | | | | Parallel Link Interface 1 | |
| DUT |-------------------------------->| Tester| | DUT |-------------------------------->| Tester|
| | . | | | | . | |
| | . | | | | . | |
| | . | | | | . | |
| |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>| | | |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>| |
| | Parallel Link Interface N | | | | Parallel Link Interface N | |
--------- --------- --------- ---------
Figure 4. Test Topology 4: IGP Convergence Test Topology Figure 4. Test Topology 4: IGP Convergence Test Topology
for Parallel Link Convergence for Parallel Link Convergence
Link-State IGP Data Plane Route Convergence
Figure 4 shows the test topology to measure IGP Route Convergence
time with members of a Parallel Link. These times are measured by
observing packet loss in the data plane at the Tester. In this
topology, the DUT is configured with each Egress interface as a
member of a Parallel Link and the Tester emulates the single
next-hop router.
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 MAY be used for link-state
OSPF. The Route Convergence test methodology for both is IGPs, such as ISIS or OSPF. The Route Convergence test methodology
identical. The IGP adjacencies are established on the Preferred is 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 Routing Protocol Configuration 3.2.2 Routing Protocol Configuration
The obtained results for IGP Route Convergence may vary if The obtained results for IGP Route Convergence may vary if
other routing protocols are enabled and routes learned via those other routing protocols are enabled and routes learned via those
protocols are installed. IGP convergence times MUST be benchmarked protocols are installed. IGP convergence times MUST be benchmarked
without routes installed from other protocols. without routes installed from other protocols.
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. To obtain results similar to those that would be Convergence. To obtain results similar to those that would be
observed in an operational network, it is reocmmended that the observed in an operational network, it is RECOMMENDED that the
number of installed routes and nodes closely approximates that number of installed routes and nodes closely approximates that
of the network (e.g. thousands of routes with tens of nodes). of the network (e.g. thousands of routes with tens of nodes).
The number of areas (for OSPF) and levels (for ISIS) can impact The number of areas (for OSPF) and levels (for ISIS) can impact
the benchmark results. 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. Benchmarking metrics may be measured at any fixed values for time. Benchmarking metrics may be measured at any fixed values for
these timers. It is RECOMMENDED that the following timers be these timers. It is RECOMMENDED that the following timers be
configured to the minimum values listed: configured to the minimum values listed:
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
IGP Data Plane Route Convergence
3.2.5 Convergence Time Metrics 3.2.5 Interface Types
The Packet Sampling Interval [Po07t] value is the fastest All test cases in this methodology document may be executed with any
measurable convergence time. The RECOMMENDED value for the interface type. All interfaces MUST be the same media and Throughput
Packet Sampling Interval is 10 milliseconds. Rate-Derived Link-State IGP Data Plane Route Convergence
Convergence Time [Po07t] is the preferred benchmark for IGP
Route Convergence. This benchmark must always be reported
when the Packet Sampling Interval is set <= 10 milliseconds
on the test equipment. If the test equipment does not permit
the Packet Sampling Interval to be set as low as 10
milliseconds, then both the Rate-Derived Convergence Time and
Loss-Derived Convergence Time [Po07t] MUST be reported.
3.2.6 Interface Types [Br91][Br99] for each test case. The type of media may dictate which
All test cases in this methodology document may be executed with test cases may be executed. This is because each interface type has
any interface type. All interfaces MUST be the same media and a unique mechanism for detecting link failures and the speed at which
Throughput [Br91][Br99] for each test case. The type of media that mechanism operates will influence the measure results. Media
may dictate which test cases may be executed. This is because and protocols MUST be configured for minimum failure detection delay
each interface type has a unique mechanism for detecting link to minimize the contribution to the measured Convergence time. For
failures and the speed at which that mechanism operates will example, configure SONET with the minimum carrier-loss-delay. All
influence the measure results. Media and protocols MUST be
configured for minimum failure detection delay to minimize the
contribution to the measured Convergence time. For example,
configure SONET with the minimum carrier-loss-delay. All
interfaces SHOULD be configured as point-to-point. interfaces SHOULD be configured as point-to-point.
3.2.7 offered load 3.2.6 Packet Sampling Interval
The offered load MUST be the Throughput of the device as defined The Packet Sampling Interval [Po07t] value is the fastest measurable
in [Br91] and benchmarked in [Br99] at a fixed packet size. Rate-Derived Convergence Time [Po07t]. The RECOMMENDED value for the
Packet size is measured in bytes and includes the IP header and Packet Sampling Interval is 10 milliseconds. Rate-Derived Convergence
payload. The packet size is selectable and MUST be recorded. Time is the preferred benchmark for IGP Route Convergence. This
The Forwarding Rate [Ma98] MUST be measured at the Preferred Egress benchmark must always be reported when the Packet Sampling Interval
Interface and the Next-Best Egress Interface. The duration of is set <= 10 milliseconds on the test equipment. If the test
offered load MUST be greater than the convergence time. The equipment does not permit the Packet Sampling Interval to be set as
destination addresses for the offered load MUST be distributed low as 10 milliseconds, then both the Rate-Derived Convergence Time
such that all routes are matched. This enables Full Convergence and Loss-Derived Convergence Time [Po07t] MUST be reported.
[Po07t] to be observed.
IGP Data Plane Route Convergence 3.2.7 Offered Load
The offered load MUST be the Throughput of the device as defined in
[Br91] and benchmarked in [Br99] at a fixed packet size. At least
one packet per route in the FIB for all routes in the FIB MUST be
offered to the DUT within the Packet Sampling interval. Packet size
is measured in bytes and includes the IP header and payload. The
packet size is selectable and MUST be recorded. The Forwarding
Rate [Ma98] 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 and each route is offered an equal share of the total
Offered Load. This requirement for the Offered Load to be
distributed to match all destinations in the route table creates
separate flows that are offered to the DUT. The capability of the
Tester to measure packet loss for each individual flow (identified
by the destination address matching a route entry) and the scale
for the number of individual flows for which it can measure packet
loss should be considered when benchmarking Route-Specific
Convergence [Po07t].
3.2.8 Selection of Convergence Time Benchmark Metrics
The methodologies in the section 4 test cases MAY be applied to
benchmark Full Convergence and Route-Specific Convergence with
benchmarking metrics First Route Convergence Time, Loss-Derived
Convergence Time, Rate-Derived Convergence Time, Reversion
Convergence Time, and Route-Specific Convergence Times [Po07t].
When benchmarking Full Convergence the Rate-Derived Convergence
Time benchmarking metric SHOULD be measured. When benchmarking
Route-Specific Convergence the ROute-Specific Convergence Time
benchmarking metric SHOULD be measured. The First Route Convergence
Time benchmarking metric MAY be measured when benchmarking either
Full Convergence or Route-Specific Convergence.
Link-State IGP Data Plane Route Convergence
3.3 Reporting Format 3.3 Reporting Format
For each test case, it is recommended that the reporting table below For each test case, it is recommended that the reporting table below
is completed and all time values SHOULD be reported with resolution is completed and all time values SHOULD be reported with resolution
as specified in [Po07t]. as specified in [Po07t].
Parameter Units Parameter Units
--------- ----- --------- -----
IGP (ISIS or OSPF) Test Case test case number
Interface Type (GigE, POS, ATM, etc.)
Test Topology (1, 2, 3, or 4) Test Topology (1, 2, 3, or 4)
IGP (ISIS, OSPF, other)
Interface Type (GigE, POS, ATM, other)
Packet Size offered to DUT bytes Packet Size offered to DUT bytes
Total Packets Offered to DUT number of Packets
Total Packets Routed by DUT number of Packets
IGP Routes advertised to DUT number of IGP routes IGP Routes advertised to DUT number of IGP routes
Nodes in emulated network number of nodes Nodes in emulated network number of nodes
Packet Sampling Interval on Tester milliseconds Packet Sampling Interval on Tester milliseconds
IGP Timer Values configured on DUT IGP Timer Values configured on DUT:
Interface Failure Indication Delay seconds Interface Failure Indication Delay seconds
IGP Hello Timer seconds IGP Hello Timer seconds
IGP Dead-Interval seconds IGP Dead-Interval seconds
LSA Generation Delay seconds LSA Generation Delay seconds
LSA Flood Packet Pacing seconds LSA Flood Packet Pacing seconds
LSA Retransmission Packet Pacing seconds LSA Retransmission Packet Pacing seconds
SPF Delay seconds SPF Delay seconds
Benchmarks Forwarding Metrics
First Prefix Conversion Time seconds Total Packets Offered to DUT number of Packets
Total Packets Routed by DUT number of Packets
Convergence Packet Loss number of Packets
Out-of-Order Packets number of Packets
Duplicate Packets number of Packets
Convergence Benchmarks
Full Convergence
First Route Convergence Time seconds
Rate-Derived Convergence Time seconds Rate-Derived Convergence Time seconds
Loss-Derived Convergence Time seconds Loss-Derived Convergence Time seconds
Route-Specific Convergence
Number of Routes Measured number of flows
Route-Specific Convergence Time[n] array of seconds
Minimum R-S Convergence Time seconds
Maximum R-S Convergence Time seconds
Median R-S Convergence Time seconds
Average R-S Convergence Time seconds
Reversion
Reversion Convergence Time seconds Reversion Convergence Time seconds
First Route Convergence Time seconds
Route-Specific Convergence
Number of Routes Measured number of flows
Route-Specific Convergence Time[n] array of seconds
Minimum R-S Convergence Time seconds
Maximum R-S Convergence Time seconds
Median R-S Convergence Time seconds
Average R-S Convergence Time seconds
Link-State IGP Data Plane Route Convergence
4. Test Cases 4. Test Cases
The test cases follow a generic procedure tailored to the specific It is RECOMMENDED that all applicable test cases be executed for
DUT configuration and Convergence Event. This generic procedure is best characterization of the DUT. The test cases follow a generic
as follows: procedure tailored to the specific DUT configuration and Convergence
Event[Po07t]. This generic procedure is as follows:
1. Establish DUT configuration and install routes. 1. Establish DUT configuration and install routes.
2. Send offered load with traffic traversing Preferred Egress 2. Send offered load with traffic traversing Preferred Egress
Interface [Po07t]. Interface [Po07t].
3. Introduce Convergence Event to force traffic to Next-Best 3. Introduce Convergence Event to force traffic to Next-Best
Egress Interface [Po07t]. Egress Interface [Po07t].
4. Measure First Prefix Convergence Time. 4. Measure First Route Convergence Time.
4. Measure Rate-Derived Convergence Time. 5. Measure Loss-Derived Convergence Time, Rate-Derived
5. Recover from Convergence Event. Convergence Time, and optionally the Route-Specific
6. Measure Reversion Convergence Time. Convergence Times.
6. Wait the Sustained Convergence Validation Time to ensure there
no residual packet loss.
7. Recover from Convergence Event.
8. Measure Reversion Convergence Time, and optionally the First
Route Convergence Time and Route-Specific Convergence Times.
IGP Data Plane Route Convergence 4.1 Convergence Due to Local Interface Failure
4.1 Convergence Due to Link Failure
4.1.1 Convergence Due to Local Interface Failure
Objective Objective
To obtain the IGP Route Convergence due to a local link failure event To obtain the IGP Route Convergence due to a local link 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
Preferred Egress Interface [Po07t] and Next-Best Egress Interface Egress Interface [Po07t] and Next-Best Egress Interface [Po07t]
[Po07t] using the topology shown in Figure 1. Set the cost of using the topology shown in Figure 1. Set the cost of the routes
the routes so that the Preferred Egress Interface is the 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 [Po07t]. DUT on Ingress Interface [Po07t].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic is routed over Preferred Egress Interface.
4. Remove link on DUT's Preferred Egress Interface. 4. Remove link on DUT's Preferred Egress Interface.
5. Measure First Prefix Convergence Time [Po07t] as DUT detects the 5. Measure First Route Convergence Time [Po07t] as DUT detects the
link down event and begins to converge IGP routes and traffic link down event and begins to converge IGP routes and traffic
over the Next-Best Egress Interface. over the Next-Best Egress Interface.
6. Measure Rate-Derived Convergence Time [Po07t] 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 Next-Best Egress Interface. the Next-Best Egress Interface. Optionally, Route-Specific
Convergence Times [Po07t] MAY be measured.
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 DUT's Preferred Egress Interface. 8. Restore link on DUT's Preferred Egress Interface.
9. Measure Reversion Convergence Time [Po07t] as DUT detects the 9. Measure Reversion Convergence Time [Po07t], and optionally
link up event and converges all IGP routes and traffic back measure First Route Convergence Time [Po07t] and Route-Specific
to the Preferred Egress Interface. Convergence Times [Po07t], as DUT detects the link up event and
converges all IGP routes and traffic back to the Preferred
Results Egress Interface.
The measured IGP Convergence time is influenced by the Local
link failure indication, SPF delay, SPF Hold time, SPF Execution
Time, Tree Build Time, and Hardware Update Time [Po07a].
4.1.2 Convergence Due to Neighbor Interface Failure
Objective
To obtain the IGP Route Convergence due to a local link
failure event at the Tester's Neighbor Interface.
Procedure
1. Advertise matching IGP routes from Tester to DUT on
Preferred Egress Interface [Po07t] and Next-Best Egress Interface
[Po07t] using the topology shown in Figure 1. Set the cost of
the routes so that the Preferred Egress Interface is the
preferred next-hop.
2. Send offered load at measured Throughput with fixed packet
size to destinations matching all IGP routes from Tester to
DUT on Ingress Interface [Po07t].
IGP Data Plane Route Convergence
3. Verify traffic routed over Preferred Egress Interface. Link-State IGP Data Plane Route Convergence
4. Remove link on Tester's Neighbor Interface [Po07t] connected to
DUT's Preferred Egress Interface.
5. Measure First Prefix Convergence Time [Po07t] as DUT detects the
link down event and begins to converge IGP routes and traffic
over the Next-Best Egress Interface.
6. Measure Rate-Derived Convergence Time [Po07t] as DUT detects the
link down event and converges all IGP routes and traffic over
the Next-Best Egress Interface.
7. Stop offered load. Wait 30 seconds for queues to drain.
Restart offered load.
8. Restore link on Tester's Neighbor Interface connected to
DUT's Preferred Egress Interface.
9. Measure Reversion Convergence Time [Po07t] as DUT detects the
link up event and converges all IGP routes and traffic back
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 Hold time, SPF Execution link failure indication, SPF delay, SPF Hold time, SPF Execution
Time, Tree Build Time, and Hardware Update Time [Po07a]. Time, Tree Build Time, and Hardware Update Time [Po07a].
4.1.3 Convergence Due to Remote Interface Failure 4.2 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 [Po07t] and Next-Best Egress Preferred Egress Interface [Po07t] and Next-Best Egress
Interface [Po07t] using the topology shown in Figure 2. Interface [Po07t] using the topology shown in Figure 2.
Set the cost of the routes so that the Preferred Egress Set the cost of the routes so that 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
SUT on Ingress Interface [Po07t]. SUT 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 [Po07t] 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 First Prefix Convergence Time [Po07t] as SUT detects the 5. Measure First Route Convergence Time [Po07t] as SUT detects the
link down event and begins to converge IGP routes and traffic link down event and begins to converge IGP routes and traffic
over the Next-Best Egress Interface. over the Next-Best Egress Interface.
6. Measure Rate-Derived Convergence Time [Po07t] as SUT detects 6. 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. Optionally, Route-Specific
Convergence Times [Po07t] MAY be measured.
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 Preferred Egress Interface. DUT's Preferred Egress Interface.
9. Measure Reversion Convergence Time [Po07t] as DUT detects the 9. Measure Reversion Convergence Time [Po07t], and optionally
link up event and converges all IGP routes and traffic back measure First Route Convergence Time [Po07t] and Route-Specific
to the Preferred Egress Interface. Convergence Times [Po07t], as DUT detects the link up event and
converges all IGP routes and traffic back to the Preferred Egress
IGP Data Plane Route Convergence Interface.
Results Results
The measured IGP Convergence time is influenced by the link failure The measured IGP Convergence time is influenced by the link failure
indication, LSA/LSP Flood Packet Pacing, LSA/LSP Retransmission indication, LSA/LSP Flood Packet Pacing, LSA/LSP Retransmission
Packet Pacing, LSA/LSP Generation time, SPF delay, SPF Hold time, Packet Pacing, LSA/LSP Generation time, SPF delay, SPF Hold time,
SPF Execution Time, Tree Build Time, and Hardware Update Time SPF Execution Time, Tree Build Time, and Hardware Update Time
[Po07a]. This test case may produce Stale Forwarding [Po07t] due to [Po07a]. This test case may produce Stale Forwarding [Po07t] due to
microloops which may increase the Rate-Derived Convergence Time. microloops which may increase the measured convergence times.
4.2 Convergence Due to Local Adminstrative Shutdown Link-State IGP Data Plane Route Convergence
4.3 Convergence Due to Local Adminstrative Shutdown
Objective Objective
To obtain the IGP Route Convergence due to a local link failure event To obtain the IGP Route Convergence due to a administrative shutdown
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 [Po07t] and Next-Best Egress Interface Preferred Egress Interface [Po07t] and Next-Best Egress Interface
[Po07t] 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 [Po07t]. DUT on Ingress Interface [Po07t].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic is routed over Preferred Egress Interface.
4. Perform adminstrative shutdown on the DUT's Preferred Egress 4. Perform adminstrative shutdown on the DUT's Preferred Egress
Interface. Interface.
5. Measure First Prefix Convergence Time [Po07t] as DUT detects the 5. Measure First Route Convergence Time [Po07t] as DUT detects the
link down event and begins to converge IGP routes and traffic link down event and begins to converge IGP routes and traffic
over the Next-Best Egress Interface. over the Next-Best Egress Interface.
6. Measure Rate-Derived Convergence Time [Po07t] as DUT converges 6. Measure Rate-Derived Convergence Time [Po07t] as DUT converges
all IGP routes and traffic over the Next-Best Egress Interface. all IGP routes and traffic over the Next-Best Egress Interface.
Optionally, Route-Specific Convergence Times [Po07t] MAY be
measured.
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 Preferred Egress Interface by administratively enabling 8. Restore Preferred Egress Interface by administratively enabling
the interface. the interface.
9. Measure Reversion Convergence Time [Po07t] as DUT converges all 9. Measure Reversion Convergence Time [Po07t], and optionally
IGP routes and traffic back to the Preferred Egress Interface. measure First Route Convergence Time [Po07t] and Route-Specific
Convergence Times [Po07t], as DUT detects the link up event and
converges all IGP routes and traffic back to the Preferred
Egress Interface.
Results Results
The measured IGP Convergence time is influenced by SPF delay, The measured IGP Convergence time is influenced by SPF delay,
SPF Hold time, SPF Execution Time, Tree Build Time, and Hardware SPF Hold time, SPF Execution Time, Tree Build Time, and Hardware
Update Time [Po07a]. Update Time [Po07a].
IGP Data Plane Route Convergence 4.4 Convergence Due to Layer 2 Session Loss
4.3 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, such as PPP session loss. session loss.
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 [Po07t] and Next-Best Egress Interface Preferred Egress Interface [Po07t] and Next-Best Egress Interface
[Po07t] 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 [Po07t]. DUT on Ingress Interface [Po07t].
3. Verify traffic routed over Preferred Egress Interface.
4. Remove Layer 2 session from Tester's Neighbor Interface [Po07t] Link-State IGP Data Plane Route Convergence
connected to Preferred Egress Interface.
5. Measure First Prefix Convergence Time [Po07t] as DUT detects the 3. Verify traffic is routed over Preferred Egress Interface.
link down event and begins to converge IGP routes and traffic 4. Tester removes Layer 2 session from DUT's Preferred Egress
over the Next-Best Egress Interface. Interface [Po07t]. It is RECOMMENDED that this be achieved with
messaging, but the method MAY vary with the Layer 2 protocol.
5. Measure First Route Convergence Time [Po07t] as DUT detects the
Layer 2 session down event and begins to converge IGP routes and
traffic over the Next-Best Egress Interface.
6. Measure Rate-Derived Convergence Time [Po07t] as DUT detects the 6. 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. Optionally,
Route-Specific Convergence Times [Po07t] MAY be measured.
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 Layer 2 session on DUT's Preferred Egress Interface. 8. Restore Layer 2 session on DUT's Preferred Egress Interface.
9. Measure Reversion Convergence Time [Po07t] as DUT detects the 9. Measure Reversion Convergence Time [Po07t], and optionally
session up event and converges all IGP routes and traffic measure First Route Convergence Time [Po07t] and Route-Specific
over the Preferred Egress Interface. Convergence Times [Po07t], as DUT detects the session up event
and converges all IGP routes and traffic 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 Hold time, SPF Execution failure indication, SPF delay, SPF Hold time, SPF Execution
Time, Tree Build Time, and Hardware Update Time [Po07a]. Time, Tree Build Time, and Hardware Update Time [Po07a].
4.4 Convergence Due to IGP Adjacency Failure 4.5 Convergence Due to Loss of IGP Adjacency
Objective Objective
To obtain the IGP Route Convergence due to a Local IGP Adjacency To obtain the IGP Route Convergence due to loss of the IGP
failure event. Adjacency.
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 [Po07t] and Next-Best Egress Interface Preferred Egress Interface [Po07t] and Next-Best Egress Interface
[Po07t] 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 [Po07t]. DUT on Ingress Interface [Po07t].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic is routed over Preferred Egress Interface.
IGP Data Plane Route Convergence
4. Remove IGP adjacency from Tester's Neighbor Interface [Po07t] 4. Remove IGP adjacency from Tester's Neighbor Interface [Po07t]
connected to Preferred Egress Interface. connected to Preferred Egress Interface. The Layer 2 session
5. Measure First Prefix Convergence Time [Po07t] as DUT detects the MUST be maintained.
link down event and begins to converge IGP routes and traffic 5. Measure First Route Convergence Time [Po07t] as DUT detects the
over the Next-Best Egress Interface. loss of IGP adjacency and begins to converge IGP routes and
traffic over the Next-Best Egress Interface.
6. Measure Rate-Derived Convergence Time [Po07t] as DUT detects the 6. 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. Optionally,
Route-Specific Convergence Times [Po07t] MAY be measured.
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 IGP session on DUT's Preferred Egress Interface. 8. Restore IGP session on DUT's Preferred Egress Interface.
9. Measure Reversion Convergence Time [Po07t] as DUT detects the
session up event and converges all IGP routes and traffic Link-State IGP Data Plane Route Convergence
over the Preferred Egress Interface.
9. Measure Reversion Convergence Time [Po07t], and optionally
measure First Route Convergence Time [Po07t] and Route-Specific
Convergence Times [Po07t], as DUT detects the session recovery
event and converges all IGP routes and traffic 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 Hold time, SPF Interval, IGP Dead Interval, SPF delay, SPF Hold time, SPF
Execution Time, Tree Build Time, and Hardware Update Time [Po07a]. Execution Time, Tree Build Time, and Hardware Update Time [Po07a].
4.5 Convergence Due to Route Withdrawal 4.6 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 Preferred 1. Advertise matching IGP routes from Tester to DUT on Preferred
Egress Interface [Po07t] and Next-Best Egress Interface [Po07t] Egress Interface [Po07t] and Next-Best Egress Interface [Po07t]
using the topology shown in Figure 1. Set the cost of the routes using the topology shown in Figure 1. Set the cost of the routes
so that the Preferred Egress Interface is the preferred next-hop. so that the Preferred Egress Interface is the preferred next-hop.
It is RECOMMENDED that the IGP routes be IGP external routes
for which the Tester would be emulating a preferred and a
next-best Autonomous System Border Router (ASBR).
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 [Po07t]. DUT on Ingress Interface [Po07t].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic is 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. The Tester records the time it
5. Measure Rate-Derived Convergence Time [Po07t] as DUT withdraws sends the withdrawal message(s). This MAY be achieved with
inclusion of a timestamp in the traffic payload.
5. Measure First Route Convergence Time [Po07t] as DUT detects the
route withdrawal event and begins to converge IGP routes and
traffic over the Next-Best Egress Interface. This is measured
from the time that the Tester sent the withdrawal message(s).
6. 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. Optionally, Route-Specific
6. Measure First Prefix Convergence Time [Po07t] as DUT detects the Convergence Times [Po07t] MAY be measured.
link down event and begins to converge IGP routes and traffic
over the Next-Best Egress Interface.
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. Re-advertise IGP routes to DUT's Preferred Egress Interface. 8. Re-advertise IGP routes to DUT's Preferred Egress Interface.
9. Measure Reversion Convergence Time [Po07t] as DUT converges all 9. Measure Reversion Convergence Time [Po07t], and optionally
IGP routes and traffic over the Preferred Egress Interface. measure First Route Convergence Time [Po07t] and Route-Specific
Convergence Times [Po07t], as DUT converges all 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 Hold time, SPF Update time as influenced by the SPF or route calculation delay,
Execution Time, Tree Build Time, and Hardware Update Time [Po07a]. Hold time, Execution Time, and Hardware Update Time [Po07a].
IGP Data Plane Route Convergence Link-State IGP Data Plane Route Convergence
4.6 Convergence Due to Cost Change 4.7 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 Preferred 1. Advertise matching IGP routes from Tester to DUT on Preferred
Egress Interface [Po07t] and Next-Best Egress Interface [Po07t] Egress Interface [Po07t] and Next-Best Egress Interface [Po07t]
using the topology shown in Figure 1. Set the cost of the routes using the topology shown in Figure 1. Set the cost of the routes
so that the Preferred Egress Interface is the preferred next-hop. so that the Preferred Egress 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 [Po07t]. DUT on Ingress Interface [Po07t].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic is 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 First Prefix Convergence Time [Po07t] as DUT detects the 5. Measure First Route Convergence Time [Po07t] as DUT detects the
link down event and begins to converge IGP routes and traffic cost change event and begins to converge IGP routes and traffic
over the Next-Best Egress Interface. over the Next-Best Egress Interface.
6. Measure Rate-Derived Convergence Time [Po07t] as DUT detects the 6. 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. Optionally, Route-Specific
Convergence Times [Po07t] MAY be measured.
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. Re-advertise IGP routes to DUT's Preferred Egress Interface 8. Re-advertise IGP routes to DUT's Preferred Egress Interface
with original lower cost metric. with original lower cost metric.
9. Measure Reversion Convergence Time [Po07t] as DUT converges all 9. Measure Reversion Convergence Time [Po07t], and optionally
IGP routes and traffic over the Preferred Egress Interface. measure First Route Convergence Time [Po07t] and Route-Specific
Convergence Times [Po07t], as DUT converges all 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.7 Convergence Due to ECMP Member Interface Failure 4.8 Convergence Due to ECMP Member Interface Failure
Objective Objective
To obtain the IGP Route Convergence due to a local link failure event To obtain the IGP Route Convergence due to a local link failure event
of an ECMP Member. of an ECMP Member.
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 each ECMP 2. Advertise matching IGP routes from Tester to DUT on each ECMP
member. member.
3. Send offered load at measured Throughput with fixed packet size to 3. Send offered load at measured Throughput with fixed packet size to
destinations matching all IGP routes from Tester to DUT on Ingress destinations matching all IGP routes from Tester to DUT on Ingress
Interface [Po07t]. Interface [Po07t].
4. Verify traffic routed over all members of ECMP Set. 4. Verify traffic is routed over all members of ECMP Set.
5. Remove link on Tester's Neighbor Interface [Po07t] 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 First Prefix Convergence Time [Po07t] as DUT detects the
link down event and begins to converge IGP routes and traffic
over the Next-Best Egress Interface.
IGP Data Plane Route Convergence Link-State IGP Data Plane Route Convergence
7. Measure Rate-Derived Convergence Time [Po07t] as DUT detects the 6. Measure First Route Convergence Time [Po07t] as DUT detects the
link down event and converges all IGP routes and traffic link down event and begins to converge IGP routes and traffic
over the other ECMP members.
7. Measure Rate-Derived Convergence Time [Po07t] as DUT detects
the link down event and converges all IGP routes and traffic
over the other ECMP members. At the same time measure over the other ECMP members. At the same time measure
Out-of-Order Packets [Po06] and Duplicate Packets [Po06]. Out-of-Order Packets [Po06] and Duplicate Packets [Po06].
Optionally, Route-Specific Convergence Times [Po07t] MAY be
measured.
8. Stop offered load. Wait 30 seconds for queues to drain. 8. Stop offered load. Wait 30 seconds for queues to drain.
Restart offered load. Restart offered load.
9. Restore link on Tester's Neighbor Interface connected to 9. Restore link on Tester's Neighbor Interface connected to
DUT's ECMP member interface. DUT's ECMP member interface.
10. Measure Reversion Convergence Time [Po07t] as DUT detects the 10. Measure Reversion Convergence Time [Po07t], and optionally
link up event and converges IGP routes and some distribution measure First Route Convergence Time [Po07t] and Route-Specific
of traffic over the restored ECMP member. Convergence Times [Po07t], as DUT detects the link up event and
converges IGP routes and some distribution 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
[Po07a]. [Po07a].
4.8 Convergence Due to ECMP Member Remote Interface Failure 4.9 Convergence Due to ECMP Member 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 for an ECMP Member. failure event for an ECMP Member.
Procedure Procedure
1. Configure ECMP Set as shown in Figure 2 in which the links 1. Configure ECMP Set as shown in Figure 2 in which the links
from R1 to R2 and R1 to R3 are members of an ECMP Set. from R1 to R2 and R1 to R3 are members of an ECMP Set.
2. Advertise matching IGP routes from Tester to SUT to balance 2. Advertise matching IGP routes from Tester to SUT to balance
traffic to each ECMP member. traffic to 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
SUT on Ingress Interface [Po07t]. SUT on Ingress Interface [Po07t].
4. Verify traffic routed over all members of ECMP Set. 4. Verify traffic is routed over all members of ECMP Set.
5. Remove link on Tester's Neighbor Interface to R2 or R3. 5. Remove link on Tester's Neighbor Interface to R2 or R3.
6. Measure First Prefix Convergence Time [Po07t] as SUT detects 6. Measure First Route Convergence Time [Po07t] as SUT detects
the link down event and begins to converge IGP routes and the link down event and begins to converge IGP routes and
traffic over the Next-Best Egress Interface. traffic over the other ECMP members.
7. Measure Rate-Derived Convergence Time [Po07t] as SUT detects 7. 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 other ECMP members. At the same time measure over the other ECMP members. At the same time measure
Out-of-Order Packets [Po06] and Duplicate Packets [Po06]. Out-of-Order Packets [Po06] and Duplicate Packets [Po06].
Optionally, Route-Specific Convergence Times [Po07t] MAY be
measured.
8. Stop offered load. Wait 30 seconds for queues to drain. 8. Stop offered load. Wait 30 seconds for queues to drain.
Restart offered load. Restart offered load.
9. Restore link on Tester's Neighbor Interface to R2 or R3. 9. Restore link on Tester's Neighbor Interface to R2 or R3.
10. Measure Reversion Convergence Time [Po07t] as SUT detects the
link up event and converges IGP routes and some distribution Link-State IGP Data Plane Route Convergence
of traffic over the restored ECMP member.
10. Measure Reversion Convergence Time [Po07t], and optionally
measure First Route Convergence Time [Po07t] and
Route-Specific Convergence Times [Po07t], as SUT detects
the link up event and converges IGP routes and some
distribution 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
[Po07a]. [Po07a].
IGP Data Plane Route Convergence 4.10 Convergence Due to Parallel Link Interface Failure
4.9 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 [Po07t]. DUT on Ingress Interface [Po07t].
4. Verify traffic routed over all members of Parallel Link. 4. Verify traffic is routed over all members of Parallel Link.
5. Remove link on Tester's Neighbor Interface [Po07t] 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 First Prefix Convergence Time [Po07t] as DUT detects the 6. Measure First Route Convergence Time [Po07t] as DUT detects the
link down event and begins to converge IGP routes and traffic link down event and begins to converge IGP routes and traffic
over the Next-Best Egress Interface. over the other Parallel Link members.
7. Measure Rate-Derived Convergence Time [Po07t] as DUT detects the 7. 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. At the same time measure the other Parallel Link members. At the same time measure
Out-of-Order Packets [Po06] and Duplicate Packets [Po06]. Out-of-Order Packets [Po06] and Duplicate Packets [Po06].
Optionally, Route-Specific Convergence Times [Po07t] MAY be
measured.
8. Stop offered load. Wait 30 seconds for queues to drain. 8. Stop offered load. Wait 30 seconds for queues to drain.
Restart offered load. Restart offered load.
9. Restore link on Tester's Neighbor Interface connected to 9. Restore link on Tester's Neighbor Interface connected to
DUT's Parallel Link member interface. DUT's Parallel Link member interface.
10. Measure Reversion Convergence Time [Po07t] as DUT detects the 10. Measure Reversion Convergence Time [Po07t], and optionally
link up event and converges IGP routes and some distribution measure First Route Convergence Time [Po07t] and
of traffic over the restored Parallel Link member. Route-Specific Convergence Times [Po07t], as DUT
detects the link up event and converges IGP routes and some
distribution 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 [Po07a]. Time [Po07a].
Link-State IGP Data Plane Route Convergence
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, Ron Bonica, David Ward, Thanks to Sue Hares, Al Morton, Kevin Dubray, Ron Bonica, David Ward,
and the BMWG for their contributions to this work. Kris Michielsen and the BMWG for their contributions to this work.
IGP Data Plane Route Convergence
8. References 8. References
8.1 Normative References 8.1 Normative References
[Br91] Bradner, S., "Benchmarking Terminology for Network [Br91] Bradner, S., "Benchmarking Terminology for Network
Interconnection Devices", RFC 1242, IETF, March 1991. Interconnection Devices", RFC 1242, IETF, March 1991.
[Br97] Bradner, S., "Key words for use in RFCs to Indicate [Br97] Bradner, S., "Key words for use in RFCs to Indicate
[Br99] Bradner, S. and McQuaid, J., "Benchmarking Methodology for [Br99] Bradner, S. and McQuaid, J., "Benchmarking Methodology for
Network Interconnect Devices", RFC 2544, IETF, March 1999. Network Interconnect Devices", RFC 2544, IETF, March 1999.
skipping to change at page 16, line 30 skipping to change at page 16, line 44
[Ma98] Mandeville, R., "Benchmarking Terminology for LAN [Ma98] Mandeville, R., "Benchmarking Terminology for LAN
Switching Devices", RFC 2285, February 1998. Switching Devices", RFC 2285, February 1998.
[Mo98] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998. [Mo98] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998.
[Po06] Poretsky, S., et al., "Terminology for Benchmarking [Po06] Poretsky, S., et al., "Terminology for Benchmarking
Network-layer Traffic Control Mechanisms", RFC 4689, Network-layer Traffic Control Mechanisms", RFC 4689,
November 2006. November 2006.
[Po07a] Poretsky, S., "Considerations for Benchmarking Link-State [Po07a] Poretsky, S., "Considerations for Benchmarking Link-State
IGP Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-14, IGP Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-15,
work in progress, November 2007. work in progress, February 2008.
[Po07t] Poretsky, S., Imhoff, B., "Benchmarking Terminology for [Po07t] Poretsky, S., Imhoff, B., "Benchmarking Terminology for
Link-State IGP Convergence", Link-State IGP Convergence",
draft-ietf-bmwg-igp-dataplane-conv-term-14, work in draft-ietf-bmwg-igp-dataplane-conv-term-15, work in
progress, November 2007. progress, February 2008.
8.2 Informative References 8.2 Informative References
None None
Link-State IGP Data Plane Route Convergence
9. Author's Address 9. Author's Address
Scott Poretsky Scott Poretsky
Reef Point Systems NextPoint Networks
3 Federal Street 3 Federal Street
Billerica, MA 01821 Billerica, MA 01821
USA USA
Phone: + 1 508 439 9008 Phone: + 1 508 439 9008
EMail: sporetsky@reefpoint.com EMail: sporetsky@nextpointnetworks.com
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
IGP Data Plane Route Convergence
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
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 This document and the information contained herein are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
skipping to change at page 17, line 41 skipping to change at page 18, line 5
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. 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 assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be 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.
Link-State IGP Data Plane Route Convergence
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 copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 101 change blocks. 
250 lines changed or deleted 302 lines changed or added

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