ANSI INCITS 286-1997 Information Technology - Abstract Test Suite for FDDI Station Management Conformance Testing (FDDI SMT ATS).pdf

《ANSI INCITS 286-1997 Information Technology - Abstract Test Suite for FDDI Station Management Conformance Testing (FDDI SMT ATS).pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS 286-1997 Information Technology - Abstract Test Suite for FDDI Station Management Conformance Testing (FDDI SMT ATS).pdf（945页珍藏版）》请在麦多课文档分享上搜索。

1、ANSI INCITS 286-1997 (R2002)(formerly ANSI X3.286-1997)for Information Technology Abstract Test Suite for FDDI StationManagement Conformance Testing(FDDI SMT ATS)Approval of an American National Standard requires review by ANSI that therequirements for due process, consensus, and other criteria for

2、approvalhave been met by the standards developer.Consensus is established when, in the judgement of the ANSI Board ofStandards Review, substantial agreement has been reached by directly andmaterially affected interests. Substantial agreement means much more thana simple majority, but not necessarily

3、 unanimity. Consensus requires that allviews and objections be considered, and that a concerted effort be madetowards their resolution.The use of American National Standards is completely voluntary; theirexistence does not in any respect preclude anyone, whether he has approvedthe standards or not,

4、from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumstances give interpretation on any American NationalStandard. Moreover, no person shall have

5、the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the secretariat or sponsor whose name appears on the titlepage of this standard.CAUTION NOTICE:This American N

6、ational Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purchasers of American National Standards mayreceive current information on all standards by ca

7、lling or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican National Standards Institute11 West 42nd, New York, NY 10036Copyright 1998 by Information Technology Industry Council (ITI)All rights reserved.No part of this publication may be reproduced in any

8、form, in an electronic retrieval system or otherwise,without prior written permission of the publisher.Printed in the United States of AmericaCAUTION: The developers of this standard have requested that holders of patents that may be required for theimplementation of the standard disclose such paten

9、ts to the publisher. However, neither the developers nor thepublisher have undertaken a patent search in order to identify which, if any, patents may apply to this standard.As of the date of publication of this standard and following calls for the identification of patents that may be re-quired for

10、the implementation of the standard, no such claims have been made. No further patent search is con-ducted by the developer or publisher in respect to any standard it processes. No representation is made orimplied that licenses are not required to avoid infringement in the use of this standard. Ameri

11、can National Standardfor Information Technology Abstract Test Suite for FDDI StationManagement Conformance Testing(FDDI SMT ATS)ANSIX3.286-1997SecretariatInformation Technology Industry Council (ITI)Approved September 25, 1997American National Standards Institute, Inc.AbstractConformance tests are s

12、pecified herein to test the Station Management (SMT) functions and protocols ofFDDI. FDDI is a set of standards which define a 100 Mbps token ring architecture that uses fiber opticsas the transmission medium over distances of tens of kilometers in extent.iiContentsPageForeword iv1Scope 12Normative

13、references 13Definitions . 24Conventions and abbreviations. 25Timer definition 26Physical Connection Management (PCM) CFM: Configuration Man agement;F: Fail (when used in the verdict columnof the Dynamic Behavior tables);I: Inconclusive (when used in theverdict column of the DynamicBehavior tables);

14、ILS: Idle Line State;IUT: Implementation Under Test;MAC: Media Access Control;MLS: Master Line State;P: Pass (when used in the verdictcolumn of the Dynamic Behaviortables);PCM: Physical Connection Management;PDU: Protocol Data Unit defined in termsof SMT and MAC Frames;PHY: Physical Layer Protocol;P

15、ICS: Protocol Implementation Con-formance Statement;PIXIT: Protocol Implementation eXtraInformation for Testing;TTCN: Tree and Tabular CombinedNotation;TTCN(P): Tree and Tabular C ombined Notationfor PCM QLS: Quiet Line State;ALS: Active Line State;HLS: Halt Line State;ERR: Error;RMT: Ring Managemen

16、t;MIB: Management Information Base.5 Timer definitionA set of timers, as described below, is used inthe test suite, their values must be initializedprior to the beginning of test, unless a defaultvalue is specified.T_REQ: the Target Token Rotation Timer(TTRT) is configured in the IUTs MAC in unitsof

17、 s. This value will be converted to units of 80ns for MAC claim process.T_REQ1: an alternate TTRT configured in the IUTsMAC in units of s. This value will be converted tounits of 80 ns for MAC claim process.T_REQ2: an alternate TTRT configured in theOthers MAC in units of s. This value will be conve

18、rtedto units of 80 ns for MAC claim process.T_Max: the maximum token rotation time in s.D_Max: the maximum ring latency. The defaultvalue is 1773 s.T_Non_Op: time to allow ring recovery to occurbefore duplicate address conditions areexamined. The default value is 1 s.RM_React: maximum for the RMT st

19、ate ma-chine to recognize that transition conditionsexist and to execute the appropriate transition. The default value is 83 ms.T_Jam: time for which Jam Beacon is sent. The default value is 370 ms.T_DBJ: time to start the second Beacon of theDouble Beacon Jam after the first Beacon issent. The defa

20、ult value is 82 ms.T-Direct: time for which a Directed Beacon issent before the Trace function is invoked. Thedefault value is 370 ms.ANSI X3.286-19973T_Stuck: time to allow a Stuck Beacon to besent, followed by the initiation of a Trace. Thedefault value is 8 s.T_Rmode: the maximum time allowable f

21、orRestricted Dialogue on the ring. The defaultvalue is zero seconds for Non-Used RestrictedDialogue.T_Announce: the interval between sendingJam Beacons. The default value is 2500 ms.T_Limit: The rate-limiting interval for the StatusReport Protocol. The default value is 2 s.Topr: Time required for a

22、test operator to initiateoperation on the IUT, for example, triggering NIFrequest frame to be sent from the IUT. This isused in conjunction with the TTCN Implicit Sendevent for test coordina tion. This test suite uses adefault value of 3 minutes.The following are the expiration values of thetimers u

23、sed in PCM test cases. Whenever thename and the value correspond to AmericanNational Standard X3.229, the ANSI referenceis indicated.TB_Min: Minimum Break time for link.Range: TB_Min 4.823 ms withdefault valuesDefault: 5 ms (SMT PCM);TB_Max: Break time before the BS_Flag is set.TB_Max shall be suffi

24、ciently large so that it willnot be set inadvertently by noise gener at ed byan optical bypass switch, which is bounded byMI_Max.Range: TB_Max 30.0 ms with defaultvaluesDefault: 50 ms (SMT PCM);MI_Max: Maximum Optical Bypass mediainterruption time. The range and default valuefor MI_Max is specified

25、in the PMD document.Range: MI_Max 15.0 msDefault: 15 ms (SMT PCM) C_Min: Minimum time required to remain in theConnect State to ensure that the other end hasrecognized Halt Line State.Range: C_Min 1.2 ms with defaultvaluesDefault: 1.6 ms (SMT PCM);C_Second: A timer used to check PCM wait fora change

26、 in the Connect State since it entersConnector State from Break State and has notyet received HLS.Default: 1 s;PC_React: Maximum time for PCM to make astate transition to Break upon receiving QLS.Range: PC_React 3.0 msDefault: 3 ms (SMT PCM);LS_Min: Length of time continuous reception ofILS is requi

27、red to be used by PCM.Range: 25 s LS_Min 0.48 s withdefault valuesDefault: 0.48 s(SMT PCM);LS_Max: Maximum time to reestablish thecorrect line state as specified in the PHY docu-ment.Range: LS_Max 25 sDefault: 25 s (SMT PCM);TL_Min: Minimum time to transmit a PHY linestate before advancing to the Ne

28、xt PCM state.TL-Min is set to twice the time required for linestate recognition(LS_Max).Range: TL_Min 50 s with defaultvaluesDefault: 50 s (SMT PCM);N_Second: A Timer used to check PCM wait toreceive ILS in Next StateDefault: 1 s;LS_Less: A timer which measures the amountof time that it take the IUT

29、 to make a correctLine State transition.Default: 0.24 s;T_Out: Signalling timeout. The minimum timethat a PCM State Machine will remain in a stateawaiting a line state change. When a line statechange is expected and no transition is made inT_Out time, a transition shall be made to theBreak State.Ran

30、ge: T_Out 100 msDefault: 100 ms (SMT PCM);LC_Short: Short Link Confidence Test TimeRange: LC_Short 5*10(4) nsDefault: 50 ms (SMT PCM);LC_Medium: Medium Link Confidence TestTime.Range: LC_Medium 50 *10(LER_Cutoff)nsANSI X3.286-19974Default: 500 ms (SMT PCM);LC_Long: Long Link Confidence Test Time.Ran

31、ge: LC_Long 500 * 10 (LER_ Cutoff)nsDefault: 5 s (SMT PCM);LC_Extended: Extended Link Confidence TestTime.Range: LC_Extended 50 sDefault: 50 s (SMT PCM);T_Next(7): LC_Test, Time for Link ConfidenceTest (SMT PCM);B_Second: A timer used to check when IUTdetects Link Error Rate exceeds the LER_Cutoffth

32、reshold; it enters Break State and transmitsQLS.Default: 1 s;T_Next(9): Time for the optional MAC LocalLoop to prevent deadlock. This allows sufficienttime for MAC recovery process completion andthe exchange of neighbor information frames.Range: T_Next(9) 200 msDefault: 200 ms (SMT PCM).NS_Max: The

33、maximum length of time thatnoise as measured by TNE, is allowed before aconnection is broken down and restarted.Range: 5.8 ms NS_Max 0.7255 msDefault: 1.3 ms (SMT PCM);Trace_Max: Maximum propagation time for aTrace on an FDDI topology. Trace_Max placesa lower bound on the detection time for a non-re

34、covering ring (T_Stuck)Range: Trace_Max 6.001773 s withdefault valuesDefault: 7.0 s6 Physical ConnectionManagement (PCM) when transmission ofthe packet is complete, the tester transmits ILS*/n ?line-state /* check if the current linestate is in a specific state */n ?OTHERWISE /* any line state */n S

35、TART timer-name /* start the timer withpre-specified duration */n ?TIMEOUT timer-name /* test forexpiration for the specified timer */n +test-procedure-name /* call another testprocedure */n GOTO label /* goto another eventline with indicated label */As in many programming languages, a com-ment is a

36、 character string of the following form:/* Text of comment */A label for an event line is denoted by a se-quence of letters ending with a “:“, and ap pearsafter the indentation level number, for example,3 L1:?TIMEOUT C_min.The “!“ Transmit event means that the testerbegins sending the indicated line

37、 state andcontinues sending it until another “!“ operator isencountered.The START timer event may be combined withthe Transmit (!) or Line state check (?) eventlines. Multiple timers may be started on thesame event. For example,1 !QLS START TB_Min, START TB_Max.The event lines are evaluated starting

38、 from thefirst indentation level, 1. There may beseveral event lines at each indentation level. These event lines represent a set of alternativesand the tester must wait for at least one of themto occur before proceeding to the nextindentation level. If multiple events occur at thesame time, the eve

39、nt line appearing firstapplies. A transmit event line (!) is consideredto have occured or completed when thetransmission of the specified line state symbolsis initiated. A line state check event (?) issatisfied when the current line state matches thespecified state.When an event line is satisfied, t

40、he testermoves on to the next indentation level followingthat event line. If there is no higher level eventline, then the test is complete. If a completedANSI X3.286-19976event line contains a verdict specification, thetest is also considered completed, even if thereis a higher indentation level eve

41、nt line following.The event lines, with the exception of GOTO,SEND and Tree Attachment Event, may assignone of these verdicts: PASS, FAIL, orINCONCLUSIVE.A GOTO event can only specify the labels ap-pearing on the first line of an indentation levelthat is lower or equal to the current in dentationlev

42、el.An event line that invokes another procedure isconsidered not satisfied if none of the first levelevent lines in that procedure have occured.Note that PCM is intended to operate in verynoisy environments (perhaps as bad as a BERof 10 2 and does not generally react to briefnoise events. We do not

43、simulate noise in ourPCM tests except for the Link Quality Tests;rather we expect that the IUT and the testertransmit nothing but clean line states withoutany errors. If the IUT transmits NLS or LSU it isalways grounds for failure.“TTCN(P) does not use the normal TTCN Con-straints. This is because t

44、he Constraints sectionof TTCN uses PDUs rather than Line States todefine Con strai nts.An example illustrates the TTCN(P) notation.This example is the test case To_Next specifiedin 6.2.1.5:Procedure:1+Start_To_Connect2 !HLS Start C_Min3 A:?Timeout C_Min /*Comment*/4 B:?HLS5 Goto B4 ?ILS Pass4 ?Other

45、wise Fail(2)3 ?HLS4 Goto A3 ?Otherwise Fail(1)In To_Next the procedure Start_To_Connect isattached by the first statement:1+Start_To_Connect, which is specified in6.3.2, is:Procedure:1!QLS Start TB_Min2 ?Timeout TB_Min3 A:?QLS4 Goto A3 ?HLS /*Comment*/3 ?Otherwise InconclusiveThe key to understandin

46、g the attachment is thatthe attaching test is attached to each of theterminal leaves of the attached routine. Aterminal leaf is any statement other than aGOTO that has no lower layer and is notqualified with Pass, Fail or Inconclusive verdict.In Start_To_Connect there is one terminal leaf:3 ?HLSEach

47、 test has a specific purpose. The purposeof To_Next is to verify that the IUT remains inthe Connect State for at least C_Min beforegoing to the Next State. Start_To_Connect isused simply to bring the IUT to the ConnectState. Therefore it is a simple routine to prog-ress a correct IUT to the Connect

48、State anddoes not attempt to test all the requirements ofPCM to get to the Connect State; these aretested elsewhere in an incremental fashion.The first statement of Start_To_Connect, andthe only statement at level 1 is:1!QLS Start TB_MinThis statement causes the tester to transmitQLS and to start th

49、e TB_Min timer.Control falls to the next statement at level 2:2 ?Timeout TB_MinThis statement causes the tester to wait, stillsending QLS, until the timer TB_Min expires,since there is no alternative at this level. Thisshould cause the IUT to go to the Break State.There are three alternatives at level 3:3 A:?QLS.3 ?HLS3 ?Otherwise InconclusiveAlternatives at the same level are evaluated inorder and then the evaluation is repeated u