Abstract Test Suite for Ethernet in the First Mile Operation, Administration & Maintenance

Transcription

1 Abstract Suite for Ethernet in the First Mile Operation, Administration & Maintenance Editor Company Telephone Isabelle Morency Iometrix isa@iometrix.com Contributors Company Telephone Bob Mandeville Iometrix bob@iometrix.com June nd, 00 Disclaimer The information in this publication is believed to be accurate as of its publication date. Such information is subject to change without notice and Iometrix is not responsible for any errors. Iometrix does not assume any responsibility to update or correct any information in this publication. Notwithstanding anything to the contrary, Iometrix makes no representation or warranty, expressed or implied, concerning the completeness, accuracy, or applicability of any information contained in this publication. No liability of any kind shall be assumed by Iometrix as a result of reliance upon any information contained in this publication. The receipt or any use of this document or its contents does not in any way create by implication or otherwise any express or implied license or right to Iometrix patent, copyright, trademark or trade secret rights which are or may be associated with the ideas, techniques, concepts or expressions contained herein. About Iometrix Iometrix is the networking industry's preeminent testing authority dedicated to developing the rigorous, standardsbased methodologies essential to any meaningful evaluation of advanced enterprise and WAN technologies. Iometrix is the successor to ENL (European Network Laboratories), the independent test lab founded by Bob Mandeville in 99. In more than a decade of active evaluations, ENL earned a well-deserved reputation for innovation, rock-solid methodologies, and hands-on experience with some of the largest networks in the world, including the European Commission, World Health Organization (WHO), and several global financial institutions. Copyright 00 Iometrix Inc. All Rights Reserved. No part of this publication may be reproduced in any form or by any means. Copyright 00 Iometrix Inc. Page

2 Table of Contents INTRODUCTION ABSTRACT STRUCTURE OF DOCUMENT SCOPE DEFINITIONS ABBREVIATIONS REFERENCES COMPLIANCE LEVELS... 9 TESTING METHODOLOGIES CONFORMANCE TESTING...0. PERFORMANCE TESTING INTEROPERABILITY TESTING.... FUNCTIONAL TESTING... 3 TEST BED SCHEMATICS... ETHERNET IN THE FIRST MILE OAM OUTLINE THE OAM SUBLAYER...3. OAM SUBLAYER INTERNAL AND EXTERNAL COMMUNICATIONS OAM PROTOCOL DATA UNITS (OAMPDUS) Information OAMPDUs Event Notification OAMPDUs Variable Request OAMPDUs Variable Response OAMPDUs Loopback Control OAMPDUs Organization Specific OAMPDUs ETHERNET IN THE FIRST MILE OAM REQUIREMENTS AND TEST PROCEDURE SPECIFICATION FORMAT... 9 Table 0: Definition Template ETHERNET IN THE FIRST MILE OAM REQUIREMENTS AND TEST PROCEDURE OAM FUNCTIONAL SPECIFICATIONS... 0 Table : Passive mode limited transmission Variable Request OAMPDUs... 0 Table : Passive mode limited transmission Loopback Control OAMPDUs... 0 Table 3: OAMPDU transmission when local_pdu is set to LF_INFO... Table : OAMPDU transmission when local_pdu is set to RX_INFO... Table 5: OAMPDU transmission when local_pdu is set to INFO... Table 6: OAMPDU transmission when local_pdu is set to INFO... Copyright 00 Iometrix Inc. Page

3 Table 7: OAMPDU transmission when local_pdu is set to ANY - OAM_CTL.request service primitive with one or more Critical Link Event parameters... 3 Table 8: OAMPDU transmission when local_pdu is set to ANY OAMPDU.request service primitive (Information OAMPDU)... 3 Table 9: OAMPDU transmission when local_pdu is set to ANY OAMPDU.request service primitive (Event Notification OAMPDU)... Table 0: OAMPDU transmission when local_pdu is set to ANY OAMPDU.request service primitive (Variable Request OAMPDU)... Table : OAMPDU transmission when local_pdu is set to ANY OAMPDU.request service primitive (Variable Response OAMPDU)... 5 Table : OAMPDU transmission when local_pdu is set to ANY OAMPDU.request service primitive (Loopback Control OAMPDU)... 5 Table 3: OAMPDU transmission when local_pdu is set to ANY OAMPDU.request service primitive (Organization Specific OAMPDU)... 6 Table : OAMPDU Flags field reserved encoding Remote Stable and Remote Evaluating bits... 6 Table 5: OAMPDU Flags field reserved encoding Local Stable and Local Evaluating bits... 7 Table 6: Reserved bits Flags field... 7 Table 7: OAMPDU Code field... 8 Table 8: OAMPDU reception when local_pdu is not set to ANY... 8 Table 9: OAMPDU reception when local_pdu is set to ANY (Information OAMPDUs)... 9 Table 0: OAMPDU reception when local_pdu is set to ANY (Event Notification OAMPDUs)... 9 Table : OAMPDU reception when local_pdu is set to ANY - (Variable Request OAMPDUs) Table : OAMPDU reception when local_pdu is set to ANY (Variable Response OAMPDUs) Table 3: OAMPDU reception when local_pdu is set to ANY (Loopback Control OAMPDUs)... 3 Table : OAMPDU reception when local_pdu is set to ANY (Organization Specific OAMPDUs)... 3 Table 5: OAMPDU reception when local_pdu is set to ANY (Unknown Code field OAMPDUs)... 3 Table 6: Multiplexer transparent pass-through... 3 Table 7: Effect of OAMPDUs on frames already submitted to the subordinate sublayer OAM EVENT NOTIFICATION GENERATION AND RECEPTION... 3 Table 8: Response to Critical events (Information OAMPDU)... 3 Table 9: Response to Critical events (Event Notification OAMPDU)... 3 Table 30: Response to Critical events (Variable Request OAMPDU) Table 3: Response to Critical events (Variable Response OAMPDU) Table 3: Response to Critical events (Loopback Control OAMPDU) Table 33: Response to Critical events (Organization Specific OAMPDU) Copyright 00 Iometrix Inc. Page 3

4 Table 3: Critical Event reception Table 35: Link Event reception OAM OAMPDUS Table 36: OAMPDU tagging Table 37: Minimum size OAMPDU Table 38: Information OAMPDU frame Structure Table 39: Information OAMPDU when local_pdu is set to LF_INFO Table 0: Information OAMPDU when local_pdu is not set to LF_INFO and the remote_state_valid = FALSE... 0 Table : Information OAMPDU when local_pdu is not set to LF_INFO and the remote_state_valid = TRUE... 0 Table : Reserved Information TLV Type values (0x03 to 0xFD)... Table 3: Reserved Information TLV Type value (0xFF)... Table : Event Notification OAMPDU frame Structure... Table 5: Event Notification OAMPDU - Sequence Number... Table 6: Event Notification OAMPDU Events...3 Table 7: Variable Request OAMPDU frame Structure... 3 Table 8: Variable Request OAMPDU Data field... Table 9: Variable Response OAMPDU frame Structure... Table 50: Variable Response OAMPDU Data field... 5 Table 5: Loopback Control OAMPDU frame Structure... 5 Table 5: Loopback Control OAMPDU Data field... 6 Table 53: Reserved OAM remote loopback command value (0x00)... 6 Table 5: Reserved OAM remote loopback command values (0x03 to 0xFF)... 7 Table 55: Organization Specific OAMPDU frame Structure... 7 Table 56: Organization Specific OAMPDU Organizationally Unique Identifier field OAM LOCAL INFORMATION TLVS... 9 Table 57: Local Information TLV structure... 9 Table 58: Local Information TLV OAM Version field... 9 Table 59: Local Information TLV Revision field - Active Device Table 60: Local Information TLV Revision field Passive Device Table 6: Local Information TLV State field - Remote loopback initiation (Enable OAM Remote Loopback Step of )... 5 Table 6: Local Information TLV State field Remote loopback initiation (Enable OAM Remote Loopback Step of )... 5 Table 63: Local Information TLV State field - Remote loopback termination (Disable OAM Remote Loopback Step of )... 5 Table 6: Local Information TLV State field - Remote loopback termination (Disable OAM Remote Loopback Step of )... 5 Table 65: Local Information TLV State field Reception of a Loopback Control OAMPDU (Enable OAM Remote Loopback) Table 66: Local Information TLV State field - Reception of a Loopback Control OAMPDU (Disable OAM Remote Loopback) Table 67: Local Information TLV Transmission of State field Parser Action value equal to 0x Copyright 00 Iometrix Inc. Page

5 Table 68: Reserved bits State field... 5 Table 69: Local Information TLV OAM Configuration field Table 70: Reserved bits OAM Configuration field Table 7: Local Information TLV OAMPDU Configuration field Table 7: Local Information TLV OUI field Table 73: Reserved bits OAMPDU Configuration field Table 7: Local Information TLV Vendor Specific Information field OAM REMOTE INFORMATION TLVS Table 75: Remote Information TLV structure Table 76: Remote Information TLV OAM Version field Table 77: Remote Information TLV Revision field Table 78: Remote Information TLV State field Table 79: Remote Information TLV OAM Configuration field Table 80: Remote Information TLV OAMPDU Configuration field Table 8: Remote Information TLV OUI field... 6 Table 8: Remote Information TLV Vendor Specific Information field OAM ORGANIZATION SPECIFIC INFORMATION TLVS... 6 Table 83: Organization Specific Information TLV structure...6 Table 8: Organization Specific Information TLV OUI field OAM LINK EVENTS TLVS Table 85: Errored Symbol Period Event TLV structure...63 Table 86: Errored Frame Event TLV structure Table 87: Errored Frame Period Event TLV structure... 6 Table 88: Errored Frame Seconds Summary Event TLV structure... 6 Table 89: Organization Specific Event TLV structure Table 90: Organization Specific Event Organizationally Unique Identifier field Table 9: Reserved Link Event TLV Type values (0x05 to 0xFD) Table 9: Reserved Link Event TLV Type value (0xFF) OAM VARIABLE DESCRIPTORS AND CONTAINERS...67 Table 93: Variable Descriptor structure Table 9: Variable Descriptor / Variable Branch / references MIB attributes Table 95: Variable Descriptor / Variable Branch / does not reference MIB actions Table 96: Variable Container structure Table 97: Variable Container / Variable Branch / reference MIB attributes Table 98: Variable Container / Variable Branch /does not reference MIB actions Table 99: Reserved Variable Indication coding value (0x00) Table 00: Reserved Variable Indication coding values (0x0 to 0xF) Table 0: Reserved Attribute Indication coding values (0x5 to 0x3F)... 7 Table 0: Reserved Object Indication coding values (0x5 to 0x5F)... 7 Table 03: Reserved Package Indication coding values (0x65 to 0x7F) OAM ADDITIONAL CONFORMANCE TESTS...73 Table 0: Timing considerations for OAM remote loopback - Enable Table 05: Timing considerations for OAM remote loopback - Disable Copyright 00 Iometrix Inc. Page 5

6 Table 06: Simultaneous OAM remote loopback commands Higher SA DTE 7 Table 07: Simultaneous OAM remote loopback commands Lower SA DTE. 7 Table 08: Response to an OAM remote loopback command from a Passive peer Table 09: OAM TLVs Parsing rules TLV type 0x00 (End of TLV marker) Table 0: OAM TLVs Parsing rules TLV length 0x00 or 0x Table : OAM TLVs Parsing rules TLVs with unknown or unexpected types Table : OAM TLVs Parsing rules TLVs with length/type mismatch Table 3: OAM TLVs Parsing rules TLVs extending beyond the OAMPDU frame size Table : Variable parsing rules Branch field equal to 0x Table 5: Variable parsing rules Branch or Leaf with unknown or unexpected values...78 Table 6: Response to a Variable Request from a Passive peer Table 7: Variable Response sent within one second Table 8: Variable Response with an error indication MIB package Table 9: Variable Response with an error indication MIB object Table 0: Reserved bits ignored on reception Flags field... 8 Table : Reserved bits ignored on reception State field... 8 Table : Reserved bits ignored on reception OAM Configuration field... 8 Table 3: Reserved bits ignored on reception OAMPDU Configuration field 8 Table : Remote Stable and Remote Evaluating bits reserved encoding Table 5: Local Stable and Local Evaluating bits reserved encoding Table 6: Invalid OAMPDUs ignored on reception Destination address... 8 Table 7: Invalid OAMPDUs ignored on reception Length/Type... 8 Table 8: Invalid OAMPDUs ignored on reception Subtype Table 9: OAMPDU frames generation FAULT State Table 30: OAMPDU frames generation ACTIVE_SEND_LOCAL State Table 3: OAMPDU frames generation SEND_LOCAL_REMOTE State Table 3: OAMPDU frames generation SEND_LOCAL_REMOTE_OK State Table 33: OAMPDU frames generation SEND_ANY State Table 3: Maximum size OAMPDU Table 35: Maximum OAMPDU Frames Generation ACTIVE_SEND_LOCAL State...88 Table 36: Maximum OAMPDU frames generation SEND_LOCAL_REMOTE State...89 Table 37: Maximum OAMPDU frames generation SEND_LOCAL_REMOTE_OK State Table 38: Maximum OAMPDU frames generation SEND_ANY State Copyright 00 Iometrix Inc. Page 6

7 Table of Figures Figure : Setup # Figure : Setup # Figure 3: Setup #3 Figure : Relation between the OAM sublayer and the ISO/IEC Open systems Interconnection (OSI) reference model and the IEEE 80.3 CSMA/CD LAN model 3 Figure 5: OAM sublayer internal and external communications Figure 6: Information OAMPDU frame structure 5 Figure 7: Event Notification OAMPDU frame structure 6 Figure 8: Variable Request OAMPDU frame structure 7 Figure 9: Variable Response OAMPDU frame structure 7 Figure 0: Loopback Control OAMPDU frame structure 8 Figure : Organization Specific OAMPDU frame structure 8 Copyright 00 Iometrix Inc. Page 7

8 Introduction. Abstract This document defines the requirements and corresponding test procedures that determine the readiness of a networking device to provide Ethernet in the First Mile, Operation Administration and Maintenance (OAM) functions. OAM provides various data link mechanisms useful for monitoring link operations such as remote fault indication and remote loopback control, that complement higher layers applications. The requirements defined in the revision of this working draft are based on the IEEE Draft P80.3ah/3.3 document. The corresponding test definitions provide vendors, carriers, and laboratories with a common well-known set of criteria to qualify the readiness of a device to support Ethernet in the First Mile OAM mechanisms.. Structure of Document This document is structured as follows: Section : Constitutes the introduction. It describes the abstract, scope, and structure of the document. It also provides definitions, abbreviations, references and compliance levels. Section : Defines conformance, performance, interoperability and functional testing. Section 3: Presents the three test bed schematics. Section : Provides an overview of Ethernet in the First Mile OAM. Section 5: Specifies the format used to create the requirements and test procedures of section 6. Section 6: Describes the requirements and test procedures for Ethernet in the First Mile OAM..3 Scope The scope of this document is to define the requirements and the corresponding test procedures to qualify the ability of a networking device or system, to deliver Ethernet in the First Mile Operation, Administration and Maintenance (OAM) monitoring mechanisms. Implementation specifications are outside the scope of this document. This document may be updated in the future, to reflect new work done by the IEEE, Ethernet in the First Mile task force. Copyright 00 Iometrix Inc. Page 8

9 . Definitions OAM Discovery: Process that detects the presence and configuration of the OAM sublayer in the remote DTE. Operation, Administration and Maintenance (OAM): A group of network support functions that monitor and sustain network segment operation. These activities include, but are not limited to, failure detection, notification, location, and repairs. The OAM functions are intended to eliminate faults and keep a segment in an operational state and support activities required to provide the services of a subscriber access network to users/subscribers..5 Abbreviations DA EFM OAM OAMPDU PICS SA TLV destination address Ethernet in the first mile operation, administration and maintenance operation, administration and maintenance protocol data unit protocol implementation conformance statement source address type length value.6 References IEEE Draft P80.3ah/D3.3 IETF RFC 9.7 Compliance Levels 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 IETF RFC 9. All key words must use upper case, bold text. Copyright 00 Iometrix Inc. Page 9

10 ing Methodologies This document describes the requirements and corresponding test procedures to be used when testing a networking device or system s ability to deliver Ethernet in the First Mile OAM functions. The definitions of the requirements are tightly based on the IEEE Draft P80.3ah/D3.3. Vendors can refer to such requirements and test procedures in the development and commercial cycles of their products and carriers can refer to them to ensure that the devices or systems they select to deploy meet certain well-defined criteria. Various types of criteria can be used to establish the requirements a device must satisfy to deliver OAM functions. This document refers to four such criteria: conformance, performance, interoperability and functionality.. Conformance ing Ethernet in the First Mile OAM conformance testing consists of testing the extent to which a DTE conforms to the IEEE P80.3ah standard. Conformance testing is generally extensive as it consists of testing a DTE against every feature and function defined in the specification. A conformance test suite targets a specific layer. Therefore, a product can meet conformance at one layer but not at another. Conformance testing can also be used whenever an interoperability problem arises between different pieces of equipment, to further explain the nature of the problem. An example of this would be a test of the multiplexer s ability to provide transparent pass-through of frames from the superior sublayer to the subordinate sublayer.. Performance ing EFM, OAM performance testing evaluates an OAM implementation under different traffic and load conditions to see how well it performs. Performance testing consists of measuring parameters that are traffic dependent under well-known traffic conditions. Performance parameters of an implementation are function related. In general, it involves two functions: traffic generation and traffic analysis. For each function, three types of performance criteria can be measured; speed, accuracy and dependability. An example of this would be the error free transmission of frames while the device is in loopback mode for a well-defined period of time. Copyright 00 Iometrix Inc. Page 0

11 .3 Interoperability ing The purpose of Ethernet in the first Mile OAM interoperability testing is to confirm the degree of interoperability of DTEs. Interoperability problems may arise when different equipment from different vendors are interconnected. Users need to have a certain confidence level that the implementations can interoperate with one another. Two situations can be observed which can impact the interoperability between DTEs. The first situations happen when the DTEs implement the same mandatory functions, but differ with regard to the optional ones. The second situation is when the DTEs implement different mandatory functions. The latter may occur due to changes that are introduced from one version to the next of the evolving of the standard itself. Interoperability testing is used to measure the condition under which two or more systems with separate and different implementations will interoperate and produce the expected behavior. It involves testing both the capabilities and the behavior of an implementation in an interconnected environment and checking whether an implementation can interoperate with another implementation. An example of this would be the ability of a device to initiate and go through all the steps of the OAM discovery process while interconnected to a different vendor s device.. Functional ing The OAM functional testing purpose is to have the insurance that the DTE satisfies certain well-defined functional criteria some of which can be safely taken for granted and other which it may be useful to test. Usually, these tests do not have a direct correspondence with the PICS. An example of this would be the ability of a device to ignore OAMPDU frames with an invalid destination address. Conformance, interoperability and functional test results are typically reported as pass or see comments, whereas performance test results are generally reported in terms of frame counts, times and rates. Copyright 00 Iometrix Inc. Page

12 3 Bed Schematics Although some tests may require very specific test bed configurations, most tests defined in this document can be executed on a single device test bed or a system test bed. The three test bed configurations are schematically represented in the following figures TESTER DTE Port A OAM ENABLED Port A Figure : Setup # TESTER Port A Port B OAM ENABLED NO OAM DTE Port A Port B Figure : Setup # TESTER Port A Port B OAM ENABLED OAM ENABLED DTE Port A Port B Figure 3: Setup #3 Copyright 00 Iometrix Inc. Page

13 Ethernet in the First Mile OAM Outline OAM is intended for point-to-point and emulated point-to-point IEEE 80.3ah links. Implementation of OAM functionality is optional and a conformant implementation may implement it for some ports within a system while not implementing it for other ports.. The OAM Sublayer OAM comprises an optional sublayer between a superior sublayer such as MAC client or optional Link Aggregation and a subordinate sublayer such as MAC or optional MAC Control sublayer. The following figure shows the relationship between the OAM sublayer and the ISO/IEC Open systems Interconnection (OSI) reference model and the IEEE 80.3 CSMA/CD LAN model. OSI Reference Model Layers Application Presentation Session Transport Network Data Link Physical LAN CSMA/CD Layers LLC-Logical Link Control or other MAC Client OAM (Optional) MAC Control (Optional) MAC-Media Access Control Figure : Relation between the OAM sublayer and the ISO/IEC Open systems Interconnection (OSI) reference model and the IEEE 80.3 CSMA/CD LAN model. OAM Sublayer Internal and External Communications A superior sublayer such as the MAC client communicates with the OAM sublayer using the standard MAC data service interface. The OAM sublayer communicates with a subordinate sublayer such as the MAC control or MAC using the same standard service interfaces. The OAM sublayer communicates internally using the OAM internal service interface. Copyright 00 Iometrix Inc. Page 3

14 N The following figure shows the usage of interlayer interfaces by the OAM sublayer as well as the major functions within the OAM sublayer and their relationships. OAM client MAC client OAM_CTL.indication OAMPDU.indication MCF:MA_DATA.indication OAM_CTL.request OAMPDU.request MCF:MA_DATA.request 80.3 MAC data Service interface Control MAC client frames OAMPDUs CTL:OAMI.request CTL:OAMI.indication LBF:OAMI.request Loopback frames Multiplexer Parser 80.3 MAC data Service interface MAC:MA_DATA.request MAC:MA_DATA.indication MAC Control (Optional) MAC-Media Access Control Physical Layer Figure 5: OAM sublayer internal and external communications.3 OAM Protocol Data Units (OAMPDUs) OAM information is conveyed in slow protocol frames called OAM Protocol Data Units (OAMPDUs). OAMPDUs contain the appropriate control and status information used to monitor, test and troubleshoot OAM-enabled links. OAMPDUs traverse a single link; MAC clients like bridges or switches do not forward OAMPDUs. There are six types of OAMPDUs that are identified with specific codes. Copyright 00 Iometrix Inc. Page

15 .3. Information OAMPDUs The Information OAMPDUs are generated to communicate local and remote OAM information. The following figure shows the Information OAMPDU frame structure. Octets Fields Fixed Values 6 6 Destination Address Source Address Length/Type 0-80-c Octets 3 Fields Information Type Information Length OAM Version Revision State OAM Configuration OAMPDU Configuration OUI Vendor Specific Info LOCAL INFORMATION Fixed Values 0x0 0x0 0x0 Subtype 0x03 Flags -96 Code Data/Pad FCS INFORMATION OAMPDU 0x00 Information Type Information Length OAM Version Revision State OAM Configuration OAMPDU Configuration 0x0 0x0 0x0 0x0 3 OUI Vendor Specific Info REMOTE INFORMATION 3 x Information Type Information Length OUI Org. Specific Value ORGANIZATION SPECIFIC 0xFE Figure 6: Information OAMPDU frame structure Copyright 00 Iometrix Inc. Page 5

16 .3. Event Notification OAMPDUs The Event Notification OAMPDUs are generated to alert the remote device of link events. The following figure shows the Event Notification OAMPDU frame structure. Octets Fields Fixed Values 6 Destination Address 0-80-c Source Address Length/Type Subtype Flags Code Data/Pad FCS EVENT NOTIFICATION OAMPDU x03 0x0 Octets Event Type Fields Sequence Number SEQUENCE NUMBER Event Length Event Time Stamp Errored Symbol Window Errored Symbol Threshold Errored Symbols Error Running Total Event Running Total ERRORED SYMBOL PERIOD EVENT Event Type Event Length Event Time Stamp Errored Frame Window Errored Frame Threshold Errored Frames Error Running Total Event Running Total ERRORED FRAME EVENT Event Type Event Length Event Time Stamp Errored Frame Window Errored Frame Threshold Errored Frames Error Running Total Event Running Total ERRORED FRAME PERIOD EVENT Event Type Event Length Event Time Stamp Err.Fr.Sec.Sum. Window Err.Fr.Sec.Sum. Threshold Err.Fr.Sec.Summary Error Running Total Event Running Total Fixed Values 0x0 0x8 0x0 0xA 0x03 0xC 0x0 0x ERRORED FRAME SECONDS SUMMARY EVENT Event Type 0xFE Event Length 3 OUI x Organization Specific Value ORGANIZATION SPECIFIC EVENT Figure 7: Event Notification OAMPDU frame structure Copyright 00 Iometrix Inc. Page 6

17 .3.3 Variable Request OAMPDUs The Variable Request OAMPDUs are generated to request one or more specific MIB variables. The following figure shows the Variable Request OAMPDU frame structure. Octets Fields Fixed Values 6 Destination Address 0-80-c Source Address Length/Type Subtype x03-96 Flags Code Data/Pad FCS VARIABLE REQUEST OAMPDU 0x0 Octets Fields Variable Branch Variable Leaf VARIABLE DESCRIPTOR Fixed Values Figure 8: Variable Request OAMPDU frame structure.3. Variable Response OAMPDUs The Variable Response OAMPDUs are generated to return one or more specific MIB variables. The following figure shows the Variable Response OAMPDU frame structure. Octets Fields Fixed Values 6 Destination Address 0-80-c Source Address Length/Type Subtype Flags Code Data/Pad FCS 0x03 0x03 VARIABLE RESPONSE OAMPDU Octets Fields Variable Branch Variable Leaf Variable Width -8 Variable Value VARIABLE CONTAINER Fixed Values 0x0 Figure 9: Variable Response OAMPDU frame structure Copyright 00 Iometrix Inc. Page 7

18 .3.5 Loopback Control OAMPDUs The Loopback Control OAMPDUs are generated to enable or disable OAM remote loopback. The following figure shows the Loopback Control OAMPDU frame structure. Octets Fields Fixed Values 6 Destination Address 0-80-c Source Address Length/Type Subtype x03 Octets Fields Fixed Values Flags Remote Loopback Command 0x0 + Code Data/Pad 0x0 ENABLE REMOTE LOOPBACK COMMAND FCS LOOPBACK CONTROL OAMPDU Remote Loopback Command 0x0 DISABLE REMOTE LOOPBACK COMMAND Figure 0: Loopback Control OAMPDU frame structure.3.6 Organization Specific OAMPDUs The Organization Specific OAMPDUs are generated to communicate Organizationally Unique Identifier and undefined organizational specific information. The following figure shows the Organization Specific OAMPDU frame structure. Octets Fields Fixed Values 6 Destination Address 0-80-c Source Address Length/Type Subtype x03 Octets Fields Fixed Values Flags 3 OUI Code 0xFE -96 Data/Pad FCS ORGANIZATION SPECIFIC OAMPDU ORGANIZATION SPECIFIC Figure : Organization Specific OAMPDU frame structure Copyright 00 Iometrix Inc. Page 8

19 5 Ethernet in the First Mile OAM Requirements and Procedure Specification Format Table 0: Definition Template Name Definition ID Reference Document Type Status Requirement Description Description of DUT/SUT Object Bed Configuration Procedure Units Variables Results Remarks ETHERNET IN THE FIRST MILE OAM REQUIREMENTS AND TEST PROCEDURE Name derived from the reference document A first punctuated alphanumeric string is assigned to each defined requirement and test procedure couple. It is using the following convention: one or two letter; abbreviated DTE OAM Mode three letters; abbreviated Abstract Set document name three to five characters; IEEE P80.3ah/D3.3 PICS Item A second punctuated alphanumeric string, between parentheses is also assigned to each defined requirement and test procedure couple. It is using the following convention: one letter; abbreviated reference document five to six numbers; reference document related sub clause Example: P-ATS-OFS (I ) P: DTE configured in Passive mode ATS: Abstract Suite document OFS: OAM, Functional Specification PICS, Item (I ): IEEE P80.3ah/D3.3, sub clause Reference document name Conformance, Interoperability, Performance or Functional test type Mandatory, Optional or Additional test status A brief description of the requirement that the device must or should satisfy The type of Ethernet in the First Mile Device Under Succinct description of the test purpose Succinct description of the test bed configuration Succinct description of the test procedure with mention of the test stimulus and expected output Specific frame fields values, time units, rates and counts in integer such as milliseconds, frames per second and numbers of frames transmitted or received Description of variables such as frame length, test duration, numbers of interfaces under test Description of the textual, numerical and/or graphical format in which to display test results Description of any particular observations that might affect the test result Copyright 00 Iometrix Inc. Page 9

20 6 Ethernet in the First Mile OAM Requirements and Procedure Note: This section contains a sample of representative tests from each functional area which have been extracted from the OAM Abstract Suite Draft 3.3C. 6. OAM Functional Specifications Table : Passive mode limited transmission Variable Request OAMPDUs Operation, Administration, and Maintenance (OAM) Functional Specifications Name Passive mode limited transmission Variable Request OAMPDUs Definition ID P-ATS-OFS (I ) Reference IEEE Draft P80.3ah/D3.3 Document Type Conformance Status Mandatory (only if the Passive mode feature is supported by the DTE) Requirement A device configured in Passive mode MUST NOT send Variable Request OAMPDUs Description Description of DTE DUT/SUT Object Determine if a device configured in Passive mode sends Variable Request OAMPDUs Bed Configuration Single device test bed Setup # Procedure Initiate a Variable Request from the Passive DTE and use the tester to monitor the transmitted OAMPDUs Units OAMPDU Code field value Variables MIB attribute, MIB package and/or MIB object values Results Pass or see comments Remarks If clause 30 is implemented verify that the aoamvariablerequesttx counter value = 0 Copyright 00 Iometrix Inc. Page 0

21 6. OAM Event Notification Generation and Reception Table 8: Response to Critical events (Information OAMPDU) Name Definition ID Reference Document Type Status Requirement Description Description of DUT/SUT Object Bed Configuration Procedure Units Variables Results Remarks Operation, Administration, and Maintenance (OAM) Event Notification Generation and Reception Response to Critical events (Information OAMPDU) AP-ATS-EV (I ) IEEE Draft P80.3ah/D3.3 Conformance Mandatory The OAM sublayer MUST respond to Critical link events by setting or clearing the appropriate bits within the Flags field on any subsequently generated OAMPDUs of any type DTE Verify that the appropriate bits within the Flags field of the Information OAMPDUs are set/cleared when Critical link events are communicated to the OAM sublayer via the OAM_CTL.request service primitive Single device test bed Setup #3 Simulate the three types of Critical link events (Link fault, Dying gasp and Critical event) and use the tester to monitor the Information OAMPDUs transmitted by the DTE OAMPDU Code field and Flags field values Link fault, Dying gasp and Critical events specific faults Pass or see comments The definitions of the specific faults are implementation specific Copyright 00 Iometrix Inc. Page

22 6.3 OAM OAMPDUs Table 37: Minimum size OAMPDU Name Definition ID Reference Document Type Status Requirement Description Description of DUT/SUT Object Bed Configuration Procedure Units Variables Results Remarks Operation, Administration, and Maintenance (OAM) OAMPDUs Minimum size OAMPDU AP-ATS-PDU3 (I.57..) IEEE Draft P80.3ah/D3.3 Conformance Mandatory The DTE MUST accept at least minframesize OAMPDUs (6 octets in length) DTE Verify that the DTE successfully accepts 6 octets OAMPDUs Single device test bed Setup # Use the tester to send 6 octets OAMPDUs and verify that the DTE accepts them successfully OAMPDUs Code field and Data/Pad field values None Pass or see comments Copyright 00 Iometrix Inc. Page

23 6. OAM Local Information TLVs Table 57: Local Information TLV structure Name Definition ID Reference Document Type Status Requirement Description Description of DUT/SUT Object Bed Configuration Procedure Units Variables Results Remarks Operation, Administration, and Maintenance (OAM) Local Information TLVs Local Information TLV structure AP-ATS-LIT (I ) IEEE Draft P80.3ah/D3.3 Conformance Mandatory Local Information TLV structure MUST contain the following fields (Information Type, Information Length, OAM Version, Revision, State, OAM Configuration, OAMPDU Configuration, OUI & Vendor Specific Information) DTE Verify that all the mandatory fields are present in the Local Information TLV structure Single device test bed Setup # Use the tester to monitor the Information OAMPDUs transmitted by the DTE while it is in the SEND_ANY state OAMPDU Code field and Data/Pad field values None Pass or see comments Copyright 00 Iometrix Inc. Page 3

24 6.5 OAM Remote Information TLVs Table 80: Remote Information TLV OAMPDU Configuration field Operation, Administration, and Maintenance (OAM) Remote Information TLVs Name Remote Information TLV OAMPDU Configuration field Definition ID AP-ATS-RIT (I ) Reference IEEE Draft P80.3ah/D3.3 Document Type Conformance Status Requirement Description Description of DUT/SUT Object Bed Configuration Procedure Units Variables Results Remarks Mandatory The Remote Information TLV OAMPDU Configuration field transmitted by the DTE MUST contain the value of the last received Local Information TLV OAMPDU Configuration field DTE Verify that the Remote Information TLV OAMPDU Configuration field transmitted by the DTE contains the value of the last received Local Information TLV OAMPDU Configuration field Single device test bed Setup # Use the tester to send Information OAMPDUs and to monitor the Information OAMPDUs transmitted by the DTE OAMPDU Code field and Data/Pad field values OAMPDU Configuration field value Pass or see comments Copyright 00 Iometrix Inc. Page

25 6.6 OAM Organization Specific Information TLVs Table 8: Organization Specific Information TLV OUI field Operation, Administration, and Maintenance (OAM) Organization Specific Information TLVs Name Organization Specific Information TLV OUI field Definition ID AP-ATS-OIT (I ) Reference IEEE Draft P80.3ah/D3.3 Document Type Conformance Status Mandatory (only if the Organization Specific Information TLV feature is supported by Requirement Description Description of DUT/SUT Object Bed Configuration Procedure Units Variables Results Remarks the DTE) The Organization Specific Information TLV OUI field within the Information OAMPDUs transmitted by the DTE MUST contain the -bit Organizationally Unique Identifier of the Vendor DTE Verify that the Organization Specific Information TLV OUI field transmitted by the DTE contains the -bit Organizationally Unique Identifier of the Vendor Single device test bed Setup # Use the tester to monitor the Information OAMPDUs transmitted by the DTE during all the testing activities OAMPDU Code field and Data/Pad field values OUI field value Pass or see comments Copyright 00 Iometrix Inc. Page 5

26 6.7 OAM Link Events TLVs Table 85: Errored Symbol Period Event TLV structure Name Definition ID Reference Document Type Status Requirement Description Description of DUT/SUT Object Bed Configuration Procedure Units Variables Results Remarks Operation, Administration, and Maintenance (OAM) Link Events TLVs Errored Symbol Period Event TLV structure AP-ATS-ET (I ) IEEE Draft P80.3ah/D3.3 Conformance Mandatory (only if the Link Events feature is supported by the DTE) The Errored Symbol Period Event TLV structure MUST contain the following fields (Event Type, Event Length, Event Time Stamp, Errored Symbol Window, Errored Symbol Threshold, Errored Symbols, Error Running Total and Event Running Total) DTE Verify that all the mandatory fields are present in the Errored Symbol Period Event TLVs structure Single device test bed Setup # Use the tester to simulate an Errored Symbol Period Event and monitor the Event Notification OAMPDUs transmitted by the DTE OAMPDU Code field and Data/Pad field values Event Time Stamp, Errored Symbol Window, Errored Symbol Threshold, Errored Symbols, Error Running Total and Event Running Total values Pass or see comments Copyright 00 Iometrix Inc. Page 6

27 6.8 OAM Variable Descriptors and Containers Table 93: Variable Descriptor structure Name Definition ID Reference Document Type Status Requirement Description Description of DUT/SUT Object Bed Configuration Procedure Units Variables Results Remarks Operation, Administration, and Maintenance (OAM) Variables Descriptors and Containers Variable Descriptor structure A-ATS-VAR (I.57.6.) IEEE Draft P80.3ah/D3.3 Conformance Mandatory (only if the Variable Retrieval and the Active mode features are supported by the DTE) The Variable Descriptor structure SHALL contain the following fields (Variable Branch and Variable Leaf) DTE Verify that all the mandatory fields are present in the Variable Descriptor structure Single device test bed Setup # Initiate Variable Requests from the DTE and use the tester to monitor the transmitted Variable Request OAMPDUs OAMPDU Code field and Data/Pad field values MIB attribute, MIB package and/or MIB object values Pass or see comments Copyright 00 Iometrix Inc. Page 7

28 6.9 OAM Additional Conformance s Table 0: Timing considerations for OAM remote loopback - Enable Name Definition ID Reference Document Type Status Requirement Description Description of DUT/SUT Object Bed Configuration Procedure Units Variables Results Remarks Operation, Administration, and Maintenance (OAM) Additional Conformance s Timing considerations for OAM remote loopback - Enable AP-ATS-ACT (I ) IEEE Draft P80.3ah/D3.3 Conformance Mandatory (only if the OAM remote loopback feature is supported by the DTE) Within one second of receiving a Loopback Control OAMPDU with the Enable remote loopback command, the DTE MUST set its parameters and send an Information OAMPDU DTE Verify that within one second of receiving a Loopback Control OAMPDU with the Enable remote loopback command, the DTE sets its parameters and sends an Information OAMPDU Single device test bed Setup # Use the tester to send a Loopback Control OAMPDU with the Enable remote loopback command to the DTE and confirm that within one second, the DTE sends back an Information OAMPDU Milliseconds None Pass or see comments Copyright 00 Iometrix Inc. Page 8