Engineering Procedure

SAEP-701 18 September 2014

Plant Ethernet Network Test Procedure
Document Responsibility: Plants Networks Standards Committee

Saudi Aramco DeskTop Standards

Table of Contents

1 Scope................................................................. 2
2 Conflicts and Deviations.................................... 2
3 Applicable Documents....................................... 2
4 Test Cases......................................................... 4

Appendix A – Test Procedure Worksheet

for Local Area Network................................. 9
Appendix B – Test Procedure Worksheet
for Remote Site Network Connectivity....... 20

Previous Issue: 18 July 2012 Next Planned Update: 6 September 2016

Revised paragraphs are indicated in the right margin Page 1 of 50
Primary contact: Almadi, Soloman Musa on 966-3-8801357

Copyright©Saudi Aramco 2014. All rights reserved.

Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

1 Scope

Scope of this document covers test procedure for Ethernet networks that are part of
Saudi Aramco industrial and process automation applications operating environment.
This document may be utilized as part of, but not limited to, Integrated Factory
Acceptance Test (IFAT) and Site Acceptance Test (SAT) work flow when deploying
Closed Circuit Television (CCTV), Intelligent Field (I-Field), Power System
Automation, Supervisory Control and Data Acquisition System (SCADA), and remote
site network connectivity in Saudi Aramco.

2 Conflicts and Deviations

2.1 Any conflicts between this Procedure and other applicable Saudi Aramco
Engineering Procedures (SAEPs), Saudi Aramco Engineering Standards (SAESs),
Saudi Aramco Materials System Specifications (SAMSSs), Saudi Aramco
Standard Drawings (SASDs), or industry standards, codes, and forms shall be
resolved in writing by the Company or Buyer Representative through the
Manager, Process & Control Systems Department of Saudi Aramco, Dhahran.

Test cases that may not be applicable to the network in question may be
eliminated with proponents' approval.

2.2 Direct all requests to deviate from this Procedure in writing to the Company or
Buyer Representative, who shall follow internal company procedure SAEP-302
and forward such requests to the Manager, Process & Control Systems
Department of Saudi Aramco, Dhahran.

3 Applicable Documents

All referenced documents and similar material or equipment supplied shall be

considered part of this Procedure to the extent specified herein and shall be of the latest
issue (including all revisions, addenda, and supplements), unless stated otherwise.

3.1 Saudi Aramco References

Saudi Aramco Engineering Procedures

SAEP-302 Instructions for Obtaining a Waiver of a Mandatory
Saudi Aramco Engineering Requirement
SAEP-1630 Preparation of Integration Test Procedure Document
SAEP-1634 Factory Acceptance Test
SAEP-1638 Instructions Site Acceptance Test Plan

Page 2 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

Saudi Aramco Engineering Standards

SAES-P-126 Power Monitoring and Control System
SAES-T-634 Telecommunications – Cable Testing and Acceptance

Saudi Aramco Materials System Specifications

23-SAMSS-010 Distributed Control Systems
23-SAMSS-701 Industrial Ethernet Switch Specifications

Other Document
FSD Functional Specification Document for the Network in
Question

3.2 Industry Codes and Standards

Institute of Electrical and Electronics Engineers

IEEE 1588 Standard for a Precision Clock Synchronization
Protocol for Networked Measurement and Control
Systems
IEEE 802.1D This specification defines the Spanning Tree Protocol
IEEE 802.1P This specification defines QoS tagging and port-based
priority
IEEE 802.1Q This specification defines the standard for frame
tagging and VLAN trunking
IEEE 802.1w This specification defines Rapid Spanning Tree
Protocol
IEEE 802.1X This specification defines the standard for port-based
Network Access Control
IEEE 802.3 This specification defines the Ethernet group
IEEE 802.3u This specification defines the Fast Ethernet
IEEE 802.3z This specification defines the Gigabit Ethernet
(fiber-based)
IEEE 802.3ab This specification defines the standard for Gigabit
Ethernet (copper-based; unshielded twisted pair
(UTP) category 5, 5e, or 6 cabling)
IEEE 802.3ad This specification defines the standard for link
aggregation
IEEE 802.3x This specification defines the full duplex flow control

Page 3 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

1000Base-SX Multi-mode Fiber using 62.5 and 50-micron core; uses

850 nano-meter laser and can go up to 220 meters
with 62.5-micron, 550 meters with 50-micron
1000BaseLX Single-mode fiber that uses a 9-micron core and
1310 nanometer laser, and can go from
3 kilometers up to 10 kilometers
1000BaseLH/ZX 1000 BASE- LH/ZX Operates on Ordinary Single-
Mode Fiber Optic Link and Spans up to 43.4 miles
(70 km) long
IETF RFC 2544 Benchmarking Methodology for Network Interconnect
Devices
IETF RFC 2889 Benchmarking Methodology for LAN Switching Devices
IETF RFC 1323 TCP Extensions for High Performance
IETF RFC 4445 PCR Jitter: Overall Program Clock Reference Jitter
IETF RFC-3393 IP Packet Delay Variation Metric for IP Performance
Metrics (IPPM)
IETF RFC-791 Internet Protocol
IETF RFC-2475 Architecture for Differentiated Services
ITU-T Y.1541 Network Performance Objectives for IP Based Services
ITU G.1050 Network Model for Evaluating Multimedia
Transmission Performance over Internet Protocol
ITU-T J.241 QoS Measurement Methods for Video over Broadband
IP
ITU-T G.821 Error Performance of an International Digital
Connection Operating at a Bit Rate below the
Primary Rate and Forming Part of an Integrated
Services Digital Network
ITU-T G.826 End-to-end Error Performance Parameters and
Objectives for International, Constant Bit Rate
Digital Paths and Connections

4 Test Cases

The test cases shall confirm the Ethernet switch capabilities in support of process
automaton traffic in Saudi Aramco. Test cases are divided into three major categories.
These are: Test case 4.1 thru 4.4 covering Ethernet switching node capabilities; Test
case 4.5 addressing the Network Management System; and Test case 4.5 addressing the
end-to-end network testing. The test cases shall be conducted in collaboration with the

Page 4 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

vendor. The test tools shall be calibrated and test team members are recommended to
be trained in network and system testing. The Ethernet frame utilized in the traffic test
tool generator shall be 1518 Bytes.

4.1 Switch Interface Test Cases

4.1.1 Test switch port interface for auto-negotiate the data rate, the duplex
settings (full/half) and auto-crossover (MDI/MDX) functionality.

Expected Results: Confirm the capability (Pass/Fail)

4.1.2 Test case for industrial-grade RJ-45 connectors; i.e., modified office
type RJ-45 connectors so that it can withstand the harsh environment.

Expected Results: Confirm the capability (Pass/Fail)

4.1.3 Test case for manual configuration of port speed selection (10 Mbps,
100 Mbps, or 1 Gbps)

Expected Results: Confirm the capability (Pass/Fail)

4.1.4 Test case for port mirroring.

Expected Results: Confirm the capability (Pass/Fail)

4.1.5 Test case for the different optical interfaces [Small-Form-Factor-

Pluggable (SFP)] LX or LH with SC or LC connector (Single mode)

Expected Results: Confirm the capability (Pass/Fail)

4.1.6 Test case for 100BASE-TX ports standard 8 pin RJ-45 UTP
connectors.

Expected Results: Confirm the capability (Pass/Fail)

4.2 Switch Network Capabilities

4.2.2 Test case for supporting IEEE 1588 standard if required (i.e., Power
System Automation).

Expected Results: Confirm the capability (Pass/Fail)

4.2.3 Test case for IEEE 802.1p QoS standard for priority queues and strict
priority scheduling: classification, policing/metering, and marking
functions on per port basis at ingress and queuing/scheduling functions
at egress

Page 5 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

Expected Results: Confirm the capability (Pass/Fail)

4.2.4 Test case for IEEE 802.1Q VLANs configurations

Expected Results: Confirm the capability (Pass/Fail)

4.2.5 Test case for port aggregation

Expected Results: Confirm the capability (Pass/Fail)

4.2.6 Test case for broadcast or multicast threshold filtering

Expected Results: Confirm the capability (Pass/Fail)

4.3 Switch Network Performance (Delay, Throughput)

4.3.1 Test cases for typical throughput delays (port-in to port-out for a 1518
byte Ethernet frame of:
a. 10 BASE-T: 1.3 ms,
b. 100 BASE-T: 150 µs,
c. and Gigabit Ethernet: 30 µs.

Expected Results: Confirm the capability (Pass/Fail)

4.3.3 Test cases for network ring protection type (Spanning Tree Protocol -
STP; Rapid Spanning Tree Protocol-RSTP; and vendor specific ring
protection) based on a 50 switch nodes network.

Expected Results: Confirm the capability (Pass/Fail)

4.3.4 Test case for ring coupling protection

Expected Results: Confirm the capability (Pass/Fail)

4.3.5 Test cases for network dual homing protection

Expected Results: Confirm the capability (Pass/Fail)

4.4 Switch Capabilities

4.4.1 Test case for supporting physical storage/retrieval of switch

configuration.

Expected Results: Confirm the capability (Pass/Fail)

Page 6 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

4.4.2 Test case for operating Temperature or Vendor Certification Report

shall comply to 23-SAMSS-701.

Expected Results: Confirm the capability (Pass/Fail)

4.4.3 Test case for Humidity or Vendor Certification Report shall comply
with 23-SAMSS-701.

Expected Results: Confirm the capability (Pass/Fail)

4.4.4 Test case to support the following security functionalities:

a) The ability to disable/enable spare/ maintenance or console ports
to prevent casual access.
b) Port security to control access based on the MAC address
c) Access control list to control access based on IP address
d) VLANs
e) Radius authentication
f) SSL/SSH
g) Firewall and VPN

Expected Results: Confirm the capability (Pass/Fail)

4.5 Network Management System

The Expected Results for these test cases is: Confirm the capability
(Pass/Fail/list limitations)

4.5.1 Test NMS software ability to provide accesses to any SNMP data
identified and supported by the standard SNMP protocol from the
vendor switch for the network in question. This may include: Test
NMS software ability to monitor the link state of each port of the
switch, the amount of traffic being carried by the switch on a port-by-
port basis, the internal temperature of the switch, alarms relay output
for port break, power failure, number of supported devices, and other
SNMP data elements from the managed switches.

4.5.2 Test the NMS software ability to collect SNMP information and
provides calculated values such as bandwidth utilization.

4.5.3 Test the NMS software OPC2.0 rev compliance.

Page 7 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

4.5.4 Test the NMS software ability to support Auto-Discovery function for
detection of new devices within the network.

4.5.5 Test case for supporting SNMP and GUI web base as means for remote
monitoring and configuration.

4.5.6 Test case for mapping diagnostic LED indicators for 10/100/1000 Mbps
Link Activity and port failure.

4.5.7 Test configuration and diagnostics capabilities through the switch

console port.

4.5.8 Test the switch ability to encrypt passwords to counteract IP spoofing

and provide secure browser sessions.

4.6 End-to-End Network Test Cases

4.6.1 Appendix A: Testing local area network

4.6.2 Appendix B: Testing remote network

Revision Summary
6 September 2011 New Saudi Aramco Engineering Procedure.
18 July 2012 Editorial revision to change the primary contact.
18 September 2014 Editorial revision to transfer this engineering document from Communications Standards
Committee to be under the newly established Plants Networks Standards Committee.

Page 8 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

Appendix A – Test Procedure Worksheet for Local Area Network

NOTES: Referred to in this document:

1) Industrial Local Area Network

i. The Local Area Network encompasses all Ethernet network types using
Fiber optic cables that support industrial and process applications.

ii. The Local Network design may have a fault-tolerant network. The user
may ignore those test cases that are not applicable or are not part of the
acquired system specifications.

Page 9 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

Appli-
# Test Procedure Expected Results Results
cable
Initial Conditions
1 Existing network traffic load Expected Results: Display
(Mbps) at the highest and capture link utilization
congested node
Rational: Establish a baseline
for the traffic load in steady
state operation
2 System and Network in Expected Results: Application
steady state, initiate a Response time should be
command to assess process below 1 second
control application response
time. Rational: Comply Saudi
Aramco SAMSS
(e.g., 23-SAMSS-010) and
establish a baseline for the
application response time in
steady state operation
3 System and Network in Expected Results: Network
steady state, initiate a ping response time should be below
command to assess network 2 milliseconds
response time
Rational: Local area network
response time is 1 millisecond.
Assess network delay impact
on the application.
4 System and Network in Expected Results: Should be
steady state, indentify packet zero packet loss under normal
loss or Bit Error Rate load

Rational: Communication
protocol is based on TCP/IP so
it is expected to have zero
packet loss during steady state.
5 System and Network in Expected Results: Display
steady state, indentify traffic and capture traffic mix
mix by service type (TCP,
UDP, SNMP, IP, ICMP, etc.) Rational: “Information” to
understand traffic behavior of
the network.

Page 10 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

Appli-
# Test Procedure Expected Results Results
cable
6 System and Network in Expected Results: Broadcast
steady state, indentify should be zero, Unicast should
message type packet mix be the most.
Unicast, Broadcast, Multicast
Rational: Control system
traffic is based on unicast or
multicast. Broadcast message
are a source of overloading the
network.
7 System and Network is Expected Results: Zero
running steady state, unplug impact on the application and
Controller Primary Interface visualization

Rational: Test Ethernet

switch’s switch-over time and
this is typically sub second (i.e.,
transparent to the application)
8 System and Network is Expected Results: Controller
running steady state, unplug communication and
Controller Primary Interface visualization lost immediately
and backup interface
Rational: Test Ethernet switch
communication restorability.
9 System and Network is Expected Results: Controller
running steady state, re-plug communication and
Controller Primary Interface visualization reappear in less
and backup interface than one (1) second

Rational: Test Ethernet switch

communication restorability
10 System and Network is Expected Results: The new
running steady state, change timing should appear in HMI,
NTP server time controller, servers, and
synchronizations time source switches

Rational: Test remote

synchronization for different
connected elements via NTP.

Page 11 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

Appli-
# Test Procedure Expected Results Results
cable
11 Layer 2 Network is running Expected Results: Three (3)
steady state, impose a one items to track:
(1) Node failure and observe
network switch-over time a) Switch-over time should be
below 1 second.

b) Packet loss needs to be

identified

c) Application impacts need to

be identified.

Rational: Test to comply with

the minimum requirements for
Ethernet switch for Application
Material specification and
Application standard
requirements
12 Layer 2 Network is running Expected Results: Three (3)
steady state, impose a one items to track:
(1) Link failure and observe
link recovery time. a) Link recovery time should
be below 1 second.

b) Packet loss needs to be

identified.

c) Application impacts need to

be identified.

Rational: Test to comply with

the minimum requirements for
Ethernet switch for Application
Material specification and
Application standard
requirements

Page 12 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

Appli-
# Test Procedure Expected Results Results
cable
13 Layer 2 Network is running Expected Results: Three (3)
steady state, impose a two (2) items to track:
Node failures (one at each
domain) and observe network a) Switch-over time should be
switch-over time below 1 second.

b) Packet loss needs to be

identified.

c) Application impacts need to

be identified.

Rational: Test to comply with

the minimum requirements for
Ethernet switch for Application
Material specification and
Application standard
requirements
14 Layer 2 Network is running Expected Results: Three (3)
steady state, impose a two (2) items to track:
Links failures (one at each
domain) and observe network a) Link recovery time should
link recovery time be below 1 second.

b) Packet loss needs to be

identified.

c) Application impacts need to

be identified.

Rational: Test to comply with

the minimum requirements for
Ethernet switch for Application
Material specification and
Application standard
requirements

Page 13 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

Appli-
# Test Procedure Expected Results Results
cable
15 Verify switch unmanaged Expected Results:
capabilities.  Switch access via HTTP
(HHTPS)
 Navigate switch port
configuration
 SNMP v3 capable
 MAC address filters for port
access
Rational: Test to comply with
the minimum requirements for
Ethernet switch for Application
Material specification and
Application standard
requirements
16 Perform a loop test by Expected Results: Network
creating a L2 loop shall handle the loop by putting
one link in non-forwarding state
and continue normal operation

Rational: Test network

topology resiliency to loop if the
architecture calls for this type of
configuration.
17 Randomly remove a power Expected Results: Switch
supply then reconnect the should continue on auxiliary
power supply supply

Rational: Test to comply with

the minimum requirements for
Ethernet switch for Application
Material specification and
Application standard
requirements

Page 14 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

Appli-
# Test Procedure Expected Results Results
cable
18 Randomly remove switch Expected Results: Switch
fabric module then insert the should continue on auxiliary
module back (For redundant supply
switch fabric switches)
Rational: Test to comply with
the minimum requirements for
Ethernet switch for Application
Material specification and
Application standard
requirements
19 Connect to random port Expected Results: Port shall
be disabled

Rational: Test to comply with

the minimum requirements for
network security.
20 Connect a PC to an uplink Expected Results: Port shall
port be configured as trunk and no
communication shall happen

Rational: Test to comply with

the minimum requirements for
Ethernet switch for Application
Material specification and
Application standard
requirements
21 Connect to switch with a Expected Results: Machine
DHCP client shall not get a DHCP address

Rational: Test to comply with

the minimum requirements for
network security.

Page 15 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

Appli-
# Test Procedure Expected Results Results
cable
Traffic Loading Test Cases
22 System and Network in a Expected Results: Display
steady state, impose and capture link utilization
maximum alarm flooding
condition Rational: Test to comply with
the minimum requirements for
network security and
performance.
23 Simulate a broadcast storm Expected Results: The
by pinging the “entire” network should handle the
network using large buffer broadcast. Operator’s
size, while monitoring workstation should continue
operator’s screen updates. see plant process.

Example: ping 192.168.1.255 NMS, if configured with

–l 32000 -t appropriate threshold,
should generate an alert for
abnormal network
utilization.
Rational: Test to comply with
the minimum requirements for
Ethernet switch for Application
Material specification and
Application standard
requirements

Page 16 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

Appli-
# Test Procedure Expected Results Results
cable
24 System and Network in Expected Results:
steady state, initiate a UDP  Utilization should be 30%
traffic load at 30% of available plus existing traffic load
bandwidth. Identify: (test case 1)
 Utilization  Delay should be below
 Delay 2 millisecond
 Jitter  Jitter be below 1 millisecond
 Packet Loss  Packet Loss should be none
 Application Response time
should be below 1 second

Rational: Test to comply with

the minimum requirements for
Ethernet switch for Application
Material specification and
Application standard
requirements
25 System and Network in Expected Results:
steady state, initiate a UDP  Utilization should be 70%
traffic load at 70% of available plus existing traffic load
bandwidth. Identify: (test case 1)
 Utilization  Delay should be below
 Delay 2 millisecond
 Jitter  Jitter be below 1 millisecond
 Packet Loss  Packet Loss should be none
 Application Response time
should be below 1 second

Rational: Assess loading

impacts on DCS traffic.

Page 17 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

Appli-
# Test Procedure Expected Results Results
cable
26 System and Network in Expected Results:
steady state, initiate a UDP  Utilization should be 100%
traffic load at 100% of plus existing traffic load
available bandwidth. Identify: (test case 1). Capture
 Utilization  Delay
 Delay  Jitter
 Jitter  Packet Loss
 Packet Loss  Application Response time

Rational: Assess loading

impacts on Application traffic.
27 System and Network in Expected Results:
steady state, initiate a TCP  Utilization should be 30%
traffic load at 30% of available plus existing traffic load
bandwidth. Identify: (test case 1)
 Utilization  Delay should be below
 Delay 2 millisecond
 Jitter  Jitter be below 1 millisecond
 Packet Loss  Packet Loss should be none
 Application Response time
should be below 1 second

Rational: Assess loading

impacts on DCS traffic.
28 System and Network in Expected Results:
steady state, initiate a TCP  Utilization should be 70%
traffic load at 70% of available plus existing traffic load
bandwidth. Identify: (test case 1)
 Utilization  Delay should be below
 Delay 2 millisecond
 Jitter  Jitter be below 1 millisecond
 Packet Loss  Packet Loss should be none
 Application Response time
should be below 1 second

Rational: Assess loading

impacts on Application traffic.

Page 18 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

Appli-
# Test Procedure Expected Results Results
cable
29 System and Network in Expected Results:
steady state, initiate a TCP  Utilization should be 100%
traffic load at 100% of plus existing traffic load
available bandwidth. Identify: (test case 1). Capture
 Utilization  Delay
 Delay  Jitter
 Jitter  Packet Loss
 Packet Loss  Application Response time

Rational: Assess loading

impacts on Application traffic.
30 Verify the separation of every Expected Results: PING
VLAN Subnet from each site command with each plant area
going to/from Core Site. should be successful and cross
PING command from the different plant areas should not
plant area 1 to plant area 2 processed.
and PING command with
each plant area Rational: Test to comply with
the minimum requirements for
network security.
31 Confirm the Equipment Expected Result: Equipment
Inventory as listed on the inventory on the site should be
Delivery Sheet and record the complete and should
serial number for each correspond to the number and
equipment, network topology model as indicated on the
maps, etc. Delivery Sheet.

Page 19 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

Appendix B – Test Procedure Worksheet

for Remote Site Network Connectivity

NOTES: Referred to in this document:

1) Core Ethernet switch (Core Site):

i. The core switch referred to in this document is the switch that located at the
core site and connects all different remote switches to the industrial and
process automation applications and support system servers (e.g., CCTV,
I-Field, Power System Automation, SCADA, Voice over IP, etc...)

ii. In this appendix the CORE SWITCH was highlighted just for illustration
purpose with abbreviation of CORE SW and it be Alcatel, CISCO, Juniper
or any other Layer 3 switch vendor that provides routing.

2) Industrial Ethernet switch (i.e., Remote Site):

i. The Industrial Ethernet switch referred to in this document is the switch that
is installed at the well site (Remote Site) aggregating different traffic (CCTV,
I-Field, RTU, Voice over IP, etc...) and sending it to the core switch via a
ring or point to point topology.

ii. In this appendix the INDUSTRIAL ETHERNET SWITCH was highlighted

with the abbreviation of IES and it can be Alcatel, Cisco, Hirschmann
Juniper, MOXA or any other INDUSTRIAL ETHERNET based vendor
switch that operate in Saudi Aramco field environment.

3) Network Topology: The network topology referred to in this document can be

ring, point-to-point, star, or a combination of these network models.

4) The user may ignore those test cases that are not applicable or are not part of
the acquired system specifications.

5) Test cases are conducted independent of QoS settings (i.e., Best Effort vs.
Class of Service - CoS differentiation). QoS CoS settings shall be validated
prior to conducting the test. The result shall correlate to CoS QoS settings.

6) SAEP-1638 (Instructions Site Acceptance Test Plan) and (SAEP-1630

Preparation of Integration Test Procedure Document) may be used concurrently
with these test cases.

Page 20 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 18 September 2014
Next Planned Update: 6 September 2016 Plant Ethernet Networks Test Procedure

APPENDIX B – TABLE OF CONTENTS

1.0 INTRODUCTION TO LOCAL TEST ................................................................ 35

2.0 INTRODUCTION TO NETWORK TEST ......................................................... 36
3.0 TEST EQUIPMENT ......................................................................................... 37
4.0 TEST MATRIX FOR NETWORK TEST ........................................................... 38
II. LOCAL TEST
1.0 EQUIPMENT SITE INVENTORY .................................................................... 39
2.0 PHYSICAL EXAMINATION ............................................................................. 43
3.0 LOCAL ACCESS TEST ................................................................................... 46
4.0 POWER REDUNDANCY TEST ...................................................................... 51
II. NETWORK TEST FOR 1 GIGABIT ETHERNET RING
1.0 RECEIVED OPTICAL POWER TEST ............................................................. 56
2.0 THROUGHPUT TEST ..................................................................................... 61
3.0 LATENCY TEST.............................................................................................. 67
4.0 FRAME LOSS TEST ....................................................................................... 73
5.0 VLAN TEST ..................................................................................................... 78
6.0 PATH FAILURE TEST .................................................................................... 83
7.0 RING COUPLING TEST ................................................................................. 89

Page 21 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

Introduction to Local Test

The worksheet detailed can be used to perform the Local Network and Switch Test of
deployed infrastructure in the field.

Prior to the start of the network test, the equipment must be tested locally.

The following tests shall be performed during the Local Test:

Test to be performed Test Procedure Number

Equipment Site Inventory TPR-SWITCH-LOCAL-01
Physical Examination TPR-SWITCH-LOCAL-02
Local Access Test TPR-SWITCH-LOCAL-03
Power Redundancy Test TPR-SWITCH-LOCAL-04

Introduction to Network Test

The procedure detailed can be used to perform the Network Test of single vendor or
multivendor vendor deployed switching infrastructure for both the core and access
network layers.

Prior to the start of the network test, the equipment should have been tested locally.

The following test shall be performed during the Network Test:

Test to be performed Test Procedure Number

Received Optical Power Test TPR-SWITCH-NTWK-01
Throughput Test TPR-SWITCH-NTWK-02
Latency Test TPR-SWITCH-NTWK-03
Frame Loss Test TPR-SWITCH-NTWK-04
VLAN Test TPR-SWITCH-NTWK-05
Path Failure Test TPR-SWITCH-NTWK-06
Ring Coupling Test TPR-SWITCH-NTWK-07

Page 22 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

The test results shall be recorded in the Test Data Sheets and in case there are deviations, all efforts
shall be made to correct any noted discrepancy. All blank spaces on the Test Data Sheets should be
filled in indicating N/A for those not applicable.

Test Equipment
2 ea Local Craft Terminal with LAN Cable and Console Cable (Serial DB9)
2 sets 10/100/1000 Ethernet Analyzer (Example: Ethernet Analyzer EXFO FTB-8510) or an
equivalanet such as:
 Fault Timing Analysis (FTA): http://www.garrettcom.com/ftacontest.htm
 Jperf2.0Download:http://sourceforge.net/projects/iperf/files/jperf/jperf%20
2.0.0/jperf-2.0.0.zip/download
 Qcheck: http://www.ixchariot.com/products/datasheets/qcheck.html
2 sets Optical Power Meter
2 sets Digital Multimeter

Test Matrix for Network Test

The following matrix shows the various tests to be performed for each station.

STATION ID
Core Ring/Backbone

Access Layer 1

Access Layer n
Item Test Description
Access Layer 2

…..
…
….
Layer

01 Received Optical Power Test    

02 Throughput Test (TCP/UDP)    
03 Latency Test    
04 Frame Loss Test    
05 VLAN Test    
06 Path Failure Test    
07 Ring Coupling Test    

Where ( n*) is the last station number or remote site to be tested.

Page 23 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

I. LOCAL TEST
TEST PROCEDURE
LOCAL TEST
SITE INVENTORY CHECK
PURPOSE
To verify and record the Equipment Inventory at each site.
TEST EQUIPMENT
N.A.
ACCESSORIES
N.A.
TEST PROCEDURE
1. Confirm the Equipment Inventory as listed on the Delivery Sheet and record the serial number
for each equipment.

EXPECTED RESULTS
Equipment inventory on the site should be complete and should correspond to the
number and model as indicated on the Delivery Sheet.

Ethernet Analyzer TEST DATA SHEET

LOCAL TEST
TEST PROCEDURE : SITE INVENTORY CHECK
TEST PROCEDURE NO. : TPR-SWITCH-LOCAL-01
SITE NAME : ______________________
NODE NAME / TYPE : ______________________
DATE PERFORMED : ______________________

TEST EQUIPMENT
CALIBRATION DUE
DESCRIPTION MANUFACTURER/MODEL SERIAL NUMBER
DATE

INVENTORY
Description Manufacturer Serial No. Remarks

Page 24 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

REMARKS/EXEMPTION ITEMS

TEST PARTICIPANTS/WITNESSES
COMPANY/DEPT. NAME SIGNATURE DATE

Vendor or Contractor

S.A. Representative

S.A. Representative

S.A. Representative

S.A. Representative

S.A. Representative

Page 25 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST PROCEDURE
LOCAL TEST
CORE SWITCH (CORE SW) / INDUSTRIAL ETHERNET SWITCH (IES)
TEST PROCEDURE NO. TPR-SWITCH-LOCAL-02
PHYSICAL QUALITY CHECK
PURPOSE
To confirm the physical quality of the equipment including cabling works at the site.

TEST EQUIPMENT
None
ACCESSORIES
None
TEST PROCEDURE
1. Inspect the physical quality of the installed equipment including the cabling works for each
site.

EXPECTED RESULTS
As installed, any equipment should not have physical deformities and cabling should be done
cleanly and should adhere to established standards.

TEST DATA SHEET

LOCAL TEST
TEST PROCEDURE : PHYSICAL QUALITY CHECK
TEST PROCEDURE NO. : TPR-SWITCH-LOCAL-02
SITE NAME : ______________________
NODE NAME / TYPE : ______________________
DATE PERFORMED : ______________________

REMARKS/EXEMPTION ITEMS

Page 26 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST PARTICIPANTS/WITNESSES
COMPANY/DEPT. NAME SIGNATURE DATE
Vendor or Contractor
S.A. Representative
S.A. Representative
S.A. Representative
S.A. Representative
S.A. Representative

Page 27 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST PROCEDURE
LOCAL TEST
INDUSTRIAL ETHERNET SWITCH MODEL (IES) SWITCH
TEST PROCEDURE NO. TPR-SWITCH-LOCAL-03
LOCAL ACCESS TEST
PURPOSE
To verify that the Industrial Switch can be accessed locally

TEST EQUIPMENT
1 ea Local Craft Terminal (Laptop Computer)

ACCESSORIES
1 pc DB9 Serial Console Cable

TEST PROCEDURE
1. Connect the Local Craft Terminal to Industrial Ethernet Switch using the DB9 Serial
Console Cable.

2. Run the switch’s proprietary Emulator program (i.e., Moxa’s PComm) on the PC to access
the console configuration utility.

3. Navigate thru the Command Line Interface of the equipment to verify that it is accepting
command instructions from the Local Craft Terminal.

4. Repeat Steps 1 to 3 for every Industrial Switch.

EXPECTED RESULTS
The Switch should display the proper command hierarchy as instructed from the Local Craft
Terminal without delays in execution.

Page 28 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST DATA SHEET

LOCAL TEST
TEST PROCEDURE : LOCAL ACCESS TEST
TEST PROCEDURE NO. : TPR-SWITCH-LOCAL-03
SITE NAME : ______________________
NODE NAME / TYPE : ______________________
DATE PERFORMED : ______________________

TEST EQUIPMENT
CALIBRATION DUE
DESCRIPTION MANUFACTURER/MODEL SERIAL NUMBER
DATE

LOCAL ACCESS TEST

Switch Command Status Remarks

Switch Command Status Remarks

REMARKS/EXEMPTION ITEMS

TEST PARTICIPANTS/WITNESSES
COMPANY/DEPT. NAME SIGNATURE DATE
Vendor or Contractor
S.A. Representative
S.A. Representative
S.A. Representative

Page 29 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST PROCEDURE
LOCAL TEST
INDUSTRIAL SWITCH
TEST PROCEDURE NO. TPR-SWITCH-LOCAL-04
POWER REDUNDANCY TEST
PURPOSE
To verify that the remaining Power Supply module is able to function when the
other DC input power source fails.
TEST EQUIPMENT
1 ea Local Craft Terminal (Laptop Computer)
ACCESSORIES.
1 pc DB9 Serial Console Cable
TEST PROCEDURE
1. Connect PC1 to Ethernet port 1 of the Switch and configure the IP address of PC1.

2. Connect PC2 to Ethernet port 2 of the Switch and configure the IP address of PC2.

3. Remove the attached DC input power cable 1 connected at the back of the industrial switch.
Re-connect the DC input 1 and do the same to the DC input 2 of the Switch.

4. Issue a PING command from PC1 to PC2.

EXPECTED RESULTS
In any stage of the removal of the DC Power Cable, the Switch should not Turn Off and the PING
replies as reflected on the Local Craft Terminal should not register a TIMEOUT.

Page 30 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST DATA SHEET

LOCAL TEST
TEST PROCEDURE : POWER REDUNDANCY TEST
TEST PROCEDURE NO. : TPR-SWITCH-LOCAL-04
SITE NAME : ______________________
NODE NAME / TYPE : ______________________
DATE PERFORMED : ______________________

TEST EQUIPMENT
CALIBRATION DUE
DESCRIPTION MANUFACTURER/MODEL SERIAL NUMBER
DATE

SWITCH POWER REDUNDANCY

Power Inputs Switch Status PING Status Remarks
DC input 1
DC input 2

REMARKS/EXEMPTION ITEMS

TEST PARTICIPANTS/WITNESSES
COMPANY/DEPT. NAME SIGNATURE DATE

Vendor or Contractor
S.A. Representative
S.A. Representative
S.A. Representative
S.A. Representative
S.A. Representative

Page 31 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

II. NETWORK TEST FOR 1 GIGABIT ETHERNET RING

TEST PROCEDURE
NETWORK TEST
INDUSTRIAL ETHERNET SWITCH
TEST PROCEDURE NO. TPR-SWITCH-NTWK-01
RECEIVED OPTICAL POWER TEST
PURPOSE
To verify that the Optical Power received is within the Receiver Sensitivity range of Industrial
Ethernet Switch.

TEST EQUIPMENT
2 sets Optical Power Meter

ACCESSORIES
2 sets Optical Cleaning Materials

TEST PROCEDURE
1. Remove the Optical Patch Cord from the G2 receiving port of the Switch (West side) and
connect it to the Optical Power Meter.
2. Remove the Optical Patch Cord from the G3 receiving port of the Switch (East Side) and
connect it to the other Optical Power Meter.

3. Measure the received Optical Power from the West and East Sides. After this has been done,
note and record the Optical Power as indicated on the Optical Power Meter.

4. Repeat Steps 1 to 3 for every Industrial Switch Receive Optical Interface. Be sure to clean all
optical interfaces during testing.

EXPECTED RESULTS
Compliance to SAES-T-634 is required. For illustration purpose only, MOXA switch was used.
Each vendor will have their own specific requirements.

For MOXA’s SFP-1GLXLC, Receiver Sensitivity Range is from -3 dBm to -20 dBm
For MOXA’s SFP-1GLHXLC, Receiver Sensitivity Range is from -3 dBm to -24 dBm

Page 32 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST DATA SHEET

NETWORK TEST
TEST PROCEDURE : RECEIVED OPTICAL POWER TEST
TEST PROCEDURE NO. : TPR-SWITCH-NTWK-01
SITE NAME : ______________________
NODE NAME / TYPE : ______________________
DATE PERFORMED : ______________________

TEST EQUIPMENT
CALIBRATION DUE
DESCRIPTION MANUFACTURER/MODEL SERIAL NUMBER
DATE

RECEIVED OPTICAL POWER

Switch Received Optical Power Status Remarks

REMARKS/EXEMPTION ITEMS

TEST PARTICIPANTS/WITNESSES
COMPANY/DEPT. NAME SIGNATURE DATE
Vendor or Contractor
S.A. Representative
S.A. Representative
S.A. Representative
S.A. Representative
S.A. Representative

Page 33 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST PROCEDURE
NETWORK TEST
CORE SWITCH (CORE SW)/ INDUSTRIAL (IES°) SWITCH
TEST PROCEDURE NO. TPR-SWITCH-NTWK-02
THROUGHPUT TEST
PURPOSE
To determine and verify the Maximum Data Rate of the 1Gigabit link between Core switch and
Industrial Ethernet Switch.
TEST EQUIPMENT
2 sets 10/100/1000 Ethernet Analyzer (Example: Ethernet Analyzer EXFO FTB-8510)
ACCESSORIES
4 ea Single Mode Fiber Optic Patch Cords
TEST PROCEDURE
1. At core switch site, connect the 1Gigabit Ethernet Analyzer to the Tx/Rx Optical Port of
GLC-LH-SM that is plugged into the Core Switch using the Singlemode Fiber Optic Patch
Cords.
2. At the remote site, connect the 1Gigabit Ethernet Analyzer to the Tx/Rx Optical Port of
Industrial Ethernet Switch using the Singlemode Fiber Optic Patch Cords.
3. At the core switch site, run the test using 64-byte packets sent at 100% load for 60
seconds and take note of the number of frames that is transmitted by the 10Gigabit
Ethernet Analyzer.
Note: Before a packet is forwarded across the backplane, an internal 32-byte tag is added
to aid internal switching.
4. At the Remote site, take note of the number of frames that is received by the 1Gigabit
Ethernet Analyzer. If the count of transmitted frames is equal to the count of received
frames, raise the rate of the transmitted frames at the Local site and re-run the test. If fewer
frames are received than were transmitted, reduce the rate of the transmitted frames at the
Local site and re-run the test. The THROUGHPUT is the fastest rate at which the count of
Test Frames transmitted at the Local site is equal to the number of Test Frames received at
the Remote site.

EXPECTED RESULTS
The test conditions and the expected results for the 1G would be as follows:

CASE I. NO TRAFFIC IN RING

 If the traffic is equivalent to 1G, remote site (well) TX should be equal to RX.
 If the traffic generated from the remote site (well) is greater than 1G, RX should be equal to
1G.

CASE I. IF TRAFFIC IS EXISTING AT RING

 If the traffic generated plus the existing traffic (in production) from the remote site (well) is
greater than 1G, Core Switch RX should be equal to 1G.

Page 34 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST DATA SHEET

NETWORK TEST
TEST PROCEDURE : THROUGHPUT TEST
TEST PROCEDURE NO. : TPR-SWITCH-NTWK-02
SITE NAME : ______________________
NODE NAME / TYPE : ______________________
DATE PERFORMED : ______________________

TEST EQUIPMENT
CALIBRATION DUE
DESCRIPTION MANUFACTURER/MODEL SERIAL NUMBER
DATE

THROUGHPUT
Packet Size @ 100% TX Frames RX Frames Remarks
Traffic Load
TCP:
UDP:

Packet Size @ 100% TX Frames RX Frames Remarks

Traffic Load
TCP:
UDP:

Page 35 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

REMARKS/EXEMPTION ITEMS

TEST PARTICIPANTS/WITNESSES
COMPANY/DEPT. NAME SIGNATURE DATE

Vendor or Contractor

S.A. Representative

S.A. Representative

S.A. Representative

S.A. Representative

Page 36 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST PROCEDURE
NETWORK TEST
CISCO C6506-E/ IESA
TEST PROCEDURE NO. TPR-SWITCH-NTWK-03
LATENCY TEST

PURPOSE
To measure the maximum latency for time-sensitive applications such as Video and VOIP
applications.

TEST EQUIPMENT
2 sets 10/100/1000 Ethernet Analyzer (e.g., EXFO FTB-8510)

ACCESSORIES
2 ea RJ45 Straight LAN Cable

TEST PROCEDURE
1. At Core switch site, connect the 10/100/1000 Ethernet Analyzer using the RJ45 Straight
LAN Cable on a pre-determined VLAN port of the core (e.g., WS-X6548-GE-45AF card that
is on the CISCO 6506-E) Core Switch #1.
2. At the remote site, connect the 10/100/1000 Ethernet Analyzer on the corresponding VLAN
port of the Industrial Switch using the RJ45 Straight LAN Cable.
3. From Core switch site, run the test using 64-byte packets sent at 100% load for 60 seconds
and take note of the number of frames that is transmitted by the 10Gigabit Ethernet
Analyzer.
Note: Before a packet is forwarded across the backplane, an internal 32-byte tag is added
to aid internal switching.
4. At the Remote site, take note of the number of frames that is received by the 10/100/1000
Ethernet Analyzer. If the count of transmitted frames is equal to the count of received
frames, raise the rate of the transmitted frames at the Core switch site and re-run the test. If
fewer frames are received than were transmitted, reduce the rate of the transmitted frames
at Core switch site and re-run the test. The THROUGHPUT is the fastest rate at which the
count of Test Frames transmitted at the Local site is equal to the number of Test Frames
received at the Remote site. Take note of the achieved THROUGHPUT.
5. The latency result per Industrial Ethernet switch would be as follows.
Latency: 10 microseconds
To calculate the one-way latency, use the following formula:
Max L = Nswitch x Latency + Latency of 10G ring
Where: Nswitch – no. of switch in a ring
Latency – 10 microseconds

Page 37 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

6. Repeat Steps 1 to 5 for the other Industrial Ethernet switch within a ring.

7. Conduct the same test case and report on the application performance. The applications
and accepted results are defined below:

a. Video streams: Delay below 50ms, jitter below 10ms

b. Voice streams: Delay (one way) below 150ms, jitter below 10ms
c. Process control: Delay (one way) below 10 ms, jitter below 10ms.

EXPECTED RESULTS
The actual network LATENCY should not be more than the claimed LATENCY which is equivalent to 10
microseconds per switch. The End-to-end network delay shall be 10ms.The applications accepted
results are defined below:
 Video streams: Delay below 50 ms, jitter below 10 ms
 Voice streams: Delay (one way) below 150 ms, jitter below 10 ms
 Process control: Delay (one way) below 10 ms, jitter below 10 ms.

Page 38 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST DATA SHEET

NETWORK TEST
TEST PROCEDURE : LATENCY TEST
TEST PROCEDURE NO. : TPR-SWITCH-NTWK-03
SITE NAME : ______________________
NODE NAME / TYPE : ______________________
DATE PERFORMED : ______________________

TEST EQUIPMENT
CALIBRATION DUE
DESCRIPTION MANUFACTURER/MODEL SERIAL NUMBER
DATE

LATENCY @ 1G
From/To Max Latency per Switch Average Latency Remarks

REMARKS/EXEMPTION ITEMS

TEST PARTICIPANTS/WITNESSES
COMPANY/DEPT. NAME SIGNATURE DATE
Vendor or Contractor
S.A. Representative
S.A. Representative
S.A. Representative
S.A. Representative

Page 39 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST PROCEDURE
NETWORK TEST
CORE SWITCH (CORE SW)/ INDUSTRIAL ETHERNET (IES)
TEST PROCEDURE NO. TPR-SWITCH-NTWK-04
FRAME LOSS TEST AT WELL SITE
PURPOSE
To determine and verify the percentage of Lost Frames when the 1Gigabit link between Core
switch at the backbone site and Industrial Ethernet Switches (remote sites) is at Full Load.

TEST EQUIPMENT
2 sets 10/100/100 Ethernet Analyzer (e.g., Ethernet Analyzer EXFO FTB-8510)

ACCESSORIES
4 ea Single Fiber Optic Patch Cords

TEST PROCEDURE
1. At Core site, connect the 1Gigabit Ethernet Analyzer to the Tx/Rx Optical Port of GLC-LH-
SM that is plugged in to the Core Switch using the Singlemode Fiber Optic patch cords.
2. At the remote site, connect the 1Gigabit Ethernet Analyzer to the Tx/Rx Optical Port of
Industrial Switch using the Singlemode Fiber Optic patch cords.
3. From the local site, send a specific number of frames at 1Gbps specific rate for a duration
of 30 minutes. Take note of the number of frames that is transmitted by the 1Gigabit
Ethernet Analyzer.
4. At the Remote site, take note of the number of frames that is received by the 1Gigabit
Ethernet Analyzer.
% FRAME LOSS = [(Tx Frames – Rx Frames) / Tx Frames] x 100
5. Repeat Steps 1 to 4 for the remaining GLC-LH-SM cards.

EXPECTED RESULTS
Frame Loss Percentage should be 100 at 1Gbps Full Rate.
Transmitted Frames should be equal to Received Frames at Full Load.

Page 40 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST DATA SHEET

NETWORK TEST
TEST PROCEDURE : FRAME LOSS TEST
TEST PROCEDURE NO. : TPR-SWITCH-NTWK-04
SITE NAME : ______________________
NODE NAME / TYPE : ______________________
DATE PERFORMED : ______________________

TEST EQUIPMENT
CALIBRATION DUE
DESCRIPTION MANUFACTURER/MODEL SERIAL NUMBER
DATE

FRAME LOSS @ 1Gbps RATE

Switch # and Port Tx Frames Rx Frames Remarks

REMARKS/EXEMPTION ITEMS

Page 41 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST PARTICIPANTS/WITNESSES
COMPANY/DEPT. NAME SIGNATURE DATE

Vendor or Contractor

S.A. Representative

S.A. Representative

S.A. Representative

S.A. Representative

S.A. Representative

Page 42 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST PROCEDURE
NETWORK TEST
CORE SWITCH (CORE SW)/ INDUSTRIAL ETHERNET SWITCH (IES
TEST PROCEDURE NO. TPR-SWITCH-NTWK-05
VLAN TEST
PURPOSE
To verify the separation of every VLAN Subnet from each site going to/from Core Site.

TEST EQUIPMENT
2 ea Local Craft Terminal (Laptop Computer)

ACCESSORIES
2 ea RJ45 Straight LAN Cable

TEST PROCEDURE
1. At the remote site, connect the Local Craft Terminal to one of the Ethernet ports of the
Industrial Switch using the RJ45 LAN Cable.

2. At Core site, connect the Local Craft Terminal to the corresponding VLAN port of the Core
Switch.

3. Issue a PING command from the remote site Local Craft Terminal to the Local Craft
Terminal that is connected at the Core site.

4. At Core site, transfer the connection of the Local Craft Terminal to another VLAN port that is
not a member of the VLAN group at the remote site Local Craft Terminal.

5. Issue a PING command from the remote site Local Craft Terminal to the Local Craft
Terminal that is connected to a different VLAN at the Core site.

6. Perform Procedures 1 to 5 for every VLAN Subnet at each remote site.

EXPECTED RESULTS
PING requests to the same VLAN should have a REPLY from Core site.
PING requests to a different VLAN should have no REPLY from Core site.

Page 43 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST DATA SHEET

NETWORK TEST
TEST PROCEDURE : VLAN TEST
TEST PROCEDURE NO. : TPR-SWITCH-NTWK-05
SITE NAME : ______________________
NODE NAME / TYPE : ______________________
DATE PERFORMED : ______________________

TEST EQUIPMENT
CALIBRATION DUE
DESCRIPTION MANUFACTURER/MODEL SERIAL NUMBER
DATE

VLAN TEST
From VLAN and Port To VLAN and Port PING Reply Remarks

REMARKS/EXEMPTION ITEMS

TEST PARTICIPANTS/WITNESSES
COMPANY/DEPT. NAME SIGNATURE DATE
Vendor or Contractor
S.A. Representative
S.A. Representative
S.A. Representative
S.A. Representative
S.A. Representative

Page 44 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST PROCEDURE
NETWORK TEST
INDUSTRIAL ETHERNET (IES) SWITCH
TEST PROCEDURE NO. TPR-SWITCH-NTWK-06
PATH FAILURE TEST
PURPOSE
To verify the Network Path Protection and Recovery time of 1G Ring when there is a Fiber Optic
cable cut. The expected recovery time for ring should be in compliance with the vendor
specification (in this case, MOXA Turbo Ring is less than 20 milliseconds).

TEST EQUIPMENT
2 ea Local Craft Terminal (Computer Laptop)

ACCESSORIES
2 ea RJ45 Straight LAN Cable

TEST PROCEDURE
1. At remote site A, connect the PC1 to port 1 of the Industrial Ethernet Switch using the RJ45
LAN Cable.
2. At the same location, site A, connect the 10/100/1000 Ethernet Analyzer to port 2 of
Industrial Ethernet Switch using the RJ45 LAN Cable.
3. At remote site B, connect the PC2 to port 1 of the Industrial Ethernet Switch using the RJ45
LAN Cable.
4. At the same location, site B, connect the 10/100/1000 Ethernet Analyzer to port 2 of
Industrial Ethernet Switch using the RJ45 LAN Cable.
5. Issue a PING command from the remote site PC1 to PC2 that is connected at remote site
B. Make sure that no packet drops are detected.
6. At the remote site A, remove the fiber optic connection of the Industrial Ethernet Switch that
is facing remote site B. Observe the communication status between PC1 and PC2. Some
packet drops are detected at this time due to topology change.
7. After 1 minute, reconnect the 1G fiber optic patch cord to Industrial Ethernet Switch.
Observe the communication status between PC1 and PC2. Some packet drops are
detected at this time due to topology change.
8. Perform Procedures 1 to 7 for every VLAN Subnet at each remote site. Make sure to clean
every Fiber Optic patch cord at every stage of the test and replace the patch cords to its
original connection after the test.

EXPECTED RESULTS
The recovery time for Ring should be in line with the vendor specification (in this case, MOXA should be
less than 20milliseconds).

Page 45 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST DATA SHEET

NETWORK TEST
TEST PROCEDURE : PATH FAILURE TEST
TEST PROCEDURE NO. : TPR-SWITCH-NTWK-06
SITE NAME : ______________________
NODE NAME / TYPE : ______________________
DATE PERFORMED : ______________________

TEST EQUIPMENT
CALIBRATION DUE
DESCRIPTION MANUFACTURER/MODEL SERIAL NUMBER
DATE

PATH FAILURE
Removed Fiber Optic Recovery Time PING Reply Remarks
Port

REMARKS/EXEMPTION ITEMS

Page 46 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST PARTICIPANTS/WITNESSES
COMPANY/DEPT. NAME SIGNATURE DATE

Vendor or Contractor

S.A. Representative

S.A. Representative

S.A. Representative

S.A. Representative

S.A. Representative

Page 47 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST PROCEDURE
NETWORK TEST
CORE SWITCH (CORE SW) / INDUSTRIAL ETHERNET (IES) SWITCH
TEST PROCEDURE NO. TPR-SWITCH-NTWK-07
RING COUPLING TEST

PURPOSE
To verify the capability of single ring compose of Industrial Ethernet Switch (IES) and Core switch
(CORE SW switch). The industrial Ethernet Switch shall be able to receive/ forward the packets
through the vendor ring [protocol (in this case for MOXA, turbo ring) and communication coupling
between Industrial Ethernet switch and the core switch.
TEST EQUIPMENT
2 sets 10/100/1000 Ethernet Analyzer (EXFO FTB-8510)
2 sets Local Craft Terminal (Laptop Computer)

ACCESSORIES
2 ea RJ45 Straight LAN Cable

TEST PROCEDURE
1. At the head-end switch 1, connect the Local Craft Terminal (PC1) to one of the Ethernet
ports of the Industrial Ethernet Switch using the RJ45 LAN Cable.
2. At the head-end switch 2, connect the Local Craft Terminal (PC2) to one of the Ethernet
ports of the Industrial Ethernet Switch using the RJ45 LAN Cable.
3. Configure RSTP on each of the co-located Core switch and connect two Giga ports of Core
switch to Industrial Ethernet Switch single ring network.
4. From PC2, ping to Core Switch IP address.
5. Enable Ring Coupling on the head-end Industrial Ethernet switches. Set head-end switch 1
as the master device and head-end switch 2 as the slave device.
6. Observe the coupling port status, one will indicate primary while the other port will show as
back-up.
7. Disconnect one Giga port of Core switch between Core Switch and Industrial Ethernet
switches ring network.
8. From the remote site in which the Ethernet Analyzer is connected to Industrial Ethernet
switches, observe the recovery time that is detected by the 1Gigabit Ethernet Analyzer and
record the result in the Test Data.
9. Reconnect the Giga port of Core Switch between Core Switch and Industrial Ethernet
switches ring network.
10. Observe the recovery time that is detected by the 1Gigabit Ethernet Analyzer and record
the result in the Test Data.

Page 48 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

EXPECTED RESULTS

Make sure that the delay counter for Ring Coupling should be less than 1 second.
For test item no. 4:

PC2 can ping to Core Switch successfully.

For test item no. 7:

PC2 can ping to Core Switch successfully after topology change.

For test item no. 9:

PC2 can ping to Core Switch successfully after topology change.

Page 49 of 50
Document Responsibility: Communications Standards Committee SAEP-701
Issue Date: 5 July 2011
Next Planned Update: 5 July 2016 Plant Ethernet Network Test Procedure

TEST DATA SHEET

NETWORK TEST
TEST PROCEDURE : RING COUPLING TEST
TEST PROCEDURE NO. : TPR-SWITCH-NTWK-07
SITE NAME : ______________________
NODE NAME / TYPE : ______________________
DATE PERFORMED : ______________________
TEST EQUIPMENT
DESCRIPTION MANUFACTURER/MODEL SERIAL NUMBER CALIBRATION DUE DATE

RING COUPLING TEST

Removed Giga Port Recovery Time (ms) PING Reply Remarks

Removed Giga Port Recovery Time (ms) PING Reply Remarks

REMARKS/EXEMPTION ITEMS

TEST PARTICIPANTS/WITNESSES
COMPANY/DEPT. NAME SIGNATURE DATE
Vendor or Contractor
S.A. Representative
S.A. Representative
S.A. Representative
S.A. Representative
S.A. Representative

Page 50 of 50