Swm0008 Iscs Users Guide

g GE Energy Services
iSCS User's Guide

Theory and Configuration
Document Number : SWM0008

Version : 2.00
Revision : 3
Date : 09-May-2003
Classification : General, Full Release
iSCS User's Guide
GE Energy Services Theory and Configuration
NOTICE OF 2003, General Electric Canada Inc. All rights reserved.

COPYRIGHT &
PROPRIETARY The contents of this manual are the property of General Electric Canada Inc. No
RIGHTS part of this work may be reproduced or transmitted in any form or by any means,
except as permitted in written license agreement with General Electric Canada Inc.
General Electric Canada Inc. has made every reasonable attempt to ensure the
completeness and accuracy of this document. However, the information contained in
this manual is subject to change without notice, and does not represent a
commitment on the part of General Electric Canada Inc.
Any attached hardware schematics and technical descriptions, or software listings
that disclose source code, are for information purposes only. Reproduction in whole
or in part to create working hardware or software for other than General Electric
Canada Inc. products is strictly prohibited, except as permitted by written license
agreement with General Electric Canada Inc.
TRADEMARK WESDAC is a registered trademark of General Electric Company, General Electric

NOTICES Canada Inc. and/or GE Harris Energy Control Systems Canada, Inc. All other brand
and product names mentioned in this document are trademarks or registered
trademarks of their respective companies.
SWM0008 2.00 3 General
ii Full Release
iSCS User's Guide
Theory and Configuration GE Energy Services
Modification Record
VERSION REVISION DATE INITIALS COMMENT

1.00 1 17-May-00 RFN Created
2.00 1 30-Nov-01 RFN General review to update to current iSCS product
features.
Pg. 2-5 Include reference to UDP and IEC 104
Pg. 5-8 Gateway/Broadcast info added
Pg. 9-2 what is not iSCS block added
Pg. 9-4 Ethernet vs. 802.3
add UCA/IEC 104 info
choosing B100 variant
Pg. 10-4 correct dialog example for services to
show UCA and IEC 104 protocols
2 04-Mar-02 RFN Update to current GE Energy Services standards
3 09-May-03 CH Changes for D200 multi-node device
General SWM0008-2.00-3
Full Release iii
iSCS User's Guide
iv Full Release
iSCS User's Guide
Table of Contents
About This Document ..................................................................................................................................xi

Overview .........................................................................................................................................xi
Purpose of this Document ............................................................................................................. xii
Who is the Audience .................................................................................................................... xiii
Part A: A LAN & IP Networking Primer ........................................................................................ A-1
Chapter 1: Introduction to LANs...............................................................................................................1

Overview ..........................................................................................................................................1
Evolution of LANs...........................................................................................................................2
Components of a LAN .....................................................................................................................3
Chapter 2: Network of Choice: Ethernet...................................................................................................5

Overview ..........................................................................................................................................5
Why Ethernet?..................................................................................................................................6
Suitability .........................................................................................................................................8
Advanced Capabilities......................................................................................................................9
Chapter 3: Ethernet Basics ......................................................................................................................11

Overview ........................................................................................................................................11
What is Ethernet? ...........................................................................................................................12
Ethernet Media ...............................................................................................................................14
Ethernet Addressing .......................................................................................................................18
Chapter 4: Extending Ethernet LANs .....................................................................................................19

Overview ........................................................................................................................................19
Reasons for Linking LANs ............................................................................................................20
The OSI Model...............................................................................................................................21
Communication ..............................................................................................................................22
Chapter 5: Internetworking Devices........................................................................................................23

Overview ........................................................................................................................................23
The Repeater ..................................................................................................................................24
The Ethernet Bridge .......................................................................................................................26
The Router, or Gateway .................................................................................................................29
Chapter 6: Background of the Internet Protocols....................................................................................31

Overview ........................................................................................................................................31
History............................................................................................................................................32
The Internet Protocols ....................................................................................................................33
Internet Protocol Application Services...........................................................................................34
A Layered Set of Protocols ............................................................................................................35
Full Release v
iSCS User's Guide
Chapter 7: Internet Protocols...................................................................................................................37

Overview ........................................................................................................................................37
The Internet Protocol......................................................................................................................38
Transmission Control Protocol.......................................................................................................39
Transport Layer Protocols Other Than TCP ..................................................................................40
Application Layer Protocols...........................................................................................................41
Newer Applications Protocols ....................................................................................................42
Chapter 8: The IP to Ethernet Connection ..............................................................................................43

Overview ........................................................................................................................................43
Addressing in IP / Ethernet Networks............................................................................................44
The Internet Protocol and Addressing............................................................................................45
Networking.....................................................................................................................................48
Physical Network Independence ....................................................................................................49
Serial IP Communication ...............................................................................................................50
Part B: Introduction to iSCS..............................................................................................................B-1
Chapter 9: What is iSCS?..........................................................................................................................3

Overview ..........................................................................................................................................3
The iSCS Concept ............................................................................................................................4
What is iSCS For?............................................................................................................................5
iSCS Architecture.............................................................................................................................7
iSCS Architecture.............................................................................................................................7
LAN Media/Protocols ......................................................................................................................8
Chapter 10: Single or Dual Ethernet LAN..............................................................................................9

Overview ..........................................................................................................................................9
Dual LAN Implementation.............................................................................................................10
Exercise 1: Defining Single / Dual iSCS LAN Project Properties ..................................................12
Configuring iSCS LAN Project Properties ....................................................................................12
Exercise 2: Defining Single / Dual LAN Device Properties............................................................20
Configuring iSCS LAN Device Properties ....................................................................................20
Chapter 11: TELNET and iSCS............................................................................................................27

Exercise 3: Enabling TELNET in an iSCS Device..........................................................................28
Configuring TELNET ....................................................................................................................28
Exercise 4: Enabling TELNET Client Functionality.......................................................................29
Configuring WESMAINT as a TELNET Client............................................................................29
Exercise 5: Enabling TELNET Host Functionality .........................................................................31
Configuring WESMAINT as a TELNET Host ..............................................................................31
Using TELNET WESMAINT........................................................................................................33
Exercise 6: Testing WESMAINT TELNET Access........................................................................34
Using WESMAINT as a TELNET Client......................................................................................34
vi Full Release
iSCS User's Guide
Chapter 12: TFTP File Transfer............................................................................................................37

Overview ........................................................................................................................................37
Exercise 7: Config/Code Down/Upload Using TFTP .....................................................................38
Using TFTP File Transfer ..............................................................................................................38
Chapter 13: Automatic Initialization - BootP .......................................................................................43

Overview ........................................................................................................................................43
BootP Operation.............................................................................................................................44
Windows-Based BootP / TFTP Solution........................................................................................46
Exercise 8: PC Network Settings for BootP / TFTP........................................................................47
Configuring Windows NT4 for BootP / TFTP...............................................................................47
Exercise 9: Installation of the BootP Server Utility ........................................................................50
Installing the BootP Server ............................................................................................................50
Exercise 10: Creating the BootPtab Files......................................................................................52
Configuring the BootP Server ........................................................................................................52
Exercise 11: Installation of the TFTP Server Utility.....................................................................55
Installing the TFTP Server .............................................................................................................55
Exercise 12: Setting-up the TFTP Server Utility ..........................................................................57
Configuring the TFTP Server.........................................................................................................57
Config Pro and BootP / TFTP ........................................................................................................59
Exercise 13: Config Pro Setup for BootP / TFTP .........................................................................60
Defining Project/Device Properties for BootP/TFTP.....................................................................60
Exercise 14: Testing the BootP/TFTP Server ...............................................................................65
BootP/TFTP Server Operation .......................................................................................................65
Normal Startup Cycle.....................................................................................................................70
Chapter 14: Serial IP Connection - PPP................................................................................................71

Overview ........................................................................................................................................71
PPP Operation ................................................................................................................................72
Uses of PPP ....................................................................................................................................73
Exercise 15: Configuring a PC for PPP.........................................................................................74
Configuring Windows NT4 for PPP ..............................................................................................74
Exercise 16: Configuring the Device for PPP ...............................................................................79
Configuring the PPP Application...................................................................................................79
Exercise 17: Testing the PPP Configuration .................................................................................83
Establishing a PPP Connection ......................................................................................................83
Exercise 18: PPP Config Pro - WESMAINT Links......................................................................86
Using PPP to Access WESMAINT from Config Pro ....................................................................86
Chapter 15: Advanced Monitoring Applications ..................................................................................89

Overview ........................................................................................................................................89
Virtual Terminal.............................................................................................................................90
Virtual Connect ..............................................................................................................................91
File Transfer ...................................................................................................................................92
Full Release vii
iSCS User's Guide
Digital Fault Recording..................................................................................................................93

Power Quality.................................................................................................................................94
Other Features of iSCS...................................................................................................................95
viii Full Release

List of Figures
Figure 3-1 10BASE5 Network ...................................................................................................................14

Figure 3-2 10BASE2 Network ...................................................................................................................15
Figure 3-3 10BASE-T Network .................................................................................................................16
Figure 4-1 The OSI 7-Layer Model ...........................................................................................................21
Figure 4-2 OSI Stacks, Point-to-point Communication .............................................................................22
Figure 5-1 Example of a Repeater Used in Linking 10BASE5 LAN Cables.............................................25
Figure 5-2 A Repeater in the OSI Model ...................................................................................................25
Figure 5-3 A Bridge in the OSI Model.......................................................................................................26
Figure 5-4 Learning Bridge Example.........................................................................................................27
Figure 5-5 A Router in the OSI Model.......................................................................................................29
Figure 6-1 The OSI vs. the IP Stack...........................................................................................................35
Figure 8-1 Internet Addressing: Classes ....................................................................................................45
Figure 8-2 Subnetwork Addressing............................................................................................................46
Figure 9-1 iSCS Architecture.......................................................................................................................7
Figure 10-1 Example of Dual-LAN ...........................................................................................................10
Figure 13-1 BootP / TFTP Flowchart.........................................................................................................45
Full Release ix
iSCS User's Guide
x Full Release
About This Document
Overview
Introduction This section of the document will outline what information the document will
provide the reader, and identify what information is not included
It also will identify the target audience for the document.
In this chapter This chapter contains the following topics
Topic See Page

Purpose of this Document xii
Who is the Audience xiii
Full Release xi
iSCS User's Guide
Purpose of this Document
What This This document is designed to provide users with the basic theory and procedures
Document they will need to engineer and configure an Ethernet-based Integrated Substation
Provides Control System, or iSCS.
Using this document, a user will be able to create a complete Ethernet LAN
communication system that can be used as a platform for other subsystems, such as:
DNP 3.0, IEC 104 or UCATM SCADA communication using UDP or TCP/IP
Advanced Monitoring Applications (AMA) that transfer COMTRADE files
using TFTP
Virtual Connection using TELNET
Some of these subsystems are discussed briefly later in this document.
What This This document does not provide:

Document Does
instruction for any of the subsystems that will employ the iSCS communication
Not provide.
platform.
instruction for configuring any applications not related to iSCS
Please refer to the appropriate documents for each of the applications or subsystems,
as required.
Document Style This manual uses the Systeme International (SI) and the Microsoft Manual of Style
and Convention as a basis for styles and conventions.
Rules
Training Tool This document may be used as a self-teaching aid, or as a training manual for a
formal GE Energy Services training program
Technical GE Energy Services representatives are available Monday through Friday, 8:00 a.m.
Support to 5:00 p.m. Mountain Standard Time.
Contacting Us GE Energy Services Toll-Free: + 1.800.518.2303

2728 Hopewell Place NE Phone: + 1.403.214.4600
Calgary, Alberta Canada Fax: + 1.403.243.1815
T1Y 7J7 email:
GEH_Calgary.Support@ps.ge.com
xii Full Release

iSCS User's Guide
Who is the Audience
Job Titles We have designed this document for use by Substation Automation Systems
engineers, application specialists and/or SCADA system and maintenance engineers
who are responsible for installing, configuring and maintaining an iSCS
communication system.
Experience & This Users Guide assumes that anyone using this manual has some prior knowledge
Abilities of:
the electrical industry
personal computer use and terminology
GE Energy Services products
Prerequisites Before performing the steps in the procedures in this document, a user must:
be familiar with the hardware components of the iSCS project
have full Administrator rights to the Windows-based PC
be fully competent in the use of Config Pro V4
Full Release xiii
iSCS User's Guide
xiv Full Release

Part A: A LAN & IP Networking Primer
Overview
Introduction This part of the manual is provided as an introduction to LAN and Internet
networking concepts, and provides some answers to questions like: Why was
Ethernet chosen as a communication platform.
In this Part This Part contains the following Chapters
Topic See Page

Chapter 1: Introduction to LANs 1
Chapter 2: Network of Choice: Ethernet 5
Chapter 3: Ethernet Basics 11
Chapter 4: Extending Ethernet LANs 19
Chapter 5: Internetworking Devices 23
Chapter 6: Background of the Internet Protocols 31
Chapter 7: Internet Protocols 37
Chapter 8: The IP to Ethernet Connection 43
Full Release A-1
iSCS User's Guide
A-2 Full Release

Chapter 1: Introduction to LANs
Overview
Introduction This chapter is designed to assist that reader that is new to LAN technologies.
It provides some insight about why LANs were developed, and what components
actually make up a LAN
Topic See Page

Evolution of LANs 2
Components of a LAN 3
Full Release 1
iSCS User's Guide
Evolution of LANs
Why LANs? With the introduction of the mini-computer in the 70s, and the personal computer in
the 80s, it became apparent that there was a lot of time and money being wasted
because users could not take advantage of the work done by others in their
environment.
A lot of money was spent providing software and peripherals for each user because
here was no easy way for them to share these resources.
What Was A way to interconnect the various computing devices together. The Local Area
Needed Network became the solution to this need.
Characteristics Some of the fundamental functions and characteristics that all LANs have are:
of LANs:
Function Description
Resource Sharing Allow users to share storage devices, printers and
communications devices
Information User can access information on common storage devices, or
Sharing each others systems
Common Access All network devices connect to the LAN using the same
Mechanism techniques
High Speed The large number of devices on a LAN, and the growing
volume of data traffic demands a large bandwidth.
Inexpensive To keep the cost per user down, inexpensive media and
interface hardware is required.
Decentralized LANs should not have an over-reliance on any single
Control component. i.e., a single component failure will not seriously
affect the entire system
Device Devices can be purchased from different sources and added
Independence to the network with a minimum of difficulty
User Control Users are free to define their network parameters as they see
it best to suit their environment.
2 Full Release
iSCS User's Guide
Components of a LAN
Two Groups of A LAN is not just a way of wiring together several devices.
Components
It is the sum of several components that cannot be used independently, but which
work together to provide the desired characteristics. The components necessary to
construct a LAN can be grouped into two categories:
Hardware Components
Software Components
Hardware Hardware components found in LANs include:

Components
Component Examples
Media Coaxial cable, either thick or thin
Twisted-pair wire, can be either shielded or unshielded
Fiber-optic cable
Unbounded (wireless), using infrared or microwave
technology.
Nodes Any intelligent device attached to a LAN is referred to as a
Node.
Types of Nodes include:
PCs and workstations
Servers
Gateways and routers
Interfaces All nodes on a network have some form of interface to
connect the device to the specific LAN media in use.
Examples are:
Network interface Cards (NICs) for servers and PCs.
External bus or parallel port adapters
Integrated interfaces for large computers and
communication devices.
Wiring Centers Often referred to as Concentrators, Hubs or Multistation
Access Units (MAUs), they are most commonly found in
LANs using twisted-pair media.
Full Release 3
iSCS User's Guide
Components of a LAN, Continued
Software There are two primary categories of software found in LANs:

Components
Application Programming Interfaces, or APIs.
Network Operating Systems, or NOSs.
The API These invisible programs interface the hardware components of a nodes LAN
interface with the Network Operating System.
Examples of APIs are:
NetBIOS
APPC
Named Pipes
Berkley Sockets
WINSock
The NOS Provides the interface between the users applications that are running in the node,
and its API.
Some NOSs have separate server and client components. Others operate in a peer-
to-peer mode with similar functionality for each node.
Examples of NOSs are:
Novell NetWare
OS/2 LAN Manager
Banyan Vines
TCP/IP
OSI
NOSs Other A NOS defines the format, or protocol, of the data that is passed from one node to
Important Roles another on a LAN.
These protocols are responsible for:
establishing, maintaining and breaking down, logical connections between nodes
and/or applications
packetizing or framing data for transmission
addressing and routing frames to their destination
verifying the datas integrity once received
security of the information in transit
providing recovery procedures when errors occur.
4 Full Release
Chapter 2: Network of Choice: Ethernet
Overview
Introduction Ethernet is the LAN technology of choice for substation applications.

This chapter will help the reader understand why this choice was made, by
comparing it to other LAN technologies.
Topic See Page

Why Ethernet? 6
Suitability 8
Advanced Capabilities 9
Full Release 5
iSCS User's Guide
Why Ethernet?
A Substation The requirements of a substation LAN can be grouped into three categories :
LAN Requires:
Technical Characteristics
Suitability
Advanced Capabilities
Available LAN Several LAN technologies were chosen for examination including:
Options
Ethernet
Token Bus
Token Ring
Profibus (DP and FMS)
Fiber Distributed Data Interface (FDDI).
Technical The measure of the performance of a LAN, particularly in the substation automation
Characteristics: application, can be measured by analyzing these characteristics:
Bandwidth/Data Throughput
Data Latency
Deterministic nature
Time Synchronization capability
Bandwidth/ Virtually all LAN topologies have the actual bandwidth to handle even the largest of
Throughput present substation communication requirements.
At 10 Mbps, Ethernet has good performance, and the future 100 Mbps variations will
perform even better.
What is Latency? Latency is a measure of the time required for a message to be delivered across a
LAN to its designated destination.
Inherent Latency Token-passing LANs are:

of Ethernet vs.
most efficient when heavily loaded
Token-passing
LANs the least efficient when lightly loaded due to the fact that a significant amount of
time is wasted waiting for the passing of the token.
Conversely, Ethernet is the only viable LAN option that does not use a variation of
token-passing. Delay in an Ethernet LAN is due primarily to the effects of traffic
loading, with delays being almost insignificant when load is small, increasing
exponentially as load increases.
At the light loading typical of a substation LAN, the Ethernet systems will have the
smallest delay (latency) of any LAN type.
Continued on next page
6 Full Release
iSCS User's Guide
Why Ethernet?, Continued
Deterministic A LAN is deterministic when it is possible to calculate the worst case performance,
if the LAN is functioning correctly without errors.
All token-passing LANs can be considered deterministic due to the fact that the
worst-case performance can be calculated, but only if the network is 100% reliable.
Under error conditions, however, Ethernet is less disturbed by noise, physical breaks
and power interruptions than the other LAN technologies. An Ethernet network
experiencing this type of error will simply result in a retransmission of the traffic.
Token-passing systems respond to errors by corrupting or losing the token, which
results in severe delays in re-generating the token.
This means that in the real world of substation LANs, Ethernet is actually more
deterministic.
Time Time synchronization relies on the ability to spontaneously (<1 millisecond) transmit
Synchronization a message whenever a time sync request is made.
In reality, none of the LAN types allow for guaranteed spontaneous transmission.
Ethernet, however, should succeed in excess of 99.9% of the time, given the light
network loading.
Full Release 7
iSCS User's Guide
Suitability
Three Issues There are three main issues in determining the suitability of a LAN type for a
substation system:
Simplicity
Reliability
Environmental Tolerance
Simplicity The simplicity of a LAN type can be broken into several factors:
Ease of installation of network interfaces and media.
Minimal training required to install and maintain the LAN system components.
Accessibility of network components and media.
Choice of media types, with the ease of combining them into one network.
Ethernet type LANs are considered the choice when these factors are considered.
Reliability The topology of a LAN can impact its reliability. For example:
Ring networks are susceptible in that any break in the ring will stop all
communication.
A bus or star topology is more tolerant of media breakage.
If a token master or bus monitor fails, a new master or monitor must be
arbitrated, causing large delays.
Ethernet has no centralized or de-centralized control, removing these
concerns.
With the exception of FDDI, none of the LAN types has a standard for redundancy.
Ethernet, and most other LAN types, can be installed in a parallel LAN
configuration to provide some redundancy.
Environmental None of the LAN standards were developed with criteria such as noise immunity and
Tolerance isolation in mind.
Systems using Fiber-optic cables inherently have the advantage here.
For networks using twisted-pair or coaxial cables, Ethernet is well suited due its use
of baseband Manchester encoding which provides immunity to low frequency AC
noise.
8 Full Release
iSCS User's Guide
Advanced Capabilities
Four Categories Peer-Peer Communications

Application Layer Choices
Multiple Application Layer Support
Standards Advantages
Peer-Peer To support interlocking and intertripping, techniques used to tie control functions
Communication and supervisory information from one network device to another, the LAN must
support peer to peer communications.
Neither the latencies associated with message relaying, nor the dependence on a
third device, and the resulting drop in reliability, can be tolerated.
Application Layer The 802 series and FDDI LANs can support any profile designed to be
Choices implemented over the 802.2 standard (Logical Link Control or LLC).
The IEC 104 and UCA committees have defined standards for communication
over Ethernet type LANs.
The DNP Technical Committee has presented a standardized definition for
transmission of the DNP application layer over an IP network.
Multiple The 802 series and FDDI LANs inherently support implementations of multiple
Application Layer application layers simultaneously.
Support
The Internet Protocol, for example supports applications such as:
TELNET
Bootstrap Protocol (BootP)
File Transfer Protocol (FTP)
Trivial File Transfer Protocol (TFTP)
Simple Network Management Protocol (SNMP)
Profibus supports only two application layers. The service primitives defined at the
Profibus data link layer do not correspond to typical ISO Open Systems
Interconnect (OSI) model primitives making application layer swapping even more
difficult.
Advantages of Through adherence to a standard, many benefits are expected:

Standards
access to third party maintenance and diagnostic tools
easier access to the skills required to maintain the LAN
more choice in compatible protocols and products
better inter-operability
Full Release 9
iSCS User's Guide
Advanced Capabilities, Continued
Most Common Being the most common of the standards, Ethernet derives several benefits:
Standard
Ethernet is always examined when defining new multi-layer communications
protocols.
This is important when considering the ability to upgrade as application layer
protocols evolve (e.g., UCA/MMS).
Other LAN types also become accepted simply because of their
interchangeability with Ethernet through adherence to the 802 family standards.
LAN product vendors tend to make their products compatible with this standard
leading to better connectivity options for Ethernet.
Rating the The overall rating after totaling all these factors was that the LAN options were
Choices ranked in this order:
1. FDDI and Ethernet
2. Token Bus and Token Ring
3. Profibus
When price was taken into account, there are only two feasible choices at this time:
Profibus can be implemented for about $50 per channel making it the least costly
alternative.
Ethernet can be implemented for about $100 per channel making it the most
economically acceptable alternative
10 Full Release
Chapter 3: Ethernet Basics
Overview
Introduction In the early 1980s based on work done by XEROX, INTEL and DEC, the IEEE
established a standard for Ethernet.
This chapter will assist the reader unfamiliar with Ethernet in better understanding
what makes it work, and how it can be used.
Topic See Page

What is Ethernet? 12
Ethernet Media 14
Ethernet Addressing 18
Full Release 11
iSCS User's Guide
What is Ethernet?
Definition A collaboration of DEC, Intel and Xerox developed the original Ethernet.
Eventually the technology was adopted (and modified slightly) by the IEEE who
referred to it as the 802.3 standard.
This standard laid out specifications including:
Baseband Speed of 10 Mbps
A bus topology, i.e., all devices share a common straight-line communication
path.
Network access control method known as CSMA/CD (Carrier-Sense, Multiple
Access with Collision Detection)
CSMA/CD? What does Carrier Sense, Multiple Access with Collision Detection mean?
Term Description
CS Any station wishing to transmit onto the shared media must first
listen for the absence of a Carrier, indicating that the line is no
longer busy, before transmitting.
Once no carrier is sensed, after waiting a randomly generated delay
time, the station can proceed with transmitting its message onto the
network media.
This random delay time is intended to prevent two stations
from transmitting at exactly the same instant, after the carrier
drops.
While sending its message, the station must continue to monitor the
signal on the media, in the event that there is more energy on the
media than the station actually transmitted.
If there is more energy, it would indicate that some other has
transmitted traffic at the same time, or external noise is present.
MA More than two stations can share, or access, the network media.
CD If the transmitting station does detect the presence of too much
energy on the media while transmitting, (a Collision is Detected) it
will generate a jam signal to:
let the rest of the network stations know that a collision has
taken place.
notify the receiving station to discard any data it did receive.
Once the jam signal is complete, all stations are free to resume
communicating, including the affected stations that can now re-
transmit their lost messages.
12 Full Release
iSCS User's Guide
What is Ethernet?, Continued
Collisions are In any Ethernet network, collisions will occur.

Inevitable
With the high bandwidth available, the casual observer rarely notices delays from the
resulting occasional retransmissions.
Statistically, the probability of collisions increases exponentially as network loading
increases. If network load increases too much, performance will be significantly
impacted.
In a worst-case situation, the network can become saturated with retransmissions
and/or broadcast messages, causing a total communication failure.
Full Release 13
iSCS User's Guide
Ethernet Media
The Original The original Ethernet was created using a large diameter coaxial cable, often referred
Ethernet Cable to as Thick Net
Thick Coaxial When the IEEE adopted the technology, and modified it slightly, they named the
Cable thick coaxial cable standard 10BASE5.
The 10 refers to the speed of 10 Mbps
BASE indicates Baseband signaling.
The 5 specifies the maximum length of the coaxial cable as 500 meters.
Unpopular due to its bulk, and complex interfaces known as Attached Unit Interfaces
(AUI), other standards evolved.
Network Server Workstation

Workstation
10Base5 (Thick Net) Ethernet
Transciever
AUI Cable
Network Printer
Workstation
Figure 3-1 10BASE5 Network
14 Full Release
iSCS User's Guide
Ethernet Media, Continued
Thin Coaxial Later, a less expensive, smaller diameter coaxial cable was introduced.
Cable
Sometimes referred to as Thin Net or Cheaper Net, the IEEE assigned this type
the designation 10BASE2
The 2 indicates that the maximum distance that this media is capable of is reduced to
200 meters.
Interfaces for this type of media are usually coaxial T connectors that attach
directly to the Network Interface Card (NIC) of each LAN device.
Network Server
Workstation
10BASE2 (Thin Net)

Ethernet
Network Printer
Figure 3-2 10BASE2 Network
Full Release 15
iSCS User's Guide
Unshielded A limitation of bus networks using a single coaxial cable is that a problem with any
Twisted-Pair single device on the cable, or a break in the cable, can render the entire network
segment useless.
A solution to this problem was developed using unshielded twisted-pair (UTP)
copper wire, in a Star configuration.
At the center of the star is an intelligent Multi-port Repeater, or Hub, where all
twisted-pair segments are terminated.
At the other end of each 100 to 150 Meter segment is a single network node.
In this way, any problem with an individual cable or node can be automatically
isolated from the rest of the network, only affecting only one node.
The IEEE has designated this type of media 10BASE-T
IBM Compatible
10BASE-T Twisted-Pair
Ethernet
Network Printer
Workstation
Hub
Twisted-Pair Wire
Network Server
Figure 3-3 10BASE-T Network
Because most 10BASE-T hubs are repeaters, they are subject to the 4-repeater rule
Note when cascading. Refer to Part A:Chapter 5: Internetworking Devices
16 Full Release
iSCS User's Guide
Fiber-Optic The use of Fiber-optic media for Ethernet networks resolved two more concerns
Cable affecting copper-wire networks:
susceptibility to Electro-Magnetic Interference (EMI) in noisy environments.
distance limitations
Fiber-optic media is virtually immune to EMI, and can be extended to 2 km in length

Fiber is always used in a point-to-point configuration, but can be used in a Star
topology, similar to twisted-pair systems.
The IEEE standard for this media is 10BASE-FL.
Other Standards A newer standard designated 100BASE-X has been growing in popularity.
The 100 indicates a 100 Mbps data rate.
The X would be replaced by the cable designation as implemented.
The IEEE has listed other variations of Broadband standards, referred to as

10BROAD-X that have only found limited application.
Full Release 17
iSCS User's Guide
Ethernet Addressing
Background Any two devices that wish to communicate over an Ethernet LAN Must know each
others Ethernet address.
The device manufacturer typically assigns this address, known as the MAC address
(Media Access and Control), to the network interface when it is made, and is not
normally changeable.
Address Format All Ethernet MAC addresses are six octets in length, or 48 bits.
There are 3 types of addresses:
The physical or burned-in address of a specific network interface.
Broadcast address, represented by all address bits = 1 often represented as:
FF FF FF FF FF FF
By definition, all devices must listen to an address of this type.

Multicast addresses, where the Least Significant Bit of the Most Significant Byte
is set to 1.
A multicast is a limited form of broadcast. A subset of network nodes agrees to

respond to certain multicast addresses.
18 Full Release
Chapter 4: Extending Ethernet LANs
Overview
Introduction As substation LANs grow, there are several products that can be used to help in that
growth.
This chapter helps you plan the best method for making that growth happen.
Topic See Page

Reasons for Linking LANs 20
The OSI Model 21
Communication 22
Full Release 19
iSCS User's Guide
Reasons for Linking LANs
Background There are several reasons why a LAN would need to be extended, or broken up into
multiple sections. Some of these are
The chosen media cannot be stretched far enough to reach all nodes, without
exceeding specifications.
There are more nodes to connect to the network than the media specifications
will allow.
Network load is getting too high, impacting performance and reliability.
Network managers want to restrict some users from accessing certain resources,
while giving access to others.
Linking LANs It may be desirable to link existing localized LANs together to create a larger
Corporate network, or Intranet. Reasons for doing this include:
Providing access to information or services on one LAN to users on another
departmental LAN.
To link two or more remote LANs for similar reasons
Allow management of all networks from one central location
Internetworking Virtually all internetworking products and protocols conform, at least in part, to the
OSI model, created by the International Standards Organization (ISO).
Discussing the basic concepts of this model, often called the 7-layer stack, will help
you understand the functions of various internetworking components.
20 Full Release
iSCS User's Guide
The OSI Model
7 Layer Model In the OSI model, all network devices have software and hardware components that
perform various functions required to reliably communicate over any type of
complex network.
These seven functions, or layers, are shown below in the following figure.
Application Layer
Presentation Layer
Session Layer
Transport Layer
Network Layer
Data Link Layer
Physical Layer
Figure 4-1 The OSI 7-Layer Model
Layer Functions The general role of each of the layers is outlined below, from the top of the stack:
Layer Layer Name Description

7 Application Is not the application being run on the host, but standard
Layer services that are provided to the applications. e.g., file
transfer, terminal emulation, email etc.
6 Presentation Defines the format or layout of data, and its
Layer interpretation. Text or graphic compression may be done
at this layer.
5 Session Establishes, maintains and terminates logical connections
Layer
4 Transport Provides end-to-end reliability by having the destination
Layer host communicate with the originating host
3 Network Provides routing capabilities, including mapping
Layer addresses to locations, and switching
2 Data Link Defines the frame format and addressing, error detection
Layer and frame acknowledgment.
1 Physical Specifies the physical interconnection, including
Layer electrical characteristics of the signals on the interface.
Full Release 21
iSCS User's Guide
Communication
Moving Through Two devices communicating with each other over a direct network connection will
the Layers transmit their messages:
down though the layers of their own stack
across the physical media
then up through the stack layers at the destination end of the circuit.
Responses return by the same path, in the opposite direction
Device 1 Device 2
Application Layer Application Layer

Presentation Layer Presentation Layer
Session Layer Session Layer
Transport Layer Transport Layer
Network Layer Network Layer
Data Link Layer Media Data Link Layer
Physical Layer Physical Layer
Figure 4-2 OSI Stacks, Point-to-point Communication
22 Full Release
Chapter 5: Internetworking Devices
Overview
Introduction To allow LANs to grow, or merge together, there are three types of networking
products that can be used:
Repeaters
Bridges
Routers (Gateways)
The role of each of these devices, and how their roles relate to the ISO model
follows.
Topic See Page

The Repeater 24
The Ethernet Bridge 26
The Router, or Gateway 29
Full Release 23
iSCS User's Guide
The Repeater
Background The main function of a repeater is to overcome the fundamental distance limitations
of all LAN media.
It is a device A repeater
that:
amplifies
reshapes, and
re-times
signals as they pass from one LAN cable to another.
Advantages of a A repeater
repeater
can be used to connect one type of media to another, i.e., fiber to coaxial cable.
does not actually examine or process any data.
are very fast, causing virtually no perceptible delay to network traffic.
can be used to isolate a network cable when a physical problem exists on that
section.
Limitations: Limitations of repeaters:

Ethernet specifications restrict the number of sequential repeaters that can be
used in building a single LAN. This is referred to as the 4-repeater rule where an
Ethernet network can have a maximum of 5 sections of media separated by a
maximum of 4 repeaters
Repeaters are invisible to LAN traffic, and therefore cannot easily be
controlled by a Network Manager
Because they only operate at the Physical Layer of the OSI model, they cannot
distinguish good signals from bad, and therefore cannot filter out noise or
improperly formatted frames.
24 Full Release
iSCS User's Guide
The Repeater, Continued
A Repeater in
Use
Network Server Workstation Workstation
10BASE5 (Thick Net) Ethernet
Transciever
AUI Cable
Printer
Repeater
Network Server Workstation

AUI Cable
10BASE5 (Thick Net) Ethernet
Transciever
Printer
Workstation
Figure 5-1 Example of a Repeater Used in Linking 10BASE5 LAN Cables
The Repeater
and OSI Model
Device 1 Device 2

Network Layer Network Layer
Data Link Layer Data Link Layer
Physical Layer Repeater Physical Layer
Figure 5-2 A Repeater in the OSI Model
Full Release 25
iSCS User's Guide
The Ethernet Bridge
Definition By definition, a Bridge is used to interconnect two LAN segments, operating at both
the Physical and Data Link Layers of the OSI Model.
This is shown graphically in this diagram.
Device 1 Device 2

Network Layer Bridge Network Layer
Data Link Layer D/L Data Link Layer
Physical Layer P P Physical Layer
Figure 5-3 A Bridge in the OSI Model
A Two Level Because a bridge operates at both the Physical and Data Link levels, it can recognize
Device the Data Link components of data frames, as they appear on the LAN segments.
In addition to the basic functions of a repeater:
It is a device can learn network devices Ethernet source addresses and

that: store them in address tables, one for each interface.
checks frames for errors, and discards them if necessary.
working together with other bridges in the same LAN can
provide redundant link capability. This process requires that the
bridges utilize the Spanning-tree Algorithm (IEEE 802.1
standard) to prevent duplicate paths from occurring.
NOTE: Bridged Ethernet LANs all logically belong to the same LAN.
The separate parts of a bridged LAN are referred to as Segments.
26 Full Release
iSCS User's Guide
The Ethernet Bridge, Continued
Advantages of Learning bridges are capable of isolating frames carried on one segment from
Bridges forwarding to another segment, if both the source and destination Ethernet addresses
are on the same side of the bridge.
The following diagram illustrates this.
Network Server A Workstation A Workstation
10BASE5 (Thick Net) Ethernet Segment A
Transciever
AUI Cable
Printer
Bridge
Network Server B Workstation
AUI Cable
Segment B 10BASE5 (Thick Net) Ethernet
Transciever
Printer
Workstation
Figure 5-4 Learning Bridge Example
Learning Bridge Over time, the bridge in the center of the above diagram will learn the Ethernet
Operation (MAC) address of each of the network nodes on both Segment A and Segment
B.
If the bridge sees frames from Workstation A that have a destination address for
the Server A, it will know that it does not need to forward those frames across to
Segment B. This is referred to as Filtering.
Conversely, if the same workstation sends a frame to the address of Server B on
Segment B, the bridge knows to pass the frame on to its destination. This is
referred to as Forwarding
Some bridges have configurable tables that can be used to prevent the
forwarding of frames from an address on one segment to a specific address on
another segment.
Full Release 27
iSCS User's Guide
The Ethernet Bridge, Continued
Advantages, If a LAN can be set up so that the stations on one segment primarily exchange
(continued) frames with other stations on the same segment, the load on each segment can be
greatly reduced.
Spanning-tree bridging can provide for more network reliability, through the use
of redundant links.
Limitations: Bridges are more expensive than repeaters.

Generally are slower and delay traffic more than the simpler repeater.
Because they do not look at the content or type of data in the frames passing
through, they cannot be used for any type of protocol security.
Unknown destination addresses, and broadcast addresses, are always forwarded
through a bridge.
A condition known as a broadcast storm cannot be prevented using a bridge.
Two Types of The functionality of the Data Link Layer of the OSI model has been further divided
Bridges: into two sub layers:
The lower half, adjacent to the Physical Layer, is known as the Media Access
and Control (MAC) sub layer.
The upper half is known as the IEEE 802.2 Logical Link Control, or LLC sub
layer.
MAC Bridges Bridges that only use the MAC sub layer of the Data Link Layer can only be used to
bridge between Ethernet segments.
LLC Bridges LLC bridges can be used to convert LANs from one Physical Layer to another. For
example: Ethernet to Token-ring bridging.
Because of the difficulty in converting Ethernets Spanning Tree information into
Source Routing, as used in Token-ring networks, this type of bridging is more
expensive, and much less common.
28 Full Release
iSCS User's Guide
The Router, or Gateway
Definition Also called Gateways in the IP world, Routers are devices that are used to
interconnect LANs, operating at the Physical, Data Link and Network Layers of the
OSI Model.
This is shown graphically in Figure 5-5.
Device 1 Device 2

Transport Layer Router Transport Layer
Network Layer N/W Network Layer
Data Link Layer DL DL Data Link Layer
Physical Layer P P Physical Layer
Figure 5-5 A Router in the OSI Model
A Three Layer Because Routers operate at the bottom three layers of the OSI model, they have the
Device Network Layer functionality necessary to intelligently determine the best path
through complex networks.
Some of the other features that are unique to routers are that it:
can be used to convert LAN types
can be used as a Fire Wall
can inter-operate with other routers by using standard routing algorithms
Conversion of Routers can be fitted with different LAN interfaces allowing them to pass traffic
LAN Type from an Ethernet LAN to a Token-ring LAN.
Note: The network protocol must be common to both LANs
Fire Walls Because a router has the capability of recognizing certain data formats and types, it
can be programmed to not forward certain types of messages, while allowing others.
For example:
protocol broadcasts or multicasts
specific protocols
specific addresses or ranges of addresses
Full Release 29
iSCS User's Guide
The Router, or Gateway, Continued
Standards Based Allows routers manufactured by different vendors to operate together in a system.
This is done primarily through the use of standard routing algorithms like:
RIP, or Routing Information Protocol
OSPF, or Open Shortest Path First
EGP, or Exterior Gateway Protocol
Limitations The main disadvantages of routers are the costs associated with:
higher price associated with higher complexity
administration and configuration time.
reduced performance resulting from the increased processing of traffic.
Another limitation of an IP Gateway is that they cannot forward Ethernet broadcast
or multicast frames. This means that any process that uses ARP or RARP, such as
BootP, cannot be used outside of a local LAN.
30 Full Release
Chapter 6: Background of the Internet
Protocols
Overview
Introduction With the physical Ethernet network in place, the movement of traffic over that
network must be managed by a structured set of rules.
For GE Energy Services iSCS networks, the Internet Protocol Suite has been
chosen to provide those rules.
This chapter will provide some of the background information that a reader will find
useful in understanding the implementation of this protocol in an iSCS system.
Topic See Page

History 32
The Internet Protocols 33
Internet Protocol Application Services 34
A Layered Set of Protocols 35
Full Release 31
iSCS User's Guide
History
The Roots of the In the 60s, development of packet switching technology, by Bolt, Baranek and
Internet Newman (BBN), was funded by the US Dept. of Defense Advanced Research
Protocols Projects Agency (originally ARPA, now called DARPA)
In 1969, Universities in California, Utah and the Standford Research Institute first
demonstrated the technology.
In 1975, BBN initiated Telenet, the first public Packet Switched Network (PSN)
More History The technology was incorporated into the Arpanet in 1981 as the only protocol that
would be used. The term Internet is coined at this time.
Beginning in 1983, the Arpanet was dismantled and divided into several
interconnected networks including:
the DDN, (which includes the MILNET, a large military network),
NSFNET (1985-6)
CSNET, and the
BITNET
More milestones are listed below:
Year Change
1990 the Arpanet was totally dissolved
1991 Gopher, a menu driven search tool was developed
1993 the WWW was released by CERN in Switzerland using HTTP
(Hypertext Transfer Protocol)
1993-4 MOSAIC and Netscape Navigator released as browsing tools
32 Full Release
iSCS User's Guide
The Internet Protocols
Background Because the Internet Protocol suite was developed by DARPA, primarily a funding
agency for network research, it is not a commercial product.
It has evolved without the endorsement of any standards agencies.
The Internet The IAB is the group that sets the long-term direction for the Internet.
Activities Board
IAB It is responsible for maintaining the older IEN (Internet Engineering Notification)
and more recently, the RFC (Request for Comment) reporting and information
systems.
IEN and RFC The IEN process is no longer used, but may still provide useful information.
It was used for informal dialogue with the regulatory bodies.
The RFC is used to propose additions or changes to protocols, reports of work,
and release of official standards.
It is also a source of information about almost anything IP related, including
tutorials
Why is the IP It was incorporated into UNIX 4.2 BSD in 1982, marrying the Internet Protocol
Suite so Popular? and UNIX
IP support is integrated into most variations of UNIX free of extra cost.
Also in 1982, the Address Resolution Protocol (ARP) was added to map IP
addresses to Ethernet addresses.
This was fundamental in the development of (diskless) client-server
applications.
Later, SUN added its Network File System (NFS) protocol to the Internet
Protocol implementation on SUN workstations
The "Internet TCP and IP are only two of the protocols in the suite.
Protocol Suite"
These, plus UDP and ICMP, provide "low level" functions required for many
application services.
Abbreviation Protocol
IP Internet Protocol
TCP Transmission Control Protocol
UDP User Datagram Protocol
ICMP Internet Control Message Protocol
Full Release 33
iSCS User's Guide
Internet Protocol Application Services
"Traditional" These services were among the first to evolve as standard components of the IP
Application suite:
Services
Application Function
File Transfer An (authorized) user on any computer can send or receive
Protocol (FTP) files from another computer
Remote Login A user on one computer can "log into" another computer on
(TELNET) the same network
Computer Mail A user can send a file to another user's mail file
(SMTP)
Newer
Application These application services were added later as standard components of the IP suite:
Services
Application Function
Network File Allow a user to access files on another computer. Provides
Systems (NFS) the illusion that the files are on another disk drive on the
user's own computer.
Remote Printing Allows users to print on another computer (or server) as if
the printer was attached to their own computer.
Remote Execution Allows a user to run a process on a different computer
Name Servers Provides a central database for cross-referencing host
names, addresses, users and passwords etc.
Terminal Servers A dedicated host programmed to run a TELNET application
Attached asynchronous terminals can simply ask for the
name of the computer to log into
Network-oriented Allows a program to use a bit-mapped display on a different
Window Systems computer
Network An application which can interrogate, or receive messages
Management from network devices and generate a report on system
(SNMP) performance and status.
34 Full Release
iSCS User's Guide
A Layered Set of Protocols
What is the Method of interconnecting physical networks

Internet Set of rules that allow computers on these networks to communicate
Protocol?
Does not define or restrict the type of physical network
OSI vs. IP Figure 6-1 The OSI vs. the IP Stack below shows some of the IP Protocols, as they
are used in an Ethernet type of network.
It illustrates the approximate comparison of the IP stack layers compared to the OSI
stack layers
Note: There is no direct correlation between the IP and OSI stacks. They are
only shown this way for comparison.
NOTE: The Internet Protocols only define the top three layers of the IP stack.
OSI Layer IP Layer
Application Application TEL FTP IEC UCA DNP TFTP BootP

NET 104
Presentation
Session Transport TCP UDP ICMP
Transport
Network Internet IP
IEEE 802.2 Logical Link Control (LLC)
Data Link Network
Interface IEEE 802.3 CSMA/CD (Ethernet) (MAC)
Physical Hardware 10BASE-X
Figure 6-1 The OSI vs. the IP Stack
Full Release 35
iSCS User's Guide
36 Full Release
Chapter 7: Internet Protocols
Overview
Introduction The Internet Protocol Suite is made up of a collection of services that provide a range
of functionality.
This chapter provides basic details about many of the most common protocol
services that will be used in an iSCS project.
Topic See Page

The Internet Protocol 38
Transmission Control Protocol 39
Transport Layer Protocols Other Than TCP 40
Application Layer Protocols 41
Newer Applications Protocols 42
Full Release 37
iSCS User's Guide
The Internet Protocol
IP The most fundamental Internet Service, IP is:

unreliable
delivery not guarantied, will not detect lost or duplicated data
connectionless
each packet treated independently
packets could use different paths through a complex network, and data could
arrive out of sequence because of different path delays
IP Defines the basic unit of data transfer, and

the exact format of data
Contains a set of rules specifying how errors should be handled, and how packets are
processed.
The Datagram is the basic unit of transfer at the IP level. The Datagram:
has a header and data field
header includes Internet (IP) source and destination addresses, not physical
addresses
Encapsulation IP Datagrams are software packets that have to be transported by Data Link, or
hardware, frames or packets.
Encapsulation is the carrying of a datagram in a physical network frame
The maximum size that an encapsulated datagram can be depends on the
physical frame size of the transport system.
IP Addressing All the Internet Protocol networks, whether private or part of the Internet, use the
same addressing convention.
All addresses must fall within the range of, in decimal:
000.000.000.000 to 255.255.255.255
If not connecting to the Internet, a local administrator can assign (almost) the entire
address in any way he sees fit.
Note: IP addressing is discussed in more detail in Chapter 8: The IP to Ethernet
Connection.
38 Full Release
iSCS User's Guide
Transmission Control Protocol
TCP Is the second most important service, TCP:

is a Multiplexing interface between application programs and the IP delivery
service.
ensures that data delivered is in the same order as it was sent.
sets up a virtual connection before data is transferred.
communicates in Full Duplex mode.
is a Reliable delivery system provided by the Internet Suite.
may be used with other packet delivery systems besides IP.
is not a software package, just a set of rules.
TCP Specifies: the format of data, and the acknowledgments used to insure reliable delivery.
procedures used to make sure data arrives correctly.
how machines recover lost or duplicated packets.
how TCP software can tell the difference between several destination
applications (ports) on one machine.
how two machines set up and break connections.
TCP Does Not Details on how an application program interfaces with TCP.
Specify:
this increases flexibility to whatever operating system the computer is using.
Application Data Data coming in from an application is a Stream of octets, not packets.
Flow Broken-up
TCP divides the stream into Segments that are handed down to the IP layer,
ultimately to become Datagrams.
Note: The size of the segments can be controlled as a form of flow control.
Uses of TCP UDP is used as an interface between IP and application layer protocols like:
TELNET
FTP
DNP 3.0
IEC 104 and,
UCA RFC 1006
Full Release 39
iSCS User's Guide
Transport Layer Protocols Other Than TCP
UDP User Datagram Protocol is a connectionless datagram delivery service that does not
guarantee delivery.
UDP is used when:
messages and responses are short. i.e., do not require sequencing.
communication links are point-to-point, ensuring that all datagrams arrive in the
order they were sent.
time-sensitive data cannot tolerate the added delays of TCP processing. i.e.,
UDP is more deterministic that TCP.
Uses of UDP UDP is used as an interface between IP and application layer protocols like:
SNMP
NFS
TFTP
BootP
DNP 3.0
ICMP The Internet Control Message Protocol:

is a required part of all IP implementations.
destination is within the IP stack, not a higher layer protocol. Therefore, it does
not require port numbers.
like UDP, ICMP is connectionless and does not require sequence numbers.
used for network error messages, or to interrogate network devices.
message is carried in IP datagram.
40 Full Release
iSCS User's Guide
Application Layer Protocols
The Three File Transfer Protocol (FTP)

Traditional Remote Terminal (TELNET)
Protocols:
Computer Mail (SMTP)
FTP Used to transfer files between hosts on the Internet.

There are two types of FTP:
Type Description
Anonymous FTP allows any user to access computers which contain file
archives.
Full-service FTP is used when a user has accounts on multiple hosts, and
wishes to move files between them.
TELNET The Internet standard protocol for remote terminal connection

A terminal or host at one site can exchange data with a host at another site.
A user must have accounts on both hosts, and must log into both.
Once connected, the illusion is that the terminal is directly connected to the
remote host.
A host that requests a connection to another is called a TELNET Client.
A host that is a service for terminal users is called a TELNET Host.
SMTP Simple Mail Transfer Protocol

Users maintain files on their own hosts.
Users could add files to other users mail files.
Ultimately, mail servers were used.
Early PC implementations of IP did not support mail.
Full Release 41
iSCS User's Guide
Newer Applications Protocols
More recent Remote Login (RLOGIN)

Additions Trivial File Transfer Protocol (TFTP)
Bootstrap Protocol (BootP)
Network File System (NFS)
RLOGIN Used by users who log into TELNET Hosts.

Remote Login is a protocol that simplifies the login process by allowing the user to
log into a network host without the additional step of entering another username or
password.
TFTP Trivial File Transfer Protocol is used to transfer software images or files from a host
node to a target node.
Often used to download code and configuration files to devices on the same LAN.
BootP The Bootstrap Protocol is by network nodes to request configuration information

files from a BootP server.
Can use the RARP process to download the IP address. More on RARP in
Chapter 8:
is often used in conjunction with TFTP.
NFS The Network File Systems protocol as developed by SUN Microsystems, uses UDP,
and allows mounting of files across multiple computers.
Useful for diskless workstations, it allows all files and commands to access the NFS
mounted disk as if it were a local disk.
SNMP Simple Network Management Protocol used by central management stations is a

protocol used to request and collect data from network devices.
It also defines the format for this data.
42 Full Release
Chapter 8: The IP to Ethernet Connection
Overview
Introduction Historically, the Internet Protocols and Ethernet have been associated for longer than
any other LAN networking system.
This chapter shows how the two components work together to provide a total
networking solution.
Topic See Page

Addressing in IP / Ethernet Networks 44
The Internet Protocol and Addressing 45
Networking 48
Physical Network Independence 49
Serial IP Communication 50
Full Release 43
iSCS User's Guide
Addressing in IP / Ethernet Networks
The Problem: Two IP devices must know each other's IP address to communicate, and
Two Ethernet nodes must know each other's Ethernet addresses to communicate.
What happens when only one of the two addresses is known?
A Possible The devices could keep a permanent table in each network host with matched pairs
Solution? of Internet and physical addresses for other hosts on the network.
It becomes very difficult to add or change devices in a large network. i.e.. all
devices must be manually reprogrammed.
A better solution was created to automate the creation of these tables.
Address How it works:

Resolution
A device on an Ethernet LAN wants to communicate with another, but only
Protocol - ARP
knows the others IP address.
It broadcasts an ARP request containing the destination IP address onto the
Ethernet bus.
All devices on the network will hear the broadcast, but only the one matching the
requested IP address will respond.
The ARP reply, with matched IP and Ethernet addresses, will be stored in the
sender's ARP table for future reference.
More on ARP ARP table entries are usually given a Time-To-Live (TTL) so that they will be
discarded if not used for a set period of time.
this allows for network changes, and
it prevents ARP tables from growing too large over time.
Other devices on the network can listen-in on the ARP process, and use the
information to update their own ARP tables.
This is sometimes referred to as Promiscuous ARP.
Another What happens when a diskless workstation knows its own Ethernet address but does
Problem: not know its IP address?
The device will broadcast a Reverse ARP request onto the network
Reverse ARP - A RARP server will process the RARP request, and send a RARP reply back to the
RARP device telling it what its IP address is.
Note: Usually a RARP server has to be programmed by an administrator. i.e.., if
a device is added or replaced on the network, the server table has to be
manually changed.
RARP is commonly used as part of a BootP process.
44 Full Release
iSCS User's Guide
The Internet Protocol and Addressing
Address Format Review:

All the Internet Protocol networks, whether private or part of the Internet, use the
same addressing convention.
All addresses must fall within the range of, in decimal:
000.000.000.000 to 255.255.255.255
Internet The Network Information Center (NIC), or other controlling body, assigns the Class
Addressing: and the NetID portion of address.
Classes
Network devices look at the first bits of the address to see what class has been
assigned. The three main classes are described here:
Class A allows for 126 networks with up to 16 million hosts each.
Class B allows for over 16 thousand networks with up to 65,000 hosts each.
Class C allows for over 2 million nets with up to 255 hosts each.
Bit # 0 1 2 8 16 24 31
Class A 0 NetID HostID
Class B 1 0 NetID HostID
Class C 1 1 0 NetID HostID
Figure 8-1 Internet Addressing: Classes
Reserved 0 is reserved for network devices that don't know their own address
Addresses 255 is used for broadcasts to all devices on the network
Addresses should never start with 0, 127, or any number above 223
Full Release 45
iSCS User's Guide
The Internet Protocol and Addressing, Continued
Subnetworking Is used by organizations with many small networks, wishing to combine them into
one internetwork
The HostID part of the address is broken down into divisions.
Users on outside cannot see subnetwork divisions.
Host A Host B
128.6.4.1 128.6.4.2
Subnetwork 128.6.4.0
Network 128.6.4.3
Address
Internet Gateway
128.6.0.0
128.6.5.3
Subnetwork 128.6.5.0
128.6.5.1 128.6.5.2
Host C Host D
Figure 8-2 Subnetwork Addressing
Subnetwork The example network has been assigned a Class B network address of 128.6.0.0 ,
Addressing and the gateway is configured to break the HostID into 2 subnets:
(Refer to 128.6.4.0 and 128.6.5.0

Figure 8-2)
This use of the third octet as a Sub-NetID is sometimes called Class C
subnetworking.
46 Full Release
iSCS User's Guide
The Internet Protocol and Addressing, Continued
NOTE: The HostID portion of an address does not have to be broken up into 8 bit pieces.
Some implementations allow the HostID to be sub-divided into Sub-NetIDs as often
as necessary.
Subnet Mask Internet standards specify that a site using subnet addressing must choose a 32-bit
mask for all of their network nodes (hosts).
NetID bits, including the Subnet ID bits, are all set to 1, and 0s are used to identify
the HostID part of the mask.
The Subnet mask for the previous example would become:
11111111.11111111.11111111.00000000
Note that this is often written as:
255.255.255.000
or
FF.FF.FF.00
but should be thought of as ones and zeros.
Full Release 47
iSCS User's Guide
Networking
Two Types of IP Direct Routing

Routing: a packet can be sent directly from one machine to another. i.e., they are on
the same physical (sub)network.
Indirect Routing
a packet cannot be sent directly and must be intercepted by a gateway
(router) and sent to the destination machine. i.e., they are on different
physical (sub)networks.
Which One? How does a Device Know Which to Use?

It compares the Network Identifier (NetID) part of the destination IP address with its
own (source) NetID.
If they are the same, they are on the same network and can use direct routing.
Conversely, if they are different, it will have to identify a gateway to send
packets to.
In some cases, a "default" gateway will be used to simplify the decision process.
Default In some cases, an IP network will have more than one Gateway to other networks.
Gateways
One is usually designated as the Default Gateway.
This default will be the first one interrogated by network devices when Indirect
Routing is required.
If the default is not the best gateway, it will forward, or redirect the packets to
the better one.
48 Full Release
iSCS User's Guide
Physical Network Independence
Any Network IP specifications do not specify the nature of the physical networks used to build an
Type internet.
Any network, or mix of networks, that use a packet or framing system can be used.
These include X.25, Frame Relay, Ethernet, Token Ring, Arcnet or serial line
encapsulation.
MTU Defined The Maximum Transfer Unit:

is the maximum number of octets a physical frame is allowed to transfer in its
data field.
When setting up a connection, IP negotiates an appropriate size for the datagram.
IP can only see the networks that the nodes are actually attached to.
If along a communication path, a datagram runs into a network with a smaller
MTU, the original datagram is split up into fragments and later reassembled.
Fragments Each fragment is reduced in size to fit into the MTU of the newly encountered
physical frame.
Fragments of fragments are not allowed. i.e., a datagram can only be fragmented
once.
Fragments are only reassembled at final destination, no matter how many
gateways are encountered along the way.
Full Release 49
iSCS User's Guide
Serial IP Communication
Two Main Types Serial Line Internet Protocol (SLIP) is the oldest, and is restricted to IP
communication.
Point-to-Point Protocol (PPP) is more recent, and can be used for other
protocols, if necessary.
SLIP is a protocol used for point-to-point serial connections using IP only.

Links can be either synchronous or asynchronous.
Links can be dedicated or dialup.
Devices on each end must have SLIP software running.
How it Works Slip is a framing protocol that:

only defines a sequence of characters that frame IP packets on a serial line.
does not provide a mechanism to allow hosts to exchange addressing
information.
does not detect errors, this is left to IP.
A Variation: When used for character-mode communication, SLIP is inefficient. i.e. the TCP and
Compressed IP headers together consume at least 40 octets.
SLIP - CSLIP
The Van Jacobson compression algorithm is used to reduce the header to
between 3 and 5 octets.
Only the header is compressed.
PPP The Point-to-Point Protocol adds error detection and link parameter negotiation to
SLIP and CSLIP.
LCP (Link Control Protocol) is used to automatically negotiate frame size,
compression on or off, and control character escaping.
Automates the connection process.
Unlike SLIP and CSLIP, it has a Type field, allowing other protocols to be
carried within its frames.
Is becoming a standard for interoperability between different vendors' router
products.
50 Full Release
Part B: Introduction to iSCS
Overview
Introduction The chapters in this part of the document provide the background information and
exercises to assist a reader in building, configuring and operating an iSCS network.
In this chapter This Part of the document contains the following Chapters and Exercises:
Topic See Page

Chapter 9: What is iSCS?
Chapter 10: Single or Dual Ethernet LAN
Exercise 1: Defining Single / Dual iSCS LAN Project Properties 12
Exercise 2: Defining Single / Dual LAN Device Properties 20
Chapter 11: TELNET and iSCS
Exercise 3: Enabling TELNET in an iSCS Device 28
Exercise 4: Enabling TELNET Client Functionality 29
Exercise 5: Enabling TELNET Host Functionality 31
Exercise 6: Testing WESMAINT TELNET Access 34
Chapter 12: TFTP File Transfer
Exercise 7: Config/Code Down/Upload Using TFTP 38
Chapter 13: Automatic Initialization - BootP
Exercise 8: PC Network Settings for BootP / TFTP 47
Exercise 9: Installation of the BootP Server Utility 50
Exercise 10: Creating the BootPtab Files 52
Exercise 11: Installation of the TFTP Server Utility 55
Exercise 12: Setting-up the TFTP Server Utility 57
Exercise 13: Config Pro Setup for BootP / TFTP 60
Exercise 14: Testing the BootP/TFTP Server 65
Full Release B-1
iSCS User's Guide
Serial IP Communication, Continued
In this chapter (continued)
Topic See Page

Chapter 14: Serial IP Connection - PPP
Exercise 15: Configuring a PC for PPP 74
Exercise 16: Configuring the Device for PPP 79
Exercise 17: Testing the PPP Configuration 83
Exercise 18: PPP Config Pro - WESMAINT Links 86
Chapter 15: Advanced Monitoring Applications
B-2 Full Release

Chapter 9: What is iSCS?
Overview
Introduction The Integrated Substation Control System, or iSCS, is not a single product.
The term iSCS:
defines the characteristics, features and capabilities of the components of a
complete Ethernet LAN-based substation automation and control communication
system.
specifies that the Internet Protocol Suite is the foundation for all
communication within these substation automation systems.
identifies all of the compatible hardware and software components and products
that are to be used when integrating an iSCS network.
Topic See Page

The iSCS Concept 4
What is iSCS For? 5
iSCS Architecture 7
LAN Media/Protocols 8
Full Release 3
iSCS User's Guide
The iSCS Concept
iSCS Defined iSCS is an open architecture, high performance substation automation network
incorporating GE Energy Services products as well as third party products.
The use of a high speed LAN as a backbone permits a greater level of:
Integration
Distribution of network architecture
Functionality.
The iSCS The GE Energy Services hardware products that can be used in an iSCS are:
Hardware
D20 VME
D200
D25
PowerLink
Common To be incorporated into an iSCS, all system components must share these features:
Features
Ethernet LAN interface(s)
TCP/UDP/IP communication capability
What is Not The physical LAN that supports iSCS communication can also be used to support
iSCS? other types of communication concurrently. Examples of protocols that can be used
include:
personal computer network protocols such as Novell, NetBIOS and LAN
Manager.
control center to control center protocols, such as ICCP, running over an OSI
communication protocol.
GE Energy Services implementations of UCA applications using OSI
communication protocols like TP4/CLNP.
None of these examples are considered a part of an iSCS system.
4 Full Release
iSCS User's Guide
What is iSCS For?
Legacy Protocols Over the past decades, many proprietary SCADA (Supervisory, Control And Data
Acquisition) communications protocols have been developed. The majority of these
protocols had been developed with the same goals. Some of these goals were:
Operate in a Master-slave mode
master (station) has control over entire network
master determines when it wants information, no provision for a slave that
needs to report an alarm
Communicate as efficiently as possible over low-speed (serial) data links.
communication is primarily over long-distance master-remote links
protocol overhead is minimized
only raw data is transmitted
data identified by point number only
Report time-sensitive information as quickly as possible.
data is reported with minimal pre-processing
data is packaged into relatively small packets to minimize delays
Provide a secure and timely control mechanism.
Select-Before-Operate (SBO) verification procedures used
choices of variables such as duration and repetition counts defined at remote,
rather than transmitted as part of control message
Goals of Modern Newer SCADA protocols are being developed to achieve more aggressive goals that
SCADA include (but are not limited to):
Protocols
Use established OSI-based network standards.
open protocols open door to multi-vendor implementations
more readily accepted by international communities
Peer-to-peer operation.
unsolicited reporting of alarms
fast control interlocking between IEDs
Broadcast / multicast communication.
synchronized control commands to multiple remotes
network freeze commands
Object-oriented information reporting.
objects contain information such as: description, resolution, scaling factor,
quality, etc., as well as the actual data.
master can use description instead of point number to identify the source of
object data.
Full Release 5
iSCS User's Guide
What is iSCS For?, Continued
Support for The trade-off that these newer protocols have encountered is that they have much
These New higher overhead, making them much less effective when using traditional low-speed
Protocols and SCADA networking techniques.
Devices
In addition to increased overhead, these new protocols are tasked with the
transportation of much higher data volumes, due in part to the increase in processing
power of network devices.
This increase in data volume and overhead has, in turn, demanded a substantial
increase in network bandwidth.
A Solution: iSCS GE Energy Services introduced the iSCS LAN concept to address these
Networks requirements.
iSCS LAN software components can be incorporated into many of GE Energy
Services products, including:
D20 and D200 series devices
D25 Multifunction IEDs, and
PowerLink SCADA GUI
What Protocols iSCS networks can now support these SCADA network protocols:
Does iSCS
DNP 3.0
Support?
network devices using DNP 3.0 protocol can now communicate using either
TCP/IP or UDP/IP over a LAN or internet system
IEC 104
devices using the serial IEC 101 protocol have been enhanced to provide
IEC 104 TCP/IP LAN support.
UCATM
devices using the UCATM system can now communicate over an iSCS using
the RFC 1006 based TCP/IP implementation.
For more information about GE Energy Services implementation of these protocol
applications, refer to the appropriate Configuration Guides. For background on
UCA, refer to Introduction to UCA.
6 Full Release
iSCS User's Guide
iSCS Architecture
iSCS Figure 9-1 iSCS Architecture illustrates some of the connectivity options that an
Architecture iSCS can utilize.
The features of the components of an iSCS are outlined in the following chapters.
GUI
Remote PowerLink WEB Client
To Enterprise
SCADA/EMS Masters
Intra/Internet Communications
WAN
GUI
GUI
GPS Receiver Bridge/Router
Redundant PowerLink Server
D200 Server/Gateway
Dual Ethernet LAN
Digital
Fault Fibre Optic Cables
Recorder
I/O
D25 Gateway
Status
I/O
Controls
I/O IEDs
I/O IED's for
Analogs
Protection
AC inputs IED at
I/O I/O
circuit breaker
Distributed
I/O
Outdoor Locations
iSCS Architecture
Figure 9-1 iSCS Architecture
Full Release 7
iSCS User's Guide
LAN Media/Protocols
IP / Ethernet Many of the applications that can be used in an iSCS network rely on the
Features of iSCS functionality that is inherent to many Ethernet networks using the Internet
Protocol Suite.
Some of the features that can be implemented in the iSCS architecture are:
Dual Ethernet LANs
Automatic Initialization (BootP)
File Transfer (TFTP)
Remote terminal access (TELNET)
Virtual Connection
Ethernet LAN While the term Ethernet is used generically for this type of network, iSCS
Type networks can actually be designed to follow either the Ethernet Type II or the IEEE
802.3 Standard.
The DNP 3.0, IEC 104 and UCAs RFC 1006 protocols can use either variant by
specifying the version of B100.
Note: At the present time, the choice of Ethernet variants must be determined
when the application software is specified for each network device. As a
guideline, this table may help you to determine which choice to use:
To choose this variant: order IP Protocol Stack version:

Ethernet Type-II B100-0
IEEE 802.3 B100-8
UCA OSI The GE Energy Services UCA OSI TP4/CLNP and GOOSE protocol
Networks implementations use integrated stack software that can automatically switch between
Ethernet and 802.3.
They do not require the services of either variant of B100 because they are not
using the Internet Protocol.
Select the B100 variant based on other internetwork applications such as TELNET,
BootP or network management that require the services of the IP stack.
Interface Options Interface options for the GE Energy Services network devices include:
Thin coax, or 10BASE2
Unshielded Twisted-Pair (UTP), or 10BASE-T
Fiber-optic, or 10BASE-FL
All interfaces are available with two independent connections.
8 Full Release
Chapter 10: Single or Dual Ethernet LAN
Overview
Introduction All GE Energy Services iSCS devices support either one or two physical Ethernet
LAN interfaces.
Dual LANs can be configured for added security and reliability.
With the iSCS LAN platform defined, other types of applications can be set up to use
the communications path, for example:
TELNET for remote WESMAINT access and testing.
BootP and TFTP configuration management.
DNP 3.0, UCAs RFC 1006, and/or IEC 104 SCADA communication protocol
support.
Power Quality data file transfer.
Topic See Page

Dual LAN Implementation 10
Exercise 1: Defining Single / Dual iSCS LAN Project Properties 12
Configuring iSCS LAN Project Properties 12
Exercise 2: Defining Single / Dual LAN Device Properties 20
Configuring iSCS LAN Device Properties 20
Full Release 9
iSCS User's Guide
Dual LAN Implementation
Dual LANs All GE Energy Services iSCS devices may be fitted with more than one Ethernet
communication channel.
In this case, each channel will have to be assigned a unique IP address, each one on a
separate LAN.
The use of the dual channel option requires that each channel be connected to a
different Subnet. The subnets may be interconnected, but if they are, they must be
isolated from each other by an IP Gateway.
The following diagram shows how the networks could be connected.
iSCS Host iSCS Host iSCS Host
LAN A
LAN Address 209.197.139.000
Gateway
LAN B
LAN Address 209.197.138.000
Figure 10-1 Example of Dual-LAN
Channel Names Using Config Pro, the programmer gives each iSCS device a unique name when it is
created. <Device_name> can be used as an example.
In order for an iSCS Master Station, or any other host to communicate with another
iSCS host over dual Ethernet connections, there must be a way to differentiate one
channel on a device from another.
To do this, Config Pro will automatically assign to each interface the channel names:
<Device_name>-A
and
<Device_name>-B.
10 Full Release
iSCS User's Guide
Dual LAN Implementation, Continued
MAC / IP Each device in a dual-LAN system will have two channel designators, each having
Addressing of Ethernet and IP addresses.
Channels
Below is an example:
Channel Identifier Ethernet (MAC) Address IP Address

<Device_name>-A 00 00 EF F9 E2 A4 207.197.138.10
<Device_name>-B 00 00 EF F9 E2 A5 207.197.139.10
When Two When two iSCS devices want to talk to each other, they do not address each other by
Devices Want to their <Device_name>, Ethernet address or IP address.
Talk
They use the Channel Identifier to identify the Name, MAC and IP address of the
specific interface they wish to use.
Dual LANs and The Dual LAN system does not imply that the two LANs are automatically
Redundancy redundant.
Redundancy is determined by the application that uses the dual Ethernet links.
Some examples:
One application will use the alternate interface as a fail-over link to use in the
event that the first link fails. This may be considered redundancy.
Another application will choose the first available link when starting its
communication. It may not be able to switch over to the other link except when
the application is stopped and restarted.
A third option may allow a user to select which link they wish to use when
manually establishing a connection.
None of these examples can use a load-sharing algorithm.
Full Release 11
iSCS User's Guide
Exercise 1: Defining Single / Dual iSCS LAN Project

Properties
Configuring iSCS LAN Project Properties
Background The ideal implementation of a dual-LAN system would be based on two entirely
independent network paths.
A system that shares media or interfaces would inherently build in a single-point-of-
failure, reducing overall reliability.
Figure 10-1 Example of Dual-LAN, shows how a dual LAN system could be
physically connected.
Prerequisites The procedures that follow assume that:

the Project and network Devices have been created, configured for non-LAN
communication, and tested.
all iSCS network devices have:
LAN interfaces installed
LAN media installed and connected
been assigned IP addresses for each LAN and interfaces.
Note ( The Labs that follow will show how to setup either a single or dual LAN system.
The differences in configuring a single LAN system will be noted in the procedures.
Procedure The following steps illustrate how to use Config Pro to configure an iSCS Project for
dual-LAN
Step Action
1 Open the Project Properties for the iSCS project.
2 Click the LAN tab
Results: A dialog box like the one below will appear.
12 Full Release
iSCS User's Guide
Configuring iSCS LAN Project Properties, Continued
Procedure (continued)
Step Action
3 Select the LAN Based Project checkbox.
Note: The default value of 1 Segment should only be changed if

network devices are installed on separate LAN segments that
are isolated by an IP Gateway or Router.
Single LAN Project Properties
4 Click the Segments tab
Results: The following dialog box will open.
5 Select the LAN A Enabled check box
Full Release 13
iSCS User's Guide
Step Action
6 Type the:
LAN A Address
Subnet Mask, and
Default Gateway (if used)
for this LAN segment
7 If the network has more that one segment, as noted in Step 3 above, there
will be multiple Segment tabs at the lower-left of the dialog box.
Repeat Step 6 for each segment.
Results: For a single LAN system, the Project Properties
configuration is complete.
Second LAN Project Properties
8 Click the LAN B tab at the top of the dialog box.
9 Repeat Steps 5 to 7 using the parameters specific to the second LAN.
Click OK when completed.
Results: The Config Pro desktop will display the single or dual LAN by
showing vertical lines down the left side, as shown in the
example below.
LAN
Symbols
14 Full Release
iSCS User's Guide
Generic hosts In Config Pro, you can add non-GE Energy Services hosts, such as printers,
and multi-node PowerLink and terminal devices to your iSCS LAN project. You add these under the
D200 hosts Generic tab in the main Project window. Each of these non-GE Energy Services
hosts has an IP address assigned under the device properties.
A D200 remote device with the BusNet Driver application installed is capable of
multi-node communication, where each communicating node acts as a LAN host.
For any Generic device and for each D200 non-lead communicating node, the B100
Host table must also be configured for its Host Name and Host Address.
Procedure Follow these steps to configure the B100HOST table for generic devices assigned
host IP addresses on your LAN project.
Step Action
1 On the Project menu select Project Properties.
Result: The Select Project to Edit dialog box appears.
2 Select the iSCS Project on which you want to configure the B100 Host
table.
Result: The Project Properties dialog box appears.
3 Click the LAN tab.
4 Click the Hosts tab.
Results: A dialog box like the one below appears.
The list on this tab shows the hosts entered in the B100 Host table.
Full Release 15
iSCS User's Guide
Step Action
4 To add a new host, click the + Add button.
5 Enter the Host Name and Host Address. Click OK.

Results: The dialog dismisses and the new host is added to the B100
Host Table. The new host appears in the Hosts tab list.
6 To edit an existing host, click the Change button.

Results: The Enter Host Information dialog box appears.
7 Edit the Host Name and Host Address. Click OK.
Results: The dialog dismisses and the changes are saved to the B100
Host Table.
8 To delete a host from the B100 Host table, select the host you want to
delete from in the Hosts tab list. Click the Delete button.
Results: A confirmation pop-up appears.
9 Click Yes to continue the delete action.
Results: The selected Host is deleted from the B100 Host Table.
16 Full Release
iSCS User's Guide
D200 Multi-node Each of the network cards in a multi-node system is assigned one IP address per
configuration node. The LAN A and LAN B addresses are assigned in the normal way: go to
Device Properties | LAN Settings | LAN Specific and enter the LAN addresses in
the Host Address field in the normal way.
When you configure the B100 Host table for Node Host Names and Addresses,
follow these rules:
build Node Host Names using: <D200 Name><Node Number>-<LAN ID>.
For example, D200SYS2-A is the host name for node 2 on Device D200SYS on
LAN A.
the first two IP addresses are assigned to Node 1 and are the address for the two
LAN network cards. The rule for each further node is simply the addition of the
node number to the respective LAN network interface card IP address. For
example, if LAN A network card is assigned 192.168.1.10 and is assigned to
node 1, then the node 2 LAN A IP address is 192.168.1.12, the node 3 address
becomes 192.168.1.13 and so on.
Note ( When assigning the Host IP Address for multiple nodes, three things should be
noted:
If any particular node is not configured as a communicating node, then the
addition rule still applies. If node 3 was not assigned an IP address, then node 4
IP addresses are 192.168.1.14 and 192.168.2.14 for LANs A and B respectively.
You must NOT assign the first increment address after the LAN A address or the
first increment address after the LAN B address: 192.168.1.11 and 192.168.2.11
in this example, since these are reserved for the system assigned IP Host address
for the BusNet driver.
You must be careful NOT to exceed the largest permissible address for the
network. In the example, if the LAN B network interface card was configured
with IP Address 192.168.2.253, then node two LAN B host addresses would be
192.168.2.255 using the addition rule and this would exceed the maximum of
192.168.2.254 for the network.
Full Release 17
iSCS User's Guide
Procedure Follow these steps to configure the B100HOST table for a D200 multi-node
communication device on your LAN project.
Step Action
1 On the Project menu select Project Properties.
Result: The Select Project to Edit dialog box appears.
2 Select the iSCS Project on which you want to configure the B100 Host
table.
Result: The Project Properties dialog box appears.
4 Click the Hosts tab.
Results: A dialog box like the one below will appear.
The list on this tab shows the hosts entered in the B100 Host table.
18 Full Release
iSCS User's Guide
Step Action
5 To add a new D200 non-lead communication node host name and
address, click the + Add button.
6 Enter the Host Name and Host Address. Follow the rules for Node Host
Naming and Addressing as given above: D200 Multi-node configuration
Click OK.
Results: The dialog dismisses and the new communicating node host
names and addresses are added to the B100 Host Table. The
new host appears in the Hosts tab list.
7 To edit existing communicating node host names and address, click the
Change button.
Results: The Enter Host Information dialog box appears.
8 Edit the Host Name and Host Address. Follow the rules for Node Host
Naming and Addressing as given above: D200 Multi-node configuration.
Click OK.
Results: The dialog dismisses and the changes are saved to the B100
Host Table.
9 To delete a communicating node host from the B100 Host table, select
the host you want to delete from in the Hosts tab list. Click the Delete
button.
Results: A confirmation pop-up appears.
10 Click Yes to continue the delete action.
Results: The selected communicating node host is deleted from the
B100 Host Table.
Full Release 19
iSCS User's Guide
Exercise 2: Defining Single / Dual LAN Device

Properties
Configuring iSCS LAN Device Properties
Prerequisites Before an iSCS device can be configured for LAN communication, the Project
Properties must be previously defined.
Exercise 1: Defining Single / Dual iSCS LAN Project Properties shows the steps to
define these properties.
Background Each LAN-attached device in an iSCS system must have its properties configured
identifying it as a member of one or both IP networks.
It is very possible that some devices in an iSCS system will Not be attached to the
LAN at all.
Some of these devices may be serially connected to LAN devices.
These devices do not need to be configured for iSCS communications.
Some serially attached devices may be virtually connected to the LAN be using
PPP.
PPP configuration will be discussed in a separate section of this document.
Procedure This procedure outlines steps, using Config Pro, to define the Device Properties of a
LAN-attached iSCS device.
Step Action
1 Open the iSCS project, and click (once) the LAN-attached device icon.
2 Click the Device Properties button on the Tool Bar, or
Right-click the icon, and select Properties
Device Properties LAN Settings - General
3 Select the LAN Based Device check box
Results: A new tab, LAN Settings, will appear at the top of the dialog
box.
4 Click the LAN Settings tab

Results: The following dialog box will appear.
20 Full Release
iSCS User's Guide
Configuring iSCS LAN Device Properties, Continued
Step Action
5 Click the Not Used option for the BootP Settings.
BootP configuration will be demonstrated in a later section of this
document.
6 Select the Connected to LAN A check box, if not already checked.

If the project has two LANs, select the Connected to LAN B option if
appropriate. It will be grayed-out as shown above if the project is a
single LAN system.
7 If LAN is multi-segment, select the segment that this device is connected
to.
Device Properties LAN Settings LAN Specific
8 Click the LAN Specific tab
Results: A dialog similar to the one shown below will appear
Full Release 21
iSCS User's Guide
Step Action
9 Type the Host Address of this device into the appropriate fields.
Note 1: The LAN Address and Subnet Mask as defined for the
project are shown grayed-out. The Subnet ID part of the Host
Address must be the same as the LAN Address shown.
Note 2: The Ethernet Address can be left all-zeros as shown. It is not
necessary to fill in this field unless the device is a BootP
Client.
Device Properties LAN Settings Services
10 Click the Services tab
Note: The steps that follow will prepare the device configuration for
DNP 3.0, RFC 1006 or IEC 104 communication over LAN.
If DCA or DPA IP communication is not required, these steps

can be omitted.
22 Full Release
iSCS User's Guide
Step Action
11 If the version of iSCS LAN Stack (P112) software running in your
device is less than Version 130, type and/or select the values as shown in
the example graphic below for the protocols used in your particular
device.
If the version of iSCS LAN Stack software in this device is Ver. 130, or
higher, and you wish to use the default port numbers, the Services fields
can be deleted completely.
Why? If left blank, the newer iSCS software will automatically insert
default values, and/or values derived from the DPA or DCA
applications.
Notes ( The Port Numbers shown in Step 11 are the official port numbers assigned to
the DNP 3.0, UCAs RFC 1006 and IEC 104 protocols respectively by the IETF.
If you are using DNP or IEC 104, other numbers may work, but all iSCS devices
that communicate with each other must have the same port numbers assigned to
their respective protocol services.
RFC 1006 must use port number 102.
DNP services can use either UDP or TCP link protocols, default port numbers
are the same as shown for either protocol.
UCA RFC 1006 and IEC 104 protocols do not support UDP and must use TCP.
Full Release 23
iSCS User's Guide
Step Action
Repeat Procedure and Generate
12 Repeat Steps 1 through 11 for all devices in the iSCS project, as
required.
13 Click the Generate iSCS LAN Configuration icon on the Tool Bar.
Note: Do not perform this step until all device configurations are
completed. Any changes to device or project properties will
require repeating this step.
Results: Depending on the number of devices, complexity of
configuration and PC power, this may take several minutes.
What Was Review: All devices on any LAN must know each others:
Accomplished
Ethernet hardware, or MAC address, and
IP address
before they can communicate with each other.
In an iSCS system, they must also know the:
Channel identifier or name.
The last step in the previous procedure, clicking the Generate iSCS LAN
Configuration icon, updated all of the iSCS network devices Host Tables.
What is a Host A Host Table is a cross-reference table used by each network device allowing it to
Table? communicate with another device simply by using that device's Host Name.
The Host Table is used by the devices communication software to convert the
channel identifiers, or names, to IP addresses.
24 Full Release
iSCS User's Guide
View the Host The Host Table for any iSCS device can be viewed by performing the following
Table steps.
Step Action
1 Open the iSCS Project and double-click the device icon for one of the
iSCS devices
2 Click the Data Translation Applications tab
Results: A collection of application icons will be displayed, like the
graphic below.
3 Double-click the etc\Services (Internet Protocol Stack) icon
4 Double-click the Host Configuration table icon.

Results: A table like the one below will be displayed.
5 Double-clicking the IP Address field on any row will show the IP

Address associated with the Host Name on the left.
Note 1: Use this procedure to check that all iSCS devices are listed,
and that their IP addresses are correct.
Note 2: This table is Read-only and cannot be edited.
Procedures If all devices and the iSCS LAN configurations have generated without errors, you
Complete? are now ready to configure the applications that will use the services of the iSCS.
Full Release 25
Chapter 11: TELNET and iSCS
Overview
Introduction iSCS devices support TELNET in these ways:

as a TELNET client, the device can receive TELNET requests from other hosts
on the LAN, and connect them with a WESMAINT task for login.
The host may be an iSCS device or a third party TELNET host.
as a TELNET host, the device can generate TELNET requests to:
other iSCS devices to access their WESMAINT facility, or
third-party devices that are included in its Host Table
Topic See Page

Exercise 3: Enabling TELNET in an iSCS Device 28
Configuring TELNET 28
Exercise 4: Enabling TELNET Client Functionality 29
Configuring WESMAINT as a TELNET Client 29
Exercise 5: Enabling TELNET Host Functionality 31
Configuring WESMAINT as a TELNET Host 31
Using TELNET WESMAINT 33
Exercise 6: Testing WESMAINT TELNET Access 34
Using WESMAINT as a TELNET Client 34
Full Release 27
iSCS User's Guide
Exercise 3: Enabling TELNET in an iSCS Device
Configuring TELNET
Background TELNET functionality in an iSCS device can be broken into two distinct areas:
Client Functions
Host Functions
Both of these functions require that the B051 TELNET Application be enabled.
Prerequisites Before the TELNET application can be employed:

iSCS LAN Project and Device Properties must be defined as in Exercise 1:
Exercise 2:
The B051 application must be present in the devices firmware.
Procedure Use these steps to enable and configure the B051 TELNET application.
Step Action
1 Open the iSCS project and the device that you wish to enable TELNET
functionality
Results: A collection of application icons will be displayed, like the
graphic below.
3 If not already enabled, right-click the TELNET application icon, and

click Enable
Results: When enabled, the red X will not appear next to the icon.
Lab Complete For most simple applications of TELNET, such as WESMAINT, simply enabling the
application will be all that is required.
Performance may be improved for other uses, such as Virtual Terminal, by fine-
tuning some of the parameters accessed by opening the application.
28 Full Release
iSCS User's Guide
Exercise 4: Enabling TELNET Client Functionality
Configuring WESMAINT as a TELNET Client
Background The TELNET Client functionality is provided by allowing a serially connected

WESMAINT user access to an Application menu item.
Once configured, an authorized WESMAINT user will be able to select and log into
any of the iSCS TELNET Host devices on the same LAN as the local device.
TELNET connections can Only be initiated from a serially connected

Note WESMAINT session.
Incoming TELNET (host) connections are blocked from initiating outgoing
TELNET (client) connections.
Limitation All versions of the B051 TELNET Application up to and including Ver. 1.30 will
only support 1 client and 1 host connection at a time.
Future versions are planned that will support multiple connections concurrently.
Procedure Follow this procedure to enable TELNET client functionality to WESMAINT.
Step Action
1 Click System Point Database Applications tab in the target device
configuration
2 Double-click the WESMAINT icon
3 Double-click the User Configuration Table icon
4 Press the TAB key until the Application Control field is highlighted, and
press the SPACEBAR.
Results: A dialog similar to the one below will appear.
Full Release 29
iSCS User's Guide
Configuring WESMAINT as a TELNET Client, Continued
Step Action
5 Type the number 32051 into the first unused field in the Application
Number column. Click OK when ready.
Note: All fields to the right of the number should display Enable.
Finished? The preceding procedure will enable client functionality for a WESMAINT user
logged into the device.
If TELNET host capability is not required, the configuration is now complete and
ready to generate and download.
The following Exercise outlines the enabling of TELNET Host functionality.
30 Full Release
iSCS User's Guide
Exercise 5: Enabling TELNET Host Functionality
Configuring WESMAINT as a TELNET Host
Background Any incoming TELNET client connection requests are directed automatically to the
devices WESMAINT application.
Once connected, the client will be prompted to log into WESMAINT, in exactly the
same way that a local WESMAINT user would be prompted. After logging in, the
user is then free to navigate around the menus, based on user rights.
How it Works To enable the TELNET host functionality of a device, a connection path must be
defined that links the TELNET applications host software with the WESMAINT
application.
In effect, this link will simulate a serial connection from the requesting client directly
to WESMAINT.
Procedure Follow this procedure to enable the devices TELNET Host capability.
Step Action
1 Click System Point Database Applications tab in the target device
configuration
2 Double-click the WESMAINT icon
3 Double-click the Port Configuration Table icon
4 Click once on any field in the lowest row displayed to select the row.
Press the DOWN-ARROW key.
Results: a new duplicate row will appear below the original row
5 Press the TAB or SHIFT-TAB key until the Comm Port field is
highlighted, and press the SPACEBAR.
6 Press the down-arrow key repeatedly until TEL1 is highlighted, and
press the SPACEBAR.
Results: The display should now be similar to the one below.
Full Release 31
iSCS User's Guide
Configuring WESMAINT as a TELNET Host, Continued
Step Action
7 All fields to the right of the Comm Port field will still be the same as
the row above the selected row.
Press the TAB or END key until the Task Name field is highlighted, and
then press the SPACEBAR.
8 Press the down-arrow key until WES2 is highlighted, and press the
SPACEBAR.
Note: It is imperative that Task Names not be assigned to more than
one Port. If WES2 is already in use, be sure to pick a unique
Task Name for the new port.
9 Close all tables, and click the Generate iSCS LAN Configuration icon
in the Tool Bar.
Lab Complete The configuration is now ready to download to the target device.
Note ( It is possible to create multiple TELNET ports in this table, and doing so will not
affect the operation of the device.
At the current release of software, only one TELNET port can be used at a time.
Future releases will allow multiple ports.
32 Full Release
iSCS User's Guide
Using TELNET WESMAINT
Background There are two ways to establish a TELNET link to an iSCS devices WESMAINT
facility:
From a second iSCS device, a local (serial) WESMAINT user can initiate a
TELNET request to the target iSCS device
From a Windows PC, a user can use the Windows TELNET accessory, or a
third-party utility, to generate a TELNET request to the target iSCS device.
Both of these techniques will be discussed in the procedures that follow.
Advantages / The following table may help choose the best solution for your environment.
Disadvantages of
each
Client Application Advantages Disadvantages
Serial WESMAINT Terminal emulation is User must have Config
connection from 2nd already defined and Pro installed on PC
device optimized for
WESMAINT access.
Look-and-feel same as
local WESMAINT
Hot keys work the same
way as local
WESMAINT
Windows or 3rd party May be free Emulation may be not
TELNET client Config Pro Not required configurable
May support features May not support Hot
not included in Config keys, manual login
Pro emulator required
Look-and-feel different
from local WESMAINT
Full Release 33
iSCS User's Guide
Exercise 6: Testing WESMAINT TELNET Access
Using WESMAINT as a TELNET Client
Prerequisites The following procedures will assume that you have completed Exercise 3:
Enabling TELNET in an iSCS Device, Exercise 4: Enabling TELNET Client
Functionality, and Exercise 5: Enabling TELNET Host Functionality , and
downloaded to at least two iSCS devices.
Procedure 1 This procedure shows you how to establish a TELNET session from a local serial
WESMAINT application to a remote LAN-connected WESMAINT application.
Step Action
1 Connect the Config Pro PCs serial communication port to device #1s
front panel WESMAINT interface using a WESMAINT cable
2 Log into the local WESMAINT
3 Press 3, or press DOWN-ARROW to highlight APPLICATION MENUS and
press ENTER
4 Press RIGHT-ARROW to highlight B051 TELNET and press ENTER
Results: a display of all iSCS devices in this devices Host table is
shown. An example is shown below
5 Press DOWN or UP-ARROW to highlight the target devices host name and
press ENTER
Results: display will go blank when connection is established
6 Press ENTER one or more times to bring up Welcome screen from the
remote devices WESMAINT.
7 Log in as you would for a local WESMAINT.
Results: Based on user restrictions, you are now free to use menus as a
local user might.
34 Full Release
iSCS User's Guide
Using WESMAINT as a TELNET Client, Continued
Note ( There are a few restrictions on TELNET WESMAINT users that you may encounter,
due to TELNETs inherent control character passthrough issues.
These are some restrictions you may see (but not limited to):
68K Monitor functions such as SA COMX for serial analyzer will be blocked
because the CONTROL-C will not pass through to stop the function
An incoming TELNET user cannot generate an outgoing TELNET request.
Procedure 2 This procedure shows how to establish a TELNET session from the Windows NT PC
TELNET accessory to a remote LAN-connected WESMAINT application.
Step Action
1 Click Start | Program | Accessories | TELNET on your PC
2 Click Connect | Remote System from the TELNET accessorys menus.
3 Type either the IP address or the Host Name of the target devices
interface into the Host Name field.
If the Port and TermType fields are not as shown below in the example,
change them now.
Note: If the PCs Host file has been updated to show the name and
IP address of your target device, you can substitute that Host
Name for the IP address.
4 Click Connect
Results: The display will go blank when connection is established
5 Press ENTER one or more times to bring up the Welcome screen from the
remote devices WESMAINT application.
6 Type the User Name and Password as you would for a local
WESMAINT.
Results: Based on user restrictions, you are now free to use menus as a
local user might.
Full Release 35
iSCS User's Guide
36 Full Release
Chapter 12: TFTP File Transfer
Overview
Introduction This chapter demonstrates how to configure and use Config Pro to download and
upload configuration and code files over an Ethernet iSCS LAN.
Other types of file transfer, such as GE Energy Services Advanced Monitoring
Applications COMTRADE files, are discussed in user guides for those products.
In this chapter This chapter contains the following topic
Topic See Page

Exercise 7: Config/Code Down/Upload Using TFTP 38
Using TFTP File Transfer 38
Full Release 37
iSCS User's Guide
Exercise 7: Config/Code Down/Upload Using TFTP
Using TFTP File Transfer
Background Possibly one of the most welcome features of the iSCS LAN system is the ease and
speed that the Config Pro PC can transfer a configuration file to or from an iSCS
device.
D25 and D200 devices also have the ability to accept TFTP transfers of their
firmware (flash memory) code files.
The configuration files that are downloaded are the *.ZLB compressed files,
generated by Config Pro when device configurations are generated.
Uploaded configuration files will appear as <devicename>.UPL and will be in
the same binary format as the *.IMG file created by Config Pro.
Configuration Before a TFTP transfer of a configuration or code file can be initiated, Config Pro
File Download must be set up for LAN communication.
The following procedure shows the steps to set up Config Pro for LAN
communication, and file up/download.
Step Action
Config Pro Preferences
1 Click File | Preferences | Communications | LAN
Results: A dialog box similar to the following will appear
2 Type (or select) the IP address of the LAN interface(s) of the Config Pro
PC into the IP Address fields. Click OK.
38 Full Release
iSCS User's Guide
Using TFTP File Transfer, Continued
Configuration File Download (continued)
Step Action
Switch to LAN Communications
3 Right-click the device icon that represents the device you wish to
download to.
4 Click Communications | Communications Options
Results: The following dialog box will appear.
5 Click the iSCS LAN option, if not already selected. Click OK.
Note: Default values for other options and tabs are usually
satisfactory for most applications. Adjust if necessary.
Full Release 39
iSCS User's Guide
Configuration File Download (continued)
Step Action
Downloading the Configuration File
6 Right-click the device icon that represents the device you wish to
download to.
7 Click Communications | Configuration Download
Results: Download will now start. Device will automatically restart

when download is complete.
File Upload The steps of the preceding procedure show how to transfer (download) a
Procedure configuration file to an iSCS device.
The Procedure to upload a configuration file from a device is almost identical.
The Step 7 of the procedure would be altered to click the Configuration Upload
option.
File Format The uploaded configuration file is Not a compressed file like the downloadable file
transferred in Step 7. It is actually a binary file that is read directly from the
NVRAM of the device.
When the transfer is complete, and has no errors, it is saved to the Config Pro device
directory as <devicename>.upl
This file can subsequently be used to recover the operating configuration into Config
Pro. The procedure for recovering configurations can be found in the Config Pro
Tutorial on the Config Pro CD-ROM
40 Full Release
iSCS User's Guide
D25 and D200 The D25 and D200 products can have their Code file downloaded to refresh, add or
Code Download change the applications that reside in their firmware (flash memory).
Procedure
In the case of a D25 device, the procedure to download a code file is almost the same
as the preceding procedure. Only Step 7 is changed to click the Code Download
option. The graphic below shows the dialog to perform this alternate step.
The procedure for the D200 multi-processor device differs.
Procedure Follow these steps to do a Code Download to a D200 multi-processor device.
Step Action
1 Right-click the D200 device icon that represents the device you wish to
download to.
2 Click Communications | Configuration Download.
Results: The Select Target Processor dialog appears.
Use the Processor drop-down list selection field to select the D200
processor to which you want the code to be downloaded. If you want the
code to be generated to all processors, then check All Processors.
Click OK.
Results: The code is downloaded to the selected processor or all
processors.
Full Release 41
iSCS User's Guide
42 Full Release
Chapter 13: Automatic Initialization - BootP
Overview
Introduction The Bootstrap Protocol (BootP) permits a client machine to obtain its Internet
Protocol address and configuration file information from a centralized network
server. This configuration file information may then be used as a pointer to locate
the TFTP server and directory path where a code and/or configuration file can be
automatically accessed and transferred to the client.
This chapter provides the background and configuration procedures to implement a
BootP configuration management system.
Topic See Page

BootP Operation 44
Windows-Based BootP / TFTP Solution 46
Exercise 8: PC Network Settings for BootP / TFTP 47
Configuring Windows NT4 for BootP / TFTP 47
Exercise 9: Installation of the BootP Server Utility 50
Installing the BootP Server 50
Exercise 10: Creating the BootPtab Files 52
Configuring the BootP Server 52
Exercise 11: Installation of the TFTP Server Utility 55
Installing the TFTP Server 55
Exercise 12: Setting-up the TFTP Server Utility 57
Configuring the TFTP Server 57
Config Pro and BootP / TFTP 59
Exercise 13: Config Pro Setup for BootP / TFTP 60
Defining Project/Device Properties for BootP/TFTP 60
Exercise 14: Testing the BootP/TFTP Server 65
BootP/TFTP Server Operation 65
Normal Startup Cycle 70
Full Release 43
iSCS User's Guide
BootP Operation
Client Requests The bootstrap operation for a booting client machine starts with the client
broadcasting a BootP Request message onto the LAN to obtain its IP interface
configuration information, and pointers to code and configuration files
Server Responds A BootP Server responds by providing the booting client with its:
IP address
subnet mask
default gateway IP address
file server IP address
boot file name
client host name, and
server host name
Config Pros Config Pro is responsible for generating several files used during the BootP and
Role in BootP TFTP processes:
File Function
BootPtab Used by the BootP Server as the source of information it
needs to create response to a BootP client request
BOOTFILE.TXT Used by the TFTP Server to inform a client device of the
availability, location, date and names of one or both of:
a binary code file used to program that devices
firmware (flash memory)
a (compressed) configuration file for that device
<Devicename>.zlb The compressed configuration file for a device.
It will be transferred by the TFTP application to the device,
which then de-compresses it into NVRAM
44 Full Release
iSCS User's Guide
BootP Operation, Continued
Important The BootP Server maintains information that informs the client where the
BOOTFILE.TXT file is located on a TFTP Server.
The BootP Server software Does Not maintain configuration or program files itself.
It is only used to provide IP addressing information, as shown above.
BootP / TFTP This flowchart illustrates a normal BootP and TFTP startup cycle.
Flow Chart
.
Device Restart
Device broadcasts a BootP .

. Device reboots
Request onto LAN
BootP Server replies with IP

address information, and Device decompresses/loads
location of BOOTFILE.TXT files into memory
on TFTP Server
Device requests TFTP Device requests TFTP

Server to transfer Server to transfer Code/
BOOTFILE.TXT Config files.
Does
Code/Config match Device boots into Service
No
what is running in Mode
device?
Yes
Device resumes
normal operation
.
Figure 13-1 BootP / TFTP Flowchart
Note: Refer to B054-0FS.DOC, TFTP File Manager Functional Specification,

for a more detailed flowchart.
Full Release 45
iSCS User's Guide
Windows-Based BootP / TFTP Solution
Introduction This BootP Server utility is supplied as an extra option available on the Config Pro 4
CD-ROM
Installation of the utility will be provided in a following section of this manual.
BootP and TFTP A companion utility also provided on the Config Pro CD-ROM is the TFTP Server.
Together, they provide full functionality where:
the BootP Server responds to a client request with IP addressing information and
where to locate the TFTP Server that maintains program and configuration files.
the TFTP Server transfers program and/or configuration files to the requesting
client, when the client determines that it should.
Important! The BootP Server and the TFTP Server utilities Must be installed on the same
Windows NT-based PC.
Dual-LAN To support dual LANs, the Windows-based PC used as the BootP and TFTP server
Support must have two Ethernet interfaces installed, with each addressed to one of the two
LANs.
Once installed, the server applications will automatically recognize the IP addresses
assigned to the two interfaces, and respond to requests accordingly.
A requesting client will generate a BootP request message onto both LANs at the
same time.
The requesting client is responsible for prioritizing the LAN A as the server it will
use first. Only if the LAN A server does not respond will the client then revert to a
response it has received from the LAN B server.
46 Full Release
iSCS User's Guide
Exercise 8: PC Network Settings for BootP / TFTP
Configuring Windows NT4 for BootP / TFTP
Background Before the BootP or TFTP utilities will operate on their host PC, the Windows NT
networking parameters must be defined.
If the PC is currently part of an existing LAN, consult your system administrator to

Note determine if the configuration changes outlined in the following procedure will
conflict with other network software.
Before Starting Information you will need for the following procedure include:
Network Address(es) for LAN(s)
IP addressing for all devices, including the server PC
Network Mask for this (and any other) subnets
Default Gateway address (if used)
Note: Windows NT disk set may be required to install Windows components

that may not be currently installed onto the PC
DHCP The Dynamic Host Control Protocol, or DHCP, is essentially an enhancement to

BootP.
If DHCP is enabled on a PC, it becomes by definition a BootP client.
A network connection set up as a BootP client cannot also be a BootP Server
If the PC is currently using a network card running DHCP to obtain its network
settings, you do not have to disable this feature but BootP will not be able use this
card.
Provided there is at least one network card on the PC that is configured as static, then
BootP will run.
Prerequisites The PC Must have an Ethernet network interface card installed and its drivers
configured before starting this procedure.
The BootP and TFTP utilities Must be installed on either:
the same PC that Config Pro is installed, or
a PC or LAN server that shares network drives with the Config Pro PC
Full Release 47
iSCS User's Guide
Configuring Windows NT4 for BootP / TFTP, Continued
Procedure Follow this procedure to configure the Windows NT PC for BootP / TFTP.
Step Action
1 Click Start | Settings | Control Panel on the host PC monitor
2 Double-click the Network icon
3 Click the Protocols tab
Results: the following dialog box will appear.
4 Click the TCP/IP Protocol item to select it.
Note: If this item is not displayed, consult the Windows NT

documentation to install the protocol.
5 Click the Properties button

Results: The following dialog box will be displayed.
48 Full Release
iSCS User's Guide
Configuring Windows NT4 for BootP / TFTP, Continued
Step Action
6 If not already selected, click the Specify an IP address option.
7 Type into the fields:

IP address of PC interface(s)
Subnet mask used on this LAN segment
Default gateway for this LAN (if used)
8 Click OK when finished.
Note: Setting DNS, WINS and Routing parameters are not required
for the operation of the BootP Server utility.
It may be necessary to configure these parameters for other
network applications running on the PC. Consult your network
administrator for assistance.
9 Restart the PC, as prompted, to put changes into effect.
Full Release 49
iSCS User's Guide
Exercise 9: Installation of the BootP Server Utility
Installing the BootP Server
Background The BootP Server utility is installed from the Config Pro 4 installation dialog box.
Procedure Follow these steps to install the BootP Server utility onto a Windows NT PC
Step Action
1 Insert Config Pro 4 CD-ROM into PCs drive.

Wait for a few seconds for the installation window shown below to
pop up.
If it does not automatically start, use the Start menu or Explorer to
run HSETUP.EXE from the CD.
Results: The dialog box below should appear:

2 Click the Optional Extras button.
Results: A dialog box showing the two Server utility installation icons
appears.
50 Full Release
iSCS User's Guide
Installing the BootP Server, Continued
Step Action
3 Click the BootP Server icon.
4 If a message prompts you to shut down any conflicting applications, do

so at this time.
Note: You may have to Access the Settings | Control Panel |
Services to stop conflicting services from running.
5 Click Next when prompted for the next 2 dialog boxes

6 Click Finish to compete the installation.
7 Click OK when prompted to restart the computer.
You may have noticed that the installation does not provide any options for drive or
Note path selection.
Both the BootP Server and the TFTP Server utilities are installed to the Windows NT
directories, and are accessed via the Control Panel.
Full Release 51
iSCS User's Guide
Exercise 10: Creating the BootPtab Files
Configuring the BootP Server
Background The BootPtab file is an automatically updated file that maintains the BootP
information for all BootP clients in a project that is serviced by the BootP Server
utility.
An example of a BootPtab file for a 3-device system is shown below.
Figure 13-2 Example BootPtab File
The filename of the BootP information file can be changed as desired. BootPtab is
Note used here as an example.
File Location The directory and path where the BootPtab file is located is not important, as long as
it is accessible to both the BootP Server and Config Pro applications.
The path shown in this procedure is only a suggestion.
52 Full Release
iSCS User's Guide
Configuring the BootP Server, Continued
Procedure Follow this procedure to:

Become familiar with the operation of the BootP Server utility
Create the BootPtab and BootPlog files
Step Action
1 Click Start | Settings | Control Panel from the Windows NT desktop

2 Double-click the BootP Server icon.
3 Click the Configuration tab.
4 Type (or browse to) a drive \ path \ filename for both the:
Configuration file
Log file. (if used)
Note: The paths show in the above example are only suggestions.
Modify as necessary for your system.
5 Select the Keep Log File option, if desired. (recommended)

Note: If the Keep Log File check box is selected, the Server will use
this file to record the results of all BootP requests issued by
devices for which there are entries present in the Configuration
File.
Click the Help button for more details.
Full Release 53
iSCS User's Guide
Configuring the BootP Server, Continued
Step Action
6 Click the Apply button at the lower right of the dialog box.
Results: The two text files will be created at the location designated by
the path in the two File fields.
You can verify that the files have been correctly created using
Windows Explorer. The files will be empty at this time.
7 Click the Status tab

Results: the dialog box below will be displayed
8 If the BootP utility has been installed successfully, the IP address(es) of
the server PCs interface(s) will be displayed in the Adapters Accepting
Requests box on the left.
Note: If the PC has a network card installed running DHCP, then this
will show in the Adapters Not Accepting Requests box.
9 If you do not see a display similar to the one above, click Start | Control
Panel | Services to see if the BootP service is running.
Start the service if required.
54 Full Release
iSCS User's Guide
Exercise 11: Installation of the TFTP Server Utility
Installing the TFTP Server
Background The TFTP Server utility is installed from the Config Pro 4 installation dialog box.
Procedure Follow these steps to install the TFTP Server utility onto a Windows NT PC
Step Action
1 Insert Config Pro 4 CD-ROM into PCs drive.
Wait for a few seconds for the installation window shown below to
pop up.
If it does not automatically start, use the Start menu or Explorer to
run HSETUP.EXE from the CD.
Results: The Dialog Box below should appear:

2 Click the Optional Extras tab.
Results: A dialog box showing the two Server utility installation icons
appears.
Full Release 55
iSCS User's Guide
Installing the TFTP Server, Continued
Step Action
3 Click the TFTP Server icon.
4 If a message prompts you to shut down any conflicting applications, do

so at this time.
Note: You may have to Access the Settings | Control Panel |
Services to stop conflicting services from running.
5 Click Next when prompted for the next 2 dialog boxes

6 Click Finish to compete the installation.
7 Click OK if prompted to restart the computer.
56 Full Release
iSCS User's Guide
Exercise 12: Setting-up the TFTP Server Utility
Configuring the TFTP Server
Procedure Follow this procedure to:

Become familiar with the operation of the TFTP Server utility
Define the parameters necessary for proper operation of the utility
Step Action
1 Click Start | Settings | Control Panel from the Windows NT desktop

2 Double-click the TFTP Server icon.
3 Click the Configuration tab.
4 Type a path into the:
Inbound File Directory
Outbound File Directory
Note: The recommended path should identify the location of the root
Config Pro project directory where the device configuration
files are located.
Full Release 57
iSCS User's Guide
Configuring the TFTP Server, Continued
Step Action
5 Select the Keep History check box if you want to keep a log of TFTP
transfers.
The log can be viewed or cleared at any time by clicking the buttons
seen after clicking the History tab
6 Click Apply when ready.
7 Click the Status tab
Results: the dialog box below will be displayed
8 If the TFTP utility has been installed successfully, the IP address(es) of
the server PCs interface(s) will be displayed in the Adapters Accepting
Requests box on the left.
9 If you do not see a display similar to the one above, click Start | Control
Panel | Services to see if the BootP service is running.
Start the service if required.
58 Full Release
iSCS User's Guide
Config Pro and BootP / TFTP
Background As mentioned before in this section, it is Config Pros responsibility to create the
files used by the BootP and TFTP Servers.
It is also necessary for Config Pro to update and date/time stamp these files any time
a configuration or code change is performed.
The BootPtab The BootPtab file used by the BootP Server is one of the files that must be updated
Files by Config Pro.
Because Config Pro can maintain configuration information for many projects, it is
necessary that each project to have a unique BootPtab file.
Multiple BootPtab files can:
have unique file names (i.e., BootPtab1, BootPtab2, etc.) and stored in the same
location, or
have the same names, but be stored in unique locations
The Other Files The other two files are also generated by Config Pro are used by the TFTP Server.
They are:
BOOTFILE.TXT, and
<Devicename>.ZLB
and are stored in Config Pro device directories.
The TFTP Server can locate these two files by:
following the main Config Pro project directory path as defined in Exercise 12:
Setting-up the TFTP Server Utility, then
following path and sub-directory information in the BootPtab file.
Full Release 59
iSCS User's Guide
Exercise 13: Config Pro Setup for BootP / TFTP
Defining Project/Device Properties for BootP/TFTP
Prerequisites If you wish to perform the following procedure, you Must be an experienced Config
Pro user.
Recommendation iSCS devices should be Fully configured and operational before adding the BootP /
TFTP system.
This procedure assumes that the LAN communication parameters are already in
place in the Config Pro tables.
Information You At the Project level

Will Need
The location (path) where the BootPtab file for this iSCS project is located
The IP address(es) of the BootP Server PCs interfaces
All BootP Client device configurations will have to be programmed with their:
MAC (Ethernet hardware) addresses
Procedure Use Config Pro to perform the following procedure.
Step Action
Setting the Project Properties
1 Click the Project Properties button for this iSCS project
3 Click the BootP Server tab.
Results: The following dialog box will be displayed
4 Select the Automatically Update check box
60 Full Release
iSCS User's Guide
Defining Project/Device Properties for BootP/TFTP, Continued
Step Action
5 Type (or browse) the path and file name of the BootPtab file for this
project.
Note: the file and path shown in this graphic are only examples. Use
the same path and file name you used in Exercise 10: Creating
the BootPtab Files
6 Repeat the above step for the other segment if dual LANs are in use in
this project.
7 Click the Server Addresses tab
8 Type the IP address(es) of the BootP Server PCs interface(s) into the
Address fields, and click OK when ready.
Note: The values shown in this graphic are only examples. Enter the
addresses used in your system, only.
Setting the Device Properties
9 Right-click one of the iSCS device icons.
10 Click Properties from the drop-down list.
Results: A dialog box will open with the General tab selected.
Note: The LAN Based Device check box should already be selected.
Full Release 61
iSCS User's Guide
Step Action
11 Click the LAN Settings tab
Results: The following dialog box will appear
12 Select the Client checkbox on the left.
Results: If Client was not already selected, the BootP Window field
will appear with a default value of 180 seconds.
This value is the maximum time that the client will wait for a
BootP response from any primary or secondary server. This
default should work for most systems.
13 Click the LAN Specific tab

Results: A dialog box similar to the one below will appear.
62 Full Release
iSCS User's Guide
Step Action
14 Type the Ethernet Address (MAC address) of this devices interface,
and click OK when complete.
Notes: The MAC address is not required for standard SCADA

communication over a LAN. It is Only required for BootP
applications.
The Host Address should already be visible, as it is required

for SCADA communication
15 Repeat steps 9 through 14 for the LAN B interface, if used.

16 Repeat steps 9 through 15 for all BootP Client devices in this project.
Full Release 63
iSCS User's Guide
Step Action
Generate the iSCS LAN
17 Click the Generate iSCS LAN Configuration button, as shown by the
arrow below.
Results: After a short wait (depending on number of devices and

configuration complexity) this pop-up box will inform you that
the BootP Server has been updated.
The Output Window at the botton of the screen will show

useful debugging information if errors are encountered.
64 Full Release
iSCS User's Guide
Exercise 14: Testing the BootP/TFTP Server
BootP/TFTP Server Operation
Background In an iSCS system using the BootP and TFTP system, there are 3 possible results of a
client device restarting and generating a BootP Request:
# What Happens Result
1 A BootP Server is unavailable or The client device will wait for its
inaccessible for some reason configured delay (typically 180
seconds.) for any BootP Servers to
respond.
After this time, the device will fall
back to its stored files, if it has
any.
If the device has no stored files, it
will continue to regenerate BootP
Requests after a random delay,
max 127 seconds.
2 A BootP Server responds The device will start normally
normally. using its stored code and
The device requests the configuration files.
BOOTFILE.TXT from the
TFTP Server
The BOOTFILE.TXT that the
TFTP Server returns shows that
the server files match the files
currently stored in the devices
memory
3 A BootP Server responds The device requests the TFTP
normally. Server transfer only the required
The device requests the files.
BOOTFILE.TXT from the
TFTP Server
The BOOTFILE.TXT that the
TFTP Server shows that the
server files do not match the
files currently stored in the
devices memory
Full Release 65
iSCS User's Guide
BootP/TFTP Server Operation, Continued
How to Tell Normally the BootP / TFTP process is a fully automatic process that will occur any
What is time an iSCS device is restarted.
Happening
In many cases, this process will occur unobserved at an unmanned site.
Outwardly, it is also difficult to determine the success or failure of the process,
because the device only shows a limited number of external indications.
Available Tools The programmer has 2 main options to monitor the process of BootP and TFTP:
WESMAINT
Third-party LAN diagnostic tools or software
Note: Third-party tools will not be discussed in this document.
Using The following procedure outlines steps that can be used to monitor the BootP / TFTP
WESMAINT sequence, as it progresses.
Familiarity with using WESMAINT should be considered a prerequisite.
Note: Serial (front-panel) WESMAINT must be used for this procedure, as

dialup or LAN connected WESMAINT session will be disconnected part
way through the procedure.
Step Action
Refresh Configuration Boot Files
1 Click the Generate iSCS LAN Configuration icon for the Config Pro
project.
Results: this will update the BOOTFILE.TXT and the
<Devicename>.ZLB files so that they will have more current
time/date information than the device has in memory.
2 Connect the serial WESMAINT cable from the Server PC to the device
front-panel WESMAINT connector.
3 Click the Terminal Emulator icon in Config Pros tool bar, and press
ENTER.
Results: The WESMAINT Welcome screen should appear. There is no
need to log in.
66 Full Release
iSCS User's Guide
Using WESMAINT (continued)
Step Action
First Start Cycle
4 Restart the device by either:
Power off and on cycle, or
Log into WESMAINT, access the 68K monitor and type boot
Results: The terminal window will show the diagnostic tests and
startup scripts being run.
5 Wait for all screen activity, then press ENTER

Results: The WESMAINT Welcome screen and login prompt should
appear.
6 Press F2 to login
7 Navigate to the Error Log and press ENTER
Results: A display similar to the on shown below will appear
8 Lines 1 to 3 of the display below indicate the linking of the IP

information with the first Ethernet interface (en0).
The lines 4 and 5 show the start and completion of the TFTP transfer of
the BOOTFILE.TXT
Results: The contents of the BOOTFILE.TXT will not match the file
dates etc. that are in the devices memory. This will signal the
device to restart into service mode.
Full Release 67
iSCS User's Guide
Step Action
Second Start Cycle
9 After device has completed restarting into service mode, press ENTER
Results: The login prompt should appear.(Not WESMAINT)
10 Press F2 to login.
Results: After a few seconds, you may be prompted to view the file
transfers in progress by entering TFTP
11 Type TFTP when screen activity stops.
Results: At the top of this display the TFTP file transfer progress will
be displayed.
First the BOOTFILE.TXT transfer will be shown, then, after a

few seconds wait, the <devicename>.ZLB file will transfer.
After the <devicename>.ZLB file is decompressed into

NVRAM the device will again restart.
Final Start Cycle
12 Wait for all screen activity to stop, then press ENTER
Results: The WESMAINT Welcome screen and login prompt should
appear.
13 Press F2 to login
68 Full Release
iSCS User's Guide
Step Action
14 Navigate to the Error Log and press ENTER
Results: A display similar to the one shown in Step 8 will appear
15 Again, the Error Log will show the TFTP transfer of the
BOOTFILE.TXT
Results: The contents of the BOOTFILE.TXT will now match the file
dates etc. that are in the devices memory. This will signal the
device to start into normal operation.
Full Release 69
iSCS User's Guide
Normal Startup Cycle
Background In a typical system, a device will not require the download of a new configuration or
code file except in rare occasions where network changes or additions are being
performed.
A Normal Cycle As shown in the previous Exercise 14: Testing the BootP/TFTP Server,
WESMAINT is a useful tool that can be used to monitor the progress of a BootP /
TFTP startup cycle.
The final start cycle described in Steps 12 through 15 of Lab 8: show what is seen
during a normal cycle.
Review: Because the contents of the BOOTFILE.TXT now match the file dates etc.
that are in the devices memory, the device will start into normal operation.
70 Full Release
Chapter 14: Serial IP Connection - PPP
Overview
Introduction The PPP Application, B057, is designed to provide a virtual IP link between two
serially connected devices.
One of these devices is an iSCS D20, D25 or D200
The other device is a Windows-based PC, often the same PC that has Config Pro
installed.
This chapter will help the user understand the role of PPP in an iSCS network, and
assist in the configuration of both the device and the PC.
Topic See Page

PPP Operation 72
Uses of PPP 73
Exercise 15: Configuring a PC for PPP 74
Configuring Windows NT4 for PPP 74
Exercise 16: Configuring the Device for PPP 79
Configuring the PPP Application 79
Exercise 17: Testing the PPP Configuration 83
Establishing a PPP Connection 83
Exercise 18: PPP Config Pro - WESMAINT Link 86
Using PPP to Access WESMAINT from Config Pro 86
Full Release 71
iSCS User's Guide
PPP Operation
Background The Point-to-Point Protocol, PPP, is an Internet standard method of transporting IP

(and other protocol) datagrams over point-to-point serial links.
PPP provides a negotiation mechanism enabling the devices to determine optimum
link configuration through an automatic peer-to-peer interaction when link is set up.
The PPP The B057 application is responsible for establishing and maintaining a point-to-point
Applications dial-up serial link between a PC-based PPP client and a D20, D25 or D200 device.
Role
The Windows The Dial-Up Networking facility of Windows 95, 98 or NT provides the client
PCs Role functionality of the PPP subsystem.
While other PPP client software may be used successfully, this document will focus
on Windows NT as an example.
The PPP application (B057) provides answer-only functionality. It does not have
Note dial-out capability.
Implication: PPP cannot be used to link two iSCS IEDs.
PPP The GE Energy Services PPP (B057) application supports these features:
Implementation
IP protocol support only.
Answer-only operation
Dial-up only. i.e., direct serial connection from PC to device is not supported
due to Windows NT PPP implementation issues.
Communication speed is fixed at the rate defined in the B057_CFG table. i.e.,
autospeed (or autobaud) not supported
Supports user-defined username and password connection security
72 Full Release
iSCS User's Guide
Uses of PPP
PPP Applications The serial IP link that is created between a Windows PC and the iSCS device can be
used for many purposes. Some examples:
Config Pro terminal emulator access to a devices WESMAINT utility.
3rd-party (or Windows) TELNET client connection to WESMAINT
Configuration and/or code file up/download
Virtual Connection
DNP 3.0 connection from PowerLink to an iSCS device
Power Quality file transfer
Concurrent Possibly the greatest advantage that PPP can provide is that any of the above
Operation examples can be used at the same time, over the same physical link.
This means that a single communication path can support several types of data
transfers allowing for cost savings.
Performance Due to the limited bandwidth of dial-up modems, and the increased latency of this
Considerations type of communication, response and throughput will be much less than a LAN-
based IP connection.
Users must be aware of the effects that combining different data transfers over one
PPP link will have.
For example:
SCADA traffic response may be significantly slowed, or stopped, if a Power Quality
COMTRADE file was transferred over the same link.
Adjusting software timers in the respective applications can minimize some of these
effects.
Example of PPP The labs that follow will demonstrate the configuration of the various components
in Use that make up the PPP subsystem.
Config Pro will be used to test the communication from the PC through the PPP link,
to the WESMAINT utility on the target device.
Full Release 73
iSCS User's Guide
Exercise 15: Configuring a PC for PPP
Configuring Windows NT4 for PPP
Background Implementing PPP requires the configuration of several separate components:

Dial-up modems must be configured appropriately for the desired speed and
dial/answer characteristics.
This document will not provide a procedure to configure modems.
The client PC must have its Dial-up Networking and modem parameters
installed and configured, and
The target device must have the B057 PPP application enabled and configured.
Prerequisites Dial-up Networking must be installed on the client PC.

The B057 PPP application must be included in the devices firmware.
Procedure 1, the Follow this procedure to configure PPP on a Windows NT4 PC.
PC Set up :
Step Action
Install / Configure Dial-up Modem
1 Click Start | Control Panel | Modems to install and/or define the

properties of the modem to be used on the client PC.
Need help?
Refer to Windows Help or Manuals, and modem
documentation to assist in this step.
Note: The B057 application does not support autospeed or autobaud,
therefore modems must be configured for fixed-speed
operation
Configure Dial-up Networking
2 Click Programs | Accessories | Dial-up Networking
Results: A dialog box like the one below will appear
74 Full Release
iSCS User's Guide
Configuring Windows NT4 for PPP, Continued
Procedure 1, the PC Set up : (continued)
Step Action
3 If this is the first time the dialog has been opened, click the New button.
If Dial-up Networking has been set up before, click the More button and
then click Edit entry and modem properties
Results: A dialog similar to the one below will appear.
4 If required, type a name into the Entry Name field
5 Type the phone number of the remote dial-up modem into the Phone
number field
6 Select the correct modem (if more than one is installed) in the Dial
Using field.
Full Release 75
iSCS User's Guide
Step Action
7 Click to de-select the Use another port if busy option
8 Click the Configure button
Results: The following dialog will appear
9 Select the Initial Speed to match the speed that will be used for the
connection.
Click other options as appropriate for your modem, and click OK.
10 Click the Server tab at the top of the dialog box

76 Full Release
iSCS User's Guide
Step Action
TCP/IP Server Configuration
11 Select the PPP, Windows NT . server type, if not already selected.
12 Click the Network Protocols options so that Only TCP/IP is selected.
13 Verify that Enable Software Compression is not selected
14 Click Enable PPP LCP extensions if not yet selected.
15 Click the TCP/IP Settings button.
TCP/IP Parameter Configuration
16 Click Specify an IP address and then type a valid address into the IP
address field.
Note: The address shown in the above example works in a test

configuration, but may not be suitable for your application.
Full Release 77
iSCS User's Guide
Step Action
17 Click to select the Server assigned name server address option
18 Do Not select the Use IP header compression.
Why? Header compression is not supported by the devices B057
application.
19 Click to select the Use default gateway on remote network option, and
click OK
Other Settings
20 Click the Script tab.
21 Click None for all options
22 Click the Security tab
23 Click to select the Accept any authentication.. option, and click OK
24 Click the More button again.
25 Verify that the Operator assisted or manual dialing option does not
have a check mark beside it. Click to de-select if required
Note: De-selecting this option causes the dial-up networking
software to automatically dial the number entered in Step 5.
If manual dialing is required, leave this option selected.
Procedure 1 The set up of the PC should now be complete.

Complete
The next procedure will outline steps to configure the device's PPP (B057)
application.
78 Full Release
iSCS User's Guide
Exercise 16: Configuring the Device for PPP
Configuring the PPP Application
Procedure 2, The following procedure shows the steps to use Config Pro to configure the B057
Configuring PPP application.
B057
Step Action
1 Open the target Project | Device using Config Pro

Results: The desktop will show a collection of icons, including the PPP
Driver icon, as shown below.
3 If the PPP Driver application is not enabled (as indicated by a red X at

the lower-left corner of the icon) right click the icon and click Enable
4 Double-click the PPP Driver icon

5 Double-click the PPP main config table icon
Results: a row of communication option fields will appear. The
following table will help define those options
Full Release 79
iSCS User's Guide
Configuring the PPP Application, Continued
Field Name Description Typical Value

Port The serial comm. port on the device used to COM4
communicate to the remote client.
Baud The transmit/receive data rate used for this serial 9600 bps
comm. port.
Modem settings must be set to match this value.
Bits per char Number of data bits per character. 8
Modem settings must match this value.
Parity type Odd or Even parity selection. None
Parity mode Enable or disable parity checking. Disable
Stop bits Number of stop bits sent after data bits. 1
RTS Device will assert the RTS signal during data Enable
transmission.
CTS Device will only transmit data when CTS signal is Disable
asserted by the modem.
DCD Device will only receive data when DCD signal is Enable
asserted by the modem.
RTS On delay Time (ms) that RTS is asserted before the start of 0
data transmission.
DCD On Time (ms) that receive data is inhibited after 0
delay receiving an asserted DCD signal.
RTS Off Time (ms) that RTS is kept asserted after the end of 0
delay the message.
Max PPP Maximum size (in bytes) of a data packet PPP will 2048
receive unit encapsulate for transmission in a frame.
(MRU)
May be negotiated by PPP to a lower value based
on client options.
80 Full Release
iSCS User's Guide
Procedure 2, Configuring B057 (continued)
Field Name Description Typical Value

ACCM Use of Asynchronous Control Character Mapping Disable
(ACCM) will reduce data transfer efficiency by up
to 50%.
This option should only be used when the data link
equipment requires its use.
CHAP Enable/disable CHAP (Challenge Handshake Enable
Authentication Protocol) authentication.
CHAP will periodically re-check Username and
Password during session for added security.
Challenge The number of attempts sending CHAP challenge 2
retries requests before receiving a valid response or
dropping the connection.
Challenge The period (in minutes) between two CHAP 5
period challenges during normal communication.
Procedure 2, The following steps will complete the configuration of the B057 PPP Driver
continued application
Step Action
6 Click the PPP user configuration tab at the bottom of the window.
Results: The default values shown in the example below should appear.
Full Release 81
iSCS User's Guide
Procedure 2, continued (continued)
Step Action
7 Each record in this table defines a username and password pair that
must be provided by the client upon connection, and when a CHAP
challenge request is transmitted by the device.
Type a valid username / password pair into the fields.
Notes: This configuration table is only used when CHAP is enabled.
The number of users that can be configured is not limited, and

all users are permitted on all configured communication ports.
8 Close all device windows, and Generate (the downloadable files for) the
configuration
9 Download and check the new configuration for errors, before starting the
next lab.
82 Full Release
iSCS User's Guide
Exercise 17: Testing the PPP Configuration
Establishing a PPP Connection
Background The preceding Exercise 15: Configuring a PC for PPP and Exercise 16:
Configuring the Device for PPP will allow a remote PC client to dial into a serial
port on the target device and establish an IP connection to applications running in
that device.
As a test, the following procedures will show:
a way to verify that the connection is established, and
how to connect to a devices WESMAINT facility using a Windows TELNET
client utility.
Prerequisite Before this lab can be performed:

Exercise 15: Configuring a PC for PPP and Exercise 16: Configuring the
Device for PPP (or equivalent) must be completed
Configuration file must be downloaded to the target device
Dialup modems must be installed and configured on both the PC and the target
device
Procedure This procedure shows how to establish a PPP connection to the target device, and a
simple test to verify communication.
Step Action
1 Double-click My Computer on your desktop, and then double-click
Dial-up Networking.
Results: A dialog box similar to the one below will appear.
Full Release 83
iSCS User's Guide
Establishing a PPP Connection, Continued
Step Action
2 Select the appropriate entry in the Phonebook entry to dial field, and
click the Dial button.
Results: The following password prompt dialog will appear
3 Type the User name and Password into the fields, and click OK.
Results: A pop-up will inform you that dialing is in progress, and the
modem speaker may be heard during dialing and connect
negotiation.
4 Open an MS-DOS window, and type:

ping x.x.x.x
and press ENTER
where: x.x.x.x is the IP address of PPP the application in the device.
Note: The IP address of the target devices PPP application will
always be equal to one more than the address defined in
Exercise 15: Configuring a PC for PPP, Step 16
Example: The IP address defined in, Step 16 was:
1.1.1.1
The IP address of the target devices PPP application becomes:

1.1.1.2
Results: A DOS window similar to the one following will be displayed.
84 Full Release
iSCS User's Guide
Establishing a PPP Connection, Continued
Step Action
5 If the connection is successful, the target device will reply four times,
showing the time taken for the reply to be received back at the PC.
6 From the same MS-DOS window, type:

telnet x.x.x.x
and press ENTER
Results: A blank TELNET window will open
Note: The same TELNET utility can be started by clicking Start |
Programs | Accessories | TELNET
7 Press ENTER to bring up the WESMAINT welcome display.

8 Type the correct username and password, and press ENTER to log in to
WESMAINT.
Note: Because the WESMAINT connection is made using TELNET
over the PPP IP link, you will be subject to the same
restrictions as a LAN-based TELNET connection.
Procedure By performing the preceding procedure, you can see how any configured PC can dial
Complete into a devices PPP dialup port and remotely perform a variety of tests and
maintenance functions, without the need of any additional software.
The following procedure will show how you can use Config Pro to make the
connection even simpler.
Full Release 85
iSCS User's Guide
Exercise 18: PPP Config Pro - WESMAINT Links
Using PPP to Access WESMAINT from Config Pro
Background Exercise 15: Configuring a PC for PPP and Exercise 16: Configuring the Device
for PPP allows a remote PC client to dial into a serial port on the target device and
establish an IP connection to a WESMAINT application in that device.
This lab shows how to use Config Pro to simplify the connection and log in by using
its integrated communications utilities.
Prerequisite Before this lab can be performed:

Exercise 15: and Exercise 16: (or equivalent) must be completed
Configuration file must be downloaded to the target device
Dialup modems must be installed and configured on both the PC and the target
device
Config Pro must be installed on the client Windows NT PC
Procedure This procedure shows how to use Config Pro to establish a PPP connection to the
target device, and log in to WESMAINT on that device.
Step Action
Set up Config Pro for PPP
1 Open the Config Pro project and right-click the icon that represents the
target device.
2 Click Communications | Communications options
Results: The following dialog box will appear
3 Click the PPP option check box, to select it.

Results: a new PPP tab will appear at the top of the dialog box.
86 Full Release
iSCS User's Guide
Using PPP to Access WESMAINT from Config Pro, Continued
Step Action
4 Click the PPP tab
Results: The following dialog will appear.
5 Select the appropriate entry in the Dial-up Networking Entry field.

Note: Dial-up Networking entries can be created or edited from this
dialog, if necessary.
6 Type the Username and Password for this devices PPP application,
into the fields, and click OK.
Connect to Device Via PPP
7 Verify the iSCS device icon is selected. Click once on it if it is not.

8 Click the Terminal Emulator item in the Config Pro Speed Bar.
Results: A pop-up will inform you that dialing is in progress, and the
modem speaker may be heard during dialing and connect
negotiation.
When connection is complete, the Config Pro Terminal

Emulator window will be open, and blank.
9 Press ENTER to bring up the WESMAINT welcome display, and press F2

to log in.
Note: Because the WESMAINT connection is made using TELNET
over the PPP IP link, you will be subject to the same
restrictions as a LAN-based TELNET connection.
10 Press CONTROL-L when finished WESMAINT session, to log out and

disconnect modem connection.
Full Release 87
iSCS User's Guide
88 Full Release
Chapter 15: Advanced Monitoring
Applications
Overview
Introduction With an iSCS LAN system installed and operating, the door is now open to use the
high-bandwidth available for several advanced applications.
This chapter introduces some of those applications, with a short discussion of each
one.
If the reader is interested in learning more about any of these applications, please
consult your GE Energy Services representative for more information or
documentation.
Topic See Page

Virtual Terminal 90
Virtual Connect 91
File Transfer 92
Digital Fault Recording 93
Power Quality 94
Other Features of iSCS 95
Full Release L-89
iSCS User's Guide
Virtual Terminal
Virtual Terminal The Virtual Terminal application (A155) is an optional software feature of an iSCS
Defined device that provides:
the capability for a WESMAINT user to transparently access and communicate
through a remote devices select serial communication port.
Communicate Any serially connected device that normally communicates with a local serial ASCII
with What? terminal or device. Examples may include:
maintenance ports
diagnostic display interfaces
configuration ports
data display ports
Virtual Terminal The remote TELNET access (via an iSCS LAN) to a devices WESMAINT facility
and iSCS automatically extends the Virtual Terminal function to LAN-connected TELNET
clients
90 Full Release
iSCS User's Guide
Virtual Connect
Virtual Connect A Virtual Connection is a link from a selected software application running on a
Defined Windows PC to a software application running on a remote iSCS device.
The connection itself is made to appear Virtually the same as a direct serial
connection from the PCs communication port to the application running in, or IED
attached to, a local iSCS device.
What Does VC When a Virtual Connect session is launched and the connection to the remote
Do? device is established, Virtual Connect starts at the beginning of a customized script,
sending specified character sequences, waiting for specified responses and executing
special commands until it reaches the end of the script.
When the script completes, and the connection is established successfully, a defined
user application is launched.
This user application can now use the connection as though it was a direct serial link
from the PCs serial port to the remote target application or IED.
Can Use Virtual Using a Virtual Connect utility on their LAN connected PC, in conjunction with the
Terminal Virtual Terminal application in the target device, a user can setup what appears to
be a direct serial connection from an application on their PC to a remote end devices
attached IED interface.
This allows the use of an iSCS devices ASCII serial or binary interface to
communicate directly with an attached IED to:
change a configuration setting
retrieve an oscillographic record
perform some other function which does not need to be performed immediately
(i.e. in real-time).
The Connection Virtual connections to a remote device may be done in one or more of these ways:
using the same communication path that is used for real-time control and
monitoring.
This process may delay or suspend the real-time communication while the
virtual connection is active.
using a separate user interface port on the end device.
This is desirable because no loss or delay in the main communication link
will occur. It does, however, require two connections.
Full Release 91
iSCS User's Guide
File Transfer
Background Current implementations of iSCS use the Trivial File Transfer Protocol (TFTP) to
move data files between devices on an IP network
TFTP Reviewed TFTP is the Internet Protocols connectionless file transfer protocol.
It relies on the User Datagram Protocol, (UDP) to transport the messages from one
device to another.
Types of Files The TFTP file transfer process can transfer several types of files:
Transferred
COMTRADE formatted files for oscillographic or fault record data.
Configuration files
Code or application program files
Graphic plot or image files
92 Full Release
iSCS User's Guide
Digital Fault Recording
Components of The Digital Fault Recording (DFR) subsystem is made up of several components:
The DFR
The DFR Data Translation Application (DTA) B063,
Subsystem
an optional software component of the Gen. II and Gen. III D25.
The PowerLink Master Station
Used to interrogate the D25 for DFR data files, and log them to a database
The DirectView COMTRADE file viewer
Used by an operator to access and display the logged database files.
Virtual Connect utility
Allows the operator to remotely access the on-line configuration capability
of the DFR DTA
An iSCS LAN
Provides the high-speed network link to tie the PowerLink GUI to the iSCS
device running the DFR DTA
The DFR DTA When triggered:

Captures feeder current and voltage data on up to 15 analog channels.
The sampled values of current and voltage are collected and stored for up to 240
cycles. (4 Seconds @ 60 Hz)
The status values of up to 96 physical digital inputs for the time of the analog
waveform capture are also recorded
The Oscillographic waveform capture and the status information are combined
and stored in the COMTRADE file format.
Triggers Digital Fault Recording is triggered by:

an analog input change (measured or computed)
a digital input change
by a pseudo-control operation
This trigger allows the Digital Fault Recording process to be initiated by:
any event detected
other applications of the D25
an operator on demand.
Once Recorded The DFR DTA toggles a pseudo digital input point to signal that a COMTRADE file
is available to be requested. This digital input point is then reported to a master
station (PowerLink), which responds by initiating a request for the COMTRADE
file.
The file can then be transferred and archived to the GUI platform where the
Oscillographic file can be viewed with a Windows based viewer, like DirectView.
Full Release 93
iSCS User's Guide
Power Quality
Components of The Power Quality (PQ) subsystem is made up of several pieces of equipment and
the Power software:
Quality
Subsystem A D25 running the PQ DTA (B063), and Plant I/O DCA (P097).
A Personal Computer running PowerLink 3.07 or higher.
PowerLink Power Quality Module,
Used to interrogate the D25 for DFR data files, and log them to a database.
Virtual Connect utility
Allows the operator to remotely access the on-line configuration capability
of the PQ DTA
PowerLink Configuration Blaster (Version 3.07 only)
PQ Event Viewer, DirectView
Used by an operator to access and display the logged COMTRADE database
files.
An iSCS LAN
Provides the high-speed network link to tie the PowerLink GUI to the iSCS
device running the PQ DTA
What is the PQ The PQ DTA is an optional software component of the D25 which offers users the
DTA? ability to:
monitor voltage variations for short-duration and extended-duration sags, swells,
and interruptions.
triggers to start and stop recording a capture of the RMS voltage profiles of such
events.
generates alarms, formats them into DNP 3.0 complex objects, and alerts the
PowerLink host that an event has occurred and that a record is available.
After Capture The captured RMS voltage profile is converted into COMTRADE file format that
can be uploaded to a PowerLink host where the file can be stored in ODBC format.
The Oscillographic file can then be viewed with the PQ Event Viewer, DirectView, a
Windows based viewer.
On-Line The parameters which define:

Configuration
swell
sag
interruption events
the optional enabling of RMS voltage profiling of each event.
can be configured offline through the configuration system and during run-time
through an on-line configuration interface.
94 Full Release
iSCS User's Guide
Other Features of iSCS
Enhanced Advanced Applications

Automation
Preprogrammed Procedures
Platform
Volt / VAR Control
Load Shedding
LTC Control
Predictive Maintenance Information Capture and Display

Condition Based Monitoring
Asset Management
Advanced Power up device diagnostics

System WESMAINT
Diagnostics
PowerLink communications summary
LAN Sniffer
Open System LAN -

Architecture Ethernet or IEEE 802.3
TCP/IP
UDP/IP
TFTP
TELNET
DNP
IEC 104
UCA RFC 1006
Serial communications
Application library to support IED integration
Application library to support Master Station communication
Future - 100BASE-T/FL
Full Release 95

Swm0008 Iscs Users Guide

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Swm0008 Iscs Users Guide

Загружено:

Авторское право:

Доступные форматы

g GE Energy Services

iSCS User's Guide

Document Number : SWM0008

NOTICE OF 2003, General Electric Canada Inc. All rights reserved.

TRADEMARK WESDAC is a registered trademark of General Electric Company, General Electric

SWM0008 2.00 3 General

VERSION REVISION DATE INITIALS COMMENT

SWM0008 2.00 3 General

About This Document ..................................................................................................................................xi

Part A: A LAN & IP Networking Primer ........................................................................................ A-1

Chapter 1: Introduction to LANs...............................................................................................................1

Chapter 2: Network of Choice: Ethernet...................................................................................................5

Chapter 3: Ethernet Basics ......................................................................................................................11

Chapter 4: Extending Ethernet LANs .....................................................................................................19

Chapter 5: Internetworking Devices........................................................................................................23

Chapter 6: Background of the Internet Protocols....................................................................................31

Chapter 7: Internet Protocols...................................................................................................................37

Chapter 8: The IP to Ethernet Connection ..............................................................................................43

Part B: Introduction to iSCS..............................................................................................................B-1

Chapter 9: What is iSCS?..........................................................................................................................3

Chapter 10: Single or Dual Ethernet LAN..............................................................................................9

Chapter 11: TELNET and iSCS............................................................................................................27

SWM0008 2.00 3 General

Chapter 12: TFTP File Transfer............................................................................................................37

Chapter 13: Automatic Initialization - BootP .......................................................................................43

Chapter 14: Serial IP Connection - PPP................................................................................................71

Chapter 15: Advanced Monitoring Applications ..................................................................................89

Digital Fault Recording..................................................................................................................93

SWM0008 2.00 3 General

viii Full Release

Figure 3-1 10BASE5 Network ...................................................................................................................14

SWM0008 2.00 3 General

In this chapter This chapter contains the following topics

Topic See Page

Purpose of this Document

What This This document does not provide:

Contacting Us GE Energy Services Toll-Free: + 1.800.518.2303

SWM0008 2.00 3 General

xii Full Release

Who is the Audience

SWM0008 2.00 3 General

xiv Full Release

In this Part This Part contains the following Chapters

Topic See Page

SWM0008 2.00 3 General

A-2 Full Release

In this chapter This chapter contains the following topics

Topic See Page

SWM0008 2.00 3 General

Hardware Hardware components found in LANs include:

Components of a LAN, Continued

Software There are two primary categories of software found in LANs:

SWM0008 2.00 3 General

Introduction Ethernet is the LAN technology of choice for substation applications.

In this chapter This chapter contains the following topics

Topic See Page

Inherent Latency Token-passing LANs are:

Continued on next page

SWM0008 2.00 3 General

Why Ethernet?, Continued

SWM0008 2.00 3 General

Four Categories Peer-Peer Communications

Advantages of Through adherence to a standard, many benefits are expected:

Continued on next page