Revision 2: Updated the error recovery tables. Incorporate input from February 23, 2004 teleconference.
|
|
|
- Edward Greene
- 5 years ago
- Views:
Transcription
1 To: INCITS T10 Committee From: Susan Gray, Quantum Date: February 23, 2004 Document Number: T10/04-056r2 Subject: ADT Link service error recovery 1 Revision History Revision 2: Updated the error recovery tables. Incorporate input from February 23, 2004 teleconference. Revision 1: Incorporate input from February 9, 2004 teleconference. Revision 0: Initial proposal 2 Discussion The current error recovery section does not address error recovery of link service frames. The following table summarizes the intended recovery procedures for each frame type and port state. Corrupted errors become retryable errors and are not listed in the table. Symbol framing errors don t relate to frames and always have the same recovery procedure and therefore are not listed in the table. Legend: retryable (sender detected error) protocol should never happen resource limitation recoverable (only possible for non-link service frames) none: no error recovery method is currently defined impossible: can t happen illegal: not valid to send the frame type in the corresponding state Transmitter error recovery Frame State P0 Initial P1 Login / TS Active / TS Paused Login Logout NOP Pause Initiate Other frame types (port login is always sent from p1 login) Initiate new login exchange transition to P1 N/A
2 P4 Logged Out T1 Initiate T2 Retry Initiate Abort open exchanges & initiate Login exchange with default params (AOE = 1) Receiver error recovery Frame State P0 Initial Login Logout NOP Pause Initiate Other frame types P1 Login / T0 Active / T1 Paused P4 Logged Out R1 Pending R2 Recovering ADT Revision 10 currently includes the following error recovery subclauses: 4.7 link layer error recovery Error detection Error detection overview Error detection by the frame sender Error detection by the frame receiver Error recovery for non link service frames (place holder for Login recovery) Retryable error
3 Corrupted frame Protocol error Resource limitation Recoverable error Error recovery for symbol framing errors 3 Proposed changes Add N5:Login complete state to handle the successful completion of the login process and allows N0:Idle to be used for error cases. Globally change N4:Complete to N4:Agreed add f) N5:Login Complete replace existing Figure 5 Link Negotiation state diagram with the following diagram
4 Link Negotiation Login IU Received Acknowledgment IU Received Acknowledgement IU Transmitted N0:Idle Initiate Login N1:Negotiating N2:Accept Sent N3:Accept ACK Sent N5:Login Complete N4:Agreed Login Process Complete (from any state except N5:Login Complete) Acknowledgement IU State Description (N0:Idle) The N0:Idle state waits for the port to receive a Transition N0:Idle to N1:Negotiating This transition shall occur when a Received message is received and the parameters within the are unacceptable.
5 Transition N0:Idle to N2:Accept Sent If the received has the ACCEPT bit is set to zero and the parameters are acceptable, the port shall send a with the parameters unchanged and the ACCEPT bit set to one and transition to N2:Accept Sent Transition N3:Accept ACK Sent to N5:Login Complete When the ACK IU has finished transmitting, the port shall set its operating parameters to the negotiated values and transition to N5:Login Complete Transition N4:Agreed to N5:Login Complete After receiving an ACK IU for the it sent, the port shall set its operating parameters to the negotiated values and transition to N5:Login Complete N5:Login Complete state State description A port enters this state when both ports have sent and received a with the ACCEPT bit set to one. Upon entry into this state, a Login Process Complete message shall be sent to the port state machine Error recovery for non link service frames Error recovery for s If an error is detected on a, the receiver port shall transition to P1:Login, sub state N0:Idle and the transmitter port shall restart the negotiation process. This is accomplished by transitioning to N1:Negotiating and initiating a[0] new login exchange using default operating parameters Error recovery for symbol framing errors After detecting four or more symbol framing errors without the receipt of a frame, a port shall abort all exchanges, set the operating parameters of the interface to default settings, transition to P1:Login and initiate a Login exchange with the AOE bit set to one.
Revision 6: Red text Incorporate comments from January 5, 2004 conference call. Minor wording changes.
To: INCITS T10 Committee From: Susan Gray, Quantum Date: January, 5, 2004 Document Number: T10/03-355r6 Subject: ADT Section 4.7.1.3 1 Revision History Revision 6: Red text Incorporate comments from January
Seagate 4 35 E last sentence Why is the P0:P1 transition condition described here?
ADT Letter Ballot Comments Company Number Page E/T Location Comment Suggestion Seagate 2 34 E 4.1 first sentence Numeral "2" should be spelled out Change to "two" Seagate 3 35 E 4.3.1 last sentence Grammar:
04-162r0 ADT Letter Ballot Comment Resolutions
Company Number Page Reference E/T Comment Additional Comment Disposition HPQ 1 1 E Replace with 'Working Draft' on two lines. HPQ 2 1 E Replace with 'T10 Project 1557-D' on two lines with the line break
ADT Frame Format Notes (Paul Suhler) ADI ADT Frame Format Proposal (Rod Wideman)
To: INCITS T10 Membership From: Paul Entzel, Quantum Date: 11 November 2002 Document: T10/02-329r2 Subject: Proposed frame format for ADT 1 Related Documents T10/02-233r0 T10/02-274r0 ADT Frame Format
Revisions. General. T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 13 June 2008 SUBJECT: T10/07-469r5, ADT-2: Internet ADT (iadt)
TO: T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 13 June 2008 SUBJECT: T10/07-469r5, ADT-2: Internet ADT (iadt) Revisions 0 Initial revision (2 November 2007) 1 First revision (9 March
Revisions. General. T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 29 May 2008 SUBJECT: T10/07-469r4, ADT-2: Internet ADT (iadt)
TO: T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 29 May 2008 SUBJECT: T10/07-469r4, -2: Internet (i) Revisions 0 Initial revision (2 November 2007) 1 First revision (9 March 2008) Changed
Revisions. T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 31 August 2008 SUBJECT: T10/07-469r8, ADT-2: Internet ADT (iadt)
TO: T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 31 August 2008 SUBJECT: T10/07-469r8, ADT-2: Internet ADT (iadt) Revisions 0 Initial revision (2 November 2007) 1 First revision (9 March
Revision 1: Correct editorial issues identified at the 22 September 2003 working group conference call.
To: From: INCITS T10 Committee Paul Entzel, Quantum Date: 20 October 2003 Document: Subject: T10/03-322r2 Transport protocol service extensions for ADT. 1 Revision History Revision 0: Initial revision.
04-162r2 ADT Letter Ballot Comment Resolutions
ADIC 1 2 E I believe George has a different e-mail W address ADIC 2 2 E The even numbered roman numeral page numbers are right-facing instead of left (through TOC section) W Accepted 14 ADIC 3 3 E The
Draft Minutes Automation/Drive Interface (ADI) Working Group Ad Hoc Teleconference T10/03-069r0 29 January :00 AM 10:00 AM PST
Draft Minutes Automation/Drive Interface (ADI) Working Group Ad Hoc Teleconference T10/03-069r0 29 January 2003 8:00 AM 10:00 AM PST 0. Conference Call Information (hosted by Seagate): Toll Free: (866)
Revisions. T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 21 October 2008 SUBJECT: T10/08-409r0, ADT-2: Internet ADT (iadt)
TO: T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 21 October 2008 SUBJECT: T10/08-409r0, ADT-2: Internet ADT (iadt) Revisions T10/07-469: 0 Initial revision (2 November 2007) 1 First revision
T10/03-229r1 SAS-1.1 Transport layer retries ladder diagrams
To: T10 Technical Committee From: Jim Jones, Quantum (jim.jones@quantum.com) and Rob Elliott, HP (elliott@hp.com) Date: 11 August 2003 Subject: T10/03-229r1 SAS-1.1 Transport Layer Retries ladder diagrams
Draft Minutes Automation/Drive Interface (ADI) Working Group Ad Hoc Teleconference T10/03-151r0 26 March :00 AM 10:00 AM PST
Draft Minutes Automation/Drive Interface (ADI) Working Group Ad Hoc Teleconference T10/03-151r0 26 March 2003 8:00 AM 10:00 AM PST Conference Call Information: Hosted by: Quantum Toll Free: (800) 668-7083
T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 21 January January 2009 SUBJECT: T10/08-409r5, ADT-2: Internet ADT (iadt)
TO: T10 Membership FROM: Paul A. Suhler, Quantum Corporation DATE: 21 January 200914 January 2009 SUBJECT: T10/08-409r5, ADT-2: Internet ADT (iadt) Revisions T10/07-469: 0 Initial revision (2 November
T10/03-229r0 SAS-1.1 Transport layer retries ladder diagrams
To: T10 Technical Committee From: Jim Jones, Quantum (jim.jones@quantum.com) and Rob Elliott, HP (elliott@hp.com) Date: 25 June 2003 Subject: T10/03-229r0 SAS-1.1 Transport Layer Retries ladder diagrams
Added item 33 and assigned to Paul Entzel Revision 0 Reopened item 1 and tentatively assigned to Michael Banther.
TO: T10 embership FRO: Paul A. Suhler, Quantum Corporation DATE: 6 November 2006 SUBJECT: T10/ 06-060r4, 06-060 Revision 4 Dropped items 8 and 21 Corrected name of state machine in item 24 06-060 Revision
6 June r0 SAM-4 SCSI Initiator Port and Target Port capabilities attributes
6 June 2007 07-263r0 SAM-4 SCSI Initiator Port and Target Port capabilities attributes To: T10 Technical Committee From: Rob Elliott (elliott@hp.com) Date: 6 June 2007 Subject: 07-263r0 SAM-4 SCSI Initiator
12 January r1 SAS2: ST_TTS retransmitted DATA frames
To: T10 Technical Committee From: Bob Sheffield (Robert.L.Sheffield@intel.com) Date: 12 January 2007 Subject: 06-371r1 SAS2: ST_TTS retransmitted DATA frames Revision history Revision 0 (20 July 2006)
Pack Manager Program System Design Document
PACK MANAGER PROGRAM SYSTEM DESIGN DOCUMENT 1 Pack Manager Program System Design Document Latest Revision: 26 March 2014 Prepared by: Naing Htet Abstract This document describes the design of the software
Fault Tolerance. Goals: transparent: mask (i.e., completely recover from) all failures, or predictable: exhibit a well defined failure behavior
Fault Tolerance Causes of failure: process failure machine failure network failure Goals: transparent: mask (i.e., completely recover from) all failures, or predictable: exhibit a well defined failure
iscsi Consortium Error Recovery Test Suite For iscsi Targets
iscsi Consortium Error Recovery Test Suite For iscsi Targets Version 0.2 Last Update: February 19 2004 iscsi Consortium 121 Technology Drive Suite 2 Durham, NH 03824-3525 Research Computing Center Phone:
Fault Tolerance Causes of failure: process failure machine failure network failure Goals: transparent: mask (i.e., completely recover from) all
Fault Tolerance Causes of failure: process failure machine failure network failure Goals: transparent: mask (i.e., completely recover from) all failures or predictable: exhibit a well defined failure behavior
Revisions. Introduction. Proposal
To: INCITS Technical Committee T10 From: Kevin Butt Date: Printed Monday, January 07, 2008 6:31 pm Document: T10/08-025r1 Persistent Reservations - Team Revisions 1. 08-025r0 Initial revision (10 December
The objective. Atomic Commit. The setup. Model. Preserve data consistency for distributed transactions in the presence of failures
The objective Atomic Commit Preserve data consistency for distributed transactions in the presence of failures Model The setup For each distributed transaction T: one coordinator a set of participants
T10/03-186r2 SAS-1.1 Transport layer retries
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) and Jim Jones, Quantum (jim.jones@quantum.com) Date: 28 July 2003 Subject: T10/03-186r1 SAS-1.1 Transport layer retries T10/03-186r2 SAS-1.1
03-186r5 SAS-1.1 Transport layer retries 13 January 2004
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 13 January 2004 Subject: 03-186r5 SAS-1.1 Transport layer retries Revision history Revision 0 (6 May 2003) first revision Revision
03-186r3r3 SAS-1.1 Transport layer retries 25 October 2003
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 25 October 2003 Subject: 03-186r3r3 SAS-1.1 Transport layer retries Revision history Revision 0 (6 May 2003) first revision Revision
DAQ Electronics, Inc 262B Old New Brunswick Road, Piscataway, NJ
DAQ Electronics, Inc 262B Old New Brunswick Road, Piscataway, NJ 08854-3756 DNP3 Server Configuration CallistoView version 5.0A This is a description of the unique DNP configuration dialogs and files in
r5 09 December 2008
08-249 r5 09 December 2008 To: T10 SAS Protocol Working Group From: Brian Day and George Penokie Subject: SAS 2.+ SPL: 08-249 Link Layer Power Management Revision History Revision 0 - Initial draft Revision
All page numbers refer to the printed page number, not the PDF page number.
SPI-3 Revision 10 Letter Ballot Comments 28 October 1999 by Rob Elliott, Compaq Computer Corporation All page numbers refer to the printed page number, not the PDF page number. The first three comments
Revision History Revision 0 (T10/06-225r0): Posted to the T10 web site on 4 May 2006.
To: INCITS T10 Committee From: Matt Ball, Quantum Corporation Date: March 13, 2007 Subject: SSC-3: Key Entry using Encapsulating Security Payload (ESP) Revision History Revision 0 (T10/06-225r0): Posted
Add the following section to REPORT SUPPORTED OPERATION CODES command.
Page 1 of 7 Self Describing Cmd Timouts.fm/05-284r4 November 8, 2006 To: INCITS Technical Committee T10 From: Kevin Butt, IBM Date: November 8, 2006 12:48 pm Document: T10/05-284r4 Subject: SPC-4: Self
Computer Peripherals
Computer Peripherals School of Computer Engineering Nanyang Technological University Singapore These notes are part of a 3rd year undergraduate course called "Computer Peripherals", taught at Nanyang Technological
A can be implemented as a separate process to which transactions send lock and unlock requests The lock manager replies to a lock request by sending a lock grant messages (or a message asking the transaction
03-346r2 SAS-1.1 Pathway recovery priority corrections 3 November 2003
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 3 November 2003 Subject: 03-346r2 SAS-1.1 Pathway recovery priority corrections Revision history Revision 0 (22 October 2003) First
04-372r1 SAM-4 SPC-4 SAS-1.1 I_T NEXUS RESET task management function 13 November 2004
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 13 November 2004 Subject: 04-372r1 SAM-4 SPC-4 SAS-1.1 I_T NEXUS RESET task management function Revision history Revision 0 (5 November
Revisions. Introduction. Proposal
To: INCITS Technical Committee T10 From: Kevin Butt Date: Printed Wednesday, January 23, 2008 10:01 am Document: T10/08-025r3 Persistent Reservations - Team Revisions 1. 08-025r0 Initial revision (10 December
Fault Tolerance. o Basic Concepts o Process Resilience o Reliable Client-Server Communication o Reliable Group Communication. o Distributed Commit
Fault Tolerance o Basic Concepts o Process Resilience o Reliable Client-Server Communication o Reliable Group Communication o Distributed Commit -1 Distributed Commit o A more general problem of atomic
Category: Standards Track July 2004
Network Working Group Request for Comments: 3821 Category: Standards Track M. Rajagopal E. Rodriguez R. Weber July 2004 Fibre Channel Over TCP/IP (FCIP) Status of this Memo This document specifies an Internet
SAM-2 Letter Ballot comment HP 71 expressed a concern long held by the SAM-2/3 editor, to whit:
ENDL TEXAS Date: 2 April 2003 To: T10 Technical Committee From: Ralph O. Weber Subject: Remove ULP and LLP from SAM-3 SAM-2 Letter Ballot comment HP 71 expressed a concern long held by the SAM-2/3 editor,
Revision History Revision 0 (T10/06-225r0): Posted to the T10 web site on 4 May 2006.
To: INCITS T10 Committee From: Matt Ball, Quantum Corporation Date: 27 June 2006 Subject: SSC-3: Using NIST AES Key-Wrap for Key Establishment Revision History Revision 0 (T10/06-225r0): Posted to the
INTERNATIONAL TELECOMMUNICATION UNION. SERIES Q: DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 (DSS 1), DATA LINK LAYER
INTERNATIONAL TELECOMMUNICATION UNION CCITT Q.921 THE INTERNATIONAL TELEGRAPH AND TELEPHONE CONSULTATIVE COMMITTEE (11/1988) SERIES Q: DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 (DSS 1), DATA LINK LAYER
T10/02-230r1. Maxtor Corporation 500 McCarthy Boulevard Milpitas, CA USA
Maxtor Corporation 500 McCarthy Boulevard Milpitas, CA 95035 USA To: Serial Attached SCSI Protocol Working Group From: Mark Evans Phone: 408-894-5310 Email: mark_evans@maxtor.com Date: 08 July 2002 Subject:
MYE017 Distributed Systems. Kostas Magoutis
MYE017 Distributed Systems Kostas Magoutis magoutis@cse.uoi.gr http://www.cse.uoi.gr/~magoutis Message reception vs. delivery The logical organization of a distributed system to distinguish between message
Draft Minutes Ad Hoc Meeting Automation/Drive Interface (ADI) Working Group Portland, Oregon T10/03-041r0 January 14, :00 AM 5:00 PM PST
Draft Minutes Ad Hoc Meeting Automation/Drive Interface (ADI) Working Group Portland, Oregon T10/03-041r0 January 14, 2003 9:00 AM 5:00 PM PST 1. Introductions: Group Intel hosted the meeting. Paul Suhler
Basic concepts in fault tolerance Masking failure by redundancy Process resilience Reliable communication. Distributed commit.
Basic concepts in fault tolerance Masking failure by redundancy Process resilience Reliable communication One-one communication One-many communication Distributed commit Two phase commit Failure recovery
04-372r0 SAM-4 SPC-3 SAS-1.1 I_T NEXUS LOSS task management function 5 November 2004
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 5 November 2004 Subject: 04-372r0 SAM-4 SPC-3 SAS-1.1 I_T NEXUS LOSS task management function Revision history Revision 0 (5 November
Specific Changes Change 1 [modify abstract]: On the ANSI title page, remove the following paragraph from the abstract:
![Specific Changes Change 1 [modify abstract]: On the ANSI title page, remove the following paragraph from the abstract:](/thumbs/87/95283047.jpg "Specific Changes Change 1 [modify abstract]: On the ANSI title page, remove the following paragraph from the abstract:")
ENDL TEXAS Date: 5 January 2003 To: T10 Technical Committee From: Ralph O. Weber Subject: Remove AEN from SPC-3 In November, T10 agreed to remove AER (Asynchronous Event Reporting) from SAM-3. This proposal
Today: Fault Tolerance. Reliable One-One Communication
Today: Fault Tolerance Reliable communication Distributed commit Two phase commit Three phase commit Failure recovery Checkpointing Message logging Lecture 17, page 1 Reliable One-One Communication Issues
17 March r1 SAM-4 SAS-2 QUERY UNIT ATTENTION task management function
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 17 March 2007 Subject: 07-067r1 SAM-4 SAS-2 QUERY UNIT ATTENTION task management function Revision history Revision 0 (13 February
Objective. Performance. Availability. Cost. A good network citizen
Objective Performance Interconnect will meet or exceed current storage needs and enable growth High bandwidth, minimum latency Availability Enable various levels of recovery Cost Reuse whatever available
Gene Milligab, T10 Principal member
X3T10/97-225r20 Seagate Technology Tel: 405-324-3070 10323 West Reno (West Dock) Fax: 405-324-3794 Oklahoma City, OK 73127-9705 gene_milligan@notes.seagate.com P.O. Box 12313 Oklahoma City, OK 73157-2313
To: T10 Membership T10/97-184R4 Subject: Use of Class 2 for Fibre Channel Tapes From: Date: 23-Oct-1997
To: T10 Membership T10/97-184R4 Subject: Use of Class 2 for Fibre Channel Tapes From: Date: 23-Oct-1997 This paper describes the use of the Fibre Channel Class 2 protocol
UNH IOL iscsi CONSORTIUM
UNH IOL iscsi CONSORTIUM Error Recovery Test Suite for iscsi Targets Version 0.2 Technical Document Last Updated January 4, 2007 2006 University of New Hampshire UNH-IOL iscsi Consortium 121 Technology
T10/06-119r0 SAS-2 BREAK_REPLY 28 February 2006
T10/06-119r0 SAS-2 _REPLY 28 February 2006 To: T10 Technical Committee From: Timothy Hoglund, LSI Logic Date: 28 February 2006 Subject: Serial Attached SCSI - 2 (SAS-2) Revision History Revision 0 (28
Table 2 - Data buffer descriptor formats. NO DATA BUFFER DESCRIPTOR PRESENT h 0. DIRECT DATA BUFFER DESCRIPTOR
11 September 2001 T10/01-230r2 Document: T10/01-230r2 Date: 11 September 2001 To: T10 Committee Membership From: Edward A. Gardner, Ophidian Designs Subject: SRP Buffer Descriptor Subclause Rewrite My
T10/05-142r3 SAT - LOG SENSE command and SMART
To: T10 Technical Committee From: Wayne Bellamy (wayne.bellamy@hp.com), Hewlett Packard Date: September 2, 2005 Subject: T10/05-142r3 SAT - LOG SENSE command and SMART Revision History Revision 0 (April
The challenges of non-stable predicates. The challenges of non-stable predicates. The challenges of non-stable predicates
The challenges of non-stable predicates Consider a non-stable predicate Φ encoding, say, a safety property. We want to determine whether Φ holds for our program. The challenges of non-stable predicates
The number in square brackets at the end of each comment description counts all the comments presented in this document.
ENDL TEXAS Date: 4 May 2005 To: T10 Technical Committee From: Ralph O. Weber Subject: Response to T10 Letter Ballot comments on SPC-3 This document contains the responses to the T10 Letter Ballot comments
CS 123: Lecture 12, LANs, and Ethernet. George Varghese. October 24, 2006
CS 123: Lecture 12, LANs, and Ethernet George Varghese October 24, 2006 Selective Reject Modulus failure Example w = 2, Max = 3 0 0 1 3 0 A(1) A(2) 1 0 retransmit A(1) A(2) buffer Case 1 Case 2 reject
ETSF05/ETSF10 Internet Protocols Transport Layer Protocols
ETSF05/ETSF10 Internet Protocols Transport Layer Protocols 2016 Jens Andersson Transport Layer Communication between applications Process-to-process delivery Client/server concept Local host Normally initialiser
Configuration Guide. For Managing EAPs via EAP Controller
Guide For Managing EAPs via EAP Controller 1910012313 REV1.0.0 December 2017 CONTENTS 1 Overview... 1 2 Configuration... 2 2.1 Managing EAPs in the Same Subnet... 2 2.2 Managing EAPs in Different Subnets...
Distributed Systems Fault Tolerance
Distributed Systems Fault Tolerance [] Fault Tolerance. Basic concepts - terminology. Process resilience groups and failure masking 3. Reliable communication reliable client-server communication reliable
TS-3GA (Rel5)v5.1.0 Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface
TS-3GA-24.011(Rel5)v5.1.0 Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface Feb 21,2003 THE TELECOMMUNICATION TECHNOLOGY COMMITTEE TS-3GA-24.011(Rel5)v5.1.0 Point-to-Point
Transport Protocols and TCP
Transport Protocols and TCP Functions Connection establishment and termination Breaking message into packets Error recovery ARQ Flow control Multiplexing, de-multiplexing Transport service is end to end
Point of Care: Login, Sync, Logout, and Quit
Point of Care: Login, Sync, Logout, and Quit Point of Care is a program that allows you to complete assessments, confirm services, and pass medications without having a constant internet connection. You
MSA Event Descriptions Reference Guide
MSA Event Descriptions Reference Guide Abstract This guide is for reference by storage administrators to help troubleshoot storage-system issues. It describes event messages that may be reported during
file:///c:/users/hpguo/dropbox/website/teaching/fall 2017/CS4470/H...
1 of 9 11/26/2017, 11:28 AM Homework 3 solutions 1. A window holds bytes 2001 to 5000. The next byte to be sent is 3001. Draw a figure to show the situation of the window after the following two events:
COPYRIGHT DISCLAIMER TRADEMARK NOTICES PART NUMBER REVISION HISTORY CONTACTING TANDBERG DATA CORPORATION
VXA-320 (VXA-3) SCSI Reference COPYRIGHT DISCLAIMER TRADEMARK NOTICES Copyright 2008 by Tandberg Data Corporation. All rights reserved. This item and the information contained herein are the property of
University of New Hampshire InterOperability Laboratory Gigabit Ethernet Consortium
University of New Hampshire InterOperability Laboratory Gigabit Ethernet Consortium As of July 31 st, 2002 the Gigabit Ethernet Consortium Clause 37 Auto Negotiation Conformance Test Suite Version 1.3
22 March r1 FCP-4 QUERY TASK task management function
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 22 March 2007 Subject: 07-072r1 FCP-4 QUERY TASK task management function Revision history Revision 0 (14 February 2007) First revision
17 March r1 SAM-4 SAS-2 QUERY TASK SET task management function
17 March 2007 07-066r1 SAM-4 SAS-2 QUERY ASK SE task management function o: 10 echnical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 17 March 2007 Subject: 07-066r1 SAM-4 SAS-2 QUERY ASK SE task
PROMISE ARRAY MANAGEMENT ( PAM) FOR FastTrak S150 TX2plus, S150 TX4 and TX4000. User Manual. Version 1.3
PROMISE ARRAY MANAGEMENT ( PAM) FOR FastTrak S150 TX2plus, S150 TX4 and TX4000 User Manual Version 1.3 Promise Array Management Copyright 2003 Promise Technology, Inc. All Rights Reserved. Copyright by
EasyChair Instructions for Authors
EasyChair Instructions for Authors The submission and review of papers for SIGUCCS 2017 will be managed through an online conference paper management system called EasyChair. This system gives you, the
Fault Tolerance. Distributed Systems IT332
Fault Tolerance Distributed Systems IT332 2 Outline Introduction to fault tolerance Reliable Client Server Communication Distributed commit Failure recovery 3 Failures, Due to What? A system is said to
ENDL TEXAS. T10/03-005r0
ENDL TEXAS Date: 5 January 2003 To: T10 Technical Committee From: Ralph O. Weber Subject: Almost since I started editing SAM I have wanted to move anything not directly part of the architecture from SAM
Switch Memory and Configuration
6 Switch Memory and Configuration Contents Overview..................................................... 6-3 Overview of Configuration File Management................... 6-3 Using the CLI To Implement
UE Context Retention
This chapter describes the support of during SCTP Association recovery in the following sections: Feature Summary and Revision History, page 1 Feature Description, page 2 How It Works, page 2 Configuring,
EUROPEAN ETS TELECOMMUNICATION August 1996 STANDARD
EUROPEAN ETS 300 402-3 TELECOMMUNICATION August 1996 STANDARD Source: ETSI TC-SPS Reference: DE/SPS-05030-1 ICS: 33.080, 35.100.20 Key words: ISDN, DSS1, layer 2, D-channel, LAPF Integrated Services Digital
04-075r0 SBC-2 Obsolete more features 27 February 2004
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 27 February 200 Subject: 0-075r0 SBC-2 Obsolete more features Revision history Revision 0 (27 February 200) First revision Related
TCG. TCG Storage Interface Interactions Specification. Specification Version 1.0. January 27, Contacts:
TCG Storage Interface Interactions Specification January 27, 2009 Contacts: storagewg@trustedcomputinggroup.org Copyright TCG 2009 TCG Copyright 2009 Trusted Computing Group, Incorporated. Disclaimer,
UNH IOL iscsi CONSORTIUM
UNH IOL iscsi CONSORTIUM Error Recovery Test Suite for iscsi Targets Version 2.1 Technical Document Last modified January 13, 2010 2006-2010 University of New Hampshire UNH-IOL iscsi Consortium 121 Technology
Class 3 Error Detection and Recovery for Sequential Access Devices Preliminary ANSI T10 Working Document R22
Class 3 Error Detection and Recovery for Sequential Access Devices Preliminary ANSI T10 Working Document 97-189R22 Scope Problems exist in PLDA in detecting and correcting error conditions on sequential
Network Working Group
Network Working Group Request for Comments: 2961 Category: Standards Track L. Berger LabN Consulting, LLC D. Gan Juniper Networks, Inc. G. Swallow Cisco Systems, Inc. P. Pan Juniper Networks, Inc. F. Tommasi
Please follow the steps to configure this Web Smart switch. Step 1: Use a twisted pair cable to connect this switch to your PC.
Web Smart Switch Configure Please follow the steps to configure this Web Smart switch. Step 1: Use a twisted pair cable to connect this switch to your PC. Step 2: Set your PC s IP to 192.168.2.xx. Step
CS 541 Database Systems. Three Phase Commit
CS 541 Database Systems Three Phase Commit 1 Introduction No ACP can eliminate blocking if total failures or total site failures are possible. 2PC may cause blocking even if there is a nontotal site failure
2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold.
T0/06-6 revision 0 Date: March 0, 2006 To: T0 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAM-4: Converting to UML part Overview The current SCSI architecture follows no particular documentation
This amendment A1 modifies the European Telecommunication Standard ETS (1991)
AMENDMENT ETS 300 104 A1 June 1994 Source: ETSI TC-SPS Reference: RE/SPS-05059 ICS: 33.080 Key words: ISDN, ISDN basic access, Layer 3 aspects This amendment A1 modifies the European Telecommunication
78.4 Data Link Layer Capabilities
Draft Amendment to IEEE Std 0.-0 IEEE 0.az Energy Efficient Ethernet Task Force May 0. Data Link Layer Capabilities Additional capabilities and settings are supported using frames based on the IEEE 0.
2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold.
T0/06-6 revision 2 Date: May 22, 2006 To: T0 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAM-4: Converting to UML part Overview The current SCSI architecture follows no particular documentation
Transport Protocols and TCP: Review
Transport Protocols and TCP: Review CSE 6590 Fall 2010 Department of Computer Science & Engineering York University 1 19 September 2010 1 Connection Establishment and Termination 2 2 1 Connection Establishment
Filing the 990-N epostcard for
Filing the 990-N epostcard for 2015-16 This is your chapter s tax return and is not optional. The IRS will revoke the chapter s tax-exempt status and your chapter will have to reorganize with the IRS.
Category: Standards Track February Fault Tolerance for the Label Distribution Protocol (LDP)
Network Working Group A. Farrel, Ed. Request for Comments: 3479 Movaz Networks, Inc. Category: Standards Track February 2003 Fault Tolerance for the Label Distribution Protocol (LDP) Status of this Memo
This user guide covers how existing CSUFEDU Qualtrics account users can migrate their account from the CSUFEDU brand to the Fullerton brand.
Quick Reference Guide Converting Your Qualtrics Account from CSUFEDU This user guide covers how existing CSUFEDU Qualtrics account users can migrate their account from the CSUFEDU brand to the Fullerton
Chapter 8 Fault Tolerance
DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S. TANENBAUM MAARTEN VAN STEEN Chapter 8 Fault Tolerance 1 Fault Tolerance Basic Concepts Being fault tolerant is strongly related to
ETHERNET. Clause 28 Auto-Negotiation State Machine Base Page Exchange Test Suite v5.5. Technical Document. Last Updated: July 22, :11PM
ETHERNET Clause 28 Auto-Negotiation State Machine Base Page Exchange Test Suite v5.5 Technical Document Last Updated: July 22, 2004 6:11PM Ethernet Consortium 121 Technology Drive, Suite 2 oratory Durham,
Note: All CDB formats in this proposal assume that is approved for incorporation prior to or concurrently with this proposal.
ENDL TEXAS Date: 3 July 2008 To: T10 Technical Committee From: Ralph O. Weber Subject: Introduction The SNIA OSD TWG Snapshots Proposal describes the ability to replicate entire partitions in the form
TSG-RAN Meeting #13 TSGRP#13(01) 0595 Beijing, China, 18-21, September, 2001
TSG-RAN Meeting #13 TSGRP#13(01) 0595 Beijing, China, 18-21, September, 2001 Title: Agreed CRs to TS 25.415 Source: TSG-RAN WG3 Agenda item: 8.3.3/8.3.4/9.4.3 RP Tdoc R3 Tdoc Spec CR_Num Rev Release CR_Subject
Fault Tolerance. Distributed Systems. September 2002
Fault Tolerance Distributed Systems September 2002 Basics A component provides services to clients. To provide services, the component may require the services from other components a component may depend
BACnet Protocol Implementation Conformance Statement Automated Logic G5RE
Date: 6/1/2017 Vendor Name: Automated Logic Product Name: G5RE Product Model Number: G5RE Applications Software Version: N/A Firmware Revision: 100.02.2018 BACnet Protocol Revision: 9 Product Description: