draft-ietf-bmwg-reset-02.txt   draft-ietf-bmwg-reset-03.txt 
Benchmarking Methodology WG Rajiv Asati Benchmarking Methodology WG Rajiv Asati
Internet Draft Cisco Internet Draft Cisco
Updates: 2544 (if approved) Carlos Pignataro Updates: 2544 (if approved) Carlos Pignataro
Intended status: Informational Cisco Intended status: Informational Cisco
Expires: April 2011 Fernando Calabria Expires: May 2011 Fernando Calabria
Cisco Cisco
Cesar Olvera Cesar Olvera
Consulintel Consulintel
October 10, 2010 November 9, 2010
Device Reset Characterization Device Reset Characterization
draft-ietf-bmwg-reset-02 draft-ietf-bmwg-reset-03
Abstract Abstract
An operational forwarding device may need to be re-started An operational forwarding device may need to be re-started
(automatically or manually) for a variety of reasons, an event that (automatically or manually) for a variety of reasons, an event that
we call a "reset" in this document. Since there may be an we call a "reset" in this document. Since there may be an
interruption in the forwarding operation during a reset, it is interruption in the forwarding operation during a reset, it is
useful to know how long a device takes to resume the forwarding useful to know how long a device takes to resume the forwarding
operation. operation.
skipping to change at page 2, line 10 skipping to change at page 2, line 10
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference 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
This Internet-Draft will expire on April 10, 2011. This Internet-Draft will expire on May 9, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction...................................................4 1. Key Words to Reflect Requirements..............................4
1.1. Scope.....................................................4 2. Introduction...................................................4
1.2. Recovery Time Measurement Methods.........................4 2.1. Scope.....................................................4
1.3. Reporting Format..........................................5 2.2. Recovery Time Measurement Methods.........................5
2. Key Words to Reflect Requirements..............................7 2.3. Reporting Format..........................................6
3. Test Requirements..............................................7 3. Test Requirements..............................................7
4. Reset Test.....................................................8 4. Reset Test.....................................................8
4.1. Hardware Reset............................................8 4.1. Hardware Reset Test.......................................9
4.1.1. Routing Processor (RP) / Routing Engine reset........9 4.1.1. Routing Processor (RP) / Routing Engine Reset........9
4.1.1.1. RP Reset for a single-RP device (REQUIRED)......9 4.1.1.1. RP Reset for a single-RP device (REQUIRED)......9
4.1.1.2. RP Switchover for a multiple-RP device (OPTIONAL) 4.1.1.2. RP Switchover for a multiple-RP device (OPTIONAL)
........................................................10 ........................................................10
4.1.2. Line Card (LC) Removal and Insertion (REQUIRED).....11 4.1.2. Line Card (LC) Removal and Insertion (REQUIRED).....11
4.2. Software Reset...........................................12 4.2. Software Reset Test......................................12
4.2.1. Operating System (OS) reset (REQUIRED)..............12 4.2.1. Operating System (OS) Reset (REQUIRED)..............13
4.2.2. Process reset (OPTIONAL)............................13 4.2.2. Process Reset (OPTIONAL)............................13
4.3. Power interruption.......................................14 4.3. Power Interruption Test..................................14
4.3.1. Power Interruption (REQUIRED).......................14 4.3.1. Power Interruption (REQUIRED).......................15
5. Security Considerations.......................................15 5. Security Considerations.......................................16
6. IANA Considerations...........................................16 6. IANA Considerations...........................................16
7. Acknowledgments...............................................16 7. Acknowledgments...............................................16
8. References....................................................17 8. References....................................................17
8.1. Normative References.....................................17 8.1. Normative References.....................................17
8.2. Informative References...................................17 8.2. Informative References...................................17
Authors' Addresses...............................................18 Authors' Addresses...............................................18
1. Introduction 1. Key Words to Reflect Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119]. RFC 2119 defines the use of these key words to help make
the intent of standards track documents as clear as possible. While
this document uses these keywords, this document is not a standards
track document.
2. Introduction
An operational forwarding device (or one of its components) may need An operational forwarding device (or one of its components) may need
to be re-started for a variety of reasons, an event that we call a to be re-started for a variety of reasons, an event that we call a
"reset" in this draft. Since there may be an interruption in the "reset" in this document. Since there may be an interruption in the
forwarding operation during a reset, it is useful to know how long a forwarding operation during a reset, it is useful to know how long a
device takes to resume the forwarding operation. In other words, it device takes to resume the forwarding operation. In other words, it
is desired to know how long the recovery time after the reset is. is desired to know the duration of the recovery time following the
reset.
However, the answer to this question is no longer simple and However, the answer to this question is no longer simple and
straight-forward as the modern forwarding devices employ many straight-forward as the modern forwarding devices employ many
hardware advancements (distributed forwarding, etc.) and software hardware advancements (distributed forwarding, etc.) and software
advancements (graceful restart, etc.) that influence the recovery advancements (graceful restart, etc.) that influence the recovery
time after the reset. time after the reset.
1.1. Scope 2.1. Scope
This document specifies a methodology for characterizing reset (and This document specifies a methodology for characterizing reset (and
recovery time) during benchmarking of forwarding devices, and recovery time) during benchmarking of forwarding devices, and
provides clarity and consistency in reset procedures beyond what is provides clarity and consistency in reset procedures beyond what is
specified in [RFC2544]. Software upgrades incur additional specified in [RFC2544]. Software upgrades involve additional
benchmarking complexities and are outside the scope of this benchmarking complexities and are outside the scope of this
document. document.
These procedures may be used by other benchmarking documents such as These procedures may be used by other benchmarking documents such as
[RFC2544], [RFC5180], [RFC5695], etc., and is expected that other [RFC2544], [RFC5180], [RFC5695], etc., and is expected that other
protocol-specific benchmarking documents would reference this protocol-specific benchmarking documents would reference this
document for reset recovery time characterization. document for reset recovery time characterization.
This document updates Section 26.6 of [RFC2544]. This document updates Section 26.6 of [RFC2544].
This document focuses on only the reset criterion of benchmarking, This document focuses only on the reset criterion of benchmarking,
and presumes that it would be beneficial to [RFC5180], [RFC5695], and presumes that it would be beneficial to [RFC5180], [RFC5695],
and other BMWG benchmarking efforts. and other BMWG benchmarking efforts.
1.2. Recovery Time Measurement Methods 2.2. Recovery Time Measurement Methods
The 'recovery time' is the time during which the traffic forwarding The 'recovery time' is the time during which the traffic forwarding
is temporarily interrupted following a reset event. Strictly is temporarily interrupted following a reset event. Strictly
speaking, this is the time over which one or more frames are lost. speaking, this is the time over which one or more frames are lost.
This definition is similar to that of 'Loss of connectivity period' This definition is similar to that of 'Loss of connectivity period'
defined in [IGPConv] section 4. defined in [IGPConv] section 4.
There are two accepted methods to measure the 'recovery time': There are two accepted methods to measure the 'recovery time':
1. Frame-Loss Method - This method requires testtool capability to 1. Frame-Loss Method - This method requires test tool capability
monitor the number of lost frames. In this method, the offered to monitor the number of lost frames. In this method, the
stream rate (frames per second) must be known. The recovery offered stream rate (frames per second) must be known. The
time is calculated per the below equation: recovery time is calculated per the below equation:
Recovery_time = Frames_lost (packets) / Offered_rate Frames_lost (packets)
(packets per second) Recovery_time = -------------------------------------
Offered_rate (packets per second)
2. Time-Stamp Method - This method requires testtool capability to 2. Time-Stamp Method - This method requires test tool capability
timestamp each frame. In this method, the testtool timestamps to timestamp each frame. In this method, the test tool
each transmitted frame and monitors the received frame's timestamps each transmitted frame and monitors the received
timestamp. During the test, the test tool would record the frame's timestamp. During the test, the test tool would record
timestamp (Timestamp A) of the frame that was last received the timestamp (Timestamp A) of the frame that was last
prior to the reset interruption and the timestamp (Timestamp received prior to the reset interruption and the timestamp
B) of the first frame after the interruption stopped. The (Timestamp B) of the first frame after the interruption
difference between Timestamp B and Timestamp A is the recovery stopped. The difference between Timestamp B and Timestamp A is
time. the recovery time.
The tester/operator MAY use either method for recovery time The tester / operator MAY use either method for recovery time
measurement depending on the testtool capability. However, the measurement depending on the test tool capability. However, the
Frame-loss method SHOULD be used if the test tool is capable of (a) Frame-loss method SHOULD be used if the test tool is capable of (a)
counting the number of lost frames per stream, and (b) transmitting counting the number of lost frames per stream, and (b) transmitting
test frame despite the physical link status, whereas Time-stamp test frame despite the physical link status, whereas Time-stamp
method SHOULD be used if the test tool is capable of (a) time- method SHOULD be used if the test tool is capable of (a) time-
stamping each frame, (b) monitoring received frame's timestamp, and stamping each frame, (b) monitoring received frame's timestamp, and
(c) transmitting frames only if the physical link status is UP. (c) transmitting frames only if the physical link status is UP.
1.3. Reporting Format 2.3. Reporting Format
All reset results are reported in a simple statement including the All reset results are reported in a simple statement including the
frame loss and recovery times. frame loss (if measured) and recovery times.
For each test case, it is RECOMMENDED that the following parameters For each test case, it is RECOMMENDED that the following parameters
be reported in these units: be reported in these units:
Parameter Units or Examples Parameter Units or Examples
-----------------------------------------------------------------
Throughput Frames per second and bits per Throughput Frames per second and bits per
second second
Loss (average) Frames Loss (average) Frames
Recovery Time (average) Milliseconds Recovery Time (average) Milliseconds
Number of trials Integer count Number of trials Integer count
Protocol IPv4, IPv6, MPLS, etc. Protocol IPv4, IPv6, MPLS, etc.
skipping to change at page 6, line 30 skipping to change at page 6, line 42
Port Media Ethernet, GigE (Gigabit Ethernet), Port Media Ethernet, GigE (Gigabit Ethernet),
POS (Packet over SONET), etc. POS (Packet over SONET), etc.
Port Speed 10 Gbps, 1 Gbps, 100 Mbps, etc. Port Speed 10 Gbps, 1 Gbps, 100 Mbps, etc.
Interface Encap. Ethernet, Ethernet VLAN, Interface Encap. Ethernet, Ethernet VLAN,
PPP, HDLC, etc. PPP, HDLC, etc.
For mixed protocol environments, frames SHOULD be distributed For mixed protocol environments, frames SHOULD be distributed
between all the different protocols. The distribution MAY between all the different protocols. The distribution MAY
approximate the network conditions of deployment. IN all cases the approximate the network conditions of deployment. In all cases the
details of the mixed protocol distribution MUST be included in the details of the mixed protocol distribution MUST be included in the
reporting. reporting.
Additionally, the DUT and test bed provisioning, configuration, and Additionally, the DUT (Device Under Test) / SUT (System Under Test)
deployed methodologies that may influence the overall recovery time and test bed provisioning, port and Line Card arrangement,
MUST be listed. (Refer to the additional factors listed in Section configuration, and deployed methodologies that may influence the
3). overall recovery time MUST be listed. (Refer to the additional
factors listed in Section 3).
The reporting of results MUST regard repeatability considerations The reporting of results MUST regard repeatability considerations
from Section 4 of [RFC2544]. It is RECOMMENDED to perform multiple from Section 4 of [RFC2544]. It is RECOMMENDED to perform multiple
trials and report average results. trials and report average results.
2. Key Words to Reflect Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119]. RFC 2119 defines the use of these key words to help make
the intent of standards track documents as clear as possible. While
this document uses these keywords, this document is not a standards
track document.
3. Test Requirements 3. Test Requirements
In order to provide consistent and fairness while benchmarking a set In order to provide consistent and fairness while benchmarking a set
of different DUTs, the Network tester / Operator MUST (a) use of different DUTs, the Network tester / operator MUST (a) use
identical control and data plane information during testing, (b) identical control and data plane information during testing, (b)
document & report any factors that may influence the overall time document & report any factors that may influence the overall time
after reset / convergence. after reset / convergence.
Some of these factors include: Some of these factors include:
1. Type of reset - Hardware (line-card crash, etc.) vs. Software 1. Type of reset - Hardware (line-card crash, etc.) vs. Software
(protocol reset, process crash, etc.) or even complete power (protocol reset, process crash, etc.) or even complete power
failures failures
skipping to change at page 8, line 42 skipping to change at page 9, line 5
Section 4.1 describes various hardware resets, whereas Section 4.2 Section 4.1 describes various hardware resets, whereas Section 4.2
describes various software resets. Additionally, Section 4.3 describes various software resets. Additionally, Section 4.3
describes power interruption tests. These sections define and describes power interruption tests. These sections define and
characterize these resets. characterize these resets.
Additionally, since device specific implementations may vary for Additionally, since device specific implementations may vary for
hardware and software type resets, it is desirable to classify each hardware and software type resets, it is desirable to classify each
test case as "REQUIRED" or "OPTIONAL". test case as "REQUIRED" or "OPTIONAL".
4.1. Hardware Reset 4.1. Hardware Reset Test
A test designed to characterize the time it takes a DUT to recover A test designed to characterize the time it takes a DUT to recover
from the hardware reset. from the hardware reset.
A "hardware reset" generally involves the re-initialization of one A "hardware reset" generally involves the re-initialization of one
or more physical components in the DUT, but not the entire DUT. or more physical components in the DUT, but not the entire DUT.
A hardware reset is executed by the operator for example by physical A hardware reset is executed by the operator for example by physical
removal of a physical component, by pressing on a "reset" button for removal of a hardware component, by pressing on a "reset" button for
the component, or could even be triggered from the command line the component, or could even be triggered from the command line
interface. interface.
For routers that do not contain separate Routing Processor and Line For routers that do not contain separate Routing Processor and Line
Card modules, the hardware reset tests are not performed since they Card modules, the hardware reset tests are not performed since they
are not relevant; instead, the power interruption tests MUST be are not relevant; instead, the power interruption tests MUST be
performed (see Section 4.3) in these cases. performed (see Section 4.3) in these cases.
4.1.1. Routing Processor (RP) / Routing Engine reset 4.1.1. Routing Processor (RP) / Routing Engine Reset
The Routing Processor (RP) is the DUT module that is primarily The Routing Processor (RP) is the DUT module that is primarily
concerned with Control Plane functions. concerned with Control Plane functions.
4.1.1.1. RP Reset for a single-RP device (REQUIRED) 4.1.1.1. RP Reset for a single-RP device (REQUIRED)
Objective Objective
To characterize time needed for a DUT to recover from a Route To characterize time needed for a DUT to recover from a Route
processor hardware reset in a single RP environment. processor hardware reset in a single RP environment.
skipping to change at page 10, line 4 skipping to change at page 10, line 13
least 15 seconds before any test activities are performed. The least 15 seconds before any test activities are performed. The
traffic should use the minimum frame size possible on the media traffic should use the minimum frame size possible on the media
used in the testing and rate should be sufficient for the DUT to used in the testing and rate should be sufficient for the DUT to
attain the maximum forwarding throughput. This enables a finer attain the maximum forwarding throughput. This enables a finer
granularity in the recovery time measurement. granularity in the recovery time measurement.
Third, perform the Route Processor (RP) hardware reset at this Third, perform the Route Processor (RP) hardware reset at this
point. This entails for example physically removing the RP to point. This entails for example physically removing the RP to
later re-insert it, or triggering a hardware reset by other means later re-insert it, or triggering a hardware reset by other means
(e.g., command line interface, physical switch, etc.) (e.g., command line interface, physical switch, etc.)
Finally, the characterization is completed by recording the frame Finally, the characterization is completed by recording the frame
loss (as reported by the test tool) and calculating the recovery loss or time stamps (as reported by the test tool) and calculating
time (by following the section 1.2). the recovery time (as defined in Section 2.2).
Reporting format Reporting format
The reporting format is defined in Section 1.3. The reporting format is defined in Section 2.3.
4.1.1.2. RP Switchover for a multiple-RP device (OPTIONAL) 4.1.1.2. RP Switchover for a multiple-RP device (OPTIONAL)
Objective Objective
To characterize time needed for "secondary" Route Processor To characterize time needed for "secondary" Route Processor
(sometimes referred to as "backup" RP) of a DUT to become active (sometimes referred to as "backup" RP) of a DUT to become active
after a "primary" (or "active") Route Processor hardware reset. after a "primary" (or "active") Route Processor hardware reset.
This process is often referred to as "RP Switchover". The This process is often referred to as "RP Switchover". The
characterization in this test should be done for the default DUT characterization in this test should be done for the default DUT
skipping to change at page 11, line 8 skipping to change at page 11, line 17
Second, ensure that the DUT is able to forward the traffic for at Second, ensure that the DUT is able to forward the traffic for at
least 15 seconds before any test activities are performed. The least 15 seconds before any test activities are performed. The
traffic should use the minimum frame size possible on the media traffic should use the minimum frame size possible on the media
used in the testing and rate should be sufficient for the DUT to used in the testing and rate should be sufficient for the DUT to
attain the maximum forwarding throughput. This enables a finer attain the maximum forwarding throughput. This enables a finer
granularity in the recovery time measurement. granularity in the recovery time measurement.
Third, perform the primary Route Processor (RP) hardware reset at Third, perform the primary Route Processor (RP) hardware reset at
this point. This entails for example physically removing the RP, this point. This entails for example physically removing the RP,
or triggering a hardware reset by other means (e.g., command line or triggering a hardware reset by other means (e.g., command line
interface, physical switch, etc.) It is up to the Operator to interface, physical switch, etc.) It is up to the operator to
decide if the primary RP needs to be re-inserted after a grace decide if the primary RP needs to be re-inserted after a grace
period or not. period or not.
Finally, the characterization is completed by recording the frame Finally, the characterization is completed by recording the frame
loss (as reported by the test tool) and calculating the recovery loss or time stamps (as reported by the test tool) and calculating
time (by following the section 1.2). the recovery time (as defined in Section 2.2).
Reporting format Reporting format
The reset results are potentially reported twice, one for the The reset results are potentially reported twice, one for the
default switchover behavior (i.e., the DUT without any switchover- default switchover behavior (i.e., the DUT without any switchover-
specific enhanced configuration) and the other for the switchover- specific enhanced configuration) and the other for the switchover-
specific behavior if it exists (i.e., the DUT configured for specific behavior if it exists (i.e., the DUT configured for
optimized switchover capabilities that minimize the downtime optimized switchover capabilities that minimize the downtime
during the actual switchover). during the actual switchover).
The reporting format is defined in Section 1.3, and also includes The reporting format is defined in Section 2.3, and also includes
any specific redundancy scheme in place. any specific redundancy scheme in place.
4.1.2. Line Card (LC) Removal and Insertion (REQUIRED) 4.1.2. Line Card (LC) Removal and Insertion (REQUIRED)
The Line Card (LC) is the DUT component that is responsible with The Line Card (LC) is the DUT component that is responsible with
packet forwarding. packet forwarding.
Objective Objective
To characterize time needed for a DUT to recover from a Line Card To characterize time needed for a DUT to recover from a Line Card
skipping to change at page 12, line 22 skipping to change at page 12, line 30
Third, perform the Line Card (LC) hardware reset at this point. Third, perform the Line Card (LC) hardware reset at this point.
This entails for example physically removing the LC to later re- This entails for example physically removing the LC to later re-
insert it, or triggering a hardware reset by other means (e.g., insert it, or triggering a hardware reset by other means (e.g.,
command line interface (CLI), physical switch, etc.). However, command line interface (CLI), physical switch, etc.). However,
most accurate results will be obtained using the CLI or a physical most accurate results will be obtained using the CLI or a physical
switch, and therefore these are RECOMMENDED. Otherwise, the time switch, and therefore these are RECOMMENDED. Otherwise, the time
spent trying to physically seat the LC will get mixed into the spent trying to physically seat the LC will get mixed into the
results. results.
Finally, the characterization is completed by recording the frame Finally, the characterization is completed by recording the frame
loss (as reported by the test tool) and calculating the recovery loss or time stamps (as reported by the test tool) and calculating
time (by following the section 1.2). the recovery time (as defined in Section 2.2).
Reporting Format Reporting Format
The reporting format is defined in Section 1.3. The reporting format is defined in Section 2.3.
4.2. Software Reset 4.2. Software Reset Test
To characterize time needed for a DUT to recover from the software To characterize time needed for a DUT to recover from the software
reset. reset.
In contrast to a "hardware reset", a "software reset" involves only In contrast to a "hardware reset", a "software reset" involves only
the re-initialization of the execution, data structures, and partial the re-initialization of the execution, data structures, and partial
state within the software running on the DUT module(s). state within the software running on the DUT module(s).
A software reset is initiated for example from the DUT's Command A software reset is initiated for example from the DUT's Command
Line Interface (CLI). Line Interface (CLI).
4.2.1. Operating System (OS) reset (REQUIRED) 4.2.1. Operating System (OS) Reset (REQUIRED)
Objective Objective
To characterize time needed for a DUT to recover from an Operating To characterize time needed for a DUT to recover from an Operating
System (OS) software reset. System (OS) software reset.
Procedure Procedure
First, complete some or all of the following operational tasks: First, complete some or all of the following operational tasks:
save the current DUT configuration, specify software boot save the current DUT configuration, specify software boot
parameters, ensure the appropriate software files are available, parameters, ensure the appropriate software files are available,
or perform additional Operating System task. or perform additional Operating System task.
Second, ensure that the DUT is able to forward the traffic for at Second, ensure that the DUT is able to forward the traffic for at
least 15 seconds before any test activities are performed. The least 15 seconds before any test activities are performed. The
traffic should use the minimum frame size possible on the media traffic should use the minimum frame size possible on the media
used in the testing and rate should be sufficient for the DUT to used in the testing and rate should be sufficient for the DUT to
attain the maximum forwarding throughput. This enables a finer attain the maximum forwarding throughput. This enables a finer
skipping to change at page 13, line 21 skipping to change at page 13, line 31
traffic should use the minimum frame size possible on the media traffic should use the minimum frame size possible on the media
used in the testing and rate should be sufficient for the DUT to used in the testing and rate should be sufficient for the DUT to
attain the maximum forwarding throughput. This enables a finer attain the maximum forwarding throughput. This enables a finer
granularity in the recovery time measurement. granularity in the recovery time measurement.
Third, trigger an Operating System re-initialization in the DUT, Third, trigger an Operating System re-initialization in the DUT,
by operational means such as use of the DUT's Command Line by operational means such as use of the DUT's Command Line
Interface (CLI) or other management interface. Interface (CLI) or other management interface.
Finally, the characterization is completed by recording the frame Finally, the characterization is completed by recording the frame
loss (as reported by the test tool) and calculating the recovery loss or time stamps (as reported by the test tool) and calculating
time (by following the section 1.2). the recovery time (as defined in Section 2.2).
Reporting format Reporting format
The reporting format is defined in Section 1.3. The reporting format is defined in Section 2.3.
4.2.2. Process reset (OPTIONAL) 4.2.2. Process Reset (OPTIONAL)
Objective Objective
To characterize time needed for a DUT to recover from a software To characterize time needed for a DUT to recover from a software
process reset. process reset.
Such time period may depend upon the number and types of process Such time period may depend upon the number and types of process
running in the DUT and which ones are tested. Different running in the DUT and which ones are tested. Different
implementations of forwarding devices include various common implementations of forwarding devices include various common
processes. A process reset should be performed only in the processes. A process reset should be performed only in the
skipping to change at page 14, line 17 skipping to change at page 14, line 27
traffic should use the minimum frame size possible on the media traffic should use the minimum frame size possible on the media
used in the testing and rate should be sufficient for the DUT to used in the testing and rate should be sufficient for the DUT to
attain the maximum forwarding throughput. This enables a finer attain the maximum forwarding throughput. This enables a finer
granularity in the recovery time measurement. granularity in the recovery time measurement.
Third, trigger a process reset for each process running in the DUT Third, trigger a process reset for each process running in the DUT
and considered for testing from a management interface (e.g., by and considered for testing from a management interface (e.g., by
means of the Command Line Interface (CLI), etc.) means of the Command Line Interface (CLI), etc.)
Finally, the characterization is completed by recording the frame Finally, the characterization is completed by recording the frame
loss (as reported by the test tool) and calculating the recovery loss or time stamps (as reported by the test tool) and calculating
time (by following the section 1.2). the recovery time (as defined in Section 2.2).
Reporting format Reporting format
The reporting format is defined in Section 1.3, and is used for The reporting format is defined in Section 2.3, and is used for
each process running in the DUT and tested. Given the each process running in the DUT and tested. Given the
implementation nature of this test, details of the actual process implementation nature of this test, details of the actual process
tested should be included along with the statement. tested should be included along with the statement.
4.3. Power interruption 4.3. Power Interruption Test
"Power interruption" refers to the complete loss of power on the "Power interruption" refers to the complete loss of power on the
DUT. It can be viewed as a special case of a hardware reset, DUT. It can be viewed as a special case of a hardware reset,
triggered by the loss of the power supply to the DUT or its triggered by the loss of the power supply to the DUT or its
components, and is characterized by the re-initialization of all components, and is characterized by the re-initialization of all
hardware and software in the DUT. hardware and software in the DUT.
4.3.1. Power Interruption (REQUIRED) 4.3.1. Power Interruption (REQUIRED)
Objective Objective
To characterize time needed for a DUT to recover efrom a complete To characterize time needed for a DUT to recover from a complete
loss of electric power or complete power interruption. This test loss of electric power or complete power interruption. This test
simulates a complete power failure or outage, and should be simulates a complete power failure or outage, and should be
indicative of the DUT/SUTs behavior during such event. indicative of the DUT/SUTs behavior during such event.
Procedure Procedure
First, ensure that the entire DUT is at a permanent state to which First, ensure that the entire DUT is at a permanent state to which
it will return to after the power interruption, by performing some it will return to after the power interruption, by performing some
or all of the following operational tasks: save the current DUT or all of the following operational tasks: save the current DUT
configuration, specify boot parameters, ensure the appropriate configuration, specify boot parameters, ensure the appropriate
skipping to change at page 15, line 29 skipping to change at page 15, line 38
granularity in the recovery time measurement. granularity in the recovery time measurement.
Third, interrupt the power (AC or DC) that feeds the corresponding Third, interrupt the power (AC or DC) that feeds the corresponding
DUTs power supplies at this point. This entails for example DUTs power supplies at this point. This entails for example
physically removing the power supplies in the DUT to later re- physically removing the power supplies in the DUT to later re-
insert them, or simply disconnecting or switching off their power insert them, or simply disconnecting or switching off their power
feeds (AC or DC as applicable). The actual power interruption feeds (AC or DC as applicable). The actual power interruption
should last at least 15 seconds. should last at least 15 seconds.
Finally, the characterization is completed by recording the frame Finally, the characterization is completed by recording the frame
loss (as reported by the test tool) and calculating the recovery loss or time stamps (as reported by the test tool) and calculating
time (by following the section 1.2). the recovery time (as defined in Section 2.2).
For easier comparison with other testing, the 15 seconds are For easier comparison with other testing, the 15 seconds are
removed from the reported recovery time. removed from the reported recovery time.
Reporting format Reporting format
The reporting format is defined in Section 1.3. The reporting format is defined in Section 2.3.
5. Security Considerations 5. Security Considerations
Benchmarking activities, as described in this memo, are limited to Benchmarking activities, as described in this memo, are limited to
technology characterization using controlled stimuli in a laboratory technology characterization using controlled stimuli in a laboratory
environment, with dedicated address space and the constraints environment, with dedicated address space and the constraints
specified in the sections above. specified in the sections above.
The benchmarking network topology will be an independent test setup The benchmarking network topology will be an independent test setup
and MUST NOT be connected to devices that may forward the test and MUST NOT be connected to devices that may forward the test
skipping to change at page 16, line 25 skipping to change at page 16, line 37
6. IANA Considerations 6. IANA Considerations
There is no IANA consideration for this document. There is no IANA consideration for this document.
7. Acknowledgments 7. Acknowledgments
The authors would like to thank Ron Bonica, who motivated us to The authors would like to thank Ron Bonica, who motivated us to
write this document. The authors would also like to thank Al Morton, write this document. The authors would also like to thank Al Morton,
Andrew Yourtchenko, David Newman, John E. Dawson, Timmons C. Player, Andrew Yourtchenko, David Newman, John E. Dawson, Timmons C. Player,
Jan Novak, Steve Maxwell, and Ilya Varlashkin for providing thorough Jan Novak, Steve Maxwell, Ilya Varlashkin, and Sarah Banks for
review, useful suggestions, and valuable input. providing thorough review, useful suggestions, and valuable input.
This document was prepared using 2-Word-v2.0.template.dot. This document was prepared using 2-Word-v2.0.template.dot.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
skipping to change at page 18, line 37 skipping to change at page 18, line 37
USA USA
Email: fcalabri@cisco.com Email: fcalabri@cisco.com
Cesar Olvera Cesar Olvera
Consulintel Consulintel
Joaquin Turina, 2 Joaquin Turina, 2
Pozuelo de Alarcon, Madrid, E-28224 Pozuelo de Alarcon, Madrid, E-28224
Spain Spain
Phone: +34 91 151 81 99
Email: cesar.olvera@consulintel.es Email: cesar.olvera@consulintel.es
 End of changes. 50 change blocks. 
89 lines changed or deleted 95 lines changed or added

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