Gproxy
HOST LINKS
GPROXY
G&R
Network Manager
&
SNMP proxy agent
http://www.gar.no/hostlinks/
TM
G&R
Microsoft, Windows, MS, MS-DOS are registered trademarks of Microsoft Corp.
IBM and PC are registered trademarks of IBM Corp.
UNIX is a registered trademark in the United States and other
countries, licensed exclusively through X/Open Company, Ltd.
Any other product names are trademarks of their respective owners.
Version 6.3
© Gallagher & Robertson as 1990-2005
All Rights Reserved
GALLAGHER & ROBERTSON AS, Kongens gate 23, N- 0153 Oslo, Norway
Tel: +47 23357800 • Fax: +47 23357801
www: http://www.gar.no/
e-mail: [email protected]
G&R
Contents
Host Links Gproxy ............................................................................. 1
Installation.................................................................................................................. 1
Scope of the Product .................................................................................................. 2
Run-time licenses ....................................................................................................... 3
Load balancing.................................................................................... 5
Enabling management statistics ................................................................................. 6
SSL connections......................................................................................................... 7
Port numbers .............................................................................................................. 7
Ggate .......................................................................................................................... 8
Ggate port number .......................................................................................... 8
Client configuration ........................................................................................ 9
Glink.......................................................................................................... 9
Glink for Java .......................................................................................... 10
Gweb ........................................................................................................................ 10
GwebS, the G&R web server........................................................................ 10
Port number ............................................................................................. 11
Other web servers ......................................................................................... 11
Port number ............................................................................................. 12
Client configuration ...................................................................................... 12
Glink for Java servers............................................................................................... 13
Port number................................................................................................... 13
Client configuration ...................................................................................... 13
License sharing.................................................................................. 15
Initializing the license server.................................................................................... 15
Requesting a license ................................................................................................. 15
License back up........................................................................................................ 16
Restoring license limits ............................................................................................ 16
License communities................................................................................................ 17
Using ‘backup only’ licenses ................................................................................... 17
Alarms................................................................................................ 19
The alarm text library............................................................................................... 19
The alarm log ........................................................................................................... 21
G&R/Gproxy
i
G&R
SNMP support................................................................................... 23
Startup/Configuration...................................................................... 25
Parameters ................................................................................................................ 25
Command line examples ............................................................................... 28
Gproxy input data............................................................................. 29
Type 0 – alarm record ................................................................................... 29
Type 1 - connection event record.................................................................. 29
Type 2 - disconnection event record ............................................................. 29
Type 3 – Connection failures ........................................................................ 29
Type 4 – Statistics record.............................................................................. 30
Type 5 - Route state event record ................................................................. 30
Type 6 – Glink for Java Logon request record ............................................. 30
Type 7 – Gweb statistics record.................................................................... 30
Type 8 – License statistics record ................................................................. 30
Gproxy reports.................................................................................. 31
The System report .................................................................................................... 32
The Summary report................................................................................................. 35
The Detail report ...................................................................................................... 37
The Ggate Gateway report ....................................................................................... 39
The Load balancing reports...................................................................................... 41
The Glinkj server report ........................................................................................... 43
The License server report......................................................................................... 44
The Route report ...................................................................................................... 45
The User report ........................................................................................................ 47
The Session report.................................................................................................... 49
The MIB report ........................................................................................................ 50
The ‘HEX report’ ..................................................................................................... 52
Administration .................................................................................. 53
Gmanager operator commands................................................................................. 53
Monitoring Gproxy .................................................................................................. 54
Gproxy logging ........................................................................................................ 54
Appendix: Host Links Manuals....................................................... 55
ii
G&R/Gproxy
G&R
Appendix: Host Links License Keys ............................................... 57
Glicense.................................................................................................................... 57
License keys ............................................................................................................. 59
Appendix: Host Links Server Administration............................... 61
Appendix: Host Links DSA Utilities ............................................... 65
Gconame ....................................................................................................... 65
Gerror............................................................................................................ 66
Glnode........................................................................................................... 66
Gmacfix ........................................................................................................ 66
Gping ............................................................................................................ 67
Grnode .......................................................................................................... 67
Gtrace............................................................................................................ 67
Gtsupd........................................................................................................... 68
Appendix: Host Links Trace............................................................ 69
Trace activation ........................................................................................................ 69
Trace types ............................................................................................................... 69
Structure ................................................................................................................... 70
Tracing Ggate........................................................................................................... 71
Examples - G&R products ....................................................................................... 71
CPI-C and Gweb trace files...................................................................................... 73
Appendix: Error Codes.................................................................... 75
OSI/DSA error codes ............................................................................................... 75
Windows Sockets error Codes ................................................................................. 87
Appendix: G&R MIB extension ...................................................... 91
Appendix: Formatted SNMP trap trace......................................... 97
G&R/Gproxy
iii
G&R
iv
G&R/Gproxy
G&R
Host Links Gproxy
Installation
The G&R emulations and gateways are independent programs, but part of the
G&R Host Links product set available on all major UNIX/Linux platforms.
Many of the products are also available for Windows servers. For details on
platforms supported, software delivery and installation refer to the Host Links
Installation and Configuration manual.
VTnnn, xterm, ... terminal environment
Qsim
V78sim
G3270
Host Links platforms
Gspool
GUFT
GlAPI
Gproxy
Bull/IBM
Mainframes
LAN Workgroup, PCs
and Macs with Glink
Ggate
Gweb
Gspool
GUFT
GlAPI
LDSA
Gproxy
Powerful, multi-CPU
UNIX or Windows NT
Windows NT or
UNIX on PC
VIP7800 terminal environment
Pthru
Gspool
GUFT
GlAPI
Gproxy
G&R/Gproxy
1
G&R
Scope of the Product
Gproxy is a network management program used for supervision, management,
load balancing and license sharing of G&R Host Links applications.
Gproxy can be set up as a freestanding monitor program and/or report
generator in a small network, or play a bigger role in a larger network. It can
also act as an SNMP ‘proxy agent’ and report to one or more SNMP
management systems. Even though Gproxy can in principle be used by
anybody who has access to a Host Links installation, the typical Gproxy user is
an administrator or an operator in a network control center.
One of Gproxy's most important features is load balancing for G&R gateway
and server applications, ensuring that connections from Host Links clients
or from Glink users are evenly spread.
Another important task is acting as a license server in a shared license
configuration, ensuring that if a Host Links gateway or server system is
temporarily out of business, the licenses belonging to the failing system will be
automatically taken over by the remaining Host Links gateway or server
systems.
Gproxy receives and acts on information in a 'network management UDP
record' that is optionally generated and broadcast by G&R Host Links
applications. Theses broadcasts contain either statistical type information (e.g.
gateway load) or network event type information, such as detailed information
about connections, disconnections, error events and backup-route switching.
On UNIX/Linux systems, Gproxy can run in the foreground on a user screen
(in ‘VDU presentation mode’), or it can be set up to run unattended as a
background process. In the latter case Gproxy can optionally generate HTML
reports (in ‘HTML presentation mode’) that can be viewed by anyone with a
web browser. A choice of reports is available in both presentation modes that
enable the administrator to monitor Host Links user activities and resource
usage.
If Gproxy is used in an SNMP environment, Gproxy can be set up to forward
information in SNMP ‘trap’ format to up to 4 SNMP manager stations located
somewhere in the network.
2
G&R/Gproxy
G&R
Gproxy can optionally log network administration information to a log-file that
can be viewed at any time.
Gproxy is delivered as a single executable. No data- or configuration files are
necessary, but the command line arguments can optionally be included in a
configuration file.
Run-time licenses
In order to run Gproxy, the following license keys must be present in your
licenses file:
basic
For the base G&R run-time system
gproxy
For Gproxy
If SSL is used, you also need the following license key:
ssl
For the SSL versions of the DSA/DIWS line handler
The licenses file is located:
Windows Server
\gar\config\licenses
UNIX/Linux
/usr/gar/config/licenses
The licenses file identifies the G&R distributor, the owner of the license and
the licensed products. The license key for a product will normally state for how
many simultaneous sessions the product is licensed. If a limitation is specified
in the license, only the licensed number of sessions can be active at any time.
G&R/Gproxy
3
G&R
4
G&R/Gproxy
G&R
Load balancing
An important Gproxy feature is the ability to balance the load of gateways and
server programs. Currently Gproxy can perform load balancing for
G&R/Ggate gateways, G&R/Gweb servers and G&R/Glinkj servers. A
subset of the load balancing functionality is also supported for other (i.e. non
G&R) web servers. Gproxy can perform load balancing for all of these servers
simultaneously if desired.
Gproxy running on a single system can load balance for several servers running
on different systems. Two copies of Gproxy on different systems provide
robust load balancing that functions when one Gproxy system is down,
provided the clients are configured to try both systems, or the DNS name server
is configured to return both systems when the client does a look-up for the IPaddress. If Gproxy is to also provide license-sharing services, then it is a
prerequisite that Gproxy runs on all systems where a server runs. If all of the
Gproxy copies are to be used for load balancing, then the DNS configuration
needs to be more advanced.
Load balancing of the G&R products is based on statistical information that is
optionally distributed in network management UDP records by the various
Host Links server components. In load balancing mode, Gproxy maintains
various load-tables that contain current, highest and maximum usage counters
as well as various other statistical information reported by these servers.
Since this statistical information is sent out at regular intervals, Gproxy detects
any non-responsive or terminated server by the absence of its UDP statistics
record. If no statistical information has been received from a given server
within the time limits (configurable, default 20 seconds), Gproxy assumes that
the server has been terminated. This ensures that clients are always directed to
an operative, as well as the lightest loaded, server program.
G&R/Gproxy
5
G&R
In load balancing mode, Gproxy takes over the TCP/IP socket of the server in
question and ‘listens’ for connection requests coming in from the clients e.g.
requests for connection to G&R/Ggate or G&R/Gweb. When a connection
request comes in from a client, Gproxy sends back a ‘redirect record’. This
redirect record contains the network address of the server with the lowest load.
The client then automatically issues a new connect request using the suggested
network address. The suggested server can be located on the same system as
Gproxy or on some other Host Links system in the network. This initial
redirection dialog is handled automatically by the client application and is
transparent to the user.
Gproxy optionally generates load-balancing reports in either 'VDU' or HTML
format (see the Gproxy reports chapter). The reports are updated every time
load statistics are received from the servers and show the current, highest and
maximum load of the server program.
Load balanced servers can be manually disabled and re-enabled by means of
simple operator commands (see the Administration chapter).
Load balancing is a background task that takes place independently of other
activity, such as report generation.
Enabling management statistics
The statistical information, which is a prerequisite for the load balancing
functionality, must be explicitly enabled by command line parameter to the
server or gateway. The information can be either broadcast (i.e. made available
to all systems) or directed to up to 4 specific Gproxy addresses.
All server programs supports the following parameters:
-NA xxx yyy zzz
Send statistics to Gproxy network administration
stations (up to 4 IP-addresses may be given)
-NB on/OFF
Enable broadcasting to all Gproxy stations
e.g. send statistics from a G&R/Ggate gateway to Gproxy on 'saturn' and
'jupiter':
gg_tcp -na saturn jupiter -lp 30843 .......
6
G&R/Gproxy
G&R
SSL connections
Gproxy supports connections from SSL clients and can load balance these in
exactly the same way as ordinary (non-SSL) connections. In the case of a SSL
configuration, a separate version of the Gproxy program, GproxyS, is
delivered. There are no other functional differences between these two versions
of the program than SSL support; the SSL version supports an extra set of
common SSL command line parameters and uses other port numbers as
outlined in the paragraph below.
For a general description of SSL support in Host Links programs, and the
command line parameters, see the G&R/SSL manual.
Port numbers
When Gproxy is load balancing a server, it takes over the TCP/IP socket (i.e.
the port number) that is normally used by the server for client connections.
The table below shows the default port numbers used by Gproxy when load
balancing the various servers, and the Gproxy command line parameter that
can be used if you want to use a non-default port (note that if you change the
default port, you must also change the client configurations).
Server
Default port
Parameter
Ggate
30841
-LBGGA NNNNN
Ggate SSL
30851
-LBGGA NNNNN
GlinkJS
30842
-LBGLJ NNNNN
GlinkJS SSL
30852
-LBGLJ NNNNN
Gwebs
80
-LBGWB NNNNN
Gweb SSL
443
-LBGWB NNNNN
Other web server
80
-LBWEB NNNNN
Other web server SSL
443
-LBWEB NNNNN
G&R/Gproxy
7
G&R
Ggate
Ggate load balancing is by default enabled. e.g.
gproxy -pt html -rt gga
Gproxy would run in default background mode, doing default load balancing
for Ggate. It would generate a HTML report for Ggate load balancing.
In load balancing mode, Gproxy will open the Ggate TCP/IP socket and listen
for connection requests coming in from Glink, from Host Links clients or
from user-written GlAPI applications. Gproxy will use the default Ggate port
number (see Ggate port number) unless another port number has been given
with the –LBGGA command line parameter. When a connection request is
received on the socket, Gproxy starts up a separate process that takes over the
initial dialog with the client. When the client parameters are received and
validated, a redirect command is sent to the client redirecting it to the Ggate
system with lowest load factor. Gproxy then terminates the connection to the
client. The client automatically issues a new connect request using the
suggested network address.
If the balanced systems are of comparable size, the load factor is simply the
number of concurrent sessions reported by Ggate. If Gproxy is load balancing
Ggate systems of different sizes (most importantly as regards the physical link
capacity i.e. link types and numbers), a ‘load threshold’ value can be used by
Ggate; in which case the load factor is calculated based on the threshold
percentage.
Ggate port number
The default port used by Ggate is 30841. This is taken over by Gproxy when
load balancing is enabled, so Ggate must be started using another port. There
are two ways of achieving this:
Use the Ggate -LP command line parameter e.g.
gg_tcp –lp 30843 –nb
8
G&R/Gproxy
G&R
Configure the Ggate port number in the TCP/IP ‘services’ file. This file
is located in the following directory:
Windows server
UNIX/Linux
%SystemRoot\System32\Drivers\Etc
/etc
add a line to the file e.g.
ggate 30843/tcp
Alternatively Gproxy can be configured to use another connection port. This is
done in the same way using either the ‘services’ file or the Gproxy -LP
parameter. This is not the preferred alternative since it would require that all
client (e.g. Glink) configurations would need to be configured to use a nonstandard port number.
If an attempt is made to start Ggate and Gproxy using the same port number,
the second program will not start. An error message will be returned to the
caller e.g. if Ggate was the last program to start:
Bind Ggate socket failed (Ggate executing on same system?)
Client configuration
Glink
The IP-address remains the same, but
Gproxy is running on the target system, and
has taken over the Ggate port.
An Alternate IP-address is configured in
case the first connect fails. This is a second
Gproxy system. The result is robust load
balancing, which functions even if one
Gproxy system is down.
The delay of zero means that connects are
sent simultaneously to both Gproxy systems.
G&R/Gproxy
9
G&R
Glink for Java
The Server address remains the same, but
Gproxy is running on the target system, and
has taken over the Ggate port.
An Alternate server address is configured
in case the first connect fails. This is a
second Gproxy system. The result is robust
load balancing, which functions even if one
Gproxy system is down.
The Random connect check box causes
Glink for Java to try the first connect to the
Server or Alternate server in a random
manner.
Gweb
GwebS, the G&R web server
Load balancing for the Gweb server (GwebS) is enabled by the Gproxy
command line parameter -LBGWB [port number]. The port number is
optional, and defaults to 80 (the standard GwebS port) e.g.
gproxy -nlb -lbgwb -pt html -rt gwb
Gproxy runs in default background mode, doing load balancing for GwebS,
and generating a Gweb load balance report in HTML. Load balancing for
Ggate is suppressed. Note that port 80 is a restricted TCP/IP port. This is no
problem for the Windows version of the server program, but in the
UNIX/Linux case Gproxy must be launched from the root user and the sbit must be set on the executable file.
10
G&R/Gproxy
G&R
When load balancing for GwebS, Gproxy takes over the GwebS port (see
GwebS port number) and listens for Gweb connection requests coming from
the client browsers. When a connection is received, a standard HTTP redirect
command is sent back to the browser containing the IP-address and port
number of the GwebS system with the lowest load.
Port number
The default port used by GwebS is the standard web server port (port number
80). This is taken over by Gproxy when load balancing is enabled, so GwebS
must be started using another port e.g. using the GwebS -LP command line
parameter e.g.
gwebs –lp 8000 –nb
Other web servers
Gproxy offers a subset of load balancing functionality for other web servers.
This is enabled by the command line parameters:
-LBWEB [port number]
-WEBSPORT port number
gproxy -nlb -lbweb -websport 8000
Gproxy must run on every system that runs a web server to be load balanced,
and must be started with the -lbweb parameter, which causes it to check local
Gweb usage, and broadcast web server statistics on behalf of the non-G&R web
server. These broadcasts enable the load balancing function.
Gproxy takes over the web server port given in the -LBWEB parameter
(defaults to 80) and listens for Gweb connection requests from the client
browsers. When a connection is received a standard HTTP redirect command is
sent back containing the IP-address of the web server with the lowest current
load, and the non-standard port number on which the web servers are listening
(given to Gproxy in the –WEBSPORT parameter).
G&R/Gproxy
11
G&R
There are restrictions when load balancing for other web servers; there is no
communication between Gproxy and the non-G&R web server on who’s behalf
Gweb is generating web server statistics, and therefore no way Gproxy can be
sure of the state of the web server. If the Gweb usage count is zero, this can be
due to the fact that the web server is not executing. If the web server has for
some reason stopped, a manual intervention is necessary (e.g. restart Gproxy
without the -LBWEB/-WEBSPORT parameters on that system).
Port number
The default connection port number used by web servers is 80. This is taken
over by Gproxy when load balancing is enabled, so the non-G&R web server
in question needs to be started using another port.
Client configuration
Web browsers have standard functionality for connecting to an alternative
address if the first connect fails. URLs for connection to a particular web server
are always symbolic, and must be looked up in a DNS server. If there are two
web servers that are equivalent in functionality (i.e. both have Gweb running
on the system), then DNS for the system can be configured to return both
addresses, and browsers automatically try the second if the first is down.
12
G&R/Gproxy
G&R
Glink for Java servers
GlinkjS load balancing activities must be enabled by the Gproxy command
line parameter -LBGLJ [port number]. The port number is optional, and
defaults to 30842 (the standard GlinkjS port) e.g.
Gproxy -nlb -lbglj -pt html -rt glj
Gproxy runs in default background mode, doing load balancing for GlinkjS,
and generating a GlinkjS load balance report in HTML. Load balancing for
Ggate is suppressed.
When load balancing GlinkjS, Gproxy will take over the GlinkjS port (see
GlinkjS port number) and will listen for Glink for Java client
connection requests. When a connection is received, a redirect command
containing the IP-address and port number of the GlinkjS system having the
lowest current load is sent back to the client.
GlinkjS load information is reported in the statistical network management
record that is sent out at regular intervals to Gproxy when GlinkjS is started
with the -NA/-NB parameter.
Port number
The default connection port used by GlinkjS is 30842. This is taken over by
Gproxy when load balancing is enabled so Glinkjs must be started using
another port using the GlinkjS server's -LP command line parameter e.g.
glinkjs –lp 30844 –nb
Client configuration
configserver=myserver.acme.com
server.port=30844
backupserver=mybackup.acme.com
backup.port=30844
The GlinkjS system and port are specified in glink.ini. In this case Gproxy
would be running on both systems for robust load balancing.
G&R/Gproxy
13
G&R
14
G&R/Gproxy
G&R
License sharing
In a multiple system Host Links configuration, Gproxy by default operates
as a license server for Host Links programs if the licenses have a site limit
in addition to the system limit. In such a shared license configuration Gproxy
must run on all Host Links systems sharing licenses.
When operating in license server mode, Gproxy is responsible for allocating
and de-allocating licenses for the local applications, and distributing license
statistics information periodically to other Gproxy license servers. The license
statistics allow Gproxy to know the state and current usage of the shared
licenses on all the Host Links systems, and in the event that one or more of
the systems should fail, makes it possible for the remaining servers to take over
the licenses belonging to the failing systems.
A license server HTML report can be generated. It shows the status and license
usage of all the license servers in the configuration and is updated each time
license statistics are broadcast.
Initializing the license server
When Gproxy starts it reads through the local license file looking for shared
license entries. A shared license is one for which there is a site limit in addition
to the system limit. Currently Ggate, Gweb and GlApi and UNIX/Linuxbased emulator licenses (Qsim, V78sim, G3270) can be shared. If a shared
license is found Gproxy starts a license server child process. The child initiates
license usage structures and license server pipe-files for all shared license
entries. It then starts its normal license routine, listening for license statistics
from other license servers and broadcasting its own license tables.
Requesting a license
All license entries are maintained in a local license pool. The license pool is
built the first time any Host Links application is started on a system and it is
located in the system’s shared memory.
G&R/Gproxy
15
G&R
Host Links applications check their license when they start. If the license is
not shared, they simply request a license from the local license pool. If the
license is shared, they initiate a connection to the license server over the license
server pipe-file. The Gproxy license server process receives this license request
and returns the first available license it finds in the license pool, or rejects the
request if none are available. When the Host Links application terminates,
it calls the license server to release the license.
License back up
A Gproxy license server knows the maximum and current license load of the
systems in the configuration from the license statistics that are periodically
(default every 10 seconds) broadcast by each Gproxy in the configuration when
operating in license sharing mode. If a Gproxy license server stops sending
license statistics, it is assumed that the system on which it is running has failed.
The active license server(s) detect this and automatically take over the failing
system’s licenses. In a configuration with multiple active license servers, the
failing system’s licenses will be shared evenly between the remaining license
servers.
When a Gproxy license server starts, it expects other Gproxy license servers to
have reported their license statistics within an initialization period (currently set
to 5 minutes). If the sum of the license limits reported by the other systems
does not reach the configured ‘site limit’ within this initialization period,
Gproxy assumes that one or more systems must be inoperative and this triggers
the license backup routine as described above.
Restoring license limits
Whenever a new Gproxy license server is detected, any existing license servers
adjust their license tables to reflect their share of the site limit. If this new
system is a known (previously active) system that comes back on line, the
license servers restore their original license limits and resume normal
processing.
16
G&R/Gproxy
G&R
License communities
A license server operates in a ‘license community’ if a license entry has a
‘community number’. In such cases, the license server will only maintain
license information reported by servers in the same community. If the license
community number reported in a broadcast is not identical to the one in the
license entry, that license broadcast is simply ignored. This makes it possible to
divide an intranet of production systems into several license ‘subnets’ or to mix
test systems and production systems without confusing the license server
routines.
Using ‘backup only’ licenses
A shared license entry can have a license limit of zero. This license entry is
ignored until one or more systems in that license configuration is not
functioning i.e. it is treated as a ‘backup only’ system. In a backup situation (if
one or more systems stops working) its site license is activated and the system
takes its share of the shared license. A ‘backup only’ system is deactivated
again when the license network is fully operational i.e. when the failing system
is back on line.
G&R/Gproxy
17
G&R
18
G&R/Gproxy
G&R
Alarms
Gproxy optionally generates a log of ‘Alarms’. This log is in HTML format
and contains error messages that are generated by Host Links applications.
Typically Host Links applications call the alarm routines whenever an
event has taken place that might need some sort of manual intervention.
The alarm log makes it easier for the administrator to investigate possible
abnormalities and simplifies the task of finding significant error messages
which otherwise might be located in various log and trace files.
There are 4 Gproxy alarm severity levels:
6
4
3
2
–
–
–
information
low/warning
high/error
critical
Gproxy takes a command line parameter -ALM N, where N sets the Gproxy
severity level i.e. the lowest severity (highest number) to be included in the
HTML alarm log e.g. -ALM 3 results in ‘error’ and ‘critical’ alarms only.
The Alarm routines are implemented in Gspool, GUFTsrv, Listener and in
Ggate. Alarm routines are also called from some of the central subroutines that
are used by most Host Links server programs.
The alarm text library
The alarm text library is located in the ‘misc’ subdirectory:
Windows server
\gar\misc\alarm
UNIX/Linux
/usr/gar/misc/alarm
It is a plain text file and can be modified or translated to suit the installation.
The severity levels can also be changed, but the record format must be
correctly maintained.
G&R/Gproxy
19
G&R
The following is an extract of the alarm library:
# Format: NNNN M,text string
# NNNN = 4 digit alarm number
# M = 1 digit alarm level, 6=info, 4=warning, 3=error, 2=fatal
# e.g. Error 1234 with severity 3 and text ‘Warning’ is coded:
# 1234 3,Warning
###########################################################
#
# 100 - Listener texts
#
0101 2,Could not initialize Gmonitor information
0102 3,The Gstart DLL could not be loaded
0103 3,Failed to allocate memory for listening application
0104 3,Refusing incoming connection request
#
# 200 Ggate
#
0201 2,Accept client socket failed
0202 2,Invalid Ggate license
0203 2,Could not open Ggate server structure
0204 2,Could not open Log file
0210 3,Insufficient Ggate client licenses
0211 4,Operator requested DISConnect of all clients
#
# 300 Gspool
#
0304 3,Macro not defined
0305 3,Gspool failed to open and write to file
0306 3,Gspool will now abort DPF8 connection
0307 3,DPF8 report count reset to 0, report files removed
0308 4,DPF8 STOP command received
0309 3,Printdata received for unknown printer
20
G&R/Gproxy
G&R
The alarm log
The following is an example of an Alarm log:
G&R/Gproxy
21
G&R
22
G&R/Gproxy
G&R
SNMP support
Gproxy can act as an SNMP ‘proxy’ agent. SNMP support is enabled by the
-mipN command line parameter. In SNMP mode, Gproxy sends SNMP
‘enterprise specific traps’ to SNMP network management systems. Up to 4
SNMP management systems can be addressed. SNMP traps can be filtered
using the ‘exclusive filter’ parameter, -efX. Generation and distribution of
SNMP traps is a background task that takes place independent of other (output) activity.
The SNMP trap format is available as an enterprise specific MIB extension.
Two trap formats are used: ‘event trap format’ (used by enterprise specific trap
1,2 and 3) and ‘statistic trap format’ (used by enterprise specific trap no.4). See
appendix for a detailed description of the G&R MIB extension. See also the
formatted dump of the SNMP traps.
Gproxy does not support SNMP ‘get’, ‘getnext’ and ‘set’ commands.
G&R/Gproxy
23
G&R
24
G&R/Gproxy
G&R
Startup/Configuration
Parameters
Gproxy takes parameters from the command line and/or from a configuration
file, gproxy.cfg located in the standard Host Links configuration directory
i.e.
/usr/gar/config/default/gproxy.cfg
Parameters from the command line override parameters from the configuration
file. The configuration file expects a single parameter (with qualifier if
appropriate) per line. Any text to the right of a [* ; #] character is regarded as
a comment.
Gproxy accepts the following parameters:
Parameter
Description
-alm N
Enable Alarm HTML report and set the severity level N:
6=info, 4=low, 3=high, 2=critical. All levels less than N
are also reported. N=3 reports high and critical
-bg ON/off
Sets Gproxy in background mode and runs as a server
-ci 10
Check interval in seconds. How often Gproxy checks for
inactive gateways and updates status information
-co name
SNMP community name used by the receiving SNMP
entity
-dbg on/OFF
Activate Gproxy tracing
-efX
Exclude forwarding SNMP traps of broadcast record
type X. This parameter is positional i.e. must follow the
–mipN parameter to which it applies
-erX
Exclude reporting of broadcast record type X (1-8)
G&R/Gproxy
25
G&R
Parameter
Description
-gga addr
Monitor the Ggate gateway running on the specified IP
address (necessary for Ggate report mode)
-glj addr
Monitor the GlinkJ server running on the specified IP
address (necessary for GlinkjS report mode)
-hp path
HTML path. Default SYSDIR/html/gproxy
-idt GUID/IP
Client identification type. Default IP
-ipn ON/off
Use numeric/symbolic IP addresses (reports)
-lbgga portno
Load balance Ggate. Default ON with port 30841
-lbglj portno
Load balance GlinkjS. Default OFF. Default port 30842
-lbgwb portno
Load balance GwebS. Default OFF. Default port is 80
-lbweb portno
Load balance other web server. Default port is 80
-lic on/off
Enable license server activity. Default enabled if license
file contains site limits
-ln scid
Local DSA node name. Defaults to the local node from
the DSA configuration file
-log ON/off
Activate logging. Writes a summary record to the log file
for each broadcast received. When in ‘server mode’, the
log file will be located in the server directory
/usr/gar/servers/SCID.gpr/
Otherwise the log file will be opened in the working
directory
-logsz KB
Sets the limit of the log file. Default 64KB
-mipN addr
IP address of the SNMP management system. Up to 4
management stations are supported (i.e. N = 1-4). If
no SNMP IP address is given, SNMP activities are
disabled
-myip addr
IP address of the system on which Gproxy is running.
This should not normally be needed, but Gproxy can fail
to find its own address on systems with multiple network
cards (or an incorrect network configuration)
-nlb on/OFF
Disable Ggate load balancing (enabled by default)
26
G&R/Gproxy
G&R
Parameter
Description
-pt vdu html
all
Presentation mode. Set to VDU, HTML or ALL if
Gproxy should generate reports. Defaults to no
reporting. Setting VDU forces background OFF
-rt type
If presentation type (-pt) is set. Possible report types:
types
SUM – summary report
DET – detail report
GGA – Ggate load balance report
GLJ – GlinkJ load balance report
GWB - Gweb load balance server report
LIC - license server report
MIB – MIB report
RTE - route report
SES – session report
USR – user report
HEX – hex dump report
ALL – all reports except ‘summary’
Several –RT parameters can be supplied
-si secs
Time before an inactive server is considered defunct
-snf IPmask
Gproxy should redirect Glink connection to Ggate
systems in the same subnet first. Sets mask to be used to
check for the same subnet
-sno IPmask
If Gproxy should redirect Glink connection to Ggate
systems in the same subnet only. Sets mask to be used to
check for the same subnet
-ssi ssi
SSI (Server Side Include) extension used for HTML
pages that need server-side update. Default ‘SSI’
-uc 512
Max user count. Number of users monitored in ‘user’
report mode. Maximum 4096. Defaults to 512
-websport
Port used by non-G&R web servers for which Gproxy is
doing load balancing.
For SSL parameters, see the G&R/SSL manual.
G&R/Gproxy
27
G&R
Command line examples
gproxy
Gproxy runs in background mode doing load balancing for Ggate, logging of
all incoming broadcasts in the G&R server directory and license server
processing if the license contains a site limit.
gproxy –nlb on –lbglj 30845 –pt html –rt glj –glj hlpc
Gproxy runs in background mode doing load balancing for a Glinkj server on
port 30845, and generating a report showing usage of the Glink for Java server
on the system having the IP-address hlpc. It does license server processing if
the license contains a site limit. Load balancing is disabled for Ggate.
gproxy -pt html –rt sum -rt lic -rt gga –er4
Gproxy runs in background mode with load balancing for Ggate. It does license
server processing if the license contains a site limit. A summary report, load
balance report and a license server HTML report are generated. Record type 4
is ignored (on the summary report).
Given the following gproxy.cfg file:
*
* Parameters file for Gproxy on 192.111.222.24
*
-co secret
-mip1 saturn
; Manager on ‘Saturn’
-ef2
; Ignore disconnects
-mip2 pluto11
; Manager on ‘Pluto11’
and this command line:
gproxy –pt html –rt gga
Gproxy runs in background mode showing Ggate load balancing statistics in a
HTML report. SNMP support is enabled and Gproxy communicates with the
SNMP ‘community’ secret It forwards all broadcasts as SNMP traps to IPaddress saturn and forwards all broadcasts except type2 (disconnects) to
pluto11. It does Ggate load balancing (default).
28
G&R/Gproxy
G&R
Gproxy input data
Gproxy receives and acts on network related administrative data records that
are optionally broadcast by Host Links components (most importantly line
handlers and gateways) in the network. They report statistical information or
details of connections, disconnections, error events and backup-route
switching. The following record types are defined:
Type 0 – alarm record
These records contain Alarm information e.g. severity and error text. Host
Links server programs send alarms. The record is used for the Alarm log.
Type 1 - connection event record
These records contain data on a DSA connection event. It includes addresses
and names of the client, the application and the host, and a list of all the Gline
parameters given (and default) for the session. The line handler (gl_dsa)
generates this record type when -NA or -NB is among the Gline parameters.
Type 2 - disconnection event record
These records contain information about normal user or application-initiated
disconnects. The line handler (gl_dsa) generates this record when a client
disconnects and -NA or -NB is among the Gline parameters.
Type 3 – Connection failures
These records contain information about unsuccessful connection attempts.
Both the error-code and error-text are supplied, as well as the parameters used
in the failing request. The line handler (gl_dsa) generates this record when a
client connection request fails and -NA or -NB is among the Gline parameters.
G&R/Gproxy
29
G&R
Type 4 – Statistics record
These records contain statistical information about gateway load and resource
usage. Ggate and the Glink for Java server generate them for use in
load balancing and load reports.
Type 5 - Route state event record
These records contain information about network events that cause a change in
a network route state. The state is changed either automatically due to an
unsuccessful network connection, or as a result of an operator update command
(using either the gtsupd utility or an internal Gproxy service command).
Type 6 – Glink for Java Logon request record
These records contain information about a client registering itself with the
Glink for Java server. Used for the GlinkJ server report.
Type 7 – Gweb statistics record
These records contain statistical information about Gweb load and resource
usage. Gweb generates them for use in load balancing and load reports.
Type 8 – License statistics record
These records contain information about shared license resource usage. Gproxy
generates them when license sharing is enabled.
30
G&R/Gproxy
G&R
Gproxy reports
Administrative records broadcast from the various Host Links components will,
as long as the event is relevant for the chosen report and not explicitly excluded
by the -erX parameter, cause reports to be generated or updated if reporting is
enabled (-pt). The report types generated or updated can be specified
individually (several -rt) or collectively by means of -rt ALL (note that
ALL does not include the ‘summary report’).
Gproxy supports two presentation modes, VDU and HTML. In VDU
presentation mode the event will immediately be visible in the current report on
the user’s terminal. VDU mode requires that Gproxy is run in the foreground.
In HTML mode a new HTML page is generated and will be sent to the browser
using a ‘push-technique’ without any interaction from the browser user. This
documentation will focus on HTML mode.
Several report types are supported and enabled by command line arguments at
Gproxy startup time. The HTML reports are displayed in separate browser
windows. The administrator can display all reports that are of particular
interest, or can choose to have the summary report active and select the
appropriate report whenever an interesting network event occurs in the
summary report.
The following is a description of the report types generated by Gproxy.
G&R/Gproxy
31
G&R
The System report
The system report is a collection of valuable information otherwise found on
several other reports. It is generated automatically whenever the –PT HTML
parameter is set and is the natural choice of report in a daily monitoring
situation. The report is updated every ‘check interval’ (default 10 seconds) and
contains the following:
System information:
IP address
Local IP address
Node name
Local node name (DSA SCID)
System ID
Local system ID (computer name)
Time
Last time stamp
Base directory
Host Links base directory (SYSDIR)
Started
Gproxy start time
Static license information:
32
Installation
Customer name
Platform
Type of platform (e.g. Windows)
Release
Current release number
SSL Mode
If operating in SSL Mode
Customer no
Customer number
Ref. No
License reference number
Community
License community number
G&R/Gproxy
G&R
License server information (one line per shared license entry)
License name
The name of the license entry
Used
Number of licenses currently in use
Max
Current maximum number of licenses (current limit)
Org
Original maximum license limit
Site
The site limit
Corp
Corporate limit (for future use)
Load balance information (one line for Ggate, web server and GlinkjS)
Port
Port number used for client connection to server
Servers
Number of servers in this network
Best
Current ‘best’ server
Load factor
Load factor (normally current number of connections)
Redirects
Number of redirects since startup
Event information (one set for each record type: license stats, gateway stats,
connect events, connection failures, GlinkjS stats, Alarms, GwebS stats,
disconnect events, route events and IO counts):
Number
Number of records received (since last update)
Total
Number of records received (since startup)
G&R/Gproxy
33
G&R
Example System report:
34
G&R/Gproxy
G&R
The Summary report
Each broadcast network event generates a single line of output in the summary
report, and the report covers the 16 most recent events. Please note that
generating the summary report is resource intensive, since every event
generates 16 individual 'detailed reports’ that you can access from the Event
link on the summary report line.
For each of the events the following fields are shown:
Event
Gproxy internal event sequence number
Time
The time Gproxy received the information
Component
The name of the reporting program
Address
The network (IP) address of the reporting program
SNMP status
Indicates if the event was reported as an SNMP trap
Event type
Event (record-) type
G&R/Gproxy
35
G&R
Click the ‘event’ link for a closer look. A new browser window will be opened with
a detailed view of the chosen entry.
36
G&R/Gproxy
G&R
The Detail report
In the detail report a network event generates a full screen of data. It displays
all elements of the administrative record. This always includes names,
addresses, time-stamp and event serial number of the reporting program, as
well as the name and address of the client (i.e. in the case of an event reported
by a gateway application). In the case of host connection requests, all the
parameters used by the line handler (including defaults) are shown. In the case
of a failing host connection, any error text returned by the host or generated by
the line handler or the underlying communication stack is also shown.
The following is an overview of the fields reported:
Statistics records:
Event no
The serial number of the reported event
Time
The time the event was reported
SNMP status
Values: ok, failed, Ign, N.A.
Program
The name of the reporting Host Links program
Network address
The IP address of the reporting component
Serial no
The number of the Gproxy event
Uptime
Seconds since startup (of the reporting component)
Sent host
Number of bytes sent upstream
Sent client
Number of bytes sent downstream
Sessions
Total no. of sessions through this gateway
High
Highest no. of simultaneous sessions
Max
Maximum (set by license)
Route records:
Event no
The serial number of the reported event
Time
The time the event was reported
SNMP status
Values: ok, failed , Ign., N.A.
Program
The name of the reporting Host Links program
Connects, disconnects and error records:
G&R/Gproxy
37
G&R
Event no
The serial number of the reported event
Time
The time the event was reported
SNMP status
Values are: ok, failed, Ign., N.A.
Program
The name of the reporting Host Links program
Client
Name (userid) of the client
Address
Client network address (if gateway type)
Host name
The DSA (SCID) name of the host system
Coname
Name of dsa.config ‘coname’ entry if used
Network address
The IP-address of the reporting component
Serial no
The number of the Gproxy event
Uptime
Seconds since startup (of the reporting component)
Sent host
Number of bytes sent upstream
Sent client
Number of bytes sent downstream
Example Detail mode report:
38
G&R/Gproxy
G&R
The Ggate Gateway report
In gateway mode Gproxy monitors the usage of a specific Ggate gateway. The
address of the gateway can be given on the command line (using the -gwa
parameter) or can be entered interactively using the Gproxy command
interface. In gateway monitor mode, key information from the most recent
event reported by the monitored gateway is shown in the first few lines. Then
for each user connected through the gateway follows the process ID (PID), the
users IP-address and the host name to which the user is connected. In VDU
presentation mode, if there are more users connected through the gateway than
can be shown on a single screen, you can ‘navigate’ by means of the page-up
and page-down keys on the keyboard.
The following information is shown:
The headings:
Program
The name and version of the gateway being monitored
Serial number
Serial number of the last event reported by this gateway
Uptime
The ‘uptime’ (in seconds) for this gateway
KB Up
The number of K bytes moved upstream (to host)
KB Down
The number of K bytes moved downstream (to client)
Sessions
The current number of host sessions
Hi
The highest number of host sessions registered
Max
Maximum number of session (allowed per license)
Users
The current number of host users
Hi
Highest number of users registered
Max
Maximum number of users (allowed per license)
Per session:
PID
Process ID of the line handler
Username
The network address (IP address) of the user
UID
User identifier (if supplied by the client)
G&R/Gproxy
39
G&R
Example Gateway mode report:
40
G&R/Gproxy
G&R
The Load balancing reports
Gproxy produces a load balancing report mode for each server type (Ggate,
GlinkjS, GwebS). Each report shows load information for every server of
that type known to Gproxy (i.e. configured to send statistical information to
Gproxy). The report reflects the current state of the ‘load tables’ used for load
balancing purposes. The ‘best’ (lowest load) gateway is indicated i.e. this is the
gateway that will be suggested in the redirect record for the next client
connection.
The following information is shown per gateway:
Gateway address
The network address of the gateway
Port
The port number
Load
Current number of sessions
Fact
The load factor (used in calculation of ‘best’ gateway)
Tres
Threshold value (max) set for this gateway
High
The highest number of session registered
Max
The maximum (set by license)
Updated
Time stamp last update
Remarks
Indicates ‘best’ gateway or ‘disabled’ gateway
G&R/Gproxy
41
G&R
Example load balancing report:
42
G&R/Gproxy
G&R
The Glinkj server report
In GlinkJ server reporting mode Gproxy maintains a table of clients connected
to a given GlinkJ server. The address of the GlinkJ server must be given in the
–glj command line parameter at Gproxy start time. The table is updated each
time Gproxy receives a ‘logon record’ broadcast from the GlinkJ server when a
client connects. The report is only available in HTML format.
Example Glinkj server report:
G&R/Gproxy
43
G&R
The License server report
In license reporting mode Gproxy gathers license statistics from all Gproxy
systems known to it, including itself if license server activity is enabled by
parameter (-lic) or default. All shared licenses for all servers are shown. The
license name, current usage, the original maximum license count and the
maximum site limitations are reported.
The example below shows a configuration with 2 known Gproxy systems
acting as license servers.
The second one, hobby.gar.no, is no longer reporting its counters and Gproxy
on arildxp.gar.no has assumed that hobby has failed, and taken over its shared
licenses.
Example License server report:
44
G&R/Gproxy
G&R
The Route report
In route mode Gproxy collects information about the state and usage of all the
configured transport routes configured in the TS directives in the dsa.cfg
configuration file. Each time a host connection is established or terminated, the
line module will update the count for the TS route used and a route statistics
record will be forwarded to Gproxy. In a backup route configuration, an
unsuccessful connection attempt causes Gline to set the TS route in question
in a disabled state. Such state changes are also detected and reported on the
output report.
The following fields are shown:
TS route name
The route name i.e. the name configured in the TS directive in
dsa.cfg.
NSAP
The network address as configured in the -NS parameter of
the TS directive.
State
The route state (possible values: down, lock, disa, enbl and
used)
Sessions
# of session - number of session using this route
G&R/Gproxy
45
G&R
Example Route mode report:
46
G&R/Gproxy
G&R
The User report
In user report mode Gproxy maintains a table of all Host Links users and the
number of sessions in the network. The definition of a ‘user’ depends on the
setting of the –uid command line parameter and is either a unique IP-address
or a unique UserID (GUID). The number of users monitored is set using -uc
N (N defaults to 512, maximum 4096) The table is updated every time Gproxy
registers a connect, disconnect or error broadcast.
The following fields are shown:
Heading info
Users
The current number of users
HiUser
Highest number of users allowed
HiReg
Highest number of users registered
Max
Maximum number of sessions (allowed per license)
Sessions
The current number of sessions
HiSess
The highest number of sessions registered
Per user
User IP
IP-address
Sessions
Number of active sessions this user
KB Up
The number of K bytes moved upstream (to host)
KB Down
The number of K bytes moved downstream (to client)
UserID
GUID, if supplied by the client application
G&R/Gproxy
47
G&R
Example User mode report:
48
G&R/Gproxy
G&R
The Session report
In session reporting mode Gproxy maintains a table of all Host Links sessions.
The table is updated ever time Gproxy registers a connect, disconnect or error
broadcast. The report is only available in HTML format.
Example Session report:
G&R/Gproxy
49
G&R
The MIB report
In MIB reporting mode all relevant information is displayed in SNMP MIB
format. Each field is prefixed with its SNMP ‘object ID’, ‘object name’ and its
value.
The following fields are shown:
Statistics:
progno
internal number of the reporting component
progname
the name of the reporting component (Host Links program)
progaddr
the network address (normally the IP-address)
pid
the program ID
serialno
the number of the Gproxy event
sessionno
total no. of session through this gateway
max
maximum number of sessions this interval
min
minimum number of sessions this interval
event no
the serial number of the reported event
upstreams
number of bytes sent to host
downstreams
number of bytes sent to client
Connections, disconnections and errors:
50
progno
internal number of the reporting component (Host Links
program)
progname
name of the reporting component
progaddr
network address (normally the IP address)
pid
program ID
serialno
number of the Gproxy event
username
applicable to GWDNTD gateways only
useraddr
network address (IP-address) of the user
session number
applicable to gateways
hostname
name of the host (normally DSA remote session ID)
retcode
return code (applicable to connect errors)
G&R/Gproxy
G&R
timeofday
of the event
error text
(if connect failure)
coname
correspondent name (from dsa.cfg)
parameters
all given and generated parameters (connects and errors)
Example MIB report:
G&R/Gproxy
51
G&R
The ‘HEX report’
In HEX mode the UDP record is displayed 16 characters per line in
hexadecimal and printable ASCII as shown in the following:
52
G&R/Gproxy
G&R
Administration
Gmanager operator commands
When operating in background server mode, commands must be given through
the command interface in Gmanager (see the Host Links server
administration appendix below). Select the Gproxy server (position by means
of the curser up/down keys) and click ‘send server command’ (F3 in the
character based version of Gmanager). The following commands can be
given:
Command
Parameter
Description
DOWN
Terminates Gproxy
STATUS
Request that status information be reported to
the log file
PARAM
Brings up a dialog box or command line that
allows you to feed any parameter to Gproxy.
Please note that some parameters might not
work when given interactively i.e. they can
only be given at server start time
DEBUG
ON/OFF
Toggles on and off tracing and debugging
interactively
NUMI
ON/OFF
Toggles numeric IP format on and off i.e.
switches between use of numeric and
symbolic (host name) IP-address format
DISABLE
gga/gwb/glj
IPaddress
Disables a server for load balancing e.g.
DISA gga gars.gar.no
ENABLE
gga/gwb/glj
IPaddress
Enables a server for load balancing e.g.
ENAB gga gars.gar.no
SILENT
TSUPD
G&R/Gproxy
Stop generation of output reports
route state
Set a transport route to a given state. See the
53
G&R
gtsupd utility for parameters
Monitoring Gproxy
When Gproxy is started with the –sv (server) parameter it executes in the
background. None of the Gproxy VDU output screens are generated and there
is no command interface. As all other Host Links server programs, Gproxy
reports its current status to the Gmanager database. This can be viewed using
the UNIX, DOS or Windows version of Gmanager. If the G&R system
directory on a file server is shared by several Host Links platforms,
Gmanager shows the status of all Host Links servers on all the Host Links
platforms sharing the G&R system directory. Gmanager’s active server list
shows you the most recent status message from any Gproxy sharing the G&R
system directory, and you can view the log files at the touch of a key or a
mouse click. You can also terminate Gproxy by sending it the DOWN
command from Gmanager.
Gproxy logging
If the log file is enabled (-log, default ON), essential information from the
administrative records received is written to the log file. If Gproxy is
configured to run as a G&R server, the log file will be created in the G&R
server directory, otherwise the log file will be located in the current directory.
The following is an extract from a Gproxy log file.
[2003/09/11 15:00:17] G&R/Gproxy 6.1.0/m32pc Jul 19 2003 started
[2003/09/11 15:00:17] Thu Sep 11 15:00:17 2003 15ac357f:
1 G&R A/S:G&R A/S:*:1:1 for Gproxy:*:0:0:0:0:*
[2003/09/11 15:00:17] 1x 2519MHz Intel(R) Pentium(R) 4 CPU 2.53GHz 83MB
[2003/09/11 15:00:17] Command line:
-dbg -alm 6 -lbgwb 8080 -lbgga 30841 -pt html -rt all -na arildxp
[2003/09/11 15:00:17] CreateLicChild
[2003/09/11 15:00:18] BrdCst: GWBstat Prog: Gwebs 611, Addr: raider.gar.no
[2003/09/11 15:00:18]
Req. cmplt:42, running:0, sess. cmplt:3, running:0
[2003/09/11 15:00:21] BrdCst: GGAstat Prog: Ggate 610, Addr: arildxp.gar.no
[2003/09/11 15:00:21] LicDialog, granted Ggate license 1 to pid=5932
[2003/09/11 15:00:21]
Curr user: 0, max: 100, high: 0 Curr sess: 0 high:0
[2003/09/11 15:00:22] BrdCst: GWBstat Prog: Gwebs 610, Addr: andersh2.gar.no,
Serial: 59374
[2003/09/11 15:00:22]
Req. cmplt:43, running:0, sess. cmplt:6, running:11
[2003/09/11 15:00:27] BrdCst: GWBstat Prog: Gwebs 610, Addr: jim2.gar.no
[2003/09/11 15:00:27]
Req. cmplt:0, running:0, sess. cmplt:0, running:0
[2003/09/11 15:00:28] BrdCst: GWBstat Prog: Gwebs 611, Addr: raider.gar.no
[2003/09/11 15:00:28]
Req. cmplt:42, running:0, sess. cmplt:3, running:0
[2003/09/11 15:00:32] BrdCst: GWBstat Prog: Gwebs 610, Addr: andersh2.gar.no
[2003/09/11 15:00:32]
Req. cmplt:43, running:0, sess. cmplt:6, running:11
[2003/09/11 15:00:35] BrdCst: GGAstat Prog: Ggate 610, Addr: arildxp.gar.no
[2003/09/11 15:00:35]
Curr user: 0, max: 100, high: 1 Curr sess: 0 high:1
54
G&R/Gproxy
G&R
Appendix: Host Links
Manuals
Below you find a complete list of all available Host Links manuals:
Installation
Host Links Servers
Installation and Configuration on UNIX/Linux
Host Links Emulators
Installation and Configuration on UNIX/Linux
Host Links
Installation and Configuration on Windows
Line handling
Gline
Line Handler and DSA/OSI Configuration
Ggate
Transparent Gateway
Gproxy
Network Manager & SNMP Proxy Agent
G&R SSL
Using SSL for security in G&R products
GlAPI
Application Programming Interfaces
Emulations
Gspool
Network Printer Emulation
GUFT
Unified File Transfer
G3270
Emulating IBM 3270 Terminals
G5250
Emulating IBM 5250 Terminals
Pthru
Gateway to the Bull Primary Network
Qsim
Emulating Questar DKU7107-7211 & VIP7700-7760
V78sim
Emulating VIP7801 & VIP7814
Gweb
Web Browser Front-end for DKU, VIP7700-7760,
VIP7800, IBM3270 and IBM5250 Emulations
G&R/Gproxy
55
G&R
56
G&R/Gproxy
G&R
Appendix: Host Links
License Keys
All G&R products require a license key to run. If you are a G&R distributor
you need a license key from G&R. If you are a customer you should have
received the license keys from your distributor together with the software. The
licenses are stored in text format in a file named licenses.
If licenses is delivered with the product files, it is merged with any existing
licenses in the configuration directory when you run the install procedure.
UNIX/Linux
/usr/gar/config/licenses
Windows server
C:\gar\config\licenses
Glicense
The Glicense program is included in every software delivery, and it can be
used even though no license key is installed. This allows you to create or
modify your own licenses from a license card. You must execute Glicense
from a user-id that has permission to write in the configuration directory (i.e.
the Host Links administration user gar for Host Links). When executed with
no parameters, Glicense will check for an existing licenses file. If found
it will skip directly to the command dialog, but if there is no license then it will
prompt you for distributor name, customer name and the main license key. Be
careful to type the names and the key exactly as given to you by your
distributor. It is important that you respect case and spaces between words.
To tell Glicense explicitly where the license file is, or where it should be
written, supply the full path as an option. For example:
glicense /usr/gar/config/licenses
Enter the license information, text and keys, exactly as specified on the
supplied license card.
G&R/Gproxy
57
G&R
Once the first time installation has been done, you can simply run Glicense
without any options and it will automatically find the licenses file.
When started Glicense gives you the following prompt:
Enter command or '?':
If you enter '?' a list of the available commands is returned:
Use these commands to define/modify and save the licenses file.
A = Add
Add a new product to the license file.
D = Delete
Delete a product from the license file.
R = Read
Read in a new license file.
M = Merge
Merge in license keys from a license file
W = Write
Save the license file.
P = Print
Display a list of configured products.
N = New
Create a new license file.
H = Hardware
Change the hardware platform
X = eXpiration
Define an expiration date for all products.
V = Version
Set new version for all products
Q = Quit
Quit the Glicense program.
ENTER
The ENTER key quits Glicense
If you enter the Print command, the result will be something like this:
Enter command or '?': p
Distributor: Bull A/S
Customer: Arbeidsdirektoratet
Product: Basic
Product: Gline
Product: Ggate
Product: Gspool
Product: Qsim
58
G&R/Gproxy
G&R
License keys
Below you find a complete list of all Host Links and Glink for Java license keys:
License key
Products that require this key
basic
All products.
ggate
Ggate.
gspool
Gspool.
guft
GUFT server.
Guftc
GUFT client.
gproxy
Gproxy.
qsim
Qsim.
v78sim
V78sim.
g3270
G3270.
g5250
G5250.
pthru
Pthru.
sdkglapi
GlAPI SDK.
Glapi
GlAPI run-time.
Telnet
Enable Ggate Telnet support
Tnvip
Enable Ggate TNVIP support
ssl
Enables SSL support
Marben
Marben OSI Stack for Windows NT 4
Marben2K
Marben OSI Stack for Windows 2000
MarbenXP
Marben OSI Stack for Windows XP
Marben03
Marben OSI Stack for Windows 2003
Gweb
Gweb Professional Edition All terminal emulations
Gljopen
Glink for Java Open (VTnnn/ANSI/Minitel).
Gljpro
Glink for Java Professional Edition.
G&R/Gproxy
59
G&R
License key
Products that require this key
Gljent
Glink for Java Enterprise Edition.
Gljall
Glink for Java All terminal emulations.
Gljsa
Glink for Java Standalone (No configuration server).
Gljsrv
Glink for Java Server (Configuration and License).
Gljcnx
Glink for Java Gconnect (J2EE connector)
Gljdsa
Glink for Java DGA (native DSA comms stack)
Gljggen
Glink for Java Gargen
60
G&R/Gproxy
G&R
Appendix: Host Links Server
Administration
Gmanager is the Host Links administration tool. It can be used to control,
configure and monitor all the G&R Host Links server programs.
The dialog and interaction between the server programs and Gmanager is based on
information located in a database file _active.srv that is located in the Host
Links servers directory. The first time a Host Links server program starts up it
registers itself in this ‘active’ file. Thereafter the server program updates this
database with status information whenever the server is active.
The Gmanager program is available in 2 different versions – a Windows GUI
based version gmanw.exe and a character based subset gman (UNIX/Linux
binary) or gman.exe (PC console application).
The basic functionality of the two versions is the same, but the Windows version
interfaces directly to other Windows-only Host Links administrative tools
(Gconfig, Gservice), and can also start the browser directly to view HTML
reports produced by Gproxy, if enabled, or to view the HTML pages associated
with a Gweb or Glink for Java installation.
The Gproxy reports, Gweb and Glink for Java web pages are of course
available to administrators of UNIX/Linux Host Links systems, and can be viewed
by starting a browser manually, and connecting to the appropriate URLs:
http://mysite.mydomain.com/Gproxy
http://mysite.mydomain.com/Gweb
http://mysite.mydomain.com/GlinkJ
A summary of the available functions follows. The Windows-only functions are
marked.
G&R/Gproxy
61
G&R
Gmanager can be used to perform the most common Host Links administrative
tasks i.e.:
View the last reported status information from the servers
Start new server
Restart a server
Send a command to a server
View a server log file
View a server trace file
Load the DSA configuration into an editor
Compile the DSA configuration
Call Gconfig the server configuration program (Windows)
Start the configuration wizard (Windows)
Load the Gservice configuration into an editor (Windows)
Start the Host Links server programs using Gservice (Windows)
Edit the product specific configuration files
Connect directly to the Gproxy HTML pages, if enabled (Windows)
Connect directly to the Gweb HTML pages, if enabled (Windows)
View program version numbers, program link information (Windows)
View license info and license usage (Windows)
View Host Links environment information, the ‘VMAP’ (Windows)
62
G&R/Gproxy
G&R
The commands that are accepted by all servers are:
DOWN - terminates the server
STATUS - reports server-specific status information to the log file
PARAM - brings up a dialog box that allows the operator to give a command
line parameter to the server. Note that some parameters do not work when
given interactively i.e. they can only be handled at server startup time
DEBUG ON/OFF - toggles on and off tracing interactively
Additionally, the server in question might support other interactive commands.
For a description of the supported commands, check the server-specific
documentation.
G&R/Gproxy
63
G&R
64
G&R/Gproxy
G&R
Appendix: Host Links DSA
Utilities
The Gline package includes a set of Gline communication utilities. These are
used when testing and debugging connection problems. The utilities are delivered as part of the Gline package and can be used without any additional configuration. The nodes to be tested must of course be configured in the dsa.cfg
file.
Gconame
Lists the parameters generated from a given CONAME. The utility works for
both CONAME and RESOURCE e.g.:
gconame tnviptm
Checking 'dsa.cfg' for coname 'tnviptm'
Coname: tnviptm, type TM, parameters:
-DA misfld
-S_
-D_
-CODE 0000
-CODE 1000
-CODE 1800
-TEXT Remote SCID?:
-CODE 4700
-TEXT Remote application?:
-CODE 1400
-CODE 1600
-TEXT Password?:
G&R/Gproxy
65
G&R
Gerror
Shows the text message associated with a DSA reason code. Only the most
common codes are supported i.e. the ones related to network, transport and session communication layers. Errors generated by the OSI-stack on the Host
Links platform are not covered by this utility; please refer to the documentation
from the vendor of the stack e.g.:
gerror 0109
Reporting component: Session control (01) 0109, Dialog
protocol error or negotiation failed (wrong logical
record).
For a detailed description of all reason codes, please consult the Bull manual
OSI/DSA Network System Messages and Return codes (39A2 26DM).
Glnode
List and verify the communications parameters of the local node e.g.:
glnode
Local node name : GRDL
Local session control id : GRDL
DSA200 address (area:tsm): 54:60 (36:3C)
Gmacfix
When you connect to FCP cards on Bull mainframes via an Ethernet port on the
LAN-Extender the mainframe address is given in Ethernet (LLC) format. If you
connect to an FDDI adapter you must convert the MAC address to SMT. e.g.:
gmacfix 080038000fab
MAC address 080038000fab = 10001c00f0d5
66
G&R/Gproxy
G&R
Gping
Connects to a remote system using the Gline parameters set on the command
line. If successful it returns ‘connected to application’, otherwise it shows the
error code returned e.g.:
gping -li dsa -dn b7dl -da iof -du jim -pw mydogsname
Gping - $$DSA: Connected to application
Grnode
Return the parameters (in dsa.cfg) and the state of a remote node e.g.:
grnode b6dl
Checking ‘dsa.cfg’ for node ‘b6dl’
Session control id : B6DL
DSA200 address (area:tsm) : 1:5 (1:5)
Inactivity interval : 0
Route 0
Load balance percentage : 0
TP class : 2
TP expedited : 0
TPDU size : 0
Network address : 130405
Gtrace
Same as gping but writes the DSA/DIWS communication trace on the user’s
terminal (applicable to UNIX versions) e.g.:
gtrace -li dsa -dn ln40 -da snm151
D6:Application event @ 14:17:17.6003. tokenitem = 00
D6:Application event @ 14:17:17.6082. tokenitem = 00
D6:Connect request called, node = LN40
D6:OurBufferSizes. ApplMaxXmit = 511, ApplMaxRecv = 500
Rec:4000 0002 s:2
Rec:506B 0010 s:16
etc etc
Gtrace - line trace ending.
Gtrace - $$DSA: Connected to application.
G&R/Gproxy
67
G&R
Gtsupd
Update the state of a transport route. Transport routes can be set automatically
in a disabled state if a backup route is configured. When such a state change
occurs the route will be set back to the enabled state after a configurable timer
has expired. The default is 15 minutes. You can reset the state of such a route
with the gtsupd utility e.g.:
gtsupd hipp -st enbl
TS-entry ‘hipp’ updated OK. Old state = LOCK, new state =
ENBL
68
G&R/Gproxy
G&R
Appendix: Host Links Trace
If you experience any kind of problem when using a Host Links application,
the application trace file and/or the line handler trace file will provide useful
documentation of the problem.
Trace activation
The Host Links products automatically create sub-directories in the debug
directory when debug is activated: at product level using the -dbg parameter,
or at line level using the -d_ or -s_ parameters to the line module.
Windows
server
gspool -id gs1 –dbg –ps \\SERVER\LEXMARK
-li dsa -da tptst -d_ on
UNIX
Linux
gspool -id gs1 -dbg-pc lp -li dsa
-da tptst -d_ on
Most G&R products include a facility for setting product or line parameters
dynamically. It is therefore generally possible to turn on debug or trace without
modifying the command line or configuration of a production system.
Trace types
All Host Links products accept a parameter –dbg, which starts an application
level trace of internal events. This is useful when investigating malfunctions or
looking closely at product behaviour.
All Gline line handlers accept a parameter -d_ to turn on a data trace. It
records data and enclosure level being exchanged with the line handler. It is
useful when documenting product malfunction e.g. an emulation error, because
it records exactly what the host sends and what the G&R application replies. It
can be used to simulate a customer situation, reproduce a problem and to verify
that a correction fixes the documented problem.
G&R/Gproxy
69
G&R
All Gline line handlers accept a parameter -s_ to turn on a session trace. It
records the raw data being exchanged between the line module and the underlying transport layer (e.g. OSI Transport, or TCP socket), as well as internal
events and protocol states. It is useful when investigating protocol failures such
as unsuccessful connect attempts or abnormal disconnections.
Structure
The Host Links file structure includes a debug directory to collect the trace and
debug files in one location where the permissions can be adjusted as required
for security. By default only the Host Links administrator can access the
directory. The debug directory is created by the initialization procedure and
located (by default) in:
Windows
server
\gar\debug
UNIX
Linux
/usr/gar/debug
If the application is a client type of application, a debug sub-directory with the
same name as the user (UNIX username or PC login name) is created and all
debug files are located there. This includes the line level trace except in the
special case where the client application connects via Ggate and the line level
trace is written on the Ggate system using the Ggate DSA node name as a
debug sub-directory.
If the application is a server type of application, then a sub-directory will be
created using the DSA node name on behalf of which the server application is
executing. If the server does not use DSA the default local session control
name is still used if there is a dsa.cfg file. If there is no dsa.cfg file then
the system’s UNIX or Windows communications node name is used. You can
find this name using the command uname –n on UNIX systems, or the
Network section of the control panel on Windows systems. This covers
situations where several instances of a server are executing on the same system
and accepting incoming calls to different DSA node names, or where several
Host Links systems using the same server product share a file system.
70
G&R/Gproxy
G&R
Tracing Ggate
When Glink, a Host Links client or a customer application based on GlAPI
connects through Ggate to the application, the line handler trace is generated on
the Ggate system, with the name and location shown in the table:
Windows
server
UNIX
Linux
\gar\debug\NODE\ggaNN-PPPP.dbg
/usr/gar/debug/NODE/ggaNN-PPPP.dbg
NODE is the local DSA node name used by the Ggate system.
The trace file name consists of the prefix ggaNN- followed by the IP-address
of the client, suffixed by .dbg for a terminal session or –dbp for a printer
session. The following is a trace file name for Ggate session sequence number
5 executing on Host Links system GRDL initiated from a Glink client on IPaddress jim.gar.no:
gga05-jim.gar.no.dbg
This file, and possibly also a Glink debug file and a Glink communication trace
file activated by the /J command line parameter will be needed by the support
engineer investigating any problem.
To enable a line handler trace through Ggate the product’s start-up command or
configuration file would look like this:
-LI YYY:ZZZZ -S_ -D_
(YYY =line handler identification, i.e. DSA or DIWS)
(ZZZZ =IP-address of the system running Ggate)
Examples - G&R products
Examples of directory and file names in the debug structure are:
/usr/gar/debug/jim
G&R/Gproxy
Debug directory for user ‘jim’
71
G&R
72
qsm.dbg
Qsim emulator debug file
-dbg
qsm-gli.dbg
Qsim host line trace
-li dsa -s_
pth-glit.dbg
Pthru terminal line trace
-term -s_
pth-glih.dbg
Pthru -host line trace
-li dsa -s_
g32.dbg
G3270 emulator debug file
-dbg
g32-gli.dbg
G3270 host line trace
-s_
/usr/gar/debug/mike
Debug directory for user ‘mike’
v78.dbg
V78sim emulator debug file
-dbg
v78-gli.dbg
V78sim host line trace
-li dsa -s_
guf.dbg
GUFT client debug file
-dbg
guf-gli.dbg
GUFT client host line trace
-li dsa -s_
/usr/gar/debug/en01
Debug directory for node ‘en01’
guf.def
GUFT server debug file
-dbg
guf-gli.def
GUFT server host line trace
-li dsa -s_
gli-gli.dsa
DSA listener host line trace
-s_
gli-gli.diw
DIWS listener host line trace
-s_
gsp.def
Gspool (default -id) debug
file
-dbg
gsp-gli.def
Gspool (default -id) host
trace
-li dsa -s_
gga01-mike.gar.no.dbg
Ggate line trace, first Glink
-s_
gga02-mike.gar.no.dbg
Ggate line trace second
Glink
-s_
/usr/gar/debug/en02
Debug directory for node ‘en02’
gsp.abc
Gspool (-id abc) debug
file
-dbg
gsp-gli.abc
Gspool (-id abc) host
trace
-li dsa -s_
gspc-gli.def
Gspool DPF8 command
-li tcp -s_
G&R/Gproxy
G&R
trace
gspd-gli.def
Gspool DPS8 data trace
-li tcp -s_
gsp._00
Gspool started on demand
debug
-dbg
gsp-gli._00
Gspool started on demand
trace
-li dsa -s_
CPI-C and Gweb trace files
Gweb uses the CPI-C libraries so the Gweb debug structure is exactly the same
as for CPI-C, except that Gweb inserts its own product identifier into the file
name structure. CPI-C applications use the ‘client’ style of debug and create a
debug directory with the UNIX username or PC login name used by the
process that started them.
The application level debug (-dbg) and line trace (-s_ and -d_) are set in the
cpic.cfg file. The line trace goes to the debug directory, with the name built
up as follows:
<product_id><session_id>-<process_id>.<debug_type>
product_id
Value
Comment
cpi
CPI-C API
cp3
CPI-C 3270
cp7
CPI-C 7800
cpd
CPI-C DKU
gw3
Gweb3270
gw7
Gweb7800
gwd
Gwebdku
session_id
(nn)
If multi-session application, 1-63
process_id
n (n n n...)
Varies by platform
debug_type
dgb
Application level debug
G&R/Gproxy
73
G&R
gli
Line trace
Example:
\gar\debug\system
74
debug directory for user "system"
cpi-16.dbg
CPI-C single session debug
-dbg
cpi-16.gli
CPI-C single session line trace
-li dsa -s_
cpi2-123.dbg
CPI-C session 2 application
debug
-dbg
gw7-20172.gli
Gweb7800 host line trace
-li dsa -s_
G&R/Gproxy
G&R
Appendix: Error Codes
OSI/DSA error codes
Below is a list of OSI/DSA error codes and the corresponding description.
These are the same descriptions that the G&R/Gerror utility will display
when given the DSA code as a parameter.
code Description
00xx General Errors
0001
0002
0003
0004
0005
0006
0007
0008
0009
000A
000B
000C
000D
000E
000F
0010
0011
Open Failure in LC - Reject for unknown reason
Open Failure in LC - Acceptor customer node inoperable
Open Failure in LC - Acceptor customer node saturated.
Open Failure in LC - Acceptor mailbox unknown.
Open Failure in LC - Acceptor mailbox inoperable.
Open Failure in LC - Acceptor mailbox saturated.
Open Failure in LC - Acceptor application program saturated
Connection refused. Transport protocol error or negotiation failed.
Open Failure in LC - Dialog protocol error or negotiation failed
Open Failure in LC - Presentation protocol error or negotiation
failed
Open Failure in LC / Connection refused lack of system resources
Open Failure in LC / Connection refused from GCOS7 duplicate
user
Open Failure in LC, Duplicate implicit LID / Q class not started
Open Failure in LC, Duplicate GRTS Id / lack of memory resources
Open Failure in LC, No Logical line declared for DACQ / 7
connection refused
Open Failure in LC, GCOS 8 GW Missing translation / Incorrect
device length in ILCRL.
Open Failure in LC, DAC connection not initialized / Too many jobs
executing
G&R/Gproxy
75
G&R
0012
0013
0014
0016
0017
0018
0019
001A
001B
001C
001D
001F
0020
0021
0022
0023
0024
0030
0031
0033
0039
003C
003E
003F
0040
0041
0042
0044
0045
0047
004F
0050
0051
0052
0053
76
Open Failure in LC, No binary transfer / impossible to start the IOF
job
Open Failure in LC, connection is not negotiated in FD mode /
impossible to start the IOF job
Disconnection - Timeout resulting from absence of traffic.
Option missing for an RBF mailbox.
Connection refused - Incorrect access right for MB.
Connection refused - Incorrect access rights for the application.
Connection refused - Unknown pre-negotiated message path
Connection refused - Security validation failed.
Connection refused - Unknown acceptor mailbox extension.
Connection refused - Inoperable acceptor mailbox extension.
Connection refused - Invalid Message group number.
Disconnection - no more memory space.
Connection refused - Unknown node.
Connection refused - inaccessible node or Host down.
Connection refused - saturated site.
Connection refused - inoperable mailbox.
(X.25) Packet too long. Problem with packet size. / Connection
block already used.
Syntax Error - option not known (received on close VC).
(X.25) No response to call request packet - timer expired.
(X.25) Timer expired for reset or clear indication.
Disconnection - transport protocol error (MUX).
Presentation Control Protocol Error
The application has not the turn
Message group closed
(X.25) Facility code not allowed. / Connection refused - unknown
node
Connection refused - path not available.
Connection refused - Duplicate USER ID / Facility parameter not
allowed
(X.25) Invalid calling address.
(X.25) Invalid facility length.
(X.25) No logical channel available.
DNSC: (X.25) Invalid call packet length.
Normal disconnection (GCOS3/8)
Error or Event on LC initiated by GW
Error or Event on LC initiated by GW.
Error or Event on LC initiated by GW. TCall
G&R/Gproxy
G&R
0054
0055
0056
0057
0058
0059
005A
005B
005C
005D
005E
005F
0060
0061
0062
0064
0065
0066
0067
0068
0069
006A
006B
006C
006D
0078
0079
007F
0081
0082
Error or Event on LC initiated by GW. DIA in LOCK State
Error or Event on LC initiated by GW. DIA error
Error or Event on LC initiated by GW. GW has no known
explanation.
Error or Event on LC initiated by GW. Reject mailbox permanent
Error or Event on LC initiated by GW. No more input lines in
DACQ
Time-out on GCOS 3/8 gateway.
Error or Event on LC initiated by GW. Disconnect from terminal
without reason
Error or Event on LC initiated by GW. Wrong letter or wrong record
Error or Event on LC initiated by GW. Forbidden letter received
Error or Event on LC initiated by GW. Forbidden letter received
Error or Event on LC initiated by GW. No buffer for secondary
letter
Error or Event on LC initiated by GW. No buffer for fragmented
letter
Error or Event on LC initiated by GW. Disconnect on end of phase
record
Error or event on LC initiated by GW. No buffer for control letter.
Error or event on LC initiated by GW. Mailbox in closing phase
Error or event on LC initiated by GW. Flow control error.
Error or event on LC initiated by GW. CH locked by operator.
Error or event on LC initiated by GW. Disconnect with a normal
TMG F2 exchange.
Error or event on LC initiated by GW. Teletel rerouting error from
DACQ
Error or event on LC initiated by GW. Teletel routing error from
DACQ
Error or event on LC initiated by GW. Teletel rerouting error from
TM
Error or event on LC initiated by GW. Teletel rerouting error from
TM
Syntax error - text too long.
Syntax error - illegal object in a GA command.
Syntax error - unknown node Id.
Syntax error - illegal command for this object.
Syntax error - illegal date.
(X.25) No route available for X.25 switching.
No more network routes available for switching.
(X.25) Hop count reached for X.25 switching.
G&R/Gproxy
77
G&R
0083
0085
0086
0087
0090
0092
0093
0094
0096
009C
009D
009E
009F
00B2
00B6
00C0
00D7
00DE
00E1
00E6
(X.25) Flow control negotiation error.
(X.25) Frame level disconnection.
(X.25) Frame level connection.
(X.25) Frame level reset.
Frame level not set.
(X.25) X.25 Echo service in use.
(X.25) Incorrect password for PAD connection.
(X.25) No more PAD connections allowed.
(X.25) TS SX25 or NU X25 objects locked.
(X.25) Invalid packet header. X.25 protocol error.
(X.25) Incompatible header. X.25 protocol error.
(X.25) Logical Channel Number too high.
(X.25) Incorrect packet type.
Use of invalid password through PAD
Unknown mailbox selection for PAD connection using the PAD
password.
(X.25) Normal disconnection.
(X.25) TS image (of type DSA or DIWS) in LOCK state.
(X.25) NS RMT or NR SW in LOCK state.
Connection refused. Mailbox is not in ENBL state.
QOS not available permanently.
01xx Session Control
0100
0101
0102
0103
0104
0105
0106
0107
0108
0109
010A
010B
010C
010D
010E
010F
0110
78
Logical connection accepted or normal termination
Rejection for unknown reason or abnormal termination
Acceptor node inoperable.
Acceptor node saturated. When a node has no available resources
Acceptor mailbox unknown.
Acceptor mailbox inoperable.
DNS: Acceptor mailbox saturated.
DNS: Acceptor application program saturated.
Transport protocol error or negotiation failed (DSA 200 only).
Dialog protocol error or negotiation failed. (Wrong logical record).
Time-out on session initiation / unknown LID
Acceptor mailbox extension unknown.
Acceptor mailbox extension inoperable.
Invalid Session Number.
Unknown node.
System error. System generation error or insufficient memory space
Application abnormal termination. Subsequent to an abnormal
occurrence in the dialogue
G&R/Gproxy
G&R
0111
0112
0113
0115
0117
0118
0119
011A
011E
011F
0120
0121
0122
0123
0124
0125
0126
0127
0128
0129
012B
012C
012D
012E
012F
0130
0131
0132
0133
0134
013C
013E
013F
0140
0151
0152
0153
0154
0156
Normal terminate rejected.
Protocol not supported.
Session control service purged by user.
Disconnection Time-out on message group initiation.
Incorrect Access Right for MB
Incorrect Access Right for the Application
Pre-negotiated Message Path Descriptor unknown
Security validation failed
Incorrect object status
Not enough memory space available.
Node unknown.
The channel object (CH) is in LOCK state
Saturation - no plug available
Object status = LOCK
Connection block (TSCNX) already used
Disconnection already running
The connection block (TSCNX) is disconnected (or not connected)
Change Credit value < 0
Ineffective Change Credit ( delta = 0 )
No more deferred letters
"Reinitialization" Request
"Reinitialization" in progress
"Reinitialization" in progress, letters are dropped
Close virtual circuit. Either no mapping exists between PA/NR or
CL and VC/NS
Null connection object index.
Undefined function at Sysgen time.
Letter too large with respect to the negotiated size.
The received letter is longer than the size which was
Disconnection of the session control user
Interface error on EOR (End-Of-Record) processing.
Presentation control protocol error.
You do not have the turn.
Message group closed.
Session is closed.
Request refused, no system buffers available.
Incorrect addressing record.
No presentation record in the ILCAL or ILCRL
Negotiation failed on session mode
Negotiation failed on resynchronization.
G&R/Gproxy
79
G&R
0157
0158
0159
015A
015B
015C
015D
0160
0161
0162
0163
0164
0165
0166
0167
0168
0169
016A
016B
016C
016D
016E
016F
0170
0171
0172
0173
0174
0175
0176
0177
0178
0179
017A
017B
017C
017D
017E
80
Negotiation failed on END to END ACK
No presentation record in the connection letter
Negotiation failed on session mode
Negotiation failed on letter size (in the Logical Connection record).
Negotiation failed on resynchronization (in the Logical Connection
record).
Negotiation failed on end-to-end ACK (Logical Connection record).
No support of the "letter" interface because Multirecord is not
negotiated.
Incorrect TSPACNX table.
Protocol error on letter reception.
Negotiation failure.
Record header length error.
Protocol error.
Protocol error reception of control letter.
Type or length error on interrupt letter.
Protocol error on reception of data letter.
Dialog protocol error.
Unknown event.
Protocol error on data transfer.
Invalid status for a disconnection request.
Invalid status for a recover
Invalid status for a suspend/resume request.
Negotiation failure.
Unknown command.
Error in presentation protocol
Letter header length error in
ILCAL is not DSA 200 protocol.
Error in session record.
Normal disconnection, without complementary reason code.
Letter is not in ASCII or EBCD.
Connection protocol letter header
Letter header protocol error.
Record header protocol error.
Record header length error.
Mbx record header length error.
Error on buffer transfer.
DSA 200 record header protocol
DSA 300 record header protocol
Unsupported connection options.
G&R/Gproxy
G&R
017F
0180
0181
0182
0190
0191
0192
0193
0194
0195
0196
0197
0198
0199
019A
019B
019C
019D
019E
019F
01A0
01A1
01A2
01A3
01A4
01A5
01A6
01A7
01A8
01A9
01AA
01AB
01AC
01C0
01C1
01C2
01C3
01E0
01E1
Character error in ASCII string.
No segmented record size.
Invalid mailbox object index.
Mapping error for a remote connection.
No more buffers.
Byte count is greater than GP.
Byte count is greater than GP.
Byte count is greater than GP.
Byte count is greater than GP.
Byte count is greater than GP.
Byte count is greater than GP.
Byte count is greater than GP.
No more buffers.
Byte count is greater than GP.
Byte count is greater than GP.
Byte count is greater than GP.
Byte count is greater than GP.
Byte count is greater than GP.
Byte count is greater than GP.
Byte count is greater than GP.
Invalid transfer state.
Suspend protocol running.
Suspend protocol running.
Recover protocol running.
Forbidden function in write request. ($WRITE)
Conflicting parameters for segmented record. (SWBREC)
Protocol conflict - suspend/recover.
Protocol not supported - letter/end-to-end ACK. (SWBLET)
Multi-record letter in progress.
Interrupt request forbidden.
Send control record request forbidden. (SCTROL)
Forbidden for TWA session - turn is here. (SREAD)
Termination forbidden - suspend or recover in progress. (STERM)
No space available for downstream connection request. (SMECNX)
No space available for upstream connection request. (SMUCNX)
No space available for upstream SCF connection. (SMRCNX)
No space available for session context. ($SCTX)
Enclosure or data length error for a write request. ($WRITE)
Enclosure or data length error for a write segment record request.
(SWBREC)
G&R/Gproxy
81
G&R
01E2
01E3
01E4
01E8
01E9
01EA
01EB
01EC
Enclosure error for 'give turn' request. (SGVTRN)
Interrupt request is not demand turn, attention/data attention, or
purge record.
Input status for a send control letter is not permitted.
Write request without turn.
Write segmented record request without turn.
Write segmented letter request without turn.
Send control letter request without turn.
Disconnection request without turn.
02xx Presentation Control
0201
0202
0203
0204
0205
0206
0207
0230
0231
0232
0233
0234
0235
0236
0237
Protocol level not supported
Application designation protocol error.
Character encoding error. TM cannot support the proposed
encoding.
Character set error. TM cannot support the proposed character set.
Character subset error. TM cannot support the proposed character
subset.
Incorrect record encoding.
Incorrect parameter encoding.
Data presentation control error. The presentation control proposed
for this session cannot be used
Device type is incompatible with the configuration.
TM control protocol is incorrect.
Device-sharing attributes are invalid.
Initiator or acceptor configuration is not correct.
Logical device index error.
Number of logical devices is incompatible with the configuration.
TM protocol record not supported.
03xx Terminal Management
0300
0301
0302
0303
0304
0305
0306
0307
82
Sysgen error WARNING. There is no mapped object; some objects
will be spare.
Operator requested session abort or logged.
Idle time run out after secondary network failure.
Idle time run out for no traffic.
Form not found.
Operator requested suspension.
Destructive attention send on the session.
Unknown TX addressed in this session. TM is unable to a the
session.
G&R/Gproxy
G&R
030A
0310
031E
0320
0321
0322
0323
0324
0325
0326
0327
0328
0329
032A
032B
032C
032D
032E
0330
0331
0332
0340
0341
0342
0343
0344
0345
0346
0347
0348
0349
034A
0350
0360
0361
0362
0370
Protocol error. A record was received which did not comply with
current standards
Insufficient resources. The receiver cannot act on the request
because of a temporary
Incorrect value for Retry or Wait parameters on UP LL command.
Function not supported.
Parameter error. This can result
Resource not available. The
Intervention required (on principal device).
Request not executable.
EOI required.
Presentation space altered, request executed.
Presentation space altered, request not executed.
Presentation space integrity lost.
Device busy. The device is busy and cannot execute the request.
Device disconnected.
Resource not configured.
Symbol set not loaded.
Read partition state error.
Page overflow.
Subsidiary device temporarily not available.
Intervention required at subsidiary device.
Request not executable because of subsidiary device.
TM cannot accept a new connection.
Object status incorrect.
The TM configuration is not correct.
Unknown TX addressed on this session.
Data presentation protocol error.
Device type is incompatible with the configuration, or is not
supported.
TM control protocol incorrect.
Device shareability attributes are invalid.
Initiator or acceptor configuration is not correct.
Logical device index error.
Number of logical devices incompatible with the configuration.
Disconnection of TM after reinitialization of the network.
File not found. (Welcome and Broadcast Messages)
Site not found. (Welcome and Broadcast Messages)
NASF error. (Welcome and Broadcast Messages)
No-session timeout. Device disconnected.
G&R/Gproxy
83
G&R
0371
0372
0373
0374
0375
0376
0380
0381
0382
0383
0384
038C
0390
0391
0392
03C0
No-input timeout. Device disconnected.
No-output timeout. Device disconnected.
Timeout due to no backup session being initiated.
Timeout due to no backup session being established.
Connection refused because of late activation of back up session.
Disconnection of current session to switch to backup session.
AUTOCN parameter not declared.
Mixed ETB in data sent by VIP screen and cassette
Data header sent by the terminal incorrect.
Desynchronization in the exchange of data.
KDS block count error.
Remote terminal is not connected
Unknown mailbox.
No call packet to return.
No "Possibility" command to return Protocol error
Slave device disconnection.
17xx Network Layer
1701
1702
1706
1707
1708
1709
1710
1711
1712
1713
1714
1717
1718
1719
171A
171B
171C
171E
171F
1721
1723
1724
84
PAD connection refused.
Flow control error.
Logical channel number not zero in restart packet.
Illegal packet length or use of D-bit forbidden.
Illegal header.
Illegal Logical Channel Number.
Invalid packet type for the automaton state. Protocol error
Incorrect packet type.
Inconsistent network parameters in the generation file.
No more space.
DSAC network layer object not usable.
USED/ENBL transition. Transport station is locked.
USED/ENBL transition. This is a back-up NR.
USED/ENBL transition. Dynamic close due to load.
USED/ENBL transition. Transfer time-out has elapsed.
USED/ENBL transition. This is a back-up NR.
USED/ENBL transition. Transport station is idle.
USED/ENBL transition. NR object is locked.
ENBL/LOCK transition. NR HDLC has no more memory space.
Remote station is inaccessible via the configured network. Check
Incorrect PAD password.
Virtual circuit already in use. LCN (Logical Channel Number) too
high.
G&R/Gproxy
G&R
1725
1726
1727
1729
1731
1732
1733
1740
1741
1742
1744
1745
1747
1749
174F
1755
1760
1770
1771
1781
1782
1783
1785
1786
1787
1790
1791
1792
1793
1794
1795
179B
179D
179E
179F
Invalid virtual circuit.
Packet too short. Protocol error for the equipment directly connected
to the Bull Datanet.
Incompatibility between the generation parameters of two
communicating systems on window or packet size.
Packet size in communicating systems not the same.
Timer runs out while waiting for call confirmation.
Timer runs out while waiting for clear confirmation.
Timer has run out while waiting a reset confirm.
Call setup or call clearing problem.
Open failure on virtual circuit. No flow control on this NS.
Incorrect facility. Protocol error for the equipment directly
connected to the Bull Datanet.
Unknown subscriber.
End of time-out on reset confirm. Invalid facility length. Protocol
error for the equipment directly
No logical channel available.
End of time-out on call confirm.
Incorrect packet length. Protocol error for the equipment directly
connected to the Bull Datanet.
Flow control, window, packet size or reset error.
Frame disconnection.
Frame connection.
Frame reset.
No more network routes available for X.25 switching.
Maximum of 15 switches have been used,
Flow control negotiation error.
Frame level disconnection.
Frame level connection.
Frame level reset.
Frame level not established.
No more logical paths available for the PAD.
Echo service busy.
Incorrect PAD password.
All the PAD virtual circuits are used
X.25 initialization not possible.
LCN not null in restart packet
Incompatible header (receive error: all VC of concerned NS
LCN greater than NBVC in NS directive
Incorrect packet type
G&R/Gproxy
85
G&R
17A0
17B0
17B1
17B2
17B3
17B4
17B5
17B6
17B8
17B9
17CB
17CC
17CE
17CF
17D0
17D4
17D7
17DD
17DE
17DF
17E0
17E1
17E2
17E3
17E4
17E5
17E6
17E7
17E9
17EB
17EE
17FF
Invalid facility.
Normal disconnection.
X.25 Echo in use.
No more logical channels available.
No more PAD connections allowed.
TS SX25 or NU X25 object locked.
Buffer capacity overflow.
Normal disconnection.
Unknown calling SNPA (Sub-Network Point of Attachment).
Internet problem.
Call collision on VC
Incompatible generations (NR object without mapping).
Invalid status NR locked.
Lack of space.
Unknown subscriber.
TSCNX already used for another connection. SCF internal error.
Transport station locked.
Proper NS locked.
Invalid status NR locked.
Lack of space.
Forbidden parameter or invalid value.
Invalid transition.
Upward-mapped object (TS) not locked.
No object mapped above.
NR not locked (MP NR -ADD/-SUB) or virtual circuit already open.
NR is last in list and the TS is not locked.
No object mapped above (UP NR -PRIO). NR not mapped on TS.
Upward mapped object not locked
Mix of datagram and connection network
Class inconsistent with NR.
Incompatible generations. NR object without mapping.
Wrong parameter in administrative CALL
18xx Transport Layer
1800
1801
1802
1803
1804
1805
86
Normal disconnection initiated by the correspondent
Local saturation at connection request time.
Failed negotiation at connection time.
Duplicate connection. Two or more requests have been issued for
the same connection.
Redundant request.
Retransmission Time-out at transport level.
G&R/Gproxy
G&R
1806
1807
1808
1809
180A
180B
180C
1817
181F
1821
1824
182E
182F
1831
1832
1833
1834
1835
183A
183C
1840
18A1
18B0
18EF
Survey time-out at transport level.
Transport protocol error.
Session Control specified is not available (inaccessible).
Requested Session Control Id unknown by remote transport.
Termination because of disconnection by administration.
Session Control/Transport interface error.
Connection request on non-sharable VC in case of ISO Transport.
ISO: header or parameter length is invalid.
Station in shut-down state.
No memory space at connection time.
Session Control inaccessible by configured session routes. ISO:
Session entity not attached to TSAP.
Collision between Close NC and Open TC.
Remote station not configured.
Resource saturation.
ISO: No route for the called NSAP.
ISO: Received NSAP addresses are wrong.
Segmentation violation.
ISO:QOS priority not available temporarily, due to a local condition
(for example, lack of resources).
ISO:QOS priority permanently unavailable locally (for example, due
to an error in the system generation).
ISO: Remote reason not specified.
ISO: Remote transport entity congestion at connect request time.
Server in terminating state. TC has been re-assigned on another NC.
An additional NC has been assigned to a TC.
NC has been re-assigned on another VC.
Disconnection at Transport level caused by reception of RESTART
DSA during the transfer phase.
Windows Sockets error Codes
Below is a list of Windows Sockets return codes and the corresponding
description.
Hex
code
Windows Sockets Access
Error name
G&R/Gproxy
Description
87
G&R
88
2714
WSAEINTR
2719
271E
WSAEBADF
WSAEFAULT
2726
WSAEINVAL
2728
WSAEMFILE
2733
WSAEWOULDBLOCK
2734
WSAEINPROGRESS
2735
WSAEALREADY
2736
2737
2738
WSAENOTSOCK
WSAEDESTADDRREQ
WSAEMSGSIZE
2739
WSAEPROTOTYPE
273A
WSAENOPROTOOPT
273B
WSAEPROTONOSUPPORT
273C
WSAESOCKTNOSUPPORT
273D
WSAEOPNOTSUPP
273E
273F
WSAEPFNOSUPPORT
WSAEAFNOSUPPORT
2740
WSAEADDRINUSE
2741
WSAEADDRNOTAVAIL
The (blocking) call was cancelled
via WSACancelBlockingCall()
The socket descriptor is not valid.
An invalid argument was supplied
to the Windows Sockets API.
An invalid call was made to the
Windows Sockets API.
No more file descriptors are
available.
The socket is marked as nonblocking and no connections are
present to be accepted.
A blocking Windows Sockets call
is in progress.
The asynchronous routine being
cancelled has already completed.
The descriptor is not a socket.
A destination address is required.
The datagram was too large to fit
into the specified buffer and was
truncated.
The specified protocol is the wrong
type for this socket.
The option is unknown or
unsupported.
The specified protocol is not
supported.
The specified socket type is not
supported in this address family.
The referenced socket is not a type
that supports connection-oriented
service.
The specified address family is not
supported by this protocol.
The specified address is already in
use.
The specified address is not
available from the local machine.
G&R/Gproxy
G&R
2742
WSAENETDOWN
2743
WSAENETUNREACH
2744
WSAENETRESET
2745
2746
2747
WSAECONNABORTED
WSAECONNRESET
WSAENOBUFS
2748
2749
274A
274B
274C
WSAEISCONN
WSAENOTCONN
WSAESHUTDOWN
WSAETOOMANYREFS
WSAETIMEDOUT
274D
WSAECONNREFUSED
274E
WSAELOOP
274F
2750
2751
2752
2753
2754
2755
2756
2757
276B
WSAENAMETOOLONG
WSAEHOSTDOWN
WSAEHOSTUNREACH
WSAENOTEMPTY
WSAEPROCLIM
WSAEUSERS
WSAEDQUOT
WSAESTALE
WSAEREMOTE
WSASYSNOTREADY
G&R/Gproxy
The Windows Sockets
implementation has detected that
the network subsystem has failed.
The network address can't be
reached from this host. There is
probably a problem in the way you
have set up TCP/IP routing for
your PC (most likely you have not
defined a default router).
The connection must be reset
because the Windows Sockets
implementation dropped it.
The connection has been closed.
Not enough buffers available, or
too many connections.
The socket is already connected.
The socket is not connected.
The socket has been shutdown.
Attempt to connect timed out
without establishing a connection.
The attempt to connect was
forcefully rejected. The service on
the other side is not available.
Too many symbolic links were
encountered in translating the path
name.
The host machine is out of service.
The host machine is unreachable.
Indicates that the underlying
network subsystem is not ready for
network communication.
89
G&R
90
276C
WSAVERNOTSUPPORTED
276D
WSANOTINITIALISED
2AF9
WSAHOST_NOT_FOUND
2AFA
WSATRY_AGAIN
2AFB
WSANO_RECOVERY
2AFC
WSANO_DATA
The version of Windows Sockets
API support requested is not
provided by this particular
Windows Sockets implementation.
A successful WSAStartup() must
occur before using this API.
Authoritative answer host not
found.
Non-authoritative answer host not
found, or SERVERFAIL.
Non-recoverable errors,
FORMERR, REFUSED, NOTIMP.
Valid name, no data record of
requested type.
G&R/Gproxy
G&R
Appendix: G&R MIB
extension
GAR-MIB DEFINITIONS ::= BEGIN
-• GAR-MIB: This MIB defines the G&R manageable objects.
-IMPORTS
enterprises, Counter
FROM RFC1155-SMI
OBJECT-TYPE
FROM RFC-1212
TRAP-TYPE
FROM RFC-1215
gar
OBJECT IDENTIFIER ::= { enterprises 827 }
garTrapEvnt
OBJECT IDENTIFIER ::= { gar 1 }
garTrapStat
OBJECT IDENTIFIER ::= { gar 2 }
-• garTrap Group
-• The trap group contains information about traps sent by the
• various G&R-programs in the network.
• Trap TE: Contains all info available for a spec event
• Trap TS: Statistics trap, IO counters etc
-• Currently all ServerX comms programs (using GL_DIWS) and all
• DNTD gateways broadcast information which is processed by the
• G&R proxy SNMP agent (Gproxy).
• Specific trap numbers used:
• 1 (host connect),
• 2 (host disconnect),
• 3 (failed host connect)
• 4 (statistics)
G&R/Gproxy
91
G&R
• Event trap
garTEProgNo
SYNTAX
gwnb6(1),
gwnw6(2),
gwtcp6(3),
gldiws(10),
glx25(11),
gltcp(12),
glsna(13),
qsim(20),
pthru(21),
v78sim(22),
g3270(23),
padcon(24),
gmailer(25),
gspool(26),
guft(27),
guftsrv(28)
OBJECT-TYPE
INTEGER{
}
ACCESS
read-only
STATUS
mandatory
DESCRIPTION “Identifies the broadcasting application (program) type”
::= { garTrapEvnt 1 }
garTEProgAddress
OBJECT-TYPE
SYNTAX
OCTET STRING
ACCESS
read-only
STATUS
mandatory
DESCRIPTION “Network address of broadcasting program”
::= { garTrapEvnt 2 }
garTEPid
OBJECT-TYPE
SYNTAX
OCTET STRING
ACCESS
read-only
STATUS
mandatory
DESCRIPTION “Pid (ServerX) or gatewayname”
::= { garTrapEvnt 3 }
garTESerialNo
OBJECT-TYPE
SYNTAX
INTEGER
ACCESS
read-only
STATUS
mandatory
DESCRIPTION “Broadcasting programs broadcast serial number”
::= { garTrapEvnt 4 }
garTEProgVersion
OBJECT-TYPE
SYNTAX
OCTET STRING
ACCESS
read-only
STATUS
mandatory
DESCRIPTION “Version/release number of broadcasting program”
::= { garTrapEvnt 5 }
garTEUserName
OBJECT-TYPE
SYNTAX
OCTET STRING
ACCESS
read-only
STATUS
mandatory
DESCRIPTION “Name of (end-)user”
::= { garTrapEvnt 6 }
garTEUserAddr
OBJECT-TYPE
SYNTAX
OCTET STRING
ACCESS
read-only
STATUS
mandatory
DESCRIPTION “Network address of (end-) user (if gateway)”
::= { garTrapEvnt 7 }
92
G&R/Gproxy
G&R
garTESessionNo
OBJECT-TYPE
SYNTAX
INTEGER
ACCESS
read-only
STATUS
mandatory
DESCRIPTION “The session number in question.
Applicable for gateways only.”
::= { garTrapEvnt 8 }
garTEHostName
OBJECT-TYPE
SYNTAX
OCTET STRING
ACCESS
read-only
STATUS
mandatory
DESCRIPTION “Name of host (TSAP/SC-ID or Insid)”
::= { garTrapEvnt 9 }
garTERetcode
OBJECT-TYPE
SYNTAX
INTEGER
ACCESS
read-only
STATUS
mandatory
DESCRIPTION “Error code returned in case of connection failure”
::= { garTrapEvnt 10 }
• Statistics trap
garTSProgNo
OBJECT-TYPE
SYNTAX
INTEGER
ACCESS
read-only
STATUS
mandatory
::= { garTrapStat 1 }
garTSProgAddress
OBJECT-TYPE
SYNTAX
OCTET STRING
ACCESS
read-only
STATUS
mandatory
::= { garTrapStat 2 }
garTSPid
OBJECT-TYPE
SYNTAX
OCTET STRING
ACCESS
read-only
STATUS
mandatory
::= { garTrapStat 3 }
garTSSerialNo
OBJECT-TYPE
SYNTAX
INTEGER
ACCESS
read-only
STATUS
mandatory
::= { garTrapStat 4 }
garTSSessNo
OBJECT-TYPE
SYNTAX
INTEGER
ACCESS
read-only
STATUS
mandatory
DESCRIPTION “Current no of sessions”
::= { garTrapStat 5 }
garTSMaxNo
OBJECT-TYPE
SYNTAX
INTEGER
ACCESS
read-only
STATUS
mandatory
DESCRIPTION “Max no. of sessions since last report”
::= { garTrapStat 6 }
garTSMinNo
OBJECT-TYPE
SYNTAX
INTEGER
ACCESS
read-only
STATUS
mandatory
DESCRIPTION “Min no. of sessions since last report”
::= { garTrapStat 7 }
garTSUpstream
OBJECT-TYPE
SYNTAX
INTEGER
G&R/Gproxy
93
G&R
ACCESS
read-only
STATUS
mandatory
DESCRIPTION “Number of octets sent to host”
::= { garTrapStat 8 }
garTSDownstream
OBJECT-TYPE
SYNTAX
INTEGER
ACCESS
read-only
STATUS
mandatory
DESCRIPTION “Number of octets sent to host”
::= { garTrapStat 9 }
END
94
G&R/Gproxy
G&R
G&R/Gproxy
95
G&R
96
G&R/Gproxy
G&R
Appendix: Formatted SNMP
trap trace
SNMP trap formatted (‘Sniffer’ format) dump:
- - - - - - - - - - - - - - - - Frame 1 - - - - - - - - - - - - - - - - SUMMARY Delta T
Destination
Source
Summary
M
1
ArildDell
Arild Zenith
ARP R PA=[192.150.211.25]
HA=0000C0F2A817 PRO=IP
ARP:
ARP:
ARP:
ARP:
ARP:
ARP:
ARP:
ARP:
ARP:
ARP:
ARP:
ARP:
----- ARP/RARP frame ----Hardware type = 1 (10Mb Ethernet)
Protocol type = 0800 (IP)
Length of hardware address = 6 bytes
Length of protocol address = 4 bytes
Opcode 2 (ARP reply)
Sender’s hardware address = WstDigF2A817, Arild Zenith
Sender’s protocol address = [192.150.211.25]
Target hardware address = 00608CB3A339, ArildDell
Target protocol address = [192.150.211.12]
ADDR HEX
ASCII
0000 00 60 8C B3 A3 39 00 00 C0 F2 A8 17 08 06 00 01 .‘...9..........
0010 08 00 06 04 00 02 00 00 C0 F2 A8 17 C0 96 D3 19 ................
0020 00 60 8C B3 A3 39 C0 96 D3 0C 00 00 00 00 00 00 .‘...9..........
0030 00 00 00 00 23 21 79 17 02 00 00 00
....#!y.....
- - - - - - - - - - - - - - - - Frame 2 - - - - - - - - - - - - - - - - SUMMARY Delta T
Destination
Source
Summary
2
0.0005 Arild Zenith
ArildDell
SNMP Trap Enterprise specific
enterprise.827.1.1 .. enterprise.827.1.9 (9 items)
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
----- Simple Network Management Protocol ----Version = 0
Community = public
Command = Trap
Enterprise = {1.3.6.1.4.1.827}
Network address = [192.150.211.12]
Generic trap = 6 (Enterprise specific)
Specific trap = 2
Time ticks = 239500
Object = {1.3.6.1.4.1.827.1.1} (enterprise.827.1.1)
Value = 2
Object = {1.3.6.1.4.1.827.1.2} (enterprise.827.1.2)
Value = 00006E205FC5
Object = {1.3.6.1.4.1.827.1.3} (enterprise.827.1.3) SNMP: Value
=
Object = {1.3.6.1.4.1.827.1.4} (enterprise.827.1.4)
G&R/Gproxy
97
G&R
SNMP: Value = 17
SNMP:
SNMP: Object = {1.3.6.1.4.1.827.1.5} (enterprise.827.1.5)
SNMP: Value =
SNMP:
SNMP: Object = {1.3.6.1.4.1.827.1.6} (enterprise.827.1.6)
SNMP: Value = ARILD
SNMP:
SNMP: Object = {1.3.6.1.4.1.827.1.7} (enterprise.827.1.7)
SNMP: Value = 00608CB3A339
SNMP:
SNMP: Object = {1.3.6.1.4.1.827.1.8} (enterprise.827.1.8)
SNMP: Value = 0
SNMP:
SNMP: Object = {1.3.6.1.4.1.827.1.9} (enterprise.827.1.9)
SNMP: Value = Ella Server
SNMP:
ADDR HEX
ASCII
0000 00 00 C0 F2 A8 17 00 60 8C B3 A3 39 08 00 45 00 .......‘...9..E.
0010 00 FF 00 10 00 00 3C 11 56 8B C0 96 D3 0C C0 96 ......<.V.......
0020 D3 19 78 77 00 A2 00 EB 20 FB 30 82 00 DF 02 01 ..xw.... .0.....
0030 00 04 06 70 75 62 6C 69 63 A4 82 00 D0 06 07 2B ...public......+
0040 06 01 04 01 86 3B 04 04 C0 96 D3 0C 02 01 06 02 .....;..........
0050 01 02 02 03 03 A7 8C 30 82 00 B2 30 0E 06 09 2B .......0...0...+
0060 06 01 04 01 86 3B 01 01 02 01 02 30 19 06 09 2B .....;.....0...+
0070 06 01 04 01 86 3B 01 02 04 0C 30 30 30 30 36 45 .....;....00006E
0080 32 30 35 46 43 35 30 0D 06 09 2B 06 01 04 01 86 205FC50...+.....
0090 3B 01 03 04 00 30 0E 06 09 2B 06 01 04 01 86 3B ;....0...+.....;
00A0 01 04 02 01 11 30 0D 06 09 2B 06 01 04 01 86 3B .....0...+.....;
00B0 01 05 04 00 30 12 06 09 2B 06 01 04 01 86 3B 01 ....0...+.....;.
00C0 06 04 05 41 52 49 4C 44 30 19 06 09 2B 06 01 04 ...ARILD0...+...
00D0 01 86 3B 01 07 04 0C 30 30 36 30 38 43 42 33 41 ..;....00608CB3A
00E0 33 33 39 30 0E 06 09 2B 06 01 04 01 86 3B 01 08 3390...+.....;..
00F0 02 01 00 30 18 06 09 2B 06 01 04 01 86 3B 01 09 ...0...+.....;..
0100 04 0B 45 6C 6C 61 20 53 65 72 76 65 72 53
..Ella ServerS
- - - - - - - - - - - - - - - - Frame 3 - - - - - - - - - - - - - - - - SUMMARY Delta T
Destination
Source
Summary
3
1.1384 Arild Zenith
ArildDell
SNMP Trap Enterprise specific
enterprise.827.1.1 .. enterprise.827.1.9 (9 items)
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
98
----- Simple Network Management Protocol ----Version = 0
Community = publicSNMP: Command = Trap
Enterprise = {1.3.6.1.4.1.827}
Network address = [192.150.211.12]
Generic trap = 6 (Enterprise specific)
Specific trap = 1
Time ticks = 239500
Object = {1.3.6.1.4.1.827.1.1} (enterprise.827.1.1)
Value = 2
Object = {1.3.6.1.4.1.827.1.2} (enterprise.827.1.2)
Value = 00006E205FC5
Object = {1.3.6.1.4.1.827.1.3} (enterprise.827.1.3)
Value =
Object = {1.3.6.1.4.1.827.1.4} (enterprise.827.1.4)
Value = 18
G&R/Gproxy
G&R
SNMP:
SNMP: Object = {1.3.6.1.4.1.827.1.5} (enterprise.827.1.5)
SNMP: Value =
SNMP:
SNMP: Object = {1.3.6.1.4.1.827.1.6} (enterprise.827.1.6)
SNMP: Value = ARILD
SNMP:
SNMP: Object = {1.3.6.1.4.1.827.1.7} (enterprise.827.1.7)
SNMP: Value = 00608CB3A339
SNMP:
SNMP: Object = {1.3.6.1.4.1.827.1.8} (enterprise.827.1.8)
SNMP: Value = 0
SNMP:
SNMP: Object = {1.3.6.1.4.1.827.1.9} (enterprise.827.1.9)
SNMP: Value = Ella Server
SNMP:
ADDR HEX
ASCII
0000 00 00 C0 F2 A8 17 00 60 8C B3 A3 39 08 00 45 00 .......‘...9..E.
0010 00 FF 00 11 00 00 3C 11 56 8A C0 96 D3 0C C0 96 ......<.V.......
0020 D3 19 78 77 00 A2 00 EB 1F FC 30 82 00 DF 02 01 ..xw......0.....
0030 00 04 06 70 75 62 6C 69 63 A4 82 00 D0 06 07 2B ...public......+
0040 06 01 04 01 86 3B 04 04 C0 96 D3 0C 02 01 06 02 .....;..........
0050 01 01 02 03 03 A7 8C 30 82 00 B2 30 0E 06 09 2B .......0...0...+
0060 06 01 04 01 86 3B 01 01 02 01 02 30 19 06 09 2B .....;.....0...+
0070 06 01 04 01 86 3B 01 02 04 0C 30 30 30 30 36 45 .....;....00006E
0080 32 30 35 46 43 35 30 0D 06 09 2B 06 01 04 01 86 205FC50...+.....
0090 3B 01 03 04 00 30 0E 06 09 2B 06 01 04 01 86 3B ;....0...+.....;
00A0 01 04 02 01 12 30 0D 06 09 2B 06 01 04 01 86 3B .....0...+.....;
00B0 01 05 04 00 30 12 06 09 2B 06 01 04 01 86 3B 01 ....0...+.....;.
00C0 06 04 05 41 52 49 4C 44 30 19 06 09 2B 06 01 04 ...ARILD0...+...
00D0 01 86 3B 01 07 04 0C 30 30 36 30 38 43 42 33 41 ..;....00608CB3A
00E0 33 33 39 30 0E 06 09 2B 06 01 04 01 86 3B 01 08 3390...+.....;..
00F0 02 01 00 30 18 06 09 2B 06 01 04 01 86 3B 01 09 ...0...+.....;..
0100 04 0B 45 6C 6C 61 20 53 65 72 76 65 72 53
..Ella ServerS
- - - - - - - - - - - - - - - - Frame 4 - - - - - - - - - - - - - - - - SUMMARY Delta T
Destination
Source
Summary
4 122.1291 Arild Zenith
ArildDell
SNMP Trap Enterprise specific
enterprise.827.2.1 .. enterprise.827.2.9 (9 items)
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
----- Simple Network Management Protocol ----Version = 0
Community = public
Command = Trap
Enterprise = {1.3.6.1.4.1.827}
Network address = [192.150.211.12]
Generic trap = 6 (Enterprise specific)
Specific trap = 4
Time ticks = 252000
Object = {1.3.6.1.4.1.827.2.1} (enterprise.827.2.1)
Value = 2
Object = {1.3.6.1.4.1.827.2.2} (enterprise.827.2.2)
Value = 00006E205FC5
Object = {1.3.6.1.4.1.827.2.3} (enterprise.827.2.3)
Value =
Object = {1.3.6.1.4.1.827.2.4} (enterprise.827.2.4)
Value = 19
G&R/Gproxy
99
G&R
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
SNMP:
ADDR
0000
0010
0020
0030
0040
0050
0060
0070
0080
0090
00A0
00B0
00C0
00D0
00E0
00F0
100
Object = {1.3.6.1.4.1.827.2.5} (enterprise.827.2.5)
Value = 2
Object = {1.3.6.1.4.1.827.2.6} (enterprise.827.2.6)
Value = 2
Object = {1.3.6.1.4.1.827.2.7} (enterprise.827.2.7)
Value = 0
Object = {1.3.6.1.4.1.827.2.8} (enterprise.827.2.8)
Value = 188
Object = {1.3.6.1.4.1.827.2.9} (enterprise.827.2.9)
Value = 20092
HEX
00 00
00 E9
D3 19
00 04
06 01
01 04
06 01
06 01
32 30
3B 02
02 04
02 05
02 06
02 07
02 08
3B 02
C0
00
78
06
04
02
04
04
35
03
02
02
02
02
02
09
F2
12
77
70
01
03
01
01
46
04
01
01
01
01
02
02
A8
00
00
75
86
03
86
86
43
00
13
02
02
00
00
02
17
00
A2
62
3B
D8
3B
3B
35
30
30
30
30
30
BC
4E
00
3C
00
6C
04
60
02
02
30
0E
0E
0E
0E
0F
30
7C
60
11
D5
69
04
30
01
02
0D
06
06
06
06
06
0F
53
8C
56
04
63
C0
82
02
04
06
09
09
09
09
09
06
B3
9F
3C
A4
96
00
01
0C
09
2B
2B
2B
2B
2B
09
A3
C0
30
82
D3
9C
02
30
2B
06
06
06
06
06
2B
39
96
82
00
0C
30
30
30
06
01
01
01
01
01
06
08
D3
00
BA
02
0E
19
30
01
04
04
04
04
04
01
00
0C
C9
06
01
06
06
30
04
01
01
01
01
01
04
45
C0
02
07
06
09
09
36
01
86
86
86
86
86
01
00
96
01
2B
02
2B
2B
45
86
3B
3B
3B
3B
3B
86
ASCII
.......‘...9..E.
......<.V.......
..xw.....<0.....
...public......+
.....;..........
......‘0...0...+
.....;.....0...+
.....;....00006E
205FC50...+.....
;....0...+.....;
.....0...+.....;
.....0...+.....;
.....0...+.....;
.....0...+.....;
......0...+.....
;....N|S
G&R/Gproxy
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement