User interfaces and naming conventions

Related topics
“About Microsoft Windows Server 2008, Windows Server 2012, and Windows 7 user interfaces” on page
12
“Local area connection and NIC names” on page 12
“Standard naming conventions for NICs” on page 12
“FTE community naming restrictions” on page 13
2.1.1 About Microsoft Windows Server 2008, Windows Server 2012, and
Windows 7 user interfaces
Honeywell FTE Mux driver for Experion R4xx is installed on a node that uses only Windows Server 2008,
Windows Server 2012 or Windows 7 as its operating system.
2.1.2 Local area connection and NIC names
Local area connection and NIC names can be different than the examples used throughout the guide.
These
names vary depending upon when the NIC is installed, how the operating system detects the new
hardware, and
whether or not the connections are renamed using the conventions recommended in this guide.
2.1.3 Standard naming conventions for NICs
The terms A - Yellow and B - Green are used consistently throughout this guide to describe the Network
Interface Card (NIC) connections and switches used in an FTE network. Although not mandatory,
Honeywell
recommends this naming convention to make it easier to identify each network connection and verify if it
is
connected to the appropriate switch. The A- Yellow network connection is connected to the switch in the
“Yellow” network tree. The following table describes these terms and how they apply to the FTE network.
Term Component Used for describing the ... Example
A - Yellow NIC NICs primary port which usually has
the lowest MAC address to which the
Yellow cable is connected.
FTE south plant A – Yellow
Switch Switch to which all the primary
adapter ports are connected using
Yellow cable.
Switch A (Yellow tree)
Switch tree Collection of all the A switches.
Switches to which all the Yellow
cables are connected.
Yellow network tree
B - Green NIC NICs secondary port which usually
has the next highest MAC address to
which the Green cable is connected.
FTE south plant B – Green
Switch Switch to which all the secondary
adapter ports are connected using
Green cable.
Switch B (Green tree)
Switch tree Collection of all the B switches.
Switches to which all the Green
cables are connected.
Green network tree
2 INTRODUCTION
12 www.honeywell.com
2.1.4 FTE community naming restrictions
FTE community names must not be longer than 244 characters and must not contain any of the special
characters listed in the following table.
Key on keyboard Description
Tab
\ Back slash
/ Forward slash
: Colon
* Asterisk
? Question mark
< Less than
> Greater than
| Pipe
2 INTRODUCTION
13

2.2 Before you begin

Before installing FTE, you must have knowledge of FTE requirements and configuration rules in addition
to
any specific site and networking requirements. Honeywell recommends you review the following
documents
before installing FTE.
• Fault Tolerant Ethernet (FTE) Specification and Technical Data.
• Fault Tolerant Ethernet (FTE) Overview and Implementation Guide.
• Windows Domain and Workgroup Implementation Guide
• For planning information, refer to Windows Domain and Workgroup Planning Guide
• For operation system migration information, refer the appropriate operating system-specific
implementation
guide Windows Domain Implementation Guide for Windows Server 2008 R2
• Windows Domain Implementation Guide for Windows Server 2012
• Planning, Installation, and Service Guide, for the specific platform on which FTE is being installed.
• General Release Software Change Notice (SCN), which provides last-minute changes, special
instructions,
and workarounds.
Related topics
“FTE network requirements” on page 14
“Installation variations for FTE” on page 14
“FTE node types” on page 15
2.2.1 FTE network requirements
Before installing any FTE nodes, it is assumed you have performed the following tasks according to the
FTE
Overview and Implementation Guide.
• Established an ethernet structure for your FTE network.
• Properly installed and configured Honeywell approved Cisco ethernet switches according to Honeywell
best
practices
2.2.2 Installation variations for FTE
Procedures for implementing a Fault Tolerant Ethernet network and FTE nodes vary depending upon the
following factors.
• Specific components ordered for the FTE system
• Migrating existing nodes to FTE or installing new FTE nodes
• Node type
• Operating system
• Network configuration (level 1 and level 2)
• Requested level of Honeywell support.
– Customer installs Honeywell-qualified FTE components only
– Honeywell installs Honeywell-qualified FTE components only
– Honeywell certifies customer equipment for use with FTE
2 INTRODUCTION
14 www.honeywell.com
2.2.3 FTE node types
FTE can be installed on the following types of nodes.
• Experion server (ESV)
• Experion server TPS (ESV-T)
• Experion Flex (ES-F)
• Experion Console Extension station (ES-CE)
• Experion Application Control Environment (ACE)
• Experion Console station (ES-C) or Experion Console station with TPS (ES-T)
• Experion Application Control Environment TPS (ACET)
• Experion Highway Gateway (EHG)
• Experion C200 Simulation Control Environment (SIM-C200)
• Experion Application server (EAS)
• Experion Application node
• Domain controller
• Simulation Control Environment (SCE)
Attention
The Honeywell FTE Adapter network Identification may appear as “unidentified network", for systems in a
workgroup with Windows Server 2008 and Windows 7 nodes. This does not indicate a problem with the network, but
merely identifies that the node cannot establish an internet connection. Nodes that are joined to a domain illustrate
the
domain name as the identified network.
With Experion, the FTE driver can be installed on a Windows 7 64-bit operating system. The FTE driver can be
installed on Windows 7 32-bit operating system only in Experion R400.x.
2 INTRODUCTION
15

2.3 Overview of Honeywell FTE Mux-IM protocol driver

With Experion R4XX, the configuration and behavior of Honeywell FTE on the network and operating
system
has changed. The FTE is assigned one IP address for configuration. This reduces the number of IP
addresses
required for each computer.
The FTE Mux-IM protocol driver is backward compatible with the previous Experion releases, enabling
visibility during migrations and upgrades. It implies that the interaction between the nodes in the
community is
backward compatible. The previous versions of FTE continue to be configured as per that version’s
Installation
and Service Guide.
2 INTRODUCTION
16 www.honeywell.com

2.4 Honeywell FTE Mux-IM Protocol Driver Properties

interface
The Honeywell FTE Mux-IM Protocol Driver Properties interface provides operational status, driver
details,
and configuration option for the FTE Mux intermediate protocol driver. The user interface includes the
following tabs.
• Version tab
• Configure tab
• View Logs tab
• FTE Community Status tab
Related topics
“Version tab” on page 17
“Configure tab” on page 18
“View Logs tab” on page 18
“FTE Community Status tab” on page 21
2.4.1 Version tab
The Version tab displays the details of Honeywell FTE Mux IM Protocol driver, Configuration Utility, and
WMI Provider. Version information is extracted from a version resource linked into the executables.
2 INTRODUCTION
17
2.4.2 Configure tab
The Configuration tab of the Honeywell FTE Mux-IM Protocol Driver Properties interface displays the
current
virtual and physical adapters and the binding relationship between physical adapters and the Honeywell
FTE
adapter. Both the adapters (virtual and physical) are displayed in a tree. Properties for each adapter in
the tree
may be viewed by selecting the desired adapter either in the tree or from a list box that lists all physical
and
Honeywell FTE adapters. Properties may be read-only (example: MAC ID) or may be editable (example:
Device Index).
Adapters that are not assigned (bound) to the Honeywell FTE adapters display information specific to that
physical adapter. Adapters are assigned to Honeywell FTE adapters by dragging and dropping the
physical
adapter onto the Honeywell FTE adapter tree. Refer to the section “Operating and servicing FTE” on
page 79
for detailed information on how to drag and drop the physical adapters onto the Honeywell FTE adapters.
2.4.3 View Logs tab
The View Logs tab displays the FTE, Control Firewall, and Non-FTE node log files. These log files are
written
every two minutes by the FTE Mux-IM Protocol Driver. You can save the image of the log files to a
defined file
location.
The following three options are available in the View Logs tab.
• FTE Log: lists the FTE nodes and provides information about the nodes. The information includes the
connection status and details for every node seen by the local computer’s FTE Community. The following
image illustrates the FTE Log.
2 INTRODUCTION
18 www.honeywell.com
• Control Firewall Log: lists all of the Honeywell CF9 devices active on the FTE network, with
operational
details such as firmware and hardware revisions for each device seen by FTE on the network. This log
also
lists the Honeywell Modbus Firewalls that are connected on the network. The following image illustrates
the
Control Firewall Log.
2 INTRODUCTION
19
• Non-FTE Node Log: lists all the nodes that are not considered to be FTE community nodes. This list
may
include other computers or ethernet switches and other devices that are not running Honeywell’s FTE
algorithm. The following image illustrates the Non-FTE Node Log.
2 INTRODUCTION
20 www.honeywell.com
2.4.4 FTE Community Status tab
The FTE Community Status tab hosts the FTE auxiliary display. The System Management Display,
Experion
Station detail display, and the FTE and Heartbeat Node Status Display hosts this same status viewer. It is
preferred to use one of the other methods to view the FTE Community Status.
2 INTRODUCTION
21
2 INTRODUCTION
22 www.honeywell.com
3 FTE Installation and Configuration
checklists
Related topics
“FTE installation scenarios” on page 24
“Configure FTE on a factory-configured Experion node” on page 25
“Install and configure FTE with an Experion system” on page 26
“Install and configure FTE on existing Experion nodes” on page 28
“Convert a single ethernet supervisory node to an FTE node” on page 30
“Convert a dual supervisory ethernet node to an FTE node” on page 32
“Install and configure FTE using Installation Builder” on page 34
“Install and configure FTE on domain controllers” on page 35
23

3.1 FTE installation scenarios

This section explains the items and checklists required to configure and install the different FTE
installation
scenarios for Experion release 4xx.x. If the network type must be changed from the prior Experion
release 3xx ,
the network type and configuration must be reconfigured before the start of migration to the Experion
4xx.x
installation. Since the operating systems must be completely reinstalled with either Windows 7 or
Windows
Server 2008, it is recommended to change the network before migration to preserve the database and
history.
Refer to the FTE Installation and Service Guide for R3xx network conversion scenarios.
The following table assumes that all nodes are already setup for FTE installation and the hardware is
configured
to support FTE.
Scenario What you need
“Configure FTE on a factory-configured Experion node”
on page 25
Getting started with Experion Guide, “Configuring Experion
nodes after factory Installation” section.
“Install and configure FTE with an Experion system” on
page 26
• Experion PKS Software Installation User’s Guide
• Experion PKS System Initialization media
• Experion PKS Installation media
• Experion documentation media
• Experion PKS Support Software media
“Install and configure FTE on existing Experion nodes” on
page 28
• Experion PKS Software Installation User’s Guide
• Experion PKS Installation media
• Experion PKS Support Software media
“Convert a single ethernet supervisory node to an FTE
node” on page 30
FTE Installation and Service Guide for R3xx network
conversion scenario
“Convert a dual supervisory ethernet node to an FTE
node” on page 32
FTE Installation and Service Guide for R3xx network
conversion scenario
“Install and configure FTE using Installation Builder” on
page 34
Installation Builder User Guide (optional)
“Install and configure FTE on domain controllers” on
page 35
• Any one of the following as per your requirement.
– Root or peer Domain Controller running Windows
Server 2003
– Root, peer or read-only Domain Controller running
Windows Server 2008
– Root, peer or read-only Domain Controller running
Windows Server 2012
• Experion PKS Software Installation User’s Guide
• Experion PKS System Initialization media
• Experion PKS Installation media
• Experion PKS Support Software media
3 FTE INSTALLATION AND CONFIGURATION CHECKLISTS
24 www.honeywell.com

3.2 Configure FTE on a factory-configured Experion

node
Factory configured FTE nodes are those in which the Experion software is loaded, FTE NIC is installed
and the
FTE network ports are configured.
Prerequisites
Perform all of the tasks required in the Getting Started with Experion Guide including the ANCIM files
generated by the node definition tool.
Considerations
For a factory installed node do not power up the computer until you are ready to completely configure the
computer. Powering up the computer prompts you for information about your system.
Checklist
After performing each procedure, return to the checklist to reference the next procedure.
Task Status
Before performing any operations on the factory-configured Experion node, refer to
the topic “Configuring Experion nodes after factory Installation” in Getting started
with Experion Guide.
“Configure/verify FTE Mux-IM protocol driver properties” on page 66.
“Configure the Honeywell FTE adapter” on page 71.
“Connect network cables to switches” on page 76.
“Verify the Honeywell FTE driver operation” on page 72.
3 FTE INSTALLATION AND CONFIGURATION CHECKLISTS
25

3.3 Install and configure FTE with an Experion system

If you are installing FTE with an Experion system, refer to the “Configuring FTE device index (only for
Experion system running with FTE)” section of the Experion PKS Software Installation User’s Guide. Use
this
section to perform post-installation configuration tasks.
Prerequisites
The following media and documents are required.
• Experion PKS Software Installation User’s Guide for the release being installed.
• Experion migration guide for the release being installed.
• Experion PKS System Initialization media.
• Experion PKS Installation media.
• Experion PKS Support Software media.
• Experion documentation media.
Considerations
If FTE is chosen as the network type when installing Experion system, FTE software is installed
automatically
and you are prompted for configuration information. Once the Experion system installation is completed,
the
FTE configuration must be verified for its operation.
During the initialization steps ensure FTE is selected for the network type and the NIC- FTE Yellow is
configured with at least an IP address, a subnet mask, and a default gateway. This must be performed
when
selecting the installation parameters for a clean operating system installation on the Network and Input/
Output Device Configuration dialog box as illustrated in the following image.
3 FTE INSTALLATION AND CONFIGURATION CHECKLISTS
26 www.honeywell.com
Checklist
Task Status
To install the operating system and Experion application software, refer to the section
“Perform a clean Experion installation” in the Experion PKS Software Installation
User’s Guide.
If you are migrating an existing FTE node from R3xx, migrate the Experion PKS node
with FTE, refer to the appropriate Experion migration guide for migration instructions.
To verify the FTE operation, refer to section “Configure/verify FTE Mux-IM protocol
driver properties” on page 66
“Configure the Honeywell FTE adapter” on page 71.
Attention
This is only necessary to verify the IP address
“Connect network cables to switches” on page 76.
“Verify the Honeywell FTE driver operation” on page 72
3 FTE INSTALLATION AND CONFIGURATION CHECKLISTS