TJ29xx_L2_UTP

TJ29xx L2 Test Plan TJ29xx L2 Test Plan

Version 00.11

VME L2 Unit Test Plan ITP <<0.1>>

Revision History:

Revision Date Author Reason Reviewed By Approved By

0.1 2-May-2011 Saikat Choudhury

First version Sarveshwara Chary, Vinod Chowdappa

0.2 15-Mar-2012 Umang Updated with FP6_4_0 new L2 features

0.3 20-Mar-2012 Ganesh Patwardhan

Updated with FP6_4_0 new L2 features

Review History:

Revision Review Date Reviewer(s) Review Comments

0.1 05/09/11Sarveshwara Chary, Vinod Chowdappa

VME_L2_UTP_RR.txt

Tejas Networks India Ltd. Company Confidential Page 2 of 26

VME L2 Unit Test Plan ITP <<0.1>>

Table of Contents

1Introduction..........................................................................................................................4

1.1Document Objectives......................................................................................................4

1.2Scope...............................................................................................................................4

1.3Intended Audience...........................................................................................................4

1.4Acronyms.........................................................................................................................4

1.5Applicable Standards......................................................................................................5

1.6References.......................................................................................................................5

2Unit test cases.......................................................................................................................6

2.1Functional testing...........................................................................................................62.1.1VLAN testing...........................................................................................................62.1.2Spanning Tree Protocol............................................................................................82.1.3Access Control list (ACL)........................................................................................92.1.4Link Aggregation Group (LAG)............................................................................102.1.5IGMP Snooping.....................................................................................................112.1.6Port Protection .......................................................................................................122.1.7Port mirroring.........................................................................................................132.1.8Port Security...........................................................................................................142.1.9COS Test................................................................................................................142.1.10Diffserv................................................................................................................172.1.11Diffserv Simple-policer........................................................................................182.1.12 Service port Policy..............................................................................................19

2.2Testing across Upgrade and Downgrade.....................................................................202.2.1L3 Image................................................................................................................20

3Appendix A: Open issues...................................................................................................21

Tejas Networks India Ltd. Company Confidential Page 3 of 26

1 Introduction

1.1 Document Objectives

This document captures the unit test plan for VME_L2 switch. Since only L2 features are available in this switch so testing is in accordance to L2 features only

It starts with a description of the physical topology of the test setup and the associated test configurations. There are multiple configurations on the same topology.

The test cases will then refer to a specific configuration used for that test.

1.2 Scope

This document shall cover the following:

· Test setup: physical topology, configurations

· Unit test cases

1.3 Intended Audience

- DPG team / ELANP development team

- IE team

- PV team

1.4 Acronyms

Acronym Description

CLI Command Line Interface

FE Fast Ethernet (100Mbps)

GE Gigabit Ethernet (1000Mbps)

IP Internet Protocol

IGMP Internet Group Management Protocol

OSPF Open Shortest Path First

PIM Protocol Independent Multicast

1.5 Applicable Standards

1. IETF RFCs for switching

2. IEEE L2 switching standards: 802.1, 802.3 WG

1.6 References

Srl#. Documents Referred

1. TJFCM01 PRD, Mar 2010

http://tn100build/cgi-bin/cvsweb/Documentation/Requirements/TJFCM01_PRD.doc

2. VME_l2_DD, April 2011

http://tn100build/cgi-bin/cvsweb/Documentation/FCM/VME_l2_DD.doc

2 Unit test casesThis section enumerates the test cases in detail. The following format shall be used for each test case.

§ Test ID

o Represents a unique ID for the test case

§ Test Configuration

o Refers to applicable test configuration for the test case

§ Test Description

o Describes the purpose of the test case

o Provides detailed procedure for configuration and executing test case

§ Expected Result

o Describes the expected results from the test case

2.1 Functional testing

2.1.1 VLAN testingTest ID: TC_FUNC_1

Test Configuration: C1

Spirent ports SP-1 and SP-2 are connected to VME L2 switch via ports 1 and 2 respectively.

Port 1 and 2 form part of same vlan 100.

VME L2SP-1 SP-2

Test Description:

1. Untagged frames sent from SP-1

2. VLAN 100 tagged frames sent from SP-1.

3. 'vlan pvid 100' is configured for port 1. Untagged frames sent from SP-1.


5. 'vlan tagging 100' is configured for port 2. Untagged frames sent from SP-1.



Expected Result:

1. No frames are received at SP-2. Frames dropped at port-1.

2. SP-2 receives untagged frames. Port counters increments for port-1 and 2.

3. Untagged frames received at SP-2.

4. Untagged frames received at SP-2.

5. VLAN 100 tagged frames received at SP-2.

6. VLAN 100 tagged frames received at SP-2.

7. No frames are received at SP-2. Frames dropped at port-1.

2.1.2 Spanning Tree ProtocolTest ID: TC_FUNC_2

Test Configuration: C2_A

SP1

VME L2

Spirent port SP is connected to node via port-1. Port-2 is connected physically to port-3. . Port 1,2 and 3 form part of same VLAN 200.

Configuration : C2_B

Spirent port SP1 is connected to node via port-1.Ports 2 and 3 are connected to the ports 2 and 3 of other node. Port 1,2 and 3 form part of same VLAN 200.

Test Description:

1. Send vlan 200 frame from SP1.

2. Apply spanning tree protocol on ports 1,2 and 3. Send 30 frames with vlan 200 from SP1.

3. Repeat the test steps for configuration C2_B.

Expected Result:

1. Looping is expected. All port counters(1,2 and 3) will show rapid increments.

2. Port counter will increment by 30 for port-1 and port-2/port-3. One of ports 2/3 will show disabled STP state.

3. Port counter will increment by 30 for port-1 and port-2/port-3. One of ports 2/3 will show disabled STP state.

2.1.3 Access Control list (ACL)Test ID: TC_FUNC_3


VME L2

VME L2

SP11 SP2

VME L2

Spirent ports SP-1 and SP-2 are connected to VME L2 switch via ports 1 and 2 respectively.

Port 1 and 2 form part of same vlan 100.

a)Create mac ACL M1 with 9 permit rules

b)Create mac ACL M2 with 9 deny rules

c)Create ip ACL 111 with 9 permit rules

d)Create ip ACL 112 with 9 deny rules

Test Description:

1. Apply ACL M1 on interface 1. Send 10 streams from spirent SP-1 (9 streams matching the different criteria as per M1 ACL and one stream with non-matching parameters).

2. Apply ACL M2 on interface 1. Send 10 streams from spirent SP-1 (9 streams matching the different criteria as per M2 ACL and one stream with non-matching parameters).

3. Apply ACL 111 on interface 1. Send 10 streams from spirent SP-1 (9 streams matching the different criteria as per ACL 111 and one stream with non-matching parameters).

4. Apply ACL 112 on interface 1. Send 10 streams from spirent SP-1 (9 streams matching the different criteria as per M1 112 and one stream with non-matching parameters).

Expected Result:

1. For first 9 stream traffic will flow. Last stream with non-conforming values will be dropped as unacceptable frames.

2. For first 9 stream traffic will be dropped. Last stream with non-conforming values will be allowed to flow.

SP-1 SP-2

3. For first 9 stream traffic will flow. Last stream with non-conforming values will be dropped as unacceptable frames.

4. For first 9 stream traffic will dropped. Last stream with non-conforming values will be allowed..

2.1.4 Link Aggregation Group (LAG)Test ID: TC_FUNC_4


Spirent port SP1 is connected to node via port-1.Ports 2 and 3 are connected to the ports 2 and 3 of other node. Ports 2 and 3 form part of LAG for both nodes.

Test Description:

1. Check LAG status in both nodes.

2. Send traffic from SP1.

3. Shutdown the active LAG member ports and resend traffic from SP1.

Expected Result:

1. LAG 1/1 should show ports 2 and 3 as its members and status should be up.

2. Traffic should be through to SP2.

3. Traffic should be through to SP2.

2.1.5 IGMP SnoopingTest ID: TC_FUNC_5

VME L2

VME L2

SP11 SP2

Test Configuration: C5_A

In above setup SP-1 acts as router side and SP-2 and SP-3 acts as host side. SP1 and SP2 part of VLAN 300. SP1 and SP3 form part of VLAN 400. SP1, SP2 and SP3 are connected to ports 1,2 and 3 respectively.,

Configuration :C5_B

In this setup port 1 is connected to the actual router port. SP2 and SP3 are the hosts connected to ports 2 an 3.

Test Description:

1. Send query from SP-1 (using setup C3_A)

2. Send join from SP-2 and SP-3 for different groups.( using setup C3_A)

3. Send leave from SP-3 (using setup C3_A)

4. Send join from SP-2 and SP-3 for different groups G1 and G2.( using setup C3_B).

5. Send traffic from SP-1 for group G1.

Expected Result:

VME L2SP-1 SP-2

SP-3

SP21

VME L2

ROUTER

TJ2910

SP-3

1. Query will be received by both hosts SP-2 and SP-3.

2. Both joins should be received by router side SP-1. The igmp snooping table should also be updated.

3. Leave should be received by SP-1. The IGMP Snooping table entry should be deleted after sometime(no report received in reply to group-specific query sent out).

4. Joins should be updated in the routing table of the router TJ2910 also.

5. Traffic will be forwarded only to thr hosts from which join for group G1 is received.

2.1.6 Port Protection Test ID: TC_FUNC_6


In above setup SP1, SP2 and SP3 are connected to ports 1, 2 and 3 respectively. Ports 2 and 3 are protected ports. Port 1 is unprotected (default) port. Ports 1, 2 and 3 forms part of same VLAN.

Test Description:

1. Send traffic from SP-1.

2. Send traffic from SP-2

Expected Result:

1. Traffic will be forwarded to both SP-2 and SP-3.

2. Traffic will be forwarded only to SP-1.

2.1.7 Port mirroringTest ID: TC_FUNC_7

VME L2SP-1 SP-2

SP-3


In above setup SP1, SP2 and SP3 are connected to ports 1, 2 and 3 respectively. Interface 1 and 2 form part of same vlan 500. Port2 is mirrored on to port-3.

Test Description:

1. Send vlan 500 tagged frames from SP-1.

2. Remove port mirroring and send same streams.

Expected Result:

1. identical frames are captured in SP-2 and SP-3

2. Only SP-2 receives the frames.

2.1.8 Port SecurityTest ID: TC_FUNC_8

Test Configuration:

Add static MAC addresses to be locked.

Test Description:

VME L2SP-1 SP-2

SP-3

VME L2SP-1 SP-2

1. Send traffic with MAC address that of the static locked entry.

2. Send traffic with other MAC addresses.

Expected Result:

1. Traffic will be dropped for the locked MAC address.

2. Traffic will be forwarded.

2.1.9 GVRP TESTTest ID: TC_FUNC_9

Test Configuration: c9_A

in above set-up SP-1 and SP-2 are connected with port 1 of both TJ2900 nodes. port 2 of both nodes are connected to each other. Now set gvrp adminmode on both node.

Configuration: c9_B

SP-1 TJ2900

NODE1

TJ2900

NODE2

SP-2

SP-1TJ2900

NODE1

TJ2900

NODE2SP-2

above set-up is similar to c9_A except port 3 of NODE 1 is connected with port 3 of NODE 3(TJ2910). Set gvrp adminmode up on all nodes like

(TEJOS Routing) #set gvrp adminmode

Test Description:

1) Enable gvrp interfacemode on port 2 of both nodes in configuration c9_A like :

#(TEJOS Routing) (Interface 0/2)#set gvrp interfacemode

and create vlan 100 on NODE1.

2) include port 1 of both node in vlan 100 and enable tagging for vlan 100. Send packet with tag 100 from SP-1.

3) Enable gvrp interfacemode on port 2 of all nodes in configuration c9_B and create vlan 100 on NODE 3.

4) Repeat step 2 for configuration c9_B.

Expected Result:

1) vlan 100 should be automatically created on NODE2 with vlan type dynamic(GVRP). port 2 of NODE 2 should be part of vlan 100.

2) Rx counter should increase on SP-2 and packets should be received with tag 100.

3) vlan 100 should be automatically created on NODE1 and NODE2 with vlan type dynamic(GVRP). port 2 of NODE 2 and port 3 of NODE 1 should be part of vlan 100.

TJ2910

NODE3


2.1.10 MVRP TESTTest ID: TC_FUNC_10

Test Configuration: c9_A .

Test Description:

enable mvrp on both nodes like.

(TEJOS Routing) (Config)#mvrp

1) Enable mvrp on port 2 of both nodes in configuration c9_A like :

#(TEJOS Routing) (Interface 0/2)#mvrp

and create vlan 100 on NODE1.

2) include port 1 of both node in vlan 100 and enable tagging for vlan 100. Send packet with tag 100 from SP-1.

3) see mvrp statistics on port 2 of both nodes like:

(TEJOS Routing) #show mvrp statistics 0/2

Expected Result:

1) vlan 100 should be automatically created on NODE2 with vlan type dynamic(MVRP). port 2 of NODE 2 should be part of vlan 100.


3) MVRP messages transmitted counter should increase on port 2 of NODE 1 and MVRP messages received counter increases on port 2.

2.1.11 COS TestTest ID: TC_FUNC_11


SP-1 and SP-2 are connected to ports 1 and 2 which forms part of vlan 750.

A. Dot1p CoS test

Test Description:

Configure following CLI commands

#classofservice trust <dot1p>

Create the dot1p mapping like

#classofservice dot1p-mapping 0 0








Configure bandwidth distribution for the COS queues.

#cos-queue min-bandwidth <30> <25> <20> <12> <8> <5>

1. Send 8 streams from spirent SP-1 having equal band-width with different priorities.

2. Reverse the dot1p mapping map dot1p value 0 to queue 7 and vice versa. Again send the 8 streams from spirent end.

Expected Result:

VME L2SP-1 SP-2

1. At SP-2 the stream with dot1p value 0 will have lowest drops whereas stream having dot1p value 7 will have maximum drops.

2. At SP-2 the stream with dot1p value 7 will have lowest drops whereas stream having dot1p value 0 will have maximum drops.

B. DSCP test

#classofservice trust ip-dscp

Configure the ip-dscp mapping (af11->Q0 ..... cs7->Q7)

The bandwidth distribution same as above.

Test Description:

3. Send 8 streams from spirent SP-1 having equal band-width with different dscp values.

4. Reverse the ip-dscp mapping map dscp value af11 to queue 7 and cs7 to queue 0. Again send the 8 streams from spirent end.

Expected Result:

3. At SP-2 the stream with ip-dscp value af11 will have lowest drops whereas stream having dscp value cs7 will have maximum drops.

4. At SP-2 the stream with ip-dscp value cs7 will have lowest drops whereas stream having ip-dscp value af11 will have maximum drops.

C. IP-Precedence Test

#classofservice trust ip-precedence

Configure the ip-precedence mapping ( 0->Q0 ..... 7->Q7)

The bandwidth distribution same as above.

Test Description:

5. Send 8 streams from spirent SP-1 having equal band-width with different ip-precedence values.

6. Reverse the ip-precedence mapping map precedence value 0 to queue 7 and vice versa. Again send the 8 streams from spirent end.

Expected Result:

5. At SP-2 the stream with ip-precedence value 0 will have lowest drops whereas stream having ip-precedence value 7 will have maximum drops.

6. At SP-2 the stream with ip-precedence value 7 will have lowest drops whereas stream having ip-precedence value 0 will have maximum drops.

2.1.12 DiffservTest ID: TC_FUNC_12


SP-1 and SP-2 are connected to ports 1 and 2 which forms part of vlan 750.

I. create class :

#class-map match-all <cm-1>

#match vlan 750

II. create policy

#policy-map pm1 in

#class cm1

#mark ip-precedence 7

III. apply service policy on interface

#service-policy in <pm1>

Test Description:

VME L2SP-1 SP-2

1. Send streams with parameters not matching the criteria.

2. Send streams with VLAN tagged 750.

3. Same test can be performed for ip-dscp, cos or other actions like redirect, drop

Expected Result:

1. Packets are forwarded without any ip-precedence modification.

2. Receiving packets are modified ip-precedence value is changed to 7.

3. Diffserv should work properly as per the policy actions.

2.1.13 Diffserv Simple-policerTest ID: TC_FUNC_13


#class-map match-all proto3

>match protocol ip

#policy-map SP2 in

>class proto3

>>police simple 128 32 conform-action set-prec-transmit 3 violate-action set-prec-transmit 7

Test Description:

1. Send streams with ip-precedence 0 at rate above 128 kbps.

2. set action as : "police simple 128 32 conform-action transmit violate-action drop

Send streams at rate above 128 kbps.

3.With same configuration send streams at rate below 128 kbps.

4. set action as : "police two-rate 128 32 256 64 conform-action transmit exceed-action set-cos-transmit 3 violate-action drop.

Send streams below 128 kbps.

5.With same configuration send above 128 kbps but below 256 kbps.

6.With same configuration send above 256 kbps.

Expected Result:

1. Frames received at SP-2 will have frames with ip-precedence 3 and 7 both.

2. Frames received at SP-2 with ip precedence 0 .

3. No Frames received at SP-2 .

4. Frames received at sp-2 with ip precedence 0 .

5. Frames received at sp-2 with cos 3 .

6. No Frames received.

2.1.14 Service port PolicyTest ID: TC_FUNC_13

Test Configuration: Not required

Test Description:

1. From CLI configure service port details like ip etc. Execute show service port command.

2. Try to access the node using service port ip.

Expected Result:

1. Show command show the details as configured from CLI.

2. User can log in to the node using service ip.

2.1.15 802.3ah EFM - OAM Unit TestingThe attached document describes the EFM test cases.

2.1.16 Auto – VOIP

Test ID: TC_FUNC_14


Test Description:

.Enable auto-voip on switch globally as and set speed of port 2 as 100 mbps

#(config)auto-voip

1.send 2 streams one with cos priority 1 and another stream is RTP (Real Time Packet) with utp header from SP1 both with rate 120 Mbps.

2.send 2 streams one with cos priority 6 and another stream is RTP (Real Time Packet) with utp header from SP1 both with rate 120 Mbps.

Expected Result:

1.Packet drop for Real time packet is less than cos priority 1 traffic.

2.Packet drop for Real time packet is less than cos priority 6 traffic

2.1.17 WRED

Test ID: TC_FUNC_15


Test Description:

Change speed at port 2 as 100mbps. Enable cos-queue mapping and assign user priority 7 to cos-

queue 7 and user priority 0 to cos-queue 0 . Make scheduling type for cos queue 7 is strict and for cos-queue 0 is WFD. Set queue management type WRED for queue 0 and tail-drop for queue 0(as default).

Now create diffserv policy trtcm and bind it with port 1 where commited-rate is 30 mbps and exceed rate is 80 mbps.

1.send two streams one with cos queue priority 7 and speed 90 mbps and another with cos queue priority 0 with speed 90 mbps(so that all packets should be red). Change the maximum and minimum threshold and drop probability for red packet and monitor the difference in queue size at SP2.

2. send two streams one with cos queue priority 7 and speed 90 mbps and another with cos queue priority 0 with speed 20 mbps(so that all packets should be green). Change the maximum and minimum threshold and drop probability for green packet and monitor the difference in queue size at SP2

Expected Result:

1.queue width should change accordingly as we change the maximum and minimum threshold and drop probability for red packet.

2. queue width should change accordingly as we change the maximum and minimum threshold and drop probability for green packet

2.2 Testing across Upgrade and Downgrade

2.2.1 L3 ImageTest ID: TC_REB_1

Test Configuration:

In above setup SP1, SP2 and SP3 are connected to ports 1, 2 and 3 respectively. Load L3 FCM image and configure L3 features like OSPF, IGMP, PIM and others on interfaces 1,2 and 3.

Test Description:

1. Capture the frames on spirent side SP-1,SP-2 and SP-3.

2. Load VME L2 image and reboot. Start capture on spirent side.

3. Try to configure and view L3 components.

4. Load L3 image again and capture.

Expected Result:

1. OSPF, IGMP and PIM protocol packets are captured.

2. No L3 protocol packets are captured.

3. L3 components should be strictly inaccessible from CLI.

VME L2SP-1 SP-2

SP-3

4. L3 protocol packets captured in spirent side. From CLI L3 components are accessible and configurable.

3 Appendix A: Open issues1. Stress testing is not done for VME L2 but this

is already done for TJ2910.

TJ29xx_L2_UTP

Documents

tejas networks

real time

tcfunc13 test

vlan type

set gvrp adminmode

enable gvrp

vme l2 switch

spirent ports