CN101764723A - Interoperability testing method for multicast listener discovery protocol under IPv6 - Google Patents

Abstract

The present invention discloses an interoperability testing method for a multicast listener discovery protocol under IPv6, which belongs to the technical field of network communication protocols. The interoperability testing method comprises the following steps of: environment setting for a testing system; multicast listener discovery tests of nodes; a multicast listener discovery test of a router; and test result generation. The multicast listener discovery test of nodes consists of multicast listener discovery subtests for nodes, and if all the subtests pass, the multicast listener discovery test of nodes passes. The multicast listener discovery test of a router consists of multicast listener discovery subtests for the router, and if the subtests pass, the multicast listener discovery test passes. A user can identify whether a device in a network supports the IPV6 multicast listener discovery protocol by means of the interoperability testing method.

Description

The interoperability testing method of multicast listener discovery protocol under a kind of IPv6

Technical field

The invention belongs to the network communication protocol technical field, relate in particular to the interoperability testing method of multicast listener discovery protocol under a kind of IPv6.

Background technology

MLD is the abbreviation of Multicast Listener Discovery Protocol (multicast listener discovery agreement), it is used for IPv6 (Internet Protocol Version 6, IP network agreement 6.0 editions) router and finds multicast listener on its directly connected subnet.Multicast listener (Multicast Listener) is those host nodes of wishing receiving multicast data.

Router is by the MLD agreement, can understand the listener whether the IPv6 multicast group is arranged on oneself the directly connected subnet, and does respective record at lane database.Simultaneously, router is also safeguarded the timer information relevant with these IPv6 multicast address.

The MLD router uses IPv6 cast link local address to send the MLD message as source address.MLD uses ICMPv6 (Internet Control Message Protocol for IPv6 is at the Internet Internet Control Message Protocol of IPv6) type of message.All MLD messages are limited on the link-local, and jumping figure is 1.

Summary of the invention

The objective of the invention is to, the interoperability testing method of multicast listener discovery protocol under a kind of IPv6 is provided, method of testing is by being installed in the test script software in the test macro, the equipment of supporting the IPv6 multicast listener discovery protocol being carried out the interoperability property testing.

Technical scheme is that the interoperability testing method of multicast listener discovery protocol under a kind of IPv6 is characterized in that described method of testing comprises the following steps:

Step 1: test system environment setting;

Step 2: the multicast listener discovery test of node;

Step 3: the multicast listener discovery test of router;

Step 4: generate test result.

The multicast listener discovery test of described node is made up of the test of node multicast listener discovery, comprising:

1) receives the peak response time-delay test that timer is set to 0 general polling request;

2) receive the peak response time-delay test that timer is set to non-0 general polling request and sends report;

3) receive the peak response time-delay test that timer is set to 0 certain multicast address query requests;

4) receive the peak response time-delay test that timer is set to non-0 certain multicast address query requests;

5) receive effective query messages test that should not have numerical value;

6) receive invalid Query Information test;

7) transmission report message test;

8) receive the report message test that should not have numerical value;

9) time-delay of the peak response in report message test;

10) receive the test of report;

11) report that is transmitted as request is tested;

12) all node tests of link range;

13) transmit the test of end;

14) node state conversion-idle detectaphone test;

15) node state conversion-time-delay detectaphone test;

If the test of described node multicast listener discovery takes to automatically perform mode, then according to above-mentioned 1)-15) order carry out, if do not take to automatically perform mode, then carry out according to random order;

The test of described node multicast listener discovery is all passed through, and then the test of the multicast listener discovery of described node is passed through, otherwise the multicast listener discovery test of described node is not passed through.

The multicast listener discovery test of described router is made up of the test of router multicast listener discovery, comprising:

1) the transmission test of initialization and general inquiry;

2) send the test of inquiry;

3) receive the invalid message test of finishing;

4) receive the report message test that should not have numerical value;

5) receive invalid query messages test;

6) receive the invalid query messages test that should not have numerical value;

7) receive invalid report message test;

8) receive the report message test that should not have numerical value;

9) other inquiries present the introns test;

10) multicast listener introns test;

11) query State conversion test;

12) non-query State conversion test;

13) there is not listener's query State conversion test on the scene;

14) listener's query State conversion test on the scene;

15) query State conversion of checking the listener is tested;

16) no listener non-query State conversion test on the scene;

17) listener's non-query State conversion test on the scene;

18) non-query State conversion of checking the listener is tested;

19) non-inquiry finishes the reception first son test of message;

20) non-inquiry finishes the reception second son test of message;

21) inquiry transfers the test of non-inquiry's to when checking the listener;

If the test of described router multicast listener discovery takes to automatically perform mode, then according to above-mentioned 1)-21) order carry out, if do not take to automatically perform mode, then carry out according to random order;

The test of described router multicast listener discovery is all passed through, and then the test of the multicast listener discovery of described router is passed through, otherwise the multicast listener discovery test of described router is not passed through.

Described generation test result is specifically: the collection analysis message is also exported WEB form test result, comprises numbering, project, result, daily record script, grouping.

Effect of the present invention is by method of testing provided by the invention, can know whether the equipment in the network supports the IPv6 multicast listener discovery protocol, and then whether decision can send multicast packet by the equipment in network.

Description of drawings

Fig. 1 is the interoperability testing method flow chart of multicast listener discovery protocol under the IPv6 provided by the invention;

Fig. 2 is the interoperability testing method first kind test environment figure of multicast listener discovery protocol under the IPv6 provided by the invention;

Fig. 3 is the interoperability testing method second class testing environment map of multicast listener discovery protocol under the IPv6 provided by the invention;

Fig. 4 is interoperability testing method the 3rd class testing environment map of multicast listener discovery protocol under the IPv6 provided by the invention;

Fig. 5 is interoperability testing method the 4th class testing environment map of multicast listener discovery protocol under the IPv6 provided by the invention;

Fig. 6 is the interoperability testing method test result schematic diagram of multicast listener discovery protocol under the IPv6 provided by the invention.

Embodiment

Below in conjunction with accompanying drawing, preferred embodiment is elaborated.Should be emphasized that following explanation only is exemplary, rather than in order to limit the scope of the invention and to use.

The interoperability testing method of multicast listener discovery protocol under a kind of IPv6 provided by the invention by being installed in installation testing script software in the test macro, carries out uniformity test to the equipment of supporting the IPv6 multicast listener discovery protocol.Tested equipment is the network equipment with IPv6 multicast listener discovery protocol function, and test environment comprises four kinds of test environments of Fig. 2-Fig. 5.

Fig. 1 is the interoperability testing method flow chart of multicast listener discovery protocol under the IPv6 provided by the invention.Among Fig. 1, method of testing provided by the invention comprises:

Step 101: test system environment setting.

Step 102: the multicast listener discovery test of node.

The multicast listener discovery test of node is made up of the test of node multicast listener discovery, comprising:

1) receive the peak response time-delay test that timer is set to 0 general polling request, its concrete test process is:

Test setting: Fig. 2 is the method for testing first kind test environment figure of multicast listener discovery protocol under the IPv6 provided by the invention, sets test environment according to Fig. 2.Wherein in Fig. 2, equipment under test 201, test router 202 link to each other by certain network link 203, network link 203 can be various Ethernet connected modes, test router 202 is being connected on the network by network link 203, and test router 202 has on the numerical value IPv6 source address littler than equipment under test 201.

Test specifically:

Part 1, a multicast group peak response time-delay=0;

Step 1: configuration equipment under test 201 adds multicast group FF1E::1:3;

Step 2: peak response time-delay of test router 202 transmissions is 0 general query requests on network link 203;

Step 3: observe equipment under test 201 sends this grouping on network link 203 situation;

Part 2, a plurality of multicast group peak response time-delay=0;

Step 4: configuration equipment under test 201 joins multicast group FF1E::1:3 and multicast group FF1E::1:4;

Step 5: on network link 203, peak response time-delay of configuration testing router two 02 transmission is 0 general query requests;

Step 6: observe equipment under test 201 sends this grouping on network link 203 situation.

Observed result:

Part 1 result requires: require the request response (in 1 second) that equipment under test 201 should send network link 202 at once in the step 3, the form of response is to send the form of report to IPv6 destination address and multicast listener discovery protocol address by multicast group FF1E::1:3.

Part 2 result requires: require in the step 6, the request response (in 1 second) that equipment under test 201 should be at once send network link 202, the form of response are to send a report and send another report to multicast group FF1E::1:4 simultaneously to multicast group FF1E::1:3 for IPv6 destination address and multicast listener discovery protocol.

Meet the requirement as a result of above-mentioned part 1 and part 2, then receive the peak response time-delay test that timer is set to 0 general polling request and pass through.

2) receive the peak response time-delay test that timer is set to non-0 general polling request and sends report.

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Part 1: peak response time-delay=1000;

Step 1: configuration equipment under test 201 adds multicast group FF1E::1:3;

Step 2: configuration equipment under test 201 adds multicast group FF1E::1:4;

Step 3: on network link 203, peak response time-delay of test router 202 transmissions is 1000 general query requests;

Step 4: observe equipment under test 201 sends this grouping on network link 203 situation.

Part 2: peak response was delayed time less than remaining time;

Step 5: equipment under test 201 should join multicast group FF1E::1:3;

Step 6: on network link 203, peak response time-delay of configuration testing router two 02 transmission is 2000 general polling request;

Step 7: on network link 203, peak response time-delay of configuration testing router two 02 transmission is 1000 general polling request;

Step 8: observe equipment under test 201 sends this grouping on network link 203 situation;

The 3rd part: peak response was delayed time greater than remaining time;

Step 9: equipment under test 201 should join multicast group FF1E::1:3;

Step 10: on network link 203, peak response time-delay of configuration testing router two 02 transmission is 1000 general polling request;

Step 11: on network link 203, peak response time-delay of configuration testing router two 02 transmission is 2000 general polling request;

Step 12: observe equipment under test 201 sends this grouping on network link 203 situation.

Observed result:

The 4th step results requires: the request response (in 100 milliseconds of clocks) that equipment under test 201 should send test router 202 at once, the form of response are to send a report and send another report to multicast group FF1E::1:4 simultaneously to multicast group FF1E::1:3 for IPv6 destination address and multicast listener discovery protocol;

The 6th step results requires: equipment under test 201 should be 0～2000 millisecond for the timer time range of FF1E::1:3 multicast group setting oneself;

The 7th step results requires: when equipment under test 201 should also have unnecessary 1000 milliseconds in the timer time of FF1E::1:3 multicast group, the timer time of resetting equipment under test 201 was 0～2000 millisecond;

The 8th step results requires: equipment under test 201 should send to report of multicast group FF1E::1:3 in step 6 is received 1000 milliseconds of general polling request.

The 10th step results requires: equipment under test 201 should send to the FF1E::1:3 multicast group to the timer value of oneself in 0～1000 millisecond;

The 11st step results requires: because the remaining timer time less than maximum response time (2000 milliseconds), equipment under test 201 should not reset the timer of oneself;

The 12nd step results requires: require the request response (in 1 second) that equipment under test 201 should send test router 202 at once in the step 3, the form of response is to send the form of report to IPv6 destination address and multicast listener discovery protocol address by multicast group FF1E::1:3.

Meet above-mentioned observed result requirement, then receive timer and be set to non-0 general polling request and send the peak response time-delay test of reporting pass through.

3) receive the peak response time-delay test that timer is set to 0 certain multicast address query requests.

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Part 1: peak response time-delay=0;

Step 1: configuration equipment under test 201 adds multicast group FF1E::1:3;

Step 2: on network link 203, peak response time-delay of test router 202 transmissions is 0 general query requests;

Step 3: observe equipment under test 201 transmits grouping on network link 203 situation;

Part 2: a plurality of multicast group peak response time-delays=0;

Step 4: configuration equipment under test 201 adds multicast group FF1E::1:3 and FF1E::1:4;

Step 5: on network link 203, peak response time-delay of configuration testing router two 02 transmission is 0 spy

Decide multicast address FF1E::1:3 query requests;

Step 6: observe equipment under test 201 transmits grouping on network link 203 situation;

Step 7: on network link 203, peak response time-delay of configuration testing router two 02 transmission is 0 certain multicast address FF1E::1:3 query requests;

Step 8: observe equipment under test 201 transmits grouping on network link 203 situation;

The 3rd part:

Step 9: do not dispose equipment under test 201 and add multicast group FF1E::1:3;

Step 10: on network link 203, peak response time-delay of configuration testing router two 02 transmission is 0 certain multicast address FF1E::1:3 query requests;

Step 11: observe equipment under test 201 transmits grouping on network link 203203 situation.

Observed result:

The 3rd step results requires: the request response (in 1 second) that equipment under test 201 should send test router 202 at once, the form of response are for IPv6 destination address and multicast listener discovery protocol and to multicast group FF1E::1:3;

The 6th step results requires: the request response (in 1 second) that equipment under test 201 should send test router 202 at once, the form of response are for IPv6 destination address and multicast listener discovery protocol and to multicast group FF1E::1:3;

The 8th step results requires: the request response (in 1 second) that equipment under test 201 should send test router 202 at once, the form of response are for IPv6 destination address and multicast listener discovery protocol and to multicast group FF1E::1:4;

The 13rd step results requires: the request response that equipment under test 201 should not send test router 202 does not promptly send message to IPv6 destination address and multicast listener discovery protocol to multicast group FF1E::1:3;

Meet above-mentioned observed result requirement, then receive the peak response time-delay test that timer is set to 0 certain multicast address query requests and pass through.

4) receive the peak response time-delay test that timer is set to non-0 certain multicast address query requests.

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Part 1: peak response time-delay=1000;

Step 1: configuration equipment under test 201 adds multicast group FF1E::1:3;

Step 2: configuration equipment under test 201 adds multicast group FF1E::1:4;

Step 3: on network link 203, peak response time-delay of test router 202 transmissions is 1000 general query requests;

Step 4: observe equipment under test 201 sends this grouping on network link 203 situation;

Part 2: peak response was delayed time less than remaining time;

Step 5: equipment under test 201 should join multicast group FF1E::1:3;

Step 6: on network link 203, peak response time-delay of configuration testing router two 02 transmission is 2000 general polling request;

Step 7: on network link 203, peak response time-delay of configuration testing router two 02 transmission is 1000 general polling request;

Step 8: observe equipment under test 201 sends this grouping on network link 203 situation;

The 3rd part: peak response was delayed time greater than remaining time;

Step 9: equipment under test 201 should join multicast group FF1E::1:3;

Step 10: on network link 203, peak response time-delay of configuration testing router two 02 transmission is 1000 general polling request;

Step 11: on network link 203, peak response time-delay of configuration testing router two 02 transmission is 2000 general polling request;

Step 12: observe equipment under test 201 sends this grouping on network link 203 situation;

Observed result:

The 4th step results requires: the request response (in 100 milliseconds of clocks) that equipment under test 201 should send test router 202 at once, the form of response are to send a report and send another report to multicast group FF1E::1:4 simultaneously to multicast group FF1E::1:3 for IPv6 destination address and multicast listener discovery protocol;

The 6th step results requires: equipment under test 201 should be 0～2000 millisecond for the timer time range of FF1E::1:3 multicast group setting oneself;

The 7th step results requires: when equipment under test 201 should also have unnecessary 1000 milliseconds in the timer time of FF1E::1:3 multicast group, the timer time of resetting equipment under test 201 was 0～2000 millisecond;

The 8th step results requires: equipment under test 201 should send to report of multicast group FF1E::1:3 in step 6 is received 1000 milliseconds of general polling request;

The 10th step results requires: equipment under test 201 should send to the FF1E::1:3 multicast group to the timer value of oneself in 0～1000 millisecond;

The 11st step results requires: because the remaining timer time less than maximum response time (2000 milliseconds), equipment under test 201 should not reset the timer of oneself;

The 12nd step results requires: require in the step 3, the request response (in 1 second) that equipment under test 201 should send test router 202 at once, the form of response is to send the form of report to IPv6 destination address and multicast listener discovery protocol address by multicast group FF1E::1:3.

Meet above-mentioned observed result requirement, then receive the peak response time-delay test that timer is set to non-0 certain multicast address query requests and pass through.

5) receive effective query messages test that should not have numerical value.

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Part 1: the general inquiry of code domain;

Step 1: the configuration equipment under test adds multicast group FF1E::1:3;

Step 2: on link 0, test router sends the query messages that a general code domain comprises one 100 numerical value;

Step 3: observe by the grouping that on link 0, is sent by equipment under test;

Part 2: the certain multicast address inspection of code domain;

Step 4: the configuration equipment under test adds multicast group FF1E::1:3;

Step 5: on link 0, test router sends a certain multicast address FF1E::1:3 and comprises the query requests that code domain is 100 numerical value;

Step 6: observe by the grouping that on link 0, is sent by equipment under test;

Step 7: the configuration equipment under test adds multicast group FF1E::1:3;

Step 8: on link 0, test router sends a certain multicast address FF1E::1:3 and comprises the query requests that code domain is 30 numerical value;

Step 9: observe by the grouping that on link 0, is sent by equipment under test;

The 3rd part: the general inquiry that keeps the territory;

Step 10: the configuration equipment under test adds multicast group FF1E::1:3;

Step 11: on link 0, test router 1 sends a certain multicast address FF1E::1:3 and comprises and keep the query requests that thresholding is 30 numerical value;

Step 12: observe by the grouping that on link 0, is sent by equipment under test;

Step 13: the configuration equipment under test adds multicast group FF1E::1:3;

Step 14: on link 0, the length that certain multicast address FF1E::1:3 of test router 1 transmission comprises information is 32 eight hyte query messages;

Step 15: observe by the grouping that on link 0, is sent by equipment under test;

Step 16: the configuration equipment under test adds multicast group FF1E::1:3;

Step 17: on link 0, the length that certain multicast address FF1E::1:3 of test router 1 transmission comprises information is 32 eight hyte query messages;

Step 18: observe by the grouping that on link 0, is sent by equipment under test.

Observed result:

3rd, 6,9,12,15 and 18 step results require: equipment under test should accept request, and ignores and does not wish numerical value and be report of FF1E::1:3 multicast group transmission.

Meet above-mentioned observed result requirement, then receive effective query messages test that should not have numerical value and pass through.

6) receive invalid Query Information test.

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Part 1: invalid parity check in the general inquiry information;

Step 1: the configuration equipment under test adds multicast group FF1E::1:3;

Step 2: on link 0, test router 1 sends a generality request that has nonvalid parity check;

Step 3: the situation of observing equipment under test transmission grouping on link 0;

Part 2: invalid parity check in the certain multicast address

Step 4: the configuration equipment under test adds multicast group FF1E::1:3;

Step 5: on link 0, test router 1 to the transmission of certain multicast address FF1E::1:3 a query requests that has invalid parity check;

Step 6: the situation of observing equipment under test transmission grouping on link 0;

The 3rd part: the global source address in the general inquiry information;

Step 7: the configuration equipment under test adds multicast group FF1E::1:3;

Step 8: on link 0, test router 1 has sent a generality request that has test router 1 global address as the IPv6 source address;

Step 9: the situation of observing equipment under test transmission grouping on link 0;

The 4th part: the global source address in the specific multicast inquire address;

Step 10: the configuration equipment under test adds multicast group FF1E::1:3;

Step 11: on link 0, test router 1 sends the particular multicast group request to FF1E::1:3 and test router 1 global address as the IPv6 source address;

Step 12: the situation of observing equipment under test transmission grouping on link 0;

The 5th part: length is less than 24 8 hytes in the general inquiry information;

Step 13: the configuration equipment under test adds multicast group FF1E::1:3;

Step 14: on link 0, test router 1 sends the general query requests that length is 20 eight hytes;

Step 15: observe the grouping that sends by equipment under test on the link;

The 6th part: length is less than 24 8 hytes in the specific multicast inquire address;

Step 16: the configuration equipment under test adds multicast group FF1E::1:3;

Step 17: on link 0, test router 1 sends the query requests that a particular group FF1E::1:3 has 20 8 hyte length;

Step 18: the situation of observing equipment under test transmission grouping on link 0

The 7th part: in the specific multicast inquire address at the unicast address in multicast address territory;

Step 19: the configuration equipment under test adds multicast group FF1E::1:3;

Step 20: on link 0, test router 1 sends the query requests of a particular group FF1E::1:3 for the test router link local address;

Step 21: observe the grouping that sends by equipment under test on the link;

Observed result:

The 4th step results requires:

Meet whole requirements as a result of above-mentioned observation step 1～step 21, receive that then the test of invalid Query Information passes through.

7) transmission report message test.

Test setting:, test environment is set according to shown in Figure 3.Wherein, in Fig. 3, equipment under test 301, test router 302 and test macro 304 are to link to each other by certain network link 303, and network link 303 can be various Ethernet connected modes, 302 are being connected on the network by 303, and 302 have on the numerical value IPv6 source address littler than 301.

Test process:

Step 1: the configuration equipment under test adds multicast group FF1E::1:3;

Step 2: on link 0, test router 1 is 2000 milliseconds Query Information immediately to peak response time-delay of FF1E::1:3 transmission;

Step 3: observe by the grouping that on link 0, is sent by equipment under test.

Observed result:

The 3rd step results requires: equipment under test should send a report information, and having multicast address is that FF1E::1:3 is to multicast group address FF1E::1:3; Report information can not surpass 24 8 hytes.

Meet above-mentioned observed result requirement, then transmit the test of report message and pass through.

8) receive the report message test that should not have numerical value.

Test setting: the set-up mode that sets test environment (with 7 in the step 102) according to Fig. 3).

Test process:

Part 1: code domain test;

Step 1: configuration equipment under test 301 adds multicast group FF1E::1:3;

Step 2: on network link 303, test router 302 sends a certain multicast address request for the FF1E::1:3 address;

Step 3: on network link 303, test router 302 is that 100 FF1E::1:3 address sends a certain multicast address request for comprising the code thresholding;

Step 4: observe by the grouping that on network link 303, is sent by equipment under test 301;

Part 2: keep domain test;

Step 5: configuration equipment under test 301 adds multicast group FF1E::1:3;

Step 6: on network link 303, test router 302 sends a certain multicast address request for the FF1E::1:3 address;

Step 7: on network link 303, test router 302 is that 30 FF1E::1:3 address sends a certain multicast address request for comprising the code thresholding;

Step 8: observe by the grouping that on network link 303, is sent by equipment under test 301;

The 3rd part: message-length is greater than 24 eight hytes

Step 9: configuration equipment under test 301 adds multicast group FF1E::1:3;

Step 10: on network link 303, test router 302 sends a certain multicast address request for the FF1E::1:3 address;

Step 11: on network link 303, test router 302 transmits the report information that length is 32 eight hytes to FF1E::1:3 immediately;

Step 12: observe the grouping that on network link 303, is sent by equipment under test 301.

Observed result:

4th, 8 and 12 step results require: equipment under test should accept request, and ignores and does not wish that numerical value can't send report for the FF1E::1:3 multicast group.

Meet above-mentioned observed result requirement, then receive the report message test that should not have numerical value and pass through.

9) time-delay of the peak response in report message test.

Test setting: the set-up mode that sets test environment (with 7 in the step 102) according to Fig. 3).

Test process:

Step 1: configuration equipment under test 301 adds multicast group FF1E::1:3;

Step 2: on network link 303, test router 302 is 2000 milliseconds Query Information immediately to peak response time-delay of FF1E::1:3 transmission;

Step 3: on network link 303, test router 302 is 500 milliseconds Query Information immediately to peak response time-delay of FF1E::1:3 transmission;

Step 4: observe by the grouping that on link 0, is sent by equipment under test.

Observed result:

The 4th step results requires: it is 500 response that equipment under test should be ignored the maximum delay of sending from test router 302, be sure of that equipment under test can not be reset at 0 to 500 FF1E::1:3 timer.In fact equipment under test 301 should stop counter and no longer send report from the response of test router 302, because test node has been set up one.

Meet above-mentioned observed result requirement, then the test of the time-delay of the peak response in report message is passed through.

10) receive the test of report.

Test setting: the set-up mode that sets test environment (with 7 in the step 102) according to Fig. 3).

Test process:

Part 1: do not have the report of link local address;

Step 1: configuration equipment under test 301 adds multicast group FF1E::1:3;

Step 2: on network link 303, test router 302 sends a certain multicast address query requests for FF1E::1:3;

Step 3: on network link 303, test router 302 sends the report of multicast FF03::1:3 at once for FF1E::1:3, and the IPv6 source address is set to the global address of test node on the network link 303;

Step 4: observe by the grouping that on network link 303, is sent by equipment under test 301;

Part 2: have the report of invalid parity check;

Step 5: configuration equipment under test 301 adds multicast group FF1E::1:3;

Step 6: on network link 303, test router 302 sends a certain multicast address query requests for FF1E::1:3;

Step 7: on network link 303, test router 302 has invalid MLD parity check report for multicast FF03::1:3 sends one at once;

Step 8: observe by the grouping that on network link 303, is sent by equipment under test 301;

The 3rd part: less than the report of 24 byte lengths;

Step 9: configuration equipment under test 301 adds multicast group FF1E::1:3;

Step 10: on network link 303, test router 302 sends a certain multicast address query requests for FF1E::1:3;

Step 11: on network link 303, test router 302 sends the report that length is 20 bytes for multicast FF03::1:3 at once;

Step 12: observe by the grouping that on network link 303, is sent by equipment under test 301;

The 4th part: the report of sending from other nodes;

Step 13: configuration equipment under test 301 adds multicast group FF1E::1:3

Step 14: on network link 303, test router 302 sends a certain multicast address query requests for FF1E::1:3;

Step 15: on network link 303, test router 302 sends a report for multicast FF03::1:3 at once;

Step 16: observe by the grouping that on network link 303, is sent by equipment under test.

Observed result:

4th, 8 and 12 step results require: because the report of sending from test node 1 is invalid, equipment under test should send the certain multicast address query requests that has multicast group FF1E::1:3 for IPv6 destination address and MLD multicast address respond from test router.

The 2nd and 4 step results require: because effective during from report that test node 1 sends, equipment under test should not respond the request of sending from test router 1.Should not send report message to multicast group FF1E::1:3.

Meet above-mentioned observed result requirement, then receive the test of report and pass through.

11) report that is transmitted as request is tested.

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Step 1: configuration equipment under test 201 adds multicast group FF1E::1:3; Note the interval (should defaultly be made as 10) of the non-request report of equipment under test 201;

Step 2: observe by the grouping that on network link 203, is sent by equipment under test;

Observed result:

The 2nd step results requires: equipment under test should send 2 reports (non-request report is (defaulting to 10 seconds) at interval) respectively after adding multicast group FF1E::1:3 be 3 seconds.

Meet above-mentioned observed result requirement, the report test that then is transmitted as request is passed through.

12) all node tests of link range;

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Step 1: test router 202 sends a certain multicast address query requests to FF02::1 (all node addresss of link range);

Step 2: observe equipment under test 201.

Observed result:

The 2nd step results requires: equipment under test 201 can not send report to FF02::1 (all node addresss of link range).

Meet above-mentioned observed result requirement, then all node tests of link range are passed through.

13) transmit the test of end;

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Part 1: finish message;

Step 1: configuration equipment under test 201 adds multicast group FF1E::1:3;

Step 2: configuration equipment under test 201 leaves multicast group FF1E::1:3;

Step 3: observe by the grouping that on network link 203, is sent by equipment under test 201;

Part 2: finish optimization under the default condition;

Step 4: configuration equipment under test 301 adds multicast group FF1E::1:3;

Step 5: enable test node on network link 203, test router 202 also is the listener of multicast group FF1E::1:3;

Step 6: finish if optimize, be sure of to be configured to not be sent completely information during report information equipment under test 201 if the FF1E::1:3 address is prevented from;

Step 7: on network link 203, test router 202 sends a certain multicast address request for the FF1E::1:3 multicast group;

Step 8: on network link 203, test router 202 sends a report for multicast FF03::1:3 at once;

Step 9:; Configuration equipment under test 201 leaves multicast group FF1E::1:3;

Step 10: observe the transmission situation that is grouped on the network link 203;

The 3rd part: close the optimization of finishing under the condition;

Step 11: configuration equipment under test 301 adds multicast group FF1E::1:3;

Step 12: enable test node on network link 203, test router 202 also is the listener of multicast group FF1E::1:3;

Step 13: be implemented if optimize, even the FF1E::1:3 report information is prevented from also disposing equipment under test and still is sent completely message;

Step 14: on network link 203, test router 202 sends a certain multicast address request for the FF1E::1:3 multicast group;

Step 15: on network link 203, test router 202 sends a report for multicast FF03::1:3 at once;

Step 16: configuration equipment under test 201 leaves multicast group FF1E::1:3;

Step 17: observe by the grouping that on network link 203, is sent by equipment under test 201.

Observed result:

The 3rd step results requires: equipment under test 201 should leave the group back send a multicast address position be FF1E::1:3 finish the multicast address of message to the all-router on the link.Finishing message should comprise:

link-local?IPv6?Source?Address

IPv6?Hop?Limit?of?1

IPv6?Router?Alert?option?in?a?Hop-by-Hop?Options?header

Valid?checksum

Code?field?value＝0

Reserved?field?value＝0

Maximum?Response?Delay?field?value＝0

Finishing message can not be long above 24 eight hytes;

The 6th step results requires: if equipment under test does not support to finish message optimisation, second portion should be ignored.If the equipment under test support is finished information optimization and is described, default should opening;

The 10th step results requires: equipment under test should not transmit after leaving multicast group FF1E::1:3 and finish message;

The 13rd step results requires: the 3rd step should not skip if equipment under test is not supported to finish message optimisation, if message optimisation is finished in the equipment under test support, must be able to close;

The 17th step results requires: equipment under test should leave message of finishing that has multicast group address FF1E::1:3 to all addresses of link (FF02::2) of multicast group FF1E::1:3 transmission.Finishing message should comprise:

link-local?IPv6?Source?Address

IPv6?Hop?Limit?of?1

IPv6?Router?Alert?option?in?a?Hop-by-Hop?Options?header

Valid?checksum

Code?field?value＝0

Reserved?field?value＝0

Maximum?Response?Delay?field?value＝0

Finishing message can not be long above 24 eight hytes.

Meet above-mentioned observed result requirement, then transmit the test of end and pass through.

14) node state conversion-idle detectaphone test.

Test setting: the set-up mode that sets test environment (with 7 in the step 102) according to Fig. 3).

Test process:

Part 1: the inquiry of receiving;

Step 1: with tested together as listener's (equipment under test 301 counts multicast group FF1E::1:3 already) of multicast group FF1E::1:3;

Step 2: to have maximum response time be 1000 certain multicast address request message to test router 302 for multicast group FF1E::1:3 sends one;

Step 3: observe by the grouping that on network link 303, is sent by equipment under test 301;

Part 2:

Step 4: with tested together as listener's (equipment under test 301 counts multicast group FF1E::1:3 already) of multicast group FF1E::1:3

Step 5: test router 302 sends a certain multicast address request for multicast group FF1E::1:3;

Step 6: observe by the grouping that on network link 303, is sent by equipment under test 301;

Step 7: wait for that equipment under test 301 sends the listener of a state free time once more;

Step 8: configuration equipment under test 301 stops to intercept multicast group FF1E::1:3;

The 3rd part:

Step 9: with tested together as listener's (equipment under test 301 counts multicast group FF1E::1:3 already) of multicast group FF1E::1:3;

Step 10: test router 302 sends a certain multicast address request for multicast group FF1E::1:3;

Step 11: test router 302 sends a report message for multicast group FF1E::1:3 at once;

Step 12: observe the transmission situation that is grouped on the network link 303;

Step 13: wait for that equipment under test sends the listener of a state free time once more;

Step 14: configuration equipment under test 301 stops to intercept multicast group FF1E::1:3;

Step 15: observe by the grouping that on network link 303, is sent by equipment under test 301.

Observed result:

The 3rd step results requires: after receiving the request message that test router 302 sends, equipment under test 301 enters in " request is received " incident.In this incident, equipment under test 301 starts the timer of the record that is used to delay time for multicast address FF1E::1:3, and delay value is between [0, maximum response time].In the present embodiment, should be between [0,1000].When equipment under test 301 enters time-delay prison hearer state, can within the 0-1000 millisecond, send a report information.

The 6th step results requires: after receiving the request message that test router 302 sends, equipment under test 301 sends a report information for multicast group FF1E::1:3, and a sign is set, be used to indicate that this is the last report that sends to this multicast group FF1E::1:3.Then, equipment under test 301 enters " inertia prison hearer " state.

The 9th step results requires: after equipment under test 301 is configured to stop to monitor multicast group FF1E::1:3, it will enter " stopping to monitor " incident.When the sign of equipment under test 301 is set to indicate to last report that this multicast group FF1E::1:3 sends, it will be sent completely message to the group FF1E::1:3 on the network link 303, and equipment under test 301 enters " non-monitoring " state thereupon.

The 12nd step results requires: behind the report message of receiving test router 302, equipment under test 301 does not send report message to multicast group FF1E::1:3, and can remove and indicate that the report that sends to this multicast group FF1E::1:3 is the sign of last report, then, equipment under test 301 enters " inertia prison hearer " state.

The 15th step results requires: after equipment under test 301 is configured to stop to monitor multicast group FF1E::1:3, it will enter " stopping to monitor " incident.The sign of equipment under test 301 is eliminated, and indicates that it is not the last report that sends to multicast group FF1E::1:3.So equipment under test 301 needn't be sent completely message to the multicast group FF1E::1:3 on the network link 303, equipment under test 301 enters " non-monitoring " state thereupon.

Meet above-mentioned observed result requirement, then node state conversion-idle detectaphone test is passed through.

15) node state conversion-time-delay detectaphone test.

Test setting: the set-up mode that sets test environment (with 7 in the step 102) according to Fig. 3).

Test process:

Part 1: the report of receiving;

Step 1: with tested together as listener's (equipment under test 301 counts multicast group FF1E::1:3 already) of multicast group FF1E::1:3;

Step 2: test router 302 is multicast group FF1E::1:3, and sending one, to have maximum response time be 1000 certain multicast address request message;

Step 3: test router 302 sends a report message for multicast group FF1E::1:3 at once;

Step 4: observe by the grouping that on network link 303, is sent by equipment under test.

Part 2: last report is designated to be provided with and stops to intercept;

Step 5: with tested together as listener's (equipment under test 301 counts multicast group FF1E::1:3 already) of multicast group FF1E::1:3;

Step 6: test router 302 sends a certain multicast address request for multicast group FF1E::1:3;

Step 7: observe by the grouping that on network link 303, is sent by equipment under test;

Step 8: wait for that equipment under test 301 sends the listener of a state free time once more;

Step 9: test router 302 is 5000 certain multicast address request for peak response time-delay of multicast group FF1E::1:3 transmission.;

Step 10: before equipment under test 301 delay counters were expired, configuration equipment under test 301 stopped to intercept multicast group FF1E::1:3;

Step 11: observe by the grouping that on network link 303, is sent by equipment under test; The 3rd part: the last report sign empties and stops to intercept;

Step 12: with tested together as listener's (equipment under test 301 counts multicast group FF1E::1:3 already) of multicast group FF1E::1:3;

Step 13: test router 302 sends a certain multicast address request for multicast group FF1E::1:3;

Step 14: test router 302 sends a report message for multicast group FF1E::1:3 at once;

Step 15: observe the transmission situation that is grouped on the network link 303;

Step 16: wait for that equipment under test 301 sends the listener of a state free time once more;

Step 17: test router 302 is 5000 certain multicast address request for peak response time-delay of multicast group FF1E::1:3 transmission;

Step 18: when equipment under test 301 delay timers were expired, the configuration equipment under test stopped to intercept multicast group FF1E::1:3;

Step 19: observe by the grouping that on network link 303, is sent by equipment under test 301;

The 3rd part: timer is expired

Step 20: with tested together as listener's (equipment under test 301 counts multicast group FF1E::1:3 already) of multicast group FF1E::1:3;

Step 21: to have maximum response time be 1000 certain multicast address request message to test router 302 for multicast group FF1E::1:3 sends one;

Step 22: observe by the grouping that on network link 303, is sent by equipment under test.

Observed result:

The 4th step results requires:

After receiving report message from test router 302, equipment under test 301 starts " report receives " incident.In this incident, equipment under test 301 stops the timer of multicast address FF1E::1:3, and removes that to be used to identify it be not the sign that sends report at last to this multicast group.Equipment under test 301 changes " inertia monitoring " state over to.Equipment under test 301 needn't send report message to multicast group FF1E::1:3.

The 7th step results requires:

After receiving request message from test router 302, equipment under test 301 sends report message to multicast group FF1E::1:3, and the sign of equipment under test 301 is set to send to group FF1E::1:3 at last the equipment of report, and then equipment under test 301 returns " inertia monitoring " state.

The 9th step results requires:

After receiving request message from test router 302, equipment under test 301 turns back to " time-delay is monitored " state.

The 11st step results requires:

After equipment under test 301 was configured to stop to monitor multicast group FF1E::1:3, equipment under test 301 entered " stopping to monitor " incident.Be last equipment because the sign of equipment under test 301 is configured to identify this equipment, so equipment under test 301 stops timer and be sent completely message to group FF1E::1:3 on network link 303 to multicast group FF1E::1:3 transmission report message.The state of equipment under test 301 becomes " non-monitoring ".

The 15th step results requires:

Behind the report message that receives from test router 302, equipment under test 301 can not send report message to multicast group FF1E::1:3, and it is not the sign that sends the equipment of report message at last to multicast group FF1E::1:3 that equipment under test 301 can be removed this equipment of sign.Equipment under test 301 returns " inertia monitoring " state.

The 17th step results requires:

When equipment under test 301 was received the request message that comes from test router 302, equipment under test 301 returned " time-delay is monitored " state.

The 19th step results requires:

After equipment under test 301 was configured to stop to monitor multicast group FF1E::1:3, equipment under test 301 entered " stopping to monitor " incident.It is not the sign that sends the equipment of report message at last to multicast group FF1E::1:3 that equipment under test 301 can be removed this equipment of sign.Equipment under test 301 needn't be sent completely message to group FF1E::1:3 on network link 303 thereupon.Equipment under test 301 stops to organize the delay timer of FF1E::1:3, and becomes " non-monitoring " state.

Meet above-mentioned observed result requirement, then the test of node state conversion-time-delay detectaphone is passed through.

If the test of described node multicast listener discovery takes to automatically perform mode, then according to above-mentioned 1)-15) order carry out, if do not take to automatically perform mode, then carry out according to random order;

The test of described node multicast listener discovery is all passed through, and then the test of the multicast listener discovery of described node is passed through, otherwise the multicast listener discovery test of described node is not passed through.

Step 103: the multicast listener discovery test of router.

The multicast listener discovery test of described router is made up of the test of router multicast listener discovery, comprising:

1) the transmission test of initialization and general inquiry.

Test setting: set test environment according to Fig. 4.Wherein, in Fig. 4, equipment under test 401 links to each other by certain network link 402, and network link 402 can be various Ethernet connected modes.

Test process:

Step 1: the multicast listener at equipment under test is found agreement.

Observed result:

The 1st step results requires:

Equipment under test transmitted a general inquiry in every some seconds.After initialization, equipment under test can change inquiry's state over to, in every some seconds, transmits a general inquiry.This general inquiry can send to all nodes of multicast address.The multicast address territory is set to 0, and the peak response time-delay is configured to ask to respond the time (being defaulted as 10000) of interruption.

Meet above-mentioned observed result requirement, then the transmission test of initialization and general inquiry is passed through.

2) send the test of inquiry.

Test setting: the set-up mode that sets test environment (with 1 in the step 103) according to Fig. 4).

Test process:

Part 1: general inquiry;

Step 1: test router sends general inquiry, and this test router is the inquiry on the network link 401;

Part 2: certain multicast address inquiry

Step 2: connect test router and network link 402;

Step 3: test router transmits one and reports to multicast address FF1E::1:3;

Step 4: equipment under test changes into the prison hearer state of current multicast address FF1E::1:3, and test router transmits to multicast address FF1E::1:3 and finishes message;

Step 5: observe the packet that equipment under test transmits to network link 402;

The 3rd part: a plurality of certain multicast address inquiries;

Step 6: connect test router and network link 402;

Step 7: test router sends one and reports to multicast address FF1E::1:3;

Step 8: test router sends one and reports to multicast address FF1E::1:4;

Step 9: equipment under test changes into the prison hearer state of current multicast address FF1E::1:3, and test router transmits to multicast address FF1E::1:3 and finishes message;

Step 10: observe the packet that equipment under test transmits to network link 402;

Step 11: equipment under test changes into the prison hearer state of current multicast address FF1E::1:4, and test router transmits to multicast address FF1E::1:4 and finishes message;

Step 12: observe the packet that equipment under test transmits to network link 402;

The 4th part: do not have a plurality of certain multicast address inquiries;

Step 13: connect test router and network link 402;

Step 14: test router sends one and reports to multicast address FF1E::1:3;

Step 15: equipment under test changes into the prison hearer state of current multicast address FF1E::1:3, and test router transmits to multicast address FF1E::1:4 and finishes message;

Step 16: observe the packet that equipment under test transmits to network link 402;

Observed result:

The 4th step results requires:

Meet the requirement as a result of above-mentioned observation step 1～step 16, then send the test of inquiry and pass through.

3) receive the invalid message test of finishing.

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Part 1: invalid parity check;

Step 1: test router sends a report to multicast address FF1E::1:3, any inquiry that test router response equipment under test sends to this address;

Step 2: after equipment under test changed into the prison hearer state of current multicast address FF1E::1:3, test router sent the message of finishing that has illegal verification to multicast address FF1E::1:3;

Step 3: wait for and monitor the inquiry interruption at last and monitor the time (being defaulted as 2 seconds) of the product of query counts at last, but the time of not being longer than the multicast monitoring interruption;

Step 4: observe the packet that equipment under test sends to network link 402;

Part 2: global source address;

Step 5: test router sends a report to multicast address FF1E::1:3, any inquiry that test router response equipment under test sends to this address;

Step 6: after equipment under test changed into the prison hearer state of current multicast address FF1E::1:3, test router transmitted one to multicast address FF1E::1:3 and has with the global address of the test router message of finishing as the IPv6 source address;

Step 7: wait for and monitor the inquiry interruption at last and monitor the time (being defaulted as 2 seconds) of the product of query counts at last, but the time of not being longer than the multicast monitoring interruption;

Step 8: observe the packet that equipment under test sends to network link 402;

The 3rd part: length is less than 24 eight hytes;

Step 9: test router sends a report to multicast address FF1E::1:3, any request that test router response equipment under test sends to this address;

Step 10: after equipment under test changed into the prison hearer state of current multicast address FF1E::1:3, test router sent the message of finishing that length is 20 bytes to multicast address FF1E::1:3;

Step 11: wait for and monitor the inquiry interruption at last and monitor the time (being defaulted as 2 seconds) of the product of query counts at last, but the time of not being longer than the multicast monitoring interruption;

Step 12: observe the packet that equipment under test sends to network link 402;

Observed result:

4th, 8 and 12 step results require: equipment under test is ignored the message of finishing of test router transmission, and can not change the inspection listening state over to; As to illegally finishing the response of message, the multicast address standard queries that sends to address FF1E::1:3 can not be sent out.

Meet above-mentioned observed result requirement, then receive and invalid finish the test of message and pass through.

4) receive the report message test that should not have numerical value.

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Part 1:

Step 1: test router transmits a report to multicast address FF1E::1:3, any inquiry that test router response equipment under test sends to this address;

Step 2: after equipment under test changed into the prison hearer state of current multicast address FF1E::1:3, test router was 100 the message of finishing to code field length of multicast address FF1E::1:3 transmission;

Step 3: observe the packet that equipment under test sends to network link 203;

Part 2:

Step 4: test router sends a report to multicast address FF1E::1:3, any inquiry that test router response equipment under test sends to this address;

Step 5: after equipment under test changed into the prison hearer state of current multicast address FF1E::1:3, test router was 30 the message of finishing to reserved field length of multicast address FF1E::1:3 transmission;

Step 6: observe the packet that equipment under test sends to network link 203;

The 3rd part:

Step 7: test router sends a report to multicast address FF1E::1:3, any inquiry that test router response equipment under test sends to this address;

Step 8: after equipment under test changed into the prison hearer state of current multicast address FF1E::1:3, test router was that the multicast address FF1E::1:3 of 32 bytes sends one and finishes message to length;

Step 9: observe the packet that equipment under test sends to network link 203;

Step 10: test router sends a report to multicast address FF1E::1:3, any request that test router response equipment under test sends to this address;

Step 11: after equipment under test changed into the prison hearer state of current multicast address FF1E::1:3, test router was 1000 the message of finishing to a peak response time-delay of multicast address FF1E::1:3 transmission field;

Step 12: observe the packet that equipment under test transmits to network link 203;

Observed result:

3rd, 6,9 and 12 step results require:

Equipment under test is received finishing message and changing the inspection listening state over to of test router transmission.The multicast address standard queries that message is finished in response can send to address FF1E::1:3.

Meet above-mentioned observed result requirement, receive that then the report message test that should not have numerical value passes through.

5) receive invalid query messages test;

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Part 1: invalid parity check;

Step 1: test router has IPv6 source address littler than equipment under test on the numerical value;

Step 2: test router sends a general inquiry that has illegal check to all nodes of multicast address (FF02::1);

Step 3: observe equipment under test;

Part 2: global source address;

Step 4: test router has IPv6 source address littler than equipment under test on the numerical value;

Step 5: it is the general inquiry of IPv6 source address that test router sends the global address with test router to all nodes of multicast address (FF02::1);

Step 6: observe equipment under test;

The 3rd part: length is less than 24 eight hytes

Step 7: test router has IPv6 source address littler than equipment under test on the numerical value;

Step 8: test router sends the general inquiry that length is 20 bytes to all nodes of multicast address (FF02::1);

Step 9: observe equipment under test;

Observed result:

3rd, 6 and 9 step results require: equipment under test is ignored the General Request Message that test router sends, and does not change " non-monitoring " state over to; Equipment under test continues as the inquiry, periodically sends general request to network link 203.The request that all equipment under tests send all has the IPv6 source address of present networks, and IPv6 bar number is 1, and IPv6 route alert option is at the head of hop-by-hop options.

Meet above-mentioned observed result requirement, receive that then the test of invalid query messages passes through.

6) receive the invalid query messages test that should not have numerical value.

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Part 1: encoding domain;

Step 1: test router has IPv6 source address littler than equipment under test on the numerical value;

Step 2: test router is configured to 100 general inquiry to code field length of all nodes of multicast address (FF02::1) transmission;

Step 3: observe the packet that equipment under test sends to network link 203;

Part 2: keep the territory;

Step 4: test router has IPv6 source address littler than equipment under test on the numerical value;

Step 5: test router is 30 general inquiry to reserved field length of all nodes of multicast address (FF02::1) transmission;

Step 6: observe the packet that equipment under test sends to network link 203;

The 3rd part: length is greater than 24 eight hytes;

Step 7: test router has IPv6 source address littler than equipment under test on the numerical value;

Step 8: test router is in multicast address, and message-length is that all nodes (FF02::1) of 32 bytes send a general inquiry;

Step 9: observe the packet that equipment under test sends to network link 203;

Observed result:

3rd, 6 and 9 step results require: equipment under test is carried out the general inquiry message that test router sends, and changes into non-inquiry's state; Equipment under test can periodically not send general inquiry to network link 203.

Meet above-mentioned observed result requirement, receive that then the invalid query messages test that should not have numerical value passes through.

7) receive invalid report message test.

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Part 1: invalid parity check;

Step 1: test router sends a report to multicast address FF1E::1:3;

Step 2:200 is after second, and test router sends a report that has illegal verification to multicast address FF1E::1:3;

Step 3: wait for 60 seconds (remaining time that multicast monitoring interrupts);

Step 4: test router is sent completely message to multicast address FF1E::1:3;

Step 5: observe equipment under test;

Part 2: global source address;

Step 6: test router sends a report to multicast address FF1E::1:3;

Step 7:200 is after second, and test router sends the report that a source address is set to the global address of the test router on the network link 203 to multicast address FF1E::1:3;

Step 8: wait for 60 seconds (remaining time that multicast monitoring interrupts);

Step 9: test router is sent completely message to multicast address FF1E::1:3;

Step 10: observe equipment under test;

The 3rd part: length is less than 24 eight hytes;

Step 11: test router sends a report to multicast address FF1E::1:3;

Step 12:200 is after second, and test router sends the report that length is 20 bytes to multicast address FF1E::1:3;

Step 13: wait for 60 seconds (remaining time that multicast monitoring interrupts);

Step 14: test router is sent completely message to multicast address FF1E::1:3;

Step 15: observe equipment under test;

Observed result:

5th, 10 and 15 step results require: equipment under test is ignored the report message that test router sends, and does not keep current prison hearer state; When receiving first illegal report, cross after date remaining time to the multicast monitoring interruption, equipment under test no longer shows the prison hearer of multicast address FF1E::1:3, changes non-listening state over to; When test router is sent completely message, because equipment under test is no longer monitored multicast address FF1E::1:3, equipment under test can not send the multicast address standard queries to address FF1E::1:3.

Meet above-mentioned observed result requirement, receive that then the test of invalid report message passes through.

8) receive the report message test that should not have numerical value.

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Part 1: code domain;

Step 1: test router sends a report to multicast address FF1E::1:3;

Step 2:200 is after second, and test router is 100 report to code word segment value of multicast address FF1E::1:3 transmission;

Step 3: wait for 60 seconds (remaining time that multicast monitoring interrupts);

Step 4: test router is sent completely message to multicast address FF1E::1:3;

Step 5: observe equipment under test;

Part 2: keep the territory;

Step 6: test router sends a report to multicast address FF1E::1:3;

Step 7:200 is after second, and test router is 30 report to reserved word segment value of multicast address FF1E::1:3 transmission;

Step 8: wait for 60 seconds (remaining time that multicast monitoring interrupts);

Step 9: test router is sent completely message to multicast address FF1E::1:3;

Step 10: observe equipment under test;

The 3rd part: length is greater than 24 eight hytes;

Step 11: test router sends a report to multicast address FF1E::1:3;

Step 12:200 is after second, and test router is report of multicast address FF1E::1:3 transmission of 32 bytes to message-length;

Step 13: wait for 60 seconds (remaining time that multicast monitoring interrupts);

Step 14: test router is sent completely message to multicast address FF1E::1:3;

Step 15: observe equipment under test;

The 4th part: peak response time-delay territory;

Step 16: test router sends a report to multicast address FF1E::1:3;

Step 17:200 is after second, and test router is that value that the multicast address FF1E::1:3 of 32 bytes sends a peak response time-delay territory is 1000 report to message-length;

Step 18: wait for 60 seconds (remaining time that multicast monitoring interrupts);

Step 19: test router is sent completely message to multicast address FF1E::1:3;

Step 20: observe equipment under test;

Observed result:

5th, 10,15 and 20 step results require: equipment under test should receive the report that test router sends, and keeps current prison hearer states thereafter 60 seconds.Because equipment under test always with address FF1E::1:3 as listen address, when it receive that test router sends finish message after, equipment under test will send the multicast address standard queries to address FF1E::1:3.

Meet above-mentioned observed result requirement, receive that then the report message test that should not have numerical value passes through.

9) other inquiries present the introns test.

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Part 1: the timer setting that other inquiries are current;

Step 1: on the network link 203, per 125 seconds all systems to multicast group of test router send a general inquiry;

Step 2: test router stops to send general inquiry;

Step 3: observe to send general inquiry for the last time from test router and forward inquiry's state to and send time of an inquiry to equipment under test;

Part 2:

Step 4: on the network link 203, per 125 seconds all systems to multicast group of test router send a general inquiry;

Step 5: test router stops to send general inquiry; The time that stops to send interrupts (promptly 125 seconds) and interrupts (promptly 225 seconds) less than other inquiries greater than inquiry;

Step 6: test router continues to send request like that as the step 4 of this part;

Step 7: observe the packet that equipment under test sends;

Observed result:

The 1st step results requires: after receiving the inquiry that test router sends, equipment under test changes non-requestor's state immediately over to;

The 3rd step results requires: send general inquiry for the last time from test router and should equal other inquiries to the time that equipment under test forwards inquiry's state to and sends an inquiry and interrupt;

The 4th step results requires: after receiving the request that test router sends, equipment under test changes non-inquiry's state immediately over to;

The 7th step results requires: when equipment under test is received the general inquiry of test router on the network link 203, it will restart other inquiry timers; Equipment under test needn't become the inquiry on the network link 203, also needn't send any query messages.

Meet above-mentioned observed result requirement, then other inquiries present introns tests and pass through.

10) multicast listener introns test.

Test setting: set test environment according to Fig. 5.Wherein, in Fig. 5, equipment under test 501 links to each other with second test router 503 with first test router 502 with second link 505 by first network link 504, and first network link 504 and second link 505 can be various Ethernet connected modes.

Test process:

Part 1: the multicast listener timer is provided with;

Step 1: the multicast listener of restarting equipment under test is found agreement;

Step 2: first test router 502 sends a multicast listener to multicast group FF1E::1:3 and finds protocol report;

Step 3: on first network link 504, second test router 503 sends multicast packet to address FF1E::1:3;

Part 2: the multicast listener timer is provided with replacement;

Step 4: the test of (first) above continuing (multicast listener of not restarting equipment under test is found agreement);

Step 5: wait for 30 seconds;

Step 6: the general inquiry request that first test router, 502 response equipment under tests send sends legal multicast listener to multicast group FF1E::1:3 and finds protocol report

Step 7: wait for 250 seconds;

Step 8: on first network link 504, second test router 503 sends multicast packet to address FF1E::1:3;

The 3rd part: group membership's timer is expired;

Step 9: the test of (second portion) above continuing (multicast listener of not restarting equipment under test is found agreement);

Step 10: first test router 502 stops to send report;

Step 11: wait for 265 seconds;

Step 12: on first network link 504, first test router 502 sends to address FF1E::1:3 and sends multicast packet;

Observed result:

The 3rd step results requires: after equipment under test is restarted, become the inquiry of first network link 504; When receiving first test router 502 to report that multicast group FF1E::1:3 sends, equipment under test can start the timer (multicast monitoring interruption) of this multicast group; Test router sends multicast packet to first network link 504;

The 8th step results requires: whenever equipment under test is received the report that first test router 502 sends to multicast group FF1E::1:3, and the timer (multicast monitoring interrupts, and is defaulted as 260 seconds) that equipment under test all can be reset this multicast group; Equipment under test sends multicast packet to first network link 504;

The 6th step results requires: after first test router 502 sent final report (FR), equipment under test stopped to show member's (multicast monitoring interruption) of multicast group FF1E::1:3 some seconds; Equipment under test sends multicast packet to first network link 504.

Meet above-mentioned observed result requirement, then the test of multicast listener introns is passed through.

11) query State conversion test.

Test setting: the set-up mode that sets test environment (with 1 in the step 102) according to Fig. 2).

Test process:

Part 1: the inquiry that comes from low IP address;

Step 1: wait for that equipment under test 201 becomes the inquiry on the network link 203;

Step 2: test router 202 has on the numerical value IPv6 source address littler than equipment under test 201, sends general inquiries to network link 203;

Step 3: observe the transmission situation that is grouped on the network link 203;

Part 2: general inquiry timer is expired;

Step 4: wait for that equipment under test 201 becomes the inquiry on the network link 203;

Step 5: test router 202 has on the numerical value IPv6 source address bigger than equipment under test 201, sends general inquiries to network link 203;

Step 6: the transmission situation of observed data on network link 203;

Observed result:

The 3rd step results requires: when equipment under test was received inquiry from test router, equipment under test started other inquiry's counters; Equipment under test changes " non-listening state " over to.Equipment under test can not send any general inquiry to network link 203;

The 6th step results requires: when equipment under test was received inquiry from test router, because the IP address is big, equipment under test kept the inquiry's state on the network link 203; After equipment under test sent general inquiry, inquiry response interrupted some seconds, and the general inquiry counter is expired; Equipment under test sends general inquiry and restarts the general inquiry counter, simultaneously show state " inquiry ".

Meet above-mentioned observed result requirement, then the test of query State conversion is passed through.

12) non-query State conversion test;

Test setting: set test environment according to Fig. 2.Wherein, in Fig. 2, equipment under test 201, test router 202 link to each other by certain network link 203.Network link 203 can be various Ethernet connected modes, and test router 202 is connected on the network by network link 203, and test router 202 has on the numerical value IPv6 source address littler than equipment under test 201.

Test process:

Part 1: the inquiry that comes from low IP address;

Step 1: test router 202 has on the numerical value IPv6 source address littler than equipment under test 201;

Step 2: equipment under test 201 becomes non-inquiry on the network link 203 by the time;

Step 3: test router 202 sends general inquiry to network link 203;

Step 4: observe the transmission situation that is grouped on the network link 203;

Part 2:

Step 5: test router 202 has on the numerical value IPv6 source address littler than equipment under test 201;

Step 6: test router 202 sends general inquiry to network link 203;

Step 7: wait for that other inquiries present some seconds (being defaulted as 255 seconds) at interval;

Step 8: observed data wraps in the transmission situation on the network link 203;

Observed result:

The 4th step results requires: receive the inquiry that test router sends when equipment under test, equipment under test is restarted other inquiries and is presented counter.Equipment under test keeps " non-inquiry " state; Equipment under test can not send general inquiry to network link 203;

The 8th step results requires: other inquiries presented interruption after some seconds, and equipment under test sends general inquiry, started the general inquiry counter and transferred " inquiry " state to.

Meet above-mentioned observed result requirement, the test of then non-query State conversion is passed through.

13) there is not listener's query State conversion test on the scene.

Test setting: set test environment according to Fig. 5.Wherein, in Fig. 5, equipment under test 501 links to each other with second test router 503 with first test router 502 with second network link 505 by certain first network link 504, and first network link 504 and second network link 505 can be various Ethernet connected modes.

Test process:

Step 1: the configuration equipment under test becomes the inquiry on the network link; Initialization does not have the prison hearer of multicast group FF1E::1:3;

Step 2: test router sends report message to multicast group FF1E::1:3;

Step 3: second network link, 505, the second test routers 503 send multicast packet to address FF1E::1:3;

Step 4: observe equipment under test;

Observed result:

The 4th step results requires: after receiving the report that comes from first test router 502 when equipment under test, equipment under test can produce an address that enters FF1E::1:3, and starts multicast monitoring person interrupt counter; Test router sends multicast packet to first network link 504.

Meet above-mentioned observed result requirement, then do not have listener's query State conversion test on the scene to pass through.

14) listener's query State conversion test on the scene.

Wherein, in Fig. 5, equipment under test 501 links to each other with second test router 503 with first test router 502 with second network link 505 by certain first network link 504, and first network link 504 and second network link 505 can be various Ethernet connected modes.

Test process:

Part 1: receive report;

Step 1: first test router 502 sends a report message to multicast group FF1E::1:3;

Step 2: on second network link 505, second test router 503 sends a multicast packet to destination address FF1E::1:3;

Step 3: observe test router;

Step 4: in maximum was monitored break period, first test router 502 sent the identical report message of report message that sends with step 1 to multicast group FF1E::1:3;

Step 5: on second network link 505, second test router 503 sends a multicast packet to destination address FF1E::1:3;

Step 6: observe test router;

Part 2: the address timer is expired;

Step 7: first test router 502 sends a report message to multicast group FF1E::1:3;

Step 8: wait for that multicast monitoring interrupts (giving tacit consent to 260 seconds);

Step 9: on second network link 505, second test router 503 sends a multicast packet to destination address FF1E::1:3;

Step 10: observe test router;

The 3rd part: accept to finish message

Step 11: first test router 502 sends a report message to multicast group FF1E::1:3;

Step 12:10 is after second, and first test router 502 is sent completely message to the equipment under test of multicast group FF1E::1:3;

Step 13: on second network link 505, second test router 503 sends a multicast packet to destination address FF1E::1:3;

Step 14: observe the transmission situation that is grouped on first network link 504;

Observed result:

The 3rd step results requires: when equipment under test is received the report of first test router 502, change " the prison hearer presents " state over to and have the inlet that enters multicast address FF1E::1:3;

The 6th step results requires: when equipment under test was received second report of first test router 502, equipment under test bit address FF1E::1:3 was restarted timer; Equipment under test keeps " the prison hearer presents " state, and equipment under test sends multicast packet to first network link 504;

The 10th step results requires: when equipment under test is received the report of first test router 502, change " the prison hearer presents " state over to and have the inlet that enters multicast address FF1E::1:3; Behind multicast monitoring person EOI, first test router 502 can not send any report message, and the equipment under test deletion enters the inlet of multicast address FF1E::1:3, and the notice Routing Protocol is not monitored the prison hearer of this address; Equipment under test changes " not having the prison hearer presents " state over to; Equipment under test need not send multicast packet to first network link 504;

The 14th step results requires: when equipment under test receive to address FF1E::1:3 send finish message the time, equipment under test enabling address timer (supervise the hearer at last and inquire about the product that interrupts with last prison hearer query counts, be defaulted as 2 seconds); Equipment under test retransmits timer for the address start that last prison hearer inquires about interruption, for address FF1E::1:3 sends a multicast address standard queries, change " checking the prison hearer " state simultaneously over to, equipment under test need not send multicast packet to first network link 504.

Meet above-mentioned observed result requirement, then listener's query State conversion test on the scene is passed through.

15) query State conversion of checking the listener is tested.

Test setting: set test environment according to Fig. 5.Wherein, in Fig. 5, equipment under test 501 links to each other with second test router 503 with first test router 502 with second network link 505 by first network link 504, and first network link 504 and second network link 505 can be various Ethernet connected modes.

Test process:

Part 1: receive report;

Step 1: first test router 502 is sent completely message to multicast group FF1E::1:3;

Step 2:5 is after second, and first test router 502 sends report message to multicast group FF1E::1:3;

Step 3: on second network link 505, second test router 503 sends multicast packet to destination address FF1E::1:3;

Step 4: observe equipment under test;

Part 2:

Step 5: first test router 502 is sent completely message to multicast group FF1E::1:3;

Step 6: wait for that monitoring inquiry at last interrupts finishing;

Step 7: on second network link 505, second test router 503 sends multicast packet to destination address FF1E::1:3;

Step 8: observe the packet that first network link 504 sends to equipment under test;

The 3rd part:

Step 9: first test router 502 is sent completely message to multicast group FF1E::1:3;

Step 10: the wait equipment under test is that the address timer of address FF1E::1:3 is expired;

Step 11: on second network link 505, second test router 503 sends multicast packet to destination address FF1E::1:3;

Step 12: observe the transmission situation that is grouped on first network link 505;

Observed result:

The 4th step results requires: receive the report of first test router, 502 transmissions when equipment under test after, it is address FF1E::1:3 timer that equipment under test starts; Remove and retransmit timer, change " the prison hearer presents " state over to; Equipment under test must send multicast packet to first network link 504;

The 8th step results requires: cross after date at the re-transmission timer, equipment under test should send a multicast address standard queries to address FF1E::1:3, restarts to be used for supervising at last the re-transmission timer of hearer's interruption and to keep " inspection prison hearer " state; Equipment under test must send multicast packet to first network link 504;

The 12nd step results requires: the address timer at the address of equipment under test FF1E::1:3 is crossed after date, equipment under test notice Routing Protocol is not supervised the hearer and is monitored this address, the deletion equipment under test enters the inlet of address FF1E::1:3, removes to retransmit timer and change " not having the prison hearer presents " state over to; Equipment under test needn't send multicast packet to first network link 504.

Meet above-mentioned observed result requirement, check that then listener's query State conversion test is passed through.

16) no listener non-query State conversion test on the scene.

Test setting: set test environment according to Fig. 5.Wherein, equipment under test 501 links to each other with second test router 503 with first test router 502 with second network link 505 by first network link 504 in Fig. 5, and first network link 504 and second network link 505 can be various Ethernet connected modes.

Test process:

Part 1: receive report;

Step 1: first test router 502 sends report message to multicast group FF1E::1:3;

Step 2: observe equipment under test 501;

Step 3: maximum prison hearer is in break period, and first test router 502 sends and the same report message of step 1 to multicast group FF1E::1:3;

Step 4: observe equipment under test 501;

Part 2: the address timer is expired

Step 5: first test router 502 sends multicast group FF1E::1:3 report information to equipment under test;

Step 6: wait for multicast monitoring person interruption (being defaulted as 260 seconds);

Step 7: observe equipment under test 501;

The 3rd part: finish receiving message;

Step 8: first test router 502 sends multicast group FF1E::1:3 report information to equipment under test;

Step 9: equipment under test changed prison over to the hearer presents state for address FF1E::1:3 after, first test router 502 sent and sends multicast group FF1E::1:3 to equipment under test and finish information;

Step 10: observe the transmission situation that is grouped on first network link 504;

Observed result:

The 2nd step results requires: receive the report of first test router 502 when equipment under test after, equipment under test changes " the prison hearer presents " state over to and produces an inlet that enters address FF1E::1:3;

The 4th step results requires: receive second report of first test router 502 when equipment under test after, equipment under test is restarted the timer of address FF1E::1:3; Equipment under test keeps " the prison hearer presents " state;

The 7th step results requires: receive the report of first test router 502 when equipment under test after, equipment under test changes " the prison hearer presents " state over to and produces an inlet that enters address FF1E::1:3; Have no progeny in the multicast monitoring person, first test router 502 does not send any report message, and the equipment under test deletion enters the inlet of address FF1E::1:3, notifies Routing Protocol not supervise the hearer address simultaneously; Equipment under test changes " not having the prison hearer presents " state over to.

The 10th step results requires: when equipment under test was received the multicast address standard queries of an address FF1E::1:3, equipment under test started the peak response time-delay address timer (supervising hearer's query counts at last) in the query messages and changes " check and monitor " state over to; Equipment under test needn't send the MAS inquiry to address FF1E::1:3.

Meet above-mentioned observed result requirement, then do not have listener's non-query State conversion test on the scene and pass through.

17) listener's non-query State conversion test on the scene.

Test setting: according to shown in Figure 3, equipment under test 301, test router 302 and test macro 304 link to each other by certain network link 303, and link can be various Ethernet connected modes.

Test process:

Part 1: receive report;

Step 1: test router 302 sends a report message to multicast ground FF1E::1:3;

Step 2: observe equipment under test 301;

Step 3: in break period, test router 302 sends and the step to multicast ground FF1E::1:3 maximum prison hearer

Rapid 1 same report message

Step 4: observe equipment under test 301;

Part 2: the address timer is expired;

Step 5: test router 302 sends multicast ground FF1E::1:3 report message to equipment under test 301;

Step 6: wait for multicast monitoring person break period (giving tacit consent to 260 seconds);

Step 7: observe equipment under test 301;

The 3rd part:

Step 8: test router 302 sends multicast ground FF1E::1:3 report message to equipment under test 301;

Step 9: after the prison hearer that equipment under test changes address FF1E::1:3 over to presented state, test router 302 sent multicast ground FF1E::1:3 to equipment under test and finishes message;

Step 10: observe the transmission situation that is grouped on the network link 303;

Observed result:

The 2nd step results requires: when equipment under test was received the report of test router 302 transmissions, equipment under test changed " the prison hearer presents " state over to and has the inlet of a multicast address FF1E::1:3;

The 4th step results requires: when equipment under test was received second report of test router 302 transmissions, equipment under test was restarted address FF1E::1:3 timer; Equipment under test keeps " the prison hearer presents " state;

The 7th step results requires: when equipment under test was received the report of test router 302 transmissions, equipment under test changed " the prison hearer presents " state over to and has the inlet of a multicast address FF1E::1:3; After multicast monitoring interrupted, test router 302 did not send any report message, and the inlet of equipment under test deletion address FF1E::1:3 and notice Routing Protocol be the prison hearer of this address not; Equipment under test enters " not having the prison hearer " state;

The 10th step results requires: when equipment under test was received the multicast address standard queries of an address FF1E::1:3, equipment under test started the peak response time-delay address timer (supervising hearer's query counts at last) in the query messages and changes " check and monitor " state over to; Equipment under test needn't send the MAS inquiry to address FF1E::1:3.

Meet above-mentioned observed result requirement, then listener's non-query State conversion test on the scene is passed through.

18) non-query State conversion of checking the listener is tested.

Test setting: according to shown in Figure 3, equipment under test 301, test router 302 and test macro 304 link to each other by certain network link 303, and network link 303 can be various Ethernet connected modes.

Test process:

Part 1: receive report;

Step 1: test router 302 sends a multicast address standard queries to multicast group FF1E::1:3;

Step 2: before the address of FF1E::1:3 timer was expired, test router 302 sent a report message to multicast group FF1E::1:3;

Step 3: observe equipment under test;

Part 2: the address timer is expired;

Step 4: test router 302 sends a multicast address standard queries to multicast group FF1E::1:3;

Step 5: the address timer of waiting for equipment under test address FF1E::1:3 is expired;

Step 6: observe the transmission situation that is grouped on the network link 303;

Observed result:

The 3rd step results requires: when equipment under test was received the report of test router, the timer of equipment under test enabling address FF1E::1:3 also changed " the prison hearer presents " state over to; The inlet of equipment under test tabulation explicit address FF1E::1:3;

The 6th step results requires: the address timer at the address of equipment under test FF1E::1:3 is crossed after date, and the hearer is not supervised in this address of equipment under test notice Routing Protocol, and the inlet of deletion address FF1E::1:3 also changes " not having the prison hearer " state over to.

Meet above-mentioned observed result requirement, check that then listener's non-query State conversion test is passed through.

19) non-inquiry finishes the reception first son test of message.

Test setting: according to shown in Figure 3, equipment under test 301, test router 302 and test macro 304 link to each other by certain network link 303, and link can be various Ethernet connected modes.

Test process:

Step 1: test router 302 is sent completely message to network link 303;

Step 2: observe equipment under test.

Observed result:

The 3rd step results requires: when equipment under test receive test router 302 finish message the time, equipment under test is ignored this message; After peak response time-delay (supervising hearer's query counts at last), the prison hearer that equipment under test needn't notify multicast routing protocol not have address FF1E::1:3 presents, tabulate all the time inlet of explicit address FF1E::1:3 of equipment under test.

Meet above-mentioned observed result requirement, then non-inquiry finishes the reception first son test of message and passes through.

20) non-inquiry finishes the reception second son test of message.

Test setting: equipment under test 501, test router 502 link to each other by certain network link 504 in Fig. 5, and network link 504 can be various Ethernet connected modes.

Test process:

Step 1: 502 transmissions of first test router are 10000 milliseconds standard queries to peak response time-delay of address FF1E::1:3 transmission;

Step 2: first test router 502 is 500 milliseconds multicast address standard queries to peak response time-delay of address FF1E::1:3 transmission;

Step 3: network link 504, the first test routers 503 send a multicast packet to destination address FF1E::1:3;

Step 4: observe equipment under test.

Observed result:

The 4th step results requires: receive the multicast address standard queries that sends to address FF1E::1:3 when equipment under test, if this address timer of equipment under test is greater than 2*500 (the 2nd, the last prison hearer query counts of equipment under test), equipment under test can be set to 1000 by timer; In 1 second, equipment under test can not listed the prison hearer of address FF1E::1:3; Equipment under test does not send multicast packet to first network link 504.

Meet above-mentioned observed result requirement, then non-inquiry finishes the reception second son test of message and passes through.

21) inquiry transfers the test of non-inquiry's to when checking the listener.

Test setting: according to shown in Figure 3, equipment under test 301, test router 302 and test macro 304 link to each other by certain network link 303, and network link 303 can be various Ethernet connected modes.

Test process:

Part 1: timer is expired;

Step 1: the address FF1E::1:3 of test router 302 on network link 303 sends a report;

Step 2: after equipment under test entered prison the hearer presents state, test router 302 sent and sends one to address FF1E::1:3 and finish message;

Step 3: test router 302 to address FF1E::1:3 send one finish message after, test router 302 equipment that is lower than equipment under test of the IP address numerical value on network link 303 immediately sends an inquiry;

Step 4: test router is any inquiry of response address FF1E::1:3 not;

Step 5: observe equipment under test;

Part 2: the report that receives;

Step 6: test router sends a report to the address of network link 303 FF1E::1:3;

Step 7: after equipment under test entered prison the hearer presents state, test router was sent completely message to address FF1E::1:3;

Step 8: after address FF1E::1:3 was sent completely message, test router sent the equipment that IP address numerical value on network link 303 is lower than equipment under test immediately and sends an inquiry at test router

Step 9:1 is after second, the inquiry of test router response address FF1E::1:3;

Step 10: observe equipment under test;

Observed result

The 5th step results requires: when equipment under test receive test router finish message after, equipment under test sends the inquiry of multicast address standard queries to address FF1E::1:3, and start this address timer (supervise the hearer at last and inquire about interruption and last prison hearer query counts), be defaulted as 2 seconds; It is expired up to timer that equipment under test outwards sends the multicast address standard queries, and after the inquiry of receiving test router, equipment under test is not in inquiry's state; Cross after date at timer, equipment under test can not send any inquiry to network link 303;

The 10th step results requires: when equipment under test receive test router finish message after, equipment under test sends the multicast address standard queries to address FF1E::1:3, and start this address timer (supervise the hearer at last and inquire about interruption and last prison hearer query counts), be defaulted as 2 seconds; Equipment under test outwards sends the multicast address standard queries and receives the described report of step 9 up to it; After the inquiry of receiving test router, equipment under test is not in inquiry's state; After receiving report, equipment under test can not send any inquiry to network link 303.

Meet above-mentioned observed result requirement, then the inquiry transfers the test of non-inquiry's to and passes through when checking the listener.

If the test of described router multicast listener discovery takes to automatically perform mode, then according to above-mentioned 1)-21) order carry out, if do not take to automatically perform mode, then carry out according to random order;

The test of described router multicast listener discovery is all passed through, and then the test of the multicast listener discovery of described router is passed through, otherwise the multicast listener discovery test of described router is not passed through.

Step 104: generate test result.

Fig. 6 is the interoperability testing method test result schematic diagram of multicast listener discovery protocol under the IPv6 provided by the invention.Among Fig. 6, generate test result specifically: the collection analysis message is also exported WEB form test result, comprises numbering, project, result, daily record script, grouping.

The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.

Claims (4)

1. the interoperability testing method of multicast listener discovery protocol under the IPv6 is characterized in that described method of testing comprises the following steps:

Step 1: test system environment setting;

Step 2: the multicast listener discovery test of node;

Step 3: the multicast listener discovery test of router;

Step 4: generate test result.

2. the interoperability testing method of multicast listener discovery protocol under a kind of IPv6 according to claim 1 is characterized in that the multicast listener discovery test of described node is made up of the test of node multicast listener discovery, comprising:

1) receives the peak response time-delay test that timer is set to 0 general polling request;

2) receive the peak response time-delay test that timer is set to non-0 general polling request and sends report;

3) receive the peak response time-delay test that timer is set to 0 certain multicast address query requests;

4) receive the peak response time-delay test that timer is set to non-0 certain multicast address query requests;

5) receive effective query messages test that should not have numerical value;

6) receive invalid Query Information test;

7) transmission report message test;

8) receive the report message test that should not have numerical value;

9) time-delay of the peak response in report message test;

10) receive the test of report;

11) report that is transmitted as request is tested;

12) all node tests of link range;

13) transmit the test of end;

14) node state conversion-idle detectaphone test;

15) node state conversion-time-delay detectaphone test;

If the test of described node multicast listener discovery takes to automatically perform mode, then according to above-mentioned 1)-15) order carry out, if do not take to automatically perform mode, then carry out according to random order;

The test of described node multicast listener discovery is all passed through, and then the test of the multicast listener discovery of described node is passed through, otherwise the multicast listener discovery test of described node is not passed through.

3. the interoperability testing method of multicast listener discovery protocol under a kind of IPv6 according to claim 1 is characterized in that the multicast listener discovery test of described router is made up of the test of router multicast listener discovery, comprising:

1) the transmission test of initialization and general inquiry;

2) send the test of inquiry;

3) receive the invalid message test of finishing;

4) receive the report message test that should not have numerical value;

5) receive invalid query messages test;

6) receive the invalid query messages test that should not have numerical value;

7) receive invalid report message test;

8) receive the report message test that should not have numerical value;

9) other inquiries present the introns test;

10) multicast listener introns test;

11) query State conversion test;

12) non-query State conversion test;

13) there is not listener's query State conversion test on the scene;

14) listener's query State conversion test on the scene;

15) query State conversion of checking the listener is tested;

16) no listener non-query State conversion test on the scene;

17) listener's non-query State conversion test on the scene;

18) non-query State conversion of checking the listener is tested;

19) non-inquiry finishes the reception first son test of message;

20) non-inquiry finishes the reception second son test of message;

21) inquiry transfers the test of non-inquiry's to when checking the listener;

If the test of described router multicast listener discovery takes to automatically perform mode, then according to above-mentioned 1)-21) order carry out, if do not take to automatically perform mode, then carry out according to random order;

The test of described router multicast listener discovery is all passed through, and then the test of the multicast listener discovery of described router is passed through, otherwise the multicast listener discovery test of described router is not passed through.

4. the interoperability testing method of multicast listener discovery protocol under a kind of IPv6 according to claim 1, it is characterized in that described generation test result specifically: the collection analysis message is also exported WEB form test result, comprises numbering, project, result, daily record script, grouping.

Images