Internet Engineering Task Force (IETF) R. Asati
Request for Comments: 6201 C. Pignataro
Updates: 1242, 2544 F. Calabria
Category: Informational Cisco
ISSN: 2070-1721 C. Olvera
Consulintel
March 2011
Device Reset Characterization
Abstract
An operational forwarding device may need to be restarted
(automatically or manually) for a variety of reasons, an event called
a "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 device takes to resume the forwarding operation.
This document specifies a methodology for characterizing reset (and
reset time) during benchmarking of forwarding devices and provides
clarity and consistency in reset test procedures beyond what is
specified in RFC 2544. Therefore, it updates RFC 2544. This
document also defines the benchmarking term "reset time" and, only in
this, updates RFC 1242.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6201.
Asati, et al. Informational [Page 1]
RFC 6201 Reset Characterization March 2011
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................3
1.1. Scope ......................................................3
1.2. Reset Time .................................................4
1.3. Reset Time Measurement Methods .............................5
1.4. Reporting Format ...........................................6
2. Key Words to Reflect Requirements ...............................7
3. Test Requirements ...............................................7
4. Reset Tests .....................................................8
4.1. Hardware Reset Tests .......................................9
4.1.1. Routing Processor (RP) / Routing Engine Reset .......9
4.1.2. Line Card (LC) Removal and Insertion (REQUIRED) ....11
4.2. Software Reset Tests ......................................12
4.2.1. Operating System (OS) Reset (REQUIRED) .............12
4.2.2. Process Reset (OPTIONAL) ...........................13
4.3. Power Interruption Test ...................................14
4.3.1. Power Interruption (REQUIRED) ......................14
5. Security Considerations ........................................15
6. Acknowledgments ................................................16
7. References .....................................................16
7.1. Normative References ......................................16
7.2. Informative References ....................................16
Asati, et al. Informational [Page 2]
RFC 6201 Reset Characterization March 2011
1. Introduction
An operational forwarding device (or one of its components) may need
to be restarted for a variety of reasons, an event called a "reset"
in this document. Since there may be an interruption in the
datatracker.ietf.org