Foxboro Evo™

Process Automation System

The Foxboro Evo Control

Network Architecture Guide

*B0700AZ* *V*

B0700AZ

Rev V
August 28, 2017
Schneider Electric, Foxboro, Foxboro Evo, FoxView, and I/A Series are trademarks of Schneider Electric SE, its
subsidiaries and affiliates.

All other brand names may be trademarks of their respective owners.

Copyright 2014–2017 Schneider Electric.

All rights reserved.

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Schneider Electric Systems USA, Inc. supplied software supported by this
documentation, you should read and understand the following information concerning
copyrighted software.
1. The license provisions in the software license for your system govern your obligations
and usage rights to the software described in this documentation. If any portion of
those license provisions is violated, Schneider Electric Systems USA, Inc. will no
longer provide you with support services and assumes no further responsibilities for
your system or its operation.
2. All software issued by Schneider Electric Systems USA, Inc. and copies of the software
that you are specifically permitted to make, are protected in accordance with Federal
copyright laws. It is illegal to make copies of any software media provided to you by
Schneider Electric Systems USA, Inc. for any purpose other than those purposes
mentioned in the software license.
Contents
Tables.................................................................................................................................... vii

Figures.................................................................................................................................... ix

Safety Information ................................................................................................................. xi

Preface................................................................................................................................. xiii
Purpose .................................................................................................................................. xiii
Audience ................................................................................................................................ xiii
Revision Information ............................................................................................................. xiii
Reference Documents ............................................................................................................ xiv
Terms and Definitions ........................................................................................................... xiv

1. Introduction ...................................................................................................................... 1
Overview of The Foxboro Evo Control Network Architecture .................................................. 1
Switched Ethernet Features .................................................................................................. 1
The Foxboro Evo Control Network Features ....................................................................... 2
Standard Configuration Features ..................................................................................... 2
Enhanced Network Configuration Features ..................................................................... 2
Loop Detection Policy (LDP) Deployed on The Foxboro Evo Control Network ............ 3
Loop Protection Algorithm (LPA) ................................................................................... 4
Virtual Local Area Networks (VLANs) on The Foxboro Evo Control Network ............... 5
The Foxboro Evo Control Network - Overview ................................................................... 5
The Foxboro Evo Control Network Topologies .............................................................. 6
The Foxboro Evo Control Network - Network Details ............................................................. 7
Network Example ................................................................................................................ 7
The Foxboro Evo Control Network Specifications - Overview ........................................... 10
The Foxboro Evo Control Network Constraints ............................................................ 10
Address Translation Stations (ATS) Guidelines ............................................................. 10
Specifications ................................................................................................................. 11
The Foxboro Evo Control Network Workstations ............................................................. 12
The Foxboro Evo Control Network Ethernet Switches ........................................................... 12
The Foxboro Evo Control Network Approach to High Availability ................................... 13
Advantages of Foxboro-Supplied Switches ............................................................................... 13
Control Network Cabling ....................................................................................................... 14
Category 5 Cabling ............................................................................................................ 15
Fiber Optic Cabling ........................................................................................................... 15
Single Mode Cable ........................................................................................................ 16
Simplex Single Mode Cable ........................................................................................... 16

iii
B0700AZ – Rev V Contents

Multimode Cable .......................................................................................................... 16

2. Site Planning ................................................................................................................... 19

Site Planning Overview ........................................................................................................... 19
Network Considerations ..................................................................................................... 19
Traffic Considerations ........................................................................................................ 22
Network Loading ............................................................................................................... 23
Equipment Considerations ................................................................................................. 24
Hardware Requirements ..................................................................................................... 24
Switch Utilization in the Standard Configurations ........................................................ 24
Switch Utilization in the Enhanced Network Configurations ........................................ 24
Firmware Considerations .................................................................................................... 25
The Foxboro Evo Control Network Design Rules ................................................................... 25
Standard Configuration Design Rules ................................................................................ 25
Non-Foxboro Evo Equipment ....................................................................................... 26
Enhanced Network Configuration Design Rules ................................................................ 27
Additional Guidelines For High Availability on The Foxboro Evo Control Network ......... 29
Planning Loop Protection Algorithm (LPA) Configurations .......................................... 29
Planning Enhanced Network Configurations ................................................................ 30
The Foxboro Evo Control Network Design ............................................................................ 33
I/O Network Design Rules ................................................................................................. 34
The Foxboro Evo Control Network Topologies ................................................................. 34
Standard Configurations ................................................................................................ 35
Enhanced Network Configurations ............................................................................... 47
I/O Network Topology Configurations ......................................................................... 55
Switch and Fiber Cable Budget and Loss ............................................................................ 55
Fiber Cable Budget and Loss ........................................................................................ 55
Fiber Optic Budgets ...................................................................................................... 55
Fiber Budgeting Between Foxboro Evo Devices and Switch Fiber Optic Connections ... 56
The Foxboro Evo Control Network Cabling ...................................................................... 59
Twisted-Pair Cabling ..................................................................................................... 59
Null Hub ...................................................................................................................... 59
Switch and Converter Fiber Optic Cabling .................................................................... 60
FCP280, FCP270, ZCP270, FCM100Et, and FCM100E Fiber Signal Cabling ........... 63

3. Installation (Cabling) ...................................................................................................... 69

Connecting The Foxboro Evo Control Network Components ................................................ 69
Fiber Optic Cabling Guidelines .......................................................................................... 69
Interconnecting Ethernet Switches ..................................................................................... 69
Inter Switch Link (ISL) Interfaces .................................................................................. 70
Switch Configuration .............................................................................................................. 71

4. Maintenance.................................................................................................................... 73
The Foxboro Evo Control Network and Other Associated Foxboro Evo-Related Addresses .... 73
General Troubleshooting Guidelines ....................................................................................... 75

iv
Contents B0700AZ – Rev V

Characterize the Problem ................................................................................................... 75

Determine Which Devices are Affected .............................................................................. 75
Troubleshoot the Affected Devices ..................................................................................... 76
System Management Displays ................................................................................................. 76
Limitations on Number of Switches Assigned to a Single System Monitor ......................... 77
Indicators ................................................................................................................................ 77
Ethernet Switches ............................................................................................................... 77
Media Converter ................................................................................................................ 77
Fiber Optic Cable Handling and Cleaning .............................................................................. 78
Handling Fiber Optic Cable ............................................................................................... 78
Cleaning Fiber Optic Cable ................................................................................................ 80
Contamination of Fiber Optic Connectors and Sockets ................................................. 80
Contamination Prevention ............................................................................................ 80
Contamination Removal ............................................................................................... 81
Examples of Fiber Optic Connector Cleaning Products ................................................. 82
Environmental Guidelines .................................................................................................. 82
Dust Mitigation and Prevention .................................................................................... 82
Airborne Chemicals and Prevention .............................................................................. 82

5. Combining Two or More Instances of The Foxboro Evo Control Networks................... 83

Overview ................................................................................................................................. 83
Planning Stage .................................................................................................................... 84
Station Addressing .............................................................................................................. 84
Bridge Switch Functionality ............................................................................................... 84
Topology Constants ........................................................................................................... 84
Combining Star Network Topologies ..................................................................................... 85
Combining Star with Tree Network Topology ........................................................................ 87
Combining Tree Network Topologies .................................................................................... 88
Combining Ring Network Topologies .................................................................................... 89

Appendix A. COMEX Fault Handling on The Foxboro Evo Control Network ................... 91
COMEX Layers ...................................................................................................................... 91
COMEX Applications Layer .............................................................................................. 91
Application Layer Protocol and Timers ......................................................................... 91
Transport Layer .................................................................................................................. 92
Transport Layer Protocol and Timers ............................................................................ 94
Network Layer ................................................................................................................... 95
Operation ...................................................................................................................... 95
Logical Link Control Layer ................................................................................................ 95
Transmit Operation ...................................................................................................... 95
Receive Operation ......................................................................................................... 96
MAC Layer ........................................................................................................................ 96

v
B0700AZ – Rev V Contents

Appendix B. The Foxboro Evo Network Fault Handling..................................................... 97

LINK ...................................................................................................................................... 97
“PORT TEST” Packets ........................................................................................................... 97
“LLC_PING” Test .................................................................................................................. 98
MTK “Ping” Test ............................................................................................................... 99
Ping Voting Test ................................................................................................................ 99
Notifications ...................................................................................................................... 99
Workstation Address Qualification ..................................................................................... 99
ZCP-FCM Communications ................................................................................................ 100
DIAGNOSTIC Information ................................................................................................. 101

Index .................................................................................................................................. 103

vi
Tables
1-1. Differences Between Legacy LPA and Enhanced LPA ................................................... 4
1-2. The Foxboro Evo Control Network Specifications ...................................................... 11
1-3. Fiber Cable Power Losses ............................................................................................ 17
1-4. SFP Mini-GBIC Transceivers ..................................................................................... 17
2-1. Differences Between Legacy LDP and CoS LDP ......................................................... 31
2-2. Fiber Cable Power Losses ............................................................................................ 55
2-3. Kit DG100AF ............................................................................................................. 56
2-4. CAT5 Cable - Maximum Transmission Distance ........................................................ 59
2-5. Prefabricated CAT5 STP Cables with RJ-45 Connectors ............................................ 59
2-6. Null Hub .................................................................................................................... 60
2-7. Multimode Fiber Cables with LC Connectors ............................................................. 60
2-8. Multimode Fiber Cables with MT-RJ to MT-RJ Connectors ..................................... 61
2-9. Multimode Fiber Cable with LC and SC Connectors ................................................. 61
2-10. Multi-mode Fiber Optic Cable - Maximum Transmission .......................................... 61
2-11. Single Mode Fiber Optic Cable - Maximum Transmission ......................................... 61
2-12. Single Mode Fiber Optic Jumper Cables ..................................................................... 62
2-13. Simplex-Single Mode Fiber Optic Cable - Maximum Transmission ............................ 62
2-14. Fiber Optic Cables ...................................................................................................... 64
2-15. Switch Group Isolation ............................................................................................... 66
4-1. IP Address Assignments ............................................................................................... 73
A-1. Out of Sequence DT and Ack Packets ........................................................................ 93

vii
B0700AZ – Rev V Tables

viii
Figures
1-1. The Foxboro Evo Control Network (Star Topology Shown) ......................................... 8
1-2. The Foxboro Evo Control Network with an I/O Network ............................................ 9
2-1. Large Network (Enhanced Network Configuration) ................................................... 28
2-2. Small Network (Standard Configuration) ................................................................... 36
2-3. Medium Network (Ring) (Standard Configuration) .................................................... 37
2-4. Medium or Large Network (Star) (Standard Configuration) ....................................... 38
2-5. Medium or Large Network (Double Star) (Standard Configuration) .......................... 39
2-6. Large Network - All Blades (Standard Configuration) ................................................. 40
2-7. Large Network - Inverted Tree
(Standard Configuration) ............................................................................................ 41
2-8. Large Network - Blades and Low-Cost Switches
(Modified Inverted Tree) ............................................................................................ 42
2-9. The Foxboro Evo Control Network Tiers ................................................................... 43
2-10. Root Switches Connected ........................................................................................... 44
2-11. Second Tier Connections ............................................................................................ 45
2-12. Third Tier Connections .............................................................................................. 46
2-13. Fourth Tier Connections ............................................................................................ 46
2-14. Labeling the Switches .................................................................................................. 47
2-15. Small Network (Enhanced Network Configuration) ................................................... 48
2-16. Star Topology (Enhanced Network Configuration) .................................................... 49
2-17. Double Star Topology (Enhanced Network Configuration) ........................................ 50
2-18. Inverted Tree Topology (Enhanced Network Configuration) ...................................... 52
2-19. Modified Inverted Tree Topology (Enhanced Network Configuration) ...................... 54
2-20. P0973LR and P0973LS LC Fiber Attenuators ............................................................ 57
2-21. LC Fiber Attenuators in FCP270’s Fiber Optic Transceivers ....................................... 58
2-22. Receive (Rx) and Transmit (Tx) Ports for FCP280, ZCP270, and ATS ...................... 58
2-23. Switch to Switch and Switch to Patch Panel Connections ........................................... 63
2-24. FCP280 Signal Cabling ............................................................................................... 67
2-25. FCP270, ZCP270, FCM100Et and FCM100E Signal Cabling .................................. 68
3-1. Switch-to-Switch Fiber via Uplink Port ....................................................................... 70
3-2. Port-to-Port Connection via Fiber Optic Ports ........................................................... 71
4-1. SC Connector, Typical ............................................................................................... 79
4-2. Multimode MT-RJ Connector .................................................................................... 79
4-3. Multimode Duplex LC Connector .............................................................................. 80
4-4. Lint in Fiber Optic LC Socket .................................................................................... 81
5-1. Combining Two Star Network Topologies Into
One Tree Network Topology (Before) ........................................................................ 85
5-2. Combining Two Star Network Topologies Into
One Tree Network Topology (After) .......................................................................... 85
5-3. Combining a Star Network Topology with a Tree Network Topology
Into One Tree Network Topology (Before) ................................................................ 87
5-4. Combining a Star Network Topology with a Tree Network Topology
Into One Tree Network Topology (After) ................................................................... 87

ix
B0700AZ – Rev V Figures

5-5. Combining Two Tree Network Topologies Into One Tree Network Topology
(Before) ....................................................................................................................... 88
5-6. Combining Two Tree Network Topologies Into One Tree Network Topology
(After) ......................................................................................................................... 88
5-7. Combining Two (4) Tier Tree Network Topologies
Into One (4) Tier Tree Network Topology (After) ...................................................... 89
5-8. Combining Ring Network Topologies ........................................................................ 90

x
Safety Information
Important Information
Read these instructions carefully and look at the equipment to
become familiar with the device before trying to install, operate, ser-
vice, or maintain it. The following special messages may appear
throughout this manual or on the equipment to warn of potential
hazards or to call attention to information that clarifies or simplifies
a procedure.

The addition of either symbol to a "Danger" or

"Warning" safety label indicates that an electrical
hazard exists which will result in personal injury if
the instructions are not followed.

This is the safety alert symbol. It is used to alert you to

potential personal injury hazards. Obey all safety messages
that follow this symbol to avoid possible injury or death.

DANGER
DANGER indicates a hazardous situation which, if not avoided, will
result in death or serious injury.

WARNING
WARNING indicates a hazardous situation which, if not avoided, could
result in death or serious injury.

CAUTION
CAUTION indicates a hazardous situation which, if not avoided, could
result in minor or moderate injury.

NOTICE
NOTICE is used to address practices not related to physical injury.
Please Note
Electrical equipment should be installed, operated, serviced, and main-
tained only by qualified personnel. No responsibility is assumed by
Schneider Electric for any consequences arising out of the use of this
material.

A qualified person is one who has skills and knowledge related to the con-
struction, installation, and operation of electrical equipment and has
received safety training to recognize and avoid the hazards involved.
Preface

Purpose
This document provides overview guidelines and requirements for designing, installing, and
maintaining the Foxboro Evo™ Control Network, formerly known as “The MESH Control
Network” until Foxboro Evo Control Core Services v9.1.
Topics include:
♦ Site planning
♦ Installation
♦ Maintenance
The documents listed in “Reference Documents” provide information specific to the control
network hardware.
For detailed and specific information on the Ethernet equipment, refer to the documentation
supplied by the switch vendor. These documents may also be available on the Global Customer
Support web site at https://pasupport.schneider-electric.com. The control network documents for
Foxboro Evo systems are available on the Foxboro Evo Control Network Configuration Tool CD-
ROM (K0173ZU) provided by Schneider Electric’s Foxboro business unit.

Audience
This document is for use by process engineering, operations, installation, and maintenance
personnel. These personnel are expected to have a working knowledge of Ethernet LANs and
Foxboro Evo configurations.

Revision Information
Revision V includes these changes:
Global
♦ Rewrote all safety messages
♦ Updated terminology to meet safety standards
♦ Updated P0972YL to RH102AL
Chapter 1 “Introduction”
♦ Updated Table 1-4 on page 17
Chapter “Preface”
♦ Added “OMMO” on page xix
Chapter 2 “Site Planning”
♦ Added Table 2-1 on page 31
♦ Updated “Standard Large Networks (Inverted Tree Topology)” on page 39

xiii
B0700AZ – Rev V Preface

Chapter 5 “Combining Two or More Instances of The Foxboro Evo Control Networks”
♦ Updated “Overview” on page 83

Reference Documents
These documents provide additional or related information to the hardware used in the Foxboro
Evo Control Network:
♦ The Foxboro Evo Control Network Hardware Instructions for S-Series Switches
(P0973KD/P0973KK/P0973LN) (B0700CE)
♦ A4-Series (P0973JM/P0973JN/P0973JP) Switches, Hardware and Software
Configuration Instructions (B0700CF)
♦ A-Series (P0973BH/P0973BJ/P0973BK) Switches, Hardware and Software
Configuration Instructions (B0700CH)
♦ The MESH Control Network Hardware Instructions for C-Series Switches
(P0973KJ/HA/BL) and B-Series Switches (P0973LK) (B0700CJ)
♦ The MESH Control Network Hardware Instructions for N-Series Switches
(P0973AR/P0973AS/P0972YE) (B0700CK)
♦ V-Series (P0972WP/P0972YC) Switches, Hardware and Software Configuration
Instructions (B0700CL)
♦ E7 Chassis and 16-port Fiber (P0972MK/P0972MJ) Switches, Hardware and Software
Configuration Instructions (B0700CM)
♦ I-Series (P0973GA/GB/HB/HC) Industrial Switch, Hardware and Software
Configuration Instructions (B0700CN)
♦ Media Converter Installation and Configuration Guide for Control Networks (B0700CP)
These documents provide additional or related information to the control network concepts:
♦ Switch Configurator Application Software Guide for the Foxboro Evo Control Network
(B0700CA)
♦ The Foxboro Evo Control Network Architecture (PSS 31H-7NETWORK)
♦ The Foxboro Evo Control Network Ethernet Equipment (PSS 31H-7NwEquip)
♦ System Definition: A Step-by-Step Procedure (B0193WQ)
♦ I/A Series Configuration Component (IACC) User's Guide (B0700FE)
♦ System Manager (B0750AP)
♦ Refer to the System Development documents in the Preface in Foxboro Evo Control
Software Deployment Guide (B0750BA) for the Foxboro Evo Control Editors.

Terms and Definitions

10Base-T
10 Mb twisted-pair Ethernet

100Base-TX
100 Mb twisted-pair Fast Ethernet

xiv
Preface B0700AZ – Rev V

100Base-FX
100 Mb fiber optic Fast Ethernet

1000Base-LX
IEEE 802.3z specification for Gigabit Ethernet over two strands of 50/125 or 62.5/125 micron core
MMF or 9/125 micron core SMF fiber cable using long wavelength optical transmission.

1000Base-SX
IEEE 802.3z specification for Gigabit Ethernet over two strands of 50/125 or 62.5/125 micron core
MMF fiber cable using short wavelength optical transmission.

1000Base-T
IEEE 802.3ab specification for Gigabit Ethernet using CAT5 copper Ethernet cable.

1000Base-BX
IEEE 802.3ab specification for Gigabit Ethernet over a single strand of 9/125 micron core SMF fiber
cable. The communication over a single strand of fiber is achieved by separating the transmission
wavelength of the two devices - transmitted data and received data are broadcasted and received on
separate wavelengths.

1000Base-ZX
IEEE 802.3ab specification for Gigabit Ethernet over a single strand of 9/125 micron core SMF fiber
cable using 1,550 nm wavelength to achieve distances of at least 70 km (43.5 mi).

ACN
Auxiliary Communications Network, a Distributed Control System (DCS) network.

ANSI
American National Standards Institute

Auto-Negotiation
Signalling method allowing each node to select the optimum operational mode (for example, speed
and duplex mode) based on the capabilities of the node to which it is connected.

Backbone
Another term for bus that refers to the main link that connects network nodes. The term is often used
to describe the main network connections composing the network.

Beacon
The packet type and packet on the network upon which the port disabling is enacted.

Bi-directional GBIC
The Bi-directional Gigabit Interface Converters are deployed as a pair. One of the SFP Mini-GBICs is
placed at one end of a single strand of single mode fiber (terminated with an LC UPC1 connector)
and the second at the other end of the same fiber, achieving bi-directional transmission on a single

1.
“UPC” denotes an “ultra” quality polish on the fiber endface of a cable.

xv
B0700AZ – Rev V Preface

fiber. These Mini-GBICs support the Digital Optical Monitoring (DOM) extensions to the SFP stan-
dard.

BPDU
Bridge Protocol Data Units are frames that contain information about the Spanning tree protocol
(STP).

BPP
Beacon Priority Policy - A role/service that allows for the Beacon packet to have the highest priority
when propagating though the network. This helps ensure the Beacon packet is transmitted back to
the PBQ in a flooded switch.

BootP
Bootstrap Protocol

Bridge Priority Value

The range of priority values used to determine which device is selected as the Spanning Tree root.
This value can range from 0- 65535 for bridge priority mode 802.1d (decrement by 1) or from 0-
61440 for bridge priority mode 802.1t (decrement by 4096).

CAT5
Category 5 Twisted Pair Cable - such as 10Base-T, 100Base-TX and 1000Base-T.

CBP
(Circuit Breaker Policy) a role/service that disables a port when a Beacon packet is received from an
edge switch or from the tier below.

Circuit Breaker
A policy rule that disables a port that receives an incoming packet of an outgoing Beacon packet
“Loop”.

Circuit Breaker PBQ/SBQ (CBPBQ/CBSBQ)

This is used to refer to policy rule that disables an uplink port that interfaces two root switches that
receives an incoming packet of an outgoing Beacon packet “Loop”. This function is a subset of the
Circuit Breaker.

CLI
Command Line Interface

Core Switch
Refers to the main body of switches that provide the network with its backbone connections. A core
switch can also be considered an “edge switch” in reference to the root; however the outer most edge
switches within the network are normally not considered to be core switches.

CRC
Cyclic Redundancy Check

xvi
Preface B0700AZ – Rev V

CSMA/CD
Carrier Sense Multiple Access/Collision Detection

Data Loop or Loop Path

Refers to a condition where data traverses a redundant path with no termination point.

DCE
Data Communications Equipment (modem)

DSR
Data Set Ready

DTE
Data Terminal Equipment

DTR
Data Terminal Ready

Edge Switch
Refers to an outer switch in a network topology that is linked to the primary root or backup root
bridge switch directly in one to two tier configurations, and indirectly in three to four tier configura-
tions.

ESD
Electrostatic Discharge

FCS
Frame Check Sequence

Fast Ethernet (FE)

Set of Ethernet standards that carry traffic at the nominal rate of 100 Mbps.

FTM
Frame Transfer Matrix

Full-Duplex
Transmission method that allows two network devices to transmit and receive concurrently, effectively
doubling the bandwidth of that link.

GBIC
Gigabit Interface Converter

HTTP
Hypertext Transfer Protocol

ICMP
Internet Control Message Protocol

xvii
B0700AZ – Rev V Preface

IEEE
Institute of Electrical and Electronics Engineers

IEEE 802.3
Defines carrier sense multiple access with collision detection (CSMA/CD) access method and physi-
cal layer specifications.

IEEE 802.3ab
Defines a media access method and physical layer specifications for 1000Base-T Gigabit Ethernet.

IEEE 802.3u
Defines a media access method and physical layer specifications for 100Base-TX Fast Ethernet over
CAT5 cable.

IEEE 802.3x
Defines Ethernet frame start/stop requests and timers used for paused flow control on full-duplex
links.

IEEE 802.3z
Defines a media access method and physical layer specifications for 1000Base Gigabit Ethernet.

IGMP
Internet Group Management Protocol, used to establish host memberships in particular multicast
groups on a single network.

IOC
Input/Output Controller (part of the Z-Module Control Processor (ZCP270))

IOM
Input/Output Module

IP
Internet Protocol

LAN
Local Area Network

LPA
Loop Protection Algorithm (Refer to Switch Configurator Application Software Guide for the Fox-
boro Evo Control Network (B0700CA) for more information.)

LDP
Loop Detection Policy (Refer to Switch Configurator Application Software Guide for the Foxboro Evo
Control Network (B0700CA) for more information.)

LED
Light Emitting Diode

xviii
Preface B0700AZ – Rev V

MAC
Media Access Control

MDI
Media Dependent Interface or Media Device Interface

MIB
Management Information Base

MMF
Multi-mode Fiber cable

NEM
Network Expansion Module

OMMO
Object Manager Multicast Optimization

PBQ
Primary Beacon Queryer - The switch with the lowest IP address and with the IGMP “Beacon”
enabled.

Policy
A group of rules which a network device uses to make forwarding, blocking, or port-disable decisions.

RFC
Request for Comment

RMON
Remote Monitoring

Role
A collection of services

RSTP
Rapid Spanning-Tree Protocol (IEEE 802.1w standard)

Rule Hit
An action when a packet classifier finds the packet.

Rules
Packet classifiers that are used to identify packet types on the network.

RXD
Receive Data

xix
B0700AZ – Rev V Preface

SBQ
Secondary Beacon Query - The switch with the second lowest IP address and with the IGMP “Bea-
con” enabled.

Service
A collection of Rules

SFP
Small Form Factor Pluggable (Type of Mini-GBIC)

SMF
Single-mode Fiber cable

SNMP
Simple Network Management Protocol

STP
Spanning-Tree Protocol (IEEE 802.1d standard)

TCP/IP
Transmission Control Protocol/Internet Protocol

TDR
Transient Data Recorder

TFTP
Trivial File Transfer Protocol

The Foxboro Evo Control Network

Formerly known as “The MESH Control Network”, a switched Fast Ethernet network based on IEEE
802.3u (Fast Ethernet) and IEEE 802.3z (gigabit Ethernet) standards. After the first mention of “the
Foxboro Evo Control Network”, subsequent mentions of this network use “the control network”.

TXD
Transmit Data

UTP
Unshielded Twisted Pair

VLAN
Virtual Local Area Network

xx
1. Introduction
This chapter provides an introduction to the concepts and equipment used in the Foxboro Evo
Control Network.

NOTE
The previously named "Security Enhanced Network" has been renamed as the
"Enhanced Network Configuration".

Overview of The Foxboro Evo Control Network

Architecture
The Foxboro Evo Control Network (“the control network”) is a switched Fast Ethernet network
based on IEEE 802.3u (Fast Ethernet) and IEEE 802.3z (Gigabit Ethernet) standards. The con-
trol network consists of a number of Ethernet switches connected in a mesh configuration.
The control network configuration allows high availability for end devices by providing
redundant data paths that help eliminate link loss, network device isolation, or issues that may
cause a loss of communications.The flexibility of the architecture allows you to design a network
configuration that fits the needs of the control system. A configuration can be as simple as a
workstation and controller connected with a single pair of switches, or as complex as a multi-
switch, fully meshed control network, communicating at speeds up to 1 gigabit per second.
The control network architecture integrates powerful control stations and workstations in a
100 Mb/1 Gb Ethernet network. These control stations, workstations, and networks comprise
scalable systems for process monitoring, process control and integration with industrial informa-
tion management systems.
High speed, coupled with redundancy and peer-to-peer characteristics, provides high
performance end-to-end device connectivity. Station interfaces to redundant Ethernet switches
provide redundant communications between stations.

NOTE
The graphics of switches and media converters in this document are intended as
generic illustrations of networking concepts and do not necessarily reflect the
currently offered products.

Switched Ethernet Features

Standard Fast Ethernet switches and fiber optic/copper cabling provide versatile solutions for
building the control network using industry standard protocols. The 12-port or larger managed
Ethernet switches used in the control network allow connection of multiple control stations,
workstations, and other Ethernet switches. Unmanaged switches are not supported by the FECN
control network because they offer no redundancy and diagnostics troubleshooting cannot be
performed on unmanaged switches.

1
B0700AZ – Rev V 1. Introduction

The Foxboro Evo Control Network Features

Two types of network configuration methods are available in the control network -
Standard Configuration and Enhanced Network Configuration.

Standard Configuration Features

The Standard Configuration of the control network provides these features:
♦ System scalability by interconnecting Ethernet switches with 16-ports or more in a
linear, ring, star, inverted tree, or modified inverted tree network topology
(configuration). The topology depends on the network site requirements.
♦ Ethernet switches connected in a mesh configuration with up to 1920 Foxboro Evo
stations (including switches - see Table 1-2)
♦ The FECN provides device connectivity support for Fast Ethernet (100 Mb) and
Gigabit Ethernet (1000 Mb)
♦ The FECN provides inter-switch connectivity with 1000Base-T and with modular
uplinks to the network’s high-speed backbones using 1 Gb 1000Base-T, 1000Base-SX,
1000Base-LX, 1000Base-LX/LH, 1000Base-ZX, and 1000Base-BX standards
♦ Full-duplex operation based on the IEEE 802.3 standards
♦ Rapid Spanning Tree Protocol (RSTP - IEEE 802.1w) which manages redundant
paths, helps prevent loops, and provides high speed convergence time for a network
♦ Network management and configuration through a local port or Web access for
various switches
♦ System Management software for monitoring the health of the control system and
managing equipment in the system
♦ Software in every station that manages redundant Ethernet ports in response to
network monitoring
♦ High speed response to detected network and station faults to provide a redundant
network

Enhanced Network Configuration Features

The Enhanced Network Configuration is now available to provide improvements in loop
detection not offered in the Standard Configuration. It provides all of the features listed in
“Standard Configuration Features” on page 2 as well as the improvements in loop detection policy
(LDP).
The Enhanced Network Configuration deploys specific network topologies and switch
configurations that allow for advanced network loop detection in the event of a detected RSTP
instability. This advanced network loop detection minimizes the potential for degraded network
communications in the event of RSTP instability.
Deploying the advanced network loop detection is accomplished by carefully designing the
network and correctly deploying the Loop Detection Policy (LDP) algorithms required for the
network design, and by following the network configuration requirements provided in this
document.

2
 NOTE
When designing an Enhanced Network Configuration network, each device/switch
within the network is required to be connected to two different switches within the
network. If the network is constructed with less than two connections between
devices/switches, data traffic could be disrupted if any single device goes offline or
there is a detected fault that causes the loop detection algorithm Rule Hit.

Loop Detection Policy (LDP) Deployed on The Foxboro Evo Control

Network
Due to the design of the Standard or Enhanced Network Configurations of the control network,
redundant links form physical loops in the network and are controlled (Blocked) by Rapid
Spanning Tree Protocol (RSTP), creating a logical loop-free network. However, in the event of a
network storm or some other RSTP instability, loops can form. In an Enhanced Network
Configuration, in addition to RSTP and LPA, Loop Detection (LDP) is deployed to block these
redundant loops.
A loop is detected by establishing a well-known data path and its source. To establish a known
path, the concept known as the “Beacon” is deployed. The Beacon routinely sends out an IGMP
data packet from the root to the edge switches of the network. In the event of a loop, the packet is
forwarded back towards the root. When the data packet is seen at an unexpected source port, the
assumption is that a loop occurred and an action (Rule) needs to occur. A switch’s port deployed
with “Circuit Breaker” disables the first port on which the incorrectly sourced packet is received.
Chassis switches, such as the N-Series Platinum (DFE) switches (P0973BQ, P0973BR,
P0973BT, and P0973BS) and S-Series switches (P0973KD, P0973KK and P0973LN), offer
advanced packet switching services that can scope data packets beyond the source and destination
MAC-address. By looking at other data points in the packets, the switch can make decisions on
which of these data points to mark a packet on. Once a particular packet is identified, the switch
can take action on it. The action of interest is disabling a looped port. Disabling this looping port
maintains a loop-free network. The switches alert the network administrator with SNMP traps
and syslog messages. Resolve these detected problems to 'fix' the network loop in a timely manner.
When disabled by the LDP, a disabled port can be monitored by SMDH through a link down
trap. Other methods of monitoring and management of ports can be accomplished by utilizing
the switch's CLI port or NetSight™ Console.

NOTE
A false hit on the redundant backup root bridge port occurs when LDP is deployed
across the network on S-Series switches when both of these conditions have been
met:
– The Foxboro Evo root switch hosting monitor (SMDH, System Monitor, etc.) is
offline or the designated NetSight Console server is offline. (Root switches must be
configured to report to the monitoring device that has been taken offline.)
– An event (port detected failure, switch detected failure, and so on) causes the
network to re-span.
If both of these events occur and the primary root bridge port is online, the backup
root switch’s redundant backup root bridge port becomes disabled. If the
primary root bridge port is offline, this event does not occur

3
B0700AZ – Rev V 1. Introduction

Loop Protection Algorithm (LPA)

The Loop Protection Algorithm (LPA) is a feature developed for the control network to help pre-
vent short circuit loops in a network with redundant paths, by requiring ports to receive type 2
BPDUs (Bridge Protocol Data Units) (RSTP/MSTP) on point-to-point inter-switch links (ISLs)
before their states are allowed to go to forwarding. Further, if a BPDU time-out occurs on a port,
its state transitions to its listening state until a BPDU is received.
LPA helps protect both upstream and downstream facing ports. When a root or alternate port
loses its path to the root bridge due to message age expiration, it takes on the role of designated
port. It does not forward traffic until a BPDU is received. When a port is intended to be the
designated ISL port, it constantly proposes and does not forward packets until a type 2 BPDU is
received, and reverts to listening if it gets no response. This helps protect against mis-
configuration and RSTP instability by the connected bridge. LPA operates as per port, per MST
instance. LPA is required to be set on all inter-switch links. LPA is made up of several related
functions:
♦ Control of port forwarding state based on reception of agreement BPDUs
♦ Control of port forwarding state based on reception of disputed BPDUs
♦ Communicating port non-forwarding status through traps and syslog messages
♦ Disabling a port based on the frequency of events
There are two LPA features within the Foxboro Evo Control Network "Legacy" and "Enhanced".
For more information on which switches support these features, refer to Table 1-1 and the Switch
Configurator Application Software Guide for the Foxboro Evo Control Network (B0700CA).

Table 1-1. Differences Between Legacy LPA and Enhanced LPA

Legacy LPA Enhanced LPA

Legacy Loop Protection Algorithm (LPA) func- Enhanced Loop Protection Algorithm (LPA)
tionality cannot guarantee sub-second failover helps prevent packet flooding (e.g. network
and network storming under one second. storming, generally less than one second) during
a network storm (RSTP instability), which
helps to prevent packet loss between devices
(when devices have multiple data paths).

4
 NOTICE
POTENTIAL DATA LOSS

• S-Series Firmware 7.61.09.0001

Legacy Loop Detection Policy (LDP) cannot be deployed on
the inter-switch link (ISL) ports between Tier 1 (root) and Tier
2 of an instance of the control network when both Tiers are S-
Series switches running with SCAS 3.5.2 and firmware
7.61.09.0001. LDP cannot be deployed on the ISL ports
between the two root switches. Loop Protection Algorithm
(LPA) can be deployed on the ISL ports between Tier 1 and
Tier 2 with S-Series switches and also on the root ISLs with
firmware 7.61.09.0001.
• S-Series Switches
The S-Series switches have been known to cause network
instability when "Legacy" LDP and/or "Legacy" LPA deployed
in a network. Install firmware 08.32.02.0008/.0009 or greater
on all S-Series switches to prevent these issues. To download
this firmware, refer to Switch Configurator Application
Software Guide for the Foxboro Evo Control Network
(B0700CA), Chapter 12, "Downloading Qualified Firmware
Images"

Failure to follow these instructions can result in data loss.

Virtual Local Area Networks (VLANs) on The Foxboro Evo Control

Network
A VLAN acts like an ordinary Local Area Network (LAN), but in a VLAN, connected devices do
not have to be physically connected to the same segment. The VLAN allows devices located in
separate areas or connected to separate ports to belong to a single VLAN group. Devices that are
assigned to such a VLAN group, send and receive broadcast and multicast traffic as though they
were connected to a common network. VLAN-aware switches isolate broadcast, multicast, and
unknown traffic received from VLAN groups, so that traffic from stations in a VLAN are con-
fined to that VLAN.
Additional details about VLANs are provided in Switch Configurator Application Software Guide
for the Foxboro Evo Control Network (B0700CA, revision W or later), in Chapter 11, “Using
VLANs on The Control Networks” and Appendix D, “Understanding Virtual Local Area Net-
works (VLANs)”.

The Foxboro Evo Control Network - Overview

The control network is designed to provide multiple communication paths between any two
devices or stations connected to the network. This network architecture provides very high avail-
ability, while reducing network complexity, cost, and maintenance requirements.

5
B0700AZ – Rev V 1. Introduction

The Foxboro Evo Control Network Topologies

There are several basic control network topologies for the control network supported by the Fox-
boro Evo system. These are:
♦ Linear
♦ Ring
♦ Star
♦ Inverted tree
♦ Modified inverted tree

NOTE
When constructing the Enhanced Network Configuration, do not use the ring
topology when deploying this configuration.

Each configuration/topology listed has unique features and the one chosen for a particular net-
work depends on the specific requirements of the site or installation. The diagrams in “The Fox-
boro Evo Control Network Topologies” on page 34 provide examples of the different topologies
as well as recommendations on where they might be used.

NOTE
The star topology is the preferred topology for FECN networks, provided that geo-
graphical constraints allow this topology.

6
The Foxboro Evo Control Network - Network Details
Network Example
The control network utilizes qualified Fast Ethernet switches which are configured to form a
highly robust redundant network. Figure 1-1 on page 8 shows an example with several Foxboro
Evo stations and Control Processors connected redundantly to the control network.
Workstations are also redundantly connected to the Fast Ethernet switches.
The Z-module Control Processor 270 (ZCP270) main processor’s Ethernet ports connect to the
control network, where the ZCP270 I/O controller (IOC) ports have the option of connecting
directly to the control network or a dedicated I/O network.
The Fieldbus Communications Module (FCM100Et or FCM100E) provides the interface
between the ZCP270 and the FBMs and connects to the control network or a dedicated I/O net-
work.
When designing the control network architecture, address the following concerns:
♦ For critical I/O communications, which in this context can be defined as I/O applica-
tions that cannot allow for a disruption of fieldbus communications over a five second
span, place the ZCP270 IOC and FCM I/O on a separate network.
♦ For non-critical I/O communications, the FCM100s and ZCP IOC ports can con-
nect directly to the control network. Whenever possible, attach the ZCP IOC ports
and FCMs to the same switches within the network, keeping the ZCP IOC to FCM
communications local to the switch (see Figure 1-1).
If a dedicated I/O network is to be employed, use a simple linear topology and switch selection,
per the standard guidelines for the control network, where the ZCP270 I/O controller (IOC)
ports A/B and FCM I/O ports A/B (Fieldbus A and Fieldbus B) A side and B side are separated on
independent networks. It is also possible to have multiple I/O networks, such as having an I/O
network for each ZCP IOC and its FCMs.

NOTE
A single switch pair can accommodate multiple ZCPs and FCMs. If isolation of the
CP I/O is desired, VLANs can be created on the I/O network switches or
independent switch pairs can be utilized.

NOTE
Switches on a dedicated I/O network cannot be seen in SMDH or System Manager.
However, Fieldbus A and Fieldbus B errors are indicated in a normal manner using
the “Sys” Key and are visible in SMDH or System Manager. Also, a dedicated I/O
network cannot be used for FBMs using the GPS SOE/TDR time sync package (see
Time Synchronization User's Guide (B0700AQ)).

For more information on configuring a dedicated I/O network, refer to “I/O Network Design
Rules” on page 34 and “I/O Network Topology Configurations” on page 55.

7
B0700AZ – Rev V 1. Introduction

ZCP270

INFORMATION NETWORK

WORKSTATIONS

SPLITTER/
COMBINERS

ETHERNET
SWITCHES

THE FOXBORO EVO

CONTROL NETWORK

SPLITTER/COMBINER
(NOT USED WITH FCM100E)
DIN RAIL
FCP280 BASEPLATE

FCM100Et FBM
FBM
or FCM100E

DIN RAIL
BASEPLATE

TO/FROM TO/FROM
PROCESS PROCESS

Figure 1-1. The Foxboro Evo Control Network (Star Topology Shown)

8
 The FOXBORO EVO
CONTROL NETWORK

ZCP270

SPLITTER/
COMBINERS

I/O NETWORK

SPLITTER/COMBINER
(NOT USED WITH FCM100E)
DIN RAIL
BASEPLATE

FCM100Et FBM
or FCM100E

TO/FROM
PROCESS

Figure 1-2. The Foxboro Evo Control Network with an I/O Network

9
B0700AZ – Rev V 1. Introduction

The Foxboro Evo Control Network Specifications - Overview

The Foxboro Evo Control Network Constraints
In evaluating the performance of the control network, consider the following criteria when
designing large networks:
♦ Network Convergence - Network Convergence time is a measure of how fast a group
of Ethernet switches reach a stable network topology. It is one of the main design goals
of the control network as it is critical that the network is able to support the sending
and delivery of the initial data following a topology change within the timeout period
of the applications which use the network.
♦ Network Delay - The delay of a network specifies how long it takes for a bit of data to
travel across the network from one node or endpoint to another. It is typically
measured in multiples or fractions of seconds. Delay may differ slightly, depending on
the location of the specific pair of communicating nodes. Delay is typically reported as
maximum and average delay and divided into several parts:
♦ Processing delay - time routers take to process the packet header
♦ Queuing delay - time the packet spends in routing queues
♦ Transmission delay - time it takes to push the packet's bits onto the link
♦ Propagation delay - time for a signal to reach its destination
♦ Packet queuing and de-queuing, packet reception.
When designing large networks, network traffic needs to be taken in consideration. Due to net-
work traffic considerations, networks greater than 250 switches are only supported on the control
network’s Inverted and Modified Inverted Tree topologies. Using the Inverted Tree topology and
utilizing a four (4) tier network approach can greatly decrease the root bridge traffic required for
the network convergence and pass through communications. Whenever possible, use a ten to two
(10:2) approach when designing these large networks, where each branch of the network is 10
edge switches (Tier 4) to two distribution switches (Tier 3), 10 distribution switches (Tier 3) to
two distribution switches (Tier 2), and five distribution switches (Tier 2) to two root switches
(Tier 1).

Address Translation Stations (ATS) Guidelines

When connecting the Nodebus to the control network:
♦ Monitor all ATS stations for dropped packets
♦ Do not allow historization of data across the ATS unless Object Manager Multicast
Optimization (OMMO) is implemented on the station with the historian.
♦ Minimize peer to peer connections across an ATS, including:
♦ Nodebus to the control network connections
♦ Nodebus to Nodebus connections across an ATS.
♦ Verify that any data exchanged between Nodebus and the control network is able to
tolerate transient traffic rates and possible dropped packets in the connecting ATS.
♦ Some containment of transient multicast traffic can be achieved by blocking specific
Foxboro Evo Multicast addresses at the switch ports connected to the ATS stations if
multicast traffic rates measured on the system are determined to be too high.

10
 ♦ Background traffic in the system due to switches - BPDUs and SNMP packets - can
also be blocked at the switch ports connected to the ATS stations to reduce the traffic
load on the ATS. BPDU packets are not passed through the ATS to Nodebus, how-
ever, the ATS still processes the packet consuming CPU cycles in the ATS. SNMP
packets are passed through to the Nodebus side.
♦ The ATS throttles the multicast rate into the node to 20 per half second.
♦ Upgrade or replace some older station types on the node (See FAQ 38 on the GCS
website).

Specifications

Table 1-2. The Foxboro Evo Control Network Specifications

Specifications
Number of Foxboro Evo stations connected 1920 Foxboro Evo stations including switches, maximum (FCM100Ets
to the control network and FCM100Es are not included in count). Up to 500 switches.
Number of Ethernet switches between any Seven maximum
two stations
Number of IP addresses 10,000 maximum includes switches, controllers, workstations and
FCM100Ets and FCM100Es.
VLANs on the control network Six (6) configurable VLANs are supported on the control network
Standards Supported 100 Mb Full-duplex operation for fiber optic and copper cable.
Modular uplinks using 1 Gb 1000Base-T, 1000Base-SX,
1000Base-LX, 1000Base-LX/LH,1000Base-ZX, and 1000Base-BX stan-
dards
Speeds Supported Fast Ethernet (100 Mb) and uplink Gigabit Ethernet (1000 Mb)
Protocols Used Rapid Spanning Tree Protocol (RSTP - IEEE 802.1w), 802.3, 802.3ad
Cable Lengths - Interconnecting stations or CAT5:100Base-TX or 1000Base-T; 100 m (328 ft) maximum
Ethernet switches Fiber optic:
100Base-FX; 2 km (6,560 ft) maximum (MMF)
1000Base-SX; 275 m (900 ft) maximum (MMF)
1000Base-LX/LH; 2 km (6,560 ft) maximum (MMF)
1000Base-LX; 10 km (6.2 mi) maximum (SMF)
1000Base-BX; 10 km (6.2 miles) maximum (S-SMF)
1000Base-BX; 40 km (24.85 miles) maximum (S-SMF)
1000Base-ZX; SMF, 80 km (49.7 miles) maximum (SMF)
1000Base-BX; 120 km (74.5 miles) maximum (S-SMF)
Cable Lengths - Total connection length Single mode fiber (SMF), 80 km (49.7 mi) maximum
allowed between switches Multimode fiber (MMF), 2 km (6,560 ft) maximum
Simplex-Single mode fiber (SMF), 120 km (74.5 mi) maximum
The Control Network Distance Note that the total network delays between two end devices should not
exceed 100ms roundtrip. This assumes that CPs are running a BPC of
0.5 seconds and are not using a 100ms OM Scanner.

For more information, refer to these Product Specifications Sheets:

♦ The Foxboro Evo Control Network Architecture (PSS 31H-7NETWORK)
♦ The Foxboro Evo Control Network Ethernet Equipment (PSS 31H-7NwEquip).

11
B0700AZ – Rev V 1. Introduction

The Foxboro Evo Control Network Workstations

Foxboro Evo workstations can be connected to the control network. These workstations provide
host services to fault-tolerant control processors. In addition, the workstation provides the opera-
tor interface for the display of graphic and textual information.
Each workstation connects to the switches in the control network by way of copper or fiber inter-
face cards in the workstation. Two Network Interface Cards (NIC) are offered:
♦ 100Base-FX
♦ 10/100Base-TX
Virtual Servers (V90) connect to the switches in the control network by way of copper or fiber
interface cards in the workstation. Two Network Interface Cards (NIC) are offered:
♦ 1000Base-FX
♦ 1000Base-TX
The workstation can be directly connected to Ethernet switches or through the use of a media
converter, described in Media Converter Installation and Configuration Guide for Control Networks
(B0700CP). In addition, the built-in Ethernet interface on the workstation’s motherboard can be
used to interface to a plant information network.

The Foxboro Evo Control Network Ethernet Switches

A switch is an active multiport network and bridge device that provides a separate collision
domain for each port, and uses Media Access Control (MAC) layer to direct network packets to
the appropriate station or switch. This allows multiple simultaneous communications among net-
work devices connected to the switch.
The control network is a switched Fast Ethernet network based on IEEE 802.3u (Fast Ethernet)
and IEEE 802.3z (gigabit Ethernet) standards, and utilizes standard commercial off-the-shelf
Ethernet switches to allow you to configure your system to meet your functional, performance
and plant requirements. Switches listed in “Reference Documents” on page xiv have been tested
and qualified by Foxboro for use with Foxboro Evo products.

NOTICE
POTENTIAL DATA LOSS

Using non-qualified switches may cause RSTP instability. The list of

vendors and their qualified switches can be obtained from the Global
Customer Support Center web site at
https://pasupport.schneider-electric.com

Failure to follow these instructions can result in data loss.

12
 Refer to the documentation included with your Foxboro qualified Ethernet switches for details of
their capabilities.

The Foxboro Evo Control Network Approach to High Availability

The control network is designed to provide high availability through redundant network commu-
nication paths while at the same time achieving the highest possible loop prevention.
Mechanisms are in place to block redundant paths to help protect the control network from data
storms:
♦ RSTP (Rapid Spanning Tree Protocol) is used in both Standard and Enhanced
Network Configurations and blocks redundant links.
♦ CoS LDP (Loop Detection Policy) is deployed on Enhanced Network Configura-
tions. It monitors the network for loops, disabling the port once a maximum number
of Beacon packets have been received on the ingress port. Failover is deterministic of
the packet rate of the network storm.
♦ Enhanced LPA (Loop Protection Algorithm) is needed for both Standard and
Enhanced Network Configurations which monitors the network for loops and blocks
network traffic from propagating across network loops while helping prevent packet
flooding during a network storm (RSTP instability), this allows minimal packet loss
between devices (when devices have multiple data paths).
The control network employs Rapid Spanning Tree Protocol (RSTP) in conjunction with Loop
Protection Algorithm (LPA) to provide handshaking between switches to control, or block, physi-
cal loops so that the control network can provide redundancy within a logical loop-free network.
The Enhanced Network Configuration also employs the use of Loop Detection Protocol (LDP)
in certain configurations to monitor the network for loops and to disable ports in the event that a
loop is detected. LDP monitors the uplink ports, by sending out a pre-defined IGMP data packet
or “Beacon”, and establishing expected data paths. LDP periodically sends out the Beacon data
packets and, if a data packet is detected on an unexpected ingress port, LDP assumes that a loop
exists and it disables the port to help prevent network data storms.

Advantages of Foxboro-Supplied Switches

The control network requires switches purchased from Foxboro. This provides a number of
advantages, described here.
♦ Can customers include Ethernet switches from other suppliers for use in the control
network?
Only Foxboro-supplied Ethernet switches have been qualified for use in the Foxboro
Evo system. Other switches may or may not work and may not meet the performance
specifications required for a secure, reliable high performance in the control network.
♦ Why won't other switches provide the same performance?
The Foxboro-supplied switch is off the shelf equipment and has been optimized to
meet the stringent performance specifications for the control network. For example,
the Rapid Spanning Tree Protocol algorithm that manages traffic paths is optimized to
meet the requirement for network recovery on failure of a root switch in less than one
second. This level of performance is much better than is typically achievable with
other vendor's hardware and RSTP implementation.

13
B0700AZ – Rev V 1. Introduction

♦ Can customers purchase switches from third parties with the correct certified firm-
ware to work with the Foxboro Evo system?
Although switches qualified for use with Foxboro Evo systems can also be purchased
from third parties, they will not necessarily have been furnished with the correct firm-
ware version that has been qualified.
♦ What other disadvantages are there if unqualified switches are used in the control
network?
The Switch Configurator Application Software (SCAS), supplied with the Foxboro-
supplied switch, is also designed to configure switches qualified by Foxboro, making
configuration easier, quicker, more reliable and facilitates troubleshooting and config-
uration verification. Using the SCAS tool to configure switches eliminates errors
caused by typing commands incorrectly, when entering a command. When non-qual-
ified switches are used, commands must be manually entered, increasing the potential
for misconfiguration. A mapping process is also required map the commands used by
Foxboro-qualified switches to a non-qualified vendors command set.
♦ How could a user get the correct firmware?
They would need to contact Foxboro and either purchase replacement firmware for
each switch on a one time charge basis or purchase a Foxboro support contract which
would cover the cost of replacement firmware.? Is the firmware provided by Foxboro
for the control network switches exclusive to Foxboro-supplied switches? Changes to
the firmware used in Foxboro Evo systems are included in the standard product. Peri-
odically, changes are made to the firmware; future versions of the firmware which have
not been qualified by Foxboro may or may not be compatible with Foxboro Evo
systems.

Control Network Cabling

Four different types of cabling of various lengths may be used:
♦ Shielded twisted-pair 100Base-T CAT5 cabling - 100 m (328 ft.) maximum
♦ Shielded twisted-pair 1000Base-T CAT5 cabling - 100 m (328 ft.) maximum
♦ Multimode fiber optic cabling - 2 km (1.25 mi) maximum for 100Base-FX
♦ Multimode fiber optic cabling - 275 m (900 ft) maximum for 1000Base-SX
♦ Multimode fiber optic cabling - 550 m (1800 ft) maximum for 1000Base-LX
♦ Multimode fiber optic cabling - 2 km (1.25 mi) maximum for 1000Base-LX/LH
♦ Single mode fiber optic cabling - 10 km (6.21 mi) maximum for 1000Base-LX
♦ Simplex single mode fiber optic cabling - 10 km (6.21 mi) maximum for
1000Base-BX10.
♦ Single mode fiber optic cabling - 80 km (49.68 mi) maximum for
1000Base-ZX/ELX.
♦ Simplex single mode fiber optic cabling - 40 km (24.8 mi) maximum for
1000Base-BX40
♦ Simplex single mode fiber optic cabling - 120 km (74.53 mi) maximum for
1000Base-BX120.

14
Category 5 Cabling
There are two basic configurations of Category 5 (CAT5) cables:
♦ Straight-through cables: Cables used to connect workstations to Ethernet switches,
and media converters to Ethernet switches.
♦ Crossover cables (also called a null hub): Cables used to interconnect Ethernet
switches.
Some switches have auto MDI/MDI-X ports (for example, 24-Port Copper) which provide the
crossover and do not require a crossover cable.

NOTE
All Category 5 cabling must be of shielded type for optimal interference mitigation.

Normally, when one switch is connected to another, the transmit and receive wires must be
crossed over, such that the transmit wires from switch #1 connects to the receive wires from
switch #2, and vice versa. Crossover cables are used much less frequently than straight-through
cables. A straight through cable can be used as a crossover cable if used in conjunction with a null
hub cable adapter (P0971PK).
A null hub is a very short cable that has a male RJ-45 connector on one end and a female RJ-45
connector on the other. The transmit and receive wires are reversed, so when it is connected to the
end of a straight-through cable, the resulting cable system can act as a crossover cable. The null
hub is used to interconnect switches using straight-through CAT5 when neither switch is
equipped with auto MDI/MDI-X ports (crossover port).

Fiber Optic Cabling

The fiber optic cable’s electrical isolation characteristics provide protection from voltage differen-
tials and ground loops and permit communication installations to pass through areas where
intrinsically safe operation is required. The fiber optic cable is unaffected by electrical noise such
as EMI and RFI and can be installed even in these cases, where copper cables may not be accept-
able:
♦ Areas containing rotating machinery, arc welders, and so forth
♦ Cable trays containing high voltage power lines
♦ Outdoor areas exposed to lightning hazards (with appropriately rated cable)
♦ Areas containing strong magnetic fields
♦ Longer distances than twisted pair cable.
Three different types of fiber optic cable may be used in the control network:
♦ Single mode cable
♦ Simplex single mode (single strand) cable
♦ Multimode cable (switch-to-device connections and uplink connections).

15
B0700AZ – Rev V 1. Introduction

NOTE
Single mode and multimode fiber optical devices are not compatible. Both devices
being connected (and the cable) must be of the same type in order to help ensure
proper operation. In certain limited cases (connecting Ethernet switch uplink ports,
for example), a mode conditioning cable may be employed so that multimode fiber
cable can be used with a single mode device. Refer to the “Ethernet Switch Inter-
connection Diagrams” in the documentation included with your Foxboro-qualified
Ethernet switches for specific information.

NOTE
The fiber optic cables mentioned in this document may require additional
mechanical protection, particularly when run between different enclosures.

Single Mode Cable

In the control network, single mode fiber optic cable can be used to connect Ethernet switches to
each other through each switch’s uplink port. Design the uplink ports of each of the switches
being connected for single mode operation. Refer to the “Ethernet Switch Interconnection Dia-
grams” in the documentation included with your Foxboro qualified Ethernet switches for infor-
mation on uplink modules for use with single mode fiber optic cable.

Simplex Single Mode Cable

In the control network, simplex single mode fiber optic cable is a single strand of SMF fiber that
can be used to connect Ethernet switches to each other through each switch’s uplink port. Design
the uplink ports of each of the switches being connected for simplex single mode operation. To
use simplex single mode fiber, bi-directional Mini-GBICs must be used, listed in the switch’s own
documentation. Use an upstream and downstream GBIC, each transmitting on the same fiber but
at different frequencies. When ordering these Mini-GBICs, acquire a matching pair, one of each
type. When ordering these devices, always order using a kit number, which includes one of each
of these modules. These kit numbers are listed in each switch’s specific document.

Multimode Cable
Multimode fiber optic cable is employed in different situations in the control network:
♦ Controller to Switch - The Foxboro Evo control processors connect to the Ethernet
switch(es) through 100Base-FX port(s) using a multimode fiber optic cable termi-
nated with LC connectors.
♦ Field Communications Module (FCM) to Switch - The redundant Foxboro Evo
FCMs connect to the Ethernet switches through 100Base-FX ports using a multi-
mode fiber optic cable terminated with LC connectors.
♦ Workstation to Ethernet Switch - A workstation is capable of connecting directly to
Ethernet switch’s 100Base-FX port using a multimode fiber optic cable terminated
with LC to MT-RJ connectors. An Ethernet switch without a fiber optic port, can use
two media converters between the switches and the workstations. Connection is based
on NIC type and switch type. Media converters can be used when NICs do not match
switch ports.

16
 ♦ Ethernet Switch to Ethernet Switch - Ethernet switches that are equipped with multi-
mode fiber uplink ports can be connected directly to each other. The fiber optic cable
should be terminated with LC type connectors, depending on the switch interface
modules.
Table 1-3 lists some typical and worst case power losses for fiber optic cable, splitter/combiners,
and patch cords.

Table 1-3. Fiber Cable Power Losses

Link Element Expected Value Comments

Splitter/Combiner 4.5 db
MT-RJ Patch Cord 0.5 db 0.75 db worst case
LC, SC, and other simi- 0.15 db 0.5 db worst case
lar patch cords
Singlemode fiber cable 0.5 db/km at 1300 nm wavelength
(SMF) 0.275 db/km at 1550 nm wavelength
Simplex-Singlemode 0.33 - 0.35 db/km at 1310 nm wavelength
fiber cable 0.21 - 0.24 db/km at 1490 nm wavelength
(Simplex-SMF)1 0.19 - 0.20 db/km at 1550 nm wavelength
0.20 - 0.23 db/km at 1625 nm wavelength
Multimode fiber cable 1.0 db/km at 1300 nm wavelength
(MMF) 3.5 db/km at 850 nm wavelength
Splice loss 0.25 db Mechanical splice
50/125 μM mating 5.25 db -5.0 dB mating loss and a -0.25 dB for
62.5/125 μM loss mechanical splice
Aging reserve 1.0 db 62.5/125 micron cable
Patch Panel loss 2.0 db average
1.
These db losses may vary in the S-SMF cables depending on the mandrel diameter due to
macrobend loss.

Table 1-4 lists the available Mini-GBIC transceivers which can be used with the switches in the
control network - refer to the Foxboro manuals included with each switch for details on their
installation and use.

Table 1-4. SFP Mini-GBIC Transceivers

Cable
Foxboro Part Cross Reference Type
Number Part Number Supported Description
RH102AL 10070H RJ-45 10/100/1000Base-TX
100 m (330 FT) MGBIC module RJ-45 (TX)
P0972YQ MGBIC-LC03 LC 1000Base-LX\LH MMF
2 km MGBIC module LC LX/LH (1310nm)

17
B0700AZ – Rev V 1. Introduction

Table 1-4. SFP Mini-GBIC Transceivers (Continued)

Cable
Foxboro Part Cross Reference Type
Number Part Number Supported Description
P0972WT MGBIC-LC01 LC 1000Base-SX MMF
275 m MGBIC module LC SX (850nm)
P0972WU MGBIC-LC09 LC 1000Base-LX (10 km (6.2 mi)) SMF
MGBIC module LC LX (1310nm)
P0973LV MGBIC-08 LC 1000Base-ZX SMF
80 km (49.6mi) MGBIC module LC ZX
(1550nm)
P0973GJ1 I-MGBIC-GSX LC Industrial 1000Base-SX MMF
275m MGBIC module LC SX (850nm)
P0973GH1 I-MGBIC-GLX LC Industrial 1000Base-LX SMF
10 km (6.2 mi) MGBIC module LC LX
(1310nm)
P0973LV1 MGBIC-08 LC Industrial 1000Base-ZX SMF
80km MGBIC module LC ZX (1550nm)
P0973JA1 I-MGBIC-LC03 LC Industrial 1000Base-LX\LH MMF
2 km MGBIC module LC LX/LH (1310nm)
Kit P0973JD2 Simplex 1000Base-BX (10 km (6.2 mi)) S-SMF
P0973JB MGBIC-BX10-U LC 10 km MGBIC module Bi-directional
P0973JC MGBIC-BX10-D Up/Down S-LC BX (1310nm/1490nm)
Kit P0973KP3 Simplex 1000Base-BX (40 km (25 mi)) S-SMF
P0973KM MGBIC-BX40-U LC 40 km MGBIC module Bi-directional
P0973KN MGBIC-BX40-D Up/Down Link S-LC BX (1310nm/1490nm)
Kit P0973KS4 Simplex 1000Base-BX (120 km (74.6 mi)) S-SMF
P0973KQ MGBIC-BX120-U LC 120 km MGBIC module Bi-directional
P0973KR MGBIC-BX120-D Up/Down S-LC BX (1490nm/1590nm)
P0973JE5 MGBIC-LC04 LC 100Base-FX MMF
2 km MGBIC module 100Mb LC LX
(1310nm)
1. Industrial Mini-GBIC to be used with I-Series switch (P0973GA) with thermal limits of -40 to
+60°C (-40 to +140°F).
2. Kit P0973JD contains both the “upstream” Mini-GBIC (P0973JB) and the “downstream” Mini-
GBIC (P0973JC).
3. Kit P0973KP contains both the “upstream” Mini-GBIC (P0973KN) and the “downstream” Mini-
GBIC (P0973KM).
4. Kit P0973KS contains both the “upstream” Mini-GBIC (P0973KQ) and the “downstream” Mini-
GBIC (P0973KR).
5. P0973JE is a 100Base-FX Mini-GBIC and is for end 100Mb device connectivity which is not
intended to be used as an ISL uplink GBIC.

18
2. Site Planning
This chapter describes the steps to take and the options to consider when planning the Foxboro
Evo Control Network.
The design of each instance of the control network is different, and depends on the needs and
requirements of the individual site. The next sections provide information to help network
designers plan the control network that meets the needs of their specific site.

Site Planning Overview

The control network allows communication between the control stations, workstations, and Field
Communications Modules (FCMs) connected to the network. This network is formed by
interconnecting the control stations and workstations through the use of fiber optic or copper
cable, Ethernet switches and, if necessary, media converters. Although copper cables can be used,
fiber cables are recommended for industrial networks. In a properly constructed network, the
stations on the network are able to communicate with each other. For a high degree of reliability,
construct the control network so that there are redundant signal paths between each device on the
control network.
Although the design of the control network is driven largely by the site’s physical environment,
traffic and organizational requirements, there are rules to follow when connecting devices to form
the control network. The next two sections explain the factors affecting the physical environment
and the traffic considerations of the control network.

Network Considerations
The physical location of equipment at the site influences the control network design. To choose
equipment and cabling appropriate to the requirements for the specific site, use the answers to the
following questions, along with the control network design rules and device/cable specifications
in this chapter and Appendix A “COMEX Fault Handling on The Foxboro Evo Control
Network”.
♦ What is the maximum end-to-end distance between devices in the control network?
The distance between the ends of the control network may determine what kind
of Ethernet switches are used and what kind of cabling is used between those
switches. If individual cable runs are greater than a hundred meters, it is necessary
to use fiber optic cable, due to its capability for transmitting signals over longer
distances. Consider all hardware when the network requires multiple hops. Do
not use switches that are not designed as a distribution switch in the network core.
The total network delays between two end devices should not exceed 100 ms.
♦ Will the control network be deploying VLANs other than VLAN2 (required for the

19
B0700AZ – Rev V 2. Site Planning

FECN)?

NOTE
When setting up a first time installation of the control network, deploy VLAN 2
“FECN” on all ports used for communications between Foxboro Evo devices.
(Refer to NOTICES below.)
If a system is up and functional without VLAN 2 deployed across the network, a
system shutdown is required to deploy VLANs. If VLAN 2 is deployed prior to
system startup, additional VLANs can be added at a later date without system
interference (shutdown).

♦ If yes, how many VLANs will the control network require?

The control network supports up to six VLANs, one (1) of which must be reserved for
Foxboro Evo system devices (VLAN 2 “I/A Control Ports”), and all Foxboro Evo con-
trol devices shall be attached to VLAN 2 FE ports.
Only one Foxboro Evo control system can be supported on the control network.
There can be no duplicate MAC addresses across the control network VLANs.
Since VLAN2 is needed for the Foxboro Evo control network, VLAN2 needs to be
enabled on the uplink ports for all the switches in the control network
.

NOTICE
POTENTIAL DATA LOSS

• When VLANs are added to an existing installation of the control

network, move all Foxboro Evo devices to VLAN2. Until this
occurs, the communications between the Foxboro Evo devices
are broken.
• Connect all Foxboro Evo devices to Device ports that have
been assigned to VLAN 2 FECN or “I/A Control Ports”. If this is
not done, the Foxboro Evo devices on the network cannot com-
municate correctly with each other. Refer to the “Flowchart for
Assignment of Uplinks and Ports to VLAN” figure in the
“Switch Configuration Parameters Dialog Box” section in
Switch Configurator Application Software Guide for the Foxboro
Evo Control Network (B0700CA).
• If VLANs are to be utilized in the control network, all switches
within the network are required to be configured for all utilized
VLANs. If a VLAN is configured on an outer edge switch and a
core switch has not been configured for that VLAN (in the case
where no port assignment is required), data from the outer
edge switch VLAN will not propagate through the core switch.

Failure to follow these instructions can result in data loss.

20
2. Site Planning B0700AZ – Rev V

♦ What will the protocols be on the non-Foxboro Evo VLANs?

VLANs other than VLAN 1 and 2 shall not utilize protocols other than TCP/IP
and/or UDP/IP.
♦ What will be the loading on the FE device ports?
No VLAN Port shall exceed 50% loading.
♦ What is the non-Foxboro Evo VLAN end device speed usage?
No end devices with transfer (Tx) and receive (Rx) speeds greater than 100Mb are
supported.
♦ Will the switch be installed in an adverse environment?

NOTICE
POTENTIAL DATA LOSS

• Use an X-Series switch when installing switches within the

same enclosure as the Control Processors.This switch has
been developed for this purpose.
• Also be aware that all switches currently offered other than the
X-Series switch are not suited for the same conditions in which
the CP/FCM can operate.
• If switches are installed within the same enclosure, the overall
environmental rating of this enclosure is reduced to a class G1
rating.

Failure to follow these instructions can result in data loss.

♦ How many control stations and workstations will be connected to the control
network?
The number of control stations and workstations influences how many Ethernet
switches and separate cables are included in the control network. It may be wise to
plan for expansion and growth when arriving at this number.
♦ How are the control stations and workstations distributed?
The physical distribution of control stations and workstations can have a bearing on
the type and number of Ethernet switches, as well as the type of cabling used. If the
control stations and workstations are clustered together, two larger capacity switches
may be able to accommodate them all. If they are dispersed, several smaller switches
may be a better solution. For large distances and noise protection, use fiber optic
cables between switches. You can also use fiber optic cables between switches and con-
trol stations, workstations, or FCMs. Consider cable routing between devices.
♦ Will the control network have redundant signal paths?
Yes, a control network with redundant paths is recommended for all control systems.
♦ Through what kind of physical environment will the cabling pass?
Fiber optic cable is immune to magnetic fields and electrical noise, so it can be used in
places where copper cable would be unreliable. If cabling must be routed through

21
B0700AZ – Rev V 2. Site Planning

areas subject to high EMI or RFI, we recommend fiber optic cable. Due to its
immunity to lightning, use fiber optic cable (rated for outdoor use) for outdoor cable
runs.
♦ Where will the equipment be located?
Will switches be mounted in racks, in cabinets, or placed on shelves or tabletops? Take
into consideration thermal requirements, especially if the equipment will be mounted
in an enclosed cabinet or area. Avoid high or moderate electromagnetic noise sources,
for example, machinery, switchgear, high-voltage lines, and so forth, in close
proximity, to help provide reliable operation.
♦ Have plans for future expansion been considered?
Consider installing Ethernet switches with additional ports so that control stations or
workstations can be easily added in the future. Running extra copper or fiber optic
cable allows for network expansion later.
♦ Have maintenance and troubleshooting provisions been made?
Leaving at least one unused port on each Ethernet switch allows for maintenance and
troubleshooting of managed switches. A system network management package
(SNMP) must be available that runs on a separate PC, not a Foxboro Evo
workstation. Patch panels at the end of cable segments facilitate troubleshooting and
network re-configuration.
♦ Newer switches use 1 Gb uplinks. Can a new iteration of the control network be built
including legacy 100 Mb uplinks?
While an implementation of the control network may be built using 100 Mb uplinks,
this is not recommended due to loading concerns. Enhanced Network Configurations
need to use 1 Gb uplink ports.
♦ Are ample AC power outlets available at the proper location:
♦ For the chassis switch?
♦ For switches?
♦ For redundant power supplies?
♦ For media converters and AC to DC power adapters for media converters?

Traffic Considerations
Consider specific traffic requirements when planning the control network.
♦ Should certain control stations or workstations be connected to the same switch?
To reduce traffic through the root switches, it may be advantageous to group control
stations or workstations according to department, process, or other criteria that is
important to the site or organization.
♦ Should certain control stations or workstations not be connected to the same switch?
Each control station or workstation from a particular group should be connected to
two separate switches. If one switch were to go offline, these control stations or
workstations can access the network through the redundant switch. Without a
redundant network, none of the workstations from that group would have network
access. Workstations should have two Ethernet ports to access the network.

22
2. Site Planning B0700AZ – Rev V

Network Loading
Understanding the details of the network traffic flow is an important part of planning and
implementing the control network for a Foxboro Evo system. This provides insight on how to
verify that there is sufficient network bandwidth available between network devices.
This is difficult to measure, since available bandwidth is a dynamic quantity where the amount of
traffic that can be transmitted over a link can change given its current traffic conditions and what
applications are running on those devices.
The process of designing industrial networks is a very challenging task due to its inherent
complexity. A load prediction can be achieved by approximating the environment, modeling the
network components and analyzing the interrelations. This process works well for industrial
networks since they tend to be more static and are typically slow to evolve.
The control network steady state load should not exceed a maximum load of 50% of any given
link.
The control network is a full-duplex, point-to-point system. This network does not have a colli-
sion domain. Unlike half-duplex links, full-duplex links do not deteriorate as the network load
increases. All end-devices can transmit at will. However, if the control network is designed with
100 Mb uplinks, communication from these end-devices could cause a bottleneck due to insuffi-
cient available network bandwidth1. Since the control network runs in full-duplex mode, both
transmit and receive channels can run at 100 Mb simultaneously without degradation on the
adjacent channel.
The control network traffic rates are also affected by third-party applications or user applications
that generate high packet rates. Workstation to workstation operations on the control network,
such as copying extremely large files, can also result in a temporary high bandwidth usage up to
50% of the network:
Network loading is represented by the percent of time that the network is in use over a given
period. By definition, individual Ethernet segments can only transmit one packet at a time. For
any given moment, the Ethernet segment is either at 100% loaded (transmitting a packet), or at
0% utilization (idle). The network loading percentage shows the percentage of time the network
is in use over a set period.
When calculating the network loading, you need to know how many bytes of network traffic are
being handled by the network over a set period. This involves totaling the input (or output) byte
counts for a set period, and dividing by the total capacity of the device interface for that period.
To determine the total number of bits received on the interfaces, each of the packet byte rates is
multiplied by 8.
%loading = (dataSent * 8) / (intSpeed * sampleTime) * 100
Where:
dataSent = total number of bytes sent
intSpeed = maximum connection speed
sampleTime = duration of time required for transmissions

1. Flow control and rate limiting are disabled, and full-duplex cables are used, allowing the controllers
transmitted packet to egress though the network without delaying or filtering. However, by doing
this, a packet on a heavily loaded network can cause traffic to slow. When you use the Control Net-
work, the switch acts as a traffic cop controlling the data to maximize the traffic flow. If you disable
flow control, the traffic flows faster but can cause detected issues when traffic loads are high.

23
B0700AZ – Rev V 2. Site Planning

For example, for a system having 6 x 1500 byte sends on 100Mb connection at maximum of 2Mb
(2 * 1,000,000 bps) every 500 milliseconds:
7.2% = (6 * 1500) * 8 / (2,000,000 bps * 0.50secs) * 100

Equipment Considerations
The control network was designed and tested for operation with the Ethernet switches listed in
“Reference Documents” on page xiv. The network may operate with similar, off-the-shelf
equipment, but Foxboro is not responsible for any system malfunctions that may occur if such
equipment is used.
If you use your own network equipment:
♦ You must meet the bandwidth requirements (1 Gb for uplink ports and 100 Mb for
device ports) for the Foxboro Evo equipment you have chosen.
♦ There can be no Layer 3 inter-network devices (for example, routers) between any
Foxboro Evo equipment, with the exception of CNI routers. See Control Network
Interface (CNI) User’s Guide (B0700GE).

Hardware Requirements
While switches with 100 Mb uplink ports are allowed on networks with standard configurations,
Enhanced Network Configurations require the use of 1 Gb uplink ports. However, use 1 Gb
uplink connections to interconnect switches in all configurations, if available.

Switch Utilization in the Standard Configurations

Any switches defined in the table “Foxboro-Supplied Ethernet Switches” in the “Introduction” of
Switch Configurator Application Software Guide for the Foxboro Evo Control Network (B0700CA)
can be used in Standard Configurations.

Switch Utilization in the Enhanced Network Configurations

Refer to the Appendix A table “Qualified Switch Standard/Enhanced Network Configuration
Compatibilities Matrix” in Switch Configurator Application Software Guide for the Foxboro Evo
Control Network (B0700CA) for a list of allowed switch types in Enhanced Network Configura-
tions.
Since the Enhanced Network Configurations deploy Loop Detection Policy algorithm (LDP)
methods to monitor and help protect the network from RSTP instability or Data Loop (storm),
specific switch types must be used in a variety of required locations within the network. Refer to
the Appendix A Qualified Switches for The Control Network Table A-1 to identify which switch
type falls into the categories “Enhanced Network” and “LDP Deployable”.
♦ In a linear topology in an Enhanced Network Configuration, both switches must be
from the “LDP Deployable” category.
♦ A ring topology cannot be supported as an Enhanced Network Configuration.
♦ In a star topology in an Enhanced Network Configuration, both root and backup root
switches must be from the “LDP Deployable” category. All other switches within the
star network can be from the “Enhanced Network” category.
♦ In an inverted tree topology in an Enhanced Network Configuration, all core (root
and distribution) switches within the network must be from the “LDP Deployable”

24
2. Site Planning B0700AZ – Rev V

category. All outer edge switches within the tree network can be any switch series or
type.
♦ The modified inverted tree topology (MITT) in an Enhanced Network Configura-
tion requires that all switches within the network core (root/distribution) are “LDP
Deployable”. All outer edge switches within the tree network can be any switch series
or type. However, the redundant switches (A/B switches) must be deployed on differ-
ent tiers.

Firmware Considerations
When planning which Foxboro-supplied Ethernet switches to use when building the control net-
work for your system, be aware that certain versions of these switch’s firmware and/or hardware
may be incompatible with one another.
Refer to the Appendix A “Qualified Switch Firmware Compatibilities Matrix” in Switch
Configurator Application Software Guide for the Foxboro Evo Control Network (B0700CA) for the
Foxboro Evo qualified and compatible hardware and firmware for each switch.

The Foxboro Evo Control Network Design Rules

When designing the control network, keep the following rules/guidelines in mind.

Standard Configuration Design Rules

These rules apply to the standard design of the control network:
♦ No more than 1920 logical stations where:
♦ Fault-tolerant stations count as one logical station.
♦ Workstations count as one logical station.
♦ Ethernet switches count as one logical station
♦ FCMs are not counted.
♦ No more than 10,000 IP addresses where:
♦ A fault-tolerant FCP280, FCP270, or CNI counts as one address.
♦ A fault-tolerant ZCP270 counts as two addresses.
♦ An ATS station counts as two addresses.
♦ Workstations on the control network count as two addresses prior to I/A Series®
software v8.2; Workstations on the control network with I/A Series software v8.2-
v8.8 or Foxboro Evo Control Core Services v9.0 or later count as one address.
♦ Nodebus workstations count as one address.
♦ Ethernet switches count as one address.
♦ FCMs count as one address.
♦ Up to 500 managed switches are allowed.
♦ Verify that there are no more than seven switches in the path between any two devices
(four (4) network Tiers) in the control network.

25
B0700AZ – Rev V 2. Site Planning

♦ Routers are only allowed in the control network to connect a Control Network Inter-
face (CNI) with a customer-supplied interconnect to another control network. This is
discussed in Control Network Interface (CNI) User’s Guide (B0700GE).
♦ Make Switch-to-Switch connections (uplink ports) using 1 Gb uplink ports to allow
enough bandwidth for network traffic of Foxboro Evo equipment
♦ Only two configured root bridges are allowed in the network.
♦ Horizontal switch interlinks (links between switches of the same tier) are not allowed,
except between the root and backup root switches. (See Figure on page 28).
♦ The control network must have redundant uplink connections between the root and
backup root switches.
♦ The control network supports up to six VLANs, one (1) of which must be reserved for
Foxboro Evo system devices (VLAN 2 “FECN”).
♦ Only one Foxboro Evo system can be supported on the control network. To allow
multiple Foxboro Evo systems to share their control data, refer to Control Network
Interface (CNI) User's Guide (B0700GE).
♦ If VLANs are deployed, all Foxboro Evo control devices shall be attached to VLAN 2
FE ports. VLAN deployment is needed when deploying an Enhanced Network
Configuration
♦ If VLANs are deployed, all switches in the network must have VLAN 2 enabled on
the switch’s uplink ports.
♦ VLANs other than VLAN 1 and 2 shall not utilize protocols other than TCP/IP
and/or UDP/IP.
♦ No VLAN port shall exceed 50% loading.
♦ No end devices with transfer (Tx) and receive (Rx) speeds greater than 1Gb are sup-
ported. The V90/V91 Virtual server utilizes 1Gb ports on virtual switches and is not
considered an end device but are considered networking devices (switches).

NOTE
Reserve one port on each managed Ethernet switch for testing and diagnostic pur-
poses. Do not connect any device to this port.

Non-Foxboro Evo Equipment

These rules apply to non-Foxboro Evo equipment:
♦ Non-Foxboro Evo equipment (for example, routers, hubs, and unmanaged switches)
are not allowed to be connected to the control network.
♦ Do not connect a corporate or plant enterprise network directly to the control net-
work. To communicate from a corporate or plant enterprise network, use an
additional NIC on a Foxboro Evo workstation.

26
2. Site Planning B0700AZ – Rev V

Enhanced Network Configuration Design Rules

When designing the Enhanced Network Configuration, the Standard Network Configuration
rules/guidelines must be followed as well as those below:
♦ Make core switches only LDP-supported switches, as described in the Appendix A
table “Qualified Switch Standard/Enhanced Network Configuration Compatibilities
Matrix” in B0700CA.
♦ When deploying Legacy LDP, the root switch must have the lowest IP address in the
network or at least an address lower than the backup root switch. This is no longer a
requirement when deploying CoS LDP.
♦ Do not use an application on the network which requires IGMP, such as IP video.
♦ Methods for active network monitoring (for example, NetSight Policy Manager) are
not required but are recommended for medium to large networks.

NOTE
The following rules only apply when deploying Legacy LDP on a Enhanced Net-
work Configuration.

♦ Deploy the Circuit Breaker Policy (CBP) at all uplinks ports facing the outer edge
(away from the root), ports that are not and will not be blocked by spanning tree.
♦ Deploy the Beacon Priority Policy (BPP) at all uplink ports facing towards the root.
♦ Use the Backplane Circuit Breaker Policy (BPCB) (used only for E-Series bridge cards
P0973BS) to detect RSTP detected failures on the E-Series second and third genera-
tion blades only (defined in the Appendix table “Qualified Switch Standard/Enhanced
Network Configuration Compatibilities Matrix” in Switch Configurator Application
Software Guide for the Foxboro Evo Control Network). Do not interface any other
switches to the second and third generation blades via uplink or data ports. Blades
with the BPCB policy (E-Series second and third generation blades) should reside at
the outer most edge of the network. A detailed description of BPCB and other policies
can be found in the appendix section “Deploying Loop Detection Policies” in the
Switch Configurator Application Software Guide for the Foxboro Evo Control Network.
♦ All edge switch uplink ports facing the root require the spanning tree admin path cost
to be increased (≥200000), this helps ensure efficient port blocking at the edge.

NOTE
On S-Series chassis switches (S4), the two interlinks between the root and the
backup should be on the same blade (Slot 2 Fabric Module).

27
B0700AZ – Rev V 2. Site Planning

Interlink flows across the network (on the same tier), this is only recommended at the root tier
with Circuit Breaker PBQ and SBQ deployed.

Uplink paths should Backup Root

be gigabit paths
Primary Root

TIER 1

Managed Switches Managed Switches

Interlinks should flow

towards or away
from root, i.e. from
one tier to the
other.

Gigabit Ethernet over Gigabit Ethernet over

Fiber Uplink Ports Fiber Uplink Ports
TIER 2

TIER 3

TIER 4

Control Workstation
Processor

Figure 2-1. Large Network (Enhanced Network Configuration)

28
2. Site Planning B0700AZ – Rev V

NOTE
On S-Series chassis switches (S4), the two interlinks between the root and the
backup should be on the same blade (Slot 2 Fabric Module).

Additional Guidelines For High Availability on The Foxboro Evo

Control Network
The design of each instance of the control network is different, and depends on the needs and
requirements of the individual site. This section provides the information necessary to help
network designers plan the control network that meets the needs of their specific site.
The control network is constructed so that there are redundant links that form physical loops in
the network which are controlled (blocked) by Rapid Spanning Tree Protocol (RSTP), creating a
logical loop-free network. In the event of RSTP instability, deploying LPA provides additional
functionality by isolating switches not responding to BPDU proposal - agreement requests.

NOTE
Loop Protection Algorithm (LPA) functionality is required to be deployed across
both Standard Network Configurations and the Enhanced Network Configura-
tions.

Planning Loop Protection Algorithm (LPA) Configurations

A control network with LPA deployed will isolate switches which fail to participate in the network
spanning tree, and helps prevent network storming. LPA allows communications to continue on
the control network by isolating switches from the network that are not participating in the RSTP
functionality.
Legacy Loop Protection Algorithm (LPA) functionality cannot guarantee sub-second failover.
Generally, failover occurs between one to six seconds. Enhanced Loop Protection Algorithm
(LPA) helps prevent packet flooding during a network storm (RSTP instability), helping to pro-
vide minimal packet loss between devices (when devices have multiple data paths). Utilizing LDP
sub-second failover is no longer needed nor required since network traffic is not interrupted.
Since LPA does not cause the link to drop when it blocks a port, it is recommended to deploy
NetSight to monitor the LPA traps. Refer to Switch Configurator Application Software Guide for the
Foxboro Evo Control Network (B0700CA) for more information.

Spanning Tree Behavior with Enhanced LPA

A spanning tree design must be implemented correctly to provide a loop-free network during
normal operations. When Enhanced Loop Protection Algorithm (LPA) is deployed, improper
configuration can cause “false” triggers of the LPA which can disable active switches.
Verify that all switches within the network are capable and enabled to support Enhanced LPA.
Switches running firmware that does not support Enhanced LPA must be upgraded to the latest
firmware in order to deploy it. Refer to the table “Qualified Firmware for Use in The Control
Network” in the appendix “Qualified Switch Firmware Compatibilities Matrix” in Switch Config-
urator Application Software Guide for the Foxboro Evo Control Network (B0700CA) for the list of
firmware that supports this feature.

29
B0700AZ – Rev V 2. Site Planning

refer to Switch Configurator Application Software Guide for the Foxboro Evo Control Network
B0700CA for details on configuring Enhanced LPA for Legacy LPA and non-LPA switches.

NOTE
Enhanced Loop Protection Algorithm (LPA) functionality can be deployed across
both Standard Network Configurations and the Enhanced Network Configura-
tions.

Planning Enhanced Network Configurations

A control network with CoS LDP (also referred to as the Enhanced Network Configuration) iso-
lates storming switches, and allows communications to continue on the control network. CoS
LDP isolates a loop or storming switch by disabling a port once a maximum of up to 7 Beacon
packets have been received on the ingress port. Failover is deterministic based on the packet rate of
the network storm. LDP causes the link to go down if it blocks a port, resulting in a trap to Sys-
tem Monitor and an indication in SMDH or the System Manager. See Switch Configurator Appli-
cation Software Guide for the Foxboro Evo Control Network (B0700CA) for more information.
In a properly constructed network, the switches on the network are able to communicate with
each other with a high degree of reliability and redundancy. The control network is constructed so
that there are redundant links that form physical loops in the network which are controlled
(Blocked) by Rapid Spanning Tree Protocol (RSTP), creating a logical loop-free network. In the
event instability occurs with this function, the (LDP) loop detection algorithm provides a method
to detect the fault and isolate the device causing the instability.
There are rules that must be followed when connecting switches to form the control network. The
next section explains the dynamics affecting the physical topology and the traffic considerations of
the control network.
Once the general plan for the network configuration has been outlined, the physical design of the
network can be defined. Refer to Switch Configurator Application Software Guide for the Foxboro
Evo Control Network (B0700CA) for the rules concerning network configuration/topology and
the specifications for the network devices (switches, converters, interface modules) and cabling,
and to choose the equipment that is needed to implement the network plan.

NOTE
For a variety of questions to help you define both the Standard and Enhanced
Network Configurations, refer to “Network Considerations” on page 19.

When the physical design has been finalized, make a drawing or map of the network topology and
save it. Update the map whenever a physical change is made to the control network.

Spanning Tree Behavior with Legacy LDP Versus CoS LDP

A Spanning Tree design must be implemented correctly to provide a loop-free network during
normal operations:
♦ There are conditions that can cause LDP to have a false trigger leading to a disabled
port or isolated switch. CoS LDP has been designed to handle these conditions by
preventing a trigger unless more than one packet is detected in a potential loop.

30
2. Site Planning B0700AZ – Rev V

♦ When Legacy LDP is deployed, verify that your edge switches keep their redundant
connections blocked. The path cost typically involves the sum of the path costs, that
is, of the links that are traversed. This cost can be adjusted by altering the default
assigned path costs for individual links. An edge switch may not block its ports in an
expected order, though other switches may do so. Edge switches must have their path
cost administratively increased to get their local ports to block. This keeps the “Bea-
con” packet from being forwarded to a port with the “Circuit Breaker” policy.
Increasing a path cost on a switch port increases its likeliness to block all local ports on
edge devices in a topology for the control network. This path cost is dependent on the
switch interconnections between the switch tiers. The edge switch uplink ports path
cost must be increased to ≥200000.
♦ You no longer a need to adjust the path cost when CoS LDP is deployed.
When Legacy LDP is deployed, ports designated as the “Beacon” ports, must have their path cost
set from the default value of 20000 to a value ≥400000. The admin path cost is automatically
adjusted when utilizing the Switch Configurator Application Software (Rev 1.1.4 or greater) dis-
cussed in Switch Configurator Application Software Guide for the Foxboro Evo Control Network
(B0700CA). There is no longer a need to adjust path cost when CoS LDP is deployed.

Table 2-1. Differences Between Legacy LDP and CoS LDP

Legacy LDP CoS LDP

Legacy Loop Detection Policy (LDP) failover CoS Loop Detection Policy (LDP) port dis-
occurs on the first Beacon packet received on abling of a port occurs once a maximum num-
the ingress port. This can causes false hits. ber of Beacon packets have been received on the
ingress port. Failover is deterministic of the
packet rate of the network storm.
Legacy LDP deploys an ICMP Beacon across CoS LDP deploys an ICMP Beacon across a
the DCS Control Ports VLAN, VLAN 2. LDP Control VLAN, VLAN 2000, by doing
this it removes the ICMP "Beacon" packets off
the DCS Control Network VLAN and allows
for tighter control over the Beacon packet deliv-
ery.
Legacy LDP deploys multiple rules across the CoS LDP deploys only 1 rule across the net-
network "Beacon", "Circuit Breaker", "PBQ" work "Circuit Breaker", Circuit Breaker can be
and "SBQ", which requires careful planning on deployed on all and any port. However, when
how the network is laid out and configured. deploying CoS LDP on the root switches the
root bridging ports (ISL ports between the two
root switches) must be identified as PBQ/SBQ
ports when assigning rules (these ports are typi-
cally identified when deploying LPA).

Refer to Switch Configurator Application Software Guide for the Foxboro Evo Control Network
(B0700CA) for a detailed list of switches that support the LDP enhanced network configuration
feature.

31
B0700AZ – Rev V 2. Site Planning

IGMP “Beacon” Behavior

LDP functions utilize IGMP packets which act as a beacon. The IGMP “Beacon” is enabled only
on the root and backup root switches in the network when deploying LDP. Only the designated
root switch with the lowest IP address sends out a “Beacon” query packet. The Secondary “Bea-
con” Queryer (SBQ) acts as a backup and only sends out a “Beacon” query packet if the root
switch goes offline or a loss of link occurs between the two root switches.
When Legacy LDP is deployed, the root switch must be configured with the lower IP address of
the root and backup root pair in order for LDP to operate properly. The switch with the lowest IP
address and with its IGMP “Beacon” enabled is chosen as the Primary Beacon Queryer (PBQ).
When configuring the network in SysDef, IACC or System Editor, designate the root switch with
the lowest switch IP address of the root/backup root pair.
In the event of a root switch going offline, the SBQ on the backup root takes over. Once the root
switch has been placed back online PBQ from the root sends out an IGMP “Beacon” packet stop-
ping the SBQ on the backup root from transmitting its Beacon packet.

NOTICE
POTENTIAL DATA LOSS

• In the event of a root switch going offline, the LDP Beacon

“PBQ” becomes disabled and the functions of the root switch
move to the backup root switch along with the LDP Beacon
“SBQ”. Once the root switch going offline has been resolved
and the switch has been placed back on the network, the LDP
Beacon “PBQ” becomes enabled, disabling the “SBQ”.
• When Legacy LDP is deployed, the redundant root bridge links
between the root and backup root are viewed by LDP as a loop
within the network, which causes LDP to disable one of the
links (the blocking port). To recover from this rule hit, the root
switch (switch with the lowest IP address) needs to regain root
functions.
• You can help prevent this event if VLAN 2 is deployed on the
network, by moving the root switch host ports to a secure
VLAN. “VLAN 2” (host port moved to VLAN 2 is required for a
Foxboro Evo system), by deploying VLAN 2 may reduce the
chance of false port hits between the two root switches.

Failure to follow these instructions can result in data loss.

The default timing for the IGMP protocol causes one packet to be sent every 125 seconds. In
order to provide a “Beacon” packet that allows a loop to be detected within one second the IGMP
timer is set to one second for LDP. Since IGMP packets are multicast packets they are forwarded
out from the root to the edge switches of the network. In the event of a loop, the packet is for-
warded back towards the root where a port with a circuit breaker policy detects it and disables the
port shutting down the loop.
Normally IGMP packets are used to sustain and prune multicast flows in a network and are used
for IP video. Any application which uses IGMP, such as IP video, cannot be used on an Enhanced
Network control network since it disrupts LDP operation.

32
2. Site Planning B0700AZ – Rev V

The Foxboro Evo Control Network Design

Once the general plan for the control network has been outlined, the physical design of the
network can be defined. The next two sections describe the rules concerning network
configuration/topology and list the specifications for the network devices (switches, converters,
interface modules) and cabling. Use these sections to choose the equipment that is needed to
implement the plan that was derived from the answers to the questions at the beginning of this
chapter. When the physical design has been finalized, make a drawing or map of the network
topology and save it. Update the map whenever a physical change is made to the control network.

33
B0700AZ – Rev V 2. Site Planning

I/O Network Design Rules

These rules apply to the I/O network design for ZCP270s on the control network:
♦ Only Foxboro-qualified switches supported for the control network are permitted on
the I/O network.
♦ The I/O network does not support redundant ISL links between switches. Only single
links between switches are allowed.
♦ Routers are not allowed in the I/O network.
♦ Make Switch-to-Switch connections (ISL uplink ports) using 1 Gb uplink ports to
allow enough bandwidth for network traffic of the Foxboro Evo equipment.
100 Mbps uplinks are not supported on the I/O network.
♦ Configured root bridges are allowed in the I/O network, but not required.
♦ Do not interlink the “A” Fieldbus switches to the “B” Fieldbus switches (see
Figure 1-2 on page 9). The two Fieldbuses must maintain separation.
♦ Only the linear topology is supported on the I/O network, with no more than seven
switches in series. Use the fewest number of switches with which you can configure
the I/O network.
♦ The same number of switches must be maintained on both the “A” side and the “B”
side of the I/O network.

NOTE
A dedicated I/O network switch can be configured with the Switch Configurator
Application Software (SCAS), as discussed in Switch Configurator Application Soft-
ware Guide for the Foxboro Evo Control Network (B0700CA).

NOTE
Reserve one port on each managed Ethernet switch for testing and diagnostic
purposes. Do not connect any device to this port.

The Foxboro Evo Control Network Topologies

A key feature of the control network is that all data paths within the network are redundant; this
aids in communications for the device port monitor, device peer-to-peer communications, and
overall network performance. This is accomplished by using a control network design in which
each Foxboro Evo station is ideally connected to two different Ethernet switches. Each of the
Ethernet switches is then connected to two other Ethernet switches. This design provides
redundant data paths so that a single switch does not cause the network to become unstable.
Enhanced Network Configurations provide the loop detection algorithm known as LDP to help
protect against RSTP instability and/or data loop (storm) instability. When deployed on an
Enhanced Network Configuration, LDP allows for the isolation of a switch or port (depending
on the type of detected failure) during a network storm when caused by a spanning tree instability
or a data looping. This function prunes the loops, maintaining network communications between
devices during a network storm.

34
2. Site Planning B0700AZ – Rev V

NOTE
If the network is constructed with less than two connections between devices, data
traffic could be disrupted if any single device goes offline.

The control network can be constructed using two network configuration/topology methods.
The first is the Standard Configuration as described in this section under “Standard Configura-
tions” below and the second is the Enhanced Network Configuration as described in “Enhanced
Network Configurations” on page 47. The topology chosen depends largely on the size, complex-
ity, site requirements, and network specifications of the control network. The next paragraphs
provide some guidelines for choosing a network configuration (topology).

NOTE
The subsequent graphics of switches and media converters are intended as generic
illustrations of networking concepts and do not necessarily reflect the currently
offered products.

Standard Configurations
There are five basic standard configurations that are supported by the control network. As well,
the variations of these topologies listed below can be made as long as all design rules are met. Be
aware that some restrictions to these variations listed below may be warranted.
The basic standard configurations and their approved variations are as follows:
♦ Linear
♦ Ring
♦ Star (Variation: Double Star)
♦ Inverted tree
♦ Modified inverted tree (Variation: Inverted Stepped Tier Tree)

35
B0700AZ – Rev V 2. Site Planning

Standard Small Networks (Linear Topology)

A small network, consisting of two switches, could be configured as in Figure 2-2.

Gigabit Ethernet over

Fiber Uplink Ports

P92

Fiber Managed
Switches
Network Adapters

FCP280
Figure 2-2. Small Network (Standard Configuration)

In this example, two fiber optic Ethernet switches are used and the workstation and controller
have a 100 Mb connection to each of the switches. The connections between the switches can use
the switch’s high speed uplink ports (1 Gb).

NOTE
Two connections between switches are required for proper redundancy.

Larger Chassis switches can be used instead of the non-Chassis Fiber switches. Larger Chassis
switches allow hundreds of workstations, controllers and FCMs to be connected to the control
network. This provides a small network but quite a large control system. Multiple FCP280s,
FCP270s, CNIs, FCM100s, ZCP270s, ATS modules, and workstations/servers can be connected
to a redundant switch.

36
2. Site Planning B0700AZ – Rev V

Standard Medium Networks (Ring Topology)

A medium-sized network of three to seven switches can be configured as a ring. Figure 2-3 shows
an example of a ring topology containing six switches. In this example, all the switches are fiber
optic and each switch is connected to the two switches adjacent to it. If one of the switches
becomes nonfunctional, the ring is broken but RSTP (802.1w) reroutes data around the break
and the network remains operable. Typically a failover time of less than 1 second is achievable
using switches qualified and supplied by Foxboro and configured in accordance with Foxboro Evo
documentation.

NOTE
The Foxboro Evo system imposes a seven switch limit on the length of any data
path. This means that there can be no more than seven switches between any two
devices in the network.

Primary Root

Fiber Managed
Backup Root Switches

Gigabit Ethernet over

Fiber Uplink Ports

Figure 2-3. Medium Network (Ring) (Standard Configuration)

Star Topology
A medium and large-size network can also be configured in a star topology as shown in
Figure 2-4. The star topology is the preferred topology for control systems. In star topology, two
switches make up the backbone of the network and should be configured as the root and backup
root switches. The other switches “edge switches” in the network are connected to both root
switches. If desired, other devices (workstations or controllers) can be connected directly to the
root switches.
A Star topology has a limitation of the total number of edge switches and/or devices based on the
root switch's available ISL ports. This limit is derived from the maximum number of Gb ports on
the switch.
Two ports are used for interconnection between the primary and backup root.

37
B0700AZ – Rev V 2. Site Planning

Expandable
Chassis Switch

Fiber Managed
Switches

Primary
Root

Fiber Managed
Switches
Backup
Root

Gigabit Ethernet over

Fiber Uplink Ports
Figure 2-4. Medium or Large Network (Star) (Standard Configuration)

The Double Star Configuration Figure 2-5 (a variation of the Star Configuration, shown in
Figure 2-4) allows the user to benefit from the Star Configuration advantages while allowing the
user to deploy a much larger sized network. Observe bandwidth considerations between the Star
topology switches, to minimize bandwidth consumption. The majority of peer-to-peer end device
communications should reside local to the individual Star topologies.

NOTE
This type of topology as shown in Figures 2-5 and 2-7 is ideal when deploying older
switches that do not support Enhanced LPA. To utilize Enhanced LPA on this net-
work topology all root switches and switches attached to the root (Tier 1 and 2)
require the Enhance LPA functionality, whereas the other edge can deploy Legacy
LPA.

38
 2. Site Planning B0700AZ – Rev V

Expandable Chassis Switches

S-Series S-Series
Primary Root Secondary Root

Gigabit Ethernet over TIER 1

Fiber Uplink Ports

A-, I- or V-Series Switches A-, I- or V-Series Switches

TIER 2
X-Series Switches

X-Series Switches X-Series Switches

TIER 3
X-Series Switches
Figure 2-5. Medium or Large Network (Double Star) (Standard Configuration)

Standard Large Networks (Inverted Tree Topology)

Design large networks to use an inverted tree topology or a modified inverted tree topology.
For the inverted tree topology as shown in Figure 2-6, Ethernet switches are arranged in tiers,
with primary and backup root switches in the top tier. Each switch is connected to two different
switches in the tier above it and end stations may be connected to any of the switches. A large net-
work containing 12 switches in four tiers is illustrated in Figure 2-6.

39
B0700AZ – Rev V 2. Site Planning

NOTE
There is a limit of four tiers on the Inverted Tree topology, as shown in Figure 2-6.
This is to help prevent the path between any two devices from containing more
than seven switches. There can be no more than three tiers of switches (including
the root) in order to comply with the Foxboro Evo system requirements of the Mod-
ified Inverted Tree topology as shown in Figure 2-8.

Primary Root Backup Root

Uplink paths should
be gigabit paths Note: Primary and Backup
Root Switches have two
TIER 1 connections.

Managed Switches Managed Switches

TIER 2
Gigabit Ethernet over Gigabit Ethernet over
Fiber Uplink Ports Fiber Uplink Ports

TIER 3

TIER 4

Control Workstation
Processor

NOTE: In this topology, the FCP280 and its host workstation can only be attached to the S-Series
switches with fiber optic cable. No copper 100Mb end devices are allowed.
Figure 2-6. Large Network - All Blades (Standard Configuration)

40
 2. Site Planning B0700AZ – Rev V

The Inverted tree topology, shown in Figure 2-7, is an example which demonstrates that users can
utilize a non-symmetrical tree topology.
In this topology when using copper uplinks, switches connected between the tiers cannot be sepa-
rated by more than 100 meters due to the distance restrictions on the copper uplinks. In the
example in Figure 2-7, the uplinks between tiers 2 and 3 are not required to be interfaced to the
switch directly above each. However, verify that all switches in the network are interfaced with
two (2) uplinks to the tier above them.

Expandable Chassis Switches

S-Series S-Series
Primary Root Secondary Root
Gigabit Ethernet over
Fiber Uplink Ports TIER 1

X-Series X-Series Switches

Switches
TIER 2
X-Series
Switches

TIER 3

X-Series X-Series Switches

Switches

TIER 4
X-Series Switches

Figure 2-7. Large Network - Inverted Tree

(Standard Configuration)

Modified Inverted Tree Topology (MITT)

The modified inverted tree topology is similar to the inverted tree topology but allows for root
switch redundancy. In this topology, the root/backup root switches have redundancy via the core
switches in the event both root switches were to becomes nonfunctional. In the event both root
switches become nonfunctional, one of the tier 2 core switches will take over as the root switch

41
B0700AZ – Rev V 2. Site Planning

allowing communications between all devices. It is required that a priority be set designating a
second root and backup root in this type of topology. Redundant data paths allow the network to
continue to operate if any one component becomes nonfunctional. This allows end devices to be
interfaced at different tiers within the network, so detected failures within the network have min-
imum impact on device-to-device communications.
There can be no more than three tiers of switches (including the root) in order to comply with the
Foxboro Evo system requirements of the Modified Inverted Tree.

NOTE
Figure 2-8 shows the S4 chassis (P0973KD) as the core switch that can also be
deployed with SSA chassis (P0973LN) at the core if LDP needs to be deployed. If
LDP is not needed, the MITT can be deployed with any switch series supporting
multiple (more than 4) ISL (1Gb) ports when deployed as a core switch. All switch
types can be deployed as edge switches.

Core Switches Core Switches

Primary Root Backup Root

TIER 1

Gigabit Ethernet over

Fiber Uplink Ports
Gigabit Ethernet over
Fiber Uplink Ports

TIER 2

Core Switches

TIER 3

Control
Processor
Figure 2-8. Large Network - Blades and Low-Cost Switches
(Modified Inverted Tree)

42
2. Site Planning B0700AZ – Rev V

Physical Layout of an Inverted Tree Topology

When designing the physical layout of a Inverted Tree Topology, these guidelines apply:
♦ Make Switch-to-Switch connections (uplink ports) using 1 Gb uplink ports to allow
enough bandwidth for network traffic of Foxboro Evo equipment
♦ Have a primary and backup root switch on the network
♦ Have no more than four tiers of switches, including the primary and backup root
switches
♦ Have no horizontal connections between switches on the same tier except the root and
backup.
♦ This minimizes the number of switch interconnections in order to facilitate faster
network re-spanning of the network tree.
♦ This also reduces the likelihood of a loop occurring.
♦ Connect each switch to two different switches in the tier above it
♦ Make two connections between the primary root and the backup root.
Step 1: Determine Physical Structure
In the example that follows, the primary and backup root switches are in the top tier, and the
remaining switches are divided between the other three tiers. To determine the number of
switches in each of the three tiers, divide the number of switches by three. In this example, the
result is three (with one left over), which suggests that there should be approximately three
switches per tier. Keeping in mind that there should be an even number of switches in each tier,
switches are added or subtracted until this guideline is met. In this case we arrive at a solution that
has two switches in the second tier, and four switches in each of the remaining two tiers.

Primary Backup
Root Switches Switch Switch

2nd Tier Switch Switch

3rd Tier Switch Switch Switch Switch

4th Tier Switch Switch Switch Switch

Figure 2-9. The Foxboro Evo Control Network Tiers

43
B0700AZ – Rev V 2. Site Planning

Step 2: Connect Root Switches

Two connections are made between the primary and backup root switches. Make these connec-
tions from gigabit uplink port to gigabit uplink port. Connecting a gigabit uplink port to a giga-
bit uplink port increases the speed of the response.

Primary Backup
Root Switches Switch Switch

2nd Tier Switch Switch

3rd Tier Switch Switch Switch Switch

4th Tier Switch Switch Switch Switch

Figure 2-10. Root Switches Connected

44
2. Site Planning B0700AZ – Rev V

Step 3: Connect Second Tier

Once the primary and backup root switches have been connected, make separate connections
from each second tier switch to both the primary and backup root switches using gigabit connec-
tions.

Primary Backup
Root Switches Switch Switch

2nd Tier Switch Switch

3rd Tier Switch Switch Switch Switch

4th Tier Switch Switch Switch Switch

Figure 2-11. Second Tier Connections

45
B0700AZ – Rev V 2. Site Planning

Step 4: Connect Third Tier

Each switch on the third tier should have separate connections to two different switches in the tier
above it. In this case there are only two switches in the tier above, so a connection is made to each
of them.

Primary Backup
Root Switches Switch Switch

2nd Tier Switch Switch

3rd Tier Switch Switch Switch Switch

4th Tier Switch Switch Switch Switch

Figure 2-12. Third Tier Connections

Step 5: Connect Fourth Tier

The final step is to connect each switch in the fourth tier to two different switches in the tier
above it. Connections may be made to any two switches in the tier, but consider keeping a man-
ageable traffic load on each switch.

Primary Backup
Root Switches Switch Switch

2nd Tier Switch Switch

3rd Tier Switch Switch Switch Switch

4th Tier Switch Switch Switch Switch

Figure 2-13. Fourth Tier Connections

46
2. Site Planning B0700AZ – Rev V

Step 6: Label the Switches

Label switches and cables to aid in organizing the network connections. The strategy illustrated
here is one method. This example uses the ‘A’ and ‘B’ labels as an aid in migrating from two sepa-
rate nodebus networks to the control network. Numeric superscripts are added to designate the
tier and the switch number within the tier. Any labeling strategy which helps to keep the network
connections organized may be used.

Primary Backup
A11 B11
Root Switches Switch Switch

2nd Tier Switch A21 Switch B21

Switch A31 Switch B31 Switch A32 Switch B32

3rd Tier

4th Tier Switch A41 Switch B41 Switch A42 Switch B42

Figure 2-14. Labeling the Switches

Enhanced Network Configurations

There are four basic Enhanced Network Configurations that are supported by the control net-
work. These are:
♦ Linear
♦ Star (Variation: Double Star)
♦ Inverted tree
♦ Modified inverted tree
The next diagrams provide examples of the different topologies deploying the loop detection algo-
rithm (LDP) as well as recommendations on where they might be used. All Enhanced Network
Configurations require specific switch models as the root or backup root. The Inverted Tree and
modified inverted tree requires all switches except the outer edge switches to have LDP.
Refer to the “LDP Deployable” switches in the Appendix A table “Qualified Switch
Standard/Enhanced Network Configuration Compatibilities Matrix” in Switch Configurator
Application Software Guide for the Foxboro Evo Control Network(B0700CA) for the applicable
switch models.

47
B0700AZ – Rev V 2. Site Planning

“Linear” Networks (Enhanced Network)

A small network, consisting of two switches, could be configured as shown in Figure 2-15.

Gigabit Ethernet over

Fiber Uplink Ports

P92

DFE Platinum
Switches
Network Adapters

FCP280
Figure 2-15. Small Network (Enhanced Network Configuration)

NOTE
Two connections between switches are required for proper redundancy.

Larger Chassis switches can be used instead of the non-Chassis Fiber switches. Larger Chassis
switches allow hundreds of workstations, controllers and FCMs to be connected to the control
network. This provides a small network but quite a large control system. Multiple FCP280,
FCP270s, CNIs, FCM100s, ZCP270s, ATS modules, and workstations can be connected to a
redundant switch.

48
2. Site Planning B0700AZ – Rev V

Star Topology (Enhanced Network)

The star topology is the preferred topology for all networks. It is the easiest to maintain, expand,
and deploy. In a star topology, the switches at the outside edge of the network have connections to
each of the two root switches. The two root switches are connected to each other and the edge
switches. Redundant data paths (Root Bridge Ports) allow the network to continue to operate if
any one path is nonfunctional.
Figure 2-16 illustrates a star network in the Enhanced Network Configuration. In an Enhanced
Network star topology, the total number of edge switches is determined by the total number of
available 1Gb uplinks (ISL) ports, minus to two required root bridge ports. In this configuration,
if an edge switch spanning tree protocol becomes unstable, LDP removes the loop that was cre-
ated when the spanning tree does not block the alternate port. In the event the switch becomes
nonfunctional in a manner that causes a network flood, LDP isolates the nonfunctional switch
from the network, allowing its redundant switch to take over. An inverted tree topology or modi-
fied inverted tree topology can be considered if there is a larger number of edge switches required.

Figure 2-16. Star Topology (Enhanced Network Configuration)

49
 B0700AZ – Rev V 2. Site Planning

The double star topology allows the user to benefit from the star topology advantages while allow-
ing the user to deploy a much larger sized network.
Observe bandwidth considerations between the star topology switches. To minimize bandwidth
consumption, verify that the majority of peer-to-peer end device communications reside local to
the individual star topologies.

Expandable Chassis Switches

S-Series S-Series
Primary Root Secondary Root
Gigabit Ethernet over
Fiber Uplink Ports
TIER 1

A-, I- or V-Series Switches A-, I- or V-Series Switches

S-Series S-Series TIER 2

Chassis Chassis
Switch Switch

X-Series Switches X-Series Switches

TIER 3
X-Series Switches

Figure 2-17. Double Star Topology (Enhanced Network Configuration)

50
2. Site Planning B0700AZ – Rev V

Inverted Tree Topology (Enhanced Network)

The inverted tree topology is suited for very large networks with specific physical constraints. In
this topology the switches are arranged in tiers, with the root switches in the top tier and up to
three tiers below them (maximum of four tiers). The two root switches are connected to each
other and the other switches each have a connection to two of the switches in the tiers above and
below them. Redundant data paths allow the network to continue to operate if any one data link
becomes nonfunctional. The deployment of the loop detection algorithm allows for redundant
network condition monitoring by RSTP and LDP.

NOTE
When utilizing an Inverted Tree Topology in the Enhanced Network Configura-
tion, verify that all switches within the network core (root / distribution) are switch
types that support the loop detection algorithm.

An inverted tree network topology is illustrated in Figure 2-18.

There can be no more than four tiers of switches (including the root) in order to comply with the
RSTP requirement, limiting the number of switches between devices to seven.

NOTE
The Inverted Tree variation example of this topology is not shown as a Enhanced
Network Configuration. However, this configuration can be utilized by heeding
this rule:

All switches in the network must be interfaced with two (2) uplinks to the tier
above it, all uplinks attached to a tier above it must be attached to a switch that is
“LDP deployable” and if a switch is attached to a tier below it, it too must be “LDP
deployable”.

Refer to the “LDP Deployable” switches in the Appendix table “Qualified Switch
Standard/Enhanced Network Configuration Compatibilities Matrix” in Switch Con-
figurator Application Software Guide for the Foxboro Evo Control Network (B0700CA)
for the applicable switch models.

51
B0700AZ – Rev V 2. Site Planning

Primary Root Backup Root

TIER 1
DFE Platinum DFE Platinum
Switches Switches

TIER 2
Gigabit Ethernet over Gigabit Ethernet over
Fiber Uplink Ports Fiber Uplink Ports

TIER 3

TIER 4

Control Workstation
Processor

NOTE: In this topology, the FCP280 and its host workstation can only be attached to the S-Series
switches with fiber optic cable. No 100Mb copper devices are allowed.
Figure 2-18. Inverted Tree Topology (Enhanced Network Configuration)

52
2. Site Planning B0700AZ – Rev V

Modified Inverted Tree Topology (Enhanced Network)

The modified inverted tree topology is similar to the inverted tree topology but allows for root
switch redundancy. In this topology, the root/backup root switches have redundancy through the
core switches in the event both root switches were to become nonfunctional. In the event both
root switches becomes nonfunctional, the (by configuration) designated core switch assumes the
root functionality, maintaining the network spanning tree topology communications intact.
Redundant data paths allow the network to continue to operate if any one data link becomes non-
functional. This allows end devices to be interfaced at different tiers within the network, so link
loss between switches or nonfunctional switches within the network has minimum impact on
device-to-device communications.
A modified inverted tree network topology is illustrated in Figure 2-19.
There can be no more than three tiers of switches (including the root) in order to comply with the
Foxboro Evo system requirements of the Modified Inverted Tree.

NOTE
Figure 2-19 shows S4 chassis (P0973KD) as the core switch, but it can also be
deployed with SSA chassis (P0973LN) at the core when LDP is deployed
(Enhanced Network Configuration).

53
B0700AZ – Rev V 2. Site Planning

Core Switches Core Switches

Primary Root Backup Root

TIER 1

Gigabit Ethernet over

Fiber Uplink Ports
Gigabit Ethernet over
Fiber Uplink Ports

TIER 2

Core Switches

TIER 3

Control
Processor
Figure 2-19. Modified Inverted Tree Topology (Enhanced Network Configuration)

54
2. Site Planning B0700AZ – Rev V

I/O Network Topology Configurations

Only linear topologies are supported for use in a dedicated I/O network.

The Linear I/O Network

The linear I/O network can consist of a single A bus switch and a single B bus switch (two
switches in total) or up to seven switches interlinked together using 1Gb (ISL) uplinks for each
bus. Only use additional switches when the total FCM and ZCP port count exceeds the switch
port count, or when the geographical conditions dictate the requirement for more than one
switch. When using Single Mode Fiber ISLs, the distance between two switches can be up to, but
not exceed, 80 km. When using Multi-Mode Fiber ISLs, the distance can be up to 2 km. No
crossover ISL links between the “A” and “B” buses are supported on the linear I/O network. Refer
to Figure 1-2 on page 9.

Switch and Fiber Cable Budget and Loss

Fiber Cable Budget and Loss
The typical power budget for 100FX system of the control network with 62.5/125 m fiber is 11.0
db and worst case (includes aging) is 10.0 db.
Table 2-2 lists some typical and worst case power losses for fiber optic cable, splitter/combiners,
and patch cords.

Table 2-2. Fiber Cable Power Losses

Link Element Value Comments

Splitter/Combiner 4.5 db
MT-RJ Patch Cord 0.5 db 0.75 db worst case
LC, SC, and other 0.15 db 0.5 db worst case
similar patch cords
Singlemode fiber 0.5 db/km at 1300 nm wavelength
cable (SMF) 0.275 db at 1550 nm wavelength
Multimode fiber cable 1.0 db/km at 1300 nm wavelength
(MMF) 3.5 db/km at 850 nm wavelength
Splice loss 0.25 db Mechanical splice
50/125 μM mating 5.25 db -5.0 dB mating loss and a -0.25 dB for
62.5/125 μM loss mechanical splice
Aging reserve 1.0 db 62.5/125 micron cable
Patch Panel loss 2.0 db average

Fiber Optic Budgets

Refer to the documentation included with your Foxboro qualified Ethernet switches for details of
their fiber optic budgets.

55
B0700AZ – Rev V 2. Site Planning

Fiber Budgeting Between Foxboro Evo Devices and Switch Fiber Optic
Connections
The custom fiber optic transceiver used by Foxboro Evo and I/A Series Control Processors (CPs),
Control Network Interfaces (CNIs), Fieldbus Communications Modules (FCMs), and Address
Translation Stations (ATSs) overdrives some vendor versions of the standard 100Base-FX trans-
ceivers. In particular, the station or device may not establish a link, or may be unable to re-estab-
lish a link once the link is lost. The most common indication of this issue is higher than normal
CRC error counts when connected to switch ports with 100Base-FX, even though the vendor’s
transceivers are within the 802.3u 100Base-FX specification.

NOTE
It is normal to see one CRC error count for every CP hot re-marry operation.

Normally, FCP270s, ZCP270s, and FCM100Ets are used with splitter/combiners that reduce the
optical power sufficiently so that this issue does not occur. However, the ATSs, FCM100Es, single
FCP270s, single ZCP270s, single FCM100Ets, and fiber optic network adapter (RH924WA) Rev
A-C which is used by FCP280s and CNIs may experience this problem if the fiber optic cable run
is short and there is not enough loss in the path to reduce the optical power 6.0 dB at 850nm. (for
example, a non-redundant “simplex/single” station may have this issue as well.)
The upgrade kit DG100AF provides LC fiber attenuators that can be inserted into the fiber optic
transceivers for each affected CP, CNI, FCM, or ATS. They provide some attenuation to the
amplitude of the signals to the switches on the control network.

Table 2-3. Kit DG100AF

Quantity Part No. Description

2 P0973LR 0db LC Fiber Attenuator
2 P0973LS 6db LC Fiber Attenuator
1 SI0-00618 Installation instructions

One upgrade kit is required for the following:

♦ Single FCP270
♦ Single FCM100Et
♦ Redundant pair of fiber optic network adapters (RH924WA) for FCP280 or CNI
modules
♦ Redundant pair of FCM100E modules
Two upgrade kits are required for the following:
♦ Single ZCP270
♦ Redundant pair of ATS modules
This section describes where to insert the attenuators in the fiber optic transceiver for each CP,
CNI, FCM, or ATS.

56
2. Site Planning B0700AZ – Rev V

P0973LR LC Fiber Attenuator P0973LS LC Fiber Attenuator

Figure 2-20. P0973LR and P0973LS LC Fiber Attenuators

For each fiber optic transceiver on the Foxboro Evo station (CP, CNI, FCM, or ATS) that requires
these attenuators, proceed as follows:
1. Before installing attenuators, check System Manager or SMDH to verify that commu-
nications over both cables “A” and “B” on the Foxboro Evo station are healthy and
without errors. Also, alert any required personnel that the Foxboro Evo station may
lose fiber optic communications.
Add the attenuators to one cable at a time (for example, cable “B” first and then cable
“A”) to enable this installation process to be performed while the Foxboro Evo station
is running online to help prevent communication disruption. If communications are
disrupted for some reason, they are restored automatically when the cables are plugged
in again.
2. For the fiber optic transceiver for cable “B” on your Foxboro Evo station, perform
these steps:
a. Unplug the LC fiber optic cable from the fiber optic transceiver. Remember which
is receive (Rx) and which is transmit (Tx).
b. Insert the 0db LC fiber attenuator (P0973LR) into the receive (Rx) port of the
fiber optic transceiver, as shown in Figure 2-21. This port is marked on the
FCP270 and FCM100E/Et. Figure 2-22 shows where this port is on the ZCP270,
ATS, or fiber optic network adapter (RH924WA).
c. Insert the 6db LC fiber attenuator (P0973LS) into the transmit (Tx) port of the
fiber optic transceiver, as shown in Figure 2-21. This port is marked on the
FCP270 and FCM100E/Et. Figure 2-22 shows where this port is on the ZCP270,
ATS, or fiber optic network adapter (RH924WA).
d. Plug the LC fiber optic cables into the appropriate LC fiber attenuators. The Fox-
boro Evo station restores communications over this link.
e. Verify that communications have recovered for this link in System Manager or
SMDH.

57
B0700AZ – Rev V 2. Site Planning

P0973LS LC P0973LR LC P0973LS LC P0973LR LC

Fiber Attenuator Fiber Attenuator Fiber Attenuator Fiber Attenuator

Figure 2-21. LC Fiber Attenuators in FCP270’s Fiber Optic Transceivers

FCP280 or CNI Rx/Tx Connections ZCP270 Rx/Tx Connections

Rx Tx
FCP280 Fiber

A
Adapter Modules
in FCP280
Baseplate

Rx Tx
B
Tx Rx

Rx Tx
A

Rx Tx
Cable “A” Cable “B”
B

The FCP280/CNI has a separate fiber adapter

module to connect to the Foxboro Evo Control
Network. Its Rx/Tx connections are as ATS Rx/Tx Connections
shown above.
Rx Tx
A

Rx Tx
B

Figure 2-22. Receive (Rx) and Transmit (Tx) Ports for FCP280, ZCP270, and ATS

58
2. Site Planning B0700AZ – Rev V

3. Repeat the previous step for the fiber optic transceiver for cable “A” on your CP, CNI,
FCM, or ATS.
4. Repeat for any other fiber optic transceivers which need these attenuators.
The procedure is complete.

The Foxboro Evo Control Network Cabling

The following sections provide the specifications and transmission distance capabilities for the
fiber optic, and twisted-pair cabling used in the control network.

Twisted-Pair Cabling
Category 5 (CAT5), shielded twisted-pair (STP) copper cable is used in the control network for
connecting switches to RJ-45 ports on other devices. CAT5 cable can also be used, with the
appropriate uplink module, to connect copper switch ports to other copper switch ports or media
converters.
Transmission distances for CAT5 copper cable are given in Table 2-4.

Table 2-4. CAT5 Cable - Maximum Transmission Distance

Application Transmission Protocol Max. Distance

Media converter to RJ-45 port, 100Base-TX and 100 m (328 ft) for all
switch to switch, port to port 1000Base-T applications

Table 2-5 lists the prefabricated CAT5 STP cables with RJ-45 connectors that are offered by Fox-
boro.

Table 2-5. Prefabricated CAT5 STP Cables with RJ-45 Connectors

Connector
CAT5 Cable Length Type
P0972UB 1 m (3.3 ft) RJ-45
P0971XK 3 m (10 ft) RJ-45
P0971XL 15 m (50 ft) RJ-45
P0972MR 30 m (100 ft) RJ-45
P0971XM 50 m (165 ft) RJ-45
P0971XN 100 m (330 ft) RJ-45

NOTE
Plenum grade jackets are supplied on cables over three meters in length that are
offered by Foxboro. This applies to both fiber optic and CAT5 copper cables.

Null Hub
A null hub is a very short cable that has a male RJ-45 connector on one end and a female RJ-45
connector on the other. The transmit and receive wires are reversed, so when it is connected to the

59
B0700AZ – Rev V 2. Site Planning

end of a straight-through cable, the resulting cable system acts as a crossover cable. The null hub is
used to connect switches that do not have an MDI crossover port or an auto MDI/MDI-X port.
Table 2-6. Null Hub

Null Hub Part Number Length

P0971PK 0.3 m (1 ft)

Switch and Converter Fiber Optic Cabling

Two types of fiber optic cable can be used to connect devices in the control network: multimode
fiber optic cable and single mode fiber optic cable. Each cable type is used in different applica-
tions and the devices that are connected must support the type of cable being used. The next sec-
tions give the supported uses and maximum transmission distances for each type of fiber optic
cable. Cables with different characteristics can be used, but maximum transmission distance may
be reduced. Cable specifications, such as flexibility, rodent protection, fire retardant, and durabil-
ity, depend on the application. Check with your cable installer/vendor for a list of application spe-
cific cable characteristics.

Multimode Fiber Optic Cabling

Multimode fiber optic cable is used to connect stations to switches, media converters to other
devices, and, with the appropriate uplink module, Ethernet switches to other Ethernet switches.
Foxboro recommends that the selected multimode fiber optic cabling have these characteristics:
♦ 62.5 micron core/125 micron cladding
♦ Maximum allowable signal loss = 1 dB/km at a wavelength of 1300 nm
♦ Maximum allowable signal loss = 3.5 dB/km at a wavelength of 850 nm.
Multimode fiber cables offered by Foxboro that meet the recommended specifications are given in
Table 2-7, Table 2-8, and Table 2-9. Refer to the diagrams in the documentation included with
your Foxboro-qualified Ethernet switches for detailed information on cabling.

Table 2-7. Multimode Fiber Cables with LC Connectors

Minimum
Connector Bend
Cable Length Type Radius
P0972UN 0.5 m (1.5 ft) (gray) LC
P0972VG 0.5 m (1.5 ft) (orange) LC
P0972UJ 1 m (3 ft) LC
P0972TN 3 m (9.8 ft) LC 2 inches
P0972TP 15 m (50 ft) LC
P0972TQ 50 m (165 ft) LC
P0972WX (50 micron/mode 3 m (10 ft) LC
conditioning cable)

60
2. Site Planning B0700AZ – Rev V

Table 2-8. Multimode Fiber Cables with MT-RJ to MT-RJ Connectors

Minimum
Connector Bend
Cable Length Type Radius
P0972KV 3 m (9.8 ft) MT-RJ
P0972KW 15 m (50 ft) MT-RJ 2 inches
P0972KX 50 m (165 ft) MT-RJ

Table 2-9. Multimode Fiber Cable with LC and SC Connectors

Cable Length Connector Type

P0972WW 3 m (9.8 ft) Two ceramic-type LC connectors on one
end, with SC connectors on the other end

Table 2-10. Multi-mode Fiber Optic Cable - Maximum Transmission

Application Transmission Protocol Max. Distance
Switch to Switch 1000Base-X 2Km (1.24mi)
MMF cable is supplied by the customer

Single Mode Fiber Optic Cabling

Equip each switch with an appropriate uplink module in order to use single mode fiber optic
cable. Foxboro recommends that the selected single mode fiber optic cabling have these character-
istics:
♦8-10 micron core/125 micron cladding
♦ Typical allowable signal loss = 0.5 dB/km at a wavelength of 1300 nm or 0.275 dB at
a wavelength of 1550 nm.
Transmission distances for single mode fiber optic cable are given in Table 2-11.

Table 2-11. Single Mode Fiber Optic Cable - Maximum Transmission

Application Transmission Protocol Max. Distance

Switch to Switch 1000Base-X 80K (49.6 miles)
SMF cable is supplied by the customer

Foxboro does offer single mode fiber optic cables for use with patch panels. The control network
uses cables with LC connectors which have a pair of fibers which crossover within the cable (TX-
to-RX). When patch panels are used on site, if they are constructed using LC connectors, consider
the number of panels in series between end devices which need to be built. For instance, if a cable
run is terminated with two patch panels and also connects to end devices, and the patch panel was
constructed so that the cable is straight-through, then using two crossover cables (one at each end)
does not work.

61
B0700AZ – Rev V 2. Site Planning

Table 2-12. Single Mode Fiber Optic Jumper Cables

Description Length Part Number

Single Mode Fiber (SMF) fiber optic patch cable w/ LC and 3 m (9.8 ft) P0973EW
SC connectors. Cable to be configured as a null modem (i.e.,
input/output crossed)
Single Mode Fiber (SMF) fiber optic patch cable w/ LC and 3 m (9.8 ft) RH973EX
ST connectors. (supersedes
P0973EX)
Single Mode Fiber (SMF) fiber optic patch cable w/ LC and 15 m (50 ft) RH973FY
ST connectors. (supersedes
P0973FY)
Single Mode Fiber (SMF) fiber optic patch cable w/ LC and 50 m (165 ft) RH973FZ
ST connectors. (supersedes
P0973FZ)
Single Mode Fiber (SMF) fiber optic patch cable w/ LC - LC 3 m (9.8 ft) RH973FV
connectors. (supersedes
P0973FV)
Single Mode Fiber (SMF) fiber optic patch cable w/ LC - LC 15 m (50 ft) RH973FW
connectors. (supersedes
P0973FW)
Single Mode Fiber (SMF) fiber optic patch cable w/ LC - LC 50 m (165 ft) RH973FX
connectors. (supersedes
P0973FX)

Simplex-Single Mode Fiber Optic Cabling

Equip each switch with an appropriate uplink module in order to use Simplex-single mode fiber
optic cables. Foxboro recommends that the selected Simplex-single mode fiber optic cabling has
these characteristics:
♦ 8-10 micron core/125 micron cladding
♦ Typical allowable signal loss = 0.5 dB/km at a wavelength of 1300 nm or 0.275 dB at
a wavelength of 1590 nm
Transmission distances for Simplex-single mode fiber optic cable are given in Table 2-13.

Table 2-13. Simplex-Single Mode Fiber Optic Cable - Maximum Transmission

Application Transmission Protocol Max. Distance

Switch to Switch 1000Base-BX 120Km (74.6 mi)
S-SMF cable is supplied by the customer

Foxboro does not offer Simplex-single mode fiber optic cables. The control network uses cables
with a LC connector which has a single fiber which uses a different Tx frequency from the Rx fre-
quency as a crossover within the same cable.

62
2. Site Planning B0700AZ – Rev V

Connector Types for Switches

Refer to the documentation included with your Foxboro qualified Ethernet switches for their con-
nector types and uplink ports.

Patch Panels
The LC jumper cables go straight through and the connector on the switch serves as the crossover.
When patch panels are created using LC connectors, if the fiber run between two patch panels has
a crossover, then the jumpers supplied by Foxboro do not work. See Figure 2-23.

P1 TX RX
P4
RX TX

TX RX
RX TX

TX RX
RX TX

P4 TX RX P1
RX TX

Switch Switch
Switch to Switch Connection

P1 TX RX TX RX TX RX
P4
RX TX RX TX RX TX

TX RX TX RX TX RX
RX TX RX TX RX TX

TX RX TX RX TX RX
RX TX RX TX RX TX

P4 TX RX TX RX TX RX P1
RX TX RX TX RX TX

Switch Patch Patch Switch

Switch to Patch Panel Connection
Figure 2-23. Switch to Switch and Switch to Patch Panel Connections

FCP280, FCP270, ZCP270, FCM100Et, and FCM100E Fiber Signal Cabling

The cables listed in Table 2-14 are offered for use in making 100 Mb fiber optic cable connections
for the control network. Whether these items are shipped to your location depends on the
100 Mb network cabling configuration specified at the time of system purchase.
Fiber optic cabling connects the Ethernet 100 Mb switches using one MT-RJ connector and con-
nects directly to the fiber adapters on an FCP280 baseplate, or a FCM100E using two ceramic
type LC fiber optic connectors. These same connectors can connect the switches to the split-
ter/combiner for the FCP270, ZCP270, or FCM100Et.
Verify that the maximum optical insertion loss though each connector is equal to or less than 0.5
db. For the fiber optic cable lengths, refer to Table 2-14.

63
B0700AZ – Rev V 2. Site Planning

Table 2-14. Fiber Optic Cables

Part
Number Connector Length Color Use Cable Material
P0972TR LC to 3 m (9.8 ft) No specified Switch to Split- MMF
P0972TS MT-RJ 15 m (49.5 ft) color ter/Combiner 62.5/125
FCP270/ micron
P0972TT 50 m (165 ft)
ZCP270/
- Customer sup- FCM100Et
plied, over 50 m or directly to
(165 ft) to 2 km FCM100E
(6600 ft) fiber (without Split-
optic cable ter/Combiner)
P0972 UJ LC to LC 1.0 m (3 ft)
P0972TN 3 m (10 ft)
P0972TP 15 m (50 ft)
P0972TQ 50 m (165 ft)
RH972ZQ 0.25 m (1.0 ft)
(supersedes
P0972ZQ)
P0972UN 0.5 m (2.1 ft) Gray color for
A Bus
P0972VG 0.5 m (2.1 ft) Orange color
for B Bus

64
2. Site Planning B0700AZ – Rev V

Table 2-14. Fiber Optic Cables (Continued)

Part
Number Connector Length Color Use Cable Material
RH972VD ST to 3 m (9.8 ft) No specified Interface MMF
(supersedes MT-RJ color MT-RJ devices 62.5/125
P0972VD) to an ST-type micron
RH972VE 15 m (49.5 ft) patch panel
(supersedes
P0972VE)
RH972VF 50 m (165 ft)
(supersedes
P0972VF)
P0972WW LC to SC 3 m (9.8 ft) Interface legacy Mode condi-
P0972LQ tion MMF
(GPIM-01) to
P0972WT
(MGBIC-LC01)
P0972WX 3 m (9.8 ft)
P0972QP SC to SC 3 m (9.8 ft) SMF
P0973EW LC to SC 3 m (9.8 ft) Interface legacy SMF 10
P0972LR micron
(GPIM-09) to
P0972WU
(MGBIC-LC09)
RH973EX LC to ST 3 m (9.8 ft) Interface
(supersedes P0972WU
P0973EX) (MGBIC-LC09)
to an ST patch
panel

When designing the control network topology, be aware that when utilizing the FCP280 copper
adapter (RH924UQ) or the workstation copper NIC card (P0922KY), consider switch types.
Refer to “Group B” in Table 2-15 for switches with copper connectivity. Refer to “Group A” in
Table 2-15 for switches with fiber optic connectivity.
When utilizing copper cabling, evaluate cables transitioning through an excessive EMI noise envi-
ronment. If it is determined that the copper cabling cannot be used in these circumstances, the
switch may be required to be installed in the same enclosure. If this is the case, only the X-Series
switches (RH102AM/AN/AP) can be utilized within a control processor’s enclosure (refer to the
enclosure PSSes called out in G-Series Enclosures Overview (PSS 21H-2GOV B3) for each enclo-
sure’s specifications). Also evaluate environmental considerations since the X-Series switch does
not meet the same G-rating as the control processor.

65
B0700AZ – Rev V 2. Site Planning

Table 2-15. Switch Group Isolation

Group A - Fiber Optic Switches Group B - Copper Switches

P0972YC (V-Series) P0972WP (V-Series)
P0972YJ (N-Series) P0972YG (N-Series)
P0973BJ (A-Series) P0973BH (A-Series)
P0973BK (A-Series) P0973BK (A-Series)
P0973BR (N-Series) P0973BQ (N-Series)
P0973BS (N-Series)
P0973GB (I-Series) P0973GA (I-Series)
P0973HB (I-Series) P0973HC (I-Series)
P0973HC (I-Series)
P0973JN (A4-Series) P0973JM (A4-Series)
P0973JP (A4-Series) P0973JP (A4-Series)
P0973HA (C-Series)1 P0973LK (B-Series)
P0973KD (S-Series)1
P0973KJ (C-Series)1
P0973KK (S-Series)1
P0973LN (S-Series)1
RH102AB (X-Series)1, 2 RH102AB (X-Series)1, 2
RH102AC (X-Series)1, 2 RH102AC (X-Series)1, 2
RH102AD (X-Series)1, 2 RH102AD (X-Series)1, 2
RH102AN (X-Series) RH102AM (X-Series)
RH102AP (X-Series) RH102AP (X-Series)
RH102AQ (X-Series)
RH102AY (X-Series)
1. Supports the 100Mb Fiber LC MMF if using P0973JE SFP transceiver.
2.
Supports the 100 Mb Copper RG-45 if using RH102AL SFP transceiver
and configured as a 100 Mb device port.

Figure 2-24 shows the cabling for the FCP280. Figure 2-25 shows the cabling for the FCP270,
ZCP270, FCM100Et, FCM100E or patch panels.

66
 OPTIONAL 1 GBit UPLINKS.
REQUIRE UPLINK GBIC MODULES
(P0972WT, P0972WU, RH102AL,
P0972YQ, P0973GH, P0973GJ, P0922KY
10/100Base-TX
P0973FT, or P0973FU) ETHERNET
Fiber 100Base-FX SWITCH Copper 100Base-TX SWITCH PCI CARD

NOTES:
W/RJ-45 CONNECTORS
SWITCH GROUP A SWITCH GROUP B P0922KY
10/100Base-TX
2. Site Planning

TWO SINGLE

ETHERNET
ETHERNET CARD(S)

PCI CARD
COPPER
CABLE GROUP A
Copper 100Base-TX SWITCH
W/RJ-45 CONNECTORS PROCESSOR CARDS
Fiber 100Base-FX SWITCH SWITCH GROUP B THE CONTROL (Workstation)
NETWORK
SWITCH GROUP A

Twinaxial CAT5 cabling

Fiber Optic
Up to 100 m (328 ft).
Cable Group E

CP adapters, this length is 2 km (1.24 mi).

Fiber Adapter (RH924WA) Copper Adapter (RH924UQ) -See Notes

FCP FCP FCP FCP

280 280 280 280

Figure 2-24. FCP280 Signal Cabling

Connection to FCP280 Connection to FCP280
(Fiber) (Copper)

CONNECTION TO ZCP270
GREEN
COPPER (ie, Cu) ETHERNET CABLE
* = NULL MODEM CABLE

C5-Series switches (P0973KJ), and S-Series switches (P0973KD/P0973KK).

# = 1:1 CABLE MAGENTA
FIBER (ie, FO) ETHERNET CABLE

NOTE: Processor I/O cards are illustrated for cabling purposes only.

1. The copper adapter cannot be used with the C-Series switches (P0973BL/P0973HA),
CABLE GROUP A FIBER CABLE GROUP E
100Base-TX, CAT 5 MMF with MT-RJ/LC CABLES
P0972UB = 0.5 m P0972TR = 3 m
P0971XK = 3 m P0972TS = 15 m
P0971XL = 15 m P0972TT = 50 m
P0972MR = 30 m CUSTOMER SUPPLIED = >50m, < 2 km
B0700AZ – Rev V

P0971XM = 50 m

67
P0971XN = 100 m

2. For the FCP280, the maximum length of a copper cable connection is 100 m (328 ft). For MMF fiber
 OPTIONAL 1 GBit UPLINKS.
REQUIRE UPLINK GBIC MODULES

68
(P0972WT, P0972WU, RH102AL,
P0972YQ, P0973GH, P0973GJ, P0922KY
10/100Base-TX
P0973FT, or P0973FU) ETHERNET
Fiber 100Base-FX SWITCH Copper 100Base-TX SWITCH PCI CARD
W/RJ-45 CONNECTORS
SWITCH GROUP A SWITCH GROUP B P0922KY
10/100Base-TX
TWO SINGLE

ETHERNET
B0700AZ – Rev V

ETHERNET CARD(S)

PCI CARD
COPPER
CABLE GROUP A
Copper 100Base-TX SWITCH
W/RJ-45 CONNECTORS PROCESSOR CARDS
Fiber 100Base-FX SWITCH SWITCH GROUP B THE CONTROL (Workstation)
NETWORK
SWITCH GROUP A

SINGLE FCP
SINGLE FCM
A

A
FBM FBM B
FBM FBM

(P0917YZ)
FIBER OPTIC

FCP270
CABLE GROUP E RH972ZQ/
(P0972ZA)
(P0972ZA)

FCM100E**
FCM100E**

B I/A Series I/A Series P0972ZQ

P0972UN (GRAY) I/A Series I/A Series I/A Series I/A Series
P0972VG (ORANGE)
FAULT TOLERANT PAIR
REDUNDANT PAIR

OPTICAL
SPLITTER
A A

OPTICAL
SPLITTER
A A
FBM
OPTICAL
SPLITTER

OPTICAL
SPLITTER
B B

(P0917YZ)
(P0917YZ)

FCP270
FCP270

FBM

OPTICAL
SPLITTER
(P0926GS)
(P0926GS)

I/A Series
FCM100Et**
FCM100Et**

B B
DIN RAIL
MOUNTED

I/A Series I/A Series I/A Series

OPTICAL
SPLITTER
ZCP270 ZCP270 RH972ZQ/P0972ZQ

OPTICAL
SPLITTER
OPTICAL
SPLITTER

P0972UN (GRAY)
P0926AH RH972ZQ/P0972ZQ P0926AH P0972VG (ORANGE)
P0926AH
P0972UN (GRAY)
CONNECTION TO FCP270 CONNECTION TO FCM100Et
P0972VG (ORANGE)
or FCM100E
CONNECTION TO ZCP270
GREEN
COPPER (ie, Cu) ETHERNET CABLE
* = NULL MODEM CABLE
# = 1:1 CABLE MAGENTA ** Also, FCM100E modules (P0972ZA)
FIBER (ie, FO) ETHERNET CABLE
may be used in place of FCM100Ets.
The FCM100E modules do not require
splitter/combiners for connection to the switches.

Figure 2-25. FCP270, ZCP270, FCM100Et and FCM100E Signal Cabling

NOTE: Processor I/O cards are illustrated for cabling purposes only.

CABLE GROUP A FIBER CABLE GROUP E

100Base-TX, CAT 5 MMF with MT-RJ/LC CABLES
P0972UB = 0.5 m P0972TR = 3 m
P0971XK = 3 m P0972TS = 15 m
P0971XL = 15 m P0972TT = 50 m
P0972MR = 30 m CUSTOMER SUPPLIED = >50m, < 2 km
2. Site Planning

P0971XM = 50 m
P0971XN = 100 m
3. Installation (Cabling)
This chapter describes the steps necessary to install the cabling that enables the Foxboro Evo
Control Network equipment to communicate.
Installation of the control network consists of locating the individual components and then mak-
ing connections between them using fiber optic or copper cable. The next paragraphs provide the
information necessary for the cabling installation of the high performance system network.

NOTE
Refer to the documentation included with your Foxboro qualified Ethernet switches
to install these switches and the media converters as part of the control network.

Connecting The Foxboro Evo Control Network

Components
Fiber Optic Cabling Guidelines
Follow these guidelines when making fiber optic connections between devices in the control net-
work:
♦ Minimum bend radius - Fiber optic cable can be damaged if it is bent too sharply.
Maintain a minimum bend radius of two inches when using fiber optic cable supplied
by Foxboro. Follow the cable manufacturers guidelines if third-party fiber optic cable
is used.
♦ Cable straps - Design cable straps, if used, for use with fiber optic cable. Hard plastic
cable ties can damage fiber optic cable and are not recommended.
♦ Dust caps - Keep dust caps in place over the cable ends and in the switches while
cables are being routed to help protect the polished cable ends. It is recommended to
install dust caps on unused switch ports.

Interconnecting Ethernet Switches

Depending on which switch model has been selected as the root network switch, additional
switches may be connected in one of several ways. Refer to the “Ethernet Switch Interconnection
Diagrams” in the documentation included with your Foxboro qualified Ethernet switches for
detailed cabling diagrams.

69
B0700AZ – Rev V 3. Installation (Cabling)

NOTICE
POTENTIAL DATA LOSS

Do not make direct interconnection between ports of the same switch

(loopback). Loopbacks can result in network detected failures during
RSTP instability.

Failure to follow these instructions can result in data loss.

Refer to page 61 for a list of single mode fiber optic cables for use at patch panels.

NOTE
These graphics of switches and media converters are intended as generic illustra-
tions of networking concepts and do not necessarily reflect the currently offered
products.

NOTE
These sections pertain to both standard switches and chassis switches.

Inter Switch Link (ISL) Interfaces

The Ethernet switches can be connected to each other through the use of an uplink port. Depend-
ing upon which uplink module is installed, the switch is able to communicate over single mode,
multimode fiber optic cable, or CAT5 copper cable. Transmission via uplink ports is made using
the Gigabit Ethernet protocol. The ISL ports utilizing fiber optic cable uses LC type connectors
and should be designed for the mode (single mode vs. multimode) of the uplink module that is
installed in the Ethernet switch’s interface slot (SFP). Figure 3-1 shows a connection between two
Ethernet switches using their fiber optic uplink ports.

Fiber Switch Fiber Switch

1000Base-SX, 1000Base-BX, 1000Base-LX or

1000Base-ZX
62.5/125 micron Single/Multimode
Fiber Optic Cable
w/LC-type Connectors
Figure 3-1. Switch-to-Switch Fiber via Uplink Port

Managed switches can be connected directly to other switches connecting each switch’s fiber optic
ports with fiber optic cable.

70
3. Installation (Cabling) B0700AZ – Rev V

NOTE
Verify that the transmit (TX) port of one switch is connected to the receive (RX)
port of the other switch. The standard Foxboro LC to LC cable helps ensure proper
TX to RX connections.

Fiber optic cable can be used to connect fiber switches to other fiber switches using each device’s
100Base-FX fiber ports. Multimode fiber cable is connected between a port on each switch.
Figure 3-2 gives an example of a port-to-port connection via fiber optic cable. However, even
though this method can be used for uplink ports, it is not recommended due to the 100 Mb
port's bandwidth capabilities. This method of uplinks must not be used for the Enhanced Net-
work Configuration topology designs. Normally, use 1 Gb uplink connections to interconnect
switches in all standard or enhanced network designs.

Fiber Switch Fiber Switch

100Base-FX
62.5/125 micron Multimode
Fiber Optic Cable
w/LC Connectors
Figure 3-2. Port-to-Port Connection via Fiber Optic Ports

NOTICE
POTENTIAL DATA LOSS

If Fast Ethernet “Device” ports are used as uplink ports between

switches, it is very important that the switch spanning tree edge-port
protocol settings be configured correctly. Not doing so will cause
system degradation during switch failover, causing excessive packet
flooding possibly resulting in network instability. (Refer to Switch
Configurator Application Software Guide for the Foxboro Evo Control
Network (B0700CA).)

Failure to follow these instructions can result in data loss.

Switch Configuration
Refer to Switch Configurator Application Software Guide for the Foxboro Evo Control Network
(B0700CA) and the documentation included with your Foxboro qualified Ethernet switches for
instructions on configuring them for the control network.

71
B0700AZ – Rev V 3. Installation (Cabling)

NOTE
It is highly recommended that you change the switch’s admin user account name
and password. You need to set the password as a strong password. For more infor-
mation on changing the switch password and settings, refer to Switch Configurator
Application Software Guide for the Foxboro Evo Control Network (B0700CA).

72
4. Maintenance
This chapter provides troubleshooting information for the Foxboro Evo Control Network.

The Foxboro Evo Control Network and Other

Associated Foxboro Evo-Related Addresses
The Foxboro Evo equipment IP addresses for the control network are 151.128.81.1 -
151.128.83.254. IP addresses assigned to the primary port of control processors (FCP280,
FCP270, ZCP270), FCM100Ets, FCM100Es, and workstations are 151.128.y.z (where y is a
number between 152 and 191, and z is a number between 1 and 254). The IP addresses for the
alternate ports of FCM100Ets, FCM100Es or workstations are 151.128.w.z (where w is derived
from y above as w = y - 128, and z is the same value as above). The IP addresses for the primary
I/O controller ports of ZCP270 are 151.128.v.z (where v is derived from y above as v = y + 64, and
z is the same value as above). The IP addresses for the alternate Input/Output Controller (IOC)
ports of ZCP270 are 151.128.u.z (where u is derived from y above as u = y - 64, and z is the same
value as above). See Table 4-1.
Fault tolerant stations, such as FCP280s, FCP270s, and ZCP270s, use the same IP addresses for
both modules of the fault tolerant pair. Additionally, the ZCP270 requires a third and fourth IP
address for its Input/Output Controller (IOC) ports. These also are derived and assigned accord-
ing to Table 4-1.

Table 4-1. IP Address Assignments

I/A Series or
Foxboro Evo
Release Port IP Address
v8.0 or later I/O Network Switches and 151.128.83.1 through 151.128.83.254
CNI VRRP gateways
v8.0 or later Network Monitoring Devices 151.128.82.1 through 151.128.82.254
v8.0 or later Primary Port 151.128.152.1 through 151.128.191.254
v8.0 to v8.1.x Alternate Port1 151.128.24.1 through 151.128.63.254
v8.0 or later Primary IOC Port 151.128.216.1 through 151.128.255.254
v8.0 or later Alternate IOC Port 151.128.88.1 through 151.128.127.254
v8.0 or later Switches 151.128.81.1 through 151.128.083.254
Pre-v8.0 Single Node 151.128.8.65 through 151.128.8.126
Pre-v8.0 Multi-Node 151.128.16.65 through 151.128.23.254
Pre-v8.0 Switches 151.128.079.001 through 151.128.080.254

73
B0700AZ – Rev V 4. Maintenance

Table 4-1. IP Address Assignments (Continued)

I/A Series or
Foxboro Evo
Release Port IP Address
- Open Foxboro IP addresses 151.128.1.1 through 151.128.7.254
151.128.8.1 through 151.128.8.64
151.128.9.1 through 151.128.16.64
151.128.64.1 through 151.128.78.254
151.128.84.1 through 151.128.151.254
151.128.192.1 through 151.128.215.254
1. At I/A Series software v8.2, the intermediate driver was changed so that the Alternate Port IP address
is not used.

IP addresses for devices on the control network (workstations, controllers, managed switches,
FCM100Ets and FCM100Es) are assigned by the system configurator (Foxboro Evo Control Edi-
tors, SysDef, or IACC). For information on using a system configurator, refer to:
♦ System Definition: A Step-by-Step Procedure (B0193WQ)
♦ I/A Series Configuration Component (IACC) User's Guide (B0700FE)
♦ Hardware Configuration User's Guide (B0750BB)
Once the configurator has assigned the primary IP address, each Ethernet switch must be config-
ured with its assigned IP address using the Command Line Interface (CLI) Entries or Switch
Configurator Application Software (discussed in the switch configuration section of the docu-
mentation included with your Foxboro qualified Ethernet switches). One IP address is assigned to
each non-Chassis Ethernet switch in the control network. For the SSA Chassis switch
(P0973KK/LN), the chassis is assigned one IP address. For the S4 Chassis switch (P0973KD), the
chassis is assigned only one IP address for the three blades.
The system configurator (Foxboro Evo Control Editors, SysDef, or IACC) assigns a MAC (Media
Access Control) address for each station on the network. The primary port MAC addresses are
assigned from the range, 00006CC00000 to 00006CC03FFF. The alternate port MAC addresses
are derived from the primary port MAC addresses by “ORing” the primary network MAC address
with 000000004000, yielding a range of 00006CC04000 to 00006CC07FFF. The MAC
addresses for the primary I/O controller ports of ZCP270 are derived from the primary port
MAC addresses by “ORing” the primary network MAC address with 000000008000, yielding a
range of 00006CC08000 to 00006CC0BFFF. The MAC addresses for the alternate I/O control-
ler ports of ZCP270 are derived from the primary port MAC addresses by “ORing” the primary
network MAC address with 00000000C000, yielding a range of 00006CC0C000 to
00006CC0FFFF.
Workstations, FCP280s FCP270, ZCP270, CNIs, FCM100Et, FCM100E and FBMs are
assigned letterbugs to identify the module by the system configurator. FBMs are not assigned IP
or MAC addresses. Letterbugs and IP addresses can be changed using the system configurator.

74
4. Maintenance B0700AZ – Rev V

General Troubleshooting Guidelines

When a problem is detected with the control network, it is worthwhile to take an organized
approach to diagnosing the cause. A random or scattered approach generally takes longer and can
make it more difficult to track down the cause by introducing additional unknowns. These sec-
tions will help you troubleshoot the network.

Characterize the Problem

The initial step in diagnosing detected network problems is to understand what kind of problem
exists.
♦ Has the detected problem existed previously or has it just started?
Newly detected problems are sometimes caused by a change in the control network
configuration. Check to see whether there have been recent changes to the control
network hardware, software, or configuration files.
♦ Is the detected problem constant or intermittent?
Detected problems that are constant are often the result of a component detected fail-
ure or a change to the control network configuration. Detected problems that are
intermittent can be caused by environmental factors such as excess heat, electrical
noise, poor contacts, or high attenuation.
♦ What kind of error indication is occurring?
Device communication detected failure - inability to communicate with one or more
devices on the control network. This happens when the information path has been
broken or interrupted. Possible causes are damaged or misconnected cabling, a
detected failure in a network device, or high attenuation.
Data Loss - incorrect data is arriving at one or more devices. The data path is intact,
but the data is being corrupted along the way. This can be caused by unstable network
devices, environmental factors, or exceeding transmission distance limits.
Error message - software has detected a problem. This can be caused by any number
of things. The text of the error message indicates what kind of problem has been
detected.

Determine Which Devices are Affected

Identifying the devices that are affected helps to determine where the cause of the problem lies.
For example, if all the unreachable devices are connected to the same Ethernet switch, then it
would be worthwhile to start troubleshooting at that switch.
When troubleshooting an Enhanced Network Configuration with LDP deployed, refer to the sec-
tion “Loop Detection Monitoring and Maintenance” in Switch Configurator Application Software
Guide for the Foxboro Evo Control Network (B0700CA) before continuing.
Follow the steps below to identify which device or devices are affected.
1. Are the detected problems limited to specific devices (stations, switches), or are they
general in nature?
2. Can the devices be reached using the ping command?
3. Does the ping -s command report that packets are being dropped?

75
B0700AZ – Rev V 4. Maintenance

4. What does System Management Displays indicate? Refer to “System Management

Displays” on page 76.
5. Use a network topology map to determine the physical location of the affected
devices.

Troubleshoot the Affected Devices

1. Check activity and status indicators on the affected devices.
2. Verify that the devices are getting power (check Status LEDs).
3. Check that the devices are correctly cabled and that the cables are not damaged (swap
a suspect cable with a known good cable).
4. Verify that the limit on distance between devices has not been exceeded. Distance is
dependent on transmission mode and cable type.
5. If fiber optic cable is being used, verify that the optical budget (total signal loss - dB),
bandwidth, and dispersion are within specification.
6. Verify that traffic rates to the affected devices are not excessive.
7. Check System Management error counters. Refer to System Management Displays
(B0193JC) or System Manager (B0750AP).
8. Verify that the devices are properly configured. Also check that the adjacent device in
the network is correctly configured as well.

NOTE
Before removing a switch from the network, record its existing configuration. This
information is necessary when the replacement switch is configured.

NOTE
Verify that a replacement switch is correctly configured before adding it to the net-
work. Any uplink ports should be installed before the switch is configured. Refer to
the documentation included with your Foxboro qualified Ethernet switches for
more information.

System Management Displays

The System Management Display Handler (SMDH) and System Manager obtain current and
historical information about the system from the System Monitor, and display this information in
System Management displays. SMDH and System Manager use SNMP to access the switches to
obtain status information from each switch. With regard to the control network and associated
Ethernet switches, SMDH and System Manager provide these displays:
♦ A Switched Network View of the configured switches
♦ A Switch Domain display that shows the control network stations in the selected
Switch’s domain.
♦ A Switch Ports Display which shows each port of the switch that was selected on the
Domains display

76
4. Maintenance B0700AZ – Rev V

♦ Detailed equipment information (EQUIP INFO) and equipment change (EQUIP

CHG) displays for each port of the selected Ethernet switch.
For information on viewing this information in the System Manager, refer to System Manager
(B0750AP).

NOTE
X460 switches (RH102AC/AC) have two IEEE1588 ports that are monitored using
SNMP and are not enabled until physically populated. Currently the IEEE1588
(Precession Time Protocol) ports are not supported on the FECN.
However, since the ports are monitored System Manager will report these ports as
failed.

NOTE
The switch ID names for the X-series switches will always be lead by the model type
(i.e. X440G2 <letter-bug>) and because of this limitation SysMon may report the
this error:
LBUG – IP in the d:/usr/fox/sp/switches.cfg file doesn’t match the switch LBUG –
IP

NOTE
The X-series switches have an out-of-band Management Ethernet port that is not
used on the control network (FECN). However, it is monitored using SNMP since
the port is monitored System Manager will report this port as failed.

Limitations on Number of Switches Assigned to a Single System

Monitor
In order to optimize the performance of System Monitors on a system with I/A Series software
v8.x and Foxboro Evo Control Core Services v9.0 or later, the total number of switches assigned
to a single System Monitor cannot exceed fifteen, and the total number of switch ports for the
switches assigned to a single System Monitor cannot exceed five hundred.

Indicators
Ethernet Switches
For the location and meaning of the indicators on a particular Ethernet switch, refer to the docu-
mentation provided with the switch.

Media Converter
For the location and meaning of the indicators on a particular media converter, refer to the docu-
mentation provided with the device.

77
B0700AZ – Rev V 4. Maintenance

Fiber Optic Cable Handling and Cleaning

Fiber optics communication relies on a clear path for its signals. Make every effort to install
splices, connectors, and terminations as clean as possible from dust, oils, and surface abrasions,
thus reducing their effects on optical data transmission.

Handling Fiber Optic Cable

Consult the cable specifications for the cable you are installing. Mishandling the cable may cause
damage that can alter its transmission characteristics requiring replacement of the cable. When
handling fiber optic cabling:

WARNING
POSSIBLE EYE DAMAGE

• Never look directly into the end of a fiber cable or bulkhead

adapter. Eye damage may result. Laser light can damage your
eyes. Laser light is invisible. Viewing it directly does not cause
pain. The iris of the eye does not close involuntarily as when
viewing a bright light. Consequently, serious damage to the ret-
ina of the eye is possible.
• Never look into the end of a fiber, at a connector, or a connector
in an inspection microscope which may have a laser coupled to
it. If accidental eye exposure to laser light be suspected,
arrange for an eye examination immediately.

Failure to follow these instructions can result in serious injury.

♦ Turn off power to the equipment before cleaning or looking at fiber cable ends.
♦ Always use dust covers on the end of the fiber cable connector (see Figure 4-1,
Figure 4-2 and Figure 4-3) or any bulkhead (including unused bulkheads)
♦ Do not pull or kink the cable as the glass strand in the middle might become damaged
or broken
♦ Do not walk-on, step-on, or crush the cable as the glass strand in the middle might
become damaged or broken
♦ Keep bend radii no less than two inches
♦ Use specialized optical cable raceways and plenums whenever available
♦ Never use tie wraps as you would with electrical cables
♦ When using optical connectors, insert or remove the ferrule straight into the sleeve.
Minimize wiggling the connection as this may loosen the tight fit
♦ For SC connectors, orient the prominent key on the connector body with the slot in
the bulkhead adapter. Push the connector until it clicks. To remove, pinch the con-
nector body between your thumb and finger, and gently pull straight out (see
Figure 4-1)

78
4. Maintenance B0700AZ – Rev V

Release Tabs
Dust Covers

Figure 4-1. SC Connector, Typical

♦ For MT-RJ connectors, orient the connector body with the slot in the bulkhead
adapter. Push the connector until it clicks. To remove, push the release tab between
your thumb and finger, and gently pull straight out (see Figure 4-2)

Release Tab Dust Cover

Figure 4-2. Multimode MT-RJ Connector

♦ For LC connectors, orient the connector body with the slot in the bulkhead adapter.
Push the connector until it clicks. To remove, push the release tab between your
thumb and finger, and gently pull straight out (see Figure 4-3).

79
B0700AZ – Rev V 4. Maintenance

Release Tab
Dust Covers

Figure 4-3. Multimode Duplex LC Connector

Cleaning Fiber Optic Cable

Contamination of Fiber Optic Connectors and Sockets
Fiber optic cable connector parts are particularly sensitive to contamination which reduces the
light transfer from one side of the interface to the other. Finger oils, dust, fuzz, and so forth, can
attenuate the photon transfer across the cable connector to the socket interface. Experience has
shown that minute quantities of contaminants can have major effects on the communication
between controllers and workstations.
The first line of defense is to help prevent contamination from building up on the sensitive fiber
optic surfaces. The second approach is to remove the contamination once it has occurred. Preven-
tion of contamination is easier and cheaper than cleaning up after the fact.

Contamination Prevention
The easiest way to help prevent contamination from affecting fiber optic sockets is to keep the
protective covers (see Figure 4-1, Figure 4-2 and Figure 4-3) on all sockets which are not currently
in use. Retain these dust covers (rubber plugs) in a place where they can be retrieved or maintain a
ready supply of covers so that they may be inserted into sockets when cables are removed. All fiber
optic switches, control modules (for example, FCP280, FCP270 and ZCP270), and interface
modules (for example FCM100Et, FCM100E, Fiber NIC, ATS) come with protective plugs
installed in each socket. Figure 4-4 shows an example of microscopic lint which has lodged in a
fiber optic LC socket. The contaminant in this example kept the port from functioning. This type
of contamination similarly affects MT-RJ and SC connectors, especially when static charges on
the connectors attract charged particles.

80
4. Maintenance B0700AZ – Rev V

Figure 4-4. Lint in Fiber Optic LC Socket

Cleanliness is equally necessary with FO cable connectors’ plugs. Finger oils as well as dust and
lint can negatively affect the cable plug’s transmission abilities. As with the sockets, the easiest
defense is to keep the dust covers, which come shipped on the connectors, in place until just
before insertion into a socket.

Contamination Removal
In spite of following the best contamination prevention procedures, you may eventually encoun-
ter a “dirty” connection, in which case you must clean the connection. There are basically three
methods to remove contamination from FO connections; blowing, chemical washing, and abra-
sion.
The blowing method consists of removing dust or lint from a connector with a blast of dusting
gas such as Tetrafluoroethane, usually from an aerosol can. This is effective for removing material
in depressions (such as in a socket) which is loosely coupled to the surface, for example, as by
static electricity. Because dust can be transferred into connector sockets through the normal inser-
tion of cable plugs, it is good practice to dust off the connector before plugging it in.
Chemical washing basically consists of flushing or wiping the face of a fiber with isopropyl alco-
hol. The alcohol can be wiped on the fiber face by applying the fluid to a lint-free wipe or lint-free
swab, or by using pre-saturated wipes. These alcohol saturated wipes are most useful in cleaning
the connectors on the ends of cables where the exposed fibers are most easily accessible. The alco-
hol saturated swabs are needed for the female sockets in which the fiber is located in deep recesses.
The abrasion technique is useful for cleaning cable connectors such as MT-RJ style; it is not used
to clean sockets. It is a dry method which does not require isopropyl alcohol. It is generally avail-
able in the form of a fabric tape housed in a dispenser which exposes a short length of tape over
which you wipe the end of the connector. The fabric tape acts as a fine abrasive which removes
contamination from the glass fiber end.
Examples of cleaning products are listed below.If you use fiber optic cables, verify that you have
similar items available so that you can quickly get back on-line when a contamination situation
arises. Observe the storage and use suggestions provided by the vendor of these cleaning products
because some are classified as hazardous material. Obtain and use the Material Safety Data Sheets
(MSDS) and U.S. Department of Transportation DOT-E 10232 literature associated with these
products as handling guides.

81
B0700AZ – Rev V 4. Maintenance

Examples of Fiber Optic Connector Cleaning Products

These products are available through various distributors:
♦ Techspray Fiber Optic Cleaning Kit, Part number 1602 (see: www.techspray.com)
Contains: Isopropyl alcohol, alcohol saturated wipes, aerosol duster, swabs, and wipes.
♦ Techspray Aerosol Duster, Part number 1671-15S (see: www.techspray.com)
Contains an Aerosol duster (can of compressed Tetrafluoroethane gas).
♦ Cletop S Cassette cleaner, P/N 14110611 (see: www.cletop.com)
An abrasive-type cable connector cleaner.
♦ Cletop 1.25 mm Q-tip (swab) stick cleaner, P/N 14100401(see: www.cletop.com)
♦ Corning Cable Systems, P/N 2104359-01(see: www.corning.com/cablesystems)
An abrasive-type cleaning cassette.

Environmental Guidelines
Dust Mitigation and Prevention
Dust accumulation on ingress and egress venting is common after prolonged use.
We recommend routine maintenance to check and clean ingress and egress vents. Over time, dust
accumulation can create vent blockages, decreasing airflow and increasing component tempera-
tures resulting in reduced reliability. Maintenance should start with monthly inspections and
should be adjusted based on dust accumulation.
Removing dust from equipment is a part of maintenance. To remove dust:
♦ Use proper precautions for electrostatic discharge (ESD)
♦ Use a vacuum cleaner that is properly grounded through a cord having an equipment-
grounded conductor and grounding plug.
♦ Make sure equipment is power down and power has been removed from the
equipment.
♦ Carefully vacuum the dust particles from the inlet and exit venting of the equipment
to allow for proper airflow and ventilation.

NOTE
Operating the equipment without proper maintenance can decrease the equip-
ment’s service life.

Airborne Chemicals and Prevention

Various airborne chemicals and contaminants can cause corrosion and thus decrease the service
life of the electronic equipment. To reduce the risk of corrosion, keep the equipment in areas that
are safe for long-term human occupation.

82
5. Combining Two or More
Instances of The Foxboro Evo
Control Networks
This chapter provides information on combining two or more instances of the Foxboro Evo
Control Network.

Overview
When combining two or more implementations of the control networks, many variables must be
taken into consideration. Combining control networks actually refers to combining Foxboro Evo
systems. When Foxboro Evo systems are combined, generate new Commit media which contains
the stations from the combined systems. Recommit all workstations and any station that receives
a new letterbug, NSAP, MAC address or IP address has to be rebooted.
These examples cover some of the basic situations and list the essential principles to follow. Take
care when combining networks in order to help prevent system or network problems and even
possible system shutdown.
Rules:
1. Perform a complete inventory of all device IP, MAC and NSAP addresses on all net-
works to verify that no duplicate addresses are present.
2. Establish the topology of both networks and obtain the following required informa-
tion.
a. Which switches are designated as the root bridge switches (Root/Back-up root) on
all networks
b. What topology configuration are the networks (Star, Tree, Ring, etc.), and are
they compatible with each other (with the consideration of the step c below)?
c. When the two networks become, as one, will any two switch communications
exceed the maximum limit of seven hops?
d. If VLANs are deployed on one or more networks do the VLAN assignments
match between the networks?
e. If Loop Protection Algorithm (LPA) is deployed on one or more networks, how
will they function between each other when considering the rule requirements for
LPA? For more information on the LPA rules, refer to “Planning Loop Protection
Algorithm (LPA) Configurations” on page 29.
f. If Loop Detection Policy (LDP) is deployed on one or more networks, how will
they function between each other when considering the rule requirements for
LDP?

83
B0700AZ – Rev V 5. Combining Two or More Instances of The Foxboro Evo Control Networks

WARNING
POTENTIAL LOSS OF DATA AND/OR PROCESS CONTROL

When combining two or more “live” networks, the process can result in
loss of data or control of the process. It is very important that all
network and device components attached to the network be 100%
functional and verify that you know the functioning status of all
switches (root, back-up root, uplink port status, configuration and
location).

Failure to follow these instructions can result in death or serious

injury.

These sections describe the process by which two or more networks are combined.

Planning Stage
Assume that if two or more networks are being combined that there is more than one Foxboro
Evo system in operation. To combine two or more Foxboro Evo systems, re-commit the systems
in whole. When re-committing the systems, consider the Bridge switch functionality - see below.

Station Addressing
1. If duplicate IP, MAC and NSAP addresses on Foxboro Evo devices or stations exist
within the networks, then those stations or devices have to have new addresses
assigned.
2. Stations and devices with new addressing have to be marked PCHANG and rebooted
after the whole system has been committed.
3. If duplicate IP addresses exist on a network switch, reconfigure the switch with a new
IP address and re-commit the switch host workstation to acknowledge the new IP
address of the switch.

Bridge Switch Functionality

1. Establish which pair of switches will be the root and the backup root of the new com-
bined network.
a. Make the root and backup root the switch within the network that has the largest
throughput capability.
b. Make the root and back-up root have the lowest set of IP addresses among the net-
work switches. (This is not mandatory but it is highly recommended.)
c. Any former root/backup switches need to have the priority of their Bridge IDs
changed.

Topology Constants
When merging two or more networks, consider the physical layout of the topology. For example,
if a four-layer Tree topology is to be combined with a Star topology, the Tree cannot be added to

84
5. Combining Two or More Instances of The Foxboro Evo Control Networks B0700AZ – Rev V

the Star. However, the Star can be added to the Tree but only at the root or layer one switches.
Adding the Tree to the Star results in a five-layer Tree, exceeding the limit of seven switches (hops)
between any two devices on the network. Adding the Star to the Tree's root or at the layer two
switches only results in a broader Tree which does not exceed the seven hop limit.
There are an unlimited number of ways in which network topologies can be combined. However,
follow the rules established in this document. Because of the unlimited ways of combining net-
works, take each case with its own considerations. Although this document cannot cover every
possibility, the following are a few methods in which networks should be combined.

Combining Star Network Topologies

In Figure 5-1 below, A1 and B1 are root switches with the A2 and B2 as backup root switches
within their respective Star topology networks. To combine the two Star networks with minimum
impact to the physical layout of switch and cabling, the two Star networks are combined to form
a three layered Tree topology, shown in Figure 5-2 below.

A1 A2 B1 B2
Star Star

Figure 5-1. Combining Two Star Network Topologies Into

One Tree Network Topology (Before)

A1 A2

B1 B2

Figure 5-2. Combining Two Star Network Topologies Into

One Tree Network Topology (After)

It is assumed that A1 and B1 are the root bridge switches within their respective networks and A2
and B2 are the back-up root bridges within their respective networks.

85
B0700AZ – Rev V 5. Combining Two or More Instances of The Foxboro Evo Control Networks

To do this, the following actions are required:

1. Verify that the A1 and A2 switches have a Bridge Priority value at least two (2) less
than the B1 switch. If they do not, reconfigure the A1 and A2 switches with a lower
priority value.
2. Power down the B2 switch and physically remove it from the B network, removing all
cables attached to this switch.
3. Re-configure the B2 switch as an edge switch in the A network. (Refer to Switch Con-
figurator Application Software Guide for the Foxboro Evo Control Network (B0700CA)
for configuration information.)
4. With the B2 switch powered down, physically connect the B2 switch to the A1 and
A2 switches via uplink (Trunk) cables one for each A root switch. Configure the A
root switch uplink (Trunk) port to accept the new cables (if previously disabled or if
100Mb ports are to be used).
5. Remove the previously cross-linked cables between the B1 and B2 switches from the
B1 switch. Reconnect the B network edge switches to the B2 switch.
6. Power up the B2 switch. When this is completed, the B1 switch will re-span, releasing
its root bridge function to the A1 switch. All devices on the B network have now been
migrated to the A network.
7. Power down the B1 switch and physically remove it from what is now the A network,
removing all cables attached to this switch.
8. Re-configure the B1 switch as an edge switch in the A network. (Refer to Switch Con-
figurator Application Software Guide for the Foxboro Evo Control Network (B0700CA)
for configuration information.)

NOTE
If the two networks are to be separated for maintenance at some point, insert a
lower bridge priority value (i.e. 32000) for this B1 switch. At the time of separation,
the switch re-establishes its root functions. The same can be done for the B2 switch
as well, but with a higher bridge priority value (i.e. 32001).

9. Add the B1 switch to the A network via uplink (Trunk) cables - one for each A root
switch. Configure the A root switch uplink (Trunk) ports to accept the new cables (if
previously disabled or if 100Mb ports are to be used).
10. Make the physical connections to the A root switches utilizing the old cross-linked
root connections to the B2 switch.
11. Reconnect the B1 switch to the former B network edge switches.
12. Power up the B1 switch.
You have just converted two Star network topologies into one Tree network topology.
If two Star network topologies are to be combined and it is desired that a Star topology be main-
tained (see Figure on page 89), you must also apply the process of eliminating the seconded pair
of root switches, discussed in “Combining Tree Network Topologies” on page 88.

86
5. Combining Two or More Instances of The Foxboro Evo Control Networks B0700AZ – Rev V

Combining Star with Tree Network Topology

The process for combining a Star network Topology with a Tree network Topology is the same as
for the previous procedure, “Combining Star Network Topologies” on page 85. See Figure 5-3
and Figure 5-4 below.

Tree
A1 A2 B1 Star B2

Figure 5-3. Combining a Star Network Topology with a Tree Network Topology Into One Tree
Network Topology (Before)

A1 A2

B2
B1

Figure 5-4. Combining a Star Network Topology with a Tree Network Topology Into One Tree
Network Topology (After)

87
B0700AZ – Rev V 5. Combining Two or More Instances of The Foxboro Evo Control Networks

Combining Tree Network Topologies

The process for combining two Tree network topologies is the same as for the preceding two Star
network procedures. Combining two Tree network topologies is possible if one or more of the
topologies has less than four tiers (layers). If two or more Tree network topologies has four tiers,
then this combination process is not possible. A tier (layer) must be removed from one of the
topologies, as only one topology can have four tiers. This causes an increase in effort and a higher
risk in having a network detected failure.

Tree Tree
A1 A2 B1 B2

Figure 5-5. Combining Two Tree Network Topologies Into One Tree Network Topology
(Before)

A1 A2

B2
B1

Figure 5-6. Combining Two Tree Network Topologies Into One Tree Network Topology
(After)

For two four-tier topologies, remove the root and back-up root switches of the second network
and connect the second tier switches of this network to the root and back-up root of the first
topology (see Figure ).

88
5. Combining Two or More Instances of The Foxboro Evo Control Networks B0700AZ – Rev V

A1 A2 B1 B2

Figure 5-7. Combining Two (4) Tier Tree Network Topologies Into One (4) Tier Tree Network
Topology (After)

Combining Ring Network Topologies

Ring topologies are not recommend to be combined since the seven hop limit restricts the size of
the network topology to a maximum of seven switches in the network Ring topology. When com-
bining Ring topologies, it is recommended that the Ring topology migrate to the Star or Tree
topology that best suits the physical layout of the site requirements. Because of the potential
excessive amount of re-cabling, it is recommended that a plant shutdown be considered. Even
combining a Ring with a Star or Tree topology, it is recommended that at least the Ring topology
network side be shut down.
A Ring topology can migrate to a Star topology before combining the networks without requiring
a plant shutdown. To migrate from a Ring topology to a Star topology, first determine which
switches are the root and backup switches. If a root and backup are not configured yet, configure
them first. A Star topology can be created by manipulating the uplink “Trunk” cables as shown in
Figure 5-8 below. If there are no extra 1Gb uplink ports, the 100Mb uplink ports of the B1/B2
switches can be used. Ideally, if two rings are to be combined, replace the final root and backup
root switches with switches that can support the required 1G ISL ports required for the network
topology so that all uplinks utilize 1Gb connections.
By using Figure 5-8 below and Figure 5-2 above (which combines two stars), two rings could be
converted into stars and then combined.

89
B0700AZ – Rev V 5. Combining Two or More Instances of The Foxboro Evo Control Networks

B1 B2 Root and Backup

B1 B2

Move cables one at a time

B1 B2

Added cables
Figure 5-8. Combining Ring Network Topologies

90
Appendix A. COMEX Fault
Handling on The Foxboro Evo
Control Network
This chapter provides information on Communication Executive (COMEX) fault handling in
the Foxboro Evo Control Network.

COMEX Layers
COMEX Applications Layer
This layer provides connectionless and exposed LLC communications services. Connectionless
messages are contained in unit data packets.
There are two types of connectionless messages - acknowledged and unacknowledged. For acknowl-
edged communications, there is a two-way acknowledgement (handshake), where the receiver of
the unit data packet replies with an ack1 packet to the initial sender, which then responds with an
ack2 packet.
No replies (acks) are returned for unacknowledged message types. However, these message packets
are sent twice, first out the primary port, and then 1 second later, out the secondary port. The
Foxboro multicasts are unacknowledged connectionless messages. The Foxboro “Broadcast” is
actually one of the Foxboro Multicasts.
Cable selection is based on an array in COMEX. The number of transmits is used as an index into
this table to select the cable. Seven (7) transmission attempts (Versatile Real-Time Executive
(VRTX) devices) are allowed, with the number of transmits starting at 1. Therefore, the first entry
in the array (index 0) is a filler and not used. The remaining entries indicate the cable selection as
follows: Primary, Primary, Secondary, Secondary, Primary, Primary, and Secondary. On the third
transmission attempt, a cable test is requested before attempting to send the message. When the
number of transmits exceeds the maximum (7 for VRTX devices), the message is flushed. For the
Foxboro Evo and I/A Series stations on either the Foxboro Evo Control Network and/or the I/A Series
software 7.x Control Network (Windows XP® or later workstations and Nucleus Plus devices), this
maximum is also 7.

Application Layer Protocol and Timers

A transmitted acknowledged connectionless Unit Data packet requires an Ack1 response from the
receiver. Upon receiving the Ack1 response, the initiator responds with an Ack2 packet.
A transmitted unacknowledged connectionless Unit Data packet is directed to the Primary cable,
and requires no response. Rather, after waiting 1 second, the packet is re-directed to the Second-
ary cable. (Since the Data Link Layer of the control network and the I/A Series 7.x Control Net-
work systems determines the active communications port, the preceding cable directions are
ignored.)

91
B0700AZ – Rev V Appendix A. COMEX Fault Handling on The Foxboro Evo Control Network

A reference delay is used to time the receipt of Ack1's and Ack2's and the duplicate transmission
of unacknowledged packets. This time delays are as follows:
♦ Round trip time delay - 1.01 seconds
This is a basic delay period for stations on the same Node, for which some other
delays are based. For stations on another Node on the same LAN, 1 is added to this
value. For stations on another LAN on the same Site, 2 is added to this value. Note
that the Site in the comms hierarchy was not implemented.
♦ Acknowledged UD packet transmitted (retransmit time-out) - 1 second time-out for
receipt of Ack1 response
Not receiving a response within the time-out period results in the UD packet being
re-transmitted, up to the limit of retries. This value is subject to ongoing optimization in
the Control Network devices, and may change without notice.
♦ Ack1 response sent - Time-out period is taken from the original acknowledged UD
packet (its retransmit time-out) and modified, for receiving the Ack2 response.
The time-out period is multiplied by the maximum number of connectionless retries
allowed and 1 added. Then, the round trip delay is added to the time - 1.01 seconds
for same node, 2.01 seconds for same LAN, and 3.01 seconds for same site. There-
fore, the reference delay is between 9.01 and 11.01 seconds, for VRTX stations.
(Because, the site hierarchy part of the communications system was not implemented, the
same LAN would be the furthest round trip delay - 10.01 seconds.) Not receiving the
Ack2 response is the same as if the Ack2 was received - resources are released.
♦ Unacknowledged UD packet transmitted - 1 second time-out.
Timer expiration results in sending duplicate unacknowledged UD packet on other
cable. This is the case because no response is expected that would stop the timer.
♦ Unacknowledged UD packet received
The time-out period is taken from the original unacknowledged UD packet and mul-
tiplied by 2. Then, the round trip delay is added to the time - 1.01 seconds for same
node, 2.01 seconds for same LAN, and 3.01 seconds for same site. Therefore, the ref-
erence delay is between 3.01 and 5.01 seconds. (Because, the site hierarchy part of the
communications system was not implemented, the same LAN would be the furthest round
trip delay - 4.01 seconds.) When the duplicate packet is received, or with timer expira-
tion, receive resources are released.

Transport Layer
This layer provides connected communications services. The protocol of this layer is based on a
reduced subset of what appears to be class 4, as defined in RFC 905, “ISO Transport Protocol Spec-
ification, ISO DP 8073”, dated April 1984. The message is contained in a data transfer packet
(DT). Connections are set up by sending a Connection Request packet (CR). The response is a
Connection Confirm packet (CC) to accept the connection, or a Disconnect Request (DR) to refuse
the connection. When the initiator receives an acceptance (CC packet), an Ack (AK) packet is sent
to acknowledge the connection. DT packets are acknowledged with an AK packet. In addition, if
either side of the connection has not sent a packet in a certain time-out period, an AK packet is
then sent as a “heartbeat” to show that the connection is still active. Disconnects are initiated with
a DR packet. The disconnect is accepted by replying with a Disconnect Confirm (DC) packet.

92
Appendix A. COMEX Fault Handling on The Foxboro Evo Control Network B0700AZ – Rev V

DT packets are sequenced and use a “window” controlling the number of outstanding DT pack-
ets before an AK is received. The sequence number starts at 0 and is incremented for successive
DT packets. The receiver of the DT packet responds with an AK, indicating the sequence number
of the next expected packet. If a DT packet is received in error, then the AK contains the sequence
number of that packet. A receive credit value is given in the CR, CC, and AK packets, indicating
the size of the “window” for the receiver. In effect, the transmitter can have no more than the
receive credit number of transmitted packets outstanding with the receiver.
When a connection is requested, (or any packet expecting an ack response) the initiator waits the
Retransmit Timer period for the response, before retransmitting the packet. When a connection
is established, DT packets or heartbeats (AK's) are sent every Window Timer period. A DT or
AK packet is expected to be received within the Inactivity Timer period, in order to maintain the
connection. When a DT packet is received, the receiver does not wait longer than the AK Timer
period before transmitting a response (AK).
Messages could be received in multiple data packets. This is called a multi-packet receive. The
packet indicates if it is the last packet of a transmission (EOT bit of the sequence number octet).
Multi-packets need to be linked into a single message before being delivered to IPC. In addition,
during multi-packet receives, the receive credit get boosted above normal and an AK set to change
the credits with the sender. With the last packet, the receive credit gets set back to normal, and an
AK is then sent to change the credit back to normal with the sender. (At the sender, it becomes his
transmit credit.)
When a connection exists, the messages to be transmitted are placed in the Wait Ack Queue
(WAKQ) to wait for their acknowledgment. Received packets (DTs or ACKs) that are out of
sequence with what is expected are handled according to this table:

Table A-1. Out of Sequence DT and Ack Packets

Received Packet Action Retransmit Timer Ack Timer

ACK seq < outstand- Acknowledged packets Restarted if any packets -
ing DT pkt's last seq. removed from WAKQ, on WAKQ acknowl-
if present. Available new edged and new ones
packets sent up to xmit sent. If WAKQ empty,
credit limit. timer stopped.
ACK seq same as last Ignored. No action. -
ACK seq received.
ACK seq > outstand- Out of sequence coun- No action. -
ing pkts last seq + 1 ter incremented. ACK
ignored.
DT seq < next Dumped. - Start timer if not
expected - 1. already running.
DT seq = next Dumped and ACK - (This packet was the
expected - 1 sent. last one acknowl-
edged and timer
should already be
stopped.)
DT seq > next Dumped. - No action.
expected

93
B0700AZ – Rev V Appendix A. COMEX Fault Handling on The Foxboro Evo Control Network

Transmissions expecting a response are attempted 8 times (7 retries), before the packet is dis-
carded. For the Foxboro Evo and I/A Series stations on either the Foxboro Evo Control Network and/or
the I/A Series software 7.x Control Network, this limit is 8 attempts for both Windows XP workstations
and Nucleus Plus devices (7 retries). Transmissions not expecting a response (AK and DC packets)
are only sent once. The cable selection is governed by an array. The number of retries is used as an
index into the array. Cables in this array are selected as follows: primary, primary, secondary, sec-
ondary, primary, secondary, primary, secondary. Packets expecting a response use this array. Pack-
ets not expecting a response (AK and DC), use another array. The result of using this array, is that
the cable is swapped between the primary and secondary, with every transmit. Because AK and
DC packets use private resources that are not released (these packets are created in the TL), the
transmit count keeps incrementing, so that these packets alternate cables.
The retry count is for an individual message (not a response) on a given connected channel. The
transmit count is only for responses being sent using the private resources. Individual messages are
retried. Responses (AK, DC) are not retried, because they do not get a response.
When the retry count is 2, a cable test is requested. When the retry count exceeds the maximum,
the message is flushed.

Transport Layer Protocol and Timers

The timers used by the Transport Layer are:
♦ Retransmit Timer - 0.5 seconds for VRTX devices (for the Foxboro Evo and
I/A Series stations on the Foxboro Evo Control Network and/or the I/A Series soft-
ware 7.x Control Networks. this value is 0.5 seconds for Nucleus Plus devices and 0.5
seconds for Windows XP or later workstations)
Maximum time allowed between sending a packet and receiving an AK for it. This
timer automatically restarts itself. Timer expiration causes a transmission reattempt of
the packets in the Wait Ack Queue, up to the retry limit. When outstanding packets
are AK'ed, this timer is stopped (and packets removed from the queue).
♦ Inactivity Timer - 10 seconds
Maximum time allowed to receive heartbeat AK's (or DT's). This is a one-shot timer.
It is restarted whenever a packet is received. At timer expiration, the connection is
aborted.
♦ Window Timer - 2 seconds for VRTX devices (for the Foxboro Evo and I/A Series sta-
tions on the Foxboro Evo Control Network and/or the I/A Series software 7.x Control
Networks, this value is 2 seconds for Nucleus Plus devices and two seconds for Win-
dows XP or later workstations) Maximum time allowed between sending heartbeat
AK's (or DT's)
This timer automatically restarts itself. It is also restarted whenever an AK or DT is
sent. At expiration, an AK packet is sent.
♦ AK Timer - 75 msecs
Maximum time allowed between the first DT received and transmitting its AK. This
is a one-shot timer. At expiration, an AK packet is sent.
Normally, when the number of received DT packets equals the limit, an AK packet is
sent. In this case, the timer provides a cap on the time between received data and its
AK transmission. The limit is 1.

94
Appendix A. COMEX Fault Handling on The Foxboro Evo Control Network B0700AZ – Rev V

When a connection is requested with a CR packet, a CC packet response is generated by the

receiving end. The Retransmit Timer is used to time the response. If the timer expires before get-
ting the response, the CR packet is resent, up to the maximum retries, before the packet and the
connection are aborted. If the protocol is successful, a connected channel is created. Then the
Inactivity Timer is used by both ends of the channel for receiving packets from the other end of
the channel. These packets can be either DT packets or Acks (DT acknowledgements or heart-
beats). If the Inactivity Timer expires, the connection is aborted.
With a connection established, and a DT packet sent, an Ack response is expected. The Retrans-
mit Timer is used to time the response. If the timer expires before getting the response, the DT
packet is re-sent, up to the maximum retries, before the packet and the connection are aborted.
With a connection established, and a DR packet sent, a DC response is expected. The Retransmit
Timer is used to time the response. If the timer expires before getting the response, the DR packet
is re-sent, up to the maximum retries, before the packet and the connection are aborted.
An aborted connection causes a DR packet to be sent. The expected response and timers are the
same as previously described. The difference is that instead of IPC requesting the disconnect, the
request is initiated by the Transport Layer.

Network Layer
The Network Layer provides routing to the Nodebus, to another Nodebus (through the LAN
Interface), and back into the box (upper layers).

Operation
There are no states in the Network Layer operation, because no protocol is performed. The pri-
mary responsibility of this layer is routing the packets. Packets are routed to the local node, to the
LAN Interface in VRTX devices for other nodes, and back to the upper layers in the same station.
In the control network devices, off-node packets are routed to a specific Address Translation Sta-
tion (ATS), rather than to a LAN Interface.
Point-to-point packets are routed to the upper layers when the destination NSAP (site, LAN, and
node ID's) is the same as the source NSAP. The destination and source are on the same station
and the packet is routed to the upper layers as if it was a received packet.
Multicast packets are sent out the station. They are also routed to the upper layers of the source
station, if the Reroute bit (in the packet) is set and the multicast group is active in the station.

Logical Link Control Layer

The implementation of this layer is based on IEEE 802.2, class 1 (Type 1 Operation only), using
only unnumbered UI commands (information). No other U commands are supported. There-
fore, the poll/final bit is not used (it is not valid for UI commands).

Transmit Operation
There are no states used in an LLC transmit operation. The LLC header is simply added to the
packet and it is passed on to the MAC layer.

95
B0700AZ – Rev V Appendix A. COMEX Fault Handling on The Foxboro Evo Control Network

Receive Operation
The LLC distributes received packets according to whether they are normal data packets, diagnos-
tic packets, or exposed LLC packets. Several additional packet types are defined for the control
network devices.
The routing of connected and connectionless packets is based on the Network Layer destination
LSAP (Link Service Access Point). These packets specify network routing (Network Layer LSAP),
providing for routing by the destination LLC Layer to the destination Network Layer.
For exposed LLC packets, 2 LSAPs are supported. The Application Layer 802.1 individual LSAP is
used for downloading station images, and the Application Layer 802.1 group LSAP is used for
cable test messages (diagnostics). These packets are distributed directly to the Application Layer.
The diagnostic packet used for a cable test is sent by NFD with a Station Manager destination
LSAP, via exposed llc (through IPC and the Application Layer). Received Station Manager packets
are passed by the LLC Layer directly to SMD (station manager diagnostics), which echoes them
back directly through the LLC Layer, as an Application Layer 802.1 group destination LSAP. These
are then passed by the receiver LLC Layer directly to the Application Layer (and thus, back to
NFD).
The control network devices provide for additional destination LSAPs:
♦ NFD PROXY for the control network to Nodebus NFD cable test proxy packet.
♦ MAC QUERY for a Mac Query packet.
(Other LSAPs are used by the control network communications drivers and ATS devices for vali-
dating network integrity.)

MAC Layer
The MAC layer is designed for the individual hardware for which it interfaces.

96
Appendix B. The Foxboro Evo
Network Fault Handling
This chapter provides information on fault handling in the Foxboro Evo Control Network.
Fault handling on the control network is handled on a per station basis. This fault handling pro-
cess is a proprietary Schneider Electric patented process. This description applies to dual port
COMEX stations which have two roles for their ports, including workstations, FCP, ZCP, and
ATS stations:
♦ An active port based on the system address for that station.
♦ A standby port that only is used for testing with a different MAC address until it is
determined that the active port is not functioning correctly.
COMEX implements seven retries on the active port spaced over 3.5 seconds for connected mes-
sages. Connectionless acknowledged messages perform seven retries over seven seconds. COMEX
relies on lower level mechanisms to select the best possible port as the active port. The port select-
ing behavior of the stations is as follows.

LINK
The first line of defense is the Link Integrity Signal. This signal is derived by the PHY Interface
hardware and is indicative of the presence of “IDLE” symbols received. If a port does not have
“LINK”, it cannot send or receive. If the Link signal goes inactive, the port is not usable and the
driver switches the station address on the module to the other port if it does have a “LINK” sig-
nal. Typically switches stop sending if they detect no activity on a port (to conserve power) so link
becomes a bi-directional indication. Loss of LINK switchover is indicated to the customer as
PORT A (or B) detected failure in the smon_log and SMDH.
Causes of loss of link:
♦ Switch power down
♦ Switch detected failure
♦ Cable detected failure of either the transmit or receive fiber
♦ Dirty cable
♦ Module hardware detected failure

“PORT TEST” Packets

If both LINK signals are active, two “PORT TEST” packets are sent by the driver in control pro-
cessors, Address Translation Stations (ATS) and workstations at these rates:
♦ For workstations and CPs, the “PORT TEST” is run every 300 milliseconds.
♦ Both the Primary and Backup ATS modules of a pair run the “PORT TEST”
individually, every 300 milliseconds for the Primary module, and every
120 milliseconds for the Backup.

97
B0700AZ – Rev V Appendix B. The Foxboro Evo Network Fault Handling

One “PORT TEST” packet is sent from the “A” port to the “B” port and one “PORT TEST”
packet from the “B” to the “A”. In the body of the packet is the text “Prim Port Test” and “Alt Port
Test”. Reception of these packets in both directions indicate that both ports have equal connectiv-
ity to the rest of the network. As long as “LINK” is good and the “PORT TEST” packets succeed,
no port switching occurs.
A single port test packet detected failure is flagged and the Excessive Collision Counter is incre-
mented but no switchover occurs until two “PORT TEST” in a row have experienced a detected
failure. The definition of a detected “PORT TEST” failure is when two “PORT TEST” packets,
in a row, are lost or missed, in either direction.
If two successive “PORT TEST” tests are lost or missed, due to the inability to receive both pack-
ets the module initiates the “PING” test. The PING test will try to find the best solution to get to
its devices. The “PORT TEST” packets cease for 400 milliseconds while the “PING” test
attempts to detect the best way to overcome a loss of peer-to-peer communication. After the
llc_ping test runs the module goes back to sending port tests until the network is healthy.
Potential causes of a “PORT TEST” loss of communication are as follows:
♦ Switch detected failure causing islanded switches
♦ Message storm substantially interfering with normal communications
♦ Internal switch detected failure of the switch connected to the “A” port or the “B”
port
♦ Module hardware detected failure
♦ Broken or damaged cable.

“LLC_PING” Test
These tests are implemented on both control processors, ATSes and workstations (with slightly
different behavior). Their primary purpose is to place active communications on the port with the
greatest network connectivity to the system in the event of a switch becoming islanded from the
network; when both ISL ports on an edge switch go offline this will cause the switch to become
isolated from the remaining control network. The LLC_Ping test only runs when the above
“PORT TEST” detects a loss of its peer-to-peer communications, and uses “PING” packets and
their responses to identify the best port to help ensure connectivity to the rest of the stations on
the control network.
This is NOT the standard IP “PING” packet; it is a COMEX llc_ping type (DSAP = 0x0A,
SSAP = 0x0A). Only COMEX stations send this message to help ensure that the targeted station
is running the software that replies to this “PING”. The packet indicates that this is an llc_ping
request and is sent on both the “A” and “B” ports. When any COMEX station receives this
request it responds with a LLC_PING_response packet with the same format (DSAP = 0x0A,
SSAP = 0x0A) to the senders MAC address. The station who initiated the llc_ping message
then tallies the responses and makes a decision whether to switch ports or not.

98
Appendix B. The Foxboro Evo Network Fault Handling B0700AZ – Rev V

MTK “Ping” Test

For controllers and ATS stations, a two tiered test is run. First a “PING” packet is sent to the
workstation identified as the Master Time Keeper (MTK). Having the controllers finding a com-
mon path to this workstation and selecting it for active communications results in the controllers
being able to communicate with each other. Active communications is selected to run on the port
which receives the packet from the MTK workstation, correcting any islanding network devices.
Workstations do not run this test. Alternatively, this test is referred to as the “Follow the Master
Timer Keeper” algorithm as this text is placed in the SMON log when the controllers implement
a port switch to align with the path to the MTK.

Ping Voting Test

In workstations (or in controllers if the MTK does not respond on either bus) the Ping Voting test
verifies the path to up to seven stations that have previously been in communication with this
controller. It is used to allow the module to select the port with the highest connectivity with its
most recent COMEX partners based on a most recently received table.
1. IF all responses are received on both cables, this is considered a “Good” case and no
switchover is performed and no messages are sent.
2. IF more responses (for example, four responses on Alternate (Backup) and two on
Primary) are received on the Alternate port, a port switch is performed; no Hot-
Remarry should occur on fault-tolerant stations. This port switch places the Alternate
as the Primary port and re-assigns the MAC addresses of the ports. A broadcast is sent
to update all switches with the new MAC address location. A message is sent to the
alarm printer and the smon_log if enabled.
PING Test Sent = 7 Replies = Pri 2 Alt 4 new cable = B (or A)

Notifications
A workstation does not currently send any messages to the alarm printer/SMON log.
Workstations run in promiscuous mode. Upon a Primary port swap, the NIC is not repro-
grammed but the software does use the Primary port MAC address and IP on the Backup port
when a swap occurs.

Workstation Address Qualification

For workstations, the only addresses qualified to participate in the test are Foxboro Evo worksta-
tion MAC addresses starting in “00 00 6C” which includes FCP, ZCP, and ATS. This allows the
workstations to “follow the controllers”, helping to ensure that all participants in the control net-
work make the same decision and thus helping to prevent multiple islands from being formed.
IF an equal number of responses or more responses are received on the Primary port, no switch-
ing is performed and a “PORT FAILURE” message for the Alternate port is sent to the alarm
printer.

99
B0700AZ – Rev V Appendix B. The Foxboro Evo Network Fault Handling

NOTE
It is important to note that this level of testing only occurs when multiple faults
cause islanding of stations within the control network. All single faults (such as a
link detected failure or single uplink path breakage) and many multiple faults (such
as powering down an edge switch which causes 24 ports to lose their link) are han-
dled instantly by the control network architecture and Foxboro Evo software.

ZCP-FCM Communications
Communications between the ZCP and the FCM use raw IP packets. The ZCP sends an
alternating request/reply transaction on each Ethernet cable to talk to the FCM pair at all times.
On discovery of any detected failure, the field connection has its reliability score reduced. The
ZCP uses the more reliable cable exclusively while background mechanisms try to rehabilitate the
malfunctioning cable.
The ZCP maintains a quality of connection for each FCM separately. If one FCM has a loss of
communication on channel A, that FCM prefers to use channel B. All others would still use A or
B normally.
There are no retries. All Ethernet, IP, and port addresses are unique to the particular network.

NOTE
If the user has required the ZCP to use the “A” Ethernet cable and the “A” cable has
in fact lost its peer-to-peer communications, the ZCP blindly follows the require-
ment to use the “A” cable even though it does not work. This is done to aid debug-
ging.

NOTE
Two FCMs can have the same addresses if they are on separate networks; for exam-
ple, behind different ZCPs and not on the control network.

There is no LLC3 protocol on the I/O side between the ZCP and the FCM.
ZCP and FCM communication behaves as discussed below in the following cases:
Case 1: The ZCP does not receive a response on the primary port to an FCM and/or
switch.
Behavior: The ZCP retains a health score on each of its connections. It maintains com-
munications on the “A” or “B” bus, whichever is more healthy. However, the FCM is also
trying to recover the bad cable, and is sending health packets on the bad cable. A success-
fully delivered packet raises the ZCP’s health score, so the bad cable’s health score may
increase. Multiple successes raise the cable’s health score to completely good. When the
score is equal that of the other cable, the ZCP starts to alternate between cables again for
its communication to the FCM.
Case 2: The ZCP communicates with several FCMs and does not receive a response on a
port.

100
Appendix B. The Foxboro Evo Network Fault Handling B0700AZ – Rev V

Behavior: The ZCP maintains a quality of connection for each FCM separately. If one
FCM has a loss of communications on the “A” bus, that FCM switches to the “B” bus.
The other FCMs would still use “A” or “B” normally. A message indicating this change
should be generated by the ZCP on the FCM's behalf.

DIAGNOSTIC Information
Diagnosing network detected failures on the control network is complicated but here is some gen-
eral information:
1. PORT FAILURE MESSAGE
a. Most likely caused by loss of the LINK signal.
b. Most likely caused by a cable problem or dirty (very common) Fiber connections.
c. Loss of link may be reported by both the switch and the station “PORT FAIL-
URE” message and the SMDH port field.
d. “PORT FAILURE” is also indicated by a loss of its peer-to-peer communications
from the Primary port to the Alternate port. The Alternate port displays the
“PORT FAILURE”.
2. FT LINK
a. On FT station both stations must have a common link on at least one cable to
stay married.
b. If the Primary loses both links it reboots and the Shadow becomes Primary.
c. Modules do not marry without at least one common link. If no common link is
found a module goes RED/GREEN.
3. ZCP LINK
a. For ZCPs loss of link is handled in the same fashion as detected failure on the
Application network.
b. For ZCP I/O functionality as of 8.2 there must be a path from the “A” port of the
ZCP to the “A” port of the FCM or the “B” port to “B” port in order for the ZCP
to maintain comms. The ZCP cannot talk from the “A” port to the FCM “B” port
MAC address. This means that cross-wired systems have multiple points that can
cause a loss of communications between the CP and FCM as follows:
♦ ZCP port “A” to Switch 1 port 1
♦ ZCP port “B” to Switch 2 port 1
♦ FCM port “A” to Switch 2 port 2
♦ FCM port “B” to Switch 1 port 2
♦ Switch 1 port 3 to Switch 2 port 3
If this configuration was built the ZCP to FCM communications would work fine
with the hardware functioning as expected. Any of these would cause loss of I/O
communications:
♦ Switch 1 -power down or loss of communications
♦ Switch 2 -power down or loss of communications
♦ Switch 1 port 3 loss of link or switch 2 port 3 loss of link

101
B0700AZ – Rev V Appendix B. The Foxboro Evo Network Fault Handling

♦Cross Cabling of Switch 1 port 3 to Switch 2 port 3

4. System Monitor counters
a. MAC resets indicate either Hot-Remarries or Port link loss.
b. Excessive Collisions indicate either continuous (evenly incrementing approxi-
mately 1 per second) or intermittent problems on the control network (incre-
menting at less than 1 per second) causing “A” to “B” detected failures.
c. At the present time, workstations do not indicate “A” to “B” port test detected
failures unless a port switch occurs.

102
Index
C Null hub 15, 59
Cable
fiber optic 60 P
specifications 59 Prefabricated cables 59
twisted-pair 59
Cabling S
fiber optic 63 Single mode fiber. See Fiber optic cable, single
Cleaning mode
fiber optic cable 80 Site planning 19
SMDH 76
E System Management displays 76
Ethernet switches T
connecting 69
Topology, network 34
indicators 77, 78, 80 Troubleshooting 75
Twisted-pair cable 59
F
FCP280 copper adapter 65 U
Fiber optic cable 15, 60 Uplink port 70
cleaning 80
handling 78 V
Fiber optic cabling 63 VLANs 5, 19, 26
G W
Gigabit Ethernet uplink ports 70 Workstation copper NIC card 65
H
Handling
Fiber optic cable 78

I
I/O network 7
design rules 34
illustration 9
topology configuration 55
Indicators
Ethernet switches 77, 78, 80
media converter 77
IOC (I/O Controller) 7

M
Multimode fiber. See Fiber optic cable,
multimode

N
Network components connections 69
Network topology 34

103
Schneider Electric Systems USA, Inc.
38 Neponset Avenue
Foxborough, MA 02035-2037
United States of America
www.schneider-electric.com

Global Customer Support

Inside US: 1-866-746-6477
Outside US: 1-508-549-2424
https://pasupport.schneider-electric.com