Veryx ATTEST TM. Sample Test cases Overview. Conformance Test Suite. Protocol Independent Multicast Sparse Mode (PIM-SM)

Transcription

1 Veryx ATTEST TM Conformance Test Suite Protocol Independent Multicast Sparse Mode (PIM-SM) Sample Test cases Overview Part Number: T / TCLS PIM-SM /1.0

2 This page is intentionally left blank.

3 Introduction The Veryx ATTEST TM PIM-SM Conformance test suite is designed to enable quick and efficient testing of Protocol Independent Multicast - Sparse Mode (PIM-SM) version 2 protocols as defined by IETF RFC 4601 and RFC Veryx has developed about 280 test cases that comprehensively test routers for PIM-SMv2 conformance and are organized into the following Test Groups: S. No Group Cases Sample Cases 1. Assert Group (AST) Bootstrap Router Group (BSR) Data Forwarding Group (DFG) Designated Router Group (DRG) Finite State Machine Group (FSM) Join Prune Group (JPG) Local Membership Group (LMG) Neighbor Group (NEI) Packet Format Group (PKT) Register Group (REG) Rendezvous Point Group (RPG) Shortest Path Tree Group (SPT) Source Specific Multicast Group (SSM) Reselection Group (RSG) 3 - Total Copyright Veryx Technologies. Page 1

4 The following is a listing of the PIM-SM sample test cases. List of sample test cases Assert(S,G) state Machine NI->W state on recv (S,G) data on OIF Assert(S,G) state Machine NI->W->W state on recv Inferior Assert(S,G) Upstream (S,G) state machine NJ->J->NJ state when OIF is NULL due to lost assert(s,g) BSR Election based on Priority To verify that the (S,G) Assert state machine on the interface transitions from the NO_INFO state to the I_AM_ASSERT_WINNER state on receiving an (S,G) data packet on the downstream interface whose (S,G) downstream state machine is in the JOIN state. To verify that the (S,G) Assert state machine on the interface remains in the I_AM_ASSERT_WINNER state after receiving an Inferior ASSERT(S,G) message from another router on that interface. To verify that the upstream (S,G) state machine transitions from the JOINED state to the NOT_JOINED state and that the router sends a PRUNE(S,G) message towards S whenever the router loses Assert on the outgoing interfaces, which causes the JOIN_DESIRED(S,G) to become FALSE. The upstream state machine transitions back to the JOINED state once the Assert timer expires. To verify that the BootStrap Router (BSR) is elected based on Bootstrap Router Priority. RFC 4601, Sec 4.6.1, Page 84 AST_001 RFC 4601 sec 4.6.1, page 84 AST_003 RFC 4601, Sec 4.6.1, Page 89 RFC 4601 Sec 4.7, Page 103 RFC 5059 Sec 1.2, Page 5 AST_034 BSR_001 Copyright Veryx Technologies. Page 2

5 BSR Election based on IP Address, same Priority BSR construct RP-set from local pool of C-RPs and sends RP-set in BSM C-RP send C-RP-ADV Msg with default Group range 224/4 when Group range is not configured DR Election based on IP Address Router loses DR Election based on DR Priority on recv Hello with higher DR Priority Router loses DR Election based on IP Address on recv Hello with higher IP address, no DR Priority To verify that the BootStrap Router (BSR) is elected based on the IP address, when a BOOTSTRAP message with same BSR Priority is received from the neighbor. To verify that the BootStrap Router (BSR) constructs the RP-Set from the pool of C- RPs that are configured locally by the management and includes it in the BOOTSTRAP messages. To verify that the router sends CANDIDATE-RP-ADVERTISEMENT message to the BSR with Group Range set to default value 224/4, when it is configured as Candidate RP and the Group Range is not specified. To verify that the DR Election on an interface takes place based on the IP Address, unless all the PIM neighbors on the interface advertise that they are capable of using the DR Election Priority option. To verify that the Router, on receiving HELLO message from an existing Neighbor with a DR Election Priority value higher than that of itself, ceases to be the DR on that interface. To verify that the Router loses DR Election on an interface despite higher DR priority, when it receives a HELLO message from a new neighbor with a higher IP address but without the DR Election Priority Option. RFC 4601, Sec 3, Page 12, RFC 5059, Sec 2, Page 8, Sec 3.1.4, Page 15., RFC 4601, Sec 3, Page 12, RFC 5059, Section 1.2, Page 6. RFC 4601, Sec 3, Page 12, RFC 5059, Section 3.3 Page 19. RFC 4601, Sec 4.3.1, Page 31, Sec 4.3.2, Page 33. RFC 4601, Sec 4.3.2, Page 34. RFC 4601, Sec 4.3.2, Page 33, 34. BSR_002 BSR_019 BSR_025 DRG_001 DRG_011 DRG_012 Copyright Veryx Technologies. Page 3

6 (*,*,RP) downstream state machine NI->J->PP->NI state, send PRUNE_ECHO(*,*,RP) if there is more than one neighbor (*,G) downstream state machine NI->NI state on recv JOIN(*,G) not addressed to router Router process JOIN message with multiple (S,G) entries Router sends JOIN(S,G) when route towards Source S is found DR forwards data to local hosts which sent request for joining Group G Periodic Hello messages on PIM enabled interfaces Hello messages sent only on PIM enabled interfaces To verify that the (*,*,RP) downstream state machine on the interface, when transitioning from the PRUNE_PENDING state to the NO_INFO state on expiry of the Prune Pending timer, sends a PRUNE_ECHO(*,*,RP) message on the subnet connected to the downstream interface only if there is more than one neighbor. To verify that the (*,G) downstream state machine on an interface remains in the NO INFO state when it receives a JOIN(*,G) message not targeted to the address of the interface. To verify that the Router sends JOIN message(s) towards the sources, on receiving a JOIN message with multiple (S,G) entries from the downstream router on an interface. To verify that the Router sends a JOIN(S,G) message towards source S when it finds a route towards source S. To verify that the Designated Router of a subnet forwards the multicast packets received from the upstream router (or RP) to the local hosts on the outgoing interfaces which are in the JOIN (*,G) state for Group G. To verify that periodic HELLO messages are sent on each PIM-enabled interface at Hello_Period intervals. To verify that PIM HELLO messages are sent on an interface only when PIM is enabled on it. RFC 4601, Sec 4.5.1, Page 48, 49 RFC 4601, Sec 4.5.1, Page 50, 51 FSM_004 FSM_015 RFC 4601, Sec 4.5, Page 45 JPG_011 RFC 4601, Sec 4.5.7, Page 73 RFC 4601, Sec 6.1.1,Page 136 RFC 4601, Sec 4.3.1, Page 30 RFC 4601, Sec 4.3.1, Page 30 JPG_012 LMG_002 NEI_001 NEI_002 Copyright Veryx Technologies. Page 4

7 DR Priority option included in Hello message Packet Format check for HELLO messages Packet Format check for BOOTSTRAP messages with no RP-Set Packet Format check for BOOTSTRAP messages with RP-Set Packet Format check for JOIN(*,G) messages DR ignores multicast data for G from local host if the RP for G is not known DR ignores multicast data from non-local source RP set SPT(S,G) to FALSE on expiry of (S,G) Keep Alive timer To verify that the DR Election Priority option is included in HELLO messages. To verify that HELLO messages are sent to neighbors in the correct format. To verify that the BOOTSTRAP messages constructed by the bootstrap router have the correct format. To verify that the BOOTSTRAP messages with RP set sent by the BSR have the correct format. To verify that the JOIN (*, G) messages propagated by the downstream router have the correct format. To verify that the Designated Router of a subnet ignores multicast data traffic from a local source for the group whose RP information is not known. To verify that the Designated Router of a subnet ignores multicast data traffic from non-local source. To verify that the Rendezvous Point switches to the source-specific Shortest Path Tree (SPT), on receiving multicast data traffic from the Source and sets the SPTbit(S,G) to FALSE, on expiry of the (S,G) Keep Alive Timer. RFC 4601, Sec 4.3.1, Page 31 RFC 4601, Sec 4.9.2, Page 113, 114, 115 and 116 RFC 5059, Sec 4.1, Page 26,27 RFC 5059, Sec 4.1, Page 26,27, Sec 3.6, Page 23 RFC 4601, Sec 4.9.5, Page 120 and 121 NEI_003 PKT_001 PKT_002 PKT_004 PKT_007 SHOULD RFC 4601, Sec 4.4, Page 38 REG_006 RFC 4601, Sec 4.4.1, Page 38 RFC 4601, Sec 4.5.7, Page 73 REG_008 SPT_009 Copyright Veryx Technologies. Page 5

8 (S,G) downstream state machine NI->J->NI state for SSM group G DR not sends Register to RP on recv data from local hosts for SSM Group To verify that the (S,G) downstream state machine on an interface transitions from the NO_INFO state to the JOIN state on receiving a JOIN(S,G) message for the Source-Specific Multicast (SSM) Group G from the downstream router, and transitions back to the NO_INFO state after the Expiry timer expires. To verify that the Designated Router of a subnet ignores multicast data traffic from local sources for the Source-Specific Multicast (SSM) group address (232/8 range). RFC 4601, Sec 4.8.2,Page 107,Sec 4.5.3, Page 53 RFC 4601, Sec 4.8.1, Page 106 SSM_001 SSM_004 Copyright Veryx Technologies. Page 6

9 About Veryx Technologies Veryx Technologies (formerly Net-O 2 Technologies) provides innovative Verification and Measurement Solutions for the global communications industry. ATTEST solutions verify networking equipment being used for Access, Carrier Ethernet, Data Center, Edge, Enterprise, Industrial and Security. The unique offerings from Veryx enable customers to reduce the time-required-to-test and enhance their time-to-market. Veryx ATTEST TM is the trademark of Veryx Technologies. All other trademarks of respective owners are acknowledged. E mail: info@veryxtech.com Web: Copyright Veryx Technologies. Page 7