UserGd Axs4iccp 132095

AX-S4 ICCP
Users Guide
AXS4-ICCP-132-095
Revision 8
SISCO, Inc. 1999-2011

All Rights Reserved by:
Systems Integration Specialists Company, Inc.
6605 19 Mile Road, Sterling Heights, MI 48314-9921, U.S.A.
Tel: +1-586-254-0020, Fax: +1-586-254-0053
E-Mail: support@sisconet.com, URL: http://www.sisconet.com
Printed in U.S.A.
11/2011
AX-S4 ICCP for Windows

Users Guide
COPYRIGHT NOTICE
Copyright 1999-2011 Systems Integration Specialists Company Inc. All
Rights Reserved.
This document is provided under license to authorized licensees only. No part
of this document may be copied or distributed, transmitted, transcribed, stored
in a retrieval system, or translated into any human or computer language, in
any form or by any means, electronic, mechanical, magnetic, manual, or
otherwise, disclosed to third parties, except as allowed in the license
agreement, without the express written consent of Systems Integration
Specialists Company Incorporated, 6605 19 Mile Road, Sterling Heights, MI,
48314, U.S.A.
DISCLAIMER
Systems Integration Specialists Company, Inc. makes no representation or
warranties with respect to the contents of this manual and specifically disclaims
any implied warranties of merchantability of fitness for any particular purpose.
Further, Systems Integration Specialists Company, Inc. reserves the right to
revise this publication and to make changes in it from time to time without
obligation of Systems Integration Specialists Company, Inc. to notify any
person or organization of such revision or changes.
Revision 8
11/02/2011
Table of Contents
INTRODUCTION ........................................................................................................... 1
Chapter Descriptions ............................................................................................. 2
Terminology ........................................................................................................... 3
The AX-S4 ICCP Model ......................................................................................... 4
Supported Functionality ........................................................................................ 5
System Requirements ............................................................................................. 6
Assumptions ........................................................................................................... 7
Application Support ............................................................................................... 7
INSTALLATION ............................................................................................................ 9
Setup Task List ....................................................................................................... 9
Installation for Windows ...................................................................................... 10
Directory Structure .............................................................................................. 11
Multiple Ethernet adapters and TCP/IP .............................................................. 12
Stack Startup Considerations............................................................................... 13
AX-S4 ICCP Startup Considerations ................................................................... 14
TCP/IP (via RFC1006) Support........................................................................... 15
Activating the AXS4-ICCP Product ..................................................................... 16
Starting AX-S4 ICCP as a Normal Process ......................................................... 21
Running AX-S4 ICCP .......................................................................................... 21
GETTING STARTED.................................................................................................... 23
Configuration ....................................................................................................... 23
Using AX-S4 ICCP as an ICCP Server................................................................ 24
ICCP Addressing Issues....................................................................................... 24
Redundancy ......................................................................................................... 25
AX-S4 ICCP CONFIGURATION ................................................................................. 27
ICCP Configuration Utility.................................................................................. 28
BUILDING APPLICATIONS USING OPC ....................................................................... 73
OPC General Concepts ....................................................................................... 73
OPC Servers ........................................................................................................ 73
OPC Item Strings ................................................................................................. 73
General OPC Item Strings ................................................................................... 74
Local and Remote Item Strings ............................................................................ 75
Quality Flags ....................................................................................................... 76
AX-S4 ICCP Redundancy .................................................................................... 79
Local Server Data Values .................................................................................... 81
Local Server Messages ........................................................................................ 82
Local Server Devices ........................................................................................... 82
Local Server Status Information .......................................................................... 83
Remote Server General Information .................................................................... 84
Remote Server Link Information .......................................................................... 84
Remote Server Data Values ................................................................................. 85
Remote Server Transfer Sets ................................................................................ 86
Remote Server Information Messages.................................................................. 86
i
AX-S4 ICCP User's Guide
Remote Server Devices ......................................................................................... 86

Add a Remote Control Center Configuration ....................................................... 87
Reloading a Remote Control Center Bilateral Table ........................................... 87
Information Message Handling ............................................................................ 88
Device Handling ................................................................................................... 88
Selecting a Remote Device ................................................................................... 89
Operating a Remote Device ................................................................................. 90
Getting Tag Information from a Remote Device .................................................. 90
Setting Tag Information of a Remote Device ....................................................... 90
AX-S4 ICCP Statistics .......................................................................................... 90
Local Status Information ...................................................................................... 92
Error Handling ..................................................................................................... 92
Test Applications .................................................................................................. 93
REMOTE CONTROL CENTER IDENTIFICATION AND ASSOCIATION MATCHING ............ 95
AX-S4 ICCP Matching Algorithm ........................................................................ 96
Matching Criteria ................................................................................................. 97
AX-S4 ICCP REDUNDANCY SYSTEM ........................................................................ 99
Redundancy System Features ............................................................................... 99
Redundancy Definitions ..................................................................................... 100
Redundant System Block Diagram ..................................................................... 102
AX-S4 ICCP OPC Item Availability ................................................................... 103
Local ICCP Data Value Quality During Switchover ......................................... 103
Remote OPC Item Value Quality During Switchover......................................... 104
Deployment Options ........................................................................................... 104
Redundant AX-S4 ICCP Configuration Issues ................................................... 107
Basic AX-S4 ICCP Redundant Configuration Process ...................................... 107
On-Line AX-S4 ICCP Reconfiguration .............................................................. 108
Data Synchronization Issues .............................................................................. 109
AX-S4 ICCP MONITOR ........................................................................................... 121
Drop-Down Menus ............................................................................................. 122
Local Control Center Overview ......................................................................... 124
Statistics ............................................................................................................. 125
Logging .............................................................................................................. 127
Data Values ........................................................................................................ 131
Local Devices ..................................................................................................... 133
Local Messages .................................................................................................. 135
Remote Control Centers Overview ..................................................................... 136
Remote Control Center Messages ...................................................................... 148
Remote Control Center DSTS Overview............................................................. 149
Local Data Set Transfer Sets Overview .............................................................. 154
LOG VIEWER AND LOGGING .................................................................................... 159
Log File Locations ............................................................................................. 160
Sample Logging .................................................................................................. 168
ii
Table of Contents
ACSE MVL ......................................................................................................... 197

TROUBLESHOOTING ................................................................................................ 199
Problems establishing an Association ............................................................... 199
RPL Configuration Issues .................................................................................. 199
ADVANCED TOPICS ................................................................................................. 201
AX-S4 ICCP Registry Parameters ..................................................................... 201
OSI STACK REGISTRY PARAMETERS ...................................................................... 201
STACK CONFIGURATION ......................................................................................... 203
Using Database Configuration .......................................................................... 203
Configuration Utility.......................................................................................... 203
Configuring Host Names and Addresses ........................................................... 206
Configuring AR Names ...................................................................................... 206
ADDRESSING ISSUES ............................................................................................... 213
Presentation Address ......................................................................................... 213
ACSE Parameters .............................................................................................. 214
Addressing Concepts.......................................................................................... 215
Addressing ......................................................................................................... 217
INDEX ..................................................................................................................... 219
iii
iv
Chapter 1: Introduction
Chapter 1
Introduction
AX-S4 ICCP is an OLE for Process Control (OPC) Server that provides plug-in
connectivity to ICCP-TASE.2 for any Windows application supporting the popular
OPC Interface. With AX-S4 ICCP, any Microsoft Windows Software Application
Package that supports OPC as a client can use the ICCP protocols to access real-time
data in networked control centers and applications. It also allows Windows
applications to communicate with control centers and other applications over ICCPbased Ethernet networks.
Figure 1: AX-S4 ICCP Block Diagram
Chapter Descriptions
This manual explains how to interface OPC client applications to ICCP
devices or applications through SISCOs AX-S4 ICCP OPC Server. The
Users Guide will explain the mechanics of the interface process. It is
presented in the following sections:
Chapter 1, Introduction, a brief overview, system requirements, and
features supported by AX-S4 ICCP.
Chapter 2, Installation, describes how to install and use AX-S4 ICCP.
Chapter 3, Getting Started, outlines AX-S4 features and setup options.
Chapter 4, AX-S4 ICCP Configuration, describes the use of the ICCP
Configuration Utility.
Chapter 5, Building Applications using OPC, describes how to use AX-S4
ICCPs OPC server capabilities.
Chapter 6, Remote Control Center Identification/Association Matching,
describes connection control flexibility of AX-S4 ICCP.
Chapter 7, AX-S4 ICCP Redundancy System, describes how to use AX-S4
ICCPs redundancy features.
Chapter 8, AXS4-ICCP Monitor, describes an OPC client application
designed for monitoring and controlling AX-S4 ICCP.
Appendix A, Logging, describes the SISCO Log Configuration Utility and
Log Viewer. It describes selectable log masks and illustrates sample
logging for AX-S4 ICCP.
Appendix B, Troubleshooting, explains how to troubleshoot basic
problems with AX-S4 ICCP.
Appendix C, Advanced Topics addresses AX-S4 ICCP advanced
programming issues.
Appendix D, Stack Configuration, describes how to configure the Stack
using the configuration utility. It should not be necessary to use this utility.
It is retained for backwards compatibility.
Appendix E, Addressing Issues, explains the addressing scheme from the
network and programmatic points of view such as the Selector and AP
Titles.
2
Terminology
The following terms are used throughout the AX-S4 ICCP documentation.
Term
Description
Association
A special property of a class used to associate instances within an

Information Model. An association can be one-to-one, one-tomany, many-to-one, and many-to-many.
AX-S4 ICCP
This product provides the interface between control centers and

applications on the ICCP network and the Windows-based
Applications that can act as OPC clients.
Client
A role assumed by an application when interacting with other

applications that are assuming the server role. The client role is
generally assumed by an application that is making requests for
data from a server while the server is the application that owns
the data.
COM
Component Object Model.
ISO
International Organization for Standardization.

http://www.iso.org
ICCP
Inter-Control Centre Communications Protocol
ICCP Control
Center or
Application
This refers to the control center or application running on a

network using the ICCP (TASE.2) protocols for communication.
OPC
OLE (Object Linking and Embedding) for Process Control.

http://www.opcfoundation.org/
OPC Client
Application
This refers to an OPC application developed using a Software

Application Package or a programming tool such as Visual C++.
Server
A role assumed by an application when interacting with other

applications that are assuming the client role. The server role is
generally assumed by an application that is the authoritative
source for data that other client applications might request access
to or information about.
Software
Application
Package
This refers to a front-end Windows-based product. It is used to

provide the OPC or DDE functionality. Typically a SCADA,
HMI, or historian product.
3
Term
Description
TASE.2
IECC870-6-503 TASE.2 Services and Protocol V1996-08 and

IEC 870-6-802 TASE.2 Object Models V1996-08
XML
Extensible Markup Language. This is an international

specification that specifies how to construct documents (which
can also be messages) that contain information. It is based upon a
hierarchical ASCII based tagging scheme and is in prevalent use
in integration and Internet applications.
The AX-S4 ICCP Model

The AX-S4 ICCP Model provides a means for describing how the various
components work together.
SCADA/HMI
Package
XML
Import/Export
OPC Client
COM
DCOM
OPC Server
Bilateral
Tables
ICCP Clients
and Servers
ICCP
TCP/IP
ISO
Ethernet
Network
Figure 2: AX-S4 ICCP Model
Supported Functionality
OPC Interface
AX-S4 ICCP adheres to the OPC Specification V3.00. This specification can
be freely downloaded from the OPC Foundations web site at
http://www.opcfoundation.org. Download is free but you must register with a
valid email address.
AX-S4 ICCP supports the following server side OPC interfaces:
IOPCAsyncIO
IOPCAsyncIO2
IOPCAsyncIO3
IOPCBrowse
IOPCBrowseServerAddressSpace
IOPCCommon
IOPCGroupStateMgt
IOPCGroupStateMgt2
IOPCItemIO
IOPCItemMgt
IOPCItemProperties
IOPCServer
IOPCSyncIO
IOPCSyncIO2
IConnectionPointContainer
IDataObject
IEnumOPCItemAttributes
AX-S4 ICCP supports the following client side interface:
IAdviseSink
IOPCDataCallback
IOPCShutdown
System Requirements
Intel x86 32 or 64 bit based (or AMD based Intel compatible) computer
with a, hard disk with at least 2 GB free, 1GB RAM (minimum) and a
CD-ROM drive.
Windows XP Professional Version 2002 service pack 3,

Windows 2003 Standard R2 service pack 2,
Windows 2008 R2 64 bit Primary Test Operating System,
Windows 2008 R1 32 bit,
Windows 7 64 bit
Windows 7 32 bit.
WARNING:
AX-S4 ICCP is a 32 bit application. In addition, SISCOs 32-bit
OSILLC driver used for OSI connectivity will not install on any of
the 64-bit Windows systems. Only TCP/IP is tested and supported.
Any Software Application Package for Windows supporting OPC 3.0 or

OPC 2.05.
AXS4-ICCP-132-095-DEV or AXS4-ICCP-132-095-PAK. A
Development license is required before purchasing a PAK license.
HASP Software license file or HASP USB dongle. The decision as to

which one is determined at purchase. If using a software license file, a
permanent license file that enables the product to operate indefinitely is
available by web, email, or fax. Please follow the installation instructions
provided to obtain the permanent license file. A thirty-day demo license
file is provided with this product.
Note: Existing customers that have a printer port, Sentinel License or
USB dongle may continue to use that form of licensing.
An 802.3 network with TCP/IP (RFC1006).
For Windows, 1GB of Random Access Memory (RAM) and/or hard disk
space in addition to that required by Windows processing. (The operating
system swaps the contents of its RAM with the hard disk if the RAM does
not have enough memory to do all its processing). Increased memory
improves the performance of your system.
Additional hard disk space and memory to accommodate the applications

that you are running on your system.
ICCP control centers or applications with which to communicate.
Assumptions
You are familiar with the Microsoft Windows operating environment you
are using.
You are familiar with the ICCP (Inter-Control Centre Communications

Protocol IECC870-6-503 TASE.2 Services and Protocol V1996-08 and
IEC 870-6-802 TASE.2 Object Models V1996-08).
You are familiar with the OPC specification and the OPC features of the
OPC Client Application Software Package you intend to use.
The AX-S4 ICCP software will be installed on a system that meets the
minimum requirements described above.
Application Support
This document and the associated software have been designed with the intent
that the user will develop the necessary applications. It is assumed that the
user of this software will have knowledge and expertise in the Application
Software Package or Programming Tool.
SISCO is solely responsible for the proper operation of the AX-S4 ICCP
product and not the developed Client Application or the Application Software
Package that is used with AX-S4 ICCP. The support available from SISCO
for AX-S4 ICCP does not include support of the OPC Client Application
Software Package (e.g., PI, InTouch, etc.).
IF YOU NEED SUPPORT FOR AN APPLICATION SOFTWARE
PACKAGE OR PROGRAMMING TOOL, YOU MUST CONTACT THE
DEVELOPER OF THAT SOFTWARE FOR SUPPORT. SISCO cannot
provide support on the OPC Client Application Software Package.
Chapter 2: Installation
Chapter 2
Installation
The following section will provide detailed instruction for installing and using AX-S4
ICCP for Windows.
Note: Before uninstalling an older version of AX-S4 ICCP, be sure to backup all
configuration and database files in the \iccpcfg and \osill2 directories.
Specifically the following files: iccpcfg.mdb, and siscinf3.mdb.
Setup Task List

The following steps should be taken to setup and use AX-S4 ICCP.
1.
Install the network adapter per the instructions that accompany it.
2.
Start Windows.
3.
Install the AX-S4 ICCP product. See the next paragraph for information.
4.
Reboot your computer and restart Windows.
5.
Make sure all information is properly configured using the supplied

Configuration Utility.
6.
Start AX-S4 ICCP by clicking on the Start button and selecting

ProgramsSISCOAX-S4 ICCPAX-S4 ICCP. The SISCO Stack
will start automatically. See page 16 for more information.
7.
Start an OPC Client and use OPC Commands to communicate with

AX-S4 ICCP.
Installation for Windows

Due to extensive changes to comply with UAC requirements on Windows 2008,
and Windows 7, SISCO has moved the location of almost all SISCO installed files
compared to the previous AX-S4 ICCP product. By default, the new development
files are located in C:\Program Files\ SISCO\AX-S4 ICCP or C:\Program Files
(x86)\ SISCO\AX-S4 ICCP on 64 bit systems. The SISCO OSI Stack binaries
have not moved. Configuration files are now located in the Common Application
Data path. Existing configuration files (like the iccpcfg.mdb or siscinf3.mdb) are
preserved in a backup directory. The installation will convert the existing data
base files to the new format and can be found in the Common Application Data
path depending on the Windows OS.
Carefully follow the steps shown below to install AX-S4 ICCP.
1.
AX-S4 ICCP installation requires a user to have Adminstrator Privileges.
2.
Insert the AXS4-ICCP-132-095 CD-ROM into the CD-ROM drive.
3.
If the Autorun feature is enabled on your computer, go to Step 4.

Otherwise, click on Start, select the Run option, and type the following
command:
{d}:setup
where {d} designates the letter of your CD-ROM drive.
10
4.
When the AX-S4 ICCP Setup initializes, you are restricted to install AXS4 ICCP to a default set of folder names. The folder names may not be
changed. It is possible to install AXS4 ICCP to a hard drive other than
drive c.
5.
The installation script will search the Windows Registry for previously
installed product components and install over the top of any existing
installation. This is strongly recommended if updating the product. The
registry entries will be updated accordingly to reflect the path of currently
installed AX-S4 ICCP product. The default directory for installing
SISCO products is c:\ Program Files\SISCO or c:\ Program Files
(x86)\SISCO on 64-bit systems.
6.
Follow the instructions on the screen to complete the AX-S4 ICCP

installation.
7.
The installation sequence is as follows:

- all prerequisites such as the Visual C++ Redistributable
- license driver file
- LogViewer
- the rest of the AX-S4 ICCP Components including the ICCP Monitor
and ICCP Configuration Utility
- license activation software
Directory Structure
The following directory structure should now exist on your computer.
11
Directory Path
Description
\Program Files\SISCO\AX-S4 ICCP
AX-S4 ICCP Program
<Common Application Data>\SISCO\AX-S4

ICCP\Config
AX-S4 ICCP Client Log

and Configuration files
<Common Application Data>\SISCO\AX-S4

ICCP\Documentation
All AX-S4 ICCP

Documentation
\Program Files\SISCO\Common
SISCO OPCDAAuto.dll
C:\Windows\System32
<WINSYSDIR>
\Program Files\SISCO\License
SISCO License file
<Common Application Data>\SISCO
Sisco Software
Configuration,
Documentation and Log
files
The <Common Application Data> is different for various Windows

Operating Systems.
Windows XP/2003 Application Data Common directory:
\Documents and Settings\All Users\Application Data
Windows Vista/7/2008 Application Data Common directory:

\ProgramData
Multiple Ethernet adapters and TCP/IP

The SISCO Stack uses the underlying system to manage the TCP/IP connectivity in
single or multi-card environment. There is no need to configure multiple subnetworks
for TCP/IP connectivity in the SISCO Configuration Utility.
Only one Local Host should be configured and the IP Address could be set to
127.1.1.1.
12
Stack Startup Considerations

Under Windows, the Stack can run either as a Service or as a normal process. By
default on a new installation, the Stack is installed as a Service with the Startup Type
option set to Manual. If this option remains unchanged, the Stack will run as a normal
process. This means that the Stack will start whenever an application is started. If the
Startup Type option is set to Automatic and computer restarted, the Stack will run as a
Service and will be started automatically when the operating system powers up before
any users log in. However, no user interaction with the Stack will be possible.
To change the Startup option on Windows XP/2003/2008/Windows 7, follow these
steps:
1.
Click on Start, select Control Panel.
2.
Open Administrative Tools.
3.
Select Services.
4.
Locate the SISCO OSI Stack and double click on it.
5.
Select Startup type Automatic from the startup options.
13
AX-S4 ICCP Startup Considerations

Under Windows, AX-S4 ICCP can be run as a Service or a normal process.
AX-S4 ICCP is installed as a normal process. Start AX-S4 ICCP by clicking
on the Start button and selecting ProgramsSISCOAX-S4
ICCPAX-S4 ICCP. AX-S4 ICCP can also be started by OPC Clients.
Note: Since the AX-S4 ICCP Client is dependent on the SISCO OSI Stack
service, when this product is started at boot time, the stack also will be
started.
Running AX-S4 ICCP as a Service

During installation, AX-S4 ICCP is configured to run as a normal process in
the COM Service Control Manager Registry. If you want to use OPC and run
AX-S4 ICCP as a service, execute the following command:
In this case, the COM SCM will start AX-S4 ICCP as a service.
To revert to the original configuration and run as a manual process, execute
the following command:
In this case, the COM SCM will start AX-S4 ICCP as a normal process.
14
Note: These commands must be executed from the AX-S4 ICCP directory.
By default, AX-S4 ICCP is setup as a Service with the Startup Type option set
to Manual. To have AX-S4 ICCP run as a Service that is started
automatically when the operating system powers up, set the Startup Type
option to Automatic.
Note: AX-S4 ICCP is dependent on the SISCO Stack service, so when AXS4 ICCP is started at boot time the stack will be started as well.
TCP/IP (via RFC1006) Support

In order to support TCP/IP (RFC1006), install an Ethernet card and configure
the Internet Protocol (TCP/IP) that provides a compliant WINSOCK2
implementation on Windows.
15
Activating the AXS4-ICCP Product

(New Customers Only)
Notes: Users updating to latest version of AX-S4 ICCP product that have existing
licensing such as a USB dongle, or Sentinel software activation may continue
to use these without re-activating the software.
The AX-S4 ICCP product now uses HASP Software protection. This can be either a
USB Dongle or a software lock which must be activated. This product comes with a
30 day trial license.
Activated licenses can run on a full machine or a Virtual Machine. Using HASP,
products running with an activated license can be accessed through Remote Desktop.
If you are using a USB Dongle, attach it to an open USB port. The LED in the USB
Dongle will turn red when it detects the appropriate drivers. Customers must request a
USB Dongle at the time of purchase.
For existing AX-S4 ICCP users, a Dongle Exchange Form must be filled out and a fee
paid to cover the cost of the exchange. Please contact SISCO Technical Support for
more information.
If you are using a Dongle, skip the remaining software license activation steps below.
16
Initial Activation with Internet Access

To activate the AX-S4 ICCP product, click on the Start button and select
ProgramsSISCOAX-S4 ICCPActivate AX-S4 ICCP
The activation screen will tell you how many days are remaining on the trial
license. To activate a permanent license, enter the Activation Code into the
Product Key field and click on the Activate button. To exit this
application click on the Cancel button.
If you run this application and a permanent license is already activated you
there will be a message displayed to that effect.
Update License or New license with no Internet Access

To apply a new license if the machine does not have internet access, or
update, modify a license for the AX-S4 ICCP product, click on the Start
button and select ProgramsSISCOAX-S4 ICCPUpdate AX-S4
ICCP License
17
From the Collect Key Status Information tab, create a *.c2v file by
clicking on the Collect Information Button. Send this file to SISCO.
SISCO will make the modifications to your license and send back a *.v2c file.
Select this *.vc2 file from the Apply License Update tab and click on the
Apply Update button.
18
HASP Admin Control Center

To get information on all the HASP licenses on this machine, click on the
Start button and select ProgramsSISCOAX-S4 ICCPHASP
Admin Control Center. Select the Products options to display the installed
products on this machine.
19
Click on the Features button under Actions to get detailed information on the
Features installed for this license
License Changes
All license information is tracked in the individual AX-S4 ICCP log files. There are
two cases in which the license will become invalid.
1.
Adding/removing hard drive to/from the system will cause the license matching
criteria to fail.
2.
The AX-S4 ICCP product may have to be removed from the original machine and
transferred to another.
In either case, please contact SISCO Technical Support (support@sisconet.com) and

request a License Move Form to transfer the license.
20
Starting AX-S4 ICCP as a Normal Process

To start AX-S4 ICCP, click on the Start button and select
ProgramsSiscoAX-S4 ICCPAX-S4 ICCP. The AX-S4 ICCP icon
will appear on your taskbar.
Note: The SISCO OSI Stack will start automatically.
AX-S4 ICCP is now ready to respond to OPC requests from any Software
Application Package.
Running AX-S4 ICCP

On startup, AX-S4 ICCP will load the selected configuration (see Chapter 4,
AX-S4 ICCP Configuration on page 27 for more information) and optionally
establish any configured associations. In case of startup failures, examine the
log files axs4iccp.log and axs4iccp.err to determine the source of the
problem. These are found in the <Common Application Data>\ SISCO\AXS4 ICCP\Client directory. Please refer to the Appendix A: Log Viewer and
Appendix B:Troubleshooting.
21
Once AX-S4 ICCP has started successfully, maximize AX-S4 ICCP by clicking on the
AX-S4 ICCP icon. The following screen will appear and the Status and Log windows
will be displayed:
Figure 3: AX-S4 ICCP main screen

AX-S4 ICCP Status window is shown at the top of the AX-S4 ICCP main screen. It
indicates the number of current OPC clients, the number of configured Remote Control
Centers, the number of active associations, and the selected logging mode. If the
ViewStatus option is checked, status information on AX-S4 ICCP can be viewed
dynamically. If the ViewStatus option is not checked the status screen will not be
displayed.
AX-S4 ICCP Log is displayed at the bottom. It logs all general activity that allows
you to monitor ICCP and OPC activity. If ViewActivity Log is checked, all
activity related to the AX-S4 ICCP process can be viewed. If ViewActivity Log is
unchecked, the Activity Log screen will not be displayed.
Please refer to Appendix A: Log Viewer for more information on logging.
22
Chapter 3: Getting Started
Chapter 3
Getting Started
Configuration
The ICCP Configuration Utility (IccpCfg) is the primary tool for configuring
all aspects of AX-S4 ICCP. IccpCfg can be used to:
Configure network addressing
Configure AX-S4 ICCP control parameters
Configure Local Control Center objects
Configure Remote Control Centers
Configure Associations
Some features of IccpCfg are:
Supports multiple Local Control Centers
Supports multiple Bilateral Tables
Supports on-line reconfiguration
Supports Client Value Discovery
Supports Automatic Creation of DataSetTransferSets
Can export configuration information to XML
Can import configuration information from XML
See Chapter 4: AX-S4 ICCP Configuration on page 27 for more information.
23
AX-S4 ICCP for Windows User's Guide
Using AX-S4 ICCP as an ICCP Server

In order for AX-S4 ICCP to behave as an ICCP server, an OPC Client must
be available to provide data. Local storage is provided for all local data
values. This data is read by and reported to configured ICCP remote control
centers without intervention by an OPC Client. Information messages and
some device operations require responses from an OPC Client.
The level of OPC Client responsibilities can be altered using the Auto
parameters located in the AX-S4 ICCP General Parameters of the ICCP
Configuration Utility. When the Auto features are enabled, an OPC Client
needs to update the Value (or State) attribute and the
Quality.CurrentSource attribute of a local Data Value. When the Auto
features are disabled, an OPC Client needs to update all local Data Value
attributes. See the General Parameters section on page 28 for more
information.
ICCP Addressing Issues

The network address information for ICCP Control Centers is usually
contained in the Bilateral Agreement. For more information on Network
Addressing Basics, see Appendix E: Addressing Issues on page 213. To setup
local and remote network addresses using the ICCP Configuration Utility, see
the Addressing section of Chapter 4: AX-S4 ICCP Configuration on page 39
for details.
One of the fundamental responsibilities of an ICCP Server is Access Control.
To correctly enforce Access Control a server must be able to determine who is
calling. This is achieved by comparing the source address of an incoming
connection with remote addresses configured locally. AX-S4 ICCP uses a set
of rules for matching each element of the network address. These rules can be
modified if there are connection problems with other ICCP nodes. The default
rules are sufficient for interoperating with most other ICCP software products.
See Chapter 6: Remote Control Center Identification/Association Matching
on page 95 for more information on the AX-S4 ICCP Matching algorithm.
24
Redundancy
Two AX-S4 ICCP nodes can be set up as a redundant pair. The redundant pair
consists of an active node and a standby node. The active node maintains
ICCP associations. The standby node waits for a failover condition. The
redundant nodes pass messages to allow the standby node to detect a failover
condition in the active node. See Chapter 7: AX-S4 ICCP Redundancy System
on page 99 for more information.
Use the ICCP Configuration Utility to setup the Redundancy options. General
information is required for the redundancy connection. Several parameters are
used to determine when failover occurs. Options for synchronizing data are
also available. See Chapter 4: AX-S4 ICCP Configuration on page 27 for
more information.
OPC Item strings can be used to monitor and control the state of each node.
The redundancy items strings are only supported if AX-S4 ICCP is configured
as Redundant Primary Role or Redundant Secondary Role. See Chapter 5:
Building Applications Using OPC on page 73 for more information.
25
26
Chapter 4: AX-S4 ICCP Configuration
Chapter 4
AX-S4 ICCP Configuration

Objects for AX-S4 ICCP are defined using the ICCP Configuration Utility.
Using this utility, configuration data is maintained in an Access Database and
can be exported to an XML file. AX-S4 ICCP can read the data directly from
the database or from the XML file (This option can be set in the ICCP
Configuration Utility). The XML file can be edited with any editor but it is
strongly recommended that the ICCP Configuration Utility be used to ensure
that the XML file is error free.
To start the ICCP Configuration Utility, from the Start bar, select
ProgramsSISCOICCP ConfigurationICCP Configuration. It
brings up the following screen:
Figure 4: ICCP Configuration Utility main screen
27
ICCP Configuration Utility

The ICCP Configuration Utility is used to create and maintain Local Control
Center objects and Bilateral Tables for exchanging data with Remote Control
Centers. It also is used to set AX-S4 ICCP options for the ICCP server,
connection control, and redundancy control. Furthermore, the ICCP
Configuration Utility can be used to configure the SISCO OSI Stack. Before
using this utility to setup Local Control Center and Remote Control Center
addresses, please see Appendix E: Addressing Issues on page 213. The
following are configuration definitions available from the drop down menu
selections on the top:
File
Export
This feature exports Local Control Center information from the ICCP
Configuration Database to an XML configuration file.
Import
This feature imports Local Control Center information from a configuration
file (XML or CFG) to the ICCP Configuration Database.
Edit - Preferences
AR Modes - Configuration Mode
This specifies the mode of AX-S4 ICCP configuration. ICCP-Lite uses the
ICCP Configuration database (IccpCfg.mdb). AX-S4 ICCP uses the AX-S4
database (siscinf3.mdb).
AR Modes Display Mode
This specifies the style of AR Name configuration. Summary mode displays
all AR Name information as a single Addressing node independent of any
Local Control Center. Distributed mode displays AR Name information as
multiple Addressing nodes within a Local Control Center; each node, and
its AR Names are associated with a specific control center.
28
AR Modes Assignment Mode

This specifies the validation constraints on AR Names assigned to
associations. Constrained mode imposes AR Name validation checks based
on AR Display Mode. Unconstrained mode imposes no checks and allows
the assignment of any AR Name in the database.
General - Confirm Actions
Checking this box will enable the display of validation message boxes with
each action (e.g., Are you sure you want to do this?).
Data Set Calculation - Conservative
Checking this box instructs IccpCfg to assume that the remote node always
uses the ListOfVariables encoding option for DSTS reports, even when this
results in the report being too large to send. Most implementations
automatically switch to the more compact NamedVariableList encoding
option in this case, which allows more variables to be added to a DataSet.
Tree Navigation - Double Click
Checking this box will require a double click on a node in the navigation tree
to view a form in the right pane, disabling the single click option.
View Reset Column Sizes

Sets the column width of all configuration tables to the
default size.
Tools
Association Summary
This is the summary of configuration information for all associations. The
following parameters can be configured by clicking within a field and entering
the new data. Some fields will have dropdown boxes from which to make a
new selection. The Esc key can be used to end the edit and return the original
contents to the field.
Local Control Center
This is the name of the Local Control Center to which the
association belongs. It cannot be edited.
29
Remote Control Center

This is the name of the Remote Control Center to which the
association belongs. It cannot be edited.
Association
This is the name of the association.
Initiate
If this parameter is set to YES, it will indicate that the Local
Control Center will initiate associations with this Remote
Control Center. Set to NO, the association state will go from
IDLE to LISTEN when the association is started.
Local AR
This specifies the local AR Name used for the association. It will be
highlighted in red if it is missing or configured with an AR Name that does
not exist in the database.
Remote AR
This specifies the remote AR Name used for the association.
If Initiate is set to YES, the Local Control Center will
attempt to establish an association with this AR Name. It
will be highlighted in red if it is missing or configured with
an AR Name that does not exist in the database.
Remote AR2, Remote AR3, Remote AR4
Up to four remote AR Names can be selected for an association. If Initiate is
set to YES, the Local Control Center will attempt to establish an association
with Remote AR. When a connection to Remote AR cannot be established,
the Local Control Center will attempt a connection with each successive AR
Name (i.e., 2-4). Remote AR 2, Remote AR 3, and Remote AR 4 are optional.
Compact Database
This will reclaim space from deleted records in the configuration database.
Start AX-S4 ICCP
This option starts AX-S4 ICCP.
30
Start AX-S4 ICCP Monitor

This option starts the AX-S4 ICCP OPC Monitor. This program allows using
Windows Client Terminal Services (WTCS) and provides an improved
integration of AX-S4 ICCP with the user environment. See Chapter 8 for
more information on the functionality of the AX-S4 ICCP Monitor.
General Parameters
Configuration - Source
This specifies what AX-S4 ICCP will load at startup, a XML configuration
file or a Local Control Center from the ICCP Configuration database.
Configuration - File Name
This is the name of a XML configuration file that AX-S4 ICCP will load at
startup if Configuration Source is XML.
Configuration - Local Control Center Name
This is the name of a Local Control Center in the ICCP Configuration
database that AX-S4 ICCP will load at startup if the Configuration Source is
selected as DirectDatabase.
Spare Capacity - Num Called Association
AX-S4 ICCP will setup the number of called associations based on the
number of those already configured. This parameter indicates the number of
additional called associations to setup, which will allow for adding
associations to existing Remote Control Centers as well as adding new
Remote Control Centers.
Spare Capacity - Num Calling Association
AX-S4 ICCP will setup the number of calling associations based on the
number of those already configured. This parameter indicates the number of
additional calling associations to setup, which will allow for adding
associations to existing Remote Control Centers as well as adding new
Auto - Increment COV
If checked, AX-S4 ICCP will automatically increment the Change of Value
counter for a Local data value each time the value is written by an OPC
Client.
31
Auto - Time Stamp

If checked, AX-S4 ICCP will automatically update the timestamp for a Local
data value each time the value is written by an OPC Client.
Auto - Quality Flags
If checked, AX-S4 ICCP will automatically handle the quality flags associated
with a Local data value each time the value is written by an OPC Client. At
startup the quality flags are set to:
Validity = INVALID
CurrentSource = configured normal source
NormalValue = NORMAL
TimeStampQuality = VALID if Auto-TimeStamp is enabled
When an OPC Client writes the Value attribute of a Local data value, the
quality flags are set:
Validity = VALID
NormalValue = NORMAL If the Value written is within configured
range, else ABNORMAL.
Auto - Start Associations
If checked, AX-S4 ICCP automatically starts all configured associations.
Auto - Device Select Timeout
Indicates the number of seconds the server will wait for an operate request
before clearing the device state. Default is 30 seconds.
ICCP Services Enable Client DV Reads
If checked, AX-S4 ICCP will issue read requests to retrieve data for OPC
Clients when the requested remote data value is not configured into a
DSTransferSet. When disabled, an error is returned to the OPC Client if the
remote data value is not in a DSTransferSet. It is recommended that this
option be DISABLED as a poorly configured AX-S4 ICCP can flood a
remote ICCP server with read requests. Polling an ICCP Server for data can
cause association instability and poor performance.
32
Local Host Parameters

Normally recommend not changing these parameters.
Allow Multiple Local Hosts
By checking this box, multiple local hosts can be designated for use when the
SISCO Stack is configured to run over multiple network adapters.
Local Host, Local Host 2, Local Host 3, Local Host 4
The Local Host parameter designates a local host and shows the adapter
assigned to that local host. Local Host 2, Local Host 3, and Local Host 4 are
valid only when the Allow Multiple Local Hosts parameter is set.
Identification Parameters
Note:
Please refer to Chapter 6: Remote Control Center

Identification/Association Matching on page 95 for further
information regarding the use of the following parameters.
AE - Allow Missing
When this parameter is set to not checked (default), all AE Title elements that
are configured (locally) for the AR Name must be present in the Calling and
Called AE Titles. When checked, any AE elements not sent by the Remote
Control Center are treated as present and matched, regardless of whether they
are configured for the AR Name.
AE - Allow Extra
When this parameter is set to checked (default), it is acceptable for the
Remote Control Center to send AE elements that are not configured for the
AR Name. When set to not checked, all AE Title elements that are NOT
configured (locally) for the AR Name must NOT be present in the Calling and
Called AE Titles.
Local/Remote - Association/Address Matching Control Parameters
The matching control parameters of AP Title, AE Qualifier, AP Invoke, AE
Invoke, PSEL, SSEL, TSEL, and Net Address each affect a single local or
remote addressing element. If a matching control parameter is checked, then
the configured (locally) value of that parameter must match the value as
received in the initiate indication.
33
Matching Control Parameter
Default
Match Local AP Title
No
Match Local AE Qualifier
No
Match Local AP Invoke
No
Match Local AE Invoke
No
Match Local PSEL
Match Local SSEL
Match Local TSEL
Match Local Network Address
No
Match Remote AP Title
Match Remote AE Qualifier
Match Remote PSEL
Match Remote SSEL
Match Remote TSEL
Match Remote Network Address
No
OPC Parameters
Time Stamp Use ICCP Time Stamp
This option enables/disables the use of the ICCP time stamp as the OPC time
stamp for any remote data value. If the remote data value does not have an
associated timestamp, the Transfer_Set_Time_Stamp is used. The
Transfer_Set_Time_Stamp specifies the time the TransferReport was
generated at the TASE.2 server.
DSConditionsDetected Include in DataFlags
The option enables/disables the inclusion of DSConditions detected in the
ICCP Client Value DataFlags item string. It includes the following:
OtherExternalEvent
IntegrityTimeOut
OperatorRequest
ObjectChange
IntervalTimeOut
34
ICCP to OPC Quality Mapping

These options allow selecting the parts of the Quality Mask when the
DSConditionsDetected Include in DataFlags is checked. The
following options are available to be checked:
Use Time Stamp Quality If checked, TimeStampQuality is mapped to
OPC quality. The TimeStampQuality attribute has the value VALID if the
current value of the TimeStamp attribute contains the time stamp of when the
value was last changed, and has the value INVALID at all other times
Use Normal Value If checked, NormalValue is mapped to OPC quality.
The NormalValue attribute reports whether value of the point is within the
normal range.
Use Current Source If checked, CurrentSource is mapped to OPC
quality. The CurrentSource attribute specifies the current source of the data as
follows: TELEMETERED means the data value was received from a
telemetered site. CALCULATED means the data value was calculated based
on other data values. ENTERED means the data value was entered manually.
ESTIMATED means the data value was estimated (State Estimator, etc.)
Use Validity If checked, Validity is mapped to OPC quality. The Validity
attribute specifies the validity or quality of the PointValue data it is associated
with. These are based on the source systems interpretation as follows:
VALID means the Data value is valid. HELD means previous data value has
been held over. Interpretation is local. SUSPECT means the Data value is
questionable. Interpretation is local. NOTVALID means the Data value is not
valid.
Redundancy Parameters
Role
This is the redundancy role of this node. The options include Not
Redundant, Redundant Primary, and Redundant Secondary. Default
is Not Redundant.
Backup OPC Local Data Quality
Use this flag to set the quality of all local data values returned from a
Standby AX-S4 ICCP node to an OPC client. Options are Good,
Uncertain, and Bad. The default is Good.
35
Backup OPC Remote Data Quality

Use this flag to set the quality of all remote data values returned from a
Standby AX-S4 ICCP node to an OPC client. Options are Good,
Uncertain, and Bad. The default is Good.
Backup OPC Server State Suspended
If checked and the AX-S4 ICCP node is in STANDBY, calls to the OPC
Server function GetStatus will return SUSPENDED instead of
RUNNING.
Automatic Configuration Synchronization
The data synchronization feature can be used to keep the values of the Local
and Remote ICCP objects up to date in the Standby node. All data changes in
the Active node are sent to the Standby node when the appropriate data
synchronization mode is selected. Options are:
None
No automatic configuration synchronization takes place between the
Active and Standby AX-S4 ICCP nodes.
Active
Automatic configuration synchronization is syncd to the Active AXS4 ICCP.
Primary
Automatic configuration synchronization is syncd to the Primary
AX-S4 ICCP.
Secondary
Automatic configuration synchronization is syncd to the Secondary
AX-S4 ICCP.
36
Data Synchronization
This is the level of data synchronization to enable.
Options for Mode are:
Local
The Active AX-S4 ICCP node sends local object changes to the
Standby AX-S4 ICCP node. This data may or may not be current
on the standby node depending on the Buffer options below and the
stability of the RPL link.
Local and Remote
The Active AX-S4 ICCP node sends local object changes to the
Standby AX-S4 ICCP node as well as values received from
Remote Control Centers. This data may or may not be current on the
standby node depending on the Buffer options below and the stability
of the RPL link.
Remote
The Active AX-S4 ICCP node values received from Remote
Control Centers. This data may or may not be current on the standby
node depending on the Buffer options below and the stability of the
RPL link.
Pipeline
This is the number of data sync messages that can be sent to the
Standby node before receiving a response.
Buffer Time
This is the number of milliseconds to accumulate data changes
before sending a data sync message to the Standby node.
Buffer Count
This is the maximum number of data changes to accumulate before
sending a data sync message to the Standby node.
Association Connect Timeout
Enabled
This enables the link connection timeout option.
37
Timeout
This is the number of milliseconds that the active node is given to
establish at least one ICCP Link.
RPL Connection
Port
This is the TCP Port number for the connection between the primary
AX-S4 ICCP and the secondary AX-S4 ICCP (RPL connection).
Partner IP
This is the IP Address for the RPL connection. It is only required for
the Redundant Primary node.
Seal Mode
The RPL Security Seal system provides an authentication and data validation
mechanism, using private key encryption, CRC data validation, and antiplayback timestamps.
There are three types of Seal Modes:
NONE (0) This allows RPL to avoid performance penalty in the case of an
externally secured environment.
FALLBACK (1) This is valid only for Primary mode, allows the primary to
automatically switch between SEAL and NOSEAL modes. This mode is
intended to be used when migrating to the SEAL version; the NOSEAL
version is compatible with the previous version of RPL protocol.
ALL (2). This requires the use of SEAL mode and is the default mode.
Seal Time Window
This is the maximum allowed clock time differential between clocks in each
AX-S4 ICCP. If the difference is exceeded the RPL link will become
disabled. The default is 10 seconds.
AX-S4 ICCP defaults to using Seal Mode ALL. If updating from an AX-S4
ICCP version BEFORE V4.0059 - 1) Both AXS4 ICCP systems will have to
be upgraded before RPL can be reestablished or 2) After upgrading the first
redundant AX-S4 ICCP system, Open the redundancy form and set the Seal
mode from ALL to None. Having a Seal Mode of None allows unsealed RPL
communication with a legacy AX-S4 ICCP system.
38
RPL Timers
Retry Time
This is the frequency of RPL reconnect attempts in milliseconds.
Startup Time
This is the number of milliseconds the Redundant Secondary node
waits, after startup, for the RPL connection before switching to
"Active" mode.
Heartbeat Tx Period
This is the frequency, in milliseconds, of heartbeat transmissions to
the partner node.
Switch to Active Delay
This is the number of milliseconds to wait before implementing a
manual switchover.
Addressing
The following parameters can be configured by clicking within a field and entering the
new data. Some fields will have dropdown boxes from which to make a new selection.
If editing in a table, the Esc key can be used to end the edit and return the original
contents to the field. The Basic tab includes Name, Use TCP/IP, IP/Net Address, AP
Title, AE Qualifier, and Comment. The Selectors tab includes Name, PSEL, SSEL,
and TSEL. The All tab includes all the fields.
Name
This is the Application Reference Name (AR Name), an ASCII string of up to
64 characters that identifies the Application Entity (AP Title and AE
Qualifier) and Presentation Address information associated with an
application.
Use TCP/IP
This indicates whether the AR Name maps to TCP/IP stack. Only TCP/IP is
supported.
IP/Net Address
This is the Presentation Address of the application the AR Name is
representing. TCP/IP uses a host name or IP Address (e.g., 204.254.125.148).
39
AP Title
This is the Application Process Title, an Object Identifier assigned by the
network naming authority to represent a particular application process. This
parameter is optional, although in ICCP applications it is commonly used.
AE Qualifier
This is an optional integer value used to qualify the Application Entity.
Description
This is an optional field for the user to enter a description for the Local
Control Center. The maximum length is 255 characters.
PSEL
This is an octet string representing the Presentation Selector. It is used to
identify a Presentation SAP. Only one local AR Name can be configured
without a PSEL, SSEL, and TSEL. The maximum PSEL size is 16 octets (32
ASCII encoded hex digits). This field is optional and is used as an advanced
feature.
SSEL
This is an octet string representing the Session Selector. It is used to identify a
Session SAP. Only one local AR Name can be configured without a PSEL,
SSEL, and TSEL. The maximum SSEL size is 16 octets (32 ASCII encoded
hex digits). This field is optional and is used as an advanced feature.
TSEL
This is an octet string representing the Transport Selector. It is used to
identify a Transport SAP. A maximum number of 8 different transport
selectors can be configured. Only one local AR Name can be configured
without a PSEL, SSEL, and TSEL. The maximum TSEL size is 32 octets (64
ASCII encoded hex digits). This field is optional and is used as an advanced
feature.
Local Control Center

The following parameters can be configured by clicking within a field and
entering the new data. Some fields will have dropdown boxes from which to
make a new selection. If editing in a table, the Esc key can be used to end the
edit and return the original contents to the field.
40
Name
This is a unique text string to identify the name of the ICCP Local Control
Center. The maximum size is 32 characters.
Max MMS Message Size
This is the maximum number of bytes that can be transferred in a single MMS
request. The default is 32000.
Max Data Sets
This is the maximum number of data sets allowed on each link. The default is
10.
Max Data Set Transfer Sets
This is the maximum number of transfer sets allowed on each link. The
default is 10.
Description
This is an optional field for the user to enter a description for the Local
Control Center. The maximum length is 255 characters.
When adding a Local Control Center, the following parameters become
available:
Derive from Remote Control Center
If this box is checked, it allows a Local Control Center to be created from a
Remote Control Center.
Select Remote Control Center
This parameter is available only when "Derive from Remote Control Center"
is checked. Select a Remote Control Center from which to create the Local
Control Center.
41
Local Control Center Data Values

Name
This is a unique text string representing the name of the data value. Each
name is up to 32 characters in length consisting of alphanumeric characters
(az, AZ, and 09), underscore (_) or dollar sign ($). The first
character must be a letter.
Data Type
This is the type of the data value. The following is a list of valid types:
State
StateQ
StateQTimeTag
StateQTimeTagExtended
StateExtended
StateSupplement
StateSupplementQ
StateSupplementQTimeTag
StateSupplementQTimeTagExtended
StateSupplementExtended
Discrete
DiscreteQ
DiscreteQTimeTag
DiscreteQTimeTagExtended
DiscreteExtended
Real
RealQ
RealQTimeTag
RealQTimeTagExtended
RealExtended
42
Normal Source
This is a field required to support AutoQualityFlags. Possible values include
Telemetered (The data value is normally received from a telemetered site)
Calculated (The data value is normally calculated based on other data
values), Entered (The data value is normally entered manually), or
Estimated (The data value is normally estimated (State Estimator, etc.)).
Normal Min
This is an optional field required to support AutoQualityFlags. It is the
smallest value considered normal for the data value.
Normal Max
This is an optional field required to support AutoQualityFlags. It is the largest
value considered normal for this data value.
Map Info
This is an optional field used to provide an efficient coupling to the real data.
For example, it may be an index, a SQL statement, a name or an address (Map
Info is unused by AX-S4 ICCP).
Description
This is an optional field used to enter a description for the data value. The
maximum length is 255 characters.
Add a Data Value
This dialog box is used to add a data value for the Local Control Center. To
access this box:
1.
Click on the appropriate Data Values node in the navigation tree of the left
pane. Note: Server data values are not added; they are selected from the
list of Local Control Center data values.
2.
Click on the Add button in the right pane to bring up the Add Data Value
dialog box.
3.
Enter a unique Name. All other fields are optional.
4.
Click on the Insert button to add the data value. The dialog box will
remain open, allowing you to add other data values.
43
5.
When finished, click on the OK button to save all added data values and
close the dialog box, or click on the Cancel button to discard all added
data values and close the dialog box.
6.
In the right pane, click on the OK button to save changes and close the
dialog box, or the Cancel button to discard changes and close the dialog
box.
Local Control Center Devices

Name
This is a text string identifying the name of the device. Each names is up to 32
characters in length consisting of alphanumeric characters (az, AZ,
and 09), underscore (_) or dollar sign ($). The first character must
be a letter.
Device Type
Indicates the device type. Valid options include Command, Real, or Discrete.
Command is a 16-bit integer, Real is a 32-bit real, and Discrete is a 16-bit
integer.
SBO
If Yes, it indicates that this is a Select-Before-Operate device. SelectBefore-Operate Device objects require the ICCP client to select the Device
object before attempting to operate on it. The server shall check if the Device
object is available and operable, and return a success or failure of the client's
select required depending upon the Device object's state.
Check Back ID
This is used for SBO Devices only. This attribute contains a symbolic
description of the physical object being controlled. The data is returned by the
system operating the physical object to the system requesting the operation so
that the system requesting the operation can be assured the proper object has
been selected. The Check Back ID is a 16-bit integer.
Select Timeout
This is used for SBO devices only. It indicates the number of seconds the
server will wait for an operate request before clearing the device state.
44
Tag Enabled
Indicates that this device can be tagged. Tags are usually used to prevent
operation of a device.
Map Info
For example, it may be an index, a SQL statement, a name, or an address
(Map Info is unused by AX-S4 ICCP).
Description
This is an optional field used to enter a description for the device. The
Add a Device
This dialog box is used to add a device for the Local Control Center. To
access this box:
1.
Click on the appropriate Devices node in the navigation tree of the left
pane. Note: Server devices are not added; they are selected from the list
of Local Control Center devices.
2.
Click on the Add button in the right pane to bring up the Add Device
dialog box.
3.
4.
Click on the Insert button to add the device. The dialog box will remain
open, allowing you to add other devices.
5.
When finished, click on the OK button to save all added devices and
devices and close the dialog box.
6.
box.
45
Local Control Center Messages

Info Reference
This is a unique integer used to identify the information message. It triggers
the processing of the message by the receiving system because it is found in
the first variable of a Block 4 message. For example, if InfoReference=29, the
first variable in the report, Info_Mess_Header, would contain number 29 as
the first component of the InfoBuffHeader.
Max Size
Remote Control Centers

Name
This is a unique text string to identify the ICCP Remote Control Center. The
maximum size is 32 characters.
Note: The Remote Control Center name should not be the same as the Local
Control Center name.
TASE.2 Version
This indicates the version of TASE.2 being used - options are 1996-08 and
2000-08.
Description
This is an optional field used to enter a description for the Remote Control
Center. The maximum length is 255 characters.
46
When adding a Remote Control Center, the following parameters are available:
Derive from Local Control Center
If this box is checked, it allows a Remote Control Center to be created from a
Local Control Center.
Select Local Control Center
This parameter is available only when Derive from Local Control Center
is checked. Select a Local Control Center from which to create the Remote
Control Center.
Default Scope
This selects a default scope for Data Values created for this Remote Control
Center. Select either ICC or VCC.
Default Client Data Value Access
This selects a default access for Data Values created for this Remote Control
Center. Select either the Read Only or Read/Write radio button.
Remote Control Center Associations

edit and return the original contents to the field. The Basic tab includes
Name, Local AR, Initiate, Retry Delay, Remote AR, Service Role, and
Description. The Remote ARs tab includes Name, and Remote ARs 2 4.
The Parameters tab includes Name, Max MMS Message Size, Max
Requests Pending, Max Indications Pending, Max Nesting Level, and
Heartbeat. The All tab includes all the fields.
Basic Tab
Name
This is a unique name of the link between the local control center and the
remote control center (text string, 32 characters). It identifies the association.
47
Local AR
This specifies the Local AR Name used for the association. It will be
highlighted in red if it is missing, if it is configured with an AR Name that
does not exist in the database, or if it has the same selectors as another AR
Name being used as a Local AR for the Control Center.
Initiate
If this parameter is set to Yes, it will indicate that the Local Control Center
will initiate associations with this Remote Control Center. If set to No, the
association state will go from IDLE to LISTEN when the association is
started.
Retry Delay
If the previous entry, Initiate, is set to Yes, this is the number of seconds to
wait before retrying a timed out association request.
Remote AR
This specifies the remote AR Name used for the association. If Initiate is set
to Yes, the Local Control Center will attempt to establish an association with
this AR Name. It will be highlighted in red if it is missing or configured with
an AR Name that does not exist in the database. If Initiate is set to No, this
AR Name will be used to match incoming association requests.
Service Role
The Service Role is part of a Bilateral Table Agreement. It indicates the ICCP
activity required for the remote control center - Client, Server, or both
Client & Server.
Description
This is an optional field used to enter a description for the association. The
Remote ARs
Remote AR 2, Remote AR 3, and Remote AR 4
Up to four remote AR Names can be selected for an association. If Initiate is
set to Yes, the Local Control Center will attempt to establish an association
with Remote AR. When a connection to Remote AR cannot be established,
the Local Control Center will attempt a connection with each successive AR
Name (i.e., 2-4). Remote AR 2, Remote AR 3, and Remote AR 4 are optional.
48
If Initiate is set to No, these AR Names will be used to match incoming

association requests.
Parameters
Max MMS Message Size
This is the maximum size of the MMS message size. It cannot exceed the Max
MMS Message Size designated for the Local Control Center.
Max Requests Pending
This is the maximum number of outstanding of ICCP Client Requests. The
default is 5.
Max Indications Pending
This is the maximum number of remote requests the ICCP Server will allow.
The default is 5.
Max Nesting Level
This is the suggested maximum data structure nesting level to use. AX-S4
ICCP supports a maximum of 10 levels of nesting. Each structure or array and
each structure or array within a structure or array is equivalent to one nesting
level. The default is 5.
Heartbeat
This is a timer that, when enabled, will send an ICCP Identify request to
Remote control centers to ensure a valid TCP/IP connection. When a
communication path is lost, this allows for quicker association failure
detection and recovery. Enabling this feature is recommended for redundant
systems because it can speed up failover in situations where TCP/IP socket
level connections would otherwise linger. A value of 0 (the default) disables
the HeartBeat.
Remote Control Center Bilateral Tables

Bilateral Tables are the computer representation of the Bilateral Agreement. A
Bilateral Agreement is an agreement between two control centers which
includes the data elements to be accessed and the means to access them. The
representation used is a local matter of the ICCP implementation.
49

edit and return the original contents to the field. The Basic tab includes
Name, Bilateral Table ID, Active, Local Domain, Remote Domain, Shortest
Interval, and Description. The Block tab includes Blocks 1-9. The Options
tab includes Name, Remote Data Value Validation, Remote Data Value Get
Config, and Remote Data Value Exclude Invalid. The All tab includes all the
fields.
Basic
Name
This is a unique text string used to identify the Bilateral Table.
Bilateral Table ID
This is the symbolic name (up to 32 characters) of the bilateral table version,
which is matched to the remote systems bilateral table version during the start
of an association. If the two do not match, the association is not allowed.
Active
This parameter indicates whether the Bilateral Table should be used to
communicate with the Remote Control Center. Only one Bilateral Table may
be active at a time and configuration MUST be reloaded after changing this
parameter.
Local Domain
This is the name of the domain supported by the Local Control Center for use
by the remote client. This is a text string up to 32 characters in length
consisting of alphanumeric characters (az, AZ, and 09),
underscore (_) or dollar sign ($). The first character must be a letter.
Remote Domain
This is the name of the domain supported by the Remote Control Center for
use by the local client. This is a text string up to 32 characters in length
consisting of alphanumeric characters (az, AZ, and 09),
underscore (_) or dollar sign ($). The first character must be a letter.
Shortest Interval
This is the shortest periodic interval (in seconds) allowed for transfer sets.
The default is 1 second.
50
Description
This is an optional field used to enter a description for the Bilateral Table.
The maximum length is 255 characters.
Block 1 Block 9
These parameters indicate the blocks to be used when communicating with the
Remote Control Center. These are the ICCP Blocks to be included in the
ICCP Servers Supported Features. AX-S4 ICCP Supports Blocks 1, 2, 4,
and 5 ONLY.
Server Data Values

Name
This is a text string identifying the name of the data value and must be a valid
Local Control Center data value. It cannot be edited.
Scope
VCC indicates that the scope of the data value is VMD specific and is global
to the Local Control Center. ICC indicates that the scope of the data value is
domain specific and is limited to the domain designated for use by the Remote
Control Center.
Data Type
This is the type of the data value. Editing of this field is restricted to data
types that fall within the data type of the Local Control Center data value that
was selected.
The following is a list of valid types:
State
StateQ
StateQTimeTag
StateExtended
StateSupplement
StateSupplementQ
Discrete
DiscreteQ
DiscreteQTimeTag
51
DiscreteExtended
Real
RealQ
RealQTimeTag
RealExtended
Read Only
If set to Yes, this indicates that the TASE.2 client cannot modify the data
value.
Map Info
For example, it may be an index, a SQL statement, a name or an address (Map
Info is unused by AX-S4 ICCP).
Select
This screen allows you to select preconfigured data values for the Bilateral
Table.
52
1.
With the mouse, grab the menu scroll bar of the Available Data Values or
the Included Data Values and scroll up or down to view the entire list.
2.
To select a data value for the Bilateral Table, double click it in the
Available Data Values list or select it and press >.
3.
To remove a data value from the Bilateral Table, double click it in the
Included Data Values list or select it and press <.
4.
The Scope button in the lower right hand side selects a default scope for
Data Values created for this Remote Control Center. Select either ICC or
VCC.
5.
Data Access button in the lower right hand side selects a default access
for Data Values created for this Remote Control Center. Select either
Read Only or Read/Write radio button.
6.
When finished, click on the OK button to save changes and close the
dialog box, or click on the Cancel button to discard changes and close
the dialog box.
Server Devices
Name
This is a text string identifying the name of the device and must reference a
previously defined Local Control Center Device. It cannot be edited.
Scope
to the Local Control Center. ICC indicates that the scope of the device is
Control Center.
Device Type
This is the type of the device. It cannot be edited.
Tag Enabled
If set to Yes, this indicates that the device can be tagged.
Map Info
Select
This screen allows you to select preconfigured devices for the Bilateral
Table.
1.
With the mouse, grab the menu scroll bar of the Available Devices or the
Included Devices and scroll up or down to view the entire list.
2.
To select a device for the Bilateral Table, double click it in the Available
Devices list or select it and press >.
3.
To remove a device from the Bilateral Table, double click it in the

Included Devices list or select it and press <.
4.
The Scope button in the lower right hand side selects a default scope for
Data Values created for this Remote Control Center. Select either ICC or
VCC.
53
5.
When finished, click on the OK button to save changes and close the
dialog box, or click on the Cancel button to discard changes and close
the dialog box.
Server Messages
Info Reference
This is an integer that uniquely identifies the information message object
within the given scope and must reference a previously defined Local Control
Center Message. It triggers the processing of the message by the receiving
system because it is found in the first variable of a Block 4 message. For
example, if InfoReference=29, the first variable in the report,
Info_Mess_Header, would contain number 29 as the first component of the
InfoBuffHeader.
Scope
to the Local Control Center. ICC indicates that the scope of the device is
Control Center.
Map Info
Client Data Values

Show Only Unassigned Data Values
This is option allows the user to display assigned Data Values or unassigned
Data Values (those not assigned to Data Set Transfer Sets).
Name
This is a unique text string identifying the name of the data value. Each names
is up to 32 characters in length consisting of alphanumeric characters (az,
AZ, and 09), underscore (_) or dollar sign ($). The first
character must be a letter.
54
Scope
VCC if the scope of the data value is global to the remote control center. ICC
if the scope of the data value is limited to the domain designated for use by
the local control center.
Data Type
This is the type of the data value. The following is a list of valid types:
State
StateQ
StateQTimeTag
StateExtended
StateSupplement
StateSupplementQ
Discrete
DiscreteQ
DiscreteQTimeTag
DiscreteExtended
Real
RealQ
RealQTimeTag
RealExtended
Read Only
If set to Yes, this indicates that the TASE.2 client cannot modify the data
value.
Map Info
Description
This is an optional field used to enter a description for the data value. The
55
Add a Data Value

This dialog box is used to add a data value for the Remote Control Center. To
access this box:
1.
Click on the appropriate Data Values node in the navigation tree of the left
pane. Note: Server data values are not added; they are selected from the
list of Local Control Center data values.
2.
Click on the Add button in the right pane to bring up the Add Data Value
dialog box.
3.
4.
Click on the Insert button to add the data value. The dialog box will
remain open, allowing you to add other data values.
5.
When finished, click on the OK button to save all added data values and
data values and close the dialog box.
6.
box.
New
This form includes newly discovered DataValues. When DataValues are
found in this form, the user may manually accept or exclude the new points.
The OK button must pressed before DataValues transition to the DataValues
form when accepted or the Excluded form if excluded
Missing
DataValues appearing in this form are present in the Clients BilateralTable
but not in the Servers BilateralTable. Possible reasons for the mismatch
could be case sensitivity or an ICC, VCC scope mismatch between the two
sites. The remote control center may have also temporarily removed the
visibility of the DataValue. The user has the option of deleting the values
permanently from the client BilateralTable. When mismatched problems have
been addressed and new BilateralAgreeements discovered, DataValues may
automatically leave this form.
56
Mistyped
DataValues found in this form have some issue preventing the GetDataValues
service from completing successfully. Two possible reasons that prevent a
DataValue name that is known to the Client from being Read are 1) The client
expects different class (type) of data than the server is returning or 2) The
server is returning a Read DataAccess error instead of a value. The form of
data the client expects as well as the form of data the server is returning are
both listed in this table.
Excluded
DataValues appearing in this form have been manually excluded from the
New Data Values form. They may be left in this form - this means they will be
ignored if found again in the Discovery process or they may be moved to the
DataValues form and used in DataSets etc. The purpose for configuring
DataValue(s) in this form is to identify those DataValues in a Remote Control
Center that are being exposed as part of the BilateralAgreement but the local
control center is not interested in or is not capable of accessing.
Client Devices
Name
This is a unique text string identifying the device. Each names is up to 32
characters in length consisting of alphanumeric characters (az, AZ,
and 09), underscore (_) or dollar sign ($). The first character must
be a letter.
Scope
VCC if the scope of the device is global to the remote control center. ICC if
the scope of the device is limited to the domain designated for use by the local
control center.
Device Type
Valid options are Command, Real, or Discrete.
57
SBO
If set to Yes, this indicates a Select-Before-Operate device.
Check Back ID
This is used for SBO Devices only. This attribute contains a symbolic
description of the physical object being controlled. The data is returned by the
system operating the physical object to the system requesting the operation so
that the system requesting the operation can be assured the proper object has
been selected. The Check Back ID is a 16-bit integer.
Tag Enabled
If set to Yes, this indicates tag permission granted to the local client.
Map Info
Description
This is an optional field used to enter a description for the device. The
Add a Device
This dialog box is used to add a device for the Remote Control Center. To
access this box:
58
1.
Click on the appropriate Devices node in the navigation tree of the left
pane. Note: Server devices are not added; they are selected from the list
of Local Control Center devices.
2.
Click on the Add button in the right pane to bring up the Add Device
dialog box.
3.
4.
Click on the Insert button to add the device. The dialog box will remain
open, allowing you to add other devices.
5.
When finished, click on the OK button to save all added devices and
devices and close the dialog box.
6.
box.
Client Messages
Info Reference
This is a unique integer used to identify the information message object within
the given scope. It triggers the processing of the message by the receiving
system because it is found in the first variable of a Block 4 message. For
example, if InfoReference=29, the first variable in the report,
Info_Mess_Header, would contain number 29 as the first component of the
InfoBuffHeader.
Scope
VCC if the scope of the information message is global to the remote control
center. ICC if the scope of the information message is limited to the domain
designated for use by the local control center.
Max Size
This is the maximum number of valid octets (characters) in this message. The
default is 500.
Map Info
Description
This is an optional field used to enter a description for the message. The
Client Data Sets

Transfer Set Name
This is used to specify the MMS Named Variable in the Information Report
that will contain the name of the Transfer Set object that generated the
Transfer Report. Selecting Yes will include special data value
Transfer_Set_Name in the data set.
59
Transfer Set Time Stamp

that will contain the Transfer Set Time Stamp object value that contains the
time the Transfer Report was generated. Selecting Yes will include special
data value Transfer_Set_Time_Stamp in the data set.
DS Condition Detected
that will contain the DSConditions Detected object specifying conditions that
became true, triggering the generation of the Transfer Report. Selecting Yes
will include special data value DS_Conditions_Detected in the data set.
Note: AX-S4 ICCP adds the three above special data values to each data set
by default.
Event Code Detection
that will contain the Event Code Detected object specifying other external
event condition that became true, triggering the generation of the Transfer
Report. Selecting Yes will include special data value Event_Code_Detected
in the data set.
Note: Event_Code_Detected is not used by AX-S4 ICCP.
Description
This is an optional field used to enter a description for the data set. The
View
This button is used to view the contents of a selected data set. The screen
allows viewing all the values associated with a selected Data Set. The Data
Value Name and Data Type are displayed for each. Prev and Next buttons
allow scrolling through the contents of all the Client Data Sets.
Change
This button is used to display assigned data values or unassigned data values
(those not assigned to Data Transfer Sets).
60
How to Add a Block 5 object to a DataSet

When the Remote Control Centers TASE.2 Version is set to 2000-08, a Remote
Control Centers Device Tag and Reason can be included in a DataSet. There are two
ways to add a devices Tag and Reason using the ICCP Configuration Utility:
1.
Statically this means click on the Remote Control Centers Client Data
Sets. Then select a DataSet Name by clicking on the DS name in right
pane. Then click on the Change button. A new form will appear that displays
members of a specific DataSet. Device control points are listed in the left
pane. Expand the Devices in the left pane, then highlight the name of the
device, then click the > button. This moves the device name to the pane on the
right. Click the OK button on the bottom of the form the save the change.
2.
Device Tag and Reason can be added to a DataSet by right clicking on

Client (From Remote) then Auto Assign Variables to DSTS. A form
named Auto Assign Variables to DSTS will appear. Check the check box
in the upper right of the form named Assign Device Tags. Click the OK
button. DataSets and DataSetTransferSets are automatically generated using
this feature. All known Device tags will appear in one of the DataSets. Their
names are viewable from one of the DataSets found in the Client DataSets
form .
Client Data Set Transfer Sets

edit and return the original contents to the field. The Basic tab includes Data
Set, Association, Start Time, RBE, Critical, Interval, Integrity Check, Buffer
Time, and Description. The DS Conditions tab includes Interval Time Out,
Integrity Time Out, Object Change, Operator Request, and External Event.
The All tab includes all the fields plus TLE.
Data Set
This is the name of the data set.
Association
This is the name of the association previously defined in the Associations
form.
61
Start Time
This is the time value for the TASE.2 server to begin Condition Monitoring. If
Start Time is 0, then the TASE.2 server will assume it to be its current time
and will begin Condition Monitoring immediately. The default is 0.
RBE
This is a Boolean flag controlling the Report By Exception mechanism. The
default, Yes, implies that the changed objects are reported.
Critical
This is a Boolean flag controlling the type of Transfer Report. A setting of
Yes means that the Transfer Report is critical and an acknowledgement from
the TASE.2 client back to the TASE.2 server is expected. The default is No
no acknowledgement is sent.
Interval
This is the time interval between Data Set Transfer reports. The Interval starts
when the Start Time occurs. If RBE is set to No, then the current state of all
objects in the data set are reported when the Interval expires. If RBE is set to
Yes, then the current state of only the changed objects in the data set are
reported when the Interval expires. If multiple changes occur to the same
object during the Interval, then only the final value is reported. The default is
10.
Integrity Check
This is the time value for integrity check when IntegrityTimeOut and RBE
conditions are used. The default is 30.
Buffer Time
This is the time interval for buffering the ObjectChange condition before
reporting to the TASE.2 client. The Buffer Time starts when the first
ObjectChange condition occurs. If RBE is false, then the current states of all
objects in the Data Set are reported when the Buffer Time expires. If RBE is
true, then the current state of only the changed objects in the Data Set are
reported when the Buffer Time expires. If the Buffer Time is zero, then a
report is generated for each change. If multiple changes occur to the same
object during the Buffer Time, then only the final value is reported. The
default is 2.
Note: A Buffer Time of 0 can cause AX-S4 ICCP to be flooded with Data Set
Transfer Reports and can affect overall network performance.
62
Description
This is an optional field used to enter a description for the data set. The
DS Conditions
Interval Time Out
This indicates whether or not the TASE.2 server should send a report when
the Interval time arrives. The default is No.
Integrity Time Out
This indicates whether or not the TASE.2 server should send a report of the
entire Data Set when the Integrity Check time interval expires. This only
applies when RBE is TRUE. The default is Yes.
Object Change
any object in the Data Set changes. Possible changes include a change of
value, status, or quality flags. The default is Yes.
Operator Request
This indicates whether or not the TASE.2 server should send a report when an
operator at the TASE.2 server control center requests it. The default is No.
External Event
any other external event condition that is not described in the other conditions
becomes true. The default is No.
TLE
This is the time value for Time Limit for Execution (in seconds). This is a
time that is primarily relevant to the TASE.2 server. It is the time over which
the TASE.2 server has to send the Data Set Transfer Report to the TASE.2
client. If the TASE.2 server anticipates that it cannot send the Data Set
Transfer Report to the TASE.2 client within the TLE time, then it shall not
generate the report, and shall discard the data. The default is 60.
63
Data Value Discovery

AX-S4 ICCP provides the ability to discover Data Values
present in a Remote Control Center (Client). The primary
features implemented are the ability to:
1. Validate Existing Configuration
2.
a.
Detect Data Values that are missing or mistyped in

the Remote Control Center.
b.
Remove misconfigured Data Values from

DataSets.
c.
Mark misconfigured Data Values in the

configuration database for review by the user.
Detect New Data Values

a.
Detect Data Values in the Remote Control Center

that are currently not configured.
b.
Add newly detected Data Values to the AX-S4

ICCP configuration database for acceptance by the
user.
c.
Add newly detected Data Values to the runtime

configuration, making them immendiately
available.
This option allows configuring the AX-S4 ICCP Discovery subsystem. This
highly configurable feature provides significant assistance in the area of Client
Data Values (Data Values present in a Remote Control Center).
Enable Client Data Value Discovery
This check box is used to enable/disable the overall Discovery subsystem,
regardless of other Discovery configuration settings. This means that this box
must be checked in order to use any of the Discovery features. Note that most
systems will benefit from enabling at least some of the Discovery features.
General - Association
Indicates the Association on which the Data Value Discovery is to be
performed. There is at most one single association per Remote Control Center
that is used for Discovery. The selected association mode must be either Client
or Client/Server.
64
Execute
This option tells AX-S4 ICCP when it is to perform Discovery. Note that
regardless of this option setting, the user can always initiate the Discovery
process manually by writing an OPC item. Each Remote Control Center gains
a Discover attribute through the OPC interface when the check box Enable
Client Value Discovery is checked.
For example, if the current Local Control Center had a Remote Control
Center named UtilitySiteB and the Discovery attribute for this RCC was
enabled, the OPC application could write a 1 to the following OPC item
string to discover new Data Values UtilitySiteB:Discover.
Options are:
User Initiated: Discovery takes place only when the user initiates it using an
OPC control item.
First Connection: Discovery is performed the first time a connection is
established to the Remote Control Center after AX-S4 ICCP starts, or after a
configuration reload. Subsequent stops and restarts of the link will not cause
Discovery to take place.
Every Connection: Discovery is performed every time a connection is
established. This option will always keep the Local Control Center up-to-date
with the server Bilateral Table changes being made and loaded into the
Remote Control Center. Please note that selecting this setting can add to
association startup time and CPU Utilization and should be selected
carefully.
Automatically Accept Database Changes:
The Discovery subsystem can optionally change the configuration database
it can write new Data Values to the configuration database, and mark
misconfigured Data Values. By default, all database changes are made
available for user review, but do not become a part of the active configuration
until accepted by the user.
If this option is checked, the database changes will be accepted automatically
and will become part of the active configuration without user intervention.
Please note that removing the user from the process is typically not desirable
please consider the implication carefully before enabling this option.
65
Create XML File for Remote Data Values:

If this option is checked, IccpCfg will create an importable
XML file for the Data Values. When the Discovery has
completed, a message will appear in the standard log of
AX-S4 ICCP (axs4iccp.log) stated where the XML file was
written to:
Example: XML Update for Remote 'TGMPI1_1
complete. (See C:\Program files\SISCO\
axs4iccp\rem_TGMPI1_1.xml)
Configured Client Data Values - Validate Configured Data Values
AX-S4 ICCP can validate the presence (and optionally) the type of all
configured Data Values. This check box is used to enable/disable this feature,
regardless of other settings for Configured Data Value Validation.
Remove Mismatches from Data Sets
If this option is checked, AX-S4 ICCP will remove misconfigured (missing or
mistyped) Data Values from DataSets. In general, ICCP servers will not allow
creation of a DataSet containing an invalid Data Value. This option can be
used to help ensure that DataSets can be created and data transfer can take
place.
Correct Mismatches in Databases:
If this option is checked, AX-S4 ICCP will mark missing and mistyped Data
Values in the configuration database. The user can then use the IccpCfg Utility
to examine the configuration mismatches and accept or reject the proposed
changes.
Data Type Validation
Options are:
None: No validation is done.
Normal: With this recommended setting, AX-S4 ICCP will use the MMS
Read service to validate the types. This option is fast but cannot distinguish
between Data Value types of StateQualityTimestamp and DiscreteQuality.
Detailed: With this alternate setting, AX-S4 ICCP will use the
GetVariableAccessAttributes service to validate the types. This option can
take much longer to execute, but can always accurately determine the types as
configured in the server.
66
New Client Data Values - Discover New Data Values

AX-S4 ICCP can detect Data Values in the Remote Control Center that are not
configured, and add these new Data Values to the configuration database
and/or the active configuration. This check box is used to enable/disable this
feature regardless of other settings for New Client Data Values. If checked,
AX-S4 ICCP will use the MMS GetNameList service to look for new Data
Values.
Add to Active Configuration
If this option is checked, the newly discovered Client Data Values (and their
associated OPC items) will be added to the runtime configuration. An OPC
Client will be able to browse newly discovered Data Values after the discovery
process is complete. If this option is checked, the Add to Database option
must also be checked.
Add to Database
If this option is checked, the newly discovered Client Data Values will be
added to the AX-S4 ICCP configuration database. The user can then use the
IccpCfg Utility to examine the new Data Values and accept or reject the
proposed changes.
Derived Types Using
Options are: Detailed: With this recommended setting, AX-S4 ICCP will use
the MMS GetVariableAccessAttributes service to determine types for newly
discovered variables.
Quick: With this alternate setting, AX-S4 ICCP will use the MMS Read
service to determine types for newly discovered variables. This setting has the
advantage of being very fast and is more tolerant of non-conformant
implementations. However it is not possible to distinguish between Data
Value types StateQualityTimestamp and DiscreteQuality based on data, so
AX-S4 ICCP will assume DiscreteQuality. This means that the user must
review all newly discovered Data Values and verify that the types are
correct.
Auto DSTS Parameters

This option allows the user to configure the AX-S4 ICCP Auto-DSTS feature.
This feature allows AX-S4 ICCP to automatically assign remote Data Values
into DataSets and create DataSetTransferSets. all at runtime and without
additional configuration.
Note that using this feature gives up some control, but does ensure that all
Data Values are present in DataSets. This is especially useful in systems where
the Data Value set is not static.
67
Enable Auto DataSetTransferSet Creation

If this box is checked, AX-S4 ICCP will automatically assign remote Data
Values into DataSets and create DataSetTransferSets. If this box is not
checked, the user elects to forgo automatically assigning remote Data Values
and only sets parameters for later assignment.
Association
This is the association over which the DataSetTransferSets are to be received.
Assign Data Values by Data Type
If this box is checked one of three options can be selected:
Real: Assigns Real, RealQ, RealQTimeTag and RealExtended Data Values
into DataSets and creates DataSetTransferSets.
Discrete: Assigns Discrete, DiscreteQ, DiscreteQItemTag, and
DiscreteExtended Data Values into DataSets and creates DataSetTransferSets.
State: Assigns State, StateQ, StateQTimeTag and StateExtended Data Values
into DataSets and creates DataSetTransferSets.
DataSet Parameters
Depending on the data type, the following parameters are displayed, but
possible defaults may be different.
Max DSTS PDU Size
Indicates the maximum MMS message size. Note this value is
configured prior to the TASE.2 association being established and
should come from BilateralAgreement with the Remote site.
However, it is possible to misconfigure this field with a higher or
lower number than the value actually negotiated when the association
takes place.
Conservative DS Data Size Calculation
If checked, Data Sets with less Data Values will be created for the
same MMS message size. The size calculation has to do with the
transfer syntax used to send MMS messages produced by long form
length and indefinite length ASN.1 encodings.
68
Limit Data Values in DataSets

If checked, the maximum number of Data Values included in a Data
Set may be selected. If not checked, the maximum number of Data
Values that will fit into a Data Set per the size calculation algorithm
will be used.
Max DVs per Data Set
This option is only available, if Limit Data Values in Data Sets is
checked. It indicates the maximum number of Data Values per Data
Set that will be used.
Special Variables
All TASE.2 servers have mandatory support for the following special
variables. Because AX-S4 ICCP offers Data Value attributes based on server
support for the special variables it is not possible to unselect these variables
from being added to DataSets.
Transfer Set Name
If checked, it is used to specify the MMS Named Variable
Transfer_Set_Name in the Information Report. The Transfer Set
Name contains the name of the Transfer Set Object that generated the
Transfer Report. Transfer Set Name is required when the ICCPCFG
Utility is in AX-S4 ICCP Configuration Mode.
Transfer_Set_Time_Stamp in the Information Report. The Transfer
Set Time Stamp object value contains the GMTBasedSeconds time
the Transfer Report was generated by the TASE.2 server. AX-S4
ICCP requires The Transfer Set Time Stamp is required when the
IccpCfg Utility is in AX-S4 ICCP Configuration Mode.
DS Conditions Detected
DSConditions_Detected in the Information Report. The DS
Conditions Detected object specifies the conditions that became true,
leading to the generation of the Transfer Report. DS Conditions
Detected is required when the IccpCfg Utility is in AX-S4 ICCP
Configuration Mode.
69
Event Code Detected

Event_Code_Detected in the Information Report that will contain the
Event Code Detected object specifying other external event
conditions that trigger the generation of the Transfer Report.
Transfer Set Parameters Start Time
Indicates the start time for the TASE.2 server to begin Condition Monitoring.
If Start Time is 0, then the TASE.2 server will assume it to be its current time
and will begin Condition Monitoring immediately. Default is 0.
RBE
If checked, the Report By Exception mechanism will be
implemented.
Critical
If checked, the Transfer Report is critical, and an acknowledgement
from the TASE.2 Client back to the TASE.2 Server is expected.
DS Conditions Interval Time Out
If checked, indicates that the TASE.2 Server should send a report
when the Interval Time arrives.
Integrity Time Out
If checked, indicates that the TASE.2 Server should send a report of
the entire Data Set when the Integrity Check Time interval expires
only applies when RBE is enabled.
Object Change
If checked, indicates whether the TASE.2 Server should send a report
only applies when RBE is enabled.
70
Operator Request
If checked, indicates whether the TASE.2 Server should send a report
when an operator at the TASE.2 server control center requests it.
Note: It is possible to configure AX-S4 ICCP to request this DS
Conditions however AX-S4 ICCP will only process the parameter.
No current operations are available in the TASE.2 spec to allow a
client to request a transfer set.
External Event
If checked, requests for TransferSet to be sent on an external event
may not be supported on all servers.
Interval
Allows entering the time interval between TASE.2 server reports.
The Interval starts when the Start Time occurs. If RBE is NOT
checked, then the current state of ALL objects in the DataSet are
reported when the Interval expires. If RBE is checked, then the
current state of ONLY THE CHANGED objects in the data set are
reported when the interval expires. If multiple changes occur to the
same object during the Interval, then only the final value is reported.
Default is 10 seconds.
Integrity Check
May enter a time value for integrity when Integrity TimeOut and
RBE conditions are used. Default is 30 seconds.
Buffer Time
May enter the time interval for buffering the ObjectChange condition
before reporting to the TASE.2 Client. The Buffer Time starts when
the first ObjectChange condition occurs. If RBE is NOT checked,
then the current states of ALL objects in the DataSet are reported
when the Buffer Time expires. If RBE is checked, then the current
state of ONLY THE CHANGED objects in the DataSet are reported
when the Buffer Time expires. If Buffer Time is 0, then a report is
generated for each change. If multiple changes occur to the same
object during the Buffer Time, then only the final value is reported.
Default is 2 seconds.
71
TLE
May enter a time value for Time Limit for Execution. This is a time
that is primarily relevant to the TASE.2 Server. It is the time over
which the TASE.2 Server has to send the DataSet Transfer Report to
the TASE.2 Client. If the TASE.2 Server anticipates that it cannot
send the DSTS to the TASE.2 Client within the TLE time, then it will
not generate the report and will discard the data. The default is 60
seconds.
72
Chapter 6: Remote Control Center Identifcation and Association Matching
Chapter 5
Building Applications using

OPC
OPC General Concepts
AX-S4 ICCP, with its OPC interface can provide applications with easy
access to real-time data using a standard interface. OPC, a standard developed
by the OPC Foundation for interfacing Windows-based applications to device
networks, is based upon Microsofts COM/DCOM technology for
Windows.
With AX-S4 ICCP supporting OPC and ICCP connectivity can be provided to
any OPC enabled application without custom programming. With OPC, AXS4 ICCP is the only interface needed to retrieve data from any number of
remote control centers. It will make possible communication between
Windows applications and ICCP control centers as well as other applications
over ICCP-based Ethernet networks.
OPC Servers
When AX-S4 ICCP is installed, it registers the following OPC Server:
1.
SISCO.AXS4ICCP.3. This provides the OPC Custom Interface (the

preferred interface for use by HMI packages). The OPCDAAuto.dll is
installed to allow Visual Basic application to access registered OPC
Servers.
OPC Item Strings

The AX-S4 ICCP OPC interface supports browsing by OPC clients. Using the
browsing features is the simplest way to create OPC Groups and Items. If the
OPC Client software does not support browsing, the item strings must be
constructed manually. The following discussion should help in determining
the syntax and required content of the OPC item strings.
73
General OPC Item Strings
AddRemoteVCC
74
AddRemoteVCC is a VT_BSTR (string). Write the

name of a new remote control center to load the
configuration data from the data base.
LocalControlCenterName
Allows displaying the name of the current

local control center.
OPC Client Count
Allows displaying the current number of

OPC Clients attached to AX-S4 ICCP.
The ICCP Configuration Utility and the
ICCP Monitor are OPC clients.
SaveCurrentSettings
SaveCurrentSettings is a VT_BOOL.
Write VARIANT_TRUE to save all
window sizes and locations to the registry.
Local and Remote Item Strings

All AX-S4 ICCP objects are either a Local Server object or a Remote object.
The Local Server objects are further classified as Data Values, Local Status
Information, Information Messages, or Devices. The Remote objects are
Links, Data Values, Transfer Sets, Information Messages, or Devices. The
general form of an OPC Item String for a Local Server object is:
LocalCCName:ObjectType~ObjectName.Attribute
The general form of an OPC Item String for a Remote object is:
RemoteCCName:ObjectType~ObjectName.Attribute
The LocalCCName component is the name of the local control center. The
RemoteCCName component is the name of the remote control center
providing the data.
The ObjectType can be DataValue, InfoMsg, DeviceSelect, DeviceOperate,
DeviceTag, DeviceGetTag, or DeviceSetTag. The Local Control Center has
an additional ObjectType (LocalStatus). The Remote Control Center has
additional ObjectTypes (Link and TransferSet).
The Object name is the configured name of the object in the case of data
values, links, and devices. For information messages the object name is
Ref# followed by the configured reference number. For Transfer Sets, the
object name is the Data Set name associated with the transfer set. LocalStatus
object names are predefined and listed below.
Many different Attributes are possible depending on the ObjectType and the
type of the object. Data Values that are of type RealQ have different attributes
than Data Values of type RealExtended. Remote Data Values that are part of
an active Data Set Transfer Set have additional attributes pertaining to the
transfer set. Device attributes vary depending on the device operation.
Different attributes are required to select a device than to operate one. For
Information Messages and Devices, the attributes for the ICCP Server are
different than the attributes available to the ICCP Client. That is, the attributes
differ for local objects and remote objects.
75
The following sample item strings define the available attributes.

Item String
Type
Value
R/W
lccName:LocalStatus~DataSyncStatus
VT_BSTR
Read
Only
lccName:LocalStatus~GetIccpConfiguration
VT_BOOL
Active
Inactive
Mismatch
Not
Enabled
True/False
rccName:DataSyncStatus
VT_BSTR
Read
Only
rccName:GetIccpConfiguration
VT_BOOL
Active
Inactive
Mismatch
Not
Enabled
True/False
Read
Write
Read
Write
Quality Flags
If enabled, the AX-S4 ICCP server will automatically handle the quality flags
associated with a local data value each time the value is written by an OPC
Client. At startup the quality flags are set to:
Validity = INVALID
CurrentSource = configured normal source
NormalValue = NORMAL
TimeStampQuality = VALID if Auto-TimeStamp is enabled
When an OPC Client writes the Value attribute of a data value, the quality
flags are set:
Validity = VALID
NormalValue = NORMAL If the Value written is within configured
range, else ABNORMAL.
76
ICCP to OPC Quality Mapping

The OPC Quality of remote data values can optionally be based on ICCP
Client Data Value quality flags.
The following registry value
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SISCO
\AX-S4 ICCP\CurrentVersion\AXS4ICCP\UseLegacyQualityMappings
must be set to 1 in order to use the mappings described in the table below.
The UseLegacyQualityMappings default is 1.
Use the ICCP Configuration Utility OPC parameters form to set the ICCP to
OPC Quality Mapping. This value is logically ANDed with the DataFlag
item to create a mapping value that is used to determine the OPC quality for
the item as follows:
Quality
Mask
0x00
0xc0
0x54
0xd8
0x40
0xd8
0x40
0x40
0x08
New
OPC
Quality
BAD
GOOD no
reason
UNCERTAIN
eng. units
exceeded
GOOD with
local override
UNCERTAIN
No reason
GOOD with
LocalOverride
UNCERTAIN
No reason
UNCERTAIN
No Reason
BAD not
connected
Old
OPC
Quality
BAD
GOOD
ICCP
Validity
Any
VALID = 0
ICCP
Current
Source
Any
Any
ICCP
Normal
Value
Any
Normal = 0
ICCP
Timestam
p Quality
Any
Valid = 0
GOOD
VALID = 0
Any
Abnormal =
1
Valid = 0
GOOD
VALID = 0
Not (TELE
Normal = 0
Valid = 0
Invalid =
1
Valid = 0
METERED=0)
GOOD
VALID = 0
Any
Any
GOOD
HELD = 1
Any
Any
GOOD
HELD = 1
Any
Any
GOOD
SUSPECT =
2
NOT VALID
=3
Any
Any
Invalid =
1
Any
Any
Any
Any
GOOD
ICCP State Polarity

ICCP State bits are mapped to OPC Boolean where 1 is OFF and 2 is ON per tables in
clause 8.1 of IEC 60870-6-802. There is a registry parameter called
ICCPStatePolaritySwitch controls the polarity of the mapping globally within AX-S4
ICCP as follows. The default is 0.
77
ICCPStatePolarity = 0
When the OPC clients writes a the State value of a Local Data Value as an OPC
Boolean, the Boolean value will be transformed as follows:
OPC Value
FALSE
TRUE
ICCP State Value

1
2
An OPC Client reading a State value of a Remote Data Value as an OPC Boolean will
see the following OPC values depending on the value of the ICCP state variable:
ICCP State Value
0
1
2
3
OPC Value
Last Known
FALSE
TRUE
Last Known
OPC Quality
Uncertain
OPC_QUALITY_EGU_EXCEEDED
OPC_LIMIT_LOW
Good
Good
Uncertain
OPC_LIMIT_HIGH
ICCPStatePolarity = 1
When the OPC clients writes a the State value of a Local Data Value as an OPC
Boolean the Boolean value will be transformed as follows:
OPC Value
FALSE
TRUE
ICCP State Value

2
1
An OPC Client reading a State value of a Remote Data Value as an OPC Boolean will
see the following OPC values depending on the value of the ICCP state variable:
ICCP State Value
3
2
1
0
78
OPC Value
Last Known
FALSE
TRUE
Last Known
OPC Quality
Uncertain
OPC_LIMIT_LOW
Good
Good
Uncertain
OPC_LIMIT_HIGH
AX-S4 ICCP Redundancy

The following item strings are available only when redundancy support is enabled. See
Chapter 7: AX-S4 ICCP Redundancy System on page 99 for more information.
Redundancy:CurrentMode
The current mode of the redundant node.

Possible Values: Active, Standby,
ActiveLocked, StandbyLocked, and
Startup
Data Type: VT_BSTR
Access: Read Only
Redundancy:Status
The status of the RPL connection.

Possible Values: Connected and Not
Connected
Data Type: VT_BSTR
Access: Read Only
Redundancy:TotalICCPLinks
The number of ICCP links for all

configured remote control centers.
Data Type: VT_I4
Access: Read Only
Redundancy:ActiveICCPLinks
The number of ICCP links with an active

state.
Data Type: VT_I4
Access: Read Only
Redundancy:DataSyncRate
The number of data items sent to the

Standby node per second.
Data Type: VT_I4
Access: Read Only
79
Redundancy:HeartbeatTransmitPeriod
The frequency of heartbeat

message sent to the partner node
in milliseconds.
Data Type: VT_I4
Access: Read/Write
Redundancy:HeartbeatHighWaterRx
The longest time between

received heartbeat messages in
milliseconds.
Data Type: VT_I4
Access: Read/Write
Redundancy:LinkConnectTimeoutEnable
State of the Association (Link)

Connect Timeout option.
Data Type: VT_BOOL
Access: Read/Write
Redundancy:LinkConnectTimeout
The number of milliseconds that

the active node is given to
establish at least one ICCP Link.
Data Type: VT_I4
Access: Read/Write
Redundancy:ModeSelect
Allows manual mode selection. The

Default option will set the Redundant
Primary node as the active node and the
Redundant Secondary node as the
standby node. The Forced options will
perform the switchover and issue a
ModeLock request.
Possible Values: Active, Standby, Force
Active, Force Standby, and Default
Data Type: VT_BSTR
Access: Read/Write
80
Redundancy:ModeLock
Enable/Disable automatic mode switches.

Possible Values: Lock and Unlock
Data Type: VT_BSTR
Access: Read/Write
Local Server Data Values

TestLocal:DataValue~DVName.Value
TestLocal:DataValue~DVName.TimeStamp
TestLocal:DataValue~DVName.COV
TestLocal:DataValue~DVName.State
TestLocal:DataValue~DVName.Quality.CurrentSource
TestLocal:DataValue~DVName.Quality.NormalValue
TestLocal:DataValue~DVName.Quality.Validity
TestLocal:DataValue~DVName.Quality.TimeStamp
81
The quality components can be passed to OPC Clients as short integers or

strings. They are defined as follows:
Attribute
Value
CurrentSource
NormalValue
Validity
TELEMETERED
CALCULATED
ENTERED
ESTIMATED
NORMAL
ABNORMAL
VALID
HELD
SUSPECT
NOTVALID
Local Server Messages

TestLocal:InfoMsg~Ref#1.LocalRef
TestLocal:InfoMsg~Ref#1.Message
TestLocal:InfoMsg~Ref#1.MessageID
TestLocal:InfoMsg~Ref#1.RemoveVCC
TestLocal:InfoMsg~Ref#1.SendMessage
Local Server Devices

TestLocal:DeviceSelect~DevName.Indication
TestLocal:DeviceSelect~DevName.RemoteVCC
TestLocal:DeviceSelect~DevName. CheckBackID
TestLocal:DeviceSelect~DevName.Status
TestLocal:DeviceSelect~DevName.SendResponse
TestLocal:DeviceOperate~DevName.Indication
TestLocal:DeviceOperate~DevName.RemoteVCC
82
String
TestLocal:DeviceOperate~DevName.Value
TestLocal:DeviceOperate~DevName.Status
TestLocal:DeviceOperate~DevName.SendResponse
TestLocal:DeviceTag~DevName.Reason
TestLocal:DeviceTag~DevName.TagVaue
TestLocal:DeviceTag~DevName.RemoteVCC
Local Server Status Information

TestLocal:LocalStatus~AXS4DataSetTranRptRecd
TestLocal:LocalStatus~AXS4DataSetTranRptSent
TestLocal:LocalStatus~AXS4DeviceGetTagInd
TestLocal:LocalStatus~AXS4DeviceGetTagReq
TestLocal:LocalStatus~AXS4DeviceOperateInd
TestLocal:LocalStatus~AXS4DeviceOperateReq
TestLocal:LocalStatus~AXS4DeviceSelectInd
TestLocal:LocalStatus~AXS4DeviceSelectReq
TestLocal:LocalStatus~AXS4DeviceSetTagInd
TestLocal:LocalStatus~AXS4DeviceSetTagReq
TestLocal:LocalStatus~AXS4InfoMessagesRecd
TestLocal:LocalStatus~AXS4InfoMessagesSent
TestLocal:LocalStatus~AXS4NumErrors
TestLocal:LocalStatus~AXS4ReadDataValueInd
TestLocal:LocalStatus~AXS4ReadDataValueReq
TestLocal:LocalStatus~AXS4WriteDataValueInd
TestLocal:LocalStatus~AXS4WriteDataValueReq
TestLocal:LocalStatus~CfgFileName
TestLocal:LocalStatus~CfgVCCNames
TestLocal:LocalStatus~Error
TestLocal:LocalStatus~NumActiveLinks
TestLocal:LocalStatus~NumActiveVCC
TestLocal:LocalStatus~NumCfgLinks
TestLocal:LocalStatus~NumCfgVCC
83
Remote Server General Information

TestRemote:AXS4DataSetTranRptRecd
TestRemote:AXS4DataSetTranRptSent
TestRemote:AXS4DeviceGetTagInd
TestRemote:AXS4DeviceGetTagReq
TestRemote:AXS4DeviceOperateInd
TestRemote:AXS4DeviceOperateReq
TestRemote:AXS4DeviceSelectInd
TestRemote:AXS4DeviceSelectReq
TestRemote:AXS4DeviceSetTagInd
TestRemote:AXS4DeviceSetTagReq
TestRemote:AXS4InfoMessagesRecd
TestRemote:AXS4InfoMessagesSent
TestRemote:AXS4NumErrors
TestRemote:AXS4ReadDataValueInd
TestRemote:AXS4ReadDataValueReq
TestRemote:AXS4WriteDataValueInd
TestRemote:AXS4WriteDataValueReq
TestRemote:Bilateral_TableID
TestRemote:ReloadBLT
TestRemote:Supported_Features
TestRemote:TASE2_Version
Remote Server Link Information

TestRemote:Link~LinkName.AXS4DataSetTranRptRecd
TestRemote:Link~LinkName.AXS4DataSetTranRptSent
TestRemote:Link~LinkName.AXS4DeviceGetTagInd
TestRemote:Link~LinkName.AXS4DeviceGetTagReq
TestRemote:Link~LinkName.AXS4DeviceOperateInd
TestRemote:Link~LinkName.AXS4DeviceOperateReq
TestRemote:Link~LinkName.AXS4DeviceSelectInd
84
TestRemote:Link~LinkName.AXS4DeviceSelectReq
TestRemote:Link~LinkName.AXS4DeviceSetTagInd
TestRemote:Link~LinkName.AXS4DeviceSetTagReq
TestRemote:Link~LinkName.AXS4InfoMessagesRecd
TestRemote:Link~LinkName.AXS4InfoMessagesSent
TestRemote:Link~LinkName.AXS4NumErrors
TestRemote:Link~LinkName.AXS4ReadDataValueInd
TestRemote:Link~LinkName.AXS4ReadDataValueReq
TestRemote:Link~LinkName.AXS4WriteDataValueInd
TestRemote:Link~LinkName.AXS4WriteDataValueReq
TestRemote:Link~LinkName.Enabled
TestRemote:Link~LinkName.State
Remote Server Data Values

TestRemote:DataValue~DVName.Value
TestRemote:DataValue~DVName.TimeStamp
TestRemote:DataValue~DVName.COV
TestRemote:DataValue~DVName.State
TestRemote:DataValue~DVName.Quality.CurrentSource
TestRemote:DataValue~DVName.Quality.NormalValue
TestRemote:DataValue~DVName.Quality.Validity
TestRemote:DataValue~DVName.Quality.TimeStamp
TestRemote:DataValue~DVName.DSConditions_Detected*
TestRemote:DataValue~DVName.Transfer_Set_Time_Stamp*
85
TestRemote:DataValue~DVName.DataFlags**
Data Type: VT_I4
Data Format:
Bit 0 = Quality.TimeStamp
Bit 1 = Quality.NormalValue
Bit 2 = Quality.CurrentSource Lo
Bit 3 = Quality.CurrentSource Hi
Bit 4 = Quality.Validity Lo
Bit 5 = Quality.Validity Hi
Bit 6 through Bit 25 = Unused
Bit 26 = DSConditions.OtherExternalEvent***
Bit 27 = DSConditions.IntegrityTimeOut***
Bit 28 = DSConditions.OperatorRequest***
Bit 29 = DSConditions.ObjectChange***
Bit 30 = DSConditions.IntervalTimeOut***
Bit 31 = unused
*Attribute only available for Data Values involved in active transfer sets.
**Contains the ICCP Quality data and optionally the DSConditions Detected
from the Data Set Transfer Report.
***If DSConditions are present.
Remote Server Transfer Sets

TestRemote:TransferSet~DataSetName.Enabled
Remote Server Information Messages

TestRemote:InfoMsg~Ref#1001.LocalRef
TestRemote:InfoMsg~Ref#1001.Message
TestRemote:InfoMsg~Ref#1001.MessageID
Remote Server Devices

TestRemote:DeviceSelect~DevName.SendRequest
TestRemote:DeviceSelect~DevName.CheckBackID
TestRemote:DeviceSelect~DevName.Status
TestRemote:DeviceOperate~DevName.Value
TestRemote:DeviceOperate~DevName.SendRequest
86
TestRemote:DeviceOperate~DevName.Status
TestRemote:DeviceGetTag~DevName.SendRequest
TestRemote:DeviceGetTag~DevName.Reason
TestRemote:DeviceGetTag~DevName.TagValue
TestRemote:DeviceGetTag~DevName.Status
TestRemote:DeviceSetTag~DevName.Reason
TestRemote:DeviceSetTag~DevName.TagValue
TestRemote:DeviceSetTag~DevName.SendRequest
TestRemote:DeviceSetTag~DevName.Status
Add a Remote Control Center Configuration

This item string is not associated with a Local or Remote control center. It is
used to add a Remote Control Center configuration. The syntax is as follows:
AddRemoteVCC
Writing this item string with the name of the new Remote Control Center
causes the default configuration file (XML file or DataBase) to be reread and
parsed. The new Remote Control Center and its objects are added to AX-S4
ICCP. Any errors associated with this operation appear in the item string
LocalName:LocalStatus~Error.
Reloading a Remote Control Center Bilateral

Table
Each Remote Control Center can have its object set reloaded while AXS4ICCP is running by writing the item string RemoteName:ReloadBLT to the
boolean value (e.g., the number 1). Writing this item string with the value of
TRUE causes the default configuration file (XML file or DataBase) to be
reread and parsed. Any change to the object set associated with the Remote
Control Center is reflected in AX-S4 ICCP.
87
Information Message Handling

To send a message to a remote ICCP client the OPC client must include the
LocalRef, Message, MessageID, RemoteVCC, and SendMessage attributes of
a Local Server Message in the OPC Group. The OPC Client must write values
to all the attributes, writing the SendMessage attribute last. The RemoteVCC
field is the name of the Remote Control Center to which to send the message.
Set the SendMessage attribute to 1 to send the message.
To receive an information message from a remote ICCP server, the OPC
client application must monitor the LocalRef, Message, and MessageID
attributes of a Remote Control Center Info Message. The attributes are
updated as data is received from the remote server.
Device Handling
To handle incoming Select Device requests the OPC Client application must
monitor the Indication, RemoteVCC, CheckBackID, Status, and
SendResponse attributes of a LocalControlCenter device. When a Select
Device Request is received from a remote client, the Indication attribute is
changed to 1 and the RemoteVCC attribute is updated with the name of the
remote control center requesting to select the device. The OPC Client
application must respond by writing the CheckBackID, Status, and
SendResponse attributes.
Valid Status values are:
0 = Success
1 = Device Does Not Exist
2 = Access Denied
3 = Device Inoperable
4 = Device Temporarily Unavailable
Set the SendResponse attribute to 1 to send the response.
The AX-S4 ICCP server will automatically respond to a Select request in
certain situations.
88
If the device is already selected, the AX-S4 ICCP server will

automatically respond with Device Temporarily Unavailable.
If no OPC Client is monitoring the SelectDevice and a CheckBackID has

been configured the AX-S4 ICCP Server will automatically respond to
the Select Device request.
If no OPC Client is monitoring the SelectDevice and no CheckBackID is

configured, the AX-S4 ICCP server will respond with Device
Temporarily Unavailable.
If an Operate Device request is not received from the remote client who
selected the device with the time specified in the configuration file for
select device timeout, the AX-S4 ICCP server will clear the device and
enable selecting.
To handle incoming Operate Device requests the OPC Client application must
monitor the Indication, RemoteVCC, Value, Status, and SendResponse
attributes of a LocalControlCenter device. When an Operate Device request is
received from a remote client, the Indication attribute is set to 1, the Value is
set to the value received from the remote client and the RemoteVCC attribute
is set to the name of the remote control center requesting to operate the
device. It is the responsibility of the OPC Client application to set the Status,
as defined above, and write a 1 to the SendResponse attribute. The AX-S4
ICCP server will return a Device Temporarily Unavailable status if the
DeviceOperate is not actively monitored by an OPC Client.
The SetTag and GetTag operations for LocalControlCenter devices are
handled automatically by the AX-S4 ICCP server. To monitor tagging activity
for a local control center device, include the Reason, TagValue, and
RemoteVCC attribute of a DeviceTag object.
Selecting a Remote Device

The OPC Client application must monitor the SendRequest, CheckBackID,
and Status attributes of a RemoteControlCenter DeviceSelect object. Write a
1 to the SendRequest attribute. The Status and CheckBackID returned from
the remote server will be updated upon receipt.
89
Operating a Remote Device

To operate a remote device, the OPC Client application must monitor the
SendRequest, Value and Status attributes of a RemoteControlCenter
DeviceOperate object. Write the Value attribute and set the SendRequest
attribute to 1. The Status returned from the remote server will be updated
upon receipt.
Getting Tag Information from a Remote

Device
To get the tag information from remote device, the OPC client application
must monitor the SendRequest, Reason, TagValue, and Status attributes of a
RemoteControlCenter DeviceGetTag object. Set the SendRequest attribute to
1. The remaining attributes will be updated upon receipt from the remote
server.
Setting Tag Information of a Remote Device

To set the tag information of a remote device, the OPC Client application
must monitor the SendRequest, Reason, TagValue, and Status attributes of a
RemoteControlCenter DeviceSetTag object. Set the Reason, TagValue, and
SendRequest attributes. The Status will be updated with the server response
upon receipt.
AX-S4 ICCP Statistics

AX-S4 ICCP tracks certain ICCP events for the entire local ICCP server, for
each remote and for each link. All statistics are made available to an OPC
Client as Read Only fields. The item strings used to monitor these statistics
are noted above.
To monitor the local server statistics use item strings similar to the following:
TestLocal:LocalStatus~AXS4DataSetTranRptRecd
90
To monitor the statistics for a specific Remote Control Center use item strings
similar to the following:
TestRemote:AXS4DataSetTranRptRecd
To monitor the statistics for a specific Link, use item strings similar to:
TestRemote:Link~LinkName.AXS4DataSetTranRptRecd
The statistic items are defined as:
AXS4DataSetTranRptRecd:
Number of Data Set Transfer Reports

received.
AXS4DataSetTranRptSent:
Number of Data Set Transfer Reports

sent.
AXS4DeviceGetTagInd:
Number of Get Tag requests received.
AXS4DeviceGetTagReq:
Number of Get Tag requests sent.
AXS4DeviceOperateInd:
Number of Operate requests received.
AXS4DeviceOperateReq:
Number of Operate requests sent.
AXS4DeviceSelectInd:
Number of Select requests received.
AXS4DeviceSelectReq:
Number of Select requests sent.
AXS4DeviceSetTagInd:
Number of Set Tag requests received.
AXS4DeviceSetTagReq:
Number of Set Tag requests sent.
AXS4InfoMessagesRecd:
Number of Information Messages

received.
AXS4InfoMessagesSent:
Number of Information Messages sent.
AXS4NumErrors:
Number of ICCP errors
AXS4ReadDataValueInd:
Number of Read Data Value requests

received.
AXS4ReadDataValueReq:
Number of Read Data Value requests

sent.
AXS4WriteDataValueInd:
Number of Write Data Value requests

received.
AXS4WriteDataValueReq:
Number of Write Data Value requests

sent.
The statistics can also be viewed on the AX-S4 ICCP Connection State
window.
91
Local Status Information

AX-S4 ICCP Local Status Information consists of the statistics as mentioned
above and some other items that summarize the state of the local server. All
fields are Read Only. The CfgVCCNames item returns an array of strings
containing the names of all the configured Remote Control Centers. The Error
item returns a string explaining the error that occurred.
Error Handling
Some errors can occur which are not fatal to the ICCP Client or the ICCP
Server. These errors are stored and passed to an OPC Client that is monitoring
the TestLocal:LocalStatus~Error item string. Due to the nature of OPC and
the requirement that an OPC Server only supply updates to an OPC Client at
predefined intervals, the ICCP errors that occur are queued up and passed to
the OPC Client one at a time when the OPC group timer expires. The OPC
time stamp indicates when the error occurred. No intervention is required by
the OPC Client. However, in some cases, configuration changes may correct
the error condition.
The error string passed to the OPC Client has the following form:
remoteName:linkName~domainName/objectName.errorText
The domainName/ is optional.
The following errorText strings may be reported:
92
CreatingDataSetError Unknown variable
CreatingDataSetError No READ permission
CreatingDataSetError Read variable failed
ReadRequestError FAIL
ReadRequestError Bilateral Table mismatch on ASN.1 value and type
Critical NACK Received
Critical Data not arrived
Critical Data Time Out
Unable to STOP Remote*
Unable to Reload configuration*
Unable to ReDefine Remote*
Unable to load configuration**
Supported Features Read Failure Association Denied***
Supported Features Mismatch Association Denied***
ICCP Version Read Failure Association Denied***
Bilateral Table Id Mismatch Association Denied***
* Errors that occur when reloading configuration for a remote. No link name
is present and the object name = ReloadBLT.
**Errors that occur when adding a remote configuration. No link name is
present and the object name = AddRemote.
***Error string does not contain an object name.
Test Applications
The AX-S4 ICCP product CD contains two test applications that will assist in
both learning AX-S4 ICCP and testing your OPC Client application. OPC
Client.exe is a sample OPC Client application that will allow you to connect
to AX-S4 ICCP, create groups, and add and remove items. IccpLiteTest.exe
is a sample ICCP Client/Server. This application is located in
\<ApplicationData>\SISCO\AX-S4 ICCP\ICCPLiteTestApplication. The
details for using this executable are in ICCP LiteTest Sample Program.PDF
in the AXS4ICCP\doc directory.
93
94
Chapter 6
Remote Control Center

Identification and Association
Matching
The AX-S4 ICCP configuration process includes defining Associations, which
are used to enable ICCP connections to be established with RCCs (Remote
Control Centers). The Association configuration includes the local network
address (via Local AR Name) and one or more remote network addresses (via
remote AR Names). Associations can be Calling (AX-S4 ICCP sends the
initiate request) or Called (the Remote Control Center sends the initiate
request). The following applies to Called associations only.
When an initiate indication is received, AX-S4 ICCP uses the received
addressing information to determine with which configured Association the
connection should be matched. The addressing information available for use
in this matching is as follows:
AE Title
AP Title (optional)
AE Qualifier (optional)
AP Invoke ID (optional)
AE Invoke ID (optional)
Presentation Selector (PSEL)
Session Selector (SSEL)
Transport Selector (TSEL)
Network Address (OSI Network Address or IP Address)
95
The ICCP protocol specification (IEC 870-6-503) is not definitive regarding

the addressing elements to be used in identifying a Remote Control Center,
but does indicate that the AE Title is the preferred identifier. However, the
specification also notes that an AE Title is bound to a single Presentation
Address (which includes the Selectors), and so either the Presentation Address
or the AE Title can be used for Remote Control Center identification. This
means that it is within the letter of the specification to not support the use of
AE Titles in addressing.
AX-S4 ICCP Matching Algorithm

Some ICCP implementations and systems make use of Selector based address
differentiation and do not use the AE Title addressing elements. Because of
this, AX-S4 ICCP is designed to recognize this addressing approach and work
correctly in this environment. Meaning that the default settings for AX-S4
ICCP will allow recognition of Remote Control Centers by a combination of
AE Title and the Selectors.
Note that both the local (called) and remote (calling) addresses are used in the
matching algorithm, as described as follows:
96
For Each Configured Remote

{
For Each Configured Association
{
If the Association is: Called, Idle, and Enabled
{
If the Called address matches the Local AR Name
address
{
For Each configured Remote AR Name for the
Association
{
If the Calling address matches the Remote AR
Name
{
If this is the best match so far, the Initiate
Indication is matched to the configured
Association
}
}
}
}
}
}
Matching Criteria
The criteria for declaring that an address matches the configured address (AR
Name) for an Association is specified by a set of control parameters. These
parameters provide support for a variety of address resolution schemes, and
will help ensure accurate and reliable mapping of incoming connections to
configured Associations. Note that these control parameters apply to all
Associations and addresses, and so the requirements for all remotes must be
considered.
The default mapping control parameter values will be appropriate for most
installations, where the set remotes make use of both AE Title and Selector
based addressing. With this configuration, we can summarize the address
mapping as follows:
97
Local Address/AR Name
AE Titles are ignored.
Selectors (PSEL, SSEL, TSEL) must match.
Network Address is ignored.
Remote Address/AR Name
98
AE Title must match
AP Title and AE Qualifier only (Invoke IDs ignored)
All AE Title elements configured at AX-S4 ICCP must be received.
AE elements received but not configured at AX-S4 ICCP are

ignored.
Selectors (PSEL, SSEL, TSEL) must match.
Network Address is ignored.
Chapter 7: AX-S4 ICCP Redundancy System
Chapter 7
AX-S4 ICCP Redundancy

System
The following chapter will describe the functionality and architecture of the
AX-S4 ICCP redundancy system. This system allows two AX-S4 ICCP nodes
to be deployed in redundant configurations, improving system availability.
Redundancy System Features
When an AX-S4 ICCP node is configured as a redundant node, a number

of OPC Items are made visible. These items can be used to monitor and
control the redundancy subsystem. See AX-S4 ICCP OPC Item
Availability on page 103 for item paths and descriptions.
Automatic switchovers can take place due to heartbeat timeout when the
Active node terminates normally, or optionally when the Active node is
unable to establish any active ICCP Links in a configurable period of
time.
Either node can initiate a manual Active/Standby mode switch. This can
be done via the OPC server interface. Redundancy Monitor or any OPC
client application can be used for this purpose.
99
There is no automatic return to the default mode. If the Primary fails and
the Secondary becomes active, the Secondary will then remain Active
regardless of whether the Primary becomes available again. Of course
Redundancy Monitor or another OPC client application can manually
cause the transition back to secondary via the OPC interface.
Both nodes send heartbeat messages to the partner node. These heartbeat
messages contain node state information, which is used as input
information in the switchover control algorithm.
The Active node will optionally send Data Value sync information to the
Standby node. This can consist of local data values or both local and
remote data values, and serves to keep the Standbys data in sync with the
Active.
The redundancy control subsystem supports the AX-S4 ICCP on-line

configuration features. The procedures for performing on-line
reconfiguration are discussed on page 108.
The mode can be locked so that mode switches are disabled. This can be
done via the OPC interface. Redundancy Monitor or any OPC client
application can be used for this purpose.
The AX-S4 ICCP redundancy system is designed to integrate smoothly

with commercially available OPC redundancy brokers.
Redundancy Definitions
Primary Node
One of two nodes in a redundant pair; the role is selected using IccpCfg. The
Primary node is responsible initiating the Redundancy Port Link (RPL)
connection. Otherwise, it is functionally the same as the Secondary. A
Primary can be in Active or Standby mode.
Secondary Node
One of two nodes in a redundant pair; the role is selected using IccpCfg. The
Secondary node listens for RPL connections. Otherwise, it is functionally the
same as the Primary. A Secondary can be in Active or Standby mode.
100
Active Mode
A node in the Active mode has all ICCP associations enabled. The Active
node can establish ICCP associations with remote ICCP nodes and perform
ICCP client and server activities.
Standby Mode
A node in the Standby mode has all ICCP associations disabled. The Standby
node does not communicate with ICCP remotes, but rather monitors the state
of the Active node. In the case of Active node failure (or other conditions),
the Standby node will become Active.
Redundancy Port Link (RPL)

The Redundancy Port Link (RPL) is the communications channel between the
Primary and Secondary. Heartbeat, Data Synchronization and other
redundancy control messages are exchanged via RPL. This link makes use of
a dedicated TCP port.
IccpCfg
This is the AX-S4 ICCP Configuration Utility. This application is used to
configure the redundancy features of AX-S4 ICCP. Note that AX-S4 ICCP
must be restarted for redundancy control changes to take effect.
Redundancy Monitor
This is the AX-S4 ICCP Redundancy Monitor Utility. This application is used
to monitor and control the redundancy features of AX-S4 ICCP. It makes use
of the OPC interface and redundancy control items.
101
Redundant System Block Diagram

The figure below shows the elements of a redundant AX-S4 ICCP system.
OPC Client
Application
OPC Client
Application
Redundancy
Monitor
Redundancy
Monitor
OPC Server Interface
AX-S4 ICCP: Primary Node
AX-S4 ICCP: Secondary Node
ICCP Client/Server
ICCP Links
Enabled when
Primary is
Active
RPL Interface
RPL Interface
RPL Protocol: Heartbeat/Control/Data
ICCP Client/Server
ICCP Links
Enabled when
Secondary is
Active
ICCP Network
ICCP Remote
ICCP Remote
ICCP Remote
Figure 5: Elements of a redundant AX-S4 ICCP system
102
AX-S4 ICCP OPC Item Availability

Redundancy Items
The set of OPC items related to Redundancy are available only when the node
is configured to be either a Redundant Primary or Redundant Secondary.
If the node is Not Redundant, these items will not be available.
Active Node
When a node is in the Active node, all OPC items can be accessed normally
and will have values and qualities as though the node is not part of a
redundant pair.
Standby Node
When a node is in the Standby mode, all OPC items for ICCP Remotes will
have a Bad quality because the node is not receiving the values from the
Remote.
Local OPC items are available and a OPC client can continue to update the
values regardless of the mode. This can be useful in a deployment
configuration with redundant OPC clients, but not for deployment
configurations using an OPC redundancy broker. Deployment configuration
options are discussed on page 104.
Local ICCP Data Value Quality During

Switchover
When a node first switches from Standby to Active the quality and value of
the ICCP Data Values being sourced may bumpas the newly Active node
acquires new values from the OPC Client. That is, if the Standbys copy of the
local data values is not kept up to date, remote nodes may receive data that is
either old or invalid.
This sourced data bump can be minimized by using one of the following
techniques:
1.
Make use of the AX-S4 ICCP redundancy system Data Synchronization

facilities for keeping the Standby data values warm. Select the Local and
Remote or Local mode.
103
2.
Ensure that the OPC Client will attach to the appropriate DataSource and
update the local data values in the Standby node. Note that this option may
not be possible in some redundant system deployment scenarios, such as when
an OPC redundancy broker is used. See the Deployment Options below for
more information.
Remote OPC Item Value Quality During

Switchover
When a node first switches from Standby to Active the quality of remotely
sourced OPC Item values will be BAD. As the newly Active node establishes
associations with remote ICCP nodes and acquires values the quality of these
items will transition to GOOD.
Deployment Options
AX-S4 ICCP can be deployed in a variety of redundant configurations, each with it
benefits and shortcomings. Two common deployment options are discussed below.
104
Deployment Option 1: Integrate With Redundancy Broker

The figure on the following page shows an AX-S4 ICCP redundant system
integrated with an OPC redundancy broker. This configuration allows a single
OPC client application to make use of an enhanced availability ICCP interface
with no additional programming in the OPC client application. The OPC
client is unaware that it is making use of a redundant OPC server.
OPC Client
Application
Redundant OPC
OPC Redundancy Broker

(ORB)
OPC Client Interface
DCOM
ICCPClient/Server
RPL Interface
DCOM
RPL Interface
ICCP Client/Server
Figure 6: AX-S4 ICCP redundant system integrated with an OPC

redundancy broker
105
Deployment Option 2: Redundant OPC Client Applications

Figure on the following page shows an AX-S4 ICCP redundant system
deployed with redundant OPC Client applications. This configuration enables
deployment of two independent OPC Clients using a single set of ICCP
associations. Note that the OPC client applications will need to be aware of
redundant system issues and will likely require additional application logic in
order to interact with an OPC Server that may be in Standby mode. Data
synchronization may or may not be appropriate for these types of deployments
depending on design details.
Local ICCP Value Source
Remote ICCP Value Sink
Remote Values
Received
Local Values
Updated
Internal Interface
OPC Client
Application A
Local Values
Updated
Remote Values
Received
Internal Interface
Control
OPC Client
Application B
OPC Interface
OPC Interface
ICCP Client/Server
RPL Interface
RPL Interface
ICCP Client/Server
Figure 7: AX-S4 ICCP redundant system deployed with redundant OPC Client
applications
106
Redundant AX-S4 ICCP Configuration Issues

Generally the Primary and Secondary nodes will be configured to use
identical ICCP configurations (Local objects, Bilateral tables, etc.). This is
particularly important when using an OPC redundancy broker configuration,
so that the available OPC item set remains consistent. That is, the OPC items
that are in use by the OPC Client should be available in both nodes. If the
available OPC item set is not the same for the Primary and Secondary nodes,
failover situations can result in undesirable OPC client behavior.
AX-S4 ICCP makes use of the IccpCfg for ICCP object configuration as well
as network addressing. The ICCP configuration information is stored in a
database on each AX-S4 ICCP node (IccpCfg.mdb). Network addressing
information is always read from the SISCO stack configuration database
(siscinf3.mdb) and the ICCP configuration and Network addressing are
loosely coupled via AR Names, which means that the ICCP references AR
Names (for ICCP associations) that must be present in the SISCO stack
configuration database. Thus, both nodes can use the same IccpCfg database.
AX-S4 ICCP can be configured to read the configuration directly from the
database or from an XML encoded configuration file, which can exported
from the database using IccpCfg.
Basic AX-S4 ICCP Redundant Configuration

Process
1.
Working at node A with IccpCfg, perform all required configuration

including ICCP objects and network addressing.
2.
Test the configuration on node A.
3.
When ready to bring node B on-line (or up to date), transfer the ICCP
configuration from node A to node B.
If the direct database load option is selected, this will typically mean
transferring the ICCP configuration database (IccpCfg.mdb), or
optionally performing an XML export at node A and an XML import at
node B.
107
If the XML load option is selected, this will mean transferring the XML
configuration file from node A to node B, then importing it.
Both cases entail file transfers from node A to node B. The tools to be
used for accomplishing the required configuration file transfers is outside
the scope of the AX-S4 ICCP Redundancy System.
1.
Working at node B with the updated configuration, verify that all

referenced Local and Remote AR Names are present and correct.
The IccpCfg Association Summary feature will be helpful in
identifying problem areas.
2.
Test the configuration on node B, using the manual switchover

features as appropriate.
If these procedures are used, both the Primary and Secondary node will then
have complete and correct copies of all configuration information. Note that it
is not necessary that the Network configurations match (e.g., addresses), but
that the AR Names are present. This flexibility can be useful in configuring
network redundancy, but care must be taken to ensure that both nodes address
the correct Remotes.
On-Line AX-S4 ICCP Reconfiguration

The basic configuration procedures apply to on-line configuration. The
redundancy subsystem provides the tools for updating both nodes smoothly.
When a node has a configuration change, the partner is notified of the change
and the configurations are compared and the data sync system is updated as
appropriate.
Of course, the issue of OPC Item availability must be considered during the
update process, especially when the OPC redundancy deployment
configuration is being used. In this case, only OPC items that are present in
both node configurations can be relied on in case of a failover. For this
reason, it is advisable to update both nodes to the same ICCP configuration in
a timely manner.
108
Data Synchronization Issues

The data synchronization feature can be used to keep the values of the Local
and Remote ICCP objects up to date in the Standby node. All data changes in
the Active node are sent to the Standby node when the appropriate data
synchronization mode is selected.
The AX-S4 ICCP redundancy subsystem makes use of CRCs over the ICCP
configuration to ensure that data synchronization can take place correctly and
safely. These configuration CRCs are calculated at AX-S4 ICCP startup and
when the configuration is changed on either node. The Local objects and each
Remote have independent configuration CRCs.
When the configuration CRCs are received, data synchronization can take
place only within scopes with matching configuration CRCs. Local and each
Remote are managed separately. This means that local configurations must
match for local data sync and each remote configuration must match for that
remote to be able to perform data synchronization. Within the matching
scopes, the Standby will request initial data from the Active node, and the
Active node will send all changed data to the Standby.
Configuration Synchronization
Installations making use of the AX-S4 ICCP redundancy features typically needed to
have both systems running identical configurations, so that switchovers are relatively
transparent and Data Value synchronization can take place. The table below describes
the configuration elements that AX-S4 ICCP uses, where they are stored, and whether
they will be handled by the initial implementation of the synch system.
Configuration Element
Location
CRC?
Syncd?
Registry
No
No
Registry
Registry
No
No
No
No
Registry
No
No
Registry
No
No
siscinf3.mdb
No
No
AX-S4 ICCP
General (Configuration source, Auto
param, etc.)
Remote Identification parameters
OPC Parameters (Timestamp, quality
handling)
Redundancy (Role, IP addresses,
options)
Logging
Network Addressing
Local AR Names
109
Configuration Element
Remote AR Names
Location
CRC?
Syncd?
siscinf3.mdb
No
No
Registry
No
No
secManCfg.xml
secManCfg.xml
secManCfg.xml
No
No
No
No
No
No
secManCfg.xml
secManCfg.xml
secManCfg.xml
No
No
No
No
No
No
Windows
Certificate Store
Windows
Certificate Store
No
No
No
No
IccpCfg Database
IccpCfg Database
IccpCfg Database
No
No
No
Yes
Yes
Yes
IccpCfg Database
IccpCfg Database
Yes
No
Yes
Yes
IccpCfg Database
Yes
Yes
IccpCfg Database
IccpCfg Database
IccpCfg Database
No
No
No
Yes
Yes
Yes
Stack
Local Host
Security
General
Enable Security
Certificate IDs
SSL Options (Ciphers, rekey control,
etc.)
Local AR Security
Remote AR Security
SNAP parameters
System
Local Certificates
Certificate Revocation Lists
LocalControlCenter
General
MaxDsTs
MaxDataSets
MaxMmsMsgSize
ICCP Objects
Local Data Values: Names
Local Data Values: Type, Normal
Source
Local Devices: Names, SBO, Check
back ID, Taggable
Local Devices: Type
Local Devices: Timeout
Local Messages
110
Remote Control Centers

General
TASE.2 Version
Bilateral Table Name
Bilateral Table Id
Local/Remote Domain Names
Shortest Interval
Supported Blocks
IccpCfg Database
IccpCfg Database
IccpCfg Database
IccpCfg Database
IccpCfg Database
IccpCfg Database
No
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
IccpCfg Database
IccpCfg Database
No
No
Yes
Yes
IccpCfg Database
IccpCfg Database
No
No
Yes
Yes
IccpCfg Database
IccpCfg Database
IccpCfg Database
Yes
No
Yes
Yes
Yes
Yes
IccpCfg Database
IccpCfg Database
IccpCfg Database
IccpCfg Database
IccpCfg Database
IccpCfg Database
IccpCfg Database
IccpCfg Database
No
Yes
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
IccpCfg Database
No
Yes
Associations
Local, Remote AR Names
Association parameters: Role, Retry,
Heartbeat, Timeouts
Service Role
MMS Parameters: Message Size, Req.Ind
Pending
ICCP Objects
Server Data Values: Name, Scope, Type
Server Data Values: Read Only
Server Devices: Name, Scope, Type, Tag
Enable
Server Messages
Client Data Values: Name, Scope, Type
Client Data Values: Read Only
Client Data Sets
Client DSTS
Discovery/Validation Options
Auto-DSTS Options
Client Devices: Name, Scope, Type, SBO,
CheckBack, Tag
Client Messages
111
Compounding the difficulty is the availability of the Discovery feature in AX-S4 ICCP.
When a redundant pair is setup to use automatic discovery of new data values, it is
possible to have the configurations go out of sync without user action, preventing
remote Data Value data synchronization from taking place. This can occur with the
new discovery system when the Update Runtime Configuration == Add New Data
Values or when Update ICCP Configuration Database == Automatically Accept
Updates
In order to keep configurations in sync, administrators currently have to manually
transfer the configuration files from one node to the other via some external means then
manually apply the new configuration to the second system. This typically involves
using the IccpCfg configuration tool to export the configuration at one node and import
at the other.
The AX-S4 ICCP Configuration Synchronization subsystem is designed to assist in
keeping the redundant pair configurations in sync.
Note: Configuration synchronization requires use of a single bilateral table in both
systems.
SISCO recommends two approaches (Policies) for Configuration Synchronization.
While other approaches are possible, the potential for problems is much greater.
SISCO does not support any approaches other than the two recommended Policies.
Policy 1: Administer Approved Configuration Changes
1.
Client Data Value Configuration

Differences between the current set of configured Client Data Values and that
which is exposed by the remote control center will be discovered by AX-S4
ICCP and written into the configuration database for review. This will include
new, deleted, and changed data values.
No changes will be put into effect until the administrator uses IccpCfg to
review and either accept or reject them, then the remote configuration can be
reloaded .
2.
Primary/Secondary node configuration synchronization may be initiated
manually in order to pull (manually force) the configuration from one node to
the other over the RPL connection.
Automatic configuration synchronization is disabled, so that no changes to
configuration are made without administrator action.
112
3.
The following settings should be used on the forms indicated in the table:
Configuration Settings
Discovery Options
Setting
Notes
Enable Discovery
On
Discovery should almost always be enabled, because it is the

mechanism used to perform configured Data Value
validation.
Execute (User Initiated,

First Connection, Every
Connection)
Every
Connection
This setting should be used assuming there is a single Client

Association to the remote; otherwise, it should be set to User
Initiated. Note that there is some startup overhead for
performing Discovery on every connection, but this setting
provides the best configuration maintenance results.
Automatically Accept
Database Changes
Off
This setting ensures that the administrator reviews all

changes before they are put into effect.
Configured Data Values

Validate Configured Data
Values
On
These settings allow configuration mismatches to be

tolerated, so that mis-configured Client Data Values will not
prevent a DataSet from being created.
Remove Mismatches from

DataSets
On
Correct Mismatches in
Database
On
This setting allows AX-S4 ICCP to markup the

configuration database to show what configuration
mismatches are found. These markups do not affect
operation until the user accepts or rejects the changes.

(Normal, Detailed)
Normal
This setting verifies that the Client Data Values are

accessible and provides reasonable confidence on data types.
Detailed validation provides more positive type validation
but is much slower.
Discover New Data Values
On

Add to Active
Configuration
Off
This setting ensures that the administrator reviews all

changes before they are put into effect.
Add to Database
On

Set Read Only Attribute
On
Depends on the remote implementation, but writing data

values is somewhat unusual.
New Data Values
113
Discovery Options
Setting
Notes
Derive Type Using (Quick,

Normal)
Normal
This setting is appropriate when the remote is a well

behaved ICCP Server. Only Data Value names should be
returned by the server in the Get Data Value Names
operation. The Remote ICCP Server must return ICCP
responses for the Get Data Value Type operations that
comply with the IEC 60870-6-802 specification on
IndicationPoint Type descriptions.
AUTO DSTS
Options
Setting
Notes
Enable
On
Under this policy the administrator can make use of either

configured or AUTO DSTS. In general, AUTO DSTS should
be used so that all Client Data Values are certain to be
included in DSTS.
Redundancy Options
Enabled
On
Timeout
60000
System and application dependent.
Backup OPC
Local Data Quality Flag
(Bad, Good, Uncertain)
Good
Remote Data Quality Flag

(Bad, Good, Uncertain)
Good
Server State Suspended
Off
OPC Client and application dependent.
RPL Timers
Retry Time
2000
Startup Time
10000
Heartbeat TX Period
5000
Switch to Active Delay
1000
Mode (None, Local, Local
& Remote)
Local &
Remote

Mode (None, Active,
Primary, Secondary)
114
None
This setting requires that configuration synchronization be

initiated manually.
Policy 2: Automatic Configuration Changes

1.
Client Data Value Configuration

Differences between the current set of configured Client Data Values and
that which is exposed by the remote control center will be discovered by
AX-S4 ICCP and written into the configuration database without
administrator approval. This will include new, deleted, and changed data
values.
All changes will be put into effect immediately, so that newly added Client
Data Values will be available via new OPC items.
2.
Active to Standby node configuration synchronization will be initiated
automatically by AX-S4 ICCP when differences are detected. This means
that the node in the Standby node (configuration synchronization Slave)
will pull the configuration from the Active node (configuration
synchronization Master) via the RPL connection.
3.
Considerations
Note that when using this policy, configuration changes happen
automatically and without visibility based entirely on the behavior of the
remote ICCP node. This is only advisable when the nature of the remote
ICCP node and its administrator policies are well known.
a.
AX-S4 ICCP must be using a single client association.
b.
The remote ICCP implementation must be well behaved with respect

to the MMS GetNameList and GetVariableAccessAttributes services
as specified by the TASE.2 services (Get Data Value Names, Get
Data Value Types):
i.
Data Values only are to be returned in the GetNameList

response.
ii.
Data Values must be exposed via the GetNameList in either

VCC or ICC scope (not both).
iii. The correct ASN.1 type definitions (including element names)

must be returned for data values.
c.
The administrator of the remote ICCP node must make use of

acceptable configuration management policies.
115
d.
4.
Local configuration changes to Client Data Values are not persistent.

That is, if the administrator manually changes Client Data Values in
either node, they will be overwritten by AX-S4 ICCP during the
discovery or configuration synchronization processes.
The following settings should be used on the forms indicated in the table:
Configuration Settings
Discovery
Options
Setting
Note
Enable Discovery
On
Discovery should almost always be enabled, because it is the

mechanism used to perform configured Data Value validation.
Execute (User
Initiated, First
Connection, Every
Connection)
Every
Connection
This setting should be used assuming there is a single Client

Association to the remote; otherwise, it should be set to User
Initiated. Note that there is some startup overhead for performing
Discovery on every connection, but this setting provides the best
configuration maintenance results.
Automatically
Accept Database
Changes
On
This setting keeps changes from being easily visible to the system
administrator.
Configured Data Values

Validate Configured
Data Values
On
This setting allows configuration mismatches to be tolerated, so that

mis-configured Client Data Values will not prevent a DataSet from
being created.
Remove Mismatches
from DataSets
On
Correct Mismatches
in Database
On
This setting allows AX-S4 ICCP to markup the configuration

database to show what configuration mismatches are found. These
markups do not affect operation until the user accepts or rejects the
changes.

(Normal, Detailed)
Normal
This setting verifies that the Client Data Values are accessible and
provides reasonable confidence on data types. Detailed validation
provides more positive type validation but is much slower.
Discover New Data

Values
On

changes.
Add to Active
Configuration
On
This setting exposes new Client Data Values as OPC items when
they are discovered.
New Data Values
116
Discovery
Options
Setting
Note
Add to Database
On

changes.
Set Read Only

Attribute
On
Depends on the remote implementation, but writing data values is

somewhat unusual.
Derive Type Using

(Quick, Normal)
Normal
This setting is appropriate when the remote is a well behaved ICCP

Server. Only Data Value names should be returned by the server in
the Get Data Value Names operation. The Remote ICCP Server
must return ICCP responses for the Get Data Value Type operations
that comply with the IEC 60870-6-802 specification on
IndicationPoint Type descriptions.
AUTO DSTS
Options
Setting
Note
Enable
On
Under this policy configured DSTS are not effective, and so the
AUTO DSTS features should be enabled so that all Client Data
Values are included in DSTS.
Redundancy Options
Enabled
On
Timeout
60000
Backup OPC
Local Data Quality
Flag (Bad, Good,
Uncertain)
Good
Remote Data Quality

Flag (Bad, Good,
Uncertain)
Good
Server State
Suspended
Off
RPL Timers
Retry Time
2000

117
Discovery
Options
Setting
Startup Time
10000
Heartbeat TX Period
5000
Switch to Active
Delay
1000
Note
Mode (None, Local,
Local & Remote)
Local &
Remote

Mode (None, Active,
Primary, Secondary)
Active
This setting instructs the Standby node to obtain its configuration

from the Active node whenever changes are detected.
Data Synchronization Sample Startup Scenarios

The table below demonstrates a set of typical data synchronization scenarios.
Configuration CRC mismatches are marked with a *.
Node A
Scenario
118
Node B
Local
Rem 1
Rem 2
Local
Rem 1
Rem 2
CRC
CRC
CRC
CRC
CRC
CRC
Identical
Configurations.
Data A,B sent
Identical
Configurations.
Data A,B,C
sent
Remarks
Local data
sync OK
Remote 1
data sync
OK
Local data
sync OK
Remote 1
data sync
OK
Remote 2
data sync
OK
Node A
Scenario
Node B
Local
Rem 1
Rem 2
Local
Rem 1
Rem 2
CRC
CRC
CRC
CRC
CRC
CRC
Local match,
Remote
mismatch.
Data A sent
*B
*C
Local
mismatch,
Remote match.
Data B sent
*A
*C
Local match, 1
Remote
mismatch.
Data A,B sent
*C
Remarks
Local data
sync OK
Remote 1
data sync
NOT OK
Local data
sync NOT
OK
Remote 1
data sync
OK
*D
Local data
sync OK
Remote 1
data sync
OK
Remote 2
data sync
NOT OK
Data Synchronization Scenario: Add Remote

This scenario illustrates the sequence of events for adding a Remote node to a
redundant AX-S4 ICCP system. Configuration CRC mismatches are marked
with a *.
Node A
Node B
Step
Local
CRC
Rem 1
CRC
Startup
w/Identical
Configurations.
Data A,B sent
Active Node
(A) adds
Remote 2 online. CRCs
exchanged.
No Data sent
Standby Node
(B) adds
Remote 2 online. CRCs
exchanged.
Data C sent
Rem 2
CRC
Local
CRC
Rem 1
CRC
Rem 2
CRC
*C
n/a
Remarks
Local data sync

OK
Remote 1 data
sync OK
Local data sync
OK
Remote 1 data
sync OK
Remote 2 data
sync NOT OK
Local data sync
OK
Remote 1 data
sync OK
Remote 2 data
sync OK
119
120
Chapter 8: AX-S4 ICCP Monitor
Chapter 8
AX-S4 ICCP Monitor

The AX-S4 ICCP Monitor is an OPC client application designed for monitoring and
controlling AX-S4 ICCP. It allows a user to examine the state of internal AX-S4 ICCP
elements such as associations, Data Values, DSTS, Devices, Messages, statistics, etc.
The AX-S4 ICCP Monitor also allows control of associations and the discovery,
redundancy, and logging subsystems.
Figure 8: AX-S4 ICCP Monitor Main Screen

The following are configuration definitions available from the drop down menu
selections on the top:
121
Drop-Down Menus
Edit
Preferences
Figure 9: AX-S4 ICCP Monitor Preferences

This feature displays the following configurable parameters:
Group Update Rate
Indicates the default update rate for all OPC

groups shown in the AX-S4 ICCP Monitor.
Double Click
This preference allows selecting whether the

mouse selection is a double click or a single click
(box is unchecked).
Local Data Value Fields These preferences allow selecting which fields to
display for the Selected tab of any Local Data
Values.
122
Remote Data Value Fields
These preferences allow selecting which

fields to display for the Selected tab of
any Remote Data Values.
Tools
Clear Status
This feature clears the status pane at the bottom of the monitor.
Start Log Viewer

This feature starts the SISCO Log Viewer. The SISCO Log Viewer allows
users to view logging generated from one or more logging sources. It makes
use of TCP/IP for log data transfer, and so can be used to view diagnostic
logging from both local and remote sources. The SISCO Log Viewer is
compatible with Microsoft Client Terminal Services. Please refer to Appendix
A for more information.
123
Local Control Center Overview

The following screen is displayed when the Local Control Center Name is
selected in the tree in the left pane. It displays overview information on the
Local Control Center.
Figure 10: Local Control Center Overview screen

The following information is displayed:
AX-S4 ICCP Version Displays the release version of the software.
Status
Displays the Status of AX-S4 ICCP. Options are:

Running, Standby, or Suspended.
Remotes Number of Remotes
124
Indicates the number of configured

Number of Active Remotes
Indicates the number of Remote Control

Centers actively connected to AX-S4
ICCP.
Associations Number of Associations

Number of Active Associations
Indicates the number of

configured associations.
Indicates the number of associations

actively connected to AX-S4 ICCP.
Statistics
This screen displays general statistics on the local control center.
Figure 11: AX-S4 ICCP Monitor Statistics Screen

In all cases, the time stamp of the last item update is shown in the third column.
125
Server Services
Data Value Services
DSTS Reports Sent
Indicates the number of DataSetTransferSet Reports sent by

AX-S4 ICCP.
Data Value Read Indications
Indicates the number of Reads received by AX-S4

ICCP.
Data Value Write Indications
Indicates the number of Writes received by AX-S4

ICCP.
Device Services
Device Get Tag Indications
Indicates the number of Get Tags received by AXS4 ICCP.
Device Operate Indications
Indicates the number of Device Operates received

by AX-S4 ICCP.
Device Select Indications
Indicates the number of Device Selects received by

AX-S4 ICCP.
Device Set Tag Indications
Indicates the number of Set Tags received by AXS4 ICCP.
Information Messages
Information Messages Sent
Indicates the number of Information Messages sent

by AX-S4 ICCP.
Client Services
Data Value Services
DSTS Reports Received
Indicates the number of DataSetTransferSet

Reports received by AX-S4 ICCP.
Data Value Read Requests
Indicates the number of Read Requests sent by

AX-S4 ICCP. Note: After initial values have been
read by AX-S4 ICCP, the Enable Remote DV
Reads checkbox must be selected in the ICCP
Configuration Utility in order to use the
GetDataValues service to repeatedly poll Remote
Data Values. Caution: This behavior is NOT
recommended!
126
Data Value Write Requests
Indicates the number of Write Requests sent by

AX-S4 ICCP.
Device Services
Device Get Tag Requests
Indicates the number of Get Tag Requests sent by

AX-S4 ICCP.
Device Operate Requests
Indicates the number of Device Operate Requests

sent by AX-S4 ICCP.
Device Select Requests
Indicates the number of Device Select Requests

sent by AX-S4 ICCP.
Device Set Tag Requests
Indicates the number of Set Tag Requests sent by

AX-S4 ICCP.
Information Messages Received Indicates the number of Information Messages
received by AX-S4 ICCP.
Logging
This screen allows enabling/disabling of filtered logging for AX-S4 ICCP. General
AX-S4 ICCP Logging (as selected on the AX-S4 ICCP main screen) is global to all
associations. Filtered logging of MMS Client/Server primitive transactions and PDUs
(Protocol Data Units) is available on an association basis. As soon as you enable
logging on an association, it turns off association specific logging on all the other
associations.
Then Log Masks on the following screen can be enabled by setting the mask to True.
127
Figure 12: AX-S4 ICCP Monitor Log Masks

MMS
Client
This logging is useful to watch DataSets be created on the Client and

DSTransferSets received. An example of MMS client logging is
shown in Appendix A.
Server
This logging is useful to watch DataSets be created and

DSTransferSets sent. An example of MMS server logging is shown
in Appendix A.
Note:
128
Enabling Client and Server logging is useful when troubleshooting why an

association goes active but later disconnects. Client and Server logging
produces human readable decoded results from MMS PDUs. This can cause a
noticeable performance hit on a system. The standard log file will also wrap
quickly and often needs to be extended in size from the default.
PDU
MMS PDU (Protocol Data Unit) logs the hexadecimal encoding/

decoding coming across the wire. This logging is useful when it
becomes necessary to see a comprehensive list of client/server
transactions. Sometimes client/server logging causes the log file to
wrap prematurely and the interesting part of the conversation is lost.
PDU logging is not as severe a performance hit as enabling
Client/Server logging; therefore, more information can be retained
per logging incident. SISCO can then use a utility called mmslog to
analyze the information from the PDU log off-line. An example of
MMS PDU logging is shown in the Appendix A.
MI
Flow
This logging enables flow and audit information from the SISCO
MMS-EASE Lite ICCP implementation. An example of MI Flow
logging is shown the in Appendix A.
Matching
This logging displays how parameters configured in the

Identification tree affect the addressing configuration found for
Remote Control Centers. This log mask is useful when determining
why associations are not established. It will show which remotes are
considered for incoming connect indications and which remotes are
ignored. An example of MI Matching logging is shown in Appendix
A.
Config
This logging is useful when troubleshooting issues related to

configuration changes not showing up in the TASE.2 provider at
runtime (It shows what you have configured vs. what you think you
have configured). An example of ICCP logging is shown in
Appendix A.
Discovery
Logs client data value information retrieved from the server during
discovery.
AX-S4
Flow
This logging enables flow and audit information from the AX-S4
ICCP implementation. An example of AX-S4 Flow logging is shown
in Appendix A.
ICCP
This enables a high level audit of DataSet and DSTransferSet

creation. This logging is useful when troubleshooting DataSet and
DSTransferSet creation problems. An example of ICCP logging is
shown in the Appendix A.
129
Memory
This logging shows an internal low level audit of dynamic memory

allocated and released by the SISCO memory management library.
This log mask is normally only used internally by SISCO.
OPC
This enables an audit trail of the OPC methods used in the DA

server. Generally this is not useful. An example of OPC logging is
shown in Appendix A.
Debug
This provides more detailed logging for browsing and enumerating

objects. An example of Debug logging is shown in Appendix A.
ASN.1
Encode
This causes the production of each ASN.1 encoded MMS transaction

to be logged. This is useful for diagnosing MMS implementation
problems. An example of ASN.1 Encode logging is shown in
Appendix A.
Decode
This shows the parse of each incoming MMS transaction into the
class form tag length and data of each ASN.1 production. It is useful
for diagnosing MMS implementation problems as well as problems
related to seeing MMS rejects at runtime. An example of ASN.1
Decode logging is shown in Appendix A.
ACSE
Flow
This shows Layer 7 (ACSE) information related to IP Addresses and

selector values. This is useful for double-checking DIB information
used to troubleshoot problems seen when establishing associations.
An example of ACSE Flow logging is shown in Appendix A.
Decode
This is used to diagnose ACSE layer problems. It is generally not

used by customers. An example of ACSE Decode is shown in
Appendix A.
MVL
This is mostly connection related logging. An example of ACSE

MVL logging is shown in Appendix A.
Redundancy
This log mask is used to troubleshoot AX-S4 ICCP redundancy

issues. They show a varying level of information related to sharing
Data Values between machines and are not normally used by
customers.
Security
Flow
Data
Debug
130
This logging is used for the SISCO add-on toolkit only.
Log Timing
Elapsed
Indicates log time in elapsed seconds.

4900.069s MVLLOG_ACSEDATA (mvl_acse.c 1659)
Date/Time
Indicates log time in Date, Time format.

Wed Jun 09 14:39:57 2004 MVLLOG_ACSEDATA
(mvl_acse.c 1659)
System
Indicates log time in System Time format.

7283.566 sec MVLLOG_ACSEDATA (mvl_acse.c 1659)
Disabled
Disables all time stamping for logging.

MVLLOG_ACSEDATA (mvl_acse.c 1659)
Data Values
This screen displays all locally configured data values.
Figure 13: AX-S4 ICCP Monitor Data Values
131
Basic
The following items are displayed:
Name
This is a unique text string used to identify the data value.
Value
Indicates the value of the DataValue.
TimeStamp
Indicates the timestamp for a data value each time the value is
written by an OPC Client.
COV
Indicates the Change of Value counter for a data value each time the
value is written by an OPC Client.
Note:
Quality
The TimeStamp and COV fields are only updated when AX-S4 ICCP is
configured to do so; else the OPC client is required to update these two
fields.
In addition to Name, the following quality flags are displayed:
Quality Validity
Quality TimeStamp
Quality Normal Value
Quality Current Source
All
All options are displayed.
Selected
This folder displays the columns selected in the Preferences option

shown at the top of AX-S4 ICCP Monitor. As selecting additional
columns adds to the processing required by this utility, most columns
are set off by default.
132
Local Devices
This screen displays all locally configured devices.
Figure 14: AX-S4 ICCP Monitor Local Devices

Red means the quality was bad, so 'bad value' is displayed for the value. Magenta
means the quality is uncertain, so the value is displayed in magenta with a (?) behind it.
Basic
Name
This is a unique text string used to identify the device.
Operate Indication
When an Operate Device request is received from a remote

client, the Indication attribute is set to 1.
Operate Remote VCC
When the Operate Indication is set to 1, this attribute is set

to the name of the Remote Control Center requesting to
operate the device.
133
Operate Send Response This value is written by the OPC client after all Operate
response parameters are written to the OPC server. This
transitions the Operate Indication to the Off (0) state.
Operate Status
This value [04] is written by the OPC Client after an

Operate Indication is received.. Valid Status values are:
0 = Success
2 = Access Denied
Operate Value
Select
This is the value received from the ICCP Client during the
Operate Indication.
The following options are displayed:
Select Check Back ID
This is used for SBO Devices only. This attribute contains a

symbolic description of the physical object being
controlled. The data is returned by the system operating the
physical object to the system requesting the operation so
that the system requesting the operation can be assured the
proper object has been selected. The Check Back ID is a
16-bit integer.
Select Indication
When a Select Device Request is received from a remote

client, this attribute is changed to 1.
Select Remote VCC
When the Select Indication is set to 1, this attribute is

updated with the name of the Remote Control Center
requesting to select the device.
Select Send Response
True means the send response will be sent.
Select Status
This is the value sent to the ICCP Client by the Select

response.
Tag
Tag Reason
Indicates the reason for the tag.
Tag Remote VCC
Indicates the Remote Control Center that tagged the device.
Tag Value
Indicates the value of the tag received from the Remote

Control Center.
All
134
Local Messages
This screen displays all locally configured messages.
Figure 15: AX-S4 ICCP Local Messages

Name
Indicates a unique integer used to identify the information message.
Local Ref
Specifies a 32-bit integer value agreed upon between the sender and
receiver of the message. It is used to further identify the Information
Message.
Message
Displays the actual message to send to the Remote Control Center.
Message ID
Specifies a 32-bit integer used to identify different instances of an

Information Message object.
Remote VCC
Indicates the Remote Control Center to which to send the message.
Send Message
This attribute must be set to 1 to send an Information Message to the

135
Remote Control Centers Overview

This screen displays overview information on all configured Remote Control Centers.
Figure 16: AX-S4 ICCP Monitor Remote Control Centers Overview

Remote
Indicates the previously configured name of the Remote

Control Center.
Association
Indicates the name assigned to the association.
136
Enabled
Indicates whether this association is enabled. Enabled

means the status of the Link will transition towards an
ACTIVE status. Right click on this option allows disabling
the association to disabled.
Status
Indicates the status of the association options are: IDLE,

INIT_REQ, BACKOFF, ACTIVE, LISTEN,
CONCLUDING, DISCOVERY. IDLE generally means that
the association has not been started.
Authentication
This indicates the type of authentication used for this

connection. Default is none. This is only used for AX-S4
ICCP Secure.
Encryption
This indicates the type of encryption used for this

connection. Default is none. This is only used for AX-S4
ICCP Secure.
Individual Remote Control Center Overview

If a Remote Control Center name is selected, right click will provide the
following two options:
Reload
This allows reloading the Bilateral Table information according to the settings
in the IccpCfg utility.
Discover
This feature executes the discovery algorithm according to the parameters
known when 1) AXS4ICCP was started, or 2) the last time the Reload feature
was executed
Note:
If you have changed some parameters on the Discovery form of the IccpCfg
utility and want them used to discover Client Data Values, use the Reload
feature not the Discovery feature.
In addition, the following screen is displayed when a Remote Control Center
Name is selected in the tree in the left pane. It displays overview information
on the selected Remote Control Center
137

Bilateral Table ID
Indicates the symbolic name (up to 32 characters) of the

bilateral table version, which is matched to the remote
systems bilateral table version during the start of an
association. If the two do not match, the association is not
allowed.
TASE.2 Version
Indicates the supported version of TASE.2 (ICCP).
Supported Features
Indicates the value of the features supported by the remote

control center.
Association
Enabled

Status

138
Authentication

connection. Default is none.
Encryption

Statistics
This screen displays general statistics on the Remote Control Center.
Figure 17: AX-S4 ICCP Monitor RCC Statistics

In all cases, the time stamp of the last message received is shown in the third column.
Server Services
Data Value Services
DSTS Reports Sent
Indicates the number of DataSetTransferSet Reports sent to

Indicates the number of Read Indications received

from the Remote Control Center.
139
Indicates the number of Data Value Write

Indications received from the Remote Control
Center.
Device Services
Indicates the number of Get Tag Indications

received from the Remote Control Center.
Indicates the number of Device Operate

Center.
Indicates the number of Device Select Operations

performed by the Remote Control Center.
Indicates the number of Set Tag Operations

performed by the Remote Control Center.

to the Remote Control Center.
Client Services
Data Value Services

Reports received from the Remote Control Center.
Indicates the number of Read Requests sent to the

Indicates the number of Write Requests sent to the

Device Services
Indicates the number of Get Tag requests sent to

Indicates the number of Device Operate requests

sent to the Remote Control Center.
Indicates the number of Device Select requests

sent to a Remote Control Center.
Indicates the number of Set Tag requests sent to a

140
Errors
Indicates the number of service errors encountered

during the ICCP conversation.
Remote Control Center Association Overview

This screen displays association information on a specified Remote Control Center.
Association
Enabled

141
Status

Authentication

connection. Default is None.
Encryption

Remote Control Center Association Statistics

This screen displays statistics associated information with primary link of a specified
Figure 18: AX-S4 ICCP Monitor Remote CC Association Statistics

In all cases, the time stamp of the last OPC item update is shown in the third column.
Server Services
Data Value Services
142
DSTS Reports Sent
Indicates the number of DataSetTransferSet Reports sent to

Indicates the number of Read Indications received

Indicates the number of Write Indications received

Device Services
Indicates the number of Get Tag Indications

Indicates the number of Device Operate

Center.
Indicates the number of Device Select Indications

Indicates the number of Set Tag Indications


to the remote control center.
Client Services
Data Value Services

Reports received by Remote Control Center.
Indicates the number of Read Requests sent to

Indicates the number of Write Requests sent to

Device Services
Indicates the number of Get Tag Requests sent to

Indicates the number of Device Operate Requests

sent to Remote Control Center.
143
Indicates the number of Device Select Requests

sent to Remote Control Center.
Indicates the number of Set Tag Requests sent to

Errors
Indicates the number of various errors encountered

during the ICCP conversation.
Remote Control Center Data Values

This screen displays information on data values configured for this selected Remote
Control Center.
Figure 19: AX-S4 ICCP Monitor RCC Data Values

Basic
144
Name
Value
TimeStamp
Indicates the timestamp attribute for the Data Value as assigned by

COV
Indicates the Change of Value counter for a data value each time the
value is changed in the Remote Control Center. If this value
increments more than a value of 1 between changes, it has changed
value more than once.
DS Conditions Detected The conditions that triggered the DSTransferSet report to be

sent. Possible values are:
OtherExternalEvent
IntegrityTimeOut
OperatorRequest
ObjectChange
IntervalTimeOut
Transfer Set Time Stamp Indicates the time the Transfer Report was generated by the
server.
Quality In addition to Name, the following quality flags are displayed:
Quality Validity
Quality TimeStamp
All
Selected

145
Remote Control Center Devices

This screen displays all configured devices for a selected Remote Control Center.
Figure 20: AX-S4 ICCP Monitor RCC Devices

Basic
Name
This is a unique text string used to identify the device.
Operate Send Request
If set to 1, indicates that an Operate Send Request will be

sent to the Remote Control Center.
Operate Status
This value [04] is sent by the Remote Control Center in

the Operate response. Valid Status values are:
0 = Success
2 = Access Denied
146
Operate Value
Select
This value is sent to the Remote Control Center in the

Operate request.
Select Check Back ID
This is used for SBO Devices only. The data is received

from the Remote Control Center in the Select response. The
Check Back ID is a 16-bit integer.
Select Send Request
If set to 1, indicates that a Select Send Request will be sent

to the Remote Control Center.
Operate Status
This value [04] is received from the Remote Control

Center in the Operate response. Valid Status values are:
0 = Success
2 = Access Denied
Tag
Get Tag Reason
Get Tag Send Request
When the Get Tag Send Request is set to 1, the Get Tag
Send Request is sent to the Remote Control Center.
Get Tag Status
Indicates the Status of the Get Tag Send Request options

are:
SUCCESS
NO-TAG-ATTRIBUTE
ACCESS-DENIED
DEVICE-TEMP-UNAVAILABLE
OTHER-ERROR
Get Tag Value
Indicates the value of the tag received from the Get Tag
Send Request.
Set Tag Reason
Set Tag Send Request
When the Set Tag Send Request is set to 1, the Set Tag
Send Request is sent to the Remote Control Center.
147
Set Tag Status
Indicates the Status of the Set Tag Send Request options

are:
SUCCESS
NO-TAG-ATTRIBUTE
ACCESS-DENIED
DEVICE-TEMP-UNAVAILABLE
OTHER-ERROR.
Set Tag Value

All
Indicates the value of the tag received from the Set Tag
Send Request.
Remote Control Center Messages

This screen displays all configured messages on a selected Remote Control Center.
Figure 21: AX-S4 ICCP Monitor RCC Messages

Name
148
Indicates a unique integer used to identify the information message.
Local Ref
Indicates the Local reference received from the Remote Control

Center.
Message
Displays the actual message received from the Remote Control

Center.
Message ID
Indicates the Message ID attribute received from the Remote Control

Center.
Remote Control Center DSTS Overview

This screen displays overview information on all previously configured
DSTransferSets on a selected Remote Control Center.
Figure 22: AX-S4 ICCP Monitor RCC DSTS Overview

Name
Indicates the name of the DSTransferSet.
Enabled
Indicates whether the DSTransferSet is enabled.

149
Last Time of Report
Indicates the last time the DSTransferSet was sent.
Remote Control Center DSTS Status and Parameters

This screen displays information on a selected DSTransferSet.
Figure 23: AX-S4 ICCP Monitor RCC DSTS Status and Parameters
Status
Enabled
Indicates if this DSTransferSet is enabled.
Association
Indicates the name of the association.
Data Set Name
Indicates the name of the Data Set.
Name
Report Count
Indicates the number of DSTransferSets sent.
Last Time of Report
150
Parameters
Start Time
Indicates the time value for the TASE.2 server to begin

Condition Monitoring.
RBE
Indicates whether RBE is enabled. Report By Exception

implies that the changed objects are reported.
Critical
Indicates whether critical is enabled. This controls the type

of Transfer Report acknowledgement. A setting of True
means that the Transfer Report is critical and an
acknowledgement from the TASE.2 client back to the
TASE.2 server is expected.
DSConditions.Interval Indicates whether or not the TASE.2 server should send a

report when the Interval time arrives.
DSConditions.Integrity Indicates whether or not the TASE.2 server should send a
report of the entire Data Set when the Integrity Check time
interval expires. This only applies when RBE is TRUE.
DSConditions.Change Indicates whether or not the TASE.2 server should send a
report when any object in the Data Set changes. Possible
changes include a change of value, status, or the quality flag
DSConditions.Operator Indicates whether or not the TASE.2 server should send a
report when an operator at the TASE.2 server control center
requests it.
DSConditions.External Indicates whether or not the TASE.2 server should send a
report when any other external event condition that is not
described in the other conditions becomes true.
Interval
Indicates the time interval between TASE.2 server reports.

The Interval starts when the Start Time occurs. If RBE is set
to No, then the current state of all objects in the data set are
reported when the Interval expires. If RBE is set to Yes,
then the current state of only the changed objects in the data
set are reported when the Interval expires. If multiple
changes occur to the same object during the Interval, then
only the final value is reported. .
Integrity Check
Indicates the time value for integrity check when

IntegrityTimeOut and RBE conditions are used.
151
Buffer Time
Indicates the time interval for buffering the ObjectChange

condition before reporting to the TASE.2 client. The Buffer
Time starts when the first ObjectChange condition occurs.
If RBE is false, then the current states of all objects in the
Data Set are reported when the Buffer Time expires. If RBE
is true, then the current state of only the changed objects in
the Data Set are reported when the Buffer Time expires. If
the Buffer Time is zero, then a report is generated for each
change. If multiple changes occur to the same object during
the Buffer Time, then only the final value is reported.
TLE
Indicates the time value for Time Limit for Execution. This
is a time that is primarily relevant to the TASE.2 server. It is
the time over which the TASE.2 server has to send the Data
Set Transfer Report to the TASE.2 client. If the TASE.2
server anticipates that it cannot send the Data Set Transfer
Report to the TASE.2 client within the TLE time, then it
shall not generate the report, and shall discard the data.
152
Remote Control Center Selected DSTS Data Values

This screen displays information on the data values associated with a selected
DSTransferSet.
Figure 24: AX-S4 ICCP Monitor RCC Selected DSTS Data Values
Basic
Name
Value
TimeStamp
Indicates the timestamp for a data value.
COV
Indicates the Change of Value counter for a data.
Indicates the DS Conditions Detected object

specifying conditions that became true, triggering
the generation of the Transfer Report. AX-S4
ICCP requires DS Conditions detected.
153
Indicates the time the Transfer Report was

generated by the server.
Quality
Quality Validity
Quality TimeStamp
All
Selected

Local Data Set Transfer Sets Overview

This screen displays all locally configured DSTransferSets.
Figure 25: AX-S4 ICCP Monitor Local DSTS Overview
154

Name
Enabled
Indicates whether the DSTransferSet is enabled.
Last Time of Report
Local DSTS Status and Parameters
Figure 26: AX-S4 ICCP Monitor Local DSTS Status & Parameters
Status
Enabled
Indicates if this DSTransferSet is enabled.
Association
Indicates the name of the association.
Data Set Name
Indicates the name of the Data Set.
Name
Report Count
Indicates the number of DSTransferSets sent.

155
Last Time of Report
Parameters
Start Time
Indicates the time value for the TASE.2 server to begin

Condition Monitoring.
RBE
Indicates whether RBE is enabled. Report By Exception

implies that the changed objects are reported.
Critical
Indicates whether critical is enabled. This controls the type

of Transfer Report acknowledgement. A setting of True
means that the Transfer Report is critical and an
acknowledgement from the TASE.2 client back to the
TASE.2 server is expected.
DSConditions.Interval Indicates whether or not the TASE.2 server should send a

report when the Interval time arrives.
DSConditions.Integrity Indicates whether or not the TASE.2 server should send a
report of the entire Data Set when the Integrity Check time
interval expires. This only applies when RBE is TRUE.
DSConditions.Change Indicates whether or not the TASE.2 server should send a
report when any object in the Data Set changes. Possible
changes include a change of value, status, or the quality flag
DSConditions.Operator Indicates whether or not the TASE.2 server should send a
report when an operator at the TASE.2 server control center
requests it.
DSConditions.External Indicates whether or not the TASE.2 server should send a
report when any other external event condition that is not
described in the other conditions becomes true.
Interval
Indicates the time interval between TASE.2 server reports.

The Interval starts when the Start Time occurs. If RBE is set
to No, then the current state of all objects in the data set are
reported when the Interval expires. If RBE is set to Yes,
then the current state of only the changed objects in the data
set are reported when the Interval expires. If multiple
changes occur to the same object during the Interval, then
only the final value is reported. .
Integrity Check
Indicates the time value for integrity check when

IntegrityTimeOut and RBE conditions are used.
156
Buffer Time
Indicates the time interval for buffering the ObjectChange

condition before reporting to the TASE.2 client. The Buffer
Time starts when the first ObjectChange condition occurs.
If RBE is false, then the current states of all objects in the
Data Set are reported when the Buffer Time expires. If RBE
is true, then the current state of only the changed objects in
the Data Set are reported when the Buffer Time expires. If
the Buffer Time is zero, then a report is generated for each
change. If multiple changes occur to the same object during
the Buffer Time, then only the final value is reported.
TLE
Indicates the time value for Time Limit for Execution. This
is a time that is primarily relevant to the TASE.2 server. It is
the time over which the TASE.2 server has to send the Data
Set Transfer Report to the TASE.2 client. If the TASE.2
server anticipates that it cannot send the Data Set Transfer
Report to the TASE.2 client within the TLE time, then it
shall not generate the report, and shall discard the data.
Local Selected DSTS Data Values
Figure 27: AX-S4 ICCP Monitor Local Selected DSTS Data Values
157
Basic
Name
Value
TimeStamp
Indicates the timestamp for a data value.
COV
Indicates the Change of Value counter for a data.
Indicates the DS Conditions Detected object

specifying conditions that became true, triggering
the generation of the Transfer Report. AX-S4
ICCP requires DS Conditions detected.
Indicates the time the Transfer Report was

generated by the server.
Quality
Quality Validity
Quality TimeStamp
All
Selected

158
Appendix A: Log Viewer and Logging
Appendix A
Log Viewer and Logging

The Log Viewer is a SISCO application used to look at logging from multiple
applications in one file. It can also be setup on a remote machine to capture
logging from multiple applications. Current log parameter settings can be
modified without bringing applications down. This allows modifying log
parameters while the application is running.
To capture logging for applications running on the same computer as the Log
Viewer, no additional configuration has to be done. The Log Viewer will
automatically detect the applications and start capturing their logging.
To capture logging for applications running on a different computer, the Log
Viewer will have to be configured to look for the application. The SISCO Log
Viewer runs on the Windows platform but can remotely access logging on
non-Windows machines.
Please refer to the LogViewer Users Guide for general information on how to
use this application. StartProgramsSISCOLog ViewerSISCO
Log Viewer Users Guide.
159
Log File Locations

Log files will be located in the following directories:
160
<Common Application Data>\SISCO\LogViewer
<Common Application Data>\SISCO\AX-S4 ICCP

o AXS4ICCP.log
To access these directories, folder options need to be set to Show hidden files and
folders.
Within the file directory window select Alt-F. This will bring up an alternate menu
select Tools Folder Options. Make sure that show hidden files, folders, and
drives is selected.
For example:
\Documents and Settings\All Users\Application Data\SISCO\AX-S4
ICCP\axs4iccp.log
AX-S4 ICCP provides several useful diagnostic tools for troubleshooting problems in
addressing, configuration, and application development. Samples of different log
masks are shown later in this section.
161
AX-S4 ICCP0 Client Control LogMask definitions

Log Viewer Source Name: AXSICCPControl
The log configuration file for AX-S4 ICCP is called AxsICCPLogCfg.xml.
Standard Logging
No logging turned on results in errors and normal errors logging. This is the
recommended default logging since it will capture errors without comprising
the system usage. Any additional logging turned on for any extensive time
period will result in increases in CPU usage and a decrease in performance.
This is not recommended without recommendation from SISCO Technical
Support.
162
Axs4ICCPLogMasks
Flow
This logging displays the flow and audit information for AX-S4 ICCP. It
basically displays activity within the AX-S4 ICCP interface.
Recommended setting: Disabled.
ICCP
This enables a high level audit of DataSet and DSTransferSet creation.
This logging is useful when troubleshooting DataSet and DSTransferSet
creation problems. Recommended setting: Disabled.
OPC
OPC logging shows OPC transaction activity such as browsing and the
OPC method used. This logging is not particularly useful unless
troubleshooting specific AX-S4 ICCP to OPC Client problems.
Recommended setting: Disabled.
163
OPCData
OPCData logs all variant data when an OPC client issues a Write or
WriteVQT request.Recommended setting: Disabled.
MiLogMasks
Configuration
This logging is useful when troubleshooting issues related to
configuration changes not showing up in the ICCP provider at runtime (It
shows what you have configured vs. what you think you have
configured). Recommended setting: Disabled.
Addressing
This logging displays how parameters configured in the Identification
tree affect the addressing configuration found for Remote Control
Centers. This log mask is useful when determining why associations are
not established. It will show which remotes are considered for incoming
connect indications and which remotes are ignored. Recommended
setting: Disabled
Discovery
Logs client data value information retrieved from the server during
discovery. Recommended setting: Disabled
Flow
This logging enables flow and audit information from the SISCO
MMS-EASE Lite ICCP implementation. Recommended setting: Disabled
MmsLogMasks
Client
This logging displays information on AX-S4 ICCP to Remote Control
Center activity from the client side such as connection issues as well as
read and write requests. Recommended setting: Disabled.
Server
This logging displays information on AX-S4 ICCP to Remote Control
Center from the server side such as connection issues as well as read
and write requests. Normally Client and Server logging are turned on in
conjunction to troubleshoot problems concerning associations and
address configuration. Recommended setting: Disabled.
164
MvlLogMasks
Flow
This logging displays the flow control logging for MMS-Lite Virtual
Machine interface. These are internal MVL calls from within AX-S4
ICCP. Recommended setting: disabled.
ACSE
This logging audits MMS events passed up through the ACSE layer
mostly connection related logging. Recommended setting: disabled
unless specified by SISCO Technical Support.
ACSEData
ACSEData displays the raw ACSE message (as hex bytes). This is
normally only useful for diagnosing ACSE encoding or decoding
problems. Recommended setting: Disabled unless specified by SISCO
Technical Support.
SecurityLogMasks
This logging is used for the SISCO add-on toolkit only and is provided in
separate documentation . If the Security Extensions is not installed, no logging
is generated.
RedundancyLogMasks
RPL_LOG_NERR
This log mask is used to show nonfatal errors on the redundancy link in
AX-S4 ICCP. This is enabled by default.
RPL_LOG_FLOW
This log mask is used to show redundancy link flow and audit tracing in
AX-S4 ICCP. Recommended setting: disabled.
IR_LOG_NERR
This log mask is used to show nonfatal errors in the redundancy
implementation. This is enabled by default.
IR_LOG_FLOW
This log mask will track redundancy transactions. Recommended setting:
disabled.
165
IR_LOG_DATA
This log mask will track redundancy data synchronization. Recommended
setting: disabled.
ACSELogMasks
AcseEncode
This is used to diagnose ACSE layer problems in encoding. It is generally
not used by customers. Recommended setting: disabled.
AcseDecode
This is used to diagnose ACSE layer problems in decoding. It is generally
not used by customers. Recommended setting: disabled.
SocketLogMasks
Notice
This log mask will show nonfatal errors in IPC communications (ie,
redundancy link or log viewer link. This logging is enabled by default.
Flow
This is used to diagnose flow control in the socket layer. Recommended
setting: disabled.
Transmit
This logging shows Redundancy data being transmitted at the TCP socket
layer. Normally when its enabled and nothing is logged, Redundancy is
misconfigured or the Windows Firewall is on without an exception
configured for the Redundancy port. This is used to diagnose transmit
messages in the socket layer. Recommended setting: disabled.
Receive
This logging shows Redundancy data being received at the TCP socket
layer. Normally when its enabled and nothing is logged, Redundancy is
misconfigured or the Windows Firewall is on without an exception
configured for the Redundancy port. This is used to diagnose receive
messages in the socket layer. Recommended setting: disabled.
166
SxLogMasks
Notice
This log mask shows nonfatal errors when parsing xml data. This logging
is enabled by default.
Decode
This is used to diagnose something decode problems when parsing xml
data. Recommended setting: disabled.
ASN.1LogMasks
Notice
This log mask shows nonfatal errors during ASN.1 encoding or decoding.
This logging is enabled by default.
Encode
This logging displays encoding of a PDU at the ASN.1 level. The SISCO
ASN.1 encoder builds from back to front. It is recommended to remain
off unless specified by SISCO Technical Support.
Decode
This logging displays ASN.1 decode information such as parsing class,
form, tag, length, and contents. It is recommended to remain off unless
specified by SISCO Technical Support.
SuicLogMasks
Indication
This logging shows ACSE indication logging (the module that interfaces
MMS to the underlying OSI Stack) in MMS Protocol Data Units (PDUs)
to the application. Recommended setting: disabled unless specified by
SISCO Technical Support.
Confirm
This logging shows ACSE confirmation logging (the module that
interfaces MMS to the underlying SISCO Stack) in MMS Protocol Data
Units (PDUs) to the application. Recommended setting: disabled unless
specified by SISCO Technical Support.
167
Abort
This logging displays the information on aborts from the SUIC layer
interface. Recommended setting: disabled unless specified by SISCO
Technical Support.
Sample Logging
MMS Client Logging
***********************************************************
LOGGING STARTED Thu Oct 27 16:14:17 2011
***********************************************************
2011-10-27 16:14:17.976 SW_LOCK_FLOW (SwLock.cpp 300 0x000006ac)
Software License: HASP 28 Days Remaining
Indicates licensing
2011-10-27 16:14:18.007 SLOGALWAYS (Axiccb.c 111 0x000006ac)
Product: AXS4ICCP-132-095, Version: 5.0000.0 Indicates version
2011-10-27 16:14:18.757 AXIC_LOG_ALWAYS (axs4iccp.cpp 807 0x000006ac)
AX-S4 ICCP Started OK
2011-10-27 16:14:18.914 AXIC_LOG_NERR (Iccp.cpp 1604 0x00000bcc)
Discover not enabled for remote UtilitySiteB
2011-10-27 16:14:26.726 MMS_LOG_ALWAYS (Mlogl.c 185 0x00000bb0)
MMS Request
Reading special variables for Bilateral Table
Invoke ID = 1
Opcode = 4
Operation is : READ
Specification with Result : NO
Variable Access Specification
Number of Variables = 3
Variable 1)
DOM-Specific Domain Id: ICCP_B
Item Id: Bilateral_Table_ID
Alternate Access : Not Present
Variable 2)
VMD-Specific Name : Supported_Features
Variable 3)
VMD-Specific Name : TASE2_Version
MMS Confirm
Invoke ID = 1
Opcode = 4
Operation is : READ
Variable Access Specification : Not Present.
Number of Access Results = 3
Result
1) : Success
Derived TDL: Fstring11
VIS STRING value : SiteA_SiteB
Bilateral Table ID
168
Result
2) : Success
Derived TDL: Bstring12
BIT STRING value :
00000 D8 00
Result
3) : Success
Derived TDL: {Long,Long}
StructureStart
INTEGER 32 value : 2000
StructureEnd
Supported Blocks
*.*
TASE.2 version

MMS Request
Invoke ID = 2
Opcode = 2
Operation is : IDENTIFY
MMS Request
Invoke ID = 3
Opcode = 13
Operation is : DEL_VARLIST
Scope of Delete = 0,
Scope of Delete = 0, specific
Domain Name : Not Present
Variable Names : 1
Item Id: ExtendedMeasurements
MMS Confirm
Invoke ID = 2
Opcode = 2
System Information Follows:
Vendor
: SISCO
Model
: ICCP-Lite
Revision : 5.4000
2011-10-27 16:14:26.836 AXIC_LOG_NERR (Axicmi.c 509 0x00000bb0)
Identify Response for Remote 'UtilitySiteB', Association
'PrimaryLink':
Vendor: 'SISCO'
Identify Information returned from SiteB
Model: 'ICCP-Lite'
Revision: '5.4000'
MMS Confirm
Invoke ID = 3
Opcode = 13
Number Matched : 1
Number Deleted : 1
MMS Request
Returns list of Data Values
Invoke ID = 4
Opcode = 11
Operation is : DEF_VARLIST
169
Item Id: ExtendedMeasurements

Variable 1)
Item Id: Transfer_Set_Name
Variable 2)
Item Id: Transfer_Set_Time_Stamp
Variable 3)
Item Id: DSConditions_Detected
Variable 4)
Item Id: MEASUREMENT_DE_01
Variable 5)
Variable 6)
Variable 7)
Variable 8)
Variable 9)
Item Id: MEASUREMENT_RE_01
Variable 10)
Variable 11)
Variable 12)
Variable 13)
Variable 14)
Item Id: MEASUREMENT_SE_01
Variable 15)
170

Variable 16)
Variable 17)
Variable 18)
MMS Confirm
Invoke ID = 4
Opcode = 11
MMS Request
Invoke ID = 5
Opcode = 4
Operation is : READ
Variable 1)
Item Id: Next_DSTransfer_Set
MMS Request
Invoke ID = 6
Opcode = 5
Operation is : WRITE
Variable 1)
AA -Specific Name : IM_Transfer_Set
Number of Data to Write : 1
Write Data 1)
Derived TDL: Bool
ST_BOOLEAN value
: 1
MMS Confirm
Invoke ID = 5
Opcode = 4
Operation is : READ
Result
1) : Success
Derived TDL: {Ulong,Fstring6,Fstring8}
StructureStart
UNSIGNED 32 value : 1
171
VIS STRING value

VIS STRING value
StructureEnd
: ICCP_B
: DSTS0000

MMS Request
Invoke ID = 7
Opcode = 5
Variable 1)
Item Id: DSTS0000
Number of Data to Write : 1
Write Data 1)
Derived TDL:
{{Ulong,Fstring6,Fstring20},Long,Long,Long,Long,Long,Bstring5,Bool,Bool,
Bool,Bool,Bool,Long}
StructureStart
StructureStart
UNSIGNED 32 value : 1
VIS STRING value : ICCP_B
VIS STRING value : ExtendedMeasurements
StructureEnd
BIT STRING value :
00000 60
*`*
ST_BOOLEAN value
: 0
ST_BOOLEAN value
: 0
ST_BOOLEAN value
: 1
ST_BOOLEAN value
: 0
ST_BOOLEAN value
: 1
StructureEnd
MMS Confirm
Invoke ID = 6
Opcode = 5
Number of Results = 1
Response
1) : Success
MMS Confirm
Invoke ID = 7
Opcode = 5
Number of Results = 1
Response
1) : Success
172
MMS Server Logging

***********************************************************
***********************************************************
2011-10-27 16:16:48.220 SW_LOCK_FLOW (SwLock.cpp 300 0x0000084c)
2011-10-27 16:16:48.251 SLOGALWAYS (Axiccb.c 111 0x0000084c)
Product: AXS4ICCP-132-095, Version: 5.0000.0
2011-10-27 16:16:48.954 AXIC_LOG_ALWAYS (axs4iccp.cpp 807 0x0000084c)
2011-10-27 16:16:49.157 AXIC_LOG_NERR (Iccp.cpp 1604 0x00000aa8)
2011-10-27 16:16:54.829 MMS_LOG_ALWAYS (Mlogl.c 185 0x000009c0)
MMS Indication
MMS indication received from SiteB
Invoke ID = 0
Opcode = 85
Operation is : INITIATE
MMS CORE P-CONTEXT INITIATE
Max Segment Size = 32000.
Max Outstanding Requests Calling = 5.
Max Outstanding Requests Called = 5.
Max Data Nesting = 5.
MMS initiate Detail :
Version : 1
Parameter Support :
STR1
STR2
VNAM
VLIS
Service Support:
GET_NAMLIST
IDENTIFY
READ
WRITE
GET_VARDEF
DEF_VARLIST
GET_VARLIST
DEL_VARLIST
INFO_RPT
CONCLUDE
Core Context Position : 0
MMS Response
Invoke ID = 0
Opcode = 85
Operation is : INITIATE
MMS CORE P-CONTEXT INITIATE
Max Segment Size = 32000.
Max Outstanding Requests Calling = 5.
Max Outstanding Requests Called = 5.
Max Data Nesting = 5.
MMS initiate Detail :
173
Version : 1
Parameter Support :
STR1
STR2
VNAM
VLIS
Service Support:
GET_NAMLIST
IDENTIFY
READ
WRITE
GET_VARDEF
DEF_VARLIST
GET_VARLIST
DEL_VARLIST
INFO_RPT
CONCLUDE
Core Context Position : 0
MMS Indication
Indication from SiteB showing Bilateral Table info
Invoke ID = 22
Opcode = 4
Operation is : READ
Variable 1)
DOM-Specific Domain Id: ICCP_A
Item Id: Bilateral_Table_ID
Variable 2)
VMD-Specific Name : Supported_Features
Variable 3)
VMD-Specific Name : TASE2_Version
MMS Response
Local Variables sent to SiteB
Invoke ID = 22
Opcode = 4
Operation is : READ
Result
1) : Success
Derived TDL: Fstring11
VIS STRING value : SiteA_SiteB
Result
2) : Success
Derived TDL: Bstring12
BIT STRING value :
00000 D8 00
*.*
Result
3) : Success
Derived TDL: {Long,Long}
StructureStart
StructureEnd
174
MMS Indication
Invoke ID = 23
Opcode = 2
MMS Response
Invoke ID = 23
Opcode = 2
System Information Follows:
Vendor
: SISCO, Inc.
Model
: AXS4ICCP-132-095
Revision : 5.0000.0
2011-10-27 16:16:55.079 AXIC_LOG_NERR (Axicmi.c 509 0x000009c0)
'PrimaryLink':
Vendor: 'SISCO'
Model: 'ICCP-Lite'
Revision: '5.4000'
MMS Indication
Invoke ID = 24
Opcode = 13
Scope of Delete = 0,
Scope of Delete = 0, specific
Domain Name : Not Present
Variable Names : 1
Item Id: AllPoints
MMS Error Response
Invoke ID = 24
Service Error : Definition, Object Undefined
Problem Type : 2
Problem Code : 1
MMS Indication
Invoke ID = 25
Opcode = 11
Item Id: AllPoints
Variable 1)
Item Id: Transfer_Set_Name
Variable 2)
Item Id: Transfer_Set_Time_Stamp
Variable 3)
Item Id: DSConditions_Detected
175

Variable 4)
Item Id: Event_Code_Detected
Variable 5)
Item Id: ActualVoltage
Variable 6)
Item Id: GasOn
Variable 7)
Item Id: GasTurbineStatus
Variable 8)
Item Id: HourlyPlantMWH
Variable 9)
Item Id: Measurement_01
Variable 10)
Variable 11)
Variable 12)
Item Id: OverLimit_01
Variable 13)
Item Id: OverLimit_02
Variable 14)
Item Id: PlantStatus
Variable 15)
Item Id: Price_Rate_01
Variable 16)
Item Id: Price_Rate_02
Variable 17)
Item Id: SpareState_01
Variable 18)
Item Id: SpareState_02
176

Variable 19)
Item Id: SteamTurbineStatus
Variable 20)
Item Id: Temperature_01
Variable 21)
Item Id: Temperature_02
Variable 22)
Item Id: WaterOn
PDU Logging
This is hexadecimal ASN.1 logging do not turn on unless requested by SISCO.
***********************************************************
LOGGING STARTED Tue Jun 08 15:42:37 2004
***********************************************************
Tue Jun 08 15:42:37 2004 MVLLOG_ACSEDATA (mvl_acse.c 1659)
ACSE: Rx'd 419 bytes on MVL_NET_INFO 0x01996c7c
00000
A3 82 01 9F A0 82 01 9B
A0 82 01 12 30 1F A0 1D
*............0...*
00010
A1 1B 1A 06 49 43 43 50
5F 42 1A 11 54 72 61 6E
*....ICCP_B..Tran*
00020
73 66 65 72 5F 53 65 74
5F 4E 61 6D 65 30 25 A0
*sfer_Set_Name0%.*
00030
23 A1 21 1A 06 49 43 43
50 5F 42 1A 17 54 72 61
*#.!..ICCP_B..Tra*
00040
6E 73 66 65 72 5F 53 65
74 5F 54 69 6D 65 5F 53
*nsfer_Set_Time_S*
00050
74 61 6D 70 30 23 A0 21
A1 1F 1A 06 49 43 43 50
*tamp0#.!....ICCP*
00060
5F 42 1A 15 44 53 43 6F
6E 64 69 74 69 6F 6E 73
*_B..DSConditions*
00070
5F 44 65 74 65 63 74 65
64 30 1F A0 1D A1 1B 1A
*_Detected0......*
00080
06 49 43 43 50 5F 42 1A
11 4D 45 41 53 55 52 45
*.ICCP_B..MEASURE*
00090
4D 45 4E 54 5F 44 45 5F
30 31 30 1F A0 1D A1 1B
*MENT_DE_010.....*
000A0
1A 06 49 43 43 50 5F 42
1A 11 4D 45 41 53 55 52
*..ICCP_B..MEASUR*
000B0
45 4D 45 4E 54 5F 44 45
5F 30 32 30 1F A0 1D A1
*EMENT_DE_020....*
000C0
1B 1A 06 49 43 43 50 5F
42 1A 11 4D 45 41 53 55
*...ICCP_B..MEASU*
000D0
52 45 4D 45 4E 54 5F 44
45 5F 30 33 30 1F A0 1D
*REMENT_DE_030...*
000E0
A1 1B 1A 06 49 43 43 50
5F 42 1A 11 4D 45 41 53
*....ICCP_B..MEAS*
000F0
55 52 45 4D 45 4E 54 5F
44 45 5F 30 34 30 1F A0
*UREMENT_DE_040..*
00100
1D A1 1B 1A 06 49 43 43
50 5F 42 1A 11 4D 45 41
*.....ICCP_B..MEA*
00110
53 55 52 45 4D 45 4E 54
5F 44 45 5F 30 35 A0 81
*SUREMENT_DE_05..*
00120
82 A2 12 86 01 01 8A 06
49 43 43 50 5F 42 8A 05
*........ICCP_B..*
00130
44 53 54 53 30 85 04 40
C6 16 AD 84 02 03 20 A2
*DSTS0..@...... .*
00140
12 85 02 0B 56 85 04 40
C6 16 AD 84 02 00 56 86
*....V..@......V.*
00150
02 0B 56 A2 12 85 02 0B
56 85 04 40 C6 16 AD 84
*..V.....V..@....*
00160
02 00 56 86 02 0B 56 A2
12 85 02 0B 56 85 04 40
*..V...V.....V..@*
00170
C6 16 AD 84 02 00 56 86
02 0B 56 A2 12 85 02 0B
*......V...V.....*
00180
56 85 04 40 C6 16 AD 84
02 00 56 86 02 0B 56 A2
*V..@......V...V.*
177
MI Flow
Internal AX-S4 ICCP logging.
***********************************************************
LOGGING STARTED Wed Jun 09 08:24:35 2004
***********************************************************
Wed Jun 09 08:24:35 2004 SLOGALWAYS (AXICCB.C 80)
Product: AXS4ICCP-132-095, Version: 3.0155
Wed Jun 09 08:24:35 2004 AXIC_LOG_NERR (axicRed.c 1239)
NonRedundant node.
Wed Jun 09 08:24:35 2004 AXIC_LOG_ALWAYS (axs4iccp.cpp 1100)
Wed Jun 09 08:24:38 2004 AXIC_LOG_NERR (axicmi.c 500)
'PrimaryLink':
Vendor: 'SISCO'
Model: 'ICCP-Lite'
Revision: '5.0051'
Wed Jun 09 08:25:58 2004 MILOG_FLOW (Mis.c 1378)
Sending DSTS full interval report (DS AllPoints)
Including variable: ActualVoltage
Including variable: GasOn
Including variable: GasTurbineStatus
Including variable: HourlyPlantMWH
Including variable: Measurement_01
Including variable: OverLimit_01
Including variable: OverLimit_02
Including variable: PlantStatus
Including variable: Price_Rate_01
Including variable: Price_Rate_02
Including variable: SpareState_01
Including variable: SpareState_02
Including variable: SteamTurbineStatus
Including variable: Temperature_01
Including variable: Temperature_02
Including variable: WaterOn
Wed Jun 09 08:25:58 2004 MILOG_FLOW (Mis.c 1819)
Actual info report size: 258
178
MI MATCHING
Useful for diagnosing issues in the Identification form of the ICCP Configuration
Utility.
***********************************************************
LOGGING STARTED Mon Jun 14 14:32:00 2004
***********************************************************
Mon Jun 14 14:32:00 2004 SLOGALWAYS (AXICCB.C 80)
Mon Jun 14 14:32:00 2004 MILOG_ADDR (Axicmain.c 363)
AllowMissingAE
= No
AllowExtraAE
= No
LocalApTitle
= No
LocalAeQualifier = No
LocalApInvoke
= No
LocalAeInvoke
= No
LocalPsel
= Yes
LocalSsel
= Yes
LocalTsel
= Yes
LocalNetAddress = No
RemoteApTitle
= No
RemoteAeQualifier= No
RemoteApInvoke
= No
RemoteAeInvoke
= No
RemotePsel
= Yes
RemoteSsel
= Yes
RemoteTsel
= Yes
RemoteNetAddress = No
Mon Jun 14 14:32:01 2004 AXIC_LOG_NERR (axicRed.c 1239)
NonRedundant node.
Mon Jun 14 14:32:01 2004 AXIC_LOG_ALWAYS (axs4iccp.cpp 1100)
Mon Jun 14 14:32:06 2004 MILOG_ADDR (Mi.c 1887)
Association Indication: find the target Remote/Association
Looking at Remote 'UtilitySiteB'
Association 'PrimaryLink'
* Found matching association
Matched: Remote 'UtilitySiteB', Asociation 'PrimaryLink'
179
MI CONFIG
Useful for diagnosing general ICCP configuration issues.
***********************************************************
LOGGING STARTED Thu Jun 10 13:44:05 2004
***********************************************************
Thu Jun 10 13:44:05 2004 SLOGALWAYS (AXICCB.C 80)
Thu Jun 10 13:44:05 2004 ICFG_LOG_FLOW (IcfgDb.cpp 109)
Configuration Read Start
Thu Jun 10 13:44:05 2004 ICFG_LOG_FLOW (IccpDBA.cpp 87)
Opening ICCP Configuration Database ...
Thu Jun 10 13:44:05 2004 MILOG_CFG (MI_ICFG.C 141)
u_icfg_StartLocalCtrlCenter
LOCAL CONTROL CENTER Name:
UtilitySiteA
Maximum DSTS:
10
Maximum DS:
10
Maximum MMS PDU Size:
32000
u_icfg_StartLocalObjects
u_icfg_StartLocalDataValues total: 20
u_icfg_LocalDataValue
Local Data Value name:
GasOn
Local Data Value type:
StateExtended
Normal Source:
Telemetered
Map Info:
snip.
u_icfg_EndLocalDataValues
u_icfg_StartLocalDevices total: 10
u_icfg_LocalDevice
Local Device name:
BreakerA
180
Local Data Values Type:

Map Info:
Sbo Device:
Tag Enable:
Discrete
N
Y

u_icfg_LocalDevice
Local Device name:
BreakerB
Local Data Values Type:
State
Map Info:
Sbo Device:
N
Tag Enable:
Y
snip
u_icfg_EndLocalDevices
u_icfg_StartLocalInfoMsgs total: 6
u_icfg_LocalInfoMsg
LOCAL Info Msg:
1
Map Info:
Max Size:
128
snip
u_icfg_EndLocalInfoMsgs
u_icfg_EndLocalObjects
u_icfg_StartRemCCs total: 1
u_icfg_StartRemCC
REMOTE CONTROL CENTER Name:
UtilitySiteB
Bilateral Table Name:
BLT1
BiLatTblId:
SiteA_SiteB
Local Dom:
ICCP_A
Remote Dom:
ICCP_B
Shortest Interval:
1
Blocks:
0xd8000000
181
u_icfg_StartLinks total: 1
u_icfg_Link
Name:
PrimaryLink
Local Ar:
SiteA
Remote Ar[0]:
SiteB
Connect Role:
0x4
Service Role:
0x18
Retry Time:
10
Max Mms Pdu Size:
32000
Max Req Pend:
5
Max Ind Pend:
5
Max Nest:
5
Heartheat Time:
0
Logging Enable:
OFF
u_icfg_EndLinks total
u_icfg_StartServerObjs
NumVccDv:
0
NumVccDs:
0
NumIccDv:
20
NumIccDs:
0
Num VCC Dev:
0
Num ICC Dev:
6
Num VCC InfoMsgs: 0
Num ICC InfoMsgs: 4
u_icfg_StartServerDataValues total: 20
u_icfg_ServerDataValue
Server Data Value name:
ActualVoltage
Scope:
ICC
Server Data Value Type:
RealQ
Read Only:
Y
Map Info:
snip
u_icfg_EndServerDataValues
182
u_icfg_StartServerDevices total: 6
u_icfg_ServerDevice
Server Device name:
BreakerA
Scope:
ICC
Server Device type:
Real
Map Info:
u_icfg_ServerDevice
Server Device name:
BreakerB
Scope:
ICC
Server Device type:
Discrete
Map Info:
u_icfg_EndServerDevices
u_icfg_StartServerInfoMsgs total: 4
u_icfg_ServerInfoMsg
SERVER Info Ref:
1
Scope:
ICC
SERVER Info Ref:
3
Scope:
ICC
SERVER Info Ref:
5
Scope:
ICC
SERVER Info Ref:
7
Scope:
ICC
u_icfg_EndServerInfoMsgs
u_icfg_StartServerDataSets total: 0
u_icfg_EndServerDataSets
183

u_icfg_EndServerObjs
u_icfg_StartClientObjs
NumVccDv:
0
NumIccDv:
60
NumDs:
7
NumTsCtrl:
4
Num ICC Dev:
8
Num VCC Dev:
0
Num ICC InfoMsgs: 2
Num VCC InfoMsgs: 0
u_icfg_StartClientDataValues total: 60
u_icfg_ClientDataValue
Name:
MEASUREMENT_D_01
Scope:
ICC
Type:
Discrete
Read Only: N
Status:
OK
Map Info:
snip
u_icfg_EndClientDataValues
u_icfg_StartClientDevices total: 8
u_icfg_ClientDevice
CLIENT Device name: COMMAND_DEV_1
Scope:
ICC
Local Device Type: Real
Map Info:
Sbo:
N
Tag Enable:
Y
snip
u_icfg_EndClientDevices
184

u_icfg_StartClientInfoMsgs total: 2
u_icfg_ClientInfoMsg
CLIENT Data Value name:
2
Scope:
ICC
Map Info:
Max Size:
500
u_icfg_EndClientInfoMsgs
u_icfg_StartClientDataSets total: 7
u_icfg_ClientDataSet
CLIENT Data Set name:
DiscreteMeasurements
Num Dv:
15
0) MEASUREMENT_D_01
ICC
1) MEASUREMENT_D_02
ICC
2) MEASUREMENT_D_03
ICC
3) MEASUREMENT_D_04
ICC
4) MEASUREMENT_D_05
ICC
5) MEASUREMENT_DQ_01
ICC
ICC
ICC
ICC
ICC
10) MEASUREMENT_DQTT_01
ICC
ICC
ICC
ICC
ICC
snip
u_icfg_EndClientDataSets
u_icfg_StartClientDSTSs total: 4
u_icfg_ClientDSTS
CLIENT DS Transfer Set name: DS_AUTO_DISCRETE_0001
Association:
PrimaryLink
Interval:
10
Rbe:
Y
185
Buf Time:
Integrity:
Start Time:
Critical:
DSConditions Requested:
Integrity: Y
Interval: N
Change: Y
snip
2
30
0
N

u_icfg_EndClientDSTSs
Thu Jun 10 13:44:05 2004
u_icfg_Discovery
Enable
Association
GetNameList
GetvaaCfgDv
GetvaaNewDv
ReadCfgDv
ReadNewDv
NewDvReadOnly
RtExcludeMissing
RtExcludeMistyped
RtExcludeReadError
RtAddNew
DbAddNew
DbDeleteMissing
DbCorrectMistyped
DbAutoAccept
WriteXml
ExecuteOnce
ExecuteAlways
MILOG_CFG (MI_ICFG.C 1661)

:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
Y
PrimaryLink
N
N
Y
Y
N
Y
Y
Y
Y
N
Y
Y
Y
N
N
N
N
Thu Jun 10 13:44:05 2004 MILOG_CFG

u_icfg_ClientAutoDSTS
Association
: PrimaryLink
Assign By Type : Y
Real, Enable: Y
DataSet Parameters
Scope:
MaxDstsPduSize:
MaxDvPerDs :
Conservative:
Transfer_Set_Name:
Transfer_Set_Time_Stamp:
186
(MI_ICFG.C 1707)
VCC
32000
200
N
Y
Y
DSConditions_Detected:
Event_Code_Detected:
DSTS Parameters
Interval:
Rbe:
Buf Time:
Integrity:
Start Time:
Critical:
DSConditions Requested:
Integrity:
Interval:
Change:
Thu Jun 10 13:44:05 2004 MILOG_CFG
u_icfg_EndClientObjs
Y
N
10
Y
2
30
0
N
Y
N
Y
(MI_ICFG.C 1280)

u_icfg_EndRemCC
u_icfg_EndRemCC
u_icfg_EndLocalCtrlCenter
Thu Jun 10 13:44:05 2004 ICFG_LOG_FLOW (IccpDBA.cpp 137)
Closing ...
Thu Jun 10 13:44:05 2004 ICFG_LOG_FLOW (IcfgDb.cpp 119)
Configuration Read Complete
AX-S4 ICCP FLOW

Shows general processing information.
***********************************************************
***********************************************************
Mon Jun 14 14:49:16 2004 AXIC_LOG_FLOW (Axicmain.c 145)
Reading DataBase for LocalControlCenter UtilitySiteA
Mon Jun 14 14:49:16 2004 AXIC_LOG_FLOW (axicRed.c 80)
Initiating Redundancy Support.
187

NonRedundant node.
Mon Jun 14 14:49:16 2004 AXIC_LOG_FLOW (axicRed.c 97)
axicRedInit: node is not redundant.
Mon Jun 14 14:49:16 2004 AXIC_LOG_FLOW (axicopc.cpp 41)
Starting AX-S4 ICCP OPC Server
Mon Jun 14 14:49:24 2004 AXIC_LOG_FLOW (axicmi.c 675)
CreateDataSets for Link PrimaryLink
Mon Jun 14 14:49:24 2004 AXIC_LOG_FLOW (AXICCB.C 141)
Link PrimaryLink Is UP
Mon Jun 14 14:49:24 2004 AXIC_LOG_NERR (axicmi.c 500)
'PrimaryLink':
Vendor: 'SISCO'
Model: 'ICCP-Lite'
Revision: '5.0051'
CreateDataSets for Link PrimaryLink
snip
Start all data set transfer sets for Link PrimaryLink
Start all data set transfer sets for Link PrimaryLink
snip
Mon Jun 14 14:51:41 2004 AXIC_LOG_ICCP (AXICCB.C 340)
Received DSTS Report for data set DS_AUTO_DISCRETE_0001
DSTS Report for data set DS_AUTO_DISCRETE_0001 DONE
Sending Transfer Report DSTS0 to Remote VCC UtilitySiteB
Received DSTS Report for data set DS_AUTO_REAL_0001
188
AX-S4 ICCP OPC

General information on OPC groups and items.
***********************************************************
***********************************************************
Wed Jun 09 08:56:19 2004 AXIC_LOG_OPC (Opcgroup.cpp 376)
OPCGroup 'frmDspLLog'::DoUpdateGroup
OPCGroup 'frmMain'::DoUpdateGroup
189
AX-S4 ICCP DEBUG

***********************************************************
***********************************************************
Product:
AXS4ICCP-132-095, Version: 3.0155

NonRedundant node.
Mon Jun 14 14:56:55 2004 AXIC_LOG_OPCDEBUG (iccp.cpp 781)
EnumObjects for groupType 0
GetPathName for groupType 0
GetPathName for groupType 0
Identify Response for Remote 'UtilitySiteB', Association 'PrimaryLink':
Vendor:
Model:
Revision:
'SISCO'
'ICCP-Lite'
'5.0051'
Mon Jun 14 14:56:57 2004 MILOG_DEBUG (Mi_size.c 124)

Calculating information report size
Added overhead: 26
Added NVL name: 65
Added seq of data cstr overhead: 73
Added DV 0 data: 86
Added DV 1 data: 103
190

ASN.1 Decode
Do not turn on unless requested by SISCO.
***********************************************************
***********************************************************
Wed Jun 09 09:01:44 2004 ASN1_LOG_DEC (asn1r.c 217)
ASN.1 MESSAGE TO DECODE : len = 337
00000
A3 82 01 4D A0 82 01 49
A1 21 A1 1F 1A 06 49 43
*...M...I.!....IC*
00010
43 50 5F 42 1A 15 44 53
5F 41 55 54 4F 5F 44 49
*CP_B..DS_AUTO_DI*
00020
53 43 52 45 54 45 5F 30
30 30 31 A0 82 01 22 A2
*SCRETE_0001...".*
00030
12 86 01 01 8A 06 49 43
43 50 5F 42 8A 05 44 53
*......ICCP_B..DS*
00040
54 53 30 85 04 40 C7 0A
38 84 02 03 20 85 03 13
*TS0..@..8... ...*
00050
A5 9C 85 03 13 A5 9C 85
03 13 A5 9C 85 03 13 A5
*................*
00060
9C 85 03 13 A5 9C A2 12
85 02 08 FF 85 04 40 C7
*..............@.*
00070
0A 38 84 02 00 FF 86 02
08 FF A2 12 85 02 08 FF
*.8..............*
00080
85 04 40 C7 0A 38 84 02
00 FF 86 02 08 FF A2 12
*..@..8..........*
00090
85 02 08 FF 85 04 40 C7
0A 38 84 02 00 FF 86 02
*......@..8......*
000A0
08 FF A2 12 85 02 08 FF
85 04 40 C7 0A 38 84 02
*..........@..8..*
000B0
00 FF 86 02 08 FF A2 12
85 02 08 FF 85 04 40 C7
*..............@.*
000C0
0A 38 84 02 00 FF 86 02
08 FF A2 09 85 03 03 8A
*.8..............*
000D0
72 84 02 00 A6 A2 09 85
03 03 8A 72 84 02 00 A6
*r..........r....*
000E0
A2 09 85 03 03 8A 72 84
02 00 A6 A2 09 85 03 03
*......r.........*
000F0
8A 72 84 02 00 A6 A2 09
85 03 03 8A 72 84 02 00
*.r..........r...*
00100
A6 A2 0E 85 02 7D 82 85
04 40 C7 0A 38 84 02 00
*.....}...@..8...*
00110
A6 A2 0E 85 02 7D 82 85
04 40 C7 0A 38 84 02 00
*.....}...@..8...*
00120
A6 A2 0E 85 02 7D 82 85
04 40 C7 0A 38 84 02 00
*.....}...@..8...*
00130
A6 A2 0E 85 02 7D 82 85
04 40 C7 0A 38 84 02 00
*.....}...@..8...*
00140
A6 A2 0E 85 02 7D 82 85
04 40 C7 0A 38 84 02 00
*.....}...@..8...*
00150
A6
*.*
Wed Jun 09 09:01:44 2004 ASN1_LOG_DEC (asn1r.c 226)

Current decode offset: 0x00014
00000
1A 15 44 53 5F 41 55 54
00010
54 45 5F 30 30 30 31
4F 5F 44 49 53 43 52 45
*..DS_AUTO_DISCRE*
*TE_0001*
Element : Univ, Prim, ID = 26, Len = 21

Level 4 parse complete
Level 3 parse complete
191
ASN.1 Encode
Do not turn on unless requested by SISCO.
***********************************************************
***********************************************************
Wed Jun 09 09:12:13 2004 ASN1_LOG_ENC (asn1r.c 776)
Starting ASN.1 message construct
Starting constructor @ level 1
Finish primitive
00000
84 02 00 31
*...1*
Finish primitive
00000
87 05 08 00 00 00 00
*.......*
Finish level 1 constructor

Length = 13
00000
A2 0B 87 05 08 00 00 00
00 84 02 00 31
*............1*
Wed Jun 09 09:12:13 2004 ASN1_LOG_ENC (asn1r.c 776)

Starting ASN.1 message construct
Starting constructor @ level 1
ACSE Flow
Useful for diagnosing connection issues such as selectors.
***********************************************************
***********************************************************
Product:
Mon Jun 14 15:00:41 2004 SUIC_LOG_IND (marbutil.c 225)

pt_mb_or () opened 'suic11244.mbx'
Mon Jun 14 15:00:41 2004 SUIC_LOG_IND (marbutil.c 247)
pt_mb_ow () opened 'osill2.mbx'
Mon Jun 14 15:00:41 2004 SUIC_LOG_CNF (marb_tx.c 308)
Activate Request for 'SiteA'
Sharable = FALSE
Presentation Selector:
00000
00 00 00 05
*....*
Session Selector:
00000
00 01
*..*
Transport Selector:
00000
00 01
Network Address (IP): 127.0.0.1
192
*..*
Mon Jun 14 15:00:41 2004 SUIC_LOG_IND (marb_rx.c 586)

Register Confirm received for SiteA
Listen Request issued on channel 0 for 'SiteA'
NonRedundant node.
Associate Indication received for SAP #15
Associate Indication accepted on channel 0
Local AR Name: 'SiteA'
Application Context = 8
Presentation Context List:
Context ID = 3
ASN Mask = 1
Calling AP Title = [ 1 3 9999 1 ]
Calling AP Invoke ID not present
Calling AE Qualifier = 1
Calling AE Invoke ID not present
Called AP Title = [ 1 3 9999 2 ]
Called AP Invoke ID not present
Called AE Qualifier = 2
Called AE Invoke ID not present
Calling Authentication Mechanism Name not present
Calling Authentication Value not present
Calling Presentation Selector:
00000
00 00 00 06
*....*
Calling Session Selector:

00000
00 01
*..*
Calling Transport Selector:

00000
00 01
*..*
Calling Encryption: NONE

Calling Cipher Suite: 000000
Calling Certificate Matched: NO
Calling Network Address (IP): 127.0.0.1
Called Presentation Selector:
00000
00 00 00 05
*....*
Called Session Selector:

00000
00 01
*..*
Called Transport Selector:

00000
00 01
*..*
Called Network Address (IP): 127.0.0.1
193
39 bytes of User Information received

00000
A8 25 80 02 7D 00 81 01
05 82 01 05 83 01 05 A4
*.%..}...........*
00010
16 80 01 01 81 03 05 E1
00 82 0C 03 6E 1C 00 00
*............n...*
00020
00 00 00 00 00 01 10
*.......*

Associate Response issued on channel 0
AP Context Mask = 8
Responding AP Title = [ 1 3 9999 2 ]
Responding AP Invoke ID not present
Responding AE Qualifier = 2
Responding AE Invoke ID not present
Presentation Context List:
Context ID = 3
ASN Mask = 1
Responding Authentication Mechanism Name not present
Responding Authentication Value not present
39 bytes of User Information sent
00000
A9 25 80 02 7D 00 81 01
05 82 01 05 83 01 05 A4
*.%..}...........*
00010
16 80 01 01 81 03 05 E1
00 82 0C 03 6E 1C 00 00
*............n...*
00020
00 00 00 00 00 01 10
*.......*

88 bytes of User Data sent on channel 0
00000
A0 56 02 01 01 A4 51 A1
4F A0 4D 30 20 A0 1E A1
*.V....Q.O.M0 ...*
00010
1C 1A 06 49 43 43 50 5F
42 1A 12 42 69 6C 61 74
*...ICCP_B..Bilat*
00020
65 72 61 6C 5F 54 61 62
6C 65 5F 49 44 30 16 A0
*eral_Table_ID0..*
00030
14 80 12 53 75 70 70 6F
72 74 65 64 5F 46 65 61
*...Supported_Fea*
00040
74 75 72 65 73 30 11 A0
0F 80 0D 54 41 53 45 32
*tures0.....TASE2*
00050
5F 56 65 72 73 69 6F 6E
*_Version*

Ready Indication received on channel 0
Data Transfer Indication received on channel 0
Fragment length (1) = 88
EOM detected
88 bytes of User Data received
00000
A0 56 02 01 32 A4 51 A1
4F A0 4D 30 20 A0 1E A1
*.V..2.Q.O.M0 ...*
00010
1C 1A 06 49 43 43 50 5F
41 1A 12 42 69 6C 61 74
*...ICCP_A..Bilat*
00020
65 72 61 6C 5F 54 61 62
6C 65 5F 49 44 30 16 A0
*eral_Table_ID0..*
00030
14 80 12 53 75 70 70 6F
72 74 65 64 5F 46 65 61
*...Supported_Fea*
00040
74 75 72 65 73 30 11 A0
0F 80 0D 54 41 53 45 32
00050
5F 56 65 72 73 69 6F 6E
194
*tures0.....TASE2*
*_Version*
ACSE Data
ACSE info with PDU logging.
***********************************************************
***********************************************************
2011-10-27 16:19:26.878 SW_LOCK_FLOW (SwLock.cpp 300 0x00000178)
2011-10-27 16:19:26.909 SLOGALWAYS (Axiccb.c 111 0x00000178)
Product: AXS4ICCP-132-095, Version: 5.0000.0
2011-10-27 16:19:27.519 AXIC_LOG_ALWAYS (axs4iccp.cpp 807 0x00000178)
2011-10-27 16:19:27.753 AXIC_LOG_NERR (Iccp.cpp 1604 0x00000598)
00000 A8 25 80 02 7D 00 81 01 05 82 01 05 83 01 05 A4 *...}........*
00010 16 80 01 01 81 03 05 E1 00 82 0C 03 6E 1C 00 00 *..........n...*
00020 00 00 00 00 00 01 10
*.......*
00000 A9 25 80 02 7D 00 81 01 05 82 01 05 83 01 05 A4 *...}........*
00010 16 80 01 01 81 03 05 E1 00 82 0C 03 6E 1C 00 00 *..........n...*
00020 00 00 00 00 00 01 10
*.......*
2011-10-27 16:19:30.581 MVLLOG_ACSEDATA (mvl_acse.c
ACSE: Sending 88 bytes on MVL_NET_INFO 0x0242BDFC
00000 A0 56 02 01 01 A4 51 A1 4F A0 4D 30 20 A0
00010 1C 1A 06 49 43 43 50 5F 42 1A 12 42 69 6C
00020 65 72 61 6C 5F 54 61 62 6C 65 5F 49 44 30
00030 14 80 12 53 75 70 70 6F 72 74 65 64 5F 46
00040 74 75 72 65 73 30 11 A0 0F 80 0D 54 41 53
00050 5F 56 65 72 73 69 6F 6E
ACSE: Rx'd 88 bytes on MVL_NET_INFO 0x0242BDFC
00000 A0 56 02 01 1D A4 51 A1 4F A0 4D 30 20 A0
00010 1C 1A 06 49 43 43 50 5F 41 1A 12 42 69 6C
00020 65 72 61 6C 5F 54 61 62 6C 65 5F 49 44 30
00030 14 80 12 53 75 70 70 6F 72 74 65 64 5F 46
00040 74 75 72 65 73 30 11 A0 0F 80 0D 54 41 53
00050 5F 56 65 72 73 69 6F 6E
743 0x000009c4)
1E
61
16
65
45
A1
74
A0
61
32
* V...QO M0 .*
*...ICCP_B..Bilat*
*eral_Table_ID0. *
*...Supported_Fea*
*tures0. ...TASE2*
*_Version*
1719 0x000009c4)
1E
61
16
65
45
A1
74
A0
61
32
* V...QO M0 .*
*...ICCP_A..Bilat*
*eral_Table_ID0. *
*...Supported_Fea*
*tures0. ...TASE2*
*_Version*
2011-10-27 16:19:30.613 MVLLOG_ACSEDATA (mvl_acse.c 743 0x000009c4)

00000 A1 22 02 01 1D A4 1D A1 1B 8A 0B 53 69 74 65 41 *"......SiteA*
00010 5F 53 69 74 65 42 84 03 04 D8 00 A2 07 85 02 07 *_SiteB......*
00020 D0 85 01 08
*..*
00000 A1 22 02 01 01 A4 1D A1 1B 8A 0B 53 69 74 65 41 *"......SiteA*
00010 5F 53 69 74 65 42 84 03 04 D8 00 A2 07 85 02 07 *_SiteB......*
00020 D0 85 01 08
*..*
00000 A0 05 02 01 02 82 00
* .....*
00000 A0 27 02 01 03 AD 22 A1 20 A1 1E 1A 06 49 43 43 * '..." ...ICC*
00010 50 5F 42 1A 14 45 78 74 65 6E 64 65 64 4D 65 61 *P_B..ExtendedMea*
00020 73 75 72 65 6D 65 6E 74 73
*surements*
195

00000 A0 05 02 01 1E 82 00
00000 A1 2E 02 01 1E A2 29 80 0B 53 49 53 43 4F
00010 49 6E 63 2E 81 10 41 58 53 34 49 43 43 50
00020 33 32 2D 30 39 35 82 08 35 2E 30 30 30 30
* .....*
743 0x000009c4)
2C 20
2D 31
2E 30
*....)..SISCO, *
*Inc...AXS4ICCP-1*
*32-095.5.0000.0*

00000 A1 1F 02 01 02 A2 1A 80 05 53 49 53 43 4F 81 09 *.......SISCO. *
00010 49 43 43 50 2D 4C 69 74 65 82 06 35 2E 34 30 30 *ICCP-Lite.5.400*
00020 30
*0*
2011-10-27 16:19:30.675 AXIC_LOG_NERR (Axicmi.c 509 0x000009c4)
Vendor: 'SISCO'
Model: 'ICCP-Lite'
Revision: '5.4000'
00000 A1 0B 02 01 03 AD 06 80 01 01 81 01 01
*...........*
00000 A0 82 02 87 02 01 04 AB 82 02 80 A1 1E 1A 06 49 * .........I*
00010 43 43 50 5F 42 1A 14 45 78 74 65 6E 64 65 64 4D *CCP_B..ExtendedM*
00020 65 61 73 75 72 65 6D 65 6E 74 73 A0 82 02 5C 30 *easurements .\0*
00030 1F A0 1D A1 1B 1A 06 49 43 43 50 5F 42 1A 11 54 *. ....ICCP_B..T*
00040 72 61 6E 73 66 65 72 5F 53 65 74 5F 4E 61 6D 65 *ransfer_Set_Name*
00050 30 25 A0 23 A1 21 1A 06 49 43 43 50 5F 42 1A 17 *0. #!..ICCP_B..*
00060 54 72 61 6E 73 66 65 72 5F 53 65 74 5F 54 69 6D *Transfer_Set_Tim*
00070 65 5F 53 74 61 6D 70 30 23 A0 21 A1 1F 1A 06 49 *e_Stamp0# !...I*
00080 43 43 50 5F 42 1A 15 44 53 43 6F 6E 64 69 74 69 *CCP_B..DSConditi*
00090 6F 6E 73 5F 44 65 74 65 63 74 65 64 30 1F A0 1D *ons_Detected0. .*
000A0 A1 1B 1A 06 49 43 43 50 5F 42 1A 11 4D 45 41 53 *...ICCP_B..MEAS*
000B0 55 52 45 4D 45 4E 54 5F 44 45 5F 30 31 30 1F A0 *UREMENT_DE_010. *
000C0 1D A1 1B 1A 06 49 43 43 50 5F 42 1A 11 4D 45 41 *....ICCP_B..MEA*
000D0 53 55 52 45 4D 45 4E 54 5F 44 45 5F 30 32 30 1F *SUREMENT_DE_020.*
000E0 A0 1D A1 1B 1A 06 49 43 43 50 5F 42 1A 11 4D 45 * ....ICCP_B..ME*
000F0 41 53 55 52 45 4D 45 4E 54 5F 44 45 5F 30 33 30 *ASUREMENT_DE_030*
00100 1F A0 1D A1 1B 1A 06 49 43 43 50 5F 42 1A 11 4D *. ....ICCP_B..M*
00110 45 41 53 55 52 45 4D 45 4E 54 5F 44 45 5F 30 34 *EASUREMENT_DE_04*
00120 30 1F A0 1D A1 1B 1A 06 49 43 43 50 5F 42 1A 11 *0. ....ICCP_B..*
00130 4D 45 41 53 55 52 45 4D 45 4E 54 5F 44 45 5F 30 *MEASUREMENT_DE_0*
00140 35 30 1F A0 1D A1 1B 1A 06 49 43 43 50 5F 42 1A *50. ....ICCP_B.*
00150 11 4D 45 41 53 55 52 45 4D 45 4E 54 5F 52 45 5F *.MEASUREMENT_RE_*
00160 30 31 30 1F A0 1D A1 1B 1A 06 49 43 43 50 5F 42 *010. ....ICCP_B*
00170 1A 11 4D 45 41 53 55 52 45 4D 45 4E 54 5F 52 45 *..MEASUREMENT_RE*
00180 5F 30 32 30 1F A0 1D A1 1B 1A 06 49 43 43 50 5F *_020. ....ICCP_*
00190 42 1A 11 4D 45 41 53 55 52 45 4D 45 4E 54 5F 52 *B..MEASUREMENT_R*
001A0 45 5F 30 33 30 1F A0 1D A1 1B 1A 06 49 43 43 50 *E_030. ....ICCP*
001B0 5F 42 1A 11 4D 45 41 53 55 52 45 4D 45 4E 54 5F *_B..MEASUREMENT_*
001C0 52 45 5F 30 34 30 1F A0 1D A1 1B 1A 06 49 43 43 *RE_040. ....ICC*
001D0 50 5F 42 1A 11 4D 45 41 53 55 52 45 4D 45 4E 54 *P_B..MEASUREMENT*
001E0 5F 52 45 5F 30 35 30 1F A0 1D A1 1B 1A 06 49 43 *_RE_050. ....IC*
001F0 43 50 5F 42 1A 11 4D 45 41 53 55 52 45 4D 45 4E *CP_B..MEASUREMEN*
00200 54 5F 53 45 5F 30 31 30 1F A0 1D A1 1B 1A 06 49 *T_SE_010. ....I*
00210 43 43 50 5F 42 1A 11 4D 45 41 53 55 52 45 4D 45 *CCP_B..MEASUREME*
00220 4E 54 5F 53 45 5F 30 32 30 1F A0 1D A1 1B 1A 06 *NT_SE_020. ....*
00230 49 43 43 50 5F 42 1A 11 4D 45 41 53 55 52 45 4D *ICCP_B..MEASUREM*
00240 45 4E 54 5F 53 45 5F 30 33 30 1F A0 1D A1 1B 1A *ENT_SE_030. ...*
00250 06 49 43 43 50 5F 42 1A 11 4D 45 41 53 55 52 45 *.ICCP_B..MEASURE*
00260 4D 45 4E 54 5F 53 45 5F 30 34 30 1F A0 1D A1 1B *MENT_SE_040. ..*
00270 1A 06 49 43 43 50 5F 42 1A 11 4D 45 41 53 55 52 *..ICCP_B..MEASUR*
00280 45 4D 45 4E 54 5F 53 45 5F 30 35
*EMENT_SE_05*
196
ACSE DECODE
Mon Jun 14 15:03:57 2004 ACSE_LOG_DEC (acse3dec.c 503)
A-DATA.ind:
acse_conn =0x19987EC, chan=0
User data length: 337

Mon Jun 14 15:03:57 2004 ACSE_LOG_DEC (acse3enc.c 999)
A-DATA.req done:
acse_conn =0x19987EC, chan=0, SUIC retcode=0

A-DATA.ind:

A-DATA.ind:

A-DATA.ind:
ACSE MVL
***********************************************************
***********************************************************
Product:
Mon Jun 14 15:08:53 2004 MVLLOG_ACSE (mvl_acse.c 411)

ACSE: Starting
ACSE: binding local name 'SiteA'
ACSE: bind OK
ACSE: Start complete, returning '0x0'
NonRedundant node.
197

ACSE: Associate Indication received
Using MVL_NET_INFO 01996cb4
Accepting the connection
Vendor:
Model:
Revision:
198
'SISCO'
'ICCP-Lite'
'5.0051'
Appendix B: Troubleshooting
Appendix B
Troubleshooting
Problems establishing an Association
Note: If AX-S4 ICCP is unable to establish an association with a remote control
center that has been configured, check the configured values for Bilateral
Table ID, Local Domain, and Remote Domain. These fields must be
consistent with data at the remote control center in order to establish an
association.
RPL Configuration Issues

RPL Configuration errors are listed in the axs4iccp.log file with a numeric number.
Below is a description of possible RPL error codes:
#define S_SEAL_KEYSEL
1
#define S_SEAL_BUFSIZE_REMAINDER
2
#define S_SEAL_ECRC_MISMATCH
3
#define S_SEAL_CRC_MISMATCH
4
#define S_SEAL_DATA_CRC_MISMATCH
5
#define S_SEAL_TIME_WINDOW
6
For example, the following error in the log file indicates that there is a time
discrepancy between the Primary and Secondary AX-S4 ICCPs indicating that the PC
clocks on both machines are out of time sync by more than the 10 second RPL
heartbeat rate:
2009-11-03 09:14:05.734 RPL_LOG_ERR (rpl.c 1246)
RPL Authentication Failure, Seal: 6, Disabling
2009-11-03 09:14:05.734 RPL_LOG_ERR (rpl.c 828)
Message integrity checks failed
This is the most common RPL error.
199
200
Appendix C: Advanced Topics
Appendix C
Advanced Topics
This appendix addresses AX-S4 ICCP advanced programming issues.
AX-S4 ICCP Registry Parameters

This section describes AX-S4 ICCP Registry parameters.
Under the HKEY_LOCAL_MACHINE\SOFTWARE\SISCO\AX-S4
ICCP\CurrentVersion\Tuning:
DataThreadPriority
The thread priority for the AX-S4 ICCP database

thread. default is
THREAD_PRIORITY_BELOW_NORMAL (-1).
STxQueSize
Transmit queue size. The default is 10.
OSI Stack Registry

Parameters
This section describes OSI Stack Registry parameters.
Under the HKEY_LOCAL_MACHINE\SOFTWARE\SISCO\Osill2\
CurrentVersion\Parameters:
LoadWinsock
If set to 0, this parameter will cause the OSI Stack

not to attempt to load the Winsock DLL. The
default is 1.
PriorityClass
Priority Class of the OSI Stack process. The

default is Normal Priority (0x20).
Priority
Priority within the Priority Class. The default is 0.
RunHidden
If set to 1, this parameter will cause the OSI Stack

to run hidden (i.e., the OSI Stack icon will not
appear on the taskbar).
201
202
UseKeepAlive
This parameter instructs the OSI Stack to enable

the TCP/IP keepalive timer. The default is 1.
WinsockLoadTime
This parameter indicates how long in seconds the

OSI Stack should wait before proceeding after the
Winsock DLL is loaded.
Appendix D: Stack Configuration
Appendix D
Stack Configuration
All necessary addressing information is handled through the ICCP Configuration
Utility. Using this Configuration Utility should only done if instructed by SISCO
Technical Support
Using Database Configuration

The following steps must be performed to configure a MMS node:
1.
Define the Host Names and associate them with a network address and/or
an IP Address.
1.
For each Host Name, define the AR Names for applications on that Host.
2.
For each Host Name that is intended to run with a SISCO OSI Stackbased product such as AX-S4 ICCP, you must configure the OSI
parameters.
Configuration Utility
The Configuration Utility consists of three major components:
The Network Configuration is used to set up the SISCO Stack. This

includes configuring Host Names, AR Names, and OSI Stack parameters.
Local configuration is used to set the Local Host and set the Local
Database Path.
To use the Configuration Utility, click on Stack Configuration in the SISCO

Stack folder. At this point, you can create, delete, and modify the OSI
configuration data. Most of this data is optional. The only requirement is that
the Network Address or the IP Address for the default local Host Name be
configured.
After changes have been saved, exit out of the Configuration Utility. The
SISCO OSI Stack can then be restarted.
File Options
203
Below is an explanation of the available menu options for File:

Open brings up a screen allowing you to open a configuration database file.
Print brings up a Print screen.
Generate Stack Config File allows you to create an osill2.cfg file for a
selected Host Name.
Convert Configuration Database will update the database to the latest
level.
Compact Database will reclaim space from deleted records in any
Microsoft Access database.
Exit quits the Configuration Utility.
Configuration Menu
Network\Addressing is used to configure Host Names and AR Names.
Network\OSI Routing is used to configure static routing.
Network\OSI Stack Parameters is used to configure subnetwork, transport, and
stack logging.
Directory is used to configure support for X.500 and/or LDAP directory services. No
longer supported.
Local\Database is used to set the Local Database Path.
Local\Host Name is used to set the Local Host.
All of these choices are described in more detail in following sub-sections.
If Network\Addressing is selected the program will bring up a screen similar to
that below which can be used to enter or alter configuration parameters.
204
Figure 28: SISCO OSI Stack Configuration Screen

The following items are common to some of the database configuration
screens:
Close shuts the current screen and returns to the main screen. If changes have
been made, the Configuration Utility will ask if you want the changes saved.
Refresh updates the list of records
Goto allows going to another record in the list.
Advanced/Basic exposes/hides advanced parameters.
New allows entering a new record into the configuration database.
Duplicate copies the data from the current record and allows you to edit the
newly created record.
Delete deletes the entire record from the configuration database.
Save saves the changes made to the database.
Cancel abandons all changes made to the record under configuration.
205
Options Menu
Confirm Actions will be set as the default. A confirmation message will
appear on the screen if there is any attempt to delete or change a record.
Use Wizards will be set as the default. The wizards will help you in creating
new records or duplicating records for Host Names, AR Names, Named
Types, Local Variables, Information Report Variables, Item Aliases, and the
SISCO OSI Stack configuration.
Configuring Host Names and Addresses

Please review the Multiple Ethernet adapters and TCP/IP section for more
information. To configure the required Host Names and associated addresses:
1.
Select Network from the Configuration menu.
2.
Click on Addressing to bring up the Network Addressing screen.
3.
Click on the Host Names tab.
Parameters shown on this screen are:
Host Name
Associates a Network Address and/or IP Address with a human-readable string.
Network Address
This is an octet string that represents an OSI Network Address (NSAP). The
maximum length is 20 octets (40 ACSII encoded hex digits).
IP Address
An IP Address can be specified either as a dotted decimal (e.g., 209.69.22.3) or as a
host name. The host name must be configured in the hosts file.
Note: Either a Network Address or an IP Address is required. Network
Addresses (NSAPs) are no longer supported.
Local Host
Configuring AR Names
206
To configure required AR Names for MMS devices and applications:

1.
2.
Click on Addressing to bring up the Network Addressing screen.
3.
Click on the AR Names folder.
All MMS devices and applications with which communication is required must be
configured.
See Addressing Issues in Appendix A for an explanation of AR Name, AP Title, AP
Invoke ID, AE Qualifier, AE Invoke ID, Psel, Ssel, and Tsel. Note that AP Title, AP
Invoke ID, AE Qualifier, and AE Invoke ID are optional and only appear if you click
on the Advanced button.
207
Other parameters shown on this screen are:
AR Name
Application Reference Name
Comment
Transport
Shared (Locally)
PSEL
This is the Presentation Selector. This field is optional. Only one local AR
Name can be configured without a PSEL, SSEL, and TSEL. The maximum
PSEL size is 16 octets (32 ASCII encoded hex digits).
SSEL
This is the Session Selector. This field is optional. Only one local AR Name
can be configured without a PSEL, SSEL, and TSEL. The maximum SSEL
size is 16 octets (32 ASCII encoded hex digits).
TSEL
This is the Transport Selector. This field is optional. A maximum number of 8
different transport selectors can be configured. Only one local AR Name can
be configured without a PSEL, SSEL, and TSEL. The maximum TSEL size is
32 octets (64 ASCII encoded hex digits).
208
AP Title
The AP Title is an Object Identifier, assigned by the network naming
authority, representing the Application Process Title for your particular
application process. An Object Identifier is a sequence of integer values
representing an application in the OSI Model. The first value in the AP Title
should be 1 (ISO) (the valid range is 0 to 2). The second value should be 1, 2,
or 3 (the valid range is 0 to 39). The third value is open for international
assignment. If your addressing is local, then this value should be 9999. The
rest of the values are arbitrary. For example, values could be assigned to
represent type and location of the application.
AP Invoke ID
This is an optional integer value used to identify an Invocation Instance of the
Application Process. The use of this parameter is currently not well defined
and therefore is discouraged.
AE Qualifier
AE Invoke ID
Application Entity. The use of this parameter is currently not well defined and
therefore is discouraged.
Configuring OSI Routing no longer supported
Configuring the Subnetwork no longer supported
Configuring the Transport Layer no longer supported
Configuring the Stack Logging Level

This screen, along with the logging information stored in the Registry, allows
you to enable and configure Stack logging on a per Host Name basis. If any of
the logging options are checked for the current local Host Name configured,
logging will be enabled to a text file called osill2d.log found in the \OSILL2
directory. This file can be examined using a text editor such as Notepad. The
logging option defaults are no checks (no logging enabled). To configure the
Stack Logging Level:
1.
2.
Click on OSI Stack Parameters to bring up the Network

209
Configuration dialog box.

3.
Click on the Stack Logging tab. The following parameters are shown on
this screen:
ACSE
If this box is checked, all ACSE activity will be logged to the log file.
Session
If this box is checked, all Session activity will be logged to the log file.
Presentation
If this box is checked, all Presentation activity will be logged to the log
file.
Low Interface
If this box is checked, all activity between the OSI Stack and the network
driver will be logged to the log file.
High Interface
If this box is checked, all activity between the OSI Stack and the
Application Layer will be logged to the log file.
Transport
If this box is checked, all Transport activity will be logged to the log file.
Errors
If this box is checked, error information will be logged to the stack log
file.
Debug
If this box is checked, debug information will be logged to the stack log
file.
OSI Stack Registry Logging Values

The following values can be set in the Logging key of the OSILL2 Registry
using the Registry editor. The key is HKEY_LOCAL_MACHINE\
SOFTWARE\SISCO\OSILL2\CurrentVersion\Logging.
LogFileEn
210
Specifies whether file logging is to be enabled. The default

is 1.
LogFile
Specifies the path name of the log file. The default is

osill2d.log.
LogSize
Specifies the size of the log file in kilobytes. The default is

1000.
Timing
Specified type of timestamp to use. Valid choices are:

0
1 (Default)
2
HardFlush
No timestamp
Date and Time
Millisecond differential time
If set, instructs the logging facility to open and close the log
file each time a log message is generated. The default is No.
DestroyOnOpen
If set, instructs the logging facility to truncate the log

file each time the stack is restarted. The default is No.
LLCTrace
Specifies whether LLC frame tracing is to be enabled.

The default is No.
TCPTrace
Specifies whether TCP/IP activity logging is to be

enabled. The default is 0.
Directory Configuration
no longer supported
Configuring X.500
no longer supported
Configuring LDAP
no longer supported
211
212
Appendix E: Addressing Issues
Appendix E
Addressing Issues
This section explains the addressing scheme from the network and programmatic
points of view. The discussion presented here assumes that you possess cursory
knowledge of the 7-layer model.
Presentation Address
In order for one MMS application to establish a connection to another MMS
application, the initiating node must know the address of the node with which
it intends to communicate. This address is called the Presentation Address and
is comprised of the Presentation Selector, Session Selector, Transport
Selector, and the Network Address (NSAP).
Selectors are octet strings that can be assigned arbitrarily. The NSAP
identifies the node on an OSI network and is equivalent to the IP Address on a
TCP/IP network. The sequence of selectors and NSAPs defines a branch
through the OSI Stack address tree as shown in the diagram below.
psel
psel
psel
psel
(0001)
(0002)
(0003)
(0004)
ssel
(0001)
tsel
(0001)
ssel
ssel
(0002)
(0003)
tsel
NSAP
(0002)
213
To be able to use the OSI stack, the application must first bind to it. This is
done by activating a Presentation Address, which creates a new branch (path)
in the address tree. Once the presentation address is successfully activated, the
application is ready to send and/or receive connect requests using the newly
activated path.
When a MMS application attempts to establish a connection, it issues a
connect request that contains the presentation address of the application
intended to receive the request. First, in order for the request to reach the
destination, the specified NSAP must match the NSAP of the remote node. If
this is the case, the request will reach its destination. Upon receipt of the
connect request, the remote OSI stack examines the selectors present in the
request. If it finds a branch in its address tree with matching selectors, the
connect request is passed to the application that activated the branch.
Otherwise, the connection is rejected.
ACSE Parameters
In some situation, as in the case of secure systems, it may be necessary for the
called application to know the identity of the caller. In others, as in the case of
MMS-based gateways, the identity of the destination must be known. To
provide and/or examine such information, ACSE offers a set of parameters
that the application can send and receive. These parameters are Application
Process Title (AP Title), Application Entity Qualifier (AE Qualifier),
Application Process Invocation Identifier (AP Invoke ID), and Application
Entity Invocation Identifier (AE Invoke ID). These parameters are optional
and their use is strictly application-specific. See the OSI Addressing section
for more information on the format of the ACSE parameters.
AR Names
MMS-EASE defines the term Application Reference Name, or AR Name.
An AR Name is an ASCII string of up to 32 characters that is used to
collectively identify Application Entity information (AP Title and AE
Qualifier) and the Presentation Address associated with an application. In
other words, an AR Name is not something that is exchanged between two
applications over the network, but rather a human-readable shorthand for the
ACSE and addressing information that it represents. MMS-EASE applications
use AR Names when calling MMS-EASE Connection Management APIs.
214
Appendix E: Addressing
Addressing Concepts
This section is intended to give you an insight into how OSI addressing works.
It introduces new concepts and abstractions that are not required in order to
program MMS-EASE application or to configure an OSI Directory
Information Base (DIB).
Review the diagram of the OSI stack below. Oval accesses shown between the
adjacent layers represent the Service Access Points (or SAPs). A SAP can be
viewed as a channel through which one layer provides a set of services (such
as connection management and data transfer) to the layer immediately above
it. A SAP is similar to a TCP/IP socket as defined by BSD (Berkeley Software
Distribution).
Psel
PSAP
Ssel
SSAP
Tsel
Application
MMS-EASE
ACSE
Presentation
Psel
PSAP
Ssel
Layer
SSAP
Session Layer
TSAP
Tsel
TSAP
Transport Layer
NSAP
Network Layer
LSAP
Data Link Layer
MAC
Address
Physical Layer
Figure 29: Seven Layer Stack
215
Additionally, the diagram shows Selectors, which are represented by arrows.

A Selector is an octet string used to identify a specific SAP at a specific layer
for all upper layers (Transport and above). Since in most OSI
implementations all SAPs at any layer provide the same set of services to their
users, all such SAPs are equivalent. Although theoretically, there may be
several selectors that identify a single SAP, for the sake of simplicity, we will
assume that each unique selector identifies a unique SAP. Also, since
selectors are simply identifiers, their values can be chosen arbitrarily. From
this discussion, it is easy to see that an OSI selector is functionally equivalent
to a TCP/IP Port number, with the exception that the TCP/IP Port number
usually defines an application protocol.
At the Network layer, no selectors are used because the NSAP (or Network
Address) itself is used to identify a node on a OSI network, in the same
fashion the IP Address is used to identify a node a TCP/IP network.
The OSI address at any specific layer is constructed by combining all the
selectors up to that layer. MMS uses presentation addresses to set up
communication channels between two MMS-enabled applications. A
presentation address is composed of the Presentation Selector, Session
Selector, Transport Selector, and one or more Network Addresses (NSAPs).
Note that in most instances, you will only have a single NSAP associated with
a presentation address. However, if your system is attached to more than one
subnetwork, it is possible to assign a unique NSAP for each such subnetwork.
To summarize, the Presentation Address represents a conduit through an OSI
Stack that an application uses to communicate with other OSI-enabled
applications on the network.
When communicating with another application process on an OSI network
using MMS-EASE, you specify the AR Name configured in the local DIB to
represent the remote application. MMS-EASE extracts the presentation
address and ACSE parameters from the DIB and passes this information to the
OSI stack.
Once the remote address is known, it becomes the job of the Network layer to
find the proper subnetwork and the best path to reach the destination NSAP.
This process, which consists of associating MAC addresses with NSAPs, is
called network routing and is implemented using the ISO End System to
Intermediate System (ES-IS) protocol.
216
Appendix E: Addressing
Network routing is accomplished in one of two ways: dynamic or static.

Dynamic routing occurs when MAC addresses associated with NSAPs are
discovered dynamically. With static routing, the user creates static routing
records in the Network layer by providing the required information via OSI
stack configuration commands. Static routing should only be used in those
situations where the remote node does not implement ES-IS. Consult the
documentation that accompanies the OSI stack for more information on how
to create static routing records.
Naming Authority
In most applications where the network is local, the assignment of SAPs and
selectors can be rather arbitrary, and is usually done on an adhoc basis.
However, the assignment of names and addresses can be an important issue
when designing a large open network. This is where the naming authority
comes into the picture. The term Naming Authority represents a person or
an organization responsible for the assignment of network addresses and
ACSE parameters across the network or networks.
Addressing
A summary of the addressing elements is shown below.
AP Title
The AP Title is an Object Identifier, assigned by the network naming
authority, representing the Application Process Title for your particular
application process. An Object Identifier is a sequence of integer values
representing an application in the OSI Model. The first value in the AP Title
should be 1 (ISO) (the valid range is 0 to 2). The second value should be 1, 2,
or 3 (the valid range is 0 to 39). The third value is open for international
assignment. If your addressing is local, then this value should be 9999. The
rest of the values are arbitrary. For example, values could be assigned to
represent type and location of the application.
AP Invoke ID
Application Process. The use of this parameter is currently not well defined
and therefore is discouraged.
AE Qualifier
217
AE Invoke ID
Application Entity. The use of this parameter is currently not well defined and
therefore is discouraged.
AE Title
Although an AR Name may be configured to use any or all of the ACSE
parameters defined above, the recommended approach is that if ACSE
information is required it should be in the form of an AE (Application Entity)
Title. The AE Title is comprised of an AP Title and an AE Qualifier. If used,
the AE Title should be registered with the appropriate naming authorities for
your network.
Presentation Selector
This octet string represents the Presentation Selector used to identify a
Presentation SAP. The maximum PSEL size is 16 octets (32 ASCII encoded
hex digits).
Session Selector
This octet string represents the Session Selector used to identify a Session
SAP. The maximum SSEL size is 16 octets (32 ASCII encoded hex digits).
Transport Selector
This octet string represents the Transport Selector used to identify a Transport
SAP. The maximum TSEL size is 32 octets (64 ASCII encoded hex digits).
218
Index
Index
A
Abort logging........................................ 168
ACSE .................................................... 130
ACSE Data logging .............................. 165
ACSE Data Sample logging.................. 195
ACSE Decode Logging ........................ 166
ACSE Decode Sample logging ............. 197
ACSE Encode Logging......................... 166
ACSE Flow........................................... 192
ACSE Log Masks ................................. 166
ACSE logging ............................... 165, 210
ACSE MVL Sample logging ................ 197
ACSE Parameters ................................. 214
Activating AXS4-ICCP .......................... 16
Activation Code ...................................... 17
Active ..................................................... 50
Active Mode ......................................... 101
Active Node .......................................... 103
Active Synchronization Config............... 36
Activity Log ............................................ 22
Add a DataValue .............................. 43, 56
Add a Device .......................................... 45
Add device for Remote Control Center .. 58
Add Remote Control Center Configuration
OPC Item String ................................. 87
Add to Active Configuration .................. 67
Add to Database...................................... 67
AddRemoteVCC ..................................... 74
Addressing .............................................. 39
Addressing Concepts ............................ 215
Addressing Issues ................................. 213
Addressing Logging.............................. 164
Advanced Topics .................................. 201
AE Qualifier ........................... 40, 209, 217
AE Title ................................................ 218
All tab ................................... 39, 47, 50, 61
Allow Extra............................................. 33
Allow Missing ........................................ 33
AP Title .................................. 40, 209, 217
Application Support.................................. 7
AR Modes............................................... 28
AR Names....................................... 39, 214
ASN.1 ................................................... 130
ASN.1 Decode logging ........................ 167

ASN.1 Decode Sample logging.... 191, 192
ASN.1 Encode logging......................... 167
ASN.1 Log Mask ................................. 167
Assign Data Values by Data Type .......... 68
Assignment Mode .................................. 29
Association .... 3, 30, 61, 68, 136, 138, 141,
150, 155
Association Connect Timeout ................ 37
Association Name .................................. 47
Association Summary............................. 29
Association/Address Matching Control
Parameters.......................................... 33
Assumptions ............................................. 7
Authentication ...................... 137, 139, 142
Auto DSTS Parameters .......................... 67
Automatic Config Synchronization ........ 36
Automatically Accept Database Changes65
Autorun .................................................. 10
AX-S4 Flow Logging ........................... 163
AX-S4 ICCP ............................................ 3
AX-S4 ICCP Version ........................ 124
AX-S4 ICCP Block Diagram ................... 1
AX-S4 ICCP Configuration ................... 27
AX-S4 ICCP Configuration main screen 27
AX-S4 ICCP Debug Sample Logging .. 190
AX-S4 ICCP FLOW ............................ 187
AX-S4 ICCP Local Messages .............. 135
AX-S4 ICCP main screen ...................... 22
AX-S4 ICCP Model ................................. 4
AX-S4 ICCP Monitor .......................... 121
Data Values...................................... 131
Local Devices .................................. 133
Local DSTS Overview ..................... 154
Local DSTS Status & Parameters .... 155
Local Selected DSTS Data Values... 157
Log Masks ....................................... 128
Main Screen ..................................... 121
Preferences....................................... 122
RCC Data Values ............................. 144
RCC Devices ................................... 146
RCC DSTS Overview ...................... 149
219
RCC DSTS Status and Parameters ...150

RCC Messages .................................148
RCC Selected DSTS Data Values ....153
RCC Statistics ..................................139
RCC Association Statistics ...............142
Remote Control Centers Overview ...136
Statistics Screen................................125
AX-S4 ICCP OPC ................................189
AX-S4 ICCP Redundancy System..........25
deployed with redundant OPC Client
applications ......................................106
integrated with an OPC redundancy
broker ............................................... 105
AX-S4 ICCP Startup Considerations......14
AX-S4 ICCP Statistics OPC Item Strings
............................................................ 90
AX-S4 MMS log masks ........................163
axs4iccp.err ............................................. 21
axs4iccp.log ............................................ 21
AXS4ICCP.log .....................................160
AxsICCPLogCfg.xml............................162
B
Basic Redundant Config Process ..........107
Basic tab ...............................39, 47, 50, 61
Bilateral Table Description .....................51
Bilateral Table ID ...........................50, 138
Block 1 Block 9 ...................................51
Block tab ................................................. 50
Buffer Count ........................................... 37
Buffer Time.................37, 62, 71, 152, 157
Building Applications using OPC...........73
C
c2v file .................................................... 18
Calculated ............................................... 43
Change .................................................... 60
Change of Value ...................................132
Chapter Descriptions ................................2
Check Back ID ..................................44, 58
Clear Status ........................................... 123
Client ................................................ 3, 128
Client Data Set Transfer Sets ..................61
Client Data Sets ......................................59
Client Data Values ..................................54
Client DataValue Name ..........................54
Client Device Name ................................57
220
Client Devices ........................................ 57

Client Messages...................................... 59
Client Services ..................... 126, 140, 143
Collect Key Status Information .............. 18
COM ........................................................ 3
Command ............................................... 44
Compact Database .................................. 30
Component Object Model ........................ 3
Config................................................... 129
Configuration File Name ........................ 31
Configuration Logging ......................... 164
Configuration Mode ............................... 28
Configuration Source ............................. 31
Configuration Synchronization ............ 109
Configured Client Data Values .............. 66
Configuring the Stack Logging Level .. 209
Confirm Actions ..................................... 29
Conservative ........................................... 29
Conservative DS Data Size Calculation . 68
Constrained ............................................ 29
Correct Mismatches in Databases........... 66
COV ............................. 132, 145, 153, 158
CRCs .................................................... 109
Create XML File for Remote Data Values
........................................................... 66
Critical.............................. 62, 70, 151, 156
D
Data Set .................................................. 61
Data Set Calculation ............................... 29
Data Set Name .............................. 150, 155
Data Synchronization ............................. 37
Data Synchronization Issues ................ 109
Data Synchronization Sample Startup
Scenarios .......................................... 118
Data Synchronization Scenario
Add Remote ..................................... 119
Data Type ................................... 42, 51, 55
Data Type Validation ............................. 66
Data Value Discovery ............................ 64
Data Value Read Indications 126, 139, 143
Data Value Read Requests ... 126, 140, 143
Data Value Services .... 126, 139, 140, 142,
143
Data Value Write Indications126, 140, 143
Data Value Write Requests .. 127, 140, 143
Data Values .......................................... 131
DataSet Parameters................................. 68
Index
DataThreadPriority ............................... 201

DataValue Name..................................... 42
Date/Time ............................................. 131
Debug ................................................... 130
Debug logging ...................................... 210
Decode .................................................. 130
Default Client Data Value Access .......... 47
Default Scope ......................................... 47
Deployment Options ............................. 104
Integrate With Redundancy Broker .. 105
Redundant OPC Client Applications 106
Derive from Local Control Center .......... 47
Derive from Remote Control Center ....... 41
Derived Types Using .............................. 67
DestroyOnOpen .................................... 211
Detailed ............................................ 66, 67
Detect New Data Values ......................... 64
Device Get Tag Indications .. 126, 140, 143
Device Get Tag Requests ...... 127, 140, 143
Device Handling OPC Item Strings ........ 88
Device Name .......................................... 44
Device Operate Indications... 126, 140, 143
Device Operate Requests ...... 127, 140, 143
Device Select Indications ..... 126, 140, 143
Device Select Requests ......... 127, 140, 144
Device Select Timeout ............................ 32
Device Services ............ 126, 127, 140, 143
Device Set Tag Indications ... 126, 140, 143
Device Set Tag Requests ...... 127, 140, 144
Device Type ................................ 44, 53, 57
DirectDatabase........................................ 31
Directory Structure ................................. 11
Disabled ................................................ 131
Discover................................................ 137
Discover New Data Values ..................... 67
Discovery .............................................. 129
Discovery Association ............................ 64
Discovery Logging ............................... 164
Discrete ............................................. 44, 68
display assigned data values or unassigned
data values .......................................... 60
Display Mode ......................................... 28
Distributed .............................................. 28
Dongle Exchange Form .......................... 16
Double Click........................................... 29
Drop-Down Menus ............................... 122
DS Condition Detected ........................... 60
DS Conditions .................................. 63, 70
DS Conditions Detected . 69, 145, 153, 158

DS Conditions tab .................................. 61
DSConditions.Change .................. 151, 156
DSConditions.External ................ 151, 156
DSConditions.Integrity ................ 151, 156
DSConditions.Interval.................. 151, 156
DSConditions.Operator ................ 151, 156
DSConditionsDetected ........................... 34
DSTS Reports Received ....... 126, 140, 143
DSTS Reports Sent .............. 126, 139, 143
E
Edit ....................................................... 122
Elapsed ................................................. 131
Elements of redundant AX-S4 ICCP.... 102
Enable Auto DataSetTransferSet Creation
........................................................... 68
Enable Client Data Value Discovery...... 64
Enable Client DV Reads ........................ 32
Enabled .. 37, 137, 138, 141, 149, 150, 155
Encode ................................................. 130
Encryption ............................ 137, 139, 142
Entered ................................................... 43
Error Handling OPC Item Strings .......... 92
Errors ........................................... 141, 144
Errors logging ...................................... 210
Estimated ................................................ 43
Event Code Detected .............................. 70
Event Code Detection ............................ 60
Every Connection ................................... 65
Excluded ................................................ 57
Execute Discovery.................................. 65
Export File ............................................. 28
Extensible Markup Language ................... 4
External Event .................................. 63, 71
F
failover ................................................... 49
figures
AXS4-ICCP Block Diagram ................ 1
AX-S4 ICCP Local Messages .......... 135
AX-S4 ICCP Model............................. 4
AX-S4 ICCP Monitor RCC Selected
DSTS Data Values ...................... 153
AX-S4 ICCP Monitor Data Values . 131
AX-S4 ICCP Monitor Local Devices
..................................................... 133
221
AX-S4 ICCP Monitor Local DSTS

Overview......................................154
AX-S4 ICCP Monitor Local DSTS
Status & Parameters .....................155
AX-S4 ICCP Monitor Local Selected
DSTS Data Values .......................157
AX-S4 ICCP Monitor Log Masks ....128
AX-S4 ICCP Monitor Main Screen .121
AX-S4 ICCP Monitor Preferences ...122
AX-S4 ICCP Monitor RCC Data
Values .......................................... 144
AX-S4 ICCP Monitor RCC Devices 146
AX-S4 ICCP Monitor RCC DSTS
Overview......................................149
AX-S4 ICCP Monitor RCC DSTS
Status and Parameters ..................150
AX-S4 ICCP Monitor RCC Messages
..................................................... 148
AX-S4 ICCP Monitor RCC Statistics
..................................................... 139
AX-S4 ICCP Monitor Remote CC
Association Statistics ...................142
AX-S4 ICCP Monitor Remote Control
Centers Overview.........................136
AX-S4 ICCP Monitor Statistics Screen
..................................................... 125
AX-S4 ICCP redundant system
deployed with redundant OPC Client
applications ..................................106
Elements of a redundant AX-S4 ICCP
system .......................................... 102
Local Control Center Overview screen
..................................................... 124
ICCP Configuration Utility main screen
....................................................... 27
Seven Layer Stack ............................215
SISCO OSI Stack Configuration Screen
..................................................... 205
First Connection .....................................65
Flow .............................................. 129, 130
G
General OPC Item Strings ......................74
General Parameters .................................31
Get Tag Reason .....................................147
Get Tag Send Request...........................147
Get Tag Status.......................................147
Get Tag Value .......................................147
222
Getting Started ....................................... 23

Getting Tag Information from a Remote
Device OPC Item String .................... 90
Group Update Rate ............................... 122
H
HardFlush ............................................. 211
HASP Admin Control Center ................. 19
HASP Software protection ..................... 16
Heartbeat ................................................ 49
Heartbeat Tx Period ............................... 39
High Interface logging.......................... 210
I
IAdviseSink .............................................. 6
ICC ......................................................... 51
ICCP ................................................. 3, 129
ICCP Addressing Issues ......................... 24
ICCP Configuration Utility .............. 23, 28
ICCP Control Center or Application ........ 3
ICCP LiteTest Sample Program.PDF ..... 93
ICCP Logging ...................................... 163
ICCP State Polarity ................................ 77
ICCP to OPC Quality Mapping ........ 35, 77
IccpCfg ........................................... 23, 101
ICCPLiteTestApplication.exe ................ 93
ICCPStatePolaritySwitch ....................... 77
IConnectionPointContainer ...................... 5
IDataObject .............................................. 5
Identification Parameters ........................ 33
IEnumOPCItemAttributes ........................ 5
Import File.............................................. 28
Include in DataFlags............................... 34
Increment COV ...................................... 31
Info Reference ............................ 46, 54, 59
Information Message Handling OPC Item
Strings ................................................ 88
Information Messages . 126, 127, 140, 141,
143, 144
Information Messages Received .. 127, 141,
144
Information Messages Sent .. 126, 140, 143
Initial Activation with Internet Access ... 17
Initiate .............................................. 30, 48
Installation ................................................ 9
Installation for Windows ........................ 10
Integrate With Redundancy Broker ...... 105
Index
Integrity Check ................. 62, 71, 151, 156

Integrity Time Out ............................ 63, 70
Inter-Control Centre Communications
Protocol TASE.2 ............................... 7
International Organization for
Standardization..................................... 3
Interval.............................. 62, 71, 151, 156
Interval Time Out ............................. 63, 70
Introduction .............................................. 1
IOPCAsyncIO ........................................... 5
IOPCAsyncIO2 ......................................... 5
IOPCBrowseServerAddressSpace ............ 5
IOPCDataCallback ................................... 6
IOPCGroupStateMgt ................................ 5
IOPCItemMgt ........................................... 5
IOPCItemProperties.................................. 5
IOPCServer............................................... 5
IOPCShutdown ......................................... 6
IOPCSyncIO ............................................. 5
IP/Net Address........................................ 39
IR Data Logging ................................... 166
IR Flow Logging .................................. 165
IR Normal Error Logging ..................... 165
ISO ........................................................... 3
L
Last Time of Report .............. 150, 155, 156
License Changes ..................................... 20
Limit Data Values in DataSets................ 69
ListOfVariables ...................................... 29
LLCTrace.............................................. 211
LoadWinsock ........................................ 201
Local and Remote Item Strings............... 75
Local and Remote Synchronization ........ 37
Local AR .......................................... 30, 48
Local Control Center ........................ 29, 40
Local Control Center Data Values .......... 42
Local Control Center Device Name ........ 53
Local Control Center Devices................. 44
Local Control Center Messages .............. 46
Local Control Center Name .................... 41
Local Control Center Name .................... 31
Local Control Center Overview ............ 124
Local Control Center Overview screen . 124
Local Data Quality.................................. 35
Local Data Set Transfer Sets Overview 154
Local Data Value Fields ....................... 122
Local Devices ....................................... 133
Local Domain ......................................... 50

Local DSTS Status and Parameters ...... 155
Local Host Parameters ........................... 33
Local ICCP Data Value Quality During
Switchover ....................................... 103
Local Messages .................................... 135
Local Ref ...................................... 135, 149
Local Selected DSTS Data Values ....... 157
Local Server
Data Values OPC Item Strings .......... 81
Devices OPC Item Strings ................. 82
Messages OPC Item Strings............... 82
Status Information OPC Item Strings 83
Local Status Info OPC Item String......... 92
Local Synchronization ........................... 37
LocalControlCenterName ...................... 74
Log ......................................................... 22
Log file locations.................................. 160
Log Timing........................................... 131
LogFile ................................................. 211
LogFileEn ............................................ 210
Logging ................................................ 127
LogSize ................................................ 211
LogViewer ........................................... 159
Low Interface logging .......................... 210
M
Matching .............................................. 129
Matching Algorithm ............................... 96
Matching Criteria ................................... 97
Max Data Set Transfer Sets .................... 41
Max Data Sets ........................................ 41
Max DSTS PDU Size ............................. 68
Max DVs per Data Set ........................... 69
Max Indications Pending ....................... 49
Max MMS Message Size ................. 41, 49
Max Nesting Level ................................. 49
Max Requests Pending ........................... 49
Max Size .......................................... 46, 59
Memory ................................................ 130
Message........................................ 135, 149
Message ID .................................. 135, 149
MI......................................................... 129
MI CONFIG ......................................... 180
MI Flow Logging ................................. 164
MI Flow Sample logging...................... 178
MI Matching Sample logging............... 179
MiLogMasks ........................................ 164
223
Missing ................................................... 56
Mistyped ................................................. 57
MMS ..................................................... 128
MMS Client Logging ............................164
MMS Client Sample logging ................168
MMS Log masks...................................164
MMS Server logging ............................164
MMS Server Sample Logging ..............173
mmslog ................................................. 129
Multiple Ethernet adapters and TCP/IP ..12
MVL ..................................................... 130
MVL flow logging ................................165
MVL Log masks ...................................165
Name..................................................... 132
Name
Bilateral Table ....................................50
Data Value ........................145, 153, 158
Device ......................................133, 146
DSTransferSet ..................149, 150, 155
Information Message ........................135
Local Control Center DataValue ........51
Message ............................................ 148
NamedVariableList .................................29
Naming Authority .................................217
New......................................................... 56
New Client Data Values .........................67
No Synchronization Configuration .........36
Normal .................................................... 66
Normal Max ............................................ 43
Normal Min ............................................ 43
Normal Source ........................................ 43
Number of Active Associations ............125
Number of Active Remotes...................125
Number of Associations........................125
Number of Remotes ..............................124
O
Object Change ..................................63, 70
Object Identifier ....................................217
ObjectType ............................................. 75
OLE (Object Linking and Embedding) for
Process Control ....................................3
On-Line Reconfiguration ......................108
OPC .................................................. 3, 130
OPC Client Application ............................3
OPC Client Count ...................................74
OPC Client.exe .......................................93
OPC Data logging .................................164
224
OPC General Concepts........................... 73

OPC Interface ........................................... 5
OPC Item Availability .......................... 103
OPC Item Strings ................................... 73
OPC Logging ....................................... 163
OPC Parameters ..................................... 34
OPC Servers ........................................... 73
OPC Specification V3.00 ......................... 5
OPCDAAuto.dll ..................................... 73
Operate Indication ................................ 133
Operate Remote VCC........................... 133
Operate Send Request .......................... 146
Operate Send Response ........................ 134
Operate Status ...................... 134, 146, 147
Operate Value............................... 134, 147
Operating a Remote Device OPC Item
String ................................................. 90
Operator Request .............................. 63, 71
Options tab ............................................. 50
OSI Stack Registry Logging Values ..... 210
OSI Stack Registry Parameters............. 201
P
Parameters tab ........................................ 47
Partner IP ............................................... 38
PDU...................................................... 129
PDU Sample Logging .......................... 177
Pipeline .................................................. 37
Policies
Administer Approved Config
Changes ....................................... 112
Automatic Config Changes.......... 115
Port ......................................................... 38
Preferences ..................................... 28, 122
Presentation Address ............................ 213
Presentation logging ............................. 210
Presentation Selector ............................ 218
Primary Node ....................................... 100
Primary Synchronization Configuration . 36
Priority ................................................. 201
PriorityClass ......................................... 201
problems establishing an association.... 199
Protocol Data Unit ............................... 129
PSEL .............................................. 40, 208
Index
Q
Quality .......................... 132, 145, 154, 158
Quality Current Source . 132, 145, 154, 158
Quality Flags..................................... 32, 76
Quality Normal Value... 132, 145, 154, 158
Quality TimeStamp ....... 132, 145, 154, 158
Quality Validity ............ 132, 145, 154, 158
Quick ...................................................... 67
R
RBE .................................. 62, 70, 151, 156
Read Only ......................................... 52, 55
Real................................................... 44, 68
Redundancy .................................... 25, 130
Redundancy Definitions ....................... 100
Redundancy Items ................................ 103
Redundancy Log masks ........................ 165
Redundancy Monitor ............................ 101
Redundancy OPC Item Strings ............... 79
Redundancy Parameters.......................... 35
Redundancy Port Link (RPL) ............... 101
Redundancy System................................ 99
Redundancy System Features ................. 99
Redundant AX-S4 ICCP Configuration
Issues ................................................ 107
Redundant OPC Client Applications .... 106
Redundant System Block Diagram ....... 102
Registry Parameters .............................. 201
Reload ................................................... 137
Reloading a Remote Control Center
Bilateral Table OPC Item String ........ 87
Remote.................................................. 136
Remote AR ....................................... 30, 48
Remote ARs tab ...................................... 47
Remote Control Center ..................... 30, 46
Association Overview ...................... 141
Association Statistics........................ 142
Associations ....................................... 47
Bilateral Tables .................................. 49
Data Values ...................................... 144
Devices ............................................. 146
DSTS Overview ............................... 149
DSTS Status and Parameters ............ 150
Identification/Association Matching . 33,
95
Messages .......................................... 148
Name .................................................. 46
Overview.......................................... 137
Selected DSTS Data Values............. 153
Statistics ........................................... 139
Remote Control Centers Overview....... 136
Remote Data Quality .............................. 36
Remote Data Value Fields.................... 123
Remote Domain ..................................... 50
Remote OPC Item Value Quality During
Switchover ....................................... 104
Remote Server
Data Values OPC Item Strings .......... 85
Devices OPC Item Strings ................. 86
General Information OPC Item Strings
........................................................... 84
Information Messages OPC Item Strings
........................................................... 86
Link Information OPC Item Strings... 84
Transfer Sets OPC Item Strings ......... 86
Remote Synchronization ........................ 37
Remote VCC ........................................ 135
Remove Mismatches from Data Sets ...... 66
Report By Exception .............................. 62
Report Count ................................ 150, 155
Reset Column Sizes................................ 29
Retry Delay ............................................ 48
Retry Time ............................................. 39
Role ........................................................ 35
RPL ...................................................... 101
RPL configuration issues ..................... 199
RPL Connection ..................................... 38
RPL Flow Logging ............................... 165
RPL Normal Error Logging ................. 165
RPL Timers ............................................ 39
RunHidden ........................................... 201
Running AX-S4 ICCP ............................ 21
Running AX-S4 ICCP as a Service ........ 14
S
sample OPC item strings ........................ 76
SaveCurrentSettings ............................... 74
SBO .................................................. 44, 58
Scope ........................ 51, 53, 54, 55, 57, 59
Seal Mode .............................................. 38
Seal Time Window ................................. 38
Secondary Node ................................... 100
Seconday Synchronization Config ......... 36
Security ................................................ 130
Security Log masks .............................. 165
225
Select Check Back ID ...................134, 147

Select Indication ...................................134
Select Local Control Center ....................47
select preconfigured data values for the
Bilateral Table ....................................52
select preconfigured devices for the
Bilateral Table ....................................53
Select Remote Control Center ................41
Select Remote VCC ..............................134
Select Send Request..............................147
Select Send Response ...........................134
Select Status.......................................... 134
Select Timeout ........................................ 44
Select-Before-Operate.............................44
Selected.........................132, 145, 154, 158
Selecting a Remote Device OPC Item
String .................................................. 89
Selectors tab ............................................ 39
Send Message .......................................135
Server ................................................ 3, 128
Server Data Values .................................51
Server Devices ........................................ 53
Server Messages .....................................54
Server Services .....................126, 139, 142
Server State Suspended...........................36
Service Role ............................................ 48
Session logging .....................................210
Session Selector ....................................218
Set Tag Reason .....................................147
Set Tag Send Request ...........................147
Set Tag Status .......................................148
Set Tag Value .......................................148
Setting Tag Information of a Remote
Device OPC Item String .....................90
Setup Task List .........................................9
Seven Layer Stack.................................215
shared memory size...............................207
Shortest Interval ......................................50
show hidden folders ..............................161
Show Only Unassigned Data Values ......54
siscinf3.mdb ............................................ 28
SISCO OSI Stack Configuration Screen
.......................................................... 205
SISCO.AXS4ICCP.3 ..............................73
Socket Flow logging .............................166
Socket Log Masks.................................166
Socket Notice logging...........................166
Socket Receive logging.........................166
226
Socket Transmit logging....................... 166

Software Application Package.................. 3
Software license file ................................. 6
software lock .......................................... 16
Spare Capacity
Num Called Association .................... 31
Num Calling Association ................... 31
Special Variables .................................... 69
SSEL .............................................. 40, 208
Stack as a Service ................................... 13
Stack Configuration.............................. 203
Stack Startup Considerations ................. 13
Standard Logging ................................. 162
Standby Mode ...................................... 101
Standby Node ....................................... 103
Start Associations ................................... 32
Start AX-S4 ICCP .................................. 30
Start AX-S4 ICCP Monitor .................... 31
Start Log Viewer .................................. 123
Start Time ......................... 62, 70, 151, 156
Starting AX-S4 ICCP Normal Process ... 21
Startup Considerations ........................... 14
Startup Time ........................................... 39
State........................................................ 68
Statistics ............................................... 125
Status ...................... 22, 124, 137, 138, 142
SUIC Abort logging ............................. 168
SUIC Confirm logging ......................... 167
SUIC Indication logging ...................... 167
SUIC Log Masks .................................. 167
Summary ................................................ 28
Supported Features ............................... 138
Supported Functionality ........................... 5
Switch to Active Delay........................... 39
Sx (XML) Log Masks .......................... 167
Sx Decode logging ............................... 167
Sx Notice logging ................................. 167
System .................................................. 131
System Requirements ............................... 6
T
Tag Enabled ............................... 45, 53, 58
Tag Reason ........................................... 134
Tag Remote VCC ................................. 134
Tag Value ............................................. 134
TASE.2 ..................................................... 4
TASE.2 Version ............................. 46, 138
TCP/IP (via RFC1006) Support ............. 15
Index
TCPTrace .............................................. 211

Telemetered ............................................ 43
Terminology ............................................. 3
Test Applications .................................... 93
The AX-S4 ICCP Model .......................... 4
Time Limit for Execution ....... 63, 152, 157
Time Stamp............................................. 32
Timeout................................................... 38
TimeStamp.................... 132, 145, 153, 158
Timing .................................................. 211
TLE ................................... 63, 72, 152, 157
Tools ............................................... 29, 123
Transfer Set
Name ............................................ 59, 69
Parameters .......................................... 70
Time Stamp .......... 60, 69, 145, 154, 158
Transport logging ................................. 210
Transport Selector................................. 218
Tree Navigation ...................................... 29
troubleshooting ..................................... 199
TSEL .............................................. 40, 208
U
UAC show hidden folders .................... 161
Unconstrained ......................................... 29
Update License with no internet access .. 18
USB Dongle ....................................... 6, 16

Use Current Source ................................ 35
Use ICCP Time Stamp ........................... 34
Use Normal Value .................................. 35
Use TCP/IP ............................................ 39
Use Validity ........................................... 35
UseKeepAlive ...................................... 202
UseLegacyQualityMappings .................. 77
User Initiated .......................................... 65
Using AX-S4 ICCP as an ICCP Server .. 24
V
Validate Configured Data Values........... 66
Validate Existing Configuration............. 64
Value ............................ 132, 145, 153, 158
VCC ....................................................... 51
view the contents of a selected data set .. 60
W
WinsockLoadTime ............................... 202
X
XML......................................................... 4
227

UserGd Axs4iccp 132095

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UserGd Axs4iccp 132095

Uploaded by

Copyright:

Available Formats

AX-S4 ICCP

SISCO, Inc. 1999-2011

AX-S4 ICCP for Windows

AX-S4 ICCP User's Guide

Remote Server Devices ......................................................................................... 86

ACSE MVL ......................................................................................................... 197

AX-S4 ICCP User's Guide

Figure 1: AX-S4 ICCP Block Diagram

AX-S4 ICCP User's Guide

A special property of a class used to associate instances within an

This product provides the interface between control centers and

A role assumed by an application when interacting with other

Component Object Model.

International Organization for Standardization.

Inter-Control Centre Communications Protocol

This refers to the control center or application running on a

OLE (Object Linking and Embedding) for Process Control.

This refers to an OPC application developed using a Software

A role assumed by an application when interacting with other

This refers to a front-end Windows-based product. It is used to

AX-S4 ICCP User's Guide

IECC870-6-503 TASE.2 Services and Protocol V1996-08 and

Extensible Markup Language. This is an international

The AX-S4 ICCP Model

AX-S4 ICCP User's Guide

AX-S4 ICCP supports the following client side interface:

Windows XP Professional Version 2002 service pack 3,

Any Software Application Package for Windows supporting OPC 3.0 or

HASP Software license file or HASP USB dongle. The decision as to

An 802.3 network with TCP/IP (RFC1006).

Additional hard disk space and memory to accommodate the applications

ICCP control centers or applications with which to communicate.

You are familiar with the ICCP (Inter-Control Centre Communications

AX-S4 ICCP User's Guide

Setup Task List

Reboot your computer and restart Windows.

Make sure all information is properly configured using the supplied

Start AX-S4 ICCP by clicking on the Start button and selecting

Start an OPC Client and use OPC Commands to communicate with

AX-S4 ICCP User's Guide

Installation for Windows

AX-S4 ICCP installation requires a user to have Adminstrator Privileges.

Insert the AXS4-ICCP-132-095 CD-ROM into the CD-ROM drive.

If the Autorun feature is enabled on your computer, go to Step 4.

Follow the instructions on the screen to complete the AX-S4 ICCP

The installation sequence is as follows:

The following directory structure should now exist on your computer.

AX-S4 ICCP User's Guide

\Program Files\SISCO\AX-S4 ICCP

AX-S4 ICCP Program

<Common Application Data>\SISCO\AX-S4

AX-S4 ICCP Client Log

<Common Application Data>\SISCO\AX-S4

All AX-S4 ICCP

SISCO License file

<Common Application Data>\SISCO

The <Common Application Data> is different for various Windows

Windows Vista/7/2008 Application Data Common directory:

Multiple Ethernet adapters and TCP/IP

Stack Startup Considerations

Click on Start, select Control Panel.

Open Administrative Tools.

Locate the SISCO OSI Stack and double click on it.