Instructions To Disable

NICs
Positively identifying which physical NIC port is associated with the network connection allows you
to rename the connections using an FTE naming convention. The FTE naming convention makes
it easier for you to verify proper operation of the FTE. In addition, refer to Standard naming
conventions for NICs.
l Identify FTE NIC ports
7.2.1 Identify FTE NIC ports

This procedure is not required if you are installing FTE on a factory configured Experion node or
- 59 -
Chapter 7 - Configure FTE
you are installing from the Experion PKS System Initialization media, which names and configures
the NIC ports.
1. Perform the following:
Click Start > Windows System > Control panel > Network and Internet > Network and Sharing
Center > Change adapter settings.
The Network Connections window appears.
2. Disconnect the Yellow network cable from the NIC port.
ATTENTION
In this example, Local Area Connection is associated with the adapter A port.
3. Right-click the Local Area Connection associated with the Network cable unplugged NIC port
and rename it using the following convention.
l FTE Community Name A – Yellow
Where Community Name is a descriptive name that does not contain special characters or
exceed 244 characters.
l FTE South Plant A – Yellow is used in the following example.
4. Reconnect the A - Yellow network cable to the NIC A port.

5. Right-click the unnamed Local Area Connection and rename it using the following convention.
l FTE Community Name B – Green
Where Community Name is a descriptive name that does not contain special characters or
exceed 244 characters.
l FTE South Plant B – Green is used in the following example.
7.3 Configure FTE network connections

If FTE is chosen as the network type when installing Experion, it is automatically installed. Use the
procedures in this section to manually configure network connections.
Use the following procedure to manually configure the network connection to support FTE
installation. For new Experion systems, all these settings are configured by the Experion
application installation routine. If the Experion PKS System Initialization media is used for
installing, all the items are automatically configured. Ensure you use this procedure before
installing FTE on a non-Honeywell supported platform to be installed with FTE such as a domain
controller or an OPC client node.
Use this procedure to verify that the physical settings have not been modified for changes in the
physical adapter properties such as new adapter driver installation.
l Configure physical network connections
l Configure the Honeywell FTE adapter
- 60 -
7.3.1 Configure physical network connections
Perform the following steps to configure the physical network connections.
2. Right-click the A - Yellow network connection and choose Properties.
The User Account Control dialog box is displayed.
3. Click Continue.
The Yellow Adapter Properties dialog box is displayed.
4. In the Networking tab, select Configure.
5. Perform the following steps in the Advanced tab and Link Speed tab, depending upon your
adapter.
l Broadcom adapter — Advanced tab
o IPv4 Checksum Offload and ensure the value is set to Rx & Tx Enabled.
o Jumbo MTU and verify/change the value to 1500.
o Large Send Offload v2 (IPv4) and verify/change the value to Disabled.
o Receive Side Scaling verify/change the value to Disabled.
o Link Speed & Duplex and verify/change the value to 100Mb full.
l Intel adapter — Advanced tab
o Jumbo Packet verify/change the value to Disabled.

o Large Send Offload (IPv4) verify/change the value to Disabled.
o Large Send Offload (IPv6) verify/change the value to Disabled.
o Receive Side Scaling verify/change the value to Disabled.
l Intel adapter — Link Speed tab
o Link Speed Tab and verify/change the value to 100Mbps/Full Duplex.

6. Click OK.
7. Repeat the above steps for the B - Green Adapter.
7.3.2 Configure the Honeywell FTE adapter
Use this procedure to manually configure the settings for the Honeywell FTE adapter, which the
system uses as its primary network connection. FTE no longer requires individual IP addresses to
be assigned to the Yellow and Green connections. The Honeywell FTE adapter uses the settings
that are assigned to the Yellow adapter at the time of FTE installation.
If the FTE installation was performed initially by factory-mode installation, this procedure is
required to set the IP address settings for the computer’s installed environment.
- 61 -
ATTENTION
If the Honeywell FTE adapter must be unbound to the physical Yellow and Green adapters,
without using a Honeywell installation or upgrade procedure, then the IP settings must be
applied to the Yellow adapter. Apply the IP settings using the procedure Verify/set NIC
adapter TCP/IPV4 properties if network connections are required while the Yellow adapter is
unbound from the Honeywell FTE adapter.
2. Right-click Honeywell FTE Adapter and choose Properties.
The Honeywell FTE Adapter Properties dialog box is displayed.
3. In the Networking tab, select Internet Protocol Version 4(TCP/IPv4) and click Properties.
The Internet Protocol Version 4 (TCP/IPV4) Properties dialog box is displayed.
4. Set the IP address, Subnet mask and Default gateway assigned for this node.
If required, set the DNS servers for this node.
5. Click OK and then click Close.
The Honeywell FTE adapter settings are now configured.
7.4 Verify the Honeywell FTE driver operation
Use this procedure to verify whether FTE is fully functioning on the node.
2. Verify the Honeywell adapter settings, select Honeywell FTE Mux-IM Protocol Driver, and then
choose Properties.
The Honeywell FTE Mux-IM Protocol Driver Properties dialog box is displayed.
3. Click the Configure tab and verify whether the settings are correct. View the FTE Network Logs
for the local node.
- 62 -
4. Select the View Logs tab and then click the FTE Log option to view the log.
5. Verify that the first node listed under FTE node list is the local node and the settings are as
expected.
6. Click the FTE Community Status tab and verify if the node is in the status list with all paths
listed as OK.
7. Click the Version tab and verify whether the version matches the node which was upgraded to
or installed as per the appropriate General Release Software Change Notice (SCN) for the
release.
8. Click Cancel and then click Close.
7.5 Configure FTE using the Installation Builder
l About Master definitions and FTE
l Considerations
l Prerequisites
l Download FTE-configured master definition
7.5.1 About Master definitions and FTE

If you create a Master definition in which you define all the FTE options, you can use it to configure
your Experion FTE node. Essentially, you download the Master definition that contains all the FTE
configuration options to the FTE node. Refer to the Installation Builder User Guide for information
on using the tool and creating a Master definition.
- 63 -
7.5.2 Considerations
l You can only perform a download when the Installation Builder is running in the online mode
and is connected to the IDB.
l When you perform a download, the integrity of the master definition is validated, and if there
are errors, you are allowed to continue.

7.5.3 Prerequisites
Before using this procedure ensure that.
l You are logged on with an account that has administrator privileges.
l You launched the Installation Builder in online mode.
l The node being updated with the master definition has Experion R301 or later software
installed.
7.5.4 Download FTE-configured master definition
Use this procedure to download the Master definition containing the correct FTE options to the
FTE node.
1. In Installation Builder network tree view, find the computer node on which the FTE options are
to be configured.
2. Select the Master Definition under the computer node in the network tree.
3. Right-click the Master Definition and choose File > Download or click toolbar.
A confirmation message is displayed.
4. Click Yes.
5. The tool verifies the target node is the same type defined in the node definition and validates
the integrity of the values. If it detects any errors, an Online Validation Errors message is
displayed.
Click OK to return to the Node Installation Builder and correct the errors. Refer to the “Validate
Node Definitions” section in the Installation Builder User Guide.
6. If there are differences between the current configuration and the configuration being
downloaded, a Comparison Report is displayed listing the differences.
7. View all the configuration items that are changed and click Download to proceed.
8. Click Exit if you do not want to proceed with the download.
If you are changing the computer name or adding the computer to a domain and you are not
logged on with an account that has adequate privileges, you are prompted for another
account and password.
9. Enter the information and press OK.
- 64 -
TIP
As its final operation, the download function launches the ANCIM Reboot Manager
and performs the following:
l Changes the computer name.
l Adds or updates the IP address(es).
l Adds the computer to a domain, if applicable.
The ANCIM Reboot Manager also manages the reboots required after performing
the above actions and running the link domain groups and the server rename
tools.
7.6 Connect network cables to switches
Use the information in this section to add the FTE node to the network. The FTE network switches
must be configured using the switch configuration files and procedures in the FTE Overview and
Implementation Guide.
Use this procedure to connect the FTE network cables to the Full Duplex 100-megabit switch ports.
The Full Duplex 100-megabit ports are the switch ports that are located after the configured uplink
ports and FTE bridge ports.
CAUTION
Ensure that you shut down the new FTE node before connecting the network cables and
adding the node to an on-process system. This ensures that any duplicate IP address is
detected immediately and allows you to resolve any IP address conflicts.
7.6.1 Connect FTE network cables
1. Shut down the FTE node.
2. Connect the Yellow network cable to one of the Full Duplex 100-megabit ports configured for
FTE nodes in Switch A (Yellow tree).
3. Connect the Yellow network cable to the NIC A (Yellow) port.
4. Connect the green network cable to one of the Full Duplex 100-megabit ports configured for
FTE nodes in Switch B (Green tree).
5. Connect the Green network cable to the NIC B (Green) port.
6. Restart the FTE node.
7. If the following error message is displayed, shut down the node and resolve the conflict.
The static IP address that was just configured is already in use on the network. Please
reconfigure a different IP address.
- 65 -
Refer to the section Resolve duplicate IP addresses
7.7 Verify FTE installation
FTE installation checklist
Use this checklist to verify proper installation of FTE.
Number Requirement Status
1 All A - Yellow cables are connected to the correct switch ports in the A - Yellow
tree.
2 All B - Green cables are connected to the correct switch ports in the B - Green
tree.
3 The Device Index is set to a unique value other than 0.
4 All values in the Device Index are unique.
ATTENTION
Dup State column of the FTE Auxiliary Display must display No
Duplicates for all nodes within the multicast scope.
5 IPMC destination address is set correctly for all nodes within the FTE Community.
6 Only the highest level of redundant switches in the LAN is interconnected using
the crossover cable.
For more information on network, refer to the FTE Overview and Implementation
Guide.
In case of issues, refer to the section Troubleshooting FTE.
- 66 -
OPERATING AND SERVICING FTE

l Modify FTE settings
l View FTE status
l Monitor nodes in an FTE network
l Replace the NICs
l Update NIC adapter drivers
8.1 Modify FTE settings

ATTENTION
To modify IP information for FTE (such as IP address), go to the Internet Protocol Version 4
(TCP/IPv4) Properties window of the Honeywell FTE adapter.
Use this procedure to access the FTE Mux-IM Protocol Driver Properties dialog box to review or
modify Honeywell FTE adapter settings. In addition, refer to the Configure/verify FTE Mux-IM
protocol driver properties for descriptions of each setting.
8.1.1 Access FTE Mux-IM Protocol Driver configuration dialog box
1. Log on to the system as Local Administrator.
3. Right-click either one of the NIC associated with FTE, and choose Properties.
Depending on the NIC selected, the FTE Yellow/Green Properties dialog box is displayed.
4. Select Honeywell FTE Mux-IM Protocol Driver and then click Properties.
If no adapters are bound to the FTE driver, select the Honeywell FTE Mux-IM Protocol Driver
check box, and then click Properties.
The FTE Mux-IM Protocol Driver Properties dialog box is displayed.
- 67 -
CHAPTER
8
5. Click the Configure tab.
You can drag the appropriate adapters under the Honeywell FTE Adapter. When you click OK,
the FTE binds and correctly checks/clears the appropriate boxes.
6. To unbind an adapter from FTE, drag the adapter away from under the Honeywell FTE
Adapter and drop it into the blank space, as illustrated in the following image.
The physical adapter is no longer offset.
- 68 -
Chapter 8 - Operating and servicing FTE
7. To bind an adapter, select the physical adapters which are not offset under the Honeywell FTE
adapter. Now drag and drop these adapters under the Honeywell FTE Adapter, as illustrated in
the following image.
8. Click one of the physical adapters (Yellow or Green) and verify the properties that appear on
the right plane.
If you manipulate the adapters that are bound to the Honeywell FTE adapter, ensure to verify
the correct adapters are categorized as Green or Yellow in the physical adapter properties. If
they are reversed, use the list in the Properties field to correct the binding.
ATTENTION
It is important to verify the adapters are categorized correctly because when
adapters are added or removed from the Honeywell FTE Adapter the Yellow/Green
association may be reversed. When a Yellow adapter is removed, the Green
becomes the primary (and indicates the same in the properties on the right). When
the Yellow is added again, the Green remains as primary. In addition, if both
adapters are removed, whichever adapter is added first assumes the primary role.
9. Review or modify the values in the FTE Mux-IM Protocol Driver Properties dialog box.
10. Click OK to close the FTE Mux-IM Protocol Driver Properties dialog box.
11. Click Close to exit the adapter properties dialog box.
8.2 View FTE status
You can view the operating status of your FTE nodes using Honeywell’s System Management and
the cable status of your FTE nodes using the FTE Status auxiliary display.
l Access status displays
l System Management Display overview
l FTE Status server and Auxiliary display overview
8.2.1 Access status displays

Status displays can be accessed in several ways as described in the following table.
- 69 -
Product Display type Option
Experion System
Management
Display
Select Start > All Programs > HoneywellExperion PKS > System
Management > System Management Display.
Or
Select Start > All Programs > Honeywell > System Management >
System Management Display
Experion FTE Status
auxiliary display
Select Start > All Programs > HoneywellExperion PKS > System
Management > FTE and Heartbeat Node Status Display.
Click the FTE Status hyperlink from the System Status Display in
Station.
Or
Click the FTE Community Status tab on Honeywell FTE Mux-IM
Protocol Driver Properties window.
TPS System
Management
Display
Open your configured System Management Display from the
Microsoft Management Console (Start > Run and type "mmc").
TPS FTE Status
auxiliary display
From the System Management Display, expand the network tree and
then click an FTE node.
Right-click the FTE Status component and click Auxiliary Display.
8.2.2 System Management Display overview
Honeywell’s System Management allows you to configure and monitor managed nodes and their
HCI-managed components in a Windows domain or a workgroup. You can view the status of the
FTE nodes from this display.
8.2.3 FTE Status server and Auxiliary display overview
The FTE Status server is an HCI-managed component. The FTE Status server communicates with
the Heartbeat provider (FTE provider) and provides connected clients with a list of all the nodes
currently reporting a heartbeat within its multicast scope. The following figure is an example of an
FTE Status Auxiliary display. Notice that the individual cable link states (A>A, A>B, B>A, B>B) of the
FTE nodes (TB6SRV1B and TB6SRV1A) can be viewed from this display.
TIP
Refer to the FTE Status Server and Display Guide for more information about using this
application to monitor your FTE node.
- 70 -
8.3 Monitor nodes in an FTE network
l Reviewing cable status
l Cable status states for FTE nodes with non-crossed cables
l Cable status states for FTE nodes with crossed cables
l Use System Management Display to identify crosslink errors
l Display status of remote FTE node
8.3.1 Reviewing cable status

The tables in this section contains examples of cable status states you may view using the System
Management display.
l The Scenario column identifies the specific scenario for which examples and pictures are
provided.
l The YES and NO in the Crossover Cable Conn. column indicate whether or not the crossover
cable is connected. Note how the removal of the crossover cable alters what the nodes are able
to “hear” on their ports.
l The YES and NO in the Port A Conn. and Port B Conn. columns indicate whether or not the A or
B cables are connected on TB6SRV1B and TB6SRV1A.
l The Sending Node column identifies the node that is transmitting to the receiving or As Viewed
By node (SRVA in the example).
l The A > A column indicates whether port A of the sending node can transmit to port A of the
receiving (viewed by) node.
l The A > B column indicates whether port A of the sending node can transmit to port B of the
l The B > A column indicates whether port B of the sending node can transmit to port A of the
l The B > B column indicates whether port B of the sending node can transmit to port B of the
- 71 -
ATTENTION
l The composite status is provided to identify any single fault when the number of
nodes exceeds the number of currently displayed nodes. You must scroll down in
the window and search each individual node to check if there is a problem.
l If there is a red circle in the composite node status, it indicates that at least one
node in the display is silent on that particular communication path.

8.3.2 Cable status states for FTE nodes with non-crossed cables
The following table lists the possible cable status states for two FTE nodes as viewed from
TB6SRV1A. In all of these examples, there are no crossed cables for TB6SRV1B or TB6SRV1A. The
cables are connected to the appropriate ports and switches and the binding order is consistent
with the cabling.
Scnario
Crossover
cable conn.
Port A
conn
Port B
conn
Sending
node A > A A > B B > A B > B
1 YES YES YES TB6SRV1B OK OK OK OK
1 YES YES YES TB6SRV1A OK OK OK OK
2 NO YES YES TB6SRV1B OK SILENT SILENT OK
2 NO YES YES TB6SRV1A OK SILENT SILENT OK
3 YES YES YES TB6SRV1B OK SILENT OK SILENT
3 YES YES NO TB6SRV1A OK SILENT SILENT SILENT
4 NO YES YES TB6SRV1B OK SILENT SILENT SILENT
4 NO YES NO TB6SRV1A OK SILENT SILENT SILENT
5 YES YES YES TB6SRV1B SILENT OK SILENT OK
5 YES NO YES TB6SRV1A SILENT SILENT SILENT OK
6 NO YES YES TB6SRV1B SILENT SILENT SILENT OK
6 NO NO YES TB6SRV1A SILENT SILENT SILENT OK
7 YES YES YES TB6SRV1B Node does
not appear
Node does
not appear
Node does
not appear
Node does
not appear
7 YES NO NO TB6SRV1A SILENT SILENT SILENT SILENT
Scenario No. 1: A and B port connected; Crossover cable connected
TB6SRV1B’s A port and B port hear from TB6SRV1A’s A port and B port.
TB6SRV1A’s A port and B port hears from both its own ports.
Scenario No. 2: A and B port connected; Crossover cable disconnected
TB6SRV1B’s and TB6SRV1A’s ports can only hear from other ports on the same switch since there
is no crossover cable between the A switch and B switch.
- 72 -
Scenario No. 3: B port disconnected; Crossover cable connected
TB6SRV1B’s A port and B port hear only from TB6SRV1A’s A port.
TB6SRV1A hears only from its own A port.
Scenario No. 4: B port disconnected; Crossover cable disconnected
TB6SRV1B’s A port hears only from TB6SRV1A’s A port.
TB6SRV1A’s A port hears only from its own A port.
Scenario No. 5: A port disconnected; Crossover cable connected
TB6SRV1B’s A port and B port hears only from TB6SRV1A’s B port.
TB6SRV1A hears only from its own B port.
Scenario No. 6: A port disconnected; Crossover cable disconnected
TB6SRV1B hears only from TB6SRV1A’s B port.
8.3.3 Cable status states for FTE nodes with crossed cables
The following table lists the possible cable status states for two FTE nodes as viewed from
TB6SRV1A. In all of these examples, TB6SRV1A has crossed cables and the cables for TB6SRV1B
are not crossed.
- 73 -
Scenario
Crossover cable
conn.
Port A
conn
Port B
conn
Sending
node A > A A > B B > A B > B
1 YES YES YES TB6SRV1B OK OK OK OK
1 YES YES YES TB6SRV1A OK OK OK OK
2 NO YES YES TB6SRV1B SILENT OK OK SILENT
2 NO YES YES TB6SRV1A OK SILENT SILENT OK
3 YES YES YES TB6SRV1B SILENT SILENT SILENT OK
3 YES YES NO TB6SRV1A SILENT OK SILENT OK
4 YES YES YES TB6SRV1B SILENT OK SILENT SILENT
4 YES YES NO TB6SRV1A SILENT SILENT SILENT OK
5 YES YES YES TB6SRV1B OK SILENT OK SILENT
5 YES NO YES TB6SRV1A OK SILENT SILENT SILENT
6 NO YES YES TB6SRV1B SILENT SILENT OK SILENT
6 NO NO YES TB6SRV1A OK SILENT SILENT SILENT
Scenario No. 1: A and B port connected; Crossover cable connected,
crossed cables
TB6SRV1B’s A port and B port hear from TB6SRV1A’s A port and B port.
TB6SRV1A’s A port and B port hears from both its own ports.
Scenario No. 2: A and B port connected; Crossover cable disconnected,
crossed cables
As the cables are crossed and the crossover cable between the switches is not connected
TB6SRV1B’s and TB6SRV1A’s ports can only hear from opposite ports.
Scenario No. 3: B port disconnected; Crossover cable connected; crossed
cables
Scenario No. 4: B port disconnected; Crossover cable disconnected;
crossed cables
- 74 -
Scenario No. 5: A port disconnected; Crossover cable connected; crossed
cables
TB6SRV1B’s A port and B port hear only from TB6SRV1A’s A port.
Scenario No. 6: A port disconnected; Crossover cable disconnected;
crossed cables
TB6SRV1B’s B port hears only from TB6SRV1A’s A port.
8.3.4 Use System Management Display to identify crosslink errors
After FTE is installed and configured, use the System Management display and the FTE Status
server to verify whether there are any crosslink errors. This procedure requires that you have
System Management display and the FTE Status server installed and configured.
TIP
Refer to the following two guides for more information about configuring a System
Management Display and using it to monitor the FTE node.
l System Management Configuration Guide
l FTE Status Server and Display Guide
1. Select Experion > System Management > System Management Display, and open a configured
System Management Display.
2. Select the FTE Status server from the FTE node being tested.
3. Locate the FTE node in the FTE Status View.
4. Remove the A port cable.
5. Examine the cable status states in the A > A to B > B columns.
6. If there are no crosslink errors, the FTE node that is being tested must not be able to hear
from its own A port and none of the other FTE node must be able to hear from the
disconnected port. Refer to the following "Disconnected A cable – no crosslink error example."
Disconnected A cable – no crosslink error example
- 75 -
7. If there is a crosslink error, the FTE node being tested indicates that it is able to hear from its
own A port even though it is disconnected. Other FTE nodes also indicate they are able to hear
from the disconnected port. Refer to the following "Disconnected A cable – crosslink error
example."
Disconnected A cable – crosslink error example
8. If there are crosslink errors, re-check all items.
8.3.5 Display status of remote FTE node
Use this feature to view the FTE status as seen from the remote node’s view. This provides a view
of the status array transmitted by the FTE driver for each FTE node. Since this is the view as seen
from the FTE driver, it is only available on FTE nodes. For example, the current FTE node is
TB6SRV1A, and view the status at FTE node TB6SRV1B, right-click on node TB6SRV1B to view the
status from that node.
1. From the FTE Status Auxiliary display, right-click the node from whose status must be viewed.
2. Review the status from the remote node’s view.
8.4 Replace the NICs
Honeywell continuously qualifies new NICs for use with FTE. This section contains checklists for
upgrading or replacing FTE NICs. Locate the checklist for your specific NIC replacement and
complete the tasks listed in the order shown.
l Special considerations when replacing NICs
l NIC replacement checklist
8.4.1 Special considerations when replacing NICs

When a NIC is installed in the computer, the operating system assigns a Globally Unique Identifier
(GUID) to the NIC. This GUID is persistent in the computer. If the NIC is removed improperly, this
GUID still exists and the FTE Mux-IM Protocol driver is bound to it. It is important to follow the
checklist for replacing the NICs in the FTE computer to ensure proper operation. If you do not
follow these steps in the correct order, it may result in a computer that must be reloaded from
scratch to get network operations working correctly.
- 76 -
8.4.2 NIC replacement checklist
The following table lists the tasks associated with removing the existing NIC and replacing it with a
new one.
Task Go to Status
Unbind the physical adapters from the Honeywell
FTE adapter
Unbind physical adapters from
Honeywell FTE adapter
Disable/remove NICs Remove NIC(s)
Shut down the computer and remove the NIC Vendor Documentation
Install dual port NIC Install dual port NIC
ATTENTION
The Found New hardware wizard may
be displayed during logging onto the
computer: If a driver is found, a
message stating the hardware is ready
for use is displayed. If the NIC card is
new or a different NIC, then Install the
adapter drivers.
Install or update NIC drivers Install or update NIC drivers
Configure NIC adapters for FTE: Verify/change
physical adapters settings
ATTENTION
Ensure to use the same Yellow IP
address settings as the previous NIC
card was using.
Configure NIC adapters for FTE
Rename the network physical adapters Rename the network physical adapters
Rebind the physical adapters to the Honeywell FTE
adapter
Rebind physical adapters to the
Honeywell FTE adapter
Configure/verify FTE Mux-IM protocol driver
properties
Configure/verify FTE Mux-IM protocol
driver properties
Restart the computer
Verify Honeywell FTE driver operation Verify the Honeywell FTE driver
operation.
8.5 Update NIC adapter drivers
This checklist must be performed when there is an update or different version of the Intel or
Broadcom dual NIC adapter driver.
ATTENTION
The order of this checklist is important, because if the physical adapters are not unbound
from the virtual Honeywell adapter, during the driver update all the adapter settings are lost
and the system encounters a stop error. Do not remove the FTE Mux driver package.
l NIC driver update checklist
- 77 -
l Remove NIC(s)
l Unbind physical adapters from Honeywell FTE adapter
l Rebind physical adapters to the Honeywell FTE adapter
8.5.1 NIC driver update checklist

The following table lists the tasks associated with updating the adapter driver version for the
installed dual NIC. After performing each procedure return to the checklist to reference the next
procedure.
Task Go to Status
Unbind the physical adapters from the Honeywell
FTE adapter.
Unbind physical adapters from
Honeywell FTE adapter.
Install or update NIC drivers Install or update NIC drivers.
Configure NIC adapters for FTE - Verify/change
physical adapters settings.
Verify/change physical adapters
settings.
Rebind the physical adapters to the Honeywell FTE
adapter.
Rebind physical adapters to the
Honeywell FTE adapter.
Configure/verify FTE Mux-IM Protocol driver
properties.
Configure/verify FTE Mux-IM protocol
driver properties.
Restart the computer.
Verify Honeywell FTE driver operation. Verify the Honeywell FTE driver
operation.
8.5.2 Remove NIC(s)
ATTENTION
Ensure to unbind the adapters before the NICs are disabled/removed. Perform this
procedure only to physically remove the NICs. This procedure must never be performed on a
system while FTE is operational, as unpredictable results such as Stop error may occur or
total loss of network communication may take place.
Use this procedure to disable and remove all the currently installed NICs. Perform this procedure
only if the dual NIC is being physically removed from the computer.
- 78 -
For Microsoft Windows 10
Enterprise 2016 LTSB (x64)
a. Right-click the My Computer icon from the
desktop or from the Start menu and choose
Manage.
The Computer Management window is
displayed.
b. In the console tree, open System Tools and
then click Device Manager.
For Microsoft Windows
Server 2016 Standard
desktop. Or from the Start menu and choose
Manage.
displayed.
b. In the console tree, open Diagnostics and then
click Device Manager.
a. On the taskbar, click Server Manager icon
The Server Manager dialog box is displayed.
b. Click Tools > Computer Management.
displayed.
c. In the console tree, open System Tools and
2. Double-click Network adapters to view all installed NICs.
3. Right-click the network adapter and choose Uninstall.
4. Click OK to confirm the removal of the device.
5. Repeat the above steps to remove each installed NIC.
8.5.3 Unbind physical adapters from Honeywell FTE adapter
Perform the following procedure for any operations that require update or removal of the NICs.
Ensure that NIC driver updates or removal is not done before FTE is unbound from the physical
NICs. Unexpected results occur, which require the complete reinstallation of Experion.
3. Select FTE Yellow, right-click on the adapter, and choose Properties.
- 79 -
4. Click Continue.
The FTE Yellow Properties dialog box is displayed.
5. Click Honeywell FTE Mux-IM Protocol Driver and then click Properties.
8. Continue with the next step in the checklist.
8.5.4 Rebind physical adapters to the Honeywell FTE adapter
Perform this procedure only after all NIC updates and operations have been completed.
3. Select FTE Yellow, right-click on the adapter, and choose Properties.
4. Click Continue.
The FTE Yellow Properties dialog box is displayed.
5. Click Honeywell FTE Mux-IM Protocol Driver and the click Properties.
- 80 -
7. Select the FTE Yellow adapter and drag the object under the Honeywell FTE Adapter #1, as
illustrated in the following image.
- 81 -
8. Select the FTE Green adapter and drag the object under the Honeywell FTE Adapter #1, as
illustrated in the following image.
ATTENTION
Ensure the Yellow adapter is rebound to the Honeywell FTE adapter first and verify
whether the Yellow adapter properties dialog box displays it as primary.
9. Select the Honeywell FTE Adapter and verify the FTE settings are as previously set.
11. Restart the computer.
12. Return to the checklist and verify FTE operations.
- 82 -
TROUBLESHOOTING FTE
l Isolating problems
l Procedures for verifying proper installation
l Fixing common problems
l Resolving network issues
l Getting further assistance
9.1 Isolating problems

9.1.1 FTE installation verification checklist
The following checklist provides a list of items that must be verified if you experience problems
with FTE installation. If you experience specific symptoms, refer to Fixing common problems to
determine an appropriate action to take.
Task Go To Status
Inspect the NICs Inspect the NICs
Verify duplicate IP addresses were not assigned Verify if duplicate IP addresses are
assigned
Verify duplicate device indexes were not assigned Verify if duplicate device indexes are
assigned
Verify connections are configured properly for FTE Verify connections are configured
properly for FTE
Verify the event logs for FTE driver state the device
is working properly
Verify the event logs for FTE driver
state is working
9.2 Procedures for verifying proper installation
l Verify Honeywell FTE software is installed
l Inspect the NICs
l Verify if duplicate IP addresses are assigned
l Verify if duplicate device indexes are assigned
l Verify connections are configured properly for FTE
l Verify the event logs for FTE driver state is working
- 83 -
CHAPTER
9
9.2.1 Verify Honeywell FTE software is installed
Use this procedure to verify the Honeywell FTE service is properly installed.
2. Right-click one of the NIC (Yellow or Green) associated with FTE, and choose Properties.
3. Verify that Honeywell FTE Mux-IM Protocol Driver appears in the list of components as
displayed in the following image.
- 84 -
Chapter 9 - Troubleshooting FTE
ATTENTION
If Honeywell FTE Mux-IM Protocol driver does not appear in the Properties dialog
box, verify if FTE driver was installed on the computer as an option.
If FTE was not installed, perform the checklist in section Install and configure FTE
on existing Experion nodes
If FTE Mux driver was installed, TAC must be contacted to properly troubleshoot why
the protocol driver is not listed in the NIC adapter properties.
9.2.2 Inspect the NICs
Use this procedure to verify whether NICs for FTE are installed properly.
For Microsoft Windows 10
Enterprise 2016 LTSB (x64)
desktop or from the Start menu and choose
Manage.
displayed.
b. In the console tree, open System Tools and
desktop. Or from the Start menu and choose
Manage.
displayed.
b. In the console tree, open Diagnostics and then
click Device Manager.
displayed.
c. In the console tree, open System Tools and
2. Expand Network adapters to view all installed NICs.
ATTENTION
The illustrations used in this procedure is an example, and may not be identical to
what you see on your screen.
3. Verify that only one Honeywell FTE Mux-IM Virtual Miniport Driver is listed for FTE as displayed
in the following image.
- 85 -
4. If Honeywell FTE Mux-IM Virtual Miniport Driver is listed for FTE, ensure and verify that you
performed all of the procedures according to the correct checklist in FTE installation
scenarios.
9.2.3 Verify if duplicate IP addresses are assigned
Use this procedure to verify whether there is a unique IP address for each of the ports on the NIC
used for FTE. This procedure is not applicable if DHCP is used for configuring the IP addresses.
1. To determine Yellow and Green adapters, select Start > Run and type command in the Run
dialog box.
2. In the command prompt window, type ipconfig /all and press ENTER.
3. Verify that the IP address for FTE Mux adapter is unique. The following image displays an
example when a duplicate IP address exists on the computer.
4. In addition, the address duplication is reported as an error in the System Event log. To view
the address duplication in the System Event log, perform the following:
Operating
system
Tasks
Microsoft
Windows 10
Enterprise
2016 LTSB
(x64)
a. Right-click the My Computer icon from the desktop or from the Start
menu and choose Manage.
The Computer Management window is displayed.
b. In the console tree, open System Tools and then click Event Viewer.
Microsoft
Windows
Server 2016
Standard
a. Right-click the My Computer icon from the desktop. Or from the
Start menu and choose Manage.
b. In the console tree, open Diagnostics and then click Event Viewer.
Microsoft
Windows
Server 2016
Standard
c. In the console tree, open System Tools and then click Event Viewer.
- 86 -
5. Click Windows Logs and then click System.
6. Review the description for the following event type, which indicates that there are two nodes
within the FTE community that have the same device index.
a. A Warning with event ID 14 for FTEMUXP “Configuration Needed. Bad FTE IP Address
Device Index”.
b. An Error with event ID 518 for FTEMUXP “A duplicate IP Address has been detected”.
7. If the IP address displays duplicate or any of the above System Events, refer to Resolve
duplicate IP addresses.
9.2.4 Verify if duplicate device indexes are assigned
Each node within an FTE Community must have a unique device index. Use this procedure to open
the event log and verify for duplicate devices indexes.
Operating
system
Tasks
Microsoft
Windows 10
Enterprise
2016 LTSB
(x64)
Microsoft
Windows
Server 2016
Standard
Microsoft
Windows
Server 2016
Standard
2. Click Windows Logs and then click System.
3. Look through the log for source of FTEMUXMP. If Event ID of 15 exists, open Event Properties.
4. Review the description for the following event type, which indicates that there are two nodes
within the FTE community that have the same device index.
l Duplicated Node. <PD Tag %2> the data has duplication state and device index.
5. If you find the duplicated node event, change the device index on one of the duplicate nodes.
Refer to the section, Configure/verify FTE Mux-IM protocol driver properties and section,
Monitor nodes in an FTE network.
9.2.5 Verify connections are configured properly for FTE
Use this procedure to verify you configured your Local Area Connections for use with FTE.
- 87 -
2. Right-click one of the FTE NICs and then choose Properties.
3. Ensure Honeywell FTE Mux-IM Protocol Driver is checked. If not, select Honeywell FTE Mux-
IM Protocol Driver.
4. Click Properties.
The Honeywell FTE Mux-IM Protocol Driver Properties dialog box is displayed.
5. Verify that the connection associated with the NICs being used for FTE is listed under
Honeywell FTE Adapter.
6. Close the Honeywell FTE Mux-IM Protocol Driver Properties, and Network Connections dialog
boxes.
9.2.6 Verify the event logs for FTE driver state is working
Use this procedure to open Event Viewer and view the events for the FTE driver.
Operating
system
Tasks
Microsoft
Windows 10
Enterprise
2016 LTSB
(x64)
Microsoft
Windows
Server 2016
Standard
Microsoft
Windows
Server 2016
Standard
2. In the console tree, click Application and Services Logs, and then click FTE.
3. Double-click the event to open the Event Properties dialog box.
4. Review the event descriptions.
9.3 Fixing common problems
l Intermittent or blocked communication to controllers on a different subnet
l NICs cannot connect
l Faulty FTE communication
l Cannot establish network communications
l FTE node does not appear in the System Management Display
l Mismatch of FTE multicast address and destination port
- 88 -
9.3.1 Intermittent or blocked communication to controllers on a
different subnet
When controllers are addressed in a different subnet when compared to the servers/consoles, the
level 2 nodes rely on addroute and ARP to establish TCP connections with controllers. If proxy arp
is enabled on the router, the router responds with its own MAC address when the level 2 nodes
ARP for the controller MAC addresses, preventing or breaking TCP communication. Hence, all
router connections to an FTE network must have the no ip proxy arp command.
Error
Indication
System Event IP Proxy ARP Detected
Cause IP Proxy ARP is enabled on the router.
Solution Disable IP Proxy ARP on the router for the FTE Community on the subnet it is located
on.
Error
Indication
System Event IP Proxy ARP Detected From and administrative Command Prompt: Type
route print, verify the specific route to the controllers is listed in the route table.
Cause Route to controllers is missing from the server/console/ACE’s route table.
Solution Check for Controller paths to be specified correctly in Control Builder. Select
Configuration Studio>Control Strategy>Configure Process Control Strategies.
From Control Builder select Tools>System Preferences> Embedded FTE Tab.
Verify/correct FTE Properties settings and wait 10 minutes to verify controllers can be
contacted.
Error
Indication
Verify the Controllers have the same IPMC Destination address, UPD Source port or
UPD Destination port values.
Cause Controllers did not get the new or latest parameters from the bootp server.
Solution Verify the bootp server’s FTE settings are configured as previously when the
controllers were last reloaded. If not reboot the controllers to pick up the new values
from the bootp server or change the migrated node’s values to match the online
controllers.
9.3.2 NICs cannot connect
After unbinding FTE, the NIC cannot communicate even though the network cables are connected.
Error
Indication
Check for switch interface to where the node is connected blinking amber.
Cause FTE adapter or switch configured for auto-negotiate resulting in speed/duplex
mismatch.
Solution Correct the speed/duplex configuration of the adapter or switch.
Error
Indication
After unbinding FTE, the computer cannot detect any computers in the network
community.
Cause After unbinding FTE, the computer’s IP address is no longer correct, because the IP
address was configured on the Honeywell FTE adapter.
Solution Change the IP address on the Yellow adapter to match the Honeywell FTE adapter’s
value using procedure Verify/set NIC adapter TCP/IPV4 properties
9.3.3 Faulty FTE communication
FTE network connection is unusually slow.
Error
Indication
The FTE node is not communicating as expected and packets are being lost.
- 89 -
Cause Duplicate device indexes within the FTE community are causing a conflict.
Solution Refer to the Verify if duplicate device indexes are assigned.
Error
Indication
Slow socket communications
Cause Switch port and node settings are not correct.
Solution
l Verify that the switch port and node are set to 100 full duplex.
l Verify that the NIC cable is connected to an FTE configured switch port. Refer to
the Installing and Configuring Switches in the FTE Overview and Implementation
Guide.
9.3.4 Cannot establish network communications
The FTE node cannot communicate with the network from either of the NIC port.
Error
Indication
The node cannot communicate with network after the node is started and then
connected to the network cables.
Cause If a node that has a duplicate IP address is connected to the network after it is already
booted up, the following error message is displayed.
“Windows has detected and IP address conflict”.
Solution Refer to the section Resolve duplicate IP addresses
9.3.5 FTE node does not appear in the System Management
Display
Error
Indication
The FTE computer does not appear in the System Management display tree on other
computers.
Cause The System Management Multicast address does not match the other Experion
nodes in the FTE Community.
Solution Change the Multicast address to match the System Management group using the
Systems Management Configuration Guide.
9.3.6 Mismatch of FTE multicast address and destination port
An FTE node does not show up in the FTE node list or FTE status display as expected
Error
Indication
The FTE computer does not appear in the FTE Status display tree on other computers
in the FTE community.
Or
The FTE computer appears by itself on the locally run FTE Status display.
Cause The FTE Multicast address does not match the other Experion nodes in the FTE
Community.
Or
The UDP source or destination addresses does not match the other nodes in the FTE
Community.
Solution Change the Multicast address and/or the UPD source and destination ports to match
the other FTE nodes in the FTE Community. Refer to the section Configure/verify FTE
Mux-IM protocol driver properties.
- 90 -
9.4 Resolving network issues
l Enable ethernet port for onboard NIC
l Resolve duplicate IP addresses
9.4.1 Enable ethernet port for onboard NIC
Use this procedure to enable the onboard NIC. Skip this procedure if onboard NICs are currently
enabled.
CAUTION
BIOS setup is an advanced tool. Enter the system setup only if you are an experienced user.
1. Restart the computer and, when prompted during system startup, press the appropriate key(s)
to enter system setup.
2. Select Integrated Devices.
3. If Network Interface Controller is listed, you have onboard NIC. Change the setting to On.
4. Save changes and exit BIOS settings to continue the system startup.
9.4.2 Resolve duplicate IP addresses
Use this procedure to resolve duplicate IP addresses for FTE node.
Operating system Tasks
Microsoft Windows 10 Enterprise 2016 LTSB (x64)
Microsoft Windows Server 2016 Standard
Microsoft Windows Server 2016 Standard
2. Right-click the Honeywell FTE Adapter, and then choose Properties.
The Honeywell FTE Adapter Properties dialog box is displayed.
3. In the Networking tab, select Internet Protocol Version 4(TCP/IPv4) and then click Properties.
The Internet Protocol Version 4(TCP/IPv4) Properties dialog box is displayed.
4. Click Use the following IP address to specify the IP address for the network connection.
5. In the IP address text box, type the IP address to be assigned to this network connection.
ATTENTION
Ensure it is a unique address in the range of addresses that are available for the
network.
6. In the Subnet mask text box, type the subnet mask for the network.
7. In the Default gateway box, type the IP address of the computer or device on your network
that connects your network to another network or to the Internet.
- 91 -
8. Select Use the following DNS server addresses and enter the IP addresses for your DNS
servers.
9. Click OK, and close all dialog boxes.
10. Verify all network cables are connected correctly. Refer to the section, Connect network cables
to switches, if necessary.
The FTE node must be visible on the network.
9.5 Getting further assistance
Other resources
Subject Resource
l Monitoring
FTE node
status
l Determinin
g cable
faults
If the FTE Status components are installed, view the status of the FTE node and
the individual cable status from a station that has Honeywell System
Management Display installed and a System Management Display configured.
Refer to the following two guides for more information.
l System Management Configuration Guide
l FTE Status Display Guide
- 92 -
Notices
Trademarks
Experion®, PlantScape®, SafeBrowse®, TotalPlant®, ControlEdge™, and TDC 3000® are registered
trademarks of Honeywell International, Inc.
OneWireless™ is a trademark of Honeywell International Sàrl
Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of Microsoft Corporation
in the United States and/or other countries.
Trademarks that appear in this document are used only to the benefit of the trademark owner,
with no intention of trademark infringement.
Third-party licenses
This product may contain or be derived from materials, including software, of third parties. The
third party materials may be subject to licenses, notices, restrictions and obligations imposed by
the licensor. The licenses, notices, restrictions and obligations, if any, may be found in the
materials accompanying the product, in the documents or files accompanying such third party
materials, in a file named third_party_licenses on the media containing the product, or at
http://www.honeywell.com/ps/thirdpartylicenses.
Documentation feedback
You can find the most up-to-date documents on the Honeywell Process Solutions support website
at:
l http://www.honeywellprocess.com/support
If you have comments about Honeywell Process Solutions documentation, send your feedback to:
l hpsdocs@honeywell.com
Use this email address to provide feedback, or to report errors and omissions in the
documentation. For immediate help with a technical problem, contact your local Honeywell
Process Solutions Customer Contact Center (CCC) or Honeywell Technical Assistance Center
(TAC).
How to report a security vulnerability
For the purpose of submission, a security vulnerability is defined as a software defect or weakness
that can be exploited to reduce the operational or security capabilities of the software.
Honeywell investigates all reports of security vulnerabilities affecting Honeywell products and
services.
To report a potential security vulnerability against any Honeywell product, please follow the
instructions at:
https://honeywell.com/pages/vulnerabilityreporting.aspx
Submit the requested information to Honeywell using one of the following methods:
l Send an email to security@honeywell.com.
or
l Contact your local Honeywell Process Solutions Customer Contact Center (CCC) or Honeywell
Technical Assistance Center (TAC) listed in the “Support” section of this document.
- 93 -
Support
For support, contact your local Honeywell Process Solutions Customer Contact Center (CCC). To
find your local CCC visit the website, https://www.honeywellprocess.com/en-US/contactus/
customer-support-contacts/Pages/default.aspx.
Training classes
Honeywell holds technical training classes about Experion PKS. These classes are taught by

Instructions To Disable

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Instructions To Disable

Încărcat de

Drepturi de autor:

Formate disponibile

NICs

7.2.1 Identify FTE NIC ports

4. Reconnect the A - Yellow network cable to the NIC A port.

7.3 Configure FTE network connections

l Configure the Honeywell FTE adapter

o Jumbo Packet verify/change the value to Disabled.

o Link Speed Tab and verify/change the value to 100Mbps/Full Duplex.

l Download FTE-configured master definition

7.5.1 About Master definitions and FTE

are errors, you are allowed to continue.

l You launched the Installation Builder in online mode.

l Adds or updates the IP address(es).

l Adds the computer to a domain, if applicable.

OPERATING AND SERVICING FTE

l Replace the NICs

l Update NIC adapter drivers

8.1 Modify FTE settings

l System Management Display overview

l FTE Status server and Auxiliary display overview

8.2.1 Access status displays

l Use System Management Display to identify crosslink errors

l Display status of remote FTE node

8.3.1 Reviewing cable status

node in the display is silent on that particular communication path.

l FTE Status Server and Display Guide

l NIC replacement checklist

8.4.1 Special considerations when replacing NICs

l Unbind physical adapters from Honeywell FTE adapter

l Rebind physical adapters to the Honeywell FTE adapter

8.5.1 NIC driver update checklist

l Resolving network issues

l Getting further assistance

9.1 Isolating problems

l Verify if duplicate device indexes are assigned

l Verify connections are configured properly for FTE

l Verify the event logs for FTE driver state is working

l Cannot establish network communications

l FTE node does not appear in the System Management Display

l Mismatch of FTE multicast address and destination port

l FTE Status Display Guide

S-ar putea să vă placă și