draft-ietf-bmwg-igp-dataplane-conv-meth-09.txt   draft-ietf-bmwg-igp-dataplane-conv-meth-10.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: June 2006 Expires in: September 2006
Scott Poretsky Scott Poretsky
Reef Point Systems Reef Point Systems
Brent Imhoff Brent Imhoff
Juniper Networks Juniper Networks
January 2006 March 2006
Benchmarking Methodology for Benchmarking Methodology for
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-meth-09.txt> <draft-ietf-bmwg-igp-dataplane-conv-meth-10.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 2, line 27 skipping to change at page 2, line 27
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...........12
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. Normative References........................................13 7. Acknowledgements............................................13
8. Author's Address............................................14 8. Normative References........................................13
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]. [1] and the new terminology that it introduces is defined in [2].
Service Providers use IGP Convergence time as a key metric of Service Providers use IGP Convergence time as a key metric of
router design and architecture. Customers of Service Providers router design and architecture. Customers of Service Providers
observe convergence time by packet loss, so IGP Route Convergence observe convergence time by packet loss, so IGP Route Convergence
is considered a Direct Measure of Quality (DMOQ). The test cases is considered a Direct Measure of Quality (DMOQ). The test cases
in this document are black-box tests that emulate the network in this document are black-box tests that emulate the network
skipping to change at page 7, line 39 skipping to change at page 7, line 39
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 [2] 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. Time, Tree Build Time, and Hardware Update Time [1].
4.1.2 Convergence Due to Neighbor Interface Failure 4.1.2 Convergence Due to Neighbor Interface Failure
Objective Objective
To obtain the IGP Route Convergence due to a local link To obtain the IGP Route Convergence due to a local link
failure event at the Tester's Neighbor Interface. failure event at the Tester's Neighbor Interface.
Procedure Procedure
1. Advertise matching IGP routes from Tester to DUT on 1. Advertise matching IGP routes from Tester to DUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [2] using the topology shown in Figure 1. Set the cost of
skipping to change at page 8, line 24 skipping to change at page 8, line 24
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 [2] 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. Time, Tree Build Time, and Hardware Update Time [1].
4.1.3 Convergence Due to Remote Interface Failure 4.1.3 Convergence Due to Remote Interface Failure
Objective Objective
To obtain the IGP Route Convergence due to a Remote Interface To obtain the IGP Route Convergence due to a Remote Interface
Failure event. Failure event.
Procedure Procedure
1. Advertise matching IGP routes from Tester to SUT on 1. Advertise matching IGP routes from Tester to SUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 2. Set the cost of [2] using the topology shown in Figure 2. Set the cost of
skipping to change at page 9, line 12 skipping to change at page 9, line 12
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 failure indication, LSA/LSP Flood Packet Pacing,
LSA/LSP Retransmission Packet Pacing, LSA/LSP Generation LSA/LSP Retransmission Packet Pacing, LSA/LSP Generation
time, SPF delay, SPF Holdtime, SPF Execution Time, Tree time, SPF delay, SPF Holdtime, SPF Execution Time, Tree
Build Time, and Hardware Update Time. The additional Build Time, and Hardware Update Time [1]. 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.
skipping to change at page 9, line 47 skipping to change at page 9, line 47
Layer 2 session down event and converges all IGP routes and Layer 2 session down event and converges all IGP routes and
traffic over the Next-Best Egress Interface. traffic over the Next-Best Egress Interface.
6. Restore Layer 2 session on DUT's Preferred Egress Interface. 6. Restore Layer 2 session on DUT's Preferred Egress Interface.
7. Measure Restoration Convergence Time [2] as DUT detects the 7. Measure Restoration Convergence Time [2] as DUT detects the
session up event and converges all IGP routes and traffic 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. Time, Tree Build Time, and Hardware Update Time [1].
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
skipping to change at page 10, line 36 skipping to change at page 10, line 36
IGP session failure event and converges all IGP routes and IGP session failure event and converges all IGP routes and
traffic over the Next-Best Egress Interface. traffic over the Next-Best Egress Interface.
6. Stop offered load. Wait 30 seconds for queues to drain. 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
7. Restore IGP session on DUT's Preferred Egress Interface. 7. Restore IGP session on DUT's Preferred Egress Interface.
8. Measure Restoration Convergence Time [2] as DUT detects the 8. Measure Restoration Convergence Time [2] as DUT detects the
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 The measured IGP Convergence time is influenced by the IGP Hello
Hello Interval, IGP Dead Interval, SPF delay, SPF Holdtime, Interval, IGP Dead Interval, SPF delay, SPF Holdtime, SPF
SPF Execution Time, Tree Build Time, and Hardware Update Time. Execution Time, Tree Build Time, and Hardware Update Time [1].
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 [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [2] using the topology shown in Figure 1. Set the cost of
skipping to change at page 11, line 10 skipping to change at page 11, line 10
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 [2].
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Tester withdraws all IGP routes from DUT's Local Interface 4. Tester withdraws all IGP routes from DUT's Local Interface
on Preferred Egress Interface. on Preferred Egress Interface.
5. Measure Rate-Derived Convergence Time [2] as DUT detects the 5. Measure Rate-Derived Convergence Time [2] as DUT withdraws
Layer 2 session down event and converges all IGP routes and routes and converges all IGP routes and traffic over the
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 [2] as DUT converges all
IGP routes and traffic over the Preferred Egress Interface. IGP routes and traffic over the Preferred Egress Interface.
Results Results
The measured IGP Convergence time is the SPF Processing and FIB The measured IGP Convergence time is the SPF Processing and FIB
Update time as influenced by the SPF delay, SPF Holdtime, Update time as influenced by the SPF delay, SPF Holdtime, SPF
SPF Execution Time, Tree Build Time, and Hardware Update Time. Execution Time, Tree Build Time, and Hardware Update Time [1].
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 [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [2] using the topology shown in Figure 1. Set the cost of
skipping to change at page 11, line 53 skipping to change at page 11, line 53
cost change event and converges all IGP routes and traffic cost change event and converges all IGP routes and traffic
over the Next-Best Egress Interface. over the Next-Best Egress Interface.
6. Stop offered load. Wait 30 seconds for queues to drain. 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
7. Re-advertise IGP routes to DUT's Preferred Egress Interface 7. Re-advertise IGP routes to DUT's Preferred Egress Interface
with original lower cost metric. with original lower cost metric.
8. Measure Restoration Convergence Time [2] as DUT converges all 8. Measure Restoration Convergence Time [2] as DUT converges all
IGP routes and traffic over the Preferred Egress Interface. IGP routes and traffic over the Preferred Egress Interface.
Results Results
There should be no measured packet loss for this case. There should be no externally observable IGP Route Convergence
and no measured packet loss for this case.
IGP Data Plane Route Convergence 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 of an ECMP Member. failure event of an ECMP Member.
Procedure Procedure
1. Configure ECMP Set as shown in Figure 3. 1. Configure ECMP Set as shown in Figure 3.
skipping to change at page 12, line 35 skipping to change at page 12, line 35
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 [2] as DUT detects the
link up event and converges IGP routes and some distribution link up event and converges IGP routes and some distribution
of traffic over the restored ECMP member. of traffic over the restored ECMP member.
Results Results
The measured IGP Convergence time is influenced by 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].
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
skipping to change at page 13, line 16 skipping to change at page 13, line 16
8. Restore link on Tester's Neighbor Interface connected to 8. Restore link on Tester's Neighbor Interface connected to
DUT's Parallel Link member interface. DUT's Parallel Link member interface.
9. Measure Restoration Convergence Time [2] as DUT detects the 9. Measure Restoration Convergence Time [2] as DUT detects the
link up event and converges IGP routes and some distribution link up event and converges IGP routes and some distribution
of traffic over the restored Parallel Link member. of traffic over the restored Parallel Link member.
Results Results
The measured IGP Convergence time is influenced by the Local The measured IGP Convergence time is influenced by the Local
link failure indication, Tree Build Time, and Hardware Update link failure indication, Tree Build Time, and Hardware Update
Time. Time [1].
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. References 7. Acknowledgements
7.1 Normative References Thanks to Sue Hares, Al Morton, Kevin Dubray, and participants of
[1] Poretsky, S., "Benchmarking Applicability for IGP the BMWG for their contributions to this work.
Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-09,
work in progress, January 2006. 8. References
8.1 Normative References
[1] Poretsky, S., "Considerations for Benchmarking IGP
Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-10,
work in progress, March 2006.
[2] Poretsky, S., Imhoff, B., "Benchmarking Terminology for IGP [2] Poretsky, S., Imhoff, B., "Benchmarking Terminology for IGP
Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-09, Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-10,
work in progress, January 2006. work in progress, March 2006.
[3] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and Dual [3] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and Dual
Environments", RFC 1195, IETF, December 1990. Environments", RFC 1195, IETF, December 1990.
[4] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998. [4] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998.
[5] Bradner, S., "Benchmarking Terminology for Network [5] Bradner, S., "Benchmarking Terminology for Network
Interconnection Devices", RFC 1242, IETF, January 1991. Interconnection Devices", RFC 1242, IETF, March 1991.
[6] Bradner, S. and McQuaid, J., "Benchmarking Methodology for [6] Bradner, S. and McQuaid, J., "Benchmarking Methodology for
Network Interconnect Devices", RFC 2544, IETF, March 1999. Network Interconnect Devices", RFC 2544, IETF, March 1999.
7.2 Informative References 8.2 Informative References
None None
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
8. 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
Burlington, MA 01803 Burlington, MA 01803
USA USA
Phone: + 1 508 439 9008 Phone: + 1 508 439 9008
EMail: sporetsky@reefpoint.com EMail: sporetsky@reefpoint.com
Brent Imhoff Brent Imhoff
 End of changes. 19 change blocks. 
30 lines changed or deleted 37 lines changed or added

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