draft-ietf-bmwg-reset-03.txt   draft-ietf-bmwg-reset-04.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: May 2011 Fernando Calabria Expires: June 2011 Fernando Calabria
Cisco Cisco
Cesar Olvera Cesar Olvera
Consulintel Consulintel
November 9, 2010 December 8, 2010
Device Reset Characterization Device Reset Characterization
draft-ietf-bmwg-reset-03 draft-ietf-bmwg-reset-04
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 May 9, 2011. This Internet-Draft will expire on June 8, 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
skipping to change at page 3, line 19 skipping to change at page 3, line 19
2.1. Scope.....................................................4 2.1. Scope.....................................................4
2.2. Recovery Time Measurement Methods.........................5 2.2. Recovery Time Measurement Methods.........................5
2.3. Reporting Format..........................................6 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 Test.......................................9 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).....12
4.2. Software Reset Test......................................12 4.2. Software Reset Test......................................12
4.2.1. Operating System (OS) Reset (REQUIRED)..............13 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 Test..................................14 4.3. Power Interruption Test..................................14
4.3.1. Power Interruption (REQUIRED).......................15 4.3.1. Power Interruption (REQUIRED).......................15
5. Security Considerations.......................................16 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
skipping to change at page 9, line 18 skipping to change at page 9, line 18
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 hardware 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.
Reset procedures that do not require the physical removal and
insertion of a hardware component are RECOMMENDED. These include
using the CLI or a physical switch or button. If such procedures
cannot be performed (e.g., for lack of platform support, or because
the corresponding Test Case calls for them), human operation time
SHOULD be minimized across different platforms and Test Cases as
much as possible, and variation in human operator time SHOULD also
be minimized across different vendors products as much as practical,
by having the same person perform the operation, and by practicing
the operation.
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.
skipping to change at page 12, line 23 skipping to change at page 12, line 36
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 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.).
most accurate results will be obtained using the CLI or a physical
switch, and therefore these are RECOMMENDED. Otherwise, the time
spent trying to physically seat the LC will get mixed into the
results.
Finally, the characterization is completed by recording the frame Finally, the characterization is completed by recording the frame
loss or time stamps (as reported by the test tool) and calculating loss or time stamps (as reported by the test tool) and calculating
the recovery time (as defined in Section 2.2). the recovery time (as defined in Section 2.2).
Reporting Format Reporting Format
The reporting format is defined in Section 2.3. The reporting format is defined in Section 2.3.
4.2. Software Reset Test 4.2. Software Reset Test
 End of changes. 7 change blocks. 
10 lines changed or deleted 17 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/