intelligent transport systems data network test plan v1

Intelligent Transport Systems Network Ready for Use Test Plan

Final Issue V1.2

Date 19th December 2011

Network Test Plan

Version 1.0

Version Date Author Summary of Revision

Draft 14/11/2011 Karl Wraith Initial Draft for Comment 1.0 30/11/2011 Karl Wraith First Release for Approval 1.1 06/12/2011 Karl Wraith Minor Updates 1.2 19/12/2011 Karl Wraith Test Results Completed

Network Test Plan

Version 1.0

Contents 1 Introduction .............................................................................................................................................................. 5

2 Definitions & Acronyms ......................................................................................................................................... 5

3 Overview .................................................................................................................................................................. 5

4 Network Diagram .................................................................................................................................................... 7

5 Stakeholders ........................................................................................................................................................... 8

6 Test Success Criteria ............................................................................................................................................. 8

7 Resources ............................................................................................................................................................... 8

8 Risks ......................................................................................................................................................................... 9

9 Program ................................................................................................................................................................... 9

9.1 Day 1 - 30th

November 2011 ............................................................................................................................. 9

9.2 Day 2 - 1st

December 2011 ................................................................................................................................ 9

10 Tools used in Testing ......................................................................................................................................... 9

11 Scope of Testing ............................................................................................................................................... 10

11.1 Part A Physical ................................................................................................................................................. 10

11.1.1 DEVICE TESTS .................................................................................................................................... 10

11.2 Part B Logical ................................................................................................................................................... 10

11.2.1 CIRCUIT TESTS .................................................................................................................................. 10

11.2.2 ROUTING TESTS ................................................................................................................................ 10

11.2.3 TRAFFIC TESTS .................................................................................................................................. 10

11.2.4 APPLICATION TESTS ........................................................................................................................ 10

11.2.5 MANAGEMENT TESTS ...................................................................................................................... 10

12 Test Cases PART A Physical ......................................................................................................................... 11

12.1 Field Cabinet Level Testing (Layer 2) ............................................................................................................... 11

12.2 Prerequisites ................................................................................................................................................... 11

12.3 Communications Link Testing (Layer 2) .......................................................................................................... 13

12.3.1 Prerequisites ......................................................................................................................................... 13

12.4 Node Cabinet Testing (Layer 3) ....................................................................................................................... 15

12.4.1 Prerequisites ......................................................................................................................................... 15

12.5 Communications Link Testing (Layer 3) .......................................................................................................... 17

12.5.1 Prerequisites ......................................................................................................................................... 17

13 Test Cases PART B ......................................................................................................................................... 19

13.1 CIRCUIT TESTS ................................................................................................................................................. 19

13.1.1 Throughput ............................................................................................................................................ 19

13.1.2 Latency ................................................................................................................................................... 19

13.1.3 Jitter ........................................................................................................................................................ 19

Network Test Plan

Version 1.0

13.2 ROUTING TESTS ............................................................................................................................................... 20

13.2.1 VLAN ...................................................................................................................................................... 20

13.2.2 RSTP ...................................................................................................................................................... 20

13.2.3 OSPF Adjacencies ............................................................................................................................... 21

13.2.4 TRAFFIC TESTS .................................................................................................................................. 21

13.2.5 Multicast ................................................................................................................................................. 21

13.2.6 QoS ......................................................................................................................................................... 21

13.3 APPLICATION TESTS ........................................................................................................................................ 21

13.3.1 DHCP & DNS ........................................................................................................................................ 21

13.3.2 NTP ......................................................................................................................................................... 22

13.3.3 STREAMS ............................................................................................................................................. 22

13.4 MANAGEMENT TESTS ..................................................................................................................................... 22

13.4.1 SNMP ..................................................................................................................................................... 22

13.4.2 Security .................................................................................................................................................. 22

14 APPENDIX A TEST REPORT SHEET TEMPLATES ................................................................................................... 23

15 APPENDIX 2 TEST RESULTS .................................................................................................................................. 31

16 APPENDIX 3 - 3rd Party Verification of Network ................................................................................................ 47

Network Test Plan

Version 1.0

1 Introduction

This document details the test approach to be undertaken to test the Intelligent Transport System roadside

equipment from a major roads project.

This includes an overview of the network, test activities, scope, entry and exit criteria, test deliverables,

resources and risks.

2 Definitions & Acronyms Acronym Definitions

ANPR Automatic Number Plate Recognition CCTV Closed Circuit Television DEV (system) Development (system) DHCP Dynamic Host Control Protocol DNS Domain Name Server DUT Device Under Test FP Field Processor IGMP Internet Gateway Management Protocol ITS Intelligent transport Systems LAN Local Area Network MALT Managed Advanced Localised Testing NTP Network Time Protocol POTS Plain Old Telephone Service RM Ramp Metering STREAMS Transmax Intelligent Transport System VLAN Virtual LAN VCS Vehicle Classification System VMS Variable Message Sign VSLS Variable Speed Limit Sign VSLC or VSL/LCS Variable Speed Limit / Lane Control Sign

3 Overview This document details the test approach to be undertaken to test the Intelligent Transport System roadside

equipment from within the Managed Advanced Localised Testing (MALT) facility prior to transporting the

equipment to the permanent site locations. The reason behind the MALT facility is to be able to fully

construct and debug the equipment and devices in a controlled environment and then have confidence that

field implementation will be able to be completed with minimal or no rework and or revisits to site/s.

This practise is a sound and well proven strategy for the deployment of advanced systems across the full

spectra of IT based systems.

The Motorway ITS Network consists of a series of Layer 2 Ethernet Switches in Field Cabinets that have

various ITS field devices connected to them. These switches are geographically distributed on both sides

of the new motorway and their primary purpose is to connect field devices listed below back to the TMC for

monitoring and managing the motorway. The field devices include:-

• Variable Message Signs

• Variable Speed Limit Signs

• Variable Speed Limit & Lane Control Signs

• Closed Circuit Television Cameras (CCTV)

Network Test Plan

Version 1.0

• Vehicle Detection Systems for monitoring vehicle counts, speed and type

• Automatic Number Plate Recognition

• Road Weather Monitoring

• Traffic Signals on the motorway interchanges

• Ramp Metering Systems

• Web Cameras

Excluded from this list are the Help Telephones that do not use the data network for operation but rather

are connected to the TMC via leased telecommunications lines (POTS).

The Layer 2 switches are then connected to special purpose Layer 3 switches in Node Cabinets which form

a self healing fibre optic ring around the extremities of the road system. Each Layer 2 switch has a path to

2 of the layer 3 switches thus providing an alternate path should one path fail for any reason.

The Layer 3 switches are connected to each other on the fibre optic ring and provide the backbone of the

communications network that then connects to TMC's preferred point of interconnect. The 2 main reasons

behind the layer 3 switches are to provide geographical distribution of the communications system and a

self healing ring communications path.

The following section shows the network diagram for the data communications network as formed by the

Layer 2 and Layer 3 switches without showing the field devices. As this test plan is specific to the data

communications network, the field devices will be dealt with under separate test plan/s.

The diagram shows how the MOTORWAY network is connected back to the TMC, however the TMC

functionality has been largely replicated in the MALT facility to allow thorough testing to be performed on

comparable systems and those systems are:-

• Layer 3 switch for point of interconnection to the TMC network

• DHCP Server

• DNS Server

• NTP Server

• STREAMS Server

• STREAMS Workstation

A working model of the CCTV monitoring software is not available for the testing but a simulated

workstation will be in place to verify any reconvergence times for the images when a primary network path

is disabled/failed.

Some of this testing may be verified into TMC’s DEV or Production systems upon connection of the Fibre

Optic link from the MALT facility to the TMC network. The level of this testing is yet to be confirmed.

Network Test Plan

Version 1.0

4 Network Diagram

Sub-N

etw

ork Segment BS

ub-N

etw

ork Segment D

Network Test Plan

Version 1.0

5 Stakeholders Responsible Accountable Consulted Informed

6 Test Success Criteria • 100% of tests executed

• All hardware pass self diagnostics

• All devices have appropriate / latest firmware loaded

• No network crashes during tests

• All devices passing traffic error free during tests

• Test traffic reroutes around failures as per the design criteria

• All devices can be managed and monitored for the NMS and or relevant application

7 Resources The resources needed to complete the testing and the allocation of time are as follows:-

Role Name Resource allocation

Network Test Plan

Version 1.0

8 Risks The risks to the successful completion are detailed below:-

• Availability of resources

• Equipment Supply / availability

• Completion of configuration

9 Program The testing will take place over 2 days with the first day spent checking the test environment and that the

Low Level Design(LLD) has been implemented correctly. The schedule will be:-

9.1 Day 1 - 30th November 2011

ITC Network Engineer (Test Lead) to review LLD and the implementation / configuration of the network in

the MALT facility. Test Manager and Test Lead to review this test plan, plan for the testing commencement

and trial run of the tests to be undertaken. The official test will begin on the 1st of December.

9.2 Day 2 - 1st December 2011

Pres-start activities and the documented Network Testing.

10 Tools used in Testing Tools that will be used to verify the success or failure of each test will be setup in the MALT facility. These

will include:-

• MXview the Network Management Software (NMS) for monitoring the Layer 2 and Layer 3 switch

operation and health along with the individual link statuses between each switch in the network.

• STREAMS Workstation will be used to confirm that the field devices that connect to STREAMS are

still available during the simulated outages that will be performed during the testing.

• CCTV Monitoring via the Video Encoder web interface.

• Streaming Media Monitor to detect the presence of Multicast traffic.

• Windows Command Line Tools, Ping, Tracert etc

• Fluke Metroscope Service provider Assistant Network Test Unit and Link Runner Duo as a reflector.

• Test Records will be maintained in purpose test report sheets in APPENDIX A of this document.

Network Test Plan

Version 1.0

11 Scope of Testing Types of tests will include:-

11.1 Part A Physical

This testing phase will be a tiered approach starting at field cabinet level, this could be considered the

Layer 2 switch level. The second tier is Communications channels between adjacent field cabinets or field

cabinets and the node cabinets where they are adjacent to each other, and finally the third tier is Node

cabinet level, which can be considered as the Layer 3 switch level. These tests are physical only and

network convergence times will be tested and recorded in the following sections.

11.1.1 DEVICE TESTS

• Simulated device failure

• Simulated link failure

• Power failure

11.2 Part B Logical

Tests conducted under Part B will include the following:-

11.2.1 CIRCUIT TESTS

• Throughput

• Delay

• Jitter

11.2.2 ROUTING TESTS

• VLAN

• RSTP

• Adjacencies

11.2.3 TRAFFIC TESTS

• Multicast

• QoS

11.2.4 APPLICATION TESTS

• DHCP

• DNS

• NTP

• SREAMS

11.2.5 MANAGEMENT TESTS

• SNMP

• Security

Network Test Plan

Version 1.0

12 Test Cases PART A Physical

12.1 Field Cabinet Level Testing (Layer 2)

Each field cabinet contains a layer 2 switch that passes and distributes the data associated with the control

and monitoring of the field devices such as a VSLC sign or a camera. The Layer 2 switch is an essential

component in the chain for the connection to the TMC for control and monitoring of field devices. Each

switch has 2 independent power inputs with fully isolated power supplies and as described in the Overview

section has 2 alternate communication paths to the Layer 3 communications network.

12.2 Prerequisites

Ensure the switch under test has 1 STREAMS device and 1 CCTV camera connected and monitored.

Network Test Plan

Version 1.0

The tests performed at this stage are:-

Item Description Success Criteria Power Failures Test the operation of the switch upon

removing one of the 2 power sources.

1. Verify the switch continues to run without any interruption to service as noted in the NMS.

2. Verify STREAMS device statuses haven’t changed.

3. Verify the CCTV image and control is functioning.

Restore the power and test the operation of the switch upon removing the opposite power source.




Remove the power completely to the Layer 2 Switch.

1. Verify the switches downstream recover from a brief interruption in service.

2. Verify STREAMS device statuses return to OK except for devices on the switch under full power failure.

3. Verify the CCTV image and control is functioning except for the switch under full power failure.

Restore all power. 1. Verify the switch boots and restores to normal operation as noted in the NMS.

2. Verify STREAMS device statuses return to OK.


Network Test Plan

Version 1.0

12.3 Communications Link Testing (Layer 2)

Each switch has 2 independent paths to the layer 3 backbone network and these tests are to test the

alternate routing should the primary communications path fail.

12.3.1 Prerequisites

Ensure the switch under test has 1 STREAMS device and 1 CCTV camera connected and monitored.

Network Test Plan

Version 1.0


Item Description Success Criteria Communications Link Failures Layer 2

Test the operation of the switch upon removing Layer 2 fibre optic connection of the current routed Path.

1. Verify the blocked becomes active and switch reconverges as noted in the NMS.

2. Verify other switches downstream reconverge and upstream are not affected.

3. Verify STREAMS device statuses haven’t changed after reconvergence.

4. Verify the CCTV image and control is functioning after reconvergence.

Restore the upstream Layer 2 fibre optic connections and test the operation of the switch upon removing the downstream Fibre Optic Path.

1. Verify the switch continues to run with a brief interruption to service as noted in the NMS.

2. Verify switches in the downstream path experience a brief interruption in service.



Remove both Layer 2 Fibre Optic connections.

1. Verify switches in the downstream path experience a brief interruption in service.

2. Verify STREAMS device statuses return to OK except for devices on the switch under full communications failure.

3. Verify the CCTV image and control is functioning except for the switch under full power failure.

Restore all Fibre Optic connections 1. Verify the switch boots and restores to normal operation as noted in the NMS.



Network Test Plan

Version 1.0

12.4 Node Cabinet Testing (Layer 3)

Each node cabinet contains a layer 3 switch that passes and distributes the data from the field network

layer 2 switches. The Layer 3 switch is an essential component in the chain for the connection to the TMC

for control and monitoring of field devices but a single failure of a layer 2 switch should only result in a brief

outage for reconvergence of the data network routing, with one exception. As mentioned in the Overview

above “It must be noted though that while the MOTORWAY network as a whole has a redundant

architecture there is a single point of failure between this network and the point of interconnect (POI) to the

TMC network this being the link between the MOTORWAY node cabinet (W134) and the TMC Node used

as the Point of Interconnect.” Thus a full failure of the layer 3 switch in node cabinet W134 would mean a

total loss of the MOTORWAY network to the TMC network.

Each switch has 2 independent power inputs with fully isolated power supplies and as described in the

Overview section are connected to each other on a self healing fibre optic ring and provide the backbone of

the communications network that then connects to TMC’s preferred point of interconnect.


Ensure a layer 2 switch that is connected to the layer 3 switch under test has 1 STREAMS device and 1

CCTV camera connected and monitored.

Network Test Plan

Version 1.0

The tests performed at this level will include:-

Item Description Success Criteria Power Failures Test the operation of the switch upon

removing one of the 2 power sources.




Restore the power and test the operation of the switch upon removing the opposite power source.




Remove the power completely to the Layer 3 Switch. (for this test only node W-134 (POI) will be excluded)

1. Verify network reconverges and all switches are back in service in NMS.

2. Verify STREAMS device statuses return to OK except for devices on the switch under full power failure.


Restore all power. 4. Verify the switch boots and restores to normal operation as noted in the NMS.



Network Test Plan

Version 1.0

12.5 Communications Link Testing (Layer 3)

Each switch sits on a redundant fibre optic ring has 2 independent paths to its neighbouring layer 3 node

switch and these tests are to test the alternate routing should the primary communications path fail.


Ensure a layer 2 switch that is connected to the layer 3 switch under test has 1 STREAMS device and 1

CCTV camera connected and monitored.

Network Test Plan

Version 1.0


Item Description Success Criteria Communications Link Failures Layer 3

Test the operation of the switch upon removing one Layer 3 fibre optic connection of the current routed Path. In the example remove the link in Segment A. Segment B should now become active.

1. Verify network reconverges and all switches are back in service in NMS.

2. Verify other switches in the network are not affected or reconverge.

3. Verify STREAMS device statuses reconverge.

4. Verify the CCTV image and control returns to OK.

Test the operation of the switch upon removing the 2nd Layer 3 fibre optic connection of the current routed Path. In the example remove the link in Segment B. (Segment B should have become active after step 1 above)

1. Verify the switch fails as noted in the NMS.

2. Verify L2 switches in the reconverge after a brief interruption in service.


4. Verify the CCTV image and control returns to OK.

Restore all Fibre Optic connections 1. Verify the restores to normal operation as noted in the NMS.

2. Verify the links return to service and that Segment B become the blocking link.



Network Test Plan

Version 1.0

13 Test Cases PART B

13.1 CIRCUIT TESTS

L3-W134

Fluke Link

Runner

Fluke

MetroScope

Gateway

Router

L3 ITS Field

Router

Layer 2 Sub Network Switches

Circuit Tests Schematic

Figure 2 Circuit Tests Scenario

13.1.1 Throughput

Using the Fluke MetroScope the throughput between two endpoints will be measured. One endpoint

connected to a layer 2 switch in the midpoint of each of the 4 sub-networks will have the throughput test

completed between it and the gateway router with the results recorded. The throughput will be compared

to the expected values in the results.

Setup an endpoint on the midpoint switch and the MetroScope on the gateway router, then run the

Throughput tests for both TCP and UDP packets using packet sizes of 100 bytes and 1000bytes. 64, 128,

256, 512, 1024, 1280, 1518

This test may be repeated once connection to the TMC network is achieved.

13.1.2 Latency

Using the Fluke MetroScope the Round Trip Time (RTT) or latency between two endpoints will be

measured. One endpoint connected to a layer 2 switch in the midpoint in each of the 4 sub-networks will

have the RTT test completed between it and the gateway router with the results recorded. The RTT will be

compared to the expected values in the results.

Setup an endpoint computer on the midpoint switch and MetroScope on the gateway router, and run the

Response Time tests for both TCP and UDP packets with 10 iterations at a data size of 100bytes.

This test may be repeated once connection to the TMC network is achieved.

13.1.3 Jitter

From the above Latency test review the test results to compare the variance in response times. These

results will be captured in the test report sheets in Appendix A.

Network Test Plan

Version 1.0

13.2 ROUTING TESTS

Blocking Port

Break Link

Blocked Port

ReconvergesLink Disconnected

Figure 3 Routing Tests Scenario

13.2.1 VLAN

Ensure VLANs are configured on each port as per the design document. No Inter-VLAN routing has been

configured.

13.2.2 RSTP

Rapid Spanning Tree Protocol (RSTP) provides the mechanism for an alternate path for the layer 2

switches in the event of a path failure. Using the Moxa MXview application confirm that all switches are

present and all links operational and confirm the location of the blocked link. Fail an active link in the

selected network chain and confirm that

• The link shows failed

• The switches reconverge through the previously blocked link

• Capture and record the results via MXview Event/All export facility.

• Record Network Convergence Times through the MetroScope reports.

Restore the link and observe the reconvergence in MXview back to the Customeral state.

Network Test Plan

Version 1.0

13.2.3 OSPF Adjacencies

Using the MOXA MX View confirm that OSPF is configured correctly and review the OSPF Neighbour

Table Entries for each of the 4 Nodes.

13.2.4 TRAFFIC TESTS

13.2.5 Multicast

Confirm Multicast Filtering is enabled using IGMP snooping and that the Layer 3 switches are configured as

the querier.

Using Streaming Media Monitor test for Multicast streams on Channels 1 and 2.

The indicator lamp will show RED if the stream is in keep alive mode (about 2% bandwidth), YELLOW if the bandwidth has dropped below 80% of normal (indicates frozen or static image in streaming video), and GREEN if the bandwidth is normal, and DARK if no bandwidth is present. A Multicast Traffic Generator will inject into a switch port set for IGMP sufficient traffic to test the function and monitor the network response.

13.2.6 QoS

QoS will be tested using a Fluke Test Instrument and the result will be tabled directly from the unit into the

Report Sheets.

13.3 APPLICATION TESTS

13.3.1 DHCP & DNS

The Transmax Field Processors use DHCP to attain IP addresses and DNS name server settings.

Remove and restore the power from an FP and confirm the FP has received an IP address and name

server information. Use the following commands:-

IP Address - cat /etc/sysconfig/networking/ifcfg-eth0

DNS (name server) - cat /etc/sysconfig/network

Confirm that the FP has resolved the STREAMS server name and appears in the STREAMS explorer.

Network Test Plan

Version 1.0

13.3.2 NTP

NTP is used to synchronise all the network clocks and the operation can be confirmed from the Transmax

Field Processor.

Use the following command:-

ntpq –np

Confirm that the FP appears in STREAMS explorer and that the clock field is showing OK.

13.3.3 STREAMS

Confirm using the STREAMS workstation that:-

• all FPs have an IP address;

• all the FPs are available and in the OK state;

• that the clock state is OK;

• the correct package is installed.

13.4 MANAGEMENT TESTS

13.4.1 SNMP

SNMP monitoring is enabled through the MXView application which is used by the NMS to monitor the

network switches. At the time of writing there were no published Trap Server/s addresses, Authentication

or Encryption settings provided. Thus this test will be based on the availability of the network switches in

the MOXA MXview application.

13.4.2 Security

Ensure all switches have a password set as per the separately supplied details for username and

password.

Network Test Plan

Version 1.0

14 APPENDIX A TEST REPORT SHEET TEMPLATES

Test Report Sheets Templates are included for each generic Device Under Test (DUT). The reports will be printed out

separately and completed during the testing for later collection and verification. Copies will be scanned and

attached the QA system as project records.

Network Test Plan Motorway Upgrade - Motorway, Customer

Version 1.0

For Contractor For Client

Inspector..............................................................................Date..................... Inspector..............................................................................Date.......................

Layer 2 Switch Physical Tests Report Sheet

Device Under Test Cabinet Results

12.0 Test Description Switch STREAMS CCTV Acc Rej N/A Comment Reject

Resolved Date

12.2 Prerequisites L2 Power

12.2a Test 1 – Remove PS1 Status unchanged

Devices unchanged

CCTV unchanged

12.2b Test 2 – Restore PS1 & Remove PS2

Status unchanged

STREAMS unchanged

CCTV unchanged

12.2c Test 3 – Remove PS1 & PS2 Downstream switch/es reconverge

Downstream Devices reconverge

Downstream CCTV reconverges

12.2d Restore PS1 & PS2 All status OK All status OK All status OK

12.3 Prerequisites L2 Comms

12.3a Comms Failure Test 1 – Remove L2 Link Upstream

Link Switch Downstream Devices reconverge


Recon Recon

12.3b Comms Failure Test 2 – Remove L2 Link Downstream

Link Switch Downstream Devices reconverge


Recon Recon

12.3c Comms Failure Test 3 – Remove both L2 Links

Link Switch Only non switch connected devices reconverge

Only non switch connected CCTV reconverge

Fail

12.3d Comms Failure Test 4 – Restore all L2 Links

All status OK All status OK All status OK


Version 1.0



Layer 3 Switch Physical Tests Report Sheet

Device Under Test Cabinet Results

MIM767L301 W160 12.0 Test Description Switch STREAMS CCTV Acc Rej N/A Comment Reject

Resolved Date

12.4 Prerequisites L3 Power

12.4a Test 1 – Remove PS1 Status unchanged

Devices unchanged

CCTV unchanged

�

12.4b Test 2 – Restore PS1 & Remove PS2

Status unchanged

STREAMS unchanged

CCTV unchanged

�

12.4c Test 3 – Remove PS1 & PS2 L3 network reconverges

All devices reconverge

All CCTV reconverges

�

12.4d Restore PS1 & PS2 All status OK All status OK All status OK �

12.5 Prerequisites L3 Comms R=Recon F=Fail

12.5a Comms Failure Test 1 – Remove L3 Link Upstream

Link L3 L2 All Devices reconverge


�

Recon R R

12.5b Comms Failure Test 2 – Remove L3 Link Downstream

Link L3 L2 All Devices reconverge


�

Recon F R

12.5c Comms Failure Test 3 – Restore all L3 Links

All status OK All status OK All status OK �


Version 1.0



Circuit Tests Report Sheet

Endpoints Results

13.0 Test Description 100 Bytes 1000 Bytes Expected

Value Acc Rej N/A Comment Reject

Resolved Date

13.1.1a Throughput TCP

13.1.1b Throughput UDP

100 Bytes (ms)

100 Bytes (ms)

Expected Value

13.1.2a Latency TCP

13.1.2b Latency UDP

% Variance (=H-L)

% Variance (=H-L)

Expected

13.1.3a Jitter TCP

13.1.3b Jitter UDP

Frame Size Frames Lost

13.1.3c Loss

Frame Size Bit Error Rate

13.1.3d BERT


Version 1.0



Routing Tests Report Sheet

Device Under Test Results

13.2 Test Description VLAN 500

(Mngmt vlan) VLAN 504 VLANs

501,502,503 Acc Rej N/A Comment Reject

Resolved Date

13.2.1 VLAN Switch Ports Switch Ports Trunked

2/1 2/2-2/8 1/1-1/2

13.2.2 RSTP Network Reconverge Y/N

Reconvergence time - link down

Reconvergence time – link up

Switch ID

Interface Name

IP address

13.2.3a OSPF

MIM755L301 OSPF1 10.1.1.1

MIM767L301 OSPF1 10.1.1.2

MIM781L301 OSPF1 10.1.1.3

MIM7 L301 OSPF1 10.1.1.4

Neighbour ID Address State

13.2.3b OSPF Neighbours MIM755L301

10.1.1.2 10.1.1.2 Full/Backup

10.1.1.3 10.1.1.3 2Way/DROther

10.1.1.4 10.1.1.4 Full/DR


Version 1.0



Traffic Tests Report Sheet


..............................................................

13.2 Test Description Acc Rej N/A Comment Reject Resolved

Date

13.2.5 Multicast

Monitor for Multicast Traffic

Storm Protection

13.2.6 QoS

See results from Fluke Test Attached separately


Version 1.0



Application Tests Report Sheet


13.3

Test Description Field Processor IP Address Acc Rej N/A Comment Reject

Resolved Date

Application Query Used Result

13.3.1a DHCP address issued cat /etc/sysconfig/networking/ifcfg-eth0

13.3.1b DNS cat /etc/resolv.conf

13.3.2 NTP ntpq -np

13.3.3 STREAMS IP State Clock Pkg


Version 1.0



SNMP & Security Tests Report Sheet


Full Networ 13.3

Test Description Result Y/N No of

Switches Acc Rej N/A Comment

Reject Resolved

Date

L3 L2

13.4.1a SNMP Switch availability in MXview

13.4.1b SNMP Settings correct

13.4.2 Security Password Audit L3 L2

Expected 4 30

Verified


Version 1.0

15 APPENDIX 2 TEST RESULTS

Completed test results and reports are to be attached in this section post completion of the works.


Version 1.0

Layer 2 Physical Tests


Version 1.0

Layer 3 Physical Tests


Version 1.0

Logical Tests – W199

Circuit Tests - Throughput, Latency, Frame Loss, Jitter and BERT


Version 1.0




Version 1.0

Logical Tests – E196



Version 1.0




Version 1.0


Routing Tests – VLAN, RSTP and OSPF


Version 1.0




Version 1.0

Logical Tests – Convergence Times Summary


Version 1.0

Logical Tests – OSPF Neighbour Table


Version 1.0

Logical Tests

Traffic Tests – Multicast and QoS


Version 1.0

Logical Tests

Application Tests – DHCP, DNS, NTP and STREAMS


Version 1.0

Logical Tests

Security and SNMP


Version 1.0

16 APPENDIX 3 - 3rd Party Verification of Network

intelligent transport systems data network test plan v1

Documents

network test plan version

karl wraith test results

karl wraith initial

karl wraith minor updates

network diagram

test success criteria

use test plan final

scope of testing